24.1.1 V2X Sidelink Communication / Pre-configured authorisation / UE in RRC_IDLE on an E-UTRAN cell operating on the anchor carrier frequency provisioned for V2X configuration / Utilisation of the resources of (serving) cells/PLMNs / Transmission
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.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 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 which does not include either v2x-CommTxPoolNormalCommon or v2x‑CommTxPoolNormal in v2x-InterFreqInfoList }
ensure that {
when { UE receives a request from upper layers to transmit V2X sidelink communication }
then { UE initiates an RRC connection, and, successfully completes a Sidelink UE information procedure to indicate the V2X sidelink communication transmission resources required }
}
(3)
with { UE being authorized for performing V2X sidelink Communication in PLMN1) and pre-configured with anchor carrier parameters for V2X configuration and with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_IDLE on Cell1/f1/PLMN1 which is operating on the anchor carrier frequency as the one pre-configured in the UE/USIM and is transmitting SystemInformationBlockType21 which includes v2x-CommTxPoolNormal in v2x-InterFreqInfoList }
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 using the configured resources in Cell1/f1/PLMN1 via SystemInformationBlockType21 }
}
(4)
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 transmitting SystemInformationBlockType21 }
ensure that {
when { Cell4/f1/PLMN1 which is broadcasting SystemInformationBlockType21 providing resources for V2X sidelink communication becomes the highest ranked cell, and, UE reselects to Cell4/f1/PLMN1 }
then { UE reselects to Cell4/f1/PLMN1, and transmits V2X sidelink communication using the configured resources in Cell4/f1/PLMN1) }
}
(5)
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 Cell4/f1/PLMN1 which is not transmitting SystemInformationBlockType21 }
ensure that {
when { Cell1/f1/PLMN1 which is broadcasting SystemInformationBlockType21 providing resources for V2X sidelink communication becomes the highest ranked cell and UE reselects to Cell1/f1/PLMN1 }
then { UE reselects to Cell1/f1/PLMN1 and transmits V2X sidelink communication using the configured resources in Cell1/f1/PLMN1) }
}
24.1.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.304 clause 11.4, TS 24.301 clause 5.5.1.2.2, TS 24.301 clause 5.5.3.2.2, TS 23.285 clauses 4.4.1.1.1, 4.4.1.1.2, 4.4.2, 4.5.1, 5.3, TS 36.331 clauses 5.2.2.4, 5.2.2.28, 5.10.1d, 5.10.2.2, 5.3.3.1a, 5.10.13.1.
[TS 36.304, clause 11.4]
If the UE has selected a cell on a non-serving frequency for sidelink communication or V2X sidelink communication or sidelink discovery announcement, it shall perform additional intra-frequency reselection process to select a better cell for sidelink operation on that frequency in accordance with section 11.4.1.
[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 24.301, clause 5.5.3.2.2]
If the UE has to request resources for V2X communication over PC5 (see TS 23.285 [47]), then the UE shall set the "active" flag to 1 in the TRACKING AREA UPDATE REQUEST message.
…
For all cases except case b, 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 TRACKING AREA UPDATE REQUEST message.
[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 to enable the UE to 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] and contain an indication of whether they are "operator managed" or "non-operator managed". The allowed "non-operator managed" radio resources for V2X communications are defined in TS 36.101 [24]. The UE uses the radio parameters only if the UE can locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit.
3) Policy/parameters for V2X communication over PC5 reference point:
– The mapping of Destination Layer-2 ID(s) and the V2X services, e.g. PSID or ITS-AIDs of the V2X application.
NOTE 1: PLMN operators coordinate to make sure Destination Layer-2 ID(s) for different V2X services are configured in a consistent manner.
NOTE 2: To pre-configure a UE with the provisioning parameters, at least the "not served by E-UTRAN" parameters of 1) and 2), and the parameters of 3) need to be included.
– The mapping of ProSe Per-Packet Priority and packet delay budget for V2X communication (autonomous resources selection mode).
[TS 23.285, clause 4.4.2]
PC5 reference point as defined in TS 23.303 [5] is used for the transmission and reception of V2X messages. The V2X communication over PC5 reference point supports roaming and inter-PLMN operations. V2X communication over PC5 reference point is supported when the UE is "served by E-UTRAN" and when the UE is "not served by E‑UTRAN".
A UE is authorized to transmit and receive V2X messages by the V2X Control Function in its home PLMN as described in clause 5.2.
The V2X communication over PC5 reference point is a type of ProSe Direct Communication with the following characteristics:
– The V2X communication over PC5 reference point is connectionless, and there is no signalling over PC5 control plane for connection establishment.
– V2X messages are exchanged between UEs over PC5 user plane.
– Both IP based and non-IP based V2X messages are supported.
– For IP based V2X messages, only IPv6 is used. IPv4 is not supported in this release.
The identifiers used in the V2X communication over PC5 reference point are described in clause 4.5.1.
[TS 23.285, clause 4.5.1]
Each UE has a Layer-2 ID for the V2X communication over PC5 reference point, which is included in the source Layer-2 ID field of every frame that it sends on the layer-2 link. The UE self-assigns the Layer-2 ID for the V2X communication over PC5 reference point.
When IP based V2X messages are supported, the UE auto-configures a link local IPv6 address to be used as the source IP address, as defined in clause 4.5.3 of TS 23.303 [5].
In order to ensure that a source UE (e.g. vehicle) cannot be tracked or identified by any other UEs (e.g. vehicles) beyond a certain short time-period required by the application, the source Layer-2 ID must be changed over time and randomized. For IP based V2X communication over PC5 reference point, the source IP address must be also changed over time and randomized. The change of the identifiers of a source UE must be synchronized across layers used for PC5, e.g. when application layer identifier changes, the source Layer-2 ID and the source IP address need to be changed.
The UE is configured with the destination Layer-2 ID(s) to be used for V2X services. The Layer-2 ID for a V2X message is selected based on the configuration as described in clause 4.4.1.1.
[TS 23.285, clause 5.3]
To perform V2X communication over PC5 reference point, the UE is configured with the related information as described in clause 4.4.1.1.
The procedure for one-to-many ProSe Direct Communication transmission described in clause 5.4.2 of TS 23.303 [5] is applied to V2X communication over PC5 reference point with following differences:
– The source Layer-2 ID is set to the Layer-2 ID described in clause 4.5.1.
– A UE shall be configured with a set of Layer-2 ID corresponding to different type of services.
The procedure for one-to-many ProSe Direct Communication reception described in clause 5.4.3 of TS 23.303 [5] is applied to V2X communication over PC5 reference point.
[TS 36.331, clause 5.2.2.4]
1> if the UE is capable of V2X sidelink communication and is configured by upper layers to receive or transmit V2X sidelink communication on a frequency:
2> if the cell used for V2X sidelink communication meets the S-criteria as defined in TS 36.304 [4]; and
2> if schedulingInfoList on the concerned frequency indicates that SystemInformationBlockType21 is present and the UE does not have stored a valid version of this system information block:
3> acquire SystemInformationBlockType21;
[TS 36.331, clause 5.2.2.28]
Upon receiving SystemInformationBlockType21, the UE shall:
1> if SystemInformationBlockType21 message includes sl-V2X-ConfigCommon:
2> if configured to receive V2X sidelink communication:
3> use the resource pool indicated by v2x-CommRxPool in sl-V2X-ConfigCommon for V2X sidelink communication monitoring, as specified in 5.10.12;
2> if configured to transmit V2X sidelink communication:
3> use the resource pool indicated by v2x-CommTxPoolNormalCommon or by v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.10.13;
[TS 36.331, clause 5.10.1d]
When it is specified that the UE shall perform V2X sidelink communication operation only if the conditions defined in this section are met, the UE shall perform V2X sidelink communication operation only if:
1> if the UE’s serving cell is suitable (RRC_IDLE or RRC_CONNECTED); and if either the selected cell on the frequency used for V2X sidelink communication operation belongs to the registered or equivalent PLMN as specified in TS 24.334 [69] or the UE is out of coverage on the frequency used for V2X sidelink communication operation as defined in TS 36.304 [4, 11.4]; or
1> if the UE has no serving cell (RRC_IDLE);
[TS 36.331, clause 5.10.2.2]
NOTE 1: A UE in RRC_IDLE that is configured to transmit […] V2X sidelink communication […] while […] SystemInformationBlockType21 including sl-V2X-ConfigCommon does not include the resources for transmission (in normal conditions), initiates connection establishment in accordance with clause 5.3.3.1a.
[TS 36.331, clause 5.3.3.1a]
For V2X sidelink communication an RRC connection is initiated only in the following case:
1> if configured by upper layers to transmit non-P2X related V2X sidelink communication and related data is available for transmission:
2> if SystemInformationBlockType21 is broadcast by the cell on which the UE camps; and if the valid version of SystemInformationBlockType21 includes sl-V2X-ConfigCommon; and sl-V2X-ConfigCommon does not include v2x-CommTxPoolNormalCommon;
[TS 36.331, clause 5.10.2.2]
1> if SystemInformationBlockType21 including sl-V2X-ConfigCommon is broadcast by the PCell:
2> ensure having a valid version of SystemInformationBlockType21 for the PCell;
2> if configured by upper layers to transmit V2X sidelink communication:
3> if the UE did not transmit a SidelinkUEInformation message since last entering RRC_CONNECTED state; or
4> initiate transmission of the SidelinkUEInformation message to indicate the V2X sidelink communication transmission resources required by the UE in accordance with clause 5.10.2.3;
[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 clause 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> if the UE is configured, by the current PCell with commTxResources set to scheduled:
5> if T310 or T311 is running; and if the PCell at which the UE detected physical layer problems or radio link failure broadcasts SystemInformationBlockType21 including v2x-CommTxPoolExceptional in sl-V2X-ConfigCommon, or v2x-CommTxPoolExceptional is included in v2x-InterFreqInfoList for the concerned frequency in SystemInformationBlockType21 or RRCConnectionReconfiguration; or
5> if T301 is running and the cell on which the UE initiated connection re-establishment broadcasts SystemInformationBlockType21 including v2x-CommTxPoolExceptional in sl-V2X-ConfigCommon, or v2x-CommTxPoolExceptional is included in v2x-InterFreqInfoList for the concerned frequency in SystemInformationBlockType21; or
5> if T304 is running and the UE is configured with v2x-CommTxPoolExceptional included in mobilityControlInfoV2X in RRCConnectionReconfiguration or in v2x-InterFreqInfoList for the concerned frequency in RRCConnectionReconfiguration:
6> configure lower layers to transmit the sidelink control information and the corresponding data based on random selection using the pool of resources indicated by v2x-CommTxPoolExceptional as defined in TS 36.321 [6];
5> else:
6> configure lower layers to request E-UTRAN to assign transmission resources 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> if a result of sensing on the resources configured in v2x-CommTxPoolNormalDedicated or v2x-CommTxPoolNormal in the entry of v2x-InterFreqInfoList for the concerned frequency in RRCConnectionReconfiguration is not available in accordance with TS 36.213 [23]:
6> if v2x-CommTxPoolExceptional is included in mobilityControlInfoV2X in RRCConnectionReconfiguration (i.e., handover case); or
6> if v2x-CommTxPoolExceptional is included in the entry of v2x-InterFreqInfoList for the concerned frequency in RRCConnectionReconfiguration; or
6> if the PCell broadcasts SystemInformationBlockType21 including v2x-CommTxPoolExceptional in sl-V2X-ConfigCommon:
7> configure lower layers to transmit the sidelink control information and the corresponding data based on random selection using the pool of resources indicated by v2x-CommTxPoolExceptional as defined in TS 36.321 [6];
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 clause 5.10.13.2;
[…]
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 clause 5.10.13.2;
[…]
5> else if SystemInformationBlockType21 includes v2x-CommTxPoolExceptional in sl-V2X-ConfigCommon:
6> from the moment the UE initiates connection establishment until receiving an RRCConnectionReconfiguration including sl-V2X-ConfigDedicated or sl-P2X-ConfigDedicated, until receiving an RRCConnectionRelease or an RRCConnectionReject, or until a result of sensing on the resources configured in v2x-CommTxPoolNormalCommon, if configured, becomes 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 clause 5.10.13.2, […], and in accordance with the timing of the selected reference as defined in clause 5.10.8;
24.1.1.3 Test description
24.1.1.3.1 Pre-test conditions
System Simulator:
SS-NW
– Cell 1, Cell 4 and Cell 11
Table 24.1.1.3.1-1: Cell parameters values
|
Cell |
Frequency |
PLMN |
|
1 |
f1 |
HPLMN (PLMN1) |
|
4 |
f2 |
PLMN1 |
|
11 |
f1 |
PLMN1 |
|
Note 1: The Frequencies f1 and f2 shall be the anchor frequencies pre-configured in the UE/USIM. |
||
– Cell 1 and Cell 4 are in the same TA, Cell11 (is in a different TA).
– System information combination 29 as defined in TS 36.508 [18] clause 4.4.3.1 is used in all active cells.
SS-UE
– SS-UE1. As defined in TS 36.508 [18], configured for and operating as V2X Sidelink Communication 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.1.3.1-2.
Table 24.1.1.3.1-2: 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.1.3.3-4 |
Preamble:
– The UE is in State Switched OFF (state 1) according to TS 36.508 [18].
24.1.1.3.2 Test procedure sequence
Table 24.1.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" … "Tn" are to be applied subsequently. The exact instants on which these values shall be applied are described elsewhere in the present clause.
Table 24.1.1.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 4 |
Cell 11 |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15 kHz |
-85 |
"Off" |
"Off" |
|
T1 |
Cell-specific RS EPRE |
dBm/15 kHz |
-85 |
-79 |
"Off" |
|
T2 |
Cell-specific RS EPRE |
dBm/15 kHz |
-85 |
"Off" |
-79 |
Table 24.1.1.3.2-2: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS configures: SS-NW – Cell 1 transmits SystemInformationBlockType21 neither including v2x-CommTxPoolNormalCommon nor v2x-CommTxPoolNormal in v2x-InterFreqInfoList (i.e. V2X sidelink communication supported by the network, no common resources provided yet). |
– |
– |
– |
– |
|
2 |
The UE is switched on. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1. |
– |
– |
– |
– |
|
3 |
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 |
|
4 |
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 |
– |
– |
|
5 |
The UE responds with CLOSE UE TEST LOOP COMPLETE. |
–> |
CLOSE UE TEST LOOP COMPLETE |
– |
– |
|
6 |
SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
7 |
Check: Does the UE transmit an RRCConnectionRequest message? |
–> |
RRCConnectionRequest |
2 |
P |
|
8 |
SS-NW transmits an RRCConnectionSetup message. |
<– |
RRCConnectionSetup |
– |
– |
|
9 |
Check: Does the UE transmit an RRCConnectionSetupComplete message? |
–> |
RRCConnectionSetupComplete |
2 |
P |
|
10 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of V2X sidelink communication? |
–> |
SidelinkUEInformation |
2 |
P |
|
11 |
SS-NW releases the connection. |
<– |
RRCConnectionRelease |
– |
– |
|
12 |
SS-NW changes SystemInformationBlockType21 to include v2x-CommTxPoolNormal in v2x-InterFreqInfoList. |
– |
– |
– |
– |
|
12A |
The SS transmits a Paging message in a paging occasion including a systemInfoModification. |
<– |
Paging |
– |
– |
|
13 |
Wait for 2 modification periods to allow for the UE to obtain the new version of the SystemInformationType21. |
– |
– |
– |
– |
|
14 |
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 |
|
15 |
The SS configures: SS-NW Cell 1 and Cell 4 parameters according to the row "T1" in table 24.1.1.3.2-1 in order to simulate the need for cell reselection to Cell 4. Cell 4 broadcasts SystemInformationBlockType21 including v2x-CommTxPoolNormal in v2x-InterFreqInfoList. |
– |
– |
– |
– |
|
16 |
Wait for 5 sec to allow the UE to adjust to cell changes and start transmission. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 4. |
– |
– |
– |
– |
|
17 |
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 the broadcast on Cell 4 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 |
4 |
P |
|
17A |
The SS configures: SS-NW Cell 4 does not broadcast SystemInformationBlockType21 |
||||
|
17B |
The SS transmits a Paging message in a paging occasion including a systemInfoModification. |
<– |
Paging |
– |
– |
|
17C |
Wait for 1.1 modification periods to allow the UE to adjust to cell changes. |
||||
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1. |
– |
– |
– |
– |
|
17D |
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 the broadcast on 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 |
5 |
P |
|
17E |
The SS configures: SS-NW Cell1, Cell 4 and Cell 11 parameters according to the row "T2" in table 24.1.1.3.2-1 in order to simulate cell reselection to Cell 11. Cell 11 broadcasts SystemInformationBlockType21 providing different resources for V2X sidelink communication transmission than those provided on Cell 1. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 11. |
– |
– |
– |
– |
|
17F |
Check: Does the Generic test procedure for ‘Tracking area updating procedure’ defined in TS 36.508 [18] clause 4.5A.2 take place during which the UE announces its V2X sidelink communication capabilities in the TRACKING AREA UPDATE REQUEST message? |
– |
– |
1 |
P |
|
17G |
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 the broadcast on Cell 11 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 |
– |
– |
|
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.1.3.3 Specific message contents
Table 24.1.1.3.3-1: SystemInformationBlockType21 for Cell 1 (step 1, Table 24.1.1.3.2-2)
|
Derivation Path: 36.508 [18], table 4.4.3.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType21-r14 ::= SEQUENCE { |
|||
|
sl-V2X-ConfigCommon-r14 SEQUENCE { |
|||
|
v2x-InterFreqInfoList-r14 SEQUENCE { |
|||
|
SL-InterFreqInfoV2X-r14[1] SEQUENCE { |
|||
|
v2x-CommCarrierFreq-r14 |
f5 in TS 36.508 [18] clause 6.2.3.5 |
||
|
v2x-UE-ConfigList-r14 SEQUENCE (SIZE (1.. maxCellIntra)) OF SL-V2X-InterFreqUE-Config-r14 { |
1 entry |
||
|
SL-V2X-InterFreqUE-Config-r14[1] SEQUENCE { |
|||
|
v2x-CommTxPoolNormal-r14 |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Note: V2X SideLink communication supported but no resources set for transmission. |
|||
Table 24.1.1.3.3-2: SystemInformationBlockType21 for Cell 1 (step 12 onwards, Table 24.1.1.3.2-2)
|
Derivation Path: 36.508 [18], table 4.4.3.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType21-r14 ::= SEQUENCE { |
|||
|
sl-V2X-ConfigCommon-r14 SEQUENCE { |
|||
|
v2x-InterFreqInfoList-r14 SEQUENCE { |
|||
|
SL-InterFreqInfoV2X-r14[1] SEQUENCE { |
|||
|
v2x-CommCarrierFreq-r14 |
f5 in TS 36.508 [18] clause 6.2.3.5 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
NOTE: V2X SideLink communication supported; resources for transmission in RRC_IDLE provided (SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_1 and COND_TX) v2x-CommTxPoolNormal in v2x-InterFreqInfoList. |
|||
Table 24.1.1.3.3-3: SystemInformationBlockType21 for Cell 4 and Cell 11 (step 15 onwards, Table 24.1.1.3.2-2)
|
Derivation Path: 36.508 [18], table 4.4.3.3-19 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType21-r14 ::= SEQUENCE { |
|||
|
sl-V2X-ConfigCommon-r14 SEQUENCE { |
|||
|
v2x-InterFreqInfoList-r14 SEQUENCE { |
|||
|
SL-InterFreqInfoV2X-r14[1] SEQUENCE { |
|||
|
v2x-CommCarrierFreq-r14 |
f5 in TS 36.508 [18] clause 6.2.3.5 |
||
|
v2x-UE-ConfigList-r14 SEQUENCE { |
|||
|
v2x-CommTxPoolNormal-r14[1] SEQUENCE { |
|||
|
SL-CommResourcePoolV2X-r14[1] |
SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_2 and COND_TX |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
NOTE: V2X SideLink communication supported; resources for transmission in RRC_IDLE provided (SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_2 and COND_TX) v2x-CommTxPoolNormal in v2x-InterFreqInfoList. |
|||
Table 24.1.1.3.3-4: SidelinkUEInformation (step 10, Table 24.1.1.3.2-2)
|
Derivation Path: 36.508 [18], table 4.6.1-21B |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SidelinkUEInformation-r12 ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
sidelinkUEInformation-r12 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
v2x-CommRxInterestedFreqList-r14 SEQUENCE (SIZE (1..maxFreqV2X-r14)) OF INTEGER (1..maxFreq) |
[f5 in TS 36.508 [18] clause 6.2.3.5] |
Configured in SIB21 |
|
|
v2x-CommTxResourceReq-r14 SEQUENCE { |
|||
|
carrierFreqCommTx-r14 |
[f5 in TS 36.508 [18] clause 6.2.3.5] |
Configured in SIB21 |
|
|
v2x-TypeTxSync-r14 |
Not checked |
||
|
v2x-DestinationInfoList-r14 SEQUENCE (SIZE (1..maxSL-Dest-r12)) OF SEQUENCE { |
Not checked. |
||
|
SL-DestinationIdentity-r12 |
Not checked |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.1.1.3.3-5: SL-V2X-Preconfiguration
|
Derivation Path: 36.508 [18], table 6.8.2.1-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SL-V2X-Preconfiguration-r14 ::= SEQUENCE { |
|||
|
anchorCarrierFreqList-r14 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
1 entry |
||
|
ARFCN-ValueEUTRA-r9[1] |
f1 in TS 36.508 [18] clause 6.2.3.1 |
||
|
} |
|||
|
} |
|||
Table 24.1.1.3.3-7: TRACKING AREA UPDATE REQUEST (step 17F, Table 24.1.1.3.2-2; step 4 TS 36.508 [18] Table 4.5A.2.1-1)
|
Derivation path: 36.508 [18] table 4.7.2-27 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
EPS update type |
|||
|
"Active" flag |
‘1’B |
||
|
UE network capability |
|||
|
V2X communication over PC5 (V2X PC5) (octet 9, bit 2) |
‘1’ |
V2X communication over PC5 supported |
|