Anritsu - Webinr - 5G - Release15 - Feb 2019 (1) - 10216 - 20190212120402244

Understanding details of
3GPP Release 15 5G-NR
Image Size
W195 x H530 px
Technology Presentation
12th February 2019
Vikas Chauhan
Business Development Manager, Anritsu EMEA
Contents
1. Standardisation activities and deployment (2
slides)
2. 5G NR key concepts (10 slides)
3. 5G NR PHY Layer (22 slides)
4. 5G NR Protocol Stack (16 slides)
5. NSA Protocol Architecture (6 slides)
Understanding details of 3GPP Release 15 5G NR

2 Copyright© ANRITSU
3GPP Schedule and Milestones for 5G
5G System Phase 1 and Phase 2
3GPP is delivering Release 15 to the industry in 3 distinct steps:

‘Early’ drop: contains Non-standalone 5G specifications (so called Option-3 family), ASN.1 frozen in March 2018;
‘Main’ drop: contains Standalone 5G (so called Option-2), ASN.1 frozen in September 2018;
‘Late’ drop: contains additional migration architectures (so called Option-4, Option-7, and 5G-5G dual connectivity), ASN.1 to be
frozen in June 2019.

Summary of Deployment Options
NG RAN (gNB and/or ng-eNB) with 5G Core or 5G EPC
CONFIDENTIAL
Contents
1. Standardisation activities and deployment(2
slides)

5G New Radio – Designed for Both Sub6 and mmWave
• Operation from low to very high bands: 0.4 – 100Ghz

 Including standalone operation in unlicensed bands
• Set of different numerologies for optimal operation in different frequency ranges
• Native forward compatibility mechanisms
• Ultra wide bandwidth
 Up to 100MHz in <6GHz
 Up to 400MHz in >6GHz
• New channel coding
 LDPC for data channel, Polar coding for control channel
• Native support for Ultra Reliable Low Latency
• Flexible and modular RAN architecture: split front haul, split C-U plane
• Native end-to-end support for Network Slicing
 Scalable TTI
 Dynamic Switching between DL and UL based on traffic conditions

5G NR Scalable Numerology
Scaling of subcarrier spacing (SCS) as per need FR1/FR2.
Change of sub-carrier spacing is possible, changing numerology “μ”.
Change of “μ” changes data rate on the sub-carrier,

hence symbol (bit) rate.
Supported transmission numerologies.

NR Frame Structure
• Single frame structure
 Applicable to FDD and TDD
One frame, Tframe = 10 ms
• Dynamic TDD baseline

 Possible to semi-statically configure
UL/DL split One subframe, Tsubframe = 1 ms
#0 #1 #2 #3 #4 #5 #6 #7 #8 #9
• 15 kHz slot identical to LTE

subframe
 Including extra samples in every 7th Δf=15 kHz
symbol One slot, 1 ms
Δf=30 kHz
One slot, 0.5 ms
Δf=60 kHz
One slot, 0.25 ms
Δf=120 kHz
One slot, 0.125 ms
Δf=240 kHz
One slot, 0.0625 ms

NR Frame Structure
Transmissions not restricted to slot boundaries
Transmissions restricted to slot boundaries Transmissions not restricted to slot boundaries
Data arrival One slot Data arrival
Long latency Short latency
Unused
Channel available Channel available

Dummy data Useful data Useful data Useful data
Efficiency loss

Resource Grid/Block/Element One Subframe
• One resource grid per numerology and

antenna port and transmission direction
(Downlink or Uplink)
• Resource block = 12 subcarriers

 One dimensional unit (unlike LTE)
• Resource element = 1 subcarrier in one

OFDM symbol

Bandwidths
• Up to 400 MHz component-carrier bandwidth (20 MHz for LTE)
• Up to 16 component carriers
 Overall bandwidth depends on frequency band
• Not all devices must support the full network carrier bandwidth
LTE NR
All UEs support full carrier BW A UE can support less than the carrier BW
20 MHz Up to 400 MHz

5 (later 32) component carriers Up to 16 component carriers

Bandwidth Adaptation & Bandwidth Part
• The receive and transmit bandwidth of a UE need not be as large as the bandwidth of the cell
and can be adjusted:
 the bandwidth can be ordered to change (e.g. to shrink during period of low activity to save power);
 the location can move in the frequency domain (e.g. to increase scheduling flexibility);
 the subcarrier spacing can be ordered to change (e.g. to allow different services).
• A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and BA
is achieved by configuring the UE with BWP(s) and telling the UE which of the configured
BWPs is currently the active one.
frequency
BWP3
20MHz/60kHz
BWP1 BWP2
40MHz 2 1 ...
10MHz/15kHz
15kHz
time

Contents
slides)

5G NR - Downlink Physical Layer
Physical channels
A downlink physical channel corresponds to a set of resource elements carrying information originating
from higher layers. The following downlink physical channels are defined:
• Physical Downlink Shared Channel, PDSCH
 Mapped to Downlink Shared Channel DL-SCH (Transport Channel)
 Mapped to Paging channel PCH (Transport Channel)
• Physical Broadcast Channel, PBCH
 Mapped to Broadcast channel BCH (Transport Channel)
