Release 1 Technical Webinar

Transcription

1 Release 1 Technical Webinar 30 May 2018

2 Agenda Overview: Al Jette (Nokia), Chair of CBRS Alliance Technical Work Group Radio Aspects: Iwo Angelow (Nokia), Chair of Radio Task Group Release 1 Coexistence: Dr. Gary Boudreau (Ericsson), Chair of Coexistence Task Group Release 1 Network Architectures: Dr. Masoud Olfat (Federated Wireless), Chair of Network Services Task Group Q&A Best to leave Q&A to the end to ensure we have time to cover all material. Use the question function in the webinar platform to submit questions during the session. Will try to address clarification questions in real-time, but general questions will be handled after presentations. 2

3 Overview CBRS Alliance is an industry forum created to champion LTE in the CBRS Band ( MHz) in accordance with FCC Part 96 Rules Information on FCC Part 96 can be found at: The Part 96 rules can be found at: select Title 47, Chapter 1, Volume 5, Part 96 WInnForum webinar: Understanding the New US 3.5 GHz Band at: Note: This Webinar is from June 2015 and a couple of the FCC rules have since been revised, but webinar remains an excellent overview. WInnForum has additional Webinars on CBRS available on youtube. 3

4 Comparing the WInnForum and CBRS Alliance WInnForum Official SDO with multiple committees Spectrum Sharing Committee (SSC) handles FCC Part 96 rules (CBRS) & working closely with US Government Technology Neutral (many members support LTE, but other members support WiMAX & proprietary technology use in the band) Developing SAS, CBSD & ESC requirements; Security methods; SAS-CBSD & SAS-SAS protocols; Certification tests for: CBSD & SAS Specifying Coexistence across multiple technologies in Release 2 (not yet approved) CBRS Alliance Focus on LTE technology in the CBRS Band. Builds upon and compliant with WInnForum Standards Developing technical specs to support LTE deployments of Private Networks, Neutral Host Networks, Multi-Service Operator Networks, etc Focus on LTE coexistence Addressing LTE commercialization, business and marketing issues Broad range of members: manufacturers, operators, verticals and more Coexistence work is ongoing in both the WInnForum and CBRS Alliance 4

5 Technical Work Group Outputs: Specifications, best practices, recommendations, guidelines, etc Published Technical Specifications can be found from web site: Contribute into other fora as appropriate (working with WInnForum, ATIS, MulteFire and 3GPP) Task groups RF Coexistence TG Network Services TG Radio TG Network Svcs TG Technical WG Coexistence TG Radio TG 5

6 CBRS Alliance builds upon the strength of established LTE standards 3GPP developed the LTE (Radio access) and the corresponding network Global Standards 3GPP developed hundreds of standards for LTE and EPS and leverages and/or references many other industry standards (IETF, ITU, OMA, NIST, ETSI Smart Cards, GPS, and many more) US Telecom systems must also comply with relevant FCC Rules and various ATIS Standards (Mobile Alerting, E911, etc) CBRS networks must also comply with WInnForum requirements (which include FCC Rules) and we layer on CBRS Alliance specifications We are exploiting the strengths of multiple standards bodies to develop a commercial LTE solution in the CBRS Band. 6

7 What makes CBRS different? LTE is designed for mobile network operators deploying in exclusive use spectrum. CBRS is lightly licensed shared spectrum, and opens opportunities for new use cases not addressed by 3GPP (e.g. Neutral Host Networks) Also defining use of a shared CBRS HNI Device Based Authentication Multi-services operator deployments And more 7

8 Radio Task Group Iwo Angelow

9 * Release independent 3GPP CBRS Bands 3550 MHz 3700 MHz 3GPP defined a CBRS TD- LTE Band (Band 48) 3GPP Standards approved in December 2016 (Rel- 14) for PAL and GAA operation Covers full CBRS range: GHz, compliant with FCC emissions requirements Additional E-UTRA BS Spurious emissions limits for Band 48 Frequency range Maximum Measurement Note Level Bandwidth 3530MHz 3720MHz -25dBm 1 MHz Applicable 10MHz from the assigned channel edge 3100MHz 3530MHz 3720MHz 4200MHz -40dBm 1 MHz 9

10 3GPP CBRS Bands Band 48: Supports channel bandwidths: 5, 10, 15 and 20MHz Signaling defined to indicate UE shall meet additional FCC requirements (UE power reduction for 15 and 20MHz channel bandwidth) All 3GPP BS classes (classified by the BS output power) supported by Band 48 UE Conformance Test Specs (RAN5) approved in June 2017 Channel bandwidth [MHz] A-MPR for "NS_27 Parameters RBstart RBend LCRB A-MPR db db db db db 10

