operation, maintenance, & troubleshooting guide...this operation, maintenance, and...

Operation, Maintenance, & Troubleshooting Guide

October 2018

Version 1.8

ii

About This Document This operation, maintenance, and troubleshooting (OMT) document is written for Wireless Internet Ser-vice Providers (WISP) and network operators. The information is intended for technical support and net-work administration personnel involved in operating Baicells networks, monitoring network performance, and troubleshooting hardware and software issues. Such personnel should already be familiar with the Baicells network components and features. Please refer to the Related Documents section for more infor-mation on available resources. In particular, refer to the Baicells Configuration & Network Administration Guide for information concerning network and feature configuration procedures.

This version of the OMT guide 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.1

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 Tech-nologies, 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.

iii

Revision Record Date Version Description Contributors/SMEs Author/Editor 1-Oct-2018 V1.8,

V1.7 Added newer alarms. Updated for latest GUIs and features; added information about dual carrier eNBs.

Nitisha Potti Cameron Kilton Wu Junfeng

Sharon Redfoot

5-Apr-2018 V1.6, V1.5, V1.4, V1.3

Updated for the following and incorpo-rated SME feedback: Standard TDD eNB version: BaiSta-tion_V100R001C00B110SPC009; 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.2.2 UE Gen 1 version: BCE-ODU-1.0.12; UE Gen2 version: BaiCPE-V100R001C01B004SPC107 OMC version: 3.4.4 BOSS version: 3.4.1

Nitisha Potti Sonny May Shawn (caojianhua) Samuel (Tang Weizhuo) Ronald Mao Rick Harnish Cameron Kilton

Sharon Redfoot

2-Jan-2018 V1.2 SME feedback Nitisha Potti Sonny May Tang Weizhuo (Samuel)

Sharon Redfoot

18-Dec-2017 V1.1 Updated HaloB, operation, maintenance, SME feedback

Jesse Raasch Cameron Kilton Nitisha Potti Tang Weizhuo (Samuel)

Sharon Redfoot

5-Dec-2017 V1.0 Draft Nitisha Potti Cameron Kilton Jesse Raasch Wu Junfeng Tang Weizhuo (Samuel)

Sharon Redfoot

Related Documents Other Baicells technical documents may be found on the Baicells support website: https://na.baicells.com/downloads/

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

https://na.baicells.com/downloads/

iv

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


CloudCore, System, OAM

Baicells Configuration & Network Administration Guide

Baicells Handoff Configuration Guidelines (Beta)

Baicells HaloB User Guide

Dual Carrier Configuration Quick Start Guide

Baicells BOSS API Manual

Baicells Operation, Maintenance, & Troubleshooting Guide (this document)

Contact Us Baicells Technologies Co., Ltd.

China North America

Address: 3F, Bldg. A, No. 1 Kai Tuo Rd, Haidian Dist, Beijing, China

Address: 555 Republic Dr., #200, Plano, TX 75074, USA

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

E-mail: [email protected] Email: [email protected] or [email protected]

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

mailto:[email protected]




http://www.baicells.com/

https://na.baicells.com/

v

Table of Contents 1. INTRODUCTION ............................................................................................................................................. 1

1.1 OVERVIEW ....................................................................................................................................................... 1 1.2 OMT TOOLS & RESOURCES ................................................................................................................................ 1

2. NORMAL NETWORK OPERATION ................................................................................................................... 3 2.1 LTE ................................................................................................................................................................ 3

2.1.1 Overview .................................................................................................................................................. 3 2.1.2 eNB Startup ............................................................................................................................................ 5 2.1.3 Random Access Procedure ....................................................................................................................... 7 2.1.4 Authentication Procedure ...................................................................................................................... 10 2.1.5 NAS Security Setup Procedure ................................................................................................................ 11 2.1.6 Location Update Procedure.................................................................................................................... 12 2.1.7 EPS Session Establishment ..................................................................................................................... 13 2.1.8 EPS Bearer .............................................................................................................................................. 19

2.2 BAICELLS CLOUDCORE DESIGN ........................................................................................................................... 24 2.3 FIXED WIRELESS WITH NO EPC .......................................................................................................................... 27

2.3.1 EPC Concerns .......................................................................................................................................... 27 2.3.2 Baicells HaloB Solution ........................................................................................................................... 29

3. FACTORS AFFECTING NETWORK PERFORMANCE ......................................................................................... 32 4. MAINTENANCE ............................................................................................................................................ 33

4.1 GENERAL PRACTICES ........................................................................................................................................ 33 4.2 OMC - DASHBOARD MONITORING .................................................................................................................... 33

4.2.1 Overview ................................................................................................................................................ 33 4.2.2 Alarms and Logs ..................................................................................................................................... 34 4.2.3 Statistics & Performance ........................................................................................................................ 59 4.2.4 eNB......................................................................................................................................................... 62 4.2.5 CPE ......................................................................................................................................................... 62

4.3 OMC - ENB .................................................................................................................................................. 63 4.3.1 Monitor ................................................................................................................................................... 64 4.3.2 Maintenance ........................................................................................................................................... 68 4.3.3 Register ................................................................................................................................................... 68 4.3.4 Upgrade .................................................................................................................................................. 69

4.4 OMC - CPE ....................................................................................................................................................... 69 4.4.1 Monitor .................................................................................................................................................. 69 4.4.2 Maintenance .......................................................................................................................................... 70 4.4.3 Register .................................................................................................................................................. 70 4.4.4 Upgrade ................................................................................................................................................. 70

4.5 OMC - STRATEGY > PCI LOCK ............................................................................................................................... 70 4.6 OMC - SYSTEM ................................................................................................................................................. 71

vi

4.6.1 Security .................................................................................................................................................. 71 4.6.2 OMC Log ................................................................................................................................................ 71

4.7 BOSS MONITORING ............................................................................................................................................. 73 4.8 ENB GUI MONITORING ........................................................................................................................................ 73

4.8.1 Additional eNB GUI BTS Info Fields ........................................................................................................ 74 4.8.2 Additional eNB GUI System Fields .......................................................................................................... 74 4.8.3 Additional eNB GUI Network Fields ....................................................................................................... 74 4.8.4 Additional eNB GUI BTS Settings ............................................................................................................ 74 4.8.5 Additional eNB GUI LTE Settings ............................................................................................................ 75

4.9 UE GUI MONITORING .......................................................................................................................................... 75 4.9.1 Additional UE GUI Status Fields ............................................................................................................. 75 4.9.2 Additional UE GUI Network Fields .......................................................................................................... 75 4.9.3 Additional UE GUI LTE Fields .................................................................................................................. 76 4.9.4 Additional UE GUI Security Fields ........................................................................................................... 76 4.9.5 Additional UE GUI VPN Fields ................................................................................................................ 76 4.9.6 Additional UE GUI System Fields ............................................................................................................ 76

4.10 ADDITIONAL KPI INFORMATION ........................................................................................................................ 76 4.10.1 Overview ............................................................................................................................................ 76 4.10.2 Monitor Channel Conditions .............................................................................................................. 77 4.10.3 Monitor LAN and WAN Backhaul ....................................................................................................... 80

4.11 CAPACITY PLANNING ...................................................................................................................................... 91 5. TROUBLESHOOTING .................................................................................................................................... 93

5.1 UE ISSUES ..................................................................................................................................................... 93 5.2 ENB ISSUES .................................................................................................................................................. 112 5.3 BACKHAUL, RF, AND OTHER ISSUES .................................................................................................................. 122

APPENDIX A: LTE REFERENCES............................................................................................................................ 125 APPENDIX B: ANTENNA BASICS – COVERAGE VS INTERFERENCE DO’S AND DON’TS .......................................... 128 APPENDIX C: RF / NETWORK PLANNING CONSIDERATIONS ............................................................................... 137 APPENDIX D: FAQS ............................................................................................................................................. 143

List of Figures FIGURE 2-1: UMTS ARCHITECTURE ....................................................................................................................................... 3 FIGURE 2-2: UE TO PGW INTERFACES ................................................................................................................................... 4 FIGURE 2-3: UE TO MME INTERFACES ................................................................................................................................... 5 FIGURE 2-4: S1 CONNECTION ............................................................................................................................................... 5 FIGURE 2-5: MIB AND SIB BROADCAST.................................................................................................................................. 6 FIGURE 2-6: RANDOM ACCESS PROCEDURE (1 OF 3) ................................................................................................................ 7 FIGURE 2-7: RANDOM ACCESS PROCEDURE (2 OF 3) ................................................................................................................ 8 FIGURE 2-8: RANDOM ACCESS PROCEDURE (3 OF 3) ................................................................................................................ 8

vii

FIGURE 2-9: ATTACH PROCEDURE.......................................................................................................................................... 9 FIGURE 2-10: ECM CONNECTION, PART 1 .............................................................................................................................. 9 FIGURE 2-11: AUTHENTICATION PROCEDURE ......................................................................................................................... 11 FIGURE 2-12: NAS SECURITY SETUP PROCEDURE ................................................................................................................... 12 FIGURE 2-13: LOCATION UPDATE PROCEDURE ....................................................................................................................... 13 FIGURE 2-14: EPS SESSION ESTABLISHMENT, PART 1 .............................................................................................................. 14 FIGURE 2-15: EPS SESSION ESTABLISHMENT, PART 2 .............................................................................................................. 15 FIGURE 2-16: EPS SESSION ESTABLISHMENT, PART 3 .............................................................................................................. 16 FIGURE 2-17: EPS SESSION ESTABLISHMENT, PART 4 .............................................................................................................. 17 FIGURE 2-18: EPS SESSION ESTABLISHMENT, PART 5 .............................................................................................................. 18 FIGURE 2-19: EPS SESSION ESTABLISHMENT, PART 6 .............................................................................................................. 19 FIGURE 2-20: EPS BEARER, PART 1 ..................................................................................................................................... 20 FIGURE 2-21: EPS BEARER, PART 3 ..................................................................................................................................... 21 FIGURE 2-22: EPS BEARER, PART 4 (SDF) ........................................................................................................................... 21 FIGURE 2-23: EPS BEARER, PART 6 (QOS PROVISIONING) ....................................................................................................... 23 FIGURE 2-24: EPS BEARER, PART 7 (QOS ENFORCEMENT) ...................................................................................................... 23 FIGURE 2-25: BAICELLS CLOUDCORE ................................................................................................................................... 24 FIGURE 2-26: NAT MODE ................................................................................................................................................. 25 FIGURE 2-27: ROUTER MODE ............................................................................................................................................ 26 FIGURE 2-28: BRIDGE MODE ............................................................................................................................................. 27 FIGURE 2-29: S1 FAILURES ................................................................................................................................................ 28 FIGURE 2-30: MME POOLING ........................................................................................................................................... 28 FIGURE 2-31: TRADITIONAL LTE ARCHITECTURE ..................................................................................................................... 29 FIGURE 2-32: HALOB CELL ................................................................................................................................................ 30 FIGURE 2-33: HALOB ARCHITECTURE ................................................................................................................................... 30 FIGURE 2-34: HOW TO GET HALOB ..................................................................................................................................... 31 FIGURE 4-1: OMC DASHBOARD ......................................................................................................................................... 34 FIGURE 4-2: ALARMS ........................................................................................................................................................ 35 FIGURE 4-3: ALARM DETAILS .............................................................................................................................................. 35 FIGURE 4-4: CONFIRM OR CLEAR ALARM .............................................................................................................................. 36 FIGURE 4-5: EXPORT ......................................................................................................................................................... 37 FIGURE 4-6: HISTORY ALARM TAB ....................................................................................................................................... 37 FIGURE 4-7: ALARM > VIEW............................................................................................................................................... 38 FIGURE 4-8: SELECT TEMPLATE ........................................................................................................................................... 38 FIGURE 4-9: ADD TEMPLATE .............................................................................................................................................. 39 FIGURE 4-10: ADD TEMPLATE FIELDS ................................................................................................................................... 39 FIGURE 4-11: VIEW .......................................................................................................................................................... 40 FIGURE 4-12: QUERY ........................................................................................................................................................ 41 FIGURE 4-13: ALARM DETAILS ............................................................................................................................................ 41 FIGURE 4-14: FILTER ......................................................................................................................................................... 42 FIGURE 4-15: ADVANCED QUERY (1 OF 2) ............................................................................................................................ 42 FIGURE 4-16: ADVANCED QUERY (2 OF 2) ............................................................................................................................ 43

viii

FIGURE 4-17: ALARM > SETTINGS ....................................................................................................................................... 43 FIGURE 4-18: ALARM FILTER > SELECTED ENODEB ................................................................................................................. 44 FIGURE 4-19: ALARM TYPE ................................................................................................................................................ 44 FIGURE 4-20: SEVERITY ..................................................................................................................................................... 45 FIGURE 4-21: EVENT TIME ................................................................................................................................................. 45 FIGURE 4-22: ENABLE FILTER TEMPLATE ............................................................................................................................... 45 FIGURE 4-23: + NEW ALARM CONFIRM TEMPLATE ................................................................................................................. 46 FIGURE 4-24: VIEW CONFIG ............................................................................................................................................... 47 FIGURE 4-25: ADD NEW TEMPLATE ..................................................................................................................................... 47 FIGURE 4-26: ALARM LIBRARY ............................................................................................................................................ 48 FIGURE 4-27: NOTIFICATION .............................................................................................................................................. 49 FIGURE 4-28: STATISTICS ................................................................................................................................................... 60 FIGURE 4-29: THROUGHPUT & PRB UTILIZATION .................................................................................................................. 61 FIGURE 4-30: UE COUNT .................................................................................................................................................. 62 FIGURE 4-31: DASHBOARD ENBS ........................................................................................................................................ 62 FIGURE 4-32: DASHBOARD > CPE > MONITOR ...................................................................................................................... 63 FIGURE 4-33: ENB MENU ................................................................................................................................................. 64 FIGURE 4-34: ENB MONITOR (1 OF 3) ................................................................................................................................ 64 FIGURE 4-35: ENB MONITOR (2 OF 3) – HALOB ENB INCLUDED IN LIST .................................................................................... 65 FIGURE 4-36: ENB MONITOR (3 OF 3) – HALOB ENB INCLUDED IN LIST .................................................................................... 65 FIGURE 4-37: FILTER ......................................................................................................................................................... 67 FIGURE 4-38: WIRELESS SETTINGS > SPECIAL SF PATTERNS OPTIONS ......................................................................................... 68 FIGURE 4-39: HISTORY GRAPHS .......................................................................................................................................... 69 FIGURE 4-40: OMC OPERATION LOGS ................................................................................................................................. 72 FIGURE 4-41: OMC SECURITY LOGS .................................................................................................................................... 72 FIGURE 4-42: OMC SYSTEM LOGS ...................................................................................................................................... 73 FIGURE 4-43: RSRP/SINR ................................................................................................................................................ 77 FIGURE 4-44: A2 EVENT THRESHOLD ................................................................................................................................... 79 FIGURE 4-45: DMZ METHODS ........................................................................................................................................... 80 FIGURE 4-46: DMZ .......................................................................................................................................................... 80 FIGURE 4-47: STATIC ROUTES ............................................................................................................................................. 81 FIGURE 4-48: CONFIGURE STATIC ROUTES ............................................................................................................................ 82 FIGURE 4-49: LAN SETTINGS (1 OF 2) ................................................................................................................................. 83 FIGURE 4-50: LAN SETTINGS (2 OF 2) ................................................................................................................................. 83 FIGURE 4-51: SECURITY SUB-MENUS ................................................................................................................................... 84 FIGURE 4-52: MAC FILTER > ADD LIST ................................................................................................................................ 85 FIGURE 4-53: IP FILTER ..................................................................................................................................................... 86 FIGURE 4-54: URL FILTER .................................................................................................................................................. 87 FIGURE 4-55: PORT FORWARDING ...................................................................................................................................... 88 FIGURE 4-56: ALG ........................................................................................................................................................... 89 FIGURE 4-57: UPNP ........................................................................................................................................................ 90 FIGURE 4-58: ATTACK PROTECTION ..................................................................................................................................... 91

ix

FIGURE 5-1: USIM STATUS ................................................................................................................................................ 93 FIGURE 5-2: CELL SIGNAL .................................................................................................................................................. 94 FIGURE 5-3: BOSS USER ACTIVATION .................................................................................................................................. 94 FIGURE 5-4: DNS STATUS .................................................................................................................................................. 95 FIGURE 5-5: PING DNS SERVER .......................................................................................................................................... 96 FIGURE 5-6: RANDOM ACCESS PARAMETERS ......................................................................................................................... 99 FIGURE 5-7: SCAN METHOD ............................................................................................................................................. 100 FIGURE 5-8: PCI LOCK .................................................................................................................................................... 101 FIGURE 5-9: APN MANAGEMENT ..................................................................................................................................... 101 FIGURE 5-10: SIM LOCK SETTINGS .................................................................................................................................... 102 FIGURE 5-11: SCHEDULING ALGORITHM PARAMETERS .......................................................................................................... 103 FIGURE 5-12: SYNC ADJUST PARAMETERS .......................................................................................................................... 103 FIGURE 5-13: LINK ACTIVATION STATE DETECTOR PARAMETERS .............................................................................................. 103 FIGURE 5-14: STATUS...................................................................................................................................................... 105 FIGURE 5-15: ENB GUI > BTS SETTING > MANAGEMENT SERVER .......................................................................................... 106 FIGURE 5-16: UE GUI > SYSTEM > TR-069 ....................................................................................................................... 106 FIGURE 5-17: DNS SETTINGS ........................................................................................................................................... 107 FIGURE 5-18: NETWORK MODE ........................................................................................................................................ 108 FIGURE 5-19: BRIDGE MODE ........................................................................................................................................... 109 FIGURE 5-20: SIMPLE LTE TOPOLOGY ................................................................................................................................ 111 FIGURE 5-21: WEEP HOLES ............................................................................................................................................. 112 FIGURE 5-22: MANAGEMENT SERVER ................................................................................................................................ 112 FIGURE 5-23: IPSEC ....................................................................................................................................................... 113 FIGURE 5-24: MME IP, PLMN, TAC ................................................................................................................................ 114 FIGURE 5-25: ENB INACTIVE ............................................................................................................................................ 114 FIGURE 5-26: GPS SYNC ................................................................................................................................................. 115 FIGURE 5-27: ENB STATUS............................................................................................................................................... 117 FIGURE 5-28: IPSEC ....................................................................................................................................................... 117 FIGURE 5-29 QUICK SETTINGS .......................................................................................................................................... 118 FIGURE 5-30: OMC > ENB > MONITOR ............................................................................................................................ 118 FIGURE 5-31: ENB STATUS............................................................................................................................................... 119 FIGURE 5-32: MANAGEMENT SERVER ................................................................................................................................ 119 FIGURE 5-33: DNS ........................................................................................................................................................ 120 FIGURE 5-34: MANAGEMENT SERVER ................................................................................................................................ 120 FIGURE 5-35: CELL ID ..................................................................................................................................................... 121 FIGURE 5-36: NAT MODE ............................................................................................................................................... 123 FIGURE 5-37: BRIDGE MODE ........................................................................................................................................... 124 FIGURE A-1: RSSI VS RSRP ............................................................................................................................................. 126 FIGURE A-2: PCI ............................................................................................................................................................ 127 FIGURE B-1: THREE 120-DEGREE SECTORS (DO NOT) ......................................................................................................... 128 FIGURE B-2: THREE 90-DEGREE SECTORS (ACCEPTABLE) ....................................................................................................... 129 FIGURE B-3: FOUR 90-DEGREE SECTORS (DO NOT) ............................................................................................................ 130

x

FIGURE B-4: FOUR 65-DEGREE SECTORS (DO!) ................................................................................................................... 131 FIGURE B-5: SIX 45-DEGREE SECTORS (BEST USE!) ............................................................................................................ 132 FIGURE B-6: DOWNTILT CALCULATOR EXAMPLE ................................................................................................................... 133 FIGURE B-7: MECHANICAL VS ELECTRICAL DOWNTILT ............................................................................................................ 134 FIGURE B-8: POLARIZATION .............................................................................................................................................. 135 FIGURE C-1: PCI PLANNING ............................................................................................................................................. 138 FIGURE C-2: PSS AND SSS (1 OF 2) ................................................................................................................................... 139 FIGURE C-3: PSS AND SSS (2 OF 2) ................................................................................................................................... 139 FIGURE C-4: EXAMPLE OF PCI USAGE CALCULATION ............................................................................................................. 140

