YD/T 3400-2018 PDF English
US$685.00 · In stock · Download in 9 secondsYD/T 3400-2018: General Technical Requirements of LTE-Based Vehicular Communication Delivery: 9 seconds. True-PDF full-copy in English & invoice will be downloaded + auto-delivered via email. See step-by-step procedureStatus: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivery | Name of Chinese Standard | Status |
| YD/T 3400-2018 | English | 685 |
Add to Cart
|
0-9 seconds. Auto-delivery
|
General Technical Requirements of LTE-Based Vehicular Communication
| Valid |
Excerpted PDFs (Download full copy in 9 seconds upon purchase)PDF Preview: YD/T 3400-2018
YD/T 3400-2018: General Technical Requirements of LTE-Based Vehicular Communication---This is an excerpt. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.), auto-downloaded/delivered in 9 seconds, can be purchased online: https://www.ChineseStandard.net/PDF.aspx/YDT3400-2018
YD
COMMUNICATION INDUSTRY STANDARD
ICS 33.060.99
M 36
General Technical Requirements of LTE-Based
Vehicular Communication
Issued on. DECEMBER 21, 2018
Implemented on. APRIL 01, 2019
Issued by. Ministry of Industry and Information Technology of PRC
Table of Contents
Foreword... 4
1 Scope... 5
2 Normative References... 5
3 Terms, Definitions and Abbreviations... 5
3.1 Terms and Definitions... 5
3.2 Abbreviations... 6
4 Overview... 7
5 General Service Requirements of LTE-Based Vehicle-to-Everything... 7
5.1 Basic requirements... 7
5.2 Effective communication distance... 9
5.3 Movement speed... 9
5.4 Communication delay... 9
5.5 Transmission reliability... 9
5.6 Requirements for information security... 9
5.7 Requirements for coverage... 10
5.8 Requirements for message sending frequency... 10
5.9 Requirements for message size... 10
6 Radio Communication System Architecture of LTE-Based Vehicle-to-
Everything... 11
6.1 Architecture model... 11
6.2 Introduction of the interface... 14
6.3 Functional entities... 15
7 Basic Functional Requirements of LTE-Based Vehicle-to-Everything... 17
7.1 High-level functional requirements... 18
7.2 Requirements of the radio function... 27
7.3 Identification... 33
7.4 Function description and message flow... 34
Appendix A (Informative) Application Scenarios and Requirements of the LTE-
Based Vehicle-to-Everything... 41
1 Scope
This Standard specifies the overall service requirements, system architecture and
basic functional requirements of LTE-based vehicular communication.
This Standard is applicable to LTE-based vehicular communication systems.
2 Normative References
The following documents are essential to the application of this document. For the
dated documents, only the versions with the dates indicated are applicable to this
document; for the undated documents, only the latest version (including all the
amendments) is applicable to this document.
3GPP TS 23.246 Multimedia Broadcast/Multicast Service (MBMS) Architecture
and Functional Description
3GPP TS 23.303 Proximity-Based Service (ProSe); Stage 2
3GPP TS 23.401 General Packet Radio Service (GPRS) Enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access
3GPP TS 23.468 Group Communication System Enablers for LTE (GCSE_LTE);
Stage 2
3GPP TS 33.185 Security Aspect for LTE Support of V2X Services
3GPP TS 36.331 Evolved Universal Terrestrial Radio Access (E-UTRA) Radio
Resource Control (RRC); Protocol Specification
3 Terms, Definitions and Abbreviations
3.1 Terms and Definitions
For the purpose of this document, the following terms and definitions apply.
3.1.1 Road side unit (RSU)
An entity that supports V2I services and may communicate with UE. The RSU may
appear as an eNB or a stationary UE. When the RSU appears as a stationary UE, it
may be in or out of the LTE network coverage.
3.2 Abbreviations
For the purpose of this document, the following abbreviations apply.
C-TEID. Common-Tunnel Endpoint IDentifier;
EPS. Evolved Packet System;
E-UTRAN. Evolved UTRAN;
HPLMN. Home Public land Mobile Network;
L.MBMS. Local MBMS;
MBMS. Multimedia Broadcast/Multicast Service;
ME. Mobile Equipment;
4 Overview
Vehicle-to-Everything (V2X) applications include Vehicle-to-Vehicle (V2V) applications,
Vehicle-to-Infrastructure (V2I) applications, Vehicle-to-Network (V2N) applications and
Vehicle-to-Pedestrian (V2P) applications.
V2V application refers to the exchange of V2V application information between
adjacent on-board UEs. The information exchange is based on the broadcast mode,
and the direct mode between UEs may be used, or information may be exchanged
between UEs through infrastructure [such as road side unit (RSU), application server].
V2I application refers to the on-board UE sends V2I application information to the RSU
or local application server; and the RSU or local application server sends the V2I
application information to the on-board UE.
V2N application refers to communication between UE and application server through
EPS network.
V2P application refers to the exchange of V2P application information between an on-
board UE and a human-held UE. Information exchange may adopt the direct mode
between UEs, or exchange information between UEs via infrastructure [such as road
side unit (RSU), application server].
5 General Service Requirements of LTE-Based Vehicle- to-Everything
5.1 Basic requirements
Requirement 1.When the sending terminal is served by E-UTRAN that supports V2X,
the message transmission shall be controlled by the 3GPP network.
Requirement 6.
5.2 Effective communication distance
Requirement 16.E-UTRA shall be able to provide sufficient effective communication
distance to ensure that the driver has sufficient response time (for instance, 4s).
5.3 Movement speed
Requirement 17.Regardless of whether the Vehicle-to-Everything terminal uses the
Vehicle-to-Everything communication service that is provided by E-UTRAN that
supports V2X communication, the 3GPP system shall be able to support messages
sending between vehicles at a maximum relative speed of 500km/h.
5.4 Communication delay
Requirement 19.For terminals that support vehicle-to-vehicle and vehicle-to-
pedestrian communication, whether it is sent directly or forwarded by a road side unit,
E-UTRA (N) shall ensure that the maximum communication delay not exceed 100ms.
Requirement 20.Only for special use cases (such as collision detection), the maximum
delay of sending V2V messages between E-UTRA (N) Vehicle-to-Everything terminals
should not exceed 20ms.
5.5 Transmission reliability
Requirement 23.The E-UTRAN network shall not rely on application layer
retransmission to provide highly reliable transmission.
5.6 Requirements for information security
Requirement 24.When the Vehicle-to-Everything terminal uses the service that is
provided by E-UTRAN that supports V2X communication, the 3GPP network shall
provide a method for the operator to authorize the Vehicle-to-Everything terminal to
perform V2X communication.
5.7 Requirements for coverage
Requirement 30.V2X services shall be supported both with and without operator
network coverage.
5.8 Requirements for message sending frequency
Requirement 31.E-UTRAN shall be able to support road side units and Vehicle-to-
Everything terminals with a message sending frequency of up to 10Hz.
NOTE. The messages transmitted by V2X applications to 3GPP may be either periodic or
triggered by specific events.
5.9 Requirements for message size
Requirement 32.Excluding security-related message units, for periodic messages, E-
UTRAN shall be able to support a maximum of 50~300 bytes of messages that are
transmitted between two UEs that support V2X applications.
6 Radio Communication System Architecture of LTE-
Based Vehicle-to-Everything
6.1 Architecture model
6.1.1 Overview
V2X communication has two mutually independent and complementary working
modes; namely, V2X communication based on PC5 direct mode and V2X
communication based on LTE-Uu. The working mode based on LTE-Uu may be unicast
or MBMS. The UE may use these two working modes to receive and transmit,
respectively. For example. A UE may use MBMS to receive V2X messages, but send
V2X messages without using LTE-Uu. A UE may also receive V2X messages through
LTE-Uu downlink unicast.
6.1.2 V2X communication architecture based on PC5 and LTE-Uu
6.1.2.1 V2X communication architecture based on PC5 and LTE-Uu in non-
roaming scenarios
6.1.2.2 V2X communication architecture based on PC5 and LTE-Uu in roaming
scenarios
6.2 Introduction of the interface
Each interface is introduced as follows.
6.3 Functional entities
6.3.1 UE
The UE may support the following functions.
7 Basic Functional Requirements of LTE-Based
Vehicle-to-Everything
7.1 High-level functional requirements
7.1.1 Authorization and provision function
7.1.1.1 Authorization and provision of V2X communication on the PC5 interface
7.1.1.1.1 Overview
The authorization of V2X communication based on the PC5 interface shall follow the
following principles.
7.1.1.1.2 Provision of the strategy/parameter
The V2X communication based on the PC5 interface needs to provide the following
information to the UE.
7.1.1.1.3 Configuration principles for the parameters of the V2X communication
on the PC5 interface
For V2X communication based on the PC5 interface, the operator may pre-configure
the parameters required for V2X communication to the UE without the need for the UE
to connect to the V2X control function to obtain the initial configuration, and follow the
following principles.
7.1.2 Sending and receiving messages on PC5 interface
The PC5 interface (as defined in 3GPP TS 23.303) is used to send and receive V2X
messages. V2X communication based on the PC5 interface supports roaming and
cross-PLMN operations. The UE may support V2X communication based on the PC5
interface in the scenarios of "using E-UTRAN services" and "not using E-UTRAN
services".
7.1.5 QoS processing
7.1.5.1 QoS management on PC5 interface
The MME sends the UE-PC5-AMBR as part of the UE context information to the eNB
based on the subscription information.
7.2 Requirements of the radio function
7.2.1 Overview
Supports the provision of V2X services through the PC5 interface and/or Uu interface.
The UE may support V2X communication based on the PC5 interface in the scenarios
of "using E-UTRAN services" and "not using E-UTRAN services".
7.3 Identification
On the PC5 interface, each UE has a Layer-2 ID for V2X communication, which is
included in each frame as the source Layer-2 ID on the Layer-2 link. The UE self-
configures Layer-2 ID for V2X communication.
7.4 Function description and message flow
7.4.1 Control plane and user plane protocol stack
The PC5-U protocol stack defined in the proximity communication (see 3GPP TS
23.303) is used for V2X communication transmission based on the PC5 interface. The
V2X communication transmission based on the PC5 interface supports IP and non-IP
PDCP SDU.
7.4.5.4 X2 handover
For handover with X2, the "V2X service authorized" indication and UE-PC5-AMBR are
sent to the target eNB.
7.4.5.5 Tracking area update (TAU)
The TAU process has the following modifications.
7.4.5.6 Acquire subscription data
The subscription data acquisition process has the following modifications. If the "V2X
services authorized" indication and the UE-PC5-AMBR subscription change, and the
S1 bearer has been established, the MME sends the modified "V2X services
authorized" indication and UE-PC5-AMBR to the eNB through the S1-AP UE Context
Modification Request message.
......
Source: Above contents are excerpted from the full-copy PDF -- translated/reviewed by: www.ChineseStandard.net / Wayne Zheng et al.
Tips & Frequently Asked QuestionsQuestion 1: How long will the true-PDF of English version of YD/T 3400-2018 be delivered?Answer: The full copy PDF of English version of YD/T 3400-2018 can be downloaded in 9 seconds, and it will also be emailed to you in 9 seconds (double mechanisms to ensure the delivery reliably), with PDF-invoice. Question 2: Can I share the purchased PDF of YD/T 3400-2018_English with my colleagues?Answer: Yes. The purchased PDF of YD/T 3400-2018_English will be deemed to be sold to your employer/organization who actually paid for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. www.ChineseStandard.us -- YD/T 3400-2018 -- Click this link and select your country/currency to pay, the exact amount in your currency will be printed on the invoice. Full PDF will also be downloaded/emailed in 9 seconds. How to buy and download a true PDF of English version of YD/T 3400-2018?A step-by-step guide to download PDF of YD/T 3400-2018_EnglishStep 1: Visit website https://www.ChineseStandard.net (Pay in USD), or https://www.ChineseStandard.us (Pay in any currencies such as Euro, KRW, JPY, AUD).
Step 2: Search keyword "YD/T 3400-2018".
Step 3: Click "Add to Cart". If multiple PDFs are required, repeat steps 2 and 3 to add up to 12 PDFs to cart.
Step 4: Select payment option (Via payment agents Stripe or PayPal).
Step 5: Customize Tax Invoice -- Fill up your email etc.
Step 6: Click "Checkout".
Step 7: Make payment by credit card, PayPal, Google Pay etc. After the payment is completed and in 9 seconds, you will receive 2 emails attached with the purchased PDFs and PDF-invoice, respectively.
Step 8: Optional -- Go to download PDF.
Step 9: Optional -- Click Open/Download PDF to download PDFs and invoice.
See screenshots for above steps: Steps 1~3 Steps 4~6 Step 7 Step 8 Step 9
|