Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 38.331  Word version:  18.2.0

Top   Top   Up   Prev   Next
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.5.17…   5.3.6…   5.3.8…   5.3.13…   5.3.14…   5.4…   5.5…   5.5.3…   5.5.4…   5.5.4.15…   5.5.4.23…   5.5.5…   5.5a…   5.7…   5.7.4…   5.7.8…   5.7.12…   5.8…   5.8.9…   5.8.9.2…   5.8.9.8…   5.8.10…   5.8.11…   5.9…   5.10…   6…   6.2.2…   6-2-2-23…   6-2-2-27…   6-2-2-43…   6-2-2-47…   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-2-341…   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.13 Conditional Reconfiguration  5.3.5.13.1 General  5.3.5.13.2 Conditional reconfiguration removal  5.3.5.13.3 Conditional reconfiguration addition/modification  5.3.5.13.4 Conditional reconfiguration evaluation  5.3.5.13.4a Conditional reconfiguration evaluation of SN initiated inter-SN CPC for EN-DC  5.3.5.13.5 Conditional reconfiguration execution  5.3.5.13.6 Subsequent CPAC reference configuration addition/removal  5.3.5.13.7 sk-Counter configuration addition/modification/removal  5.3.5.13.8 Subsequent CPAC execution  5.3.5.13a SCG activation  5.3.5.13b SCG deactivation  5.3.5.13b1 SCG activation without SN message  5.3.5.13c FR2 UL gap configuration  5.3.5.13d Application layer measurement configuration  5.3.5.14 Sidelink dedicated configuration  5.3.5.15 L2 U2N or U2U Relay UE configuration  5.3.5.15.1 General  5.3.5.15.2 L2 U2N or U2U Remote UE Release  5.3.5.15.3 L2 U2N or U2U Remote UE Addition/Modification  5.3.5.16 L2 U2N or U2U Remote UE configuration  5.3.5.16.1 L2 U2U Relay UE Release  5.3.5.16.2 L2 U2U Relay UE Addition/Modification 
...

 

5.3.5.13  Conditional Reconfiguration  p. 141

