FCC ID: P27GEN3505A CBRS Fixed Wireless CPE

CPE User Manual CPE CPE User Manual Version Author Time 2.1 Samson Sun 2018/9/7 Copyright 2018 Sercomm Corporation. All Rights Reserved. Sercomm Corporation reserves the right to make changes to this document without notice. Sercomm Corporation makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose. Sercomm Corporation assumes no liability arising out of the application or use of any product or circuit. Sercomm Corporation specifically disclaims any and all liability, including without limitation consequential or incidental damages; neither does it convey any license under its patent rights, nor the rights of others. 1 CPE User Manual Document Revision History version date reasons and contents 1.0 2017/05/08 Initial Version 1.1 2017/05/18 1.Translate to English 2.Add Senior maintenance author Samson Sun Zack Zuo 1.2 2017/05/19 Samson Sun 1. Modify some expression . 1.3 2017/07/03 Samson Sun 1. Update LED spec 2. Update snapshot base on new style . 3. Add multi PDN configuration 4. Add KPI analysis 2017/07/18 Leanshaw Zhao 1. Add Configure working band 2017/08/10 Phoebe Ge 1.How to disable PIN 2017/10/18 Binary Xue 1. Add ARM1 upgrade method 2018/02/09 Phoebe Ge 1. Add save PM log to Flash 2018/3/30 Sally Luo 1.Add ssl test 2018/4/4 Phoebe Ge 1.Add Host_cm Enable 2018/08/27 Sandy Yang 1. Add 2.7 SAS 2. Add 2.SAS Test 1. 2.7 SAS 2. 2.SAS Test 2.1 2018/09/07 Sandy Yang 1.4 1.5 1.6 1.7 1.8 1.9 2.0 2 CPE User Manual Index

............................................................................................................................... 2 Document Revision History .............................................................................................................. 2

.................................................................................................................................................. 3 Index ................................................................................................................................................. 3

........................................................................................................................................... 6 Primary Maintenance ........................................................................................................................ 6 1. CPE .......................................................................................................... 6 CPE Status Check ..................................................................................................................... 6 1.1.CPE .................................................................................................... 6 Environment check ........................................................................................................... 6 1.2. USIM ..................................................................................................... 6 USIM Card check .............................................................................................................. 6 1.3. PIN ................................................................................................................. 6 Disable PIN ....................................................................................................................... 6 1.4. CPE ....................................................................................... 7 Network information ......................................................................................................... 7 1.5. CPE ....................................................................................................... 9 CPE Version ...................................................................................................................... 9 1.6.LED ........................................................................................................................... 10 LED ................................................................................................................................. 10 2. CPE ................................................................................................................ 11 Configure CPE ........................................................................................................................ 11 2.1.APN ......................................................................................................... 11 Configure APN Name ..................................................................................................... 11 2.2. .......................................................................................................... 12 Configure Search List ..................................................................................................... 12 2.3. log Flash ...................................................................................................... 13 Save PM log into Flash ................................................................................................... 13 2.4./ Host_cm .................................................................................................. 14 Host_cm Enable/Disable ................................................................................................. 14 2.5. .......................................................................................................... 14 Factory Default ............................................................................................................... 14 2.6. .......................................................................................................... 15 Configure working band ................................................................................................. 15 2.7 SAS .................................................................................................. 16 SAS parameter configure ................................................................................................ 16 3.CPE ............................................................................................................................. 18 CPE Upgrade .......................................................................................................................... 18 3.1.CPE .......................................................................................................... 18 CPE Upgrade Method ..................................................................................................... 18 3 CPE User Manual 3.2.ARM1 ....................................................................................................... 18 CPE ARM1 Upgrade Method ......................................................................................... 18 Get CPE Logs ......................................................................................................................... 20 4.1. CPE ......................................................................................... 20 Check CPE Logs by GUI ................................................................................................ 20 4.2. CPE ................................................................................. 21 Download CPE logs by GUI ........................................................................................... 21 5. ................................................................................................................. 23 Troubleshooting and Handling ................................................................................................ 23 5.1.LTE ................................................................................................... 23 Check LTE Connection Status ........................................................................................ 23 5.1.1 USIM Checking ............................................................................. 23 USIM Checking Error analysis ............................................................................... 23 5.1.2 Network Searching ........................................................................ 23 Network Searching Error ........................................................................................ 23 5.1.3 Attaching ....................................................................................... 24 Attach Error ............................................................................................................. 24 5.2.LTE ................................................................................................... 24 CPE Wireless Quality ...................................................................................................... 24 5.2.1 CPE ....................................................................................... 25 CPE Signal Strength ................................................................................................ 25 5.2.2 CPE ........................................................................................... 26 CPE BLER .............................................................................................................. 26 5.2.3 CPE RI .................................................................................................. 27 5.2.4 CPE ............................................................................................... 27 CPE Throughput ...................................................................................................... 27 5.2.5 CPE ....................................................................................... 27 5.3.LTE ........................................................................................................... 29 LTE signaling .................................................................................................................. 29 5.3.1 NAS ............................................................................................... 29 NAS signaling ......................................................................................................... 29 5.3.2 RRC ............................................................................................... 30 RRC signaling ......................................................................................................... 30

......................................................................................................................................... 32 Advanced Management ................................................................................................................... 32 6. .................................................................................................................................... 32 Test .......................................................................................................................................... 32 6.1.iperf .......................................................................................................... 32 iperf download test .......................................................................................................... 32

......................................................................................................................................... 32 1. SSL test ............................................................................................................................... 32 1.1 cpe femto ..................................................................................................... 32 1.2 cpe .................................................................................................................... 34 2. SAS Test ............................................................................................................................ 36 4 CPE User Manual 2.1. ..................................................................................................... 36 2.2. SAS ..................................................................................................................... 36 2.3. sasd log .............................................................................................................. 36 2.4. sasd log ............................................................................................................... 36 2.5. SAS ........................................................................ 36 2.4.1. sasd .................................................................................. 37 2.4.2. sasd Register State ......................................................... 37 2.4.3. eirpCapability .................................................................................. 37

