24.1.10 V2X Sidelink Communication / Pre-configured authorisation / UE in RRC_CONNECTED on an E-UTRAN cell operating on the anchor carrier frequency for V2X configuration/ UE is scheduled to transmit V2X messages on the frequency used for V2X sidelink communication / Inter-frequency scheduled 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.10.1 Test Purpose (TP)
(1)
with { UE being authorized for performing V2X sidelink Communication in PLMN1 and pre-configured with anchor carrier parameters for V2X configuration and with Radio parameters for when the UE is "not served by E-UTRAN" and UE is in RRC_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 which does not include neither v2x-CommTxPoolNormalCommon nor v2x-CommTxPoolNormal in v2x-InterFreqInfoList }
ensure that {
when { UE successfully completes a Sidelink UE information procedure to indicate the V2X sidelink communication transmission resources required as a request from upper layers to transmit V2X sidelink communication and UE receives RRCConnectionReconfiguration message which indicates the configuration for the case E-UTRAN schedules the transmission resources based on sidelink specific BSR }
then { UE transmits Sidelink BSR to request resources for the V2X sidelink communication transmission}
}
(2)
with { UE being authorised 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_CONNECTED on Cell1/f1/PLMN1 which is operating on the anchor carrier frequency as the one pre-configured in the UE/USIM and UE having successfully completed Sidelink UE information procedure}
ensure that {
when { UE receives a Sidelink grant on PDCCH which indicates the scheduled resources for V2X sidelink communication }
then { UE transmits V2X sidelink communication using the resources scheduled by E-UTRAN.}
}
(3)
with { UE being authorised 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_CONNECTED on Cell1/f1/PLMN1 which is operating on the anchor carrier frequency as the one pre-configured in the UE/USIM,and the latest transmission of the SidelinkUEInformation including v2x-CommTxResourceReq }
ensure that {
when { UE stops to transmit V2X sidelink communication }
then { UE transmits a SidelinkUEInformation message to indicate it no longer requires V2X sidelink communication transmission resources.}
}
24.1.10.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.2.2.4, 5.2.2.28, 5.3.5.3, 5.3.10.15a, 5.10.1d, 5.10.2.2, 5.10.13.1, and TS 36.321, clause 5.14.1.4 and 6.1.3.1a. Unless otherwise stated these are Rel-14 requirements.
[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.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;
[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.2.2]
A UE capable of sidelink communication or V2X sidelink communication or sidelink discovery that is in RRC_CONNECTED may initiate the procedure to indicate it is (interested in) receiving sidelink communication or V2X sidelink communication or sidelink discovery in several cases including upon successful connection establishment, upon change of interest, upon change to a PCell broadcasting SystemInformationBlockType18 or SystemInformationBlockType19 or SystemInformationBlockType21 including sl-V2X-ConfigCommon. A UE capable of sidelink communication or V2X sidelink communication or sidelink discovery may initiate the procedure to request assignment of dedicated resources for the concerned sidelink communication transmission or discovery announcements or V2X sidelink communication transmission or to request sidelink discovery gaps for sidelink discovery transmission or sidelink discovery reception and a UE capable of inter-frequency/PLMN sidelink discovery parameter reporting may initiate the procedure to report parameters related to sidelink discovery from system information of inter-frequency/PLMN cells.
[…]
Upon initiating the procedure, the UE shall:
[…]
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
3> if since the last time the UE transmitted a SidelinkUEInformation message the UE connected to a PCell not broadcasting SystemInformationBlockType21 including sl-V2X-ConfigCommon; or
3> if the last transmission of the SidelinkUEInformation message did not include v2x-CommTxResourceReq; or if the information carried by the v2x-CommTxResourceReq has changed since the last transmission of the SidelinkUEInformation message:
4> initiate transmission of the SidelinkUEInformation message to indicate the V2X sidelink communication transmission resources required by the UE in accordance with 5.10.2.3;
2> else:
3> if the last transmission of the SidelinkUEInformation message included v2x-CommTxResourceReq:
4> initiate transmission of the SidelinkUEInformation message to indicate it no longer requires V2X sidelink communication transmission resources in accordance with 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 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;
…
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.
[TS 36.321, clause 5.14.1.4]
The sidelink Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of sidelink data available for transmission in the SL buffers associated with the MAC entity. RRC controls BSR reporting for the sidelink by configuring the two timers’ periodic-BSR-TimerSL and retx-BSR-TimerSL. Each sidelink logical channel belongs to a ProSe Destination. Each sidelink logical channel is allocated to an LCG depending on the priority of the sidelink logical channel and the mapping between LCG ID and priority which is provided by upper layers in logicalChGroupInfoList [8]. LCG is defined per ProSe Destination.
A sidelink Buffer Status Report (BSR) shall be triggered if any of the following events occur:
– if the MAC entity has a configured SL-RNTI or a configured SL-V-RNTI:
– SL data, for a sidelink logical channel of a ProSe Destination, becomes available for transmission in the RLC entity or in the PDCP entity (the definition of what data shall be considered as available for transmission is specified in [3] and [4] respectively) and either the data belongs to a sidelink logical channel with higher priority than the priorities of the sidelink logical channels which belong to any LCG belonging to the same ProSe Destination and for which data is already available for transmission, or there is currently no data available for transmission for any of the sidelink logical channels belonging to the same ProSe Destination, in which case the Sidelink BSR is referred below to as "Regular Sidelink BSR";
– UL resources are allocated and number of padding bits remaining after a Padding BSR has been triggered is equal to or larger than the size of the Sidelink BSR MAC control element containing the buffer status for at least one LCG of a ProSe Destination plus its subheader, in which case the Sidelink BSR is referred below to as "Padding Sidelink BSR";
– retx-BSR-TimerSL expires and the MAC entity has data available for transmission for any of the sidelink logical channels, in which case the Sidelink BSR is referred below to as "Regular Sidelink BSR";
– periodic-BSR-TimerSL expires, in which case the Sidelink BSR is referred below to as "Periodic Sidelink BSR";
– else:
– An SL-RNTI or an SL-V-RNTI is configured by upper layers and SL data is available for transmission in the RLC entity or in the PDCP entity (the definition of what data shall be considered as available for transmission is specified in [3] and [4] respectively), in which case the Sidelink BSR is referred below to as "Regular Sidelink BSR".
For Regular and Periodic Sidelink BSR:
– if the number of bits in the UL grant is equal to or larger than the size of a Sidelink BSR containing buffer status for all LCGs having data available for transmission plus its subheader:
– report Sidelink BSR containing buffer status for all LCGs having data available for transmission;
– else report Truncated Sidelink BSR containing buffer status for as many LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration.
For Padding Sidelink BSR:
– if the number of padding bits remaining after a Padding BSR has been triggered is equal to or larger than the size of a Sidelink BSR containing buffer status for all LCGs having data available for transmission plus its subheader:
– report Sidelink BSR containing buffer status for all LCGs having data available for transmission;
– else report Truncated Sidelink BSR containing buffer status for as many LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration.
If the Buffer Status reporting procedure determines that at least one Sidelink BSR has been triggered and not cancelled:
– if the MAC entity has UL resources allocated for new transmission for this TTI and the allocated UL resources can accommodate a Sidelink BSR MAC control element plus its subheader as a result of logical channel prioritization:
– instruct the Multiplexing and Assembly procedure to generate the Sidelink BSR MAC control element(s);
– start or restart periodic-BSR-TimerSL except when all the generated Sidelink BSRs are Truncated Sidelink BSRs;
– start or restart retx-BSR-TimerSL;
– else if a Regular Sidelink BSR has been triggered:
– if an uplink grant is not configured:
– a Scheduling Request shall be triggered.
A MAC PDU shall contain at most one Sidelink BSR MAC control element, even when multiple events trigger a Sidelink BSR by the time a Sidelink BSR can be transmitted in which case the Regular Sidelink BSR and the Periodic Sidelink BSR shall have precedence over the padding Sidelink BSR.
The MAC entity shall restart retx-BSR-TimerSL upon reception of an SL grant.
All triggered regular Sidelink BSRs shall be cancelled in case the remaining configured SL grant(s) valid for this SC Period can accommodate all pending data available for transmission in sidelink communication or in case the remaining configured SL grant(s) valid can accommodate all pending data available for transmission in V2X sidelink communication. All triggered Sidelink BSRs shall be cancelled in case the MAC entity has no data available for transmission for any of the sidelink logical channels. All triggered Sidelink BSRs shall be cancelled when a Sidelink BSR (except for Truncated Sidelink BSR) is included in a MAC PDU for transmission. All triggered Sidelink BSRs shall be cancelled, and retx-BSR-TimerSL and periodic-BSR-TimerSL shall be stopped, when upper layers configure autonomous resource selection.
The MAC entity shall transmit at most one Regular/Periodic Sidelink BSR in a TTI. If the MAC entity is requested to transmit multiple MAC PDUs in a TTI, it may include a padding Sidelink BSR in any of the MAC PDUs which do not contain a Regular/Periodic Sidelink BSR.
All Sidelink BSRs transmitted in a TTI always reflect the buffer status after all MAC PDUs have been built for this TTI. Each LCG shall report at the most one buffer status value per TTI and this value shall be reported in all Sidelink BSRs reporting buffer status for this LCG.
NOTE: A Padding Sidelink BSR is not allowed to cancel a triggered Regular/Periodic Sidelink BSR. A Padding Sidelink BSR is triggered for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built.
[TS 36.321, clause 6.1.3.1a]
Sidelink BSR and Truncated Sidelink BSR MAC control elements consist of one Destination Index field, one LCG ID field and one corresponding Buffer Size field per reported target group.
The Sidelink BSR MAC control elements are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1-2. They have variable sizes.
For each included group, the fields are defined as follows (figures 6.1.3.1a-1 and 6.1.3.1a-2):
– Destination Index: The Destination Index field identifies the ProSe Destination or the destination for V2X sidelink communication. The length of this field is 4 bits. The value is set to the index of the destination reported in destinationInfoList or v2x-DestinationInfoList and if multiple such lists are reported, the value is indexed sequentially across all the lists in the same order as specified in [8];
– LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits;
– Buffer Size: The Buffer Size field identifies the total amount of data available across all logical channels of a LCG of a ProSe Destination after all MAC PDUs for the TTI have been built. The amount of data is indicated in number of bytes. It shall include all data that is available for transmission in the RLC layer and in the PDCP layer; the definition of what data shall be considered as available for transmission is specified in [3] and [4] respectively. The size of the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 6 bits. The values taken by the Buffer Size field are shown in Table 6.1.3.1-1.
24.1.10.3 Test description
24.1.10.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 all active cells.
– SystemInformationBlockType21 for Cell 1 using parameters as specified in Table 24.1.10.3.3-1.
SS-UE
– SS-UE1. As defined in TS 36.508 [18], configured for and operating as V2X Sidelink Communication receiving device on the resources which the UE is expected to use for transmission, as defined in TS 36.508 [18] clause 6.2.3.5.
UE:
– V2X sidelink related configuration
– The UE is authorised to perform V2X Sidelink Communication.
– The UE is equipped with below information in UE or in a USIM containing default values (as per TS 36.508) except for those listed in Table 24.1.10.3.1-1.
Table 24.1.10.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.10.3.3-3. |
Preamble:
– The UE is in State Generic Radio Bearer Establishment, UE Test Mode Activated (State 3A) on Cell 1 according to TS 36.508 [18].
24.1.10.3.2 Test procedure sequence
Table 24.1.10.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Close UE Test Loop with bit E0 in UE test loop mode E LB setup IE set to one (transmission mode). |
<– |
CLOSE UE TEST LOOP |
||
|
2 |
The UE responds with CLOSE UE TEST LOOP COMPLETE. |
–> |
CLOSE UE TEST LOOP COMPLETE |
||
|
3 |
UE transmit a SidelinkUEInformation message requesting resources for transmission of V2X sidelink communication in RRC_CONNECTED |
–> |
SidelinkUEInformation |
||
|
4 |
SS-NW transmits an RRCConnectionReconfiguration message to Indicate -UE performs V2X sidelink transmission with scheduled mode. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
5 |
The UE submits RRCConnectionReconfigurationComplete message to confirm acceptance of the new configuration. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
6 |
Check: Does the UE transmit Sidelink BSR with – LCID=’10111’ – MAC subheader (E=’0’, F=’0′) – Destination index set to the index of the destination reported in ‘v2x-DestinationInfoList’ of SidelinkUEInformation in step 3 – LCG ID set to any value – Buffer Size set to 46 bytes? |
–> |
MAC PDU (Sidelink BSR) |
1 |
P |
|
7 |
The SS is configured for sidelink Grant allowing the UE to get the scheduled resources for V2X sidelink communication. |
<– |
PDCCH [for sidelink grant] |
– |
– |
|
8 |
Check: Does the UE transmit one STCH PDCP SDU packet of V2X sidelink communication data over the PC5 interface in accordance with the resources scheduled by E-UTRAN? |
–> |
STCH PDCP SDU packet |
2 |
P |
|
9 |
The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode. |
<– |
OPEN UE TEST LOOP |
– |
– |
|
10 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
OPEN UE TEST LOOP COMPLETE |
– |
– |
|
10a |
UE transmits a SidelinkUEInformation message to indicate no more V2X sidelink transmission. |
–> |
SidelinkUEInformation |
3 |
P |
|
11 |
The SS transmits a DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure. |
<– |
DEACTIVATE TEST MODE |
||
|
12 |
The UE transmits a DEACTIVATE TEST MODE COMPLETE message. |
–> |
DEACTIVATE TEST MODE COMPLETE |
– |
– |
24.1.10.3.3 Specific message contents
Table 24.1.10.3.3-0: SidelinkUEInformation (step 3, Table 24.1.10.3.2-1)
|
Derivation Path: 36.508 [18] clause 4.6.1-21B COND_TX |
|||
|
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 |
||
|
v2x-TypeTxSync-r14 |
Any value |
||
|
v2x-DestinationInfoList-r14 SEQUENCE (SIZE (1..maxSL-Dest-r12)) OF SEQUENCE { |
1 entry |
||
|
SL-DestinationIdentity-r12 |
HEX ‘0000AA’ |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.1.10.3.3-1: 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 { |
|||
|
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.10.3.3-2: RRCConnectionReconfiguration (V2X) (step 4, Table 24.1.10.3.2-1)
|
Derivation Path: 36.508 [18], table 4.6.1-8B and Table 4.6.3-20E with condition SCHEDULED |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
sl-V2X-ConfigDedicated-r14 SEQUENCE { |
|||
|
commTxResources-r14 CHOICE { |
SCHEDULED |
||
|
v2x-InterFreqInfoList-r14 SEQUENCE { |
1 entry |
||
|
SL-InterFreqInfoV2X-r14[1] SEQUENCE { |
|||
|
v2x-CommCarrierFreq-r14 |
f5 in TS 36.508 [18] clause 6.2.3.5 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 24.1.10.3.3-3: 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.1.10.3.3-4: SidelinkUEInformation (V2X) (step 10a, Table 24.1.10.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 (0..maxFreqV2X-1-r14){} |
Not Present |
||
|
v2x-CommTxResourceReq-r14 SEQUENCE (SIZE (1..maxFreqV2X-r14)) OF SEQUENCE {} |
Not Present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||