Configuration - & - Network - Administration - Guide - (SRv1.12 - 4-Sep-2018) (NXP) PDF

Configuration & Network
Administration Guide
September 2018
Version 1.12
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) and Business Operations Support System (BOSS).
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.
This version of the document is written to the following Baicells equipment software versions:
• Standard TDD eNB version: BaiStation_V100R001C00B110SPC009 and 010 (no GUI changes)
• Standard TDD eNB version for Nova-227 and Nova-233 only: 100R001C00B110SPC003
• Standard TDD eNB version for Nova-243 only: BaiStation_V1.1.0.100.11
• HaloB TDD eNB version: BaiBS_RTSH_2.4.1
• UE Gen1 version: BCE-ODU-1.0.12
• UE Gen2 version: BaiCPE_V100R001C01B005SPC009 and BaiCE_AP_2.1.4_NA
• OMC version: 4.2.3
• BOSS version: 4.3.3.3
NOTE: The forthcoming Evolved Packet Core (EPC) functions will be covered in separate
documents, Baicells Enterprise EPC Deployment Guide and Baicells Enterprise EPC User Guide.
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
4-Sep-2018 V1.12 Updated for a) UE GUI: Sonny May Sharon Redfoot
V1.11 BaiCPE_V100R001C01B005SPC009 Nitisha Potti
V1.10 and BaiCE_AP_2.1.4_NA; b) China Rick Harnish
V1.9 OMC doc v3.4; c) dual carrier Jesse Raasch
operation; d) OMC 4.2.3; and e) BOSS Cameron Kilton
4.3.3.3 Yang Yanan
5-Apr-2018 V1.8 Updated for the following and included SME Jesse Raasch Sharon Redfoot
V1.7 V1.6 review comments. Cameron Kilton
Standard TDD eNB version: Nitisha Potti
BaiStation_V100R001C00B110SPC009 Sonny May
Standard TDD eNB version for Nova-227 and Wujungfeng
Nova-233 only: 100R001C00B110SPC003 ZangDandan
Standard TDD eNB version for Nova-243 only: WangYang
BaiStation_V1.1.0.100.11 Ronald Mao
HaloB TDD eNB version: BaiBS_RTSH_2.2.2
UE Gen1 version: BCE-ODU-1.0.12; UE Gen2
version: BaiCPE-V100R001C01B004SPC107
OMC version: 3.4.4
BOSS version: 3.4.1
10-Jan-2018 V1.5 Updated to OMC v3.2.2 and BOSS v3.3.0; added Cameron Kilton Sharon Redfoot
additional details on X2 handoff and neighbor Nitisha Potti
cells config; updated terms UE and eNB for Samuel (Tang) Weizhou
consistency Wu Junfeng
Yang Yanan
16-Nov-2017 V1.4 Updated for: Cameron Kilton Sharon Redfoot
BS GUI version 100R001C00B110SPC003 Wu Junfeng
CPE GUI version BCE-ODU-1.0.12 Zhang Dandan
CloudCore OMC and BOSS version 3.0.1 Nitisha Potti
Sonny May
Yang Yanan
21-Aug-2017 V1.3 Edited based on SME review. Published. Rick Harnish Sharon Redfoot
Cameron Kilton
Wu Junfeng
Tang Houcheng
Prior V1.2 Combined OMC User Guide, Base Station Jesse Raasch Sharon Redfoot
V1.1 Configuration Guide, and BOSS User Guide. Cameron Kilton
V1.0 Added base station and CPE GUIs. Rick Harnish
Nitisha Potti
iii
Related Documents
Other Baicells technical documents may be found on the Baicells website under Support:
https://na.Baicells.com
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/06-6.5 User Manual
Atom OD04/06-14/19.5 User Manual
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
Nova-243 Outdoor 2x10WG2 FDD-TDD eNB Installation Guide
Nova-436 Outdoor 4x1W CCA TDD eNB Installation Guide
EPC/CC/OAM Baicells Configuration & Network Administration Guide (this document)
Baicells Dual Carrier Configuration Quick Guide
Baicells Handoff Configuration Guidelines (Beta trial)
Baicells HaloB User Guide
Baicells BOSS API Manual
Baicells Operation, Maintenance, & Troubleshooting Guide
Contact Us
Baicells Technologies Co., Ltd.
China North America
Address: 3F, Bldg. A, No. 1 Kai Tuo Rd, Haidian Address: 555 Republic Dr., #200, Plano, TX
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 ............................................................................................................................................... 5
2.1 COMPUTER REQUIREMENTS .............................................................................................................................. 5
2.2 LAUNCHING THE GUI ....................................................................................................................................... 6
2.3 DATA PREPARATION ......................................................................................................................................... 7
2.4 CONFIGURATION FLOW .................................................................................................................................... 7
2.5 BTS INFO ...................................................................................................................................................... 8
2.5.1 Basic Info ............................................................................................................................................ 8
2.5.2 Quick Setting .................................................................................................................................... 12
2.6 SYSTEM ....................................................................................................................................................... 14
2.6.1 NTP................................................................................................................................................... 15
2.6.2 Upgrade ........................................................................................................................................... 16
2.6.3 Backup.............................................................................................................................................. 17
2.6.4 Password .......................................................................................................................................... 18
2.7 NETWORK ................................................................................................................................................... 18
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.................................................................................................................................................. 27
2.7.6 CertStore .......................................................................................................................................... 28
2.7.7 Static Routing ................................................................................................................................... 28
2.8 BTS SETTING................................................................................................................................................ 29
2.8.1 Security Setting ................................................................................................................................ 30
2.8.2 Management Server ........................................................................................................................ 30
2.8.3 Sync Setting ...................................................................................................................................... 31
2.8.4 HaloB Setting ................................................................................................................................... 32
2.8.5 License Management ....................................................................................................................... 33
2.9 LTE ............................................................................................................................................................ 34
2.9.1 Identify Neighbor Frequencies and Cell Information........................................................................ 35
2.9.1.1 LTE Freq/Cell .......................................................................................................................................... 36
2.9.1.1.1 LTE Neigh Freq Table ......................................................................................................................... 36
2.9.1.1.2 LTE Neigh Cell Table ........................................................................................................................... 37
2.9.1.2 TD-S Freq/Cell ........................................................................................................................................ 38
2.9.1.2.1 TD-S Neigh Freq Table ............................................................................................................................ 38
2.9.1.2.2 TD-S Neigh Cell Table ............................................................................................................................. 39
2.9.1.3 GSM Freq/Cell ........................................................................................................................................ 40
2.9.1.3.1 GSM Neigh Freq Table ........................................................................................................................... 40
2.9.1.3.2 GSM Neigh Cell Table ........................................................................................................................ 41
2.9.2 Configure Mobility Parameters ........................................................................................................ 42
2.9.3 Configure Advanced Parameters...................................................................................................... 49
2.9.3.1 X2 ............................................................................................................................................................... 49
v
2.9.3.2 Power Control............................................................................................................................................. 50
2.9.3.3 eNodeB ....................................................................................................................................................... 51
2.9.3.4 GAP ............................................................................................................................................................. 52
2.9.3.5 RRC Status .................................................................................................................................................. 52
2.9.3.6 SON Function Settings ................................................................................................................................ 52
2.9.3.7 Tx and Rx .................................................................................................................................................... 53
2.9.3.8 Random Access........................................................................................................................................... 53
2.9.3.9 Working Mode ............................................................................................................................................ 54
2.9.3.10 Scheduling Algorithm ............................................................................................................................... 54
2.9.3.11 Sync Adjust Parameter ............................................................................................................................. 55
2.9.3.12 Link Activation State Detector .................................................................................................................. 55
2.9.4 Real-World LTE to LTE Handoff Configuration Example ................................................................... 55
2.10 REBOOT .................................................................................................................................................... 59
2.11 LOGOUT .................................................................................................................................................... 59
3. UE GUI ............................................................................................................................................... 60
3.1 COMPUTER REQUIREMENTS ............................................................................................................................ 60
3.2 LAUNCHING THE GUI ..................................................................................................................................... 60
3.3 STATUS........................................................................................................................................................ 62
3.3.1 Overview .......................................................................................................................................... 62
3.3.2 Routes .............................................................................................................................................. 66
3.4 NETWORK ................................................................................................................................................... 67
3.4.1 LAN Settings .................................................................................................................................... 67
3.4.2 WAN Settings .................................................................................................................................. 69
3.4.2.1 WAN Interface ........................................................................................................................................ 69
3.4.2.2 Network Mode ....................................................................................................................................... 69
3.4.2.2.1 NAT .................................................................................................................................................... 69
3.4.2.2.2 Bridge ................................................................................................................................................ 70
3.4.3 WLAN Settings (Indoor UE Model EG2030C only) ........................................................................... 71
3.4.4 Wifidog ........................................................................................................................................... 73
3.4.5 Static Routes ................................................................................................................................... 75
3.4.6 DMZ ................................................................................................................................................ 76
3.5 LTE ............................................................................................................................................................ 77
3.5.1 Connection Mode ............................................................................................................................ 78
3.5.2 Scan Method ................................................................................................................................... 78
3.5.3 APN Management........................................................................................................................... 80
3.5.4 PIN Management ............................................................................................................................ 82
3.6 SECURITY ..................................................................................................................................................... 83
3.6.1 Firewall Settings .............................................................................................................................. 84
3.6.2 MAC Filter ........................................................................................................................................ 85
3.6.3 IP Filter ............................................................................................................................................. 85
3.6.4 URL Filter .......................................................................................................................................... 87
3.6.5 Port Forwarding ............................................................................................................................... 87
3.6.6 Port Triggering ................................................................................................................................. 88
3.6.7 ALG ................................................................................................................................................... 89
3.6.8 UPNP ................................................................................................................................................ 90
3.6.9 Attack Protection ............................................................................................................................. 91
vi
3.7 VPN........................................................................................................................................................... 91
3.7.1 IPSec ................................................................................................................................................ 92
3.7.2 General VPN .................................................................................................................................... 94
3.7.3 L2 .................................................................................................................................................... 96
3.8 SYSTEM ....................................................................................................................................................... 97
3.8.1 NTP.................................................................................................................................................. 97
3.8.2 Account ........................................................................................................................................... 98
3.8.3 WEB Setting .................................................................................................................................... 99
3.8.4 TR-069 ........................................................................................................................................... 100
3.8.5 SNMP ............................................................................................................................................ 101
3.8.6 Restore/Update ............................................................................................................................. 102
3.8.6.1 Restore ................................................................................................................................................. 102
3.8.6.2 Update ................................................................................................................................................. 102
3.8.7 Diagnosis....................................................................................................................................... 103
3.8.7.1 Ping and TraceRoute............................................................................................................................. 103
3.8.7.2 Iperf...................................................................................................................................................... 105
3.8.8 Reboot ........................................................................................................................................... 106
3.9 LOGOUT .................................................................................................................................................... 107
4. CLOUDCORE......................................................................................................................................108
4.1 COMPUTER REQUIREMENTS .......................................................................................................................... 108
4.1.1 Server ............................................................................................................................................. 108
4.1.2 Client .............................................................................................................................................. 108
4.2 GETTING STARTED ....................................................................................................................................... 109
4.2.1 Accessing CloudCore ...................................................................................................................... 109
4.2.2 Overview of CloudCore Users ......................................................................................................... 109
4.2.3 Navigation...................................................................................................................................... 110
4.2.4 Help ................................................................................................................................................ 112
4.3 SYSTEM ..................................................................................................................................................... 112
4.3.1 Operator Info..................................................................................................................................... 113
4.3.2 Security.............................................................................................................................................. 113
4.3.3 Logs ................................................................................................................................................ 116
4.3.4 Security Rule................................................................................................................................... 117
4.4 OMC ....................................................................................................................................................... 118
4.4.1 Dashboard...................................................................................................................................... 119
4.4.2 eNB................................................................................................................................................. 123
4.4.2.1 Monitor .................................................................................................................................................... 123
4.4.2.2 Maintenance ........................................................................................................................................ 135
4.4.2.3 Register ................................................................................................................................................ 139
4.4.2.3.1 Device .............................................................................................................................................. 139
4.4.2.3.2 License............................................................................................................................................. 141
4.4.2.4 Upgrade ............................................................................................................................................... 141
4.4.2.4.1 Overview ......................................................................................................................................... 141
4.4.2.4.2 Upgrade Procedure ......................................................................................................................... 142
4.4.2.4.3 Software Files .................................................................................................................................. 145
4.4.3 CPE ................................................................................................................................................ 146
4.4.3.1 Monitor ................................................................................................................................................ 147
vii
4.4.3.2 Maintenance ........................................................................................................................................ 156
4.4.3.3 Register ................................................................................................................................................ 157
4.4.3.4 Upgrade ............................................................................................................................................... 159
4.4.4 Strategy .......................................................................................................................................... 164
4.4.5 Alarm ............................................................................................................................................. 166
4.4.5.1 View ............................................................................................................................................................. 166
4.4.5.2 Query ........................................................................................................................................................... 169
4.4.5.3 Settings ........................................................................................................................................................ 172
4.4.6 System ............................................................................................................................................ 179
4.4.6.1 Security ................................................................................................................................................ 179
4.4.6.2 OMC Log............................................................................................................................................... 182
4.4.7 Help ................................................................................................................................................ 183
4.5 BOSS ....................................................................................................................................................... 185
4.5.1 Overview ........................................................................................................................................ 185
4.5.2 Subscriber....................................................................................................................................... 186
4.5.2.1 Overview .............................................................................................................................................. 186
4.5.2.2 Operation ............................................................................................................................................. 187
4.5.2.2.1 Active .............................................................................................................................................. 187
4.5.2.2.2 Detail ............................................................................................................................................... 187
4.5.2.2.3 Edit .................................................................................................................................................. 191
4.5.2.2.4 Reset Password ............................................................................................................................... 193
4.5.2.2.5 Delete .............................................................................................................................................. 193
4.5.2.3 Add Individual Subscriber .................................................................................................................... 193
4.5.2.4 Bulk Import Subscribers ....................................................................................................................... 195
4.5.3 Billing ............................................................................................................................................ 197
4.5.4 Network ......................................................................................................................................... 197
4.5.5 System ............................................................................................................................................ 200
4.5.5.1 Service Plans ............................................................................................................................................. 201
4.5.5.2 Security ................................................................................................................................................ 203
4.5.5.2.1 User Account ................................................................................................................................... 204
4.5.5.2.2 User Group ...................................................................................................................................... 204
4.5.5.2.3 Role Set ........................................................................................................................................... 205
4.5.5.3 Logs .......................................................................................................................................................... 207
4.5.6 Help ................................................................................................................................................ 207
APPENDIX A: MML COMMANDS................................................................................................................208
APPENDIX B: ABBREVIATIONS AND ACRONYMS.........................................................................................209
APPENDIX C: FAQS ....................................................................................................................................233
APPENDIX D: CLOUDKEY............................................................................................................................234
viii
List of Figures
FIGURE 1-1: EXAMPLE BAICELLS ARCHITECTURE ................................................................................................................ 1
FIGURE 1-2: SAMPLE UE GUI WINDOW ......................................................................................................................... 2
FIGURE 1-3: UE & ENB GUI MENU TREES ...................................................................................................................... 2
FIGURE 1-4: SAMPLE ENB GUI WINDOW ........................................................................................................................ 3
FIGURE 1-5: SAMPLE CLOUDCORE OMC WINDOW ........................................................................................................... 4
FIGURE 1-6: CLOUDCORE GUI MENU TREES .................................................................................................................... 4
FIGURE 2-1: INTERNET PROTOCOL VERSION (TCP/IPV4) .................................................................................................... 5
FIGURE 2-2: ENB GUI LOGIN ........................................................................................................................................ 6
FIGURE 2-3: ENB GUI MENUS ...................................................................................................................................... 7
FIGURE 2-4: INITIAL CONFIGURATION FLOW ..................................................................................................................... 8
FIGURE 2-5: BASIC INFO (STANDARD ENB) ...................................................................................................................... 9
FIGURE 2-6: BASIC INFO (HALOB-ENABLED ENB) ............................................................................................................. 9
FIGURE 2-7: QUICK SETTING (STANDARD ENB) ............................................................................................................... 12
FIGURE 2-8: QUICK SETTING (HALOB ENB) ................................................................................................................... 13
FIGURE 2-9: NTP ...................................................................................................................................................... 15
FIGURE 2-10: UPGRADE ............................................................................................................................................. 16
FIGURE 2-11: BACKUP ............................................................................................................................................... 17
FIGURE 2-12: PASSWORD WINDOW ............................................................................................................................. 18
FIGURE 2-13: NETWORK – STANDARD & HALOB ENBS .................................................................................................... 19
FIGURE 2-14: INTERNET / WAN .................................................................................................................................. 20
FIGURE 2-15: DHCP ................................................................................................................................................. 21
FIGURE 2-16: VLAN ................................................................................................................................................. 22
FIGURE 2-17: IPSEC/MME POOL................................................................................................................................ 23
FIGURE 2-18: TUNNEL CONFIGURE > BASIC SETTING ....................................................................................................... 24
FIGURE 2-19: TUNNEL CONFIGURE > ADVANCE SETTING .................................................................................................. 25
FIGURE 2-20: LGW SETTING (BRIDGE, NAT, & ROUTER MODES) ...................................................................................... 27
FIGURE 2-21: CERTSTORE ........................................................................................................................................... 28
FIGURE 2-22: STATIC ROUTING .................................................................................................................................... 29
FIGURE 2-23: BTS SETTING - STANDARD & HALOB ENBS ................................................................................................. 29
FIGURE 2-24: SECURITY SETTING ................................................................................................................................. 30
FIGURE 2-25: MANAGEMENT SERVER ........................................................................................................................... 31
FIGURE 2-26: SYNC SETTING ....................................................................................................................................... 31
FIGURE 2-27: HALOB SETTING .................................................................................................................................... 33
FIGURE 2-28: LICENSE MANAGEMENT .......................................................................................................................... 34
FIGURE 2-29: LTE – STANDARD & HALOB ENBS ............................................................................................................. 35
FIGURE 2-30: NEIGH FREQ TABLE ................................................................................................................................ 36
FIGURE 2-31: LTE FREQ/CELL > NEIGH CELL TABLE SETTINGS ........................................................................................... 37
FIGURE 2-32: TD-S FREQ/CELL > NEIGH FREQ TABLE SETTINGS ........................................................................................ 38
FIGURE 2-33: TD-S FREQ/CELL > NEIGH CELL TABLE SETTINGS ......................................................................................... 40
FIGURE 2-34: GSM FREQ/CELL > NEIGH FREQ TABLE SETTINGS ........................................................................................ 41
FIGURE 2-35: GSM FREQ/CELL > NEIGH CELL SETTINGS .................................................................................................. 42
FIGURE 2-36: HANDOFF ............................................................................................................................................. 43
FIGURE 2-37: MOBILITY PARAMETERS .......................................................................................................................... 44
ix
FIGURE 2-38: A1, A2, A3, AND A5 EVENT THRESHOLDS.................................................................................................. 45
FIGURE 2-39: B2 EVENT THRESHOLD ............................................................................................................................ 46
FIGURE 2-40: MEASUREMENT CONTROL PARAMETERS..................................................................................................... 47
FIGURE 2-41: CELL SELECTION AND CELL RESELECTION PARAMETERS .................................................................................. 48
FIGURE 2-42: ADVANCED PARAMETERS SUB-MENUS ....................................................................................................... 49
FIGURE 2-43 X2 PARAMETER ...................................................................................................................................... 50
FIGURE 2-44: POWER CONTROL PARAMETERS ................................................................................................................ 50
FIGURE 2-45: ENODEB SETTINGS ................................................................................................................................. 51
FIGURE 2-46: GAP SETTINGS ...................................................................................................................................... 52
FIGURE 2-47: RRC STATUS PARAMETERS ....................................................................................................................... 52
FIGURE 2-48: SON FUNCTION SETTINGS ....................................................................................................................... 53
FIGURE 2-49: TX AND RX SETTINGS .............................................................................................................................. 53
FIGURE 2-50: RANDOM ACCESS PARAMETERS ................................................................................................................ 53
FIGURE 2-51: WORKING MODE ................................................................................................................................... 54
FIGURE 2-52: SCHEDULING ALGORITHM PARAMETERS ..................................................................................................... 54
FIGURE 2-53: SYNC ADJUST PARAMETERS...................................................................................................................... 55
FIGURE 2-54: LINK ACTIVATION STATE DETECTOR PARAMETERS ......................................................................................... 55
FIGURE 2-55: LTE FREQ/CELL > NEIGH FREQ AND NEIGH CELL TABLE SETTINGS ................................................................... 56
FIGURE 2-56: FLOWCHART OF HANDOFF EVENT THRESHOLDS ........................................................................................... 57
FIGURE 2-57: A1 THRESHOLD ..................................................................................................................................... 57
FIGURE 2-61: X2 HANDOVER ...................................................................................................................................... 58
FIGURE 2-62: REBOOT ACTION .................................................................................................................................... 59
FIGURE 2-63: LOGOUT ACTION.................................................................................................................................... 59
FIGURE 3-1: UE LAN INTERFACE EXAMPLE .................................................................................................................... 60
FIGURE 3-2: UE GUI LOGIN ........................................................................................................................................ 61
FIGURE 3-3: UE GUI MAIN MENU .............................................................................................................................. 61
FIGURE 3-4: CHANGE PASSWORD ................................................................................................................................. 62
FIGURE 3-5: OVERVIEW FIELDS (1 OF 3) ........................................................................................................................ 62
FIGURE 3-8: ROUTES ................................................................................................................................................. 66
FIGURE 3-9: NETWORK SUB-MENUS ............................................................................................................................ 67
FIGURE 3-10: LAN SETTINGS (1 OF 2) .......................................................................................................................... 68
FIGURE 3-11: LAN SETTINGS (2 OF 2) .......................................................................................................................... 68
FIGURE 3-12: NETWORK MODE ................................................................................................................................... 70
FIGURE 3-13: BRIDGE MODE ...................................................................................................................................... 70
FIGURE 3-14: WIRELESS OVERVIEW.............................................................................................................................. 71
FIGURE 3-15: SSID SETTINGS...................................................................................................................................... 72
FIGURE 3-16: L2 NETWORK EXAMPLE........................................................................................................................... 73
FIGURE 3-17: BASIC SETTINGS ..................................................................................................................................... 74
FIGURE 3-18: WHITELIST ............................................................................................................................................ 74
FIGURE 3-19: ADVANCED SETTINGS .............................................................................................................................. 75
FIGURE 3-20: STATIC ROUTES ...................................................................................................................................... 76
x
FIGURE 3-21: CONFIGURE STATIC ROUTES ..................................................................................................................... 76
FIGURE 3-22: DMZ METHODS .................................................................................................................................... 77
FIGURE 3-23: DMZ................................................................................................................................................... 77
FIGURE 3-24: LTE ..................................................................................................................................................... 78
FIGURE 3-25: CONNECTION MODE............................................................................................................................... 78
FIGURE 3-26: SCAN METHOD ...................................................................................................................................... 79
FIGURE 3-27: FREQUENCY LOCK .................................................................................................................................. 79
FIGURE 3-28: PCI LOCK ............................................................................................................................................. 80
FIGURE 3-29: APN MANAGEMENT .............................................................................................................................. 81
FIGURE 3-30: PIN MANAGEMENT ............................................................................................................................... 82
FIGURE 3-31: MODIFY PIN ......................................................................................................................................... 83
FIGURE 3-32: SECURITY.............................................................................................................................................. 84
FIGURE 3-33 FIREWALL SETTINGS ................................................................................................................................. 84
FIGURE 3-34: MAC FILTER > ADD LIST ......................................................................................................................... 85
FIGURE 3-35: IP FILTER .............................................................................................................................................. 86
FIGURE 3-36: URL FILTER........................................................................................................................................... 87
FIGURE 3-37: PORT FORWARDING ............................................................................................................................... 88
FIGURE 3-38: PORT TRIGGERING.................................................................................................................................. 89
FIGURE 3-39: ALG .................................................................................................................................................... 90
FIGURE 3-40: UPNP ................................................................................................................................................. 90
FIGURE 3-41: ATTACK PROTECTION .............................................................................................................................. 91
FIGURE 3-42: VPN > IPSEC ........................................................................................................................................ 92
FIGURE 3-43: ADVANCE SETTINGS .......................................................................................................................... 93
FIGURE 3-44: GENERAL VPN > L2TP ........................................................................................................................... 94
FIGURE 3-45: GENERAL VPN > PPTP ........................................................................................................................... 95
FIGURE 3-46: GENERAL VPN > GRE ............................................................................................................................ 96
FIGURE 3-47: SET UP L2 ............................................................................................................................................ 97
FIGURE 3-48: APN STATUS ......................................................................................................................................... 97
FIGURE 3-49: NTP .................................................................................................................................................... 98
FIGURE 3-50: ACCOUNT ............................................................................................................................................. 98
FIGURE 3-51: WEB SETTING....................................................................................................................................... 99
FIGURE 3-52: TR-069 ............................................................................................................................................. 100
FIGURE 3-53: SNMP .............................................................................................................................................. 101
FIGURE 3-54: RESTORE/UPDATE ................................................................................................................................ 102
FIGURE 3-55: DIAGNOSIS ......................................................................................................................................... 103
FIGURE 3-56: PING ................................................................................................................................................. 104
FIGURE 3-57: TRACEROUTE ...................................................................................................................................... 104
FIGURE 3-58: IPERF ................................................................................................................................................. 105
FIGURE 3-59: REBOOT ............................................................................................................................................. 106
FIGURE 3-60: LOGOUT ............................................................................................................................................. 107
FIGURE 4-1: CLOUDCORE SIGN UP AND LOGIN PAGE...................................................................................................... 109
FIGURE 4-2: CLOUDCORE USERS ................................................................................................................................ 110
FIGURE 4-3: CLOUDCORE WEB PAGE .......................................................................................................................... 110
FIGURE 4-4: CLOUDCORE NAVIGATION PANE ............................................................................................................... 110
FIGURE 4-5: CLOUDCORE WELCOME MENU ................................................................................................................ 111
FIGURE 4-6: CHANGE PASSWORD ............................................................................................................................... 111
xi
FIGURE 4-7: LOCK SCREEN ........................................................................................................................................ 111
FIGURE 4-8: OMC HELP .......................................................................................................................................... 112
FIGURE 4-9: CLOUDCORE SYSTEM MENU .................................................................................................................... 112
FIGURE 4-10: OPERATOR INFO................................................................................................................................... 113
FIGURE 4-11: USER MANAGEMENT ............................................................................................................................ 113
FIGURE 4-12: ADVANCE QUERY ................................................................................................................................. 114
FIGURE 4-13: OPERATION ......................................................................................................................................... 114
FIGURE 4-14: OPERATION > MODIFY .......................................................................................................................... 115
FIGURE 4-15: OPERATION > RESET PASSWORD ............................................................................................................. 115
FIGURE 4-16: RESET PASSWORD MESSAGE .................................................................................................................. 115
FIGURE 4-17: ADD USER .......................................................................................................................................... 116
FIGURE 4-18: LOGS ................................................................................................................................................. 117
FIGURE 4-19: SECURITY RULE (1 OF 2) ........................................................................................................................ 117
FIGURE 4-20: SECURITY RULE (2 OF 2) ........................................................................................................................ 118
FIGURE 4-21: OMC MENU ...................................................................................................................................... 118
FIGURE 4-22: DASHBOARD (1 OF 7) ........................................................................................................................... 119
FIGURE 4-23: DASHBOARD (2 OF 7) - ALARMS ............................................................................................................. 120
FIGURE 4-24: DASHBOARD (3 OF 7) - STATISTICS .......................................................................................................... 120
FIGURE 4-25: DASHBOARD (4 OF 7) - ENBS ................................................................................................................. 121
FIGURE 4-26: DASHBOARD (5 OF 7) – PERFORMANCE – THROUGHPUT & PRB UTILIZATION ................................................. 121
FIGURE 4-27: DASHBOARD (6 OF 7) – PERFORMANCE – UE COUNT ................................................................................. 122
FIGURE 4-28: DASHBOARD (7 OF 7) – CPE > MONITOR................................................................................................. 122
FIGURE 4-29: ENB MENU ........................................................................................................................................ 123
FIGURE 4-30: MONITOR ........................................................................................................................................... 123
FIGURE 4-31: DISPLAY ............................................................................................................................................. 124
FIGURE 4-32: MONITOR (1 OF 3) .............................................................................................................................. 124
FIGURE 4-35: FILTER ................................................................................................................................................ 125
FIGURE 4-37: INFORMATION > STATISTICS .................................................................................................................... 127
FIGURE 4-38: STATISTICS .......................................................................................................................................... 128
FIGURE 4-39: ALARM .............................................................................................................................................. 128
FIGURE 4-40: DEVICE REPORT LOG............................................................................................................................. 129
FIGURE 4-41: SETTINGS > WIRELESS (1 OF 2)............................................................................................................... 129
FIGURE 4-42: SETTINGS > WIRELESS (2 OF 2)............................................................................................................... 130
FIGURE 4-43: PB, BANDWIDTH, SFASSIGNMENT, SPECIALSFPATTERNS ............................................................................. 131
FIGURE 4-44: NETWORK SETTINGS ............................................................................................................................. 131
FIGURE 4-45: ICIC .................................................................................................................................................. 132
FIGURE 4-46: NTP .................................................................................................................................................. 132
FIGURE 4-47: OPERATION > OPERATION...................................................................................................................... 133
FIGURE 4-48: LOGS ................................................................................................................................................. 133
FIGURE 4-49: RESET PASSWORD (1 OF 3) .................................................................................................................... 134
FIGURE 4-52: MAINTENANCE .................................................................................................................................... 135
xii
FIGURE 4-54: NEW TASK .......................................................................................................................................... 136
FIGURE 4-57: DEVICE LOG ........................................................................................................................................ 137
FIGURE 4-58: DEVICE EXCEPTION LOG: ....................................................................................................................... 138
FIGURE 4-59: ADD NEW TASK ................................................................................................................................... 138
FIGURE 4-60: REGISTER............................................................................................................................................ 139
FIGURE 4-61: VIEW DEVICE GROUP............................................................................................................................ 139
FIGURE 4-62: ADD NEW DEVICE GROUP ..................................................................................................................... 140
FIGURE 4-63: ADD ENB ........................................................................................................................................... 140
FIGURE 4-64: IMPORT ENB....................................................................................................................................... 141
FIGURE 4-65: LICENSE ............................................................................................................................................. 141
FIGURE 4-66: UPGRADE ........................................................................................................................................... 141
FIGURE 4-68: VIEW ................................................................................................................................................. 142
FIGURE 4-69: ADD NEW UPGRADE/ROLLBACK TASK...................................................................................................... 143
FIGURE 4-70: NEW UPGRADE TASK ............................................................................................................................ 143
FIGURE 4-71: EXECUTE TYPE ..................................................................................................................................... 144
FIGURE 4-72: SELECT UPGRADE FILE........................................................................................................................... 144
FIGURE 4-73: NEW UPGRADE TASK ............................................................................................................................ 144
FIGURE 4-74: OPERATION > AWAITING START > ACTIVE ................................................................................................. 145
FIGURE 4-75: ENB > MONITOR ................................................................................................................................. 145
FIGURE 4-76: SOFTWARE FILES .................................................................................................................................. 146
FIGURE 4-77: SOFTWARE FILES - VIEW ........................................................................................................................ 146
FIGURE 4-78: CPE .................................................................................................................................................. 147
FIGURE 4-79: CPE (1 OF 2) ...................................................................................................................................... 147
FIGURE 4-80: CPE (2 OF 2) ...................................................................................................................................... 148
FIGURE 4-81: DISPLAY ............................................................................................................................................. 148
FIGURE 4-83: INFORMATION ..................................................................................................................................... 149
FIGURE 4-84: SETTINGS ........................................................................................................................................... 150
FIGURE 4-85: SYNCHRONIZE ..................................................................................................................................... 150
FIGURE 4-86: FREQUENCY LOCK ................................................................................................................................ 151
FIGURE 4-87: REBOOT ............................................................................................................................................. 151
FIGURE 4-88: HISTORY > UL/DL MCS ....................................................................................................................... 152
FIGURE 4-89: RSRP1 AND RSRP2 ............................................................................................................................. 153
FIGURE 4-90: CINR1 AND CINR2 ............................................................................................................................. 154
FIGURE 4-91: SINR ................................................................................................................................................. 155
FIGURE 4-92: DL AND UL THROUGHPUT ..................................................................................................................... 155
FIGURE 4-93: REBOOT ............................................................................................................................................. 156
FIGURE 4-94: CREATE REBOOT TASK ........................................................................................................................... 156
FIGURE 4-95: REBOOT WARNING .............................................................................................................................. 157
FIGURE 4-96: REGISTER > DEVICE .............................................................................................................................. 157
FIGURE 4-97: VIEW ................................................................................................................................................. 157
FIGURE 4-98: MODIFY DEVICE GROUP ........................................................................................................................ 158
xiii
FIGURE 4-99: ADD GROUP ....................................................................................................................................... 158
FIGURE 4-100: MOVE TO DEVICE GROUP .................................................................................................................... 159
FIGURE 4-101: ADD CPE ......................................................................................................................................... 159
FIGURE 4-102: UPGRADE > SOFTWARE ....................................................................................................................... 160
FIGURE 4-103: UPGRADE TYPE .................................................................................................................................. 160
FIGURE 4-104: UPGRADE > SOFTWARE ....................................................................................................................... 161
FIGURE 4-105: NEW UPGRADE TASK (1 OF 3).............................................................................................................. 161
FIGURE 4-106: EXECUTE TYPE ................................................................................................................................... 162
FIGURE 4-107: NEW UPGRADE TASK .......................................................................................................................... 162
FIGURE 4-108: NEW UPGRADE TASK .......................................................................................................................... 163
FIGURE 4-109: OPERATION > AWAITING START > ACTIVE ............................................................................................... 163
FIGURE 4-110: CPE > MONITOR (SOFTWARE VERSION) ................................................................................................. 163
FIGURE 4-111: PCI LOCK - ENB ................................................................................................................................ 164
FIGURE 4-112: PCI LOCK - CPE................................................................................................................................. 164
FIGURE 4-113: ADD NEW TASK (1 OF 3) ..................................................................................................................... 165
FIGURE 4-116: DASHBOARD - ALARMS ....................................................................................................................... 166
FIGURE 4-117: ALARM SUB-MENU ............................................................................................................................ 166
FIGURE 4-118: SELECT TEMPLATE .............................................................................................................................. 167
FIGURE 4-119: ADD TEMPLATE ................................................................................................................................. 168
FIGURE 4-120: ADD TEMPLATE FIELDS ........................................................................................................................ 168
FIGURE 4-121: QUERY ............................................................................................................................................. 169
FIGURE 4-122: ALARM DETAILS ................................................................................................................................. 169
FIGURE 4-123: ALARM CONFIRM AND ALARM CLEAR .................................................................................................... 170
FIGURE 4-124: EXPORT ............................................................................................................................................ 171
FIGURE 4-125: FILTER .............................................................................................................................................. 171
FIGURE 4-126: ADVANCED QUERY (1 OF 2) ................................................................................................................. 172
FIGURE 4-127: ADVANCED QUERY (2 OF 2) ................................................................................................................. 172
FIGURE 4-128: ALARM > SETTINGS ............................................................................................................................ 173
FIGURE 4-129: ALARM FILTER > SELECTED ENODEB ...................................................................................................... 173
FIGURE 4-130: ALARM TYPE ..................................................................................................................................... 174
FIGURE 4-131: SEVERITY .......................................................................................................................................... 174
FIGURE 4-132: EVENT TIME ...................................................................................................................................... 175
FIGURE 4-133: ENABLE FILTER TEMPLATE .................................................................................................................... 175
FIGURE 4-134: + NEW ALARM CONFIRM TEMPLATE ...................................................................................................... 176
FIGURE 4-135: VIEW CONFIG.................................................................................................................................... 177
FIGURE 4-136: ADD NEW TEMPLATE .......................................................................................................................... 177
FIGURE 4-137: LIBRARY ........................................................................................................................................... 178
FIGURE 4-138: NOTIFICATION ................................................................................................................................... 178
FIGURE 4-139: SYSTEM ............................................................................................................................................ 179
FIGURE 4-140: SYSTEM > SECURITY > USER ................................................................................................................. 180
FIGURE 4-141: USER GROUP .................................................................................................................................... 180
FIGURE 4-142: + ADD USER GROUP ........................................................................................................................... 181
FIGURE 4-143: ROLESET .......................................................................................................................................... 181
FIGURE 4-144: + ADD ROLE ..................................................................................................................................... 182
xiv
FIGURE 4-145: READ/WRITE FUNCTIONS .................................................................................................................... 182
FIGURE 4-146: OMC LOG > OPERATION LOG .............................................................................................................. 183
FIGURE 4-147: SECURITY LOG ................................................................................................................................... 183
FIGURE 4-148: SYSTEM LOG ..................................................................................................................................... 183
FIGURE 4-149: HELP ............................................................................................................................................... 184
FIGURE 4-150: BOSS NETWORK ARCHITECTURE .......................................................................................................... 185
FIGURE 4-151: BOSS MENU .................................................................................................................................... 186
FIGURE 4-152: SUBSCRIBER ...................................................................................................................................... 186
FIGURE 4-153: OPERATION ....................................................................................................................................... 187
FIGURE 4-154: ACTIVE............................................................................................................................................. 187
FIGURE 4-155: VIEW > OVERVIEW (1 OF 2)................................................................................................................. 188
FIGURE 4-156: VIEW > OVERVIEW (2 OF 2)................................................................................................................. 188
FIGURE 4-157: RECHARGE ........................................................................................................................................ 189
FIGURE 4-158: VIEW > CHANGE SIM CARD................................................................................................................. 189
FIGURE 4-159: SERVICE PLAN (1 OF 2) ....................................................................................................................... 190
FIGURE 4-160: SERVICE PLAN (2 OF 2) ....................................................................................................................... 190
FIGURE 4-161: INVOICES .......................................................................................................................................... 191
FIGURE 4-162: RECHARGE ........................................................................................................................................ 191
FIGURE 4-163: EDIT (1 OF 2) .................................................................................................................................... 192
FIGURE 4-164: EDIT (2 OF 2) .................................................................................................................................... 192
FIGURE 4-165: RESET PASSWORD .............................................................................................................................. 193
FIGURE 4-166: DELETE ............................................................................................................................................ 193
FIGURE 4-167: + ADD SUBSCRIBER (1 OF 3) ................................................................................................................ 194
FIGURE 4-170: IMPORT............................................................................................................................................ 195
FIGURE 4-171: BULK (1 OF 2) ................................................................................................................................... 196
FIGURE 4-172: BULK (2 OF 2) ................................................................................................................................... 196
FIGURE 4-173: OPERATOR INVOICE ............................................................................................................................ 197
FIGURE 4-174: NETWORK MENU............................................................................................................................... 197
FIGURE 4-175: SIM CARD ........................................................................................................................................ 198
FIGURE 4-176: IMPORT............................................................................................................................................ 198
FIGURE 4-177: ACTIVE CODE .................................................................................................................................... 198
FIGURE 4-178: FILE ................................................................................................................................................. 199
FIGURE 4-179: EXPORT TEMPLATE ............................................................................................................................. 199
FIGURE 4-180: RECORDS .......................................................................................................................................... 200
FIGURE 4-181: SYSTEM MENU .................................................................................................................................. 200
FIGURE 4-182: SERVICE PLANS (1 OF 2) ...................................................................................................................... 201
FIGURE 4-183: SERVICE PLANS (2 OF 2) ...................................................................................................................... 201
FIGURE 4-184: ADD SERVICE PLAN (1 OF 2) ................................................................................................................ 202
FIGURE 4-185: ADD SERVICE PLAN (2 OF 2) ................................................................................................................ 202
FIGURE 4-186: ENABLE SERVICE PLAN ........................................................................................................................ 203
FIGURE 4-187: SECURITY.......................................................................................................................................... 203
FIGURE 4-188: USER ACCOUNT ................................................................................................................................. 204
FIGURE 4-189: USER GROUP .................................................................................................................................... 204
FIGURE 4-190: VIEW USER GROUP ............................................................................................................................ 205
xv
FIGURE 4-191: + ADD USER GROUP ........................................................................................................................... 205
FIGURE 4-192: ROLE SET ......................................................................................................................................... 206
FIGURE 4-193: + ADD NEW ROLE SET ........................................................................................................................ 206
FIGURE 4-194: LOGS ............................................................................................................................................... 207
FIGURE 4-195: HELP ............................................................................................................................................... 207
List of Tables
TABLE 2-1: COMPUTER REQUIREMENTS .......................................................................................................................... 5
TABLE 2-2: BASIC INFO FIELDS ..................................................................................................................................... 10
TABLE 2-3: STATUS INFO FIELDS ................................................................................................................................... 10
TABLE 2-4: UE STATUS FIELDS ..................................................................................................................................... 11
TABLE 2-5: QUICK SETTING ......................................................................................................................................... 13
TABLE 2-6: NTP ....................................................................................................................................................... 15
TABLE 2-7: INTERNET / WAN...................................................................................................................................... 20
TABLE 2-8: TUNNEL CONFIGURE > BASIC SETTING FIELDS ................................................................................................. 24
TABLE 2-9: TUNNEL CONFIGURE > ADVANCE SETTING ...................................................................................................... 25
TABLE 2-10: LTE NEIGH FREQ SETTINGS........................................................................................................................ 36
TABLE 2-11: LTE NEIGH CELL TABLE SETTINGS ............................................................................................................... 37
TABLE 2-12: TD-S NEIGH FREQ TABLE SETTINGS ............................................................................................................ 39
TABLE 2-13: TD-S CELL SETTING FIELDS ........................................................................................................................ 40
TABLE 2-14: GSM FREQ/CELL > NEIGH FREQ TABLE SETTINGS ......................................................................................... 41
TABLE 2-15: GSM FREQ/CELL > NEIGH CELL SETTINGS ................................................................................................... 42
TABLE 2-16: A1, A2, A3, AND A5 EVENT THRESHOLD FIELDS ........................................................................................... 45
TABLE 2-17: B2 EVENT THRESHOLD FIELDS .................................................................................................................... 46
TABLE 2-18: MEASUREMENT CONTROL FIELDS ............................................................................................................... 47
TABLE 2-19: CELL SELECTION AND CELL RESELECTION FIELDS ............................................................................................ 48
TABLE 2-20: POWER CONTROL PARAMETERS ................................................................................................................. 50
TABLE 2-21: RRC STATUS PARAMETERS ........................................................................................................................ 52
TABLE 2-22: SON FUNCTIONAL PARAMETERS ................................................................................................................ 53
TABLE 2-23: RANDOM ACCESS PARAMETERS.................................................................................................................. 53
TABLE 2-24: SYNC ADJUST PARAMETERS ....................................................................................................................... 55
TABLE 2-25: LINK ACTIVATION STATE DETECTOR PARAMETERS ........................................................................................... 55
TABLE 3-1: COMPUTER REQUIREMENTS ........................................................................................................................ 60
TABLE 3-2: OVERVIEW FIELDS...................................................................................................................................... 63
TABLE 3-3: ROUTES ................................................................................................................................................... 66
TABLE 3-4: LAN SETTINGS .......................................................................................................................................... 68
TABLE 3-5: SSID ....................................................................................................................................................... 72
TABLE 3-6: DMZ ...................................................................................................................................................... 77
TABLE 3-7: APN MANAGEMENT .................................................................................................................................. 81
TABLE 3-8: MAC FILTER ............................................................................................................................................. 85
TABLE 3-9: IP FILTER.................................................................................................................................................. 86
TABLE 3-10: PORT FORWARDING ................................................................................................................................. 88
TABLE 3-11: VPN > IPSEC ......................................................................................................................................... 92
TABLE 3-12: ADVANCE IPSEC SETTINGS ........................................................................................................................ 93
xvi
TABLE 3-13: GENERAL VPN > L2TP............................................................................................................................. 94
TABLE 3-14: GENERAL VPN > PPTP ............................................................................................................................ 95
TABLE 3-15: GENERAL VPN > GRE .............................................................................................................................. 96
TABLE 3-16: WEB SETTING ........................................................................................................................................ 99
TABLE 3-17: TR069 SETTINGS .................................................................................................................................. 100
TABLE 3-18: SNMP ................................................................................................................................................ 101
TABLE 3-19: PING AND TRACEROUTE.......................................................................................................................... 104
TABLE 3-20: IPERF .................................................................................................................................................. 106
TABLE 4-1: SERVER REQUIREMENTS ............................................................................................................................ 108
TABLE 4-2: CLIENT REQUIREMENTS ............................................................................................................................ 108
TABLE 4-3: ENB MONITOR FIELDS.............................................................................................................................. 126
TABLE 4-4: WIRELESS SETTINGS ................................................................................................................................. 130
TABLE 4-5: NTP SETTINGS ........................................................................................................................................ 133
TABLE 4-6: ALARM DETAIL ........................................................................................................................................ 170
xvii
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 Long-Term Evolution (LTE) Frequency Division Duplexing (FDD) or Time-Division Duplexing (TDD)
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:

