Deep Dive 5G NR-RAN Release 2018 Q4.pptx

Deep Dive 5G NR-RAN Release 2018 Q4 | Commercial in confidence | 6/2882-560/FCP 131 5500 Uen, Rev PC8 | 2018-05-17 | Page 1
5G NR-RAN Deep Dive
2018 Q4 release

TableofContents
— General
— RAN Overview (parts of slides from later sessions)
— HW requirements
— Supported Radio products and supported bands
— General characteristics
— Changes in L1 & RRM
— NR Numerology, frame structure, NR cell
— Downlink Channels and Signals
— Uplink Channels and Signals
— Scheduling
— Link Adaptation
— L2: PDCP, RLC, MAC
— NR SU-MIMO Digital beamforming
— Energy Performance Feature
— Throughput
— EN-DC Functionality
— EN-DC Architecture and interfaces
— Bearer types and transitions
— Mobility
— User-plane functionality
— O&M including upgrade
— O&M overview
— Management system (configuration management,
fault management, performance management)
— ENM topologies
— Troubleshooting
— Licensing
— Upgrade
— Transport, Security and Synchronization
— Note that both transport part of gNB is the same
as eNB and so is synch requirements so this part is
mainly for information

DRB
NRNon-Standalone(NRNSA)
— NR Non-Standalone (NR NSA) introduces the
support for the 5G NR air-interface using existing
4G LTE infrastructure.
— NR NSA enhances mobile broadband (eMBB) to
provide increased data bandwidth and lower
latency while maintaining connection reliability
through LTE-NR Dual Connectivity.
— 5G NR node (gNB) is connected to LTE eNB
through X2 interface and to EPC/SGW via S1
(user-plane only) interface.
— NR gNB is managed by ENM through existing
O&M interface.
LTE eNB
NR UE
5G EPC
ENM
BBU
NR gNB
BBU
RU RU
LTE UE
X2
S1 S1
Uu
(e)CPRI (e)CPRI

DRB
NRNSA(EN-DC)Overview
— Ericsson’s E-UTRA-NR Dual Connectivity (EN-DC)
solution is based on Option 3x:
— LTE eNB terminates the S1 Control Signaling (S1-C)
from EPC and Signalling Radio bearer (SRB) towards
the UE.
— The user Data Bearer (DRB) is setup either as:
— Split bearer: using both LTE and NR radio resources
— LTE only bearer: using only LTE radio resources
— NR gNB terminates the S1-U user plane of the Split
bearer for the NR UE.
— LTE eNB terminates the S1-U user plane of the LTE only
bearer.
— The eNB and gNB have X2-C and X2-U connections,
where the user data of Split bearer is carried over X2-U,
and control signaling over X2-C.
eNB gNB
NR UE
X2-U
S1-U
Control signalling
S1-C
User data
S1-U
X2-C
EPC
SRB
DRB

EN-DCArchitecture
— One LTE eNB may be connected to multiple NR gNBs
— One NR gNB may be connected to multiple LTE eNBs
eNB
EPC
gNB
S1-U
NR cell
LTE cell
LTE Uu (SRB + DRB) NR Uu (DRB)
S1
NR cell
X2
X2
gNB
LTE cell
eNB
X2
S1-U
S1

EN-DCInterfaces
— RCF – Radio Controller Function
— Corresponds to 3GPP logical entity CU-CP
in a gNB
— CU-CP = Centralized Unit – Control Plane
— PPF – Packet Processing Function
— Corresponds to 3GPP logical entity CU-UP
in a gNB
— CU-UP = Centralized Unit – User Plane
— RPF – Radio Processing Function
— Corresponds to 3GPP logical entity DU in a
gNB
— DU = Distributed Unit
eNB gNB
EN-DC
UE
X2-U
Control plane
X2-AP (NR RRC)
NR L1&L2
LTE RRC (NR RRC)
S1-C (S1-AP)
User plane
RCF PPF
RPF
S1-U (GTP-U)
RCF
PPF & RPF
LTE L1&L2
S1-U (GTP-U)

— EN-DC-capable UEs are connected with one of
the following:
— LTE-only DRB in areas with no NR coverage
— Split DRB and/or LTE-only DRB in areas with
NR coverage
— Configurable per QCI and ARP
— Possible to mix LTE-only and Split DRBs
for the same UE
— Legacy LTE UEs are connected with the
following:
— LTE –only DRB
— An eNB can support both UE types
simultaneously.
NetworkSupportforLTE-onlyand
EN-DC-CapableUEs
LTE only DRB Split DRB
(Option 3x)
NR RLC
MeNB SgNB
NR PDCP
NR MAC
LTE PDCP
LTE MAC
LTE RLC LTE RLC

— DL DC Aggregation:
— DL User data is sent in both LTE and NR Leg
— Flow control on both LTE and NR Leg will minimize the
reordering in UE PDCP
— DL Fast Switch:
— DL user-data is sent in either LTE Leg or NR Leg
— Leg switching is based on NR link quality
— Good NR quality: Use NR Leg
— Poor NR quality: Use LTE leg
UserPlaneTransmissionModes(1/2)
PDCP
LTE
Leg NR Leg
PDCP
LTE
Leg
NR Leg
PDCP
LTE
Leg
NR Leg
DL Fast Switch DL DC Aggregation
DL transmission mode is controlled by operator parameter
UL L1/L2 signaling on same leg as DL user data

UserPlaneTransmissionModes(2/2)
— Uplink
— UL User Plane transmission for Split DRB controlled by operator parameter. Configuration is
signaled to UE via RRC at NR Leg Setup.
— always LTE (default)
— always NR

NR–BasicNumerology
— LTE: A single 15 kHz subcarrier spacing
— Normal and extended cyclic prefix
— NR supports sub-1GHz to several 10 GHz spectrum range
 Multiple OFDM numerologies required
— Flexible subcarrier spacing always a factor of 15kHz where n varies
from 0 to 4 ( Δf=2n∙15 kHz )
— Scaled from LTE numerology
— Higher subcarrier spacing  Shorter symbols and
cyclic prefix
— Extended cyclic prefix only standardized for 60 kHz
Data [kHz] SSB [kHz]
< 6 GHz 15, 30, 60 15, 30
> 6 GHz 60, 120 120, 240
Notes: 30 kHz subcarrier spacing is supported for Midband
(< 6 GHz) in 18.Q4
Rel-15 supports the following numerologies
15 kHz 30 kHz 60 kHz 120 kHz 240 kHz

cyclic prefix
<6 GHz 15, 30, 60 15, 30
>6 GHz 60, 120 120, 240
Notes: 30 kHz subcarrier spacing is supported for Midband
(< 6 GHz) in 18.Q4
120 kHz subcarrier spacing is supported for both data and
SSB for Highband (> 6 GHz) in 18.Q4

NR–Time/FrequencyStructure
— One slot = 14 symbols (Normal CP)
— One resource block = 12 sub-carriers
› Higher numerology  Shorter slot  Lower latency
– But also shorter cyclic prefix  Less robust to channel time dispersion

TDDFrameStructure
— 3GPP NR supports FDD, dynamic TDD, and TDD
with semi-statically configured UL/DL
configuration:
— Supported TDD pattern in 18Q4 release:
— 3 DL slots and 1 UL slot with guard period in a
slot where DL symbols are followed by UL
symbols.
— . n+3
n+1
n n+2 n+4
C D D D D D D D D D D D D D C D D D D D D D D D D
C D D D D D D D D D D D D D
PUSCH/DMRS
D
PUCCH
C
PDCCH
C
PDSCH/DMRS
D
GP
D D D D D D D D
D D D D D D
GP Guard Period

TDDFrameStructure
— NR supports FDD, dynamic TDD, and TDD with
semi-statically configured UL/DL configuration:
— Supported TDD pattern in 18Q4 release:
— 3 DL slots and 1 UL slot with guard period in a
slot where DL symbols are followed by UL
symbols.
PUSCH
PUCCH
PDCCH
PDSCH
Slot n+3
Slot n+1
Slot n Slot n+2 Slot n+4
GP
DL
UL

— One LTE eNB may be connected to
multiple NR gNBs
— One NR gNB may be connected to multiple
LTE eNBs
— NR cell selection based on:
— UE measurement based
— operator configured LTE-NR cell relation
— One gNB initially supports one NR
RRU/cell, thus 3 gNBs are required to
cover a 3-sector configuration.
— Each NR cell requires one AIR 6488.
3.5GHzNR-NSANetworkDeployment
NR
LTE

39GHzNR-NSANetworkDeployment
NR
LTE
› One LTE eNB may be connected to
multiple NR gNBs
› One NR gNB may be connected to multiple
LTE eNBs
› NR cell selection based on:
– UE measurement based
– operator configured LTE-NR cell relation
› One gNB initially supports one NR
RRU/cell, thus 3 gNBs are required to
cover a 3-sector configuration.
› Each NR cell requires one AIR 5331.

— Transport has full feature parity between the gNodeB and the eNodeB.
— All TN ports can be used simultaneously, either for resiliency or for connecting site equipment etc.
— Connectivity of site equipment may be achieved using routing or bridging
— Completely flexible IP address and VLAN configuration for all traffic types
— BFD
— Virtual Routing is supported as an enabler for traffic separation
TransportNetworkoverview

NRNSATransportInterfaceRequirements
eNB gNB gNB gNB
AIR 6488 AIR 6488 AIR 6488
Router
6672/6675
S1-UP
X2 2 Gb/s
S1-UP 3.4 Gbps
X2 2.0 Gb/s
CPRI
including XMUs
C2(eCPRI)
2/3*10 Gb/s
10 Gb/s
Cell1’ Cell2’ Cell3’
Cell1 Cell2 Cell3
Same IPsec
support on
gNB as on
eNB

NRNSATransportInterfaceRequirements
— The NR cells must be collocated with the LTE cells to acheive low latency.
eNB
gNB (BB
6630)
gNB (BB
6630)
gNB (BB
6630)
AIR 5331 AIR 5331 AIR 5331
Router
6672
S1-UP
X2 2 Gb/s
CPRI
including XMUs
C1
4*10.1
Gb/s
10 Gb/s
Cell1 Cell2 Cell3
Same IPsec
support on
gNB as on
eNB
S1-UP 4 Gbps
X2 2.0 Gb/s
LTE 2 Gbps + NR
2 (highband)

NRNSASyncSolution
anexample,alternativesolutionswitheNBasGMandIEEE1588supported,detailsin
dedicatedSyncsession
eNB gNB gNB gNB
AIR 6488 AIR 6488 AIR 6488
S1-UP
X2 1-2 Gb/s
S1-UP, X2, PTP
interfaces
~2.0 Gb/s
CPRI
including XMUs
C2
2*10 Gb/s
10 Gb/s
Cell1 Cell2 Cell3
GPS
RAN
Grandmaster
Telecom
Boundary
Clock
Router
6672
PTP
Slaves

