12.2.6 Inter-carrier concurrent operation / Sidelink Reconfiguration via PC5 RRC

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

12.2.6.1 Inter-carrier concurrent operation / Sidelink Reconfiguration via PC5 RRC / SL DRB management / Initiating UE side

12.2.6.1.1 Test Purpose (TP)

(1)

with { UE in NR RRC_CONNECTED state and having established PC5-RRC connection with peer UE }

ensure that {

when { UE is indicated by upper layer to establish a unicast SL DRB }

then { UE sends a RRCReconfigurationSidelink message to peer UE to indicate SL DRB addition. After receiving RRCReconfigurationCompleteSidelink message from peer UE, UE establishes the SL DRB }

}

(2)

with { UE in NR RRC_CONNECTED state and having established PC5-RRC connection with peer UE and having established a unicast SL DRB }

ensure that {

when { UE is indicated by upper layer to release the unicast SL DRB }

then { UE sends a RRCReconfigurationSidelink message to peer UE to indicate SL DRB release. After receiving RRCReconfigurationCompleteSidelink message from peer UE, UE releases the SL DRB }

}

12.2.6.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.8.9.1.1, 5.8.9.1.2, 5.8.9.1a.2.1 and 5.8.9.1a.1.1. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.8.9.1.1]

…

The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in sub-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, as specified in sub-clause 5.8.9.1a.1;

– the establishment of sidelink DRBs associated with the peer UE, as specified in sub-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 sub-clause 5.8.9.1a.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.

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.

[TS 38.331, clause 5.8.9.1.2]

The UE shall set the contents of RRCReconfigurationSidelink message as follows:

1> for each sidelink DRB that is to be released, according to sub-clause 5.8.9.1a.1.1, due to configuration by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or by upper layers:

2> set the SLRB-PC5-ConfigIndex included in the slrb-ConfigToReleaseList corresponding to the sidelink DRB;

1> for each sidelink DRB that is to be established or modified, according to sub-clause 5.8.9.1a.2.1, due to receiving sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR:

2> set the SLRB-Config included in the slrb-ConfigToAddModList, according to the received sl-RadioBearerConfig and sl-RLC-BearerConfig corresponding to the sidelink DRB;

…

1> start timer T400 for the destination associated with the sidelink DRB;

…

The UE shall submit the RRCReconfigurationSidelink message to lower layers for transmission.

[TS 38.331, clause 5.8.9.1a.2.1]

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;

…

[TS 38.331, clause 5.8.9.1a.1.1]

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, broadcast and unicast, if SL-RLC-BearerConfigIndex (if any) of the sidelink DRB is included in sl-RLC-BearerToReleaseList 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.

12.2.6.1.3 Test description

12.2.6.1.3.1 Pre-test conditions

System Simulator:

– SS-NW

– NR Cell 1

– System information combination 14 as defined in TS 38.508-1 [4] clause 4.4.3.1 is used in NR Cell 1.

– NR-SS-UE

– NR-SS-UE1: Operating as NR sidelink communication transmitting and receiving device and uses GNSS as the synchronization reference source.

– GNSS simulator

– The GNSS simulator is started and configured for Scenario #1.

UE:

– UE is authorised to perform NR sidelink communication.

– The UE is equipped with a USIM Configuration FFS as defined in TS 38.508 [4] Table FFS.

– The UE uses GNSS as the synchronization reference source.

Preamble:

– The UE is in state 3N-B RRC_CONNECTED_with_SL and Test Loop Function (On) with UE test loop mode E as defined in TS 38.508-1 [4] subclause 4.4A on NR Cell 1, using generic parameters Sidelink (On), Cast Type (Unicast), GNSS Sync (On).

12.2.6.1.3.2 Test procedure sequence

Table 12.2.6.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is configured by upper layer to establish a unicast SL DRB. Note: This step is triggered by MMI or AT command	–	–	–	–
2	The UE sends a RRCReconfigurationSidelink message to establish a unicast mode SL DRB.	–>	PC5-RRC: RRCReconfigurationSidelink	1	P
3	The NR-SS-UE1 sends a RRCReconfigurationSidelinkComplete message.	<–	PC5-RRC: RRCReconfigurationSidelinkComplete	–	–
4	The NR-SS-UE1 transmits the data on SL DRB to the UE. NOTE: it is expected that the UE shall receive the data – if they were received is checked in step 6.	–	–	–	–
5	The NR-SS-UE1 transmits an UE TEST LOOP NR SIDELINK PACKET COUNTER REQUEST message.	<–	UE TEST LOOP NR SIDELINK PACKET COUNTER REQUEST	–	–
6	Check: Does the UE respond with UE TEST LOOP NR SIDELINK PACKET COUNTER RESPONSE?	–>	UE TEST LOOP NR SIDELINK PACKET COUNTER RESPONSE	–	–
7	The UE is configured by upper layer to release the unicast SL DRB added by step 2. Note: This step is triggered by MMI or AT command	–	–	–	–
8	The UE sends a RRCReconfigurationSidelink message to release the unicast mode SL DRB added by step 2.	–>	PC5-RRC: RRCReconfigurationSidelink	2	P
9	The NR-SS-UE1 sends a RRCReconfigurationSidelinkComplete message.	<–	PC5-RRC: RRCReconfigurationSidelinkComplete	–	–

12.2.6.1.3.3 Specific message contents

FFS