Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.435  Word version:  19.3.0

Top   Top   Up   Prev   Next
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.14 Network slice diagnostics  9.14.1 General  9.14.2 Procedure  9.14.2.1 Network slice diagnostics procedure  9.14.3 Information flows  9.14.4 APIs  9.14.4.1 General  9.14.4.2 SS_NSCE_Network_Slice_Diagnostics 
...

 

9.14  Network slice diagnostics  p. 95

9.14.1  General  p. 95

Network slice diagnostics provides possibility for the vertical/ASP using VAL server to receive information about the specific event(s) related to service experience. The vertical/ASP using the VAL server has estimated bad QoE for a mobile user or service - either reported from a mobile user or service or detected by application and can initiate a check with NSCE. The NSCE server can provide details related to the identified event.

9.14.2  Procedure  p. 95

9.14.2.1  Network slice diagnostics procedure  p. 95

In the procedure shown in Figure 9.14.2.1-1, a mechanism is provided to allow for vertical/ASP using VAL server to initiate request for network slice diagnostics and receive all the relevant information about specific events.
Pre-conditions:
  1. Enterprise hosting the VAL server has SLA for slice services with NSCE service provider.
  2. The VAL server has subscribed to the network slice capability enablement server managing slice services.
  3. The NSCE server has initiated monitoring and gathering statistical data about its managed slices from ADAES according to clause 8.3 and 8.7 of TS 23.436.
  4. The VAL server has identified there is specific event where the application has experienced service degradation (reported errors from VAL client for degraded service (bad quality), reported errors from application (downgrade of communication, detected communication errors).
Reproduction of 3GPP TS 23.435, Fig. 9.14.2.1-1: Network slice diagnostics procedure
Figure 9.14.2.1-1: Network slice diagnostics procedure
Up
Step 1.
The VAL server sends to NSCE server a network slice diagnostics request containing information about detected service degradation.
Step 2.
NSCE server determines which specific statistics to request from ADAES based on the indicated service degradation. If the service degradation is related to detected communication error, then slice usage pattern statistics are needed. If bad quality is reported from the VAL client slice-specific application performance statistics are needed. NSCE server collects the needed statistics based on the procedure described in clause 8.7.3 of TS 23.436.
Step 3.
Based on the received statistics information and input from VAL server, the NSCE server correlated data and prepares network slice diagnostics report about the needed diagnostics.
Step 4.
NSCE server sends network slice diagnostics reply to VAL server.
Up

9.14.3  Information flows  p. 96

9.14.3.1  General  p. 96

The following information flows are specified for Network slice diagnostics:
  • Network slice diagnostics request and response

9.14.3.2  Network slice diagnostics request and response  p. 96

Table 9.14.3.2-1 and Table 9.14.3.2-2 describe information elements for the network slice diagnostics request and response between the VAL server and the NSCE server.
Information element Status Description
VAL informationMThe information of the VAL server.
Network Slice Diagnostics IDMIdentifier of the network slice diagnostics.
Service degradation typeMThe information of service degradation.
> VAL service identityMIdentifier of the VAL service to be monitored.
> ErrorsListMThe list of registered errors by VAL server.
>> ErrorNameMThe name of the reported error: detected communication error; RTT above limit; QoS downgrade.
>> Network slice related Identifier(s)MIdentifier(s) of the network slice to be checked.
>> UE(s) related Identifier(s)OIdentifier(s) of the related UE(s).
>> Area of interestOThe service area for which the requirement applies, which can be expressed as a geographical area (e.g. geographical coordinates), or a topological area (e.g. a list of TA).
>> StartTimeMThe start time point of the registered service degradation.
>> EndTimeMThe end time point of the registered service degradation.
Information element Status Description
ResultMIndicates the success or failure of network slice diagnostics request.
> Network slice Diagnostics IDO
(see NOTE 1)		Identifier of the network slice diagnostics.
> StartTimeO
(see NOTE 1)		The start time point of the available data for network slice service degradation.
> EndTimeO
(see NOTE 1)		The start time point of the available data for network slice service degradation.
> Data typeO
(see NOTE 1)		The type of the reported data samples (UE data, network data, application data).
> Data outputO
(see NOTE 1)		The reported data related to the reported error(s) in the network slice diagnostics request.
> CauseO
(see NOTE 2)		Indicates the cause of the network slice diagnostics request failure.
NOTE 1:
Shall be present if the result is success.
NOTE 2:
Shall be present if the result is failure.
Up

9.14.4  APIs  p. 97

9.14.4.1  General  p. 97

Table 9.14.3.2-1 and Table 9.14.3.2-2 illustrate the API for network slice diagnostics.
API Name API Operations Known Consumer(s) Communication Type
SS_NSCE_Network Slice DiagnosticsNetwork Slice DiagnosticsVAL serverRequest / Response
Up

9.14.4.2  SS_NSCE_Network_Slice_Diagnostics  p. 98

9.14.4.2.1  General  p. 98
API description:
This API enables the VAL server to communicate with the network slice capability enablement server for requesting network slice diagnostics over NSCE-S.
9.14.4.2.2  Network_Slice_Diagnostics  p. 98
API operation name:
Network_Slice_Diagnostics
Description:
Request for Network_Slice_Diagnostics to the NSCE server and receiving a response / result.
Known Consumers:
VAL server.
Inputs:
See Table 9.14.3.2-1.
Outputs:
See Table 9.14.3.2-2.

Up   Top   ToC