24.1.9 V2X Sidelink Communication / Pre-configured authorisation / Utilisation of the pre-configured resources / Transmission based on zoning

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.9.1 Test Purpose (TP)

(1)

with { UE is authorized for performing V2X sidelink Communication, and UE is out of coverage on the frequency used for V2X sidelink communication, and UE cannot find a cell which provides inter-frequency V2X configuration (i.e. the frequency used to transmit V2X sidelink communication is not included in v2x-InterFreqInfoList in RRCConnectionReconfiguration or in v2x-InterFreqInfoList within SystemInformationBlockType21 or SystemInformationBlockType21 is not broadcasted or there is not suitable cell) on the anchor carrier frequency as the one pre-configured in the UE/USIM and broadcasted in SystemInformationBlockType21 }

ensure that {

when { UE is triggered by an upper layer application to transmit V2X sidelink communication, and, zoneConfig is included in SL-V2X-Preconfiguration }

then { UE transmits V2X sidelink communication using the resources in the resource pool which pre-configured with zoneID equal to the zone identity determined by UE geographical coordinate }

}

24.1.9.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331 subclause 5.10.13.2.

[TS 36.331, clause 5.10.13.2]

For a frequency used for V2X sidelink communication, if zoneConfig is not ignored as specified in 5.10.13.1, the UE configured by upper layers for V2X sidelink communication shall only use the pool which corresponds to geographical coordinates of the UE, if zoneConfig is included in SystemInformationBlockType21 of the serving cell (RRC_IDLE)/ PCell (RRC_CONNECTED) or in RRCConnectionReconfiguration for the concerned frequency, and the UE is configured to use resource pools provided by RRC signalling for the concerned frequency; or if zoneConfig is included in SL-V2X-Preconfiguration for the concerned frequency, and the UE is configured to use resource pools in SL-V2X-Preconfiguration for the frequency, according to 5.10.13.1. The UE shall only use the pool which is associated with the synchronization reference source selected in accordance with 5.10.8.2.

[…]

1> if zoneConfig is included in SL-V2X-Preconfiguration for the concerned frequency and the UE is configured to transmit on v2x-CommTxPoolList in SL-V2X-Preconfiguration for the concerned frequency:

2> select the pool configured with zoneID equal to the zone identity determined below and associated with the synchronization reference source selected in accordance with 5.10.8.2;

The UE shall determine an identity of the zone (i.e. Zone_id) in which it is located using the following formulae, if zoneConfig is included in SystemInformationBlockType21 or in SL-V2X-Preconfiguration:

x1= Floor (x / L) Mod Nx;

y1= Floor (y / W) Mod Ny;

Zone_id = y1 * Nx + x1.

The parameters in the formulae are defined as follows:

L is the value of zoneLength included in zoneConfig in SystemInformationBlockType21 or in SL-V2X-Preconfiguration;

W is the value of zoneWidth included in zoneConfig in SystemInformationBlockType21 or in SL-V2X-Preconfiguration;

Nx is the value of zoneIdLongiMod included in zoneConfig in SystemInformationBlockType21 or in SL-V2X-Preconfiguration;

Ny is the value of zoneIdLatiMod included in zoneConfig in SystemInformationBlockType21 or in SL-V2X-Preconfiguration;

x is the distance in longitude between UE’s current location and geographical coordinates (0, 0) and it is expressed in meters;

y is the distance in latitude between UE’s current location and geographical coordinates (0, 0) and it is expressed in meters.

The UE shall select a pool of resources which includes a zoneID equals to the Zone_id calculated according to above mentioned formulae and indicated by v2x-CommTxPoolNormalDedicated, v2x-CommTxPoolNormalCommon, v2x-CommTxPoolNormal in v2x-InterFreqInfoList or p2x-CommTxPoolNormal in v2x-InterFreqInfoList in RRCConnectionReconfiguration, or v2x-CommTxPoolList according to 5.10.13.1.

NOTE 1: The UE uses its latest geographical coordinates to perform resource pool selection.

24.1.9.3 Test description

24.1.9.3.1 Pre-test conditions

System Simulator:

SS-NW

– No E-UTRA cell configured

– 1 GNSS simulator

SS-UE

– SS-UE1: as defined in TS 36.508 [18], configured for and operating as V2X sidelink Communication Reception 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 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.9.3.1-1.

Table 24.1.9.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.9.3.3-1

Preamble:

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

24.1.9.3.2 Test procedure sequence

Table 24.1.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Trigger 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 UE to close UE test loop mode E (transmission mode).

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 #3: move from zone id0 to zone id1 to zone id3 to zone id2, and starts step 1 to simulate a location in the centre of ZoneID = 0 as defined in TS 36.508 [18] Table 4.11.2-2.

4

Void

5

Check: Does the UE transmit STCH PDCP SDU packet of V2X sidelink communication data over the PC5 interface in accordance with the resources in the resource pool