• Physical Downlink Control Channel, PDCCH
Physical signals
A downlink physical signal corresponds to a set of resource elements used by the physical layer but
does not carry information originating from higher layers. The following downlink physical signals are
defined:
• Demodulation reference signals, DM-RS
• Phase-tracking reference signals, PT-RS
• Channel-state information reference signal, CSI-RS
• Primary synchronization signal, PSS
• Secondary synchronization signal, SSS
Physical resources
The following antenna ports are defined for the downlink:
• Antenna ports starting with 1000 for demodulation reference signals associated with PDSCH
• Antenna ports starting with 2000 for demodulation reference signals associated with PDCCH
• Antenna ports starting with 3000 for channel-state information reference signals
• Antenna ports starting with 4000 for SS/PBCH block transmission

5G NR - Uplink Physical Layer
Physical channels
An uplink physical channel corresponds to a set of resource elements carrying information originating
from higher layers. The following uplink physical channels are defined:
• Physical Uplink Shared Channel, PUSCH
 Mapped to Uplink Shared Channel UL-SCH (Transport Channel)
• Physical Uplink Control Channel, PUCCH
• Physical Random Access Channel, PRACH
 Mapped to Random access channel RACH (Transport Channel)
Physical signals
An uplink physical signal is used by the physical layer but does not carry information originating from
higher layers. The following uplink physical signals are defined:
• Demodulation reference signals, DM-RS
• Phase-tracking reference signals, PT-RS
• Sounding reference signal, SRS
Physical resources
The following antenna ports are defined for the uplink:
• Antenna ports starting with 0 for demodulation reference signals associated with PUSCH
• Antenna ports starting with 1000 for SRS, PUSCH
• Antenna ports starting with 2000 for PUCCH
• Antenna ports starting with 4000 for PRACH

LTE vs NR Reference Signals
• LTE has a ‘one size fits all’ downlink reference signal design: CRS
 Limits flexible network deployments, not network energy efficient, not applicable for higher spectrum (>6GHz),
not MIMO friendly for large number of antennas
• NR downlink reference signals are tailored for specific roles and can be flexibly adapted for
different deployment scenarios and spectrum
NR (Rel-15) downlink
LTE (Rel-8) downlink reference signals
reference signals
Synchronization
(TRS)
Synchronization
(CRS)
Demodulation
(DM-RS)
Demodulation
Channel State
(CRS)
Information
Channel State Measurement
Information (CSI-RS)
Measurement Phase Noise
(CRS) Compensation TRS: Tracking RS
Phase Noise (PT-RS) DMRS: DeModulation RS
Compensation CSI-RS: Channel Status Info RS
(CRS) CRS: Cell-Specific RS PT-RS: Phase Tracking RS

LTE vs NR: Functions of SS & RS

NR Reference Signals: DM-RS
Designed for downlink/uplink channel estimation  coherent demodulation
• NR supports two different types of DMRS

NR Reference Signals: CSI-RS / TRS
CSI-RS is designed for downlink measurement  reporting channel status info
• Three different types of CSI-RS is supported: Periodic, aperiodic, and semi-persistent CSI-RS
Periodic CSI-RS Aperiodic CSI-RS Semi-Persistent CSI-RS

Orthogonal
Up to 32 Up to 32 Up to 32
Ports
Time domain Periodic transmission once Periodic transmission once
Single transmission when triggered
behavior configured activated until deactivated
Activation
RRC signaling L1 signaling MAC CE
/Deactivation
Hybrid of periodic and aperiodic
Characteristics No L1 overhead Low latency
CSI-RS
TRS is designed for time/frequency tracking and estimation of delay/Doppler spread

• Configured as a CSI-RS with specific parameter restriction (time/freq location, RE pattern, etc)

NR Reference Signals: PT-RS
PT-RS is designed for compensation of downlink/uplink phase noise compensation
• ‘Associated’ with DM-RS so that receiver can compensate for phase noise during demodulation
• PT-RS density in time, frequency is associated with scheduled MCS, bandwidth, respectively
Scheduled MCS Time domain density
0 <= MCS < MCS1 No PTRS
MCS1 <= MCS < MCS2 Every OFDM symbol
MCS2 <= MCS < MCS3 Every 2nd OFDM symbol
MCS3 <= MCS < MCS4 Every 4th OFDM symbol

Every OFDM symbol Every 2nd OFDM symbol Every 4th OFDM symbol
Scheduled BW
Scheduled bandwidth Frequency domain density
0 <= NRB < NRB1 No PTRS

Every 2nd RB
NRB1 <= NRB < NRB2 Every 2nd RB
NRB2 <= NRB Every 4th RB

Every 4th RB

NR Reference Signals: SRS
SRS is designed for evaluation of uplink channel quality and timing
• Can also be used for downlink channel information when channel reciprocity is applicable
• Three different types of SRS is supported: Periodic, aperiodic, and semi-persistent SRS (same time
domain behavior as that of CSI-RS)
• SRS carrier switching is supported for transmitting SRS over more than one carrier using a single
uplink transmitter
• Up to 6 OFDM symbols can be used for SRS transmission to increase SRS capacity
compared to LTE (Rel-8 LTE supports up to 1 OFDM symbol)
Frequency
RB
PUSCH only
SRS/PUSCH 0 1 2 3 4 5 6 7 8 9 10 11 12 13
Slot

Transport-Channel Processing
• Overall transport-channel processing resembles LTE
• Main differences: One (or two) transport block(s) of dynamic

size delivered from the MAC layer
 LDPC coding
 Multi-antenna handling CRC
 OFDM and DFTS-OFDM in UL LDPC coding
Rate matching, hybrid-ARQ
Scrambling
Modulation
Layer mapping
Transform precoding
(UL only)
Multi-antenna precoding
Resource mapping
Physical antenna mapping

