Content for TS 26.347 Word version: 18.1.0

0 Introduction p. 11

The present document has been created as part of the MBMS Transport Protocol and API (TRAPI) work item and is based on the conclusions of TR 26.852 in order to provide application-friendly methods and interfaces to access 3GPP MBMS User services. The present document is primarily targeted for developers of web and user applications and attempts to abstract complex MBMS procedures in simple methods and interfaces. MBMS Client vendors can implement this API and URL to simplify the integration of MBMS User Services.

1 Scope p. 12

The present document provides application methods and interfaces between an MBMS-aware application and the UE MBMS Client to access 3GPP MBMS User services. The purpose of the document is the definition of enablers in order to simplify the usage of MBMS in web-centric as well as app-based service environments.

The present document defines several APIs to access MBMS User Services and URLs to access resources available as part of an MBMS User Service. The MBMS User Services are defined in TS 26.346 and are not part of the present document.

2 References p. 12

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 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".

[6]

TR 26.852: "Multimedia Broadcast/Multicast Service (MBMS); Extensions and profiling".

[7]

TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".

[8]

RFC 9112: "HTTP/1.1".

[9]

Object Management Group: "Interface Definition Language™ (IDL™) 4.0".

[10]

RFC 3066: "Tags for the Identification of Languages".

[11]

RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".

[12]

TS 29.116: "Representational state transfer over xMB reference point between content provider and BM-SC".

[13]

RFC 7595: "Guidelines and Registration Procedures for URI Schemes".

[14]

RFC 7230: " Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".

[15]

RFC 7553: "The Uniform Resource Identifier (URI) DNS Resource Record"

[16]

RFC 6335: "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry"

[17]

TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".

[18]

TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation".

[19]

TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception".

[20]

TS 24.116: "Stage 3 aspects of system architecture enhancements for TV services".

[21]

TS 26.510: "Media delivery; interactions and APIs for provisioning and media session handling".

3 Definitions and abbreviations p. 13

3.1 Definitions p. 13

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

Application Feature Enhanced Service:

An end-user service for which all associated resources are delivered through more than one MBMS User Service.

MBMS Application User Service:

An end-user service for which all associated resources are delivered through an MBMS User Service via broadcast and/or unicast bearers and which is accessible through the MBMS-API.

MBMS-API:

An Application Programming Interface between the MBMS Client and the MBMS-Aware application for a specific Application User Service.

MBMS-aware Application:

An application in the user space that communicates with the MBMS client through APIs as defined in the present document.

MBMS Client:

A function that implements functionalities defined in TS 26.346 and provides APIs and protocol-related methods to expose relevant functionalities to an MBMS-aware application.

MBMS-URL:

A Universal Resource Locator that enables a general application to access resources delivered through an MBMS User Service using the MBMS URL handler.

MBMS-URL Handler:

A logical function that translates the MBMS-URL to a sequence of MBMS-API calls in order to provide resources delivered by MBMS User Services to a general application.

3.2 Abbreviations p. 13

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

API

Application Programming Interface

DANE

DASH-Aware Network Element

DASH

Dynamic Adaptive Streaming over HTTP

IDL

Interface Definition Language

JSON

JavaScript Object Notation

HLS

HTTP live Streaming

MAA

MBMS-Aware Application

MPD

Media Presentation Description

SAND

Server and Network Assisted DASH

SDP

Session Description Protocol

USD

User Service Description

URL

Universal Resource Locator