5.3.5.13.1  General  p. 141
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 can also configure the UE with one or more candidate target PCells associated with one or more candidate target PSCells. The UE evaluates the conditions for the candidate target PCells and the associated candidate target PSCells in parallel and applies a target configuration that include PCell and PSCell for which the associated execution conditions are fullfiled. If there are multiple candidate PSCells associated with one candidate target PCell, the network provides multiple conditional configurations for the same candidate target PCell, i.e., each configuration contains one MCG configuration (for the same candidate target PCell) and one SCG configuration (for one of the multiple associated candidate PSCells). For this case, the network may also provide a complementary CHO only configuration, i.e., there is execution condition only for candidate PCell.
The network provides the configuration parameters for the target SpCell(s) in the condRRCReconfig.
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.
In EN-DC, the VarConditionalReconfig is associated with the SCG.
In NE-DC and when no SCG is configured, the VarConditionalReconfig is associated with the MCG.
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 clause 5.3.5.13.2;
1 >
if the ConditionalReconfiguration contains the condReconfigToAddModList:
2 >
perform conditional reconfiguration addition/modification as specified in clause 5.3.5.13.3;
1 >
if the ConditionalReconfiguration contains the scpac-ReferenceConfiguration:
2 >
perform subsequent CPAC reference configuration addition/removal as specified in clause 5.3.5.13.6;
1 >
if the ConditionalReconfiguration contains the sk-CounterConfiguration:
2 >
perform sk-CounterList addition/modification/removal as specified in clause 5.3.5.13.7;
1 >
if the ConditionalReconfiguration contains the servingSecurityCellSetId:
2 >
if the current VarServingSecurityCellSetID includes servingSecurityCellSetId:
3 >
replace the servingSecurityCellSetId value within VarServingSecurityCellSetID with the received servingSecurityCellSetID;
2 >
else:
3 >
store the received servingSecurityCellSetId within VarServingSecurityCellSetID.
Up
5.3.5.13.2  Conditional reconfiguration removal  p. 142
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;
Up
5.3.5.13.3  Conditional reconfiguration addition/modification  p. 142
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, condExecutionCondSCG, or condExecutionCondPSCell;
3 >
replace condExecutionCond, condExecutionCondSCG, or condExecutionCondPSCell within the VarConditionalReconfig with the value received for this condReconfigId;
2 >
if the entry in condReconfigToAddModList includes subsequentCondReconfig containing condExecutionCondToAddModList:
3 >
for each condReconfigId received in condExecutionCondToAddModList:
4 >
if an entry with the matching condReconfigId exists in the condExecutionCondToAddModList within VarConditionalReconfig;
5 >
replace the entry in condExecutionCondToAddModList within VarConditionalReconfig with the value received for this condReconfigId;
4 >
else:
5 >
add a new entry in condExecutionCondToAddModList within VarConditionalReconfig with the value received for this condReconfigId;
2 >
if the entry in condReconfigToAddModList includes subsequentCondReconfig containing condExecutionCondToReleaseList:
3 >
for each condReconfigId received in condExecutionCondToReleaseList that is part of current stored condExecutionCondToAddModList within VarConditionalReconfig:
4 >
remove the entry in condExecutionCondToAddModList within VarConditionalReconfig with the value received for this condReconfigId;
2 >
if the entry in condReconfigToAddModList includes an securityCellSetId;
3 >
replace securityCellSetId 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 clause 5.3.5.13.4;
Up
5.3.5.13.4  Conditional reconfiguration evaluation  p. 143
The UE shall:
1 >
for each condReconfigId within the VarConditionalReconfig:
2 >
if the RRCReconfiguration within condRRCReconfig includes the masterCellGroup including the reconfigurationWithSync:
3 >
if the associated condExecutionCondPSCell is configured:
4 >
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; and
4 >
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 nr-SCG within the received condRRCReconfig to be applicable cell;
3 >
else:
4 >
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 >
if 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 is not the PSCell:
4 >
consider the cell 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 the condExecutionCondPSCell is configured:
3 >
in the remainder of the procedure, consider each measId indicated in the condExecutionCondPSCell as a measId in the VarMeasConfig associated with the MCG 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) 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, condExecutionCondSCG, or condExecutionCondPSCell associated to condReconfigId:
3 >
if the condTriggerConfig is not configured with nesEvent:
4 >
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
4 >
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
4 >
if the condEventId is associated with condEventD2, 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
4 >
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:
5 >
consider the event associated to that measId to be fulfilled;
4 >
if the measId for this event associated with the condReconfigId has been modified; or
4 >
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
4 >
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
4 >
if the condEventId is associated with condEventD2, 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
4 >
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:
5 >
consider the event associated to that measId to be not fulfilled;
3 >
else:
4 >
if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition is enabled; and
4 >
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:
5 >
consider the event associated to that measId to be fulfilled;
4 >
if the measId for this event associated with the condReconfigId has been modified; or
4 >
if NES mode indication is received from lower layers, indicating that the NES-specific CHO execution condition is disabled; or
4 >
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:
5 >
consider the event associated to that measId to be not fulfilled;
2 >
if condExecutionCondPSCell is not configured:
3 >
if event(s) associated to all measId(s) within condTriggerConfig for the applicable cell are fulfilled:
4 >
consider the applicable cell, associated to that condReconfigId, as a triggered cell;
4 >
initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5;
2 >
else:
3 >
if event(s) associated to all measId(s), as indicated in the condExecutionCond and condExecutionCondPSCell, within condTriggerConfig for a target candidate cell within the stored condRRCReconfig are fulfilled:
4 >
consider the target candidate PCell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered PCell;
4 >
consider the target candidate PSCell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered PSCell;
4 >
initiate the conditional reconfiguration execution, as specified in 5.3.5.13.5.
2 >
if one of the events associated to the measIds within condTriggerConfig for the applicable cell within the stored condRRCReconfig is not configured with nesEvent, and the other event associated to the measIds within condTriggerConfig for the applicable cell within the stored condRRCReconfig is configured with nesEvent, and at least one of them is fulfilled:
3 >
consider the applicable cell within the stored condRRCReconfig, associated to that condReconfigId, as a triggered cell;
3 >
initiate the conditional reconfiguration execution, as specified in clause 5.3.5.13.5;
Up
5.3.5.13.4a  Conditional reconfiguration evaluation of SN initiated inter-SN CPC for EN-DC  p. 146
The UE shall:
1 >
for each condReconfigurationId within the VarConditionalReconfiguration specified in TS 36.331:
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:
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), 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, contained in the stored condReconfigurationToApply, associated to that condReconfigurationId as specified in clause 5.3.5.9.4 of TS 36.331, as a triggered cell;
3 >
initiate the conditional reconfiguration execution, as specified in clause 5.3.5.9.5 of TS 36.331;
Up
5.3.5.13.5  Conditional reconfiguration execution  p. 146
The UE shall:
1 >
if more than one pair of triggered PCell and associated triggered PSCell exist:
2 >
select one of the triggered PCell(s) and the associated triggered PSCell(s) as the selected cells for conditional reconfiguration execution;
1 >
else if only one pair of triggered PCell and associated triggered PSCell exists:
2 >
consider the triggered PCell and the associated triggered PSCell as the selected cells for conditional reconfiguration execution;
1 >
else 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(s) of conditional reconfiguration execution:
2 >
if the subsequentCondReconfig is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message for the selected cell:
3 >
perform the actions as specified in clause 5.3.5.13.8;
2 >
else:
3 >
apply the stored condRRCReconfig of the selected cell and perform the actions as specified in clause 5.3.5.3;
Up
5.3.5.13.6  Subsequent CPAC reference configuration addition/removal  p. 147
The UE shall:
1 >
if the scpac-ReferenceConfiguration is set to setup:
2 >
if scpac-ReferenceConfiguration exists within the VarConditionalReconfig:
3 >
replace the scpac-ReferenceConfiguration within the VarConditionalReconfig;
2 >
else:
3 >
store the scpac-ReferenceConfiguration within the VarConditionalReconfig;
1 >
else (if scpac-ReferenceConfiguration is set to release):
2 >
remove the scpac-ReferenceConfiguration within the VarConditionalReconfig;
5.3.5.13.7  sk-Counter configuration addition/modification/removal  p. 147
The UE shall:
1 >
for each securityCellSetId received in the sk-CounterConfigToAddModList IE:
2 >
if an entry with the matching securityCellSetId exists in the sk-CounterConfigToAddModList within the VarConditionalReconfig:
3 >
replace the sk-CounterList within the VarConditionalReconfig with the sk-CounterList according to the received securityCellSetId;
2 >
else:
3 >
add a new entry for this securityCellSetId within the VarConditionalReconfig;
1 >
for each securityCellSetId value included in the sk-CounterConfigToRemoveList that is part of the current sk-CounterConfigToAddModList in VarConditionalReconfig:
2 >
remove the entry with the matching securityCellSetId from the sk-CounterConfigToAddModList;
Up
5.3.5.13.8  Subsequent CPAC execution  p. 147
Upon the conditional reconfiguration execution for subsequent CPAC, the UE shall:
1 >
if the selected subsequent CPAC candidate configuration is stored in MCG VarConditionalReconfig:
2 >
release/clear all current dedicated radio configuration except for the following:
  • the MCG C-RNTI;
  • the AS security configurations associated with the master key and the secondary key;
  • for each SRB/DRB in current UE configuration:
    • keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers;
    • release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity;
  • the UE variables VarConditionalReconfig and VarServingSecurityCellSetID.