Hybrid ARQ
• Similar to LTE
• Possibility for per-CBG retransmission
• Asynchronous in DL and UL (up to 16 processes)
Transport block
CBG
0 1 0 0 CBGTI
Only this CBG is retransmitted
To soft combining Flushing of soft buffer controlled by CBGFI

PDCCH Processing
• Similar processing chain as for LTE
 Polar coding Downlink Control Information

K bit payload
Larger CRC
24-bit CRC
attachment 140 bits
• Each PDCCH NULL K bit payload 24-bit CRC
CRC
 Independently processed interleaver
 Has its own DM-RS +

RNTI
RNTI RNTI
encoding
Polar
coding
Rate
matching
No puncturing Puncturing Shortening Repetition
Scrambling
QPSK
DM-RS
Mapping to resource elements

Downlink L1/L2 Control Signaling
• Downlink Control information (DCI), transmitted on DCI format Usage
PDCCH 0_0 Scheduling of PUSCH in one cell
0_1 Scheduling of PUSCH in one cell
 Similar usage as in LTE (scheduling, …)
1_0 Scheduling of PDSCH in one cell
• PDCCH 1_1 Scheduling of PDSCH in one cell
2_0 Notifying a group of UEs of the slot format
 The only type of L1/L2 control channel in NR
Notifying a group of UEs of the PRB(s) and
 No PCFICH or PHICH (not needed in NR) 2_1 OFDM symbol(s) where UE may assume no
transmission is intended for the UE
• Main difference compared to LTE
Transmission of TPC commands for PUCCH
 Possibility for beamforming 2_2
and PUSCH
 Not necessarily spanning full carrier bandwidth 2_3
Transmission of a group of TPC commands for
SRS transmissions by one or more UEs
• CORESET (Control Resource Set)

CORESET #4
 Time-frequency region where the UE monitors for PDCCH
transmission CORESET #3
 Multiple CORESETs can be configured in a UE using RRC

CORESET #2
signaling
 CORESET0 obtained from MIB CORESET #1
 Not necessarily located at the beginning of the slot

 Frequency span in multiples of 6 RB one slot
 Time span of 1, 2, or 3 OFDM symbols
 CORESET resources can be reused for data
• Search spaces Set of REGs CCE-to-REG Set of CCEs Search space
Search space
PDCCH candidate
PDCCH candidate
mapping Search space PDCCH candidate
 Set of CCEs upon which the UE tries to blindly detect PDCCH
transmissions
 One PDCCH transmitted using aggregation level 1, 2, 4, 8, or
16 CCEs

DM-RS and QCL
• Each PDCCH has its own DM-RS…but possible to configure ‘wideband RS’
 DM-RS on every 4th subcarrier
CORESET CORESET
DM-RS for all

PDCCHs in the
DM-RS for CORESET
PDCCH #2
REGs for REGs for
PDCCH #2 PDCCH #2
DM-RS for
PDCCH #1
REGs for REGs for
PDCCH #1 PDCCH #1
Normal case – DM-RS per PDCCH Wideband RS
• Can configure TCI states (QCL relations) per CORESET

 If none configured – assume QCL with SS block
CORESET #1: CSI-RS #1 QCL:ed with DM-RS

CORESET #2: CSI-RS #2 QCL:ed with DM-RS
one slot

Blind Decoding
• Blind decoding of PDCCH using search spaces and DCI formats
 Similar concept as in LTE
 Aggregation level 1, 2, 4, 8, or 16
• Flexible configuration of when, what formats, and what aggregation levels to monitor
CORESETs with search spaces for aggregation level 2 monitored

one slot
No monitoring in this occasion of the search space Aggregation level 4 monitored No monitoring in this occasion of the search space

Uplink L1/L2 Control Signaling
• UCI on PUCCH (no simultaneous data) or PUSCH ( simultaneous data, ‘UCI on PUCCH’)
 Hybrid-ARQ acknowledgements, channel-state information, scheduling request
• PUCCH not necessarily at carrier edges (as in LTE)

 DCI can indicate the resource to use for UCI
• Beamforming support: spatial relations between PUCCH and downlink signals can be
configured
 MAC-CE used to switch between different configurations
• PUCCH on Pcell (or PScell) in case of CA, similar to LTE
PUCCH group 1 PUCCH group 2

Pcell PScell
Feedback signaling

PUCCH Formats
• Five different PUCCH formats
• All designed with low PAPR in mind, can be used irrespective of PUSCH waveform
Payload Short (1-2 OFDM symbol) Long (4 – 14 OFDM symbols)
≤2 bits PUCCH format 0 PUCCH format 1

>2 bits PUCCH format 2 PUCCH formats 3 and 4
• PUCCH timing and resources indicated in the DCI

 In essence ‘scheduling’ of PUCCH
Downlink Downlink Uplink
control data ACK
slot
ΔT2
ACK timing ΔT3

Index 3
Index Offset
0 ΔT0
1 ΔT1
2 ΔT2
3 ΔT3
… …
RRC-configured table

Cell Search and System Information Acquisition
• SS Block (SSB)
 PSS and SSS to obtain synchronization
 PBCH for (parts of) system information
• Main difference compared to LTE

 Less frequent PSS/SSS/PBCH transmission (20 ms periodicity)
 Support for beamforming
 Minimize “always on” broadcasting of system information
(possibility for “on demand” delivery)
One OFDM symbol
• Subcarrier spacing for SS Block depends on frequency band
Numerology SSB bandwidth SSB duration Frequency range
15 kHz 3.6 MHz ≈285 µs FR1 < 3GHz

