ATIS 0300240-2014 Operations Administration Maintenance and Provisioning (OAM&P) - Generic Network Information Model for Interfaces Between Operations Systems and Network Elements.pdf

《ATIS 0300240-2014 Operations Administration Maintenance and Provisioning (OAM&P) - Generic Network Information Model for Interfaces Between Operations Systems and Network Elements.pdf》由会员分享，可在线阅读，更多相关《ATIS 0300240-2014 Operations Administration Maintenance and Provisioning (OAM&P) - Generic Network Information Model for Interfaces Between Operations Systems and Network Elements.pdf（47页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0300240.2014 OPERATIONS, ADMINISTRATION, MAINTENANCE, AND PROVISIONING (OAM their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, pro

2、cesses, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an Am

3、erican National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any

4、time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards

5、 Institute. Notice of Disclaimer b) Adopting the relevant definitions in ITU-T Recommendation M.3101, where appropriate; c) Adopting the relevant definitions from the set of System Management Function (SMF) documents, where appropriate; and e) Addressing in separate documents those aspects of the ve

6、rsion 1 model that relate to the PDH transmission hierarchy. It is the intention of this standard to continue to use and align with Open Systems Interconnection (OSI) man-agement standards, where appropriate. 1.2 Purpose Current telecommunications networks are populated by a large and increasing num

7、ber of OSs and NEs supplied by different vendors. Both the number and variety of networks and services have grown, creating a diversity of network management needs. This growth has resulted in the proliferation of unique communication interfaces between OSs and NEs. The telecommunications industry s

8、tands to benefit from standardization of these interfaces, designed to ATIS-0300240.2014 2 achieve interoperability between a broad range of OSs and NEs. The purpose of this document is to provide a generic network model for use with this series of standards for telecommunications OAM b) Administrat

9、ion; c) Configuration management; d) Fault management; e) Maintenance; f) Mediation device; g) Mediation function; h) OAM i) Operations; j) Performance management; k) Provisioning; l) Security management; and m) Telecommunications management network. This document makes use of the following term def

10、ined in ATIS-0300208: OAM the latter includes portions that may be assigned for exclusive use by specific customers. Resources may be physical or logical in nature. Physical resources include customer (e.g., PBXs) or provider (e.g., digital cross connect systems) systems, their associated subsystems

11、 (e.g., ATIS-0300240.2014 5 a line card within a PBX), and also the links that interconnect these systems. Such systems are generally known as Network Elements (NEs). Logical resources include communication protocols, application programs, logs, and network services. There may also exist (separate o

12、r integrated) Telecommunications Management Network (TMN) ATIS-0300210 resources involved in operating a telecommunications network. These resources include the OSs closely associ-ated with managing specific NEs and OSs that have network-wide responsibilities. Resources allow the user to control and

13、/or observe their behaviour. The information exchanged at the management interface is modelled using design principles outlined in ITU-T Recommendation X.720. Resources are modelled as objects, and the management view of a resource is called a managed object. Additional objects, called support manag

14、ed objects, are defined to support the functions of managing a telecommunications network. This generic network information model contains definitions for generic object classes that may be applicable across technologies and functional areas. 6 Object Classes CHARACTERIZED BY servicePackage PACKAGE

15、BEHAVIOUR serviceBehaviour BEHAVIOUR DEFINED AS “The service object class is a class of managed objects that represents offerings from a provider that supply specific network functionality to one or more customers. A Service may or may not be tariffed. Services may be nested, thereby creating a cont

16、ainment relationship. The Service Type identifies the distinguishing characteristics of the Service. The Supported Ser-vice Name List identifies other Services supported by the Service, and the Supported By Object List identifies the objects that support the Service” ; ATTRIBUTES serviceID GET, serv