11 3GPP CBRS Band combinations Band 48 Intra-Band Carrier Aggregation Downlink aggregated bandwidth up to 100MHz DL Peak Rates in excess of 1Gbps (exact rates depend on modulation/coding and MIMO schemes) 4 contiguous combinations Example: Intra-band contiguous 6 non-contiguous combinations 3550 MHz Example: Intra-band non-contiguous 3700 MHz 3550 MHz 3700 MHz 11

12 3GPP CBRS Band combinations * depending on modulation and MIMO scheme, DL peak rate can exceed 1Gbps Inter-band combinations with Downlink aggregated bandwidth up to 100MHz* 71 combinations across two different bands 33 combinations across three different bands 3 combinations across four different bands One Inter-band 2DL/2UL combination involving Bands 48 and 26 (FDD at 800 MHz) Additional CA combinations currently being worked Inter-band carrier aggregation Band A Band 48 12

13 Coexistence Task Group Dr. Gary Boudreau

14 Published Coexistence Specification, Rel-1 Legacy LTE networks have been designed for licensed (i.e. exclusive) spectrum use. Operators acquire exclusive use of spectrum, synchronize their enbs transmissions (UL & DL) and plan their network to minimize co-channel interference, allowing for cell re-use= 1. CBRS rules defined in FCC Part 96 allow multiple operators, different technologies and unsynchronized transmissions to co-exist in the same frequency channel CBRS Coexistence Rel-1 focuses on optimizing co-channel spectrum use for LTE deployments by defining: Phase sync requirements LTE-TDD DL/UL configuration requirements GAA channelization SAS-CBSD protocol enhancements such as coexistence groupings to allow coordination of transmissions to minimize co-channel interference.

15 Phase Synchronization and TDD Configuration Alignment UL UE1 UE2 Desired Signal Network 1 Network 2 Interfering signal DL or UL due to co-channel interference or phase mismatch / TDD configuration mis-alignment UE1 UE2 DL If the networks are not phase synchronized or are mis-aligned on TDD configurations, network 1 (blue) enb transmits on its DL and interferes with Network 2 (red) enb reception. Also on the UL the blue UE1 transmits and interferes with the reception of the red enb transmissions at the receiving UE2. 15

16 CBRS Alliance Co-existence Concept Definitions CxG (Coexistence Group): A group of CBSDs that abide by a common interference management policy which is used to coordinate their interference within the group. CxM (Coexistence Manager): A logical entity responsible for managing coexistence between GAA users within a CxG in coordination with SAS. A CxM may reside in a SAS. ICG (Interference Coordination Group): A group of CBSDs belonging to the same CxG indicating that they can manage their own interference within the group, and do not need channel orthogonalization even if they have overlapping coverage. CCG (Common Channel Group): A group of CBSDs, that are part of the same ICG, requesting a common primary channel assignment. 16

17 Cell Phase Synchronization Cell phase synchronization and well-defined alignment of downlink and uplink resources have been identified as necessary requirements for coexistence between two LTE-TDD networks in the CBRS band. When several operators deploying LTE-TDD networks have to share a CBRS channel or operate in adjacent CBRS channels, coordination of timing and TDD configuration is important. 3GPP defines cell phase synchronization accuracy as as the maximum absolute deviation in frame start timing between any pair of cells on the same frequency that have overlapping coverage areas. An LTE-TDD CBSD that belongs to CBRS Alliance CxG shall derive frame timing with the following agreements: 1. Time reference: A time reference traceable to a common time reference. Temps Atomique International (TAI) shall be used. 2. Initialization time: The use of a common initialization time serves to align the frame boundaries, and indeed the subframe boundaries, within the required timing accuracy. Carriers in a CA scenario shall further maintain a common frame reference for all bands and band combinations as per 3GPP specifications 17

18 TDD Configuration for LTE TDD The goal of the CBRS Alliance is to allow flexible use of the CBRS band if coexistence of multiple deployments is preserved. It is well known in the industry that multiple overlapping LTE-TDD deployments in the same band can coexist if they align their frame boundaries and use the same TDD configuration. Table 1 lists the mandatory E-UTRA TDD Configurations for the CBRS Alliance CxG. The SSFconfiguration for these options is fixed to be SSF Configuration 7. Table 1: Mandatory E-UTRA TDD Configurations for the CBRS Alliance Coexistence Group. The SSF configuration for these options is fixed to be SSF Configuration 7. Uplink-Downlink Configuration UL:DL ratio Subframe Number :4 D S U U D D S U U D 2 2:6 D S U D D D S U D D The CBRS Alliance requires all LTE-TDD CBSDs that are part of the same connected set shall use the same TDD configuration. 18

