ITU-T X 791-1996 Profile for Trouble Management Function for ITU-T Applications - Series X Data Networks and Open System Communication OSI Management - Management Functions《ITU-T应用.pdf

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUN CATION STANDARDIZATION SECTOR OF ITU X.791 (1 0/96) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUN I CATI ON OS1 management - Management functions Profile for trouble management function for ITU-T applications ITU-T Recommendation X.791 (Previou

2、sly CCITT Recommendation) STD-ITU-T RECMN X.791-ENGL 199b = 48b2571 Ob37b27 O10 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATION PUBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maintenance Administrative arrange

3、ments Model and notation Service definitions Connection-mode protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing General Satellite data transmission systems MESSAGE HANDLING SYSTEMS DI

4、RECTORY OS1 NETWORKING AND SYSTEM ASPECTS OPEN SYSTEM INTERCONNECTION INTERWORKING BETWEEN NETWORKS Networking Efficiency Naming, Addressing and Registration Abstract Syntax Notation One (ASN. 1) Systems Management framework and architecture Management Communication Service and Protocol Structure of

5、 Management Information Management functions OS1 MANAGEMENT SECURITY OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X.1-X.199 X.1-X.19 X.20-X.49 X.50-X.89 X.90-X. 149 X. 150-X. 179 X.180-X.199 X.200-X.299 X.200-X.209 X.210-X

6、.219 X.220-X.229 X.230-X.239 X.240-X.259 X.260-X.269 X.270-X.279 X.280-X.289 X.29-X.299 X.300-X.399 X .300-X .349 X.350-X.399 X .400-X .499 X.500-X.599 X.600-X.699 X .600-X. 629 X.630-X.649 X.650-X.679 X.680-X.699 X.700-X.799 X.700-X.709 X.7 1 0-X.7 1 9 X.720-X.729 x.730-x.799 X.800-X.849 X. 850-X.

7、899 X.850-X.859 X.860-X.879 X.880-X.899 X.900-X.999 For further detaiis, please refer to ITU-T List of Recommendations. STD-ITU-T RECMN X-79L-ENGL 297b 48b2571 Ob37b28 T57 FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union

8、(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 basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes

9、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 (Helsinki, March 1-12, 1993). ITU-T Recommendation X.791 was prepar

10、ed by ITU-T Study Group 7 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 5th of October 1996. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O I

11、TU 1997 All 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 permission in writing from the ITU, except as noted in footnotes 4) and 5) in Annex B. Recommendation X.791 (109

12、6) 1 STD-ITU-T RECMN X.79L-ENGL 199b m qBb259L Ob37b29 993 W 1 2 3 4 5 6 7 8 11 CONTENTS Scope 1.1 Functionality . 1.2 Field of application . Normative references . 2.1 Identical Recommendations I International Standards 2.2 Paired Recommendations I International Standards equivalent in technical co

13、ntent 2.3 Additional references Definitions 3.1 ASN.l definitions . 3.2 Management framework definitions . 3.3 Conformance testing methodology definitions . 3.4 Systems management overview definitions 3.5 CMIS definitions 3.6 Management information model definitions . 3.7 Guidelines for the definiti

14、on of managed objects definitions . 3.8 Implementation conformance statements definitions 3.9 Implementation conformance statement proforma definitions . 3.10 Additional definitions . Abbreviations . Conventions 5.1 Use of graphic string syntax . 5.2 Use of list in attribute labels . 5.3 Labelling c

15、onditional packages 5.4 Describing parameters in primitives . Requirements 6.1 Trouble management report creation 6.2 Tracking trouble management reports 6.3 Management of trouble management reports 6.4 Trouble management report clearing and closure . Model description . 7.1 Introduction . 7.2 Model

16、 components generic definitions . Service description . 8.1 Introduction 8.2 Kernel functional unit . 8.3 Request Trouble Report Format Functional Unit . 8.4 Trouble History Event Notification Functional Unit 8.5 Review Trouble History Functional Unit . 8.6 Add Trouble Information Functional Unit 8.

17、7 Trouble Report StatusCommitment Time Update Notification Functional Unit . 8.8 Ven Repair Completion Functional Unit . 8.9 Modi Trouble Administration Information Functional Unit . 8.1 O Trouble Administration Configuration Event Notification Functional Unit . Recommendation X.791 (10/96) Page 1 1

