5G Training V1 Shared

Download as pdf or txt
Download as pdf or txt
You are on page 1of 40

5G targets and

standardization
07-04-2016

1 © Nokia 2016 - confidential


Outline

- 5G targets & 3GPP standardization


- Spectrum
- Special interest groups (SIGs)
• Korea Telecom 5G specification
- Network architecture
• Multiconnectivity
• Network slicing

2 © Nokia Networks
<Change information classification in footer>
Standardization plan in
3GPP

3 © Nokia Solutions and Networks 2014


Outline
5G in 3GPP
• TSG RAN agreed (03/16) on the technology study items, further WI content and phasing to be nailed
down once actual WI to be started. The use case priorization will be a challenge (see later slides)
• For SI phase work vital to have good plan when different issues are to be decided (such as channel
coding, multiple access etc) which do not have direct linking with the actual WI phasing
• Above 6 GHz Channel modeling started already earlier
• 3GPP LTE Rel 14 – 16 progress not impacted by the 5G studies/work items (Parallel track requires
increased delegation)

2015 2016 2017 2018 2019 2020

Rel-13 Rel-14 Rel-15 Rel-16


Requirements SI
3GPP 5G
Technology SI(s) Phase 2 5G WI(s)
>6 GHz Ch- Phase 1
model SI 5G WI(s)
4 © Nokia Solutions and Networks 2014
LTE-Advanced Release 14 and 5G study item focus

LTE-A evolution 5G
>20 MHz carrier BW support No need (Covered with CA) Yes

New numerology for >6GHz No need Yes


bands
Unlicensed band support Yes (Aligned with licensed band LTE) 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)*

Ultra-reliable and low-latency No special attention Yes


MTC
V2V/V2I Yes Yes

* 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

• Key issues (Phase 1) to be resolved during 2016


• Standalone 5G support (or dual connectivity only as driven by Japanese
and Korea operators + Qualcomm)
• Frequency bands
• Use cases to cover besides eMBB
• If MTC addressed specifically or not towards phase 1
• Other key items to be decided
• What kind of OFDM, numerology, channel coding etc…

• These to be sorted out during the study, before actual


specification work gets started
6 © Nokia Networks
5G technology study in 3GPP – Key L1 decisions in 2016 from RAN1
These impact the HW development the most – important for all use cases
3GPP RAN1 & RAN3
SI start 04/2016 WI start 04/2017 (est)

2016 2017 2018

Requirements

RAN1
Waveform &
numerology Phase I Work Item
Frame structure & timing

Channel coding
L1 structures (Data,
Control, RACH channels)
MIMO principles

Channel Model above 6 GHz


7 © Nokia Networks
Protocols – planned timing in 3GPP with ready RRC spec 09/2018

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

1. Rel-15: Early 5G radio Phase 1: Early 5G radio


 Early5G radio optimized for eMBB
• Introduce 5G radio anchored to LTE radio to
 5G & LTE dual connectivity
ensure fast time to market.
 5G in standalone mode
• Introduce 5G standalone radio with lean  Dynamic QoS framework
core to facilitate 5G introduction for those  Mobility framework
operators that intend to capitalize on system  Network slicing (Core)
level advantages of 5G already from the  Flexible scalability of CP/UP functions.
early phase  Minimum feature set to ensure forward
2. Rel-16: 5G radio access compatibility for cMTC and mMTC
Phase 2
usecases
• Evolve 5G radio to support all use cases Phase 2: 5G radio access
with optimized architecture enabling new  Support for all use cases
5G Core
services  Local anchoring, low latency switching
 Multi-connectivity intra-5G, inter-RAT
New IF  Enhanced mobility framework.
 e2e Network slicing including RAN aspects
 Support for evolved LTE with new
X2+
LTE 5G AP architecture.

10 © Nokia Networks Nokia view on phase 1 and phase 2 standards


Requirements and new radio
physical layer technology
components

11 © Nokia 2016 - confidential


Requirements and new radio physical layer technology components