19 GAA Channelization For GAA channel assignments, the SAS shall attempt to assign a minimum channel assignment of 10 MHz to each CBSD For CBSDs that are members of the CBRS Alliance CxG, only combinations of 5 MHz channel units can be used for spectrum inquiry and grant request for GAA. Thirty channel units of 5 MHz width are defined with the following frequency ranges (in MHz) [ (k 1) 5, k 5], k = 1, 2,, 30. CBSDs shall request a spectrum grant in multiples of these 5 MHz channel units. CxM will follow the above GAA channelization for any guard band allocation in multiples of 5MHz. 5 MHz Channelization for GAA Band 48 PAL and Federal Incumbents FSS GWBL and Federal Incumbents

20 SAS to CBSD Protocol Extensions To facilitate management of the CBRS Alliance CxG by the CBRS Alliance CxM, all CBSDs that declare themselves to be part of the CBRS Alliance CxG need to exchange information with the CBRS Alliance CxM. This is accomplished by including this information on various messages of the SAS-CBSD protocol. In particular, in the direction of CBSD to CxM, the information is contained in the groupinfo object of the groupingparam data object. In the direction of CxM to CBSD, the information is contained in the groupingconfig data object. A CBSD can send grouping information to a CxM by including the groupingparam parameter in the RegistrationRequest, the SpectrumInquiryRequest, or the GrantRequest object A CxM can suggest a new E-UTRA TDD configuration for a CBSD by assigning an E-UTRA TDD parameter value in the groupingconfig parameter that the SAS can include in the RegistrationResponse, the SpectrumInquiryResponse, the GrantResponse, or the HeartbeatResponse object. 20

21 SAS to CBSD Protocol Extensions SAS /CxM Domain Proxy CBSD s CBRS Alliance CxG SAS-CBSD Interface CBSD Use groupingparam parameter in messages Spectrum Inquiry RegistrationRequest GrantRequest Set grouptype to Coexistence Group Set groupid to CBRS Alliance CBRSAllianceInfo object desiredtddconfig EutraTddConfig object ssfconfig cbrsagrouptype CBRSA ICG CBRSA CCG Use groupingconfig parameter in messages SpectrumInquiryResponse GrantResponse HeartbeatResponse groupingconfig object additions cbrsallianceconfig cbrsaversion eutratddconfig 21

22 Network Services Task Group Dr. Masoud Olfat

23 Roles in CBRS Services CBRS Network Operator Deploys a CBRS network with an intention to provide connectivity and/or enable services to Subscribers of participating service provider(s). Network operator may need to authenticate the subscriber, as well. Service Provider (SP) Role Have service agreement, authenticates, authorizes, and provides services to subscribers, MNOs, MSOs, or MVNOs A Participating Service Provider (PSP) is a service provider offering services via the specific Neutral Host. Subscriber Role Authenticated and authorized by one or more service providers. Could be person or a device; Service Provider 1 Subscriber of SP1 2. CBRS Network Operator SP Relationship: Business Agreement 1. Subscriber-SP Relationship (Service Agreement) CBRS Network Operator Service Provider 2 Subscriber of SP2 Service Provider n Subscriber of SPn 23

24 Service Provider (SP) Use Case SP deploys the CBRS network itself SP plays both roles of SP & CBRS Network MNO plays the role of both SP and CBRS NW Operator Coverage Extension through CBRS CBRS Network Deployed by MNO 1 SPs could represent traditional MNOs and MSOs, or other traditional types of SPs. MNO1 MSO 1 MNO 2 Uses traditional 3GPP Architectures like S1 interface Connection to other SPs through roaming Subscriber for MNO1: Access to CBRS NW deployed by MNO1 Subscriber for MSO1: No Access to this particular CBRS NW Subscriber for MNO2: No Access to this particular CBRS NW 24

25 Neutral Host Network (NHN) Use Case Business agreement between the NHN Operator and a SP to provide service to participating SP s subscribers NHN Use Case CBRS Network Deployed by NHN Operator No Relationship between MNO2 and CBRS Network Operator (NHN Operator) NHN operator plays the role of CBRS Network Operator Business agreement between NHNO Operator and MNO1 Business agreement between NHNO Operator and MSO1 MNO1 and MSO play the role of SPs MNO1 MSO1 MNO 2 Both MNO1 and MSO1 could be Participating Service Providers (PSPs) Could be considered as Distributed Antenna System (DAS) Replacement CBRS in a venue, public space or a large area providing service to users of multiple MNOs Subscriber for MNO1: Access to CBRS NW deployed by NHN Operator Subscriber for MSO1: Access to CBRS NW deployed by NHN Operator Subscriber for MNO2: No Access to this particular CBRS NW deployed by NHN Operator 25

