Content for TS 38.331 Word version: 17.4.0

1… 4… 5… 5.2.2.4… 5.3… 5.3.3… 5.3.5… 5.3.5.5… 5.3.5.6… 5.3.5.7… 5.3.5.13… 5.3.6… 5.3.8… 5.3.13… 5.3.14… 5.4… 5.5… 5.5.3… 5.5.4… 5.5.5… 5.5a… 5.7… 5.7.4… 5.7.8… 5.8… 5.8.9… 5.8.10… 5.8.11… 5.9… 6… 6.2.2… 6-2-2-25… 6.3… 6.3.2… 6-3-2-27… 6-3-2-49… 6-3-2-73… 6-3-2-95… 6-3-2-108… 6-3-2-134… 6-3-2-162… 6-3-2-188… 6-3-2-213… 6-3-2-243… 6-3-2-271… 6-3-2-297… 6.3.3… 6-3-3-25… 6-3-3-51… 6.3.4… 6.3.5… 6-3-5-25… 6.3.6… 6.4… 7… 9… 11… A… A.4… B…

5.3.5.6 Radio Bearer configuration 5.3.5.6.1 General 5.3.5.6.2 SRB release 5.3.5.6.3 SRB addition/modification 5.3.5.6.4 DRB release 5.3.5.6.5 DRB addition/modification 5.3.5.6.6 Multicast MRB release 5.3.5.6.7 Multicast MRB addition/modification
...

5.3.5.6 Radio Bearer configuration p. 95

5.3.5.6.1 General p. 95

The UE shall perform the following actions based on a received RadioBearerConfig IE:

1 >

if the RadioBearerConfig includes the srb3-ToRelease or srb4-ToRelease:

2 >

perform the SRB release as specified in clause 5.3.5.6.2;

1 >

if the RadioBearerConfig includes the srb-ToAddModList or if any DAPS bearer is configured:

2 >

perform the SRB addition or reconfiguration as specified in clause 5.3.5.6.3;

1 >

if the RadioBearerConfig includes the drb-ToReleaseList:

2 >

perform DRB release as specified in clause 5.3.5.6.4;

1 >

if the RadioBearerConfig includes the drb-ToAddModList:

2 >

perform DRB addition or reconfiguration as specified in clause 5.3.5.6.5;

1 >

if the RadioBearerConfig includes the mrb-ToReleaseList:

2 >

perform multicast MRB release as specified in clause 5.3.5.6.6;

1 >

if the RadioBearerConfig includes the mrb-ToAddModList:

2 >

perform multicast MRB addition or reconfiguration as specified in clause 5.3.5.6.7;

1 >

release all SDAP entities, if any, that have no associated DRB as specified in clause 5.1.2 of TS 37.324, and indicate the release of the user plane resources for PDU Sessions associated with the released SDAP entities to upper layers;

1 >

release all SDAP entities that have no associated multicast MRB as specified in clause 5.1.2 of TS 37.324, and indicate the release of user plane resources for these MBS multicast sessions to upper layers.

5.3.5.6.2 SRB release p. 96

The UE shall:

1 >

if srb3-ToRelease is included:

2 >

release the PDCP entity and the srb-Identity of the SRB3;

1 >

if srb4-ToRelease is included

2 >

release the PDCP entity and the srb-Identity of the SRB4.

5.3.5.6.3 SRB addition/modification p. 96

The UE shall:

1 >

If any DAPS bearer is configured, for each SRB:

2 >

establish a PDCP entity for the target cell group as specified in TS 38.323, with the same configuration as the PDCP entity for the source cell group;

2 >

if the masterKeyUpdate is received:

3 >

configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KgNB);

2 >

else:

3 >

configure the PDCP entity for the target cell group with state variables continuation as specified in TS 38.323, and with the same security configuration as the PDCP entity for the source cell group;

1 >

for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment or reconfiguration from E-UTRA PDCP to NR PDCP):

2 >

establish a PDCP entity;

2 >

if AS security has been activated:

3 >

if target RAT of handover is E-UTRA/5GC; or

3 >

if the UE is connected to E-UTRA/5GC:

4 >

if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC:

5 >

configure the PDCP entity with the security algorithms and keys (KRRCenc and KRRCint) configured/derived as specified in TS 36.331;

4 >

else (i.e., UE capable of NGEN-DC):

5 >

configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;

3 >

else (i.e., UE connected to NR or UE connected to E-UTRA/EPC):

4 >

configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB/ KgNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;

2 >

if the current UE configuration as configured by E-UTRA in TS 36.331 includes an SRB identified with the same srb-Identity value:

3 >

associate the E-UTRA RLC entity and DCCH of this SRB with the NR PDCP entity;

3 >

release the E-UTRA PDCP entity of this SRB;

2 >

if the pdcp-Config is included:

3 >

configure the PDCP entity in accordance with the received pdcp-Config;

2 >

else:

3 >

configure the PDCP entity in accordance with the default configuration defined in clause 9.2.1 for the corresponding SRB;