List of Tables TABLE 2-1: MIB AND SIB BROADCAST ................................................................................................................................... 6 TABLE 2-2: ECM CONNECTION, PART 2 ............................................................................................................................... 10 TABLE 2-3: EPS BEARER, PART 5 (QOS)............................................................................................................................... 22 TABLE 4-1: ALARM DETAIL ................................................................................................................................................. 36 TABLE 4-2: ALARMS ......................................................................................................................................................... 50 TABLE 4-3: WHERE TO GENERATE LOGS ............................................................................................................................... 59 TABLE 4-4: ENB MONITOR FIELDS ....................................................................................................................................... 65 TABLE 4-5: UE STATUS PARAMETERS ................................................................................................................................... 78 TABLE 4-6: DMZ ............................................................................................................................................................. 81 TABLE 4-7: LAN SETTINGS ................................................................................................................................................. 84 TABLE 4-8: MAC FILTER .................................................................................................................................................... 85 TABLE 4-9: IP FILTER......................................................................................................................................................... 86 TABLE 4-10: PORT FORWARDING ........................................................................................................................................ 89 TABLE 5-1: RANDOM ACCESS PARAMETERS .......................................................................................................................... 99 TABLE 5-2: SCAN METHOD .............................................................................................................................................. 100 TABLE 5-3: APN MANAGEMENT ....................................................................................................................................... 102 TABLE 5-4: SYNC ADJUST PARAMETERS .............................................................................................................................. 103 TABLE 5-5: LINK ACTIVATION STATE DETECTOR PARAMETERS .................................................................................................. 104 TABLE 5-6: EXAMPLE LEDS .............................................................................................................................................. 116

1

1. Introduction

1.1 Overview

The Baicells broadband wireless access solutions are based on Long-Term Evolution (LTE) mobile commu-nications standards. From User Equipment (UE) design to eNodeB (eNB) performance, all products are tested for compliance to standards and for maximum potential.

The mission of Baicells’s founding CEO, Dr. Sun Lixin, was to create an access solution that would connect more with less. His company slogan, “LTE Easy as Wi-Fi”, encapsulates the commitment that Baicells has to providing not only excellent hardware and software products at a reasonable pricepoint, but to simpli-fying the operator system interface and focusing on customer attention throughout the lifecycle of its products.

In this operations, maintenance, and troubleshooting (OMT) guide, the Baicells support team has put to-gether information that will hopefully keep your Baicells network operating smoothly and reduce any frus-tration that might result from network issues that could arise. In the spirit of continuous improvement we hope our customers keep the dialogue open with the Baicells team to help us improve our product and service offerings.

The information identifies useful tools and other resources at your disposal, discusses what normal LTE radio and network operations look like based on design intent, and walks through recommended mainte-nance tasks - the things you should probably be doing real-time and periodically.

This guide offers direction on how to assess the state of individual devices as well as how to monitor the overall network, identifies important system alarms and what to look for in event logs, and explains how to check network key performance indicators (KPIs). The troubleshooting section covers common field issues, with steps to achieve recovery.

1.2 OMT Tools & Resources

You have many tools and resources at your disposal when it comes to managing a Baicells network:

1. User Equipment (UE) GUI – Local and Web based graphical user interface application for configur-ing, monitoring, and managing individual UEs

2. eNodeB (eNB) GUI – Local and Web based graphical user interface application for configuring, monitoring, and managing individual eNBs

3. Operations Management Console (OMC) – graphical user interface for configuring, monitoring, and managing all Baicells devices - UEs and eNBs - and including Iperf and other diagnostic tools

4. Business Operations Support System (BOSS) – graphical user interface for adding and managing subscribers

5. LTE PCI assignment cheat sheet and service – Excel file and support service for managing Physical Cell Identifiers (PCI) across the network

2

6. Website and Facebook forums, and FAQs:

- Baicells support website: https://na.baicells.com/support/

- Baicells community forum: https://community.na.baicells.com

- Baicells operators support group on Facebook: https://www.face-book.com/groups/baicellsoperatorsupportgroup/

7. Product documentation and firmware downloads web page: https://na.baicells.com/downloads/

If you cannot find what you are looking for, please contact the Baicells support team.

https://na.baicells.com/support/

https://community.na.baicells.com/

https://www.facebook.com/groups/baicellsoperatorsupportgroup/


3

2. Normal Network Operation

2.1 LTE

2.1.1 Overview Whenever you experience a network issue, it helps to understand what normal traffic flows look like in order to isolate the problem to the node(s) and resolve it. Is it an RF issue? Is it a backhaul issue? Is it a security issue? This section talks about radio access network (RAN) and core traffic flows, based on a standard Long-Term Evolution (LTE) network design.

LTE is part of the Universal Mobile Telecommunications System (UMTS) networking technology evolu-tion, sometimes referred to as 3G, 4G, etc. Figure 2-1 shows the radio functional block and the core func-tional block in a UMTS network architecture. The block of radio functions is called the Enhanced Terres-trial Radio Access Network (E-UTRAN). The block of core network functions is called the Evolved Packet Core (EPC). The S1-MME interface is the path of the mobility management traffic. The S1-U is the path of the mobility user traffic.

Figure 2-1: UMTS Architecture

The E-UTRAN components include:

• User Equipment (UE): Device directly used by end-user to communicate, such as a mobile phone, tablet, laptop, or customer premise equipment (CPE).

• E-UTRAN Node B (eNodeB or eNB): Also called the base station, the eNB is the technology evo-lution of Node B in a UMTS network. The eNB terminates the air interface protocol and is the first point of contact in the network for the UE.

Notice in Figure 5-x that the E-UTRAN network interfaces are:

• X2 Interface: Used to interconnect eNBs, where traffic load and interference-related and UE ses-sion handover-related information is exchanged.

• S1 Interface: Connects the eNB to the EPC. It is split into two interfaces, the control plane (S1-MME) and user plane (S1-U).

4

The EPC elements are:

• Mobility Management Entity (MME): Responsible for user authentication (by interacting with the HSS), idle mode location tracking, paging, roaming, handovers, bearer activation / deactiva-tion process, and selecting gateways for the UE.

• Home Subscriber Server (HSS): Central database that contains user- and subscription-related information. In a Baicells system, this is where the BOSS information is saved.

• Serving Gateway (S-GW): Gateway which terminates the interface towards E-UTRAN, serving a large number of eNBs. Responsible for handovers with neighbor eNBs and data transfer across the user plane.

• Packet Data Network Gateway (PGW): Controls IP data services, routing, allocates IP addresses, enforces policies, and provides access for non-3GPP access networks such as WiMAX and 3GPP2.

• Policy and Charging Rules Function (PCRF): Interfaces with the PGW and supports service data flow detection, policy enforcement, and flow-based charging. Through configuration and the PCRF is how operators meter the amount of traffic each subscriber is using.

In terms of core network interfaces, in the user plane – from the UE to the PGW:

• IP packets in the core network are encapsulated in an EPC-specific protocol and tunneled be-tween the PGW and the eNB. The GPRS Tunnel Protocol (GTP) is used on the S1 and S5/S8 inter-faces. (S8 is used when roaming with other carriers.)

• The protocol stack between the eNB and UE consists of the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) sublayers.

Refer to Figure 2-2 for a breakdown of the UE-PGW interfaces.

Figure 2-2: UE to PGW Interfaces

5

In the control plane – from the UE to the MME:

• The control plane additionally includes the Radio Resource Control (RRC) layer, which is responsi-ble for establishing the radio bearers and configuring the lower layers.

• The control plane handling of radio-specific functionality includes:

o Cell selection and reselection procedures

o UE information on downlink channel quality and neighbor cell information

Refer to Figure 2-3 for a breakdown of the UE-MME interfaces.

Figure 2-3: UE to MME Interfaces

2.1.2 eNB Startup The following describes what happens when the eNB first starts up.

Step 1. The eNB establishes an S1 connection with the MME (Figure 2-4). The S1 setup request pa-rameters are:

• PLMN • Cell ID • Tracking Area Code (TAC)

Figure 2-4: S1 Connection

6

Step 2. The eNB starts broadcasting the Master Information Block (MIB) and System Information Block (SIB). Refer to Figure 2-5.

Figure 2-5: MIB and SIB Broadcast

The MIB is transmitted using a physical layer channel and contains the following vital system parameters and information:

• System bandwidth

• Physical Hybrid-ARQ Indicator Channel (PHICH) information

• System frame number

The SIBs carry relevant information for the UE, which helps the UE to access a cell and perform cell-reselection. There are 16 types (since R11) of SIBs, with each one having a specific task. A minimum of two SIBs is required (SIB1 and SIB2). Refer to Table 2-1.

Table 2-1: MIB and SIB Broadcast

Features Main Parameters

MIB Carries the LTE cell’s physical layer infor-mation

DL bandwidth, SubFrame Number (SFN), and PHICH configu-ration

SIB1 UE access restriction in-formation and the scheduling of other SIBs

Access restriction information, cell selection information, scheduling information list, and carries Cell ID, Mobile Coun-try Code (MCCD), Mobile Network Code (MNC), TAC

SIB2 Radio resource configu-ration common to all UEs

Common and shared channel information, Radio Resource Controller (RRC), UL power control, preamble power ramp-ing, uplink cyclic prefix length, sub-frame hopping, and uplink EARFCN

7

2.1.3 Random Access Procedure Following is what happens as the UE attempts to access the network through an eNB. Refer to Figure 2-6.

Step 1. The UE synchronizes with the downlink channel by decoding the Primary Synchronization Sig-nal (PSS) and the Secondary Synchronization Signal (SSS).

Step 2. Upon downlink channel synchronization, the MIB and SIB messages are downloaded.

Figure 2-6: Random Access Procedure (1 of 3)

Step 3. The UE and eNB exchange messages:

• Message 1: The UE randomly selects and transmits the preamble sequence on the radio channel. (There are up to 64 different preambles.)

• Message 2: The eNB sends the Random Access Response to the UE, addressed to RA-RNT1. The message contains Temp C-RNT1, the Timing Advanced Value, and the Uplink Grant Resource.

• Message 3: The UE sends the RRC connection request message to the eNB. The message contains the UE identity (TMSI) and connection establishment cause.

• Message 4: The eNB responds with the contention resolution message to the UE and is addressed to the TMSI value. The message also contains the new C-RNTI, which will be used for further communication.

Refer to Figure 2-7.

8


Step 4. The RRC connection is established. The RRC configures the Signal Radio Bearer 1 (SRB1) for the UE and lets the UE inform the network what it wants to do. The series of actions is as follows:

• RRC Connection Request (RACH Msg3): Contains the UE identity (TMSI) and connection establishment cause.

• RRC Connection Setup Message: Contains the configuration details for SRB1.

• RRC Connection Setup Complete Message: The UE moves to ‘RRC Connected’ mode.



Step 5. The attach procedure occurs:

• On the Non-Access Stratum (NAS) communications layer, the UE sends an Attach Request message, which includes the IMSI, to request an initial attach to the NAS layer of the MME.

9

• The Attach Request message is embedded in the RRC Connection Setup Complete mes-sage, which is then embedded again in the successive Initial UE message.

At this stage, the IMSI acquisition and Evolved Packet System (EPS) Connection Management (ECM) are complete. Refer to Figure 2-9.

Figure 2-9: Attach Procedure

To explain further, the ECM connection is the logical connection between a UE and MME which tunnels across the RRC and S1 signaling connection. This connection is used for exchanging NAS messages.

The EPS Mobility Management (EMM) is a sub-layer of the NAS layer and is responsible for mobility management procedures, e.g., attach and tracking area update. See Figure 2-10.

Figure 2-10: ECM Connection, Part 1

Part 2 of the ECM connection process is described in Table 3-2.

10

Table 2-2: ECM Connection, Part 2

Layer State Entity Description

EMM EMM-Deregistered UE, MME UE is not attached to any network. MME does not know the current location of the UE.

EMM-Registered UE, MME UE is attached and successfully registered to the network. An IP address has been assigned with an established EPS bearer. MME knows the current location of the UE.

ECM ECM-Idle UE, MME No NAS signaling connection (ECM connection) established yet.

ECM-Connected UE, MME NAS signaling connection is established.

RRC RRC-Idle UE, eNB No RRC connection is established yet.

RRC-Connected UE, eNB RRC connection has been established.

2.1.4 Authentication Procedure The network is now ready to authenticate the user. It generally goes through the following process (Fig-ure 2-11).

1. Acquire Authentication Vectors

1. [MME → HSS] Authentication Info Request

2. [HSS] Generate AVs

3. [MME ← HSS] Deliver AVs

2. Mutual Authentication

1. [UE ← MME] Request by MME for User Auth

2. [UE] Generate AVs and compare

3. [UE → MME] Deliver User RES to MME

4. [MME] Network authenticating UE

At this stage, user authentication is complete.

11

Figure 2-11: Authentication Procedure

2.1.5 NAS Security Setup Procedure Following is a general description of the NAS security setup procedure (Figure 2-12).

1. [MME] Generates NAS keys

2. [UE ← MME] Helps UE to generate NAS security keys

3. [UE] Generates NAS security keys

4. [UE → MME] NAS security key generation complete

At this stage, all NAS messages are security delivered as encrypted and integrity-protected.

12

Figure 2-12: NAS Security Setup Procedure

2.1.6 Location Update Procedure The location update procedure follows this general process (Figure 2-13):

1. [MME → HSS] Notifies the HSS of the UE’s Location

2. [HSS] Updates the UE’s location

3. [MME ← HSS] Delivers user subscription information

4. [MME] Stores user’s subscription information

13

Figure 2-13: Location Update Procedure

2.1.7 EPS Session Establishment

2.1.7.1 Part 1

The general process for creating the request message for an EPS session is as follows:

• The MME selects the APN, which is provided from the HSS or UE.

• The MME selects the S-GW to go through for access to the selected P-GW.

• The MME initiates a creation request for an EPS session and a default EPS bearer.

In turn, the EPS session creation response message occurs when:

• The P-GW informs the MME of the user’s QoS information applied to the established EPS ses-sions and default EPS bearer.


14

Figure 2-14: EPS Session Establishment, Part 1

2.1.7.2 Part 2

The initial context setup request is as follows:

The MME sends an Initial Context Setup Request message so that the eNB can establish the E-UTRAN Radio Access Bearer (E-RAB), which is the concatenation of an S1 bearer and the corresponding radio bearer. The message consists of the following elements (Figure 2-15):

• UE-AMBR(UL/DL)

• S1 S-GW TEID

• UE Security Algorithm

• NAS-PDU (Attach Accept)

• E-RAB ID

• E-RAB QoS

• KENB

15


2.1.7.3 Part 3

The AS Security Mode Command/Complete process works as follows (Figure 2-16):

• The eNB generates the AS security keys from KENB for safe delivery for RRC messages and user traffic.

• The eNB informs the UE of the AS security algorithms it selected.

• The UE generates the AS security keys and performs an integrity check.

• The UE informs the eNB that the AS security keys have been generated.

16


2.1.7.4 Part 4

Reconfiguring the RRC connection occurs in the following way (Figure 2-17):

• The eNB sends an RRC Connection Reconfiguration message to the UE to activate the default ra-dio bearer (DRB), and also carries the Attach Accept message.

• The Attach Accept message contains the UE IP address, Global Unique Temporary ID (GUTI), Tracking Area Identifier (TAI) list, EPS Bearer ID, UE-AMBR, and QoS parameters. These parame-ters determine the UE’s maximum uplink throughput.

17


2.1.7.5 Part 5

The Initial Context Setup Response happens as follows:

• The eNB allocates a downlink S1 tunnel endpoint identifier (TEID) for S1 bearer and sends an Ini-tial Context Setup Response message to the MME, which is forwarded to the SGW.

The Attach Complete occurs:

• The UE sends a Direct Transfer message to the eNB, which includes the Attach Complete mes-sage that identifies the EPS Bearer Identity, NAS sequence number, and NAS-MAC.


18


Up to this point in the process, all of this happens before the UE starts sending traffic!

2.1.7.6 Part 6

The S1 Bearer Modification occurs as follows (Figure 2-19):

• The MME forwards the downlink S1 TEID received from the eNB to the SGW.

• The SGW responds to the MME via the Modify Bearer Response message. The SGW is now ready to deliver downlink S1 traffic.

• The S1 bearer is established, which allows the eNB and SGW to exchange traffic with each other.

• The default bearer from the UE to the PGW is finally established.

19


2.1.8 EPS Bearer

2.1.8.1 Part 1

The Evolved Packet System (EPS) Bearer (or simply “bearer”, for short) is defined between the PGW and UE, and maps to a specific set of QoS parameters such as data rate, latency, and packet error rate. The default bearer classes are:

• Guaranteed Bit Rate (GBR) bearer

• Non-GBR bearer

As an operator, if you have your own local EPS you can define more than just the default bearers, which determines QoS.


20

Figure 2-20: EPS Bearer, Part 1

2.1.8.2 Part 2

The following terms will help you to understand the EPS bearer traffic flows.

• Access Point Name (APN) is a gateway the UE attaches to and identifies the Packet Data Net-work (PDN).

• QoS Class Identifier (QCI) indicates nine different QoS performance characteristics.

• Allocation and Retention Priority (ARP) indicates the priority of the bearer. (This may be used to give preferential priority to a given user, e.g., such as the CEO or a Presidential hotline.)

• GBR (UL/DL) is the Guaranteed Bit Rate used for GBR type bearers, and indicates the minute bit rate to be guaranteed. (Whereas the default bearers provide only a best-effort QoS. Bearers acti-vate dynamically, depending on network congestion.)

• MBR (UL/DL) is used for GBR type bearers, and indicates the maximum bit rate allowed.

• APN-AMBR (UL/DL) is used for non-GBR type bearers, and indicates the maximum bit rate al-lowed for all bandwidth in a PDN.

• UE-AMBR (UL/DL) is the same as APN-AMBR, but is the maximum bit rate allowed for all non-GBR type bearers associated to the UE.

2.1.8.3 Part 3

Part 3 of the EPS bearer traffic flow process is best illustrated in Figure 2-21 and further explained in Part 4.

21

Figure 2-21: EPS Bearer, Part 3

2.1.8.4 Part 4 (SDF)

Part 4 of the EPS bearer flow is called the Service Data Flow (SDF). The SDF is a group of IP flows of user traffic associated with a type of service. Each SDF that matches the packet filters of a Traffic Flow Tem-plate (TFT) (DL TFT) is mapped by the P-GW to an EPS bearer that satisfies its QoS requirements. Refer to Figure 2-22.

Figure 2-22: EPS Bearer, Part 4 (SDF)

2.1.8.5 Part 5 (QoS)

The following explains the EPS bearer QoS assignments (Table 2-3).

• QoS parameters are defined at the service level and bearer level.

• Both QCI and ARP are the basic QoS parameters applied to all SDFs and EPS bearers.

• GBR, MBR, and AMBR are the rate limiting aspects of the QoS parameters.

22

• QoS authorization is handled by the Policy Control and Charging Rules Function (PCRF), which dynamically manages and controls data sessions.

• The QoS parameters are:

• SDF QoS parameters: QCI, ARP, GBR and MBR

• EPS bearer QoS parameters: QCI, ARP, GBR, MBR, APN-AMBR and UE-AMBR

Table 2-3: EPS Bearer, Part 5 (QoS)

QCI Resource Type

Priority Packet Delay Budget (ms)

Packet Er-ror Loss Rate

Services

1 GBR 2 100 10⁻2 Conversational voice

2 4 150 10⁻3 Conversational video (live streaming)

3 3 50 10⁻3 Real-time gaming

4 5 300 10⁻6 Non-conversational video (buffered streaming)

5 Non-GBR 1 100 10⁻6 IMS signaling

6 6 300 10⁻6 Video (buffered streaming), TCP-based (e.g., www, email, chat, FTP, etc.)

7 7 100 10⁻3 Voice, Video (live streaming)



2.1.8.6 Part 6 (QoS Provisioning)

Regarding the EPS Bearer QoS provisioning:

QoS parameters applied to a default bearer are provisioned by the HSS, and are downloaded by the MME when the default bearer is activated. These QoS rules can be modified by the PCRF. The PCRF is also responsible for provisioning QoS parameters for dedicated bearers.

Regarding the SDF QoS provisioning:

All the QoS parameters for SDFs are provisioned by the PCRF. The PCRF function enforces the SDFs. (Note: The Baicells EPC does not yet use this function, so the traffic is best effort for now.)


23

Figure 2-23: EPS Bearer, Part 6 (QoS Provisioning)

2.1.8.7 Part 7 (QoS Enforcement)

QoS rules are applied to each SDF and EPS bearer upon detection of user traffic (IP flows). IP flows arriv-ing at a P-GW are filtered into different SDFs. Enforcement of QoS for EPS bearers is done in the EPS enti-ties (UE, eNB, S-GW, and P-GW). Refer to Figure 2-24.

Figure 2-24: EPS Bearer, Part 7 (QoS Enforcement)

24

2.2 Baicells CloudCore Design

Figure 2-25 illustrates the Baicells CloudCore network design.

Figure 2-25: Baicells CloudCore

In NAT mode (default), the LGW can access the UE by URL, which is especially useful for the plug-and-play nature of the deployments:

• https://[IP Address]:[Port]

• [IP Address] = eNB IP

• [Port] = 5xxxx where xxxx = last 4 digits of the UE’s IMSI

An example of addressing for this configuration is shown in Figure 2-26.

25

Figure 2-26: NAT Mode

In router mode the LGW requires a static route entry to access the LGW subnet (Figure 2-27). In this case you assign a subnet for the UEs using a static route, and direct access through the IP address.

26

Figure 2-27: Router Mode

When the LGW is in bridge mode (Figure 2-28):

