12.1 PC5-only operation

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

12.1.1 PC5-only operation / Sidelink communication

12.1.1.1

12.1.1.2 PC5-only operation / Sidelink communication / Reception

12.1.1.2.1 Test Purpose (TP)

(1)

with { UE being authorized for performing NR sidelink Communication }

ensure that {

when { UE is configured by upper layer to perform NR sidelink reception }

then { UE is able to monitor NR sidelink transmission using sl-RxPool included in pre-configuration }

}

12.1.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.7. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.7]

A UE capable of NR sidelink communication that is configured by upper layers to receive NR sidelink communication shall:

1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met:

2> if the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList in RRCReconfiguration message or sl-FreqInfoList included in SIB12:

3> if the UE is configured with sl-RxPool included in RRCReconfiguration message with reconfigurationWithSync (i.e. handover):

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated by sl-RxPool;

3> else if the cell chosen for NR sidelink communication provides SIB12:

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated by sl-RxPool in SIB12;

2> else:

3> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources that were preconfigured by sl-RxPool in SL-PreconfigurationNR, as defined in sub-clause 9.3;

12.1.1.2.3 Test description

12.1.1.2.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– 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 below information in UE or in a USIM containing default values (as per TS 38.508-1 [4] clause 4.8.3.3.3).

Table 12.1.1.2.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

Service n°119 (V2X) supported

EFVST

As per TS 38.508-1 [4] clause 4.8.3.3.3

EFV2XP_PC5

SL-PreconfigurationNR field as defined in TS 38.508-1 [4], table 4.10.1-1, except SL-BWP-PoolConfigCommon field as defined in table 12.1.1.2.3.3-1

Preamble:

– The UE is in state 0-A as defined in TS 38.508-1 [4], Sidelink (On), Cast Type (Unicast), GNSS Sync (On).

12.1.1.2.3.2 Test procedure sequence

Table 12.1.1.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power on the UE.

–

–

–

–

2

Trigger UE to reset or clear the current UTC time that has been calculated from GNSS.

NOTE: The UTC time can be reset or clear on the UE using AT command (+CUTCR).

–

–

–

–

3

The NR-SS-UE1 transmits a DIRECT LINK ESTABLISHMENT REQUEST message using the pool of resources that were preconfigured by sl-RxPool in SL-PreconfigurationNR.

<–

PC5-S: DIRECT LINK ESTABLISHMENT REQUEST

–

–

4

Check: Does the UE transmit a DIRECT LINK SECURITY MODE COMMAND message.

–>

PC5-S: DIRECT LINK SECURITY MODE COMMAND

1

P

5

The NR-SS-UE1 transmits a DIRECT LINK SECURITY MODE COMPLETE message.

<–

PC5-S: DIRECT LINK SECURITY MODE COMPLETE

–

–

6

The UE transmits a DIRECT LINK ESTABLISHMENT ACCEPT message.

–>

PC5-S: DIRECT LINK ESTABLISHMENT ACCEPT

–

–

7

The NR-SS-UE1 transmits an RRCReconfigurationSidelink message.

<–

PC5-RRC: RRCReconfigurationSidelink

–

–

8

Check: Does the UE transmit an RRCReconfigurationSidelinkComplete message?

–>

PC5-RRC: RRCReconfigurationSidelinkComplete

1

P

12.1.1.2.3.3 Specific message contents

Table 12.1.1.2.3.3-1: SL-BWP-PoolConfigCommon (Preamble)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-4 with condition RXPOOL

12.1.2 PC5-only operation / Sidelink synchronization related procedure

12.1.2.1 PC5-only operation / Sidelink synchronization related procedure / Synchonization reference source (re-)selection

12.1.2.1.1 Test Purpose (TP)

(1)

with { UE is configured by upper layer to perform sidelink transmission and is configured with sl-SyncPriority = gnss in pre-configuration. }

ensure that {

when { GNSS signal is reliable and a SyncRef UE which directly synchronized to GNSS is detected. }

then { UE selects GNSS as synchonization reference source. }

}

(2)

with { UE is configured by upper layer to perform sidelink transmission and is configured with sl-SyncPriority = gnss in pre-configuration. }

ensure that {

when { Two SyncRef UEs, one directly synchronized to GNSS and the other indirectly synchronized to GNSS, are detected. }

then { UE selects the SyncRef UE directly synchronized to GNSS as synchonization reference source. }

}

(3)

with { UE is configured by upper layer to perform sidelink transmission and is configured with sl-SyncPriority = gnss in pre-configuration. }

ensure that {

when { Two SyncRef UEs, one indirectly synchronized to GNSS and the other neither directly nor indirectly synchronized to GNSS, are detected. }

then { UE selects the SyncRef UE indirectly synchronized to GNSS as synchonization reference source. }

}

(4)

with { UE is configured by upper layer to perform sidelink transmission and is configured with sl-SyncPriority = gnss in pre-configuration. }

ensure that {

when { A SyncRef UE which neither directly nor indirectly synchronized to GNSS is detected. }

then { UE selects the SyncRef UE which neither directly nor indirectly synchronized to GNSS as synchonization reference source. }

}

(5)

with { UE is configured by upper layer to perform sidelink transmission, and is configured with sl-SyncPriority = gnss in pre-configuration. }

ensure that {

when { No SyncRef UE is detectable. }

then { UE uses its internal clock as synchronization reference source. }

}

12.1.2.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.2. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.8.2]

The UE shall perform NR sidelink communication operation only if the conditions defined in this clause are met:

…

1> if the UE has no serving cell (RRC_IDLE);

[TS 38.331, clause 5.8.5.1]

Figure 5.8.5.1-1: Synchronisation information transmission for NR sidelink communication, in (partial) coverage

Figure 5.8.5.1-2: Synchronisation information transmission for NR sidelink communication, out of coverage

The purpose of this procedure is to provide synchronisation information to a UE.

[TS 38.331, clause 5.8.5.2]

A UE capable of NR sidelink communication and SLSS/PSBCH transmission shall, when transmitting NR sidelink communication, and if the conditions for NR sidelink communication operation are met and when the following conditions are met:

…

1> else:

2> for the frequency used for NR sidelink communication, if syncTxThreshOoC is included in SidelinkPreconfigNR; and the UE is not directly synchronized to GNSS, and the UE has no selected SyncRef UE or the PSBCH-RSRP measurement result of the selected SyncRef UE is below the value of syncTxThreshOoC; or

2> for the frequency used for NR sidelink communication, if the UE selects GNSS as the synchronization reference source:

3> transmit sidelink SSB on the frequency used for NR sidelink communication in accordance with TS 38.211 [16], including the transmission of SLSS as specified in 5.8.5.3 and transmission of MasterInformationBlockSidelink as specified in 5.8.9.4.3;

[TS 38.331, clause 5.8.5.3]

The UE shall select the SLSSID and the slot in which to transmit SLSS as follows:

…

1> else if triggered by NR sidelink communication and the UE has GNSS as the synchronization reference:

2> select SLSSID 0;

…

2> else:

3> select the slot(s) indicated by sl-SSB-TimeAllocation1;

1> else:

2> select the synchronisation reference UE (i.e. SyncRef UE) as defined in 5.8.6;

2> if the UE has a selected SyncRef UE and inCoverage in the MasterInformationBlockSidelink message received from this UE is set to true; or

2> if the UE has a selected SyncRef UE and inCoverage in the MasterInformationBlockSidelink message received from this UE is set to false while the SLSS from this UE is part of the set defined for out of coverage, see TS 38.211 [16]:

3> select the same SLSSID as the SLSSID of the selected SyncRef UE;

3> select the slot in which to transmit the SLSS according to the sl-SSB-TimeAllocation1 or sl-SSB-TimeAllocation2 included in the preconfigured sidelink parameters corresponding to the concerned frequency, such that the timing is different from the SLSS of the selected SyncRef UE;

…

2> else if the UE has a selected SyncRef UE:

3> select the SLSSID from the set defined for out of coverage having an index that is 336 more than the index of the SLSSID of the selected SyncRef UE, see TS 38.211 [16];

3> select the slot in which to transmit the SLSS according to sl-SSB-TimeAllocation1 or sl-SSB-TimeAllocation2 included in the preconfigured sidelink parameters corresponding to the concerned frequency, such that the timing is different from the SLSS of the selected SyncRef UE;

2> else (i.e. no SyncRef UE selected):

3> if the UE has not randomly selected an SLSSID:

4> randomly select, using a uniform distribution, an SLSSID from the set of sequences defined for out of coverage except SLSSID 336 and 337, see TS 38.211 [16];

4> select the slot in which to transmit the SLSS according to the sl-SSB-TimeAllocation1 or sl-SSB-TimeAllocation2 (arbitrary selection between these) included in the preconfigured sidelink parameters in SidelinkPreconfigNR corresponding to the concerned frequency;

[TS 38.331, clause 5.8.6.2]

The UE shall:

…

1> else if the frequency used for NR sidelink communication is included in SL-PreconfigurationNR, and sl-SyncPriority in SidelinkPreconfigNR is set to gnss and GNSS is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]:

2> select GNSS as the synchronization reference source;

1> else:

2> perform a full search (i.e. covering all subframes and all possible SLSSIDs) to detect candidate SLSS, in accordance with TS 38.133 [14]

2> when evaluating the one or more detected SLSSIDs, apply layer 3 filtering as specified in 5.5.3.2 using the preconfigured sl-filterCoefficient, before using the PSBCH-RSRP measurement results;

2> if the UE has selected a SyncRef UE:

…

3> if the PSBCH-RSRP of the current SyncRef UE is less than the minimum requirement defined in TS 38.133 [14]:

4> consider no SyncRef UE to be selected;

2> if the UE has selected GNSS as the synchronization reference for NR sidelink communication:

…

3> if GNSS becomes not reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14]:

4> consider GNSS not to be selected;

…

2> if the UE has not selected any synchronization reference:

3> if the UE detects one or more SLSSIDs for which the PSBCH-RSRP exceeds the minimum requirement defined in TS 38.133 [14] by sl-SyncRefMinHyst and for which the UE received the corresponding MasterInformationBlockSidelink message (candidate SyncRef UEs), or if the UE detects GNSS that is reliable in accordance with TS 38.101-1 [15] and TS 38.133 [14], or if the UE detects a cell, select a synchronization reference according to the following priority group order:

…

4> if sl-SyncPriority corresponding to the concerned frequency is set to gnss, and sl-NbAsSync is set to false:

5> UEs of which SLSSID is 0, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, starting with the UE with the highest PSBCH-RSRP result (priority group 1);

5> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCHS-RSRP result (priority group 2);

…

5> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 3);

[TS 38.331, clause 5.8.9.4.3]

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

…

1> else if out of coverage on the frequency used for NR sidelink communication as defined in TS 38.304 [20]; and the UE selects GNSS as the synchronization reference and sl-SSB-TimeAllocation3 is not configured for the frequency used in SidelinkPreconfigNR:

2> set inCoverage to true;

2> set reservedBits to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SidelinkPreconfigNR defined in 9.3);

2> set sl-TDD-Config to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SL-PreconfigurationNR defined in 9.3) as described in TS 38.213, clause 16.1 [13];

1> else if the UE has a selected SyncRef UE (as defined in 5.8.6):

2> set inCoverage to false;

2> set sl-TDD-Config and reservedBits to the value of the corresponding field included in the received MasterInformationBlockSidelink;

1> else:

2> set inCoverage to false;

2> set reservedBits to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SidelinkPreconfigNR defined in 9.3);

2> set sl-TDD-Config to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SL-PreconfigurationNR defined in 9.3) as described in TS 38.213, clause 16.1 [13];

1> set directFrameNumber and slotIndex according to the slot used to transmit the SLSS, as specified in 5.8.5.3;

1> submit the MasterInformationBlockSidelink to lower layers for transmission upon which the procedure ends;

[TS 38.331, clause 5.8.12]

When the UE selects GNSS as the synchronization reference source, the DFN, the subframe number within a frame and slot number within a frame used for NR sidelink communication are derived from the current UTC time, by the following formulae:

DFN= Floor (0.1*(Tcurrent –Tref–OffsetDFN)) mod 1024

SubframeNumber= Floor (Tcurrent –Tref–OffsetDFN) mod 10

SlotNumber= Floor ((Tcurrent –Tref–OffsetDFN)*2μ) mod (10*2μ)

Where:

Tcurrent is the current UTC time obtained from GNSS. This value is expressed in milliseconds;

Tref is the reference UTC time 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Thursday, December 31, 1899 and Friday, January 1, 1900). This value is expressed in milliseconds;

