ecessary for autonomous driving. Remote driving: Enables a remote driver or a V2X application to operate a remote vehi- cle for those passengers who cannot drive by themselves or remote vehicles located in dangerous environments. For a case where route variation is limited and routes are pre- dictable, such as public transportation, driving based on cloud computing can be used. High reliability and low latency are the main requirements of this use case. Remote driving enables the remote control of a vehicle by a human operator or by a cloud- based application, via V2N communication. There are several scenarios that can lever- age remote driving, including: Provide a fallback solution for autonomous vehicles. An example is during the ini- tial autonomous vehicle deployment when a vehicle is in an unfamiliar environment and has difficulty navigating. Provide remote driver services to the youths, elderly, and others who are not licensed or able to drive. Enable fleet owners to remotely control their vehicles. Examples including moving trucks from one location to another, delivering rental cars to customers, and provid- ing remotely driven taxi services. Enable cloud-driven public transportation and private shuttles, all of which are par- ticularly suitable for services with predefined stops and routes. Remote driving can reduce the cost of fully autonomous driving for certain use cases because of the less stringent technical requirements (e.g., smaller number of in-vehicle sensors and less computation requirements for sophisticated algorithms). The following are V2X requirements for supporting remote driving: - Data rate up to 1 Mbps downlink and 25 Mbps in the uplink. - Ultra-high reliability at 99.999% or higher [similar to ultra-reliable and low- latency communication (URLLC) use case]. End-to-end latency of 5 ms between the V2X application server and the vehicle. Support vehicular speeds of up to 250 km/h. Remote control will be required when an obstacle blocks an autonomous driving vehi- cle, rendering it unabl