• The LGW simulates Layer 2 with an external DHCP server to assign IP addresses.

• LTE does not use MAC addresses to distinguish UEs, and instead relies on the IMSI from the USIM card.

• The UE’s MAC address is generated from the IMSI in hex.

• To calculate the UE MAC address, convert the last 12 digits of the IMSI number to hex, and then prefix it with 8A. For example, if the IMSI is 311980000002918, you would take the last 12 digits "980000002918" and convert them to hex, which would equal "E42C8D5366": The MAC address would be 8A:E4:2C:8D:53:66.

27

Figure 2-28: Bridge Mode

2.3 Fixed Wireless with no EPC

2.3.1 EPC Concerns While using the internet for S1 connections to the backhaul core network may be flexible, it can also be unstable. The instability causes S1 failures, and there are often some end-users out of service (Figure 2-29). The MME pool improves but does not resolve the situation, and it can be costly (Figure 2-30).

28

Figure 2-29: S1 Failures

Figure 2-30: MME Pooling

29

In addition, adding the core network functions can be complicated (Figure 2-31):

• It typically requires professional network design.

• The centralized EPC can cause heavy impact when failure occurs.

• LTE is an end-to-end Layer 3 network; it is hard to migrate a Layer 2 network to LTE.

Figure 2-31: Traditional LTE Architecture

2.3.2 Baicells HaloB Solution Reference: Baicells HaloB User Guide

2.3.2.1 Overview

To address wireless service providers’ concerns related to adding core network functions to the network when full-blown end-to-end LTE may not be necessary, or for situations when signaling to the EPC may not be available (e.g., weather emergencies) and subscribers need continued service, the Baicells team created a fixed wireless, no-core solution called HaloB (Figure 2-32). In the HaloB architecture, there are no S1 tunnels from the eNBs to other devices. Each eNB operating in HaloB mode functions as a “Lite EPC” and controls its UEs and other information independently. All signaling stays local (within the eNB).

30

Figure 2-32: HaloB Cell

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 soft-ware controls its subscribers independently. All signaling stays local, within the eNB.

A HaloB eNB eliminates the transport layer between the EPC and the eNB by embedding a lite EPC directly on the eNB. Therefore, critical control plane signaling is kept local. With HaloB installed, S1 (transport) failures are eliminated. This removes wireless point-to-point (PTP) backhaul failures, fiber outages, or rout-ing mistakes from causing customer service disruption.

The only other network components involved in implementing HaloB are the Baicells Operations Manage-ment Console (OMC) and Business Operations Support System (BOSS) (Figure 2-33). During HaloB opera-tion, the CloudCore is still available for OMC monitoring and upgrade functions, and the BOSS Home Sub-scriber Server (HSS) functions. Subscriber Identity Module (SIM) card activation and bandwidth package assignment are still performed by the BOSS.

Figure 2-33: HaloB Architecture

31

With HaloB:

• The Network Access System (NAS) is processed by each HaloB-enabled eNB, which means the UEs will always be online (barring any eNB equipment failure, of course).

• Operators can enter the world of fixed wireless with a lower initial investment.

− Operators do not have to invest in local EPC hardware to offer wireless network access services. The eNBs and the core network functions are decoupled.

− The simplified structure means there is no need for professional network design and maintenance.

• The self-configuration, plug-and-play deployment model means a shorter time-to-market (TTM) and faster return-on-investment (ROI).

While there is a great deal of intelligence operating in the background of the HaloB feature, Baicells de-signed the feature to run efficiently and be easy to configure and manage. Even with HaloB operating on the eNB, in the control plane there is no huge impact on memory or processing. The eNB performs at the same level it normally would.

HaloB is a software feature that works with existing eNB hardware – you do not have to upgrade the hard-ware equipment to get the HaloB feature. The software upgrade to HaloB does require a unique feature key generated by Baicells for each eNB.

HaloB is an example of the industry movement to make LTE technology more accessible and less compli-cated, and to move more of the processing closer to the users. In essence, a HaloB eNB becomes a local EPC right on the tower!

2.3.2.2 How to get HaloB

Operators wishing to take advantage of the HaloB solution should contact their distributor (Figure 2-34). You can purchase the HaloB feature on a per-eNB or bundle basis. As part of the purchase process for existing eNBs, you will be asked to provide the eNB serial numbers to Baicells. Baicells will use the eNB serial numbers to generate the feature keys. Be sure the eNBs that you target for HaloB operation are assigned to you, the operator.

Figure 2-34: How to get HaloB

32

3. Factors Affecting Network Performance You can find many articles on the internet describing factors that affect both wireless and IP network per-formance. Optimization is constrained not only by the physics and logic involved in cell and IP network design but also by human performance – understanding the options and limitations, and avoiding or over-coming errors.

In a perfect world, you would get the maximum possible number of users per cell/eNB, the maximum downlink (DL) and uplink (UL) data rates for subscribers, seamless handoffs of voice or data sessions be-tween cells, and insignificant packet loss or delay. You would size the network to meet or exceed expec-tations without incurring unnecessary cost.

Reality is, there are a number of dynamic influences on network performance. Following are several of the many important factors to think about in planning, operating, and managing a Baicells LTE network. These are mentioned only as a reminder that running a network requires continuous observation and adaptations.

• Environmental conditions

o The existence of physical obstructions between the subscriber’s user equipment (UE) and the cell sites, at the time of installation and afterward. A line-of-sight (LOS) scenario may become a non-LOS condition as winter trees become spring trees full of leaves, for example.

o Weather disruptions

• Range and distance between cells

o Antenna selection and polarization

o Mechanical and electrical antenna downtilt

o Cell overlap and neighbor cells

o Load balancing

• Interference from other radiating devices

• Equipment wear, cabling, and weather protection

• Capacity demands

o Subscriber usage requirements, e.g., from mostly checking email and web-browsing to media-rich demands such as streaming movies or online gaming

o Subscriber mobility

o Over-subscription and network load

• Regulated spectrum, licensing, and power constraints

• Technology compatibility

33

4. Maintenance Reference: Refer to the Baicells Configuration & Network Administration Guide for information on and procedures for configuring the features and functions available through the OMC, BOSS, eNB GUI, and UE GUI.

4.1 General Practices A basic and important step to take in managing the network is to document your network setup, and to update that information as changes occur over time. Keep track of hardware models, serial numbers and locations; your operator-specific codes, passwords, and software versions; legal compliance documents; and so forth.

Routinely save and refresh your database configuration files, examine system logins, revisit user password policies, inspect cabling and weatherproofing of outdoor equipment, check that latest firmware upgrades were completed for all impacted components – and keep note of these activities. Set up notifications for alarms, especially critical and major alarms (see section 4.2.2.1.2.4 Notification). These are common sense suggestions, but some of the routine activities are easy to forget or deprioritize until you realize you have an issue and wish you had done the obvious or need the information you meant to record.

4.2 OMC - Dashboard Monitoring

4.2.1 Overview As far as daily monitoring of network performance, the best starting place for you to check the health of your network is the OMC Dashboard (Figure 4-1). The dashboard provides operators with a summary of overall network status, statistics, and performance. This at-a-glance window helps administrators to quickly grasp the network conditions and to identify issues.

Make it a regular practice to watch for critical and major alarms requiring immediate attention. Often such alarms mean system impacts to multiple subscribers. You can set up alarm notifications to email you when an alarm occurs. It is also a good idea to regularly monitor subscriber data associated with quality of ser-vice. This section explains the types of information you can monitor and the links to other menus and actions you can take through the dashboard.


34

Figure 4-1: OMC Dashboard

4.2.2 Alarms and Logs

4.2.2.1 Alarms

The first thing you may notice on the OMC dashboard is the row of colorful circles under the Alarm portion of the window. The circles display the number of active system alarms, which are categorized into 4 classes:

• Critical

• Major

• Minor

• 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 (Figure 4-2), it will take you into the Alarm > Query menu and show a list of active alarms. In the list of alarms, under the Operation column click on the 3 vertical bubbles icon next to a specific alarm and select Detail to display further information about that alarm, such as probable cause and suggestions for how to resolve it (Figure 4-3).

35

Figure 4-2: Alarms

Figure 4-3: Alarm Details

36

The alarm detail fields are described in Table 4-1.

Table 4-1: Alarm Detail

Field Name Description

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 Positioning Provides more detail about which device reported the alarm, such as the eNB se-rial 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, uncon-firmed 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, net-work 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

You can select Alarm Confirm under Operation to let other OMC administrators know you have seen an alarm reported and are working on it. If you select Clear Alarm it will remove the alarm from the active list and add it to the list of historical alarms. The windows resulting from these two actions are shown in Figure 4-4.

Figure 4-4: Confirm or Clear Alarm

37

You can export active or historical alarm details by clicking on the export icon in the upper right of the dashboard window, as shown in Figure 4-5. You can then select the destination where you want to save the file on your computer.

Figure 4-5: Export

Looking at the OMC > Alarms > History Alarm tab, under the Operation column you have the Detail and Alarm Confirm options as well as two new options: Restore alarm and Delete Alarm (Figure 4-6).

Figure 4-6: History Alarm Tab

If you select Restore alarm, the system will immediately remove the alarm from the history list and put the alarm in the active alarm list. If you want to remove the alarm permanently from either list, select Delete Alarm.

Back in the Alarm View window (Figure 4-7), you see the list of alarms in the network. The icons in the upper right of the View window are 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 tem-plate assumes you have defined one or more custom alarm templates, e.g., where you have identified specific severity levels or specific equipment, etc., that you want to see. How to create templates is ex-plained below Figure 4-7. Filter enables you to filter which columns of information you want to see in the view. Maximize/restore applies to sizing the GUI window.

38

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.

Figure 4-7: Alarm > View

Select template enables you to select a predefined template view of the alarms (Figure 4-8). To add a new, custom template, click on the Select Template icon and then on the + Add icon (Figure 4-9). In the dialogue window that opens, complete the Template Name field, select the Device Type, Group Name, and the alarms you wish to view when this template is used (Figure 4-10).

Figure 4-8: Select Template

39

Figure 4-9: Add Template

Figure 4-10: Add Template Fields

40

4.2.2.1.1 View The first time you select Alarm > View, you will receive a notice that you need to create one or more alarm monitoring templates (Figure 4-11). Select OK, which will take you into the View window. You can create different templates for different views of alarm information, e.g., different categories of alarms, specific eNBs, etc.

To create a template, in the View window click on the Select Template icon, as shown in Figure 4-11, complete the fields, and click on OK to save it; or, you can follow the instructions that were given in the notification by going to Alarm > Settings. There are multiple ways to add or modify templates. If this is your first time to create a template, please review all of section 4.2.2.1 before continuing.

Figure 4-11: View

4.2.2.1.2 Query The Alarm > Query 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-12).

41

Figure 4-12: Query

As mentioned in section 4.2.2.1 Alarms, 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-13). Refer to Table 4-1.

Figure 4-13: Alarm Details

Another function in the Query window is the column filter icon. 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-14).

42

Figure 4-14: Filter

Use the Query or Advanced Query functions to search on other fields related to alarms (Figures 4-15 and 4-16).

Figure 4-15: Advanced Query (1 of 2)

43

Figure 4-16: Advanced Query (2 of 2)

4.2.2.1.3 Settings The Alarm > Settings sub-menu functions – Basic, View Config, Library, and Notification - are shown in Figure 4-17.

Figure 4-17: Alarm > Settings

4.2.2.1.3.1 Basic

Use the Alarm > Settings > Basic 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-18). Click on OK to save the information.

44

Figure 4-18: Alarm Filter > Selected eNodeB

In the Alarm Type tab, select the categories of alarms that you wish to filter on for this template (Figure 4-19). Click on OK to save the information.

Figure 4-19: 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-20). Click on OK to save the information.

45

Figure 4-20: Severity

In the last tab, Event Time, you can set the start and end dates for collecting and displaying the information (Figure 4-21). Click on OK to save the information.

Figure 4-21: Event Time

Be sure to enable the new template in the Alarm Filter list (Figure 4-22). Use the functions under Operation to modify (pen icon) or delete (trash icon) an Alarm Filter template.

Figure 4-22: Enable Filter Template

46

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 portion of the window (Figure 4-23).

Figure 4-23: + 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 in this section on creating an Alarm Filter template for the steps to finish setting up a new Alarm Filter template using this menu.

47

4.2.2.1.3.2 View Config

The Alarm > Settings > View Config menu shows a list of existing templates and each one’s last modification time. Use the functions under Operation to view, modify, or delete a template in the list (Figure 4-24).

Figure 4-24: View Config

When you click on the + Add icon, you are provided another way to add a new template from this window (Figure 4-25). Give the new template a name, identify the Device Type, and select the devices to be re-ported. Click on OK to save the template.

Figure 4-25: Add New Template

48

4.2.2.1.3.3 Library

By selecting Alarm > Settings > Library you will see a display of all alarms that have occurred in the system (Figure 4-26). Using the adaptive display feature (the up/down arrows in the column headers), you can sort the list in ascending or descending order by the alarm identifier or by severity level. To export the data, select the export icon to save the information to your computer.

Figure 4-26: Alarm Library

4.2.2.1.3.4 Notification

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-27).

Enter the email address or addresses where the notification should be sent; you can separate multiple email addresses using a semi-colon (;). For the Sending Period(Min) field, 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.

49

Figure 4-27: Notification

Table 4-2 presents is a list of alarms with additional information regarding conditions that may trigger the alarm, actions to take, and so forth. The alarms in the table are shown in numerical order based on Alarm ID number.

Go to the next section 4.2.2.2 Logs to learn more about collecting and viewing Baicells data logs.

50

Table 4-2: Alarms

Alarm ID Event Type Severity Probable Cause Suggestions Other Possible Causes Explanation Influences / Results Trigger Reason Disposition

7 Communica-tions alarm

Critical eNB is disconnected from the OMC

1) Check if the network is avaliable. 2) Check if the OMC server address is configured correctly.

eNB is disconnected from the network

The alarm is generated when there is a network connection problem between the eNB and OMC/NMS, or the connec-tion is interrupted.

The eNB cannot be managed from the OMC/NMS.

The network connection be-tween the eNB and OMC/NMS is disconnected or interrupted.

No network connection be-tween the eNB and the OMC/NMS

1) Check if the network is avaliable. 2) Check if the OMC server address is configured cor-rectly.

11109 Communica-tions

Major S1 setup failure between eNB and EPC

1) Check the MME IP, PLMN, and TAC parameters. 2) Check if the IPSEC tunnel is con-nected. 3) Check if the network is available.

S1 interface fault After the MME receives the response from the eNB, the S1 Application Proto-col (S1AP) is connected to the underly-ing SCTP link resources available. The eNB's MME initiates a connection estab-lishment request, and the MME does a validity check. If the check does not pass, the connection cannot be estab-lished. If the conflict cannot be found, the MME establishes a connection. When the underlying SCTP link fails, or when there is an S1AP protocol layer data configuration error, or due to an abnormal MME connection, the link can-not be established and the alarm is gen-erated.

The eNB releases all the users who have access to the S1 in-terface that has failed. If the cell is the non-commissioning state for the S1 interface, the eNB deactivates the cell. If it is in the commissioning mode, the eNB may activate the cell, but new users will not have ac-cess to the cell.

Abnormal EPC link Link state - S1 interface config-uration error

1) Check the MME IP, PLMN, and TAC parameters. 2) Check if the IPSEC tunnel is connected. 3) Check if the network is available.


Major X2 setup failure Check if the parameters configured for the neighbor cell are correct. If not, modify and restart the eNB.

X2 interface failure alarm During handover, in the X2 Application Protocol (X2AP) connec-tion - when the underlying SCTP link re-sources are available, the peer eNB will initiate the connection establishment re-quest. The peer eNB will validate the le-gitimacy of the connection request. If the check does not pass, it will not be able to establish a connection. When the underlying SCTP link fails, or when there is an X2AP protocol layer configuration error, or when there is an abnormal end eNB and it cannot establish a connec-tion, the alarm is generated.

The eNB releases the users be-ing switched by an X2 interface. It generates an alarm before the recovery, and the eNB does not continue to support the switching process between the X2 interface and the corre-sponding eNB. It also does not continue to support the inter-cell interference coordination procedure with the corre-sponding eNB.

When the underlying SCTP link fails, or when there is an X2AP protocol layer configuration er-ror, or when there is an abnor-mal end eNB and it cannot es-tablish a connection, the alarm is generated.

X2 interface configuration er-ror. The eNB is not configured on the X2 end interface.

1) Confirm the corresponding neighboring configuration pa-rameters are correct. If it is not the correct neighboring cell information, edit the cor-rect configuration and then restart. If restart fails, go to step 2. 2) Check the site and the neighbor cell if there is an X2 interface, and if not, the alarm cannot be eliminated. In this case, go to step (4). Otherwise, go to step (3). 3) Extract the eNB logs, and contact technical support. 4) Alarm processing - change the neighbor configu-ration, or just ignore the alarm.

11111 Equipment Critical Memory allocation failure Device output - too many redun-dant files need to be cleaned up. Device processing has run out of space.

Memory space is insuffi-cient

When the eNB cache drops below 20 MB of free space the alarm is generated.

eNB operating anomalies If the available memory cache of the eNB during operation is less than 20M and the duration exceeds 120 seconds, an alarm is triggered. When the available memory is above the threshold (20M) and an alarm was reported, the alarm is cleared.

The eNB output needs to clean up redundant files, and the eNB processes run out of space.

Contact technical support to clear the alarm.

51



Critical SCTP link failure 1) Check if the IPSEC tunnel is con-nected. 2) Check if the network is available.

SCTP link fault alarm When the eNB detects the Stream Con-trol Transmission Protocol (SCTP), the bearer service link cannot be established and it generates the alarm.

Unable to carry signaling lead-ing to the SCTP link.

When the eNB detects Stream Control Transmission Protocol (SCTP), the bearer service link cannot be established and it generates the alarm.

Link abnormal state 1) Check if the IPSEC tunnel is connected. 2) Check if the network is available.


Warning User plane tunnel (TNL) setup failure

•No user plane is configured to carry the peer route. •The user plane carries the underly-ing link failure. •The certificate expired. •The packet filtering function ena-bled on the local end causes the de-tection of the bearer link failure. •The network or the peer device is not configured properly, resulting in failure of the bearer link detection.

The user plane bearer link fault alarm

The alarm may be generated during ses-sion establishment if the eNB detects an abnormality in the user plane traffic bearer. When the user plane bearer link is available and continuously detected for 1 minute, the alarm is reported as re-covered.

The user plane traffic cannot be carried properly.

Turn on the GPRS Tunneling Protocol - User Plane (GTP-U) static detecting function. When the eNB detects that the route to Serving GW (SGW) of the EPC is unreachable, or the MME does not respond to the GTP-U Echo request message which is sent by the eNB, the alarm is generated. When the user plane bearer link is available and continu-ously detected for 1 minute, the alarm is reported as recov-ered.

•No user plane is configured to carry the peer route. •The user plane carries the un-derlying link failure. •The certificate expired. •The packet filtering function enabled on the local end causes the detection of the bearer link failure. •The network or the peer de-vice is not configured properly, resulting in failure of the bearer link detection.

Check OMC to see if there is a simultaneous alarm 11109 or 11112. If there is, please refer to the corresponding 11109 or 11112 alarm han-dling recommendations.

11180 Processing Error

Critical PCI collision alarm from SON 1) Check the PCI configuration.

2) Check if there is a cell cover-age area.

District PCI conflict alert When the same PCI is detected between the serving cell and a neighbor cell in the Neighbor Cell List (NCL) using the same frequency, the alarm is generated.

It may lead to dropped calls and handover performance is-sues.

When the same PCI is detected between the serving cell and a neighbor cell in the Neighbor Cell List (NCL), the alarm is gen-erated.

Irrational PCI allocation plan. Cell handoff coverage exists.

1) Modify the PCI cell to en-sure the same-frequency neighbor cells are different. Restart the eNB.

2) If the alarm persists, con-tact technical support.


Critical PCI confusion alarm from SON 1) Check the PCI configuration.

2) Check if there is a cell cover-age area.

District PCI confusion warning

When the same PCI is detected between the serving cell and a neighbor cell in the Neighbor Cell Relation Table (NCRT) us-ing the same frequency, the alarm is generated.

It may lead to dropped calls and handover performance is-sues.

When the same PCI is detected between the serving cell and a neighbor cell in the Neighbor Cell Relation Table (NCRT), the alarm is generated.

Irrational PCI allocation plan. Cell handoff coverage exists.

1) Replan the PCI scheme. En-sure different co-frequency adjustments. Restart the eNB.

2 If the alarm persists, con-tact technical support

11182 Environmen-tal alarm

Major Temperature abnormality 1) Check if the enviromental tem-perature is too high. 2) Check the cooling enclosure.

Veneer (surface) abnormal temperature alarm

When the board temperature goes be-yond the rated operating temperature range, it reports this alarm. The alarm will be recovered when the operating board is within the rated operating tem-perature range for 3 minutes (the de-fault). Alarm generation duration can be set via the SET ALMFILTER command. The rated operating range for the ve-neer will vary by board type.

