Service Instance Data Structure for Cross-Domain E2E Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current lifecycle management of cross-domain end-to-end services lacks a unified, service instance-specific configuration/setup data management, particularly for service assurance, as parameters are distributed and stored per functional block, leading to inefficiencies in service management.
Innovation Solution
A computer-implemented data structure for a service instance object is introduced, comprising sections for general, E2E, and management domain-specific data, enabling centralized storage and management of service instance data across different domains, including E2E service process flow data and management domain data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If service specific parameters are distributed and stored per functional block, then each functional block can independently manage its parameters, but the service instance specific configuration data becomes difficult to access and manage centrally
Solution Approach 1:
The patent merges scattered service instance specific configuration data from multiple functional blocks into a unified data structure called ServiceInstanceObject. This object consolidates parameters related to service assurance, quality of service, and other service-specific configurations into a single accessible entity, enabling centralized management while reducing data access complexity across the service lifecycle
Solution Approach 2:
The ServiceInstanceObject is designed as a universal data structure that serves multiple functional blocks simultaneously. It provides a common interface for service assurance management, quality of service configuration, and other service-specific operations, eliminating the need for separate data structures in each functional block and enabling consistent access patterns across different system components
2Loss of information
If a unified service instance object is created to store all service specific data, then centralized management is achieved, but the data structure becomes more complex
Solution Approach 1:
The ServiceInstanceObject is segmented into distinct fields organized by functional category (service assurance parameters, quality of service parameters, service level agreement parameters, etc.). This segmentation allows the unified structure to maintain logical organization and ease of access, reducing the perceived complexity while ensuring all service instance specific data is captured and accessible to relevant functional blocks
Data Source
AI summary
A computer-implemented data structure for a service instance object and related methods and network node devices are disclosed. The computer-implemented data structure for a service instance object of a network and service management system comprises a first data section configured to store general service instance data, a second data section configured to store end-to-end (E2E) service data, a third data section configured to store E2E service process flow specific data, and a fourth data section configured to store management domain specific data.