ATIS 3GPP Webinar. Tuesday, August 29, :30 2:00 p.m. ET. Advancing ICT Industry Transformation

Transcription

1 ATIS 3GPP Webinar Tuesday, August 29, :30 2:00 p.m. ET Advancing ICT Industry Transformation

2 Agenda 3GPP Overview/Structure - Tom Anderson, ATIS Rel 15, 16 5G Schedule Key Features and Capabilities: Services Perspective - Farrokh Khatibi, Qualcomm Core Network/Architecture View - Stephen Hayes, Ericsson Description of RAN Features and Capabilities - Emad Farag, Nokia Wrap: North American Priorities Recap - Tom Anderson, ATIS Q&A 2

3 SPEAKERS Tom Anderson Senior Technology Consultant ATIS Dr. Emad Farag Sr 5G Physical Layer Standards Engineer Nokia Stephen Hayes Director of North American Standards Ericsson Dr. Farrokh Khatibi Director of Engineering QUALCOMM 3

4 Attendees will remain muted throughout the Webinar but may submit questions via attendee control panel. As many questions as possible will be addressed at the conclusion of all presentations. Unanswered questions will be addressed via . Slides will be ed to all participants. 4

5 3GPP Organizational Partners 5

6 Project Coordination Group (PCG) TSG RAN Radio Access Network RAN WG1 Radio Layer 1 spec RAN WG2 Radio Layer 2 spec Radio Layer 3 RR spec RAN WG3 lub spec, lur spec, lu spec UTRAN O&M rqmts RAN WG4 Radio Performance Protocol aspects RAN WG5 Mobile Terminal Conformance Testing RAN WG6 Legacy RAN radio and protocol TSG CT Core Network & Terminals CT WG1 MM/CC/SM (lu) CT WG3 Interworking with external networks CT WG4 MAP/GTP/BCH/SS CT WG6 Smart Card Application Aspects TSG SA Service & Systems Aspects SA WG1 Services SA WG2 Architecture SA WG3 Security SA WG4 Codec SA WG5 Telecom Management SA WG6 Mission-critical applications 6

7 Find a complete list of 3GPP work items at 7

8 Agenda 3GPP Overview/Structure - Tom Anderson, ATIS Rel 15, 16 5G Schedule Key Features and Capabilities: Services Perspective - Farrokh Khatibi, Qualcomm Core Network/Architecture View - Stephen Hayes, Ericsson Description of RAN Features and Capabilities - Emad Farag, Nokia Wrap: North American Priorities Recap - Tom Anderson, ATIS Q&A 8

9 ATIS Webinar Key Features and Capabilities Services Perspective Dr. Farrokh Khatibi Dir of Engineering Qualcomm Technologies Inc. 9

10 5G Use Cases Main use case of 5G: embb (enhanced Mobile Broadband) URLLC (Ultra-Reliable and Low Latency Communications) mmtc (massive Machine Type Communications) 8/29/

11 Enhancement of key capabilities from IMT- Advanced to IMT-2020* 8/29/2017 * Source: Recommendation ITU-R M , IMT Vision Framework and overall objectives of the future development of IMT for 2020 and beyond 11 11

12 The importance of key capabilities in different usage scenarios* 8/29/2017 * Source: Recommendation ITU-R M , IMT Vision Framework and overall objectives of the future development of IMT for 2020 and beyond 12 12

13 3GPP TS Service requirements for the 5G system - First 5G Specification from 3GPP TS was completed in February of 2017: Resolved long debate on UE vs IoT device (UICC/eUICC removed for 5G access) User Equipment: An equipment that allows a user access to network services via 3GPP and/or non-3gpp accesses. IoT device: a type of UE which is dedicated for a set of specific use cases or services and which is allowed to make use of certain features restricted to this type of UEs. Added an Annex on factory/process automation, electricity distribution, and intelligent transport use cases. 5G TRs available for context on use cases and building blocks TR SMARTER -- 5G use cases TR SMARTER-mIoT -- requirements for massive IoT TR SMARTER-CRIC -- mission critical requirements, industrial automation and tactile Internet TR SMARTER-eMBB -- evolved mobile broadband, higher data rates, higher density, deployment and coverage, scalable mobility TR SMARTER-NEO -- horizontal requirements, new business models, migration and interworking, and security. 8/29/

