1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T X.770 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2001) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OSI management Management functions and ODMA functions ODMA notification dispatch function ITU-T Recommendation X.770 (Formerly CCITT Re
2、commendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities X.1X.19 Interfaces X.20X.49 Transmission, signalling and switching X.50X.89 Network aspects X.90X.149 Maintenance X.150X.179 Administrative arrangements X.180X.199 O
3、PEN SYSTEMS INTERCONNECTION Model and notation X.200X.209 Service definitions X.210X.219 Connection-mode protocol specifications X.220X.229 Connectionless-mode protocol specifications X.230X.239 PICS proformas X.240X.259 Protocol Identification X.260X.269 Security Protocols X.270X.279 Layer Managed
4、Objects X.280X.289 Conformance testing X.290X.299 INTERWORKING BETWEEN NETWORKS General X.300X.349 Satellite data transmission systems X.350X.369 IP-based networks X.370X.399 MESSAGE HANDLING SYSTEMS X.400X.499 DIRECTORY X.500X.599 OSI NETWORKING AND SYSTEM ASPECTS Networking X.600X.629 Efficiency X
5、.630X.639 Quality of service X.640X.649 Naming, Addressing and Registration X.650X.679 Abstract Syntax Notation One (ASN.1) X.680X.699 OSI MANAGEMENT Systems Management framework and architecture X.700X.709 Management Communication Service and Protocol X.710X.719 Structure of Management Information
6、X.720X.729 Management functions and ODMA functions X.730X.799 SECURITY X.800X.849 OSI APPLICATIONS Commitment, Concurrency and Recovery X.850X.859 Transaction processing X.860X.879 Remote operations X.880X.899 OPEN DISTRIBUTED PROCESSING X.900X.999 For further details, please refer to the list of IT
7、U-T Recommendations. ITU-T X.770 (01/2001) i ITU-T Recommendation X.770 ODMA notification dispatch function Summary This Recommendation specifies a set of UML descriptions of the OMG notification service, thus placing it within the ODMA architecture (specified in ITU-T X.703) as the ODMA Notificatio
8、n Dispatch Function. Source ITU-T Recommendation X.770 was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. ii ITU-T X.770 (01/2001) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in
9、the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
10、 The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by 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 Resoluti
11、on 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and
12、 a recognized operating agency. 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. ITU takes no position concerning the evidence, validity or applicability of cla
13、imed 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 property, protected by patents, which may be required to implement this Recom
14、mendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2001 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or me
15、chanical, including photocopying and microfilm, without permission in writing from ITU. ITU-T X.770 (01/2001) iii CONTENTS Page 1 Scope. 1 2 References. 1 3 Definitions 1 3.1 Definitions from notification service 1 3.2 Definitions from ITU-T X.703 . 1 3.3 Definitions from UML 2 4 Abbreviations and c
16、onventions. 2 5 Enterprise viewpoint UML use-cases for OMG notification service . 2 5.1 Use-case overview 2 5.2 Notification delivery use case diagram. 3 5.3 Notification posting use case diagram 4 5.4 Filter administration use case diagram . 4 5.5 Consumer administration use case diagram 4 5.6 Supp
17、lier administration use case. 5 6 Information viewpoint model for OMG notification service 5 7 Computational interfaces for notification service. 8 7.1 CosEventComm module. 9 7.2 CosEventChannelAdmin module . 9 7.3 CosTypedEventComm module. 10 7.4 CosTypedEventChannelAdmin module . 10 7.5 CosNotifyC
18、omm module 12 7.6 CosNotifyChannelAdmin module 14 7.7 CosNotification module 19 7.8 CosNotifyFilter module 20 7.9 CosTypedNotifyComm module 21 7.10 CosTypedNotifyChannelAdmin module 23 8 Engineering interface definitions 27 ITU-T X.770 (01/2001) 1 ITU-T Recommendation X.770 ODMA notification dispatc
19、h function 1 Scope This ODMA Notification Dispatch Function is part of the Open Distributed Management Architecture, as specified in ITU-T X.703. This Recommendation references the specification of the OMG notification service for the normative specification of the ODP IDL (ITU-T X.950) engineering
20、viewpoint interface definitions. This Recommendation provides a UML based set of enterprise, information, and computational viewpoint language description of the OMG notification service, thus placing it within ODMA as the Notification Dispatch Function. 2 References The following ITU-T Recommendati
21、ons and other references contain provisions 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; all users of this Recommendation are there
22、fore encouraged to investigate the possibility 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. ITU-T X.703 (1997) | ISO/IEC 13244:1998, Information technology Open Distributed Ma
23、nagement Architecture. OMG Document formal/2000-06-20, Notification service specification. OMG Document formal/1999-06-01, OMG Modeling Book. 3 Definitions 3.1 Definitions from notification service The following terms are used as defined in OMG notification service: filter; mapping filter; structure
24、d notifications (content having a fixed header and a flexible body with names for each value element); typed notifications (content conforming to a statically defined syntax); untyped notifications (content determined at time of delivery). 3.2 Definitions from ITU-T X.703 The following terms are use
25、d as defined in ITU-T X.703: enterprise viewpoint; information viewpoint; computational viewpoint; engineering viewpoint; 2 ITU-T X.770 (01/2001) notification. 3.3 Definitions from UML The following terms are used as defined in UML: association; association class; class diagram; include; use case di
26、agram. 4 Abbreviations and conventions The following abbreviations are used in this Recommendation: CEC Cos Event Comm CN Cos Notification CNC Cos Notification Comm CNCA Cos Notify Channel Admin CNF Cos Notify Filter CTEC Cos Typed Event Comm The diagrams in this Recommendation use the Notation spec
27、ified in the OMG UML version 1.3. 5 Enterprise viewpoint UML use-cases for OMG notification service The actors are shown only at the first level of the use case diagram. Where the detailed decompositions are described for the use cases, the actors are not explicitly shown for readability. 5.1 Use-ca
28、se overview See Figure 5-1. T0414440-00channeladministrationconsumeradministrationnotificationdeliveryadministratorconsumersupplieradministrationnotificationpostingfilteradministrationsupplierFigure 5-1/X.770 High-level use case diagram for notification service ITU-T X.770 (01/2001) 3 In this figure
29、, all the use cases correspond to the various functions that are part of the notification service. These use cases include both administrative activities such as consumer administration, and the activities for dispatching the notifications. An administrator is responsible for administering the overa
30、ll properties of notification channels, which are used to receive notifications from suppliers and deliver the received notifications to consumers that have subscribed to the notifications. Consumers and administrators are involved in the consumer specific administration for notification channels. S
31、uppliers and administrators are involved in the supplier specific administration for notification channels. Administrators, suppliers and consumers are involved in the administration of filters, which control the receipt and delivery of notifications. The supplier is involved in the posting of notif
32、ications. The supplier may not know the ultimate consumers of the notifications it supplies. The consumer receives the delivered notifications. The consumer may not know the originating supplier of the notifications it consumes. 5.2 Notification delivery use case diagram See Figure 5-2. T0414450-00p
33、ushdeliverynotificationdeliverypulldelivery Figure 5-2/X.770 Push and pull as specialization of notification delivery Notifications may be delivered using either a push model (notification service invokes an operation on consumer in order to deliver a notification to the consumer) or a pull model (c
34、onsumer invokes an operation on the notification service in order to have its notifications delivered to itself). 4 ITU-T X.770 (01/2001) 5.3 Notification posting use case diagram See Figure 5-3. T0414460-00pullpostingnotificationposting pushpostingFigure 5-3/X.770 Push and pull as specialization fo
35、r notification posting Notifications may be posted using either a push model (supplier invokes an operation on notification service in order to post a notification) or a pull model (notification service invokes an operation on the supplier to receive posted notifications from the supplier). 5.4 Filt
36、er administration use case diagram See Figure 5-4. T0414470-00createfilterfilteradministration modifyfilterFigure 5-4/X.770 Filter administration includes creating and modifying filters There is a need for mechanisms to both create and modify the logical constructs of filters, which control the deli
37、very of notification instances based on the actual values of the parameters of the notification, (e.g. do not deliver notifications which have a error count of zero). 5.5 Consumer administration use case diagram Figure 5-5 shows how to use the proxy administration corresponding to the consumer. The
38、administration of a consumer proxy includes the following functions: create a proxy, define the filter (associating filter) to determine what notifications are to be received, and attach or detach to/from the proxy. The notify subscribe use case supports the function for the consumer to subscribe to
39、 notifications resulting from changes to the notification types published by the supplier. ITU-T X.770 (01/2001) 5 T0414480-00consumer proxyadministrationobtainadministratorconsumernotifysubscribeattachconsumeradministrationassociatefilterdetachFigure 5-5/X.770 Consumer administration 5.6 Supplier a
40、dministration use case Figure 5-6 shows how to use the proxy administration corresponding to the supplier. The administration of a supplier proxy includes the following functions: create a proxy, define the filter (associating filter) to determine what notifications are to be forwarded and attach or
41、 detach to/from the proxy. The notify publish use case supports the function for the supplier to publish changes (addition or deletion) to notification types it supplies. T0414490-00supplier proxyadministrationobtainadministratorsuppliernotifypublishattachsupplieradministrationassociatefilterdetachF
42、igure 5-6/X.770 Supplier administration 6 Information viewpoint model for OMG notification service This clause shows information object classes and their relationships. Attributes for information object classes are not shown in this clause, for purposes of simplicity of exposition. Not all classes s
43、hown in this viewpoint correspond to IDL interfaces for the notification service. See Figure 6-1. 6 ITU-T X.770 (01/2001) T0414500-00filtersimpleFilter mappingFilterFigure 6-1/X.770 Filter types A filter has a logical construct, made up from assertions on the values of the various parameters of a no
44、tification instance along with logical operators, (i.e. and, or, not). The filter evaluates to either true or false. A simple filter is used to determine delivery of a notification either into or out of a channel. If the filter construct evaluates to true the notification instance is delivered. A ma
45、pping filter is used to associate a particular quality of service value with a notification instance. If the filter construct is true, the associated QOS value is assigned to that notification instance. See Figure 6-2. T0414510-00notificationDeliveryTypeuntypedNotificationType typedNotificationTypes
46、tructureNotificationTypenotificationdeliveredAs1.3+instance+type0*Figure 6-2/X.770 Notification delivery types Each notification instance is delivered using a notification delivery type, which may be either an untyped notification type (encoded as a single value of type “any“), a structure notificat
47、ion type (encoded as a structure containing a fixed header followed by elements which are name value pairs), or a typed notification type (encoded as a strongly typed operation). Each notification instance (i.e. the specification of the semantic contents of the notification) may be delivered using o
48、ne or more of these notification delivery types. The notification service provider needs to provide translation services allowing consumers of any notification delivery type to receive notifications posted by providers using any of the three notification delivery types. See Figure 6-3. ITU-T X.770 (
49、01/2001) 7 T0414520-000*11110*0*0*0101proxyConsumerCosEventChannelnotificationChannelproxySupplierConsumerSupplierFigure 6-3/X.770 Channel types A notification channel is a specialization of a COS event channel and, as such, has zero or more proxy consumers and/or proxy suppliers. Each proxy consumer is associated with at most one supplier. Each proxy supplier is associated with at most one consumer. Each supplier may be associated with zero or more proxy consumers, while each consumer may be associa
