24.1.4 V2X Sidelink Communication / Pre-configured authorisation / Utilisation of the pre-configured resources / Reception

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

24.1.4.1 Test Purpose (TP)

(1)

with { UE being authorized for performing V2X sidelink Communication being provisioned with Radio parameters for when the UE is "not served by E-UTRAN" associated with a geographical area, and, UE out of coverage on the anchor carrier used for V2X configuration }

ensure that {

when { UE wants to receive V2X sidelink Communication, and, UE determines itself as being located in that geographical area }

then { UE is able to receive V2X sidelink Communication using the preconfigured for "not served by E-UTRAN" resources }

}

(2)

with { UE being authorized for performing V2X sidelink Communication being provisioned with Radio parameters for when the UE is "not served by E-UTRAN" associated with a geographical area, and, UE out of coverage on the anchor carrier used for V2X configuration }

ensure that {

when { UE wants to receive V2X sidelink Communication, and, UE determines itself as being not located in that geographical area }

then { UE does not initiate monitoring of V2X sidelink Communication }

}

24.1.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 23.285, clauses 4.4.1.1.1, 4.4.1.1.2, 4.4.2, 4.5.1, 5.3.

[TS 23.285, clause 4.4.1.1.1]

The basic principles of service authorization for V2X communications over PC5 reference point:

– The UE gets authorization to use V2X communications over PC5 reference point on a per PLMN basis in the serving PLMN by the V2X Control Function in the HPLMN.

– The V2X Control Function in the HPLMN requests authorization information from the V2X Control Function of the serving PLMN.

– The V2X Control Function in the HPLMN merges authorization information from home and serving PLMNs and informs the UE of the final authorization information.

– The V2X Control Function in the VPLMN or HPLMN may revoke the authorization at any time. The V2X Control Function in the HPLMN shall be notified when authorization is revoked by the VPLMN.

[TS 23.285, clause 4.4.1.1.2]

The following information is provisioned to the UE for V2X communications over PC5 reference point:

1) Authorization policy:

– When the UE is "served by E-UTRAN":

– PLMNs in which the UE is authorized to perform V2X communications over PC5 reference point.

– When the UE is "not served by E-UTRAN":

– Indicates whether the UE is authorized to perform V2X communications over PC5 reference point when "not served by E-UTRAN".

2) Radio parameters for when the UE is "not served by E-UTRAN":

– Includes the radio parameters with Geographical Area(s) that need to be configured in the UE in order to be able perform V2X communications over PC5 reference point when "not served by E-UTRAN". These radio parameters (e.g. frequency bands) are defined in TS 36.331 [9]. The UE uses the radio parameters only if the UE can locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.

3) Policy/parameters for V2X communication over PC5 reference point:

– The mapping of Destination Layer-2 ID(s) and the V2X services, e.g. PSID or ITS-AIDs of the V2X application.

NOTE 1: PLMN operators coordinate to make sure Destination Layer-2 ID(s) for different V2X services are configured in a consistent manner.

NOTE 2: To pre-configure a UE with the provisioning parameters, at least the "not served by E-UTRAN" parameters of 1) and 2), and the parameters of 3) need to be included.

– The mapping of ProSe Per-Packet Priority and packet delay budget for V2X communication (autonomous resources selection mode).

[TS 23.285, clause 4.4.2]

PC5 reference point as defined in TS 23.303 [5] is used for the transmission and reception of V2X messages. The V2X communication over PC5 reference point supports roaming and inter-PLMN operations. V2X communication over PC5 reference point is supported when the UE is "served by E-UTRAN" and when the UE is "not served by E‑UTRAN".

A UE is authorized to transmit and receive V2X messages by the V2X Control Function in its home PLMN as described in clause 5.2.

The V2X communication over PC5 reference point is a type of ProSe Direct Communication with the following characteristics:

– The V2X communication over PC5 reference point is connectionless, and there is no signalling over PC5 control plane for connection establishment.

– V2X messages are exchanged between UEs over PC5 user plane.

– Both IP based and non-IP based V2X messages are supported.

– For IP based V2X messages, only IPv6 is used. IPv4 is not supported in this release.

The identifiers used in the V2X communication over PC5 reference point are described in clause 4.5.1.

[TS 23.285, clause 4.5.1]

Each UE has a Layer-2 ID for the V2X communication over PC5 reference point, which is included in the source Layer-2 ID field of every frame that it sends on the layer-2 link. The UE self-assigns the Layer-2 ID for the V2X communication over PC5 reference point.