30 kHz 7.2 MHz ≈143 µs FR1
120 kHz 28.8 MHz ≈36 µs FR2
240 kHz 57.6 MHz ≈18 µs FR2
• SS Block not necessarily at the center of the carrier (as in LTE)

 Reason: allow for a search raster sparser than the frequency raster
 Note: SS block not necessarily aligned with the resource block grid
SSB
Frequency raster
Search raster
SS Block and Beam Sweeping
• SS burst set
Frequency range SS blocks per SS burst set
 Multiple SS blocks in different beams
– 3 GHz 4
3 – 6 GHz 8
mm-wave 64
One SS burst set
5 ms
SB #1 SB #2 SB #L SB #1 SB #2 SB #L
SB #3
SS burst set period (default 20 ms)

Beam Establishment
• Different SS block time indices are associated with different RACH time/frequency
occasions
 SIB1 provides “number of SS-block time indices per RACH time/frequency occasion”
 SSB time indices associated with RACH occasions,

first in frequency, then in time within a slot, and last in time between slots
RACH slot #0 RACH slot #1
: One RACH occasion

Multi-Beam Operation in NR

Comparison of NR-MIMO vs LTE MIMO
LTE Rel-8 LTE-A Pro Rel-15 NR Rel-15

• Coverage enhancement
• Spectral efficiency • Spectral efficiency (especially for above 6GHz)
Purpose
enhancement enhancement • Spectral efficiency
enhancement
• Beam measurement, reporting
Multi-beam
• No specification support • No specification support • Beam indication
operation
• Beam failure recovery
• Up to 4 layers per UE • Up to 4 layers per UE • Up to 4 layers per UE
Uplink
• Up to 8 layers for MU-MIMO • Up to 8 layers for MU-MIMO • Up to 12 layers for MU-MIMO
transmission
(cyclic shifts for ZC-sequence) (cyclic shifts for ZC-sequence) (orthogonal ports)
• Up to 8 layers per UE • Up to 8 layers per UE
Downlink
• Up to 4 layers per UE • Up to 4 layers for MU-MIMO • Up to 12 layers for MU-MIMO
transmission
(orthogonal ports) (orthogonal ports)
• Configurable pattern,
• Fixed pattern, overhead • Fixed pattern, overhead overhead
Reference
• Up to 4 TX antenna ports • Up to 32 TX antenna ports • Up to 32 TX antenna ports
signal
(CRS) (CSI-RS) (CSI-RS)
• Support for above 6GHz

Channel Status Info: Type-I & Type-II
Two different Channel Status Information (CSI) types are supported in NR
• Type-I which is optimized for Single User MIMO transmission with smaller uplink overhead
• Type-II which is optimized for Multi-User MIMO transmission with finer channel information and as a
consequence, larger uplink overhead
Type-I Channel Status Information Type-II Channel Status Information

Beam
selection b2 p2
Co-phase 1 3
b0
0
selection b1 a2 1
w   ai pi bi
bi W1 W2
a1 p1 i 0
W1 W2 1 b 
 w i  b3
a3 p3
 bi 
0
b0, b1, b2, b3 1 Co-phasing and

Amplitude
scaling linear combination
Beam group selection
Terminal selects beam and co-phase (relative phase Terminal selects multiple beams, amplitude scaling, and phase
difference between X-pol antennas) coefficient coefficients for linear combination between the beams

Contents
slides)

RRC/NAS: UE State Transitions

RRC Layer Functions
• RRC connection control: establishment, reconfiguration and release of the RRC connection
• Initial security activation, i.e. initial configuration of integrity protection and ciphering in RAN (SRBs, DRBs)
• INACTIVE state management

 suspension/resumption of RRC connection
• Mobility related: Handover, measurement configuration/reporting
• Failure recovery
• System information broadcast and acquisition

 On demand SI transfer – network does not always have to broadcast SI, saves network energy and resources
• Access class barring and overload handling

 Unified Access Control mechanism different from LTE, providing similar functionality
• Paging similar to LTE

 Paging occasion calculation formula updated to consider NR PHY and is S-TMSI based
• Positioning
 UE operating in NR can obtain position using LTE signals and RAT independent methods
 No support for native NR methods in Rel-15 other than E-Cellid
• UE capability transfer
 Similar to LTE with storage in AMF
 The UE capabilities in NR do not rely on UE categories: UE categories associated to fixed peak data rates are only
defined for marketing purposes and not signalled to the network. Instead, the network determines the UL and DL data
rate supported by a UE from the supported band combinations and from the baseband capabilities (modulation scheme,
MIMO layers, …).
• ANR/SON (but no MDT in Rel-15)

RRC: Connection Establishment
• Procedurally similar to LTE
 RRC connection request, setup, setup complete
 Nx connection establishment with 5GC with UE context and capability transfer
 Security configuration
 DRB setup
 Idle to connected delay different compared to LTE
o 5GC NAS service request message design is different and larger than EPC
UE gNB 5GC
UE in RRC_IDLE
RACH
RACH response
RRCConnectionRequest
RRCSetup
RRCSetupComplete
Establish Nx connection,
UE context transfer,
UE capability transfer,
Security setup
DRBSetup
UE in RRC_CONNECTED
/ CM-CONNECTED

RRC: Security
• Security establishment procedure will be the same as in LTE
• Key differences:
 Integrity protection to be supported for DRB
o Data failing Integrity protection to be discarded
 Both ciphering and integrity protection is configurable per DRB

o Certain PDU sessions may not security
 Every handover may not need a key change

