Browse Prior Art Database

COMMUNICATION BETWEEN AUTOMATION EQUIPMENT AND EXTERNAL DEVICES OR CLIENTS

IP.com Disclosure Number: IPCOM000198939D
Publication Date: 2010-Aug-18
Document File: 4 page(s) / 102K

Publishing Venue

The IP.com Prior Art Database

Abstract

REST based application architecture for automation equipments using HTTP or other protocols for distributed communication.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

COMMUNICATION BETWEEN AUTOMATION EQUIPMENT AND EXTERNAL DEVICES OR CLIENTS

Suresh Kumar, Srijit Kumar, Kjell I Svensson

Abstract

REST based application architecture for automation equipments using HTTP or other protocols for distributed communication.

Background

Communication between automation equipment and external devices or clients has been based on RPC based protocols like COM, DCOM or Web services based on SOAP and WSDL.

Purpose

This invention solves the following problem

·         Platform independence and interoperability.

·         This invention does not force the vendor to provide client software.

·         Independent evolution of server without affecting the client through server driven work flow.

·         Provides access to web based clients.

·         Provides backward and forward compatibility between automation equipment and client applications.

·         Uniform interface to the client.

·         Versioning

Description

This invention involves exposing the services of automation equipment to an external device or client through a uniform interface using HTTP as an application protocol and resource oriented architecture based on RESTful framework. A resource is a distributed component that is identifiable by a unique name (URI). A resource may have one or more representations. A representation is the data (state) about the resource in a particular format and language (media type). The uniform interface corresponds to a set of generic operations that can be applied to a resource. In the context of HTTP, the uniform interface corresponds to URI, HTTP methods and media type description.

HTTP is a synchronous request/response application protocol. In HTTP, a client always initiates a request and the server responds to the request; the server never initiates a request to the client. This communication pattern limits HTTP applications to synchronous “pull” only interaction pattern. Emulation of asynchronous communication over a synchronous communication channel is achieved through polling, long poll, streaming, HTML5 web sockets or Web Hooks.

Figure 1 HTTP and REST based Application Architecture for an Automation Equipment

Figure 1 provides an overview of a generic HTTP based solution architecture. HTTP defines a standard set of methods to perform common operations such as:

·         GET for retrieving a representation of a resource

·         PUT or POST to create a new resource

·         PUT for modifying an existing resource

·         DELETE for deleting an existing resource.

Apart from the above methods, there are two other utility methods

·         HEAD for retrieving the metadata of the representation

·         OPTIONS to check which HTTP methods a particular resource supports.

...