Baicells Configuration & Network Administration Guide (SRv1.5 10-Jan-2018) PUBLISH

Configuration & Network
Administration Guide
January 2018
Version 1.5
About This Document
This document describes the applications used for configuring and administering the Baicells
network components and subscribers. The scope includes how to use the eNodeB (eNB) and
user equipment (UE) Graphical User Interface (GUI) applications and the CloudCore suite of
applications. CloudCore includes the Operations Management Console (OMC), Business
Operations Support System (BOSS), and the forthcoming Evolved Packet Core (EPC). The EPC
information will be covered in separate documents, Baicells Enterprise EPC Deployment Guide
and Baicells Enterprise EPC User Guide.
The document is written to the following Baicells GUI software code levels:
• TDD eNB GUI version 100R001C00B110SPC003
• UE GUI version BCE-ODU-1.0.12
• CloudCore OMC version 3.2.2 and BOSS version 3.3.0
The document is intended primarily for network administrators who are responsible for adding
users to the system and configuring, monitoring, troubleshooting, and upgrading Baicells eNBs
and UEs. Appendix B provides a list of abbreviations and acronyms used.
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
10-Jan-2018 V1.5 Updated to OMC v3.2.2 Cameron Kilton Sharon Redfoot
and BOSS v3.3.0; added Nitisha Potti
additional details on X2 Samuel (Tang) Weizhou
handoff and neighbor cells Wu Junfeng
config; updated terms UE Yang Yanan
and eNB for consistency
16-Nov-2017 V1.4 Updated for: Cameron Kilton Sharon Redfoot
• BS GUI version Wu Junfeng
100R001C00B110SPC003 Zhang Dandan
• CPE GUI version BCE- Nitisha Potti
ODU-1.0.12 Sonny May
• CloudCore OMC and Yang Yanan
BOSS version 3.0.1
21-Aug-2017 V1.3 Edited based on SME Rick Harnish Sharon Redfoot
review. Published. Cameron Kilton
Wu Junfeng
Tang Houcheng
Prior V1.2 Combined OMC User Jesse Raasch Sharon Redfoot
V1.1 Guide, Base Station Cameron Kilton
V1.0 Configuration Guide, and Rick Harnish
BOSS User Guide. Added Nitisha Potti
base station and CPE
GUIs.
Related Documents
Other Baicells technical documents may be found on the Baicells support website (refer to
Contact Us). Following is a list of the technical documents:
UE – Gen 1 Atom 5dBi Indoor CPE User Manual

Atom 11dBi Outdoor CPE User Manual
Atom 19.5dBi Outdoor CPE User Manual
UE – Gen 2 Atom ID04-3.5/6.5 & ID06-6.5 User Manual (forthcoming)
Atom OD04-14/19.5 User Manual (forthcoming)
eNB – Gen 1 Nova 1W Base Station Installation Guide
Nova 1W Quick Start Guide
Nova 10W Base Station Installation Guide
Nova 10W Quick Start Guide
eNB – Gen 2 Nova-227 Outdoor 2x250mW TDD eNB Installation Guide
Nova-227 Quick Start Guide
Nova-233 Outdoor 2x1WG2 FDD-TDD eNB Installation Guide
(forthcoming)
Nova-233 Quick Start Guide (forthcoming)
Nova-243 Outdoor 2x10WG2 FDD-TDD eNB Installation Guide
(forthcoming)
iii
Nova-436 Outdoor 4x1W CCA TDD eNB Installation Guide (forthcoming)
Nova-446 Outdoor 4x10W FDD eNB Installation Guide (forthcoming)
elfcell-220 Indoor 2x50mW FDD eNB Installation Guide (forthcoming)
elfcell-220 Quick Start Guide (forthcoming)
NeutralCell Indoor Multi FDD-TDD Small Cell Installation Guide
(forthcoming)
NeutralCell Quick Start Guide (forthcoming)
Neutrino-224 Indoor 2x125mW FDD-TDD eNB Installation Guide
(forthcoming)
Neutrino-224 Quick Start Guide (forthcoming)
SolarCell Outdoor Solution Installation Guide (forthcoming)
SolarCell Quick Start Guide (forthcoming)
Spectra LTE-U Outdoor 2x500mW FDD eNB Installation Guide
(forthcoming)
Spectra LTE-U Quick Start Guide (forthcoming)
System, CloudCore, OAM Baicells Configuration & Network Administration Guide
Baicells Handoff Configuration Guidelines (Beta trial)
Baicells BOSS API Manual
Baicells Operation, Maintenance, & Troubleshooting Guide (forthcoming)
Baicells Enterprise EPC Deployment Guide (forthcoming)
Baicells Enterprise EPC User Guide (forthcoming)
Baicells System Overview (forthcoming)
Contact Us
Baicells Technologies Co., Ltd.
China North America
Address: 3F, Bldg. A, No. 1 Kai Tuo Rd, Address: 555 Republic Dr., #200, Plano, TX
Haidian Dist, Beijing, China 75074, USA
Phone: +86-10-62607100 Phone: +1-888-502-5585
Email: sales_na@Baicells.com or
E-mail: contact@Baicells.com
support_na@Baicells.com
Website: www.Baicells.com Website: https://na.Baicells.com
iv
Table of Contents
1. INTRODUCTION ......................................................................................................................... 1
2. ENB GUI ..................................................................................................................................... 6

2.1 COMPUTER REQUIREMENTS ................................................................................................................ 6
2.2 LAUNCHING THE GUI......................................................................................................................... 7
2.3 DATA PREPARATION ........................................................................................................................... 8
2.4 CONFIGURATION FLOW ...................................................................................................................... 9
2.5 BTS INFO ........................................................................................................................................ 9
2.5.1 Basic Info .............................................................................................................................. 9
2.5.2 Quick Setting ...................................................................................................................... 13
2.6 SYSTEM......................................................................................................................................... 15
2.6.1 NTP..................................................................................................................................... 15
2.6.2 Upgrade ............................................................................................................................. 16
2.6.3 Backup ............................................................................................................................... 17
2.6.4 Password ............................................................................................................................ 18
2.7 NETWORK ..................................................................................................................................... 19
2.7.1 WAN/LAN ........................................................................................................................... 19
2.7.2 DHCP .................................................................................................................................. 20
2.7.3 VLAN .................................................................................................................................. 21
2.7.4 IPSec/MME Pool................................................................................................................. 22
2.7.5 LGW.................................................................................................................................... 26
2.7.6 CertStore ............................................................................................................................ 27
2.8 BTS SETTING ................................................................................................................................. 27
2.8.1 Security Setting .................................................................................................................. 27
2.8.2 Management Server .......................................................................................................... 28
2.8.3 Sync Setting ........................................................................................................................ 29
2.9 LTE .............................................................................................................................................. 30
2.9.1 Identify Neighbor Frequencies and Cell Information ......................................................... 30
2.9.1.1 LTE Freq/Cell........................................................................................................................... 31
2.9.1.1.1 LTE Neigh Freq Table.......................................................................................................... 31
2.9.1.1.2 LTE Neigh Cell Table ........................................................................................................... 32
2.9.1.2 TD-S Freq/Cell ........................................................................................................................ 34
2.9.1.2.1 TD-S Neigh Freq Table ....................................................................................................... 34
2.9.1.2.2 TD-S Neigh Cell Table ......................................................................................................... 35
2.9.1.3 GSM Freq/Cell ........................................................................................................................ 36
2.9.1.3.1 GSM Neigh Freq Table ....................................................................................................... 37
2.9.1.3.2 GSM Neigh Cell Table ........................................................................................................ 38
2.9.2 Configure Mobility Parameters .......................................................................................... 38
2.9.3 Configure Advanced Parameters ....................................................................................... 45
2.9.3.1 X2................................................................................................................................................ 46
2.9.3.2 Power Control ............................................................................................................................. 46
v
2.9.3.3 eNodeB ....................................................................................................................................... 48
2.9.3.4 GAP ............................................................................................................................................. 49
2.9.3.5 RRC Status................................................................................................................................... 49
2.9.3.6 SON Functional ........................................................................................................................... 50
2.9.3.7 Tx and Rx..................................................................................................................................... 50
2.9.3.8 Random Access........................................................................................................................... 50
2.9.3.9 Capacity ...................................................................................................................................... 51
2.9.3.10 Scheduling Algorithm ............................................................................................................... 51
2.9.3.11 Sync Adjust ............................................................................................................................... 52
2.9.3.12 Link Activation State Detector .................................................................................................. 52
2.9.4 Real-World LTE Configuration Example.............................................................................. 53
2.10 REBOOT ...................................................................................................................................... 56
2.11 LOGOUT ...................................................................................................................................... 56
3. UE GUI ..................................................................................................................................... 58
3.1 COMPUTER REQUIREMENTS .............................................................................................................. 58
3.2 LAUNCHING THE GUI....................................................................................................................... 58
3.3 OVERVIEW..................................................................................................................................... 60
3.4 NETWORK ..................................................................................................................................... 66
3.4.1 LTE Settings ........................................................................................................................ 69
3.4.2 Scan Mode ......................................................................................................................... 71
3.4.3 APN Management ............................................................................................................. 73
3.4.4 PIN Management ............................................................................................................... 74
3.4.5 SIM Lock ............................................................................................................................. 75
3.4.6 DMZ Settings ...................................................................................................................... 75
3.4.7 Static Route ........................................................................................................................ 76
3.4.8 LAN Settings ....................................................................................................................... 77
3.5 SECURITY....................................................................................................................................... 78
3.5.1 MAC Filtering ..................................................................................................................... 79
3.5.2 IP Filtering .......................................................................................................................... 80
3.5.3 URL Filtering ....................................................................................................................... 81
3.5.4 Port Forwarding ................................................................................................................. 82
3.5.5 Access Restriction............................................................................................................... 83
3.5.6 UPnP .................................................................................................................................. 84
3.6 VPN ............................................................................................................................................ 85
3.7 IPV6 ............................................................................................................................................ 86
3.8 SYSTEM......................................................................................................................................... 88
3.8.1 Maintenance ...................................................................................................................... 89
3.8.2 Version Manager................................................................................................................ 90
3.8.3 FTP Auto Upgrade .............................................................................................................. 90
3.8.4 TR069 ................................................................................................................................. 92
3.8.5 Date & Time ....................................................................................................................... 93
3.8.6 DDNS .................................................................................................................................. 95
3.8.7 Iperf.................................................................................................................................... 96
3.8.8 Diagnostics ......................................................................................................................... 97
vi
3.8.9 Port Mirror ......................................................................................................................... 99
3.8.10 SysLog ............................................................................................................................ 100
3.8.10.1 Network .................................................................................................................................. 100
3.8.10.2 Local ....................................................................................................................................... 100
3.8.11 Ping Watchdog............................................................................................................... 101
3.8.12 Simcard Checking ........................................................................................................... 102
3.8.13 WEB Setting ................................................................................................................... 103
3.8.14 Account .......................................................................................................................... 104
3.8.15 Logout ............................................................................................................................ 105
4. CLOUDCORE........................................................................................................................... 106
4.1 COMPUTER REQUIREMENTS ............................................................................................................ 106
4.1.1 Server ............................................................................................................................... 106
4.1.2 Client ................................................................................................................................ 106
4.2 GETTING STARTED ......................................................................................................................... 107
4.2.1 Accessing CloudCore ........................................................................................................ 107
4.2.2 Overview of CloudCore Users ........................................................................................... 107
4.2.3 Navigation ....................................................................................................................... 108
4.2.4 Online Help ...................................................................................................................... 110
4.3 SYSTEM....................................................................................................................................... 110
4.3.1 Operator Info ...................................................................................................................... 110
4.3.2 Users ................................................................................................................................... 111
4.3.3 Reset Password ................................................................................................................ 112
4.3.4 Logs .................................................................................................................................. 113
4.3.5 Security Rule .................................................................................................................... 113
4.4 OMC ......................................................................................................................................... 114
4.4.1 Dashboard........................................................................................................................ 115
4.4.1.1 Individual eNBs and UEs ....................................................................................................... 115
4.4.1.2 Alarms .................................................................................................................................. 116
4.4.1.3 Statistics ............................................................................................................................... 118
4.4.1.4 Performance ......................................................................................................................... 121
4.4.2 eNB .................................................................................................................................. 122
4.4.2.1 Monitor .................................................................................................................................... 122
4.4.2.1.1 Monitor Window ................................................................................................................. 122
4.4.2.1.2 Right-Click Actions ............................................................................................................... 125
4.4.2.1.2.1 Information .................................................................................................................. 126
4.4.2.1.2.2 Synchronize .................................................................................................................. 130
4.4.2.1.2.3 Settings ........................................................................................................................ 130
4.4.2.1.2.4 Reboot ......................................................................................................................... 136
4.4.2.1.2.5 Logs .............................................................................................................................. 136
4.4.2.1.2.6 CPEs ............................................................................................................................. 137
4.4.2.2 Strategy .................................................................................................................................... 137
4.4.2.2.1 Upgrades and Rollbacks .................................................................................................... 138
4.4.2.2.2 Reboot .............................................................................................................................. 141
4.4.2.2.3 Frequency & PCI ............................................................................................................... 142
vii
4.4.2.3 File Library ................................................................................................................................ 143
4.4.3 CPE ................................................................................................................................... 144
4.4.3.1 Monitor .................................................................................................................................... 144
4.4.3.1.1 Monitor Window ................................................................................................................. 144
4.4.3.1.2 Right-Click Actions ............................................................................................................... 148
4.4.3.1.2.1 Information ....................................................................................................................... 148
4.4.3.1.2.2 Settings ............................................................................................................................. 148
4.4.3.1.2.3 Synchronize ....................................................................................................................... 149
4.4.3.1.2.4 Frequency Lock ................................................................................................................. 149
4.4.3.1.2.5 Reboot .............................................................................................................................. 150
4.4.3.2 Strategy .................................................................................................................................... 150
4.4.3.3 File Library ................................................................................................................................ 152
4.4.4 Alarm ............................................................................................................................... 153
4.4.4.1 Query ........................................................................................................................................ 154
4.4.4.2 Settings ..................................................................................................................................... 157
4.4.4.2.1 Library ............................................................................................................................... 157
4.4.4.2.2 Notification ....................................................................................................................... 158
4.4.5 System .............................................................................................................................. 159
4.4.5.1 Device Management................................................................................................................. 159
4.4.5.2 User Management .................................................................................................................... 163
4.4.5.2.1 Modify System User Group ............................................................................................... 164
4.4.5.2.2 Add New System User Group............................................................................................ 165
4.4.5.2.3 Delete System User Group ................................................................................................ 166
4.4.5.3 Log Management ...................................................................................................................... 166
4.4.5.3.1 OMC Logs.......................................................................................................................... 166
4.4.5.3.2 Device Logs ....................................................................................................................... 168
4.4.6 Help .................................................................................................................................. 169
4.5 BOSS ......................................................................................................................................... 170
4.5.1 Overview .......................................................................................................................... 170
4.5.2 Subscriber ........................................................................................................................ 171
4.5.3 Network ........................................................................................................................... 174
4.5.3.1 SIM Card ................................................................................................................................... 175
4.5.3.2 SIM Audit Records .................................................................................................................... 177
4.5.4 System .............................................................................................................................. 178
4.5.4.1 Service Plans ............................................................................................................................. 178
4.5.4.1.1 Overview of Service Plans ............................................................................................... 178
4.5.4.1.2 Configure Service Plans ................................................................................................... 178
4.5.4.2 Logs .......................................................................................................................................... 181
4.5.5 Help .................................................................................................................................. 181
APPENDIX A: MML COMMANDS .................................................................................................... 182
APPENDIX B: ABBREVIATIONS AND ACRONYMS ............................................................................ 183
APPENDIX C: FAQS ......................................................................................................................... 212
APPENDIX D: CLOUDKEY ................................................................................................................ 213
viii
List of Figures
FIGURE 1-1: EXAMPLE BAICELLS ARCHITECTURE .................................................................................................. 2
FIGURE 1-2: SAMPLE ENB GUI WINDOW.......................................................................................................... 3
FIGURE 1-3: SAMPLE UE GUI WINDOW ........................................................................................................... 3
FIGURE 1-4: ENB GUI AND UE GUI MENU TREES .............................................................................................. 4
FIGURE 1-5: SAMPLE CLOUDCORE OMC WINDOW ............................................................................................. 5
FIGURE 1-6: CLOUDCORE GUI MENU TREES ...................................................................................................... 5
FIGURE 2-1: LOCAL INTERFACE......................................................................................................................... 6
FIGURE 2-2: INTERNET PROTOCOL VERSION (TCP/IPV4) ...................................................................................... 7
FIGURE 2-3: ENB GUI LOGIN .......................................................................................................................... 8
FIGURE 2-4: ENB GUI MENU ......................................................................................................................... 8
FIGURE 2-5: INITIAL CONFIGURATION FLOW ....................................................................................................... 9
FIGURE 2-6: BASIC INFO WINDOW ................................................................................................................. 10
FIGURE 2-7: QUICK SETTING WINDOW ........................................................................................................... 13
FIGURE 2-8: NTP WINDOW .......................................................................................................................... 15
FIGURE 2-9: UPGRADE WINDOW ................................................................................................................... 17
FIGURE 2-10: BACKUP WINDOW ................................................................................................................... 18
FIGURE 2-11: PASSWORD WINDOW ............................................................................................................... 18
FIGURE 2-12: INTERNET / WAN FIELDS .......................................................................................................... 19
FIGURE 2-13: DHCP WINDOW ..................................................................................................................... 21
FIGURE 2-14: VLAN WINDOWS .................................................................................................................... 21
FIGURE 2-15: IPSEC/MME POOL WINDOW.................................................................................................... 22
FIGURE 2-16: TUNNEL CONFIGURE > BASIC SETTING ......................................................................................... 23
FIGURE 2-17: TUNNEL CONFIGURE > ADVANCE SETTING .................................................................................... 24
FIGURE 2-18: LGW SETTING WINDOW .......................................................................................................... 26
FIGURE 2-19: CERTSTORE WINDOW............................................................................................................... 27
FIGURE 2-20: SECURITY SETTING WINDOW ..................................................................................................... 28
FIGURE 2-21: MANAGEMENT SERVER WINDOW ............................................................................................... 28
FIGURE 2-22: SYNC SETTING WINDOW ........................................................................................................... 29
FIGURE 2-23: NEIGH FREQ TABLE .................................................................................................................. 31
FIGURE 2-24: LTE FREQ/CELL > NEIGH CELL TABLE SETTINGS ............................................................................. 33
FIGURE 2-25: TD-S FREQ/CELL > NEIGH FREQ TABLE SETTINGS .......................................................................... 34
FIGURE 2-26: TD-S FREQ/CELL > NEIGH CELL TABLE SETTINGS ........................................................................... 36
FIGURE 2-27: GSM FREQ/CELL > NEIGH FREQ TABLE SETTINGS .......................................................................... 37
FIGURE 2-28: GSM FREQ/CELL > NEIGH CELL SETTINGS .................................................................................... 38
FIGURE 2-29: HANDOFF ............................................................................................................................... 39
FIGURE 2-30: MOBILITY PARAMETERS ............................................................................................................ 40
FIGURE 2-31: A1, A2, A3, AND A5 EVENT THRESHOLDS ................................................................................... 41
FIGURE 2-32: B2 EVENT THRESHOLD .............................................................................................................. 42
FIGURE 2-33: MEASUREMENT CONTROL PARAMETERS ...................................................................................... 43
FIGURE 2-34: CELL SELECTION AND CELL RESELECTION PARAMETERS.................................................................... 44
FIGURE 2-35: ADVANCED PARAMETERS SUB-MENUS ........................................................................................ 45
ix
FIGURE 2-36: X2 PARAMETER ....................................................................................................................... 46
FIGURE 2-37: POWER CONTROL PARAMETERS.................................................................................................. 47
FIGURE 2-38: ENODEB SETTINGS ................................................................................................................... 48
FIGURE 2-39: GAP SETTINGS ........................................................................................................................ 49
FIGURE 2-40: RRC STATUS PARAMETERS......................................................................................................... 49
FIGURE 2-41: SON FUNCTIONAL PARAMETERS ................................................................................................ 50
FIGURE 2-42: TX AND RX SETTINGS ................................................................................................................ 50
FIGURE 2-43: RANDOM ACCESS PARAMETERS .................................................................................................. 51
FIGURE 2-44: CAPACITY PARAMETERS ............................................................................................................. 51
FIGURE 2-45: SCHEDULING ALGORITHM PARAMETERS ....................................................................................... 52
FIGURE 2-46: SYNC ADJUST PARAMETERS ....................................................................................................... 52
FIGURE 2-47: LINK ACTIVATION STATE DETECTOR PARAMETERS ........................................................................... 53
FIGURE 2-48: LTE FREQ/CELL > NEIGH FREQ AND NEIGH CELL TABLE SETTINGS ..................................................... 53
FIGURE 2-49: FLOWCHART OF HANDOFF EVENT THRESHOLDS ............................................................................. 54
FIGURE 2-50: A1 THRESHOLD ....................................................................................................................... 55
FIGURE 2-54: X2 HANDOVER ........................................................................................................................ 56
FIGURE 2-55: REBOOT ACTION ...................................................................................................................... 56
FIGURE 2-56: LOGOUT ACTION ..................................................................................................................... 57
FIGURE 3-1: UE LAN INTERFACE EXAMPLE ...................................................................................................... 58
FIGURE 3-2: UE GUI LOGIN.......................................................................................................................... 59
FIGURE 3-3: UE GUI MAIN MENU ................................................................................................................ 59
FIGURE 3-4: CHANGE PASSWORD................................................................................................................... 60
FIGURE 3-5: OVERVIEW FIELDS (1 OF 5 SCREENS) ............................................................................................. 60
FIGURE 3-10: USIM STATUS ICON ................................................................................................................. 66
FIGURE 3-11: NETWORK SUB-MENUS ............................................................................................................ 66
FIGURE 3-12: NETWORK MODE .................................................................................................................... 66
FIGURE 3-13: NETWORK MODE > ROUTER SETTINGS ........................................................................................ 67
FIGURE 3-14: HOST NAME OPTIONS .............................................................................................................. 68
FIGURE 3-15: BRIDGE MODE ........................................................................................................................ 69
FIGURE 3-16: LTE SETTINGS ......................................................................................................................... 69
FIGURE 3-17: SCAN MODE SETTINGS ............................................................................................................. 71
FIGURE 3-18: PCI LOCK SETTINGS.................................................................................................................. 72
FIGURE 3-19: BAND/FREQUENCY PREFERRED SETTINGS ..................................................................................... 72
FIGURE 3-20: APN MANAGEMENT SETTINGS .................................................................................................. 73
FIGURE 3-21: PIN MANAGEMENT SETTINGS .................................................................................................... 74
FIGURE 3-22: SIM LOCK SETTINGS................................................................................................................. 75
FIGURE 3-23: DMZ SETTINGS ....................................................................................................................... 75
x
FIGURE 3-24: STATIC ROUTE SETTINGS ............................................................................................................ 76
FIGURE 3-25: LAN SETTINGS ........................................................................................................................ 77
FIGURE 3-26: SECURITY SUB-MENUS ............................................................................................................. 78
FIGURE 3-27: SECURITY SUB-MENUS ............................................................................................................. 79
FIGURE 3-28: MAC FILTERING SETTINGS ......................................................................................................... 79
FIGURE 3-29: IP FILTERING SETTINGS ............................................................................................................. 80
FIGURE 3-30: URL FILTERING SETTINGS .......................................................................................................... 82
FIGURE 3-31: PORT FORWARDING SETTINGS .................................................................................................... 82
FIGURE 3-32: ACCESS RESTRICTION SETTINGS .................................................................................................. 83
FIGURE 3-33: UPNP ................................................................................................................................... 84
FIGURE 3-34: VPN SETTINGS ........................................................................................................................ 85
FIGURE 3-35: IPV6 SUB-MENU ..................................................................................................................... 86
FIGURE 3-36: IPV6 SETTINGS > STATUS........................................................................................................... 86
FIGURE 3-37: IPV6 WAN SETTINGS ............................................................................................................... 87
FIGURE 3-38: IPV6 LAN SETTINGS ................................................................................................................ 87
FIGURE 3-39: SYSTEM SUB-MENUS................................................................................................................ 88
FIGURE 3-40: MAINTENANCE ........................................................................................................................ 89
FIGURE 3-41: VERSION MANAGER FIELDS........................................................................................................ 90
FIGURE 3-42: FTP AUTO UPGRADE FIELDS ...................................................................................................... 91
FIGURE 3-43: TR069 FIELDS ........................................................................................................................ 92
FIGURE 3-44: DATE & TIME - SET MANUALLY................................................................................................... 94
FIGURE 3-45: DATE & TIME - SYNC FROM NETWORK ......................................................................................... 94
FIGURE 3-46: DDNS SETTINGS ..................................................................................................................... 95
FIGURE 3-47: IPERF SETTINGS ....................................................................................................................... 96
FIGURE 3-48: DIAGNOSTICS – PING ................................................................................................................ 97
FIGURE 3-49: DIAGNOSTICS – TRACEROUTE .................................................................................................... 98
FIGURE 3-50: PORT MIRROR SETTINGS ........................................................................................................... 99
FIGURE 3-51: NETWORK SYSLOG SETTINGS ................................................................................................... 100
FIGURE 3-52: LOCAL SYSLOG SETTINGS ......................................................................................................... 101
FIGURE 3-53: PING WATCHDOG SETTINGS..................................................................................................... 102
FIGURE 3-54: SIMCARD CHECKING ............................................................................................................... 103
FIGURE 3-55: WEB SETTING FIELDS ............................................................................................................. 103
FIGURE 3-56: ACCOUNT SETTINGS ............................................................................................................... 104
FIGURE 3-57: LOGOUT ACTION ................................................................................................................... 105
FIGURE 4-1: CLOUDCORE SIGN UP AND LOGIN PAGE ....................................................................................... 107
FIGURE 4-2: CLOUDCORE USERS .................................................................................................................. 108
FIGURE 4-3: CLOUDCORE WEB PAGE ........................................................................................................... 108
FIGURE 4-4: CLOUDCORE NAVIGATION PANE ................................................................................................. 108
FIGURE 4-5: CLOUDCORE WELCOME MENU .................................................................................................. 109
FIGURE 4-6: CHANGE PASSWORD................................................................................................................. 109
FIGURE 4-7: LOCK SCREEN .......................................................................................................................... 109
FIGURE 4-8: OMC HELP > ABOUT ............................................................................................................... 110
FIGURE 4-9: CLOUDCORE > SYSTEM ............................................................................................................. 110
FIGURE 4-10: USER MANAGEMENT.............................................................................................................. 111
xi
FIGURE 4-11: SEARCH FOR USER.................................................................................................................. 111
FIGURE 4-12: MODIFY USER ....................................................................................................................... 111
FIGURE 4-13: LOCK/UNLOCK USER PASSWORD OR DELETE USER ....................................................................... 112
FIGURE 4-14: ADD USER ............................................................................................................................ 112
FIGURE 4-15: RESET PASSWORD .................................................................................................................. 113
FIGURE 4-16: OPERATION LOGS................................................................................................................... 113
FIGURE 4-17: SECURITY RULE...................................................................................................................... 114
FIGURE 4-19: DASHBOARD ......................................................................................................................... 115
FIGURE 4-20: ALARMS ............................................................................................................................... 116
FIGURE 4-21: ALARM DETAILS ..................................................................................................................... 117
FIGURE 4-22: CONFIRM OR CLEAR ALARM ..................................................................................................... 117
FIGURE 4-23: EXPORT................................................................................................................................ 118
FIGURE 4-24: STATISTICS ............................................................................................................................ 118
FIGURE 4-25: ENB ONLINE DETAILS ............................................................................................................. 119
FIGURE 4-26: ENB ACTIVE DETAILS (1 OF 2) .................................................................................................. 119
FIGURE 4-27: ENB ACTIVE DETAILS (2 OF 2) .................................................................................................. 120
FIGURE 4-28: CPE CONNECT DETAILS (1 OF 2) ............................................................................................... 120
FIGURE 4-29: CPE CONNECT DETAILS (2 OF 2) ............................................................................................... 121
FIGURE 4-30: PERFORMANCE ...................................................................................................................... 121
FIGURE 4-31: ENB MENU .......................................................................................................................... 122
FIGURE 4-32: ENB > MONITOR (1 OF 2) ....................................................................................................... 122
FIGURE 4-33: ENB > MONITOR (2 OF 2) ....................................................................................................... 123
FIGURE 4-34: DISPLAY ............................................................................................................................... 124
FIGURE 4-35: FILTER.................................................................................................................................. 125
FIGURE 4-36: RIGHT-CLICK ACTIONS ............................................................................................................ 125
FIGURE 4-37: RIGHT-CLICK > INFORMATION > STATISTICS ................................................................................. 126
FIGURE 4-38: RIGHT-CLICK > INFORMATION > ALARM ..................................................................................... 127
FIGURE 4-39: RIGHT-CLICK > INFORMATION > PERFORMANCE > KPI1: UL/DL THROUGHPUT................................. 128
FIGURE 4-40: RIGHT-CLICK > INFORMATION > PERFORMANCE > KPI2: UL/DL UTILIZATION ................................... 128
FIGURE 4-41: RIGHT-CLICK > INFORMATION > PERFORMANCE > KPI3: E-RAB ESTABLISHSUCCESSRATE ................... 128
FIGURE 4-42: RIGHT-CLICK > INFORMATION > PERFORMANCE > KPI4: E-RAB ESTABLISHFAILRATE ......................... 129
FIGURE 4-43: RIGHT-CLICK > INFORMATION > PERFORMANCE > KPI5: SUCCINTERENBS1RATE............................... 129
FIGURE 4-44: RIGHT-CLICK > INFORMATION > PERFORMANCE > KPI6: KPI6: RRC ESTABLISHDROPRATE.................. 129
FIGURE 4-45: RIGHT-CLICK > INFORMATION > LOGS > DEVICE REPORT LOG......................................................... 130
FIGURE 4-46: RIGHT-CLICK > INFORMATION > LOGS > DEVICE EXCEPTION LOG .................................................... 130
FIGURE 4-47: RIGHT-CLICK > SETTINGS > WIRELESS TAB .................................................................................. 131
FIGURE 4-48: WIRELESS SETTINGS > PB OPTIONS........................................................................................... 133
FIGURE 4-49: WIRELESS SETTINGS > BANDWIDTH OPTIONS .............................................................................. 133
FIGURE 4-50: WIRELESS SETTINGS > SFASSIGNMENT OPTIONS.......................................................................... 133
FIGURE 4-51: WIRELESS SETTINGS > SPECIAL SF PATTERNS OPTIONS .................................................................. 134
FIGURE 4-52: NETWORK SETTINGS............................................................................................................... 134
FIGURE 4-53: ICIC .................................................................................................................................... 135
FIGURE 4-54: NTP SETTINGS ...................................................................................................................... 135
FIGURE 4-55: REBOOT ............................................................................................................................... 136
xii
FIGURE 4-56: LOGS ................................................................................................................................... 137
FIGURE 4-57: CPES................................................................................................................................... 137
FIGURE 4-58: STRATEGY ............................................................................................................................. 138
FIGURE 4-59: NEW UPGRADE TASK.............................................................................................................. 139
FIGURE 4-60: SELECT UPGRADE FILE ............................................................................................................ 139
FIGURE 4-61: TASK RESULTS ....................................................................................................................... 140
FIGURE 4-62: OPERATION .......................................................................................................................... 140
FIGURE 4-63: REBOOT ............................................................................................................................... 141
FIGURE 4-64: CREATE REBOOT TASK ............................................................................................................. 141
FIGURE 4-65: REBOOT TASK WARNING ......................................................................................................... 142
FIGURE 4-67: FREQUENCY & PCI ................................................................................................................. 143
FIGURE 4-68: FILE LIBRARY ......................................................................................................................... 144
FIGURE 4-69: CPE MENU .......................................................................................................................... 144
FIGURE 4-70: CPE > MONITOR (1 OF 2) ....................................................................................................... 145
FIGURE 4-71: CPE > MONITOR (2 OF 2) ....................................................................................................... 145
FIGURE 4-72: CPE HISTORY ........................................................................................................................ 147
FIGURE 4-73: RIGHT-CLICK ACTIONS ............................................................................................................ 148
FIGURE 4-74: INFORMATION ....................................................................................................................... 148
FIGURE 4-75: SETTINGS ............................................................................................................................. 149
FIGURE 4-76: FREQUENCY LOCK .................................................................................................................. 149
FIGURE 4-77: STRATEGY ............................................................................................................................. 150
FIGURE 4-78: NEW UPGRADE TASK.............................................................................................................. 151
FIGURE 4-80: REBOOT ............................................................................................................................... 152
FIGURE 4-81: FILE LIBRARY ......................................................................................................................... 153
FIGURE 4-82: ALARM MENU ...................................................................................................................... 153
FIGURE 4-83: ACTIVE ALARMS .................................................................................................................... 154
FIGURE 4-84: ADVANCED QUERY ................................................................................................................. 154
FIGURE 4-85: RIGHT-CLICK ON AN ALARM ..................................................................................................... 155
FIGURE 4-86: ALARM DETAIL ...................................................................................................................... 155
FIGURE 4-87: ALARM CONFIRM................................................................................................................... 156
FIGURE 4-88: CLEAR ALARM ....................................................................................................................... 157
FIGURE 4-89: HISTORY ALARM .................................................................................................................... 157
FIGURE 4-90: LIBRARY ............................................................................................................................... 158
FIGURE 4-91: NOTIFICATION ....................................................................................................................... 158
FIGURE 4-92: SYSTEM MENU ...................................................................................................................... 159
FIGURE 4-93: DEVICE MANAGEMENT ........................................................................................................... 159
FIGURE 4-94: VIEW DEVICE GROUP INFORMATION.......................................................................................... 160
FIGURE 4-95: MODIFY DEVICE GROUP.......................................................................................................... 160
FIGURE 4-96: DELETE DEVICE GROUP ........................................................................................................... 161
FIGURE 4-97: DELETE ENB OR CPE .............................................................................................................. 161
FIGURE 4-98: ADD DEVICE ICON AND IMPORT DEVICE CONFIGURATION ICON ....................................................... 162
FIGURE 4-99: ADD DEVICE OR IMPORT DEVICE CONFIGURATION ........................................................................ 162
xiii
FIGURE 4-100: ADD DEVICE GROUP............................................................................................................. 162
FIGURE 4-101: MOVE TO DEVICE GROUP ...................................................................................................... 163
FIGURE 4-102: SELECT DEVICE GROUP ......................................................................................................... 163
FIGURE 4-103: SYSTEM USER MANAGEMENT ................................................................................................ 163
FIGURE 4-104: MODIFY USER GROUP > MENU TAB ........................................................................................ 164
FIGURE 4-105: MODIFY USER GROUP > OPERATION TAB.................................................................................. 164
FIGURE 4-106: MODIFY USER GROUP > DEVICE GROUP TAB............................................................................. 165
FIGURE 4-107: ADD USER GROUP ............................................................................................................... 165
FIGURE 4-108: LOG MANAGEMENT MENU ................................................................................................... 166
FIGURE 4-109: OMC OPERATION LOGS ........................................................................................................ 167
FIGURE 4-110: OMC OPERATION LOGS ........................................................................................................ 167
FIGURE 4-111: OMC SECURITY LOGS........................................................................................................... 168
FIGURE 4-112: OMC SYSTEM LOGS ............................................................................................................. 168
FIGURE 4-113: DEVICE LOGS ...................................................................................................................... 169
FIGURE 4-114: HELP ................................................................................................................................. 169
FIGURE 4-115: BOSS NETWORK ARCHITECTURE ............................................................................................ 170
FIGURE 4-116: BOSS MENU ...................................................................................................................... 170
FIGURE 4-117: SUBSCRIBER ........................................................................................................................ 171
FIGURE 4-118: QUERY............................................................................................................................... 171
FIGURE 4-119: ADD NEW SUBSCRIBER ......................................................................................................... 172
FIGURE 4-120: SIM QUERY ........................................................................................................................ 172
FIGURE 4-121: SERVICE PLAN SELECTION ...................................................................................................... 172
FIGURE 4-122: SUBSCRIBER DETAIL - OVERVIEW............................................................................................. 173
FIGURE 4-123: SUBSCRIBER DETAIL – SERVICE................................................................................................ 173
FIGURE 4-124: ARCHIVED SUBSCRIBERS ........................................................................................................ 174
FIGURE 4-125: RESTORE ARCHIVED SUBSCRIBER ............................................................................................. 174
FIGURE 4-126: NETWORK MENU ................................................................................................................ 175
FIGURE 4-127: NETWORK > SIM CARD ........................................................................................................ 175
FIGURE 4-128: IMPORT ............................................................................................................................. 175
FIGURE 4-129: IMPORT SIM CARD DIALOGUE ............................................................................................... 176
FIGURE 4-130: DOWNLOAD TEMPLATE ......................................................................................................... 176
FIGURE 4-131: IMPORT SIM CARD FILE ........................................................................................................ 177
FIGURE 4-132: SIM AUDIT RECORDS ........................................................................................................... 177
FIGURE 4-133: SYSTEM MENU .................................................................................................................... 178
FIGURE 4-134: SERVICE PLANS .................................................................................................................... 178
FIGURE 4-135: FILTER LIST OF SERVICE PLANS ................................................................................................ 179
FIGURE 4-136: ADD SERVICE PLAN .............................................................................................................. 179
FIGURE 4-137: ENABLE SERVICE PLAN .......................................................................................................... 180
FIGURE 4-138: LOGS ................................................................................................................................. 181
FIGURE 4-139: SERVICE PROCESSING FILTER LIST OPTIONS ............................................................................... 181
FIGURE 4-140: HELP ................................................................................................................................. 181
xiv
List of Tables
TABLE 2-1: COMPUTER REQUIREMENTS ............................................................................................................ 6
TABLE 2-2: BASIC INFO FIELDS ....................................................................................................................... 10
TABLE 2-3: STATUS INFO FIELDS ..................................................................................................................... 11
TABLE 2-4: UE STATUS FIELDS ....................................................................................................................... 12
TABLE 2-5: QUICK SETTING FIELDS ................................................................................................................. 13
TABLE 2-6: NTP FIELDS................................................................................................................................ 16
TABLE 2-7: INTERNET / WAN FIELDS .............................................................................................................. 20
TABLE 2-8: TUNNEL CONFIGURE > BASIC SETTING FIELDS ................................................................................... 23
TABLE 2-9: TUNNEL CONFIGURE > ADVANCE SETTING FIELDS .............................................................................. 25
TABLE 2-10: LTE NEIGH FREQ SETTINGS ......................................................................................................... 31
TABLE 2-11: LTE NEIGH CELL TABLE SETTINGS ................................................................................................. 33
TABLE 2-12: TD-S NEIGH FREQ TABLE SETTINGS .............................................................................................. 34
TABLE 2-13: TD-S CELL SETTING FIELDS.......................................................................................................... 36
TABLE 2-14: GSM FREQ/CELL > NEIGH FREQ TABLE SETTINGS ........................................................................... 37
TABLE 2-15: GSM FREQ/CELL > NEIGH CELL SETTINGS ..................................................................................... 38
TABLE 2-16: A1, A2, A3, AND A5 EVENT THRESHOLD FIELDS ............................................................................. 41
TABLE 2-17: B2 EVENT THRESHOLD FIELDS...................................................................................................... 42
TABLE 2-18: MEASUREMENT CONTROL FIELDS ................................................................................................. 43
TABLE 2-19: CELL SELECTION AND CELL RESELECTION FIELDS .............................................................................. 44
TABLE 2-20: POWER CONTROL PARAMETERS ................................................................................................... 47
TABLE 2-21: RRC STATUS PARAMETERS .......................................................................................................... 49
TABLE 2-22: SON FUNCTIONAL PARAMETERS .................................................................................................. 50
TABLE 2-23: RANDOM ACCESS PARAMETERS ................................................................................................... 51
TABLE 2-24: SYNC ADJUST PARAMETERS ......................................................................................................... 52
TABLE 2-25: LINK ACTIVATION STATE DETECTOR PARAMETERS ............................................................................. 53
TABLE 3-1: COMPUTER REQUIREMENTS .......................................................................................................... 58
TABLE 3-2: OVERVIEW FIELDS ....................................................................................................................... 63
TABLE 3-3: SIGNAL STRENGTH THRESHOLDS ..................................................................................................... 65
TABLE 3-4: NETWORK MODE > ROUTER SETTINGS ............................................................................................ 67
TABLE 3-5: LTE SETTINGS ............................................................................................................................. 70
TABLE 3-6: SCAN MODE SETTINGS ................................................................................................................. 71
TABLE 3-7: APN MANAGEMENT SETTINGS ...................................................................................................... 73
TABLE 3-8: DMZ SETTINGS .......................................................................................................................... 76
TABLE 3-9: STATIC ROUTE SETTINGS ............................................................................................................... 76
TABLE 3-10: LAN SETTINGS.......................................................................................................................... 77
TABLE 3-11: MAC FILTERING SETTINGS .......................................................................................................... 80
TABLE 3-12: IP FILTERING SETTINGS ............................................................................................................... 81
TABLE 3-13: PORT FORWARDING SETTINGS ..................................................................................................... 83
TABLE 3-14: ACCESS RESTRICTION SETTINGS .................................................................................................... 84
TABLE 3-15: UPNP STATUS FIELDS ................................................................................................................. 84
xv
TABLE 3-16: VPN SETTINGS AND STATUS ........................................................................................................ 85
TABLE 3-17: IPV6 STATUS AND SETTINGS ........................................................................................................ 87
TABLE 3-18: MAINTENANCE FIELDS................................................................................................................ 89
TABLE 3-19: FTP AUTO UPGRADE SETTINGS .................................................................................................... 91
TABLE 3-20: TR069 SETTINGS ...................................................................................................................... 93
TABLE 3-21: DATE & TIME – SYNC FROM NETWORK SETTINGS ............................................................................ 95
TABLE 3-22: DDNS SETTINGS ....................................................................................................................... 95
TABLE 3-23: IPERF SETTINGS AND RESULTS ...................................................................................................... 96
TABLE 3-24: DIAGNOSTICS – PING AND TRACEROUTE FIELDS .............................................................................. 98
TABLE 3-25: PORT MIRROR SETTINGS............................................................................................................. 99
TABLE 3-26: NETWORK SYSLOG SETTINGS ..................................................................................................... 100
TABLE 3-27: LOCAL SYSLOG SETTINGS .......................................................................................................... 101
TABLE 3-28: PING WATCHDOG SETTINGS ...................................................................................................... 102
TABLE 3-29: WEB SETTINGS....................................................................................................................... 103
TABLE 3-30: ACCOUNT SETTINGS ................................................................................................................. 104
TABLE 4-1: SERVER REQUIREMENTS.............................................................................................................. 106
TABLE 4-2: CLIENT REQUIREMENTS .............................................................................................................. 106
TABLE 4-3: ENB MONITOR FIELDS ............................................................................................................... 123
TABLE 4-4: WIRELESS SETTINGS ................................................................................................................... 131
TABLE 4-5: NTP SETTINGS.......................................................................................................................... 136
TABLE 4-6: CPE > MONITOR FIELDS ............................................................................................................. 145
TABLE 4-7: ALARM DETAIL .......................................................................................................................... 155
xvi
1. Introduction
Baicells products provide Wireless Internet Service Providers (WISPs), telecom operators, and
enterprises with the ability to offer users broadband wireless access to carrier networks that
are based on Frequency Division Duplexing (FDD) or Time-Division Duplexing (TDD) Long-Term
Evolution (LTE) technology. The Baicells system supports high-speed broadband data and voice
services, helping operators to serve users in locations that might otherwise be difficult to reach.
The key components of a Baicells system include the

