26.3473GPPApplication Programming Interface and URLMultimedia Broadcast/Multicast Service (MBMS)Release 17TS
The File Delivery Application Service API provides MBMS Aware applications with interfaces to manage the reception of files delivered over File Delivery Application User Services. This API is intended to support applications that are running while files are being delivered through MBMS user services as well as applications that are not running to receive information on files received through an MBMS User service, for example as the user may have quit/exited the application.
In order to support applications that may not be currently running while files are being received, the MBMS client may keep received files for a period of time configured by the application, which includes means to collect received files even if the user does not actively interact with the application to consume the received files.
When the application is currently running and can collect the files received over MBMS User services, the MBMS client moves the files to the application space. It is ultimately the application’s responsibility to manage the storage of requested files, especially the amount of storage to be used.
Any persistent storage of received files by the MBMS client is only intended to ensure that the received files are made available to the respective requesting application. Once files are moved/copied to the application space, the application is responsible for managing those files.
When the content provider use the "content provider" announcement mode (3GPP TS 29.116 ) for a file delivery session, the BM-SC provides the service announcement information to the content provider within a SA file, following the profile 1c (Annex L.3 of 3GPP 26.346 ). This SA file may be transmitted by the content provider directly to the MBMS Aware application. In such case, SA information may be provided to the MBMS client by the MBMS aware application.
The IDL for the File Delivery Application Service API is defined in clause B.2.