nt or teleoperated driving. Radio Access Network (RAN) selection - Through the use of Cloud-RAN (C-RAN), often, V2X network slicing can support the on-demand deployment of RAN functions. In this scenario, the radio and baseband processing functionalities are split and the Baseband Unit (BBU) pool runs in the cloud. These resources can be dynamically allocated to Evolved NodeBs (eNBs) to meet the vehicles' demands. Communication mode and primitive selection - The V2X slice configuration is mapped to a communication mode such as sidelink or cellular communication. Likewise, a primitive 5G V2X such as unicast, multicast, or broadcast can be used. A network slice for autonomous driving may mostly use sidelink communications for localized interactions. Applications such as the platooning of trucks may use unicast for V2I and V2N. However, multicast may be used for accident or traffic jam warnings. Radio resource allocation - The 3GPP-recommended dynamic scheduling scheme adaptively allocates radio resources based on the buffer status of UE and works well for vehicular infotainment slices. An autonomous driving network slice may rely on semi-persistent scheduling. Numerology - Using different time/frequency numerology, 5G can support V2X communications. This takes care of Doppler effects due to the high-speed movement of vehicles. We have reviewed network slicing in the RAN. Next, we will look at network slicing of the Core Network (CN) for V2X. This involves the following: Mobility Management Entity (MME) - The MME's role in the CN is to manage the mobility, session, and auth (authentication and authorization) procedures. A good and flexible design principle is to enable multiple MME instances as Virtualized Network Functions (VNFs). These interconnected MMEs can then meet the different V2X requirements. Evolved Multimedia Broadcast and Multicast Services (eMBMS) - This helps with the quick dissemination of vehicle safety data in case of an accident or another emergency. The autonomous driving network slice can be act