• User Equipment (UE), also referred to as Customer Premise Equipment (CPE);
• Cell site equipment, comprising the eNodeB (eNB) - sometimes referred to as a base
station, base transceiver station, or cell - with integrated global positioning system
(GPS) and an operator-furnished RF antenna(s); and
• Operation, Administration, and Maintenance (OAM) software applications for
configuring and administering the Baicells network components.
The software applications include an eNB Graphical User Interface (GUI), a UE GUI, and options
for local or centralized CloudCore network applications. CloudCore is a Software-as-a-Service
(SaaS) solution managed and hosted by Baicells via Azure, a Microsoft based and North
American hosted Cloud computing platform. CloudCore includes three service modules:
Operations Management Console (OMC), Business Operations Support System (BOSS), and the
forthcoming Evolved Packet Core (EPC).
NOTE: EPC functionality is covered in separate documents, Baicells Enterprise EPC

Deployment Guide and Baicells Enterprise EPC User Guide.
Figure 1-1 illustrates a general Baicells system architecture. The photo is showing a Nova 1W
eNB.
1
Figure 1-1: Example Baicells Architecture
The GUI software applications typically are used to communicate with a specific device, i.e., a
single eNB or a single UE. Each eNB and each UE has their respective GUI application pre-
loaded on it from the manufacturer. The operator launches the GUI via an IP address using a
Web browser such as Google Chrome or Mozilla Firefox either locally or through the internet.
The GUI applications provide more configuration fields and data than does the CloudCore OMC.
Often, the additional fields are used to tune the radio frequency (RF) settings or network
settings of a given eNB or UE during troubleshooting or to improve the equipment’s
performance.
A sample window from the eNB GUI is presented in Figure 1-2. A sample window from the UE
GUI is presented in Figure 1-3. The GUI menu tree structures for both the eNB and the UE GUIs
are presented in Figure 1-4.
2
Figure 1-2: Sample eNB GUI Window
Figure 1-3: Sample UE GUI Window
3
Figure 1-4: eNB GUI and UE GUI Menu Trees
The CloudCore apps provide access to all of an operator’s Baicells network components and
subscribers. Administrators use the OMC to configure or modify the eNB and UE components
and interfaces, monitor the network, troubleshoot issues, and perform software or firmware
upgrades. A sample window from the CloudCore OMC is presented in Figure 1-5.
Administrators use the BOSS application to add, modify, and delete subscriber information and
service plans. It is also in BOSS where the administrator can activate each Subscriber
Identification Module (SIM) card, also called Universal SIM (USIM), a chip that the end-user
inserts in the UE to uniquely identify that subscriber and UE device.
While the eNB GUI, UE GUI, OMC, and BOSS pertain to the LTE radio access network (RAN),
the EPC is part of an operator’s core LTE network. EPC provides session management, mobility
management, security authentication, and policy management functions. The EPC functions
are covered in separate documents.
Operators that have carrier Network Management Systems (NMS) can centralize the Baicells
CloudCore and NMS by connecting CloudCore to NMS via the northbound networking
interface. Figure 1-6 shows the CloudCore GUI menu tree structures.
4
Figure 1-5: Sample CloudCore OMC Window
Figure 1-6: CloudCore GUI Menu Trees
The rest of this guide is organized by software application: eNB GUI, UE GUI, CloudCore OMC,
and CloudCore BOSS. Many of the device and subscriber parameters are preconfigured with
recommended default settings. However, every field and operation is explained and illustrated
in this guide to allow each operator the flexibility to use the Baicells solution to meet their
unique requirements.
5
2. eNB GUI
2.1 Computer Requirements

Table 2-1 describes the minimum requirements for 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, or Windows 7
Mac: MacOSX 10.5 or higher
Screen Resolution Higher than 1024 x 768 pixels
Browser Google Chrome 9 or higher
Internet Explorer 7.0 or higher
Mozilla Firefox 3.6 or higher
When accessing the eNB GUI locally, use an Ethernet cable to connect the computer Ethernet
interface to the MGMT interface port on the eNB unit. See example in Figure 2-1.
Figure 2-1: Local Interface
Before launching the GUI, you will need to set up the computer’s IP address to connect the
client to the server. The following steps are for a computer running Windows 7.
1. 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 to see the pop-
up window shown in Figure 2-2.
6
Figure 2-2: Internet Protocol Version (TCP/IPV4)
5. Select either Obtain an IP address automatically and proceed to step 7, or select Use
the following IP address and follow steps 6 and 7. In general, if the option for
obtaining the IP address automatically fails, you will need to set up the IP address
manually.
6. Use the following IP address option: Input the IP address, subnet mask, and default
gateway, where:
a. IP address is 192.168.150.xxx (where xxx is a number from 100 to 254).
b. Subnet mask is 255.255.255.0.
c. Default gateway is 192.168.150.1.
7. 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 Launching the GUI

To launch the GUI, open a Web browser and go to http://192.168.150.1. At the Login window,
enter Admin Name as admin and Admin Password as admin, and then click on Login. Refer to
Figure 2-3. The password may be changed after you first log in.
7
Figure 2-3: eNB GUI Login
After you log in, the main menus are shown in the left navigation pane. The fields that are
displayed on the right side of the window typically will be the last menu item that you looked
at. Use the up/down scroll bar on the right to see upper and lower fields, respectively. Use
the left/right scroll bar on the bottom to see fields on the left and right side of the window.
Refer to Figure 2-4.
Figure 2-4: eNB GUI Menu
2.3 Data Preparation

Before you start using the GUI to configure an eNB, first determine if you have the necessary
information at hand to make configuration decisions. You will need IP addresses, cell
information, protocol parameters, and so on. It may save you time overall to spend a few
minutes simply navigating through the GUI windows and reading through the correct sections
of this document before proceeding.
8
2.4 Configuration Flow
This document is organized around the visual flow of the GUI menus and fields. However, for
the initial configuration of the eNB interfaces and parameters, refer to the recommended
configuration flow provided in Figure 2-5. Also, refer to the Getting Started BaiTip on the
Baicells website: https://na.baicells.com/getting-started/
Figure 2-5: Initial Configuration Flow
2.5 BTS Info

