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

15.2 Vehicle domain service on vehicle multimedia service

A typical vehicle domain dynamic map service collects sensor and communication data provided by
sensors outside a vehicle and communication network. Information media, such as sensors and
network channels could be shared between VDS and VMS, but some of the dedicated information for
VDS will be sent directly and only to the VDS, as illustrated in Fig. 17. VDDMS, vehicle domain
dynamic map service will generate dynamic traffic information based on high definition map around
the master vehicle and send it to the vehicle human machine interactive interface. Desired language
translation should be provided by VDS and VMS as a unique interface, as required by the driver.
15.2.1 Use case – VDS on VMS

Figure 17 shows the typical input/output model of the vehicle domain service (VDS) integrated with
that of the vehicle multimedia service (VMS). The basic reference model of VMS is defined in
Figure 2 of this document.

Figure 17 – A reference model for data input/output of the VDS on VMS

VDS is one of the network services provided by the master vehicle, so basic inputs/outputs of VDS
are network communication channels such as cellular or short-range networks. VDDMS will generate
high definition maps from VDS specific signals of lidar, radar and sensors via recognized meta data
objects. Motion pictures provided by vehicle outside cameras will also generate meta data of foreign
objects around the master vehicle. Those meta data will be integrated as high definition map in VDS
functional module.

FGVM-01R1 (2019) 43