Keysightintroducingrel 16 Ofthe 5 Gnrphysicallayer 1563984110481

Javier Campos 2018.10.
24
NR Physical Layer Architect / RAN1 Delegate
I N T R O D U C I N G R E L - 1 6 O F 5 G N R P H Y S I C A L L AY E R
• 3GPP RAN1 roadmap

• Rel-16 roadmap
• New study items
• New work items
• Enhancements to NR Rel-15
• MIMO enhancements
• URLLC enhancements
• New features in NR Rel-16
• V2X
• NOMA
• Unlicensed spectrum
• …
• Identify key challenges in NR Rel-16
© Keysight Technologies 2018 2

• Update on 3GPP RAN1 NR Roadmap

• Enhancements on MIMO
• Enhancements for NR URLLC
• Unlicensed Spectrum
• Non-Orthogonal Multiple Access
• NR V2X
• UE Power Saving and Positioning
• Summary

Enhancements on MIMO
Enhancements for NR URLLC
Unlicensed Spectrum
Non-Orthogonal Multiple Access
NR V2X
UE Power Saving and Positioning
Summary

U P D AT E O N 3 G P P R A N 1 N R R O A D M A P
• RAN1 workplan for Rel-16

• Timeframe
• RAN1 meetings
• Topics for study during Rel-16 time frame
• Ongoing study items
• New study items
• Features that will be part of Rel-16 specification
• Rel-15 enhancements
• Rel-16 new features

RAN RAN RAN RAN RAN RAN RAN RAN RAN RAN
# 79 # 80 # 81 # 82 # 83 # 84 # 85 # 86 # 87 # 88
2018 2019 2020

Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2
Rel-15 Rel-16
NSA Pack age
ASN.1 Appr oval
Rel-16 SI/WI Phase

Rel-15
Rel-15 Rel-16
Late Dr op
Freeze Fr eeze Freeze
Re-15
Rel-15 Rel-16
Late ASN.1
ASN.1 Dr op ASN.1

Meeting Dates Location

RAN1 #94 20 – 24 Aug 2018 Gothenburg (Sweden)
RANP #81 10 – 13 Sep 2018 Gold Coast (Australia)
RAN1 #94bis 8 – 12 Oct 2018 Chengdu (China)
RAN1 #95 12 – 16 Nov 2018 Spokane (USA)
RANP #82 10 – 13 Dec 2018 Sorrento (Italia)
RAN1 AH1901 21 – 25 Jan 2019 Taipei (Taiwan)
RAN1 #96 25 Feb – 1 Mar 2019 Athens (Greece)
RANP #83 18 – 21 Mar 2019 China
RAN1 #96bis 8 – 12 Apr 2019 China
RAN1 #97 13 – 17 May 2019 USA
RANP #84 3 – 6 Jun 2019 TBD
• Study items started in RAN1 #92 (February’18) meeting:

• NR-based access to unlicensed spectrum (RP-181339)
• Non-orthogonal multiple access for NR (RP-181403)
• Study on NR Vehicle-to-Everything (V2X) (RP-181429)
• NR to support non-terrestrial networks (completed)
• Study items started in RAN1 #92bis (April’18) meeting:
• Integrated Access and Backhaul (RP-172290)

Document Title Completion

RANP #83
RP-181399 NR Positioning Support March 2019
RANP #82
RP-181430 Remote Interference Management for NR December 2018
RANP #84
RP-181463 UE Power Saving in NR June 2019
RANP #85
RP-181435 NR Beyond 52.6 GHz September 2019
RANP #83
RP-181477 Study on Physical Layer Enhancements for NR URLLC March 2019

Study Item TR Document

NR Positioning Support TR 38.855
Remote Interference Management for NR TR 38.866
UE Power Saving in NR TR 38.840
NR Beyond 52.6 GHz TR 38.807
Study on Physical Layer Enhancements for NR URLLC TR 38.824
NR-based access to unlicensed spectrum TR 38.889
Non-orthogonal multiple access for NR TR 38.812
Study on NR Vehicle-to-Everything (V2X) TR 38.885
NR to support non-terrestrial networks TR 38.811, TR 38.821
Integrated Access and Backhaul TR 38.874
www.3gpp.org/DynaReport/38-series.htm

Document Title Completion

RANP #86
RP-181453 Enhancements on MIMO for NR December 2019
Cross Link Interference (CLI) Handling and RANP #83
RP-181431 March 2019
Remote Interference Management (RIM) for NR

Study Item
Work Item
2018 2019 2020 SID

Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 WID
NR NOMA NR NOMA RP-181403

NR Unlicensed NR Unlicensed RP-181339
NR V2X NR V2X RP-181480
NR MIMO RP-181453
UE Power
Saving
UE Power Saving RP-181463
UE Positioning UE Positioning RP-181399
eURLLC eURLLC RP-181477

• RAN1 workplan for Rel-16

• Timeframe
• RAN1 meetings
• Topics for study during Rel-16 time frame
• Ongoing study items
• New study items
• Features that will be part of Rel-16 specification
• Rel-16 new features

