Browse Prior Art Database

Automatic Generation of ANY DEFINED BY Resolution from GDMO Definitions

IP.com Disclosure Number: IPCOM000112506D
Original Publication Date: 1994-May-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 4 page(s) / 161K

Publishing Venue

IBM

Related People

Allen, WC: AUTHOR [+3]

Abstract

A method is disclosed that allows resolution of the ASN.1 ANY DEFINED BY construct via use of the GDMO templates referenced by the ANY DEFINED BY.

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

Automatic Generation of ANY DEFINED BY Resolution from GDMO Definitions

      A method is disclosed that allows resolution of the ASN.1 ANY
DEFINED BY construct via use of the GDMO templates referenced by the
ANY DEFINED BY.

      Network management architecture is specified using both GDMO
(for the definition of managed objects) and ASN.1 (for the definition
of the necessary syntaxes).  The CMIP Services component is designed
to process network management information based on the GDMO and ASN.1
specifications.   The ASN.1 language includes ANY DEFINED BY as one
of several alternative type specification mechanisms.  This mechanism
requires the ASN.1 processor to look in an unspecified external
location for the completion of the type definition.  While the text
of the architecture specification may say what the ANY DEFINED BY is
referring to, this cannot be specified in the ASN.1 notation.  In a
number of cases, the text specifies that the ANY DEFINED BY refers to
any GDMO template of a certain type.  The mechanism described below
is used to connect the information specified using GDMO with the
ASN.1 ANY DEFINED BY reference so that the automated ASN.1 processor
can resolve the reference and perform typechecking.

      The solution has two parts, the first part implemented by the
ASN.1 compiler, and the second part by the GDMO compiler.

      The ASN.1 ANY DEFINED BY type specification mechanism has the
following syntax in ASN.1:

ANY DEFINED BY <identifier>

This mechanism may only be used when it is contained within a set or
sequence type.  The <identifier> is replaced with the label of
another component of the containing set or sequence.

      The first part of the solution was to add a significant comment
mechanism to the input language accepted by the ASN.1 compiler.  In
ASN.1, comments being with a pair of adjacent hyphens and continue to
the end of the line or until the next pair of adjacent hyphens
(whichever comes first).  Comments may appear between any two ASN.1
items.  A significant comment, as recognized by IBM's ASN.1 compiler,
is a special form of a regular comment.  Any comment with the
character '%' immediately following the initial pair of hyphens (as
--%") is a significant comment and is given special processing by the
compiler.  The --%" is only one alternative for significant comments,
characters other than the '%' could easily be chosen instead.  It
would also be possible for the compiler to define another syntax as
long as the significant comment can be distinguished from the normal
ASN.1 syntax.  The significant comments for resolving ANY DEFINED BY
references refer to tables used in resolving the ANY DEFINED BY
references and serve to associate a particular use of the ANY DEFINED
BY mechanism with a particular table to be used in processing the
type.  A significant comment must be added to the ASN.1 at each use
of the ANY DEFINED BY type specifier.  The comment must be placed
imm...