ETSI TS 129 581 V17.7.0 (2026-04)

5G; 5G System; Multicast/Broadcast Service Transport Services; Stage 3 (3GPP TS 29.581 version 17.7.0 Release 17)

RTS/TSGC-0429581vh70

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Completion Date: 02-Apr-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System;
Multicast/Broadcast Service Transport Services;
Stage 3
(3GPP TS 29.581 version 17.7.0 Release 17)


3GPP TS 29.581 version 17.7.0 Release 17 1 ETSI TS 129 581 V17.7.0 (2026-04)

Reference
RTS/TSGC-0429581vh70
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
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 on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 2 ETSI TS 129 581 V17.7.0 (2026-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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 server) which are, or may be, or may become,
essential to the present document.
Trademarks
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.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
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
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
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
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 3 ETSI TS 129 581 V17.7.0 (2026-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 8
2 References . 8
3 Definitions, symbols and abbreviations . 9
3.1 Definitions . 9
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Overview . 9
4.1 General . 9
5 Services offered by the MBSTF . 10
5.1 Introduction . 10
5.2 Nmbstf_MBSDistributionSession Service . 10
5.2.1 Service Description . 10
5.2.2 Service Operations . 11
5.2.2.1 Introduction . 11
5.2.2.2 Create . 11
5.2.2.2.1 General . 11
5.2.2.3 Update . 12
5.2.2.3.1 General . 12
5.2.2.4 Destroy . 12
5.2.2.4.1 General . 12
5.2.2.5 Retrieve . 13
5.2.2.5.1 General . 13
5.2.2.6 StatusSubscribe service operation . 14
5.2.2.6.1 General . 14
5.2.2.6.2 Subscription creation . 14
5.2.2.6.3 Subscription update . 15
5.2.2.7 StatusUnsubscribe . 15
5.2.2.7.1 General . 15
5.2.2.8 StatusNotify . 16
5.2.2.8.1 General . 16
6 API Definitions . 17
6.1 Nmbstf_MBSDistributionSession Service API . 17
6.1.1 Introduction. 17
6.1.2 Usage of HTTP . 17
6.1.2.1 General . 17
6.1.2.2 HTTP standard headers . 17
6.1.2.2.1 General . 17
6.1.2.2.2 Content type . 17
6.1.2.3 HTTP custom headers . 18
6.1.3 Resources . 18
6.1.3.1 Overview . 18
6.1.3.2 Resource: MBS Distribution sessions collection (Collection) . 18
6.1.3.2.1 Description . 18
6.1.3.2.2 Resource Definition . 19
6.1.3.2.3 Resource Standard Methods . 19
6.1.3.2.3.1 POST. 19
6.1.3.2.4 Resource Custom Operations . 20
6.1.3.3 Resource: Individual MBS distribution session (Document) . 20
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 4 ETSI TS 129 581 V17.7.0 (2026-04)
6.1.3.3.1 Description . 20
6.1.3.3.2 Resource Definition . 20
6.1.3.3.3 Resource Standard Methods . 21
6.1.3.3.3.1 PATCH . 21
6.1.3.3.3.2 DELETE . 22
6.1.3.3.3.3 GET. 23
6.1.3.3.4 Resource Custom Operations . 24
6.1.3.4 Resource: Subscriptions collection for MBS distribution session (Collection) . 25
6.1.3.4.1 Description . 25
6.1.3.4.2 Resource Definition . 25
6.1.3.4.3 Resource Standard Methods . 25
6.1.3.4.3.1 POST. 25
6.1.3.4.4 Resource Custom Operations . 27
6.1.3.5 Resource: Individual subscription for an MBS distribution session (Document) . 27
6.1.3.5.1 Description . 27
6.1.3.5.2 Resource Definition . 27
6.1.3.5.3 Resource Standard Methods . 27
6.1.3.5.3.1 DELETE . 27
6.1.3.5.3.2 PATCH . 28
6.1.3.5.4 Resource Custom Operations . 30
6.1.4 Custom Operations without associated resources . 30
6.1.5 Notifications . 30
6.1.5.1 General . 30
6.1.5.2 StatusNotify . 30
6.1.5.2.1 Description . 30
6.1.5.2.2 Target URI . 30
6.1.5.2.3 Standard Methods . 31
6.1.6 Data Model . 32
6.1.6.1 General . 32
6.1.6.2 Structured data types . 33
6.1.6.2.1 Introduction . 33
6.1.6.2.2 Type: CreateReqData . 33
6.1.6.2.3 Type: CreateRspData . 33
6.1.6.2.4 Type: DistSession . 34
6.1.6.2.5 Type: ObjDistributionData . 35
6.1.6.2.6 Type: PktDistributionData . 36
6.1.6.2.7 Type: StatusSubscribeReqData . 36
6.1.6.2.8 Type: StatusSubscribeRspData . 36
6.1.6.2.9 Type: StatusNotifyReqData . 36
6.1.6.2.10 Type: DistSessionSubscription . 36
6.1.6.2.11 Type: DistSessionEventReportList . 37
6.1.6.2.12 Type: DistSessionEventReport . 37
6.1.6.2.13 Type: UpTrafficFlowInfo . 38
6.1.6.2.14 Type: MbStfIngestAddr . 39
6.1.6.2.15 Type: ExtSsm . 41
6.1.6.3 Simple data types and enumerations . 41
6.1.6.3.1 Introduction . 41
6.1.6.3.2 Simple data types . 41
6.1.6.3.3 Enumeration: DistSessionState . 41
6.1.6.3.4 Enumeration: ObjDistributionOperatingMode . 41
6.1.6.3.5 Enumeration: ObjAcquisitionMethod . 41
6.1.6.3.6 Enumeration: PktDistributionOperatingMode . 42
6.1.6.3.7 Enumeration: DistSessionEventType . 42
6.1.6.3.8 Enumeration: PktIngestMethod . 42
6.1.6.4 Data types describing alternative data types or combinations of data types . 42
6.1.6.5 Binary data . 42
6.1.7 Error Handling . 43
6.1.7.1 General . 43
6.1.7.2 Protocol Errors . 43
6.1.7.3 Application Errors . 43
6.1.8 Feature negotiation . 43
6.1.9 Security . 43
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 5 ETSI TS 129 581 V17.7.0 (2026-04)
Annex A (normative): OpenAPI specification . 44
A.1 General . 44
A.2 Nmbstf_DistSession API . 44
Annex B (informative): Change history . 55
History . 56

ETSI
3GPP TS 29.581 version 17.7.0 Release 17 6 ETSI TS 129 581 V17.7.0 (2026-04)
Foreword
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
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 7 ETSI TS 129 581 V17.7.0 (2026-04)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 8 ETSI TS 129 581 V17.7.0 (2026-04)
1 Scope
The present document specifies the stage 3 protocol and data model for the Nmbstf Service Based Interface. It provides
stage 3 protocol definitions and message flows, and specifies the API for each service offered by the MBSTF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]. The
5G Multicast-Broadcast Session Management Services for 5G System is specified in 3GPP TS 23.247 [15] and the User
Service Architecture for 5G Multicast-Broadcast Services is specified in 3GPP TS 26.502 [17].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
2 References
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[7] 3GPP TR 21.900: "Technical Specification Group working methods".
[8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[11] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13] IETF RFC 7807: "Problem Details for HTTP APIs".
[14] IETF RFC 6902: "JavaScript Object Notation (JSON) Patch".
[15] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[16] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[17] 3GPP TS 26.502: "5G multicast–broadcast services; User Service architecture; Stage 2".
[18] 3GPP TS 29.580: "5G System; Multicast/Broadcast Service Function services; Stage 3".
[19] IETF RFC 5775: "Asynchronous Layered Coding (ALC) Protocol Instantiation".
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 9 ETSI TS 129 581 V17.7.0 (2026-04)

