4 Communication service assurance service

28.5363GPPManagement and orchestrationManagement services for communication service assuranceRelease 17Stage 2 and stage 3TS

4.1 Stage 2

4.1.1 Void

4.1.2 Model

4.1.2.1 Imported and associated information entities

4.1.2.1.1 Imported information entities and local labels

Label reference	Local label
TS 28.622 [5], IOC, Top	Top

4.1.2.1.2 Associated information entities and local labels

Label reference	Local label
TS 28.622 [5], IOC, SubNetwork	SubNetwork
TS 28.541 [6], IOC, NetWorkSlice	NetworkSlice
TS 28.541 [6], IOC, NetWorkSliceSubnet	NetworkSliceSubnet
TS 28.622 [5], IOC, ManagedElement	ManagedElement
TS 28.541 [6], attribute, serviceProfileId	serviceProfileId
TS 28.541 [6], attribute, sliceProfileId	sliceProfileId
TS 28.541 [6], attribute, taiList	taiList

4.1.2.2 Class diagram

4.1.2.2.1 Relationships

This clause depicts the set of classes that encapsulates the information relevant for this MnS. This clause provides an overview of the relationships between relevant classes in UML. This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes.

Figure 4.1.2.2.1.1: Assurance management NRM fragment

4.1.2.2.2 Inheritance

Figure 4.1.2.2.2.1: Assurance management inheritance relationships

4.1.2.3 Class definitions

4.1.2.3.1 AssuranceClosedControlLoop

4.1.2.3.1.1 Definition

This class represents the information for controlling and monitoring an assurance closed control loop associated with a NetworkSlice or NetworkSliceSubnet. It can be name-contained by SubNetwork or ManagedElement.

To express the assurance closed control loop goals, the MnS consumer needs to request the MnS producer to create an AssuranceClosedControlLoop on the MnS producer. The MnS producer may trigger to create the AssuranceClosedControlLoop as well, for example, when an instance of NetworkSlice or NetworkSliceSubnet is created, MnS producer may create an instance of AssuranceClosedControlLoop associated to the instance of NetworkSlice or NetworkSliceSubnet to assure the target described in ServiceProfile or SliceProfile. For the deletion of the assurance closed control loop, the MnS consumer needs to request the MnS producer to delete the AssuranceClosedControlLoop to free up resources on the MnS producer. MnS producer also can trigger to delete AssuranceClosedControlLoop to free up resources by itself.

For temporary deactivation of the assurance closed control loop, the MnS consumer can modify the value of the administrative state attribute to “LOCKED”. The MnS producer may disable the assurance closed control loop, for example in conflict situations, by setting the operational state attribute to “disabled”. When a closed control loop is enabled by the MnS producer, the operational state is set again to “enabled”. For the activation of an assurance closed control loop, the MnS consumer can modify the value of the administrative state attribute to “UNLOCKED”.

An AssuranceClosedControlLoop can name-contain multiple instances of AssuranceGoal which represents the assurance goal and corresponding observed or predicted goal fulfilment information (see clause 4.1.2.3.2). The AssuranceGoal may optionally include an assurance scope in terms of location (see clause 4.1.2.3.2).

The attribute “controlLoopLifeCyclePhase” is used to keep track of the lifecycle of an AssuranceClosedControlLoop.

The attribute aCCLDisallowedList is used to descope the ACCL. See clause 6.1.6 of TS 28.535 [17]. Each entry in the list indicates a specific list of attributes belonging to a managedEntity identified by the managedEntityIdentifier which the ACCL is not allowed to modify.

4.1.2.3.1.2 Attributes

The AssuranceClosedControlLoop IOC includes attributes inherited from Top IOC (defined TS 28.622[5]) and the following attributes:

Attribute name	S	isReadable	isWritable	isInvariant	isNotifyable
operationalState	M	T	F	F	T
administrativeState	M	T	T	F	T
controlLoopLifeCyclePhase	M	T	T	F	T
aCCLDisallowedList	O	T	T	F	T
Attributes related to role
networkSliceRef	CM	T	T	F	T
networkSliceSubnetRef	CM	T	T	F	T

4.1.2.3.1.3 Constraints

