0% found this document useful (0 votes)
706 views

BreezeVIEW - CBRS Deployment and Operation

This document provides an overview of BreezeVIEW software for managing CBRS deployments. It describes the key components of the CBRS solution including CBSDs and Domain Proxies. It also outlines the procedures for commercial deployment of CBSDs including ICD requirements, configuration parameters, and training from SAS providers. The document explains how BreezeVIEW is used to manage and monitor SAS servers and CBSDs through features like configuration, inventory, actions, status checking, and alarms/events. It includes extensions with SAS error codes and CBRS acronym definitions.

Uploaded by

openid_dr4OPAdE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
706 views

BreezeVIEW - CBRS Deployment and Operation

This document provides an overview of BreezeVIEW software for managing CBRS deployments. It describes the key components of the CBRS solution including CBSDs and Domain Proxies. It also outlines the procedures for commercial deployment of CBSDs including ICD requirements, configuration parameters, and training from SAS providers. The document explains how BreezeVIEW is used to manage and monitor SAS servers and CBSDs through features like configuration, inventory, actions, status checking, and alarms/events. It includes extensions with SAS error codes and CBRS acronym definitions.

Uploaded by

openid_dr4OPAdE
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 45

BreezeVIEW

CBRS Deployment and Operation

March. 2020
Document Edition: 1.3

Page 1 of 45
Revision History

Revision: Description:
1.2 ICD Configuration Parameters:
1- A clarification is added: Certificate File Name must be initiated as well
2- Add “Client certificate Password” parameter

Table of Contents
REVISION HISTORY ......................................................................................................................................................................2
TABLE OF CONTENTS ...................................................................................................................................................................2
TABLE OF FIGURES .......................................................................................................................................................................3
DOCUMENT INFORMATION AND OVERVIEW ...............................................................................................................................5
CBRS SOLUTION INTRODUCTION .................................................................................................................................................5
CBRS SOLUTION COMPONENTS ..............................................................................................................................................................6
CBSD’S PROCEDURES ...........................................................................................................................................................................7
DOMAIN-PROXY (DP) ...........................................................................................................................................................................8
CBRS COMMERCIAL DEPLOYMENT ..............................................................................................................................................9
TELRAD’S PORTFOLIO ............................................................................................................................................................................9
ICD REQUIREMENTS AND PROCEDURES ..................................................................................................................................................10
ICD Environment .......................................................................................................................................................................10
Deployment Procedures ............................................................................................................................................................10
Deployment Considerations ......................................................................................................................................................10
ICD CONFIGURATION PARAMETERS .......................................................................................................................................................11
CPI TRAINING ....................................................................................................................................................................................13
Google SAS ................................................................................................................................................................................13
Federated Wireless (FW) SAS ....................................................................................................................................................14
CommScope SAS .......................................................................................................................................................................15
CBRS MANAGEMENT VIA BREEZEVIEW ......................................................................................................................................15
SAS SERVER PROPERTIES .....................................................................................................................................................................16
Configuration Parameters ........................................................................................................................................................16
Actions ......................................................................................................................................................................................16
SAS SERVER MANAGEMENT AND MONITORING .......................................................................................................................................17
Enable CBRS Feature .................................................................................................................................................................17
Page 2 of 45
Configure the SAS Server Parameters .......................................................................................................................................17
CBSD PROPERTIES .............................................................................................................................................................................19
Configuration Parameters ........................................................................................................................................................19
Inventory Parameters ...............................................................................................................................................................20
Actions ......................................................................................................................................................................................21
CBSD Status...............................................................................................................................................................................22
CBSD MANAGEMENT AND MONITORING ...............................................................................................................................................23
CBSDs Summary widget ............................................................................................................................................................23
CBSDs List ..................................................................................................................................................................................24
CBSD Details..............................................................................................................................................................................27
CBSD Actions .............................................................................................................................................................................30
Export / Import CBSDs ..............................................................................................................................................................31
CBSD Audit Log .........................................................................................................................................................................33
Alarms & Events ........................................................................................................................................................................34
BreezeVIEW CLI Commands ......................................................................................................................................................35
EXTENSIONS ..............................................................................................................................................................................37
SAS PROCEDURES ERROR CODES ...........................................................................................................................................................37
WINNFORUM CBRS ACRONYM AND DEFINITIONS ....................................................................................................................................38
Acronym ....................................................................................................................................................................................38
Definitions .................................................................................................................................................................................40

Table of Figures
Figure 1: Telrad's Solution Architecture .................................................................................................................................... 6
Figure 2: BreezeVIEW Settings Screen ..................................................................................................................................... 17
Figure 3: Navigate to SAS Server Settings Screen .................................................................................................................... 18
Figure 4: SAS Server Settings Screen ....................................................................................................................................... 19
Figure 5: CBSDs Screen, example 1.......................................................................................................................................... 23
Figure 6: CBSDs Screen, example 2.......................................................................................................................................... 23
Figure 7: CBSDs Network Summary widget ............................................................................................................................. 23
Figure 8: CBSDs List, Default View ........................................................................................................................................... 24
Figure 9: Column Selection Screen .......................................................................................................................................... 24
Figure 10: Functional Buttons .................................................................................................................................................. 25
Figure 11: Add eNB CBSD......................................................................................................................................................... 25
Figure 12: Add eNB CBSD Screen ............................................................................................................................................. 26
Figure 13: Add UE CBSD ........................................................................................................................................................... 26
Page 3 of 45
Figure 14: Add UE CBSD Screen ............................................................................................................................................... 27
Figure 15: eNB CBSD Details .................................................................................................................................................... 28
Figure 16:UE CBSD Details ....................................................................................................................................................... 28
Figure 17: eNB and UE Inventory & State Area ....................................................................................................................... 29
Figure 18: eNB CBSD Configuration Area................................................................................................................................. 30
Figure 19: UE CBSD Configuration Area ................................................................................................................................... 30
Figure 20: Export / Import CBSDs List Button .......................................................................................................................... 31
Figure 21: CBSD Audit Log ....................................................................................................................................................... 33
Figure 22: CBSD Audit Log example. ........................................................................................................................................ 34
Figure 23: CBSD's Alarms, Example 1 ...................................................................................................................................... 34
Figure 24: CBSD's Alarms, Example 2 ...................................................................................................................................... 34
Figure 25: CBSD's Alarms, Example 3 ...................................................................................................................................... 35

Page 4 of 45
Document Information and Overview
This document describes how to integrate, deploy and operate CBRS (Citizen Broadband Radio Service)
components in the operator network.

This documents describes the specific aspects of CBRS components, procedures and how to use
BreezeVIEW WebUI and CLI for configuration and monitoring.

Main Paragraphs:

• CBRS Solution Introduction


o CBRS Solution Components
o CBSD’s Procedures
o Domain Proxy
• CBRS Commercial Deployment
o Telrad’s Specific Component
o ICD Requirements and Procedures
 ICD Environment
 Deployment Procedures
 Deployment Considerations
o Initial Configuration Parameters
o SAS Certified Profession Installer (CPI) Training
• CBRS Management via BreezeVIEW
• Extensions

CBRS Solution Introduction


CBRS is 150 MHz of spectrum – ranging from 3550 – 3700 MHz – in the 3.5 GHz band. Used by the U.S
government and other entities.
In April 2015, the FCC established Citizen Broadband Radio Service (CBRS) for shared commercial use of
that band. Some of this spectrum will continue to be used by the United States government for radar
systems, but will be available for others where not needed by the Navy.
When operating in shared spectrum, users with different levels of priority have access to the band, there
are 3 tiers of users in CBRS:
 Tier 1 (higher priority): Naval aircraft carriers, Fixed Satellite Stations, GWBL/GWPZ
 Tier 2: Priority Access Licensee (PAL)
 Tier 3: General Authorized Access (GAA)

Page 5 of 45
CBRS Solution Components
SAS - Spectrum Access System:
a system that authorizes and manages use of spectrum for the Citizens Broadband Radio Service.
SAS determines the available frequencies at a given geographic location for CBSDs and communicate that
information to the SAS manager.
1- Determine the maximum transmission power level for CBSDs at a given location and communicate that
information to the SAS manager.
2- Register and authenticate the identification information and location of CBSDs.
3- Ensure secure and reliable transmission of information between the SAS and Domain-Proxy

