CBRS Coexistence CSAS Profile

CBRS Alliance Technical Work Group

Document CBRSA-TS-2002

Version V4.0.0

March 16, 2021

LEGAL NOTICES AND DISCLOSURES

THIS SPECIFICATION IS PROVIDED "AS IS," WITHOUT ANY REPRESENTATION OR WARRANTY OF ANY KIND, EXPRESS, IMPLIED, OR STATUTORY; AND TO THE MAXIMUM EXTENT PERMITTED BY LAW, ONGO ALLIANCE, AS WELL AS ITS MEMBERS AND THEIR AFFILIATES, HEREBY DISCLAIM ANY AND ALL REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION ANY WARRANTIES OF MERCHANTABILITY, TITLE, NON-INFRINGEMENT, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, OR RELIABILITY, OR ARISING OUT OF ANY ALLEGED COURSE OF PERFORMANCE, DEALING OR TRADE USAGE. ANY PERMITTED USER OR IMPLEMENTER OF THIS SPECIFICATION ACCEPTS ALL RISKS ASSOCIATED WITH THE USE OR INABILITY TO USE THIS SPECIFICATION.

THE PROVISION OR OTHER PERMITTED AVAILABILITY OF OR ACCESS TO THIS SPECIFICATION DOES NOT GRANT ANY LICENSE UNDER ANY PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS ("IPR"). FOR MORE INFORMATION REGARDING IPR THAT MAY APPLY OR POTENTIAL AVAILABILITY OF LICENSES, PLEASE SEE THE ONGO ALLIANCE IPR POLICY. ONGO ALLIANCE TAKES NO POSITION ON THE VALIDITY OR SCOPE OF ANY PARTY'S CLAIMED IPR AND IS NOT RESPONSIBLE FOR IDENTIFYING IPR.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, UNDER NO CIRCUMSTANCES WILL ONGO ALLIANCE, OR ANY OF ITS MEMBERS OR THEIR AFFILIATES, BE LIABLE FOR DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, PUNITIVE, OR OTHER FORM OF DAMAGES, EVEN IF SUCH DAMAGES ARE FORESEEABLE OR IT HAS BEEN ADVISED OR HAS CONSTRUCTIVE KNOWLEDGE OF THE POSSIBILITY OF SUCH DAMAGES, ARISING FROM THE USE OR INABILITY TO USE THIS SPECIFICATION, INCLUDING WITHOUT LIMITATION ANY LOSS OF REVENUE, ANTICIPATED PROFITS, OR BUSINESS, REGARDLESS OF WHETHER ANY CLAIM TO SUCH DAMAGES SOUNDS IN CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE AND STRICT LIABILITY), PRODUCT LIABILITY, OR OTHER FORM OF ACTION.

THIS DOCUMENT (INCLUDING THE INFORMATION CONTAINED HEREIN) IS PROVIDED AS A CONVENIENCE TO ITS READERS, DOES NOT CONSTITUTE LEGAL ADVICE, SHOULD NOT BE RELIED UPON FOR ANY LEGAL PURPOSE, AND IS SUBJECT TO REVISION OR REMOVAL AT ANY TIME WITHOUT NOTICE. THIS DOCUMENT IS PROVIDED ON AN "AS IS", "AS AVAILABLE" AND "WITH ALL FAULTS" BASIS. ONGO ALLIANCE MAKES NO REPRESENTATION, WARRANTY, CONDITION OR GUARANTEE AS TO THE USEFULNESS, QUALITY, SUITABILITY, TRUTH, ACCURACY, OR COMPLETENESS OF THIS DOCUMENT OR ANY INFORMATION CONTAINED HEREIN. ANY PERSON THAT USES OR OTHERWISE RELIES IN ANY MANNER ON THE INFORMATION SET FORTH HEREIN DOES SO AT HIS OR HER SOLE RISK.

IMPLEMENTATION OF A [NETWORK] AND/OR RELATED PRODUCTS OR SERVICES IS OFTEN COMPLEX AND HIGHLY REGULATED, REQUIRING COMPLIANCE WITH NUMEROUS LAWS, STATUTES, REGULATIONS AND OTHER LEGAL REQUIREMENTS ("LEGAL REQUIREMENTS"). AMONG OTHER THINGS, APPLICABLE LEGAL REQUIREMENTS MAY INCLUDE NETWORK OPERATOR REQUIREMENTS UNDER FEDERAL LAW, REQUIREMENTS RELATING TO E-911, ETC. A DISCUSSION OF SUCH LEGAL REQUIREMENTS IS BEYOND THE SCOPE OF THIS DOCUMENT. ACCORDINGLY, NETWORK OPERATORS AND OTHERS INTERESTED IN IMPLEMENTING NETWORKS OR RELATED SOLUTIONS ARE STRONGLY ENCOURAGED TO CONSULT WITH APPROPRIATE LEGAL, TECHNICAL AND BUSINESS ADVISORS PRIOR TO MAKING ANY IMPLEMENTATION DECISIONS.

