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.8.9 Sidelink RRC procedure  5.8.9.1 Sidelink RRC reconfiguration  5.8.9.1.1 General  5.8.9.1.2 Actions related to transmission of RRCReconfigurationSidelink message  5.8.9.1.3 Reception of an RRCReconfigurationSidelink by the UE  5.8.9.1.8 Reception of an RRCReconfigurationFailureSidelink by the UE  5.8.9.1.9 Reception of an RRCReconfigurationCompleteSidelink by the UE  5.8.9.1.10 Sidelink reset configuration  5.8.9.1a Sidelink radio bearer management  5.8.9.1a.1 Sidelink DRB release  5.8.9.1a.1.1 Sidelink DRB release conditions  5.8.9.1a.1.2 Sidelink DRB release operations  5.8.9.1a.2 Sidelink DRB addition/modification  5.8.9.1a.2.1 Sidelink DRB addition/modification conditions  5.8.9.1a.2.2 Sidelink DRB addition/modification operations  5.8.9.1a.3 Sidelink SRB release  5.8.9.1a.4 Sidelink SRB addition  5.8.9.1a.5 Additional Sidelink RLC Bearer release  5.8.9.1a.5.1 Additional Sidelink RLC Bearer release conditions  5.8.9.1a.5.2 Additional Sidelink RLC Bearer release operation  5.8.9.1a.6 Additional Sidelink RLC Bearer addition/modification  5.8.9.1a.6.1 Additional Sidelink RLC Bearer addition/modification conditions  5.8.9.1a.6.2 Additional Sidelink RLC Bearer addition/modification operation  5.8.9.1b Sidelink Carrier Configuration  5.8.9.1b.1 Sidelink Carrier Release  5.8.9.1b.2 Sidelink Carrier Addition 
...

 

5.8.9  Sidelink RRC procedure  p. 398

5.8.9.1  Sidelink RRC reconfiguration  p. 398

5.8.9.1.1  General  p. 398
Reproduction of 3GPP TS 38.331, Fig. 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful
Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful
Up
Reproduction of 3GPP TS 38.331, Fig. 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure
Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure
Up
The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs or additional sidelink RLC bearer or PC5 Relay RLC channels, to add/modify/release sidelink carrier, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources, to (re)configure CSI reporting latency bound, to (re)configure sidelink DRX, to (re-)configure the latency bound of SL Inter-UE coordination report, and to indicate the SFN-DFN offset.
The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in clause 5.8.9.1.2 on the corresponding PC5-RRC connection in following cases:
  • the release of sidelink DRBs associated with the peer UE, or L2 U2U Relay UE and peer L2 U2U Remote UE in case of L2 U2U Relay operation, as specified in clause 5.8.9.1a.1;
  • the establishment of sidelink DRBs associated with the peer UE, or L2 U2U Relay UE and peer L2 U2U Remote UE in case of L2 U2U Relay operation, as specified in clause 5.8.9.1a.2;
  • the modification for the parameters included in SLRB-Config of sidelink DRBs associated with the peer UE, as specified in clause 5.8.9.1a.2;
  • the release of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.5;
  • the establishment of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.6;
  • the modification for the parameters included in SL-RLC-BearerConfig of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.6;
  • the release of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.1;
  • the establishment of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.2;
  • the modification for the parameters included in SL-RLC-ChannelConfigPC5 of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.2;
  • the release of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.1;
  • the addition of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.2;
  • the modification of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.2;
  • the (re-)configuration of the peer UE to perform NR sidelink measurement and report.
  • the (re-)configuration of the sidelink CSI reference signal resources and CSI reporting latency bound;
  • the (re-)configuration of the peer UE to perform sidelink DRX;
  • the (re-)configuration of the latency bound of SL Inter-UE coordination report;
  • the (re-)configuration of the local UE ID for L2 U2U Remote UEs by L2 U2U Relay UE.
  • the response to the request in a RemoteUEInformationSidelink message for the SFN-DFN offset from the L2 U2N Remote UE;
  • the change in the value of the SFN-DFN offset at the L2 U2N Relay UE.
