Agent Transfer via Canonical Rule Encoding

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing rule-based systems face challenges in efficiently moving agents with canonical rule sets between execution environments, particularly due to memory consumption issues and the need for dynamic adaptation to varying computational and networking capacities.

Innovation Solution

A method and system for encoding and decoding agents with canonical rule sets, allowing them to be transferred between execution environments while discarding unnecessary components like rule engines and working memories, and compiling the rule sets in the new environment to create a new rule engine and working memory.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the agent carries its rule engine, working memory, and compiled rule set when moving between execution environments, then the agent can execute immediately in the new environment, but the memory consumption and transfer size increase significantly

Engineering Contradiction:

Improveagent execution readinessVSAvoidmemory consumption

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential canonical rule set from the agent and separates it from the rule engine and working memory. The rule engine and working memory are discarded in the source environment and recreated in the target environment, transferring only the minimal necessary rule definitions rather than the entire execution framework.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the state of the rule set from being compiled and bound to a specific rule engine in the source environment to being uncompiled and portable canonical rules in the target environment. This parameter change enables the rule set to be transferred efficiently without carrying the entire rule engine infrastructure.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If the agent transfers its complete rule-based system including rule engine and working memory to a new execution environment, then the agent maintains full functionality, but the transfer time and network bandwidth consumption increase

Engineering Contradiction:

Improveagent functionalityVSAvoidtransfer time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the canonical rule set definitions from the complete rule-based system, separating the essential logic from the execution infrastructure. This extraction reduces the transfer payload to minimal rule definitions while maintaining the ability to recreate full functionality in the target environment.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary compilation of the rule set in the source environment and prepares it for transfer as portable canonical rules. The rule engine and working memory are discarded before transfer, and the system is pre-configured to automatically recreate these components in the target environment, reducing transfer time.

Inventive Principle:

Principle #10Preliminary action

3Quantity of substance

If the agent discards its rule engine and working memory when moving to a new execution environment, then memory usage is reduced, but the agent must recreate these components in the new environment

Engineering Contradiction:

Improvememory usageVSAvoidrecreation process

Core Design Contradiction:

Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling the agent to automatically recreate its rule engine and working memory in the target environment using the transferred canonical rule set. The system performs the recreation process autonomously without requiring external intervention, reducing memory usage while managing the complexity of component recreation.

Inventive Principle:

Principle #25Self-service

4Speed

If the agent uses procedural programming with static logic compiled into agent software, then the agent execution is efficient, but the agent cannot adapt to changing conditions or environments

Engineering Contradiction:

Improveagent execution speedVSAvoidenvironmental adaptation

Core Design Contradiction:

SpeedVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamics by making the rule set portable and reconfigurable across different execution environments. Instead of static procedural logic compiled for a specific environment, the agent uses canonical rules that can be transferred and adapted to new environments, enabling dynamic response to changing conditions while maintaining efficient execution through rule-based processing.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS7702602B1Moving an agent with a canonical rule from one device to a second device

Publication Date: 2010.04.20 CALLAHAN CELLULAR LLC

AI summary

A method for moving an agent with a canonical rule set from a first execution environment to a second execution environment, comprising encoding the agent including the canonical rule set into transferable form in the first execution environment, sending the encoded agent to the second execution environment, and decoding the agent including the canonical rule set at the second execution environment.