Name	Definition
networkSliceSubnetRef	Condition: the AssuranceGoal applies to a NetworkSliceSubNet
networkSliceRef	Condition: the AssuranceGoal applies to a NetworkSlice

4.1.2.3.1.4 Notifications

The common notifications defined in clause 4.1.2.5 are valid for this IOC, without exceptions or additions.

4.1.2.3.2 AssuranceGoal

4.1.2.3.2.1 Definition

This IOC represents assurance goal.

To express a new assurance goal for the assurance closed control loop, the MnS consumer needs to request the MnS producer to create an instance of AssuranceGoal. MnS producer can also trigger the creation of an instance of AssuranceGoal. For example, when a new instance NetworkSlice or NetworkSliceSubnet is created on the MnS producer and the corresponding SLS needs to be assured, a new instance of AssuranceGoal needs to be created and associated to the new instance NetworkSlice or NetworkSliceSubnet by configuring the attributes “networkSliceRef” or “networkSliceSubnetRef” and corresponding attributes “serviceProfileId” and “sliceProfileId”.

The attribute “assuranceTargetList” defines a list of assurance targets (the subset of attributes from an SLS, i.e. a ServiceProfile or a SliceProfile, that are subject to assurance requirements.) that should be assured by the AssuranceClosedControlLoop. The attribute “assuranceTargetList” is configured by MnS producer based on the specified ServiceProfile or SliceProfile.

NOTE: Multiple instances of AssuranceGoal can be created for a single instance of NetworkSlice or NetworkSliceSubnet.

4.1.2.3.2.2 Attributes

The AssuranceGoal IOC includes attributes inherited from Top IOC (defined TS 28.622[5]) and the following attributes:

Attribute name	S	isReadable	isWritable	isInvariant	isNotifyable
assuranceTargetList	M	T	F	F	T
sliceProfileId	CM	T	T	F	T
serviceProfileId	CM	T	T	F	T
observationTime	M	T	T	F	T

.

4.1.2.3.2.3 Attribute constraints

Name	Definition
sliceProfileId	Condition: the AssuranceGoal applies to a NetworkSliceSubNet
serviceProfileId	Condition: the AssuranceGoal applies to a NetworkSlice

4.1.2.3.2.4 Notifications

The common notifications defined in subclause 4.1.2.5 are valid for this IOC, without exceptions or additions.

4.1.2.3.3 Void

4.1.2.3.4 Void

4.1.2.3.5 AssuranceTarget <<dataType>>

4.1.2.3.5.1 Definition

This data type represents a single attribute name-value-pair of which one or more are included in an AssuranceGoal.

4.1.2.3.5.2 Attributes

Attribute name	S	isReadable	isWritable	isInvariant	isNotifyable
assuranceTargetName	M	T	T	F	T
assuranceTargetValue	M	T	F	F	T

4.1.2.3.5.3 Attribute constraints

No constraints have been defined for this document.

4.1.2.3.5.4 Notifications

The common notifications defined in clause 4.1.2.5 are valid for the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.

4.1.2.3.6 AssuranceGoalStatus <<dataType>>

4.1.2.3.6.1 Definition

This data type represents the observed and/or predicted AssuranceGoal fulfilment status.

To obtain the observed predicted status of the the goal fulfilment information, the MnS consumer can query the attributes “AssuranceGoalStatusObserved” and “AssuranceGoalStatusPredicted”from MnS producer. The attributes “AssuranceGoalStatusObserved” and “AssuranceGoalStatusPredicted” are configured by MnS producer at the end of an observation period. The observation period is assigned by MnS consumer through requesting the MnS producer to set attribute “observationTime”. The status of the goal fuilfilment is considered FULFILLED if all the constituent targets are FULFILLED.

4.1.2.3.6.2 Attributes

Attribute name	Support Qualifier	isReadable	isWritable	isInvariant	isNotifyable
assuranceGoalStatusId	M	T	F	F	T
assuranceGoalId	O	T	F	F	T
assuranceGoalStatusObserved	O	T	F	F	T
assuranceGoalStatusPredicted	O	T	F	F	T
assuranceTargetStatusList	O	T	F	F	T

4.1.2.3.6.3 Attribute constraints

No constraints have been defined for this document.

4.1.2.3.6.4 Notifications