14 Example of TS Service requirements for the 5G system Alternate authentication, credentials and identities for network access Neutral host (partnership networks) Network and service slicing 3rd party ownership /control of service slicing Industrial (factory and process) automation and KPIs Dynamic remote provisioning Security of device identities Pseudo-identifiers to hide subscriber identity (no IMSI on first attach) Elimination of UICC/eUICC requirement Self Backhauling, integrated access and backhaul Network selection optimizations 8/29/

15 Selected requirements TS Limited backward compatibility with 4G, but not as much with 2G/3G: The 5G system shall support all EPS capabilities (e.g., from TSs , , , , , , , ) with the following exceptions: CS voice service continuity and/or fallback to GERAN or UTRAN, seamless handover between 5G-RAN and GERAN, seamless handover between 5G-RAN and UTRAN, and access to a 5G core network via GERAN or UTRAN. 8/29/

16 Selected requirements TS Security The 5G system shall support operator controlled alternative authentication methods (i.e., alternative to AKA) with different types of credentials for network access for IoT devices in isolated deployment scenarios (e.g., for industrial automation). For a private network using 5G technology, the 5G system shall support network access using identities, credentials, and authentication methods provided and managed by a 3rd party and supported by 3GPP. The 5G system shall be able to protect subscriber identity and other user identifying information from passive attacks. The 5G system shall be able to protect subscriber identity and other user identifying information from active attacks. The 5G system shall be able to support identification of subscriptions independently of identification of equipment. 8/29/

17 Selected requirements TS Wireless self-backhauling The 5G network shall enable operators to support wireless self-backhaul using New Radio (NR) and E-UTRA. The 5G network shall support flexible and efficient wireless self-backhaul for both indoor and outdoor scenarios. The 5G network shall support flexible partitioning of radio resources between access and backhaul functions. The 5G network shall support autonomous configuration of access and wireless selfbackhaul functions. The 5G network shall support multi-hop wireless self-backhauling to enable flexible extension of range and coverage area. The 5G network shall support autonomous adaptation on wireless self-backhaul network topologies to minimize service disruptions. The 5G network shall support topologically redundant connectivity on the wireless self-backhaul to enhance reliability and capacity and reduce latency. 8/29/

18 Selected requirements TS /29/2017 Provisioning and network selection Based on operator policy, the 5G system shall support a mechanism to provision ondemand connectivity (e.g. IP connectivity for remote provisioning). This on-demand mechanism should enable means for a user to request on-the-spot network connectivity while providing operators with identification and security tools for the provided connectivity. The 5G system shall support a secure mechanism for a home operator to remotely provision the 3GPP credentials of a uniquely identifiable and verifiably secure device used for IoT purposes. The 5G system shall support 3GPP Access Network Selection (PLMN selection), based on the Rel-14 principles documented in 3GPP TS [3]. The 5G system shall support selection among any available PLMN/RAT combinations, identified through their respective PLMN identifier and Radio Access Technology identifier, in a prioritised order. The priority order may, subject to operator policies, be provisioned in an Operator Controlled PLMN Selector lists with associated RAT identifiers, stored in the 5G UE. The 5G system shall support, subject to operator policies, a User Controlled PLMN Selector list stored in the 5G UE, allowing the UE user to specify preferred PLMNs with associated RAT identifier in priority order. 18

