Section: 5.8.9.1.2 Actions related to transmission of RRCReconfigurationSidelink message
Content: 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; NOTE 1: Whether/how to set the parameters included in sl-LatencyBoundIUC-Report, sl-CSI-RS-Config, sl-LatencyBoundCSI-Report and sl-ResetConfig is up to UE implementation. 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; NOTE 2: If UE is in RRC_IDLE or in RRC_INACTIVE or out of coverage, or in RRC_CONNECTED and sl-UE-SelectedConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration, it is up to UE implementation to set the sl-DRX-ConfigUC-PC5. 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[ Proximity based Services (ProSe) in the 5G System (5GS) ]  [65], 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[ Proximity based Services (ProSe) in the 5G System (5GS) ]  [65], 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; NOTE 3: If UE is in RRC_IDLE or in RRC_INACTIVE or out of coverage, how to merge the split per-flow QoS on the first/second hop into a per-SLRB level QoS for RLC channel configuration derivation is up to UE implementation. The UE shall submit the RRCReconfigurationSidelink message to lower layers for transmission.