18、 1 2 2 3 3 3 3 3 3 3 4 4 4 4 4 5 7 8 8 8 8 8 8 8 10 11 12 12 12 18 36 36 37 38 38 39 39 40 40 41 41 9 10 11 8.11 8.12 8.13 8.14 8.15 8.16 8.17 8.18 8.19 8.20 Trouble Report Progress Notification Functional Unit . Cancel Trouble Report Functional Unit Extended Modify Trouble Administration Informatio

19、n Functional Unit . Delete Telecommunications Trouble Report functional unit Refer Telecommunications Trouble Report functional unit . Transfer Telecommunications Trouble Report functional unit . Update State and Status functional unit Repair Activity Object Functional Unit Summary of functional uni

20、ts . Provider Trouble Report Control Functional Unit Service mapping to Protocol 9.1 Element of procedure List of items having templates in Annex AK.790 and Recommendation X.721 . Negotiation of functional units . 9.2 9.3 Relationship with other Standards Conformance 11.1 Static conformance . 11.2 D

21、ynamic conformance 1 1.3 Management implementation conformance statement requirements Annex B MCS proforma BO.l B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 Introduction B0.2 Identification of the implementation . B0.3 Identification of the Recommendations I International Standards in which the management informa

22、tion is defined . B0.4 Management conformance summary account cnmService . contact providerTroubleReport . repairActivity : telecommunicationsTroubIeReport troubleHistoryRecord . troubleReport troubleReportFormatDefn Recommendation X.791 (10/96) Page 42 43 43 44 44 44 44 45 45 45 46 46 51 54 55 56 5

23、6 56 56 57 57 57 58 58 63 66 76 84 95 100 109 126 131 142 . 111 STD-ITU-T RECMN X-77l-ENGL L97b = 48b2573 Ob37b32 541 SUMMARY This Recommendation defines a piofile of options, from those in Recommendation X.790Amd. 1, using the document structure defined in Amendment 1 to Recommendation X.790. The p

24、rofile is concerned with general trouble management capability and provides an implementation definition for developers to design their software product to. The profile may be used by network operator personnel to speci the precise trouble management capability required, knowing that product vendor

25、can or has used the definition for product development. iv Recommendation X.791 (10/96) STD.ITU-T RECMN X.79L-ENGL L79b 48b2571 Ob37b32 488 D Recommendation X.791 PROFILE FOR TROUBLE MANAGEMENT FUNCTION FOR ITU-T APPLICATIONS (Geneva, 1996) 1 Scope From time to time all systems, including communicat

26、ions networks, develop problems or malfunctions referred to in this Recommendation as ?troubles?. A ?trouble? in a communications network is a problem that has an adverse effect on the quality of service perceived by network users. When a trouble is detected, possibly as a result of an alarm report,

27、 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 attention and that the trouble is cleared to restore the service to its previous level of capability. At the time of a trouble, a netwo

28、rk 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 to exchange trouble management information between management systems across interfaces which may be client to service provider or se

29、rvice provider to service provider interfaces and may represent inter-jurisdictional as well as intra-jurisdictional boundaries. In addition to exchanging information on trouble that has already been detected, advance information on service inaccessibility may also need to be exchanged. Thus, a serv

30、ice provider may need to inform a customer of future service inaccessibility (because of planned maintenance, for example). The scope of this Recommendation includes all of the above processes for exchange of management information. 1.1 Functionaliy This Recommendation specifies the Trouble Manageme

31、nt functionality for: Reporting of troubles on services or resources on a managed network or system; Tracking the progress of trouble to resolution; Clearing and closure of trouble. In a network environment this encompasses computer networks, data networks and telephony networks. This Recommendation

32、 defines a trouble management model, application services and a number of objects and their attributes that are necessary for trouble management. Requirements for the 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

33、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 cooperat

34、ively towards resolution of a trouble. (No distinction is made between inter-jurisdictional and intra-jurisdictional interfaces.) A trouble report gets instantiated for this purpose. In cases where CMEs are interoperating cooperatively towards the resolution of a trouble, it means that both manager