19 Selected requirements TS rd party slicing The 5G system shall allow the operator to create, modify, and delete a network slice. The 5G system shall allow the operator to define and update the set of services and capabilities supported in a network slice. The 5G system shall allow the operator to configure the information which associates a device to a network slice. The 5G system shall allow the operator to configure the information which associates a service to a network slice. The 5G system shall allow the operator to assign a device to a network slice, to move a device from one network slice to another, and to remove a device from a network slice based on subscription, device capabilities, operator's policies and services provided by the network slice. 8/29/

20 Selected requirements TS rd party slicing (cont) The 5G system shall allow the operator to authorize a 3rd party to create, modify and delete network slices, subject to an agreement between the 3rd party and the network operator. Based on operator policy, the 5G system shall provide suitable APIs to allow a 3rd party to monitor the network slice used for the 3rd party. Based on operator policy, the 5G system shall allow a 3rd party to define and update the set of services supported in a network slice used for the 3rd party. Based on operator policy, the 5G system shall allow a 3rd party to assign a device to a network slice based on subscription, device capabilities, and services provided by the network slice. Based on operator policy, the 5G system shall provide suitable APIs to allow a trusted 3rd party to adapt capacity, i.e., elasticity of capacity of a network slice used for the 3rd party. 8/29/

21 Selected requirements TS Subscription aspects An IoT device which is able to access a 5G PLMN in direct network connection mode using a 3GPP RAT shall have a 3GPP subscription. The 5G system shall allow the operator to identify a UE as an IoT device based on UE characteristics (e.g., identified by an equipment identifier or a range of equipment identifiers) or subscription or the combination of both. The 5G system shall be able to provide mechanisms to change the association between a subscription and address/number of an IoT device (e.g., changing the owner and subscription information associated with the IoT device) within the same operator and in between different operators in an automated or manual way. The 5G system shall be able to support identification of subscriptions independently of identification of IoT devices. Both identities shall be secure. 8/29/

22 Selected requirements TS Subscription aspects An IoT device which is able to connect to a UE in direct device connection mode shall have a 3GPP subscription, if the IoT device needs to be identifiable by the core network (e.g., for IoT device management purposes or to use indirect network connection mode). Based on operator policy, the 5G system shall support a mechanism to provision ondemand connectivity (e.g. IP connectivity for remote provisioning). This on-demand mechanism should enable means for a user to request on-the-spot network connectivity while providing operators with identification and security tools for the provided connectivity. The 5G system shall support a secure mechanism for a home operator to remotely provision the 3GPP credentials of a uniquely identifiable and verifiably secure IoT device. 8/29/

23 New Activities Study on LAN Support in 5G (FS_5GLAN) Study on positioning use cases (FS_5G_HYPOS) Study on enhancements of Public Warning System (FS_ePWS) Study on communication for Automation in Vertical Domains (FS_CAV) Feasibility Study on using Satellite Access in 5G (FS_5GSAT) Feasibility Study on enhancements to IMS for new RTC services (FS_enIMS) Feasibility Study on 5G message service for MIoT (FS_5GMSG) Feasibility Study on business models for network slicing (FS_BMNS) 8/29/

24 EPC -> 5G CORE WHAT s DIFFERENT? Stephen Hayes Director of North American Standards ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 24

25 5G Core ARCHITECTURE WORK Architecture Principles now agreed, but lots of details to be worked out 5G Core (Assumes new signaling towards the radio network): SA1 (Service) Work completed, except for alignments SA2 (Architecture) Normative Work to Complete Dec 2017 SA3 (Security) work to Complete March 2018 SA5 (Management) work started (but distributed) CT work starting EDCE5 (Reuses EPC signaling and assumes LTE network exists) To complete Sept 2017 ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 25

