5.3.5 RRC reconfiguration
38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 17TS
5.3.5.1 General
Figure 5.3.5.1-1: RRC reconfiguration, successful
Figure 5.3.5.1-2: RRC reconfiguration, failure
The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs/BH RLC channels/Uu Relay RLC channels/PC5 Relay RLC channels, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change or conditional PSCell addition configuration. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE.
RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases:
– reconfiguration with sync and security key refresh, involving RA to the PCell/PSCell, MAC reset, refresh of security and re-establishment of RLC and PDCP triggered by explicit L2 indicators;
– reconfiguration with sync but without security key refresh, involving RA to the PCell/PSCell, MAC reset and RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit L2 indicators.
– reconfiguration with sync for DAPS and security key refresh, involving RA to the target PCell, establishment of target MAC, and
– for non-DAPS bearer: refresh of security and re-establishment of RLC and PDCP triggered by explicit L2 indicators;
– for DAPS bearer: establishment of RLC for the target PCell, refresh of security and reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell;
– for SRB: refresh of security and establishment of RLC and PDCP for the target PCell;
– reconfiguration with sync for DAPS but without security key refresh, involving RA to the target PCell, establishment of target MAC, and
– for non-DAPS bearer: RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit L2 indicators.
– for DAPS bearer: establishment of RLC for target PCell, reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell;
– for SRB: establishment of RLC and PDCP for the target PCell.
– reconfiguration with sync for direct-to-indirect path switch, not involving RA at target side, involving re-establishment of PDCP /PDCP data recovery (for AM DRB) triggered by explicit L2 indicators.
In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for IAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, and to reconfigure PDCP for DRBs associated with the S-KgNB or SRB3, and to reconfigure SDAP for DRBs associated with S-KgNB in NGEN-DC and NR-DC, and to add/modify/release conditional PSCell change configuration, provided that the (re-)configuration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, only measConfig, radioBearerConfig, conditionalReconfiguration, bap-Config, iab-IP-AddressConfigurationList, otherConfig and/or secondaryCellGroup are included in RRCReconfiguration received via SRB3, except when RRCReconfiguration is received within DLInformationTransferMRDC.
5.3.5.2 Initiation
The Network may initiate the RRC reconfiguration procedure to a UE in RRC_CONNECTED. The Network applies the procedure as follows:
– the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is performed only when AS security has been activated;
– the establishment of BH RLC Channels for IAB is performed only when AS security has been activated;
– the establishment of Uu Relay RLC channels and PC5 Relay RLC channels (other than SL-RLC0 and SL-RLC1, that is established before RRC connection establishment) for L2 U2N Relay UE is performed only when AS security has been activated, and the establishment of PC5 Relay RLC channels for L2 U2N Remote UE (other than SL-RLC0 and SL-RLC1, that is established before RRC connection establishment) is performed only when AS security has been activated;
– the addition of Secondary Cell Group and SCells is performed only when AS security has been activated;
– the reconfigurationWithSync is included in secondaryCellGroup only when at least one RLC bearer or BH RLC channel is setup in SCG;
– the reconfigurationWithSync is included in masterCellGroup only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended;
– the conditionalReconfiguration for CPC is included only when at least one RLC bearer is setup in SCG;
– the conditionalReconfiguration for CHO or CPA is included only when AS security has been activated, and SRB2 with at least one DRB or multicast MRB or, for IAB, SRB2, are setup and not suspended.
5.3.5.3 Reception of an RRCReconfiguration by the UE
The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO, CPA or CPC):
1> if the RRCReconfiguration is applied due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3:
2> remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
1> if the RRCReconfiguration includes the daps-SourceRelease:
2> reset the source MAC and release the source MAC configuration;
2> for each DAPS bearer:
3> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
2> for each SRB:
3> release the PDCP entity for the source SpCell;
3> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the source SpCell;
2> release the physical channel configuration for the source SpCell;
2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any;
1> if the RRCReconfiguration is received via other RAT (i.e., inter-RAT handover to NR):
2> if the RRCReconfiguration does not include the fullConfig and the UE is connected to 5GC (i.e., delta signalling during intra 5GC handover):
3> re-use the source RAT SDAP and PDCP configurations if available (i.e., current SDAP/PDCP configurations for all RBs from source E-UTRA RAT prior to the reception of the inter-RAT HO RRCReconfiguration message);
1> else:
2> if the RRCReconfiguration includes the fullConfig:
3> perform the full configuration procedure as specified in 5.3.5.11;
1> if the RRCReconfiguration includes the masterCellGroup:
2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5;
1> if the RRCReconfiguration includes the masterKeyUpdate:
2> perform AS security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the sk-Counter:
2> perform security key update procedure as specified in 5.3.5.7;
1> if the RRCReconfiguration includes the secondaryCellGroup:
2> perform the cell group configuration for the SCG according to 5.3.5.5;
1> if the RRCReconfiguration includes the mrdc-SecondaryCellGroupConfig:
2> if the mrdc-SecondaryCellGroupConfig is set to setup:
3> if the mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd:
4> perform MR-DC release as specified in clause 5.3.5.10;
3> if the received mrdc-SecondaryCellGroup is set to nr-SCG:
4> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG;
3> if the received mrdc-SecondaryCellGroup is set to eutra-SCG:
4> perform the RRC connection reconfiguration as specified in TS 36.331 [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG;
2> else (mrdc-SecondaryCellGroupConfig is set to release):
3> perform MR-DC release as specified in clause 5.3.5.10;
1> if the RRCReconfiguration message includes the radioBearerConfig:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the radioBearerConfig2:
2> perform the radio bearer configuration according to 5.3.5.6;
1> if the RRCReconfiguration message includes the measConfig:
2> perform the measurement configuration procedure as specified in 5.5.2;
1> if the RRCReconfiguration message includes the dedicatedNAS-MessageList:
2> forward each element of the dedicatedNAS-MessageList to upper layers in the same order as listed;
1> if the RRCReconfiguration message includes the dedicatedSIB1-Delivery:
2> perform the action upon reception of SIB1 as specified in 5.2.2.4.2;
NOTE 0: If this RRCReconfiguration is associated to the MCG and includes reconfigurationWithSync in spCellConfig and dedicatedSIB1-Delivery, the UE initiates (if needed) the request to acquire required SIBs, according to clause 5.2.2.3.5, only after the random access procedure towards the target SpCell is completed.
1> if the RRCReconfiguration message includes the dedicatedSystemInformationDelivery:
2> perform the action upon reception of System Information as specified in 5.2.2.4;
1> if the RRCReconfiguration message includes the dedicatedPosSysInfoDelivery:
2> perform the action upon reception of the contained posSIB(s), as specified in clause 5.2.2.4.16;
1> if the RRCReconfiguration message includes the otherConfig:
2> perform the other configuration procedure as specified in 5.3.5.9;
1> if the RRCReconfiguration message includes the bap-Config:
2> perform the BAP configuration procedure as specified in 5.3.5.12;
1> if the RRCReconfiguration message includes the iab-IP-AddressConfigurationList:
2> if iab-IP-AddressToReleaseList is included:
3> perform release of IP address as specified in 5.3.5.12a.1.1;
2> if iab-IP-AddressToAddModList is included:
3> perform IAB IP address addition/update as specified in 5.3.5.12a.1.2;
1> if the RRCReconfiguration message includes the conditionalReconfiguration:
2> perform conditional reconfiguration as specified in 5.3.5.13;
1> if the RRCReconfiguration message includes the needForGapsConfigNR:
2> if needForGapsConfigNR is set to setup:
3> consider itself to be configured to provide the measurement gap requirement information of NR target bands;
2> else:
3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands;
1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR:
2> if needForGapNCSG-ConfigNR is set to setup:
3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands;
2> else:
3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands;
1> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA:
2> if needForGapNCSG-ConfigEUTRA is set to setup:
3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E‑UTRA target bands;
2> else:
3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E‑UTRA target bands;
1> if the RRCReconfiguration message includes the sl-ConfigDedicatedNR:
2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14;
NOTE 0a: If the sl-ConfigDedicatedNR was received embedded within an E-UTRA RRCConnectionReconfiguration message, the UE does not build an NR RRCReconfigurationComplete message for the received sl-ConfigDedicatedNR.
1> if the RRCReconfiguration message includes the sl-L2RelayUE-Config:
2> perform the L2 U2N Relay UE configuration procedure as specified in 5.3.5.15;
1> if the RRCReconfiguration message includes the sl-L2RemoteUE-Config:
2> perform the L2 U2N Remote UE configuration procedure as specified in 5.3.5.16;
1> if the RRCReconfiguration message includes the dedicatedPagingDelivery:
2> perform the Paging message reception procedure as specified in 5.3.2.3;
1> if the RRCReconfiguration message includes the sl-ConfigDedicatedEUTRA-Info:
2> perform related procedures for V2X sidelink communication in accordance with TS 36.331 [10], clause 5.3.10 and clause 5.5.2;
1> if the RRCReconfiguration message includes the ul-GapFR2-Config:
2> perform the FR2 UL gap configuration procedure as specified in 5.3.5.13c;
1> if the RRCReconfiguration message includes the musim-GapConfig:
2> perform the MUSIM gap configuration procedure as specified in 5.3.5.9a;
1> if the RRCReconfiguration message includes the appLayerMeasConfig:
2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d;
1> set the content of the RRCReconfigurationComplete message as follows:
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrent:
3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL;
3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList;
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier:
3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG;
2> if the RRCReconfiguration includes the masterCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier:
3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the MCG;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrent:
3> include the uplinkTxDirectCurrentList for each SCG serving cell with UL;
3> include uplinkDirectCurrentBWP-SUL for each SCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentTwoCarrier:
3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG;
2> if the RRCReconfiguration includes the secondaryCellGroup containing the reportUplinkTxDirectCurrentMoreCarrier:
3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured intra-band uplink carrier aggregation in the SCG;
NOTE 0b: The UE does not expect that the reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier is received in both masterCellGroup and in secondaryCellGroup. Network only configures at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in one RRC message.
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to eutra-SCG:
3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331 [10] clause 5.3.5.3;
2> if the RRCReconfiguration message includes the mrdc-SecondaryCellGroupConfig with mrdc-SecondaryCellGroup set to nr-SCG:
3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message;
3> if the RRCReconfiguration message is applied due to conditional reconfiguration execution and the RRCReconfiguration message does not include the reconfigurationWithSync in the masterCellGroup:
4> include in the selectedCondRRCReconfig the condReconfigId for the selected cell of conditional reconfiguration execution;
2> if the RRCReconfiguration includes the reconfigurationWithSync in spCellConfig of an MCG:
3> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:
4> include the logMeasAvailable in the RRCReconfigurationComplete message;
4> if Bluetooth measurement results are included in the logged measurements the UE has available for NR:
5> include the logMeasAvailableBT in the RRCReconfigurationComplete message;
4> if WLAN measurement results are included in the logged measurements the UE has available for NR:
5> include the logMeasAvailableWLAN in the RRCReconfigurationComplete message;
3> if the sigLoggedMeasType in VarLogMeasReport is included:
4> if T330 timer is running and the logged measurements configuration is for NR:
5> set sigLogMeasConfigAvailable to true in the RRCReconfigurationComplete message;
4> else:
5> if the UE has logged measurements available for NR:
6> set sigLogMeasConfigAvailable to false in the RRCReconfigurationComplete message;
3> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList:
4> include connEstFailInfoAvailable in the RRCReconfigurationComplete message;
3> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report; or
3> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331 [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331 [10]:
4> include rlf-InfoAvailable in the RRCReconfigurationComplete message;
3> if the UE was configured with successHO-Config when connected to the source PCell; and
3> if the applied RRCReconfiguration is not due to a conditional reconfiguration execution upon cell selection performed while timer T311 was running, as defined in 5.3.7.3:
4> perform the actions for the successful handover report determination as specified in clause 5.7.10.6, upon successfully completing the Random Access procedure triggered for the reconfigurationWithSync in spCellConfig of the MCG;
3> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report:
4> include successHO-InfoAvailable in the RRCReconfigurationComplete message;
2> if the RRCReconfiguration message was received via SRB1, but not within mrdc-SecondaryCellGroup or E-UTRA RRCConnectionReconfiguration or E-UTRA RRCConnectionResume:
3> if the UE is configured to provide the measurement gap requirement information of NR target bands:
4> if the RRCReconfiguration message includes the needForGapsConfigNR; or
4> if the NeedForGapsInfoNR information is changed compared to last time the UE reported this information:
5> include the NeedForGapsInfoNR and set the contents as follows:
6> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell;
6> if requestedTargetBandFilterNR is configured:
7> for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band;
6> else:
7> include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band;
3> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands:
4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigNR; or
4> if the needForGapNCSG-InfoNR information is changed compared to last time the UE reported this information:
5> include the NeedForGapNCSG-InfoNR and set the contents as follows:
6> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell;
6> if requestedTargetBandFilterNCSG-NR is configured:
7> for each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band;
6> else:
7> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information;
3> if the UE is configured to provide the measurement gap and NCSG requirement information of E‑UTRA target bands:
4> if the RRCReconfiguration message includes the needForGapNCSG-ConfigEUTRA; or
4> if the needForGapNCSG-InfoEUTRA information is changed compared to last time the UE reported this information:
5> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows:
6> if requestedTargetBandFilterNCSG-EUTRA is configured, for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; otherwise, include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information;
1> if the UE is configured with E-UTRA nr-SecondaryCellGroupConfig (UE in (NG)EN-DC):
2> if the RRCReconfiguration message was received via E-UTRA SRB1 as specified in TS 36.331 [10]; or
2> if the RRCReconfiguration message was received via E-UTRA RRC message RRCConnectionReconfiguration within MobilityFromNRCommand (handover from NR standalone to (NG)EN-DC);
3> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SecondaryCellGroupConfig specified in TS 36.331 [10]:
4> submit the RRCReconfigurationComplete message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331 [10], clause 5.6.2a.
3> else if the RRCReconfiguration message was included in E-UTRA RRCConnectionResume message:
4> submit the RRCReconfigurationComplete message via E-UTRA embedded in E-UTRA RRC message RRCConnectionResumeComplete as specified in TS 36.331 [10], clause 5.3.3.4a;
3> else:
4> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4/5.4.2.3;
3> if the scg-State is not included in the E-UTRA RRCConnectionReconfiguration message or E-UTRA RRCConnectionResume message containing the RRCReconfiguration message:
4> perform SCG activation as specified in 5.3.5.13a;
4> if reconfigurationWithSync was included in spCellConfig of an SCG:
5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
4> else if the SCG was deactivated before the reception of the E-UTRA RRC message containing the RRCReconfiguration message:
5> if bfd-and-RLM was not configured to true before the reception of the E-UTRA RRCConnectionReconfiguration or RRCConnectionResume message containing the RRCReconfiguration message or if lower layers indicate that a Random Access procedure is needed for SCG activation:
6> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3];
5> else the procedure ends;
4> else the procedure ends;
3> else:
4> perform SCG deactivation as specified in 5.3.5.13b;
4> the procedure ends;
2> if the RRCReconfiguration message was received within nr-SecondaryCellGroupConfig in RRCConnectionReconfiguration message received via SRB3 within DLInformationTransferMRDC:
3> submit the RRCReconfigurationComplete via E-UTRA embedded in E-UTRA RRC message RRCConnectionReconfigurationComplete as specified in TS 36.331 [10], clause 5.3.5.3/5.3.5.4;
3> if the scg-State is not included in the RRCConnectionReconfiguration:
4> if reconfigurationWithSync was included in spCellConfig of an SCG:
5> initiate the Random Access procedure on the SpCell, as specified in TS 38.321 [3];
4> else the procedure ends;
3> else:
4> perform SCG deactivation as specified in 5.3.5.13b;
4> the procedure ends;
NOTE 1: The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
2> else (RRCReconfiguration was received via SRB3) but not within DLInformationTransferMRDC:
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
NOTE 2: In (NG)EN-DC and NR-DC, in the case RRCReconfiguration is received via SRB1 or within DLInformationTransferMRDC via SRB3, the random access is triggered by RRC layer itself as there is not necessarily other UL transmission. In the case RRCReconfiguration is received via SRB3 but not within DLInformationTransferMRDC, the random access is triggered by the MAC layer due to arrival of RRCReconfigurationComplete.
1> else if the RRCReconfiguration message was received via SRB1 within the nr-SCG within mrdc-SecondaryCellGroup (UE in NR-DC, mrdc-SecondaryCellGroup was received in RRCReconfiguration or RRCResume via SRB1):
2> if the RRCReconfiguration is applied due to a conditional reconfiguration execution for CPC which is configured via conditionalReconfiguration contained in nr-SCG within mrdc-SecondaryCellGroup:
3> submit the RRCReconfigurationComplete message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3.
2> if the scg-State is not included in the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message:
3> perform SCG activation as specified in 5.3.5.13a;
3> if reconfigurationWithSync was included in spCellConfig in nr-SCG:
4> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
3> else if the SCG was deactivated before the reception of the NR RRC message containing the RRCReconfiguration message:
4> if bfd-and-RLM was not configured to true before the reception of the RRCReconfiguration or RRCResume message containing the RRCReconfiguration message; or
4> if lower layers indicate that a Random Access procedure is needed for SCG activation:
5> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
4> else the procedure ends;
3> else the procedure ends;
2> else
3> perform SCG deactivation as specified in 5.3.5.13b;
3> the procedure ends;
NOTE 2a: The order in which the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is left to UE implementation.
1> else if the RRCReconfiguration message was received via SRB3 (UE in NR-DC):
2> if the RRCReconfiguration message was received within DLInformationTransferMRDC:
3> if the RRCReconfiguration message was received within the nr-SCG within mrdc-SecondaryCellGroup (NR SCG RRC Reconfiguration):
4> if the scg-State is not included in the RRCReconfiguration message containing the RRCReconfiguration message:
5> if reconfigurationWithSync was included in spCellConfig in nr-SCG:
6> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3];
5> else:
6> the procedure ends;
4> else:
5> perform SCG deactivation as specified in 5.3.5.13b;
5> the procedure ends;
3> else:
4> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig:
5> if the RRCReconfiguration includes the scg-State:
6> perform SCG deactivation as specified in 5.3.5.13b;
4> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> else:
3> submit the RRCReconfigurationComplete message via SRB3 to lower layers for transmission using the new configuration;
1> else (RRCReconfiguration was received via SRB1):
2> if the UE is in NR-DC and;
2> if the RRCReconfiguration does not include the mrdc-SecondaryCellGroupConfig:
3> if the RRCReconfiguration includes the scg-State:
4> perform SCG deactivation as specified in 5.3.5.13b;
3> else:
4> perform SCG activation without SN message as specified in 5.3.5.13b1;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if ta-Report is configured with value enabled and the UE supports TA reporting:
4> indicate TA report initiation to lower layers;
2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;
2> if this is the first RRCReconfiguration message after successful completion of the RRC re-establishment procedure:
3> resume SRB2, SRB4, DRBs, multicast MRB, and BH RLC channels for IAB-MT, that are suspended;
1> if reconfigurationWithSync was included in spCellConfig of an MCG or SCG and when MAC of an NR cell group successfully completes a Random Access procedure triggered above; or,
1> if sl-PathSwitchConfig was included in reconfigurationWithSync included in spCellConfig of an MCG, and when successfully sending RRCReconfigurationComplete message (i.e., PC5 RLC acknowledgement is received from target L2 U2N Relay UE):
2> stop timer T304 for that cell group if running;
2> if sl-PathSwitchConfig was included in reconfigurationWithSync:
3> stop timer T420;
3> release all radio resources, including release of the RLC entities and the MAC configuration at the source side;
NOTE 2b: PDCP and SDAP configured by the source prior to the path switch that are reconfigured and re-used by target when delta signalling is used, are not released as part of this procedure.
2> stop timer T310 for source SpCell if running;
2> apply the parts of the CSI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the respective target SpCell, if any;
2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the respective target SpCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of that target SpCell;
2> for each DRB configured as DAPS bearer, request uplink data switching to the PDCP entity, as specified in TS 38.323 [5];
2> if the reconfigurationWithSync was included in spCellConfig of an MCG:
3> if T390 is running:
4> stop timer T390 for all access categories;
4> perform the actions as specified in 5.3.14.4.
3> if T350 is running:
4> stop timer T350;
3> if RRCReconfiguration does not include dedicatedSIB1-Delivery and
3> if the active downlink BWP, which is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG, has a common search space configured by searchSpaceSIB1:
4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13], of the target SpCell of the MCG;
4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2;
2> if the reconfigurationWithSync was included in spCellConfig of an MCG; or
2> if the reconfigurationWithSync was included in spCellConfig of an SCG and the CPA or CPC was configured:
3> remove all the entries within the MCG and the SCG VarConditionalReconfig, if any;
3> remove all the entries within VarConditionalReconfiguration as specified in TS 36.331 [10], clause 5.3.5.9.6, if any;
3> for each measId of the MCG measConfig, if configured, and for each measId of the SCG measConfig, if configured, if the associated reportConfig has a reportType set to condTriggerConfig:
4> for the associated reportConfigId:
5> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;
4> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig:
5> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;
4> remove the entry with the matching measId from the measIdList within the VarMeasConfig;
2> if reconfigurationWithSync was included in masterCellGroup or secondaryCellGroup:
3> if the UE initiated transmission of a UEAssistanceInformation message for the corresponding cell group during the last 1 second, and the UE is still configured to provide the concerned UE assistance information for the corresponding cell group; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE is configured to provide UE assistance information for the corresponding cell group, and the UE has initiated transmission of a UEAssistanceInformation message for the corresponding cell group since it was configured to do so in accordance with 5.7.4.2:
4> initiate transmission of a UEAssistanceInformation message for the corresponding cell group in accordance with clause 5.7.4.3 to provide the concerned UE assistance information;
4> start or restart the prohibit timer (if exists) or the leave without response timer for the MUSIM associated with the concerned UE assistance information with the timer value set to the value in corresponding configuration;
3> if SIB12 is provided by the target PCell, and the UE initiated transmission of a SidelinkUEInformationNR message indicating a change of NR sidelink communication/discovery related parameters relevant in target PCell (i.e. change of sl-RxInterestedFreqList or sl-TxResourceReqList) during the last 1 second preceding reception of the RRCReconfiguration message including reconfigurationWithSync in spCellConfig of an MCG; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution and the UE is capable of NR sidelink communication/discovery and SIB12 is provided by the target PCell, and the UE has initiated transmission of a SidelinkUEInformationNR message since it was configured to do so in accordance with 5.8.3.2:
4> initiate transmission of the SidelinkUEInformationNR message in accordance with 5.8.3.3;
2> if reconfigurationWithSync was included in masterCellGroup:
3> if configured with application layer measurements and if application layer measurement report container has been received from upper layers for which the successful transmission of the message or at least one segment of the message has not been confirmed by lower layers:
4> re-submit the MeasurementReportAppLayer message or all segments of the MeasurementReportAppLayer message to lower layers for transmission via SRB4;
2> if reconfigurationWithSync was included in masterCellGroup and the target cell provides SIB21:
3> if the UE initiated transmission of an MBSInterestIndication message during the last 1 second preceding reception of this RRCReconfiguration message; or
3> if the RRCReconfiguration message is applied due to a conditional reconfiguration execution, and the UE has initiated transmission of an MBSInterestIndication message after having received this RRCReconfiguration message:
4> initiate transmission of an MBSInterestIndication message in accordance with clause 5.9.4;
2> the procedure ends.
NOTE 3: The UE is only required to acquire broadcasted SIB1 if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located.
NOTE 4: The UE sets the content of UEAssistanceInformation according to latest configuration (i.e. the configuration after applying the RRCReconfiguration message) and latest UE preference. The UE may include more than the concerned UE assistance information within the UEAssistanceInformation according to 5.7.4.2. Therefore, the content of UEAssistanceInformation message might not be the same as the content of the previous UEAssistanceInformation message.
5.3.5.4 Secondary cell group release
The UE shall:
1> as a result of SCG release triggered by E-UTRA (i.e. (NG)EN-DC case) or NR (i.e. NR-DC case):
2> reset SCG MAC, if configured;
2> for each RLC bearer that is part of the SCG configuration:
3> perform RLC bearer release procedure as specified in 5.3.5.5.3;
2> for each BH RLC channel that is part of the SCG configuration:
3> perform BH RLC channel release procedure as specified in 5.3.5.5.10;
2> release the SCG configuration;
2> remove all the entries within the SCG VarConditionalReconfig, if any;
2> if SCG release was triggered by NR (i.e. NR-DC case):
3> remove all the entries within the MCG VarConditionalReconfig for which the RRCReconfiguration within condRRCReconfig does not include the masterCellGroup with reconfigurationWithSync, if any;
2> else (i.e. EN-DC case):
3> perform VarConditionalReconfiguration CPC removal as specified in TS 36.331 [10] clause 5.3.5.9.7;
2> stop timer T310 for the corresponding SpCell, if running;
2> stop timer T312 for the corresponding SpCell, if running;
2> stop timer T304 for the corresponding SpCell, if running.
NOTE: Release of cell group means only release of the lower layer configuration of the cell group but the RadioBearerConfig may not be released.
5.3.5.5 Cell Group configuration
5.3.5.5.1 General
The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331 [10], and for NE-DC, the SCG is configured as specified in TS 36.331 [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig IE.
The UE performs the following actions based on a received CellGroupConfig IE:
1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync:
2> perform Reconfiguration with sync according to 5.3.5.5.2;
2> resume all suspended radio bearers except the SRBs for the source cell group, and resume SCG transmission for all radio bearers, and resume BH RLC channels and resume SCG transmission for BH RLC channels for IAB-MT, if suspended;
NOTE: If the SCG is deactivated, resuming SCG transmission for all radio bearers does not imply that PDCP PDUs can be transmitted or received on SCG RLC bearers.
1> if the CellGroupConfig contains the rlc-BearerToReleaseList or rlc-BearerToReleaseListExt:
2> perform RLC bearer release as specified in 5.3.5.5.3;
1> if the CellGroupConfig contains the rlc-BearerToAddModList:
2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4;
1> if the CellGroupConfig contains the mac-CellGroupConfig:
2> configure the MAC entity of this cell group as specified in 5.3.5.5.5;
1> if the CellGroupConfig contains the sCellToReleaseList:
2> perform SCell release as specified in 5.3.5.5.8;
1> if the CellGroupConfig contains the spCellConfig:
2> configure the SpCell as specified in 5.3.5.5.7;
1> if the CellGroupConfig contains the sCellToAddModList:
2> perform SCell addition/modification as specified in 5.3.5.5.9;
1> if the CellGroupConfig contains the bh-RLC-ChannelToReleaseList:
2> perform BH RLC channel release as specified in 5.3.5.5.10;
1> if the CellGroupConfig contains the bh-RLC-ChannelToAddModList:
2> perform the BH RLC channel addition/modification as specified in 5.3.5.5.11;
1> if the CellGroupConfig contains the uu-RelayRLC-ChannelToReleaseList:
2> perform Uu Relay RLC channel release as specified in 5.3.5.5.12;
1> if the CellGroupConfig contains the uu-RelayRLC-ChannelToAddModList:
2> perform the Uu Relay RLC channel addition/modification as specified in 5.3.5.5.13;
5.3.5.5.2 Reconfiguration with sync
The UE shall perform the following actions to execute a reconfiguration with sync.
1> stop timer T430 if running;
1> start timer T430 with the timer value set to ntn-UlSyncValidityDuration from the subframe indicated by epochTime, if included in the reconfigurationWithSync for serving cell;
1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause ‘other‘ upon which the procedure ends;
1> if no DAPS bearer is configured:
2> stop timer T310 for the corresponding SpCell, if running;
1> if this procedure is executed for the MCG:
2> if timer T316 is running;
3> stop timer T316;
3> clear the information included in VarRLF-Report, if any;
2> resume MCG transmission, if suspended.
1> stop timer T312 for the corresponding SpCell, if running;
1> if sl-PathSwitchConfig is included:
2> consider the target L2 U2N Relay UE to be the one indicated by the targetRelayUE-Identity in the sl-PathSwitchConfig;
2> start timer T420 for the corresponding target L2 U2N Relay UE with the timer value set to T420, as included in the sl-PathSwitchConfig;
2> apply the value of the newUE-Identity as the C-RNTI;
2> indicate to upper layer (to trigger the PC5 unicast link establishment) with the target L2 U2N Relay UE indicated by the targetRelayUE-Identity;
2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1;
1> else (sl-PathSwitchConfig is not included):
2> if this procedure is executed for the MCG or if this procedure is executed for an SCG not indicated as deactivated in the E-UTRA or NR RRC message in which the RRCReconfiguration message is embedded:
3> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync;
2> if the frequencyInfoDL is included:
3> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId;
2> else:
3> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId;
2> start synchronising to the DL of the target SpCell;
2> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell;
2> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213 [13];
NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message.
NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access.
NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell.
2> If any DAPS bearer is configured:
3> create a MAC entity for the target cell group with the same configuration as the MAC entity for the source cell group;
3> for each DAPS bearer:
4> establish an RLC entity or entities for the target cell group, with the same configurations as for the source cell group;
4> establish the logical channel for the target cell group, with the same configurations as for the source cell group;
NOTE 2b: In order to understand if a DAPS bearer is configured, the UE needs to check the presence of the field daps-Config within the RadioBearerConfig IE received in radioBearerConfig or radioBearerConfig2.
3> for each SRB:
4> establish an RLC entity for the target cell group, with the same configurations as for the source cell group;
4> establish the logical channel for the target cell group, with the same configurations as for the source cell group;
3> suspend SRBs for the source cell group;
NOTE 3: Void
3> apply the value of the newUE-Identity as the C-RNTI in the target cell group;
3> configure lower layers for the target SpCell in accordance with the received spCellConfigCommon;
3> configure lower layers for the target SpCell in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
2> else:
3> reset the MAC entity of this cell group;
3> consider the SCell(s) of this cell group, if configured, that are not included in the SCellToAddModList in the RRCReconfiguration message, to be in deactivated state;
3> apply the value of the newUE-Identity as the C-RNTI for this cell group;
3> configure lower layers in accordance with the received spCellConfigCommon;
3> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync.
2> if the UE is acting as L2 U2N Remote UE at the source side:
3> indicate upper layer to trigger PC5 unicast link release.
Upon L2 U2N Relay UE receiving reconfigurationWithSync, it either indicates to upper layers (to trigger PC5 unicast link release) or sends Notification message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10.
5.3.5.5.3 RLC bearer release
The UE shall:
1> for each logicalChannelIdentity/LogicalChannelIdentityExt value included in the rlc-BearerToReleaseList/rlc-BearerToReleaseListExt that is part of the current UE configuration within the same cell group (LCH release); or
1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4:
2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3;
2> release the corresponding logical channel.
5.3.5.5.4 RLC bearer addition/modification
For each RLC-BearerConfig received in the rlc-BearerToAddModList IE the UE shall:
1> if the UE’s current configuration contains an RLC bearer with the received logicalChannelIdentity/LogicalChannelIdentityExt within the same cell group:
2> if the RLC bearer is associated with an DAPS bearer, or
2> if any DAPS bearer is configured and the RLC bearer is associated with an SRB:
3> reconfigure the RLC entity or entities for the target cell group in accordance with the received rlc-Config;
3> reconfigure the logical channel for the target cell group in accordance with the received mac-LogicalChannelConfig;
2> else:
3> if reestablishRLC is received:
4> re-establish the RLC entity as specified in TS 38.322 [4];
3> reconfigure the RLC entity or entities in accordance with the received rlc-Config;
3> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig;
3> if servedMBS-RadioBearer is received:
4> associate this logical channel with the PDCP entity identified by servedMBS-RadioBearer;
NOTE 1: For DRB and SRB, the network does not re-associate an already configured logical channel with another radio bearer. For MRB, the network does not re-associate an already configured logical channel with DRB or SRB. Hence servedRadioBearer is not present in this case.
NOTE 2: In DAPS handover, the UE may perform RLC entity re-establishment (if reestablishRLC is set) for an RLC bearer associated with a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3].
1> else (a logical channel with the given logicalChannelIdentity/LogicalChannelIdentityExt is not configured within the same cell group, including the case when full configuration option is used):
2> if the servedRadioBearer associates the logical channel with an SRB and rlc-Config is not included:
3> establish an RLC entity in accordance with the default configuration defined in 9.2 for the corresponding SRB;
2> else:
3> establish an RLC entity in accordance with the received rlc-Config;
2> if the servedRadioBearer associates the logical channel with an SRB and if mac-LogicalChannelConfig is not included:
3> configure this MAC entity with a logical channel in accordance to the default configuration defined in 9.2 for the corresponding SRB;
2> else:
3> configure this MAC entity with a logical channel in accordance to the received mac-LogicalChannelConfig;
2> associate this logical channel with the PDCP entity identified by servedRadioBearer or servedMBS-RadioBearer.
5.3.5.5.5 MAC entity configuration
The UE shall:
1> if SCG MAC is not part of the current UE configuration (i.e. SCG establishment):
2> create an SCG MAC entity;
1> if any DAPS bearer is configured:
2> reconfigure the MAC main configuration for the target cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList;
1> else:
2> reconfigure the MAC main configuration of the cell group in accordance with the received mac-CellGroupConfig excluding tag-ToReleaseList and tag-ToAddModList;
1> if the received mac-CellGroupConfig includes the tag-ToReleaseList:
2> for each TAG-Id value included in the tag-ToReleaseList that is part of the current UE configuration:
3> release the TAG indicated by TAG-Id;
1> if the received mac-CellGroupConfig includes the tag-ToAddModList:
2> for each tag-Id value included in tag-ToAddModList that is not part of the current UE configuration (TAG addition):
3> add the TAG, corresponding to the tag-Id, in accordance with the received timeAlignmentTimer;
2> for each tag-Id value included in tag-ToAddModList that is part of the current UE configuration (TAG modification):
3> reconfigure the TAG, corresponding to the tag-Id, in accordance with the received timeAlignmentTimer.
5.3.5.5.6 RLF Timers & Constants configuration
The UE shall:
1> if the received rlf-TimersAndConstants is set to release:
2> if any DAPS bearer is configured:
3> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIB1;
2> else:
3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
1> else:
2> if any DAPS bearer is configured:
3> configure the value of timers and constants for the target cell group in accordance with received rlf-TimersAndConstants;
2> else:
3> (re-)configure the value of timers and constants in accordance with received rlf-TimersAndConstants;
3> stop timer T310 for this cell group, if running;
3> stop timer T312 for this cell group, if running;
3> reset the counters N310 and N311.
5.3.5.5.7 SpCell Configuration
The UE shall:
1> if the UE is acting as L2 U2N Remote UE:
2> if the SpCellConfig contains the rlf-TimersAndConstants which is set to setup:
3> use value for timers T311 as received in rlf-TimersAndConstants;
2> else if rlf-TimersAndConstants is not configured for this cell group or SpCellConfig contains the rlf-TimersAndConstants which is set to release:
3> use value for timers T311, as included in ue-TimersAndConstants received in SIB1;
1> else
2> if the SpCellConfig contains the rlf-TimersAndConstants:
3> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6;
2> else if rlf-TimersAndConstants is not configured for this cell group:
3> if any DAPS bearer is configured:
4> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIB1;
3> else
4> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
2> if the SpCellConfig contains spCellConfigDedicated:
3> configure the SpCell in accordance with the spCellConfigDedicated;
3> consider the bandwidth part indicated in firstActiveUplinkBWP-Id, if included in the spCellConfigDedicated, to be the active uplink bandwidth part;
3> if the firstActiveDownlinkBWP-Id is included in the spCellConfigDedicated:
4> if the SpCellConfig is included in an RRCReconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated:
5> consider the bandwidth part indicated in firstActiveDownlinkBWP-Id to be the bandwidth part for Radio Link Monitoring, Beam Failure Detection and measurements;
4> else:
5> consider the bandwith part indicated in firstActiveDownlinkBWP-Id to be the active downlink bandwidth part;
3> if any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated:
4> stop timer T310 for the corresponding SpCell, if running;
4> stop timer T312 for the corresponding SpCell, if running;
4> reset the counters N310 and N311.
1> if the SpCellConfig contains the lowMobilityEvaluationConnected:
2> the UE may perform the evaluation of the low mobility criterion for this cell group as specified in 5.7.13.1;
1> if the SpCellConfig contains the goodServingCellEvaluationRLM:
2> the UE may perform the evaluation of the good serving cell quality criterion for this SpCell as specified in 5.7.13.2;
1> if the SpCellConfig contains the goodServingCellEvaluationBFD:
2> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2;
5.3.5.5.8 SCell Release
The UE shall:
1> if the release is triggered by reception of the sCellToReleaseList:
2> for each sCellIndex value included in the sCellToReleaseList:
3> if the current UE configuration includes an SCell with value sCellIndex:
4> release the SCell.
5.3.5.5.9 SCell Addition/Modification
The UE shall:
1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):
2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated;
2> if the sCellState is included:
3> configure lower layers to consider the SCell to be in activated state;
2> else:
3> configure lower layers to consider the SCell to be in deactivated state;
2> for each measId included in the measIdList within VarMeasConfig:
3> if SCells are not applicable for the associated measurement; and
3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:
4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;
2> if the SCellConfig contains the goodServingCellEvaluationBFD:
3> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2.
1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):
2> modify the SCell configuration in accordance with the sCellConfigDedicated;
2> if the sCellToAddModList was received in an RRCReconfiguration message including reconfigurationWithSync, or received in an RRCResume message, or received in an RRCReconfiguration message including reconfigurationWithSync embedded in an RRCResume message or embedded in an RRCReconfiguration message or embedded in an E-UTRA RRCConnectionReconfiguration message or embedded in an E-UTRA RRCConnectionResume message:
3> if the sCellState is included:
4> configure lower layers to consider the SCell to be in activated state;
3> else:
4> configure lower layers to consider the SCell to be in deactivated state.
2> if the SCellConfig contains the goodServingCellEvaluationBFD:
3> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2.
5.3.5.5.10 BH RLC channel release
The IAB-node shall:
1> for each BH-RLC-ChannelID value included in the bh-RLC-ChannelToReleaseList that is part of the current IAB-node configuration within the same cell group (LCH release); or
1> for each BH-RLC-ChannelID value that is to be released as the result of an SCG release according to 5.3.5.4:
2> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3;
2> release the corresponding logical channel.
5.3.5.5.11 BH RLC channel addition/modification
For each BH-RLC-ChannelConfig received in the bh-RLC-ChannelToAddModList IE the IAB-node shall:
1> if the current configuration contains a BH RLC Channel with the received bh-RLC-ChannelID within the same cell group:
2> if reestablishRLC is received:
3> re-establish the RLC entity as specified in TS 38.322 [4];
2> reconfigure the RLC entity or entities in accordance with the received rlc-Config;
2> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig;
1> else (a backhaul logical channel with the given BH-RLC-ChannelID was not configured before within the same cell group):
2> establish an RLC entity in accordance with the received rlc-Config;
2> configure this MAC entity with a logical channel in accordance to the received mac-LogicalChannelConfig.
5.3.5.5.12 Uu Relay RLC channel release
The L2 U2N Relay UE shall:
1> for each Uu-RelayRLC-ChannelID value included in the uu-RelayRLC-ChannelToReleaseList that is part of the current configuration within the same cell group (LCH release):
2> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3;
2> release the corresponding logical channel.
5.3.5.5.13 Uu Relay RLC channel addition/modification
For each Uu-RelayRLC-ChannelConfig received in the uu-RelayRLC-ChannelToAddModList the L2 U2N Relay UE shall:
1> if the current configuration contains a Uu Relay RLC channel with the same uu-RelayRLC-ChannelID within the same cell group:
2> if reestablishRLC is received:
3> re-establish the RLC entity as specified in TS 38.322 [4];
2> reconfigure the RLC entity in accordance with the received rlc-Config;
2> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig;
1> else (a logical channel with the given uu-RelayRLC-ChannelID was not configured before within the same cell group):
2> establish an RLC entity in accordance with the received rlc-Config;
2> configure this MAC entity with a logical channel in accordance to the received mac-LogicalChannelConfig.
5.3.5.6 Radio Bearer configuration
5.3.5.6.1 General
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 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 5.3.5.6.3;
1> if the RadioBearerConfig includes the drb-ToReleaseList:
2> perform DRB release as specified in 5.3.5.6.4;
1> if the RadioBearerConfig includes the drb-ToAddModList:
2> perform DRB addition or reconfiguration as specified in 5.3.5.6.5;
1> if the RadioBearerConfig includes the mrb-ToReleaseList:
2> perform multicast MRB release as specified in 5.3.5.6.6;
1> if the RadioBearerConfig includes the mrb-ToAddModList:
2> perform multicast MRB addition or reconfiguration as specified in 5.3.5.6.7;
1> release all SDAP entities, if any, that have no associated DRB as specified in TS 37.324 [24] clause 5.1.2, 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 TS 37.324 [24] clause 5.1.2, and indicate the release of user plane resources for these MBS multicast sessions to upper layers.
5.3.5.6.2 SRB release
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
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 [5], 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 [5], 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 [10];
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 [10] 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 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 [10], 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 [10], 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 [5];
2> else, if the discardOnPDCP is set:
3> trigger the PDCP entity to perform SDU discard as specified in TS 38.323 [5];
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
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 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 (TS 37.324 [24], clause 5.3.3);
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.
NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration.
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig.
5.3.5.6.5 DRB addition/modification
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 [10];
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 TS 37.324 [24] clause 5.1.1;
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 [24] 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 [5] 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 [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;
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 TS 36.331 [10], clause 5.4.2.3, 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 TS 38.323 [5], clause 5.1.2;
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 [5];
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;
NOTE 1: Void.
NOTE 2: When determining whether a drb-Identity value is part of the current UE configuration, the UE does not distinguish which RadioBearerConfig and DRB-ToAddModList that DRB was originally configured in. To re-associate a DRB with a different key (KeNB to S-KgNB, KgNB to S-KeNB, KgNB to S-KgNB, or vice versa), the network provides the drb-Identity value in the (target) drb-ToAddModList and sets the reestablishPDCP flag. The network does not list the drb-Identity in the (source) drb-ToReleaseList.
NOTE 3: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity.
NOTE 4: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated.
NOTE 5: Ciphering and integrity protection can be enabled or disabled for a DRB. The enabling/disabling of ciphering or integrity protection can be changed only by releasing and adding the DRB.
NOTE 6: In DAPS handover, the UE may perform PDCP entity re-establishment (if reestablishPDCP is set) or the PDCP data recovery (if recoverPDCP is set) for a non-DAPS bearer when indication of successful completion of random access towards target cell is received from lower layers as specified in TS 38.321 [3]. In this case, the UE suspends data transmission and reception for all non-DAPS bearers in the source MCG for duration of the DAPS handover.
5.3.5.6.6 Multicast MRB release
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 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.
NOTE 1: The UE does not consider the message as erroneous if the mrb-ToReleaseList includes any mrb-Identity value that is not part of the current UE configuration.
NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig.
5.3.5.6.7 Multicast MRB addition/modification
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 (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 TS 38.323 [5], clause 5.1.2;
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 [5];
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 that is not part of the UE configuration (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> if at least one multicast MRB was configured with the same mbs-SessionId prior to receiving this reconfiguration message:
3> 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 TS 37.324 [24] clause 5.1.1;
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.
NOTE 1: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. It does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity.
NOTE 2: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated.
NOTE 3: When updating the mrb-Identity, the network ensures new MRBs are listed at the end of the mrb-ToAddModList if they have the same MRB ID as in the existing UE configuration.
5.3.5.7 AS Security key update
The UE shall:
1> if UE is connected to E-UTRA/EPC or E-UTRA/5GC:
2> upon reception of sk-Counter as specified in TS 36.331 [10]:
3> update the S-KgNB key based on the KeNB key and using the received sk-Counter value, as specified in TS 33.401 [30] for EN-DC, or TS 33.501 [11] for NGEN-DC;
3> derive the KRRCenc and KUPenc keys as specified in TS 33.401 [30] for EN-DC, or TS 33.501 [11] for NGEN-DC;
3> derive the KRRCint and KUPint keys as specified in TS 33.401 [30] for EN-DC or TS 33.501 [11] for NGEN-DC.
1> else if this procedure was initiated due to reception of the masterKeyUpdate:
2> if the nas-Container is included in the received masterKeyUpdate:
3> forward the nas-Container to the upper layers;
2> if the keySetChangeIndicator is set to true:
3> derive or update the KgNB key based on the KAMF key, as specified in TS 33.501 [11];
2> else:
3> derive or update the KgNB key based on the current KgNB key or the NH, using the nextHopChainingCount value indicated in the received masterKeyUpdate, as specified in TS 33.501 [11];
2> store the nextHopChainingCount value;
2> derive the keys associated with the KgNB key as follows:
3> if the securityAlgorithmConfig is included in SecurityConfig:
4> derive the KRRCenc and KUPenc keys associated with the cipheringAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];
4> derive the KRRCint and KUPint keys associated with the integrityProtAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501 [11];
3> else:
4> derive the KRRCenc and KUPenc keys associated with the current cipheringAlgorithm, as specified in TS 33.501 [11];
4> derive the KRRCint and KUPint keys associated with the current integrityProtAlgorithm, as specified in TS 33.501 [11].
NOTE 1: Ciphering and integrity protection are optional to configure for the DRBs.
1> else if this procedure was initiated due to reception of the sk-Counter (UE is in NE-DC, or NR-DC, or is configured with SN terminated bearer(s)):
2> derive or update the secondary key (S-KgNB or S-KeNB) based on the KgNB key and using the received sk-Counter value, as specified in TS 33.501 [11];
2> derive the KRRCenc key and the KUPenc key as specified in TS 33.501 [11] using the ciphering algorithms indicated in the RadioBearerConfig associated with the secondary key (S-KgNB or S-KeNB) as indicated by keyToUse;
2> derive the KRRCint key and the KUPint key as specified in TS 33.501 [11] using the integrity protection algorithms indicated in the RadioBearerConfig associated with the secondary key (S-KgNB or S-KeNB) as indicated by keyToUse;
NOTE 2: If the UE has no radio bearer configured with keyToUse set to secondary and receives the sk-Counter without any RadioBearerConfig with keyToUse set to secondary, the UE does not consider it as an invalid reconfiguration.
5.3.5.8 Reconfiguration failure
5.3.5.8.1 Void
5.3.5.8.2 Inability to comply with RRCReconfiguration
NOTE 00: The UE behaviour specified in this clause does not apply to the following, and the UE ignores, i.e. does not take an action on and does not store, the fields that it does not support or does not comprehend:
– The fields in ServingCellConfigCommon that are defined in release-16 and later.
– The fields of searchSpaceMCCH and searchSpaceMTCH in PDCCH-ConfigCommon that are defined in release-17 and later.
The UE shall:
1> if the UE is in (NG)EN-DC:
2> if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB3;
3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration:
4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected;
3> else:
4> continue using the configuration used prior to the reception of RRCReconfiguration message;
3> if MCG transmission is not suspended:
4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends;
3> else:
4> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7, upon which the connection reconfiguration procedure ends;
2> else, if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB1;
3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration:
4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected;
3> else:
4> continue using the configuration used prior to the reception of RRCReconfiguration message;
3> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7, upon which the connection reconfiguration procedure ends.
1> else if RRCReconfiguration is received via NR (i.e., NR standalone, NE-DC, or NR-DC):
2> if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB3;
NOTE 0: This case does not apply in NE-DC.
3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration:
4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected;
3> else:
4> continue using the configuration used prior to the reception of RRCReconfiguration message;
3> if MCG transmission is not suspended:
4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends;
3> else:
4> initiate the connection re-establishment procedure as specified in clause 5.3.7, upon which the connection reconfiguration procedure ends;
2> else if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over the SRB1 or if the upper layers indicate that the nas-Container is invalid:
NOTE 0a: The compliance also covers the SCG configuration carried within octet strings e.g. field mrdc-SecondaryCellGroupConfig. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded SCG configuration or with the combination of (parts of) the MCG and SCG configurations.
NOTE 0b: The compliance also covers the V2X sidelink configuration carried within an octet string, e.g. field sl-ConfigDedicatedEUTRA. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded V2X sidelink configuration.
3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration:
4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected;
3> else:
4> continue using the configuration used prior to the reception of RRCReconfiguration message;
3> if AS security has not been activated:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘other’
3> else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB, SRB2, have not been setup:
4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause ‘RRC connection failure’;
3> else:
4> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the reconfiguration procedure ends;
1> else if RRCReconfiguration is received via other RAT (Handover to NR failure):
2> if the UE is unable to comply with any part of the configuration included in the RRCReconfiguration message or if the upper layers indicate that the nas-Container is invalid:
3> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT.
NOTE 1: The UE may apply above failure handling also in case the RRCReconfiguration message causes a protocol error for which the generic error handling as defined in clause 10 specifies that the UE shall ignore the message.
NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/failure.
NOTE 3: It is up to UE implementation whether the compliance check for an RRCReconfiguration received as part of ConditionalReconfiguration is performed upon the reception of the message or upon CHO, CPA and CPC execution (when the message is required to be applied).
5.3.5.8.3 T304 expiry (Reconfiguration with sync Failure) or T420 expiry (Path switch failure)
The UE shall:
1> if T304 of the MCG expires, or
1> if T420 expires, or,
1> if the target L2 U2N Relay UE (i.e., the UE indicated by targetRelayUE-Identity in the received RRCReconfiguration message containing reconfigurationWithSync indicating path switch as specified in 5.3.5.5.2) changes its serving PCell before path switch:
2> release dedicated preambles provided in rach-ConfigDedicated if configured;
2> release dedicated msgA PUSCH resources provided in rach-ConfigDedicated if configured;
2> if any DAPS bearer is configured, and radio link failure is not detected in the source PCell, according to clause 5.3.10.3:
3> reset MAC for the target PCell and release the MAC configuration for the target PCell;
3> for each DAPS bearer:
4> release the RLC entity or entities as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the target PCell;
4> reconfigure the PDCP entity to release DAPS as specified in TS 38.323 [5];
3> for each SRB:
4> if the masterKeyUpdate was not received:
5> configure the PDCP entity for the source PCell with state variables continuation as specified in TS 38.323 [5];
4> release the PDCP entity for the target PCell;
4> release the RLC entity as specified in TS 38.322 [4], clause 5.1.3, and the associated logical channel for the target PCell;
4> trigger the PDCP entity for the source PCell to perform SDU discard as specified in TS 38.323 [5];
4> re-establish the RLC entity for the source PCell;
3> release the physical channel configuration for the target PCell;
3> discard the keys used in target PCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any;
3> resume suspended SRBs in the source PCell;
3> for each non-DAPS bearer:
4> revert back to the UE configuration used for the DRB or multicast MRB in the source PCell, includes PDCP, RLC states variables, the security configuration and the data stored in transmission and reception buffers in PDCP and RLC entities ;
3> revert back to the UE measurement configuration used in the source PCell;
3> store the handover failure information in VarRLF-Report as described in the clause 5.3.10.5;
3> initiate the failure information procedure as specified in clause 5.7.5 to report DAPS handover failure.
2> else:
3> revert back to the UE configuration used in the source PCell;
3> if the associated T304 was not initiated upon cell selection performed while timer T311 was running, as defined in clause 5.3.7.3:
4> store the handover failure information in VarRLF-Report as described in the clause 5.3.10.5;
3> initiate the connection re-establishment procedure as specified in clause 5.3.7.
NOTE 1: In the context above, "the UE configuration" includes state variables and parameters of each radio bearer.
1> else if T304 of a secondary cell group expires:
2> if MCG transmission is not suspended:
3> release dedicated preambles provided in rach-ConfigDedicated, if configured;
3> release dedicated msgA PUSCH resources provided in rach-ConfigDedicated, if configured;
3> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends;
2> else:
3> if the UE is in NR-DC:
4> initiate the connection re-establishment procedure as specified in clause 5.3.7;
3> else (the UE is in (NG) EN-DC):
4> initiate the connection re-establishment procedure as specified in TS 36.331 [10], clause 5.3.7;
1> else if T304 expires when RRCReconfiguration is received via other RAT (HO to NR failure):
2> reset MAC;
2> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT.
NOTE 2: In this clause, the term ‘handover failure’ has been used to refer to ‘reconfiguration with sync failure’.
5.3.5.9 Other configuration
The UE shall:
1> if the received otherConfig includes the delayBudgetReportingConfig:
2> if delayBudgetReportingConfig is set to setup:
3> consider itself to be configured to send delay budget reports in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to send delay budget reports and stop timer T342, if running.
1> if the received otherConfig includes the overheatingAssistanceConfig:
2> if overheatingAssistanceConfig is set to setup:
3> consider itself to be configured to provide overheating assistance information in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide overheating assistance information and stop timer T345, if running;
1> if the received otherConfig includes the idc-AssistanceConfig:
2> if idc-AssistanceConfig is set to setup:
3> consider itself to be configured to provide IDC assistance information in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide IDC assistance information;
1> if the received otherConfig includes the drx-PreferenceConfig:
2> if drx-PreferenceConfig is set to setup:
3> consider itself to be configured to provide its preference on DRX parameters for power saving for the cell group in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide its preference on DRX parameters for power saving for the cell group and stop timer T346a associated with the cell group, if running;
1> if the received otherConfig includes the maxBW-PreferenceConfig:
2> if maxBW-PreferenceConfig is set to setup:
3> consider itself to be configured to provide its preference on the maximum aggregated bandwidth for power saving for the cell group in accordance with 5.7.4;
3> if otherConfig includes maxBW-PreferenceConfigFR2-2:
4> consider itself to be configured to provide its preference on the maximum aggregated bandwidth for FR2-2 for power saving for the cell group in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide its preference on the maximum aggregated bandwidth for power saving for the cell group and stop timer T346b associated with the cell group, if running;
1> if the received otherConfig includes the maxCC-PreferenceConfig:
2> if maxCC-PreferenceConfig is set to setup:
3> consider itself to be configured to provide its preference on the maximum number of secondary component carriers for power saving for the cell group in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide its preference on the maximum number of secondary component carriers for power saving for the cell group and stop timer T346c associated with the cell group, if running;
1> if the received otherConfig includes the maxMIMO-LayerPreferenceConfig:
2> if maxMIMO-LayerPreferenceConfig is set to setup:
3> consider itself to be configured to provide its preference on the maximum number of MIMO layers for power saving for the cell group in accordance with 5.7.4;
3> if otherConfig includes maxMIMO-LayerPreferenceConfigFR2-2:
4> consider itself to be configured to provide its preference on the maximum number of MIMO layers for FR2-2 for power saving for the cell group in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide its preference on the maximum number of MIMO layers for power saving for the cell group and stop timer T346d associated with the cell group, if running;
1> if the received otherConfig includes the minSchedulingOffsetPreferenceConfig:
2> if minSchedulingOffsetPreferenceConfig is set to setup:
3> consider itself to be configured to provide its preference on the minimum scheduling offset for cross-slot scheduling for power saving for the cell group in accordance with 5.7.4;
3> if otherConfig includes minSchedulingOffsetPreferenceConfigExt:
4> consider itself to be configured to provide its preference on the minimum scheduling offset for 480 kHz SCS and/or 960 kHz SCS for cross-slot scheduling for power saving for the cell group in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide its preference on the minimum scheduling offset for cross-slot scheduling for power saving for the cell group and stop timer T346e associated with the cell group, if running;
1> if the received otherConfig includes the releasePreferenceConfig:
2> if releasePreferenceConfig is set to setup:
3> consider itself to be configured to provide assistance information to transition out of RRC_CONNECTED in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide assistance information to transition out of RRC_CONNECTED and stop timer T346f, if running.
1> if the received otherConfig includes the obtainCommonLocation:
2> include available detailed location information for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation;
NOTE 1: The UE is requested to attempt to have valid detailed location information available whenever sending a measurement report for which it is configured to include available detailed location information. The UE may not succeed e.g. because the user manually disabled the GPS hardware, due to no/poor satellite coverage. Further details, e.g. regarding when to activate GNSS, are up to UE implementation.
1> if the received otherConfig includes the btNameList:
2> if btNameList is set to setup, include available Bluetooth measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation;
1> if the received otherConfig includes the wlanNameList:
2> if wlanNameList is set to setup, include available WLAN measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation;
1> if the received otherConfig includes the sensorNameList:
2> if sensorNameList is set to setup, include available Sensor measurement results for any subsequent measurement report or any subsequent RLF report and SCGFailureInformation;
NOTE 2: The UE is requested to attempt to have valid Bluetooth measurements, WLAN measurements and Sensor measurements whenever sending a measurement report for which it is configured to include these measurements. The UE may not succeed e.g. because the user manually disabled the WLAN or Bluetooth or Sensor hardware. Further details, e.g. regarding when to activate WLAN or Bluetooth or Sensor, are up to UE implementation.
1> if the received otherConfig includes the sl-AssistanceConfigNR:
2> consider itself to be configured to provide configured grant assistance information for NR sidelink communication in accordance with 5.7.4;
1> if the received otherConfig includes the referenceTimePreferenceReporting:
2> consider itself to be configured to provide UE reference time assistance information in accordance with 5.7.4;
1> else:
2> consider itself not to be configured to provide UE reference time assistance information;
1> if the received otherConfig includes the successHO-Config:
2> consider itself to be configured to provide the successful handover information in accordance with 5.7.10.6;
1> else:
2> consider itself not to be configured to provide the successful handover information.
1> if the received otherConfig includes the ul-GapFR2-PreferenceConfig:
2> consider itself to be configured to provide its preference on FR2 UL gap in accordance with 5.7.4;
1> else:
2> consider itself not to be configured to provide its preference on FR2 UL gap;
1> if the received otherConfig includes the musim-GapAssistanceConfig:
2> if musim-GapAssistanceConfig is set to setup:
3> consider itself to be configured to provide MUSIM assistance information for gap preference in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide MUSIM assistance information for gap preference and stop timer T346h, if running;
1> if the received otherConfig includes the musim-LeaveAssistanceConfig:
2> if musim-LeaveAssistanceConfig is set to setup:
3> consider itself to be configured to provide MUSIM assistance information for leaving RRC_CONNECTED in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide MUSIM assistance information for leaving RRC_CONNECTED and stop timer T346g, if running.
1> if the received otherConfig includes the rlm-RelaxationReportingConfig:
2> if rlm-RelaxationReportingConfig is set to setup:
3> consider itself to be configured to report the relaxation state of RLM measurements in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to report the relaxation state of RLM measurements and stop timer T346j associated with the cell group, if running;
1> if the received otherConfig includes the bfd-RelaxationReportingConfig:
2> if bfd-RelaxationReportingConfig is set to setup:
3> consider itself to be configured to report the relaxation state of BFD measurements in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to report the relaxation state of BFD measurements and stop timer T346k associated with the cell group, if running;
1> if the received otherConfig includes the scg-DeactivationPreferenceConfig:
2> if the scg-DeactivationPreferenceConfig is set to setup:
3> consider itself to be configured to provide its SCG deactivation preference in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide its SCG deactivation preference and stop timer T346i, if running.
1> if the received otherConfig includes the propDelayDiffReportConfig:
2> if the propDelayDiffReportConfig is set to setup:
3> consider itself to be configured to provide service link propagation delay difference between serving cell and neighbour cell(s) in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to provide service link propagation delay difference between serving cell and neighbour cell(s).
1> if the received otherConfig includes the rrm-MeasRelaxationReportingConfig:
2> if the rrm-MeasRelaxationReportingConfig is set to setup:
3> consider itself to be configured to report the fulfilment of the criterion for relaxing RRM measurements in accordance with 5.7.4;
2> else:
3> consider itself not to be configured to report the fulfilment of the criterion for relaxing RRM measurements.
5.3.5.9a MUSIM gap configuration
The UE shall:
1> if musim-GapConfig is set to setup:
2> for each musim-GapId included in the received musim-GapToReleaseList:
3> release the periodic MUSIM gap configuration associated with the musim-GapId;
2> for each MUSIM-Gap included in the received musim-GapToAddModList:
3> setup periodic MUSIM gap configuration indicated by the MUSIM-Gap in accordance with the received musim-GapRepetitionAndOffset (providing musim-GapRepetition and Offset value for the following condition) i.e. the first subframe of each periodic MUSIM gap occurs at an SFN and subframe of the NR PCell meeting the following condition:
SFN mod T = FLOOR(Offset/10);
subframe = Offset mod 10;
with T = musim-GapRepetition/10;
2> if musim-AperiodicGap is included:
3> setup aperiodic MUSIM gap configuration indicated by the musim-AperiodicGap in accordance with the received musim-Starting-SFN-AndSubframe, i.e. the first subframe of aperiodic MUSIM gap occurs at an SFN and subframe of the NR PCell meeting the following condition:
SFN = starting-SFN;
subframe = startingSubframe;
1> else if musim-GapConfig is set to release:
2> release the MUSIM gap configuration.
5.3.5.10 MR-DC release
The UE shall:
1> as a result of MR-DC release triggered by E-UTRA or NR:
2> release SRB3, if established, as specified in 5.3.5.6.2;
2> release measConfig associated with SCG;
2> if the UE is configured with NR SCG:
3> release the SCG configuration as specified in clause 5.3.5.4;
3> release otherConfig associated with the SCG, if configured;
3> stop timers T346a, T346b, T346c, T346d, T346e, T346j and T346k associated with the SCG, if running;
3> release bap-Config associated with the SCG, if configured;
3> release the BAP entity as specified in TS 38.340 [47], if there is no configured bap-Config;
3> release iab-IP-AddressConfigurationList associated with the SCG, if configured;
2> else if the UE is configured with E-UTRA SCG:
3> release the SCG configuration as specified in TS 36.331 [10], clause 5.3.10.19 to release the E-UTRA SCG;
5.3.5.11 Full configuration
The UE shall:
1> release/ clear all current dedicated radio configurations except for the following:
– the MCG C-RNTI;
– the AS security configurations associated with the master key;
– the SRB1/SRB2 configurations and DRB/multicast MRB configurations as configured by radioBearerConfig or radioBearerConfig2.
NOTE 1: Radio configuration is not just the resource configuration but includes other configurations like MeasConfig. Radio configuration also includes the RLC bearer configurations as configured by RLC-BearerConfig. In case NR-DC or NE-DC is configured, this also includes the entire NR or E-UTRA SCG configuration which are released according to the MR-DC release procedure as specified in 5.3.5.10.
NOTE 1a: For NR sidelink communication/discovery, the radio configuration includes the sidelink RRC configuration received from the network, but does not include the sidelink RRC reconfiguration and sidelink UE capability received from other UEs via PC5-RRC. In addition, the UE considers the new NR sidelink configurations as full configuration, in case of state transition and change of system information used for NR sidelink communication/discovery.
NOTE 1b: To establish the RLC bearer of SRB(s) after release due to fullConfig, the network can include the srb-Identity within srb-ToAddModList (i.e. the UE applies RLC default configuration) and/or provide rlc-BearerToAddModList of concerned SRB(s) explicitly.
– the logged measurement configuration;
1> if the spCellConfig in the masterCellGroup includes the reconfigurationWithSync:
2> release/ clear all current common radio configurations;
2> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311;
1> else (full configuration after re-establishment or during RRC resume):
2> if the UE is acting as L2 U2N Remote UE:
3> use value for timer T311, as included in ue-TimersAndConstants received in SIB1
2> else:
3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1;
1> if no measConfigAppLayerId is included:
2> inform upper layers about the release of all application layer measurement configurations;
2> discard any received application layer measurement report from upper layers;
2> consider itself not to be configured to send application layer measurement report.
1> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the following:
– parameters for which values are provided in SIB1;
1> apply the default MAC Cell Group configuration as specified in 9.2.2;
1> for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration):
2> establish an RLC entity for the corresponding SRB;
2> apply the default SRB configuration defined in 9.2.1 for the corresponding SRB;
NOTE 2: This is to get the SRBs (SRB1 and SRB2 for reconfiguration with sync and SRB2 for resume and reconfiguration after re-establishment) to a known state from which the reconfiguration message can do further configuration.
1> for each pdu-Session that is part of the current UE configuration:
2> release the SDAP entity (clause 5.1.2 in TS 37.324 [24]);
2> release each DRB associated to the pdu-Session as specified in 5.3.5.6.4;
NOTE 3: This will retain the pdu-Session but remove the DRBs including drb-identity of these bearers from the current UE configuration. Setup of the DRBs within the AS is described in clause 5.3.5.6.5 using the new configuration. The pdu-Session acts as the anchor for associating the released and re-setup DRB. In the AS the DRB re-setup is equivalent with a new DRB setup (including new PDCP and logical channel configurations).
1> for each mbs-SessionId that is part of the current UE configuration:
2> release the SDAP entity (clause 5.1.2 in TS 37.324 [24]);
2> release each multicast MRB associated to the mbs-SessionId as specified in 5.3.5.6.6;
NOTE 4: This will retain the mbs-SessionId but remove the multicast MRBs including mrb-identity of these bearers from the current UE configuration. Setup of the multicast MRBs within the AS is described in clause 5.3.5.6.7 using the new configuration. The mbs-SessionId acts as the anchor for associating the released and re-setup multicast MRB. In the AS the multicast MRB re-setup is equivalent with a new multicast MRB setup (including new PDCP and logical channel configurations).
1> for each pdu-Session that is part of the current UE configuration but not added with same pdu-Session in the drb-ToAddModList:
2> if the procedure was triggered due to reconfiguration with sync:
3> indicate the release of the user plane resources for the pdu-Session to upper layers after successful reconfiguration with sync;
2> else:
3> indicate the release of the user plane resources for the pdu-Session to upper layers immediately;
1> for each mbs-SessionId that is part of the current UE configuration but not added with the same mbs-SessionId in the mrb-ToAddModList:
2> if the procedure was triggered due to reconfiguration with sync:
3> indicate the release of the user plane resources for the mbs-SessionId to upper layers after successful reconfiguration with sync;
2> else:
3> indicate the release of the user plane resources for the mbs-SessionId to upper layers immediately.
5.3.5.12 BAP configuration
The IAB-MT shall:
1> if the bap-Config is set to setup:
2> if no BAP entity is established:
3> establish a BAP entity as specified in TS 38.340 [47];
2> if bap-address is included:
3> configure the BAP entity to use the bap-Address as this node’s BAP address;
2> if defaultUL-BAP-RoutingID is included:
3> configure the BAP entity to apply the default UL BAP routing ID according to the configuration;
2> if defaultUL-BH-RLC-Channel is included
3> configure the BAP entity to apply the default UL BH RLC channel according to the configuration;
2> if flowControlFeedbackType is included:
3> configure the BAP entity to apply the flow control feedback according to the configuration;
1> if the bap-Config is set to release:
2> release the concerned bap-Config;
2> if there is no other configured bap-Config for the MCG or for the SCG
3> release the BAP entity as specified in TS 38.340 [47].
5.3.5.12a IAB Other Configuration
5.3.5.12a.1 IP address management
5.3.5.12a.1.1 IP Address Release
The IAB-MT shall:
1> if the release is triggered by reception of the iab-IP-AddressToReleaseList:
2> for each iab-IP-AddressIndex value included in iab-IP-AddressToReleaseList:
3> release the corresponding IAB-IP-AddressConfiguration.
5.3.5.12a.1.2 IP Address Addition/Modification
The IAB-MT shall:
1> for each iab-IP-AddressIndex value included in the iab-IP-AddressToAddModList that is not part of the current IAB-MT configuration:
2> add the IP address indicated in iab-IP-Address, corresponding to the iab-IP-AddressIndex.
2> if added IP address is iPv4-Address:
3> if iab-IP-Usage is set to f1-C:
4> store the received IPv4 address for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else if iab-IP-Usage is set to f1-U:
4> store the received IPv4 address for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else if iab-IP-Usage is set to non-F1:
4> store the received IPv4 address for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else:
4> store the received IPv4 address for all traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
2> else if iPv6-Address is included:
3> if iab-IP-Usage is set to f1-C:
4> store the received IPv6 address for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else if iab-IP-Usage is set to f1-U:
4> store the received IPv6 address for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else if iab-IP-Usage is set to non-F1:
4> store the received IPv6 address for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else:
4> store the received IPv6 address for all traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
2> else if iPv6-Prefix is included in iab-IP-AddressToAddModList:
3> if iab-IP-Usage is set to f1-C:
4> store the received IPv6 address prefix for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else if iab-IP-Usage is set to f1-U:
4> store the received IPv6 address prefix for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else if iab-IP-Usage is set to non-F1:
4> store the received IPv6 address prefix for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
3> else:
4> store the received IPv6 address prefix for all traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex.
1> for each iab-IP-AddressIndex value included in the iab-IP-AddressToAddModList that is part of the current IAB-MT configuration:
2> modify the IP address configuration(s) in accordance with the IAB-IP-AddressConfiguration corresponding to the iab-IP-AddressIndex.
5.3.5.13 Conditional Reconfiguration
5.3.5.13.1 General
The network configures the UE with one or more candidate target SpCells in the conditional reconfiguration. The UE evaluates the condition of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells which fulfils associated execution condition. The network provides the configuration parameters for the target SpCell in the ConditionalReconfiguration IE.
In NR-DC, the UE may receive two independent conditionalReconfiguration:
– a conditionalReconfiguration associated with MCG, that is included in the RRCReconfiguration message received via SRB1; and
– a conditionalReconfiguration, associated with SCG, that is included in the RRCReconfiguration message received via SRB3, or, alternatively, included within a RRCReconfiguration message embedded in a RRCReconfiguration message received via SRB1.
In this case:
– the UE maintains two independent VarConditionalReconfig, one associated with each conditionalReconfiguration;
– the UE independently performs all the procedures in clause 5.3.5.13 for each conditionalReconfiguration and the associated VarConditionalReconfig, unless explicitly stated otherwise;
– the UE performs the procedures in clause 5.5 for the VarConditionalReconfig associated with the same cell group like the measConfig.
The UE performs the following actions based on a received ConditionalReconfiguration IE:
1> if the ConditionalReconfiguration contains the condReconfigToRemoveList:
2> perform conditional reconfiguration removal procedure as specified in 5.3.5.13.2;
1> if the ConditionalReconfiguration contains the condReconfigToAddModList:
2> perform conditional reconfiguration addition/modification as specified in 5.3.5.13.3;
5.3.5.13.2 Conditional reconfiguration removal
The UE shall:
1> for each condReconfigId value included in the condReconfigToRemoveList that is part of the current UE conditional reconfiguration in VarConditionalReconfig:
2> remove the entry with the matching condReconfigId from the VarConditionalReconfig;
NOTE: The UE does not consider the message as erroneous if the condReconfigToRemoveList includes any condReconfigId value that is not part of the current UE configuration.
5.3.5.13.3 Conditional reconfiguration addition/modification
For each condReconfigId received in the condReconfigToAddModList IE the UE shall:
1> if an entry with the matching condReconfigId exists in the condReconfigToAddModList within the VarConditionalReconfig:
2> if the entry in condReconfigToAddModList includes an condExecutionCond or condExecutionCondSCG;
3> replace condExecutionCond or condExecutionCondSCG within the VarConditionalReconfig with the value received for this condReconfigId;
2> if the entry in condReconfigToAddModList includes an condRRCReconfig;
3> replace condRRCReconfig within the VarConditionalReconfig with the value received for this condReconfigId;
1> else:
2> add a new entry for this condReconfigId within the VarConditionalReconfig;
1> perform conditional reconfiguration evaluation as specified in 5.3.5.13.4;
5.3.5.13.4 Conditional reconfiguration evaluation
The UE shall:
1> for each condReconfigId within the VarConditionalReconfig:
2> if the RRCReconfiguration within condRRCReconfig includes the masterCellGroup including the reconfigurationWithSync:
3> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the masterCellGroup in the received condRRCReconfig to be applicable cell;
2> else if the RRCReconfiguration within condRRCReconfig includes the secondaryCellGroup including the reconfigurationWithSync:
3> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon included in the reconfigurationWithSync within the secondaryCellGroup within the received condRRCReconfig to be applicable cell;
2> if condExecutionCondSCG is configured:
3> in the remainder of the procedure, consider each measId indicated in the condExecutionCondSCG as a measId in the VarMeasConfig associated with the SCG measConfig;
2> if condExecutionCond is configured:
3> if it is configured via SRB3 or configured within nr-SCG or within nr-SecondaryCellGroupConfig (specified in TS 36.331[10]) via SRB1:
4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig;
3> else:
4> in the remainder of the procedure, consider each measId indicated in the condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig;
2> for each measId included in the measIdList within VarMeasConfig indicated in the condExecutionCond or condExecutionCondSCG associated to condReconfigId:
3> if the condEventId is associated with condEventT1, and if the entry condition applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell; or
3> if the condEventId is associated with condEventD1, and if the entry conditions applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig; or
3> if the condEventId is associated with condEventA3, condEventA4 or condEventA5, and if the entry condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig:
4> consider the event associated to that measId to be fulfilled;
3> if the measId for this event associated with the condReconfigId has been modified; or
3> if the condEventId is associated with condEventT1, and if the leaving condition applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell; or
3> if the condEventId is associated with condEventD1, and if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cell during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig; or
3> if the condEventId is associated with condEventA3, condEventA4 or condEventA5, and if the leaving condition(s) applicable for this event associated with the condReconfigId, i.e. the event corresponding with the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfig:
4> consider the event associated to that measId to be not fulfilled;
2> if event(s) associated to all measId(s) within condTriggerConfig for a target candidate cell within the stored condRRCReconfig are fulfilled:
3> consider the target candidate cell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered cell;
3> initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5;
NOTE 1: Up to 2 MeasId can be configured for each condReconfigId. The conditional reconfiguration event of the 2 MeasId may have the same or different event conditions, triggering quantity, time to trigger, and triggering threshold.
NOTE 2: Void.
5.3.5.13.4a Conditional reconfiguration evaluation of SN initiated inter-SN CPC for EN-DC
The UE shall:
1> for each condReconfigurationId within the VarConditionalReconfiguration specified in TS 36.331[10]:
2> for each measId included in the measIdList within VarMeasConfig indicated in the CondReconfigExecCondSCG contained in the triggerConditionSN associated to the condReconfigurationId as specified in TS 36.331[10]:
3> if the entry condition(s) applicable for the event associated with that measId, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event associated with that measId:
4> consider this event to be fulfilled;
3> if the measId for this event has been modified; or
3> if the leaving condition(s) applicable for this event associated with that measId, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event associated with that measId:
4> consider this event associated to that measId to be not fulfilled;
2> if trigger conditions for all events associated with the measId(s) indicated in the CondReconfigExecCondSCG contained in the triggerConditionSN as specified in TS 36.331[10]), are fulfilled:
3> consider the target cell candidate within the RRCReconfiguration message contained in nr-SecondaryCellGroupConfig in the RRCConnectionReconfiguration message, as specified in TS 36.331[10], contained in the stored condReconfigurationToApply, associated to that condReconfigurationId as specified in TS 36.331[10]), clause 5.3.5.9.4, as a triggered cell;
3> initiate the conditional reconfiguration execution, as specified in TS 36.331[10]), clause 5.3.5.9.5;
NOTE: Void.
5.3.5.13.5 Conditional reconfiguration execution
The UE shall:
1> if more than one triggered cell exists:
2> select one of the triggered cells as the selected cell for conditional reconfiguration execution;
1> else:
2> consider the triggered cell as the selected cell for conditional reconfiguration execution;
1> for the selected cell of conditional reconfiguration execution:
2> apply the stored condRRCReconfig of the selected cell and perform the actions as specified in 5.3.5.3;
NOTE: If multiple NR cells are triggered in conditional reconfiguration execution, it is up to UE implementation which one to select, e.g. the UE considers beams and beam quality to select one of the triggered cells for execution.
5.3.5.13a SCG activation
Upon initiating the procedure, the UE shall:
1> if the UE is configured with an SCG after receiving the message for which this procedure is initiated:
2> if the UE was configured with a deactivated SCG before receiving the message for which this procedure is initiated:
3> consider the SCG to be activated;
3> resume performing radio link monitoring on the SCG, if previously stopped;
3> indicate to lower layers to resume beam failure detection on the PSCell, if previously stopped;
3> indicate to lower layers that the SCG is activated.
5.3.5.13b SCG deactivation
Upon initiating the procedure, the UE shall:
1> consider the SCG to be deactivated;
1> indicate to lower layers that the SCG is deactivated;
1> if bfd-and-RLM is configured to true:
2> perform radio link monitoring on the SCG;
2> indicate to lower layers to perform beam failure detection on the PSCell;
1> else:
2> stop radio link monitoring on the SCG;
2> indicate to lower layers to stop beam failure detection on the PSCell;
2> stop timer T310 for this cell group, if running;
2> stop timer T312 for this cell group, if running;
2> reset the counters N310 and N311;
1> if the UE was in RRC_CONNECTED and the SCG was activated before receiving the message for which this procedure is initiated:
2> if SRB3 was configured before the reception of the RRCReconfiguration or of the RRCConnectionReconfiguration and SRB3 is not to be released according to any RadioBearerConfig included in the RRCReconfiguration or in the RRCConnectionReconfiguration as specified in TS 36.331[10]:
3> trigger the PDCP entity of SRB3 to perform SDU discard as specified in TS 38.323 [5];
3> re-establish the RLC entity of SRB3 as specified in TS 38.322 [4].
5.3.5.13b1 SCG activation without SN message
Upon initiating the procedure, the UE shall:
1> if the SCG was deactivated before the reception of the RRCReconfiguration message or the E-UTRA RRCConnectionReconfiguration message for which the procedure invoking this clause is executed:
2> consider the SCG to be activated;
2> indicate to lower layers that the SCG is activated;
2> resume performing radio link monitoring on the SCG, if previously stopped;
2> indicate to lower layers to resume beam failure detection on the PSCell, if previously stopped;
2> if bfd-and-RLM was not configured to true before the reception of the RRCReconfiguration message or the E-UTRA RRCConnectionReconfiguration message for which the procedure invoking this clause is executed; or
2> if lower layers indicate that a Random Access procedure is needed for SCG activation:
3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321 [3].
5.3.5.13c FR2 UL gap configuration
The UE shall:
1> if ul-GapFR2-Config is set to setup:
2> if an FR2 UL gap configuration is already setup, release the FR2 UL gap configuration;
2> setup the FR2 UL gap configuration indicated by the ul-GapFR2-Config in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition:
SFN mod T = FLOOR (gapOffset/10);
if the UGRP is larger than 5ms:
subframe = gapOffset mod 10;
else:
subframe = gapOffset or (gapOffset +5);
with T = CEIL(UGRP/10).
1> else if ul-GapFR2-Config is set to release:
2> release the FR2 UL gap configuration.
NOTE 1: For ul-GapFR2-Config configuration with synchronous CA, the SFN and subframe of a serving cell on FR2 frequency is used in the gap calculation. For ul-GapFR2-Config configuration with asynchronous CA, the SFN and subframe of a serving cell on FR2 frequency indicated by the refFR2-ServCellAsyncCA in ul-GapFR2-Config is used in the gap calculation.
5.3.5.13d Application layer measurement configuration
The UE shall:
1> if measConfigAppLayerToReleaseList is included in appLayerMeasConfig within RRCReconfiguration or RRCResume:
2> for each measConfigAppLayerId value included in the measConfigAppLayerToReleaseList:
3> forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration including any RAN visible application layer measurement configuration;
3> discard any application layer measurement report received from upper layers;
3> consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId.
1> if measConfigAppLayerToAddModList is included in appLayerMeasConfig within RRCReconfiguration or RRCResume:
2> for each measConfigAppLayerId value included in the measConfigAppLayerToAddModList:
3> if measConfigAppLayerContainer is included for the corresponding MeasConfigAppLayer configuration:
4> forward the measConfigAppLayerContainer, the measConfigAppLayerId and the serviceType to upper layers considering the serviceType;
3> consider itself to be configured to send application layer measurement report for the measConfigAppLayerId in accordance with 5.7.16;
3> forward the transmissionOfSessionStartStop, if configured, and measConfigAppLayerId to upper layers considering the serviceType;
3> if ran-VisibleParameters is set to setup and the parameters have been received:
4> forward the measConfigAppLayerId, the ran-VisiblePeriodicity, if configured, the numberOfBufferLevelEntries, if configured, and the reportPlayoutDelayForMediaStartup, if configured, to upper layers considering the serviceType;
3> else if ran-VisibleParameters is set to release:
4> forward the measConfigAppLayerId and inform upper layers about the release of the RAN visible application layer measurement configuration;
3> if pauseReporting is set to true:
4> if at least one segment, but not all segments, of a segmented MeasurementReportAppLayer message containing an application layer measurement report associated with the measConfigAppLayerId has been submitted to lower layers for transmission:
5> submit the remaining segments of the MeasurementReportAppLayer message to lower layers for transmission;
4> suspend submitting application layer measurement report containers to lower layers for the application layer measurement configuration associated with the measConfigAppLayerId;
4> store any previously or subsequently received application layer measurement report containers associated with the measConfigAppLayerId for which no segment, or full message, has been submitted to lower layers for transmission;
3> else if pauseReporting is set to false and if transmission of application layer measurement report containers has previously been suspended for the application layer measurement configuration associated with the measConfigAppLayerId:
4> submit stored application layer measurement report containers to lower layers, if any, for the application layer measurements configuration associated with the measConfigAppLayerId;
4> resume submitting application layer measurement report containers to lower layers for the application layer measurement configuration associated with the measConfigAppLayerId;
NOTE 1: The UE may discard reports when the memory reserved for storing application layer measurement reports becomes full.
NOTE 2: The transmission of RAN visible application layer measurement reports and appLayerSessionStatus is not paused when pauseReporting is set to true.
5.3.5.14 Sidelink dedicated configuration
Upon initiating the procedure, the UE shall:
1> if sl-FreqInfoToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> for each entry included in the received sl-FreqInfoToReleaseList that is part of the current UE configuration:
3> release the related configurations from the stored NR sidelink communication/discovery configurations;
1> if sl-FreqInfoToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> if configured to receive NR sidelink communication:
3> use the resource pool(s) indicated by sl-RxPool for NR sidelink communication reception, as specified in 5.8.7;
2> if configured to transmit NR sidelink communication:
3> use the resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.8.8;
2> if configured to receive NR sidelink discovery:
3> use the resource pool(s) indicated by sl-DiscRxPool or sl-RxPool for NR sidelink discovery reception, as specified in 5.8.13.2;
2> if configured to transmit NR sidelink discovery:
3> use the resource pool(s) indicated by sl-DiscTxPoolSelected, sl-DiscTxPoolScheduling, sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional for NR sidelink discovery transmission, as specified in 5.8.13.3;
2> perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolScheduling, sl-DiscTxPoolSelected, sl-DiscTxPoolScheduling or sl-TxPoolExceptional for NR sidelink communication/discovery transmission, as specified in 5.5.3;
2> use the synchronization configuration parameters for NR sidelink communication/discovery on frequencies included in sl-FreqInfoToAddModList, as specified in 5.8.5;
1> if sl-RadioBearerToReleaseList or sl-RLC-BearerToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> perform sidelink DRB release as specified in 5.8.9.1a.1;
1> if sl-RadioBearerToAddModList or sl-RLC-BearerToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> perform sidelink DRB addition/modification as specified in 5.8.9.1a.2;
1> if sl-ScheduledConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> configure the MAC entity parameters, which are to be used for NR sidelink communication/discovery, in accordance with the received sl-ScheduledConfig;
1> if sl-UE-SelectedConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> configure the parameters, which are to be used for NR sidelink communication/discovery, in accordance with the received sl-UE-SelectedConfig;
1> if sl-MeasConfigInfoToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> for each SL-DestinationIndex included in the received sl-MeasConfigInfoToReleaseList that is part of the current UE configuration:
3> remove the entry with the matching SL-DestinationIndex from the stored NR sidelink measurement configuration information;
1> if sl-MeasConfigInfoToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> for each sl-DestinationIndex included in the received sl-MeasConfigInfoToAddModList that is part of the current stored NR sidelink measurement configuration:
3> reconfigure the entry according to the value received for this sl-DestinationIndex from the stored NR sidelink measurement configuration information;
2> for each sl-DestinationIndex included in the received sl-MeasConfigInfoToAddModList that is not part of the current stored NR sidelink measurement configuration:
3> add a new entry for this sl-DestinationIndex to the stored NR sidelink measurement configuration.
1> if sl-DRX-ConfigUC-ToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> for each SL-DestinationIndex included in the received sl-DRX-ConfigUC-ToReleaseList that is part of the current UE configuration:
3> remove the entry with the matching SL-DestinationIndex from the stored NR sidelink DRX configuration information;
1> if sl-DRX-ConfigUC-ToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> for each sl-DestinationIndex included in the received sl-DRX-ConfigUC-ToAddModList that is part of the current stored NR sidelink DRX configuration:
3> reconfigure the entry according to the value received for this sl-DestinationIndex from the stored NR sidelink DRX configuration information;
2> for each sl-DestinationIndex included in the received sl-DRX-ConfigUC-ToAddModList that is not part of the current stored NR sidelink DRX configuration:
3> add a new entry for this sl-DestinationIndex to the stored NR sidelink DRX configuration.
1> if sl-RLC-ChannelToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> perform PC5 Relay RLC channel release as specified in 5.8.9.7.1;
1> if sl-RLC-ChannelToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2> perform PC5 Relay RLC channel addition/modification as specified in 5.8.9.7.2;
5.3.5.15 L2 U2N Relay UE configuration
5.3.5.15.1 General
The network configures the L2 U2N Relay UE with relay operation related configurations. For each connected L2 U2N Remote UE indicated in sl-L2IdentityRemote, the network provides the configuration parameters used for relaying.
The UE performs the following actions based on a received sl-L2RelayUE-Config:
1> if the sl-L2RelayUE-Config contains the sl-RemoteUE-ToReleaseList:
2> perform the L2 U2N Remote UE release as specified in 5.3.5.15.2;
1> if the sl-L2RelayUE-Config contains the sl-RemoteUE-ToAddModList:
2> perform the L2 U2N Remote UE addition/modification as specified in 5.3.5.15.3;
5.3.5.15.2 L2 U2N Remote UE Release
The L2 U2N Relay UE shall:
1> if the release is triggered by reception of the sl-RemoteUE-ToReleaseList:
2> for each SL-DestinationIdentity value included in the sl-RemoteUE-ToReleaseList:
3> if the current UE has a PC5 RRC connection to a L2 U2N Remote UE with SL-DestinationIdentity:
4> indicate upper layers to trigger PC5 unicast link release.
5.3.5.15.3 L2 U2N Remote UE Addition/Modification
The L2 U2N Relay UE shall:
1> if no SRAP entity has been established:
2> establish a SRAP entity as specified in TS 38.351 [66];
1> for each sl-L2IdentityRemote value included in the sl-RemoteUE-ToAddModList that is not part of the current UE configuration (L2 U2N Remote UE Addition):
2> configure the parameters to SRAP entity in accordance with the sl-SRAP-Config-Relay;
2> if SRB1 is included in sl-MappingToAddModList, and no dedicated PC5 Relay RLC channel configuration associated with SRB1 included in the same RRCReconfiguration message,
3> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 for the SRB1;
1> for each sl-L2IdentityRemote value included in the sl-RemoteUE-ToAddModList that is part of the current UE configuration (L2 U2N Remote UE modification):
2> modify the configuration in accordance with the sl-SRAP-Config-Relay;
5.3.5.16 L2 U2N Remote UE configuration
The network configures the L2 U2N Remote UE with relay operation related configurations, e.g. SRAP configuration.
The UE performs the following actions:
1> if the sl-L2RemoteUE-Config contains the sl-SRAP-ConfigRemote:
2> if no SRAP entity has been established:
3> establish a SRAP entity as specified in TS 38.351 [66];
2> configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigRemote;
1> if the sl-L2RemoteUE-Config contains the sl-UEIdentityRemote:
2> use the value of the sl-UEIdentityRemote as the C-RNTI in the PCell.