The common notifications defined in clause 4.1.2.5 are valid for this <<IOC>> , without exceptions or additions.

4.1.2.3.7 AssuranceTargetStatus <<dataType>>

4.1.2.3.7.1 Definition

This data type represents the observed and/or predicted target fulfilment status.

To obtain the observed predicted status of the the target fulfilment information, the MnS consumer can query the attributes “AssuranceTargetStatusObserved” and “AssuranceTargetPredicted” from MnS producer. The attributes“AssuranceTargetStatusObserved” and “AssuranceTargetStatusPredicted” are configured by MnS producer at the end of an observation period. The observation period is assigned by MnS consumer through requesting the MnS producer to set attribute “observationTime”. The status of the target fuilfilment is considered FULFILLED if all the constituent target are FULFILLED.

Attribute name	Support Qualifier	isReadable	isWritable	isInvariant	isNotifyable
assuranceTargetStatusId	M	T	F	F	T
assuranceTargetName	O	T	F	F	T
assuranceTargetStatusObserved	O	T	F	F	T
assuranceTargetStatusPredicted	O	T	F	F	T

4.1.2.3.7.3 Attribute constraints

No constraints have been defined for this document.

4.1.2.3.7.4 Notifications

The common notifications defined in clause 4.1.2.5 are valid for the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.

4.1.2.3.8 AssuranceReport <<IOC>>

4.1.2.3.8.1 Definition

This class represents the attributes of assurance report, e.g, the information about one or multiple AssuranceGoalStatus and one or multiple AssuranceTargetStatus.

The attribute “assuranceGoalStatusList” defines a list of AssuranceGoalStatus.

AssuranceReport represents the monitoring information of an assurance closed control loop. An AssuranceReport is contained by an AssuranceClosedControlLoop. There is one AssuranceReport per assurance closed control loop for an observation time. The content of the AssuranceReport may be different for different observation time. According to the AssuranceGoal and the AssuranceReport, the consumer performs closed control loop governance as described in clause "4.2.5 Closed control loop governance and monitoring" in TS 28.535 [17].

4.1.2.3.8.2 Attributes

Attribute name	Support Qualifier	isReadable	isWritable	isInvariant	isNotifyable
assuranceGoalStatusList	O	T	F	F	T
Attributes related to role
assuranceGoalRef	O	T	F	F	T

4.1.2.3.8.3 Attribute constraints

No constraints have been defined for this document

4.1.2.3.8.4 Notifications

The common notifications defined in subclause 4.1.2.5 are valid for this IOC, without exceptions or additions.

4.1.2.3.6 AssuranceScope <<dataType>>

4.1.2.3.6.1 Definition

It indicates the target for assurance goal in terms of location. A particular ACCL can target for a particular location. The assurance goal status is ascertained based on the appropriately collected performance measurements as per the target location.

4.1.2.3.6.2 Attributes

Attribute name	S	isReadable	isWritable	isInvariant	isNotifyable
taiList	O	T	T	F	T

4.1.2.3.6.3 Attribute constraints

No constraints have been defined for this document.

4.1.2.3.6.4 Notifications

The common notifications defined in clause 4.1.2.5 are valid for the <<IOC>> using this <<dataType>> as one of its attributes, shall be applicable.

4.1.2.3.7 ACCLDisallowedAttributes <<datatype>>

4.1.2.3.7.1 Definition

This data type represents attributes which an ACCL is not allowed to change. The first attribute “managedEntityIdentifier” identifies the DN of the SubNetwork or ManagedElement, the second attribute is a list of attributeNames of the Subnetwork or ManagedElement.

4.1.2.3.7.2 Attributes

Attribute name	Support Qualifier	isReadable	isWritable	isInvariant	isNotifyable
managedEntityIdentifier	M	T	T	F	T
attributeNameList	M	T	T	F	T

4.1.2.3.7.3 Constraints

No constraints have been defined for this document.

4.1.2.3.7.4 Notifications

The common notifications defined in clause 4.1.2.5 are valid for this IOC, without exceptions or additions.

4.1.2.4 Attribute definitions

4.1.2.4.1 Attribute properties

The following table defines the properties of attributes that are specified in the present document.

Table 4.1.2.4.1.1

