Web Service Tag Mapping for XML and JSON Control Data

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional industrial control systems are unable to directly consume data in XML or JSON formats from web services, requiring developers to write complex algorithms to extract and transform data into tag-based structures, which is inefficient and requires new scripts for each format change.

Innovation Solution

An operations integration processor and engine that parses web service responses into attribute-value pairs and maps them to tags, allowing direct integration with tag-based control and data acquisition systems, eliminating the need for manual script writing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers write complex algorithms to extract and transform web service data into tag-based structures, then data can be consumed by industrial control systems, but the system complexity and development time increase significantly

Engineering Contradiction:

Improvedata consumption capabilityVSAvoidalgorithm complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary component that translates web service data formats (XML, JSON) into tag-based structures that industrial control systems can consume. This intermediary layer handles the complex transformation logic, allowing the control system itself to remain simple while still achieving adaptability to various data sources.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal data integration mechanism that can handle multiple web service data formats (XML, JSON, and other structured formats) through a single standardized interface. This multi-functional approach eliminates the need for separate complex algorithms for each data format, reducing overall system complexity while maintaining versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If manual script writing is required for each data format change, then data extraction can be customized, but the time and resources required for maintenance increase

Engineering Contradiction:

Improvedata format compatibilityVSAvoidscript development time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a universal data integration platform that supports multiple web service data formats (XML, JSON, and other structured formats) through a single standardized interface. This multi-functional approach eliminates the need for separate complex algorithms for each data format, reducing overall system complexity while maintaining versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent utilizes parameter changes in data structures and formats to enable flexible adaptation to different web service responses. By defining configurable parameters and schemas, the system can automatically adjust to format changes without requiring manual script rewriting, thus reducing maintenance time and resources.

Inventive Principle:

Principle #35Parameter changes

3Loss of information

If data is processed in raw XML or JSON format directly, then data availability increases, but conventional control systems cannot consume the data without transformation

Engineering Contradiction:

Improvedata availabilityVSAvoiddata consumption ease

Core Design Contradiction:

Loss of informationVSEase of operation

Solution Approach 1:

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data processing function into distinct layers: data acquisition from web services, format transformation through parsing and extraction, and consumption by the control system. This segmentation allows each layer to be optimized independently, maintaining data availability while ensuring ease of operation for the control system.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11782946B2Automatic tag mapping and generation from data string

Publication Date: 2023.10.10 AVEVA SOFTWARE LLC

AI summary

An operations integration processor mapping information in a language-independent data format to a tag format for integration with a tag-based control and data acquisition system. The operations integration processor receives a response from a web service and parses the response to identify one or more attribute-value pairs contained in the response. The response contains information in a language-independent data format different than a tag format. The processor maps the parsed response to one or more tags, which have at least one of a name and a value based on the information provided in the response associated with them.