................................................................................................................................................ 39 Appendix ......................................................................................................................................... 39 APLMN Search ........................................................................................ 39 Appendix A: PLMN Search Result ......................................................................................... 39 BATTACH Response ................................................................................ 40 Appendix B: ATTACH Response Result ................................................................................ 40 CCMEError ................................................................................................................ 41 Appendix C: CMEError .......................................................................................................... 41 DESM Cause .............................................................................................................. 43 Appendix D: ESM Cause ........................................................................................................ 43 EEMM Cause ............................................................................................................. 44 5 CPE User Manual Primary Maintenance 1. CPE CPE Status Check 1.1.CPE Environment check 1.2. USIM USIM Card check CPE USIM CPE LED 4 This chapter guides users to check the status of CPE, which includes environment check, USIM card check, network status check and LED check. CPE B4243 B48 There should be B42,B43 or B48 Cells nearby . 1 USIM USIM SIM USIM Card should be properly inserted. 2 USIM USIM The USIM Card should be a registered card by current network. 3 USIM PIN CPE PIN USIM PIN USIM PIN The PIN lock should be disabled with the USIM Card, if not , do PIN unlock before insert it into device . 1.3. PIN Disable PIN 1http://10.10.2.254:8080/

Visithttp://10.10.2.254:8080/

2 LTESIM PIN Locate to LTESIM PIN 3 PIN Management PIN Code PIN Code 6 Enter the PIN Code in PIN Management CPE User Manual 4 Verify Click the Verify button. 5 Disable Click the Disable button. CPE CPE CPE status information would be helpful to investigate issue . You can get basic 1.4. CPE Network information information from GUI, steps as follow 1PC fix IP:10.10.2.2 Fix 10.10.2.2 to PC. 2PC HTTPS://10.10.2.254:admin; admin Log-in to device by web browser , URL is https://10.10.2.254 User name : admin / Password : admin 7 CPE User Manual 3Status fig 1-1 CPE Click [Status] on the left menu. As shown in fig1-1, it contains CPE basic network information. Status Cause:

LTE CPE LTE connection status, indicate current CPE behavior Connection Status: CPE Indicates the connection status of CPE APN:

APN APN name Internet IP Address:

CPE IP IP address assigned from network IMEI:

International Mobile Equipment Identity IMSI:

USIM International Mobile Subscriber Identification Number EARFCN(UL):

TDD UL EARFCN of serving LTE cell EARFCN(DL):

DL EARFCN of serving LTE cell PCI:

Physical Cell ID of serving LTE cell RSSI:

Received Signal Strength Indication of serving LTE cell TAC:

Tracking Area Code of serving LTE cell RSRQ:

Reference Signal Received Quality SINR:

Signal to Interference plus Noise Ratio 8 CPE User Manual Fig1-1 CPE network information 1.5. CPE CPE Version CPE fig 1-2 CPE version is shown in the red area in fig 1-2. Firmware Version:

PKG Version:

ARM1 Version:

CPE CPE Version SDK SDK version Stack Version Stack version 9 CPE User Manual Fig 1-2 CPE and Module version POWER LED SIGNAL LED BLUE GREEN ORANGE GREEN ON OFF OFF RED OFF OFF ON Blink 2 times in 6.4 seconds OFF No Available Cell Blink 3 times in 6.4 seconds OFF OFF OFF Attach Fail Blink 4 times in 6.4 seconds OFF OFF OFF Invalid APN Name Blink 5 times in 6.4 seconds OFF Upgrading BLINK 1.6.LED LED STATUS Power On Power Off No USIM Card SIM PIN Upgrading Fail PLMN Search

/Attaching RSSI (< -106) RSRP (-106 ~ -87) RSRP (> -87) ON ON ON ON ON ON ON ON ON OFF OFF OFF OFF OFF OFF OFF ON OFF OFF OFF OFF OFF OFF OFF OFF OFF ON OFF OFF OFF OFF OFF OFF OFF OFF ON OFF OFF BLINK OFF OFF BLINK OFF OFF OFF OFF 10 CPE User Manual 2. CPE Configure CPE UI CPE UI CPE This chapter guides users to configure CPE, includes basic and advanced configuration, basic describes how to configure on GUI and the advanced describes how to configure specific function. 2.1.APN Configure APN Name 1PC fix IP:10.10.2.2 Fix 10.10.2.2 to PC. URL:https://10.10.2.254 User name : admin Password : admin 2PC HTTPS://10.10.2.254:admin; :admin Log-in to device by web browser 3LTE CPE APN name fig 2-1 Click [LTE] on the left menu, the method is shown in fig2-1:

Fig2-1 Configure APN Name 11 CPE User Manual 1. PDN PDN PDN Notice: CPE supports multiple PDN, each PDN works in different mode, double confirm current network mode and only enables related PDN to protect CPE not in service . 2. APN a) APN(NAT) -- DHCP IPCPE NAT Notice: CPE works as NAT mode. b) APN(Bridge) -- DHCP IPCPE Bridge LTE IP i. IP Notice: CPE works as Bridge mode. There is only connected PC can get IP, To change the other PC, CPE needs to restart. ii. CPE APN IP IP Notice: CPE works as Bridge mode. Connected PC cannot get IP until APNs PDN connection be established successfully. c) APN(VLAN=103) -- vlan APN IP vlan id=103IP Notice: CPE works as Bridge mode and the interface between CPE and connected PC is VLAN, and VLAN ID is 103. d) APN Notice: These three APN can be used at the same time, but there are some condition needs to meet. i. APN APN APN Name Notice: One of three APN name can be empty if there are more than 1 APN used. ii. APN(NAT) +APN(Bridge)CPE APN(NAT) CPE CPE b) Notice: When NAT and Bridge used at the same time, the APN of NAT is used for CPE itself, Bridge APN follow b) rule to work. 2.2. Configure Search List 1PC fix IP:10.10.2.2 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 1PC HTTPS://10.10.2.254:admin; :admin Open your web browser and visit device. 3LTE fig 2-2 12 CPE User Manual Click [LTE] on the left menu, the method is shown in fig2-2:

Search List Refer to examples on GUI. Fig 2-2 Configure Search List 2.3. log Flash Save PM log into Flash 1PC fix IP:10.10.2.2 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2PC HTTPS://10.10.2.254:admin; :admin Open your web browser and visit device. 3SettingsADVANCE PM log save to Flash. Click [Settings] on the left menu, get into the ADVAANCE page, click on PM log save to Flash. 13 CPE User Manual 2.4./ Host_cm Host_cm Enable/Disable 1PC fix IP:10.10.2.2 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2PC HTTPS://10.10.2.254:admin; :admin Open your web browser and visit device. 3SettingsADVANCE Host CM Enable. Click [Settings] on the left menu, get into the ADVAANCE page, click on Host CM Enable. 2.5. Factory Default 14 CPE User Manual 1PC fix IP:10.10.2.2/24 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2PC HTTPS://10.10.2.254:admin; :admin Open your web browser and visit device . 3Administration fig 2-3 Click [Administration] on the left menu, steps are shown in fig2-3 :

