Independent Submission D. Zisiadis, Ed.
Request for Comments: 6137 S. Kopsidas, Ed.
Category: Experimental M. Tsavli, Ed.
ISSN: 2070-1721 CERTH
G. Cessieux, Ed.
CNRS
February 2011
Independent Submission D. Zisiadis, Ed.
Request for Comments: 6137 S. Kopsidas, Ed.
Category: Experimental M. Tsavli, Ed.
ISSN: 2070-1721 CERTH
G. Cessieux, Ed.
CNRS
February 2011
The Network Trouble Ticket Data Model (NTTDM)
网络故障单数据模型（NTTDM）
Abstract
摘要
Handling multiple sets of network trouble tickets (TTs) originating from different participants' inter-connected network environments poses a series of challenges for the involved institutions. A Grid is a good example of such a multi-domain project. Each of the participants follows different procedures for handling trouble in its domain, according to the local technical and linguistic profile. The TT systems of the participants collect, represent, and disseminate TT information in different formats.
处理来自不同参与者互联网络环境的多组网络故障单（TTs）对相关机构构成了一系列挑战。网格就是这种多域项目的一个很好的例子。根据当地的技术和语言概况，每个参与者都遵循不同的程序来处理其领域内的问题。参与者的TT系统以不同的格式收集、表示和传播TT信息。
As a result, management of the daily workload by a central Network Operation Centre (NOC) is a challenge on its own. Normalization of TTs to a common format at the central NOC can ease presentation, storing, and handling of the TTs. In the present document, we provide a model for automating the collection and normalization of the TT received by multiple networks forming the Grid. Each of the participants is using its home TT system within its domain for handling trouble incidents, whereas the central NOC is gathering the tickets in the normalized format for repository and handling. XML is used as the common representation language. The model was defined and used as part of the networking support activity of the EGEE (Enabling Grids for E-sciencE) project.
因此，由中央网络运营中心（NOC）管理日常工作负载本身就是一项挑战。将TTs标准化为中央NOC的通用格式可以简化TTs的表示、存储和处理。在本文档中，我们提供了一个模型，用于自动收集和规范形成网格的多个网络接收的TT。每个参与者都在其领域内使用其家庭TT系统来处理故障事件，而中央国家奥委会则以标准化格式收集票据，用于存储和处理。XML被用作公共表示语言。该模型被定义并用作EGEE（电子科学使能网格）项目网络支持活动的一部分。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.
本文件不是互联网标准跟踪规范；它是为检查、实验实施和评估而发布的。
This document defines an Experimental Protocol for the Internet community. This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文档为互联网社区定义了一个实验协议。这是对RFC系列的贡献，独立于任何其他RFC流。RFC编辑器已选择自行发布此文档，并且未声明其对实现或部署的价值。RFC编辑批准发布的文件不适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6137.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6137.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction ....................................................4
1.1. Terminology ................................................5
1.2. Notations ..................................................6
1.3. About the Network Trouble Ticket Data Model ................6
1.4. About the Network Trouble Ticket Implementation ............7
1.5. Future Plans ...............................................7
2. NTTDM Types and Definitions .....................................7
2.1. Types and Definitions for the TYPE Attribute ...............8
2.1.1. Defined .............................................8
2.1.2. Free ................................................8
2.1.3. Multiple ............................................8
2.1.4. List ................................................8
2.2. Types and Definitions for the VALID FORMAT Attributes ......9
2.2.1. Predefined String ...................................9
2.2.1.1. Definitions of the Predefined Values ......10
2.2.2. String .............................................13
2.2.3. Datetime ...........................................13
3. NTTDM ..........................................................14
3.1. NTTDM Components ..........................................14
3.1.1. NTTDM Attributes ...................................14
3.2. NTTDM Aggregate Classes ...................................15
3.2.1. NTTDM-Document Class ...............................15
3.2.2. Ticket Class .......................................15
3.2.3. Ticket Origin Information ..........................17
3.2.3.1. PARTNER_ID ................................17
3.2.3.2. ORIGINAL_ID ...............................17
3.2.4. Ticket Information .................................17
3.2.4.1. TT_ID .....................................17
3.2.4.2. TT_TITLE ..................................18
3.2.4.3. TT_TYPE ...................................18
1. Introduction ....................................................4
1.1. Terminology ................................................5
1.2. Notations ..................................................6
1.3. About the Network Trouble Ticket Data Model ................6
1.4. About the Network Trouble Ticket Implementation ............7
1.5. Future Plans ...............................................7
2. NTTDM Types and Definitions .....................................7
2.1. Types and Definitions for the TYPE Attribute ...............8
2.1.1. Defined .............................................8
2.1.2. Free ................................................8
2.1.3. Multiple ............................................8
2.1.4. List ................................................8
2.2. Types and Definitions for the VALID FORMAT Attributes ......9
2.2.1. Predefined String ...................................9
2.2.1.1. Definitions of the Predefined Values ......10
2.2.2. String .............................................13
2.2.3. Datetime ...........................................13
3. NTTDM ..........................................................14
3.1. NTTDM Components ..........................................14
3.1.1. NTTDM Attributes ...................................14
3.2. NTTDM Aggregate Classes ...................................15
3.2.1. NTTDM-Document Class ...............................15
3.2.2. Ticket Class .......................................15
3.2.3. Ticket Origin Information ..........................17
3.2.3.1. PARTNER_ID ................................17
3.2.3.2. ORIGINAL_ID ...............................17
3.2.4. Ticket Information .................................17
3.2.4.1. TT_ID .....................................17
3.2.4.2. TT_TITLE ..................................18
3.2.4.3. TT_TYPE ...................................18
3.2.4.4. TT_PRIORITY ...............................18
3.2.4.5. TT_STATUS .................................19
3.2.4.6. TT_SOURCE .................................19
3.2.4.7. TT_OPEN_DATETIME ..........................19
3.2.4.8. TT_CLOSE_DATETIME .........................20
3.2.5. Trouble Details ....................................20
3.2.5.1. TT_SHORT_DESCRIPTION ......................20
3.2.5.2. TT_LONG_DESCRIPTION .......................20
3.2.5.3. TYPE ......................................21
3.2.5.4. TT_IMPACT_ASSESSMENT ......................21
3.2.5.5. START_DATETIME ............................21
3.2.5.6. DETECT_DATETIME ...........................22
3.2.5.7. REPORT_DATETIME ...........................22
3.2.5.8. END_DATETIME ..............................22
3.2.5.9. TT_LAST_UPDATE_TIME .......................23
3.2.5.10. TIME_WINDOW_START ........................23
3.2.5.11. TIME_WINDOW_END ..........................23
3.2.5.12. WORK_PLAN_START_DATETIME .................24
3.2.5.13. WORK_PLAN_END_DATETIME ...................24
3.2.6. Related Data .......................................24
3.2.6.1. RELATED_EXTERNAL_TICKETS ..................24
3.2.6.2. ADDITIONAL_DATA ...........................25
3.2.6.3. RELATED_ACTIVITY ..........................25
3.2.6.4. HISTORY ...................................25
3.2.7. Localization and Impact ............................26
3.2.7.1. AFFECTED_COMMUNITY ........................26
3.2.7.2. AFFECTED_SERVICE ..........................26
3.2.7.3. LOCATION ..................................26
3.2.7.4. NETWORK_NODE ..............................27
3.2.7.5. NETWORK_LINK_CIRCUIT ......................27
3.2.7.6. END_LINE_LOCATION_A .......................27
3.2.7.7. END_LINE_LOCATION_B .......................28
3.2.8. Contact Information ................................28
3.2.8.1. OPEN_ENGINEER .............................28
3.2.8.2. CONTACT_ENGINEERS .........................28
3.2.8.3. CLOSE_ENGINEER ............................29
3.2.9. Security ...........................................29
3.2.9.1. HASH ......................................29
3.3. NTTDM Representation ......................................29
4. Internationalization Issues ....................................31
5. Example ........................................................31
5.1. Link Failure ..............................................31
6. Sample Implementation: XML Schema ..............................32
7. Security Considerations ........................................43
8. IANA Considerations ............................................44
9. Contributors ...................................................44
10. Acknowledgements ..............................................45
3.2.4.4. TT_PRIORITY ...............................18
3.2.4.5. TT_STATUS .................................19
3.2.4.6. TT_SOURCE .................................19
3.2.4.7. TT_OPEN_DATETIME ..........................19
3.2.4.8. TT_CLOSE_DATETIME .........................20
3.2.5. Trouble Details ....................................20
3.2.5.1. TT_SHORT_DESCRIPTION ......................20
3.2.5.2. TT_LONG_DESCRIPTION .......................20
3.2.5.3. TYPE ......................................21
3.2.5.4. TT_IMPACT_ASSESSMENT ......................21
3.2.5.5. START_DATETIME ............................21
3.2.5.6. DETECT_DATETIME ...........................22
3.2.5.7. REPORT_DATETIME ...........................22
3.2.5.8. END_DATETIME ..............................22
3.2.5.9. TT_LAST_UPDATE_TIME .......................23
3.2.5.10. TIME_WINDOW_START ........................23
3.2.5.11. TIME_WINDOW_END ..........................23
3.2.5.12. WORK_PLAN_START_DATETIME .................24
3.2.5.13. WORK_PLAN_END_DATETIME ...................24
3.2.6. Related Data .......................................24
3.2.6.1. RELATED_EXTERNAL_TICKETS ..................24
3.2.6.2. ADDITIONAL_DATA ...........................25
3.2.6.3. RELATED_ACTIVITY ..........................25
3.2.6.4. HISTORY ...................................25
3.2.7. Localization and Impact ............................26
3.2.7.1. AFFECTED_COMMUNITY ........................26
3.2.7.2. AFFECTED_SERVICE ..........................26
3.2.7.3. LOCATION ..................................26
3.2.7.4. NETWORK_NODE ..............................27
3.2.7.5. NETWORK_LINK_CIRCUIT ......................27
3.2.7.6. END_LINE_LOCATION_A .......................27
3.2.7.7. END_LINE_LOCATION_B .......................28
3.2.8. Contact Information ................................28
3.2.8.1. OPEN_ENGINEER .............................28
3.2.8.2. CONTACT_ENGINEERS .........................28
3.2.8.3. CLOSE_ENGINEER ............................29
3.2.9. Security ...........................................29
3.2.9.1. HASH ......................................29
3.3. NTTDM Representation ......................................29
4. Internationalization Issues ....................................31
5. Example ........................................................31
5.1. Link Failure ..............................................31
6. Sample Implementation: XML Schema ..............................32
7. Security Considerations ........................................43
8. IANA Considerations ............................................44
9. Contributors ...................................................44
10. Acknowledgements ..............................................45
11. References ....................................................45
11.1. Normative References .....................................45
11.2. Informative References ...................................45
11. References ....................................................45
11.1. Normative References .....................................45
11.2. Informative References ...................................45
Problem-impact assessment, reporting, identification, and handling, as well as dissemination of trouble information and delegation of authority, are some of the main tasks that have to be implemented by the members of a Grid in order to successfully manage the network and maintain operational efficiency of the services offered to their users.
问题影响评估、报告、识别和处理，以及故障信息的传播和授权，是网格成员必须执行的一些主要任务，以便成功地管理网络并保持向其用户提供的服务的运行效率。
Different TT systems are used by each network domain, delivering TTs in alternate formats, while the TT load is growing proportionally with network size and serviced users.
每个网络域使用不同的TT系统，以替代格式提供TT，同时TT负载随着网络规模和服务用户的增加而成比例增长。
We hereby define a data model for TT normalization -- the Network Trouble Ticket Data Model (NTTDM) -- initially targeted for network providers serving EGEE [8]. The model is designed in accordance with RFC 1297 [11] and meets requirements of the multiple TT systems used.
我们在此定义了TT规范化的数据模型——网络故障单数据模型（NTTDM）——最初面向服务于EGEE的网络提供商[8]。该模型根据RFC 1297[11]设计，并满足所用多个TT系统的要求。
The NTTDM
NTTDM
o is both effective and comprehensive, as it compensates for the core activities of the Network Operation Centres (NOCs). It is also dynamic, allowing additional options to be included in the future, according to demand.
o 既有效又全面，因为它补偿了网络运营中心（NOC）的核心活动。它也是动态的，允许根据需求在未来加入其他选项。
o provides an XML representation for conveying incident information across administrative domains between parties that have an operational responsibility of remediation or a "watch-and-warn" policy over a defined constituency.
o 提供一种XML表示，用于在具有修复操作责任的各方之间跨管理域传递事件信息，或在定义的选区上执行“监视并警告”策略。
o encodes information about hosts, networks, and the services running on these systems; attack methodology and associated forensic evidence; impact of the activity; and limited approaches for documenting workflow.
o 对这些系统上运行的主机、网络和服务的信息进行编码；攻击方法和相关的法医证据；活动的影响；记录工作流的方法也很有限。
o aims to simplify TT exchange within the boundaries of a Grid and to enhance the functional cooperation of every NOC and of the Grid Operation Centre (GOC). Community adoption of the NTTDM enhances trouble resolution within the Grid framework and imparts network status cognizance by modeling collaboration and information exchange among operators.
o 旨在简化电网边界内的TT交换，并加强每个国家奥委会和电网运营中心（GOC）的功能合作。NTTDM的社区采用增强了网格框架内的故障解决能力，并通过模拟运营商之间的协作和信息交换来识别网络状态。
o provides a common format that allows GOCs as well as all participating NOCs to store, exchange, manage, and analyze TTs (assessment of TT impact).
o 提供一种通用格式，允许GOC以及所有参与的国家奥委会存储、交换、管理和分析TT（TT影响评估）。
o provides increased automation in handling a TT, since the network operators have a common view of the incident.
o 提高了TT处理的自动化程度，因为网络运营商对事件有共同的看法。
The model was designed and used as part of the networking support activity of the EGEE project; one of the subtasks of this support activity was to enhance the ENOC (EGEE Network Operation Centre) [9] procedures for better overall network coordination of the Grid.
该模型是作为EGEE项目网络支持活动的一部分设计和使用的；该支持活动的子任务之一是加强ENOC（EGEE网络运营中心）[9]程序，以更好地协调电网的整体网络。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [1].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[1]中所述进行解释。
The NTTDM uses specific keywords to describe the various data components. These keywords are:
NTTDM使用特定的关键字来描述各种数据组件。这些关键词是：
Defined, Free, Multiple, List, Predefined String, String, Datetime, Solved, Cancelled, Inactive, Superseded, Opened/Closed, Operational, Informational, Administrative, and Test.
已定义、自由、多个、列表、预定义字符串、字符串、日期时间、已解决、已取消、非活动、已取代、打开/关闭、操作、信息、管理和测试。
These keywords as used in this document are to be interpreted as described in Section 2.
本文件中使用的这些关键词应按照第2节所述进行解释。
Acronyms:
缩略词：
TT: Trouble Ticket
TT：麻烦票
NTTDM: Network Trouble Ticket Data Model
NTTDM：网络故障单数据模型
DB: Database
数据库
EGEE: Enabling Grid for E-sciencE
EGEE：为电子科学启用网格
ENOC: EGEE NOC
ENOC:EGEE NOC
NOC: Network Operation Centre
网络运营中心
GOC: Grid Operation Centre
GOC：电网运营中心
NREN: National Research and Educational Network
NREN：国家研究和教育网络
QoS: Quality of Service
QoS：服务质量
UML: Unified Modeling Language
UML：统一建模语言
XML: Extensible Markup Language
XML：可扩展标记语言
The NTTDM is specified in two ways: as an abstract data model and as an XML Schema. Section 3 provides a Unified Modeling Language (UML) [10] model describing the individual classes and their relationship with each other. The semantics of each class are discussed and their attributes explained. In Section 6, this UML model is converted into an XML Schema [2] [3] [4] [5]. A specific namespace [6] is also defined.
NTTDM以两种方式指定：作为抽象数据模型和XML模式。第3节提供了一个统一建模语言（UML）[10]模型，描述了各个类及其相互之间的关系。讨论了每个类的语义并解释了它们的属性。在第6节中，这个UML模型被转换成XML模式[2][3][4][5]。还定义了一个特定的名称空间[6]。
The term "XML document" refers to any instance of an XML Document. The term "NTTDM document" refers to specific elements and attributes of the NTTDM Schema. Finally, the terms "class" and "element" are used interchangeably to reference either a given UML class in the data model or its corresponding Schema implementation.
术语“XML文档”是指XML文档的任何实例。术语“NTTDM文档”是指NTTDM模式的特定元素和属性。最后，术语“类”和“元素”可以互换使用，以引用数据模型中给定的UML类或其相应的模式实现。
The NTTDM is a data representation that provides a framework for normalizing and sharing information among network operators and the GOC regarding troubles within the Grid boundaries. There has been a lot of thought processing during the design of the data model:
NTTDM是一种数据表示，它提供了一个框架，用于在网络运营商和GOC之间规范化和共享有关电网边界内故障的信息。在设计数据模型的过程中，进行了大量的思维处理：
o The data model serves as a common storage and exchange format.
o 数据模型用作通用存储和交换格式。
o Every NOC still uses its home TT system for network management within its area of control.
o 每个NOC仍然使用其家庭TT系统在其控制区域内进行网络管理。
o As there is no universally adopted definition for a trouble, in the NTTDM definition, the term is used with a comprehensive meaning to cover all NOCs.
o 由于没有普遍采用的故障定义，在NTTDM的定义中，该术语具有广泛的含义，涵盖所有国家奥委会。
o Handling every possible definition of a trouble incident would call for an extremely expanded and complex data model. Therefore, the NTTDM's purpose is to serve as the basis for normalizing and exchanging TTs. It is flexible and expressive in order to ensure that specific NOC requirements are met. Specific NOC information is kept outside the NTTDM, and external databases can be used to feed it.
o 处理故障事件的每一个可能定义都需要一个极其扩展和复杂的数据模型。因此，NTTDM的目的是作为TTs规范化和交换的基础。它具有灵活性和表现力，以确保满足特定的国家奥委会要求。具体的NOC信息保存在NTTDM之外，可以使用外部数据库为其提供信息。
o The domain of managing the information is not fully standardized and must rely on free-form textual descriptions. The NTTDM attempts to strike a balance between supporting this free-form content, while still allowing automated processing of incident information.
o 管理信息的领域没有完全标准化，必须依赖于自由形式的文本描述。NTTDM试图在支持这种自由格式的内容，同时仍然允许自动处理事件信息之间取得平衡。
The NTTDM is only one of several feasible TT data representations. The goal of this design was to be as effective and comprehensive as these other representations and to account for the management of a general Grid environment. The already used TT formats influenced the design of the NTTDM.
NTTDM只是几种可行的TT数据表示形式之一。此设计的目标是与这些其他表示一样有效和全面，并考虑通用网格环境的管理。已经使用的TT格式影响了NTTDM的设计。
Here we describe an example of a typical use case.
这里我们描述一个典型用例的示例。
The Grid project EGEE manages its infrastructure as a network overlay over the European National Research and Educational Networks (NRENs) and wants to be able to warn EGEE sites of the unavailability of the network. Thanks to collaboration with its network provider, the EGEE NOC receives a high volume of TTs (800 tickets/month, 2500 emails/month) from 20 NRENs and should always be able to cope with such a heavy load. Thanks to the NTTDM, the EGEE NOC can automate the TT workflow:
网格项目EGEE将其基础设施管理为覆盖欧洲国家研究和教育网络（NREN）的网络，并希望能够向EGEE站点发出网络不可用的警告。由于与其网络提供商的合作，EGEE NOC从20个NREN处收到大量TTs（800张票/月，2500封电子邮件/月），并且应始终能够应付如此繁重的负载。得益于NTTDM，EGEE NOC可以自动化TT工作流程：
o The TT is filtered, sorted, and stored in a local database (DB).
o TT被过滤、排序并存储在本地数据库（DB）中。
o The TT's impact on the Grid is assessed.
o 评估TT对电网的影响。
o The TT is pushed to an ENOC dashboard application and other tools (EGEE TT system, statistics, etc.).
o TT被推送到ENOC仪表板应用程序和其他工具（EGEE TT系统、统计等）。
Since this is an Experimental document, operational experience will be used to expand the subsections of Section 3.2.3, "Ticket Origin Information", below. The current specification is already used within EGEE. Other Grids are free to use it and report comments to the authors. After enough experimentation, we would like to advance it to the Standards Track.
由于这是一份实验性文件，将利用运行经验来扩展下面第3.2.3节“票证来源信息”的小节。当前规范已在EGEE中使用。其他网格可以自由使用它，并向作者报告评论。经过足够的实验，我们希望将其推进到标准轨道。
The various data elements of the TT data model are typed. This section discusses these data types. When possible, native Schema data types were adopted, but for more complicated formats, regular expressions or external standards were used.
TT数据模型的各种数据元素都是类型化的。本节讨论这些数据类型。如果可能，采用本机模式数据类型，但对于更复杂的格式，则使用正则表达式或外部标准。
These types are used to describe the TYPE attribute.
这些类型用于描述类型属性。
The Defined data type means that the data model provides a means to compute this value from the rest of the fields.
定义的数据类型意味着数据模型提供了从其余字段计算该值的方法。
The Defined data type is implemented as "Defined" in the Schema.
定义的数据类型在模式中实现为“已定义”。
The Free data type means that the value can be freely chosen.
自由数据类型意味着可以自由选择值。
All Free strings SHOULD have as an attribute the language used.
所有自由字符串都应具有所用语言的属性。
The Free data type is implemented as "Free" in the Schema.
自由数据类型在模式中实现为“自由”。
The Multiple data type consists of one value among multiple fixed values.
多重数据类型由多个固定值中的一个值组成。
The Multiple data type is implemented as "Multiple" in the Schema.
多重数据类型在模式中实现为“多重”。
"List" means many values among multiple fixed values. The List data type is implemented as "List" in the Schema.
“列表”是指多个固定值中的多个值。列表数据类型在模式中实现为“列表”。
A Predefined String means the different values are predefined in the data model.
预定义字符串表示在数据模型中预定义了不同的值。
Each field that requires a Predefined String contains a specific value. Figure 1 shows the allowed values for such fields.
需要预定义字符串的每个字段都包含一个特定值。图1显示了此类字段的允许值。
+------------------------+-----------------------------------+
| FIELD NAME | VALUES |
+------------------------+-----------------------------------+
| TT_TYPE | Operational, Informational, |
| | Administrative, Test |
+------------------------+-----------------------------------+
| TYPE | Scheduled, Unscheduled |
+------------------------+-----------------------------------+
| TT_PRIORITY | Low, Medium, High |
+------------------------+-----------------------------------+
| TT_SHORT_DESCRIPTION | Core Line Fault, Access Line |
| | Fault, Degraded Service, Router |
| | Hardware Fault, Router Software |
| | Fault, Routing Problem, Undefined |
| | Problem, Network Congestion, |
| | Client Upgrade, IPv6, QoS, VoIP, |
| | Other |
+------------------------+-----------------------------------+
| TT_IMPACT_ASSESSMENT | No impact, Reduced redundancy, |
| | Minor performance impact, Severe |
| | performance impact, |
| | No connectivity, On backup, |
| | At risk, Unknown |
+------------------------+-----------------------------------+
| TT_STATUS | Opened, Updated, Closed, Solved, |
| | Inactive, Cancelled, Reopened, |
| | Superseded, Opened/Closed |
+------------------------+-----------------------------------+
| TT_SOURCE | Users, Monitoring, Other NOC |
+------------------------+-----------------------------------+
+------------------------+-----------------------------------+
| FIELD NAME | VALUES |
+------------------------+-----------------------------------+
| TT_TYPE | Operational, Informational, |
| | Administrative, Test |
+------------------------+-----------------------------------+
| TYPE | Scheduled, Unscheduled |
+------------------------+-----------------------------------+
| TT_PRIORITY | Low, Medium, High |
+------------------------+-----------------------------------+
| TT_SHORT_DESCRIPTION | Core Line Fault, Access Line |
| | Fault, Degraded Service, Router |
| | Hardware Fault, Router Software |
| | Fault, Routing Problem, Undefined |
| | Problem, Network Congestion, |
| | Client Upgrade, IPv6, QoS, VoIP, |
| | Other |
+------------------------+-----------------------------------+
| TT_IMPACT_ASSESSMENT | No impact, Reduced redundancy, |
| | Minor performance impact, Severe |
| | performance impact, |
| | No connectivity, On backup, |
| | At risk, Unknown |
+------------------------+-----------------------------------+
| TT_STATUS | Opened, Updated, Closed, Solved, |
| | Inactive, Cancelled, Reopened, |
| | Superseded, Opened/Closed |
+------------------------+-----------------------------------+
| TT_SOURCE | Users, Monitoring, Other NOC |
+------------------------+-----------------------------------+
Figure 1. Allowed Predefined String Values
图1。允许的预定义字符串值
The Predefined String data type is implemented as "xs:string" in the Schema with a sequence of enumerations for the allowed values.
预定义的字符串数据类型在模式中实现为“xs:String”，并带有一系列允许值的枚举。
TT_TYPE
TT_型
o Operational: for network incident and maintenance only.
o 操作：仅用于网络事故和维护。
o Informational: information about the TT system or the exchange interface (maintenance, upgrade).
o 信息性：关于TT系统或exchange接口（维护、升级）的信息。
o Administrative: information about the access to the TT system (credentials) or the exchange interface.
o 管理：有关访问TT系统（凭据）或exchange接口的信息。
o Test: to test the TT system or the exchange interface, etc.
o 测试：测试TT系统或交换接口等。
TYPE
类型
o Scheduled: the incident was scheduled to happen.
o 计划：事件按计划发生。
o Unscheduled: the incident was unscheduled.
o 计划外的：事件是计划外的。
TT_PRIORITY
TT_优先级
o Low: the TT priority is low.
o 低：TT优先级低。
o Medium: the TT priority is medium.
o 中等：TT优先级为中等。
o High: the TT priority is high.
o 高：TT优先级高。
TT_SHORT_DESCRIPTION
简短描述
o Core Line Fault: malfunction of a high-bandwidth core line.
o 核心线路故障：高带宽核心线路故障。
o Access Line Fault: malfunction of a medium-bandwidth access line.
o 接入线故障：中等带宽接入线故障。
o Degraded Service.
o 降级服务。
o Router Hardware Fault: malfunction of the router hardware.
o 路由器硬件故障：路由器硬件故障。
o Router Software Fault: malfunction of the router software.
o 路由器软件故障：路由器软件故障。
o Routing Problem: incident regarding the routing service.
o 路由问题：有关路由服务的事件。
o Undefined Problem: nature of the problem not identified.
o 未定义问题：未确定问题的性质。
o Network Congestion: problem due to traffic at the network (blocked).
o 网络拥塞：由于网络上的流量（阻塞）而导致的问题。
o Client Upgrade: incidents regarding client/services upgrade.
o 客户端升级：有关客户端/服务升级的事件。
o IPv6: incident regarding the IPv6 network.
o IPv6:有关IPv6网络的事件。
o QoS: incident regarding the Quality of Service (QoS) of the network.
o QoS：有关网络服务质量（QoS）的事件。
o VoIP: incident regarding Voice over IP (VoIP).
o VoIP：关于IP语音（VoIP）的事件。
o Other: non-listed incident.
o 其他：未列出的事件。
TT_IMPACT_ASSESSMENT
TT_影响评估
o No impact: the incident does not cause any impacts.
o 无影响：事件不会造成任何影响。
o Reduced redundancy: the incident reduces network redundancy.
o 减少冗余：事件减少了网络冗余。
o Minor performance impact: the incident causes a minor performance impact.
o 轻微性能影响：事件造成轻微性能影响。
o Severe performance impact: the incident causes a severe performance impact.
o 严重性能影响：事件造成严重性能影响。
o No connectivity: the incident causes connectivity failure.
o 无连接：事件导致连接失败。
o On backup: the incident causes a malfunction of backup services.
o 备份：事件导致备份服务故障。
o At risk: the incident should not have any impact but could possibly cause some trouble.
o 风险：事件不应产生任何影响，但可能会造成一些麻烦。
o Unknown: the nature of the impact is not identified.
o 未知：未确定影响的性质。
TT_STATUS
TT_状态
o Opened: the ticket is opened.
o 已打开：车票已打开。
o Closed: the ticket is closed.
o 关闭：票已关闭。
o Updated: the ticket's contents have been updated.
o 已更新：票证的内容已更新。
o Cancelled: the ticket has been opened twice; one of the tickets is cancelled, and a relationship between them is defined via the RELATED_ACTIVITY field.
o 已取消：车票已打开两次；其中一张票据被取消，它们之间的关系通过相关的_活动字段定义。
o Solved: the incident is solved, but the team prefers to monitor/check for future issues.
o 已解决：事件已解决，但团队更愿意监控/检查未来问题。
o Opened/Closed: the ticket was opened only to report an incident that has already been solved.
o 打开/关闭：打开票据只是为了报告已解决的事件。
o Inactive: the ticket is under the responsibility of an external domain and is no longer under the reporting domain's control.
o 非活动：票证由外部域负责，不再受报告域的控制。
o Reopened: the ticket was closed by error, or the problem was erroneously declared to be solved. Data in the History field are very important in this case.
o 重新打开：票据错误关闭，或错误地宣布问题已解决。在这种情况下，历史字段中的数据非常重要。
o Superseded: the ticket has been superseded by another one (for example, a bigger problem that had resulted in many tickets was later merged into a single incident/ticket). The RELATED_ACTIVITY field SHOULD include the master ticket reference.
o 已取代：该票证已被另一个票证取代（例如，导致多个票证的更大问题后来合并为单个事件/票证）。相关的_活动字段应包括主票据参考。
Allowed transitions for TT_STATUS are only those indicated in Figure 2. Possible final states are indicated with (X).
TT_状态允许的转换仅如图2所示。可能的最终状态用（X）表示。
+------------------+
| Opened/Closed (X)|
+------------------+
|
|
V
+--------------+
/-----------------------| Reopened |<-------------------\
| | |----------\ |
| +--------------+ | |
| ^ | |
| | | |
| V | |
| +-------------------+ | |
| | Superseded (X) | | |
| | or Inactive (X) | | |
| /----------------->| or Cancelled (X) |<---\ | |
| | +-------------------+ | | |
| | ^ | | |
| | | | V |
| | +--------+ | +--------+ |
| | /---------| Opened |----/ | Solved |-----\ |
| | | | |---------------->| | | |
| | | +--------+ +--------+ | |
| | | | ^ | |
V | V | | | |
+---------+ | | | |
| |----------(|)-------------------------/ V V
| Updated | | +------------+
| |----------(|)---------------------------->| |
+---------+ | | Closed (X) |
\----------------------------->| |
+------------+
+------------------+
| Opened/Closed (X)|
+------------------+
|
|
V
+--------------+
/-----------------------| Reopened |<-------------------\
| | |----------\ |
| +--------------+ | |
| ^ | |
| | | |
| V | |
| +-------------------+ | |
| | Superseded (X) | | |
| | or Inactive (X) | | |
| /----------------->| or Cancelled (X) |<---\ | |
| | +-------------------+ | | |
| | ^ | | |
| | | | V |
| | +--------+ | +--------+ |
| | /---------| Opened |----/ | Solved |-----\ |
| | | | |---------------->| | | |
| | | +--------+ +--------+ | |
| | | | ^ | |
V | V | | | |
+---------+ | | | |
| |----------(|)-------------------------/ V V
| Updated | | +------------+
| |----------(|)---------------------------->| |
+---------+ | | Closed (X) |
\----------------------------->| |
+------------+
Figure 2. TT_STATUS Transition Diagram
图2。TT_状态转换图
The String value is defined by the user of the model. The String data type is implemented as "xs:string" in the Schema.
字符串值由模型的用户定义。字符串数据类型在模式中实现为“xs:String”。
Date-time strings are represented by the Datetime data type. Each date-time string identifies a particular instant in time; ranges are not supported.
日期时间字符串由日期时间数据类型表示。每个日期时间字符串标识特定的时间瞬间；不支持范围。
Date-time strings are formatted according to a subset of ISO 8601:2000 as documented in RFC 3339.
日期时间字符串根据RFC 3339中记录的ISO 8601:2000的子集进行格式化。
The Datetime data type is implemented as "xs:dateTime" in the Schema.
Datetime数据类型在模式中实现为“xs:Datetime”。
In this section, the individual components of the NTTDM will be discussed in detail. This class provides a standardized representation for commonly exchanged Field Name data.
在本节中，将详细讨论NTTDM的各个组件。此类为通常交换的字段名数据提供标准化表示。
The Field Name class has four attributes. Each attribute provides information about a Field Name instance. The attributes that characterize one instance constitute all the information required to form the data model.
Field Name类有四个属性。每个属性都提供有关字段名实例的信息。表征一个实例的属性构成了形成数据模型所需的所有信息。
DESCRIPTION
描述
This field contains a short description of the Field Name.
此字段包含字段名的简短说明。
TYPE
类型
The TYPE attribute contains information about the type of the Field Name it depends on. The values that it may contain are:
TYPE属性包含有关它所依赖的字段名类型的信息。它可能包含的值包括：
Defined, Free, Multiple, and List.
已定义、自由、多个和列表。
VALID FORMAT
有效格式
This attribute contains information about the format of each field. The values that it may contain are:
此属性包含有关每个字段格式的信息。它可能包含的值包括：
Predefined String, String, and Datetime.
预定义的字符串、字符串和日期时间。
MANDATORY
强制性的
This attribute indicates whether the information of each field is required or optional. If the information is required, the MANDATORY field contains the word "YES". If the information is optional, the MANDATORY field contains the word "NO".
此属性指示每个字段的信息是必需的还是可选的。如果信息是必需的，则必填字段包含单词“是”。如果信息是可选的，则必填字段包含“否”一词。
The NTTDM-Document class is the top-level class in the NTTDM. All NTTDM documents are an instance of this class.
NTTDM文档类是NTTDM中的顶级类。所有NTTDM文档都是此类的实例。
+---------------+
| NTTDM-Document|
+---------------+
| version |<>--{1..*}--[ Ticket ]
| lang |
+---------------+
+---------------+
| NTTDM-Document|
+---------------+
| version |<>--{1..*}--[ Ticket ]
| lang |
+---------------+
Figure 3. NTTDM-Document Class
图3。NTTDM文档类
The aggregate class that constitutes an NTTDM-Document is:
构成NTTDM文档的聚合类为：
Ticket
票
One or more. The information related to a single ticket.
一个或多个。与单张票相关的信息。
The NTTDM-Document class has two attributes:
NTTDM文档类有两个属性：
version
版本
STRING. The value of this attribute MUST be "1.00".
一串此属性的值必须为“1.00”。
lang
朗
Required.
必修的。
Every ticket is represented by an instance of the Ticket class. This class provides a standardized representation for commonly exchanged TT data.
每个票证都由票证类的一个实例表示。该类为通常交换的TT数据提供标准化表示。
+---------+
| Ticket |
+---------+
| lang |<>----------[ Partner_ID ]
| |<>----------[ Original_ID ]
| |<>----------[ TT_ID ]
| |<>----------[ TT_Title ]
| |<>----------[ TT_Type ]
| |<>--{0..1}--[ TT_Priority ]
| |<>----------[ TT_Status ]
| |<>--{0..1}--[ TT_Source ]
| |<>----------[ TT_Open_Datetime ]
| |<>----------[ TT_Close_Datetime ]
| |<>----------[ TT_Short_Description ]
| |<>----------[ TT_Long_Description ]
| |<>----------[ Type ]
| |<>----------[ TT_Impact_Assessment ]
| |<>----------[ Start_Datetime ]
| |<>--{0..1}--[ Detect_Datetime ]
| |<>--{0..1}--[ Report_Datetime ]
| |<>----------[ End_Datetime ]
| |<>----------[ TT_Last_Update_Time ]
| |<>--{0..1}--[ Time_Window_Start ]
| |<>--{0..1}--[ Time_Window_End ]
| |<>--{0..1}--[ Work_Plan_Start_Datetime ]
| |<>--{0..1}--[ Work_Plan_End_Datetime ]
| |<>--{0..1}--[ Related_External_Tickets ]
| |<>--{0..1}--[ Additional_Data ]
| |<>--{0..1}--[ Related_Activity ]
| |<>----------[ History ]
| |<>--{0..1}--[ Affected_Community ]
| |<>--{0..1}--[ Affected_Service ]
| |<>----------[ Location ]
| |<>--{0..1}--[ Network_Node ]
| |<>--{0..1}--[ Network_Link_Circuit ]
| |<>--{0..1}--[ End_Line_Location_A ]
| |<>--{0..1}--[ End_Line_Location_B ]
| |<>--{0..1}--[ Open_Engineer ]
| |<>--{0..1}--[ Contact_Engineers ]
| |<>--{0..1}--[ Close_Engineer ]
| |<>--{0..1}--[ Hash ]
+---------+
+---------+
| Ticket |
+---------+
| lang |<>----------[ Partner_ID ]
| |<>----------[ Original_ID ]
| |<>----------[ TT_ID ]
| |<>----------[ TT_Title ]
| |<>----------[ TT_Type ]
| |<>--{0..1}--[ TT_Priority ]
| |<>----------[ TT_Status ]
| |<>--{0..1}--[ TT_Source ]
| |<>----------[ TT_Open_Datetime ]
| |<>----------[ TT_Close_Datetime ]
| |<>----------[ TT_Short_Description ]
| |<>----------[ TT_Long_Description ]
| |<>----------[ Type ]
| |<>----------[ TT_Impact_Assessment ]
| |<>----------[ Start_Datetime ]
| |<>--{0..1}--[ Detect_Datetime ]
| |<>--{0..1}--[ Report_Datetime ]
| |<>----------[ End_Datetime ]
| |<>----------[ TT_Last_Update_Time ]
| |<>--{0..1}--[ Time_Window_Start ]
| |<>--{0..1}--[ Time_Window_End ]
| |<>--{0..1}--[ Work_Plan_Start_Datetime ]
| |<>--{0..1}--[ Work_Plan_End_Datetime ]
| |<>--{0..1}--[ Related_External_Tickets ]
| |<>--{0..1}--[ Additional_Data ]
| |<>--{0..1}--[ Related_Activity ]
| |<>----------[ History ]
| |<>--{0..1}--[ Affected_Community ]
| |<>--{0..1}--[ Affected_Service ]
| |<>----------[ Location ]
| |<>--{0..1}--[ Network_Node ]
| |<>--{0..1}--[ Network_Link_Circuit ]
| |<>--{0..1}--[ End_Line_Location_A ]
| |<>--{0..1}--[ End_Line_Location_B ]
| |<>--{0..1}--[ Open_Engineer ]
| |<>--{0..1}--[ Contact_Engineers ]
| |<>--{0..1}--[ Close_Engineer ]
| |<>--{0..1}--[ Hash ]
+---------+
Figure 4. The Ticket Class
图4。客票等级
lang
朗
Required.
必修的。
The Field Names are the Aggregate Classes that constitute the NTTDM, and each of them is an element that is characterized by a quadruple (DESCRIPTION, TYPE, VALID FORMAT, MANDATORY).
字段名是构成NTTDM的聚合类，每个类都是一个元素，其特征是四个（描述、类型、有效格式、必填）。
+--------------+
| PARTNER_ID |
+--------------+
| DESCRIPTION | The unique ID of the TT source partner.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
+--------------+
| PARTNER_ID |
+--------------+
| DESCRIPTION | The unique ID of the TT source partner.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
Figure 5. Partner_ID Class
图5。合作伙伴ID类
+--------------+
| ORIGINAL_ID |
+--------------+
| DESCRIPTION | The TT ID that was assigned by the party.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
+--------------+
| ORIGINAL_ID |
+--------------+
| DESCRIPTION | The TT ID that was assigned by the party.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
Figure 6. Original_ID Class
图6。原始ID类
+--------------+
| TT_ID |
+--------------+
| DESCRIPTION | The unique ID of the TT.
| TYPE | As defined below.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
+--------------+
| TT_ID |
+--------------+
| DESCRIPTION | The unique ID of the TT.
| TYPE | As defined below.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
Figure 7. TT_ID Class
图7。TT_ID类
TYPE is constructed as "PARTNER_ID"_"ORIGINAL_ID". PARTNER_ID and ORIGINAL_ID therefore MUST NOT contain an underscore character.
类型构造为“合作伙伴\u ID”\u“原始\u ID”。因此，合作伙伴ID和原始ID不能包含下划线字符。
+---------------+
| TT_TITLE |
+---------------+
| DESCRIPTION | The title of the TT.
| TYPE | Defined.
| VALID FORMAT | String.
| MANDATORY | Yes.
+---------------+
+---------------+
| TT_TITLE |
+---------------+
| DESCRIPTION | The title of the TT.
| TYPE | Defined.
| VALID FORMAT | String.
| MANDATORY | Yes.
+---------------+
Figure 8. TT_Title Class
图8。TT_标题类
+---------------+
| TT_TYPE |
+---------------+
| DESCRIPTION | The type of the TT.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+---------------+
+---------------+
| TT_TYPE |
+---------------+
| DESCRIPTION | The type of the TT.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+---------------+
Figure 9. TT_Type Class
图9。TT_型类
+--------------+
| TT_PRIORITY |
+--------------+
| DESCRIPTION | The TT priority.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | No.
+--------------+
+--------------+
| TT_PRIORITY |
+--------------+
| DESCRIPTION | The TT priority.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | No.
+--------------+
Figure 10. TT_Priority Class
图10。TT_优先等级
+--------------+
| TT_STATUS |
+--------------+
| DESCRIPTION | The TT status.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+--------------+
+--------------+
| TT_STATUS |
+--------------+
| DESCRIPTION | The TT status.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+--------------+
Figure 11. TT_Status Class
图11。TT_状态类
+--------------+
| TT_SOURCE |
+--------------+
| DESCRIPTION | The source of the ticket.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | No.
+--------------+
+--------------+
| TT_SOURCE |
+--------------+
| DESCRIPTION | The source of the ticket.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | No.
+--------------+
Figure 12. TT_Source Class
图12。TT_源类
+------------------+
| TT_OPEN_DATETIME |
+------------------+
| DESCRIPTION | The date and time when the TT was opened.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+------------------+
+------------------+
| TT_OPEN_DATETIME |
+------------------+
| DESCRIPTION | The date and time when the TT was opened.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+------------------+
Figure 13. TT_Open_Datetime Class
图13。TT_Open_Datetime类
+-------------------+
| TT_CLOSE_DATETIME |
+-------------------+
| DESCRIPTION | The date and time when the TT was closed.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+-------------------+
+-------------------+
| TT_CLOSE_DATETIME |
+-------------------+
| DESCRIPTION | The date and time when the TT was closed.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+-------------------+
Figure 14. TT_Close_Datetime Class
图14。TT_Close_日期时间类
+----------------------+
| TT_SHORT_DESCRIPTION |
+----------------------+
| DESCRIPTION | The short description of the trouble.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+----------------------+
+----------------------+
| TT_SHORT_DESCRIPTION |
+----------------------+
| DESCRIPTION | The short description of the trouble.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+----------------------+
Figure 15. TT_Short_Description Class
图15。TT_简短描述类
+---------------------+
| TT_LONG_DESCRIPTION |
+---------------------+
| DESCRIPTION | The detailed description of the
| | incident/maintenance reported in the TT.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------------+
+---------------------+
| TT_LONG_DESCRIPTION |
+---------------------+
| DESCRIPTION | The detailed description of the
| | incident/maintenance reported in the TT.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------------+
Figure 16. TT_Long_Description Class
图16。TT_Long_描述类
+--------------+
| TYPE |
+--------------+
| DESCRIPTION | The type of the trouble.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+--------------+
+--------------+
| TYPE |
+--------------+
| DESCRIPTION | The type of the trouble.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+--------------+
Figure 17. Type Class
图17。类型类
+----------------------+
| TT_IMPACT_ASSESSMENT |
+----------------------+
| DESCRIPTION | The impact of the incident/maintenance.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+----------------------+
+----------------------+
| TT_IMPACT_ASSESSMENT |
+----------------------+
| DESCRIPTION | The impact of the incident/maintenance.
| TYPE | Multiple.
| VALID FORMAT | Predefined String.
| MANDATORY | Yes.
+----------------------+
Figure 18. TT_Impact_Assessment Class
图18。TT_影响评估课程
+----------------+
| START_DATETIME |
+----------------+
| DESCRIPTION | The date and time that the
| | incident/maintenance started.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+----------------+
+----------------+
| START_DATETIME |
+----------------+
| DESCRIPTION | The date and time that the
| | incident/maintenance started.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+----------------+
Figure 19. Start_Datetime Class
图19。开始日期时间类
+-------------------+
| DETECT_DATETIME |
+-------------------+
| DESCRIPTION | The date and time when the incident
| | was detected.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+-------------------+
+-------------------+
| DETECT_DATETIME |
+-------------------+
| DESCRIPTION | The date and time when the incident
| | was detected.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+-------------------+
Figure 20. Detect_Datetime Class
图20。检测日期时间类
+-----------------+
| REPORT_DATETIME |
+-----------------+
| DESCRIPTION | The date and time when the incident
| | was reported.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+-----------------+
+-----------------+
| REPORT_DATETIME |
+-----------------+
| DESCRIPTION | The date and time when the incident
| | was reported.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+-----------------+
Figure 21. Report_Datetime Class
图21。报告日期时间类
+--------------+
| END_DATETIME |
+--------------+
| DESCRIPTION | The date and time when the incident/maintenance
| | ended.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+--------------+
+--------------+
| END_DATETIME |
+--------------+
| DESCRIPTION | The date and time when the incident/maintenance
| | ended.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+--------------+
Figure 22. End_Datetime Class
图22。结束日期时间类
+---------------------+
| TT_LAST_UPDATE_TIME |
+---------------------+
| DESCRIPTION | The last date and time when the TT was
| | updated.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+---------------------+
+---------------------+
| TT_LAST_UPDATE_TIME |
+---------------------+
| DESCRIPTION | The last date and time when the TT was
| | updated.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | Yes.
+---------------------+
Figure 23. TT_Last_Update_Time Class
图23。TT\u上次更新\u时间类
+-------------------+
| TIME_WINDOW_START |
+-------------------+
| DESCRIPTION | The window start time in which planned
| | maintenance may occur.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No, unless TYPE is "Scheduled".
+-------------------+
+-------------------+
| TIME_WINDOW_START |
+-------------------+
| DESCRIPTION | The window start time in which planned
| | maintenance may occur.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No, unless TYPE is "Scheduled".
+-------------------+
Figure 24. Time_Window_Start Class
图24。时间窗口开始上课
+-----------------+
| TIME_WINDOW_END |
+-----------------+
| DESCRIPTION | The window end time in which planned
| | maintenance may occur.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No, unless TYPE is "Scheduled".
+-----------------+
+-----------------+
| TIME_WINDOW_END |
+-----------------+
| DESCRIPTION | The window end time in which planned
| | maintenance may occur.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No, unless TYPE is "Scheduled".
+-----------------+
Figure 25. Time_Window_End Class
图25。时间窗口结束类
+--------------------------+
| WORK_PLAN_START_DATETIME |
+--------------------------+
| DESCRIPTION | Work planned (expected): start time
| | in case of maintenance.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+--------------------------+
+--------------------------+
| WORK_PLAN_START_DATETIME |
+--------------------------+
| DESCRIPTION | Work planned (expected): start time
| | in case of maintenance.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+--------------------------+
Figure 26. Work_Plan_Start_Datetime Class
图26。工作\计划\开始\日期时间类
+------------------------+
| WORK_PLAN_END_DATETIME |
+------------------------+
| DESCRIPTION | Work planned (expected): end time
| | in case of maintenance.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+------------------------+
+------------------------+
| WORK_PLAN_END_DATETIME |
+------------------------+
| DESCRIPTION | Work planned (expected): end time
| | in case of maintenance.
| TYPE | Multiple.
| VALID FORMAT | Datetime.
| MANDATORY | No.
+------------------------+
Figure 27. Work_Plan_End_Datetime Class
图27。工作\计划\结束\日期时间类
The period delimited by WORK_PLAN_START_DATETIME and WORK_PLAN_END_DATETIME MUST be included in the period delimited by TIME_WINDOW_START and TIME_WINDOW_END, and duplicated with {START, END}_DATETIME, even in case of maintenance.
由WORK_PLAN_START_DATETIME和WORK_PLAN_END_DATETIME分隔的期间必须包含在由TIME_WINDOW_START和TIME_WINDOW_END分隔的期间中，并与{START，END}DATETIME重复，即使在维护的情况下也是如此。
+--------------------------+
| RELATED_EXTERNAL_TICKETS |
+--------------------------+
| DESCRIPTION | The NOC entity related to the incident.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+--------------------------+
+--------------------------+
| RELATED_EXTERNAL_TICKETS |
+--------------------------+
| DESCRIPTION | The NOC entity related to the incident.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+--------------------------+
Figure 28. Related_External_Tickets Class
图28。相关\u外部\u票证类别
+-----------------+
| ADDITIONAL_DATA |
+-----------------+
| DESCRIPTION | Additional information.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | No.
+-----------------+
+-----------------+
| ADDITIONAL_DATA |
+-----------------+
| DESCRIPTION | Additional information.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | No.
+-----------------+
Figure 29. Additional_Data Class
图29。附加数据类
+------------------+
| RELATED_ACTIVITY |
+------------------+
| DESCRIPTION | The TT IDs of the related incidents.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+------------------+
+------------------+
| RELATED_ACTIVITY |
+------------------+
| DESCRIPTION | The TT IDs of the related incidents.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+------------------+
Figure 30. Related_Activity Class
图30。相关活动课程
+--------------+
| HISTORY |
+--------------+
| DESCRIPTION | The necessary actions/events log.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
+--------------+
| HISTORY |
+--------------+
| DESCRIPTION | The necessary actions/events log.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
Figure 31. History Class
图31。历史课
Note: This field MUST NOT be empty when the VALID FORMAT attribute of the TT_STATUS field is anything other than "OPENED" or "OPENED/CLOSED".
注意：当TT_状态字段的有效格式属性不是“打开”或“打开/关闭”时，此字段不得为空。
+--------------------+
| AFFECTED_COMMUNITY |
+--------------------+
| DESCRIPTION | Information about the community that was
| | affected by the incident.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | No.
+--------------------+
+--------------------+
| AFFECTED_COMMUNITY |
+--------------------+
| DESCRIPTION | Information about the community that was
| | affected by the incident.
| TYPE | Free.
| VALID FORMAT | String.
| MANDATORY | No.
+--------------------+
Figure 32. Affected_Community Class
图32。社区班
+------------------+
| AFFECTED_SERVICE |
+------------------+
| DESCRIPTION | The service that was affected by the
| | incident.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+------------------+
+------------------+
| AFFECTED_SERVICE |
+------------------+
| DESCRIPTION | The service that was affected by the
| | incident.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+------------------+
Figure 33. Affected_Service Class
图33。受影响的服务级别
+--------------+
| LOCATION |
+--------------+
| DESCRIPTION | The location (Point of Presence (POP) site,
| | city, etc.) of the incident/maintenance.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
+--------------+
| LOCATION |
+--------------+
| DESCRIPTION | The location (Point of Presence (POP) site,
| | city, etc.) of the incident/maintenance.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | Yes.
+--------------+
Figure 34. Location Class
图34。位置类
+--------------+
| NETWORK_NODE |
+--------------+
| DESCRIPTION | The NOC network node related to the incident.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+--------------+
+--------------+
| NETWORK_NODE |
+--------------+
| DESCRIPTION | The NOC network node related to the incident.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+--------------+
Figure 35. Network_Node Class
图35。网络节点类
+----------------------+
| NETWORK_LINK_CIRCUIT |
+----------------------+
| DESCRIPTION | The name of the network line related
| | to the incident.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+----------------------+
+----------------------+
| NETWORK_LINK_CIRCUIT |
+----------------------+
| DESCRIPTION | The name of the network line related
| | to the incident.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+----------------------+
Figure 36. Network_Link_Circuit Class
图36。网络链路电路类
+---------------------+
| END_LINE_LOCATION_A |
+---------------------+
| DESCRIPTION | A-end of the link.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------------+
+---------------------+
| END_LINE_LOCATION_A |
+---------------------+
| DESCRIPTION | A-end of the link.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------------+
Figure 37. End_Line_Location_A Class
图37。结束\u行\u位置\u类
+---------------------+
| END_LINE_LOCATION_B |
+---------------------+
| DESCRIPTION | B-end of the link.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------------+
+---------------------+
| END_LINE_LOCATION_B |
+---------------------+
| DESCRIPTION | B-end of the link.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------------+
Figure 38. End_Line_Location_B Class
图38。终点线位置B类
+---------------+
| OPEN_ENGINEER |
+---------------+
| DESCRIPTION | The engineer that opened the ticket.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------+
+---------------+
| OPEN_ENGINEER |
+---------------+
| DESCRIPTION | The engineer that opened the ticket.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+---------------+
Figure 39. Open_Engineer Class
图39。开放式工程师班
+-------------------+
| CONTACT_ENGINEERS |
+-------------------+
| DESCRIPTION | The engineers responsible for the incident
| | settlement.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+-------------------+
+-------------------+
| CONTACT_ENGINEERS |
+-------------------+
| DESCRIPTION | The engineers responsible for the incident
| | settlement.
| TYPE | List.
| VALID FORMAT | String.
| MANDATORY | No.
+-------------------+
Figure 40. Contact_Engineers Class
图40。联络大学工程师班
+----------------+
| CLOSE_ENGINEER |
+----------------+
| DESCRIPTION | The engineer that closed the ticket.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+----------------+
+----------------+
| CLOSE_ENGINEER |
+----------------+
| DESCRIPTION | The engineer that closed the ticket.
| TYPE | Multiple.
| VALID FORMAT | String.
| MANDATORY | No.
+----------------+
Figure 41. Close_Engineer Class
图41。近距离工科
+-------------+
| HASH |
+-------------+
| DESCRIPTION | Encrypted message hash.
| TYPE | Defined.
| VALID FORMAT| String.
| MANDATORY | No.
+-------------+
+-------------+
| HASH |
+-------------+
| DESCRIPTION | Encrypted message hash.
| TYPE | Defined.
| VALID FORMAT| String.
| MANDATORY | No.
+-------------+
Figure 42. Hash Class
图42。散列类
The collected and processed TTs received from multiple telecommunications networks are adjusted in a normalized NTTDM. Figure 43 shows the representation of this normalized data model. The "DESCRIPTION" attribute is implied.
在标准化的NTTDM中调整从多个电信网络接收的收集和处理的TTs。图43显示了此规范化数据模型的表示。“DESCRIPTION”属性是隐含的。
+------------------------+--------+------------------+---------+
| FIELD NAME | TYPE |VALID FORMAT |MANDATORY|
+------------------------+--------+------------------+---------+
|PARTNER_ID |MULTIPLE|STRING |YES |
|ORIGINAL_ID |FREE |STRING |YES |
|TT_ID |DEFINED |STRING |YES |
|TT_TITLE |DEFINED |STRING |YES |
|TT_TYPE |MULTIPLE|PREDEFINED STRING |YES |
|TT_PRIORITY |MULTIPLE|PREDEFINED STRING |NO |
|TT_STATUS |MULTIPLE|PREDEFINED STRING |YES |
|TT_SOURCE |MULTIPLE|PREDEFINED STRING |NO |
|TT_OPEN_DATETIME |MULTIPLE|DATETIME |YES |
|TT_CLOSE_DATETIME |MULTIPLE|DATETIME |YES |
|TT_SHORT_DESCRIPTION |MULTIPLE|PREDEFINED STRING |YES |
|TT_LONG_DESCRIPTION |FREE |STRING |NO |
|TYPE |MULTIPLE|PREDEFINED STRING |YES |
|TT_IMPACT_ASSESSMENT |MULTIPLE|PREDEFINED STRING |YES |
|START_DATETIME |MULTIPLE|DATETIME |YES |
|DETECT_DATETIME |MULTIPLE|DATETIME |NO |
|REPORT_DATETIME |MULTIPLE|DATETIME |NO |
|END_DATETIME |MULTIPLE|DATETIME |YES |
|TT_LAST_UPDATE_TIME |MULTIPLE|DATETIME |YES |
|TIME_WINDOW_START |MULTIPLE|DATETIME |NO |
|TIME_WINDOW_END |MULTIPLE|DATETIME |NO |
|WORK_PLAN_START_DATETIME|MULTIPLE|DATETIME |NO |
|WORK_PLAN_END_DATETIME |MULTIPLE|DATETIME |NO |
|RELATED_EXTERNAL_TICKETS|LIST |STRING |NO |
|ADDITIONAL_DATA |FREE |STRING |NO |
|RELATED_ACTIVITY |MULTIPLE|STRING |NO |
|HISTORY |FREE |STRING |YES |
|AFFECTED_COMMUNITY |FREE |STRING |NO |
|AFFECTED_SERVICE |MULTIPLE|STRING |NO |
|LOCATION |MULTIPLE|STRING |YES |
|NETWORK_NODE |LIST |STRING |NO |
|NETWORK_LINK_CIRCUIT |LIST |STRING |NO |
|END_LINE_LOCATION_A |MULTIPLE|STRING |NO |
|END_LINE_LOCATION_B |MULTIPLE|STRING |NO |
|OPEN_ENGINEER |MULTIPLE|STRING |NO |
|CONTACT_ENGINEERS |LIST |STRING |NO |
|CLOSE_ENGINEER |MULTIPLE|STRING |NO |
|HASH |DEFINED |STRING |NO |
+------------------------+--------+------------------+---------+
+------------------------+--------+------------------+---------+
| FIELD NAME | TYPE |VALID FORMAT |MANDATORY|
+------------------------+--------+------------------+---------+
|PARTNER_ID |MULTIPLE|STRING |YES |
|ORIGINAL_ID |FREE |STRING |YES |
|TT_ID |DEFINED |STRING |YES |
|TT_TITLE |DEFINED |STRING |YES |
|TT_TYPE |MULTIPLE|PREDEFINED STRING |YES |
|TT_PRIORITY |MULTIPLE|PREDEFINED STRING |NO |
|TT_STATUS |MULTIPLE|PREDEFINED STRING |YES |
|TT_SOURCE |MULTIPLE|PREDEFINED STRING |NO |
|TT_OPEN_DATETIME |MULTIPLE|DATETIME |YES |
|TT_CLOSE_DATETIME |MULTIPLE|DATETIME |YES |
|TT_SHORT_DESCRIPTION |MULTIPLE|PREDEFINED STRING |YES |
|TT_LONG_DESCRIPTION |FREE |STRING |NO |
|TYPE |MULTIPLE|PREDEFINED STRING |YES |
|TT_IMPACT_ASSESSMENT |MULTIPLE|PREDEFINED STRING |YES |
|START_DATETIME |MULTIPLE|DATETIME |YES |
|DETECT_DATETIME |MULTIPLE|DATETIME |NO |
|REPORT_DATETIME |MULTIPLE|DATETIME |NO |
|END_DATETIME |MULTIPLE|DATETIME |YES |
|TT_LAST_UPDATE_TIME |MULTIPLE|DATETIME |YES |
|TIME_WINDOW_START |MULTIPLE|DATETIME |NO |
|TIME_WINDOW_END |MULTIPLE|DATETIME |NO |
|WORK_PLAN_START_DATETIME|MULTIPLE|DATETIME |NO |
|WORK_PLAN_END_DATETIME |MULTIPLE|DATETIME |NO |
|RELATED_EXTERNAL_TICKETS|LIST |STRING |NO |
|ADDITIONAL_DATA |FREE |STRING |NO |
|RELATED_ACTIVITY |MULTIPLE|STRING |NO |
|HISTORY |FREE |STRING |YES |
|AFFECTED_COMMUNITY |FREE |STRING |NO |
|AFFECTED_SERVICE |MULTIPLE|STRING |NO |
|LOCATION |MULTIPLE|STRING |YES |
|NETWORK_NODE |LIST |STRING |NO |
|NETWORK_LINK_CIRCUIT |LIST |STRING |NO |
|END_LINE_LOCATION_A |MULTIPLE|STRING |NO |
|END_LINE_LOCATION_B |MULTIPLE|STRING |NO |
|OPEN_ENGINEER |MULTIPLE|STRING |NO |
|CONTACT_ENGINEERS |LIST |STRING |NO |
|CLOSE_ENGINEER |MULTIPLE|STRING |NO |
|HASH |DEFINED |STRING |NO |
+------------------------+--------+------------------+---------+
Figure 43. The Field Name Class
图43。字段名类
Internationalization and localization are of specific concern to the NTTDM, since it is only through collaboration, often across language barriers, that certain incidents can be resolved. The NTTDM supports this goal by depending on XML constructs, and through explicit design choices in the data model.
国际化和本地化是NTTDM特别关注的问题，因为只有通过协作（通常是跨越语言障碍）才能解决某些事件。NTTDM通过依赖XML构造和数据模型中的显式设计选择来支持这一目标。
The main advantage of the model is that it provides a normalized data type that is implemented fully in the English language and can be used conveniently. It also supports free-formed text that can be written in any language. In the future, it will provide translation services for all such free-formed text.
该模型的主要优点是它提供了一种规范化的数据类型，该数据类型完全用英语实现，并且可以方便地使用。它还支持可以用任何语言编写的自由格式文本。今后，它将为所有这些自由格式文本提供翻译服务。
In this section, an example of network TTs exchanged using the proposed format is provided. This is an actual GRNet ticket normalized according to the NTTDM. Fields that were not included in the ticket are left blank.
在本节中，提供了使用所提议的格式交换的网络TTs的示例。这是根据NTTDM标准化的实际GRNet票证。未包含在票证中的字段保留为空。
<?xml version="1.0" encoding="UTF-8"?>
<!-- This example describes a link failure that was detected -->
<?xml version="1.0" encoding="UTF-8"?>
<!-- This example describes a link failure that was detected -->
<NTTDM-Document version="1.00" lang="el"
xmlns="urn:ietf:params:xml:ns:nttdm-1.0">
<Ticket>
<Original_ID>5985</Original_ID>
<Partner_ID>01</Partner_ID>
<TT_ID>01_5985</TT_ID>
<TT_Title>Forth Link Failure</TT_Title>
<TT_Type>Operational</TT_Type>
<TT_Status>Closed</TT_Status>
<TT_Open_Datetime>2008-12-16T10:01:15+02:00</TT_Open_Datetime>
<TT_Short_Description>Core Line Fault</TT_Short_Description>
<TT_Long_Description>Forth Link Failure</TT_Long_Description>
<Type>Unscheduled</Type>
<TT_Impact_Assessment>No connectivity</TT_Impact_Assessment>
<Start_Datetime>2008-12-16T09:55:00+02:00</Start_Datetime>
<TT_Last_Update_Time>2008-12-16T15:00:34+02:00</TT_Last_Update_Time>
<Location>HERAKLION</Location>
<History>Optical transmitter was changed</History>
<TT_Close_Datetime>2008-12-16T15:05:00+02:00</TT_Close_Datetime>
<End_Datetime>2008-12-16T15:01:21+02:00</End_Datetime>
<NTTDM-Document version="1.00" lang="el"
xmlns="urn:ietf:params:xml:ns:nttdm-1.0">
<Ticket>
<Original_ID>5985</Original_ID>
<Partner_ID>01</Partner_ID>
<TT_ID>01_5985</TT_ID>
<TT_Title>Forth Link Failure</TT_Title>
<TT_Type>Operational</TT_Type>
<TT_Status>Closed</TT_Status>
<TT_Open_Datetime>2008-12-16T10:01:15+02:00</TT_Open_Datetime>
<TT_Short_Description>Core Line Fault</TT_Short_Description>
<TT_Long_Description>Forth Link Failure</TT_Long_Description>
<Type>Unscheduled</Type>
<TT_Impact_Assessment>No connectivity</TT_Impact_Assessment>
<Start_Datetime>2008-12-16T09:55:00+02:00</Start_Datetime>
<TT_Last_Update_Time>2008-12-16T15:00:34+02:00</TT_Last_Update_Time>
<Location>HERAKLION</Location>
<History>Optical transmitter was changed</History>
<TT_Close_Datetime>2008-12-16T15:05:00+02:00</TT_Close_Datetime>
<End_Datetime>2008-12-16T15:01:21+02:00</End_Datetime>
<Network_Node>
<Node>FORTH</Node>
</Network_Node>
<Network_Link_Circuit>
<Link_Circuit>FORTH-2</Link_Circuit>
</Network_Link_Circuit>
<Open_Engineer>Dimitris Zisiadis</Open_Engineer>
<Close_Engineer>Guillaume Cessieux</Close_Engineer>
<Contact_Engineers>
<Engineer>Spyros Kopsidas</Engineer>
<Engineer>Chrysostomos Tziouvaras</Engineer>
</Contact_Engineers>
<TT_Priority>High</TT_Priority>
</Ticket>
</NTTDM-Document>
<Network_Node>
<Node>FORTH</Node>
</Network_Node>
<Network_Link_Circuit>
<Link_Circuit>FORTH-2</Link_Circuit>
</Network_Link_Circuit>
<Open_Engineer>Dimitris Zisiadis</Open_Engineer>
<Close_Engineer>Guillaume Cessieux</Close_Engineer>
<Contact_Engineers>
<Engineer>Spyros Kopsidas</Engineer>
<Engineer>Chrysostomos Tziouvaras</Engineer>
</Contact_Engineers>
<TT_Priority>High</TT_Priority>
</Ticket>
</NTTDM-Document>
This section provides a sample XML Schema of the NTTDM.
本节提供了NTTDM的示例XML模式。
<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema xmlns="urn:ietf:params:xml:ns:nttdm-0.1"
xmlns:nttdm="urn:ietf:params:xml:ns:nttdm-1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:nttdm-1.0"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:annotation>
<xs:documentation
>Trouble Ticket Data Model v-1.0</xs:documentation>
</xs:annotation>
<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema xmlns="urn:ietf:params:xml:ns:nttdm-0.1"
xmlns:nttdm="urn:ietf:params:xml:ns:nttdm-1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:ietf:params:xml:ns:nttdm-1.0"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:annotation>
<xs:documentation
>Trouble Ticket Data Model v-1.0</xs:documentation>
</xs:annotation>
<!--
===============================================================
== NTTDM-Document Class ==
===============================================================
-->
<xs:element name="NTTDM-Document">
<xs:complexType>
<xs:sequence>
<xs:element ref="nttdm:Ticket" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="version" type="xs:string" fixed="1.00"/>
<xs:attribute name="lang" type="xs:language" use="required"/>
</xs:complexType>
</xs:element>
<!--
===============================================================
== NTTDM-Document Class ==
===============================================================
-->
<xs:element name="NTTDM-Document">
<xs:complexType>
<xs:sequence>
<xs:element ref="nttdm:Ticket" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="version" type="xs:string" fixed="1.00"/>
<xs:attribute name="lang" type="xs:language" use="required"/>
</xs:complexType>
</xs:element>
<!--
===============================================================
== Ticket Class ==
===============================================================
-->
<xs:element name="Ticket">
<xs:complexType>
<xs:all>
<xs:element ref="nttdm:Partner_ID"/>
<xs:element ref="nttdm:Original_ID"/>
<xs:element ref="nttdm:TT_ID"/>
<xs:element ref="nttdm:TT_Title"/>
<xs:element ref="nttdm:TT_Type"/>
<xs:element ref="nttdm:TT_Priority" minOccurs="0"/>
<xs:element ref="nttdm:TT_Status"/>
<xs:element ref="nttdm:TT_Source" minOccurs="0"/>
<xs:element ref="nttdm:TT_Open_Datetime"/>
<xs:element ref="nttdm:TT_Close_Datetime"/>
<xs:element ref="nttdm:TT_Short_Description"/>
<xs:element ref="nttdm:TT_Long_Description"/>
<xs:element ref="nttdm:Type"/>
<xs:element ref="nttdm:TT_Impact_Assessment"/>
<xs:element ref="nttdm:Start_Datetime"/>
<xs:element ref="nttdm:Detect_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:Report_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:End_Datetime"/>
<xs:element ref="nttdm:TT_Last_Update_Time"/>
<xs:element ref="nttdm:Time_Window_Start" minOccurs="0"/>
<xs:element ref="nttdm:Time_Window_End" minOccurs="0"/>
<xs:element ref="nttdm:Work_Plan_Start_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:Work_Plan_End_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:Related_External_Tickets" minOccurs="0"/>
<xs:element ref="nttdm:Additional_Data" minOccurs="0"/>
<xs:element ref="nttdm:Related_Activity" minOccurs="0"/>
<xs:element ref="nttdm:History"/>
<xs:element ref="nttdm:Affected_Community" minOccurs="0"/>
<xs:element ref="nttdm:Affected_Service" minOccurs="0"/>
<xs:element ref="nttdm:Location"/>
<xs:element ref="nttdm:Network_Node" minOccurs="0"/>
<xs:element ref="nttdm:Network_Link_Circuit" minOccurs="0"/>
<xs:element ref="nttdm:End_Line_Location_B" minOccurs="0"/>
<xs:element ref="nttdm:Open_Engineer" minOccurs="0"/>
<xs:element ref="nttdm:Contact_Engineers" minOccurs="0"/>
<xs:element ref="nttdm:Close_Engineer" minOccurs="0"/>
<xs:element ref="nttdm:Hash" minOccurs="0"/>
<xs:element ref="nttdm:End_Line_Location_A" minOccurs="0"/>
</xs:all>
<!--
===============================================================
== Ticket Class ==
===============================================================
-->
<xs:element name="Ticket">
<xs:complexType>
<xs:all>
<xs:element ref="nttdm:Partner_ID"/>
<xs:element ref="nttdm:Original_ID"/>
<xs:element ref="nttdm:TT_ID"/>
<xs:element ref="nttdm:TT_Title"/>
<xs:element ref="nttdm:TT_Type"/>
<xs:element ref="nttdm:TT_Priority" minOccurs="0"/>
<xs:element ref="nttdm:TT_Status"/>
<xs:element ref="nttdm:TT_Source" minOccurs="0"/>
<xs:element ref="nttdm:TT_Open_Datetime"/>
<xs:element ref="nttdm:TT_Close_Datetime"/>
<xs:element ref="nttdm:TT_Short_Description"/>
<xs:element ref="nttdm:TT_Long_Description"/>
<xs:element ref="nttdm:Type"/>
<xs:element ref="nttdm:TT_Impact_Assessment"/>
<xs:element ref="nttdm:Start_Datetime"/>
<xs:element ref="nttdm:Detect_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:Report_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:End_Datetime"/>
<xs:element ref="nttdm:TT_Last_Update_Time"/>
<xs:element ref="nttdm:Time_Window_Start" minOccurs="0"/>
<xs:element ref="nttdm:Time_Window_End" minOccurs="0"/>
<xs:element ref="nttdm:Work_Plan_Start_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:Work_Plan_End_Datetime" minOccurs="0"/>
<xs:element ref="nttdm:Related_External_Tickets" minOccurs="0"/>
<xs:element ref="nttdm:Additional_Data" minOccurs="0"/>
<xs:element ref="nttdm:Related_Activity" minOccurs="0"/>
<xs:element ref="nttdm:History"/>
<xs:element ref="nttdm:Affected_Community" minOccurs="0"/>
<xs:element ref="nttdm:Affected_Service" minOccurs="0"/>
<xs:element ref="nttdm:Location"/>
<xs:element ref="nttdm:Network_Node" minOccurs="0"/>
<xs:element ref="nttdm:Network_Link_Circuit" minOccurs="0"/>
<xs:element ref="nttdm:End_Line_Location_B" minOccurs="0"/>
<xs:element ref="nttdm:Open_Engineer" minOccurs="0"/>
<xs:element ref="nttdm:Contact_Engineers" minOccurs="0"/>
<xs:element ref="nttdm:Close_Engineer" minOccurs="0"/>
<xs:element ref="nttdm:Hash" minOccurs="0"/>
<xs:element ref="nttdm:End_Line_Location_A" minOccurs="0"/>
</xs:all>
<xs:attribute name="lang" type="xs:language"/>
</xs:complexType>
</xs:element>
<xs:attribute name="lang" type="xs:language"/>
</xs:complexType>
</xs:element>
<!--
===============================================================
== Partner_ID Class ==
===============================================================
-->
<xs:element name="Partner_ID" type="nttdm:string_no_underscore"/>
<!--
===============================================================
== Partner_ID Class ==
===============================================================
-->
<xs:element name="Partner_ID" type="nttdm:string_no_underscore"/>
<!--
===============================================================
== Original_ID Class ==
===============================================================
-->
<xs:element name="Original_ID" type="nttdm:string_no_underscore"/>
<!--
===============================================================
== Original_ID Class ==
===============================================================
-->
<xs:element name="Original_ID" type="nttdm:string_no_underscore"/>
<!--
===============================================================
== TT_ID Class ==
===============================================================
-->
<xs:element name="TT_ID" type="xs:string"/>
<!--
===============================================================
== TT_ID Class ==
===============================================================
-->
<xs:element name="TT_ID" type="xs:string"/>
<!--
===============================================================
== TT_Title Class ==
===============================================================
-->
<xs:element name="TT_Title" type="xs:string"/>
<!--
===============================================================
== TT_Title Class ==
===============================================================
-->
<xs:element name="TT_Title" type="xs:string"/>
<!--
===============================================================
== TT_Type Class ==
===============================================================
-->
<xs:element name="TT_Type" type="nttdm:eTT_Type"/>
<!--
===============================================================
== TT_Type Class ==
===============================================================
-->
<xs:element name="TT_Type" type="nttdm:eTT_Type"/>
<!--
===============================================================
== TT_Priority Class ==
===============================================================
-->
<xs:element name="TT_Priority" type="nttdm:eTT_Priority"/>
<!--
===============================================================
== TT_Priority Class ==
===============================================================
-->
<xs:element name="TT_Priority" type="nttdm:eTT_Priority"/>
<!--
===============================================================
== TT_Status Class ==
===============================================================
-->
<xs:element name="TT_Status" type="nttdm:eTT_Status"/>
<!--
===============================================================
== TT_Status Class ==
===============================================================
-->
<xs:element name="TT_Status" type="nttdm:eTT_Status"/>
<!--
===============================================================
== TT_Source Class ==
===============================================================
-->
<xs:element name="TT_Source" type="nttdm:eTT_Source"/>
<!--
===============================================================
== TT_Source Class ==
===============================================================
-->
<xs:element name="TT_Source" type="nttdm:eTT_Source"/>
<!--
===============================================================
== TT_Open_Datetime Class ==
===============================================================
-->
<xs:element name="TT_Open_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== TT_Open_Datetime Class ==
===============================================================
-->
<xs:element name="TT_Open_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== TT_Close_Datetime Class ==
===============================================================
-->
<xs:element name="TT_Close_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== TT_Close_Datetime Class ==
===============================================================
-->
<xs:element name="TT_Close_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== TT_Short_Description Class ==
===============================================================
-->
<xs:element name="TT_Short_Description"
type="nttdm:eTT_Short_Description"/>
<!--
===============================================================
== TT_Short_Description Class ==
===============================================================
-->
<xs:element name="TT_Short_Description"
type="nttdm:eTT_Short_Description"/>
<!--
===============================================================
== TT_Long_Description Class ==
===============================================================
-->
<xs:element name="TT_Long_Description" type="xs:string"/>
<!--
===============================================================
== TT_Long_Description Class ==
===============================================================
-->
<xs:element name="TT_Long_Description" type="xs:string"/>
<!--
===============================================================
== Type Class ==
===============================================================
-->
<xs:element name="Type" type="nttdm:eType"/>
<!--
===============================================================
== Type Class ==
===============================================================
-->
<xs:element name="Type" type="nttdm:eType"/>
<!--
===============================================================
== TT_Impact_Assessment Class ==
===============================================================
-->
<xs:element name="TT_Impact_Assessment"
type="nttdm:eTT_Impact_Assessment"/>
<!--
===============================================================
== TT_Impact_Assessment Class ==
===============================================================
-->
<xs:element name="TT_Impact_Assessment"
type="nttdm:eTT_Impact_Assessment"/>
<!--
===============================================================
== Start_Datetime Class ==
===============================================================
-->
<xs:element name="Start_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Start_Datetime Class ==
===============================================================
-->
<xs:element name="Start_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Detect_Datetime Class ==
===============================================================
-->
<xs:element name="Detect_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Detect_Datetime Class ==
===============================================================
-->
<xs:element name="Detect_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Report_Datetime Class ==
===============================================================
-->
<xs:element name="Report_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Report_Datetime Class ==
===============================================================
-->
<xs:element name="Report_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== End_Datetime Class ==
===============================================================
-->
<xs:element name="End_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== End_Datetime Class ==
===============================================================
-->
<xs:element name="End_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== TT_Last_Update_Time Class ==
===============================================================
-->
<xs:element name="TT_Last_Update_Time" type="xs:dateTime"/>
<!--
===============================================================
== TT_Last_Update_Time Class ==
===============================================================
-->
<xs:element name="TT_Last_Update_Time" type="xs:dateTime"/>
<!--
===============================================================
== Time_Window_Start Class ==
===============================================================
-->
<xs:element name="Time_Window_Start" type="xs:dateTime"/>
<!--
===============================================================
== Time_Window_Start Class ==
===============================================================
-->
<xs:element name="Time_Window_Start" type="xs:dateTime"/>
<!--
===============================================================
== Time_Window_End Class ==
===============================================================
-->
<xs:element name="Time_Window_End" type="xs:dateTime"/>
<!--
===============================================================
== Time_Window_End Class ==
===============================================================
-->
<xs:element name="Time_Window_End" type="xs:dateTime"/>
<!--
===============================================================
== Work_Plan_Start_Datetime Class ==
===============================================================
-->
<xs:element name="Work_Plan_Start_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Work_Plan_Start_Datetime Class ==
===============================================================
-->
<xs:element name="Work_Plan_Start_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Work_Plan_End_Datetime Class ==
===============================================================
-->
<xs:element name="Work_Plan_End_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Work_Plan_End_Datetime Class ==
===============================================================
-->
<xs:element name="Work_Plan_End_Datetime" type="xs:dateTime"/>
<!--
===============================================================
== Related_External_Tickets Class ==
===============================================================
-->
<xs:element name="Related_External_Tickets"
type="nttdm:eRelated_External_Tickets"/>
<!--
===============================================================
== Related_External_Tickets Class ==
===============================================================
-->
<xs:element name="Related_External_Tickets"
type="nttdm:eRelated_External_Tickets"/>
<!--
===============================================================
== Additional_Data Class ==
===============================================================
-->
<xs:element name="Additional_Data" type="xs:string"/>
<!--
===============================================================
== Additional_Data Class ==
===============================================================
-->
<xs:element name="Additional_Data" type="xs:string"/>
<!--
===============================================================
== Related_Activity Class ==
===============================================================
-->
<xs:element name="Related_Activity"
type="nttdm:eRelated_Activity"/>
<!--
===============================================================
== Related_Activity Class ==
===============================================================
-->
<xs:element name="Related_Activity"
type="nttdm:eRelated_Activity"/>
<!--
===============================================================
== History Class ==
===============================================================
-->
<xs:element name="History" type="xs:string"/>
<!--
===============================================================
== History Class ==
===============================================================
-->
<xs:element name="History" type="xs:string"/>
<!--
===============================================================
== Affected_Community Class ==
===============================================================
-->
<xs:element name="Affected_Community" type="xs:string"/>
<!--
===============================================================
== Affected_Community Class ==
===============================================================
-->
<xs:element name="Affected_Community" type="xs:string"/>
<!--
===============================================================
== Affected_Service Class ==
===============================================================
-->
<xs:element name="Affected_Service" type="xs:string"/>
<!--
===============================================================
== Affected_Service Class ==
===============================================================
-->
<xs:element name="Affected_Service" type="xs:string"/>
<!--
===============================================================
== Location Class ==
===============================================================
-->
<xs:element name="Location" type="xs:string"/>
<!--
===============================================================
== Location Class ==
===============================================================
-->
<xs:element name="Location" type="xs:string"/>
<!--
===============================================================
== Network_Node Class ==
===============================================================
-->
<xs:element name="Network_Node" type="nttdm:eNodes"/>
<!--
===============================================================
== Network_Node Class ==
===============================================================
-->
<xs:element name="Network_Node" type="nttdm:eNodes"/>
<!--
===============================================================
== Network_Link_Circuit Class ==
===============================================================
-->
<xs:element name="Network_Link_Circuit"
type="nttdm:eNetwork_Link_Circuit"/>
<!--
===============================================================
== Network_Link_Circuit Class ==
===============================================================
-->
<xs:element name="Network_Link_Circuit"
type="nttdm:eNetwork_Link_Circuit"/>
<!--
===============================================================
== End_Line_Location_A Class ==
===============================================================
-->
<xs:element name="End_Line_Location_A" type="xs:string"/>
<!--
===============================================================
== End_Line_Location_A Class ==
===============================================================
-->
<xs:element name="End_Line_Location_A" type="xs:string"/>
<!--
===============================================================
== End_Line_Location_B Class ==
===============================================================
-->
<xs:element name="End_Line_Location_B" type="xs:string"/>
<!--
===============================================================
== End_Line_Location_B Class ==
===============================================================
-->
<xs:element name="End_Line_Location_B" type="xs:string"/>
<!--
===============================================================
== Open_Engineer Class ==
===============================================================
-->
<xs:element name="Open_Engineer" type="xs:string"/>
<!--
===============================================================
== Open_Engineer Class ==
===============================================================
-->
<xs:element name="Open_Engineer" type="xs:string"/>
<!--
===============================================================
== Contact_Engineers Class ==
===============================================================
-->
<xs:element name="Contact_Engineers" type="nttdm:eEngineers"/>
<!--
===============================================================
== Contact_Engineers Class ==
===============================================================
-->
<xs:element name="Contact_Engineers" type="nttdm:eEngineers"/>
<!--
===============================================================
== Close_Engineer Class ==
===============================================================
-->
<xs:element name="Close_Engineer" type="xs:string"/>
<!--
===============================================================
== Close_Engineer Class ==
===============================================================
-->
<xs:element name="Close_Engineer" type="xs:string"/>
<!--
===============================================================
== Hash Class ==
===============================================================
-->
<xs:element name="Hash" type="xs:string"/>
<!--
===============================================================
== Hash Class ==
===============================================================
-->
<xs:element name="Hash" type="xs:string"/>
<!--
===============================================================
== Custom types definition ==
===============================================================
-->
<xs:simpleType name="string_no_underscore">
<xs:restriction base="xs:string">
<xs:pattern value="[^_]*"/>
</xs:restriction>
</xs:simpleType>
<!--
===============================================================
== Custom types definition ==
===============================================================
-->
<xs:simpleType name="string_no_underscore">
<xs:restriction base="xs:string">
<xs:pattern value="[^_]*"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="eRelated_External_Tickets">
<xs:sequence>
<xs:element name="TTid" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eRelated_External_Tickets">
<xs:sequence>
<xs:element name="TTid" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eRelated_Activity">
<xs:sequence>
<xs:element name="TT" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eRelated_Activity">
<xs:sequence>
<xs:element name="TT" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eNodes">
<xs:sequence>
<xs:element name="Node" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eNodes">
<xs:sequence>
<xs:element name="Node" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eNetwork_Link_Circuit">
<xs:sequence>
<xs:element name="Link_Circuit" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eNetwork_Link_Circuit">
<xs:sequence>
<xs:element name="Link_Circuit" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eEngineers">
<xs:sequence>
<xs:element name="Engineer" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="eEngineers">
<xs:sequence>
<xs:element name="Engineer" type="xs:string" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:simpleType name="eTT_Type">
<xs:restriction base="xs:string">
<xs:enumeration value="Operational"/>
<xs:enumeration value="Informational"/>
<xs:enumeration value="Administrative"/>
<xs:enumeration value="Test"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Type">
<xs:restriction base="xs:string">
<xs:enumeration value="Operational"/>
<xs:enumeration value="Informational"/>
<xs:enumeration value="Administrative"/>
<xs:enumeration value="Test"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eType">
<xs:restriction base="xs:string">
<xs:enumeration value="Scheduled"/>
<xs:enumeration value="Unscheduled"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eType">
<xs:restriction base="xs:string">
<xs:enumeration value="Scheduled"/>
<xs:enumeration value="Unscheduled"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Priority">
<xs:restriction base="xs:string">
<xs:enumeration value="Low"/>
<xs:enumeration value="Medium"/>
<xs:enumeration value="High"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Priority">
<xs:restriction base="xs:string">
<xs:enumeration value="Low"/>
<xs:enumeration value="Medium"/>
<xs:enumeration value="High"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Short_Description">
<xs:restriction base="xs:string">
<xs:enumeration value="Core Line Fault"/>
<xs:enumeration value="Access Line Fault"/>
<xs:enumeration value="Degraded Service"/>
<xs:enumeration value="Router Hardware Fault"/>
<xs:enumeration value="Router Software Fault"/>
<xs:enumeration value="Routing Problem"/>
<xs:enumeration value="Undefined Problem"/>
<xs:enumeration value="Network Congestion"/>
<xs:enumeration value="Client Upgrade"/>
<xs:enumeration value="IPv6"/>
<xs:enumeration value="QoS"/>
<xs:enumeration value="VoIP"/>
<xs:enumeration value="Other"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Short_Description">
<xs:restriction base="xs:string">
<xs:enumeration value="Core Line Fault"/>
<xs:enumeration value="Access Line Fault"/>
<xs:enumeration value="Degraded Service"/>
<xs:enumeration value="Router Hardware Fault"/>
<xs:enumeration value="Router Software Fault"/>
<xs:enumeration value="Routing Problem"/>
<xs:enumeration value="Undefined Problem"/>
<xs:enumeration value="Network Congestion"/>
<xs:enumeration value="Client Upgrade"/>
<xs:enumeration value="IPv6"/>
<xs:enumeration value="QoS"/>
<xs:enumeration value="VoIP"/>
<xs:enumeration value="Other"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Impact_Assessment">
<xs:restriction base="xs:string">
<xs:enumeration value="No impact"/>
<xs:enumeration value="Reduced redundancy"/>
<xs:enumeration value="Minor performance impact"/>
<xs:enumeration value="Severe performance impact"/>
<xs:enumeration value="No connectivity"/>
<xs:enumeration value="On backup"/>
<xs:enumeration value="At risk"/>
<xs:enumeration value="Unknown"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Impact_Assessment">
<xs:restriction base="xs:string">
<xs:enumeration value="No impact"/>
<xs:enumeration value="Reduced redundancy"/>
<xs:enumeration value="Minor performance impact"/>
<xs:enumeration value="Severe performance impact"/>
<xs:enumeration value="No connectivity"/>
<xs:enumeration value="On backup"/>
<xs:enumeration value="At risk"/>
<xs:enumeration value="Unknown"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Status">
<xs:restriction base="xs:string">
<xs:enumeration value="Opened"/>
<xs:enumeration value="Updated"/>
<xs:enumeration value="Closed"/>
<xs:enumeration value="Solved"/>
<xs:enumeration value="Opened/Closed"/>
<xs:enumeration value="Inactive"/>
<xs:enumeration value="Cancelled"/>
<xs:enumeration value="Reopened"/>
<xs:enumeration value="Superseded"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Status">
<xs:restriction base="xs:string">
<xs:enumeration value="Opened"/>
<xs:enumeration value="Updated"/>
<xs:enumeration value="Closed"/>
<xs:enumeration value="Solved"/>
<xs:enumeration value="Opened/Closed"/>
<xs:enumeration value="Inactive"/>
<xs:enumeration value="Cancelled"/>
<xs:enumeration value="Reopened"/>
<xs:enumeration value="Superseded"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="eTT_Source">
<xs:restriction base="xs:string">
<xs:enumeration value="Users"/>
<xs:enumeration value="Monitoring"/>
<xs:enumeration value="Other NOC"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
<xs:simpleType name="eTT_Source">
<xs:restriction base="xs:string">
<xs:enumeration value="Users"/>
<xs:enumeration value="Monitoring"/>
<xs:enumeration value="Other NOC"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
The NTTDM data model defines a data model and the relevant XML Schema for trouble ticket normalization; as such, the NTTDM itself does not raise any security concerns. However, some security issues SHOULD be considered as network TTs could carry sensitive information (IP addresses, contact details, authentication details, commercial providers involved, etc.) about flagship institutions (military, health centre...).
NTTDM数据模型定义了用于故障单规范化的数据模型和相关XML模式；因此，NTTDM本身不会引起任何安全问题。但是，应考虑一些安全问题，因为网络TTs可能携带有关旗舰机构（军事、卫生中心等）的敏感信息（IP地址、联系方式、身份验证详细信息、涉及的商业提供商等）。
The security considerations MAY involve measures during the exchange as well as during processing of the information.
安全考虑可能涉及交换期间以及信息处理期间的措施。
The HASH field is intended to provide an integrity insurance attribute within the exchanged tickets; however, it alone does not ensure integrity.
散列字段用于在交换的票据内提供完整性保险属性；然而，单靠它并不能确保完整性。
Confidentiality MAY be ensured by encrypting whole tickets or only some parts of them. This could permit meaningful tickets to be disclosed, while only sensitive information would be protected.
可以通过加密整张票或只加密其中的一部分来确保机密性。这可以允许有意义的票据被披露，而只有敏感信息才会受到保护。
Peer entity authentication SHOULD be provided in order to establish a session with data origin authentication, regardless of the form in which the TTs are exchanged -- being delivered either through email, web forms, or through a Simple Object Access Protocol (SOAP) service. SOAP is considered the better choice; the model itself, though, does not specify the communications requirements.
应该提供对等实体身份验证，以便建立具有数据源身份验证的会话，而不管TTs是以何种形式交换的——通过电子邮件、web表单或简单对象访问协议（SOAP）服务传递。肥皂被认为是更好的选择；不过，模型本身并没有指定通信需求。
The underlying communications service MUST provide guarantees to properly address integrity, confidentiality, and peer entity authentication. The selection of the enforcing mechanisms is not in the scope of this document, and the choice is up to the implementers.
底层通信服务必须提供保证，以正确处理完整性、机密性和对等实体身份验证。强制执行机制的选择不在本文档的范围内，由实施者进行选择。
For data processing security, each participating organization MAY use its own privacy policy, as part of its own data processing system. This approach avoids any interoperability issues and does not pose any extra burden for the adoption of the current scheme into the operational procedures of the NOCs. Unauthorized and inappropriate usage MUST be avoided.
为了数据处理安全，每个参与组织都可以使用自己的隐私政策，作为自己数据处理系统的一部分。这种方法避免了任何互操作性问题，并且不会对将当前方案纳入国家奥委会的操作程序造成任何额外负担。必须避免未经授权和不适当的使用。
This document uses URNs to describe an XML namespace and Schema conforming to a registry mechanism described in [7].
本文档使用URN来描述符合[7]中描述的注册表机制的XML名称空间和模式。
Registration for the NTTDM namespace:
注册NTTDM命名空间：
o URI: urn:ietf:params:xml:ns:nttdm-1.0
o URI:urn:ietf:params:xml:ns:nttdm-1.0
o Registrant Contact: See the first author listed in the "Authors' Addresses" section of this document.
o 注册人联系人：见本文件“作者地址”部分列出的第一作者。
o XML: None. Namespace URIs do not represent an XML specification.
o XML：没有。命名空间URI不表示XML规范。
Registration for the NTTDM XML Schema:
注册NTTDM XML架构：
o URI: urn:ietf:params:xml:schema:nttdm-1.0
o URI:urn:ietf:params:xml:schema:nttdm-1.0
o Registrant Contact: See the first author listed in the "Authors' Addresses" section of this document.
o 注册人联系人：见本文件“作者地址”部分列出的第一作者。
o XML: See the XML Schema in Section 6 of this document.
o XML：请参阅本文档第6节中的XML模式。
Leandros Tassiulas Centre for Research and Technology Hellas 6th km Thermi-Thessaloniki, 57001 Hellas
Leandros Tassiulas研究与技术中心Hellas 6公里Therma Thessaloniki，57001 Hellas
EMail: leandros@uth.gr
EMail: leandros@uth.gr
Chrysostomos Tziouvaras Greek Research and Technology Network 56, Mesogion Av. 11527, Athens Hellas
Chrysostomos Tziouvaras希腊研究和技术网络56，Mesogion Av。11527，雅典希腊
EMail: tziou@grnet.gr
EMail: tziou@grnet.gr
Xavier Jeannin National Centre for Scientific Research Network Unit - UREC France
Xavier Jeannin国家科学研究中心网络单位-法国UREC
EMail: Xavier.Jeannin@urec.cnrs.fr
EMail: Xavier.Jeannin@urec.cnrs.fr
The following groups and individuals contributed substantially to this document and are gratefully acknowledged:
以下团体和个人对本文件作出了重大贡献，谨此致谢：
- Toby Rodwell and Emma Apted (DANTE)
- 托比·罗德韦尔和艾玛·阿普特（但丁）
- Claudio Allocchio, Gloria Vuagnin, and Claudia Battista (GARR)
- 克劳迪奥·阿洛乔、格洛丽亚·沃宁和克劳迪娅·巴蒂斯塔（加尔）
- Karin Schauerhammer and Robert Stoy (DFN)
- Karin Schauerhammer和Robert Stoy（DFN）
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] World Wide Web Consortium, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation, 26 November 2008, <http://www.w3.org/TR/2008/REC-xml-20081126>.
[2] 万维网联盟，“可扩展标记语言（XML）1.0（第五版）”，W3C建议，2008年11月26日<http://www.w3.org/TR/2008/REC-xml-20081126>.
[3] World Wide Web Consortium, "XML Schema Part 0: Primer Second Edition", W3C Recommendation, 28 October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/>.
[3] 万维网联盟，“XML模式第0部分：入门第二版”，W3C建议，2004年10月28日<http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/>.
[4] World Wide Web Consortium, "XML Schema Part 1: Structures Second Edition", W3C Recommendation, 28 October 2004, <http://www.w3.org/TR/xmlschema-1/>.
[4] 万维网联盟，“XML模式第1部分：结构第二版”，W3C建议，2004年10月28日<http://www.w3.org/TR/xmlschema-1/>.
[5] World Wide Web Consortium, "XML Schema Part 2: Datatypes Second Edition", W3C Recommendation, 28 October 2004, <http://www.w3.org/TR/xmlschema-2/>.
[5] 万维网联盟，“XML模式第2部分：数据类型第二版”，W3C建议，2004年10月28日<http://www.w3.org/TR/xmlschema-2/>.
[6] World Wide Web Consortium, "Namespaces in XML 1.0 (Third Edition)", W3C Recommendation, 8 December 2009, <http://www.w3.org/TR/2009/REC-xml-names-20091208/>.
[6] 万维网联盟，“XML 1.0中的名称空间（第三版）”，W3C建议，2009年12月8日<http://www.w3.org/TR/2009/REC-xml-names-20091208/>.
[7] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004.
[7] Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，2004年1月。
[8] Enabling Grids for E-sciencE, http://www.eu-egee.org/.
[8] 为电子科学启用网格，http://www.eu-egee.org/.
[9] Enabling Grids for E-sciencE, "ENOC, EGEE Network Operation Centre", http://technical.eu-egee.org/index.php?id=353.
[9] 为电子科学启用网格，“ENOC，EGEE网络运营中心”，http://technical.eu-egee.org/index.php?id=353.
[10] Rumbaugh, J., Jacobson, I., and G. Booch, "The Unified Modeling Language Reference Manual," ISBN 020130998X, Addison-Wesley, 1998.
[10] Rumbaugh，J.，Jacobson，I.，和G.Booch，“统一建模语言参考手册”，ISBN 02030998X，Addison-Wesley，1998年。
[11] Johnson, D., "NOC Internal Integrated Trouble Ticket System Functional Specification Wishlist ("NOC TT REQUIREMENTS")", RFC 1297, January 1992.
[11] Johnson，D.，“NOC内部集成故障单系统功能规范愿望列表（“NOC TT要求”），RFC 1297，1992年1月。
Authors' Addresses
作者地址
Dimitris Zisiadis (editor) Centre for Research and Technology Hellas 6th km Thermi-Thessaloniki, 57001 Hellas
Dimitris Zisiadis（编辑）Hellas研究和技术中心，距离Therma Thessaloniki 6公里，57001 Hellas
EMail: dzisiadis@iti.gr
EMail: dzisiadis@iti.gr
Spyros Kopsidas (editor) Centre for Research and Technology Hellas 6th km Thermi-Thessaloniki, 57001 Hellas
斯皮罗斯·科普西达斯（编辑）希腊研究与技术中心，距离塞萨洛尼基6公里，邮编57001
EMail: spyros@uth.gr
EMail: spyros@uth.gr
Matina Tsavli (editor) Centre for Research and Technology Hellas 6th km Thermi-Thessaloniki, 57001 Hellas
Matina Tsavli（编辑）Hellas研究和技术中心，距离Therma Thessaloniki 6公里，57001 Hellas
EMail: sttsavli@uth.gr
EMail: sttsavli@uth.gr
Guillaume Cessieux (editor) Computer Centre of National Institute for Nuclear Physics and Particle Physics (IN2P3-CC) France
Guillaume Cessieux（编辑）法国国家核物理和粒子物理研究所（IN2P3-CC）计算机中心
EMail: Guillaume.Cessieux@cc.in2p3.fr
EMail: Guillaume.Cessieux@cc.in2p3.fr