o Change of keys expected only if there is change in Central Unit (CU) (i.e., PDCP location) for split
CU/DU RAN

RRC: Mobility
• Mobility procedures also similar to LTE
 No procedural changes/optimisations for Handover or inter-RAT mobility compared to LTE in

Rel-15
o Main changes are to UE measurements based on NR PHY
 Idle mode: Similar to LTE

o Priority based mechanisms of LTE re-used
 Applicable also for INACTIVE
o Changes required to support NR PHY for cell reselection measurements

New RRC_INACTIVE State
• Significant delay reduction in INACTIVE to CONNECTED compared to IDLE to
CONNECTED
• Reduce the signalling overhead (on radio and network interfaces), enabling UE power
consumption similar to IDLE while improving the UE access latency
• Key aspects:
 UE context storage in in RAN during INACTIVE
o UE context stores both 5GC information including security and UE radio configurations
o allowing transitions between INACTIVE and CONNECTED without involving Core Network
o UE centric mobility, e.g. cell (re)-selection in INACTIVE
 Transitions between Inactive and Connected, and mobility while in Inactive are hidden from CN

RRC: State Transitions
• INACTIVE  CONNECTED
 3-step RRC procedure
RRC_CONNECTED
• CONNECTED  INACTIVE Release with

Release
suspend
 1-step RRC procedure
Resume
Reject
• INACTIVE  IDLE RRC_INACTIVE

 2-step RRC procedure for RNAU (request/release)
 Autonomously by UE:
Release Setup
o Upon reception of CN initiating paging
o Upon reselecting to other RAT
RRC_IDLE

RRC: RAN-Initiated Paging and RNA Update
RRC_INACTIVE is characterized by:
• Use of RAN Notification Area (RNA) for RAN Notification

CN
INACTIVE Area (RNA)

 similar to CN tracking area for Idle
NG-C/U associated UE in RRC_INACTIVE is
with the UE in seen as CN CONNECTED
• RNA is configured per UE by gNB gNB
RRC_INACTIVE
 1 to N cells defined by a List of cells or list of RAN
Area ID or list of TA IDs
gNB stores the UE AS
gNB Context (including an
• UE is reachable within a configured RNA via a associated UE s identifier)
RAN-initiated paging gNB

 RAN-initiated paging uses a RAN configured UE ID
(I-RNTI)
UE in gNB
RRC_INACTIVE RAN-initiated paging
• RNAU triggered periodically and when moving mechanism sent over
Xn and radio interface
outside of the configured RNA

RRM
Overall measurement framework is similar to LTE except beam related aspects.
• Three measurement types: intra-frequency, inter-frequency, inter-RAT measurements for E-UTRA
• The association between a measurement object and a reporting configuration is created by a

measurement identity
• Reference signal: SSB for idle mode; SSB and/or CSI-RS for Connected mode
• Beam level measurement and reporting

 The UE measures multiple beams of a cell and derive the cell quality from the multiple beams
 Measurement reports may contain beam results (beam identifier only, measurement result and beam identifier,
or no beam reporting) in addition to cell quantities
• Measurement gap
• Non-gap-assisted or gap-assisted depends on the capability of the UE, the active BWP of the UE and the
current operating frequency

Measurement Model in RRC_CONNECTED State
In RRC_CONNECTED, the UE measures multiple beams (at least one) of a cell and the measurements
results (power values) are averaged to derive the cell quality. In doing so, the UE is configured to consider a
subset of the detected beams.
Filtering takes place at two different levels: at the physical layer to derive beam quality and then at RRC
level to derive cell quality from multiple beams.
RRC configures
RRC configures RRC configures
parameters
parameters parameters
UE
UE Implementation
Implementation
specific
specific
A A1
gNB beam 1 Layer1 filtering C
Beam B Layer 3 Evaluation of
gNB beam 2 Layer1 filtering D
Consolidation/ filtering for cell reporting
Cell quality 1
Selection quality C criteria
gNB beam K Layer1 filtering
K beams
K beams L3 Beam filtering
L3 Beam filtering Beam Selection X beams
for reporting
L3 Beam filtering
E F
RRC configures RRC configures

parameters parameters
Understanding details of 3GPP Release 15 5G NR46

Layer 2 Structure
Functional description of data flow through layer 2
QoS Flows QoS Flows
QoS flow QoS flow QoS flow

SDAP SDAP handling
handling handling
Radio Bearers Radio Bearers
ROHC ROHC ROHC ROHC ROHC ROHC

PDCP PDCP
Security Security Security Security Security Security
RLC Channels RLC Channels
Segm. Segm. Segm. Segm. Segm. Segm.

RLC ARQ
... ARQ ARQ
... ARQ RLC ...
ARQ ARQ
Logical Channels Logical Channels
Scheduling / Priority Handling Scheduling
MAC Multiplexing UE1 Multiplexing UEn MAC Multiplexing
HARQ HARQ
HARQ
Transport Channels
Transport Channels
Downlink Layer 2 Structure

Uplink Layer 2 Structure

User Plane Protocol Stack - Overview
NR PDCP, RLC and MAC are all new protocols but share many similarities with corresponding LTE
protocols
SDAP protocol introduced to support new flow based QoS model of the 5GC
UE gNB
SDAP SDAP
PDCP PDCP
RLC RLC
MAC MAC
PHY PHY

Service Data Adaptation Protocol (SDAP)
• 5G CN and upper layers in the UE mark packets for
transmission with a QoS flow identifier (QFI) in both DL
and UL
• Each QFI associated with different QoS in terms of UE gNB

