HaloB Solution

User Guide
CloudCore OMC 8.0.6
BaiBS_RTS_3.7.11
BaiBS_RTD_3.7.11
BaiBS_QRTB_2.9.14

August 2022

Version 1.16
About This Document
This document is intended for operators implementing the Baicells eNodeB (eNB) HaloB feature. An eNB
operating in HaloB mode provides “lite" core functions so it can continue serving subscribers even when
it has no connection to the Long-Term Evolution (LTE) Evolved Packet Core (EPC).
Included is a description of the HaloB architecture, benefits, activation process, and differences in eNB
configuration when in HaloB mode versus normal mode. Users of this document should already be familiar
with the eNB GUI and the Baicells CloudCore Operations Management Console (OMC), and Business
Operations and Support System (BOSS) applications.
The information in this document is based on the following Baicells software versions:
• eNB: BaiBS_RTS_3.7.11 (Nova227, Nova233, Nova243)
• eNB: BaiBS_RTD_3.7.11 (Nova246)
• eNB: BaiBS_QRTB_2.9.14 (Nova436Q, Nova430i, Nova430e, and Neutrino430)
• CloudCore OMC: Version 8.0.6
• CloudCore BOSS: Version 8.0.6
Terms used in this document or related to LTE are listed in alphabetical order and described in
Acronyms and Abbreviations, which can be found at Baicells.com > Resources > Documents.

New in This Release

The following updates are provided in this release:
• Added description of the HaloB network architecture.
• Updated for software version QRTB 2.9.14 to configure the eNB to HaloB mode (Centralized Mode
and Standalone Mode).
• Updated for software version RTD 3.7.11 features, improvements, and GUI changes.
• Added procedures to configure HaloB mode on CloudCore OMC version 8.0.6.

Copyright Notice
Baicells Technologies 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. The Baicells
logo is a proprietary trademark of Baicells Technologies. Other trademarks mentioned in this document
belong to their owners.

Disclaimer
All products, services, and features bought from Baicells Technologies are subject to the constraints of the
company's business contract and terms. All or part of the products, services, or features described in this
document might not be your specific Baicells network. Unless stated in the contract, Baicells Technologies
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.

Revision Record
Date Version Description SMEs/Contributors Author/Editor
08-Aug-2022 V1.16 • Updated for eNB releases Yunfeng Jiang, Angelin Selvaraj
QRTB 2.9.14, RTS 3.7.11, Sonny May, Jocelyn Watson
RTD 3.7.11, CloudCore Abel Lamas Kathy Clark
OMC 8.0.6
• Added procedures to
configure HaloB mode on
CloudCore OMC
23-Mar-2021 V1.15 Updated for eNB releases RTS Nitisha Potti, Jesse Kathy Clark
3.7.5, RTD 3.7.5, QRTB 2.5.4, Raasch
OMC 6.3.4, and BOSS 6.3.4
27-Oct-2020 V1.14 Updated for eNB releases RTS Nitisha Potti, Jesse Kathy Clark
3.6.6 and QRTB 2.4.2, OMC Raasch
6.2.8, BOSS 6.2.3
28-Feb-2020 V1.13 New logo & colors Chris Culver Sharon Redfoot
10-Jan-2020 V1.12 Corrected licensing info Rick Harnish, Nitisha Sharon Redfoot
17-Dec-2019 V1.11 Updated for eNB releases RTS Potti, Jesse Raasch
3.4.8 and QRTB 2.0.5, OMC
5.2.7, BOSS 5.2.5
27-Aug-2019 V1.10 Added missing OMC step. Nitisha Potti, Jesse Sharon Redfoot
26-Aug-2019 V1.9 Updated for OMC 5.0.7, BOSS Raasch, Sonny May
21-Aug-2019 V1.8 4.5.2, eNB RTS 3.3.x & QRTBA
1.0.x

Resources
• Documentation - Baicells product datasheets, technical manuals, and a list of acronyms and
abbreviations can be found at Baicells.com > Resources > Documents.

• Support - Open a support ticket, process an RMA, and the Support Forum is at
Baicells.com > Support.

Contact Us
Baicells Technologies
5700 Tennyson Pkwy, #300, Plano, TX 75024, USA
Phone: +1-888-502-5585
Email: [email protected] for North America or [email protected] for all other regions
Website: baicells.com

