ETSI TS 126 348 V16.3.0 (2020-11)

ETSI TS 126 348 V16.3.0 (2020-11)
TECHNICAL SPECIFICATION
LTE;
5G;
Northbound Application Programming Interface (API)
for Multimedia Broadcast/Multicast Service (MBMS)
at the xMB reference point
(3GPP TS 26.348 version 16.3.0 Release 16)
---------------------- Page: 1 ----------------------
3GPP TS 26.348 version 16.3.0 Release 16 1 ETSI TS 126 348 V16.3.0 (2020-11)
Reference
DTS/TSGS-0426348vg30
Keywords
5G,LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or

print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any

existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI

deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.

Users of the present document should be aware that the document may be subject to revision or change of status.

Information on the current status of this and other ETSI documents is available at

If you find errors in the present document, please send your comment to one of the following services:

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying

The content of the PDF version shall not be modified without the written authorization of ETSI.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and

oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and

IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information

pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found

in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in

respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee

can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.

ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no

right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does

not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).

The present document may refer to technical specifications or reports using their 3GPP identities. These shall be

The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.

In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and

"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

Intellectual Property Rights ................................................................................................................................ 2

Legal Notice ....................................................................................................................................................... 2

Modal verbs terminology .................................................................................................................................... 2

Foreword ............................................................................................................................................................. 5

Introduction ........................................................................................................................................................ 5

1 Scope ........................................................................................................................................................ 6

2 References ................................................................................................................................................ 6

3 Definitions and abbreviations ................................................................................................................... 7

3.1 Definitions .......................................................................................................................................................... 7

3.2 Abbreviations ..................................................................................................................................................... 7

4 Architecture .............................................................................................................................................. 7

4.1 General ............................................................................................................................................................... 7

4.2 xMB reference point ........................................................................................................................................... 8

5 Procedure .................................................................................................................................................. 9

5.1 General ............................................................................................................................................................... 9

5.2 Authentication and Authorization ...................................................................................................................... 9

5.2.1 Introduction................................................................................................................................................... 9

5.2.2 Authentication Procedure ........................................................................................................................... 10

5.2.3 Authorization Procedure ............................................................................................................................. 10

5.3 Service Management Procedures ..................................................................................................................... 11

5.3.1 Introduction................................................................................................................................................. 11

5.3.2 Create Service ............................................................................................................................................. 11

5.3.3 Get Service Properties ................................................................................................................................ 12

5.3.4 Update Service Properties ........................................................................................................................... 12

5.3.5 Terminate a Service .................................................................................................................................... 12

5.3.6 Service Notifications................................................................................................................................... 13

5.3.7 List of Service Properties ............................................................................................................................ 13

5.4 Session Management Procedures ..................................................................................................................... 16

5.4.1 Introduction................................................................................................................................................. 16

5.4.2 Create Session ............................................................................................................................................. 16

5.4.3 Get Session Properties ................................................................................................................................ 17

5.4.4 Update Session Properties .......................................................................................................................... 17

5.4.5 Terminate a Session .................................................................................................................................... 18

5.4.6 Session Properties ....................................................................................................................................... 18

5.4.7 Geographical area for mission critical services .......................................................................................... 31

5.5 User Plane Procedures ...................................................................................................................................... 31

5.5.1 Introduction................................................................................................................................................. 31

5.5.2 File Distribution .......................................................................................................................................... 32

5.5.3 RTP Streaming ............................................................................................................................................ 32

5.5.4 Transport ..................................................................................................................................................... 32

5.5.5 Notification Messages................................................................................................................................. 32

5.6 File Delivery Manifest ...................................................................................................................................... 33

5.6.1 General ........................................................................................................................................................ 33

5.6.2 File Delivery Manifest ................................................................................................................................ 33

5.6.3 JSON Schema for File Delivery Manifest .................................................................................................. 35

Annex A (informative): xMB User Plane (xMB-U) ............................................................................. 38

A.0 General ................................................................................................................................................... 38

A.1 Generic File Delivery ............................................................................................................................. 38

A.1.1 Introduction ...................................................................................................................................................... 38

A.1.2 File ingestion with Pull ..................................................................................................................................... 38

A.1.3 File ingestion with Push ................................................................................................................................... 40

A.2 DASH Media Presentation Delivery ...................................................................................................... 41

A.2.1 Introduction ...................................................................................................................................................... 41

A.2.2 DASH Content ingestion with Pull .................................................................................................................. 42

A.2.3 DASH Content ingestion with Push ................................................................................................................. 44

A.3 MBMS Streaming (with RTP) ............................................................................................................... 45

A.4 Transparent Delivery .............................................................................................................................. 46

A.5 HLS Media Presentation Delivery .................................................................................................................... 48

A.5.1 Introduction ...................................................................................................................................................... 48

A.5.2 Segment and Playlist Order Guarantee ............................................................................................................. 48

A.5.3 HLS Content Ingestion with Pull ..................................................................................................................... 48

A.5.3.1 Introduction ........................................................................................................................................... 48

A.5.3.2 Content ingestion steps ......................................................................................................................... 48

A.5.4 HLS Content Ingestion with Push .................................................................................................................... 49

A.5.4.1 Introduction ........................................................................................................................................... 49

A.5.4.2 Content ingestion steps ......................................................................................................................... 49

Annex B (informative): Change history ............................................................................................... 50

History .............................................................................................................................................................. 51

This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal

TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an

Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,

z the third digit is incremented when editorial only changes have been incorporated in the document.

The present document defines a northbound interface between the BM-SC and the content provider. The interface is

called xMB. Both external (3rd party) content providers and 3GPP defined API invokers e.g. GCS AS can use the xMB

