Tech-invite3GPPspaceIETF RFCsSIP
index21222324252627282931323334353637384‑5x

Content for  TS 38.331  Word version:  17.4.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.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.13  Conditional Reconfiguration |R16|p. 116

5.3.5.13.1  Generalp. 116
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.
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;
Up
5.3.5.13.2  Conditional reconfiguration removalp. 116
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;
5.3.5.13.3  Conditional reconfiguration addition/modificationp. 117
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 clause 5.3.5.13.4;
Up
5.3.5.13.4  Conditional reconfiguration evaluationp. 117
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) 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 clause 5.3.5.13.5;
Up
5.3.5.13.4a  Conditional reconfiguration evaluation of SN initiated inter-SN CPC for EN-DC |R17|p. 118
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 executionp. 119
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 clause 5.3.5.3;
Up

5.3.5.13a  SCG activation |R17|p. 119

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 |R17|p. 119

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 |R17|p. 120

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 |R17|p. 120

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 |R17|p. 121

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

5.3.5.14  Sidelink dedicated configuration |R16|p. 122

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 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 >
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 clause 5.5.3;
2 >
use the synchronization configuration parameters for NR sidelink communication/discovery on frequencies included in sl-FreqInfoToAddModList, 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-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-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:
2 >
perform PC5 Relay RLC channel addition/modification as specified in clause 5.8.9.7.2;
Up

5.3.5.15  L2 U2N Relay UE configuration |R17|p. 124

5.3.5.15.1  Generalp. 124
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 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.
Up
5.3.5.15.2  L2 U2N Remote UE Releasep. 124
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/Modificationp. 124
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;
Up

5.3.5.16  L2 U2N Remote UE configuration |R17|p. 125

The network configures the L2 U2N Remote UE with relay operation related configurations, e.g. SRAP configuration.
The L2 U2N Remote UE shall:
1 >
if sl-SRAP-ConfigRemote is set to setup:
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-SRAP-ConfigRemote is set to release:
2 >
release the relay operation related configurations.
Up

Up   Top   ToC