2 >
release/clear all current common radio configuration;
1 >
else:
2 >
release/clear all current dedicated radio configuration associated with the SCG except for the following:
  • the AS security configurations associated with the secondary key;
  • for each SRB/DRB in current UE configuration which is using the secondary key:
    • keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers;
    • release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity;
  • the UE variables VarConditionalReconfig.
2 >
release/clear all current common radio configuration associated with the SCG;
1 >
use the default values specified in clause 9.2.3 for timers T310, T311 and constants N310, N311 for the cell group for which the subsequent CPAC cell switch procedure is triggered;
1 >
if the securityCellSetId is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message:
2 >
if servingSecurityCellSetId is not included within VarServingSecurityCellSetID; or
2 >
if the value of the securityCellSetId is not equal to the value of servingSecurityCellSetId within VarServingSecurityCellSetID:
3 >
consider the first sk-Counter value in the sk-CounterList associated with the securityCellSetId within the VarConditionalReconfig as the selected sk-Counter value, and perform security key update procedure as specified in clause 5.3.5.7;
3 >
remove the selected sk-Counter value from the sk-CounterList associated with the securityCellSetId within the VarConditionalReconfig;
3 >
if the current VarServingSecurityCellSetID includes servingSecurityCellSetId:
4 >
replace the value of servingSecurityCellSetId within VarServingSecurityCellSetID with the value of securityCellSetId associated with the selected cell;
3 >
else:
4 >
store the servingSecurityCellSetId within VarServingSecurityCellSetID with the value of securityCellSetId associated with the selected cell;
1 >
if the selected subsequent CPAC candidate configuration is stored in the SCG VarConditionalReconfig:
2 >
for each drb-Identity value included in RadioBearerConfig associated with the secondary key (S-KgNB) as indicated by keyToUse that is part of the current UE configuration:
3 >
trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323;
3 >
re-establish the corresponding RLC entity as specified in TS 38.322;
1 >
else:
2 >
for each drb-Identity value included in RadioBearerConfig that is part of the current UE configuration:
3 >
if a different keyToUse value is configured; or
3 >
if a new sk-Counter value has been selected due to the conditional reconfiguration execution for subsequent CPAC:
4 >
trigger the PDCP entity of the bearer to perform PDCP reestablishment as specified in TS 38.323;
3 >
else:
4 >
trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323;
4 >
re-establish the corresponding RLC entity as specified in TS 38.322;
1 >
if scpac-ConfigComplete is not included within the VarConditionalReconfig for the selected cell:
2 >
if the subsequent CPAC candidate cell configuration is stored in MCG VarConditionalReconfig:
3 >
consider scpac-ReferenceConfiguration in MCG VarConditionalReconfig to be the current UE configuration;
2 >
else:
3 >
consider scpac-ReferenceConfiguration in SCG VarConditionalReconfig to be the current SCG configuration;
1 >
apply the stored condRRCReconfig of the selected cell(s) and perform the actions as specified in clause 5.3.5.3;
1 >
release the radio bearer(s) and the associated logical channel(s) that are part of the current UE configuration but not part of the subsequent CPAC candidate configuration for the selected cell, or the subsequent CPAC reference configuration (in case the subsequent CPAC candidate configuration does not include scpac-ConfigComplete).
Up