26 Private and Hybrid Network Use Case NO Relationship between MNO1/MSO1 and CBRS Network Operator (Enterprise1) Private NW Use Case Provides service to employees, machines and other devices, as authorized by the private network provider. MNO 1 MSO 1 CBRS Network Deployed by Enterprise 1 (Enterprise 1 plays a CBRS Network Operator role) Enterprise 1 (Enterprise1 plays an SP role) The private network operator plays roles of both SP and CBRS Network Operator, with no business relationship with MNOs or MSOs. industrial, mining, off-shore or other isolated environments. Fixed Networks Private enterprise Network Private residential Networks wireless backhaul for connecting enbs to a 3GPP core network. Industrial IOT Subscriber of MNO1 : NO Access to this particular CBRS NW deployed by Enterprise 1 MNO1 plays the role of both SP and CBRS NW Operator CBRS Network Deployed by MNO1 MNO 1 Subscriber of MNO1 : Access to CBRS NW deployed by MNO1 Subscriber of MSO1: NO Access to this particular CBRS NW deployed by Enterprise 1 Hybrid Use Case 2 SP Centric Business agreement between MNO 1 (as CBRS NW Operator) and MSO 1 MSO 1 Subscriber of MSO 1 Access to CBRS NW deployed by MNO 1 26 Employee of Enterprise1: Access to CBRS NW deployed by Enterprise 1 NO Relationship between MNO2 and CBRS Network Operator (MNO1) MNO 2 Subscriber of MNO 2 NO Access to this particular CBRS NW

27 Multi-Subscription UE Use Case UE has two subscriptions To a Private Network To an MNO or MSO MNO access used Private Network coverage is unsatisfactory. Separate Credentials for Private Network and the MNO s SP. UE first authenticates to Private Network by using Private Network Credentials Private Network s IP connectivity is used then to provide a secure tunnel into the MNO s network using MNO authentication for MNO services. 27

28 CBRS NHN Architecture Requirements & Guidelines User authentication upon attachment to the NHN shall be performed against Primary Service Provider (PSP) subscriber database systems. PSP eligibility control on a per-nhn basis dynamically white-list or blacklist NHNs Mobility between NHNs and between an NHNs and SP Minimized data plane outages during inter-system mobility. Minimize changes and customizations to PSP networks and use standardized and available interfaces to PSP NHN operationally decoupled from PSP to the extent possible Minimize changes to 3GPP-defined behaviors of UEs and other EPC nodes (both in NHN and PSP Network) 28

29 Network Architecture SP2 EPC, using 3GPP EPC architecture epdg HSS S2b Depicts the network architecture for Private Network Neutral Host Network Hybrid Network (supports both Private and NHN network) Internet SGi Local Services SGi SGi SGi PDN GW S2a NH-GW 3GPP AAA Local AAA/Proxy NH-MME STa-N/SWa-N STa cbaaa EPC using NHN EPC architecture HSS SWx 3GPP AAA Non-3GPP AAA SP1 EPC, using 3GPP EPC architecture using a non-cbrs-i value as PLMN-ID Private EPC using 3GPP EPC architecture using a CBRS-I value as PLMN-ID enodeb enodeb CBRS RAN Broadcasts SP1 PLMN-ID and CBRS-I in SIB1 CBRS-NID in SIB1 PSP-IDs for SP2 and Private Network in SIB17 LTE Radio SP1 USIM based credentials SP1 3GPP UE - With SP1's PLMN-ID in USIM LTE Radio Private USIM-based credentials Private 3GPP UE - With a CBRS-I value as PLMN-ID and private network s CBRS-NID in USIM LTE Radio SP2 USIM based credentials SP2 NHN-capable UE - With SP2's PLMN-ID in USIM LTE Radio Private USIM/ Certificate/Usernamepassword based Private credentials NHN-capable UE - Configured with CBRS-I, CBRS-NID, and private network s PSP-ID 29

30 Release 2 and Beyond Work Items under study in Release 2 MSO Use Case Fixed Network Use Case Non-SIM Based Security Framework (3GPP-Based Access Network (Non-EPS-AKA) Beyond Release 2 Continue to develop specifications to address CBRS market needs 30