ITU-T X 790-1995 Trouble Management Function for ITU-T Applications - Data Networks and Open System Communications - OSI Management (Study Group 7) 120 pp《ITU-T应用困难管理功能-数据和开放网络通信-O.pdf

《ITU-T X 790-1995 Trouble Management Function for ITU-T Applications - Data Networks and Open System Communications - OSI Management (Study Group 7) 120 pp《ITU-T应用困难管理功能-数据和开放网络通信-O.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 790-1995 Trouble Management Function for ITU-T Applications - Data Networks and Open System Communications - OSI Management (Study Group 7) 120 pp《ITU-T应用困难管理功能-数据和开放网络通信-O.pdf（120页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMU N CATION UN ION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.790 DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OS1 MANAGEMENT (1 1/95) TROUBLE MANAGEMENT FUNCTION FOR ITU-T APPLICATIONS ITU-T Recommendation X.790 (Previously “CCITT Recommendation”) FOREWORD The ITU-

2、T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (ITU). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommen- dations on them with a view to standardizing telecommunications on a worldwide b

3、asis. The World Telecommunication Standardization Conference (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 p

4、rocedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). ITU-T Recommendation X.790 was prepared by ITU-T Study Group 7 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 21st of November 1995. NOTE In this Recommendation, the expression “Administration” i

5、s used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITU 1996 Ali rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without

6、 permission in writing from the ITU. _ ITU-T RECMN*X.90 95 4862571 Ob07790 266 = Subject area PUBLIC DATA NETWORKS ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS Recommendation Series (February 1994) ORGANIZATION OF X-SERIES RECOMMENDATIONS Interfaces Transmission, Signa

7、lling and Switching X.20-X.49 X.50-X.89 I Services and Facilities I X. 1-X.19 I Network Aspects Maintenance X.90-X. 149 X. 150-X. 179 Model and Notation I Administrative Arrangements I X. 180-X. 199 I X.200-X.209 Service Definitions Connection-mode Protocol Specifications X.2 10-X.2 19 X.220-X.229 P

8、ICS Proformas Protocol Identification I Connectionless-mode Protocol Specifications I X.230-X.239 I X.240-X.259 X.260-X.269 Security Protocols Layer Managed Objects X.270-X.279 X.280-X.289 Conformance Testing INTERWORKING BETWEEN NETWORKS General Mobile Data Transmission Systems X.290-X.299 X.300-X.

9、349 X.350-X.369 Management MESSAGE HANDLING SYSTEMS X.370-X.399 X.400-X.499 DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS I OS1 MANAGEMENT I X.700-X.799 I x.500-x.599 I SECURITY I X. 800-X.849 Networking X. 600-X.649 I Commitment, Concurrency and Recovery I X. 850-X. 859 I Naming, Addressing and Regis

10、tration Abstract Syntax Notation One (ASN. 1) X.650-X.679 X.680-X.699 Transaction Processing Remote Operations OPEN DISTRIBUTED PROCESSING _ X. 860-X. 879 X.880-X.899 X.900-X.999 _ ITU-T RECMNMX.790 95 W 4862591 Ob07791 1T2 W CONTENTS scope 1.1 Functionality . 1.2 Field of application . 1.3 Document

11、 structure . Normative References 2.1 Identical Recommendations 1 International Standards 2.2 Paired Recommendations I International Standards equivalent in technical content 2.3 Additional References Definitions Abbreviations . Conventions 5.1 Use of graphic string syntax . 5.2 Use of list in attri

12、bute labels . 5.3 Labelling conditional packages 5.4 Describing parameters in primitives . Requirements 6.1 Trouble management report creation 6.2 6.3 6.4 Tracking trouble management reports Management of trouble management reports . Trouble management report clearing and closure . Model description