OnGo Alliance 3855 SW 153rd Drive, Beaverton, OR 97003 www.ongoalliance.org info@ongoalliance.org Copyright © 2021 OnGo Alliance, All Rights Reserved

1 Introduction and Scope

An objective of the CBRS Alliance is to allow flexible use of the CBRS band while supporting coexistence of multiple deployments. A Technical Specification [1] has been developed to address coexistence among multiple LTE and/or 5G NR networks. The CBRS Alliance Coexistence Group (CxG) is managed by a Coexistence Manager (CxM) that is combined with a SAS to form a CBRS Alliance SAS Entity (CSAS). Moreover, WInnForum is in process of defining additional optional features on top of Release 1 specifications [2] in order to improve the performance of CBRS networks [11].

This specification defines a set of profiles characterized by a combination of baseline CBRS Alliance Coexistence functionalities as defined by [1] and a subset of WInnForum optional features to address the needs of a particular CBRS use case. Each of these specific sets of features are called a "CSAS Profile" in this document.

The key words "required", "shall", "shall not", "should", "should not", "recommended", "may", and "optional" in this document are to be interpreted as described in RFC-2119 [3].

Note: LTE and E-UTRA are equivalent terms for the purposes of this TS. Furthermore, unless otherwise noted, references to CBSDs refer to CBRS Alliance CBSDs.

2 References

• [1] CBRSA-TS-2001, "CBRS Coexistence Technical Specifications",
• [2] WInnF-TS-0112, "Requirement for Commercial Operation in the U.S. 3550-3700 MHz Citizen Broadband Radio Service Band", V1.8.0.
• [3] RFC-2119, "Key Words in RFCs to indicate Requirement Levels."
• [4] Electronic Code of Federal Regulations, Title 47, Chapter I, Subchapter D, Part 96
• [5] WInnF-TS-0061, "Test and Certification for Citizens Broadband Radio Service (CBRS); Conformance and Performance Test Technical Specification; SAS as Unit Under Test (UUT)", Version V1.5.1.
• [6] WInnF-TS-1001, "CBRS Operational and Functional Requirements (Release 2)".
• [7] WInnF-SSC-0010, "Signaling Protocols and Procedures for Citizens Broadband Radio Service (CBRS): WInnForum Recognized CBRS Grouping Parameters".
• [8] WInnF-TS-3002, "Signaling Protocols and Procedures for Citizens Broadband Radio Service (CBRS): Extensions to Spectrum Access System (SAS) - Citizens Broadband Radio Service Device (CBSD) Interface Technical Specification (Release 2)
• [9] WInnF-TS-3003, "Signaling Protocols and Procedures for Citizens Broadband Radio Service (CBRS): Extensions to Spectrum Access System (SAS) - SAS Interface Technical Specification (Release 2)"
• [10] WInnF-TR-5001, "CBRS Deployment Guidelines for Installers".
• [11] Enhancements to CBRS Baseline Standards (Release 2)", Wireless Innovation Forum, available here
• [12] ONGO Private LTE Deployment Guide, CBRS-Alliance, available here

3 Definitions and Abbreviations

3.1 Abbreviations

2-D: Two Dimensional
CBRS: Citizens Broadband Radio Service
CBRSA: CBRS Alliance
CBSD: Citizens Broadband Radio Service Device
DP: Domain Proxy.
GAA: General Authorized Access.
LTE: Long Term Evolution
NRI: Non-Regulatory Impacting
PAL: Priority Access License
RI: Regulatory Impacting
SAS: Spectrum Access System
TDD: Time Division Duplex
TR: Technical Report
TS: Technical Specifications
UE: User Equipment

3.2 Definitions

CSAS Profile: A statement of the mandatory, recommended, and optional procedures, messages, and parameters for the implementation of a compliant CSAS.
Non-Regulatory Impacting (NRI) features: Features that do not impact the result of approved WInnForum Release 1 test and certification process.
Regulatory Impacting (RI) features: Features that may impact the result of WInnForum Release 1 test and certification or Part 96 requirements.

4 WInnForum Release 2 Development

Per Part 96 FCC rules [4], every SAS must be compliant to WInnForum Release 1 Test and Certification Specifications [5]. It is expected that a mix of WInnForum Release 1 and post WInnForum Release 1 (Release 2, Release 3, etc., herein called Release 2) deployments coexist in the CBRS ecosystem for the foreseeable future. No entity is mandated to support any functionality beyond WInnForum Release 1, therefore supporting WInnForum Release 2 is not mandatory for any entity, including SASs. All entities claiming support for WInnForum Release 2 are responsible for working with WInnForum Release 1 entities in a mixed Release environment. Namely, any WInnForum Release 2 entity must support backward compatibility to WInnForum Release 1 entities using SAS-CBSD and SAS-SAS protocols, and any feature requiring coordination among SASs. WInnTo that end, all features defined in WInnForum Release 2 Specifications are optional [6].