delay, reliability, etc SDAP SDAP
RB2 RB2
• SDAP layer maps QoS flows to radio bearers, with RB1 RB1
PDCP/RLC of each RB configured appropriately for the
PDCP PDCP
PDCP PDCP
QoS
RLC RLC
RLC RLC
• MAC layer gives differentiated handling (e.g. priority) to
traffic from different RBs MAC MAC
• gNB has flexibility how to achieve the QoS

Packet Data Convergence Protocol (PDCP)
• Header compression/decompression through the use of RoHC
• Ciphering and integrity protection
 Key difference compared to LTE PDCP is that integrity protection can be applied to user plane traffic as well
as control plane signalling
• Data duplication
 Key new feature compared to LTE PDCP
• Duplication detection and reordering of received PDPC PDUs
PDCP - Data duplication Duplication - CA case Duplication - DC case

• PDCP PDUs can be duplicated for transmission over SDAP SDAP
2 RLC bearer
PDCP PDCP
• Motivated to enable the reliability/delay requirements
for URLLC applications RLC RLC
bearer 1 RLC bearer 1 RLC
• In case of carrier aggregation (CA)
 Restrictions configured in the MAC ensure that RLC RLC
duplicated data is transmitted via different component RLC RLC bearer 2
bearer 2
carriers
MAC
• In case of dual connectivity (DC) MAC MAC
 RLC bearers are mapped to different cell groups (i.e. Cell
MCG and SCG)
Cell
Different CCs
group 1 group 2

Radio Link Control Protocol (RLC)
• The RLC sublayer supports three transmission modes (like LTE):
 Transparent Mode (TM);
 Unacknowledged Mode (UM);
 Acknowledged Mode (AM).
• Similar functionality compared to LTE RLC:

 Segmentation to match the transmitted PDU size to the available radio resources
 Error correction through ARQ
• Key differences compared to LTE RLC:

 Does not provide concatenation of RLC SDUs
o Equivalent functionality now provided by the MAC layer. Motivated to enable UL RLC PDUs to be pre
processed within the UE before reception of UL grant.
 Does not provide reordering of received RLC SDUs
o Equivalent functionality now provided by the PDCP layer

Medium Access Control (MAC)
• Similar functionality compared to LTE MAC:
 Multiplexing and demultiplexing of data from different radio bearers to the transport blocks that are carried by the
physical layer
 Priority handling between data from different radio bearers
 Error correction through Hybrid ARQ.
 Discontinuous reception (DRX)
• Key differences compared to LTE MAC

 Functionality to support beam based operation for high frequent operation.
 More flexible UL configured grants
 MAC PDU format optimised to enable pre-processing and facilitate low delay
Beam Management Functions of MAC
• Beam failure detection and recovery

 UE Phy layer monitors beam failure detection (BFD) reference signals to determine a beam failure
 On beam failure detection the UE MAC layer initiates beam failure recovery
o Selects a suitable beam on which to attempt recovery
o Performs random access procedure
• Beam management
 Mobility between beams is performed by a combination of Phy and MAC signalling
 RRC signalling involved only to provide a measurement configuration (e.g. configuration of the reference signals to
be measured, etc)

Contents
slides)

NSA: Overall Architecture
• Dual connectivity:
 Master Node (MN):
o Overall master, responsible for connection S1
establishment with UE, connection to Core
network, handover etc.
MeNB
o Master Cell Group (MCG) for UE
o For EN-DC, MN is an LTE eNB RRC
X2-C
 Secondary Node (SN)

SgNB
o Secondary Cell Group (SCG) for UE
o For EN-DC, SN is an NR gNB Uu NR RRC
UE
Uu
RRC
(MeNB
state)

NSA: Control Plane for EN-DC
• Single RRC state machine and control plane connection Inter Node
to CN based at MCG interaction
MCG RRC SCG RRC
MCG PDCP SCG PDCP

• Network has two RRC entities (MCG and SCG) that can
RLC /MAC /PHY RRC RLC /MAC /PHY
generate full RRC messages diversity
through
 RRC messages generated by the secondary can be split bearer
Including
transported transparently by the master (at least in some
SRB3
cases, e.g. for first configuration)
UE
RLC /MAC /PHY RLC /MAC /PHY
MCG PDCP SCG PDCP
• Direct RRC messages from SCG over NR – SCG SRB
(SRB3) Interaction
MCG RRC SCG RRC
SRB3: SCG SRB
• A new direct SRB between SeNB and UE – SRB3

 Motivation:
o Lower signalling delay over direct NR interface – no Xn delay and faster NR radio
o Less processing at MN
 Can only be used for messages that do not need coordination between MN and SN
• Can be configured based on SN decision.

 The following RRC messages can be sent via the SRB in the SCG
o RRCConnectionReconfiguration, RRCConnectionReconfigurationComplete, MeasurementReport
 SCG SRB is of higher scheduling priority than all DRBs
• UE still processes one message at a time in sequence irrespective of the path the message is
received in
NSA: Sub Architecture Options (3/3a/3x)
and Bearer Types
• Different bearer types based on:
 Bearer termination point of the CN interface; and
 Radio interface used for data transfer
• Single UE may be configured with different bearer types
• MN terminated and SN terminated bearer types

 Indicates where the data from core network for that bearer terminates in RAN
o Also indicates the location of SDAP (for 5GC) and PDCP entities in the network for this bearer
o E.g., MN terminated bearer implies all the data to and from CN for this bearer is through MN
 Does not imply anything about which radio interface is used for this bearer