To prevent the board from fail-ing when the temperature is too high, the board will power down automatically, disrupting normal operations.

When the operating tempera-ture exceeds the rated temper-ature for the boards (default parameter BOARD_ALARM_THRESHOLD_1_TEMPERATURE 85), and it is in this state for 120 seconds, it will report this alarm. When the temperature is lower than the rated temperature of the board, the alarm will be cleared.

Ambient temperature is too high

1) Check if the ambient tem-perature is too high. If it is too high, turn on cold air con-ditioning. 2) Check the cooling cabinet.

52



Minor Board temperature is too high 1) Check if the environment temper-ature is too high. 2) Check the cooling enclosure.

Board veneer (surface) temperature is too high

Any board with an ambient temperature that is outside the normal range, either too high or too low, will cause the board to fail or not work properly, resulting in service degradation.

When the operating tempera-ture exceeds the rated temper-ature for the board (default pa-rameter BOARD_ALARM_THRESHOLD_1_TEMPERATURE 85), and it is in this state for 120 seconds, it will report this alarm. When the temperature is back within nor-mal limits for the board, the alarm will be cleared.

Ambient temperature is too high

1) Check if the ambient tem-perature is too high. If it is too high, turn on cold air con-ditioning. 2) Check the cooling cabinet.

11184 Equipment Major Cell unavailable 1) Check the configuration parame-ters for SR cycle, CQI cycle, and maximum number of users.

2) Export logs, and contact technical support.

Cell unavailable Cell not completely shut down Node cannot provide services Cell does not completely shut down

Configuration error

11185 Equipment Minor No user access 1) Check if there is an S1 fault - alarm ID 11109. If there is, resolve that alarm.

2) Check if the cell is activated.

3) Check if the antenna status is normal.

Cell has no traffic alert The alarm is generated when the eNB detects no user access within the set time (ALARM_THRESHOLD_CELL_NO_ TRAFFIC default is 3600 seconds).

Rebuild completed before the eNB could provide services

The alarm is generated when the eNB detects no user access within the set time (ALARM_THRESHOLD_CELL_NO_TRAFFIC default is 3600 sec-onds).

No user access; radio link fail-ure; S1 fault

11187 Equipment Major Master version software is una-vailable

Upgrade to the latest version of software.

Master version software is unavailable

The eNB has 2 main and a backup stor-age region. The main (master) area holds the software that is currently run-ning on the eNB. During startup, if the main area appears incomplete or empty, or if it does not recognize the software, the alarm is generated.

This may happen during board burn-in. The following warning will occur: “Upgrade the eeprom bit31- damage system main area flag damage 1- 0- un-damaged; bit30- prepara-tion zone system damage flag damage 1- 0- undamaged

Upgrade failed Re-upgrade to the latest ver-sion of software.

11188 Equipment Major Automatic fallback Upgrade to the latest version of software.

Automatic fallback When the eNB detects that the cur-rent version of software is abnormal, it automatically rolls back to the previ-ous version and this alarm is generated.

Upgrade to the latest version of software.

Upgraded software runs less than 60 minutes

1) Re-upgrade the eNB soft-ware.

11189 Equipment alarm

Major GPS cannot sync to clock source 1) Check the configuration of the clock reference source. 2) Check if the GPS antenna is connected or faulty.

Clock synchronization source failure alarm

The Midi Processing Unit (MPU) is syn-chronized by an external clock source phase-locked loop, a system clock for each service processing module. When the eNB uses a local oscillator that may be longer than the holding time, the alarm occurs. The station is not synchro-nized.

Various eNB processing services exceptions will occur, such as handover failure and dropped calls. Results can be severe.

GPS status is determined whether or not the alarm is generated. If you choose to sync, there is no way for the synchronization to be success-ful. The alarm will be gener-ated. The alarm will clear when the GPS syncs.

A reference clock source is not configured. The GPS antenna cannot synchronize.

1) Check the configuration of the clock source. 2) Check to see if the GPS an-tenna has failed.


Major GPS unavailable 1) Check the GPS antenna connec-tions. 2) If the GPS antenna is faulty, re-place it.

GPS is not available The alarm is generated when the eNB detects the absence of the GPS antenna, or when there is no GPS signal.

Various eNB processing services exceptions will occur, such as handover failure and dropped calls. Results can be severe.

The alarm will clear when the eNB detects the GPS antenna or GPS signal.

GPS antenna - GPS does not ex-ist; out of step

1) Check the GPS antenna connections. 2) If the GPS antenna is faulty, replace it.

11191 Processing er-ror alarm

Minor Time sync failed 1. Check that the NTP configuration is correct. 2. Check whether the network is op-erating normally. 3. Check the GPS antenna for prob-lems.

Time synchronization failed alarm

When synchronization between the eNB and the clock source time synchroniza-tion server fails, the alarm is generated.

When the NTP synchronization fails and the GPS synchroniza-tion fails, the alarm is reported.

Clock reference source is not configured.

Replace the equipment, and contact technical support.

53


11196 Equipment Warning Module type unknown Unknown card type The eNB detects an unknown card type The eNB cannot provide ser-vice. When starting OAM, it is unable to use DL/UL EARFCN calibration parameters.

The card type is not set at the factory, or the card type does not match a known type.


Warning Configuration check error 1) Check the alarm details for the specific parameter name, and mod-ify the configuration. 2) If unsure, extract the logs and check the log detail for more infor-mation. 3) If still uncertain, send the logs to technical support.

Configuration check failure alarm

When the eNB checks the configuration parameters for the range and other val-ues, if the check fails this alarm is gener-ated. The alarm will not clear until the configuration is corrected and after the OMC restarts the synchronization.

A parameter check failure may prevent the establishment of the cell after the protocol stack is up.

During eNB start-up, if a config-uration parameter does not match other dependent param-eters, the alarm is generated. It will not clear until the configu-ration is corrected and the eNB is restarted and synchronized with the OMC.

When you modify a parameter and related parameters have not changed as needed, the alarm will trigger.

1) Check the alarm details for the specific parameter name, and modify the configuration. 2) If unsure, extract the logs and check the log detail for more information. 3) If still uncertain, send the logs to technical support.


Critical GPS irreclaimable Confirm the connection state to re-start the eNB GPS antenna.

GPS synchronization unre-coverable alarm

GPS work process is interrupted for more than 30 minutes. 1PPS does not automatically recover synchronization after 40ms

Inter-eNB handover cannot produce interference to the neighbor eNBs. The eNB may need to reboot.

GPS synchronization is out of step for more than 30 minutes.

GPS antenna - The GPS cannot be more than 30 minutes out of step.

Confirm the connection state to restart the eNB GPS an-tenna. No support.


Warning Local eNB consecutive login at-tempts within 1 minute fail

Local eNB consecutive login attempts within 1 minute failure alarm

When a user tries unsuccessfully multi-ple times to log in to the eNB using the local data / management port, after 6 tries within 1 minute, the alarm is gener-ated. After 5 minutes, the local manage-ment interface is locked and the user cannot log in through the local port. This notifies the OMC, and an administrator has to confirm the alarm before the user can try again.

5 minutes after the alarm gen-eration, the local port is locked and the user cannot log in through the local eNB data / management port interface.

6 unsuccessful local eNB login attempts within 1 minute

Login failed after 6 consecutive tries within 1 minute

The alarm is only used to no-tify the OMC. The alarm is not cleared automatically. It must be confirmed by an OMC administrator to ensure there was no malicious at-tempt to access the eNB.


Critical PCI self-configuration failure Turn off the self-configuring func-tion, and configure the PCI manu-ally. Reboot the eNB.

PCI self-configuration failure

The alarm is generated when self-config-uration is enabled and there is no PCI configured in the PCI list. Disable self-configuration, and configure the PCI manually. Reboot the eNB.

The cell cannot be activated The alarm is generated when self-configuration is enabled and there is no PCI configured in the PCI list.

When self-configuration is ena-bled, the PCI is in conflict with other PCIs in the PCI list.


Major SFP (optical module) tempera-ture is too high

1) In OMC check if the optical mod-ule temperature alarm threshold is set too low; if it is, reset it to a rea-sonable upper limit temperature. If the alarm is still not resolved, go to step (2). 2) Check to see if the room temper-ature is too high; if it is, increase cold air conditioning. If room tem-perature is normal, go to Step (3). 3) Replace the optical module. If the alarm is not resolved, contact tech-nical support.

The optical module tem-perature is too high

The optical module temperature is above the highest allowed temperature threshold.

No S1 link can be established with the optical module, so there is no communication.

Optical module temperature is too high

The external environment must support the optical module to work properly.

1) In OMC check if the optical module temperature alarm threshold is set too low; if it is, reset it to a reasonable up-per limit temperature. If the alarm is still not restored, go to step (2). 2) Check to see if the room temperature is too high; if it is, increase cold air condition-ing. If room temperature is normal, go to Step (3). 3) Replace the optical mod-ule. If the alarm is not re-stored, please contact tech-nical support.

54



Major SFP (optical module) tempera-ture is too low

1) In OMC check if the optical mod-ule temperature alarm threshold is set too low; if it is, reset the lower limit value to a reasonable tempera-ture. If the alarm is still not re-solved, go to step (2). 2) Check whether the room temper-ature is too low. If it is, increase the heating in the room. If the room temperature is normal, go to Step (3). 3) Replace the optical module. If the alarm is not resolved, contact tech-nical support.

The optical module tem-perature is too low

The optical module temperature is be-low the lowest temperature threshold.


Optical module temperature is too low

The external environment must support the optical module to work properly.

1) In OMC check if the optical module temperature alarm threshold is set too low; if it is, reset the lower limit value to a reasonable temperature. If the alarm is still not re-stored, go to step (2). 2) Check whether the room temperature is too low. If it is, increase the heating in the room. If the room tempera-ture is normal, go to Step (3). 3) Replace the optical mod-ule. If the alarm is not re-stored, contact technical sup-port.


Major SFP (optical module) voltage is too high

1) Check if the voltage is normal. If it is normal, go to Step (2). 2) Replace the optical module to see if this resolves the issue. If it does not, contact technical support.

High voltage warning for optical module

The alarm is generated when the maxi-mum voltage of the optical module ex-ceeds the maximum voltage threshold.


Optical module operating volt-age is too high

The optical module power sup-ply is out of range.

1) Check if the voltage is nor-mal. If it is normal, go to Step (2). 2) Replace the optical module to see if this resolves the is-sue. If it does not, contact technical support.


Major SFP (optical module) voltage is too low

1) Check if the voltage is normal. If it is normal, go to Step (2). 2) Replace the optical module to see if this resolves the issue. If it does not, contact technical support.

Low voltage warning for optical module

The alarm is generated when the optical module voltage is less than the mini-mum threshold.


Optical module operating volt-age is too low.

The optical module power sup-ply is out of range.

1) Check if the voltage is nor-mal. If it is normal, go to Step (2). 2) Replace the optical module to see if this resolves the is-sue. If it does not, contact technical support.


Major SFP (optical module) voltage bias is too high (The voltage bias is the DC cur-rent that is deliberately applied between circuits.)

(1) Using a multimeter, check to see if the voltage is normal. If it is nor-mal, go to Step (2). 2) Replace the optical module. If the alarm is not resolved, contact tech-nical support.

The optical module voltage bias value is too high

The optical module bias value is higher than the maximum threshold value, so an alarm is generated.


Operating voltage bias is too high.

The optical module power sup-ply voltage bias is out of range.

(1) Using a multimeter, check to see if the voltage is nor-mal. If it is normal, go to Step (2). 2) Replace the optical mod-ule. If the alarm is not re-solved, contact technical sup-port.


Major SFP (optical module) voltage bias is too low (Voltage bias is the DC current that is deliberately applied be-tween circuits.)

(1) Using a multimeter, check to see if the voltage is normal. If it is nor-mal, go to Step (2). 2) Replace the optical module. If the alarm is not resolved, contact tech-nical support.

The optical module voltage bias value is too low

The optical module bias value is lower than the minimum threshold value, so an alarm is generated.


Operating voltage bias is too low

The optical module power sup-ply voltage bias is out of range

(1) Using a multimeter, check to see if the voltage is normal. If it is normal, go to Step (2). 2) Replace the optical mod-ule. If the alarm is not re-solved, contact technical sup-port.


Minor SFP (optical module) transmit power is too high

1) Check that the optical module is connected correctly. If it is correct and the problem persists, go to step (2). 2) Without exception, replace the optical module.

High optical module trans-mit power

The alarm is generated when the optical module transmit power is higher than the maximum transmit power value.


Optical module transmit power is too high

Improper use of optical mod-ules can attenuate the transmit power too high.

1) Check that the optical module is connected cor-rectly. If it is correct and the problem persists, go to step (2). 2) Without exception, replace the optical module.

55



Minor SFP (optical module) transmit power is too low

1) Check that the optical module is connected correctly. If it is correct and the problem persists, go to step (2).

Low optical module trans-mit power

The alarm is generated when the optical module transmit power is below the minimum transmit power value.


Optical module transmit power is too low

Improper use of optical mod-ules can attenuate the transmit power too low.

1) Check that the optical module is connected cor-rectly. If it is correct and the problem persists, go to step (2). 2) Without exception, replace the optical module.


Minor SFP (optical module) receive power is too high

Check whether the optical fiber line is the correct type and if it is con-nected properly.

High optical module re-ceive power

The alarm is generated when the optical module receive power is higher than the maximum receive power value.


Optical module receive power is too high

Improper use of optical mod-ules can attenuate the receive power too high.

Check whether the optical fi-ber line is the correct type and if it is connected properly.


Minor SFP (optical module) receive power is too low

Check whether the optical fiber line is the correct type and if it is con-nected properly.

Low optical module receive power

The alarm is generated when the optical module receive power is lower than the minimum receive power value.

No S1 link can be established with the optical module, so there is no communication

Optical module receive power is too low

Improper use of optical mod-ules can attenuate the receive power too low.

Check whether the optical fi-ber line is the correct type and if it is connected properly.


Minor SFP (optical module) transmit fault (TX_FAULT) status abnor-mality

1) Check if the optical module is connected correctly. If it is and the problem persists, go to step (2). 2) Without exception, replace the optical module.

The optical module trans-mit fault (TX_FAULT) status is abnormal.

The alarm is generated when the optical module transmitter is faulty.


The optical module transmitter is faulty.

It may be an optical module failure or hardware damage, or it may be associated with choosing to use an SFP module or not.

1) Check if the optical module is connected correctly. If it is and the problem persists, go to step (2). 2) Without exception, replace the optical module.


Minor SFP (optical module) receive line-of-site status abnormality

Check if the optical fiber line is properly secured, and if it is the cor-rect type of optical module.

The optical module receive line-of-site status is abnor-mal.

The alarm is generated when the optical module cannot detect received power.


Undetectable received power by the optical module

May be an optical module fail-ure, or hardware damage, or the optical module is not in-serted, or it may be associated with choosing to use an SFP module or not..

Check if the optical fiber line is properly secured, and if it is the correct type of optical module.


Major SFP (optical module) is not in position

Ensure the optical module is in-serted correctly.

Optical module is not pre-sent

The alarm is generated when the optical port is not connected to the optical module.


The optical module is not in-serted.

The optical module is not in-serted.

Ensure the optical module is inserted correctly.

11217 Equipment Major IP path excessive packet loss rate

1) Use a Gigabit switch, and check whether the negotiation status is Gigabit.

The package loss rate on the WAN port is too high.

The switch periodically checks the GMAC statistic for packet loss on the WAN port (typically every 5/10/15 minutes). If the packet loss rate is higher than the threshold (default 5/100), then the alarm is generated. The alarm will be cancelled when the packet loss rate is lower then the threshold (default is 1/100) for a period of time.

Serious packet loss rate affects traffic throughput.

The switch periodically checks the GMAC statistic for packet loss on the WAN port (typically every 5/10/15 minutes). If the packet loss rate is higher than the threshold (default 5/100), then the alarm is generated.

The package loss rate on the WAN port is too high.

2) Check if there is a large number of attack packets in the network.

The alarm will be cancelled when the packet loss rate is lower then the threshold (de-fault is 1/100) for a period of time.

3) Check if there is any external en-vironment moisture or electromag-netic interference. If so, trouble-shoot and resolve.

56


11218 Equipment Major MAC excessive frame error rate

1. Check the network cable for crys-tal head connection problems.

The frame error rate on the WAN port is too high.

The switch periodically checks the GMAC statistic for frame error rate on the WAN port (typically every 5/10/15 minutes; the default is 5 mins). If the frame error rate is higher than the threshold for the period (default is 5/1000), then the alarm is generated. When the frame er-ror rate is lower than the threshold (de-fault is 1/1000) for the period, the alarm is cancelled.

Serious frame errors will cause the S1 link to break.

The switch periodically checks the GMAC statistic for frame error rate on the WAN port (typically every 5/10/15 minutes; the default is 5 mins). If the frame error rate is higher than the threshold for the pe-riod (default is 5/1000), then the alarm is generated.

The frame error rate on the WAN port is too high.

2. Restart the device. (Switch-ing chip may have caused timing is-sues.)

When the frame error rate is lower than the threshold (de-fault is 1/1000) for the period, the alarm is cancelled.

3. Check the external environment for issues such as moisture or elec-tromagnetic interference. If so, troubleshoot and resolve.

11219 Equipment Major GPS module communication fault

1) Check the GPS power supply. GPS module communica-tion failure

The alarm is generated when the eNB cannot receive messages from the GPS module.

Many eNB issues will occur, such as handover failure, dropped calls, or no traffic at all.

Check peridically to see if the GPS module is functioning nor-mally. A return value of 0 means the GPS module is func-tioning properly. A GPS value of 1 means the GPS module is not functioning properly.

GPS power supply issue

2) Check peridically to see if the GPS module is functioning normally. A return value of 0 means the GPS module is functioning properly. A GPS value of 1 means the GPS mod-ule is not functioning properly.

GPS module is not functioning properly

11220 Equipment Major Phased-Lock Loop (PLL) unlock Contact Baicells support to reconfig-ure PLL

Phased-Lock Loop (PLL) unlock

CDCM6208 unlocked Affects the system clock Check register 21 of CDCM6208 to see if it is unlocked according to bit2.

CDCM6208 unclock Reconfigure CDCM6208

11221 Equipment Major Phased-Lock Loop (PLL) severely unlocked

Restart the system. Phased-Lock Loop (PLL) severely unlocked

CDCM6208 has been unlocked for a long time

Affects the system clock CDCM6208 has been unlocked for at least 30 minutes

CDCM6208 has been unlocked for at least 30 minutes

Restart the system.

11223 Equipment Minor No GPS antenna 1) Check the GPS antenna connec-tion.

2) Peridically check the GPS antenna status. A return value of 0 means the GPS antenna is not in position. A return value of 1 means the GPS an-tenna is in position.

The GPS antenna is not in position.

The GPS antenna is not connected. This affects synchronization and causes many eNB issues, such as handover failure, dropped calls, or no traffic at all.

Peridically check the GPS an-tenna status. A return value of 0 means the GPS antenna is not in position. A return value of 1 means the GPS antenna is in position.

The GPS antenna is not con-nected.

11224 Equipment Warning Interference from neighbor cell detected

Synchronize the cell with the neigh-bor cell.

Interference from neighbor cell detected

The alarm is generated when the UE de-tects interference from a neighbor cell.

The issue affects throughput and BLER.

When the UE detects a differ-ence between DL/UL pathloss

When the UE detects the UL pathloss is higher than the DL pathloss


Critical eNB transmitter sync failure None Transmitter sync failure The alarm is generated when the eNB's transmit oscillator goes out of sync.

Transmitter sync failure No support


Warning eNB receiver sync failure None Receiver sync fault The alarm is generated when the eNB's receive oscillator goes out of sync.

Receiver sync failure No support


Critical eNB transmitter failure due to power exceeds maximum threshold

The operator needs to set the power back to normal.

Transmitter failure due to power exceeds maximum threshold

The alarm is generated when the eNB's transmit power exceeds the maximum threshold. The carrier will be disabled. The alarm can be cleared via RF OAM ac-tion, but the carrier will not be automat-ically enabled.

The carrier will be disabled. Transmitter exceeds maximum power level allowed

57



Warning eNB transmitter failure due to power being out of range

The operator needs to set the power back to normal.

Transmitter failure due to transmit power being out of range

The alarm is generated when the eNB transmit power is out of the normal range. The alarm will be cleared when the transmit power returns to the proper range.

Transmitter power exceeds range failure


Warning eNB receiver failure due to failed state receive path

Check the RF receiver setting, such as Rx channel gain.

Receiver fault due to failed state receive path

The alarm may be generated by a possi-ble receiver error.

Receiver failed state receive path


Critical eNB critical temperature threshold reached

None Critical temperature threshold reached

If the eNB reaches a critical temperature threshold, the carrier will be disabled. The alarm can be cleared via RF OAM ac-tion, but the carrier will not be enabled automatically.

The carrier will be disabled. Critical temperature reached No support


Warning eNB warning temperature threshold reached

None Warning temperature threshold reached

The alarm is generated when a carriers's path temperature has reached a warn-ing threshold.