OffsetDFN is the value sl-OffsetDFN if configured, otherwise it is zero. This value is expressed in milliseconds.

μ=0/1/2/3 corresponding to the 15/30/60/120 kHz of SCS for SL, respectively.

NOTE 1: In case of leap second change event, how UE obtains the scheduled time of leap second change to adjust Tcurrent correspondingly is left to UE implementation. How UE handles to avoid the sudden discontinuity of DFN is left to UE implementation.

NOTE 2: Void.

12.1.2.1.3 Test description

12.1.2.1.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE 1, 2 and 3 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE 1 transmits S-SSB with SLSSID = 0, inCoverage = true in slots determined by sl-SSB-TimeAllocation1 and GNSS timing.

– NR-SS-UE 2 transmits S-SSB with SLSSID = 0, inCoverage = false in slots determined by sl-SSB-TimeAllocation2 and GNSS timing.

– NR-SS-UE 3 transmits S-SSB with SLSSID = 336, inCoverage = false in slots determined by sl-SSB-TimeAllocation1 and GNSS timing.

– 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 below information in UE or in a USIM containing default values (as per TS 38.508-1 [4]) except for those listed in Table 12.1.2.1.3.1-1.

Table 12.1.2.1.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

As per TS 36.508 [18] clause 4.9.3.4

EFVST

Service n°119 is "available"

EFV2XP_PC5

As per TS 38.508-1[4] clause 4.8.3.3.3

SL-PreconfigurationNR included in V2X data policy over PC5 is defined in Table 12.1.2.1.3.3-1

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), GNSS Sync (On) as defined in TS 38.508-1 [4], subclause 4.5.1.

12.1.2.1.3.2 Test procedure sequence

Table 12.1.2.1.3.2-1 illustrates the sidelink power levels to be applied for NR-SS-UE 1, 2 and 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1", "T2" and "T3", are applied at the point indicated in the Main behaviour description in Table 12.1.2.1.3.2-2.

Table 12.1.2.1.3.2-1: Time instances of NR-SS-UE power level and parameter changes in conducted test environment

Parameter

Unit

NR-SS-UE 1

NR-SS-UE 2

NR-SS-UE 3

Remark

T0

NR-SS-UE power

dBm/

SCS

-85

OFF

OFF

Priority of NR-SS-UE 1 is lower than GNSS

EPRE ratio of S-SSS to NR-SS-UE power

dB

0

–

–

T1

NR-SS-UE power

dBm/

SCS

-85

-85

OFF

Priority of NR-SS-UE 2 is lower than Priority of NR-SS-UE 1

EPRE ratio of S-SSS to NR-SS-UE power

dB

0

0

–

T2

NR-SS-UE power

dBm/

SCS

OFF

-85

-85

Priority of NR-SS-UE 3 is lower than Priority of NR-SS-UE 2

EPRE ratio of S-SSS to NR-SS-UE power

dB

–

0

0

T3

NR-SS-UE power

dBm/

SCS

OFF

OFF

-85

Priority of UE internal clock is lower than NR-SS-UE 3

EPRE ratio of S-SSS to NR-SS-UE power

dB

–

–

0

Table 12.1.2.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS triggers UE to close UE test loop mode E (Transmit Mode).

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

–

–

–

–

2

The SS waits 10 seconds

–

–

–

–

3

Check: Does the UE transmit S-SSBs which satisfy all following conditions?

  • SLSSID = 0;
  • incoverage = true in SL-MIB;
  • slotIndex and directFrameNumber in SL-MIB are consistent with the slot index and DFN calculated based on the UTC time obtained from GNSS as specified in TS 38.331 [22] clause 5.8.12;
  • transmitted in slots determined by sl-SSB-TimeAllocation1 and GNSS timing;
  • reserveBits in SL-MIB is consistent with reserveBits in pre-configuration.

–

–

1

P

4

The SS powers off GNSS simulator.

–

–

–

–

5

The SS re-adjusts the NR-SS-UE power level according to row "T1" in table 12.1.2.1.3.2-1.

–

–

–

–

6

The SS waits 10 seconds

–

–

–

–

7

Check: Does the UE transmit S-SSBs which satisfy all following conditions?

  • SLSSID = 0;
  • incoverage = false in SL-MIB;
  • slotIndex and directFrameNumber in SL-MIB are consistent with the slot index and DFN of SyncRef UE 1;
  • transmitted in slots determined by sl-SSB-TimeAllocation2 and NR-SS-UE 1 timing;
  • reserveBits in SL-MIB is consistent with reserveBits in SL-MIB of NR-SS-UE 1.

–

–

2

P

8

The SS re-adjusts the NR-SS-UE power level according to row "T2" in table 12.1.2.1.3.2-1.

–

–

–

–

9

The SS waits 10 seconds

–

–

–

–

10

Check: Does the UE transmit S-SSBs which satisfy all following conditions?

  • SLSSID = 336;
  • incoverage = false in SL-MIB;
  • slotIndex and directFrameNumber in SL-MIB are consistent with the slot index and DFN of SyncRef UE 2.
  • transmitted in slots determined by sl-SSB-TimeAllocation1 and the NR-SS-UE 2 timing?
  • reserveBits in SL-MIB is consistent with reserveBits in SL-MIB of NR-SS-UE 2.

–

–

3

P

11

The SS re-adjusts the NR-SS-UE power level according to row "T3" in table 12.1.2.1.3.2-1.

–

–

–

–

12

The SS waits 10 seconds

–

–

–

–

13

Check: Does the UE transmit S-SSBs which satisfy all following conditions?

  • SLSSID is consistent with SLSSID of NR-SS-UE 3;
  • incoverage = false in SL-MIB;
  • slotIndex and directFrameNumber in SL-MIB are consistent with the slot index and DFN of SyncRef UE 3;
  • transmitted in slots determined by sl-SSB-TimeAllocation2 and SyncRef UE 3 timing;
  • reserveBits in SL-MIB is consistent with reserveBits in SL-MIB of SyncRef UE 3.

–

–

4

P

14

The SS re-adjusts the NR-SS-UE power level according to row "T0" in table 12.1.2.1.3.2-1.

–

–

–

–

15

The SS waits 10 seconds

–

–

–

–

16

Check: Does the UE transmit S-SSBs which satisfy all following conditions?

  • SLSSID is larger than 335;
  • incoverage = false in SL-MIB;
  • reserveBits in SL-MIB is consistent with reserveBits in pre-configuration.

–

–

5

P

17

The SS triggers UE to open UE test loop mode E.

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

–

–

–

–

12.1.2.1.3.3 Specific message contents

Table 12.1.2.1.3.3-1: V2X service identifier to default mode of communication mapping rule (Pre-configuration, UE under test)

Derivation Path: TS 38.508-1 [4] Table 4.7.5.5-53

Information Element

Value/remark

Comment

Condition

DMC

’10’B

Default mode of communication is set to broadcast

Table 12.1.2.1.3.3-2: SL-SyncConfig (Pre-configuration, UE under test)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-31

Information Element

Value/remark

Comment

Condition

SL-SyncConfig-r16 ::= SEQUENCE (SIZE (1..maxSL-SyncConfig-r16)) OF SL-SyncConfig-r16 {

1 entry

SL-SyncConfig-r16[1] SEQUENCE {

txParameters-r16 SEQUENCE {

syncTxThreshOoC-r16

13

actual threshold is +infinity

}

}

Table 12.1.2.1.3.3-3: +CCUTLE (Table 12.1.2.1.3.2-2, step 1)

Derivation Path: TS 38.508-1 [4] Table 4.7B-1 with condition Close and Transmit

Table 12.1.2.1.3.3-4: MasterInformationBlockSidelink (Table 12.1.2.1.3.2-2, SyncRef UE 1, 2 and 3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-1

Information Element

Value/remark

Comment

Condition

MasterInformationBlockSidelink ::= SEQUENCE {

inCoverage-r16

true

SyncRef UE 1

false

SyncRef UE 2

SyncRef UE 3

directFrameNumber-r16

DFN determined based on the formula given in 38.331 [22] clause 5.8.12.

slotIndex-r16

slot index determined based on the formula given in 38.331 [22] clause 5.8.12.

reservedBits-r16

01

SyncRef UE 1

10

SyncRef UE 2

11

SyncRef UE 3

}

Table 12.1.2.1.3.3-5: MasterInformationBlockSidelink (Table 12.1.2.1.3.2-2, step 3, 7, 10, 13 and 16, UE under test)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-1 with condition TX

Information Element

Value/remark

Comment

Condition

MasterInformationBlockSidelink ::= SEQUENCE {

inCoverage-r16

true

Step 3

false

Step 7, 10, 13, 16

directFrameNumber-r16

DFN determined based on the formula given in 38.331 [22] clause 5.8.12

Step 3, 7, 10, 13

Not checked

Step 6

slotIndex-r16

slot index determined based on the formula given in 38.331 [22] clause 5.8.12

Step 3, 7, 10, 13

Not checked

Step 6

reservedBits-r16

00

Same as preconfiguration

Step 3, 16

01

Same as SyncRef UE 1

Step 7

10

Same as SyncRef UE 2

Step 10

11

Same as SyncRef UE 3

Step 13

}

Table 12.1.2.1.3.3-6: +CCUTLE (Table 12.1.2.1.3.2-2, step 17)

Derivation Path: TS 38.508-1 [4] Table 4.7B-1 with condition Open

12.1.2.2 PC5-only operation / Sidelink synchronization related procedure / SL-SSB transmission Initiation and Cease

12.1.2.2.1 Test Purpose (TP)

(1)

with { UE is configured by upper layer to perform sidelink transmission. }

ensure that {

when { UE selects GNSS as synchonization reference source. }

then { UE keeps transmitting S-SSB. }

}

(2)

with { UE is configured by upper layer to perform sidelink transmission and is configured with syncTxThreshOoC in pre-configuration. }

ensure that {

when { UE selects SyncRef UE as synchronization reference source. PSBCH-RSRP of the SyncRef UE is lower than syncTxThreshOoC. }

then { UE starts transmitting S-SSB. }

}

(3)

with { UE is configured by upper layer to perform sidelink transmission and is configured with syncTxThreshOoC in pre-configuration. }

ensure that {

when { UE selects SyncRef UE as synchronization reference source. PSBCH-RSRP of the SyncRef UE is above than syncTxThreshOoC. }

then { UE stops transmitting S-SSB. }

}

(4)

with { UE is configured by upper layer to perform sidelink transmission and is configured with syncTxThreshOoC in pre-configuration. }

ensure that {

when { UE selects SyncRef UE as synchronization reference source. PSBCH-RSRP of the SyncRef UE is above than syncTxThreshOoC. }

then { UE stops transmitting S-SSB. }

}

12.1.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.2. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.8.2]

The UE shall perform NR sidelink communication operation only if the conditions defined in this clause are met:

…

1> if the UE has no serving cell (RRC_IDLE);

[TS 38.331, clause 5.8.5.1]

Figure 5.8.5.1-1: Synchronisation information transmission for NR sidelink communication, in (partial) coverage

Figure 5.8.5.1-2: Synchronisation information transmission for NR sidelink communication, out of coverage

The purpose of this procedure is to provide synchronisation information to a UE.

[TS 38.331, clause 5.8.5.2]

A UE capable of NR sidelink communication and SLSS/PSBCH transmission shall, when transmitting NR sidelink communication, and if the conditions for NR sidelink communication operation are met and when the following conditions are met:

…

1> else:

2> for the frequency used for NR sidelink communication, if syncTxThreshOoC is included in SidelinkPreconfigNR; and the UE is not directly synchronized to GNSS, and the UE has no selected SyncRef UE or the PSBCH-RSRP measurement result of the selected SyncRef UE is below the value of syncTxThreshOoC; or

2> for the frequency used for NR sidelink communication, if the UE selects GNSS as the synchronization reference source:

3> transmit sidelink SSB on the frequency used for NR sidelink communication in accordance with TS 38.211 [16], including the transmission of SLSS as specified in 5.8.5.3 and transmission of MasterInformationBlockSidelink as specified in 5.8.9.4.3;

12.1.2.2.3 Test description

12.1.2.2.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE 1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE 1 transmits S-SSB with SLSSID = 0, inCoverage = true in slots determined by sl-SSB-TimeAllocation1 and GNSS timing.

– 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 below information in UE or in a USIM containing default values (as per TS 38.508-1 [4]) except for those listed in Table 12.1.2.2.3.1-1.

Table 12.1.2.2.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

As per TS 36.508 [18] clause 4.9.3.4

EFVST

Service n°119 is "available"

EFV2XP_PC5

As per TS 38.508-1[4] clause 4.8.3.3.3

SL-PreconfigurationNR included in V2X data policy over PC5 is defined in Table 12.1.2.2.3.3-1

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), GNSS Sync (On) as defined in TS 38.508-1 [4], subclause 4.5.1.

