Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Universal Protocol Conversion

IP.com Disclosure Number: IPCOM000117056D
Original Publication Date: 1995-Dec-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 89K

Publishing Venue

IBM

Related People

Dunn, JM: AUTHOR [+2]

Abstract

Disclosed is a method for the transparent attachment of a host application to communication circuits using proprietary protocols.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Universal Protocol Conversion

      Disclosed is a method for the transparent attachment of a host
application to communication circuits using proprietary protocols.

      Conventional wireless networks are supported by public and
private communication service providers.  While the public carriers
have adopted open standards, based on telecommunications access
methods and protocols, to attach customer hosts to the network, the
private carriers have created proprietary protocols using standard
circuit connections from a user host to the carrier gateway.  The
software must adapt to such a proprietary protocol.

      This type of requirement has conventionally been met by
providing a unique device driver for each unique protocol, such as a
printer, plotter, or special modem, to be installed by the
application.  However, this approach is not practical in the wireless
communication environment because the various carriers have not
agreed to a single, uniform Application Program Interface (API).
Thus, device drivers cannot be configured to mate with applications
using a common API.  Furthermore, the wireless carriers are unwilling
to provide proprietary interfaces to application providers for
shipment with the application, since the end-user of the service, not
the application provider, is the licensee.  Even if this conventional
solution could be implemented, the differences between protocols
would prevent a single application from concurrently using two or
more carriers, such as a truck fleet using a single dispatch
operation
to communicate with radios operating with different carriers.

      The Figure is a block diagram of the method disclosed herein,
which uses a table-driven protocol conversion program to provide a
common API to all applications.  This program creates a structure
including a send queue 1 and a receive queue 2, along with a protocol
message table 3 and an Automatic Send/Receive (ASR) map 4 for each of
the carriers to be used.  The process engine 5, not having been
provided by the licencessee of the pr...