Attribute Name	Documentation and Allowed Values	Properties
controlLoopLifeCyclePhase	It indicates the lifecycle phase of the AssuranceClosedControlLoop instance. AllowedValues: Preparation, Commissioning, Operation and Decommissioning.	type: Enum multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: NULL isNullable: False
assuranceTargetName	The name of the attribute which is part of AssuranceTarget and AssuranceTargetStatus. The assuranceTargetName uniquely identifies the name of an AssuranceTarget instance in corresponding AssuranceTargetStatus instance. The assuranceTargetName shall be equal to the name of an attribute in the relevant ServiceProfile or SliceProfile. The relevant ServiceProfile or SliceProfile is identified by the attribute serviceProfileId or sliceProfileId in the AssuranceGoal.	type: String multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceTargetValue	The value of the attribute which is part of AssuranceTarget	type: String multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceTargetList	This is an attribute containing a list of AssuranceTarget(s) that are part of an AssuranceGoal	type: AssuranceTarget multiplicity: 1..* isOrdered: False isUnique: True defaultValue: None isNullable: False
observationTime	It indicates the observation period of assuranceGoalStatusObserved and assuranceGoalStatusPredicted. The assurance goal will be observed from the start of each observation period, then at the end of each observation period, the value for assuranceGoalStatusObserved and assuranceGoalStatusPredicted will be derived and configured. The observation time is expressed in seconds.	type: Integer multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceGoalStatusObserved	It holds the status of the observed goal fulfilment to the assuranceGoal. The value is FULFILLED only if all the constituent assuranceTargetStatusObserved are FULFILLED. During the initial operation of a closed control loop no fulfilment information may be available to report, the value NO_REPORT will be used. allowedValues: "NO_REPORT , "FULFILLED", “NOT_FULFILLED Editor’s Note: Whether a more suiteable phrase for NO_REPLY is needed is FFS.	type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceGoalStatusPredicted	It holds the status of the predicted future goal fulfilment to the assuranceGoal . The value is FULFILLED only if all the constituent assuranceTargetStatusPredicted are FULFILLED. During the initial operation of a closed control loop no fulfilment information may be available to report, the value NO_REPORT will be used. allowedValues: "NO_REPORT", "FULFILLED", “NOT_FULFILLED". Editor’s Note: Whether a more suiteable phrase for NO_REPLY is needed is FFS.	type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceTargetStatusObserved	It holds the status of the observed target fulfilment to the assuranceGoal. allowedValues: "FULFILLED", “NOT_FULFILLED	type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceTargetStatusPredicted	It holds the status of the predicted future target fulfilment to the assuranceGoal allowedValues: "FULFILLED", “NOT_FULFILLED"	type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
networkSliceRef	It holds the reference to the NetworkSlice instance subject to assurance requirements	type: Dn multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
networkSliceSubnetRef	It holds the reference to the NetworkSliceSubnet instance subject to assurance requirements	type: Dn multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
operationalState	It indicates the operational state of the AssuranceClosedControlLoop instance. It describes whether the resource is installed and partially or fully operable (Enabled) or the resource is not installed or not operable (Disabled). Allowed values; Enabled/Disabled allowedValues: "ENABLED", "DISABLED". The meaning of these values is as defined in 3GPP TS 28.625 [14] and ITU-T X.731 [15].	type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: Disabled allowedValues: Enabled, Disabled isNullable: False
administrativeState	It indicates the administrative state of the AssuranceClosedControlLoop instance. It describes the permission to use or the prohibition against using the AssuranceClosedControlLoop instance. The administrative state is set by the MnS consumer. Allowed values; Locked/Unlocked allowedValues: "LOCKED", "UNLOCKED". The meaning of these values is as defined in 3GPP TS 28.625 [14] and ITU-T X.731 [15].	type: ENUM multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: Locked allowedValues: Locked, Unlocked isNullable: False
assuranceScope	It indicates the target for assurance goal in terms of a particular location. Allowed values: Not Applicable	type: AssuranceScope multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: NA allowedValues: NA isNullable: False
ManagedEntityIdentifier	The DN of a managed entity Allowed values: not applicable	Type: DN multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: NA allowedValues: NA isNullable: True
attributeNameList	This is a list parameter identifies a list ofthe attributes names of a ManagedElement or a Subnetwork identified with ManagedEntityIdentifier that are not allowed to be modified by an ACCL. Allowed values: not applicable	Type: AttributeNameList of String multiplicity: 1..* isOrdered: TrueFalse isUnique: True defaultValue: NA allowedValues: NA isNullable: True
aCCLDisallowedList	This is a list of ACCLDisallowedAttributesparameter identifies the list of ManagedElement or Subnetwork identified with ManagedEntityIdentifier and corresponding attributes that are not allowed to be modified by an ACCL. Allowed values: not applicable	Type: ACCLDisallowedAttributes multiplicity: 1..* isOrdered: TrueFalse isUnique: True defaultValue: NA allowedValues: NA isNullable: True
assuranceGoalStatusId	The indication of the AssuranceGoalStatus.	type: IntegerString multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceTargetStatusId	The indication of the AssuranceTargetStatus.	type: IntegerString multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceGoalStatusList	This is an attribute containing a list of assuranceGoalStatus	type: AssuranceGoalStatus multiplicity: 1..* isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceTargetStatusList	This is an attribute containing a list of assuranceTargetStatus	type: AssuranceTargetStatus multiplicity: 1..* isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
assuranceGoalDnId	It holds the identity in AssuranceGoalStatus that uniquely identifies the corresponding Dn of the AssuranceGoal instance for which the assuranceGoalStatus applies	type: Dn multiplicity: 1 isOrdered: N/A isUnique: N/A defaultValue: None isNullable: False
NOTE 1: Void NOTE 2: Void