MCG and SCG Bearer
• Indicates which radio interface is used to data
for this bearer
 MCG bearer implies all the data for this bearer

is sent only over MCG radio interface
o RLC bearer (RLC +MAC logical channel) in MCG
PDCPLTE PDCPNR
 SCG bearer implies all the data for this bearer is RLCLTE RLCNR
sent only over SCG radio interface
RLC bearer RLC bearer
o RLC bearer in SCG
MACLTE MACNR
 Figure shows MN terminated MCG bearer
(option 3) and SN terminated SCG bearer
MN terminated SN terminated
(option 3a) MCG bearer SCG bearer

Split Bearer Options 3/3x
S1-U or NG-U
MN terminated split bearer (option 3)
• Indicates both MN and SN RLC bearers are configured for this
bearer Xn
• DL data can be sent over both PDCPNR
 UL data can be configured to be sent over
 Either one of the two UL; or RLCLTE RLCNR
 Split over both paths; or
 Duplicated over both paths MACLTE MACNR
MeNB (LTE) SgNB (NR)

SN terminated split bearer (option 3x)
• Split bearer as before
• CN connection for data transfer is over SN
S1-U or NG-U
• New option introduced for EN-DC
Xn
• Allows more flexible network implementation without impacting PDCPNR
LTE eNB hardware
RLCLTE RLCNR
 All PDCP processing in SN for this bearer
MACLTE MACNR
MeNB (LTE) SgNB (NR)

Unified Bearer at UE
A unified split bearer concept at UE
• Agnostic of the PDCP location (termination point) S1
 common behaviour at the UE
PDCPNR
• Supports MCG/SCG or both RLC bearers for a PDCP

entity RLCLTE RLCNR
MACLTE MACNR
• Change of bearer type is simple – by adding or removing
RLC bearers MCG SCG

Anritsu 5G Solutions by Test Applications
TRx device RF/L1 Integration Conformance Production
mm Wave Wireless characteristics measurement Conformance Test

measurement Signalling test
5G Conformance test system
Vector Network Analyzer 5G Carrier Acceptance Test system
5G TRx/Signaling Tester
Production
5G Wideband NCP One Box

Power Master Signal Analyzer Tester
4G Anchors
Spectrum Master
OTA chamber
Field Master Pro
Field I&M

OTA Test Environment for 5G-NR RF & Protocol
Integrated OTA environment for beamforming test (Signaling & Non-Signaling)
MA8171A
MA8181A
RF Chamber
28GHz Test Antenna
Z1996A MA8175A
28GHz/39GHz Test Antenna Positioner
MA80001A Z1984A
28GHz RF Converter Jig for Tray
MA80002A (On roadmap)
39GHz RF Converter
MA8174A
MT8000A
Position Controller
Radio Communication
Test Station(5G NR Tester)
■NSA LTE Anchor
B0746A MT8821C (for RF Test)
RF Chamber Rack MD8430A (for Protocol Test)
B0747A
RF Converter Rack
GUI
MX800010A-002 MX800030A/50A
NR TDD OTA Meas. Software Rapid Test Designer (RTD)
(for OTA RF test) (for protocol test)

Thank You !!!
Appendix – A.1 - UE Identities
In this sub clause, the identities used by NR connected to 5GC are listed. For scheduling at cell level, the following identities are
used:
- C-RNTI: unique UE identification used as an identifier of the RRC Connection and for scheduling;
- CS-RNTI: unique UE identification used for Semi-Persistent Scheduling in the downlink or configured grant in the uplink;
- INT-RNTI: identification of pre-emption in the downlink;
- P-RNTI: identification of Paging and System Information change notification in the downlink;
- SI-RNTI: identification of Broadcast and System Information in the downlink;
- SP-CSI-RNTI: unique UE identification used for semi-persistent CSI reporting on PUSCH;
For power and slot format control, the following identities are used:
- SFI-RNTI: identification of slot format;
- TPC-PUCCH-RNTI: unique UE identification to control the power of PUCCH;
- TPC-PUSCH-RNTI: unique UE identification to control the power of PUSCH;
- TPC-SRS-RNTI: unique UE identification to control the power of SRS;
During the random access procedure, the following identities are also used:
- RA-RNTI: identification of the Random Access Response in the downlink;
- Temporary C-RNTI: UE identification temporarily used for scheduling during the random access procedure;
- Random value for contention resolution: UE identification temporarily used for contention resolution purposes during the
random access procedure.
For NR connected to 5GC, the following UE identities are used at NG-RAN level:
- I-RNTI: used to identify the UE context in RRC_INACTIVE.
Appendix – A.2 – Network Identities
The following identities are used in NG-RAN for identifying a specific network entity:
- AMF Name: used to identify an AMF.

- NR Cell Global Identifier (NCGI): used to identify NR cells globally. The NCGI is constructed from the PLMN identity the
cell belongs to and the NR Cell Identity (NCI) of the cell.
- gNB Identifier (gNB ID): used to identify gNBs within a PLMN. The gNB ID is contained within the NCI of its cells.
- Global gNB ID: used to identify gNBs globally. The Global gNB ID is constructed from the PLMN identity the gNB
belongs to and the gNB ID. The MCC and MNC are the same as included in the NCGI.
- Tracking Area identity (TAI): used to identify tracking areas. The TAI is constructed from the PLMN identity the tracking
area belongs to and the TAC (Tracking Area Code) of the Tracking Area.
- Single Network Slice Selection Assistance information (S-NSSAI): identifies a network slice.

