Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 26.346  Word version:  17.2.1

Top   Top   None   None   Next
0…   4…   5…   7…   8…   8A…   9…   10…   11…   A…   D…   K…

 

0  Introductionp. 13

MBMS is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients. Transmitting the same data to multiple recipients allows network resources to be shared.
The MBMS bearer service offers two modes:
  • Broadcast Mode.
  • Multicast Mode.
MBMS user services can be built on top of the MBMS bearer service. Further, the MBMS User Services may use other UMTS bearer services to deliver data. The present document specifies four delivery methods for the MBMS user services: download, streaming, GC, and Transparent. Examples of applications using the download delivery method are news and software upgrades. Delivery of live music is an example of an application using the streaming delivery method. Transparent delivery method allows the distribution of generic IP applications over MBMS bearers.
There can be several MBMS user services. The objective of the present document is the definition of a set of media codecs, formats and transport/application protocols to enable the deployment of MBMS user services. The present document takes into consideration the need to maximize the reuse of components of already specified services like PSS and MMS.
Up

1  Scopep. 14

The present document defines a set of media codecs, formats and transport/application protocols to enable the deployment of MBMS user services either over the MBMS bearer service or other UMTS Bearer Services within the 3GPP system.
In this version of the specification, only MBMS download and streaming delivery methods are specified. The present document does not preclude the use of other delivery methods.
The present document includes information applicable to network operators, service providers and manufacturers.
Up