Warning temperature thresh-old reached

No support


Critical Frequency out of sync None Frequency out of sync The alarm is triggered when the eNB fre-quency goes out of sync

Loss of frequency synchroniza-tion

No support


Critical Time out of sync None Time is not synchronized The alarm is triggered when the eNB timing goes out of sync

Loss of time synchronization No support


Critical Specific time sync source lost None Specific time synchroniza-tion source is lost

The alarm is triggered when the time synchronization source is lost. The alarm is only raised if the source timing has been acquired and then subsequently lost.

Synchronization source lost No support


Major Association failure - Radio Re-source Controller (RRC) be-tween the user equipment / Stream Control Transmission Protocol (SCTP) between the MME and eNB

None RRC SCTP association failed The alarm is generated when there is an RRC / SCTP association failure.

If SCTP failure, the eNB will not have service. If RRC failure, the UE will not connect.

Connection establishment error (RRC / SCTP)

No support


Warning Radio Resource Controller (RRC) S1AP connection success

None RRC S1AP connection suc-ceeded

RRC S1AP connection success alarm. Connection Establishment Error (RRC / S1Ap)

No support

11415 Processing error

Critical LTE OAM configuration failure Check LTE configuration. Critical LTE OAM configura-tion failure

1) Error in SON carrier fre-quency or DL Tx power configu-ration.

2) Error in RRM cell configura-tion.

3) Failure to process S1AP pro-visioning request or failure to send S1AP provisioning rseponse to OAM.

4) Failure to process an RRC provisioning request or failure to send an RRC provisioning re-sponse to OAM.

5) Failure in startup configura-tion


Critical No free Physical Cell Identifier (PCI) to use in the provisioned list

None No configuration list for PCI is available

The alarm is generated when there is no PCI information configured.

Configuration or customization error (PCI)

No support

58


12400 Equipment Critical Hardware self-test failure Export the logs, and reboot the sys-tem.

Hardware self-test failure The module detects whether the vari-ous hardware states are normal dur-ing the startup process.

Module cannot start up Device access failure or de-vice initialize failure

1) APD firmware error

2) Failure of crystal oscillator voltage configuration

3) SPI bus access failure

4) I2C bus access failure

5) CPLD configuraton failure


Major Optical module temperature is too high

1) Check the room temperature to see if it is too high. If it is, increase the cold air conditioning. If the room temperature is normal, go to step (2). 2) Replace the optical mod-ule. If the alarm is not restored, con-tact technical support.

Temperature anomalies The optical module temperature gets too high for normal operation.

An optical module running for a long time in a high-tempera-ture environment can easily lead to device failure.

The Radio Unit (RU) is gener-ated when the module temper-ature is too high.

The ambient temperature is too high.

1) Check the room tempera-ture to see if it is too high. If it is, increase the cold air con-ditioning. If the room tem-perature is normal, go to step (2). 2) Replace the optical module. If the alarm is not re-stored, contact technical sup-port.

12402 Equipment Major VSWR overage Check to see if the antenna feeder is connected properly. If it is con-nected properly, replace the feeder.

VSWR is too high The system detects a mismatch between the feeder connection and the device. In this case, it leads to the VSWR being too high.

This problem affects service quality. The long-term opera-tion may lead to damage of the power amplifier.

The VSWR reading is higher than the threshold (default is 6).

1) The feeder is not connected properly.

2) Feeder faults

Check whether the connec-tion is loose or there is dam-age to the antenna.

12403 Equipment Minor Avalanche Photodiode (APD) chip status error

Export the logs, and reboot the sys-tem.

APD chip is not working normally

In order to ensure the quality of the sig-nal, the APD will correct the signal.

Affects quality of service APD chip indicates an internal state error or a chip access er-ror

APD Internal error IF the alarm is not cancelled after 3 minutes, restart the system.

12404 Equipment Major Power amplifier current over-rage

Check whether the Tx Power is too high.

Power amplifier overflow Detection of power amplifier cur-rent overage while running

If running over the power limit for a long time, can cause dam-age to the power amplifier

Power amplifier current ex-ceeds threshold

Excessive power

12405 Equipment Major No Tx power alarm 1) Check the RF Status. If off, turn on the switch and check again.

2) Restart the system.

No Tx power When the eNB power is too low, the alarm is generated.

Affects throughput and cover-age

When the Tx power of each an-tenna is lower than 10 dB, it triggers the alarm.

12406 Equipment Major RSSI is unbalanced 1) Check whether the RSSI value be-tween 2 channels is unbalanced.

2) Restart the system.

RSSI unbalanced The alarm is generated when the receiv-ing signals of 2 channels on the same eNB are extremely different.

Affects traffic throughput Issues occurs when the signal difference value of the receiv-ing signal of 2 channels is greater than 20 dBm

Receiving channel anomaly Restart the system

59

4.2.2.2 Logs

The Baicells system collects device, operation, backup, system, security, and debug logs during the opera-tion of the system. Viewing the log files and the flow of logs provides valuable information about what events took place and when. Many operators use third-party applications to continually watch for key words or word strings in the logs that then alert the operator of certain events or outcomes. When inves-tigating a system alarm, pair the log information to the probable causes to help isolate the issue.

Table 4-3 summarizes the interfaces where you can generate, view, and export logs.

Table 4-3: Where to Generate Logs

User Interface Navigation Description

OMC eNB > Monitor > Operation > Information > Logs

Run a Device Report on the eNB and its associ-ated UEs.

System > OMC Log > Operation Log Provides a record of all OMC activities. Use query or advanced query to search by Opera-tion Name, Operator, User Name, Operate IP, Time, or Record Detail, and to Export the logs.

System > OMC Log > Security Log Same as for Operation Logs but specific to sys-tem security related events

System > OMC Log > System Log Run a Device Report (same as described in first row)

eNB GUI System > Backup > Backup Log Files Use to collect the latest backup log file.

System > Backup > Backup Crash Logs Use to get eNB backup crash log files, including error logs pertaining to hardware and software issues. Logs will contain as much of the latest data records as can be preserved within the cache space.

4.2.3 Statistics & Performance The dashboard statistics and performance graphs provide key network performance indicators (KPI). The statistics block of the dashboard presents three sets of data: eNB Active, eNB Online, and CPE Connect (Figure 4-28). 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 net-work - and the number that are offline. The third block, CPE Connect, shows the total number of UEs connected to the network as well as the number of UEs that are disconnected. If you look at these statistics and notice connection issues, you will need to drill down on specific eNBs or UEs to investigate.

60

Figure 4-28: Statistics

If the eNB Active data is showing some drops, it could mean there is an issue with the Baicells cloud or a backhaul issue, especially if all sites went down. In such a case you would go to the OMC > eNB > Monitor page, and look for active outages (Active Status = Inactive). For dropped sites, you would try to access that site and locate the problem. If you are using a third-party network performance monitoring app, you could check to see if there is an internet outage.

If you are seeing CPE disconnects and if the eNB’s are online, there may be a problem with the connection to the Home Subscriber Server (HSS) in the EPC (eNB > Monitor > MME Status = Inactive). It could also be some type of interference between the UE and eNB. In this case you would check the RF readouts, such as BLER (eNB GUI > BTS Info > Basic Info > Status Info > Radio Resource Usage), and CINR and SINR (OMC > CPE > Monitor > History > CINR1 and CINR2, and SINR graphs).

61

The Performance block of the dashboard provides graphs of throughput, physical resource block (PRB) utilization, and UE count. 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.

The throughput graph shows the aggregate uplink (red) and downlink (black) throughput rates across all of the operator’s eNBs over the last 5 minutes (Figure 4-29). If you have multiple users complaining of slow network speeds, review this graph to see how eNBs are performing overall in regards to throughput. Some suggestions for responding to reports of high latency or low speed are covered in the troubleshooting section of this document. Please refer to these troubleshooting steps to try and resolve throughput issues: UE-7 High Latency and UE-8 Low Speed. Refer, also, to eNB-5 Link Flap or Drop, which includes other rea-sons for service degradation that you may need to check.

Figure 4-29: Throughput & PRB Utilization

The PRB utilization graph shows the average percentage 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 eNB allocates PRBs to the UEs based on their RF signal quality. If the PRB utilization number is approaching 80%, it means your eNB is reaching capacity. When you look at PRB utilization in combination with aggre-gate throughput numbers and both are high, you probably need to start planning to add more eNBs to handle existing and new subscriber traffic.

If you are reaching maximum capacity on an eNB channel but seeing lower throughput numbers, refer to the troubleshooting steps in section 5 concerning low speed, interference, and hardware failures.

The UE Count (Figure 4-30) shows the total number of connected users at that point in time.

62

Figure 4-30: UE Count

In addition to the KPIs described in the OMC dashboard, drill-down data for individual eNBs and UEs are discussed throughout this Maintenance section of the document. Refer specifically to section 4.10 Addi-tional KPI Information.

4.2.4 eNB The eNB section of the Dashboard lists all of the operator’s eNBs and contains a search bar so you can find and check the status of individual eNBs (Figure 4-31).

Figure 4-31: Dashboard eNBs

4.2.5 CPE In the CPE part of the Dashboard window, if you click on the double arrows on the right, as shown in Figure 4-32, the OMC will jump you into the CPE > Monitor sub-menu. The CPE > Monitor fields are explained in section 4.4.1.

63

Figure 4-32: Dashboard > CPE > Monitor

4.3 OMC - eNB The OMC eNB menu includes 4 sub-menus: Monitor, Maintenance, Register, and Upgrade (Figure 4-33). From the OMC dashboard, when you select a specific eNB to drill down on its status, the window takes you into the eNB Monitor page.

64

Figure 4-33: eNB Menu

4.3.1 Monitor

4.3.1.1 General Information

The eNB monitor function allows you to see any eNBs that are configured in your network. Figures 4-34, 4-35, and 4-36 show the fields as you scroll from left to right. The displays in Figures 4-35 and 4-36 include a HaloB eNB in the lists. All of the fields are explained in Table 4-4.

Figure 4-34: eNB Monitor (1 of 3)

65

Figure 4-35: eNB Monitor (2 of 3) – HaloB eNB Included in List

Scrolling to the right…..

Figure 4-36: eNB Monitor (3 of 3) – HaloB eNB Included in List

Scrolling to the right…..

Table 4-4: 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, ans Operation.

Alarm Provides the color code of the severity, as well as the number count at each se-

verity level

66

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 parame-ter 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). Active means the S1 sig-naling is up and that TX/RX are on. If the status reports inactive, check the MME, IPSec, and OMC status. Refer to section 5.2 eNB Issues.

MME Status The Mobility Management Entity responsible for initiating paging and authenti-cation of mobile devices is active or inactive

KPI Report Status Key Performance Indicators report status is normal or broken. This field is re-served for future use.

Sync Status The eNB is synchronized or unsynchronized with the GPS. If the GPS is unsyn-chronized, check to see if the GPS antenna and connector are connected; also, ensure GPS Sync is enabled. Refer to section 5.2 eNB Issues.

UE Count Number of users actively connected to this eNB

Uptime Length of time this eNB has been operational - dd:hh:mm:ss. The uptime indi-cates how long the eNB has been online. If the uptime is shorter than expected, the eNB may have rebooted or have been rebooted or lost connection with the backhaul.

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. This information may be needed when troubleshooting.

Software Version Software version running on the eNB. Check the Baicells website to see if there is a later firmware version available. If there is, we recommend upgrading to the latest available release. Each release typically includes bug fixes, enhancements, and sometimes new features.

UBoot Version Universal boot loader code level information sometimes needed when trouble-shooting issues.

Kernel Version Kernel code level information sometimes needed when troubleshooting issues. The firmware includes the kernel.

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

67

Satellites The number of GPS satellites found and reported by the eNB. This field is active only in eNBs running BaiBS_RTS_2.1.x or later.

HaloB-Centralized Shows if the centralized mode of the HaloB feature is enabled or disabled on this eNB. For HaloB configuration information, refer to the HaloB User Guide.

You can review the eNB list, or you can enter a specific eNB serial number or cell name and perform a search for it. Use the Filter icon in the column row (Figure 4-37) to filter the list of eNBs by disconnected, synchronized failure, and/or connected.

Figure 4-37: Filter

4.3.1.2 SubFrame Assignment & Special SubFrame Patterns Configuration

For a specific eNB listed in the eNB > Monitor window, under Operations if you select Settings you are presented a dialogue window with 4 configuration tabs: Wireless, Network, ICIC, and NTP. While these fields are explained in the Baicells Configuration & Network Administration Guide, here we describe two important wireless fields, SubFrame Assignment and Special SubFrame Patterns, in more detail.

Most internet users use a lot more download than upload bandwidth. In LTE Time Division Duplexing (TDD), the downlink/uplink transmission ratios (that is, data throughput from eNB to UE or UE to eNB) can be manipulated using the Subframe Assignment (SA) field. The guard period of an eNB switching be-tween downlink transmissions of traffic and uplink receptions of traffic can be manipulated using the Special Subframe Patterns (SSP) field. Both of these settings may be found in OMC > eNB > Monitor when you click on Operation for a given eNB and select Settings, or in the eNB GUI > Quick Settings.

The Baicells eNB SA value may be set to 1 or 2. Setting the value to 1 means the downlink and uplink transmissions get equal time. Setting the SA value to 2 (default) means the downlink gets 3 times the amount of time for transmissions as the uplink (3:1 ratio).

The LTE SSP configuration options are SSP0 through SSP8 (Figure 4-38), but only categories SSP5 and SSP7 framing formats are used at this time in a Baicells eNB. The SSP value represents the turn-around time based on distance between the UE and the eNB.

https://na.baicells.com/downloads/#1533842982626-109b3fc0-ba0e


68

Typically, the farther the distance the UE is from the eNB the more likely it is you will need to use the longer guard period of SSP5. The guard period determines the maximum supportable cell size; the guard has to be long enough to cover the propagation delay of downlink interferers. The default setting is 7.

Important: All sectors on the same tower should use the same Special Sf Pattern setting of 5 or 7.

If the default of 7 is used for SSP and you as the operator want the eNB to reach farther distances, you might consider changing the SSP value to 5 and monitoring the resulting effect on users. Refer to Figure 4-38. Just make sure to set the SSP value the same for all eNBs on the same tower.

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

Figure 4-38: Wireless Settings > Special Sf Patterns Options

4.3.2 Maintenance The eNB > Maintenance sub-menu is where you can create tasks to reboot, reset passwords, or run device logs on one or more eNBs. Reboots are necessary after firmware upgrades, certain configuration changes, and at times for troubleshooting purposes. When an eNB is rebooted, service is disrupted.

4.3.3 Register As your network grows, use the eNB > Register sub-menu to create and maintain eNB device groups. The eNBs you assign to a device group share the same configuration parameters. An example of when using device groups is more efficient is during upgrades. To upgrade multiple eNBs at the same time, you can simply select each device group to update, and the system will upgrade all of the eNBs in that device group, 5 at a time.

https://community.na.baicells.com/t/baitip-of-the-day-december-14th-2016-subframes-and-special-subframes/163


69

When added in software, all eNBs default to the default device group. However, you can define your own device groups and assign eNBs as needed. Device groups save time, too, when making configuration changes that you want to disperse across multiple eNBs associated to that device group.

The Register sub-menu also is used to import feature licenses, e.g., when implementing the HaloB solution.

4.3.4 Upgrade As mentioned in section 4.3.3, you can use device groups to expedite upgrading multiple eNBs that share the same configuration parameters. Please refer to the Baicells Configuration & Network Administration Guide for procedures on performing upgrades.

A best practice is to regularly check with Baicells for the latest eNB and UE firmware, and to keep network components upgraded to the latest code. Most software versions include bug fixes and sometimes en-hancements to or new features. Use the eNB > Upgrade function to perform code changes on equipment. ENBs and UEs will reboot upon upgrading the firmware. Most operators thus choose less busy network times to upgrade in order to minimize service disruption.

Caution: The selected eNBs will be restarted according to the execution plan, and the eNBs will stop serving UEs during the restart.

4.4 OMC - CPE

The OMC CPE menu is similar to the eNB menu: Monitor, Maintenance, Register, and Upgrade. Ongoing CPE monitoring and maintenance guidance is provided in this section.

4.4.1 Monitor Make it a practice to visit the CPE > Monitor fields regularly to check the list of UEs in the network and the data fields that are meaningful to throughput and quality of service. You can view both current and histor-ical data on a per-UE basis. Referring to the Baicells Configuration & Network Administration Guide, some of the more critical data points to check are presented when you click on the graph icon in the History column for a given UE. The History graphs (Figure 4-39) present UL/DL MCS, RSRP1/2, CINR1/2, SINR, DL/UL Throughput values, as explained below the figure.

Note: Cat6 UEs will report 4 instead of 2 RSRP and CINR values.

Figure 4-39: History Graphs




70

• MCS and CINR - The Modulation and Coding Scheme (MCS) for uplink and downlink and the Car-rier-to-Interference-plus-Noise Ratio (CINR) values provide indications of channel quality. 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 available for the user. If the MCS value is in the single digits, the user likely has chan-nel quality problems such as RF obstructions or interference affecting service. You may need to investigate each UE further.

• RSRP and SINR – Reference Symbol Received Power (RSRP) and Signal-to-Interference-plus-Noise Ratio (SINR) provide information about signal strength. Weak signal strength can cause connectiv-ity issues and dropped sessions. Refer to the troubleshooting section, UE-2 Dropped Connections and UE-5 Weak RF Signal.

Refer to section 4.10 Additional KPI Information for more information about interpreting these values.

4.4.2 Maintenance The CPE > Maintenance sub-menu is where you can create a reboot task for one or more CPEs. Reboots are necessary after firmware upgrades, certain configuration changes, and at times for troubleshooting purposes. When a CPE is rebooted, service is disrupted.

Unlike the eNB > Maintenance sub-menu, the CPE > Maintenance sub-menu does not offer the reset pass-words or run device reports options. Typically, the end-user will be the person who initiates a password reset using the UE GUI. There are no device reports for the UEs.

4.4.3 Register The CPE > Register > Device sub-menu works the same way as for eNB > Register > Device, except it is for UEs. It saves time and is more efficient to set up user groups for users sharing the same configuration settings. Adding a new CPE via OMC is referred to as registering the CPE. If not assigned to a custom user group, a new CPE will be placed in the default user group.

4.4.4 Upgrade The same guidance described for eNBs in section 4.3.4 applies to UEs as well.

4.5 OMC - Strategy > PCI Lock

PCI Lock is a type of scan mode that allows you to select the specific E-UTRA Absolute Radio Frequency Channel Number (EARFCN) and Physical Cell Identifier (PCI) for a device. You can add more than one PCI Lock list per device. The UE will scan the list for eNBs with the EARFCN and PCI combination.

If you need to change the EARFCN or 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 imple-ment the bulk-change. The steps for configuring PCI Lock are described in the Baicells Configuration & Network Administration Guide.



71

Note 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.

Caution: The selected eNBs will be restarted according to the execution plan, and the eNBs will stop serving UEs during the restart.

Any UEs that are offline during the execution of the task will not receive the change. You may need to check the status of each one and possibly reinitiate the task to ensure all UEs associated to the eNB(s) are updated.

4.6 OMC - System

The System menu in OMC refers to the OMC as a system. This menu includes two options: Security and OMC Log.

4.6.1 Security The System > Security sub-menu is where you establish roles, user groups, and administrative users in the OMC. Like device groups for eNB, user groups provide a way of grouping OMC users with the same config-uration settings together. Managing configuration changes through user groups is more efficient than mak-ing changes on a per-user basis. Periodically check the names and roles of OMC administrative users to ensure the correct privileges are applied as intended. How to configure OMC administrative user groups and roles is described in the Baicells Configuration & Network Administration Guide.

4.6.2 OMC Log Since there may be multiple OMC administrators, it is a good idea to regularly scan through the logging events reported in the OMC. Select System > OMC Log to open the Operation Log window. An operation log is simply a record of events that have taken place in the operator’s CloudCore account (Figure 4-40). These logs represent all CloudCore user activity, and are useful for a quick look-up of actions taken by all administrative users.

The latest log appears on the top of the list. Regularly check for any anomalies such as unknown users, unauthorized access, and irregular activities that may require further investigation.


72

Figure 4-40: OMC Operation Logs

The OMC Security Log tab (Figure 4-41) lists OMC administrative user login and logout activities, providing details about user name, IP address, date and time, etc., for each listing.

Figure 4-41: OMC Security Logs

The OMC System Log tab (Figure 4-42) provides serial number, device name, device type, operate IP, op-eration type, progress, and time.

73

Figure 4-42: OMC System Logs

4.7 BOSS Monitoring

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. During ongoing management of the network, use BOSS to check SIM card inventory and to find, verify, or change subscriber information. Keeping track of SIM card inven-tory is important for quick resolution of SIM-related issues in the field and for adding individual or bulk subscribers. It is likely that you will need to enable, edit, or delete service plans over time in BOSS to differentiate service offers, e.g., for sales campaigns, as the network grows, and so forth.

4.8 eNB GUI Monitoring