Fig 2-3 Factory Default 2.6. Configure working band

(1) PC fix IP:10.10.2.2/24 Fix 10.10.2.2/24 to PC , no Gateway address be assigned .

(2) telnet CPEtelnet 10.10.2.254, /root/gct Telnet 10.10.2.254 username:root password:gct

(3) DM Follow below steps to make CPE enter DM mode 1) shell lted_cli lted_client_init_ex success Under shell, input led_cli, and it will show lted_client_init_ex success 2) DM> DM Press return(or Enter) on the keyboard, if it shows DM>, meas CPE is under DM mode 3) DM> arm1log 2 If it doesn t show DM>, please input arm1log 2 4) q 0 If it show out too much log, please input q 0 under DM mode.

(4) nvm bcfgr 49 0 CPE Input nvm bcfgr 49 0, and it will show current support band list.

(5) nvm bcfgw 49 0 48 CPE 48 Input nvm bcfgw 49 0 48, to set that support band list is 48 in CPE.

(6) nvm bcfgsv 1 Input nvm bcfgsv 1 to save current configure.

(7) CPEkern reboot 15 CPE User Manual Input kern reboot to reboot CPE. Following is a detailed example:

1. telnet 10.10.2.254, root/gct 2. #lted_cli 3. DM>nvm bcfgr 49 0 4. DM>nvm bcfgw 49 0 48 5. DM>nvm bcfgsv 1 6. DM>kern reboot 2.7 SAS SAS parameter configure 1PC fix IP:10.10.2.2/24 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2PC HTTPS://10.10.2.254:admin; :admin Open your web browser and visit device . 3SettingsSAS fig 2-4 Click [Settings] on the left menu, then click [SAS] on the top menu, which is shown in fig2-4 :

4 Configure parameters and upload certificates 16 CPE User Manual 17 Fig 2-4 SAS parameter configure CPE User Manual 3.CPE CPE Upgrade 3.1.CPE CPE Upgrade Method 21PC fix IP: 10.10.2.2 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2 CPE : HTTPS://10.10.2.254 (: admin : admin);

Open your web browser and visit device . 3 Administration ;

Click the Administration. 4 Upgrade ;

Click the Upgrade. 5(: SERCOMM_CPE_101A.bin);

Choose the file you want to upgrade (e.g: SERCOMM_CPE_101A.bin). 6 Upload . Click the Upload button to upgrade. Fig 3-1 CPE Upgrade 3.2.ARM1 CPE ARM1 Upgrade Method 1PC fix IP: 10.10.2.2 18 CPE User Manual Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2 CPE : HTTP://10.10.2.254:8080;

Open your web browser and visit device . 3 System ;

Click the System. 4 Firmware Update ;

Click the Firmware Update. 5(: tk.gz);

Choose the file you want to upgrade (e.g: tk.gz). 6 RAW Format;

Choose RAW Format. 7 Update . Click the Update button to upgrade. 19 CPE User Manual 4. CPE Get CPE Logs 4.1. CPE Check CPE Logs by GUI CPE Steps to check logs as follow:

3PC fix IP:10.10.2.2 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2 CPEHTTPS://10.10.2.254admin admin Open your web browser and visit device . 3 LOG Click [LOG] on the left menu, as shown in fig4-1. 4 LOG LOG There are five sub pages, each shows different kind of CPE logs. LOG CPE Includes running logs such as attach procedure STATUS CPE Includes CPE connection status PM CPE Periodic Monitor Logs such as signal strength and flow statistics NAS NAS NAS signaling during attach RRC RRC RRC signaling during attach 20 CPE User Manual 21 Fig 4-1 CPE Logs 4.2. CPE Download CPE logs by GUI 41PC fix IP: 10.10.2.2 Fix 10.10.2.2/24 to PC , no Gateway address be assigned . 2 CPE : HTTPS://10.10.2.254 (: admin : admin);

Open your web browser and visit device . 3 LOG ;

Click the Administration. 4 Download Log ;

Click the Download Log to download log. 5 Run win_unpackage.bat on Windows OS to generate unzip logs. Fix 4-2 Download CPE Logs CPE User Manual 22 CPE User Manual 5. Troubleshooting and Handling CPE CPE LTE This chapter mainly described how to troubleshooting, we can get the suspicious point from LTE connection status and log analysis . 5.1.LTE Check LTE Connection Status CPE CPE 1.3 Status Cause When CPE attach failed, you can get the reason why CPE attach failed through HealthCheck value which illustrated in chapter 1.3, the value of the HealthCheck is defined as follows:

InitialModule i. ii. USIMChecking iii. ConfigChecking iv. Detaching v. NetworkSearching vi. Attaching vii. PDNActiving viii. Established Success USIMCheckingNetworkSearchingAttaching When a process is normally complete, success will be added to tail of the that step , else a error cause will be added . The following three chapters define the detail of the possible error in in step USIMChecking, NetworkSearching, and Attaching. 5.1.1 USIM Checking USIM Checking Error analysis USIM CME ErrorCME Error C. The section is primarily check USIM, and CME Error is generated if the check fail. Please refer to the appendix C about the definition of CME Error.. 5.1.2 Network Searching Network Searching Error 23 CPE User Manual A The are two mainly cases which may cause the network searching failure , and please get the right reason by searching the error code in appendix A .:

A. A. A frequency is set but any cell in such frequency be broadcast nearby in the environment. In this case , please double confirm you've set with a right frequency . B. No cell available nearby , which causes network searching failed. 5.1.3 Attaching Attach Error PDN Attach Attach PDN Active The procedure of the PDN activation can be separated into two steps : network attach and PDN active, the failure cause of this sub-procedure can be found by searching error code in appendix B . 1Attach B Attach failure (reference appendix B) :

