1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.816TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Corrigendum 2(08/2002) SERIES Q: SWITCHING AND SIGNALLING Q3 interface CORBA-based TMN services Corrigendum 2 ITU-T Recommendation Q.816 (2001) Corrigendum 2 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND
2、 SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEM No. 4 Q.120Q.139
3、SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 Q.140Q.199 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.250Q.309 SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399 SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF S
4、IGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.
5、1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.816 (2001)/Cor.2 (08/2002) i ITU-T Recommendation Q.816 CORBA-based TMN services Corrigend
6、um 2 Source Corrigendum 2 to ITU-T Recommendation Q.816 (2001) was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 6 August 2002. ii ITU-T Rec. Q.816 (2001)/Cor.2 (08/2002) FOREWORD The International Telecommunication Union (ITU) is the United Nation
7、s specialized agency in 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 telecommunicatio
8、ns on a worldwide basis. 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 la
9、id down in WTSA Resolution 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 telecommunic
10、ation administration and 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
11、 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 property, protected by patents, which may be required
12、 to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2002 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without
13、 the prior written permission of ITU. ITU-T Rec. Q.816 (2001)/Cor.2 (08/2002) iii CONTENTS Page 1) Subclause 6.2 1 ITU-T Rec. Q.816 (2001)/Cor.2 (08/2002) 1 ITU-T Recommendation Q.816 CORBA-based TMN services Corrigendum 2 1) Subclause 6.2 Replace the following paragraph: (R) NOTIF-4 The Notificatio
14、n Service shall support structured events. with this new paragraph: (R) NOTIF-4 The Notification Service shall support either structured events or structured and typed events. The managed system application code, however, must generate only structured or only typed notifications, not both. And immed
15、iately after add the following Note: NOTE Typed events do not rely upon the use of CORBA any data types, making them more efficient and, therefore, the preferred choice. Add the following text after the Note: Since managed systems may generate either structured or typed events, managing systems gene
16、rally need to be able to receive both typed and structured events for best performance and interoperability. If a managing system does support both, it shall choose the most efficient way of receiving notifications. One way to do this is to initially subscribe to both structured and typed events and
17、 note what type of events are received. The managed system must generate heartbeat notifications, so the managing system should not have to wait long to receive a notification. Since an event channel that supports both structured and typed events can translate typed events to structured but not vice
18、 versa, the managing system can deduce how the notifications are originally being generated by the managed system application. First, if the event channel does not support typed notifications, the managing system will be prevented from subscribing to typed notifications. The managing system will the
19、n know that all notifications will be structured. If the managing system can subscribe to both and receives copies of notifications in both typed and structured format, it knows that the notifications are being generated by the managed system application as typed events and that the event channel is
20、 creating a copy and translating it to structured. The managing application should then unsubscribe to structured notifications to relieve the event channel from performing this duty. If the managing system can subscribe to both but receives only structured notifications, it knows that they are bein
21、g originally generated as structured notifications and it may unsubscribe to the typed notifications. Table 2 lists the possible permutations in the kinds of events supported by the managed system application itself, the managed systems notification channel and the managing system application. Comme
22、nts on each combination are provided. The managed system application code may generate only structured notifications or only typed notifications, but not both. If managed systems were allowed to generate both, it would be impossible for a managing system to receive notifications in the most efficien
23、t manner while being assured of receiving all notifications. The event channel may support structured notifications only, or structured and typed notifications. An event channel that supports only typed notifications would not conform to the OMGs Notification Service specification 4. 2 ITU-T Rec. Q.
24、816 (2001)/Cor.2 (08/2002) Table 2/Q.816 Managed system application generates Event channel supports Managing system can receive Comments Structured Structured only Structured only Straightforward compatibility. The managing system simply subscribes to and receives structured events. Structured Stru
25、ctured only Typed only Incompatible. When the managing system attempts to subscribe to typed events the channel will not support it. The managing system should report that it is incompatible with the managed system because the managing system does not support structured events. Structured Structured
26、 only Both Compatible. The managing systems attempt to subscribe to typed events will be rejected by the channel, but it will be able to receive structured events. Structured Both Structured only Straightforward compatibility. The managing system simply subscribes to and receives structured events.
27、Structured Both Typed only Incompatible. The managing system will be able to successfully subscribe to typed events from the event channel, but since the channel cannot translate structured events to typed events, it will not receive any notifications. The managing system will detect a problem when
28、it does not receive heartbeat notifications. It should report the problem and suggest as a likely cause, its incompatibility with systems that generate only structured events. Structured Both Both Compatible. The managing system will be able to successfully subscribe to both structured and typed eve
29、nts, but since the channel cannot translate structured events to typed events, it will receive only structured events. The managing system should unsubscribe to the typed events when it detects it is receiving only structured events. Typed Structured only Structured only Nonsensical. It does not mak
30、e sense for a managed system supplier to provide application code that generates typed events if the systems event channel supports only structured events. Typed Structured only Typed only As above. Typed Structured only Both As above. Typed Both Structured only Compatible. The managing system subsc
31、ribes to structured events and relies upon the channel to convert. Performance could be an issue. Typed Both Typed only Straightforward compatibility. The managing system simply subscribes to and receives typed events. Typed Both Both Compatible. The managing system will be able to successfully subs
32、cribe to both structured and typed events, and will receive notifications in both forms. The managing system should unsubscribe to the structured events as soon as it successfully receives a typed event. ITU-T Rec. Q.816 (2001)/Cor.2 (08/2002) 3 The incompatibility problems listed in Table 2 result
33、when a managing system is limited to only receiving typed events. If a managing system supports only typed events, an implementation agreement must be made with managed system suppliers to also support typed events. Replace the following paragraph: (O) NOTIF-6 The use of typed events is optional. wi
34、th this new paragraph: (O) NOTIF-6 Null requirement, not deleted to maintain numbering. Delete the Note following (O) NOTIF-6. Geneva, 2002 SERIES OF ITU-T RECOMMENDATIONS Series A Organization of the work of ITU-T Series B Means of expression: definitions, symbols, classification Series C General t
35、elecommunication statistics Series D General tariff principles Series E Overall network operation, telephone service, service operation and human factors Series F Non-telephone telecommunication services Series G Transmission systems and media, digital systems and networks Series H Audiovisual and m
36、ultimedia systems Series I Integrated services digital network Series J Cable networks and transmission of television, sound programme and other multimedia signals Series K Protection against interference Series L Construction, installation and protection of cables and other elements of outside plan
37、t Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits Series N Maintenance: international sound programme and television transmission circuits Series O Specifications of measuring equipment Series P Telephone transmi
38、ssion quality, telephone installations, local line networks Series Q Switching and signalling Series R Telegraph transmission Series S Telegraph services terminal equipment Series T Terminals for telematic services Series U Telegraph switching Series V Data communication over the telephone network Series X Data networks and open system communications Series Y Global information infrastructure and Internet protocol aspects Series Z Languages and general software aspects for telecommunication systems
