XML Event Interface for OPC Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing OPC Data Access interfaces are limited to the Microsoft COM/DCOM framework, making it difficult for automation applications written in languages like Java to directly access and interact with industry devices, complicating data exchange and limiting interoperability.

Innovation Solution

An XML-based event-driven interface for OPC Data Access that allows service-oriented event-driven applications to communicate with industry devices using XML events, which are translated into COM/DCOM API calls, enabling remote interaction and data exchange through standard channels like sockets and Web services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If OPC Data Access interface is restricted to Microsoft COM/DCOM framework, then interoperability within Windows environment is achieved, but accessibility for applications in other languages (e.g., Java) is limited

Engineering Contradiction:
Improvelanguage compatibilityVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary translation layer that converts XML-based event-driven interface calls into COM/DCOM API calls. This mediator enables Java and other non-Windows applications to access OPC Data Access interfaces without directly implementing COM/DCOM, thus improving language compatibility while maintaining the existing COM/DCOM framework integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If custom interface or driver is written for each application needing device access, then direct device access is achieved, but development time and complexity increase

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoiddevelopment time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent creates a universal XML-based event-driven interface that can be used by applications in any programming language to access OPC Data Access interfaces. This single standardized interface replaces the need for multiple custom drivers, significantly reducing development time and improving ease of manufacture while maintaining broad compatibility.

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

3Productivity

If manual process is used for data exchange between enterprise software and industry devices, then data exchange is achieved, but automation and efficiency are reduced

Engineering Contradiction:
Improvedata exchange efficiencyVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The patent implements an automated event-driven architecture where the system automatically translates XML events into COM/DCOM API calls and manages data exchange between enterprise software and industry devices without manual intervention. This self-service mechanism significantly improves productivity and automation level compared to manual data exchange processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8196155B2XML-based event driven interface for OPC data access
Publication Date: 2012.06.05 ORACLE INT CORP
  • US8196155B2 patent drawing
  • US8196155B2 patent drawing
  • US8196155B2 patent drawing

AI summary

Communication from applications may be carried in XML-based events through sockets, Web services, JMS, HTTP, telnet channels, and the like to an OPC client. The OPC client may include an event engine configured to process the XML-based events, and convert them to appropriate COM/DCOM API invocations. In some embodiments, the OPC client buffers collected data from the COM/DCOM API, and transmits the buffered data in an XML event to an application based on a subscription time schedule and/or value condition. The OPC client allows service oriented event-driven applications to interact with industry devices remotely via the open architecture provided by the OPC specification using a business level language syntax.