Page 34 - Use cases and requirements for the vehicular multimedia networks - Focus Group on Vehicular Multimedia (FG-VM)

8.4 Data formats and storage

8.4.1 Use case and considerations
There is a need to define a minimum set of data formats to be supported by a VMS to allow for
interoperability between different VMS and different VMNS providers. The following aspects should
be considered:
– Codecs (and protocols) used by broadcast and interactive systems to and from a VMS.
– Contents on nomadic devices (mobile phones) when connecting to the VMS (e.g., to share
content via the VMU).
– Existing codecs usually supported by current infotainment solution.
– Additional sensors and their storage/compression requirements for VM system services
(e.g., maps, AR, telematics).

The main ECU may be built on a powerful processor, while processors with lower capabilities
(e.g., limited set of codecs) may be available in the vehicle (e.g., with mounted display in back seat
positions). As such, it can be desirable to transcode content received at the main ECU in formats
supported throughout the vehicle.
Further, as the amount of data exchanged between device and infrastructure is becoming a bottleneck,
evaluation of codec performances (compression, lossless/lossy capabilities) should be taken in
account when deciding on codec support. In the context of a VMS, this data comprises at least audio,
video, images and point-cloud (such as lidar) which can be used both for entertainment and safety
purposes.

In addition, VMS and VMU will need to support software updates. These updates and software codecs
should be securely provided. Their use and access by different VMNS may be restricted.

8.4.1.1 Requirements – Data format

For multimedia broadcasting services provided by a VMNS service provider, the media types, content
navigation methods and interactivity methods supported by a VMS and VMNP shall be selected from
the recommended format in [ITU-T BT.2055-1].
Additional media types may be supported by the VMS and the VMNP to address some regional
requirements (e.g., support of AVS2 codecs in China).

A VMN application may support additional software codecs to address the need of a VMNS service
provider.

For interactive, and non-broadcasted VMNS, the VMNP and VMS:
– Should support the same multimedia broadcast media types
– May support JPEG-XS

– May support MPEG-H 3D audio
NOTE – The selection of media types and transmission protocol formats (e.g., MPEG-DASH, MBMS, etc.)
will be refined after the architecture phase.

9 Privacy considerations

9.1 Background

A VMS could have the following characteristics:
1) Be available on a connected vehicle (or/and autonomous vehicle)
2) Be personalizable, like a phone, a subscription or a service tailored to the user and to the
user's interests

24 FGVM-01R1 (2019)