35、and agent CME may have a shared responsibility for resolution of trouble. The trouble management function Recommendation is one that may be used by a CME acting in: 1) a manager role to manage trouble(s) and any corresponding trouble report(s) that have been raised to an agent role CME for resolutio

36、n; an agent role responsible for resolving trouble(s) and any corresponding trouble report(s) that have been raised to it by a manager role CME; 2) Recommendation X.791 (1 0196) 1 STD.ITU-T RECMN X-771-ENGL L99b = 48b2571 Ob37633 314 m 3) both an agent and manager role to manage trouble(s) and any c

37、orresponding trouble report(s) that have been raised internally (ie. to the part performing the agent role), by another part of itself performing the manager role. In this case, the CME itself is responsible for resolving the trouble, but in addition, the CME may also inform other manager role CMEs

38、that are part of the cooperating networks, if they are liable to be affected by the trouble or can help with trouble resolution. The actual means and methods by which the manager perceives the trouble in the first place and the means and methods employed by the agent for detection and identification

39、 of the trouble are outside the scope of this Recommendation. 2 Normative references The following Recommendations 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 vali

40、d. All Recommendations and other references are subject to revision: ail users of this Recommendation are therefore 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 Recommendati

41、ons is regularly published. 2.1 Identical Recommendations I International Standards - ITU-T Recommendation X.2 1 O (1 993) I ISOIIEC 1073 1 : 1994, Information technology - Open Systems Interconnection - Basic Reference Model: Conventions for the definition of OSI services. - ITU-T Recommendation X.

42、217 (1995) 1 ISO/IEC 8649:1996, Information technology - Open Systems Interconnection - Service definition for the association control service element. - ITU-T Recommendation X.680 (1994)/Amd.1 (1995) I ISOflEC 8824-1:1995/Amd.1:1995, Information technology - Abstract Syntax Notation One (ASN.1): Sp

43、ecification of basic notation - Amd. I: Rules of extensibility. - CCITT Recommendation X.701 (1992)ICor.l (1992)/Cor.2 (1995) 1 ISOIIEC 10040:1992/Cor.l: 1994fCor.2: 1995, Information technology - Open Systems Interconnection - Systems management overview. - CCITT Recommendation X.72 1 (1 992)ICor.

44、1 (1 994) 1 ISOflEC 1 O 165-2: 1992ICor. 1 : 1994, Information technology - Open Systems Interconnection - Structure of management information: Definition of management information. - CCITT Recommendation X.722 (1992) 1 ISOhEC 10165-4:1992, Information technology - Open Systems Interconnection - Str

45、ucture of management information: Guidelines for the definition of managed objects. - ITU-T Recommendation X.724 (1996) I ISOAEC 10165-6:1997, Information technology - Open Systems Interconnection - Structure of management information: Requirements and guidelines for implementation conformance state

46、ment proformas associated with OSI management. - CCITT Recommendation X.730 (1992) I ISOIIEC 10164-1:1993, Information Technology - Open Systems Interconnection - Systems management: Object management jnction. - CCITT Recommendation X.73 1 (1 992)ICor. 1 (1995) 1 ISOflEC 1 O 164-2:1992/Cor. 1 : 1995

47、, Information technology - Open Systems Interconnection - Systems management: State management function. - CCITT Recommendation X.734 ( 1992)/Cor. 1 (1 994) 1 ISOIIEC 1 O 164-5: 1993ICor. 1 : 1994, Information technology - Open Systems Interconnection - Systems management: Event report management fu

48、nciion. - CCITT Recommendation X.735 (1992) 1 ISO/IEC 10164-6:1993, Information technology - Open Systems Interconnection - Systems management: Log control function. - ITU-T Recommendation X.741 (1995) 1 ISOIEC 10164-9:1995, Information technoogv - Open Systems interconnection - Systems management:

49、Objects and attributes for access control. 2 Recommendation X.791 (10/96) 2.2 Paired Recommendations I International Standards equivalent in technical content - CCITT Recommendation X.209 (1988), Specifcation of basic encoding rules for Abstract Syntax Notation One (ASN. 1). ISO/IEC 8825: 1990, Information technology - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1). CCITT Recommendation X.7 1 O ( 199 i), Common management information service definition for CCITT applications. ISO/IEC 9595: 199 1, Information t