26 Comparison between EPC & 5GC - Standards view Feature Area EPC/EPS 5GC/5GS Stand-alone NR Not Supported Supported RAN deployment option 2 Network slicing Network architecture One DCN per UE DECOR/eDECOR separation APN separation within DCN Node based architecture 3GPP defined appl. protocols over IP CP/UP split with CUPS ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 26 Multiple simultaneous slices per UE UE assisted selection as in edecor Slice aware RAN Service Based Architecture Network Functions (NF) providing services to other NFs in Control Plane CP/UP split based on CUPS evolution Access Access dependent procedures AMF, SMF and UPF used for 3GPP & non-3gpp access Common N1/N2/N3 interfaces QoS QCI based bearers QoS Flow based framework incl Reflective QoS, Per packet marking & Separation of CN and AN QoS Session Management Mobility Policy Authentication Full IP session continuity or distributed connectivity through LIPA/SIPTO Same Mobility functionality for all subscriber categories LTE dormant modes (LTE Light connections) local in LTE RAN Charging and QoS based policies Proprietary access & mobility based policies Separate policy provisioning to UE for access nw selection EPS-AKA based user/subscriber authentication IMSI-based credentials Different Session continuity modes Full IP session continuity at the same time as distributed connectivity Access to Local Access Data Nws and Appl. Function influence on traffic routing Service area restriction (aka Mobility on Demand) concept Provides flexibility to cater for different subscriber categories RRC Inactive mode RAN dormant mode with data link setup time Unified policy framework Access & mobility based policies, charging and QoS based policies, and policy provisioning to UE Input to policies from Network Analytics (NWAD) EAP-AKA based user/subscription authentication Possibility to be based on alternative credentials than IMSI

27 NR STANDALONE SUPPORT REQUIRES THE 5G CORE ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 27

28 NETWORK SLICING Enhancements to the DECOR and edecor functionality of EPC. UE Selection A UE can be a member of up to 8 slices at a time RAN aware of slices Better resource isolation Standardized Slices for roaming (embb, URLCC, MIoT) ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 28

29 SERVICE BASED ARCHITECTURE Node to Node Protocols Network Services ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 29

30 Access INDEPENDENT FUNCTIONS Access and Mobility Function Generalized Session Management Function Generalized User Plane Functions Generalized N1/N2/N3 interfaces are common ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 30

31 QoS Replaced Bearer based QoS Model with Flow Based QoS Model Standardized and non-standardized QoS classes are possible Per Packet Marking Separation of CN and AN QoS handling ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 31

32 Session MANAGEMENT IP address preservation is now optional Separation of Session and Mobility management Service continuity and session continuity separation More flexibility in traffic routing ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 32

33 Mobility On demand mobility now possible (service area restrictions) Some mobility functions moved to RAN with introduction on RAN inactive connected state POLICY Unified Policy Framework that covers QoS, AMF, UE policies, etc. Network analytics as an input into policy ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 33

34 SECURITY Unified and access agnostic authentication architecture for SIM and SIM-less UEs based on Extensible Authentication Protocol (EAP) Framework Additionally, EPS-AKA* (an EPS-AKA version allowing higher HN control) will be also allowed Enhanced privacy protection (encryption) of subscription permanent identifier over air interface ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 34

35 ATIS 3GPP Webinar - 5G Core Network Ericsson Inc Page 35

36 5G RAN Features and Capabilities Dr. Emad Farag (Nokia Bell Labs) Senior 5G Physical Layer Standards Engineer August 29 th, ATIS 3GPP Webinar, 29-Aug-17

