Scribd
Upload
242 views4 pages

R2-1703278 PDCP Count Rollover in Option 3

This document discusses how to handle PDCP count rollover in NR-PDCP, especially for SCG split bearers in 5G NR-LTE dual connectivity. It proposes using intra-cell handover when rollover occurs in NR-PDCP for SCG split bearers since resources are used in both the master and secondary nodes. For SCG bearers, it is the secondary node's decision to trigger either intra-cell handover or SCG change based on whether the master node resources are utilized. The document puts forth these proposals and observations for discussion at the 3GPP RAN meeting.

Uploaded by

Terry Bacchin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
242 views4 pages

R2-1703278 PDCP Count Rollover in Option 3

This document discusses how to handle PDCP count rollover in NR-PDCP, especially for SCG split bearers in 5G NR-LTE dual connectivity. It proposes using intra-cell handover when rollover occurs in NR-PDCP for SCG split bearers since resources are used in both the master and secondary nodes. For SCG bearers, it is the secondary node's decision to trigger either intra-cell handover or SCG change based on whether the master node resources are utilized. The document puts forth these proposals and observations for discussion at the 3GPP RAN meeting.

Uploaded by

Terry Bacchin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

3GPP TSG RAN WG2 Meeting #97bis R2-1703278

Spokane, USA, 3 – 7th April 2017

Agenda Item: 10.2.2.4


Source: Sony
Title: PDCP count rollover in Option 3/3a/3x
Document for: Discussion

1.Introduction
TR 38.804 captured the following agreements for security:
Security key refresh is not performed at every mobility procedure (i.e. handover), at least for the case of mobility where
the PDCP anchor point is not changed.

NOTE: It is to be confirmed by SA3 considering whether it has any implication on the inputs for key derivation,
e.g. PCI.

For DC between LTE and NR where the master RAT is LTE, S-KeNB is derived from KeNB of the master node.

In this contribution we look into how to handle PDCP count rollover especially for the SCG split bearer.
RAN2 is still waiting from SA3 on how to derive the keys and the ciphering mechanism to be used on the
NR side. This contribution is based on the assumption that any security parameter which may result in
duplication of the security parameters and need key refresh.

2.Discussion
SCG Split bearer
Figure below describes SCG split bearer user plane architecture and also highlights the problem related to
count rollover in NR-PDCP layer. SCG split bearer will utilise resources in NR-PDCP, NR-RLC, NR-MAC
and LTE-RLC and LTE-MAC sublayers.

Figure 1: SCG split bearer user plane protocol stack and count rollover
If PDCP count or any other parameter’s rollover happens on the NR side, LTE side resources may also need
to be reset. MCG-MAC reset will impact all existing resources like SRBs and other DRBs on the MCG side.

Figure 2: Message sequence if SCG Change procedure is used


Figure above shows the message sequence if SCG change procedure is used as baseline. LTE-DC PDCP
count rollover in SN leads to SCG change procedure being triggered whereby SCG resources are reset. When
PDCP count rollover happens in EN-DC, SN inform MN about it. MN will then derive a new S-KeNB and
send it to the SN like LTE-DC. For SCG bearer, SCG-PDCP, SCG-RLC and SCG-MAC were reset and
probably the same principle could be used for SCG split bearer. However, if SCG-PDCP is reset then MCG-
RLC and MCG-MAC should also be reset. But MCG-MAC is common to all SRBs and DRBs.
Observation 1: LTE DC SCG change procedure, if applied to SCG split bearer, will result in reset of
SCG-PDCP, SCG-RLC and SCG-MAC on the SCG side and MCG-RLC and MCG-MAC on MCG
side in case of PDCP count rollover.
The interruption to user plane will be similar to UE moving to Idle state or performing intra cell HO. It is
worth mentioning that intra cell HO is used when KeNB needs rekeying and probably reused for EN-DC
KeNB refresh as well.
It seems straightforward to use intra cell HO procedure when rollover of any security related parameters
happen in the NR-PDCP as well. The message sequence is shown below:

Figure 3: Intra cell handover triggered by NR-PDCP Count rollover


Based on Figure 3, we conclude that:
Proposal 1: MN is informed about NR-PDCP count rollover as security credentials in the SN are based
on KeNB.
Proposal 2: Use intra cell handover when any rollover happens in NR-PDCP for SCG split bearer and
resources in MN are also used.

MCG bearer
SCG change procedure can be used whereby intra cell handover is triggered, as discussed above:
Proposal 3: If PDCP count rollover happens in MCG-PDCP, requiring refresh of KeNB, then intra
cell handover is triggered.

SCG bearer
We believe that SCG bearer is a special type of SCG split bearer and same handling as SCG split bearer
should apply. However, SCG change procedure can also apply whereby only SCG side of resources are reset.
Observation 2: Either intra cell handover or SCG change procedure can be applied for PDCP count
rollover for SCG bearer
However, we believe that only SCG split bearer should be standardised. So, it should be SN decision to
trigger either intra cell handover (SCG split bearer) or SCG change procedure (SCG bearer) based on if
resources are being utilised in the MN or not.
Proposal 4: it should be SN decision to trigger either intra cell handover or SCG change procedure
based on if resources are being utilised in the MN. If agreed, RAN3 should be informed about it.

3.Conclusion
We propose RAN2 to discuss and agree on following observations and proposals:

Observation 1: LTE DC SCG change procedure, if applied to SCG split bearer, will result in reset of
SCG-PDCP, SCG-RLC and SCG-MAC on the SCG side and MCG-RLC and MCG-MAC on MCG
side in case of PDCP count rollover.
Proposal 1: MN is informed about NR-PDCP count rollover as security credentials in the SN are based
on KeNB.
Proposal 2: Use intra cell handover when any rollover happens in NR-PDCP for SCG split bearer and
resources in MN are also used.
Proposal 3: If PDCP count rollover happens in MCG-PDCP, requiring refresh of KeNB, then intra
cell handover is triggered.
Observation 2: Either intra cell handover or SCG change procedure can be applied for PDCP count
rollover for SCG bearer
Proposal 4: It should be SN decision to trigger either intra cell handover or SCG change procedure
based on if resources are being utilised in the MN. If agreed, RAN3 should be informed about it.
4. References
[1] RP-170874: New WID on New Radio Access Technology, NTTDOCOMO

[2] 3GPP TR 38.802 Study on New Radio (NR) Access Technology; Physical Layer Aspects (Release 14)

[3] 3GPP TR 38.804 Study on New Radio Access Technology; Radio Interface Protocol Aspects (Release 14)

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy