ITU-T Q 823-1996 Stage 2 and Stage 3 Functional Specifications for Traffic Management - Series Q Switching and Signalling Specifications of Signalling System No 7 - Q3 Interface (S.pdf

《ITU-T Q 823-1996 Stage 2 and Stage 3 Functional Specifications for Traffic Management - Series Q Switching and Signalling Specifications of Signalling System No 7 - Q3 Interface (S.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 823-1996 Stage 2 and Stage 3 Functional Specifications for Traffic Management - Series Q Switching and Signalling Specifications of Signalling System No 7 - Q3 Interface (S.pdf（116页珍藏版）》请在麦多课文档分享上搜索。

1、 STD-ITU-T RECMN Q-BZ3-ENGL L99b W qb2592 Ob27555 TBO m INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.823 (07/96) SERIES Q: SWITCHING AND SIGNALLING Specifications of Signalling System No. 7 - Q3 interface Stage 2 and Stage 3 functional specifications

2、for traffic man age ment ITU-T Recommendation Q.823 (Previously CCITT Recommendation) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE

3、 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATION OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES I

4、NTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS General Message transfer part Simplified message transfer part Signalling connection control part Telephone user part ISDN supplementary services Data user part Signalling System

5、No. 7 management ISDN user part Transaction capabilities application part Test sDecification 43 interface DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 General Data link layer Network layer User-network management Stage 3 description for supplementary services using DSS 1 PUBLIC LAND MOBILE NETWORK INT

6、ERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN Q.l-Q.3 Q.4-Q.59 Q.60-Q.99 Q. 1 00-Q. 119 Q.120-Q.249 Q ,250-Q.309 Q. 31 0-Q. 399 Q.400-(2.499 Q. 500-Q. 599 Q.600-Q.699 Q.700-Q.849 Q.700 Q. 701 Q.709 Q.710 Q.711-Q.719 Q .72O-Q. 729 Q.7304.739 Q I 7404.749 Q.750-Q.759 Q. 77

7、04.779 Q.780-Q.799 Q.80-Q.849 Q.850-Q.999 Q.850-Q.919 Q. 92041.929 Q.930-Q.939 Q. 940-Q .949 Q.950-Q.999 Q.1000-Q.1099 Q.1100-Q.1199 Q. 1200-Q.1999 Q.2000-Q.2999 Q. 760-Q.769 For frther details, please refir to ITU-T List of Recommendations. COPYRIGHT International Telecommunications Union/ITU Telec

8、ommunicationsLicensed by Information Handling ServicesSTD-ITU-T RECMN Q.823-ENGL L77b W 48b259L Ob29557 853 W ITU-T RECOMMENDATION Q.823 STAGE 2 AND STAGE 3 FUNCTIONAL SPECIFICATIONS FOR TRAFFIC MANAGEMENT Summary The scope of this Recommendation is to provide an information model which covers the m

9、anagement aspects of the traffic management service functions in an exchange. The scope is limited only to circuit switched networks using hierarchical routing. This Recommendation focuses on the Stage 2 and Stage 3 description of the 43 interface between Network Elements (NEs) and Operations System

10、s (0%). The Stage 1 description is provided in E.410-Series Recommendations and in Recommendation E.502. Source ITU-T Recommendation Q.823 was prepared by ITU-T Study Group 11 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 9th of July 1996. COPYRIGHT International Tele

11、communications Union/ITU TelecommunicationsLicensed by Information Handling Services STD.ITU-T RECMN Q-823-ENGL 199b m Yb259L 0b29558 79T = FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Stan

12、dardization Sector (ITU-T) is a permanent organ of the ITU. The 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. The World Telecommunication Standardization Conference

13、 (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas o

14、f information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operati

15、ng agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The IT takes no position concerning the evidence, validity or applicability of claimed Intellect

16、ual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU hadhad not received notice of intellectual property, protected by patents, which may be required to implement this Recommendati

17、on. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1997 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechani

18、cal, including photocopying and microfilm, without permission in writing from the IT. II Recommendation 4.823 (07/96) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services1 2 2.1 2.2 3 4 4.1 4.2 5 6 6.1 6.2 6.3 7 7.1 7.2 7.3 7.4 8 8.1 8.2 9

19、10 10.1 STD-ITU-T RECMN Q-823-ENGL L77b Lib2571 b27557 b2b m CONTENTS Scope Introduction Functional requirements . Modelling methodology . Normative references Definitions Alternate routed Direct routed . Symbols and abbreviations . Information model Entity relationship diagram Inheritance hierarchy

20、 Naming hierarchy . Infomation model description . Object class descriptions 7.1.1 Managed element fragment . 7.1.2 Performance monitoring fragment 7.1.3 Control fragment . 7.1.5 Administrative fragment . 7.1.4 State fragment . Definition of common attributes 7.2.1 Relative distinguished name 7.2.2

21、State attributes . Description of actions . Description of notifications Functional units Negotiation of functional units . Functional units from other Recommendations . Relationship with other Recommendations Conformance Static conformance . 1 1 2 2 2 4 5 5 7 8 9 10 10 12 21 39 39 40 40 40 40 40 41

22、 41 41 42 42 42 . 111 Recommendation 4.823 (07196) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services STD-ITU-T RECMN Q.823-ENGL L97b W LiBb259L Ob275b0 3ir8 10.2 Dynamic conformance 1 O . 3 Management implementation conformance statement

23、 requirements . 11 1 1.1 Formal object class definitions . Definition of object classes . 11.1.1 ACC . 1 1.1.2 accAffectedTraffic . 1 1 . 1.3 accTrigger 11.1.4 adc . 1 1.1.5 adcTrigger . 1 1 . 1.6 cancelFrom 11.1.7 cancelRerouted 11.1.8 cancelTo 1 1 . 1.9 CircuitEndPointSubgroupCurrentData 1 1 . 1 .

24、 1 O circuitEndPointSubgroupHistoryData . 1 1.1.1 1 congestionLevelIndication 1 1.1.12 destinationCodeContro1 . 11.1.13 dccGroup . 1 1 . 1 . 14 exchangeCumentData 1 1.1.15 exchangeHistoryData 1 1 . 1. 16 htrDestination 1 1.1.17 observedDestination 1 1.1.18 observedDestinationCurrentData 1 1.1.19 obs

25、ervedDestinationHistoryData . 11.1.20 scr 11.1.21 ScrAffectedTraffic . 11.1.22 skip 11 . 1 . 23 StateIndicator 1 1.1.24 tarFrom 11.1.25 tarTo 1 1.1.26 tmCircuitEndPointSubgroup . 1 1 . 1.27 tmCircuitEndPointSubgroupCurrentData . 11.1.28 tmExchangeCurrentData . 1 1 . 1.29 tmObservedDestinationCurrent

26、Data . 11.1.30 tmTrafficControlCurrentData 1 1.1.3 1 trafficcontrol . 11.1.32 trafficControlCurrentData . 1 1.1.33 traffcControlHistoryData . Page 43 44 44 44 44 45 45 45 46 47 48 48 49 50 50 50 51 52 53 53 54 54 55 55 56 56 57 57 58 59 60 60 61 61 62 62 62 iv Recommendation 4.823 (07/96) COPYRIGHT

27、International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services11.2 Definition of name binding 11.3 Definition of packages 1 1.4 Definition of common behaviour . 1 1.5 Definition of attributes . 11.6 Definition of actions . 1 1.7 1 1.8 Definition of notificatio

28、ns ASN . 1 defined types module Appendix I . Traffic management TMN management service . Appendix II . Correlation between E.412 traffic controls and object classes covered in this Recommendation Appendix III . State transition diagrams for automatic and manual controls . Appendix IV . Differentiati

29、on of direct and alternate routed traffic for cancel-to and cancel- fi-om controls Appendix V . Use of 4.822 history data for traffic measurements V . 1 Introduction V.2 Overview of the performance management information model- V.3 Initial configuration V.3.1 Current data . V.3.2 History data . V.3.

30、3 Simple scanner V.4 Autonomous reporting V.5 Polled reporting V.6 Changes to the report V.7 Conclusions Appendix VI . Circuit end point subgroup object definition Appendix VI1 . Mapping of NM functions to functional units . Appendix VI11 . Support of the audit functionality using Q.823 VI11 . 1 Int

31、roduction VIII.2 Functional requirements . VIII.3 Types of audit . VIII.3.1 FulVpartial audit VIII.3.2Change audit VI11.4 Mechanisms VIII.4.1 Use of PT-GET service . Recommendation 4.823 (07/96) Page 63 67 70 71 80 81 82 87 88 89 90 91 91 91 92 92 92 92 93 93 94 94 95 98 99 99 99 100 100 100 100 100

32、 V COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesVIII.4.2Use of simple scanner VIII.4.3Use of discovery object . VIII.5 Conclusions Appendix IX - Examples of addressing errors in Q.823 . IX . 1 Introduction IX.2 Protocol machine gener

33、ated errors . IX.3 Use of CMISE errors IX.4 Use of specific errors IX.5 Conclusion Appendix X - Control hierarchy . Page 101 102 102 102 102 102 103 105 105 105 vi Recommendation 4.823 (07/96) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Ser

34、vicesSTD-ITU-T RECMN Q=23-ENGL 177b m Lib257L Ob295b 057 = Recommendation 4.823 STAGE 2 AND STAGE 3 FUNCTIONAL SPECIFICATIONS FOR TRAFFIC MANAGEMENT (Geneva, 1996) 1 Scope The scope of this Recommendation is to provide an information model which covers the management aspects of the traffic managemen

35、t service functions in an exchange. The scope is limited only to circuit switched networks using hierarchical routing. This Recommendation focuses on the Stage 2 and Stage 3 description of the Q3 interface between Network Elements Es) and Operations Systems (OSs). The Stage 1 description is provided

36、 in E.41 O-Series Recommendations and in Recommendation E.502. The following restrictions on the scope are to be regarded: - For traffic surveillance and management, this Recommendation makes use of the traffic measurements defined in the E-Series of Recommendations. The handling and processing of t

37、raffic management related information on the OS level and the forwarding of these data on the OS level are out of the scope of this Recommendation. Network performance data is needed as input for the traffic management controls. Sometimes the same data can be used for traffic measurements, but this

38、coincidence is ignored in this context. The network performance data is identified and modelled as far as it is relevant and when the models are not available from other Recommendations. Functions which are supportable by information models defined in other Recommendations are not redefined in this

39、Recommendation. Those information models are either referenced directly by the incorporation of the objects or indirectly by subclassing from other information. As far as possible and sensible, the functions defined in the OS1 Systems Management Functions are considered. - - - - 2 Introduction The o

40、bjective of traffic management is to enable as many calls as possible to be completed successfully. This objective is met by maximizing the use of available resources in any situation. It is also considered a part of this function to supervise the performance of a network and to be able, if necessar

41、y, to take action to control the flow of traffic for optimizing the utilization of the network capacity. The information model presented in this Recommendation provides a common view for the performance data retrieval from the NE, and for the administration of controls and instructions from the OS t

42、o the NE. The performance data provides information for the activation of traffic management controls and for the validation of traffic management actions. It also serves as input data for further traffic management actions. Recommendation 4.823 (07/96) 1 COPYRIGHT International Telecommunications U

43、nion/ITU TelecommunicationsLicensed by Information Handling ServicesSTD-ITU-T RECMN Q-823-ENGL 179b 48b257L Ob275b4 T73 2.1 Functional requirements The traffic management control functions considered in the model are based on controls specified in Recommendation E.412. The performance monitoring fun

44、ctions in this model are based on measurement items selected out of Recommendation E. 5 02. Appendix I identifies the individual traffic management service functions incorporated in Recommendation M.3200 that are covered by this Recommendation and those that are out of scope of this Recommendation.

45、Appendix II provides a mapping between E.412 controls and the control objects covered in this Recommendation. 2.2 Modelling methodology The modelling techniques described in Recommendation M.3020 (TMN Interface Specification Methodology) are used in this Recommendation. The definitions of the suppor

46、ting managed object classes given in the OS1 Recommendations (X.700-Series Recommendations) have been adopted in the modelling work. 3 Normative references The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this

47、 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 therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and ot

48、her references listed below. A list of the currently valid ITU-T Recommendations is regularly published. 2 CCITT Recommendation E.4 1 O (1 992), International network management - General information. CCITT Recommendation E.411 (1 992), International network management - Operational guidance. CCITT

49、Recommendation E.412 (1 992), Network management controls. CCITT Recommendation ES02 (1 9921, Traflc measurement requirements for digital telecommunication exchanges. ITU-T Recommendation M.30 1 O (19961, Principles for a Telecommunications Management Network. ITU-T Recommendation M.3 100 (1995), Generic network information model. ITU-T Recommendation 4.542 (1 993), Digit exchange design objectives - Operations and maintenance. ITU-T Recommendation Q.763 (1993), Formats and codes of the ISDN User Part of Signalling System No. 7. ITU-T Recommendation Q.822 (1994), S