In RRC_CONNECTED, the UE applies the NR sidelink communications parameters provided in RRCReconfiguration (if any). In RRC_IDLE or RRC_INACTIVE, the UE applies the NR sidelink communications parameters provided in system information (if any). For other cases, UEs apply the NR sidelink communications parameters provided in SidelinkPreconfigNR (if any). When UE performs state transition between above three cases, the UE applies the NR sidelink communications parameters provided in the new state, after acquisition of the new configurations. Before acquisition of the new configurations, UE continues applying the NR sidelink communications parameters provided in the old state.
Up
5.8.9.1.2  Actions related to transmission of RRCReconfigurationSidelink message  p. 400
The UE shall set the contents of RRCReconfigurationSidelink message as follows:
1 >
for each sidelink DRB that is to be released, according to clause 5.8.9.1a.1.1, due to configuration by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or by upper layers:
2 >
set the entry included in the slrb-ConfigToReleaseList corresponding to the sidelink DRB;
1 >
for each sidelink DRB that is to be established or modified, according to clause 5.8.9.1a.2.1, due to receiving sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR:
2 >
if the sidelink DRB is a per-hop sidelink DRB (i.e. the UE is not acting as a L2 U2U Remote UE):
3 >
if a sidelink DRB is to be established:
4 >
assign a new logical channel identity for the logical channel to be associated with the sidelink DRB and set sl-MAC-LogicalChannelConfigPC5 in the SLRB-Config to include the new logical channel identity;
3 >
set the SLRB-Config included in the slrb-ConfigToAddModList, according to the received sl-RadioBearerConfig and sl-RLC-BearerConfig corresponding to the sidelink DRB;
2 >
else if the sidelink DRB is an end-to-end sidelink DRB (i.e. the UE is acting as a L2 U2U Remote UE, and configure peer L2 U2U Remote UE with end-to-end SDAP and PDCP, or provide the L2 Relay UE with the QoS flow to end-to-end DRB mapping):
3 >
if the UE is in RRC_CONNECTED:
4 >
set the SLRB-Config included in the slrb-ConfigToAddModList, according to the received sl-RadioBearerConfig in sl-ConfigDedicatedNR;
3 >
else if the UE is in RRC_IDLE/RRC_INACTIVE:
4 >
set the SLRB-Config included in the slrb-ConfigToAddModList, which is derived by end-to-end QoS profile, according to the sl-RadioBearerConfig in SIB12;
3 >
if the UE is out of coverage:
4 >
set the SLRB-Config included in the slrb-ConfigToAddModList, which is derived by end-to-end QoS profile, according to the sl-RadioBearerConfig in SidelinkPreconfigNR;
1 >
for each additional sidelink RLC bearer that is to be released, according to clause 5.8.9.1a.5.1, due to configuration by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or by upper layers:
2 >
set the entry included in the sl-RLC-BearerToReleaseList corresponding to the additional sidelink RLC bearer;
1 >
for each additional sidelink RLC bearer that is to be established or modified, according to clause 5.8.9.1a.6.1, due to receiving sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR:
2 >
if an additional sidelink RLC bearer is to be established:
3 >
assign a new logical channel identity for the logical channel to be associated with the sidelink DRB and set sl-MAC-LogicalChannelConfigPC5 in the SL-RLC-BearerConfig to include the new logical channel identity;
2 >
set the SL-RLC-BearerConfig included in the sl-RLC-BearerToAddModList, according to the received sl-RadioBearerConfig and sl-RLC-BearerConfig corresponding to the additional sidelink RLC bearer;
1 >
set the entry included in the sl-CarrierToReleaseList corresponding to the sidelink carrier(s) for which MAC entity indicates that the maximum number of consecutive HARQ DTX for a specific destination has been reached;
1 >
set the entry included in the sl-CarrierToAddModList corresponding to the sidelink carrier, taking into account of at least carrier(s) mapped to the sidelink QoS flow(s) configured by the upper layer, carriers configured in sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR, and carrier(s) supported by both UEs;
1 >
set the sl-MeasConfig as follows:
2 >
If the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList/ sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12:
3 >
if UE is in RRC_CONNECTED:
4 >
set the sl-MeasConfig according to stored NR sidelink measurement configuration information for this destination;
3 >
if UE is in RRC_IDLE or RRC_INACTIVE:
4 >
set the sl-MeasConfig according to stored NR sidelink measurement configuration received from SIB12;
2 >
else:
3 >
set the sl-MeasConfig according to the sl-MeasPreConfig in SidelinkPreconfigNR;
1 >
set the sl-LatencyBoundIUC-Report;
1 >
start timer T400 for the destination;
1 >
set the sl-CSI-RS-Config;
1 >
set the sl-LatencyBoundCSI-Report;
1 >
set the sl-ResetConfig;
1 >
set the sl-DRX-ConfigUC-PC5 as follows:
2 >
If the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList/ sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12:
3 >
if UE is in RRC_CONNECTED and if sl-ScheduledConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration:
4 >
set the sl-DRX-ConfigUC-PC5 according to stored NR sidelink DRX configuration information for this destination;
1 >
for each PC5 Relay RLC channel that is to be released due to configuration by sl-ConfigDedicatedNR:
2 >
set the SL-RLC-ChannelID corresponding to the PC5 Relay RLC channel in the sl-RLC-ChannelToReleaseListPC5;
1 >
for each PC5 Relay RLC channel that is to be established or modified due to receiving sl-ConfigDedicatedNR:
2 >
if a PC5 Relay RLC channel is to be established:
3 >
assign a new logical channel identity for the logical channel to be associated with the PC5 Relay RLC channel and set sl-MAC-LogicalChannelConfigPC5 in the SL-RLC-ChannelConfigPC5 to include the new logical channel identity;
2 >
set the SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 according to the received SL-RLC-ChannelConfig corresponding to the PC5 Relay RLC channel, including setting sl-RLC-ChannelID-PC5 to the same value of sl-RLC-ChannelID received in SL-RLC-ChannelConfig;
1 >
if the UE is operating as a L2 U2N Relay UE:
2 >
if the destination UE is a L2 U2N Remote UE that requested the SFN-DFN offset in a previous RemoteUEInformationSidelink message:
3 >
if the SFN-DFN offset has changed since a previous transmission of the RRCReconfigurationSidelink message, or no previous transmission of the RRCReconfigurationSidelink message has occurred since the reception of the RemoteUEInformationSidelink message:
4 >
set the sl-SFN-DFN-Offset according to the relation between the SFN timeline of the PCell and the DFN timeline;
1 >
if the UE is acting as L2 U2U Relay UE, and if the procedure is initiated to configure local ID to the connected L2 U2U Remote UEs:
2 >
if the local ID pair is to be assigned or modified for an end-to-end PC5 connetion, and if both the PC5-RRC connection with L2 U2U Remote UE and the PC5-RRC connection with peer L2 U2U Remote UE are successfully established:
3 >
include an entry in sl-LocalID-PairToAddModList, and set the fields as below:
4 >
according to association between User Info and L2 ID as specified in TS 23.304, set sl-RemoteUE-LocalIdentity to include the new local UE ID, and set sl-RemoteUE-L2Identity to include the source L2 ID of L2 U2U Remote UE in the SL-SRAP-ConfigPC5, if needed;
4 >
according to association between User Info and L2 ID as specified in TS 23.304, set sl-PeerRemoteUE-LocalIdentity to include the new local UE ID, and and set sl-PeerRemoteUE-L2Identity to include the destination L2 ID of peer L2 U2U Remote UE in the SL-SRAP-ConfigPC5, if needed;
2 >
else if the local ID pair is to be released for an end-to-end PC5 connetion:
3 >
include an entry in sl-LocalID-PairToReleaseList, with the value of SL-DestinationIdentity set to the destination L2 ID of the peer L2 U2U Remote UE;
1 >
if the UE is acting as L2 U2U Remote UE (i.e. Tx UE), and if the procedure is initiated to configure the first hop PC5 Relay RLC channel of an end-to-end sidelink DRB to the connected L2 U2N Relay UE (i.e. Rx UE), based on configuration in SIB12 or SidelinkPreconfigNR; or
1 >
if the UE is acting as L2 U2U Relay UE (i.e. Tx UE) and is in RRC_IDLE or in RRC_INACTIVE or OoC, and if the procedure is initiated to configure the second hop PC5 Relay RLC channel to the connected L2 U2N Remote UE (i.e. Rx UE) based on configuration in SIB12 or SidelinkPreconfigNR:
2 >
if a PC5 Relay RLC channel is to be established:
3 >
assign a new RLC channel ID and set sl-RLC-ChannelID-PC5 in the SL-RLC-ChannelConfigPC5 to include the new RLC channel ID;
3 >
assign a new logical channel identity for the logical channel to be associated with the PC5 Relay RLC channel and set sl-MAC-LogicalChannelConfigPC5 in the SL-RLC-ChannelConfigPC5 to include the new logical channel identity;
3 >
if the UE is in RRC_IDLE or in RRC_INACTIVE:
4 >
set the SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 according to the SL-RLC-BearerConfig derived based on the per-hop QoS of the end-to-end SLRB according to SIB12;
3 >
else if the UE is out of coverage:
4 >
set the SL-RLC-ChannelConfigPC5 included in the sl-RLC-ChannelToAddModListPC5 according to the SL-RLC-BearerConfig derived based on the per-hop QoS of the SLRB according to SidelinkPreconfigNR;
The UE shall submit the RRCReconfigurationSidelink message to lower layers for transmission.
Up
5.8.9.1.3  Reception of an RRCReconfigurationSidelink by the UE  p. 402
The UE shall perform the following actions upon reception of the RRCReconfigurationSidelink:
1 >
if the RRCReconfigurationSidelink includes the sl-ResetConfig:
2 >
perform the sidelink reset configuration procedure as specified in clause 5.8.9.1.10;
1 >
if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList:
2 >
for each entry value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration;
3 >
perform the sidelink DRB release procedure, according to clause 5.8.9.1a.1;
1 >
if the RRCReconfigurationSidelink includes the slrb-ConfigToAddModList:
2 >
for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is not part of the current UE sidelink configuration:
3 >
if sl-MappedQoS-FlowsToAddList is included:
4 >
apply the SL-PQFI included in sl-MappedQoS-FlowsToAddList;
3 >
perform the sidelink DRB addition procedure, according to clause 5.8.9.1a.2;
2 >
for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is part of the current UE sidelink configuration:
3 >
if sl-MappedQoS-FlowsToAddList is included:
4 >
add the SL-PQFI included in sl-MappedQoS-FlowsToAddList to the corresponding sidelink DRB;
3 >
if sl-MappedQoS-FlowsToReleaseList is included:
4 >
remove the SL-PQFI included in sl-MappedQoS-FlowsToReleaseList from the corresponding sidelink DRB;
3 >
if the sidelink DRB release conditions as described in clause 5.8.9.1a.1.1 are met:
4 >
perform the sidelink DRB release procedure according to clause 5.8.9.1a.1.2;
3 >
else if the sidelink DRB modification conditions as described in clause 5.8.9.1a.2.1 are met:
4 >
perform the sidelink DRB modification procedure according to clause 5.8.9.1a.2.2;
1 >
if the RRCReconfigurationSidelink includes the sl-RLC-BearerToReleaseList:
2 >
for each entry value included in the sl-RLC-BearerToReleaseList that is part of the current UE sidelink configuration;
3 >
perform the additional sidelink RLC bearer release procedure, according to clause 5.8.9.1a.5;
1 >
if the RRCReconfigurationSidelink includes the sl-RLC-BearerToAddModList:
2 >
for each SL-RLC-BearerConfigIndex value included in the sl-RLC-BearerToAddModList that is not part of the current UE sidelink configuration:
3 >
perform the additional sidelink RLC bearer addition procedure, according to clause 5.8.9.1a.6;
2 >
for each SL-RLC-BearerConfigIndex value included in the sl-RLC-BearerToAddModList that is part of the current UE sidelink configuration:
3 >
perform the additional sidelink RLC bearer modification procedure, according to clause 5.8.9.1a.6;
1 >
if the RRCReconfigurationSidelink includes the sl-CarrierToReleaseList:
2 >
for each entry value included in the sl-CarrierToReleaseList that is part of the current UE sidelink configuration;
3 >
perform the sidelink carrier release procedure, according to clause 5.8.9.1b.1;
1 >
if the RRCReconfigurationSidelink includes the sl-CarrierToAddModList:
2 >
for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is not part of the current UE sidelink configuration:
3 >
perform the sidelink carrier addition procedure, according to clause 5.8.9.1b.2;
2 >
for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is part of the current UE sidelink configuration:
3 >
perform the carrier modification procedure, according to clause 5.8.9.1b.2;
1 >
if the RRCReconfigurationSidelink message includes the sl-MeasConfig:
2 >
perform the sidelink measurement configuration procedure as specified in clause 5.8.10;
1 >
if the RRCReconfigurationSidelink message includes the sl-CSI-RS-Config:
2 >
apply the sidelink CSI-RS configuration;
1 >
if the RRCReconfigurationSidelink message includes the sl-LatencyBoundCSI-Report:
2 >
apply the configured sidelink CSI report latency bound;
1 >
if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToReleaseListPC5:
2 >
for each SL-RLC-ChannelID value included in the sl-RLC-ChannelToReleaseListPC5 that is part of the current UE sidelink configuration;
3 >
perform the PC5 Relay RLC channel release procedure, according to clause 5.8.9.7.1;
1 >
if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToAddModListPC5:
2 >
for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModListPC5 that is not part of the current UE sidelink configuration:
3 >
perform the PC5 Relay RLC channel addition procedure, according to clause 5.8.9.7.2;
2 >
for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModListPC5 that is part of the current UE sidelink configuration:
3 >
perform the PC5 Relay RLC channel modification procedure according to clause 5.8.9.7.2;
1 >
if the RRCReconfigurationSidelink message includes the sl-DRX-ConfigUC-PC5; and
1 >
if the UE accepts the sl-DRX-ConfigUC-PC5:
2 >
configure lower layers to perform sidelink DRX operation according to sl-DRX-ConfigUC-PC5 for the associated destination as defined in TS 38.321;
1 >
if the RRCReconfigurationSidelink message includes the sl-LatencyBoundIUC-Report:
2 >
apply the configured sidelink IUC report latency bound;
1 >
if the RRCReconfigurationSidelink message includes the sl-LocalID-PairToReleaseList or sl-LocalID-PairToAddModList:
2 >
configure SRAP entity to perform NR sidelink L2 U2U relay operation accordingly for the end-to-end PC5 connection peer L2 U2U Remote UE as defined in TS 38.351;
1 >
if the RRCReconfigurationSidelink message includes the sl-MappingToAddModListPC5 or sl-MappingToReleaseListPC5:
2 >
configure lower layers to perform NR sidelink L2 U2U relay operation according to mapping between end-to-end sidelink bearer of L2 U2U Remote UE and egress PC5 Relay RLC channel as defined in TS 38.351;
1 >
if the UE is unable to comply with (part of) the configuration included in the RRCReconfigurationSidelink (i.e. sidelink RRC reconfiguration failure):
2 >
continue using the configuration used prior to the reception of the RRCReconfigurationSidelink message;
2 >
set the content of the RRCReconfigurationFailureSidelink message;
3 >
submit the RRCReconfigurationFailureSidelink message to lower layers for transmission;
1 >
if the RRCReconfigurationSidelink message includes the sl-SFN-DFN-Offset:
2 >
if the sl-SFN-DFN-Offset is set to setup:
3 >
apply the configured SFN-DFN time offset;
2 >
if the sl-SFN-DFN-Offset is set to release:
3 >
release the received sl-SFN-DFN-Offset;
1 >
else:
2 >
set the content of the RRCReconfigurationCompleteSidelink message;
3 >
if the UE rejects the sidelink DRX configuration sl-DRX-ConfigUC-PC5 received from the peer UE:
4 >
include the sl-DRX-ConfigReject in the RRCReconfigurationCompleteSidelink message;
4 >
consider no sidelink DRX to be applied for the corresponding sidelink unicast communication;
3 >
submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission;
Up
5.8.9.1.4  Void
5.8.9.1.5  Void
5.8.9.1.6  Void
5.8.9.1.7  Void
5.8.9.1.8  Reception of an RRCReconfigurationFailureSidelink by the UE  p. 405
The UE shall perform the following actions upon reception of the RRCReconfigurationFailureSidelink:
1 >
stop timer T400 for the destination, if running;
1 >
continue using the configuration used prior to corresponding RRCReconfigurationSidelink message;
1 >
if UE is in RRC_CONNECTED:
2 >
perform the sidelink UE information for NR sidelink communication procedure, as specified in clause 5.8.3.3 or clause 5.10.15 in TS 36.331;
Up
5.8.9.1.9  Reception of an RRCReconfigurationCompleteSidelink by the UE  p. 405
The UE shall perform the following actions upon reception of the RRCReconfigurationCompleteSidelink:
1 >
stop timer T400 for the destination, if running;
1 >
consider the configurations in the corresponding RRCReconfigurationSidelink message to be applied.
2 >
if the RRCReconfigurationCompleteSidelink message includes the sl-DRX-ConfigReject:
3 >
consider no sidelink DRX to be applied for the corresponding sidelink unicast communication.
5.8.9.1.10  Sidelink reset configuration  p. 405
The UE shall:
1 >
release/clear current sidelink radio configuration of this destination received in the RRCReconfigurationSidelink;
1 >
release the sidelink DRBs of this destination, in according to clause 5.8.9.1a.1;
1 >
release the additional sidelink RLC bearer of this destination, if configured, in according to clause 5.8.9.1a.5;
1 >
reset the sidelink specific MAC of this destination.
Up