37 The 5G Vision September 2015: ITU-R articulates vision for international mobile telecommunications in 2020 and beyond. Diverse use cases, to enhance the networked society: - Enhanced Mobile Broadband (embb): to meet the ever increasing demand for higher data rates and new applications (Enhanced multi-media, VR/AR) - Ultra-Reliable Low Latency Communications (URLLC): to meet demand for industrial automation, driverless cars, etc - Massive Machine Type Communications (mmtc): to meet the demand of the internet of things with billions of connected devices Diverse deployment scenarios - Urban, sub-urban, rural, high-speed, non-terrestrial, etc. Diverse spectrum requirements - Diverse frequency range from sub-ghz to 100 GHz - Diverse spectrum licensing models: Licensed, unlicensed and shared bands - Diverse spectrum usage schemes: FDD, TDD, Dynamic TDD, CA, DC - Coexistence with legacy radio access technologies 10 Mbit/s/m 2 (100x) 3x Spectral Efficiency Low power Low cost Massive Communication 1 million device/km 2 (10x) Enhanced Mobile Broadband 20 Gbps (20x) Net efficiency (100x) Sub-1msec (10x) Ultra-reliable low latency High mobility: 500 Km/hr ITU: International Telecommunication Union ITU-R: ITU Radio sector FDD: Frequency Division Duplexing TDD: Time Division Duplexing CA: Carrier Aggregation DC: Dual Connectivity Page 37 ATIS 3GPP Webinar, 29-Aug-17

38 5G Standardization timeline in 3GPP Study Item New Radio (NR) addresses the ITU-R vision for IMT (also known as 5G) Study of NR took place in release 14, starting late 2015 to early 2017 Culminated in several TRs, addressing channel model, requirements and scenarios and feasibility study. SI: Study Item TR: Technical Report Page 38 Q Q4 Q1 Q2 Q3 Q4 Q1 3GPP Workshop on 5G TR expanded in TR to include frequencies from 0.5 GHz to 100 GHz TR SI: Channel Model above 6GH Scope ATIS 3GPP Webinar, 29-Aug-17 TR : Study on channel model for frequency spectrum above 6 GHz SI: Scenarios and req. for next gen RAT Q2 TR : Study on scenarios and requirements for next generation access technologies SI: New radio access technology 5G NR work item TR (Study on new radio access technology) & TRs /2/3/ Study on new radio access technology: Radio access architecture and interfaces Study on new radio access technology Physical layer aspects Study on new radio access technology: Radio Frequency (RF) and co-existence aspects Study on new radio access technology Radio interface protocol aspects

39 5G Standardization timeline in 3GPP Release 15 work item Release 15 NR work item: - Focus on urgent market needs for embb and URLLC. - Allow for forward compatibility for future releases - Backward compatibility to LTE is not required In March 17, RAN TSG agreed to accelerate the NR work item schedule: - Early drop of NSA complete by end of year - Keeping the schedule of SA (completion by Q2 2018) 2017 Q1 Q2 Q3 Q4 NR SI 2018 Q1 Q2 Q3 Q4 5G NR Phase 1 (Release 15) work item 5G NR Phase 2 study item 2019 Q1 Q2 Q3 Q4 5G NR Phase 2 (Release 16) work item ITU IMT-2020 Submission NSA: Non-Standalone TSG: Technical Specification Group Page 39 SA: Standalone ATIS 3GPP Webinar, 29-Aug-17 Source: RP

40 Release 15 NR Study Items 9 Release 15 NR study items approved in March/June RAN plenaries - RAN WG1-led study items Study on NR to support non-terrestrial networks Study on NR-based access to unlicensed spectrum Study on Non-Orthogonal Multiple Access (NOMA) for NR Study on evaluation methodology of new V2X use cases for LTE and NR - RAN WG2-led study items Study on integrated access and backhaul for NR - RAN WG3-led study items Study on separation of CP and UP for split option 2 for NR Study on CU-DU lower layer split for New Radio - RAN WG4-led study items Study of test methods for New Radio - Study on self-evaluation towards IMT-2020 submission Due to prioritization of the NR work item, the start of the RAN1 and RAN2 led study items have been postponed Page 40 ATIS 3GPP Webinar, 29-Aug-17