When you log in to the eNB GUI, the GUI displays the navigation pane on the left side of the
window and the fields for the first menu item, BTS Info, on the right side. BTS stands for Base
Transceiver Station, a term used interchangeably with base station in the wireless industry
and with eNB used in LTE. “Transceiver” refers to the base station’s ability to both transmit
and receive radio signals.
2.5.1 Basic Info

The Basic Info sub-menu displays 3 blocks of status information: Basic Info, Status Info, and UE
Status, as shown in Figure 2-6 (showing full scroll-down view). The fields collectively provide a
quick overview about the eNB and its operational status. The Basic Info fields are described in
Table 2-2.
9
Figure 2-6: Basic Info Window
Table 2-2: Basic Info Fields
Field Name Description

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 (SN) for the eNB
MAC Data Link layer Media Access Control (MAC) address for the
eNB
The Status Info fields provide high-level information on operation and connectivity. The
fields are described in Table 2-3.
10
Table 2-3: Status Info Fields

Link Speed Negotiated Data rate negotiated between the eNB and the WAN
interface
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 (MME) 1 status is connected
or unconnected 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.
OMC Status The Operations Management Console (OMC) status is
connected or unconnected to the eNB.
IPSec Status The Internet Protocol Security (IPSec) gateway is connected
or unconnected 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.
OTA Sync Status Over-the-Air (OTA) status, either synchronized or not
synchronized with other eNBs in the area. Refer to section
2.8.3 for more information.
1588 Sync Status 1588V2 status, either synchronized or not synchronized
with other eNBs in the area. Refer to section 2.8.3 for more
information.
GPS Sync Status Global Positioning System (GPS) status, either synchronized
or not synchronized with other eNBs in the area. Refer to
section 2.8.3 for more information.
Radio Resource Usage Uplink (UL) and downlink (DL) use of the Physical Resource
Block (PRB) expressed as %. Indicates how busy the cell is.
The PRB is an LTE specification that allocates users a specific
number of subcarriers for a predetermined amount of time.
UL and DL Block Error Ratio (BLER), which represents a ratio

of the number of erroneous blocks received to the total
number of blocks sent. Expressed as %.
The UE Status fields provide a synopsis of the UEs connected to the eNB. The UE fields are
described in Table 2-4.
11
Table 2-4: UE Status Fields

UE Connections Number of UEs currently connected to the eNB
UE ID The UE Identification (ID) number
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.
IP Internet Protocol (IP) address for the eNB
PORT Port number assigned to the UE to allow remote logins. For
example, type in BS IP:5<last 4 digits of IMSI>
DownLink Rate (Mbps) The data throughput rate, in megabits per second (Mbps),
of data transmitted by the eNB to the UE
UpLink Rate (Mbps) The data throughput rate, in megabits per second (Mbps),
of data transmitted by the UE to the eNB
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-30dB.
dlcqi Downlink Channel Quality Indicator (DLCQI) 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 (ULMCS) is a
numerical index based on Orthogonal Frequency Division
Multiplexing (OFDM) that represents the maximum data
rate that 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 (DLMCS) – see
description for “ulmcs” above
txPower 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.
12
2.5.2 Quick Setting
The Quick Setting fields must be configured to determine the cell parameters, and are often
planned as part of the operator’s overall network design. The Quick Setting window is shown
in Figure 2-7, and the fields are described in Table 2-5. After modifying the Quick Settings, click
on Save to save the configuration. Use the Reset button if you want to reset the configuration
to the original default settings.
Figure 2-7: Quick Setting Window
Table 2-5: Quick Setting Fields

Duplex Mode Preset field that cannot be configured. The duplex mode of
the Baicells eNB is 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. Choices are:
• FCC, for United States Federal Communications
Commission
• Canada or Other Area
Band The eNB’s operating frequency band, which is specific to
13
the hardware model being used.
Bandwidth Channel bandwidth the eNB may use: either 10 MHz or 20
MHz. Applies to both uplink and downlink. The default is 20
MHz.
Frequency The eNB’s operating frequency, selected by the operator.
The range depends on the eNB hardware model and
country code.
SubFrame Assignment Downlink (DL) and uplink (UL) subframe configuration,
either 1 or 2, where:
1 = DL:UL is 2:2 transmission ratio
2 = DL:UL is 3:1 transmission ratio (default)
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
Patterns synchronization of downlink and uplink timing. The default
is 7.

subframes/163
PCI Physical Cell Identification (PCI) allocated by the operator.
Range is 0-503. PCI is Layer 1 identity, 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).
Cloud EPC The Cloud Evolved Packet Core (EPC) is either enabled or
disabled. The CloudCore EPC module is in testing and
planned for a future release. When you disable the Cloud
EPC setting, it unlocks the greyed out fields below it.
Cell ID The logical cell identification (ID) randomly assigned to this
eNB. The range is 0-268,435,455.
MME IP The Internet Protocol (IP) address of the Mobility
Management Entity (MME). The MME is responsible for
initiating paging and authentication of mobile devices.
There may be more than one MME in the network.
PLMN The numerical identifier for the operator’s Public Land
Mobile Network (PLMN) for this cell. Must be a 5- or 6-digit
number.
TAC Tracking Area Code (TAC) where the eNB is located. The TAC
14
is used to determine the range of the paging information.
The operator can use a number between 1 – 65,535. The
default is 1.
RF Status Enable or disable the eNB’s RF antenna. Default is enable.
Power Modify Output power on each port, typically left as 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.
2.6 System
The System menus are used for setting the Network Time Protocol (NTP), for upgrading or
downgrading the eNB operating software, for backing up the configuration database, and for
resetting the password to access the eNB configuration. The menu items and associated
fields are described in this section.
2.6.1 NTP
The operator may use more than one NTP server to provide correct time-of-day to the eNB.
The NTP window is shown in Figure 2-8, and the fields are described in Table 2-6. After
modifying the NTP settings, click on Save to save the configuration. Use the Reset button if
you want to reset the configuration to the original manufacturer’s default settings.
Figure 2-8: NTP Window
15
Table 2-6: NTP Fields

Current Date & Time Displays the current date and time that the eNB is using
NTP Sync Period Network Time Protocol (NTP) time interval for
synchronizing between the eNB and the primary NTP
server. The range is 10-65,535 seconds.
Time Zone The time zone where the eNB is located
Date Format The format of the date display, e.g., mm/dd/yy
NTP Servers – Server 1 Primary NTP server IP address
Port Primary NTP server port number
Server 2 Optional: Secondary NTP server IP address
Port Optional: Secondary NTP server port number
Server 3 Optional: Tertiary NTP server IP address
Port Optional: Tertiary NTP server port number
Server 4 Optional: Quaternary NTP server IP address
Port Optional: Quaternary NTP server port number
2.6.2 Upgrade
The Upgrade menu shown in Figure 2-9 provides the ability for you to upgrade software and
firmware, perform a software rollback (downgrade), or install patches to the current software
running on the eNB. In each case you will click on Choose File in the dialogue window that
opens, 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).
A software upgrade (or rollback) will reboot the eNB automatically. More upgrade/rollback
capabilities are provided through the OMC. Refer to section 4.4.2.2.1.
Caution: The reboot action will disrupt eNB service.
16
Figure 2-9: Upgrade Window
2.6.3 Backup
The Backup function is where you can acquire the backup files for the current configuration,
and the backup log files and crash files for the eNB; import configuration files (e.g., to create
a new eNB using the configuration from an existing eNB); and restore all of the default
configuration settings for the eNB. The System > Backup window is shown in Figure 2-10.
To initiate one of the backup actions, click on the appropriate button, e.g., Get Backup Files.
The system will display “Preparing backup file” and then present you with a dialogue window
for you to select where you want to save the file.
To import a configuration file, under Import Configuration Files select Choose File. Navigate to
the file you want to import, highlight the file and click on Open, and then select Import LTE
Configurations.
To restore the default configuration of the eNB, under Restore Default Configuration select
Restore Settings. The eNB will reboot when you perform a restore action.
17
Figure 2-10: Backup Window
2.6.4 Password
The System > Password menu allows you to change the eNB administrator’s password. Enter
the new password, from 5 to 15 characters, and then enter it again to confirm it. Click on Save
to save the password change. Refer to Figure 2-11. Use the Reset button if you want to reset
the password to the original default setting.
Figure 2-11: Password Window
18
2.7 Network
The Network settings are where you configure the network interfaces for the eNB. The
interfaces include the wide area network (WAN) or local area network (LAN), the Dynamic Host
Configuration Protocol (DHCP), virtual LANs (VLANs), the IP security (IPSec) gateway and
Mobility Management Entity (MME) pools, and the Local Gateway (LGW) mode.
You also will upload the certificate authority (CA) document, equipment certificate document,
and/or the certificate key document as part of the Network settings. The certificates carry the
authorization credentials to operate the eNB.
2.7.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. A WAN interface supports multiple
VLANs.
The LAN interface is used only as a local maintenance port during initial eNB setup and basic
configuration. The LAN interface is not used during normal eNB operation.
Figure 2-12 shows the Internet / WAN and Local Network / LAN fields. The Internet / WAN
fields are described in Table 2-7. For the Local Network / LAN fields, simply enter the IP address
and subnet mask address for the local network connection. The default IP address for the LAN
interface is 192.168.168.1. Click on Save to save the data. Use the Reset button if you want to
reset the configuration to the original manufacturer’s default settings.
Figure 2-12: Internet / WAN Fields
19
Table 2-7: Internet / WAN Fields

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
DNS Servers Domain Name Server (DNS) IP address. More than one DNS
server may be added.
2.7.2 DHCP
If a local DHCP server will be used, in the Network > DHCP menu check on the check box next
to LAN DHCP Server Enabled. You can 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.
Refer to Figure 2-13. After entering the information, click on Save to save the data. Use the
Reset button if you want to reset the configuration to the original manufacturer’s default
settings.
20
Figure 2-13: DHCP Window
2.7.3 VLAN
To add a virtual LAN, in the Network > VLAN window under VLAN Table click on New. This
opens a VLAN Setting window (Figure 2-14). 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.
For the Protocol Switch, select DHCP or Static. If you select Static, enter the IP address,
netmask, and gateway information. Then, click on Save.
For more information on setting up VLANs on the Nova eNBs, please refer to the BaiTip on the
Baicells website: https://community.na.baicells.com/t/setup-vlans-on-nova-enb/460
Figure 2-14: VLAN Windows
21
2.7.4 IPSec/MME Pool
The system will enable the IP Security (IPSec) gateway by default. The security protocols are
provided in the network layer to ensure the safety of message transmission. You can add,
modify, or delete an IPSec server using the Network > IPSec/MME Pool menu (Figure 2-15).
Figure 2-15: IPSec/MME Pool Window
Under IPSec Setting, the IPSec Status field should show a check mark in the box next to Enabled.
You can select the Internet Key Exchange (IKE) Negotiation Destination Port of either 4500 or
500. If you modify this information, click on Save to save the changes. Use the Reset button to
restore the default parameters.
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 Edit button, a new window called Tunnel Configure opens (Figure 2-
16), where you can configure the tunnel fields. Two tabs, Basic and Advance Setting, appear.
The Basic Setting fields are shown in Figure 2-16 and described in Table 2-8. The Advance
Setting fields are shown in Figure 2-17 and described in Table 2-9. The advanced settings
become particularly important to network operations as areas become denser.
Please read the following caution concerning the advanced IPSec settings.
22
Caution: It is highly recommended that you use the default
values and not change the advance settings for IPSec.
Improper changes may lead to system exception.
Figure 2-16: Tunnel Configure > Basic Setting
Table 2-8: Tunnel Configure > Basic Setting Fields

Enabled Check to enable or uncheck to disable 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.
Right Subnet IP address 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. 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. It must be consistent with
the security gateway side. If there is no security gateway
23
right identifier, leave this field empty.
Left Interface Options are:
• WAN(eth2)
• PPPOE(pppoe-wan)
• None
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!
Pre Shared Key (PSK) must be consistent with the security
gateway.
LeftSourceIP : string Virtual address allocation. If absent, use the local IP
address.
Figure 2-17: Tunnel Configure > Advance Setting

[Recommend leaving at default values]
24
Table 2-9: 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
• modp1024 (default)
• 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 are:
• 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:
• modp768
• modp1024 (default)
• modp1536
• modp2048
modp4096
ESP Authentication ESP authentication algorithm to be used:
• sha1 (default)
• sha512
KeyLife IPsec security association (SA) renegotiation time.
Format: s (seconds), m (minutes), h (hours)
The default setting is 20 minutes.
IKELifeTime IKE security association renegotiation time.
25
RekeyMargin Renegotiation time before the expiry of IKELifeTime
(negotiate the IKE security association time before the
expiry of IKELifeTime).
Self Define Keyingtries Number of renegotiation attempts after an IKE negotiation
fails. The 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.
The default setting is 30 seconds.
The MME Pool fields shown above in Figure 2-15 allow you to enable an MME pool and
identify up to 2 MMEs in the core network using their IP addresses. The interface binding
should already be defined under the Network > WAN/LAN window.
If you make any changes to the IPSec gateway, tunnel list, or MME Pool, click on Save to
retain the configuration changes. Use the Reset button to restore the configuration settings
to their original default values.
2.7.5 LGW
The local gateway (LGW) fields shown in Figure 2-18 allow you to enable or disable the
gateway; to select an LGW Mode of Network Address Translation (NAT), router, or bridge;
and to select an LGW Interface Binding of WAN or PPPoE. Most operators use bridge mode.
In older versions of code, NAT was the default. You can then enter the LGW IP Pool address
and network. The IP binding range is 10.10.0.1 to 10.10.0.254.
Figure 2-18: LGW Setting Window
26
For guidance on setting the LGW to router mode, please refer to the BaiTip on the Baicells
website: https://community.na.baicells.com/t/enb-basestation-lgw-router-mode-
configuration-example/89
2.7.6 CertStore
The Certificate (Cert) Store is a place within the eNB database for storing authorization
credentials. To upload any of the files, simply click on the Choose 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. This stores the documents with the other eNB
data. Refer to Figure 2-19.
Figure 2-19: CertStore Window
2.8 BTS Setting

The base transceiver station (BTS), or eNB, settings are related to security, management, and
synchronization with other network elements. Each menu item is explained in this section.
2.8.1 Security Setting

The Security Setting fields pertain to the LTE encryption algorithms used (Figure 2-20). The
selections will depend on the LTE core network setup. For the ciphering algorithm, you may
choose 128-EEA1, 128-EEA2, 128-EEA3, or EEAO. For the integrity algorithm, you may choose
128-EIA1, 128-EIA2, or 128-EIA3. If you make changes, click on Save. Use the Reset button to
restore the settings to their default configuration.
27
Figure 2-20: Security Setting Window
2.8.2 Management Server

You can use the CloudCore OMC to configure and administer the Baicells eNBs and UEs.
Enter the internet address for the CloudCore server to be used. The CloudKey field is related
to the plug-and-play aspect of the Baicells network elements. Newer versions of UE firmware
allow the UEs to be picked up automatically by the OMC without having to configure them
under Device Management. (OMC Device Management is covered in section 4.4.5.1 of this
document.) Once the UE is connected, if the CloudKey is entered on the UE it will be added
to the operator’s OMC account automatically.
In the CloudKey field, enter the CloudKey identifier using a range of 0-6 a-z, or A-Z, or 0-9.
Click on Save to save the configuration. Use the Reset button to restore the configuration
settings to their original default values. Refer to Figure 2-21.
Figure 2-21: Management Server Window
28
2.8.3 Sync Setting
The LTE technology standards specify timing and synchronization requirements between
adjacent eNBs. Synchronized transmission helps to avoid eNBs interfering with one another,
optimize bandwidth usage, and enhance network capacity.
Baicells supports multiple eNB synchronization methods. Operators may choose the
synchronization method to meet their network requirements. The default priority among the
different Baicells methods is as follows: Over-the-air interface (OTA), Global Positioning System
(GPS), and 1588V2 synchronization. Whichever method you select, you will enter the
parameters for that method and disable the other synchronization methods in the BTS Setting >
Sync Setting window (Figure 2-22).
Figure 2-22: Sync Setting Window
For OTA Sync, enter the scanning Public Land Mobile Network (PLMN) number (5- or 6-digit
integer), the scanning band (38, 39, or 40, depending on your eNB model), and the scanning
frequency [ranges from 38700 (2305 MHz) to 39600 (2395 MHz)].
If you enable GPS Sync, you can then choose which time reference type(s) to use for the GPS
clock:
• GPS – choose this option if you installed a GPS antenna with the eNB; it will reference
the atomic clock at the monitor stations and satellites, accurate within 25 ns.
• Glonass – generated by the GLONASS Central Synchronizer, whose time scale
implements leap seconds like Coordinated Universal Time (UTC).
29
• BeiDou – a continuous time scale which is synchronized with UTC within 100 ns.
• Galileo - a continuous time scale maintained by Galileo Central Segment, with an offset
of below 50 ns.
• Qzss – Quasi-Zenith Satellite System (QZSS) is a highly precise three or four orbiting
satellite timing system that is in development for Japan. Expected availability is by the
end of 2017.
Click on Save to save the configuration data. Use the Reset button to restore the configuration
settings to their original default values.
2.9 LTE
The LTE parameters are important for efficient wireless network operation. Through this menu
you will establish the neighboring eNBs operating in the same geographical area as 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.
Under this LTE menu, you will (a) configure the neighboring eNBs’ frequencies and identify
each eNB running on that frequency (section 2.9.1); (b) configure the current eNB’s mobility
parameters (section 2.9.2); and (c) examine the current eNB’s advanced settings (section 2.9.3).
It is a good idea to review all of the information in this 2.9 LTE section to understand how the
configuration settings interact. Note that many, if not all, of the advanced settings should be
left with their default values; any modification should be determined only by experienced
wireless professionals.
Make sure the current and neighboring eNBs are both GPS enabled and synchronized. With
any changes to these configuration parameters, reboot the eNB for the new configuration to
take effect. A case study for LTE to LTE handoffs is provided in section 2.9.4 Real-World LTE
Configuration Example.
2.9.1 Identify Neighbor Frequencies and 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.
30
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.9.1.1 LTE Freq/Cell

Using the LTE Freq/Cell sub-menu, you can configure parameters related to how adjacent eNBs
operating with LTE technology work with the Baicells eNB that you are configuring. You will
define for the Baicells eNB how to deal with any neighboring LTE eNBs.
2.9.1.1.1 LTE Neigh Freq Table
Under Neigh Freq Table, select New. This will open the Neigh Freq Settings window, as shown
in Figure 2-23 and described in Table 2-10. The parameters shown in the figurereflect the
recommended settings for this operator example. Click on Save to save the configuration data.
Figure 2-23: Neigh Freq Table
Table 2-10: LTE Neigh Freq Settings

EARFCN In short, this is the frequency point of the neighboring eNB’s
frequency. Range is 0-65,535. EARFCN tands 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. In this example, the recommended 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
31
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.
In this example, the recommended value is 0 dB.
Resel Timer Determines when the cell reselection timer expires. Range is
0-7 seconds. In this example, the recommended value is 0
seconds.
Resel Prior Priority of cell reselection to cells at this frequency. Range is 0-
7 (an integer). In this example, the recommended 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. In this example, the recommended value is 18 dB.
Resel Thresh Low The cell reselection threshold for 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). Range is 0-31 dB.
In this example, the recommended value is 13 dB.
P-Max The maximum transmit power that UEs in this cell are allowed
to use in the uplink. Range is -30 to 33 dBm. In this example,
the recommended value is 23 dBm.
2.9.1.1.2 LTE Neigh Cell Table

Under Neigh Cell Table, select New. This will open the Cell Setting window, as shown in Figure
2-24 and described in Table 2-11. The parameters shown in the figure reflect the
recommended settings for this operator example. Click on Save to save the configuration data.
32
Figure 2-24: LTE Freq/Cell > Neigh Cell Table Settings
Table 2-11: 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. In this
example, the recommended 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. In this
TAC Tracking Area Code (TAC) of this neighbor cell. Range is 0-
65535.
33
2.9.1.2 TD-S Freq/Cell
Using the TD-S Freq/Cell sub-menu, you can configure parameters related to how adjacent
eNBs operating with TD-SCDMA technology work with the Baicells eNB that you are
configuring. You will define for the Baicells eNB how to deal with any neighboring TD-SCDMA
eNBs.
2.9.1.2.1 TD-S Neigh Freq Table
Under TD-S Neigh Freq Table, select New. This will open the Neigh Freq Settings window, as
shown in Figure 2-25 and described in Table 2-12. Even though some of the field names are
the same as in Table 2-10 for LTE eNBs, in some cases the ranges are different for TD-SCDMA.
Click on Save to save the configuration data.
Figure 2-25: TD-S Freq/Cell > Neigh Freq Table Settings
Table 2-12: TD-S Neigh Freq Table Settings

TDD Mode Enter the Time Division Duplex (TDD) mode, one of three
possible chip rates (bps) used 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
34
Telecommunications System (UMTS) 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 -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 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.
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).
Range is 0-31.
P-Max The maximum transmit power that UEs in this cell are
allowed to use in the uplink. Range is -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.9.1.2.2 TD-S Neigh Cell Table

2-26 and described in Table 2-13. Click on Save to save the configuration data.
35
Figure 2-26: TD-S Freq/Cell > Neigh Cell Table Settings
Table 2-13: TD-S Cell Setting Fields

UARFCN Display of the frequency point of the neighboring eNB’s
frequency.
PLMN The Public Land Mobile Network (PLMN) that 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.
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.9.1.3 GSM Freq/Cell

Using the GSM Freq/Cell sub-menu, you can configure parameters related to how adjacent
eNBs operating with GSM technology work with the Baicells eNB that you are configuring. You
will define for the Baicells eNB how to deal with any neighboring GSM eNBs.
36
2.9.1.3.1 GSM Neigh Freq Table
Under GSM Neigh Freq Settings, select New. This will open the Neigh Freq Settings window,
as shown in Figure 2-27 and described in Table 2-14. Please note that even though some of
the field names are the same as in Table 2-10 for LTE eNBs, in some cases the ranges are
different for GSM. Click on Save to save the configuration data.
Figure 2-27: GSM Freq/Cell > Neigh Freq Table Settings
Table 2-14: 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. 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). 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).
Range is 0-31.
37
2.9.1.3.2 GSM Neigh Cell Table
2-28 and described in Table 2-15. Click on Save to save the configuration data.
Figure 2-28: GSM Freq/Cell > Neigh Cell Settings
Table 2-15: 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) that 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.
2.9.2 Configure Mobility Parameters

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-29.
*NOTE: The terms “handoff” and “handover” are used interchangeably in LTE.
38
Figure 2-29: 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.9.4 Real-World LTE 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-30 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.
39
Figure 2-30: Mobility Parameters
To begin the configuration, next to A1 Event Threshold select the + icon as shown in Figure 2-
30 above. The resulting window presents the fields for each sub-menu you open, as illustrated
in Figure 2-31, where A1, A2, A3, and A5 Event Threshold sub-menus have been opened.
The configuration values shown in Figure 2-31 are the recommended settings for the eNB in
this operator example*. Table 2-16 describes each of the A1, A2, A3, and A5 Event Threshold
fields. Click on Save to save the configuration data.
*NOTE: The Automatic Neighbor Relation (ANR) function is not supported at this time.
40
Figure 2-31: A1, A2, A3, and A5 Event Thresholds
Table 2-16: 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. 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/
41
baicellsoperatorsupportgroup/permalink/1760449424249426/
A3 Event Threshold
Intra-Freq Handover The LTE A3 event is triggered when a neighbor cell becomes
A3 Offset better than the serving cell by as much as the offset value. The
offset can be either positive or negative. Range is -30 dB to 30
dB. In this example, the recommended value is 10 (integer),
which means 10*0.5 = 5 dB.
Intra-Freq ANR A3 Automatic Neighbor Relation (ANR) – not supported at this
Offset time. Range is -30 dB to 30 dB. The integer should be less than
or equal to the Intra-Freq Handover A3 Offset parameter.
A5 Event Threshold
Inter-Freq Handover The LTE A5 event is triggered when the serving cell becomes
A5 RSRP Threshold 1 worse than Threshold 1 while a neighbor cell becomes better
than Threshold 2. Range is 0-97 dB. In this example, the
recommended value is 40 (integer), which equals -140 dBm +
40 = -100 dBm.
Inter-Freq Handover Range is 0-97 dB. In this example, the recommended value is
A5 RSRP Threshold 2 45 (integer), which equals -140 dBm + 45 = -95 dBm.
Inter-Freq ANR A5 Automatic Neighbor Relation (ANR) – not supported at this
RSRP Threshold 1 time. Range is 0-97. The integer should be larger than or equal
to the Inter-Freq Handover A5 RSRP Threshold 1 parameter.
Inter-Freq ANR A5 Automatic Neighbor Relation (ANR) – not supported at this
RSRP Threshold 2 time. Range is 0-97. The integer should be less than or equal
to the Inter-Freq Handover A5 RSRP Threshold 2 parameter.
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-32 and described in Table 2-17.
Click on Save to save the configuration data.
Figure 2-32: B2 Event Threshold
Table 2-17: B2 Event Threshold Fields