eNB
gNB (BB
6630)
gNB (BB
6630)
gNB (BB
6630)
AIR 5331 AIR 5331 AIR 5331
S1-UP
X2 1-2 Gb/s
S1-UP, X2 , PTP
interfaces
~2.0 Gb/s
CPRI
including XMUs
10 Gb/s
Cell1 Cell2 Cell3
GPS
RAN
Grandmaster
Telecom
Boundary
Clock
Router
6672
PTP
Slaves
C1
4*10.1
Gb/s
NRNSASyncSolution
anexample,alternativesolutionswitheNBasGMandIEEE1588supported,detailsin
dedicatedSyncsession

O&MIntroduction
— Assumption: ENM (including ENM applications) and
management of Baseband Radio Nodes are known.
— ENM is pre-requisite for management of NR-NSA (no OSS-RC
support)
— The eNodeB and the gNodeB are separate managed elements of
different managed element types
— A gNodeB is managed in the same way, with the same interfaces
and applications as an eNodeB:
— ENM
— ENM Northbound Interface (NBI) *)
— EM tools (EMCLI, EMGUI and AMOS)
— New support for NR-NSA systems introduced in ENM
*) except for PM events
ENM
eNodeB
(RadioNode)
EMCLI
EMGUI
ENM
CLI
FM
AP
ENM-SHM
PM
BULK
CM
AMOS
“gNodeB”
(5GRadioNode)
…
ENM NBI
NMS
ME ME
NR-NSA system
ME Type
eNodeB RadioNode
gNodeB 5GRadioNode

MOMOverview
— Many MOM fragments are the same for the eNodeB and the ”gNodeB” -> all the basic O&M support
(CM, FM, PM, Upgrade, etc.) works in the same way for the two ME types
— The difference between the two ME types is that the eNodeB has the ENodeBFunction while the
“gNodeB” will have three other functions that are standardized by 3GPP
“gNodeB”
(5GRadioNode)
ManagedElement
Equipment
Transport
GNBCUCPFunction
SystemFunctions
NodeSupport
GNBCUUPFunction
GNBDUFunction
eNodeB
(RadioNode)
ManagedElement
Equipment
Transport
ENodeBFunction
SystemFunctions
NodeSupport
EquipmentSupport
Function
EquipmentSupport
Function
MO names are preliminary and may change

ENMSupportfor“gNodeB”andNR-NSASystem
— ENM will provide the same basic O&M support for
“gNodeB” (CM, FM, PM, etc.) as for eNodeB
— ENM Support added for management of an NR-NSA
system (an eNodeB with connected “gNodeBs”)
— NR-NSA Topology added to “selection” panels in
applicable applications
— Autointegration of “gNodeB” and reconfiguration
of eNodeB in a single AP project
— Support for logical and geographical views of
NR-NSA systems

SupportedBasebandHW
— The NR NSA may be deployed on the following
Baseband units:
— eNB: Baseband 5216 / 5212 / 6630 / 6620
— gNB: Baseband 6630

Technical Specification
Antenna Elements 128
Antenna Branches 64T64R
Antenna Matrix (row x col) 8 x 8, (2x1 subarray)
Band 3500–3600Mhz
IBW 100 MHz
Output Power 200 W
Power Consumption <1000 W
Weight ~45 kg
Dimensions 800*400*150 mm
Type of cooling Passive
CEPT compliance
Multi-layer MU MIMO:
Up to 16 layers
AIR6488B42D

Band 3500–3600Mhz
IBW 100 MHz
Output Power 200 W
Weight ~45 kg
CEPT compliance
Up to 16 layers
AIR6488B42D
AIR 6488 with Telstra specific filtering will be
developed, based on spectrum auction outcome

Band 3420–3600Mhz
IBW 100 MHz
Output Power 200 W
Weight ~50 kg
CEPT compliance
Up to 16 layers
AIR6488B42F

Band 3600–3800Mhz
IBW 100 MHz
Output Power 200 W
Weight ~45 kg
CEPT compliance
Up to 16 layers
AIR6488B43

Band 37–40Ghz
IBW 1200 MHz
Output Power 200 W (53 dBm / beam)
Weight 14 kg
Dimensions (volume) 19 liters
CEPT compliance
Multi-layer SU MIMO: 2 layers
AIR5331

Characteristics

PeakL2Throughput(Mbps)
Downlink,Single-layer
› For multiple layers, the single-layer peak throughput is scaled by the number of layers.
› Supported configuration in 2018Q4:
› 20/100MHz BW, 1+1 DMRS and up to 2 layers  725 Mbps *
› Up to 4 layers in demo/limited field trial  1.4 Gbps *
• Note: Throughput provided by NR leg. The throughput provided by LTE leg may be aggregated with NR leg through LTE-NR Dual connectivity.
LTE CA is supported pending UE capability.
0.00
50.00
100.00
150.00
200.00
250.00
300.00
350.00
400.00
450.00
1 DMRS 1+1 DMRS 1 DMRS 1+1 DMRS
64QAM 256QAM
Peak L2 Throughput (Mbps)
Downlink, Single-layer
20 40 60 80 100

Uplink,Single-layer
0
20
40
60
80
100
120
140
20 40 60 80 100
Uplink, Single-layer
64QAM 1 DMRS 64QAM 1+1 DMRS
› 20/100MHz BW/1+1 DMRS is supported in 2018-Q4.

gNB
RANLatency–Userplane
— The RAN contribution for Round Trip Time (RTT) is estimated
to 4 ms.
— This includes:
— Data arrival in gNB
— DL and UL data processing in gNB
— Air interface delay (TTI: 0.5 ms)
— Estimated UE processing time

NR-NSAMid-bandCapacity2018–Q4
(1/2)
— 1 gNB supports 1 NR cell:
— 3 gNBs and 3 corresponding Baseband 6630 units are required
to cover a 3-sector configuration.
— SU-MIMO
— 4 Layers in DL
— 1 Layer in UL
— Terminating Antenna BW
— DL 400 MHz (1 Sectors x 100 MHz Carrier BW x 4 Layer)
— UL 100 MHz (1 Sectors x 100 MHz Carrier BW x 1 Layer)

NR-NSAMid-bandCapacity2018–Q4
(2/2)
— Up to 5 connected UEs per cell is supported
— Maximum throughput supported per cell*
— 1.46 Gbps in DL
— 107 Mbps in UL
*100 MHz bandwidth
Downlink: 4 layers SU-MIMO, 256 QAM
Uplink: 1 Layer SU-MIMO, 64 QAM
TDD pattern: DL: 75% UL: 25%

MainProcessorLoadimpactonLTEeNB
— A Service Request, i.e. RRC connection and Bearer setup, including NR leg setup is estimated to
consume twice amount of MP processing capacity in the eNB compared to a LTE legacy connection
setup.
— Negligible impact on Main Processor load in the eNB if the number of NR-capable UEs are low.

L1&RRM

TableofContents
— NR Numerology, Frame structure, NR cell
— Downlink Channels and Signals
— Uplink Channels and Signals
— Scheduling
— Link Adaptation
— L2- PDCP, RLC, MAC
— NR SU-MIMO Digital Beamforming
— Energy Performance Feature
— Abbreviations

cyclic prefix
< 6 GHz 15, 30, 60 15, 30
> 6 GHz 60, 120 120, 240
Notes: 30 kHz subcarrier spacing is supported for < 6 GHz
frequency bands in 18.Q4 for both data and SSB.

TDDFrameStructure
— NR supports FDD, dynamic TDD, and TDD with
semi-statically configured UL/DL configuration:
— TDD pattern supported in 18.Q4 is: 3 DL slots and 1
UL slot with guard period in a slot where DL symbols
are followed by UL symbols.
— DL/UL assignment is communicated to UE through
RRC configuration.
n+3
n+1
n n+2 n+4
—NR supports “slot-based transmissions”
(PDSCH/PUSCH Type A) and “non-slot-
based transmissions” (PDSCH/PUSCH Type
B).
—Only Type A is supported in 18.Q4.
PUSCH/DMRS
D
PUCCH
C
PDCCH
C
PDSCH/DMRS
D
GP
D D D D D D D D
D D D D D D
C C

NRCellandBWP
— NR Cell
— Defined by the (same) SS Block information
— Supports cell Bandwidth of 20 / 100 MHz in 18.Q4
(40 / 60 /80 MHz will be supported in 19.Q1)
— Bandwidth Parts (BWP)
— A BWP is associated with a numerology, PXCCH, PXSCH,
and DM-RS within a BWP share the same numerology.
— A UE is limited to a single active BWP at a time.
— In 18.Q4, BWP is equivalent to cell bandwidth.
— Within each BWP a CORESET is configured for the UE to
monitor the PDCCH.
SS1 SS2
NR Cell
UE BW = Cell BW
BWP
Overall carrier

Downlink Channels and
Signals

SS/PBCHBlock
— The synchronization signal and PBCH block (SSB) consists of Primary
Synchronization Signal (PSS), Secondary Synchronization Signal (SSS),
and PBCH.
— Uses 4 consecutive OFDM symbols.
— Transmitted every 5 / 10 / 20 / 40 / 80 / 160 ms.
— SSB periodicity is configured in RRC parameter, default to 20ms in
18.Q4
— Numerology of SSB depends on frequency band.
— 30KHz subcarrier spacing is supported in 18.Q4
— Time locations where SSB can be sent are determined by sub-carrier
spacing.
— Polar coding is used for PBCH.
— NR cell search is based on the primary and secondary synchronization
signals, and PBCH DMRS
— UE performs matched filtering to find PSS.
— UE detects SSS in the frequency domain.
— PSS and SSS together indicate physical Cell ID (in total
3*336 = 1008 physical Cell IDs).
— UE decodes MIB contained in PBCH. MIB is transmitted in PBCH with
periodicity of 80ms.
— System Frame Number (SFN)
— Subcarrier spacing for initial access
— SSB Subcarrier Offset
— DMRS TypeA Position
frequency
symbols
PBCH
PBCH
SSS
PSS
PBCH
PBCH
127
subcarriers
240
subcarriers
SSB periodicity = 20ms (default)
slots
5ms