Update on 3GPP RAN1 NR Roadmap

Unlicensed Spectrum
NR V2X
Summary

ENHANCEMENTS ON MIMO
• Identify areas for enhancement in Rel-16

• PAPR with PUSCH/PUSCH DMRS
• PAPR with CSI-RS
• CSI-RS Type II enhancements

• Enhancements on MU-MIMO support

• Enhancements on multi-TRP/panel transmission
• Enhancements on multi-beam operation, primarily targeting FR2 operation:
• UL and/or DL transmit beam selection specified in Rel-15 to reduce latency and overhead
• Specify UL transmit beam selection for multi-panel operation that facilitates panel-specific beam
selection
• Specify a beam failure recovery for SCell based on the beam failure recovery specified in Rel-15
• Specify CSI-RS and DMRS enhancement for PAPR reduction (no change on Rel-
15 RE mapping)

• There is an issue with high PAPR for DMRS

transmission relative to PDSCH/PUSCH data
symbols for some DMRS configurations
• 1.8- 2.53 dB for rank 2 transmission
• 2dB ~ 4dB for rank 4 transmission
• Especially important to improve UL coverage
• Lower PAPR means higher output power by the UE, improving
UL coverage
• Enhancements for PDSCH DMRS and PUSCH

DMRS are specified in Rel-16 to reduce the PAPR to
similar level as for data symbols
• The network can indicate to the UE whether Rel-15 or
Rel-16 DMRS is used

• For PDSCH/PUSCH DMRS for CP-OFDM

• DMRS enhancements are specified in Rel-16 to reduce the PAPR to the same level as for data symbols for
all port combinations given
• Each CDM group can be configured with different cinit
• The following solution categories are precluded:
• Modification of OCC
• Modification to PN sequence generation
• Modifications of the DMRS resource assignment
• For PUSCH/PUCCH DMRS for DFT-s-OFDM

• New DMRS sequences are specified in Rel-16 to reduce the PAPR to the same level as for data symbols

ENHANCEMENTS ON MIMO Under discussion
• CSI-RS report in Rel-15:

• CSI type I:
• Report is codebook and PMI based with normal spatial resolution
• CSI type II:
• Enhanced feedback with higher spatial resolution (codebook-based)
• Limited to rank 1 and 2
• Enhancements for Rel-16:

• Type II overhead reduction for rank 1-2
• Type II rank > 2 extension

• Identify areas for enhancement in Rel-16

• PAPR with PUSCH/PUSCH DMRS
• PAPR with CSI-RS
• CSI-RS Type II enhancements

Unlicensed Spectrum
NR V2X
Summary

ENHANCEMENTS FOR NR URLLC
• Why URLLC needs to be enhanced?

• Missed features from Rel-15
• New Rel-16 use cases
• What will be enhanced in URLLC?
• Traffic multiplexing
• Grant-free transmission in UL

• In Rel-15 the basic support for URLLC was introduced with:

• Slot and time/frequency assignment structures for low latency
• Methods for improved reliability
• Rel-15 enabled use case improvements
• Such as AR/VR (i.e. entertainment industry)
• New Rel-16 use cases with higher requirements
• Factory automation
• Motion control
• Transport industry
• Remote driving
• Electrical power distribution
• Power distribution grid fault and outage management
• Differential protection

# of UEs
Use Case Reliability Latency Traffic Model Description
(per cell)
Transport Industry 99.999% 5ms 30 Periodic Remote driving
Power distribution
99.9999% 5ms 8 80 bytes Grid fault
Power Distribution Outage management
250 bytes
99.999% 15ms 8 Differential protection
Periodic
20 bytes
Factory automation 99.9999% 2ms 40 Motion control
Periodic
Rel-15 use case
99.999% 1ms 20 256 bytes N/A
(e.g. AR/VR)

• Investigate enhancements to URLLC (i.e. Ultra Reliable Low Latency

Communications)
• FR1 and FR2
• TDD and FDD
• The study is focusing on the following items:
• Higher reliability (up to 10-6 level)
• Higher availability
• Short latency in the order of 0.5 to 1 ms
• Depending on the use cases: factory automation, transport industry and electrical power distribution

• PDCCH enhancements
• Compact DCI, PDCCH repetition, increased PDCCH monitoring capability
• UCI enhancements
• Enhanced HARQ feedback methods, CSI feedback enhancements
• PUSCH Enhancements
• Mini-slot level hopping & retransmission/repetition enhancements
• Enhanced multiplexing considering different latency and reliability requirements
• Enhanced UL grant-free transmissions

UL grant for
eMBB PUSCH
UL grant for URLCC PUSCH
• UL pre-emption indication + higher TPC command
is not defined in Rel-15 slot
• Dynamic multiplexing is still
DL
supported based on the
existing power control
• Power control can help
URLLC boost transmit power URLLC with power boost
in case of a preemption
UL
SR for URLLC eMBB PUSCH
URLLC PUSCH
UL grant for
eMBB PUSCH
UL grant for URLCC PUSCH
• Upon a received scheduling + higher TPC command
request from a URLLC UE: slot
• gNB may decide to multiplex URLLC
DL
transmission with another eMBB
transmission on shared resources
• UL power control enhancements
URLLC with power boost
are going to be studied
UL
SR for URLLC eMBB PUSCH
URLLC PUSCH