5.3.5.13a  SCG activation  p. 151

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.
Up

5.3.5.13b  SCG deactivation  p. 151

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:
3 >
trigger the PDCP entity of SRB3 to perform SDU discard as specified in TS 38.323;
3 >
re-establish the RLC entity of SRB3 as specified in TS 38.322.
Up

5.3.5.13b1  SCG activation without SN message  p. 151

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.
Up

5.3.5.13c  FR2 UL gap configuration  p. 152

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.
Up

5.3.5.13d  Application layer measurement configuration  p. 152

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 >
if stored, release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig;
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 clause 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;
4 >
if the memory reserved for storing application layer measurement report containers becomes full while the reporting is paused and if the UE is configured with appLayerMeasPriority:
5 >
discard reports in priority order where reports with the lowest priority are discarded first;
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;
3 >
if configForRRC-IdleInactive is set to true:
4 >
store the received qoe-Reference, measConfigAppLayerId, serviceType, qoe-MeasurementType, qoe-AeaScope, mce-Id, configForRRC-IdleInactive, appLayerMeasPriority, if included, in VarAppLayerIdleConfig;
4 >
if the qoe-AreaScope includes plmn-IdentityList:
5 >
set plmn-IdentityList in VarAppLayerPLMN-ListConfig to include the RPLMN as well as the PLMNs included in plmn-IdentityList;
4 >
else:
5 >
set plmn-IdentityList in VarAppLayerPLMN-ListConfig to include the RPLMN;
Up

5.3.5.14  Sidelink dedicated configuration  p. 154

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/sl-FreqInfoToAddModListExt 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 clause 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 clause 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 clause 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 clause 5.8.13.3;
2 >
if configured to receive sidelink control information for SL-PRS measurement:
3 >
use the resource pool(s) indicated by sl-RxPool and/or sl-PRS-RxPool for SL-PRS reception, as specified in clause 5.8.18.2;
2 >
if configured to transmit SL-PRS:
3 >
use the resource pool(s) indicated by sl-PRS-TxPoolSelectedNormal, sl-PRS-TxPoolScheduling, sl-BWP-PRS-PoolConfig or sl-PRS-TxPoolExceptional for SL-PRS transmission, as specified in clause 5.8.18.3;
2 >
perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolScheduling, sl-PRS-TxPoolSelectedNormal, sl-PRS-TxPoolScheduling, sl-DiscTxPoolSelected, sl-DiscTxPoolScheduling, sl-TxPoolExceptional or sl-PRS-TxPoolExceptional for NR sidelink communication/discovery/positioning transmission, as specified in clause 5.5.3;
2 >
use the synchronization configuration parameters for NR sidelink communication/discovery/positioning on frequencies included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt, as specified in clause 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 clause 5.8.9.1a.1;
1 >
if sl-RLC-BearerToReleaseListSizeExt is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2 >
perform additional sidelink RLC bearer release as specified in 5.8.9.1a.5;
1 >
if sl-RadioBearerToAddModList or sl-RLC-BearerToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2 >
perform sidelink DRB addition/modification as specified in clause 5.8.9.1a.2;
1 >
if sl-RLC-BearerToAddModListSizeExt is included in sl-ConfigDedicatedNR within RRCReconfiguration:
2 >
perform additional sidelink RLC bearer addition/modification as specified in clause 5.8.9.1a.6;
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 clause 5.8.9.7.1;
1 >
if sl-RLC-ChannelToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration or RRCSetup:
2 >
perform PC5 Relay RLC channel addition/modification as specified in clause 5.8.9.7.2;
Up