Attach MME USIM Cause EMM 129 RRC Cause EMM 138. The most familiar attach failure is reject by MME. A unregistered USIM could be the main reason , in this case , you can see error code EMM 129. Another familiar case is something wrong with the Cell which CPE is trying to attach , the error code is EMM 138. EMS cause 3GPP TS 24.301 Annex B. Could refer to Annex B (it is copied from 3GPP TS24.301) 2PDN Active PDN Active failure 5.2.LTE CPE Wireless Quality CPE LTE PM PM 4.2 fig 5-1 PM 3 PM 24 CPE User Manual Bad radio quality can cause the high drop rate , low data rate etc. We can get the radio quality of the environment by analysis PM log. You can refer to chapter 4.2 to get PM log, and as shown in fig 5-1 is a full cycle of PM logs. The following three chapter simply describe how to get KPI information through a full PM cycle. Fig 5-1 a full cycle of PM logs 5.2.1 CPE CPE Signal Strength fig 5-1 2 3 CINR,RSRP,RSSI CPE

[SCC]

Marked with 2 and 3 in the red area in fig5-1, we can see the values of CINR, RSRP and RSSI, in parentheses, there are two value meas CPE has two antennas, two values correspond to two antennas respectively, "[SCC]" meas secondary carrier , the various indicators of reference values as shown below:

CINR - CINR SINR CINR 17dB 17dB CINR - the CINR equivalent SINR, CINR needs more than 17 db, if less than 17 db, maybe lead to CPE UL/DL BLER rising, resulting in reduced the transmission efficiency, such as transmission is lowly or packet loss is .highly. RSRP - -95dBmRSRP

. RSRP - the recommended value is greater than -95dbm, RSRP is used to indicate the effective power of the eNodeB, and the relatively weak signals are bad for the transmission in air. So if the signal is below the expected value, please check the environment. 25 CPE User Manual

- make sure the antenna is aligned with the Cell

RSRP

- confirm there is no barrier between the device and Cell, especially no metal barrier. To ensure the device meet the RSRP requirements , adjusting the location is necessary sometimes .

- confirm a reasonable distance between the device and Cell, you can simply determine by a commercial mobile phone, if mobile phone works well at that place , it means the distance should be reasonable. RSSI - -75dBm -55dBm RSSI - the recommended value is -75dBm to -55dBm . RSRP RSSI 10%

5% 5.2.2 CPE Most of time ,RSRP and RSSI are often taken into analysis together , but it seems not a easy work, there is a simple way we can follow, analyze the BLER . UL BLER or DL BLER should not be occupied for a long time in the degree of the maximum value - 10%, our experiences show that antenna angle, distance , TX power of cell can take effect to the BLER . The recommended value of BLER less than 5%. You can refer to chapter 5.2.2 to analyze BLER.. 5.2.2 CPE CPE BLER fig 5-1 4 5 [SCC]

BLER HI BLER HI Label 4 and 5 in the red area in fig 3-1, you can get BLER information, "[SCC]"

meas secondary carrier, BLER shows download BLER, HI shows upload BLER. The BLER and HI formats are as follows:

BLER (P1 / P2, P3 / P4) HI (P5 / P6) BLER (P1 / P2, P3 / P4) HI (P5 / P6) P1: CW0 P1: the number of bad blocks on the CW0 channel 26 CPE User Manual P2: CW0 P2: the total number of blocks on the CW0 channel P3: CW1 P3: the number of bad blocks on the CW1 channel P4: CW1 P4: the total number of blocks on the CW1 channel P5:

P5: the number of bad blocks on the upload channel P6:

P6: the total number of blocks on the upload channel The calculation of DL BLER and UL BLER as follows:

: (P1 + P3)/(P2 + P4) * 100%

DL BLER: (P1 + P3)/(P2 + P4) * 100%

P5 / P6 * 100%

UL BLER: P5 / P6 * 100%

RI MINO RI 1 single fig 5-1 6 Label 6 in the red area in fig 3-1, you can count the traffic flows of different layers, and the 5.2.3 CPE RI 5.2.4 CPE CPE Throughput log format is as follows:

PHY/MAC/RLC/PDCP/IPC(P1,P2) PHY/MAC/RLC/PDCP/IPC(P1,P2) P1 P1download throughput P2 P2upload throughput 5.2.5 CPE CPE 27 CPE User Manual environmentthroughput BLER 6 1 3 Web page in CPE supports LTE signal related parameters for connection quality analysis. They can be found from Status/Environment, Throughput, and BLER 28 CPE User Manual 5.3.LTE LTE signaling 5.3.1 NAS NAS signaling info CPE NAS LM> TYPE:

NAS fig 5-2 info NAS In the info log , the NAS signaling of CPE is placed, according to the keywords "LM >

TYPE:" to you can retrieve the NAS signaling, figure 5-2 is the NAS signaling retrieved from Info log:

NAS FAIL REJECT info info log debug When negative keyword (such as FAIL, REJECT, etc.) presents in the log , you will need to Fig 5-2 NAS signaling 29 CPE User Manual analyze the signaling in the context of the issue point to find out the cause of the exception, if the info log is not sufficient to find out the cause of the exception occurs, will need to set log to debug level. RRC The RRC signaling mainly has the following procedures:

1Attach The Attach process EMM_ATTACH_REQUEST EMM_ATTACH_ACCEPT EMM_ATTACH_COMPLETE EMM_ATTACH_REJECT 2 Business request process EMM_SERVICE_REQUEST EMM_SERVICE_REJECT 5.3.2 RRC RRC signaling info CPE RRC LM> message c1 :

RRC fig 5-3 info RRC In the info log can see RRC signaling of CPE, you can according to the keywords "LM >

message c1:" to retrieve the RRC signaling, figure 5-3 is the part RRC signaling retrieved from info log Fig 5-3 RRC signaling RRC fail reject info info log debug When see anomalies in RRC signaling (such as fail, reject, etc.), you will need to analyze the signaling in the context of the problem point to find out the cause of the exception, if the info log is not sufficient to find out the cause of the exception occurs, you will need to set log to debug level. 30 CPE User Manual RRC The RRC signaling mainly has the following procedures:

1RRC RRC Establishment Process rrcConnectionRequest rrcConnectionSetup rrcConnectionSetupComplete 2RRC RRC Reconfiguration Process rrcConnectionReconfiguration rrcConnectionReconfigurationComplete 3RRC RRC Reestablishment Process rrcConnectionReestablishmentRequest rrcConnectionReestablishment rrcConnectionReestablishmentComplete rrcConnectionReestablishmentReject 31 CPE User Manual Advanced Management 6. Test 6.1.iperf iperf download test 1PC dhcp IP 10.10.2.10 IP The PC gets the IP via DHCP (assuming the IP is 10.10.2.10). 2telnet/console 10.10.2.254 Telnet to 10.10.2.254. 3 iptables -t nat -I PREROUTING -i lte0pdn0 ! -p icmp -j DNAT --to 10.10.2.10 Perform iptables -t nat -I PREROUTING -i lte0pdn0 ! -p icmp -j DNAT --to 10.10.2.10. 4 iptables -A FORWARD -d 10.10.2.10 -j ACCEPT Perform iptables -A FORWARD -d 10.10.2.10 -j ACCEPT. 5 PC iperf -s -u -i 1 iperf UDP server Run the iperf-s-u-i 1 (iperf UDP server) on the PC. 6SSH PGW iperf -c 192.168.200.2 -u -b 100M -i 1 -t 9999 (192.168.200.2 lte0pdn0 IP 10.10.2.254 ifconfig ) SSH to the PGW and run the iperf-c 192.168.200.2-u-b 100M - I 1-t 9999 (IP on lte0pdn0, available on 10.10.2.254);

1. SSL test 1.1 cpe femto Femto HeMscpe IP: 11.11.111.18femto IP: 11.11.111.17 1.1.1 SSL CML Agent Get Parameter 32 CPE User Manual femto femto_cli TestMethod Test Result IMEI femto_cli get Device.X_SCM_CPE.Status.Hardware.IMEI TestMethod 1. ID configuration 2. Device Method GetParameterValues Device.X_SCM_CPE.Status.Hardware.IMEI GetParameterValues value Test Result IMEI value Get_permission -> get_datatype -> get_attr -> get Set Parameter femto femto_cli Method 1 Test Result femto_cli set Device.X_SCM_CPE.Status.Hardware.IMEI=aaaa IMEI set writable check -> TR069_set femto_cli set cpe permission 5 femto_cli sset cpe Method 2 1. ID, configuration 2. Device Method SetParameterValues edit value Device.X_SCM_CPE.ModuleConfigMgmt.PLMN.SecEARFCN.4.SecondaryEARFCN SetParameterValues Test Result set Get_permission(permission 5 ) -> get_attr -> get(

set) -> TR069_set ValueChange TestMethod 1.cmld_client set Device.X_SCm_CPE.Status.UpgradeState=1 2. ID configuration 3. Alarm -> Device Current Alarm alarm Test Result Device Current Alarm 20007 Traversing the tree Download Datamodel GetParameterNames Method 1 Device Method Download Datamodel -> confirm Method 2 Device Method GetParameterNames paramter path Device. GetParameterNames Test Result download success 33 CPE User Manual 1.1.2 SSL File Agent Download/Upload Config Upload Config to Femto TestMethod 1. ID configuration 2. Device Method Upload CFG File Upload, refresh Test Result configuration file device id Download Config to CPE TestMethod 1. ID configuration 2. Device Method Device Upgrade file type configuration file restore upgrade restore Restore config Test Result Upload log cpe cpe valuechange valuechange femto femto HeMs HeMs HeMs cpe valuechange get HeMs cpe log 1. ID configuration 2. Device Method Upload Log File Upload now refresh start periocdic Cmld_client set Device.X_SCM_CPE.ActionMgmt.LogFull=1 Cpe logfull Test Result Log_XXX_cpe_XXX.zip FW Upgrade get HeMs cpe log 1. ID configuration 2. Device Method Device Upgrade file type upgrade file MultiPkg( single cpe fw) Upgrade Test Result 1.2 cpe ssl /tmp/ftp cmld_client, cmld, libcml_api.so, (cml ) act_mod, valuechange ssl_agent, ssl_test, libscm_ssl.so ssl_agent ssl start_ssl.sh LD_LIBRARY_PATH=. ./cmld /tmp/nv/nvram.xml &

LD_LIBRARY_PATH=. ./act_mod &

LD_LIBRARY_PATH=. ./ssl_agent -f /etc/.ssl_certs/ca.cert -s /etc/.ssl_certs/server.cert

-k /etc/.ssl_certs/server.key -c /etc/.ssl_certs/client.cert -l /etc/.ssl_certs/client.key -m -g -d 34 CPE User Manual 127.0.0.1 -p 8888 &

cmld act_mod ssl_agent client server -c -l ssl ssl 16:40:57 I SSLAGNT> Conection from 127.0.0.1:dbae 16:40:58 D SSLAGNT> Peer Info: /C=CN/ST=JiangSu/O=Sercomm/OU=Sercomm/CN=Client 16:40:58 D SSLAGNT> Peer Info: /C=CN/ST=JiangSu/O=Sercomm/OU=Sercomm/CN=Server 16:40:58DSSLAGNT>Peer Issuer:/C=CN/ST=JiangSu/L=SuZhou/O=Sercomm/OU=Sercomm/CN=CA 16:40:58 I SSLAGNT> Conected to server 127.0.0.1:22b8, after 0times 16:40:58DSSLAGNT>Peer Issuer:/C=CN/ST=JiangSu/L=SuZhou/O=Sercomm/OU=Sercomm/CN=CA wireshark ssl 1.2.1 SSL CML Agent Get Parameter TestMethod Test Result IMEI Set Parameter TestMethod Test Result IMEI aaa ValueChange 1.2.2 SSL File Agent ssl_test help:

cmld_client get Device.X_SCM_CPE.Status.Hardware.IMEI -s cmld_client set Device.X_SCM_CPE.Status.Hardware.IMEI=aaa -s TestMethod Test Result 20007(FW upgrade failure) ssl peer cmld_client set Device.X_SCm_CPE.Status.UpgradeState=1 -s Fw Upgrade TestMethod

./ssl_test -d 127.0.0.1 -a /etc/.ssl_certs/ca.cert

-c /etc/.ssl_certs/client.cert -l /etc/.ssl_certs/client.key