PDCCH–Configurations(1/2)
— Control-resource set (CORESET)
— A CORESET is a subset of the downlink physical resource
configured to carry control signaling (PDCCH).
— For the slot-based (Type A) scheduling, the CORESET is
located at the beginning of a slot.
— The REs in a CORESET are organized in Resource Elements
Groups (REGs). Each REG consists of 12 REs of one OFDM
symbol in one RB.
— Allocation in the frequency domain is done in units of 6 REGs.
— PDCCH
— A PDCCH is confined to one CORESET with aggregation level
of up to 16 control channel elements(CCE).
— Supported aggregation level depends on the CORESET
size and cell bandwidth.
— REG bundling and precoding granularity
— The REGs can be configured to form REG bundles. REG
bundle size depends on CORESET length in time.
— REG bundle size of 6 is supported in 18.Q4.
— Polar coding is used for PDCCH.
DM-RS
Data
Data
Data
…
Data
Data
PDCCH
PDSCH
CORESET
DM-RS

PDCCH–Configurations(2/2)
— PDCCH DMRS
— DMRS is mapped on all REGs on all the OFDM symbols for a given PDCCH candidate.
— Search spaces
— A PDCCH candidate is a set of control channel elements(CCE) in which a UE may expect to
receive a PDCCH of a certain DCI format.
— A search space is a set of PDCCH candidates monitored by a single UE or several UEs.
— A UE-specific search space is monitored by a single UE.
— A common search space may be monitored by several UEs.
— Search space is configured by RRC signaling.
— PDCCH blind decoding
— A UE shall attempt to blindly decode all its PDCCH candidates in all assigned search spaces.

PDSCH(1/2)
— DL transport block is carried by PDSCH
— A transport block is mapped to one carrier.
— LDPC coding is used.
— The following modulation orders are supported: QPSK, 16QAM, 64QAM and 256QAM.
— Single transmission scheme for PDSCH
— UEs can receive 1–4 MIMO layers.
— Implementation enables beamforming and/or transmit diversity schemes.
— PDSCH DM-RS
— Type 1 with up to 4 DM-RS ports is supported.
— For slot-based mapping (Type A), a UE is configured with the first front-loaded DM-RS in the third
symbol of the slot, and in addition, it will be configured with 1 or 2 additional DM-RSs.

PDSCH(2/2)
—Resource allocation
— Same-slot scheduling: PDCCH and the scheduled PDSCH have the same
numerology.
— Resource allocation in the frequency domain are supported by semi-static
configuration:
— Type 0: Bitmap of RBGs. RBG size (4, 8, or 16 RBs) is determined by BWP size
and RRC configuration. Configuration 1 is supported.
— Resource allocation in the time domain
— Slot-based mapping (Type A) is supported.
—PRB bundling
— Precoding Resource Block Group (PRG) of wideband are supported.
— Configured by higher layer

ChannelStateInformationReference
Signal(CSI-RS)
— Channel state information reference signal (CSI-RS) was first introduced in LTE release 10 to support
transmission mode 9 with up to 8 layers.
— CSI-RS evolved substantially over the releases to support more functionalities, especially in NR.
— CSI-RS are needed for the following NR functionalities:
— Link adaptation
— Codebook-based DL precoding
— Non-codebook based DL precoding
— Tracking reference signals (TRS) for frequency/time tracking
— Radio link monitoring (RLM)
— L3 mobility

TRS(1/2)
— Unlike LTE, NR does not have CRS; hence, TRS is introduced for fine time-frequency tracking.
— Tracking reference signals (TRS) is configured by UE specific RRC signaling as a set of CSI-RS resources
with setting higher layer parameter TRS-INFO to “true”.
— For FR1, the UE may be configured with a CSI-RS resource set of four periodic CSI-RS resources in two
consecutive slots with two CSI-RS resources in each slot.
— For each CSI-RS resource, it’s configured by CSI-RS-ResourceMapping with below restrictions:
— The OFDM symbol indices of the two CSI-RS resources in a slot is given by one of (4,8), (5,9) or
(6,10).
— For each CSI-RS resource
— One-port
— Density = 3
— The bandwidth is UE BWP, and in units of 4.
— The periodicity is one of 10, 20, 40, or 80ms.
— Same pattern is applied for two slots
— TRS is transmitted independent of PDSCH transmission.
— Power boosting of TRS could be supported by configuring 1~3 ZP CSI-RS resources.

TRS(2/2)
— All the UE shall be configured with the same TRS resource within the cell.
— Only one periodic TRS resource is supported and configured for each UE.
— The periodicity of TRS can be configured per cell through MOM attribute.
— Set to 40ms by default.
— The time domain location (symbol index within one slot) is fixed to (4,8).
— Different power boosting level can be configured per cell.
— TRS slot offset
— No colliding with RA Msg2 as much as possible
— No colliding with SSB/PBCH slot

TRSFormat
*one slot is only
supported for
> 6 GHz
CSI-RS resource #1
CSI-RS resource #2
CSI-RS resource #3
CSI-RS resource #4
— An example of TRS format is illustrated:

CSI-RSResource
— Non-zero-power CSI-RS resources
— Used for DL channel measurement
— Periodic CSI-RS resource configuration will be supported.
— The periodicity of NZP CSI-RS is configured per cell.
— UE is configured with the same Non-zero-power CSI-RS resource within the cell. (*)
— Only one NZP CSI-RS resource set is configured for UE to measure DL channel.
— CSI-Interference Management (CSI-IM) resources
— It’s configured for UE to measure DL inter-cell interference.
— Only one periodic CSI-IM resource is configured for DL inter-cell interference measurement.
— The periodicity is the same as NZP CSI-RS
— The frequency band is the same as that for NZP CSI-RS.
— All the UEs shall be configured with the same CSI-IM resource.
— Zero-power CSI-RS resources
— Used for inter-cell interference measurement and PDSCH rate-matching.
— One Zero-power CSI-RS resource shall be configured as the same location as CSI-IM.
— More ZP CSI-RS will be configured if TRS power boosting is needed.
*Assume UE supports 32-ports CSI-RS

Uplink Channels and
Signals

NRContentionBasedRandomAccess
—NR-NSA uses Dual Connectivity.
— Creation of the UE context in the gNodeB is performed before the random
access procedure is initialized.
— Before the random access procedure to the gNodeB, the UE connects to the
eNodeB through RRC.
— Before the random access procedure, the UE receives a C-RNTI to be used for
the NR leg through RRC signaling that is tunneled over the LTE leg.
—Basic functionality allows scheduling of RA Msg2, Msg3, and
Contention Resolution Message.
—Random access coverage is comparable to that of other NR
channels.

NRRandomAccessProcedure
—The contention-based RA procedure is similar to LTE.
— NR-NSA case: a C-RNTI is assigned to the UE before the RA
procedure.
Msg1
Preamble
Msg3
PUSCH
Time
[slot]
rar-WindowLength ra-ContentionResolutionTimer
> X symbols
Msg2
PDSCH
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Msg2
PDCCH
Contention
resolution
grant
PUSCH

—RA Msg1 - PRACH transmission
— PRACH preamble format B4 with a ZC Sequences of length 139 is chosen.
— The 3GPP defined PRACH configuration table has PRACH configuration
indexes for each preamble format which indicate:
— The periodicity, the PRACH subframe, the number of slots within the PRACH subframe,
the number of time-domain PRACH occasions within the PRACH slot, the start symbol
within the slot, and the PRACH duration in symbols.
— For the first product, a PRACH configuration index with 10ms periodicity
will be configured.
— The same subcarrier spacing is used for PRACH and PUSCH.
— A single PRACH resource is configured, which means that no beam
sweeping is present.

—RA Msg2 – Random Access Response (RAR)
— Transmitted using a DCI on the PDCCH and a PDSCH transmission.
— The RAR contains allocation information for the Msg3 PUSCH
transmission
— A new concept of CORESET is introduced to transmit PDCCH in NR.
— A CORESET is a time/frequency region in which a UE searches for DCI.
— For instance, for a 20 MHz system, a single CORESET of the size of 8 CCEs in the first
symbol is used for both DL and UL DCIs.
— The UE monitors the PDCCH in common and UE-specific search spaces within defined
CORESET(s).
— For RAR, the UE monitors Type1 PDCCH common search space for a DCI scrambled by
the RA-RNTI.

— RA Msg3 - PUSCH transmission
— The UE transmits Msg3 on the PUSCH upon successful RAR reception:
— RAR received within the RAR response window
— Contains RA preamble identifier that matches the transmitted preamble
— Msg3 PUSCH message includes the C-RNTI transmitted in the LTE leg.
— RA Contention Resolution Timer starts after Msg3 is transmitted.
— Contention Resolution Message
— For NR-NSA, the contention resolution message is an UL grant sent on the PDCCH.
— A regular PDCCH transmission is addressed to the C-RNTI of the UE, which
contains an UL grant for a new transmission.
— The UE monitors PDCCH candidates in a UE-specific search space for a DCI format
scrambled by the C-RNTI.
— Reception of the PUSCH transmission (using the contention resolution grant) signifies
that the contention based RA procedure is completed successfully.

PUCCHConfiguration(1/3)
—PUCCH carries HARQ-ACK, SR(scheduling
request)
—Long PUCCH to be configured in one
cell/BWP
—Amount of PUCCH resources will be static
configured after Cell/BWP setup in 18Q4.
— FDM with PUSCH (PRB-based)
— One Pair of PRBs allocated for PUCCH
resources (14 symbols)
— Frequency hopping is enabled
PDCCH
PDCCH
PUCCH
Slot duration
PUSCH
PUCCH PUCCH
PUCCH

—Upon UE connection setup
— Resource sets for DL HARQ-ACK.
— PUCCH format 1 (1 or 2 bits): 3 resources are configured per UE.
— PUCCH format 3 (3+ bits): 1 resource is configured per UE.
— No resource is configured for periodic CSI report.
— Only aperiodic CSI report is supported on PUSCH.
— Every UE is given an SR resource at UE setup
—If a UE would transmit a PUCCH that has a same first symbol and
duration with a PUSCH transmission, the UE multiplexes the UCI in the
PUSCH transmission and does not transmit the PUCCH.

—Periodic SR resource
— Only one SR per UE is configured.
— One SR resource is configured for all UL bearers in one cell.
— All UEs have the same SR periodicity
— SR Periodicity may be configured depending on the numerology.
— For FR1, SR periodicity can be chosen from slots of 20, 40, 80, or 160.
— PUCCH format 1 is configured for SR report.

PUSCH
— UL transport block is carried by PUSCH:
— A transport block is mapped to one carrier, with LDPC coding and CP-OFDM.
— The following modulation orders are supported: QPSK, 16QAM, 64QAM.
— Single transmission scheme for PUSCH:
— Codebook-based, single Tx and 1 layer
— 1 port DMRS
— Resource allocation
— DCI and scheduled PUSCH have an offset of minimum 2 slots.
— Frequency resource allocation Type 1 is supported with semi-static configuration, indicated by
starting virtual RB position and a length of contiguously allocated RBs.
— Resource allocation in the time domain:
— At least slot-based mapping Type A is supported.