12.1.2.2.3.2 Test procedure sequence

Table 12.1.2.2.3.2-1 illustrates the sidelink power levels to be applied for NR-SS-UE 1, 2 and 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1" and "T2", are applied at the point indicated in the Main behaviour description in Table 12.1.2.2.3.2-2.

Table 12.1.2.2.3.2-1: Time instances of NR-SS-UE power level and parameter changes in conducted test environment

Parameter

Unit

NR-SS-UE 1

Remark

T0

NR-SS-UE power

dBm/

SCS

OFF

NR-SS-UE 1 is powered off.

EPRE ratio of S-SSS to NR-SS-UE power

dB

–

T1

NR-SS-UE power

dBm/

SCS

-106

The power level to ensure that PSBCH-RSRP of NR-SS-UE 1 is lower than syncTxThreshOoC

EPRE ratio of S-SSS to NR-SS-UE power

dB

0

T2

NR-SS-UE power

dBm/

SCS

-94

The power level to ensure that PSBCH-RSRP of NR-SS-UE 1 is higher than syncTxThreshOoC

EPRE ratio of S-SSS to NR-SS-UE power

dB

0

Table 12.1.2.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS triggers UE to close UE test loop mode E (Transmit Mode).

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

–

–

–

–

2

The SS waits 10 seconds

–

–

–

–

3

Check: Does the UE transmit S-SSBs in slots determined by sl-SSB-TimeAllocation1 and GNSS timing?

–

–

1

P

4

The SS powers off GNSS simulator.

–

–

–

–

5

The SS re-adjusts the NR-SS-UE power level according to row "T1" in table 12.1.2.2.3.2-1.

–

–

–

–

6

The SS waits 10 seconds

–

–

–

–

7

Check: Does the UE transmit S-SSBs in slots determined by sl-SSB-TimeAllocation2 and NR-SS-UE 1 timing?

–

–

2

P

8

The SS re-adjusts the NR-SS-UE power level according to row "T2" in table 12.1.2.2.3.2-1.

–

–

–

–

9

The SS waits 10 seconds

–

–

–

–

10

Check: Does the UE transmit S-SSBs in slots determined by sl-SSB-TimeAllocation2 and NR-SS-UE 1 timing?

–

–

3

F

11

The SS re-adjusts the NR-SS-UE power level according to row "T0" in table 12.1.2.2.3.2-1.

–

–

–

–

12

The SS waits 10 seconds

–

–

–

–

13

Check: Does the UE transmit S-SSBs?

–

–

4

P

14

The SS triggers UE to open UE test loop mode E.

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

–

–

–

–

12.1.2.2.3.3 Specific message contents

Table 12.1.2.2.3.3-1: V2X service identifier to default mode of communication mapping rule (Pre-configuration, UE under test)

Derivation Path: TS 38.508-1 [4] Table 4.7.5.5-53

Information Element

Value/remark

Comment

Condition

DMC

’10’B

Default mode of communication is set to broadcast

Table 12.1.2.2.3.3-2: +CCUTLE (Table 12.1.2.2.3.2-2, step 1)

Derivation Path: TS 38.508-1 [4] Table 4.7B-1 with condition Close and Transmit

Table 12.1.2.2.3.3-3: MasterInformationBlockSidelink (Table 12.1.2.2.3.2-2, SyncRef UE 1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-1

Information Element

Value/remark

Comment

Condition

MasterInformationBlockSidelink ::= SEQUENCE {

inCoverage-r16

true

directFrameNumber-r16

DFN determined based on the formula given in 38.331 [22] clause 5.8.12.

slotIndex-r16

slot index determined based on the formula given in 38.331 [22] clause 5.8.12.

}

Table 12.1.2.2.3.3-5: MasterInformationBlockSidelink (Table 12.1.2.2.3.2-2, step 3, 7, 13, UE under test)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-1 with condition TX

Information Element

Value/remark

Comment

Condition

MasterInformationBlockSidelink ::= SEQUENCE {

inCoverage-r16

true

Step 3

false

Step 7, 13

directFrameNumber-r16

DFN determined based on the formula given in 38.331 [22] clause 5.8.12

Step 3, 7

Not checked

Step 13

slotIndex-r16

slot index determined based on the formula given in 38.331 [22] clause 5.8.12

Step 3, 7

Not checked

Step 13

}

Table 12.1.2.2.3.3-6: +CCUTLE (Table 12.1.2.2.3.2-2, step 17)

Derivation Path: TS 38.508-1 [4] Table 4.7B-1 with condition Open

12.1.3 PC5-only operation / Measurement configuration and reporting via PC5 RRC

12.1.3.1 PC5-only operation / Measurement configuration and reporting via PC5 RRC / PSBCH-RSRP measurement configuration

12.1.3.1.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE on unicast sidelink }

ensure that {

when { UE is configured by upper layer to configure periodical PSBCH-RSRP measurement}

then { UE sends a RRCReconfigurationSidelink message to peer UE }

}

12.1.3.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.1, 5.8.9.1.3, 5.8.9.1.9. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.8.1]

The PC5-RRC signalling, as specified in sub-clause 5.8.9, can be initiated after its corresponding PC5 unicast link establishment (TS 23.287 [55]).

[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> set the sl-MeasConfig as follows:

2> If the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList 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> start timer T400 for the destination associated with the sidelink DRB;

1> set the sl-CSI-RS-Config;

1> set the sl-LatencyBoundCSI-Report,

NOTE 1: How to set the parameters included in sl-CSI-RS-Config and sl-LatencyBoundCSI-Report is up to UE implementation.

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

[TS 38.331, clause 5.8.9.1.3]

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

1> if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList:

2> for each SLRB-PC5-ConfigIndex value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration;

3> perform the sidelink DRB release procedure, according to sub-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 sub-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 sub-clause 5.8.9.1a.1.1 are met:

4> perform the sidelink DRB release procedure according to sub-clause 5.8.9.1a.1.2;

3> else if the sidelink DRB modification conditions as described in sub-clause 5.8.9.1a.2.1 are met:

4> perform the sidelink DRB modification procedure according to sub-clause 5.8.9.1a.2.2;

1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig:

2> perform the sidelink measurement configuration procedure as specified in 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 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> else:

2> set the content of the RRCReconfigurationCompleteSidelink message;

3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission;

NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure.

[TS 38.331, clause 5.8.9.1.9]

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.

12.1.3.1.3 Test description

12.1.3.1.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE1 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 uses GNSS as the synchronization reference source.

– The UE is equipped with below information in UE or in a USIM containing default values (as per TS 38.508-1 [4] clause 4.8.3.3.3) except for those listed in Table 12.1.3.1.3.1-1.

Table 12.1.3.1.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

service no. 119 is available

EFVST

Service no.2 V2X policy configuration data over PC5 is supported, i.e. value is ’01 02′ HEX

EFV2XP_PC5

As per TS 38.508-1[4] clause 4.8.3.3.3

SL-PreconfigurationNR included in V2X data policy over PC5 is defined in Table 12.1.3.1.3.3-1

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.22.

12.1.3.1.3.2 Test procedure sequence

Table 12.1.3.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE is configured by upper layer to initiate the sidelink RRC reconfiguration procedure to configure periodical PSBCH-RSRP measurement

Note: This step is triggered by MMI or AT command.

—

2

Check: Does UE send a RRCReconfigurationSidelink message to NR-SS-UE1?

–>

PC5 RRC: RRCReconfigurationSidelink

1

P

3

NR-SS-UE1 sends a RRCReconfigurationCompleteSidelink message

<–

PC5 RRC: RRCReconfigurationCompleteSidelink

12.1.3.1.3.3 Specific message contents

Table 12.1.3.1.3.3-1: SL-PreconfigurationNR

Derivation path: TS 38.508-1 [4], Table 4.10.1-1

Information Element

Value/Remark

Comment

Condition

SL-PreconfigurationNR-r16 ::= SEQUENCE {

sidelinkPreconfigNR-r16 SEQUENCE {

sl-MeasPreConfig-r16

SL-MeasConfigCommon

}

}

Table 12.1.3.1.3.3-2: SL-MeasConfigCommon (Table 12.1.3.1.3.3-1)

Derivation path: TS 38.508-1 [4], Table 4.6.6-13

Information Element

Value/Remark

Comment

Condition

SL-MeasConfigCommon-r16 ::= SEQUENCE {

sl-MeasObjectListCommon-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ObjectId-r16)) OF SL-MeasObjectInfo-r16{

1 entry

SL-MeasObjectInfo-r16[1] SEQUENCE {

entry 1

sl-MeasObjectId-r16

1

sl-MeasObject-r16 SEQUENCE {

frequencyInfoSL-r16

ARFCN-ValueNR as defined in TS 38.508-1 [4], Table 4.6.3-5 with condition SL_SSB of NRf1

}

}

}

}

Table 12.1.3.1.3.3-3: RRCReconfigurationSidelink (step 2, Table 12.1.3.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 with condition SL_MEASand TX

Information Element

Value/Remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

sl-MeasConfig-r16 CHOICE {

setup SEQUENCE {

sl-ReportConfigToAddModList-r16

SL-ReportConfigList-r16 as defined in TS 38.508-1 [4], Table 4.6.6-24 with condition PERIODICAL

}

}

}

}

}

Table 12.1.3.1.3.3-4: RRCReconfigurationCompleteSidelink (step 3, Table 12.1.3.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-4 with condition RX

12.1.3.2 PC5-only operation / Measurement configuration and reporting via PC5 RRC / PSBCH-RSRP measurement reporting / Event S1 and S2

12.1.3.2.1 Test Purpose (TP)

(1)

with { UE configured to perfv

form event S1 PSBCH-RSRP measurement on SL-SSB via PC5 RRC }

ensure that {

when { PSBCH-RSRP measurement results of SL SSB are below threshold }

then { UE does not trigger PSBCH-RSRP measurement reporting }

}

(2)

with { UE configured to perform event S1 PSBCH-RSRP measurement on SL-SSB via PC5 RRC }

ensure that {

when { PSBCH-RSRP measurement results of SL SSB are above threshold }

then { UE triggers PSBCH-RSRP measurement reporting }

}

(3)

with { UE configured to perform event S2 PSBCH-RSRP measurement on SL-SSB via PC5 RRC }

ensure that {

when { PSBCH-RSRP measurement results of SL SSB are above threshold }

then { UE does not trigger PSBCH-RSRP measurement reporting }

}

(4)

with { UE configured to perform event S2 PSBCH-RSRP measurement on SL-SSB via PC5 RRC }

ensure that {

when { PSBCH-RSRP measurement results of SL SSB are below threshold }

then { UE triggers PSBCH-RSRP measurement reporting }

}

12.1.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1.3, 5.8.10.2.1, 5.8.10.2.5, 5.8.10.2.7, 5.8.10.3.1, 5.8.10.4.2, 5.8.10.4.3 and 5.8.10.5.1. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.9.1.3]

The UE shall perform the following actions upon reception of the RRCReconfigurationSidelink:

…

1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig:

2> perform the sidelink measurement configuration procedure as specified in 5.8.10;

…

1> else:

2> set the content of the RRCReconfigurationCompleteSidelink message;

3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission;

NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure.

[TS 38.331, subclause 5.8.10.2.1]

The UE shall:

…

1> if the received sl-MeasConfig includes the sl-MeasObjectToAddModList in the RRCReconfigurationSidelink:

2> perform the sidelink measurement object addition/modification procedure as specified in 5.8.10.2.5;

…

1> if the received sl-MeasConfig includes the sl-ReportConfigToAddModList in the RRCReconfigurationSidelink:

2> perform the sidelink reporting configuration addition/modification procedure as specified in 5.8.10.2.7;

1> if the received sl-MeasConfig includes the sl-QuantityConfig in the RRCReconfigurationSidelink:

2> perform the sidelink quantity configuration procedure as specified in 5.8.10.2.8;

…

1> if the received sl-MeasConfig includes the sl-MeasIdToAddModList in the RRCReconfigurationSidelink:

2> perform the sidelink measurement identity addition/modification procedure as specified in 5.8.10.2.3;

