Content for TS 23.435 Word version: 19.3.0

0… 4… 5… 7… 9… 9.4… 9.5… 9.6… 9.7… 9.8… 9.9… 9.10… 9.11… 9.12… 9.13… 9.14… 9.15… 9.16… 9.17… 9.18… A…

9.6 Discovery of management service exposure 9.6.1 General 9.6.2 Procedure 9.6.2.1 VAL-triggered MnS discovery procedure 9.6.2.2 OAM-triggered new/modified MnS discovery 9.6.3 Information flows 9.6.4 APIs 9.6.4.1 General 9.6.4.2 SS_NSCE_Management_Service Discovery
...

9.6 Discovery of management service exposure p. 52

9.6.1 General p. 52

A Management Domain (MD) feature/capability is anything of use offered by the management system to the 3rd party application. Therefore, a new feature could be a managed entity, a MnS or management API, any software, hardware, or other functionality - for example, new technology support, new coverage area, new network slice type or instance, new NFs or new network slice subnet type or instance. To be able to utilise capabilities/features of the management system the applications must be made aware of existence of such features and capabilities. All MD features/capabilities come with a pre-configured exposure, where this can be configured by the operator for a given slice. This exposure is used to decide which application can see which information regarding the capability/feature. Exposure refers to the permissions that the 3rd party entity has gained over its use of the management service, e.g., the ability to read, or execute or modify or delete can be considered as different sorts of exposure.

The first procedure (clause 9.6.2.1) provides the NSCE server support for translating the VAL server request to a MnS requirement and the exposure of service/management data related to his request. The second procedure (clause 9.6.2.2) supports the notification to the VAL server, based on a new/modified MnS / capability for a target slice.

9.6.2 Procedure p. 52

9.6.2.1 VAL-triggered MnS discovery procedure p. 52

In this procedure, the VAL server initially requests the new MnS which are supported by a target slice and based on this request the NSCE server requests from the OAM/MnS registry the MnS discovery. Then, the OAM/MnS registry derives the details to be exposed based on the NSCE server/VAL server permissions and provides the list of MnS for the given slice and the access details via the NSCE server to the VAL server.

Pre-conditions:

The VAL server has registered to receive NSCE services.
The NSCE server is trusted by the OAM, and a contract has been signed between the MNO and NSCE server provider to allow OAM interfaces and/or network slice information exposure.
MnS registry at OAM is aware of the allowed MnS and the permissions for a given slice.

Figure 9.6.2.1-1 illustrates a solution for the MnS discovery support.

Reproduction of 3GPP TS 23.435, Fig. 9.6.2.1-1: MnS discovery support

Figure 9.6.2.1-1: MnS discovery support

The steps of this procedure are as follows:

Step 1.

The VAL server sends a Management Service Discovery subscribe request message to NSCE server to indicate a requirement for receiving the expected exposure capability type and the related permissions for a target slice or for a given VAL application.

Step 2.

The NSCE server sends a response to the subscription request, indicating a success or failure of the subscription request.

Step 3.

The NSCE server translates the requirement based on the subscription, and in particular identifies the needed exposure capability type and translates it to a MnS exposure requirement. Such translation of the requirement includes the mapping to a list of MnSs (specified in TS 28.532) which are needed for the given slice and VAL server permissions.

Step 4.

The NSCE server coordinates with the 5GS and discovers the related network service(s), by triggering the MnS service discovery as specified in clause 5.2.1.3 of TS 28.537. In particular, NSCE server acts as MnS discovery service consumer (for all MnS needed for a target slice based on VAL requirement) requests from MnS discovery service producer(s) at OAM the discovery of MnS information for the MnS related to the target slice or VAL application. The 5GS, MnS discovery service producer(s) sends the discovery result including related exposure information such as management service identifier, management service information and management service producer information to the NSCE server.

Step 5.

The NSCE server sends a management service discovery subscription notify message to provide the service/management data based on step 4, including the list of MnS and the corresponding exposure details to the VAL server.

9.6.2.2 OAM-triggered new/modified MnS discovery p. 53

This procedure includes the case when a new/modified MnS is deployed at the MD for the given slice, and the OAM/MnS registry provides this information directly to VAL server (assuming that VAL server has registered to the MD).

Pre-conditions:

VAL server is registered to NSCE server based on clause 9.2.
NSCE server has subscribed to OAM / MnS discovery service registry.

