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

Network communication channels connected to VDS will be shared with VMS in order to exchange
other kinds of communication network services. Motion pictures acquired by cameras outside the
vehicle are also shared similar to the vehicle outside/surrounding monitor service of VMS.
VDDMS will have some user interactive functions, such as traffic information monitor, warning
messages about dangerous traffic objects and interactive messaging services between the driver in the
master vehicle and domain vehicles and other participants of surrounding traffic. The driver
condition, which could be monitored by the vehicle cabin camera, could be an optional VDS services.
These interactive human machine interface (HMI) services with the driver will be basically provided
by VMS and VDS that will utilize these VMS service connecting to VMS.
As explained in clause 6, Figure 2 of the VMS input/output reference model, the VDS function
indicated in Figure 16 never shows a single physical unit. It is located in the VMS function in the
figure, but its function is independently implemented from VMS functions. VDS shares some
inputs/outputs with VMS and uses the interactive HMI service of the VMS. Therefore, this document
includes implementation of a VDS function along with the multimedia network platform of VMS.

15.2.2 Requirements – VDS use case in relation with VMS

This clause will provide use case requirements about VDS, focusing VDDMS on VMS. Relevant use
case definition and detailed explanation are given in clause 15.2.

VVR1: The VMS may be designed to support VDS function.

VVR2: If the VDS is implemented with VMS, network communication channels and connection shall
be accessible to both the VMS and VDS.
NOTE 1 – VMS and VDS will share only lower layers of communication channel.

VVR3: If the VDS is implemented with VMS, raw data from external cameras of the vehicle and
sensors shall be accessible by VMS and VDS independently.
NOTE 2 – Low level motion picture data input to VDS will be treated by image recognition engine to convert
lighter Meta data of traffic objects.

VVR4: The VMS may provide interactive HMI with driver to the VDS, especially to VDDMS.
VVR5: If VDS is implemented with VMS, the VMS and VDS shall keep real time quality between
interactive HMI and real surrounding traffic condition.
NOTE 3 – It is important for VMS and VDS to give good synchronization between their displayed contents of
VDDMS and real traffic condition around the vehicle.
VVR6: If VDS is implemented with VMS, good synchronization between VDDMS graphic contents
displayed by VMS and surrounding real traffic condition shall be defined as delay time between them.
NOTE 4 – The criteria of delay time depends on other requirements.

16 Matching of described use cases with driving levels
The following table matches use cases and services that have been defined within the focus group
with the SAE driving levels. All activities that are mentioned in the table should be considered for a
driving vehicle. When the vehicle parks or stands still, all services are available for the driver as well
as for the passengers. Excluded in this case is a standing vehicle at traffic lights or other traffic signs
as in this case the vehicle and the driver are still considered as active traffic participants similar to a
driving car.
Within the driving levels, a distinction on what drivers (D) and passengers (P) are allowed to do in
the framework of these use cases and services is taken into consideration.

44 FGVM-01R1 (2019)