24.1.5 V2X Sidelink Communication / Pre-configured authorisation / UE in RRC_CONNECTED on an E-UTRAN cell operating on the anchor carrier frequency provisioned for V2X configuration / Utilisation of the resources of (serving) cells/PLMNs / Transmission / RRC connection re-establishment
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.5.1 Test Purpose (TP)
(1)
with { UE being authorized for performing V2X sidelink Communication in PLMN1 and pre-configured with anchor carrier parameters for V2X configuration and being provisioned with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_CONNECTED 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 indicating no provision of resources for V2X sidelink communication }
ensure that {
when { UE receives a request from upper layers to transmit V2X sidelink communication }
then { UE successfully completes a Sidelink UE information procedure to indicate the V2X sidelink communication transmission resources required, and, UE is able to transmit V2X sidelink communication using the configured resources in Cell1/f1/PLMN1 (V2X-commTxResources set to setup and resources provided in V2X-commTxPoolNormalDedicated) }
}
(2)
with { UE being authorized for performing V2X sidelink Communication in PLMN1 and pre-configured with anchor carrier parameters for V2X configuration and being provisioned with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_CONNECTED 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 indicating no provision of resources for V2X sidelink communication, and, UE having successfully completed Sidelink UE information procedure to indicate the V2X sidelink communication transmission resources required and transmitting V2X sidelink communication using the configured resources in Cell1/f1/PLMN1 (commTxResources set to setup and resources provided in commTxPoolNormalDedicated ) }
ensure that {
when { UE receives RRCConnectionReconfiguration message with V2X-commTxResources set to release }
then { UE releases the resources allocated for V2X sidelink communication transmission previously configured by commTxResources in Cell1/f1/PLMN1, and, UE re-starts transmission of V2X sidelink communication when resources become available (commTxResources set to setup, scheduled and resources provided in v2x-commTxPoolNormalDedicated }
}
(3)
with { UE being authorized for performing V2X sidelink Communication in PLMN1 and pre-configured with anchor carrier parameters for V2X configuration and being provisioned with Radio parameters for when the UE is "not served by E-UTRAN", and, UE is in RRC_CONNECTED 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 indicating no provision of resources for V2X sidelink communication, and, UE having successfully completed Sidelink UE information procedure requesting V2X sidelink communication transmission resources and transmitting V2X sidelink communication }
ensure that {
when { UE detects radio link failure >1 sec after the UE transmitted the SidelinkUEInformation message, and, T301 is running and the cell on which the UE initiated connection re-establishment (Cell2/f1/PLMN1) broadcasts SystemInformationBlockType21 including v2x-commTxPoolExceptional }
then { UE is able to transmit V2X sidelink communication using the resources configured by v2x-CommTxPoolExceptional on Cell2/f1/PLMN1, and, after the T301 expires UE initiates a Sidelink UE information procedure requesting V2X sidelink communication transmission resources, and, UE is able to transmit V2X sidelink communication using the configured resources in Cell2/f1/PLMN1 (commTxResources set to setup, scheduled and resources provided in v2x-commTxPoolNormalDedicated) }
}
24.1.5.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 23.285, clauses 4.4.1.1.1, 4.4.1.1.2, 4.4.2, 4.5.1, 5.3, TS 36.331, clauses 5.2.2.4, 5.2.2.28, 5.3.5.3, 5.3.5.4, 5.3.7.5, 5.3.10.15a, 5.10.1d and 5.10.13.1.
[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.3.5.3]
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
…
1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated:
2> perform the V2X sidelink communication dedicated configuration procedure as specified in 5.3.10.15a;
…
[TS 36.331, clause 5.3.5.4]
If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:
…
1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated or mobilityControlInfoV2X:
2> perform the V2X sidelink communication dedicated configuration procedure as specified in 5.3.10.15a;
…
[TS 36.331, clause 5.3.7.5]
The UE shall:
…
1> if SystemInformationBlockType21 including sl-V2X-ConfigCommon is broadcast by the PCell; and the UE transmitted a SidelinkUEInformation message indicating a change of V2X sidelink communication related parameters relevant in PCell (i.e. change of v2x-CommRxInterestedFreq or v2x-CommTxResourceReq) during the last 1 second preceding detection of radio link failure:
2> initiate transmission of the SidelinkUEInformation message in accordance with 5.10.2.3;
…
[TS 36.331, clause 5.3.10.15a]
The UE shall:
1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated or sl-P2X-ConfigDedicated:
2> if commTxResources is included and set to setup:
3> use the resources indicated by commTxResources for V2X sidelink communication transmission, as specified in 5.10.13;
3> perform CBR measurement on the transmission resource pool indicated in sl-V2X-ConfigDedicated for V2X sidelink communication transmission, as specified in 5.5.3;
2> else if commTxResources is included and set to release:
3> release the resources allocated for V2X sidelink communication transmission previously configured by commTxResources;
2> if v2x-InterFreqInfoList is included:
3> use the synchronization configuration and resource configuration parameters for V2X sidelink communication on frequencies included in v2x-InterFreqInfoList;
1> if the RRCConnectionReconfiguration message includes the mobilityControlInfoV2X:
2> if v2x-CommRxPool is included:
3> use the resources indicated by v2x-CommRxPool for V2X sidelink communication reception, as specified in 5.10.12;
2> if v2x-CommTxPoolExceptional is included:
3> use the resources indicated 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’s serving cell (for RRC_IDLE or RRC_CONNECTED) fulfils the conditions to support V2X sidelink communication in limited service state as specified in TS 23.285 [78, 4.4.8]; and if either the serving cell is on the frequency used for V2X sidelink communication operation or the UE is out of coverage on the frequency used for V2X sidelink communication operation as defined in TS 36.304 [4, 11.4]; or
1> if the UE has no serving cell (RRC_IDLE);
[TS 36.331, clause 5.10.13.1]
A UE capable of V2X sidelink communication that is configured by upper layers to transmit V2X sidelink communication and has related data to be transmitted shall:
1> if the conditions for sidelink operation as defined in 5.10.1d are met:
2> if in coverage on the frequency used for V2X sidelink communication as defined in TS 36.304 [4, 11.4]; or
2> if the frequency used to transmit V2X sidelink communication is included in v2x-InterFreqInfoList in RRCConnectionReconfiguration or in v2x-InterFreqInfoList within SystemInformationBlockType21:
3> if the UE is in RRC_CONNECTED and uses the PCell or the frequency included in v2x-InterFreqInfoList in RRCConnectionReconfiguration for V2X sidelink communication:
4> 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 5.10.13.2;
4> else if the UE is configured with v2x-commTxPoolNormalDedicated in sl-P2X-ConfigDedicated or p2x-CommTxPoolNormal in v2x-InterFreqInfoList in RRCConnectionReconfiguration and the UE is configured to transmit P2X related V2X sidelink communication:
5> select a resource pool according to 5.10.13.2;
5> transmit P2X related V2X sidelink communication according to 5.10.13.1a;
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> 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 by 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:
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 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, or v2x-commTxPoolNormalDedicated in sl-V2X-ConfigDedicated, 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 in normal or exceptional cases.
24.1.5.3 Test description
24.1.5.3.1 Pre-test conditions
System Simulator:
SS-NW
– Cell 1
Table 24.1.5.3.1-1: Cell parameters values
|
Cell |
Frequency |
PLMN |
|
1 |
f1 |
HPLMN (PLMN1) |
|
2 |
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 Cell 1 and Cell 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:
– 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.5.3.1-1.
Table 24.1.5.3.1-1: UE/ USIM configuration
|
USIM field |
Priority |
Value |
Access Technology Identifier |
|
EFUST |
Service n°119 (V2X) supported |
||
|
EFVST |
As per TS 36.508 [18] clause 4.9.3.4 |
||
|
EFV2X_CONFIG |
SL-V2X-Preconfiguration field as defined in Table 24.1.5.3.3-1 |
Preamble:
– The UE is in Generic Radio Bearer Establishment, UE Test Mode Activated (State 3A) on Cell 1 according to TS 36.508 [18].
24.1.5.3.2 Test procedure sequence
Table 24.1.5.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.5.3.2-1: Time instances of cell power level and parameter changes
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
|
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-79 |
-85 |
|
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
“Off” |
-85 |
Table 24.1.5.3.2-2: 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 |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 1. |
– |
– |
– |
– |
|
3 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of V2X sidelink communication in RRC_CONNECTED in the next 5 sec? |
–> |
SidelinkUEInformation |
1 |
P |
|
4 |
SS-NW transmits an RRCConnectionReconfiguration message assigning V2X sidelink communication transmission resources for RRC_CONNECTED (commTxResources set to setup, scheduled and resources provided in InterFreqInfoList). |
<– |
RRCConnectionReconfiguration |
– |
– |
|
5 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
6 |
Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of sidelink communication data over the PC5 interface in accordance with the resources indicated in the RRCConnectionReconfiguration? NOTE 1: The UE may send multiple packets. The reception of one of them is sufficient for achieving the Pass verdict. NOTE 2: The structure of the data is not checked and it is just considered as octetstrings by the SS. |
–> |
STCH PDCP SDU packet |
1 |
P |
|
7 |
SS-NW transmits an RRCConnectionReconfiguration message requesting the UE to release the resources allocated for V2X sidelink communication transmission in RRC_CONNECTED (commTxResources set to release). |
<– |
RRCConnectionReconfiguration |
– |
– |
|
8 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
9 |
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 |
|
10 |
SS-NW transmits an RRCConnectionReconfiguration message providing new resources for sidelink communication transmission in RRC_CONNECTED (commTxResources set to setup, scheduled and resources provided in InterFreqInfoList; |
<– |
RRCConnectionReconfiguration |
– |
– |
|
11 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
12 |
Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of V2X sidelink communication data over the PC5 interface accordance with the resources indicated in the RRCConnectionReconfiguration message? 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 |
|
13 |
The SS configures: SS-NW Cell 1 and Cell 2 parameters according to the row "T1" in table 24.1.5.3.2-1 in order to simulate radio link failure. |
– |
– |
– |
– |
|
– |
EXCEPTION: The following events unless otherwise stated are to be observed in Cell 2. |
– |
– |
– |
– |
|
14 |
UE sends RRCConnectionReestablishmentRequest message. |
–> |
RRCConnectionReestablishmentRequest |
||
|
15 |
Wait for time=(T301)/2 |
– |
– |
– |
– |
|
16 |
Check: Does the UE transmit during the re-establishment procedure one STCH PDCP SDU packet of V2X sidelink communication data over the PC5 interface in accordance with the resources indicated in v2x-CommTxPoolExceptional broadcasted on Cell 2 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 |
|
17 |
The SS-NW transmits RRCConnectionReestablishment message. |
<– |
RRCConnectionReestablishment |
– |
– |
|
18 |
The UE transmits RRCConnectionReestablishmentComplete message. |
–> |
RRCConnectionReestablishmentComplete |
– |
– |
|
19 |
Check: Does the UE transmit a SidelinkUEInformation message requesting resources for transmission of sidelink communication in the next 1 sec? |
–> |
SidelinkUEInformation |
3 |
P |
|
20 |
SS-NW transmits an RRCConnectionReconfiguration message assigning sidelink communication transmission scheduled resources (commTxResources set scheduled). |
<– |
RRCConnectionReconfiguration |
– |
– |
|
21 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
22 |
Check: Does the UE transmit in the next 60 sec one STCH PDCP SDU packet of sidelink communication data over the PC5 interface in accordance with the resources indicated in the RRCConnectionReconfiguration? 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 |
|
23 |
The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode. |
<– |
OPEN UE TEST LOOP |
– |
– |
|
24 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
25 |
The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure. |
<– |
DEACTIVATE TEST MODE |
– |
– |
|
26 |
The UE transmits a DEACTIVATE TEST MODE COMPLETE message. |
–> |
DEACTIVATE TEST MODE COMPLETE |
– |
– |
24.1.5.3.3 Specific message contents
Table 24.1.5.3.3-1: SL-V2X-Preconfiguration
|
Derivation Path: 36.508 [18], table 6.8.2.1-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SL-V2X-Preconfiguration-r14 ::= SEQUENCE { |
|||
|
anchorCarrierFreqList-r14 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
1 entry |
||
|
ARFCN-ValueEUTRA-r9[1] |
f1 in TS 36.508 [18] clause 6.2.3.1 |
||
|
} |
|||
|
} |
|||
Table 24.1.5.3.3-2: SystemInformationBlockType21 for Cell 1 (when active, Table 24.1.5.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.5.3.3-3: SystemInformationBlockType21 for Cell 2 (when active, Table 24.1.5.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-CommTxPoolExceptional-r14 |
SL-CommResourcePoolV2X-r14-DEFAULT using conditions BITMAP_2 and COND_TX |
||
|
v2x-InterFreqInfoList-r14 SEQUENCE { |
|||
|
SL-InterFreqInfoV2X-r14[1] SEQUENCE { |
|||
|
v2x-CommCarrierFreq-r14 |
f5 in TS 36.508 [18] clause 6.2.3.5 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.1.5.3.3-4: SidelinkUEInformation (V2X) (steps 3 and 19, Table 24.1.5.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-CommTxResourceReq-r14 SEQUENCE (SIZE (1..maxFreqV2X-r14)) OF SEQUENCE { |
|||
|
carrierFreqCommTx-r14 |
f5 in TS 36.508 [18] clause 6.2.3.5 |
Configured in SIB21 |
|
|
v2x-TypeTxSync-r14 |
Not checked. |
Not checked. |
|
|
} |
|||
|
v2x-DestinationInfoList-r14 SEQUENCE (SIZE (1..maxSL-Dest-r12)) OF SEQUENCE { |
Not checked. |
Not checked. |
|
|
SL-DestinationIdentity-r12 |
Not checked |
Not checked |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.1.5.3.3-5: RRCConnectionReconfiguration (V2X) (steps 4, 10 and 20, Table 24.1.5.3.2-2)
|
Derivation Path: 36.508 [18], table 4.6.1-8B condition SETUP AND SCHEDULED |
Table 24.1.5.3.3-6: RRCConnectionReconfiguration (V2X) (step 7, Table 24.1.5.3.2-2)
|
Derivation Path: 36.508 [18], table 4.6.1-8B condition RELEASE |
Table 24.1.5.3.3-7: RRCConnectionReestablishmentRequest (step 14, Table 24.1.5.3.2-2)
|
Derivation Path: 36.508 [18], table 4.6.1-13 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReestablishmentRequest ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcConnectionReestablishmentRequest-r8 SEQUENCE { |
|||
|
ue-Identity SEQUENCE { |
|||
|
c-RNTI |
the value of the C-RNTI of the UE |
||
|
physCellId |
PhysicalCellIdentity of Cell 1 |
||
|
shortMAC-I |
The same value as the 16 least significant bits of the XMAC-I value calculated by SS |
||
|
} |
|||
|
reestablishmentCause |
otherFailure |
||
|
} |
|||
|
} |
|||
|
} |
|||