Network Service Orchestration for Overlapping Configuration Conflicts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network management systems face inefficiencies and conflicts when managing parallel execution of network services with overlapping device configurations, leading to increased processing times and reduced throughput due to shared ownership of configuration nodes.
Innovation Solution
Implementing an optimistic concurrency control protocol with guarded commands to record service metadata changes during the service invocation phase, allowing for parallel execution of network services by detecting and resolving conflicts through retry mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional network management systems configure services for individual managed devices, then network services can be deployed, but processing time increases and throughput decreases due to sequential conflict resolution
Solution Approach 1:
The system performs preliminary conflict detection by examining service metadata and configuration node ownership information before executing service transactions. This preliminary action identifies potential conflicts early, allowing the system to resolve them before they impact throughput, thus maintaining reliability while improving productivity.
Solution Approach 2:
The patent introduces an intermediary conflict detection and resolution mechanism that acts as a mediator between parallel service transactions. This intermediary layer analyzes service metadata, detects conflicts regarding configuration node ownership, and resolves them through retry logic, enabling parallel execution without sacrificing configuration correctness.
2Productivity
If network services are executed in parallel with overlapping device configurations, then throughput improves, but conflicts increase leading to service restarts
Solution Approach 1:
The system performs preliminary conflict detection by examining service metadata and configuration node ownership information before executing service transactions. This preliminary action identifies potential conflicts early, allowing the system to resolve them before they impact throughput, thus maintaining reliability while improving productivity.
Solution Approach 2:
The patent implements a feedback mechanism where conflict detection results from service metadata analysis feed into retry logic. When conflicts are detected, the system uses feedback from the conflict resolution process to retry service transactions with adjusted timing or sequencing, reducing unnecessary service restarts and time loss.
3Measurement precision
If service metadata is tracked for conflict detection, then parallel execution accuracy improves, but system complexity increases
Solution Approach 1:
The patent extracts service metadata (ownership information, configuration node identifiers) from the service transaction context and stores it separately in a data store. This extraction allows the conflict detection mechanism to access precise metadata without adding complexity to the core service execution logic, maintaining measurement precision while managing system complexity.
Data Source
AI summary
Techniques, methods, and systems for managing a set of data network nodes in a Network Management System (NMS). In some examples, a method may include receiving, at the network orchestrator, a service invocation for a service transaction associated with a transaction object; storing, by the network orchestrator, service metadata as part of the transaction object; determining whether there is a service metadata conflict associated with the transaction object; and in response to determining that there is the service metadata conflict associated with the transaction object, retrying the service transaction; or in response to determining that there is no service metadata conflict associated with the transaction object, applying the service metadata to one or more nodes of the set of data nodes.