17、iceType GET-REPLACE; NOTIFICATIONS “Rec. X.721:1992”:qualityofServiceAlarm; CONDITIONAL PACKAGES “Rec. M.3100:2005”:createDeleteNotificationsPackage PRESENT IF “the objectCreation and ob-jectDeletion notifications defined in Recommendation X.721 are supported by an instance of this class.”, “Rec. M.

18、3100:2005”:attributeValueChangeNotificationPackage PRESENT IF “the attributeValue-Change notifications defined in Recommendation X.721 is supported by an instance of this class.”, “Rec. M.3100:2005”:stateChangeNotificationPackage PRESENT IF “the stateChange notification defined in Recommendation X.7

19、21 is supported by an instance of this class.”, “Rec. M.3100:2005”:administrativeOperationalStatesPackage PRESENT IF “an instance supports it”, usageStatePackage PRESENT IF “an instance supports it”, alarmStatusPackage PRESENT IF “an instance supports it”, “Rec. M.3100:2005”:currentProblemListPackag

20、e PRESENT IF “an instance supports it”, supportedServiceNameListPackage PRESENT IF “an instance supports it”, supportedByObjectListPackage PRESENT IF “an instance supports it”; REGISTERED AS gnimObjectClass 1; ATIS-0300240.2014 9 6.2 Additional Packages 6.2.1 Supported by Object List supportedByObje

21、ctListPackage PACKAGE ATTRIBUTES “Rec. M.3100:2005”:supportedByObjectList GET-REPLACE ADD-REMOVE; REGISTERED AS gnimPackage 1; 6.2.2 Supported Service Name List supportedServiceNameListPackage PACKAGE ATTRIBUTES supportedServiceNameList GET-REPLACE ADD-REMOVE; REGISTERED AS gnimPackage 2; 6.2.3 Alar

22、m Status alarmStatusPackage PACKAGE ATTRIBUTES “Rec. M.3100:2005”:alarmStatus GET; REGISTERED AS gnimPackage 3; 6.2.4 Usage State usageStatePackage PACKAGE ATTRIBUTES “Rec. X.721:1992”:usageState GET; REGISTERED AS gnimPackage 4; All other conditional packages of the Service object are defined in IT

23、U-T Recommendation M.3100. 6.3 Additional Attributes 6.3.1 Service ID serviceID ATTRIBUTE WITH ATTRIBUTE SYNTAX GNIMASN1DefinedTypesModule.NameType; MATCHES FOR EQUALITY; BEHAVIOUR ATIS-0300240.2014 10 serviceIDBehaviour BEHAVIOUR DEFINED AS “The Service ID is an attribute type whose distinguished v

24、alue can be used as an RDN when naming an instance of the Management Operations Schedule object class”; REGISTERED AS gnimAttribute 1; 6.3.2 Service Type serviceType ATTRIBUTE WITH ATTRIBUTE SYNTAX GNIMASN1DefinedTypesModules.ServiceType; MATCHES FOR EQUALITY; BEHAVIOUR serviceTypeBehaviour BEHAVIOU

25、R DEFINED AS “The service Type attribute identifies the distinguishing characteristics of a Service”; REGISTERED AS gnimAttribute 2; 6.3.3 Supported by Object List (See ITU-T Recommendation M.3100 for the GDMO template for this attribute.) 6.3.4 Supported Service Name List supportedServiceNameList A

26、TTRIBUTE WITH ATTRIBUTE SYNTAX GNIMASN1DefinedTypesModules.ObjectList; MATCHES FOR EQUALITY; BEHAVIOUR supportedServiceNameListBeh BEHAVIOUR DEFINED AS “The Supported Service Name List attribute type specifies the services supported by a given managed object”; REGISTERED AS gnimAttribute 3; 6.3.5 Al

27、arm Status (See ITU-T Recommendation M.3100 for the GDMO template for this attribute.) ATIS-0300240.2014 11 6.3.6 Usage State (See ITU-T Recommendation M.3100 for the description of this attribute.) 6.4 Additional Notifications 6.4.1 Service Alarm This notification is used to report when the managed

