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

standards, so that the QoS of these media services can be guaranteed while the vehicle is roaming
across different networks. Secondly, service providers may use different application layer protocols
to support similar media services, i.e., either MPEG-DASH or HLS can be used to support streaming
services. Therefore, the transmission protocols and reception methods shall be transparent to the
upper layer protocols so that the vehicle multimedia network can be used by various service providers
to run their own services. Thirdly, the transmission protocols and reception method shall be able to
take full advantage of the characteristics of various wireless networks to improve the QoS of these
media services, or to optimize the overall network efficiency.

At present, ITU-T SG16/Q27 has achieved important progress in the standardization of vehicle
gateway (VG) and vehicle gateway platform (VGP). In the related Recommendations
[ITU-T F.749.1] and [ITU-T H.560], functional requirements for VGs, service requirements for
VGPs, architecture and functional entities of VGPs, and communications interface between external
applications and VGPs are well defined with a focus on intelligent transportation services. However,
none of these Recommendations provides transmission protocols or reception methods that can fulfill
the vehicle media service requirements of clause 7.3.
1) Recommendation [ITU-T F.749.1], Functional Requirements for Vehicle Gateways.
2) Recommendation [ITU-T F.749.2], Service Requirements for Vehicle Gateway Platforms.

3) Recommendation [ITU-T H.550], Architecture and Functional Entities of Vehicle Gateway
Platforms.

4) Recommendation [ITU-T H.560], Communications Interface between External Applications
and a Vehicle Gateway Platform [ITU-T H.560].

7.3.3 Requirements – VMS converged network

The requirements on network convergence transmission and onboard terminal processing are listed
as follows:

R1: Convergence network transmission and reception function of the VMS shall be agnostic to the
underlying physical layer transmission standards and be transparent to the upper layer applications.
R2: The VMS should take full advantage of different network characteristics to ensure uninterrupted
and seamless services (e.g., to keep the overall network costs minimum).
R3: The increase in the end-to-end system converged network transmission delays due to the VMS
should be minimized.
R4: The increase in the overall system start-up and channel switching time due to the convergence
network transmission and reception function of the VMS shall be minimized.

R5: The VMS shall require none or minimum modifications to the existing broadcasting and mobile
communication infrastructures and shall be compatible with major media streaming and broadcasting
protocols.

7.4 Networking connection among multiple terminals within the vehicle

7.4.1 Use case A – Nomadic device connectivity
The VMS provides in-vehicle media content distribution over a local wireless network
(e.g., Wi-Fi, Bluetooth, etc.) Various types of terminal (such as various types of IVI screens, mobile
phones, tablets, etc.) can connect to the vehicular multimedia system and receive content adapted to
the characteristics of the different terminals.
7.4.2 Use case B – Screen casting

Support the interactive connection between the VMS and a user's mobile device. Mobile devices use
a variety of existing screen casting systems, a non-exhaustive list includes technologies such as Wi-Fi

14 FGVM-01R1 (2019)