Content for TS 29.591 Word version: 19.0.0
4.3 Nnef_EASDeployment Service
4.3.1 Service Description
4.3.1.1 Overview
4.3.1.2 Service Architecture
4.3.1.3 Network Functions
4.3.2 Service Operations
4.3.2.1 Introduction
4.3.2.2 Nnef_EASDeployment_Subscribe service operation
4.3.2.3 Nnef_EASDeployment_Unsubscribe service operation
4.3.2.4 Nnef_EASDeployment_Notify service operation
...
...
4.3 Nnef_EASDeployment Service |R17| p. 24
4.3.1 Service Description p. 24
4.3.1.1 Overview p. 24
The Nnef_EASDeployment service, as defined in TS 23.502, is provided by the Network Exposure Function (NEF). This service allows the SMF to subscribe/unsubscribe the notification of AF provisioned EAS Deployment information, and for the NEF to notify the AF provisioned EAS Deployment information to the subscribed SMF.
4.3.1.2 Service Architecture p. 24
The 5G System Architecture is defined in TS 23.501.
The Nnef_EASDeployment service is part of the Nnef service-based interface exhibited by the Network Exposure Function (NEF).
Known consumer of the Nnef_EASDeployment service is:
- Session Management Function (SMF)
4.3.1.3 Network Functions p. 25
4.3.1.3.1 Network Exposure Function (NEF) p. 25
The Network Exposure Function (NEF) is a functional element that support for the NF service consumer (i.e SMF) subscribing to the notification of the AF provisioned EAS Deployment Information and provide EAS Deployment Information change notification to the NF service consumer as defined in this specification.
4.3.1.3.2 NF Service Consumers p. 25
The known NF service consumers are as follows:
The Session Management Function (SMF):
- supports (un)subscribing to notifications of subscribed event(s) from the NEF.
- supports receiving the notifications of subscribed event(s) from the NEF.
4.3.2 Service Operations p. 25
4.3.2.1 Introduction p. 25
Service operations defined for the Nnef_EASDeployment Service are shown in Table 4.3.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 changes of EAS Deployment Information. | NF service consumer |
| Nnef_ | This service operation is used by an NF service consumer to explicitly unsubscribe the notification of changes of EAS Deployment Information. | NF service consumer |
| Nnef_ | This service operation is used by the NEF to provide subscribed event information, e.g.updated EAS Deployment Information to the NF service consumer. | NEF |
4.3.2.2 Nnef_EASDeployment_Subscribe service operation p. 26
4.3.2.2.1 General p. 26
This service operation is provided by the NEF for NF consumers to explicitly subscribe the notification of changes of EAS Deployment Information.
4.3.2.2.2 Creating a new subscription p. 26
In order to subscribe to EAS Deployment Information change event, the SMF shall send an HTTP POST request message to the NEF for the "EAS Deployment Event Subscriptions" resource. The HTTP POST message shall include EasDeploySubData data structure as request body. The EasDeploySubData data structure shall include:
DataRepository service as described in TS 29.504 to fetch the EAS Deployment Information 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 EAS Deployment Event Subscription" resource. Then the NEF shall send a HTTP "201 Created" response with EASDeploySubData 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 indicator is included in the subscription request, the NEF shall include in the response body the currently available EAS Deployment Information that match the subscription.
If the NEF receives an error code from the UDR, the NEF shall take proper error handling actions and shall respond to the SMF with a proper error status code.
- Event Id in the "eventId" attribute;
- An notification correlation ID provided by the NF service consumer during the subscription as "notifId" attribute; and
- An URI to receive the subscribed EAS Deployment information change notifications as "notifUri" attribute.
- an indicator to immediately report the current status of EAS Deployment Information if available, as "immRep" attribute;
- (list of) DNN and/or S-NSSAI combination as "dnnSnssaiInfos" attribute;
- identification of an application as "appId" attribute; and/or
- an internal Group Identifier as "interGroupId" attribute.
4.3.2.3 Nnef_EASDeployment_Unsubscribe service operation p. 26
4.3.2.3.1 General p. 26
This service operation is used by an NF service consumer (i.e. SMF) to explicitly unsubscribe the notification of changes of EAS Deployment Information.
The following procedure using the Nnef_EASDeployment_Unsubscribe service operation is supported:
- unsubscription from the notification of changes of EAS Deployment Information.
4.3.2.3.2 Unsubscription of notification of changes of EAS Deployment Information p. 27
In order to delete an existing subscription to EAS Deployment Information change event, the NF service consumer shall send an HTTP DELETE request message to the individual resource URI "{apiRoot}/nnef-eas-deployment/<apiVersion>/subscriptions/{subscriptionId}" in which the "{subscriptionId}" is the subscription correlation identifier of the existing subscription resource that is to be deleted.
The NEF shall delete the individual resource and shall respond to the NF service consumer with an HTTP "204 No Content" response message.
If the NEF cannot delete the individual resource, shall take proper error handling actions and shall respond to the NF service consumer with a proper error status code.
4.3.2.4 Nnef_EASDeployment_Notify service operation p. 27
4.3.2.4.1 General p. 27
The Nnef_EASDeployment_Notify service operation enables the NEF to notify the subscribed event information, e.g. updated EAS Deployment Information to the NF Consumer.
The following procedure using the Nnef_EASDeployment_Notify service operation is supported:
- notification about subscribed EAS Deployment Information change.
4.3.2.4.2 Notification of changes of EAS Deployment Information p. 27
When the EAS Deployment information is changed, the NEF shall provide a notification to the subscribed NF service consumer by sending an HTTP POST message that include the EasDeployInfoNotif data structure in the request body to notify the EAS Deployment information changes to the NF service consumer.
The EasDeployInfoNotif data structure shall include the subscribed Event ID and the EAS Deployment Information.
Upon receipt of the EAS Deployment event notification, the NF service consumer shall respond with a "204 No Content" status code to confirm the received notification.