28、 object detects a service error. It has the same semantics as the quality of Service Alarm notification defined in ITU-T Recommendation X.721. 6.5 Additional Module Definition GNIMASN1DefinedTypesModule iso memberbody usa(840) ansi-t1-240-1998(10043) gnim(0) DEFINITIONS IMPLICIT TAGS := BEGIN EXPORT

29、S everything IMPORTS NameType, ObjectList FROM ASN1DefinedTypesModule ccitt recommendation m gnm(3100) informationModel(0) asn1Modules(2) asn1DefinedTypesModule(0) ; gnimObjectClass OBJECT IDENTIFIER:= iso memberbody usa(840) ansi-t1-240-1998(10043) gnimObjectClass(3) gnimPackage OBJECT IDENTIFIER:=

30、 iso memberbody usa(840) ansi-t1-240-1998(10043) gnimPackage(4) gnimAttribute OBJECT IDENTIFIER:= iso memberbody usa(840) ansi-t1-240-1998(10043) gnimAttribute(7) ServiceType := CHOICE number INTEGER, pString PrintableString, serviceobjectid OBJECT IDENTIFIER END end of GNIMASN1DefineTypesModule 7 C

31、onformance ITU-T Recommendation M.3101 defines management conformance requirements of the Generic Network Infor-mation Model defined in ITU-T Recommendation M.3101. However, M.3101 does not define conformance re-quirements for management information that is referenced in ITU-T Recommendation M.3100.

32、 ATIS-0300240.2014 12 This standard is intended to provide a network model to support the implementation of standardized messages for OSNE interfaces. It is therefore intended to be used with the associated message specification standards. The complete set of conformance requirements for standardize

33、d OSNE messages is given in the conformance section of those standards. Where other telecommunications standards import any of the definitions contained in this standard, such references shall comply with the behavioral and syntactic aspects of those types to the extent specified in this standard. W

34、here other standards refine any of the object class definitions contained in this standard via the refinement and referencing mechanisms defined in ITU-T Recommendation X.722, the object classes that refine these definitions shall comply with the behavioral and syntactic aspects of the superclass to

35、 the extent defined in this standard. ATIS-0300240.2014 13 Annex A (informative) A Bibliography At the time of publication of this standard, the editions of the following references were valid. All standards are subject to revision, and parties are encouraged to investigate the possibility of applyi