ENHANCEMENTS FOR NR URLLC Under discussion
UL grant for
eMBB PUSCH UL pre-emption indication
• Upon a received scheduling UL grant for URLLC PUSCH
request from a URLLC UE: slot
• gNB may decide to multiplex URLLC DL
transmission on shared resources
• An UL PI can be transmitted by
gNB after the URLLC grant is
decoded to indicate the preempted
resources/symbols to the eMBB UE UL
Scheduled eMBB
SR for URLLC PUSCH
URLLC PUSCH
Cancelled eMBB
transmission
Original UL grant for eMBB PUSCH
• Upon a received scheduling UL grant for URLLC PUSCH
request from a URLLC UE:
New UL grant for eMBB PUSCH
• gNB may decide to multiplex URLLC slot
transmission on shared resources DL
• UL eMBB transmission can be re-

scheduled to other preemption-free
resources after the URLLC
transmission is scheduled
UL
Scheduled eMBB
SR for URLLC PUSCH
URLLC PUSCH
• Rel-15 behavior
• When a UE is configured with repetitions:
• Same symbol allocation applies across the consecutive slots for both grant-based and grant-free PUSCH transmissions
• The waiting time (frame alignment) for grant-free transmission can be up to 1 slot
Data arrives
Slot #n Slot #n+1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13
Rel-15 repetition across slots (repetition factor K = 4)
Slot
Rep #1 Rep #2
Repetition for non-slot PUSCH in Rel-15 One repetition per slot

• Rel-16 enhancements Slot #n

• Consider mini-slot level repetition for grant-free UL
0 1 2 3 4 5 6 7 8 9 10 11 12 13
transmission
• Benefits:
• Lower processing time for gNB receiver
• Precoder/QCL(or SRI)-cycling across repetitions
Rep #1 Rep #3
Rep #2 Rep #4
Mini-Slot Level Frequency Hopping

• Consider mini-slot level repetition for grant-free UL
transmission
Rel-15 repetition across slots (repetition factor K = 4)
• Benefits: Slot
• Precoder/QCL(or SRI)-cycling across repetitions One repetition per slot
Rel-16 eURLLC enabled PUSCH repetition (repetition factor K = 4)
Slot
More than one repetition per slot

Rel-16 eURLLC enabled PUSCH repetition (repetition factor K = 4)
Slot
All repetitions within a slot
PUSCH Repetition Enhancements

• Rel-16 enhancements Repetition Repetition

• Consider mini-slot level repetition for grant-free UL #1 #2
transmission
• Benefits:
• Precoder/QCL(or SRI)-cycling across repetitions
Rep #1 Rep #2
TRP #1 TRP #2
PUSCH Receptions with precoder/QCL-cycling

• Why URLLC needs to be enhanced?

• Missed features from Rel-15
• New Rel-16 use cases
• What will be enhanced in URLLC?
• Traffic multiplexing
• Grant-free transmission in UL


NR V2X
Summary

UNLICENSED SPECTRUM
• Current status of discussions about unlicensed spectrum

• Unlicensed spectrum concepts
• LBT protocol
• Regulatory constraints
• NR-U procedures
• Channel access
• Initial access and mobility for NR-U
• Wide bandwidth operation

UNLICENSED SPECTRUM
• Agreements on evaluation assumptions also including deployment

scenarios, co-existence with other networks & network topologies, etc.
• Study the additional functionality needed beyond the specifications for
operation in licensed spectrum in the following deployment scenarios:
• Carrier aggregation between licensed band NR (PCell) and NR-U
(SCell)
• NR-U SCell may have both DL and UL or DL-only
• Dual connectivity between licensed band LTE (PCell) and NR-U
(PSCell)
• Stand-alone NR-U
UNLICENSED SPECTRUM
Idle State
• CCA - Clear Channel Assessment No

No
Initial CCA
• The evaluation of presence/absence of other signals Needs to Tx?
Yes
Another Tx
needed?
• LBT - Listen Before Talk Yes Yes
• The mechanism for which an equipment applies CCA Has the channel
been idle for the
Yes
Transmit?
No
before using the channel initial CCA period?
No
Generate a
random counter Update the
Nϵ[0, q-1] contention
window q
No
Has the channel
been idle for the
eCCA defer period? Input (e.g. ACK/
Extended CCA
NACK)
Yes
Yes
N=0?
No
Sense the medium for
N=N-1 one eCCA slot
duration T
No Yes
Busy?
UNLICENSED SPECTRUM
• Occupied bandwidth shall be between

First RB Last RB
80% and 100% of the declared bandwidth
• The occupied channel bandwidth is the ...
bandwidth containing 99 % of the power of the
signal
Between 80% and 100% of System Bandwidth
• Try to make the first RB and the last RB
separated far enough to cover 80% of the system
bandwidth
• Maximum PSD per MHz PSD (dBm/MHz)
• Output power per any MHz cannot exceed the
1 MHz
...
limit specified by the regulation
• Try to occupy as many MHz as possible either in
Best possible output power
RB or in subcarrier to gain a best output power
UNLICENSED SPECTRUM
• These two regulatory constraints are overcome with an interlace based