• User Equipment (UE), also referred to as Customer Premise Equipment (CPE), which resides at
the subscriber’s location;
• Cell site equipment, which connects wireless UE to the internet and 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
• CloudCore and other software applications for configuring and managing the Baicells network
components.
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. Currently CloudCore includes
two service modules: Operations Management Console (OMC) and Business Operations Support
System (BOSS). Additional Evolved Packet Core (EPC) functions are planned. Figure 1-1 illustrates a
general Baicells system architecture. The photo is showing a Nova 1W eNB.
Figure 1-1: Example Baicells Architecture
1
The software applications include a UE Graphical User Interface (GUI) and an eNB GUI, which run on
each piece of equipment. The GUI software applications typically are used to communicate with a
specific device, i.e., a single UE or a single eNB. Each UE and eNB 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
UE or eNB during initial installation or troubleshooting, or to improve the equipment’s performance.
A sample window from the UE GUI is presented in Figure 1-2. Figure 1-3 shows a high-level view of the
UE and eNB GUI menu trees. A sample window from the eNB GUI is presented in Figure 1-4.
Figure 1-2: Sample UE GUI Window
Figure 1-3: UE & eNB GUI Menu Trees
NOTE: The GUI trees may vary by software version, operating mode, and hardware model.
2
Figure 1-4: Sample eNB GUI Window
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 UE GUI, eNB 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 trees.
3
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.
4
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+, Internet Explorer 7.0+, Mozilla Firefox 3.6+
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. 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-1.
Figure 2-1: Internet Protocol Version (TCP/IPV4)
5
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-2.
The password may be changed after you first log in.
NOTE: If you are using a two-carrier eNB and wish to set it up in dual carrier (split sector) mode,
you will need to log in to Cell 1 using 192.168.150.1 and log in to Cell 2 using 192.168.150.2.
Please refer to the Baicells Dual Carrier Configuration Quick Guide for further information
related to dual carrier software differences.
Figure 2-2: eNB GUI Login
After you log in, the main menus are shown in the left navigation pane (Figure 2-3). 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. Notice that there are
menu differences between a standard eNB GUI and a HaloB eNB GUI.
NOTE: The eNB GUI menu varies according to the eNB operation mode (standard or HaloB),
software version, and hardware model. HaloB is an optional, value-added operator feature.
This document focuses on the standard eNB GUI, and at times points out differences seen
when the eNB is operating in HaloB mode. Please refer to the Baicells HaloB User Guide for
more details about how to enable HaloB.
6
Figure 2-3: eNB GUI Menus
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.
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-4.
7
Refer to the Getting Started BaiTip on the Baicells website:
https://na.baicells.com/getting-started/
Figure 2-4: 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 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-5 (showing full scroll-down view). A few fields are slightly different when the eNB
is operating in HaloB mode (Figure 2-6). The fields collectively provide a quick overview about the eNB
and its operational status. The Basic Info fields are described in Table 2-2.
8
Figure 2-5: Basic Info (Standard eNB)
Figure 2-6: Basic Info (HaloB-Enabled eNB)
9
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 identifier for the eNB
MAC Data Link layer Media Access Control address for the eNB
The Status Info fields provide high-level information on operation and connectivity. The fields are
described in Table 2-3.
Table 2-3: Status Info Fields