41 5G RAN Specifications 3G 25.xxx WCDMA/HSPA 38.8xx/38.9xx Study items TR Link to 3GPP WG4 specification 4G 5G 36.xxx LTE 38.xxx NR RAN WG4 RAN WG1 RAN WG2 38.1xx UE/BTS Requirements 38.2xx Physical Layer 38.3xx Radio Protocols Link to 3GPP WG1 specification : Physical Layer General description : Services provided by the physical layer : Physical channels and modulation : Multiplexing and channel coding : Physical layer procedures for control : Physical layer procedures for data : Physical layer measurements Link to 3GPP WG2 specification RAN WG3 38.4xx Architecture/Interfaces Link to 3GPP WG3 specification NR Specs currently in draft. Target completion by year s end. Page 41 ATIS 3GPP Webinar, 29-Aug-17

42 Radio Access Network Architecture Non-standalone NR Control-plan in E-UTRA Data plan in NR and E-UTRA Option 3 series uses EPC core Option 7 series uses NGC core Standalone NR Control-plan and data in NR (option 2) NR base station is known as gnb EPC NGC EPC NGC S1-C S1-U S1-C S1-U S1-U Xx-U E-UTRA Xx-C NR E-UTRA Xx-C NR Option 3 Option 3a E-UTRA-NR DC via EPC where the E-UTRA is the master EPC NGC NG2 NG3 E-UTRA NR Option 2 Early drop by end of year is option 3 series. Page 42 ATIS 3GPP Webinar, 29-Aug-17

43 RAN Logical Architecture Functional Split between central and distributed unit Source: Option 2 being standardized in release 15 Lower layer split is being studied in release 15 Page 43 ATIS 3GPP Webinar, 29-Aug-17

44 LTE vs NR Release 15 Feature LTE NR Release 15 Carrier Frequency Update 6 GHz Up to 52.6 GHz Uplink waveform DFT-S-OFDM DFT-S-OFDM and CP-OFDM Bandwidth Max 20 MHz Below 6 GHz:100 MHz Above 6 GHz: 400 MHz Spectrum Occupancy 90% of Channel BW 98% of Channel BW Subcarrier Spacing 15 KHz {15, 30, 60, 120, 240} KHz 240 for sync signals only Max FFT Size 2048 (up to 1200 SC) 4096 (up to ~3300 SC) Duplexing Scheme FDD and TDD (fixed) FDD and TDD (dynamic) Self Contained Slot Not supported Can be Supported PUCCH Duration 13 or 14 Symbols Long (4-14 Symbols) and Short PUCCH (1, 2 Symbols) HARQ Timing Fixed Flexible Channel Coding Data Channels: Turbo Ctl Channels: CC Number of MIMO layers 8 12 Number of CA Data Channels: LDPC Ctl Channels: Polar Page 44 ATIS 3GPP Webinar, 29-Aug-17

45 NR Waveform Waveform is based on OFDM - With scalable subcarrier spacing DL Waveform: CP-OFDM UL Waveform: - CP-OFDM: Supported in all cases - DFT-s-OFDM: Supported in case of single stream with low PAPR/CM (budget limited scenarios) - No 7.5 KHz frequency shift in uplink UL: CP-OFDM DFT-s-OFDM Waveform DL: CP-OFDM OFDM: Orthogonal Frequency Division Multiplexing CP-OFDM: Cyclic Prefix OFDM PAPR: Peak-to-Average Power Ratio DFT-s-OFDM: Discrete Fourier Transform Spread OFDM Page 45 ATIS 3GPP Webinar, 29-Aug-17

46 NR frame structure and numerology Scalable Numerology Sub-carrier spacing (SCS): 15 KHz x 2 N N Subframe 0 Duration 1 ms = 0 5 Higher SCS for larger BW Higher SCS for lower latency Slot 0 Subframe 1 Subframe 9 NCP: 14 Symbols Slot M -1 Lower SCS more delay spread robust ECP: 12 Symbols Extended CP supported for 60 KHz. N NR Frame Structure M 2 More delay spread robust Additional 16 Ts added to CP of first OFDM symbol every 0.5 ms for NCP Support Mini-Slots Mini Slot: smallest scheduled unit Mini-slot is 1 or more symbols Support low latency operation Scalable numerology to adapt to carrier frequency, deployment scenario and use case CP OFDM Symbol 0.5 ms Frame: Duration 10 ms Symbol boundary alignment across numerologies, with same CP overhead Page 46 ATIS 3GPP Webinar, 29-Aug-17

