5.16 EcsAddressProvision API
29.5223GPP5G SystemNetwork Exposure Function Northbound APIsRelease 18Stage 3TS
5.16.1 Resources
5.16.1.1 Overview
All resource URIs of this API should have the following root:
{apiRoot}/3gpp-ecs-address-provision/v1
"apiRoot" is set as described in clause 5.2.4 in 3GPP TS 29.122 [4]. "apiName" shall be set to "3gpp-ecs-address-provision" and "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.
This clause describes the structure for the Resource URIs as shown in figure 5.16.1.1-1 and the resources and HTTP methods used for the EcsAddressProvision API.
Figure 5.16.1.1-1: Resource URI structure of the EcsAddressProvision API
Table 5.16.1.1-1 provides an overview of the resources and HTTP methods applicable for the EcsAddressProvision API.
Table 5.16.1.1-1: Resources and methods overview
|
Resource name |
Resource URI |
HTTP method |
Description |
|
ECS Address Provision Configurations |
/{afId}/configurations |
GET |
Read all configurations for a given AF identified by {afId} |
|
POST |
Create a new configuration to provision ECS address(es) |
||
|
Individual ECS Address Provision Configuration |
/{afId}/configurations/{configurationId} |
GET |
Read an existing configuration identified by {configurationId} |
|
PUT |
Modify all of the properties of an existing configuration identified by {configurationId} |
||
|
DELETE |
Delete a configuration identified by {configurationId} |
5.16.1.2 Resource: ECS Address Provision Configurations
5.16.1.2.1 Introduction
This resource allows a AF to read all active ECS Address Provision Configurations for a given AF, or create an new Individual ECS Address Provision Configuration to the NEF.
5.16.1.2.2 Resource Definition
Resource URI: {apiRoot}/3gpp-ecs-address-provision/v1/{afId}/configurations
This resource shall support the resource URI variables defined in table 5.16.1.2.2-1.
Table 5.16.1.2.2-1: Resource URI variables for this resource
|
Name |
Data type |
Definition |
|
apiRoot |
string |
Clause 5.2.4 of 3GPP TS 29.122 [4]. |
|
afId |
string |
Identifier of the AF. |
5.16.1.2.3 Resource Methods
5.16.1.2.3.1 General
The following clauses specify the resource methods supported by the resource as described in clause 5.16.1.2.2.
5.16.1.2.3.2 GET
The GET method allows to read all active configurations for a given AF. The AF shall initiate the HTTP GET request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.16.1.2.3.2-1.
Table 5.16.1.2.3.2-1: URI query parameters supported by the GET method on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
N/A |
This method shall support the request data structures specified in table 5.16.1.2.3.2-2 and the response data structures and response codes specified in table 5.16.1.2.3.2-3.
Table 5.16.1.2.3.2-2: Data structures supported by the GET Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
N/A |
Table 5.16.1.2.3.2-3: Data structures supported by the GET Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
array(EcsAddressProvision) |
M |
0..N |
200 OK |
All the configurations for the AF are returned. |
|
N/A |
307 Temporary Redirect |
Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource 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, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource 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 GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. |
||||
Table 5.16.1.2.3.2-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 in an alternative NEF. |
Table 5.16.1.2.3.2-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 in an alternative NEF. |
5.16.1.2.3.3 POST
The POST method creates a new resource to Individual ECS Address Provision Configuration for a given AF. The AF shall initiate the HTTP POST request message and the NEF shall respond to the message. The NEF shall construct the URI of the created resource.
This method shall support the request data structures specified in table 5.16.1.2.3.3-1 and the response data structures and response codes specified in table 5.16.1.2.3.3-2.
Table 5.16.1.2.3.3-1: Data structures supported by the POST Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
EcsAddressProvision |
M |
1 |
Parameters to create a confirguation to provision ECS address. |
Table 5.16.1.2.3.3-2: Data structures supported by the POST Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
EcsAddressProvision |
M |
1 |
201 Created |
The configuration 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 of 3GPP TS 29.122 [4] also apply. |
||||
Table 5.16.1.2.3.3-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-ecs-address-provision/v1/{afId}/configurations/{configurationId} |
5.16.1.3 Resource: Individual ECS Address Provision Configuration
5.16.1.3.1 Introduction
This resource allows a AF to read, update or delete an existing Individual ECS Address Provision Configuration.
5.16.1.3.2 Resource Definition
Resource URI: {apiRoot}/3gpp-ecs-address-provision/v1/{afId}/configurations/{configurationId}
This resource shall support the resource URI variables defined in table 5.16.1.3.2-1.
Table 5.16.1.3.2-1: Resource URI variables for this resource
|
Name |
Data type |
Definition |
|
apiRoot |
string |
Clause 5.2.4 of 3GPP TS 29.122 [4]. |
|
afId |
string |
Identifier of the AF. |
|
configurationId |
string |
Identifier of the configuration resource. |
5.16.1.3.3 Resource Methods
5.16.1.3.3.1 General
The following clauses specify the resource methods supported by the resource as described in clause 5.16.1.3.2.
5.16.1.3.3.2 GET
The GET method allows to read the active configuration for a given AF and a given configuration Id. The AF shall initiate the HTTP GET request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.16.1.3.3.2-1.
Table 5.16.1.3.3.2-1: URI query parameters supported by the GET method on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
N/A |
This method shall support the request data structures specified in table 5.16.1.3.3.2-2 and the response data structures and response codes specified in table 5.16.1.3.3.2-3.
Table 5.16.1.3.3.2-2: Data structures supported by the GET Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
N/A |
Table 5.16.1.3.3.2-3: Data structures supported by the GET Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
EcsAddressProvision |
M |
1 |
200 OK |
The information for the configuration in the request URI are returned. |
|
N/A |
307 Temporary Redirect |
Temporary redirection, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource 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, during configuration retrieval. The response shall include a Location header field containing an alternative URI of the resource 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 GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. |
||||
Table 5.16.1.3.3.2-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 in an alternative NEF. |
Table 5.16.1.3.3.2-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 in an alternative NEF. |
5.16.1.3.3.3 PUT
The PUT method is used to replace an existing Individual ECS Address Provision Configuration. The AF shall initiate the HTTP PUT request message and the NEF shall respond to the message.
This method shall support the request data structures specified in table 5.16.1.3.3.3-1 and the response data structures and response codes specified in table 5.16.1.3.3.3-2.
Table 5.16.1.3.3.3-1: Data structures supported by the PUT Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
EcsAddressProvision |
M |
1 |
Replace an existing Individual ECS Address Provision Configuration. |
Table 5.16.1.3.3.3-2: Data structures supported by the PUT Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
EcsAddressProvision |
M |
1 |
200 OK |
The configuration was updated successfully. |
|
N/A |
204 No Content |
The configuration was updated successfully. |
||
|
N/A |
307 Temporary Redirect |
Temporary redirection, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource 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, during configuration modification. The response shall include a Location header field containing an alternative URI of the resource 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 PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. |
||||
Table 5.16.1.3.3.3-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 NEF. |
Table 5.16.1.3.3.3-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 NEF. |
5.16.1.3.3.4 DELETE
The DELETE method deletes an existing Individual ECS Address Provision Configuration. The AF shall initiate the HTTP DELETE request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.7.1.3.3.4-1.
Table 5.7.1.3.3.4-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 5.7.1.3.3.4-2 and the response data structures and response codes specified in table 5.7.1.3.3.4-3.
Table 5.7.1.3.3.4-2: Data structures supported by the DELETE Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
N/A |
Table 5.7.1.3.3.4-3: Data structures supported by the DELETE Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
N/A |
204 No Content |
The configuration was terminated successfully. |
||
|
N/A |
307 Temporary Redirect |
Temporary redirection, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource 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, during configuration termination. The response shall include a Location header field containing an alternative URI of the resource 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 DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. |
||||
Table 5.7.1.3.3.4-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 in an alternative NEF. |
Table 5.7.1.3.3.4-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 in an alternative NEF. |
5.16.1A Notifications
Notifications are not applicable to this API.
5.16.2 Data Model
5.16.2.1 General
This clause specifies the application data model supported by the EcsAddressProvision API.
Table 5.16.2.1-1 specifies the data types defined for the EcsAddressProvision API.
Table 5.16.2.1-1: EcsAddressProvision API specific Data Types
|
Data type |
Clause defined |
Description |
Applicability |
|
EcsAddressProvision |
5.16.2.3.2 |
Represents ECS address provision configuration information. |
5.16.2.2 Reused data types
The data types reused by the EcsAddressProvision API from other specifications are listed in table 5.16.2.2-1.
Table 5.16.2.2-1: Re-used Data Types
|
Data type |
Reference |
Comments |
|
EcsServerAddr |
3GPP TS 29.571 [8] |
|
|
Link |
3GPP TS 29.122 [4] |
Identifies a referenced resource. |
|
SpatialValidityCond |
3GPP TS 29.571 [8] |
|
|
SupportedFeatures |
3GPP TS 29.571 [8] |
Used to negotiate the applicability of the optional features defined in table 5.16.3-1. |
5.16.2.3 Structured data types
5.16.2.3.1 Introduction
This clause defines the structured data types to be used in resource representations.
5.16.2.3.2 Type: EcsAddressProvision
Table 5.16.2.3.2-1: Definition of type EcsAddressProvision
|
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
self |
Link |
C |
0..1 |
Identifies the individual configuration resource. Shall be present in the HTTP GET response when reading all the configurations for an AF. |
|
|
ecsServerAddr |
EcsServerAddr |
M |
1 |
Represents the ECS address(es). |
|
|
spatialValidityCond |
SpatialValidityCond |
O |
0..1 |
Spatial validity condition. |
|
|
tgtUe |
TargetUeId |
O |
0..1 |
Target UE information. |
|
|
suppFeat |
SupportedFeatures |
M |
1 |
Indicates the negotiated supported features. |
5.16.2.4 Simple data types and enumerations
5.16.2.4.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
5.16.2.4.2 Simple data types
The simple data types defined in table 5.16.2.4.2-1 shall be supported.
Table 5.16.2.4.2-1: Simple data types
|
Type Name |
Type Definition |
Description |
Applicability |
5.16.3 Used Features
The table below defines the features applicable to the EcsAddressProvision API. Those features are negotiated as described in clause 5.2.7 of 3GPP TS 29.122 [4].
Table 5.16.3-1: Features used by EcsAddressProvision API
|
Feature number |
Feature Name |
Description |
5.16.4 Error handling
5.16.4.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 clauses shall apply.
5.16.4.2 Protocol Errors
In this Release of the specification, there are no additional protocol errors applicable for the EcsAddressProvision API.
5.16.4.3 Application Errors
The application errors defined for EcsAddressProvision API are listed in table 5.16.4.3-1.
Table 5.16.4.3-1: Application errors
|
Application Error |
HTTP status code |
Description |
Applicability |
5.17 AMPolicyAuthorization API
5.17.1 Resources
5.17.1.1 Overview
All resource URIs of this API should have the following root:
{apiRoot}/3gpp-am-policyauthorization/v1
"apiRoot" is set as described in clause 5.2.4 in 3GPP TS 29.122 [4]. "apiName" shall be set to "3gpp-am-policyauthorization" and "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.
This clause describes the structure for the Resource URIs as shown in figure 5.17.1.1-1 and the resources and HTTP methods used for the AMPolicyAuthorization API.
Figure 5.17.1.1-1: Resource URI structure of the AMPolicyAuthorization API
Table 5.17.1.1-1 provides an overview of the resources and HTTP methods applicable for the AMPolicyAuthorization API.
Table 5.17.1.1-1: Resources and methods overview
|
Resource name |
Resource URI |
HTTP method |
Description |
|
Application AM Contexts |
/{afId}/app-am-contexts |
POST |
Create a new Individual application AM context resource and may create the child AM Policy Events Subscription sub-resource. |
|
Individual application AM Context |
/{afId}/app-am-contexts/{appAmContextId} |
GET |
Reads an existing Individual application AM context resource. |
|
PATCH |
Updates an existing Individual application AM context resource. It can also create or update an AM Policy Events Subscription sub-resource. |
||
|
DELETE |
Deletes an existing Individual application AM context resource and the child AM Policy Events Subscription sub-resource. |
||
|
AM Policy Events Subscription |
/{afId}/app-am-contexts/{appAmContextId}/events-subscription |
PUT |
Creates a new AM Policy Events Subscription sub-resource or modifies an existing AM Policy Events Subscription sub-resource. |
|
DELETE |
Deletes an AM Policy Events Subscription sub-resource. |
5.17.1.2 Resource: Application AM Contexts
5.17.1.2.1 Introduction
This resource allows an AF to request the creation of a new Individual application AM context resource.
5.17.1.2.2 Resource Definition
Resource URI: {apiRoot}/3gpp-am-policyauthorization/v1/{afId}/app-am-contexts
This resource shall support the resource URI variables defined in table 5.17.1.2.2-1.
Table 5.17.1.2.2-1: Resource URI variables for this resource
|
Name |
Data type |
Definition |
|
apiRoot |
string |
Clause 5.2.4 of 3GPP TS 29.122 [4]. |
|
afId |
string |
Identifier of the AF. |
5.17.1.2.3 Resource Methods
5.17.1.2.3.1 General
The following clauses specify the resource methods supported by the resource as described in clause 5.17.1.2.2.
5.17.1.2.3.2 POST
The POST method creates a new resource to Individual application AM context for a given AF. The AF shall initiate the HTTP POST request message and the NEF shall respond to the message. The NEF shall construct the URI of the created resource.
This method shall support the request data structures specified in table 5.17.1.2.3.2-1 and shall support the response data structures and response codes specified in table 5.17.1.2.3.2-2.
Table 5.17.1.2.3.2-1: Data structures supported by the POST Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
AppAmContextExpData |
M |
1 |
Contains the exposure information for the creation of a new Individual application AM context resource. |
Table 5.17.1.2.3.2-2: Data structures supported by the POST Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
AppAmContextExpRespData |
M |
1 |
201 Created |
Successful case. The Individual application AM context resource was created successfully. The URI of the created resource shall be returned in the "Location" HTTP header. |
|
ProblemDetails |
O |
0..1 |
500 Internal Server Error |
(NOTE 2) |
|
NOTE 1: 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. NOTE 2: Failure causes are described in clause 5.17.5. |
||||
Table 5.17.1.2.3.2-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-am-policyauthorization/v1/{afId}/ app-am-contexts/{appAmContextId} |
5.17.1.3 Resource: Individual Application AM Context
5.17.1.3.1 Introduction
This resource allows an AF to read, update or delete an existing Individual application AM context.
5.17.1.3.2 Resource Definition
Resource URI: {apiRoot}/3gpp-am-policyauthorization/v1/{afId}/app-am-contexts/{appAmContextId}
This resource shall support the resource URI variables defined in table 5.17.1.3.2-1.
Table 5.17.1.3.2-1: Resource URI variables for this resource
|
Name |
Data type |
Definition |
|
apiRoot |
string |
Clause 5.2.4 of 3GPP TS 29.122 [4]. |
|
afId |
string |
Identifier of the AF. |
|
appAmContextId |
string |
Identifier of the application AM context formatted according to IETF RFC 3986 [44]. |
5.17.1.3.3 Resource Methods
5.17.1.3.3.1 General
The following clauses specify the resource methods supported by the resource as described in clause 5.17.1.3.2.
5.17.1.3.3.2 GET
The GET method allows to read the existing application AM context for a given AF and a given application AM context Id. The AF shall initiate the HTTP GET request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.17.1.3.3.2-1.
Table 5.17.1.3.3.2-1: URI query parameters supported by the GET method on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
N/A |
This method shall support the request data structures specified in table 5.17.1.3.3.2-2, the response data structures and response codes specified in table 5.17.1.3.3.2-3 and the Location Headers specified in table 5.17.1.3.3.2-4 and table 5.17.1.3.3.2-5.
Table 5.17.1.3.3.2-2: Data structures supported by the GET Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
N/A |
Table 5.17.1.3.3.2-3: Data structures supported by the GET Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
AppAmContextExpData |
M |
1 |
200 OK |
Successful case. The exposure information of an existing Individual application AM context in the request URI is returned. |
|
N/A |
307 Temporary Redirect |
Temporary redirection, during the AM context retrieval. The response shall include a Location header field containing an alternative URI of the resource 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, during the AM context retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
|
ProblemDetails |
O |
0..1 |
404 Not Found |
(NOTE 2) |
|
NOTE 1: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. NOTE 2: Failure causes are described in clause 5.17.5. |
||||
Table 5.17.1.3.3.2-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 in an alternative NEF. |
Table 5.17.1.3.3.2-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 in an alternative NEF. |
5.17.1.3.3.3 PATCH
The PATCH method is used to modify an existing Individual application AM context. The AF shall initiate the HTTP PATCH request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.17.1.3.3.3-1.
Table 5.17.1.3.3.3-1: URI query parameters supported by the PATCH method on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
n/a |
This method shall support the request data structures specified in table 5.17.1.3.3.3-2, the response data structures and response codes specified in table 5.17.1.3.3.3-3 and the Location Headers specified in table 5.17.1.3.3.3-4 and table 5.17.1.3.3.3-5.
Table 5.17.1.3.3.3-2: Data structures supported by the PATCH Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
AppAmContextExpUpdateData |
M |
1 |
Contains the modification(s) to be applied to the Individual application AM context resource. |
Table 5.17.1.3.3.3-3: Data structures supported by the PATCH Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
AppAmContextExpRespData |
M |
1 |
200 OK |
Successful case. The exposure information of the updated application AM context. |
|
N/A |
204 No Content |
The application AM context was updated successfully. |
||
|
N/A |
307 Temporary Redirect |
Temporary redirection, during the AM context modification. The response shall include a Location header field containing an alternative URI of the resource 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, during the AM context modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
|
ProblemDetails |
O |
0..1 |
400 Bad Request |
(NOTE 2) |
|
ProblemDetails |
O |
0..1 |
404 Not Found |
(NOTE 2) |
|
NOTE 1: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. NOTE 2: Failure causes are described in clause 5.17.5. |
||||
Table 5.17.1.3.3.3-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 in an alternative NEF. |
Table 5.17.1.3.3.3-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 in an alternative NEF. |
5.17.1.3.3.4 DELETE
The DELETE method deletes an existing Individual application AM context. The AF shall initiate the HTTP DELETE request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.17.1.3.3.4-1.
Table 5.17.1.3.3.4-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 5.17.1.3.3.4-2 and the response data structures and response codes specified in table 5.17.1.3.3.4-3, and the Location Headers specified in table 5.17.1.3.3.4-4 and table 5.17.1.3.3.4-5.
Table 5.17.1.3.3.4-2: Data structures supported by the DELETE Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
N/A |
Table 5.17.1.3.3.4-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 case. The application AM context was terminated successfully. |
||
|
N/A |
307 Temporary Redirect |
Temporary redirection, during the AM context termination. The response shall include a Location header field containing an alternative URI of the resource 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, during the AM context termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
|
ProblemDetails |
O |
0..1 |
404 Not Found |
(NOTE 2) |
|
NOTE 1: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. NOTE 2: Failure causes are described in clause 5.17.5. |
||||
Table 5.17.1.3.3.4-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 in an alternative NEF. |
Table 5.17.1.3.3.4-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 in an alternative NEF. |
5.17.1.4 Resource: AM Policy Events Subscription
5.17.1.4.1 Introduction
This resource allows an AF to create a new AM policy events subscription sub-resource or modifies an existing AM policy events subscription sub-resource.
5.17.1.4.2 Resource Definition
Resource URI: {apiRoot}/3gpp-am-policyauthorization/v1/{afId}/app-am-contexts/{appAmContextId}/events-subscription
This sub-resource shall support the resource URI variables defined in table 5.17.1.4.2-1.
Table 5.17.1.4.2-1: Resource URI variables for this resource
|
Name |
Data type |
Definition |
|
apiRoot |
string |
Clause 5.2.4 of 3GPP TS 29.122 [4]. |
|
afId |
string |
Identifier of the AF. |
|
appAmContextId |
string |
Identifier of the application AM context formatted according to IETF RFC 3986 [44]. |
5.17.1.4.3 Resource Methods
5.17.1.4.3.1 General
The following clauses specify the resource methods supported by the sub-resource as described in clause 5.17.1.4.2.
5.17.1.4.3.2 PUT
The PUT method allows to create a new AM policy events subscription sub-resource in an existing application AM context or modifies an existing AM policy events subscription sub-resource. The AF shall initiate the HTTP PUT request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.17.1.4.3.2-1.
Table 5.17.1.4.3.2-1: URI query parameters supported by the PUT method on this resource
|
Name |
Data type |
P |
Cardinality |
Description |
|
N/A |
This method shall support the request data structures specified in table 5.17.1.4.3.2-2, the response data structures and response codes specified in table 5.17.1.4.3.2-3 and the Location Headers specified in table 5.17.1.4.3.2-4, table 5.17.1.4.3.2-5 and table 5.17.1.4.3.2-6.
Table 5.17.1.4.3.2-2: Data structures supported by the PUT Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
AmEventsSubscData |
M |
1 |
Contains the information for the creation and/or modification of the AM Policy Events Subscription. |
Table 5.17.1.4.3.2-3: Data structures supported by the PUT Response Body on this resource
|
Data type |
P |
Cardinality |
Response codes |
Description |
|
AmEventsSubscRespData |
M |
1 |
201 Created |
Successful case. The AM policy events subscription sub-resource was created. The representation of the AM Policy Events Subscription sub-resource is included within the properties of the AmEventsSubscData data type. The one or more matched events, if available, are included within the properties of the AmEventsNotification data type. |
|
AmEventsSubscRespData |
M |
1 |
200 OK |
Successful case. The AM policy events subscription sub-resource was modified and a representation of the sub-resource is returned. The representation of the AM Policy Events Subscription sub-resource is included within the properties of the AmEventsSubscData data type. The one or more matched events, if available, are included within the properties of the AmEventsNotification data type. |
|
N/A |
204 No Content |
Successful case. The AM policy events subscription sub-resource was modified successfully, with no content to be sent in the response message body. |
||
|
N/A |
307 Temporary Redirect |
Temporary redirection, during the AM policy events subscription or modification. The response shall include a Location header field containing an alternative URI of the resource 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, during the AM policy events subscription or modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
|
ProblemDetails |
O |
0..1 |
404 Not Found |
(NOTE 2) |
|
NOTE 1: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. NOTE 2: Failure causes are described in clause 5.17.5. |
||||
Table 5.17.1.4.3.2-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 resource in which an AM policy events subscription sub-resource has been created, according to the structure: |
Table 5.17.1.4.3.2-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 in an alternative NEF. |
Table 5.17.1.4.3.2-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 in an alternative NEF. |
5.17.1.4.3.3 DELETE
The DELETE method deletes existing subscribed AM policy event(s) within the existing Individual application AM context. The AF shall initiate the HTTP DELETE request message and the NEF shall respond to the message.
This method shall support the URI query parameters specified in table 5.17.1.4.3.3-1.
Table 5.17.1.4.3.3-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 5.17.1.4.3.3-2 and the response data structures and response codes specified in table 5.17.1.4.3.3-3 and the Location Headers specified in table 5.17.1.4.3.3-4 and table 5.17.1.4.3.3-5.
Table 5.17.1.4.3.3-2: Data structures supported by the DELETE Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
N/A |
Table 5.17.1.4.3.3-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 case. The AM policy event(s) subscription resource is deleted. |
||
|
N/A |
307 Temporary Redirect |
Temporary redirection, during the AM policy events deletion. The response shall include a Location header field containing an alternative URI of the resource 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, during the AM policy events deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative NEF. Redirection handling is described in clause 5.2.10 of 3GPP TS 29.122 [4]. |
||
|
ProblemDetails |
O |
0..1 |
404 Not Found |
(NOTE 2) |
|
NOTE 1: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [4] also apply. NOTE 2: Failure causes are described in clause 5.17.5. |
||||
Table 5.17.1.4.3.3-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 in an alternative NEF. |
Table 5.17.1.4.3.3-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 in an alternative NEF. |
5.17.2 Notifications
5.17.2.1 Introduction
Upon receipt of AM Event Notification from the PCF indicating the subscribed AM policy event is detected, the NEF shall send an HTTP POST message including the notified AM policy event to the AF. The NEF and the AF shall support the notification mechanism as described in clause 5.2.5 of 3GPP TS 29.122 [4].
Table 5.17.2.1-1: Notifications overview
|
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
|
AM Event Notification |
{eventNotifUri} |
POST |
The AM policy changes event notification is provided by the NEF to the AF. |
5.17.2.2 AM Event Notification
5.17.2.2.1 Description
The AM Event Notification is used by the NEF to report one or several observed AM policy change events to AF that has subscribed to such Notifications via the AM policy events subscription sub-resource.
5.17.2.2.2 Callback URI
The Callback URI "{eventNotifUri}" shall be used with the callback URI variables defined in table 5.17.2.2.2-1.
Table 5.17.2.2.2-1: Callback URI variables
|
Name |
Definition |
|
eventNotifUri |
Callback reference provided by the AF during creation/modification of the subscription within the AM policy events subscription sub-resource as defined in Table 5.17.3.3.2-1 or Table 5.17.3.3.3-1 or Table 5.6.2.4-1 of 3GPP TS 29.534 [43]. |
5.17.2.2.3 Operation Definition
5.17.2.2.3.1 Notification via HTTP POST
This method shall support the request data structures specified in table 5.17.2.2.3.1-1 and the response data structures and response codes specified in table 5.17.2.2.3.1-2 and the Location Headers specified in table 5.17.2.2.3.1-3 and table 5.17.2.2.3.1-4.
Table 5.17.2.2.3.1-1: Data structures supported by the POST Request Body on this resource
|
Data type |
P |
Cardinality |
Description |
|
AmEventsNotification |
M |
1 |
Provides information about the observed access and mobility policy change events by the NEF to the AF. |
Table 5.17.2.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 event 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.17.2.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.17.2.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.17.2.2.3.2 Notification via Websocket
If supported by both AF and NEF and successfully negotiated, the AM Event Notification may alternatively be delivered through the Websocket mechanism as defined in clause 5.2.5.4 of 3GPP TS 29.122 [4].
5.17.3 Data Model
5.17.3.1 General
This clause specifies the application data model supported by the AMPolicyAuthorization API.
Table 5.17.3.1-1 specifies the data types defined for the AMPolicyAuthorization API.
Table 5.17.3.1-1: AMPolicyAuthorization API specific Data Types
|
Data type |
Clause defined |
Description |
Applicability |
|
AppAmContextExpData |
5.17.3.3.2 |
Represents an Individual application AM context exposure resource. |
|
|
AppAmContextExpRespData |
5.17.3.5.1 |
Represents a response to a modification or creation request of an Individual Application AM context resource. It may contain the notification of the already met events. |
|
|
AppAmContextExpUpdateData |
5.17.3.3.3 |
Contains the modification(s) to be applied to the Individual application AM context exposure resource. |
|
|
GeographicalArea |
5.17.3.3.4 |
Contains geographical area information (e.g. a civic address or shapes). |
5.17.3.2 Reused data types
The data types reused by the AMPolicyAuthorization API from other specifications are listed in table 5.17.3.2-1.
Table 5.17.3.2-1: Re-used Data Types
|
Data type |
Reference |
Comments |
|
AmEventsNotification |
3GPP TS 29.534 [43] |
Describes the notification about the events occurred within an Individual application AM context resource. |
|
AmEventsSubscData |
3GPP TS 29.534 [43] |
Identifies the AM policy events the application subscribes to. |
|
AmEventsSubscDataRm |
3GPP TS 29.534 [43] |
This data type is defined in the same way as the "AmEventsSubscData" data type, but with the OpenAPI "nullable: true" property. |
|
AmEventsSubscRespData |
3GPP TS 29.534 [43] |
It represents a response to an AM policy events subscription request and contains the created/updated AM Policy Events Subscription resource. It may also include the Notification of the events met at the time of subscription. |
|
CivicAddress |
3GPP TS 29.572 [34] |
Identifies the civic address. |
|
DurationSec |
3GPP TS 29.122 [4] |
Indicates the time duration. |
|
DurationSecRm |
3GPP TS 29.122 [4] |
Indicates the time duration, same as the "DurationSec" data type, but with the OpenAPI "nullable: true" property. |
|
GeographicArea |
3GPP TS 29.572 [34] |
Identifies the geographical information with shapes. |
|
Gpsi |
3GPP TS 29.571 [8] |
Identifies a GPSI. |
|
Link |
3GPP TS 29.122 [4] |
Identifies a referenced resource. |
|
SupportedFeatures |
3GPP TS 29.571 [8] |
Used to negotiate the applicability of the optional features defined in table 5.17.4-1. |
|
WebsockNotifConfig |
3GPP TS 29.122 [4] |
Contains the configuration parameters to set up notification delivery over Websocket protocol. |
5.17.3.3 Structured data types
5.17.3.3.1 Introduction
This clause defines the structured data types to be used in resource representations.
5.17.3.3.2 Type: AppAmContextExpData
Table 5.17.3.3.2-1: Definition of type AppAmContextExpData
|
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
self |
Link |
C |
0..1 |
Identifies the individual configuration resource. Shall be present in the HTTP GET response when reading all the configurations for an AF. |
|
|
evSubscs |
AmEventsSubscData |
O |
0..1 |
Represents the subscription to one or more AM policy events. |
|
|
gpsi |
Gpsi |
M |
1 |
Identifies the GPSI. |
|
|
highThruInd |
boolean |
C |
0..1 |
Indicates whether high throughput is desired for the indicated UE traffic. Set to "true" if high throughput is desired; otherwise set to "false". Default value is "false" if omitted. (NOTE) |
|
|
covReqs |
array(GeographicalArea) |
C |
1..N |
Identifies the allowed geographical areas. (NOTE) |
|
|
policyDuration |
DurationSec |
O |
0..1 |
Indicates the time duration that the policy shall last. |
|
|
suppFeat |
SupportedFeatures |
C |
0..1 |
Indicates the negotiated supported features.. It shall be supplied by the AF in the POST request that requests a creation of an Individual application AM context resource. It shall be supplied by the NEF in the response to the POST request that requests a creation of an Individual application AM context resource. |
|
|
requestTestNotification |
boolean |
O |
0..1 |
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 |
Configuration parameters to set up notification delivery over Websocket protocol. |
Notification_websocket |
|
NOTE: Either "highThruInd" attribute or "covReqs" attribute or both shall be included. |
|||||
5.17.3.3.3 Type: AppAmContextExpUpdateData
Table 5.17.3.3.3-1: Definition of type AppAmContextExpUpdateData
|
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
evSubscs |
AmEventsSubscDataRm |
O |
0..1 |
Represents the subscription to one or more AM policy events. |
|
|
highThruInd |
boolean |
O |
0..1 |
Indicates whether high throughput is desired for the indicated UE traffic. Set to "true" if high throughput is desired; otherwise set to "false". |
|
|
covReqs |
array(GeographicalArea) |
O |
1..N |
Identifies the allowed geographical areas. (NOTE) |
|
|
policyDuration |
DurationSecRm |
O |
0..1 |
Indicates the time duration that the policy shall last. |
|
|
NOTE: The value of the property shall be set to NULL for removal. |
|||||
5.17.3.3.4 Type: GeographicalArea
Table 5.17.3.3.4-1: Definition of type GeographicalArea
|
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
|
civicAddress |
CivicAddress |
C |
0..1 |
Identifies a civic address. |
|
|
shapes |
GeographicArea |
C |
0..1 |
Identifies a geographic area specified by different shapes. |
|
|
NOTE: One of "civicAddress" attribute or "shapes" attribute shall be included. |
|||||
5.17.3.4 Simple data types and enumerations
5.17.3.4.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
5.17.3.4.2 Simple data types
The simple data types defined in table 5.17.3.4.2-1 shall be supported.
Table 5.17.3.4.2-1: Simple data types
|
Type Name |
Type Definition |
Description |
Applicability |
5.17.3.5 Data types describing alternative data types or combinations of data types
5.17.3.5.1 Type: AppAmContextExpRespData
Table 5.17.3.5.1-1: Definition of type AppAmContextExpRespData as a list of non-exclusive alternatives
|
Data type |
Cardinality |
Description |
Applicability |
|
AmEventsNotification |
0..1 |
It represents the notification of a match event during the creation or modification of the Individual application AM context data. |
|
|
AppAmContextExpData |
1 |
It represents the Individual application AM context resource. |
5.17.4 Used Features
The table below defines the features applicable to the AMPolicyControl API. Those features are negotiated as described in clause 5.2.7 of 3GPP TS 29.122 [4].
Table 5.17.4-1: Features used by AMPolicyAuthorization 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.17.5 Error handling
5.17.5.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 clauses shall apply.
5.17.5.2 Protocol Errors
In this Release of the specification, there are no additional protocol errors applicable for the AMPolicyAuthorization API.
5.17.5.3 Application Errors
The application errors defined for the AMPolicyAuthorization API are listed in table 5.17.5.3-1.
Table 5.17.5.3-1: Application errors
|
Application Error |
HTTP status code |
Description |
|
INVALID_POLICY_REQUEST |
400 Bad Request |
The HTTP request is rejected because the service information for the AM context is invalid or insufficient for the PCF to perform the requested action. |
|
APPLICATION_AM_CONTEXT_NOT_FOUND |
404 Not Found |
The HTTP request is rejected because the specified Individual Application AM Context does not exist. |
|
POLICY_ASSOCIATION_NOT_AVAILABLE |
500 Internal Server Error |
The PCF failed in executing binding with the UE/AM Policy Context. |