waveform
• Each interlace includes equally separated RBs
• One or more interlaces can be scheduled to one UE
L PRBs
RB 2L+1
RB 2L+2
RB 3L+1
RB 3L+2
RB L+1
RB L+2
RB 2L
RB 3L
RB 0
RB 1
RB 2
RB L
... ... ...
Interlace #0
Interlace #1
Interlace #2
UNLICENSED SPECTRUM
• Modifications to initial access procedures considering limitations on access to the channel

based on LBT
• Develop techniques to handle reduced SS/PBCH block and RMSI transmission opportunities due
to LBT failure
• Enhancement to 4-step RACH
• Mechanisms to handle reduced Message 1/2/3/4 transmission opportunities due to LBT failure
• 2-step RACH potentially has benefit for channel access
• Potential modifications to RLM/RRM procedures due to reduced transmission
opportunities for DL signals and channels due to LBT failure
• Modifications to paging procedures due to reduced transmission opportunities for paging
due to LBT failure

UNLICENSED SPECTRUM
• Channel access cannot be done in bandwidths larger than 20 MHz due to

regulatory constraints
• How to transmit in larger bandwidths?
• Activate/transmit the whole or part of a BWP depending on the outcome of LBT procedure
• Option 1a: Multiple BWPs configured, multiple BWPs activated, transmission of PDSCH on one or more
BWPs
• Option 1b: Multiple BWPs configured, multiple BWPs activated, transmission of PDSCH on single BWP
• Option 2: Multiple BWPs can be configured, single BWP activated, gNB transmits PDSCH on a single
BWP if CCA is successful at gNB for the whole BWP
• Option 3: Multiple BWPs can be configured, single BWP activated, gNB transmits PDSCH on parts or
whole of single BWP where CCA is successful at gNB

LBT Successful
LBT Failure
UNLICENSED SPECTRUM
• Option 1a: Multiple BWPs configured, multiple BWPs activated, transmission of PDSCH on one or
more BWPs
• Option 1b: Multiple BWPs configured, multiple BWPs activated, transmission of PDSCH on single
BWP
20 MHz
20 MHz
BWP 1
BWP 1
Activated Activated Activated
BWP 1 BWP 1 BWP 1
20 MHz
20 MHz
BWP 3
Activated
BWP 3
20 MHz
20 MHz
BWP 2
BWP 2
Activated
BWP 2
20 MHz
20 MHz
Option 1a © Keysight Technologies 2018 Option 1b 44
LBT Successful
LBT Failure
UNLICENSED SPECTRUM
more BWPs
BWP
20 MHz
20 MHz
BWP 1
BWP 1
BWP 1 BWP 1 BWP 1
20 MHz
20 MHz
BWP 3
Activated
BWP 3
20 MHz
20 MHz
BWP 2
BWP 2
Activated
BWP 2
20 MHz
20 MHz
LBT Successful
LBT Failure
UNLICENSED SPECTRUM
more BWPs
BWP
20 MHz
20 MHz
BWP 1
BWP 1
BWP 1 BWP 1 BWP 1
20 MHz
20 MHz
BWP 3
Activated
BWP 3
20 MHz
20 MHz
BWP 2
BWP 2
Activated
BWP 2
20 MHz
20 MHz

LBT Successful
LBT Failure
UNLICENSED SPECTRUM
• Option 2: Multiple BWPs can be configured, single BWP activated, gNB transmits PDSCH on a
single BWP if CCA is successful at gNB for the whole BWP
• Option 3: Multiple BWPs can be configured, single BWP activated, gNB transmits PDSCH on
parts or whole of single BWP where CCA is successful at gNB
20 MHz
20 MHz
20 MHz
20 MHz
Activated
BWP 1
BWP 1
BWP 1
Activated Activated
BWP 1 BWP 1
20 MHz
20 MHz
20 MHz
20 MHz

Option 2 Option 3
LBT Successful
LBT Failure
UNLICENSED SPECTRUM
20 MHz
20 MHz
20 MHz
20 MHz
Activated
BWP 1
BWP 1
BWP 1
Activated Activated
BWP 1 BWP 1
20 MHz
20 MHz
20 MHz
20 MHz

Option 2 Option 3
LBT Successful
LBT Failure
UNLICENSED SPECTRUM
20 MHz
20 MHz
20 MHz
20 MHz
Activated
BWP 1
BWP 1
BWP 1
Activated Activated
BWP 1 BWP 1
20 MHz
20 MHz
20 MHz
20 MHz
Option 2 Option 3
UNLICENSED SPECTRUM
• Current status of discussions about unlicensed spectrum

• Unlicensed spectrum concepts
• LBT protocol
• Regulatory constraints
• NR-U procedures
• Channel access
• Initial access and mobility for NR-U
• Wide bandwidth operation