47 NR Bandwidth and Waveform Maximum NR carrier BW: - Below 6 GHz: 100 MHz - Above 24 GHz: 400 MHz Minimum possible NR carrier BW: - Below 6 GHz: 5 MHz - Above 6 GHz: 50 MHz SCS per frequency range in NR - Below 1 GHz: 15 and 30 KHz [FFS 60 KHz] - Between 1 and 6 GHz: 15, 30 and 60 KHz - Between 24 and 52.6 GHz: 60 and 120 KHz 240 GHz not considered for data - Other SCS can be added in later releases. Example LTE NR R15 SCS 15 KHz 120 KHz Subcarriers FFT Size 2K 4K Transmission BW 18 MHz 392 MHz Channel BW 20 MHz 400 MHz Spectrum Utilization 90% 98% Peak throughput (8x8 MIMO 256 QAM) 0.8 Gbps 17.3 Gbps Increased FFT size and subcarrier spacing increases channel bandwidth by 20x Increased spectrum utilization allows for more efficient use of spectrum Page 47 ATIS 3GPP Webinar, 29-Aug-17

48 Synchronization Signals and Broadcast Channel Designed to handle multi-beam deployments - Transmission organized in SS Blocks (Synchronization Signal Blocks) - Transmission period of SS blocks is half a frame (5 ms) - More SS blocks in mmwaves to support more beams PSS PBCH SSS PBCH 4-Symbol SS/PBCH Block For carrier frequencies <= 3GHz, there are up to 4 SS/PBCH blocks per half a frame For carrier frequencies > 3 and <= 6GHz, there are up to 8 SS/PBCH blocks per half a frame For carrier frequencies > 6GH, there are up to 64 SS/PBCH blocks per half a frame SS Burst Period SS Burst Duration < 5 msec Page 48 ATIS 3GPP Webinar, 29-Aug-17

49 SS Block Time Structure Pattern selected to: Allow LTE coexistence Support TDD Mixed data and sync numerology One SCS pattern selected per band Burst duration 5ms to limit UE on time. Burst set period can be between 5 to 160 ms SS Burst = 5ms SCS = 15 KHz L=4,8 SCS = 30 KHz L=4,8 1ms SCS = 15 KHz L=4,8 SCS = 30 KHz L=8 SS Burst Set Period SCS = 15 KHz L=8 SCS = 15 KHz L=8 SCS = 15 KHz: 2 SS Blocks per 14 Symbols (1ms) SCS = 30 KHz Pattern 1: 4 SS Blocks per 14 Symbols (1ms) SCS = 30 KHz Pattern 2: 4 SS Blocks per 14 Symbols (1ms) For frequency range less than 6 GHz SS Burst = 5ms No Sync blocks Page 49 ATIS 3GPP Webinar, 29-Aug-17

50 Random Access Channel 4-step RACH procedure as in LTE RACH use cases include: - Initial access in single/multi-beam systems - Handover - Beam recovery - On-demand SI Association of sync blocks to RACH resources and/or preamble indices - Handle scenarios with and without beam correspondence at gnb and UE - UE selects RACH resource/preamble index based on DL SS block measurements Tx Beams PRACH sequence design - Long sequence (L=839 (as in LTE)). Subcarrier spacing: 1.25 and 5 KHz For large cells and high speed trains - Short sequence (L=127 or 139) Subcarrier spacing: - Sub-6GHz: 15 and 30 KHz - mmwave: 60 and 120 KHz. SCS can be the same as data to simplify the receiver design Short PRACH for efficient multi-beam system support Rx Beams SSB0 SSB1 SSB2 SSB3 RR0 RR1 RR2 RR3 SS Blocks Association RACH Resources Page 50 ATIS 3GPP Webinar, 29-Aug-17