5.3.5.15  L2 U2N or U2U Relay UE configuration  p. 156

5.3.5.15.1  General  p. 156
The network configures the L2 U2N or U2U Relay UE with relay operation related configurations. For each connected L2 U2N or U2U Remote UE indicated in sl-L2IdentityRemote, the network provides the configuration parameters used for relaying.
The L2 U2N Relay UE shall:
1 >
if sl-L2RelayUE-Config is set to setup:
2 >
if the sl-L2RelayUE-Config contains the sl-RemoteUE-ToReleaseList:
3 >
perform the L2 U2N Remote UE release as specified in clause 5.3.5.15.2;
2 >
if the sl-L2RelayUE-Config contains the sl-RemoteUE-ToAddModList:
3 >
perform the L2 U2N Remote UE addition/modification as specified in clause 5.3.5.15.3;
1 >
else if sl-L2RelayUE-Config is set to release:
2 >
release the relay operation related configurations.
The L2 U2U Relay UE shall:
1 >
if sl-L2RelayUE-Config is set to setup:
2 >
if the sl-L2RelayUE-Config contains the sl-U2U-RemoteUE-ToReleaseList:
3 >
perform the L2 U2U Remote UE release as specified in clause 5.3.5.15.2;
2 >
if the sl-L2RelayUE-Config contains the sl-U2U-RemoteUE-ToAddModList:
3 >
perform the L2 U2U Remote UE addition/modification as specified in clause 5.3.5.15.3;
1 >
else if sl-L2RelayUE-Config is set to release:
2 >
release the related configurations.
Up
5.3.5.15.2  L2 U2N or U2U Remote UE Release  p. 157
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.
The L2 U2U Relay UE shall:
1 >
if the release is triggered by reception of the sl-U2U-RemoteUE-ToReleaseList:
2 >
for each SL-DestinationIdentity value included in the sl-U2U-RemoteUE-ToReleaseList:
3 >
release the configuration associated with the L2 U2U Remote UE.
Up
5.3.5.15.3  L2 U2N or U2U Remote UE Addition/Modification  p. 157
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;
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-ConfigRelay;
2 >
if SRB1 is included in sl-MappingToAddModList, and sl-EgressRLC-ChannelPC5 is configured:
3 >
release SL-RLC1, if established;
3 >
associate the PC5 Relay RLC channel as indicated by sl-EgressRLC-ChannelPC5 with SRB1;
2 >
else: (i.e. SRB1 is not included in sl-MappingToAddModList, or SRB1 is included in sl-MappingToAddModList, but sl-EgressRLC-ChannelPC5 is not configured)
3 >
if SL-RLC1 is not established:
4 >
apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with 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-ConfigRelay;
The L2 U2U Relay UE shall:
1 >
if no SRAP entity has been established:
2 >
establish a SRAP entity as specified in TS 38.351;
1 >
for each target L2 U2U Remote UE indicated in sl-L2IdentityRemote value included in the sl-U2U-RemoteUE-ToAddModList that is not part of the current UE configuration (target L2 U2U Remote UE Addition):
2 >
for each source L2 U2U Remote UE indicated in sl-SourceUE-Identity in accordance with one entry of the sl-SourceRemoteUE-ToAddModList, configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U;
1 >
for each target L2 U2U Remote UE indicated in sl-L2IdentityRemote value included in the sl-U2U-RemoteUE-ToAddModList that is part of the current UE configuration (target L2 U2U Remote UE modification):
2 >
for each source L2 U2U Remote UE indicated in sl-SourceUE-Identity included in the sl-SourceRemoteUE-ToReleaseList (source L2 U2U Remote UE Release):
3 >
release the configuration associated with the source L2 U2U Remote UE;
2 >
for the source L2 U2U Remote UE indicated in sl-SourceUE-Identity included in the sl-SourceRemoteUE-ToAddModList that is not part of the current UE configuration (source L2 U2U Remote UE Addition):
3 >
configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U;
2 >
for the source L2 U2U Remote UE indicated in sl-SourceUE-Identity included in the sl-SourceRemoteUE-ToAddModList that is part of the current UE configuration (source L2 U2U Remote UE modification):
3 >
modify the configuration in accordance with the sl-SRAP-ConfigU2U;
Up