[TS 38.331, subclause 5.8.10.2.5]

The UE shall:

1> for each sl-MeasObjectId included in the received sl-MeasObjectToAddModList:

2> if an entry with the matching sl-MeasObjectId exists in the sl-MeasObjectList within the VarMeasConfigSL, for this entry:

3> for each sl-MeasId associated with this sl-MeasObjectId included in the sl-MeasIdList within the VarMeasConfigSL, if any:

4> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included;

4> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId;

3> reconfigure the entry with the value received for this sl-MeasObject;

2> else:

3> add a new entry for the received sl-MeasObject to the sl-MeasObjectList within VarMeasConfigSL.

[TS 38.331, subclause 5.8.10.2.7]

The UE shall:

1> for each sl-ReportConfigId included in the received sl-ReportConfigToAddModList:

2> if an entry with the matching sl-ReportConfigId exists in the sl-ReportConfigList within the VarMeasConfigSL, for this entry:

3> reconfigure the entry with the value received for this sl-ReportConfig;

3> for each sl-MeasId associated with this sl-ReportConfigId included in the sl-MeasIdList within the VarMeasConfigSL, if any:

4> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included;

4> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId;

2> else:

3> add a new entry for the received sl-ReportConfig to the sl-ReportConfigList within the VarMeasConfigSL.

[TS 38.331, subclause 5.8.10.3.1]

A UE shall derive NR sidelink measurement results by measuring one or multiple DMRS associated per PC5-RRC connection as configured by the peer UE associated, as described in 5.8.10.3.2. For all NR sidelink measurement results the UE applies the layer 3 filtering as specified in sub-clause 5.5.3.2, before using the measured results for evaluation of reporting criteria and measurement reporting. In this release, only NR sidelink RSRP can be configured as trigger quantity and reporting quantity.

The UE shall:

1> for each sl-MeasId included in the sl-MeasIdList within VarMeasConfigSL:

2> if the sl-MeasObject is associated to NR sidelink and the sl-RS-Type is set to dmrs:

3> derive the layer 3 filtered NR sidelink measurement result based on DMRS for the trigger quantity and each measurement quantity indicated in sl-ReportQuantity using parameters from the associated sl-MeasObject, as described in 5.8.10.3.2.

2> perform the evaluation of reporting criteria as specified in 5.8.10.4.

[TS 38.331, subclause 5.8.10.4.2]

The UE shall:

1> consider the entering condition for this event to be satisfied when condition S1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition S1-2, as specified below, is fulfilled;

1> for this NR sidelink measurement, consider the NR sidelink frequency corresponding to the associated sl-MeasObject associated with this event.

Inequality S1-1 (Entering condition)

Ms – Hys > Thresh

Inequality S1-2 (Leaving condition)

Ms + Hys < Thresh

The variables in the formula are defined as follows:

Ms is the NR sidelink measurement result of the NR sidelink frequency, not taking into account any offsets.

Hys is the hysteresis parameter for this event (i.e. sl-Hysteresis as defined within sl-ReportConfig for this event).

Thresh is the threshold parameter for this event (i.e. s1-Threshold as defined within sl-ReportConfig for this event).

Ms is expressed in dBm in case of RSRP.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

[TS 38.331, subclause 5.8.10.4.3]

The UE shall:

1> consider the entering condition for this event to be satisfied when condition S2-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition S2-2, as specified below, is fulfilled;

1> for this NR sidelink measurement, consider the NR sidelink frequency indicated by the sl-MeasObject associated to this event.

Inequality S2-1 (Entering condition)

Ms + Hys < Thresh

Inequality S2-2 (Leaving condition)

Ms – Hys > Thresh

The variables in the formula are defined as follows:

Ms is the NR sidelink measurement result of the NR sidelink frequency, not taking into account any offsets.

Hys is the hysteresis parameter for this event (i.e. sl-Hysteresis as defined within sl-ReportConfig for this event).

Thresh is the threshold parameter for this event (i.e. s2-Threshold as defined within sl-ReportConfig for this event).

Ms is expressed in dBm in case of RSRP.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

[TS 38.331, subclause 5.8.10.5.1]

Figure 5.8.10.5.1-1: NR sidelink measurement reporting

The purpose of this procedure is to transfer measurement results from the UE to the peer UE associated.

For the sl-MeasId for which the NR sidelink measurement reporting procedure was triggered, the UE shall set the sl-MeasResults within the MeasurementReportSidelink message as follows:

1> set the sl-MeasId to the measurement identity that triggered the NR sidelink measurement reporting;

1> if the sl-ReportConfig associated with the sl-MeasId that triggered the NR sidelink measurement reporting is set to sl-EventTriggered or sl-Periodical:

2> set sl-ResultDMRS within sl-MeasResult to include the NR sidelink DMRS based quantity indicated in the sl-ReportQuantity within the concerned sl-ReportConfig;

1> increment the sl-NumberOfReportsSent as defined within the VarMeasReportListSSL for this sl-MeasId by 1;

1> stop the periodical reporting timer, if running;

1> if the sl-NumberOfReportsSent as defined within the VarMeasReportListSL for this sl-MeasId is less than the sl-ReportAmount as defined within the corresponding sl-ReportConfig for this sl-MeasId:

2> start the periodical reporting timer with the value of sl-ReportInterval as defined within the corresponding sl-ReportConfig for this sl-MeasId;

1> else:

2> if the sl-ReportType is set to sl-Periodical:

3> remove the entry within the VarMeasReportListSL for this sl-MeasId;

3> remove this sl-MeasId from the sl-MeasIdList within VarMeasConfigSL;

1> submit the MeasurementReportSidelink message to lower layers for transmission, upon which the procedure ends.

12.1.3.2.3 Test description

12.1.3.2.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE1 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 uses GNSS as the synchronization reference source.

– The UE is equipped with a USIM containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using NR-SS-UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.23.

12.1.3.2.3.2 Test procedure sequence

Table 12.1.3.2.3.2-1 illustrates the downlink power levels and other, if any, changing parameters to be applied for the NR-SS-UE at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described elsewhere in the present clause.

Table 12.1.3.2.3.2-1: Time instances of simulated NR-SS-UE power level and parameter changes

Parameter

Unit

NR-SS-UE1

Comment

T0

S-RSRP

dBm/SCS

-98

Power level is such that entering condition for event S1 Ms – Hys > Thresh is not satisfied and entering condition for event S2 Ms + Hys < Thresh is satisfied.

T1

S-RSRP

dBm/SCS

-76

Power level is such that entering condition for event S1 Ms – Hys > Thresh is satisfied and entering condition for event S2 Ms + Hys < Thresh is not satisfied.

Table 12.1.3.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The NR-SS-UE1 transmits an RRCReconfigurationSidelink message including sl-MeasConfig to setup event S1 triggered PSBCH-RSRP measurement and reporting.

<–

PC5 RRC: RRCReconfigurationSidelink

–

–

2

The UE transmits an RRCReconfigurationCompleteSidelink message.

–>

PC5 RRC: RRCReconfigurationCompleteSidelink

–

–

3

Check: Does the UE transmit a MeasurementReportSidelink message to report event S1 within the next 10s?

–

–

1

F

4

The NR-SS-UE1 re-adjusts the power level according to row "T1" in Table 12.1.3.2.3.2-1.

–

–

–

–

–

EXCEPTION: Step 5 below is repeated until 2 MeasurementReportSidelink messages are received from the UE.

–

–

–

–

5

Check: Does the UE transmit a MeasurementReportSidelink message to report event S1?

–>

PC5 RRC: MeasurementReportSidelink

2

P

6

The NR-SS-UE1 transmits an RRCReconfigurationSidelink message including sl-MeasConfig to setup event S2 triggered PSBCH-RSRP measurement and reporting.

<–

PC5 RRC: RRCReconfigurationSidelink

–

–

7

The UE transmits an Table 12.1.3.2.3.2-2 message.

–>

PC5 RRC: Table 12.1.3.2.3.2-2

–

–

8

Check: Does the UE transmit a MeasurementReportSidelink message to report event S2 within the next 10s?

–

–

3

F

9

The NR-SS-UE1 re-adjusts the power level according to row "T0" in Table 12.1.3.2.3.2-1.

–

–

–

–

–

EXCEPTION: Step 10 below is repeated until 2 MeasurementReportSidelink messages are received from the UE.

–

–

–

–

10

Check: Does the UE transmit a MeasurementReportSidelink message to report event S2?

–>

PC5 RRC: MeasurementReportSidelink

4

P

12.1.3.2.3.3 Specific message contents

