ITU-T X 790 AMD 1-1996 Trouble Management Function for ITU-T Applications - Series X Data Networks and Open System Communication - OSI Management - Management Functions (Amendment rm.pdf

《ITU-T X 790 AMD 1-1996 Trouble Management Function for ITU-T Applications - Series X Data Networks and Open System Communication - OSI Management - Management Functions (Amendment rm.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 790 AMD 1-1996 Trouble Management Function for ITU-T Applications - Series X Data Networks and Open System Communication - OSI Management - Management Functions (Amendment rm.pdf（133页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.790 Amendment I (1 0/96) SERIES X: DATA NETWORKS AND OPEN SYSTEM COM M U N I CATI ON OS1 management - Management functions Trouble management function for ITU-T appl cations Amendment I : Implementation con

2、formance statements proformas ITU-T Recommendation X.790 - Amendment I (Previously CCITT Recommendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATION PUBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maintenan

3、ce Administrative arrangements 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 ME

4、SSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS OPEN SYSTEM INTERCONNECTION INTERWORKING BETWEEN NETWORKS Networking Efficiency Naming, Addressing and Registration Abstract Syntax Notation One (ASN. 1) OS1 MANAGEMENT Systems Management framework and architecture Management Communi

5、cation Service and Protocol 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.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.290-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

6、.600-X.629 X.630-X.649 X.650-X.679 X.680-X.699 X.700-X.799 X.700-X.709 X.710-X.719 Structure of Management Information X.720-X.729 SECURITY OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X.800-X. 849 X.850-X.899 X.850-X.859

7、X.860-X.879 X.880-X.899 X.900-X.999 For firrther details, please refer to ITU-T List of Recommendations. FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (I). The ITU-T is responsible for studying technical, operating and

8、 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 the topics for study by the ITU-T Study Groups which, in their turn,

9、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). Amendment 1 to ITU-T Recommendation X.790, was prepared by ITU-T Study Group 7 (1993-1996) and was approve

10、d 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 adminisration and a recognized operating agency. O ITU 1997 All rights reserved. No part of this publicati

11、on may be reproduced or utilized in any fonn or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the IT, except as noted in footnotes 4) and 5) in Annex B. Recommendation X.790/Amd.l (10/96) 1 CONTENTS 3 Definitions 11 Conformance Annex

12、 B - MCS proforma MOCS proforma B1 B2 B3 B4 B5 B7 B8 B9 B10 11 account . cnmService . contact providerTroubleReport . repairActivity . telecommunicationsTroubleReport troubleHistosrRecord . troubleReport troubleReportFormatDefn Recommendation X.790/Amd.l (10/96) Page 1 5 6 13 13 17 28 39 53 71 95 10

13、2 117 SUMMARY Recommendation X.790 provides many possible options for implementors to choose fiom in the development of a product, This means that an Operations System (OS) product fiom one vendor needing to interwork with an OS product fiom another vendor must be developed to some common and explic

14、it agreement both developers use concerning the actual options to be developed in their software products for X.739 based messages. This amendment provides a means to specify message options in such a way that the later documentation of actual options chosen for product can be more explicit. The res

15、ult is that the time to carry out interoperability test between an OS from one vendor and an OS fiom another vendor may be reduced because product developers can be provided with more explicit message specification. . Recommendation X.790/Amd.l (10/96) 111 STD=ITU-T RECMN X.790 AMD 1-ENGL L97b 48b25

16、7L Ob315PO 331 = Amendment 1 to Recommendation X.790 TROUBLE MANAGEMENT FUNCTION FOR ITU-T APPLICATIONS AMENDMENT 1 Implementation conformance statements proformas (Geneva, 1996) 1) Replace clause 3 with the following: 3 Definitions For the purposes of this Recommendation, the following definitions

17、apply: 3.1 ASN.l definitions This Recommendation makes use of the following term defined in CCITT Rec. X.208 and IS0 8824: - object identifier. 3.2 Management framework definitions This Recommendation makes use of the following term defined in CCITT Rec. X.700 and ISOAEC 7498-4: - managed object. 3.

