Browse Prior Art Database

Standardized Architected Datastream Transposer

IP.com Disclosure Number: IPCOM000108446D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 76K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+3]

Abstract

A methodology is described for transposing Abstract Syntax Notation/1 (ASN.1) encoding to/from a Generalized Data Stream (GDS) encoding. This allows data stream conversion between systems which would otherwise not be able to communicate. The present invention allows successful communication between ASN.1 entities and GDS entities. The syntactical conversion between formats is the first important step. Semantic mapping is achieved by understanding the specific systems.

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

Standardized Architected Datastream Transposer

       A methodology is described for transposing Abstract
Syntax Notation/1 (ASN.1) encoding to/from a Generalized Data Stream
(GDS) encoding.  This allows data stream conversion between systems
which would otherwise not be able to communicate.  The present
invention allows successful communication between ASN.1 entities and
GDS entities.  The syntactical conversion between formats is the
first important step.  Semantic mapping is achieved by understanding
the specific systems.

      Many Open System Interconnect (OSI) applications represent
their application objects, protocols and datastreams through Abstract
Syntax Notation/1.  Many System Network Architecture applications
represent their objects, protocols and datastreams through a General
Datastream Notation (GDS notation).  Many existing protocol parsers
and builders are designed for the GDS formats.  An enterprise may
wish to utilize their existing GDS parser and builder to manipulate
ASN.1 encoding, especially when converting between different media or
protocols.  This would allow existing systems to recognize ASN.1
protocols and objects without creating an ASN.1 encoder/decoder.
This would also permit existing GDS systems to be utilized as
transport and relay mechanisms for ASN.1 protocols.  A mechanism is
needed to permit ASN.1 encoding to be represented within a GDS.

      This article describes a mechanism for transposing ASN.1
objects into GDS constructs.  In particular, a method for transposing
GDS, Document Interchange Architecture Structures to and from an
ASN.1 format.  A GDS encoding is constructed by what is often
described as an LLIDF (Length-Length-Identifier-Form...