13、 . 7.1 Introduction 7.1.1 Instantiation of troubles reports 7.1.2 An overview of the trouble management objects model . 7.1.3 Trouble report states and status . Model components generic definitions . 7.2.1 Object class definitions . 7.2.2 Attribute type definitions 7.2.3 Error messages 7.2 Service d

14、escription . 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 Introduction Kernel functional unit . 8.2.1 Enter Trouble Report 8.2.2 Request Trouble Report Status . Request Trouble Report Format Functional Unit . Trouble History Event Notification Functional Unit 8.4.1 Trouble History Event Notification 8.4.2 Pa

15、rameters . Review Trouble History Functional Unit . Add Trouble Information Functional Unit Trouble Report Status/Commitment Time Update Notification Functional Unit . 8.7.1 Trouble Report Status/Commitment Time Update Notification . Verify Repair Completion Functional Unit Modify Trouble Administra

16、tion Information Functional Unit . Recommendation X.790 (11/95) Page 1 1 1 2 2 2 3 3 4 6 7 7 7 7 7 7 7 9 9 10 11 11 11 11 15 16 17 23 34 34 34 36 36 36 36 37 37 37 38 38 38 38 39 39 1 . ITU-T RECMN*X*790 95 4862591 Ob07792 039 9 10 11 8.10 8.1 1 8.12 8.13 8.14 8.15 8.16 8.17 8.18 8.19 8.20 Trouble A

17、dministration Configuration Event Notification Functional Unit . 8.10.1 Attribute Value Change Notification 8.10.3 Object Deletion Notification . Trouble Report Progress Notification Functional Unit . 8.1 1.1 8.1 1.2 Parameters . 8.10.2 Object CreationNotification Trouble Report Progress Notificatio

18、n . Cancel Trouble Report Functional Unit Extended Modi Trouble Administration Information Functional Unit . Delete Telecommunications Trouble Report functional unit Refer Telecommunications Trouble Report functional unit . Transfer Telecommunications Trouble Report functional unit . Update State an

19、d Status functional unit Repair Activity Object Functional Unit Provider Trouble Report Control Functional Unit Summary of functional units . Service mapping to Protocol 9.1 Element of procedure 9.1.1 Trouble History Event Notification Service procedures . 9.1.2 Trouble Report Progress Notification

20、Service procedures List of items having templates in Annex A and Recommendation X.721 9.2.1 Objects 9.2.2 Attributes . 9.2.3 Notifications 9.2.4 Actions 9.3 Negotiation of functional units . Relationship with other Standards Conformance 11.1 Static conformance . 1 1.2 Dynamic conformance 1 1.3 11.4

21、11.5 9.2 Management implementation conformance statement requirements Conformance to the general purpose platform profile for CCITT Rec . X.733 I ISO/IEC 10164-4 Conformance to support managed object definition . Annex A . Managed objects . Managed object class and package definitions . A.l.l Accoun

22、t . A.1.2 cnmservice A.1.3 contact . A.1.4 providerTroubleReport . A . 1.5 repairActivity A . 1.6 service . A.l A . 1.7 telecommunicationsTroubleReport . A.1.8 troubleHistoryRecord A . 1.9 troubleReport A.l.10 troubleReportFormatDefn . ii Recommendation X.790 (11/95) Page 40 40 40 41 41 41 41 41 42

23、42 42 42 43 43 43 43 45 45 45 47 50 50 50 53 54 54 55 55 55 55 55 56 56 57 57 57 57 58 60 61 62 63 68 70 72 ITU-T RECMNrX.790 95 111 4862591 Ob07793 T75 W A.2 Attribute definitions A.2.1 A.2.2 A.2.3 A.2.4 A.2.5 A.2.6 A.2.7 A.2.8 A.2.9 A.2.10 A.2.11 A.2.12 A.2.13 A.2.14 A.2.15 A.2.16 A.2.17 A.2.18 A.

