Page 46 - Use cases and requirements for the vehicular multimedia networks - Focus Group on Vehicular Multimedia (FG-VM)
P. 46
R3: It shall be possible to wipe all the data (application, content and data) on the VMS to return the
VMS to its factory settings.
R4: It shall be possible to wipe a subset of the data on the VMS.
R5: The wipe shall be able to be performed by different authorised entities such as the VMNS service
provider, the end-user or the VMS manufacturer.
12.3 Use Case – VMS software security
Due to increasing system complexity, software error or software fault may exist in VMS, which may
cause crashes. The system should guarantee that such fault would not cause operation errors or
abnormal stop that would threaten security, and would cause the entire vehicle system may not work
properly.
12.3.1 Requirements
R1: The vehicular multimedia systems shall be segregated from other vehicular control systems to
avoid the failure and system fault of the whole vehicle systems. The vehicular multimedia systems
should also provide physical or logical access controls for the isolation of sensitive applications,
application data, or systems.
13 Safety
13.1 Use case – Driving safety: Speed control
Before L4 and L5 autonomous vehicle are commercialized, consuming audio and video content in
vehicles will easily be a cause for driver's distraction. In accordance with local regulation, when the
vehicle speed reaches a certain threshold (it differs based on local regulation, for instance
from 0 kilometer to 15 kilometers per hour), the VMS shall automatically block entertainment content
on the driver-side display. Speed control is a common practice already in use in countries around the
world.
Requirement:
R1: In accordance with local regulation, when the vehicle speed is above a given threshold, the VMS
shall be able to automatically block entertainment content on the driver-side display.
14 Definition of vehicular multimedia configurations
As smart connected vehicles are more broadly available, vehicular multimedia services are becoming
richer and more complex than before. Vehicular multimedia configurations for smart connected
vehicle could be used to manufacture and qualify vehicles accordingly. Customers can know which
multimedia capabilities his/her vehicle multimedia offers.
14.1 Use case – Vehicular multimedia configurations
Currently, when customers choose a vehicle to acquire, the vendor of the vehicle generally provides
them with a limited configure sheet which may not have detailed information on the multimedia
capability of the vehicle (e.g., FM/CD/DVD and some other storage disk such as USB disk/SD
card/TF card). With the specification of VMS, and the deployment of smart connected
vehicle/autonomous driving/ADAS, vehicular multimedia system (VMS) configurations should be
defined and include network connectivity, media display, HMI controls, PII protection and security
capabilities.
1) Networks connectivity capabilities:
VMS configurations should support one or more of the following:
36 FGVM-01R1 (2019)