4.1.2.4.2 Constraints

No constraints have been identified for this document.

4.1.2.4.3 Notifications

This subclause presents a list of notifications, defined in [7], that provisioning management service consumer can receive. The notification parameter objectClass/objectInstance, defined in [10], would capture the DN of an instance of an IOC defined in the present document.

4.1.2.5 Common notifications

4.1.2.5.1 Alarm notifications

This clause presents a list of notifications, defined in TS 28.532 [7], that an MnS consumer may receive. The notification header attribute objectClass/objectInstance, defined in TS 32.302 [8], shall capture the DN of an instance of a class defined in the present document.

Name	Qualifier	Notes
notifyNewAlarm	M	—
notifyClearedAlarm	M	—
notifyAckStateChanged	M	—
notifyAlarmListRebuilt	M	—
notifyChangedAlarm	O	—
notifyCorrelatedNotificationChanged	O	—
notifyChangedAlarmGeneral	O	—
notifyComments	O	—
notifyPotentialFaultyAlarmList	O	—

4.1.2.5.2 Configuration notifications

This clause presents a list of notifications, defined in TS 28.532 [7], that an MnS consumer may receive. The notification header attribute objectClass/objectInstance, defined in TS 32.302 [8], shall capture the DN of an instance of a class defined in the present document.

Name	Qualifier	Notes
notifyMOICreation	O	—
notifyMOIDeletion	O	—
notifyMOIAttributeValueChanges	O	—
notifyMOIChanges	O	—
notifyEvent	O	—

4.1.3 Procedures

4.1.3.1 SLS Assurance Procedure

Figure 4.1.3.1.1 SLS assurance procedure

For the purpose of the procedure shown in Figure 4.1.3.1.1 "entities participating in the loop" refers to any entity in the 3GPP management system responsible for the functioning of an ACCL to ensure the AssuranceControlLoopGoal required by an AssuranceControlLoop_Consumer.

1. AssuranceControlLoop_consumer derives AssuranceControlLoopGoal from the ServiceProfile or SliceProfile.

2. AssuranceControlLoop_consumer provides the AssuranceControlLoopGoal to Entities_Participating_in_loop by utilizing the provision management services defined in as defined in clause 11.1.1.3 of TS 28.532 [7].

NOTE 1: In case the Entities_Participating_in_loop represents CrossDomain_Entities_Participating_in_loop, the AssuranceControlLoopGoal is the attribute(s) of the ServiceProfile. In case the Entities_Participating_in_loop represents Domain_Entities_Participating_in_loop, the AssuranceControlLoopGoal is the attribute(s) of the SliceProfile.