Unlicensed Spectrum
NR V2X
Summary

N O N - O R T H O G O N A L M U LT I P L E A C C E S S
• Current status of discussions about NOMA

• Scope of NOMA study item
• NOMA concepts
• NOMA transmitter
• NOMA receiver
• NOMA frame structure
• NOMA use cases

Power
• Orthogonal Multiple Access
• Resource assignment is orthogonal between users
User #1
User #2
User #3
User #5
User #4
• CDMA
• All power assigned to users
• Each user is assigned different codes
• OFDMA
• All power assigned to users Code
CDMA
• Each user is assigned different frequency resources
Power
User #1
User #2
User #3
User #5
User #4
Frequency
OFDMA
• Non-Orthogonal Multiple Access

• Resource assignment is not orthogonal between
users
Power
• Users transmit on the same time and frequency
resources
User #5
User #1
• Power is shared between users
User #7
User #3
• Superposition and power allocation
User #6
User #2
User #8
User #9
User #4
Frequency

• Discussed both link-level and system level simulation assumptions

• Discussions on aspects such as transmitter/receiver/procedure for NOMA
• Both grant-based and grant-free NOMA to be studied:
• Grant-based NOMA is supported at least for eMBB scenario
• Grant-free NOMA is supported at least for mMTC scenario
• Grant-free NOMA can be considered for eMBB scenario
• NOMA in UL is an attractive feature for mMTC applications
• Improves system load capability
After December’18 meeting it will be decided whether it will continue with a WI or not

• NOMA is mainly used in UL

• When network operates in grant-based mode
• Transmission schemes proposed for NOMA can be applied to MU-MIMO as well
• The gain of NOMA over MU-MIMO in spectral efficiency is questionable
• When the network operates in grant-free mode and the UL access is
contention-free
• The gain of NOMA over MU-MIMO in spectral efficiency is questionable
• The most significant gain of NOMA over MU-MIMO can be achieved in the
following scenarios:
• Contention-based, grant-free transmission
• Small data transmission from RRC_INACTIVE state

Small power allocated to cell-center UE
Power
Large power allocated to cell-edge UE
Frequency
Cell Edge UE
Cell Center UE

Small power allocated to cell-center UE
Power
Large power allocated to cell-edge UE
Frequency
Interference
Cell Edge UE
from cell-
center UE
Power
Cell-edge UE
signal decoding
(without SIC)
Cell Center UE
Frequency
Cell-center UE
Power
Power
signal decoding
SIC of cell-
edge UE signal
Frequency Frequency
Successive Interference Cancellation

Power
UE2
High reception SINR Low reception SINR

UE1
Frequency
SIC of UE2 UE1 Signal UE2 Signal

Transmission Decoding Decoding
y1 = h1 · (x1 + x2) + w1
y1
UE2 Signal
Decoding
x2
h1· x2
UE2 Signal
Reconstruction
UE1 Signal
x1
- Decoding

Transmitter side data processing for NOMA can be based on one or more of the following aspects:
NOMA Specific Blocks
Bit-Level Symbol-Level
Channel Resource
Scrambler/ Modulator Spreading/Scrambling/
Encoder mapping
Interleaver Interleaving
• Bit-Level Processing
• Goal is to randomize the inter-user interference
• Can be either interleaving or scrambling
• Modulator
• Same modulator as NR can be used
• Joint modulation and spreading can be used to further reduce inter-user interference
• Symbol-Level Processing
• Some NOMA schemes use low cross-correlation spreading sequences
• Several receiver architectures are being considered

• MMSE-IRC
• MMSE-Hard IC
• ESE detector and soft IC
• EPA detector and soft IC
• These receiver architectures are being evaluated currently at RAN1
• Performance
• Complexity

• Typical NOMA receiver

• The interference cancellation can be hard, soft, or hybrid
• The interference cancellation block may or may not be used
Received signal
Detector Decoder
Interference
Cancellation (IC)

• MMSE-IRC Received signal MMSE User 1

Decoder
• Baseline receiver which has been widely used in the legacy Detector
gNB implementation
• Intra and inter-cell interference are suppressed via MMSE
User 2
detection MMSE
Detector
Decoder
• No interference cancellation is performed
. . .
. . .
. . .
MMSE User N
Decoder
Detector

• MMSE-hard IC Received signal MMSE

Decoder
User 1
• Adding interference cancellation Detector
• The interference cancellation is

based on the hard output of the
Spreading Modulator Re-Encoding
decoder
SINR MMSE User 2
IC Detector
Decoder
Sorting
Spreading Modulator Re-Encoding
SINR MMSE User 3

IC Detector
Decoder
Sorting
. . .
• NOMA transmission can be:

• Synchronous (No time offset)
• Asynchronous (Time offset)
• Frame structure consisting of preamble and data
• Capable of supporting the grant-free based UL transmission
• Can provide more robust gNB reception and HARQ support as the gNB would be made aware of the UE
identity necessary for data packet demodulation before the data is actually transmitted
PREAMBLE DATA

• Current status of discussions about NOMA