iii
Table of Contents
1. Overview....................................................................................................................................1
1.1 Introduction ...................................................................................................................... 1
1.2 HaloB Network Architecture ............................................................................................. 2
1.3 HaloB Solution ................................................................................................................... 2
1.4 Benefits ............................................................................................................................. 3
2. Configuration .............................................................................................................................4
2.1 Configure HaloB Mode on eNBs Running QRTB Software ................................................. 4
2.2 Configure HaloB Mode on eNBs Running RTS/RTD Software ............................................ 7
2.3 Configure HaloB Mode on CloudCore OMC..................................................................... 10

List of Figures
Figure 1-1: LTE Network Architecture ......................................................................................................... 1
Figure 1-2: HaloB Logical Architecture ........................................................................................................ 2
Figure 1-3: HaloB Solution .......................................................................................................................... 3
Figure 2-1: HaloB License (QRTB) ................................................................................................................ 5
Figure 2-2: HaloB Mode – Centralized Mode (QRTB) .................................................................................. 5
Figure 2-3: HaloB Mode – Standalone Mode (QRTB) .................................................................................. 6
Figure 2-4: Verify Status (QRTB) .................................................................................................................. 7
Figure 2-5: Import HaloB License (RTS/RTD) ............................................................................................... 8
Figure 2-6: HaloB Mode – Centralized Mode (RTS/RTD) ............................................................................. 8
Figure 2-7: HaloB Mode – Single Mode (RTS/RTD)...................................................................................... 9
Figure 2-8: HaloB License (CloudCore OMC) ............................................................................................. 10
Figure 2-9: Verify HaloB License ................................................................................................................ 11
Figure 2-10: HaloB Enable (CloudCore OMC) ............................................................................................ 11
Figure 2-11: Configure HaloB (Quick Setting Tab) ..................................................................................... 12
Figure 2-12: Configure HaloB (BTS Tab)..................................................................................................... 12
Figure 2-13: Configure HaloB (Special Tab) ............................................................................................... 13
Figure 2-14: MML Command LST HALOB .................................................................................................. 14
Figure 2-15: MML Command MOD HALOB ............................................................................................... 14
Figure 2-16: MML Command CLEAR IMSI ................................................................................................. 15
Figure 2-17: MML Command LST DSCP ..................................................................................................... 15

iv
1. Overview

1.1 Introduction
The Baicells HaloB feature was developed and patented by Baicells to address the needs of wireless
operators who:
• Are concerned about adding core network functions when full-blown end-to-end Long-Term
Evolution (LTE) networking may not be necessary for their customer locations; and
• Want an eNodeB (eNB) to continue providing network service even if the link to the core
network is not unavailable, e.g., due to an outage or S1 link failure.
Operators in these situations need a way to offer or continue service without being dependent on the
availability of the LTE Evolved Packet Core (EPC) network functions to do so (Figure 1-1).
Figure 1-1: LTE Network Architecture

An eNB set to operate in HaloB mode will have onboard “lite EPC" capabilities by transitioning the
Mobility Management Entity (MME) function to the eNB. The eNB handles User Equipment (UE)
attachment and signaling (including the control plane), even though there are no S1 tunnels from the
eNB to the EPC. A HaloB eNB can serve subscribers even when it has no connection to the EPC
network.

1 |P a g e
1.2 HaloB Network Architecture
Compared to the traditional LTE network architecture, the lite EPC solution reduces the cost of network
deployment and construction time significantly. In addition, the HaloB network (Figure 1-2) enables
eNBs to work in a plug-and-play fashion and build the network anywhere.
To enhance the Quality of Experience (QoE) for the customers, Baicells has developed HaloB solutions
based on embedded EPC, which removes the dependence on the control plane. Therefore, the control
plane is in the embedded EPC, and the user plane is present locally. The eNB with embedded EPC is
called HaloB eNB. The HaloB eNB ensures whether the devices are active and allows disconnected
devices to activate and establish a connection. This capability can be significant during emergencies like
severe weather, EPC outages, and other service disruptions.
Figure 1-2: HaloB Logical Architecture

1.3 HaloB Solution

Each HaloB-enabled eNB controls its subscribers independently, eliminating wireless service
disruptions that otherwise would be caused by S1 (transport) failures, wireless Point-to-Point (PTP)
backhaul failures, fiber outages, or routing mistakes.
The only other Baicells components involved in HaloB operation are the Baicells Operations
Management Console (OMC) for remote network management and the Business and Operations
Support System (BOSS), which stores the operator's Subscriber Identity Module (SIM) card, subscriber,
and service plan information (Figure 1-3).