ChannelCoding
— PDCCH (DCI), PBCH:
— Polar codes
— UCI
— Very short UCI (K<=11 bits): short block codes
— K=1: repetition code
— K=2: simplex code
— 3<=K<=11: LTE Reed-Mueller code
— Longer UCI (K>11 bits): Polar codes
— Include both UCI carried by PUCCH and PUSCH
— PDSCH, PUSCH:
— LDPC codes

Scheduling

BasicNRScheduling
— A few (up to 5) connected UEs are assumed in an NR cell.
— All connected UEs are assumed to support full bandwidth configured for the cell.
— The BWP of UE must be same as the cell bandwidth.
— Each PDSCH/PUSCH transmission requires an explicit DL/UL grant on PDCCH.
— In every time slot, one or both of the following happens:
— Up to one UE is allocated for PDSCH transmission in DL slot
— Up to one UE is allocated for PUSCH transmission in UL slot
— Single User MIMO
— One codeword with up to 4 layers for UE PDSCH transmission.
— Enable Low Energy Scheduler Solution to reduce power consumption by shaping DL traffic data and
increasing blanked subframes when Radio temperature rises.
— TPC for PUCCH, PUSCH and SRS are not supported in first release.

DLUETrafficScheduling
— DCI 1-1 is used for UE PDSCH transmission.
— K0 in “Time domain resource assignment” is 0 (PDSCH is transmitted at the same slot as associated
PDCCH).
— PDSCH-to-HARQ_feedback (K1) values are not smaller than the slot value in “Time domain resource
assignment” (K2) provided in DCI 0-1 for the same UE.
PUSCH/DMRS
D
PUCCH
C
PDCCH
C
PDSCH/DMRS
D
HARQ feedback
PDSCH scheduling
PUSCH scheduling
n+3
n+1
n n+2
D D D D D D D D
D D D D D D
n+7
D D D D D D D D
D D D D D D

DLUETrafficScheduling
— Resource allocation type 0 is used for PDSCH resource allocation.
— Resource allocation based on DL data buffer of the UE.
— gNodeB Link Adaptation
— Multiple bearers can be supported.
— Priority scheduling:
— Resource Fair based among all types of bearers
— Adaptive HARQ retransmission.
— Codeword based retransmission

ULUETrafficscheduling
— DCI 0-1 is used for UE PUSCH transmission grant.
— K2 is compliant to 3GPP requirement which is minimum 2 slots
— Resource allocation type 1 is used for PUSCH resource allocation.
— Resource allocation is based on BSR and PHR reports of the UE.
— UL link adaptation is supported
— One layer is transmitted over PUSCH.
— Modulation
— Up to 64QAM
— Adaptive HARQ Retransmission
— Codeword based retransmission
— Multiple bearers can be supported.
— Priority scheduling:
— Resource Fair based among all data bearers.

Link Adaptation

LinkAdaptation
— Link Adaptation (LA) for PDSCH and PUSCH consists of the following:
— Inner loop MCS selector targeting a fixed Block Error Rate (BLER) of 10% for all HARQ
transmissions
— Outer loop channel quality corrector based on HARQ ACK/NACK feedback to enforce the BLER
target
— For PDSCH, CSI reported by UE (CQI, RI) is used as input for LA:
— Aperiodic CSI-RS reporting with subband CQI
— For PUSCH, signal power and noise-plus-interference is measured in the gNodeB and used as input for
LA, together with UE-reported PHR.

LinkAdaptation
— For PDSCH, a single transport block with up to 4 layers per DL assignment is supported.
— The number of layers follows the UE-reported RI feedback.
— For PUSCH, a single transport block with a single layer per UL assignment is supported.
— TB-based HARQ feedback and retransmission is supported for both PUSCH and PDSCH.
— For PDCCH, a fixed aggregation level is used for all UEs, targeting cell edge coverage.

TransportBlockSizeDetermination(1/2)
Hybrid method is adopted for transport block size
determination:
1. Calculate an intermediate number of information
bits
𝑁𝑖𝑛𝑓𝑜 = 𝜐 ∙ 𝑄𝑚 ∙ 𝑅 ∙ 𝑛𝑃𝑅𝐵 ∙ 𝑁𝑅𝐸
′
— 𝜐 is the number of layers
— 𝑄𝑚 is the modulation order, obtained from the
MCS index (Table 5.1.3.1-1 and Table Table
5.1.3.1-2 in TS 38.214)
— 𝑅 is the code rate, obtained from the MCS index
— 𝑛𝑃𝑅𝐵 is the total number of allocated PRBs
determined from DCI
— 𝑁𝑅𝐸
′
is the quantized average number of available
REs in an allocated PRB (see next slide)
2. If 𝑁𝑖𝑛𝑓𝑜 ≤ 3824, use a look-up table to determine
TBS (Table 5.1.3.2-2)
3. Otherwise, use a formula to determine TBS
Table 5.1.3.2-2: TBS for 3824
info 
N
Index TBS Index TBS Index TBS Index TBS
1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416
5 56 35 408 65 1480
6 64 36 432 66 1544
7 72 37 456 67 1608
8 80 38 480 68 1672
9 88 39 504 69 1736
10 96 40 528 70 1800
11 104 41 552 71 1864
12 112 42 576 72 1928
13 120 43 608 73 2024
14 128 44 640 74 2088
15 136 45 672 75 2152
16 144 46 704 76 2216
17 152 47 736 77 2280
18 160 48 768 78 2408
19 168 49 808 79 2472
20 176 50 848 80 2536
21 184 51 888 81 2600
22 192 52 928 82 2664
23 208 53 984 83 2728
24 224 54 1032 84 2792
25 240 55 1064 85 2856
26 256 56 1128 86 2976
27 272 57 1160 87 3104
28 288 58 1192 88 3240
29 304 59 1224 89 3368
30 320 60 1256 90 3496

TransportBlockSizeDetermination(2/2)
— To support flexible scheduled durations for PDSCH/PUSCH in NR,
average number of available REs in a PRB 𝑁𝑅𝐸
′
is quantized from
𝑋 = 12 ∙ 𝑁𝑠𝑦𝑚𝑏
𝑠ℎ
− 𝑁𝐷𝑀𝑅𝑆
𝑃𝑅𝐵
− 𝑁𝑜ℎ
𝑃𝑅𝐵
according to table on the right
— 𝑁𝑠𝑦𝑚𝑏
𝑠ℎ
is the number of scheduled OFDM symbols
— 𝑁𝐷𝑀𝑅𝑆
𝑃𝑅𝐵
is the number of REs for DM-RS per PRB in the scheduled
duration including the overhead of the DM-RS CDM groups
indicated by DCI format 1_0/1_1
— 𝑁𝑜ℎ
𝑃𝑅𝐵
is the overhead configured by higher layer
— The set of possible 𝑁𝑜ℎ
𝑃𝑅𝐵
values are [0, 6, 12, 18]
— Default value is 0 for both UL and DL
X 𝑁𝑅𝐸
′
X ≤ 9 6
9<X ≤ 15 12
15<X ≤ 30 18
30<X ≤ 57 42
57<X ≤ 90 72
90<X ≤ 126 108
126<X ≤ 150 144
150<X 156

MCSTableforPDSCHandPUSCH
Table 5.1.3.1-2: MCS index table 2 for PDSCH
MCS Index
IMCS
Modulation Order
Qm
Target code Rate R x [1024] Spectral
efficiency
0 2 120 0.2344
1 2 193 0.3770
2 2 308 0.6016
3 2 449 0.8770
4 2 602 1.1758
5 4 378 1.4766
6 4 434 1.6953
7 4 490 1.9141
8 4 553 2.1602
9 4 616 2.4063
10 4 658 2.5703
11 6 466 2.7305
12 6 517 3.0293
13 6 567 3.3223
14 6 616 3.6094
15 6 666 3.9023
16 6 719 4.2129
17 6 772 4.5234
18 6 822 4.8164
19 6 873 5.1152
20 8 682.5 5.3320
21 8 711 5.5547
22 8 754 5.8906
23 8 797 6.2266
24 8 841 6.5703
25 8 885 6.9141
26 8 916.5 7.1602
27 8 948 7.4063
28 2 reserved
29 4 reserved
30 6 reserved
31 8 reserved
Table 5.1.3.1-1: MCS index table 1 for PDSCH
MCS Index
IMCS
Modulation Order
Qm
Target code Rate R x [1024] Spectral
efficiency
0 2 120 0.2344
1 2 157 0.3066
2 2 193 0.3770
3 2 251 0.4902
4 2 308 0.6016
5 2 379 0.7402
6 2 449 0.8770
7 2 526 1.0273
8 2 602 1.1758
9 2 679 1.3262
10 4 340 1.3281
11 4 378 1.4766
12 4 434 1.6953
13 4 490 1.9141
14 4 553 2.1602
15 4 616 2.4063
16 4 658 2.5703
17 6 438 2.5664
18 6 466 2.7305
19 6 517 3.0293
20 6 567 3.3223
21 6 616 3.6094
22 6 666 3.9023
23 6 719 4.2129
24 6 772 4.5234
25 6 822 4.8164
26 6 873 5.1152
27 6 910 5.3320
28 6 948 5.5547
29 2 reserved
30 4 reserved
31 6 reserved
— Table: 64QAM, use for both PDSCH and PUSCH — Table2: 256QAM, use for PDSCH only

L2- PDCP, RLC, MAC

gNB
UE
3GPP UPProtocolArchitecture(forSignaling)
PDCP
RLC
MAC
PDCP
RLC
MAC
PHY PHY
PDCP SDU
PDCP SDU
header
PDCP PDU
RLC Control
header PDCP Control
header
MAC Control
header header
header
header
ASN.1 coded RRC message
header
header
header
Moreover, the UP architecture offers inband control for both data and signaling:
or or

Details,FormatsinNRPDCP/RLC
— PDCP layer:
— Based on LTE but adapted to the new physical layer of NR:
— trimmed to make simpler and faster processing
— DRB support for 18 bits and 12 bits PDCP SN (both applicable for UM and AM)
— RLC layer:
— Based on LTE but adapted to the new physical layer of NR:
— trimmed to make simpler and faster processing
— Concatenation replaced by Multiplexing by MAC
— Single RLC SDU or segment of same per RLC PDU
— DRB AM support for 12 and 18 bits SN
— Same SN is used for segmented RLC SDU/RLC PDU, SO refers to the bytes of RLC SDU
— AM only: Use NACK Range (and E3) to report losses of multiple adjacent RLC PDUs
— No SO field on the header of a first segment of an SDU