• Physical layer related requirements in the TR38.913 can be summarized as follows


 A very diverse set of deployments ranging from Indoor Hotspot to Extreme Rural coverage
 A wide range of spectrum bands up to 100 GHz and bandwidths up to 1 GHz
 Wide range of device speeds, up to 500 km/h
 Ultra-deep indoor coverage with tentative target of 164 dB MCL
 D2D/V2V links
 Target peak rate of 20 Gbps in uplink and 10 Gbps in downlink
 Significantly improved system capacity, user data rates and spectral efficiency over LTE
 Target C-plane latency of 10 ms
 Target U-plane latency of 4 ms for mobile broadband, and 0.5 ms for ultra low latency communication
 Target mobility-incurred connection interruption of 0 ms
 Target reliability of delivering a packet in 1 ms with 1-10-5 reliability
 Tentative target UE battery life of 15 years for massive MTC type terminals
 Improved UE energy efficiency while providing much better MBB data rate
 Improved network energy efficiency
 Target connection density of 1 million devices / km2
 Tight interworking with LTE
 Connectivity through multiple transmission points
 Operator-controlled sidelink (device-to-device) operation

12 © Nokia 2016 - confidential


Requirements and new radio physical layer technology components, cont.

• The following implications to the physical layer design can be derived from the requirements

Below 2 GHz Below 3 GHz 3 – 40 GHz 20 – 100 GHz


Network topology Wide area deployment Urban Area Small cell deployment Ultra dense small cells
deployment
Technologies eMBB, mMTC, URLLC eMBB, mMTC, URLLC eMBB, (mMTC, URLLC) eMBB, (URLLC)
Waveform OFDMA based OFDMA based OFDMA based Single carrier DFT-s-
OFDM
Frame structure Unified and flexible across deployments
digital BF digital BF Digital/Analogue/hybrid Analogue/hybrid BF
BF
Multi antenna Unified feedback framework, eNB processing transparent to the UE, CSI feedback agnostic to eNB
processing
Mobility Decreasing with the increase of frequency band operation

13 © Nokia 2016 - confidential


Requirements and new radio physical layer technology components, cont.

New radio design should focus on:


• Both FDD and TDD should be supported.
• Multiple different OFDM numerologies should be supported for different deployment environments and
frequency bands.
• Multiple different TTI lengths should be supported for different latency and cell range targets.
• Support for flexible/dynamic TDD should be considered for configurations optimized for bands above 3
GHz.
• mMTC (IoT) point of optimization should be around or below 1 GHz.
• Single carrier waveforms should be considered for configurations optimized for very high bands, e.g. >
40 GHz, as well as for mMTC.
• LBT mechanism should be supported for Licenced-Assisted Access for unlicensed spectrum
- It still remains to be seen if 3GPP can/will address use of 5G in unlicensed spectrum without assistance from 5G (or LTE) in a standalone
way, as is being discussed for LTE with MulteFire outside 3GPP.

14 © Nokia 2016 - confidential


Spectrum

15 © Nokia 2016 - confidential


Executive Summary
Expectations and Observations
• In most of the regions, 5G will be commercially launched in year 2020 at spectrum
between 3-6 GHz (e.g. at 3.4-3.8 GHz) and deployments above 6GHz will follow some
years later, though some countries such as Korea, US and Japan likely to start with 28
GHz as well (Verizon also looking at 39 GHz)
• Currently, no spectrum currently in the range 4-24 GHz for 5G
• For below 6 GHz min 50-100 MHz per operator (based on LTE CA – not on 5G
performance) and for above 6GHz min 400[-1000/3000] MHz per operator is needed for
[extreme mobile broadband use case of] 5G
• 5G trial activities are ongoing in spectrum both below and above 6 GHz
• First commercial pre-5G deployment is expected in US at 28/39GHz for FWA
• First major mobile 5G trial is expected at Korean Olympics also at 28 GHz

16 © Nokia 2016 - confidential


Spectrum below 6 GHz for early 5G introduction
Spectrum under consideration for first commercial deployments
GHz 3.0 3.5 4.0 4.5 5.0 5.5 6.0
3.7 4.2
US ?

3.3 3.7 4.4 4.5 4.8 5.0


China 2017 (PoC) ? ?

3.4 3.6
Korea 2018

4.4 4.9 5.47 5.725


Japan 2016 (PoC) unlicensed

3.4 3.6 3.8


Europe UEFA
?
2020?

Based on customer discussion


Based on spectrum regulatory body discussion

Based on both spectrum regulatory body and customer discussion

17 © Nokia 2016 - confidential


5G SIGs (Special Interest Groups)

18 07/04/2016 © Nokia 2014


