# 3 GPP 5G V2X Scenarios: Performance of QoS Parameters Using Turbo Codes
## 2 3 GPP 5G V2X QoS Scenarios and Proposed Dynamic System Model  
The performance requirements for 3 GPP 6 5G V2X scenarios are shown at Table 1 and are reproduced from [25; 26; 27; 28]. It is useful to first define a few communication range terms. In reference [28] the communication range is considered to be \"short\" for distances smaller than 200 m, \"medium\" for distances between 200 m and 500 m and \"long\" for distances larger than 500 m.  
A brief description of Table 1 scenarios follows, according to [26; 28]. It is well known that reliability is affected by the required latency. Thus, the lower transmission latency requirement, the higher the required reliability value [28]. In scenario 1 (V2V/V2I mode) cooperative awareness is used, which represents warnings and environmental awareness, like emergency vehicle warnings and emergency electronic brake lights. It requires data rates between 5 kbps to 96 kbps and between 90 to 95% reliability. For scenario 2 (V2V/V2I mode) cooperative sensing is used and it requires data rates between 5 kbps to 25 Mbps and reliabilities greater than 95%. An example would be an exchange of sensor data in a crash mitigation scenario, where 25 Mbps of data are transmitted with very high reliability within 3 ms [28]. Scenario 3 (V2V/V2I mode) includes cooperative maneuvers, with data rates between 10 kbps and 5 Mbps and high reliability (>99%). Here, the goal is the coordination of the trajectories between vehicles and dense platooning represents an exemplary case. Hence, dense platooning has a latency requirement of 3 ms, reliability higher than 99% and a data rate higher than 25 Mbps if sensor sharing is used. Scenario 4 (vehicle-to-pedestrian or V2P mode) includes vulnerable road user cases (it represents notifications of pedestrians and cyclists). Here, we have data rates between 5 kbps to 10 kbps and 95% reliability. Scenario 4 cases are similar to scenario 1 in terms of latency and reliability requirements. The difference is that the receiver device is user equipment and the required data is low, which means that the corresponding data rate is also low [28]. For scenario 5 (vehicle-to-network or V2N/V2I mode), traffic efficiency is used and latency and reliability requirements are loosened, while data rate values are between 10 kbps and 2 Mbps. At uplink, every vehicle updates the traffic management server with location and road information (more efficient route selections). At downlink, the digital maps are updated. Finally, at scenario 6 (V2N mode) tele\(-\)operated driving is used and it requires data rates larger than 25 Mbps and high reliability. Therefore, a minimum 25 Mbps uplink data rate is required for the use of from two or more cameras and other sensor vehicle information. A reliability value higher than 99% (to avoid possible malfunctions) and a latency value of less than 20 ms (for vehicle control) are required [28]. We assume the system simulation model presented in [20]. There are several operating scenarios in spectrum usage for LTE V2X, which have been used in published literature. We simulate a system that consists of two moving vehicles as platoons of vehicles with small inter-vehicle distances (about 20 m) in an urban area. The vehicles interchange small cooperative awareness messages (CAMs) with critical information for safety applications (i.e., location, relative speed [29]) featuring as many as possible QoS requirements for the most common user defined 3 GPP cases such as V2V, V2P, V2I, V2N communications [2]. The transmitting data messages are combined with its side\(-\)link control information (SCI), transmitted within the same subframe and conveying crucial information, which is appropriate for the decoding at the receiver side. At LTE\(-\)V2X Release 14, one CAM per time transmission interval (TTI) value of 1 ms is transmitted. The simulations are conducted in different channel and environmental conditions for a fairly large range of SNR values (0-10 dB) that incorporate high wireless interference/radio frequency (RF) jamming scenarios.