PDCP Data PDU for DRBs
PDCP SDU
Header
Field
Meaning Length
(bits)
SRB
AM
DRB
AM
DRB
UM
D/C Data / Control
flag
1 X X
R Reserved 1 X X X
SN Sequence
Number
12/18 12 12/18 12/18
MAC-I MAC Integrity 32 X option option
D/C R R R R R byte 1
byte 2
byte 3
D/C R R R byte 1
byte 2
SN
SN
SN
or
SN
SN
SDU
• Same header structure as LTE
• 12 or 18 bits SN field (7, 12, 15, 18 in LTE)

SDU • Same as LTE
• Used for BCCH, PCCH, and CCCH
RLC Data PDU format - RLC TM PDU
SDU
PDU

• Similar (but not same) header structure as LTE
• 18 or 12 bits SN field (16 or 10 in LTE)
• Just one SDU or one segment per RLC PDU (no concatenation)
• Segmentation of RLC SDU / PDU:
• SI field indicates First and/or/nor Last byte of SDU
• Same SN for a SDU, and all segments
• SO describes the non-zero offset for a neither-nor segment
• Receiver can reassemble RLC SDU by SN, SO, or SI
• RF and LI fields are not used in contrast to LTE
RLC SDU
Header
Field
Meaning Length
(bits)
UM AM
D/C Data / Control flag 1 N/A X
P Poll bit 1 N/A X
SI Segmentation Info* 2 X X
R Reserved 1 X X
SN Sequence Number 18/12 X X
SO Segmentation Offset 16 X X
D/C P R R byte 1
byte 2
byte 3
D/C P R R byte 1
byte 2
byte 3
byte 4
byte 5
SN
SN
SO
SI
SI
SO
SN
or
SN
SN
SN
RLC Data PDU Format - RLC AM PDU (18 Bits SN)
AM PDU (18 bits SN for SDU segment)
AM PDU (18 bits SN for SDU)
SDU

RLC Control PDU Format - STATUS PDU (18 Bits SN)
• Extends RLC status reporting from LTE by adding block NACK reporting.
• E3=1 multiple adjacent SN missing, indicated by NACK range.
• SOstart and SOend appear before NACK range if both are used.
7 6 5 4 3 2 1 0
D/C Oct 1
Oct 2
E1 R Oct 3
Oct 4
Oct 5
E1 E2 E3 R R R Oct 6
Oct 7
Oct 8
Oct 10
Oct 11
Oct 12
Oct 13
Oct 14
Oct 15
Oct 16
Oct 18
…
SOend
SOend
NACK_SN
NACK_SN
SOstart
SOstart
NACK_SN
NACK_SN
NACK_SN
NACK_SN
NACK_SN
ACK_SN
ACK_SN
NACK_SN
CPT
ACK_SN
NACK_SN
NACK range
Header Field Meaning Length
(bits)
D/C Data / Control flag 1
CPT Control PDU type 3
ACK_SN Acknowledgement SN 12/18
E1 1: [NACK_SN,E1,E2,E3] follows 1
E2 1: [SOstart, SOend] follows for this NACK_SN 1
E3 1: NACK Range follows from this NACK_SN 1
NACK_SN SN detected as lost 18/12
NACK range Number of adjacent SNs lost including NACK_SN 8
SOstart Position of First byte of lost portion with NACK_SN 16
SOend Position of Last byte of lost portion with NACK_SN 16
MAC RLC control MAC CE MAC Padding CE
MAC CE
… …
MAC RLC RLC SDU MAC RLC RLC SDU

RLC SDU
Header
Field
Meaning Length
(bits)
UM AM
D/C Data / Control flag 1 N/A X
P Poll bit 1 N/A X
SI Segmentation Info* 2 X X
R Reserved 1 X X
SN Sequence Number 18/12 X X
SO Segmentation Offset 16 X X
RLC Data PDU Format - RLC AM PDU (12 Bits SN)
D/C P byte 1
byte 2
D/C P byte 1
byte 2
byte 3
byte 4
SN
SN
SN
SO
SI
SI
SO
or
SN
AM PDU (12 bits SN for SDU segment)
AM PDU (12 bits SN for SDU)
SDU • Similar (but not same) header structure as LTE
• 18 or 12 bits SN field (16 or 10 in LTE)
• Just one SDU or one segment per RLC PDU (no concatenation)
• Segmentation of RLC SDU / PDU:
• SI field indicates First and/or/nor Last byte of SDU
• Same SN for a SDU, and all segments
• SO describes the non-zero offset for a neither-nor segment
• Receiver can reassemble RLC SDU by SN, SO, or SI
• RF and LI fields are not used in contrast to LTE

RLC Control PDU Format - STATUS PDU (12 Bits SN)
• Extends RLC status reporting from LTE by adding block NACK reporting.
• E3=1 multiple adjacent SN missing indicated by NACK range.
• SOstart and SOend appear before NACK range if both are used.
Header Field Meaning Length
(bits)
D/C Data / Control flag 1
CPT Control PDU type 3
ACK_SN Acknowledgement SN 12/18
E1 1: [NACK_SN,E1,E2,E3] follows 1
E2 1: [SOstart, SOend] follows for this NACK_SN 1
E3 1: NACK Range follows from this NACK_SN 1
NACK_SN SN detected as lost 12/18
NACK range Number of adjacent SNs lost including NACK_SN 8
SOstart Position of First byte of lost portion with NACK_SN 16
SOend Position of Last byte of lost portion with NACK_SN 16
7 6 5 4 3 2 1 0
D/C Oct 1
Oct 2
E1 R R R R R R R Oct 3
Oct 4
E1 E2 E3 R Oct 5
Oct 6
E1 E2 E3 R Oct 7
Oct 8
Oct 9
Oct 10
Oct 11
Oct 12
Oct 13
E1 E2 E3 R Oct 14
Oct 15
NACK_SN
…
SOend
SOend
SOstart
SOstart
NACK_SN
ACK_SN
ACK_SN
CPT
NACK_SN
NACK range
NACK_SN
NACK_SN
NACK_SN
MAC RLC control MAC CE MAC Padding CE
MAC CE
… …
MAC RLC RLC SDU MAC RLC RLC SDU

MAC RLC PDCP Data Unit
MAC Sub-PDU Format for SDU (Service Data Unit)
Header
Field
Meaning Length
(bits)
R Reserved 1
F Format Field 1
LCID Logical Channel Id 6
L Length of data in bytes 8/16
R F=0 byte 1
byte 2
R F=1 byte 1
byte 2
byte 3
LCID for SDU
L
or
L
L
LCID for SDU
SDU • Similar MAC subheader structure as in LTE
• 6 bits LCID field (5 in LTE).
• 1 or 2 bytes Length (L) field in MAC subheader for SDU
• 0, 1 … 32 is used for ‘identity of logical channel’
• 0,1 … 16 in LTE
MAC SDU

MAC SUB-PDU format for CE (Control Element)
• No Length (L) field for fixed size CEs
• 1 or 2 bytes Length (L) field in variable size CEs
• Upper range of LCIDs (63, 62 …) is used for CEs
• In a DL PDU, CEs are placed in front on SDUs
• In a UL PDU, SDUs are placed in front on CEs
• If needed, padding is always placed at the end
R R byte 1
R F=0 byte 1
byte 2
R F=1 byte 1
byte 2
byte 3
L
L
L
LCID for CE (fixed size)
LCID for CE (variable small size)
LCID for CE (variable large size)
MAC CE MAC SDU MAC Padding CE
MAC CE MAC SDU
. . . . . .
UL PDU :
DL PDU :
MAC CE
MAC SDU MAC Padding CE
MAC CE
MAC SDU . . .
. . .
LCID in DL is used for
111000 - 111010 Activation/Deactivation
111101 TAC
111111 Padding
LCID in UL is used for
111000 - 111001 PHR
111011- 111110 BSR
111111 Padding

NR SU-MIMO Digital
Beamforming

Background
— This feature provides beamforming functionality for the NR 64TRX AAS, enabling Full-Dimension
MIMO (FD-MIMO).
— Antenna configuration is 4x8x2.
V
H
2D antenna array
4
rows
8 columns
Subarray with
2-4 x-pol elements

FeatureOverview
— DL cell shaping
— PSS/SSS/PBCH/PDCCH/PDSCH/DMRS
— UL cell shaping and UL SU-MIMO with 1 layer
— PRACH/PUCCH/PUSCH
— Up to 4 layer codebook-based beamforming for DL SU-MIMO
— DL codebook-based beamforming
— CSI-RS configurations and CSI reports
MOM-configurable
sector shape and
digital tilt
HIGHRISE V
H

SystemConfigurations
— Operators can configure systems with MOM attributes for the following
deployment scenarios:
— Macro site (large horizontal angle, relatively smaller vertical angle)
— Hot spot (large horizontal angle, large vertical angle)
— High-rise (relatively smaller horizontal angle, large vertical angle)
Deployment
scenario
Macro site Hot spot High Rise
Horizontal HPBW 65o 65o 20o
Vertical HPBW 8o 30o 30o

BenefitsandGains
— Flexible cell coverage for different cell shapes, including the elevation dimension.
— UL and DL beamforming has the following benefits:
— Improves network capacity by increasing cell throughput.
— Reduces interference and improves throughput for cell-edge users
— Improves network coverage by increasing the range of signals, improving signal gain and
reducing interference

Energy Performance
Feature

MicroSleepTx
— Micro Sleep Tx decreases energy consumption in the RU by automatically turning off the PA when
there is nothing to transmit on the downlink.
— When no data is scheduled in the cell, it is possible to turn off the PA without degrading the
performance. Better energy savings potential in NR because of less continuous system information
transmission compared to LTE.
— Micro Sleep Tx is basic feature and always enabled.

Throughput

Downlink,Single-layer
› For multiple layers, the single-layer peak throughput is scaled by the number of layers.
› TDD pattern: 3DL+1UL slots
• Note: Throughput provided by NR leg. The throughput provided by LTE leg may be aggregated with NR leg through LTE-NR Dual connectivity.
LTE CA is supported pending UE capability.
0.00
50.00
100.00
150.00
200.00
250.00
300.00
350.00
400.00
450.00
1 DMRS 1+1 DMRS 1 DMRS 1+1 DMRS
64QAM 256QAM
Downlink, Single-layer
20 40 60 80 100

AggregatedLTE+NRPeakThroughput(Mbps)
Downlink
0.00
500.00
1000.00
1500.00
2000.00
2500.00
3000.00
NR 2 layers NR 4 layers NR 2 layers NR 4 layers
64QAM 256QAM
Aggregated LTE + NR Peak Throughput (Mbps)
(Downlink)
20 40 60 80 100
› LTE FDD DL peak throughput is based on 16 DL MIMO layers ( with DL 4/5CC CA).
– LTE CA is pending on UE capabilities
› The EN-DC efficiency factor is assumed to be 0.8 ( This factor may vary in different load and RF condition).
› NR Throughput is based on “3DL+1UL” TDD Pattern supported in 2018 Q4 :

