Application-Aware Modbus Gateway Data Grouping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing Modbus data model lacks the ability to group data and manage storage at a level required by individual applications to effectively manage field devices, especially in configurations with multiple Modbus slave devices.

Innovation Solution

An application-aware gateway device operating under the Modbus protocol is introduced, which sends process data from industrial equipment to a gateway device, creates data maps in memory based on application contexts, and assigns unit IDs to these maps, allowing client devices to subscribe and receive grouped process data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a flat data table structure is used in Modbus protocol to store field device data, then the data storage is simple and follows the standard protocol format, but the ability to group and organize data according to application contexts is lost, making it difficult to manage data from multiple slave devices effectively

Engineering Contradiction:
Improvedata organization flexibilityVSAvoiddata management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the flat data table into multiple hierarchical levels: application contexts, data maps, data groups, and individual data items. This segmentation allows data to be organized according to application-specific needs while maintaining the underlying Modbus protocol structure. Each level provides a different dimension of organization, enabling flexible data access patterns without requiring complete reorganization of the base data structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds dimensional organization to the traditional flat Modbus data structure by introducing application contexts as a new dimension. Instead of only organizing data by device registers (one dimension), the system now organizes data by application context (second dimension), data map (third dimension), and data group (fourth dimension). This multi-dimensional organization enables the same data to be accessed and grouped differently for different applications.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Loss of information

If data from multiple Modbus slave devices is consolidated into a single flat table, then all data is accessible, but the data becomes difficult to organize and associate with meaning or context for specific applications

Engineering Contradiction:
Improvedata context preservationVSAvoiddata structure complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the consolidated data into application-specific contexts, creating separate data maps for different applications. Each data map contains only the data relevant to that application, preserving the contextual meaning and relationships. This segmentation prevents data from different applications from mixing together and losing their specific contexts, while still allowing access to all underlying data through the hierarchical structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by allowing different application contexts to have different data organization structures, grouping criteria, and access patterns. Each application context can be customized to reflect the specific needs and requirements of that application, rather than forcing all applications to use a single uniform data structure. This enables each application to maintain its data with the appropriate level of detail and organization.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If the Modbus protocol maintains a standard flat message structure, then compatibility with existing devices is ensured, but the protocol cannot support application-specific data grouping and prioritization requirements

Engineering Contradiction:
Improveapplication-specific data managementVSAvoidprotocol compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary layer (the application context data model) between the standard Modbus protocol and the application layer. This intermediary maintains compatibility with the standard Modbus flat message structure while providing additional organization and context at the application level. The system translates between the standard protocol format and the application-specific data groups, ensuring that existing Modbus devices continue to work while enabling advanced data management capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the protocol functionality into two parts: the transport layer continues to use the standard Modbus flat message structure for compatibility, while the application layer introduces a new hierarchical data model for application-specific organization. This segmentation allows both standard protocol compatibility and advanced data management to coexist without interfering with each other.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250119319A1Application aware modbus gateway
Publication Date: 2025.04.10 HONEYWELL INTERNATIONAL INC
  • US20250119319A1 patent drawing
  • US20250119319A1 patent drawing
  • US20250119319A1 patent drawing

AI summary

A Modbus gateway includes a processor, an application memory, and a data acquisition module for receiving field data from an industrial process run in a plant including processing equipment having associated field devices. The data acquisition module is coupled to provide the field data to a data broker having at least one memory that stores the field data according to data registers associated with the field devices. The data broker is coupled to the application memory containing at least one data map organized according to an application context requested by a subscribed client device for an application executing at the client device. The data broker is coupled to associate the data registers into a grouping of field data according to the data map, wherein the processor causes the grouping of field data to be sent to the client device subscribed to the data map.