-f /tmp/ftp/*.bin -e 0 tail -f /var/cgitest Test Result Download Config to CPE TestMethod

./ssl_test -d 127.0.0.1 -a /etc/.ssl_certs/ca.cert 35 CPE User Manual

-c /etc/.ssl_certs/client.cert -l /etc/.ssl_certs/client.key

-f /tmp/ftp/cpe_cfg.zip -e 2 Test Result /tmp/ftp cpe_cfg.zip Upload Config to Femto TestMethod

./ssl_test -d 127.0.0.1 -a /etc/.ssl_certs/ca.cert

-c /etc/.ssl_certs/client.cert -l /etc/.ssl_certs/client.key

-f /tmp/ftp/cpe_cfg.zip -e 1 Test Result /tmp/ftp cpe_cfg.zip Upload log TestMethod LD_LIBRARY_PATH=. ./ssl_test -d 127.0.0.1 -a /etc/.ssl_certs/ca.cert

-c /etc/.ssl_certs/client.cert -l /etc/.ssl_certs/client.key

-f /tmp/ftp/log.zip -e 3 Test Result /tmp/ftp log.zip 2. SAS Test 2.1. FW SAS FW 3.1 CPE 2.5 SAS 2.7 SAS 2.2. SSH protocol:

SSH2 Hostname: 10.10.2.254 username: root password: sercomm.cd1 2.3. SAS 2.4. sasd log SAS Server SAS SAS SAS sasd log GUI log 4.2. CPE sasd log SAS tail -f /var/log/messages | grep sas -i 2.5. sasd log SAS 2.6. SAS 36 SAS GUI CPE User Manual GUI 2.7 SAS cmld_client 2.4.1. sasd sasd cmld_client show | grep 'sas' -i 2.4.2. SAS /SAS IoT a) sasd Register State cmld_client set Device.X_SCM_CPE.SAS.Registered=0 cmld_client set Device.X_SCM_CPE.SAS.State="Unknown"

b) eirpCapability MaxTxPower :

cmld_client set Device.X_SCM_CPE.ModuleConfigMgmt.MaxTxPower=20 37 CPE User Manual 38 CPE User Manual Appendix APLMN Search Appendix A: PLMN Search Result Result Cause LAPI_PLMN_SELECT_RESULT_SUCCESS LAPI_PLMN_SELECT_RESULT_FAILURE LAPI_PLMN_SELECT_RESULT_ABORTED LAPI_PLMN_SELECT_RESULT_INVALID_USIM LAPI_PLMN_SELECT_RESULT_ALREADY_IN_PROGRESS LAPI_MISMATCH_FREQ_BAND LAPI_FREQ_LIST_NOT_EXIST LAPI_PLMN_BAND_INVALID_PARAMETER Display String Success NoNetwork InternalError InvalidUSIM InProgress FreqBandMisatch FreqListNotFind FreqError 0 1 2 3 4 5 6 7 39 CPE User Manual BATTACH Response Appendix B: ATTACH Response Result regResult regResultOrg 0 : LAPI_REG_RESULT_SUCCESS 0 :LAPI_REG_RESULT_SUCCESS Success 1:ATT_FAIL_SERVICE_NOT_ALLOWED_U NTIL_POWER_CYCLE_OR_UICC_REPLACE 3: Illegal UE 6: Illegal ME 7: EPS services not allowed e3GPP EMM Cause:

ServiceLimit-NeedCycl 8: EPS services and non-EPS services not allowed 2:ATT_FAIL_SERVICE_NOT_ALLOWED_C URRENT_PLMN 11: PLMN not allowed ServiceLimit3GPP 14: EPS services not allowed in EMM Cause:

3:ATT_FAIL_SERVICE_IS_LIMITED tracking area this PLMN 12: Tracking area not allowed 13: Roaming not allowed in this 15: No suitable cells in this tracking area ServiceLimit-Paramete rsMismatch3GPP EMM Cause:

4: ATT_FAIL_AUTO_RETRY_AFTER_T3402 When the attach attempt counter is equal to 5. T3402Timeout3GPP EMMCause151 5:ATT_FAIL_OTHERS All of other cases Others3GPP EMM Cause:

40 CPE User Manual CCMEError Appendix C: CMEError Refer to 3GPP 24.007:section9.2 Numeric Text 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 18 20 21 22 23 24 25 26 27 30 31 32 40 41 42 43 44 45 46 47 48 phone failure no connection to phone phone-adaptor link reserved peration not allowed operation not supported PH-SIM PIN required PH-FSIM PIN required PH-FSIM PUK required SIM not inserted (See NOTE 1) SIM PIN required SIM PUK required SIM failure (See NOTE 1) SIM busy (See NOTE 1) SIM wrong (See NOTE 1) incorrect password SIM PIN2 required SIM PUK2 required memory full invalid index not found memory failure text string too long invalid characters in text string dial string too long invalid characters in dial string no network service network timeout network not allowed - emergency calls only network personalization PIN required network personalization PUK required network subset personalization PIN required network subset personalization PUK required service provider personalization PIN required service provider personalization PUK required corporate personalization PIN required corporate personalization PUK required hidden key required (See NOTE 2) 41 EAP method not supported Incorrect parameters command implemented but currently disabled command aborted by user not attached to network due to MT functionality restrictions modem not allowed - MT restricted to emergency calls only operation not allowed because of MT functionality restrictions fixed dial number only allowed - called number is not a fixed dial number (refer CPE User Manual unknown temporarily out of service due to other MT usage language/alphabet not supported unexpected data value system failure data missing call barred message waiting indication subscription failure 49 50 51 52 53 54 55 56 3GPP TS 22.101 [147]) 57 58 59 60 61 62 63 100 103 illegal MS 106 illegal ME 107 GPRS not allowed 111 PLMN not allowed 112 location area not allowed 113 roaming not allowed in this location area 127 missing or unknown apn 132 service option not supported 133 request service option not subscribed 134 service option temporary out of order 148 unspecified GPRS error 149 PDP authentication fail 150 invalid mobile class 171 last PDN disconnection not allowed 240 PLMN search already progress 241 EPS service not allowed 242 EPS service and non EPS service not allowed 243 APN verification fail 244 Network reject 245 already in progress NOTE 1: This error code is also applicable to UICC. NOTE 2: This key is required when accessing hidden phonebook entries. 42 CPE User Manual DESM Cause Appendix D: ESM Cause 43 CPE User Manual EEMM Cause Result Cause 8 22 23 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 49 50 51 52 53 54 55 56 59 60 81 95 96 97 98 99 100 101 111 112 ESM_OPERATOR_DETERMINED_BARRING ESM_INSUFFICIENT_RESOURCES ESM_UNKNOWN_OR_MISSING_APN ESM_UNKNOWN_PDN_TYPE ESM_USER_AUTHENTICATION_FAILED ESM_REQUEST_REJECTED_BY_SGWORPGW ESM_REQUEST_REJECTED_UNSPECIFIED ESM_SERVICE_OPTION_NOT_SUPPORTED ESM_REQUESTED_SERVICE_OPTION_NOT_SUBSCRIBED ESM_SERVICE_OPTION_TEMPORARILY_OUT_OF_ORDER ESM_PTI_ALREADY_IN_USE ESM_REGULAR_DEACTIVATION ESM_EPS_QOS_NOT_ACCEPTED ESM_NETWORK_FAILURE ESM_REACTIVATION_REQ ESM_FEATURE_NOT_SUPPORTED ESM_SEMANTIC_ERROR_IN_TFT_OPERATION ESM_SYNTACTICAL_ERROR_IN_TFT_OPERATION ESM_INVALID_EPS_BEARER_ID ESM_SEMANTIC_ERROR_IN_PACKET_FILTERS ESM_SYNTACTICAL_ERRORS_IN_PACKET_FILTERS ESM_EPS_BEARER_WITHOUT_TFT_ALREADY_ACTIVATED ESM_PTI_MISMATCH ESM_LAST_PDN_DISCONNECTION_NOT_ALLOWED ESM_PDN_TYPE_IPV4_ONLY_ALLOWED ESM_PDN_TYPE_IPV6_ONLY_ALLOWED ESM_SINGLE_ADDRESS_BEARERS_ONLY_ALLOWED ESM_ESM_INFORMATION_NOT_RECEIVED ESM_PDN_CONNECTION_DOES_NOT_EXIST ESM_MULTIPLE_PDN_CONNECTIONS_FOR_A_GIVEN_APN_NOT_ALLOWED ESM_COLLISION_WITH_NETWORK_INITIATED_REQUEST ESM_UNSUPPORTED_QCI_VALUE ESM_BEARER_HANDLING_NOT_SUPPORTED ESM_INVALID_PTI_VALUE ESM_SEMANTICALLY_INCORRECT_MESSAGE ESM_INVALID_MANDATORY_INFORMATION ESM_MESSAGE_TYPE_NON_EXISTENT_OR_NOT_INPLEMENTED ESM_MESSAGE_TYPE_NOT_COMPATIBLE_WITH_THE_PROTOCOL_STATE ESM_INFORMATION_ELEMENT_NON_EXISTENT_OR_NOT_IMPLEMENTED ESM_CONDITIOINAL_IE_ERROR ESM_MESSAGE_NOT_COMPATIBLE_WITH_THE_PROTOCOL_STATE 44 ESM_PROTOCOL_ERROR_UNSPECIFIED ESM_APN_RESTRICTION_VALUE_INCOMPATIBLE_WITH_ACTIVE_EPS_BEARER_C ONTEXT CPE User Manual Appendix E: EMM Cause Original REGISTRATION RESULT 0 : LAPI_REG_RESULT_SUCCESS

/* 3GPP EMM Cause \*/