In addition to the OMC monitoring fields, the eNB GUI contains other fields specific to each eNB. Only the fields not already covered in the OMC sections 4.2 through 4.6 are covered in this section.

NOTE: The eNB GUI menu varies according to the eNB operation mode (standard or HaloB), soft-ware version, and hardware model. HaloB is an optional, value-added operator feature. This docu-ment 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 the HaloB feature.


74

4.8.1 Additional eNB GUI BTS Info Fields The eNB GUI offers additional information about each specific eNB that you may need to check periodically for purposes of monitoring and managing eNB performance. For example, if a user is experiencing trouble connecting to the network you may need to check the Cell Status field to see if the status of the eNB is reported as active or inactive (refer to UE-1 No network connection and eNB-3 Fails to start).

Sometimes you may need to check the GPS Sync Status to see if the eNB is synchronized with the GPS (refer to eNB-2 GPS unsynchronized). Normally alarms are generated for these issues, which will typically trigger you to check the sync status using the eNB GUI. For multiple eNBs sharing one site, make sure GPS synchronization is enabled on each eNB and that the GPS Sync is successful. Otherwise, timing collision will occur. Other status indicators under the BTS Info menu include MME status, OMC status, IPSec status, and UE-related status information.

4.8.2 Additional eNB GUI System Fields

The System fields appear only in the eNB GUI. Use these fields to check network timing synchronization and to upgrade the software, back up the configuration, or restore a configuration on an eNB. You should routinely perform backups of the eNB configuration, e.g., once a week or once a month depending on how often the configuration is changed. The data may be needed in the event you have to recover your settings, which enables you to do so without manually reconfiguring everything. You can also reset the eNB pass-word using this menu. As with any computer or web site, it is a good idea to periodically change the pass-word to keep access more secure.

4.8.3 Additional eNB GUI Network Fields The additional network fields in the eNB GUI pertain to the eNB’s connection with the external network. On a per-eNB level you can modify any of the network settings when needed using the eNB GUI. As your network grows you may need to add more IP addresses or other DNS servers, for example.

4.8.4 Additional eNB GUI BTS Settings Most of the fields in the eNB GUI > BTS Setting windows concern how the eNB operates, including security algorithms, identification of the eNB’s management server (e.g., CloudCore OMC), and the LTE synchroni-zation settings between geographically adjacent eNBs.

The security algorithms, called ciphering and integrity algorithms, pertain to the encryption algorithms used in relation to the LTE core network setup. The sync setting is required by LTE standards to ensure synchronized transmissions in the same geographical area, necessary to avoid eNBs interfering with one another, optimize bandwidth usage, and enhance network capacity.

For HaloB-enabled eNBs the BTS Setting will show two additional sub-menus: HaloB Setting, where you enable/disable HaloB operation, and License Management, where you import the feature key license spe-cific to each HaloB eNB. Operators can move an eNB in and out of HaloB operation if they have purchased the HaloB feature. To read more about HaloB, please refer to the Baicells HaloB User Guide.


75

4.8.5 Additional eNB GUI LTE Settings In the eNB GUI the LTE settings pertain to mobility, RF signaling, and power control. All are important to how efficiently the eNB processes traffic and to user quality of service.

Please refer to the Baicells Configuration & Network Administration Guide for guidance on configuring or changing any of these parameters. Additional mobility information related to configuring X2 handoffs is provided in the Baicells Handoff Configuration Guide (available upon request from Baicells support).

In most cases, the advanced LTE parameters should be left with their default values. However, sometimes the Baicells support team will adjust these to help resolve operator issues. Any modification to the ad-vanced fields should be determined only by experienced wireless professionals.

4.9 UE GUI Monitoring

As with the eNB GUI, further monitoring and actions may be taken using the UE GUI on each customer’s indoor or outdoor on-premises equipment. The UE GUI contains more fields than does the OMC. Only the fields not already covered in the OMC sections 4.2 through 4.6 are covered in this section.

4.9.1 Additional UE GUI Status Fields Under the Overview sub-menu, the real-time status and configuration settings are associated with infor-mation very specific to each UE unit. For example, you can quickly tell if the USIM card status is reported as connected or unconnected; to which operator the UE belongs; what is the data throughput on the UE; RF signaling values; usage time; and so forth. Part of routine maintenance is to check these high-level fields periodically to ensure the subscriber is receiving an acceptable level of service. A number of trou-bleshooting steps rely on information reported by the UE GUI.

4.9.2 Additional UE GUI Network Fields The network fields that appear in the UE GUI but not the OMC include status and statistical information, as measured by the UE, and some settings that pertain to the UE’s connection to the eNB and backhaul network. The network settings pertain to local and wide area network, including network mode, static routing, and DMZ (firewalls).

For certain models of UE, such as EG2030C, this sub-menu also contains wireless LAN (WLAN) settings. Newer versions of the UE GUI may include additional features you can enable, such as Wifidog and Wi-Fi alignment. These features are explained in the Baicells Configuration & Network Administration Guide.

Refer to section 4.10 Additional KPI Information for more information related to UE key performance in-dicators.



76

4.9.3 Additional UE GUI LTE Fields Visit the UE GUI whenever you need to check or change the connection method, frequency scan method, gateway configurations, and PIN settings. This menu offers the ability to implement or remove frequency and PCI lock.

4.9.4 Additional UE GUI Security Fields Firewall settings, filtering and forwarding rules, access restrictions, and plug-and-play may be set up or changed in the UE GUI security menu. The filtering and restriction settings usually need to be managed regularly to ensure that only authorized users are able to access the UE and to limit the type of traffic coming into and going out of the UE. For example, if a child is using the UE to access the internet, the parent may not want the child to be able to access certain websites. In such a case you would enable the firewall and URL Filtering and identify the websites that would be restricted from access. Later versions of the UE GUI include a featue called Attack Protection, which you may use to help detect and prevent hacker attacks. If the user is experiencing TCP, UDP, or ICMP attacks, you would come to the Security > Attack Protection fields to configure the settings.

4.9.5 Additional UE GUI VPN Fields Use the VPN menu to enable the user to connect the UE to a virtual private network (VPN). People who telecommute for work often use the company’s VPN to access their intranet, for example. You can con-figure the VPN connection as L2 or L2TP. This menu is also where you enable/disable or change IPSec policies such as IKE and ESP.

4.9.6 Additional UE GUI System Fields There are several fields in the System menu that are relevant for maintenance and troubleshooting. You can configure network timing settings, change the account password, enable the Web GUI, configure TR-069 security, set up SNMP, restore configuration data, and reboot the UE. Use this menu, also, to initiate diagnostic tests such as ping, traceroute, and iperf. Run a ping test to see if the UE is communicating with other network devices, e.g., an eNB; run a traceroute to see how long it takes for the UE packets to reach a destination; and use iperf to measure throughput. In section 5 Troubleshooting, these tests are mentioned in the context of identifying and solving particular types of issues.

4.10 Additional KPI Information

4.10.1 Overview The key performance indicators (KPIs) primarily focus on wireless network performance, with some back-haul network check points. Baicells provides three wireless KPIs which are measured by the UE and re-ported to the serving eNB on a regular basis:

77

• Reference Signal Received Power (RSRP) is the average power of the LTE reference signals over the entire bandwidth. The range is -44 to -140dBm.

• Received Signal Strength Indicator (RSSI) measures the total received wide-band power including the noise.

• Reference Signal Received Quality (RSRQ) indicates the quality of the received reference signal. The range is -3 to -19.5 dB.

RSRQ formula:

RSRQ = N x RSRP / RSSI, where:

N = Number of Physical Resource Blocks (PRBs)

First, look at the UE’s RSRP measurement. This value is probably the most important for the operator to check. Is the value within the range? We recommend this value to be at least -110 dBm; if the value is lower, there is a problem. Refer to Figure 4-43 on evaluating RSRP and Signal-to-Interference-Plus-Noise Ratio (SINR) values.

Figure 4-43: RSRP/SINR

Typically, there is a delta of about 30 dBm between RSRP and RSSI. You will often see RSSI around -70 or -80 dBm. Beyond that, there is likely a problem. RSRP does a better job of measuring signal power from a specific sector while potentially excluding noise from other sectors.

RSRQ depends on the serving cell power and the number of transmit antennas. RSRQ gives you an indica-tion of the noise floor. Noise is anything not contributing to the required signal, such as distortion, inter-ference, and defraction. Of course, noise distorts the required signal.

Refer to Appendix A: LTE References for more information on KPI measurements.

4.10.2 Monitor Channel Conditions Poor channel conditions can lead to quality of service (QoS) issues. For instance, a subscriber may have network connectivity, but data packets drop; voice or video is disrupted; a web page may take a long time to refresh; and so forth. Check the following for indications of poor channel conditions in the RF signal.

1) Check the eNB GUI or OMC parameters concerning radio conditions described in Table 4-5.

78

Table 4-5: UE Status Parameters


dlcqi Downlink Channel Quality Indicator (DLCQI) indicates how good or bad the communica-tion channel quality is for data being transmitted from the eNB to the UE. CQI is a combi-nation of SNR, SINR, and SNDR. Value range is 1-15. We recommend a value of 10 or above. Check this value when the UL and DL speeds are off, in which case you will need to try and improve the signal.

ulmcs Uplink Modulation and Coding Scheme (ULMCS) is a numerical index based on Orthogonal Frequency Division Multiplexing (OFDM) that represents the maximum data rate that the UE can achieve when transmitting data over-the-air to the eNB. The MCS index value comprises several variables, including channel width, modulation type, coding rate, and spatial streams. The MCS is assigned by the eNB to the UE. If the MCS value is low, check the RSRP, SINR, and CINR.

dlmcs Downlink Modulation and Coding Scheme (DLMCS) – see description for “ulmcs” above

2) Using the eNB GUI, examine the LTE > Advanced and Mobility Parameter (Figure 4-44) settings. The following are recommended settings to optimize channel conditions.

a) LTE > Advanced > Power Control Parameters:

• Max Pathloss – At present, the default is 125. We recommend you change the value to 135 to accommodate for higher pathloss, for situations where there is a lot of foliage be-tween the UE and eNB.

• Target UL SINR – The default is 5 and recommended.

• Po_ue_pusch – The default setting is 0. We recommend you set the value to 7 to increase the uplink UE signaling power.

b) LTE > Mobility Parameters:

• A2 Event threshold – The default setting is 65. We recommend setting the value to 0. This will accommodate a minimum RSRP of -140 dBm and stop A2 triggers that may cause UE drops or flapping between two eNBs.

• Cell Selection Parameter > Qrxlevmin (dBm) – The default is -60 dBm. We recommend changing the value to -70 in NLOS situations. The minimum RSRP required for cell selec-tion = 2Qrxlevmin+Qrxlevminoffset. Thus, setting the parameter to -70 will give the minimum RSRP=2-60+1 = -139 dBm.

c) LTE > Advanced > Random Access Parameters:

• Zero Correlation Zone Config – The default is 10, but if the distance needed to be covered by the eNB is greater than 5 miles we recommend changing the value to 12. Doing so will take the distance covered to around 9 miles. The value can be increased to 15 to go be-yond that if there is clear line-of-sight (LOS) between the eNB and UE.

79

All of these recommended parameters should help to optimize the channel conditions. They will not dras-tically improve the RSRP value, but they will help the UEs in bad RF conditions to latch onto the eNB by improving the RF signals. The minimum RSRP of -110 dBm is recommended; going below that is not advis-able.

3) Using the eNB GUI, examine the LTE > Mobility > A2 Event Threshold settings:

In cases where there is a coverage overlap between sectors on the same tower or overlap between sectors of different towers, the A2 measure in the eNB settings has been discovered to be a key contributor to-wards maintaining a stable connection between the eNB and UE. An A2 event is triggered when the serving cell RSRP goes below the set threshold value in the eNB settings. Let’s say the threshold value is set to 65; the way it works is A2 = 65-140 = -75 dBm. Therefore, as soon as the RSRP reaches below -75 dBm the A2 event is triggered and the UE starts looking for a signal better than -75 dBm, thus throttling its connection with the current eNB. This can cause the UE to drop off and jump between eNBs (except for when they are PCI locked).

This case is helpful for mobile devices that are moving around and need to be handed off between cell sites. Since handoff is not required for fixed users in such cases, the A2 setting can be lowered down to zero, so that the A2 threshold = 0-140 = -140 dBm. This will prevent the UE from searching for other po-tential eNBs serving a signal better than -140 dBm. This has proved beneficial in increasing the UL and DL modulation and coding scheme (MCS), mostly in cases of overlapping cell coverage.

Please note that for the setting to take effect, the eNB has to be rebooted after changing the setting.

Figure 4-44: A2 Event Threshold

80

4.10.3 Monitor LAN and WAN Backhaul Some of the more critical settings affecting LAN and WAN backhaul are described below. It is a good idea to check these settings on a regular basis.

1) DMZ settings In technology, the Demilitarized Zone (DMZ) refers to a firewall between incoming WAN traffic and the LAN to which the UE is connected. Two basic DMZ methods are (a) using a single firewall, also known as the three-legged model, and (b) using dual firewalls (Figure 4-45). These architectures can be expanded to create very complex architectures depending on the network requirements.

Figure 4-45: 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 Con-trol Message Protocol (ICMP) redirect error messages, for which you enter the host server IP address. Both of these are configured in the UE GUI > Network > DMZ sub-menu. Refer to Figure 4-46 and Table 4-6. Activate any changes by clicking on SAVE & APPLY.

Figure 4-46: DMZ

81

Table 4-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.

2) 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 UE GUI > Network > Static Routes sub-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 4-47).

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 one or more static routes 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 4-48). 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.

Figure 4-47: Static Routes

82

Figure 4-48: Configure Static Routes

3) LAN Settings

In the UE GUI > Network > LAN Settings sub-menu, 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 change the address, for example to make the address easier to remember, make sure that the address you choose is unique to your network. You are going need to access the Web management page using the new IP address.

You can bind an IP address to the UE based on its Media Access Control (MAC) address. If binding is con-figured, the UE will receive the same IP address each time it accesses the DHCP server. When configured as a DHCP server, the UE automatically provides the TCP/IP configuration for the LAN clients that support DHCP client capabilities. If DHCP services are disabled, you must have another DHCP server on the LAN or each client must be configured manually.

To add a device to the setup list, click on Add List. After entering the information, click on SAVE & APPLY to save your data. Refer to Figures 4-49 and 4-50, and Table 4-7.

83

Figure 4-49: LAN Settings (1 of 2)

Figure 4-50: LAN Settings (2 of 2)

84

Table 4-7: LAN Settings


LAN Host Settings

IP Address Enter the UE’s IP address

Subnet Mask Enter the UE’s subnet mask address

DHCP Settings

DHCP Server Select the check box next to Enable to configure the UE as a DHCP server

Start IP Address Enter the starting IP address that the DHCP server may use for individual clients associated with this UE. Must be a different IP address from the one set in the Network > LAN Settings, but must be on the same network segment.

End IP Address Enter the ending IP address that the DHCP server may use for individual clients associated with this UE. Must be a different IP address from the one set in the Network > LAN Settings, but must be on the same network segment.

Lease Time Enter the lease time (in minutes). The range is 2 to 1440 minutes. The default is 720 minutes (recommended).

Bundled Address List

Index List number

IP Address IP address of the device associating to the UE

MAC Address MAC address of the device associating to the UE

4) Security

The UE GUI Security menu opens to several sub-menus, as shown in Figure 4-51. If you enable the firewall, the other sub-menus allow you to configure the firewall‘s MAC filter, IP filter, and so forth. If you make a change, click on SAVE & APPLY to save the data.

Figure 4-51: Security Sub-Menus

85

a) MAC Filter

Media Access Control (MAC) Filtering allows you to identify a list of devices either allowed to access or denied from accessing the UE. As a subscriber brings in new devices or allows guest devices, the list must be maintained. In the UE GUI > Security > MAC Filtering sub-menu, select Enable to enable MAC filtering, and then determine whether you will allow or forbid the defined MAC address to access the UE. Refer to Figure 4-52 and Table 4-8. To add a MAC Filtering rule, under MAC Filtering List select Add List. After en-tering the information, select Submit to save the data.

Figure 4-52: MAC Filter > Add List

Table 4-8: MAC Filter


MAC Filter Select the check box next to Enable to enable MAC filtering

Authority besides list items

Select allow to allow the MAC addresses in the MAC List, or select forbid to 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.

86

b) IP Filter

The same is true for Internet Protocol (IP) filtering as was described for MAC Filtering. IP Filtering allows you to filter data based on the IP address of a source device. You can define a list of devices either allowed to access or denied from accessing the UE. The list must be maintained over time. 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 4-53 and explained in Table 4-9. When finished, select SAVE & APPLY to activate the settings.

Figure 4-53: IP Filter

Table 4-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 al-low to or forbid from the UE

87

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 Range

Enter the IP address range for the destination device(s) to be filtered, in the for-mat 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

c) 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 4-54. 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. The list should be maintained as needed to prohibit access to unwanted URLs through the UE.

Figure 4-54: URL Filter

88

d) Port Forwarding

When Network Address Translation (NAT) is enabled on the UE, you can redirect a communication re-quest 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 ex-ample, 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. You may need to enable/disable or add port filtering rules for the UE.

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 4-55. To add more lists, click on ADD. The fields are explained in Table 4-10. After entering the information, select SAVE & APPLY to activate the settings.

Figure 4-55: Port Forwarding

89

Table 4-10: Port Forwarding


Service Type Select the type of service, either Custom, DNS, FTP, IPSec, POP3, SMTP, PPTP, Re-alplay, 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.

e) Port Triggering

Use the UE GUI > Security > Port Triggering feature to filter certain applications that use a trigger port to build a connection through a UE. When port triggering is enabled, the UE will forward the data to the external forward port.

f) ALG

Use the UE GUI > Security > ALG sub-menu to maintain any Application Layer Gateway (ALG) functions to augment the firewall when the local gateway (LGW) mode on the UE is set to NAT. ALG 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 manage the differ-ent types of application protocols by clicking on the check box next to any you wish to enable (Figure 4-56). Click on SAVE & APPLY.

Figure 4-56: ALG

90

g) 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 en-terprise-class devices. Check this setting if a subscriber is having difficulty using a particular device with their UE.

In the Security > UPNP menu, click on the check box next to Enable UPnP to allow it to function on this UE (Figure 4-57). Once enabled, any redirects of traffic will display in the Active UPnP Redirects section of the window. Click on SAVE & APPLY.

Figure 4-57: UPNP

h) Attack Protection

As a security precaution, you may decide to enable the Attack Protection feature found in the UE GUI under Security > 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 4-58), 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.

91

Figure 4-58: Attack Protection

4.11 Capacity Planning

To improve resource utilization and to avoid unnecessary costs, operators often prefer to deploy multiple eNBs on the same cell site structure. Doing so, however, can have a negative impact on the LTE service, for example, cause neighbor cell interference or PCI collision.

In most cases, the operator will install three eNBs on one site. For purposes of providing guidance for planning for this type of growth, we use the following guidance:

• Each eNB constitutes one cell, and each cell is called Cell1, Cell2, and Cell3.

• The separate central frequency for each eNB is called F1, F2, and F3.

• The separate bandwidth for each eNB is called B1, B2, and B3.

• The separate PCIs for each eNB are called P1, P2, and P3.

92

Baicells strongly recommends that the deployment of multiple eNBs sharing one physical site be in ac-cordance with the following constraints.

Frequency

The frequency that is set for each eNB cannot be the same or overlapping. There is no intersection be-tween FB1, FB2 and FB3. In other words, use the logic in the following formulas:

1) F1 ≠ F2 ≠ F3

2) Set FB1 = [F1-B1/2, F1+B1/2]

3) Set FB2 = [F2-B2/2, F2+B2/2]

4) Set FB3 = [F3-B3/2, F3+B3/2]

PCI

The PCI numbers for each eNB should be between 0 and 503 according to the 3GPP protocol. Furthermore, to avoid PCI interference, PCI1 mod 3 ≠ PCI2 mod 3 ≠ PCI3 mod 3. (Mod is a mathematical modulo operator.)

Cell ID

The Cell ID for each new eNB should be unique in the whole evolved packet core (EPC). Otherwise, the eNB will not launch normally.

SA and SSP

The Subframe Assignment (SA) and Special Subframe Pattern (SSP) should be the same between all of the eNBs sharing the same physical site. Otherwise, subframe collision will occur.

GPS Sync

For multiple eNBs sharing one site, enable GPS synchronization and make sure that the GPS Sync is suc-cessful. Otherwise, timing collision will occur.

Cellular Coverage

The antenna connected to each eNB sharing the same physical site should be aimed in different directions. The horizontal angle of each antenna should be a reasonable arrangement to avoid overlapping cellular coverage. UEs should not be deployed at the edge of the cellular coverage.

93

5. Troubleshooting In this section, the common types of issues that may occur in a Baicells network are classified by hardware component or logical entity. Each type of issue has been given a numerical identifier, for example, UE-1, UE-2, eNB-1, eNB-2, etc. If you do not find the issue you are experiencing, please check the Baicells FAQs, website or Facebook forum (see links in Appendix D), or contact the Baicells support team to open a ticket (go to Contact Us).

