Understand the 3GPP Architectures for V2X and eV2X Communications

Course outline : Connected vehicles have been around for about 10 years with a development of services that followed that of cellular technologies (2G, 3G, 4G). Today it is possible to receive and report traffic information or access Infotainment services on board. Beyond these commercial and business developments, the emergency call service (eCall) is the first connectivity service to be mandatory on all new vehicles since 2018. It therefore requires vehicle connectivity to cellular networks and geolocation using satellite positioning systems (eg, GPS). As such, eCall marks the large-scale start of connectivity services for vehicles.
In the global context of road transport, connectivity will be a major asset to support the start of new commercial services and the emergence of new directions from the European community and member states in this area. The exchange of data between vehicles, traffic management centers and the Internet will allow the development of new services for car users. The automotive industry will undergo two major changes with the development of autonomous driving and that of road safety and traffic management services. These two developments will require the deployment of new 5G technology.
Autonomous driving will require a large amount of data from the car's sensors to be aggregated to calculate the trajectory of the car; communications between vehicles and between vehicles and infrastructures will enable the latter to exchange richer real-time messages concerning changes in road traffic. They will contribute to the acquisition of a broader vision of the travel space specific to each vehicle.
The adoption of quality standards is absolutely essential to offer vehicles reliable and secure communications while allowing interoperability of services at the global level. Standards based on open platforms are necessary for the deployment of systems and their interoperability, but also to avoid market fragmentation and the postponement of the deployment of V2X technologies. The standardization work initially carried out by 3GPP called V2X is currently being extended to concern new architecture diagrams intended to support eV2X (for Vehicle to Everything) communications to allow vehicles to communicate in real time with their environment in order to improve road safety, traffic efficiency and energy savings.
The purpose of this training is to introduce the V2X ecosystem and describe the eV2X needs, associated services, 5G architecture for eV2X and uRLLC network slice to meet latency, jitter, and reliability requirements.
1. From V2X to eV2X
1.1. V2X Standards
1.2. Support for V2X application types with 3GPP
1.2.1. Vehicle-to-Vehicle (V2V)
1.2.2. Vehicle-to-Pedestrian (V2P)
1.2.3. Vehicle-to-Network (V2N)
1.2.4. Vehicle-to-Infrastructure (V2I)
1.3. Automation level
1.3.1. Level 0: no automation
1.3.2. Level 1: driver assistance
1.3.3. Level 2: partial automation
1.3.4. Level 3: conditional automation
1.3.5. Level 4: high automation
1.3.6. Level 5: full automation
1.4. V2X versus 802.11P
1.5. Spectrum for V2X services
1.6. 3GPP improvements to support eV2X
1.6.1. eV2X versus V2X
1.6.2. Vehicle-to-everything (eV2X) communication service
1.6.3. Vehicle platooning
1.6.4. Advanced driving
1.6.5. Extended sensors
1.6.6. Remote driving

2. Architecture for V2X services
2.1. V2X communication based on PC5
2.2. V2X communication based on LTE-Uu
2.3. V2X Architecture based on PC5 and LTE-Uu
2.3.1. V2X Application Server
2.3.2. V2X Control Function
2.3.3. V2X Application
2.3.4. V1, V2, V3, V4, V5, LTE-Uu and PC5 interfaces
2.4. Policies/parameters provisioning for V2X communications on UE via PC5 and LTE-Uu
2.5. Transmission/Reception of V2X messages via PC5 and LTE-Uu
2.6. Call flows for the associated procedures

3. Architecture for eV2X services
3.1. eV2X communication based on PC5
3.2. V2X communication based on NG-Uu
3.3. Policies/parameters provisioning for V2X communications on UE via PC5 and NG-Uu
3.4. Impacts of eV2X on 5GC procedures
3.4.1. UE registration procedure
3.4.2. UE Service request procedure
3.4.3. N2 handover procedure
3.4.4. Xn handover procedure
3.4.5. Impacts on existing entities and interfaces

4. uRLLC Slice
4.1. Key elements to meet uRLLC requirements on latency, jitter and reliability
4.2. Minimization of UE mobility on latency and jitter between the access network and the core network and in the core network
4.3. More reliable transmission than that of a single tunnel on the N3 and N9 interfaces on the user plane
4.4. QoS supervision of QoS flows with uRLLC requirements
4.5. Impacts on policy control and charging control