CBSD - Citizens Broadband Radio Service Device:


Fixed Stations, or networks of such stations, that operate on a Priority Access or General Authorized Access
basis in the Citizens Broadband Radio Service consistent with this rule part.
In Telrad’s solution, CBSDs are eNBs and UEs.
A CBDS shall operate at or below the maximum power level and frequencies as authorized by the SAS.

DP - Domain-Proxy:
serves as SAS managing intermediary such that the SAS communicates directly with the Domain-Proxy
rather than with each individual CBSD.
BreezeVIEW acts as a Domain-Proxy and supports the following main functions:
1- Accept a set of one or more available channels and select channels for use by specific CBSDs, and
configure the CBSDs respectively.
2- Receive confirmation of channel assignment from SAS, manage CBSDs registration and authorization
with the SAS
3- Perform bidirectional bulk CBSD registration and directive processing.

Figure 1: Telrad's Solution Architecture

Page 6 of 45
CBSD’s Procedures
A CBRS device (CBSD) needs authorization from the SAS before it starts to transmit in the CBRS band.
The Domain-Proxy communicate with the SAS using the SAS-CBSD API.

SAS supports the following procedures for communicating with the Domain-Proxy.
 CBSD Registration
 CBSD Grant Request
 CBSD Heartbeat
 CBSD Relinquish
 CBSD Deregister

Each of these procedures consists of a Request/Response message exchange between the BreezeVIEW
Domain-Proxy and the SAS, the Domain-Proxy initiates the Request and the SAS sending a Response with
appropriate Error Code.

CBSD Registration
A CBSD shall be registered by SAS to be able to make requests for Spectrum Grants (service transmission).
As part of the CBSD Registration procedure, Domain-Proxy provides the SAS with its device specific
information, like device type, serial no, FCC ID, etc. as well as its installation information like location,
height, deployment type, etc.
The SAS validates the CBSD authenticity and registration information to verify the correctness of the data
provided by the Domain-Proxy and whether the CBSD is blacklisted and has to be denied service.

CBSD Grant
The Grant procedure is used for a Registered CBSD to request access for the spectrum managed by the SAS.
This procedure can only be performed after a successful registration of the CBSD with the SAS.
The Grant Request should include:
1- The CBSD frequency range it wishes to operate upon.
2- The desired maximum TX power.
On successful operation, SAS sends a successful Grant Response with information on the duration of the
Grant validity and allowed peak transmit power, and the Heartbeat Duration.

CBSD Heartbeat
The Heartbeat procedure is used to maintain the validity of the CBSD assigned Grants with the SAS.
Heartbeat request informs SAS that the CBSD still using the allocated spectrum, and allows SAS to suspend
or terminate the grant.
The SAS uses the HB Response message to inform a state change, such:
 Grant Expiry time
 Transmit Time
 Grant Status: Termination or Suspension.

Page 7 of 45
CBSD Deregister
Deregistration Procedure is used by the BreezeVIEW to deregister a CBSD from the SAS.

CBSD Relinquish
The Spectrum Relinquishment procedure used by the Domain-Proxy to relinquish an assigned/active Grant
for a CBSD. The Domain-Proxy sends the Relinquishment Request message to the SAS to inform the SAS
that the CBSD no longer requires use of the frequency segment assigned in the Grant.

BreezeVIEW Domain-Proxy may initiate this request for the following state transitions:
1- CBSD is no longer reachable/managed.
2- CBSD is no longer going to transmit on the frequency segment assigned in the Grant.
3- SAS has instructed to vacate the frequency segment assigned in the Grant.
4- Switching CBSD to a different operating frequency

Domain-Proxy (DP)
BreezeVIEW acts as a Domain-Proxy between SAS and the Devices (eNBs, UEs).

It communicates with the SAS, accepts instructions such a grant confirmation or denial for requested
spectrum, and configure the CBSDs (eNBs, UEs) respectively.

The Domain-Proxy maintains a state machine algorithm per CBSD, and provides information about the
CBSD state and statuses. CBSD state may be affected by variant causes, such SAS instructions, CBSD HW
state, connectivity’s state and others.

The Domain-Proxy automatically configures eNB and UE devices following SAS instructions, user
configuration, and the state machine algorithm.
For example, when receiving a Grant for eNB CBSD, SAS manager shall configure the Central Frequency,
Max TX power and activate Start Transmission operation, or alternatively, stops eNB transmission if Grant
is rejected.

Page 8 of 45
CBRS Commercial Deployment

Telrad’s Portfolio
Telrad’s portfolio of products including the following components which are specifically designed to
provide a complete CBRS solution.
Device name Model Name FCC ID
BreezeCompact 1000 3.x CMP.XT-BS-3.4-3.7 ARA-CMP1K3X96
CPE 9000 3.x CPE9000-PRO-1D-3.x ARA-CPE9000PRO3X
CPE 8100 3.x CPE8100-PRO-1D-3.x ARA-CPE81003X96
Domain Proxy BreezeVIEW

Telrad performed full IOT tests with the following Spectrum Access Systems (SAS) vendors:
• Federated Wireless SAS
• Google SAS
• CommScope SAS

CPE SW Releases:

• CPE8100
The CPE firmware that support CBRS is FW1937 and up.
V1.3.2P0_R1937 – non CBRS
V1.3.4P8_R1937 – CBRS
• CPE9000:
Before you migrate the CPE to CBRS you should upgrade the CPE to FW157 and up (FW-
Telrad_CPE9000_01.01.02.157.ipk). From this FW the CPE is ready to support CBRS.

There are 2 files:


1. Enable CBRS (prov-Telrad_CBRS_enable_01.01.02.157.ipk).
2. Disable CBRS (prov-Telrad_CBRS_disable_01.01.02.157.ipk).
To migrate the CPE to CBRS mode, you should only upload to CPE the CBRS enable file (prov-
Telrad_CBRS_enable).
If the action succeeded you should see in CPE view the CBRS mode ON.

Page 9 of 45
ICD Requirements and Procedures
ICD Environment

The Initial Commercial Deployment (ICD) is a short-term, geographically limited commercial deployment.
The goal of the ICD is for Spectrum Access Server (SAS) administrators to prove that their SAS service
complies with the FCC rules in a real-world setting.

 ICD is the final step in the FCC’s SAS certification process. ICD is expected to last 60-90 days.
The first 30 days is the “compliance period” and the SAS and active CBSDs will be closely managed and
reported on. Once completed, FCC reporting is reduced, and Operators can grow their CBSD
deployments in numbers and geography, based on their desired schedule.
 FCC requires CBSD devices to be (FCC lab) certified.
 ICD Requires operation under the FCC part 96 CBRS rules.
 Once the ICD starts, the Commercial SAS will no longer support Operator STAs.

Deployment Procedures

To access the GAA unlicensed spectrum before it is commercially available, the operator should take part in
the ICD.
1- It is necessary to negotiate with SAS vendor to access the spectrum and ensure equipment compliance.

2- SAS vendor shall provide an access to the ICD Commercial Web Portal, the operator should use it for
ICD provisioning.

3- SAS vendor shall provide an access to the SAS Server, the operator should register the Domain-Proxy in
the SAS Server.

4- Certified Professional Installers (CPI) should use his digital credentials to sign installation parameters for
all CBSDs devices (mandatory for Category B CBSD registrations).
a. An administrator account should be established on the Web Portal once a sales agreement is
completed and the contact information for the Administrator is provided.
b. CPI certificate conditioned by passing a CPI training course.
c. Using the Portal, CPI user shall enter the CBSDs specific installation parameters needed for
registration.

Deployment Considerations

The SAS fully implements the required WInnForum requirements designed meet FCC requirements to
protect Incumbents.

1. Performs nightly Coordinated Periodic Activities among SASes (CPAS), this process runs daily

 Federated SAS: 24 Hour Interval: Start Midnight PST; End 3 AM PST