2 |P a g e
 The HaloB eNB retains the subscriber
Figure 1-3: HaloB Solution
information of UEs that are attached or have
been attached in the past. When a new
subscriber requests an attachment, the eNB
uses the TR-069 connection to contact BOSS
and download the subscriber's International
Mobile Subscriber Identity (IMSI) and service
plan, a method referred to as centralized
mode.
A subscriber can attach to multiple HaloB
eNBs, and each eNB will store the IMSI and
service plan for future attachments.

Operators who have integrated BOSS and third-party billing software using Application Programming
Interfaces (APIs) will see no change due to HaloB operation. When a UE attempts to attach to a HaloB
eNB, the HaloB eNB operating in centralized mode contacts the BOSS to verify that the IMSI is valid and
active, and collects the service plan information. All information is downloaded to the HaloB eNB’s
memory. Once stored in the eNB memory, the UE will remain attached indefinitely. If an eNB or UE
reboot occurs, the UE attachment request is checked against the eNB's local HaloB memory for the UE
to reattach.

1.4 Benefits
With HaloB:
• Network access is processed by each HaloB-enabled eNB, which means the UEs will always be
online (barring any equipment failure, of course).
• Operators can enter the world of fixed wireless with a lower initial investment.
− The eNB and the core network functions are decoupled.
− The simplified structure means there is no need for professional network design.
− Shorter Time to Market (TTM) and faster Return on Investment (ROI).
• Operators are not required to buy or change any equipment. HaloB is embedded in the eNB
software and can be enabled through a per-eNB software license.
• An operator can switch an eNB back and forth between standard operating mode and HaloB
mode by simply enabling/disabling the feature and rebooting the eNB.
While a great deal of intelligence is operating in the background of the HaloB feature, Baicells designed
the feature to be easy to configure, manage, and run efficiently. In the control plane, there is no
significant impact on memory or processing; the eNB performs at the same level it usually would. HaloB
is an example of the industry movement to make LTE networks more accessible and less complicated,
and to move more of the processing closer to users. In essence, a HaloB eNB becomes a local EPC right
on the tower.

3 |P a g e
2. Configuration
To enable the HaloB feature, verify that the eNB is running the latest software version for your eNB
model. The latest software is available on the Baicells website under Support > Firmware.
NOTE: Although the HaloB feature is built into the software for most Baicells eNBs, you will
need to import the HaloB license to activate the feature. The license import instructions are
provided in the following procedures.

The eNB can function in Normal mode or HaloB mode. In Normal mode, the eNB works as a standard
eNB connecting to the traditional EPC. In HaloB mode, the eNB's embedded EPC provides "lite" core
functions so the eNB can continue serving subscribers even when the eNB has no connection to the
LTE EPC. There are two modes in the HaloB feature: Centralized mode and Standalone mode.
• Centralized Mode: In centralized mode, the HaloB eNB is configured and monitored by the
CloudCore OMC and BOSS module, which acts as an agent to manage SIM card data.
• Standalone Mode: Standalone mode removes the OMC+BOSS requirement and allows
operators to input subscriber profiles directly into each HaloB eNB. The HaloB eNB can be
easily configured and maintained using the Local Maintenance Terminal (LMT). As each HaloB
eNB does not require communicating with other HaloB eNBs, a single HaloB eNB can be used
in emergency disaster relief.
You can use the eNB GUI or the OMC to enable the feature. The procedure in each application is
described below.

2.1 Configure HaloB Mode on eNBs Running QRTB Software

NOTE: This section only applies to Nova436Q, Nova430i, Nova430e, and Neutrino430.

Follow the steps below to transition the Nova436Q, Nova430i, Nova430e, or the Neutrino430 eNB to
HaloB eNB. For more information on sign-up, refer to the eNodeB Configuration Guide - BaiBS_QRTB
Software.
1. Log in: Open a web browser and enter http://192.168.150.1. If you have not changed the
eNB’s initial username and password, use the defaults: admin/admin.
2. Import HaloB license: Go to System > License (Figure 2-1) and perform the following steps.
NOTE: If the eNB came with the HaloB license key preloaded, the HaloB license should appear
in the License List.

a. Click on Select File.

b. Find, highlight, and upload the HaloB with centralized mode target file saved on your
computer.
c. Import the file to the License List.

4 |P a g e
Figure 2-1: HaloB License (QRTB)