Appendix A.3 – System Information Handling
System Information (SI) consists of a MIB and a number of SIBs, which are divided into Minimum SI and Other SI:
Minimum SI comprises basic information required for initial access and information for acquiring any other SI. Minimum SI
consists of:
- MIB contains cell barred status information and essential physical layer information of the cell required to receive further system information, e.g.
CORESET#0 configuration. MIB is periodically broadcast on BCH.
- SIB1 defines the scheduling of other system information blocks and contains information required for initial access. SIB1 is also referred to as
Remaining Minimum SI (RMSI) and is periodically broadcast on DL-SCH or sent in a dedicated manner on DL-SCH to UEs in
RRC_CONNECTED.
Other SI encompasses all SIBs not broadcast in the Minimum SI. Those SIBs can either be periodically broadcast on DL-
SCH, broadcast on-demand on DL-SCH (i.e. upon request from UEs in RRC_IDLE or RRC_INACTIVE), or sent in a
dedicated manner on DL-SCH to UEs in RRC_CONNECTED. Other SI consists of:
- SIB2 contains cell re-selection information, mainly related to the serving cell;
- SIB3 contains information about the serving frequency and intra-frequency neighbouring cells relevant for cell re-selection (including cell re-
selection parameters common for a frequency as well as cell specific re-selection parameters);
- SIB4 contains information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection (including cell re-
selection parameters common for a frequency as well as cell specific re-selection parameters);
- SIB5 contains information about E-UTRA frequencies and E-UTRA neighbouring cells relevant for cell re-selection (including cell re-selection
parameters common for a frequency as well as cell specific re-selection parameters);
UE gNB
- SIB6 contains an ETWS primary notification;
- SIB7 contains an ETWS secondary notification; Minimum SI (MIB)
- SIB8 contains a CMAS warning notification; periodically broadcast on BCH
Minimum SI (SIB1)
- SIB9 contains information related to GPS time and Coordinated Universal Time (UTC). periodically broadcast on DL-SCH
Minimum SI (SIB1)
For a cell/frequency that is considered for camping by the UE, the UE is not unicast on DL-SCH
required to acquire the contents of the minimum SI of that cell/frequency from Other SI (SIBn)
periodically broadcast on DL-SCH
another cell/frequency layer. This does not preclude the case that the UE
Other SI (SIBn)
applies stored SI from previously visited cell(s). broadcast on-demand on DL-SCH
If the UE cannot determine the full contents of the minimum SI of a cell by Other SI (SIBn)
unicast on DL-SCH
receiving from that cell, the UE shall consider that cell as barred.
In case of BA, the UE only acquires SI on the active BWP.


Anritsu - Webinr - 5G - Release15 - Feb 2019 (1) - 10216 - 20190212120402244

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Anritsu - Webinr - 5G - Release15 - Feb 2019 (1) - 10216 - 20190212120402244

Enviado por

Direitos autorais:

Formatos disponíveis

Understanding details of

3GPP Release 15 5G-NR

Understanding details of 3GPP Release 15 5G NR

3GPP is delivering Release 15 to the industry in 3 distinct steps:

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

• Operation from low to very high bands: 0.4 – 100Ghz

Understanding details of 3GPP Release 15 5G NR

Change of “μ” changes data rate on the sub-carrier,

Understanding details of 3GPP Release 15 5G NR

• Dynamic TDD baseline

• 15 kHz slot identical to LTE

Understanding details of 3GPP Release 15 5G NR

Transmissions restricted to slot boundaries Transmissions not restricted to slot boundaries

Data arrival One slot Data arrival

Long latency Short latency

Channel available Channel available

Understanding details of 3GPP Release 15 5G NR

• One resource grid per numerology and

• Resource block = 12 subcarriers

• Resource element = 1 subcarrier in one

Understanding details of 3GPP Release 15 5G NR

20 MHz Up to 400 MHz

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

Periodic CSI-RS Aperiodic CSI-RS Semi-Persistent CSI-RS

TRS is designed for time/frequency tracking and estimation of delay/Doppler spread

Understanding details of 3GPP Release 15 5G NR

Scheduled MCS Time domain density

0 <= MCS < MCS1 No PTRS

MCS1 <= MCS < MCS2 Every OFDM symbol

MCS2 <= MCS < MCS3 Every 2nd OFDM symbol

MCS3 <= MCS < MCS4 Every 4th OFDM symbol

Scheduled bandwidth Frequency domain density

0 <= NRB < NRB1 No PTRS

NRB1 <= NRB < NRB2 Every 2nd RB

NRB2 <= NRB Every 4th RB

Understanding details of 3GPP Release 15 5G NR

Understanding details of 3GPP Release 15 5G NR

• Main differences: One (or two) transport block(s) of dynamic

 OFDM and DFTS-OFDM in UL LDPC coding

Rate matching, hybrid-ARQ

Physical antenna mapping

Understanding details of 3GPP Release 15 5G NR

• Possibility for per-CBG retransmission

• Asynchronous in DL and UL (up to 16 processes)

Only this CBG is retransmitted

To soft combining Flushing of soft buffer controlled by CBGFI

Understanding details of 3GPP Release 15 5G NR

• Each PDCCH NULL K bit payload 24-bit CRC

 Has its own DM-RS +

No puncturing Puncturing Shortening Repetition

Mapping to resource elements

Understanding details of 3GPP Release 15 5G NR

• CORESET (Control Resource Set)

 Multiple CORESETs can be configured in a UE using RRC

 Not necessarily located at the beginning of the slot