5.8.9.1a  Sidelink radio bearer management  p. 406

5.8.9.1a.1  Sidelink DRB release  p. 406
5.8.9.1a.1.1  Sidelink DRB release conditions  p. 406
For NR sidelink communication, a sidelink DRB release is initiated in the following cases:
1 >
for groupcast, broadcast and unicast, if slrb-Uu-ConfigIndex (if any) of the sidelink DRB is included in sl-RadioBearerToReleaseList in sl-ConfigDedicatedNR; or
1 >
for groupcast and broadcast, if no sidelink QoS flow with data indicated by upper layers is mapped to the sidelink DRB for transmission, which is (re)configured by receiving SIB12 or SidelinkPreconfigNR; or
1 >
for groupcast, broadcast and unicast, if SL-RLC-BearerConfigIndex (if any) of the associated RLC entity(ies) (i.e., including the additional sidelink RLC bearer if applicable) for the sidelink DRB is included in sl-RLC-BearerToReleaseList/sl-RLC-BearerToReleaseListSizeExt in sl-ConfigDedicatedNR; or
1 >
for unicast, if no sidelink QoS flow with data indicated by upper layers is mapped to the sidelink DRB for transmission, which is (re)configured by receiving SIB12 or SidelinkPreconfigNR, and if no sidelink QoS flow mapped to the sidelink DRB, which is (re)configured by receiving RRCReconfigurationSidelink, has data; or
1 >
for unicast, if SLRB-PC5-ConfigIndex (if any) of the sidelink DRB is included in slrb-ConfigToReleaseList in RRCReconfigurationSidelink or if sl-ResetConfig is included in RRCReconfigurationSidelink; or
1 >
for unicast, when the corresponding PC5-RRC connection is released due to sidelink RLF being detected, according to clause 5.8.9.3; or
1 >
for unicast, when the corresponding PC5-RRC connection is released due to upper layer request according to clause 5.8.9.5.
Up
5.8.9.1a.1.2  Sidelink DRB release operations  p. 406
For each sidelink DRB, whose sidelink DRB release conditions are met as in clause 5.8.9.1a.1.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall:
1 >
for groupcast and broadcast; or
1 >
for unicast, if the sidelink DRB release was triggered after the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or indicated by upper layers:
2 >
release the PDCP entity for NR sidelink communication associated with the sidelink DRB;
2 >
if SDAP entity for NR sidelink communication associated with this sidelink DRB is configured:
3 >
indicate the release of the sidelink DRB to the SDAP entity associated with this sidelink DRB (clause 5.3.3 of TS 37.324);
2 >
release SDAP entities for NR sidelink communication, if any, that have no associated sidelink DRB as specified in clause 5.1.2 of TS 37.324;
1 >
for groupcast and broadcast; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release was triggered due to the configuration received within the sl-ConfigDedicatedNR:
2 >
for each sl-RLC-BearerConfigIndex included in the received sl-RLC-BearerToReleaseList/sl-RLC-BearerToReleaseListSizeExt that is part of the current UE sidelink configuration:
3 >
release the RLC entity and the corresponding logical channel for NR sidelink communication, associated with the sl-RLC-BearerConfigIndex.
1 >
for unicast, if the sidelink DRB release was triggered due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release was triggered due to the configuration received within the SIB12, SidelinkPreconfigNR or indicated by upper layers:
2 >
release the RLC entity and the corresponding logical channel for NR sidelink communication associated with the sidelink DRB;
2 >
perform the sidelink UE information procedure in clause 5.8.3 for unicast if needed.
1 >
if the sidelink radio link failure is detected for a specific destination:
2 >
release the PDCP entity, RLC entity and the logical channel of the sidelink DRB for the specific destination.
Up
5.8.9.1a.2  Sidelink DRB addition/modification  p. 407
5.8.9.1a.2.1  Sidelink DRB addition/modification conditions  p. 407
For NR sidelink communication, a sidelink DRB addition is initiated only in the following cases:
1 >
if any sidelink QoS flow is (re)configured by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR and is to be mapped to one sidelink DRB, which is not established; or
1 >
if any sidelink QoS flow is (re)configured by RRCReconfigurationSidelink and is to be mapped to a sidelink DRB, which is not established;
For NR sidelink communication, a sidelink DRB modification is initiated only in the following cases:
1 >
if any of the sidelink DRB related parameters is changed by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or RRCReconfigurationSidelink for one sidelink DRB, which is established;
Up
5.8.9.1a.2.2  Sidelink DRB addition/modification operations  p. 407
For the sidelink DRB, whose sidelink DRB addition conditions are met as in clause 5.8.9.1a.2.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall:
1 >
for groupcast and broadcast; or
1 >
for unicast, if the sidelink DRB addition was triggered due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB addition was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or indicated by upper layers:
2 >
if an SDAP entity for NR sidelink communication associated with the destination and the cast type of the sidelink DRB does not exist:
3 >
establish an SDAP entity for NR sidelink communication as specified in clause 5.1.1 of TS 37.324;
2 >
(re)configure the SDAP entity in accordance with the sl-SDAP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-SDAP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, associated with the sidelink DRB;
2 >
establish a PDCP entity for NR sidelink communication and configure it in accordance with the sl-PDCP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-PDCP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, associated with the sidelink DRB;
2 >
for a per-hop sidelink DRB (i.e. the UE is not acting as L2 U2U Remote UE):
3 >
establish a RLC entity for NR sidelink communication and configure it in accordance with the sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, associated with sidelink DRB;
3 >
if this procedure was due to the reception of a RRCReconfigurationSidelink message:
4 >
configure the MAC entity with a logical channel in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink associated with the sidelink DRB, and perform the sidelink UE information procedure in clause 5.8.3 for unicast if need;
3 >
else if this procedure was due to the reception of a RRCReconfigurationCompleteSidelink message:
4 >
configure the MAC entity with a logical channel associated with the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR;
3 >
else (i.e. for groupcast/broadcast):
4 >
configure the MAC entity with a logical channel associated with the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR and assign a new LCID to this logical channel.
2 >
for an end-to-end sidelink DRB (i.e. the UE is acting as L2 U2U Remote UE):
3 >
if the UE is in RRC_CONNECTED:
4 >
associate this end-to-end sidelink DRB with the PC5 RLC channel indicated by sl-EgressRLC-ChannelPC5 included in sl-ConfigDedicatedNR, received from RRCReconfiguration;
3 >
else if the UE is in RRC_IDLE or RRC_INACTIVE:
4 >
associate this end-to-end sidelink DRB with the PC5 RLC channel derived by per-SLRB QoS profile of this end-to-end sidelink DRB based on the configuration in SIB12;
3 >
else if the UE is out of coverage:
4 >
associate this end-to-end sidelink DRB with the PC5 RLC channel derived by per-SLRB QoS profile of this end-to-end sidelink DRB based on the configuration in SidelinkPreconfigNR;
For the sidelink DRB, whose sidelink DRB modification conditions are met as in clause 5.8.9.1a.2.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall:
1 >
for groupcast and broadcast; or
1 >
for unicast, if the sidelink DRB modification was triggered due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB modification was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR:
2 >
reconfigure the SDAP entity of the sidelink DRB, in accordance with the sl-SDAP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-SDAP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included;
2 >
reconfigure the PDCP entity of the sidelink DRB, in accordance with the sl-PDCP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-PDCP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included;
2 >
reconfigure the RLC entity of the sidelink DRB, in accordance with the sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included;
2 >
reconfigure the logical channel of the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink or sl-MAC-LogicalChannelConfig received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included.
Up
5.8.9.1a.3  Sidelink SRB release  p. 410
The UE shall:
1 >
if a PC5-RRC connection release for a specific destination is requested by upper layers or AS layer; or
1 >
if the sidelink radio link failure is detected for a specific destination:
2 >
release the PDCP entity, RLC entity and the logical channel of the sidelink SRB for PC5-RRC message of the specific destination;
2 >
consider the PC5-RRC connection is released for the destination.
1 >
if PC5-S transmission for a specific destination is terminated in upper layers:
2 >
release the PDCP entity, RLC entity and the logical channel of the sidelink SRB(s) for PC5-S message of the specific destination;
1 >
if discovery transmission for a specific destination is terminated in upper layers:
2 >
release the PDCP entity, RLC entity and the logical channel of the sidelink SRB4 for discovery message of the specific destination;
Up
5.8.9.1a.4  Sidelink SRB addition  p. 410
The UE shall:
1 >
if transmission of PC5-S message for a specific destination is requested by upper layers for sidelink SRB:
2 >
establish PDCP entity, RLC entity and the logical channel of a sidelink SRB for PC5-S message, as specified in clause 9.1.1.4;
1 >
if transmission of discovery message for a specific destination is requested by upper layers for sidelink SRB:
2 >
establish PDCP entity, RLC entity and the logical channel of a sidelink SRB4 for discovery message, as specified in clause 9.1.1.4;
1 >
if a PC5-RRC connection establishment for a specific destination is indicated by upper layers:
2 >
establish PDCP entity, RLC entity and the logical channel of a sidelink SRB for PC5-RRC message of the specific destination, as specified in clause 9.1.1.4;
2 >
consider the PC5-RRC connection is established for the destination.
Up
5.8.9.1a.5  Additional Sidelink RLC Bearer release  p. 411
5.8.9.1a.5.1  Additional Sidelink RLC Bearer release conditions  p. 411
For NR sidelink communication, additional sidelink RLC bearer release is initiated in the following cases:
1 >
for sidelink DRB, the release conditions are met as in clause 5.8.9.1a.1.1 for the associated sidelink DRB; or
1 >
for sidelink SRB, the release conditions are met as in clause 5.8.9.1a.3 for the associated sidelink SRB; or
1 >
for sidelink DRB, if SL-RLC-BearerConfigIndex (if any) of the sidelink DRB or SRB is included in sl-RLC-BearerToReleaseList in RRCReconfigurationSidelink;
1 >
for sidelink DRB, if SL-RLC-BearerConfigIndex (if any) of the additional Sidelink RLC Bearer is included in sl-RLC-BearerToReleaseListSizeExt in sl-ConfigDedicatedNR and if the SL-TxProfile of the associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsIncompatible; or
1 >
for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer, and if the SL-TxProfile of the associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides not to use PDCP duplication; or
1 >
for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if the SL-TxProfile of the associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides not to use PDCP duplication;
1 >
for sidelink SRB, if UE decides not to use PDCP duplication;
Up
5.8.9.1a.5.2  Additional Sidelink RLC Bearer release operation  p. 411
The UE shall:
1 >
for groupcast and broadcast; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the additional sidelink RLC bearer release was triggered due to the configuration received within the sl-ConfigDedicatedNR:
2 >
for each sl-RLC-BearerConfigIndex included in the received sl-RLC-BearerToReleaseListSizeExt in sl-ConfigDedicatedNR that is part of the current UE sidelink configuration:
3 >
release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication, associated with the sl-RLC-BearerConfigIndex.
1 >
for unicast, if the additional sidelink RLC bearer release was triggered due to the reception of the RRCReconfigurationSidelink message:
2 >
for each SL-RLC-BearerConfigIndex included in received sl-RLC-BearerToReleaseList in RRCReconfigurationSidelink that is part of the current UE sidelink configuration:
3 >
release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication associated with the SL-RLC-BearerConfigIndex;
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the additional sidelink RLC bearer release was triggered due to the configuration received within the SIB12, SidelinkPreconfigNR or indicated by upper layers:
2 >
for each SL-RLC-BearerConfigIndex included in transmitted sl-RLC-BearerToReleaseList in RRCReconfigurationSidelink that is part of the current UE sidelink configuration:
3 >
release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication associated with the SL-RLC-BearerConfigIndex;
Up
5.8.9.1a.6  Additional Sidelink RLC Bearer addition/modification  p. 412
5.8.9.1a.6.1  Additional Sidelink RLC Bearer addition/modification conditions  p. 412
For NR sidelink communication, additional sidelink RLC bearer addition is initiated only in the following cases:
1 >
for unicast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModList in the RRCReconfigurationSidelink for a slrb-PC5-ConfigIndex; or
1 >
for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer, and if the SL-TxProfile of all associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsIncompatible; or
1 >
for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer, and if the SL-TxProfile of at least one associated QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides to use PDCP duplication; or
1 >
for unicast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer; or
1 >
for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if the SL-TxProfile of all associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsIncompatible; or
1 >
for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if the SL-TxProfile of at least one QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides to use PDCP duplication; or
1 >
for unicast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if both UEs support PDCP duplication; or
1 >
for unicast, for sidelink SRB, if UE decides to use PDCP duplication;
For NR sidelink communication, additional sidelink RLC bearer modification is initiated only in the following cases:
1 >
if any of the additional sidelink RLC bearer related parameters is changed by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or RRCReconfigurationSidelink for one additional sidelink RLC bearer, which is established;
Up
5.8.9.1a.6.2  Additional Sidelink RLC Bearer addition/modification operation  p. 412
For the additional Sidelink RLC bearer, whose addition conditions are met as in clause 5.8.9.1a.6.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall:
1 >
for groupcast and broadcast; or
1 >
for unicast, if the additional Sidelink RLC bearer addition was triggered due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, for DRB, after receiving the RRCReconfigurationCompleteSidelink message, if the additional Sidelink RLC bearer addition was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or indicated by upper layers; or
1 >
for unicast, for SRB, after receiving the RRCReconfigurationCompleteSidelink message, if the additional Sidelink RLC bearer addition was decided by UE:
2 >
establish an additional RLC entity for NR sidelink communication and configure it in accordance with each sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR for SL DRB, and as specified in clause 9.1.1.4 for SL SRB;
2 >
if this procedure was for Sidelink DRB:
3 >
if this procedure was due to the reception of a RRCReconfigurationSidelink message:
4 >
configure the MAC entity with a logical channel in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink associated with the sidelink RLC entity;
3 >
else if this procedure was due to the reception of a RRCReconfigurationCompleteSidelink message:
4 >
configure the MAC entity with a logical channel associated with the sidelink RLC entity, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR;
3 >
else (i.e. for groupcast/broadcast):
4 >
configure the MAC entity with a logical channel associated with the sidelink RLC entity, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR and assign a new LCID to this logical channel.
3 >
if the UE is in RRC_CONNECTED:
4 >
indicate the allowed carriers for the two RLC bearers of the DRB, as indicated in sl-AllowedCarriers, to lower layer;
3 >
else:
4 >
indicate the allowed carriers for the two RLC bearers of the DRB, decided by UE implementation, to lower layer, where the carrier indicated in sl-FreqInfoList is used for the RLC bearer if the SL-TxProfile of at least one associated QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible;
2 >
else (i.e., if this procedure was for Sidelink SRB):
3 >
configure the MAC entity with a logical channel associated with the sidelink RLC entity, as specified in clause 9.1.1.4.
3 >
if the UE is in RRC_CONNECTED:
4 >
indicate the allowed carriers for the two RLC bearers of the SRB, as indicated in allowedCarrierFreqSet1/allowedCarrierFreqSet2, to lower layer;
3 >
else:
4 >
indicate the allowed carriers for the two RLC bearers of the SRB, decided by UE implementation, to lower layer, where the carrier indicated in sl-FreqInfoList is used for the RLC bearer if the SL-TxProfile of at least one associated QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible;
For the additional Sidelink RLC bearer, whose modification conditions are met as in clause 5.8.9.1a.6.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall:
1 >
for groupcast and broadcast; or
1 >
for unicast, if the additional Sidelink RLC bearer modification was triggered due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the additional Sidelink RLC bearer modification was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR:
2 >
reconfigure the RLC entity of the sidelink DRB, in accordance with the sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included;
2 >
reconfigure the logical channel of the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink or sl-MAC-LogicalChannelConfig received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included.
Up