PeakNRThroughput(Mbps)
Uplink,Single-layer
0
20
40
60
80
100
120
140
20 40 60 80 100
Uplink, Single-layer
64QAM 1 DMRS 64QAM 1+1 DMRS
› TDD pattern: 3DL+1UL slots
› 20/100MHz BW, 1+1 DMRS and uplink 1 layer
• Note: Throughput provided by NR leg.

— MAC – MediumAccess Control
— MCS – ModulationCoding Scheme
— MIB – MasterInformation Block
— NR – New Radio
— NSA – Non-Standalone
— RAR - RandomAccess Response
— RBG - Resource Block Group
— REG – Resource-element Group
— RI – RankIndicator
— RLC – RadioLink Control
— RS – Reference Signal
— SCS – Subcarrier Spacing
— SPS - Semi-persistentScheduling
— SR – Scheduling Request
— SRS – Sounding Reference Signal
— SSS - SecondarySynchronizationSignal
— SU-MIMO - Single-userMultiple Input Multiple Output
— TB – TransportBlock
— TPC - TransmitPower Control
— TRS - TrackingReference Signal
— UCI - Uplinkcontrolinformation
— USS - UE-specificSearchSpace
— BWP – Bandwidth Part
— CBG – Code Block Group
— CCE – Control ChannelElement
— CQI – ChannelQuality Indicator
— CORESET – Control Resource Set
— CP – Cyclic Prefix
— CSI - Channelstate information
— CSI-IM CSI-Interference Management
— CSS – Common Search Space
— DCI - Downlink control information
— DMRS – Demodulation Reference Signal
— FR1 – Frequency Range 1
— PBCH - PhysicalBroadcast Channel
— PDCCH - PhysicalDownlink Control Channel
— PDCP - Packet Data Convergence Protocol
— PDSCH - Physical Downlink Shared Channel
— PHR – Power Headroom Report
— PRACH - PhysicalRandom Access Channel
— PRB – PhysicalResource Block
— PRG - Precoding Resource Block Group
— PSS- Primary Synchronization Signal
— PUCCH - PhysicalUplink Control Channel
— PUSCH - Physical Uplink Chared channel
Abbreviations

EN-DC Functionality

TableofContents
— EN-DC Architecture and Interfaces
— Idle Mode Behavior
— EN-DC Bearer Types
— NR Leg Setup and Release
— Configuration of Carrier Aggregation
— Mobility
— Inactivity Supervision
— EN-DC User-plane functionality
— LTE & NR Power Sharing
— Handling of S1 E-RAB Procedures
— VoLTE and CSFB support

EN-DC Architecture and
Interfaces

EN-DCArchitecture
— E-UTRA-NR Dual Connectivity (EN-DC):
— a UE is connected to one eNB that acts as a Master Node (MeNB) and one gNB that acts as a
Secondary Node (SgNB).
— control plane signalling is via eNB
— the eNB is connected to EPC via the S1 interface and to the gNB via the X2-C and X2-U interface.
— the gNB is connected to EPC via the S1-U interface.
eNB
EPC/SGW
gNB
S1-C
S1-U: SN terminated DRB
NR cell
LTE cell
LTE Uu (SRB + DRB) NR Uu (DRB)
eNB provides the Master Cell Group (MCG)
gNB provides the Secondary Cell Group (SCG)
EPC/MME
S1-U: MN terminated DRB
NR cell
X2
X2
gNB
One gNB can be connected to
multiple eNBs
One eNB can
connect to
multiple gNBs

EN-DCInterfaces
— RCF – Radio Controller Function
— Corresponds to 3GPP logical entity CU-CP
in a gNB
— PPF – Packet Processing Function
— Corresponds to 3GPP logical entity CU-UP
in a gNB
— RPF – Radio Processing Function
— Corresponds to 3GPP logical entity DU in a
gNB
eNB gNB
EN-DC
UE
X2-U
S1-U
Control plane
X2-C (NR RRC)
NR L1&L2
LTE RRC (NR RRC)
S1-C
User plane
RCF PPF
RPF
S1-U
RCF
PPF & RPF
LTE L1&L2
CU-CP = Centralized Unit – Control Plane
CU-UP = Centralized Unit – User Plane
DU = Distributed Unit

Idle Mode Behavior

IdleModeBehaviorforEN-DC-capable
UEs
— EN-DC capable UEs are camping in LTE, i.e. the following idle mode tasks are performed in LTE
— PLMN selection
— System information acquisition
— Cell selection and reselection
— Tracking area update
— Paging
— Idle mode behavior for EN-DC capable UEs are identical to idle mode behavior for legacy LTE UEs

NRIndicatorinSIB2
— Network support for EN-DC can be indicated in SIB2.
— The information can be used by the UE to e.g. display a “5G icon” on the
phone.
— EN-DC support in SIB2 is configurable per E-UTRAN cell and PLMN.
— One PLMN in the cell can be selected for EN-DC usage.
5G

EN-DC Bearer Types

— MN terminated MCG DRB (Legacy LTE DRB):
— LTE PDCP configuration
— KeNB
— LTE Cell Group
— SN terminated Split DRB:
— NR PDCP configuration
— S-KgNB
— LTE Cell Group and NR Cell Group
— SRB:
— LTE PDCP configuration
— KeNB
— LTE Cell Group
EN-DCBearerTypes

MeNB SgNB
EN-DCBearerTypes
NetworkPerspective
SRB
(KeNB)
MN terminated MCG bearer (“Option1” )
(KeNB)
SN terminated Split bearer (“Option 3x”)
(S-KgNB)
LTE RLC
LTE PDCP NR PDCP
NR MAC
NR RLC
LTE PDCP
LTE RLC
LTE MAC
LTE RLC

— EN-DC-capable UEs are connected with one of
the following:
— MCG DRB(s) in areas with no NR coverage
— Split DRB(s) and/or MCG DRB(s) in areas
with NR coverage
— Configurable per QCI and ARP
— Possible to mix MCG DRBs and Split DRBs
for the same UE
— Up to 8 DRBs per UE supported
— Legacy LTE UEs are connected with the
following:
— MCG DRB (Option 1)
— An eNB can support both UE types
simultaneously.
NetworkSupportforLTE-onlyand
EN-DC-capableUEs
LTE MAC NR MAC
LTE RLC
LTE PDCP
MCG DRB
(Option 1)
NR PDCP
Split DRB
(Option 3x)
LTE RLC NR RLC
MeNB SgNB

— NR Leg Setup
— Bearer is reconfigured to an
SN terminated Split DRB
— Change of PDCP version and
security key
— Measurement based setup
(B1) or configuration based
setup (blind)
— Initial Context Setup
— Bearer is set up as
MN terminated MCG
DRB
— User plane data over
LTE radio only
— NR Leg Release
— Bearer type is changed to
MN terminated MCG DRB
— Change of PDCP version
and security key
— Triggered by e.g. NR RLF,
NR Cell lock
EN-DCBearerTypeTransitions
MN terminated
MCG DRB
SN terminated
Split DRB
Initial Context
Setup
NR Leg Setup
NR Leg Release
Release to Idle
mode
— Release to Idle mode
– UE is released to IDLE
mode
– Any resources for the
Split DRB in the eNB and
the gNB are released

NR Leg Setup and Release

— Two step procedure for EN-DC establishment:
1. At Initial Context Setup bearers are setup as a MN
terminated MCG DRB.
— EN-DC specific UE capabilities are fetched if
not received from core network
— Optionally a B1 measurement is started.
2. The bearer is reconfigured to a Split bearer and the
NR Leg is added
a. at reception of a B1 measurement report
(measurement based setup), or
b. after the Initial Context Setup procedure is
completed (configuration based setup)
— Initial User-plane configuration for the Split DRB:
— Downlink: NR
— Uplink: LTE or NR (configurable)
EN-DCEstablishment-Overview
UE MeNB SgNB EPC
Initial Context Setup
• Fetch of EN-DC specific UE capabilities
(optional)
• Start of B1 measurements (optional)
NR Leg Setup (eNB to gNB relocation)
B1 Measurement Report

SelectionofCandidateNRCell
The candidate NR cell is identified by its Physical Cell Id (PCI)
and Frequency.
Measurement based NR Leg Setup
— NR IRAT measurements (Event B1) are started during
Initial Context Setup procedure
— Measurements are started if the criteria to setup the NR
Leg are fulfilled
— Measured quantities: SSB RSRP, RSRQ or RS-SINR
— Candidate NR cell is the best cell listed in the B1
Measurement Report.
Configuration based NR Leg Setup
— One candidate NR cell can be configured per EUtranCell
ManagedElement
ENodeBFunction
“GUtraNetwork”
“ExternalGNodeB
Function”
“ExternalNrCell”
EUtranCell
eNodeB
(RadioNode)
“NrFrequency”
“Candidate NR
cell” for
Configuration
based NR Leg
Setup

NRLegSetupCriteria
— NR Leg Setup is initiated if
— Basic Intelligent Connectivity license is activated in eNB
— EN-DC support is enabled in the E-UTRAN cell
— X2 connection is established to the gNB controlling the candidate NR cell
— UE is EN-DC capable and supports 2 Tx in UL
— UE supports the LTE and NR frequency band combination
— EN-DC is allowed for the PLMN used by the UE
— NR Leg setup is only initiated for the DRBs configured as “Split DRB enabled”. Other DRBs remain
as MN terminated MCG bearers.
— “Split DRB enabled” is configurable in eNB based on QCI and ARP

NRLegSetup
eNBtogNBrelocation,ULinLTE
UE SgNB
MeNB SGW MME
UL/DL User data in LTE
RRC: B1 Measurement Report
Prepare for DRB reconfiguration
X2: SgNB Addition Request (RRC: CG-ConfigInfo)
Allocate PDCP and SCG resources.
X2: SgNB Addition Request Acknowledge (RRC: CG-Config)
Suspend DRB
X2: SN Status Transfer
RRC Reconfiguration (“Add SCG” stop B1)
LTE Random Access
RRC Reconfiguration Complete
X2: SgNB Reconfiguration Complete
UL User data in LTE (new ciphering key)
NR Random Access
S1-AP: E-RAB Modification Indication
S1-AP: E-RAB Modification Confirm
Bearer
Modification
Prepared for UL data
Resume DRB
End marker packet
New path
LTE PDCP NR PDCP
LTE RLC LTE RLC NR RLC
LTE MAC NR MAC
SGW
S1-U
S1-U
PDCP COUNT + DL
data forwarding
X2-U
RA RA
DL Data forwarding
MeNB SgNB
LTE MAC
DL User data in NR (new ciphering)
User-plane

