5.4 ResourceManagementOfBdt API
29.1223GPPRelease 18T8 reference point for Northbound APIsTS
5.4.1 Overview
The ResourceManagementOfBdt API is a RESTful API that allows the SCS/AS to request background data transfer related conditions for a set of UEs. The ResourceManagementOfBdt API defines a set of data models, resources and the related procedures for the creation and management of the background data transfer request. The corresponding JSON schema for the representation of the resources and operations defined by the ResourceManagementOfBdt API is provided in its complete form in Annex A.4.
5.4.2 Data model
5.4.2.1 Resource data types
5.4.2.1.1 Introduction
This clause defines data structures to be used in resource representations.
Table 5.4.2.1.1-1 specifies data types re-used by the ResourceManagementOfBdt API from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the ResourceManagementOfBdt API.
Table 5.4.2.1.1-1: ResourceManagementOfBdt API re-used Data Types
|
Data type |
Reference |
Comments |
|
GeographicArea |
3GPP TS 29.572 [42] |
Identifies the geographical information of the user(s). |
|
CivicAddress |
3GPP TS 29.572 [42] |
Identifies the civic address information of the user(s). |
|
NetworkAreaInfo |
3GPP TS 29.554 [50] |
Identifies a network area information. |
|
SupportedFeatures |
3GPP TS 29.571 [45] |
Used to negotiate the applicability of the optional features defined in table 5.4.4-1. |
Table 5.4.2.1.1-2 specifies the data types defined for the ResourceManagementOfBdt API.
Table 5.4.2.1.1-2: ResourceManagementOfBdt API specific Data Types
|
Data type |
Clause defined |
Description |
Applicability |
|
Bdt |
5.4.2.1.2 |
Represents a Background Data Transfer subscription. |
|
|
BdtPatch |
5.4.2.1.3 |
Represents a Background Data Transfer subscription modification request. |
|
|
ExNotification |
5.4.2.1.4 |
Represents a Background Data Transfer notification. |
|
|
TrafficDescriptor |
5.4.2.3.2 |
Identify a traffic descriptor as defined in Figure 5.2.2 of 3GPP TS 24.526 [64]. |
|
|
TransferPolicy |
5.4.2.2.2 |
Represents an offered transfer policy sent from the SCEF to the SCS/AS, or a selected transfer policy sent from the SCS/AS to the SCEF. |
5.4.2.1.2 Type: Bdt
This type represents a BDT subscription. The same structure is used in the subscription request and subscription response.
Table 5.4.2.1.2-1: Definition of type Bdt
|
Attribute name |
Data type |
Cardinality |
Description |
Applicability (NOTE 1) |
|
self |
Link |
0..1 |
Link to the resource "Individual BDT Subscription". This parameter shall be supplied by the SCEF in HTTP responses. |
|
|
supportedFeatures |
SupportedFeatures |
0..1 |
Used to negotiate the supported optional features of the API as described in clause 5.2.7. This attribute shall be provided in the POST request and in the response of successful resource creation. |
|
|
volumePerUE |
UsageThreshold |
1 |
Identifies the data volume expected to be transferred per UE. |
|
|
numberOfUEs |
integer |
1 |
Identifies the number of UEs. |
|
|
desiredTimeWindow |
TimeWindow |
1 |
Identifies the time interval. |
|
|
locationArea |
LocationArea |
0..1 |
Identifies the area within which the SCS/AS requests the number of UE. |
Bdt |
|
locationArea5G |
LocationArea5G |
0..1 |
Identifies the area within which the AF requests the number of UE. |
LocBdt_5G |
|
referenceId |
BdtReferenceId |
0..1 |
Identifies a selected policy of background data transfer. |
|
|
transferPolicies |
array(TransferPolicy) |
0..N |
Identifies an offered transfer policy. |
|
|
selectedPolicy |
integer |
0..1 |
Identity of the selected background data transfer policy. Shall not be present in initial message exchange, can be provided by NF service consumer in a subsequent message exchange. |
|
|
externalGroupId |
ExternalGroupId |
0..1 |
Identifies a group of users. (NOTE 2) |
Group_Id |
|
notificationDestination |
Link |
0..1 |
Contains the URI to receive the BDT notification from the NEF. |
BdtNotification_5G |
|
warnNotifEnabled |
boolean |
0..1 |
Indicates whether the BDT warning notification is enabled or not. If it is set to true, the BDT warning notification is enabled; if it is set to false or absent, the BDT warning notification is disabled. |
BdtNotification_5G |
|
trafficDes |
TrafficDescriptor |
0..1 |
Contains the traffic descriptor of the background data. (NOTE 2) |
|
|
NOTE 1: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. NOTE 2: The attribute is only applicable to the NEF. |
||||
5.4.2.1.3 Type: BdtPatch
This type represents a BDT request for the service provided by the SCS/AS to the SCEF via T8 interface. The structure is used for PATCH request.
Table 5.4.2.1.3-1: Definition of type BdtPatch
|
Attribute name |
Data type |
Cardinality |
Description |
Applicability (NOTE) |
|
selectedPolicy |
integer |
1 |
Identity of the selected background data transfer policy. |
|
|
warnNotifEnabled |
boolean |
0..1 |
Indicates whether the BDT warning notification is enabled. – true: the BDT warning notification is enabled; – false: the BDT warning notification is not enabled. |
BdtNotification_5G |
|
notificationDestination |
Link |
0..1 |
Contains the URI to receive the BDT notification from the NEF. |
enNB |
|
NOTE: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. |
||||
5.4.2.1.4 Type: ExNotification
This type represents a BDT notification provided by the NEF to the AF. The structure is used for POST request.
Table 5.4.2.1.4-1: Definition of type ExNotification
|
Attribute name |
Data type |
Cardinality |
Description |
Applicability (NOTE) |
|
bdtRefId |
BdtReferenceId |
1 |
This IE indicates transfer policies of background data transfer which the notification corresponds to. |
|
|
locationArea5G |
LocationArea5G |
0..1 |
This IE represents a network area where a network performance will go below the criteria set by the operator. |
|
|
timeWindow |
TimeWindow |
0..1 |
This IE indicates a time window when a network performance will go below the criteria set by the operator. |
|
|
candPolicies |
array(TransferPolicy) |
0..N |
This IE indicates a list of the candidate transfer policies from which the AF may select a new transfer policy due to network performance degradation. |
|
|
NOTE: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no features are indicated, the related property applies for all the features. |
||||
5.4.2.2 Referenced structured data types
5.4.2.2.1 Introduction
This clause defines structured data types that are referenced from data structures defined in the previous clauses.
5.4.2.2.2 Type: TransferPolicy
This data type represents an offered transfer policy sent from the SCEF to the SCS/AS, or a selected transfer policy sent from the SCS/AS to the SCEF.
Table 5.4.2.2.2-1: Definition of type TransferPolicy
|
Attribute name |
Data type |
Cardinality |
Description |
Applicability (NOTE) |
|
bdtPolicyId |
integer |
1 |
Identifier for the transfer policy |
|
|
maxUplinkBandwidth |
Bandwidth |
0..1 |
Indicates the maximum aggregated bitrate in the uplink authorized by the PCRF. |
|
|
maxDownlinkBandwidth |
Bandwidth |
0..1 |
Indicates the maximum aggregated bitrate in the downlink authorized by the PCRF. |
|
|
ratingGroup |
integer |
1 |
Indicates the rating group during the time window. |
|
|
timeWindow |
TimeWindow |
1 |
Indicates the recommended time window of the transfer policy |
|
|
NOTE: Properties marked with a feature as defined in clause 5.4.4 are applicable as described in clause 5.2.7. If no feature are indicated, the related property applies for all the features. |
||||
5.4.2.3 Referenced simple data types and enumerations
5.4.2.3.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. In addition, data types and enumerations defined in clause 5.2.1 can be referenced.
5.4.2.3.2 Simple data types
The simple data types defined in table 5.4.2.3.2-1 shall be supported.
Table 5.4.2.3.2-1: Simple data types
|
Type name |
Description |
|
TrafficDescriptor |
String identifying a traffic descriptor as defined in table 5.2.1 of 3GPP TS 24.526 [64]. |
5.4.3 Resource structure
5.4.3.1 General
All resource URIs of this API should have the following root:
{apiRoot}/3gpp-bdt/v1
"apiRoot" is set as described in clause 5.2.4. All resource URIs in the clauses below are defined relative to the above root URI.
The following resources and HTTP methods are supported for this API:
Table 5.4.3.1-1: Resources and methods overview
|
Resource name |
Resource URI |
HTTP method |
Meaning |
|
BDT Subscription |
/{scsAsId}/subscriptions |
GET |
Read all active background data transfer subscription resources for a given SCS/AS |
|
POST |
Create a new background data transfer subscription resource |
||
|
Individual BDT Subscription |
/{scsAsId}/subscriptions/{subscriptionId} |
PATCH |
Modify a background data transfer subscription resource to select one of the transfer policies offered by the SCEF |
|
PUT |
Update a background data transfer subscription resource for negotiation of background data transfer policy |
||
|
GET |
Read a background data transfer subscription resource |
||
|
DELETE |
Delete a background data transfer resources |
5.4.3.2 Resource: BDT Subscriptions
5.4.3.2.1 Introduction
This resource allows the SCS/AS to read all active long-term transactions related to BDT resource management.
5.4.3.2.2 Resource definition
Resource URI: {apiRoot}/3gpp-bdt/v1/{scsAsId}/subscriptions
This resource shall support the resource URI variables defined in table 5.4.3.2.2-1.
Table 5.4.3.2.2-1: Resource URI variables for resource "BDT Subscriptions"
|
Name |
Data type |
Definition |
|
apiRoot |
string |
See clause 5.2.4. |
|
scsAsId |
string |
Identifier of the SCS/AS. |
5.4.3.2.3 Resource methods
5.4.3.2.3.1 GET
The GET method allows to read all active resources for a given SCS/AS. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message.
This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.2.3.1-1 and table 5.4.3.2.3.1-2.
Table 5.4.3.2.3.1-1: URI query parameters supported by the GET method on this resource
|
Name |
Data type |
Cardinality |
Remarks |
|
none specified |
Table 5.4.3.2.3.1-2: Data structures supported by the GET request/response by the resource
|
Request body |
Data type |
Cardinality |
Remarks |
|
|
none |
||||
|
Response body |
Data type |
Cardinality |
Response codes |
Remarks |
|
array(Bdt) |
0..N |
200 OK |
The resource information for the SCS/AS in the request URI are returned. |
|
|
none |
307 Temporary Redirect |
Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
none |
308 Permanent Redirect |
Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. |
||||
Table 5.4.3.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 of the resource located in an alternative SCEF. |
Table 5.4.3.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 of the resource located in an alternative SCEF. |
5.4.3.2.3.2 PUT
This HTTP method is not supported for the resource.
5.4.3.2.3.3 PATCH
This HTTP method is not supported for the resource.
5.4.3.2.3.4 POST
The POST method creates a new background data transfer subscription resource for a given SCS/AS. The SCS/AS shall initiate the HTTP POST request message and the SCEF shall respond to the message.
This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.2.3.4-1 and table 5.4.3.2.3.4-2.
Table 5.4.3.2.3.4-1: URI query parameters supported by the POST method on this resource
|
Name |
Data type |
Cardinality |
Remarks |
|
none specified |
Table 5.4.3.2.3.4-2: Data structures supported by the POST request/response by the resource
|
Request body |
Data type |
Cardinality |
Remarks |
|
|
Bdt |
1 |
Parameters to register a subscription to request background data transfer related information with the SCEF. |
||
|
Response body |
Data type |
Cardinality |
Response codes |
Remarks |
|
Bdt |
1 |
201 Created |
The resource was created successfully. The URI of the created resource shall be returned in the "Location" HTTP header. |
|
|
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. |
||||
Table 5.4.3.2.3.4-3: 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}/3gpp-bdt/v1/{scsAsId}/subscriptions/{subscriptionId} |
5.4.3.2.3.5 DELETE
This HTTP method is not supported for the resource.
5.4.3.3 Resource: Individual BDT Subscription
5.4.3.3.1 Introduction
This resource allows the SCS/AS to manage resources for BDT using a long-term transaction.
5.4.3.3.2 Resource definition
Resource URI: {apiRoot}/3gpp-bdt/v1/{scsAsId}/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 5.4.3.3.2-1.
Table 5.4.3.3.2-1: Resource URI variables for resource "Individual BDT Subscription"
|
Name |
Data type |
Definition |
|
apiRoot |
string |
See clause 5.2.4. |
|
scsAsId |
string |
Identifier of the SCS/AS. |
|
subscriptionId |
string |
Identifier of the subscription resource. The subscriptionId corresponds to the stage 2 TLTRI. |
5.4.3.3.3 Resource methods
5.4.3.3.3.1 GET
The GET method allows to read an individual BDT subscription resource to obtain details of an active resource BDT subscription. The SCS/AS shall initiate the HTTP GET request message and the SCEF shall respond to the message.
This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.3.3.1-1 and table 5.4.3.3.3.1-2.
Table 5.4.3.3.3.1-1: URI query parameters supported by the GET method on this resource
|
Name |
Data type |
Cardinality |
Remarks |
|
none specified |
Table 5.4.3.3.3.1-2: Data structures supported by the GET request/response by the resource
|
Request body |
Data type |
Cardinality |
Remarks |
|
|
none |
||||
|
Response body |
Data type |
Cardinality |
Response codes |
Remarks |
|
Bdt |
1 |
200 OK |
The resource information related to the request URI is returned. |
|
|
none |
307 Temporary Redirect |
Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
none |
308 Permanent Redirect |
Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. |
||||
Table 5.4.3.3.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 of the resource located in an alternative SCEF. |
Table 5.4.3.3.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 of the resource located in an alternative SCEF. |
5.4.3.3.3.2 PUT
The PUT method allows the SCS/AS to modify an existing subscription resource completely. It is initiated by the SCS/AS and answered by the SCEF.
This method shall support request and response data structures, and response codes, as specified in the table 5.4.3.3.3.2-1.
Table 5.4.3.3.3.2-1: Data structures supported by the PUT request/response by the resource
|
Request body |
Data type |
Cardinality |
Remarks |
|
|
Bdt |
1 |
The SCS/AS requests to update the BDT policy subscription. |
||
|
Response body |
Data type |
Cardinality |
Response codes |
Remarks |
|
Bdt |
1 |
200 OK |
The subscription was modified successfully. The SCEF shall return an updated subscription in the response payload body. |
|
|
none |
204 No Content |
The subscription was updated successfully. |
||
|
none |
307 Temporary Redirect |
Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
none |
308 Permanent Redirect |
Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. |
||||
Table 5.4.3.3.3.2-2: 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 in an alternative SCEF. |
Table 5.4.3.3.3.2-3: 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 in an alternative SCEF. |
5.4.3.3.3.3 PATCH
The PATCH method allows the SCS/AS to modify an existing subscription resource, in order to notify the SCEF about the selected transfer policy. The SCS/AS shall initiate the HTTP PATCH message and the SCEF shall respond to the message.
This method shall support request and response data structures, and response codes, as specified in the table 5.4.3.3.3.3-1.
Table 5.4.3.3.3.3-1: Data structures supported by the PATCH request/response by the resource
|
Request body |
Data type |
Cardinality |
Remarks |
|
|
BdtPatch |
1 |
Background data transfer policy selected by the SCS/AS. |
||
|
Response body |
Data type |
Cardinality |
Response codes |
Remarks |
|
Bdt |
1 |
200 OK |
The resource was modified successfully. The SCEF shall return an updated subscription in the response payload body. |
|
|
none |
204 No Content |
The resource was modified successfully. |
||
|
none |
307 Temporary Redirect |
Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
none |
308 Permanent Redirect |
Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. |
||||
Table 5.4.3.3.3.3-2: 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 in an alternative SCEF. |
Table 5.4.3.3.3.3-3: 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 in an alternative SCEF. |
5.4.3.3.3.4 POST
This HTTP method is not supported for the resource.
5.4.3.3.3.5 DELETE
The DELETE method deletes the resource and terminates the BDT subscription. The SCS/AS shall initiate the HTTP DELETE message and the SCEF shall respond to the message.
This method shall support the URI query parameters, request and response data structures, and response codes, as specified in the table 5.4.3.3.3.5-1 and table 5.4.3.3.3.5-2.
Table 5.4.3.3.3.5-1: URI query parameters supported by the DELETE method on this resource
|
Name |
Data type |
Cardinality |
Remarks |
|
none specified |
Table 5.4.3.3.3.5-2: Data structures supported by the DELETE request/response by the resource
|
Request body |
Data type |
Cardinality |
Remarks |
|
|
none |
||||
|
Response body |
Data type |
Cardinality |
Response codes |
Remarks |
|
none |
204 No Content |
The resource was terminated successfully. |
||
|
none |
307 Temporary Redirect |
Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
none |
308 Permanent Redirect |
Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative SCEF. Redirection handling is described in clause 5.2.10. |
||
|
NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 also apply. |
||||
Table 5.4.3.3.3.5-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 in an alternative SCEF. |
Table 5.4.3.3.3.5-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 in an alternative SCEF. |
5.4.3.4 Void
5.4.3A Notifications
5.4.3A.1 General
The notifications provided by the ResourceManagementOfBdt API are specified in this clause.
Table 5.4.3A-1: Notifications overview
|
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
|
BDT Warning Notification |
{notificationDestination} |
POST |
Notify the BDT warning from the NEF to the AF identified by the notification destination URI (NOTE) |
|
NOTE: This notification may only be supported in 5G. |
|||
5.4.3A.2 BDT Warning Notification
5.4.3A.2.1 Description
The BDT warning notification allows the NEF to notify the AF of the BDT warning notification. The notification may only be supported in 5G.
5.4.3A.2.2 Target URI
The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 5.4.3A.2.2-1.
Table 5.4.3A.2.2-1: Callback URI variables
|
Name |
Data type |
Definition |
|
notificationDestination |
Link |
Reference provided by the AF when the AF requests to send a BDT warning notification when the network performance in the area of interest goes below the criteria set by the operator. This URI shall be provided within the "notificationDestination" attribute in the Bdt data type. |
5.4.3A.2.3 Standard Methods
5.4.3A.2.3.1 Notification via POST
The POST method allows to notify AS identified by the notification destination URI of the BDT warning by the NEF and the AF shall respond to the message.
This method shall support the request data structures specified in table 5.4.3A.2.3.1-1 and the response data structures and response codes specified in table 5.4.3A.2.3.1-2.
Table 5.4.3A.2.3.1-1: Data structures supported by the POST Request Body
|
Data type |
Cardinality |
Description |
|
ExNotification |
1 |
Representation of the BDT warning notification. |
Table 5.4.3A.2.3.1-2: Data structures supported by the POST Response Body
|
Data type |
Cardinality |
Response codes |
Description |
|
none |
204 No Content |
This case represents a successful notification of BDT warning notification. |
|
|
none |
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 SCS/AS where the notification should be sent. Redirection handling is described in clause 5.2.10. |
|
|
none |
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 SCS/AS where the notification should be sent. Redirection handling is described in clause 5.2.10. |
|
|
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 also apply. |
|||
Table 5.4.3A.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 SCS/AS towards which the notification should be redirected. |
Table 5.4.3A.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 SCS/AS towards which the notification should be redirected. |
5.4.3A.2.3.2 Notification via Websocket
If supported by both AF and NEF and successfully negotiated, the ExNotification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4.
5.4.4 Used Features
The table below defines the features applicable to the ResourceManagementOfBdt API. Those features are negotiated as described in clause 5.2.7.
Table 5.4.4-1: Features used by ResourceManagementOfBdt API
|
Feature Number |
Feature |
Description |
|
1 |
Bdt |
The feature supports the pre-5G (e.g. 4G) requirement. |
|
2 |
LocBdt_5G |
The feature supports the 5G requirement. This feature may only be supported in 5G. |
|
3 |
Group_Id |
The feature supports forwarding an external group identifier of the user. This feature shall not be supported in pre-5G. |
|
4 |
BdtNotification_5G |
The feature supports the sending of BDT notification. This feature includes sending of the BDT warning notification to the AF. This feature may only be supported in 5G. |
|
5 |
enNB |
The feature supports enhancement of northbound interfaces, e.g. enable the SCS/AS to update notification destination during modification procedure. |
|
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "Notification". Description: A clear textual description of the feature. |
||
5.4.5 Error handling
5.4.5.1 General
HTTP error handling shall be supported as specified in clause 5.2.6.
In addition, the requirements in the following clauses shall apply.
5.4.5.2 Protocol Errors
In this Release of the specification, there are no additional protocol errors applicable for the ResourceManagementOfBdt API.
5.4.5.3 Application Errors
The application errors defined for ResourceManagementOfBdt API are listed in table 5.4.5.3-1.
Table 5.4.5.3-1: Application errors
|
Application Error |
HTTP status code |
Description |
Applicability |