Link Speed Negotiated Data rate negotiated between the eNB and the WAN interface
HaloB Status This field appears only in an eNB operating in HaloB mode, as described in the
Baicells HaloB User Guide. As part of the implementation procedure for the
HaloB feature, the operator sets this field to Enable to activate the feature.
Cell Status Active or Inactive. When the eNB is operating (transmitting and receiving
signals), the status will be active. If not, the status will be reported as inactive.
MME Status Mobility Management Entity status is connected or 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 Baicells Operations Management Console status is connected or
unconnected to the eNB.
IPSec Status The Internet Protocol Security 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. Note that this field does not appear when the eNB is
operating in HaloB mode.
OTA Sync Status Over-the-Air 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.
NOTE: Although it appears as a sync option in the GUI, 1588

has not been tested and is not supported currently.
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 a percentage. 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
10
of erroneous data blocks received to the total number of blocks sent.
Expressed as a percentage. BLER is a measure of how successful a data
transmission is over the air at the Physical/MAC layer level.
*NOTE: The BLER fields are not visible in a Nova-243 eNB running
BaiStation_V1.1.0.100.11 software.
The UE Status fields provide a synopsis of the UEs connected to the eNB. The UE fields are described
in Table 2-4.
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.
LGW MAC The MAC address of the local area network gateway.
NOTE: This field is not visible on a Nova-243 eNB running

BaiStation_V1.1.0.100.11 software.
IP Internet Protocol address for the eNB

PORT Port number assigned to the UE to allow remote logins. For example, type in
the eNB IP: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-30 dB.
dlcqi Downlink Channel Quality Indicator indicates how good or bad the
communication channel quality is for data being transmitted from the eNB to
the UE. CQI is a combination of SNR, SINR, and SNDR. Value range is 1-15.
ulmcs Uplink Modulation and Coding Scheme is a numerical index based on
Orthogonal Frequency Division Multiplexing (OFDM) that represents the
maximum data rate the UE can achieve when transmitting data over-the-air to
the eNB. The MCS index value comprises several variables, including channel
width, modulation type, coding rate, and spatial streams.
dlmcs Downlink Modulation and Coding Scheme – see description for “ulmcs” above,
which in this case pertains to the downlink
txPower Transmit (Tx) power is the amount of radio frequency (RF) power (in Watts) that
the UE produces. Unit of measurement is dBm. Range is -8 to +23 dBm.
Uplink BLER Block Error Ratio (BLER) is a measure of how successful a data transmission is
over the air at the Physical/MAC layer level. Uplink BLER represents a ratio of
the number of erroneous data blocks received to the total number of blocks
sent from the UE to the eNB. NOTE: The BLER fields are not visible in a Nova-
11
243 eNB running BaiStation_V1.1.0.100.11 software.
Downlink BLER Block Error Ratio (BLER) is a measure of how successful a data transmission is
over the air at the Physical/MAC layer level. Downlink BLER represents a ratio of
the number of erroneous data blocks received to the total number of blocks
sent from the eNB to the UE. NOTE: The BLER fields are not visible in a Nova-
243 eNB running BaiStation_V1.1.0.100.11 software.
pathloss This field displays for HaloB-enabled eNBs only. It reports the reduction in
power density (attenuation) as the wireless signal propagates through space.
The pathloss value impacts the overall RF link budget. An RF link budget is an
accounting of all the gains and losses from the transmitter, through the medium
to the receiver.
2.5.2 Quick Setting

The Quick Setting fields must be configured to determine the cell parameters and transmission
information. The Quick Setting window for a standard eNB is shown in Figure 2-7, and for a HaloB-
enabled eNB in Figure 2-8. Note that for a HaloB eNB, the MME IP field is replaced with the
“Transmission interface binding” field. 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.
NOTE: For newer generation eNBs, to change the WAN interface type from fiber to copper, use
the command line interface (CLI):
CELL> enable
CELL# set network wan media ‘copper’
//Power cycle the eNB.
Figure 2-7: Quick Setting (Standard eNB)
12
Figure 2-8: Quick Setting (HaloB eNB)
Table 2-5: Quick Setting

Duplex Mode Preset field that cannot be configured at this time. 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, or
Canada or Other Area
Band The eNB’s operating frequency band, which is specific to the hardware model.
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 synchronization of
Patterns downlink and uplink timing. The guard period between switching from DL to UL
or UL to DL determines the maximum supportable cell size. The guard period has
to be large enough to cover the propagation delay of DL interferers. The default
setting is 7.
13
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 randomly assigned to this eNB. The range is 0-
268,435,455.
MME IP This field appears for standard eNBs (not operating in HaloB mode). Enter the 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.
Transmission interface This field appears for HaloB-enabled eNBs only. Select WAN or PPPoE for the
binding external network interface.
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 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 to allow it to radiate or to keep it from
radiating.
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.
*NOTE: If you are using a two-carrier eNB such as Nova-436 and wish to set it up in dual carrier
(split sector) mode, you must change the EARFCN and PCI in one of the cells to a different value
so that the two cells do not interfere with one another. You must also enable Cloud EPC so that
you can define a separate IPSec tunnel for each cell. Please refer to the Baicells Dual Carrier
Configuration Quick Guide for further information related to dual carrier software differences.
2.6 System
The System menus are used for setting the Network Time Protocol (NTP), used when 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.
14
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-9, 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-9: NTP
Table 2-6: NTP

Current Date & Time Displays the current date and time that the eNB is using
NTP Sync Period Network Time Protocol interval for synchronizing between the eNB and the
primary NTP server. The range is 10-65,535 seconds.
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
15
2.6.2 Upgrade
The Upgrade menu shown in Figure 2-10 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.4 Upgrade.
Caution: The reboot action will disrupt eNB service. For two-carrier eNBs
operating in dual carrier (split sector) mode, rebooting one cell will automatically
reboot the other cell. For more information on dual carrier operation, refer to the
Baicells Dual Carrier Configuration Quick Guide.
NOTE: For two-carrier eNBs operating in dual carrier (split sector) mode, upgrade or
downgrade only Cell 1. Any changes to Cell 1 software automatically affects Cell 2.
Figure 2-10: Upgrade
16
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-11.
NOTE: The Restore function is available only on Cell 1 of a two-carrier eNB such as Nova-436
operating in dual carrier (split sector) mode. For more information, please refer to the Baicells
Dual Carrier Configuration Quick Guide.
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.
Figure 2-11: Backup
17
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-12. Use the Reset button if you want to reset the password to the
original default setting.
Figure 2-12: Password Window
2.7 Network
The Network settings are where you configure the network interfaces for the eNB (Figure 2-13). This
section discusses the standard eNB Network interface. Please refer to the Baicells HaloB User Guide
for HaloB configuration information.
The Network 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.
18
Figure 2-13: Network – Standard & HaloB eNBs
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-14 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.
NOTE: For two-carrier eNBs operating in dual carrier (split sector) mode, you will be able to
modify the WAN setting only for Cell 1. Cell 2 will automatically accept the configuration for
Cell 1 WAN interface. Please refer to the Baicells Dual Carrier Configuration Quick Guide for
further information related to dual carrier software differences.
19
Figure 2-14: Internet / WAN
Table 2-7: Internet / WAN

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.
20
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-15. 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.
Caution: Concerning two-carrier eNBs operating in dual carrier (split sector) mode:
If the Internet/WAN interface Connect Type was set to copper, the DHCP function
cannot be used for either Cell 1 or Cell 2. If the Internet/WAN interface Connect
Type was set to fiber, the DHCP function can be used for Cell 1 but not for Cell 2.
Refer to the Baicells Dual Carrier Configuration Quick Guide for details about
configuration differences related to this operating mode.
Figure 2-15: DHCP
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-16). 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
21
Figure 2-16: VLAN
2.7.4 IPSec/MME Pool

The system will enable the IP Security (IPSec) gateway by default for standard eNBs (not operating in
HaloB mode). 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-17).
NOTE 1: The IPSec/MME Pool is not included in the GUI of an eNB operating in HaloB mode.
NOTE 2: Concerning two-carrier eNBs operating in dual carrier (split sector) mode: Out of box,
the eNB GUI will show the IPSec gateway for only one cell. Under Quick Settings, when you
enabled Cloud EPC and saved the setting this automatically established two IPSec tunnels and
enabled the MME Pool. Please refer to the Baicells Dual Carrier Configuration Quick Guide for
details.
22
Figure 2-17: IPSec/MME Pool
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-18), where you can
configure the tunnel fields. Two tabs, Basic and Advance Setting, appear. The Basic Setting fields are
shown in Figure 2-18 and described in Table 2-8. The Advance Setting fields are shown in Figure 2-19
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.
Caution: It is highly recommended that you use the default advance settings
for IPSec. Improper changes may lead to system exception.
23
Figure 2-18: 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 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)
24
• (aka_psk)
• (aka_cert)
Pre Shared Key Caution: Change not recommended!
The 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-19: Tunnel Configure > Advance Setting

[Recommend leaving at default values]
Table 2-9: Tunnel Configure > Advance Setting

[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
25
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.
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. 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.
26
The MME Pool fields shown above in Figure 2-17 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-20 allow you to enable or disable the gateway
connection to the backhaul network; to select an LGW Mode of Network Address Translation (NAT),
router, or bridge; and to select an LGW Interface Binding of WAN – Wide Area Network - or PPPoE –
Point-to-Point Protocol over Ethernet. 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-20: LGW Setting (Bridge, NAT, & Router Modes)
For additional 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
27
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-21.
NOTE: The CertStore menu is not included in the GUI of an eNB operating in HaloB mode.
Figure 2-21: CertStore
2.7.7 Static Routing

The Static Routing menu appears only when an eNB is operating in HaloB mode and the WAN/LAN
connection is set to Static IP. If you have set the eNB GUI > Network > WAN/LAN parameter for a HaloB-
enabled eNB to Static IP, in the Static Routing menu you define the destinations where the HaloB eNB
will route traffic (Figure 2-22).
Existing routes will display in the Route State section of the window, showing the destination IP address,
gateway, genmask (general destination netmask), etc. To add a new static routing address to the list,
click on the New button, enter the information, and click on Save. Please refer to the Baicells HaloB
User Guide for further information on configuring HaloB-enabled eNBs.
28
Figure 2-22: Static Routing
2.8 BTS Setting

The base transceiver station (BTS), or eNB, settings relate to security, management, and
synchronization with other network elements (Figure 2-23). Each item is explained in this section.
Figure 2-23: BTS Setting - Standard & HaloB eNBs
29
2.8.1 Security Setting
The Security Setting fields pertain to the LTE encryption algorithms used (Figure 2-24). 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.
Figure 2-24: Security Setting
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. Certain versions of UE firmware allow the UEs to be
picked up automatically by the OMC without having to configure them in 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.
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-25.
NOTE: For two-carrier eNBs operating in dual carrier (split sector) mode: Cell 1 and Cell 2 must
be added separately in the OMC using their individual serial numbers. Add your operator
CloudKey in the GUI of both cells so that both cells associate to your cloud account. Each cell
will appear as a separate eNB in the OMC. For more information, please refer to the Baicells
Dual Carrier Configuration Quick Guide.
30
Figure 2-25: Management Server
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-26).
NOTE 1: The two cells in a two-carrier eNB share a single GPS antenna. If GPS sync is selected,
it is controlled by Cell 1 and therefore configured in the Cell 1 GUI. Cell 2 will sync with the
same antenna as used by Cell 1.
*NOTE 2: Although it appears as a sync option in the GUI, 1588 has not been tested and is not
supported currently.
Figure 2-26: Sync Setting
31
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).
• 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.8.4 HaloB Setting

The HaloB Setting menu will appear in the eNB GUI only if the operator has purchased the HaloB
feature for the eNB and upgraded the eNB with the HaloB software. HaloB is an invention of Baicells
Technologies, developed to address certain wireless service provider scenarios. In particular, HaloB
addresses:
• Operators who are concerned about adding core network functions to the network when
full-blown end-to-end Long-Term Evolution (LTE) networking may not be necessary; and
• Operators who want subscriber service to continue in case there is a situation where the
Evolved Packet Core (EPC) becomes unavailable (e.g., severe weather).
Operators in these situations need a way to offer or continue offering subscribers service but not be
dependent on the availability of the core LTE EPC functions in order to do so. In simple terms, HaloB
is an eNB with onboard “lite” EPC capabilities. HaloB can be purchased as an add-on feature that the
operator can enable/disable as needed on a per-eNB basis.
When an eNB is operating in HaloB mode, it provides the necessary EPC functions for UE attachment,
signaling, and control. There are no S1 tunnels from the eNB to the EPC. Each eNB running HaloB
software controls its subscribers independently. All signaling stays local, within the eNB. A HaloB-
enabled eNB uses the TR069 connection to the cloud to download subscriber information. If a new
subscriber attempts to attach to the HaloB eNB, the eNB does a quick query to the OMC/BOSS to
validate and download the subscriber’s information.
Use the HaloB setting to enable or disable HaloB operation on the eNB (Figure 2-27). For more
information on HaloB, please refer to the Baicells HaloB User Guide.
NOTE: In the initial 2.4.1 release, VxLan required an optional separate feature key, as shown in
Figure 2-27.
32
Figure 2-27: HaloB Setting
2.8.5 License Management

The BTS Setting > License Management menu pertains only to the HaloB feature at this time. If the
operator has purchased the HaloB feature for the eNB, Baicells generates a unique feature key specific
to the eNB based on its serial number. When the operator receives the feature key file from Baicells,
the operator uses this menu to import the license. Refer to Figure 2-28. For more information on HaloB,
please refer to the Baicells HaloB User Guide.
33
Figure 2-28: License Management
2.9 LTE
The LTE parameters are important for efficient wireless network operation (Figure 29). 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.
NOTE: HaloB-enabled eNBs operate as standalone entities. At this time, most of the LTE and
mobility parameters do not apply to a HaloB eNB.
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 to LTE Handoff
Configuration Example.
34
Figure 2-29: LTE – Standard & HaloB eNBs
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.
35
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-30 and described in Table 2-10. The parameters shown in the figure reflect the recommended
settings for this operator example. Click on Save to save the configuration data.
Figure 2-30: 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 stands for Evolved Universal Mobile Telecommunications
System (UMTS) Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency
Channel Number.
Q-RxLevMin The minimum received signal level at which user equipment (UE) will detect a
neighboring eNB’s signal. The range is -70 to -22 dBm. 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 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.
36
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.
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. The 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-31
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.
Figure 2-31: 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
37
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 example, the recommended value is 0 dB.
TAC Tracking Area Code (TAC) of this neighbor cell. Range is 0-65535.
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-32 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-32: TD-S Freq/Cell > Neigh Freq Table Settings
38
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 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.
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.
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

and described in Table 2-13. Click on Save to save the configuration data.
39
Figure 2-33: 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.
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-34 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.
40
Figure 2-34: 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. The range is 0-7.
Resel Thresh High The cell reselection threshold for a higher priority inter-band frequency.
frequency cell has a higher cell reselection priority than the serving cell). The
range is 0-31.
Resel Thresh Low The cell reselection threshold for a lower priority inter-band frequency.
frequency cell has an absolute priority lower than the serving cell). The range is
0-31.
2.9.1.3.2 GSM Neigh Cell Table

and described in Table 2-15. Click on Save to save the configuration data.
41
Figure 2-35: 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-36.
NOTE 1: The terms handoff and handover are used interchangeably in LTE.
NOTE 2: Handoff is not supported at this time on an eNB operating in HaloB mode.
42
Figure 2-36: 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 to LTE Handoff Configuration Example.
The default settings in the Mobility Parameter sub-menus represent standard LTE deployments. Many
of the mobility settings should be left with their default values. Any modification should be determined
only by experienced wireless professionals.
Figure 2-37 shows the sub-menus for the mobility parameters. In terms of LTE to LTE handoff, only the
A1, A3, A5, Measurement Control, Cell Selection Parameter, and Cell ReSelection Parameter fields are
used. The B2 Event Thresholds pertain only to TD-SCDMA and GSM adjacent cells, not to adjacent LTE
cells.
You will configure these mobility parameters for every adjacent eNB. If the serving eNB determines
that more than one adjacent eNB meets the RSRP event thresholds, the Cell Reselection settings will
determine to which adjacent eNB the serving eNB would hand off.
To begin the configuration, next to A1 Event Threshold select the + icon as shown in Figure 2-38. The
resulting window presents the fields for each sub-menu you open, as illustrated in the figure, where
A1, A2, A3, and A5 Event Threshold sub-menus have been opened.
The configuration values shown in Figure 2-38 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.
43
Figure 2-37: Mobility Parameters
44
Figure 2-38: 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/
baicellsoperatorsupportgroup/permalink/1760449424249426/
A3 Event Threshold
Intra-Freq Handover A3 The LTE A3 event is triggered when a neighbor cell becomes better than the
45
Offset 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 Offset Automatic Neighbor Relation (ANR) – not supported at this 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 A5 The LTE A5 event is triggered when the serving cell becomes worse than
RSRP Threshold 1 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 A5 Range is 0-97 dB. In this example, the recommended value is 45 (integer),
RSRP Threshold 2 which equals -140 dBm + 45 = -95 dBm.
Inter-Freq ANR A5 RSRP Automatic Neighbor Relation (ANR) – not supported at this time. Range is 0-
Threshold 1 97. The integer should be larger than or equal to the Inter-Freq Handover A5
RSRP Threshold 1 parameter.
Inter-Freq ANR A5 RSRP Automatic Neighbor Relation (ANR) – not supported at this time. Range is 0-
Threshold 2 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-39 and described in Table 2-17. Click on Save to
save the configuration data.
Figure 2-39: B2 Event Threshold
Table 2-17: B2 Event Threshold Fields

