Content for TS 38.331 Word version: 17.4.0

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

5.3.5.7 AS Security key update 5.3.5.8 Reconfiguration failure 5.3.5.8.2 Inability to comply with RRCReconfiguration 5.3.5.8.3 T304 expiry (Reconfiguration with sync Failure) or T420 expiry (Path switch failure) 5.3.5.9 Other configuration 5.3.5.9a MUSIM gap configuration 5.3.5.10 MR-DC release 5.3.5.11 Full configuration 5.3.5.12 BAP configuration 5.3.5.12a IAB Other Configuration
...

5.3.5.7 AS Security key update p. 102

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:

3 >

update the S-KgNB key based on the KeNB key and using the received sk-Counter value, as specified in TS 33.401 for EN-DC, or TS 33.501 for NGEN-DC;

3 >

derive the KRRCenc and KUPenc keys as specified in TS 33.401 for EN-DC, or TS 33.501 for NGEN-DC;

3 >

derive the KRRCint and KUPint keys as specified in TS 33.401 for EN-DC or TS 33.501 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;

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;

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;

4 >

derive the KRRCint and KUPint keys associated with the integrityProtAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501;

3 >

else:

4 >

derive the KRRCenc and KUPenc keys associated with the current cipheringAlgorithm, as specified in TS 33.501;

4 >

derive the KRRCint and KUPint keys associated with the current integrityProtAlgorithm, as specified in TS 33.501.

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;

2 >

derive the KRRCenc key and the KUPenc key as specified in TS 33.501 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 using the integrity protection algorithms indicated in the RadioBearerConfig associated with the secondary key (S-KgNB or S-KeNB) as indicated by keyToUse;

5.3.5.8 Reconfiguration failure p. 103

5.3.5.8.1 Void

5.3.5.8.2 Inability to comply with RRCReconfiguration p. 103

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 clause 5.3.7 of TS 36.331, 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 clause 5.3.7 of TS 36.331, 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;

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:

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 clause 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 clause 5.3.11, with release cause 'RRC connection failure';

3 >

else:

4 >

initiate the connection re-establishment procedure as specified in clause 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.

5.3.5.8.3 T304 expiry (Reconfiguration with sync Failure) or T420 expiry (Path switch failure) p. 105

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 clause 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 clause 5.1.3 of TS 38.322, and the associated logical channel for the target PCell;

4 >

reconfigure the PDCP entity to release DAPS as specified in TS 38.323;

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;

4 >

release the PDCP entity for the target PCell;

4 >

release the RLC entity as specified in clause 5.1.3 of TS 38.322, 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;

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.

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 clause 5.3.7 of TS 36.331;

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.

5.3.5.9 Other configuration p. 107

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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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;

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;

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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 clause 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 |R17| p. 111

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 p. 111

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 clause 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, 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 clause 5.3.10.19 of TS 36.331 to release the E-UTRA SCG;

5.3.5.11 Full configuration p. 112

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, PC5 Relay RLC channel as configured by SL-RLC-ChannelConfig, and Uu Relay RLC channel as configured by Uu-RelayRLC-ChannelConfig. 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 clause 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 >

if sl-PathSwitchConfig was included in reconfigurationWithSync:

3 >

use the default values specified in clause 9.2.3 for timer T311;

2 >

else:

3 >

use the default values specified in clause 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 >

if the UE is acting as L2 U2N Remote UE at the target side during reconfiguration with sync, or after re-establishment, or during RRC resume:

2 >

apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1;

1 >

else:

2 >

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;

2 >

apply the default MAC Cell Group configuration as specified in clause 9.2.2;

2 >

for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration):

3 >

establish an RLC entity for the corresponding SRB;

3 >

apply the default SRB configuration defined in clause 9.2.1 for the corresponding SRB;

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

2 >

release each DRB associated to the pdu-Session as specified in clause 5.3.5.6.4;

1 >

for each mbs-SessionId that is part of the current UE configuration and associated to a multicast MRB:

2 >

release the SDAP entity (clause 5.1.2 in TS 37.324);

2 >

release each multicast MRB associated to the mbs-SessionId as specified in clause 5.3.5.6.6;

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 |R16| p. 114

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;

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.

5.3.5.12a IAB Other Configuration |R16| p. 114

5.3.5.12a.1 IP address management p. 114

5.3.5.12a.1.1 IP Address Release p. 114

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 p. 115

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.