5G Training V1 Shared
5G Training V1 Shared
5G Training V1 Shared
standardization
07-04-2016
2 © Nokia Networks
<Change information classification in footer>
Standardization plan in
3GPP
LTE-A evolution 5G
>20 MHz carrier BW support No need (Covered with CA) Yes
Lower latency Yes (TTI < 0.5 ms may not be needed) Yes
Ultra-low cost MTC Yes (LTE-M, NB-IoT) Yes (May adopt low cost from NB-IoT)*
* With NB-IoT there is no obvious need for low cost 5G solution in near term. Release 14 solution with 200 kHz
From cost (and ecosystem) point of view not foreseen how to make clearly better with 5G in this segment.
5 © Nokia 2015
5G Technology Study item
- Key issues before actual specification work starts
Requirements
RAN1
Waveform &
numerology Phase I Work Item
Frame structure & timing
Channel coding
L1 structures (Data,
Control, RACH channels)
MIMO principles
8 © Nokia Networks
5G Technology study fronthaul functional split
• Many functional split possibilities – different fronthaul requirements
Cloud RAN functionality options
5G larger bandwidth + use of more
5G RRC 5G RRC 5G RRC 5G RRC
antenna elements makes having only RF
5G PDCP 5G PDCP 5G PDCP 5G PDCP
at site in most cases not-feasible
5G RLC 5G RLC 5G RLC
5G MAC 5G MAC 5G radio specification work should
5G PHY consider functional split in early phase as
it has major development impact
5G RLC
5G MAC 5G MAC RAN3 work could start in 04/2015
5G PHY 5G PHY 5G PHY (impacts L1 processing times & data
5G RF 5G RF 5G RF 5G RF rates)
Antenna site functionality options Nokia prefers specifying at least
fronthaul functional split in 3GPP, where
Fronthaul interface to define the actual interface needs still
be determined (different L1s possible)
9 © Nokia Networks
Path to “5G and 5G optimized architecture” in 3GPP – Phasing overview
• The following implications to the physical layer design can be derived from the requirements
3.4 3.6
Korea 2018
OFDM symbol
DL only DL-C DL DL DL DL DL
N scRB subcarriers
N scRB subcarriers
Subcarriers/ carrier 1200
N PRB 100 Resource element (k , l )
UL
N RB
• 1 PRB (Physical Resource Block): 12 subcarriers
• 1 PRBG (G=Group) : 4 Consecutive PRB = 48 subcarriers
• PRBG is a minimum resource allocation unit
k 0
l0 l N symb
UL
1
22 © Nokia Solutions and Networks 2014
Dc: DL ctrl, Dd: DL data, Ud: UL data, Uc: UL ctrl, GP: Guard Period
Frame structure B.RS: BRRS, C.RS: CSI-RS, SRS: Sounding RS
Broadcast subframe
Common Control subframes Data subframes Data subframe index
index
DL with bi- 2 Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd GP Uc Uc
directional 3 Dc Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd
control 4 Dc Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd GP Uc
5 Dc Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd GP Uc Uc
6 Dc GP Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
7 Dc GP Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Uc
UL with bi- 8 Dc GP Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Uc Uc
directional 9 Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud
control 10 Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Uc
11 Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Uc Uc
23 © Nokia Solutions and Networks 2014
*) we can select a sub-set of these to minimize the number of configurations to test and implement. May need also
2 symbol GP for larger cells
Access Link operation (1/2)
• eNB can dynamically select the sybframe type among predetermined subframe types
• UE determines the subframe type from xPDCCH
Downlink Uplink
• DL grant (xPDCCH) and related xPDSCH are • Predetermined scheduling delay for
located in the same subframe
• UE processing time: xPUSCH (e.g. 1 subframe).
• Predetermined time for xPDSCH reception • This provides sufficient processing time for
and xPUCCH preparation (e.g. 1-2 UE to detect UL grant and prepare xPUSCH
subframes) • Asynchronous HARQ: All retransmissions
• xPDSCH HARQ-ACK timing is indicated explicitly in
the DL grant are trigged by DCI (No need for PHICH).
… … XPUCCH
xPDSCH
xPUSCH
xPDSCH
24 scheduling
07/04/2016 © Nokia 2014 - File Name - Version - Creator - DocID
xPUSCH
HARQ-ACK delay scheduling
Confidential
Access Link operation (2/2) beam xPDCCH
symbol
UL & DL switch
xPDSCH
grants
subframe
xPDCCH
• Subframe contains one or more (= two) xPDCCH symbols
• Number of xPDCCH symbols is dynamically determined by eNB.
• There is an opportunity for RF beam switching after the 1st xPDCCH symbol
• FDM between parallel xPDCCH channels within each xPDCCH symbol UL & DL DL grants
• UE searches DCI from both two symbols that can be mapped to xPDCCH grants (+ possible UL grants for UEs
having xPDSCH in this
subframe)
xPUCCH beam
switch
• Subframe contains one or more (=two) xPUCCH symbols
• Support for xPUCCH repetition for improved coverage xPUCCH symbol
• Suppor for variable number of Ues transmitting xPUCCH
• Number of xPUCCH symbols is dynamically determined by eNB
• FDM between parallel xPUCCH channels witin each xPUCCH symbol
• There is an opportunity for RF beam switching before the last xPUCCH
symbol
subframe
25 Scalable design
07/04/2016
© Nokia forName
2014 - File xPDCCH/xPUCCH
- Version - Creator - DocIDis needed e.g. due to limitations of RF beamforming
Confidential
Framework
Beam based system
…
• Per port ESS to send common control
18RB PSS via 14x8 =112 RF beams
- xPBCH is for delivering essential information including sub-frame number & BS SSS • Assuming x-pol beams
beam configuration (beam per panel) 56 x-
pol beams (directions)
• xPBCH BRS/ per subframe
- Multi port TxD based on port specific BRS per sweeping block PBCH
…
subsequent control and data
#n
GP for RTD
• xPDSCH
- Supports CL-MIMO, SFBC
- Supports MU-MIMO
• Current assumption is ‘transparent’ MU-MIMO
- Reuse LTE codebook
- Same DMRS design for DL and UL: front-loaded DMRS structure
- For high velocity case additional DMRS would be needed
• xPDCCH
- TxD
- Localized transmission mode:
• Defining CRBG, xREG similar to ePDCCH (CRBG = 2 xREGs)
- First one or two OFDMA symbols in every data subframe : Separated search space at each symbol, AL 2, 4, 8, 16 are supported
- 4 DCI format : A1/A2 for UL, B1/B2 for DL
• Other UE specific RS
- On demand: PC-RS/CPE-RS, scheduled Beam Refinement RS (BRRS) *), scheduled CSI-RS
• xPUSCH
- Supports CL-MIMO, SFBC
- Reuse LTE codebook
- Same design for DMRS as for DL: front-loaded DMRS structure
• xPUCCH
- Format 1 series + format 2 to support larger payload to carry bundled HARQ ACK/NACK and CSI
- Does not exist at all subframe, PUCCH transmission is scheduled by DL grant
• SR
- Can be sent on PRACH subframes
- 8 bands of 72 tones, FDM with PRACH
- Also on xPUCCH (Format 1)
• SRS
- On demand transmission (aperiodic)
Will Nokia reuse the KT Answer: Yes, the intention is to promote the
5G SIG specification KT 5G SIG specification for trials with other
operators as well (subject to legal
with trials for other framework)
operators?
32 © Nokia Solutions and Networks 2014
Architecture
- Network slicing
33 07/04/2016
Nokia Confidential Devaki Chandramouli
Network Slicing | Optimized service delivery for heterogeneous use cases
Multiple independent instances on one physical network
E2e management & Security & Full automation and
orchestration Privacy self-optimization
Orchestrator
Connected car slice All kinds of NaaS
Smart Grid slice
HD video slice
Platforms
Leader of 5GPPP
Infrastructure NORMA*
5G multiservice
architecture design
5G ready
Cognitive Distributed Programmable AirFrame data enter
Dynamic network level Content & processing Software-defined
control & orchestration where its needed functions
Programmable core
and transport
10,000 x >10 Gbps 100 Mbps <1 ms 10-100 x ultra low 10 years
*5G Novel Radio Multiservice adaptive network Architecture
34 © Nokia Confidential
Internal
Network orchestrator for life-cycle management of network instances
Optimized service delivery for heterogeneous use cases
Network orchestrator
35 07/04/2016
Nokia Confidential
Network Slicing - Architecture principles and considerations
37 07/04/2016
Nokia Confidential
Multi-dimensional selection principle – use cases
Illustrations
Stationary IoT UE can request a service referred to as “session on demand” for a certain
application. In this case, network chooses functional entities necessary to support session on
demand (and no function selected to offer support for mobility).
Critical MTC UE can request a service referred to as “efficient user plane path” for a
certain application. In this case, network chooses functional entities necessary to
support low latency user plane path and at the same time offer support for route
optimization, as needed due to UE mobility.
38 07/04/2016
Nokia Confidential
Multi-connectivity
3GPP expected to have tight interworking between LTE and 5G
MAC MAC
one is discussing.
LTE 5G
• With below 6 GHz one can operate well in a
5G only mode, while with higher bands it
becomes more challenging – especially with
SWI/SPL mobility
PDCP PDCP PDCP • Verizon 28 GHz (39 GHz) are planned
RLC RLC RLC to be standalone (but stationary)
MAC MAC • Example figures from KT 5G SIG, 3GPP will
LTE 5G have more freedom in solution definition
39 07/04/2016 Alternative 3
Nokia Confidential
Thank you
Background reading: