Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 26.346  Word version:  19.1.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.3…   6   7…   7.3…   8…   8A…   8B…   9…   9.4…   10…   11…   12…   A   B…   C…   D…   G…   H…   J…   K…   L…   M…

 

A (Normative)  FLUTE support requirementsp. 202

This clause provides a Table representation of the requirement levels for different features in FLUTE. Table A.1 includes requirements for an MBMS Client and an MBMS server for FLUTE support as well as the requirements for a FLUTE client and a FLUTE server according to the FLUTE protocol (RFC 3926). The terms used in Table A.1 are described underneath.
FLUTE Client support requirement as per RFC 3926 MBMS FLUTE Client support requirement as per present document FLUTE Server use requirement as per RFC 3926 MBMS FLUTE Server use requirement as per present document
FLUTE Blocking AlgorithmRequiredRequiredStrongly recommendedRequired
Symbol Encoding AlgorithmCompact No-Code algorithm required.
Other FEC building blocks are undefined optional plug-ins.
Compact No-Code algorithm required.
MBMS Forward Error Correction required
Compact No-Code algorithm is the default option.
Other FEC building blocks are undefined optional plug-ins.
Compact No-Code algorithm is the default option. MBMS Forward Error Correction.
Congestion Control Building Block (CCBB) / AlgorithmCongestion Control building blocks undefined.Single channel support requiredSingle channel without additional CCBB given for the controlled network scenario.Single channel support required
Content Encoding for FDT InstancesOptionalOptionalOptionalShall not be used
Content Encoding for any other file than FDT InstancesOptionalRequiredOptionalOptional
A flag active (header)RequiredOptional
(see Note at the end of this Annex)
OptionalSet to zero
(see Note at the end of this Annex)
B flag active (header)RequiredRequiredOptionalNot recommended to use
T flag active and SCT field (header)OptionalOptionalOptionalSet to zero
R flag active and ERT field (header)OptionalOptionalOptionalSet to zero
Content-Location attribute (FDT)RequiredRequiredRequiredRequired
TOI (FDT)RequiredRequiredRequiredRequired
FDT Expires attribute (FDT)RequiredRequiredRequiredRequired
Complete attribute (FDT)RequiredRequiredOptionalOptional
FEC-OTI-Maximum-Source-Block-LengthRequiredRequiredRequiredRequired
FEC-OTI-Encoding-Symbol-LengthRequiredRequiredRequiredRequired
FEC-OTI-Max-Number-of-Encoding-SymbolsRequiredRequiredRequiredRequired
FEC-OTI-FEC-Instance-IDRequiredOptionalRequiredOptional
FEC-OTI-Scheme-Specific-Infon/aRequiredn/aRequired if MBMS FEC used
The following are descriptions of the above terms:
  • Blocking algorithm: The blocking algorithms is used for the fragmentation of files. It calculates the source blocks from the source files.
  • Symbol Encoding algorithm: The symbol encoding algorithm is used for the fragmentation of files. It calculates encoding symbols from source blocks for Compact No-Code FEC. It may also be used for other FEC schemes.
  • Congestion Control Building Block: A building block used to limit congestion by using congestion feedback, rate regulation and receiver controls (RFC 3048).
  • Content Encoding for FDT Instances: FDT Instance may be content encoded for more efficient transport, e.g. using GZIP.
  • Content Encoding for any other file than FDT Instances: Files may be content encoded for more efficient transport, e.g. using GZIP.
  • A flag: The Close Session flag for indicating the end of a session to the receiver in the ALC/LCT header. See the Note at the end of this Annex.
  • B flag: The Close Object flag is for indicating the end of an object to the receiver in the ALC/LCT header.
  • T flag: The T flag is used to indicate the use of the optional "Sender Current Time (SCT)" field (when T=1) in the ALC/LCT header.
  • R flag: The R flag is used to indicate the use of the optional "Expected Residual Time (ERT)" field in the ALC/LCT header.
  • Content Location attribute: This attribute provides a URI for the location where a certain piece of content (or file) being transmitted in a FLUTE session is located.
  • Transport Object Identifier (TOI): The TOI uniquely identifies the object within the session from which the data in the packet was generated.
  • FDT Expires attribute: Indicates to the receiver the time until which the information in the FDT is valid.
  • Complete attribute: This may be used to signal that the given FDT Instance is the last FDT Instance to be expected on this file delivery session.
  • FEC-OTI-Maximum-Source-Block-Length: This parameter indicates the maximum number of source symbols per source block.
  • FEC-OTI-Encoding-Symbol-Length: This parameter indicates the length of the Encoding Symbol in bytes.
  • FEC-OTI-Max-Number-of-Encoding-Symbols: This parameter indicates the maximum number of Encoding Symbols that can be generated for a source block.
  • FEC-OTI-FEC-Instance-ID: This field is used to indicate the FEC Instance ID, if a FEC scheme is used.
  • FEC-OTI-Scheme-Specific-Info: Carries Object Transmission Information which is specific to the FEC scheme in use.
Up

Up   Top   ToC