Dynamic Metamodel Orchestration for Context-Aware Network Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software development practices are inflexible and brittle, struggling to adapt to dynamic, distributed, and complex environments, leading to suboptimal coordination and responsiveness in distributed organizations, which limits the exploitation of contextually relevant resources and hinders the ability to respond to external events effectively.

Innovation Solution

A system and method for declaratively modeling complex domains using a unified language, enabling the interpretation and execution of contextually motivated network services through normalized lifecycle management operations, which are dynamically composed and managed across micro-capabilities, resources, and network entities, facilitating flexible and responsive interactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static, linear processes and orchestration are used, then implementation simplicity is maintained, but adaptability and responsiveness to external events deteriorate

Engineering Contradiction:
ImproveadaptabilityVSAvoidprocess complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic process orchestration where workflows can be modified at runtime based on external events and contextual conditions. The system transitions from static, pre-defined linear processes to dynamic, adaptive processes that can reconfigure themselves in response to changing requirements, thereby resolving the contradiction between adaptability and complexity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments processes into modular, independently manageable units that can be composed and reconfigured dynamically. This segmentation allows the system to maintain simplicity at the component level while achieving adaptability through flexible composition of segments, addressing the contradiction between process complexity and adaptability.

Inventive Principle:
Principle #1Segmentation

2Productivity

If rigid flow patterns are used, then process control is simplified, but responsiveness to external events deteriorates

Engineering Contradiction:
ImproveresponsivenessVSAvoidorchestration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system employs dynamic flow patterns that can adapt their execution path based on external events and contextual information. This dynamic orchestration enables the system to respond rapidly to external stimuli while maintaining manageable complexity through standardized adaptation mechanisms.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent incorporates feedback mechanisms that allow the orchestration system to monitor external events and adjust process flow in real-time. This feedback-driven approach enhances responsiveness to external events while keeping orchestration complexity manageable through automated decision-making based on predefined feedback rules.

Inventive Principle:
Principle #23Feedback

3Productivity

If pre-established context optimization is used, then process efficiency is improved, but exploitation of contextually relevant resources deteriorates

Engineering Contradiction:
Improveprocess efficiencyVSAvoidresource exploitation
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic context adaptation where processes are optimized for the actual runtime context rather than pre-established contexts. This allows the system to maintain high efficiency by adapting to the specific context at execution time while simultaneously exploiting the full range of contextually relevant resources that become available dynamically.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11743144B2Systems and methods for domain-driven design and execution of metamodels
Publication Date: 2023.08.29 ENTERPRISEWEB LLC
  • US11743144B2 patent drawing
  • US11743144B2 patent drawing
  • US11743144B2 patent drawing

AI summary

An order is received indicating a network service model. A context of the order is identified. A deployment plan is generated using the network service model, the deployment plan facilitating an instantiation of a contextually-motivated network service instance as a set of normalized lifecycle management (LCM) operations performed against each of a plurality of associated service entities. The deployment plan is deployed, the deploying including binding each of the normalized LCM operations, based on the context of the order, to one or more respective micro-capabilities, each of the respective micro-capabilities having previously been onboarded to the system as one or more corresponding modeled objects capable of being declaratively composed, each of the corresponding modeled objects including a mapping of object properties, object behaviors, and standard LCM operations to one or more existing micro-capabilities of the system. The deploying also including managing execution of the one or more respective micro-capabilities and associated resources, associated storage, and associated network and service allocation and configuration, to instantiate the contextually-motivated network service instance.