24.2 P2X Sidelink Communication
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.2.1 P2X 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 / Transmission / Partial sensing
24.2.1.1 Test Purpose (TP)
(1)
with { UE supporting V2X sidelink communication }
ensure that {
when { UE performs Attach procedure, or, Normal tracking area updating procedure }
then { UE announces its V2X communication over PC5 supported capabilities }
}
(2)
with { UE supporting partial sensing and 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 transmitting SystemInformationBlockType21 with partialSensing selected in resourceSelectionConfigP2X }
ensure that {
when { UE is triggered by an upper layer application to transmit V2X sidelink communication }
then { UE is able to transmit V2X sidelink communication based on partial sensing in Cell1/f1/PLMN1 via SystemInformationBlockType21 }
}
24.2.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.301 clause 5.5.1.2.2, TS 36.331 clauses 5.2.2.4, 5.2.2.28 and 5.10.13.1a.
[TS 24.301, clause 5.5.1.2.2]
If the UE supports V2X communication over PC5, then the UE shall set the V2X PC5 bit to "V2X communication over PC5 supported" in the UE network capability IE of the ATTACH REQUEST message.
[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 schedulingInfoList on the serving cell/PCell indicates that SystemInformationBlockType21 is present and the UE does not have stored a valid version of this system information block:
3> acquire SystemInformationBlockType21 from serving cell/PCell;
[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, p2x-CommTxPoolNormalCommon, v2x-CommTxPoolNormal, p2x-CommTxPoolNormal 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, v2x-CommTxPoolNormal and v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.5.3;
[TS 36.331, clause 5.10.13.1a]
A UE configured to transmit P2X related V2X sidelink communication shall:
1> if partialSensing is included and randomSelection is not included in resourceSelectionConfigP2X of the pool selected; or
1> if both partialSensing and randomSelection are included in resourceSelectionConfigP2X of the pool selected, and the UE selects to use partial sensing:
2> configure lower layers to transmit the sidelink control information and the corresponding data based on partial sensing (as defined in TS 36.321 [6] and TS 36.213 [23]) using the selected resource pool, if the UE supports partial sensing;
1> if partialSensing is not included and randomSelection is included in resourceSelectionConfigP2X of the pool selected.
2> configure lower layers to transmit the sidelink control information and the corresponding data based on random selection (as defined in TS 36.321 [6] and TS 36.213 [23]) using the selected resource pool;
1> if both partialSensing and randomSelection is included in resourceSelectionConfigP2X of the pool selected, and the UE selects to use random selection:
2> configure lower layers to transmit the sidelink control information and the corresponding data based on random selection using the selected resource pool and indicates to lower layers that transmissions of multiple MAC PDUs are allowed (as defined in TS 36.321 [6] and TS 36.213 [23]).
NOTE: If both partialSensing and randomSelection is included in resourceSelectionConfigP2X of the pool selected, the selection between partial sensing and random selection is left to UE implementation.
24.2.1.3 Test description
24.2.1.3.1 Pre-test conditions
System Simulator:
SS-NW
– Cell 1
– 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.2.1.3.3-2.
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:
– Pedestrian UE- The UE support the partial sensing capability.
– 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.2.1.3.1-1.
Table 24.2.1.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 |
As per TS 36.508 [18] clause 4.9.3.4. SL-V2X-Preconfiguration field as defined in Table 24.2.1.3.3-1 |
Preamble
– The UE is in State Switched OFF (state 1) according to TS 36.508 [18].
24.2.1.3.2 Test procedure sequence
Table 24.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The UE is switched on |
– |
– |
– |
– |
|
2 |
Check: Does the Generic test procedure from step 1 to 18 for ‘UE Registration (State 2A)’ defined in TS 36.508 [18] clause 4.5.2A takes place during which the UE announces its V2X sidelink communication capabilities in the ATTACH REQUEST message? |
– |
– |
1 |
P |
|
3 |
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 |
– |
– |
|
4 |
The UE responds with CLOSE UE TEST LOOP COMPLETE |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
5 |
SS-NW releases the connection |
<– |
RRCConnectionRelease |
– |
– |
|
6 |
Check: Does the UE transmit STCH PDCP SDU packets of V2X sidelink communication data over the PC5 interface in accordance with the resources indicated in Cell 1 SystemInformationBlockType21? 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 |
2 |
P |
|
7 |
The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode. |
<– |
OPEN UE TEST LOOP |
– |
– |
|
8 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
9 |
The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure |
<– |
DEACTIVATE TEST MODE |
– |
– |
|
10 |
The UE transmits a DEACTIVATE TEST MODE COMPLETE message |
–> |
DEACTIVATE TEST MODE COMPLETE |
– |
– |
24.2.1.3.3 Specific message contents
Table 24.2.1.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 ARFCN-ValueEUTRA-r9 SEQUENCE { |
1 entry |
||
|
ARFCN-ValueEUTRA-r9[1] |
f1 in TS 36.508 [18] clause 6.2.3.1 |
||
|
} |
|||
|
} |
|||
Table 24.2.1.3.3-2: SystemInformationBlockType21 for Cell 1 (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 (1..maxFreq)) OF SL-InterFreqInfoV2X-r14 { |
1 entry |
||
|
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 { |
|||
|
p2x-CommTxPoolNormal-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPool-r14)) OF SL-CommResourcePoolV2X-r14 { |
1 entry |
||
|
SL-CommResourcePoolV2X-r14[1] SEQUENCE { |
SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_1 and COND_TX |
||
|
resourceSelectionConfigP2X-r14 SEQUENCE { |
|||
|
partialSensing-r14 |
true |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.2.1.3.3-3: ATTACH REQUEST (step 2 Table 24.2.1.3.2-1; step 4 TS 36.508 [18] Table 4.5.2.3-1)
|
Derivation path: 36.508 [18] , table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
UE network capability |
|||
|
V2X communication over PC5 (V2X PC5) (octet 9, bit 2) |
‘1’ |
V2X communication over PC5 supported |
|
24.2.2 P2X 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 / Transmission / Random selection
24.2.2.1 Test Purpose (TP)
(1)
with { UE supporting V2X sidelink communication }
ensure that {
when { UE performs Attach procedure, or, Normal tracking area updating procedure }
then { UE announces its V2X communication over PC5 supported capabilities }
}
(2)
with { UE NOT supporting partial sensing and 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 transmitting SystemInformationBlockType21 with partialSensing selected in resourceSelectionConfigP2X }
ensure that {
when { UE is triggered by an upper layer application to transmit V2X sidelink communication }
then { UE does not initiate V2X sidelink Communication }
}
(3)
with { UE NOT supporting partial sensing and 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 transmitting SystemInformationBlockType21 with randomSelection selected in resourceSelectionConfigP2X }
ensure that {
when { UE is triggered by an upper layer application to transmit V2X sidelink communication }
then { UE is able to transmit V2X sidelink communication based on resourceSelectionConfigP2X in SystemInformationBlockType21 }
}
24.2.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.301 clause 5.5.1.2.2, TS 36.331 clauses 5.2.2.4, 5.2.2.28 and 5.10.13.1a.
[TS 24.301, clause 5.5.1.2.2]
If the UE supports V2X communication over PC5, then the UE shall set the V2X PC5 bit to "V2X communication over PC5 supported" in the UE network capability IE of the ATTACH REQUEST message.
[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 schedulingInfoList on the serving cell/PCell indicates that SystemInformationBlockType21 is present and the UE does not have stored a valid version of this system information block:
3> acquire SystemInformationBlockType21 from serving cell/PCell;
[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, p2x-CommTxPoolNormalCommon, v2x-CommTxPoolNormal, p2x-CommTxPoolNormal 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, v2x-CommTxPoolNormal and v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.5.3;
[TS 36.331, clause 5.10.13.1a]
A UE configured to transmit P2X related V2X sidelink communication shall:
1> if partialSensing is included and randomSelection is not included in resourceSelectionConfigP2X of the pool selected; or
1> if both partialSensing and randomSelection are included in resourceSelectionConfigP2X of the pool selected, and the UE selects to use partial sensing:
2> configure lower layers to transmit the sidelink control information and the corresponding data based on partial sensing (as defined in TS 36.321 [6] and TS 36.213 [23]) using the selected resource pool, if the UE supports partial sensing;
1> if partialSensing is not included and randomSelection is included in resourceSelectionConfigP2X of the pool selected.
2> configure lower layers to transmit the sidelink control information and the corresponding data based on random selection (as defined in TS 36.321 [6] and TS 36.213 [23]) using the selected resource pool;
1> if both partialSensing and randomSelection is included in resourceSelectionConfigP2X of the pool selected, and the UE selects to use random selection:
2> configure lower layers to transmit the sidelink control information and the corresponding data based on random selection using the selected resource pool and indicates to lower layers that transmissions of multiple MAC PDUs are allowed (as defined in TS 36.321 [6] and TS 36.213 [23]).
NOTE: If both partialSensing and randomSelection is included in resourceSelectionConfigP2X of the pool selected, the selection between partial sensing and random selection is left to UE implementation.
24.2.2.3 Test description
24.2.2.3.1 Pre-test conditions
System Simulator:
SS-NW
– Cell 1
– 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.2.2.3.3-2, in which partialSensing is selected.
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:
– Pedestrian UE
– The UE do not support the partial sensing capability.
– 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.2.2.3.1-1.
Table 24.2.2.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 |
As per TS 36.508 [18] clause 4.9.3.4. SL-V2X-Preconfiguration field as defined in Table 24.2.2.3.3-1 |
Preamble:
– The UE is in State Switched OFF (state 1) according to TS 36.508 [18].
24.2.2.3.2 Test procedure sequence
Table 24.2.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The UE is switched on. |
– |
– |
– |
– |
|
2 |
Check: Does the Generic test procedure from step 1 to 18 for ‘UE Registration (State 2A)’ defined in TS 36.508 [18] clause 4.5.2A takes place during which the UE announces its V2X sidelink communication capabilities in the ATTACH REQUEST message? |
– |
– |
1 |
P |
|
3 |
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 |
– |
– |
|
4 |
The UE responds with CLOSE UE TEST LOOP COMPLETE. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
5 |
SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
6 |
Check: Does the UE transmit in the next 60 sec STCH PDCP SDU packets of V2X sidelink communication data over the PC5 interface? |
–> |
STCH PDCP SDU packet |
2 |
F |
|
7 |
SS-NW changes SystemInformationBlockType21 which randomSelection is selected according to Table 24.2.2.3.3-3. |
– |
|||
|
8 |
The SS transmits a Paging message in a paging occasion including a systemInfoModification. |
<– |
Paging |
||
|
9 |
Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType21. |
– |
|||
|
10 |
Check: Does the UE transmit STCH PDCP SDU packets of V2X sidelink communication data over the PC5 interface in accordance with the resources indicated in Cell 1 SystemInformationBlockType21? 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 |
3 |
P |
|
11 |
The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode. |
<– |
OPEN UE TEST LOOP |
– |
– |
|
12 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
13 |
The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure. |
<– |
DEACTIVATE TEST MODE |
– |
– |
|
14 |
The UE transmits a DEACTIVATE TEST MODE COMPLETE message. |
–> |
DEACTIVATE TEST MODE COMPLETE |
– |
– |
24.2.2.3.3 Specific message contents
Table 24.2.2.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 ARFCN-ValueEUTRA-r9 SEQUENCE { |
1 entry |
||
|
ARFCN-ValueEUTRA-r9[1] |
f1 in TS 36.508 [18] clause 6.2.3.1 |
||
|
} |
|||
|
} |
|||
Table 24.2.2.3.3-2: SystemInformationBlockType21 for Cell 1 (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 (1..maxFreq)) OF SL-InterFreqInfoV2X-r14 { |
1 entry |
||
|
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 { |
|||
|
p2x-CommTxPoolNormal-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPool-r14)) OF SL-CommResourcePoolV2X-r14 { |
1 entry |
||
|
SL-CommResourcePoolV2X-r14[1] SEQUENCE { |
SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_1 and COND_TX |
||
|
resourceSelectionConfigP2X-r14 SEQUENCE { |
|||
|
partialSensing-r14 |
true |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.2.2.3.3-3: ATTACH REQUEST (step 2 Table 24.2.2.3.2-1; step 4 TS 36.508 [18] Table 4.5.2.3-1)
|
Derivation path: 36.508 [18] , table 4.7.2-4 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
UE network capability |
|||
|
V2X communication over PC5 (V2X PC5) (octet 9, bit 2) |
‘1’ |
V2X communication over PC5 supported |
|
Table 24.2.2.3.3-4: SystemInformationBlockType21 for Cell 1 (step 7, Table 24.2.2.3.2-1)
|
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 (1..maxFreq)) OF SL-InterFreqInfoV2X-r14 { |
1 entry |
||
|
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 { |
|||
|
p2x-CommTxPoolNormal-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPool-r14)) OF SL-CommResourcePoolV2X-r14 { |
1 entry |
||
|
SL-CommResourcePoolV2X-r14[1] SEQUENCE { |
SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_1 and COND_TX |
||
|
resourceSelectionConfigP2X-r14 SEQUENCE { |
|||
|
randomSelection-r14 |
true |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
24.2.3 P2X Sidelink Communication / Pre-configured authorisation / Utilisation of the pre-configured resources / Transmission
24.2.3.1 Test Purpose (TP)
(1)
with { UE being authorized as Pedestrian UE 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 transmit V2X sidelink Communication, and, UE determines itself as being located in that geographical area }
then { UE is able to transmit V2X sidelink Communication using the preconfigured for "not served by E-UTRAN" resources }
}
(2)
with { UE being authorized as Pedestrian UE 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 transmit V2X sidelink Communication, and, UE determines itself as being not located in that geographical area }
then { UE does not initiate V2X sidelink Communication }
}
24.2.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 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.2.3.3 Test description
24.2.3.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 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:
– Pedestrian UE
– The UE is equipped with below information in UE or in a USIM containing default values (as per TS 36.508 [18]).
Table 24.2.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 |
As per TS 36.508 [18] clause 4.9.3.4. SL-V2X-Preconfiguration field as defined in Table 24.2.3.3.3-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.2.3.3.2 Test procedure sequence
Table 24.2.3.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). NOTE: The UE test loop mode E may be closed by MMI or AT command (+CCUTLE). |
– |
– |
– |
– |
|
3 |
Trigger the UE to reset UTC time. NOTE: The UTC time reset may be performed by MMI or AT command (+CUTCR). |
– |
– |
– |
– |
|
4 |
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. |
||||
|
5 |
Check: Does the UE transmit V2X sidelink communication data over the PC5 interface in accordance with the resources pre-configured in p2x-CommTxPoolList-r14? |
–> |
STCH PDCP SDU packet |
1 |
P |
|
6 |
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. |
||||
|
7 |
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. |
– |
– |
– |
– |
|
8 |
Check: Does the UE transmit, in the next 10 seconds, V2X sidelink communication data over the PC5 interface ? |
–> |
STCH PDCP SDU packet |
2 |
F |
|
9 |
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). |
– |
– |
– |
– |
|
10 |
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.2.3.3.3 Specific message contents
Table 24.2.3.3.3-1: 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 { |
|||
|
v2x-PreconfigFreqList-r14 (SIZE (1..maxFreqV2X-r14)) OF SL-V2X-PreconfigFreqInfo-r14 SEQUENCE { |
1 entry |
||
|
SL-V2X-PreconfigFreqInfo-r14[1] SEQUENCE { |
|||
|
v2x-CommTxPoolList-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPoolPreconf-r14)) OF SL-V2X-PreconfigCommPool-r14 { |
1 entry |
||
|
SL-V2X-PreconfigCommPool-r14[1] |
SL-V2X-PreconfigCommPool-r14-DEFAULT using conditions BITMAP_2 and COND_TX |
||
|
} |
|||
|
p2x-CommTxPoolList-r14 (SIZE (1..maxSL-V2X-TxPoolPreconf-r14)) OF SL-V2X-PreconfigCommPool-r14 SEQUENCE { |
1 entry |
||
|
SL-V2X-PreconfigCommPool-r14[1] |
SL-V2X-PreconfigCommPool-r14-DEFAULT using condition BITMAP_1 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
24.2.4 P2X Sidelink Communication / Pre-configured authorisation / UE in RRC_IDLE on an E-UTRAN cell operating on the anchor carrier frequency for V2X configuration/ UE transmits V2X sidelink communication using Tx parameters based on PPPP and configured CBR
24.2.4.1 Test Purpose (TP)
(1)
with { UE being authorized as Pedestrian UE 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 transmitting SystemInformationBlockType21 which includes cbr-CommonTxConfigList-r14 and p2x-CommTxPoolNormal-r14 }
ensure that {
when { UE is triggered by an upper layer application to transmit V2X sidelink communication with configured PPPP and configured CBR are available }
then { UE is able to transmit V2X sidelink communication using the configured resources associated with the configured PPPP and configured CBR based on the SystemInformationBlockType21}
}
24.2.4.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.14.1.1, TS 36.331, clauses 5.10.13.1 and clause 5.10.13.1].
[TS 36.321, clause 5.14.1.1]
Sidelink grants are selected as follows for V2X sidelink communication:
– if the MAC entity is configured to receive a sidelink grant dynamically on the PDCCH and data is available in STCH, the MAC entity shall:
[…]
– if the MAC entity is configured by upper layers to transmit using a pool of resources as indicated in subclause 5.10.13.1 of [8] based on sensing, or partial sensing, or random selection only if upper layers indicates that transmissions of multiple MAC PDUs are allowed according to subclause 5.10.13.1a of [8], and the MAC entity selects to create a configured sidelink grant corresponding to transmissions of multiple MAC PDUs, and data is available in STCH, the MAC entity shall for each Sidelink process configured for multiple transmissions:
– if SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER was equal to 1 the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is above the probability configured by upper layers in probResourceKeep; or
– if neither transmission nor retransmission has been performed by the MAC entity on any resource indicated in the configured sidelink grant during the last second; or
– if sl-ReselectAfter is configured and the number of consecutive unused transmission opportunities on resources indicated in the configured sidelink grant is equal to sl-ReselectAfter; or
– if there is no configured sidelink grant; or
– if the configured sidelink grant cannot accommodate a RLC SDU by using the maximum allowed MCS configured by upper layers in maxMCS-PSSCH and the MAC entity selects not to segment the RLC SDU; or
NOTE: If the configured sidelink grant cannot accommodate the RLC SDU, it is left for UE implementation whether to perform segmentation or sidelink resource reselection.
– if transmission(s) with the configured sidelink grant cannot fulfil the latency requirement of the data in a sidelink logical channel according to the associated PPPP, and the MAC entity selects not to perform transmission(s) corresponding to a single MAC PDU; or
NOTE: If the latency requirement is not met, it is left for UE implementation whether to perform transmission(s) corresponding to single MAC PDU or sidelink resource reselection.
– if a pool of resources is configured or reconfigured by upper layers:
– clear the configured sidelink grant, if available;
– select one of the allowed values configured by upper layers in restrictResourceReservationPeriod and set the resource reservation interval by multiplying 100 with the selected value;
NOTE: How the UE selects this value is up to UE implementation.
– randomly select, with equal probability, an integer value in the interval [5, 15] for the resource reservation interval higher than or equal to 100ms, in the interval [10, 30] for the resource reservation interval equal to 50ms or in the interval [25, 75] for the resource reservation interval equal to 20ms, and set SL_RESOURCE_RESELECTION_COUNTER to the selected value;
– select the number of HARQ retransmissions from the allowed numbers that are configured by upper layers in allowedRetxNumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped in allowedRetxNumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) and the CBR measured by lower layers according to [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available;
– select an amount of frequency resources within the range that is configured by upper layers between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) and the CBR measured by lower layers according to [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available;
– if transmission based on random selection is configured by upper layers:
– randomly select the time and frequency resources for one transmission opportunity from the resource pool, according to the amount of selected frequency resources. The random function shall be such that each of the allowed selections can be chosen with equal probability;
– else:
– randomly select the time and frequency resources for one transmission opportunity from the resources indicated by the physical layer according to subclause 14.1.1.6 of [2], according to the amount of selected frequency resources. The random function shall be such that each of the allowed selections can be chosen with equal probability;
– use the randomly selected resource to select a set of periodic resources spaced by the resource reservation interval for transmission opportunities of SCI and SL-SCH corresponding to the number of transmission opportunities of MAC PDUs determined in subclause 14.1.1.4B of [2];
– if the number of HARQ retransmissions is equal to 1 and there are available resources left in the resources indicated by the physical layer that meet the conditions in subclause 14.1.1.7 of [2] for more transmission opportunities:
– randomly select the time and frequency resources for one transmission opportunity from the available resources, according to the amount of selected frequency resources. The random function shall be such that each of the allowed selections can be chosen with equal probability;
– use the randomly selected resource to select a set of periodic resources spaced by the resource reservation interval for the other transmission opportunities of SCI and SL-SCH corresponding to the number of retransmission opportunities of the MAC PDUs determined in subclause 14.1.1.4B of [2];
– consider the first set of transmission opportunities as the new transmission opportunities and the other set of transmission opportunities as the retransmission opportunities;
– consider the set of new transmission opportunities and retransmission opportunities as the selected sidelink grant.
– else:
– consider the set as the selected sidelink grant;
– use the selected sidelink grant to determine the set of subframes in which transmissions of SCI and SL-SCH occur according to subclause 14.2.1 and 14.1.1.4B of [2];
– consider the selected sidelink grant to be a configured sidelink grant;
– else if SL_RESOURCE_RESELECTION_COUNTER = 0 and when SL_RESOURCE_RESELECTION_COUNTER was equal to 1 the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is less than or equal to the probability configured by upper layers in probResourceKeep:
– clear the configured sidelink grant, if available;
– randomly select, with equal probability, an integer value in the interval [5, 15] for the resource reservation interval higher than or equal to 100ms, in the interval [10, 30] for the resource reservation interval equal to 50ms or in the interval [25, 75] for the resource reservation interval equal to 20ms, and set SL_RESOURCE_RESELECTION_COUNTER to the selected value;
– use the previously selected sidelink grant for the number of transmissions of the MAC PDUs determined in subclause 14.1.1.4B of [2] with the resource reservation interval to determine the set of subframes in which transmissions of SCI and SL-SCH occur according to subclause 14.2.1 and 14.1.1.4B of [2];
– consider the selected sidelink grant to be a configured sidelink grant;
– else, if the MAC entity is configured by upper layers to transmit using a pool of resources as indicated in subclause 5.10.13.1 of [8], the MAC entity selects to create a configured sidelink grant corresponding to transmission(s) of a single MAC PDU, and data is available in STCH, the MAC entity shall for a Sidelink process:
– select the number of HARQ retransmissions from the allowed numbers that are configured by upper layers in allowedRetxNumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped in allowedRetxNumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) and the CBR measured by lower layers according to [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available;
– select an amount of frequency resources within the range that is configured by upper layers between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH included in pssch-TxConfigList and, if configured by upper layers, overlapped between minSubchannel-NumberPSSCH and maxSubchannel-NumberPSSCH indicated in cbr-pssch-TxConfigList for the highest priority of the sidelink logical channel(s) and the CBR measured by lower layers according to [6] if CBR measurement results are available or the corresponding defaultTxConfigIndex configured by upper layers if CBR measurement results are not available;
– if transmission based on random selection is configured by upper layers:
– randomly select the time and frequency resources for one transmission opportunity of SCI and SL-SCH from the resource pool, according to the amount of selected frequency resources. The random function shall be such that each of the allowed selections can be chosen with equal probability;
– else:
– randomly select the time and frequency resources for one transmission opportunity of SCI and SL-SCH from the resource pool indicated by the physical layer according to subclause 14.1.1.6 of [2] , according to the amount of selected frequency resources. The random function shall be such that each of the allowed selections can be chosen with equal probability;
– if the number of HARQ retransmissions is equal to 1:
– if transmission based on random selection is configured by upper layers and there are available resources that meet the conditions in subcause 14.1.1.7 of [2] for one more transmission opportunity:
– randomly select the time and frequency resources for the other transmission opportunity of SCI and SL-SCH corresponding to additional transmission of the MAC PDU from the available resources, according to the amount of selected frequency resources. The random function shall be such that each of the allowed selections can be chosen with equal probability;
– else, if transmission based on sensing or partial sensing is configured by upper layers and there are available resources left in the resources indicated by the physical layer that meet the conditions in subcause 14.1.1.7 of [2] for one more transmission opportunity:
– randomly select the time and frequency resources for the other transmission opportunity of SCI and SL-SCH corresponding to additional transmission of the MAC PDU from the available resources, according to the amount of selected frequency resources. The random function shall be such that each of the allowed selections can be chosen with equal probability;
– consider a transmission opportunity which comes first in time as the new transmission opportunity and a transmission opportunity which comes later in time as the retransmission opportunity;
– consider both of the transmission opportunities as the selected sidelink grant;
– else:
– consider the transmission opportunity as the selected sidelink grant;
– use the selected sidelink grant to determine the subframes in which transmission(s) of SCI and SL-SCH occur according to subclause 14.2.1 and 14.1.1.4B of [2];
– consider the selected sidelink grant to be a configured sidelink grant;
NOTE: For V2X sidelink communication, the UE should ensure the randomly selected time and frequency resources fulfil the latency requirement.
NOTE: For V2X sidelink communication, when there is no overlapping between the chosen configuration(s) in pssch-TxConfigList and chosen configuration(s) indicated in cbr-pssch-TxConfigList, it is up to UE implementation whether the UE transmits and which transmitting parameters the UE uses between allowed configuration(s) indicated in pssch-TxConfigList and allowed configuration(s) indicated in cbr-pssch-TxConfigList.
The MAC entity shall for each subframe:
– if the MAC entity has a configured sidelink grant occurring in this subframe:
– if SL_RESOURCE_RESELECTION_COUNTER = 1 and the MAC entity randomly selected, with equal probability, a value in the interval [0, 1] which is above the probability configured by upper layers in probResourceKeep:
– set the resource reservation interval equal to 0;
– if the configured sidelink grant corresponds to transmission of SCI:
– instruct the physical layer to transmit SCI corresponding to the configured sidelink grant;
– for V2X sidelink communication, deliver the configured sidelink grant, the associated HARQ information and the value of the highest priority of the sidelink logical channel(s) in the MAC PDU to the Sidelink HARQ Entity for this subframe;
– else if the configured sidelink grant corresponds to transmission of first transport block for sidelink communication:
– deliver the configured sidelink grant and the associated HARQ information to the Sidelink HARQ Entity for this subframe.
NOTE: If the MAC entity has multiple configured grants occurring in one subframe and if not all of them can be processed due to the single-cluster SC-FDM restriction, it is left for UE implementation which one of these to process according to the procedure above.
[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:
[…]
3> else:
4> if the cell chosen for V2X sidelink communication transmission broadcasts SystemInformationBlockType21:
5> if the UE is configured to transmit non-P2X related V2X sidelink communication, and if SystemInformationBlockType21 includes v2x-CommTxPoolNormalCommon or v2x-CommTxPoolNormal in v2x-InterFreqInfoList for the concerned frequency in sl-V2X-ConfigCommon and a result of sensing on the resources configured in v2x-CommTxPoolNormalCommon or v2x-CommTxPoolNormal in v2x-InterFreqInfoList for the concerned frequency is available in accordance with TS 36.213 [23]:
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-CommTxPoolNormalCommon or v2x-CommTxPoolNormal in v2x-InterFreqInfoList for the concerned frequency, which is selected according to 5.10.13.2;
5> else if the UE is configured to transmit P2X related V2X sidelink communication, and if SystemInformationBlockType21 includes p2x-CommTxPoolNormalCommon or p2x-CommTxPoolNormal in v2x-InterFreqInfoList for the concerned frequency in sl-V2X-ConfigCommon:
6> select a resource pool from p2x-CommTxPoolNormalCommon or p2x-CommTxPoolNormal in v2x-InterFreqInfoList for the concerned frequency according to 5.10.13.2, but ignoring zoneConfig in SystemInformationBlockType21;
6> transmit P2X related V2X sidelink communication according to 5.10.13.1a;
5> else if SystemInformationBlockType21 includes v2x-CommTxPoolExceptional in sl-V2X-ConfigCommon or v2x-CommTxPoolExceptional in v2x-InterFreqInfoList for the concerned frequency:
6> from the moment the UE initiates connection establishment until receiving an RRCConnectionReconfiguration including sl-V2X-ConfigDedicated, or until receiving an RRCConnectionRelease or an RRCConnectionReject; or
6> if the UE is in RRC_IDLE and a result of sensing on the resources configured in v2x-CommTxPoolNormalCommon or v2x-CommTxPoolNormal in v2x-InterFreqInfoList for the concerned frequency in Systeminformationblocktype21 is not available in accordance with TS 36.213 [23]:
7> configure lower layers to transmit the sidelink control information and the corresponding data based on random selection (as defined in TS 36.321 [6]) using the pool of resources indicated in v2x-CommTxPoolExceptional;
2> else:
3> 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-CommTxPoolList in SL-V2X-Preconfiguration in case of non-P2X related V2X sidelink communication, which is selected according to 5.10.13.2, or using one of the resource pools indicated by p2x-CommTxPoolList in SL-V2X-Preconfiguration in case of P2X related V2X sidelink communication, which is selected according to 5.10.13.2, and in accordance with the timing of the selected reference as defined in 5.10.8;
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, v2x-CommTxPoolNormalDedicated in sl-V2X-ConfigDedicated, or v2x-CommTxPoolNormal in v2x-InterFreqInfoList for the concerned frequency, as configured above.
NOTE 1: If there are multiple frequencies for which normal or exceptional pools are configured, it is up to UE implementation which frequency is selected for V2X sidelink communication transmission.
24.2.4.3 Test description
24.2.4.3.1 Pre-test conditions
System Simulator:
SS-NW
– Cell 1
Table 24.2.4.3.1-1: Cell parameters values
|
Cell |
Frequency |
PLMN |
|
1 |
f1 |
PLMN1 |
|
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 Cell1.
– SystemInformationBlockType21 for Cell 1 using parameters as specified in Table 24.2.4.3.3-2.
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:
– Pedestrian UE
– The UE is authorised to perform V2X Sidelink Communication, with ProSe Per-Packet Priority (PPPP) set to 2 (FFS).
– 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.2.4.3.1-1.
Table 24.2.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 Table 24.2.4.3.3-1 |
Preamble:
– The UE is in State Generic Radio Bearer Establishment, UE Test Mode E Activated (State 3A) on Cell 1 according to TS 36.508 [18].
24.2.4.3.2 Test procedure sequence
Table 24.2.4.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 transmits a SidelinkUEInformation message requesting resources for transmission of V2X sidelink communication in RRC_CONNECTED in the next 5 sec. |
–> |
SidelinkUEInformation |
– |
– |
|
4 |
SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
5 |
Check: Does the UE transmit data on the V2X sidelink communication with MCS =17 in Tx parameters of sl-CBR-PSSCH-TxConfig[1] specified in Table 24.2.4.3.3-3? NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. |
–> |
STCH PDCP SDU packet |
1 |
P |
|
6 |
SS-NW changes SystemInformationBlockType21 with new CBR configuration in cbr-pssch-TxConfigList-r14 specified in Table 24.2.4.3.3-6. |
– |
– |
– |
– |
|
7 |
The SS transmits a Paging message in a paging occasion including a systemInfoModification. |
<– |
Paging |
– |
– |
|
8 |
Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType21. |
– |
– |
||
|
9 |
Check: Does the UE transmit data on the V2X sidelink communication with MCS = 8 in Tx parameters of sl-CBR-PSSCH-TxConfig[2] specified in Table 24.2.4.3.3-3? NOTE: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. |
–> |
STCH PDCP SDU packet |
1 |
P |
|
10 |
Generic procedure as specified in TS 36.508 [18] Table 4.5.3.3-1 |
– |
– |
– |
– |
|
11 |
The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode. |
<– |
OPEN UE TEST LOOP |
– |
– |
|
12 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
13 |
The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure. |
<– |
DEACTIVATE TEST MODE |
||
|
14 |
The UE transmits a DEACTIVATE TEST MODE COMPLETE message. |
–> |
DEACTIVATE TEST MODE COMPLETE |
||
24.2.4.3.3 Specific message contents
Table 24.2.4.3.3-1: 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 |
||
|
} |
|||
|
} |
|||
Table 24.2.4.3.3-2: SystemInformationBlockType21 for Cell 1 (preamble, Table 24.2.4.3.2-1)
|
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 (1..maxFreq)) OF SL-InterFreqInfoV2X-r14 { |
1 entry |
||
|
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 { |
|||
|
p2x-CommTxPoolNormal-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPool-r14)) OF SL-CommResourcePoolV2X-r14 { |
1 entry |
||
|
SL-CommResourcePoolV2X-r14[1] SEQUENCE { |
|||
|
sl-OffsetIndicator-r14 |
Not present |
||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
11111111111111111111 |
BITMAP_6 |
|
|
} |
|||
|
adjacencyPSCCH-PSSCH-r14 |
true |
BOOLEAN |
|
|
sizeSubchannel-r14 |
n5 |
Independent to BW |
|
|
numSubchannel-r14 |
n10 |
||
|
startRB-Subchannel-r14 |
0 |
||
|
startRB-PSCCH-Pool-r14 |
Not present |
||
|
rxParametersNCell-r14 |
Not present |
||
|
dataTxParameters-r14 {} |
Not present |
||
|
dataTxParameters-r14 SEQUENCE { |
COND_TX |
||
|
alpha-r12 |
al0 |
||
|
p0-r12 |
31 |
||
|
} |
|||
|
zoneID-r14 |
Not present |
INTEGER (0..7) |
|
|
threshS-RSSI-CBR-r14 |
23 |
-66 dBm |
BW10 |
|
poolReportId-r14 |
Not present |
||
|
cbr-pssch-TxConfigList-r14 SEQUENCE (SIZE (1..8)) OF SL-PPPP-TxConfigIndex-r14{ |
1 entry |
||
|
sl-PPPP-TxConfigIndex-r14[1] SEQUENCE { |
|||
|
priorityThreshold-r14 |
8 |
||
|
defaultTxConfigIndex-r14 |
0 |
||
|
cbr-ConfigIndex-r14 |
0 |
||
|
tx-ConfigIndexList-r14 := SEQUENCE (SIZE (1..maxCBR-Level-r14)) OF Tx-ConfigIndex-r14 { |
3 entries |
||
|
tx-ConfigIndex[1] |
0 |
||
|
tx-ConfigIndex[2] |
1 |
||
|
tx-ConfigIndex[3] |
2 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
resourceSelectionConfigP2X-r14 |
Not present |
||
|
syncAllowed-r14 |
Not present |
||
|
restrictResourceReservationPeriod-r14 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
cbr-CommonTxConfigList-r14 |
SL-CBR-CommonTxConfigList-r14 (Table 24.2.4.3.3-3) |
||
|
} |
|||
|
} |
|||
Table 24.2.4.3.3-3: SL-CBR-CommonTxConfigList-r14 (Table 24.2.4.3.3-2)
|
Derivation Path: 36.331 clause 6.3.8 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SL-CBR-CommonTxConfigList-r14 :: = SEQUENCE |
|||
|
cbr-RangeCommonConfigList-r14 SEQUENCE (SIZE (1..maxSL-V2X-CBRConfig-r14)) OF SL-CBR-Levels-Config-r14 { |
1 entry |
||
|
sl-CBR-Levels-Config-r14[1] SEQUENCE (SIZE (1..maxCBR-Level-r14)) OF SL-CBR-r14 { |
3 entries |
||
|
sl-CBR-r14[1] |
20 |
INTEGER(0..100) |
|
|
sl-CBR-r14[2] |
60 |
INTEGER(0..100) |
|
|
sl-CBR-r14[3] |
100 |
INTEGER(0..100) |
|
|
} |
|||
|
} |
|||
|
sl-CBR-PSSCH-TxConfigList-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxConfig-r14)) OF SL-CBR-PSSCH-TxConfig-r14 { |
3 entries |
||
|
sl-CBR-PSSCH-TxConfig[1] |
SL-CBR-PSSCH-TxConfig-r14 with condition LOW_CBR (Table 24.2.4.3.3-4) |
||
|
sl-CBR-PSSCH-TxConfig[2] |
SL-CBR-PSSCH-TxConfig-r14 with condition MID_CBR (Table 24.2.4.3.3-4) |
||
|
sl-CBR-PSSCH-TxConfig[3] |
SL-CBR-PSSCH-TxConfig-r14 with condition HIGH_CBR (Table 24.2.4.3.3-4) |
||
|
} |
|||
|
} |
|||
Table 24.2.4.3.3-4: SL-CBR-PSSCH-TxConfig-r14 (Table 24.2.4.3.3-3)
|
Derivation Path: 36.331 clause 6.3.8 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SL-CBR-PSSCH-TxConfig-r14 ::= SEQUENCE { |
|||
|
cr-Limit-r14 |
10000 |
INTEGER(0..10000) |
|
|
tx-Parameters-r14:: = SEQUENCE{ |
|||
|
minMCS-PSSCH-r14 |
17 |
LOW_CBR |
|
|
8 |
MID_CBR |
||
|
3 |
HIGH_CBR |
||
|
maxMCS-PSSCH-r14 |
17 |
LOW_CBR |
|
|
8 |
MID_CBR |
||
|
3 |
HIGH_CBR |
||
|
minSubChannel-NumberPSSCH-r14 |
1 |
||
|
maxSubchannel-NumberPSSCH-r14 |
10 |
||
|
allowedRetxNumberPSSCH-r14 |
n0 |
||
|
maxTxPower-r14 |
Not Present |
||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
LOW_CBR |
The Tx parameters used for V2X communication in low CBR scenario. The CBR level is lower than 20% which is configured in sl-CBR-r14[1]. |
|
MID_CBR |
The Tx parameters for V2X communication in mid CBR scenario. The CBR level is from 20% to 60% which is configured in sl-CBR-r14[2] |
|
HIGH_CBR |
The Tx parameters used for V2X communication in high CBR scenario. The CBR level is higher than 60% which is configured in sl-CBR-r14[3] |
Table 24.2.4.3.3-5: SidelinkUEInformation (step 3, Table 24.2.4.3.2-1)
|
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 (1..maxFreq) |
[f5 in TS 36.508 [18] clause 6.2.3.5] |
Configured in SIB21 |
|
|
v2x-CommTxResourceReq-r14 SEQUENCE { |
|||
|
v2x-CommTxFreqList-r14 SEQUENCE (SIZE (1..maxFreqV2X-r14)) OF { INTEGER (1..maxFreq) } |
[f5 in TS 36.508 [18] clause 6.2.3.5] |
Configured in SIB21 |
|
|
v2x-TypeTxSyncList-r14 SEQUENCE (SIZE (1..maxFreqV2X-r14)) OF SEQUENCE { |
|||
|
SL-TypeTxSync-r14 |
Not checked |
||
|
} |
|||
|
v2x-DestinationInfoList-r14 SEQUENCE (SIZE (1..maxSL-Dest-r12)) OF SEQUENCE { |
Not checked. |
||
|
SL-DestinationIdentity-r12 |
Not checked |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.2.4.3.3-6: SystemInformationBlockType21 for Cell 1 (step 6, Table 24.2.4.3.2-1)
|
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 (1..maxFreq)) OF SL-InterFreqInfoV2X-r14 { |
1 entry |
||
|
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 { |
|||
|
p2x-CommTxPoolNormal-r14 SEQUENCE (SIZE (1..maxSL-V2X-TxPool-r14)) OF SL-CommResourcePoolV2X-r14 { |
1 entry |
||
|
SL-CommResourcePoolV2X-r14[1] SEQUENCE { |
|||
|
sl-OffsetIndicator-r14 |
Not present |
||
|
sl-Subframe-r14 CHOICE { |
|||
|
bs20-r14 |
11111111111111111111 |
BITMAP_6 |
|
|
} |
|||
|
adjacencyPSCCH-PSSCH-r14 |
true |
BOOLEAN |
|
|
sizeSubchannel-r14 |
n5 |
Independent to BW |
|
|
numSubchannel-r14 |
n10 |
||
|
startRB-Subchannel-r14 |
0 |
||
|
startRB-PSCCH-Pool-r14 |
Not present |
||
|
rxParametersNCell-r14 |
Not present |
||
|
dataTxParameters-r14 {} |
Not present |
||
|
dataTxParameters-r14 SEQUENCE { |
COND_TX |
||
|
alpha-r12 |
al0 |
||
|
p0-r12 |
31 |
||
|
} |
|||
|
zoneID-r14 |
Not present |
INTEGER (0..7) |
|
|
threshS-RSSI-CBR-r14 |
23 |
-66 dBm |
BW10 |
|
poolReportId-r14 |
Not present |
||
|
cbr-pssch-TxConfigList-r14 SEQUENCE (SIZE (1..8)) OF SL-PPPP-TxConfigIndex-r14{ |
1 entry |
||
|
sl-PPPP-TxConfigIndex-r14[1] SEQUENCE { |
|||
|
priorityThreshold-r14 |
8 |
||
|
defaultTxConfigIndex-r14 |
1 |
||
|
cbr-ConfigIndex-r14 |
0 |
||
|
tx-ConfigIndexList-r14 SEQUENCE (SIZE (1..maxCBR-Level-r14)) OF Tx-ConfigIndex-r14 { |
3 entries |
||
|
tx-ConfigIndex[1] |
0 |
||
|
tx-ConfigIndex[2] |
1 |
||
|
tx-ConfigIndex[3] |
2 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
resourceSelectionConfigP2X-r14 |
Not present |
||
|
syncAllowed-r14 |
Not present |
||
|
restrictResourceReservationPeriod-r14 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
cbr-CommonTxConfigList-r14 |
SL-CBR-CommonTxConfigList-r14 (Table 24.2.4.3.3-3) |
||
|
} |
|||
|
} |
|||