24、2.19 A.2.20 A.2.21 A.2.22 A.2.23 A.2.24 A.2.25 A.2.26 A.2.27 A.2.28 A.2.29 A.2.30 A.2.3 1 A.2.32 A.2.33 A.2.34 A.2.35 A.2.36 A.2.37 A.2.38 A.2.39 A.2.40 A.2.41 A.2.42 A.2.43 A.2.45 A.2.46 A.2.47 A.2.48 A.2.49 A.2.50 A.2.5 1 A.2.52 A.2.53 A.2.54 A.2.55 A.2.56 A.2.57 A.2.58 A.2.59 A.2.60 A.2.61 Accoun

25、t contact list . Account name . Activity code . Activity duration . Activity info Activity person Additional text Additional trouble info list Additional trouble status info After hrs repair auth Agent contact object ptr Alternate manager contact person . Alternate manager contact object ptr Applica

26、ble managed object class list Applicable managed object instance list . Authorization list Begin time . Call back info list Called number . Cancel requested by manager . Close out naTT Commitment time . Commitment time request . Contact company Contact details . Contact function Contact id Contact n

27、ames . Contact object ptr list Contact type Close out verification Cust trouble tick num Customer work center . Dialog Electronic mail address . End time Escalation list Facsimile telephone number list Hand off center . Hand off location Hand off person name . Hand off time . Last update time A loca

28、tion access address Z location access address A location access hours . Z location access hours . A location access person . Z location access person . Maintenance org contact name . Maintenance org contact ptr Maintenance org contact time . Maint service charge . Managed object access from time . M

29、anaged object access hours Agent contact person . Alarm record ptr list Entry time Hand off person ptr . Initiating mode Recommendation X.790 (11/95) Page 73 73 73 73 73 73 73 73 73 74 74 74 74 74 74 74 75 75 75 75 75 75 75 75 75 76 76 76 76 76 76 76 76 76 77 77 77 77 77 77 77 77 77 78 78 78 78 78 7

30、8 78 78 78 79 79 79 79 79 79 79 79 79 . 111 A.2.62 A.2.63 A.2.64 A.2.65 A.2.66 A.2.61 A.2.68 A.2.69 A.2.10 A.2.11 A.2.12 A.2.13 A.2.14 A.2.75 A.2.16 A.2.77 A.2.18 A.2.19 A.2.80 A.2.81 A.2.82 A.2.83 A.2.84 A.2.85 A.2.86 A.2.87 A.2.88 A.2.89 A.2.90 A.2.91 A.2.92 A.2.93 A.2.94 A.2.95 A.2.96 A.2.91 A.2.

31、98 A.2.99 Managed object access to time Managed object instance . Manager contact person Manager search key1 Manager search key2 Managed object instance alias list . Manager contact object ptr Manager search key3 Manager search key list . perceived trouble severity . Received time Related trouble re

32、port list Outage duration . Preferred priority . Repair activity . Repair activity list . Repeat report . Responsible person ptr Responsible person name Restored time Service alias list Service description Service location list . Service Id Supported service name list Suspect object list . Telephone

33、 number list . Trouble clearance person Trouble detection time Trouble found . Trouble location Tr constrained to single value attr id list . Tr format id . Trouble report id . Tr must be present attr id list Tr may be present attr id list . Service type . Trouble report format object ptr . A.2.100

34、Trouble report number list A.2.101 Trouble report state . A.2.102 Trouble report status . A.2.103 Trouble report status time . A.2.104 Trouble report status window . A.2.105 Trouble type A.2.106 Tsp priority . A.2.107 Type text . A.2.108 Unavailable service ptr A.3 Error messages A.3.1 Trouble Repor

35、t Already Exists . A.3.3 Can Not close A.3.4 Trouble Report Must Be Present Attribute Missing A.3.5 Cannot Veri or Deny at This Time A.3.6 Trouble Report Change Denied A.3.2 Fallback Reporting Page 80 80 80 80 80 80 80 80 81 81 81 81 81 81 81 81 82 82 82 82 82 82 82 82 83 83 83 83 83 83 83 83 84 84