18、3 Conformance testing methodology definitions This Recommendation makes use of the following terms defined in IT-T Rec. X.290 and ISO/IEC 9646-1: a) b) PICS proforma; c) system conformance statement. Protocol Implementation Conformance Statement (PICS); 3.4 Systems management overview definitions Th

19、is Recommendation makes use of the following terms defined in CCITT Rec. X.701 I ISOAEC 10040, with the exceptions as indicated: a) agent; b) managed object class; c) managed object conformance statement; d) manager; e) MOCS proformas; f) notification. The definition of the term “agent” in CCITT Rec

20、. X.701 I ISO/IEC 10040 is used with the following restriction. With respect to a particular telecommunications service (or resource) instance, it shall be possible to manage the service with one system playing the manager role, and the other playing the agent role. The definition of the term “manag

21、ei in CCITT Rec. X.701 I ISOAEC 10040 is used with the following restriction. With respect to a particular telecommunications service (or resource) instance, it shall be possible to manage the service with one system playing the manager role, and the other playing the agent role. Recommendation X.79

22、0/Amd.l (10/96) 1 STD.ITU-T RECMN X=770 AMD 1-ENLL 177b iidb257L Ob3l1521 278 m 3.5 CMIS definitions This Recommendation makes use of the following terms defined in CCITT Rec. X.710 and ISOAEC 9595: a) attribute; b) attribute type; e) attribute value. 3.6 Management information model definitions Thi

23、s Recommendation makes use of the following terms defined in CCITT Rec. X.720 1 ISOhEC 10165-1: a) action; b) behaviour; e) characteristic; d) conditional package; e) instantiation; f) name binding; 9 package; h) parameter; i) superclass. 3.7 This Recommendation makes use of the following term defin

24、ed in CCITT Rec. X.722 I ISO/IEC 10165-4: Guidelines for the definition of managed objects definitions - template. 3.8 Implementation conformance statements definitions This Recommendation makes use of the following terms defined in ITU-T Rec. X.296 and ISO/IEC 9646-7: a) (ICs) item; b) (ICs) questi

25、on; e) status (vaiue); d) (support) answer. 3.9 This Recommendation makes use of the following terms defined in IIZT-T Rec. X.724 I ISOAEC 10165-6: Implementation conformance statement proforma definitions a) b) Management Conformance Summary (MCS); e) MCS proforma; d) MRCS proforma. Managed Relatio

26、nship Conformance Statement (MRCS); 3.10 Additional definitions For the purpose of this Recommendation, the following definitions apply. 3.10.1 identified (usually by the customer). alias: Another name, besides the object identifier, by which a trouble report may be known, referenced or 2 Recommenda

27、tion X.790/Amd.l (1 0/96) 3.10.2 application entity: The aspects of an application process pertinent to OSI. 3.10.3 exchange of application protocol control information through their use of presentation services. application association: A cooperative relationship between two application entities, f

28、ormed by their 3.10.4 other necessary information for the interworking of application entities on an application association. application context: An explicitly identified set of application service elements, related options, and any 3.10.5 associated alarms: Alarms directly related to a given ident

29、ified trouble. 3.10.6 cancelled: A manager can request the agent to “cancei” a trouble report. The manager wants to abort this trouble report (either because it was entered in error or because there is no longer any trouble condition). Under certain conditions (e.g. the trouble has not been dispatch

30、ed or tested), the agent will “cancel” the trouble report by updating its status to “closed-out by customer request.” “Cancelling” a trouble report may also have business ramifications beyond the scope of this Recommendation (e.g. whether the customer must pay for the trouble report). 3.10.7 clearin

31、g trouble reports: An assertion by an agent that actions which are identified in the trouble report or the repair activity object instances have been satisfactorily performed to resolve the trouble, or that such actions are no longer necessary, such that in either case the trouble report is a candid

32、ate for closure. 3.10.8 client: User of a service provided by a system or a network. 3.10.9 closed-out: A trouble report is considered “cloed-out when the agent determines that the reported trouble has either been cleared or no longer exists, and the agent updates the trouble report status to indica

