24.1.8 V2X Sidelink Communication / Pre-configured authorisation / UE camped on an E-UTRAN cell operating on the anchor carrier frequency provisioned for V2X configuration / Utilisation of the resources of cells/PLMNs / Transmission based on zoning
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.8.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 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 operating on the anchor carrier frequency as the one pre-configured in the UE/USIM and is broadcasting SystemInformationBlockType21 indicating the resource based on zoning for V2X sidelink communication}
ensure that {
when { UE is triggered by an upper layer application to transmit V2X sidelink communication }
then { UE transmits V2X sidelink communication using the resources in the resource pool which configured with zoneID equal to the zone identity determined by UE geographical coordinate }
}
24.1.8.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.2.2.4, 5.2.2.28, 5.3.5.3, 5.3.10.15a, 5.10.1d, 5.10.2.2, 5.10.13.1, 5.10.13.2. Unless otherwise stated these are Rel-14 requirements.
[TS 36.331, clause 5.10.13.1]
A UE capable of V2X sidelink communication that is configured by upper layers to transmit V2X sidelink communication and has related data to be transmitted 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]; or
2> if the frequency used to transmit V2X sidelink communication is included in v2x-InterFreqInfoList in RRCConnectionReconfiguration or in v2x-InterFreqInfoList within SystemInformationBlockType21:
3> if the UE is in RRC_CONNECTED and uses the PCell or the frequency included in v2x-InterFreqInfoList in RRCConnectionReconfiguration for V2X sidelink communication:
…
4> else if the UE is configured with v2x-commTxPoolNormalDedicated or v2x-CommTxPoolNormal in the entry of v2x-InterFreqInfoList for the concerned frequency in sl-V2X-ConfigDedicated in RRCConnectionReconfiguration and the UE is configured to transmit non-P2X related V2X sidelink communication:
…
5> else:
6> configure lower layers to transmit the sidelink control information and the corresponding data based on sensing (as defined in TS 36.321 [6] and TS 36.213 [23]) using one of the resource pools indicated by v2x-commTxPoolNormalDedicated or v2x-CommTxPoolNormal in the entry of v2x-InterFreqInfoList for the concerned frequency, which is selected according to 5.10.13.2;
…
The UE capable of non-P2X related V2X sidelink communication that is configured by upper layers to transmit V2X sidelink communication shall perform sensing on all pools of resources which may be used for transmission of the sidelink control information and the corresponding data. The pools of resources are indicated by SL-V2X-Preconfiguration, v2x-CommTxPoolNormalCommon, or v2x-commTxPoolNormalDedicated in, as configured above.
[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 the entry of v2x-InterFreqInfoList for the concerned frequency and the UE is configured to transmit on v2x-CommTxPoolNormal in v2x-InterFreqInfoList or p2x-CommTxPoolNormal in v2x-InterFreqInfoList in RRCConnectionReconfiguration; or
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, 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.8.3 Test description
24.1.8.3.1 Pre-test conditions
System Simulator:
SS-NW
– Cell 1
– 1 GNSS simulator
Note 1: The frequency f1 shall be the anchor frequency 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 Cell 1.
– SystemInformationBlockType21 for Cell 1 using parameters as specified in Table 24.1.8.3.3-1.
SS-UE
– SS-UE1. As defined in TS 36.508 [18], configured for and operating as V2X Sidelink Communication receiving 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 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.8.3.1-1.
Table 24.1.8.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.8.3.3-2. |
Preamble:
– The UE is in State Generic Radio Bearer Establishment, UE Test Mode Activated (State 3A) on Cell 1 according to TS 36.508 [18].
24.1.8.3.2 Test procedure sequence
Table 24.1.8.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Close UE Test Loop with bit E0 in UE test loop mode E LB setup IE set to one (transmission mode). |
<– |
CLOSE UE TEST LOOP |
– |
– |
|
2 |
The UE responds with CLOSE UE TEST LOOP COMPLETE. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
3 |
UE transmit a SidelinkUEInformation message requesting resources for monitoring of V2X sidelink communication in RRC_CONNECTED in the next 5 sec. |
–> |
SidelinkUEInformation |
||
|
4 |
SS-NW releases the connection. |
<– |
RRCConnectionRelease |
||
|
4A |
Trigger the UE to reset UTC time. NOTE: The UTC time reset may be performed by MMI or AT command (+CUTCR). |
||||
|
5 |
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. |
||||
|
6 |
Void |
– |
– |
||
|
7 |
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 indicated the zoneConfig in the SystemInformationBlockType21 with zoneID = 0 (Table24.1.8.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 |
|
8 |
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 |
– |
– |
– |
– |
|
9 |
Wait for 64.5 sec (as detailed in TS 36.508 [18] Table 4.11.2-2) to allow the simulated location for the the UE to change zone and for the UE to acquire new location data. |
– |
– |
– |
– |
|
10 |
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 indicated the zoneConfig in the SystemInformationBlockType21 with zoneID = 1 (Table24.1.8.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 |
|
11 |
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. |
– |
– |
– |
– |
|
12 |
Wait for 59.5 sec (as detailed in TS 36.508 [18] Table 4.11.2-2) to allow the simulated location for the the UE to change zone and for the UE to acquire new location data. |
– |
– |
– |
– |
|
13 |
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 indicated the zoneConfig in the SystemInformationBlockType21 with zoneID = 3 (Table 24.1.8.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 |
|
14 |
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. |
– |
– |
– |
– |
|
15 |
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. |
– |
– |
– |
– |
|
16 |
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 indicated the zoneConfig in the SystemInformationBlockType21 with zoneID = 2 (Table24.1.8.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 |
|
17 |
Generic procedure for Generic Radio Bearer Establishment (State 3) defined in TS 36.508 [18] clause 4.5.3 takes place |
||||
|
18 |
The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode. |
<– |
OPEN UE TEST LOOP |
||
|
19 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
||
|
20 |
The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure. |
<– |
DEACTIVATE TEST MODE |
||
|
21 |
The UE transmits a DEACTIVATE TEST MODE COMPLETE message. |
–> |
DEACTIVATE TEST MODE COMPLETE |
||
24.1.8.3.3 Specific message contents
Table 24.1.8.3.3-1: SystemInformationBlockType21 (Preamble)
|
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 (SIZE (0..maxFreqV2X-1-r14)) OF SL-InterFreqInfoV2X-r14 { |
|||
|
SL-InterFreqInfoV2X-r14[1] SEQUENCE { |
|||
|
v2x-CommCarrierFreq-r14 |
f5 in TS 36.508 [18] clause 6.2.3.5 |
||
|
v2x-UE-ConfigList-r14 SEQUENCE { |
|||
|
v2x-CommRxPool-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPool-r14)) OF SL-CommResourcePoolV2X-r14 { |
4 entries |
||
|
SL-CommResourcePoolV2X -r14[1] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
11111000000000000000 |
||
|
} |
|||
|
SL-CommResourcePoolV2X -r14[2] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
00000111110000000000 |
||
|
} |
|||
|
SL-CommResourcePoolV2X -r14[3] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
00000000001111100000 |
||
|
} |
|||
|
SL-CommResourcePoolV2X -r14[4] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
00000000000000011111 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
v2x-CommTxPoolNormal–r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPool-r14)) OF SL-CommResourcePoolV2X-r14 { |
4 entries |
||
|
SL-CommResourcePoolV2X -r14[1] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
11111000000000000000 |
||
|
} |
|||
|
zoneID-r14 |
0 |
||
|
} |
|||
|
SL-CommResourcePoolV2X -r14[2] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
00000111110000000000 |
||
|
} |
|||
|
zoneID-r14 |
1 |
||
|
} |
|||
|
SL-CommResourcePoolV2X -r14[3] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
00000000001111100000 |
||
|
} |
|||
|
zoneID-r14 |
2 |
||
|
} |
|||
|
SL-CommResourcePoolV2X -r14[4] SEQUENCE { |
|||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
00000000000000011111 |
||
|
} |
|||
|
zoneID-r14 |
3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
zoneConfig-r14 SEQUENCE { |
|||
|
zoneLength-r14 |
m100 |
||
|
zoneWidth-r14 |
m50 |
||
|
zoneIdLongiMod-r14 |
2 |
||
|
zoneIdLatiMod-r14 |
2 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.1.8.3.3-2: SL-V2X-Preconfiguration
|
Derivation Path: 36.508 [18], table 4.10.1.1-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SL-V2X-Preconfiguration-r14 ::= SEQUENCE { |
|||
|
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 |
||
|
} |
|||
|
} |
|||