UTRA B2 RSRP Threshold parameter 1 of the UTRA Time Domain Scheduling (TDS) based B2
Threshold 1 event. Range is 0-97 dB. Default is 70 dB.
RSRP Threshold 2 Threshold parameter 2 of the Reference Signal Received Power (RSRP) based
B2 event. Range is -5 dB to 91 dB.
GERAN B2 RSRP Threshold 1 Threshold parameter 1 of the GSM Edge Radio Access 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 Network (GERAN) B2
Threshold 2 event, based on Inter-Radio Access Technology (IRAT). Range is 0-63 dB.
46
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-35 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-40 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-40: 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. The range is 0-5120 ms. In this example,
the recommended value is 480 ms.
The Cell Selection Parameter and Cell ReSelection Parameter sub-menus are shown in Figure 2-41
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.
47
Figure 2-41: 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.
Qhyst Delay time for reselection. Range is 0-24 dB. In this example, the recommended
value is 1 dB.
Reselection Priority Priority for reselection. Range is 0-7 (integer). In this example, the
recommended value is 4.
ThreshServingLow Threshold for selection to cells of 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.
48
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-42 shows the Advanced
parameters sub-menus. Each one is explained in this section.
NOTE: HaloB-enabled eNBs operate as standalone entities and cannot be configured for X2
handoff at this time. A HaloB eNB GUI will not show the X2 menu.
Figure 2-42: Advanced Parameters Sub-Menus
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.
49
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-43). Click on Save to save the configuration.
NOTE: HaloB-enabled eNBs operate as standalone entities and cannot be configured for X2
handoff at this time. A HaloB eNB GUI will not show the X2 menu.
Figure 2-43 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-44 and described in Table 2-20.
Click on Save to save the configuration.
Figure 2-44: 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 (PRACH). Range is -90 to -
Power 120.
Po_nominal_pusch Physical Uplink Shared Channel (PUSCH) carries user data. It supports
Quadrature Phase Shift Keying (QPSK) and 16 Quadrature Amplitude
50
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.
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-45. 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-45: eNodeB Settings
51
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-46. Click on Save to save the configuration.
Figure 2-46: 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-47 and Table 2-21. Click on Save to save the configuration.
Figure 2-47: 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.
2.9.3.6 SON Function Settings

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-48 and Table 2-22. Click on Save to save the configuration.
52
Figure 2-48: SON Function Settings
Table 2-22: SON Functional Parameters

PCI Selfconfig Enable or disable self-configuration of the eNB Physical Cell Identifier (PCI)*.
The default is disable.
PCI Self-configuring The Physical Cell Identifier (PCI) numbers to use. Enter each PCI number, and
Optional List 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-49.
Figure 2-49: 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-50 and
explained in Table 2-23. Click on Save to save the configuration.
Figure 2-50: 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.
53
Zero Correlation Zone Specifies the cyclic shift intervals to generate the PRACH sequence. Range
Config is 0-15. Default is 10.
https://community.na.baicells.com/t/baitip-of-the-day-
december-14th-2016-subframes-and-special-subframes/163
PRACH Freq Offset Determines the location of the 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 Working Mode

The Working Mode allows you to set the eNB to handle the maximum number of multiple users (96*)
or limit it to service a maximum of 32 users, called Low Delay Mode (Figure 2-51). When this value is
set to Low Delay Mode(32UE), fewer users will be served but will have more capacity than when the
value is set to handle the maximum of 96 users.
*NOTE: Depending on eNB model and software version
Figure 2-51: Working Mode
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:
• 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 considered.
• RR – Round Robin (RR) scheduling (default) 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-52. Click on Save to save the configuration.
Figure 2-52: Scheduling Algorithm Parameters
54
2.9.3.11 Sync Adjust Parameter
The Sync Adjust parameters help the system to compensate for packet delay in the uplink and
downlink. Do not modify these fields. Refer to Figure 2-53 and Table 2-24 concerning these settings.
Figure 2-53: 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-54 and Table 2-25.
Click on Save to save the configuration.
Figure 2-54: 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 to LTE Handoff 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-55 shows how the LTE Neigh Frequency and Neigh Cell
tables are configured in this example.
55
Figure 2-55: LTE Freq/Cell > Neigh Freq and Neigh Cell Table Settings
Concerning the A1, A2, A3, and A5 event thresholds, review the flowchart shown in Figure 2-56. 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.
56
Figure 2-56: Flowchart of Handoff Event Thresholds
For the A1 event threshold, assume the starting measurement is set to 45 (Figure 2-57). 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.
Figure 2-57: A1 Threshold
Under the A2 Event Threshold, assume the LTE A2 RSRP threshold is set to 40 (Figure 2-58). 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.
57
For the A3 Event Threshold, assume the offset value is set to 10 (Figure 2-59). 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-60).
If the UE reports an A5 event (RSRP of the serving cell < -100 dBm, and the RSRP of the neighbor cell
is > -95 dBm), the eNB may command the UE to hand off to the target inter-frequency cell.
Assume that X2 Handover is enabled (Figure 2-61). 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-61: X2 Handover
With any changes to these configuration parameters, reboot the eNB for the new configuration to take
effect.
58
2.10 Reboot
To reboot the eNB click on the Reboot menu item, and then click on Reboot Now as shown in Figure
2-62. 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-62: Reboot Action
2.11 Logout
To log out of the eNB GUI, click on the Logout menu item shown in Figure 2-63. You will automatically
be logged out of the GUI and presented with the login screen.
Figure 2-63: Logout Action
59
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
60
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 associated with the operator’s account in OMC. Refer to Appendix D.
1. Set up the UE as instructed in the user manual for the device.
2. Open a Web browser, and enter:
a. http://192.168.150.1 (Gen 2 UEs),
b. http://192.168.254.1 (Gen 1 UEs), or
c. http://192.168.1.1 (Gen 1 UEs on firmware older than V1.0.3)
and then press Enter.
3. At the login window (Figure 3-2), enter the default user name (admin) and password (admin),
and click on Login. To protect your UE from unauthorized access, change the password after
your first login. The steps for password change are explained below Figure 3-3.
Figure 3-2: UE GUI Login
After you log in, the main menu is shown in the left navigation pane (Figure 3-3). 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
61
To change your password, go to System > admin (Figure 3-4). Enter the new password, and then re-
enter the new password to confirm it. The password may be 5 to 8 ASCII characters (letters,
numbers, and special characters). Baicells recommends using a mix of upper and lower case letters
plus numbers. Click on Submit to save the change. Select Save & Apply.
Figure 3-4: Change Password
3.3 Status
The UE GUI status menu is like a dashboard about the UE. It provides information about the model,
software version, serial number, performance, and other usage data. The two sub-menus, Overview
and Routes, are explained in this section.
3.3.1 Overview
The Overview menu provides system and device status information for the given UE. Scroll down the
page to see all of the fields (Figures 3-5 to 3-7). The fields are described in Table 3-2.
Figure 3-5: Overview Fields (1 of 3)
62
Table 3-2: Overview Fields

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

ARP
IPv4-Address Current or most recently used Internet Protocol address of the target device
MAC-Address Current or most recently used Media Access Control address of the target
device
Interface The local area network interface through which the IP address reaches the
target device
Active IPv4-Routes
Network Name of the external network
Target IP address range for traffic on the external network
IPv4-Gateway The gateway address for IPv4 addresses
Metric Number of times the UE accessed the external network
Table Name of the routing table used by the gateway
66
3.4 Network
The Network menu opens to several sub-menus, as shown in Figure 3-9. This section explains each
sub-menu.
Figure 3-9: Network Sub-Menus
3.4.1 LAN Settings

In the LAN Settings sub-menu (Figures 3-10 and 3-11), you can enter or change the IP address settings
for the UE. By default, the IP address is 192.168.254.1 (Gen 1 UEs) or 192.168.150.1 (Gen 2 UEs) and
the subnet mask is 255.255.255.0. If you edit the address, for example to make the address easier to
remember, make sure that the address you choose is unique to your network. You will use the address
to access the Web GUI.
You can bind an IP address to the UE based on its Media Access Control (MAC) address. If binding is
configured, the UE will receive the same IP address each time it accesses the Dynamic Host
Configuration Protocol (DHCP) server. DHCP dynamically assigns an IP address and other network
configuration parameters to each device on the network so they can communicate with other IP
networks. When configured as a DHCP server, the UE automatically provides the TCP/IP configuration
for the LAN clients that support DHCP client capabilities. If DHCP services are disabled, you must have
another DHCP server on the LAN or each client must be configured manually.
To add a device to the setup list, click on ADD LIST. Table 3-4 describes each field. After entering the
information, click on SAVE & APPLY to activate the new settings.
67
Figure 3-10: LAN Settings (1 of 2)
Figure 3-11: LAN Settings (2 of 2)
Table 3-4: LAN Settings

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

The Network > WAN Settings are where you select or enter the WAN Interface, Network Mode, and
Domain Name Server (DNS) information. Refer to Figure 3-12.
3.4.2.1 WAN Interface

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

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

Country Code Select the country code for the region where the UE is located, or select World
Wide, which means this configuration can be used anywhere.
Channel AUTO or wireless channel – If set the AUTO, the device will scan the network
and start a Wi-Fi association in a clear channel.
Ssid Service Set Identifier is auto-filled based on which SSID you selected SETTINGS
for
Encryption Select the type of security encryption to use for this SSID, e.g., WPA2-PSK
Cipher Select the type of cipher to designate the encryption protocol, e.g., TKIP/CCMP
Password Password that users must enter to access this SSID/WLAN. Must be at least 8
characters long.
Hidden Click on the check box to hide the password
Network Select the data path – either LAN or L2. If configured as L2, this SSID can bind to
a VLAN tag, so the traffic will add this VLAN tag for L2 isolation service. L2
isolation service prevents communications between wired and wireless clients
in the network. See example of L2 setup in Figure 3-16.
72
Figure 3-16: L2 Network Example
3.4.4 Wifidog
The feature, Wifidog, is an embeddable captive portal solution used to build wireless hotspots. It works
in cooperation with a remote authentication server. When Wifidog is enabled, every connected Wi-Fi
device (smart phone, tablet, laptop, etc.) will be authenticated through the remote authentication
server.
NOTE: Baicells recommends not enabling Wifidog on a Baicells UE that uses Power over
Ethernet (PoE). The feature requires a connection to an authentication server to function.
To enable Wifidog, go to Network > Wifidog. Notice that there are 3 tabs on this page. Under the Basic
Settings tab you will be able to input the authentication server address and authentication code, and
enable Web Authentication (Figure 3-17). Click on SAVE & APPLY before leaving the tab.
73
Figure 3-17: Basic Settings
Under the Whitelist tab you can add URL addresses to be whitelisted – that is, allowed – from a user’s
wireless device without having to authenticate (Figure 3-18). Separate each URL with a comma (,).
In the Free certification equipment field, you also will enter the wireless devices’ MAC addresses, also
using a comma (,) to separate each one. Be sure to click on SAVE & APPLY before leaving the tab.
Figure 3-18: Whitelist
Use the Advanced Settings tab to configure the authentication gateway port number, HTTP port
number, and connection parameters. Enter the server path for the authentication server, and select
how often the UE will try to connect to the authentication server by indicating the interval period, in
seconds. The Client timed out field allows you to define the maximum amount of time before failure
to authenticate times out, e.g., 5 minutes. Refer to Figure 3-19. Be sure to click on SAVE & APPLY before
leaving the tab.
74
Figure 3-19: Advanced Settings
3.4.5 Static Routes

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

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.5 LTE
The LTE menu is where you define the connection method for the UE to connect to the network, the
scan method for how the UE scans the available frequencies, APN Management, and PIN Management
(Figure 3-24). Each function is described in this section.
77
Figure 3-24: LTE
3.5.1 Connection Mode

You can set the UE to connect automatically to the network (assuming the user has inserted a valid
SIM card), or you can set the connection mode to manual, where the user takes the action to connect
to the network each time (Figure 3-25). Click on SAVE & APPLY to activate the setting.
Figure 3-25: Connection Mode
3.5.2 Scan Method

The Scan Mode 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-26 to 3-28 to view the Scan Mode configuration fields based on which method you select.
Select one of the following options:
• Full Band – The UE will routinely scan all channels in the band, which can make the time it takes to
connect longer than the other modes. The band is dependent on the model of UE being used.
• Frequency Lock – You can specify which band(s) the UE will scan. After selecting this option, click on
ADD LIST. This will open a new window where you can input the band number and the preferred E-
UTRA Absolute Radio Frequency Channel Number (EARFCN). Click on ADD to add the settings.
• PCI Lock – Allows you to select the specific E-UTRA Absolute Radio Frequency Channel Number
(EARFCN) and Physical Cell Identifier (PCI). Click on ADD LIST to enter the settings (Figure 3-26). After
entering the information, click on ADD. You can add more than one PCI Lock list. The UE will scan the
list for eNBs with the PCI and EARFCN combination.
78
Click on SAVE & APPLY to activate the configuration.
Figure 3-26: Scan Method
Figure 3-27: Frequency Lock
79
Figure 3-28: PCI Lock
3.5.3 APN Management

An Access Point Name (APN) is the name of a gateway between a 3G/4G mobile network and
another computer network, frequently the public internet. The UE supports 4 APN configurations. Go
to LTE > APN Management to configure the different services (Figure 3-29 and Table 3-7). Click on
SAVE & APPLY to activate the data. The bottom of the screen lists any APNs that have been defined
for this UE.
80
Figure 3-29: APN Management
Table 3-7: APN Management

APN Number Select the APN number – 1, 2, 3, or 4
Enable Select the check box next to Enable to enable this APN
APN Name Enter the name of this APN, as defined in the eNB configuration
Default Gateway To enable a default gateway to this eNB, select the check box next to Enable.
Apply To Select either No [None] Specified, TR069, SNMP, or SNMP+TR069 to indicate
which protocol may be used to collect information about the eNBs to which this
UE may connect.
81
3.5.4 PIN Management
The purpose of the LTE > PIN Management menu is to give you the ability to require users to enter a
personal identification number (PIN) before they can use the UE. If a PIN has been enabled on the UE
and a user enters the wrong PIN, they will not be allowed to connect to the internet through the UE.
The USIM Status field indicates if the UE’s SIM card is inserted and available. The SIM card status must
show “Available” before you can configure a PIN or access the internet through the UE.
The PIN Verification field initially is not enabled. If you click on the check box next to Enable, it opens
up the field where you can enter the PIN number (Figure 3-30). The PIN number may be 4-8 digits,
using numbers only. Click on SAVE & APPLY.
Caution: Once you enable the PIN and click on SAVE & APPLY, you will need to remember
the PIN number and enter it before you can modify the PIN Management settings.
Figure 3-30: PIN Management
Figure 3-31 shows the screens you will see after enabling a PIN. To disable the PIN or to modify the
PIN number, select the check box next to Modify PIN – Enable. You will have to enter the current PIN
number, then the new PIN number, and re-enter the new PIN number. Click on SAVE & APPLY.
82
Figure 3-31: Modify PIN
3.6 Security
The Security menu is where you can enable a firewall for the UE and configure related security
parameters (Figure 3-32). Each sub-menu is described in this section.
83
Figure 3-32: Security
3.6.1 Firewall Settings

When you select the Security menu it opens to the Firewall Settings (Figure 3-33). If you enable the
firewall by clicking on the check box, the other sub-menus under Security allow you to configure the
firewall‘s MAC filter, IP filter, and so forth. Click on SAVE & APPLY to activate the settings.
Figure 3-33 Firewall Settings
84
3.6.2 MAC Filter
Media Access Control (MAC) Filtering allows you to identify a list of devices either allowed to access
or forbidden from accessing the network (Figure 3-34). Select Enable to enable MAC filtering, and then
determine whether you will allow or forbid the defined MAC address(es) to access the network. The
fields are described in Table 3-8.
To add a MAC Filter rule, under MAC List select ADD LIST. Enter the MAC address. To add more
addresses, click on ADD. After entering the information, select SAVE & APPLY to activate the settings.
Figure 3-34: MAC Filter > Add List
Table 3-8: MAC Filter

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

IP Filter Select the check box next to Enable to enable IP filtering
Service Type Select the type of service, either custom, FTP, SSH, TELNET, SMTP, HTTP, POP3,
HTTPs, HTTP Proxy to allow to or forbid from the UE
Protocol Select the type of data protocol, either ALL, TCP, UDP, TCP&UDP, or ICMP to
allow to or forbid from the UE
Source Address Range Enter the IP address range for the source device(s) in the format of x.x.x.x or
x.x.x.x/mask. The mask value may be 0 or 32.
Source Port Range Enter the port number range for the source device in the format of 1000 to
1500, or 1000.
Destination Address Enter the IP address range for the destination device(s) to be filtered, in the
Range 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 forbid the IP Filter list
86
3.6.4 URL Filter
The Uniform Resource Location (URL) Filtering function allows you to define a list of URL addresses
that the user is forbidden from accessing. When you set the filter to Enable, a Settings window appears.
Enter the specific URL address users cannot access, as shown in Figure 3-36. To add more URL
addresses, click on ADD. After entering the addresses, select SAVE & APPLY to activate the settings.
The URL(s) you entered will appear in the URL List.
Figure 3-36: URL Filter
3.6.5 Port Forwarding

When Network Address Translation (NAT) is enabled on the UE under the Network > WAN settings,
you can redirect a communication request from one address and port number combination to
another. Only the IP address on the WAN side is open to the internet. If a computer on the LAN is
enabled to provide services for the internet (for example, work as an FTP server), 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 the check box next to Port Forwarding – Enable, and click on
ADD LIST as shown in Figure 3-37. To add more lists, click on ADD. The fields are explained in Table 3-
10. After entering the information, select SAVE & APPLY to activate the settings.
87
Figure 3-37: Port Forwarding
Table 3-10: Port Forwarding

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

Port triggering is a configuration option on a router - in this case, the UE - configured for Network
Address Translation (NAT) under Network > WAN settings. When an application uses a trigger port to
build a connection, the UE will forward the data to the forward port. Refer to Figure 3-38. When
completed, select SAVE & APPLY.
88
Figure 3-38: Port Triggering
3.6.7 ALG
The Application Layer Gateway (ALG) function provides a security component that augments a firewall
or the Network Address Translation (NAT) used by the UE. It allows customized NAT traversal filters to
be plugged into the gateway to support address and port translation for certain application layer
control/data protocols such as FTP, H.323 ALG, SIP, and PPTP. You can enable the different types of
application protocols by clicking on the check box next to any you wish to enable (Figure 3-39). Click
on SAVE & APPLY.
89
Figure 3-39: ALG
3.6.8 UPNP
Universal Plug and Play (UPnP) is a set of networking protocols that allows device-to-device networking
on a local network. When UPNP is enabled, devices seamlessly discover each other’s presence on the
local network and attach dynamically to one another and to network services. Typically, UPnP is
reserved for residential or private networks and not used in an enterprise environment as it may
consume too many resources in a network with a large number of devices.
In the Security > UPNP menu, click on the check box next to Enable UPnP to allow it to function on this
UE (Figure 3-40). Once enabled, any redirects of traffic will display in the Active UPnP Redirects section
of the window. Click on SAVE & APPLY.
Figure 3-40: UPNP
90
3.6.9 Attack Protection
Attack protection is an additional security feature that helps prevent computer hacker attacks such
as TCP SYN FLOOD, UDP FLOOD, and IMCP FLOOD for devices connected to the network through a
Baicells UE. In the Security > Attack Protection window (Figure 3-41), click on the check box next to
TCP, UDP, and ICMP single and/or multiple connections. When you click the check box, the field on
the right becomes editable. Accept the default timer value, in seconds, or enter a value for each type
of attack protection you enable. When finished, click on SAVE & APPLY.
Figure 3-41: Attack Protection
3.7 VPN
The Virtual Private Network (VPN) menu enables you to configure a connection between the UE and
a VPN, e.g., to access a corporate network when telecommuting for work. You can enable a Layer 2
Tunneling Protocol (L2TP) gateway or a Layer 2 network connection to the VPN.
91
3.7.1 IPSec
Internet Protocol Security (IPSec) is a network protocol suite that authenticates and encrypts data
packets sent over a network. IPsec includes protocols for establishing mutual authentication
between agents at the beginning of the session and negotiation of cryptographic keys to use during
the session. IPsec can protect data flows between a pair of hosts (host-to-host), between a pair of
security gateways (network-to-network), or between a security gateway and a host (network-to-
host).
At the VPN > IPSec menu, click on ADD POLICY to configure the settings for one or more IPSec
policies for the UE. Enter the policy name, remote gateway, local and remote subnets, and pre-
shared key for the VPN connection. Click on SAVE. Refer to Figure 3-42 and Table 3-11.
Figure 3-42: VPN > IPSec
Table 3-11: VPN > IPSec

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

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

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

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

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

HTTP Select the check box next to Enable to log in to an HTTP Web address
HTTPPort Enter the HTTP port number to be used. Range is 80 to 65,535. Default is port
80.
HTTPS Select the check box next to Enable to log in to an HTTPS Web address
Redirect HTTPS Select the check box to allow HTTP addresses to be redirected to more secure
HTTPS addresses
Allow HTTPs Login From Select the check box next to Enable to log in to an HTTPs Web address from the
WAN WAN
HTTPSPort Enter the HTTPS port number to be used. Range is 80 to 65,535. Default is port
80.
99
3.8.4 TR-069
If your network operates using a TR-069 auto-configuration server (ACS), the ACS will automatically
provide the UE parameters. If you 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-52 and
explained in Table 3-17. After entering, click on SAVE & APPLY to activate the settings.
Figure 3-52: TR-069
Table 3-17: TR069 Settings

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

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

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

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

