Content for TS 29.591 Word version: 19.0.0
4.4 Nnef_TrafficInfluenceData Service
4.4.1 Service Description
4.4.1.1 Overview
4.4.1.2 Service Architecture
4.4.1.3 Network Functions
4.4.2 Service Operations
4.4.2.1 Introduction
4.4.2.2 Nnef_TrafficInfluenceData_Subscribe service operation
4.4.2.3 Nnef_TrafficInfluenceData_Unsubscribe service operation
4.4.2.4 Nnef_TrafficInfluenceData_Notify service operation
...
...
4.4 Nnef_TrafficInfluenceData Service |R18| p. 27
4.4.1 Service Description p. 27
4.4.1.1 Overview p. 27
The Nnef_TrafficInfluenceData service, as defined in TS 23.502, is provided by the Network Exposure Function (NEF). This service allows the NF service consumer (e.g., V-SMF) supporting HR-SBO to subscribe/unsubscribe the notification of Traffic Influence from AF in VPLMN, and for the V-NEF to notify the Traffic Influence to the subscribed NF service consumer (e.g., V-SMF).
4.4.1.2 Service Architecture p. 27
The Nnef_TrafficInfluenceData service is part of the Nnef service-based interface exhibited by the Network Exposure Function (NEF).
Known NF service consumer of the Nnef_TrafficInfluenceData service is:
- Session Management Function (SMF)
4.4.1.3 Network Functions p. 28
4.4.1.3.1 Network Exposure Function (NEF) p. 28
The Network Exposure Function (NEF) allows the NF service consumer to subscribe to and unsubscribe from the NEF for the Traffic Influence Data from AF.
4.4.1.3.2 NF Service Consumers p. 28
The known NF service consumers are as follows:
The Session Management Function (SMF):
- supports (un)subscribing to notifications of Traffic Influence Data from the NEF.
- supports receiving the notifications of Traffic Influence Data from the NEF.
4.4.2 Service Operations p. 28
4.4.2.1 Introduction p. 28
Service operations defined for the Nnef_TrafficInfluenceData Service are shown in Table 4.4.2.1-1.
| Service Operation Name | Description | Initiated by |
|---|---|---|
| Nnef_ | This service operation is used by an NF service consumer to explicitly subscribe the notification of Traffic Influence Data. | NF service consumer |
| Nnef_ | This service operation is used by an NF service consumer to explicitly unsubscribe the notification of Traffic Influence Data. | NF service consumer |
| Nnef_ | This service operation is used by the NEF to provide Traffic Influence Data to the NF service consumer. | NEF |
4.4.2.2 Nnef_TrafficInfluenceData_Subscribe service operation p. 29
4.4.2.2.1 General p. 29
This service operation is provided by the NEF for NF service consumers to explicitly subscribe the notification of Traffic Influence Data.
4.4.2.2.2 Creating a new subscription p. 29
Figure 4.4.2.2.2-1 illustrates the creation of a Individual Traffic Influence Data Subscription.
In order to subscribe to Traffic Influence Data, the NF service consumer (e.g., SMF) shall send a Nnef_TrafficInfluenceData_Subscribe request using the HTTP POST method to the NEF with "{apiRoot}/nnef-traffic-influence-data/<apiVersion>/subscriptions" as request URI as shown in step 1 of Figure 4.4.2.2.2-1. The HTTP POST message shall include TrafficInfluDataSub data structure as request body. The TrafficInfluDataSub data structure shall include:
DataRepository service as described in TS 29.504 to retrieve and subscribe to the Traffic Influence Data in the application data in the UDR.
After receiving a successful response from the UDR, the NEF shall create a new subscription and assign a subscription identifier for the "Individual Traffic Influence Data Subscription" resource. Then the NEF shall send an HTTP "201 Created" response with TrafficInfluDataSub data structure as response body and a Location header field containing the URI of the created individual subscription resource to the NF service consumer.
If the immediate report indication is included in the subscription request, the NEF shall include the currently available Traffic Influence Data in the response body.
If errors occur when processing the HTTP POST request or receiving an error code from the UDR, the NEF shall send an HTTP error response as specified in clause 5.3.7.
- the notification URI in the "notifUri" attribute;
- the notification correlation identifier in the "notifCorrId" attribute;
- the identifications of DNN in the "dnns" attribute and/or the identifications of network slice in the "snssais" attribute;
- the identification(s) of target UE(s) in the "supis" attribute;
- the any UE indication in the "anyUe" attribute;
- the identification(s) of the HPLMN in the "hplmnId" attribute;
- the UE address(es) either in the "ipv4Addrs" attribute or in the "ipv6Addrs" attribute;
- the reporting requirements of the subscription in "rptInfo" attribute.
4.4.2.2.3 Modifying an existing subscription p. 30
Figure 4.4.2.2.3-1 illustrates the modification of an existing subscription.
To modify an existing subscription to event notifications, the NF service consumer shall send an HTTP PUT request with: "{apiRoot}/nnef-traffic-influence-data/<apiVersion>/subscriptions/{subscriptionId}" as request URI, as shown in step 1 of Figure 4.4.2.2.3-1, where "{subscriptionId}" is the subscription ID of the existing subscription. The TrafficInfluDataSub data structure is included as request body as described in clause 4.4.2.2.2.
Upon successful reception of an HTTP PUT request with: "{apiRoot}/nnef-traffic-influence-data/<apiVersion>/subscriptions/{subscriptionId}" as request URI and TrafficInfluDataSub data structure as request body, the NEF shall interact with the UDR by invoking the Nudr_DataRepository service as described in TS 29.504 to retrieve and subscribe to the Traffic Influence Data in the application data in the UDR.
After receiving a successful response from the UDR, the NEF shall:
- send HTTP "200 OK" response (as shown in Figure 4.4.2.2.3-1, step 2a) with a response body containing a representation of the updated subscription in the TrafficInfluDataSub data type; or
- send HTTP "204 No Content" response (as shown in Figure 4.4.2.2.3-1, step 2b).
4.4.2.3 Nnef_TrafficInfluenceData_Unsubscribe service operation p. 31
4.4.2.3.1 General p. 31
This service operation is used by an NF service consumer to explicitly unsubscribe the notification of Traffic Influence Data.
The following procedure using the Nnef_TrafficInfluenceData_Unsubscribe service operation is supported:
- unsubscription from the notification of Traffic Influence Data.
4.4.2.3.2 Unsubscription of notification of Traffic Influence Data p. 31
Figure 4.4.2.3.2-1 illustrates the unsubscription of event notifications from NEF.
In order to delete an existing subscription to Traffic Influence Data, the NF service consumer shall send an HTTP DELETE request message with "{apiRoot}/nnef-traffic-influence-data/<apiVersion>/subscriptions/{subscriptionId}" as request URI, as shown in step 1 of Figure 4.4.2.3.2-1, where "{subscriptionId}" is the subscription identifier of the existing subscription resource that is to be deleted.
Upon successful reception of an HTTP DELETE, the NEF shall delete the individual resource and shall respond to the NF service consumer with an HTTP "204 No Content" response message, as shown in step 2 of Figure 4.4.2.3.2-1.
If the received HTTP DELETE request needs to be redirected, the NEF shall send an HTTP redirect response as specified in clause 6.10.9 of TS 29.500.
If errors occur when processing the HTTP DELETE request, the NEF shall send an HTTP error response as specified in clause 5.3.7.
4.4.2.4 Nnef_TrafficInfluenceData_Notify service operation p. 31
4.4.2.4.1 General p. 31
The Nnef_TrafficInfluenceData_Notify service operation enables the NEF to notify the Traffic Influence Data to the NF service consumer.
The following procedure using the Nnef_TrafficInfluenceData_Notify service operation is supported:
- notification about subscribed Traffic Influence Data.
4.4.2.4.2 Notification of changes of Traffic Influence Data p. 31
Figure 4.4.2.4.2-1 illustrates the notification about Traffic Influence Data.
If the NEF observes Traffic Influence Data that an NF service consumer has subscribed, the NEF shall send an HTTP POST request as shown in step 1 of Figure 4.4.2.4.2-1, with the "{notifUri}" as request URI containing the value previously provided by the NF service consumer within the corresponding subscription, and the TrafficInfluDataNotify data structure as request body.
The TrafficInfluDataNotify data structure shall include:
- the notification correlation identifier in the "notifCorrId" attribute;
- Traffic Influence Data within the "eventNotifications" attribute. When the AF request is for subscribing to UP path change events of the HR-SBO PDU session, the NEF shall include the "upPathChgNotifUri" and "upPathChgNotifCorreId" attributes of the TrafficInfluData data structure defined in TS 29.519.
