6.5 Namf_MBSBroadcast Service API
29.5183GPP5G SystemAccess and Mobility Management ServicesRelease 18Stage 3TS
6.5.1 API URI
The Namf_MBSBroadcast service shall use the Namf_MBSBroadcast API.
The API URI of the Namf_MBSBroadcast API shall be:
{apiRoot}/<apiName>/<apiVersion>
The request URI used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
– The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
– The <apiName> shall be "namf-mbs-bc".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 6.5.3.
6.5.2 Usage of HTTP
6.5.2.1 General
HTTP/2, as defined in IETF RFC 7540 [19], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
HTTP messages and bodies for the Namf_MBSBroadcast service shall comply with the OpenAPI [23] specification contained in Annex A.
6.5.2.2 HTTP standard headers
6.5.2.2.1 General
The usage of HTTP standard headers shall be supported as specified in clause 5.2.2 of 3GPP TS 29.500 [4].
6.5.2.2.2 Content type
The following content types shall be supported:
– JSON, as defined in IETF RFC 8259 [8], shall be used as content type of the HTTP bodies specified in the present specification as indicated in clause 5.4 of 3GPP TS 29.500 [4].
– The Problem Details JSON Object (IETF RFC 7807 [36]). The use of the Problem Details JSON object in a HTTP response body shall be signalled by the content type "application/problem+json".
Multipart messages shall also be supported (see clause 6.5.2.4) using the content type "multipart/related", comprising:
– one JSON body part with the "application/json" content type; and
– one or more binary body parts with 3gpp vendor specific content subtypes.
The 3gpp vendor specific content subtypes defined in Table 6.5.2.2.2-1 shall be supported.
Table 6.5.2.2.2-1: 3GPP vendor specific content subtypes
content subtype |
Description |
vnd.3gpp.ngap |
Binary encoded payload, encoding NG Application Protocol (NGAP) IEs, as specified in clause 9.3 of 3GPP TS 38.413 [9] (ASN.1 encoded). |
NOTE: Using 3GPP vendor content subtypes allows to describe the nature of the opaque payload (i.e. NGAP information) without having to rely on metadata in the JSON payload. |
See clause 6.5.2.4 for the binary payloads supported in the binary body part of multipart messages.
6.5.2.3 HTTP custom headers
6.5.2.3.1 General
In this release of this specification, no custom headers specific to the Namf_MBSBroadcast service are defined. For 3GPP specific HTTP custom headers used across all service-based interfaces, see clause 5.2.3 of 3GPP TS 29.500 [4].
6.5.2.4 HTTP multipart messages
HTTP multipart messages shall be supported, to transfer opaque N2 Information in the following service operations (and HTTP messages):
– ContextCreate Request and Response (POST);
– ContextUpdate Request and Response (POST);
– ContextStatusNotify service operation (POST).
HTTP multipart messages shall include one JSON body part and one or more binary body parts comprising:
– N2 payload (see clause 6.1.6.4).
The JSON body part shall be the "root" body part of the multipart message. It shall be encoded as the first body part of the multipart message. The "Start" parameter does not need to be included.
The multipart message shall include a "type" parameter (see IETF RFC 2387 [9]) specifying the media type of the root body part, i.e. "application/json".
NOTE: The "root" body part (or "root" object) is the first body part the application processes when receiving a multipart/related message, see IETF RFC 2387 [9]. The default root is the first body within the multipart/related message. The "Start" parameter indicates the root body part, e.g. when this is not the first body part in the message.
For each binary body part in a HTTP multipart message, the binary body part shall include a Content-ID header (see IETF RFC 2045 [10]), and the JSON body part shall include an attribute, defined with the RefToBinaryData type, that contains the value of the Content-ID header field of the referenced binary body part.
6.5.3 Resources
6.5.3.1 Overview
Figure 6.5.3.1-1: Resource URI structure of the Namf_MBSBroadcast Service API
Table 6.5.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 6.5.3.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description (service operation) |
Broadcast MBS session contexts collection |
/mbs-contexts |
POST |
ContextCreate |
Individual broadcast MBS session context |
/mbs-contexts/{mbsContextRef}/update |
update (POST) |
ContextUpdate |
/mbs-contexts/{mbsContextRef} |
DELETE |
ContextRelease |
6.5.3.2 Resource: Broadcast MBS session contexts collection
6.5.3.2.1 Description
This resource represents a collection of Broadcast MBS session contexts created by NF service consumers of the Namf_MBSBroadcast service.
This resource is modelled as the Collection resource archetype (see clause C.2 of 3GPP TS 29.501 [5]).
6.5.3.2.2 Resource Definition
Resource URI: {apiRoot}/namf-mbs-bc/<apiVersion>/mbs-contexts
This resource shall support the resource URI variables defined in table 6.5.3.2.2-1.
Table 6.5.3.2.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See clause 6.5.1 |
apiVersion |
string |
See clause 6.5.1. |
6.5.3.2.3 Resource Standard Methods
6.5.3.2.3.1 POST
This method shall support the URI query parameters specified in table 6.5.3.2.3.1-1.
Table 6.5.3.2.3.1-1: URI query parameters supported by the POST method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 6.5.3.2.3.1-2 and the response data structures and response codes specified in table 6.5.3.2.3.1-3.
Table 6.5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ContextCreateReqData |
M |
1 |
Data within ContextCreate Request |
Table 6.5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
ContextCreateRspData |
M |
1 |
201 Created |
Successful creation of a broadcast MBS context |
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. |
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
Table 6.5.3.2.3.1-4: Headers supported by the 201 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
Contains the URI of the newly created resource, according to the structure: {apiRoot}/namf-mbs-bc/<apiVersion>/mbs-contexts/{mbsContextRef} |
Table 6.5.3.2.3.1-5: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
Table 6.5.3.2.3.1-6: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
6.5.3.2.4 Resource Custom Operations
None.
6.5.3.3 Resource: Individual broadcast MBS session context
6.5.3.3.1 Description
This resource represents an Individual broadcast MBS session context created by an NF service consumer of the Namf_MBSBroadcast service.
This resource is modelled as the Document resource archetype (see clause C.2 of 3GPP TS 29.501 [5]).
6.5.3.3.2 Resource Definition
Resource URI: {apiRoot}/namf-mbs-bc/<apiVersion>/mbs-contexts/{mbsContextRef}
This resource shall support the resource URI variables defined in table 6.5.3.3.2-1.
Table 6.5.3.3.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See clause 6.5.1 |
apiVersion |
string |
See clause 6.5.1 |
mbsContextRef |
string |
String identifying an individual broadcast MBS session context |
6.5.3.3.3 Resource Standard Methods
6.5.3.3.3.1 DELETE
This method shall support the URI query parameters specified in table 6.5.3.3.3.1-1.
Table 6.5.3.3.3.1-1: URI query parameters supported by the DELETE method on this resource
Name |
Data type |
P |
Cardinality |
Description |
n/a |
This method shall support the request data structures specified in table 6.5.3.3.3.1-2 and the response data structures and response codes specified in table 6.5.3.3.3.1-3.
Table 6.5.3.3.3.1-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 6.5.3.3.3.1-3: Data structures supported by the DELETE Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Successful deletion of a broadcast MBS context |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. |
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
Table 6.5.3.3.3.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
Table 6.5.3.3.3.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
6.5.3.3.4 Resource Custom Operations
6.5.3.2.4.1 Overview
Table 6.5.3.2.4.1-1: Custom operations
Operation Name |
Custom operaration URI |
Mapped HTTP method |
Description |
update |
/mbscontexts/{mbsContextRef}/update |
POST |
ContextUpdate service operation |
6.5.3.2.4.2 Operation: update (POST)
6.5.3.2.4.2.1 Description
This {mbsContextRef} identifies the individual broadcast MBS session context to be updated.
6.5.3.2.4.2.2 Operation Definition
This operation shall support the request data structures specified in table 6.5.3.2.4.2.2-1 and the response data structure and response codes specified in table 6.5.3.2.4.2.2-2.
Table 6.5.3.2.4.2.2-1: Data structures supported by (POST) the update operation Request Body
Data type |
P |
Cardinality |
Description |
ContextUpdateReqData |
M |
1 |
Data within the ContextUpdate Request |
Table 6.5.3.2.4.2.2-2: Data structures supported by the (POST) update operation Response Body
Data type |
P |
Cardinality |
Response codes |
Description |
ContextUpdateRspData |
M |
1 |
200 OK |
Successful update of the broadcast MBS session context, with content in the response |
n/a |
204 No Content |
Successful update of the broadcast MBS session context, without content in the response |
||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. |
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
Table 6.5.3.2.4.2.2-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
Table 6.5.3.2.4.2.2-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI of the resource located on an alternative service instance within the same AMF or AMF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
6.5.4 Custom Operations without associated resources
There are no custom operations without associated resources supported by the Namf_MBSBroadcast Service in this release of the specification.
6.5.5 Notifications
6.5.5.1 General
This clause specifies the notifications provided by the Namf_MBSBroadcast service.
Table 6.5.5.1-1: Notifications overview
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
Broadcast MBS Session Context Status Notification |
{notifyUri} |
POST |
ContextStatusNotify |
6.5.5.2 Broadcast MBS Session Context Status Notification
6.5.5.2.1 Description
The Broadcast MBS session context notification is used by the AMF to report one or several status changes of a Broadcast MBS session context to a NF service consumer.
6.5.5.2.2 Target URI
The Callback URI "{notifyUri}" shall be used with the callback URI variables defined in table 6.5.5.2.2-1.
Table 6.5.5.2.2-1: Callback URI variables
Name |
Definition |
notifyUri |
String formatted as URI with the Callback URI |
6.5.5.2.3 Notification Standard Methods
6.5.5.2.3.1 POST
This method shall support the request data structures specified in table 6.5.5.2.3.1-1 and the response data structures and response codes specified in table 6.5.5.2.3.1-2.
Table 6.5.5.2.3.1-2: Data structures supported by the POST Request Body
Data type |
P |
Cardinality |
Description |
ContextStatusNotification |
M |
1 |
Represents the notification to be delivered |
Table 6.5.5.2.3.1-3: Data structures supported by the POST Response Body
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
|||
RedirectResponse |
O |
0..1 |
307 Temporary Redirect |
Temporary redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent. If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
RedirectResponse |
O |
0..1 |
308 Permanent Redirect |
Permanent redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent. If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |
Table 6.5.5.2.3.1-4: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer to which the notification should be sent |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
Table 6.5.5.2.3.1-5: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
A URI pointing to the endpoint of the NF service consumer to which the notification should be sent |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the request is redirected |
6.5.6 Data Model
6.5.6.1 General
This clause specifies the application data model supported by the API.
Table 6.5.6.1-1 specifies the data types defined for the Namf_MBSBroadcast service based interface protocol.
Table 6.5.6.1-1: Namf_MBSBroadcast specific Data Types
Data type |
Clause defined |
Description |
ContextCreateReqData |
6.5.6.2.2 |
Data within ContextCreate Request |
ContextCreateRspData |
6.5.6.2.3 |
Data within ContextCreate Response |
ContextStatusNotification |
6.5.6.2.4 |
Data within ContextStatusNotify Request |
ContextUpdateReqData |
6.5.6.2.5 |
Data within ContextUpdate Request |
ContextUpdateRspData |
6.5.6.2.6 |
Data within ContextUpdate Response |
N2MbsSmInfo |
6.5.6.2.7 |
N2 MBS Session Management Information |
OperationEvent |
6.5.6.2.8 |
Operation Event |
NgranFailureEvent |
6.5.6.2.9 |
NG-RAN failure event |
OperationStatus |
6.5.6.3.3 |
Operation Status |
NgapIeType |
6.5.6.3.4 |
NGAP Information Element Type |
OpEventType |
6.5.6.3.5 |
Operation Event Type |
NgranFailureIndication |
6.5.6.3.6 |
Indication of a NG-RAN failure event |
Table 6.5.6.1-2 specifies data types re-used by the Namf service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Namf service based interface.
Table 6.5.6.1-2: Namf re-used Data Types
Data type |
Reference |
Comments |
MbsSessionId |
3GPP TS 29.571 [6] |
MBS Session Id |
AreaSessionId |
3GPP TS 29.571 [6] |
Area Session Id |
MbsServiceArea |
3GPP TS 29.571 [6] |
MBS Service Area |
RefToBinaryData |
3GPP TS 29.571 [6] |
Reference to binary body part |
Uri |
3GPP TS 29.571 [6] |
URI |
DurationSec |
3GPP TS 29.571 [6] |
Duration in seconds |
MbsServiceAreaInfo |
3GPP TS 29.571 [6] |
MBS Service Area Information for a Location dependent MBS session |
GlobalRanNodeId |
3GPP TS 29.571 [6] |
Global RAN Node Identifier |
6.5.6.2 Structured data types
6.5.6.2.1 Introduction
Structured data types used in Namf_MBSBroadcast service are specified in this clause.
6.5.6.2.2 Type: ContextCreateReqData
Table 6.5.6.2.2-1: Definition of type ContextCreateReqData
Attribute name |
Data type |
P |
Cardinality |
Description |
mbsSessionId |
MbsSessionId |
M |
1 |
MBS Session ID |
mbsServiceArea |
MbsServiceArea |
C |
1 |
MBS Service Area This IE shall be present if this is a Local broadcast MBS session. (NOTE 1) |
mbsServiceAreaInfoList |
array(MbsServiceAreaInfo) |
C |
1..N |
List of MBS service areas and their related Area Session IDs. This IE shall be present if this is a Location dependent broadcast MBS service. (NOTE 1) |
n2MbsSmInfo |
N2MbsSmInfo |
M |
1 |
This IE shall be present and shall contain N2 MBS Session Management related information.(see clause 6.5.6.4). |
notifyUri |
Uri |
M |
1 |
This IE shall contain the notification URI where to be notified about the status change of the broadcast MBS session context. |
maxResponseTime |
DurationSec |
O |
0..1 |
Maximum response time (in seconds) to receive information about the completion of the Broadcast MBS session establishment. |
snssai |
Snssai |
M |
1 |
This IE shall be included to indicate the S-NSSAI of the MBS session. (NOTE 2). |
mbsmfId |
NfInstanceId |
O |
0..1 |
This IE may be present to contain the NF Instance ID of the MB-SMF. |
mbsmfServiceInstId |
string |
O |
0..1 |
This IE may be present to contain the NF Service Instance ID within the NF Instance of the MB-SMF. |
NOTE 1: Either the mbsServiceAreaInfoList IE or the mbsServiceArea IE shall be present. NOTE 2: If an MB-SMF does not receive the S-NSSAI from the NEF/MBSF, the MB-SMF shall include a pre-configured default SNSSAI. |
6.5.6.2.3 Type: ContextCreateRspData
Table 6.5.6.2.3-1: Definition of type ContextCreateRspData
Attribute name |
Data type |
P |
Cardinality |
Description |
mbsSessionId |
MbsSessionId |
M |
1 |
MBS session identifier. |
n2MbsSmInfoList |
array(N2MbsSmInfo) |
O |
1..10 |
When present, this IE shall contain N2 MBS Session Management related information.(see clause 6.5.6.4). |
operationStatus |
OperationStatus |
C |
0..1 |
This IE shall be present and indicate the completion of the MBS session start operation, if the AMF received the NG-RAN responses from all involved NG-RAN(s). (NOTE) |
NOTE: If this IE is not present, it indicates either of the following conditions (a) not all response are received from NG-RANs, while the maximum response timer is still running, or (b) the AMF has not received the maximum response timer in the request from the MB-SMF and not all response are received from NG-RANs. |
6.5.6.2.4 Type: ContextStatusNotification
Table 6.5.6.2.4-1: Definition of type ContextStatusNotification
Attribute name |
Data type |
P |
Cardinality |
Description |
mbsSessionId |
MbsSessionId |
M |
1 |
MBS Session ID |
areaSessionId |
AreaSessionId |
C |
0..1 |
Area Session ID This IE shall be present if this is a Location dependent broadcast MBS service. |
n2MbsSmInfoList |
array(N2MbsSmInfo) |
O |
1..10 |
When present, this IE shall contain N2 MBS Session Management related information.(see clause 6.5.6.4). |
operationStatus |
OperationStatus |
C |
0..1 |
This IE shall be present and indicate the completion of the MBS session start or update operation, if the NF Service Consumer has requested to establish or update the Broadcast MBS session context and a response has been received from all NG-RANs. This IE shall be present and indicate the incompletion of the MBS session start or update operation, if the NF Service Consumer has requested to establish or update the Broadcast MBS session context within a maximum response time and the AMF has not received responses from all NG-RANs before the maximum response time elapses. (NOTE) |
operationEvents |
array(operationEvent) |
O |
1..N |
This IE may be present to report a list of operation events related to the Broadcast MB Session. |
NOTE: If this IE is not present, it indicates either of the following conditions (a) not all response are received from NG-RANs, while the maximum response timer is still running, or (b) the AMF has not received the maximum response timer in the request from the MB-SMF and not all response are received from NG-RANs. |
6.5.6.2.5 Type: ContextUpdateReqData
Table 6.5.6.2.5-1: Definition of type ContextUpdateReqData
Attribute name |
Data type |
P |
Cardinality |
Description |
mbsServiceArea |
MbsServiceArea |
O |
0..1 |
MBS Service Area This IE may be present for a Location independent broadcast MBS session. (NOTE) |
mbsServiceAreaInfoList |
array(MbsServiceAreaInfo) |
O |
1..N |
List of MBS service areas and their related Area Session IDs. This IE may be present for a Local broadcast MBS service. (NOTE) |
n2MbsSmInfo |
N2MbsSmInfo |
O |
0..1 |
When present, this IE shall contain N2 MBS Session Management related information.(see clause 6.5.6.4). |
ranIdList |
array(GlobalRanNodeId) |
O |
1..N |
This IE may be included when the MBS session update is to be performed only in a list of specific NG-RAN(s) as specified in clause 8.3.2.3 of 3GPP TS 23.527 [33]). |
noNgapSignallingInd |
boolean |
O |
0..1 |
This IE may be present during the restoration procedure to select an alternative AMF for a Broadcast MBS Session at AMF failure as specified in clause 8.3.2.4 of 3GPP TS 23.527 [33]). When present, this IE shall be set as following: – true: the AMF may consider to not trigger a NGAP signaling message to any NG-RAN. |
notifyUri |
Uri |
O |
0..1 |
When present, this IE shall contain the notification URI where to be notified about the status change of the broadcast MBS session context. |
maxResponseTime |
DurationSec |
O |
0..1 |
Maximum response time (in seconds) to receive information about the completion of the Broadcast MBS session update. |
n2MbsInfoChangeInd |
boolean |
O |
0..1 |
When present, this IE shall indicate whether the information within the N2 MBS Session Management container has changed or not, as follows: – true: the information has changed; – false: the information has not changed. |
NOTE: Either the mbsServiceAreaInfoList IE or the mbsServiceArea IE may be present. |
6.5.6.2.6 Type: ContextUpdateRspData
Table 6.5.6.2.6-1: Definition of type ContextUpdateRspData
Attribute name |
Data type |
P |
Cardinality |
Description |
n2MbsSmInfoList |
array(N2MbsSmInfo) |
O |
1..10 |
When present, this IE shall contain N2 MBS Session Management related information.(see clause 6.5.6.4). |
operationStatus |
OperationStatus |
C |
0..1 |
This IE shall be present and indicate the completion of the MBS session start operation, if the AMF received the NG-RAN responses from all involved NG-RAN(s). (NOTE) |
NOTE: If this IE is not present, it indicates either of the following conditions (a) not all response are received from NG-RANs, while the maximum response timer is still running, or (b) the AMF has not received the maximum response timer in the request from the MB-SMF and not all response are received from NG-RANs. |
6.5.6.2.7 Type: N2MbsSmInfo
Table 6.5.6.2.7-1: Definition of type N2MbsSmInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
ngapIeType |
NgapIeType |
M |
1 |
This IE shall indicate the NGAP IE type of the ngapData as specified in clause 6.5.6.3.4. |
ngapData |
RefToBinaryData |
M |
1 |
This IE shall contain the reference to the binary data part carrying the NGAP data. |
ranId |
GlobalRanNodeId |
M |
1 |
This IE shall indicate the Global RAN ID of the gNB that generated the N2 MBS Session Management related information. |
6.5.6.2.8 Type: OperationEvent
Table 6.5.6.2.8-1: Definition of type OperationEvent
Attribute name |
Data type |
P |
Cardinality |
Description |
opEventType |
OpEventType |
M |
1 |
Indicates the event type of an operation event related to the Broadcast MBS Session. |
amfId |
NfInstanceId |
C |
0..1 |
This IE shall be present to contain the NF Instance ID of the AMF sending the Context Status Notify Request message if the operation event type indicates an AMF change event. |
ngranFailureEventList |
array(NgranFailureEvent) |
C |
1..N |
This IE shall be present if the event type is related to a NG-RAN. |
6.5.6.2.9 Type: NgranFailureEvent
Table 6.5.6.2.9-1: Definition of type NgranFailureEvent
Attribute name |
Data type |
P |
Cardinality |
Description |
ngranId |
GlobalRanNodeId |
M |
1 |
Indicates the identity of the RAN node. The IE shall contain the gNB ID. |
ngranFailureIndication |
NgranFailureIndication |
M |
1 |
This IE shall contain the information related to the NG-RAN failure. |
6.5.6.3 Simple data types and enumerations
6.5.6.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
6.5.6.3.2 Simple data types
The simple data types defined in table 6.5.6.3.2-1 shall be supported.
Table 6.5.6.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
6.5.6.3.3 Enumeration: OperationStatus
The enumeration OperationStatus represents the status of a Broadcast MBS session start or update operation.
Table 6.5.6.3.3-1: Enumeration OperationStatus
Enumeration value |
Description |
"MBS_SESSION_START_COMPLETE" |
This value indicates the completion of the Broadcast MBS session establishment, i.e. that the AMF has received a response from all NG-RANs. |
" MBS_SESSION_START_INCOMPLETE" |
This value indicates the incompletion of the Broadcast MBS session establishment because the AMF has not received responses from all NG-RANs before the maximum response time that was indicated in the request elapses. |
"MBS_SESSION_UPDATE_COMPLETE" |
This value indicates the completion of the Broadcast MBS session update, i.e. that the AMF has received a response from all NG-RANs. |
" MBS_SESSION_UPDATE_INCOMPLETE" |
This value indicates incompletion of the Broadcast MBS session update because the AMF has not received responses from all NG-RANs before the maximum response time that was indicated in the request elapses. |
6.5.6.3.4 Enumeration: NgapIeType
Table 6.5.6.3.4-1: Enumeration NgapIeType
Enumeration value |
Description |
"MBS_SES_REQ" |
MBS Session Setup or Modification Request Transfer |
"MBS_SES_RSP" |
MBS Session Setup or Modification Response Transfer |
"MBS_SES_FAIL" |
MBS Session Setup or Modification Failure Transfer |
"MBS_SES_REL_RSP" |
MBS Session Release Response Transfer |
6.5.6.3.5 Enumeration: OpEventType
Table 6.5.6.3.5-1: Enumeration: OpEventType
Enumeration value |
Description |
"AMF_CHANGE" |
This value indicates that the AMF has taken over of the Broadcast MBS Session. |
"NG_RAN_EVENT" |
This value indicates that an event related to a NG-RAN for the Broadcast MBS Session has taken place. |
6.5.6.3.6 Enumeration: NgranFailureIndication
The enumeration NgranFailureIndication indicates a NG-RAN failure event.
Table 6.5.6.3.6-1: Enumeration NgranFailureIndication
Enumeration value |
Description |
"NG_RAN_RESTART_OR_START" |
This value indicates that the AMF has detected a (re)start of a NG-RAN. |
"NG_RAN_FAILURE_WITHOUT_RESTART" |
This value indicates that the AMF has detected a NG-RAN failure without a restart. |
"NG_RAN_NOT_REACHABLE" |
This value indicates that the AMF has failed to reach the NG-RAN when sending a NGAP MBS Session Setup/Modification/Release Request message. |
6.5.6.4 Binary data
6.5.6.4.1 Introduction
This clause defines the binary data that shall be supported in a binary body part in an HTTP multipart message (see clauses 6.5.2.2.2 and 6.5.2.4).
Table 6.5.6.4.1-1: Binary Data Types
Name |
Clause defined |
Content type |
N2 Information |
6.5.6.4.3 |
vnd.3gpp.ngap |
6.5.6.4.2 N2 Information
6.5.6.4.2.1 Introduction
N2 Information shall encode NG Application Protocol (NGAP) IEs, as specified in clause 9.3.A of 3GPP TS 38.413 [12] (ASN.1 encoded), using the vnd.3gpp.ngap content-type.
6.5.6.4.2.2 NGAP IEs
N2 Information may encode following NGAP MB-SMF related IE specified in clause 9.3.5 of 3GPP TS 38.413 [12], as summarized in Table 6.5.6.4.2.2-1.
Table 6.5.6.4.2.2-1: N2 Information content for class MBS-SM
NGAP IE |
Reference (3GPP TS 38.413 [12]) |
Related NGAP message |
MBS Session Setup or Modification Request Transfer |
9.3.5.3 |
BROADCAST SESSION SETUP REQUEST BROADCAST SESSION MODIFICATION REQUEST |
MBS Session Setup or Modification Response Transfer |
9.3.5.5 |
BROADCAST SESSION SETUP RESPONSE BROADCAST SESSION MODIFICATION RESPONSE |
MBS Session Setup or Modification Failure Transfer |
9.3.5.6 |
BROADCAST SESSION SETUP FAILURE BROADCAST SESSION MODIFICATION FAILURE |
MBS Session Release Response Transfer |
9.3.5.14 |
BROADCAST SESSION RELEASE RESPONSE (NOTE) |
NOTE: An MBS Session Release Response Transfer IE shall only be sent to the MB-SMF during a Broadcast MBS Session Release Require procedure (see clause 7.3.6 of 3GPP TS 23.247 [55]), when unicast transport applies over N3mb, to transfer the DL F-TEID of the NG-RAN node in which the MBS session has been released and towards which the delivery of MBS data shall be stopped. |
6.5.7 Error Handling
6.5.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [4].
6.5.7.2 Protocol Errors
Protocol Error Handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
6.5.7.3 Application Errors
The common application errors defined in the Table 5.2.7.2-1 in 3GPP TS 29.500 [4] may also be used for the Namf_MBSBroadcast service, and the following application errors listed in Table 6.5.7.3-1 are specific for the Namf_MBSBroadcast service.
Table 6.5.7.3-1: Application errors
Application Error |
HTTP status code |
Description |
6.5.8 Feature Negotiation
The optional features in table 6.5.8-1 are defined for the Namf_MBSBroadcast API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
Table 6.5.8-1: Supported Features
Feature number |
Feature Name |
Description |
6.5.9 Security
As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Namf_MBSBroadcast API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server.
If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Namf_MBSBroadcast API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2.
NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Namf_MBSBroadcast service.
The Namf_MBSBroadcast API defines a single scope "namf-mbs-bc" for the entire service, and it does not define any additional scopes at resource or operation level.
6.5.10 HTTP redirection
An HTTP request may be redirected to a different AMF service instance, within the same AMF or a different AMF of an AMF set, e.g. when an AMF service instance is part of an AMF (service) set or when using indirect communications (see 3GPP TS 29.500 [4]).
An SCP that reselects a different AMF producer instance will return the NF Instance ID of the new AMF producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4].
If an AMF within an AMF set redirects a service request to a different AMF of the set using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new AMF towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4].