ivated on the fly for multicast flows for these safety-critical messages. Application servers - Traditionally, application servers run in the cloud or data centers. With MEC, the V2X application servers can run at the eNodeB location. This allows for a reduction in latency for V2X-related services. After looking at the network slicing of the RAN, let us look at the slicing of the UE. On vehicular devices, network slicing may impact certain configurations. In some cases, vehicular UE may even host a V2X application server as a container. In these cases, a slice should be able to support the vehicular UE to act as a storage unit for other UE nearby - for example, a pedestrian using a smartphone. Now that we have looked at the network slicing considerations for V2X, in the next section, we will deep-dive into V2X. 5G V2X As we learned in the preceding sections, V2X refers to highly reliable communication between the major components of intelligent transportation and traffic systems and their sensors. V2X requires low-latency and high-bandwidth capabilities such as those provided by 5G. Let us explore V2X further. 5G and Autonomous Vehicles V2X technology V2X is often used as the umbrella term for connected vehicles and the communications around them. Figure 14.14 shows V2X communications (see https://www.autoweek.com/news/ technology/a36190311/v2x-technology/ for more details): Vehicle-to-Pedestrian Vehicle-to-Network Communication Communication Vehicle-to Vehicle Vehicle-to-Infrastructure Communication Communication Figure 14.14 - V2X communications In Figure 14.14, we can see the interplay of V2X with V2V, V2P, V2I, and V2N. In order to foster interoperability, there are multiple standards around V2X. 5G communications allow fast-moving vehicles to act like a smart cluster rather than individual cars (https : //www.ericsson.com/ en/news/2019/9/5g-and-v2x) Let us look at the V2X standards next. The V2X standards We will look at the standards that are evolving around AVs. IEEE 1609 is a collection of such standards 