5G Special Interest Group landscape Verizon 5G SIG
Bi-lateral with Nokia & Alcatel-Lucent
Samsung, Qualcomm
5GIG Intel Ericsson, Verizon
Nokia, Samsung, Qualcomm, Intel, Cisco, LG
Ericsson, SKT, Verizon (NEW),
Qualcomm
Vodafone, Intel, Huawei, Samsung Nokia owner: Douglas White
CMCC, Orange, Intel, Sony, Objective: Develop VzW 5G
Docomo, Alcatel-Lucent FiOS specification, incluence
3GPP
Nokia owner: Ulrich Dropmann Nokia goal: Make Nokia the
Objective: Alignment before Verizon 5G vendor,
3GPP L1/L2 = KT specification
Nokia goal: Drive Nokia views
to other companies
5G TSA (Trial KT 5G SIG
3GPP
Specification Nokia, Samsung
Qualcomm, Ericsson
5GCG Alliance) KT, Intel
Nokia, Samsung, Qualcomm, Docomo, SKT, KT, Verizon
Ericsson, Huawei, CMCC Nokia, Ericsson, Qualcomm
Docomo Samsung, Intel Nokia owner: Antti Toskala
No plans Nokia owner: Antti Toskala
Objective: Develop 2018 5G
Trial specification
Nokia owner: Karri Ranta-aho
Objective: Alignment before
to make Objective: Develop global 5G
trial specification
Nokia goal: Make Nokia the
2018 Olympics 5G vendor
3GPP on requirements etc
Nokia goal: Drive Nokia views
input to Nokia goal: Make KT/Verizon
5G SIG spec basis for this &
to 19
other07/04/2016
companies © Nokia 2014 3GPP enable use for trials globally
KT SIG specification – pre-standard 5G for 2018 Olympics
L1 presentation with focus on L1 channels

20 © Nokia Solutions and Networks 2014


Overview of L1 principles
Parameter Value
Channel coding 802.11n based LDPC with added MCS levels + HARQ -> good
choise with reasonable implementation complexity
Carrier bandwidth 100 MHz (Effective 90 MHz with 1200 sub-carriers with 75 kHz
sub-carrier spacing), multiple carriers (max 8 = 800 MHz)
Multiple Access Cyclic Prefix - OFDM / TDD

Frame Structure 0.2 ms sub-frame

OFDM symbol

DL only DL-C DL DL DL DL DL

S-DL DL-C DL DL DL GP UL-C

S-UL DL-C GP UL UL UL UL-C


21 © Nokia Solutions and Networks 2014
0.2 ms
Downlink/Uplink OFDMA PHY One uplink slot Tslot

Carrier BW [MHz] 100 MHz


UL
N symb
Clock Rate [Msps/s] 153.6 OFDM symbols

Subcarrier spacing [kHz] 75 k  N RB N sc  1


UL RB

Symbol length [us] 13.3


Symbols /sub-frame 14
Resource block
Data (I)FFT block size 2048 UL
N symb  N scRB resource elements
Sub-frame length [us] 200
Cyclic Prefix [us] 0.94/1.04
Guard Period [us] One Symbol

 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

l0 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

Two Subframe type Radio frame is 10 ms, 50 subframes

Broadcast subframe
Common Control subframes Data subframes Data subframe index
index

DL SYNC, PBCH, UL RACH DL/UL Data 0, 25 Remaining indices

Data subframe OFDMA symbol index


configuration* 0 1 2 3 4 5 6 7 8 9 10 11 12 13
0 Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd
1 Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd GP Uc

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).

xPUSCH scehduling delay, ~1 subframe


UE processing time, ~1 subframe
xPDCCH

… … 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

• Selected technology components • Selected technology components


• Flexible TDD per subframe basis • DM-RS based dedicated control
• Bi-directional control in each and data
subframe • No always-on reference signals
• Same UL and DL structure for (CRS)
data • Only periodical sweeping subframes
• Beamformed common control • Support for UE side RF
plane beamforming training
• Sync, PBCH, Beam RS, PRACH • Support for UEs having hybrid transceiver
architecture
• Beam RS (BRS)
• Up to 8 antenna ports

26 © Nokia Solutions and Networks 2014


Sweeping subframe (beam based PSS/SSS/ESS/BRS/xPBCH)
One radio frame
• Sweeping broadcast subframe is defined per every 5ms for
downlink common control 5ms
- Cell search and detection, MIB acquisition, beam detection and measurements 14 sweeping blocks
• Sweeping sub-frame is composed by 14 sweeping blocks
• Each sweeping block is composed by
PSS/SSS/ESS/BRS/xPBCH
- PSS/SSS is for symbol and frame timing acquisition • Up to 8 antenna ports 
• One port transmission (sent via all RF beams) up to 8 RF beams per
block
- ESS is for symbol indication (sub-frame timing) BRS/ • Each RF beam carries
PBCH
- BRS is for BS beam detection, selection, measurements, wideband CSI PSS/SSS/eSSS/PBCH/B
eam specific RS
measurement
• One subframe allows BS