UTRA B2 RSRP Threshold parameter 1 of the UTRA Time Domain
Threshold 1 Scheduling (TDS) based B2 event. Range is 0-97 dB. Default
is 70 dB.
42
RSRP Threshold 2 Threshold parameter 2 of the Reference Signal Received
Power (RSRP) based B2 event. Range is -5 dB to 91 dB.
GERAN B2 RSRP Threshold parameter 1 of the GSM Edge Radio Access
Threshold 1 Network (GERAN) B2 event based on 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
Threshold 2 Network (GERAN) B2 event, based on Inter-Radio Access
Technology (IRAT). Range is 0-63 dB.
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 (refer to Figure 2-33 and Table 2-18). 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 Measurement Control Parameters are shown in Figure 2-33 and described in Table 2-18.
The parameters shown in the figure reflect the recommended settings for this operator
example. Click on Save to save the configuration data.
Figure 2-33: Measurement Control Parameters
Table 2-18: 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. 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.
Range is 0-5120 ms. In this example, the recommended
value is 480 ms.
43
The Cell Selection Parameter and Cell ReSelection Parameter sub-menus are shown in Figure
2-34 and described in Table 2-19. The parameters shown in the figure reflect the settings
recommended in this operator example. Click on Save to save the configuration data.
Figure 2-34: Cell Selection and Cell ReSelection Parameters
Table 2-19: 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. 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. 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
dB. 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. In
this example, the recommended value is 31 (integer), which
means 31*2 = -62 dB.
Qrxlevmin(dBm) Minimum level for reselection. Range is -70 dBm to -22
dBm. In this example, the recommended value is -62
(integer), which means -62*2 = -124 dBm.
44
Qhyst Delay time for reselection. Range is 0-24 dB. In this
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 low 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.
2.9.3 Configure Advanced Parameters

Many, if not all, of the advanced settings should be left with their default values. Any
modification should be determined only by experienced wireless professionals. Figure 2-35
shows the Advanced parameters sub-menus. Each one is explained in this section.
Figure 2-35: Advanced Parameters Sub-Menus
45
2.9.3.1 X2
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.
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-36). Click on Save to save the
configuration.
Figure 2-36: X2 Parameter
2.9.3.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-37 and described
in Table 2-20. Click on Save to save the configuration.
46
Figure 2-37: Power Control Parameters
Table 2-20: 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. Range is -60 dB to
50 dB.
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 Initial power of the Physical Random-Access Channel
Power (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.
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.
47
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.
Target ul sinr Desired Signal-to-Interference-Plus-Noise Ratio (SINR) level
to ensure an acceptable level 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.
Options are -600, -477, -300, -177, 0, 100, 200, or 300.

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.9.3.3 eNodeB
The eNodeB Settings sub-menu is used at this time to simply name the eNB you are configuring,
as shown in Figure 2-38. The types of characters and length of the name that may be used are
provided in the figure. Click on Save to save the configuration.
Figure 2-38: eNodeB Settings
48
2.9.3.4 GAP
The Inter-Frequency Measurement Gap 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 creates a gap in which the UE will not receive or transmit with the serving cell,
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 and 2 is a GAP measurement period of 80 ms. The default is 1
(40 ms). See Figure 2-39. Click on Save to save the configuration.
Figure 2-39: GAP Settings
2.9.3.5 RRC Status

In the Radio Resource Control (RRC) Status sub-menu, 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-40 and Table 2-21. Click on Save to
save the configuration.
Figure 2-40: RRC Status Parameters
Table 2-21: 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.
49
2.9.3.6 SON Functional
The Self-Organizing Network (SON) function refers to standards-based automation
technology designed to make the planning, configuration, management, optimization, and
healing of mobile radio access networks (RANs) simpler and faster. SON provides the plug-
and-play capability of newly deployed Baicells eNBs. When enabled, the new eNB will auto-
configure its Physical Cell Identifier (PCI). Refer to Figure 2-41 and Table 2-22. Click on Save to
Figure 2-41: SON Functional Parameters
Table 2-22: SON Functional Parameters

PCI Selfconfig Enable or disable self-configuration of the eNB Physical Cell
Identifier (PCI)
PCI Self-configuring The Physical Cell Identifier (PCI) numbers to use. Enter each
Optional List PCI number, and click on Add. The range is 0-503. To
remove a PCI number, select the Remove button.
2.9.3.7 Tx and Rx
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 0-76 dB. The default
value will be displayed. Refer to Figure 2-42.
Figure 2-42: Tx and Rx Settings
2.9.3.8 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 are shown
in Figure 2-43 and explained in Table 2-23. Click on Save to save the configuration.
50
Figure 2-43: Random Access Parameters
Table 2-23: Random Access Parameters

Preamble Format Packet preamble format (based on PRACH Index) to be
used for this cell and communicated to UEs. Options are
0 or 4.
Zero Correlation Zone Config Specifies the cyclic shift intervals to generate the PRACH
sequence. Range is 0-15. Default is 10.
subframes/163
PRACH Freq Offset Determines the location of the Physical Random-Access
Channel (PRACH) preamble in the frequency domain.
The range is:
• 10MHz – 1 to 43
• 20MHz – 2 to 92
2.9.3.9 Capacity
The Capacity parameters set a limit on the number of active UEs that can be supported
simultaneously by the eNB. If enabled, the eNB can support up to 96 UEs; if disabled, the
eNB can support a maximum of 32 UEs. Refer to Figure 2-44. Click on Save to save the
configuration.
Figure 2-44: Capacity Parameters
2.9.3.10 Scheduling Algorithm

The Scheduling Algorithms 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 strategies used are:
51
• MAXC/I or SCI– The 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.
• PFS – Proportionally Fair Scheduling (PFS) balances between user channel quality
and fairness, where both cell throughput and user fairness are not considered.
• RR – Round Robin (RR) scheduling allocates resources to all UEs equally. Neither QoS
nor memory is considered.
The uplink (UL) and downlink (DL) scheduling options are Max C/I or SCI, PFS, and RR. Refer
to Figure 2-45. Click on Save to save the configuration.
Figure 2-45: Scheduling Algorithm Parameters
2.9.3.11 Sync Adjust

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-46 and Table 2-24 concerning
these settings.
Figure 2-46: Sync Adjust Parameters
Table 2-24: Sync Adjust Parameters

GPS Sync Adjust Value An integer. Range is -65,535 to 65,535. Default is 0.
ICTA Adjust Value Industry Council for Tangible Assets (ICTA) Adjust Value is
an integer. Range is -65,535 to 65,535. Default is 0.
2.9.3.12 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 reboot the UE. If you select Disable, the watchdog will not reboot the UE.
Refer to Figure 2-47 and Table 2-25. Click on Save to save the configuration.
52
Figure 2-47: Link Activation State Detector Parameters
Table 2-25: Link Activation State Detector Parameters

Link Keep Alive Enable or disable the link activation state detector for the
link between the UE and EPC, LAN, or both
Link Keep Alive Timer Select 5, 10, or 15 minutes for the link keep alive timer
2.9.4 Real-World LTE Configuration Example

Following is a collective example of the LTE menu parameters, to illustrate how the system
performs based on the configuration settings. Figure 2-48 shows how the LTE Neigh Frequency
and Neigh Cell tables are configured in this example.
Figure 2-48: LTE Freq/Cell > Neigh Freq and Neigh Cell Table Settings
53
Concerning the A1, A2, A3, and A5 event thresholds, review the flowchart shown in Figure 2-
49. The serving eNB starts what is called 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.
Figure 2-49: Flowchart of Handoff Event Thresholds
For the A1 event threshold, assume the starting measurement is set to 45 (Figure 2-50). If the
UE measures RSRP > -95 dBm, the UE will report the A1 event and then the network will stop
the A1 and A5 event measurements and start the A2 event measurement.
54
Figure 2-50: A1 Threshold
Under the A2 Event Threshold, assume the LTE A2 RSRP threshold is set to 40 (Figure 2-51). 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.
For the A3 Event Threshold, assume the offset value is set to 10 (Figure 2-52). 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 threshold 1 is set to 40 and threshold 2 is set to 45 (Figure
2-53). 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.
55
Assume that X2 Handover is enabled (Figure 2-54). 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-54: X2 Handover
With any changes to these configuration parameters, reboot the eNB for the new configuration
to take effect.
2.10 Reboot
To reboot the eNB click on the Reboot menu item, and then click on Reboot Now as shown in
Figure 2-55. The eNB will automatically reboot.
NOTE: If you need to reboot the eNB, we recommend that you collect logs on the eNB
before you reboot it. That data may be needed for troubleshooting.
Figure 2-55: Reboot Action
2.11 Logout
To log out of the eNB GUI, click on the Logout menu item shown in Figure 2-56. You will
automatically be logged out of the GUI and presented with the login screen.
56
Figure 2-56: Logout Action
57
3. UE GUI

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
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
You can also use a Web browser to log in to the Web GUI to configure and manage the UE.
NOTE: Some service providers pre-configure the device using a CloudKey, which means
the device may already be configured in the network. Refer to Appendix D.
58
1. Set up the UE as instructed in the user manual for the device.
2. Open a Web browser, and enter http://192.168.254.1 (or enter
http://192.168.1.1 if on older firmware 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). The fields
displayed on the right side of the window may be the last menu item that you looked at.
Figure 3-3: UE GUI Main Menu
To change your password, go to System > Account. Here you can change the UE admin’s
password or the user’s password, as shown in Figure 3-4. Enter the current password, the
new password, and then re-enter the new password to confirm it. The password may be 5 to
15 ASCII characters (letters, numbers, and special characters). Click on Submit to save the
change. Select Enable User.
59
Figure 3-4: Change Password
3.3 Overview
The Overview menu provides system and device status information for the given UE. Scroll
down the page to see all of the fields (Figures 3-5, 3-6, 3-7, 3-8, and 3-9). The fields are
described in Table 3-2.
Figure 3-5: Overview Fields (1 of 5 Screens)
60
61
62
Table 3-2: Overview Fields

System Information
Device Up Time Displays the duration of time the UE has been powered on,
in hours and minutes
Connection Time Displays the duration of time the UE has been connected to
the LTE network, in hours and minutes
Device Information
Model Name The model of UE hardware in use
Software The operating software version that the UE is running
Firmware The firmware software version in the UE
BootROM The bootrom software version in the UE
SN The UE’s unique serial number
IMEI The UE’s unique International Mobile Equipment Identity
(IMEI) number, a 15- or 17-digit code that uniquely
identifies mobile devices
IMSI The UE’s International Mobile Subscriber Identity (IMSI)
number, a unique identification associated with the cellular
LTE network.
LTE Supported Band The UE’s operating band, either 41 or 42/43. (Additional
bands are planned on the product roadmap.)
Module SN The UE’s Subscriber Identification Module (SIM) serial
number (SN)
Hardware Version The UE’s hardware version number
CloudKey For operators using CloudCore, the CloudKey is a number
assigned to this UE so that the UE can be identified
automatically by the Baicells Operations Management
Center (OMC). Once the UE is connected, if the CloudKey is
entered on the UE it will be added to the operator’s OMC
account automatically.
NickName Optional subscriber or UE unit name
CPU Usage
Current Displays the current percent of CPU usage
Max Displays the maximum percent of CPU usage since the last
reboot
Min Displays the minimum percent of CPU usage since the last
reboot
Memory Usage
Total Displays the total amount of memory used, in kilobytes (KB)
Current Displays the current percent of memory used
63
Max Displays the maximum percent of memory used since the
last reboot
Min Displays the minimum percent of memory used since the
last reboot
LTE Status
USIM Card Status The UE’s Universal Subscriber Identity Module (USIM) card
status, either normal or not ready
Status The UE is either connected or unconnected from the LTE
network
Mode LTE mode is Time Division Duplexing (TDD) or Frequency
Division Duplexing (FDD)
Operator The operator’s identification number
Signal Strength Indicates the strength of the signal between this UE and the
serving eNB, either Strong, Good, or Weak. Some UEs have
3 LEDs, and some have 5 LEDs. Signal strength thresholds
are determined per the values given in Table 3-3.
SINR Signal-to-Interference-Plus-Noise Ratio (SINR) of the signal
received from the eNB, expressed in decibels (dB)
DL MCS The downlink signal (eNB to UE) Modulation and Coding
Scheme (MCS) currently being used (index)
UL MCS The uplink signal (UE to eNB) Modulation and Coding
Scheme (MCS) currently being used (index)
DL Data Rate The current, maximum, and minimum downlink (eNB to UE)
data throughput rate
UL Data Rate The current, maximum, and minimum uplink (UE to eNB)
data throughput rate
DNS Server Domain Name Server (DNS) information:
• APN Name • Access Point Name (APN) for each eNB with which
the UE can communicate
• Status • The DNS server for each eNB reports as either
Enabled or Disabled
• IP Address • The IP address of the DNS server
• Subnet Mask • The subnet mask address of the DNS server
LAN Status
MAC Address The UE’s Media Access Control (MAC) address
IP Address The UE’s local Internet Protocol (IP) address
Subnet Mask The UE’s local subnet mask address
Throughput Statistics (for Access Point Names, or APNs, and LAN)
Port The Access Point Name (APN), or eNB, with which this UE is
communicating
Received Total Traffic Total amount of traffic received through this APN, in
64
megabytes (MB) since the last reboot
Received Packets The total number of packets received from this APN
Received Errors Number of errors reported on packets received from the
APN
Received Dropped Number of dropped packets received from the APN
Sent Total Traffic Total amount of traffic sent from the UE to this APN, in
megabytes (MB) since the last reboot
Sent Packets The total number of packets this UE sent to the APN
Sent Errors Number of errors reported on packets sent from this UE to
the APN
Sent Dropped Number of dropped packets sent from this UE to the APN
Device List
Index List number of device connected to the UE on the LAN port
Device Name Name of the device connected to the UE on the LAN port
MAC Address Media Access Control (MAC) address of the device
connected to the UE on the LAN port.
IP Address IP address of the device connected to the UE on the LAN
port
Lease Time Amount of time the UE’s IP address has been leased
Type Type of device, LAN or DHCP
Table 3-3: Signal Strength Thresholds
# LEDs RSRP<-115 -115≤RSRP<-110 -110≤RSRP<-105 -105≤RSRP<-95 -95≤RSRP<-85 -85≤RSRP
3 0 1 1 1 1 1
SINR < -3
5 0 1 1 1 1 1
-3≤SINR<1 3 0 1 2 2 2 2
5 0 1 2 2 2 2
1≤SINR<4.6 3 0 1 2 2 2 2
5 0 1 2 3 3 3
4.6≤SINR<13 3 0 1 2 2 2 3
5 0 1 2 3 4 4
13≤SINR 3 0 1 2 2 2 3
5 0 1 2 3 4 5
In the top part of the UE GUI window are some icons. If you hover over the first icon you will
get a quick status on the Universal Subscriber Identity Module (USIM) card for the UE (Figure
3-10). You will also see the current signal strength; the more “bars” shown the better the
signal strength.
65
Figure 3-10: USIM Status Icon
3.4 Network
The Network menu opens to several sub-menus, as shown in Figure 3-11.
Figure 3-11: Network Sub-Menus
When you select Network, it opens to the first sub-menu, Network Mode (Figure 3-12). You
can select the network mode as either Network Address Translation (NAT), Router, or Bridge.
In older versions of code, NAT was the default. Most operators use bridge mode.
Figure 3-12: Network Mode
66
Depending on which mode you select, you may see additional configuration fields. The
Router settings are shown in Figure 3-13 and described in Table 3-4. The fields with an
asterisk (*) next to them are mandatory.
Figure 3-13: Network Mode > Router Settings
Table 3-4: Network Mode > Router Settings

Network Mode NAT, Router, or Bridge
Connection Mode Select to use either Dynamic Host Control Protocol (DHCP)
or static IP address
Host Name See options in Figure 3-14
WAN IP Address Enter the WAN IP address
WAN Subnet Mask Enter the WAN subnet mask
WAN Gateway Address Enter the WAN gateway address
WAN MTU Enter the maximum transmission unit (MTU) for the WAN
interface. This value indicates the size of the largest
network layer protocol data unit (PDU) that the eNB can
communicate in a single transaction. The range is 576-1500
67
bytes.
DNS1 Enter the IP address of the primary Domain Name Server
(DNS).
DNS2 Enter the IP address of the secondary Domain Name Server
(DNS).
NTP1 Select the primary Network Time Protocol (NTP) server.
NTP2 Select the secondary Network Time Protocol (NTP) server.
Optional NTP Server If you wish to use additional NTP servers, select the check
box and enter the location.
Figure 3-14: Host Name Options
When you are finished configuring the UE in router mode, click on the Submit button to save
the changes.
If you set the Network Mode to Bridge mode and click on Submit, the system will prompt
you to be sure you want to make that change. Selecting OK will cause the UE to restart, thus
interrupting current service. Refer to Figure 3-15.
The same warning message and restart will occur if you switch from Bridge to NAT or Router
mode.
68
Figure 3-15: Bridge Mode
3.4.1 LTE Settings

The LTE Settings sub-menu primarily offers information about the UE’s connection to the
eNB. You can, however, configure the connection method as either Auto or Manual. If you
change the method, select Submit to save the change. Refer to Figure 3-16 and Table 3-5 for
information about each field.
Figure 3-16: LTE Settings
69
Table 3-5: LTE Settings

Settings
Status Displays the connected or disconnected status of the UE to
the eNB
Signal Strength Indicates the strength of the signal between this UE and the
serving eNB, either Strong, Good, or Weak. Refer back to
Table 3-3 for the thresholds.
Connect Method Manual or Auto connect to the LTE network. If you change
the connection method, click on Submit to save the
change.
Status
DL MCS The downlink (eNB to UE) signal Modulation and Coding
Scheme (MCS) currently being used
UL MCS The uplink (UE to eNB) signal Modulation and Coding
Scheme (MCS) currently being used
DL Frequency The frequency at which the downlink (eNB to UE) traffic is
being communicated, expressed in kilohertz (KHz)
UL Frequency The frequency at which the uplink (UE to eNB) traffic is
being communicated, expressed in kilohertz (KHz)
Bandwidth 10,000 KHz (10 MHz) or 20,000 KHz (20 MHz), depending
on the UE model
RSRP The Reference Signal Received Power (RSRP) from the eNB,
expressed in dBm
RSRQ The Reference Signal Received Quality (RSRQ) from the
eNB, expressed in dB
SINR Signal-to-Interference-Plus-Noise Ratio (SINR) of the signal
received from the eNB, expressed in dB
CINR Carrier-to-Interference-Plus-Noise (CINR, or C/I) reflects the
signal quality of the signal received from the eNB,
expressed in dB
Tx Power Transmit (Tx) power of the signal received at the UE from
the eNB
PCI Physical Cell Identifier (PCI) which uniquely identifies the
cell site in the wireless network
Cell ID The logical cell identification (ID) randomly assigned to this
eNB. The range is 0-268,435,455.
MCC Unique Mobile Country Code (MCC) used to identify the
operator of this network. MCC + MNC = PLMN.
MNC Unique Mobile Network Code (MNC) used to identify the
network operator. MNC + MCC = PLMN.
70
3.4.2 Scan Mode
The Scan Mode setting 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 Figures 3-17, 3-18, and 3-19 to view the Scan Mode configuration fields based on
which mode you select. The fields are explained in Table 3-6. Click on Submit to save the
configuration.
Figure 3-17: Scan Mode Settings
Table 3-6: Scan Mode Settings

Settings
Scan Mode Select one of the following:
• FullBand – The UE will routinely scan all channels in
the band. The band is dependent on the model of UE
being used. Click on Submit after selecting this
option.
• 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-18). After entering the
information, click on Add and then Submit. You can
add more than one PCI Lock list. The UE will scan the
list for eNBs with the PCI and EARFCN combination.
• Band/Frequency Preferred – You can specify which
band(s) the UE will scan. After selecting
Band/Frequency Preferred, click on Add List. This will
71
open an EARFCN settings field (Figure 3-19). Select
the desired EARFCN from the drop-down list, and
then click on Add to add the list. Click on Submit to
save the changes.
Figure 3-18: PCI Lock Settings
Figure 3-19: Band/Frequency Preferred Settings
72
3.4.3 APN Management
In the Access Points Name (APN) Management menu, you can configure up to 4 eNBs to
which this UE may connect. Refer to Figure 3-20 and Table 3-7 concerning the parameters.
Click on Submit to save your data.
Figure 3-20: APN Management Settings
Table 3-7: APN Management Settings

APN Selection
APN Number Select the APN number – 1, 2, 3, or 4
APN Settings
Enable Select the check box next to Enable to enable this APN
Name Required field: Enter a name for this APN
APN Name Enter the name of this APN, as defined in the eNB
configuration
Authentication Type Select type of authentication required for this eNB:
• None – the eNB is not required to authenticate itself to
the UE
• PAP – stands for Password Authentication Protocol,
where the eNB will authenticate itself to the UE using a
static user name and password
• CHAP – stands for Challenge-Handshake Authentication
Protocol, where the eNB will authenticate itself to the
UE through an authenticating entity
73
PDN Type Select the type of Packet Data Network (PDN) the eNB can
use when communicating with this UE: IPv4, IPv6, or IPv4v6
MTU Required field: Enter the Maximum Transmit Unit (MTU),
which is the size of the largest network layer protocol data
unit (PDU) that the eNB can communicate in a single
transaction. The range is 576 to 1500 bytes.
Manage Interface To enable a management interface to this eNB, select the
check box next to Enable.
Default Gateway To enable a default gateway to this eNB, select the check
box next to Enable.
3.4.4 PIN Management

The Personal Identification Number (PIN) Management function allows you to enable or
disable the subscriber requirement to enter a PIN before using the UE. The PIN provides an
additional layer of security to protect the UE against unauthorized use, such as for
unauthorized access to the internet.
Select Enable or Disable for the PIN Verification setting, as shown in Figure 3-21. When you
enable PIN Verification, you are prompted to define a 4- to 8-digit PIN number. As indicated
in the figure, the user is allowed up to 3 attempts after the first attempt to enter the correct
PIN before being locked out. Note that you can elect to Remember My PIN. Click on Submit
to save your changes.
Figure 3-21: PIN Management Settings
74
3.4.5 SIM Lock
The UE’s Subscriber Identification Module (SIM) card may be locked to the operator’s network
based on the 3-digit Mobile Country Code (MCC) and the 2- or 3-digit Mobile Network Code
(MNC). Enter the settings as shown in Figure 3-22. The MCC + MNC = Public Land Mobile
Network (PLMN). Click on Submit to save your data.
Figure 3-22: SIM Lock Settings
3.4.6 DMZ Settings

In technology, the Demilitarized Zone (DMZ) refers to a firewall between incoming WAN traffic
and the LAN to which the UE is connected. 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-23 and Table 3-8. Save any
changes by clicking on Submit.
Figure 3-23: DMZ Settings
75
Table 3-8: DMZ Settings

DMZ Enable or disable the DMZ server
ICMP Redirect Enable or 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.4.7 Static Route

If the APN Management Authentication Type is set as Password Authentication Protocol (PAP),
in this Static Route sub-menu you will define the static route addressing to be used between
the eNB and this UE. You may define more than 1 static route to use. To add a static route, click
on Add List. The Static Route Settings fields will appear. The fields are shown in Figure 3-24
and explained in Table 3-9. Click on Submit to save your data.
Figure 3-24: Static Route Settings
Table 3-9: Static Route Settings

Dest IP Address Enter the destination (eNB) IP address
Subnet Mask Enter the eNB’s subnet mask address
Interface Identify this interface by selecting APN1, APN2, APN3,
APN4, or LAN
76
3.4.8 LAN Settings
In this sub-menu, you can enter or change the IP address settings for the UE. By default, the IP
address is 192.168.254.1 and the subnet mask is 255.255.255.0. If you change it, for example
to make the address easier to remember, make sure that the address you choose is unique to
your network. You will need to access the Web management page with the new IP address.
You can bind an IP address to the UE based on its Media Access Control (MAC) address. If
binding is configured, the UE will receive the same IP address each time it accesses the DHCP
server. 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. After entering the information, click on
Submit to save your data. Refer to Figure 3-25 and Table 3-10.
Figure 3-25: LAN Settings
Table 3-10: LAN Settings

LAN Host Settings
IP Address Enter the UE’s IP address
Subnet Mask Enter the UE’s subnet mask address
DHCP Settings
77
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.5 Security
The Security menu opens to several sub-menus, as shown in Figure 3-26.
Figure 3-26: Security Sub-Menus
When you select Security, it opens to the Firewall Setting (Figure 3-27). If you enable the
firewall, the other sub-menus allow you to configure the firewall ‘s MAC filter, IP filter, and so
forth. Each of these is explained in the following sections. If you make a change, click on Submit
to save the data.
78
Figure 3-27: Security Sub-Menus
3.5.1 MAC Filtering

