Patent classifications
H04L41/5022
Bandwidth part configuration for network slicing
A slice manager associated with a network access point of a telecommunication network can manage combinations of network slices and bandwidth parts for user equipment (UE). The bandwidth parts can have independently set numerologies, such as subcarrier spacing values. The UE can be configured to use one or more active bandwidth parts at a time, such that the slice manager can instruct the UE to use multiple active bandwidth parts simultaneously with respect to the same network slice or multiple network slices.
Intent execution method and apparatus
The present disclosure relates to intent execution methods and apparatus. In one example method, an element management system (EMS) receives a first intent from a network management system (NMS). The first intent indicates the EMS to execute a first command on a first network element and execute a second command on a second network element, a second intent in an active state is maintained in the EMS, the second intent indicates the EMS to execute a third command on the first network element, and the first command and the third command are mutually exclusive. The EMS receives a first parameter and conflict policy information. The EMS determines whether to execute the second command on the second network element, and executes the first command or the third command on the first network element based on the conflict policy information.
Intent execution method and apparatus
The present disclosure relates to intent execution methods and apparatus. In one example method, an element management system (EMS) receives a first intent from a network management system (NMS). The first intent indicates the EMS to execute a first command on a first network element and execute a second command on a second network element, a second intent in an active state is maintained in the EMS, the second intent indicates the EMS to execute a third command on the first network element, and the first command and the third command are mutually exclusive. The EMS receives a first parameter and conflict policy information. The EMS determines whether to execute the second command on the second network element, and executes the first command or the third command on the first network element based on the conflict policy information.
SYSTEMS AND METHODS FOR AUTOMATING NETWORK SLICE CONFIGURATION
In some implementations, a first device may receive, from a second device, network function (NF) configuration information indicating that an NF instance is to be provisioned to support a combination of network slices. The NF configuration information may include first network slice information regarding the first network slice and second network slice information regarding the second network slice. The first device may obtain, from a data structure, first slice configuration information associated with the NF instance supporting the first network slice and second slice configuration information associated with the NF instance supporting the second network slice. The first device may generate configuration parameters to provision the NF instance to support the combination of network slices and provide the configuration parameters to cause the NF instance to be provisioned to support the combination of network slices.
SYSTEMS AND METHODS FOR AUTOMATING NETWORK SLICE CONFIGURATION
In some implementations, a first device may receive, from a second device, network function (NF) configuration information indicating that an NF instance is to be provisioned to support a combination of network slices. The NF configuration information may include first network slice information regarding the first network slice and second network slice information regarding the second network slice. The first device may obtain, from a data structure, first slice configuration information associated with the NF instance supporting the first network slice and second slice configuration information associated with the NF instance supporting the second network slice. The first device may generate configuration parameters to provision the NF instance to support the combination of network slices and provide the configuration parameters to cause the NF instance to be provisioned to support the combination of network slices.
DETECTING CRITICAL REGIONS AND PATHS IN THE CORE NETWORK FOR APPLICATION-DRIVEN PREDICTIVE ROUTING
In one embodiment, a device obtains quality of experience metrics for an online application. The device generates a mapping between network paths traversed by traffic of the online application and the quality of experience metrics. The device identifies a core entity along the network paths that is responsible for degradation of the quality of experience metrics. The device sends an alert regarding the core entity, whereby the alert causes the traffic of the online application to avoid the core entity.
Shim layer for extracting and prioritizing underlying rules for modeling network intents
Systems, methods, and computer-readable media for receiving one or more models of network intents, comprising a plurality of contracts between providers and consumers, each contract containing entries with priority values. Each contract is flattened into a listing of rules and a new priority value is calculated. The listing of rules encodes the implementation of the contract between the providers and the consumers. Each entry is iterated over and added to a listing of entries if it is not already present. For each rule, the one or more entries associated with the contract from which the rule was flattened are identified, and for each given entry a flat rule comprising the combination of the rule and the entry is generated, wherein a flattened priority is calculated based at least in part on the priority value of the given one of given entry and the priority value of the rule.
Shim layer for extracting and prioritizing underlying rules for modeling network intents
Systems, methods, and computer-readable media for receiving one or more models of network intents, comprising a plurality of contracts between providers and consumers, each contract containing entries with priority values. Each contract is flattened into a listing of rules and a new priority value is calculated. The listing of rules encodes the implementation of the contract between the providers and the consumers. Each entry is iterated over and added to a listing of entries if it is not already present. For each rule, the one or more entries associated with the contract from which the rule was flattened are identified, and for each given entry a flat rule comprising the combination of the rule and the entry is generated, wherein a flattened priority is calculated based at least in part on the priority value of the given one of given entry and the priority value of the rule.
Computer network troubleshooting
- Arjun Mathur ,
- Andrew Ash ,
- Anuraag Bahl ,
- Andy Chen ,
- Aydin Keskin ,
- Christopher Rogers ,
- Anshuman Prasad ,
- Ankit Shankar ,
- Casey Patton ,
- Christopher Wynnyk ,
- Joanna Peller ,
- Jonathan Victor ,
- Mackenzie Bohannon ,
- Mitchell Skiles ,
- Nikhil Taneja ,
- Ryan Norris ,
- Scott Adams ,
- Samuel Sinensky ,
- Sri Krishna Vempati ,
- Thomas Mathew ,
- Vinoo Ganesh ,
- Rahij Ramsharan
A system for troubleshooting network problems is disclosed. A model can use demographic information, network usage information, and network membership information to determine an importance of a problem. The importance of the problem for the user who reported the problem, a number of other users affected by the problem, and the importance of the problem to the other users can be used to determine a priority for resolving the problem. Before and after a work order is executed to resolve the problem, network metrics can be gathered, including aggregate network metrics, and automatically presented in various user interfaces. The analysis of the metrics can be used to update a database of which work orders are assigned in response to which problems.
Computer network troubleshooting
- Arjun Mathur ,
- Andrew Ash ,
- Anuraag Bahl ,
- Andy Chen ,
- Aydin Keskin ,
- Christopher Rogers ,
- Anshuman Prasad ,
- Ankit Shankar ,
- Casey Patton ,
- Christopher Wynnyk ,
- Joanna Peller ,
- Jonathan Victor ,
- Mackenzie Bohannon ,
- Mitchell Skiles ,
- Nikhil Taneja ,
- Ryan Norris ,
- Scott Adams ,
- Samuel Sinensky ,
- Sri Krishna Vempati ,
- Thomas Mathew ,
- Vinoo Ganesh ,
- Rahij Ramsharan
A system for troubleshooting network problems is disclosed. A model can use demographic information, network usage information, and network membership information to determine an importance of a problem. The importance of the problem for the user who reported the problem, a number of other users affected by the problem, and the importance of the problem to the other users can be used to determine a priority for resolving the problem. Before and after a work order is executed to resolve the problem, network metrics can be gathered, including aggregate network metrics, and automatically presented in various user interfaces. The analysis of the metrics can be used to update a database of which work orders are assigned in response to which problems.