Introduction

This Part defines management information, interfaces and protocols for the various entities making up a CDPD Service Provider Network. Provided that these specifications have been implemented, a CDPD Service Provider may purchase components from various suppliers and manage them using a common management framework. In addition, different service providers can exchange CDPD management information by following these specifications.

This Part assumes that the reader is familiar with CDPD in general, as presented in Part 100. Part 100 provides a comprehensive glossary of CDPD terms. References to non-CDPD documents, shown in square brackets (e.g., [CCITT-X.701]), are listed in Part 100, which provides a complete CDPD bibliography.

Developers of CDPD systems, equipment and software shall follow these specifications for management functions. Each CDPD Service Provider may determine which, if any, of these specifications shall be required in their procurement of CDPD equipment.

A CDPD Service Provider Network is managed using X.700 and, optionally, Simple Network Management Protocol (SNMPv2). The X.700 management protocols and functions are specified by the Network Management Forum (NM Forum) set of OMNIPoint 1 documents.¹ These include the Common Management Information Protocol (CMIP) [CCITT-X.711], Common Management Information Service (CMIS) [CCITT-X.710], and the Technique of Modelling Management Information as Managed Objects [CCITT-X.701], [CCITT-X.720].

SNMPv2 may be used to manage Mobile End Systems (M-ESs). SNMPv2 is defined in a series of Internet RFCs [RFC-1441], [RFC-1442], [RFC-1443], [RFC-1444] [RFC-1445], [RFC-1446], [RFC-1447], [RFC-1448], [RFC-1449], [RFC-1450], [RFC-1451] and [RFC-1452]. An SNMPv2 M-ES Management Information Base (MIB) is defined in Part 752.

Wherever possible, the CDPD System Specification uses existing, standard managed objects defined by the International Organization for Standardization (ISO) [CCITT-X.721], International Telegraph and Telephone Consultative Committee (CCITT) [CCITT-M.3100] and industry groups such as the NM Forum [NMF-006] and the Open Systems Environment Implementors' Workshop (OIW) [OIW-1]. Refinements of standard objects, specific to CDPD, are used where appropriate; these objects are defined in the CDPD Library (Part 750). These objects are intended to be implemented directly although they may be refined further by subclassing to meet specific CDPD Service Provider requirements.

A Managed Object Ensemble defines how a collection of managed objects may be used to satisfy management requirements in a particular management context [NMF-025]. The following ensembles are defined for managing one or more CDPD systems:

• CDPD MD-IS and MDBS Management Ensemble (Part 731)

• CDPD Inter-Domain Management Ensemble (Part 732)

• CDPD Accounting Management Ensemble (Part 733)

• Generic Equipment Management Ensemble (Part 734).

The following ensembles have been defined by the NM Forum for OMNIPoint 1. These ensembles may be used to manage local and interexchange physical layer data circuits (e.g., T1s or DS0s):

• Reconfigurable Circuit Service: Configuration Management [NMF-017]

• Reconfigurable Circuit Service: Alarm Surveillance [NMF-018].

1. See [OMNIPoint-1] for a complete list of the OMNIPoint 1 documents.