36、ng the most recent editions of the standards indicated below. ATIS-0300227.2008, Operations, administration, maintenance, and provisioning (OAM REGISTERED AS 1 3 17 104 objectclass(1) tr836(3) ds1CTPBidirectional(3); B.2.2 ds1CTPSink ds1CTPSink MANAGED OBJECT CLASS DERIVED FROM “Rec. M.3100“:connect

37、ionTerminationPointSink; CHARACTERIZED BY “Rec. M.3100“:createDeleteNotificationsPackage, “Rec. M.3100“:attributeValueChangeNotificationPackage, ds1CTPSinkPkg PACKAGE BEHAVIOUR ds1CTPSinkBeh; ATTRIBUTES ds1CTPId PERMITTED VALUES BCRTR836Iss1Mod.IntegerNameType GET; REGISTERED AS 1 3 17 104 objectcla

38、ss(1) tr836(3) ds1CTPSink(4);ds1CTPSinkBeh BEHAVIOUR DEFINED AS “This managed object represents a termination point where the DS1 link connection is terminated. A change in the value of the operationalState attribute in the inherited operationalStatePackage shall cause a stateChange notification if

39、this attribute is present. A change in the value of any of the following attributes, provided the attribute is present in the managed object, shall cause an attributeValueChange notification: supportedByObjectList (inherited) downstreamConnectivityPointer (inherited) alarmStatus (in the inherited tm

40、nCommunicationsAlarmInformationPackage) currentProblemList (in the inherited tmnCommunicationsAlarmInformationPackage) alarmSeverityAssignmentProfilePointer (in the inherited alarmSeverityAssignmentPointerPackage) channelNumber (in the inherited channelNumberPackage). “; B.2.3 ds1CTPSource ds1CTPSou

41、rce MANAGED OBJECT CLASS DERIVED FROM “Rec. M.3100“:connectionTerminationPointSource; ATIS-0300240.2014 17 CHARACTERIZED BY “Rec. M.3100“:createDeleteNotificationsPackage, “Rec. M.3100“:attributeValueChangeNotificationPackage, ds1CTPSourcePkg PACKAGE BEHAVIOUR ds1CTPSourceBeh; ATTRIBUTES ds1CTPId PE

42、RMITTED VALUES BCRTR836Iss1Mod.IntegerNameType GET; REGISTERED AS 1 3 17 104 objectclass(1) tr836(3) ds1CTPSource(5); ds1CTPSourceBeh BEHAVIOUR DEFINED AS “This managed object represents a termination point where the DS1 link connection is terminated. A change in the value of the operationalState at

43、tribute in the inherited operationalStatePackage shall cause a stateChange notification if this attribute is present. A change in the value of any of the following attributes, provided the attribute is present in the managed object, shall cause an attributeValueChange notification: supportedByObject

44、List (inherited) upstreamConnectivityPointer (inherited) alarmStatus (in the inherited tmnCommunicationsAlarmInformationPackage) currentProblemList (in the inherited tmnCommunicationsAlarmInformationPackage) alarmSeverityAssignmentProfilePointer (in the inherited alarmSeverityAssignmentPointerPackag

45、e) channelNumber (in the inherited channelNumberPackage). “; B.2.4 ds1LineTTPBidirectional ds1LineTTPBidirectional MANAGED OBJECT CLASS DERIVED FROM “Rec. M.3100“:trailTerminationPointBidirectional, ds1LineTTPSink, ds1LineTTPSource; CONDITIONAL PACKAGES loopbackPkg PRESENT IF “an instance is used as

46、 a Facility Access Digroup (FAD) or a Test Access Digroup (TAD)“, loopbackEnablePkg PRESENT IF “the loopbackPkg package is present and an instance supports it“; REGISTERED AS 1 3 17 104 objectclass(1) tr836(3) ds1LineTTPBidirectional(6); B.2.5 ds1LineTTPSink ds1LineTTPSink MANAGED OBJECT CLASS DERIV

47、ED FROM “Rec. M.3100“:trailTerminationPointSink; CHARACTERIZED BY “Rec. X.721 | ISO/IEC 10165-2“: administrativeStatePackage, “Rec. M.3100“:createDeleteNotificationsPackage, “Rec. M.3100“:attributeValueChangeNotificationPackage, “Rec. M.3100“:stateChangeNotificationPackage, “Rec. M.3100“:tmnCommunic

48、ationsAlarmInformationPackage, communicationsAlarmEffectOnServicePkg, ds1LineTTPSinkPkg PACKAGE BEHAVIOUR ds1LineTTPSinkBeh; ATTRIBUTES ATIS-0300240.2014 18 ds1LineTTPId PERMITTED VALUES BCRTR836Iss1Mod.IntegerNameType GET, ds1LineCode GET-REPLACE; CONDITIONAL PACKAGES lineCircuitAddressPkg PRESENT

49、IF “the supporting equipment object (identified by the inherited supportedByObjectList attribute) supports multiple instances of this object class“, callReferencePkg PRESENT IF “an instance supports it“, terminateLeavePkg PRESENT IF “the terminate and leave capability is supported“; REGISTERED AS 1 3 17 104 objectclass(1) tr836(3) ds1LineTTPSink(7); ds1LineTTPSinkBeh BEHAVIOUR DEFINED AS “This managed object represents a termination point where the digital DS1 signal (1.544 Mbps) is terminated. A communicationsAlarm notificati