• Scope of NOMA study item
• NOMA concepts
• NOMA transmitter
• NOMA receiver
• NOMA frame structure
• NOMA use cases

Unlicensed Spectrum

Summary

NR V2X
• NR V2X use cases

• NR V2X physical layer
• Sidelink physical layer
• Definition
• Physical and transport channels
• Sidelink procedures
• Synchronization
• Resource allocation
• Discovery
• UE grouping

NR V2X
• Software Update
• Real-Time Situational Awareness & High-Definition Map
• Vulnerable Road User (VRU)
• Platooning
• Cooperative Maneuvers of Autonomous Vehicles for Emergency Situations
• Remote Automated Driving Cancellation (RADC)
• Automated Intersection Crossing
• Autonomous Vehicles Parking by Remote Driving
• High Definition Sensor Sharing
NR V2X
• Software Update

• Platooning

NR V2X
• Software Update

• Platooning

NR V2X
• Software Update
• Platooning

NR V2X
• Software Update
• Platooning


NR V2X
• Software Update
• Platooning


NR V2X
• Software Update
• Platooning


NR V2X
• Software Update
• Platooning

NR V2X
• The access link (i.e. DL/UL) is used

for communication between gNB and
UEs
• The sidelink is used for
communication between UEs
• This is the link used for V2X in LTE and
NR
Sidelink

NR V2X
• NR V2X will support: Unicast, groupcast and broadcast

• LTE V2X only supported broadcast communication
• For unicast: HARQ feedback and HARQ combining are supported
• For groupcast: HARQ feedback and HARQ combining are supported
• NR V2X is expected to work in licensed and unlicensed bands
• NR-V2X sidelink should be able to operate:
• Out of coverage
• Partial coverage
• In-coverage

NR V2X Under discussion
Node-S Node-S
Node-S Local Manager Local Manager
Node-S Local Manager
Local Manager
DCI-R (G-RNTI) DCI-R (B-RNTI)

DCI-R (U-RNTI)
Data Data
Data Data
Node-R(s) Node-T Node-R(s) Node-T

Node-R Node-T Node-R Node-T
Three parties Unicast Groupcast Broadcast

communication
diagram
The function of Node-S is to coordinate the resource usage within a local area

NR V2X
• The following channels are at least defined for NR V2X:

• PSSCH
• PSCCH
• PSCCH at least carries information necessary to decode PSSCH
• NR V2X sidelink synchronization includes at least the following:

• S-SSB: NR SSB structure as the starting point
• Sidelink PSS (S-PSS)
• Sidelink SSS (S-SSS)
• PSBCH
• Periodic transmission of S-SSB is supported
• Sidelink SSB should be designed to be distinguishable from NR SSB
• Different frequency position and different relative time-positions

NR V2X
Option 1a Option 1b
• Multiplexing of PSCCH and the associated
PSCCH
PSSCH:
PSCCH
• Option 1: Non-overlapping time resources PSSCH PSSCH
• Option 1A: The frequency resources used by the two
channels are the same
• Option 1B: The frequency resources used by the two
channels can be different
• Option 2: Non-overlapping frequency resources in
the all the time resources used for transmission Option 2 Option 3
(i.e. the time resources used by the two channels PSCCH
are the same)
• Option 3: A part using overlapping time resources Under discussion
PSCCH
Frequency
PSSCH
in non-overlapping frequency resources
PSSCH
Time

NR V2X
• Sidelink control information (SCI)

• SCI is transmitted in PSCCH
• SCI includes at least one SCI format which includes the information necessary to decode the
corresponding PSSCH
• Sidelink feedback control information (SFCI)
• SFCI includes at least one SFCI format which includes HARQ-ACK for the corresponding
PSSCH
• Under study:
• How to include other feedback information (if supported) in SFCI
• How to convey SFCI on sidelink in PSCCH, and/or PSSCH, and/or a new physical sidelink channel

NR V2X
• NR sidelink supports the SCSs supported by Uu:

• FR1: 15, 30, 60 kHz
• FR2: 60, 120 kHz
• Still to be discussed:
• CP length
• Synchronization signal subcarrier spacing
• UE is not required to receive sidelink transmissions using different SCSs simultaneously in a given
carrier
• Still to be discussed if this applies to sidelink synchronization signals/channels
• UE is not required to transmit sidelink transmissions using different SCSs simultaneously in a
given carrier
• Still to be discussed if this applies to sidelink synchronization signals/channels

NR V2X
•Sidelink synchronization sources:

• GNSS
• eNB (i.e. network-based)
• gNB (i.e. network-based)
• NR UE (i.e. device-based)

NR V2X
•At least two sidelink resource allocation modes are defined

for NR-V2X sidelink communication:
• Mode 1: Base station schedules sidelink resource(s) to be used by
UE for sidelink transmission(s)
• Mode 2: UE determines (i.e. base station does not schedule) sidelink
transmission resource(s) within sidelink resources configured by
base station/network or pre-configured sidelink resources
• UE autonomously selects sidelink resource for transmission
• UE assists sidelink resource selection for other UE(s) LTE Uu can provide the
• UE is configured with NR configured grant (type-1 like) for sidelink transmission semi-static configuration