3 Definitions, symbols and abbreviations
3.1 Definitions
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 TR 21.905 [1].
For the definitions of the basic SBI notions (e.g. apiRoot, API URI, Callback URI, etc.), SBI specific abbreviations (e.g.
CRUD, YAML, etc.), special characters, operators and delimiters that are used by SBI specifications, see clause 3 in
3GPP TS 29.501 [5].
3.2 Symbols
For the purposes of the present document, the following symbols apply:

3.3 Abbreviations
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
3GPP TR 21.905 [1].
5MBS 5G Multicast-Broadcast Services
AF Application Function
ALC Asynchronous Layered Coding
AS Application server
DNN Data Network Name
MBSF Multicast/Broadcast Service Function
MBSTF Multicast/Broadcast Service Transport Function
MB-SMF Multicast/Broadcast Session Management Function
MB-UPF Multicast/Broadcast User Plane Function
NEF Network Exposure Function
NF Network Function
S-NSSAI Single Network Slice Selection Assistance Information
TSI Transmission Session Identifier
URI Uniform Resource Identifier
4 Overview
4.1 General
Within the 5GC, the MBSTF offers services to the MBSF via the Nmbstf service based interface (see
3GPP TS 23.501 [2] and 3GPP TS 26.502 [17]).
Figures 4.1 provides the reference model (in service based interface representation and in reference point
representation), with focus on the MBSTF and the scope of the present specification.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 10 ETSI TS 129 581 V17.7.0 (2026-04)
MBSF
Nmb2 Nmbstf MBSTF
Figure 4-1: Reference model – MBSTF
Nmb2 is the reference point between MBSF and MBSTF.
The functionalities supported by the MBSTF are listed in clause 5.3.2.12 of 3GPP TS 23.247 [15].
The services and service operations provided by the Nmbstf interface are listed in clause 7.3 of 3GPP TS 26.502 [17].
5 Services offered by the MBSTF
5.1 Introduction
Table 5.1-1 summarizes the SBI services produced by the MBSTF.
Table 5.1-1: NF Services provided by MBSTF
Service Name Description Example
Consumers
Nmbstf_MBSDistributionSession Manage (e.g. Create, Modify, Delete) a new MBS MBSF
Distribution Session within the MBSTF.