33、te the trouble report is “closed-out”. Only an agent can change the trouble report status to “cloedOut. The status of a trouble report might change to “closedOutJ3yCustReq” as a result of a request to cancel the trouble report fi-om the manager. 3.10.10 closing trouble reports: An assertion by an Ag

34、ent that the trouble is resolved such that the cleared trouble report may only be processed further to generate a trouble history record and/or be deleted. 3.10.11 conformant management entity: A real open system which supports the interoperable interface defined in this Recommendation. 3.10.12 cont

35、act: A person who can provide additional information about the trouble on behalf of the manager or the agent. 3.10.13 customer: The customer is an user of telecommunications services provided by a service provider. Specifically, in the context of this Recommendation, the customer is a user who choos

36、es to use the OS (Operations System) -to-OS-OS1 interface for network management across jurisdictions in order to achieve control of the telecommunication services (or resources) being used. The customer (or customer representative) acts in the manager role. There is no requirement that the interfac

37、e be confined to cases where there is a traditional telecommunication service customer to service provider relationship between the parties. Two telecommunication service providers (carriers) may use this interface to exchange trouble reports in situations where their networks interwork in order to

38、provide service to an end user. In that case, the Customer role may change from situation to situation. However, in any particular situation, one carrier will be the customer who will act in the manager role, while the other will be the supplier and will act in the agent role. 3.10.14 defer: To post

39、pone work on, or set aside, a trouble report until such time as when appropriate conditions are met and it can be progressed further. 3.10.15 event: An instantaneous occurrence that changes the global status of an object. This status change may be persistent or temporary, thus allowing for surveilla

40、nce, monitoring, and performance measurement functionality, etc. Events may or may not generate reports; they may be spontaneous or planned; they may trigger other events or may be triggered by one or more other events. I 3.10.16 attention to resolve the trouble. escalating a trouble report: Identif

41、jing a trouble report which is to receive urgent and immediate supervisory 3.10.17 fault management: Fault Management consists of a set of functions that enable the detection, isolation, and correction of abnormal operation of the telecommunications network and its environment. Recommendation X.79O/

42、Amd.l (10196) 3 STD.ITU-T RECMN X.770 AND 1-ENGL 177b = q8b2591 Ob31523 O40 W 3.10.18 jurisdiction: This refers to the functional separation of telecommunications networks. A jurisdiction is one of the following four types: - Local Exchange Carrier Network; - Interexchange Carrier Network; - End Use

43、r Network; - Some combination of the above. 3.10.19 outage: Unavailability of a service or resource. 3.10.20 perceived severity: The seriousness of the problem as seen by the person reporting the trouble. 3.10.21 priority: The degree of urgency with which the manager requires resolution of the probl

44、em. 3.10.22 service: This term represents telecommunication capabilities that the customer buys or leases fiom a service provider. Service is an abstraction of the network-element-oriented or equipment-oriented view. Identical services can be provided by different network elements, and different ser

45、vices can be provided by the same network elements. 3.10.23 service provider: A system or a network that provides a telecommunication service to a customer. In the context of this Recommendation, a service provider is specifically a provider of telecommunication services who offers the OS-to-OS-OS1

46、interface to allow a customer the capability for network management across jurisdictions in order to control the services (or resources) being provided (see Customer). A service provider acts in the agent role. There is no requirement that the interface be confined to cases where there is a traditio

47、nal telecommunication service customer to telecommunication service provider relationship between the parties. It is certainly possible that two telecommunication carriers, whose networks interwork to provide a telecommunications service to an end user, may use this interface. In that case, the cust

48、omer and service provider roles may change from situation to situation. However, in any particular situation, one carrier will be the customer and have the manager role, while the other will be the supplier, and will have the agent role. 3.10.24 status of a trouble report: The stage that has been re

49、ached by a trouble report since its instantiatiodcreation while the trouble is being resolved. 3.10.25 time-stamp: A time value used to indicate when a particular activity, action or an occurrence of an event took place. 3.10.26 trouble: 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. 3.10.27 trouble administration: Trouble Administration consists of a set of functions that enable troubles to be reported and their status tracked. Trou