FileList

array

Container for the set of files, for delivery over MBMS, whose properties or transport parameters are given in the File Delivery Manifest. This field may contain the following child parameters:

– fileURL

– fileDisplayURL

– fileEarliestFetchTime

– fileLatestFetchTime

– fileSize

– targetReceptionCompletionTime

– keepUpdatedInterval

– unicastAvailability

– byteRange

– ETag

– fileRepetition

string

fileURL

–

–

–

In the case of pull-based content ingestion, the resource location of the file, as an HTTP(S) URL, at the Content Provider server from which the BM-SC can request the file.

string

fileDisplayURL

–

–

–

HTTP(S) URL of the file as provided to the MBMS-aware application.

integer

fileEarliestFetchTime

–

UTC time with second-level precision

–

In the case of pull-based content ingestion, the absolute time, expressed as the 32-bit integer portion of an NTP time stamp, representing the earliest time that the BM-SC can request the file from the Content Provider server. Absence of this parameter is an indication that the BM-SC may submit a request for the file at a time of its choosing.

integer

fileLatestFetchTime

–

UTC time with second-level precision

–

In the case of pull-based content ingestion, the absolute time, expressed as the 32-bit integer portion of an NTP time stamp, representing the latest time that the BM-SC can request the file from the Content Provider server. Absence of this parameter is an indication that the BM-SC may submit a request for the file at a time of its choosing.

integer

fileSize

–

bytes

–

Precise or estimated size of the file in units of bytes. If this parameter is absent, it means that the file size is not known to the Content Provider.

integer

targetReceptionCompletionTime

–

UTC time with second-level precision

–

A hint from the CP to the BM-SC on the nominally expected time, expressed as the 32-bit integer portion of an NTP time stamp, at which the file should be completely received by the MBMS client and made available to the MBMS-aware application. The BM-SC is expected to schedule and order transmission of the file in accordance to this attribute. Absence of this parameter is an indication that there is no explicit requirement by the CP on when the reception of the file at the MBMS client should occur, other than it should not be earlier than earliestReceptionCompletionTime, if present, in the File Delivery Manifest.

integer

keepUpdatedInterval

milliseconds

–

Interval that the BM-SC is expected to check for update of the file if it belongs to a Keep-Updated Service.

boolean

unicastAvailability

–

–

false

Indication that the file is also available for unicast acquisition by the application at a Content Provider server whose location is given by the HTTP(S) URL corresponding to the value of the parameter fileDisplayURL.

boolean

byteRange

—

—

false

If present and set to “true”, indicates that the HTTP(S) URL given in the fileDisplayURL parameter can be used for Byte-Range-Based file repair (subclause 9.3) otherwise fileDisplayURL parameter should not be used for Byte-Range-Based file repair.

string

ETag

—

—

—

represents the value of the ETag as defined in RFC 2616 [18] which may also serve as the version identifier for the file in the Byte-Range-Based file repair requests.

The ETag should only be supplied by the 3rd party content provider if it is expected that it is different from the one provided over xMB-U when fetching the file.

number

fileRepetition

–

–

–

The number of times the file shall be sent on the session (a value of 1 means the file shall be sent only once). This counter shall be decremented each time the file has been transmitted. When the counter reaches zero, the file shall cease to be delivered. The BM-SC may send FEC repair symbols instead of source symbols. Default value is 1.

Note that the expected behaviour is that the BM-SC first sends all the files as ordered in “FileList”, then decrements the counter for each file, and subsequently retransmits the list of files again (only those files whose counter > 0 are transmitted). This process is repeated until either the counter reaches ‘0’, or the session stop time has elapsed, whichever event occurs first.