Media Access Control (MAC) Filtering allows you to identify a list of devices either allowed to
access or denied from accessing the UE. Select Enable to enable MAC filtering, and then
determine whether you will allow or deny the defined MAC address to access the UE. Refer to
Figure 3-28 and Table 3-11. To add a MAC Filtering rule, under MAC Filtering List select Add
List. After entering the information, select Submit to save the data.
Figure 3-28: MAC Filtering Settings
79
Table 3-11: MAC Filtering Settings

MAC Filtering Manager
MAC Filtering Select the check box next to Enable to enable MAC filtering
Within the Rule to Select Allow to allow the MAC addresses in the MAC
Allow/Deny Filtering List; or, select Deny to deny the MAC addresses in
the MAC Filtering List
MAC Filtering List
Index List number
MAC Address Enter the MAC address to allow or deny access to the UE
3.5.2 IP Filtering
Internet Protocol (IP) filtering allows you to filter data based on the IP address of the source
device. You can define a list of devices either allowed to access or denied from accessing the
UE. The IP Filtering sub-menu enables you to configure the IP address range, as shown in Figure
3-29 and explained in Table 3-12. To add an IP filtering rule, under IP Filtering List select Add
List to open the configuration fields. Select Submit to save the data.
Figure 3-29: IP Filtering Settings
80
Table 3-12: IP Filtering Settings

IP Filtering Manager
IP Filtering Select the check box next to Enable to enable IP filtering
Except the Rules to Select Allow to allow the IP addresses in the IP Filtering List;
Allow/Deny or, select Deny to deny the IP addresses in the MAC
Filtering List
IP Filtering List
Index List number
Service Select the type of service, either Custom, FTP, SSH, TELNET,
SMTP, HTTP, POP3, HTTPs, HTTP Proxy to allow or deny
from the UE
Protocol Select the type of data protocol, either ALL, TCP, UDP,
TCP&UDP, or ICMP to allow or deny from the UE
Source IP 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 IP Address Enter the IP address range for the destination device(s) to
Range be filtered, in the format of x.x.x.x or x.x.x.x/mask. The
mask value may be 0 or 32.
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 deny the current status of the IP Filtering List
3.5.3 URL Filtering

The Uniform Resource Location (URL) Filtering function allows you to filter data from URL
addresses. You can define a list of URL addresses either allowed to access or denied from
accessing the UE. The URL Filtering sub-menu enables you to configure the specific URL
addresses, as shown in Figure 3-30. First, under URL Filtering Manager select the check box
next to Enable. Click on Submit. To add a URL filtering rule, under URL Filtering List select Add
List. After entering the information, select Submit to save the data.
81
Figure 3-30: URL Filtering Settings
3.5.4 Port Forwarding

When Network Address Translation (NAT) is enabled on the UE, 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), port forwarding 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 Add List as shown in Figure 3-31. The fields are
explained in Table 3-13. After entering the information, select Submit to save the data.
Figure 3-31: Port Forwarding Settings
82
Table 3-13: Port Forwarding Settings

Service 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, or 1000.
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.5.5 Access Restriction

You can add other access restriction rules on a per-device basis. For each device you can
restrict which days and the time-of-day period to restrict the device from accessing the UE.
Refer to Figure 3-32 and Table 3-14. After entering the information, click on Submit to save
the data.
Figure 3-32: Access Restriction Settings
83
Table 3-14: Access Restriction Settings

Enable Enable or disable the restriction on this device
Name Enter a name for the device
Device Enter the device’s MAC or IP address
Weekdays Select which days of the week to restrict access
Time Select the beginning and ending time of day in hours (using
military time 0-24 hours) and minutes to restrict access
3.5.6 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.
In the UPnP sub-menu you can either enable or disable UPnP. To enable, select the check box
next to Enable, and then click on Submit. When enabled, the current status of each UPnP
device will be displayed under Current UPnP Status. Refer to Figure 3-33 and Table 3-15. To
disable UPnP, simply uncheck the check box next to Enable and again click on Submit.
Figure 3-33: UPnP
Table 3-15: UPnP Status Fields

Index List number
Description Description of the type of UPnP device
Protocol The type of data protocol, either TCP, UDP, or TCP&UDP
IP Address The UPnP device’s IP address
84
External Port Port number through which the UPnP device is
communicating with the WAN
Internal Port Port number through which the UPnP device is
communicating with the LAN
3.6 VPN
The Virtual Private Network (VPN) menu enables you to connect the UE to a VPN. To enable
the UE to use a VPN, select the check box next to Enable. Enter the settings as shown in
Figure 3-34 and described in Table 3-16. After entering the information, click on Submit to
save the changes. The status of the VPN will then display.
Figure 3-34: VPN Settings
Table 3-16: VPN Settings and Status

VPN Settings
VPN Select the check box next to Enable to enable a VPN for this
UE
Protocol Select the type of protocol the VPN uses, either PPTP, L2TP,
or GRE
VPN Server Enter the IP address of the VPN server
Username Enter a user name for the VPN
Password Enter a password for the VPN
VPN Status
Username VPN user name
Local Address VPN address on the LAN
85
Remote Address VPN address on the WAN
Online time Amount of time the VPN has been in use by this UE
3.7 IPv6
When IPv6 addressing has been enabled under Network > APN Management > PDN Type,
this sub-menu (Figure 3-35) allows you to enable or disable IPv6 on the WAN, and to set the
auto-configuration type for the LAN.
Figure 3-35: IPv6 Sub-Menu
The IPv6 status and configuration fields are shown in Figures 3-36, 3-37, and 3-38, and
described in Table 3-17. After entering the information, click on Submit to save the data.
Figure 3-36: IPv6 Settings > Status
86
Figure 3-37: IPv6 WAN Settings
Figure 3-38: IPv6 LAN Settings
Table 3-17: IPv6 Status and Settings

IPv6 Information
IPv6 Status IPv6 is reported as either enabled or disabled
WAN Connection Type AutoConfiguration is the only connection type at this time
IPv6 MGMT Global DHCPv6 is the only MGMT address at this time
Address
WAN Settings
IPv6 Enable Select the check box next to Enable to enable IPv6 packets
87
on the WAN interface
WAN Connection Type AutoConfiguration is the only option you can select
IPv6 MGMT Global DHCPv6 is the only option you can select
Address DNS From
LAN Settings
IPv6 Link-Local Address Displays the MAC address for the DHCPv6 server
AutoConfiguration Type Select either SLACC (stands for StateLess
AutoConfiguration) or DHCPv6 for the autoconfiguration
type
3.8 System
The System menu provides a number of operations that affect the UE. The System sub-
menus are shown in Figure 3-39 and explained in the sections that follow.
Figure 3-39: System Sub-Menus
88
3.8.1 Maintenance
The Maintenance sub-menu shown in Figure 3-40 provides a quick, high-level way to
start/stop, reset, back up, and restore UE functions and data. Such functions are typically
used when troubleshooting UE issues. The Maintenance fields are described in Table 3-18.
Figure 3-40: Maintenance
Table 3-18: Maintenance Fields

Radio If the UE’s radio is on, the OFF button will be shown. If the
UE’s radio is off, the ON button will be shown. Click on the
button to turn the UE radio on or off.
Restart Clicking on Restart will restart the UE. Some changes in
configuration settings require a restart action for the
changes to take effect.
Reset Clicking on the Reset button restores the UE to its default
89
factory settings
Backup Configuration File Clicking on the Backup button backs up the UE’s current
configuration
Restore Configuration File Clicking on Restore restores a UE’s configuration database
based on the target file that you select. The UE will upload
the configuration file and then restart automatically.
3.8.2 Version Manager

Version Manager displays the current UE model and software version, and allows you to
select a different (typically, newer) software version of code to upload to the UE. Most
operators should ensure that the UEs are operating with the most current available code.
Each version released from Baicells includes bug fixes and sometimes new features.
Navigate to the upgrade file and select it, click on Open, and then click on Submit to save the
changes. Refer to Figure 3-41. The software upgrade will start immediately. 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.
Figure 3-41: Version Manager Fields
3.8.3 FTP Auto Upgrade

The FTP Auto Upgrade function provides the ability for the UE to be upgraded automatically
whenever a newer software version is detected. This assumes the new software file is stored
on an FTP server, and that the UE can communicate with that server. This auto upgrade
function is particularly helpful when you have a large number of UEs to upgrade.
90
To perform an FTP auto-upgrade successfully, make sure the UE is connected to the internet.
At the FTP Auto Upgrade field, select the check box next to Enable. This will open the
configuration settings, as shown in Figure 3-42 and described in Table 3-19. Once you have
entered the information, click on Submit to save the data.
Caution: The UE will upgrade automatically according to the

settings configured here. During the upgrade, do not disconnect
the power supply or operate the UE.
Figure 3-42: FTP Auto Upgrade Fields
Table 3-19: FTP Auto Upgrade Settings

Check New FW after You can enable the FTP server to check for newer UE
connected firmware if you click the check box next to Enable. When
enabled, and when the UE is connected to the internet, the
UE will check for newer versions of code, as specified in the
settings that follow.
Upgrade Folder Enter the FTP server address (URL)
Version File Enter the file name of the software version you want to use
to upgrade the UE
Username Enter the user name to access the FTP account
Password Enter the password to access the FTP account
91
Check New FW Every Schedule how often the UE will check for a new software
version, e.g., every 24 hours. Select the check box, and
enter the time in hours. The range is 1 to 740 hours.
Start Time (24hrs) Enter the time-of-day you want the UE to check for newer
software
3.8.4 TR069
If your network operates using a TR-069 auto-configuration server (ACS), the ACS will
automatically provide the UE parameters. If you set 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-
43 and explained in Table 3-20. After entering, click on Submit to save the data.
Figure 3-43: TR069 Fields
92
Table 3-20: TR069 Settings

ACS URL Source Select DHCP or URL to identify the source of the ACS
service
ACS URL Enter the server web address
ACS Username Enter the user name to access the ACS server
ACS Password Enter the password to access the ACS server
Enable Periodic Inform Select the check box next to Enable to enable the UE to
check periodically with the ACS server for new software
Periodic Inform Interval If you enabled the Enable Periodic Inform check box, input
how often (in seconds) the UE should check the ACS server
for new information. The range is 20 to 86,400 seconds.
Connection Request Enter the user name for the ACS to access the UE
Username
Connection Request Enter the password for the ACS to access the UE
Password
CloudKey Enter the CloudKey number. The CloudKey is related to the
plug-and-play aspect of the Baicells network. Newer
versions of UE firmware allow the UE to be picked up
automatically by the ACS server without having to configure
it. Once the UE is connected, given the CloudKey the UE will
be added to operator’s ACS account automatically. Refer to
Appendix D for more information concerning CloudKey.
NickName Optionally, you can enter a nickname for the ACS server
3.8.5 Date & Time

You can set the UE’s date and time manually or synchronize it with the network. The window
will display the UE’s current date (yyyy-mm-dd) and time (hh:mm:ss). If you select Set
Manually (Figure 3-44) in the Local Time field you can change the date and time in the same
format, or click on Sync to automatically fill in the current local time.
Below the Settings, the window displays the Daylight Saving Time (DST) fields. If you enable
DST, the UE adjusts the system time for DST based on the start and end dates that you enter.
The DST window also displays the status of DST as either running or not running.
If you select Sync from Network (Figure 3-45), the UE regularly synchronizes the time with a
Network Time Protocol (NTP) server. Identify at least 2 NTP servers, and optionally a third
backup server. Enter the NTP information as explained in Table 3-21.
After entering the date and time information, click on Submit to save the data.
93
Figure 3-44: Date & Time - Set Manually
Figure 3-45: Date & Time - Sync from Network
94
Table 3-21: Date & Time – Sync from Network Settings

Primary NTP Server From the drop-down list, select the primary Network Time
Protocol (NTP) server that the UE will use
Secondary NTP Server From the drop-down list, select the secondary (backup)
Network Time Protocol (NTP) server that the UE will use
Optional NTP Server Optional: If a third backup Network Time Protocol (NTP)
server will be used, enter its IP address
Time Zone From the drop-down list, select the correct time zone for
this UE
3.8.6 DDNS
A Dynamic Domain Name Server (DDNS) is used to map a user’s dynamic IP address to a fixed
DNS service. Select the check box next to Enable to enable the DDNS service, as shown in
Figure 3-46. The fields are described in Table 3-22. After entering the information, click on
Submit to save the data.
Figure 3-46: DDNS Settings
Table 3-22: DDNS Settings

Service Provider Select oray.com or DynDNS.org as the Dynamic Domain
Name Server
Domain Enter the DNS server web address
Username Enter the user name to access the fixed DNS
Password Enter the password to access the fixed DNS
95
3.8.7 Iperf
Many operators use an open-source, cross-platform tool referred to as Iperf to measure and
tune network performance. The tool can measure the throughput of Transmission Control
Protocol (TCP) and User Datagram Protocol (UDP) packets in both directions.
In this sub-menu, you identify the server address and configure settings for the Iperf tool. Once
Iperf is set up, the resulting data for this UE is reported at the bottom of the screen. To run the
Iperf tool, after entering the settings click on Start. Refer to Figure 3-47 and Table 3-23.
Figure 3-47: Iperf Settings
Table 3-23: Iperf Settings and Results

Settings
Server Address Enter the IP address of the server running the Iperf tool
Server Port Enter the port number of the server running the Iperf tool.
Range is 1024 to 65,535. Default is 5001.
Management Port Enter the management port number of the server running
the Iperf tool. Range is 1024 to 65,535. Default is 5001.
Measurement 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.
Protocol Type Select the data protocol type, either TCP or UDP
96
Result
Status -
Uplink Speed Data throughput on the uplink (UE to eNB)
Downlink Speed Data throughput on the downlink (eNB to UE)
3.8.8 Diagnostics
The UE GUI offers 2 diagnostic tests that can be useful for troubleshooting issues with internet
connectivity: Ping and TraceRoute. Run the ping test to send a data packet of a specified size
to a target IP address or domain field to determine network speed. Run a traceroute test to
display the route a packet takes to a target IP address or domain field. The route may indicate
causes of delay in transmission.
Once you enter the ping or traceroute information, click on Ping or Traceroute, respectively,
to run the test. Each time you run a ping or traceroute, the results are displayed at the bottom
of the window. Refer to Figures 3-48 and 3-49. Table 3-24 describes each field.
Figure 3-48: Diagnostics – Ping
97
Figure 3-49: Diagnostics – TraceRoute
Table 3-24: Diagnostics – Ping and TraceRoute Fields

Ping Settings
Target IP/Domain Enter the target IP or domain address
Packet 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 to run, in seconds.
Range is 1-10. Default is 10 seconds.
Count Enter the number of times you want the ping test to try
sending the data packet. Range is 1-10. Default is 4 times.
Ping Results
Result Displays the result of the ping test as successful or failed
Details Displays the details of the ping test, showing the target IP
address or domain field, the number of data bytes sent,
number of packets transmitted, number of packets
received, and percentage of packets lost
98
TraceRoute Settings
Target IP/Domain Enter the target IP or domain address
Maximum Hops 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.
Timeout Enter the length of time for the traceroute test to run, in
seconds. Range is 1-10. Default is 10 seconds.
TraceRoute Results
Result Displays the result of the traceroute test as successful or
failed
Details Displays the details of the traceroute test, showing the
target IP or domain address, the maximum number of hops,
and the packet size
3.8.9 Port Mirror

The Port Mirror function enables you to monitor and analyze the data flow of a network
interface, in this case one of up to four eNBs. Select the check box next to Enable to enable
port mirror for the specified device. Refer to Figure 3-50 and Table 3-25. After entering the
information, click on Submit to save the data.
Figure 3-50: Port Mirror Settings
Table 3-25: Port Mirror Settings

WAN Interface Select Access Point Name (APN): APN1, APN2, APN3, or
APN4
Forward IP Address Enter the IP address of the device on the LAN where you
want the eNB port data to forward
99
3.8.10 SysLog
The UE can capture system logs (SysLog), which provide information about local or network
events. A syslog in general indicates where the event originated in the system and the
priority level. System logs are often useful when examining UE and network performance,
and to troubleshoot issues. You can select either Network or Local syslogs, which are
described in each section below.
3.8.10.1 Network
To forward network logs to a specified device such as a logging or syslog server, you will first
select the level of syslog you wish to forward and then enter the server’s IP address. Refer to
Figure 3-51 and Table 3-26. Click on Submit to save the configuration.
Figure 3-51: Network SysLog Settings
Table 3-26: Network SysLog Settings

Method Select Network or Local
Level Select the level of syslogs you want to forward to a logging
server, either Emergency, Alert, Critical, Error, Warning,
Notice, Info, or Debug
Forward IP Address If you selected Network, enter the IP address of the logging
server to which network syslogs of the level specified will
be forwarded
3.8.10.2 Local
For local logs you can specify different levels of system logs to capture and then search those
logs based on a keyword. For example, if you were looking for system events related to MAC
Filtering, you could search on a specific MAC address.
100
After you set the level of local syslog to capture, click on Submit. To search the local syslogs,
type in a keyword to search on and then click on Pull. Any results based on that keyword will
be displayed. Refer to Figure 3-52 and Table 3-27.
Figure 3-52: Local SysLog Settings
Table 3-27: Local SysLog Settings

Method Select Local
Level Select the level of syslogs you want to forward to a logging
server, either Emergency, Alert, Critical, Error, Warning,
Notice, Info, or Debug
Keyword Type in a keyword to search on in the local syslogs of the
level specified
Pull Syslog After entering a keyword, select the Pull button to pull any
local syslogs with the keyword
Result Local syslogs that were pulled and include the keyword will
be listed here
3.8.11 Ping Watchdog

The Ping Watchdog utility will ping a predefined IP address to continuously monitor the
connection status. In the case of a UE, the remote IP address is typically an eNB. If the
remote IP address does not respond to the ping, the UE will reboot.
101
Caution: The reboot action will disrupt UE service.
To enable the ping watchdog, select the check box next to Enable. The other fields in the
sub-menu will become configurable, as shown in Figure 3-53 and described in Table 3-28.
Click on Submit to save the configuration.
Figure 3-53: Ping Watchdog Settings
Table 3-28: Ping Watchdog Settings

Ping Watchdog Select the check box next to Enable to enable ping
watchdog
IP Address to Ping Enter the IP address of the target device to ping
Ping Timeout (Seconds) Enter the number of seconds before the ping times out.
Range is 1-65,535 seconds. Default is 30 seconds.
Ping Count Enter the number of ping attempts to try. Range is 1-
65,535. Default is 10.
Failure Count to Reboot Enter the number of times the ping must fail before the UE
is rebooted. Range is 1-65,535. Default is 3.
3.8.12 Simcard Checking

You can enable Simcard Checking if you want the UE to verify that the SIM card is correctly
installed in the UE. When it is correctly installed, the result will say USIM Ready under the
Network > PIN Management window. If you enable or disable the Simcard Checking function
(Figure 3-54), click on Submit to save the change.
102
Figure 3-54: Simcard Checking
3.8.13 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-55 and
Table 3-29. After entering the information, click on Submit to save the data.
Figure 3-55: WEB Setting Fields
Table 3-29: WEB Settings

HTTP Enable Select the check box next to Enable to log in to an HTTP
Web address
HTTP Port Enter the HTTP port number to be used. Range is 80 to
65,535. Default is port 80.
HTTPs Enable Select the check box next to Enable to log in to an HTTPs
Web address
103
Allow HTTPs Login from Select the check box next to Enable to log in to an HTTPs
WAN Web address from the WAN
Refresh Time Enter how often (in seconds) that you want the UE
information that is viewed from the Web to be refreshed.
Range is 5-60 seconds. Default is 10 seconds.
Session Timeout Enter the amount of time (in minutes) of inactivity in the
UE GUI before the session times out. Range is 5-1440
minutes. Default is 10 minutes.
Language Select either Chinese or English language for the UE GUI
3.8.14 Account
The Account sub-menu may be used to change the user’s or the administrative login
password, and to enable the user. The new password or user enablement will take effect
after you click on Submit. Refer to Figure 3-56 and Table 3-30.
Figure 3-56: Account Settings
Table 3-30: Account Settings

Change Password
Username Select either admin or user
Current Password Enter the admin’s or user’s current password
New Password Enter the admin’s or user’s new password
Confirm Password Enter the admin’s or user’s new password again to confirm
the correct change has been made
Settings
Enable User Select the check box next to Enable to enable the UE user
104
3.8.15 Logout
To log out of the UE GUI, select the Logout sub-menu item. The system returns you to the
login page, as illustrated in Figure 3-57.
Figure 3-57: Logout Action
105
4. CloudCore
4.1.1 Server
If you are planning to use a local version of the CloudCore Operations Management Console
(OMC), refer to Table 4-1 for the minimum server requirements.
Table 4-1: Server Requirements
Item Description
CPU 2.0 GHz 8M cache, 2 Core CPU (Xeon E5 series)
Memory 16 GB
Disk 4T
NIC Gigabit Ethernet x 2
Operating System CentOS 7.0 @64bit
4.1.2 Client
Table 4-2 describes the minimum requirements for the client computer that you use to access
the CloudCore OMC and Business Operations Support System (BOSS) applications.
NOTE: Client computer requirements for the Evolved Packet Core (EPC) module are
different. Those requirements are provided in the Baicells EPC User Guide.
Table 4-2: Client Requirements

Item Description
CPU Higher than Intel Core 1GHz
Memory Greater than 2G RAM
Disk No less than 100 MB space available
Screen Resolution At least 1024 x 768 pixels
Browser Google Chrome 47 or higher (recommended)
Mozilla Firefox 47 or higher
106
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 set up a CloudCore account. Only one 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
Overview of CloudCore Users.
1. Open a web browser, and enter the CloudCore address:

https://cloudcore.cloudapp.net/cloudcore/
2. Click on the Sign up button (Figure 4-1).
3. Complete the mandatory fields, and again click on Sign up.
4. 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 a password to
authenticate. You are now ready to start using CloudCore!
Figure 4-1: CloudCore Sign up and Login Page
Refer, also, to the Getting Started BaiTip on the Baicells website:

https://na.baicells.com/getting-started/
4.2.2 Overview of CloudCore Users

When the operator’s primary administrator opens a CloudCore account, as a CloudCore user
they are placed in the default user groups for the OMC and for the BOSS (Figure 4-2). The
default OMC user group is called Default Management Role. The default BOSS user group is
called BOSS Carrier Admin group.
107
The primary administrator can then add:
• New OMC user groups and users.
• Other BOSS users, who are associated with the existing BOSS Carrier Oper (for
operator) user group.
OMC user groups are helpful when you want to set up different login rules for different
administrative users. How to create user groups is covered in section 4.4.5.2.
Figure 4-2: CloudCore Users
4.2.3 Navigation
After logging in, the CloudCore Web page shows the main modules across the top bar:
CloudCore system, OMC, and BOSS, as shown in Figure 4-3.
Figure 4-3: CloudCore Web Page
Click on CloudCore, and use the arrow icon to toggle the left navigation pane open or closed
in any of the modules (Figure 4-4).
Figure 4-4: CloudCore Navigation Pane
108
In the upper right corner, you will see “Welcome, <your name>”. Select the down arrow next
to welcome to view a drop-down menu of general functions (Figure 4-5).
Figure 4-5: CloudCore Welcome Menu
Select Change password to enter a new password for your account (Figure 4-6). The password
may be 6 to 16 characters.
Figure 4-6: Change Password
Choose the Lock screen menu item if you wish to lock your computer screen (Figure 4-7).
Choose Logout to log out of the system.
Figure 4-7: Lock Screen
109
4.2.4 Online Help
The online help menus in OMC and BOSS offer the ability to download this guide (forthcoming),
and provide an About description of the software version (Figure 4-8).
Figure 4-8: OMC Help > About
4.3 System
4.3.1 Operator Info

After you log in to CloudCore, you will see the CloudCore System page. Expand the System
menu, as shown in Figure 4-9. Select Operator Info to see the operator name, CloudKey, and
administrator information. Notice the Edit button at the bottom, which allows you to change
all but the Operator Name and CloudKey fields.
Figure 4-9: CloudCore > System
110
4.3.2 Users
Under System > Users, any users already defined in the system will be listed in the User
Management window on the right (Figure 4-10). Scroll to the right to see all of the information.
Figure 4-10: User Management
To search for a specific user(s) already defined in the system, enter the user name or sort the
list by status or user group, and then select Query (Figure 4-11).
Figure 4-11: Search for User
When you find the user you are looking for, if you need to modify the information you can
highlight the row with the user information and click on the pen icon under Operation (Figure
4-12). After entering any changes, select OK to save the data.
Figure 4-12: Modify User
The other functions under Operation allow you to lock/unlock the user’s password, and to
delete the user. Refer to Figure 4-13.
111
Figure 4-13: Lock/Unlock User Password or Delete User
From this window you also can add users to existing user groups. (How to create user groups
is explained in section 4.4.5.2.)
To add a user, in the User Management window click on the + (add) sign in the upper right-
hand corner. A new dialogue window will open (Figure 4-14). Complete the mandatory user
information, any optional information fields, and then click on OK to save the configuration.
Note that the password may include A-Z, a-z, 0-9, dash (-), and underscore (_).
Figure 4-14: Add User
4.3.3 Reset Password

Under System > Reset Password you can reset a user’s password (Figure 4-15). You can either
select the row with the user’s account and click on the Reset Password button; or, you can
enter the user’s name in the User Name field and click on Query to locate the user’s account
and then click on the Reset Password button. When finished entering the change, click on OK.
112
Figure 4-15: Reset Password
4.3.4 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-16). 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-16: Operation Logs
4.3.5 Security Rule

Selecting System > Security Rule allows you to enable or disable the rule. To enable the
security rule, slide the toggle to the right, as shown in Figure 4-17. When enabled, only those
users with IP addresses in the specified range are allowed to log in to CloudCore. Enter the
start and end IP addresses in the allowable range, and then click on Save to save the entries.
113
Figure 4-17: Security Rule
4.4 OMC
When you click on the OMC tab, you will see a Figure 4-18: OMC Menu
new menu in the left navigation pane (Figure 4-18).
Each OMC menu item is explained in this section.
Also, refer to the Getting Started BaiTip on the

Baicells website:
https://na.baicells.com/getting-started/
114
4.4.1 Dashboard
The OMC dashboard appears on the right side window as you enter the OMC module (Figure
4-19). The dashboard provides operator personnel with a summary of network status,
statistics, and performance. This at-a-glance feature helps administrators to grasp the health
of the network overall and to quickly identify any issues.
Figure 4-19: Dashboard
4.4.1.1 Individual eNBs and UEs

The term, eNB, stands for eNodeB, which is a Long-Term Evolution (LTE) technology term.
Other terms such as base station, base transceiver station, and cell site may be used to denote
the eNB. The eNB is basically the network cell site to which the subscriber’s equipment
connects to reach the internet. There may be more than one eNB in a cell site.
The term, UE, stands for user equipment and refers to the subscriber or the device that the
subscriber is using. Another term sometimes used for UE is Customer Premise Equipment
(CPE). For simplicity, in most cases in this document the terms “eNB” and “UE” are used.
The eNB and UE sections of the dashboard contain a search bar so you can look up and check
the status of individual eNBs and UEs. All eNBs in the operator’s network are listed under eNB.
All UEs in the operator’s network are listed under CPE. Clicking on an eNB name or UE name
in either block will take you into the eNB Monitor page or CPE Monitor page, respectively. The
monitor functions are explained later in this document.
115
4.4.1.2 Alarms
The top, right window displays the number of active system 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.
If you click on the double arrows icon in the upper right corner of this block (Figure 4-20), it
will take you into the Alarm Query menu and shows a list of active alarms. In the list of alarms,
you can also right-click on a specific alarm to bring up further details about that alarm, such as
suggestions for how to resolve it (Figure 4-21). The alarms are discussed in more detail later in
this document.
Figure 4-20: Alarms
116
Figure 4-21: Alarm Details
You can also select Alarm Confirm, which lets other OMC administrators know you have seen
an alarm reported and are working on it or resolving it. If you select Clear Alarm it will remove
the alarm from the active list and add it to the historical alarms list. The windows resulting
from these two actions are shown in Figure 4-22.
Figure 4-22: Confirm or Clear Alarm
Another function related to alarms in the dashboard is the ability to export the alarm details.
Click on the export icon in the upper right of the dashboard window, as shown in Figure 4-23.
You can then select the destination where you want to save the file.
117
Figure 4-23: Export
4.4.1.3 Statistics
The statistics block of the dashboard presents three sets of data: eNB Online, eNB Active, and
CPE Connect (Figure 4-24). The first statistic, eNB Online, shows the total number of eNBs that
are currently online – that is, operational and connected to the network - and the number that
are offline.
The second statistic, eNB Active, shows the total number of eNBs that are actively in service –
that is, receiving or transmitting data – and the number that are inactive. The third block, CPE
Connect, shows the total number of UEs connected to the network as well as the number of
UEs that are disconnected.
Figure 4-24: Statistics
Click on any of the statistics to bring up more detail. When you click on eNB Online, it will take
you into the eNB > Monitor page and show you eNB online statistics (Figure 4-25).
118
Figure 4-25: eNB Online Details
When you click on the eNB Active statistic, it will take you to eNB > Monitor and show you eNB
active statistics. See Figures 4-26 and 4-27.
Figure 4-26: eNB Active Details (1 of 2)
119
Figure 4-27: eNB Active Details (2 of 2)
When you click on CPE Connect statistic, it will take you to the CPE Monitor page and show
you the UE connect statistics. See Figures 4-28 and 4-29.
Figure 4-28: CPE Connect Details (1 of 2)
120
Figure 4-29: CPE Connect Details (2 of 2)
All of the eNB Monitor and CPE Monitor fields are explained later in this document.
4.4.1.4 Performance
The dashboard Performance block offers 3 types of network performance data: Throughput,
Physical Resource Block (PRB) Utilization, and UE Count. Hover your cursor over any of the
graphs to see more detailed data for that graph (Figure 4-30).
Figure 4-30: Performance
The Throughput is a measure of the average uplink and downlink data traffic being transmitted
over the last 5 minutes across all eNBs in the network. The PRB Utilization shows the average
number of subcarriers allocated to users across all eNBs over the last 5 minutes, an indicator
of system utilization. The UE Count shows the total number of connected users at that point
in time. Notice that you can slide the x-axis left and right to see data for different times of day.
121
4.4.2 eNB
The eNB menu includes 3 sub-menus: Monitor, Strategy (Upgrade and Reboot), and File Library
(Figure 4-31). Each of these functions is explained in this section.
Figure 4-31: eNB Menu
4.4.2.1 Monitor
4.4.2.1.1 Monitor Window
The first sub-menu you can select under eNB is Monitor. The monitor function allows you to
see any eNBs that are already defined in the system. See Figures 4-32 and 4-33, showing the
fields as you scroll left to right. The fields are explained in Table 4-3.
You can review the eNB list, or you can enter a specific serial number or cell name and click on
Filter to look it up. Clicking on the Refresh button will update the information on the page. If
you click on History, the system will display historical information about the eNB. The other
fields that are shown on the monitor page will be explained under System > Device
Management, which is where you add and configure eNB and UE devices.
Figure 4-32: eNB > Monitor (1 of 2)
122
Figure 4-33: eNB > Monitor (2 of 2)
Table 4-3: eNB Monitor Fields

Serial Number eNB serial number
Cell Name Name of the cell site (in System > Device Management)
where the eNB is located
IP Address IP address of the eNB
MAC Address MAC address of the eNB
Cell ID Logical Cell ID to which this eNB is assigned
PCI Physical Cell Identifier, 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 responsible for initiating
paging and authentication of mobile devices is active or
inactive
KPI Report Status Key Performance Indicators 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
123
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
Product Type The eNB description used in OMC
Hardware Version The version of hardware for this device
Software Version Software code level running on the device
Device Group The device group to which this device has been configured
UBoot Version Universal boot loader code level, information sometimes
needed when troubleshooting issues
Kernel Version Kernel code level, information sometimes needed when
troubleshooting issues
Looking again at Figure 4-32, notice in the upper right side of the window are 4 color blocks
with numerals that represent alarm counts. Alarms are an indication of an error or problem
regarding eNB operation. The 4 colors represent 4 classes of alarm priorities - Critical, Major,
Minor, and Warning – and the numerals are the number of active alarms in that class. Alarms
are explained in section 4.4.4 of this document.
You can show, hide, or rearrange most of the columns in the Monitor window when you click
on the Display button (Figure 4-34). Two columns, Operation and Serial Number, may not be
changed. After making any other display changes, select OK to save the changes.
Figure 4-34: Display
124
If you click on Filter you can customize the Monitor information further by selecting additional
display criteria (Figure 4-35). Each time you change the filter criteria, the Monitor display
changes automatically. Simply click on the X in the upper right corner of the Filter dialogue box
to exit the filter selection function.
Figure 4-35: Filter
4.4.2.1.2 Right-Click Actions

When you right-click on any eNB listed in the Monitor window, you will get a drop-down menu
that allows you to select Information, Synchronize, Settings, Reboot, Logs, or CPEs (Figure 4-
36). Each of these functions is explained in this section.
Figure 4-36: Right-Click Actions
125
4.4.2.1.2.1 Information
By right-clicking on an eNB listed in the Monitor window and selecting Information, the
Information pop-up window displays 4 tabs of information: Statistics, Alarm, Performance, and
Logs.
The Statistics tab provides the eNB’s Serial Number, MAC Address, UBoot Version, IP Address,
Software Version, and Kernel Version (Figure 4-37). The graph on the bottom of this window
presents the eNB’s active status vs inactive status across time.
Figure 4-37: Right-Click > Information > Statistics
When you select the Alarm tab, the window displays all alarms associated with this eNB
(Figure 4-38). The list of alarms identifies the alarm number, probable cause, status, event
time, and the last update time. For any alarm in the list, you can right-click to get more
details, or confirm or clear the alarm.
126
Figure 4-38: Right-Click > Information > Alarm
When you select the Performance tab, the window displays 6 key performance indicator
(KPI) graphs:
• KPI1: UL/DL Throughput (Figure 4-39) – A graph showing the uplink (red) and
downlink (black) data throughput rates for this eNB over the past “x” number of
hours per the date shown in the date field
• KPI2: UL/DL Utilization (Figure 4-40) – A graph showing the percentage of available
resource blocks used on the uplink (red) and downlink (black) during the past “x”
number of hours per the date shown in the date field
• KPI3: E-RAB* EstablishSuccessRate (Figure 4-41) – A graph showing the percentage
of time the eNB could be accessed successfully by subscribers attempting to connect
to the network.
• KPI4: E-RAB* EstablishFailRate (Figure 4-42) – A graph showing the percentage of
time the eNB could not be accessed successfully by subscribers attempting to
connect to the network
• KPI5: SuccInterEnbS1Rate (Figure 4-43) – A graph showing the percentage of
successful handoffs from this eNB to other eNBs
• KPI6: RRC EstablishDropRate (Figure 4-44) – A graph showing the percentage of
dropped sessions after the sessions had been established
*E-RAB is an LTE term that stands for E-UTRAN Radio Access Bearer.
Notice the 2 fields above the graphs, one called Time Granularity and one showing the date
(yyyy-mm-dd). You cannot change the time granularity as of this release; however, you can
change the date to go backward or forward in order to examine the eNB performance over
several days.
127
Figure 4-39: Right-Click > Information > Performance > KPI1: UL/DL Throughput
Figure 4-40: Right-Click > Information > Performance > KPI2: UL/DL Utilization
Figure 4-41: Right-Click > Information > Performance > KPI3: E-RAB EstablishSuccessRate
128
Figure 4-42: Right-Click > Information > Performance > KPI4: E-RAB EstablishFailRate
Figure 4-43: Right-Click > Information > Performance > KPI5: SuccInterEnbS1Rate
Figure 4-44: Right-Click > Information > Performance > KPI6: KPI6: RRC EstablishDropRate
129
When you select the Logs tab, you can view the device report log (Figure 4-45) and the
device exception log (Figure 4-46).
Figure 4-45: Right-Click > Information > Logs > Device Report Log
Figure 4-46: Right-Click > Information > Logs > Device Exception Log
4.4.2.1.2.2 Synchronize
When you right-click on an eNB listed in the Monitor window and select Synchronize, the OMC
refreshes the eNB status.
4.4.2.1.2.3 Settings
Right-click on an eNB in the Monitor list, and select Settings to bring up a configuration
window (Figure 4-47). You can configure any device that has been added under System >
Device Management using the Settings selection. The fields under each tab in Settings are
explained in this section.
130
Figure 4-47: Right-Click > Settings > Wireless tab
4.4.2.1.2.3.1 Wireless tab

The Monitor > (selected eNB) > right-click on Settings opens to the first tab, Wireless (shown
in Figure 4-47 above). Each wireless field is described in Table 4-4. The pull-down menu options
are shown in Figure 4-48 for PB, Figure 4-49 for Bandwidth, Figure 4-50 for SfAssignment, and
Figure 4-451 for Special SfPatterns. Click on OK to save the configuration.
Table 4-4: Wireless Settings

Cell ID Cell ID allocated by the operator. Range 0-268435455
Cell Name Cell name allocated by the operator
MME IP address of the cell’s associated Mobility Management
Entity (MME) in the core network.
PLMN Enter the numerical identifier for the operator’s Public Land
Mobile Network (PLMN) for this cell
PCI Physical Cell Identification (PCI). Used to transmit data over
the cell. The range is 0-503. There is a maximum of 504
physical cell IDs. In a large network, the operator might have
to repeat physical cell IDs to cover all of the cell sites. Two
131
cells that share the same physical cell ID cannot be
geographically close to each other or they will interfere will
each other.
TAC Tracking Area Code (TAC) where the eNB is located. The TAC
is used to determine the range of the paging information.
The operator can use a number between 1 - 65,000. Default
is 1.
Band Indicator The eNB’s operating frequency band (hardware-specific)
Frequency (MHz) Select the eNB’s currently approved operating frequency
points (hardware-specific)
PB The index number which represents the difference of the RE
power between the symbol with RS and without RS. The
options are 0, 1, 2, or 3, which corresponds to the Physical
Random Access Channel (PRACH) configuration index
number to be used. Refer to Figure 4-39.
Bandwidth Determines the number of resource blocks (RB) to be used
in the frequency domain (in MHz) or the time domain (in
milliseconds).
Options given are: CELL_BW_N6 (1.4 MHz), CELL_BW_N15 (3

MHz), CELL_BW_N25 (5 MHz), CELL_BW_N50 (10 MHz),
CELL_BW_N75 (15 MHz), CELL_BW_N100 (20 MHz).
Only CELL_BW_N25 (5 MHz), CELL_BW_N50 (10 MHz), and

CELL_BW_N100 (20 MHz) are supported at this time.
Sf Assignment In TDD transmissions, the subframe assignment determines
the downlink to uplink transmission ratio.
Options given are: SA0, SA1, SA2, SA3, SA4, SA5, SA6, where
0-6 represents an LTE configuration index number that
determines how often the eNB will switch, per subframe,
between uplink and downlink.
Only SA1 and SA2 are supported at this time. Refer to Figure
4-41. Also, refer to the BaiTip on this setting:
december-14th-2016-subframes-and-special-subframes/163
Special Sf Patterns Special subframe (Sf) pattern - determines the guard time
between switching from uplink to downlink and from
downlink to uplink.
Options are SSP0 through SSP8.
Only SSP5 and SSP7 are supported at this time.
132
Figure 4-48: Wireless Settings > PB Options
Figure 4-49: Wireless Settings > Bandwidth Options
Figure 4-50: Wireless Settings > SfAssignment Options
133
Figure 4-51: Wireless Settings > Special Sf Patterns Options
4.4.2.1.2.3.2 Network tab

Under Settings, the second tab is Network (Figure 4-52). In the Protocol field, select the
network interface type. Select either static or DHCP, which stands for Dynamic Host Control
Protocol. Click on OK to save the configuration.
Figure 4-52: Network Settings
134
4.4.2.1.2.3.3 ICIC tab
Under Settings, the third tab is for Inter-Cell Interference Coordination (ICIC) (Figure 4-53). ICIC
is a type of interference mitigation. When enabled, ICIC applies restrictions to the radio
resource management (RRM) block, improving channel conditions across subscribers who may
be severely impacted by interference. ICIC thus enables higher spectral efficiency.
Figure 4-53: ICIC
4.4.2.1.2.3.4 NTP tab

Under Settings, the fourth tab is NTP Settings (Figure 4-54). The network time protocol (NTP)
configuration fields are explained in Table 4-5. Click on OK to save the configuration.
Figure 4-54: NTP Settings
135
Table 4-5: NTP Settings

NTP Sync Time(s) Network Time Protocol (NTP) time interval for
synchronization between the eNB and the primary NTP
server, in seconds. Range 10-65535. Default is 21,600
seconds.
NTP Server 1 Primary NTP server IP address
NTP Port 1 Primary NTP server port number
NTP Server 2 Optional: Secondary NTP server IP address
NTP Port 2 Optional: Secondary NTP server port number
NTP Server 3 Optional: Tertiary NTP server IP address
NTP Port 3 Optional: Tertiary NTP server port number
NTP Server 4 Optional: Quaternary NTP server IP address
NTP Port 4 Optional: Quaternary NTP server port number
4.4.2.1.2.4 Reboot
When you right-click on an eNB listed under eNB Monitor, if you select the Reboot option it
will ask if you are sure you want to take that action (Figure 4-55), as it will interrupt current
service to UEs. If you select OK, it will automatically reboot that eNB.
NOTE: If you need to reboot the eNB, we recommend that you collect logs on the
eNB before you reboot it. That data may be needed for troubleshooting.
Figure 4-55: Reboot
4.4.2.1.2.5 Logs
When you right-click on an eNB listed under eNB Monitor, if you select the Logs option you
will get a pop-up window asking if you want to collect logs for this eNB (Figure 4-56). If you do,
click on OK.
136
Figure 4-56: Logs
4.4.2.1.2.6 CPEs
When you right-click on an eNB listed under eNB Monitor, if you select the CPEs option it brings
up the list of UEs connected to that eNB (Figure 4-57). For each UE you will see the serial
number, name, Media Access Control (MAC) address, and International Mobile Subscriber
Identity (IMSI) number.
Figure 4-57: CPEs
4.4.2.2 Strategy
The Strategy sub-menu under eNB (Figure 4-58) refers to software version control and how
you manage the eNB software code level. Baicells continually invests in software features and
functionality. Each version of code typically has new features, enhancements, or bug fixes;
therefore, in most cases you should keep the Baicells equipment at the highest available code
level. As of OMC version 3.2.2, you can also define a change task that will update the frequency
and Physical Cell Identifiers (PCI) for the UEs associated with up to 10 eNBs.
137
Figure 4-58: Strategy
Baicells notifies operators of newer software files via the OMC GUI, as well as through social
media and the Baicells website. Different versions of code are made available by Baicells
through the OMC portal under the eNB sub-menu called File Library.
Using the eNB > Strategy functions, you can define different software upgrade or rollback tasks,
e.g., one task per code level or per set of eNBs, and save the tasks in a task list. By defining
each code version or set of eNBs as a task, you can execute the task repeatedly as needed
across the network.
4.4.2.2.1 Upgrades and Rollbacks

When you upgrade an eNB’s software, you are replacing the existing software files with newer
software files. To define a software upgrade task, click on eNB > Strategy > Upgrade, which
opens an Upgrade Task window.
To define a new upgrade task, select + (add) in the upper right corner of the Upgrade Task
window. This will open a New Upgrade Task dialogue window (Figure 4-59).
138
Figure 4-59: New Upgrade Task
Enter a task name, and in the left eNBs pane search for the eNBs to be upgraded. Click on the
right arrow to “move” the eNBs into the Selected pane. Under Execute Type, you can
upgrade the selected eNBs immediately or schedule a time for the upgrade to occur. Once an
upgrade is scheduled, you can select Suspend if you need to suspend the upgrade activity. If
you wish to retain the new upgrade task you have defined, in the Retain Configuration field,
select “Yes”. Click on Next to select the correct software file to be used to upgrade the selected
eNBs (Figure 4-60).
Figure 4-60: Select Upgrade File
139
Once selected, when you click on Finish the OMC window presents the Task Results window
to display the status of the upgrade task (Figure 4-61). A software upgrade (or rollback) will
reboot the eNB automatically.
Due to the reboot action, most operators choose less busy network time periods to perform
software upgrade/rollback actions.
Figure 4-61: Task Results
If you need to downgrade the eNB software to a prior release of software code, in the Upgrade
Task window select Software Rollback from the Upgrade Task > Upgrade Type drop-down
menu (refer to Figures 4-59 and 4-60 previously shown). The procedure is the same as an
upgrade, except this time you would select the older version of code file. Sometimes, rolling
back to the previous release of code may be necessary when troubleshooting issues or to
restore equipment to a known, stable load.
Once an upgrade or rollback task is defined, you can use the fields under Operation to view,
make active/deactive, terminate, or delete a task (Figure 4-62). The difference between
terminate and delete is terminate will stop the task from occurring or progressing, whereas
delete will remove the task altogether from the task list.
Figure 4-62: Operation
140
4.4.2.2.2 Reboot
The eNB > Strategy > Reboot action (Figure 4-63) allows you to reboot the eNB. A software
reboot may be necessary sometimes to resolve operational issues. Since the reboot action
causes service disruption, most operators choose a window of time when there are fewer or
no users on the system to execute a reboot.
NOTE: If you need to reboot the eNB, we recommend that you collect logs on the
eNB before you reboot it. That data may be needed for troubleshooting.
Figure 4-63: Reboot
To perform or schedule a reboot, use the same method as a software upgrade. Click on + (add)
to create a reboot task (Figure 4-64).
Figure 4-64: Create Reboot Task
Enter a task name, and in the left eNBs pane search for the eNB to reboot. Click on the right
arrow to “move” the eNB into the Selected pane. Under Execute Type, you can reboot
the selected eNB immediately or schedule a time for the reboot to occur. Once a reboot is
scheduled, you can select Suspend if you need to suspend the reboot activity.
141
Click on Next. You will receive a warning that the reboot action will disrupt eNB service, and it
will ask if you are sure you want to reboot it (Figure 4-65). Press OK to proceed. Once you
select OK, the window will display the Task Results in the same way it does for upgrade tasks
(refer to Figure 4-61 above).
Figure 4-65: Reboot Task Warning
As was true for upgrade and rollback tasks, once a reboot task is defined you can use the
options under Operation to view, activate, terminate, or delete a task (Figure 4-66).
4.4.2.2.3 Frequency & PCI

If you have a need to change the frequency or Physical Cell Identifier (PCI) of one or more eNBs,
rather than reconfiguring each UE attached to the eNB(s) you can use the Strategy ->
Frequency&PCI sub-menu (Figure 4-67) to define a New Frequency Lock Task and implement
the bulk-change.
142
Figure 4-67: Frequency & PCI
Looking at Figure 4-67, enter a task name for this task. At the bottom of the screen, you will
first you select the eNB(s) for which you want to change the frequency or PCI. To do this, select
the check box next to the eNB serial number.
Next, you can identify up to 10 UEs that are served by the eNB(s) to auto-change the PCI
locking configuration. To do this, enter the new frequency and new PCI information in their
respective fields, and slide the Modify the binding CPE button to the right (the slider will turn
green). You will do this for each UE.
Under Executed mode, select either Immediately or Schedule Time for the change to be
executed.
Caution: The selected eNBs will be restarted according to the

execution plan, and the eNBs will stop serving UEs during the restart.
Any UEs that are offline during the execution of the 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
associated to the eNB(s) are updated.
4.4.2.3 File Library

