5 Npcf_EventExposure Service API
29.5233GPP5G SystemPolicy Control Event Exposure ServiceRelease 18Stage 3TS
5.1 Introduction
The Npcf_EventExposure Service shall use the Npcf_EventExposure API.
The API URI of the Npcf_EventExposure API shall be:
{apiRoot}/<apiName>/<apiVersion>
The request URIs used in HTTP requests from the NF service consumer towards the PCF shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [6], i.e.:
{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>
with the following components:
– The {apiRoot} shall be set as described in 3GPP TS 29.501 [6].
– The <apiName> shall be "npcf-eventexposure".
– The <apiVersion> shall be "v1".
– The <apiSpecificResourceUriPart> shall be set as described in clause 5.3.
5.2 Usage of HTTP
5.2.1 General
HTTP/2, IETF RFC 7540 [16], shall be used as specified in clause 5.2 of 3GPP TS 29.500 [5].
HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [5].
The OpenAPI [7] specification of HTTP messages and content bodies for the Npcf_EventExposure is contained in Annex A.
5.2.2 HTTP standard headers
5.2.2.1 General
See clause 5.2.2 of 3GPP TS 29.500 [5] for the usage of HTTP standard headers.
5.2.2.2 Content type
JSON, IETF RFC 8259 [17], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [5]. The use of the JSON format shall be signalled by the content type "application/json".
"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [18].
5.2.3 HTTP custom headers
5.2.3.1 General
The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [5] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [5] may be supported.
In this Release of the specification, no specific custom headers are defined for the Npcf_EventExposure API.
5.3 Resources
5.3.1 Resource Structure
This clause describes the structure for the Resource URIs and the resources and methods used for the service.
Figure 5.3.1-1 depicts the resource URIs structure for the Npcf_EventExposure API.
Figure 5.3.1-1: Resource URI structure of the Npcf_EventExposure API
Table 5.3.1-1 provides an overview of the resources and applicable HTTP methods.
Table 5.3.1-1: Resources and methods overview
Resource name |
Resource URI |
HTTP method or custom operation |
Description |
Policy Control Events Subscriptions |
/subscriptions |
POST |
Subscription to the notification of policy control events and creation of an Individual Policy Control Events Subscription resource. |
Individual Policy Control Events Subscription |
/subscriptions/{subscriptionId} |
GET |
Reads an Individual Policy Control Events Subscription resource. |
PUT |
Modifies an Individual Policy Control Events Subscription. |
||
DELETE |
Cancels an individual subscription to notifications of policy control events. |
5.3.2 Resource: Policy Control Events Subscriptions (Collection)
5.3.2.1 Description
The Policy Control Events Subscriptions resource represents all subscriptions of the Npcf_EventExposure service at a given PCF.
5.3.2.2 Resource definition
Resource URI: {apiRoot}/npcf-eventexposure/v1/subscriptions
This resource shall support the resource URI variables defined in table 5.3.2.2-1.
Table 5.3.2.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See clause 5.1 |
5.3.2.3 Resource Standard Methods
5.3.2.3.1 POST
This method shall support the URI query parameters specified in table 5.3.2.3.1-1.
Table 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 5.3.2.3.1-2 and the response data structures and response codes specified in table 5.3.2.3.1-3.
Table 5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
PcEventExposureSubsc |
M |
1 |
Contains the information required for the creation of a new individual policy control events subscription. |
Table 5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
PcEventExposureSubsc |
M |
1 |
201 Created |
Contains the representation of the Individual Policy Control Events Subscription resource. |
NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply. |
Table 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}/npcf-eventexposure/v1/subscriptions/{subscriptionId} |
5.3.2.4 Resource Custom Operations
None.
5.3.3 Resource: Individual Policy Control Events Subscription (Document)
5.3.3.1 Description
The Individual Policy Control Events Subscription resource represents a single subscription of the Npcf_EventExposure service at a given PCF.
5.3.3.2 Resource definition
Resource URI: {apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId}
This resource shall support the resource URI variables defined in table 5.3.3.2-1.
Table 5.3.3.2-1: Resource URI variables for this resource
Name |
Data type |
Definition |
apiRoot |
string |
See clause 5.1 |
subscriptionId |
string |
Identifies a subscription to the PCF event exposure service. |
5.3.3.3 Resource Standard Methods
5.3.3.3.1 GET
This method shall support the URI query parameters specified in table 5.3.3.3.1-1.
Table 5.3.3.3.1-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.3.3.3.1-2 and the response data structures and response codes specified in table 5.3.3.3.1-3.
Table 5.3.3.3.1-2: Data structures supported by the GET Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 5.3.3.3.1-3: Data structures supported by the GET Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
PcEventExposureSubsc |
M |
1 |
200 OK |
A representation of the Individual Policy Control Events Subscription is returned. |
RedirectResponse |
O |
0..1 |
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 PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
RedirectResponse |
O |
0..1 |
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 PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply. |
Table 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 in an alternative PCF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance towards which the request is redirected. |
Table 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 in an alternative PCF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance towards which the request is redirected. |
5.3.3.3.2 PUT
This method shall support the URI query parameters specified in table 5.3.3.3.2-1.
Table 5.3.3.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.3.3.3.2-2 and the response data structures and response codes specified in table 5.3.3.3.2-3.
Table 5.3.3.3.2-2: Data structures supported by the PUT Request Body on this resource
Data type |
P |
Cardinality |
Description |
PcEventExposureSubsc |
M |
1 |
Modifies the existing Individual Policy Control Events Subscription resource. |
Table 5.3.3.3.2-3: Data structures supported by the PUT Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
PcEventExposureSubsc |
M |
1 |
200 OK |
Successful case: The Individual Policy Control Events Subscription was modified and a representation is returned. |
n/a |
204 No Content |
Successful case: The Individual Policy Control Events Subscription was modified. |
||
RedirectResponse |
O |
0..1 |
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 PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
RedirectResponse |
O |
0..1 |
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 PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply. |
Table 5.3.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 PCF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance towards which the request is redirected |
Table 5.3.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 PCF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance towards which the request is redirected |
5.3.3.3.3 DELETE
This method shall support the URI query parameters specified in table 5.3.3.3.3-1.
Table 5.3.3.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.3.3.3.3-2 and the response data structures and response codes specified in table 5.3.3.3.3-3.
Table 5.3.3.3.3-2: Data structures supported by the DELETE Request Body on this resource
Data type |
P |
Cardinality |
Description |
n/a |
Table 5.3.3.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 Individual Policy Control Events Subscription resource matching the subscriptionId was deleted. |
||
RedirectResponse |
O |
0..1 |
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 PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
RedirectResponse |
O |
0..1 |
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 PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
NOTE: The mandatory HTTP error status code for the DELETE method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply. |
Table 5.3.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 PCF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance towards which the request is redirected. |
Table 5.3.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 PCF (service) instance. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance towards which the request is redirected. |
5.3.3.4 Resource Custom Operations
None.
5.4 Custom Operations without associated resources
None.
5.5 Notifications
5.5.1 General
Notifications shall comply with clause 6.2 of 3GPP TS 29.500 [5] and clause 4.6.2.3 of 3GPP TS 29.501 [6].
Table 5.5.1-1: Notifications overview
Notification |
Callback URI |
HTTP method or custom operation |
Description (service operation) |
Policy Control Event Notification |
{notifUri} |
POST |
Notification of policy control event reporting. |
5.5.2 Policy Control Event Notification
5.5.2.1 Description
The Policy Control Event Notification is used by the PCF to report one or several observed policy control events to the NF service consumer that has subscribed to such notifications.
NOTE 1: The "callback" clause of the OpenAPI specification found in Annex A.2 associated to the POST method of the "Policy Control Events Subscriptions" resource is used as the notification request for both explicit and implicit subscriptions.
NOTE 2: For implicit subscriptions, the NEF can have previously stored in the UDR the notification URI to be used in the notifications initiated by the PCF. See 3GPP TS 29.519 [24] for the details.
5.5.2.2 Target URI
The Callback URI "{notifUri}" shall be used with the callback URI variables defined in table 5.5.2.2-1.
Table 5.5.2.2-1: Callback URI variables
Name |
Data type |
Definition |
notifUri |
Uri |
The Notification Uri as assigned by the NF service consumer either during the explicit subscription service operation and described within the PcEventExposureSubsc data type (see table 5.6.2.2-1) or during the implicit subscription via the provisioning of the corresponding application data in UDR (see 3GPP TS 29.519 [24]. (NOTE). |
NOTE: When obtained from the UDR, it corresponds to the notification URI previously stored by the NEF. |
5.5.2.3 Standard Methods
5.5.2.3.1 POST
This method shall support the URI query parameters specified in table 5.5.2.3.1-1.
Table 5.5.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 5.5.2.3.1-2 and the response data structures and response codes specified in table 5.5.2.3.1-3.
Table 5.5.2.3.1-2: Data structures supported by the POST Request Body on this resource
Data type |
P |
Cardinality |
Description |
PcEventExposureNotif |
M |
1 |
Provides Information about observed policy control events |
Table 5.5.2.3.1-3: Data structures supported by the POST Response Body on this resource
Data type |
P |
Cardinality |
Response codes |
Description |
n/a |
204 No Content |
The receipt of the Notification is acknowledged. |
||
RedirectResponse |
O |
0..1 |
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 NF consumer (service) instance where the notification should be sent. Applicable if the feature "ES3XX" is supported. |
RedirectResponse |
O |
0..1 |
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 NF consumer (service) instance where the notification should be sent. Applicable if the feature "ES3XX" is supported. |
NOTE: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [5] for the POST method shall also apply. |
Table 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 |
An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the notification request is redirected. |
Table 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 |
An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. |
3gpp-Sbi-Target-Nf-Id |
string |
O |
0..1 |
Identifier of the target NF (service) instance ID towards which the notification request is redirected. |
5.6 Data Model
5.6.1 General
This clause specifies the application data model supported by the API.
Table 5.6.1-1 specifies the data types defined for the Npcf_EventExposure service based interface protocol.
Table 5.6.1-1: Npcf_EventExposure specific Data Types
Data type |
Section defined |
Description |
Applicability |
EthernetFlowInfo |
5.6.2.6 |
Identification of an UL/DL ethernet flow. |
ExtendedSessionInformation |
IpFlowInfo |
5.6.2.7 |
Identification of an UL/DL IP flow. |
ExtendedSessionInformation |
PcEvent |
5.6.3.3 |
Policy Control Events. |
|
PcEventExposureNotif |
5.6.2.3 |
Describes notifications about Policy Control events that occurred in an Individual Policy Events Subscription resource. |
|
PcEventExposureSubsc |
5.6.2.2 |
Represents an Individual Policy Events Subscription resource. |
|
PcEventNotification |
5.6.2.8 |
Represents the information reported for a Policy Control event. |
|
PduSessionInformation |
5.6.2.9 |
Represents PDU session identification information. |
ExtendedSessionInformation |
ReportingInformation |
5.6.2.4 |
Represents the type of reporting the subscription requires. |
|
ServiceIdentification |
5.6.2.5 |
Identification of the service to which the subscription applies. |
ExtendedSessionInformation |
SnssaiDnnCombination |
5.6.2.10 |
Represents a combination of S-NSSAI and DNN(s). |
EneNA |
Table 5.6.1-2 specifies data types re-used by the Npcf_EventExposure 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 Npcf_EventExposure service based interface.
Table 5.6.1-2: Npcf_EventExposure re-used Data Types
Data type |
Reference |
Comments |
Applicability |
AccessType |
3GPP TS 29.571 [14] |
Access Type. |
|
AdditionalAccessInfo |
3GPP TS 29.512 [9] |
Indicates the combination of additional Access Type and RAT Type for MA PDU session. |
ATSSS |
AfAppId |
3GPP TS 29.514 [12] |
AF application Identifier. |
ExtendedSessionInformation |
AnGwAddress |
3GPP TS 29.514 [12] |
Carries the control plane address of the EPC untrusted non-3GPP access network gateway. (NOTE 1) |
|
DateTime |
3GPP TS 29.571 [14] |
Time stamp. |
|
Dnn |
3GPP TS 29.571 [14] |
Identifies a DNN. |
|
DurationSec |
3GPP TS 29.571 [14] |
Seconds of duration. |
|
EthFlowDescription |
3GPP TS 29.514 [12] |
Identifies an ethernet flow description. (NOTE 2) |
ExtendedSessionInformation |
Failure |
3GPP TS 29.522 [25] |
Indicates the failure reason for an unsuccessful outcome of the UE Policy Delivery. |
DeliveryOutcome |
FlowDescription |
3GPP TS 29.514 [12] |
Identifies an IP flow description. |
ExtendedSessionInformation |
Gpsi |
3GPP TS 29.571 [14] |
Generic Public Subscription Identifier. |
|
GroupId |
3GPP TS 29.571 [14] |
Identifies a group of UEs. |
|
MacAddr48 |
3GPP TS 29.571 [14] |
Mac Address of the UE. |
ExtendedSessionInformation |
NotificationFlag |
3GPP TS 29.571 [14] |
Notification flag. |
EneNA |
NotificationMethod |
3GPP TS 29.508 [15] |
Represents the Notification Method. |
|
PartitioningCriteria |
3GPP TS 29.571 [14] |
Used to partition UEs before applying sampling. |
EneNA |
PlmnIdNid |
3GPP TS 29.571 [14] |
Identifies the network: the PLMN Identifier or the SNPN Identifier. (NOTE 3) |
|
RatType |
3GPP TS 29.571 [14] |
RAT Type. |
|
RedirectResponse |
3GPP TS 29.571 [14] |
Contains redirection related information. |
ES3XX |
SamplingRatio |
3GPP TS 29.571 [14] |
Sampling Ratio. |
|
SatelliteBackhaulCategory |
3GPP TS 29.571 [14] |
Indicates the satellite or non-satellite backhaul category. |
SatelliteBackhaul |
ServiceAreaCoverageInfo |
3GPP TS 29.534 [23] |
Service area coverage in terms of tracking area codes and serving network. |
AMPoliciesEvents |
Snssai |
3GPP TS 29.571 [14] |
Identifies a S-NSSAI. |
|
Supi |
3GPP TS 29.571 [14] |
Identifies the SUPI of the UE. |
|
SupportedFeatures |
3GPP TS 29.571 [14] |
Used to negotiate the applicability of the optional features defined in clause 5.8. |
|
Uinteger |
3GPP TS 29.571 [14] |
Unsigned integer. |
|
NOTE 1: "AnGwAddress" data structure is only used to encode the ePDG address and is only applicable to the 5GS and EPC/E-UTRAN interworking scenario as defined in 3GPP TS 29.512 [9], Annex B. NOTE 2: In order to support a set of MAC addresses with a specific range in the traffic filter, feature MacAddressRange as specified in clause 5.8 shall be supported. NOTE 3: The SNPN Identifier consists of the PLMN Identifier and the NID. |
5.6.2 Structured data types
5.6.2.1 Introduction
This clause defines the structures to be used in resource representations.
5.6.2.2 Type PcEventExposureSubsc
Table 5.6.2.2-1: Definition of type PcEventExposureSubsc
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
eventSubs |
array(PcEvent) |
M |
1..N |
Subscribed Policy Control events. |
|
eventsRepInfo |
ReportingInformation |
O |
0..1 |
Represents the reporting requirements of the subscription. |
|
groupId |
GroupId |
C |
0..1 |
Represents an internal group identifier and identifies a group of UEs. It shall be present when the subscription is targeting a Group of UE(s). |
|
filterDnns |
array(Dnn) |
O |
1..N |
Represents the DNNs for which the policy event report shall apply. Each DNN is a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. If omitted it represents any DNN. |
|
filterSnssais |
array(Snssai) |
O |
1..N |
Represents the S-NSSAIs for which the policy event report shall apply. If omitted it represents any S-NSSAI. |
|
snssaiDnn |
array(SnssaiDnnCombination) |
O |
1..N |
Represents the combination list of S-NSSAI and DNN for which the policy event report shall apply. If omitted, it represents any combination. |
EneNA |
filterServices |
array(ServiceIdentification) |
O |
1..N |
Represents the services for which the policy event report shall apply. If omitted, the policy event report shall apply for all the active services. |
ExtendedSessionInformation |
notifUri |
Uri |
M |
1 |
Notification URI for Policy Control event reporting. |
|
notifId |
string |
M |
1 |
Notification Correlation ID assigned by the NF service consumer. |
|
eventNotifs |
array(PcEventNotification) |
C |
1..N |
Represents the Policy Control Events to be reported in the Npcf_EvenExposure_Subscribe response. |
ERIR |
suppFeat |
SupportedFeatures |
C |
0..1 |
This IE represents a list of Supported features used as described in clause 5.8. Shall be present in the HTTP POST request/response. (NOTE) |
|
NOTE: In the HTTP request, it represents the set of features supported by the NF service consumer. In the HTTP response, it represents the set of features supported by both the NF service consumer and the PCF. |
5.6.2.3 Type PcEventExposureNotif
Table 5.6.2.3-1: Definition of type PcEventExposureNotif
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
notifId |
string |
M |
1 |
Notification Correlation ID assigned by the NF service consumer. |
|
eventNotifs |
array(PcEventNotification) |
M |
1..N |
Represents the Policy Control Events to be reported according to the subscription corresponding to the Notification Correlation ID. |
5.6.2.4 Type ReportingInformation
Table 5.6.2.4-1: Definition of type ReportingInformation
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
immRep |
boolean |
O |
0..1 |
Indication of immediate reporting. If included, when it is set to true it indicates immediate reporting of the subscribed events, if available. Otherwise, reporting will occur when the event is met. |
|
notifMethod |
NotificationMethod |
O |
0..1 |
Represents the notification method (periodic, one time, on event detection). If "notifMethod" attribute is not supplied, the default value "ON_EVENT_DETECTION" applies. |
|
maxReportNbr |
Uinteger |
O |
0..1 |
Represents the maximum number of reports, after which the subscription ceases to exist (i.e., the reporting ends). It may be present for the "PERIODIC" and on "ON_EVENT_DETECTION" notification methods. If omitted, there is no limit. |
|
monDur |
DateTime |
C |
0..1 |
Represents the time at which the subscription ceases to exist (i.e. the subscription becomes invalid and the reporting ends). If omitted, there is no time limit. If present in the subscription request, it shall be present in the subscription response. |
|
repPeriod |
DurationSec |
O |
0..1 |
Indicates the time interval between successive event notifications. It is supplied for notification method "PERIODIC". |
|
sampRatio |
SamplingRatio |
O |
0..1 |
Indicates the ratio of the random subset to target UEs, event reports only relates to the subset. |
|
partitionCriteria |
array(PartitioningCriteria) |
O |
1..N |
Defines criteria for partitioning the UEs in order to apply the sampling ratio for each partition. It may only be included in event subscription requests when the "sampRatio" attribute is also provided. (NOTE) |
EneNA |
grpRepTime |
DurationSec |
O |
0..1 |
Indicates the time during which the event reports detected for the concerned UEs are aggregated in a group, in order to be reported together to the NF service consumer. |
|
notifFlag |
NotificationFlag |
O |
0..1 |
Indicates the notification flag, which is used to mute/unmute notifications and to retrieve events stored during a period of muted notifications. Default: "ACTIVATE". |
EneNA |
NOTE: For a given type of partitioning criteria, the UE shall belong to only one single partition as long as it is served by the NF service producer. |
5.6.2.5 Type ServiceIdentification
Table 5.6.2.5-1: Definition of type ServiceIdentification
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
servEthFlows |
array(EthernetFlowInfo) |
C |
1..N |
Ethernet flows of a service. |
ExtendedSessionInformation |
servIpFlows |
array(IpFlowInfo) |
C |
1..N |
IP flows of a service. |
ExtendedSessionInformation |
afAppId |
AfAppId |
O |
0..1 |
Contains an AF application identifier. |
ExtendedSessionInformation |
NOTE: At least one of the "servEthFlows", "servIpFlows" or "afAppId" attributes shall be present. The "servEthFlows" attribute and the "servIpFlows" attribute shall not be both present at the same time. |
5.6.2.6 Type EthernetFlowInfo
Table 5.6.2.6-1: Definition of type EthernetFlowInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
ethFlows |
array(EthFlowDescription) |
C |
1..2 |
Contains the flow description for the Uplink and/or Downlink Ethernet flows. It shall be present in the subscription request. |
ExtendedSessionInformation |
flowNumber |
integer |
M |
1 |
Identifies the ordinal number of the Ethernet flow. |
ExtendedSessionInformation |
5.6.2.7 Type IpFlowInfo
Table 5.6.2.7-1: Definition of type IpFlowInfo
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
ipFlows |
array(FlowDescription) |
C |
1..2 |
Contains the flow description for the Uplink and/or Downlink IP flows. It shall be present in the subscription request. |
ExtendedSessionInformation |
flowNumber |
integer |
M |
1 |
Identifies the ordinal number of the IP flow. |
ExtendedSessionInformation |
5.6.2.8 Type PcEventNotification
Table 5.6.2.8-1: Definition of type PcEventNotification
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
event |
PcEvent |
M |
1..N |
Reported Policy Control event. |
|
accType |
AccessType |
C |
0..1 |
Access Type. It shall be included when the reported PcEvent is "AC_TY_CH". |
|
addAccessInfo |
AdditionalAccessInfo |
O |
0..1 |
Indicates the additional combination of Access Type and RAT Type available for MA PDU session. It may be present when the notified event is "AC_TY_CH" and the PDU session is a Multi-Access PDU session. |
ATSSS |
relAccessInfo |
AdditionalAccessInfo |
O |
0..1 |
Indicates the release of a combination of Access Type and RAT Type available for MA PDU session. It may be present when the notified event is "AC_TY_CH" and the PDU session is a Multi-Access PDU session. |
ATSSS |
anGwAddr |
AnGwAddress |
O |
0..1 |
ePDG address. It shall be included if applicable when the reported PcEvent is "AC_TY_CH". |
|
ratType |
RatType |
O |
0..1 |
RAT Type. It shall be included if applicable when the reported PcEvent is "AC_TY_CH". |
|
plmnId |
PlmnIdNid |
C |
0..1 |
PLMN Identifier or the SNPN Identifier. It shall be included when the reported PcEvent is "PLMN_CH". (NOTE) |
|
appliedCov |
ServiceAreaCoverageInfo |
C |
0..1 |
The list of applied allowed Tracking Areas for the serving network where the UE is camping. It shall be included when the reported PcEvent is "SAC_CH". |
AMPoliciesEvents |
supi |
Supi |
C |
0..1 |
SUPI of the UE. It shall be present if available. |
|
gpsi |
Gpsi |
O |
0..1 |
Gpsi shall contain either an External Id or an MSISDN. |
|
timeStamp |
DateTime |
M |
1 |
Time at which the event is observed. |
|
pduSessInfo |
PduSessionInformation |
O |
0..1 |
Represents PDU session information related to the observed event. |
ExtendedSessionInformation |
repServices |
ServiceIdentification |
O |
0..1 |
Represents service information related to the observed event. |
ExtendedSessionInformation |
satBackhaulCategory |
SatelliteBackhaulCategory |
C |
0..1 |
Indicates the satellite or non-satellite backhaul category of the PDU session. It shall be included when the reported PcEvent is "SAT_CATEGORY_CH". |
SatelliteBackhaul |
delivFailure |
Failure |
C |
0..1 |
Indicates the failure reason for an unsuccessful outcome of the UE Policy Delivery. It shall be included when the reported PcEvent is "UNSUCCESS_UE_POL_DEL_SP". |
DeliveryOutcome |
NOTE: The SNPN Identifier consists of the PLMN Identifier and the NID. |
5.6.2.9 Type PduSessionInformation
Table 5.6.2.9-1: Definition of type PduSessionInformation
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
snssai |
Snssai |
M |
1 |
S-NSSAI of the PDU session. |
ExtendedSessionInformation |
dnn |
Dnn |
M |
1 |
Dnn of the PDU session, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. |
ExtendedSessionInformation |
ueIpv4 |
Ipv4Addr |
C |
0..1 |
The IPv4 address of the served UE. (NOTE 1) |
ExtendedSessionInformation |
ueIpv6 |
Ipv6Prefix |
C |
0..1 |
The IPv6 prefix of the served UE. (NOTE 1) |
ExtendedSessionInformation |
ipDomain |
string |
O |
0..1 |
Identifies the IP domain. (NOTE 2) |
ExtendedSessionInformation |
ueMac |
MacAddr48 |
C |
0..1 |
UE MAC address. (NOTE 1) |
ExtendedSessionInformation |
NOTE 1: Either the served UE IP address (an Ipv4Addr or Ipv6Prefix or both if available) or UE MAC address shall be present. NOTE 2: An "ipDomain" attribute, may be provided in combination with a "ueIpv4" attribute. |
5.6.2.10 Type SnssaiDnnCombination
Table 5.6.2.10-1: Definition of type SnssaiDnnCombination
Attribute name |
Data type |
P |
Cardinality |
Description |
Applicability |
snssai |
Snssai |
M |
1 |
S-NSSAI |
|
dnns |
array(Dnn) |
M |
1..N |
Dnn |
5.6.3 Simple data types and enumerations
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.
5.6.3.2 Simple data types
The simple data types defined in table 5.6.3.2-1 shall be supported.
Table 5.6.3.2-1: Simple data types
Type Name |
Type Definition |
Description |
Applicability |
5.6.3.3 Enumeration: PcEvent
The enumeration PcEvent represents the policy control events that can be subscribed. It shall comply with the provisions defined in table 5.6.3.3-1.
Table 5.6.3.3-1: Enumeration PcEvent
Enumeration value |
Description |
Applicability |
AC_TY_CH |
Access Type Change |
|
PLMN_CH |
PLMN Change |
|
SAC_CH |
Service Area Coverage change |
AMPoliciesEvents |
SAT_CATEGORY_CH |
Indicates that a change between different satellite backhaul category, or non-satellite backhaul, has been detected. |
SatelliteBackhaul |
SUCCESS_UE_POL_DEL_SP |
Indicates about the successful UE Policy delivery related to the invocation of AF provisioned service parameters. |
DeliveryOutcome |
UNSUCCESS_UE_POL_DEL_SP |
Indicates about the unsuccessful UE Policy delivery related to the invocation of AF provisioned service parameters. |
DeliveryOutcome |
5.7 Error handling
5.7.1 General
HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [5].
For the Npcf_EventExposure API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [6].
Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [5] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [5].
In addition, the requirements in the following clauses are applicable for the Npcf_EventExposure API.
5.7.2 Protocol Errors
In this Release of the specification, there are no service specific protocol errors applicable for the Npcf_EventExposure API.
5.7.3 Application Errors
The application errors defined for the Npcf_EventExposure service are listed in table 5.7.3-1.
Table 5.7.3-1: Application errors
Application Error |
HTTP status code |
Description |
5.8 Feature negotiation
The optional features in table 5.8-1 are defined for the Npcf_EventExposure API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [5].
Table 5.8-1: Supported Features
Feature number |
Feature Name |
Description |
1 |
ExtendedSessionInformation |
Indicates the support of additional session information in the subscription and report of policy control event. |
2 |
MacAddressRange |
Indicates the support of a set of MAC addresses with a specific range in the traffic filter. |
3 |
ATSSS |
Indicates the support of the report of the multiple access types of a MA PDU session. |
4 |
ES3XX |
Extended Support for 3xx redirections. This feature indicates the support of redirection for any service operation, according to Stateless NF procedures as specified in clauses 6.5.3.2 and 6.5.3.3 of 3GPP TS 29.500 [5] and according to HTTP redirection principles for indirect communication, as specified in clause 6.10.9 of 3GPP TS 29.500 [5]. |
5 |
AMPoliciesEvents |
Indicates the support of the report of changes of service area coverage for a UE. |
6 |
EneNA |
This feature indicates support for the enhancements of network data analytics requirements. |
7 |
SatelliteBackhaul |
Indicates the support of the report of the satellite or non-satellite backhaul category of the PDU session. |
8 |
DeliveryOutcome |
Indicates the support of notifications about the outcome of the UE Policy delivery related to the invocation of AF provisioned service parameters. |
9 |
ERIR |
Indicates the support of immediate report within the subscription response. |
5.9 Security
As indicated in 3GPP TS 33.501 [19] and 3GPP TS 29.500 [5], the access to the Npcf_EventExposure API, based on local configuration, may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [20]), using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [21]) plays the role of the authorization server.
If OAuth2 authorization is used, an NF Service Consumer, prior to consuming services offered by the Nnrf_NFManagement API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [21], clause 5.4.2.2.
NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF where the NF Service Consumer invoked the discovery of the Npcf_EventExposure service.
The Npcf_EventExposure API defines a single scope "npcf-eventexposure" for the entire service, and it does not define any additional scopes at resource or operation level.
Annex A (normative):
OpenAPI specification