scope:

The scope of this standard is limited to Operations System to Operations System interfaces for OSs used for network management and located in different jurisdictions. This standard is one of a series of standards that will specify this interface. This document describes extensions to the Generic network information model needed for OS-OS Network Management interfaces across jurisdiction boundaries. The same functional interface is specified using the Common Ojbect Request Broker Architecture (CORBA) / Interface Definition Language (IDL), as defined in The Common Ojbect Request Broker Architecture and Specification, Revision 2.2, Object Management Group, February 1998 (see Annex I).

The term, generic, is used here to imply that the managed object classes and their properties described are applicable across different network management technologies (between any managing system and any gateway system). Others in the series provide protocols, functions, and messages. OS-OS interfaces within jurisdictions are not specifically included. However, this standard can be used for that purpose at the discretion of the jurisdiction. The scope is limited to OS-OS interfaces based on the OSI Reference Model defined in ITU-T Recommendation X.200.

This standard contains an initial set of managed objects and attribute classes defined to support a subset of the Fault Management functional area, Trouble Administration. The applicability of this standard for other purposes has not been fully studied; it is not, however, precluded. Subsequent issues of this standard will augment the list of managed object classes and attribute types in order to more fully accommodate other management functional areas.

The CNM Service object class described in clause 7 of this standard is an extension of the Service object class in the original Generic Network Information Model (GNIM) described in T1.240.¹⁾ This standard is intended to play the same role for Customer Network Management as the original GNIM does for OS to NE Operations, Administration, Maintenance and Provisioning (OAM&P). It imports objects from the original GNIM as they are needed here.

It is the intention of this standard to use and align with Open Systems Interconnection (OSI) Systems Management Standards, where appropriate.

Purpose

In the open communications environment existing in North America, there is a need for the exchange of network management information between OSs in various jurisdictions. Currently no domestic or international standard exists for the exchange of such information. The absence of such a standard has resulted in the proliferation of OS-OS interfaces and the need for agreements on the means of interconnection. This diversity leads to inefficiencies in providing such interconnection and delay in the introduction of new capabilities. The telecommunications industry stands to benefit from a clear standard to achieve interoperability between OSs across jurisdictions. Development of an OS-OS interface standard will permit service providers and vendors to focus on the provisioning of new capabilities rather than the means of providing connectivity. The purpose of this standard is to provide extensions to the original Generic network information model for use with this series of standards for OAM&P interfaces between OSs across jurisdictions.

¹⁾ For complete titles of the standards referenced in clause 1, see clause 2, Normative references.