3. Configure HaloB Setting: Go to BTS Setting > Core Network (Figure 2-2). Select the HaloB
Mode radio button.
The HaloB Mode field can be changed to Centralized Mode or Standalone Mode if desired from
the drop-down menu.
NOTE: The HaloB license key comes in Centralized Mode by default. To include Standalone
Mode, you must send a special request to the Baicells Support team.

• Centralized Mode: In this mode, the eNBs connect to the CloudCore BOSS module,
which acts as an agent to manage SIM card data.
Figure 2-2: HaloB Mode – Centralized Mode (QRTB)

5 |P a g e
 • Standalone Mode: Select the Standalone Mode from the drop-down menu to store
and maintain the subscriber’s data locally. Click Template Download (Figure 2-3). Click
OK at the prompt to open and edit the template in Notepad and save the template to
your computer. Open the .csv file in Notepad. Edit the .csv file in Notepad by entering
the SIM card data and Access Point Name (APN) information. Save the edits to the .csv
file in Notepad. Upload the file by clicking Select File, navigate to the file location, select
the .csv file, and click on Import Card File. After the reboot sequence, the subscriber
information will appear on the Subscriber Data List pane.
Figure 2-3: HaloB Mode – Standalone Mode (QRTB)

4. Reboot and verify the status: The settings will take effect after the eNB reboots automatically;
if it does not reboot, reboot the eNB manually. After the eNB reboots successfully, check the
Status Info pane of the Basic Setting > Basic Info sub-menu (Figure 2-4).
• HaloB Status is ON
• Cell Status is Active
• OMC Status is Connected

6 |P a g e
Figure 2-4: Verify Status (QRTB)

2.2 Configure HaloB Mode on eNBs Running RTS/RTD Software

NOTE: This section only applies to Nova227, Nova233, Nova243, and Nova246.

1. Log in: Open a web browser and enter http://192.168.150.1. If you have not changed the
eNB's initial username and password, use the defaults: admin/admin.
2. Import License: Go to BTS Setting > License Management (Figure 2-5) and perform the
following steps.
NOTE: If the eNB came with the HaloB license key preloaded, the HaloB with centralized
mode license should display in the License List. This is the standard HaloB license. If you want
the HaloB feature to run in Standalone mode, you must send a special request to the Baicells
support team and purchase that license.

a. Click on Select File under the License pane.

b. Find and highlight the HaloB with centralized mode target file saved on your computer.
c. Click on Import License.

7 |P a g e
Figure 2-5: Import HaloB License (RTS/RTD)

NOTE: The option Single Mode displays in the HaloB Mode field drop-down menu if you have
purchased a Standalone mode license.

3. HaloB Setting: Go to BTS Setting > HaloB Setting (Figure 2-6) and choose Enable from the
HaloB field drop-down menu. The HaloB Mode field defaults to Centralized Mode. For
standalone mode, select Single Mode from the drop-down menu. The changes will not take
effect until you click Save.
• Centralized Mode: The CloudCore BOSS module acts as an agent to maintain the
subscriber’s information.
NOTE: When HaloB is set to Enable on the Nova246 (BaiBS_RTD software), the VxLan Setting
pane also displays.

Figure 2-6: HaloB Mode – Centralized Mode (RTS/RTD)

8 |P a g e
 • Standalone (Single Mode): When you select Single Mode, the Import SIM
Information pane displays. Click Template (Figure 2-7), and a .csv file will download.
Open and edit the file to include the subscriber’s information. Upload the file by
clicking Select File, navigate to the file location, select the .csv file and click Import.
After the reboot sequence, the subscriber information will display on the Subscriber
Data List pane.
Figure 2-7: HaloB Mode – Single Mode (RTS/RTD)

4. Reboot: For the settings to take effect, manually reboot the eNB. After the reboot
sequence, the eNB pulls active subscriber information from BOSS to create a local subscriber
database. The eNB now works as a HaloB eNB.

9 |P a g e
2.3 Configure HaloB Mode on CloudCore OMC
You can configure the HaloB setting on eNBs registered in CloudCore OMC. Follow the steps below to
transition a normal eNB to a HaloB eNB. For more information on sign-up and setting up a CloudCore
account, refer to CloudCore Configuration and Network Administration Guide.
1. Log in: Open a web browser and enter the CloudCore address
https://cloudcore.cloudapp.net/cloudcore/. Enter your login user name and password to start
using CloudCore.
2. Import HaloB License: Go to OMC > eNB > Inventory > License (Figure 2-8) and perform the
following steps.
a. Click on the Import icon in the upper right of the window.
b. Find and highlight the HaloB License file saved on your computer.
c. Import the file to the Basic License list.
Figure 2-8: HaloB License (CloudCore OMC)

