Abstract: A device determines, from a network slice template associated with a network slice, a quality of service (QoS) profile for the network slice that includes performance metrics for corresponding QoS parameters associated with providing a service. The device monitors performance of the network slice in association with the QoS profile, and determines, based on the performance, that a performance indicator for a QoS parameter of the network slice is outside a threshold range of a performance metric. The device determines, based on the performance information and the QoS profile, a slice modification to the network slice template for the network slice, where the slice modification is configured to cause the performance indicator to be within the threshold range of the performance metric. The device causes a network slice orchestrator to update an instantiation of the network slice according to the slice modification and the network slice template.

Abstract: A device determines, from a network slice template associated with a network slice, a quality of service (QoS) profile for the network slice that includes performance metrics for corresponding QoS parameters associated with providing a service. The device monitors performance of the network slice in association with the QoS profile, and determines, based on the performance, that a performance indicator for a QoS parameter of the network slice is outside a threshold range of a performance metric. The device determines, based on the performance information and the QoS profile, a slice modification to the network slice template for the network slice, where the slice modification is configured to cause the performance indicator to be within the threshold range of the performance metric. The device causes a network slice orchestrator to update an instantiation of the network slice according to the slice modification and the network slice template.

Abstract: The present disclosure provides a framework for quantitatively testing network services and their supporting APIs. To facilitate the testing, a testing script may be generated. The testing script may be parameterized with input data derived from a historical database. The testing script may be executed and responses received from the network during testing may be analyzed to determine metrics associated with execution of the testing script. The metrics may indicate successfully tested conditions, unsuccessfully tested conditions, untested conditions, other testing metrics, or a combination thereof. After the initial testing cycle a determination is made regarding whether a stop condition has been satisfied and if it has not been satisfied, another testing cycle may be executed. The next testing cycle may utilize a different set of input data that may be dissimilar to the input data used in the previous testing cycle so that additional conditions and functionality may be tested.