To address backward compatibility with WInnForum Release 1, the only mandatory feature for any WInnForum Release 2 entity (SAS or CBSD) is to support a mandatory protocol update to allow feature discovery/capability exchange for any WInnForum Release 2 feature over SAS-CBSD/DP and SAS-SAS interfaces. All other WInnForum Release 2 features are optional. The capability exchange protocol update will support selective implementation of WInnForum Release 2 optional features.

Using the capability exchange protocol, SASs and CBSDs may inquire about implemented WInnForum Release 2 optional features from other entities (SAS from CBSD, CBSD from SAS, and SAS from SAS) or inform other entities about implementation of such features.

As part of backward compatibility with WInnForum Release 1, careful consideration must be given to features impacting any coordination among SASs including features requiring substantial similarity in performing incumbent protection or other activities. Any entity (SAS or CBSD) that does not exchange any WInnForum Release 2 capability with a peer entity, is considered as WInnForum Release 1 by the peer entity. If multiple SASs manage CBSDs impacting the same incumbent, for any feature impacting coordination among SASs, they will fall back to the lowest common feature set of all those SASs, i.e. WInnForum Release 1.

WInnForum has divided the WInnForum Release 2 features into two main categories, i.e. Regulatory Impacting (RI) and Non-Regulatory Impacting (NRI).

NRI features are defined as features that do not impact the result of approved WInnForum Release 1 test and certification process. An example of such features is Enhanced Grouping Handling feature, which extends the concept of Coexistence Group in Release 1 to allow a CBSD to register with a SAS indicating it is part of a user/operator defined group. These features do NOT change how the SAS treats the CBSD with respect to incumbent or PAL protections.

RI features are defined as the features that may impact the result of WInnForum Release 1 test and certification or Part 96 requirements. An example of these features is the support of 2-D antenna patterns, which is aimed to increase spectral utilization and improve incumbent and PAL protection if applied beyond GAA.

Table 4-1 summarizes existing WInnForum Release 2 features, which are considered for CSAS profiling. The table includes "PAL Leasing", which is defined as an optional feature as part of WInnForum Release 1 specification [10,12].

NOTE: Different CSASs can implement different CSAS Profiles. Additionally, different CSASs could implement different optional features even if they are operating with the same CSAS Profile. In those cases, if a feature requires CSAS-CSAS coordination, the feature might not be operationally enabled according to the Feature Capability Exchange requirements in [6] and the requirements of a particular OnGo use cases might not be addressed.

Table 4-1: WInnForum Release 2 Features

5 Business Use Cases to Address

To address the objectives of this documents, the following list introduces some of the candidate use cases within the CBRS ecosystem determined by CBRS Alliance.

• Fixed Wireless Access (section 6.2)
• Mobile broadband networks (section 6.3)
• Internet of Things (IoT) (e.g. Industrial IoT, Education IoT, Health IoT) (section 6.4)

NOTE: Use cases of private networks, public venues and utilities are not addressed in this version of this document, but they will be addressed in the future version.

6 CSAS Functional Profiles

Using the WInnForum Release 2 features outlined in Table 4-1, in this Section, CSAS functional profiles are defined to address the use cases listed in Section 5. Depending on new use cases required by the CBRS Alliance Business Working Group, these SAS profiles might be extended. In the tables depicted in this Section, a feature is assigned a Functional ID, and relevant references are provided for each feature.

In order to support the CBRS Alliance specifications, a Baseline CSAS Profile is introduced in Section 6.1. This is the minimum level of feature support to be considered compliant with CBRS Alliance Release 3 and beyond, and at the same time support the required regulatory requirements. Additional profiles are introduced, as enhancements over the Baseline CSAS Profile to support specific use cases.

In this section, three level of supports are designated for each feature:

"Required" : The support of the feature is required to address the requirements of the specific use case.
"Recommended" : Support of the feature is not required to address the requirements of the specific use case but will enhance the OnGo network performance for the use case.
"Optional" : Support of the feature is neither required to address the requirements of the specific use case, nor Recommended to enhance the OnGo network performance for the use case.

In this section, "CSAS Release" refers to the latest version of CBRSA-TS-2001 [1] in each release.

6.1 Baseline CSAS Profile

This profile defines the minimum level of CSAS feature support to be considered compliant with CBRS Alliance Release 4 and beyond, and at the same time support the regulatory requirements.

Table 6-1: Baseline CSAS Profile

6.2 CSAS Profile for Fixed Wireless Support

The CSAS Profile in Table 6-2 applies to the Fixed Wireless internet services.

Table 6-2: Fixed Wireless CSAS Profile

6.3 CSAS Profile for Mobile Network Support

The CSAS Profile in Table 6-3 applies to Mobile Network support.

Table 6-3: Mobile Network CSAS Profile

6.4 CSAS Profile for IOT Support

The CSAS Profile in Table 6-4 applies to IoT (Internet of Things) support.

Table 6-4: IoT CSAS Profile

7 Comparison of CSAS Profiles [Informative]

Table 7-1 summarizes and compares the CSAS Profiles introduced in this document

Table 7-1: Summary of CSAS Profile Comparisons

Appendix A: Document History

Table 19: Change History