which pre-configured with zoneID = 0 (SL-V2X-Preconfiguration as defined in Table 24.1.9.3.3-1)?

NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict.

NOTE 2: The structure of the data is not checked and it is just considered as octetstrings by the SS.

–>

STCH PDCP SDU packet

1

P

6

SS configures:

GNSS simulator is triggered to start step 2 of Scenario #3 to simulate the UE moving to a location in the centre of ZoneID = 1 as defined in TS 36.508[18] Table 4.11.2-2.

7

Wait for 64.5 sec (as detailed in TS 36.508 [18] Table 4.11.2-2) to allow the simulated location for the UE to change zone and for the UE to acquire new location data.

8

Check: Does the UE transmit STCH PDCP SDU packet of V2X sidelink communication data over the PC5 interface in accordance with the resources in the resource pool

which pre-configured with zoneID = 1 (SL-V2X-Preconfiguration as defined in Table 24.1.9.3.3-1)?

NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict.

NOTE 2: The structure of the data is not checked and it is just considered as octetstrings by the SS.

–>

STCH PDCP SDU packet

1

P

9

SS configures:

GNSS simulator is triggered to start step 4 of Scenario #3 to simulate the UE moving to a location in the centre of ZoneID = 3 as defined in TS 36.508 [18] Table 4.11.2-2.

10

Wait for 59.5 sec (as detailed in TS 36.508 [18] Table 4.11.2-2) to allow the simulated location for the UE to change zone and for the UE to acquire new location data.

11

Check: Does the UE transmit STCH PDCP SDU packet of V2X sidelink communication data over the PC5 interface in accordance with the resources in the resource pool

which pre-configured with zoneID = 3 (SL-V2X-Preconfiguration as defined in Table 24.1.9.3.3-1)?

NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict.

NOTE 2: The structure of the data is not checked and it is just considered as octetstrings by the SS.

–>

STCH PDCP SDU packet

1

P

12

SS configures:

GNSS simulator is triggered to start step 6 of Scenario #3 to simulate the UE moving to a location in the centre of ZoneID = 2 as defined in TS 36.508 [18] Table 4.11.2-2.

13

Wait for 64.5 sec (as detailed in TS 36.508 [18] Table 4.11.2-2) to allow the simulated location for the UE to change zone and for the UE to acquire new location data.

14

Check: Does the UE transmit STCH PDCP SDU packet of V2X sidelink communication data over the PC5 interface in accordance with the resources in the resource pool

which pre-configured with zoneID = 2 (SL-V2X-Preconfiguration as defined in Table 24.1.9.3.3-1)?

NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict.

NOTE 2: The structure of the data is not checked and it is just considered as octetstrings by the SS.

–>

STCH PDCP SDU packet

1

P

15

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

16

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.9.3.3 Specific message contents

Table 24.1.9.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 {

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

v2x-CommRxPoolList-r14 SEQUENCE (SIZE (1..maxSL-V2X-RxPoolPreconf-r14)) OF SL-V2X-PreconfigCommPool-r14 {

4 entry

SL-V2X-PreconfigCommPool-r14[1] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

11111000000000000000

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

Not present

}

SL-V2X-PreconfigCommPool-r14[2] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

00000111110000000000

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

Not present

}

SL-V2X-PreconfigCommPool-r14[3] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

00000000001111100000

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

Not present

}

SL-V2X-PreconfigCommPool-r14[4] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

00000000000000011111

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

Not present

}

v2x-CommTxPoolList-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPoolPreconf-r14)) OF SL-V2X-PreconfigCommPool-r14 {

SL-V2X-PreconfigCommPool-r14[1] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

11111000000000000000

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

0

}

SL-V2X-PreconfigCommPool-r14[2] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

00000111110000000000

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

1

}

SL-V2X-PreconfigCommPool-r14[3] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

00000000001111100000

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

2

}

SL-V2X-PreconfigCommPool-r14[4] SEQUENCE {

sl-OffsetIndicator-r14

Not present

sl-Subframe-r14 CHOICE {

bs20-r14

00000000000000011111

}

adjacencyPSCCH-PSSCH-r14

true

sizeSubchannel-r14

n5/n10

BW10/ BW20

numSubchannel-r14

n10

startRB-Subchannel-r14

0

startRB-PSCCH-Pool-r14

Not present

rxParametersNCell-r14

Not present

dataTxParameters-r14 {}

Not present

dataTxParameters-r14 SEQUENCE {

alpha-r12

al0

p0-r12

31

}

zoneID-r14

3

}

zoneConfig-r14 SEQUENCE {

zoneLength-r14

m100

zoneWidth-r14

m50

zoneIdLongiMod-r14

2

zoneIdLatiMod-r14

2

}

}

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

1 entry

ARFCN-ValueEUTRA-r9[1]

f1 in TS 36.508 [18] clause 6.2.3.1

}

}