Situational Awareness | The ability to know and understand what is going on in the surroundings, e.g. the perception of environmental elements and events |
Use Cases | Characteristic parameter (KPI) | Influence quantity | ||||||
---|---|---|---|---|---|---|---|---|
Max allowed end-to-end latency | Service bit rate: user-experienced data rate | Reliability | Area Traffic capacity | Message Data Volume | Transfer Interval | Service Area | ||
5G-enabled Traffic Flow Simulation and Situational Awareness | [5-20] ms (NOTE 1) | [10~100 Mbit/s] [25](NOTE 6) | > 99.9% | [~39.6 Tbit/s/km2 ]
(NOTE 5) | Typical data:
Camera: 10M bits/s per sensor (unstructured)
LiDAR: 90M bits/s per sensor (unstructured)
Radar: 10M per sensor (unstructured)
Real-time Status information including Telemetry data:
[< 50K bits/s] per sensor/vehicle/VRU (structured) (NOTE 2) | 20-100 ms
(NOTE 3) | City or Country wide
(NOTE 4) | |
NOTE 1:
The mobile metaverse server receives the data from various sensors, performs data processing, rendering and provide feedback to the vehicles and user s. The end-to-end latency refers to the transmission delay between a UE and the mobile metaverse server. Exact value is FFS.
NOTE 2:
To support at least 80 vehicles and 1600 users present at the same location (e.g. in an area of 40m*250m) to actively enjoy immersive metaverse services for traffic simulation and traffic awareness, the area traffic capacity is calculated considering 2 cameras, 2 Radars, 2 LiDARs on road side, 1600 user's smart phones and 80 vehicles with 7 cameras, 4 radar and 2 LiDAR for each vehicle. These application layer message data need to be segmented for network transport thus doesn't mean packet size. The real-time status information including telemetry data may be structured.
NOTE 3:
The frequency considers different sensor types such as Radar/LiDAR (10Hz) and Camera (10~50Hz).
NOTE 4:
The service area for traffic flow simulation and situational awareness depends on the actual deployment, for example, it can be deployed for a city or a district within a city or even countrywide. In some cases a local approach (e.g. the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
NOTE 5:
The calculation is this table is done per one 5G network, in case of N 5G networks to be involved for such use case in the same area, this value can be divided by N. Exact value is FFS.
NOTE 6:
User experienced data rate refers to the data rate needed for the vehicle or human, the value is observed from industrial practice and exact value is FFS.
|