13.1 V2X policy provisioning

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

13.1.1 V2X policy provisioning / Precedence / Validity timer expires / geographical area changes

13.1.1.1 Test Purpose (TP)

(1)

with { UE having V2XP over PC5 configured in the USIM and UE being out of NR network coverage }

ensure that {

when { UE is required to start NR V2X communication }

then { UE conducts V2X communication according to parameters of V2XP over PC5 from USIM }

}

(2)

with { UE having V2XP over PC5 configured in the USIM and UE being in NR network coverage }

ensure that {

when { UE receives V2XP over PC5 from SS and then NR cell is off }

then { UE conducts V2X communication according to parameters of V2XP over PC5 from SS }

}

(3)

with { UE having received V2XP over PC5 from SS }

ensure that {

when { Validity timer expires and NR cell is on }

then { UE initiates a UE-requested V2X policy provisioning procedure }

}

(4)

with { UE having received V2XP over PC5 from SS after UE initiates a UE-requested V2X policy provisioning procedure }

ensure that {

when { UE is located in the geographical area and UE is requested by a service to transmit a V2X packet }

then { UE initiates a V2X communication on the frequency associated with the service }

}

(5)

with { UE having initiated a V2X communication on the frequency associated with the service }

ensure that {

when { UE moves out of the geographical area }

then { UE cannot continue the V2X communication on the frequency associated with the service }

}

13.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.587, clauses 5.2.2 and 5.2.3. Unless otherwise stated these are Rel-16 requirements.

[TS 24.501, clause 5.2.2]

…

The UE shall use the V2X configuration parameters in the following order of decreasing precedence:

a) the V2X configuration parameters provided as a V2XP using the UE policy delivery service as specified in annex D of 3GPP TS 24.501 [6];

b) the V2X configuration parameters provided by a V2X application server via V1 reference point;

c) the V2X configuration parameters configured in the USIM; and

d) the V2X configuration parameters pre-configured in the ME.

[TS 24.501, clause 5.2.3]

The configuration parameters for V2X communication over PC5 consist of:

a) a validity timer for the validity of the configuration parameters for V2X communication over PC5;

b) a list of PLMNs and RATs in which the UE is authorized to use V2X communication over PC5 when the UE is served by E-UTRA or served by NR. Each entry of the list contains a PLMN ID and RATs in which the UE is authorized to use V2X communication over PC5;

c) an indication of whether the UE is authorized to use V2X communication over PC5 when the UE is not served by E-UTRA and not served by NR;

d) list of RATs in which the UE is authorized to use V2X communication over PC5 and the radio parameters of the RAT for V2X communication over PC5 applicable per geographical area with an indication of whether these radio parameters of the RAT are "operator managed" or "non-operator managed" when the UE is not served by E-UTRA and not served by NR;

e) void

f) optionally, a list of V2X service identifier to PC5 RAT(s) and Tx profiles mapping rules. Each mapping rule contains one or more V2X service identifiers, PC5 RAT(s) and, if the PC5 RAT(s) include E-UTRA-PC5, Tx profiles corresponding to the E-UTRA-PC5;

g) configuration parameters for privacy support, consisting of:

1) a list of V2X services requiring privacy. Each entry of the list contains one or more V2X service identifiers and one or more geographical areas where the privacy is required; and

2) a privacy timer value as specified in 3GPP TS 24.588 [7] clause 5.3;

h) configuration parameters for a V2X communication over PC5 in E-UTRA-PC5, consisting of:

1) a list of V2X service identifier to destination layer-2 ID mapping rules. Each mapping rule contains one or more V2X service identifiers and the destination layer-2 ID;

2) optionally, a default destination layer-2 ID;

3) a list of PPPP to PDB mapping rules. Each mapping rule contains a ProSe Per-Packet Priority (PPPP) and a Packet Delay Budget (PDB);

4) optionally, list of V2X service identifier to V2X E-UTRA frequency mapping rules. Each mapping rule contains one or more V2X service identifiers and the V2X E-UTRA frequencies with associated geographical areas; and

5) optionally, a list of the V2X services authorized for ProSe Per-Packet Reliability (PPPR). Each entry of the list contains one or more V2X service identifiers and a ProSe Per-Packet Reliability (PPPR) value; and

i) configuration parameters for a V2X communication over PC5 in NR-PC5, consisting of:

1) optionally, a list of V2X service identifier to V2X NR frequency mapping rules. Each mapping rule contains one or more V2X service identifiers and the V2X NR frequencies with associated geographical areas;

2) a list of V2X service identifier to destination layer-2 ID for broadcast mapping rules. Each mapping rule contains one or more V2X service identifiers and the destination layer-2 ID for broadcast;