5.1 UE Issues

Following are some of the more common user equipment (UE) issues and the steps you should take to resolve them.

UE-1: No network connection

New Installations

1. For new installations: In the UE GUI > Overview > LTE Status, check the Universal Subscriber Iden-tification Module (USIM) card status (Figure 5-1). You should see “USIM Normal”. If the display says “SIM not ready”, check that the USIM card is installed firmly in the UE.

Figure 5-1: USIM Status

94

2. In the UE GUI > Status > Overview > LTE Status, check if the UE can detect a cell signal (Figure 5-2).

Figure 5-2: Cell Signal

3. If the UE cannot detect a cell signal, the UE may be out of range or on the edge of the RF cover-age area. Try adjusting the location of the UE unit near a window, at a higher level, or away from metal objects.

4. Check if the user is activated in the Baicells Business Operations Support System (BOSS) sub-scriber database (Figure 5-3). If you do not find the user, contact Baicells support to add the user in BOSS.

Figure 5-3: BOSS User Activation

95

5. If the PC cannot get an IP address from the UE, try rebooting the UE. It could be the Local Area Network (LAN) is not working.

6. Make sure the DNS server is working (Figure 5-4) by checking in the UE GUI > Overview > APN Status > DNS Server. Try to ping the DNS server using UE GUI > System > Diagnosis > Ping (Figure 5-5).

Figure 5-4: DNS Status

96

Figure 5-5: Ping DNS Server

If you see the ping can go through, that means the data path is OK. It may be other issues on the server you are visiting.

7. Check the eNB’s LGW mode setting (eNB GUI > Network > LGW). If the eNB is newly installed and LGW is not set to NAT mode, change the LGW to work in NAT mode. When you do this, you will need to reboot the eNB for the change to take effect. (Rebooting the eNB will disrupt ser-vice.) Confirm whether or not this was the UE connection issue.

8. If the LGW path was fine, the problem may be between the eNB and external router. Keep ping-ing from the UE, and check packets to/from the eNB on the router or switch that the eNB is con-necting to. Make sure the data to the assigned UE address can be routed to the eNB. Also, make sure the route table was not changed.

9. If the UE’s PCI lock feature is enabled, please make sure the frequency and PCI information are correct by checking UE GUI > LTE > Scan Method.

10. Make sure the eNB power settings are correct (eNB GUI > LTE > Advanced > Power Control). Some eNB reference signals may be set incorrectly, causing the UE to receive lower RSRP and making it very difficult to attach to the eNB.

11. Make sure the eNB status is reported as activated (eNB GUI > Basic Info > Cell Status).

12. If the UE still cannot detect the cell signal, you may need to adjust the angle, height, or downtilt of the eNB’s RF antenna.

13. If all of the steps above have checked out OK but the UE still fails to access the network, collect logs from the eNB and report the issue to Baicells support.

97

Existing UEs

For subscribers who are unable to access the network at all, you can check the below parameters.

1) eNB GUI: EARFCN for serving and adjacent eNBs

EARFCN EARFCN* is the frequency point of the serving or neighboring eNB’s frequency. Range is 0-65,535. The UE model must support a frequency range within the eNB’s fre-quency range. *EARFCN stands for Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number. Subscribers can check the frequency information on the unit itself or through the lo-cal UE GUI.

2) eNB GUI: Neighbor channels

Bands Channels in which the TD-S neighbor eNB operates. Options are band A, B, C, D, E, or F*. Check to see that the UE and eNB belong to the same band. *The letters stand for different TDS bands: 1. UTRA_TDD_128 BAND A: 9504 <= arfcn <= 9596 10054 <= arfcn <= 10121 BAND B: 9254 <= arfcn <= 9546 9654 <= arfcn <= 9946 BAND C: 9554 <= arfcn <= 9646 BAND D: 12854 <= arfcn <= 13096 BAND E: 11504 <= arfcn <= 11996 BAND F: 9404 <= arfcn <= 9596 2. UTRA_TDD_384 BAND A: 9512 <= arfcn <= 9588 10062 <= arfcn <= 10113 BAND B: 9262 <= arfcn <= 9538 9662 <= arfcn <= 9938 BAND C: 9562 <= arfcn <= 9638

98

BAND D: 12862 <= arfcn <= 13088 3. UTRA_TDD_768 BAND A: 9512 <= arfcn <= 9588 10062 <= arfcn <= 10113 BAND B: 9262 <= arfcn <= 9538

3) eNB GUI: Power control parameters

Power Ramping Recommend not changing! Step size of the Physical Random-Access Channel’s (PRACH’s) power index broadcast to the UEs via a Layer 1 channel. The value is initially used by the UEs during network connection for call setup. Options are 0, 2, 4, or 6.

Preamble Init Target Power

Recommend not changing! Initial power of the Physical Random-Access Channel for UEs to successfully connect to the network. (PRACH). Range is -90 to -120.

Po_nominal_pusch Recommend not changing! Physical Uplink Shared Channel (PUSCH) carries user data. It supports Quadrature Phase Shift Keying (QPSK) and 16 Quadrature Amplitude Modulation (QAM), with 64QAM being optional for some hardware models and software levels. Range is -126 to 24 dB.

Po_nominal_pucch Recommend not changing! 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.

Po_ue_pucch Initial UE transmit power when using Physical Uplink Control Channel (PUCCH). Range is -8 dB to 7 dB. The recommended setting is 7 dB.

Po_ue_pusch Initial UE transmit power when using Physical Uplink Shared Channel (PUSCH). Range is -8 dB to 7 dB. The recommended setting is 7 dB.

PA Recommend not changing! PA and PB are related to eNB transmit power. Physical Downlink Shared Channel (PDSCH) is the main data bearing channel. Power boosting the reference signal is allo-cated to UEs on a dynamic and opportunistic basis. The relative PDSCH power is deter-mined 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 Recommend not changing! See description for parameter “PA”. Range is 0-3.

99

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

4) eNB GUI: PRACH

The Random Access Parameters address the distance from the UE to the eNB. 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 5-6 and explained in Table 5-1. Click on Save to save the configuration.

Figure 5-6: Random Access Parameters

Table 5-1: Random Access Parameters


Preamble Format Recommend not changing! Packet preamble format (based on PRACH Index) to be used for this cell and com-municated to UEs. Options are 0 or 4.

Zero Correlation Zone Config Specifies the cyclic shift intervals to generate the PRACH sequence. Range is 0-15. Default is 10.

Refer to the BaiTip on this setting: https://commu-nity.na.baicells.com/t/baitip-of-the-day-december-14th-2016-sub-frames-and-special-subframes/163

PRACH Freq Offset Recommend not changing! Determines the location of the Physical Random-Access Channel (PRACH) pream-ble in the frequency domain. The range is: 10MHz – 1 to 43 20MHz – 2 to 92

https://community.na.baicells.com/t/recommened-advanced-settings-on-the-enb-to-optimise-channel-conditions/531

https://community.na.baicells.com/t/recommened-advanced-settings-on-the-enb-to-optimise-channel-conditions/531




100

5) UE GUI: Scan Method and PCI Lock settings:

The Scan Method determines which frequencies the UE’s routine scan of available frequencies will cover. Scanning is a process of tuning to a specific frequency and measuring the simplest signal quality [e.g, Re-ceived Signal Strength Indication (RSSI)]. As part of the cell selection and reselection process, the UE per-forms 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 5-7 and 5-8 to view the Scan Method configuration fields based on which mode you se-lect. The fields are explained in Table 5-2. Click on SAVE & APPLY to save the configuration.

Figure 5-7: Scan Method

Table 5-2: Scan Method


Settings

Scan Method Select one of the following: FullBand – The UE will routinely scan all channels in the band. The band is dependent on the model of UE being used. Click on Submit after selecting this option. PCI Lock – Allows you to select the specific E-UTRA Absolute Radio Frequency Channel Number (EARFCN) and Physical Cell Identifier (PCI). Click on Add List to enter the set-tings (Figure 5-8). After entering the information, click on Add and then Submit. You can add more than one PCI Lock list. The UE will scan the list for eNBs with the PCI and EARFCN combination. Band/Frequency Preferred – You can specify which band(s) the UE will scan. After se-lecting Band/Frequency Preferred, click on Add List. This will open an EARFCN settings field (Figure 5-9). Select the desired EARFCN from the drop-down list, and then click on Add to add the list. Click on Submit to save the changes.

101

Figure 5-8: PCI Lock

6) UE GUI: 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 5-9 and Table 5-3). Click on SAVE & APPLY to ac-tivate the data. The bottom of the screen lists any APNs that have been defined for this UE.

Figure 5-9: APN Management

102

Table 5-3: 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.

7) UE GUI – SIM Lock settings:

In older versions of the UE GUI, the UE’s Subscriber Identification Module (SIM) card could be locked to the operator’s network based on the 3-digit Mobile Country Code (MCC) and the 2- or 3-digit Mobile Net-work Code (MNC). The SIM Lock feature is not typically used because operators want to be able to use different SIMs in their equipment. If this feature is used, enter the settings as shown in Figure 5-10. The MCC + MNC = Public Land Mobile Network (PLMN). Click on Submit to save your data.

Figure 5-10: SIM Lock Settings

8) Scheduling Algorithm:

The Scheduling Algorithms are important for smooth RF operation and can impact key performance indi-cators 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 fa-vor 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 allocates resources to all UEs equally. Neither QoS nor memory is considered.

103

The uplink (UL) and downlink (DL) scheduling options in the eNB GUI under LTE > Advanced > Scheduling Algorithm are Max C/I or SCI, PFS, and RR. Refer to Figure 5-11. Click on Save to save the configuration.

Figure 5-11: Scheduling Algorithm Parameters

9) Sync Adjust:

The Sync Adjust parameters help the system to compensate for packet delay in the uplink and downlink. Do not modify these fields. Refer to Figure 5-12 and Table 5-4 concerning these settings. If you have us-ers who cannot access the network, check to ensure these settings remain at the default values shown in the figure.

Figure 5-12: Sync Adjust Parameters

Table 5-4: 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.

10) Link Activation State Detector:

The Link Activation State Detector is used to enable or disable a link watchdog. If you select Enable for this feature in the eNB GUI under LTE > Advanced > Link Activation State Detector, a watchdog action will check the UE periodically to see if it is connected or disconnected from the EPC, LAN, or both. Refer to Figure 5-13 and Table 5-5. Click on Save to save the configuration.

Figure 5-13: Link Activation State Detector Parameters

104

Table 5-5: 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

UE-2: Dropped connections

If a subscriber is experiencing UE drop issues, check the following.

eNB Reboot

An eNB reboot will disrupt UE sessions in progress. Normally, after the eNB is rebooted and the cell acti-vated, the UE can resume connection to it.

S1 Link Fail

Any S1 link issue will cause UE drops. Unfortunately, some UEs will not reconnect in the S1 flash memory (S1 goes down and comes up very quickly). In this situation, the subscriber will need to manually power cycle (reboot) the UE to make it reconnect.

Radio Link Failure

Inevitably, the eNB will sometimes detect an uplink radio link failure and will release the UE connection. The UE will then reconnect back to recover service.

Conversely, the UE will monitor its DL status and may detect a radio link failure, in which case it will release and then re-establish connection to recover service.

If this issue happens frequently on the same UE, you may need to check the RF metrics for the UE. Make sure the UE is receiving a strong enough RF signal to get sustained service. We recommend both UE an-tennas receive an RSRP better than -105 dbm. Also check that the SINR is better than 10 db. If the RSRP is good but the SINR is lower, then there may be DL interference from other eNBs and the UE is in the cross RF coverage area.

If the UE is mounted outside or at the edge of the eNB antenna propagation field, try moving the UE within antenna range. If the issue occurs frequently on multiple UEs in different locations but under the same eNB, then the eNB is likely experiencing interference from other eNBs or other sources. Try changing the eNB to a different frequency setting.

CloudCore Exception

Any problem with key network nodes such as the IPSec gateway or the evolved packet core (EPC) can lead to all UEs dropping off the connection. Usually the UEs will come back by themselves. If such an event occurs in the Baicells CloudCore, the support team will announce the incident and an estimated time for resolution.

105

UE-3: Not Found in OMC

1. Add the UE in OMC:

a. Log in to the OMC.

b. Go to CPE > Register.

c. Click the plus (+) symbol to add the device or a device group.

d. Enter the CPE MAC address.

2. Check under UE GUI > Overview that the UE is active and able to reach the internet (Figure 5-14).

Figure 5-14: Status

3. Check to see if the eNB’s management server (example in Figure 5-15) and TR-069 (example in Figure 5-16) settings are correct.

Note: An eNB operating in HaloB mode uses a TR-069 connection to the cloud to download sub-scriber 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.

106

Figure 5-15: eNB GUI > BTS Setting > Management Server

Figure 5-16: UE GUI > System > TR-069

4. Check the DNS settings in the UE GUI > Network > WAN Settings sub-menu (Figure 5-17).

107

Figure 5-17: DNS Settings

UE-4: Passing traffic but OMC status shows disconnected

1. Note the UE’s MAC address, and then delete the UE from the OMC.

2. Check the UE software code level, and upgrade it if needed.

3. Reboot the UE if no upgrade was required.

4. Add the UE back in to the OMC.

UE-5: Weak RF signal

1. From the UE Web GUI > Status > Overview window, monitor both the RSRP1 and RSRP2 values in real-time. If the values are greater than -110 dBm, it indicates that the RF signal is detectable within the service area of the eNB but may not be strong enough for a good connection. If the values are greater than -95 dBm, it indicates the RF signal is strong enough for a good connection. Baicells recommends that the UE’s RSRP values be greater than -110 dBM. Otherwise, the UE ser-vice will likely be poor or completely offline.

NOTE: If the signal is at -115 dBm or worse, Baicells support will not be able to help re-motely. Get the signal up so that a support technician can access the UE.

2. Following is a list of potential causes of RF interference you may need to check:

a) In the RF path from the eNB to the RF antenna, there may be water in the cable, bad lightning protection, bad cable termination, or simply a bad cable.

108

b) One radiator in the RF antenna is defective or disconnected internally. You may need to replace the antenna with another antenna to test it.

c) Bad UE hardware – One antenna radiator is defective or disconnected internally, or one trans-mitter is bad. Try another UE device.

d) One RF chain may be experiencing interference. Try changing to a different frequency.

e) The UE may not be mounted facing directly at the eNB antenna, or the eNB antenna downtilt may need to be adjusted. Check the antenna downtilt and vertical beamwidth in relation to the UE location.

f) The UE may be located outside of or on the edge of the eNB antenna propagation field. If possible, try moving the UE inside the propagation field.

g) Bad eNB – It could be that one RF port is disconnected from the transmitter internally, or simply a bad transmitter. You may need to replace the eNB.

UE-6: Router mode instability

In the UE GUI, go to Network > WAN Settings to check the Network Mode setting (Figure 5-18). Make sure the network mode selection matches your network setup. The UE may operate in NAT (default) or bridge mode.

Note: Older version UEs supported Router mode, but that mode is not recommended and was removed as of BaiCPE_V100R001C01B005SPC009.

Figure 5-18: Network Mode

109

NAT Mode

In NAT mode, the UE will change the private IP of the user device (computer or other smart smart device) to the UE WAN IP. User devices connect to the UE through its LAN interface. If you change the mode to NAT, reboot the UE for the change to take effect.

Router Mode

No longer recommended or an option in current GUI – For older version UEs set up in Router mode, the UE will forward all packets in Layer3 by using IP addresses. We do not recommend selecting router mode if the UE is experiencing stability issues.

Bridge Mode

In Bridge mode, the UE will pass the IP address to the first device connected to the LAN that does a DHCP request. Note that the IP will still be assigned by the cloud evolved packet core (EPC). In bridge mode, you can still access the UE via LAN if you statically configure the computer to be on the LAN IP subnet.

The Atom UE supports bridge mode version MT-23425-1.2.3-R6-Standard (Outdoor CPE) or later. If you change the network mode setting to bridge mode, the UE will reboot automatically. Once it has com-pletely rebooted, on the user device connecting to the UE configure a static IP that is in the same subnet as the UE LAN IP. Then, in the UE GUI go to LTE > APN Management, and if the GUI (older versions) shows Manage Interface enabled, deselect the Manage Interface option (Figure 5-19). Remove the static IP in the user device, and it should then be able to get the IP allocated by the EPC.


UE-7: High latency

A subscriber experiencing high latency issues may report the problem as slow internet service or poor quality voice or video sessions (e.g., stutter effect). Following are some areas to check to resolve such issues.

110

Multiple Simultaneous Users/Usage

Subscribers can connect more than one smart device to the UE for network service. If the UE is serving multiple users simultaneously, or if the bandwidth is largely consumed by one application over others (e.g., downloading a large file while also web browsing), one or more of the users may experience high latency.

Currently, there is no QoS capability to separate data traffic to different bearers. The users will have to manage sharing the UE.

Dropped Connections

High latency is an expected result during periods when a UE is dropping connection and trying to reconnect to the network.

UE-8: Low Speed

Slow internet issues can be the result of traffic congestion. All connected UEs share the serving eNB’s resources, and there may be contention for bandwidth to accommodate the number of users online and the different usage requirements at any given time. In the eNB GUI you can check the UE/CPE status to see if congestion may be the cause of low speed complaints.

If congestion is not the obvious problem, you will need to explore other data path issues. Continuing to examine the wireless connection and considering the possibility of backhaul link issues, you may need to run a speed test on the eNB. To do so, you will need an FTP server/Iperf server at the cell site on the same switch the eNB is using. In this case, we will refer to the cell site switch as the local switch.

You will also need an FTP server/Ipserf server behind the ISP switch. We will refer to this as the core switch. Refer to the simple LTE topology in Figure 5-20.

Run Local Test

Exclude the ISP link, and run the Iperf test using a client PC off of the local server; for example, use Iperf3 for the test:

Iperf3 TCP Test w/ 8 Parallel Connections - Download

Server: iperf3 -s

Client: iperf3 -c x.x.x.x -P8 -t15 -O5 -R

Iperf3 TCP Test w/ 8 Parallel Connections - Upload

Server: iperf3 -s

Client: iperf3 -c x.x.x.x -P8 -t15 -O5

If you are satisfied with the test result, you may need to check if it is an ISP link issue.

111

Figure 5-20: Simple LTE Topology

Test ISP Link

Run the same Iperf test, but this time from the server connected to the ISP switch. If you get the expected results, then you can say the bottleneck is an external link; if not, the bottleneck is in the ISP link.

Consider that multiple devices share the same ISP link. These other devices may take large amounts of bandwidth, causing the UEs connected to the eNB to suffer low speeds. Check the ISP link bandwidth in this case.

Assuming the ISP and external links are clear, check the following:

1. Make sure the test client PC is the only user of the UE.

2. Check the UE’s RF metrics for sufficient signal strength and quality.

If you still have not resolved the low speed issue, save the eNB logs and report the problem to Baicells support.

UE-9: Condensation (outdoor units)

Earlier deployments of outdoor UEs had some issues with condensation due to temperature fluctuation, missing or damaged O-rings, and over-torqued screws. This could cause overheating of the Ethernet ports and other problems.

To help prevent downtime and RMAs, we recommmend drilling weep holes in these older outdoor units (Figure 5-21). Also make sure you tighten or cover the SIM card plate, as water could possibly enter there as well.

112

Figure 5-21: Weep Holes

5.2 eNB Issues

Following are some of the more common eNodeB (eNB) issues and the steps you should take to resolve them.

eNB-1: Inactive status

1. Check the backhaul link (Management Server address) with the ISP provider (see Figure 5-22). Make sure the eNB can reach the cloud.

Figure 5-22: Management Server

2. Check the IPSec setting (eNG GUI example in Figure 5-23). Make sure the IPSec configuration is correct. Then, reboot the eNB to recover the IPSec.

NOTE 1: Always collect logs before rebooting the eNB. The logs may be needed for troubleshooting any issues.

NOTE 2: There is a possibility that some Network Address Translation (NAT) devices will discard some of the data for the specific port. If the reboot does not work, contact the Baicells support team.

113

Figure 5-23: IPSec

3. Check if the OMC parameters MME IP, PLMN, and TAC are configured correctly per your network design plan (eNB GUI example in Figure 5-24).

114

Figure 5-24: MME IP, PLMN, TAC

4. Collect eNB logs, reboot the eNB to recover, and report to Baicells support.

The chart in Figure 5-25 summarizes the eNB inactive actions.

Figure 5-25: eNB Inactive

115

eNB-2: GPS unsynchronized

1. After an initial eNB installation, if you see an unsync alarm check the following.

a) Make sure the GPS antenna was mounted correctly on the eNB, per the Installation Guide.

b) Make sure the GPS sync switch is enabled in the eNB GUI as shown in Figure 5-26.

Figure 5-26: GPS Sync

c) Check whether the GPS connector is loose.

d) Check whether the GPS antenna works by connecting it to another eNB. Reboot the eNB to check again if the above items are normal.