2 : LAPI_REG_RESULT_REJECT_2_IMSI_UNKNOWN_IN_HSS 3 : LAPI_REG_RESULT_REJECT_3_ILLEGAL_UE 5: LAPI_REG_RESULT_REJECT_5_IMEI_NOT_ACCEPTED 6 : LAPI_REG_RESULT_REJECT_6_ILLEGAL_ME 7 :LAPI_REG_RESULT_REJECT_7_EPS_SERVICES_NOT_ALLOWED 8 :LAPI_REG_RESULT_REJECT_8_EPS_AND_NON_EPS_SERVICES_NOT_ALLOWED 9 : LAPI_REG_RESULT_REJECT_9_UE_ID_CANNOT_BE_DERIVED 10 : LAPI_REG_RESULT_REJECT_10_IMPLICITLY_DETACHED 11 : LAPI_REG_RESULT_REJECT_11_PLMN_NOT_ALLOWED 12 : LAPI_REG_RESULT_REJECT_12_TA_NOT_ALLOWED 13 :LAPI_REG_RESULT_REJECT_13_ROAMING_NOT_ALLOWED_IN_THIS_TA 14 :LAPI_REG_RESULT_REJECT_14_EPS_SERVICES_NOT_ALLOWED_IN_THIS_PLMN 15 :LAPI_REG_RESULT_REJECT_15_NO_SUITABLE_CELLS_IN_THIS_TA 16 :LAPI_REG_RESULT_REJECT_16_MSC_TEMPORARILY_NOT_REACHABLE 17 : LAPI_REG_RESULT_REJECT_17_NETWORK_FAILURE 18 :LAPI_REG_RESULT_REJECT_18_CS_DOMAIN_NOT_AVAILABLE 19 : LAPI_REG_RESULT_REJECT_19_ESM_FAILURE 20 : LAPI_REG_RESULT_REJECT_20_MAC_FAILURE 21 : LAPI_REG_RESULT_REJECT_21_SYNCH_FAILURE 22 : LAPI_REG_RESULT_REJECT_22_CONGESTION 23 :LAPI_REG_RESULT_REJECT_23_UE_SEC_CAPABILITIES_MISMATCH 24 :LAPI_REG_RESULT_REJECT_24_SECURITY_MODE_REJECTED_UNSPECIFIED 25 :LAPI_REG_RESULT_REJECT_25_NOT_AUTHORIZED_FOR_THIS_CSG 26 :LAPI_REG_RESULT_REJECT_26_NON_EPS_AUTHENTICATION_UNACCEPTABLE 39 :LAPI_REG_RESULT_REJECT_39_CS_DOMAIN_TEMPORARILY_NOT_AVAILABLE 40 :LAPI_REG_RESULT_REJECT_40_NO_EPS_BEARER_CONTEXT 95 :LAPI_REG_RESULT_REJECT_95_SEMANTICALLY_INCORRECT_MESSAGE 96 :LAPI_REG_RESULT_REJECT_96_INVALID_MANDATORY_INFORMATION 97 :LAPI_REG_RESULT_REJECT_97_MESSAGE_TYPE_NON_EXISTENT_OR_NOT_IMPLEMEN 98 :LAPI_REG_RESULT_REJECT_98_MESSAGE_TYPE_NOT_COMPATIBLE_WITH_PROTOCO 99 :LAPI_REG_RESULT_REJECT_99_INFORMATION_ELEMENT_NON_EXISTENT_OR_NOT_I 100 : LAPI_REG_RESULT_REJECT_100_CONDITIONAL_IE_ERROR 101 :LAPI_REG_RESULT_REJECT_101_MESSAGE_NOT_COMPATIBLE_WITH_PROTOCOL_S TED L_STATE MPLEMENTED, TATE 111 :LAPI_REG_RESULT_REJECT_111_PROTOCOL_ERROR_UNSPECIFIED 45 CPE User Manual

/* defined registration cause */

