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.8 Information collection from NSCE server(s) 9.8.1 General 9.8.2 Procedure 9.8.2.1 Information collection from NSCE server(s) subscribe request and response 9.8.2.2 Information collection from NSCE server(s) Notify 9.8.3 Information flows 9.8.4 APIs 9.8.4.1 General 9.8.4.2 SS_NSCE_InfoCollection_Subscribe operation 9.8.4.3 SS_NSCE_InfoCollection_Notify operation
...

9.8 Information collection from NSCE server(s) p. 65

9.8.1 General p. 65

The collected information by NSCE server could be exposed to other NSCE server(s) to optimize network resource allocation, based on the agreement among the NSCE servers. Then the NSCE server providing network slice related information acts as the producer, while the NSCE server obtaining network slice related information is the consumer.

9.8.2 Procedure p. 65

9.8.2.1 Information collection from NSCE server(s) subscribe request and response p. 65

Pre-condition:

The producer NSCE server #2 has agreement with consumer NSCE server #1 to provide the collected slice information.

Figure 9.8.2.1-1: Information collection from NSCE server(s) subscribe request and response

Step 1.

The NSCE server#1 sends out the information collection subscribe request with expected period and interested slice ID, e.g., List of SNSSAI. This step could be done by pre-configuration.

Step 2.

The NSCE server #2 shall check if the NSCE server #1 is authorized to get the network slice information.

Step 3.

After authentication, the NSCE server #2 collects slice information as defined in clause 9.7.2.1 step3, step4.

Step 4.

The NSCE server #2 sends collected slice information to NSCE server #1.

Step 5.

The NSCE server #1 may process the collected slice information (such as information aggregation), if needed.

9.8.2.2 Information collection from NSCE server(s) Notify p. 66

Reproduction of 3GPP TS 23.435, Fig. 9.8.2.2-1: Information collection from NSCE server(s) Notify

Figure 9.8.2.2-1: Information collection from NSCE server(s) Notify

Step 1.

Once the reporting period is reached or the threshold is crossed, the NSCE server #2 sends information collection notify to NSCE server #1.

9.8.3 Information flows p. 66

9.8.3.1 General p. 66

The following information flows are specified for Information collection from NSCE server(s):

Information collection from NSCE server(s) subscribe request, response and notify;

9.8.3.2 Information collection from NSCE server(s) subscribe request p. 66

Table 9.8.3.2-1 describes information elements for the Information collection from NSCE server(s) subscribe request from the consumer NSCE server to the producer NSCE server(s).

Table 9.8.3.2-1: Information collection from NSCE server(s) subscribe request

Information element	Status	Description
Requester Identifier	M	Unique identifier of the requester (i.e. NSCE server ID).
Security credentials	M	Security credentials resulting from a successful authorization for the NSCE service.
Notification Target Address	O	The Notification Target Address (e.g. URL) where the notifications destined for the requester should be sent to.
List of S-NSSAI(s)	M	Identifier of the interested network slice.
> QoS type indicator	O	QoS metric type including latency, throughput, jitter, etc.
> Threshold	O	Threshold of QoS metrics.
> Reporting period	O	Indicating the metrics reporting period.
> Immediate reporting flag	O	Indicating the request needs immediate reporting or not.
Proposed expiration time	O	Proposed expiration time for the subscription.

9.8.3.3 Information collection from NSCE server(s) subscribe response p. 66

The information elements specified in the Table 9.8.3.3-1 is used for the Information collection from NSCE server(s) subscribe response sent from the producer NSCE server to the consumer NSCE server.

Table 9.8.3.3-1: Information collection from NSCE server(s) subscribe Response

Information element	Status	Description
Result	M	Indicates the success or failure of the performance and analytics subscription.
> Subscription ID	O (see NOTE 1)	Subscription identifier corresponding to the subscription.
> Network slice related performance and analytics report	O (see NOTE 2)	Network slice related performance and analytics report as defined in Table 9.7.3.4-2.
> Cause	O (see NOTE 3)	Indicates the cause of request failure.
NOTE 1: Shall be present if the result is success and shall not be present otherwise. NOTE 2: May only be present if the result is success. NOTE 3: May only be present if the result is failure.

9.8.3.4 Information collection from NSCE server(s) notify p. 67

The information elements specified in Table 9.8.3.4-1 are used for the information collection from NSCE server(s) notify sent from the producer NSCE server to the consumer NSCE server.

Table 9.8.3.4-1: Information collection from NSCE server(s) Notify

Information element	Status	Description
Subscription ID	M	Subscription identifier corresponding to the subscription.
> Network slice related performance and analytics report	M	Network slice performance and analytics (i.e. slice load) with network slice identifier(i.e. S-NSSAI).