2. Sometimes the GPS status suddenly appears unsynchronized on the OMC page while the eNB is in normal operation mode. When this happens, the probable cause is one of the following:

c) The GPS has been damaged by a natural factor, such as severe weather.

d) The GPS antenna has been unplugged manually.

e) The GPS connector is loose.

After checking any of the above items, reboot the eNB.

NOTE: Before rebooting the eNB, collect the eNB logs in case the data is needed for troubleshooting.

eNB-3: Fails to Start

The recovery steps for an eNB failing to start are divided based on whether you are dealing with a new installation or existing eNB. Go to the section that applies to your situation.

116

New Installation

Check the status of the eNB’s LED indicators, per the Installation Guide specific to each model. If you do not have the installation guide, please refer to the Baicells website in the Contact Us section.

For example, most eNB models have four LEDs to indicate operational status (Table 5-6).

Table 5-6: Example LEDs

• If the PWR LED is off, check the following:

Power polarities are correct to the eNB power input

Power (both voltage and current) meets the eNB power input requirement. If, for example, the requirement is 65W (DC 48V @1.35A), the input voltage can be in the range of DC42V to DC58V.

If the power requirements check out satisfactorily, it may be a faulty eNB. Open a ticket with Baicells support to request a Return Materials Authorization (RMA).

• If the PWR LED is on, but the RUN LED is off: It is likely there is no power input to the imbedded board. Open a ticket with Baicells support to request an RMA.

• If the ACT LED is off, and the ALM, PWR, and RUN LEDs are on:

Check the IP connectivity with CloudCore. With new installations, when the cell status is inac-tive (Figure 5-27), it could be the WAN has no IP connection. Log in to the local eNB GUI, and check if the WAN port has been configured for static_ip or check if the WAN port obtained an IP address from the DHCP server. Make sure the IP address is accessible via the internet.

117

Figure 5-27: eNB Status

Find the IPSec link setting (Figure 5-28) to see if it is wrong or missing; if so, contact Baicells support.

Figure 5-28: IPSec

• Also check the Quick Setting page to make sure the MME IP/PLMN/TAC are configured cor-rectly. Refer to Figure 5-29. If you make any changes, click on Save.

118

Figure 5-29 Quick Settings

Existing eNB

For an existing eNB that cannot activate the cell, review all of the settings mentioned under New Installa-tions to ensure the configurations have not been changed accidentally. If everything looks correct, please capture logs and then reboot the eNB to see if it can resume service. If not, open a ticket with Baicells support, attaching the log files.

eNB-4: Not displayed in OMC

Normally, you can view the eNB status and other information in OMC, as shown in Figure 5-30.

Figure 5-30: OMC > eNB > Monitor

119

If the eNB is not seen in OMC, from the local eNB GUI check the following.

• eNB status – If the eNB can access the internet and is otherwise operating normally (Figure 5-31), check with your ISP/network administrator. When the OMC cannot “see” the eNB, but locally it is operating fine, it is normally due to an eNB configuration error.

Figure 5-31: eNB Status

• Management Server setting – For the Baicells CloudCore, the address should be baiomc.cloudapp.net:48080/smallcell/AcsService (Figure 5-32).


120

• DNS settings:

Static IP - If the WAN is configured for static_ip, ensure the DNS address is set correctly, e.g., 8.8.8.8 (Figure 5-33).

Figure 5-33: DNS

DHCP - If the WAN is configured as DHCP, the DHCP likely has an invalid DNS address. For this, change the Management Server to the CloudCore OMC’s IP address (Figure 5-34).


If you are still having problems seeing the eNB in OMC, contact Baicells support.

121

eNB-5: S1 Link Flap or Drop

Subscriber experience is quickly degraded when there is a problem with the S1 link to the core network flapping or dropping. You may see the cell status reported as inactive or jumping between active and in-active. You might see the MME status displayed as disconnected or hopping between connected and dis-connected. Following are possible causes to check.

• eNB spontaneously reboots – If you notice the local eNB GUI page reload or exit and then require authentication, or from the OMC you see the IP connection displays a red “x” then you know the eNB rebooted itself. Please report this issue to Baicells support.

• eNB ID conflict – If the eNB keeps a connection to the internet but the S1 status changes every 30 seconds or so, it may be the eNB’s ID is in conflict with another eNB. Each eNB must have a unique cell ID (Figure 5-35). Normally, the first time an eNB is powered up (in factory), the generation algorithm creates a unique ID. We do not recommend modifying the ID. Note, however, that some eNBs manufactured before September 2016 did not include the genera-tion algorithm and required you to set the eNB ID manually.

Figure 5-35: Cell ID

• Network surge protector malfunctioned - For eNBs manufactured before September 2016, a network surge protector was equipped inside. Sometimes the surge protector can malfunc-tion, which reduces the electric signal through it and causes the eNB to miss some data pack-ets. If you can distinguish the eNB by serial number, we suggest removing the surge protector.

122

• Network unstable – If the backhaul network (internet) is unstable, there is not much you can do on your end to improve eNB processing. Once it is available, using a local evolved packet core (EPC) or HaloB solution would bypass the CloudCore and provide a resolution.

5.3 Backhaul, RF, and Other Issues

Other problems that may arise have been captured here.

Other-1: Speed and latency issues

1. Check if there is any flow control enabled on the switch connected to the eNB. If there is, disable it.

2. Check the UE RF parameters, such as RSRP, MCS, CINR, and SINR. See if they are optimized (refer-ence Section 4. Maintenance).

3. Check to see if the backhaul is the problem. Run iperf speed tests between the eNB and the client’s PC. Sometimes a Wi-Fi backhaul will drop the S1 signal.

4. Run the iperf tests, per the instructions found for issue number UE-8, low speed issues.

Other-2: eNB and CPE/UE routing issues

Refer, also, to issue number UE-6, Router mode instability.

A UE may be unreachable remotely due to configuration errors related to the local gateway (LGW) mode settings on both the eNB and UE.

1. There are 3 configuration options for LGW mode on the eNB and UE: Network Address Translation (NAT), Router, and Bridge mode. Note that Router mode is no longer recommended on the UE.

a) NAT mode: To access the UE when the eNB is in NAT mode, use URL: https://[IP Address]:[Port], where:

• [IP Address] is the eNB’s IP address.

• [Port] is a number with the format 5XXXX, where XXXX is the last 4 digits of the UE’s IMSI.


123

Figure 5-36: NAT Mode

b) Router mode: Use the UE’s local IP address to access the Web GUI, e.g., https://10.10.0.10.

c) Bridge mode (Figure 5-37): The eNB will create a virtual interface for every UE that attaches. Each virtual interface will then send a DHCP request and create a 1:1 mapping between the UE’s IP (from Cloud EPC) and the LGW’s IP. In Layer 2 mode, the MAC address that the UE uses is generated from the IMSI number. To calculate the UE MAC address, convert the last 12 digits of the IMSI number to hex, and then prefix it with 8A. For example: If the IMSI is 311980000002918, you would take the last 12 digits (980000002918) and convert them to hex, which would be E42C8D5366. Therefore, the MAC address would be 81:E4:2C:8D:53:66. Once you know the MAC address, you can provision your network accordingly. Use the UE’s local IP address to access the Web GUI, e.g., https://192.168.254.1.

https://10.10.0.10/

https://192.168.254.1/

124


Other-3: Interference Issues

1. If a subscriber is having trouble connecting to the network or experiencing slow or intermittent communications, it may be there is an RF interference issue either between that particular UE and the eNB or for multiple UEs connected to the same eNB. The first data points to check are CINR, MCS, and RSRP. If the CINR and MCS values are poor while the RSRP is good, that is an indication of interference. Also, if the CINR value is fluctuating, you may have an interference problem.

2. To confirm, check the CINR, MCS, and SINR values for several UEs connected to the same eNB.

3. Check the Block Error Ratio (BLER)* percentage on the eNB GUI under BTS Info > Basic Info. The UL and DL BLER represent a ratio of the number of erroneous blocks received to the total number of blocks of data sent. Anything above 10% usually indicates noise/interference on the channel.

*NOTE: The BLER value became available as of UE software version BCE-ODU-1.0.3.

4. If you have a frequency scanner and know that you are not operating anywhere near the eNB on the same frequency, scan to see if you detect signals from other devices outside your network in the eNB’s operating frequency. If you do, try changing the eNB to a different frequency within the same band.

5. Check the frequency configuration of nearby eNBs. Make sure there is no PCI conflict.

125

Appendix A: LTE References

Network Identifiers:

• Public Land Mobile Network Identity (PLMN-ID) is the identification of the network itself. PLMN is a combination of the Mobile Country Code (MCC) and Mobile Network Code (MNC).

• Tracking Area Code (TAC) identifies a tracking area within a particular network.

• E-UTRAN Cell Identity (ECI) identifies a cell within a particular network.

• Physical Cell Identity (PCI) distinguishes a cell from its immediate neighbors.

UE Identifiers:

• International Mobile Subscriber Identity (IMSI) is a unique ID that globally identifies a sub-scriber. The IMSI is programmed on the Universal SIM card (USIM).

• International Mobile Equipment Identity (IMEI) is a unique ID that globally identifies 3GPP UE hardware.

Signal Measurements:

• Received Signal Strength Indicator (RSSI) measures the total received wide-band power.

• Reference Signal Received Power (RSRP) is the average power of the LTE reference signals over the entire bandwidth. [RANGE]: -44 ~ -140dBm

RSRP does a better job of measuring signal power from a specific sector while potentially exclud-ing noise from other sectors.

126

• Reference Signal Received Quality (RSRQ) indicates the quality of the received reference signal. [RANGE]: -3 ~ -19.5dB

RSRQ Formula:

RSRQ = N x RSRP / RSSI

N = Number of PRBs

Basically, RSRQ depends on serving cell power and the number of Tx antennas.

RSSI vs RSRP (Figure A-1):

• RSSI measures the power of the entire resource block symbol containing the Reference Signal (RS).

• RSRP measures the power of a single resource element.

Figure A-1: RSSI vs RSRP

• Signal-to-Interference plus Noise Ratio (SINR) is the ratio of the average received demodulated signal power to the sum of the average co-channel interference power and the noise power from other sources.

• Carrier-to-Interference plus Noise Ratio (CINR) is the ratio between the power of the RF carrier bearing the wanted signal and the total power of interfering signals and noises.

127

PCI (Figure A-2):

Primary Synchronization Signal (PSS)

3 different sequences called Physical-Layer ID (0~2)

Secondary Synchronization Signal (SSS)

168 different sequences called Physical-Layer Cell ID Group (0~167)

3x168 = 504 available Physical-Layer Cell Identities. Once a UE knows the PCI, it also knows the location of the cell reference signals.

Figure A-2: PCI

Category 4 UE – 2rx 1tx

128

Appendix B: Antenna Basics –

Coverage vs Interference Do’s and Don’ts

The following figures present various antenna configurations, and the results you can expect from each speak for themselves.

Figure B-1: Three 120-Degree Sectors (DO NOT)

129

Figure B-2: Three 90-Degree Sectors (Acceptable)

130

Figure B-3: Four 90-Degree Sectors (DO NOT)

131

Figure B-4: Four 65-Degree Sectors (DO!)

132

Figure B-5: Six 45-Degree Sectors (BEST USE!)

Follow are some of the more critical antenna factors:

• Desired coverage area (radius from tower)

• Antenna mounting height above average terrain

• Vertical beamwidth

• Electrical downtilt

Use a downtilt calculator (example shown in Figure B-6):

• Example at http://www.commscope.com/calculators/qdowntilt.aspx

• Most antennas fall in a range of 6-8 degrees vertical beamwidth

• Use 7 as an average starting point

http://www.commscope.com/calculators/qdowntilt.aspx

133

Figure B-6: Downtilt Calculator Example

Mechanical vs Electrical Downtilt (Figure B-7):

• Need to know:

• With mechanical tilt, the coverage area is reduced in a central direction, but the coverage area in side directions is increased.

• With electrical tilt, the coverage area suffers a uniform reduction in the direction of the antenna azimuth; that is, the gain is reduced uniformly.

• Tilt is used to reduce and control interference with other sites.

• Tilt is used to concentrate the RF pattern in a desired coverage area.

• Mechanical downtilt may worsen CINR levels from neighboring sectors.

134

Figure B-7: Mechanical vs Electrical Downtilt

• The Baicells team has tested the following antennas with the Baicells equipment:

• Alpha Antennas https://alphaantennas.com/

• KP Performance Antennas https://www.kpperformance.ca

• MTI Antennas http://www.mtiwe.com/

• Fixed vs adjustable electrical downtilt

• Front-to-Back (F/B) Ratio – The F/B ratio denotes the sensitivity of an antenna to radio waves in the region of 180 degrees plus or minus 40 degrees from the main beam direc-tion in the area of space behind the antenna.

• 30-35 dB F/B Ratio is considered good; less than that is not.

• The higher the number, the better.

• Polarization (Figure B-8):

• Dual slant

• Horizontal/Vertical

• Benefits of dual slant:

• Improved noise immunity

• Improved SNR

https://alphaantennas.com/

https://www.kpperformance.ca/

http://www.mtiwe.com/

135

• Improve coverage in congested environments

• Vertical polarization generally maintains stronger receive signal than horizontal polarization (inequality)

• Slanting both polarities 45 degrees improves the receive sensitivity equality.

Figure B-8: Polarization

Baicells recommends that you find a few antennas that may fit your deployment, and then:

• Run downtilt calculations again with correct vertical beamwidth specifications.

• Choose as much electrical downtilt as possible to meet your desired downtilt; reduced mechanical downtilt reduces pattern skew.

• Total downtilt = electrical downtilt + mechanical downtilt

• Install the antenna with accurate mechanical downtilt, per calculations.

• Test, and adjust if needed.

Regarding the selection of RF cables:

• Passive InterModulation (PIM) - PIM is defined as the unwanted signal or signals generated by the non-linear mixing of 2 or more frequencies

• High PIM means poor reception and limited bandwidth to the end user, which in turn means lost customers.

• Low PIM means strong signals with more bandwidth for more users, which means happy custom-ers and higher revenues.

• Extensive testing by LTE providers discovered that legacy LMR braided cables may test perfectly in a Return Loss or VSWR test, but generally possess only average PIM perfor-mance.

136

• PIM lowers the reliability, capacity, and data rate of LTE systems. It does this by limiting the receive sensitivity.

• PIM shows up as a set of unwanted signals, created by loose or corroded connectors, nearby rust, medium or high PIM braided cable products, and other variables. Other names for PIM include the diode effect and the rusty bolt effect. Other causes of PIM:

• Over-tightening, insufficient contact pressure, distorted contact surfaces, foreign material in the mating surfaces, or corrosion

• Poorly manufactured antennas, nearby corrosion, lightning arrestors

• Connectors made for LTE usage are non-ferrous and plated with coatings such as silver, white bronze, and gold.

• Listed below are some data sheet links for low PIM cables from various manufacturers:

• RFS Cellflex49

• Superior Essex HSFC Series23

• Commscope Heliax Sureflex27

• Times Microwave LMR-SW49

http://www.rfsworld.com/WebSearchECat/datasheets/pdf/cache/LCF12-50JFN.pdf

http://ce.superioressex.com/uploadedFiles/Docs/PDF/Catalogs/Communications/HFSC.pdf

http://www.commscope.com/Docs/SureFlex_BR-104351.pdf




https://www.timesmicrowave.com/downloads/products/lmr-sw.pdf

137

Appendix C: RF / Network Planning Considerations

C.1 Coverage

Field measurements are the most accurate in predicting radio coverage in a certain area. Each area may be different. For example, the coverage inside buildings can add about 16 to 20 dB of extra signal loss. Coverage inside vehicles can increase the loss by an extra 3 to 6 dB. Obstacles such as trees present the same kinds of challenges.

Following is a list of recommended propagation modeling software applications you can use to predict coverage. These apps and services use a variety of digital terrain models (DTM) and digital surface models (DSM) to provide accurate global coverage.

• EDX Wireless

• Forsk Atoll

• TowerCoverage.com

• CloudRF online radio planning

C.2 PCI Planning

In terms of PCI planning, consider the following:

• WO synchronization signals are transmitted once every 5 ms (Figure C-1).

• Primary Synchronization Signal (PSS)

• Subframe #0 and #5

• Mapped on 72 subcarriers in the middle of the band

• OFDM symbol #6

• Secondary Synchronization Signal (SSS)

• Subframe #0 and #5

• Mapped on 72 subcarriers in the middle of the band

• OFDM symbol #5

138

Figure C-1: PCI Planning

Capacity planning (related to PCI planning):

• The challenge of macro and HetNet planning is ensuring capacity is provided where the demand is located.

• The cell spectral efficiency is critical if there is to be an effective increase in network capacity. In the presence of traffic hotspots, an adaptive modulation and coding scheme (MCS) means the difference between users sharing .5 Mbps and 100 Mbps. Providing data capacity is not like provid-ing voice “lines”.

• The location of traffic hotspots determines whether there will be a return on investment or not, and maximizes profit margins.

TDD sync signals:

• Two synchronization signals are transmitted once every 5 ms (Figures C-2 and C-3):

• Primary Synchronization Signal (PSS) ◦ Subframe #1 and #6 ◦ Mapped on 72 subcarriers in the middle of the band ◦ OFDM symbol #2

• Secondary Synchronization Signal (SSS) ◦ Subframe #0 and #5 ◦ Mapped on 72 subcarriers in the middle of the band

◦ OFDM symbol #13

139

Figure C-2: PSS and SSS (1 of 2)

Figure C-3: PSS and SSS (2 of 2)

140

PCI planning priorities:

1. The same PCIs should be avoided within the same site and as neighbors.

2. PCIs with conflicting k values should be avoided within the same site and as neighbors.

3. PCIs with conflicting m0 and m1 values should be avoided within the same site and as neighbors.

Reasons for not following these rules? Strictly: The rules will not work for an irregular pattern (refer to Figure C-3). It will cause numerous limitations on neighbors, and neighbor lists have to be shortened.

Figure C-4 provides an example formula from Excel to calculate PCI usage: =SUM(3*E2+D2)

Figure C-4: Example of PCI Usage Calculation

C.3 Power Levels and Other Challenges

When it comes to coverage, power levels and other factors must be considered:

• Different nodes and devices have different power ranges, from the smallest to the largest compo-nent.

• Increasing power can swamp the smaller components and render them inoperable; each must be planned carefully with new levels of accuracy.

• Due to the range of sizes, environment modeling for conditions such as clutter must be reconsid-ered, with accuracy as the main focus.

• Components may be deployed in significant numbers, resulting in an exponential growth in the planning complexity.

141

Below are some considerations and general guidelines to address these types of challenges:

1. Clutter Data Accuracy (recommendations)

a. Macro < 10M

b. Pico/SmallCell < 2.5M

c. Femto/Wi-Fi < 1M

d. Atto < 0.25M

2. Network Capacity

a. Provide capacity where demand is located.

b. Spectral efficiency is critical if there is to be an effective increase in network capacity. It can make the difference between users sharing 5 Mbps and 50 Mbps.

3. Location, Location, Location

a. Adaptive modulation works to achieve maximum link performance.

b. High SNR means more spectrum efficiency, which in turn maximizes ROI.

Other considerations around network capacity:

1. Network capacity is sensitive to the cell spectral efficiency.

2. An adaptive modulation and coding scheme means that user locations determine the capacity of the serving cell.

3. A commuting, dynamic population means that residential or business census falls short of the actual population distribution in modern cities.

4. Components are sensitive to the mobility of the demand. Fast-moving demand cannot be served by small cells such as picos.

5. Different components are suited to different environments. Femto and Wi-Fi are designed for in-door situations; macros and picos work effectively outdoors.

In terms of interference, consider:

1. The power of a distant macro can often be at a similar value to the power of a pico’s serving area.

2. The interference potential of a macro is increased considerably for a pico due to the greater pow-ers of the macro.

3. Complex interplays between the macro and picos or femtos should be modeled.

4. Modeling entire cities, it may be necessary to extend the signal predictions to much farther dis-tances in order to compute a site’s capacity.

142

C.4 Planning Summary

The science and art of RF planning encompasses a variety of factors:

• Use deployment-ready business case studies for cell planning.

• Use good clutter data as available, and design for capacity with coverage as the second most important factor. Remember that clutter data is not cheap, but neither is putting a site in the wrong location.

• Various techiques will be needed to understand the ROI on each site.

• Reduce power as much as possible to avoid interference between network components.

• Increase gain.

• Focus the antenna for your planned coverage area, ensure the downtilt is appropriate for your objectives, and stick to the plan.

143

Appendix D: FAQs The Baicells product data sheets, with technical specifications, may be found on the Baicells website: https://na.baicells.com/downloads/.

Go to https://baicells.zendesk.com/hc/en-us/sections/206214447-FAQs to find the most up-to-date Fre-quently Asked Questions (FAQs).

Other useful source of information about Baicells products and operator deployments may be found on the following sites:

• Baicells Community Forum: https://community.na.baicells.com/

• Baicells Operators Suport Group on Facebook: https://www.facebook.com/groups/baicellsopera-

torsupportgroup/

https://community.na.baicells.com/

