5.19 MBSTMGI API
29.5223GPP5G SystemNetwork Exposure Function Northbound APIsRelease 18Stage 3TS
5.19.1 Introduction
The Nnef_MBSTMGI service shall use the MBSTMGI API.
The API URI of MBSTMGI API shall be:
{apiRoot}/3gpp-mbs-tmgi/v1
with the following components:
– "apiRoot" is set as defined in clause 5.2.4 of 3GPP TS 29.122 [4].
– "apiName" shall be set to "3gpp-mbs-tmgi".
– "apiVersion" shall be set to "v1" for the current version defined in the present document.
All resource URIs in the clauses below are defined relative to the above root URI.
5.19.2 Resources
There are no resources defined for this API in this release of the specification.
5.19.3 Custom Operations without associated resources
5.19.3.1 Overview
The structure of the custom operation URIs of the MBSTMGI API is shown in Figure 5.19.3.1-1.
Figure 5.19.3.1-1: Custom operation URI structure of the MBSTMGI API
Table 5.19.3.1-1 provides an overview of the custom operations and applicable HTTP methods.
Table 5.19.3.1-1: Custom operations without associated resources
Operation name |
Custom operation URI |
Mapped HTTP method |
Description |
Allocate |
/allocate |
POST |
Request the allocation of TMGI(s) for new MBS session(s) or the refresh of the expiry time of already allocated TMGI(s). |
Deallocate |
/deallocate |
POST |
Request the deallocation of TMGI(s). |
5.19.3.2 Operation: Allocate
5.19.3.2.1 Description
The custom operation enables an AF to request the allocation of TMGI(s) for new MBS session(s) or the refresh of the expiry time of already allocated TMGI(s).
5.19.3.2.2 Operation Definition
This operation shall support the request and response data structures and response codes specified in table 5.19.3.2.2-1 and table 5.19.3.2.2-2.
Table 5.19.3.2.2-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
TmgiAllocRequest |
M |
1 |
Represents the parameters to request the allocation of TMGI(s) for new MBS session(s) or the refresh of the expiry time of already allocated MBS TMGI(s). |
Table 5.19.3.2.2-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
TmgiAllocResponse |
M |
1 |
200 OK |
Successful case: The TMGI allocation information (e.g. allocated MBS TMGIs, expiry time) or the refreshed expiry time for the concerned already allocated MBS TMGI(s) is/are returned to the requesting AF. |
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative target URI located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative target URI located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4] |
||
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. |
Table 5.19.3.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 target URI of the resource located in an alternative NEF. |
Table 5.19.3.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 target URI of the resource located in an alternative NEF. |
5.19.3.3 Operation: Deallocate
5.19.3.3.1 Description
The custom operation enables an AF to request the deallocation of TMGI(s).
5.19.3.3.2 Operation Definition
This operation shall support the request and response data structures and response codes specified in table 5.19.3.3.2-1 and table 5.19.3.3.2-2.
Table 5.19.3.3.2-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
TmgiDeallocRequest |
M |
1 |
Represents the MBS TMGI(s) deallocation request information (e.g. list of MBS TMGI(s) to be deallocated). |
Table 5.19.3.3.2-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
Successful case: The requested MBS TMGI(s) are deallocated. |
||
n/a |
307 Temporary Redirect |
Temporary redirection. The response shall include a Location header field containing an alternative target URI located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection. The response shall include a Location header field containing an alternative target URI located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4] |
||
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. |
Table 5.19.3.3.2-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative target URI of the resource located in an alternative NEF. |
Table 5.19.3.3.2-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative target URI of the resource located in an alternative NEF. |
5.19.4 Notifications
5.19.4.1 General
Notifications shall comply to clause 5.2.5 of 3GPP TS 29.122 [4].
Table 5.19.4.1-1: Notifications overview
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
Notification of Allocated MBS TMGI(s) Timer Expiry |
{notificationUri} |
POST |
Enable the NEF to notify an AF of the timer expiry for already allocated MBS TMGI(s). |
5.19.4.2 Notification of Allocated MBS TMGI(s) Timer Expiry
5.19.4.2.1 Description
The Notification is used by the NEF to report timer expiry of already allocated TMGI(s) to the AF.
5.19.4.2.2 Target URI
The Callback URI "{notificationUri}" shall be used with the callback URI variables defined in table 5.19.4.2.2-1.
Table 5.19.4.2.2-1: Callback URI variables
Name |
Definition |
notificationUri |
Callback URIprovided by the AF during the MBS TMGI(s) allocation or expiry time refresh request as defined in table 5.19.5.2.2-1. |
5.19.4.2.3 Operation Definition
5.19.4.2.3.1 Notification via HTTP POST
This method shall support the request data structures specified in table 5.19.4.2.3.1-1 and the response data structures and response codes specified in table 5.19.4.2.3.1-2.
Table 5.19.4.2.3.1-1: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
ExpiryNotif |
M |
1 |
Represents the MBS TMGI(s) timer expiry notification information (e.g. list of MBS TMGI(s) for which the timer has expired). |
Table 5.19.4.2.3.1-2: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
The notification is received successfully. |
||
n/a |
307 Temporary Redirect |
Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative AF where the notification should be sent. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
n/a |
308 Permanent Redirect |
Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative AF where the notification should be sent. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. |
Table 5.19.4.2.3.1-3: Headers supported by the 307 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI representing the end point of an alternative AF towards which the notification should be redirected. |
Table 5.19.4.2.3.1-4: Headers supported by the 308 Response Code on this resource
Name |
Data type |
P |
Cardinality |
Description |
Location |
string |
M |
1 |
An alternative URI representing the end point of an alternative AF towards which the notification should be redirected. |
5.19.4.2.3.2 Notification via Websocket
If supported by both AF and NEF and successfully negotiated, the Notification of Allocated MBS TMGI(s) Timer Expiry may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4 of 3GPP TS 29.122 [4].
5.19.5 Data Model
5.19.5.1 General
This clause specifies the application data model supported by the MBSTMGI API. Table 5.19.5.1-1 specifies the data types defined for the MBSTMGI API.
Table 5.19.5.1-1: MBSTMGI specific Data Types
Data type |
Clause defined |
Description |
Applicability |
TmgiAllocRequest |
5.19.5.2.2 |
Represents the full set of parameters to initiate a TMGI(s) allocation request or the refresh of the expiry time of already allocated TMGI(s). |
|
TmgiAllocResponse |
5.19.5.2.3 |
Represents TMGI(s) allocation information or the refreshed expiry time for already allocated TMGI(s). |
|
TmgiDeallocRequest |
5.19.5.2.4 |
Represents information to request the deallocation of TMGI(s). |
|
ExpiryNotif |
5.19.5.2.5 |
Represents TMGI(s) timer expiry notification information. |
Table 5.19.5.1-2 specifies data types re-used by the MBSTMGI API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the MBSTMGI API.
Table 5.19.5.1-2: MBSTMGI API re-used Data Types
Data type |
Reference |
Comments |
Applicability |
Tmgi |
3GPP TS 29.571 [8] |
Contains a TMGI. |
|
TmgiAllocate |
3GPP TS 29.532 [52] |
Contains parameters to initiate a TMGI(s) allocation request or the refresh of the expiry time of already allocated TMGI(s). |
|
TmgiAllocated |
3GPP TS 29.532 [52] |
Contains the TMGI(s) allocation information or the refreshed expiry time for already allocated TMGI(s). |
|
Uri |
3GPP TS 29.122 [4] |
Contains a TMGI. |
|
WebsockNotifConfig |
3GPP TS 29.122 [4] |
Contains the configuration parameters to set up notification delivery over Websocket protocol. |
5.19.5.2 Structured data types
5.19.5.2.1 Introduction
This clause defines the structured data types to be used in resource representations.
5.19.5.2.2 Type: TmgiAllocRequest
Table 5.19.5.2.2-1: Definition of type TmgiAllocRequest
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
afId |
string |
M |
1 |
Contains the identifier of the AF that is sending the request. |
|
tmgiParams |
TmgiAllocate |
M |
1 |
Contains the parameters to request the allocation of TMGI(s) for new MBS session(s) or the refresh of the expiry time of already allocated MBS TMGI(s). |
|
notificationUri |
Uri |
O |
0..1 |
The notification URI via which the AF desires to receive notifications on timer expiry for MBS TMGI(s). |
|
requestTestNotification |
boolean |
O |
0..1 |
Indicates whether sending a test notification shall be performed. Set to "true" by the AF to request the NEF to send a test notification as defined in clause 5.2.5.3 of 3GPP TS 29.122 [4]. Set to "false" or omitted otherwise. |
Notification_test_event |
websockNotifConfig |
WebsockNotifConfig |
O |
0..1 |
Represents configuration parameters to set up notification delivery over the Websocket protocol. |
Notification_websocket |
suppFeat |
SupportedFeatures |
C |
0..1 |
Indicates the features supported by the AF. This attribute shall be provided if feature negotiation needs to take place. |
5.19.5.2.3 Type: TmgiAllocResponse
Table 5.19.5.2.3-1: Definition of type TmgiAllocResponse
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
tmgiInfo |
TmgiAllocated |
M |
1 |
Contains the MBS TMGI(s) allocation information or the refreshed expiry time for already allocated MBS TMGI(s). |
|
suppFeat |
SupportedFeatures |
C |
0..1 |
Indicates the features supported by both the AF and the NEF. This attribute shall be provided if feature negotiation needs to take place and it was provided by the AF in the corresponding request body. |
5.19.5.2.4 Type: TmgiDeallocRequest
Table 5.19.5.2.4-1: Definition of type TmgiDeallocRequest
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
afId |
string |
M |
1 |
Contains the identifier of the AF that is sending the request. |
|
tmgis |
array(Tmgi) |
M |
1..N |
Contains the list of TMGI(s) to be deallocated. |
5.19.5.2.5 Type: ExpiryNotif
Table 5.19.5.2.5-1: Definition of type ExpiryNotif
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
tmgis |
array(Tmgi) |
M |
1..N |
Contains the list of previously allocated MBS TMGI(s) for which the timer expired. |
5.19.5.3 Simple data types and enumerations
5.19.5.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
5.19.5.3.2 Simple data types
The simple data types defined in Table 5.19.5.3.2-1 shall be supported.
Table 5.19.5.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
Applicability |
5.19.6 Used Features
The table below defines the features applicable to the MBSTMGI API. Those features are negotiated as described in clause 5.2.7 of 3GPP TS 29.122 [4].
Table 5.19.6-1: Features used by MBSTMGI API
Feature number |
Feature Name |
Description |
1 |
Notification_websocket |
The delivery of notifications over Websocket is supported as described in 3GPP TS 29.122 [4]. This feature requires that the Notification_test_event feature is also supported. |
2 |
Notification_test_event |
The testing of notification connection is supported as described in 3GPP TS 29.122 [4]. |
5.19.7 Error handling
5.19.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.6 of 3GPP TS 29.122 [4].
In addition, the requirements in the following subclauses shall apply.
5.19.7.2 Protocol Errors
In this Release of the specification, there are no additional protocol errors applicable for the MBSTMGI API.
5.19.7.3 Application Errors
The application errors defined for the MBSTMGI API are listed in table 5.19.7.3-1.
Table 5.19.7.3-1: Application errors
Application Error |
HTTP status code |
Description |