5.3.5.16  L2 U2N or U2U Remote UE configuration  p. 158

The network configures the L2 U2N or U2U Remote UE with relay operation related configurations, e.g. SRAP configuration.
The L2 U2N Remote UE shall:
1 >
if sl-L2RemoteUE-Config is set to setup or received from RRCSetup message:
2 >
if the sl-L2RemoteUE-Config contains the sl-SRAP-ConfigRemote:
3 >
if no SRAP entity has been established:
4 >
establish a SRAP entity as specified in TS 38.351;
3 >
configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigRemote;
3 >
if SRB1 is included in sl-MappingToAddModList, and sl-EgressRLC-ChannelPC5 is configured:
4 >
release SL-RLC1, if established;
4 >
associate the PC5 Relay RLC channel as indicated by sl-EgressRLC-ChannelPC5 with SRB1;
3 >
else: (i.e. SRB1 is not included in sl-MappingToAddModList, or SRB1 is included in sl-MappingToAddModList, but sl-EgressRLC-ChannelPC5 is not configured)
4 >
if SL-RLC1 is not established:
5 >
apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1;
2 >
if the sl-L2RemoteUE-Config contains the sl-UEIdentityRemote:
3 >
use the value of the sl-UEIdentityRemote as the C-RNTI in the PCell.
1 >
else if sl-L2RemoteUE-Config is set to release:
2 >
release the relay operation related configurations.
The L2 U2U Remote UE shall:
1 >
if sl-L2RemoteUE-Config is set to setup:
2 >
if the sl-L2RemoteUE-Config contains the sl-U2U-RelayUE-ToReleaseList:
3 >
perform the L2 U2U Relay UE release as specified in clause 5.3.5.16.1;
2 >
if the sl-L2RemoteUE-Config contains the sl-U2U-RelayUE-ToAddModList:
3 >
perform the L2 U2U Relay UE addition/modification as specified in clause 5.3.5.16.2;
1 >
else if sl-L2RemoteUE-Config is set to release:
2 >
release the related configurations.
Up
5.3.5.16.1  L2 U2U Relay UE Release  p. 159
The L2 U2U Relay UE shall:
1 >
if the release is triggered by reception of the sl-U2U-RelayUE-ToReleaseList:
2 >
for each SL-DestinationIdentity value included in the sl-U2U-RelayUE-ToReleaseList:
3 >
release the configuration associated with the L2 U2U Relay UE.
5.3.5.16.2  L2 U2U Relay UE Addition/Modification  p. 159
The L2 U2U Remote UE shall:
1 >
if no SRAP entity has been established:
2 >
establish a SRAP entity as specified in TS 38.351;
1 >
for each L2 U2U Relay UE indicated in sl-L2IdentityRelay value included in the sl-U2U-RelayUE-ToAddModList that is not part of the current UE configuration (L2 U2U Relay UE Addition):
2 >
for peer target L2 U2U Remote UE indicated in sl-TargetUE-Identity in accordance with one entry of the SL-PeerRemoteUE-ToAddModList, configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U;
1 >
for each L2 U2U Relay UE indicated in sl-L2IdentityRelay value included in the sl-U2U-RelayUE-ToAddModList that is part of the current UE configuration (L2 U2U Relay UE modification):
2 >
for each peer target L2 U2U Remote UE included in the sl-PeerRemoteUE-ToReleaseList (peer target L2 U2U Remote UE Release):
3 >
release the configuration associated with the peer target L2 U2U Remote UE;
2 >
for the peer target L2 U2U Remote UE indicated in sl-TargetUE-Identity included in the sl-PeerTargetRemoteUE-ToAddModList that is not part of the current UE configuration (peer target L2 U2U Remote UE Addition):
3 >
configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U;
2 >
for the peer target L2 U2U Remote UE indicated in sl-TargetUE-Identity included in the sl-PeerTargetRemoteUE-ToAddModList that is part of the current UE configuration (peer target L2 U2U Remote UE modification):
3 >
modify the configuration in accordance with the sl-SRAP-ConfigU2U;
Up

Up   Top   ToC