Page 10 of 45
 Google SAS: CPAS times to be provided by Google

 CommScope SAS: CPAS times to be provided by CommScope

In this process the SAS perform synchronization with FCC databases and exchange grant information
with any other active SAS.
2. Support of Dynamic Protection Area (DPA) for Federal Incumbent.
3. Current FCC entries for FSS and GFBL protection areas loaded into the SAS database and refreshed
during nightly CPAS.
4. Federal defined Quiet zones.

The impact of these required protection methods is that the SAS may not be able to authorize a grant
request immediately.
The DP may have to wait for the CPAS process to complete before the SAS can provide the DP a response.
Since CPAS runs once a day, a CBSD could wait between 1 and 22 hours for this to occur.

Coordination between Grant request time and CPAS process execution time will decrease the waiting time.

ICD Configuration Parameters


The following required for establishing a connection between BreezeVIEW DP and SAS Server:

SAS Server URL URL used to access the SAS server

Federated: https://spectrum-connect.federatedwireless.com/v1.2
Google: https://sas.goog/v1.2/
CommScope: https://prod.sascms-prod.net:8443

Protocol Version version of the SAS Server protocol v1.2 (default)

User ID CBSD User ID used for registering to SAS (UR-ID) – User ID value is provided by the SAS
vendor

Each Operator organization / account should have a unique User ID (UR-ID).


This UR-ID associates a CBSD with a specific Operator account on the SAS for
management and subscription usage billing.

Page 11 of 45
Server Certificate WInnForum implemented a mutual, multi-factor TLS authentication method to ensure
CBSD-SAS communication is secure for each message transaction between a CBSD and
the SAS. The ICD Commercial Spectrum Controller enforces WINNF CBR
S PKI Certificate Policy. Each SAS-Administrator has a registered CA-Root certificate
and each CBSD / Domain Proxy must have a registered CA-Root certificate.

The SAS vendor determines which Server Certificate to use - Provided by Telrad

Federated SAS uses INSTA Server Certificate:


The INSTA Production Intermediate SAS certificate and INSTA Production SAS Leaf
certificate will be sent from the SAS to a CBSD / Domain Proxy for the ICD Commercial
SAS.
To obtain the INSTA Production Root certificate for the ICD Commercial Spectrum
Controller,
it is available for download from WINNF / INSTA for Federated Wireless SAS at this
URL: https://www.insta.fi/en/services/cyber-security/cbrs-certificates

BreezeVIEW Server certificate path and name: the certificate file should be placed in
the BreezeVIEW Linux server under “/opt/lte/certificates/” folder

Server to be checked by BreezeVIEW when validating server certificate; this is needed


Distinguish Name because sometimes the DN sent by the SAS Server inside the certificate does not
(DN) match the hostname used in Server URL. This parameter provides the operator with
an alternative way to validate the server certificate in a case there is a DN mismatch
he can set here a restriction to what DN he accepts from the SAS server to accomplish
mutual authentication

Federated: federatedwireless.com
Google: to be provided by Google
CommScope: CN is prod.sascms-prod.net
DN field includes the following:
CN = prod.sascms-prod.net
OU = WInnForum SAS Provider Certificate
O = CommScope
C = US

Client Certificate Client certificate path and name - Provided by Telrad (obtain from INSTA, which is an
authorized certificate provider)

Client certificate the certificate file should be located in the BreezeVIEW Linux server under
path and name “/opt/lte/certificates/ <Certificate File Name>”

note. Certificate File Name must be initiated


Client certificate password used to decrypt client private key - Provided by Telrad
Password

Page 12 of 45
CPI Training
SAS Vendors provide access to their Web Portal (GUI) instance, the operator should use it for CBSDs
provisioning.
Certified Professional Installers (CPI) uses their digital credentials to sign installation parameters for all
CBSDs devices (mandatory for Category B CBSD registrations).

Google SAS

CPI Certified Training Google CPI online training on Coursera, after passing the online certification
course exam, you will automatically receive your CPI credentials, be registered in the
WinnForum CPI database, and can start installing devices

https://www.google.com/get/spectrumdatabase/cpi/

CBRS Professional If you want to learn about CBRS in general, but don’t need to be certified, check
Training course out our CBRS Professional Training course:

https://www.coursera.org/learn/google-cbrs-professional-training

Learn how to Manage Learn how to manage CBRS with Google SAS portal:
CBRDs with SAS
Portal (Guide) https://support.google.com/sas/?hl=iw#topic=9344791

SAS Portal A web-based application you can use for multi-step registration, CPI validation
and view the status of your CBSDs.

https://wirelessconnectivity.google.com/sas

SAS Portal API A set of APIs you can use to integrate your application with SAS. Check the
documentation at https://developers.google.com/spectrum-access-system

SAS Server URL Your CBSDs need to connect to https://sas.goog/v1.2/ to communicate with the
SAS

SAS Certificates All WinnForum root CA certificates may be used as a root of trust in the
CBSD/DP.

* Telrad will provide it


CPIs The SAS only accepts requests from CPIs accredited by approved CPI Training
Program Administrators (TPAs).
If the SAS rejects your CPI credentials, please reach out to your TPA to confirm
that your credentials are valid and have been uploaded to the WinnForum CPI
database.
Grant authorization All grants will be suspended until the official start of ICD. We're not allowed to
behavior authorize transmissions until that time.

Page 13 of 45
Incumbent protection All entities are protected according to FCC regulations. You'll find grant requests
rejected inside of exclusion zones, and may see grant adjustments or
suspensions.
Coordinated Periodic Runs nightly. You may see grant adjustments as more CBSDs come online.
Activities among
SASes (CPAS)

Federated Wireless (FW) SAS


CPI Certified Training To be provided by Federated
course
CBRS Professional To be provided by Federated
Training course
Learn how to Manage Learn how to manage CBRS with Federated SAS portal:
CBRDs with SAS Portal
https://partners.federatedwireless.com/articles/Docs/V1-5-4-Federated-Wireless-
(Guide) Spectrum-1-14-8-2019

SAS Portal Access to the ICD Commercial Spectrum Controller (SC) Web Portal (GUI) instance is
provided by Federated.
Spectrum Controller (SC) web-based application used for CBSDs registration,
CPI validation and view the status of your CBSDs

Reference the Spectrum Controller User’s Guide for additional details on the
various account types and usage. This document is available on the
Federated Wireless customer support portal:

Commercial SAS Portal URL: https://spectrum.federatedwireless.com

Commercial SAS Analytics URL: https://spectrum-analytics.federatedwireless.com/v1.5

Commercial SAS Reporting URL: https://spectrum-


reporting.federatedwireless.com/v1.5

Commercial SAS CPI URL: https://spectrum.federatedwireless.com:9998/v1.1

SAS Server URL Your CBSDs need to connect to the following URL for communicate with the SAS

https://spectrum-connect.federatedwireless.com/v1.2

SAS Certificates All WinnForum root CA certificates may be used as a root of trust in the CBSD/DP.

* Telrad will provide it

Page 14 of 45
CommScope SAS
CPI Certified Training CommScope CPI online training. CommScope’s course is focused on a practical
course approach to CPI training with simple explanations of key concepts and samples of
actual user interface screens for a Spectrum Access System.
after passing the online certification exam, you will automatically receive your CPI
credentials, be registered in the WinnForum CPI database, and can start installing
devices

https://www.commscope.com/solutions/cbrs-certified-professional-installer/

CBRS Professional If you want to learn about CBRS in general, but don’t need to be certified, check out our
Training course CBRS Professional Training course:

Interested in the training, but don't need the certification?


This course is available with no final exam and no certification, learn more:

https://commscope.netexam.com/catalog.html#:ct37836

Learn how to Manage Web site where a user would go to for documentation, training videos:
CBRDs with SAS Portal
www.myCommScope.com
(Guide)
SAS Server URL https://prod.sascms-prod.net:8443

SAS Certificates All WinnForum root CA certificates may be used as a root of trust in the CBSD/DP.

* Telrad will provide it

CBRS Management via BreezeVIEW