36、84 84 84 84 84 84 84 85 85 85 85 85 85 85 85 85 86 86 86 86 iv Recommendation X.790 (11/95) - ITU-T RECMN*X.790 95 m 48b259L Ob07795 848 = A.4 Events . AS Name Bindings . A.6 Abstract syntax . A.6.1 A.7 Rules of extensibility Appendix I - Scenarios . 1.1 Introduction I . 1.1 Trouble management envir

37、onment . 1.1.2 Trouble management roles Creation of a trouble rep0 rt . 1.2 1.3 Processing and tracking of the trouble report . 1.3.1 Clearing of the trouble report 1.3.2 Closure of the trouble rep0 rt . 1.3.3 Cancelling of the trouble report 1.4 History notification . Appendix II -Further work . II

38、 . 1 Additional requirements not met in this Recommendation . II.2 Future work . Appendix III - Overview of the service model . Appendix IV - Trouble report format examples . Appendix V . Page 86 86 89 89 102 103 103 103 103 104 105 105 105 105 105 106 106 106 106 108 110 Recommendation X.790 (11195

39、) V SUMMARY This Recommendation is concerned with the management of malfunction in systems and communications networks from the perspective of a provider of service and user of that service. In the Recommendation these malfunctions are referred to as “troubles“. A report format is defined to allow a

40、 user to report a trouble, which will then be progressed to resolution by a provider. During the resolution by the service provider, the service user may determine the current state of resolution by issuing a request for this information. When cleared the provider may notify the user. Particular typ

41、es of troubles are included; however, the use of this Recommendation by a particular application may require trouble types specific to that application to be used - this is catered for in this Recommendation. vi Recommendation X.790 (11/95) ITU-T RECMN*X-790 95 m LiBb259L Ob07797 bLO m Recommendatio

42、n X.790 TROUBLE MANAGEMENT FUNCTION FOR ITU-T APPLICATIONS (Geneva, 1995) 1 Scope From time to time all systems, including communications networks, develop problems or malfunctions referred to in this Recommendation as ?troubles?. A ?trouble? in a communications network is a problem that has an adve

43、rse effect on the quality of service perceived by network users. When a trouble is detected, possibly as a result of an alarm report, a trouble report may be entered by a user or the system may raise a report automatically. Management of that trouble report is necessary to ensure that it receives at

44、tention and that the trouble is cleared to restore the service to its previous level of capability. At the time of a trouble, a network may have been interworking with another network to provide a service, and the problem or malfunction may be due to the other network. Therefore it may be necessary

45、to exchange trouble management information between management systems across interfaces which may be client to service provider or service provider to service provider interfaces and may represent inter-jurisdictional as well as intra-jurisdictional boundaries. In addition to exchanging information

46、on trouble that has already been detected, advance information on service inaccessibility may also need to be exchanged. Thus, a service provider may need to inform a customer of future service inaccessibility (because of planned maintenance, for example). The scope of this Recommendation includes a

47、ll of the above processes for exchange of management information. 1.1 Functionality This Recommendation specifies the Trouble Management functionality for: Reporting of troubles on services or resources on a managed network or system; Tracking the progress of trouble to resolution; Clearing and clos

48、ure of trouble. In a network environment this encompasses computer networks, data networks and telephony networks. This Recommendation defines a trouble management model, application services and a number of objects and their attributes that are necessary for trouble management. Requirements for the

49、 detection of a trouble, that is to say any cause that may lead to or contribute to a manager perceiving a degradation in the quality of service of one or more network services or one or more network resources being managed, are outside the scope of this Recommendation. 1.2 Field of application In general, trouble management is the trouble reporting and tracking between Conformant Management Entities (CMEs) interoperating Co-operatively towards resolution of a trouble. (No distinction is made between inter-jurisdictional and intra-jurisdictio