3. Entities_Participating_in_loop subscribes the related performance data (e.g., the packet delay related measurements), fault data, QoE data (e.g., buffer level) and MDT data from respective sources by utilizing the Operation establishStreamingConnection as defined in clause 6.2.1 of TS 28.550 [3].

4. Entities_Participating_in_loop, optionally, subscribes the related analytical data from MDAS or network functions, e.g., NWDAF. In case of NWDAF as a provider, Nnwdaf_EventsSubscription Service as defined in clause 4.2 of TS 29.520 [11] is used.

5. Entities_Participating_in_loop collects the related performance, fault, QoE and MDT data (e.g., the packet delay related measurements), fault data, QoE data (e.g., buffer level) and MDT data from respective sources by utilizing the Operation establishStreamingConnection as defined in clause 6.2.1 of TS 28.550 [3].

6. Entities_Participating_in_loop, optionally, collects the related analytical data from MDAS or network functions, e.g., NWDAF. In case of NWDAF as a provider, Nnwdaf_EventsSubscription Service as defined in clause 4.2 of TS 29.520 [11] is used.

7. Entities_Participating_in_loop assesses if the AssuranceControlLoopGoal has been fulfilled.

8. Entities_Participating_in_loop assesses if and which action to take in case the AssuranceControlLoopGoal has not been fulfilled.

9. As per the mitigation action (e.g., scale out) resources are changed, the generic provisioning management service as defined in clause 11.1 of TS 28.532 [7] is utilized for the same.

10. Action completed.

NOTE 2: The Entities_Participating_in_loop continues to monitor and analyse the performance and perform the adjustment until the attribute(s) of SliceProfile is assured.

11. AssuranceControlLoop_consumer receives the confirmation of assurance fulfilment from Entities_Participating_in_loop by utilizing the provision management services defined in clause 11.1.1.3 of TS 28.532 [7].

4.2 Stage 3

4.2.1 Solution Set (SS) for JSON/YAML

The JSON/YAML solution set is documented in clause B.2.

Annex A (informative):
Control loop deployed in different layers

A.1 Introduction

This example gives a high-level view of control loops deployed in different layers, which consists of control loop in communication service layer, control loop in network slice layer, control loop in network slice subnet layer and control loop in NF layer, as described as Figure A.1.1, where the analytic could be leverage MDAS, and different control loops can provide input (interact with) to other control loops (in the same layer or different layers) and obtain the output from other control loops (in the same layer or different layers).

Figure A.1.1: Control loop in different layers

A.2 Control loop in communication service layer

SLA/SLS requirements provided from CSC are translated into serviceProfile, which represents the requirements for communication service assurance to the CSP. Coordination between control loop in communication service layer and control loop in network slice layer is needed to calculate the communication service resource requirements and to assure the communication service SLA/SLS requirements.

When the communication service is active, network slice performance is monitored and analysed for the communication service according to end user service experiences.

If service degradation occurs or it is predicted, the 3GPP management system could take actions, i.e. the allocated resources are scaled up or the SLS is adjusted based on pre-agreement/interaction between CSP and CSC.

A.3 Control loop in network slice layer

After receiving SLA/SLS requirements from service profile and completing the network slice provisioning, the network slice performance (e.g. KPI, QoE) are monitored and reported. Compared to the SLA/SLS requirements from service profile, when network slice performance is not met, the 3GPP management system identifies the root cause and may reconfigure the resources according to analytical report from MDAS producer. The network slice resources are also modified accordantly in case the network slice performance requirement needs to be changed based on communication service requirement adjustment.

A.4 Control loop in network slice subnet layer

After decomposing service profile to slice profile, the performance requirements for each network slice subnet are obtained. The 3GPP management system could have the capability of service observation (e.g., the supervision to the NSSI) based on MDAS. Based on such observation and comparison with initial subnet performance requirements, management actions on the NSSI might be performed if NSSI performance requirements fulfillment indicates a problem. Another possible scenario is that, when the NSSI performance requirement is changed because of the network slice modification management action, the NSSI resources might be also reconfigured.

A.5 Control loop in NF layer

NOTE: The control loop in NF layer is not addressed in the present document.

Annex B (normative):
OpenAPI definition of the COSLA NRM