Reproduction of 3GPP TS 23.435, Fig. 9.6.2.2-1: OAM-triggered new/modified MnS discovery

Figure 9.6.2.2-1: OAM-triggered new/modified MnS discovery

Step 1.

The MnS registry may discover new or modified MnS in the 3GPP MD. Such changes may be due to new/modified management service producers, new managed entities (such as new radio, new technology or new NFs), new/modified technical support (such as support in a new geography or coverage area), availability of new management data, e.g., related to slice performance. An example procedure related to the addition of a new MnS producer is provided in clause 5.2.1.1 of TS 28.537.

The MnS discovery service producer when capturing new or modified capability (e.g. new MnS producer) related to the target slice or VAL application identifies the NSCE server which needs to be informed (based on the subscription) on the new/modified capability and derives the details to be exposed to the VAL server (via the NSCE server). Then, the MnS registry sends to the NSCE server the new / modified MnS.

Step 2.

The NSCE server determines the VAL server(s) that needs to be notified on the new or modified MnS / MD capability based on their registrations. Then, NSCE server generates and sends a notification with the required information to be provided to the VAL server.

Step 3.

The information on the discovered new/modified MnS is sent as a management service discovery notification message from the NSCE server to VAL server.

9.6.3 Information flows p. 54

9.6.3.1 General p. 54

The following information flows are specified for the MnS discovery support based on clause 9.6.2 and clause 9.6.3.

9.6.3.2 Management service discovery subscribe request p. 54

Table 9.6.3.2-1 describes information elements for the Management service discovery subscribe request from the VAL server to the NSCE server.

Table 9.6.3.2-1: Management service discovery subscribe request

Information element	Status	Description
VAL server ID	M	The identifier of the VAL server.
VAL service ID	M	The identifier of the VAL service for which the MnS discovery request applies.
Network slice related Identifier(s)	O	The slice identifier, if known by the VAL server.
Exposure capability requirement	O	The requirement includes indication of the requested permissions for exposing information related to the target slice. Also, the requirement may include the exposure capability type which is supported (e.g. via EGMF or directly to MnS producer).

9.6.3.3 Management service discovery subscribe response p. 55

Table 9.6.3.3-1 describes information elements for the Management service discovery subscribe response from the NSCE server to the VAL server.

Table 9.6.3.3-1: Management service discovery subscribe response

Information element	Status	Description
Result	M	The result of the subscription request (positive or negative acknowledgement).
> Cause	O (see NOTE)	Indicates the cause of failure.
NOTE: May only be present if the result is failure.

9.6.3.4 Management service discovery notify p. 55

Table 9.6.3.4-1 describes information elements for the Management service discovery notify message from the NSCE server to the VAL server.

Table 9.6.3.4-1: Management service discovery notify

Information element	Status	Description
VAL service ID	M	The identifier of the VAL application.
Management Domain/System ID	M	The identifier of the management system/domain of interest.
List of MnS IDs / MnS producer IDs	M	The list of identifiers of the needed MnSs / MnS producers.
> MnS capability	M	The capability per needed MnS. Such capability may related to the managed elements such as considerations for radio, technology, coverage or NFs.
> MnS permissions	O	Allowed permissions of the VAL server over the MnS, e.g. whether it is allowed to read, write, delete, and/or update.
Network slice related Identifier(s)	O	The slice identifier which is mapped to the VAL application and the list of MnSs.

9.6.4 APIs p. 55

9.6.4.1 General p. 55

Table 9.6.4.1-1 illustrates the NSCE APIs for the MnS discovery feature.

Table 9.6.4.1-1: List of APIs for the MnS discovery feature

API Name	API Operations	Known Consumer(s)	Communication Type
SS_NSCE_Management_Service_Discovery	Management_Service Discovery	VAL server	Subscribe/Notify

9.6.4.2 SS_NSCE_Management_Service Discovery p. 56

9.6.4.2.1 General p. 56

API description:

This API enables the VAL server to communicate with the network slice capability enablement server for requesting management service discovery over NSCE-S.

9.6.4.2.2 SS_NSCE_Management_Service Discovery p. 56

API operation name:

Management_Service Discovery

Description:

Providing for Management_Service Discovery subscribe to the NSCE server and receiving a confirmation.

Known Consumers:

VAL server.

Inputs:

See subclause 9.6.2.1 (step 1)

Outputs:

See subclause 9.6.2.1 (step 4), 9.6.2.2 (step 3)