2  Referencesp. 14

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.146: "Multimedia Broadcast/Multicast Service; Stage 1".
[3]
TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1".
[4]
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[5]
TS 25.346: "Introduction of Multimedia Broadcast/Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
[6]
RFC 3550  / STD 0064 (July 2003): "RTP: A Transport Protocol for Real-Time Applications", H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson.
[7]
RFC 0768  / STD 0006 (August 1980): "User Datagram Protocol", J. Postel.
[8]
RFC 0791  / STD 0005 (September 1981): "Internet Protocol", J. Postel.
[9]
RFC 3926  (October 2004): "FLUTE - File Delivery over Unidirectional Transport", T. Paila, M. Luby, R. Lehtonen, V. Roca, R. Walsh.
[10]
RFC 3450  (December 2002): "Asynchronous Layered Coding (ALC) Protocol Instantiation", M. Luby, J. Gemmell, L. Vicisano, L. Rizzo, J. Crowcroft.
[11]
RFC 3451  (December 2002): "Layered Coding Transport (LCT) Building Block", M. Luby, J. Gemmell, L. Vicisano, L. Rizzo, M. Handley, J. Crowcroft.
[12]
RFC 5052  (August 2007): "Forward Error Correction (FEC) Building Block", M. Luby, M. Watson, L. Vicisano.
[13]
RFC 3695  (February 2004): "Compact Forward Error Correction (FEC) Schemes", M. Luby, L. Vicisano.
[14]
RFC 4566  (July 2006): "SDP: Session Description Protocol", M. Handley, V. Jacobson and C. Perkins.
[15]
RFC 4570  (July 2006): "Session Description Protocol (SDP) Source Filters", B. Quinn, R. Finlayson.
[16]  Void.
[17]
RFC 3048  (January 2001): "Reliable Multicast Transport Building Blocks for One-to-Many Bulk-Data Transfer", B. Whetten, L. Vicisano, R. Kermode, M. Handley, S. Floyd, M. Luby.
[18]
RFC 2616  (June 1999): "Hypertext Transfer Protocol -- HTTP/1.1".
[19]
RFC 3986  / STD 0066 (January 2005): "Uniform Resource Identifier (URI)".
[20]
TS 33.246: "3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS)".
[21]
OMG: "Unified Modeling Language (UML), version 1.5" (formal/03-03-01).
[22]
W3C Recommendation 28 October 2004: "XML Schema Part 2: Datatypes Second Edition".
[23]
RFC 5234  (January 2008): "Augmented BNF for Syntax Specifications: ABNF", D. Crocker and P. Overell.
[24]
TS 26.290: "Audio codec processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec; Transcoding functions".
[25]
TS 26.304: "Floating-point ANSI-C code for the Extended Adaptive Multi-Rate - Wideband (AMR-WB+) codec".
[26]
TS 26.273: "Speech codec speech processing functions; Extended Adaptive Multi-Rate - Wideband (AMR-WB+) speech codec; Fixed-point ANSI-C code".
[27]  Void.
[28]
TS 26.401: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; General description".
[29]
TS 26.410: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Floating-point ANSI-C code".
[30]
TS 26.411: "General audio codec audio processing functions; Enhanced aacPlus general audio codec; Fixed-point ANSI-C code".
[31]
W3C Recommendation 04 February 2004: "Extensible Markup Language (XML) 1.1", T. Bray, J. Paoli, C. Sperberg-McQueen, E. Maler, F. Yergeau and J. Cowan.
[32]
TS 26.244: "Transparent end-to-end streaming service; 3GPP file format (3GP)".
[33]
RFC 4867  (April 2007): "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs", J. Sjoberg, M. Westerlund, A. Lakaniemi, Q. Xie.
[34]
RFC 4352  (January 2006): "RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio Codec", Sjoberg J. et al.
[35]
RFC 6184  (2011): "RTP Payload Format for H.264 Video", Y.-K. Wang, R. Even, T. Kristensen, R. Jesup.
[36]  Void.
[37]
RFC 2557  (March 1999): "MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)", J. Palme, A. Hopmann, N. Shelness.
[38]
RFC 3890  (September 2004): "A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)", M. Westerlund.
[39]
RFC 3556  (July 2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth", S. Casner.
[40]
TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[41]
RFC 3640  (November 2003): "RTP Payload Format for Transport of MPEG-4 Elementary Streams", J. van der Meer, D. Mackie, V. Swaminathan, D. Singer, P. Gentric.
[42]
RFC 1952  (May 1996): "GZIP file format specification version 4.3", P. Deutsch.
[43]
ITU-T Recommendation H.264 (04/2013): "Advanced video coding for generic audiovisual services".
[44]  Void.
[45]  Void
[46]  Void .
[47]
TS 26.234: "Transparent end-to-end streaming service; Protocols and codecs".
[48]
TS 26.071: "AMR speech codec; General description".
[49]
TS 26.090: "AMR speech codec; Transcoding functions".
[50]
TS 26.073: "AMR speech Codec; C-source code".
[51]
TS 26.104: "ANSI-C code for the floating-point Adaptive Multi-Rate (AMR) speech codec".
[52]
TS 26.171: "AMR speech codec, wideband; General description".
[53]
TS 26.190: "Mandatory Speech Codec speech processing functions AMR Wideband speech codec; Transcoding functions".
[54]
TS 26.173: "ANCI-C code for the Adaptive Multi Rate - Wideband (AMR-WB) speech codec".
[55]
TS 26.204: "ANSI-C code for the floating-point Adaptive Multi-Rate Wideband (AMR-WB) speech codec".
[56]
Scalable Polyphony MIDI Specification Version 1.0: RP-34, MIDI Manufacturers Association, Los Angeles, CA, February 2002.
[57]
Scalable Polyphony MIDI Device 5-to-24 Note Profile for 3GPP Version 1.0: RP-35, MIDI Manufacturers Association, Los Angeles, CA, February 2002.
[58]
"Standard MIDI Files 1.0": RP-001, in "The Complete MIDI 1.0 Detailed Specification, Document Version 96.1", The MIDI Manufacturers Association, Los Angeles, CA, USA, February 1996.
[59]
Mobile DLS: MMA specification v1.0, RP-41 Los Angeles, CA, USA. 2004.
[60]
Mobile XMF Content Format Specification: MMA specification v1.0, RP-42, Los Angeles, CA, USA. 2004.
[61]
ITU-T Recommendation T.81 (1992) | ISO/IEC 10918-1:1993: "Information technology - Digital compression and coding of continuous-tone still images - Requirements and guidelines".
[62]
C-Cube Microsystems (September 1992): "JPEG File Interchange Format", Version 1.02.
[63]
CompuServe Incorporated (1987): "GIF Graphics Interchange Format: A Standard defining a mechanism for the storage and transmission of raster-based graphics information", Columbus, OH, USA. See at http://www.dcs.ed.ac.uk/home/mxr/gfx/2d/GIF87a.txt.
[64]
CompuServe Incorporated (1990): "Graphics Interchange Format: Version 89a", Columbus, OH, USA.
[65]
RFC 2083  (March 1997): "PNG (Portable Networks Graphics) Specification Version 1.0", T. Boutell.
[66]
W3C Working Draft 27 October 2004: "Scalable Vector Graphics (SVG) 1.2", http://www.w3.org/TR/2004/WD-SVG12-20041027/.
[67]
W3C Working Draft 13 August 2004: "Mobile SVG Profile: SVG Tiny, Version 1.2", http://www.w3.org/TR/2004/WD-SVGMobile12-20040813/.
[68]
Standard ECMA-327 (June 2001): "ECMAScript 3rd Edition Compact Profile".
[69]  Void.
[70]
ISO/IEC 10646-1 (2000): "Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane".
[71]
The Unicode Consortium: "The Unicode Standard", Version 3.0 Reading, MA, Addison-Wesley Developers Press, 2000, ISBN 0-201-61633-5.
[72]
TS 26.245: "Transparent end-to-end Packet switched Streaming Service (PSS); Timed text format".
[73]
RFC 4646:  "Tags for the Identification of Languages".
[74]
ISO 639: "Codes for the representation of names of languages".
[75]
ISO 3166: "Codes for the representation of names of countries and their subdivisions".
[76]  Void.
[77]
TS 23.003: "Numbering, addressing and identification".
[78]
RFC 5905,  "Network Time Protocol Version 4: Protocol and Algorithms Specification", D. Mills, J. Martin, J. Burbank and W. Kasch, June 2010.
[79]
[80]
RFC 3711  (March 2004): "The Secure Real-time Transport Protocol (SRTP)", M. Baugher, D. McGrew, M. Naslund, E. Carrara, K. Norrman.
[81]  Void.
[82]
RFC 4648:  "The Base16, Base32, and Base64 Data Encodings", Josefsson S., Ed., October 2006.
[83]
RFC 3023:  "XML Media Types", M. Murata, S. St.Laurent, D. Kohn, January 2001.
[84]
RFC 5905:  "Network Time Protocol Version 4: Protocol and Algorithms Specification", D. Mills, June 2010.
[85]
OMA OMNA Registered PUSH Application ID list: http://www.openmobilealliance.org/tech/omna/omna-push-app-id.htm
[86]
TR 26.936: "Performance characterization of 3GPP audio codecs".
[87]
TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".
[88]
RFC 2326:  "Real Time Streaming Protocol (RTSP)", Schulzrinne H., Rao A. and Lanphier R., April 1998.
[89]  Void.
[90]
"Service Guide for Mobile Broadcast Services": Open Mobile Alliance, OMA-TS-BCAST_ServiceGuide-V1_1, Candidate Version 1.1 -14 Sep 2010.
[91]
RFC 5053  (October 2007): "Raptor Forward Error Correction Scheme for Object Delivery", M. Luby, A. Shokrollahi, M. Watson, T. Stockhammer.
[92]
RFC 5285:  "A General Mechanism for RTP Header Extensions", D. Singer, H. Desineni, July 2008.
[93]
RFC 4396:  "RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text", Rey J. and Matsui Y., February 2006.
[94]
OMA-ERELD-DM-V1_2-20070209-A: "Enabler Release Definition for OMA Device Management, Approved Version 1.2".
[95]
TS 26.430: "Timed Graphics".
[96]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[97]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[98]
TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[99]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[100]
RFC 6064:  "SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming Service and Multimedia Broadcast/Multicast Service", M. Westerlund, P. Frojdh, January 2011.
[101]  Void.
[102]  Void.
[103]  Void.
[104]
TS 36.443: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M2 Application Protocol (M2AP)".
[105]
TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
[106]
RFC 6681,  "Raptor FEC Schemes for FECFRAME," M. Watson, T. Stockhammer and M. Luby, August 2012.
[107]
RFC 6363,  "Forward Error Correction (FEC) Framework," M. Watson, A. Begen and V. Roca, October 2011.
[108]
TS 36.304: "User Equipment (UE) procedures in idle mode".
[109]
"Mobile Location Protocol (MLP)": Open Mobile Alliance, OMA-LIF-MLP-V3_1, Approved Version 3.1 - 20 Sep 2011.
[110]
TR 26.946: "Multimedia Broadcast/Multicast Service (MBMS); User service guidelines".
[111]  Void.
[112]
ITU-T Recommendation H.265 (04/2013): "High efficiency video coding".
[113]
RFC 7798  (2016): "RTP Payload Format for High Efficiency Video Coding (HEVC)", Y.-K. Wang, Y. Sanchez, T. Schierl, S. Wenger, M. M. Hannuksela.
[114]
RFC 1035  (November 1987): "Domain Names - Implementation and Specification", P. Mockapetris.
[115]
TR 26.906: Evaluation of HEVC for 3GPP Services (Release 12).
[116]
ISO/IEC 23009-1: 2019/Amd.1:2020: Information technology -- Dynamic adaptive streaming over HTTP (DASH) -- Part 1: Media presentation description and segment formats.
[117]
TS 29.214: "Policy and charging control over Rx reference point".
[118]
TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[119]
RFC 5651:  "Layered Coding Transport (LCT) Building Block", M. Luby, M. Watson, L. Vicisano.
[120]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[121]
TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[122]
TS 23.179: "Functional architecture and information flows for mission critical communication, services; Stage 2".
[123]
TS 24.379: "Mission Critical Push to Talk (MCPTT) call control Protocol specification".
[124]
TS 26.307: "Presentation Layer for 3GPP Services".
[125]
TS 26.116: "Television (TV) over 3GPP Services; Video Profiles".
[126]
Standard ECMA-262: 5.1 Edition / June 2011, ECMAScript Language Specification.
[127]
RFC 6347  (January 2012): "Datagram Transport Layer Security Version 1.2".
[128]
TS 33.310: Network Domain Security (NDS); Authentication Framework (AF)
[129]
TS 29.116: "Representational state transfer over xMB reference point between Content Provider and BM-SC".
[130]
draft-wright-json-schema-01  "JSON Schema: A Media Type for Describing JSON Documents", April 15, 2017.
[131]
TS 24.116: "Stage 3 aspects of system architecture enhancements for TV services".
[132]
TS 24.117: "TV service configuration Management Object (MO)".
[133]
[134]
[135]
IANA Service Name and Transport Protocol Port Number Registry: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml.
[136]
TS 26.347: "Multimedia Broadcast/Multicast Service (MBMS); Application Programming Interface and URL".
[137]
RFC 5795:  "The Robust Header Compression (ROHC) Framework".
[138]
RFC 3095:  "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed".
[139]
RFC 5225:  RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite
[140]
TS 26.118: "3GPP Virtual reality profiles for streaming applications".
[141]
TS 23.180: "Common functional architecture to support mission critical services; Stage 2".
[142]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[143]
TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[144]
RFC 8216:  "HTTP Live Streaming"
[145]
ISO/IEC 23000-19:2019: "Information Technology Multimedia Application Format (MPEG-A) - Part 19: Common Media Application Format (CMAF) for segmented media".
[146]
TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation".
[147]
TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception".
[148]
ETSI TS 103 720: "5G Broadcast System for linear TV and radio services; LTE-based 5G terrestrial broadcast system".
[149]
TR 36.976: "Overall description of LTE-based 5G broadcast".
[150]
TS 26.511: "5G Media Streaming (5GMS); 5G Media Streaming (5GMS); Profiles, codecs and formats".
[151]
TS 26.512: "5G Media Streaming (5GMS); Protocols".
[152]
RFC 6335:  "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry".
[153]
IANA (Internet Assigned Numbers Authority): "IPv4 Multicast Address Space Registry", https://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml.
[154]
IANA (Internet Assigned Numbers Authority): "IPv6 Multicast Address Space Registry", https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-addresses.xhtml.
Up

3  Definitions and abbreviationsp. 20

3.1  Definitionsp. 20

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply:
Application content component:
An individual content component of an MBMS User Service, such as a video or audio media stream, or a non-real-time file, delivered by an MBMS transport session, and is available to and can be used by the MBMS application.
Application Service:
An end-user service for which the entry point document is contained in the User Service Description and whereby all associated content components are delivered through one or more MBMS User Services via broadcast and/or unicast bearers.
Broadcast session:
See TS 22.146.
Forward Error Correction (FEC):
in the context of MBMS, a FEC mechanism is used at the application layer to allow MBMS receivers to recover lost SDUs.
FLUTE channel:
equivalent to an ALC/LCT channel. An ALC/LCT channel is defined by the combination of a sender and an address associated with the channel by the sender (RFC 3926).
Frame-packed stereoscopic 3D video:
a video consisting of two views in which both views were packed into a single stream before compression.
Hybrid DASH/HLS service:
a media streaming service which can be consumed both by DASH clients and HLS clients.
Multicast joining:
See TS 22.146.
Multicast session:
See TS 22.146.
Multimedia Broadcast/Multicast Service (MBMS):
See TS 22.146.
MBMS application:
The application which resides in or interfaces with the UE, and which provides to the end-user an application service by using one or more application content components of one or more MBMS User Services.
MBMS over a Single Frequency Network:
See TS 25.346.
MBMS User Service:
The transport-level service, comprising one or more application content components, delivered by the MBMS bearer service across one or more Broadcast and/or Multicast sessions, and/or delivered by the unicast bearer service. The application content components of the MBMS User Service, in part or in whole, are provided to the MBMS application. See TS 22.246.
MBMS user service discovery/announcement:
user service discovery refers to methods for the UE to obtain the list of available MBMS user services along with information on the user service and the user service announcement refers to methods for the MBMS service provider to make the list of available MBMS user services along with information on the user service available to the UE.
MBMS user service initiation:
UE mechanisms to setup the reception of MBMS user service data. The initiation procedure takes place after the discovery of the MBMS user service.
MBMS delivery method:
mechanism used by a MBMS user service to deliver content. An MBMS delivery method uses MBMS bearers in delivering content and may make use of associated procedures.
MBMS download delivery method:
delivery of discrete objects (e.g. files) by means of a MBMS download session.
MBMS group communication delivery method:
delivery of group communication service data by means of the BM-SC ingesting UDP/IP packets from a group communications server and forwarding them over the MBMS path provided by the MBMS Bearer Service.
MBMS streaming delivery method:
delivery of continuous media (e.g. real-time video) by means of a MBMS streaming session.
MBMS Transparent delivery method:
transparent delivery of application data by means of an MBMS Transparent session.
MBMS download session:
time, protocols and protocol state (i.e. parameters) which define sender and receiver configuration for the download of content files.
MBMS streaming session:
time, protocols and protocol state (i.e. parameters) which define sender and receiver configuration for the streaming of content.
MBMS Transparent session:
time, area, protocols, and protocol state (i.e. parameters) which define sender and receiver configuration for the transparent delivery of application data flows.
Partial-File-Accept Request:
HTTP GET request that includes a partial-accept header in the HTTP request header.
Receive Only Mode:
See TS 23.246.
Receive-Only-Mode (ROM) service:
A type of eMBMS broadcast service receivable by a UE configured in Receive Only Mode. A TMGI associated with a ROM service shall contains a standardized [MCC+MNC] value. See Annex E of TS 23.246 and TS 24.116 for further details on Receive Only Mode.
RTP Session:
The RTP and RTCP traffic sent to a specific IP multicast address and port pair (one port each for RTP and RTCP) during the time period the session is specified to exist. An RTP session is used to transport a single media type (e.g. audio, video, or text). An RTP session may contain several different streams of RTP packets using different SSRCs.
Stereoscopic 3D video:
a video bitstream consisting of two views.
Unicast Bearer Service:
Synonymously used as the term "UMTS Bearer Services with interactive and/or streaming traffic classes".
Up

3.2  Abbreviationsp. 22

For the purposes of the present document, abbreviations given in TR 21.905 and the following apply:
ADPD
Associated Delivery Procedure Description
ADU
Application Data Unit
ALC
Asynchronous Layered Coding
API
Application Programming Interface
AS
Application Server
ASD
Application Service Description
AVC
Advanced Video Coding
BM-SC
Broadcast-Multicast - Service Centre
CC
Congestion Control
CPB
Coding Picture Buffer
CVS
Coded Video Sequence
DASH
Dynamic Adaptive Streaming over HTTP
ERT
Expected Residual Time
ESI
Encoding Symbol ID
FDT
File Delivery Table
FLUTE
File deLivery over Unidirectional Transport
FMT
Feedback Message Type
GCS
Group Communication Service
GCSE
Group Communication Service Enabler
HDR
High Dynamic Range
HDTV
High-DefinitionTeleVision
HEVC
High Efficiency Video Coding
HLS
HTTP Live Streaming
IANA
Internet Assigned Numbers Authority
IDR
Instantaneous Decoding Refresh
IRAP
Intra Random Access Point
ISD
Initialization Segment Description
LCT
Layered Coding Transport
LI
Leap Indicator
MBMS SAI
MBMS Service Area Identity
MCPTT
Mission Critical Push to Talk
MIME
Multipurpose Internet Mail Extensions
MMS
Multimedia Messaging Service
MooD
MBMS operation on Demand
MPD
Media Presentation Description
MSK
MBMS Service Key
MTK
MBMS Traffic Key
MUK
MBMS User Key
NAL
Network Abstraction Layer
NTP
Network Time Protocol
OMNA
Open Mobile Naming Authority
PAC
Proxy Auto-Config
PSS
Packet-switched Streaming Service
PTT
Push To Talk
RASL
Random Access Skipped Leading picture
ROM
Receive-Only-Mode
SA File
Service Announcement File
SACH
Service Announcement CHannel
SBN
Source Block Number
SCT
Sender Current Time
SEI
Supplemental Enhancement Information
SNTP
Simple Network Time Protocol
TMGI
Temporary Mobile Group Identity
TOI
Transport Object Identifier
TSI
Transport Session Identifier
UHD
Ultra High Definition
URL
Uniform Resource Locator
USBD
User Service Bundle Description
USD
User Service Description
UTC
Universal Time Coordinated
VCL
Video Coding Layer
VR
Virtual Reality
Up

Up   Top   ToC