5.8.9.1b  Sidelink Carrier Configuration  p. 414

5.8.9.1b.1  Sidelink Carrier Release  p. 414
The UE shall:
1 >
for unicast, if the sidelink carrier release was triggered due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message,
2 >
for each sl-Carrier-Id value included in the sl-CarrierToReleaseList:
3 >
if the current UE configuration includes a sidelink carrier with value sl-Carrier-Id:
4 >
release the sidelink carrier for reception.
5.8.9.1b.1.1  Sidelink Carrier Release Condition  p. 414
5.8.9.1b.1.2  Sidelink Carrier Release Operation  p. 414
5.8.9.1b.2  Sidelink Carrier Addition  p. 414
The UE shall:
1 >
for unicast, if the sidelink carrier addition was triggered due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message,
2 >
for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is not part of the current UE configuration (sidelink carrier addition):
3 >
add the sidelink carrier, corresponding to the sl-Carrier-Id, in accordance with the sl-AbsoluteFrequencyPointA for reception;
1 >
for unicast, if the sidelink carrier was modified due to the reception of the RRCReconfigurationSidelink message; or
1 >
for unicast, after receiving the RRCReconfigurationCompleteSidelink message,
2 >
for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is part of the current UE configuration (sidelink carrier modification):
3 >
modify the sidelink carrier configuration in accordance with sl-AbsoluteFrequencyPointA for reception;
Up
5.8.9.1b.2.1  Sidelink Carrier Addition Condition  p. 414
5.8.9.1b.2.2  Sidelink Carrier Addition Operation  p. 415

Up   Top   ToC