24.1.3 V2X Sidelink Communication / Pre-configured authorisation / UE in RRC_IDLE on an E-UTRAN cell operating on the anchor carrier frequency provisioned for V2X configuration / Utilisation of the resources of (serving) cells/PLMNs / Reception

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

24.1.3.1 Test Purpose (TP)

(1)

with { UE being authorized for performing V2X sidelink Communication in PLMN1 and pre-configured with anchor carrier parameters for V2X configuration and being provisioned with Radio parameters for when the UE is "not served by E-UTRAN", and, UE in RRC_IDLE on Cell1/f1/PLMN1 which is operating on the anchor carrier frequency as the one pre-configured in the UE/USIM and is transmitting SystemInformationBlockType21 which does not include v2x-CommRxPool}

ensure that {

when { UE receives a request from upper layers to receive V2X sidelink communication }

then { UE initiates an RRC connection, and, successfully completes a Sidelink UE information procedure to indicate the V2X sidelink communication reception resources required }

}

(2)

with { UE being authorized for performing V2X sidelink Communication in PLMN1 and pre-configured with anchor carrier parameters for V2X configuration and being provisioned with Radio parameters for when the UE is "not served by E-UTRAN", and, UE in RRC_IDLE on Cell1/f1/PLMN1 which is operating on the anchor carrier frequency as the one pre-configured in the UE/USIM and is transmitting SystemInformationBlockType21 which does include v2x-CommRxPool in v2x-InterFreqInfoList }

ensure that {

when { UE receives a request from upper layers to receive V2X sidelink communication }

then { UE is able to receive V2x sidelink communication using the configured resources in Cell1/f1/PLMN1 via SystemInformationBlockType21 }

}

(3)

with { UE being authorized for performing V2X sidelink Communication in PLMN1 and pre-configured with anchor carrier parameters for V2X configuration and with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_IDLE on Cell1/f1/PLMN1 which is not transmitting SystemInformationBlockType21 }

ensure that {

when { Cell3/f2/PLMN1 which is broadcasting SystemInformationBlockType21 providing resources for V2X sidelink communication becomes the highest ranked cell, and, UE reselects to Cell3/f2/PLMN1 }

then { UE is able to receive V2X sidelink communication using the configured resources in Cell3/f2/PLMN1 }

}

24.1.3.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 36.331, clauses 5.2.2.4, 5.2.2.28, 5.10.1d, 5.10.12.

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

[TS 36.331, clause 5.2.2.4]

1> if the UE is capable of V2X sidelink communication and is configured by upper layers to receive or transmit V2X sidelink communication on a frequency:

2> if the cell used for V2X sidelink communication meets the S-criteria as defined in TS 36.304 [4]; and

2> if schedulingInfoList on the concerned frequency indicates that SystemInformationBlockType21 is present and the UE does not have stored a valid version of this system information block:

3> acquire SystemInformationBlockType21;

[TS 36.331, clause 5.2.2.28]

Upon receiving SystemInformationBlockType21, the UE shall:

1> if SystemInformationBlockType21 message includes sl-V2X-ConfigCommon:

2> if configured to receive V2X sidelink communication:

3> use the resource pool indicated by v2x-CommRxPool in sl-V2X-ConfigCommon for V2X sidelink communication monitoring, as specified in 5.10.12;

2> if configured to transmit V2X sidelink communication:

3> use the resource pool indicated by v2x-CommTxPoolNormalCommon or by v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.10.13;

3> perform CBR measurement on the transmission resource pool(s) indicated by v2x-CommTxPoolNormalCommon and v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.5.3;

[TS 36.331, clause 5.10.1d]

When it is specified that the UE shall perform V2X sidelink communication operation only if the conditions defined in this section are met, the UE shall perform V2X sidelink communication operation only if:

1> if the UE’s serving cell is suitable (RRC_IDLE or RRC_CONNECTED); and if either the selected cell on the frequency used for V2X sidelink communication operation belongs to the registered or equivalent PLMN as specified in TS 24.334 [69] or the UE is out of coverage on the frequency used for V2X sidelink communication operation as defined in TS 36.304 [4, 11.4]; or

1> if the UE’s serving cell (for RRC_IDLE or RRC_CONNECTED) fulfils the conditions to support V2X sidelink communication in limited service state as specified in TS 23.285 [78, 4.4.8]; and if either the serving cell is on the frequency used for V2X sidelink communication operation or the UE is out of coverage on the frequency used for V2X sidelink communication operation as defined in TS 36.304 [4, 11.4]; or

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

[TS 36.331, clause 5.10.12]

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

1> if the conditions for sidelink operation as defined in 5.10.1d are met:

2> if in coverage on the frequency used for V2X sidelink communication, as defined in TS 36.304 [4, 11.4]:

3> if the frequency used to receive V2X sidelink communication is included in v2x-InterFreqInfoList within RRCConnectionReconfiguration or in v2x-InterFreqInfoList within SystemInformationBlockType21of the serving cell/Pcell, and v2x-CommRxPool is included in SL-V2X-InterFreqUE-Config within v2x-UE-ConfigList:

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated in v2x-CommRxPool;

3> else:

4> if the cell chosen for V2X sidelink communication reception broadcasts SystemInformationBlockType21 including v2x-CommRxPool in sl-V2X-ConfigCommon or,

4> if the UE is configured with v2x-CommRxPool included in mobilityControlInfoV2X in RRCConnectionReconfiguration:

5> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated in v2x-CommRxPool;

2> else (i.e. out of coverage on the frequency used for V2X sidelink communication, as defined in TS 36.304 [4, 11.4]):

3> if the frequency used to receive V2X sidelink communication is included in v2x-InterFreqInfoList within RRCConnectionReconfiguration or in v2x-InterFreqInfoList within SystemInformationBlockType21 of the serving cell/PCell, and v2x-CommRxPool is included in SL-V2X-InterFreqUE-Config within v2x-UE-ConfigList for the concerned frequency:

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated in v2x-CommRxPool;

3> else:

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources that were preconfigured (i.e. v2x-CommRxPoolList in SL-V2X-Preconfiguration defined in 9.3);

24.1.3.3 Test description

24.1.3.3.1 Pre-test conditions

System Simulator:

SS-NW

– Cell 1 and Cell 3

Table 24.1.3.3.1-1: Cell parameters values

Cell

Frequency

PLMN

1

f1

HPLMN (PLMN1)

3

f2

PLMN1

Note 1: The Frequencies f1 and f2 shall be the anchor frequencies pre-configured in the UE/USIM.

– System information combination 29 as defined in TS 36.508 [18] clause 4.4.3.1 is used in all active cells.

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 reception, 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 below information in UE or in a USIM containing default values (as per TS 36.508 [18]) except for those listed in Table 24.1.3.3.1-1.

Table 24.1.3.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 Table 24.1.3.3.3-1

Preamble:

– The UE is in State Switched OFF (state 1) according to TS 36.508 [18].

24.1.3.3.2 Test procedure sequence

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

Table 24.1.3.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

T0

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

Table 24.1.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures:

SS-NW

– Cell 1 transmits SystemInformationBlockType21 not including v2x-CommRxPool (i.e. V2X sidelink communication supported by the network, no common resources provided yet).

2

The UE is switched on.

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1.

3-20c4

Steps 1 – 18 from the generic test procedure for UE registration, UE Test Mode E Activated (State 2A) defined in TS 36.508 [18] clause 4.5.2A take place.

21

Close UE Test Loop with bit E0 in UE test loop mode E LB setup IE set to zero (receive mode).

<–

CLOSE UE TEST LOOP

22

The UE responds with CLOSE UE TEST LOOP COMPLETE.

–>

CLOSE UE TEST LOOP COMPLETE

23

SS-NW releases the connection.

<–

RRCConnectionRelease

24

Check: Does the UE transmit an RRCConnectionRequest message?

–>

RRCConnectionRequest

1

P

25

SS-NW transmits an RRCConnectionSetup message.

<–

RRCConnectionSetup

26

Check: Does the UE transmit an RRCConnectionSetupComplete message?

–>

RRCConnectionSetupComplete

1

P

27

Check: Does the UE transmit a SidelinkUEInformation message requesting resources for monitoring of V2X sidelink communication?

–>

SidelinkUEInformation

1

P

28

SS-NW releases the connection.

<–

RRCConnectionRelease

29

SS-NW changes SystemInformationBlockType21 to include v2x-CommRxPool in v2x-InterFreqInfoList.

30

Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType21.

EXCEPTION: Step 31 is repeated 3 times.

31

SS-UE1 transmits V2X sidelink communication over the PC5 interface in accordance with the resources indicated in SystemInformationBlockType21

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

<–

STCH PDCP SDU packet

32

The SS configures:

SS-NW

Cell 1 and Cell 3 parameters according to the row "T1" in table 24.1.3.3.2-1 in order to simulate the need for cell reselection to Cell3.

Cell 3 broadcasts SystemInformationBlockType21 including v2x-CommRxPool in v2x-InterFreqInfoList.

33

Wait for 5 sec to allow the UE to adjust to cell changes and start transmission.

EXCEPTION: The following events unless otherwise stated are to be observed in Cell 3.

EXCEPTION: Step 34 is repeated 3 times.

34

SS-UE1 transmits V2X sidelink communication over the PC5 interface in accordance with the resources indicated in SystemInformationBlockType21

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

<–

STCH PDCP SDU packet

35