• All vehicles always broadcast basic information

• Safety messages, location and identity of V2X UEs
• Each vehicle’s information is known to all other vehicles within the range
• The UE capability of a specific vehicle supporting a specific advanced
V2X service is unknown to all other vehicles within the range
• It is necessary to define a discovery procedure for the source UE to discover
the target UE for the establishment of a V2X link

UE group 1 UE group 2 UE group 3
• UEs can decide whether to form a UE group with Member Member Member
proximity UEs Header Header Header
• UEs can volunteer to be a header or a member of a Orthogonal resource set configuration of proximity UE groups
UE group
• When a UE volunteers to be a member-UE:
• It should discover a header-UE in its proximity and try to be
associated with the header-UE UE group 1
UE performs sensing to judge whether

to join the UE group
UE group in proximity Member
Header
UE group 2
Member
UE to be a new header-UE based on
judgement that there is no UE-group in
proximity
Header
New header
UE volunteers to be a member UE UE volunteers to be a header-UE

• In FR2, transmission link is sensitive to blockage

• Sensing based resource allocation may not work well
• Blockage incur hidden node
• Critical in FR2
V1
• V4 cannot sense transmission from V1

due to blockage from V2 and V3
V2 • V1 is hidden to V4
V3
V4

NR V2X
• The vehicle UE is typically equipped with half-duplex systems

• Once UE is in the transmission mode, it is not able to make the reception
• This could significantly reduce the packet reception ratio (PRR)
Packet 1
Packet 2
V4
V8
V3
V6
V1
V7
V2 V5

• Waveform • Modulation
• Candidates: • RE mapping and rate-
• CP-OFDM, DFT-s-OFDM
matching
• CP length
• Scrambling
• RS design
• Channel coding
• Data: LDPC as starting point
• Control: Polar codes as starting
point

NR V2X
• Forward/backward compatibility:
• Allow LTE network to allocate NR V2X sidelink
• NR network should also be able to allocate LTE V2X sidelink
• Coexistence solutions:
• TDM of LTE V2X and NR V2X sidelink transmissions
• Prevent overlapping or simultaneous NR and LTE V2X sidelink transmissions
• FDM of LTE V2X and NR V2X sidelink transmissions
• Simultaneous transmissions of NR and LTE V2X sidelink transmissions

NR V2X
• NR V2X use cases

• NR V2X physical layer
• Sidelink physical layer
• Definition
• Physical and transport channels
• Sidelink procedures
• Synchronization
• Resource allocation
• Discovery
• UE grouping

Unlicensed Spectrum
NR V2X
Summary

U E P O W E R S AV I N G A N D P O S I T I O N I N G
• Identify proposed techniques to reduce UE power consumption

• Go to sleep signal
• Time/frequency domain techniques
• UE processing time
• RRM measurements
• Identify objectives of UE positioning

• Identify techniques for UE power saving study with focus in RRC_CONNECTED

mode
• Network and/or UE assistance information
• Reducing PDCCH monitoring, taking into account current DRX scheme
• Study the power saving signal/channel/procedure for triggering adaptation of UE power
consumption characteristics
• Study the UE power consumption reduction in RRM measurements in
synchronous and asynchronous network deployment

• The following power saving techniques are going to be studied:

• DRX configuration
• Frequency domain
• BWP – enhancement of dynamic switching from Rel-15
• CA/DC
• Timeline relaxing of UE processing
• Reduce PDCCH Monitoring
• Reduced number of PDCCH processing
• Network assistance

• Relaxing RRM measurement for UE power saving:

• Number of RRM measurements in time domain for serving cell and neighbor
cells
• Number of measured frequencies for neighbor cells
• Measurement reports

• Study the following for triggering adaptation of UE power consumption

characteristics:
• Existing signal/channel based approach
• Signals based on PDCCH channel
• Signals based on RS
• MAC signaling
• RRC signaling
• New power saving signal/channel

U E P O W E R S AV I N G A N D P O S I T I O N I N G Under discussion
• A power saving signal helps reducing PDCCH monitoring power consumption

• Power saving signal is used to trigger UE whether to wake up in DRX cycle
• Power saving signal is also used to indicate if UE would have DL data to receive at the upcoming
DRX ON period
• UE will monitor the power saving signal before the DRX ON period
• This would reduce the UE power consumption by not waking up and decoding the PDCCH during the whole
DRX ON period Grant & PDSCH processing
Power Consumption
Control information for sleep
UE can potentially sleep for K

slots
Time
• Study requirements, evaluation scenarios/methodologies to enable positioning in

regulatory and commercial use cases
• Identify requirements such as accuracy, latency, capacity, coverage, etc.
• Define evaluation scenarios for indoor and outdoor
• Study and evaluate potential solutions of positioning technologies based on the
requirements, evaluation scenarios/methodologies
• Include at least NR-based RAT dependent positioning to operate in both FR1 and FR2
• Downlink based solutions
• Downlink and uplink based solutions
• Uplink based solutions
• Support higher accuracy location capability of 0.5m
• Support location estimation of UE in 500ms