Table 12.1.3.2.3.3-1: RRCReconfigurationSidelink (step 1, Table 12.1.3.2.3.2-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition RX and SL_MEAS

Table 12.1.3.2.3.3-2: SL-ReportConfigList (69) (Table 12.1.3.2.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-24 with condition EVENT_S1

Table 12.1.3.2.3.3-3: MeasurementReportSidelink (step 5, 10, Table 12.1.3.2.3.2-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-2 with condition TX

Table 12.1.3.2.3.3-4: RRCReconfigurationSidelink (step 6, Table 12.1.3.2.3.2-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition RX and SL_MEAS

Table 12.1.3.2.3.3-5: SL-ReportConfigList (69) (Table 12.1.3.2.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-24 with condition EVENT_S2

12.1.3.3 PC5-only operation / Measurement configuration and reporting via PC5 RRC / PSBCH-RSRP measurement reporting / Periodical reporting

12.1.3.3.1 Test Purpose (TP)

(1)

with { UE being configured to perform periodical PSBCH-RSRP measurement reporting on SL SSB via PC5 RRC }

ensure that {

when { The first measurement result is available and thereafter every time periodical timer expires until sl-NumberOfReportsSent is equal to sl-ReportAmount }

then { UE triggers PSBCH-RSRP measurement reporting }

}

12.1.3.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.10.2.1, 5.8.10.2.3, 5.8.10.2.5, 5.8.10.2.7, 5.8.10.3.1, 5.8.10.3.2, 5.8.10.4.1 and 5.8.10.5.1. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.10.2.1]

The UE shall:

….

1> if the received sl-MeasConfig includes the sl-MeasObjectToAddModList in the RRCReconfigurationSidelink:

2> perform the sidelink measurement object addition/modification procedure as specified in 5.8.10.2.5;

…

1> if the received sl-MeasConfig includes the sl-ReportConfigToAddModList in the RRCReconfigurationSidelink:

2> perform the sidelink reporting configuration addition/modification procedure as specified in 5.8.10.2.7;

1> if the received sl-MeasConfig includes the sl-QuantityConfig in the RRCReconfigurationSidelink:

2> perform the sidelink quantity configuration procedure as specified in 5.8.10.2.8;

…

1> if the received sl-MeasConfig includes the sl-MeasIdToAddModList in the RRCReconfigurationSidelink:

2> perform the sidelink measurement identity addition/modification procedure as specified in 5.8.10.2.3;

[TS 38.331, subclause 5.8.10.2.3]

The UE shall:

1> for each sl-MeasId included in the received sl-MeasIdToAddModList:

2> if an entry with the matching sl-MeasId exists in the sl-MeasIdList within the VarMeasConfigSL:

3> replace the entry with the value received for this sl-MeasId;

2> else:

3> add a new entry for this sl-MeasId within the VarMeasConfigSL;

2> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included;

2> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId;

[TS 38.331, subclause 5.8.10.2.5]

The UE shall:

1> for each sl-MeasObjectId included in the received sl-MeasObjectToAddModList:

2> if an entry with the matching sl-MeasObjectId exists in the sl-MeasObjectList within the VarMeasConfigSL, for this entry:

3> for each sl-MeasId associated with this sl-MeasObjectId included in the sl-MeasIdList within the VarMeasConfigSL, if any:

4> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included;

4> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId;

3> reconfigure the entry with the value received for this sl-MeasObject;

2> else:

3> add a new entry for the received sl-MeasObject to the sl-MeasObjectList within VarMeasConfigSL.

[TS 38.331, subclause 5.8.10.2.7]

The UE shall:

1> for each sl-ReportConfigId included in the received sl-ReportConfigToAddModList:

2> if an entry with the matching sl-ReportConfigId exists in the sl-ReportConfigList within the VarMeasConfigSL, for this entry:

3> reconfigure the entry with the value received for this sl-ReportConfig;

3> for each sl-MeasId associated with this sl-ReportConfigId included in the sl-MeasIdList within the VarMeasConfigSL, if any:

4> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included;

4> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId;

2> else:

3> add a new entry for the received sl-ReportConfig to the sl-ReportConfigList within the VarMeasConfigSL.

[TS 38.331, subclause 5.8.10.3.1]

A UE shall derive NR sidelink measurement results by measuring one or multiple DMRS associated per PC5-RRC connection as configured by the peer UE associated, as described in 5.8.10.3.2. For all NR sidelink measurement results the UE applies the layer 3 filtering as specified in sub-clause 5.5.3.2, before using the measured results for evaluation of reporting criteria and measurement reporting. In this release, only NR sidelink RSRP can be configured as trigger quantity and reporting quantity.

The UE shall:

1> for each sl-MeasId included in the sl-MeasIdList within VarMeasConfigSL:

2> if the sl-MeasObject is associated to NR sidelink and the sl-RS-Type is set to dmrs:

3> derive the layer 3 filtered NR sidelink measurement result based on DMRS for the trigger quantity and each measurement quantity indicated in sl-ReportQuantity using parameters from the associated sl-MeasObject, as described in 5.8.10.3.2.

2> perform the evaluation of reporting criteria as specified in 5.8.10.4.

[TS 38.331, subclause 5.8.10.3.2]

The UE may be configured by the peer UE associated to derive NR sidelink RSRP measurement results per PC5-RRC connection associated to the NR sidelink measurement objects based on parameters configured in the sl-MeasObject and in the sl-ReportConfig.

The UE shall:

1> for each NR sidelink measurement quantity to be derived based on NR sidelink DMRS:

2> derive the corresponding measurement of NR sidelink frequency indicated quantity based on DMRS as described in TS 38.215 [9] in the concerned sl-MeasObject;

2> apply layer 3 filtering as described in 5.5.3.2;

[TS 38.331, subclause 5.8.10.4.1]

The UE shall:

1> for each sl-MeasId included in the sl-MeasIdList within VarMeasConfigSL:

…

2> if sl-ReportType is set to sl-Periodical and if a (first) NR sidelink measurement result is available:

3> include a NR sidelink measurement reporting entry within the VarMeasReportListSL for this sl-MeasId;

3> set the sl-NumberOfReportsSent defined within the VarMeasReportListSL for this sl-MeasId to 0;

3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5, immediately after the quantity to be reported becomes available for the NR sidelink frequency:

2> upon expiry of the periodical reporting timer for this sl-MeasId:

3> initiate the NR sidelink measurement reporting procedure, as specified in 5.8.10.5.

[TS 38.331, subclause 5.8.10.5.1]

Figure 5.8.10.5.1-1: NR sidelink measurement reporting

The purpose of this procedure is to transfer measurement results from the UE to the peer UE associated.

For the sl-MeasId for which the NR sidelink measurement reporting procedure was triggered, the UE shall set the sl-MeasResults within the MeasurementReportSidelink message as follows:

1> set the sl-MeasId to the measurement identity that triggered the NR sidelink measurement reporting;

1> if the sl-ReportConfig associated with the sl-MeasId that triggered the NR sidelink measurement reporting is set to sl-EventTriggered or sl-Periodical:

2> set sl-ResultDMRS within sl-MeasResult to include the NR sidelink DMRS based quantity indicated in the sl-ReportQuantity within the concerned sl-ReportConfig;

1> increment the sl-NumberOfReportsSent as defined within the VarMeasReportListSSL for this sl-MeasId by 1;

1> stop the periodical reporting timer, if running;

1> if the sl-NumberOfReportsSent as defined within the VarMeasReportListSL for this sl-MeasId is less than the sl-ReportAmount as defined within the corresponding sl-ReportConfig for this sl-MeasId:

2> start the periodical reporting timer with the value of sl-ReportInterval as defined within the corresponding sl-ReportConfig for this sl-MeasId;

1> else:

2> if the sl-ReportType is set to sl-Periodical:

3> remove the entry within the VarMeasReportListSL for this sl-MeasId;

3> remove this sl-MeasId from the sl-MeasIdList within VarMeasConfigSL;

1> submit the MeasurementReportSidelink message to lower layers for transmission, upon which the procedure ends.

12.1.3.3.3 Test description

12.1.3.3.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE1: operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE1 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 containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.

– The UE uses GNSS as the synchronization reference source.

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4] subclause 4.4A using generic procedure defined in TS 38.508-1[4] clause 4.5.7 with parameters Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.22.

12.1.3.3.3.2 Test procedure sequence

Table 12.1.3.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

The NR-SS-UE1 transmits SLSS & MasterInformationBlockSidelink (Note 1).

<–

PC5 RRC: SLSS & MasterInformationBlockSidelink

–

–

1

The NR-SS-UE1 transmits a RRCReconfigurationSidelink message on SL-SRB3.

<–

PC5 RRC: RRCReconfigurationSidelink

–

–

2

The UE transmits a RRCReconfigurationCompleteSidelink message on SL-SRB3.

–>

PC5 RRC: RRCReconfigurationCompleteSidelink

–

–

3

Check: Does the UE transmit a MeasurementReportSidelink message to perform periodical reporting?

–>

PC5 RRC: MeasurementReportSidelink

1

P

–

EXCEPTION: After the 1st MeasurementReportSidelink message at step 3 is received, step 4 below is repeated until 15 MeasurementReport messages are received from the UE. The interval between two MeasurementReportSidelink shall be as specified by the IE sl-ReportInterval

–

–

–

–

4

Check: Does the UE transmit a MeasurementReportSidelink message to perform periodical reporting?

–>

PC5 RRC: MeasurementReportSidelink

1

P

Note 1: UE is using TS 38.508-1 [4] Table 4.6.6-31: SL-SyncConfig parameters to transmit SLSS.

12.1.3.3.3.3 Specific message contents

Table 12.1.3.3.3.3-0: SL-SyncConfig (step 0, Table 12.1.3.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-31

Information Element

Value/remark

Comment

Condition

SL-SyncConfig-r16 ::= SEQUENCE {

gnss-Sync-r16

true

}

Table 12.1.3.3.3.3-0A: MasterInformationBlockSidelink (step 0, Table 12.1.3.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-1 with condition RX AND GNSS_SYNC

Table 12.1.3.3.3.3-1: RRCReconfigurationSidelink (step 1, Table 12.1.3.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition SL_MEAS and RX

Information Element

Value/remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

sl-MeasConfig-r16 CHOICE {

setup SEQUENCE {

sl-ReportConfigToAddModList-r16

SL-ReportConfigList-r16

Table 12.1.3.3.3.3-2

}

}

}

}

}

Table 12.1.3.3.3.3-2: SL-ReportConfigList-r16 (Table 12.1.3.3.3.3-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-24 with condition PERIODICAL

Information Element

Value/remark

Comment

Condition

SL-ReportConfigList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ReportConfigId-r16)) OF SL-ReportConfigInfo-r16 {

1 entry

SL-ReportConfigInfo-r16[1] SEQUENCE {

entry 1

sl-ReportConfig-r16 SEQUENCE {

sl-ReportType-r16 CHOICE {

sl-Periodical-r16 SEQUENCE {

sl-ReportAmount-r16

r16

}

}

}

}

}

Table 12.1.3.3.3.3-3: RRCReconfigurationCompleteSidelink (step 2, Table 12.1.3.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-4 with condition TX

Table 12.1.3.3.3.3-4: MeasurementReportSidelink (step 3, step 4, Table 12.2.5.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-2 with condition TX

12.1.4 PC5-only operation / Sidelink Reconfiguration via PC5 RRC

12.1.4.1 PC5-only operation / Sidelink Reconfiguration via PC5 RRC / SL-DRB management / initiating UE side

12.1.4.1.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE }

ensure that {

when { UE is configured by higher layer to transmit a PC5 RRCReconfiguration message to establish a unicast SL-DRB }

then { UE sends a RRCReconfigurationSidelink message to peer UE }

}

(2)

with { UE having established PC5 RRC connection with peer UE }

ensure that {

when { UE is configured by higher layer to transmit a PC5 RRCReconfiguration message to modify a unicast SL-DRB }

then { UE sends a RRCReconfigurationSidelink message to peer UE }

}

(3)

with { UE having established PC5 RRC connection with peer UE }

ensure that {

when { UE is configured by higher layer to transmit a PC5 RRCReconfiguration message to release a unicast SL-DRB }

then { UE sends a RRCReconfigurationSidelink message to peer UE }

}

12.1.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 , subclause 5.8.9.1a.1.2, 5.8.9.1a.2.1, 5.8.9.1a.2.2. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.9.1a.1.2]

For each sidelink DRB, whose sidelink DRB release conditions are met as in sub-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 (TS 37.324 [24], clause 5.3.3);

2> release SDAP entities for NR sidelink communication, if any, that have no associated sidelink DRB as specified in TS 37.324 [24] clause 5.1.2;

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

[TS 38.331, subclause 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;

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;

[TS 38.331, subclause 5.8.9.1a.2.2]

For the sidelink DRB, whose sidelink DRB addition conditions are met as in sub-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 TS 37.324 [24] clause 5.1.1;

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

2> if this procedure was due to the reception of a RRCReconfigurationSidelink message:

3> 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 sub-clause 5.8.3 for unicast if need;

2> else:

3> configure the MAC entity with a logical channel associated with the sidelink DRB, by assigning a new logical channel identity, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR.

NOTE 1: When a sidelink DRB addition is due to the configuration by RRCReconfigurationSidelink, it is up to UE implementation to select the sidelink DRB configuration as necessary transmitting parameters for the sidelink DRB, from the received sl-ConfigDedicatedNR (if in RRC_CONNECTED), SIB12 (if in RRC_IDLE/INACTIVE), SidelinkPreconfigNR (if out of coverage) with the same RLC mode as the one configured in RRCReconfigurationSidelink.

For the sidelink DRB, whose sidelink DRB modification conditions are met as in sub-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.

12.1.4.1.3 Test description

12.1.4.1.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– GNSS simulator

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

– NR-SS-UE 1 is synchronised on GNSS.

UE:

– UE is authorised to perform NR sidelink communication.

– The UE is equipped with a USIM containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.

– UE is synchronised on GNSS.

Preamble:

– The UE is in state 0-A as defined in TS 38.508-1 [4].

12.1.4.1.3.2 Test procedure sequence

Table 12.1.4.1.3.2-1: Main behaviour

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power on the UE.

–

–

–

–

2

Trigger UE to reset or clear the current UTC time that has been calculated from GNSS.

NOTE: The UTC time can be reset or clear on the UE using AT command (+CUTCR).

–

–

–

–

3

The UE is configured by upper layer to establish unicast mode link.

NOTE: This can be done by sending AT COMMAND +CCUTLE to close test loop function.

–

–

–

–

4

The UE sends a DIRECT LINK ESTABLISHMENT REQUEST message.

–>

PC5-S: DIRECT LINK ESTABLISHMENT REQUEST

–

–

5

The NR-SS-UE sends a DIRECT LINK SECURITY MODE COMMAND message.

<–

PC5-S: DIRECT LINK SECURITY MODE COMMAND

–

–

6

The UE sends a DIRECT LINK SECURITY MODE COMPLETE message.

–>

PC5-S: DIRECT LINK SECURITY MODE COMPLETE

–

–

7

The NR-SS-UE sends a DIRECT LINK ESTABLISHMENT ACCEPT message.

<–

PC5-S: DIRECT LINK ESTABLISHMENT ACCEPT

–

–

8

Check: Does the UE send an RRCReconfigurationSidelink message to establish a unicast mode SL-DRB?

–>

PC5-RRC: RRCReconfigurationSidelink

1

P

9

The NR-SS-UE sends an RRCReconfigurationCompleteSidelink message.

<–

PC5-RRC: RRCReconfigurationCompleteSidelink

–

–

10

The SS sends AT COMMAND +CCUTLE to open test loop function

–

–

–

–

11

UE is configured by upper layer to modify SL-DRB to NR-SS-UE1.

NOTE: This step is triggered by MMI or AT command.

–

–

–

–

12

Check: Does the UE send an RRCReconfigurationSidelink message to modify the unicast mode SL-DRB?

–>

PC5-RRC: RRCReconfigurationSidelink

2

P

13

The NR-SS-UE sends an RRCReconfigurationCompleteSidelink message.

<–

PC5-RRC: RRCReconfigurationCompleteSidelink

–

–

14

UE is configured by upper layer to release SL-DRB to NR-SS-UE1.

Note: This step is triggered by MMI or AT command.

—

–

–

–

15

Check: Does the UE send an RRCReconfigurationSidelink message to NR-SS-UE1 to indicate SL-DRB release?

–>

PC5 RRC: RRCReconfigurationSidelink

3

P

16

The NR-SS-UE sends an RRCReconfigurationCompleteSidelink message to confirm SL-DRB release.

<–

PC5-RRC: RRCReconfigurationCompleteSidelink

–

–

12.1.4.1.3.3 Specific message contents

Table 12.1.4.1.3.3-1: DIRECT LINK ESTABLISHMENT REQUEST (step 4, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.4-7 with condition Tx

Table 12.1.4.1.3.3-2: Message DIRECT LINK SECURITY MODE COMMAND (step 5, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.4-18 with condition Rx

Table 12.1.4.1.3.3-3: Message DIRECT LINK SECURITY MODE COMPLETE (step 6, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.4-19 with condition Tx

Table 12.1.4.1.3.3-4: Message DIRECT LINK ESTABLISHMENT ACCEPT (step 7, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.4-8 with condition Rx

Table 12.1.4.1.3.3-5: RRCReconfigurationSidelink (step 8, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3, conditions TX and SL_DRB

Table 12.1.4.1.3.3-6: RRCReconfigurationCompleteSidelink (steps 9, 13 & 16, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-4, conditions RX

Table 12.1.4.1.3.3-7: RRCReconfigurationSidelink (step 12, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3, conditions TX and SL_DRB

Table 12.1.4.1.3.3-8: RRCReconfigurationSidelink (step 15, Table 12.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3, condition TX

Information Element

Value/Remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 {

1 entry

SLRB-PC5-ConfigIndex-r16 [1]

1

entry 1

}

}

}

}

12.1.4.2 PC5-only operation / Sidelink Reconfiguration via PC5 RRC / SL DRB management / Peer UE side

12.1.4.2.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE}

ensure that {

when { UE receives an RRCReconfigurationSidelink that can comply to add an unicast SL-DRB}

then { UE applies the parameters in RRCReconfigurationSidelink and sends a RRCReconfigurationCompleteSidelink message to peer UE}

}

(2)

with { UE having established PC5 RRC connection with peer UE }

ensure that {

when { UE receives an RRCReconfigurationSidelink that can comply to modify an unicast SL-DRB}

then {UE applies the parameters in RRCReconfigurationSidelink and sends a RRCReconfigurationCompleteSidelink message to peer UE }

}

(3)

with { UE having established PC5 RRC connection with peer UE }

ensure that {

when { UE receives an RRCReconfigurationSidelink that can comply to release an unicast SL-DRB}

then { UE applies the parameters in RRCReconfigurationSidelink and sends a RRCReconfigurationCompleteSidelink message to peer UE}

}

12.1.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 , subclause 5.8.9.1a.1.2, 5.8.9.1a.2.1, 5.8.9.1a.2.2. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.9.1a.1.2]

For each sidelink DRB, whose sidelink DRB release conditions are met as in sub-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 (TS 37.324 [24], clause 5.3.3);

2> release SDAP entities for NR sidelink communication, if any, that have no associated sidelink DRB as specified in TS 37.324 [24] clause 5.1.2;

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

[TS 38.331, subclause 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;

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;

[TS 38.331, subclause 5.8.9.1a.2.2]

For the sidelink DRB, whose sidelink DRB addition conditions are met as in sub-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 TS 37.324 [24] clause 5.1.1;

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

2> if this procedure was due to the reception of a RRCReconfigurationSidelink message:

3> 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 sub-clause 5.8.3 for unicast if need;

2> else:

3> configure the MAC entity with a logical channel associated with the sidelink DRB, by assigning a new logical channel identity, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR.

NOTE 1: When a sidelink DRB addition is due to the configuration by RRCReconfigurationSidelink, it is up to UE implementation to select the sidelink DRB configuration as necessary transmitting parameters for the sidelink DRB, from the received sl-ConfigDedicatedNR (if in RRC_CONNECTED), SIB12 (if in RRC_IDLE/INACTIVE), SidelinkPreconfigNR (if out of coverage) with the same RLC mode as the one configured in RRCReconfigurationSidelink.

For the sidelink DRB, whose sidelink DRB modification conditions are met as in sub-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.

12.1.4.2.3 Test description

12.1.4.2.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– GNSS simulator

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

– NR-SS-UE 1 is synchronised on GNSS.

UE:

– UE is authorised to perform NR sidelink communication.

– The UE is equipped with a USIM containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.

– UE is synchronised on GNSS.

Preamble:

– The UE is in state 0-A as defined in TS 38.508-1 [4].

12.1.4.2.3.2 Test procedure sequence

Table 12.1.4.2.3.2-1: Main behaviour

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power on the UE.

–

–

–

–

2

Trigger UE to reset or clear the current UTC time that has been calculated from GNSS.

NOTE: The UTC time can be reset or clear on the UE using AT command (+CUTCR).

–

–

–

–

3

The NR-SS-UE sends a DIRECT LINK ESTABLISHMENT REQUEST message.

<–

PC5-S: DIRECT LINK ESTABLISHMENT REQUEST

4

The UE sends a DIRECT LINK SECURITY MODE COMMAND message.

–>

PC5-S: DIRECT LINK SECURITY MODE COMMAND

–

–

5

The NR-SS-UE sends a DIRECT LINK SECURITY MODE COMPLETE message.

<–

PC5-S: DIRECT LINK SECURITY MODE COMPLETE

–

–

6

The UE sends a DIRECT LINK ESTABLISHMENT ACCEPT message.

–>

PC5-S: DIRECT LINK ESTABLISHMENT ACCEPT

–

–

7

The NR-SS-UE sends a RRCReconfigurationSidelink message to establish a unicast mode SL-DRB.

<–

PC5-RRC: RRCReconfigurationSidelink

–

–

8

Check: Does the UE send a RRCReconfigurationCompleteSidelink message?

–>

PC5-RRC: RRCReconfigurationCompleteSidelink

1

P

9

The NR-SS-UE sends a RRCReconfigurationSidelink message to indicate modification of unicast mode SL-DRB.

<–

PC5-RRC: RRCReconfigurationSidelink

–

–

10

Check: Does the UE send a RRCReconfigurationCompleteSidelink message?

–>

PC5-RRC: RRCReconfigurationCompleteSidelink

2

P

11

The NR-SS-UE sends a RRCReconfigurationSidelink message to indicate release of unicast mode SL DRB.

<–

PC5-RRC: RRCReconfigurationSidelink

–

–

12

Check: The UE sends a RRCReconfigurationSidelinkComplete message?

–>

PC5-RRC: RRCReconfigurationSidelinkComplete

3

P

12.1.4.2.3.3 Specific message contents

Editor’s note: content missing for some of the changes.

Table 12.1.4.2.3.3-1: RRCReconfigurationSidelink (step 7, Table 12.1.4.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 Conditions RX and SL_DRB

Table 12.1.4.2.3.3-2: RRCReconfigurationSidelink (step 11, Table 12.1.4.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 Conditions RX and SL_DRB

Information Element

Value/remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

slrb-ConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Config-r16 {

1 entry

SLRB-Config-r16[1] SEQUENCE {

entry 1

sl-PDCP-ConfigPC5-r16 SEQUENCE {

sl-PDCP-SN-Size-r16

len12bits

sl-OutOfOrderDelivery-r16

true

}

}

}

}

}

Table 12.1.4.2.3.3-3: RRCReconfigurationSidelink (step 14, Table 12.1.4.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3

Information Element

Value/Remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 {

1 entry

SLRB-PC5-ConfigIndex-r16 [1]

1

entry 1

}

}

}

}

12.1.5 PC5-only operation / Sidelink CSI reporting

12.1.5.1 PC5-only operation / Sidelink CSI reporting / Configuration

12.1.5.1.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE }

ensure that {

when { UE is configured by upper layer to configure SL CSI-RS resource to peer UE }

then { UE sends an RRCReconfigurationSidelink message including sl-CSI-RS-Config to peer UE and starts transmitting SL CSI-RS }

}

(2)

with { UE having established PC5 RRC connection with peer UE }

ensure that {

when { UE is configured by upper layer to trigger SL CSI report }

then { UE sends an SCI format 2-A to trigger SL CSI report }

}

12.1.5.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1.1, 5.8.9.1.2, 5.8.9.1.3. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.8.9.1.1]

General

Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful

Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure

The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources and CSI reporting latency bound.

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> set the sl-MeasConfig as follows:

2> If the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList 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> start timer T400 for the destination associated with the sidelink DRB;

1> set the sl-CSI-RS-Config;

1> set the sl-LatencyBoundCSI-Report,

NOTE 1: How to set the parameters included in sl-CSI-RS-Config and sl-LatencyBoundCSI-Report is up to UE implementation.

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

[TS 38.331, clause 5.8.9.1.3]

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

1> if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList:

2> for each SLRB-PC5-ConfigIndex value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration;

3> perform the sidelink DRB release procedure, according to sub-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 sub-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 sub-clause 5.8.9.1a.1.1 are met:

4> perform the sidelink DRB release procedure according to sub-clause 5.8.9.1a.1.2;

3> else if the sidelink DRB modification conditions as described in sub-clause 5.8.9.1a.2.1 are met:

4> perform the sidelink DRB modification procedure according to sub-clause 5.8.9.1a.2.2;

1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig:

2> perform the sidelink measurement configuration procedure as specified in 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 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> else:

2> set the content of the RRCReconfigurationCompleteSidelink message;

3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission;

NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure.

12.1.5.1.3 Test description

12.1.5.1.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE1 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 uses GNSS as the synchronization reference source.

– The UE is equipped with below information in UE or in a USIM containing default values (as per TS 38.508-1 [4] clause 4.8.3.3.3) except for those listed in Table 12.1.5.1.3.1-1.

Table 12.1.5.1.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

service no. 119 is available

EFVST

Service no.2 V2X policy configuration data over PC5 is supported, i.e. value is ’01 02′ HEX

EFV2XP_PC5

As per TS 38.508-1[4] clause 4.8.3.3.3

SL-PreconfigurationNR included in V2X data policy over PC5 is defined in Table 12.1.5.1.3.3-1

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.22.

12.1.5.1.3.2 Test procedure sequence

Table 12.1.5.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE is configured by upper layer to configure SL CSI-RS resource to NR-SS-UE1.

Note: This step is triggered by MMI or AT command.

–

–

–

–

2

Check: Does UE send a RRCReconfigurationSidelink message including sl-CSI-RS-Config?

–>

PC5 RRC: RRCReconfigurationSidelink

1

P

3

Check: Does UE start transmitting SL CSI-RS?

–>

–

1

P

4

NR-SS-UE1 sends a RRCReconfigurationCompleteSidelink message

<–

PC5 RRC: RRCReconfigurationCompleteSidelink

5

UE is configured by upper layer to trigger SL CSI report.

Note: This step is triggered by MMI or AT command.

–

–

–

–

6

Check: Does the UE transmit an SCI format 2-A with CSI request = “1” to trigger SL CSI report?

–>

PSSCH (SCI 2-A)

2

P

12.1.5.1.3.3 Specific message contents

Table 12.1.5.1.3.3-1: SL-PreconfigurationNR

Derivation path: TS 38.508-1 [4], Table 4.10.1-1

Information Element

Value/Remark

Comment

Condition

SL-PreconfigurationNR-r16 ::= SEQUENCE {

sidelinkPreconfigNR-r16 SEQUENCE {

sl-CSI-Acquisition-r16

enabled

}

}

Table 12.1.5.1.3.3-2: RRCReconfigurationSidelink (step 2, Table 12.1.5.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 with condition SL_CSI and TX

Table 12.1.5.1.3.3-3: RRCReconfigurationCompleteSidelink (step 4, Table 12.1.5.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-4 with condition RX

12.1.5.2 PC5-only operation / Sidelink CSI reporting / Reporting

12.1.5.2.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE and configured by peer UE to perform CSI measurement}

ensure that {

when { UE receives a SCI format 2-A to trigger SL CSI report}

then { UE sends an CSI reporting MAC-CE to peer UE }

}

12.1.5.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1.1,5.8.9.1.2,5.8.9.1.3, TS 38.321, clause 6.1.3.35. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.8.9.1.1]

General

Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful

Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure

The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources and CSI reporting latency bound.

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> set the sl-MeasConfig as follows:

2> If the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList 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> start timer T400 for the destination associated with the sidelink DRB;

1> set the sl-CSI-RS-Config;

1> set the sl-LatencyBoundCSI-Report,

NOTE 1: How to set the parameters included in sl-CSI-RS-Config and sl-LatencyBoundCSI-Report is up to UE implementation.

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

[TS 38.331, clause 5.8.9.1.3]

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

1> if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList:

2> for each SLRB-PC5-ConfigIndex value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration;

3> perform the sidelink DRB release procedure, according to sub-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 sub-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 sub-clause 5.8.9.1a.1.1 are met:

4> perform the sidelink DRB release procedure according to sub-clause 5.8.9.1a.1.2;

3> else if the sidelink DRB modification conditions as described in sub-clause 5.8.9.1a.2.1 are met:

4> perform the sidelink DRB modification procedure according to sub-clause 5.8.9.1a.2.2;

1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig:

2> perform the sidelink measurement configuration procedure as specified in 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 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> else:

2> set the content of the RRCReconfigurationCompleteSidelink message;

3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission;

NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure.

[TS 38.321, clause 6.1.3.35]

The Sidelink CSI Reporting MAC CE is identified by a MAC subheader with LCID as specified in Table 6.2.4-1. The priority of the Sidelink CSI Reporting MAC CE is fixed to ‘1’. The Sidelink CSI Reporting MAC CE is defined as follows (Figure 6.1.3.35-1):

– RI: This field indicates the derived value of the Rank Indicator for sidelink CSI reporting as specified in clause 8.5 of TS 38.214 [7]. The length of the field is 1 bit;

– CQI: This field indicates the derived value of the Channel Quality Indicator for sidelink CSI reporting as specified in clause 8.5 of TS 38.214 [7]. The length of the field is 4 bit;

– R: Reserved bit, set to 0.

Figure 6.1.3.35-1: Sidelink CSI Reporting MAC CE

12.1.5.2.3 Test description

12.1.5.2.3.1 Pre-test conditions

System Simulator:

– SS-UE

– NR-SS-UE1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE1 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 uses GNSS as the synchronization reference source.

– The UE is equipped with below information in UE or in a USIM containing default values (as per TS 38.508-1 [4] clause 4.8.3.3.3) except for those listed in Table 12.1.5.2.3.1-1.

Table 12.1.5.2.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

service no. 119 is available

EFVST

Service no.2 V2X policy configuration data over PC5 is supported, i.e. value is ’01 02′ HEX

EFV2XP_PC5

As per TS 38.508-1[4] clause 4.8.3.3.3

SL-PreconfigurationNR included in V2X data policy over PC5 is defined in Table 12.1.5.2.3.3-1

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.22.

12.1.5.2.3.2 Test procedure sequence

Table 12.1.5.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

NR-SS-UE1 sends an RRCReconfigurationSidelink message including sl-CSI-RS-Config and starts to transmit SL CSI-RS.

<–

PC5 RRC: RRCReconfigurationSidelink

–

–

2

UE sends a RRCReconfigurationCompleteSidelink message

–>

PC5 RRC: RRCReconfigurationCompleteSidelink

–

–

3

NR-SS-UE1 sends a SCI format 2-A with CSI request = “1” to trigger SL CSI report.

<–

PSSCH (SCI 2-A)

–

–

4

Check: Does UE send a CSI reporting MAC-CE to NR-SS-UE1?

–>

MAC CE (sidelink CSI)

1

P

12.1.5.2.3.3 Specific message contents

Table 12.1.5.2.3.3-1: SL-PreconfigurationNR

Derivation path: TS 38.508-1 [4], Table 4.10.1-1

Information Element

Value/Remark

Comment

Condition

SL-PreconfigurationNR-r16 ::= SEQUENCE {

sidelinkPreconfigNR-r16 SEQUENCE {

sl-CSI-Acquisition-r16

enabled

}

}

Table 12.1.5.2.3.3-2: RRCReconfigurationSidelink (step 1, Table 12.1.5.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 with condition RX

Table 12.1.5.2.3.3-3: RRCReconfigurationCompleteSidelink (step 2, Table 12.1.5.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-4 with condition TX

12.1.6 PC5-only operation / Sidelink failure

12.1.6.1 PC5-only operation / Sidelink failure / PC5 RRC reconfiguration failure / Initiating UE side

12.1.6.1.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE on unicast sidelink }

ensure that {

when { UE receives a RRCReconfigurationFailureSidelink from peer UE}

then { UE continues using the configuration used prior to corresponding RRCReconfigurationSidelink message}

}

12.1.6.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1.1, 5.8.9.1.8. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.9.1.1]

…

Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure

[TS 38.331, subclause 5.8.9.1.8]

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 5.8.3.3 or sub-clause 5.10.15 in TS 36.331 [10];

12.1.6.1.3 Test description

12.1.6.1.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE 1 is as defined in TS 38.508-1 [4], configured for and operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE 1 is synchronised on GNSS.

– 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 containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.

– UE is synchronised on GNSS.

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.22.

12.1.6.1.3.2 Test procedure sequence

Table 12.1.6.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE is configured by upper layer to release SL-DRB to NR-SS-UE1.

Note: This step is triggered by MMI or AT command.

–

–

–

–

2

UE sends an RRCReconfigurationSidelink message to NR-SS-UE1 to indicate SL-DRB release?

–>

PC5 RRC: RRCReconfigurationSidelink

–

–

3

The NR-SS-UE1 sends a RRCReconfigurationFailureSidelink message.

<–

PC5 RRC: RRCReconfigurationFailureSidelink

–

–

4

Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.31 indicate the UE still has SL-DRB configured in preamble?

–

–

1

–

12.1.6.1.3.3 Specific message contents

Table 12.1.6.1.3.3-1: RRCReconfigurationSidelink (step 2, Table 12.1.6.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 with condition TX

Information Element

Value/Remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 {

1 entry

SLRB-PC5-ConfigIndex-r16 [1]

1

Index value to refer to a different value than TS 38.508-1[4] Table 4.6.6-37

}

}

}

}

Table 12.1.6.1.3.3-2: RRCReconfigurationFailureSidelink (step 3, Table 12.1.6.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-5 with condition RX

12.1.6.2 PC5-only operation / Sidelink failure / PC5 RRC reconfiguration failure / Peer UE side

12.1.6.2.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE on unicast sidelink}

ensure that {

when { UE receives an RRCReconfigurationSidelink that UE cannot comply from peer UE }

then { UE continues using the configuration used prior to corresponding RRCReconfigurationSidelink message and sends a RRCReconfigurationFailureSidelink message }

}

12.1.6.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1.1, 5.8.9.1.3. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.9.1.1]