The following chapters describes the CBRS management and monitoring aspects in BreezeVIEW:
 SAS Server Properties

 SAS Server Management and Monitoring

 CBSD Properties

 CBSD Management and Monitoring

Page 15 of 45
SAS Server Properties
This chapter lists the SAS Server configuration, inventory and statuses parameters.
Next chapter will describe the view, operations and navigation for SAS Server management.
Configuration Parameters

Server URL URL used to access the SAS server

Protocol Version Version of the SAS Server protocol

User ID CBSD User ID used for registering to SAS

Server Certificate Server certificate path and name.


The certificate file should be placed in the BreezeVIEW Linux server under
“/opt/lte/certificates/”

The server certificate should be placed in BreezeVIEW Linux server under


/opt/lte/certificates folder and its path configured under
SASSettings/SASServer/SASServerCertificates

Server DN to be checked by BreezeVIEW when validating server certificate; this is needed


Distinguish Name because sometimes the DN sent by the SAS Server inside the certificate does not
match the hostname used in Server URL. This parameter provides the operator with
an alternative way to validate the server certificate in a case there is a DN mismatch
he can set here a restriction to what DN he accepts from the SAS server to
accomplish mutual authentication.

Server CRLs Optional local file containing Certificate Revocation List given by the Server
Certification Authority

Validate This option should be used to disable revocation and time validity checks for server
Certificate certificates – useful mostly for certificates missing revocation information such are
the certificates given to us by Federated.

Client Certificate Client certificate path and name

Client certificate The certificate file should be located in the BreezeVIEW Linux server under
path and name “/opt/lte/certificates/<certificate file name>”

Client certificate password used to decrypt client private key


Password

Actions

Check Connectivity – on click, the Domain-Proxy validate a connectivity with the SAS server.
Page 16 of 45
Once available, a status is presented: Connection Status: Connected/ Unreachable

SAS Server Management and Monitoring


SAS Server page is used for specifying the connection details and certificates files with the SAS server.
Prior SAS Server configuration verify that CBRS feature is enabled.

Enable CBRS Feature

1- Select the Settings from BreezeVIEW menu.


2- Select the Management Features tab.
3- Check the Enable CBRS check box for enabling CBRS Management

Figure 2: BreezeVIEW Settings Screen

Configure the SAS Server Parameters

1- Select the CBRS>SAS Server from BreezeVIEW menu. The SAS server page will be opened.

Page 17 of 45
Figure 3: Navigate to SAS Server Settings Screen

2- In the SAS server page, set the mandatory parameters:


a. Sever URL
b. Protocol Version
c. User ID
d. FCC ID
e. Server Certificate
f. Client Certificate

3- Click on the button ‘Check Connectivity’ and view the Connection Status: Connected/ Unreachable.
If the connection is Unreachable check the Notifications for viewing the error message that indicates
for the cause of the failure.

Page 18 of 45
Figure 4: SAS Server Settings Screen

CBSD Properties
This chapter details the CBSD configuration, inventory, status and state parameters.
Next chapters will describe the view, operations and navigation for CBSD’s management.
Configuration Parameters

Low Frequency (Mhz) The lowest frequency of the frequency ranges.

High Frequency (Mhz) The highest frequency of the frequency ranges.

Maximum EIRP (dBm/MHz) The maximum EIRP.


Value range: -137 and +37

Category Device Category of the CBSD.


Default: B ; Value range: A, B

Antenna Latitude Antenna Latitude of the CBSD antenna location

Page 19 of 45
Default: 38.0 ; Value range: -90..-90

Antenna Longitude Antenna Longitude of the CBSD antenna location


Default: -100 ; Value range: -180..-180

Antenna Height (meters) CBSD antenna height

Antenna Height Type The value should be “AGL” or “AMSL”. AGL height is measured relative to
the ground level. AMSL height is measured relative to the mean sea level.

Values: AMSL, AGL (default)

Antenna Horizontal A positive number in meters to indicate accuracy of CBSD antenna


Accuracy horizontal location if it’s smaller than the FCC requirement

Antenna Vertical Accuracy A positive number in meters to indicate accuracy of CBSD antenna vertical
location if it’s smaller than the FCC requirement

Antenna Deployment Whether the CBSD antenna is indoor or not.


True: indoor. False: outdoor

Values: True, False (default)

Antenna Azimuth (degrees) Antenna azimuth.


Value range: 0..359

Antenna Down tilt Mechanical antenna down tilt.


(degrees) Value range: -89..89

Antenna Gain (dBi) Peak antenna Gain.


Value range: 0..100

Antenna Beamwidth Antenna Beamwidth.


(degrees) Value range: 0..360

Cable Loss (dBi) loss of signal power due to transmission line (dBi)

Number of TX number of transmission antennas (if more than one antenna then it will be
used to compute multiple antenna signal power gain)

Antenna Model CBSD Antenna model

Inventory Parameters

CBSD Serial Number CBSD unique identifier given by the Domain-Proxy

CBSD Type The type of the CBSD HW entity: eNB or UE

Device ID The eNB Device ID, as defined in Devices list.

Page 20 of 45
The Device ID and Cell ID used for associating a CBSD to the eNB device cell.

Cell ID The eNB Cell ID.


The Device ID and Cell ID used for associating a CBSD to the eNB device cell.

IMSI ID The UE IMSI ID.


The UE IMSI ID used for associating a CBSD to the UE.

Operational TX Power the actual TX power configured on device

Total EIRP EIRP computed based on operational TX power, antenna gain, cable loss,
multiple antenna gain.
this must be less than the max EIRP authorized for grant

Actions

1- Types of CBSD Action Requests:


 Unregister Request
 Register Request
 Grant Request

a. Unregister Request, this request is used for unregister a CBSD from the SAS server.
When set, the Domain-Proxy performs deregistration from the SAS server and ignore this CBSD.
The status of the CBSD is changed to Unregister.
As long the CBSD is in this state it is not managed by Domain-Proxy.

b. Register Request, this request is used for register a CBSD with the SAS server.
A CBSD shall be registered and authorized by SAS prior to its initial service transmission.

On Register request, the CBSD will be added and managed by the SAS manager, however the
automatic state machine is not active, the CBSD will remain in this state till Grant request activation.

c. Grant Request, the Grant request is used for a Registered CBSD to request a Grant, an access for
the spectrum managed by the SAS.
When receiving a Grant Request, the SAS shall determine whether the CBSD can be allowed to
operate on the requested frequency range.

You may directly request Grant; in this case the registration will automatically perform.

2- CBSD Action Request status, this parameter shows the status of the request.
When a request is submitted until a response will be arrive, the Action Status sets to Pending.
After the response from the SAS server arrives, the ‘Action Result’ state will appear as Failed/Successful
and the final CBSD status will be presented. If the request fails. The last CBSD status will remain and the
cause of the failed Action Request will be presented in the ‘Action Description’ column.

Page 21 of 45
 Pending
 Successfully Executed
 Executed with a Failure
3- CBSD Action Request Description, the description of the action request completion state, on a failure,
it presents the error description.

CBSD Status

CBSD Status maintained by the Domain-Proxy. By default, CBSD status is Unregistered.

CBSD Statuses:
 Unregistered
 Registered
 Grant Rejected
 Grant Authorized
 Grant Suspended

Possible failures:

Error Action Descriptions


