SAS Deployment Guide
SAS Deployment Guide
User Guide
CloudCore OMC – Version 10.1.4
BaiBS_RTS_3.7
BaiCE_BG_1.8.11
BaiCE_BM_2.5.26_NA
BaiBLN_3.0
BaiBLQ_3.0
August 2023
Version 1.24
SAS Deployment User Guide
Users of this document should already be familiar with and have some experience deploying and using the
Baicells equipment and software applications.
The information in this document is based on the following Baicells software versions:
• eNodeB (eNB): BaiBS_RTS_3.7 (Nova227 and Nova233)
• eNB: BaiBLQ_3.0 (Neutrino430, Nova430e, Nova430i, and Nova436Q)
• eNB: BaiBLN_3.0 (Nova846)
• CPE: BaiCE_BG_1.8.11: Indoor CPEs: AtomID06G and AtomID15M-HP; Outdoor CPEs: AtomOD06H,
AtomOD06L, AtomOD06-LX, and AtomOD15G
• CPE: BaiCE_BM_2.5.26_NA: Outdoor CPEs (AtomOD04H and AtomOD04L)
• OMC: Version 10.1.4
Terms used in this document or related to Long-Term Evolution (LTE) are listed in alphabetical order and
described in Acronyms and Abbreviations, which can be found at Baicells.com > Resources > Documents.
2 |P a g e
SAS Deployment User Guide
Copyright Notice
Baicells Technologies copyrights the information in this document. No part of this document can 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
04-Aug-2023 V1.24 Updated for OMC 10.1.4 and BaiBLN_3.0. Reflects software Yunfeng Jiang, Blake Volk
migration from BaiBS_QRTB to BaiBLQ_3.0 for Neutrino430,
Nova430e, Nova430i, and Nova436Q.
1-May-2023 V1.23 Updated for OMC 8.3.7 and QRTB 2.12. Added BaiBLN_3.0 Blake Volk
(Nova846). Added Unverified CPI feature.
23-Jun-2022 V1.22 Editorial updates -
15-Apr-2022 V1.21 Updated for OMC 7.3.5, RTS 3.7.11, and QRTB 2.9.10. Removed Yunfeng Jiang
Virtual eNB and CPE sections.
11-Sep-2021 V1.20 Updated for OMC 7.1.6 Yunfeng Jiang, Warren Lai, Blake
Volk
16-Jun-2021 V1.19 Updated for QRTB 2.6.2 and OMC 7.0.4. Also updated to include Yunfeng Jiang, Warren Lai, Jesse
Neutrino430 and Atom OD15. Raasch
16-Mar-2021 V1.18 Updated for QRTB 2.5.4, BG_1.6.5.3 (CAT6/7), AP_2.4.7_NA Yunfeng Jiang, Jesse Raasch,
(CAT4), and OMC 6.3.4. Removed Appendix and added reference Nitisha Potti
to Acronyms & Abbreviations document.
3-Nov-2020 V1.17 Added SAS vendor recommendations for requesting grants Nitisha Potti
19-Oct-2020 V1.16 Updated for CAT6/7 BaiCE_BG_1.6.4. Nitisha Potti
14-Oct-2020 V1.15 Updated Table 4-1 SAS Settings. Removed Optional from userid Nitisha Potti
description
12-Oct-2020 V1.14 Updated for QRTB 2.4.2, AP 2.4.5 NA (CAT4), BG 1.6.2 (CAT6/7), TangHoucheng, WangYong,
OMC 6.2.6 Nitisha Potti, Jesse Raasch
8-Sep-2020 V1.13 Updated for RTS 3.6.6, QRTB 2.3.6, AP 2.4.2, OMC 6.0.5.1, BOSS Yunfeng Jiang
6.1.3
7-Jul-2020 V1.12 Software updates BG 1.5.0, AP 2.4.2, Enhancements Yunfeng Jiang, Jesse Raasch
18-May-2020 V1.11 Software updates RTS 3.6.3, QRTB 2.2.4, OMC/BOSS 6.0 Yunfeng Jiang, Nitisha Potti,
4-May-2020 V1.10 Jesse Raasch
3 |P a g e
SAS Deployment User Guide
19-Dec-2019 V1.8 OMC 5.2.7, RTS 3.4.8, QRTB 2.05 updates Ronald Mao, Pengyu Chen,
Enhancements Jason Yunfeng, Katie Heyl, Jesse
17-Dec-2019 V1.7 SME comments Raasch
12-Dec-2019 V1.6 Updates from beta trials
10-Dec-2019 V1.5 Added CPI sig gen tool
9-Dec-2019 V1.4
Resources
• Documentation - Baicells product datasheets and technical manuals 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
4 |P a g e
SAS Deployment User Guide
Table of Contents
1 OVERVIEW.............................................................................................................................................................. 8
2 REFERENCE INFORMATION ..................................................................................................................................... 9
3 PREPARATION ......................................................................................................................................................... 9
3.1 SAS ACCOUNT.......................................................................................................................................................... 9
4 CONFIGURATION .................................................................................................................................................. 10
4.1 SAS REGISTRATION OPTIONS ..................................................................................................................................... 11
List of Figures
FIGURE 4-1: EXPORT TO GOOGLE SAS PORTAL............................................................................................................................... 12
FIGURE 4-7: SAS SETTINGS (BAIBLQ_3.0, DOMAIN PROXY, SINGLE-STEP REGISTRATION) (1 OF 3) ........................................................ 21
5 |P a g e
SAS Deployment User Guide
FIGURE 4-8: SAS SETTINGS (BAIBLQ_3.0, DOMAIN PROXY, SINGLE-STEP REGISTRATION) (2 OF 3) ........................................................ 21
FIGURE 4-9: SAS SETTINGS (BAIBLQ_3.0, DOMAIN PROXY, SINGLE-STEP REGISTRATION) (3 OF 3) ........................................................ 22
FIGURE 4-10: SAS SETTINGS (BAIBLQ_3.0, DOMAIN PROXY, MULTI-STEP REGISTRATION) ................................................................... 22
FIGURE 4-11: SAS SETTINGS (BAIBLQ_3.0, DIRECT SAS, SINGLE-STEP REGISTRATION) (1 OF 3) ........................................................... 23
FIGURE 4-12: SAS SETTINGS (BAIBLQ_3.0, DIRECT SAS, SINGLE-STEP REGISTRATION) (2 OF 3) ........................................................... 23
FIGURE 4-13: SAS SETTINGS (BAIBLQ_3.0, DIRECT SAS, SINGLE-STEP REGISTRATION) (3 OF 3) ........................................................... 23
FIGURE 4-14: SAS SETTINGS (BAIBLQ_3.0, DIRECT SAS, MULTI-STEP REGISTRATION) ........................................................................ 24
FIGURE 4-17: SAS SETTINGS (BAIBLN_3.0, DOMAIN PROXY, SINGLE-STEP REGISTRATION) .................................................................. 30
FIGURE 4-18: SAS SETTINGS (BAIBLN_3.0, DOMAIN PROXY, MULTI-STEP REGISTRATION) ................................................................... 31
FIGURE 4-20: SAS SETTINGS (BAIBLN_3.0, DIRECT SAS, MULTI-STEP REGISTRATION) ........................................................................ 33
FIGURE 4-24: ENABLE SAS WITH MANUAL OPTION (USING CHECKBOX) ............................................................................................. 39
6 |P a g e
SAS Deployment User Guide
FIGURE 4-49: VIEW DEVICE LOGS (FILTER – SET DATE RANGE) ......................................................................................................... 58
FIGURE 4-50: VIEW DEVICE LOGS (FILTER – SET TIME INTERVAL) ...................................................................................................... 59
List of Tables
TABLE 2-1: CBSD CATEGORIES ..................................................................................................................................................... 9
TABLE 4-4: ENB SAS SETTINGS FOR RTS 3.7 SOFTWARE ................................................................................................................. 63
7 |P a g e
SAS Deployment User Guide
1 Overview
The Citizens Broadband Radio Service (CBRS) covers the once-regulated 3.55–3.7 GHz band. The Federal
Communications Commission (FCC) freed up the previous military only CBRS band for commercial use. CBRS
officially launched in January 2020. The ability for operators to use CBRS provides an economical way for existing
operators to increase coverage and capacity. In addition, it offers a low-cost solution for start-up operators to
enter the market. Not only does CBRS add an available spectrum, but it also rivals current Wi-Fi networks due
to its (a) propagation characteristics and (b) planned design and support for next-generation mobility and Fifth-
Generation Wireless Systems (5G) networks.
In terms of implementation, what makes CBRS especially different is the way the 3.55–3.7 GHz band can be
accessed. CBRS commercialization is based on the concept of a “shared” spectrum, where the spectrum is
dynamically assigned and released on an as-needed basis. CBRS has three tiers of spectrum use: Tier 1 (high
priority), Tier 2 (second priority), and Tier 3 (low priority). Tier 1 is Incumbent users - High-power shipboard
and land-based radar, Tier 2 is Priority Access License (PAL) users - licensed users who acquire spectrum through
auction, and Tier 3 is General Authorized Access (GAA) users.
Shared spectrum assignment is handled by Spectrum Access System (SAS) vendors. Amdocs, Federated
Wireless, and Google are FCC Part 96 certified SAS vendors. To use the CBRS spectrum, the CBRS Service
Devices (CBSDs), such as the Baicells eNodeB (eNB) and Customer Premise Equipment (CPE), also must go
through certification. Certification is an ongoing process as new products are introduced. In addition, all
CBSDs must be installed by a Certified Professional Installer (CPI) to operate within the designated spectrum
of CBRS lawfully.
The CBSD equipment must be configured to connect to a SAS vendor for band assignment. A CBSD transmits
Radio Frequency (RF) in the CBRS band and is subject to FCC rules. The SAS enforces the FCC rules. When the
assigned band is no longer needed, SAS can free it up so that other users can operate in that band.
As a champion of CBRS commercialization for years, Baicells is ready to work with operators. Once you have
your SAS vendor account and are approved to be a Baicells trial user, follow this guide to configure the eNB
and user equipment, and associate your OMC account to your SAS account.
8 |P a g e
SAS Deployment User Guide
2 Reference Information
For certification, the CBSD equipment is categorized as shown in Table 2-1.
NOTE 1: The devices in Table 2-1 can operate only if they can positively receive and decode authorization
signals transmitted by CBSDs.
NOTE 2: Unlike the CAT A and CAT B CBSDs, EUDs do not require spectrum sharing access because of
their lower transmit power. The EUDs, therefore, do not require SAS registration or CPI
certification, so the information in this document does not apply to EUDs.
NOTE 3: For reference only, the Baicells EUDs include AtomID15M-HP-EUD (EG3015M-M30-HP-EUD,
AtomOD06-LX EUD (EG-8013L-M11-EUD), and AtomOD15G EUD (EG8015G-M11-EUD).
3 Preparation
9 |P a g e
SAS Deployment User Guide
Product Software
Nova846 BaiBLN_3.0
NOTE 1: See Table 4-8 for detailed information about all of these Baicells CBSD products, including FCC
identification, FCC certified maximum EIRP, CBSD category, and more.
NOTE 2: The first generation (Gen 1) Baicells CPEs do not support SAS.
NOTE 3: Gen 1 CAT4 CPEs are now End Of Life (EOL).
NOTE 4: BaiOMC can be cloud based (cloudcore.baicells.com) or local (a private network).
4 Configuration
References:
• CloudCore Configuration and Network Administration Guide
• RTS-RTD eNodeB Configuration Guide
• 4G LTE eNodeB Configuration Guide - BaiBLQ
• 4G LTE eNodeB Configuration Guide - BaiBLN
• Atom CAT4 CPE Configuration Guide
• Atom CAT6/CAT15 CPE Configuration Guide
Caution: Once you have an account with an approved SAS vendor and enable SAS on the
CBSD and in the OMC (DP), current users attached to the CBSD are disconnected until the
CBSD reaches transmission state with the SAS. Once the SAS authorizes the CBSD and reaches
the transmission state, users are automatically reconnected.
10 | P a g e
SAS Deployment User Guide
NOTE 1: Throughout this document, the term CBSD can mean eNB or CPE. Procedures that are specific
to one device type are identified as such.
NOTE 2: Each SAS vendor provides its own GUI to assist you in using its SAS portal.
NOTE 3: When SAS is enabled on eNBs running RTS 3.7 software, the standard BTS Info > Quick Setting
fields Band, Bandwidth, Frequency, and Power Modify are greyed out; the eNB uses the configuration
based on the SAS settings response. Similarly, for eNBs running BaiBLQ_3.0 or BaiBLN_3.0 software,
when SAS is enabled on the eNB, the standard Basic Setting > Quick Setting (BaiBLQ_3.0) or BTS Info >
Quick Setting (BaiBLN) fields Band, Bandwidth, EARFCN, Frequency, and Power Modify are greyed out;
the eNB uses the configuration based on the SAS settings response. However, you can configure your
preferences for these settings by selecting a Frequency Selection Logic, described in detail in
section 4.2.1.
NOTE 4: The GUI fields vary between BaiBS_RTS, BaiBLN, and BaiBLQ software versions.
NOTE 1: Regardless of which registration option you use, you must configure the CBSD’s basic
information for successful registration with SAS.
NOTE 2: For Option 3, when using the Multi-Step registration method, Baicells recommends that
you upload all CBSD information in the SAS portal before enabling SAS on the CBSD.
NOTE 3: The CPI must upload the certificate directly through the SAS portal.
11 | P a g e
SAS Deployment User Guide
NOTE 1: Choose the Export to Google SAS function only if Google is your SAS vendor.
NOTE 2: Baicells is committed to working with all certified SAS vendors to support this functionality as it
becomes available to assist you with SAS deployment activities.
NOTE 3: The Export for CBSD Params function is used to import the parameters to the OMC (DP).
NOTE 4: The Export for monitor function creates a .cvs file of the OMC > Advance menu, SAS sub-menu
information.
12 | P a g e
SAS Deployment User Guide
Prerequisites: Verify that the management server URL is correct on the eNB GUI. Since the eNB uses a DP
method to connect to the SAS, an OMC connection is required.
1. If your NMS is the Baicells CloudCore OMC, proceed to step 2 and perform the entire procedure
described through step 6. If you are using a Local OMC or another Element Management System
(EMS) or NMS, enter the URL for that device e.g., xx.xx.xx.xx:8080/smallcell/AcsService.
2. In the BTS Setting > Management Server sub-menu, enter the URL and port number:
baiomc.cloudapp.net:8443/smallcell/AcsService. Ensure the port number specified is 8443.
3. Optional: Enable a Secure Socket Layer (SSL) connection for enhanced security.
4. If you are using the Baicells CloudCore OMC for your NMS, enter your unique operator CloudKey ID
that you received from Baicells. Your CloudKey ID displays at the top of your CloudCore account
window. (The CloudKey is not required for Local OMC).
NOTE: The CloudKey is used as part of the plug-and-play aspect of the Baicells network elements. When
you configure your CloudKey ID in the device GUI, the first time the device is powered on it is
automatically associated with your OMC account.
5. Click Save. A message displays confirming the configuration is successful. Click OK.
6. If you choose to use the Single-Step registration type, have your CPI info and all antenna
requirements ready to input before starting the configuration procedures.
NOTE: With OMC 10.1.4 software, you can now configure and modify all the CBSD settings
directly in the OMC if desired. Refer to CloudCore Configuration and Network
Administration Guide for more information.
13 | P a g e
SAS Deployment User Guide
NOTE 1: More about each registration option (Single-Step or Multi-Step) is covered in section 4.1
and section 4.3.
NOTE 2: HaloB-enabled eNBs operate as standalone entities and do not support mobility, so the
LTE menu options change depending on the HaloB function setting. Therefore, as you
select the SAS Settings sub-menu from the LTE menus, you may notice differences
between your eNB GUI and how the LTE menus are depicted in Figure 4-2 and Figure 4-3.
4. Install Param Config: Refer to Table 4-4 in section 4.5 for each parameter’s description to complete the
SAS configuration in this menu.
5. CPI info: If you selected the Single-Step method for registration type, enter the CPI ID, name, and
installation information.
6. CPI certstore: If you selected the Single-Step method for registration type, this section displays Loaded
if the CPI certificate is already uploaded from the System > CertStore sub-menu. This section displays
Missing if the CPI certificate has not been uploaded. An add/change function is provided to upload or
change the certificate here.
7. Click on Save when the configuration is complete. This step must be performed for the SAS-related
fields to display in the BTS Info > Quick Setting sub-menu.
14 | P a g e
SAS Deployment User Guide
15 | P a g e
SAS Deployment User Guide
NOTE: Certificate file types supported are p12 and pem. One of the pem formats is pkcs8.
–If you select file type p12, you must input a password.
–If you select file type pkcs8, you do not need a password.
16 | P a g e
SAS Deployment User Guide
NOTE: The Legacy Mode field is in the BTS Info > Quick Setting and does not display unless SAS is
enabled from the LTE > SAS Settings sub-menu (section 4.2.1.2).
3. Frequency Selection Logic: After sending a request for spectrum from the SAS, the DP selects the first
channel available from the SAS’s response. But operators can configure their preferred frequencies,
channel bandwidth, and power by selecting a Frequency Selection Logic and entering the Preferred
Bandwidth, Preferred Power, and Preferred Frequency.
For example, if you choose Power, Frequency, and Bandwidth for this setting, the DP uses power as the
most important value to calculate CBRS channel selection.
Select one of the following to indicate the order of importance for the frequency selection logic:
• Frequency, Bandwidth, Power
• Frequency, Power, Bandwidth
• Bandwidth, Frequency, Power
• Bandwidth, Power, Frequency
• Power, Bandwidth, Frequency (default)
• Power, Frequency, Bandwidth
5. Preferred Power: Enter the preferred power for this eNB. Preferred power is the total TX power (in
dBm) transmitted per carrier. For example, if it is desired for the eNB to emit 2W of power (2x1W) per
carrier, then the preferred power would be 33 (dBm).
17 | P a g e
SAS Deployment User Guide
6. Preferred Frequency: Enter the preferred frequency for this eNB. You can add more than one
preferred frequency and set the priority. Click on the Add (+) icon to add more preferred frequencies,
enter the value(s), and select the priority. For example, if the eNB is a two-carrier eNB, enter the
preferred frequency or frequencies for the Primary Cell (Pcell) and Secondary Cell (Scell).
NOTE 1: When applying any changes to these preferred parameters, the DP automatically
relinquishes the eNB’s existing grant and restarts the spectrum inquiry and grant
procedure.
NOTE 2: If you have purchased a Priority Access License (PAL) when using the frequency
selection logic, the DP chooses that channel type instead of a General Authorized
Access (GAA) channel. You can view SAS logs to verify the authorized channels in use.
See section 4.3.1 and Figure 4-47 for more information.
NOTE 3: The Basic Setting > Quick Setting GUI labels vary slightly depending on the carrier
setting configured in BTS Setting > Carrier Setting. If the eNB is set to Single Carrier
mode, one cell is configured. If the eNB is set to Dual Carrier (DC)/split mode, two cells
are configured and display fields for Cell1 and for Cell2. If the eNB is set to Carrier
Aggregation mode, fields display as “Pcell” and “Scell.”
NOTE 4: SAS vendors recommend requesting grants before 12:00 AM or after 3:00 AM PST.
18 | P a g e
SAS Deployment User Guide
Prerequisites: Verify that the management server URL is correct on the eNB GUI. Since the eNB uses a DP
method to connect to the SAS, an OMC connection is required.
1. If your NMS is the Baicells CloudCore OMC, proceed to step 2 and perform the entire procedure
described through step 8. If you are using a Local OMC or another Element Management System
(EMS) or NMS, enter the URL for that device e.g., xx.xx.xx.xx:8080/smallcell/AcsService.
2. If the eNB operating mode is set to Cloud EPC in the Network > Core Network menu, proceed to
step 3. Otherwise, skip to step 4.
3. In the Management Server Config pane of the BTS Setting > Management Server sub-menu, set the
Override OMC URL field to ON.
NOTE: When the Override OMC URL field is OFF, which is the default setting, the SSL and Management
Server fields are greyed out, so you must change this setting to continue configuration steps.
4. In the BTS Setting > Management Server sub-menu, enter the URL and port number:
baiomc.cloudapp.net:8443/smallcell/AcsService. Ensure the port number specified is 8443.
5. Optional: Enable a Secure Socket Layer (SSL) connection for enhanced security.
6. If you are using the Baicells CloudCore OMC for your NMS, enter your unique operator CloudKey ID
that you received from Baicells. Your CloudKey ID displays at the top of your CloudCore account
window. (The CloudKey is not required for Local OMC).
NOTE 1: The CloudKey is used as part of the plug-and-play aspect of the Baicells network elements. When
you configure your CloudKey ID in the device GUI (eNB and CPE), the first time the device is
powered on it is automatically associated with your OMC account.
NOTE 2: Notice the TR069 field is pre-configured and WAN is the default.
NOTE 3: You can also configure the Simple Network Management Protocol (SNMP) from the BTS Setting >
Management Server sub-menu. Refer to the 4G LTE eNodeB Configuration Guide - BaiBLQ for
more information.
7. Click Save. A message displays confirming the configuration is successful. Click OK.
8. If you choose to use the Single-Step registration type, have your CPI info and all antenna
requirements ready to input before starting the configuration procedures.
19 | P a g e
SAS Deployment User Guide
NOTE: With OMC 10.1.4 software, you can now configure and modify all the CBSD settings
directly in the OMC if desired. Refer to the CloudCore Configuration and Network
Administration Guide for more information.
NOTE: More about each registration option (Single-Step or Multi-Step) is covered in section 4.1
and section 4.3.
4. Install Param Config: Refer to Table 4-5 in section 4.5 for each parameter’s description to complete the
SAS configuration in this menu.
NOTE: You can enter each parameter manually, or select Automatic from the Automatic/Manual drop-
down menu, and the parameters are auto-generated (Figure 4-8 and Figure 4-12).
5. CPI info: If you selected the Single-Step method for registration type in step 3, enter the CPI ID, name,
and installation information.
6. CPI Certificate: If you selected the Single-Step method for registration type in step 3, this section
displays the CPI certificate in the Certificate List table if it is already uploaded from the System >
Certificate sub-menu. This section displays Missing if the CPI certificate has not been uploaded. Use
Select File to upload or change the certificate here.
NOTE: When the country code is set to USA-FCC(CBRS)-Direct SAS, a certType drop-down menu displays
(Figure 4-13).
20 | P a g e
SAS Deployment User Guide
21 | P a g e
SAS Deployment User Guide
NOTE: The Automatic/Manual field displays in the Install Param Config pane when the carrier mode (in
the Quick Setting pane) is set to Single Carrier and the SAS registration type (in the SAS Preferred
Setting pane) is set to Single-Step registration mode. Similarly, the Automatic/Manual field
displays in the Cell1 Install Param Config pane and the Cell2 Install Param Config pane if the
carrier mode (in the Quick Setting pane) is set to Dual Carrier and the SAS registration type (in
the SAS Preferred Setting pane) is set to Single-Step registration mode.
22 | P a g e
SAS Deployment User Guide
23 | P a g e
SAS Deployment User Guide
NOTE: Certificate file types supported are p12 and pem. One of the pem formats is pkcs8.
–If you select file type p12, you must input a password.
–If you select file type pkcs8, you do not need a password.
24 | P a g e
SAS Deployment User Guide
NOTE 1: The Legacy Mode field is in the SAS Preferred Setting pane of the Basic Setting > Quick
Setting sub-menu.
NOTE 2: The SAS Preferred Setting pane displays only when USA-FCC(CBRS)-Domain Proxy or
USA-FCC(CBRS)-Direct SAS is selected from the Country Code field drop-down menu in
the Quick Setting pane of the Basic Setting > Quick Setting sub-menu.
3. Frequency Selection Logic: After sending a request for spectrum from the SAS, the DP selects the first
channel available from the SAS’s response. But operators can configure their preferred frequencies,
channel bandwidth, and power by selecting a Frequency Selection Logic and entering the Preferred
Bandwidth, Preferred Power, and Preferred Frequency.
For example, if you choose Power, Frequency, and Bandwidth for this setting, the DP uses power as the
most important value to calculate CBRS channel selection.
Select one of the following to indicate the order of importance for the frequency selection logic:
• Frequency, Bandwidth, Power
• Frequency, Power, Bandwidth
25 | P a g e
SAS Deployment User Guide
5. Preferred Power: Enter the preferred power for this eNB. Preferred power is the total TX power (in
dBm) transmitted per carrier. For example, if it is desired for the eNB to emit 2W of power (2x1W) per
carrier, then the preferred power would be 33 (dBm).
6. Preferred Frequency: Enter the preferred frequency for this eNB. You can add more than one
preferred frequency and set the priority. Click on the Add (+) icon to add more preferred frequencies,
enter the value(s), and select the priority. For example, if the eNB is a two-carrier eNB, enter the
preferred frequency or frequencies for the Primary Cell (Pcell) and Secondary Cell (Scell).
NOTE 1: When applying any changes to these preferred parameters, the DP automatically
relinquishes the eNB’s existing grant and restarts the spectrum inquiry and grant
procedure.
NOTE 2: If you have purchased a Priority Access License (PAL) when using the frequency
selection logic, the DP chooses that channel type instead of a General Authorized
Access (GAA) channel. You can view SAS logs to verify the authorized channels in use.
See section 4.3.1 and Figure 4-47 for more information.
NOTE 3: The “Channel Reuse” checkbox in the SAS Preferred Setting pane displays only when
the eNB is set to Dual Carrier mode.
NOTE 4: The Basic Setting > Quick Setting GUI labels vary slightly depending on the carrier
setting configured in BTS Setting > Carrier Setting. If the eNB is set to Single Carrier
mode, one cell is configured. If the eNB is set to Dual Carrier (DC)/split mode, two cells
are configured and display fields for Cell1 and for Cell2. If the eNB is set to Carrier
Aggregation mode, fields display as “Pcell” and “Scell.”
NOTE 5: SAS vendors recommend requesting grants before 12:00 AM or after 3:00 AM PST.
26 | P a g e
SAS Deployment User Guide
Prerequisites: Verify that the management server URL is correct on the eNB GUI. Since the eNB uses a DP
method to connect to the SAS, an OMC connection is required.
1. If your NMS is the Baicells CloudCore OMC, proceed to step 2 and perform the entire procedure
described through step 6. If you are using a Local OMC or another Element Management System
(EMS) or NMS, enter the URL for that device e.g., xx.xx.xx.xx:8080/smallcell/AcsService.
2. In the BTS Setting > Management Server sub-menu, enter the URL and port number:
baiomc.cloudapp.net:8443/smallcell/AcsService. Ensure the port number specified is 8443.
3. Optional: Enable a Secure Socket Layer (SSL) connection for enhanced security.
4. If you are using the Baicells CloudCore OMC for your NMS, enter your unique operator CloudKey ID
that you received from Baicells. Your CloudKey ID displays at the top of your CloudCore account
window. (The CloudKey is not required for Local OMC).
NOTE: The CloudKey is used as part of the plug-and-play aspect of the Baicells network elements. When
you configure your CloudKey ID in the device GUI, the first time the device is powered on it is
automatically associated with your OMC account.
5. Click Save. A message displays confirming the configuration is successful. Click OK.
6. If you choose to use the Single-Step registration type, have your CPI info and all antenna
requirements ready to input before starting the configuration procedures.
27 | P a g e
SAS Deployment User Guide
NOTE: With OMC 10.1.4 software, you can now configure and modify all the CBSD settings
directly in the OMC if desired. Refer to CloudCore Configuration and Network
Administration Guide for more information.
NOTE: When you choose Domain Proxy, the OMC functions as a DP between the eNB and the SAS, and
SAS access is implemented through the OMC. When you choose Direct SAS, the eNB is directly
connected to the SAS server.
3. In the Server URL field, use the drop-down menu to select the server URL you want to use. Options are
Amdocs, CommScope, Google, and Custom. Choose Custom if you want to configure a server URL other
than Amdocs, CommScope, or Google.
4. SAS Registration Type: For the field in this menu, select either Single-Step or Multi-Step from the
drop-down menu. The fields displayed beneath the registration type depend on which option you
choose, as shown in Figure 4-17, Figure 4-18, Figure 4-19, and Figure 4-20.
NOTE 1: More about each registration option (Single-Step or Multi-Step) is covered in section 4.1
and section 4.3.
NOTE 2: HaloB-enabled eNBs operate as standalone entities and do not support mobility, so the
LTE Setting menu options change depending on the HaloB function setting. Therefore, as
you select the SAS Settings sub-menu from the LTE Setting menus, you may notice
differences between your eNB GUI and how the LTE Setting menus are depicted in
Figure 4-17, Figure 4-18, Figure 4-19, and Figure 4-20.
5. Install Param Config: Refer to Table 4-6 in section 4.5 for each parameter’s description to complete the
SAS configuration in this menu.
28 | P a g e
SAS Deployment User Guide
6. CPI info: If you selected the Single-Step method for registration type, enter the CPI ID, name, and
installation information.
7. CPI Certstore: If you selected the Single-Step method for registration type, this section displays Loaded
if the CPI certificate is already uploaded from the System > CertStore sub-menu. This section displays
Missing if the CPI certificate has not been uploaded. An add/change function is provided to upload or
change the certificate here.
8. Click on Save when the configuration is complete. This step must be performed for the SAS-related
fields to display in the BTS Info > Quick Setting sub-menu.
29 | P a g e
SAS Deployment User Guide
30 | P a g e
SAS Deployment User Guide
31 | P a g e
SAS Deployment User Guide
32 | P a g e
SAS Deployment User Guide
33 | P a g e
SAS Deployment User Guide
NOTE: The Legacy Mode field is in the BTS Info > Quick Setting and does not display unless SAS
is enabled from the LTE > SAS Settings sub-menu (section 4.2.3.2).
3. Frequency Selection Logic: After sending a request for spectrum from the SAS, the DP selects the first
channel available from the SAS’s response. But operators can configure their preferred frequencies,
channel bandwidth, and power by selecting a Frequency Selection Logic and entering the Preferred
Bandwidth, Preferred Power, and Preferred Frequency.
34 | P a g e
SAS Deployment User Guide
For example, if you choose Power, Frequency, and Bandwidth for this setting, the DP uses power as the
most important value to calculate CBRS channel selection.
Select one of the following to indicate the order of importance for the frequency selection logic:
• Frequency, Bandwidth, Power
• Frequency, Power, Bandwidth
• Bandwidth, Frequency, Power
• Bandwidth, Power, Frequency
• Power, Bandwidth, Frequency (default)
• Power, Frequency, Bandwidth
5. Preferred Power: Enter the preferred power for this eNB. Preferred power is the total TX power (in
dBm) transmitted per carrier. For example, if it is desired for the eNB to emit 2W of power (2x1W) per
carrier, then the preferred power would be 33 (dBm).
6. Preferred Frequency: Enter the preferred frequency for this eNB. You can add more than one
preferred frequency and set the priority. Click on the Add (+) icon to add more preferred frequencies,
enter the value(s), and select the priority. For example, if the eNB is a two-carrier eNB, enter the
preferred frequency or frequencies for the Primary Cell (Pcell) and Secondary Cell (Scell).
NOTE 1: When applying any changes to these preferred parameters, the DP automatically
relinquishes the eNB’s existing grant and restarts the spectrum inquiry and grant
procedure.
NOTE 2: If you have purchased a Priority Access License (PAL) when using the frequency selection
logic, the DP chooses that channel type instead of a General Authorized Access (GAA)
channel. You can view SAS logs to verify the authorized channels in use. See section 4.3.1
and Figure 4-47 for more information.
NOTE 3: The Basic Setting > Quick Setting GUI labels vary slightly depending on the carrier setting
configured in BTS Setting > Carrier Setting. If the eNB is set to Single Carrier mode, one
cell is configured. If the eNB is set to Dual Carrier (DC)/split mode, two cells are
configured and display fields for Cell1 and for Cell2. If the eNB is set to Carrier
Aggregation mode, fields display as “Pcell” and “Scell.”
NOTE 4: SAS vendors recommend requesting grants before 12:00 AM or after 3:00 AM PST.
35 | P a g e
SAS Deployment User Guide
36 | P a g e
SAS Deployment User Guide
NOTE: The CloudKey is used as part of the plug-and-play aspect of the Baicells network elements. When
you configure your CloudKey ID in the device GUI, the first time the device is powered on it is
automatically associated with your OMC account.
NOTE: Field descriptions for the SAS Info pane can be found in Table 4-7.
1. In the SAS Settings pane, there are two options for enabling SAS on a certified CPE: Automatic(B48) or
Manual. A description of each is below.
b. Manual - Select the Enable checkbox next to SAS (Figure 4-24). Additional configuration fields
display.
NOTE: Figure 4-24 shows the CAT6/15 CUI, but the figure applies to all CPEs.
37 | P a g e
SAS Deployment User Guide
38 | P a g e
SAS Deployment User Guide
2. In the SAS Settings window, select the Access Method, either Domain Proxy or Direct SAS
(Figure 4-25).
NOTE: Figure 4-25 shows the CAT4 GUI, but the figure applies to all CPEs.
• Domain Proxy - Notice the ACS Server URL field is auto-configured, for example:
https://baiomc.cloudapp.net:8443/smallcell/AcsService
• Direct SAS - Notice the SAS Server URL field is auto-configured, for example:
https://example.sas.server:5000/v1.2
39 | P a g e
SAS Deployment User Guide
NOTE 1: Figure 4-26 shows the CAT6/15 GUI, but the figure applies to all CPEs.
• Multi-Step - choose this method when the installation information of the device already exists on
the SAS server.
• Single-Step - choose this method when there is no installation information of the device on the
SAS server.
Figure 4-26: Registration Method
4. When Direct SAS and Single-Step registration modes are selected, additional fields display, prompting
you to configure antenna parameters (Figure 4-27). Refer to Table 4-1 for field descriptions.
NOTE: Figure 4-27 shows the CAT4 GUI, but the figure applies to all CPEs.
40 | P a g e
SAS Deployment User Guide
Field Description
Latitude Latitude of the CPE antenna location in degrees (-90.0° to 90.0°)
Longitude Longitude of the CPE antenna location in degrees (-180.0° to 180.0°)
Indoor Deployment Whether the CPE antenna is indoor or not
True - the CPE antenna is indoor
False - the antenna is outdoor
Antenna Height The CPE antenna height (meters or feet)
Antenna Azimuth Boresight direction of the horizontal plane of the antenna in degrees with respect to
true north (-0°–359°)
Antenna Downtilt Antenna downtilt in degrees and is an integer (-90.0° to 90.0°)
Antenna Beamwidth The CPE antenna beamwidth (0°–360°)
5. The SAS Server URL is the web address of the ACS. If Domain Proxy is the access method, the field is
auto-filled (see explanation in section 4.2.4.2). This field cannot be edited if Direct SAS is the access
method.
6. Enter the User ID provided by the SAS vendor.
7. Optional: Enter the Call Sign, a parameter useful to identify the PAL license under which the operator
is deploying a CPE. The parameter is not necessary to configure the GAA spectrum (3550–3700 MHz).
The range is 0 to 256 characters (using upper-case letters A–Z, lower-case letters a–z, and digits 0–9).
41 | P a g e
SAS Deployment User Guide
8. When Single-Step is selected for the Registration Method, the CPI Settings window displays, as shown
in Figure 4-28. The CPI settings are used to verify the installer’s information (refer to Table 4-2 for a
description of each field).
NOTE: Figure 4-28 shows the CAT6/15 GUI, but the figure applies to all CPEs.
9. Enter the CPI ID or CPI Name, and the Install Time, or select Auto to have the time auto-filled. Select
Browse…to upload a CPI certificate file from your personal computer. Click Save & Apply (CAT4)/Apply
(CAT6/15) to save the information or Clear to erase the data.
Figure 4-28: CPI Settings
Field Description
CPI ID The identification number of the certified professional installer
CPI Name The name of the certified professional installer
Install Time Time of day the SAS certificate is imported in (e.g., 2022-07-05T15:07:04Z) or select Auto to
have the time auto-entered.
Upload Certificate Select Browse to navigate to the saved CPI certificate on your personal computer.
42 | P a g e
SAS Deployment User Guide
43 | P a g e
SAS Deployment User Guide
44 | P a g e
SAS Deployment User Guide
NOTE 1: You can use the OMC query function (Figure 4-33) to search for a specific eNB device or check
its active status.
NOTE 2: Refer to the CloudCore Configuration and Network Administration Guide for more information
about non-SAS-related searches you can perform.
45 | P a g e
SAS Deployment User Guide
You can choose from two options, as described here, to register the eNB and CPE CBSDs with SAS using the
domain proxy (OMC).
• Choice 1 (Single-Step): Use the OMC to configure all the required parameters.
• Choice 2 (Multi-Step): Configure only the CBSD’s basic information using the OMC, and then use
the SAS portal to configure the antenna installation parameters.
NOTE 1: Regardless of the registration type, you must configure the CBSD’s basic information for
successful registration with SAS.
NOTE 2: You must upload a CPI certificate (signature) to use Single-Step registration.
NOTE 3: The CPI Certificate only needs to be uploaded once per login session.
NOTE 4: See the following sections for configuring eNB preferred frequency settings:
section 4.2.1.4 (eNBs running RTS software), section 4.2.2.4 (eNBs running BaiBLQ
software), and section 4.2.3.4 (eNBs running BaiBLN software).
46 | P a g e
SAS Deployment User Guide
3. Select the Unverified CPI icon (Figure 4-34) to open the Verify CPI Identity window.
NOTE 1: Once the CPI Certificate is verified, you do not need to upload the certificate again unless you
log out after verification. In this case, you will need to upload the certificate again.
NOTE 2: Only p12 and pem certificate file types are supported. If you use a p12 file format, select the
checkbox and enter a password in the Password field that displays.
4. Select the Import icon and navigate to the saved CPI Certificate on your computer.
5. Then enter the Password (if you’ve selected the P12 checkbox), the CPI ID, and CPI Name, and select
OK (Figure 4-35).
Figure 4-35: Import CPI Certificate
47 | P a g e
SAS Deployment User Guide
6. Click the Settings icon on the left of the desired device to display its Settings window (Figure 4-36).
Figure 4-36: Open Settings Window
48 | P a g e
SAS Deployment User Guide
7. Configure the required preferred settings parameters, which vary depending on the CBSD device type
(Figure 4-37).
NOTE: Set Legacy Mode to “Enable” if there are legacy CPEs that only support Bands 42 or 43.
NOTE 1: The Synchronize icon can be used to immediately synchronize the eNB SAS settings with the
OMC.
NOTE 2: Device logs can be viewed by clicking on the Logs icon. See section 4.3.4 and Figure 4-46 for
more information.
8. Configure the required basic information parameters, which vary depending on the CBSD device type
(Figure 4-38).
NOTE 1: Your SAS vendor provides the User ID. The Call Sign is a unique company identifier issued by
the FCC. You can configure the Call Sign, but it is not mandatory.
NOTE 2: At this time, for Radio Technology, only E_UTRA displays and the field is greyed out.
E_UTRA identifies that the eNB CBSD is using LTE technology. For Group Type, only
INTERFERENCE_COORDINATION is used. When General Authorized Access (GAA) coexistence
is introduced in the future, SAS vendors will likely use CBSD groups.
49 | P a g e
SAS Deployment User Guide
9. As shown in Figure 4-39, configure the required installation parameters, or modify the existing
parameters by selecting the Modify button (Figure 4-40).
50 | P a g e
SAS Deployment User Guide
10. Click OK and click the X icon on the upper right-hand side of the screen to close the Settings pane.
NOTE: For any newly added CBSD, you only need to add the CPI Certificate once in the OMC.
51 | P a g e
SAS Deployment User Guide
2. Check the CBSD’s connection state by clicking on the Settings icon for the device you want to check,
and the Settings pane displays. A Procedure State diagram displays at the top of the Settings pane. If
you hover over one of the Procedure State icon labels, a drop-down menu displays actions to take on
that step of the connection setup process. In Figure 4-42, for example, the device is not registered yet
and shows as Unregistered. Another scenario would enable SAS to request device registration
manually using the Procedure State diagram rather than the auto-registration option. When you
hover over the Unregistered Procedure State icon label, the drop-down menu displays the action you
perform at this point: Register req. Select this action to start the request. In Figure 4-43, for example,
the device Procedure State shows Authorized, and the drop-down menu displays three actions you
can perform: Heartbeat req, Relinquishment req, or Deregister req.
Figure 4-42: Check CBSD Connection Details (Example 1, Unregistered)
52 | P a g e
SAS Deployment User Guide
NOTE 1: Before beginning this procedure, we recommend creating your CBSD data file so it is
ready to import to the OMC when prompted. Instructions are provided below to assist
you if you need help creating a CBSD data file.
NOTE 2: Device logs can be viewed by clicking on the Logs icon. See section 4.3.4 and Figure 4-46
for more information.
2. Click on the eNB tab or CPE tab, and then click on the Import icon to access the Import CBSDs pane
(Figure 4-44).
NOTE: All the fields in this pane, and the associated files and certificates, are required for
successful CBSD data file import.
53 | P a g e
SAS Deployment User Guide
3. Click on the blue arrow icon to upload your CBSD data’s Excel file. If you need help creating a CBSD
data file, proceed to step 4. If not, skip to step 5.
4. Click on the Download Sample Template link and open or save the .xlsx file; then, once the file opens,
follow the instructions provided (Figure 4-45).
NOTE: Do not remove the template instruction page from the template file.
54 | P a g e
SAS Deployment User Guide
55 | P a g e
SAS Deployment User Guide
The logs show information pertaining to CBSD <-> OMC (DP) <-> SAS communications, i.e., messages sent to
and from SAS. There are two types of logs: Message Logs (SAS logs) and Logs (CBSD logs). In Message Logs, the
columns show the direction (From/To), Log Name, Message, and the date and time* of the event. Hover over
the Message to see the message request from DP and reply from SAS. The Logs columns show the CBSD ID,
GRANT ID, State (all CBSD states are described in Table 4-3 in section 4.3.4.1), and the date and time* of the
event.
Figure 4-46: Access Device Logs (All Key Events)
Check “spectrumInquiryResponse” messages in the Message logs (Figure 4-47) or the Channel Type column in
the Advance > SAS to verify the types of channels (GAA and PAL) being requested for use according to the
frequency selection logic settings you selected in section 4.2.1.4 (eNBs running RTS software), section 4.2.2.4
(eNBs running BaiBLQ software), and section 4.2.3.4 (eNBs running BaiBLN software).
56 | P a g e
SAS Deployment User Guide
After accessing logs, you can filter and view a sub-set of them online according to a preferred date and time
range by performing the following steps:
NOTE 1: The time range you specify cannot exceed seven calendar days (to the exact hour, minute, and
second), or you receive an error message.
NOTE 2: To configure a time range filter, you must first select a start and end date.
NOTE: The date range fields are at the top of the calendar update to display your selected days.
57 | P a g e
SAS Deployment User Guide
3. If you want to set the specific time intervals for the filter, see step 4 through step 6. Otherwise, go
to step 7.
Figure 4-49: View Device Logs (Filter – Set Date Range)
NOTE: The logs retention period governs how far back in time you can retrieve the logs. In this
case, the logs retention period is seven calendar days. Therefore, you can only
view/export logs from the last seven days.
58 | P a g e
SAS Deployment User Guide
4. Click on the start date-time interval field to display the time set box (Figure 4-50), which contains three
columns for setting hours, minutes, and seconds.
Figure 4-50: View Device Logs (Filter – Set Time Interval)
5. Click in the first column, scroll to the hour you want, and select it. Then, repeat the process to select
minutes from the middle column and seconds from the third column, in that order.
NOTE: The time intervals can also be entered in the interval fields instead of using the time set
boxes. Ensure you enter the times using the “hh:mm:ss” format with colons separating
each increment.
59 | P a g e
SAS Deployment User Guide
NOTE: We recommend applying the filters while using the Export function if you plan to export
the device logs file instead of viewing online. Refer to section 4.3.4.
State Description
Unregistered The CBSD is not yet approved or registered by the SAS or is deregistered.
Registered The CBSD is registered with SAS but does not have any grants.
Authorized The CBSD is authorized to transmit through the grant.
Granted The CBSD received the grant, but it is not currently heartbeating on the grant.
Grant-Suspended The grant is suspended when Incumbent or PAL status has changed temporarily. Then,
the CBSD can wait until the grant is re-enabled, or relinquish the grant and request
another.
NOTE: The actions described in this section can only be performed on the same device types
(eNBs or CPEs).
60 | P a g e
SAS Deployment User Guide
61 | P a g e
SAS Deployment User Guide
62 | P a g e
SAS Deployment User Guide
SAS Registration Type Select Single-Step or Multi-Step method to register the eNB with the SAS vendor.
Either A (Indoor) or B (Outdoor) according to the eNB’s designation. The main difference
category between these categories is the power limit. The eNB is typically Category B.
See Table 4-8 for more information.
Enter the user ID provided by your SAS vendor and that is associated with this SAS-enabled
eNB.
userId
The range is 0 to 256 characters (using upper-case letters A–Z, lower-case letters a–z, and
digits 0–9).
Optional: Parameter that is useful to identify the PAL license under which the operator is
deploying a CBSD.
callSign The parameter is not necessary to configure the GAA spectrum (3550–3700 MHz).
The range is 0 to 256 characters (using upper-case letters A–Z, lower-case letters a–z, and
digits 0–9).
Either A (Indoor) or B (Outdoor) according to the eNB’s designation. The main difference
category between these categories is the power limit. The eNB is typically Category B.
See Table 4-8 for more information.
63 | P a g e
SAS Deployment User Guide
Parameter Description
Enter the user ID provided by your SAS vendor and that is associated with this SAS-enabled
eNB.
userId
The range is 0 to 256 characters (using upper-case letters A–Z, lower-case letters a–z, and
digits 0–9).
Latitude of the eNB’s location. Select auto to autofill the latitude based on GPS data;
latitude otherwise, enter the latitude.
Range: -90.000000 to 90.000000).
Longitude of the eNB’s location. Select auto to autofill the longitude based on GPS data;
longitude otherwise, enter the longitude.
Range: -180.000000 to 180.000000).
Antenna Gain Set the eNB’s antenna gain. Range: -5–30 dBi.
antennaAzimuth Enter the antenna azimuth, in degrees. Default is 180°. Range: 0–359°.
antennaDowntilt Enter the degrees of antenna downtilt. Default is 5°. Range: -90°–90°.
antennaBeamwidth Enter the degrees of antenna beamwidth. Default is 65°. Range: 0–360°.
Optional: Parameter that is useful to identify the PAL license under which the operator is
deploying a CBSD. The parameter is not necessary to configure the GAA spectrum (3550–
callSign 3700 MHz).
The range is 0– 256 characters (using upper-case letters A–Z, lower-case letters a–z, and
digits 0–9).
64 | P a g e
SAS Deployment User Guide
Parameter Description
Optional: You must enter a group ID if using a group type. You cannot leave the groupID
field blank when using a group type. Instead, specify the group ID using letters, numbers,
or special characters. When you add the ID, it displays beneath this field.
groupID
Enter the Certified Professional Installer’s name. Use an underscore to separate first and
cpiName
last names; you cannot use a space in this field.
Loaded: Indicates that the CPI certificate is already uploaded from the
CPI certstore
System > CertStore sub-menu.
Select to upload or change the CPI certificate. You can also use the
add/change CPI cert System > CertStore menu to upload the certificate.
65 | P a g e
SAS Deployment User Guide
Preset field - cannot be configured at this time. Either Time Division Duplexing (TDD) or
Duplex Mode
Frequency Division Duplexing (FDD) depending on model and country.
Single Carrier: The eNB supports only one cell in this mode.
Dual-Carrier: The eNB supports two cells in this mode. Cell1 and Cell2 must both be
configured in Basic Setting > Quick Setting because the two carriers are independent of
Carrier Mode each other.
Carrier Aggregation: The eNB supports one cell in this mode, but the bandwidth and
throughput are twice what is possible in Single Carrier mode. The primary carrier is
responsible for signaling and services, while the second carrier is responsible for services
only.
Carrier Enables the eNB to broadcast. If the eNB is set to DC or CA mode, both carriers are enabled.
Activated/Deactivated
Used to assign the interface connected to the MME. The interface should be selected from
Quick Interface Binding among the network interfaces. Default is the WAN interface, but the VLAN interface can
also be used.
Shows HaloB status (ON or OFF) as set in BTS Settings > Core Network.
HaloB
NOTE: This field will not display if Cloud EPC function is ON.
The Baicells CloudCore Evolved Packet Core (EPC) is either ON or OFF. When you enable it
(ON), the fields for TAC, S1 Link Port, PLMN, MME IP (Quick Setting pane), and CELL ID (Cell
Quick Setting pane) are automatically assigned and will become greyed out. When you
Cloud EPC
disable the Cloud EPC setting (OFF), the greyed-out fields are unlocked. Also, when you
change the Cloud EPC setting, a reboot of the eNB is required.
Track Area Code (TAC) for where the eNB is located. The TAC is used to determine the range
TAC
of the paging information. Use a number between 1–65535. The default is 1.
The connection mode of the S1 interface between the eNB and the core network.
S1 Connection Mode • One: The eNB connects only to the first MME.
66 | P a g e
SAS Deployment User Guide
Parameter Description
The numerical identifier for the operator’s Public Land Mobile Network (PLMN) for this cell.
PLMN Must be a 5- or 6-digit number. If you are using the Baicells CloudCore, you must enter
PLMN = 314030. When you configure the PLMN, it displays in the PLMN ID list.
The IP address of the associated MME, which is identical to the IP address of the MME at
the core network side. If you’re using the Baicells CloudCore, you must set the MME IP
address fields to 10.3.0.9 and 10.5.0.9. When you configure the MME, it displays in the
MME IP
table below the MME IP field.
NOTE: The field will not display in HaloB mode or when IP MME Pool is
enabled.
The eNB’s operating frequency band is auto-selected based on the hardware model. If SAS
Band
is enabled, the band is assigned by the SAS vendor, and the field is greyed out.
For TDD mode, the channel bandwidth the eNB can use: 5, 10, 15, or 20 MHz. Applies to
both uplink and downlink. The default is 20 MHz.
Bandwidth
Example for B48: 55240 (3550 MHz) to 56739 (3700 MHz)
If SAS is enabled, the bandwidth is assigned by the SAS vendor, and the field is greyed out.
The eNB’s operating frequency (MHz) is selected by the operator. Range depends on the
eNB hardware model, country code, and whether SAS is enabled or not.
Frequency(MHz)
Example for B48: 55240 (3550 MHz) to 56739 (3700 MHz)
If SAS is enabled, the frequency is assigned by the SAS vendor, and the field is greyed out.
67 | P a g e
SAS Deployment User Guide
Parameter Description
This standard LTE setting pertains to synchronization of downlink and uplink timing. The
guard period between switching from DL to UL or UL to DL determines the maximum
Special SubFrame Patterns
supportable cell size. The guard period must be large enough to cover the propagation delay
of DL interferers. The range is either 5 or 7. The default setting is 7.
Physical Cell Identifier (PCI) allocated by the operator. The range is 0–503. PCI is an essential
PCI Layer 1 cell identity for each cell site in the network. Planning PCIs is crucial for QoS.
NOTE: Baicells does not use and does not work with PCI 0.
Cell ID Unique identification number for the Cell ID. The range is 0–268435455.
Turn ON or OFF the eNB’s RF antenna to allow it to transmit and receive (ON) or to keep it
RF Status
from transmitting and receiving (OFF). The default is OFF.
Output power on each port, typically left with the default values
(30 dBm x 2 = 33 dBm). Every 3 dB doubles the power. This field can be used in situations
where you need to reduce the output power, such as testing the eNB before installing it on
Power Modify
a tower; restricting the eNB output to reduce interference with other eNBs in the same
geographical area; or staying within Effective Isotropic Radiated Power (EIRP) rules. If SAS
is enabled, the bandwidth is assigned by the SAS vendor.
NOTE: The SAS Preferred Setting pane and all the associated fields will not display unless SAS is
enabled.
SAS Registration Type There are two types of SAS registration: Single-Step and Multi-Step.
Used to configure preferred frequencies, channel bandwidth, and power when SAS is
Frequency Selection enabled. After receiving channel availability from SAS, the DP uses the frequency selection
Logic logic setting to calculate CBRS channel selection based on the order of importance
identified. The default is “Power, Bandwidth, Frequency”.
Preferred Bandwidth Used to set the preferred bandwidth for the eNB.
68 | P a g e
SAS Deployment User Guide
Parameter Description
Used to set the preferred power for the eNB. The preferred power is the total TX power (in
dBm) being transmitted per carrier. The power can be set to the maximum transmitting
Preferred Power
power supported by the eNB in increments of 1 dBm. The range is 0 dBm to 30 dBm.
The default is 2 x 30 dBm.
Used to set the preferred frequency for the eNB. More than one preferred frequency can
Preferred Frequency be added, and each frequency’s priority can be set. If the eNB is set to Dual Carrier (DC)/split
mode, the preferred frequency is set for the Primary Cell (Cell1) and Secondary Cell (Cell2).
Used to designate channel reuse for Dual Carrier (DC) mode so that both Cell1 and Cell2 are
forced to use the same frequency, which is the frequency configured for Cell1. If the
Channel Reuse checkbox is selected, then only the Preferred Frequency field for Cell1 should
Channel Reuse (Dual display in Basic Setting > Quick Setting.
Carrier mode only)
NOTE: This field and checkbox will not display unless SAS is enabled and
the Carrier Mode is set to Dual-Carrier.
NOTE: The Install Param Config pane and all the associated fields will not display unless SAS is enabled.
Either A or B, according to the eNB’s designation. The main difference between these
CBSD Category
categories is the power limit. The eNB is typically Category B.
Enter a user ID, which is provided by your SAS vendor and is associated with this SAS-
enabled eNB.
User ID
The range is 0–256 characters (using upper-case letters A–Z, lower-case letters a–z, and
digits 0–9).
Optional: Parameter that is useful to identify the PAL license under which the operator is
deploying a CBSD. The parameter is not necessary to configure for the GAA spectrum
Call Sign (3550–3700 MHz).
69 | P a g e
SAS Deployment User Guide
Parameter Description
NOTE: The Cell1 Install param Config pane and all the associated fields will not display unless SAS is
enabled.
Antenna Gain Set the primary cell eNB antenna gain in a two-carrier configuration.
Range: -5–30 dB.
NOTE: The Cell2 Install Param Config pane and all the associated fields will not display unless SAS is
enabled.
Antenna Gain Set the secondary cell eNB antenna gain in a two-carrier configuration.
Range: -5–30 dB.
NOTE: The Install Param Config pane and all the associated fields will not display unless SAS is enabled.
CBSD Category Either A or B, according to the eNB’s designation. The main difference between these
categories is the power limit. The eNB is typically Category B.
See Table 4-8 for more information.
Enter a user ID, which is provided by your SAS vendor and is associated with this SAS-
User ID enabled eNB. The range is 0–256 characters (using upper-case letters A–Z, lower-case
letters a–z, and digits 0–9).
The eNB’s FCC certification number for the device. The range is 0–19 characters (using
FCC ID
upper-case letters A–Z, lower-case letters a–z, and digits 0–9).
Automatic – parameters are auto-filled (OMC pulls the info from the eNB).
Manual – operator manually enters parameters.
NOTE: This field displays here in the Install Param Config pane when the
Automatic/Manual SAS registration type is Single-Step and the Carrier Mode is set
to Single Carrier or Carrier Aggregation. This field displays in the
Cell1 Install Param Config pane and the Cell2 Install Param
Config pane when the SAS registration type is Single-Step and
the Carrier Mode is set to Dual Carrier.
70 | P a g e
SAS Deployment User Guide
Parameter Description
Deployment Select Outdoor or Indoor to indicate whether the eNB is an Indoor or Outdoor unit.
Optional: Parameter that is useful to identify the PAL license under which the operator is
deploying a CBSD. The parameter is not necessary to configure for the GAA spectrum
Call Sign
(3550–3700 MHz). The range is 0–256 characters (using upper-case letters A–Z, lower-case
letters a–z, and digits 0–9).
Optional: You must enter a group ID if using a group type. When using a group type, you
cannot leave the group ID field blank. Specify the group ID using letters, numbers, or special
characters. When you add the ID, it displays beneath this field.
Group ID
NOTE: The Cell1 Install Param Config pane and all the associated fields will not display unless SAS is
enabled.
Automatic – parameters are auto-filled (OMC pulls the info from the eNB).
Manual – operator manually enters parameters.
NOTE: This field displays here in the Cell1 Install Param Config pane when
Automatic/Manual
the SAS registration type is Single-Step and the Carrier Mode is
set to Dual Carrier. This field displays in the Install Param Config
pane when the SAS registration type is Single-Step and the
Carrier Mode is set to Single Carrier or Carrier Aggregation.
Latitude of the primary cell eNB’s location in a two-carrier configuration. Select auto to
Latitude autofill the latitude based on GPS data; otherwise, enter the latitude.
The range is -90.000000–90.000000.
Longitude of the primary cell eNB’s location in a two-carrier configuration. Select auto to
Longitude autofill the longitude based on GPS data; otherwise, enter the longitude.
The range is -180.000000–180.000000.
71 | P a g e
SAS Deployment User Guide
Parameter Description
Enter the primary cell antenna height, in meters, in a two-carrier configuration. Select auto
to autofill the antenna height.
Height Range: 0–8848 feet.
NOTE: You can express the height in feet if that is easier. The SAS converts feet to meters.
NOTE: The Cell2 Install Param Config pane and all the associated fields will not display unless SAS is
enabled.
Automatic – parameters are auto-filled (OMC pulls the info from the eNB).
Manual – operator manually enters parameters.
NOTE: This field displays here in the Cell2 Install Param Config pane when
Automatic/Manual
the SAS registration type is Single-Step and the Carrier Mode is
set to Dual Carrier. This field displays in the Install Param Config
pane when the SAS registration type is Single-Step and the
Carrier Mode is set to Single Carrier or Carrier Aggregation.
Enter the secondary cell antenna height, in meters, in a two-carrier configuration. Select
auto to autofill the antenna height. Range: 0–8848 feet.
Height
NOTE: You can express the height in feet if that is easier. The SAS converts
feet to meters.
72 | P a g e
SAS Deployment User Guide
Parameter Description
Enter the primary cell date and time of installation in a two-carrier configuration:
Install Cert Time yyyy-mm-ddThh:mm:ssZ.
Select auto to autofill the primary cell installation date and time.
Cell2 CPI Info Pane
Enter the secondary cell date and time of installation in a two-carrier configuration:
Install Cert Time yyyy-mm-ddThh:mm:ssZ.
Select auto to autofill the secondary cell installation date and time.
Displays the CPI’s certificate in the Certificate List if it has been uploaded. Displays Missing
CPI Certificate
when the certificate is missing (not uploaded).
Certificate file types are p12 and pem. One of the pem formats is pkcs8. If you select the
p12 File p12 File checkbox, you must input a password. No other file type requires inputting a
password.
73 | P a g e
SAS Deployment User Guide
74 | P a g e
SAS Deployment User Guide
Parameter Description
Longitude of the eNB’s location. Select auto to autofill the longitude based on GPS
Longitude data; otherwise, enter the longitude.
Range: -180.000000 to 180.000000).
Enter the antenna height in meters.
Height
Range: 0–300 meters.
HeightType Only Above Ground Level (AGL) can be selected.
indoorDeployment Indicate whether the eNB is an Indoor or Outdoor (default) unit.
Antenna Gain Set the eNB’s antenna gain. Range: -5–30 dBi.
Enter the antenna azimuth, in degrees.
Antenna Azimuth
Default is 180°. Range: 0–359°.
Enter the degrees of antenna downtilt.
Antenna Downtilt
Default is 5°. Range: -90°–90°.
Enter the degrees of antenna beamwidth.
Antenna Beamwidth
Default is 65°. Range: 0–360°.
Optional: Parameter that is useful to identify the PAL license under which the
operator is deploying a CBSD. The parameter is not necessary to configure the GAA
Call Sign spectrum (3550–3700 MHz).
The range is 0– 256 characters (using upper-case letters A–Z, lower-case letters a–z,
and digits 0–9).
Optional: Only INTERFERENCE_COORDINATION can be selected at this time. Adding a
Group is also optional at this time. CBSD grouping is currently not being used by SAS
Group Type
vendors but will be used in the future when General Authorized Access (GAA)
coexistence is introduced.
Optional: You must enter a group ID if using a group type. You cannot leave the
groupID field blank when using a group type. Instead, specify the group ID using
letters, numbers, or special characters. When you add the ID, it displays beneath this
field.
Group Id
75 | P a g e
SAS Deployment User Guide
Parameter Description
Select “Auto” to enter the date and time of installation automatically:
Install Cert Time
yyyy-mm-ddThh:mm:ssZ
CPI Certstore Pane
Displays the CPI’s certificate upload status.
• Loaded: Indicates that the CPI certificate is already uploaded from the
CPI Certstore
System > CertStore sub-menu.
• Missing: Indicates the CPI certificate is missing (not uploaded).
Select to upload or change the CPI certificate. You can also use the
Add/Change CPI Cert
System > CertStore menu to upload the certificate.
76 | P a g e
SAS Deployment User Guide
eNB CBSDs
CPE CBSDs
EG3015M-M30- 2AG32EG3015MM30HP
AtomID15M-HP 5 360 A 30
HP
77 | P a g e