51 NR MIMO Support different antenna schemes - Analog beamforming - Hybrid beam forming - Digital beam forming Beam management procedures: - Beam determination, beam measurement, beam reporting and beam sweeping - Beam recovery procedure including: beam failure detection, new beam identification and beam recovery request. Multi-antenna schemes - SU-MIMO and MU-MIMO - Up to two codewords in DL Reference Signals - UL reference signals Demodulation RS (DMRS) Sounding reference signals (SRS), Phase tracking RS (PT-RS) - DL reference signals such as: Demodulation RS (DMRS) Channel State Information RS (CSI-RS) Phase tracking RS (PT-RS) Time/frequency tracking RS (TRS) CSI Feedback - Type 1: Normal Feedback At least two stage precoding: W = W 1 W 2 W 1 compromises of wideband beam groups/vectors With 3D MIMO, W 1 is the Kronecker product of vertical and horizontal components W 2 is for sub-band beam selection and beam cophasing - Type 2: Enhanced feedback Explicit feedback and/or codebook-based feedback with higher spatial resolution. Page 51 ATIS 3GPP Webinar, 29-Aug-17

52 HARQ and Scheduling enabling technologies Different slot types Support FDD/TDD and Dynamic TDD 14-Symbol Slot Flexible HARQ Timing & Asynchronous DL/UL HARQ K0 K1 K3 DL Slot UL Slot Bi-directional DL Slot Bi-directional UL Slot Dc Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Dd Dd Uc Uc Dc Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Gp Uc Dc Dc Gp Ud Ud Ud Ud Ud Ud Ud Ud Ud Uc Dc DL Control Dd DL Data Uc UL Control Ud UL Data Gp Gap Uc DL Assign UL Grant K2 DL Data HARQ ACK UL Data DL Data Flexible K0, K1, K2 and K3. Lower latency than LTE. Future proofness, multi-beam support, UE capability Bi-directional Slot Front-loaded Control Front-loaded DMRS Self contained slot Dc Dc RS Dd Dc RS Dd Gp Uc DL Assignment Dd Dd Dd Slot Dd Dd Dd PDCCH: DL Assignment PDSCH Reference signal PDSCH Gap PUCCH: HARQ-ACK HARQ-ACK Dd Dd Gp Uc URLLC Aspects Requirements: 0.5 ms average latency % 1ms latency Higher SCS lower TTI Mini-slot support UL: grant free (re) transmission UL: multiple autonomous retransmissions UL: Short SR (Scheduling Request) period DL: Preemption of on going transmissions Page 52 ATIS 3GPP Webinar, 29-Aug-17

53 NR Channel Coding Key requirements to consider: Performance Implementation complexity (J/bit, Gbps/unit area) Latency Flexibility (variable block size and code rate, HARQ support) embb Channel Coding Schemes Data LDPC Control btw 3 and11 bits: LTE RM Control more than 11bits: Polar LDPC coding: Used for data channels Provides implementation and latency advantages over other coding schemes Supports incremental redundancy and chase combining HARQ. Polar coding: Through successive combining of binary channels, channels are polarized; some channels capacity approach 1, these are used for data transmissions, others approach zero, these are frozen bits. Maximum code block size: - DL control channels: UL control channels: 1024 Page 53 ATIS 3GPP Webinar, 29-Aug-17

54 Future compatibility Enablers for future compatibility Asynchronous downlink and uplink HARQ with dynamic indication of the HARQ timing Minimization of the transmission of always on signals By-directional sub frames and dynamic TDD Self-contained slots Indication of reserved resources for future use cases. Page 54 ATIS 3GPP Webinar, 29-Aug-17

55

56 Thank you for attending the ATIS 3GPP Webinar Registered attendees will receive a follow up containing links to the recording and slides from this presentation. For more information about ATIS or 3GPP, please contact Rich Moran, rmoran@atis.org 56