• Identify proposed techniques to reduce UE power consumption

• Go to sleep signal
• Time/frequency domain techniques
• RRM measurements
• Identify objectives of UE positioning

Unlicensed Spectrum
NR V2X

• Rel-16 specification will be finished • New features introduced:
by Q4’19 • Positioning
• Very early stage of Rel-16 work in 3GPP • Power saving mechanisms
(only two meetings) • NOMA
• Unlicensed spectrum access
• Enhancements introduced to Rel-15:
• MIMO • New air interface
• URLLC • V2X/Sidelink
• V2X is getting a lot of attention in RAN1
New and enhanced features need to be backward compatible with Rel-15

• Enhancements on MIMO for NR
• Remote Interference Management for NR
• UE Power Saving in NR
eMBB
• NR Beyond 52.6 GHz
• Integrated Access and Backhaul
• NR-based access to unlicensed spectrum
• Non-orthogonal multiple access for NR
mMTC
• NR Positioning Support
• Study on NR Vehicle-to-Everything (V2X)
• Study on Physical Layer Enhancements for NR URLLC

• 3GPP RAN1 roadmap

• Rel-16 roadmap
• New study items
• New work items
• Enhancements to NR Rel-15
• MIMO enhancements
• URLLC enhancements
• New features in NR Rel-16
• V2X
• NOMA
• Unlicensed spectrum
• …
• Identify key challenges in NR Rel-16

• Coexistence between Rel-15 Uu air interface and NR V2X
• Interference management
• Synchronization
• Resource assignment
• Coexistence between NR V2X and LTE
• Synchronization
• NOMA
• Impact of NOMA traffic on Rel-15 traffic
• Receiver complexity
• Network management of resources
• Grant-free asynchronous transmission
• Guaranteeing backward compatibility of Rel-16 enhanced features

• 3GPP Webpage
• www.3gpp.org
• 3GPP RAN1 Documents
• www.3gpp.org/ftp/tsg_ran/WG1_RL1
• 3GPP NR Technical Specifications and Reports
• www.3gpp.org/DynaReport/38-series.htm
• The 3G4G Blog
• blog.3g4g.co.uk
• Keysight 5G Products and Solutions
• www.keysight.com/find/5G

Keysightintroducingrel 16 Ofthe 5 Gnrphysicallayer 1563984110481

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Keysightintroducingrel 16 Ofthe 5 Gnrphysicallayer 1563984110481

Uploaded by

Copyright:

Available Formats

Javier Campos 2018.10.

• 3GPP RAN1 roadmap

© Keysight Technologies 2018 2

• Update on 3GPP RAN1 NR Roadmap

© Keysight Technologies 2018 3

© Keysight Technologies 2018 4

• RAN1 workplan for Rel-16

© Keysight Technologies 2018 5

2018 2019 2020

Rel-16 SI/WI Phase

© Keysight Technologies 2018 6

Meeting Dates Location

• Study items started in RAN1 #92 (February’18) meeting:

© Keysight Technologies 2018 8

Document Title Completion

© Keysight Technologies 2018 9

Study Item TR Document

© Keysight Technologies 2018 10

Document Title Completion

© Keysight Technologies 2018 11

2018 2019 2020 SID

NR NOMA NR NOMA RP-181403

© Keysight Technologies 2018 12

• RAN1 workplan for Rel-16

© Keysight Technologies 2018 13

Enhancements for NR URLLC

© Keysight Technologies 2018 14

• Identify areas for enhancement in Rel-16

© Keysight Technologies 2018 15

• Enhancements on MU-MIMO support

© Keysight Technologies 2018 16

• There is an issue with high PAPR for DMRS

• Enhancements for PDSCH DMRS and PUSCH

© Keysight Technologies 2018 17

• For PDSCH/PUSCH DMRS for CP-OFDM

• For PUSCH/PUCCH DMRS for DFT-s-OFDM

© Keysight Technologies 2018 18

• CSI-RS report in Rel-15:

• Enhancements for Rel-16:

© Keysight Technologies 2018 19

• Identify areas for enhancement in Rel-16

© Keysight Technologies 2018 20

© Keysight Technologies 2018 21

• Why URLLC needs to be enhanced?

© Keysight Technologies 2018 22

• In Rel-15 the basic support for URLLC was introduced with:

© Keysight Technologies 2018 23

© Keysight Technologies 2018 24

• Investigate enhancements to URLLC (i.e. Ultra Reliable Low Latency

© Keysight Technologies 2018 25

© Keysight Technologies 2018 26

SR for URLLC eMBB PUSCH

SR for URLLC eMBB PUSCH

© Keysight Technologies 2018 28

• UL eMBB transmission can be re-

Repetition for non-slot PUSCH in Rel-15 One repetition per slot

© Keysight Technologies 2018 31

• Rel-16 enhancements Slot #n

Mini-Slot Level Frequency Hopping

More than one repetition per slot

All repetitions within a slot

PUSCH Repetition Enhancements

© Keysight Technologies 2018 33