…

Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure

[TS 38.331, subclause 5.8.9.1.3]

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

1> if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList:

2> for each SLRB-PC5-ConfigIndex value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration;

3> perform the sidelink DRB release procedure, according to sub-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 sub-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 sub-clause 5.8.9.1a.1.1 are met:

4> perform the sidelink DRB release procedure according to sub-clause 5.8.9.1a.1.2;

3> else if the sidelink DRB modification conditions as described in sub-clause 5.8.9.1a.2.1 are met:

4> perform the sidelink DRB modification procedure according to sub-clause 5.8.9.1a.2.2;

1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig:

2> perform the sidelink measurement configuration procedure as specified in 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 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> else:

2> set the content of the RRCReconfigurationCompleteSidelink message;

3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission;

NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure.

12.1.6.2.3 Test description

12.1.6.2.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE 1 is as defined in TS 38.508-1 [4], configured for and operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE 1 is synchronised on GNSS.

– GNSS simulator

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

UE:

  • UE is authorised to perform NR sidelink communication.
  • UE is synchronised on GNSS.
  • The UE is equipped with a USIM containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using NR-SS-UE1 initiated unicast mode NR sidelink communication procedure in subclause 4.9.23.

12.1.6.2.3.2 Test procedure sequence

Table 12.1.6.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The NR-SS-UE1 sends a RRCReconfigurationSidelink message to UE to indicate SL-DRB release with SLRB-PC5-ConfigIndex-r16 pointing to SL-DRB which has not been configured yet?