Settings
Protocol Select the data packet protocol type, either TCP or UDP, for the test
Target IP The target, reachable IP address. Default is 192.168.23.100.
Port The target port number. Range is 1024 to 65,535. Default is 5001.
Time Enter the amount of time (in seconds) for the Iperf tool to measure the data
throughput. Range is 10 to 86,400 seconds. Default is 30 seconds.
Data Length Data length measured in bytes
Bandwidth Send/receive data rate, in kbps
Result
Status -
Uplink Speed Data throughput on the uplink
Downlink Speed Data throughput on the downlink
3.8.8 Reboot
Use the Reboot menu to perform a reboot of the UE, as shown in Figure 3-59. It can take several
minutes for the reboot to complete. After it reboots, the UE GUI will display the login screen.
Caution: The reboot action will disrupt UE service.
Figure 3-59: Reboot
106
3.9 Logout
When you click on the Logout menu, you are automatically logged out of the UE and returned to the
login screen (Figure 3-60).
Figure 3-60: Logout
107
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
108
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:

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.
109
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 under OMC in section 4.4.6.1 Security.
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
110
In the upper right corner, you will see “Welcome, <your name>”. Use the drop-down menu to access
Change password, Lock screen, and Logout 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
111
4.2.4 Help
The Help menu in OMC and BOSS provide an About description of the software version (Figure 4-8).
Figure 4-8: OMC Help
4.3 System
The CloudCore System menu provides operator-specific information and configuration settings, such
as the ability to add CloudCore administrative users, reset their passwords, or limit access to the
CloudCore account. The menu is shown in Figure 4-9. Each menu item is explained below.
Figure 4-9: CloudCore System Menu
112
4.3.1 Operator Info
When you select Operator Info you will see the operator’s name, CloudKey, and CloudCore
administrator information. Notice the Edit button at the bottom (Figure 4-10), which allows you to
change all but the CloudKey field.
Figure 4-10: Operator Info
4.3.2 Security
The CloudCore System > Security window has one sub-sub-menu: User. In this area any CloudCore
administrative users already defined in the system will be listed in the User Management window on
the right (Figure 4-11).
NOTE: These are not the network subscribers; these are the operator’s CloudCore users.
Figure 4-11: User Management
To search for a specific user already defined in the system, enter the user name or sort the list by status
or user group, and then select Query or Advance Query (Figure 4-12) for search criteria.
113
Figure 4-12: Advance Query
When you find the admin 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 3 vertical bubbles icon under Operation
(Figure 4-13). Select Modify, and enter the basic and assisted information as shown in Figure 4-14.
Fields with a star next to them are mandatory. After entering any changes, select OK to save the data.
Figure 4-13: Operation
114
Figure 4-14: Operation > Modify
The next two functions under Operation allow you to lock/unlock the user’s password, delete the user,
or reset the user’s password. To reset a CloudCore user’s password, when you select Reset Password
the system will prompt you with a message to ensure you want to reset the password before it takes
that action (Figure 4-15). Click on OK if you want to continue.
Figure 4-15: Operation > Reset Password
The system will return a message stating you will receive an email with a link, and you will have 30
days to reset the password (Figure 4-16). The user’s password may include A-Z, a-z, 0-9, dash (-), and
underscore (_) characters.
Figure 4-16: Reset Password Message
115
In the User Management window, to add a new CloudCore user click on the + (Add) icon (Figure 4-17).
This will open a window with some basic information fields to complete. A star next to a field means
that filling in the field is mandatory before you can save the information. The user’s password may
include A-Z, a-z, 0-9, dash (-), and underscore (_) characters.
Figure 4-17: Add User
4.3.3 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-18). 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.
116
Figure 4-18: Logs
4.3.4 Security Rule

Selecting System > Security Rule allows you to define rules for system user access, such as minimum
length of user name, how often users must change their passwords, etc. There are also options for
defining login rules and access rules. The parameters for login rules are straight-forward. For the access
rules, you can create IP address white lists to limit which IP addresses may log in to CloudCore. Use
the + Add icon to define more than one white list range of addresses. Refer to Figures 4-19 and 4-20.
Figure 4-19: Security Rule (1 of 2)
117
Figure 4-20: Security Rule (2 of 2)
4.4 OMC
When you click on the OMC module, you will see a menu in the left navigation pane (Figure 4-21).
Each OMC menu item is explained in this section.
See, also, the Getting Started BaiTip:
NOTE: For two-carrier eNBs operating in dual carrier (split sector) mode, Cell 1 and Cell 2 must
be added separately in the OMC using their individual serial numbers. Please refer to the
Figure 4-21: OMC Menu
118
4.4.1 Dashboard
The OMC dashboard appears on the right side window as you enter the OMC module (Figures 4-22 to
4-28). The dashboard provides operator personnel with a summary of network status, statistics, and
performance data. This at-a-glance feature helps administrators to grasp the health of the network
overall and to quickly identify any issues.
Figure 4-22: Dashboard (1 of 7)
The top of the dashboard window displays the number of active system alarms (Figure 4-22). The types
of alarms reported by OMC include communications, QoS, processing error, equipment, and
environmental alarms.
Alarms are categorized into 4 classes: Critical, Major, Minor, and Warning. Critical alarms are incidents
that can cause system outages, and should be attended to immediately. Major alarms are incidents
that can cause poor or degrading quality of service for subscribers, and therefore should be addressed
as soon as possible. Minor alarms indicate a possible issue that needs to be investigated but will not
disrupt service. Warnings are used to indicate errors that probably need to be corrected or at least
monitored, but may not require any action.
If you click on the double arrows icon in the upper right corner of this block (circled in red in Figure 4-
22) or if you click on an alarm category, it will take you into the OMC Alarm Query sub-menu and show
a list of active alarms (Figure 4-23). Please refer to section 4.4.5 for a description of the alarm
information.
119
Figure 4-23: Dashboard (2 of 7) - Alarms
Scrolling down the Dashboard window, the statistics block of the dashboard presents three sets of data:
eNB Active, eNB Online, and CPE Connect (Figure 4-24). The first 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 second 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 third
statistic, CPE Connect, shows the total number of UEs connected to or disconnected from the network.
Figure 4-24: Dashboard (3 of 7) - Statistics
120
The eNB section of the Dashboard lists all of the operator’s eNBs and contains a search bar so you can
look up and check the status of individual eNBs (Figure 4-25).
Figure 4-25: Dashboard (4 of 7) - eNBs
Scrolling farther down the Dashboard window, you will see Performance graphs showing aggregate
Throughput and Physical Resource Block (PRB) Utilization (Figure 4-26), and UE Count (Figure 4-27).
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.
PRB Utilization shows the average number of subcarriers allocated to users across all eNBs over the
last 5 minutes, an indicator of how much of available system resources are being utilized. The UE Count
shows the total number of connected users at that point in time.
Notice that you can slide the timestamp under each graph from left to right or right to left to see day-
by-day data for 7 days at a time.
Figure 4-26: Dashboard (5 of 7) – Performance – Throughput & PRB Utilization
121
Figure 4-27: Dashboard (6 of 7) – Performance – UE Count
At the CPE part of the Dashboard window, if you click on the double arrows on the right, as shown in
Figure 4-28, the OMC will jump you into the CPE > Monitor sub-menu (Figure 4-28). The CPE > Monitor
fields are explained in section 4.4.3.1.
Figure 4-28: Dashboard (7 of 7) – CPE > Monitor
122
4.4.2 eNB
The eNB menu is shown in Figure 4-29. Each of these functions is explained in this section.
Figure 4-29: eNB Menu
4.4.2.1 Monitor
The Monitor function allows you to see information about any eNBs that are already defined in your
network (Figure 4-30).
Figure 4-30: Monitor
Use the Display icon (Figure 4-31) to show, hide, or rearrange many of the columns in the Monitor
window. After making any display changes, select OK to save the changes.
123
Figure 4-31: Display
As you scroll to the right in the Monitor window you will see the additional columns of information
related to the operator’s eNBs (Figures 4-32 to 4-34).
Figure 4-32: Monitor (1 of 3)
124
If you click on a Filter icon you can customize the Monitor information further by selecting additional
display criteria (Figure 4-35).
Figure 4-35: Filter
Table 4-3 describes each field in the Monitor window.
125
Table 4-3: eNB Monitor Fields

Operation When you click on the 3 vertical bubbles under the Operation column, the menu
displays 3 sub-menu options: Information, Settings, Operation:
Alarm Provides the color code of the severity, as well as the number count of each
severity, level
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 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
UBoot Version Universal boot loader code level, information sometimes needed when
troubleshooting issues
Kernel Version Kernel code level, information sometimes needed when troubleshooting issues
Device Group The device group to which this device has been configured
RF Status Shows if the eNB’s radio is on or off
Active Ratio (30 days) The ratio of active to inactive times for this eNB during the last 30 days
Satellites The number of GPS satellites found and reported by the eNB. This field is active
only in eNBs running certain software versions.
HaloB-Centralized Shows if the centralized mode of the HaloB feature is enabled or disabled on this
eNB.
126
For more information on the HaloB feature, refer to the Baicells
HaloB User Guide.
For each row in the eNB > Monitor window, notice the 3 vertical bubbles icon under the column called
Operation. When you click on the icon, 3 options appear: Information, Settings, Operation. Refer to
Figure 4-36.
When you select Information, the pop-up window displays 4 tabs: Statistics, Alarm, Logs, and CPE
(Figure 4-37). The Statistics tab provides the eNB’s Serial Number, MAC Address, UBoot Version, IP
Address, Software Version, and Kernel Version.
Figure 4-37: Information > Statistics
The graph on the bottom of the Statistics window presents the eNB’s active status vs inactive and
online or offline status across time (Figure 4-38). You can also select UE Count from the pull-down
menu to view a graph showing the number of UEs attached to this eNB. Notice that, as with the
dashboard, you can use the time slide bar below the graph to see day-by-day data for 7 days at a time.
127
Figure 4-38: Statistics
The Alarm tab displays all alarms associated with this eNB (Figure 4-39) – either Active or History
alarms. It shows the alarm number, probable cause, status, event time, and the last update time. Use
the Filter button to display only the alarm category you are interested in. For any alarm in the list, you
use the Operation column with the vertical bubbles to get more details, or confirm or clear the alarm.
Figure 4-39: Alarm
When you select the Logs tab, you can run the device report log (Figure 4-40) and the device
exception log.
128
NOTE: The Device Exception Log will be available in a future software release.
Figure 4-40: Device Report Log
NOTE: The CPE tab is no longer available from this window.
Under Operation, when you right-click on an eNB in the Monitor list and select Settings it opens to the
Wireless tab (Figures 4-41 and 4-42). You can configure or modify any eNB from this window. Each
wireless field is described in Table 4-4. The pull-down menu options for PB, Bandwidth, SfAssignment,
and SpecialSfPatterns are shown in Figure 4-43. Click on OK to save configuration changes.
Figure 4-41: Settings > Wireless (1 of 2)
129
Figure 4-42: Settings > Wireless (2 of 2)
Table 4-4: Wireless Settings

Cell ID Cell ID allocated by the operator. Range is 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
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.
BandIndicator 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.
Power Class The transmit power of the eNB, in dBm, which appears under Quick Settings on
the eNB GUI
Bandwidth 5, 10, 15, or 20 MHz
Sf Assignment In TDD transmissions, the subframe assignment determines the downlink to
130
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.
SpecialSfPatterns Either 5 or 7. This is a standard LTE setting that pertains to synchronization of
downlink and uplink timing. The guard period between switching from DL to UL
or UL to DL determines the maximum supportable cell size. The guard period
has to be large enough to cover the propagation delay of DL interferers. The
default setting is 7.
Figure 4-43: PB, Bandwidth, SfAssignment, SpecialSfPatterns
The second tab for Operation > Settings is Network (Figure 4-44). 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-44: Network Settings
131
The third tab is for Inter-Cell Interference Coordination (ICIC) (Figure 4-45). ICIC is a type of interference
mitigation function. 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-45: ICIC
The fourth tab under Operation > Settings is NTP (Figure 4-46). The network time protocol (NTP)
configuration fields are explained in Table 4-5. Click on OK to save the configuration.
Figure 4-46: NTP
132
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
The last option under the Operation vertical bubbles icon is Operation, which brings up a menu with
4 choices: Synchronize, Logs, Reset Password, and Reboot. Refer to Figure 4-47.
NOTE: If an eNB is inactive, the choices will be greyed out.
Figure 4-47: Operation > Operation
Selecting Synchronize refreshes the eNB status in OMC. Selecting Logs launches a pop-up window
asking if you want to collect logs for this eNB (Figure 4-48). If you do, click on OK.
Figure 4-48: Logs
Use Reset Password to reset the login password for this eNB. When you take this action, the system
will return a message stating it will send you an email with a link. You will be given 30 days to reset the
password. Refer to Figures 4-49 to 4-51.
133
Figure 4-49: Reset Password (1 of 3)
134
4.4.2.2 Maintenance
The OMC > eNB > Maintenance sub-menu offers Reboot, Reset Password, and Device Log functions
(Figure 4-52). For each function you can define and schedule tasks to reboot, reset the password, or
run logs for one or more eNBs. The window opens showing a list of previously-defined tasks on the
right.
Figure 4-52: Maintenance
For each task in the list, the Operation function (3 vertical bubbles icon) presents a menu where you
can View a task, select Active to activate a task, select Terminate to stop a task from running, or
DeleteTask (Figure 4-53).
To define a new task, for example a reboot task, select Maintenance > Reboot and click on the + Add
icon to open the dialogue window shown in Figure 4-54. Select the eNBs on the left and click on the
right arrow to move the eNBs into the Selected area of the window.
135
Figure 4-54: New Task
Click on the check box next to each eNB you wish to select, and select the Execute Type. You can run
the task immediately or schedule a time for the task to run. Click on Next. For the Reboot task, you
will receive a warning that taking this action will cause the eNBs to reboot, disrupting service. Press
OK to continue.
Use the eNB > Maintenance > Reset Password function to reset the password on one or more eNBs at
the same time. Click on the + Add icon to open a dialogue window where you will select the eNBs you
for which you want to reset the passwords (Figures 4-55 and 4-56).
136
The eNB > Maintenance > Device Log function enables you to view event logs for an eNB in the list
(Figure 4-57) or to download device exception logs for an eNB (Figure 4-58).
NOTE: The Device Exception Log function is planned for a future software release.
Figure 4-57: Device Log
137
Figure 4-58: Device Exception Log:
You can also set up a Device Log task by clicking on the + Add icon to open a dialogue window and
select the eNBs for which you wish to collect the logs (Figure 4-59).
Figure 4-59: Add New Task
138
4.4.2.3 Register
The eNB > Register sub-menu provides two functions: Device and License.
4.4.2.3.1 Device
Using the Device function allows you to define eNB device groups and add devices to groups that share
the same configuration parameters (Figure 4-60).
Figure 4-60: Register
In the Device Group section on the left side of the window is a list of predefined device groups. Notice
under Operations that you can view (eye icon), modify, or delete a device group (Figure 4-61).
NOTE: You cannot modify the default device group.
Figure 4-61: View Device Group
Click on the + Add icon to create a new device group (Figure 4-62). After entering the group information,
click on OK to save the configuration.
139
Figure 4-62: Add New Device Group
In the right window is a list of the operator’s eNBs. Use the check box next to any eNB you want to
move to an existing device group or to delete. Use the + Add icon to add a new eNB to the network
(Figure 4-63).
Figure 4-63: Add eNB
The other two icons in the right window enable you to import (Figure 4-64) or export eNB device
information.
140
Figure 4-64: Import eNB
4.4.2.3.2 License
In eNB > Register > License you can import feature license files for optional features such as HaloB
(Figure 4-65). Notice the Import icon in the upper right, where you can import a file with the license
information for one or more eNBs.
Figure 4-65: License
4.4.2.4 Upgrade
4.4.2.4.1 Overview
The eNB > Upgrade function (Figure 4-66) gives you the ability to define software upgrade or rollback
tasks.
Figure 4-66: Upgrade
141
For each existing upgrade or rollback task listed, use the Operation menu to View, Active (for activate)
the task, Terminate the scheduled task, or DeleteTask (Figure 4-67).
When you select View, the last results for that task appear (Figure 4-68). The other Operation sub-
menu items relate to taking an action on a task.
Figure 4-68: View
4.4.2.4.2 Upgrade Procedure

To define a new software upgrade or rollback task, go to the Baicells website (Support > Downloads)
and download the image file to your computer. Then, follow the steps below as an example of creating
a software upgrade task. Creating an upgrade task allows you to upgrade up to 5 eNBs at a time.
1. Go to eNB > Upgrade > Software.

2. Click on the + Add icon to create the task, selecting either Software Upgrade, Software
Rollback, UBOOT Upgrade, or PATCH Upgrade (Figure 4-69).
142
Figure 4-69: Add New Upgrade/Rollback Task
3. In the New Upgrade Task window, accept or change the Task Name and select the device
group in the pull-down menu (Figure 4-70).
4. Under eNBs check the check box next to each eNB you want to upgrade (Figure 4-70). Click
on the right arrow to “move” the eNBs to the Selected list.
Figure 4-70: New Upgrade Task
5. Choose the Execute Type, which determines when the upgrade will occur – either
immediately or scheduled (Figure 4-71). Then, click on Next.
143
Figure 4-71: Execute Type
6. Select the radio button next to the new firmware image file name (Figure 4-72). Click on
Finish.
Figure 4-72: Select Upgrade File
7. The new upgrade task will now appear in the Upgrade > Software list (Figure 4-73).
144
7. In the list of image files shown on the eNB > Upgrade > Software page, find the new
firmware and under Operation select the 3 vertical bubbles icon (Figure 4-74). In the
Operation sub-menu, click on Active or click on Awaiting Start > Active (depending on which
Execute Type you selected). You will receive a Confirm window asking if you want to take the
upgrade action immediately. Select OK if you do.
Figure 4-74: Operation > Awaiting Start > Active
8. To verify that the new firmware version is on the eNBs that you initiated the upgrade task
for, go to eNB > Monitor to search for the eNBs by serial number, cell name, or IP address.
Find and check the Software Version column (Figure 4-75).
Figure 4-75: eNB > Monitor
4.4.2.4.3 Software Files