3. Verify HaloB License: To check the license information that was uploaded, go to
eNB > Monitor and perform the following steps.
a. On the Table Tab, each row of the eNB has an Operation drop-down menu. Click on
Operation > Information.
b. Under the License Info pane (Figure 2-9), the HaloB license will appear in the Feature
List table.

10 | P a g e
Figure 2-9: Verify HaloB License

4. Enable HaloB: Go to OMC > eNB > Monitor (Figure 2-10) and perform the following steps on
the eNBs you want to modify.
a. On the Table tab, each row of the eNB has an Operations drop-down menu. Click on
Operation > Actions > HaloB Enable.
b. The eNB will begin operating in HaloB mode.
Figure 2-10: HaloB Enable (CloudCore OMC)

5. To configure HaloB Setting using eNB Setting, go to step 6. To configure HaloB Setting using
Man-Machine Language (MML) commands, go to step 7.
6. Configure HaloB Setting using eNB Setting: Go to OMC > eNB > Monitor and perform the
following steps on the eNBs you want to modify.
a. Click on Operations > Settings.
b. For eNBs running QRTB product type (software), go to step c and step d. For eNBs
running RTS-RTD product type (software), go to step e and step f.
NOTE: The eNB Settings window differs between QRTB and RTS-RTD product types.

11 | P a g e
 c. Go to the Quick Setting tab (Figure 2-11). Select the HaloB radio button for the Quick
Mode field in the Quick Settings pane and click OK to save the settings.
Figure 2-11: Configure HaloB (Quick Setting Tab)

d. To choose the HaloB mode, go to the BTS tab (Figure 2-12). Under the CoreNetwork
pane, enable the HaloB Enable button. Next, select Centralized or Single from the
HaloB Mode field drop-down menu. Finally, click OK to save the settings.
NOTE: On the CloudCore OMC, the HaloB modes are Centralized and Single (Standalone).

Figure 2-12: Configure HaloB (BTS Tab)

12 | P a g e
 e. For eNBs running in the RTS-RTD product type, select the Special tab (Figure 2-13)
and enable the HaloB Enable button. Next, choose Centralized or Single from the
Mode field drop-down menu.
f. Finally, click OK to save the settings.
Figure 2-13: Configure HaloB (Special Tab)

7. Configure HaloB Setting using Man-Machine Language (MML) commands:

Go to OMC > eNB > Maintenance > MML (Figure 2-14) and perform the following steps.
a. Click the MML tab and select the software stream from the drop-down menu in the
eNB pane. A list of eNBs running the selected software display.
b. Select the eNBs you want to transition to HaloB eNB.
c. Under the MML List pane, select Special Configuration > HaloB. The four HaloB MML
commands are:
• HaloB(LST HALOB)
• HaloB(MOD HALOB)
• CLEAR IMSI(CLEAR IMSI)
• DSCP Setting(LST DSCP)
• DSCP Setting(MOD DSCP)

13 | P a g e
 d. HaloB(LST HALOB): The LST HALOB command (Figure 2-14) displays the HaloB status
and HaloB mode settings of the eNB.
Figure 2-14: MML Command LST HALOB

e. HaloB(MOD HALOB): Using the MOD HALOB command (Figure 2-15), you can modify
the eNB’s HaloB settings.

Figure 2-15: MML Command MOD HALOB

14 | P a g e
 f. CLEAR IMSI(CLEAR IMSI): To clear all the IMSI lists on HaloB and OMC, use the CLEAR
IMSI command, as shown in Figure 2-16.
Figure 2-16: MML Command CLEAR IMSI

g. DSCP Setting(LST DSCP): HaloB supports Differentiated Services Code Point (DSCP),
which ensures Quality of Service (QoS) in the network. The operators have the
flexibility to set priority depending on the nature of traffic on the customer’s network.
Using LST DSCP (Figure 2-17), you can list the DSCP values for each cell. To assign QoS
Class Index (QCI) to DSCP values, use the command DSCP Setting(MOD DSCP).
Figure 2-17: MML Command LST DSCP

h. Select the MML command, enter the configuration parameters, and click DO under the
Control Panel pane.
i. To verify the result of each MML command, check the Result pane in the MML tab view.
15 | P a g e