Generic procedure for Generic Radio Bearer Establishment (State 3) defined in TS 36.508 [18] clause 4.5.3 takes place

36

The SS-NW transmits an UE TEST LOOP PROSE PACKET COUNTER REQUEST message.

<–

UE TEST LOOP PROSE PACKET COUNTER REQUEST

37

Check: Does the UE respond with UE TEST LOOP PROSE PACKET COUNTER RESPONSE with STCH_PACKET_COUNTER=6?

–>

UE TEST LOOP PROSE PACKET COUNTER RESPONSE

2,3

P

38

The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode.

<–

OPEN UE TEST LOOP

39

The UE transmits an OPEN UE TEST LOOP COMPLETE message.

–>

OPEN UE TEST LOOP COMPLETE

40

The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure.

<–

DEACTIVATE TEST MODE

41

The UE transmits a DEACTIVATE TEST MODE COMPLETE message.

–>

DEACTIVATE TEST MODE COMPLETE

24.1.3.3.3 Specific message contents

Table 24.1.3.3.3-1: SL-V2X-Preconfiguration

Derivation Path: 36.508 [18], table 6.8.2.1-1

Information Element

Value/remark

Comment

Condition

SL-V2X-Preconfiguration-r14 ::= SEQUENCE {

anchorCarrierFreqList-r14 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE {

2 entries

ARFCN-ValueEUTRA-r9[1]

f1

ARFCN-ValueEUTRA-r9[2]

f2

}

}

Table 24.1.3.3.3-2: SystemInformationBlockType21 for Cell 1 (from step 1, Table 24.1.3.3.2-2)

Derivation Path: 36.508 [18], table 4.4.3.3-19

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType21-r14 ::= SEQUENCE {

sl-V2X-ConfigCommon-r14 SEQUENCE {

v2x-InterFreqInfoList-r14 SEQUENCE {

SL-InterFreqInfoV2X-r14[1] SEQUENCE {

v2x-CommCarrierFreq-r14

f5 in TS 36.508 [18] clause 6.2.3.5

v2x-UE-ConfigList-r14 SEQUENCE (SIZE (1.. maxCellIntra)) OF SL-V2X-InterFreqUE-Config-r14 {

1 entry

SL-V2X-InterFreqUE-Config-r14[1] SEQUENCE {

v2x-CommRxPool-r14

Not Present

}

}

}

}

}

}

Note: V2X SideLink communication supported but no resources set for reception.

Table 24.1.3.3.3-3: SystemInformationBlockType21 for Cell 3 (when active, Table 24.1.3.3.2-2)

Derivation Path: 36.508 [18], table 4.4.3.3-19

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType21-r14 ::= SEQUENCE {

v2x-InterFreqInfoList-r14 SEQUENCE {

SL-InterFreqInfoV2X-r14[1] SEQUENCE {

v2x-CommCarrierFreq-r14

f5 in TS 36.508 [18] clause 6.2.3.5

}

}

}

}

}

NOTE: V2X SideLink communication supported; resources for reception in RRC_IDLE provided (SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_2 and COND_RX) v2x-CommTxPoolNormalCommon-r14.

Table 24.1.3.3.3-4: SidelinkUEInformation (V2X) (step 27, Table 24.1.3.3.2-2)

Derivation Path: 36.508 [18], table 4.6.1-21B

Information Element

Value/remark

Comment

Condition

SidelinkUEInformation-r12 ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

sidelinkUEInformation-r12 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

v2x-CommRxInterestedFreqList-r14 SEQUENCE (SIZE (1..maxFreqV2X-r14)) OF INTEGER (0..maxFreqV2X-r14)

[f5 in TS 36.508 [18] clause 6.2.3.5]

v2x-CommTxResourceReq-r14 SEQUENCE (SIZE (1..maxFreqV2X-r14)) OF SEQUENCE {

carrierFreqCommTx-r14

Not checked

Not checked

v2x-TypeTxSync-r14

Not checked.

Not checked.

}

v2x-DestinationInfoList-r14 SEQUENCE (SIZE (1..maxSL-Dest-r12)) OF SEQUENCE {

Not checked.

Not checked.

SL-DestinationIdentity-r12

Not checked

Not checked

}

}

}

}

}

}

}

}

Table 24.1.3.3.3-5: SystemInformationBlockType21 for Cell 1 (from step 29, Table 24.1.3.3.2-2)

Derivation Path: 36.508 [18], table 4.4.3.3-19

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType21-r14 ::= SEQUENCE {

v2x-InterFreqInfoList-r14 SEQUENCE {

SL-InterFreqInfoV2X-r14[1] SEQUENCE {

v2x-CommCarrierFreq-r14

f5 in TS 36.508 [18] clause 6.2.3.5

}

}

}

}

}

NOTE: V2X SideLink communication supported; resources for reception in RRC_IDLE provided (SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_1)