The eNB > Upgrade > Software Files area provides a list of image files to view or download eNB
firmware, UBOOT, and patches (Figures 4-76 and 4-77).
145
Figure 4-76: Software Files
Figure 4-77: Software Files - View
4.4.3 CPE
When you go into the OMC > CPE sub-menu, you will see several functions listed: Monitor,
Maintenance, Register, and Upgrade (Figure 4-78).
146
Figure 4-78: CPE
4.4.3.1 Monitor
The CPE > Monitor fields are displayed in the window on the right; scroll to the right to see all of the
columns of information related to the operator’s UEs (Figures 4-79 and 4-80).
Figure 4-79: CPE (1 of 2)
147
Figure 4-80: CPE (2 of 2)
Click on the Display icon to select and arrange the columns of information you wish to be displayed for
the UEs (Figure 4-81).
Figure 4-81: Display
148
For each UE, use the Operation functions to view information, configure settings, synchronize the UE
data with the OMC, lock the UE’s frequency, or reboot the UE (Figure 4-82).
When you select Operation > Information, the system displays the basic UE information, such as serial
number, International Mobile Subscriber Identity (IMSI), transmit (Tx) power, mobile country code
(MCC), and mobile network code (MNC) (Figure 4-83).
Figure 4-83: Information
If you select Operation > Settings, you can give a name to the device and you can enable Https Login
for remote Web access (Figure 4-84). For the name, you can use A-Z, a-z, 0-9, - (dash) and _ (underline)
characters. Click on OK to save any changes.
149
Figure 4-84: Settings
Use the Operation > Synchronize function to synchronize the UE with the OMC. The icon to the right
of the Operation column will appear to spin as the two entities sync information (Figure 4-85).
Figure 4-85: Synchronize
The Operation > Frequency Lock function provides a mechanism for configuring how the UE scans
available frequencies in its periodic check, either the full band, a preferred band, or locked to a specific
PCI code or EARFCN (Figure 4-86). (Frequency scanning is covered in section 3.5.2 Scan Method.)
150
Figure 4-86: Frequency Lock
If you select the Operation > Reboot function, the system will warn you that taking this action will
cause the UE to reboot and therefore disrupt service (Figure 4-87). Click on OK if you want to go ahead
and reboot the UE.
Figure 4-87: Reboot
Back in the main CPE > Monitor window, notice the History column. If you click on the graph icon for
a specific eNB the system will display several performance graphs: UL MCS, DL MCS, RSRP1, RSRP2,
CINR1, CINR2, SINR, DL Throughput, and UL Throughput (Figures 4-88 to 4-92).
The first two graphs, UL and DL MCS, provide the average uplink and downlink Modulation and Coding
Scheme (MCS) value over time. The higher the MCS value, the better the throughput. Refer to the
Baicells Operation, Maintenance, & Troubleshooting Guide for information about interpreting the
performance results.
151
Figure 4-88: History > UL/DL MCS
The next two history graphs are the Reference Symbol Received Power 1 and 2 (RSRP1 and RSRP2)
values over time (Figure 4-89). RSRP is the average power of the LTE reference signals over the entire
bandwidth. Weak signal strength can cause connectivity issues and dropped sessions.
152
Figure 4-89: RSRP1 and RSRP2
The Carrier-to-Interference-Plus-Noise Ratio 1 and 2 (CINR1 and CINR2) graphs indicate channel quality
(Figure 4-90). The higher the MCS index reported, which can be QPSK, QAM16, or QAM64 depending
on the model of UE and eNB, the better the quality of the wireless signal and therefore the higher the
throughput rates available to the user.
153
Figure 4-90: CINR1 and CINR2
The Signal-to-Interference-Plus-Noise Ratio (SINR) graph provides the average ratio over time for this
UE (Figure 4-91). Like RSRP, SINR provides an indication of signal strength. Weak signal strength can
cause connectivity issues and dropped sessions.
154
Figure 4-91: SINR
The last two historical performance graphs for the UE are the DL and UL Throughput (Figure 4-92).
Throughput, also referred to as data rate or speed, is expressed in Megabits per Second (Mbps).
Figure 4-92: DL and UL Throughput
155
4.4.3.2 Maintenance
The CPE > Maintenance > Reboot selection enables you to define and schedule a reboot task for one
or more UEs (Figure 4-93).
Figure 4-93: Reboot
Click on the + Add icon shown in Figure 4-93 to create a new reboot task (Figure 4-94). Select the
device group and check the check box next to the UEs you want to select. “Move” them to the
Selected area using the right arrow. You can use the Execute Type area to run the task
immediately or by scheduling a time.
Click on Next to continue when ready. The system will prompt you with a warning to be sure you want
to reboot the UEs (Figure 4-95), which will disrupt service.
Figure 4-94: Create Reboot Task
156
Figure 4-95: Reboot Warning
4.4.3.3 Register
The CPE > Register > Device sub-menu works the same way as for eNB > Register > Device, except it is
for UEs (Figure 4-96). On the left side of the window are the device groups and the ability to add new
UE device groups. On the right side is the list of UEs in the operator’s network, with the ability to add
UEs and import or export UE information. Taking this action is considered registering the device in the
OMC.
Figure 4-96: Register > Device
Under Device Group, click on the eye icon to view information about the device group (Figure 4-97).
Figure 4-97: View
Use the pen icon to modify device group information (Figure 4-98). Use the trash can icon to delete a
device group.
157
Figure 4-98: Modify Device Group
To add a new device group, click on the + Add icon (Figure 4-99).
Figure 4-99: Add Group
In the list of UEs on the right, you can select one or more UEs by clicking in the check box and then
select Move to Device Group to move those UEs to a device group (Figure 4-100). Once you identify
the device group, click on OK to save the change.
158
Figure 4-100: Move to Device Group
Use the + Add icon in the upper right of the list of UEs to add a UE to a device group (Figure 4-101).
You will identify the UE by its MAC address, and then click on Add.
Figure 4-101: Add CPE
4.4.3.4 Upgrade
Under CPE > Upgrade > Software, the functions here are similar to eNB > Upgrade > Software (section
4.4.2.4), except this is where you define upgrade or rollback tasks for the operator’s UEs (Figure 4-102).
159
Figure 4-102: Upgrade > Software
You can filter the existing list of tasks using the Upgrade Type pull-down menu (Figure 4-103).
Figure 4-103: Upgrade Type
To define a new software upgrade or rollback task, go to the Baicells support forum
(https://community.na.baicells.com/latest) and download the image file to your computer. Then,
follow the steps below as an example of creating a software upgrade task. Creating an upgrade task
allows you to upgrade up to 5 UEs at a time.
1. At the main menu, go to CPE > Upgrade > Software (Figure 4-104).
2. In the Upgrade Type pull-down menu select either All, ODU SoftWare Upgrade, or IDU
SoftWare Upgrade.
3. Click on the + Add icon to create a software upgrade task, selecting either ODU Software
Upgrade or IDU Software Upgrade depending on the model of UEs you are planning to
upgrade.
160
Figure 4-104: Upgrade > Software
4. In the New Upgrade Task window, accept or change the Task Name and select the device
group in the pull-down menu (Figure 4-105).
5. Under CPEs check the check box next to each UE you want to upgrade (Figure 4-105). Click
on the right arrow to “move” the UEs to the “Selected” list.
Figure 4-105: New Upgrade Task (1 of 3)
6. Choose the Execute Type, which determines when the upgrade will occur – either
immediately or scheduled (Figure 4-106). Then, click on Next.
161
Figure 4-106: Execute Type
7. Select the radio button next to the new firmware image file name (Figure 4-107). Click on
Finish. The new upgrade task will now appear in the Upgrade > Software list (Figure 4-108).
162
8. In the list of image files shown on the CPE > Upgrade > Software page, find the new firmware
and under Operation select the 3 vertical bubbles icon (Figure 4-109). In the Operation sub-
menu, click on Active or click on Awaiting Start > Active (depending on which Execute Type
you selected). You will receive a Confirm window asking if you want to take the upgrade
action immediately. Select OK if you do.
Figure 4-109: Operation > Awaiting Start > Active
9. To verify that the new firmware version is on the UEs that you initiated the upgrade task for,
go to CPE > Monitor to search for the UEs by CPE Name, MAC Address, or IMSI. Scroll to the
right and check the Software Version column (Figure 4-110).
Figure 4-110: CPE > Monitor (Software Version)
163
4.4.4 Strategy
If you need to change the frequency or Physical Cell Identifier (PCI) of one or more eNBs or UEs, rather
than reconfiguring each eNB or UE individually you can use the Strategy -> PCI Lock sub-menu to create
a new PCI Lock task and implement the bulk-change (Figures 4-111 and 4-112).
Figure 4-111: PCI Lock - eNB
Figure 4-112: PCI Lock - CPE
To create a new PCI Lock or Frequency Lock task, select the eNB or CPE tab and then click on + Add
(Figure 4-113). Accept or modify a name for the new task, and select the Executed mode timing for
the task to run.
Select the Frequency Lock type - Full Band, Band/Frequency Preferred, or PCI lock - (Figure 4-114), and
then select the eNBs or CPEs to be locked by clicking on the check box next to each one in the list
provided (Figure 4-115). The devices you select will appear in the Selected Devices area of the screen.
Notice that when defining the lock task for eNBs you can toggle to enable/disable the “Modify the
binding CPE” function. When enabled, all UEs associated to the selected eNBs will automatically be
affected by the PCI Lock task. Click on OK to save the task.
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.
164
Figure 4-113: Add New Task (1 of 3)
165
4.4.5 Alarm
Mentioned in section 4.4.1 Dashboard, the top of the dashboard window displays the number of active
system alarms, and if you click on the double arrows it takes you into the Alarm > Query sub-menu
(Figure 4-116). All of the Alarm sub-menus are explained in this section.
Figure 4-116: Dashboard - Alarms
4.4.5.1 View
Selecting the Alarm sub-menu in OMC opens to a View of the current system alarms (Figure 4-117).
Figure 4-117: Alarm Sub-Menu
166
The types of events that may trigger alarms are communications, QoS, processing errors, equipment
issues, and environmental issues. 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.
As shown in Figure 4-117, in the upper right of the View window are several icons: Lock Screen, Refresh,
Select template, Filter, and maximize/restore. Lock Screen allows you to lock the screen. Refresh
updates the information that is displayed. Select template assumes you have defined one or more
custom alarm templates, e.g., where you have identified specific severity levels or specific equipment,
etc. How to create templates is explained in the next paragraph. Filter enables you to filter which
columns of information you want to see in the view. Maximize/restore applies to sizing the window.
Above the icons just described are two other icons: Select template and + Add template.
NOTE: If your view is showing an arrow pointing left, click on the arrow to see the two icons.
Select template enables you to select a predefined template view of the alarms (Figure 4-118). To add
a new, custom template, click on the icon and then on the + Add icon (Figure 4-119). In the
dialogue window that opens, complete the Template Name field, select the Device Type, Group Name,
and the alarms you wish to view (Figure 4-120).
Figure 4-118: Select Template
167
Figure 4-119: Add Template
Figure 4-120: Add Template Fields
168
4.4.5.2 Query
When you select Alarm > Query, the window displays two tabs: Active Alarm and History Alarm. Each
tab lists alarms that are either active or historical, and the list shows several columns of information
about each alarm (Figure 4-121).
Figure 4-121: Query
Under the Operation column you can select the 3 vertical bubbles icon next to a specific alarm to bring
up further details about that alarm, such as suggestions for how to resolve it (Figure 4-122). The fields
displayed under Alarm Detail are explained in Table 4-6.
Figure 4-122: Alarm Details
169
Table 4-6: Alarm Detail

Index System index number assigned to each alarm incident
Severity Severity of the alarm – critical, major, minor, or warning
Alarm Identifier Alarm number that identifies the type of alarm
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, such as the eNB
Positioning 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
Also use the Operation functions to confirm an alarm or to clear an alarm. To confirm an alarm means
to acknowledge that you have seen the alarm and are taking action to resolve it. To clear an alarm
means to move the alarm into the History Alarm list, typically once the alarm is resolved (Figure 4-
123).
Figure 4-123: Alarm Confirm and Alarm Clear
Notice in the upper right corner of the Alarm > Query screen is an export icon (Figure 4-124). You can
export the alarm information as a file and save it on a computer or server.
170
Figure 4-124: Export
A couple of other functions to point out in the Query window are the columns with filter icons. For
example, if you click on the Filter icon next to the Severity column, you can quickly select which
category of alarms you want to see – Major, Critical, Warning, and/or Minor (Figure 4-125).
Figure 4-125: Filter
Use the Query or Advanced Query functions to search on other fields related to alarms (Figures 4-126
and 4-127).
171
Figure 4-126: Advanced Query (1 of 2)
Figure 4-127: Advanced Query (2 of 2)
4.4.5.3 Settings
The Alarm > Settings sub-menu functions – Basic, View Config, Library, and Notification - are shown in
Figure 4-128.
172
Figure 4-128: Alarm > Settings
Use the Basic sub-sub-menu to create filter templates and alarm confirm templates for one or more
eNBs. To create a filter template, in the Alarm Filter area of the window click on the + Add icon. This
will open a dialogue window where you can name the filter template and then set up different
parameters using the 4 tabs across the top: Selected eNodeB, Alarm Type, Severity, and Event Time.
In the first tab, Selected eNodeB, check the check mark box next to the eNBs you wish to select and
“move” them to the Selected window using the right arrow (Figure 4-129). Click on OK to save the
information.
Figure 4-129: Alarm Filter > Selected eNodeB
173
In the Alarm Type tab, select the categories of alarms that you wish to filter on for this template (Figure
4-130). Click on OK to save the information.
Figure 4-130: Alarm Type
In the Severity tab, choose which category or categories you wish to filter on in this template – Critical,
Major, Minor, and/or Warning (Figure 4-131). Click on OK to save the information.
Figure 4-131: Severity
In the last tab, Event Time, you can set the start and end dates for collecting and displaying the
information (Figure 4-132). Click on OK to save the information.
174
Figure 4-132: Event Time
Be sure to enable the new template in the Alarm Filter list (Figure 4-133). Use the functions under
Operation to modify (pen icon) or delete (trash icon) an Alarm Filter template.
Figure 4-133: Enable Filter Template
The Alarm Confirm portion of Alarm > Settings > Basic provides a way to confirm specified alarms on
one or more eNBs at the same time. To set up an Alarm Confirm template, click on the + Add icon in
the upper right of the window (Figure 4-134).
175
Figure 4-134: + New Alarm Confirm Template
The tabs are similar to the Add New Alarm Filter template. You will see 3 tabs: Selected eNodeB, Alarm
Type, and Severity. Refer to previous information (section 4.4.5.1 View) on creating an Alarm Filter
template for the steps to finish setting up a new Alarm Filter template in this menu.
The next sub-sub-menu under Alarm > Settings is View Config. The list that appears indicates the last
modification time for any of the templates defined in other sub-menus. Use the functions under
Operation to view, modify, or delete a template in the list (Figure 4-135).
176
Figure 4-135: View Config
When you click on the + Add icon, you can add a new template (Figure 4-136). Give the new template
a name, identify the Device Type, and select the devices to be reported.
Figure 4-136: Add New Template
177
Selecting Alarm > Settings > Library brings up a list of all possible system alarms, providing a probable
cause and the severity level of each alarm (Figure 4-137).
Figure 4-137: Library
The Alarm > Settings > Notification window is where you can enable or disable email notifications of
alarms based on severity level. By default, notifications are disabled. Toggle the Enable button to the
right to enable the notifications function (Figure 4-138).
Enter the email address or addresses where the notification should be sent; you can separate multiple
email addresses using a semi-colon (;). For Sending Period(Min), specify how often in minutes you
want the notifications to be sent. Select the check box next to the severity level(s) for which you want
to be notified via email. Click on Save to save the configuration.
Figure 4-138: Notification
178
4.4.6 System
The OMC System menu includes Security – User, User Group, and RoleSet – and OMC Log functions
(Figure 4-139). Each function is explained in this section.
Figure 4-139: System
4.4.6.1 Security
When you select System > Security > User, in the list of users shown if you click on the check box next
to one or more users’ names the system displays a “Move to User Group” button (Figure 4-140). Use
this function to group users who share common roles or configurations.
179
Figure 4-140: System > Security > User
When you select System > Security > User Group, the window displays a list of existing user groups.
Under Operation you can view information about a group, modify the information, or delete the user
group. See Figure 4-141.
Figure 4-141: User Group
Use the + Add icon to add a new user group (Figure 4-142). Enter the basic information for the new
user group, and select the Role Set to use for this group. Role Set is explained in the following
paragraph. Click on OK to save the configuration.
180
Figure 4-142: + Add User Group
Use the System > Security > RoleSet function to define different user roles, for example by department
or position in the company, to determine a set of user privileges (Figure 4-143).
Figure 4-143: RoleSet
You can create a new role set by clicking on the + Add icon (Figure 4-144). Complete the basic
information, and select which system Functional Operations users in this role may read or edit. If you
want the users in this group to have read-only privileges for one, multiple, or all functions, click on the
check box next to the function name. If the function is an editable function, you will be presented with
2 more check boxes: Read and Write. You can select either or both fields (Figure 4-145). Also, select
the device group name(s) that the users in this role may configure, assign, or modify.
181
Figure 4-144: + Add Role
Figure 4-145: Read/Write Functions
4.4.6.2 OMC Log

The OMC > System > OMC Log sub-menu provides a way to display operation logs, security logs, and
system logs (Figures 4-146 to 4-148).
182
Figure 4-146: OMC Log > Operation Log
Figure 4-147: Security Log
Figure 4-148: System Log
4.4.7 Help
The Help > About menu displays the software version number and name (Figure 4-149).
183
Figure 4-149: Help
184
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-150 illustrates a typical network architecture with
BOSS components.
Figure 4-150: BOSS Network Architecture
In CloudCore, when you click on the BOSS tab you will see a menu in the left navigation pane (Figure
4-151). This section will explain the functions for each of the menu items.
185
Figure 4-151: BOSS Menu
4.5.2 Subscriber
4.5.2.1 Overview
The BOSS Subscriber function is used to add new subscribers and to modify, activate/deactivate, or
delete subscribers. There are two ways to add subscribers, individually and using a bulk-upload Excel
file with the subscribers’ information. Before you can subscribers, there are two other BOSS
configuration sections required to be completed first - the SIM card information (under the Network
menu) and the Service Plan information (under the System menu).
Clicking on Subscriber opens to the Subscriber tab, which brings up a list of existing active subscribers
(Figure 4-152).
NOTE: The Archive tab contains a list of any former subscribers whose accounts have been
deleted.
Figure 4-152: Subscriber
186
4.5.2.2 Operation
In the list of subscribers, under the Operation column you can click on the 3 vertical bubbles icon to
open a menu of actions you can take on that subscriber: Active, Detail, Edit, ResetPwd, and Delete
(Figure 4-153). Each action is explained in this section.
4.5.2.2.1 Active
Clicking on Operation > Active will activate the user. You will receive a system prompt asking if you are
sure you want to activate the user (Figure 4-154).
Figure 4-154: Active
4.5.2.2.2 Detail
Selecting Operation > Detail displays 4 tabs of information: Overview, Change SIM Card, Service Plan,
and Invoices.
4.5.2.2.2.1 Overview Tab
The overview tab presents the subscriber’s Contact Information, which you can edit (Figure 4-155),
and their Account Balance, current Service Plan, and Invoices (Figure 4-156).
Under Account Balance, you can select Recharge to record a subscriber’s payment (Figure 4-157). The
two options under the Method pull-down field are Cash and Voucher Card.
You also have the ability to modify the subscriber’s service plan using the Modify button. Under
Invoices, click on the See All button to get a list of all invoices in the subscriber’s history. When you do
this, you are also presented with an Export icon to export the information to a file.
187
Figure 4-155: View > Overview (1 of 2)
Figure 4-156: View > Overview (2 of 2)
188
Figure 4-157: Recharge
4.5.2.2.2.2 Change SIM Card Tab
The Change SIM Card tab initially will present the current SIM card IMSI information. To change the
IMSI, select the Revise Again button, enter the “new” IMSI, click on the Query icon, and when the
correct IMSI is found, select OK. Refer to Figure 4-158.
NOTE: Taking this action assumes you already uploaded in BOSS the information for the SIM
card to be used. Refer to section 4.5.4 Network.
Figure 4-158: View > Change SIM Card
189
4.5.2.2.2.3 Service Plan Tab
In the Service Plan tab, you will see information about the subscriber’s current service plan, such as
price per month, start and end date, and UE device serial number (Figure 4-159). Use the pen icon
under Operation to edit the information. Use the + Add icon to see a list of available service plans and
choose one for this subscriber (Figure 4-160).
Figure 4-159: Service Plan (1 of 2)
Figure 4-160: Service Plan (2 of 2)
4.5.2.2.2.4 Invoices Tab and Account Tab
Under the Invoices tab you can see the list of invoices for the subscriber. Use the Operation menu to
check details, email the subscriber concerning payment, or download the invoicing information. Use
the Export button to export the account information to a file on your computer (Figure 4-161).
190
Figure 4-161: Invoices
As explained in section x.x Overview Tab, in the Invoice tab if a subscriber has not paid, the Status
column for that subscriber will show unPaid and the Operation menu will include an additional
function: Recharge (Figure 4-162). When you select Recharge, it opens a dialogue window. The window
will display the billed amount; whether or not there is a balance on the account - with an optional Use
Balance Payment check box; the total payable amount; and the method of payment. In the Amount
field, enter the amount being paid, and optionally add notes, and then click on Recharge. Note that
the amount paid cannot be less than the Amount for Bill amount.
NOTE: You can also go to the Account tab for a subscriber to record a Recharge (payment).
Figure 4-162: Recharge
4.5.2.2.3 Edit
Under Operation, if you select Edit it will open the subscriber Identification and Contact Address fields
(Figures 4-163 and 4-164).
191
Figure 4-163: Edit (1 of 2)
Figure 4-164: Edit (2 of 2)
192
4.5.2.2.4 Reset Password
When you select Operation > ResetPwd, it opens the window shown in Figure 4-165.
Figure 4-165: Reset Password
4.5.2.2.5 Delete
If you select Operation > Delete, the system will prompt you to ensure that is the action you want to
take (Figure 4-166). The user’s account information will be moved to the Archive tab.
Figure 4-166: Delete
4.5.2.3 Add Individual Subscriber

To add a new subscriber, click on the + Add icon and enter the subscriber’s information in the fields
shown (Figures 4-167 and 4-168). Notice the two fields highlighted in red. These are mandatory fields
where you select a pre-configured SIM card and service plan (Figure 4-169) to assign to the new user.
After making your selections, click on Yes or Save to save the configuration.
193
Figure 4-167: + Add Subscriber (1 of 3)
194
4.5.2.4 Bulk Import Subscribers

To bulk-upload multiple subscribers’ information at the same time, click on the Import icon on the
upper right side of the Subscriber window (Figure 4-170).
Figure 4-170: Import
In the dialogue window that opens (Figure 4-171), select the Active Type by clicking on the radio
button next to Active or Pre-Active. Choose Active if you already configured service plans and all
subscribers you are uploading will be assigned the same service plan or default service plan. When
you select Active, the existing service plans appear in the list under the Name box. Select a service
plan from the list.
Choose Pre-Active if you have not yet created and do not yet want to configure the subscribers’ service
plan as you upload the subscribers’ information. The pre-active state allows those subscribers to have
network access but at limited speeds or to be redirected to a specified URL, depending on how the
network service is configured. Once the subscribers are assigned a service plan and make their
payment they will have full network access as defined by their assigned plan.
195
Figure 4-171: Bulk (1 of 2)
Scrolling down the Bulk dialogue window, in the Imsi Range fields (Figure 1-172) enter the first IMSI
number in the range in the upper box and the last IMSI number in the range in the lower box. Click on
Submit. The import action will be confirmed under Import Result.
Figure 4-172: Bulk (2 of 2)
196
4.5.3 Billing
The Billing menu has one option, Operator Invoice, where you can view all of the operator’s invoice
information across subscribers (Figure 4-173). Use the Year/Month field to filter the information by
date. You can also export the information to a file and save it on your computer using the Export icon.
Figure 4-173: Operator Invoice
4.5.4 Network
The Network menu under BOSS is where you will define and manage SIM card information (Figure 4-
174). 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.
Figure 4-174: Network Menu
Click on the Network > SIM Card sub-menu to view a list of SIM cards, indicating their associated IMSI
number, active status, and other information (Figure 4-175).
197
Figure 4-175: 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 an activation code provided by Baicells. The other is to import the
SIM card information using an Excel template.
1. In the SIM Card window, select the Import tab as shown in Figure 4-176.
Figure 4-176: Import
2. In the dialogue window that opens, select the Apply Mode, either Active Code or File.
a. If you select Active Code, use the pull-down menu to select the Operator and in the
Active Code field enter the code you received from Baicells (Figure 4-177). Click on
Submit to submit the information.
Figure 4-177: Active Code
b. If you select File, click on the right arrow under the File field to navigate to the Excel
file that contains the SIM card information. Select the Import button (Figure 4-178).
198
Figure 4-178: File
If you need a template for capturing the SIM card information, you can use the Export
Template button to download an Excel template (Figure 4-179).
Figure 4-179: Export Template
199
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.
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.
There is a second tab in the Network > SIM Card window called Records that shows the operator any
activity records captured from importing SIM card information into their BOSS account (Figure 4-180).
Figure 4-180: Records
4.5.5 System
The BOSS System menu (Figure 4-181) enables you to define subscriber Service Plans, configure
Security parameters for users and user groups, and view activity Logs for each subscriber (e.g.,
password resets, service plan changes, etc.).
Figure 4-181: System Menu
200
4.5.5.1 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 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. Service plans can report Status in one of three state: Disabled means the service plan has been
defined but disabled; In Use are service plans currently in use (assigned to active users); or Ready,
which are service plans that have been defined but not yet enabled. Refer to Figures 4-182 and 4-183.
Figure 4-182: Service Plans (1 of 2)
Figure 4-183: Service Plans (2 of 2)
To add a new service plan, select the + Add icon to open the dialogue window (Figures 4-184 and 4-
185). The system will assign a Product ID. A star next to a field indicates the information that you must
enter before you can save the configuration.
Notice for the UL and DL Speed fields you can Limit or Unlimit the data throughput rate of the service
plan. If you select Limit, enter the UL or DL speed in Mbps. The speed equates to the bandwidth that
subscribers with this service plan will receive when uploading data to the network (UL), e.g., 5 Mbps
or 10 Mbps, or when downloading data from the network (DL), e.g., 15 Mbps or 20 Mbps. Typically,
users will download data more often than upload data, and for that reason the DL Rate Limit may be
a higher bandwidth. The maximum UL and DL limits are determined by several factors, including which
equipment models are used. The speed fields support up to 3 decimal points (e.g., 0.001 Mbps for UL
Rate Limit means the user would get a maximum of 125 bps on the uplink).
201
Click on Submit to save the new service plan.
Figure 4-184: Add Service Plan (1 of 2)
Figure 4-185: Add Service Plan (2 of 2)
Back in the list of service plans, under the Operation column you can Enable or Delete each service
plan, or Set Default for a specific service plan (Figure 4-186).
202
Figure 4-186: Enable Service Plan
4.5.5.2 Security
In the System > Security sub-menu are three choices: User Account, User Group, and Role Set (Figure
4-187). Each of these functions is explained in this section.
Figure 4-187: Security
203
4.5.5.2.1 User Account
Selecting User Account enables you to view a list of subscribers in the operator’s network (Figure 4-
188). The information includes the Account Code, Account Name, User Group to which each subscriber
is assigned, Mobile Phone number, ID Number, Status, and E-mail address. Use the Query field to
search for a subscriber based on account code or name.
Figure 4-188: User Account
4.5.5.2.2 User Group

System > Security > User Group works much the same way as User Account, though you have options
under Operation to view, edit, or delete the group (Figure 4-189).
Figure 4-189: User Group
When you select Operation > View it brings up a list of users in that group, showing each user’s last
login time and the list of role sets for this user group (Figure 4-190).
204
Figure 4-190: View User Group
To add a new user group from this menu, click on the + Add icon, enter the basic information, and
select the role set (Figure 4-191).
Figure 4-191: + Add User Group
4.5.5.2.3 Role Set

Selecting System > Security > Role Set displays a list of role sets already defined (Figure 4-192). Use the
+ Add icon to add a new role set (Figure 4-193). Click on the check box next to each menu item you
wish for users assigned this role set to be able to read and/or write (edit).
205
Figure 4-192: Role Set
Figure 4-193: + Add New Role Set
206
4.5.5.3 Logs
The event logs under BOSS > System > Logs display information about any action in BOSS that was
taken for a given subscriber or service plan. You can query or use advanced query to locate a
subscriber’s records by name, SIM code, and so forth (Figure 4-194).
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.
Figure 4-194: Logs
4.5.6 Help
When you click on Help > About, the system displays the BOSS software version level (Figure 4-195).
Figure 4-195: Help
207
Appendix A: MML Commands
Man-Machine Language (MML) refers to the commands that the administrator may use instead of the
GUI to configure 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,
Parameter2=xxx; MOD CELL: LocalCellId=1, LTE_PHY_CELLID_LIST=102,
{Specified LTE_OAM_PLMNID=46001; {eNodeBID=1000}
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
208
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 wireless
Optimized transmission of data through radio signals, typically for
broadband internet access
3GPP Third-Generation 3GPP is a standards body that works within the scope of the
Partnership Project International Telecommunications Union (ITU) to develop
third-generation and later wireless technologies that build
upon the base provided by Global System of Mobile
Communications (GSM). The group is responsible for the
Universal Mobile Telecommunications System (UMTS)
standard, as well as High-Speed Downlink Packet Access
(HSDPA), High-Speed Uplink Packet Access (HSUPA), Evolved
High Speed Packet Access (HSPA+), and LTE.
3GPP2 Third-Generation 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 Wireless 4G is a mobile communications standard intended to evolve 3G
Systems technology, allowing wireless internet access at a much higher
speed.
AAA Authentication, AAA is a framework for controlling access to computer
Authorization, and resources, enforcing policies, auditing usage, and providing the
Accounting information necessary to bill for services.
AC Authentication Center The AC validates any security information management (SIM)
card attempting network connection when there is a live
network signal.
ACK Acknowledge or A flag used in the Transmission Control Protocol (TCP)
Acknowledgement to acknowledge receipt of a data packet.
AM Acknowledged Mode AM requires the receiver of information to send continuous
notifications to the sender that indicate it has successfully
received the information.
AMBR Aggregate Maximum Bit Rate AMBR is the maximum possible bit rate configured by the LTE
operator for a particular LTE user.
AMC Adaptive Modulation and AMC is used to denote the matching of the modulation,
Coding 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
209
subscribers to their immediate service provider.
ANR Automatic Neighbor Relation ANR is a third-generation (3G) telecommunications
specification for automating the identification of an eNB’s
neighboring cells regardless of which Universal Mobile
Telecommunications System (UMTS) technology those eNBs
are running. Having ANR capabilities relieves the operators of
having to manually provision each neighbor cell.
APN Access Point Name An access point (AP) is an eNB gateway between a Global
System for Mobile Communications (GSM), General Packet
Radio Service (GPRS), third-generation (3G) or fourth-
generation (4G) mobile network, and another computer
network, frequently the public internet. An AP name (APN) is
an identifier for a specific AP/eNB.
ARP Address Resolution Protocol ARP is a telecommunication protocol used for resolution of
internet layer addresses into link layer addresses, a critical
function in multiple-access networks.
ARP Allocation and Retention Priority level assigned to bearer traffic. In a mobile network,
Priority ARP decides whether to accept a request to establish a bearer
or reject the request when resources are limited.
ARQ Automatic Repeat reQuest ARQ is an error-control method for data transmission that uses
acknowledgements and timeouts to achieve reliable data
transmission over an unreliable service.
AS Access Stratum The AS is a functional layer in the Universal Mobile
Telecommunications System (UMTS) and LTE wireless telecom
protocol stacks between radio network and user equipment.
AS Application Server An AS is a component-based product that resides in the middle
tier of a server-centric architecture. It provides middleware
services for security and state maintenance, along with data
access and persistence.
BCCH Broadcast Control Channel BCCH is a logical broadcast channel used by the eNB in a Global
System for Mobile Communications (GSM) network to send
information about the identity of the network. This
information is used by a mobile station to get access to the
network.
BCH Broadcast Channel A BCH is a downlink channel in a Global System for Mobile
Communications (GSM) that is used by the eNBs to provide
signaling information to the mobile stations.
BER Bit Error Rate A BER is the percentage of bits that have errors relative to the
total number of bits received in a transmission, usually
expressed as ten to a negative power.
BLER Block Error Rate BLER is used in LTE/4G technology to identify the in-sync or
out-of-sync status during radio link monitoring. It is a measure
of how successful a data transmission is over the air at the
Physical/MAC layer level.
BOSS Business Operations Support BOSS is a Baicells CloudCore application that enables operator
210
System administrators to add, modify, and delete subscriber
information and service plans. Administrators also use BOSS to
activate each Subscriber Identification Module (SIM) card, a
chip that the end-user inserts in the UE to uniquely identify
that subscriber and UE.
BPSK Binary Phase Shift Keying BPSK is a digital modulation scheme that conveys data by
changing, or modulating, two distinct phases of a reference
signal (the carrier wave).
BW Bandwidth BW refers to the range of frequencies within a given band used
for transmitting a signal.
CBRS Citizens Broadband Radio CBRS is a somewhat new shared spectrum scheme that was
Service 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 identifying
Temporary Identity Radio Resource Control (RRC) connection and scheduling
dedicated to a particular subscriber.
CDMA Code Division Multiple CDMA is a wireless technology where several transmitters can
Access send information simultaneously over a single communication
channel.
CE Customer Edge The CE is the router at the customer’s premises that is
connected to the edge of a service provider’s Internet Protocol
(IP) / Multiprotocol Label Switching (MPLS) network. MPLS is a
type of data-carrying technique for high performance
telecommunications networks.
CFI Channel Format Indicator In LTE, the CFI value defines the time span, in Orthogonal
Frequency Division Multiplexing (OFDM) symbols, of the
physical downlink control channel transmission (the control
region) for a downlink subframe.
CG Charging Gateway An open system that formats and integrates charging data
records between standard and non-standard systems
CINR Carrier-to-Interference-plus- CINR is a measurement of multiple subcarriers; it reflects the
Noise Ratio 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 used by
Equipment a network subscriber to connect to the backhaul carrier
211
network through the access network.
CQI Channel Quality Indicator The Channel Quality Indicator is a value that indicates how
good or bad the communication channel quality is. The UE
sends measurements (a combination of SNR, SINR, and SNDR)
to the eNB which determine the Modulation and Coding
Scheme (MCS) value that will be used in the downlink. The
higher the value, the better the channel quality. The maximum
value is 15.
CRC Cyclic Redundancy Check CRC is an error-detecting code commonly used in digital
networks and storage devices to detect accidental changes to
raw data.
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 controls the
Function communication of Instant Messaging Service (IMS) user
equipment with IMS enhanced services across different
network accesses and domains.
CS-CN Circuit Switched Core In a CS-CN, the bit delay is constant during a connection. No
Network circuit can be degraded by competing users because it is
protected from use by other users until the circuit is released
and a new connection is set up.
CSI Channel State Information CSI refers to known channel properties of a communications
link. The information describes how a signal propagates from
the transmitter to the receiver.
DCCH Dedicated Control Channel The DCCH is a single timeslot on a radio frequency (RF) carrier
that is used to convey eight stand-alone dedicated control
channels.
DCI Downlink Control In LTE, DCI is based upon a process defined as a blind decoding
Information which depends on several decoding attempts on several
Physical Downlink Control Channels (PDCCH) candidate
locations for several defined DCI formats.
DFT Discrete Fourier Transform The DFT converts a finite sequence of equally-spaced samples
of a radio signal into an equivalent length sequence of equally-
spaced samples of the discrete-time Fourier transform (DTFT),
which is a complex-valued function of frequency.
DHCP Dynamic Host Configuration DHCP is a network protocol that enables a server to assign an
Protocol 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 Channel The DL-SCH is the main data bearing channel, which is
allocated to users on a dynamic and opportunistic basis.
212
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-space-
Allocation frequency variation in wireless channels by distributing
precious radio resources, such as spectrum and power, either
to maximize or minimize the network performance metrics.
DRX Discontinuous Reception DRX is a method used in communications to conserve energy
use. The user equipment and the network negotiate phases in
which data transfer occurs. At other times the device enters a
low power state.
DS Direct Spread DS systems transmit the message bearing signals using a
bandwidth that is more than the bandwidth that is needed by
the message signal.
DSCP Differentiated Service Code DSCP is a field in an IP packet that enables various levels of
Point 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 Channel A DTCH is an uplink or downlink communication channel that is
only accessible by one device to transfer user data.
DTX Discontinuous Transmission DTX is a method of momentarily powering down a wireless
device when there is no data throughput.
EARFCN E-UTRA Absolute Radio A unique number given to each radio channel in Global System
Frequency Channel Number for Mobile (GSM) communications. The EARFCN is used to
calculate the exact frequency of the radio channel.
ECM Evolved Packet System (EPS) ECM is the process of identifying, setting up, controlling, and
Connection Management removing a transmission path between two or more points in
the Universal Mobile Telecommunications System (UMTS)
evolved packet system.
EIRP Effective Isotropic Radiated EIRP is the product of transmitter power and antenna gain in a
Power certain direction relative to an isotropic antenna. You could
use the EIRP value, for example, to determine if the radio is
within regulatory values.
EMM Enterprise Mobility EMM refers to the people, processes, and technology focused
Management 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 (EPC) As part of the 3GPP Standard Release 8, the user data (user
User Plane plane) is separated from the signaling (control plane). EPC-U
refers to the user plane.
EPS Evolved Packet System EPS, also called Evolved Packet Core (EPC), is the central
213
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 corresponding radio
Bearer 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 Security (IPSec)
Payload standard for providing authentication, integrity, and
confidentiality of network packet data in IPv4 and IPv6
networks.
E-UTRA Evolved Universal Mobile E-UTRA is the air interface of 3GPP’s LTE upgrade path for
Telecommunications System networks.
(UMTS) Terrestrial Radio
Access
E-UTRAN Evolved Universal Mobile E-UTRAN is the combination of E-UTRA, user equipment, and
Telecommunications System eNBs.
(UMTS) Terrestrial Radio
Access Network
EV-DO Evolution for Data Optimized EV-DO is the third-generation (3G) telecommunications
standard for the wireless transmission of data through radio
signals, typically for broadband internet access.
FA Foreign Agent An FA is a router serving as a mobility agent for a mobile node.
FDD Frequency Division Duplex FDD is a method for establishing a full-duplex communications
link that uses two different radio frequencies for transmitter
(Tx) and receiver (Rx) operation.
FDM Frequency Division FDM is a technique for sending two or more signals over the
Multiplexing 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 Multiple FDMA is a channel access method used in multiple-access
Access protocols as a channelization protocol. FDMA gives users an
individual allocation of one or several frequency bands, or
channels.
FEC Forward Error Correction FEC is a method of obtaining error control in data transmission
in which the source (transmitter) sends redundant data and
the destination (receiver) recognizes only the portion of the
data that contains no apparent errors.
FFT Fast Fourier Transform The FFT is a mathematical method for transforming a function
of time into a function of frequency. Sometimes the method is
described as transforming from the time domain to the
frequency domain.
FMC Fixed Mobile Convergence FMC is the trend towards seamless connectivity between fixed
and wireless telecommunications networks.
214
FQDN Fully Qualified Domain Name Also known as an absolute domain name, FQDN is a domain
name for a specific computer or host on the internet that
specifies its exact location in the tree hierarchy of the Domain
Name System (DNS).
GBIC Gigabit Interface Converter GBIC is a standard for transceivers, commonly used with
Gigabit Ethernet and fiber channel. By offering a standard, hot
swappable electrical interface, one gigabit port can support a
wide range of physical media, from copper to long-wave,
single-mode optical fiber, at lengths of hundreds of kilometers.
GBR Guaranteed Bit Rate GBR is the minimum bit rate requested by an application. In
LTE, minimum GBR bearers and non-GBR bearers may be
provided.
GGSN Gateway GPRS Support A GGSN is part of the core network that connects Global
Node System for Mobile Communications (GSM) based third-
generation (3G) networks to the internet.
GI Guard Interval GIs are used to ensure that distinct transmissions do not
interfere with one another. These transmissions may belong to
different users (as in Time Division Multiple Access, or TDMA)
or to the same user (as in Orthogonal Frequency Division
Multiplexing, or OFDM).
GP Guard Period In Time Division Multiple Access (TDMA), each user’s
timeslot ends with a GP to avoid data loss and to reduce
interference to the following user, caused by propagation
delay. Thus, a user’s timeslot is protected from interference
from the preceding user.
GPRS General Packet Radio Service GPRS is a packet-oriented mobile data service on the second-
generation (2G) and third-generation (3G) cellular
communication system’s Global System for Mobile (GSM)
communications.
GSM Global System for Mobile A digital mobile telephony system which uses a variation of
Time Division Multiple Access (TDMA) technology. GSM is the
most widely used of the 3 digital wireless telephony
technologies (TDMA, GSM, and CDMA) in Europe and other
parts of the world.
GT Guard Time GT is the interval left vacant on a transmission channel that can
be used for synchronization and/or compensating for a signal
distortion.
GTP General Packet Radio Service GTP is a group of IP-based communications protocols used to
(GPRS) Tunneling Protocol carry General Packet Radio Service (GPRS) within Global
System for Mobile (GSM) communications), Universal Mobile
Telecommunications System (UMTS), and Long-Term Evolution
(LTE) networks.
GTP-U General Packet Radio Service GTP-U is used for carrying user data within the General Packet
(GPRS) Tunneling Radio Service (GPRS) core network and between the radio
Protocol (GTP) User Plane access network (RAN) and the core network (CN).
215
GUMMEI Globally Unique MME The GUMMEI is constructed from the Mobile Country Code
Identity (MCC), Mobile Network Code (MNC), and Mobility
Management Entity (MME) Identifier (MMEI).
GUTI Globally Unique Temporary GUTI is allocated to the user equipment (UE) by the Mobility
User Equipment (UE) Identity Management Entity (MME) and has two components - the
Globally Unique MME Identity (GUMMEI) and the MME
temporary mobile subscriber identity (M-TMSI). While the
GUMMEI identifies the MME, the M-TMSI identifies the UE
within the MME.
GW Gateway A GW refers to a piece of networking hardware that is
equipped for interfacing with another network that uses
different protocols.
HA Home Agent An HA is a router on a mobile node’s home network that
maintains information about the device’s current location, as
identified in its care-of address.
HA High Availability HA indicates 100% operation, a never failing component or
system
H-ARQ Hybrid ARQ H-ARQ is a combination of high-rate, forward error-correcting
code and Automatic Repeat Request (ARQ) error control. In
standard ARQ, redundant bits are added to data to be
transmitted using an error-detecting code such as a cyclic
redundancy check.
HDTV High-Definition Television HDTV is a television display technology that provides picture
quality similar to 35mm film.
H-FDD Half-Frequency Division H-FDD requires that two communication parties take turns
Duplex transmitting data over two separate frequency bands or
channels.
HLR Home Location Register HLR is the main database of permanent subscriber information
for a network. The HLR is an integral component of mobile
networks.
HO Handoff or Handover HO refers to the process of transferring an ongoing call or data
session from one channel (eNB 1) connected to the core
network to another channel (eNB 2).
HPLMN Home Public Land Mobile The HPLMN identifies the public network in which the
Network (PLMN) subscriber’s profile is held. Users roaming to other networks
will receive subscription information from the HPLMN.
HSDPA High Speed Downlink Packet HSDPA is an enhanced third-generation (3G) communications
Access protocol which allows networks based on Universal Mobile
Telecommunications System (UMTS) to have higher data
speeds.
HSPA High Speed Packet Access HSPA is a telecommunications technology that allows for data
transmission speeds up to 21 Mbps. HSPA+ (also called Evolved
HSPA or 4G) is a further evolution of HSPA that offers data
speeds of up to 42 Mbps.
HSS Home Subscriber Server HSS is the master user database that supports Internet
216
Protocol Multimedia Subsystem (IMS) network entities that
handle data sessions.
HSUPA High Speed Uplink Packet HSUPA is an amalgamation of two mobile protocols, High
Access 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 Interference ICI is an impairment known to degrade performance of
Orthogonal Frequency Division Multiplexing (OFDM)
transmissions. It arises from carrier frequency offsets (CFOs),
from the Doppler spread due to channel time variation, and, to
a lesser extent, from sampling frequency offsets (SFOs).
ICIC Inter-cell Interference ICIC techniques apply restrictions to the radio resource
Coordination 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 Fourier
Transform Transform (DTFT) samples as coefficients of complex sinusoids
at the corresponding DTFT frequencies. It has the same
sample-values as the original input sequence.
IEEE Institute of Electrical and The IEEE is a technical professional organization whose
Electronics Engineers purpose is to educate and advance electrical and electronic
engineering, telecommunications, computer engineering, and
allied disciplines.
IETF Internet Engineering Task The IETF is the body that defines standard internet operating
Force protocols such as TCP/IP.
IFFT Inverse Fast Fourier 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 mobile
Equipment Identity phone sets.
IMS Internet Protocol (IP) The IMS or IP Multimedia Core Network Subsystem is an
Multimedia Subsystem architectural framework for delivering IP multimedia services.
IMSI International Mobile An IMSI is used to identify the user of a cellular network and is
Subscriber Identity a unique identification associated with all cellular networks.
IMT International Mobile IMT is a set of requirements issued by the International
Telecommunication Telecommunication Union (ITU-R) in 2008 for what is marketed
as 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.
217
IPSec Internet Protocol Security IPSec is a protocol suite for secure internet
protocol communications that works by authenticating and
encrypting each IP packet of a communication session.
IPv4 Internet Protocol Version 4 IPv4 is the fourth revision of the internet protocol (IP) and a
widely-used protocol in data communications over various
kinds of networks. IPv4 is a connectionless protocol used in
packet-switched layer networks, such as Ethernet.
ISI Inter-Symbol Interference ISI is a form of distortion of a signal in which one symbol
interferes with subsequent symbols. This is an unwanted
phenomenon, as the previous symbols have a similar effect as
noise, thus making the communication less reliable.
ISUP Integrated Services Digital ISUP is the protocol used to support the signaling necessary to
Network (ISDN) Signaling provide voice and non-voice services in telephone
User Part 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 purpose is to
Telecommunication Union coordinate telecommunication operations and services
throughout the world.
KBPS Kilobits per Second In the U.S., Kbps means thousands of bits per second and is a
measure of bandwidth on a data transmission medium.
KHz Kilohertz KHz is a measure of frequency equivalent to 1,000 cycles per
second.
KPI Key Performance Indicator In the context of a telecommunications network, a KPI is a
quantifiable measure used to evaluate the success of network
performance (speed, quality). Typically, network operators will
monitor several types of KPIs to determine whether changes
may be needed to improve network performance.
L1 Layer 1 In the seven-layer Open Systems Interconnection (OSI) model
of computer networking, the physical layer (PHY), or L1, is the
first and lowest layer. The physical layer defines the means of
transmitting raw bits rather than logical data packets over a
physical link connecting network nodes.
L2 Layer 2 The data link layer, or L2, is the second layer of the seven-
layer Open Systems Interconnection (OSI) model of computer
networking. L2 is the protocol layer that transfers data
between adjacent network nodes in a wide area network
(WAN) or between nodes on the same local area network
(LAN) segment.
L3 Layer 3 The network layer, or L3, is the third layer of the seven-layer
Open Systems Interconnection (OSI) model of computer
networking. L3 is responsible for packet forwarding, including
routing through intermediate routers, since it knows the
address of neighboring network nodes. It also manages quality
218
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 their
Code 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 for Third-
Multicast Service Generation Partnership Project (3GPP) cellular networks. The
specification is designed to provide efficient delivery
of broadcast and multicast services, both within a cell as well
as within the core network.
MBR Maximum Bit Rate The MBR is the maximum number of bits that can be conveyed
or processed per unit of time.
MBSFN Multimedia Broadcast MBSFN is a transmission mode which exploits LTE’s Orthogonal
219
Multicast Service (MBMS) Frequency Division Multiplexing (OFDM) radio interface to
Single Frequency Network send multicast or broadcast data as a multicell transmission
over a synchronized single-frequency network.
MCC Mobile Country Code An MCC is used to uniquely identify the operator of a
telecommunications network. MCC + MNC = PLMN.
MCCH Multicast Control Channel The MCCH is a sublayer of Layer 2 protocol of Radio Interface
Protocol Architecture as per the Broadcast/Multicast Control
Standard (BMC-STD). It exists in the user plane only and is
located above the Radio Link Control, a Layer 2 function
responsible for mapping logical channels.
MCH Multicast Channel An MCH (one-to-many or many-to-many distribution) is a
group communication where information is addressed to a
group of destination computers simultaneously.
MCM Multi-Carrier Modulation MCM is a method of transmitting data by splitting it into
several components, and sending each of these components
over separate carrier signals. The individual carriers have
narrow bandwidth, but the composite signal can have broad
bandwidth.
MCS Modulation and Coding MCS is a numerical index based on Orthogonal Frequency
Scheme Division Multiplexing (OFDM) that represents the maximum
data rate that can be achieved over-the-air. The MCS index
value comprises several variables, including channel width,
modulation type, coding rate, and spatial streams. Link to MCS
index for 802.11n and 802.11ac: http://mcsindex.com/
ME Mobile Equipment ME is the device that the customer uses to originate and
receive calls in a wireless network, or a radio terminal used for
radio communication over the Um* interface.
*It is called Um because it is the mobile analog to the
U interface of an Integrated Services Digital Network (ISDN).
MGCF Media Gateway Control The MGCF controls the resources in media gateways with an
Function 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 Block MIB is a very important message or information that is
broadcasted by the Long-Term Evolution (LTE) eNB,
irrespective of any users’ presence. The MIB is first among the
other system information blocks (SIB), which are also
broadcasted by the eNB.
MIMO Multiple Input Multiple MIMO is an antenna technology for wireless communications
Output in which multiple antennas are used at both the source and the
220
destination. The antennas at each end of the communications
circuit are combined to minimize errors and optimize data
speed.
MIP Mobile IP MIP is an Internet Engineering Task Force (IETF) standard
communications protocol that is designed to allow
mobile device users to move from one network to another
while maintaining a permanent IP address.
MISO Multiple Input Single Output MISO is an antenna technology for wireless communications in
which multiple antennas are used at the source (but not at the
destination). The antennas are combined to minimize errors
and optimize data speed.
MMD Multimedia Domain MMD is essentially a version of the Third-Generation
Partnership Project (3GPP) Internet Protocol (IP) Multimedia
Subsystem (IMS) architecture that has been adapted by
3GPP2. In Code Division Multiple Access (CDMA) networks, the
terms IMS and MMD are often used interchangeably, even
though, technically, IMS is a subset of MMD.
MME Mobility Management Entity The Long-Term Evolution (LTE) MME is responsible for
initiating paging and authentication of mobile devices.
MMEGI MME Group Identity A group of Mobility Management Entities (MMEs) is assigned
an MMEGI, which works along with Mobility Management
Entity Code (MMEC) to make an MME identifier (MMEI). An
MMEI uniquely identifies the MME within a network.
MML Man-Machine Language MML is a standardized computing interface language for
managing telecommunications network devices from a
console.
MMS Multimedia Messaging 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 multimedia content
Multicast Service (MBMS) from one device to another.
Traffic Channel
MTU Maximum Transmission Unit The size of the largest network layer protocol data unit that
can be communicated in a single network transaction
NACK Negative Acknowledgement NACK is a signal used in digital communications to ensure that
221
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 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 that allow
System 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 used as a
Division Multiplexing 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 access is
Division Multiple Access achieved in OFDMA by assigning subsets of subcarriers to
individual users.
OMC Operations Management The Baicells OMC is a Cloud-based network management
Console 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 Process
Embedding (OLE) for Process Control is a series of standards for industrial
Control telecommunications, and which enable real-time plant data
between control devices from different manufacturers.
OSS Operations Support System An OSS is a set of programs that help a communications service
provider monitor, control, analyze, and manage a telephone or
computer network. The Baicells OSS, or BOSS, allows operators
to manage mobile subscriber information.
222
PAPR Peak-to-Average Power PAPR is the relationship between the maximum power of a
Ratio sample in a transmitted Orthogonal Frequency Division
Multiplexing (OFDM) symbol and its average power.
PBCH Physical Broadcast Channel The PBCH carries system information for user equipment
requiring access to the network. It only carries what is termed
Master Information Block, or MIB, messages.
PCC Policy and Charging Control Network function that enables application servers to
dynamically control the QoS and charging requirements
of the services they deliver. Also improves roaming
services. PCC is necessary for operators to differentiate
and monetize LTE services.
PCCH Paging Control Channel PCCH is a downlink channel that transfers paging information.
This channel is used when the network does not know the
location cell of the user equipment (UE), or the UE is in the cell
connected state but utilizing UE sleep mode procedures.
PCEF Policy and Charging A serving gateway (SGW) function that enforces gating and
Enforcement Function QoS for individual IP flows.
PCFICH Physical Control Format The PCFICH is one of the control channels that works at Layer
Indicator Channel 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 that
Function provides policy control and flow based charging control
decisions.
PDCCH Physical Dedicated Control The PDCCH carries a message called Downlink Control
Channel Information (DCI), which includes resource assignments for
user equipment.
PDCP Packet Data Convergence PDCP is specified by the Third-Generation Partnership Project
Protocol (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
223
(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 Shared The PDSCH is the main data bearing channel which is allocated
Channel 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 Automatic The PHICH in the downlink carries Hybrid ARQ
Repeat Request (ARQ) acknowledgements/negative acknowledgements (ACK/NACK)
Indicator Channel for uplink data transfers. PHICHs are in the first Orthogonal
Frequency Division Multiplexing (OFDM) symbol of each
subframe.
PHY Physical Layer The PHY layer is the first layer of the Open System
Interconnection Model, or Layer 1. The physical layer deals
with bit-level transmission between different devices and
supports electrical or mechanical interfaces connecting to the
physical medium for synchronized communication.
PLMN Public Land Mobile Network A PLMN is any wireless communications system intended for
use by terrestrial subscribers in vehicles or on foot. Such a
system can stand alone, but often it is interconnected with a
fixed system such as the public switched telephone network.
PMCH Physical Multicast Channel The PMCH is a transmission channel that is used to transfer
information from one source to one or more devices (multiple
receiving points) that are operating within a radio coverage
area. The PMCH carries the multicast channel (MCH).
PMIP Proxy Mobile IP (MIP) PMIP is a network-based mobility management protocol
standardized by Internet Engineering Task Force (IETF) and
specified in RFC 5213.
PN Pseudo-Random Noise PN is a signal noise which satisfies one or more of the standard
tests for statistical randomness. Although it seems to lack any
224
definite pattern, PN consists of a deterministic sequence of
pulses that repeat after a certain period.
PRACH Physical Random-Access PRACH is a Layer 1 channel used by wireless terminals to
Channel 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 paging
Temporary Identity messages, and is carried by the Paging Control Channel (PCCH)
logical channel which is mapped to the Paging Channel (PCH)
transport channel. The PCH transport channel is mapped to the
Physical Downlink Shared Channel (PDSCH) physical channel.
P-SCH Primary Synchronization The P-SCH is a code that is repeated at the beginning of each
Channel 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 Unit The PSDU is referred to in the Institute of Electrical and
Electronics (IEEE) 802.11 standard as the Media Access Control
Packet Data Unit (MPDU) with an additional Physical Layer
Convergence Procedure (PLCP) preamble and header. The term
typically references physical layer operations.
PSTN Public Switched Telephone The PSTN is the aggregate of the world’s circuit-switched
Network 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 Information (UCI).
Channel 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 Quadrature
Channel Phase Shift Keying (QPSK) and 16 Quadrature Amplitude
Modulation (QAM), with 64QAM being optional.
QAM Quadrature Amplitude QAM is both an analog and a digital signal modulation scheme.
Modulation 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.
225
QCI Quality of Service (QoS) Class QCI is a mechanism used in Third-Generation Partnership
Identifiers 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.
QPSK Quadrature Phase Shift QPSK is a form of Phase Shift Keying (PSK) in which two bits are
Keying modulated at once, selecting one of four possible carrier phase
shifts (0, 90, 180, or 270 degrees). QPSK allows the signal to
carry twice as much information as ordinary PSK using the
same bandwidth.
RACH Random Access Channel RACH is a shared channel used by wireless terminals to access
the mobile network for call setup and bursty data
transmission.
RAN Radio Access Network A RAN is part of a mobile telecommunications system.
Conceptually, the RAN resides between a mobile device and
the core network.
RAT Radio Access Technology RAT is the underlying physical connection method for a radio-
based communication network.
RB Radio Bearer An RB is a channel offered by Layer 2 to higher Open System
Interconnection (OSI) layers for the transfer of either user or
control data. In other words, Layer 2 offers to the upper layers
the service of information transmission between the user’s
equipment and the Universal Terrestrial Radio Access Network
(UTRAN) by means of the RBs and signaling RBs.
RB Resource Block An RB is a time and frequency resource that occupies 12
subcarriers (12×15 KHz = 180 KHz) and one slot (= 0.5 ms). RBs
are allocated in pairs by the scheduler (then referred to as
scheduling blocks).
RF Radio Frequency RF is any of the electromagnetic wave frequencies that lie in
the range extending from approximately 3 KHz to 300 GHz,
which include those frequencies used for communications or
radar signals.
RLC Radio Link Control RLC is a Layer 2 protocol used on the air interface in Universal
Mobile Telecommunications System (UMTS) and Long-Term
Evolution (LTE) networks.
ROCH Robust Header Compression ROCH is a standardized method to compress the Internet
Protocol (IP), User Datagram Protocol (UDP), UDP-Lite, Real-
Time Transport Protocol (RTP), and Transmission Control
Protocol (TCP) headers of internet packets.
RRC Radio Resource Control The RRC protocol is used on the air interface in Universal
Mobile Telecommunications System (UMTS) and Long-Term
226
Evolution (LTE) networks. RRC handles the control plane
signaling of Layer 3 between the user equipment and the Radio
Access Network (RAN) - either Universal Terrestrial Radio
Access Network (UTRAN) or Evolved UTRAN (E-UTRAN) - as
well as for the radio interface between a relay node and the E-
UTRAN.
RRM Radio Resource 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 Received The RSRP is the linear average over the power contributions
Power 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 Received The RSRQ reflects the relative ratio of signal and interference
Quality 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 the user
Indicator equipment has received, including the intra-frequency signal
and interference, the inter-frequency interference, and
thermal noise.
RTO Retransmission Timeout An RTO occurs when a sender is missing too many
acknowledgements and then takes a timeout or stops sending
packets altogether. The sender usually starts sending again
after this brief delay. Too many of these can cause delays on
the network for all users. Analyzing RTOs can help identify
packet loss and to locate congested links.
RTT Round Trip Time The length of time it takes for a signal to be sent plus the
length of time it takes for an acknowledgement of that signal
to be received.
S1-U Single 1 User Plane The S1-U interface is the interface between the Long-Term
Evolution (LTE) Radio Access Network (RAN) and the Evolved
Packet Core (EPC) transport network layer’s Mobility
Management Entity (MME) interface built on the Internet
Protocol (IP) transport eNB control plane. S1-U supports the
tunneling of end-user packets between the eNB and the User
Plane Entity (UPE).
SAE System Architecture SAE is the core network architecture of the Third-Generation
Evolution Partnership Project’s (3GPP’s) Long-Term Evolution (LTE)
wireless communications standard.
227
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 users to a
Division Multiple Access shared communication resource. It is also called Linearly Pre-
coded OFDMA (LP-OFDMA)
SCH Synchronization Channel An SCH is a downlink control channel used in Global System for
Mobile Communication (GSM) cellular telephone systems. It is
part of the Unacknowledged Mode (Um) air interface
specification. The purpose of the SCH is to allow the mobile
device to identify a nearby cell quickly and synchronize to an
eNB.
SCTP Stream Control Transmission The SCTP is a transport layer protocol, serving in a similar role
Protocol 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) Division SDMA is a satellite communications mode that optimizes the
Multiple Access use of radio spectrum and minimizes system cost by taking
advantage of the directional properties of dish antennas.
SDU Service Data Unit An SDU is a unit of data that has been passed down from an
OSI layer to a lower layer and that has not yet been
encapsulated into a protocol data unit (PDU) by the lower
layer.
SFP Small Form-Factor Pluggable An SFP is a small transceiver that plugs into the SFP port of a
network switch and connects to fiber and Gigabit Ethernet
(GbE) optical fiber cables at the other end. Superseding the
Gigabit Interface Converter (GBIC) transceiver, SFP modules
are also called "mini-GBIC" due to their smaller size.
SG Signaling Gateway An SG is a network component responsible for transferring
signaling messages (e.g., information related to call
establishment, billing, location, short messages, address
conversion, and other services) between Common Channel
Signaling (CCS) nodes that communicate using different
protocols and transports.
S-GW Serving Gateway The S-GW resides in the user plane where it forwards and
routes packets to and from the eNB and packet data
network (PDN) gateway.
SI System Information The SI provides information to the user equipment about
various parameters of both the Access Stratum (AS) and Non-
Access Stratum (NAS).
SI-1 System Information Message SI messages inform mobile devices about all important
1 parameters of how to access the network and how to find
neighboring cells.
228
SIB System Information Block A SIB carries relevant information for the user equipment (UE),
which helps the UE to access a cell, perform cell reselection,
and obtain information related to intra-frequency, inter-
frequency, and inter-Radio Access Technology (RAT) cell
selections.
SIM Subscriber Identity Module A SIM card is an integrated circuit that stores a mobile
subscriber’s critical information securely
SIMO Single Input Multiple Output SIMO is an antenna technology for wireless communications in
which multiple antennas are used at the destination (receiver),
but not at the transmitter. The antennas are combined to
minimize errors and optimize data speed. The source
(transmitter) has only one antenna.
SINR Signal-to-Interference-plus- Signal-to-Interference-plus-Noise-Ratio (SINR), also known as
Noise Ratio 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 Protocol SIP is a communications protocol for signaling and controlling
multimedia communication sessions.
SIR Signal-to-Interference Ratio See “SINR”.
SMS Short Message Service SMS is a text messaging service that uses standardized
communications protocols to enable fixed line or mobile
phone devices to exchange short text messages.
SN Service Node An SN is a switching point that comprises a point of end-user
access to the network and network services.
SNR Signal-to-Noise Ratio The SNR is a measure that compares the level of a desired
signal to the level of background noise. It is defined as the ratio
of signal power to the noise power, often expressed in
decibels.
SOFDMA Scalable Orthogonal SOFDMA refers to the air interface outlined for portable or
Frequency Division Multiple mobile WiMAX systems by the Institute of Electrical and
Access 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 Resource
Controller Control (RRC) connection with user equipment (UE), it is
known as the Serving RNC, or SRNC, for that UE. The SRNC is
responsible for the user’s mobility within the Universal
Terrestrial Radio Access Network (U-TRAN) and is also the
point of connection towards the core network.
229
STC Space-Time Coding STC is a technique used in wireless communications to transmit
multiple copies of a data stream across several antennas and
to exploit the various received versions of the data to improve
the overall reliability of the data transfer.
TA Tracking Area A TA manages and represents the locations of user equipment.
Through re-optimization, the network design is successively
improved by reassigning some cells to TAs other than their
original ones.
TAI Tracking Area Identifier The TAI is the identity used to identify tracking areas (TAs). The
TAI is constructed from the Mobile Country Code (MCC),
Mobile Network Code (MNC) and Tracking Area Code (TAC).
TDD Time Division Duplex TDD is a transmission scheme that allows asymmetric flow for
uplink and downlink data transmission. TDD refers to duplex
communication links where the uplink traffic is separated from
the downlink traffic by allocating different time slots in the
same frequency band.
TEID Tunnel Endpoint Identifier The separate tunnels between each set of end points are
identified by a TEID in the General Packet Radio Service
Tunneling Protocol for User Data (GTP-U) messages, normally a
dynamically allocated random number.
TFT Traffic Flow Template The TFT is used by the Gateway General Packet Radio Service
Support Node (GGSN) to discriminate between different user
payloads. The TFT incorporates packet filters such as quality of
service (QoS), Policy Decision Point (PDP) context, and security.
TM Transparent Mode TM is one of the three modes used to transfer the upper layer
Protocol Data Units (PDUs) via the Radio Link Control (RLC).
TTI Transmission Time Interval TTI is a parameter in Universal Mobile Telecommunications
System (UMTS) and other digital telecommunication networks
that refers to the duration of a transmission on the radio link.
TTI is related to encapsulation of data from higher layers into
frames for transmission on the Radio Link Layer (RLL).
UARFCN Universal Mobile In short, this is the frequency point of a neighboring eNB’s
Telecommunications System frequency.
(UMTS) Absolute Radio
Frequency Channel Number.
UCI Uplink Control Information The UCI is a set of information that is carried by the Physical
Uplink Control Channel (PUCCH). Depending on what kind of
information the UCI in the Physical Dedicated Control
Channel (PDCCH) carries, 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
230
customer premise equipment, or CPE) is any device used
directly by an end-user to communicate via the network.
UL Uplink The UL path of a network connection is used to send data from
the user equipment to the network.
UL-SCH Uplink Shared Channel A physical UL-SCH is a transmission channel that is used to
transport user data from one or more mobile devices that can
transmit on the channel.
UM Unacknowledged Mode UM is one of three modes used to transfer upper layer
Protocol Data Units (PDU) in Radio Link Control (RLC) used on
the air interface in Long-Term Evolution (LTE) networks.
UMA Unlicensed Mobile Access UMA is a technology that allows UMA-capable user
equipment to switch back and forth seamlessly
between networks and local wireless networks.
UMTS Universal Mobile UMTS is a third-generation broadband, packet-based
Telecommunications System transmission of text, digitized voice, video, and multimedia at
data rates up to and possibly higher than 2 megabits per
second (Mbps).
UPnP Universal Plug and Play UPnP is a set of networking protocols that permits devices
such as personal computers, printers, internet gateways, Wi-
Fi access points, and mobile devices to discover each other's
presence on the network and communicate. UPnP is intended
primarily for residential users and not enterprise-class devices.
UpPTS Uplink Pilot Time Slot The UpPTS is one of the three fields that make up the 1ms
special subframes that comprise the half-frames used in the
Long-Term Evolution (LTE) Time Division Duplex (TDD) frame
structure.
UpTS  Uplink Time Slot In Time Division Long-Term Evolution (TD-LTE) networks,
the UpTS allows the user equipment to transmit data to
the receiver.
USIM Universal Subscriber Identity A SIM card is an integrated chip that securely stores a mobile
Module subscriber’s critical information for Global (GSM) networks. A
USIM provides enhanced features and allows a subscriber to
access any Universal Mobile Telecommunications System
(UMTS) network, including GSM and CDMA.
VoIP Voice over Internet Protocol VoIP is a service that enables people to make voice calls using
only their computers connected to the network. With VoIP, the
internet is the transmission medium for telephone calls 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 Mobile VPLMN is the network on which the mobile subscriber has
Network (PLMN) roamed when leaving their Home 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
231
subcarriers (distributed) to maximize frequency diversity.
WCDMA Wideband Code Division WCDMA is a third-generation standard that employs the Direct
Multiple Access Sequence CDMA (DS-CDMA) channel access method and the
Frequency Division Duplexing (FDD) method to provide high-
speed and high-capacity service.
Wi-Fi Wi-Fi Wi-Fi is the marketing name for a standard defined by the
Institute for Electrical and Electronics Engineering (IEEE) called
802.11x. In the same way that a local area network (LAN)
describes the cabled connection of residential or business
computing devices in the same geographical or logical domain,
Wi-Fi describes the wireless connection of residential or
business computing devices in the same geographical or logical
domain. Wi-Fi also is referred to as wireless LAN (WLAN).
WiMAX Worldwide Interoperability WiMAX is a family of wireless communication standards based
for Microwave Access on the Institute for Electrical and 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
232
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/
233
Appendix D: CloudKey
Certain versions of user equipment (UE) firmware (for example, version 1.0.8) allow the operator to
pre-configure the UE to connect to the operator’s network. Baicells assigns a unique CloudKey to each
operator. The operator enters their CloudKey account information in the UE Web GUI or through BOSS,
as explained below. The operator’s CloudKey may be viewed in the top right corner of their CloudCore
account and on the CloudCore > Operator Info page.
UE GUI:
NOTE: The CloudKey field described below is not available in certain versions of software.
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 appear in the OMC
Monitor window. A reboot is not required for this field to take effect.
BOSS:
Alternatively the operator can use BOSS to add the UE. Refer to section 4.5.2 Subscriber.
234

Configuration - & - Network - Administration - Guide - (SRv1.12 - 4-Sep-2018) (NXP) PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Configuration - & - Network - Administration - Guide - (SRv1.12 - 4-Sep-2018) (NXP) PDF

Загружено:

Авторское право:

Доступные форматы

Configuration & Network

UE – Gen 1 Atom 5dBi Indoor CPE User Manual

China North America

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

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

The key components of a Baicells system include:

Figure 1-1: Example Baicells Architecture

Figure 1-2: Sample UE GUI Window

Figure 1-3: UE & eNB GUI Menu Trees

Figure 1-6: CloudCore GUI Menu Trees

2.1 Computer Requirements

Table 2-1: Computer Requirements

Figure 2-1: Internet Protocol Version (TCP/IPV4)

2.2 Launching the GUI

Figure 2-2: eNB GUI Login

2.3 Data Preparation

2.4 Configuration Flow

Figure 2-4: Initial Configuration Flow

2.5 BTS Info

2.5.1 Basic Info

Figure 2-6: Basic Info (HaloB-Enabled eNB)

Field Name Description

Table 2-3: Status Info Fields

Field Name Description

NOTE: Although it appears as a sync option in the GUI, 1588

Table 2-4: UE Status Fields

Field Name Description

NOTE: This field is not visible on a Nova-243 eNB running

IP Internet Protocol address for the eNB

2.5.2 Quick Setting

Figure 2-7: Quick Setting (Standard eNB)

Table 2-5: Quick Setting

Field Name Description

Figure 2-9: NTP

Table 2-6: NTP

Figure 2-10: Upgrade

Figure 2-12: Password Window

Table 2-7: Internet / WAN

Field Name Description

2.7.4 IPSec/MME Pool

Table 2-8: Tunnel Configure > Basic Setting Fields

Field Name Description

Figure 2-19: Tunnel Configure > Advance Setting

Table 2-9: Tunnel Configure > Advance Setting

Field Name Description

Figure 2-20: LGW Setting (Bridge, NAT, & Router Modes)

Figure 2-21: CertStore

2.7.7 Static Routing

2.8 BTS Setting

Figure 2-23: BTS Setting - Standard & HaloB eNBs

Figure 2-24: Security Setting

2.8.2 Management Server

2.8.3 Sync Setting

Figure 2-26: Sync Setting

2.8.4 HaloB Setting

2.8.5 License Management

2.9.1 Identify Neighbor Frequencies and Cell Information

2.9.1.1 LTE Freq/Cell

2.9.1.1.1 LTE Neigh Freq Table

Figure 2-30: Neigh Freq Table

Table 2-10: LTE Neigh Freq Settings

Field Name Description

2.9.1.1.2 LTE Neigh Cell Table