— MeNB initiated NR Leg Release triggered at:
— UE detected RLF
— Failed random access
— RLC UL delivery failure
— Out of synchronization (SSB)
— LTE handover
— SgNB initiated NR Leg Release triggered at:
— gNB detected RLF
— RLC DL delivery failure
— NR cell lock
NRLegReleaseOverview
UE MeNB SgNB EPC
NR Leg Release (gNB to eNB relocation) +
Start B1 measurement
SCG Failure Indication NR
MeNB initiated NR Leg Release
RLF, NR Cell Lock
SgNB initiated NR Leg
Release
RLF, suspend SCG

MeNB-initiatedNRLegRelease
gNB to eNBRelocation,ULinLTE
UE SgNB
MeNB SGW MME
UL User data in LTE
SgNB Release Request
Suspend DRB
SgNB Release Request Ack
SN Status Transfer
RRC Reconfiguration (release SCG + start B1)
LTE Random Access
UL User data in LTE (new ciphering)
E-RAB Modification Indication
E-RAB Modification Confirm
Bearer
Modification
New path
LTE PDCP NR PDCP
LTE MAC NR MAC
SGW
S1-U
X2-U
S1-U
PDCP COUNT
DL User data in NR
UE Context Release
Release resources
Release resources
RA
User-plane
LTE MAC
MeNB SgNB
Resume DRB
Trigger NR Leg Release

SgNB-initiatedNRLegRelease
gNBtoeNBRelocation,ULinLTE
UE SgNB
MeNB SGW MME
UL User data in LTE
SgNB Release Required
Suspend DRB
SgNB Release Confirm
SN Status Transfer
RRC Reconfiguration (release SCG + start B1)
LTE Random Access
UL User data in LTE (new ciphering)
E-RAB Modification Indication
E-RAB Modification Confirm
Bearer
Modification
LTE PDCP NR PDCP
LTE MAC NR MAC
SGW
S1-U
X2-U
S1-U
PDCP COUNT+ DL
data forwarding
DL User data in NR
UE Context Release
Release resources
Release resources
RA
User-plane
LTE MAC
MeNB SgNB
Trigger NR Leg Release
Resume DRB

— UE Release to IDLE mode with Split bearer
triggered at
— X2 link break detected in eNB
— MME initiated UE release to IDLE mode
— eNB initiated UE release to IDLE mode due
to e.g. inactivity
UEReleasetoIDLE-Overview
UE MeNB SgNB MME
Release to IDLE (with Split DRB)
S1-AP: UE Context Release Request
X2 Link break detected
UE Context Release Command
S1-AP: Reset
S1-AP: Reset Acknowledge

Configuration of Carrier
Aggregation

ConfigurationofCarrierAggregation
— EN-DC capable UE without Split DRB:
— LTE CA configured as in legacy LTE
— EN-DC capable UE with Split DRB:
— Up to 5CC LTE CA + 1 NR CC supported in DL
— NR CC always prioritized
— Number of LTE CCs depend on UE BW and CC capabilities for the
target LTE + NR frequency band combination
— LTE Cross-DU Carrier Aggregation supported, LTE intra band and
inter band CA supported
— Separate thresholds used for UEs with Split DRBs to speed up
configuration and activation of LTE CCs after NR Leg
Setup/Release and leg switching
— One LTE CC and one NR CC supported in UL
Pcell
Scell
Scell
Scell
Scell
PScell
LTE
CC’s
NR CC

Mobility

NRMobility-Overview
— NR Mobility supported by release of NR leg in source cell followed by setup of NR leg in the target
cell
— NR Leg in source NR cell is released at RLF, bearer is reconfigured to MN terminated MCG DRB.
— When the bearer is reconfigured a B1 measurement is started in order to find a new NR cell

LTEMobility-Overview
— LTE Mobility for EN-DC capable UE without Split DRB:
— LTE handover and LTE RRC Re-establishment as in legacy LTE
— LTE Mobility for EN-DC capable UE with Split DRB:
— LTE Intra-frequency handover supported:
— The NR Leg for a Split DRB is released at reception of a A3 Measurement Report (neighbor cell
becomes better than serving cell), SN terminated Split bearers are reconfigured to MN terminated
MCG DRBs.
— LTE intra-frequency handover is performed as in legacy LTE at reception of the next A3
measurement report.
— After the handover is completed a blind or measurement based NR Leg Setup is initiated
— LTE Inter-frequency and IRAT handovers are prevented
— RRC Re-establishment requests will trigger a release to idle mode

Mobility
LTE
frequency
NR
frequency
NR Cell B
LTE Cell B
NR Cell C
NR Cell A
UE enters RRC
connected mode
NR Leg Setup
Cell A
NR Leg
Release NR
Cell A.
B1 report (NR
Cell B)
NR RLF
NR Leg
Setup NR
Cell B
NR Leg
Release NR
Cell B.
NR RLF
NR Leg
Setup NR
Cell C.
Intra-freq
Event A3 (1)
NR Leg
Release
NR Cell C.
B1 report (NR
Cell C)
NR Leg
Setup NR
Cell C.
NR RLF
NR Leg
Release NR
Cell C.
Intra-freq
Event A3 (2)
Legacy LTE HO
LTE Cell A B1 report (NR
Cell C)

RadioLinkFailure(RLF)
— UE detected RLF:
— Failed random access (scg-ChangeFailure)
— T304 is started at reception of SCG configuration at NR Leg Setup
— T304 is stopped at successful random access.
— T304 expiry -> radio link failure
— RLC UL delivery failure (RLC-MaxNumRetx)
— Number of UL RLC retransmissions exceeds a threshold
(maxRetxThresholds)
— Out of synchronization (t310-Expiry)
— UE monitors SSB and counts “in-synch” and “out-of-synch”
indications.
— N310 consecutive “out-of-synch” indications starts timer T310
— N311 consecutive “in-synch” indication stops timer T310
— T310 expiry -> radio link failure
— Network detected RLF
— RLC DL delivery failure
— Number of DL RLC retransmissions exceeds a threshold
UE MeNB SgNB EPC
MeNB initiated NR Leg Release
SCG Failure Indication NR
UE detected RLF
Network detected RLF
Suspend SCG
SgNB initiated NR Leg Release

Inactivity Supervision

— SgNB:
— Inactivity monitoring of the NR leg is located
in NR RLC and state changes are reported to
higher layer per DRB.
— Activity/Inactivity is reported over X2 to
MeNB taking all Split DRBs into account.
— MeNB:
— Inactivity monitoring of LTE leg is located in
LTE RLC and state changes are reported to
higher layer per DRB (legacy handling).
— MeNB considers both LTE Leg and NR Leg of
Split DRBs as well as MCG DRBs when
starting and stopping tInactivityTimer .
— At expiry of tInactivityTimer the UE is
released to IDLE mode.
InactivitySupervision
RLC
LTE leg
active/inactive
NR leg
active/inactive
UE
active/inactive
S1-U
Split DRB(s)
active/inactive PDCP
X2-AP
Activity/
Inactivity
Indication
tInactivityTimer NR Inactivity Timer
MeNB
SgNB
RLC
Solution is subject to change
DRB
active/inactive
MCG DRB(s) Split DRB(s)

EN-DC User Plane
Functionality

UPFunctionalityOverview
— Downlink
— Initial DL Leg switch LTE -> NR for Split DRB at NR Leg Setup
— Triggered at reception of NR Random Access Message 3
— DL Leg switching LTE <-> NR based on NR link quality estimates (Fast switching)
— Good NR quality: DL UP in NR Leg
— Poor NR quality: DL UP in LTE Leg
— Flow control
— DL DC Aggregation
— Uplink
— UL UP transmission for Split DRB controlled by operator parameter. Configuration is signaled to UE via
RRC at NR Leg Setup.
— always LTE (default)
— always NR

— DL DC Aggregation:
— DL User data is sent in both LTE and NR Leg
— Flow control on both LTE and NR Leg will minimize the
reordering in UE PDCP
— DL Fast Switch:
— DL user-data is sent in either LTE Leg or NR Leg
— Leg switching is based on NR link quality
— Good NR quality: Use NR Leg
— Poor NR quality: Use LTE leg
DLTransmissionModes
PDCP
LTE
Leg NR Leg
PDCP
LTE
Leg
NR Leg
PDCP
LTE
Leg
NR Leg
DL Fast Switch DL DC Aggregation
DL transmission mode is controlled by operator parameter
UL L1/L2 signaling on same leg as DL user data

The quality of the NR DL link is continuously
monitored for Split bearers.
NR DL quality is based on CQI reports. Samples are
filtered over time.
— Poor NR quality: DL NR quality < threshold
— Good NR quality: DL NR quality > threshold
+ hysteresis
DLFastSwitch
Single Leg
NR
Single Leg
LTE
Poor NR quality
Good NR quality
AND prohibit
timer expired
At NR Leg Setup PDCP will start to
transmit DL user data in the NR Leg after
successful NR Random Access.
Poor NR quality detected: an
immediate switch to Single LTE
Leg is triggered.
RLC DL Delivery Failure (RLF)
detected: SgNB requests NR Leg
Release via X2.
At fast switch between single LTE leg and single
NR leg:
– Unacknowledged data is retransmitted to
the new DL leg and unsent data is
discarded in old DL leg
Good NR quality detected: A switch
to Single NR Leg is triggered after a
prohibit timer has expired.
RLF
UL is either LTE or NR based on configuration

DLDCAggregation
Single Leg
NR
Single Leg
LTE
Aggregation
LTE + NR
Poor NR quality
Good NR quality
Poor NR quality
PDCP buffer age
> threshold
PDCP buffer
empty
RLC
PDCP
RLC
PDCP buffer empty:
Start next transmission
in Single NR Leg
Packets in PDCP buffer
older than threshold:
Start to schedule DL data
on both legs according to
Flow Control feedback
information.
Poor NR quality detected:
Resend non-acknowledged
packets in the LTE Leg
SgNB
MeNB
LTE Leg
NR Leg
FC Feedback: highest successfully
delivered PDCP sequence number
At NR Leg Setup PDCP will start to
transmit DL user data in the NR Leg
RLF
UL is either LTE or NR based on configuration

LTE & NR Power Sharing

LTE&NRPowerSharing
— Only UEs supporting 2 Tx branches will be configured with Split DRBs.
— For Split DRBs the UL Tx power needs to be shared between LTE and NR to make sure that Pcmax is
not exceeded.
— Pcmax is the UE power class.
— Support for “dynamic power sharing” is indicated in UE capabilities per LTE+NR band combination.
— UEs capable of Dynamic power sharing:
— If LTE and NR data are scheduled at the same time UE will prioritize LTE transmission and scale
down/drop NR transmission power so that its total power will not exceed Pcmax
— UEs not capable of Dynamic power sharing:
— Network need to split the power between LTE and NR in a semi-static way.