The xMB reference point supports different session types, such as generic file delivery e.g. for MCData, application

streaming, including DASH streaming, RTP ingest and ingest for transparent delivery. The xMB reference point

supports unicast delivery of content, e.g. for devices outside of the MBMS coverage area.

The xMB reference point is fully integrated into the Common API Framework for 3GPP Northbound APIs (CAPIF).

The present document provides interaction methods and interfaces between a BM-SC and a content provider. The

purpose of the document is the definition of enablers for the usage of MBMS delivery.

The following documents contain provisions which, through reference in this text, constitute provisions of the present

- References are either specific (identified by date of publication, edition number, version number, etc.) or

- 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

[2] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".

[3] 3GPP TS 26.234: "Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols

[4] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive

[5] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".

[6] IETF RFC 6347: "Datagram Transport Layer Security Version 1.2", E. Rescorla, N. Modadugu.

[7] IETF RFC 4918: "HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)",

[9] IETF RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP,

[11] IETF Internet-Draft: "JSON Schema: A Media Type for Describing JSON Documents", draft-

[12] 3GPP TS 23.280, "Common functional architecture to support mission critical services; Stage 2".

[13] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting

[14] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2

[15] IETF RFC 5234 (January 2008): "Augmented BNF for Syntax Specifications: ABNF", D. Crocker

[16] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional

For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following

apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP

For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An

abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in

As shown in Figure 4.1-1, the reference point between Content Provider and BM-SC is called the xMB interface. Using

the xMB reference point, content provider can invoke procedures supported by BM-SC(s) to setup and manage MBMS

user service from BM-SC to the MBMS clients. BM-SC defines an endpoint with all supported procedures on the xMB

interface, which can then be converted to SGmb procedures for the interface between BM-SC and MBMS GW (not

The BM-SC may forward the received content for unicast delivery for appropriate functions (e.g., MBMS user service

The control plane (xMB-C) and the user plane (xMB-U) may be optionally terminated by 3GPP defined enabler /

exposure functions such as an SCEF, which exposes the same or a different interface to content providers. The exposed

The content provider may optionally exchange application level information like service metadata (e.g. serviceIds or

- the BM-SC shall support the CAPIF API provider domain functions (i.e. CAPIF-2/2e (xMB), CAPIF-3, CAPIF-

- the BM-SC xMB authentication and authorization functions (as defined in Clause 5.2) are replaced by CAPIF

The CAPIF and associated API provider domain functions are specified in TS 23.222 [10].

The content provider may be a mission critical service provider ([12]), which is arranging MC Services to Mission

Critical Organizations. Providing MC Services may require additional control of the resource allocation (QoS, coverage

area). For this purpose, the interface can be extended with the xMB mission critical extension. The xMB mission critical

The xMB reference point exists between the content provider and the BM-SC directly or via 3GPP defined enabler /

exposure functions such as SCEF. When the BM-SC connects to content provider via a 3GPP defined enabler /

exposure function, the xMB-C interface (and optionally also the xMB-U) is terminated at the 3GPP defined enabler /

The xMB reference point shall support security function for confidentiality protection of both control plane (xMB-C)

The xMB reference point defines procedures between a BM-SC and a content provider. The content provider may be

By default the BM-SC announces all the services including the different eMBMS parameters to MBMS Clients so that

MBMS Clients can activate reception of the announced MBMS services. It is also possible that the Content Provider

- Streaming: the BM-SC may use the MBMS Streaming delivery method for content distribution to MBMS

- Files: the BM-SC may use the MBMS Download delivery method for content distribution to MBMS Clients

- Application: the BM-SC may use the MBMS Download delivery method for content distribution to MBMS

- Transport-Mode: the BM-SC is transparent to the stream and passed data via MBMS bearers to UEs.

The content provider and the BM-SC shall follow the procedures in this clause for authentication and authorization over

When the content provider (API invoker) uses CAPIF to discover the BM-SC (xMB provider) and to interact with the

BM-SC, then the xMB security procedures (as defined in this clauses) are replaced by CAPIF-1 / CAPIF-1e [10]

Before provisioning of services at the BM-SC, the content provider has to be authenticated and authorized to perform

service management functions using xMB. If the content provider wants to modify or remove the provisioned services,

The content provider may have multiple and different end-points for xMB-C and xMB-U. Each connection may have

different entitlements based on the roles assigned to the requesting connecting party.

While authentication is performed based on standard (D)TLS connection and certificate exchange, authorization is

performed using either the "domain-based" or "user-based" mode as described in clause 5.2.3.

In the user-based mode, fine-grained authorization shall be performed prior to any transaction to allow the BM-SC to

check the access rights of the content provider user (either a human or a machine). Such authorization procedure, if

successful, shall result in the creation of an "access token" that the server will return to the content provider for

In the domain-based mode, additional authorization steps shall not be performed. Users within a content provider

The authentication procedure is used by the content provider and the BM-SC to authenticate each other. The content

provider shall be authenticated with the BM-SC when the content provider wants to provision new services or manage

existing services. Similarly, the BM-SC shall be authenticated by the content provider when the BM-SC needs to send

reports and notifications to the content provider. Authentication is also required for all user plane procedures.

Figure 5.2-1 shows the authentication procedure used between the content provider and the BM-SC.

1. The content provider and the BM-SC authenticate each other for performing service management and status

reporting and notification respectively. During this authentication step, the content provider and BM-SC

exchange their X.509 certificates using TLS as defined in TS 33.310 [5] and independently verify the validity of

Before using any of the MBMS xMB procedure, the Content Provider shall first use the fol