SAS request failed (BLACKLISTED) CBSD is blacklisted
SAS request failed (MISSING_PARAM) Required parameters are missing
SAS request failed (INVALID_VALUE) One or more parameters have invalid value
SAS request failed (CERT_ERROR) Error in the used certificate
SAS request failed (DEREGISTER) CBSD is automatically deregistered by the SAS.
SAS request failed (REG_PENDING) Incomplete registration information. The registration process is
failed
SAS request failed (GROUP_ERROR) An error has been identified in the grouping parameters of the
CBSD
SAS request failed 1. The frequency range indicated in the spectrum inquiry
(UNSUPPORTED_SPECTRUM request is at least partially outside of the CBRS band
2. The frequency range indicated in the grant request is at
least partially outside of the CBRS band
SAS request failed (INTERFERENCE Requested operation parameters cause too much interference.
SAS request failed (GRANT_CONFLICT Conflict with an existing Grant of the same CBSD.
SAS request failed The Grant is terminated.
(TERMINATED_GRANT
SAS request failed The Grant is suspended
(SUSPENDED_GRANT
SAS request failed 1- Operation parameters are out of sync between the CBSD
(UNSYNC_OP_PARAM and the SAS.
Page 22 of 45
2- Grant state is out of sync between the CBSD and the SAS.

CBSD Management and Monitoring


CBRS page is used for CBSD’s management and monitoring.

Figure 5: CBSDs Screen, example 1

Figure 6: CBSDs Screen, example 2

CBSDs Summary widget

CBSDs Network Summary widget presents the number of CBSDs grouped by CBSD State and Type.
These counters enable a fast list query by CBSD State and Type.

Clicking a rubric with the CBSD status, for example, Unregistered will show the list of Unregistered CBSDs.
Clicking the counter eNB/UE in the Unregistered rubric, will show the Unregistered eNB/UEs CBSDs.

Figure 7: CBSDs Network Summary widget

Page 23 of 45
CBSDs List

Figure 8: CBSDs List, Default View

List Columns

Figure 9: Column Selection Screen

Each parameter of the CBSD is shown in a separated column. The columns are:
 CBSD Serial Number
 Type
 IMSI ID
 Device ID
 Maximum EIRP
 Cell ID
 Associated eNB
 Low Frequency
 High Frequency
 CBSD Status
 Action Type
 Action Result
 Action Request User
 Action Request Date
 Height
 Height Type
 Horizontal Accuracy
 Indoor Deployment
 Azimuth
 Down Tilt (degrees)
 Gain
Page 24 of 45
 Antenna Beamwidth
 Antenna Model
 Cable Loss
 Number of TX

Functional Buttons

Figure 10: Functional Buttons

• Remove all Filters


• Add - See Single CBSD creation
• Delete - Delete CBSDs. Only CBSDs in Unregistered status can be deleted.
• Device Action - send Unregister/Register/Grant request for the selected CBSD/s to the SAS server.
The action request is applicable in the Device Action menu according to the state of the CBSD:
CBSD Status Applicable Action Request
Unregistered Register, Grant
Registered Unregister, Grant
Grant Unregister, Register
Grant Reject Unregister, Register

• Column Selection - select the column selection for adding/removing column from the CBSDs list
• Export - see Export / Import CBSD’s list.
• Refresh - Refresh the page
• Page Size - control the number of displayed CBSDs in the page:10, 50 (default), 100,500

Single CBSD Creation


For creating a single eNB CBSD do the following steps:

Figure 11: Add eNB CBSD


Page 25 of 45
1. Click the button Add CBSD.
2. In the Add CBSD dialog select the Device Type ‘eNB’

Figure 12: Add eNB CBSD Screen

3. Set the Device ID number.


This number is the Device unique identity, sets in the eNB installation phase.
It used for associating a CBSD entity with the discovered eNB (Devices List).
The Device ID number should have 1..10 digits. Device ID “0” is not valid.

4. Set the device Cell ID: 0 or 1

5. Click the Save button

For creating a single UE CBSD do the following steps:

Figure 13: Add UE CBSD

1. Click the button Add CBSD.


2. In the Add CBSD dialog select the Device Type ‘UE’

Page 26 of 45
Figure 14: Add UE CBSD Screen

3. Set the IMSI ID number.


The IMSI ID used for associating a CBSD entity with the discovered UE (UEs List).
The IMSI ID should have 14..15 digits.
4. Click the Save button

Once Save clicked, CBSD Details dialog box will be opened containing the calculated CBSD Serial Number.
The CBSD Serial Number is the unique identity of a CBSD.

Delete CBSD
Deletion of CBSD(s) is allowed only if the CBSD is in Unregistered status.

Select a single or multiple CBSDs and click on Delete button

CBSD Details

CBSD Details screen presents the selected CBSD inventory, states and configuration parameters.

Page 27 of 45
Figure 15: eNB CBSD Details

Figure 16:UE CBSD Details

Inventory & State Area


This area presents the CBSD identification parameters, inventory, State and enable a quick navigation to
the associated device.
Page 28 of 45
Figure 17: eNB and UE Inventory & State Area

• Clicking on Device ID and IMSI ID opens the eNB Device Details and UE Details screen respectively.

Configuration Area
This area presents the values of the CBSD configuration parameters and enable editing it.

Page 29 of 45
Figure 18: eNB CBSD Configuration Area

Figure 19: UE CBSD Configuration Area

CBSD Actions

CBSD Action Request: Register/ Grant / Unregister


Page 30 of 45
Action request sends request towards the SAS server. For sending the request:

1- Open the CBSDs list/ CBSD Details view.


2- Select the ‘Device Actions’ button :
3- From the Action Menu select the action option: Register/Grant/Unregister.

Export / Import CBSDs

Export / Import options


• Export CSV File / Export XLSX file
These options generate a file containing full CBSD information: configuration, inventory and status
parameters.

• Export Configuration
This option generates a file containing CBSD configuration parameters. It is used for multiple
configuration: update and add new CBSDs.

Figure 20: Export / Import CBSDs List Button

Multiple Configuration
Creation and Update of multiple CBSDs can be done via the Import XLSX tool. CBSDs that are listed in the
XLSX file and their configuration will be imported to BreezeVIEW and be saved in the data base.

1. Creation of multiple CBSDs:


• Create at least single CBSD manually.
• Select the Export button.
• Select the option Export Configuration. An XLSX file will be downloaded to your server with a table
of all the supported configuration for the import process.

Page 31 of 45
• Fill in the table with the Mandatory parameters for the import process.
Leave the CBSD Serial Number field empty, it will be created automatically by BreezeVIEW server.
• Mandatory parameters for adding eNB CBSD via Import:
o Type: ENB
o Device ID: up to 10 digits.
o Cell ID: 0 or 1.
• Mandatory parameters for adding UE CBSD via Import:
o Type: UE
o IMSI ID: between14-15 digits.

2. Updating multiple CBSDs


• Select the Export button.
• Select the option Export Configuration. An XLSX file will be downloaded to your server with a table
of all the supported configuration for the import process.
• Update the parameters in the table, except for the unique identification parameters.
Unique identification parameters cannot be updated. CBSD that its Unique identification
parameters needs be modified, should be deleted and recreated.
o Unique identification of eNB CBSD via Import:
 Type: ENB
 Device ID: up to 10 digits.
 Cell ID: 0/1
o Unique identification of UE CBSD via Import:
 Type: UE
 IMSI ID: between14-15 digits.
• Optional parameters for importing CBSD:
o Associated eNB (UE CBSD only)
o Low Frequency
o High Frequency
o Maximum EIRP
o Latitude
o Longitude
o Height
o Height Type

Page 32 of 45
o Horizontal Accuracy
o Vertical Accuracy
o Indoor Deployment
o Azimuth
o Down Tilt (degrees)
o Gain
o Cable Loss
o Antenna Beamwidth
o Antenna Model
o Number of TX
• Select Export> Import XLSX

View the updated CBSDs and click the Save button, for saving the CBSDs updates to the database.

CBSD Audit Log

CBSD Audit Log, presents the CBSD changes along the time. A change may be initiated by the user, SAS or
Domain-Proxy.

 Select a single CBSD, click on CBSD Audit Log button.

Figure 21: CBSD Audit Log

Page 33 of 45
Figure 22: CBSD Audit Log example.

Alarms & Events

Domain-Proxy issues Alarms indicating on SAS connectivity failures and CBSD failures.

Figure 23: CBSD's Alarms, Example 1

Figure 24: CBSD's Alarms, Example 2

Page 34 of 45
Figure 25: CBSD's Alarms, Example 3

 SAS Server is unreachable


The alarm initiated by the Domain-Proxy upon detecting a link failure with the SAS Server, it should be
cleared once the connection is re-established.
 CBSD Stop Transmission
The device transmission stopped due to SAS request, the alarm shows the exact reason for it.
 SAS server configuration failure
The SAS Server configuration is wrong; the alarm shows the exact reason.
e.g. wrong protocol version, expired sever certifications, etc.

BreezeVIEW CLI Commands


Useful CLI commands:
 Set SAS server settings:

set lte-sas sas-settings sas-server

Possible completions:

o fcc-id - CBSD FCC Id used for registering to SAS


o sas-client-certificates - List of certificate files used to authenticate towards SAS server
o sas-server-certificates- Certificate chain used to authenticate SAS server
o sas-server-crl - Certificates Revocations List given by the Server Certification Authority
o sas-server-distinguished-name - Distinguished Name is verified as part of SSL Negotiation
o sas-url - URL used to access SAS server
o sas-validate-certificates - Disable or Enable the Revocation and Time validity checks for server
certificates
o sas-version - SAS protocol version
o user-id - CBSD user id used for registering to SAS

 Check connectivity with the SAS server:

Page 35 of 45
request lte-sas check-connectivity

 Add CBSD

set lte-sas cbsd <cbsd serial number>

o CBSD Serial Number for eNB:


Y|XXXXXXXXXX.
Y - Cell ID: 0/1
X – 10 digits for device ID
o Cbsd Serial Number for UE:
IMSI ID
o Commit

 Configure the CBSD:


 Set the CBSD general parameters:
o category - CBSD category used for registering to SAS
o high-frequency - Range high frequency (MHz)
o low-frequency - Range low frequency (MHz)
 max-eirp - Maximum EIRP permitted by the Grant (dBm/MHz)
o Set the cbsd antenna parameters: ‘set lte-sas cbsd 00000000141 antenna’:
 azimuth - CBSD Antenna azimuth (degrees)
 beamwidth - CBSD Antenna beamwidth (degrees)
 cable-loss - CBSD Antenna cable loss (dBi)
 downtilt - CBSD Antenna tilt (degrees)
 gain - CBSD Antenna maximum gain (dBi)
 height - CBSD Antenna height (meters)
 height-type - CBSD Antenna height type
 horizontal-accuracy - CBSD Antenna horizontal accuracy (meters)
 indoor-deployment - CBSD Antenna indoor deployment
 latitude - CBSD Antenna latitude (degrees)
 longitude - CBSD Antenna longitude (degrees)
 model - CBSD Antenna model
 num-of-tx - Number of TX antenna
 vertical-accuracy - CBSD Antenna vertical accuracy (meters)

o Set action request: set lte-sas cbsd <CBSD serial Number> general action-request:
 GrantRequest

Page 36 of 45
 RegisterRequest
 UnregisterRequest
o Show cbsd list: in none configured mode: show lte-sas cbsd | tab

 Audit Log
 FetchAuditLog – get a list of audit logs; if CBSDSerialNumber is specified then only entries associated
with that CBSD are returned (this should answer your question about how UI pulls information for a
specific CBSD)
 ClearAuditLog – clear all or CBSD specific log entries

Extensions

SAS Procedures Error codes


In the error data object of a response message, SAS includes an error code to inform the status of the corresponding
request.
The error codes are grouped into the following categories:
1- 0: success
2- 100 – 199: general errors regarding CBSD and protocol
3- 200 – 299: error events related to CBSD registration
4- 300 – 399: error events related to spectrum inquiry
5- 400 – 499: error events related to grant
6- 500 – 599: error events related to heartbeat

Err Error Action Result Action Descriptions


Code
0 SUCCESS Successfully CBSD request is approved by SAS
Executed
100 VERSION Executed with a SAS protocol version used by CBSD is not supported by SAS
Failure
101 BLACKLISTED Executed with a CBSD is blacklisted. This code is returned if the CBSD is under a SAS
Failure or FCC enforcement action and is barred from CBRS operation.
102 MISSING_PARAM Executed with a Required parameters are missing
Failure
103 INVALID_VALUE Executed with a One or more parameters have invalid value
Failure
104 CERT_ERROR Executed with a There is an error in the certificate used to make the request (e.g.
Failure the credential is of the wrong role).
105 DEREGISTER Executed with a A CBSD receiving this error code is automatically deregistered by
Failure the Domain-Proxy.
The response message may contain a string describing the reason
for deregistration.

Page 37 of 45
200 REG_PENDING Executed with a Incomplete registration information. The registration process is
Failure pending. The CBSD is likely to accomplish a successful registration
when the missing registration information is made available to the
SAS.
201 GROUP_ERROR Executed with a An error has been identified in the grouping
Failure parameters of the CBSD
300 UNSUPPORTED_SPECTRUM Executed with a The frequency range indicated in the spectrum inquiry request or
Failure grant request is at least partially outside of the CBRS band.
400 INTERFERENCE Executed with a Conflict with an existing Grant of the same CBSD.
Failure
401 GRANT_CONFLICT Executed with a Conflict with an existing Grant of the same CBSD.
Failure
500 TERMINATED_GRANT Executed with a The Grant is terminated. This condition occurs if, for example,
Failure incumbent status has changed permanently causing the current
Grant to terminate. The CBSD radio will be set to off.
501 SUSPENDED_GRANT Executed with a The Grant is suspended. This condition occurs if incumbent status
Failure has changed temporarily.
502 UNSYNC_OP_PARAM Executed with a Operation parameters are out of sync between the Domain-Proxy
Failure and the SAS.

WinnForum CBRS Acronym and Definitions


Acronym
CA Certificate Authority
CBRS Citizens Broadband Radio Service
CBSD Citizens Broadband Radio Service Device
CBSD-ID CBSD Identifier
CFR Code of Federal Regulations
CGI CBSD Group Identifier
CPAS Coordinated Periodic Activities among SASs
CP Certification Policy
CPI Certified Professional Installer
CPIDI Certified Profession Installer Device Information
CPIR-ID Certified Professional Installer Registration Identification
CPS Certification Practice Statement
CRA Certificate Requesting Account
CRL Certificate Revocation List
CSR Certification Signing Request
DoD U.S. Department of Defense
DP Domain Proxy

Page 38 of 45
DPA Dynamic Protection Area
DR Demand Response
DRAS Demand Response Automation Server
ECC Elliptic Curve Cryptography
EIRP Effective Isotropic Radiated Power
EMS Element Management System
ESC Environmental Sensing Capability
E-UTRA Evolved Universal Terrestrial Radio Access
EUD End User Device
FCC Federal Communications Commission
FIPS Federal Information Processing Standards
FRN FCC Registration Number
FSS Fixed-Satellite Service [
GAA General Authorized Access
GWBL Grandfathered Wireless Broadband Licensee
GWPZ Grandfathered Wireless Protection Zone
HAAT Height Above Average Terrain
HTTP Hypertext Transfer Protocol
HTTPS Secure HTTP (e.g., with TLS)
IAP Iterative Allocation Process
ID Identifier, Identity
ICG Interference Coordination Group
IETF Internet Engineering Task Force
IMG Interference Margin Group
IOT Inter-Operability Test
ISO Independent System Operators
JSIR Joint Spectrum Interference Resolution
JSON JavaScript Object Notation
MFCN Mobile / Fixed Communication Networks
MFG Manufacturer
NOAA National Oceanic and Atmospheric Administration
NTIA National Telecommunications and Information Administration
OA&M Operations, Administration and Maintenance
OCSP Online Certificate Status Protocol
OR-ID Owner Registration ID
PA Policy Authority

Page 39 of 45
PA Priority Access
PAL Priority Access License
PAL-ID Priority Access License Identifier
PKCS Public-Key Cryptography Standard
PKI Public Key Infrastructure
PPA PAL Protection Area
PPA-ID PAL Protection Area Identifier
RAN Radio Access Network
RFC Request for Comment
RFP Request for Proposal
SAS Spectrum Access System
UR-ID User Registration Identity
UUT Unit Under Test
WBS Wireless Broadband Service
WInnForumTM The Wireless Innovation Forum
WISP Wireless Internet Service Provider based on

Definitions
Admin Test Harness: A collection of routines that can be configured by the test operator to inject data that is required for
the purpose of the test cases, into the SAS UUT. The Admin Test Harness also has the ability to recognize the completion of
CPAS executed by the SAS UUT.

Aggregated Channel Bandwidth. The Aggregated Channel Bandwidth is the bandwidth of a single channel, or in the case of
multiple contiguous channels, the bandwidth between the upper and lower limits of the combined contiguous channels.

Blacklist: A list of CBSDs that are to be denied service.

BTS-CBSD: A base transceiver station CBSD that serves one or more points, which may be EUDs or CPE-CBSDs. [3]
Category A CBSD: A lower power CBSD that meets the general requirements applicable to all CBSDs and the specific
requirements for Category A CBSDs set forth in sections 96.41 and 96.43. [FCC rules]

Category B CBSD. A higher power CBSD that meets the general requirements applicable to all CBSDs and the specific
requirements for Category B CBSDs set forth in sections 96.41 and 96.45. [FCC rules]

CBRS band: The 3550-3700 MHz Citizens Broadband Radio Service band. [3,11]

CBRS-wide: Across the entire CBRS system including all CBRS entities (note: this is equivalent to system-wide). [10]

CBSD Antenna: The radiating element(s) of the CBSD. From the perspective of the SAS-CBSD interface, each CBSD has one
Note that the CBSD’s antenna may be instantiated with multiple physical antennas (e.g., an antenna array for MIMO
operation), but those antennas must be transmitting one aggregate waveform collectively from a single geolocation, and
with a total transmit power that conforms to all the CBSD’s registration parameters and authorized transmit power levels
provided by the SAS in its active grants (e.g., maximum allowable EIRP). [2, 3]

Page 40 of 45
CBSD Group Identifier (CGI): An identifier used to allow one or more registering CBSDs to identify as a group that the CBSD
User for those CBSDs has established.

CBSD-ID: The system-wide unique identifier for registered CBSDs.

CBSD Registration: The process required to register a valid Citizens Broadband Radio Service Device (CBSD) with a SAS.
The procedure by which a CBSD indicates to a SAS its intention to operate. Successful registration implies a validation by
the SAS that the CBD has been FCC certified and confers on the CBSD the right to be authorized by the SAS to operate in
accordance with a Grant. During the registration process, each CBSD provides a fixed location, unique identifiers (e.g.,
owner information, device information), Group membership, and radio-related capabilities. A successful registration
procedure concludes with the SAS providing a unique identifier for that CBSD.
CBSD Test Harness. A collection of routines that can be configured by the test operator to interact with the SAS UUT via
interfaces specified in [n.9] and automates critical test sequences and procedures in this document and [n.14]. Via these
interfaces and following the specified test procedures, the CBSD Test Harness emulates the SAS-CBSD Request Messages
specified in [n.9] that would be generated by one CBSD, using a TLS connection with CBSD certificate to the SAS UUT. If
multiple CBSD Test Harnesses are directly connected to the SAS UUT, each has its own TLS connection to the SAS UUT. The
software without the CBSD certificate is stored in a public location.

CBSD User: The registered entity that has operational responsibility for the CBSD.

Certificate. A message that, at least, states a name or identifies the CA, identifies the Subscriber, contains the Subscriber’s
public key, identifies the Certificate’s Validity Period, contains a Certificate serial number, and is digitally signed by the CA
that issued the certificate.

Certificate Applicant. An individual or organization that requests the issuance of a Certificate by aa CA.

Certificate Application. A request from a Certificate Application (or authorized agent of the Certificate Applicant) to a CA
for the issuance of a Certificate.

Certificate Chain. An order list of Certificates containing a Subscriber Certificate and one or more CA Certificates, which
terminates in a root Certificate.

Certificate Policy (CP). The principal statement of policy governing the PKI.

Certificate Signing Request (CSR). A message conveying a request to have a Certificate issued.

Certificate Authority (CA). An entity authorized to issue, manage, revoke, and renew Certificates in the PKI

Certification Practice Statement (CPS). A statement of the practices that a CA employs in approving or rejecting Certificate
Applications and issuing, managing, and revoking Certificates

Certificate Requesting Account (CRA). The online portal to assist Certificate Applicants in requesting Certifications.

Certified Professional Installer (CPI): Any individual trained and currently validly certified from an accredited CPI Training
Program based on the relevant Part 96 rules and associated technical best practices for the Citizens Broadband Radio
Spectrum (CBRS).

CPI Accreditation Standard: Standard defining how a CPI Training Program Administrator can be accredited to run a
Certified Professional Installer (CPI) Training Program. The CPI Accreditation Standard includes a curriculum standard
defining the requirements necessary for trainees to be certified as a Certified Professional Installer. The CPI Accreditation
Standard includes a requirement for an objective certification test to be administered by a program administrator as part
of the CPI Training Program. Passing this test is a prerequisite for an individual to be considered a Certified Professional
Installer.
Page 41 of 45
CPI Training Program: A required training curriculum contained in a valid program, as defined by the CPI Accrediting body,
for certification of a CPI. Such curriculum may have mandatory (such as Part 96 and rules-based requirements) and
optional components (such as industry best practices or manufacturer or SAS specific training). [10]

CPI Training Program. Mandatory training/curriculum required by the CPI Training Program Administrator as a prerequisite
for taking the objective certification test

CPI Training Program Administrator: Entity such as a network equipment operator that develops a Certified Professional
Installer (CPI) Training Program, gains accreditation, administers the objective certification test and maintains certification
records.

CPI Training Program Administrator: Entity such as a Network Equipment Operator, an equipment vendor, a SAS operator,
or a third-party training organization that develops a Certified Professional Installer (CPI) Training Program, gains
accreditation, administers the objective certification test and maintains CPI records

CPI Registration Identification (or ID) (CPIR-ID): The unique identifier provided by the CPI Accrediting Body through the CPI
Training Program to CPIs who are validly and currently certified and registered as CPIs

Channel. The contiguous frequency ranges between lower and upper frequency limits.

Citizens Broadband radio Service Device (CBSD). Fixed Stations, or networks of such stations, that operate on a Priority
Access or General Authorized Access basis in the Citizens Broadband Radio Service consistent with Title 47 CFR Part 96.
For CBSDs which comprise multiple nodes or networks of nodes, CBSD requirements apply to each node even if network
management and communication with the SAS is accomplished via a single network interface. End User Devices are not
considered CBSDs. [FCC rules]
Citizens Broadband radio Service Device (CBSD): Fixed Stations, or networks of such stations, that operate on a Priority
Access or General Authorized Access basis in the Citizens Broadband Radio Service consistent with Title 47 CFR Part 96
[n.8]. For CBSDs which comprise multiple nodes or networks of nodes, CBSD requirements apply to each node even if
network management and communication with the SAS is accomplished via a single network interface.

Cluster List: The set of CBSDs, identified by their CBSD-IDs, included in a PPA claim. The PAL Holder provides this Cluster
List to the Managing SAS. These are the CBSDs that provide service and coverage within the claimed PPA.

Coexistence Group: A group of CBSDs that coordinate their own interference within the group according to a common
interference management policy.

Compromise. A violation of a security policy, in which an unauthorized disclosure of, or loss of control over, sensitive
information has occurred. With respect to private keys, a Compromise is a loss, theft, disclosure, modification,
unauthorized use, or other compromise of the security of such private key.
Device Certificate. An end-entity non-CA certificate of the PKI chain installed in CBRS devices such as SAS Provider, Domain
Proxy, Installer, PAL and CBSD devices.
Digital Certificate Subscriber Agreement. An agreement used by a CA setting forth the terms and conditions under which
an individual or organization acts as a Subscriber.
Domain Proxy (DP): An entity engaging in communications with the SAS on behalf of multiple individual CBSDs or networks
of CBSDs. The Domain Proxy can also provide a translational capability to interface legacy radio equipment in the 3650-
3700 MHz band with a SAS to ensure compliance with Part 96 rules.
Domain Proxy (DP) Test Harness. A collection of routines that can be configured by the test operator to interact with the
SAS UUT via interfaces specified in [n.9] and automates critical test sequences and procedures in this document and
[n.14]. Via these interfaces and following the specified test procedures, the DP Test Harness emulates the SAS-CBSD
Request Messages specified in [n.9] that would be generated by one or more CBSDs, using a TLS connection with DP

Page 42 of 45
certificate to the SAS UUT. If multiple DP Test Harnesses are connected to the SAS UUT, each has its own TLS connection to
the SAS UUT. The DP function within the DP Test Harness merely aggregates the Request Messages of multiple single
CBSDs and disaggregates the respective Response Messages of the SAS UUT and does nothing else (i.e., does not have any
other unique functionality of a real Domain Proxy).
Dynamic Protection Area (DPA): A predefined protection area which is activated or deactivated to protect a federal
incumbent radar. An activated DPA must be protected from aggregate CBSD interference. A deactivated DPA is not
protected from CBSD interference. [10]
Environmental Sensing Capability (ESC). A system that detects and communicates the presence of a signal from an
Incumbent User to an SAS to facilitate shared spectrum access consistent with sections 96.15 and 96.67. [FCC rules]
Environmental Sensing Capability (ESC) Test Harness: A collection of routines that can be configured by the test operator
to interact with the SAS UUT in order to execute the ESC functionalities of the test cases described in this document. Via
these interfaces and following the specified test procedures, the ESC Test Harness emulates the messages that would be
sent from an ESC system to a SAS. The ESC Test Harness software is stored in a public location specified in [i.1]. [2]
Exclusion Zone. A geographic area wherein no CBSD shall operate. Exclusion Zones shall be enforced and maintained by
the SAS. Exclusion Zones will be converted to Protection Zones following the approval and commercial deployment of an
ESC and SAS consistent with this part. [FCC rules]
Fixed Station. A CBSD or End User Device that transmits and/or receives radio communication signals at a fixed location.
Fixed Stations may be moved from time to time but Fixed CBSDs must turn off and re-register with the SAS prior to
transmitting from a new location. [FCC rules]

General Authorized Access (GAA) User. An authorized user of one or more CBSDs operating on a General Authorized Access
basis, consistent with section 96.33, et seq. [FCC rules]
Geo-Location Capability. The capability of a CBSD to register its geographic coordinates within the level of accuracy
specified in section 96.39. The CBSD location is used by the SAS to determine frequency availability and maximum transmit
power limits for CBSDs. [FCC rules]
Grant: The authorization provided by a SAS to a CBSD, subject to a Heartbeat exchange, to transmit using specified
operating parameters. Grants are identified by a unique Grant identifier. Once issued, a Grant’s operating parameters are
never changed; if new or modified operating parameters are required, then a new Grant must be obtained. The Grant's
operating parameters are maximum EIRP and Channel. A Grant can be in different states as defined in section 7.
Granted State: The “GRANTED” state refers to a spectrum Grant that has been allocated to a CBSD by the SAS. This Grant
state does not allow radio transmission by the CBSD relative to the Grant.
Group: A collection of CBSDs which are provided a special, common form of management by the SAS. The nature of the
special management is dependent on Group type.
Incumbent User. A federal entity authorized to operate on a primary basis in accordance with the table of frequency
allocations, fixed satellite service operator, or Grandfathered Wireless Broadband Licensee authorized to operate on a
primary basis on frequencies designated in section 96.11. [FCC rules]
Initial Certification. Initial Certification in this specification applies to Release 1; however, after Initial Certifications, each
SAS administrator could have an alternate method that, when approved by the FCC, would be allowed.
Interference Coordination Group: A group of CBSDs that does not require intra-group, inter-CBSD interference
coordination from the SAS.
Main Test Harness: A collection of routines that can be configured by the test operator to interact with the SAS UUT in
order to execute the test cases. It includes the reference models, Admin Test Harness, SAS Test Harnesses, DP Test

Page 43 of 45
Harnesses, CBSD Test Harnesses, and all other test harnesses defined in this document. The Main Test Harness software is
stored in a public location specified in [i.1].
Managing SAS: The SAS that administers a PAL and serves the CBSDs that form the Cluster List of a PPA registered to a PAL
Holder that is authorized to use that PAL. The Managing SAS is the SAS which accepts, checks, and validates a PPA claim
and which issues a PPA-ID for a valid PPA, and which shares the PPA-ID and the PPA vertex points with all SASs.
Subsequently, the Managing SAS serves the CBSDs on the PPA Cluster List. The Managing SAS also serves CBSDs using GAA
grants and their CBSD Users.
Non-Public Registration Data. CBSD registration data that would allow one to identify a licensee and must [shall] therefore
be obfuscated pursuant to FCC Requirement 96.55(a)(3).
OR-ID: Owner Registration ID. The system-wide unique identifier for Registered Owners.
Owner / Registered Owner: The owner of one or more CBSD devices and/or the owner of one or more PAL licenses. All
owners of CBSDs must be registered as owners, whether they use GAA or PAL spectrum. All owners of PAL licenses must
be registered as owners, even if they have not deployed any CBSDs. All pre-registered eligible lessees must be registered
as owners. All brokers or transferring agents who handle PAL rights or PPA claims must be registered as owners.
PAL-ID: The system-wide unique identifier for a PAL.
PAL database: The system-wide accessible database that allows the look-up of a PAL boundary and PAL ownership based
upon the PAL-ID.
PAL Holder: The entity who has legal rights to make PPA claims under the registered PAL.
PAL Reserved Channel: A 10 MHz channel in the range of 3550-3650 that a SAS may establish for exclusive use of a set of
one or more CBSDs that are registered as belonging to a PPA based upon acquired PAL rights.

PAL Protection Area (PPA): The area of protected use of a channel or set of channels within an owned or leased PAL. The
PPA is defined by a set of CBSDs (the Cluster List) and a boundary (a set of vertex points) that define the PPA within the
PAL. All SAS are obligated to protect PPAs from interference.
PKI: Public Key Infrastructure. A system which organizations credentials vouched for by a hierarchical structure containing
a Root of Trust (RoT). The Root of Trust signs credentials for trusted parties which authenticate their identities. Those
parties may then sign credentials for another level of trusted parties.
Priority Access License (PAL). A license to operate on a Priority Access basis, consistent with section 96.23, et seq. [FCC
rules]
Priority Access Licensee. A holder of one or more PALs. Priority Access Licensees shall be entitled to protection from
General Authorized Access Users and other Priority Access Licensees within the defined temporal, geographic, and
frequency limits of their PAL, consistent with the rules set forth in this part. [FCC rules]
Processing Center. A secure facility created by an appropriate organization (e.g., Symantec) that houses, among other
things, the cryptographic modules used for the issuance of Certificates.
Protection Zone. A geographic area wherein CBSDs may operate only with the permission of an approved SAS and ESC.
[FCC rules]
Public Registration Data. Data that SAS Administrators must share with the public according to FCC requirement
96.55(a)(3)
Registered Owner Identifier (ROI): An identifier used to allow one or more registering CBSDs to identify its (their)
Registered Owner and to allow the association to a specific grouping that the Registered Owner has established. This
grouping may correspond to area, to a domain proxy or proxies, to a lessee, or some other useful group.
Service Area. One or more contiguous License Areas held by the same Priority Access Licensee. [FCC rules]

Page 44 of 45
SAS: Spectrum Access System. A system that maintains records of all authorized services and CBSDs in the Citizens
Broadband Radio Service frequency bands, is capable of determining the available channel at a specific geographic
location, provides information on available channels to CBSDs that have been certified under the Commission’s equipment
authorization procedures, determines and enforces maximum power levels for CBSDs, and enforces protection criteria for
Incumbent Users and Priority Access Licensees, and performs other functions as set forth in the Federal Communications
Commission (FCC) rules. Spectrum Access Systems shall also refer to multiple Spectrum Access Systems operating in
coordination and in accordance with Part 96 [i.1
User Registration ID (UR-ID). The system-wide unique identifier for Registered Users of the CBRS; these may be CBSD Users
or PAL Holders.

Page 45 of 45

You might also like