3) optionally, a default destination layer-2 ID for broadcast;

4) a list of V2X service identifier to destination layer-2 ID for groupcast mapping rules. Each mapping rule contains one or more V2X service identifiers and the destination layer-2 ID for groupcast;

5) a list of V2X service identifier to default destination layer-2 ID for unicast initial signalling mapping rules. Each mapping rule contains one or more V2X service identifiers and the default destination layer-2 ID for initial signalling to establish unicast connection;

6) a list of V2X service identifier to PC5 QoS parameters mapping rules. The PC5 QoS parameters are specified in clause 5.4.2 of 3GPP TS 23.287 [3];

7) an AS configuration, including a list of SLRB mapping rules applicable when the UE is not served by E-UTRA and is not served by NR. Each SLRB mapping rule contains a PC5 QoS profile and an SLRB. The PC5 QoS profile contains the following parameters:

i) the PC5 QoS profile contains a PQI;

ii) if the PQI of the PC5 QoS profile identifies a GBR QoS, the PC5 QoS profile contains a PC5 flow bit rates consisting of a guaranteed flow bit rate (GFBR) and a maximum flow bit rate (MFBR);

iii) if the PQI of the PC5 QoS profile identifies a non-GBR QoS, the PC5 QoS profile contains the PC5 link aggregated bit rate consisting of a per link aggregate maximum bit rate (PC5 LINK-AMBR);

NOTE: PC5 link aggregated bit rate is only used for unicast mode communications over PC5.

iv) the PC5 QoS profile contains a range, which is only used for groupcast mode communications over PC5; and

v) the PC5 QoS profile can contain the priority level, the averaging window, and the maximum data burst volume. If one or more of the priority level, the averaging window or the maximum data burst volume are not contained in the PC5 QoS profile, their default values apply;

8) a list of NR-PC5 unicast security policies. Each entry in the list contains an NR-PC5 unicast security policy composed of:

i) one or more V2X service identifiers;

ii) the signalling integrity protection policy for the V2X service identifier(s);

iii) the signalling ciphering policy for the V2X service identifier(s);

iv) the user plane integrity protection policy for the V2X service identifier(s);

v) the user plane ciphering policy for the V2X service identifier(s); and

vi) one or more geographical areas where the NR-PC5 unicast security policy applies; and

9) a list of V2X service identifier to default mode of communication mapping rules. Each mapping rule contains one or more V2X service identifiers and the default mode of communication (one of unicast, groupcast or broadcast).

13.1.1.3 Test description

13.1.1.3.1 Pre-test conditions

SS-NW:

– NR Cell 1.

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

– 1 GNSS 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 receiving device on the resources which the UE is expected to use for transmission.

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

UE:

– The UE is equipped with a USIM configuration as defined in clause 4.8.3.3.3 of TS 38.508-1 [4].

– UE is synchronised on GNSS.

Preamble:

– UE is brought to state 4-A, Out of Coverage (NR sidelink), in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.7.2-1 using generic procedure parameter Sidelink (On), Cast Type (unicast), UE initiating unicast mode NR sidelink comunication, Test Loop Function (On) with UE test loop mode E.

13.1.1.3.2 Test procedure sequence

Table 13.1.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures:

SS-NW

– NR Cell 1 as "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3.

– GNSS simulator is configured for Scenario #1.

–

–

–

–

2

Check: Does the UE continuously send STCH SDAP PDUs on SL DRB#n in every PSSCH duration with the resources pre-configured in SL-PreconfigurationNR IE with NRf1 test frequency for NR Sidelink in USIM? (Note 1)

NOTE: The UE has activated and closed test loop mode E in the preamble.

–>

V2X Data packet

1

P

3

Trigger the UE to open UE test loop mode E

NOTE: The UE test loop mode E may be opened by MMI or AT command (+CCUTLE).

–

–

–

–

4

Trigger the UE to deactivate UE test loop mode.

NOTE: The deactivation of UE test loop mode may be performed by MMI or AT command (+CATM).

–

–

–

–

5

The SS configures:

SS-NW

– NR Cell 1 as "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3.

–

–

–

–

6

The UE performs Step 1-22a1 of Table 4.5.2.2-2 in TS 38.508-1 [4], with ‘connected without release’.

–

–

–

–

7

SS-NW transmits a DL NAS TRANSPORT message containing a MANAGE UE POLICY COMMAND message to transfer the V2X policy to the UE.

<–

5GMM: DL NAS TRANSPORT

PCF: MANAGE UE POLICY COMMAND

–

–

8

The UE transmits a UL NAS TRANSPORT message containing a MANAGE UE POLICY COMPLETE message

–>

5GMM: UL NAS TRANSPORT

UE V2X: MANAGE UE POLICY COMPLETE

