Baicells Configuration Network Admin Guide Srv1.26 28-Feb-2020

Configuration & Network
Administration Guide
February 2020
Version 1.26
About This Document
This document describes the mainstream applications used for configuring and administering the Baicells
network components and subscribers. The scope of information includes the standard single carrier eNodeB
(eNB) GUI, the user equipment (UE) GUI, and the Baicells CloudCore Operations Management Console (OMC)
and Business Operations & Support System (BOSS). The target audience is network administrators who are
responsible for configuring, monitoring, troubleshooting, and upgrading Baicells eNBs and UEs; configuring
network interfaces; adding subscribers; and creating service plans.
Separate documents are available for specific use cases or to focus on particular deployment scenarios:
• HaloB User Guide
• Carrier Aggregation & Dual Carrier Configuration Guide
• SAS Deployment Guide
• Spectra LTE-U
• Local OMC+BOSS
• Local Evolved Packet Core (EPC)
This publication of the guide is written to the following Baicells software versions:
• eNB versions:
o Nova-227/233/243: BaiBS_RTS_3.4.8 (focus)
o Nova-436Q: BaiBS_QRTB_2.0.5 (differences from RTS only)
• Cat4 UE version: BaiCE_AP_2.2.1_NA
• Cat6/7 UE differences: BCE_MD-1.0.1-B036SP28-NA (Appendix A)
• CloudCore OMC version: 5.2.7
• CloudCore BOSS version: 5.2.5
Copyright Notice
Baicells Technologies, Inc., copyrights the information in this document. No part of this document may be
reproduced in any form or means without the prior written consent of Baicells Technologies, Inc. The Baicells
logo is a proprietary trademark of Baicells Technologies, Inc. Other trademarks mentioned in this document
belong to their owners.
Disclaimer
All products, services, and features bought from Baicells Technologies, Inc., are subject to the constraints of the
company's business contract and terms. All or part of the products, services, or features described in this
document might not be your specific Baicells network. Unless stated in the contract, Baicells Technologies, Inc.,
does not make any explicit or default statement or guarantee about the contents of this document.
Unless stated otherwise, this document serves only as a user guide, and all descriptions / information /
suggestions mean no guarantee, neither explicit nor implicit.
The information in this document is subject to change at any time without notice. For more information, please
consult with a Baicells technical engineer or the support team. Refer to the Contact Us section.
ii
Revision Record
Date Version Description SMEs/Contributors Author/Editor
28-Feb-2020 V1.26 New logo & colors Chris Culver Sharon Redfoot
21-Feb-2020 V1.25 Added further info on Nova-436Q DC, SAS Nitisha Potti, Jesse Raasch
2-JAN-2020 V1.24 SME comments Nitisha Potti Sharon Redfoot
17-Dec-2019 V1.23 Updated for RTS 3.4.8, OMC 5.2.7 Jesse Raasch, Nitisha Potti, Jie Lewis,
19-Nov-2019 V1.22 SME comments from Dandan WuJunfeng, Zhang Dandan, Sonny
14-Nov-2019 V1.21 Updated for RTS 3.4.5 (HaloB, Standard, SAS), QRTB May, LiuGuidong
2.0.4 (HaloB, CA, DC, SAS), OMC 5.2.4, BOSS autopay,
and new PLMN for Baicells NA CloudCore
Support Resources
• Documentation - Baicells product data sheets and technical manuals may be found at Baicells >
Resources > Documentation.
• Support - Open a support ticket, process an RMA, and the Support Forum are at Baicells > Support.
Contact Us
Baicells Technologies Co., Ltd. Baicells Technologies North America, Inc.
CHINA NORTH AMERICA
Address 3F, Bldg. A, No. 1 Kai Tuo Rd, Haidian Dist, 555 Republic Dr., #200, Plano, TX 75074, USA
Beijing, China
Phone Phone: +86-10-62607100 Phone: +1-888-502-5585
Email E-mail: contact@Baicells.com Email: sales_na@Baicells.com or support_na@Baicells.com
Website Website: www.Baicells.com Website: https://na.Baicells.com
iii
Table of Contents
1 INTRODUCTION ....................................................................................................................................................... 1
2 ENB GUI ................................................................................................................................................................... 2
2.1 COMPUTER REQUIREMENTS ...........................................................................................................................................2
2.2 LAUNCHING THE GUI ...................................................................................................................................................3
2.3 CONFIGURATION FLOW .................................................................................................................................................4
2.4 BTS INFO ...................................................................................................................................................................4
2.4.1 Basic Info ............................................................................................................................................................4
2.4.2 Quick Setting ......................................................................................................................................................7
2.5 SYSTEM .....................................................................................................................................................................9
2.5.1 NTP ...................................................................................................................................................................10
2.5.2 Upgrade ............................................................................................................................................................11
2.5.3 Backup ..............................................................................................................................................................12
2.5.4 Password ..........................................................................................................................................................13
2.5.5 Web ..................................................................................................................................................................13
2.5.6 CertStore ...........................................................................................................................................................13
2.6 NETWORK ................................................................................................................................................................14
2.6.1 WAN/LAN .........................................................................................................................................................15
2.6.2 DHCP .................................................................................................................................................................17
2.6.3 MME&IPSec Binding .........................................................................................................................................17
2.6.4 LGW ..................................................................................................................................................................21
2.6.5 Diagnostics .......................................................................................................................................................22
2.6.6 Static Routing ...................................................................................................................................................23
2.7 BTS SETTING ............................................................................................................................................................23
2.7.1 Security Setting .................................................................................................................................................24
2.7.2 Management Server .........................................................................................................................................24
2.7.3 Sync Setting ......................................................................................................................................................25
2.7.4 HaloB Setting ....................................................................................................................................................26
2.7.5 License Management .......................................................................................................................................27
2.7.6 Carrier Setting (Nova-436Q only) .....................................................................................................................27
2.8 LTE .........................................................................................................................................................................28
2.8.1 Identify Neighbor Frequencies & Cell Information............................................................................................29
2.8.2 LTE Freq/Cell .....................................................................................................................................................29
2.8.3 TD-S Freq/Cell ...................................................................................................................................................31
2.8.4 GSM Freq/Cell ...................................................................................................................................................34
2.8.5 Mobility Parameter...........................................................................................................................................36
2.8.6 Advanced ..........................................................................................................................................................41
2.8.7 Real-World LTE to LTE Handoff Configuration Example ....................................................................................58
2.8.8 SAS Settings ......................................................................................................................................................61
2.8.9 Spectrum Analyzer ............................................................................................................................................63
2.8.10 UL PRB RSSI Report.......................................................................................................................................65
2.9 REBOOT ...................................................................................................................................................................67
2.10 LOGOUT...................................................................................................................................................................67
iv
3 UE GUI ................................................................................................................................................................... 68
3.1 COMPUTER REQUIREMENTS .........................................................................................................................................68
3.2 LAUNCHING THE GUI .................................................................................................................................................68
3.3 STATUS ....................................................................................................................................................................70
3.3.1 Overview ...........................................................................................................................................................70
3.3.2 Routes ...............................................................................................................................................................73
3.4 NETWORK ................................................................................................................................................................74
3.4.1 LAN Settings .....................................................................................................................................................75
3.4.2 WAN Settings ....................................................................................................................................................76
3.4.3 WLAN Settings (Indoor UE Model EG2030C only).............................................................................................78
3.4.4 Wifidog .............................................................................................................................................................80
3.4.5 Static Routes .....................................................................................................................................................81
3.4.6 DMZ ..................................................................................................................................................................82
3.5 LTE .........................................................................................................................................................................83
3.5.1 Connection Mode .............................................................................................................................................84
3.5.2 Scan Method.....................................................................................................................................................84
3.5.3 APN Management ............................................................................................................................................85
3.5.4 PIN Management .............................................................................................................................................86
3.6 SECURITY .................................................................................................................................................................88
3.6.1 Firewall Settings ...............................................................................................................................................88
3.6.2 MAC Filter .........................................................................................................................................................89
3.6.3 IP Filter..............................................................................................................................................................90
3.6.4 URL Filter ..........................................................................................................................................................91
3.6.5 Port Forwarding ................................................................................................................................................91
3.6.6 Port Triggering ..................................................................................................................................................92
3.6.7 ALG ...................................................................................................................................................................93
3.6.8 UPNP.................................................................................................................................................................94
3.6.9 Attack Protection ..............................................................................................................................................94
3.7 VPN .......................................................................................................................................................................95
3.7.1 IPSec .................................................................................................................................................................95
3.7.2 General VPN .....................................................................................................................................................98
3.7.3 L2 ....................................................................................................................................................................100
3.8 SYSTEM .................................................................................................................................................................101
3.8.1 NTP .................................................................................................................................................................101
3.8.2 Account ...........................................................................................................................................................102
3.8.3 WEB Setting ....................................................................................................................................................102
3.8.4 TR-069 ............................................................................................................................................................103
3.8.5 SNMP ..............................................................................................................................................................104
3.8.6 Restore/Update ..............................................................................................................................................105
3.8.7 Diagnosis ........................................................................................................................................................106
3.8.8 Reboot ............................................................................................................................................................108
3.9 LOGOUT.................................................................................................................................................................109
4 CLOUDCORE......................................................................................................................................................... 110
4.1 CLIENT COMPUTER REQUIREMENTS.............................................................................................................................110
4.2 GETTING STARTED....................................................................................................................................................110
4.2.1 Accessing CloudCore .......................................................................................................................................110
v
4.2.2 CloudCore Users .............................................................................................................................................112
4.2.3 Navigation Pane .............................................................................................................................................112
4.2.4 GUI Icons.........................................................................................................................................................113
4.2.5 Help ................................................................................................................................................................114
4.3 SYSTEM .................................................................................................................................................................114
4.3.1 Billing ..............................................................................................................................................................114
4.3.2 Invoice.............................................................................................................................................................117
4.3.3 Security ...........................................................................................................................................................119
4.3.4 Security Rule ...................................................................................................................................................120
4.3.5 Logs ................................................................................................................................................................121
4.4 OMC ....................................................................................................................................................................122
4.4.1 Dashboard ......................................................................................................................................................122
4.4.2 eNB .................................................................................................................................................................125
4.4.3 CPE ..................................................................................................................................................................141
4.4.4 Alarm ..............................................................................................................................................................153
4.4.5 Advance > SAS ................................................................................................................................................161
4.4.6 System ............................................................................................................................................................162
4.4.7 Help ................................................................................................................................................................167
4.5 BOSS ....................................................................................................................................................................168
4.5.1 Overview .........................................................................................................................................................168
4.5.2 Subscriber .......................................................................................................................................................169
4.5.3 Network ..........................................................................................................................................................181
4.5.4 System ............................................................................................................................................................185
4.5.5 Help ................................................................................................................................................................192
APPENDIX A: UE CAT6/7 GUI ........................................................................................................................................ 193
APPENDIX B: ABBREVIATIONS & ACRONYMS ............................................................................................................... 219
vi
List of Figures
FIGURE 1-1: STANDARD BAICELLS LTE NETWORK ................................................................................................................................1
FIGURE 2-1: INTERNET PROTOCOL VERSION (TCP/IPV4) .....................................................................................................................2
FIGURE 2-2: LOGIN .......................................................................................................................................................................3
FIGURE 2-3: HOME PAGE ...............................................................................................................................................................3
FIGURE 2-4: INITIAL ENB CONFIGURATION FLOW................................................................................................................................4
FIGURE 2-5: MESSAGE ...................................................................................................................................................................5
FIGURE 2-6: BASIC INFO.................................................................................................................................................................5
FIGURE 2-7: QUICK SETTING ...........................................................................................................................................................8
FIGURE 2-8: SYSTEM MENU..........................................................................................................................................................10
FIGURE 2-9: NTP .......................................................................................................................................................................10
FIGURE 2-10: UPGRADE...............................................................................................................................................................11
FIGURE 2-11: BACKUP .................................................................................................................................................................12
FIGURE 2-12: PASSWORD ............................................................................................................................................................13
FIGURE 2-13: WEB .....................................................................................................................................................................13
FIGURE 2-14: CERTSTORE ............................................................................................................................................................14
FIGURE 2-15: NETWORK MENU ....................................................................................................................................................14
FIGURE 2-16: WAN/LAN............................................................................................................................................................15
FIGURE 2-17: VLAN ...................................................................................................................................................................16
FIGURE 2-18:DHCP ...................................................................................................................................................................17
FIGURE 2-19: MME&IPSEC BINDING ............................................................................................................................................17
FIGURE 2-20: TUNNEL SETTING - BASIC SETTING TAB ........................................................................................................................18
FIGURE 2-21: TUNNEL SETTING - ADVANCE SETTING TAB ...................................................................................................................19
FIGURE 2-22: IPSEC BINDING .......................................................................................................................................................21
FIGURE 2-23: LGW SETTING (NAT, BRIDGE, & ROUTER MODES) ........................................................................................................22
FIGURE 2-24: DIAGNOSTICS ..........................................................................................................................................................22
FIGURE 2-25: STATIC ROUTING......................................................................................................................................................23
FIGURE 2-26: BTS SETTING MENU ................................................................................................................................................23
FIGURE 2-27: SECURITY SETTING ...................................................................................................................................................24
FIGURE 2-28: MANAGEMENT SERVER ............................................................................................................................................25
FIGURE 2-29: SYNC SETTING.........................................................................................................................................................25
FIGURE 2-30: 1588 SYNC (FUTURE FEATURE) ..................................................................................................................................26
FIGURE 2-31: HALOB SETTING ......................................................................................................................................................26
FIGURE 2-32: LICENSE MANAGEMENT ............................................................................................................................................27
FIGURE 2-33: CARRIER SETTING ....................................................................................................................................................28
FIGURE 2-34: LTE MENU .............................................................................................................................................................28
FIGURE 2-35: LTE FREQ/CELL .......................................................................................................................................................29
FIGURE 2-36: NEIGH FREQ TABLE ..................................................................................................................................................30
FIGURE 2-37: LTE NEIGH CELL TABLE SETTINGS ...............................................................................................................................31
FIGURE 2-38: TD-S FREQ/CELL .....................................................................................................................................................32
FIGURE 2-39: TD-S NEIGH FREQ TABLE SETTINGS ............................................................................................................................32
FIGURE 2-40: TD-S FREQ/CELL > NEIGH CELL TABLE SETTINGS...........................................................................................................33
FIGURE 2-41: GSM FREQ/CELL > NEIGH FREQ TABLE SETTINGS..........................................................................................................34
FIGURE 2-42: GSM FREQ/CELL > NEIGH FREQ TABLE SETTINGS..........................................................................................................34
vii
FIGURE 2-43: GSM FREQ/CELL > NEIGH CELL SETTINGS ...................................................................................................................35
FIGURE 2-44: HANDOFF...............................................................................................................................................................36
FIGURE 2-45: MOBILITY PARAMETERS ............................................................................................................................................37
FIGURE 2-46: A1, A2, A3, AND A5 EVENT THRESHOLDS ...................................................................................................................37
FIGURE 2-47: B2 EVENT THRESHOLD .............................................................................................................................................38
FIGURE 2-48: MEASUREMENT CONTROL PARAMETERS ......................................................................................................................39
FIGURE 2-49: CELL SELECTION AND CELL RESELECTION PARAMETERS ...................................................................................................40
FIGURE 2-50: ADVANCED .............................................................................................................................................................41
FIGURE 2-51: X2 PARAMETER.......................................................................................................................................................42
FIGURE 2-52: POWER CONTROL PARAMETERS .................................................................................................................................42
FIGURE 2-53: ENODEB SETTINGS ..................................................................................................................................................43
FIGURE 2-54: GAP SETTINGS .......................................................................................................................................................44
FIGURE 2-55: RRC STATUS PARAMETERS ........................................................................................................................................44
FIGURE 2-56: RADIO PARAMETERS ................................................................................................................................................44
FIGURE 2-57: SON FUNCTION SETTINGS ........................................................................................................................................45
FIGURE 2-58: TX AND RX SETTINGS................................................................................................................................................46
FIGURE 2-59: RANDOM ACCESS PARAMETERS..................................................................................................................................46
FIGURE 2-60: WORKING MODE ....................................................................................................................................................47
FIGURE 2-61: SCHEDULING ALGORITHM PARAMETERS .......................................................................................................................47
FIGURE 2-62: SYNC ADJUST PARAMETERS .......................................................................................................................................48
FIGURE 2-63: LINK ACTIVATION STATE DETECTOR..............................................................................................................................48
FIGURE 2-64: ICIC SETTINGS ........................................................................................................................................................49
FIGURE 2-65: SIGNALING TRACE ....................................................................................................................................................50
FIGURE 2-66: PROTOCOL SETTING .................................................................................................................................................51
FIGURE 2-67: DECODE AS ............................................................................................................................................................51
FIGURE 2-68: GET SCTP MESSAGE ................................................................................................................................................52
FIGURE 2-69: PROTOCOL SETTING .................................................................................................................................................52
FIGURE 2-70: DECODE AS ............................................................................................................................................................53
FIGURE 2-71: GET SCTP MESSAGE ................................................................................................................................................53
FIGURE 2-72: FILTER ...................................................................................................................................................................53
FIGURE 2-73: UE RNTI ...............................................................................................................................................................54
FIGURE 2-74: CELL ACCESS CONTROL .............................................................................................................................................54
FIGURE 2-75: INTERFERENCE DETECTION ........................................................................................................................................55
FIGURE 2-76: MULTI NETWORK ELEMENT .......................................................................................................................................56
FIGURE 2-77: SSH ......................................................................................................................................................................56
FIGURE 2-78: CELL BARRED INFO ...................................................................................................................................................57
FIGURE 2-79: LTE NEIGH FREQ AND NEIGH CELL ..............................................................................................................................58
FIGURE 2-80: A1 THRESHOLD .......................................................................................................................................................58
FIGURE 2-84: X2 ........................................................................................................................................................................59
FIGURE 2-85: FLOWCHART OF HANDOFF EVENT THRESHOLDS .............................................................................................................60
FIGURE 2-86: SAS ......................................................................................................................................................................61
FIGURE 2-87: SPECTRUM ANALYZER ...............................................................................................................................................63
FIGURE 2-88: EXAMPLES OF SPECTRUM SCANNING RESULTS ...............................................................................................................65
viii
FIGURE 2-89: LTE > UL PRB RSSI REPORT .....................................................................................................................................66
FIGURE 2-90: WITH INTERFERENCE ................................................................................................................................................66
FIGURE 2-91: REBOOT .................................................................................................................................................................67
FIGURE 2-92: LOGOUT ACTION .....................................................................................................................................................67
FIGURE 3-1: UE LAN INTERFACE EXAMPLE ......................................................................................................................................68
FIGURE 3-2: UE GUI LOGIN .........................................................................................................................................................69
FIGURE 3-3: UE GUI - MAIN MENU ..............................................................................................................................................69
FIGURE 3-4: CHANGE PASSWORD ..................................................................................................................................................70
FIGURE 3-5: OVERVIEW FIELDS / DASHBOARD (1 OF 2) .....................................................................................................................70
FIGURE 3-6: OVERVIEW FIELDS / DASHBOARD (2 OF 2) .....................................................................................................................71
FIGURE 3-7: ROUTES ...................................................................................................................................................................74
FIGURE 3-8: NETWORK SUB-MENUS ..............................................................................................................................................74
FIGURE 3-9: LAN SETTINGS ..........................................................................................................................................................75
FIGURE 3-10: NETWORK MODE ....................................................................................................................................................77
FIGURE 3-11: BRIDGE MODE ........................................................................................................................................................77
FIGURE 3-12: WIRELESS OVERVIEW ...............................................................................................................................................78
FIGURE 3-13: SSID SETTINGS .......................................................................................................................................................79
FIGURE 3-14: WIFIDOG ...............................................................................................................................................................80
FIGURE 3-15: WHITELIST .............................................................................................................................................................80
FIGURE 3-16: ADVANCED SETTINGS ...............................................................................................................................................81
FIGURE 3-17: STATIC ROUTES........................................................................................................................................................82
FIGURE 3-18: CONFIGURE STATIC ROUTES .......................................................................................................................................82
FIGURE 3-19: DMZ METHODS .....................................................................................................................................................83
FIGURE 3-20: DMZ ....................................................................................................................................................................83
FIGURE 3-21: LTE .......................................................................................................................................................................83
FIGURE 3-22: CONNECTION MODE ................................................................................................................................................84
FIGURE 3-23: SCAN METHOD .......................................................................................................................................................84
FIGURE 3-24: FREQUENCY LOCK ....................................................................................................................................................85
FIGURE 3-25: PCI LOCK ...............................................................................................................................................................85
FIGURE 3-26: APN MANAGEMENT ................................................................................................................................................86
FIGURE 3-27: PIN MANAGEMENT .................................................................................................................................................87
FIGURE 3-28: MODIFY PIN ..........................................................................................................................................................88
FIGURE 3-29: SECURITY ...............................................................................................................................................................88
FIGURE 3-30: FIREWALL SETTINGS .................................................................................................................................................89
FIGURE 3-31: MAC FILTER > ADD LIST ...........................................................................................................................................89
FIGURE 3-32: IP FILTER................................................................................................................................................................90
FIGURE 3-33: URL FILTER ............................................................................................................................................................91
FIGURE 3-34: PORT FORWARDING .................................................................................................................................................92
FIGURE 3-35: PORT TRIGGERING ...................................................................................................................................................93
FIGURE 3-36: ALG .....................................................................................................................................................................93
FIGURE 3-37: UPNP ...................................................................................................................................................................94
FIGURE 3-38: ATTACK PROTECTION ................................................................................................................................................95
FIGURE 3-39: VPN MENU ...........................................................................................................................................................95
FIGURE 3-40: VPN > IPSEC .........................................................................................................................................................96
FIGURE 3-41: ADVANCE SETTINGS ............................................................................................................................................97
FIGURE 3-42: GENERAL VPN > L2TP .............................................................................................................................................98
ix
FIGURE 3-43: GENERAL VPN > PPTP ............................................................................................................................................99
FIGURE 3-44: GENERAL VPN > GRE ..............................................................................................................................................99
FIGURE 3-45: SET UP L2............................................................................................................................................................100
FIGURE 3-46: APN STATUS ........................................................................................................................................................101
FIGURE 3-47: NTP ...................................................................................................................................................................101
FIGURE 3-48: ACCOUNT ............................................................................................................................................................102
FIGURE 3-49: WEB SETTING ......................................................................................................................................................102
FIGURE 3-50: TR-069...............................................................................................................................................................103
FIGURE 3-51: SNMP ................................................................................................................................................................104
FIGURE 3-52: RESTORE/UPDATE..................................................................................................................................................105
FIGURE 3-53: DIAGNOSIS ...........................................................................................................................................................106
FIGURE 3-54: PING ...................................................................................................................................................................106
FIGURE 3-55: TRACEROUTE ........................................................................................................................................................107
FIGURE 3-56: IPERF ..................................................................................................................................................................108
FIGURE 3-57: REBOOT ...............................................................................................................................................................109
FIGURE 3-58: LOGOUT ..............................................................................................................................................................109
FIGURE 4-1: CLOUDCORE SIGN UP AND LOGIN PAGE .......................................................................................................................111
FIGURE 4-2: SIGN UP FIELDS .......................................................................................................................................................111
FIGURE 4-3: NAVIGATION PANE ...................................................................................................................................................112
FIGURE 4-4: CLOUDCORE WELCOME MENU ..................................................................................................................................112
FIGURE 4-5: HELP > ABOUT ........................................................................................................................................................114
FIGURE 4-6: SYSTEM MENU........................................................................................................................................................114
FIGURE 4-7: BILLING MENU........................................................................................................................................................115
FIGURE 4-8: ADD CREDIT CARD ...................................................................................................................................................115
FIGURE 4-9: UPCOMING INVOICE.................................................................................................................................................116
FIGURE 4-10: INVOICES .............................................................................................................................................................116
FIGURE 4-11: USER COUNT ........................................................................................................................................................117
FIGURE 4-12: URL > STRIPE .......................................................................................................................................................117
FIGURE 4-13: INVOICE ...............................................................................................................................................................118
FIGURE 4-14: LIST TAB ..............................................................................................................................................................118
FIGURE 4-15: LIST TAB > OPERATIONS > DETAILS............................................................................................................................119
FIGURE 4-16: (ADMINISTRATIVE) USER .........................................................................................................................................119
FIGURE 4-17: RESET PASSWORD..................................................................................................................................................119
FIGURE 4-18: ADD ADMINISTRATIVE USER ....................................................................................................................................120
FIGURE 4-19: SECURITY RULE .....................................................................................................................................................121
FIGURE 4-20: LOGS...................................................................................................................................................................121
FIGURE 4-21: OMC MENUS ......................................................................................................................................................122
FIGURE 4-22: DISPLAY ...............................................................................................................................................................122
FIGURE 4-23: DASHBOARD - ALARM QUERY ..................................................................................................................................123
FIGURE 4-24: STATISTICS (1 OF 2) ................................................................................................................................................124
FIGURE 4-25: STATISTICS (2 OF 2) ................................................................................................................................................124
FIGURE 4-26: ENB MENU ..........................................................................................................................................................125
FIGURE 4-27: MONITOR ............................................................................................................................................................125
FIGURE 4-28: ACTIVE RATIO EXAMPLE ..........................................................................................................................................126
FIGURE 4-29: DISPLAY ...............................................................................................................................................................127
FIGURE 4-30: FILTER EXAMPLE ....................................................................................................................................................127
x
FIGURE 4-31: ADVANCED QUERY .................................................................................................................................................127
FIGURE 4-32: OPERATIONS .........................................................................................................................................................128
FIGURE 4-33: STATISTICS ............................................................................................................................................................128
FIGURE 4-34: STATUS INFO .........................................................................................................................................................128
FIGURE 4-35: ALARM ................................................................................................................................................................129
FIGURE 4-36: DETAIL.................................................................................................................................................................129
FIGURE 4-37: DEVICE REPORT LOG & DEVICE EXCEPTION LOG ..........................................................................................................130
FIGURE 4-38: LICENSE INFO ........................................................................................................................................................130
FIGURE 4-39: SETTINGS .............................................................................................................................................................131
FIGURE 4-40: MORE .................................................................................................................................................................131
FIGURE 4-41: LOGS...................................................................................................................................................................131
FIGURE 4-42: RESET PASSWORD (1 OF 3) .....................................................................................................................................132
FIGURE 4-45: MAINTENANCE .....................................................................................................................................................133
FIGURE 4-46: RESET PASSWORD..................................................................................................................................................133
FIGURE 4-47: CREATE REBOOT TASK ............................................................................................................................................134
FIGURE 4-48: LOG - ADD TASK....................................................................................................................................................134
FIGURE 4-49: OPERATIONS > VIEW (TASK RESULTS) - DEVICE REPORT LOG EXAMPLE ............................................................................135
FIGURE 4-50: SOFTWARE ROLLBACK.............................................................................................................................................136
FIGURE 4-51: OPERATIONS > VIEW (TASK RESULTS) - SOFTWARE ROLLBACK ........................................................................................136
FIGURE 4-52: REGISTER .............................................................................................................................................................137
FIGURE 4-53: VIEW DEVICE GROUP .............................................................................................................................................137
FIGURE 4-54: ADD NEW DEVICE GROUP .......................................................................................................................................137
FIGURE 4-55: ADD (REGISTER) ENB .............................................................................................................................................138
FIGURE 4-56: IMPORT/EXPORT ENB INFORMATION ........................................................................................................................138
FIGURE 4-57: LICENSE ...............................................................................................................................................................139
FIGURE 4-58: UPGRADE.............................................................................................................................................................139
FIGURE 4-59: ADD NEW UPGRADE TASK ......................................................................................................................................140
FIGURE 4-60: CPE ....................................................................................................................................................................141
FIGURE 4-61: MONITOR ............................................................................................................................................................141
FIGURE 4-62: DISPLAY ...............................................................................................................................................................143
FIGURE 4-64: INFORMATION .......................................................................................................................................................144
FIGURE 4-65: SETTINGS .............................................................................................................................................................144
FIGURE 4-66: SYNCHRONIZE .......................................................................................................................................................145
FIGURE 4-67: FREQUENCY LOCK ..................................................................................................................................................145
FIGURE 4-68: REBOOT ...............................................................................................................................................................145
FIGURE 4-69: HISTORY - UL/DL MCS ..........................................................................................................................................145
FIGURE 4-70: HISTORY - RSRP1/2 ..............................................................................................................................................146
FIGURE 4-71: HISTORY - CINR1/2 ..............................................................................................................................................146
FIGURE 4-72: HISTORY - SINR ....................................................................................................................................................147
FIGURE 4-73: HISTORY - DL/UL THROUGHPUT ..............................................................................................................................147
FIGURE 4-74: REBOOT ...............................................................................................................................................................148
FIGURE 4-75: REBOOT WARNING ................................................................................................................................................148
xi
FIGURE 4-77: PCI LOCK .............................................................................................................................................................149
FIGURE 4-79: REGISTER .............................................................................................................................................................150
FIGURE 4-80: DEVICE ................................................................................................................................................................151
FIGURE 4-81: NEW UPGRADE TASK .............................................................................................................................................152
FIGURE 4-83: SOFTWARE FILES ...................................................................................................................................................153
FIGURE 4-84: ALARM MENU ......................................................................................................................................................153
FIGURE 4-85: DASHBOARD ALARMS .............................................................................................................................................154
FIGURE 4-86: FIRST TIME USING ALARM > VIEW ............................................................................................................................154
FIGURE 4-87: ADD NEW TEMPLATE .............................................................................................................................................155
FIGURE 4-88: QUERY ................................................................................................................................................................155
FIGURE 4-89: ALARM DETAILS ....................................................................................................................................................156
FIGURE 4-90: EXPORT ...............................................................................................................................................................157
FIGURE 4-91: FILTER .................................................................................................................................................................157
FIGURE 4-92: ALARM > SETTINGS ................................................................................................................................................157
FIGURE 4-93: VIEW TEMPLATE ....................................................................................................................................................158
FIGURE 4-94: NEW TEMPLATE ....................................................................................................................................................158
FIGURE 4-95: ENB ALARM RULE .................................................................................................................................................158
FIGURE 4-96: OMC ALARM RULE ...............................................................................................................................................159
FIGURE 4-97: LIBRARY ...............................................................................................................................................................159
FIGURE 4-98: NOTIFICATION .......................................................................................................................................................160
FIGURE 4-100: ADVANCE > SAS..................................................................................................................................................161
FIGURE 4-101: SETTINGS ...........................................................................................................................................................162
FIGURE 4-102: OPERATIONS .......................................................................................................................................................162
FIGURE 4-112: SYSTEM .............................................................................................................................................................163
FIGURE 4-113: USER.................................................................................................................................................................163
FIGURE 4-114: MOVE TO USER GROUP ........................................................................................................................................163
FIGURE 4-115: USER.................................................................................................................................................................164
FIGURE 4-116: USER GROUP ......................................................................................................................................................164
FIGURE 4-117: + ADD USER GROUP ............................................................................................................................................164
FIGURE 4-118: ROLE SET ...........................................................................................................................................................165
FIGURE 4-119: + ADD ROLE (SET) ...............................................................................................................................................165
FIGURE 4-120: SECURITY RULE ...................................................................................................................................................166
FIGURE 4-121: OMC LOG .........................................................................................................................................................166
FIGURE 4-122: OMC SECURITY LOGS ..........................................................................................................................................167
FIGURE 4-123: HELP .................................................................................................................................................................167
FIGURE 4-124: BOSS NETWORK ARCHITECTURE ............................................................................................................................168
FIGURE 4-125: BOSS MENU ......................................................................................................................................................168
FIGURE 4-126: SUBSCRIBER........................................................................................................................................................169
FIGURE 4-127: + ADD SUBSCRIBER (1 OF 3) ..................................................................................................................................170
FIGURE 4-130: IMPORT .............................................................................................................................................................172
FIGURE 4-131: EXPORT TEMPLATE...............................................................................................................................................172
xii
FIGURE 4-132: IMPORT BULK SUBSCRIBERS ...................................................................................................................................173
FIGURE 4-134: CHANGE SERVICE PLAN (1 OF 2).............................................................................................................................174
FIGURE 4-135: CHANGE SERVICE PLAN (2 OF 2).............................................................................................................................174
FIGURE 4-136: OPERATION > ACTIVE EXAMPLE ..............................................................................................................................175
FIGURE 4-137: VIEW > OVERVIEW (1 OF 2) ..................................................................................................................................175
FIGURE 4-138: VIEW > OVERVIEW (2 OF 2) ..................................................................................................................................176
FIGURE 4-139: RECHARGE .........................................................................................................................................................176
FIGURE 4-140: VIEW > CHANGE SIM CARD ..................................................................................................................................177
FIGURE 4-141: SERVICE PLAN (1 OF 2) .........................................................................................................................................177
FIGURE 4-142: SERVICE PLAN (2 OF 2) .........................................................................................................................................178
FIGURE 4-143: INVOICES TAB .....................................................................................................................................................178
FIGURE 4-144: ACCOUNT TAB ....................................................................................................................................................178
FIGURE 4-145: EDIT (1 OF 2) .....................................................................................................................................................179
FIGURE 4-146: EDIT (2 OF 2) .....................................................................................................................................................180
FIGURE 4-147: DELETE ..............................................................................................................................................................180
FIGURE 4-148: RESET PASSWORD................................................................................................................................................181
FIGURE 4-149: SIM CARD SLOT ..................................................................................................................................................181
FIGURE 4-150: SIM CARD .........................................................................................................................................................182
FIGURE 4-151: ADVANCED QUERY...............................................................................................................................................182
FIGURE 4-152: APPLY MODE ......................................................................................................................................................183
FIGURE 4-153: ACTIVE CODE IMPORT ..........................................................................................................................................183
FIGURE 4-154: FILE IMPORT .......................................................................................................................................................184
FIGURE 4-155: RECORDS ...........................................................................................................................................................184
FIGURE 4-156: SYSTEM MENU ...................................................................................................................................................185
FIGURE 4-157: SERVICE PLANS (1 OF 2) .......................................................................................................................................185
FIGURE 4-158: ADVANCE QUERY.................................................................................................................................................186
FIGURE 4-159: ADD NEW SERVICE PLAN ......................................................................................................................................186
FIGURE 4-160: ADD SERVICE PLAN ..............................................................................................................................................187
FIGURE 4-162: SECURITY ...........................................................................................................................................................188
FIGURE 4-163: USER ACCOUNT ..................................................................................................................................................188
FIGURE 4-164: USER GROUP ......................................................................................................................................................189
FIGURE 4-165: VIEW USER GROUP ..............................................................................................................................................189
FIGURE 4-166: + ADD USER GROUP ............................................................................................................................................190
FIGURE 4-167: ROLE SET ...........................................................................................................................................................190
FIGURE 4-168: + ADD NEW ROLE SET ..........................................................................................................................................191
FIGURE 4-169: LOGS.................................................................................................................................................................191
FIGURE 4-170: HELP .................................................................................................................................................................192
xiii
List of Tables
TABLE 2-1: COMPUTER REQUIREMENTS ............................................................................................................................................2
TABLE 2-2: BASIC INFO FIELDS.........................................................................................................................................................5
TABLE 2-3: QUICK SETTING ............................................................................................................................................................8
TABLE 2-4: NTP .........................................................................................................................................................................11
TABLE 2-5: WAN/LAN ...............................................................................................................................................................16
TABLE 2-6: TUNNEL CONFIGURE > BASIC SETTING TAB ......................................................................................................................18
TABLE 2-7: TUNNEL CONFIGURE > ADVANCE SETTING FIELDS ..............................................................................................................20
TABLE 2-8: DIAGNOSTICS .............................................................................................................................................................23
TABLE 2-9: SECURITY SETTINGS - FOR INFORMATION ONLY .................................................................................................................24
TABLE 2-10: 1588 SYNC (FUTURE FEATURE) ....................................................................................................................................26
TABLE 2-11: LTE NEIGH FREQ SETTINGS .........................................................................................................................................30
TABLE 2-12: LTE NEIGH CELL TABLE SETTINGS .................................................................................................................................31
TABLE 2-13: TD-S NEIGH FREQ TABLE SETTINGS ..............................................................................................................................32
TABLE 2-14: TD-S CELL SETTING FIELDS .........................................................................................................................................33
TABLE 2-15: GSM FREQ/CELL > NEIGH FREQ TABLE SETTINGS ...........................................................................................................35
TABLE 2-16: GSM FREQ/CELL > NEIGH CELL SETTINGS .....................................................................................................................35
TABLE 2-17: A1, A2, A3, AND A5 EVENT THRESHOLD FIELDS.............................................................................................................38
TABLE 2-18: B2 EVENT THRESHOLD FIELDS .....................................................................................................................................39
TABLE 2-19: MEASUREMENT CONTROL FIELDS .................................................................................................................................39
TABLE 2-20: CELL SELECTION AND CELL RESELECTION FIELDS ..............................................................................................................40
TABLE 2-21: POWER CONTROL PARAMETERS ...................................................................................................................................42
TABLE 2-22: RRC STATUS PARAMETERS ..........................................................................................................................................44
TABLE 2-23: SON FUNCTIONAL PARAMETERS ..................................................................................................................................45
TABLE 2-24: RANDOM ACCESS PARAMETERS ...................................................................................................................................46
TABLE 2-25: SYNC ADJUST PARAMETERS.........................................................................................................................................48
TABLE 2-26: LINK ACTIVATION STATE DETECTOR ...............................................................................................................................48
TABLE 2-27: ICIC SETTINGS..........................................................................................................................................................49
TABLE 2-28: SIGNALING TRACE .....................................................................................................................................................50
TABLE 2-29: CELL ACCESS CONTROL...............................................................................................................................................55
TABLE 2-30: INTERFERENCE DETECTION ..........................................................................................................................................55
TABLE 2-31: MULTI NETWORK ELEMENT ........................................................................................................................................56
TABLE 2-32: SAS .......................................................................................................................................................................62
TABLE 3-1: COMPUTER REQUIREMENTS ..........................................................................................................................................68
TABLE 3-2: OVERVIEW FIELDS .......................................................................................................................................................71
TABLE 3-3: ROUTES.....................................................................................................................................................................74
TABLE 3-4: LAN SETTINGS ...........................................................................................................................................................76
TABLE 3-5: SSID ........................................................................................................................................................................79
TABLE 3-6: DMZ ........................................................................................................................................................................83
TABLE 3-7: APN MANAGEMENT ...................................................................................................................................................86
TABLE 3-8: MAC FILTER ..............................................................................................................................................................89
TABLE 3-9: IP FILTER ...................................................................................................................................................................90
TABLE 3-10: PORT FORWARDING...................................................................................................................................................92
xiv
TABLE 3-11: VPN > IPSEC ...........................................................................................................................................................96
TABLE 3-12: ADVANCE IPSEC SETTINGS ..........................................................................................................................................97
TABLE 3-13: GENERAL VPN > L2TP ..............................................................................................................................................98
TABLE 3-14: GENERAL VPN > PPTP ..............................................................................................................................................99
TABLE 3-15: GENERAL VPN > GRE .............................................................................................................................................100
TABLE 3-16: WEB SETTING ........................................................................................................................................................103
TABLE 3-17: TR069 SETTINGS ....................................................................................................................................................103
TABLE 3-18: SNMP..................................................................................................................................................................104
TABLE 3-19: PING AND TRACEROUTE ...........................................................................................................................................107
TABLE 3-20: IPERF ....................................................................................................................................................................108
TABLE 4-1: CLIENT REQUIREMENTS ..............................................................................................................................................110
TABLE 4-2: GUI ICONS ..............................................................................................................................................................113
TABLE 4-3: ENB MONITOR FIELDS ...............................................................................................................................................125
TABLE 4-4: MONITOR ................................................................................................................................................................141
TABLE 4-5: ALARM DETAILS ........................................................................................................................................................156
xv
1 Introduction
The Baicells products give network operators the ability to offer Internet service to subscribers using LTE-based
broadband wireless access. In a standard configuration, the key components include user equipment (UE),
eNodeB (eNB) radio access network equipment, and cloud-based core functions and network/subscriber
management applications (Figure 1-1). A subscriber connects a laptop, tablet, or other smart device through the
UE - also called Customer Premise Equipment (CPE) - which connects wirelessly to an eNB. The eNB
communicates with the LTE backhaul network.
The available operations, administration, and management (OAM) applications include an eNB GUI, a UE GUI,
the Baicells CloudCore Operations Management Console (OMC), and the Baicells CloudCore Business Operations
& Support System (BOSS). All of these apps are documented in this guide.
The eNB GUI and the UE GUI are used to configure and manage individual devices. The CloudCore apps may be
used to configure and manage all of the operator's network devices across multiple sites through the OMC and
all of the subscribers and service plans through BOSS. Baicells charges a monthly CloudCore usage fee based on
the number of active users.
CloudCore includes not only management apps but also provides the core LTE network functions that are shown
in the figure. Private network solutions such as Local EPC and Local OMC+BOSS are available.
Figure 1-1: Standard Baicells LTE Network
Many of the equipment and network interface parameters are preconfigured with recommended default
settings from the factory. However, every field and operation is explained and illustrated in this guide to allow
each operator the flexibility to use the Baicells Cloudcore-based solution to meet their unique requirements.
1
2 eNB GUI
This section uses BaiBS_RTS_3.4.8 software version for a single-carrier eNB running in standard mode as the
focus for explaining how to configure the eNB. Any major differences for non-standard or two-carrier
configurations are noted. Not all menus and fields are applicable to every eNB model or deployment scenario.
Specific documents that are available for such exceptions, for specific use cases, or to focus on particular
deployment scenarios are cited.
2.1 Computer Requirements

Refer to Table 2-1 for the minimum requirements of the computer that you use to launch the eNB GUI.
Table 2-1: Computer Requirements
Item Description
CPU Higher than Intel Core 1GHz
Memory Greater than 2G RAM
Hard Disk No less than 100 MB space available
Operating System Microsoft: Windows XP, Windows Vista, Windows 7, or higher Mac: MacOSX 10.5 or higher
Screen Resolution Higher than 1024 x 768 pixels
Browser Google Chrome 9+, Internet Explorer 7.0+, Mozilla Firefox 3.6+
You can launch the eNB GUI through a Web address (discussed in section 2.2). If you are on-site you can connect
a computer directly to the eNB unit's Local Maintenance Terminal (LMT), which is the MGMT/LAN port. Before
launching the GUI, you will need to set up the computer’s IP address to connect the client to the server, e.g.:
1. In Windows 7, select Start > Control Panel, and in the pop-up window click on Network and Internet.
2. Click on View network status and tasks, and then click on Local Connectivity.
3. In the window labeled Status of Local Connectivity, click on Properties. This will open the Properties of
Local Connectivity window.
4. Select Internet Protocol Version (TCP/IPV4), and click on Properties (Figure 2-1).
Figure 2-1: Internet Protocol Version (TCP/IPV4)
Either Obtain an IP address automatically and proceed to step 6, or
Use the following IP address and follow steps 5 and 6. If the option
for obtaining the IP address automatically fails, you will need to set
up the IP address manually.
5. Use the following IP address option: Input the IP address, subnet
mask, and default gateway, where:
• IP address is 192.168.150.xxx (xxx is a number from 100 to 254).
• Subnet mask is 255.255.255.0.
• Default gateway is 192.168.150.1.
6. In the command window, execute ping 192.168.150.1 and check
whether the connection between the local (client) computer and the
server is working.
2
2.2 Launching the GUI
To launch the GUI, open a Web browser and go to http://192.168.150.1. At the Login window (Figure 2-2), enter
admin for both the default name and password.
NOTE: For security reasons, you should change the password after you first log in rather than leaving the
default admin name and password. Refer to section 2.5.4 of this document.
Figure 2-2: Login

The GUI home page will display, showing the navigation pane on the left
(example in Figure 2-3). The menus may vary by hardware model, software
version, and eNB operating mode.
Use the vertical/horizontal scroll bars to see all of a menu's fields. Vertical scroll
bars are usually on the right side of the window. Horizontal scroll bars are usually
at the bottom of the window.
Figure 2-3: Home Page
3
2.3 Configuration Flow
This document is organized around the visual flow of the GUI menus and fields. However, during initial eNB
installation and configuration, perform the basic configuration steps in the order shown in Figure 2-4.
Figure 2-4: Initial eNB Configuration Flow
2.4 BTS Info

2.4.1 Basic Info
Under BTS Info > Basic Info are several fields providing essential eNB operational information. The fields that are
displayed depend on the hardware model, software version, and eNB operating mode. For example, if you were
running the eNB in HaloB mode, the field HaloB Status Enable would appear after WAN Link Status. If the eNB
is a two-carrier system configured for dual carrier (DC) / split mode, you will see fields that differentiate Cell 1
and Cell 2, e.g., RF Status(CELL1) and RF Status(CELL2).
Switching to a different operating mode requires a warm reboot of the eNB. You will see a message pop up to
please wait while settings are applied. When you get this message, click on OK to initiate the reboot (Figure 2-5).
Refer to the following documents that are specific to non-standard operating modes:
• HaloB User Guide
• Carrier Aggregation & Dual Carrier (Split Mode) Configuration Guide
• SAS Deployment Guide
4
Figure 2-5: Message
The eNB GUI refreshes the basic information every 15 seconds. The basic info window is shown in Figure 2-6,
and the fields are described in Table 2-2.
Figure 2-6: Basic Info
Table 2-2: Basic Info Fields
Field Name Description

Basic Info
Product Type The eNB model
Hardware Version The version number of the eNB hardware
Software Version The version number of the operating software running on the eNB
SN Number Serial Number identifier for the eNB
MAC Data Link layer Media Access Control address for the eNB
Status Info
Link Speed Negotiated Data rate negotiated between the eNB and the WAN interface
WAN Link Status Status of link between eNB and WAN (external) interface: Connected/Not connected
Cell Status Active or Inactive. When the eNB is operating (transmitting and receiving signals), the
status will be active. If not, the status will be reported as inactive.
MME Status Mobility Management Entity status is connected or not connected to the eNB. The
LTE MME is responsible for initiating paging and authentication of mobile devices. The
operator may have more than one MME in the network.
NOTE: This field will not appear in HaloB mode.
5
OMC Status Status of the link between the eNB and the Baicells Operations Management Console is
either connected or not connected
IPSec Status The Internet Protocol Security gateway is connected or not connected to the eNB. The
operator may have more than one IPSec gateway. The system will enable the IPSec by
default. In the presence of a security gateway, the security protocols are provided in
the network layer to ensure the safety of the message transmission.
NOTE: This field will not appear if the eNB is operating in HaloB mode.
Sync Status The eNB is either synchronized or not synchronized with other eNBs in the area. Refer
to section 2.7.3 for more information.
Sync Source The source providing synchronization of transmissions, typically the GPS
RF Status (CELL1) and (CELL2) Indicates if the RF is on (transmitting and receiving) or off. For two-carrier eNBs, each
cell is reported.
SAS Status Field that displays whether CBRS Spectrum Access System (SAS) is enabled or disabled.
Refer to section 2.8.8.
Radio Resource Usage
UL PRB Usage Shows the percentage of available Physical Resource Blocks being used in the uplink.
NOTE: A two-carrier eNB operating in dual carrier/split mode will display Cell
1 and Cell 2 data. Refer to the Carrier Aggregation & Dual Carrier
Configuration Guide.
DL PRB Usage Shows the percentage of available Physical Resource Blocks being used in the downlink.
NOTE: A two-carrier eNB operating in dual carrier/split mode will display Cell
1 and Cell 2 data. Refer to the Carrier Aggregation & Dual Carrier
Uplink BLER Block Error Ratio (BLER) is a measure of how successful a data transmission is over-the-
air at the Physical/MAC layer. Uplink BLER represents a ratio of the number of
erroneous data blocks received to the total number of blocks sent from UE to eNB.
DownLink BLER Block Error Ratio (BLER) is a measure of how successful a data transmission is over-the-
air at the Physical/MAC layer level. Downlink BLER is a ratio of the number of erroneous
data blocks received to the total number of blocks sent from the eNB to the UE.
UE Status
UE Connections Number of UEs currently connected to the eNB; if at least 1, additional fields display
UE ID The UE identification number assigned by the system
IMSI The International Mobile Subscriber Identity (IMSI) number. An IMSI is used to identify
the user of a cellular network and is a unique identification associated with all cellular
networks.
LGW MAC The MAC address of the local area network gateway.
IP Internet Protocol address for the eNB
PORT Port number assigned to the UE to allow remote logins. For example, type in the eNB
<IP address>:5<last 4 digits of IMSI>
UL Throughput (Mbps) The data throughput rate, in megabits per second (Mbps), of data transmitted uplink by
the UE to the eNB
DL Throughput (Mbps) The data throughput rate, in megabits per second (Mbps), of data transmitted
6
downlink by the eNB to the UE
ULSINR Uplink Signal-to-Interference-Plus-Noise Ratio (ULSINR) describes the signal strength of
the UE’s signals to the eNB in comparison with other interfering signals or background
noise, expressed in dB. Range is 0-30 dB.
DLCQI Downlink Channel Quality Indicator indicates how good or bad the communication
channel quality is for data being transmitted from the eNB to the UE. CQI is a
combination of SNR, SINR, and SNDR. Value range is 1-15.
ULMCS Uplink Modulation and Coding Scheme is a numerical index based on Orthogonal
Frequency Division Multiplexing (OFDM) that represents the maximum data rate the UE
can achieve when transmitting data over-the-air to the eNB. The MCS index value
comprises several variables, including channel width, modulation type, coding rate, and
spatial streams.
DLMCS Downlink Modulation and Coding Scheme – see description for “ulmcs” above, which in
this case pertains to the downlink
TxPower (dBm) Transmit (Tx) power is the amount of radio frequency (RF) power (in Watts) that the UE
produces. Unit of measurement is dBm. Range is -8 to +23 dBm.
Uplink BLER Block Error Ratio (BLER) is a measure of how successful a data transmission is over-the-
air at the Physical/MAC layer level. Uplink BLER represents a ratio of the number of
erroneous data blocks received to the total number of blocks sent from UE to eNB.
DownLink BLER Block Error Ratio (BLER) is a measure of how successful a data transmission is over-the-
air at the Physical/MAC layer level. Downlink BLER is a ratio of the number of erroneous
data blocks received to the total number of blocks sent from the eNB to the UE.
Pathloss&Interference(dB) Reports the reduction in power density (attenuation) as the wireless signal propagates
through space. The pathloss value impacts the overall RF link budget. An RF link budget
is an accounting of all the gains and losses from the transmitter, through the medium
to the receiver.
2.4.2 Quick Setting

The Quick Setting fields must be configured for cell parameters and transmission information (Figure 2-7). When
an eNB is attaching to the core network through the Baicells CloudCore, the PLMN field must be set to 314030.
When the eNB connects to CloudCore, the MME IP address fields will be set to 10.3.0.9 and 10.5.0.9. Check to
make sure the eNB has obtained the 2 MME addresses. All of the Quick Setting fields are described in Table 2-3.
NOTE 1: When CBRS Spectrum Access System (SAS) is enabled, the Quick Settings for Band, Bandwidth,
Frequency, and Power Modify become invalid and those fields greyed out; the eNB will use the settings
determined by the SAS vendor. Refer to the SAS Deployment Guide.
NOTE 2: Quick Settings for QRTB 2.0.x will display fields for Cell1 and for Cell2, also referred to as Primary
Cell (PCELL) and Secondary Cell (SCELL). Refer to the Carrier Aggregation & Dual Carrier (Split Mode)
For most Quick Setting parameter changes, you must perform a warm reboot the eNB for the changes to take
effect. Use the Reset button if you want to reset the configuration to the original default settings.
7
Figure 2-7: Quick Setting
Table 2-3: Quick Setting

Duplex Mode Preset field - cannot be configured at this time. Either Time Division Duplexing (TDD) or
Frequency Division Duplexing (FDD) depending on model and country.
Country Code The country code determines which regulatory restrictions to place on the eNB. Options:
FCC (United States Federal Communications Commission), or Canada or Other Area
Band The eNB’s operating frequency band, which is auto-selected based on the hardware model
or assigned by the Spectrum Access System (SAS) vendor if SAS is enabled.
Bandwidth For TDD mode, the channel bandwidth the eNB may use: 5, 10, 15, or 20 MHz. Applies to
both uplink and downlink. The default is 20 MHz. Example for B43: 44190 (3660 MHz) to
44490 (3690 MHz). If SAS is enabled, the bandwidth will be assigned by the SAS vendor.
EARFCN The frequency point of the eNB’s frequency.
Frequency(MHz) The eNB’s operating frequency. Range depends on the eNB hardware model, country code,
and whether or not SAS is enabled. Example for B41: 44190(3660MHz) to 44490(3690MHz).
If SAS is enabled, the bandwidth will be assigned by the SAS vendor.
SubFrame Assignment Downlink (DL) and uplink (UL) subframe configuration, either 0, 1, or 2, where:
0 = DL:UL is 1:3 transmission ratio*
1 = DL:UL is 2:2 transmission ratio
2 = DL:UL is 3:1 transmission ratio (default)
*Nova-436Q does not support SFA = 0 (1:3)
Refer to the BaiTip on this setting: https://community.na.baicells.com/t/baitip-

of-the-day-december-14th-2016-subframes-and-special-subframes/163
Special SubFrame Either 5 or 7. This is a standard LTE setting that pertains to synchronization of downlink and
Patterns uplink timing. The guard period between switching from DL to UL or UL to DL determines the
maximum supportable cell size. The guard period has to be large enough to cover the
propagation delay of DL interferers. The default setting is 7.
NOTE: BaiBS_QRTB_2.0.x provides additional options.
PCI Physical Cell Identification (PCI) allocated by the operator. Range is 0-503. PCI is an essential
Layer 1 cell identity for each cell site in the network. Planning PCIs is crucial for QoS.
Cloud EPC The Baicells CloudCore Evolved Packet Core (EPC) is either enabled/ON or disabled/OFF.
8
When you enable it, the parameters for Cell ID, MME Interface Binding, TAC, and MME IP are
automatically assigned. When you disable the Cloud EPC setting, it unlocks the greyed-out
fields below it, e.g., Cell ID, PLMN, and TAC. When you change the Cloud EPC setting, it will
perform a warm reboot of the eNB.
Cell ID The logical cell identification randomly assigned to this eNB by the operator. The range is 0-
268,435,455. In a two-carrier eNB, each cell has its own Cell ID.
MME Interface Binding When IPSec is set to enabled, this parameter is not displayed. Assign the interface connected
(Non-IPSec) to the MME or other external transmission interface if the eNB is operating in HaloB mode.
The interface should be selected among the network interfaces already configured. The
interface is configured under the GUI menu Network > WAN/LAN. The WAN interface is used
by default, but the VLAN interface or PPPoE can also be used.
S1 Connection Mode One - The eNB will connect only to the first MME
All - The eNB will connect to all MMEs configured
TAC Tracking Area Code (TAC) for where the eNB is located. The TAC is used to determine the
range of the paging information. Use a number between 1 - 65,535. The default is 1.
RF Status Enable/ON or disable/OFF the eNB’s RF antenna to allow it to transmit and receive or to
keep it from transmitting and receiving. The default is Enable/ON.
Power Modify Output power on each port, typically left with the default values. 30 dBm x2 = 33 dBm. Every
3 dB doubles the power. This field may be used in situations where you need to reduce the
output power, such as testing the eNB before installing it on a tower; restricting the eNB
output to reduce interference with other eNBs in the same geographical area; or staying
within Effective Isotropic Radiated Power (EIRP) rules. If SAS is enabled, the bandwidth will
be assigned by the SAS vendor.
PLMN The numerical identifier for the operator’s Public Land Mobile Network (PLMN) for this cell.
Must be a 5- or 6-digit number. If you are using the Baicells CloudCore, you must enter
PLMN = 314030.
MME IP This field appears for eNBs operating in standard mode. Enter the IP address of the Mobility
Management Entity (MME). If you are using the Baicells CloudCore, the MME IP addresses
will be 10.3.0.9 and 10.5.0.9.
2.5 System
The System menu (Figure 2-8) includes Network Time Protocol (NTP), software upgrade/rollback, configuration
backup, password reset (for the eNB GUI), Web enablement for remote access to the eNB*, and the CertStore
for uploading eNB certificates, e.g., licensing files.
NOTE 1: In QRTB 2.0.x, this menu includes Diagnostics but not CertStore. In RTS 3.4.8 the Diagnostics
menu is under the Network menu and therefore documented in the Network section.
NOTE 2: The Web menu and the CertStore menu are not available in QRTB 2.0.x.
9
Figure 2-8: System Menu
2.5.1 NTP
The operator may configure more than one NTP server to provide synchronized time-of-day to the eNB (Figure
2-9). The NTP fields vary slightly between single-carrier eNB RTS 3.4.8 and two-carrier eNB QRTB 2.0.x GUIs. The
fields are described in Table 2-4.
Figure 2-9: NTP
10
Table 2-4: NTP
Current Date & Time Displays the current date and time that the eNB is using
NTP Sync Period Network Time Protocol interval for synchronizing between the eNB and the primary NTP
server. The range is 10-65,535 seconds. The default is 60 seconds.
Time Zone The time zone for where the eNB is located
Date Format The format of the date display, e.g., mm/dd/yy
Enabled Enable/Disable NTP sync
NTP Servers – Server 1 Primary NTP server IP address
Port Primary NTP server port number
Server 2 Optional: Slave NTP server IP address
Port Optional: Slave NTP server port number
2.5.2 Upgrade
Use the Upgrade menu to upgrade or downgrade (rollback) the eNB software (Figure 2-10).
Figure 2-10: Upgrade
Perform the following steps:

1. Go to System > Upgrade.
2. Click on Choose File or Select File in the dialogue window that opens.
3. Find and highlight the target file, click on Open, and then click on the appropriate GUI action button --
Upgrade Now, Click Rollback, Upgrade Uboot, or Upgrade Patch, depending on hardware model and
software version. You may get a pop-up window to click Proceed.
4. After the upgrade is completed (about 5 minutes), the eNB will perform a warm reboot.
Caution: The reboot action will disrupt eNB service.
11
NOTE 1: Older versions of the eNB GUI may look different. When upgrading from an older version to the
latest, the GUI home page and other menus will automatically switch over to the new GUI. However,
when rolling back from the latest software to a former software version, the home page and other GUI
menus will not switch back to the older GUI. In this case you must verify the configuration (e.g., IP address).
NOTE 2: Additional upgrade capabilities, such as upgrading multiple eNBs simultaneously, are available
using the OMC. Refer to section 4.4.2.4 Upgrade.
2.5.3 Backup
The Backup function is used to back up the current configuration, log files, crash logs, and the core file*; to
import configuration files (e.g., to create a new eNB using the configuration from an existing eNB); or to restore
all of the default configuration settings for the eNB. The System > Backup window is shown in Figure 2-11.
*NOTE: The core backup file may be requested by Baicells support to assist in troubleshooting.
Figure 2-11: Backup
To initiate a backup:
1. Click on the blue rectangle action, e.g., Get Backup Files.
2. The system will display “Preparing backup file” and then present a dialogue window for you to select
where you want to save the file.
To import a configuration file:
1. Select Choose File, and navigate to the file you want to import.
2. Highlight the file, click on Open, and then select Import LTE Configurations.
To restore the default configuration:
1. Under Restore Default Configuration, select Restore Settings.
2. The eNB will perform a warm reboot when you restore the default configuration.
12
2.5.4 Password
The System > Password menu is where you change the eNB administrator’s (GUI) password. Enter the new
password, from 5 to 15 characters, and then enter it again to confirm it (Figure 2-12). Use the Reset button if
you want to reset the password to the original default setting of admin.
Figure 2-12: Password
2.5.5 Web
The default HTTP (Web) port for the eNB is port 80 (Figure 2-13). Use this menu to change the port number.
After entering a new port number and saving, the eNB will perform a warm reboot. It usually takes about 5
minutes to restart successfully. To access the GUI using the new port number, open a Web browser and enter
the IP address with the new port number, e.g., 192.168.100.101:80.
Figure 2-13: Web
2.5.6 CertStore
The CertStore menu provides a way to store important files unique to the eNB, such as regulatory
authorization files and HaloB or other licensed feature key files (Figure 2-14).
To upload any of the files, simply click on the Select File button and navigate to the file to be uploaded. Once
you highlight the file, click on Open. When you return to the Certificate Upload window, click on Upload. When
the file finishes uploading, the file name appears in the Certificate List portion of the window.
13
Figure 2-14: CertStore
2.6 Network
The Network settings are where you configure the network interfaces for the eNB (Figure 2-15).
NOTE 1: The MME&IPSec Binding menu is named IPSec/MME Pool in QRTB 2.0.x.
NOTE 2: The Diagnostics menu is under the System menu in QRTB 2.0.x
Figure 2-15: Network Menu
14
2.6.1 WAN/LAN
The WAN interface is an external communication portal (Internet connection) between the eNB’s Network
Management System (NMS) and the MME. The eNB’s NMS may be the Baicells Operations Management Console
(OMC) or the LTE NMS. The only option for the Interface name field is WAN.
The WAN/LAN menu (Figure 2-16) is for configuring the default router/ Domain Name Services (DNS), the type
of physical connection that the eNB uses to the external network, the local LAN information, and one or more
VLANs (single-carrier eNBs only). The physical Connect Type may be copper or fiber and may connect via DHCP,
PPPoE, or a Static IP:
• Dynamic Host Configuration Protocol (DHCP) – the eNB’s IP address will be obtained dynamically from
the local DHCP server. The current DHCP server IP address will be displayed, along with the link speed.
When DHCP is selected as the connection method, there are no further WAN fields to configure in this
window.
• Point-to-Point Protocol Over Ethernet (PPPoE) – not recommended. If PPPoE is selected, you will be
prompted to enter the user name and password. The range of each is 1 to 100 digits. You can also enter
an access controller name and service name.
• Static IP – IPv4 address, netmask, and gateway or IP address of the Domain Name Server (DNS), where
multiple addresses are allowed.
The Local Network/LAN fields are used to configure the Local Maintenance Terminal (LMT) port on the eNB. The
port may be used during initial eNB setup and configuration. Enter the IP address and subnet mask address for
the local network connection. The default LAN IP address is 192.168.150.1.
Figure 2-16: WAN/LAN
In the VLAN Table section, to add a VLAN click on the + Add icon to open the VLAN Setting window (Figure 2-17).
Enter a 1- to 15-digit VLAN name and a VLAN ID within the range of 2-4094. The VLAN ID must be a unique
number from any other VLAN. Avoid entering “12”, which is commonly used by the LAN interface. All of the
Network > WAN/LAN fields are described in Table 2-5.
15
Figure 2-17: VLAN
Table 2-5: WAN/LAN

Default Route/DNS
Interface Name Wide Area Network (WAN) is the eNB connection route to the Internet
DNS Servers Domain Name Server (DNS) IP address. More than one DNS server may be added.
Internet / WAN
Access LMT through Enable or disable the Local Maintenance Terminal connection through the WAN port.
WAN port
Connect Type Select Copper or Fiber type of connection to the WAN
MTU Maximum Transmission Unit - maximum network packet size. Default is 1500 bytes. Range: 1200-
1600 bytes.
Connect Via Options for the connection type are:
• Dynamic Host Configuration Protocol (DHCP) – the eNB’s IP address will be obtained
dynamically from the local DHCP server. The current DHCP server IP address will be displayed,
along with the link speed. When DHCP is selected as the connection method, there are no
further WAN fields to configure in this window.
• Point-to-Point Protocol Over Ethernet (PPPoE) – not recommended. If PPPoE is selected, you
will be prompted to enter the user name and password. The range of each is 1 to 100 digits.
You can also enter an access controller name and service name.
• Static IP – IPv4 address, netmask, and gateway or IP address of the Domain Name Server (DNS),
where multiple addresses are allowed
Static IP If the WAN connection is via static IP, enter the IP address
Subnet Mask If the WAN connection is via static IP, enter the subnet mask address
Gateway If the WAN connection is via static IP, enter the gateway address
Local Network / LAN
IP Address IP address for the local area network connection. The default LAN IP address is 192.168.150.1.
Subnet Mask Subnet mask for the local area network connection. Default is 255.255.255.0.
16
2.6.2 DHCP
If a local DHCP server will be used, in the Network > DHCP menu click on the check box next to LAN DHCP Server
Enabled (Figure 2-18). Enter the start (lowest) leased IP address and the end (highest) leased IP address in the
range.
The lease time field is used to indicate how long a leased IP address remains active before it expires. The range
of time may be up to 9,999 hours; the default is 12 hours. Use the Reset button if you want to reset the
configuration to the original default settings.
Figure 2-18:DHCP
2.6.3 MME&IPSec Binding
NOTE 1: This menu is not included in the GUI of an eNB operating in HaloB mode.
NOTE 2: The MME&IPSec Binding menu is named IPSec/MME Pool in QRTB 2.0.x.
NOTE 3: The MME IP addresses will be 10.3.0.9 and 10.5.0.9 when using PLMN 314030 connecting to the
Baicells CloudCore.
2.6.3.1 IPSec Setting

The IP Security (IPSec) interface is used to route the control plane information between the eNB and the EPC
(Figure 2-19). By default, in standard mode the system will enable the IPSec gateway. You can select the Internet
Key Exchange (IKE) Negotiation Destination Port of either 4500 or none, and either WAN(eth2), PPPOE(pppoe-
wan), or none for the Left Interface.
Figure 2-19: MME&IPSec Binding
17
2.6.3.2 IPSec Tunnel List
Under the IPSec Tunnel List, you can define up to two sets of data per IPSec tunnel. Tunnel 0 and Tunnel 1 display
information about the tunnel name, gateway, authorization method, and status. If you click on the Settings icon,
a new window called Tunnel Configure opens (Figure 2-20), where you can configure the tunnel fields. Notice
the two tabs, Basic Setting and Advance Setting. In RTS 3.4.8 you can also add another IPSec tunnel by clicking
on the + Add icon.
2.6.3.2.1 Tunnel Configure - Basic Setting
The Basic Setting fields are shown in Figure 2-20 and described in Table 2-6.
Figure 2-20: Tunnel Setting - Basic Setting Tab
Table 2-6: Tunnel Configure > Basic Setting Tab

Enabled Check to enable/ON or uncheck to disable/OFF IP security gateway
Tunnel Name The existing tunnel name will be shown in a light grey color. The field may be configured
only if fewer than the maximum 2 data tunnels are currently defined. The tunnel name may
be 10 characters, either digits 0-9 or lower-case letters a-z or upper case letters A-Z.
Gateway Enter the IPSec security gateway IP address. Make sure the IP address entered here
matches the actual IP address on the security gateway side. When using the Baicells
CloudCore, enter baicells-epc.cloudapp.net.
18
Right Subnet and Mask IP address and subnet mask of the remote subnet, which must be consistent with the
security gateway side. Messages within this address range will be packed as a tunnel.
Left Identifier Identification of this client end (0-48 digit string). It must be consistent with the security
gateway side. If there is no security gateway left identifier, leave this field empty.
Right Identifier Identification of the server end (0-48 digit string). It must be consistent with the security
gateway side. If there is no security gateway right identifier, leave this field empty.
AuthBy Caution: Change not recommended!
Authentication method of the IPSec server. Must be consistent with the security gateway
side. Options are:
• (psk) (default)
• (cert)
• (aka_psk)
• (aka_cert)
Pre Shared Key Caution: Change not recommended!
The Pre Shared Key (PSK) must be consistent with the security gateway.
LeftSourceIP Virtual address allocation: 0-30 digit string for RTS 3.4.8 or 0-64 digit string for QRTB 2.0.x. If
absent, use the local IP address.
2.6.3.2.2 Tunnel Configure - Advance Setting

Caution: It is highly recommended that for the Advance Setting fields you use the
default values. Improper changes may lead to system exceptions.
The Advance Setting fields become particularly important to network operations as areas become denser with
users. Please refer to Figure 2-21 and Table 2-7.
Figure 2-21: Tunnel Setting - Advance Setting Tab
[Recommend leaving at default values]
19
Table 2-7: Tunnel Configure > Advance Setting Fields
[Recommend leaving at default values]

IKE Encryption Internet Key Exchange (IKE) encryption method. IKE is a protocol used to ensure security for
virtual private network (VPN) negotiation and remote host or network access. Options are:
• aes128 (default)
• aes256
• 3des
IKE DH Group IKE Diffie-Hellman (DF) key computation, or exponential key agreement, to be used
between two entities. Options are:
• modp768 (default)
• modp1024
• modp1536
• modp2048
• modp4096
IKE Authentication IKE authentication algorithm to be used:
• sha1 (default)
• sha512
ESP Encryption Encapsulating Security Payload (ESP) – a member of the IPsec protocol suite that provides
origin authenticity, integrity, and confidentiality protection of packets. Options:
• aes128 (default)
• aes256
• 3des
ESP DH Group ESP Diffie-Hellman (DF) key computation, or exponential key agreement, to be used
between two entities. Options are:
• null
• modp768
• modp1024 (default)
• modp1536
• modp2048
• modp4096
ESP Authentication ESP authentication algorithm to be used: sha1
KeyLife IPsec security association (SA) renegotiation time. Format: Minutes, Hours, or Days. The
default setting is 40 minutes.
IKELifeTime IKE security association renegotiation time. Format: Minutes, Hours, or Days.
The default setting is 60 minutes.
RekeyMargin Renegotiation time before the expiry of IKELifeTime (negotiate the IKE security association
time before the expiry of IKELifeTime). Format: Minutes, Hours, or Days. The default setting
is 5 minutes.
Self Define Keyingtries Number of renegotiation attempts after an IKE negotiation fails. Default is 3.
Dpdaction DPD stands for dead peer detection (DPD) protocol. Determines what action to take when a
gateway exception occurs:
• None
• Clear
• Hold
• Restart (default)
Dpddelay Time interval for sending the DPD detection message. Format: Seconds, Minutes, or Days.
The default setting is 30 seconds.
20
2.6.3.3 IPSec Binding
NOTE: In QRTB 2.0.x this function is labeled MME Pool.
In a typical network setup using the Baicells CloudCore, the security tunnel is between the eNB and the MME
in the core network. This menu is used to bind an IPSec tunnel with an MME IP address.
The Baicells CloudCore uses two MMEs, MME-1 and MME-2. MME-1 uses IP address 10.3.0.9, and MME-2
uses IP address 10.5.0.9. Use the configuration fields for MME-1/tunnel 1 and MME-2/tunnel 2 to bind the
interfaces (Figure 2-22).
Figure 2-22: IPSec Binding
2.6.4 LGW
The Baicells eNodeB (eNB) splits the data plane and the control plane, so there are two IP addresses per user
equipment (UE). The data plane is sent out the local gateway (LGW), while the control plane is routed through
an IPSec tunnel to the Cloud Evolved Packet Core (EPC).
Most manufacturers do not split the two planes and all traffic is sent through a hardware EPC. You have that
option with Baicells as well, but anyone using the Baicells CloudCore EPC uses LGW.
Using the eNB GUI, follow the steps below to configure LGW.
1. Go to Network > LGW (Figure 2-23).
2. Verify that LGW is enabled.
3. Select one of three LGW modes:
• NAT - Network Address Translation - The IP address is kept local between the eNB and CPE. The eNB
modifies the network address in the IP packet headers. To reach user equipment remotely, enter:
https://<eNB IP address><5+last 4 digits of CPE IMSI>
Leave the CPE Web GUI https port as 433; do not change the port number. IP binding uses address
range 10.10.0.1 to 10.10.0.254.
• Router - Enable static IP addressing, and identify the range of addresses. The LGW (external router)
will assign an IP address when a CPE attaches. IP binding uses address range 10.10.0.1 to 10.10.0.254.
• Bridge - Layer 2 will create a virtual interface for each CPE that attaches using a DHCP request to
create a 1:1 mapping between the CPE IP address (from the EPC) and the LGW IP address. A CPE's
MAC address is generated from its IMSI: Convert the last 12 digits to hex, and then prefix it with
"8A". For example, if the IMSI = 117040000002918, the MAC address would be 8A:95:02:F9:B6:6.
21
4. Enter the required fields. For the LGW Interface Binding field, you can select either WAN or PPPoE. You
can then enter the LGW IP Pool address and netmask. The IP binding range is 10.10.0.1 to 10.10.0.254.
For router mode, if you enable Static Address, enter the first and last IP addresses and configure the
IMSI to IP Binding IMSI.
5. If you change the LGW mode, you must perform a warm reboot the eNB for the changes to take effect.
Rebooting will interrupt service temporarily.
Figure 2-23: LGW Setting (NAT, Bridge, & Router Modes)
2.6.5 Diagnostics
NOTE: In QRTB 2.0.x the Diagnostics menu appears under the System menu.
Use the System > Diagnostics menu to perform a ping test or traceroute from the eNB. Figure 2-24 provides an
example of the fields. Each field is described in Table 2-8. After entering the settings, click on Implement to run
the test.
Figure 2-24: Diagnostics
22
Table 2-8: Diagnostics
Parameter Description
Method of Diagnostics Ping or Traceroute
Target IP/Domain The IP address or domain name of the destination device
Packet Size The size of the packet to be sent. Range is 56-9000 bytes.
Timeout The timeout period when the test ends. Range is 1-10 seconds.
Packet Num The number of packets to be sent. Range is 1-10.
2.6.6 Static Routing

Use this menu to add Static IP routing addresses and monitor their status (Figure 2-25). Existing routes will
display in the Added Route List section of the window, showing the destination IP address, netmask or genmask
(for general destination netmask), and other data.
To add a new static routing address to the list, click on the + (Add) icon, enter the information, and click on Save.
Once created, you can enable/disable the address. To edit an existing static routing setting, click on the display
icon, modify the information, and then save.
Figure 2-25: Static Routing
2.7 BTS Setting

The base transceiver station (BTS) settings relate to eNB security, management, and synchronization with other
network elements (Figure 2-26).
NOTE: In QRTB 2.0.x this menu also includes the sub-menu, Carrier Setting, covered in section 2.7.6.
Figure 2-26: BTS Setting Menu
23
2.7.1 Security Setting
Caution: Do not modify these security settings; keep the default values.
The Security Setting fields pertain to the LTE encryption algorithms that are used (Figure 2-27). The selections
will depend on the LTE core network setup. In a two-carrier eNB, these settings apply to both the primary and
secondary cell. Table 2-9 identifies the parameters.
Figure 2-27: Security Setting
Table 2-9: Security Settings - For Information Only

Parameter Name Description
Ciphering Algorithm Encryption algorithm options:
• EEA0 (default)
• 128-EEA1: 128-EEA1, EEA0
• 128-EEA2: 128-EEA2, EEA0
• 128-EEA3: 128-EEA3, 128-EEA1, EEA0
Integrity Algorithm Integrity protection algorithm options:
• 128-EIA1: 128-EIA1, EIA0 (default)
• 128-EIA2: 128-EIA2, EIA0
• 128-EIA3: 128-EIA3, 128-EIA1, EIA0
2.7.2 Management Server

For the Network Management Service (NMS), an operator has the option to use the Baicells CloudCore OMC, a
Local OMC, or their own management server (Figure 2-28). Follow the steps below to configure the management
server.
1. Optional: Enable a Secure Socket Layer (SSL) connection for enhanced security. When you set to
Enable, a message will pop up telling you the default port number for HTTPS is 8443.
2. Enter the http:// address for your management server. If it is the Baicells CloudCore OMC, enter
baiomc.cloudapp.net:48080/smallcell/AcsService. If you are using Local OMC or other EMS/NMS
server, enter the URL for that device.
3. If you are using the Baicells CloudCore OMC for your NMS, enter your unique operator CloudKey ID
that you received from Baicells. The CloudKey is used as part of the plug-and-play aspect of the
Baicells network elements. When you configure your CloudKey number in the device GUI (eNB and
UE), the first time the device is powered on it will automatically be associated to your OMC account.
24
Figure 2-28: Management Server
2.7.3 Sync Setting

The LTE technology standards specify timing and synchronization requirements between adjacent eNBs.
Synchronized transmissions help to avoid eNBs interfering with one another, optimizes bandwidth usage, and
enhances network capacity.
In the Sync Setting menu (Figure 2-29), enable the Forced Sync Switch and enable the GPS Sync Switch. Select
the timing technology - either Glonass, BeiDou, Galileo, or Qzss. When you click on Save to retain the settings,
a pop-up message will tell you to reboot (warm reboot) the eNB for the new settings to be applied. Click on OK.
NOTE: The QRTB 2.0.x Sync Setting menu has only one field: Sync Mode. The options are FREE_RUNNING,
NTP, PTP, GNSS, NL, EXT_CLK, and EXT_PPS. The additional options are related to selecting 1588v2 sync
mode, which will be introduced in North America in 1H2020.
After the reboot, the window will display the GPS software version, the current number of satellites the GPS is
tracking, and the satellite signal strength. Use the Reset button if you want to restore the configuration settings
to their original default values.
Figure 2-29: Sync Setting
Upon successful beta testing of 1588v2 synchronization, commercial Baicells eNBs will be able to support both
unicast and multicast; Layer 2 multicast will not be supported. At that time, the eNB will meet the time variation
requirements within +/- 1 µs and frequency deviation within 50 ppb.
25
Using 1588v2 synchronization requires a highly reliable network environment. The network delay jitter must be
less than 20 µs, and the link delay must be less than 1 ms. This method will not support soft routing, soft
switching, or other similar devices. The operator will need to purchase a separate 1588v2 license for the eNB to
support this sync mode. Refer to Figure 2-30 and Table 2-10.
Figure 2-30: 1588 Sync (future feature)
Table 2-10: 1588 Sync (future feature)

Parameter Name Description
1588 Sync Switch Enable or disable the 1588v2 server sync method
Domain Enter a domain identifier in the range of 0-255
Unicast Multicast Switching Select either unicast or multicast transmission
Asymmetry Enter the asymmetry (offset) value, in nanoseconds, between the server and the eNB.
The range is -65535 to 65535.
1588 Interface Binding WAN is the only available interface binding
2.7.4 HaloB Setting

The HaloB Setting menu (Figure 2-31) is used by operators who have a HaloB license for the eNB. This menu is
used to enable/disable the eNB to operate in HaloB mode. Refer to the Baicells HaloB User Guide for more
information about this feature.
Figure 2-31: HaloB Setting
26
2.7.5 License Management
The License Management menu may be used to import license files for optional features such as HaloB or
regulatory certificates of authorization to operate (Figure 2-32). When imported, the files are stored in the eNB
memory and shown in the License List area of this window. The bottom half of the window pertains licenses for
using one or more 1588v2 servers for transmission timing synchronization (refer to section 2.7.3 Sync Setting).
Figure 2-32: License Management
2.7.6 Carrier Setting (Nova-436Q only)

Reference: Carrier Aggregation & Dual Carrier (Split Mode) Configuration Guide
The Carrier Setting menu is used for two-carrier eNBs running QRTB software (Figure 2-33). You can set the
Nova-436Q eNB to run as either a single carrier, two combined carriers using Carrier Aggregation (CA), or two
separate carriers using Dual Carrier (DC)/split mode. In single carrier mode only Cell 1 will operate, and it will
use only 2 RF ports instead of 4. Operators may need to use this mode if they have limited spectrum or are
planning to change to CA or DC mode at a later time, for example when more capacity is needed for the coverage
area.
If you set the Carrier Mode to Dual Carrier, the Carrier Aggregation Enabled check box is automatically checked.
Leave as is and save if you want to run the eNB in CA mode. If you want to use DC mode, uncheck the check box
and save. Whenever you change the carrier setting, you must perform a warm reboot the eNB for the change
to take effect.
NOTE: The Nova-436Q CA mode supports contiguous or non-contiguous channels in the North American
bands defined by 3GPP.
27
Figure 2-33: Carrier Setting
2.8 LTE
The LTE menu contains several sub-menus related to mobility as well as other radio-related settings (Figure 2-34).
Many LTE parameters are important for efficient wireless network operation.
When setting up mobility, you have to establish the neighboring eNBs operating in the same geographical area
as is the eNB that you are configuring. This information is completed for each eNB so that the eNBs collectively
work well with one another to handle mobile users and to balance the traffic load.
NOTE 1: HaloB-enabled eNBs operate as standalone entities and do not support mobility.
NOTE 2: QRTB 2.0.x does not support mobility; therefore, the Lte Setting menu includes only Advanced
and SAS Settings sub-menus.
NOTE 3: QRTB 2.0.x does not support Spectrum Analyzer or UL PRB RSSI Report.
Figure 2-34: LTE Menu
Use the first 5 sub-menus under LTE to (a) configure the neighboring eNBs’
frequencies and identify each eNB running on that frequency (section 2.8.1); (b)
configure the current eNB’s mobility parameters (beginning with section 2.8.2); and
(c) examine the current eNB’s advanced settings (section 2.8.6).
It is a good idea to review all of the information in this section to understand how
the configuration settings relate.
Important: Make sure the current and neighboring eNBs are (a) GPS enabled and
(b) synchronized.
If you change these parameters, perform a warm reboot of the eNB for the new
configuration to take effect. A case study for LTE to LTE handoffs is provided in
section 2.8.7 Real-World LTE to LTE Handoff Configuration Example.
28
2.8.1 Identify Neighbor Frequencies & Cell Information
Potentially, there are 3 types of neighboring eNBs: other LTE eNBs; eNBs running another type of wireless
technology called Time Division Synchronous Code Division Multiple Access (TD-SCMDA); and those operating
with the Global System for Mobile (GSM) communications technology. For each type of neighboring eNB, you
will first add the neighbor frequency settings via the Neigh Freq Table, and then you will add the cell information
associated to the frequencies via the Neigh Cell Table.
You can configure the Neigh Cell Table for both inter-frequency (between different frequencies) and intra-
frequency (within the same frequency) neighboring eNBs. For inter-frequency cells, you must add the neighbor
inter-frequency settings in the Neigh Frequency Table before you try to add the neighbor inter-frequency cell
(eNB) information. Conversely, if you need to delete a neighbor inter-frequency record, you must first delete the
neighbor inter-frequency cells (eNBs) associated to it. For an intra-frequency neighbor cell, meaning a neighbor
eNB operates on the same frequency as the eNB you are configuring, you do not need to configure the Neigh
Freq Table but you do need to configure the Neigh Cell Table.
2.8.2 LTE Freq/Cell

Using the LTE Freq/Cell sub-menu (Figure 2-35), you can configure parameters related to how adjacent eNBs
operating with LTE technology work with the Baicells LTE eNB that you are configuring. You will define for the
Baicells eNB how to deal with any neighboring LTE eNBs.
Figure 2-35: LTE Freq/Cell
2.8.2.1 LTE Neigh Freq Table

Under Neigh Freq Table, select the + (Add) icon. This will open the Neigh Freq Settings window, as shown in
Figure 2-36 and described in Table 2-11. You can configure up to 8 LTE frequency tables. The parameters shown
in the figure reflect the recommended settings for this operator example.
29
Figure 2-36: Neigh Freq Table
Table 2-11: LTE Neigh Freq Settings

EARFCN In short, this is the frequency point of the neighboring eNB’s frequency. Range is 0-65,535.
EARFCN stands for Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial
Radio Access (E-UTRA) Absolute Radio Frequency Channel Number.
Q-RxLevMin The minimum received signal level at which user equipment (UE) will detect a neighboring
eNB’s signal. The range is -70 to -22 dBm. A typical value is -62, which equals -124 dBm.
Q-OffsetRange Indicates the difference in signal level between the serving and neighboring eNBs, as
determined by the received signal level at the UE. If the received signal level is better from a
neighboring eNB by at least this amount of difference in dB, the UE will reselect the other cell.
The range is +24 to -24 dB. A typical value is 0 dB.
Resel Timer Determines when the cell reselection timer expires. Range is 0-7 seconds. A typical value is 0
seconds.
Resel Prior Priority of cell reselection to cells at this frequency. Range is 0-7 (integer). A typical value is 4.
Resel Thresh High The cell reselection threshold for higher priority inter-band frequency. Represents the access
threshold level at which the UE will leave the serving cell and reselect another cell at the target
frequency (assuming the target frequency cell has a higher cell reselection priority than the
serving cell). Range is 0-31 dB. A typical value is 18 dB.
Resel Thresh Low The cell reselection threshold for lower priority inter-band frequency. Represents the access
frequency (assuming the target frequency cell has an absolute priority lower than the serving
cell). Range is 0-31 dB. A typical value is 13 dB.
P-Max The maximum transmit power that UEs in this cell are allowed to use in the uplink. The range is
-30 to 33 dBm. A typical value is 23 dBm.
2.8.2.2 LTE Neigh Cell Table

You can configure up to 16 LTE Neigh Cell Tables. Click on the + (Add) icon to open the Cell Setting window, as
shown in Figure 2-37 and described in Table 2-12. The parameters shown in the figure reflect the recommended
settings for this operator example.
30
Figure 2-37: LTE Neigh Cell Table Settings
Table 2-12: LTE Neigh Cell Table Settings

PLMN The 5- or 6-digit Public Land Mobile Network (PLMN) that the neighbor cell belongs to.
Cell ID The cell ID of the neighbor cell. Range is 0-268,435,455.
EARFCN Frequency point of the neighbor cell. EARFCN stands for Evolved Universal Mobile
Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) Absolute Radio
Frequency Channel Number.
PCI Physical Cell Identifier (PCI) of the neighbor cell. Range is 0-503.
QOFFSET Frequency offset of this neighbor cell. Indicates the difference in signal level between the
serving and this neighboring eNB, as determined by the received signal level at the UE. If the
received signal level is better from this neighbor eNB by at least this amount of difference in
dB, the UE will reselect this cell. Range is +24 to -24 dB. A typical value is 0 dB.
CIO Cell Individual Offset (CIO) is this neighbor eNB’s cell offset, which is one of the variables
used to determine which eNB will best serve a given UE. Range is -24 to 24 dB. A typical
value is 0 dB.
TAC Tracking Area Code (TAC) of this neighbor cell. Range is 0-65535.
eNodeB Type Macro or Home
2.8.3 TD-S Freq/Cell

Using the TD-S Freq/Cell sub-menu (Figure 2-38), you can configure parameters related to how adjacent eNBs
operating with TD-SCDMA technology work with the Baicells LTE eNB that you are configuring. You will define
for the Baicells eNB how to deal with any neighboring TD-SCDMA eNBs. The maximum is 5.
31
Figure 2-38: TD-S Freq/Cell
2.8.3.1 TD-S Neigh Freq Table

Under TD-S Neigh Freq Table, click on the + (Add) icon to open Neigh Freq Settings, as shown in Figure 2-39 and
described in Table 2-13. Even though some of the field names are the same as in the LTE Neigh Freq Table, in
some cases the ranges are different for TD-SCDMA. Configure up to 5 frequency tables for TD-S eNBs.
Figure 2-39: TD-S Neigh Freq Table Settings
Table 2-13: TD-S Neigh Freq Table Settings

TDD Mode Select a chip rates (bps) to spread the signal: UTRA_TDD_128, UTRA_TDD_384, or
UTRA_TDD_768.
Bands Channels in which the TD-S neighbor eNB operates. Options are A, B, C, D, E, or F.
UARFCN In short, this is the frequency point of the neighboring eNB’s frequency. Range is 9505 to 9595,
or 10054 to 10121. The acronym stands for Universal Mobile Telecommunications System
32
(UMTS) Absolute Radio Frequency Channel Number.
Q-RxLevMin Minimum received signal level at which a UE will detect a neighboring eNB’s signal. The range
is -60 to -13 dBm.
Resel Prior Priority of cell reselection to cells at this frequency. Range is 0-7.
Resel Thresh High The cell reselection threshold for a higher priority inter-band frequency. Represents the access
frequency (assuming the target frequency cell has a higher cell reselection priority than the
serving cell). Range is 0-31.
Resel Thresh Low The cell reselection threshold for a lower priority inter-band frequency. Represents the access
frequency (assuming the target frequency cell has an absolute priority lower than the serving
cell). Range is 0-31.
P-Max The maximum transmit power UEs in this cell are allowed to use uplink. Range: -50 to -33 dB.
Q-Offset Indicates the difference in signal level between the serving and neighboring eNBs, as
determined by the received signal level at the UE. If the received signal level is better from a
neighboring eNB by at least this amount of difference in dB, the UE will reselect the other cell.
The range is -15 to 15 dB.
2.8.3.2 TD-S Neigh Cell Table

Under Neigh Cell Table, click on the + (Add) icon. This will open the Cell Setting window, as shown in Figure 2-40
and described in Table 2-14. You can configure up to 5 cell tables.
Figure 2-40: TD-S Freq/Cell > Neigh Cell Table Settings
Table 2-14: TD-S Cell Setting Fields

UARFCN Display of the frequency point of the neighboring eNB’s frequency.
PLMN The Public Land Mobile Network (PLMN) the neighbor cell belongs to. Range is 5-6 digits.
Cell ID The cell ID of the neighbor cell. Range is 1-65,535.
RNC ID The neighbor cell’s Radio Network Controller (RNC) ID. Range is 0-65,535.
33
Scrambling Code The scrambling code assigned to this neighbor cell. Range is 0-127. The scrambling code is
unique to each eNB and is used to distinguish one eNB’s data from another eNB’s data.
LAC Location Area Code (LAC) of the neighbor cell
2.8.4 GSM Freq/Cell

Using the GSM Freq/Cell sub-menu (Figure 2-41), you can configure parameters related to how adjacent eNBs
operating with GSM technology work with the Baicells LTE eNB that you are configuring. You will define for the
Baicells eNB how to deal with any neighboring GSM eNBs. You can configure up to 16 adjacent GSM eNB
frequency tables and 16 cell tables.
Figure 2-41: GSM Freq/Cell > Neigh Freq Table Settings
2.8.4.1 GSM Neigh Freq Table

Under GSM Neigh Freq Settings, click on the + (Add) icon. This will open the Neigh Freq Settings window, as
shown in Figure 2-42 and described in Table 2-15. Please note that even though some of the field names are the
same as in the LTE Neigh Freq Table, in some cases the ranges for GSM are different.
Figure 2-42: GSM Freq/Cell > Neigh Freq Table Settings
34
Table 2-15: GSM Freq/Cell > Neigh Freq Table Settings

BAND Channel in which the GSM neighbor eNB operates: GSM850, GSM900, DCS1800, or PCS1900.
ARFCN In short, this is the frequency point of the neighbor eNB’s frequency. Range is 128-251. The
acronym stands for Absolute Radio Frequency Channel Number.
Q-RxLevMin The minimum received signal level at which a UE will detect a neighboring eNB’s signal. The
range is 0-45 dBm.
Resel Prior Priority of cell reselection to cells at this frequency. The range is 0-7.
Resel Thresh High The cell reselection threshold for a higher priority inter-band frequency. Represents the
access threshold level at which the UE will leave the serving cell and reselect another cell at
the target frequency (assuming the target frequency cell has a higher cell reselection priority
than the serving cell). The range is 0-31.
Resel Thresh Low The cell reselection threshold for a lower priority inter-band frequency. Represents the
access threshold level at which the UE will leave the serving cell and reselect another cell at
the target frequency (assuming the target frequency cell has an absolute priority lower than
the serving cell). The range is 0-31.
2.8.4.2 GSM Neigh Cell Table

Under Neigh Cell Table, click on the + (Add) icon. This will open the Cell Setting window, as shown in Figure 2-43
and described in Table 2-16.
Figure 2-43: GSM Freq/Cell > Neigh Cell Settings
Table 2-16: GSM Freq/Cell > Neigh Cell Settings

ARFCN Display of the frequency point of the neighbor eNB’s frequency.
PLMN The Public Land Mobile Network (PLMN) the neighbor cell belongs to. Range is 5-6 digits.
LAC Location Area Code (LAC) of the neighbor cell
BSIC Base station identification code (BSIC) of the neighbor cell
Cell ID The cell ID of the neighbor cell. Range is 1-65,535.
35
2.8.5 Mobility Parameter
The Mobility Parameter menu pertains to how roaming UE sessions are handled between different eNBs in the
same service area. When a UE is actively connected to an eNB, the current eNB is referred to as the serving eNB
or cell. The other eNBs in the area are referred to as either neighbor or target eNBs or cells.
The process of a device moving from cell to cell and changing over from its serving eNB to a neighbor (target)
eNB is called handoff or handover. The UE exchanges information with its serving eNB to perform cell selection
and reselection based on parameters which you will set for each eNB. Refer to Figure 2-44.
NOTE 1: The terms handoff and handover are used interchangeably in LTE.
NOTE 2: Handoff is not supported at this time on an eNB operating in HaloB mode.
Figure 2-44: Handoff
What the UE measures that determines cell selection and reselection is the Reference Signal Received Power
(RSRP) of the serving as well as neighboring eNBs. The measurements are sent periodically to the serving eNB,
which then determines if the UE would be better served by an adjacent eNB. Refer to the case study in section
2.8.7 Real-World LTE to LTE Handoff Configuration Example.
The default settings in the Mobility Parameter sub-menus represent standard LTE deployments. Many of the
mobility settings should be left with their default values. Any modification should be determined only by
experienced wireless professionals.
Figure 2-45 shows the sub-menus for the mobility parameters. In terms of LTE to LTE handoff, only the A1, A3,
A5, Measurement Control, Cell Selection Parameter, and Cell ReSelection Parameter fields are used. The B2 Event
Thresholds pertain only to TD-SCDMA and GSM adjacent cells, not to adjacent LTE cells.
You will configure these mobility parameters for every adjacent eNB. If the serving eNB determines that more
than one adjacent eNB meets the RSRP event thresholds, the Cell Reselection settings will determine to which
adjacent eNB the serving eNB would hand off.
To begin the configuration, next to A1 Event Threshold and the other event thresholds, select the + icon. The
resulting window presents the fields for each sub-menu: A1, A2, A3, and A5 Event Threshold (Figure 2-46). The
configuration values in the figure are the recommended settings for the eNB in this operator example. Table
2-17 describes each of the event threshold fields.
36
Figure 2-45: Mobility Parameters
Figure 2-46: A1, A2, A3, and A5 Event Thresholds
37
Table 2-17: A1, A2, A3, and A5 Event Threshold Fields

A1 Event Threshold
LTE A1 RSRP Threshold The LTE A1 event is triggered when the serving cell’s Reference Signal Received Power (RSRP)
becomes better than the A1 threshold. The A1 event can be used to turn off certain inter-cell
measurements. Range is 0-97 (integer). Default value is 90. In this example, the
recommended value is 45 (integer), which means -140 dBm + 45 = -95 dBm.
A2 Event Threshold
LTE A2 RSRP Threshold The LTE A2 event is triggered when the serving cell’s Reference Signal Received Power (RSRP)
becomes worse than the A2 threshold. Range is 0-97 dB. The default is 65. In this example,
the recommended value is 40 (integer), which means -140 dBm + 40 = -100 dBm.
Refer to the Baicells Tip concerning A2 settings:
https://www.facebook.com/groups/
baicellsoperatorsupportgroup/permalink/1760449424249426/
A3 Event Threshold
Intra-Freq Handover A3 The LTE A3 event is triggered when a neighbor cell becomes better than the serving cell by as
Offset much as the offset value. The offset can be either positive or negative. Range is -30 dB to 30
dB. The default is 10. In this example, the recommended value also is 10 (integer), which
means 10*0.5 = 5 dB.
A3 Hysteresis Specifies the entering (A3-1) and leaving (A3-2) conditions for A3 events. Default is 1 dBm.
Range: 0 - 30 dBm
A3 Time To Trigger The period of time that specific criteria for the A3 event are met in order to trigger a
measurement report. Default is ms160.
A5 Event Threshold
Inter-Freq Handover A5 The LTE A5 event is triggered when the serving cell becomes worse than Threshold 1 while a
RSRP Threshold 1 neighbor cell becomes better than Threshold 2. Range is 0-97 (integer). The default is 70. In
the example, the recommended value is 40 (integer): equals -140 dBm + 40 = -100 dBm.
Inter-Freq Handover A5 Range is 0-97 (integer). The default is 65. In this example, the recommended value is 45
RSRP Threshold 2 (integer), which equals -140 dBm + 45 = -95 dBm.
A5 Time To Trigger The period of time that specific criteria for the A5 event are met in order to trigger a
measurement report. Default is ms480. Range: ms0 - ms5120
The B2 Event Thresholds pertain only to TD-SCDMA and GSM adjacent cells, not to adjacent LTE cells. The B2
Event Threshold fields are shown in Figure 2-47 and described in Table 2-18.
Figure 2-47: B2 Event Threshold
38
Table 2-18: B2 Event Threshold Fields

UTRA B2 RSRP Threshold parameter 1 of the UTRA Time Domain Scheduling (TDS) based B2 event. Range is
Threshold 1 0-97 dB. Default is 70 dB.
RSRP Threshold 2 Threshold parameter 2 of the Reference Signal Received Power (RSRP) based B2 event.
Range is -5 dB to 91 dB. The default is 0.
GERAN B2 RSRP Threshold parameter 1 of the GSM Edge Radio Access Network (GERAN) B2 event based on
Threshold 1 Reference Signal Received Power (RSRP). Range is 0-97 dB. Default is 10 dB.
GERAN B2 IRAT Threshold parameter 2 of the GSM Edge Radio Access Network (GERAN) B2 event, based on
Threshold 2 Inter-Radio Access Technology (IRAT). Range is 0-63 dB. The default is 20.
The Measurement Control parameters determine how frequently the UE measures the serving and
neighboring eNBs’ RSRP values and at what level of hysteresis-based RSRP triggers a handoff (Figure 2-48 and
Table 2-19). The UE evaluates the RF conditions around it and reports the information to the serving eNB. The
eNB’s radio resource management function evaluates the measurements and determines whether or not to
hand off the session to a neighbor eNB. The parameters shown in the figure reflect the recommended settings
for this operator example.
Figure 2-48: Measurement Control Parameters
Table 2-19: Measurement Control Fields

Hysteresis Refers to the hysteresis (historical records) of the handover measurement events. The value is
used to avoid the frequent triggering of cell handover evaluation due to the fluctuation in wireless
signals. This setting tells the UE, if you hear another eNB with at least this amount of dB better,
initiate a handover. The lower the number the sooner the handover is initiated. If set too low, it
may cause the UE to ping-pong between eNBs. Such events are tracked by the EPC, but not by the
eNB. Range is 0-30 dB. The default is 0. In this example, the recommended value is 5 dB.
Time To Trigger Length of time the target cell RSRP value is better than the serving cell before the UE initiates a
handover request. The range is 0-5120 ms. The default is ms480 (recommended).
Range: ms0 - ms5120.
The Cell Selection Parameter and Cell ReSelection Parameter sub-menus are shown in Figure 2-49 and
described in Table 2-20. The parameters shown in the figure reflect the settings recommended in this example.
39
Figure 2-49: Cell Selection and Cell ReSelection Parameters
Table 2-20: Cell Selection and Cell ReSelection Fields

Cell Selection Parameter
Qrxlevmin(dBm) Minimum acceptable signal level at the UE before cell selection. Range is -70 dBm to -22
dBm. The default is -60. In this example, the recommended value is -62 dBm. The value will
be this number x 2, e.g., if set to -60 the value will actually be -120 dBm, minus the offset.
Qrxdevminoffset Minimum level offset (difference) in RSRP at the UE needed for cell selection. Range is 1-8
dB. The default is 1. In this example, the recommended value is 1 dB.
Cell ReSelection Parameter
S-IntraSearch Intra-band measurement threshold that must be met before the UE will reselect a neighbor
eNB. Range is 0-31 (integer). In this example, the recommended value is 31 (integer), which
means 31*2 = 62 dB.
S-NonIntraSearch Inter-band measurement threshold that must be met before the UE will reselect a neighbor
eNB. Range is 0-31 (integer). In this example, the recommended value is 31 (integer), which
means 31*2 = -62 dB.
Qrxlevmin(dBm) Minimum level for reselection. Range is -70 to -22 (integer). In this example, the
recommended value is -62 (integer), which means -62*2 = -124 dBm.
Qhyst Delay time for reselection. Range is 0-24 dB. In this example, the recommended value is 1 dB.
Reselection Priority Priority for reselection. Range is 0-7 (integer). In this example, the recommended value is 4.
ThreshServingLow Threshold for selection to cells of lower priority. Range is 0-31 dB. In this example, the
recommended value is 31 dB.
Allowed Meas BW Sib3 Measurement bandwidth allowed. Choices are n15, n25, n50, n75, or n100. The default
value is n50.
40
2.8.6 Advanced
Caution: Many, if not all, of the Advanced settings should be left with their default values. Any
modifications should be determined only by experienced wireless professionals.
The Advanced settings are primarily used to fine-tune the RF settings and to configure special features. Figure
2-50 shows the LTE > Advanced sub-menus which are explained in this section.
NOTE 1: On a two-carrier eNB running QRTB 2.0.x, the Advanced settings are configured on the primary
cell (PCELL) for both the PCELL and the secondary cell (SCELL).
NOTE 2: The following menus that are shown in Figure 2-50 are not available in QRTB 2.0.x:
X2, eNodeB Settings, GAP Settings, Tx And Rx Parameters, SON Function Settings, Working Mode, Sync
Adjust Parameter, ICIC Settings, Signaling Trace, Cell Access Control Settings, Interference Detection
Parameters, Multi Network Element, SSH Setting, Cell barred info.
NOTE 3: A two-carrier eNB running QRTB 2.0.x has an additional Advanced menu called Radio Parameters.
Figure 2-50: Advanced
2.8.6.1 X2
NOTE: This menu is not available in QRTB 2.0.x.
An X2 interface is a logical interface which may be enabled for intra-LTE eNB handovers when the Mobility
Management Entity (MME) being used for the UE is the same for both the serving and the target eNB. If
enabled, the two eNBs can communicate directly with one another without communicating through a radio
network controller (RNC). The X2 starts buffering on the target eNB in advance of a handover.
By default, the X2 interface parameter is disabled. The recommended setting is Enable. To enable X2, select
Enable from the pull-down menu (Figure 2-51).
41
Figure 2-51: X2 Parameter
2.8.6.2 Power Control

The Power Control Parameters help to limit UE transmit power to the eNB being configured, including the
power of the transmitted reference signals. The parameters factor into the overall RF link budget. The power
control parameters are shown in Figure 2-52 and described in Table 2-21.
Figure 2-52: Power Control Parameters
Table 2-21: Power Control Parameters

p-Max The maximum power that a UE can transmit in this cell. Range is -30 dB to 33 dB.
Reference Signal Power Transmit power of the reference signals. Auto-set to 2.
Power Ramping Step size of the Physical Random-Access Channel’s (PRACH’s) power index broadcast to
the UEs via a Layer 1 channel used by UEs to access the mobile network for call setup and
bursty data transmission. Options are 0, 2, 4, or 6.
Preamble Init Target Power Initial power of the Physical Random-Access Channel (PRACH). Range is -90 to -120.
Po_nominal_pusch Physical Uplink Shared Channel (PUSCH) carries user data. It supports Quadrature Phase
Shift Keying (QPSK) and 16 Quadrature Amplitude Modulation (QAM), with 64QAM being
optional. Range is -126 to 24 dB.
42
Po_nominal_pucch Physical Uplink Control Channel (PUCCH) is used to carry Uplink Control Information
(UCI). LTE UEs can never transmit both PUCCH and Physical Uplink Shared Channel
(PUSCH) during the same subframe. Range is -127 to -96 dB.
Alpha Power control loss compensation factor, which controls the UE power. Range is 0 to 100.
Max Pathloss Maximum threshold at which the UE determines not to transmit to the eNB based on
pathloss. Pathloss is the difference between the transmitted reference signal information
and the actual received signal power. Range is 100 to 135.
Basic UL Target SINR or Desired Signal-to-Interference-Plus-Noise Ratio (SINR) level to ensure an acceptable level
Target ul sinr of communication between the UE and eNB, while also controlling interference that
might be caused to neighboring cells. Range is -6 dB to 10 dB.
Po_ue_pucch Initial UE transmit power when using Physical Uplink Control Channel (PUCCH). Range is -
8 dB to 7 dB.
Po_ue_pusch Initial UE transmit power when using Physical Uplink Shared Channel (PUSCH). Range is -8
dB to 7 dB.
PA Physical Downlink Shared Channel (PDSCH) is the main data bearing channel. Power
boosting the reference signal is allocated to UEs on a dynamic and opportunistic basis.
The relative PDSCH power is determined by two computed parameters: PA and PB. Traffic
loading must be balanced with controlling interference to neighboring cells. Auto-set
to -3.
PB See description for parameter “PA”. Range is 0-3.
To optimize channel conditions on the eNB, please refer to the BaiTip posted on the Baicells
website: https://community.na.baicells.com/t/recommened-advanced-settings-on-the-enb-to-optimise-
channel-conditions/531
2.8.6.3 eNodeB
The eNodeB Settings sub-menu is used to name the eNB you are configuring and to select the eNB type, as
shown in Figure 2-53. For the name, the types of characters and length of the name that may be used are
provided in the figure. For type, choose either Macro or Home. "Macro" means the eNB is covering a large cell
area and the transmission power is on the higher end of the power range. "Home" means the eNB's transmission
power is much lower than Macro and covers a much smaller area.
Figure 2-53: eNodeB Settings
2.8.6.4 GAP
43
The Inter-Frequency Measurement Gap (Inter-Frequency Meas GAP) field pertains to how a UE measures the
signal quality of a neighbor cell that is operating at a different frequency from the serving cell. The gap
parameter (Figure 2-54) creates a time gap during which the UE will not receive or transmit with the serving
cell. It will switch its frequency to the target cell and perform a measurement of signal quality before coming
back to the serving cell.
The Baicells eNB radio resource control (RRC) gap may be set to 1 or 2, where:
• 1 is a GAP measurement period of 40 ms (default)
• 2 is a GAP measurement period of 80 ms
Figure 2-54: GAP Settings
2.8.6.5 RRC Status

Under Radio Resource Control Status (RRC Status Parameters), you will configure parameters related to how
the RRC protocol in the air interface control plane establishes, maintains, and releases an RRC connection
between UEs and the eNB. If the Ue Inactivity Timer is set to 0, the timer does not take effect. The UE inactive
status duration is equal to the RRC inactivity timer times the maximum expiry count. Refer to Figure 2-55 and
Table 2-22.
Figure 2-55: RRC Status Parameters
Table 2-22: RRC Status Parameters

Ue Inactivity Timer Expire time of the UE inactive status timer(s). Range is 0-4294967 seconds. If set to 0, the timer
does not take effect.
Max Expiry Count Maximum number of times the UE’s inactive status timer expires. The range is 1-65,535 times.
2.8.6.6 Radio Parameters (Nova-436Q Only)

In a two-carrier Nova-436Q eNB running QRTB 2.0.x software, if there are uplink signal issues you can use this
menu to increase the eNB's default Uplink Receive Gain Correction value, shown as zero (0) dB in Figure 2-56.
Conversely, if UEs are near the eNB and their transmit power is very high, you can decrease this value. Enter a
value between -48 and 48 dB. One unit is measured in 0.25 dB.
Figure 2-56: Radio Parameters
44
2.8.6.7 SON Function Settings
The Self-Organizing Network (SON) Function Settings refer to standards-based automation technology
designed to make the planning, configuration, management, optimization, and healing of mobile radio access
networks (RANs) simpler and faster. When enabled, the eNB will auto-configure these mobility related values.
Refer to Figure 2-57 and Table 2-23.
Figure 2-57: SON Function Settings
Table 2-23: SON Functional Parameters

PCI Selfconfig Enable or disable self-configuration of the eNB Physical Cell Identifier (PCI) and other RF
settings. Default: Disable
PCI Self-configuring The Physical Cell Identifier (PCI) numbers to use. Enter each PCI number, and click the +
Optional List (Add) icon. The range is 0-503. To remove a PCI number, select the Remove button.
Home eNodeB Start PCI Starting PCI number. Range is 0-503. Default is 0.
Home eNodeB PCI Range The last PCI number that may be used. Range is 0-503. Default is 503.
ANR report Type Automatic Neighbor Relation trigger: No ANR (default), STRONG CELL, or INTRA&INTER
Period report amount Specifies the number of measurement reports applicable for the event threshold period.
Options are r1, r2, r4, r8, r16, r32, r64, and Infinity (default)
Intra-Freq ANR A3 Offset See "Intra-Freq ANR A3 Offset" in section 2.8.5, Table 2-17.
Inter-Freq ANR A5 RSRP See "Inter-Freq ANR A5 RSRP Threshold 1" in section 2.8.5, Table 2-17.
Threshold 1
Inter-Freq ANR A5 RSRP See "Inter-Freq ANR A5 RSRP Threshold 2" in section 2.8.5, Table 2-17.
Threshold 2
45
2.8.6.8 Tx And Rx Parameters
The Transmit (Tx) and Receive (Rx) Parameters PHY RXGAIN field controls how much RF signal gain UEs will have
in the uplink. Do not modify this field. The range is -48 to 48 dB. Refer to Figure 2-58.
Figure 2-58: Tx and Rx Settings
2.8.6.9 Random Access

The preamble format to be used in a specific cell is messaged from the eNB to the UEs using a Physical
Random-Access Channel (PRACH) configuration index. The UE uses the preamble to access the network when
it is first powered on. The settings for Random Access Parameters are shown in Figure 2-59 and explained in
Table 2-24.
Figure 2-59: Random Access Parameters
Table 2-24: Random Access Parameters

Preamble Format Packet preamble format [based on the Physical Random-Access Channel (PRACH) index] to
be used for this cell and communicated to UEs. Options are 0, 2, or 4.
Prach-Configuration The PRACH configuration index number that will be broadcast to the UEs via SIB2. Options
Index are: 0, - 4, 6, 9, 10, 12, 15, 16, or 18.
Zero Correlation Zone Specifies the cyclic shift intervals to generate the preamble sequence. Range is 0-15 in the
Config standard eNB GUI. The range is 0-63. Default is 10.
Refer to the BaiTip on this setting: https://community.na.baicells.com/t/baitip-
of-the-day-december-14th-2016-subframes-and-special-subframes/163
PRACH Freq Offset Determines the location of the PRACH preamble in the frequency domain. Range: 5 - 89
PRACH Root Sequence Index broadcast by the eNB and used by UEs to calculate the preamble they should use to
attach to the eNB. The default value is 12. Range: 0 - 837.
46
2.8.6.10 Working Mode
The Working Mode allows you to configure the maximum*number of simultaneous, connected users or limit it
to service a maximum of 32 users, called Low Delay Mode (Figure 2-60). When this value is set to Low Delay
Mode(32UE), fewer users will be served but will have more capacity than when the value is set to handle the
maximum of 96 users. Otherwise, select Multi-user Mode(96UE) to support the highest possible number of users.
*NOTE: The maximum number of users depends on eNB model, software version, and operating mode.
Figure 2-60: Working Mode
2.8.6.11 Scheduling Algorithm

The Scheduling Algorithm fields are important for smooth RF operation and can impact key performance
indicators such as cell throughput, cell edge users, Voice Over IP (VoIP) capacity, and data Quality of Service
(QoS). The most common scheduling strategy is round robin (RR), which is the default type for both UL and DL.
Refer to Figure 2-61.
Round Robin scheduling allocates resources to all UEs equally. Neither QoS nor memory is considered.
NOTE 1: In addition to round robin, a two-carrier eNB running QRTB 2.0.x includes SCI and PFS:
(a) SCI, also referred to as Maximum Carrier-to-Interference (C/I) ratio, allocates resources to UEs
in favor of those with good channel quality. QoS is considered, but memory is not.
(b) Proportionally Fair Scheduling (PFS) balances between user channel quality and fairness, where
both cell throughput and user fairness are considered.
NOTE 2: A later release of RTS software is planned to support PFS.
Figure 2-61: Scheduling Algorithm Parameters
2.8.6.12 Sync Adjust Parameter
The Sync Adjust Parameters help the system to compensate for packet delay in the uplink and downlink.
Do not modify these fields. Refer to Figure 2-62 and Table 2-25 concerning these settings.
NOTE: At this time only GPS sync is allowed. The 1588v2 server option for syncing is not available in North
America at this time, but is planned in a later release.
47
Figure 2-62: Sync Adjust Parameters
Table 2-25: Sync Adjust Parameters

GPS or 1588 Sync Adjust Value Default is 0 µs. Range: -2000 to 2000 µs
ICTA Adjust Value Industry Council for Tangible Assets (ICTA) Adjust Value
Default is 0 µs. Range: -2000 to 2000 µs
2.8.6.13 Link Activation State Detector

The Link Activation State Detector is used to enable or disable a link watchdog. If you select Enable, a
watchdog action will check the UE every “x” minutes to see if it is connected or disconnected from the EPC,
LAN, or both, and if disconnected after “x” number of minutes the watchdog will perform a warm reboot the
UE. If you select Disable, the watchdog will not reboot the UE. Refer to Figure 2-63 and Table 2-26.
Figure 2-63: Link Activation State Detector
Table 2-26: Link Activation State Detector

Link Keep Alive Enable/disable the link activation state detector between the UE and EPC, LAN, or both
Link Keep Alive Timer Select 5, 10, or 15 minutes for the link keep alive timer. 5 minutes is the default.
2.8.6.14 ICIC Setting
In LTE, Inter-Cell Interference Coordination (ICIC) reduces inter-cell interference by having UEs that are at the
same cell edge but attached to different cells use different frequency resources. This is typical for roaming
scenarios and sometimes PCI conflicts.
To enable ICIC among adjacent eNBs, go to Advanced > ICIC Setting and enable Single Frequency Reuse (Figure
2-64). In most cases you will accept the default values of the other fields, which are described in Table 2-27.
48
Figure 2-64: ICIC Settings
Table 2-27: ICIC Settings

SFR Enable/Disable Single Frequency Reuse
CEU Decisions Offset Common Equipment Unit (CEU) frequency offset. Range is -30 to 30 dB.
CEU Decision Hysteresis CEU hysteresis threshold. Range is 0-30.
CEU Report Interval CEU reporting interval, in milliseconds or minutes. Default is 1 min.
CEU Report Amount Limit number of CEU reports per reporting period (integer). Default is Infinity.
Options: r1, r2, r4, r8, r16, r32, r64, Infinity.
CEU PRB Range CEU Physical Resource Block (PRB) range. Default is 0 - 14. Options: 0 - 14, 15 -
29, 30 - 49, 0 - 11, 12 - 23, 24 - 35, 36 - 49.
PA Adjustable Enable or disable Power Amplifier (PA) adjustment
2.8.6.15 Signaling Trace
2.8.6.15.1 Description
The Signaling Trace function is typically used for troubleshooting UE attachment and handover issues. During a
signaling trace, Radio Resource Control (RRC) and Stream Control Transmission Protocol (SCTP) packets are
captured in real-time. The packets are sent to a remote computer running Wireshark* or to a Local OMC** and
displayed so the data can be analyzed. The Baicells CloudCore OMC does not support the Signaling Trace feature.
*NOTE 1: For more information about the Wireshark app, refer to https://www.wireshark.org/.
**NOTE 2: Local OMC is covered in the Local OMC Administrator Guide, available upon request.
The RRC protocol controls the UE and eNB over-the-air communications, and is especially important during
mobility scenarios as a mobile user is handed off from one eNB to another. SCTP is a transport layer for the S1-
MME signaling bearer and is responsible for the Evolved Packet System (EPS) bearer setup/modification/release,
handover procedures, Non-Access Stratum (NAS) signaling transport, and paging procedures.
2.8.6.15.2 Configuration
In the eNB GUI, go to LTE > Advanced > Signaling Trace to enable the RRC and SCTP functions (Figure 2-65). Each
field is described in Table 2-28. You do not need to reboot the eNB to initiate the trace.
49
Figure 2-65: Signaling Trace
Table 2-28: Signaling Trace

RRC Signaling Trace Switch Enable Enable or disable the RRC signaling trace function.
Switch
RRC Signaling Trace OMC Format Enable or disable sending the RRC signaling trace to the Local OMC.
RRC Signaling Trace Dest IP The IP address of the computer where RRC signaling trace data will be sent.
The default value is 127.0.0.1, which should be changed.
RRC Signaling Trace Dest Port The port number of the computer where the RRC signaling trace data will be
sent. Range: 0-65535. Default value is 4337.
NOTE: For MAC computers, if there is an existing MAC package (directory) make
sure you use a different port number for the RRC package.
RRC Signaling Trace Duration The duration of the RRC signaling trace. Range: 0~30 minutes. A value of zero
(0) means continuous.
SCTP Signaling Trace Enable Switch Enable or disable the SCTP signaling trace function.
SCTP Signaling Trace OMC Format Enable or disable sending the SCTP signaling trace to the Local OMC.
SCTP Signaling Trace Dest IP The IP address of the computer where the SCTP signaling trace data will be
sent. The default value is 127.0.0.1.
SCTP Signaling Trace Dest Port The port number of the computer where the SCTP signaling trace data will be
sent. Range: 0-65535. Default value is 36412.
SCTP Signaling Trace Duration The duration of the SCTP signaling trace. Range: 0-30 minutes. A value of zero
(0) means continuous.
50
2.8.6.15.3 Wireshark Settings
Go to section 2.8.6.15.3.1 if you are using Wireshark 1.x, or go to section 2.8.6.15.3.2 if you are using Wireshark
2.x to use the app for signaling trace. A few troubleshooting tips are described in section 2.8.6.15.3.3.
2.8.6.15.3.1 Wireshark 1.x
1. Protocol:
a. Go to Edit > Preferences > Protocols > PDCP-LTE (Figure 2-66).
b. Select the check box for Try Heuristic LTE-PDCP over UDP framing.
Figure 2-66: Protocol Setting
2. SCTP message:
a. Find the related UDP package, and start a capture.
b. Locate and select a packet with protocol UDP and destination port 36412. Or, you can use filter
udp.port=36412.
c. Right-click on the packet, and choose Decode As… (Figure 2-67).
Figure 2-67: Decode As
3. Go to the Transport tab, and set the destination as 36412 and the decoding type as SCTP (Figure 2-68).
Get the SCTP message as shown in the figure.
51
Figure 2-68: Get SCTP Message
2.8.6.15.3.2 Wireshark 2.x

1. Protocol:
a. Go to Analyze > Enabled Protocols.
b. Select the check boxes for PDCP-LTE and pdcp_lte_udp (Figure 2-69).
Figure 2-69: Protocol Setting
2. SCTP message:
a. Find the related UDP package, and start a capture.
b. Locate and select a packet with protocol UDP and destination port 36412. Or, you can use filter
udp.port=36412.
c. Right-click on the packet, and choose Decode As… (Figure 2-70).
52
Figure 2-70: Decode As
d. Go to the Transport tab, and set the destination as 36412 and the decoding type as SCTP (Figure
2-71). Get the SCTP message as shown in the figure.
Figure 2-71: Get SCTP Message
3. Filter:
a. In the filter window, enter lte_rrc, and display the RRC message.
b. Optionally, enter the RRC and S1AP command as shown in Figure 2-72.
Figure 2-72: Filter
NOTE: In order to distinguish multiple user packets in RRC messages, we use the MAC-I field, which
changes it to show UE RNTI (Figure 2-73).
53
Figure 2-73: UE RNTI
2.8.6.15.3.3 Troubleshooting
Following are some common issues when running a signaling trace, and how to address them.
• IP address: Make sure the IP you use for the computer you are sending trace messages to is reachable.
First try to ping it from the eNB (System > Diagnostics). If a ping does not go through, check for and
temporarily disable any firewall or antivirus software apps.
• No RRC messages: If a trace yields no results, try changing the filter condition (refer back to Figure 2-72).
• Local OMC not displaying results: Make sure you have registered the eNB in the Local OMC.
2.8.6.16 Cell Access Control
The Cell Access Control menu under LTE > Advanced is for operators who have deployed a Local EPC in their
private network. This function is not available for operators using the Baicells CloudCore EPC. The feature allows
an operator with a Local EPC to enable or disable the Allocation and Retention Priority (ARP) function for this
eNB (Figure 2-74). ARP prioritizes traffic services assigned a Guaranteed Bit Rate (GBR). Typically, ARP is
considered only when a new bearer (subscriber) attempts to attach. If the eNB is out of resources, the
attachment request will be denied until resources are available.
The goal of this feature is to ensure proper QoS for in-progress sessions by rejecting radio bearer requests when
they cannot be accommodated, e.g., when the total uplink GBR bandwidth exceeds the UL GBR Acceptance
Threshold or the total number of GBR bearers exceeds the Maximum Number of GBR Bearers. The thresholds
defined in this sub-menu determine how much of the eNB's resources can be allocated in the uplink and in the
downlink. Refer to Table 2-29 for a description of the fields.
Figure 2-74: Cell Access Control
54
Table 2-29: Cell Access Control
ARP Enable or disable the ARP function
UL GBR Acceptance Uplink GBR acceptance threshold. Range: 0-10000 Mbps. Default is 10000 Mbps.
Threshold
DL GBR Acceptance Downlink GBR acceptance threshold. Range: 0-10000 Mbps. Default is 10000 Mbps.
Threshold
2.8.6.17 Interference Detection Parameters
Using this menu you can enable/disable the Interference Detection feature to trigger an alarm notification when
the eNB reaches a set of configured thresholds. The eNB will calculate UL and DL path loss based on Reference
Signal (RS) power, Signal-to-Noise Ratio (SNR), and other measurements. It compares the path loss data between
UL and DL, and if there is a significant difference (in dB) for a specified period of time, it is likely due to UL
interference. If the thresholds are met, the eNB reports the interference alarm (ID 11224) to the OMC.
To configure the Interference Detection feature, in the eNB GUI go to LTE > Advanced > Interference Detection
(Figure 2-75). The fields are described in Table 2-30.
Figure 2-75: Interference Detection
Table 2-30: Interference Detection

Interference Detection Enable or disable the interference detection function.
Detect Threshold Interference detection threshold, based on the amount of difference, in dB, between
UL and DL path loss. Range is 1-20 dB. Default is 5 dB.
Alarm Threshold Alarm trigger threshold, based on the percentage of all UEs passing traffic that are
meeting the detection threshold for the amount of time specified in the Alarm Period
field. Range is 1-100%. Default is 60%.
Alarm Period Set the minimum period of time that the interference detection threshold is sustained
before the alarm is triggered. Range is 1-60 minutes. Default is 5 minutes.
2.8.6.18 Multi Network Element
If you have multiple network elements providing the same service, use this sub-menu to bind the eNB to:
• A specific S1-User path (e.g., operator has Local EPC as well as CloudCore EPC);
• An X2 interface (eNB to eNB handoff scenarios); or
• A TR-069 interface (multiple ACS servers).
55
Refer to Figure 2-76 and Table 2-31.
Figure 2-76: Multi Network Element
Table 2-31: Multi Network Element

S1-U Binding Select the binding interface for S1-U - either WAN (default) or VLAN
X2-C and X2-U Binding Select the control plane and user traffic binding interface for X2 - either WAN (default)
or VLAN
tr069 Binding Select the binding interface for TR-069 - either WAN (default) or VLAN
2.8.6.19 SSH Setting
Enable the Secure Shell (SSH) setting for a secure, encrypted connection to the eNB from a remote location
(Figure 2-77). If SSH is disabled, you will not be able to SSH into the eNB remotely.
Figure 2-77: SSH
2.8.6.20 Cell barred info
A barred cell is a type of access control, where UEs of a certain priority level may not be allowed to attach to the
eNB due to congestion. An Access Class between 0-15 is embedded in the user SIM card as a way to prioritize
user traffic for a period of time. The restricted access to the eNB is not a permanent blockage.
Use the LTE > Advanced > Cell barred info menu to enable/disable barring of the 0-15 classes, and to enter the
time periods for each (Figure 2-78: Cell barred info). The time period determines how long the eNB is barred
from being accessed by any UEs with a SIM access class that has been enabled for barring.
"MO-Signaling" refers to Mobile Originated Signaling, i.e., when a UE requests access to the eNB. "MO-Data"
refers to Mobile Originated Data, meaning actual user traffic.
The cell barring factor for MO-Signaling and MO-Data determines if a UE needs to treat a cell as barred or not.
The barring factor can be a value between 0 - 0.95 in increments of 0.05. The barring time determines for how
long the cell is barred from access, and can be configured as 4, 8, 16, 32, 64, 128, 256, or 512 seconds.
56
Figure 2-78: Cell barred info
57
2.8.7 Real-World LTE to LTE Handoff Configuration Example
Following is an example of the LTE mobility-related parameters based on eNB software version RTS 3.4.8, to
illustrate how the system performs based on the configuration settings. Figure 2-79 shows how the LTE Neigh
Frequency and Neigh Cell Table settings are configured in this customer example.
Figure 2-79: LTE Neigh Freq and Neigh Cell
Explanation of the event thresholds: The serving eNB starts the A2 and A3 event threshold measurements. If
the A3 event threshold is met by a neighbor intra-frequency cell, the UE session will be handed off to that target
eNB. If the A2 event threshold is met, it stops the A2 measurement and triggers the A1 and A5 measurements.
Then, if the A1 event threshold is met, it stops the A1/A5 measurements and starts the A2 evaluation again.
Assuming the A5 measurement indicates the neighbor inter-frequency cell is better than the serving cell, the
serving eNB will hand off the session to the neighbor eNB.
Example: For the A1 Event Threshold, assume the starting measurement is set to 45 (Figure 2-80). If the UE
measures RSRP > -95 dBm, the UE will report the A1 event and the network will stop the A1 and A5 event
measurements and start the A2 event measurement.
Figure 2-80: A1 Threshold
Under the A2 Event Threshold, assume the LTE A2 RSRP Threshold value is set to 40 (Figure 2-81). If the UE
measures RSRP < -100 dBm, the UE will report the A2 event and the network will start the A1 and A5 event
measurements.
58
For A3 assume the Intra-Freq Handover A3 Offset value is set to 10 (Figure 2-82). If the UE reports an A3 event
(offset > 10*0.5 = 5 dB), the eNB may command the UE to hand off to the target intra-frequency cell.
For the A5 Event Threshold, assume the Inter-Freq Handover A5 RSRP Threshold1 value is set to 40 and Inter-
Freq Handover A5 RSRP Threshold2 value is set to 45 (Figure 2-83). If the UE reports an A5 event (RSRP of the
serving cell < -100 dBm, and the RSRP of the neighbor cell is > -95 dBm), the eNB may command the UE to hand
off to the target inter-frequency cell.
Assume that X2 is enabled (Figure 2-84). To ensure X2 handover is successful, the Mobility Management Entity
(MME) must support eNB configuration transfer and MME configuration transfer S1 message handling.
Figure 2-84: X2
With any changes to these configuration parameters, perform a warm reboot the eNB for the new configuration
to take effect.
The chart in Figure 2-85 shows the flow of these handoff event thresholds.
59
Figure 2-85: Flowchart of Handoff Event Thresholds
60
2.8.8 SAS Settings
Reference: Baicells SAS Deployment Guide
The Citizens Broadband Radio Service (CBRS) band covers 3.55-3.65 GHz. Operators must sign up with a
Spectrum Access System (SAS) provider for services to handle the dynamic frequency assignment and release
process. Baicells provides FCC Part 96 certified eNBs and UEs CBRS Service Devices (CBSDs) that can operate
within the FCC rules for CBRS. Initial Commercial Deployments (ICD) of CBRS SAS began in September 2019.
The Baicells eNBs use domain proxy (DP) to connect to the SAS server by leveraging the existing connection with
the OMC. All eNBs will need to be connected to the OMC in order to connect to the SAS.
The following are the minimum software levels for SAS to work:
• Nova-227/233/243: BaiBS_RTS_3.4.8 or later
• Nova-436Q: BaiBS_QRTB_2.0.5 or later
• Beta OMC: https://cloudcore.baicells.com (5.2.7)
NOTE: Legacy Gen 1 CPEs do not support SAS.
***This section covers only the eNB LTE > SAS Settings. Please refer to the SAS Deployment Guide for the full
instructions to implement CBRS SAS operation.***
In the eNB GUI, the LTE > SAS Settings menu opens by default as disabled. When you enable SAS, you will enter
the installation information and the Certified Professional Installer (CPI) credentials. The SAS vendor will control
the eNB's power and frequency point, as required by CBRS regulations. When SAS is enabled, the BTS Info >
Quick Settings for Band, Bandwidth, Frequency, and Power modify become invalid; the eNB will use the SAS
settings. Refer to Figure 2-86 and Table 2-32.
NOTE 1: The SAS settings in QRTB 2.0.x are slightly different. Refer to the SAS Deployment Guide.
NOTE 2: Legacy Gen 1 CPEs do not support SAS.
Figure 2-86: SAS
61
Table 2-32: SAS
SAS Settings
SAS Enable/Disable the SAS function
Install Param Config
category Either A or B according to the CBRS device designation. The eNB is Category B.
userid Optional: Enter a user ID associated with this SAS-enabled eNB.
fccid The CBRS FCC certification number for the device.
latitude Latitude of the eNB's location. Select auto to autofill the latitude based on GPS
data; otherwise, enter the latitude.
longitude Longitude of the eNB's location. Select auto to autofill the longitude based on
GPS data; otherwise, enter the latitude.
height Enter the antenna height, in meters. Range: 0-300 meters.
heightType Only Above Ground Level (AGL) may be selected
indoorDeployment Indicate whether the eNB is an Indoor or Outdoor (default) unit
Antenna Gain Set the eNB antenna gain. Range: -5 to 30 dBi.
LowFreq Enter the lowest frequency, in MHz, in the frequency range this eNB will use
HighFreq Enter the highest frequency, in MHz, in the frequency range this eNB will use
MaxEIRP Maximum Effective Isotropic Radiated Power that may be radiated from the
antenna. Range: 0-20 PSD dBm/MHz
antennaAzimuth Enter the antenna azimuth, in degrees. Default is 180°. Range: 0 - 359°
antennaDowntilt Enter the degrees of antenna downtilt. Default is 5°. Range: -90° to 90°.
antennaBeamwidth Enter the degrees of antenna beamwidth. Default is 65°. Range: 0 - 360°.
callSign The Unlicensed National Information Infrastructure (U-NII) radio band the
wireless operator uses. Range: 0 - 256 digits.
groupType Only INTERFERENCE_COORDINATION may be selected at this time.
groupID You must enter a group ID using letters, numbers, or special characters for the
groupType. You cannot leave the field blank. When you add the ID, it will be
displayed beneath this field.
CPI info
cpiId Enter the Certified Professional Installer's identification number.
cpiName Enter the Certified Professional Installer's name.
installCertificationTime Enter the date and time of installation: yyyy-mm-ddThh:mm:ssZ
62
2.8.9 Spectrum Analyzer
Reference: Baicells Spectrum Analysis User Guide
NOTE: This feature is not available in QRTB 2.0.x.
2.8.9.1 Description
The eNB Spectrum Scanning Mode feature helps you to see what is happening in the RF spectrum. It may be
used to analyze signal amplitude (strength) as it varies by signal frequency on the uplink. You can use this
information to determine the best frequency to use and to identify where there may be interference. Frequency
scanning encompasses both frequency and time information. The scan looks at the uplink data within a
configured frequency range for up to 20 MHz at a time.
IMPORTANT: As indicated by the feature name, when you put the eNB into spectrum scanning mode it is no
longer working like it normally does and UEs will not be able to attach to the eNB. Therefore, it is important to
remember to return the configuration back to normal mode when you are finished with the scan.
NOTE: When the eNB is operating in spectrum scanning mode, it uses the TDD subframe assignment of
"1" and the special subframe pattern of "7". These settings are restored to their previous values in BTS
Info > Quick Setting when the eNB is set back to normal operating mode.
2.8.9.2 Configuration
To initiate spectrum scanning, follow the steps below.
1. In the eNB GUI, go to LTE > Spectrum scanning mode (Figure 2-87).
2. Set the Mode field to Spectrum Scan Mode, and select the country code, band, and frequency range you
wish to analyze. The start and end frequencies must be within the same band, and there must be a 20
MHz gap between StartFrequency and EndFrequency.
3. Save the settings.
Figure 2-87: Spectrum Analyzer
63
4. Perform a warm reboot of the eNB.
5. Once the eNB finishes rebooting, in the GUI go back to LTE > Spectrum scanning mode and select Sweep
to start the scan. The sweep usually takes about one minute.
6. To see the scan results, click on Get Result. The results will appear at the bottom of the window.
Examples of results are shown below in section 2.8.9.3.
7. When you are finished, remember to set the Mode field back to Normal and perform a warm reboot to
exit the spectrum scanning mode and return to normal operating mode.
When initiating a scan, possible error messages you may see include:
• Frequency Lock error - Start and end frequencies entered in the GUI are out of range or not supported
• Gain error - Indicates an offset error in converting the baseband signal to RF signal strength
• Sync error - Indicates an issue with the I/Q data where the uplink subframe starting point cannot be
identified. Performing a warm reboot of the eNB may clear this error.
• PCI error - The Physical Cell Identifier (PCI) cannot be read from the GUI setting or is out of range.
2.8.9.3 Interpreting the Results

There are two types of scan results: frequency domain and time domain. For 20 MHz* spectrum, when you run
the scan you will get 2 uplink frequency domain results and 2 time domain results, where:
• First UL subframe = Combined UL subframes from the first half-frame (subframes 2 or 7)
• Second UL subframe = Combined UL subframes from the second half-frame (subframes 3 or 8)
*NOTE: The actual usable bandwidth is 18 MHz (20 MHz minus 2 MHz), because 1 MHz for the start
frequency and 1 MHz for the end frequency are omitted.
Figure 2-88 is an example of the spectrum scanning results for the frequency domain and the time domain.
Please refer to the Spectrum Analysis User Guide for additional information and examples.
64
Figure 2-88: Examples of Spectrum Scanning Results
2.8.10 UL PRB RSSI Report

Reference: Baicells Spectrum Analysis User Guide
NOTE: This feature is not available in QRTB 2.0.x.
The UpLink (UL) Physical Resource Block (PRB) Received Signal Strength Indicator (RSSI) Report feature may be
used when you think you have an interference issue. RSSI measures the total received wideband power, including
noise. When you run this report, the eNB looks for UE subframes not being used (no PRBs assigned, no traffic)
then takes the RSSI measurement.
65
By default this feature is disabled. In the eNB GUI, go to the LTE menu > UL PRB RSSI Report to enable it (Figure
2-89). Next, set the report period. This time period determines how often the report will run, and may be set
from 1 to 255 seconds. The feature will remain enabled and continue to run until you reset it to Disable; it will
not automatically shut off.
Figure 2-89: LTE > UL PRB RSSI Report
The report will display a graph in real-time at the bottom of the window, showing the total UL RSSI (in dBm)
along the y-axis for each PRB along the x-axis. Since there are multiple antenna elements, the Baicells eNB
reports each RF chain - ANT1 and ANT2. Only 20 MHz of bandwidth can be detected at one time. The report
shown in Figure 2-89 indicates a clean (no interference) environment. Figure 2-90 is a report where there is
interference.
Figure 2-90: With Interference
66
2.9 Reboot
To reboot the eNB go to the Reboot menu (Figure 2-91). You are presented with two options: Warm Reset and
Cold Reset.
• Warm reset - Does not power off the eNB to perform the reboot. It will retain all of the configuration
database.
• Cold reset - In the event you have an issue that cannot be recovered by a warm reset, you may need to use
cold reset. A cold reset will power off the eNB for a short period of time, and then it will start back up. It
will retain all of the configuration database.
NOTE 1: When you need to reboot the eNB, Baicells recommends that you collect logs on the eNB before
you reboot it. That data may be needed for troubleshooting.
NOTE 2: In a lab test environment, you can disable GPS Sync to reduce the reboot time.
Figure 2-91: Reboot
2.10 Logout
To log out of the eNB GUI, click on the Logout menu shown in Figure 2-92. You will automatically be logged out
of the GUI and presented with the login screen.
Figure 2-92: Logout Action
67
3 UE GUI
NOTE: The flow of screens shown in this section are based on a Cat4 UE. The GUI was changed for Cat6/7
UEs. For Cat6/7 screens and differences, please refer to Appendix A.
3.1 Computer Requirements

The computer requirements for the UE GUI are the same as for the eNB GUI, and repeated here in Table 3-1.
Table 3-1: Computer Requirements
Item Description
CPU Pentium 500 MHz or higher
Memory 128 MB RAM or higher
Hard Disk 50 MB available space
Operating System Microsoft: Windows XP, Windows Vista, or Windows 7
Mac: MacOSX 10.5 or higher
Screen Resolution 1024 x 768 pixels or higher
Browser Google Chrome 9 or later; Internet Explorer 7.0 or later; Mozilla Firefox 3.6 or later;
Safari 5 or later
3.2 Launching the GUI

When accessing the UE GUI locally, use an Ethernet cable to connect the computer Ethernet interface to a LAN
interface port on the back or bottom of the UE (example in Figure 3-1).
Figure 3-1: UE LAN Interface Example
68
You can also use a Web browser to log in to the Web GUI to configure and manage the UE.
NOTE: Another option is to enter your CloudKey in the GUI so that when the device powers up it will
automatically be added to your CloudCore account.
1. Set up the UE as instructed in the user manual for the device.

2. Open a Web browser, and enter:
a. http://192.168.150.1 (Gen 2 UEs),
b. http://192.168.254.1 (Gen 1 UEs), or
c. http://192.168.1.1 (Gen 1 UEs on firmware older than V1.0.3),
and then press Enter.
3. At the login window (Figure 3-2), enter the default user name (admin) and password (admin), and click
on Login. To protect your UE from unauthorized access, change the password after your first login. The
steps for password change are explained below Figure 3-3.
Figure 3-2: UE GUI Login
After you log in, the main menu is shown in the left navigation pane (Figure 3-3).
Figure 3-3: UE GUI - Main Menu
To change your password, go to System > admin (Figure 3-4). Enter the new password, and then re-enter the
new password to confirm it. The password may be 5 to 16 ASCII characters (letters, numbers, and special
characters). Baicells recommends using a mix of upper and lower case letters plus numbers. Click on Submit to
save the change. Select Save & Apply.
69
Figure 3-4: Change Password
3.3 Status
The UE GUI Status menu is like a dashboard about the UE. It provides information about the model, software
version, serial number, performance, and other usage data. The two sub-menus, Overview and Routes, are
explained in this section.
3.3.1 Overview
The Overview menu, sometimes referred to as a dashboard, provides system and device status information for
the given UE. Scroll down the page to see all of the fields (Figure 3-5 and Figure 3-6), which are described in
Table 3-2.
Figure 3-5: Overview Fields / Dashboard (1 of 2)
70
Figure 3-6: Overview Fields / Dashboard (2 of 2)
Table 3-2: Overview Fields

Current State
Connection State Indicates the connection status between the UE and the network – either Checking SIM,
Scanning, Registering, Acquiring IP, Connected, or Disconnected
Signal Intensity Indicates the strength of the signal between this UE and the serving eNB - either excellent,
good, general, bad, or severe. The UE unit typically displays 3 to 5 LEDs to indicate this level.
Lan State The connection between the UE and the local area network is either link up or link down
Devices Connected A count of the number of devices connected to this UE via LAN or Wireless LAN
Device Info
Product Name LTE ROUTER indicates the UE is operating as a router
Product Model Baicells’s hardware model name
Hardware Version The version of hardware for this UE unit
Software Version The version of software running on this UE
Software Build Time Baicells’s software build date
71
SN The UE’s unique serial number
LTE Status
USIM Status The Universal Subscriber Identity Module status is either available or not ready
LTE Mode The UE is operating in either Frequency Division Duplexing (FDD) or Time Division Duplexing
(TDD) mode
PLMN The Public Land Mobile Network (PLMN) to which the UE is connected
Cell ID The cell site ID to which the UE is connected
PCI The Physical Cell Identifier (PCI) ID is unique to each eNB. PCI indicates to which eNB device
the UE is connected. An operator can have multiple eNB devices in the same cell.
Earfcn The E-UTRA Absolute Radio Frequency Channel Number (band and frequency) within which
the UE operates
DL Frequency The frequency that the UE is using in the downlink (eNB to UE). In LTE, the carrier frequency
in the uplink and downlink is designated by the EARFCN, which identifies the LTE band and
carrier frequency.
UL Frequency The frequency that the UE is using in the uplink (UE to eNB). In LTE, the carrier frequency in
the uplink and downlink is designated by the EARFCN, which identifies the LTE band and
carrier frequency.
IMSI The UE’s International Mobile Subscriber Identity (IMSI) number, a unique
identification associated with the LTE network.
IMEI The UE’s unique International Mobile Equipment Identity (IMEI) number, a 15- or 17-digit
code that uniquely identifies mobile devices
Bandwidth The range of frequencies within the band the UE may use for transmitting a signal
RSRQ Reference Signal Received Quality – A value that reflects the signal quality of the received
reference signal. Indicates the noise floor.
SINR1 Signal-to-Interference-Plus-Noise Ratio 1 – A value that reflects the signal strength of the
signal received from one of the antennas in the eNB, expressed in decibels (dB)
SINR2 Signal-to-Interference-Plus-Noise Ratio 2 – A value that reflects the signal strength of the
signal received from one of the antennas in the eNB, expressed in decibels (dB)
DL MCS The downlink signal (eNB to UE) Modulation and Coding Scheme (MCS) currently being used.
This index represents the overall channel conditions and helps to indicate the maximum
throughput available to the UE.
UL MCS The uplink signal (UE to eNB) Modulation and Coding Scheme (MCS) currently being used.
This index represents the overall channel conditions and indicates the maximum throughput
available to the UE.
RSRP1 Reference Symbol Received Power 1 – A value that reflects the linear average over the
power contributions for the resource elements in one antenna that carry cell-specific
reference signals within the frequency bandwidth
RSRP2 Reference Symbol Received Power 2 – A value that reflects the linear average over the
power contributions for the resource elements in one antenna that carry cell-specific
reference signals within the frequency bandwidth
Throughput Statistics
DL The current downlink (eNB to UE) data throughput rate, in Kbps, for this UE in the last 3
minutes
72
UL The current uplink (UE to eNB) data throughput rate, in Kbps, for this UE in the last 3 minutes
Average The average DL and UL data throughput rates, in Kbps, for this UE in the last 3 minutes
Peak The peak DL and UL data throughput rates, in Kbps, for this UE in the last 3 minutes
Sum The total (sum) DL and UL data throughput rates, in Kbps, for this UE in the last 3 minutes
APN Status
APN Number Access Point Name (APN) is a gateway between a 3G/4G mobile network and another
computer network, frequently the public Internet
Enable Shows the status of APN 1, 2, 3, or 4 - enable or disable
MAC Address The APN’s Media Access Control address
Connection Type Indicates the type of local area network connection the UE uses to connect to the APN, e.g.,
dhcp for Dynamic Host Configuration Protocol
IP Address The Internet Protocol address of the APN to which the UE is connected
DNS Server The Domain Name Server used by the APN to which the UE is connected
LAN Status
MAC Address The Media Access Control address of the local area network
IP Address The Internet Protocol address currently used by the local area network
Netmask The subnet mask address currently used by the local area network
Devices List
Index An integer assigned to each device connected to the UE
Device Name The name of a device connected to the UE
MAC Address The Media Access Control address of a device connected to the UE
IP Address The Internet Protocol address of a device connected to the UE
Lease Time Amount of time a device’s IP address has been leased
Type Identifies whether or not the device got its IP address from the local area network DHCP
service
3.3.2 Routes
The Status > Routes sub-menu displays the current routing rules defined for the UE, including Address
Resolution Protocol (ARP) and Active IPv4-Routes (Figure 3-7). ARP is a protocol for mapping a Layer 3 network
IP address to each device’s Layer 2 Media Access Control (MAC) address on the local network.
The IP version rules will display according to how Network > Static Routes is configured. The fields in the Status >
Routes screen are described in Table 3-3 according to the example in the figure.
73
Figure 3-7: Routes
Table 3-3: Routes

ARP
IPv4-Address Current or most recently used Internet Protocol address of the target device
MAC-Address Current or most recently used Media Access Control address of the target device
Interface The local area network interface through which the IP address reaches the target device
Active IPv4-Routes
Network Name of the external network
Target IP address range for traffic on the external network
IPv4-Gateway The gateway address for IPv4 addresses
Metric Number of times the UE accessed the external network
Table Name of the routing table used by the gateway
3.4 Network
The Network menu opens to several sub-menus, as shown in Figure 3-8. This section explains each sub-menu.
Figure 3-8: Network Sub-Menus
74
3.4.1 LAN Settings
In the LAN Settings sub-menu (Figure 3-9), you can enter or change the IP address settings for the UE. By default,
the IP address is 192.168.254.1 (Gen 1 UEs) or 192.168.150.1 (Gen 2 UEs) and the subnet mask is 255.255.255.0.
If you edit how the address displays, for example to make the address easier to remember, make sure that the
address you choose is unique to your network. You will use the address to access the Web GUI.
You can bind an IP address to the UE based on its Media Access Control (MAC) address. If binding is configured,
the UE will provide IP addresses to devices on the LAN. DHCP dynamically assigns an IP address and other
network configuration parameters to each device on the network so they can communicate with other IP
networks.
When configured as a DHCP server, the UE automatically provides the TCP/IP configuration for the LAN clients
that support DHCP client capabilities. If DHCP services are disabled, you must have another DHCP server on the
LAN or each client must be configured manually.
To add a device to the setup list, click on ADD LIST. Table 3-4 describes each field. After entering the information,
click on SAVE & APPLY to activate the new settings.
Figure 3-9: LAN Settings
75
Table 3-4: LAN Settings

LAN Host Settings
IP Address Enter the UE’s IP address
Subnet Mask Enter the UE’s subnet mask address
DHCP Settings
DHCP Server Select the check box next to Enable to configure the UE as a DHCP server
Start IP Address Enter the starting IP address that the DHCP server may use for individual clients associated
with this UE. Must be a different IP address from the one set in the Network > LAN Settings,
but must be on the same network segment.
End IP Address Enter the ending IP address that the DHCP server may use for individual clients associated
with this UE. Must be a different IP address from the one set in the Network > LAN Settings,
but must be on the same network segment.
Lease Time Enter the lease time (in minutes). The range is 2 to 1440 minutes. The default is 720 minutes
(recommended).
Bundled Address List
Index List number
IP Address IP address of the device associating to the UE
MAC Address MAC address of the device associating to the UE
3.4.2 WAN Settings

The Network > WAN Settings are where you select or enter the Wide Area Network (WAN) Interface, Network
Mode, and Domain Name Server (DNS) information. Each sub-menu is described in this section.
3.4.2.1 WAN Interface

For the WAN Interface field, select LTE (Figure 3-10).
NOTE: The GUI may offer another WAN interface option of ETH for Ethernet port. That option is for special
use cases only and not typically included in the commercial UE GUI.
3.4.2.2 Network Mode

The Network Mode may be configured as either Network Address Translation (NAT) or Bridge, depending on
which UE model you are using (Figure 3-10). NAT is the default setting, but many operators use bridge mode.
NOTE: Former UE GUIs also allowed Router as a network mode setting. This option was not recommended
and was removed as of software version BaiCPE_V100R001C01B005SPC009.
3.4.2.2.1 NAT
NAT allows multiple hosts on a private network to access the Internet using a single public IP address. If you
want the UE network mode to use NAT, select the NAT pull-down menu option and click on SAVE & APPLY to
activate the settings.
76
Figure 3-10: Network Mode
3.4.2.2.2 Bridge
Selecting bridge mode disables NAT and allows the UE to function as a DHCP server without IP address conflict.
If you set the network mode to Bridge and click on SAVE & APPLY, and if you have enabled L2 under the VPN
settings, the system will prompt you to disable L2 first before making that change. Click OK, and go to the
VPN > L2 menu and select Destroy (covered in section 3.7 VPN). Refer to Figure 3-11.
Figure 3-11: Bridge Mode
77
3.4.3 WLAN Settings (Indoor UE Model EG2030C only)
The Baicells Cat6/7 Indoor UE, Atom ID06-6.5, has built-in 802.11 Wi-Fi capabilities, providing converged LAN
and Wireless LAN (WLAN) interfaces into one integrated LTE service. The Wi-Fi uses 2.4 GHz unlicensed spectrum.
For the EG2030C UEs, you can configure up to 4 independent Service Set Identifiers (SSID) on the local network.
This allows users to customize the settings for each SSID/WLAN differently.
When you go to the Network > WLAN Settings, the Wireless Overview window will display the 4 SSIDs that are
available to activate (Figure 3-12). To enable an SSID, click on SETTINGS. This will open a settings dialogue
window (Figure 3-13). Enter the settings per Table 3-5, and click on OK.
When you are returned to the Wireless Overview window, for the SSID you just configured select the blue
ENABLE button. The blue ENABLE button will turn to a gold DISABLE button, which means that SSID is now
enabled. To disable an SSID, select DISABLE.
Figure 3-12: Wireless Overview
78
Figure 3-13: SSID Settings
Table 3-5: SSID

Country Code Select the country code for the region where the UE is located, or select World Wide, which
means this configuration can be used anywhere.
Channel AUTO or wireless channel – If set the AUTO, the device will scan the network and start a Wi-
Fi association in a clear channel.
Ssid Service Set Identifier is auto-filled based on which SSID you selected SETTINGS for
Encryption Select the type of security encryption to use for this SSID, e.g., WPA2-PSK
Cipher Select the type of cipher to designate the encryption protocol, e.g., TKIP/CCMP
Password Password that users must enter to access this SSID/WLAN. Must be at least 8 characters
long.
Hidden Click on the check box to hide the password
Network Select the data path – either LAN or L2. If configured as L2, this SSID can bind to a
VLAN tag, so the traffic will add this VLAN tag for L2 isolation service. L2 isolation
service prevents communications between wired and wireless clients in the network.
Example:
79
3.4.4 Wifidog
The feature, Wifidog, is available on indoor Atom UEs and may be used to build wireless hotspots. The feature
works in cooperation with a remote authentication server. When Wifidog is enabled, Wi-Fi devices such as guest
users will have to be authenticated through the remote authentication server.
NOTE 1: The feature requires a connection to an authentication server to function.

NOTE 2: Wifidog is not recommended for Baicells UEs using Power over Ethernet (PoE).
You can create a whitelist to identify which website addresses, or URLs, users are allowed to reach. You can also
limit the number of times that a user may try to log in within a configured time period before failure to
authenticate times out. These settings help to avoid unauthorized use of the network.
In the GUI, go to Network > Wifidog (Figure 3-14). Notice the 3 tabs in the window - Basic Settings, Whitelist,
and Advanced Settings. In the Basic Settings tab, enable Web authentication and enter the authentication server
address and authentication code. Click on SAVE & APPLY before leaving the tab.
Figure 3-14: Wifidog
In the Whitelist tab you can add URL addresses to be whitelisted – that is, allowed – without the user having to
authenticate (Figure 3-15). Separate each URL with a comma (,). For the free certification equipment field, enter
the hotspot users' device MAC addresses. Use a comma (,) to separate each one. Click on SAVE & APPLY before
leaving the tab.
Figure 3-15: Whitelist
80
In the Advanced Settings tab (Figure 3-16), if you want all hotspot users to use the same authentication server
and login requirements, enter the server path information and set the Check internal field (maximum time, in
seconds), for logging in and the Client timed out field (maximum amount of time before failure to authenticate
times out, in minutes).
Figure 3-16: Advanced Settings
3.4.5 Static Routes

Routes specify over which interface and gateway a certain host or network can be reached. Static routes are
typically used in small local networks where the routing table entries are populated manually.
In the Network > Static Routes menu you can select the type of Packet Data Network (PDN) packets that may be
used to communicate with this UE: IPv4 or IPv6 (Figure 3-17).
NOTE: IPv6 is not currently supported in the Baicells CloudCore EPC. However, operators using their own
EPC that supports IPv6 can enable the Baicells UEs to pass IPv6 traffic.
To configure a static route for this UE, go to the Static IPv4 Routes or Static IPv6 Routes section of the window
and click on the ADD button. This will open the fields where you can input the target IP address, netmask,
interface type (APN, LAN, or WAN), and gateway address Figure 3-18). When finished, click on ADD again.
Use the Delete button to remove a static route.
81
Figure 3-17: Static Routes
Figure 3-18: Configure Static Routes
3.4.6 DMZ
In technology, the Demilitarized Zone (DMZ) refers to a firewall between incoming WAN traffic and the LAN to
which the UE is connected. Two basic DMZ methods are (a) using a single firewall, also known as the three-
legged model, and (b) using dual firewalls (Figure 3-19). These architectures can be expanded to create complex
architectures depending on the network requirements.
82
Figure 3-19: DMZ Methods
When the LAN has a DMZ server, you can enable DMZ for the UE so that packets from the WAN are sent directly
to the DMZ server before being discarded by the firewall. Optionally, you can enable Internet Control Message
Protocol (ICMP) redirect error messages, for which you enter the host server IP address. Refer to Figure 3-20
and Table 3-6. Activate any changes by clicking on SAVE & APPLY.
Figure 3-20: DMZ
Table 3-6: DMZ

DMZ Enable/disable the DMZ server
ICMP Redirect Enable/disable Internet Control Message Protocol (ICMP) redirect error messages for this UE
Host Address Enter the IP address of the host server. The address must be different from the IP address set
under Network > LAN Settings, but they must be on the same network segment.
3.5 LTE
Figure 3-21: LTE
The LTE menu is where you define the connection method for the UE to connect to the
network, the scan method for how the UE scans the available frequencies, APN
Management, and PIN Management (Figure 3-21). Each function is described in this
section.
83
3.5.1 Connection Mode
You can set the UE to connect automatically to the network (assuming the user has inserted a valid SIM card),
or you can set the connection mode to manual, where the user takes the action to connect to the network each
time (Figure 3-22). Click on SAVE & APPLY to activate the setting.
Figure 3-22: Connection Mode
3.5.2 Scan Method

The Scan Method determines which frequencies the UE’s routine scan of available frequencies will cover.
Scanning is a process of tuning to a specific frequency and measuring the simplest signal quality [e.g., Received
Signal Strength Indication (RSSI)]. As part of the cell selection and reselection process, the UE performs the
scan first and then selects a small number of candidate cells to go through the next step of measuring and
evaluating signals to select the best eNB to serve it.
Refer to Figure 3-23, Figure 3-24, and Figure 3-25 to view the Scan Method configuration fields based on which method
you select. Select one of the following options:
• Full Band – The UE will routinely scan all channels in the band, which can make the time it takes to connect
longer than the other modes. The band is dependent on the model of UE being used.
• Frequency Lock – You can specify which band(s) the UE will scan. After selecting this option, click on ADD LIST.
This will open a new window where you can input the band number and the preferred E-UTRA Absolute Radio
Frequency Channel Number (EARFCN). Click on ADD to add the settings.
• PCI Lock – Allows you to select the specific E-UTRA Absolute Radio Frequency Channel Number (EARFCN) and
Physical Cell Identifier (PCI). Click on ADD LIST to enter the settings (Figure 3-25). After entering the information,
click on ADD. You can add more than one PCI Lock list. The UE will scan the list for eNBs with the EARFCN and
PCI combination.
Click on SAVE & APPLY to activate the configuration.
Figure 3-23: Scan Method
84
Figure 3-24: Frequency Lock
Figure 3-25: PCI Lock
3.5.3 APN Management

An Access Point Name (APN) is the name of a gateway between a 3G/4G mobile network and another computer
network, frequently the public Internet. The UE supports 4 APN configurations. Go to LTE > APN Management
to configure the different services (Figure 3-26 and Table 3-7). Click on SAVE & APPLY to activate the data. The
bottom of the screen lists any APNs that have been defined for this UE.
NOTE: If you are using a Local EPC, typically you would configure the APNs in the core.
85
Figure 3-26: APN Management
Table 3-7: APN Management

APN Number Select the APN number – 1, 2, 3, or 4
Enable Select the check box next to Enable to enable this APN
APN Name Enter the name of this APN, as defined in the eNB configuration
Default Gateway To enable a default gateway to this eNB, select the check box next to Enable.
Apply To Select either No [None] Specified, TR069, SNMP, or SNMP+TR069 to indicate which protocol
may be used to collect information about the eNBs to which this UE may connect.
NOTE: SNMP will be supported on Cat6/7 UEs in a later release.
3.5.4 PIN Management

The purpose of the LTE > PIN Management menu is to give you the ability to require users to enter a personal
identification number (PIN) before they can use the UE. If a PIN has been enabled on the UE and a user enters
the wrong PIN, they will not be allowed to connect to the Internet through the UE.
86
The USIM Status field indicates if the UE’s SIM card is inserted and available. The USIM card status must show
“Available” before you can configure a PIN or access the Internet through the UE.
The PIN Verification field initially is not enabled. If you click on the check box next to Enable, it opens up the field
where you can enter the PIN number (Figure 3-27). The PIN number may be 4-8 digits, using numbers only. Be
sure to write down the PIN information in case you need it later!
Important: Once you enable the PIN and click on SAVE & APPLY, you will need to remember the PIN number and
enter it before you can modify the PIN Management settings.
Figure 3-27: PIN Management
To disable the PIN or to modify the PIN number, select the check box next to Modify PIN – Enable. Figure 3-28
shows the screen you will see when you select Modify PIN. You will have to enter the current PIN number, then
the new PIN number, and re-enter the new PIN number.
87
Figure 3-28: Modify PIN
3.6 Security
The Security menu is where you can enable a firewall for the UE and configure related security parameters
(Figure 3-29). Each sub-menu is described in this section.
Figure 3-29: Security
3.6.1 Firewall Settings

When you select the Security menu it opens to the Firewall Settings window (Figure 3-30). If you enable the
firewall by clicking on the check box, the other sub-menus under Security allow you to configure the firewall‘s
MAC filter, IP filter, and so forth.
88
Figure 3-30: Firewall Settings
3.6.2 MAC Filter

The Media Access Control Filter (MAC Filter) allows you to identify a list of devices either allowed to access or
forbidden from accessing the network (Figure 3-31). Select Enable to enable MAC filtering, and then determine
whether you will allow or forbid the defined MAC address(es) to access the network. The fields are described in
Table 3-8. To add a MAC Filter rule, under MAC List select ADD LIST. Enter the MAC address. To add more
addresses, click on ADD.
Figure 3-31: MAC Filter > Add List
Table 3-8: MAC Filter

MAC Filter Select the check box next to Enable to enable MAC filtering
Authority besides list Select allow to allow the MAC addresses in the MAC List, or select forbid to deny the MAC
items addresses in the MAC List
MAC Address Enter each MAC address to allow/forbid access to the UE, and click on ADD.
89
3.6.3 IP Filter
The Internet Protocol Filter (IP Filter) allows you to filter services based on the IP address of the source device.
You can define a list of devices either allowed to access or forbidden from accessing the network services. To
enable IP filtering, select the check box next to Enable. Click on ADD LIST to bring up the settings window. The
IP Filter settings enable you to configure the protocol and IP address ranges, as shown in Figure 3-32 and
explained in Table 3-9.
Figure 3-32: IP Filter
Table 3-9: IP Filter

IP Filter Select the check box next to Enable to enable IP filtering
Service Type Select the type of service, either custom, FTP, SSH, TELNET, SMTP, HTTP, POP3, HTTPs, HTTP
Proxy to allow to or forbid from the UE
Protocol Select the type of data protocol, either ALL, TCP, UDP, TCP&UDP, or ICMP to allow to or
forbid from the UE
Source Address Range Enter the IP address range for the source device(s) in the format of x.x.x.x or x.x.x.x/mask.
The mask value may be 0 or 32.
Source Port Range Enter the port number range for the source device in the format of 1000 to 1500, or 1000.
Destination Address Enter the IP address range for the destination device(s) to be filtered, in the format of
Range x.x.x.x or x.x.x.x/mask. The mask value may be 0 or 32.
90
Destination Port Range Enter the port number range for the destination device(s) to be filtered, in the format of
1000 to 1500, or 1000.
Status Allow or forbid the IP Filter list
3.6.4 URL Filter

The Uniform Resource Location Filter (URL Filter) allows you to define a list of URL addresses that the user is
forbidden from accessing. When you set the filter to Enable, a Settings window appears. Enter the specific URL
address users cannot access, as shown in Figure 3-33. To add more URL addresses, click on ADD. After entering
the addresses and saving, the URL(s) you entered will appear in the URL List.
Figure 3-33: URL Filter
3.6.5 Port Forwarding

When Network Address Translation (NAT) is enabled on the UE under the Network > WAN settings, you can
redirect a communication request from one address and port number combination to another. Only the IP
address on the WAN side is open to the Internet. If a computer on the LAN is enabled to provide services for
the Internet (for example, work as an FTP server), configuring the Port Forwarding settings is required so that
all accesses to the external server port from the Internet are redirected to the server on the LAN.
To add a port forwarding rule, click on the check box next to Enable, and click on ADD LIST as shown in Figure
3-34. To add more lists, click on ADD. The fields are explained in Table 3-10.
91
Figure 3-34: Port Forwarding
Table 3-10: Port Forwarding

Service Type Select the type of service, either Custom, DNS, FTP, IPSec, POP3, SMTP, PPTP, Realplay, SSH,
HTTPs, SNMP, SNMP Trap, Telnet, TFTP, or HTTP
Protocol Select the type of data protocol, either TCP, UDP, or TCP&UDP
Remote Port Range Enter the port number range for the remote device in the format of 1000 to 1500
Local Host Enter the local host IP address. The address must be different from the IP address that is set
for the LAN Host Settings parameter, but they must be on the same network segment.
Local Port Enter the local port number. Range is 1 to 65,535.
3.6.6 Port Triggering

The Port Triggering sub-menu is a configuration option on a router - in this case, the UE - configured for Network
Address Translation (NAT) under Network > WAN settings. When an application uses a trigger port to build a
connection, the UE will forward the data to the forward port. Refer to Figure 3-35.
92
Figure 3-35: Port Triggering
3.6.7 ALG
The Application Layer Gateway (ALG) sub-menu provides a security component that augments a firewall or the
Network Address Translation (NAT) used by the UE. It allows customized NAT traversal filters to be plugged into
the gateway to support address and port translation for certain application layer control/data protocols such as
FTP, H.323 ALG, SIP, and PPTP. You can enable the different types of application protocols by clicking on the check
box next to any you wish to enable (Figure 3-36).
Figure 3-36: ALG
93
3.6.8 UPNP
The Universal Plug & Play (UPnP) function provides a set of networking protocols that allows device-to-device
networking on a local network. When UPnP is enabled, devices seamlessly discover each other’s presence on
the local network and attach dynamically to one another and to network services. Typically, UPnP is reserved for
residential or private networks and not used in an enterprise environment as it may consume too many
resources in a network with many devices.
In the Security > UPNP menu, click on the check box next to Enable UPnP to allow it to function on this UE (Figure
3-37). Once enabled, any redirects of traffic will display in the Active UPnP Redirects section of the window.
Figure 3-37: UPNP
3.6.9 Attack Protection

The Attack Protection settings provide an additional security measure that helps prevent computer hacker
attacks such as TCP SYN FLOOD, UDP FLOOD, and IMCP FLOOD for devices connected to the network through a
Baicells UE. In the Security > Attack Protection window (Figure 3-38), click on the check box next to TCP, UDP,
and ICMP single and/or multiple connections. When you click the check box, the field on the right becomes
editable. Accept the default timer value, in seconds, or enter a value for each type of attack protection you
enable.
94
Figure 3-38: Attack Protection
3.7 VPN
Figure 3-39: VPN Menu
The Virtual Private Network (VPN) menu (Figure 3-39) enables you to configure a
connection between the UE and a VPN, e.g., to access a corporate network when
telecommuting for work. You can enable a Layer 2 Tunneling Protocol (L2TP) gateway or a
Layer 2 network connection to the VPN. Each sub-menu is described in this section.
3.7.1 IPSec
The Internet Protocol Security (IPSec) settings are for a network protocol suite that authenticates and encrypts
data packets sent over a network. IPsec includes protocols for establishing mutual authentication between
agents at the beginning of the session and negotiation of cryptographic keys to use during the session. IPsec can
protect data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-
network), or between a security gateway and a host (network-to-host).
At the VPN > IPSec menu, click on ADD POLICY to configure the settings for one or more IPSec policies for the
UE. Enter the policy name, remote gateway, local and remote subnets, and pre-shared key for the VPN
connection. Refer to Figure 3-40 and Table 3-11.
95
Figure 3-40: VPN > IPSec
Table 3-11: VPN > IPSec

Enable Click on the check box to enable IPSec
Policy Name Enter a policy name using up to 32 characters
Remote Gateway IP address of the remote gateway
Local Subnet Optional: IP address of the local subnet
Remote Subnet Optional: IP address of the remote subnet
Pre-Shared Key Up to 128 characters
Click on ADVANCE SETTINGS to configure additional IPSec parameters such as key exchange version, IKE
encryption, etc. Refer to Figure 3-41 and Table 3-12.
96
Figure 3-41: ADVANCE SETTINGS
Table 3-12: Advance IPSec Settings

Key Exchange Version Internet Key Exchange (IKE) encryption method version 2 or version 1. IKE is a protocol used
to ensure security for virtual private network (VPN) negotiation and remote host or network
access.
Negotiation Mode Initiator mode or Responder mode
IKE Encryption 3des, aes128, aes192, or aes256
IKE DH Group modp768, modp1024, modp1536, modp2048, or modp4096
IKE Authentication md5, sha1, sha256, sha384, or sha512
ESP Encryption des, 3des, aes128, aes192, or aes256
ESP DH Group none, modp768, modp1024, modp1536, modp2048, or modp4096
ESP Authentication md5, sha1, sha256, sha384, or sha512
Left Identifier 1-28 characters
Right Identifier 1-28 characters
KeyLife 120-604800 seconds
IKELifeTime 120-604800 seconds
RekeyMargin 120-604800 seconds
Dpdaction none, clear, hold, or restart
Dpddelay 1-300 seconds
Keyingtries 0 means forever
97
3.7.2 General VPN
The VPN > General VPN menu offers 3 options. The first option allows you to set up a Layer 2 Tunneling
Protocol (L2TP) gateway for the VPN connection. An L2TP gateway provides an unencrypted tunnel between
the UE and the VPN. All Internet traffic including Internet service provider (ISP) services will pass through the
VPN. If you plan to use L2TP, in the Settings window click on the check box next to Enable (Figure 3-42). Refer
to Table 3-13 for a description of each field.
Figure 3-42: General VPN > L2TP
Table 3-13: General VPN > L2TP

VPN Click on the check box to enable VPN
Protocol L2TP
Default GW Click on the check box to enable a default gateway
Server IP Server IP address
User Name Enter a user name
Password Enter a password
IPSec Encryption Enable or disable
Remote Subnet Remote subnet IP address
Pre-Shared Key 1-128 characters
98
The second option is Point-to-Point Tunneling Protocol (PPTP), which is an obsolete method for implementing
VPNs. It became obsolete because of the many security issues it presented. PPTP uses a TCP control channel and
a generic routing encapsulation tunnel to encapsulate PPP packets. Refer to Figure 3-43 and Table 3-14 to
configure PPTP.
Figure 3-43: General VPN > PPTP
Table 3-14: General VPN > PPTP

Protocol PPTP
User Name Enter a user name
Password Enter a password
MPPE Select the check box to enable Microsoft Point-to-Point Encryption
The third option is Generic Routing Encapsulation (GRE), which is a tunneling protocol developed by Cisco
Systems. GRE encapsulates a wide variety of network layer protocols inside virtual point-to-point links over an
IP network. Refer to Figure 3-44 and Table 3-15: General VPN > GRE to configure GRE for the VPN.
Figure 3-44: General VPN > GRE
99
Table 3-15: General VPN > GRE

Protocol GRE
Local IP Local IP address
Remote IP Remote IP address
3.7.3 L2
Virtual Extensible Local Area Network (VxLAN) is a network virtualization technology that attempts to address
the scalability problems associated with large cloud computing deployments. Baicells’s L2 VPN technology is
based on VxLAN and must be coordinated with the Baicells CloudCore EPC. L2 will not work if you are using
another vendor’s EPC.
To configure L2 VPN, go to VPN > L2 and click on SET UP (Figure 3-45). The screen will show “Is Setting Up” to
indicate the connection is being established. The resulting screen for a successful connection will show Last
Command/Result of “set up/OK”.
When the UE starts an L2 VPN service, all APN services defined under LTE > APN Management will be activated
and the UE will work like a Layer 2/Layer 3 switch (Figure 3-46).
To release the L2 VPN connection, select DESTROY. The screen will report “Is Destroying”, and then it will
return to the Set Up screen.
Figure 3-45: Set Up L2
100
Figure 3-46: APN Status
3.8 System
The System menu provides several sub-menus related to the Network Time Protocol (NTP) server,
administrator account, WEB settings, TR-069, and SNMP settings, and the ability to restore/update, diagnose,
or reboot the UE. Each sub-menu is explained in this section.
3.8.1 NTP
The operator may configure up to 4 NTP servers to provide correct time-of-day to the network devices. In the
UE GUI you can establish the time zone that the UE is in, and enable NTP client to use any of the defined NTP
services or select one or more specific NTP servers the UE will use for time synchronization with the network
(Figure 3-47). Use the SYNC WITH BROWSER button to refresh the local time that is displayed.
Figure 3-47: NTP
101
3.8.2 Account
The System > Account menu may be used to change the UE’s administrative login password (Figure 3-48). The
new password must be re-entered to confirm it. You can hover over the green icon at the end of the field to
select Reveal/hide password. The admin password must be 5 to 12 characters. Baicells recommends using a
combination of upper- and lower-case letters and numbers.
Figure 3-48: Account
3.8.3 WEB Setting

The WEB Setting provides the ability to monitor and manage the UE over the Internet using a Web
management application. This is especially helpful when troubleshooting issues remotely, e.g., a user calls in
for technical assistance. To configure, refer to Figure 3-49 and Table 3-16.
Figure 3-49: WEB Setting
102
Table 3-16: WEB Setting

HTTP Select the check box next to Enable to log in to an HTTP Web address
HTTPPort Enter the HTTP port number to be used. Range is 80 to 65,535. Default is port 80.
HTTPS Select the check box next to Enable to log in to an HTTPS Web address
Redirect HTTPS Select the check box to allow HTTP addresses to be redirected to more secure HTTPS
addresses
Allow HTTPs Login From Select the check box next to Enable to log in to an HTTPs Web address from the WAN
WAN
HTTPSPort Enter the HTTPS port number to be used. Range is 80 to 65,535. Default is port 80.
3.8.4 TR-069
If your network operates using a TR-069 auto-configuration server (ACS), the ACS will automatically provide
the UE parameters. If you enable the ACS parameters on both the ACS and the UE, you do not need to set
other parameters on the UE itself. Use the TR069 sub-menu to implement the TR-069 function for the UE, as
shown in Figure 3-50 and explained in Table 3-17.
Figure 3-50: TR-069
Table 3-17: TR069 Settings

TR069 Select the check box next to Enable to enable a TR-069 auto-configuration service (ACS)
ACS Type Select URL or DHCP to identify the source of the ACS service. When you select URL, the next
field (ACS Address) appears.
ACS Address Enter the server Web address
User Name Enter the user name to access the ACS server
Password Enter the password to access the ACS server
CPE periodic reporting Select the check box next to Enable to enable the UE to periodically check with the ACS
103
server for new software
Periodic If you enabled CPE periodic reporting, input how often the UE should check the ACS server
for new information. The range is 20 to 86,400 seconds.
CloudKey Enter the operator's unique CloudKey . When the device powers up the first time it will
automatically be added to the operator's CloudCore account.
NickName Optional – enter a nick name to identify the server
3.8.5 SNMP
As of BaiCE_AP_2.1.4_NA release, you can enable SNMP on individual UEs to allow the Network Management
Service (NMS) to collect event logs, alarm logs, and other data. See Figure 3-51. After clicking on the check box
next to SNMP, complete the fields to configure this capability. Refer to Table 3-18 for a description of each field.
Figure 3-51: SNMP
Table 3-18: SNMP

SNMP Enable Simple Network Management Protocol by clicking the check box. To disable, uncheck
the check box.
NMS Address NMS server IP address
NMS Port NMS server port number
Listening Port Peer port number for the UE to listen to packets from the NMS
Trap Community Public or private - identifier to distinguish read/write permissions for data from the CPE to
the NMS
104
Version Select the SNMP version level you wish to implement - V1&V2c (for SNMPv1+SNMPv2c) or
V3 (for SNMPv3)
Read Community Public or private. Read-only community name.
RW Community Public or private. Read/Write community name.
3.8.6 Restore/Update
Use the System > Restore/Update menu to reset the UE or to update the firmware.
3.8.6.1 Restore
“Restore” in this case means to reset the UE to its factory default configuration settings (Figure 3-52). To
initiate a restore action, in the System > Restore/Update window click on PERFORM RESET.
Figure 3-52: Restore/Update
3.8.6.2 Update
To update (upgrade) the UE to a different firmware version, first download the image file from the Baicells
support website (Baicells > Support > Downloads) and save it to your computer. Next, under the Flash new
firmware image part of the Restore/Upgrade window, determine if you want to keep the current configuration
settings on the UE (Figure 3-52). If you do, select the check box next to Keep settings. Click on Choose File to
navigate to the new image file on your computer, and then click on FLASH IMAGE to initiate the upgrade. After
the upgrade the UE will restart automatically, running the newer version of code.
Caution: Do not power off the UE or disconnect it from the computer during an upgrade.
To upgrade a specific module, meaning to apply a patch to the current firmware, first download the image file
from the Baicells support website (Baicells > Support > Downloads) and save it to your computer. In the
System > Restore/Update window under the Module upgrade section, click on Choose File (Figure 3-54).
Navigate to the new module image file, and then click on FLASH IMAGE to initiate the patch upgrade.
105
3.8.7 Diagnosis
The System > Diagnosis menu provides 3 diagnostic tests that can be useful for troubleshooting issues with
Internet connectivity: Ping, TraceRoute, and Iperf (Figure 3-53). Each test is explained in this section.
Figure 3-53: Diagnosis
3.8.7.1 Ping and TraceRoute

Running a ping test will send a data packet of a specified size from the UE to a target IP address to determine if
there is a connection and if there is any packet loss.
Running a traceroute test will display the route a packet takes from the UE to a target IP address, and the time
in milliseconds between hops. The route may indicate causes of delay in transmission.
To initiate a ping or traceroute test, under Method select the radio button next to the test name. Once you enter
the ping or traceroute information in the fields (Figure 3-54 and Figure 3-55), click on the blue Ping or Traceroute
button to run the test. Each time you run a ping or traceroute, the bottom of the screen will show the progress
(e.g., “Testing… please wait!”) and the results will then display. Refer to Table 3-19 for a description of each field.
Figure 3-54: Ping
106
Figure 3-55: TraceRoute
Table 3-19: Ping and TraceRoute

Method Select the radio button for Ping or TraceRoute
Target IP Enter the target IP address to ping or perform a traceroute
Interface Select DEFAULT (APN1) or APN1, 2, 3, or 4 to diagnose the APN connection.
Package Size Enter the size of data packet to send, in bytes. Range is 1-9000. Default is 56 bytes.
Timeout Enter the length of time for the ping test or traceroute to run, in seconds. Ping range is 1-10.
Default is 10 seconds. Traceroute range is 1-60. Default is 10 seconds.
Count For ping, enter the number of times you want the ping test to try sending the data. Range is
1-10. Default is 4 times.
Maximum Hops For traceroute, enter the maximum number of hops (network nodes) the data packet should
take to reach the target IP or domain address. Range is 1-30. Default is 30.
Results (Ping) Displays the details of the ping test, showing the target IP address, the number of data bytes
sent, number of packets transmitted, number of packets received, and percentage of packets
lost
Results (TraceRoute) Displays the details of the traceroute test, showing the target IP, the maximum number of
hops, the packet size, and the time between hops
3.8.7.2 Iperf
The Iperf tool under System > Diagnosis measures the throughput of either Transmission Control Protocol (TCP)
or User Datagram Protocol (UDP) packets between the UE and a target IP address. The results are useful for
assessing network performance and for troubleshooting issues.
107
Referring to Figure 3-56, to run the iperf test select the Method of Diagnostics by clicking on the radio button
next to Iperf. Enter the iperf settings per the field descriptions in Table 3-20. Click on the IPERF button. The
results will appear at the bottom of the screen.
Figure 3-56: Iperf
Table 3-20: Iperf

Settings
Protocol Select the data packet protocol type, either TCP or UDP, for the test
Target IP The target, reachable IP address. Default is 192.168.23.100.
Port The target port number. Range is 1024 to 65,535. Default is 5001.
Time Enter the amount of time (in seconds) for the Iperf tool to measure the data throughput.
Range is 10 to 86,400 seconds. Default is 30 seconds.
Data Length Data length measured in bytes
Bandwidth Send/receive data rate, in kbps
Result
Status -
Uplink Speed Data throughput on the uplink
Downlink Speed Data throughput on the downlink
3.8.8 Reboot
Use the Reboot menu to perform a reboot of the UE, as shown in Figure 3-57. It can take several minutes for
the reboot to complete. After it reboots, the UE GUI will display the login screen.
Caution: The reboot action will disrupt UE service.
108
Figure 3-57: Reboot
3.9 Logout
When you click on the Logout menu, you are automatically logged out of the UE and returned to the LOGIN
screen (Figure 3-58).
Figure 3-58: Logout
109
4 CloudCore
The Baicells CloudCore services include the core LTE functions mentioned in section 1 of this document, plus the
Operations Management Console (OMC) for network management and the Business Operations & Support
System (BOSS) for subscriber management. This section covers the CloudCore System menu, the OMC, and BOSS.
To use CloudCore, operators are charged a monthly rate based on the number of subscribers who were active
for at least 3 days during the month. The first time an operator's administator logs in to their CloudCore account,
they are asked to enter or verify basic company information and provide a credit card number. More about billing
plans is covered in section 4.3.1.
4.1 Client Computer Requirements

Table 4-1 describes the minimum requirements for the client computer you use to access the Baicells CloudCore
Operations Management Console (OMC) and Business Operations Support System (BOSS) applications.
Table 4-1: Client Requirements
Item Description
CPU Higher than Intel Core 1GHz
Memory Greater than 2G RAM
Disk No less than 100 MB space available
Operating System Microsoft: Windows XP, Windows Vista, or Windows 7
Mac: MacOSX 10.5 or higher
Screen Resolution At least 1024 x 768 pixels
Browser Google Chrome 47 or higher (recommended)
Mozilla Firefox 47 or higher
4.2 Getting Started
4.2.1 Accessing CloudCore

To access the Baicells CloudCore, as an operator you first need to sign up for a CloudCore account. Follow the
steps below to get signed up. Only one contact person from each operator is necessary to establish the
primary account as the operator’s administrator. Once the operator’s administrator is added, s/he can add
other users. Refer to section 4.2.2 CloudCore Users.
Open a web browser, and enter the CloudCore address: https://cloudcore.cloudapp.net/cloudcore/
Click on the Sign up button (Figure 4-1).
1. Complete the mandatory fields (Figure 4-2), and again click on Sign up.
2. You will receive an email from CloudCore. In the email, click on the CloudCore link to go to the Login
page. Enter your login user name (email address) and password to authenticate. You are now ready to
start using CloudCore!
110
Figure 4-1: CloudCore Sign up and Login Page
Figure 4-2: Sign up Fields
Refer to the Getting Started BaiTip on the website: https://na.baicells.com/getting-started/
111
4.2.2 CloudCore Users
CloudCore users are referred to as administrators, or admins. As an admin, in OMC and BOSS you can configure
role sets and user groups as well as add other administrative users. If a user is not assigned to a user group, the
user will be placed in a default group. Both OMC and BOSS have default user groups. Administrative users are
only assigned in OMC, meaning if you create a user account in OMC you automatically have the same user
account in BOSS.
4.2.3 Navigation Pane

After logging in, and assuming your primary administrator has established the billing information per section
4.3.1, the CloudCore web page defaults to the OMC menu. Use the arrow icon under the OMC name in the top
bar to open or close the navigation pane (menus) on the left (Figure 4-3).
Figure 4-3: Navigation Pane
In the upper right corner, you will see “Welcome, <your name>”. Use the drop-down menu next to your name
to Change password, Lock screen, or Logout (Figure 4-4).
NOTE: The purpose of the CloudKey field is explained in section 2.7.2.
Figure 4-4: CloudCore Welcome Menu
112
4.2.4 GUI Icons
You can hover over an icon in a GUI window to see what its function is. Table 4-2 is a compiled list of all the icons
that are used in the GUI windows, with a description of each.
Table 4-2: GUI Icons
Icon Description
Search for a specific device or item.
Add a new device/item or a new task.
Import multiple devices at one time, or upgrade file.
Export file to the local computer.
Edit/Modify the information for a device/item.
Delete a device/item or a task.
View the information for a device/item.
The operation (action) menu for a device/item
Synchronize the device information on the OMC
Reboot a device.
Download a file.
The device is operating as expected (normal).
The device is offline.
Display settings – e.g., to move columns in a window around, to customize the
window to meet your needs, or to edit an existing entry
/ Lock/unlock the screen.
Refresh the displayed results.
Reselect a template for the alarm view.
Filter results according to alarm type and severity.
/ Maximize/restore the screen.
Copy an existing user to create a new user having the same role set permission as the
selected user.
Reset the login password of the user.
As an administrator, force a user to log out.
Unlock a user who was locked out after exceeding the threshold for the maximum
number of times a user can enter a wrong password.
113
4.2.5 Help
The Help > About menu in OMC and BOSS shows the application's software version (Figure 4-5).
Figure 4-5: Help > About
4.3 System
The CloudCore System menus, in this case affecting all CloudCore users for the account, provide operator-specific
information, some of which is view-only and some of which may be edited by an administrator (Figure 4-6). Each
menu item is explained in this section.
NOTE: Some CloudCore menus/ functions are limited to Beta trial operators as Baicells tests new features.
4.3.1 Billing
The Billing menu presents the operator's billing contact information, credit card on file, and present and past
invoices (Figure 4-7).
114
Figure 4-7: Billing Menu
To add credit card information from this menu, under the Credit Card section of the window click on + Add and
enter the card information. To include more details such as cardholder name, address, etc., click on More Options
(Figure 4-8). Once added, the credit card entry will be listed and you can use the Operations actions to View,
Modify, Delete, or Set as Default.
Figure 4-8: Add Credit Card
Where the window says Upcoming Invoice, you will see the due date, active user count, and dollar amount owed.
When you click on the User Count number, it takes you to the user details (Figure 4-9).
115
Figure 4-9: Upcoming Invoice
In the Invoice section of the Billing window you will see the current invoice information. To view historical
invoices, click on View more invoice. The details include the invoice date, who it was sent to, active user count,
and so forth (Figure 4-10).
Figure 4-10: Invoices
If you click on the User Count hyperlink, it opens the detail page showing the user names, IMSIs, and usage days
that were included in the invoice (Figure 4-11). The URL column provides a way to view and download the invoice
details provided by the Stripe service (Figure 4-12).
116
Figure 4-11: User Count
Figure 4-12: URL > Stripe
4.3.2 Invoice
The CloudCore Invoice menu is basically a dashboard for your Baicells invoice information (Figure 4-10). The
Statistics tab displays the total billing amount, how much of that total has been paid, and how much is unpaid
during the period of time which you select.
117
Figure 4-13: Invoice
The List tab is simply a list of all the invoices you have received from Baicells, with the most recent on top (Figure
4-14).
Figure 4-14: List Tab
Under Operations, if you click on the Details icon the window will display a summary of that specific invoice and
a list of payments that have been made (Figure 4-15).
118
Figure 4-15: List Tab > Operations > Details
4.3.3 Security
The CloudCore System > Security menu is used to add CloudCore administrators to the operator's account. The
operator's existing CloudCore administrative users will be listed in the User Management window (Figure 4-16).
Use the Operations actions to unlock, delete, or reset a user's password.
Figure 4-16: (Administrative) User
When you select Reset Password, the system will ask if you are sure you want to take that action. Click on OK if
you want to continue. The system will return a message stating that the user will receive an email with a link,
and will have 30 days to reset the password (Figure 4-17). The user’s password may include A-Z, a-z, 0-9, dash
(-), and underscore (_) characters.
Figure 4-17: Reset Password
119
To add a new administrative user, click on the + Add icon to open the configuration window (Figure 4-18). Fields
with a star next to them are mandatory. If a user is not assigned to a user group, they will automatically be
placed in the default group.
Figure 4-18: Add Administrative User
4.3.4 Security Rule

Selecting System > Security Rule allows you to set up rules concerning administrative user access to the
operator's CloudCore account. Click on Edit to take any of the following actions (Figure 4-19).
• Login Limit
o Limit Single User Login - if you toggle the field to enable this feature, only one administrative
user will be able to access the operator's CloudCore account
o Limit User Login Switch - enable if you want to limit the maximum number of users who can
access the operator's CloudCore account
o User Login Max Number - enter the number of logins permitted
• Access Rule
o IP White List - enable if you want to create IP address white lists to limit which IP addresses may
log in to the operator's CloudCore account.
o Start IP - when IP White List is enabled, enter the starting IP address
o End IP - when IP White List is enabled, enter the ending IP address
120
Figure 4-19: Security Rule
4.3.5 Logs
From the CloudCore System page, selecting System > Logs opens the Operation log window. An operation log is
simply an account of events that have taken place in the operator’s CloudCore account (Figure 4-20). Logs
represent all CloudCore user activity, and are useful for a quick look-up of activities across all users. The latest
log appears on the top of the list.
Figure 4-20: Logs
121
4.4 OMC
When you click on the OMC module in CloudCore, you will see menus in the left navigation pane (Figure 4-21).
Each OMC menu item is explained in this section.
See, also, the Getting Started BaiTip: https://na.baicells.com/getting-started/
Figure 4-21: OMC Menus
4.4.1 Dashboard
The OMC dashboard appears when you enter the OMC module. The dashboard provides operator personnel
with a summary of network status, statistics, and performance data. This at-a-glance feature helps
administrators to grasp the health of the overall network and to quickly identify any issues.
4.4.1.1 Display
If you click on the display icon in the upper right a pop-up window appears (Figure 4-22). You can select
which dashboard elements you want to see, and you can move their position in the window using the up and
move to top icons.
Figure 4-22: Display
122
4.4.1.2 Alarms
The top of the dashboard window displays the number of active system alarms. The types of alarms reported by
OMC include communications, QoS, processing error, equipment, and environmental alarms. Alarms are
categorized into 4 classes: Critical, Major, Minor, and Warning. Critical alarms are incidents that can cause system
outages, and should be attended to immediately. Major alarms are incidents that can cause poor or degrading
quality of service for subscribers, and therefore should be addressed as soon as possible. Minor alarms indicate
a possible issue that needs to be investigated but will not disrupt service. Warnings are used to indicate errors
that probably need to be corrected or at least monitored, but may not require any action.
To get more information about the alarms, you can either click on the double arrows, which will jump you to the
Alarm > Query menu, or click on the down arrow to display the details (Figure 4-23). If you click on an alarm
category, for example the red circle showing the number of critical alarms, that will also jump you to the Alarm >
Query window. Please refer to section 4.4.4 for a description of the alarm information.
Figure 4-23: Dashboard - Alarm Query
123
4.4.1.3 Statistics
The Statistics section of the dashboard pertains to all of the operator’s eNBs and UEs. The graphs represent
active/inactive eNBs (transmitting or receiving data), online/offline eNBs, connected/disconnected UEs, UL/DL
performance throughput, physical resource block (PRB) utilization, a UE count, and lists showing the eNBs and
the UEs in the operator's network (Figure 4-24 and Figure 4-25).
The difference between active/inactive and online/offline eNBs is active represents the eNBs transmitting or
receiving data, inactive means the eNBs that are online but not currently active; online shows the number of
eNBs that are operational but not transmitting or receiving data; and offline means the eNB is not connected to
the network or otherwise unavailable.
Throughput is a measure of the average uplink and downlink data traffic, in Mbps, being transmitted over the
last 5 minutes across all eNBs in the network. PRB Utilization shows the average number of subcarriers allocated
to users across all eNBs over the last 5 minutes, an indicator of how much of available system resources are
being utilized. Notice under the graphs that you can slide the timestamp under from left to right or right to left
to see day-by-day data for 7 days at a time.
Figure 4-24: Statistics (1 of 2)
Figure 4-25: Statistics (2 of 2)
124
4.4.2 eNB
The eNB menu provides functions that are important to monitoring and maintaining all eNBs in the operator's
network (Figure 4-26). Each of these functions is explained in this section.
Figure 4-26: eNB Menu
4.4.2.1 Monitor
The Monitor function allows you to see information about each eNB that is configured in your network (Figure
4-27). Use the scroll bar near the bottom of the window as needed to see all of the column headers. You can
adjust the column widths by hovering your cursor on the vertical lines that separate each column.
To select which types of information is displayed in your view of the Monitor window, refer to section 4.4.2.1.1.
Table 4-3 provides a description of all Monitor information.
Figure 4-27: Monitor
Table 4-3: eNB Monitor Fields

Operations When you highlight the row of an eNB and click on the icon under Operations, 3 options
are presented: Information, Settings, More. The Operations functions are described in
section 4.4.2.1.2.
<Untitled> The column that just shows a filter icon at the top presents an eNB's present status:
Connected (blue) to the network or Disconnected (red) from the network.
Alarm Provides the color code of the severity, as well as the number of alarms at each level
Serial Number eNB serial number
Cell Name Name given the eNB
IP Address IP address of the eNB
IPSEC Address IP address of the IPSec gateway
MAC Address MAC address of the eNB
125
Cell ID Logical Cell ID to which this eNB is assigned
PCI Physical Cell Identifier (PCI), or Layer 1 identity, is an essential configuration parameter of
a radio cell that uniquely identifies each cell site in the wireless network. PCI planning is
crucial for quality of service (QoS).
Active Status The eNB is active (operating) or inactive (not operating)
MME Status The Mobility Management Entity (MME) responsible for initiating paging and
authentication of mobile devices is active or inactive
KPI Report Status The Key Performance Indicators (KPI) report status is normal or broken. This field is
reserved for future use.
Sync Status The eNB is synchronized or unsynchronized with other eNBs in the same cell
UE Count Number of User Equipment (UEs) actively connected to this eNB
Uptime Length of time this eNB has been operational - dd:hh:mm:ss
Last Connection Time The last time this eNB was connected to the OMC/Cloud - yy:mm:dd
Duplex Mode Either TDD or FDD
Model The eNB equipment model (part number)
Product Type Auto-populated eNB description used in OMC, e.g., Standard, 436Q-CA, etc.
Hardware Version The version of hardware for this device
Software Version Software code level running on the device
Earfcn EARFCN frequency the eNB is using
Device Group The device group to which this device has been configured
RF Status Shows if the eNB’s radio is on or off
Active Ratio (30 days) The ratio of active to inactive times for this eNB during the last 30 days. An example is
provided in Figure 4-28.
Satellites The number of GPS satellites found and reported by the eNB. This field is active only in
eNBs running certain software versions.
HaloB-Centralize Shows if the centralized mode of the HaloB feature is enabled or disabled on this eNB.
For more information about HaloB, refer to the Baicells HaloB User Guide.
Longitude The eNB's longitude coordinate
Latitude The eNB's latitude coordinate
Height The eNB's antenna height, in meters
MMEPOOL Ipsec Address IPSec gateway address for the MME pool
Figure 4-28: Active Ratio Example
126
4.4.2.1.1 Display
Use the Display icon (Figure 4-29) to show, hide, or rearrange columns in the eNB Monitor window. If you want
to see all of the columns, simply select All and then OK.
Figure 4-30: Filter Example

Use the Filter icon next to a column header to customize a column
of information by selecting another display criterion to narrow
the results (Figure 4-30). To find a specific eNB use the query field
by entering the eNB serial number, cell name, or IP address. Use
Advanced Query to refine the search or to pull up information on
all eNBs in a specific device group, all eNBs with a certain status,
etc. (Figure 4-31).
Figure 4-31: Advanced Query
127
4.4.2.1.2 Operations
For each row in the eNB > Monitor window, notice the icon of 3 vertical bubbles under the column called
Operations (Figure 4-32). When you click on the icon, 3 menu options appear: Information, Settings, More.
Figure 4-32: Operations
4.4.2.1.2.1 Information
The Information option displays 4 tabs: Statistics, Alarm, Logs, and License Info (Figure 4-33). The first tab is
shown.
Figure 4-33: Statistics
4.4.2.1.2.1.1 Statistics
If you are monitoring a two-carrier eNB, the first field will be Cell Infos, as shown above in Figure 4-34, and you
will see a break-down of the monitoring data for the primary cell (Pcell) and the secondary cell (Scell). For Status
Info, you can select eNB Active Status, Online Status, or UE Count, which will result in a graphic representing the
current data. The example in Figure 4-34 is for eNB Active Status, which shows it was inactive all day on July 26.
Figure 4-34: Status Info
128
4.4.2.1.2.1.2 Alarm
The Alarm tab displays all alarms associated with this eNB (Figure 4-35), both current and historical, when you
select either the Active Alarm tab or the History Alarm tab. It shows the alarm number, probable cause, status,
event time, and the last update time.
Use the Filter icon to display only the alarm category you are interested in. For any alarm in the list, use the
Operation menus to get more details (Figure 4-36), confirm or clear the alarm, or in the case of a history alarm,
to restore an alarm. Please refer to a more detailed description of the alarms in section 4.4.1.2.
Figure 4-35: Alarm
Figure 4-36: Detail
129
4.4.2.1.2.1.3 Logs
When you select the Logs tab, use the tabs to view the device report log or the device exception log list (Figure
4-37). Notice that for the logs that are listed, you can download the log file using the down arrow.
Figure 4-37: Device Report Log & Device Exception Log
4.4.2.1.2.1.4 License Info

If you purchased optional eNB functions such as Carrier Aggregation or Dual Carrier, the License Info tab will
display the list of licenses (Figure 4-38). Licenses generally are packaged by quantity and expiration date,
although such restrictions may not apply in your country.
Figure 4-38: License Info
130
4.4.2.1.2.2 Settings
In the eNB > Monitor window, when you click on the Operation icon for a specific eNB and select Settings, you
will get the Quick Settings window shown in Figure 4-39. If the eNB has a Cell Name field populated on the main
Monitor page, the Quick Settings window will auto-populate the eNodeb Name field. Otherwise, enter the eNB
name and select OK for the system to apply the Quick Setting values found in the BTS Info > Quick Setting menu.
Figure 4-39: Settings
4.4.2.1.2.3 More
Additional operations may be performed when you highlight an eNB in the Monitor window, select Operations,
and then select More: Synchronize, Logs, Reset Password, or RF OFF (Figure 4-40). If an eNB is inactive or
ineligible for an action to be taken, the choice(s) will be greyed out. For example, the Reset Configuration
function is used only by Baicells support.
Figure 4-40: More
Selecting Synchronize refreshes the eNB status in OMC. Selecting Logs launches a pop-up window asking if you
want to collect logs for this eNB (Figure 4-41). If you do, click on OK.
Figure 4-41: Logs
131
Clicking on Reboot will initiate a warm reboot causing the eNB to reboot immediately. Selecting HaloB Enable
will put the eNB into HaloB operating mode. Selecting Active will activate the eNB into service if it is currently
inactive. The RF OFF option enables you to turn the eNB's antenna transmissions off (or on), depending on its
current state.
Use Reset Password to reset the login password for this eNB. When you take this action, the system will return
a message stating it will send you an email with a link. You will be given 30 days to reset the password. Refer to
Figure 4-42, Figure 4-43, and Figure 4-44.
Figure 4-42: Reset Password (1 of 3)
132
4.4.2.2 Maintenance
The eNB > Maintenance menu offers Reset Password, Reboot, Log, and Software Rollback functions (Figure 4-45).
For each function you can define and schedule tasks for one or more eNBs.
Figure 4-45: Maintenance
4.4.2.2.1 Reset Password

The eNB > Maintenance > Reset Password menu is where you can reset the password on one or more eNBs at
the same time by creating a task. Click on the + Add icon to open the dialogue window, select the target eNBs,
and click on the Reset Password button to immediately change the current passwords (Figure 4-46). Once a task
has finished executing, click on Operations > View to display the Task Results at the bottom of the window. If a
task has already been executed and finished, some Operations actions such as Suspend and Terminate will be
greyed out.
4.4.2.2.2 Reboot
To define a new reboot task, select Maintenance > Reboot, and click on the + Add icon (Figure 4-47). In the
dialogue window, select the target eNBs, select the Execute Mode, and select OK.
133
Figure 4-47: Create Reboot Task
Once the Reboot task is saved, it appears in the list of task names. Use the Operations actions to View or Delete
the task. As with Reset Password, selecting Operations > View displays task results and a time stamp for the
executed task at the bottom of the window.
4.4.2.2.3 Log
The eNB > Maintenance > Log menu offers 4 views of eNB devices: Device Report Log, Alarm Log, Device
Exception Log, and Event Log (Figure 4-48). For the Device Report and the Alarm logs, you can create tasks to
generate the log files for multiple eNBs.
The Operations actions for a log task are View, Terminate, Download, and Delete. As with Reset Password,
selecting Operations > View displays task results at the bottom of the window (Figure 4-49). If a task has already
been executed and finished, some Operations actions such as Suspend and Terminate will be greyed out.
Figure 4-48: Log - Add Task
134
Figure 4-49: Operations > View (Task Results) - Device Report Log Example
4.4.2.2.4 Software Rollback

In the event you need to roll the eNB software back to a previous version, use this eNB > Maintenance > Software
Rollback menu to create a rollback task (Figure 4-50). Similar to the other maintenance tasks, use the + Add
function to create a rollback task for multiple eNBs.
Notice in this case, however, you must select a Product Type. Only eNBs of the same product type can be grouped
into a single task. The Intel-based eNBs such as Nova-227, Nova-233, and Nova-243 are considered to be the
Standard product type. Other product types typically refer to the two-carrier Nova-436Q eNB. When the 436Q
is licensed to run in Carrier Aggregation (CA) mode, for example, you might see 436Q-CA in the product type
category.
Select the specific eNBs from the list in the New Rollback Task window, and then select an Executed Mode and
click on OK. When the task appears in the Software Rollback task list, use the Operations actions to view the task
results once executed, display information about the task settings, or delete the task. An example of task results
is shown in Figure 4-51.
135
Figure 4-50: Software Rollback
Figure 4-51: Operations > View (Task Results) - Software Rollback
4.4.2.3 Register
The eNB > Register menu provides two functions: Device and License. These are explained in this section.
136
4.4.2.3.1 Device
This menu is used to register eNBs in the operator's network by adding the eNB configuration information. You
can also create, view, modify, and delete eNB device groups (Figure 4-52). An eNB device group is a way of
grouping eNBs with the same parameters to more easily execute reconfiguration, reboot, upgrade, and other
types of tasks.
Figure 4-52: Register
In the Device Group Information section on the left side of the window is a list of predefined device groups.
Notice under Operations that you can View (eye icon) (Figure 4-53), Modify, or Delete a device group.
NOTE: You cannot modify the default device group.
Figure 4-53: View Device Group
Click on the + Add icon to create a new device group (Figure 4-54). After entering the group information, click
on OK to save the configuration.
Figure 4-54: Add New Device Group
137
On the right side of the Device window is a list of the operator’s eNBs. When you click on the + Add icon you
register the device in the operator's network (Figure 4-55). You will be prompted to enter the eNB's serial number.
Use the check box next to any eNB in the list that you want to move to an existing device group or to delete.
Figure 4-55: Add (Register) eNB
The other two icons in the window enable you to import or export eNB device information (Figure 4-56).
Figure 4-56: Import/Export eNB Information
4.4.2.3.2 License
In eNB > Register > License you can import, activate, view, and download feature license files for optional
features such as HaloB. Per Figure 4-57, the sequence for using the license function is (1) import the file; (2)
activate the license; and (3) verify the device is showing the active status for the licensed feature. When activated,
the license goes into effect on the appropriate device immediately.
You can toggle between a licensed mode and standard operating mode by going to the eNB > Monitor page,
finding the device in the list, and selecting Operations > (feature name) Enable/Disable, e.g., HaloB Enable or
HaloB Disable.
138
Figure 4-57: License
4.4.2.4 Upgrade
The eNB > Upgrade function (Figure 4-58) gives you the ability to configure software upgrade tasks which can
be applied to multiple eNBs at the same time. There is no limit on the number of devices you can target for an
upgrade task; however, only 20 devices will be upgraded at the same time.
Figure 4-58: Upgrade
The Upgrade window shows 2 tabs: IMAGE Upgrade File and PATCH Upgrade File. Under either tab, any upgrade
tasks already created will appear in the list below. Use the Operations actions to View any results of an existing
task that has been executed or to download the results.
139
To define a new upgrade task, follow the steps below as an example of creating a software upgrade task. Creating
an upgrade task allows you to upgrade multiple eNBs instead of having to do so one by one. There is no limit on
the number of devices you can target for the upgrade task; however, only 20 devices will be upgraded at the
same time.
1. Go to eNB > Upgrade.
2. Click on the + Add icon to create the task (Figure 4-59).
3. Accept or create a task name, and select the product type, where:
• Standard is for single-carrier eNBs (Nova-227, -233, and -243)
• 436Q is for the two-carrier Nova-436Q eNB
4. Check the check box next to each eNB you want included in this task. The list will appear under
Selected.
5. The available software files will display under the File list section of the window. Highlight the row
displaying the software version you want to upgrade or rollback to.
6. Select the Executed mode for when you want the task to execute. To retain current configuration
settings on the eNBs to be upgraded, check the check box next to Retain Configuration.
7. Select OK. The new upgrade task will now appear in the Upgrade > Software list. Once the task has
executed, verify that the new firmware version is on the eNBs by going to eNB > Monitor and checking
the Software Version column.
Figure 4-59: Add New Upgrade Task
140
4.4.3 CPE
The CPE menu includes several functions: Monitor, Maintenance, Register, and Upgrade (Figure 4-60). Each is
explained in this section.
Figure 4-60: CPE
4.4.3.1 Monitor
The CPE > Monitor window shows the list of existing UEs in the operator's network (Figure 4-61), with multiple
columns of information for each one. The meaning of each column header is described in Table 4-4. The columns
reporting current RF values, such as RSRP, CINR, and SINR, use color (red) to indicate if a value is out of the
normal range.
Figure 4-61: Monitor
Table 4-4: Monitor

Operations When you highlight the row of a UE and click on the icon under Operations, a list of actions
you can take on that UE is displayed: Information, Settings, Synchronize, Frequency Lock,
and Reboot. Refer to section 4.4.3.1.2.
<Untitled> The column that just shows a filter icon at the top presents a UE's present status:
Connected (blue) to the network or Disconnected (red) from the network.
141
Serial Number The UE unit’s serial number
CPE Name Name given to the UE by the operator
IMSI The UE’s unique International Mobile Subscriber Identity (IMSI) number
Cell Name The name of the cell in which the UE’s currently serving eNB is identified
PCI The currently serving eNB’s Physical Cell Identifier, or Layer 1 identity, which uniquely
identifies each cell site in the wireless network
UL_MCS The currently serving eNB’s Modulation and Coding Scheme (MCS) index value on the
uplink. The value is based on channel quality. If the value assigned reaches single digits,
you likely have channel quality problems.
DL_MCS The currently serving eNB’s Modulation and Coding Scheme (MCS) index value on the
downlink. The value is based on channel quality. If the value assigned reaches single digits,
you likely have channel quality problems.
RSRP1 Reference Symbol Received Power (RSRP) is an LTE power metric (dB) which provides
information about signal strength. RSRP is an average of the RF power in each subcarrier.
(There are 2 antenna cables from the eNB to the RF antenna, with dual polarity. The
system measures the RSRP on each.)
RSRP2 Reference Symbol Received Power (RSRP) is an LTE power metric (dB) which provides
information about signal strength. RSRP is an average of the RF power in each subcarrier.
(There are 2 antenna cables from the eNB to the RF antenna, with dual polarity. The
system measures the RSRP on each.)
CINR1 Carrier-to-Interference-plus-Noise Ratio (CINR) is a measurement (dB) of multiple
subcarriers, which reflects the signal quality of the LTE carrier system. (For most eNBs
there are 2 antenna cables from the eNB to the RF antenna, with dual polarity. The system
measures the CINR on each.)
CINR2 Carrier-to-Interference-plus-Noise Ratio (CINR) is a measurement (dB) of multiple
subcarriers, which reflects the signal quality of the LTE carrier system. (In most eNBs there
are 2 antenna cables from the eNB to the RF antenna, with dual polarity. The system
measures the CINR on each.)
SINR Signal-to-Interference-plus-Noise-Ratio (SINR), also known as the carrier-to-interference
ratio (CIR or C/I), is a quantity (dB) used to give theoretical upper bounds on channel
capacity. SINR is calculated based on the power of a certain signal of interest divided by
the sum of interference power from all the other interfering signals and background noise.
DL Throughput (Mbps) The current downlink data rate from eNB to UE - in Megabits per second (Mbps)
UL Throughput (Mbps) The current uplink data rate from UE to eNB - in Megabits per second (Mbps)
Uptime Number of hours the UE has been powered on
Last Connection Time The last time the UE was connected to the OMC/CloudCore
IP Address The UE’s current IP address
MAC Address The UE unit’s MAC address
Cell ID The cell ID of the currently serving eNB for this UE
Module IDU for indoor unit or ODU for outdoor unit
Model Name The specific UE hardware model
Software Version The current version of software loaded on this UE
142
Tx Power Current UE transmit power, in dBm
MCC Mobile Country Code - used to uniquely identify the operator of a telecommunications
network. MCC + MNC = PLMN.
MNC Mobile Network Code - uniquely identifies a mobile network operator (carrier) using the
GSM (including GSM-R), UMTS, and LTE public land mobile networks. MCC + MNC = PLMN.
Device Group The configured UE device group to which this UE belongs
History The graphs (Figure 4-63) provide historical information about the UE:
• Uplink (UL) and Downlink (DL) Modulation Coding Scheme (MCS) used.
• Reference Signal Received Power (RSRP) 1 and 2 are measurements of the average
power of the LTE reference signals over the entire bandwidth
• Carrier-to-Interference Plus Noise Ratio (CINR) 1 and 2 are values that represent the
ratio between the power of the RF carrier (wireless signal) bearing the wanted signal
and the total power of interfering signals and noises
• Signal-to-Interference Ratio (SINR) is a value representing the ratio of the average
received demodulated signal power to the sum of the average co-channel interference
power and the noise power from other sources
Downlink (DL) and Uplink (UL) Throughput indicate the average number of Mbps of data
transmitted between the eNB and UE. DL is eNB to UE and UL is UE to eNB
4.4.3.1.1 Display
Click on the Display icon to select and arrange the columns of information you wish to be displayed for the UEs
(Figure 4-62). If you want to see all of the information, simply click on All. Moving an item up in the list will result
in that item (column header) appearing farther to the left in the Monitor window.
4.4.3.1.2 Operations
For each UE, use the Operations functions to view information, configure settings, and take other actions (Figure
4-63).
143
4.4.3.1.2.1 Information
When you select Operations > Information, the system displays the basic UE information, such as serial number,
International Mobile Subscriber Identity (IMSI), transmit (Tx) power, mobile country code (MCC), and mobile
network code (MNC) (Figure 4-64).
Figure 4-64: Information
4.4.3.1.2.2 Settings
If you select Operation > Settings, you can give a name to the device. You can use A-Z, a-z, 0-9, - (dash) and _
(underline) characters. The maximum number of characters is 45. You can also enable Https Login for remote
Web access (Figure 4-65) to the UE by clicking on the check box for that field.
4.4.3.1.2.3 Actions
4.4.3.1.2.3.1 Synchronize
Use the Operation > Synchronize function to synchronize the UE data with the OMC. The icon to the right of the
Operation column will appear to spin as the two entities sync information (Figure 4-66).
144
Figure 4-66: Synchronize
4.4.3.1.2.3.2 Frequency Lock

The Operation > Frequency Lock function provides a mechanism for configuring how the UE scans available
frequencies in its periodic check for the best signal - Band/Frequency Preferred, Full Band, or PCI lock to a specific
PCI ID or to one or more eNB EARFCNs (Figure 4-67). Frequency scanning is explained in section 3.5.2.
Figure 4-67: Frequency Lock
4.4.3.1.2.3.3 Reboot
If you select the Operation > Reboot function, the system will warn you that taking this action will cause the UE
to reboot and therefore disrupt service (Figure 4-68). Click on OK if you want to go ahead and reboot the UE.
Figure 4-68: Reboot
4.4.3.1.3 History
Back in the main CPE > Monitor window, notice the History column. If you click on the graph icon for a specific
UE the system will display several performance graphs: UL MCS, DL MCS, RSRP1, RSRP2, CINR1, CINR2, SINR, DL
Throughput, and UL Throughput (Figure 4-69).
Figure 4-69: History - UL/DL MCS
The first two graphs, UL and DL MCS, provide the average uplink and downlink Modulation and Coding Scheme
(MCS) index value over time. The higher the MCS value, the better the throughput. Refer to the Baicells Operation,
Maintenance, & Troubleshooting Guide for information on interpreting the MCS performance results.
145
The next two history graphs are the Reference Symbol Received Power 1 and 2 (RSRP1 and RSRP2) (Figure 4-70).
RSRP is the average power of the LTE reference signals over the entire bandwidth. Weak signal strength can
cause connectivity issues and dropped sessions.
The Carrier-to-Interference-Plus-Noise Ratio 1 and 2 (CINR1 and CINR2) graphs indicate channel quality (Figure
4-71). The higher the MCS index reported, which can be QPSK, QAM16, or QAM64 depending on the model of
UE and eNB, the better the quality of the wireless signal and therefore the higher the throughput rates available
to the user.
Figure 4-70: History - RSRP1/2
Figure 4-71: History - CINR1/2
The Signal-to-Interference-Plus-Noise Ratio (SINR) graph provides the average ratio over time for this UE (Figure
4-72). Like RSRP, SINR provides an indication of signal strength. Weak signal strength can cause connectivity
issues and dropped sessions.
146
Figure 4-72: History - SINR
The last two historical performance graphs for the UE are the DL and UL Throughput (Figure 4-73). Throughput,
also referred to as data rate or speed, is expressed in Megabits per Second (Mbps).
Figure 4-73: History - DL/UL Throughput
4.4.3.2 Maintenance
4.4.3.2.1 Reboot
The CPE > Maintenance > Reboot menu is used to define and schedule a reboot task for one or more UEs (Figure
4-74). Use the search bar or Advance Query to filter an existing list of reboot tasks. To create a new reboot task,
click on the + Add icon.
147
Figure 4-74: Reboot
Enter a task name, and select a device group if you want to filter the list of UEs based on device group name.
Check the check box next to the UEs you want to include in the reboot task. “Move” them to the Selected area
using the right arrow. Select the Execute Type either to run the task immediately or schedule a time for it to run.
Click on Next to continue when ready. The system will prompt you with a warning to be sure you want to reboot
the UEs (Figure 4-75), per the execute time, which will disrupt service.
Figure 4-75: Reboot Warning
In the list of existing tasks that have been defined, use the functions under Operations to take any of the
following actions: View task results, Stop a task in process, Terminate a scheduled task without deleting it, or
DeleteTask (Figure 4-76). Unavailable actions for that task will be greyed out. An example of the View task results
is shown in the figure.
148
4.4.3.2.2 PCI Lock

The Physical Cell Identifier (PCI) Lock function allows you to "hard-configure" to which eNB(s) selected UEs/CPEs
can attach (Figure 4-77). Click on the + Add icon to create a CPE PCI Lock task, which will assign and execute the
same Frequency Lock option to multiple UEs: Full Band, Band/Frequency Preferred, or PCI lock. (Each option is
explained in section 3.5.2 Scan Method in this document.) The resulting fields will vary based on which scan
option you choose.
Figure 4-77: PCI Lock
149
Caution: When the task is run it performs a warm reboot of the affected eNBs and reboots the UEs,
which interrupts service.
Important: Any UEs that are offline during the execution of a task will not receive the change. You may need to
check the status of each one and possibly reinitiate the task to ensure all UEs are updated.
The Operations actions available for each PCI Lock task are View results if task already executed, Start the task,
Terminate the task without deleting it, or DeleteTask (Figure 4-78). Unavailable options for a task will be greyed
out.
4.4.3.3 Register
The CPE > Register menu is used to identify devices in the system (Figure 4-79). Adding a device in this menu is
considered registering it in the CloudCore account.
Figure 4-79: Register
The CPE > Register > Device menu works the same way as for eNB > Register > Device, covered in section 4.4.2.3.1,
except it is for UEs (Figure 4-80). On the left side of the window are the device groups and the ability to add new
UE device groups. For each device group you can view (eye icon), edit (pen icon), or delete (trash can icon) using
the Operations actions.
On the right side is the list of UEs in the operator’s network, with the ability to add or delete UEs, move UEs to
a device group, or import or export UE information. Taking the + Add action is considered registering the device
in the OMC. Use the + Add icon in the upper right to add device groups or to add UEs.
150
Figure 4-80: Device
4.4.3.4 Upgrade
4.4.3.4.1 Software
The CPE > Upgrade > Software procedure is similar to an eNB upgrade in that you create an upgrade task. Use
this menu to create tasks for upgrading multiple UEs. There is no limit on the number of devices you can target
for the upgrade task; however, only 20 devices will be upgraded at the same time.
To define a new software task, follow the steps below.
1. At the main menu, go to CPE > Upgrade > Software.
2. Click on the + (Add) icon in the upper right side of the window (Figure 4-81).
3. Accept or change the Task Name.
4. Select the Product Type, either ODU (for outdoor UE models), or IDU (for indoor UE models).
5. In the list of UEs that displays, under Select Device select the UEs you want to upgrade. Use the query
field as needed to search for each specific device by serial number or name.
6. The available software files will display under the File list section of the window. Highlight the row
displaying the software version you want to use for the upgrade.
7. Select the Executed mode, either Immediately, Awaiting Start, or Schedule Time. Awaiting Start may
be used to delay a scheduled upgrade or rollback task. Schedule Time allows you to select a date and
time for the task to execute. When finished, select OK.
After the upgrade task has executed, go to CPE > Monitor, search for the UEs that were targeted for the
upgrade/rollback, and check the Software Version column to verify the task executed correctly.
151
Figure 4-81: New Upgrade Task
Use the Operations function to View any results of a task that has been executed, to Stop the task while in
process, Terminate but not delete the task, display the Information about the task configuration, or Delete the
task (Figure 4-82). Unavailable actions will be greyed out. The figure shows the View task results at the bottom.
152
4.4.3.4.2 Software Files
The CPE > Upgrade > Software Files function displays the list of image files available for UEs. Select the correct
tab - ODU or IDU - to see software image files for either the outdoor or indoor UE (Figure 4-83). Check the Baicells
website to ensure you have the latest software (firmware) for your device. The Operations functions include View
information about the file, Download the image file, Edit the information, or Delete the file. Unavailable actions
will be greyed out.
Figure 4-83: Software Files
4.4.4 Alarm
4.4.4.1 Overview
Alarm conditions are captured and reported for the operator's network. The types of events that may trigger
alarms include issues with communications, Quality of Service (QoS), equipment, environmental conditions, or
processing errors.
Alarms are categorized into 4 severity classes: Critical, Major, Minor, or Warning. Critical alarms are incidents that
can cause system outages, and should be attended to immediately. Major alarms are incidents that can cause
poor or degrading quality of service for subscribers, and therefore should be addressed as soon as possible.
Minor alarms indicate a possible issue that needs to be investigated but will not disrupt service. Warnings are
used to indicate errors that probably need to be corrected or at least monitored, but may not require any action.
The Alarm menu (Figure 4-84) is where you can set up alarm templates, e.g., to filter data based on severity level
or specific eNBs; view all of the operator's currently active and historical alarms; search (query) for specific
alarms; look at the library of all alarms created for a Baicells system; and set up email notifications based on
criteria that you define.
Figure 4-84: Alarm Menu
153
Mentioned in section 4.4.1, the top of the Dashboard window displays the number of active system alarms in the
operator's network, and if you click on the double arrows it takes you into the Alarm > Query sub-menu (Figure
4-85). All of the Alarm sub-menus are explained in this section.
Figure 4-85: Dashboard Alarms
4.4.4.2 View & Create Alarm Template

The first time you select Alarm > View, you will receive a notice that you need to create an alarm monitoring
template (Figure 4-86). You can create a template in this window, or by going to the Alarm > Setting menu. The
templates function allows you to set up custom filtered templates for alarms, e.g., to view only certain severity
levels. In the View window:
1. Click on the Create Template icon in the upper right corner of the window, as shown in Figure 4-86. The
new window will display any existing templates and show a + (Add) icon in the top right.
2. Click on the + Add icon, enter a template name, and if not already selected, select the eNB radio button
for Device Type.
3. Under Group Name, select the eNB device group you want to monitor using this alarm template.
4. In the Alarm List, select the alarms you want included in the template.
a. If you select the top check box, it will automatically select all alarms to monitor; otherwise, go
through the alarm list (use query to narrow) and check which alarms you want to monitor.
b. You can sort the list in each column that has the up/down arrows. For example, by clicking on
Device Type, the display changes the display order for that column.
5. When you have finished selecting the alarms, click on OK.
NOTE: You will be able to set up email notifications under Alarm > Settings > Notification.
Figure 4-86: First Time Using Alarm > View
154
Figure 4-87: Add New Template
4.4.4.3 Query
In Alarm > Query, use the tabs to view all of the operator's currently active or historical alarms (Figure 4-88).
Figure 4-88: Query
155
For any alarm in the active list, when you click on the Operations icon you can select Detail to get more alarm
details (Figure 4-89); Alarm Confirm to acknowledge you have seen the alarm; or Clear Alarm to remove it from
the active list to the historical alarm list. The fields shown when you select Detail are described in Table 4-5.
When you confirm an alarm, you are provided a description box to enter notes before selecting Confirm.
In the historical alarms list, one additional Operations function is available: Restore Alarm. When you restore an
alarm, it is moved to the active alarm list.
Figure 4-89: Alarm Details
Table 4-5: Alarm Details

Index System index number assigned to each alarm incident
Severity Severity of the alarm – critical, major, minor, or warning
Alarm Identifier Alarm number that identifies the type of alarm
NE Type Network Entity incurring the alarm, e.g., OMC, eNB, UE
Network Element Provides more detail about which device reported the alarm, e.g., eNB serial number, name
Event Type Alarm classification – communications, QoS, processing error, equipment, or environmental
Alarm Status Current state of the alarm – confirmed and active, confirmed and inactive, unconfirmed and
active, unconfirmed and inactive
Event Time Date and time when the alarm occurred
Confirmed User Indicates if the alarm was confirmed (acknowledged) by an OMC administrator
Confirmed Time Indicates the time at which the alarm was confirmed (acknowledged) by an OMC admin
Update Time Last time the alarm status was updated
Probable Cause Reason alarm probably occurred – for example, clock source synchronization, network
problems, GPS unavailable, etc.
Specific Problem Further detail about why the alarm may have occurred – information varies per alarm
Suggestion Actions you may need to take to resolve the alarm – suggestions vary per alarm
156
Notice in the upper right corner of the Alarm > Query screen is an Export icon (Figure 4-90). You can export the
alarm information as a file to save on a computer or server.
Figure 4-90: Export
Some columns have filter icons (Figure 4-91). As an example of this function, if you click on the Filter icon next
to the Severity column, you can quickly select which category of alarms you want to see – Major, Critical,
Warning, and/or Minor.
Figure 4-91: Filter
4.4.4.4 Settings
The Alarm > Settings menu includes View Template, Basic, Library, and Notification (Figure 4-92). Each function
is explained in this section.
Figure 4-92: Alarm > Settings
4.4.4.4.1 View Template

As with the View menu, the View Template menu opens to a list of any existing alarm templates that have been
configured (Figure 4-93). Use the actions under Operations to view (eye icon), modify (pen icon), or delete (trash
icon) an existing alarm template. To add a new alarm template, click on the + Add icon. This will open a New
Template dialogue window (Figure 4-94). Enter a template name, select the device type, select an eNB device
group or groups, and then choose which alarms you want included in this template.
157
Figure 4-93: View Template
Figure 4-94: New Template
4.4.4.4.2 Alarm Rule

Use the Alarm Rule menu to set up rules for specific devices and how you want alarm types (categories) or
severity levels to be handled: Only Store, No Display; No Store, No Display; or Auto Confirm. To create a rule,
click on the + Add icon (Figure 4-95). You can configure the rule by selected eNBs or by alarm IDs reported in
OMC.
Figure 4-95: eNB Alarm Rule
Give the rule a name, and select Enable or Disable for the rule status to take effect. Select an Execution Action,
and then the device type, either eNB or OMC. If you select eNB, find the eNBs you wish to be associated with
the rule and click on the check box to "move" them into the Selected pane.
158
Next, choose the alarm type(s) and the severity level(s) to filter. You can set an Event Time by using the Start
Time and Finish Time, meaning to report the alarms only during this window of time. Be sure to enable the new
rule when you want it to become active. If you select OMC as the Device Type, you can filter how you want
specific alarm IDs handled and reported in OMC (Figure 4-96).
Figure 4-96: OMC Alarm Rule
4.4.4.4.3 Library
Selecting Alarm > Settings > Library brings up a list of all possible system alarms, providing a probable cause and
the severity level of each alarm (Figure 4-97). As with other menus, you can adjust the column size, filter some
of the columns, and use the search bar to look for specific alarms.
Figure 4-97: Library
4.4.4.4.4 Notification
The Alarm > Settings > Notification window is where you can define and enable or disable email notification
templates based on the criteria you set (Figure 4-98). To create a new notification template, click on the + (Add)
icon in the upper right. Give the template a name, and optionally enter a description. Set the notification cycle
(in minutes - multiples of 10 from 10 to 60 - or real time), which determines how often the system checks for
conditions that meet the criteria set in the template.
159
Figure 4-98: Notification
Select the device type, eNB. You can search by device group or specific eNBs. Use the search bar to find the
device group(s) or eNBs you want included in this template. As you click on the check box next to a device group
name, the group is automatically added to the Selected Device Group pane on the right. Next, under the Alarm
List identify the alarms for which you want to be notified. If you select the top check box, it will highlight all of
the alarms. As you select the alarms, they will automatically be added to the Selected Alarm pane on the right.
At the bottom of this window, enter one or multiple email addresses where you want the notifications sent. If
there are multiple email addresses, separate them using a semi-colon (;).
Each notification template will appear in the main Notification window. By default, the notification templates
are given a status of Close. Go to Operations > Open to activate the template. Other Operations functions are
View template details, Modify a template, and Delete a template (Figure 4-99).
160
4.4.5 Advance > SAS
Reference: SAS Deployment Guide
This section covers only the OMC SAS parameters. Please refer to the SAS Deployment Guide for all of the
implementation procedures.
4.4.5.1 Overview
The Citizens Broadband Radio Service (CBRS) band covers 3.55-3.7 GHz. Operators must sign up with a Spectrum
Access System (SAS) provider for services to handle the dynamic frequency assignment and release process.
Baicells provides FCC Part 96 certified eNB and UE CBRS Service Devices (CBSDs) that can operate within the FCC
rules for CBRS. Initial Commercial Deployments (ICD) of CBRS/SAS began in September 2019.
The OMC will reflect the eNB GUI > LTE > SAS settings where you enter the installation information and Certified
Professional Installer (CPI) credentials. The SAS vendor will control the eNB's power and frequency point, as
required by CBRS regulations, once all steps in the OMC are completed and tested. When SAS is enabled, the
BTS Info > Quick Settings for Band, Bandwidth, Frequency, and Power modify become invalid; the eNB will use
the SAS settings.
4.4.5.2 Requirements
The Baicells eNBs use domain proxy (DP) to connect to the SAS server by leveraging the existing connection with
the OMC. All eNBs will need to be connected to the OMC in order to connect to the SAS. The minimum software
versions that support SAS are:
• Nova-227/233/243: BaiBS_RTS_3.4.8 or later
• Nova-436Q: BaiBS_QRTB_2.0.5 or later
• OMC: https://cloudcore.baicells.com (5.2.7)
NOTE: Legacy Gen 1 CPEs do not support SAS.
4.4.5.3 About the OMC Advance > SAS Menu
The Advance > SAS page will list any devices that are configured for SAS operation (Figure 4-100). When you
select a device in the list, click on the Settings icon to enable/disable SAS and to select or change a SAS vendor
(Figure 4-101).
Figure 4-100: Advance > SAS
161
There are 3 Operations actions for the devices listed in the SAS window: Install Params, Procedure, and SAS ON
or OFF (Figure 4-102). Selecting Install Params displays the eNB device information such as serial number,
frequency, status, etc. Selecting Procedure displays the status of the eNB connection to the SAS server in a
progressive state: Unregistered, Registered, Granted, Authorized, Transmission. SAS ON/OFF is a quick way to
enable or disable SAS operation for the selected eNB.
4.4.6 System
The OMC System menu primarily covers various levels of security functions, general system information such as
resource utilization, and system logs (Figure 4-103). Each function is explained in this section.
162
Figure 4-103: System
4.4.6.1 Security
4.4.6.1.1 User
"Users" in this menu refers to OMC administrators. Adding new users follows a hierarchical order: First, configure
the role sets (section 4.4.7.1.3); next, configure the user groups (section 4.4.7.1.2); and then add new users (this
section). This recommended flow is based on the mandatory fields in each of those menus.
When you select System > Security > User, a list of existing users will be shown. To add a new administrative user,
click on the + Add icon to open the configuration window. Fields with a star next to them are mandatory. Refer
to Figure 4-104. If a user is not assigned to a user group, they will automatically be placed in the default group.
Figure 4-104: User
In the list of existing users, if you need to move a user to a different group you can select the check box next to
the name and a pop-up button appears, allowing you to easily Move to User Group (Figure 4-105).
Figure 4-105: Move to User Group
Under Operations, you can copy the user information, modify the user's information, or delete the user from
the system. Depending on the user's status you can also reset the user's password or unlock their account. Refer
to Figure 4-106.
163
Figure 4-106: User
4.4.6.1.2 User Group

An OMC administrative user group represents "like" users, e.g., those who have the same OMC privileges or are
in the same department or are in the same geographical area, etc. The User Group menu displays a list of existing
user groups if any have been configured. Any user not assigned to a user group will be placed in the default user
group. In the list of existing user groups, under Operations you can view information about a group, modify the
information, or delete the user group. See Figure 4-107.
Figure 4-107: User Group
Before adding a new user group, you should first configure the role sets, as assigning a role set to the group is a
mandatory field. Role Sets is covered next in section 4.4.7.1.3. Use the + Add icon to add a new user group (Figure
4-108). Enter the Basic Info settings - User Group Name and Description for the new user group - and select one
or more Role Sets to assign to this group.
Figure 4-108: + Add User Group
164
4.4.6.1.3 Role Set
Use the Role Set menu to define different sets of OMC user privileges (Figure 4-109). To create a new role set
click on the + Add icon. Complete the Basic Info settings, and optionally add a description. Then you will select
which OMC functions are authorized, whether users with this role set can read, write, or both for each OMC
function, and which user groups are part of this role set.
If an OMC function you select under Functional Authority List is an editable function, you will be presented with
2 more check boxes under Functional Operation: read and write. You can select either field or both fields. For
the Resource Authority List, you can also select users that are in one or more user groups. An example is shown
in Figure 4-110.
Figure 4-109: Role Set
Figure 4-110: + Add Role (Set)
4.4.6.2 Security Rule

Selecting System > Security Rule allows you to set up rules concerning administrative user access to the
operator's CloudCore account. Click on Edit to take any of the following actions (Figure 4-111).
165
• Login Limit
o Limit Single User Login - if you toggle the field to enable this feature, only one administrative
user will be able to access the operator's CloudCore account
o Limit User Login Switch - enable if you want to limit the maximum number of users who can
access the operator's CloudCore account
o User Login Max Number - enter the number of logins permitted
• Access Rule
o IP White List - enable if you want to create IP address white lists to limit which IP addresses may
log in to the operator's CloudCore account.
o Start IP - when IP White List is enabled, enter the starting IP address
o End IP - when IP White List is enabled, enter the ending IP address
Figure 4-111: Security Rule
4.4.6.3 Logs
The System > OMC Log menu is where you can display OMC Operation and OMC Security event logs. Figure
4-112 shows the column headers from left to right; they are the same for both tabs.
Figure 4-112: OMC Log
Click on the View icon to see log details. On the Operation Log tab, the view will present 3 tabs: Operation Log,
Security Log, and System Log so you can filter the log events you want to see. An example of security log is
provided in Figure 4-113. Use the Export icon to export the data to a file on your computer.
166
Figure 4-113: OMC Security Logs
4.4.7 Help
The Help > About menu displays the OMC software version number and name (Figure 4-114).
Figure 4-114: Help
167
4.5 BOSS
4.5.1 Overview
Individual subscribers are added to the network using the Baicells Business and Operation Support System
(BOSS). Sometimes referred to as BaiBOSS, this application is part of the CloudCore suite of applications for
managing the network.
The subscriber information configured in BOSS is used for multiple purposes. First, operators can connect BOSS
to their billing systems to manage subscriber accounts, and second, BOSS information is available to the OMC
for easier network management. The Baicells BOSS is comprised of 3 parts: BOSS server, BOSS client, and a
database. Figure 4-115 illustrates a typical network architecture with BOSS components.
Figure 4-115: BOSS Network Architecture
In CloudCore, when you click on the BOSS selection in the top bar it opens the BOSS menu. If the menu is closed,
click on the arrow next to BaiBOSS (Figure 4-116). This section explains the functions for each of the menu items.
Figure 4-116: BOSS Menu
168
4.5.2 Subscriber
4.5.2.1 Description
The BOSS Subscriber menu is used to add new subscribers and to modify, activate/deactivate, or delete
subscribers. There are two ways to add subscribers, individually and using a bulk-upload .csv file with the
subscribers’ information. Before you can add subscribers, there are two other BOSS configuration components
you must complete first - importing the SIM card information (under the Network menu) and creating Service
Plans (under the System menu).
Select Subscriber to open the Subscriber tab, which brings up a list of existing active subscribers (Figure 4-117).
Several actions you can take in the list of subscribers is discussed in section 4.5.2.3 Operations.
NOTE: The Archive tab contains a list of any former subscribers whose accounts have been deleted.
Figure 4-117: Subscriber
4.5.2.2 Add Subscriber

4.5.2.2.1 Add Individual Subscriber
When you add a new subscriber - part of which includes assigning a SIM card - and save the information, the
user and the SIM card will be activated and the user will have access to the network. Also, as soon as the
subscriber's status is active:
• If the CloudKey was entered in the UE's GUI, once the UE is powered on it will trigger the automatic
registration of the UE in the operator’s OMC account.
• The Baicells CloudCore per-active-user billing to the operator begins.
To add a new subscriber, click on the + Add icon and enter the subscriber’s information in the fields shown in
Figure 4-118 and Figure 4-119. Notice the two fields highlighted in red. These are mandatory fields where you
select an imported SIM card IMSI number and either use the default service plan ($0 billing) or assign a service
plan that you created (Figure 4-120). When you save the subscriber information, their account will be activated
by default. To deactivate a user, go to the Operations > Active/Deactive.
NOTE: It may take the GUI a few minutes to refresh the subscriber's status from inactive to active.
The cpeName Switch field is one you can toggle on/off. When on, the CPE name for this user is synchronized
with the CPE name in BOSS, and vice-versa. If you want to enter a cpeName (field below it) for this subscriber,
toggle it on. After making your selections, click on Yes or Save to save the configuration.
169
Figure 4-118: + Add Subscriber (1 of 3)
170
171
4.5.2.2.2 Bulk Import Subscribers
Bulk import allows you to upload multiple subscribers' information simultaneously using an Excel template. This
function should be used for those subscribers who will be assigned the same service plan.
Click on the Import icon shown on the upper right side of the Subscriber window (Figure 4-121).
Figure 4-121: Import
In the dialogue window that opens, scroll down to Export Template to save the template file to your computer
(Figure 4-122). In the template file that you saved, enter the subscribers' information and save the file again.
Figure 4-122: Export Template
Back at the top of the bulk subscriber window, the Active Type radio button will be enabled and will display
below it any existing service plans (Figure 4-123). Use the search bar to locate a specific service plan in the list.
Select a service plan to assign to the subscribers. Once the subscribers are assigned a service plan and make
their payment, they will have full network access as defined by their assigned plan.
Next, click on the Import button to upload the bulk subscriber information that you saved in the template. The
result of the import action will display to indicate whether or not the import was successful.
172
Figure 4-123: Import Bulk Subscribers
4.5.2.3 Operations
In the list of subscribers, under the Operations column you can click on the 3 vertical bubbles icon to open a
menu of actions you can take on that subscriber: Change Service Plan, Active, Detail, Edit, Delete, and ResetPwd
(Figure 4-124). Each action is explained in this section.
173
4.5.2.3.1 Change Service Plan
To change an existing subscriber's service plan, under Operations select Change Service Plan. This opens to the
View window at the Service Plan tab (Figure 4-125). Use the pen icon under Operations to change the user's
assigned service plan. This will bring up a list of existing service plans. Use the search bar to find the name of
the service plan you want, and then select the radio button next to it and click on Choose (Figure 4-126).
Figure 4-125: Change Service Plan (1 of 2)
Figure 4-126: Change Service Plan (2 of 2)
4.5.2.3.2 Active
When you add a new subscriber and assign an IMSI number, the subscriber by default is activated in BOSS. There
may be times when you need to deactivate a user, perhaps temporarily (did not pay bill, for example). To toggle
between deactivate and activate, use the Operation > Active function You will receive a system prompt asking if
you are sure you want to take the action (Figure 4-127).
174
Figure 4-127: Operation > Active Example
4.5.2.3.3 Detail
Selecting Operation > Detail displays 4 tabs of information concerning the subscriber: Overview, Change SIM
Card, Service Plan, Invoices, and Account.
4.5.2.3.3.1 Overview Tab
The Overview tab presents the subscriber’s Contact Information, which you can edit by selecting the Edit button
(Figure 4-128), and their Account Balance, current Service Plan, and Invoices (Figure 4-129).
Under Account Balance, you can select Recharge to record a subscriber’s payment (Figure 4-130). The two
options under the Method pull-down field are Cash and Voucher Card.
You also have the ability to modify the subscriber’s service plan using the Modify button. Under Invoices, click
on the See All button to get a list of all invoices in the subscriber’s history. When you do this, you are also
presented with an Export icon if you want to export the information to a file.
Figure 4-128: View > Overview (1 of 2)
175
Figure 4-129: View > Overview (2 of 2)
Figure 4-130: Recharge
4.5.2.3.3.2 Change SIM Card Tab

The Change SIM Card tab initially will present the current SIM card IMSI information. To change the IMSI, select
the Revise Again button, enter the “new” IMSI, click on the Query icon, and when the correct IMSI is found,
select OK. Refer to Figure 4-131.
176
NOTE: Taking this action assumes you already uploaded in BOSS the information for the SIM card to be
used. Refer to section 4.5.4 Network.
Figure 4-131: View > Change SIM Card
4.5.2.3.3.3 Service Plan Tab

This function is the same as was explained for Operations > Change Service Plan. It is just another way to change
a subscriber's service plan.
In the Detail > Service Plan tab, you will see information about the subscriber’s current service plan, such as
price per month, start and end date, and UE device serial number (Figure 4-132). Use the pen icon under
Operation to edit the information. Use the + Add icon to see a list of available service plans and choose one for
this subscriber (Figure 4-133).
Figure 4-132: Service Plan (1 of 2)
177
Figure 4-133: Service Plan (2 of 2)
4.5.2.3.3.4 Invoices Tab

Under the Invoices tab you can see the subscriber's list of invoices, with details such as invoice number, status,
balance, due date, etc. Use the Export button to export the invoice information to a file on your computer (Figure
4-134).
Figure 4-134: Invoices Tab
4.5.2.3.3.5 Account Tab

In the Account tab, if the subscriber has an unpaid balance you can use the Recharge button to charge the
account. If the subscriber has a credit balance, you can use the Refund button to credit the account. Use the
Query function to search for a list of billing transactions within a range of dates. The Reset button may be used
to clear previous query results. Use the Export button to export the results to a file that you can save on a
computer. Refer to Figure 4-135.
Figure 4-135: Account Tab
178
4.5.2.3.4 Edit
Under Operation, if you select Edit it will open the subscriber Identification and Contact Address fields (Figure
4-136 and Figure 4-137). Notice in the cpeName Switch field, you can toggle on/off the field below it where you
can enter the CPE name the subscriber uses. When set to On, the cpeName field becomes editable.
Figure 4-136: Edit (1 of 2)
179
Figure 4-137: Edit (2 of 2)
4.5.2.3.5 Delete
If you select Operation > Delete, the system will prompt you to ensure that is the action you want to take (Figure
4-138). If you select OK, the user’s account information will be moved to the Archive tab.
Figure 4-138: Delete
180
4.5.2.3.6 Reset Password
When you select Operation > ResetPwd, it opens the window shown in Figure 4-139.
4.5.3 Network
4.5.3.1 Overview
In the same way that mobile phones use Subscriber Identity Module (SIM) cards - also referred to as Universal
SIM (USIM) - in their handsets, each network subscriber provided with the Baicells broadband wireless access
user equipment (UE) uses a SIM card they get from the operator. The operator purchases packs of SIM cards
from Baicells or one of its distributors.
The SIM card fits into the Baicells UE (Figure 4-140) and uniquely identifies that subscriber to the network via
an International Mobile Subscriber Identity (IMSI) number. The SIM card also contains a unique International
Mobile Equipment Identity (IMEI) number that identifies each piece of hardware – in this case, each Baicells UE.
• IMSI = Subscriber (the person)
• IMEI = Hardware (the UE unit)
Figure 4-140: SIM Card Slot
181
The Network menu in BOSS is used to manage SIM cards (Figure 4-141). When you click on this menu the window
displays two tabs, SIM Card and Records (of SIM card transactions). The SIM Card tab is where you view, import,
and manage SIM card information. Once the SIM information, specifically the IMSI, is imported and assigned to
a user, when the UE is installed and powered on it will trigger the automatic registration of the UE in the
operator’s OMC account. This is part of the CloudKey activation process described under the eNB and UE GUI
sections of this document.
NOTE: In the BOSS GUI, SIM Code and IMSI show as two different fields in some windows but are the
same number and mean the same thing.
An operator can upload the SIM card numbers into the Baicells Business & Operations Support System (BOSS)
as a batch or individually using one of two methods presented in section 4.5.4.2.
After importing the SIM card information, when you add a new subscriber in BOSS you will be able to select one
of the SIM card numbers, and once all information is entered and saved the SIM card and the user are then
activated and the user will have access to the network.
If SIM cards have previously been imported, the window will display a list of those SIM cards. The list provides
information such as IMSI number, active status, operator, etc., as shown in Figure 4-141.
Figure 4-141: SIM Card
Use the search field or the Advanced Query function to find specific SIM card information or to narrow the list
using additional fields - SIM Code/IMSI number, status, or a range of SIM card numbers (Figure 4-142).
Figure 4-142: Advanced Query
182
4.5.3.2 Import SIMs
Adding SIM cards to BOSS employs an import function. To import the SIM information, in the main window click
on the Import button. This opens a dialogue window (Figure 4-143). You can choose between two Apply Mode
methods:
1. Active [Activate] Code Import – allows you to import a batch of SIM cards in multiples of 10 (e.g.,
10, 20, 30, etc.) all at once using a Baicells activation code.
2. File Import – allows you to upload a file of individual IMSI numbers if you did not purchase a pack
of 10 SIMS and do not have an activation code.
Even if you have an activation code, you could still choose to use the file import method; however, it would not
be as expedient as simply activating the codes using the code number.
Figure 4-143: Apply Mode
4.5.3.2.1 Active Code Import

To import SIM cards using an activation code for a group of 10, 20, 30, etc. SIM cards at a time, go to BOSS >
Network > SIM Card. Click on Import, and select Active Code for the Apply Mode. Enter the code you received
from Baicells, and click on Submit (Figure 4-144).
Figure 4-144: Active Code Import
4.5.3.2.2 File Import

To import a file with the list of individual SIM card IMSI numbers:
1. In BOSS, go to Network > SIM Card (Figure 4-145).
2. Click on the Export icon, scroll down the window, and select Export Template.
3. Save the template to your computer without changing the file name.
183
4. Enter the IMSI number(s) in the file.
5. Select Import to navigate to your file and import it.
6. You will get a dialog box saying how many SIM cards have been added successfully. Click on OK.
NOTE: If an operator attempts to import SIM cards that do not belong to them, the system will auto-
generate an audit request to the Baicells super administrator. On a case-by-case basis Baicells Support
may be able to assist you in importing SIM cards from other vendors. Open a support ticket to request
this assistance.
Figure 4-145: File Import
4.5.3.3 Records
The Records tab lists all SIM card related transactions for that operator's BOSS account. The type of information
displayed is shown in Figure 4-146. You again have a search bar and an advanced query function to find specific
SIM card records based on transaction batch number, SIM code range, or SIM card status.
Figure 4-146: Records
184
4.5.4 System
The BOSS System menu (Figure 4-147) enables you to define subscriber Service Plans, configure Security
parameters for users and user groups, and view activity Logs for each subscriber (e.g., password resets, service
plan changes, etc.).
4.5.4.1 Service Plans

BOSS is preconfigured with a default service plan set to $0 billing. This plan may be used during free trials or
testing. To assign a billing plan to your subscribers, in BOSS you can create different service plans and billing
packages. BOSS supports a time-based plan with a month-to-month service renewal window.
BOSS does not currently support direct billing, but it can be integrated with third-party billing management
systems (refer to the BOSS API Manual). The subscriber’s information is then relayed to the third-party application.
Look at the service plan fields in BOSS (Figure 4-148) to ensure you have the necessary information. Use the
search bar or Advance Query function to narrow the list of service plans (Figure 4-149).
Figure 4-148: Service Plans (1 of 2)
185
Figure 4-149: Advance Query
To view or configure service plans, in BOSS go to System > Service Plans, and click on the + (Add) icon to create
each plan. As you add each subscriber (covered in the next section), along with the IMSI you will select one of
the service plans. Refer to Figure 4-150.
Figure 4-150: Add New Service Plan
To add a new service plan, select the + Add icon to open the dialogue window (Figure 4-151). The system will
assign a Product ID. A star next to a field indicates the information that you must enter before you can save the
configuration. Enter a product name, price (per period), the options for downlink and uplink speeds (next
paragraph), and the period.
For the Speed UL and Speed DL fields you can Limit or Unlimit the data throughput of the service plan. If you
select Limit, enter the UL or DL speed in Mbps. The speed equates to the bandwidth that subscribers with this
service plan will receive when uploading data to the network (UL), e.g., 5 Mbps or 10 Mbps, or when
downloading data from the network (DL), e.g., 15 Mbps or 20 Mbps.
186
Typically, users will download data more often than upload data, and for that reason the DL rate limit is usually
a higher bandwidth. The maximum UL and DL limits are determined by several factors, including which
equipment models are in your network. The speed fields support up to 3 decimal points (e.g., 0.001 Mbps for
UL Rate Limit means the user would get a maximum of 125 bps on the uplink).
Click on Submit to save the new service plan. The plan is automatically activated and will display in the list of
service plans on the main page.
Figure 4-151: Add Service Plan
Under the Operation column you can disable, edit, delete, or set the service plan as the default (Figure 4-152).
Taking the action to disable, delete or set the default pops open a dialogue box asking if you are sure you want
to take the action. If you do, click on OK. The edit function will open the Edit Service Plan window, showing the
same fields as were presented when you added the service plan.
187
4.5.4.2 Security
In the System > Security sub-menu are three choices: User, User Group, and Role Set (Figure 4-153). Each of
these functions is explained in this section.
Figure 4-153: Security
4.5.4.2.1 User Account

Selecting User Account enables you to view a list of subscribers in the operator’s network (Figure 4-154). The
information includes the Account Code, Account Name, User Group to which each subscriber is assigned, Mobile
Phone number, ID Number, Status, and E-mail address. Use the search field to search for a subscriber based on
account code or name.
Figure 4-154: User Account
4.5.4.2.2 User Group

System > Security > User Group works much the same way as User Account, but provides a list of user groups
and you have options under Operation to view, edit, or delete the group (Figure 4-155).
188
Figure 4-155: User Group
When you select Operation > View it brings up a list of users in that group, showing each user’s last login time
and the list of role sets for this user group (Figure 4-156).
NOTE: You cannot edit or delete the default user group. Users who are not assigned to an operator-
defined group are automatically added to the default group.
Figure 4-156: View User Group
To add a new user group from this menu, click on the + Add icon, enter the basic information, and select the role
set (Figure 4-157).
189
Figure 4-157: + Add User Group
4.5.4.2.3 Role Set

Selecting System > Security > Role Set displays a list of role sets already defined (Figure 4-158). Use the + Add
icon to add a new role set (Figure 4-159). Click on the check box next to each menu item you wish for users
assigned this role set to be able to read and/or write (edit). To save the new role set, click on Yes.
Figure 4-158: Role Set
190
Figure 4-159: + Add New Role Set
4.5.4.3 Logs
The event logs under BOSS > System > Logs display information about any action in BOSS that was taken for a
given subscriber or service plan (Figure 4-160). The system will list details about any actions taken concerning a
subscriber; for instance, if you change a subscriber’s service plan, the event log reflects details about the action,
such as old and new service plan names, and date and time of the change. You can query or use advanced query
to locate a subscriber’s records by name, SIM code, and so forth.
Figure 4-160: Logs
191
4.5.5 Help
When you click on Help > About, the system displays the BOSS software version level (Figure 4-161).
Figure 4-161: Help
192
Appendix A: UE Cat6/7 GUI
The GUI for Cat6/7 UEs takes on a different appearance and menu flow compared to Cat4 UEs. Some
functionality has been added or modified. This appendix shows the UE GUI tabs, menus, and fields for an Atom
Cat6/7 device. The Cat6/7 model used for screenshots was EG7010A-M11, an outdoor high-gain UE.
1. Cat6/7 Login & Status Icons
The Login screen functions the same as for Cat4 UEs but has the newer look-and-feel (Figure A-1).
Figure A-1: Cat6/7 Login
After logging in, the landing page is the Status > System Info window shown in Figure A-2. First, though, look at
the icons at the top of the window.
Figure A-2: Cat6/7 Landing Page
In the top bar are 3 UE status icons: PIN, signal strength, and network connection. Refer to Figure A-3. These
icons provide an at-a-glance indication of whether the UE is online or not, the signal level it is receiving, and
connection or disconnection to/from the network.
193
Figure A-3: Cat6/7 Status Icons
2. Cat6/7 Online Help

Whereas the Cat4 UE GUI showed only the software version when you clicked on Help, in Cat6/7 the Help
function provides online information about the client GUI specifications and configuration fields. When you click
on Help, it opens a new tab to display a Help menu (Figure A-4). The initial landing page is the top menu,
Foreword. Figure A-5 shows the expanded sub-menus. Help includes recommended best practices.
Figure A-4: Cat6/7 Online Help Menu & Landing Page
Figure A-5: Cat6/7 Online Help Expanded Sub-Menus
194
3. Cat6/7 Wizard Tab
The Cat6/7 GUI brings a new function, Wizard (Figure A-6). Wizard is a quick and easy way to configure the UE
using standard configuration values. On the side of the Wizard window are the same functions shown in the tabs
across the top of the GUI page: Status, Settings, etc. This makes it easy to change any of the default settings
during initial setup.
Figure A-6: Cat6/7 Wizard
Follow the steps below to run the Wizard setup.

Step 1: PIN - The Wizard function first displays PIN, showing the USIM Card Status and whether a PIN to access
the UE has been configured (Figure A-7). The default is Disable.
Figure A-7: Cat6/7 Wizard Step 1
Step 2: Internet - The Internet tab is where you can set the connection mode, either Always on (default) or
Manual (Figure A-8). Any further configuration needed will be performed using the Settings tab.
195
Figure A-8: Cat6/7 Wizard Step 2
4. Cat6/7 Status Tab

4.1 System Info
The Status > System Info menu does not contain configurable fields, but instead displays information fields about
the UE hardware, software, and status (Figure A-9). For example, the Main Board Firmware Version (in this case,
BCE-MD-1.0.1-B036SP28-NA), indicates the software version currently running on the UE.
Figure A-9: Cat6/7 System Info
4.2 Device Status

This sub-menu shows the Internet connection status, including the current IP address and DNS servers. It also
shows the LAN IP address (IPv4 and IPv6), netmask, and MAC address. See Figure A-10.
196
Figure A-10: Cat6/7 Device Status
4.3 DHCP Client List

The DHCP client information includes the host name, MAC address, IP address, and Lease Time (Figure A-11).
Figure A-11: Cat6/7 DHCP Client List
4.4 LTE Status

In the Cat6/7 GUI you will see some new fields that are not displayed at this time in the Cat4 GUI (Figure A-12):
• Service Status of the network connection, either valid, restricted, or no service
• MIMO Status related to the UE's antenna technology
• RRC State, either connected or idle
• EPS Mobility Management (EMM) State for connection management, either registered or unregistered
• Cell Radio Network Temporary Identifier (C-RNTI) connection status, unique UE ID assigned by the eNB
• CQI1 and CQI2, which indicate the wideband and subband channel and channel edge quality
• Secondary Carrier Component (SCC) data related to Carrier Aggregation (CA), where the index will be 1
when using CA
• Roaming yes, no, or NA
• Transmission Mode between UE and eNB, e.g., SISO, MIMO
• Rank Number shows the number of data streams being used (1 = one data stream, 2 = 2 data streams,
4 = 4 data streams)
• Handover State during roaming
197
Figure A-12: Cat6/7 LTE Status
4.5 VPN Status

If a VPN has been configured, this menu will display the operation mode for VPN traffic: NAT, router, or tunnel
(Figure A-13).
Figure A-13: Cat6/7 VPN Status
4.6 Firewall Status

If a firewall is enabled, this menu displays information related to the firewall configuration (Figure A-14). Refer
to section 5.6.4 System Security for field descriptions and options.
Figure A-14: Cat6/7 Firewall Status
198
5. Cat6/7 Settings Tab
The Settings tab (Figure A-15) is where you configure all of the parameters for the UE if different from the
defaults set up by the Wizard utility.
Figure A-15: Cat6/7 Settings Tab
5.1 LAN Settings

5.1.1 LAN/DHCP
In this menu you can enable/disable a DHCP relay function (Figure A-16). Changes to these parameters may reset
the server. If you change the gateway IP address and mask, some functions such as DMZ and port forwarding
may become unavailable and will have to be reset.
If you enable DHCP Server, the UE will automatically assign an IP address to users. Baicells recommends not
putting the LAN IP and DHCP IP addresses in the same network segment with the UE WAN IP. Also, avoid WAN
IP conflicts between LAN IP and device IP.
Figure A-16: Cat6/7 LAN
5.1.2 DHCP Static Leases

You can enable and assign up to 16 static leases (Figure A-17). Any currently configured static leases will
appear in the bottom part of the window.
199
Figure A-17: Cat6/7 DHCP Static Leases
5.2 LTE
5.2.1 Network Selection
As with Cat4 UEs, you can configure the UE to automatically search for available network connections or
require users to connect to a network manually (A-18).
Figure A-18: Cat6/7 Network Selection
5.2.2 Internet Settings

This menu is new in the Cat6/7 GUI (Figure A-19). Here, you can enable roaming and configure
Internet/network connection settings for mobile users. During roaming, the Internet connection can be set as
always on or manual; and the data connection to specific websites can also be set to always on or manual. The
PDP field allows you to permit IPv4, IPv6, or IPv4v6 traffic.
200
Figure A-19: Cat6/7 Internet Settings
5.2.3 APN Profile

You can configure 8 APN gateways, and assign an authorization type as either null, auto, CHAP, or PAP (Figure
A-20). Any APNs already configured appear at the bottom of the window.
Figure A-20: Cat6/7 APN Profile
5.2.4 PIN Management

Requiring users to enter a PIN to access the network through the UE is disabled by default (Figure A-21). When
enabled, users must enter a PIN number and are limited to the number of "wrong" entries before being locked
out. If locked out, the user must contact their service provider and request the USIM card's PUK code.
201
Figure A-21: Cat6/7 PIN Management
The various USIM Card Status states are:

• No USIM Card inserted
• PIN Disabled, no need to verify
• PIN Required
• PIN Verified
• PIN Locked, need PUK code to unlock
• PIN Permanently Locked - this occurs when the user has had to request and enter the PUK code more
than 10 times, in which case the USIM is locked forever
5.2.5 Cell Selection
The Scan Mode defaults to Full Band (Figure A-22). You can change it to a dedicated EARFCN or to PCI lock. If
you change the Scan Mode setting, you will see a message stating that the UE is initializing and then the new
setting will take effect. Notice when PCI lock is selected, the Cat6/7 GUI now displays a Site Survey window
showing the eligible eNBs and their RSSI, RSRP, and RSRQ data. The eNB that is selected is indicated as well.
Figure A-22: Cat6/7 Cell Selection
202
5.2.6 SIM Lock
The SIM Lock feature can be enabled to lock the UE to a specific SIM card IMEI code (Figure A-23). When
enabled (by selecting SIM Lock Check), you must enter the operator's PLMN ID and click on Apply.
Figure A-23: Cat6/7 SIM Lock
5.2.7 MTU
The Maximum Transmission Unit (MTU) is new in the Cat6/7 GUI (Figure A-24). You can enter a value between
1280 and 1500 bytes to set the maximum data packet size that can be transmitted to/from this UE.
Figure A-24: Cat6/7 MTU
5.2.8 Advanced
In the Advanced sub-menu (Figure A-25) you can identify the MIMO / Carrier Aggregation (CA) mode as either
Auto, 4x4 MIMO, or 2CA. The Cat6/7 UE has 4 antenna ports. The 4x4 MIMO selection may be used when
communicating with single carrier eNBs. The 2CA selection is for Carrier Aggregation (CA) and means each
carrier will use 2x2 MIMO. Leaving the selection to Auto will automatically set the mode based on whether
single carrier or CA can be used.
Figure A-25: Cat6/7 Advanced
203
5.3 WAN Settings
5.3.1 Operation Mode
A Cat6/7 UE includes additional options for operation mode compared to the Cat4 UE. Cat4 gives you the option
of NAT or Bridge mode. Cat6/7 includes not only NAT Mode and Bridge Mode but also Router Mode and Tunnel
Mode (Figure A-26). The Tunnel Mode may be either L2TP or Generic Routing Encapsulation (GRE).
If you select a mode that is other than the default NAT Mode, you will see additional fields displayed. Look at
the example for Tunnel Mode in Figure A-27.
NOTE: If you change the mode, you will receive a warning that the new mode requires the UE to reboot
to take effect. A reboot disrupts service.
Figure A-26: Cat6/7 Operation Mode
Figure A-27: Cat6/7 Tunnel Mode Example
5.3.2 DNS Mode

You can manually configure a primary DNS server and a secondary DNS server, or leave the default Automatic
DNS mode (Figure A-28).
204
Figure A-28: Cat6/7 DNS Mode
5.4 Route Settings

The only permitted Route Type is LAN, but you can add up to 16 rules. Any routes already configured appear at
the bottom of the window (Figure A-29).
Figure A-29: Cat6/7 Route Settings
5.5 NAT
5.5.1 Port Forwarding
By default, Port Forwarding is disabled. When you enable it, additional fields are displayed for configuring the
forwarding information (Figure A-30). If configured, Port Forwarding takes precedence over the DMZ function;
therefore, packets that conform to the forwarding rules will skip the DMZ rules. Please refer to the online Help
function for more information on using this feature.
205
Figure A-30: Cat6/7 Port Forwarding
5.5.2 DMZ
If you enable a DMZ, enter the DMZ address as shown in Figure A-31.
Figure A-31: Cat6/7 DMZ
5.5.3 ALG
The ALG settings are the same for Cat6/7 as for Cat4 (Figure A-32). Refer to the online Help for information
about the ALG function.
206
Figure A-32: Cat6/7 ALG
5.5.4 Port Trigger

The Port Triggering feature is an option that is disabled by default in Cat6/7 as it is in Cat4 (Figure A-33). When
you enable it, additional configuration fields appear. The fields are described in the online Help.
Figure A-33: Cat6/7 Port Trigger
5.6 Security Settings

5.6.1 IP Filtering
There is no difference in how IP Filtering works in Cat6/7 GUI when compared to Cat4, but the layout is
different (Figure A-34). The maximum number of filters is 16. If you use an IP Filter white list, you must enable
the SPI Filter firewall function under Security Settings > System Security; otherwise, the UE will not be able to
connect to the network.
207
Figure A-34: Cat6/7 IP Filtering
5.6.2 IPv6 Filtering

The IPv6 Filtering menu is new in the Cat6/7 GUI. The fields, options, and functionality are almost exactly the
same as for IP Filtering covered in section 5.6.1; however, the protocol selections are slightly different (Figure
A-35). The maximum number of filtering rules for IPv6 is 16.
Figure A-35: Cat6/7 IPv6 Filtering
208
5.6.3 MAC Filtering
MAC Filtering is no different in the Cat6/7 GUI vs Cat4. If enabled, you will enter the MAC addresses you wish
to allow or deny (Figure A-36).
Figure A-36: Cat6/7 MAC Filtering
5.6.4 URL Filtering

URL Filtering enables you to blacklist and/or whitelist web addresses (Figure A-37).
Figure A-37: Cat6/7 URL Filtering
5.6.5 System Security

This new menu in the Cat6/7 GUI allows you to set a security profile level for the UE, making it faster and easier
to configure the various security settings. The types of security settings are remote web login, access control list,
block port scanner, block SYN flood, and SPI firewall. Block Port Scanner prevents malicious scanning of the UE
ports. Block SYN Flood prevents denial-of-service attacks. Stateful Packet Inspection (SPI) Firewall tracks the
status of the various network connections that pass through the firewall.
The security profile may be set to None, Medium, High, or Custom. With the exception of Security Level = None,
you can enable/disable specific security features in the lower part of the window (Figure A-38). Notice that if
you select Security Level = Custom, the default values for the fields in the lower part of the window change.
209
The 4 Security Level settings are described below and in the online Help:
• High (default) - Enables ACL, Block Port Scanner, Block SYN Flood, and SPI Firewall
• Custom - You can configure the security rules as needed
• None - Disables the firewall
• Medium - Enables Block Port Scanner and Block SYN Flood
Figure A-38: Cat6/7 System Security
5.6.6 Connect Limit

The Cat6/7 GUI includes this new Connect Limit menu where you can configure up to 16 rules for limiting
network connections through the UE (Figure A-39). The rules you create appear at the bottom of the window.
Figure A-39: Cat6/7 Connect Limit
210
5.6.7 Schedule
In the Cat6/7 GUI you can now configure up to 16 schedules to limit when users may access the network
through the UE (Figure A-40). You can set up each rule to occur only one time or on a cycle.
Figure A-40: Cat6/7 Schedule
5.7 Advanced
5.7.1 NTP
The NTP settings in Cat6/7 are slightly different from Cat4 with the addition of the Mode field (Figure A-41). You
can set the timing to sync from the network or to be set manually. If set the mode to manually, you will be able
to enter the time manually, like you can do on a personal computer.
Note the Daylight Savings Time (DST) field which you can enable to automatically update the NTP timing at the
onset and end of DST.
Figure A-41: Cat6/7 NTP
211
5.7.2 TR-069
There is no difference in the TR-069 configuration fields in Cat6/7 vs Cat4 (Figure A-42).
Figure A-42: Cat6/7 TR-069
5.7.3 TR-069 Certificate

This Cat6/7 menu item gives you a place to upload the TR-069 certificate in the UE (Figure A-43).
Figure A-43: Cat6/7 TR-069 Certificate
5.7.4 DDNS
Dynamic Domain Name Server (DDNS) is the DNS used by the APN to which the UE is connected, in most cases
the EPC through the TR-069 connection. Whereas in the Cat4 GUI you could define the DNS as manual or primary
and secondary under the WAN settings, in the Cat6/7 DDNS menu you can identify dynamic or No-ip service
type, set up a username and password, etc., per Figure A-44. The No-ip setting enables external traffic to access
the UE based on a domain name - e.g., using the user's name.
212
Figure A-44: Cat6/7 DDNS
5.7.5 Account
The Account menu in Cat6/7 includes one new field, Modify Web Lock Time (Figure A-45). You can configure a
timeout period indicating how long users may access the network through the UE. The online Help gives the
password rules, e.g., 8-15 characters, mix of numbers and letters, etc.
Figure A-45: Cat6/7 Account
6. Cat6/7 Statistics Tab

The Statistics tab in Cat6/7 reports both WAN and LAN data (Figure A-46). The data is refreshed real-time. If
you click on the Clear button, it will delete all of the data and restart the collection.
213
Figure A-46: Cat6/7 Statistics
7. Cat6/7 Maintenance Tab

The Maintenance tab is where the backups, upgrades, and other use-when-needed functions reside in the
Cat6/7 GUI (Figure A-47). Note that when importing configuration data, as soon as the file is uploaded the UE
will reboot automatically, thus disrupting service. Do not power off during the recovery operation.
Figure A-47: Cat6/7 Maintenance Tab
7.1 Backup Settings

In the Cat6/7 GUI use this menu to export (save) the configuration settings or import existing (saved) settings
(Figure A-48).
214
Figure A-48: Cat6/7 Backup Settings
7.2 Update
There is no difference in how you perform an upgrade or rollback in Cat6/7 (Figure A-49). Simply choose the
image file, and click on Update.
Figure A-49: Cat6/7 Update
7.3 Web Service

Enabling Web Service so that you can access the UE remotely functions the same way in Cat6/7 (Figure A-50).
Figure A-50: Cat6/7 Web Service
7.4 System Log

The display of logs in Cat6/7 looks different from Cat4 but provides relatively the same information (Figure A-
51). Selecting the check box for Settings opens additional fields such as export, clear, or filter log information.
215
Figure A-51: Cat6/7 System Log
7.5 System Messages

The System Messages function is new in Cat6/7, and is used for troubleshooting (Figure A-52).
Figure A-52: Cat6/7 System Messages
7.6 Diagnostics
In Cat6/7 you can run a TCP dump, ping, or traceroute using the Diagnostics menu (Figure A-53).
216
Figure A-53: Cat6/7 Diagnostics
7.7 Ping Watchdog

There is no change to the Ping Watchdog feature in Cat6/7 (Figure A-54).
Figure A-54: Cat6/7 Ping Watchdog
7.8 Reboot
The Reboot menu is for both the restore and reboot functions (Figure A-55). When restoring, if the page does
not refresh automatically within 60 seconds, enter the login address manually.
217
Figure A-55: Cat6/7 Reboot
218
Appendix B: Abbreviations & Acronyms
Abbreviations and acronyms used in this document or related to LTE are listed in alphabetical order and
described in the table below.
Acronym Abbreviation for Description

1xEV-DO 1x Evolution for Data Optimized 1xEV-DO is a telecommunications standard for the wireless
transmission of data through radio signals, typically for broadband
Internet access
2CA 2 Carrier Aggregation In Carrier Aggregation (CA) mode, the eNB uses 2x2 MIMO on each
carrier.
3GPP Third-Generation Partnership 3GPP is a standards body that works within the scope of the
Project International Telecommunications Union (ITU) to develop third-
generation and later wireless technologies that build upon the base
provided by Global System of Mobile Communications (GSM). The
group is responsible for the Universal Mobile Telecommunications
System (UMTS) standard, as well as High-Speed Downlink Packet
Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), Evolved
High Speed Packet Access (HSPA+), and LTE.
3GPP2 Third-Generation Partnership 3GPP2 is a collaboration between multiple telecommunications
Project 2 associations to make a globally applicable third-generation (3G)
mobile phone system specification within the scope of the
International Telecommunications Union’s (ITU) IMT-2000 project.
4G Fourth-Generation Wireless 4G is a mobile communications standard intended to evolve 3G
Systems technology, allowing wireless Internet access at a much higher
speed.
AAA Authentication, Authorization, AAA is a framework for controlling access to computer resources,
and Accounting enforcing policies, auditing usage, and providing the information
necessary to bill for services.
AC Authentication Center The AC validates any security information management (SIM) card
attempting network connection when there is a live network signal.
ACK Acknowledge or A flag used in the Transmission Control Protocol (TCP)
Acknowledgement to acknowledge receipt of a data packet.
ALG Application Layer Gateway One or more application protocols may be used to augment a
firewall by assigning a public address to a computer(s) inside a
private network, or to filter Network Address Translations (NAT) used
by a network device. Examples of application layer control data
protocols are FTP, H.323 ALG, SIP, and PPTP.
AM Acknowledged Mode AM requires the receiver of information to send continuous
notifications to the sender that indicate it has successfully received
the information.
AMBR Aggregate Maximum Bit Rate AMBR is the maximum possible bit rate configured by the LTE
operator for a particular LTE user.
219
AMC Adaptive Modulation and AMC is used to denote the matching of the modulation, coding, and
Coding other signal and protocol parameters to the conditions on the radio
link.
AN Access Network AN is the part of a telecommunications network that connects
subscribers to their immediate service provider.
ANR Automatic Neighbor Relation ANR is a third-generation (3G) telecommunications specification for
automating the identification of an eNB’s neighboring cells
regardless of which Universal Mobile Telecommunications System
(UMTS) technology those eNBs are running. Having ANR capabilities
relieves the operators of having to manually provision each neighbor
cell.
APN Access Point Name An access point (AP) is an eNB gateway between a Global System for
Mobile Communications (GSM), General Packet Radio Service (GPRS),
third-generation (3G) or fourth-generation (4G) mobile network, and
another computer network, frequently the public Internet. An AP
name (APN) is an identifier for a specific AP/eNB.
ARP Address Resolution Protocol ARP is a telecommunication protocol used for resolution of Internet
layer addresses into link layer addresses, a critical function in
multiple-access networks.
ARP Allocation and Retention Priority level assigned to bearer traffic. In a mobile network, ARP
Priority decides whether to accept a request to establish a bearer or reject
the request when resources are limited.
ARQ Automatic Repeat reQuest ARQ is an error-control method for data transmission that uses
acknowledgements and timeouts to achieve reliable data
transmission over an unreliable service.
AS Access Stratum The AS is a functional layer in the Universal Mobile
Telecommunications System (UMTS) and LTE wireless telecom
protocol stacks between radio network and user equipment.
AS Application Server An AS is a component-based product that resides in the middle tier
of a server-centric architecture. It provides middleware services for
security and state maintenance, along with data access and
persistence.
BCCH Broadcast Control Channel BCCH is a logical broadcast channel used by the eNB in a Global
System for Mobile Communications (GSM) network to send
information about the identity of the network. This information is
used by a mobile station to get access to the network.
BCH Broadcast Channel A BCH is a downlink channel in a Global System for Mobile
Communications (GSM) that is used by the eNBs to provide signaling
information to the mobile stations.
BER Bit Error Rate A BER is the percentage of bits that have errors relative to the total
number of bits received in a transmission, usually expressed as ten to
a negative power.
BLER Block Error Rate BLER is used in LTE/4G technology to identify the in-sync or out-of-
sync status during radio link monitoring. It is a measure of how
220
successful a data transmission is over the air at the Physical/MAC
layer level.
BOSS Business Operations Support BOSS is a Baicells CloudCore application that enables operator
System administrators to add, modify, and delete subscriber information and
service plans. Administrators also use BOSS to activate each
Subscriber Identification Module (SIM) card, a chip that the end-user
inserts in the UE to uniquely identify that subscriber and UE.
BPSK Binary Phase Shift Keying BPSK is a digital modulation scheme that conveys data by changing,
or modulating, two distinct phases of a reference signal (the carrier
wave).
BW Bandwidth BW refers to the range of frequencies within a given band used for
transmitting a signal.
CA Carrier Aggregation A wireless technology used in a two-carrier eNodeB that allows
operators to aggregate contiguous and non-contiguous channels in
order to provide one wider channel and more capacity per cell.
CBRS Citizens Broadband Radio A 150 MHz wide channel of the 3.5 GHz (3550-3700 MHz) band in the
Service United States that was only recently made available to enterprises by
the Federal Communication Commission (FCC). A new Spectrum
Access System (SAS) technology is in development using highly
automated methods to dynamically allocate the prized CBRS
spectrum on a tiered, priority, licensed basis, while minimizing
interference with other CBRS and incumbent users.
CBSD CBRS Service Devices The equipment certified to provide CBRS services
CDMA Code Division Multiple Access CDMA is a wireless technology where several transmitters can send
information simultaneously over a single communication channel.
CE Customer Edge The CE is the router at the customer’s premises that is connected to
the edge of a service provider’s Internet Protocol (IP) / Multiprotocol
Label Switching (MPLS) network. MPLS is a type of data-carrying
technique for high performance telecommunications networks.
CEU Common Equipment Unit Generic term describing devices that share resources, in this case
spectrum. The term is used in relation to Inter-Cell Interference
Coordination (ICIC), a technique that applies restrictions to the radio
resources to improve channel conditions that would otherwise cause
interference.
CFI Channel Format Indicator In LTE, the CFI value defines the time span, in Orthogonal Frequency
Division Multiplexing (OFDM) symbols, of the physical downlink
control channel transmission (the control region) for a downlink
subframe.
CG Charging Gateway An open system that formats and integrates charging data records
between standard and non-standard systems
CINR Carrier-to-Interference-plus- CINR is a measurement of multiple subcarriers; it reflects the signal
Noise Ratio quality of the LTE carrier system.
CN Core Network A CN is the central part of a telecommunications network that
provides various services to customers who are connected through
221
the access network.
CoA Care-of Address The CoA identifies a mobile node’s current point of attachment to
the Internet and makes it possible to connect from a different
location without changing the device’s home address.
CP Cyclic Prefix CP refers to the prefixing of a symbol with a repetition of the end. As
a guard interval, it eliminates the inter-symbol interference from the
previous symbol.
CPE Customer Premise Equipment CPE, also called User Equipment (UE), is the equipment used by a
network subscriber to connect to the backhaul carrier network
through the access network.
CPI Certified Professional Installer An installer who is trained and certified to install radio equipment for
the Citizens Broadband Radio Service (CBRS) band.
CQI Channel Quality Indicator The Channel Quality Indicator is a value that indicates how good or
bad the communication channel quality is. The UE sends
measurements (a combination of SNR, SINR, and SNDR) to the eNB
which determine the Modulation and Coding Scheme (MCS) value
that will be used in the downlink. The higher the value, the better the
channel quality. The maximum value is 15.
CRC Cyclic Redundancy Check CRC is an error-detecting code commonly used in digital networks
and storage devices to detect accidental changes to raw data.
C-RNTI Cell Radio Network Temporary C-RNTI is a unique temporary identification used for identifying Radio
Identity Resource Control (RRC) connection and scheduling dedicated to a
particular subscriber.
CS Circuit-Switched CS is a type of network in which a physical path is obtained for and
dedicated to a single connection between two end-points in the
network for the duration of the connection.
CSCF Call Session Control Function The CSCF is responsible for the signaling that controls the
communication of Instant Messaging Service (IMS) user equipment
with IMS enhanced services across different network accesses and
domains.
CS-CN Circuit Switched Core Network In a CS-CN, the bit delay is constant during a connection. No circuit
can be degraded by competing users because it is protected from use
by other users until the circuit is released and a new connection is set
up.
CSI Channel State Information CSI refers to known channel properties of a communications link. The
information describes how a signal propagates from the transmitter
to the receiver.
DCCH Dedicated Control Channel The DCCH is a single timeslot on a radio frequency (RF) carrier that is
used to convey eight stand-alone dedicated control channels.
DCI Downlink Control Information In LTE, DCI is based upon a process defined as a blind decoding which
depends on several decoding attempts on several Physical Downlink
Control Channels (PDCCH) candidate locations for several defined DCI
formats.
DFT Discrete Fourier Transform The DFT converts a finite sequence of equally-spaced samples of a
222
radio signal into an equivalent length sequence of equally-spaced
samples of the discrete-time Fourier transform (DTFT), which is a
complex-valued function of frequency.
DHCP Dynamic Host Configuration DHCP is a network protocol that enables a server to assign an IP
Protocol address automatically to a computer from a defined range of
numbers configured for a given network.
DL Downlink DL is the direction of traffic flow from the eNB transmitting to one or
more subscribers. Uplink (UL) is the opposite direction, traffic flowing
from the subscriber’s customer premise or user equipment to the
eNB.
DL-SCH Downlink Shared Channel The DL-SCH is the main data bearing channel, which is allocated to
users on a dynamic and opportunistic basis.
DNS Domain Name System A directory of Internet domain names that are translated into IP
addresses
DP Domain Proxy An Internet service used to protect your domain registrant details
DRA Dynamic Resource Allocation DRA is an essential technique to exploit the time-space-frequency
variation in wireless channels by distributing precious radio
resources, such as spectrum and power, either to maximize or
minimize the network performance metrics.
DRX Discontinuous Reception DRX is a method used in communications to conserve energy
use. The user equipment and the network negotiate phases in which
data transfer occurs. At other times the device enters a low power
state.
DS Direct Spread DS systems transmit the message bearing signals using a bandwidth
that is more than the bandwidth that is needed by the message
signal.
DSCP Differentiated Service Code DSCP is a field in an IP packet that enables various levels of service to
Point be assigned to network traffic. This is achieved by marking each
packet on the network with a DSCP code and appropriating to it the
corresponding level of service.
DST Daylight Saving Time Originally started to conserve energy, DST is the practice of
advancing clocks (usually one hour) during summer months so that
evening daylight lasts longer.
DTCH Dedicated Traffic Channel A DTCH is an uplink or downlink communication channel that is only
accessible by one device to transfer user data.
DTX Discontinuous Transmission DTX is a method of momentarily powering down a wireless
device when there is no data throughput.
EARFCN E-UTRA Absolute Radio A unique number given to each radio channel in Global System for
Frequency Channel Number Mobile (GSM) communications. The EARFCN is used to calculate the
exact frequency of the radio channel.
ECM Evolved Packet System (EPS) ECM is the process of identifying, setting up, controlling, and
Connection Management removing a transmission path between two or more points in the
Universal Mobile Telecommunications System (UMTS) evolved
packet system.
223
EIRP Effective Isotropic Radiated EIRP is the product of transmitter power and antenna gain in a
Power certain direction relative to an isotropic antenna. You could use the
EIRP value, for example, to determine if the radio is within regulatory
values.
EMM Enterprise Mobility EMM refers to the people, processes, and technology focused on
Management managing devices, wireless networks, and other computing services
in a business context.
eNB E-UTRAN Node B In LTE, the eNB is a base station that manages radio resources and
mobility in the cell and sector to optimize all the user
communications in a flat radio network structure.
EPC Evolved Packet Core EPC is a framework for providing converged voice and data on a
fourth-generation (4G) LTE network.
EPC-U Evolved Packet Core (EPC) User As part of the 3GPP Standard Release 8, the user data (user plane) is
Plane separated from the signaling (control plane). EPC-U refers to the user
plane.
EPS Evolved Packet System EPS, also called Evolved Packet Core (EPC), is the central network
portion of the Universal Mobile Telecommunications System (UMTS)
LTE mobile communication system. The packet system primarily
transfers packet data between edge networks and the radio access
network (RAN).
E-RAB E-UTRAN Radio Access Bearer The concatenation of an S1 bearer and the corresponding radio
bearer. E-RAB transports the packets of an EPS bearer between a UE
and the EPC, and allows the UE to be tracked as it moves.
ESP Encapsulating Security Payload ESP is a protocol within the Internet Protocol Security (IPSec)
standard for providing authentication, integrity, and confidentiality
of network packet data in IPv4 and IPv6 networks.
EUD End User Device Term used for CBRS certified user equipment
E-UTRA Evolved Universal Mobile E-UTRA is the air interface of 3GPP’s LTE upgrade path for networks.
Telecommunications System
(UMTS) Terrestrial Radio Access
E-UTRAN Evolved Universal Mobile E-UTRAN is the combination of E-UTRA, user equipment, and eNBs.
(UMTS) Terrestrial Radio Access
Network
EV-DO Evolution for Data Optimized EV-DO is the third-generation (3G) telecommunications standard for
the wireless transmission of data through radio signals, typically for
broadband Internet access.
FA Foreign Agent An FA is a router serving as a mobility agent for a mobile node.
FDD Frequency Division Duplex FDD is a method for establishing a full-duplex communications link
that uses two different radio frequencies for transmitter (Tx) and
receiver (Rx) operation.
FDM Frequency Division Multiplexing FDM is a technique for sending two or more signals over the same
radio channel. Each signal is transmitted as a unique range of
frequencies within the bandwidth of the channel as a whole,
224
enabling several signals to be transmitted simultaneously.
FDMA Frequency Division Multiple FDMA is a channel access method used in multiple-access protocols
Access as a channelization protocol. FDMA gives users an individual
allocation of one or several frequency bands, or channels.
FEC Forward Error Correction FEC is a method of obtaining error control in data transmission in
which the source (transmitter) sends redundant data and the
destination (receiver) recognizes only the portion of the data that
contains no apparent errors.
FFT Fast Fourier Transform The FFT is a mathematical method for transforming a function of
time into a function of frequency. Sometimes the method is
described as transforming from the time domain to the frequency
domain.
FMC Fixed Mobile Convergence FMC is the trend towards seamless connectivity between fixed and
wireless telecommunications networks.
FQDN Fully Qualified Domain Name Also known as an absolute domain name, FQDN is a domain name
for a specific computer or host on the Internet that specifies its exact
location in the tree hierarchy of the Domain Name System (DNS).
GBIC Gigabit Interface Converter GBIC is a standard for transceivers, commonly used with Gigabit
Ethernet and fiber channel. By offering a standard, hot swappable
electrical interface, one gigabit port can support a wide range of
physical media, from copper to long-wave, single-mode optical fiber,
at lengths of hundreds of kilometers.
GBR Guaranteed Bit Rate GBR is the minimum bit rate requested by an application. In LTE,
minimum GBR bearers and non-GBR bearers may be provided.
GGSN Gateway GPRS Support Node A GGSN is part of the core network that connects Global System for
Mobile Communications (GSM) based third-generation (3G)
networks to the Internet.
GI Guard Interval GIs are used to ensure that distinct transmissions do not interfere
with one another. These transmissions may belong to different users
(as in Time Division Multiple Access, or TDMA) or to the same user
(as in Orthogonal Frequency Division Multiplexing, or OFDM).
GP Guard Period In Time Division Multiple Access (TDMA), each user’s
timeslot ends with a GP to avoid data loss and to reduce interference
to the following user, caused by propagation delay. Thus, a user’s
timeslot is protected from interference from the preceding user.
GPRS General Packet Radio Service GPRS is a packet-oriented mobile data service on the second-
generation (2G) and third-generation (3G) cellular communication
system’s Global System for Mobile (GSM) communications.
GRE Generic Routing Encapsulation A tunneling protocol developed by Cisco Systems that can
encapsulate a wide variety of network layer protocols inside virtual
point-to-point or point-to-multipoint links over an Internet Protocol
network.
GSM Global System for Mobile A digital mobile telephony system which uses a variation of Time
Division Multiple Access (TDMA) technology. GSM is the most widely
225
used of the 3 digital wireless telephony technologies (TDMA, GSM,
and CDMA) in Europe and other parts of the world.
GT Guard Time GT is the interval left vacant on a transmission channel that can be
used for synchronization and/or compensating for a signal distortion.
GTP General Packet Radio Service GTP is a group of IP-based communications protocols used to carry
(GPRS) Tunneling Protocol General Packet Radio Service (GPRS) within Global System for Mobile
(GSM) communications), Universal Mobile Telecommunications
System (UMTS), and Long-Term Evolution (LTE) networks.
GTP-U General Packet Radio Service GTP-U is used for carrying user data within the General Packet Radio
(GPRS) Tunneling Service (GPRS) core network and between the radio access network
Protocol (GTP) User Plane (RAN) and the core network (CN).
GUMMEI Globally Unique MME Identity The GUMMEI is constructed from the Mobile Country Code (MCC),
Mobile Network Code (MNC), and Mobility Management Entity
(MME) Identifier (MMEI).
GUTI Globally Unique Temporary GUTI is allocated to the user equipment (UE) by the Mobility
User Equipment (UE) Identity Management Entity (MME) and has two components - the Globally
Unique MME Identity (GUMMEI) and the MME temporary mobile
subscriber identity (M-TMSI). While the GUMMEI identifies the MME,
the M-TMSI identifies the UE within the MME.
GW Gateway A GW refers to a piece of networking hardware that is equipped for
interfacing with another network that uses different protocols.
HA Home Agent An HA is a router on a mobile node’s home network that maintains
information about the device’s current location, as identified in its
care-of address.
HA High Availability HA indicates 100% operation, a never-failing component or system
H-ARQ Hybrid ARQ H-ARQ is a combination of high-rate, forward error-correcting code
and Automatic Repeat Request (ARQ) error control. In standard ARQ,
redundant bits are added to data to be transmitted using an error-
detecting code such as a cyclic redundancy check.
HDTV High-Definition Television HDTV is a television display technology that provides picture quality
similar to 35mm film.
H-FDD Half-Frequency Division Duplex H-FDD requires that two communication parties take turns
transmitting data over two separate frequency bands or channels.
HLR Home Location Register HLR is the main database of permanent subscriber information for a
network. The HLR is an integral component of mobile networks.
HO Handoff or Handover HO refers to the process of transferring an ongoing call or data
session from one channel (eNB 1) connected to the core network to
another channel (eNB 2).
HPLMN Home Public Land Mobile The HPLMN identifies the public network in which the subscriber’s
Network (PLMN) profile is held. Users roaming to other networks will receive
subscription information from the HPLMN.
HSDPA High Speed Downlink Packet HSDPA is an enhanced third-generation (3G) communications
Access protocol which allows networks based on Universal Mobile
226
Telecommunications System (UMTS) to have higher data speeds.
HSPA High Speed Packet Access HSPA is a telecommunications technology that allows for data
transmission speeds up to 21 Mbps. HSPA+ (also called Evolved HSPA
or 4G) is a further evolution of HSPA that offers data speeds of up to
42 Mbps.
HSS Home Subscriber Server HSS is the master user database that supports Internet Protocol
Multimedia Subsystem (IMS) network entities that handle data
sessions.
HSUPA High Speed Uplink Packet HSUPA is an amalgamation of two mobile protocols, High Speed
Access Downlink Packet Access (HSDPA) and HSUPA, that extends and
improves the performance of existing third-generation (3G) mobile
networks utilizing Wideband Code Division Multiple Access (WCDMA)
protocols.
ICD Initial Commercial Deployment Term used for the initial trials of CBRS/SAS
ICI Inter-Carrier Interference ICI is an impairment known to degrade performance of Orthogonal
Frequency Division Multiplexing (OFDM) transmissions. It arises from
carrier frequency offsets (CFOs), from the Doppler spread due to
channel time variation, and, to a lesser extent, from sampling
frequency offsets (SFOs).
ICIC Inter-cell Interference ICIC techniques apply restrictions to the radio resource management
Coordination (RRM) block, improving favorable channel conditions across subsets
of users that are severely impacted by the interference, and thus
attaining high spectral efficiency.
IDFT Inverse Discrete Fourier IDFT is a Fourier series, using the Discrete-Time Fourier Transform
Transform (DTFT) samples as coefficients of complex sinusoids at the
corresponding DTFT frequencies. It has the same sample-values as
the original input sequence.
IDU Indoor Unit Refers to indoor user equipment
IEEE Institute of Electrical and The IEEE is a technical professional organization whose purpose is to
Electronics Engineers educate and advance electrical and electronic engineering,
telecommunications, computer engineering, and allied disciplines.
IETF Internet Engineering Task The IETF is the body that defines standard Internet operating
Force protocols such as TCP/IP.
IFFT Inverse Fast Fourier Transform An IFFT algorithm computes the Discrete Fourier Transform (DFT) of
a sequence, or its inverse.
IMEI International Mobile Equipment IMEI is a 15- or 17-digit code that uniquely identifies mobile phone
Identity sets.
IMS Internet Protocol (IP) The IMS or IP Multimedia Core Network Subsystem is an
Multimedia Subsystem architectural framework for delivering IP multimedia services.
IMSI International Mobile Subscriber An IMSI is used to identify the user of a cellular network and is a
Identity unique identification associated with all cellular networks.
IMT International Mobile IMT is a set of requirements issued by the International
Telecommunication Telecommunication Union (ITU-R) in 2008 for what is marketed as
227
fourth-generation (4G) mobile phone and Internet access service.
IN Intelligent Networks An IN is a telephone network architecture in which the service logic
for a call is located separately from the switching facilities, allowing
services to be added or changed without having to redesign the
switching equipment.
IP Internet Protocol IP is the protocol by which data is sent from one computer to
another over the Internet.
IPSec Internet Protocol Security IPSec is a protocol suite for secure Internet protocol communications
that works by authenticating and encrypting each IP packet of a
communication session.
IPv4 Internet Protocol Version 4 IPv4 is the fourth revision of the Internet protocol (IP) and a widely-
used protocol in data communications over various kinds of
networks. IPv4 is a connectionless protocol used in packet-switched
layer networks, such as Ethernet.
ISI Inter-Symbol Interference ISI is a form of distortion of a signal in which one symbol interferes
with subsequent symbols. This is an unwanted phenomenon, as the
previous symbols have a similar effect as noise, thus making the
communication less reliable.
ISUP Integrated Services Digital ISUP is the protocol used to support the signaling necessary to
Network (ISDN) Signaling User provide voice and non-voice services in telephone communications.
Part It is an extension of Signaling System 7 (SS7), used as the interface
protocol for voice and data within, and for ingression or egression
to/from, the Public Switched Telephone Network (PSTN).
ITU International The ITU is an agency of the United Nations whose purpose is to
Telecommunication Union coordinate telecommunication operations and services throughout
the world.
KBPS Kilobits per Second In the U.S., Kbps means thousands of bits per second and is a
measure of bandwidth on a data transmission medium.
KHz Kilohertz KHz is a measure of frequency equivalent to 1,000 cycles per second.
KPI Key Performance Indicator In the context of a telecommunications network, a KPI is a
quantifiable measure used to evaluate the success of network
performance (speed, quality). Typically, network operators will
monitor several types of KPIs to determine whether changes may be
needed to improve network performance.
L1 Layer 1 In the seven-layer Open Systems Interconnection (OSI) model of
computer networking, the physical layer (PHY), or L1, is the first and
lowest layer. The physical layer defines the means of transmitting
raw bits rather than logical data packets over a physical link
connecting network nodes.
L2 Layer 2 The data link layer, or L2, is the second layer of the seven-layer Open
Systems Interconnection (OSI) model of computer networking. L2 is
the protocol layer that transfers data between adjacent network
nodes in a wide area network (WAN) or between nodes on the same
local area network (LAN) segment.
228
L3 Layer 3 The network layer, or L3, is the third layer of the seven-layer Open
Systems Interconnection (OSI) model of computer networking. L3 is
responsible for packet forwarding, including routing through
intermediate routers, since it knows the address of neighboring
network nodes. It also manages quality of service (QoS), and
recognizes and forwards local host domain messages.
LAC Location Area Code The geographical location of an eNB. Used by mobile devices in
determining the best serving eNB.
LB Load Balancing In computing, LB distributes workloads across multiple computing
resources, such as computers, a computer cluster, network links,
central processing units, or disk drives. Load balancing aims to
optimize resource use, maximize throughput, minimize response
time, and avoid overload of any single resource.
LCR Low Chip Rate Universal Terrestrial Radio Access (UTRA) Time Division Duplexing
(TDD) 1.28 Megachips per Second (MCPS) LCR, or UTRA-TDD LCR, is
an air interface standard found in Universal Mobile
Telecommunications System (UMTS) mobile networks in China as an
alternative to Wideband Code Division Multiple Access (W-CDMA).
LI Lawful Intercept LI describes obtaining communications network data pursuant to
lawful authority for the purpose of analysis or evidence. Such data
generally consists of signaling or network management information,
or, in fewer instances, the content of the communications.
LTE Long-Term Evolution LTE is a standard for high-speed wireless communication for mobile
phones and data terminals. It is based on the Global System for
Mobile Communications (GSM) / Enhanced Data Rates
for GSM Evolution (EDGE) and Universal Mobile Telecommunications
System (UMTS) / High Speed Packet Access (HSPA) network
technologies. LTE increases the capacity and speed using a
different radio interface together with core network improvements.
MAC Medium Access Control In the IEEE 802 reference model of computer networking, the media
access control (MAC) layer is the lower sublayer of the data link layer
(Layer 2) of the seven-layer Open Systems Interconnection (OSI)
model.
MAC Message Authentication Code The MAC is used to authenticate devices based on their physical MAC
addresses. It is an early form of filtering. MAC authentication
requires that the MAC address of a machine must match a manually
defined list of addresses.
MBMS Multimedia Broadcast Multicast MBMS is a point-to-multipoint interface specification for Third-
Service Generation Partnership Project (3GPP) cellular networks. The
specification is designed to provide efficient delivery of broadcast
and multicast services, both within a cell as well as within the core
network.
MBR Maximum Bit Rate The MBR is the maximum number of bits that can be conveyed or
processed per unit of time.
229
MBSFN Multimedia Broadcast Multicast MBSFN is a transmission mode which exploits LTE’s Orthogonal
Service (MBMS) Single Frequency Division Multiplexing (OFDM) radio interface to send
Frequency Network multicast or broadcast data as a multicell transmission over a
synchronized single-frequency network.
MCC Mobile Country Code An MCC is used to uniquely identify the operator of a
telecommunications network. MCC + MNC = PLMN.
MCCH Multicast Control Channel The MCCH is a sublayer of Layer 2 protocol of Radio Interface
Protocol Architecture as per the Broadcast/Multicast Control
Standard (BMC-STD). It exists in the user plane only and is located
above the Radio Link Control, a Layer 2 function responsible for
mapping logical channels.
MCH Multicast Channel An MCH (one-to-many or many-to-many distribution) is a group
communication where information is addressed to a group of
destination computers simultaneously.
MCM Multi-Carrier Modulation MCM is a method of transmitting data by splitting it into several
components, and sending each of these components over
separate carrier signals. The individual carriers have narrow
bandwidth, but the composite signal can have broad bandwidth.
MCS Modulation and Coding Scheme MCS is a numerical index based on Orthogonal Frequency Division
Multiplexing (OFDM) that represents the maximum data rate that
can be achieved over-the-air. The MCS index value comprises several
variables, including channel width, modulation type, coding rate, and
spatial streams. Link to MCS index for 802.11n and 802.11ac:
http://mcsindex.com/
ME Mobile Equipment ME is the device that the customer uses to originate and receive calls
in a wireless network, or a radio terminal used for radio
communication over the Um* interface.
*It is called Um because it is the mobile analog to the U interface of
an Integrated Services Digital Network (ISDN).
MGCF Media Gateway Control The MGCF controls the resources in media gateways with an H.248
Function interface.
MGW Media Gateway An MGW is a translation device or service that converts media
streams between disparate telecommunications technologies such as
Plain Old Telephone Service (POTS), Signaling System 7 (SS7), Next-
Generation networks (2G, 2.5G, and 3G radio access networks), or
private branch exchange (PBX) systems.
MHz Megahertz A MHz is one million hertz, as a measure of the frequency of radio
transmissions or the clock speed of a computer.
MIB Master Information Block MIB is a particularly important message or information that is
broadcasted by the Long-Term Evolution (LTE) eNB, irrespective of
any users’ presence. The MIB is first among the other system
information blocks (SIB), which are also broadcasted by the eNB.
MIMO Multiple Input Multiple Output MIMO is an antenna technology for wireless communications in
which multiple antennas are used at both the source and the
230
destination. The antennas at each end of the communications circuit
are combined to minimize errors and optimize data speed.
MIP Mobile IP MIP is an Internet Engineering Task Force (IETF) standard
communications protocol that is designed to allow mobile device
users to move from one network to another while maintaining a
permanent IP address.
MISO Multiple Input Single Output MISO is an antenna technology for wireless communications in which
multiple antennas are used at the source (but not at the destination).
The antennas are combined to minimize errors and optimize data
speed.
MMD Multimedia Domain MMD is essentially a version of the Third-Generation Partnership
Project (3GPP) Internet Protocol (IP) Multimedia Subsystem (IMS)
architecture that has been adapted by 3GPP2. In Code Division
Multiple Access (CDMA) networks, the terms IMS and MMD are
often used interchangeably, even though, technically, IMS is a subset
of MMD.
MME Mobility Management Entity The Long-Term Evolution (LTE) MME is responsible for initiating
paging and authentication of mobile devices.
MMEGI MME Group Identity A group of Mobility Management Entities (MMEs) is assigned
an MMEGI, which works along with Mobility Management Entity
Code (MMEC) to make an MME identifier (MMEI). An MMEI uniquely
identifies the MME within a network.
MML Man-Machine Language MML is a standardized computing interface language for managing
telecommunications network devices from a console.
MMS Multimedia Messaging Service MMS is a standard way to send messages that include multimedia
content over a network.
MNC Mobile Network Code Uniquely identifies a mobile network operator (carrier) using the
GSM (including GSM-R), UMTS, and LTE public land mobile networks
MS Mobile Station An MS comprises all user equipment and software needed for
communication with a mobile network.
MSC Mobile Switching Center The MSC is a second-generation (2G) core network element which
controls the network switching subsystem elements. Alternatively, or
adaptively, Maximum Segment Size (MSS) can be used in Global
System for Mobile Communications (GSM) networks as well if the
manufacturer has implemented support for GSM networks in the
MSS.
MTCH Multimedia Broadcast Multicast MTCHs are the channels used to transport multimedia content from
Service (MBMS) Traffic Channel one device to another.
MTU Maximum Transmission Unit The size of the largest network layer protocol data unit that can be
communicated in a single network transaction
NACK Negative Acknowledgement NACK is a signal used in digital communications to ensure that data is
received with a minimum of errors. Sometimes the NACK signal is
called a rejection (REJ).
NAS Non-Access Stratum NAS is a functional layer in Universal Mobile Telecommunications
231
System (UMTS) and Long-Term Evolution (LTE) wireless telecom
protocol stacks between the core network and user equipment. This
layer establishes communication sessions and maintains continuous
communications with the user equipment as it moves.
NBM Network-Based Mobility An alternate from host-based mobility, NBM requires no localized
mobility management support on the mobile nodes and is
independent of global mobility management protocol, resulting in
modular mobility management architecture.
NFV Network Function Virtualization NFV is a network architecture concept that uses the technologies of
information technology (IT) virtualization to virtualize entire classes
of network node functions into building blocks that may connect, or
chain, together to create communication services.
NMS Network Management System An NMS is a set of hardware and/or software tools that allow an
information technology (IT) professional to supervise the individual
components of a network within a larger network
management framework. In the context of a Baicells network, the
Operations Management Console (OMC) is a network management
application that may communicate with the LTE NMS through the
northbound interface.
NTP Network Time Protocol The network operator may use one or more NTP servers to provide
correct time-of-day to the eNBs and other equipment.
ODU Outdoor Unit Refers to outdoor user equipment
OFDM Orthogonal Frequency Division OFDM is a frequency division multiplexing scheme used as a digital
Multiplexing multi-carrier modulation method. Many closely spaced orthogonal
sub-carrier signals are used to carry data on several parallel data
streams or channels.
OFDMA Orthogonal Frequency Division OFDMA is a multi-user version of OFDM. Multiple access is achieved
Multiple Access in OFDMA by assigning subsets of subcarriers to individual users.
OMC Operations Management The Baicells OMC is a Cloud-based network management application
Console with a graphical user interface (GUI) that enables operator
administrators to configure and manage the Baicells eNBs and UEs.
OPC Object Linking and Embedding Open Platform Communications (OPC) and OLE for Process Control is
(OLE) for Process Control a series of standards for industrial telecommunications, and which
enable real-time plant data between control devices from different
manufacturers.
OSS Operations Support System An OSS is a set of programs that help a communications service
provider monitor, control, analyze, and manage a telephone or
computer network. The Baicells OSS, or BOSS, allows operators to
manage mobile subscriber information.
PAPR Peak-to-Average Power Ratio PAPR is the relationship between the maximum power of a sample in
a transmitted Orthogonal Frequency Division Multiplexing (OFDM)
symbol and its average power.
PBCH Physical Broadcast Channel The PBCH carries system information for user equipment requiring
access to the network. It only carries what is termed Master
232
Information Block, or MIB, messages.
PCC Policy and Charging Control Network function that enables application servers to dynamically
control the QoS and charging requirements of the services
they deliver. Also improves roaming services. PCC is necessary
for operators to differentiate and monetize LTE services.
PCC Primary Carrier Component In Carrier Aggregation (CA), the primary component carrier is
complemented with one or several secondary component carriers
(SCC). The PCC handles all the control signaling while the SCC is used
to increase the data throughput.
PCCH Paging Control Channel PCCH is a downlink channel that transfers paging information. This
channel is used when the network does not know the location cell of
the user equipment (UE), or the UE is in the cell connected state but
utilizing UE sleep mode procedures.
PCEF Policy and Charging A serving gateway (SGW) function that enforces gating and QoS for
Enforcement Function individual IP flows.
Pcell Primary Cell Carrier 1 of a two-carrier eNodeB. The primary cell operates on the
primary frequency, in which the UE performs the initial connection
establishment, initiates the connection re-establishment procedure,
or is used in a handover state.
PCFICH Physical Control Format The PCFICH is one of the control channels that works at Layer 1, the
Indicator Channel physical layer. It is used to dynamically indicate the number of
symbols to be used for the Physical Dedicated Control
Channel (PDCCH).
PCH Paging Channel The PCH is the downlink transport channel in Universal Mobile
Telecommunications System (UMTS) that carries the Paging Control
Channel (PCCH). It is used to broadcast paging and notification
messages in a cell. The PCH is transported in the Secondary Common
Control Physical Channel (S-CCPCH).
PCI Physical Cell Identifier PCI, or Layer 1 identity, is an essential configuration parameter of a
radio cell that uniquely identifies each cell site in the wireless
network. PCI planning is crucial for quality of service (QoS) and
somewhat similar to scrambling code allocation in Wide-Band Code
Division Multiple Access (WCDMA) air interface standards.
PCRF Policy and Charging Rule PCRF is the software node designated in real-time that provides
Function policy control and flow-based charging control decisions.
PDCCH Physical Dedicated Control The PDCCH carries a message called Downlink Control Information
Channel (DCI), which includes resource assignments for user equipment.
PDCP Packet Data Convergence PDCP is specified by the Third-Generation Partnership Project (3GPP)
Protocol in TS 25.323 for Universal Mobile Telecommunications System
(UMTS) and TS 36.323 for Long-Term Evolution (LTE) networks. The
PDCP is in the radio protocol stack in the UMTS and LTE air interface
on top of the Radio Link Control (RLC) layer.
PDN Packet Data Network The PDN is specified and identified by the Access Point Name (APN),
or eNB, to allow a mobile data user to communicate with the
233
network.
PDP Packet Data Protocol PDPs are network layer (Layer 3) addresses. General Packet Radio
Service (GPRS) systems support both X.25 and Internet Protocol (IP)
network layer protocols. Therefore, PDP addresses can be X.25, IP, or
both.
PDP Policy Decision Point PDP is a point in the network which evaluates digital access requests
against authorization policies before issuing access decisions.
PDSCH Physical Downlink Shared The PDSCH is the main data bearing channel which is allocated to
Channel users on a dynamic and opportunistic basis. The PDSCH also is used
to transmit broadcast information not transmitted on the Physical
Broadcast Channel (PBCH) which includes System Information Blocks
(SIB), paging, and Radio Resource Control (RRC) signaling messages.
PDU Protocol Data Unit A PDU is information that is delivered as a unit among peer entities
of a network and that may contain control information, such as
address information or user data.
P-GW PDN Gateway The P-GW communicates with the outside world, i.e., packet data
networks (PDN), using a Silicon Graphics International (SGI) interface.
Each PDN is identified by an access point (AP), or eNB, name.
PHICH Physical Hybrid Automatic The PHICH in the downlink carries Hybrid ARQ
Repeat Request (ARQ) Indicator acknowledgements/negative acknowledgements (ACK/NACK) for
Channel uplink data transfers. PHICHs are in the first Orthogonal Frequency
Division Multiplexing (OFDM) symbol of each subframe.
PHY Physical Layer The PHY layer is the first layer of the Open System Interconnection
Model, or Layer 1. The physical layer deals with bit-level transmission
between different devices and supports electrical or mechanical
interfaces connecting to the physical medium for synchronized
communication.
PLMN Public Land Mobile Network A PLMN is any wireless communications system intended for use by
terrestrial subscribers in vehicles or on foot. Such a system can stand
alone, but often it is interconnected with a fixed system such as the
public switched telephone network.
PMCH Physical Multicast Channel The PMCH is a transmission channel that is used to transfer
information from one source to one or more devices (multiple
receiving points) that are operating within a radio coverage area. The
PMCH carries the multicast channel (MCH).
PMIP Proxy Mobile IP (MIP) PMIP is a network-based mobility management protocol
standardized by Internet Engineering Task Force (IETF) and specified
in RFC 5213.
PN Pseudo-Random Noise PN is a signal noise which satisfies one or more of the standard tests
for statistical randomness. Although it seems to lack any definite
pattern, PN consists of a deterministic sequence of pulses that repeat
after a certain period.
PRACH Physical Random-Access PRACH is a Layer 1 channel used by wireless terminals to access the
Channel mobile network, e.g., Time Division, Frequency Division, or Code
234
Division Multiple Access (TDMA, FDMA, CDMA) based network for
call setup and bursty data transmission.
PRB Physical Resource Block The PRB is an LTE specification that allocates users a specific number
of subcarriers for a predetermined amount of time.
PRI Primary Rate Interface The PRI is a telecommunications interface standard used on an
Integrated Services Digital Network (ISDN) for carrying multiple
Digital Signal Zero (DS0) voice and data transmissions between the
network and a user.
P-RNTI Paging Radio Network The P-RNTI is used by the user equipment to receive paging
Temporary Identity messages, and is carried by the Paging Control Channel (PCCH) logical
channel which is mapped to the Paging Channel (PCH) transport
channel. The PCH transport channel is mapped to the Physical
Downlink Shared Channel (PDSCH) physical channel.
P-SCH Primary Synchronization The P-SCH is a code that is repeated at the beginning of each time
Channel slot. The same code is used by all the cells and enables the user
equipment to detect the existence of the Universal Mobile
Telecommunications System (UMTS) cell and to synchronize on the
time slot boundaries.
PSD Power Spectral Density Describes the distribution of power into frequency components of a
signal. Any physical signal can be decomposed into a number of
discrete frequencies, or a spectrum of frequencies, over a continuous
range.
PSDU Protocol Service Data Unit The PSDU is referred to in the Institute of Electrical and
Electronics (IEEE) 802.11 standard as the Media Access Control
Packet Data Unit (MPDU) with an additional Physical Layer
Convergence Procedure (PLCP) preamble and header. The term
typically references physical layer operations.
PSTN Public Switched Telephone The PSTN is the aggregate of the world’s circuit-switched telephone
Network networks that are operated by national, regional, or local operators,
providing infrastructure and services for public telecommunications.
PUCCH Physical Uplink Control The PUCCH is used to carry Uplink Control Information (UCI). Long-
Channel Term Evolution (LTE) user equipment can never transmit both PUCCH
and Physical Uplink Shared Channel (PUSCH) during the same
subframe.
PUSCH Physical Uplink Shared Channel The PUSCH channel carries user data. It supports Quadrature Phase
Shift Keying (QPSK) and 16 Quadrature Amplitude Modulation
(QAM), with 64QAM being optional.
QAM Quadrature Amplitude QAM is both an analog and a digital signal modulation scheme. It
Modulation conveys two analog message signals, or two digital bit streams, by
modulating the amplitudes of two carrier waves, using
the amplitude-shift keying (ASK) digital modulation scheme or
amplitude modulation (AM) analog modulation scheme.
QCI Quality of Service (QoS) Class QCI is a mechanism used in Third-Generation Partnership Project
Identifiers (3GPP) Long Term Evolution (LTE) networks to ensure bearer traffic is
235
allocated appropriate quality of service (QoS).
QoS Quality of Service QoS refers to the capability of a network to provide better service to
selected network traffic. Various technologies, including Frame
Relay, Asynchronous Transfer Mode (ATM), Ethernet, 802.1
networks, Synchronous Optical Networking (SONET), and Internet
Protocol (IP) routed networks are capable of providing various levels
of QoS.
QPSK Quadrature Phase Shift Keying QPSK is a form of Phase Shift Keying (PSK) in which two bits are
modulated at once, selecting one of four possible carrier phase shifts
(0, 90, 180, or 270 degrees). QPSK allows the signal to carry twice as
much information as ordinary PSK using the same bandwidth.
RACH Random Access Channel RACH is a shared channel used by wireless terminals to access the
mobile network for call setup and bursty data transmission.
RAN Radio Access Network A RAN is part of a mobile telecommunications system. Conceptually,
the RAN resides between a mobile device and the core network.
RAT Radio Access Technology RAT is the underlying physical connection method for a radio-based
communication network.
RB Radio Bearer An RB is a channel offered by Layer 2 to higher Open System
Interconnection (OSI) layers for the transfer of either user or control
data. In other words, Layer 2 offers to the upper layers the service of
information transmission between the user’s equipment and the
Universal Terrestrial Radio Access Network (UTRAN) by means of the
RBs and signaling RBs.
RB Resource Block An RB is a time and frequency resource that occupies 12 subcarriers
(12×15 KHz = 180 KHz) and one slot (= 0.5 ms). RBs are allocated in
pairs by the scheduler (then referred to as scheduling blocks).
RF Radio Frequency RF is any of the electromagnetic wave frequencies that lie in the
range extending from approximately 3 KHz to 300 GHz, which include
those frequencies used for communications or radar signals.
RLC Radio Link Control RLC is a Layer 2 protocol used on the air interface in Universal Mobile
Telecommunications System (UMTS) and Long-Term Evolution (LTE)
networks.
ROCH Robust Header Compression ROCH is a standardized method to compress the Internet Protocol
(IP), User Datagram Protocol (UDP), UDP-Lite, Real-Time Transport
Protocol (RTP), and Transmission Control Protocol (TCP) headers of
Internet packets.
RRC Radio Resource Control The RRC protocol is used on the air interface in Universal Mobile
Telecommunications System (UMTS) and Long-Term Evolution (LTE)
networks. RRC handles the control plane signaling of Layer 3
between the user equipment and the Radio Access Network (RAN) -
either Universal Terrestrial Radio Access Network (UTRAN) or
Evolved UTRAN (E-UTRAN) - as well as for the radio interface
between a relay node and the E-UTRAN.
RRM Radio Resource Management RRM is the system level management of co-channel interference,
236
radio resources, and other radio transmission characteristics in
wireless communication systems. RRM functionality is used in
cellular networks, wireless local area networks, and wireless sensor
systems.
RSRP Reference Symbol Received The RSRP is the linear average over the power contributions for the
Power resource elements that carry cell-specific reference signals within the
frequency bandwidth. The signal strength reflects the user
equipment’s received Carrier Routing System (CRS) power of a Long-
Term Evolution (LTE) cell.
RSRQ Reference Signal Received The RSRQ reflects the relative ratio of signal and interference within
Quality the system. RSRQ = N×RSRP/(E-UTRA carrier RSSI), where:
N is the number of resource blocks (RBs) of the Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) carrier Received Signal
Strength Indicator (RSSI) measurement bandwidth, and RSRP is the
Reference Symbol Received Power.
RSSI Received Signal Strength RSSI is the linear mean value of all the signals that the user
Indicator equipment has received, including the intra-frequency signal and
interference, the inter-frequency interference, and thermal noise.
RTO Retransmission Timeout An RTO occurs when a sender is missing too many
acknowledgements and then takes a timeout or stops sending
packets altogether. The sender usually starts sending again after this
brief delay. Too many of these can cause delays on the network for
all users. Analyzing RTOs can help identify packet loss and to locate
congested links.
RTT Round Trip Time The length of time it takes for a signal to be sent plus the length of
time it takes for an acknowledgement of that signal to be received.
S1-U Single 1 User Plane The S1-U interface is the interface between the Long-Term Evolution
(LTE) Radio Access Network (RAN) and the Evolved Packet Core (EPC)
transport network layer’s Mobility Management Entity (MME)
interface built on the Internet Protocol (IP) transport eNB control
plane. S1-U supports the tunneling of end-user packets between the
eNB and the User Plane Entity (UPE).
SAE System Architecture Evolution SAE is the core network architecture of the Third-Generation
Partnership Project’s (3GPP’s) Long-Term Evolution (LTE) wireless
communications standard.
SAS Spectrum Access System A shared spectrum access technology that facilitates the dynamic
allocation of Citizens Broadband Radio Service (CBRS) spectrum on a
tiered, priority basis, while minimizing interference with other CBRS
and incumbent users. CBRS is a 150 MHz wide channel of the 3.5 GHz
(3550-3700 MHz) band in the United States and was only recently
made available to enterprises by the Federal Communication
Commission (FCC).
SC Single Carrier An SC transmission means one radio frequency (RF) carrier is used to
carry the information. Hence, information in the form of bits is
carried by a single RF carrier.
237
SCC Secondary Carrier Component In Carrier Aggregation (CA), the primary component carrier (PCC) is
complemented with one or several secondary component carriers
(SCC). The PCC handles all the control signaling while the SCC is used
to increase the data throughput.
Scell Secondary Cell Carrier 2 of a two-carrier eNodeB. The secondary cell, operating on a
secondary frequency, may be configured once a Radio Resource
Control (RRC) connection is established and may be used to provide
additional radio resources.
SC-FDMA Single Carrier Frequency SC-FDMA deals with the assignment of multiple users to a shared
Division Multiple Access communication resource. It is also called Linearly Pre-coded OFDMA
(LP-OFDMA)
SCH Synchronization Channel An SCH is a downlink control channel used in Global System for
Mobile Communication (GSM) cellular telephone systems. It is part
of the Unacknowledged Mode (Um) air interface specification. The
purpose of the SCH is to allow the mobile device to identify a nearby
cell quickly and synchronize to an eNB.
SCTP Stream Control Transmission The SCTP is a transport layer protocol, serving in a similar role to the
Protocol popular Transmission Control Protocol (TCP) and User Datagram
Protocol (UDP).
SDF Service Data Flow An SDF is an aggregate set of packet flows that match a set of service
data flow filters in a Policy and Charging Control (PCC) rule.
SDMA Space (or Spatial) Division SDMA is a satellite communications mode that optimizes the use of
Multiple Access radio spectrum and minimizes system cost by taking advantage of
the directional properties of dish antennas.
SDU Service Data Unit An SDU is a unit of data that has been passed down from an OSI layer
to a lower layer and that has not yet been encapsulated into a
protocol data unit (PDU) by the lower layer.
SFP Small Form-Factor Pluggable An SFP is a small transceiver that plugs into the SFP port of a network
switch and connects to fiber and Gigabit Ethernet (GbE) optical fiber
cables at the other end. Superseding the Gigabit Interface Converter
(GBIC) transceiver, SFP modules are also called "mini-GBIC" due to
their smaller size.
SFR Single Frequency Reuse Frequency reuse is a general wireless concept that refers to spectrum
sharing. The term here is related to Inter-Cell Interference
Coordination (ICIC) that, when enabled, allows UEs that are at the
same cell edge but attached to different eNodeBs to use different
frequency resources (automatically assigned) and avoid interfering
with each other.
SG Signaling Gateway An SG is a network component responsible for transferring signaling
messages (e.g., information related to call establishment, billing,
location, short messages, address conversion, and other services)
between Common Channel Signaling (CCS) nodes that communicate
using different protocols and transports.
S-GW Serving Gateway The S-GW resides in the user plane where it forwards and routes
238
packets to and from the eNB and packet data network (PDN)
gateway.
SI System Information The SI provides information to the user equipment about various
parameters of both the Access Stratum (AS) and Non-Access Stratum
(NAS).
SI-1 System Information Message 1 SI messages inform mobile devices about all important parameters
of how to access the network and how to find neighboring cells.
SIB System Information Block A SIB carries relevant information for the user equipment (UE), which
helps the UE to access a cell, perform cell reselection, and obtain
information related to intra-frequency, inter-frequency, and inter-
Radio Access Technology (RAT) cell selections.
SIM Subscriber Identity Module A SIM card is an integrated circuit that stores a mobile subscriber’s
critical information securely
SIMO Single Input Multiple Output SIMO is an antenna technology for wireless communications in which
multiple antennas are used at the destination (receiver), but not at
the transmitter. The antennas are combined to minimize errors and
optimize data speed. The source (transmitter) has only one antenna.
SINR Signal-to-Interference-plus- Signal-to-Interference-plus-Noise-Ratio (SINR), also known as the
Noise Ratio carrier-to-interference ratio (CIR or C/I), is a quantity (dB) used to
give theoretical upper bounds on channel capacity. SINR is calculated
based on the power of a certain signal of interest divided by the sum
of the interference power from all the other interfering signals and
background noise.
SIP Session Initiation Protocol SIP is a communications protocol for signaling and controlling
multimedia communication sessions.
SIR Signal-to-Interference Ratio See “SINR”.
SISO Single Input Single Output The use of only one antenna both in the transmitter and receiver.
SMS Short Message Service SMS is a text messaging service that uses standardized
communications protocols to enable fixed line or mobile phone
devices to exchange short text messages.
SN Service Node An SN is a switching point that comprises a point of end-user access
to the network and network services.
SNR Signal-to-Noise Ratio The SNR is a measure that compares the level of a desired signal to
the level of background noise. It is defined as the ratio of signal
power to the noise power, often expressed in decibels.
SOFDMA Scalable Orthogonal Frequency SOFDMA refers to the air interface outlined for portable or mobile
Division Multiple Access WiMAX systems by the Institute of Electrical and Electronics
Engineers (IEEE), used in the IEEE 802.16e (2005) standard.
SON Self-Organizing Network SON refers to automation technology designed to make the planning,
configuration, management, optimization, and healing of mobile
radio access networks (RANs) simpler and faster. SON functionality
and behavior has been specified in generally accepted mobile
industry standards.
239
SRNC Serving Radio Network When a Radio Network Controller (RNC) has a Radio Resource
Controller Control (RRC) connection with user equipment (UE), it is known as
the Serving RNC, or SRNC, for that UE. The SRNC is responsible for
the user’s mobility within the Universal Terrestrial Radio Access
Network (U-TRAN) and is also the point of connection towards
the core network.
STC Space-Time Coding STC is a technique used in wireless communications to transmit
multiple copies of a data stream across several antennas and to
exploit the various received versions of the data to improve the
overall reliability of the data transfer.
TA Tracking Area A TA manages and represents the locations of user equipment.
Through re-optimization, the network design is successively
improved by reassigning some cells to TAs other than their original
ones.
TAI Tracking Area Identifier The TAI is the identity used to identify tracking areas (TAs). The TAI is
constructed from the Mobile Country Code (MCC), Mobile Network
Code (MNC) and Tracking Area Code (TAC).
TDD Time Division Duplex TDD is a transmission scheme that allows asymmetric flow for uplink
and downlink data transmission. TDD refers to duplex
communication links where the uplink traffic is separated from the
downlink traffic by allocating different time slots in the same
frequency band.
TEID Tunnel Endpoint Identifier The separate tunnels between each set of end points are identified
by a TEID in the General Packet Radio Service Tunneling Protocol for
User Data (GTP-U) messages, normally a dynamically allocated
random number.
TFT Traffic Flow Template The TFT is used by the Gateway General Packet Radio Service
Support Node (GGSN) to discriminate between different user
payloads. The TFT incorporates packet filters such as quality of
service (QoS), Policy Decision Point (PDP) context, and security.
TM Transparent Mode TM is one of the three modes used to transfer the upper layer
Protocol Data Units (PDUs) via the Radio Link Control (RLC).
TTI Transmission Time Interval TTI is a parameter in Universal Mobile Telecommunications System
(UMTS) and other digital telecommunication networks that refers to
the duration of a transmission on the radio link. TTI is related to
encapsulation of data from higher layers into frames for transmission
on the Radio Link Layer (RLL).
UARFCN Universal Mobile In short, this is the frequency point of a neighboring eNB’s frequency.
(UMTS) Absolute Radio
Frequency Channel Number.
UCI Uplink Control Information The UCI is a set of information that is carried by the Physical Uplink
Control Channel (PUCCH). Depending on what kind of information
the UCI in the Physical Dedicated Control Channel (PDCCH) carries,
240
PDCCH is classified into various formations.
UDP User Datagram Protocol The UDP is one of the core members of the Internet Protocol (IP)
suite. With UDP, computer applications can send messages, in this
case referred to as datagrams, to other hosts on an IP network.
UE User Equipment In Long-Term Evolution (LTE) networks, UE (also referred to as
customer premise equipment, or CPE) is any device used directly by
an end-user to communicate via the network.
UL Uplink The UL path of a network connection is used to send data from the
user equipment to the network.
UL-SCH Uplink Shared Channel A physical UL-SCH is a transmission channel that is used to transport
user data from one or more mobile devices that can transmit on the
channel.
UM Unacknowledged Mode UM is one of three modes used to transfer upper layer Protocol Data
Units (PDU) in Radio Link Control (RLC) used on the air interface in
Long-Term Evolution (LTE) networks.
UMA Unlicensed Mobile Access UMA is a technology that allows UMA-capable user equipment to
switch back and forth seamlessly between networks and local
wireless networks.
UMTS Universal Mobile UMTS is a third-generation broadband, packet-based transmission of
Telecommunications System text, digitized voice, video, and multimedia at data rates up to and
possibly higher than 2 megabits per second (Mbps).
UPnP Universal Plug and Play UPnP is a set of networking protocols that permits devices such as
personal computers, printers, Internet gateways, Wi-Fi access points,
and mobile devices to discover each other's presence on the network
and communicate. UPnP is intended primarily for residential users
and not enterprise-class devices.
UpPTS Uplink Pilot Time Slot The UpPTS is one of the three fields that make up the 1ms special
subframes that comprise the half-frames used in the Long-Term
Evolution (LTE) Time Division Duplex (TDD) frame structure.
UpTS  Uplink Time Slot In Time Division Long-Term Evolution (TD-LTE) networks, the UpTS
allows the user equipment to transmit data to the receiver.
USIM Universal Subscriber Identity A SIM card is an integrated chip that securely stores a mobile
Module subscriber’s critical information for Global (GSM) networks. A USIM
provides enhanced features and allows a subscriber to access any
Universal Mobile Telecommunications System (UMTS) network,
including GSM and CDMA.
VoIP Voice over Internet Protocol VoIP is a service that enables people to make voice calls using only
their computers connected to the network. With VoIP, the Internet is
the transmission medium for telephone calls, sending voice data in
packets using IP rather than by traditional circuit transmissions of the
Public Switched Telephone Network (PSTN).
VPLMN Visited Public Land Mobile VPLMN is the network on which the mobile subscriber has roamed
Network (PLMN) when leaving their Home PLMN (HPLMN).
VRB Virtual Resource Blocks Physical Resource Blocks (PRBs) and VRBs support various kinds of
241
resource allocations. VRB supports both block-wise transmission
(localized) and transmission on non-consecutive subcarriers
(distributed) to maximize frequency diversity.
WCDMA Wideband Code Division WCDMA is a third-generation standard that employs the Direct
Multiple Access Sequence CDMA (DS-CDMA) channel access method and the
Frequency Division Duplexing (FDD) method to provide high-speed
and high-capacity service.
Wi-Fi Wi-Fi Wi-Fi is the marketing name for a standard defined by the Institute
for Electrical and Electronics Engineering (IEEE) called 802.11x. In the
same way that a local area network (LAN) describes the cabled
connection of residential or business computing devices in the same
geographical or logical domain, Wi-Fi describes the wireless
connection of residential or business computing devices in the same
geographical or logical domain. Wi-Fi also is referred to as wireless
LAN (WLAN).
WiMAX Worldwide Interoperability for WiMAX is a family of wireless communication standards based on the
Microwave Access Institute for Electrical and Electronics Engineering (IEEE) 802.16 set of
standards, which provide multiple physical layer (PHY) and Media
Access Control (MAC) options.
WInnForum Wireless Innovation Forum A non-profit organization that advocates spectrum innovation and
advancing radio technologies
WLAN Wireless Local Area Networks See “Wi-Fi”.
242

Baicells Configuration Network Admin Guide Srv1.26 28-Feb-2020

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Baicells Configuration Network Admin Guide Srv1.26 28-Feb-2020

Încărcat de

Drepturi de autor:

Formate disponibile

Configuration & Network

CHINA NORTH AMERICA

Phone Phone: +86-10-62607100 Phone: +1-888-502-5585

Email E-mail: contact@Baicells.com Email: sales_na@Baicells.com or support_na@Baicells.com

Website Website: www.Baicells.com Website: https://na.Baicells.com

2.1 Computer Requirements

Figure 2-2: Login

Figure 2-3: Home Page

2.4 BTS Info

Table 2-2: Basic Info Fields

Field Name Description

2.4.2 Quick Setting

Table 2-3: Quick Setting

Field Name Description

Refer to the BaiTip on this setting: https://community.na.baicells.com/t/baitip-

Perform the following steps:

Caution: The reboot action will disrupt eNB service.

Figure 2-11: Backup

Caution: The reboot action will disrupt eNB service.

Figure 2-15: Network Menu

Table 2-5: WAN/LAN

Field Name Description

2.6.3 MME&IPSec Binding

2.6.3.1 IPSec Setting

Table 2-6: Tunnel Configure > Basic Setting Tab

Field Name Description

2.6.3.2.2 Tunnel Configure - Advance Setting

Field Name Description

NOTE: In QRTB 2.0.x this function is labeled MME Pool.

2.6.6 Static Routing

2.7 BTS Setting

Figure 2-26: BTS Setting Menu

Table 2-9: Security Settings - For Information Only

2.7.2 Management Server

2.7.3 Sync Setting

Table 2-10: 1588 Sync (future feature)

2.7.4 HaloB Setting

2.7.6 Carrier Setting (Nova-436Q only)

Figure 2-34: LTE Menu

2.8.2 LTE Freq/Cell

2.8.2.1 LTE Neigh Freq Table

Table 2-11: LTE Neigh Freq Settings

Field Name Description

2.8.2.2 LTE Neigh Cell Table

Table 2-12: LTE Neigh Cell Table Settings

Field Name Description

2.8.3 TD-S Freq/Cell

2.8.3.1 TD-S Neigh Freq Table

Table 2-13: TD-S Neigh Freq Table Settings

Field Name Description

2.8.3.2 TD-S Neigh Cell Table

Table 2-14: TD-S Cell Setting Fields

Field Name Description

2.8.4 GSM Freq/Cell

2.8.4.1 GSM Neigh Freq Table

Field Name Description

2.8.4.2 GSM Neigh Cell Table

Table 2-16: GSM Freq/Cell > Neigh Cell Settings

Field Name Description

Figure 2-44: Handoff

Figure 2-46: A1, A2, A3, and A5 Event Thresholds

Field Name Description

Field Name Description