EN-DCPowerSettingsforSplitDRB
— Power setting 1: UE is capable of dynamic power sharing
— P-LTE: Pcmax
— P-NR: Pcmax
— Power setting 2: UE is not capable of dynamic power sharing
— P-LTE and P-NR set by operator

Handling of S1 E-RAB
Procedures

S1E-RABProcedures
— E-RAB Setup
— New bearer is set up as MN-terminated MCG DRB
— If the bearer is configured as “Split DRB allowed” a reconfiguration to SN terminated Split DRB will
be made at next “NR Leg Setup” trigger.
— E-RAB Release
— Release of MN-terminated MCG DRBs as in legacy LTE
— Release of SN-terminated Split DRBs is rejected towards Core Network, followed by eNB-initiated
release to IDLE mode.
— E-RAB Modify
— E-RAB Modify of MN-terminated MCG DRBs as in legacy LTE
— E-RAB Modify of SN-terminated Split DRB is accepted and ignored

VOLTE/CSFB Support

VoLTESupport
— Configuration of Split DRB is controlled per QCI
and ARP, e.g.
— QCI 5: Split DRB disabled
— QCI 1: Split DRB disabled
— QCI 9: Split DRB enabled
— An EN-DC capable UE can be configured with a
mix of MN terminated MCG bearers and SN
terminated Split bearers.
— VoLTE call + simultaneous NR data supported
with limited performance:
— TTI bundling cannot be activated
— Limited support for LTE mobility
— RRC Re-establishment triggers UE release to
idle mode
— X2 link break triggers UE release to idle mode
LTE MAC NR MAC
LTE RLC
LTE PDCP
QCI5
NR PDCP
QCI9
LTE RLC NR RLC
LTE RLC
LTE PDCP
QCI1
Only for trial activities due to limited
VoLTE performance!

SupportforCSFB
— CSFB from idle mode
— Supported as in legacy LTE
— CSFB in connected mode
— Supported as in legacy LTE for EN-DC capable UE with no Split DRB
— CSFB request from core network rejected for EN-DC capable UE with Split DRB

O&M Overview

TableofContents
— Introduction and overview
— Configuration Management including MOM and Autointegration
— Fault Management
— Performance Management
— ENM Topologies
— Troubleshooting
— Licensing
— SW/HW Management
— CPI

Introduction
— This presentation describes O&M for the planned Ericsson implementation of NR NSA 5G in 18.Q4
release.
— Note that 3GPP standards are not yet settled and implementation scope might change due to
currently unknown events so treat information herein as working material.
— ENM is a prerequisite for management of 5G (i e OSS-RC will not support management of “gNodeBs”).
— It is assumed that eNodeBs and “gNodeBs” in NR-NSA deployments are managed by the same ENM.
— One ENM will support management of up to 1000 “gNodeBs” in 18 Q4.
— ENM must be on a SW version that supports 5GRadioNode and eNodeB must be on a SW version that
supports EN-DC.
— It is assumed that ENM (including ENM applications) and management of Baseband Radio Nodes are
known.

O&MIntroduction
— The eNodeB and the ”gNodeB” are separate managed elements
of different managed element types
— A ”gNodeB” is managed in the same way, with the same
interfaces and applications as an eNodeB:
— ENM
— ENM Northbound Interface (NBI) *)
— EM tools (EMCLI, EMGUI and AMOS)
— New support for NR-NSA systems introduced in ENM
*) except for PM events
ENM
eNodeB
(RadioNode)
EMCLI
EMGUI
ENM
CLI
FM
AP
ENM-SHM
PM
BULK
CM
AMOS
“gNodeB”
(5GRadioNode)
…
ENM NBI
NMS
ME ME
NR-NSA system
ME Type
eNodeB RadioNode
”gNodeB” 5GRadioNode

MOMOverview
— Many MOM fragments are the same for the eNodeB and the ”gNodeB” -> all the basic O&M support
(CM, FM, PM, Upgrade, etc.) works in the same way for the two ME types
— The difference between the two ME types is that the eNodeB has the ENodeBFunction while the
“gNodeB” will have three other functions that are standardized by 3GPP
“gNodeB”
(5GRadioNode)
ManagedElement
Equipment
Transport
GNBCUCPFunction
SystemFunctions
NodeSupport
GNBCUUPFunction
GNBDUFunction
eNodeB
(RadioNode)
ManagedElement
Equipment
Transport
ENodeBFunction
SystemFunctions
NodeSupport
EquipmentSupport
Function
EquipmentSupport
Function

ENMSupportfor“gNodeB”andNR-NSASystem
— ENM will provide the same basic O&M support for
“gNodeB” (CM, FM, PM, etc.) as for eNodeB
— ENM Support added for management of an NR-NSA
system (an eNodeB with connected “gNodeBs”)
— NR-NSA Topology added to “selection” panels in
applicable applications
— Autointegration of “gNodeB” and reconfiguration
of eNodeB in a single AP project
— Support for logical and geographical views of
NR-NSA systems

O&M Use Cases

— 3GPP (TS 28.541) works with
standardization for NR with first step in
release 15
— NR model much more standardized than
LTE model
— Prepared for high layer split architecture
— Three managed functions
— Two cells
— X2 between eNodeB and “gNodeB”
modeled via End points
MOMin“gNodeB”accordingto3GPP forNR
“gNodeB”
(5GRadioNode)
ManagedElement
GNBDU-
Function
GNBCUUP-
Function
GNBCUCP-
Function
NRCellCU
NRCellDU
EndPoint_X2C
EndPoint_X2U
eNodeB
(RadioNode)
X2-U
X2-C

— By implementing the “3-split” already
from the beginning the “gNodeB” is
prepared for the future:
— 5G RAN will have the same look and
feel independent of deployment
— To move between different
deployments will be fairly easy, e.g.
from embedded deployment to vRAN
deployment
— Multi vendor scenarios will be
supported via standardized interfaces
Why“3-split”?
GNBDU-
Function
GNBCUUP-
Function
NRCellDU
GNBCUCP-
Function
NRCellCU
F1-U F1-C
E1

MOMupdatesineNodeBforNR-NSAsupport
— MOM updates in eNodeB to support NR-NSA
deployment:
— X2 between the eNodeB and connected
“gNodeB´s”
— candidate NR cell
ManagedElement
ENodeBFunction
“GUtraNetwork”
“ExternalGNodeB
Function”
“ExternalNrCell”
EUtranCell
eNodeB
(RadioNode)
“NrFrequency”
“EndPoint_X2U”
“gNodeB”
(5GRadioNode)
“EndPoint_X2C”
X2-U
X2-C

Auto-Integration
— A “gNodeB” can be autointegrated in the same way as an eNodeB
— Several different deployment scenarios will be supported in AP in ENM:
— ”gNodeB” is integrated to an existing eNodeB
— ”gNodeB” and eNodeB are integrated in the same roll-out activity
— Integration of a “gNodeB” and necessary reconfigurations of the eNodeB are
supported in the same AP project
— For autointegration of a “gNodeB”, similar configuration files are needed as for
an eNodeB
— ECT can be used to validate configuration files for a “gNodeB” in the same way
as for an eNodeB”
— Before ANR is standardized and developed, X2 between eNodeB´s and
“gNodeB´s” have to be configured in configuration files
gNodeB-Rollout-Project
ProjectInfo.xml
gNodeB-Node
•nodeInfo.xml
•siteBasic.xml
•siteInstallation.xml
•siteEquipment.xml
•License.xml
•TNBulkCM.xml
•RNBulkCM.xml
eNodeB-Node
•nodeInfo.xml
•License.xml
•X2-Configuration

ConfigurationManagement
— The eNodeB and the ”gNodeB” are configured
separately
— CM notifications are sent from the “gNodeB” in the
same way as from the eNodeB
— Fewer configuration options will be available on
the “gNodeB” compared to the eNodeB since the
MOM will contain fewer attributes
— mainly due to that no control plane exists on
the “gNodeB”
ENM
eNodeB
(RadioNode)
“gNodeB”
(5GRadioNode)
NMS

ConfigurationManagementTools
— ENM CM tools have support for “gNodeB” in the
same way as for eNodeB:
— Network Explorer, Topology Browser
— ENM CM CLI and scripting
— Parameter Management
— Bulk import/export, Dynamic CM NBI (CM Events)
— All supporting Multi-ME operations
— AMOS
— Same supported operations as legacy
— EM tool
— EMCLI available for “gNodeB” both on site and
from ENM

FaultManagement
— The eNodeB and the ”gNodeB” have individual alarm
handling
— Heartbeat alarm from ENM for each ME
— Link break on X2
— At link break detection on X2, link recovery actions
are initiated
— If recovery actions at link break do not succeed,
alarms are raised in the “gNodeB”
ENM
eNodeB
(RadioNode)
“gNodeB”
(5GRadioNode)
NMS
X2

FaultManagementTools
— ENM FM tools have the same support for
the ”gNodeB” as for the eNodeB:
— Alarm Monitor
— 3GPP CORBA NBI
— FM CLI
— EM tools
— EMCLI and EMGUI available for the
”gNodeB” both on site and from ENM

— PM counters are handled in the same way in the eNodeB and
the “gNodeB”, e.g. same file format
— PM events are handled in the same way in the eNodeB and
the “gNodeB”. Some differences like format of the data for
the “gNodeB” compared to eNodeB
— PM for Control Plane: Mainly from the eNodeB
— PM for User Plane: Both from the eNodeB and the ”gNodeB”
— Event Based Statistics (EBS) to produce counters in ENM
based on PM events
PerformanceManagement-Overview
ENM
eNodeB
(RadioNode)
“gNodeB”
(5GRadioNode)
NMS
PM counters
PM events
PM counters PM events
PM events
Control plane
+User plane
PM counters
PM events
User plane
EBS

ENMPerformanceManagementTools
— ENM PM tools will support the ”gNodeB” in
the same way as the eNodeB
— Support for generation of “gNodeB” PM
counters in EBS
— ENIQ Statistics support, including reports
with ”gNodeB” KPIs
— Network Health Monitor with ”gNodeB” KPIs

Deep Dive 5G NR-RAN Release 2018 Q4.pptx

Deep Dive 5G NR-RAN Release 2018 Q4.pptx

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Deep Dive 5G NR-RAN Release 2018 Q4.pptx

Similaire à Deep Dive 5G NR-RAN Release 2018 Q4.pptx (20)

Dernier

Dernier (20)

Deep Dive 5G NR-RAN Release 2018 Q4.pptx

Notes de l'éditeur