<–

PC5 RRC: RRCReconfigurationSidelink

–

–

2

Check: Does the UE sends an RRCReconfigurationFailureSidelink message.

–>

PC5 RRC: RRCReconfigurationFailureSidelink

1

P

3

Check: Does the test result of generic test procedure in TS 38.508-1 subclause 4.9.31 indicate the UE still has SL-DRB configured in preamble?

–

–

1

–

12.1.6.2.3.3 Specific message contents

Table 12.1.6.2.3.3-1: RRCReconfigurationSidelink (step 1, Table 12.1.6.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 with condition RX

Information Element

Value/Remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 {

1 entry

SLRB-PC5-ConfigIndex-r16 [1]

2

Index value to refer to a different value than TS 38.508-1[4] Table 4.6.6-37

}

}

}

}

Table 12.1.6.2.3.3-2: RRCReconfigurationFailureSidelink (step 2, Table 12.1.6.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-5 with condition TX

12.1.6.3 PC5-only operation / Sidelink failure / Sidelink radio link failure / Transmission side

12.1.6.3.1 Test Purpose (TP)

(1)

with { UE having established PC5 RRC connection with peer UE on unicast sidelink and has sent an RRCReconfigurationSidelink message to peer UE }

ensure that {

when { UE does not receive RRCReconfigurationCompleteSidelink or RRCReconfigurationFailure before T400 expires}

then { UE releases PC5-RRC connection and indicates the release to upper layer}

}

(2)

with { UE having established PC5 RRC connection with peer UE on unicast sidelink and has established a AM SL-DRB}

ensure that {

when { Retransmission number of the AM SL-DRB reaches the maximum number of retransmissions}

then { UE releases PC5-RRC connection and indicates the release to upper layer.}

}

(3)

with { UE having established PC5 RRC connection with peer UE on unicast sidelink }

ensure that {

when { MAC detects that maximum number of consecutive HARQ DTX has been reached }

then { UE releases PC5-RRC connection and indicates the release to upper layer }

}

12.1.6.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.3. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.9.3]

The UE shall:

1> upon indication from sidelink RLC entity that the maximum number of retransmissions for a specific destination has been reached; or

1> upon T400 expiry for a specific destination; or

1> upon indication from MAC entity that the maximum number of consecutive HARQ DTX for a specific destination has been reached; or

1> upon integrity check failure indication from sidelink PDCP entity concerning SL-SRB2 or SL-SRB3 for a specific destination:

2> consider sidelink radio link failure to be detected for this destination;

2> release the DRBs of this destination, in according to sub-clause 5.8.9.1a.1;

2> release the SRBs of this destination, in according to sub-clause 5.8.9.1a.3;

2> discard the NR sidelink communication related configuration of this destination;

2> reset the sidelink specific MAC of this destination;

2> consider the PC5-RRC connection is released for the destination;

2> indicate the release of the PC5-RRC connection to the upper layers for this destination (i.e. PC5 is unavailable);

2> if UE is in RRC_CONNECTED:

3> perform the sidelink UE information for NR sidelink communication procedure, as specified in 5.8.3.3;

NOTE: It is up to UE implementation on whether and how to indicate to upper layers to maintain the keep-alive procedure [55].

12.1.6.3.3 Test description

12.1.6.3.3.1 Pre-test conditions

System Simulator:

– NR-SS-UE

– NR-SS-UE 1 is as defined in TS 38.508-1 [4], configured for and operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE 1 is synchronised on GNSS.

– 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 containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3.
  • UE is synchronised on GNSS.

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On) using UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.23.

12.1.6.3.3.2 Test procedure sequence

Table 12.1.6.3.3.2-1: Specific Parameters

Parameter

Value

Comment

sl-MaxRetxThreshold-r16

1

sl-MaxNumConsecutiveDTX-r16

1

Table 12.1.6.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE is configured by upper layer to release SL-DRB to NR-SS-UE1.

Note: This step is triggered by MMI or AT command.

–

–

–

–

2

UE sends an RRCReconfigurationSidelink message to NR-SS-UE1 to indicate SL-DRB release

–>

PC5 RRC: RRCReconfigurationSidelink

–

–

3

NR-SS-UE1 does not respond and waits for the expiration of t_400 (1 second).

–

–

–

–

3A

1 second after step 3, the NR-SS-UE1 sends a DIRECT LINK RELEASE REQUEST message.

<–

PC5-S: DIRECT LINK RELEASE REQUEST

–

–

4

Check: Does the UE send a DIRECT LINK RELEASE ACCEPT message within the next 5 seconds.

–>

PC5-S: DIRECT LINK RELEASE ACCEPT

1

F

5

The UE is brought to state 4-A as defined in TS 38.508-1 [4], subclause 4.4A using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On), Test Mode = On using procedure in subclause 4.9.23.

