BEAM Platform Event-Driven Edge Computing Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software architecture patterns and communication protocols lack abstraction layers capable of supporting semantic interoperability requirements for the Internet of Things, Edge Computing, and Unified Commerce, leading to fragmented systems with complex and costly integrations.

Innovation Solution

A BEAM platform with a digital message format, communicator, event processor, runtime dataset, and query processor facilitates unified management, automation, and interoperability by creating, updating, and deleting digital representations of objects, and transporting semantically interoperable events, queries, and view datasets among devices, enabling real-time event-driven process orchestration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional software architecture patterns and communication protocols are used, then device communications can be established, but semantic interoperability and unified management across devices are achieved

Engineering Contradiction:
Improvesemantic interoperabilityVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an event-driven architecture with standardized event schemas and abstraction layers that act as intermediaries between diverse devices and systems. These intermediaries enable semantic interoperability by translating device-specific communications into unified event formats, allowing devices to interact without direct complex integrations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a universal event-driven platform that handles multiple device types, communication protocols, and business processes through a single standardized framework. This multi-functional approach allows the system to manage diverse devices and data formats uniformly, reducing integration complexity while maintaining adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If device-specific communication protocols are used, then device functionality is optimized, but integration cost and complexity increase

Engineering Contradiction:
Improvedevice operation efficiencyVSAvoidintegration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the communication architecture into distinct layers: device-specific protocol handlers at the edge and a standardized event-driven core. This segmentation allows device optimization to be isolated from integration complexity, enabling efficient device operation while maintaining unified management through the standardized event layer.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If fragmented systems are used, then device independence is maintained, but interoperability and data exchange efficiency decrease

Engineering Contradiction:
Improvedevice independenceVSAvoiddata exchange efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent creates standardized event copies and abstractions of device-specific data and communications. By copying device data into unified event schemas, the system maintains device independence while enabling efficient interoperability through standardized data representations that can be processed uniformly across the platform.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12061582B2No-code, event-driven edge computing platform
Publication Date: 2024.08.13 MIGLIORI DOUGLAS T
  • US12061582B2 patent drawing
  • US12061582B2 patent drawing
  • US12061582B2 patent drawing

AI summary

Unified management, automation, interoperability, and synchronization of virtual and physical device systems utilizing components of a no-code, event-driven edge computing platform on any device and/or across difference devices. In an embodiment, a system on a device accesses a first events dataset which represents a two-dimensional structure. Each row in the events dataset is processed by the system to create or update the state of a runtime dataset which represents a two-dimensional structure. The state of the runtime dataset comprises an instance of an event-defined system including event-defined processes. In an embodiment, the event-defined processes are executed by the system to process a second events dataset, wherein the execution of the event-defined processes further updates the state of the runtime dataset and may create one or more new events for processing.