1 >

if any DAPS bearer is configured, for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration:

2 >

if the pdcp-Config is included:

3 >

reconfigure the PDCP entity for the target cell group in accordance with the received pdcp-Config;

1 >

else, for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration:

2 >

if the reestablishPDCP is set:

3 >

if target RAT of handover is E-UTRA/5GC; or

3 >

if the UE is connected to E-UTRA/5GC:

4 >

if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC:

5 >

configure the PDCP entity to apply the integrity protection algorithm and KRRCint key configured/derived as specified in TS 36.331, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

5 >

configure the PDCP entity to apply the ciphering algorithm and KRRCenc key configured/derived as specified in TS 36.331, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

4 >

else (i.e., a UE capable of NGEN-DC):

5 >

configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB) or secondary key (S-KgNB), as indicated in keyToUse, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

5 >

configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

3 >

else (i.e., UE connected to NR or UE in EN-DC):

4 >

configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB), as indicated in keyToUse , i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

4 >

configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

3 >

re-establish the PDCP entity of this SRB as specified in TS 38.323;

2 >

else, if the discardOnPDCP is set:

3 >

trigger the PDCP entity to perform SDU discard as specified in TS 38.323;

2 >

if the pdcp-Config is included:

3 >

reconfigure the PDCP entity in accordance with the received pdcp-Config.

5.3.5.6.4 DRB release p. 98

The UE shall:

1 >

for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration; or

1 >

for each drb-Identity value that is to be released as the result of full configuration according to clause 5.3.5.11:

2 >

release the PDCP entity and the drb-Identity;

2 >

if SDAP entity associated with this DRB is configured:

3 >

indicate the release of the DRB to SDAP entity associated with this DRB (clause 5.3.3 of TS 37.324);

2 >

if the DRB is associated with an eps-BearerIdentity:

3 >

if a new bearer is not added either with NR or E-UTRA with same eps-BearerIdentity:

4 >

indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers.

5.3.5.6.5 DRB addition/modification p. 98

The UE shall:

1 >

for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used):

2 >

establish a PDCP entity and configure it in accordance with the received pdcp-Config;

2 >

if the PDCP entity of this DRB is not configured with cipheringDisabled:

3 >

if target RAT of handover is E-UTRA/5GC; or

3 >

if the UE is connected to E-UTRA/5GC:

4 >

if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:

5 >

configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in TS 36.331;

4 >

else (i.e., a UE capable of NGEN-DC):

5 >

configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the key (KUPenc) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable;

3 >

else (i.e., UE connected to NR or UE connected to E-UTRA/EPC):

4 >

configure the PDCP entity with the ciphering algorithms according to securityConfig and apply the KUPenc key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB/S-KeNB) as indicated in keyToUse;

2 >

if the PDCP entity of this DRB is configured with integrityProtection:

3 >

configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the KUPint key associated with the master (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse;

2 >

if an sdap-Config is included:

3 >

if an SDAP entity with the received pdu-Session does not exist:

4 >

establish an SDAP entity as specified in clause 5.1.1 of TS 37.324;

4 >

if an SDAP entity with the received pdu-Session did not exist prior to receiving this reconfiguration:

5 >

indicate the establishment of the user plane resources for the pdu-Session to upper layers;

3 >

configure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324 and associate the DRB with the SDAP entity;

3 >

for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB;

2 >

if the DRB is associated with an eps-BearerIdentity:

3 >

if the DRB was configured with the same eps-BearerIdentity either by NR or E-UTRA prior to receiving this reconfiguration:

4 >

associate the established DRB with the corresponding eps-BearerIdentity;

3 >

else:

4 >

indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

1 >

for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and configured as DAPS bearer:

2 >

reconfigure the PDCP entity to configure DAPS with the ciphering function, integrity protection function and ROHC function of the target cell group as specified in TS 38.323 and configure it in accordance with the received pdcp-Config;

2 >

if the masterKeyUpdate is received:

3 >

if the ciphering function of the target cell group PDCP entity is not configured with cipheringDisabled:

4 >

configure the ciphering function of the target cell group PDCP entity with the ciphering algorithm according to securityConfig and apply the KUPenc key associated with the master key (KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received from the target cell group and sent to the target cell group by the UE;

3 >

if the integrity protection function of the target cell group PDCP entity is configured with integrityProtection:

4 >

configure the integrity protection function of the target cell group PDCP entity with the integrity protection algorithms according to securityConfig and apply the KUPint key associated with the master key (KgNB) as indicated in keyToUse;

2 >

else:

3 >

configure the ciphering function and the integrity protection function of the target cell group PDCP entity with the same security configuration as the PDCP entity for the source cell group;

2 >

if the sdap-Config is included and when indication of successful completion of random access towards target cell is received from lower layers as specified in [3]:

3 >

reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS 37.324;

3 >

for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB;

1 >

for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration and not configured as DAPS bearer:

2 >

if the reestablishPDCP is set:

3 >

if target RAT of handover is E-UTRA/5GC; or

3 >

if the UE is connected to E-UTRA/5GC:

4 >

if the UE is capable of E-UTRA/5GC but not capable of NGEN-DC:

5 >

if the PDCP entity of this DRB is not configured with cipheringDisabled:

6 >

configure the PDCP entity with the ciphering algorithm and KUPenc key configured/derived as specified in clause 5.4.2.3 of TS 36.331, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

4 >

else (i.e., a UE capable of NGEN-DC):

5 >

if the PDCP entity of this DRB is not configured with cipheringDisabled:

6 >

configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB) or the secondary key (S-KgNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

3 >

else (i.e., UE connected to NR or UE connected to E-UTRA/EPC (in EN-DC or capable of EN-DC)):

4 >

if the PDCP entity of this DRB is not configured with cipheringDisabled:

5 >

configure the PDCP entity with the ciphering algorithm and KUPenc key associated with the master key (KeNB/ KgNB) or the secondary key (S-KgNB/S-KeNB), as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent PDCP PDUs received and sent by the UE;

4 >

if the PDCP entity of this DRB is configured with integrityProtection:

5 >

configure the PDCP entity with the integrity protection algorithms according to securityConfig and apply the KUPint key associated with the master key (KeNB/KgNB) or the secondary key (S-KgNB) as indicated in keyToUse;

3 >

if drb-ContinueROHC is included in pdcp-Config:

4 >

indicate to lower layer that drb-ContinueROHC is configured;

3 >

if drb-ContinueEHC-DL is included in pdcp-Config:

4 >

indicate to lower layer that drb-ContinueEHC-DL is configured;

3 >

if drb-ContinueEHC-UL is included in pdcp-Config:

4 >

indicate to lower layer that drb-ContinueEHC-UL is configured;

3 >

if drb-ContinueUDC is included in pdcp-Config:

4 >

indicate to lower layer that drb-ContinueUDC is configured;

3 >

re-establish the PDCP entity of this DRB as specified in clause 5.1.2 of TS 38.323;

2 >

else, if the recoverPDCP is set:

3 >

trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323;

2 >

if the pdcp-Config is included:

3 >

reconfigure the PDCP entity in accordance with the received pdcp-Config.

2 >

if the sdap-Config is included:

3 >

reconfigure the SDAP entity in accordance with the received sdap-Config as specified in TS37.324 [24];

3 >

for each QFI value added in mappedQoS-FlowsToAdd, if the QFI value is previously configured, the QFI value is released from the old DRB;

5.3.5.6.6 Multicast MRB release |R17| p. 101

The UE shall:

1 >

for each mrb-Identity value included in the mrb-ToReleaseList that is part of the current UE configuration; or

1 >

for each mrb-Identity value that is to be released as the result of full configuration according to clause 5.3.5.11:

2 >

release the PDCP entity and the mrb-Identity;

2 >

if there is no other multicast MRB configured with the same mbs-SessionId as configured for the released multicast MRB:

3 >

indicate the release of the user plane resources for the mbs-SessionId to upper layers.

5.3.5.6.7 Multicast MRB addition/modification |R17| p. 101

The UE shall for each element in the order of entry in the list mrb-ToAddModList:

1 >

if mrb-Identity value included in the mrb-ToAddModList is part of the UE configuration:

2 >

if mrb-Identity value included in the mrb-ToAddModList for which mrb-IdentityNew is included (i.e., multicast MRB ID change):

3 >

update the mrb-Identity to the value mrb-IdentityNew;

2 >

if the reestablishPDCP is set:

3 >

if drb-ContinueROHC is included in pdcp-Config:

4 >

indicate to lower layer that drb-ContinueROHC is configured;

3 >

if drb-ContinueEHC-DL is included in pdcp-Config:

4 >

indicate to lower layer that drb-ContinueEHC-DL is configured;

3 >

re-establish the PDCP entity of this multicast MRB as specified in clause 5.1.2 of TS 38.323;

2 >

else, if the recoverPDCP is set:

3 >

trigger the PDCP entity of this MRB to perform data recovery as specified in TS 38.323;

2 >

if the pdcp-Config is included:

3 >

reconfigure the PDCP entity in accordance with the received pdcp-Config;

1 >

else if mrb-Identity value included in the mrb-ToAddModList is not part of the UE configuration (i.e., multicast MRB establishment including the case when full configuration option is used):

2 >

establish a PDCP entity and configure it in accordance with the received pdcp-Config;

2 >

associate the established multicast MRB with the corresponding mbs-SessionId;

2 >

if an SDAP entity with the received mbs-SessionId does not exist:

3 >

establish an SDAP entity as specified in clause 5.1.1 of TS 37.324;

3 >

if an SDAP entity with the received mbs-SessionId did not exist prior to receiving this reconfiguration:

4 >

indicate the establishment of the user plane resources for the mbs-SessionId to upper layers.