ATIS 0300228-2011 OAM&P C Services for Interfaces Between Operations Systems Across Jurisdictional Boundaries to Support Fault Management (Trouble Administration).pdf

《ATIS 0300228-2011 OAM&P C Services for Interfaces Between Operations Systems Across Jurisdictional Boundaries to Support Fault Management (Trouble Administration).pdf》由会员分享，可在线阅读，更多相关《ATIS 0300228-2011 OAM&P C Services for Interfaces Between Operations Systems Across Jurisdictional Boundaries to Support Fault Management (Trouble Administration).pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD FOR TELECOMMUNICATIONS ATIS-0300228.2011 OAM their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The

2、American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American Nation

3、al Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Ins

4、titute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. Notice of Disclaimer they may be spontaneous or

5、 planned; they may trigger other events or may be triggered by one or more other events. 3.12 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. 3.13 Juris

6、diction: This refers to the functional separation of telecommunications networks. A jurisdiction is one of the following four types: 1. Local Exchange Carrier Network; 2. Interexchange Carrier Network; 3. End User Network; or 4. Some combination of the above. 3.14 Manager: The Systems Management Ove

7、rview (SMO), as defined in ISO/IEC 10040, but 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. 3.15 Service Provid

8、er: The service provider is anyone who offers the OS-to-OS OSI interface to allow network management across jurisdictions of telecommunications services (or resources) they provide. The service provider acts in the agent role. See customer. There is no requirement that the interface be confined to c

9、ases where there is a traditional telephone customer relationship between the parties. It is certainly the case that two carriers might use this interface. In that case, the customer role may change from time to time. However, such a relationship can be decomposed into two manageragent relationships

10、. 3.16 Trouble Administration: Trouble Administration consists of a set of functions that enable troubles to be reported and their status tracked. Trouble Administration services include request trouble report format, enter trouble report, add trouble information, cancel trouble report, request trou

11、ble report status, review trouble history, attribute value change notification (e.g., trouble report status/commitment time), object creation/deletion (trouble report), verify trouble repair completion, and modify trouble administration information. ATIS-0300228.2011 5 4 ABBREVIATIONS 2) Trouble Adm

12、inistration; and 3) Testing. Fault Management uses surveillance data collected on a set of services. The gathering and reporting of surveillance data is controlled by a set of generic functions. Fault Management functions for Customer ATIS-0300228.2011 6 Network Management interfaces include maintai

13、ning and examining error logs, reporting error conditions, managing trouble reports, and performing diagnostic tests. 6.2 Trouble Administration Functions The following list describes the trouble administration functions of Fault Management: a) enter trouble report: TMN gives notice to another TMN t

14、hat a service provided by that TMN is in need of repair. b) request trouble report status: TMN asks for status information on a previously entered trouble report. c) request trouble report format: TMN requests another TMN to provide a template for a trouble report for a particular service or class o

15、f services. This allows the originating TMN to know what attributes of a trouble report are considered mandatory or optional by the receiving TMN. d) trouble history event: TMN notifies the TMN that originated the trouble report that it has been closed out, or keeps the close out information in an i

16、nternal log. e) review trouble history: TMN asks for information about past troubles that it has reported. f) add trouble information: TMN adds information to a trouble report that it has entered. g) trouble report status update: TMN notifies the TMN that originated a trouble report that the status

17、of that trouble report has changed. h) trouble report commitment time update: TMN notifies the TMN that originated a trouble report that the commitment time for that trouble report has changed. i) trouble report attribute value change: TMN notifies the TMN that originated a trouble report that other

18、 attributes of interest for that trouble report have changed. j) enrol trouble report: TMN notifies the TMN that would normally originate a trouble report that a trouble report has been created, either as the result of a request or as a result of an internal action by the notifying TMN. k) deenrol t

19、rouble report: TMN notifies the TMN that would normally originate a trouble report that a trouble report has been deleted, either as the result of a request or as a result of an internal action by the notifying TMN. l) verify repair completion: This allows the TMN that originated a trouble report to

20、 verify that the repair has been completed to its satisfaction before the trouble report is closed out in the receiving TMN. m) modify other trouble report attributes: TMN modifies writable attributes of a trouble report that are not specifically covered in other functions. n) enrol Trouble Report F

21、ormat Definition: TMN notifies the TMN that would normally originate a trouble report that a Trouble Report Format Definition has been created. o) deenrol Trouble Report Format Definition: TMN notifies the TMN that would normally originate a trouble report that a Trouble Report Format Definition has

22、 been deleted. p) attribute value change Trouble Report Format Definition: TMN notifies the TMN that would normally originate a trouble report that a Trouble Report Format Definition attribute of interest has changed. q) trouble report progress update: TMN notifies the TMN that originated a trouble

23、report about progress on resolving the trouble. ATIS-0300228.2011 7 r) cancel trouble report: TMN gives notice to another TMN that a previously reported trouble is no longer of interest. 7 OBJECT CLASSES The CMISE service that it maps onto; and Restrictions (if any) on the usages of the CMIS paramet

24、ers. NOTE Detailed parameter descriptions are not included when the SET and GET services are used. ATIS-0300228.2011 9 The CMIS services, procedures, and parameters are defined in ISO/IEC 9595. The mapping of the following services to the confirmed or unconfirmed mode of the supporting CMISE service

25、s, except where specified, is a local implementation issue and is not specified by this standard. 9.1 Kernel Functional Unit The Kernel functional unit has the following capabilities: Entering Trouble Report; and Requesting Trouble Report Status. 9.1.1 Enter Trouble Report The PT-CREATE service, as

26、described in ISO/IEC 10164-1, is used to allow a manager to request that a trouble report be created by the agent with the appropriate information. The PT-CREATE service request is issued by the manager with the Telecommunications Trouble Report object class as the managed object class parameter. If

27、 the manager chooses not to use the reference object option, the manager shall supply the following attributes as part of the create operation: Managed Object Instance; Trouble Type; and Additional Trouble Information List; plus any manager-supplied attributes in conditional packages identified as “

28、must be present”. The manager also has the option to include manager-supplied attributes in conditional packages identified as “may be present” attributes. Administrations (Service Providers) shall state the required object classes on which troubles may be reported. If the input information is corre

29、ct, the agent will respond with the name (Trouble Report ID). The attribute list parameter is mandatory in the response for trouble reports that contain attributes (other than Trouble Report ID) supplied by the agent. The Enter Trouble Report service supports the following Error messages defined in

30、ATIS-0300227.2008: 1. Trouble Report Already Exists; and 2. Fall Back Reporting. ATIS-0300228.2011 10 9.1.2 Request Trouble Report Status The PT-GET service, as described in ISO/IEC 10164-1, is used to allow a manager to request status information on a trouble report. The manager issues a PT-GET aga

31、inst the Trouble Report Status attribute and the Trouble Report Status Time attribute in the Telecommunications Trouble Report object class. Other “readable” Telecommunications Trouble Report attributes may also be present in the request. For example, this service could also be used to query the sta

32、tus of more than one (potentially all) trouble reports for that manager. For example, a manager may wish to view all clearedAwaitingCustVerification trouble reports. By using the scoping and filtering capabilities of CMISE, the managing system could get the trouble report status of all its trouble r

33、eports where the state is not closed. 9.2 Request Trouble Report Format Functional Unit The PT-GET service, as described in ISO/IEC 10164-1, is used to allow a manager to determine the format for reporting troubles on either a CNM Service or a GNIM object representing a telecommunications network re

34、source. Based on the trouble report format, the manager supplies a different set of attributes when entering a trouble report (see Enter Trouble Report service). The Telecommunications Trouble Report attributes that the manager must supply are determined by a PT-GET on the tRMustSupplyAttrIDList att

35、ribute in the appropriate instance of the Trouble Report Format Definition object. The Telecommunications Trouble Report attributes that the manager may choose to supply are determined by a PT-GET on the tRMaySupplyAttrIDList attribute in the appropriate instance of the Trouble Report Format Definit

36、ion object. The appropriate instance of the Trouble Report Format Definition object is determined by either: a) A PT-GET on the Trouble Report Format Pointer attribute in the CNM Service object (when the format must be defined on an object instance basis); b) A scoped and filtered PT-GET of the Trou

37、ble Report Format Definition object for values of the Applicable Managed Object Classes attribute that match the CNM Service or GNIM object class (when the format is the same for an entire object class); or c) A scoped and filtered PT-GET of the Trouble Report Format Definition object for values of

38、the Applicable Managed Object Instances attribute that match the GNIM object instance (when the format is specific to the object instance). ATIS-0300228.2011 11 Table 2 - Trouble History Event Notification Service Parameters Parameter name Req/Ind Rsp/Cnf Invoke Identifier M M(=) Mode M - Managed ob

39、ject class M U Managed object instance M U Event type M C(=) Event time M - Event information M - Current time - U Event reply - C Errors - 9.3 Trouble History Event Notification Functional Unit 9.3.1 Trouble History Event Notification The Trouble History Event Notification service allows a managed

40、system to report the trouble report close out information (when the trouble report state transitions to the closed value) to the managing system or log the information in the managed system. This service uses the CMIS M-EVENT-REPORT service and procedures defined in ISO/IEC 9595. Some implementation

41、s may restrict the values of the discriminator construct so that all Trouble History Event Notifications are logged in the managed system and none are reported to the managing system. Table 2 shows the parameters used in the Trouble History Event Notification service. 9.3.2 Parameters The following

42、parameters are defined for use in this standard in the Trouble History Event Notification Service and are formally defined in ISO/IEC 9595: Invoke identifier: See ISO/IEC 9595. Mode: The mode shall have the value, “confirmed”. Managed object class: This parameter indicates the Telecommunications Tro

43、uble Report object class. Managed object instance: This parameter specifies an instance of the Telecommunications Trouble Report object class. Event type: This parameter identifies the Trouble History Event Notification. It may be included in the success confirmation and shall be included if the eve

44、nt reply parameter is included. Event time: This parameter is mandatory. Event information: This parameter includes the trouble report close-out information. This includes the following parameters (defined in 14.2): ATIS-0300228.2011 12 o managed object instance o received time o trouble found o act

45、ivity duration (optional) o additional trouble information list (optional) o authorization list (optional) o cancel requested by manager (optional) o close out narrative (optional) o close out verification (optional) o commitment time (optional) o customer trouble ticket number (optional) o perceive

46、d trouble severity (optional) o restored time (optional) o trouble clearance person (optional) o trouble report number list (optional) o trouble type (optional) Current time: See ISO/IEC 9595. Event reply: The inclusion of this parameter in the response is conditional upon the successful receipt of

47、the event report. If included, it will be NULL. Errors: See ISO/IEC 9595. 9.4 Review Trouble History Functional Unit The PT-GET service, described in ISO/IEC 10164-1, is used to allow a manager to request information about past troubles reported for a particular CNM service or GNIM object instance r

48、epresenting a telecommunications resource. The PT-GET service request is issued by the manager with the trouble history record object as the managed object class parameter. 9.5 Add Trouble Information Functional Unit The PT-SET service, described in ISO/IEC 10164-1, is used to allow a manager to pro

49、vide additional descriptive text for an open trouble report. This additional information will be added to the description provided upon trouble entry. The Additional Trouble Information attribute is set-valued with an attribute syntax “graphic string”. A minimum of 256 octets shall be supported regardless of the number of values in the set. The manager can only add information, but not remove it. It is possible that the oldest information may be lost if an implementation has restrictions on the maximum size. The PT-SET service is issued by the manager again