Network Service Change Deployment via Configuration Schema Partitioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for deploying changes to network services in communications networks are inefficient, often requiring serial deployment and taking significant time, which can lead to delays and potential service disruptions, and lack the ability to prioritize or roll back changes quickly.
Innovation Solution
The solution involves partitioning the configuration schema into independent configuration group types, allowing for parallel deployment and management of changes using conditional convergence logic, enabling operators to prioritize and adjust the speed of deployment based on current state instances at each site.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If serial deployment method is used, then deployment control is simple, but deployment time is long and efficiency is low
Solution Approach 1:
The configuration schema is divided into multiple independent configuration group types (e.g., network function instances, network function connections, service level agreements). This segmentation allows parallel deployment of different configuration groups, significantly improving deployment efficiency while maintaining manageable complexity through structured organization.
Solution Approach 2:
The patent introduces a hierarchical dimension to deployment control with service orchestrators at different levels (e.g., global service orchestrator, regional service orchestrator) that can independently manage deployment of different configuration groups. This dimensional approach enables parallel processing at multiple levels while providing centralized control where needed.
2Speed
If parallel deployment is implemented, then deployment speed increases, but conditional logic and state management become more complex
Solution Approach 1:
By segmenting the configuration schema into independent configuration group types, the patent enables parallel deployment while isolating convergence logic to specific groups. Each configuration group has its own convergence logic that operates independently, reducing the overall complexity of managing parallel deployments.
Solution Approach 2:
Service orchestrators act as intermediaries between the deployment system and network elements. They receive deployment instructions, evaluate convergence logic, and coordinate the actual deployment, simplifying the complexity of managing parallel deployments with conditional convergence requirements.
3Productivity
If configuration schema is partitioned into multiple group types, then parallel deployment is enabled, but system configuration complexity increases
Solution Approach 1:
The configuration schema is segmented into distinct configuration group types, each representing a specific aspect of network service configuration. This segmentation enables parallel processing of independent configuration groups, improving deployment throughput while maintaining clarity through structured categorization.
Solution Approach 2:
The patent creates a universal configuration framework where service orchestrators can manage multiple configuration group types using the same fundamental mechanisms (receive definition, evaluate convergence logic, send instructions). This multi-functionality reduces the practical complexity of managing the partitioned schema by reusing established patterns.
4Adaptability or versatility
If conditional convergence logic is added, then deployment flexibility and prioritization improve, but deployment time for state evaluation increases
Solution Approach 1:
Convergence logic is defined and prepared in advance as part of the configuration schema, along with the logic for evaluating current state instances. This preliminary preparation allows rapid evaluation during deployment without requiring complex real-time analysis, reducing state evaluation time while maintaining flexibility.
Solution Approach 2:
The system incorporates feedback mechanisms where service orchestrators evaluate the current state of configuration groups and adjust deployment accordingly. This feedback loop enables flexible, conditional deployment while optimizing evaluation time by using cached state information and incremental updates rather than full re-evaluation.
Data Source
AI summary
A service orchestrator receives a definition of a change to a network service to be deployed over a plurality of sites of a communications network. The definition comprises a configuration schema with a plurality of fields, which are partitioned into a plurality of different configuration group types. The service orchestrator receives an instance of the configuration group type. The service orchestrator receives conditional convergence logic specifying the received instance each site is to use conditional on a current state instance of the configuration group type used at the site. The service orchestrator sends instructions to each of the sites based on the conditional convergence logic, the instructions comprising the received instance. The instructions are configured to trigger a site convergence agent at each site to deploy the change to the network service according to the received instance of the configuration group type and the conditional convergence logic.