Table 5.1-2 summarizes the corresponding APIs defined for this specification.
Table 5.1-2: API Descriptions
OpenAPI Specification
Service Name Clause Description apiName Annex
File
MBSTF
TS29581_ nmbstf-
Nmbstf_MBSDistributionSession 5.2 Distribution A.2
Nmbstf_DistSession.yaml distsession
Session Service
5.2 Nmbstf_MBSDistributionSession Service
5.2.1 Service Description
The Nmbstf_MBSDistributionSession service operates on MBS distribution sessions. The following are the key
functionalities of this NF service:
- Creation, modification, retrieval and deletion of MBS Distribution Sessions
Table 5.2.1-1 lists the service operations that are supported by the Nmbstf_MBSDistributionSession service.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 11 ETSI TS 129 581 V17.7.0 (2026-04)
Table 5.2.1-1: Service operations supported by the Nmbstf_MBSDistributionSession service
Operation
Service Operations Description Example Consumers
Semantics
Create a new MBS Distribution Session Request /
Create MBSF
within the MBSTF Response
Request /
Update Update an existing MBS Distribution Session MBSF
Response
Request /
Destroy Delete an existing MBS Distribution Session MBSF
Response
Retrieve the parameters of an existing MBS Request /
Retrieve MBSF
Distribution Session Response
Subscribe to notifications related to an MBS
StatusSubscribe MBSF
Distribution Session
Unsubscribe from notifications related to an Subscribe/
StatusUnsubscribe MBSF
MBS Distribution Session Notify
Notify event(s) related to an MBS Distribution
StatusNotify MBSF
Session
5.2.2 Service Operations
5.2.2.1 Introduction
See Table 5.2.1-1 for an overview of the service operations supported by the Nmbstf_MBSDistributionSession service.
5.2.2.2 Create
5.2.2.2.1 General
The Create service operation shall be used to create a new MBS Distribution Session within the MBSTF (see
clauses 5.2, 4.5.2 of 3GPP TS 26.502 [17]).
The NF Service Consumer (e.g. MBSF) shall create an MBS Distribution session in the MBSTF by using the HTTP
POST method as shown in Figure 5.2.2.2.1-1.
NF Service
MBSTF
Consumer
1. POST ./dist-sessions (CreateReqData)
2a. 201 Created (CreateRspData)
2b. 4xx/5xx (ProblemDetails)
2c. 3xx (RedirectResponse)
Figure 5.2.2.2.1-1: MBS Distribution session creation
1. The NF Service Consumer shall send a POST request (CreateReqData) targeting the MBS Distribution Sessions
collection resource of the MBSTF. The payload body of the POST request shall contain the following
information:
- The baseline parameters for an MBS Distribution Session including Distribution Session Identifier, and;
- Additional MBS Distribution Session parameters for Object Distribution Method, or;
- Additional MBS Distribution Session parameters for Packet Distribution Method;
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 12 ETSI TS 129 581 V17.7.0 (2026-04)
2a. On success, the MBSTF shall return a "201 Created" response. The "Location" header shall be present and shall
contain the URI of the created resource. The payload body of the POST response (CreateRspData) shall contain
a representation of the created MBS session.
2b. On failure, one of the HTTP status code listed in Table 6.1.3.2.3.1-3 shall be returned. The message body shall
contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in
Table 6.1.3.2.3.1-3.
2c. On redirection, "307 Temporary Redirect" or "308 Permanent Redirect" shall be returned. A RedirectResponse
IE shall be included in the payload body of POST response.
5.2.2.3 Update
5.2.2.3.1 General
The Update service operation shall be used to update an existing MBS Distribution Session within the MBSTF (see
clauses 5.2, 4.5.2 of 3GPP TS 26.502 [17]).
The NF Service Consumer (e.g. MBSF) shall update an MBS Distribution session in the MBSTF by using the HTTP
PATCH method as shown in Figure 5.2.2.3.1-1.
NF Service
MBSTF
Consumer
1. PATCH ./dist-sessions/{distSessionRef} (PatchData)
2a. 204 No Content
2b. 200 OK (DistSession)
2c. 4xx/5xx (ProblemDetails)
2d. 3xx (RedirectResponse)
Figure 5.2.2.3.1-1: MBS Distribution session update
1. The NF Service Consumer shall send a PATCH request (PatchData) to update the MBS distribution session.
2a. On success, the MBSTF shall return "204 No Content";
2b. On success, the MBSTF shall return "200 OK" containing new resource representation of MBS distribution
session;
2c. On failure, one of the HTTP status code listed in Table 6.1.3.3.3.1-3 shall be returned. The message body shall
contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in
Table 6.1.3.3.3.1-3.
2d. On redirection, "307 Temporary Redirect" or "308 Permanent Redirect" shall be returned. A RedirectResponse
IE shall be included in the payload body of PATCH response.
5.2.2.4 Destroy
5.2.2.4.1 General
The Destroy service operation shall be used to delete an existing MBS Distribution Session within the MBSTF (see
clauses 5.2, 4.5.2 of 3GPP TS 26.502 [17]).
The NF Service Consumer (e.g. MBSF) shall delete an MBS Distribution session in the MBSTF by using the HTTP
DELETE method as shown in Figure 5.2.2.4.1-1.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 13 ETSI TS 129 581 V17.7.0 (2026-04)
NF Service
MBSTF
Consumer
1. DELETE ./dist-sessions/{distSessionRef}
2a. 204 No Content
2b. 4xx/5xx (ProblemDetails)
2c. 3xx (RedirectResponse)
Figure 5.2.2.4.1-1: MBS Distribution session deletion
1. The NF Service Consumer shall send a DELETE request (distSessionRef) to release the MBS distribution
session.
2a. On success, the MBSTF shall delete the MBS distribution session and return a "204 No Content" response.
2b. On failure, one of the HTTP status code listed in Table 6.1.3.3.3.2-3 shall be returned. The message body shall
contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in
Table 6.1.3.3.3.2-3.
2c. On redirection, "307 Temporary Redirect" or "308 Permanent Redirect" shall be returned. A RedirectResponse
IE shall be included in the payload body of DELETE response.
5.2.2.5 Retrieve
5.2.2.5.1 General
The Retrieve service operation shall be used to retrieve the parameters of an existing MBS Distribution Session within
the MBSTF (see clauses 5.2, 4.5.2 of 3GPP TS 26.502 [17]).
The NF Service Consumer (e.g. MBSF) shall retrieve an MBS Distribution session in the MBSTF by using the HTTP
GET method as shown in Figure 5.2.2.5.1-1.
NF Service
MBSTF
Consumer
1. GET ./dist-sessions/{distSessionRef}
2a. 200 OK (distSession)
2b. 4xx/5xx (ProblemDetails)
2c. 3xx (RedirectResponse)
Figure 5.2.2.5.1-1: MBS Distribution session retrieval
1. The NF Service Consumer shall send a GET request to the resource representing the MBS distribution session
(distSessionRef).
2a. On success, the MBSTF shall respond with "200 OK" with the message body containing parameters of the
distribution session (distSession).
2b. On failure, one of the HTTP status code listed in Table 6.1.3.3.3.3-3 shall be returned. The message body shall
contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in
Table 6.1.3.3.3.3-3.
2c. On redirection, "307 Temporary Redirect" or "308 Permanent Redirect" shall be returned. A RedirectResponse
IE shall be included in the payload body of GET response.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 14 ETSI TS 129 581 V17.7.0 (2026-04)
5.2.2.6 StatusSubscribe service operation
5.2.2.6.1 General
The StatusSubscribe service operation shall be used by an NF Service Consumer (e.g. MBSF) to create a subscription to
the MBSTF notifications related to the event(s) of an MBS distribution session.
5.2.2.6.2 Subscription creation
The NF Service Consumer (e.g. MBSF) shall subscribe to MBSTF service notifications by using the HTTP POST
method as shown in Figure 5.2.2.6.2-1.
NF Service
MBSTF
Consumer
1. POST ./dist-sessions/{distSessionRef}/subscriptions
(StatusSubscribeReqData)
2a. 201 Created (StatusSubscribeRspData)
2b. 4xx/5xx (ProblemDetails)
2c. 3xx (RedirectResponse)
Figure 5.2.2.6.2-1: Subscribing to MBSTF notifications
1. The NF Service Consumer shall send a POST request (StatusSubscribeReqData) to the resource URI
representing the subscriptions collection resource in the MBSTF. The payload body of the POST request shall
contain:
- the list of MBS distribution session events requested to be subscribed.
- the Notification URI , indicating the address where the MBSTF shall send the notifications;
The request body may also contain:
- an expiry time suggested by the NF Service Consumer, representing the time span during which the
subscription is desired to be kept active; and
- Notification Correlation ID;
2a. On success, the MBSTF shall return a "201 Created" response. The "Location" header shall be present and shall
contain the URI of the created resource. The payload body of the POST response (StatusSubscribeRspData) shall
include:
- the Distribution Session Identifier;
- the list of events successfully subscribed;
- the expiry time after which the subscription becomes invalid.
2b. On failure, one of the HTTP status code listed in the data structures supported by the POST Response Body (see
Table 6.1.3.4.3.1-3) shall be returned. The message body shall contain a ProblemDetails structure with the
"cause" attribute set to one of the application error listed in the same Table 6.1.3.4.3.1-3).
2c. On redirection, "307 Temporary Redirect" or "308 Permanent Redirect" shall be returned. A RedirectResponse
IE shall be included in the payload body of POST response.
ETSI
3GPP TS 29.581 version 17.7.0 Release 17 15 ETSI TS 129 581 V17.7.0 (2026-04)
5.2.2.6.3 Subscription update
When the StatusSubscribe service operation is used for updating a subscription, the NF Service Consumer (e.g. MBSF)
shall update its subscription to MBSTF notifications by using the HTTP PATCH method as shown in Figure 5.2.2.6.3-
1.
NF Service
MBSTF
Consumer
1. PATCH ./dist-sessions/{distSessionRef}/subscriptions/
{subscriptionId} (array(PatchItem))
2a. 200 OK (StatusSubscription)
2b. 4xx/5xx (ProblemDetails)
2c. 3xx (RedirectResponse)
...