–

–

9

The SS configures:

SS-NW

– NR Cell 1 as "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3.

–

–

–

–

10

Trigger the UE to activate UE test loop mode

NOTE: The activation of UE test loop mode may be performed by MMI or AT command (+CATM).

–

–

–

–

11

Trigger the UE to close UE test loop mode E (transmission mode).

NOTE: The UE test loop mode E may be closed by MMI or AT command (+CCUTLE).

–

–

–

–

12

Check: Does the UE continuously send STCH SDAP PDUs on SL DRB#n in every PSSCH duration with the resources pre-configured in SL-PreconfigurationNR IE with NRf2 test frequency for NR Sidelink of V2X policy in step 7? (Note 1)

–>

V2X Data packet

2

P

13

The SS configures:

SS-NW

– NR Cell 1 as "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3.

–

–

–

–

14

Check: Does the UE transmit a UL NAS TRANSPORT message containing a UE POLICY PROVISIONING REQUEST message within 30 seconds after step 7.

–>

5GMM: UL NAS TRANSPORT

UE V2X: UE POLICY PROVISIONING REQUEST

3

P

15

SS-NW transmits a DL NAS TRANSPORT message containing a MANAGE UE POLICY COMMAND message

<–

5GMM: DL NAS TRANSPORT

PCF: MANAGE UE POLICY COMMAND

–

–

16

The SS configures:

SS-NW

– NR Cell 1 as "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3.

–

–

–

–

17

Trigger the UE to reset UTC time.

NOTE: The UTC time reset may be performed by MMI or AT command (+CUTCR).

–

–

–

–

18

SS configures:

GNSS simulator is configured for Scenario #2: move from inside Geographical area #1 to outside Geographical area #1, and starts step 1 to simulate a location in the centre of Geographical area #1 as defined in TS 38.508-1 [4] Table 4.11.2-2. Geographical area #1 is also pre-configured in the UE.

–

–

–

–

19

Check: Does the UE continuously send STCH SDAP PDUs on SL DRB#n in every PSSCH duration with the resources in SL-PreconfigurationNR IE with NRf3 test frequency for NR Sidelink of V2X policy in step 15? (Note 1)

–>

V2X Data packet

4

P

20

SS configures:

GNSS simulator is triggered to start step 2 of Scenario #2 to simulate the UE moving to a location outside Geographical area #1 as defined in TS 38.508-1 [4] Table 4.11.2-2. The area outside Geographical area #1 is not pre-configured in the UE.

–

–

–

–

21

Wait for 71 sec (as detailed in TS 38.508-1 [4] Table 4.11.2-2) to allow the simulated location for the UE to leave Geographical area #1 and for the UE to acquire new location data.

–

–

–

–

22

Check: Does the UE continuously send STCH SDAP PDUs on SL DRB#n in every PSSCH duration with the resources in SL-PreconfigurationNR IE with NRf3 test frequency for NR Sidelink of V2X policy in step 15, in the next 10 seconds?

–>

V2X Data packet

5

F

23

Trigger the UE to open UE test loop mode E

NOTE: The UE test loop mode E may be opened by MMI or AT command (+CCUTLE).

–

–

–

–

24

Trigger the UE to deactivate UE test loop mode.

NOTE: The deactivation of UE test loop mode may be performed by MMI or AT command (+CATM).

–

–

–

–

Note 1: Although the UE is expected to transmit continuously, only one STCH SDAP SDU packet is shown explicitly in this step sequence.

13.1.1.3.3 Specific message contents

