Dynamic Service Orchestration via Rules Engine

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing service orchestration systems, particularly those using Business Process Execution Language (BPEL), face challenges in quickly changing and managing dynamic rules and orchestration, especially in real-world applications with complex, dynamic observed rules, making it difficult to configure and manage these systems in a flexible and timely manner.

Innovation Solution

A dynamic command and control system that includes a service orchestration platform, a rules engine, and a command and control module, allowing for real-time modification of service orchestration and rules without altering the underlying services, using a user interface to input and configure these changes, and a database to store and manage event, rules, and asset data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static service orchestration using BPEL is used, then service composition is achieved, but flexibility to change rules and orchestration is poor

Engineering Contradiction:

Improveflexibility to change rules and orchestrationVSAvoidcomplexity of managing and changing orchestration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic service orchestration by separating the orchestration logic from the underlying services. The service orchestration platform allows rules and orchestration configurations to be modified in real-time without changing the actual service implementations. This is achieved through a configuration interface that enables dynamic updates to orchestration parameters, service bindings, and business rules while services continue to operate unchanged.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system segments the service orchestration into distinct components: the service orchestration platform, the underlying services, and the configuration interface. This segmentation allows independent modification of orchestration rules without affecting service code. The platform maintains a separation between static service definitions and dynamic orchestration parameters, enabling flexible reconfiguration through parameter changes rather than code modifications.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If service orchestration is applied to real-world applications with dynamic rules, then applicability increases, but difficulty to configure and manage increases

Engineering Contradiction:

Improveapplicability to real-world dynamic applicationsVSAvoidease to configure and manage

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The service orchestration platform acts as an intermediary layer between the underlying services and the configuration interface. This mediator enables dynamic rule changes and orchestration modifications through a user-friendly interface without requiring direct access to service code or complex configuration files. The platform translates high-level configuration parameters into executable orchestration logic, simplifying management of dynamic rules in real-world applications.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service configuration through an automated service orchestration platform that handles rule changes and orchestration updates without requiring developer intervention. The configuration interface allows operators to modify service bindings, update business rules, and reconfigure orchestration parameters directly through parameter changes, which the platform automatically processes and applies to the running services.

Inventive Principle:

Principle #25Self-service

3Productivity

If dynamic modification of orchestration is enabled, then real-time changes are possible, but time to implement changes may increase

Engineering Contradiction:

Improvespeed of implementing changesVSAvoidtime to configure and manage changes

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The service orchestration platform performs preliminary configuration and validation of orchestration parameters before applying changes to running services. The system pre-processes configuration inputs, validates parameter syntax and semantics, and prepares update packages in advance. This preliminary action ensures that when changes are deployed, they are applied immediately without requiring lengthy processing or manual intervention, thus reducing the time loss associated with dynamic reconfiguration.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS8719824B2Dynamically configurable command and control systems and methods

Publication Date: 2014.05.06 RAYTHEON CO

AI summary

A method and system in a Service Orchestration Architecture environment that provides rules engine-based service orchestration, task, and alert management for collaboration between one or more nodes of operation. The system provides multiple levels of configurability. In one aspect, the system includes a rules engine to define the command and control (C2) service orchestration.