Content for TS 23.286 Word version: 18.5.0
0…
4…
6…
7…
9…
9.2…
9.3…
9.4…
9.5…
9.6…
9.7…
9.8…
9.9…
9.10…
9.11…
9.12…
9.13…
9.14…
9.15…
9.16…
9.17…
9.18
9.19…
9.20…
9.21…
9.22…
10…
10.2.8…
A
B…
C…
D…
9.5 File Distribution p. 44
9.5.1 General p. 44
The VAE capabilities provide support for file distribution to the V2X application specific layer. The VAE capabilities abstract the aspects like file chunking, QoE management, file delivery from the V2X application specific layer.
9.5.2 Use of MBMS "files" session type p. 44
The VAE server acts as a content provider and the VAE client acts as an MBMS client in the xMB reference model (subclause 4.1 in TS 26.348).
The VAE server makes use of the xMB procedures from TS 26.348 to create MBMS sessions whose type is set to "files" and to request the delivery of files over these sessions. Before provisioning files to the BM-SC, the VAE server prepares the file for distribution, which may include partition of large files into smaller files or encryption.
The VAE server is responsible for translating the parameters related to the V2X application triggering the file delivery into corresponding xMB parameters. Table 9.5.2-1 describes the mapping between the V2X parameters and the xMB API properties specified in TS 26.348.
| V2X parameter | Corresponding xMB API property |
|---|---|
| File transfer session indicator | Session Type: Files |
| List of files to be sent by the VAE server and their locations | File List |
| Target geographical area for the V2X UEs | Geographical Area |
| Information about the V2X application (e.g., software update, HD map download) | Service Class |
| Maximum bitrate for the V2X application | Max Bitrate |
| Maximum delay for the V2X application | Max Delay |
| QoE metrics the VAE server is interested in receiving about the V2X application | QoE Reporting |
| Local MBMS information or local MBMS activation indication | Local MBMS information (NOTE) |
|
NOTE:
The local MBMS information as the xMB API property is defined in TS 29.116.
|
|