Table 13.1.1.3.3-0: DL NAS TRANSPORT (step 7, 15, Table 13.1.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.7.1-11

Information Element

Value/remark

Comment

Condition

Payload container type

‘0101’B

UE policy container type

Payload container

Set according to Table 13.1.1.3.3-1

Table 13.1.1.3.3-1: MANAGE UE POLICY COMMAND (step 7, 15, Table 13.1.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.7.6-1

Information Element

Value/remark

Comment

Condition

UE policy section management list

UE policy section management list contents

1 entry

UE policy section management sublist (PLMN-1)

UE policy section management sublist contents

Instruction 1

UE policy section contents

UE policy part 1

UE policy part type

‘0011’B

V2XP

UE policy part contents

See Table 13.1.1.3.3-2

Table 13.1.1.3.3-2: UE policy part contents (Table 13.1.1.3.3-1)

Derivation Path: TS 38.508-1 [4] Table 4.7.5.4-1

Information Element

Value/remark

Comment

Condition

UE policy part contents={V2XP contents}

See Table 13.1.1.3.3-3

Table 13.1.1.3.3-3: V2XP contents (Table 13.1.1.3.3-2)

Derivation Path: TS 38.508-1 [4] Table 4.7.5.4-2

Information Element

Value/remark

Comment

Condition

V2XP info #1

See Table 13.1.1.3.3-4

V2XP info #2

Not Present

Table 13.1.1.3.3-4: V2XP info (Table 13.1.1.3.3-3)

Derivation Path: TS 38.508-1 [4] Table 4.7.5.4-3

Information Element

Value/remark

Comment

Condition

V2XP info contents

See Table 13.1.1.3.3-5

Table 13.1.1.3.3-5: V2XP info = {UE policies for V2X communication over PC5} (Table 13.1.1.3.3-4)

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

Information Element

Value/remark

Comment

Condition

Validity timer

‘FF FF FF FF FF FF FF FF FF FF’H

5 bytes, Expiration UTC time of validity of the UE policies, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds)

Step 15

Current GNSS UTC time + 30 seconds

Step 7

V2X service identifier to PC5 RAT and Tx profiles mapping rules

See Table 4.7.5.5-12 in TS 38.508-1 [4] with condition NR-PC5

Not served by E-UTRA and not served by NR

See Table 13.1.1.3.3-6

Table 13.1.1.3.3-6: Not served by E-UTRA and not served by NR (Table 13.1.1.3.3-5)

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

Information Element

Value/remark

Comment

Condition

EPINENN

‘0’B

UE is not authorized to use V2X communication over E-UTRA-PC5 when not served by E-UTRA and not served by NR

E-UTRA radio parameters per geographical area list

Not present

NR radio parameters per geographical area list

See Table 13.1.1.3.3-7

Table 13.1.1.3.3-7: Radio parameters per geographical area list (Table 13.1.1.3.3-6)

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

Information Element

Value/remark

Comment

Condition

Radio parameters per geographical area info 1

See Table 13.1.1.3.3-8

Table 13.1.1.3.3-8: Radio parameters per geographical area info (Table 13.1.1.3.3-7)

Derivation TS 38.508-1 [4] Table 4.7.5.5-8

Information Element

Value/remark

Comment

Condition

Radio parameters

See Table 13.1.1.3.3-9

Table 13.1.1.3.3-9: Radio parameters (Table 13.1.1.3.3-8)

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

Information Element

Value/remark

Comment

Condition

Radio parameters contents

See Table 13.1.1.3.3-10

Table 13.1.1.3.3-10: SL-PreconfigurationNR (Table 13.1.1.3.3-9)

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-PreconfigFreqInfoList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF {

1 entry

SL-FreqConfigCommon-r16[0]

See Table 13.1.1.3.3-11

}

}

}

Table 13.1.1.3.3-11: SL-FreqConfigCommon (Table 13.1.1.3.3-10)

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

Information Element

Value/remark

Comment

Condition

SL-FreqConfigCommon-r16 ::= SEQUENCE {

sl-SCS-SpecificCarrierList-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier {

1 entry

SCS-SpecificCarrier[1]

See Table 13.1.1.3.3-12

entry 1

}

sl-AbsoluteFrequencyPointA-r16

sl-AbsoluteFrequencyPointA as defined for the SL NRf2 frequency

See TS 38.508-1 [4] Table 6.2.3.7-1.

Step 7

sl-AbsoluteFrequencyPointA as defined for the SL NRf3 frequency

See TS 38.508-1 [4] Table 6.2.3.7-1.

Step 15

sl-AbsoluteFrequencySSB-r16

sl-AbsoluteFrequencySSB as defined for the SL NRf2 frequency

See TS 38.508-1 [4] Table 6.2.3.7-1.

Step 7

sl-AbsoluteFrequencySSB as defined for the SL NRf3 frequency

See TS 38.508-1 [4] Table 6.2.3.7-1.

Step 15

}

Table 13.1.1.3.3-12: SCS-SpecificCarrier (Table 13.1.1.3.3-11)

Derivation Path: TS 38.508-1 [4] Table 4.6.3-160

Information Element

Value/remark

Comment

Condition

SCS-SpecificCarrier ::= SEQUENCE {

offsetToCarrier

offsetToCarrier as defined for the SL NRf2 frequency

See TS 38.508-1 [4] Table 6.2.3.7-1.

Step 7

offsetToCarrier as defined for the SL NRf3 frequency

See TS 38.508-1 [4] Table 6.2.3.7-1.

Step 15

}

Table 13.1.1.3.3-13: UL NAS TRANSPORT (step 8, 14, Table 13.1.1.3.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.7.1-11

Information Element

Value/remark

Comment

Condition

Payload container type

‘0101’B

UE policy container type

Payload container

Set to MANAGE UE POLICY COMPLETE message

Step 8

Set to UE POLICY PROVISIONING REQUEST message

Step 14