128 : LAPI_REG_RESULT_FAILURE_NO_USIM 129 : LAPI_REG_RESULT_FAILURE_INVALID_USIM 130 :LAPI_REG_RESULT_FAILURE_NETWORK_INIT_DETACH_TRIGGERED 131 :LAPI_REG_RESULT_FAILURE_DEFALULT_BEARER_SETUP_FAILURE 132 : LAPI_REG_RESULT_FAILURE_MAX_ATTACH_ATTEPT 133 : LAPI_REG_RESULT_ATTACH_IS_ALREADY_IN_PROGRESS 134 :LAPI_REG_RESULT_FAILURE_PDNCONNECT_APN_VERIFICATION_FAIL 137 :LAPI_REG_RESULT_FAILURE_START_USIM_REFRESH_MODE_4_5_6 138 : LAPI_REG_RESULT_FAILURE_LOWER_LAYER_FAIL 139 :LAPI_REG_RESULT_FAILURE_UE_INIT_DETACH_TRIGGERED 140 : LAPI_REG_RESULT_FAILURE_P_CSCF_MISSING 141 : LAPI_REG_RESULT_FAILURE_T3402_RUNNING 142: LAPI_REG_RESULT_FAILURE_MO_DATA_BARRING 143:LAPI_REG_RESULT_FAILURE_NOT_ALLOW_LIMITED_IMS_EMERGENCY 144: LAPI_REG_RESULT_LIMITED_SERVICE_ONLY 256 : LAPI_REG_RESULT_NO_AVAILABLE_CELL 150LAPI_REG_RESULT_T3410_Timeout 151LAPI_REG_RESULT_T3420_Timeout 152LAPI_REG_RESULT_T3430_Timeout 153LAPI_REG_RESULT_T3418_Timeout 154LAPI_REG_RESULT_T3417_Timeout 155LAPI_REG_RESULT_T3411_Timeout 156LAPI_REG_IMS_NI_DEREG_IND 157LAPI_REG_RESULT_T3442_Timeout 0xFFFF:LAPI_REG_RESULT_OTHER_FAILURE 46 Federal Communication Commission Interference Statement This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. Radiation Exposure Statement:

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 47cm between the radiator & your body. Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Professional installation instruction 1. Installation personal This product is designed for specific application and needs to be installed by a qualified personal who has RF and related rule knowledge. The general user shall not attempt to install or change the setting. 2. Installation location The product shall be installed at a location where the radiating antenna can be kept 47cm from nearby person in normal operation condition to meet regulatory RF exposure requirement. 3. Installation procedure Please refer to users manual for the detail. 4. Warning Please carefully select the installation position and make sure that the final output power does not exceed the limit set force in relevant rules. The violation of the rule could lead to serious federal penalty.

Sercomm Corporation Taipei Office: 8F, No.3-1, YuanQu St., NanKang, Taipei 115, Taiwan, R.O.C. TEL: 886-2-2655-3988 FAX: 886-2-2655-3966 Date: 2019-12-04 FCC ID: P27GEN3505A To whom it may concern:

AUTHORIZATION LETTER We, the undersigned, hereby authorize Andrea Hsia/ Supervisor of Bureau Veritas Consumer Products Services (H.K.) Ltd., Taoyuan Branch (BV CPS Taoyuan) of Taiwan to act on our behalf in all manners relating to FCC application for equipment authorization, including signing of all documents relating to these matters. Any and all acts carried out by Andrea Hsia/ Supervisor of BV CPS Taoyuan on our behalf shall have the same effect as acts of our own. If you have any questions regarding the authorization, please dont hesitate to contact us. Sincerely yours,

Sercomm Corporation Nick Wu / Engineer TEL: 886-2-2655-3988*2556 FAX: 886-2-2655-3965 E-mail: nick_wu@sercomm.com

Sercomm Corporation Taipei Office: 8F, No.3-1, YuanQu St., NanKang, Taipei 115, Taiwan, R.O.C. TEL: 886-2-2655-3988 FAX: 886-2-2655-3966 Professional Installation Attestation Date: 2019-12-12 FCC ID: P27GEN3505A To Whom It May Concern:

Please be advised that due to the unique Market and function targeted by this product, this product will need special trained professional in configuring and installing the product. We hereby declare that the product will be distributed through controlled distribution channel which has special trained professional to install this product and will not be sold directly to the general public through retail store. Thank you for your attention. Sincerely yours,

Sercomm Corporation Nick Wu/ Engineer TEL: 886-2-2655-3988*2556 FAX: 886-2-2655-3965 E-mail: Nick_wu@sercomm.com

Sercomm Corporation Taipei Office: 8F, No.3-1, YuanQu St., NanKang, Taipei 115, Taiwan, R.O.C. TEL: 886-2-2655-3988 FAX: 886-2-2655-3966 Date: 2019-12-04 FCC ID: P27GEN3505A To the attention of Federal Communications Commission Authorization and Evaluation Division Confidentiality Request Pursuant to Sections 0.457 and 0.459 of the Commissions Rules, the Applicant hereby requests confidential treatment of information accompanying this Application as outlined below:

Schematics Block Diagram Operational Description Part list Tune-up Procedure The above materials contain trade secrets and proprietary information not customarily released to the public. The public disclosure of these matters might be harmful to the Applicant and provide unjustified benefits to its competitors. The Applicant understands that pursuant to Rule 0.457, disclosure of this Application and all accompanying documentation will not be made before the date of the Grant for this application. Sincerely yours,

Sercomm Corporation Nick Wu / Engineer TEL: 886-2-2655-3988*2556 FAX: 886-2-2655-3965 E-mail: nick_wu@sercomm.com

Sercomm Corporation Taipei Office: 8F, No.3-1, YuanQu St., NanKang, Taipei 115, Taiwan, R.O.C. TEL: 886-2-2655-3988 FAX: 886-2-2655-3966 Date: 2019-12-13 FCC ID: P27GEN3505A To the attention of Federal Communications Commission Authorization and Evaluation Division Confidentiality Request Pursuant to Sections 0.457 and 0.459 of the commissions rules, we request short-term confidential treatment for the following information until 180 days after the Grant Date of Equipment Authorization in order to ensure sensitive business information remains confidential until the actual marketing of the device:

External photos Test Setup photos Users manual Internal Photos Sincerely yours,

Sercomm Corporation Nick Wu / Engineer TEL: 886-2-2655-3988*2632 FAX: 886-2-2655-3965 E-mail: nick_wu@sercomm.com