The file library is a list of eNB software upgrade files per code release from Baicells (Figure 4-
68). Each file shows the file name, product type (e.g., eNB), file size, version number, the
upload date and time, and a description. It is from the file library that the New Upgrade Task >
Select Upgrade File list is generated during an upgrade or rollback.
143
Figure 4-68: File Library
4.4.3 CPE
When you expand the CPE menu in OMC, you will see 3 sub-menus: Monitor, Strategy, and File
Library. Refer to Figure 4-69. Each of these functions is explained in this section.
Figure 4-69: CPE Menu
4.4.3.1 Monitor
4.4.3.1.1 Monitor Window
The CPE > Monitor function presents status information about all UEs in the operator’s
network. You can enter a specific UE serial number, name, MAC address, or IMSI number, and
click on Search to find that UE and display its status. You can also export the data using the
arrow icon in the upper right section of the window.
The fields are shown in Figures 4-70 and 4-71, progressing from left to right using the scroll
bar. The fields are explained in Table 4-6.
144
Figure 4-70: CPE > Monitor (1 of 2)
Figure 4-71: CPE > Monitor (2 of 2)
Table 4-6: CPE > Monitor Fields

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
145
PCI The currently serving eNB’s Physical Cell Identifier, or Layer 1
identity, which uniquely identifies each cell site in the
wireless network
History See Figure 4-72.
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. (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. (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 the 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
146
per second (Mbps)
Uptime(h) Number of hours the UE has been powered on
Last Connection Time The last time the UE was connected to the OMC/CloudCore
Serial Number The UE unit’s serial number
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
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
If you click on the graph icon in the History column (Figure 4-72) for a particular UE, it will bring
up numerous fields of data about the UE’s performance. Scroll down to see all of the fields.
The meaning of the fields were explained above in Table 4-7, CPE > Monitor.
Figure 4-72: CPE History
147
4.4.3.1.2 Right-Click Actions
When you right-click on any UE listed in the Monitor window, you will get a drop-down menu
that allows you to select Information, Settings, Synchronize, Frequency Lock, or Reboot (Figure
4-73). Each of these items is explained in this section.
Figure 4-73: Right-Click Actions
4.4.3.1.2.1 Information
By right-clicking on a UE listed in the Monitor window and selecting Information, the
Information pop-up window displays the serial number, the International Mobile Subscriber
Identity (IMSI) number, the transmit (Tx) power, the Mobile Country Code (MCC), and the
Mobile Network Code (MNC) for the UE (Figure 4-74). Click on OK to exit the window.
Figure 4-74: Information
4.4.3.1.2.2 Settings
Right-click on a UE in the Monitor list, and select Settings to bring up a configuration window
(Figure 4-75). You can give the UE a name, and you can enable remote access to the UE by
checking the check box next to Https Login. Enabling this allows a technician to get into a user’s
Web GUI from the internet.
148
Figure 4-75: Settings
4.4.3.1.2.3 Synchronize
When you right-click on a UE in the Monitor list and select Synchronize, the OMC refreshes the
UE data that is displayed.
4.4.3.1.2.4 Frequency Lock
Right-clicking on a UE and then selecting Frequency Lock allows you to change the Scan Mode.
Current options are Full Band or PCI lock (Figure 4-76). Full band enables the UE to operate on
any frequency within the designated frequency band. PCI lock, referring to a cell’s Physical Cell
Identifier, specifies to which cell the UE must connect.
If you select PCI lock, the system will display the current E-UTRA Absolute Radio Frequency
Channel Number (EARFCN) and PCI to which the UE is connected, and then allow you to change
these parameters (Figure 4-76). Using PCI lock allows the operator to “force” a UE to connect
within a specific cell and use a specific channel number. This may be necessary to avoid the UE
from connecting to undesirable eNBs.
Figure 4-76: Frequency Lock
149
4.4.3.1.2.5 Reboot
To reboot a UE via the GUI, right-click on the UE in the Monitor window and select Reboot. A
software reboot is sometimes necessary when troubleshooting UE issues.
4.4.3.2 Strategy
The term “strategy” here refers to software version control and how you manage the UE
software code level. Baicells continually invests in software features and functionality. Each
version of code typically has new features, enhancements, or bug fixes; therefore, in most
cases you should keep the Baicells equipment at the highest available code level. The strategy
sub-menus are shown in Figure 4-77.
Figure 4-77: Strategy
Baicells notifies operators of newer software files via the OMC GUI, as well as through social
media and the Baicells website. Different versions of code are made available by Baicells
through the OMC portal under the CPE sub-menu called File Library.
Using the CPE > Strategy functions, you can define different software upgrade tasks, e.g., one
task per code level or per set of UEs, and save the tasks in a task list. By defining each code
version or set of UEs as a task, you can execute the task repeatedly as needed across the
network.
The steps for defining a CPE upgrade task follow the same format as described for eNBs in
section 4.4.2.2.1. To create a new upgrade task, click on the + Add icon and select an upgrade
type. The choices are ODU Software Upgrade (for outdoor UEs) or IDU Software Upgrade (for
indoor UEs). The New Upgrade Task dialogue window will open (Figure 4-78).
150
Figure 4-78: New Upgrade Task
Enter a task name, and in the left CPEs pane search for the UEs to be upgraded. Click on the
right arrow to “move” the UEs into the Selected pane. Under Execute Type, you can
upgrade the selected UEs immediately or schedule a time for the upgrade to occur. Once an
upgrade is scheduled, you can select Suspend if you need to suspend the upgrade activity. If
you wish to retain the new upgrade task you have defined, in the Retain Configuration field,
select “Yes”.
Click on Next to select the correct software file to be used to upgrade the selected UEs. Once
selected, when you click on Finish the OMC window presents the Task Results window to
display the status of the upgrade task. A software upgrade will reboot the UE automatically.
Due to the reboot action, most operators choose less busy network time periods to perform
software upgrade/rollback actions.
151
Once an upgrade task is defined, you can use the fields under Operation to view, make active,
terminate, or delete a task (Figure 4-79). The difference between terminate and delete is
terminate will stop the task from occurring or progressing, whereas delete will remove the
task altogether from the task list.
The reboot action for a UE is also the same procedure as for an eNB (refer to section 4.4.2.2.2
and see Figure 4-80 below).
Figure 4-80: Reboot
4.4.3.3 File Library

The file library is a list of UE software files per code release from Baicells (Figure 4-81). Each
file listed shows the file name, product type, file size, version number, upload time, and
description. It is from the file library that the New Upgrade Task > Select Upgrade File list is
generated during an upgrade or rollback.
152
Figure 4-81: File Library
4.4.4 Alarm
The next menu item in the OMC is the Alarm section (Figure 4-82). The purpose of the Alarm
function is to observe active (unresolved) warnings regarding eNB operation, as well as review
historical alarm messages, customize the display, and set up notification messages.
Figure 4-82: Alarm Menu
Alarms are categorized into 4 classes: Critical, Major, Minor, and Warning. The upper right part
of the screen shown in Figure 4-82 displays the number of system alarms present in each
category.
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.
153
4.4.4.1 Query
When you select Alarm > Query, the window on the right defaults to the list of active alarms.
Notice the search and export icons (Figure 4-83). Use the query (search) bar to enter the serial
number of a specific eNB, or use advanced query to find alarms based on severity, alarm
identifier, event type, probable cause, or event window of time (start and end). The advanced
search window is shown in Figure 4-84.
Figure 4-83: Active Alarms
Figure 4-84: Advanced Query
If you right-click on an alarm shown in the list, you will be given 3 options: Detail, Alarm
Confirm, and Clear Alarm (Figure 4-85).
154
Figure 4-85: Right-Click on an Alarm
Selecting Detail will display information about the specific alarm (Figure 4-86). The information
is explained in Table 4-7.
Figure 4-86: Alarm Detail
Table 4-7: Alarm Detail

Index System index number assigned to each alarm incident
Severity Severity of the alarm – critical, major, minor, or warning
155
Alarm Identifier Alarm number that identifies the type of alarm
Network Element Type Type of entity incurring the alarm, e.g., OMC, eNB, UE
Network Element Provides more detail about which device reported the alarm,
Positioning such as the eNB serial number or name
Event Type Alarm classification – either 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 administrator
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
Selecting Alarm Confirm acknowledges you have seen the alarm. Doing this lets other OMC
administrators know that the problem has been seen and is, hopefully, in the process of being
resolved. You can add a description or notes about the alarm. Click on Confirm to save the
information. Refer to Figure 4-87.
Figure 4-87: Alarm Confirm
156
To clear an alarm that has been resolved and remove it from the alarm list, right-click on the
alarm in the list and select Clear Alarm. You will be prompted to confirm you want to take this
action (Figure 4-88). If you select OK, the selected alarm will disappear immediately from the
active list.
Figure 4-88: Clear Alarm
Once cleared, an active alarm becomes an historical alarm. Looking at the History Alarm tab,
you have the same regular and advanced query capabilities as for Active Alarm. When you
right-click on a history alarm, you can still select Detail and Alarm Confirm, but notice two new
options: Restore alarm and Delete Alarm (Figure 4-89).
Figure 4-89: History Alarm
If you select Restore alarm, the system will immediately remove the alarm from the history list
and put the alarm in the active alarm list. If you want to remove the alarm permanently from
either list, when you right-click on the history alarm select Delete Alarm.
4.4.4.2 Settings
The alarm settings allow you to view and customize the display of a list of all alarms, with the
option to export the data to a file. It is in this section that you can also set up notifications for
alarm occurrences. These functions are explained in this section.
4.4.4.2.1 Library
Clicking on Alarm > Library displays a list of all alarms that have occurred in the system (Figure
4-90). Using the adaptive display feature, you can sort the list in ascending or descending order
by the alarm identifier or by severity level. To record or further manipulate usage of the data,
you can select the export icon to send the data to a file.
157
Figure 4-90: Library
4.4.4.2.2 Notification
The Alarm > Notice function allows you to set up automatic notification emails based on the
alarm severity level that you select. To enable this feature, slide the Enable bar to the right
(Figure 4-91). Enter the email address(es) to which the notification is to be sent; use a semi-
colon (;) to separate each email address. Notifications will be sent every 10 minutes to the
email addresses specified.
Next, choose the alarm severity level(s) for which you want to be notified by clicking on the
check box next to the alarm level. Click on the Save button to save the notifications
configuration.
Figure 4-91: Notification
158
4.4.5 System
The OMC System menu includes device management for both eNBs and UEs; user
management of individual users and user groups; and log management (Figure 4-92). It is
under these System functions that you can add eNBs and UEs to the network.
Optionally, you can create device groups for eNBs and UEs, or user groups for users, when
multiple devices or users share the same configuration settings or to simply make it easier to
manage multiple devices or users, e.g., based on location, service level, and so forth. Each
System sub-menu is explained in this section.
Figure 4-92: System Menu
4.4.5.1 Device Management

Selecting System > Device Management opens a window that shows a list of device groups on
the left and a list of individual eNBs on the right. You can switch between eNBs and UEs using
the tabs at the top. Refer to Figure 4-93.
Figure 4-93: Device Management
159
In the list of device groups, you can use the eye icon under Operation to see more information
about a specific group. An example is shown in Figure 4-94.
Figure 4-94: View Device Group Information
Use the pencil icon under Operation to modify a device group (Figure 4-95).
Figure 4-95: Modify Device Group
You can delete a device group using the trash can icon under Operation. The system will
prompt you to be sure before you delete the group. Taking this action will result in the users
assigned to that group being moved to the default group. Click on OK to continue the action.
160
Figure 4-96: Delete Device Group
In the list of eNBs or UEs, you have the option to delete a device by selecting the trash can
icon under Operation. The system will prompt you to be sure you want to continue the delete
action (Figure 4-97). If you do, select OK.
Figure 4-97: Delete eNB or CPE
In the upper right corner of the Device Management window, you will see a + icon to add
devices and an import icon to import device configuration data. Refer to Figure 4-98.
161
Figure 4-98: Add Device Icon and Import Device Configuration Icon
Using the + add icon, you will be prompted to enter the device’s serial number and click on
Add. After you enter the serial number and press OK, the Device Management window will
now include that new device in the list on the right. Using the import function, you will be
asked to identify the file path to the file to be uploaded. Click OK after you have selected the
file. Refer to Figure 4-99.
Figure 4-99: Add Device or Import Device Configuration
Unless the device is added to a device group that you have defined, the new device will be
placed automatically in the Default Device Group.
To create a device group, in the left pane called Device Group, click on + add (Figure 4-100).
Enter a group name and description, and then click on OK.
Figure 4-100: Add Device Group
162
Once the device group has been created, you can select the check box next to each device in
the list on the right, and then select Move to Device Group (Figure 4-101). Select the device
group name that you want to move the device to, and then click on OK (Figure 4-102).
Figure 4-101: Move to Device Group
Figure 4-102: Select Device Group
4.4.5.2 User Management

The term “user” in the System > User Management menu refers to OMC administrators. This
menu is typically used by the operator’s primary administrator to configure other
administrators who may access the operator’s OMC account. This menu should not be
confused with the Baicells Business and Operation Support System (BOSS), one of the
CloudCore applications for subscriber management.
The page is organized like the Device Management page, where the list of administrative user
groups appears on the left and the list of individual administrative users appears on the right.
You will see the user name, the user group to which the user is assigned, current status (e.g.,
active or inactive), a description, and the last login time (Figure 4-103).
Figure 4-103: System User Management
163
4.4.5.2.1 Modify System User Group
To modify an existing system user group, click on the pen icon under Operation. This will open
a dialogue box with 3 tabs: Menu, Operation, and Device Group. See Figure 4-104.
Figure 4-104: Modify User Group > Menu tab
The Menu tab allows you to select the OMC functions that you want users in that group to
have access to. Click on OK to save the configuration.
Under the Operation tab (Figure 4-105), for all users in the user group you can select Reboot
to reboot the UEs, select Factory Reset to reset the UEs to the original settings they had from
the manufacturer, or select Delete to delete the UEs. Click on OK to save the configuration.
Figure 4-105: Modify User Group > Operation tab
164
The Device Group tab allows you to change the user group name or description for the selected
user group (Figure 4-106), and to associate the user group with a device group.
Figure 4-106: Modify User Group > Device Group tab
4.4.5.2.2 Add New System User Group

To add a new system user group, in the left navigation pane that says User Group, click on the
+ (add) icon. The system will display a dialogue window for you to assign a user group name
and description, and to define the OMC Operation options for the group (Figure 4-107). Use
the Device Group tab to assign the user group to a device group. Click on OK in each tab to
Figure 4-107: Add User Group
165
4.4.5.2.3 Delete System User Group
Use the trash can icon under Operation to delete an existing system user group. The system
will prompt you to be sure before you take this action.
4.4.5.3 Log Management

The System > Log Management function is where you can collect, view, or save many different
kinds of logging events that occur in the Baicells network. The two sub-menus shown in Figure
4-108 enable you to view logging information both for the operator’s OMC account and for
the operator’s Baicells network devices.
Figure 4-108: Log Management Menu
4.4.5.3.1 OMC Logs

The OMC logs account for all operator events that occur in their OMC account. There are 3
sets of OMC logs: Operation, Security, and System logs. The Operation logs appear first. Refer
to Figure 4-109.
166
Figure 4-109: OMC Operation Logs
You can use the query or advanced query to sort the list of logs by operation name, operator
(if you manage more than one account), administrative user name, operate [operator] IP,
record details, start time, or end time (Figure 4-110). The query functions are similar across
the log categories.
Figure 4-110: OMC Operation Logs
The OMC operation logs are very useful for determining which users have been using the
operator’s OMC account, what actions they took, and so forth. The adaptive display of the logs
enables you to toggle the columns in order to customize your view. For instance, toggling on
Operation Name sorts the list alphabetically in either ascending or descending order. Toggling
on Record Detail sorts the list by date and time in either ascending or descending order.
When you click on the Security tab at the top, you will see a list of OMC events related to OMC
system security (Figure 4-111).
167
Figure 4-111: OMC Security Logs
Clicking on the System Log tab displays logs pertaining to the Baicells network devices (Figure
4-112). Use the query function to find a specific device.
Figure 4-112: OMC System Logs
4.4.5.3.2 Device Logs

The System > Log Management > Device Log option offers two views of eNB devices: Device
Report Log and Device Exception Log. In the dialogue window you can search for logs for all
devices in the operator’s network, or you can select a specific eNB using its serial number to
query and bring up the information. Refer to Figure 4-113.
168
Figure 4-113: Device Logs
The Device Report Log is for collecting periodic log reports from eNBs. The Device Exception
Log will report when an eNB crashes or something else causes it to reboot.
4.4.6 Help
The Help > About menu displays the software version number and name (Figure 4-114). In a
future CloudCore release, this Baicells Configuration and Network Administration Guide will
be a pdf download option from the Help menu.
Figure 4-114: Help
169
4.5 BOSS
4.5.1 Overview
Individual users (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 tab you will see a menu in the left navigation pane
(Figure 4-116). This section will explain the functions for each of the menu items.
Figure 4-116: BOSS Menu
170
4.5.2 Subscriber
The BOSS Subscriber function is where you can view, modify, or delete any existing subscribers
and where you will add new subscribers to your network. Clicking on the Subscriber menu
brings up a list of existing active subscribers (Figure 4-117).
Figure 4-117: Subscriber
Use the Query button to display only the SIM cards you wish to view or change. You can filter
the list by SIM code, subscriber name, status (Figure 4-118), etc.
Figure 4-118: Query
When planning to add a new subscriber, you will need two special pieces of information that
must be pre-configured: the SIM code for the card the user inserts in the UE, and the service
plan for the subscriber. The SIM cards are identified to the system under BOSS > Network,
covered later in this section. The service plans are created under BOSS > System > Service Plans,
also covered later in this section. You will need to add the SIM cards and define the service
plans prior to adding a new subscriber. Additionally, we recommend that you review those
sections and gather the required information before you begin using BOSS to add new
subscribers in the system.
To add a new subscriber, click on the New button. This will bring up a New Subscriber dialogue
window, as shown in Figure 4-119. The fields highlighted in red are mandatory fields; also, you
must enter an email address for the subscriber to receive invoices. For the SIM Card field, click
on the magnifying glass icon to search for the correct SIM card number (Figure 4-120). When
you find the SIM card number, highlight the row and click on Select. The SIM Card field will
then be populated with the subscriber’s SIM code.
171
Figure 4-119: Add New Subscriber
Figure 4-120: SIM Query
For the Service Plan, you will use the magnifying glass to bring up a list of available plans
defined under System > Service Plans and select the service level the user wishes to subscribe
to (Figure 4-121). Many operators offer different service level packages at different rates. A
subscriber’s service can be changed only one time per month. How to add service plans is
covered in section 4.5.4.1.
Figure 4-121: Service Plan Selection
Once you complete the new subscriber information, click on Save to save the configuration.
You will see the new subscriber information in the list under the Subscriber tab (Figure 4-122).
However, initially the subscriber will be in suspended status. When you are satisfied that the
subscriber’s information is correct, find the subscriber in the list and select Active under the
Operation field. The system will ask you to confirm the operation. Click on OK to activate the
subscriber. The subscriber should now be able to access the operator’s network.
172
To edit a subscriber’s information, highlight the subscriber in the subscriber list, and then
select Detail under the Operation column (Figure 4-122). This will bring up most of the
subscriber’s detailed information. The subscriber detail window has 2 sub-menus, Overview
and Service. While in the Overview sub-menu, click on Edit to open fields where you can make
general changes. Clicking on the Edit button changes the button to a Save button. When
finished making the changes, click on Save.
Figure 4-122: Subscriber Detail - Overview
To change the subscriber’s service plan or SIM card number, click on the Service sub-menu on
the left under Subscriber (Figure 4-123). If the service plan type is “free”, it can be modified to
any type of service plan. If the type is “pre-pay” or “invoice”, it can only be modified to the
same type of service plan. Select the Change button, make the changes, and select Save to
retain the changes.
Figure 4-123: Subscriber Detail – Service
173
After a service plan is modified, BaiBOSS will calculate the balance of the previous service plan
automatically according to the service plan type:
• Data Plan – After the data plan is changed, the bill is created at once. The amount of
the bill will include the balance of the previous service plan and the amount of the
new service plan. Data Plan is not activated in the software as of this release.
• Time Plan – After the time plan is changed, the bill will be created on the first day of
the second month. The amount of the bill will include the balance of the previous
service plan and the amount of the second month of the new plan.
Notice that you can also delete the subscriber using the Delete button under the Operation
field. As with the Active operation, using the Delete operation will bring up a confirmation
window. When you delete a subscriber record, it is maintained in the Archive list. Click on OK
to save the configuration.
To see a list of subscribers that have been deleted (archived), select the Archive tab at the top
left of the Subscriber list window. You can run a query to locate a subscriber, reset subscriber
information, and restore a subscriber to active status. Refer to Figure 4-124.
Figure 4-124: Archived Subscribers
To restore a subscriber whose account was archived, in the Subscriber > Archive list use the
Restore button under Operation (Figure 4-125).
Figure 4-125: Restore Archived Subscriber
4.5.3 Network
The Network menu under BOSS is where you will define and manage SIM card information
(Figure 4-126). Typically, the Baicells super administrator will import the SIM card information
into BOSS, send the operator an activation code, and then the operator’s administrator can
import the information into their BOSS account. It is this list of SIM cards that you search on
when adding a new subscriber or editing an existing subscriber’s SIM information.
174
Figure 4-126: Network Menu
4.5.3.1 SIM Card

Click on Network > SIM Card to display a list of existing SIM cards in use (Figure 4-127). Use
the open fields and Query button to sort the list as needed.
Figure 4-127: Network > SIM Card
The BaiBOSS system provides two ways for the administrator to import the operator’s SIM
cards. One is to activate the SIM cards using the activation code provided by Baicells. The other
is to import the SIM card information using an Excel template.
To activate SIM cards using the Baicells activation code, follow the steps below.
1. In the SIM Card list window, select the Import tab as shown in Figure 4-128.
Figure 4-128: Import
2. Click on the Import SIM Card button to open a dialogue box (Figure 4-129).
175
Figure 4-129: Import SIM Card Dialogue
3. For Activate Code, input the activation code and click on Import. One activation code
supports up to 100 SIM cards.
4. To view the list of SIM cards that correspond to the activation code, in the SIM Card
list click on Detail.
The other method for importing SIM cards is to import the SIM information using an Excel
template. In Network > SIM Card, click on the Import sub-menu at the top of the window, and
then select the File sub-menu. Click on the Download Template button to save the Excel file
format for entering the SIM card information (Figure 4-130).
Figure 4-130: Download Template
In the Excel file you will enter the IMSI of the SIM cards to be imported. After you complete
and save the file, back in the Import > File dialogue box click on the pen icon next to the File
field and navigate to the file with the SIM card information (Figure 4-131). When you have
found the file, select the Import button.
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.
176
Figure 4-131: Import SIM Card File
Once the SIM information, specifically the IMSI, is imported or assigned, when the UE is
installed and powered on it will trigger the automatic UE registration in the operator’s OMC
account. This is part of the CloudKey activation process described in Appendix D.
4.5.3.2 SIM Audit Records

The Network > SIM Audit Records function enables you to run queries and keep track of SIM
card assignment and usage. You can sort the list of SIM cards by batch number, SIM code
number range, or status. The Status field selections are shown in Figure 4-132.
Figure 4-132: SIM Audit Records
177
4.5.4 System
The BOSS System menu (Figure 4-133) enables you to define subscriber service plans and to
look at logging events for each subscriber (e.g., password resets, service plan changes, etc.).
Figure 4-133: System Menu
4.5.4.1 Service Plans

4.5.4.1.1 Overview of Service Plans
The BaiBOSS system currently supports one type of payment service: a time-based plan. A
time plan is based on a month-to-month service renewal window. When a subscriber is added
to BOSS and assigned to a time plan, the system sends an invoice at the first of each month.
The invoice will include the charges for the previous month and show a prepaid amount for
the next month.
BaiBOSS allows subscriber payment through cash or online bill payment. If payment is by cash,
the operator’s administrator can input in BOSS the amount of cash paid.
4.5.4.1.2 Configure Service Plans

When you click on System > Service Plans, the system will display a list of any existing service
plans already defined. You can perform a search for a particular service plan, and you can
create new service plans. Refer to Figure 4-134.
Figure 4-134: Service Plans
178
When you select System > Service Plans the list of existing service plans defaults to service
plans that are in use. Service plans can be in one of three states, and you can filter the list by
using the Status pull-down menu, as shown in Figure 4-135. Select Disabled for a list of service
plans that have been defined but disabled. Select In Use for a list of service plans currently in
use (assigned to active users). Select Ready for a list of service plans that have been defined
but not yet enabled. After making your selection, click on Query to refresh the list.
Figure 4-135: Filter List of Service Plans
To add a new service plan, select the Add Service Plan button to open the dialogue window
(Figure 4-136). Even once you save the new service plan, it will not be enabled for use to assign
to subscribers until you select Enable (shown in Figure 4-137).
Figure 4-136: Add Service Plan
179
Figure 4-137: Enable Service Plan
Each new service plan that you configure is automatically assigned a code number in the
system. Currently, the service plan period covers one month, as most operators bill subscribers
on a monthly basis. You must complete the Add New Subscriber fields highlighted in red.
Assign a unique name to this service plan in the Name field. The UL Rate Limit (M) equates to
the bandwidth that subscribers with this service plan will receive when uploading data to the
network, e.g., 5 Mbps or 10 Mbps. The DL Rate Limit (M) equates to the bandwidth that
subscribers with this service plan will receive when downloading data from the network.
Typically, users will download data more often than upload data, and for that reason the DL
Rate Limit may be a higher bandwidth, e.g., 25 Mbps or 35 Mbps. The maximum UL and DL
limits are determined by several factors, including which equipment models are used.
Enter the UL and DL Rate Limit based on Mbps. The entry supports 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).
The Based field uses the default time plan in this version of software. The Period field choice
in this release is 1month only. Enter the dollar amount in the Amount ($) field indicating the
amount of money you wish to charge subscribers associated with this plan. You have the
option to add further information under the Notes field. Click on Save to save the information.
The new service plan will appear in the Service Plans list.
Under the Operation field in the list of plans are 3 choices: Enable/Disable, Delete, and Edit.
Select Enable to enable the new service plan so that you can assign subscribers to it. If you
wish to temporarily disable a service plan, highlight the row for the target plan and click on
Disable. The system will return a confirmation window, and the plan will be suspended until
you enable it again. Use Delete if you want to completely delete the plan. When this action is
taken, subscribers assigned to this service plan will be moved to the default service plan.
To edit details of an existing service plan, highlight the row for the target plan and click on Edit.
This will bring up the same dialogue window as when you first created the plan. Enter your
changes, and then select Save to save the revised plan.
180
4.5.4.2 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. You can query for a subscriber’s records using
their name, SIM code, and so forth. 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. Refer to Figure 4-138.
Figure 4-138: Logs
You can filter and run a query to sort the list of logs based on name, SIM code, or time period.
You can also filter the list based on type of activity you need to see. To do this, use the Service
Processing pull-down menu (Figure 4-139). The choices are SIM Changes, Active users, New
users, Service Changes, Deletions, and Deactivated users. After making your selection, click on
Query.
Figure 4-139: Service Processing Filter List Options
4.5.5 Help
When you click on Help > About, the system displays the BOSS software version level (Figure
4-140). In a future CloudCore release, the Help menu will include this document.
Figure 4-140: Help
181
Appendix A: MML Commands
Man-Machine Language (MML) refers to the commands that the administrator enters to “talk”
to and manage the system. The MML commands used with Baicells systems are defined in the
format shown in the table below.
Note: When importing MML scripts, the instructions need to be separated line by line and
stored in .txt format.
Grammar Action Subject: Examples:

Index=i,
Parameter1=xxx, MOD CELL: LocalCellId=1, LTE_PHY_CELLID_LIST=102,
Parameter2=xxx; LTE_OAM_PLMNID=46001; {eNodeBID=1000}
{Specified
Unit=xxx} MOD UETIMER: LocalCellId=1, LTE_T300=100;
{eNodeBID=1001}
Elements Action LST, MOD, ADD, RMV, etc., corresponding to Columns S,
T, U, and V
Subject eNB, Cell, etc., corresponding to Column D
Parameter Example: PCI=101, corresponding to mib_dn in Column
Q. Multiple parameters are allowed under the same
subject.
Specified Unit Example: eNodeBID=1000 means the eNodeB whose ID is
1000
Index Index of the subjects, e.g., number of the cell.
LOCALCELLID=1 corresponds to i
Punctuation Space 1. Separate the Action and the Subject; 2. No special
meanings
Colon： Separate the Subject and the options
Comma, Separate the parameters
Semicolon; Finish the current command
Brace{} Specify an eNB number
182
Appendix B: Abbreviations and Acronyms
Acronyms related to the Baicells network or that are used in this document are listed in
alphabetical order and described in the table below.
Acronym Abbreviation for Description

1xEV-DO 1x Evolution for Data 1xEV-DO is a telecommunications standard for the
Optimized wireless transmission of data through radio signals,
typically for broadband internet access
3GPP Third-Generation 3GPP is a standards body that works within the
Partnership Project scope of the 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 3GPP2 is a collaboration between multiple
Partnership Project 2 telecommunications 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 4G is a mobile communications standard intended to
Wireless Systems evolve 3G technology, allowing wireless internet
access at a much higher speed.
AAA Authentication, AAA is a framework for controlling access to
Authorization, and computer resources, enforcing policies, auditing
Accounting 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
Acknowledgement (TCP) to acknowledge receipt of a data packet.
AM Acknowledged Mode AM requires the receiver of information to send
continuous notifications to the sender that indicate
it has successfully received the information.
183
AMBR Aggregate Maximum Bit AMBR is the maximum possible bit rate configured
Rate by the LTE operator for a particular LTE user.
AMC Adaptive Modulation AMC is used to denote the matching of the
and Coding modulation, coding, and 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 ANR is a third-generation (3G) telecommunications
Relation 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 ARP is a telecommunication protocol used for
Protocol resolution of internet layer addresses into link layer
addresses, a critical function in multiple-access
networks.
ARP Allocation and Priority level assigned to bearer traffic. In a mobile
Retention Priority network, ARP decides whether to accept a request
to establish a bearer or reject the request when
resources are limited.
ARQ Automatic ARQ is an error-control method for data transmission
Repeat reQuest 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.
184
BCCH Broadcast Control BCCH is a logical broadcast channel used by the eNB
Channel 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.
BOSS Business Operations BOSS is a Baicells CloudCore application that enables
Support System operator 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 BPSK is a digital modulation scheme that conveys
Keying 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.
CBRS Citizens Broadband CBRS is a somewhat new shared spectrum scheme
Radio Service that was introduced in the US at 3.5 GHz. It is
especially well suited for in-building small cells. CBRS
could result in improved LTE services from service
providers, as well as enable enterprises to build their
own private LTE networks.
C-RNTI Cell Radio Network C-RNTI is a unique temporary identification used for
Temporary Identity identifying Radio Resource Control (RRC) connection
and scheduling dedicated to a particular subscriber.
CDMA Code Division Multiple CDMA is a wireless technology where several
Access 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
185
(MPLS) network. MPLS is a type of data-carrying
technique for high performance telecommunications
networks.
CFI Channel Format In LTE, the CFI value defines the time span, in
Indicator 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- CINR is a measurement of multiple subcarriers; it
plus-Noise Ratio reflects the signal 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 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 CPE, also called User Equipment (UE), is the
Equipment equipment used by a network subscriber to connect
to the backhaul carrier network through the access
network.
CQI Channel Quality The CQI is an indicator which carries the information
Indicator on how good or bad the communication channel
quality is.
CRC Cyclic Redundancy CRC is an error-detecting code commonly used in
Check digital networks and storage devices to detect
accidental changes to raw data.
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 The CSCF is responsible for the signaling that
Function controls the communication of Instant Messaging
Service (IMS) user equipment with IMS enhanced
services across different network accesses and
domains.
186
CS-CN Circuit Switched Core In a CS-CN, the bit delay is constant during a
Network 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 CSI refers to known channel properties of a
Information communications link. The information describes how
a signal propagates from the transmitter to the
receiver.
DCCH Dedicated Control The DCCH is a single timeslot on a radio frequency
Channel (RF) carrier that is used to convey eight stand-alone
dedicated control channels.
DCI Downlink Control In LTE, DCI is based upon a process defined as a blind
Information decoding which depends on several decoding
attempts on several Physical Downlink Control
Channels (PDCCH) candidate locations for several
defined DCI formats.
DFT Discrete Fourier The DFT converts a finite sequence of equally-spaced
Transform samples of a 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 DHCP is a network protocol that enables a server to
Configuration Protocol assign an IP 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 The DL-SCH is the main data bearing channel, which
Channel 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
DRA Dynamic Resource DRA is an essential technique to exploit the time-
Allocation 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 DRX is a method used in communications to
Reception conserve energy use. The user equipment and the
187
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 DSCP is a field in an IP packet that enables various
Code Point levels of service to 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.
DTCH Dedicated Traffic A DTCH is an uplink or downlink
Channel communication channel that is only accessible by
one device to transfer user data.
DTX Discontinuous DTX is a method of momentarily powering
Transmission down a wireless device when there is no data
throughput.
EARFCN E-UTRA Absolute Radio A unique number given to each radio channel in
Frequency Channel Global System for Mobile (GSM) communications.
Number The EARFCN is used to calculate the exact frequency
of the radio channel.
ECM Evolved Packet System ECM is the process of identifying, setting up,
(EPS) Connection controlling, and removing a transmission path
Management between two or more points in the Universal Mobile
Telecommunications System (UMTS) evolved packet
system.
EIRP Effective Isotropic EIRP is the product of transmitter power and
Radiated Power antenna gain in a 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
Management technology focused on 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 As part of the 3GPP Standard Release 8, the user
(EPC) User Plane data (user plane) is separated from the signaling
188
(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 The concatenation of an S1 bearer and the
Bearer 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 ESP is a protocol within the Internet Protocol
Payload Security (IPSec) standard for providing
authentication, integrity, and confidentiality of
network packet data in IPv4 and IPv6 networks.
E-UTRA Evolved Universal E-UTRA is the air interface of 3GPP’s LTE upgrade
Mobile path for networks.
Telecommunications
System (UMTS)
Terrestrial Radio Access
E-UTRAN Evolved Universal E-UTRAN is the combination of E-UTRA, user
Mobile equipment, and eNBs.
Telecommunications
System (UMTS)
Terrestrial Radio Access
Network
EV-DO Evolution for Data EV-DO is the third-generation (3G)
Optimized 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 FDD is a method for establishing a full-duplex
Duplex communications link that uses two different radio
frequencies for transmitter (Tx) and receiver (Rx)
operation.
FDM Frequency Division FDM is a technique for sending two or more signals
Multiplexing over the same radio channel. Each signal is
transmitted as a unique range of frequencies within
the bandwidth of the channel as a whole, enabling
several signals to be transmitted simultaneously.
FDMA Frequency Division FDMA is a channel access method used in multiple-
Multiple Access access protocols as a channelization protocol. FDMA
189
gives users an individual allocation of one or several
frequency bands, or channels.
FEC Forward Error FEC is a method of obtaining error control in data
Correction 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 FMC is the trend towards seamless connectivity
Convergence between fixed and wireless telecommunications
networks.
FQDN Fully Qualified Domain Also known as an absolute domain name, FQDN is a
Name 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 GBIC is a standard for transceivers, commonly used
Converter 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 A GGSN is part of the core network that connects
Node 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 GPRS is a packet-oriented mobile data service on the
190
Service second-generation (2G) and third-generation (3G)
cellular communication system’s Global System for
Mobile (GSM) communications.
GSM Global System for A digital mobile telephony system which uses a
Mobile variation of Time Division Multiple Access (TDMA)
technology. GSM is the most widely 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 GTP is a group of IP-based communications protocols
Service (GPRS) used to carry General Packet Radio Service (GPRS)
Tunneling Protocol within Global System for Mobile (GSM)
communications), Universal Mobile
Telecommunications System (UMTS), and Long-Term
Evolution (LTE) networks.
GTP-U General Packet Radio GTP-U is used for carrying user data within the
Service (GPRS) General Packet Radio Service (GPRS) core network
Tunneling and between the radio access network (RAN) and
Protocol (GTP) User the core network (CN).
Plane
GUMMEI Globally Unique MME The GUMMEI is constructed from the Mobile
Identity Country Code (MCC), Mobile Network Code (MNC),
and Mobility Management Entity (MME) Identifier
(MMEI).
GUTI Globally Unique GUTI is allocated to the user equipment (UE) by the
Temporary User Mobility Management Entity (MME) and has two
Equipment (UE) Identity 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
191
(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 HDTV is a television display technology that provides
Television picture quality similar to 35mm film.
H-FDD Half-Frequency Division H-FDD requires that two communication parties take
Duplex 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 The HPLMN identifies the public network in which
Mobile Network the subscriber’s profile is held. Users roaming to
(PLMN) other networks will receive subscription information
from the HPLMN.
HSDPA High Speed Downlink HSDPA is an enhanced third-generation (3G)
Packet Access communications protocol which allows networks
based on Universal Mobile Telecommunications
System (UMTS) to have higher data speeds.
HSPA High Speed Packet HSPA is a telecommunications technology that
Access 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 HSUPA is an amalgamation of two mobile protocols,
Packet Access High Speed 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.
ICI Inter-Carrier ICI is an impairment known to degrade performance
Interference 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).
192
ICIC Inter-cell Interference ICIC techniques apply restrictions to the radio
Coordination resource management (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
Transform Fourier Transform (DTFT) samples as coefficients of
complex sinusoids at the corresponding DTFT
frequencies. It has the same sample-values as the
original input sequence.
IEEE Institute of Electrical The IEEE is a technical professional organization
and Electronics whose purpose is to educate and advance electrical
Engineers and electronic engineering, telecommunications,
computer engineering, and allied disciplines.
IETF Internet Engineering The IETF is the body that defines standard internet
Task Force operating protocols such as TCP/IP.
IFFT Inverse Fast Fourier An IFFT algorithm computes the Discrete Fourier
Transform Transform (DFT) of a sequence, or its inverse.
IMEI International Mobile IMEI is a 15- or 17-digit code that uniquely identifies
Equipment Identity mobile phone sets.
IMS Internet Protocol (IP) The IMS or IP Multimedia Core Network
Multimedia Subsystem Subsystem is an architectural framework for
delivering IP multimedia services.
IMSI International Mobile An IMSI is used to identify the user of a cellular
Subscriber Identity network and is a unique identification associated
with all cellular networks.
IMT International Mobile IMT is a set of requirements issued by the
Telecommunication International Telecommunication Union (ITU-R) in
2008 for what is marketed as 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 IPSec is a protocol suite for secure internet
Security protocol communications that works by
authenticating and encrypting each IP packet of a
communication session.
IPv4 Internet Protocol IPv4 is the fourth revision of the internet protocol
Version 4 (IP) and a widely-used protocol in data
193
communications over various kinds of networks. IPv4
is a connectionless protocol used in packet-switched
layer networks, such as Ethernet.
ISI Inter-Symbol ISI is a form of distortion of a signal in which one
Interference 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 ISUP is the protocol used to support the signaling
Digital Network (ISDN) necessary to provide voice and non-voice services in
Signaling User Part telephone communications. 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
Telecommunication purpose is to coordinate telecommunication
Union 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 In the context of a telecommunications network, a
Indicator 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.
L3 Layer 3 The network layer, or L3, is the third layer of the
194
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 The MAC is used to authenticate devices based on
195
Code 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 MBMS is a point-to-multipoint interface specification
Multicast Service for Third-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.
MBSFN Multimedia Broadcast MBSFN is a transmission mode which exploits LTE’s
Multicast Service Orthogonal Frequency Division Multiplexing (OFDM)
(MBMS) Single radio interface to send multicast or broadcast data
Frequency Network 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 The MCCH is a sublayer of Layer 2 protocol of Radio
Channel 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 MCM is a method of transmitting data by splitting it
Modulation 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 MCS is a numerical index based on Orthogonal
Scheme 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
196
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
Function with an H.248 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 MIB is a very important message or information that
Block 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 MIMO is an antenna technology for wireless
Output communications in which multiple antennas are
used at both the source and the 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 MISO is an antenna technology for wireless
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
197
are often used interchangeably, even though,
technically, IMS is a subset of MMD.
MME Mobility Management The Long-Term Evolution (LTE) MME is responsible
Entity 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 MMS is a standard way to send messages that
Service 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 MTCHs are the channels used to transport
Multicast Service multimedia content from one device to another.
(MBMS) Traffic Channel
MTU Maximum Transmission The size of the largest network layer protocol data
Unit unit that can be communicated in a single network
transaction
NACK Negative NACK is a signal used in digital communications to
Acknowledgement 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 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
198
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 NFV is a network architecture concept that uses the
Virtualization 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 An NMS is a set of hardware and/or software tools
System 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.
OFDM Orthogonal Frequency OFDM is a frequency division multiplexing scheme
Division Multiplexing used as a digital 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 OFDMA is a multi-user version of OFDM. Multiple
Division Multiple Access access is achieved in OFDMA by assigning subsets of
subcarriers to individual users.
OMC Operations The Baicells OMC is a Cloud-based network
Management Console management application with a graphical user
interface (GUI) that enables operator administrators
to configure and manage the Baicells eNBs and UEs.
OPC Object Linking and Open Platform Communications (OPC) and OLE for
Embedding (OLE) for Process Control is a series of standards for industrial
Process Control telecommunications, and which enable real-time
plant data between control devices from different
manufacturers.
OSS Operations Support An OSS is a set of programs that help a
System communications service provider monitor, control,
199
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 PAPR is the relationship between the maximum
Ratio power of a sample in a transmitted Orthogonal
Frequency Division Multiplexing (OFDM) symbol and
its average power.
PBCH Physical Broadcast The PBCH carries system information for user
Channel equipment requiring access to the network. It only
carries what is termed Master Information Block, or
MIB, messages.
PCC Policy and Charging Network function that enables application servers to
Control 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.
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
Enforcement Function gating and QoS for individual IP flows.
PCFICH Physical Control Format The PCFICH is one of the control channels that works
Indicator Channel at Layer 1, the 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
Function that provides policy control and flow based charging
200
control decisions.
PDCCH Physical Dedicated The PDCCH carries a message called Downlink
Control Channel Control Information (DCI), which includes resource
assignments for user equipment.
PDCP Packet Data PDCP is specified by the Third-Generation
Convergence Protocol Partnership Project (3GPP) 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 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 The PDSCH is the main data bearing channel which is
Shared Channel allocated to 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 The PHICH in the downlink carries Hybrid ARQ
Automatic Repeat acknowledgements/negative acknowledgements
Request (ARQ) Indicator (ACK/NACK) for uplink data transfers. PHICHs are in
Channel 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
201
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 A PLMN is any wireless communications system
Network 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 The PMCH is a transmission channel that is used to
Channel 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
Channel terminals to access the mobile network, e.g., Time
Division, Frequency Division, or Code 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
Temporary Identity paging 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.
202
P-SCH Primary Synchronization The P-SCH is a code that is repeated at the beginning
Channel of each time 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.
PSDU Protocol Service Data The PSDU is referred to in the Institute of Electrical
Unit 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 The PSTN is the aggregate of the world’s circuit-
Telephone Network switched telephone 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
Channel Information (UCI). Long-Term Evolution (LTE) user
equipment can never transmit both PUCCH and
Physical Uplink Shared Channel (PUSCH) during the
same subframe.
PUSCH Physical Uplink Shared The PUSCH channel carries user data. It supports
Channel 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 modulation scheme. It 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 QCI is a mechanism used in Third-Generation
(QoS) Class Identifiers Partnership Project (3GPP) Long Term Evolution (LTE)
networks to ensure bearer traffic is 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.
203
QPSK Quadrature Phase Shift QPSK is a form of Phase Shift Keying (PSK) in which
Keying 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 RACH is a shared channel used by wireless terminals
Channel 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 RAT is the underlying physical connection method for
Technology 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
(UMTS) and Long-Term Evolution (LTE) networks.
ROCH Robust Header ROCH is a standardized method to compress the
Compression 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
(UMTS) and Long-Term Evolution (LTE) networks.
RRC handles the control plane signaling of Layer 3
between the user equipment and the Radio Access
204
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 RRM is the system level management of co-channel
Management interference, 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 The RSRP is the linear average over the power
Received Power contributions for the 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 The RSRQ reflects the relative ratio of signal and
Received Quality interference within 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
Indicator the user 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 acknolwedgement
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
205
eNB control plane. S1-U supports the tunneling of
end-user packets between the eNB and the User
Plane Entity (UPE).
SAE System Architecture SAE is the core network architecture of the Third-
Evolution Generation Partnership Project’s (3GPP’s) Long-Term
Evolution (LTE) wireless communications standard.
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.
SC-FDMA Single Carrier Frequency SC-FDMA deals with the assignment of multiple
Division Multiple Access users to a shared communication resource. It is also
called Linearly Pre-coded OFDMA (LP-OFDMA)
SCH Synchronization An SCH is a downlink control channel used in Global
Channel 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 The SCTP is a transport layer protocol, serving in a
Transmission Protocol similar role to the 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) SDMA is a satellite communications mode that
Division Multiple optimizes the use of radio spectrum and minimizes
Access 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 An SFP is a small transceiver that plugs into
Pluggable 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.
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)
206
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 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 SI messages inform mobile devices about all
Message 1 important parameters of how to access the network
and how to find neighboring cells.
SIB System Information A SIB carries relevant information for the user
Block 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 A SIM card is an integrated circuit that stores a
Module mobile subscriber’s critical information securely
SIMO Single Input Multiple SIMO is an antenna technology for wireless
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- Signal-to-Interference-plus-Noise-Ratio (SINR), also
plus-Noise Ratio 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 the interference power from all the
other interfering signals and background noise.
SIP Session Initiation SIP is a communications protocol for signaling and
Protocol controlling multimedia communication sessions.
SIR Signal-to-Interference See “SINR”.
Ratio
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.
207
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 SOFDMA refers to the air interface outlined for
Frequency Division portable or mobile WiMAX systems by the Institute
Multiple Access 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.
SRNC Serving Radio Network When a Radio Network Controller (RNC) has a Radio
Controller Resource 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 The separate tunnels between each set of end points
Identifier are identified by a TEID in the General Packet Radio
Service Tunneling Protocol for User Data (GTP-U)
messages, normally a dynamically allocated random
208
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 TTI is a parameter in Universal Mobile
Interval 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
Telecommunications eNB’s frequency.
System (UMTS)
Absolute Radio
Frequency Channel
Number.
UCI Uplink Control The UCI is a set of information that is carried by the
Information Physical Uplink Control Channel (PUCCH). Depending
on what kind of information the UCI in the Physical
Dedicated Control Channel (PDCCH) carries, 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
209
(RLC) used on the air interface in Long-Term
Evolution (LTE) networks.
UMA Unlicensed Mobile UMA is a technology that allows UMA-capable user
Access equipment to switch back and forth seamlessly
between networks and local wireless networks.
UMTS Universal Mobile UMTS is a third-generation broadband, packet-based
Telecommunications transmission of text, digitized voice, video, and
System 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 A SIM card is an integrated chip that securely stores
Identity Module a mobile 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 VoIP is a service that enables people to make voice
Protocol calls using only their computers connected to the
network. With VoIP, the internet is the transmission
medium for telephone calls by sending voice data in
packets using IP rather than by traditional circuit
transmissions of the Public Switched Telephone
Network (PSTN).
VPLMN Visited Public Land VPLMN is the network on which the mobile
Mobile Network subscriber has roamed when leaving their Home
(PLMN) PLMN (HPLMN).
VRB Virtual Resource Blocks Physical Resource Blocks (PRBs) and VRBs support
various kinds of resource allocations. VRB supports
both block-wise transmission (localized) and
transmission on non-consecutive subcarriers
210
(distributed) to maximize frequency diversity.
WCDMA Wideband Code Division WCDMA is a third-generation standard that employs
Multiple Access the Direct 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 WiMAX is a family of wireless communication
Interoperability for standards based on the Institute for Electrical and
Microwave Access Electronics Engineering (IEEE) 802.16 set of
standards, which provide multiple physical layer
(PHY) and Media Access Control (MAC) options.
WLAN Wireless Local Area See “Wi-Fi”.
Networks
211
Appendix C: FAQs
If you have questions, please check the most up-to-date Frequently Asked Questions (FAQs)
as well as other helpful resources on the following websites:
• Baicells support website - https://na.Baicells.com/support/
• Baicells support forum on Facebook -
https://www.facebook.com/groups/Baicellsoperatorsupportgroup/
212
Appendix D: CloudKey
More recent releases of user equipment (UE) firmware (for example, version 1.0.8) allow the
operator to pre-configure the UE using the Baicells CloudCore Operations Management
Console (OMC). The operator enters their CloudKey account information in the UE Web GUI
or through the OMC, as follows. The operator’s CloudKey information is shown in the top right
corner of their CloudCore account. Each CloudKey is unique to each operator.
UE GUI:
Log in to the UE GUI for the device.
1. Click on the System tab located on the left.
2. Click on TRO69.
3. Enter the operator’s CloudKey information in the box marked CloudKey.
4. Click on Submit, and once the UE attaches to the eNB the UE will apear in the OMC
Monitor window. A reboot is not required for this field to take effect.
OMC:
Alternatively the operator can use the OMC Device Manager function to add the UE.
1. Log in to your OMC account.
2. Click on System > Device Management.
3. Click +Add in the top right corner.
4. A popup window will appear. Enter the UE’s MAC address, and the UE device will be
added to the operator’s account.
213

Baicells Configuration & Network Administration Guide (SRv1.5 10-Jan-2018) PUBLISH

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Baicells Configuration & Network Administration Guide (SRv1.5 10-Jan-2018) PUBLISH

Transféré par

Droits d'auteur :

Formats disponibles

Configuration & Network

UE – Gen 1 Atom 5dBi Indoor CPE User Manual

2. ENB GUI ..................................................................................................................................... 6

APPENDIX A: MML COMMANDS .................................................................................................... 182

APPENDIX B: ABBREVIATIONS AND ACRONYMS ............................................................................ 183

APPENDIX C: FAQS ......................................................................................................................... 212

APPENDIX D: CLOUDKEY ................................................................................................................ 213

The key components of a Baicells system include the

NOTE: EPC functionality is covered in separate documents, Baicells Enterprise EPC

Figure 1-3: Sample UE GUI Window

Figure 1-6: CloudCore GUI Menu Trees

2.1 Computer Requirements

2.2 Launching the GUI

2.3 Data Preparation

2.5 BTS Info

2.5.1 Basic Info

Table 2-2: Basic Info Fields

Field Name Description

Field Name Description

UL and DL Block Error Ratio (BLER), which represents a ratio

Field Name Description

Table 2-5: Quick Setting Fields

Field Name Description

Refer to the BaiTip on this setting:

Refer to the BaiTip on this setting:

Field Name Description

Caution: The reboot action will disrupt eNB service.

Figure 2-10: Backup Window

Field Name Description

Figure 2-16: Tunnel Configure > Basic Setting

Table 2-8: Tunnel Configure > Basic Setting Fields

Field Name Description

Figure 2-17: Tunnel Configure > Advance Setting

2.8 BTS Setting

2.8.1 Security Setting

2.8.2 Management Server

2.9.1 Identify Neighbor Frequencies and Cell Information

2.9.1.1 LTE Freq/Cell

Table 2-10: LTE Neigh Freq Settings

Field Name Description

2.9.1.1.2 LTE Neigh Cell Table

Table 2-11: LTE Neigh Cell Table Settings

Field Name Description

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

Field Name Description

2.9.1.2.2 TD-S Neigh Cell Table

Table 2-13: TD-S Cell Setting Fields

Field Name Description

2.9.1.3 GSM Freq/Cell

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

Field Name Description

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

Field Name Description

2.9.2 Configure Mobility Parameters

Table 2-16: A1, A2, A3, and A5 Event Threshold Fields

Field Name Description

Table 2-17: B2 Event Threshold Fields

Field Name Description

Table 2-18: Measurement Control Fields

Field Name Description

Table 2-19: Cell Selection and Cell ReSelection Fields

Field Name Description

2.9.3 Configure Advanced Parameters