1、 International Telecommunication Union ITU-T M.3702TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2010) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Integrated services digital networks Common management services Notification management Protocol neutral requirem
2、ent and analysis Recommendation ITU-T M.3702 ITU-T M-SERIES RECOMMENDATIONS TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International teleph
3、one circuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.
4、1199 International public telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600
5、M.3999Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3702 (01/2010) i Recommendation ITU-T M.3702 Common management services Notification management Protocol neutral requirement and analysis Summary Recommendation I
6、TU-T M.3702 provides the requirements and analysis for one of the common management services notification management. The functional requirements for notification management interface include the management functions for notification subscription, notification type, notification storage and recovery
7、. In the analysis part, the detail information model supporting the above function across the management interface is provided. History Edition Recommendation Approval Study Group 1.0 ITU-T M.3702 2010-01-13 2 Keywords Common management service, notification management, notification IRP. ii Rec. ITU
8、-T M.3702 (01/2010) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is
9、responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by
10、the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collab
11、orative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certai
12、n mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requiremen
13、ts. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. IT
14、U takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual
15、property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 All rights rese
16、rved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T M.3702 (01/2010) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviation
17、s 3 5 Conventions 3 6 Requirements 3 6.1 Concepts and background . 3 6.2 Business-level requirements . 3 6.3 Specification-level requirements 5 7 Analysis 16 7.1 Concepts and background . 16 7.2 Information object classes 17 7.3 Interface definition . 22 Bibliography. 38 Rec. ITU-T M.3702 (01/2010)
18、1 Recommendation ITU-T M.3702 Common management services Notification management Protocol neutral requirement and analysis 1 Scope The purpose of this Recommendation is to define an interface through which a manager can subscribe to an agent for receiving notifications. This Recommendation provides
19、the requirements and analysis phase of one of the common management services: Notification management in a protocol neutral way. It defines, for the purpose of subscribing to an agent for receiving notifications, the basic requirements that shall be fulfilled by a notification interface. Agents gene
20、rate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. An agent emits notifications. A manager receives notifications. This Recommendation defines an interface through which a manager can subscribe to an agent for receiving
21、notifications and the information model used to define specific notification types in other Recommendations. Notifications are sent to managers without the need for managers to periodically check for new notifications. This Recommendation provides the protocol neutral model definition for notificati
22、on. It defines, for the purpose of subscribing to an agent for receiving notifications, the information observable and controlled by the management systems client, and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all no
23、tifications. An agent may emit one or multiple types of notifications, defined as extensions of the notification information object class (IOC) defined herein. This Recommendation defines a mechanism that a manager can use to determine the types of notifications supported by an agent. It also define
24、s a mechanism (subscribe and unsubscribe operations) that a manager can use to specify the type of notifications an agent should emit to a manager during subscription. It also defines a mechanism (getSubscriptionIds operation) that a manager can use to check which types of notifications it has subsc
25、ribed to. A manager can set and change filtering criteria applicable during the life-cycle of a subscription and subscribe to filters already configured by another manager. A manager can also exercise flow control on an agents emission of notifications (suspendSubscription, resumeSubscription operat
26、ions). A manager can create several subscriptions. This will result in multiple subscriptions. As far as the agent is concerned, notifications are sent to multiple destinations with different filtering criteria. This Recommendation specifies the information that is carried in all notifications. Furt
27、her information is defined by specializations of the Notification IOC. How a manager discovers the agents address or reference (so that the manager can invoke an operation) is outside the scope of this Recommendation. 2 References The following ITU-T Recommendations and other references contain prov
28、isions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possib
29、ility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommen
30、dation. 2 Rec. ITU-T M.3702 (01/2010) ITU-T M.3020 Recommendation ITU-T M.3020 (2009), Management interface specification methodology. ITU-T M.3160 Recommendation ITU-T M.3160 (2008), Generic, protocol-neutral management information model. ITU-T X.680 Recommendation ITU-T X.680 (2008) | ISO/IEC 8824
31、-1:2008, Information technology Abstract syntax Notation One (ASN.1): Specification of basic notation. ITU-T X.701 Recommendation ITU-T X.701 (1997) | ISO/IEC 10040:1998, Information technology Open Systems Interconnection Systems management overview. ITU-T X.734 Recommendation ITU-T X.734 (1992) |
32、ISO/IEC 10164-5:1993, Information technology Open Systems Interconnection Systems Management: Event report management function. ITU-T X.790 Recommendation ITU-T X.790 (1995), Trouble management function for ITU-T applications. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the fo
33、llowing terms defined elsewhere: 3.1.1 agent ITU-T M.3020: Encapsulates a well-defined subset of management functionality. It interacts with managers using a management interface. From the managers perspective, the agent behaviour is only visible via the management interface. 3.1.2 event ITU-T X.790
34、: An instantaneous occurrence that changes the global status of an object. This status change may be persistent or temporary, thus allowing for surveillance, monitoring, and performance measurement functionality, etc. Events may or may not generate reports; they may be spontaneous or planned; they m
35、ay trigger other events or may be triggered by one or more other events. 3.1.3 information object class ITU-T M.3020: Describes the information that can be passed/used in management interfaces and is modelled using the stereotype “Class“ in the UML meta-model. For a formal definition of information
36、object class and its structure of specification, see Annex B of ITU-T M.3020. 3.1.4 manager ITU-T M.3020: Models a user of agent(s) and it interacts directly with the agent(s) using management interfaces. Since the manager represents an agent user, it gives a clear picture of what the agent is suppo
37、sed to do. From the agent perspective, the manager behaviour is only visible via the management interface. NOTE Considered equivalent to IRPManager 3GPP TS 32.150. 3.1.5 notification ITU-T X.701: Information emitted by a managed object relating to an event that has occurred within the managed object
38、. 3.2 Terms defined in this Recommendation This Recommendation has no new definitions. Rec. ITU-T M.3702 (01/2010) 3 4 Abbreviations This Recommendation uses the following abbreviations: DN Distinguished Name EM Element Manager IOC Information Object Class IRP Integration Reference Point NE Network
39、Element NM Network Manager UML Unified Modelling Language 5 Conventions This Recommendation follows the conventions defined in ITU-T M.3020. In this Recommendation, the term “subscription“ indicates a subscription of a notification service, and the term “subscriber“ is the representation in an agent
40、 of a receiver of notifications, Notification IRP is an interface in an agent providing notification management functions. 6 Requirements 6.1 Concepts and background Information of an event is carried in notification. An agent (typically an EM or a NE) emits notifications. A manager (typically a net
41、work management system) receives notifications. The purpose of Notification IRP is to define an interface through which a manager can subscribe to an agent for receiving notifications. This notification IRP bases its design on work captured in ITU-T X.734. 6.2 Business-level requirements 6.2.1 Requi
42、rements An event may occur in the network at any time. The agent should send notifications to the manager indicating these events. The notification management requirements can be grouped into one of the following categories: General, i.e., the notification management requirements with general purpos
43、e, e.g., notification report, notification mechanism, notification header, etc. Subscription management, e.g., subscribe notification, unsubscribe notifications, suspend subscription, resume subscription, modify subscription, query subscription. Notification type, e.g., query notification type. Noti
44、fication storage and recovery, e.g., temporary notification storage and recover. 6.2.1.1 General REQ-NO-FUN-01 The agent shall provide a mechanism to send notifications to managers. REQ-NO-FUN-02 The notification mechanism will allow the definition of notification types in other Recommendations. 4 R
45、ec. ITU-T M.3702 (01/2010) REQ-NO-FUN-03 It is required that all notifications emitted by the notification interface support the same header that contains enough information to identify the type of notification, the source of the notification and the time at which the notification originated. 6.2.1.
46、2 Subscription management The following requirements apply to the notification management interface. REQ-NO-FUN-O4 The agent shall provide the managers with the capability to subscribe and unsubscribe to the notification mechanism. REQ-NO-FUN-05 A manager shall be able to specify filtering criteria
47、(including the types of notifications) of a subscription that shall be applied by the notification mechanism. REQ-NO-FUN-06 A manager shall be able to specify the destination of a subscription to which notifications should be forwarded by the notification mechanism in the agent. REQ-NO-FUN-07 A mana
48、ger shall be able to suspend and resume the notifications pertaining to a subscription. Events may be lost when notifications are suspended. REQ-NO-FUN-08 A manager shall be able to suspend and resume notifications from all subscriptions for a given agent. Events may be lost when notifications are s
49、uspended. REQ-NO-FUN-09 Any manager shall be able to set and change filtering criteria applicable during the life-cycle of one of its subscriptions in order to change the pre-defined criteria which determine what notifications are sent. REQ-NO-FUN-10 A manager shall be able to query the information of a specified subscription in an agent. REQ-NO-FUN-11 A manager shall be able to query the information of all the subscriptions of the manager for the given agent. 6.2.1.3 Notification type REQ-NO-FUN-12 T
