Network Service Traceability for Automated Redesign After Model Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network function virtualization (NFV) systems lack effective end-to-end traceability support, making it difficult to assess the impact of changes in virtual network function descriptors (VNFDs) on network service design and deployment, and to automatically redesign and redeploy services when requirements are not met.
Innovation Solution
The MAPLE-T approach integrates traceability support into the MAGIC Process Modelling and Enactment Environment (MAPLE) to generate both local and global traceability information during process enactment, using megamodels to link artifacts and enable change impact analysis, allowing for automatic redesign and redeployment of network services based on traceability analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traceability information is represented as extra-model models conforming to an external metamodel, then traceability semantics are preserved, but device complexity increases due to multiple models and metamodels
Solution Approach 1:
The patent embeds traceability information directly within the existing model structures by extending metamodels with traceability elements. Instead of creating separate extra-model traceability models, the traceability links and metadata are nested inside the target models themselves, allowing semantics to be preserved while reducing structural complexity.
Solution Approach 2:
The patent combines traceability information with the target model artifacts by integrating trace links as first-class citizens within the model structure. This merging eliminates the need for separate traceability models and their associated metamodels, reducing overall system complexity while maintaining semantic integrity.
2Measurement precision
If a pure metamodel approach is used for traceability metamodelling, then traceability semantics are precisely defined, but adaptability decreases making the metamodel rigid to change
Solution Approach 1:
The patent implements a dynamic metamodel structure that allows traceability elements to be added, removed, or modified based on specific project requirements. The metamodel is designed to be extensible, enabling adaptation to different domains and use cases while maintaining core traceability semantics through a standardized framework.
Solution Approach 2:
The patent creates a universal traceability metamodel that can serve multiple purposes across different projects and domains. The metamodel is designed to be multi-functional, supporting various traceability needs (requirements tracing, design tracing, verification tracing) through a single adaptable framework rather than requiring separate rigid metamodels for each case.
3Adaptability or versatility
If trace tagging approach is used with a general traceability metamodel, then adaptability increases for reuse in other projects, but measurement precision decreases with weak usage semantics
Solution Approach 1:
The patent applies local quality by allowing each project to annotate the general traceability metamodel with domain-specific tags and semantics tailored to their particular needs. While the underlying metamodel remains general and reusable, each instantiation can have customized trace link types, attributes, and validation rules that provide strong, precise semantics for that specific domain.
Solution Approach 2:
The patent performs preliminary action by providing a pre-configured general traceability metamodel framework that includes common traceability patterns and structures. This preliminary setup enables immediate reuse across projects while allowing subsequent customization to strengthen semantics for specific use cases, combining the benefits of reusability with domain-specific precision.
4Measurement precision
If manual traceability analysis is performed to assess change impact, then measurement precision is high, but productivity decreases due to time-consuming manual processes
Solution Approach 1:
The patent implements automated feedback mechanisms that continuously monitor traceability links and automatically assess change impact by analyzing the traceability model structure. When changes are detected in source models, the system automatically traces the impact through defined trace links and provides precise impact assessment feedback, eliminating the need for manual analysis while maintaining accuracy.
Solution Approach 2:
The patent enables the traceability system to perform self-service automated impact analysis by leveraging the structured traceability metadata embedded in the models. The system automatically queries the traceability information, computes impact relationships, and generates assessment results without human intervention, significantly improving productivity while maintaining measurement precision through the structured traceability framework.
Data Source
AI summary
The disclosure relates to a method, system and computer readable media for redesigning and redeploying a network service (NS) upon determining that a running instance of the NS fails to meet at least one NS requirement. The method comprises detecting a change in at least one input model of a NS design; executing a traceability analysis for the change in the at least one input model of the NS design; and upon determining, based on the traceability analysis, that the NS fails to meet the at least one NS requirement, redesigning and redeploying the NS.