–

–

–

–

6

The SS triggers UE to close UE test loop mode E (Transmission Mode).

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

–

–

–

–

7

The UE transmits one AMD PDU#1 to NR-SS-UE1 on SL-DRB

–>

AMD PDU#1 (SN=0)

–

–

–

EXCEPTION: Steps 9-10 are repeated sl-maxRetxThreshold times

–

–

–

–

–

EXCEPTION: In parallel to steps 9-10 any additional AMD PDU’s received are ignored by the SS

–

–

–

–

8

The NR-SS-UE1 transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.

<–

STATUS PDU

–

–

9

The UE transmits one AMD PDU#1 to NR-SS-UE1

–>

AMD PDU#1 (SN=0)

–

–

10

The NR-SS-UE1 transmits an RLC STATUS PDU. ACK_SN =1 and NACK_SN =0.

<–

STATUS PDU

–

–

11

1 second after step 10, the NR-SS-UE1 sends a DIRECT LINK RELEASE REQUEST message.

<–

PC5-S: DIRECT LINK RELEASE REQUEST

–

–

11A

Check: Does the UE send a DIRECT LINK RELEASE ACCEPT message within the next 5 seconds?

–>

PC5-S: DIRECT LINK RELEASE ACCEPT

2

F

12

The UE is brought to state 4-A as defined in TS 38.508-1 [4], subclause 4.4A using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On), Test Mode = On using procedure in subclause 4.9.23.

–

–

–

–

13

The SS triggers UE to close UE test loop mode E (Transmission Mode).

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

–

–

–

–

14

The NR-SS-UE1 MAC is configured to not send HARQ feedback

–

–

–

–

–

EXCEPTION: Step 14 is repeated sl-MaxNumConsecutiveDTX-r16 times

–

–

–

–

–

EXCEPTION: In parallel to step 14 any additional MAC PDU’s received are ignored by the SS.

–

–

–

–

15

The UE transmits one MAC PDU to NR-SS-UE1

–>

MAC PDU

–

–

15A

1 second after step 15, the NR-SS-UE1 sends a DIRECT LINK RELEASE REQUEST message.

<–

PC5-S: DIRECT LINK RELEASE REQUEST

16

Check: Does the UE send a DIRECT LINK RELEASE ACCEPT message within the next 5 seconds?

–>

PC5-S: DIRECT LINK RELEASE ACCEPT

3

F

12.1.6.3.3.3 Specific message contents

Table 12.1.6.3.3.3-1: RRCReconfigurationSidelink (step 2, Table 12.1.6.3.3.2-2)

Derivation path: TS 38.508-1 [4], Table 4.6.1A-3 with condition TX

Information Element

Value/Remark

Comment

Condition

RRCReconfigurationSidelink ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfigurationSidelink-r16 SEQUENCE {

slrb-ConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-PC5-ConfigIndex-r16 {

1 entry

SLRB-PC5-ConfigIndex-r16 [1]

1

entry 1

}

}

}

}

Table 12.1.6.3.3.3-2: DIRECT LINK RELEASE REQUEST (Steps 3A, 11 and 15A, Table 12.1.6.3.3.2-2)

Derivation Path: Table 4.7.4-11 with condition Rx

12.1.7 PC5-only operation / Sidelink UE capability transfer via PC5 RRC

12.1.7.1 PC5-only operation / Sidelink UE capability transfer via PC5 RRC / One-way and two-way transfer

12.1.7.1.1 Test Purpose (TP)

(1)

with { UE has established PC5 RRC connection with peer UE on unicast sidelink }

ensure that {

when { UE receives a UECapabilityEnquirySidelink message from peer UE }

then { UE sends a UECapabilityInformationSidelink message to peer UE }

}

(2)

with { UE has established PC5 RRC connection with peer UE on unicast sidelink }

ensure that {

when { UE is configured by upper layer to initiate capability transfer procedure }

then { UE sends a UECapabilityEnquirySidelink message to peer UE }

}

(3)

with { UE has established PC5 RRC connection with peer UE on unicast sidelink }

ensure that {

when { UE is configured by upper layer to initiate capability transfer procedure and to provide UE radio access capabilities }

then { UE sends a UECapabilityEnquirySidelink message with ue-CapabilityInformationSidelink to peer UE }

}

12.1.7.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.2.1, 5.8.9.2.2, 5.8.9.2.3 and 5.8.9.2.4. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, subclause 5.8.9.2.1]

This clause describes how the UE compiles and transfers its sidelink UE capability information for unicast to the initiating UE.

Figure 5.8.9.2.1-1: Sidelink UE capability transfer

[TS 38.331, subclause 5.8.9.2.2]

The UE may initiate the sidelink UE capability transfer procedure upon indication from upper layer when it needs (additional) UE radio access capability information.

[TS 38.331, subclause 5.8.9.2.3]

The initiating UE shall set the contents of UECapabilityEnquirySidelink message as follows:

1> include in UE radio access capabilities for sidelink within ue-CapabilityInformationSidelink, if needed;

NOTE 1: It is up to initiating UE to decide whether ue-CapabilityInformationSidelink should be included.

1> set frequencyBandListFilterSidelink to include frequency bands for which the peer UE is requested to provide supported bands and band combinations;

NOTE 2: The initiating UE is not allowed to send the UECapabilityEnquirySidelink message without including the field frequencyBandListFilterSidelink.

1> submit the UECapabilityEnquirySidelink message to lower layers for transmission.

[TS 38.331, subclause 5.8.9.2.4]

The peer UE shall set the contents of UECapabilityInformationSidelink message as follows:

1> include UE radio access capabilities for sidelink within ue-CapabilityInformationSidelink;

1> compile a list of "candidate band combinations" only consisting of bands included in frequencyBandListFilterSidelink, and prioritized in the order of frequencyBandListFilterSidelink (i.e. first include band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on).

1> include into supportedBandCombinationListSidelinkNR as many band combinations as possible from the list of "candidate band combinations", starting from the first entry;

1> include the received frequencyBandListFilterSidelink in the field appliedFreqBandListFilter of the requested UE capability;

1> submit the UECapabilityInformationSidelink message to lower layers for transmission.

NOTE: If the UE cannot include all band combinations due to message size or list size constraints, it is up to UE implementation which band combinations it prioritizes.

12.1.7.1.3 Test description

12.1.7.1.3.1 Pre-test conditions

System Simulator:

– SS-UE

– Operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.

– GNSS simulator

UE:

  • UE is authorised to perform NR sidelink communication.

Preamble:

– The UE is in state 4-A as defined in TS 38.508-1 [4], subclause 4.4A using generic procedure parameter Sidelink (On), Cast Type (Unicast), GNSS Sync (On).

12.1.7.1.3.2 Test procedure sequence

[Editor’s Note: For the below test procedure sequence it is assumed that the initiating UE side (= UE under test) as well as the peer UE (= SS-UE) are both out-of-coverage.]

Table 12.1.7.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE receives a UECapabilityEnquirySidelink message from SS-UE on SL-SRB3.

<–

PC5 RRC: UECapabilityEnquirySidelink

–

–

2

Check: Does the UE send a UECapabilityInformationSidelink message?

PC5 RRC: UECapabilityInformationSidelink

1

P

3

The UE is configured by upper layers to initiate capability transfer procedure and to include only the single frequency band and band combination which is currently used in this TC for communication over PC5 interface.

Note: This step is triggered by MMI or AT command.

–

–

–

–

4

Check: Does the UE send on SL-SRB3 a UECapabilityEnquirySidelink message?

–>

PC5 RRC: UECapabilityEnquirySidelink

2

P

5

The SS-UE sends a UECapbilityInformationSidelink message.

<–

PC5 RRC: UECapabilityInformationSidelink

–

–

6

The UE is configured by upper layers to initiate capability transfer procedure, to include only the single frequency band and band combination which is currently used in this TC for communication over PC5 interface and to provide UE radio access capabilities.

Note: This step is triggered by MMI or AT command.

–

7

Check: Does the UE send on SL-SRB3 a UECapabilityInformationSidelink message with ue-CapabilityInformationSidelink-r16 IE?

–>

PC5 RRC: UECapabilityEnquirySidelink

3

P

8

The SS-UE sends a UECapabilityInformationSidelink message.

<–

PC5 RRC: UECapabilityInformationSidelink

–

–

12.1.7.1.3.3 Specific message contents

Table 12.1.7.1.3.3-1: UECapabilityEnquirySidelink (step 1, Table 12.1.7.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-6

Information Element

Value/remark

Comment

Condition

UECapabilityEnquirySidelink ::= SEQUENCE {

criticalExtensions CHOICE {

ueCapabilityEnquirySidelink-r16 SEQUENCE {

frequencyBandListFilterSidelink-r16

FreqBandList with condition NR_SL_PC5

Includes only the single frequency band and band combination which is currently used in this TC for communication over the PC5 interface

NR_SL_PC5

}

}

}

Table 12.1.7.2.3.3-2: UECapabilityInformationSidelink (step 2, Table 12.1.7.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-7

Information Element

Value/remark

Comment

Condition

UECapabilityEnquirySidelink ::= SEQUENCE {

criticalExtensions CHOICE {

ueCapabilityInformationSidelink-r16 SEQUENCE {

pdcp-ParametersSidelink-r16 SEQUENCE {

outOfOrderDeliverySidelink-r16

Checked

pc_outOfOrderDeliverySidelink_r16

}

rlc-ParametersSidelink-r16 SEQUENCE {

am-WithLongSN-Sidelink-r16

Checked

pc_amWithLongSN_Sidelink_r16

um-WithLongSN-Sidelink-r16

Checked

pc_umWithLongSN_Sidelink_r16

}

supportedBandCombinationListSidelinkNR-r16

Checked

Includes all band combinations which the UE (= UE Under Test) supports for NR Sidelink acc. to the declared UE capabilities

supportedBandListSidelink-r16

Checked

Includes all frequency bands which the UE (= UE Under Test) supports for NR Sidelink acc. to the declared UE capabilities

appliedFreqBandListFilter-r16

Checked

Includes only the single frequency band and band combination which the SS-UE requested to include in the IE frequencyBandListFilterSidelink-r16 of UECapabilityEnquirySidelink message acc. to Table 12.1.7.2.3.3-1.

}

}

}

Table 12.1.7.1.3.3-3: UECapabilityEnquirySidelink (step 4, Table 12.1.7.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-6

Information Element

Value/remark

Comment

Condition

UECapabilityEnquirySidelink ::= SEQUENCE {

criticalExtensions CHOICE {

ueCapabilityEnquirySidelink-r16 SEQUENCE {

frequencyBandListFilterSidelink-r16

FreqBandList with condition NR_SL_PC5

Includes only the single frequency band and band combination which is currently used in this TC for communication over the PC5 interface

NR_SL_PC5

}

}

}

Table 12.1.7.1.3.3-4: UECapabilityInformationSidelink (steps 5 and 8, Table 12.1.7.1.3.2-1)

Derivation Path: TS 38.331 [6], clause 6.6.2

Information Element

Value/remark

Comment

Condition

UECapabilityInformationSidelink ::= SEQUENCE {

rrc-TransactionIdentifier-r16

RRC-TransactionIdentifier

criticalExtensions CHOICE {

ueCapabilityInformationSidelink-r16 SEQUENCE {

accessStratumReleaseSidelink-r16

rel16

supportedBandCombinationListSidelinkNR-r16

Includes only the single band combination which is currently used in this TC for communication over the PC5 interface.

supportedBandListSidelink-r16

Includes only the single frequency band which is currently used in this TC for communication over the PC5 interface

appliedFreqBandListFilter-r16

Includes only the single frequency band and band combination which the UE requested to include in the IE frequencyBandListFilterSidelink-r16 of UECapabilityEnquirySidelink message acc. to Table 12.1.7.1.3.3-1.

}

}

}

Table 12.1.7.1.3.3-5: UECapabilityEnquirySidelink (step 7, Table 12.1.7.1.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.6.1A-6 with condition TWO_WAY_ENQUIRY

Information Element

Value/remark

Comment

Condition

UECapabilityEnquirySidelink ::= SEQUENCE {

criticalExtensions CHOICE {

ueCapabilityEnquirySidelink-r16 SEQUENCE {

frequencyBandListFilterSidelink-r16

FreqBandList with condition NR_SL_PC5

Includes only the single frequency band and band combination which is currently used in this TC for communication over the PC5 interface

NR_SL_PC5

ue-CapabilityInformationSidelink-r16

Checked

}

}

}