ENVELOPE

This use-case will focus on the periodic vehicle data collection for improving the DT version of the vehicle, which may be used afterwards, e.g., for predictive maintenance or improved vehicle design and performance, where the periodic data collection is time and/or event-triggered.

The collected data implies collecting a large volume of data from onboard sensors and roadside unit sensors for a short period (e.g., less than 3 min.), where longer data latency is allowed – the communication is not time-critical and not safety-critical.

The latency and bandwidth requirements will be mapped to a QoS profile provided by the network operator.
The APIs required for flexible QoS (profile) reservation and the reconfiguration of the 5G network to support this use case are unclear and not standardised yet. This use case will demonstrate how 5G/B5G networks could support flexible QoS allocation in dynamically changing situations by providing APIs from the 5G core network to service providers.

In this use case, the Digital Twin service plays a key role. It requests the underlying V2X communication services to inform the telecommunication operator (5G network) via newly designed APIs about the data coming from the vehicle and roadside unit sensors in the near future. The trigger for this notification can be time-based or event-based (e.g., a vehicle that is close to an intersection and is going to engage in a manoeuvre). The network operator checks the possibility of allocating the necessary resources in time based on the available resources in nearby base stations. The DT and V2X communication services then inform the vehicle (user equipment) about the reply received from the network (positive or negative reply). Based on the timely received request (originating from the DT), the telecommunication operator can better plan and coordinate the usage of its network resources, and the Digital Twin service can efficiently collect data from vehicles.