Browse Prior Art Database

Routing Unsolicited Messages within a System Utilizing the OSI Management Model

IP.com Disclosure Number: IPCOM000112082D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 75K

Publishing Venue

IBM

Related People

Allen, WC: AUTHOR [+4]

Abstract

A method is disclosed that allows routing of unsolicited management messages (event reports) to specific applications that reside on a single system.

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

Routing Unsolicited Messages within a System Utilizing the OSI Management
Model

      A method is disclosed that allows routing of unsolicited
management messages (event reports) to specific applications that
reside on a single system.

Various possible methods of routing Events to applications that
reside on a different system from the originator.

      The protocols defined to perform systems management by the OSI
standards include messages that are emitted under specific
conditions.  These are called event reports.  These messages do not
carry their destination.  Instead there is a function, the Event

Forwarding Discriminator, that receives all of these messages,
compares them to conditions for transmission, and forwards them to
one or more destinations.  The destination is defined to be an
AE-Title (Application Entity Title).  This allows the message to be
sent to the correct Application Entity.  This level of routing was
defined to satisfy the needs of the very simple system-structure
model shown in Fig. 1 (A Single AE on a system).  This is the mode 1
that is normally discussed in the standards.  Configurations in the
real world are often more complicated.  Each system is likely to have
several different applications running, each of which may be
interested in different types of messages.  Without modification to
the EFD function, routing event reports to the correct application on
a system would require the structure shown in Fig. 1 (Multiple AEs on
a system).  This requires that each application be its own AE, and
that parallel associations be established in order to send event
reports to each of the applicati...