• 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

27 © Nokia Solutions and Networks 2014


PRACH subframes (beam based PRACH)

• Corresponding sweep for PRACH as for DL


common control can be configured in case BS
operates using hybrid architecture
• Associate PRACH resources to BS beams
• UE selects PRACH resource based on best DL
beam determined from BRS measurements on
periodical DL sweep
Frequency
• Enables UE to transmit PRACH preamble when
BS is receiving using appropriate RX beam 6 RBs #1
• Enables BS to learn the preferred BS beam for
Random Access Response message TX and for


subsequent control and data
#n

GP for RTD

CPrac CPrac … CPrac CPrac


TSEQ h
TSEQ TSEQ TSEQ
h h h

28 © Nokia Solutions and Networks 2014


PRACH subframe (200 us)
Front-loaded DMRS structure
Downlink overall

• 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

29 © Nokia Solutions and Networks 2014


Uplink overall

• 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)

30 © Nokia Solutions and Networks 2014


Downlink MIMO: Working Assumptions
Parameter Value

# antenna ports at eNB ≥2

#Max. co-scheduled users per TTI 4

Max. throughput per UE 5 Gps

Max. throughput per cell 20 Gps

Transceiver architecture @ eNB Hybrid

Transceiver architecture @ UE Hybrid

Max. rank per UE 2

31 © Nokia Solutions and Networks 2014


KT 5G SIG relationship to 3GPP & other operators

Will Nokia propose KT Answer: No, Nokia will propose more


5G SIG parameters optimized 5G design, such as channel
coding etc. We can’t compromize 5G
also to 3GPP? performance due 2018 Olympics timeline

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

Applications business models


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

Network service catalog


• Extreme Mobile Broadband
instance #3 Extreme • Basic Mobile Broadband
instance #2 Mobile instance #3
Broadband instance #2 • Massive MTC
CP
CP instance #1 UP • Critical MTC
Massive MTC UP
Critical MTC
instance #1 • Vehicle-to-Infrastructure
instance #1
• Vehicle-to-vehicle
• ...

35 07/04/2016
Nokia Confidential
Network Slicing - Architecture principles and considerations

•Allow a mobile operator to address •Network slicing should allow operators to


different use cases, services with different provide services by abstracting the
demands on network capabilities effectively. functionality offered by the network slice
•Each network slice can be based on through open APIs exposure to 3rd party
service provider.
different architectural principles. Network
UE can be served by multiple UP slices at a
slicing is an appropriate means to keep
given time. UE can be served by any CP/UP
networks based on different architectures
slice at any time. This may depend on factors
separated. such as UE capabilities, applications etc.
•Each Network slice has its own isolated set •Selection principles are critical for network
of resources, this means e.g. that deploying, slicing to be accomplished. Definition of a
maintaining and usage of a network slice multi-dimensional descriptor (e.g.
does not affect other network slices. application, service descriptor) configured in
•Network slice can also share resources the UE and reported to the network allows
between them. network Considerations
select a particular slice.
Architecture Principles Architecture Principles
36 07/04/2016
Nokia Confidential
Network slices for diverse use cases
Static use case is considered under Massive MTC umbrella

•Scalable Control plane •Highest reliability for •Optimized for Sporadic


•High-performance control plane and user Data Transmission of
user plane, potentially plane Short Data Burst
•Extreme Power Savings
distributed •User plane in edge
•Enhanced
•Mobility on demand, cloud for lowest latency monitoring/reporting (e.g.
including high-speed •Local switching location reporting)
mobility
Extreme Mobile
Critical MTC Massive MTC
Broadband

37 07/04/2016
Nokia Confidential
Multi-dimensional selection principle – use cases
Illustrations

Mobile broadband UE can request a service referred to as “session continuity” for a


certain application. In this case, network chooses functional entities necessary to
support mobility procedures, session management and other relevant functions such
as policy control, security.

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

•First phase in many cases to rely on dual


connectivity with LTE-anchor on lower band
SWI/SPL

• The more important, the higher 5G band


PDCP PDCP PDCP

RLC RLC RLC

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:

40 © Nokia 2016 - confidential

You might also like