When IP based V2X messages are supported, the UE auto-configures a link local IPv6 address to be used as the source IP address, as defined in clause 4.5.3 of TS 23.303 [5].

In order to ensure that a source UE (e.g. vehicle) cannot be tracked or identified by any other UEs (e.g. vehicles) beyond a certain short time-period required by the application, the source Layer-2 ID must be changed over time and randomized. For IP based V2X communication over PC5 reference point, the source IP address must be also changed over time and randomized. The change of the identifiers of a source UE must be synchronized across layers used for PC5, e.g. when application layer identifier changes, the source Layer-2 ID and the source IP address need to be changed.

The UE is configured with the destination Layer-2 ID(s) to be used for V2X services. The Layer-2 ID for a V2X message is selected based on the configuration as described in clause 4.4.1.1.

[TS 23.285, clause 5.3]

To perform V2X communication over PC5 reference point, the UE is configured with the related information as described in clause 4.4.1.1.

The procedure for one-to-many ProSe Direct Communication transmission described in clause 5.4.2 of TS 23.303 [5] is applied to V2X communication over PC5 reference point with following differences:

– The source Layer-2 ID is set to the Layer-2 ID described in clause 4.5.1.

– A UE shall be configured with a set of Layer-2 ID corresponding to different type of services.

The procedure for one-to-many ProSe Direct Communication reception described in clause 5.4.3 of TS 23.303 [5] is applied to V2X communication over PC5 reference point.

24.1.4.3 Test description

24.1.4.3.1 Pre-test conditions

System Simulator:

SS-NW

– 1 GNSS simulator

– No E-UTRA cell configured

SS-UE

– SS-UE1. As defined in TS 36.508 [18], configured for and operating as V2X Sidelink Communication transmitting device on the resources which the UE is expected to use for transmission, as defined in TS 36.508 [18] clause 6.2.3.5.

UE:

– V2X sidelink related configuration

– The UE is authorised to perform V2X Sidelink Communication

– The UE is equipped with the information below (Table 24.1.4.3.1-1) in the UE or in a USIM containing default values (as per TS 36.508 [18]).

Table 24.1.4.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

Service n°119 (V2X) supported

EFVST

As per TS 36.508 [18] clause 4.9.3.4

EFV2X_CONFIG

SL-V2X-Preconfiguration field as defined in 36.508 [18], table 6.8.2.1-1

Geographical area field as defined in TS 36.508 [18] clause 4.9.3.1.

Preamble:

– The UE is in state V2X out of coverage (State 5-V2X), according to TS 36.508 [18].

24.1.4.3.2 Test procedure sequence

Table 24.1.4.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

2

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

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

2A

Trigger the UE to reset UTC time.

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

3

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 36.508 [18] Table 4.11.2-2. Geographical area #1 is also pre-configured in the UE.

3A

Wait for px_AquireGNSS_MaxTime for the UE to acquire location data and start receiving.

EXCEPTION: Step 4 is repeated 3 times.

4

SS-UE1 sends sidelink communication over the PC5 interface

NOTE: This step verifies TP1 – it is expected that the UE shall receive these packets – if they were received is checked in step 6.

<–

STCH PDCP SDU packet

5

Trigger UE to request the counter of successful reception of STCH packets

NOTE: The ProSe packed counter may be requested by MMI or AT command (+CUSPCREQ).

6

Check: Does the UE send a response with the counter of STCH packets = 3?

1

P

7

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 36.508 [18] Table 4.11.2-2. The area outside Geographical area #1 is not pre-configured in the UE.

8

Wait for 71 sec (as detailed in TS 36.508 [18] 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.

EXCEPTION: Step 9 is repeated 3 times.

9

SS-UE1 sends sidelink communication over the PC5 interface

NOTE: This step verifies TP2 – it is expected that the UE shall not receive these packets – if they were received is checked in step 11.

<–

STCH PDCP SDU packet

10

Trigger UE to request the counter of successful reception of STCH packets

NOTE: The ProSe packed counter may be requested by MMI or AT command (+CUSPCREQ).

.

.

11

Check: Does the UE send a response with the counter of STCH packets = 3?

.

.

2

P

11A

Trigger UE to open UE test loop mode E

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

.

.

.

.

12

Trigger UE to deactivate UE test loop mode.

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

.

24.1.4.3.3 Specific message contents