1、 ATIS-0300028 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part VII, Information Sharing Version 12.0 ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information
2、, entertainment and communications industry. More than 200 companies actively formulate standards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Archi
3、tectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American
4、Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the Am
5、erican National Standards Institute (ANSI). For more information, please visit www.atis.org. Notice This document was developed by the Alliance for Telecommunications Industry Solutions (ATIS) sponsored Next Generation Interconnection Interoperability Forum (NGIIF). The NGIIF addresses next-generati
6、on network interconnection and interoperability issues associated with emerging technologies. Specifically, it develops operational procedures which involve the network aspects of architecture, disaster preparedness, installation, maintenance, management, reliability, routing, security, and testing
7、between network operators. In addition, the NGIIF addresses issues which impact the interconnection of existing and next generation networks and facilitate the transition to emerging technologies. All changes to this document shall be made through the NGIIF issue resolution process. Note Regarding P
8、revious Versions The NIIF Reference Document was formerly known as the Network Operations Forum (NOF) Reference Document. The NOF Reference Document was published and maintained by Bellcore. The last version of the NOF Reference Document is Issue 13. Disclaimer and Limitation of Liability The inform
9、ation provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or
10、 vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURP
11、OSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRE
12、SSLY ADVISES THAT ANY AND ALL USE OF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0300028, NGIIF Reference Document, Part VII, Information Sharing, Formerly NIIF 5024 The NGIIF Reference Document, Part VII, Information Sharing, is an ATIS standard devel
13、oped by the NGIIF Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2011 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic re
14、trieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. 2 INFORMATION SHARING Table of Contents 1. GENERAL 3 A. Purpose 3 B. Applicability 3 C. Definition 3 D. Docum
15、ent Organization 3 E. Purpose Of Information Sharing 3 2. BASIC PREMISES 4 3. CRITERIA FOR SHARING INFORMATION 4 4. OPERATING PRINCIPLES 4 5. SCOPE 5 6. SERVICE PROVIDER RESPONSIBILITIES 6 A. Service Provider Stand Alone Testing Environment 6 B. Compatibility Testing Between Service Providers 6 C. S
16、ervice Provider Daily Operation 6 D. Service Providers 6 E. Documentation 6 7. VENDOR/MANUFACTURER RESPONSIBILITIES 7 A. Vendor/Manufacturer And Customer (Customer Reported) 7 B. Customer/Vendor/Manufacturer To Interconnected Service Providers 7 C. Vendors/Manufacturers 7 D. Vendor/Manufacturer Disc
17、overed Problems 8 E. Differences In Specifications Interpretation 8 8. INFORMATION TO BE SHARED BETWEEN VENDOR/MANUFACTURER AND CUSTOMER 8 9. INFORMATION TO BE SHARED BETWEEN CUSTOMER AND VENDOR/MANUFACTURER 9 10. MODES OF COMMUNICATION 9 A. Proactive Notification Mode 10 B. Vendor/Manufacturer Elec
18、tronic Message System Mode 10 11. FACILITY OUTAGE REPORTING GUIDELINES 10 3 1 GENERAL 1.1 Purpose This document is intended to provide the appropriate guidance to facilitate the sharing of information. It identifies types of information which may be shared, the circumstances under which it should be
19、 shared, the extent to which sharing is appropriate, and the mechanisms and timing for that sharing. It represents industry consensus arrived at with the full participation of members of the Network Interconnection Interoperability Forum which consists of Access Service Providers, Access Service Cus
20、tomers and Vendor/Manufacturers. 1.2 Applicability This document is intended to be a living document, therefore subject to revision and upgrading under the Carrier Liaison Committee guidelines. This document does not replace or supersede any existing Contracts, Tariffs or any other legally binding d
21、ocuments. 1.3 Definition For the purposes of this document the term Service Provider is used to indicate both Access Service Providers (ASP) and Access Service Customers (ASC). 1.4 Document Organization The remainder of this document is organized into the following sections: Purpose of Information S
22、haring Basic premises Criteria Operating principles Scope Service Provider responsibilities Vendor/Manufacturer responsibilities Information to be shared Modes of communication(s) 1.5 Purpose of Information Sharing The purpose of information sharing as described in this document is to enable all ser
23、vice providers and vendor/manufacturers to utilize information uncovered by other service providers and/or vendor/manufacturers through the testing, validation and application of software, hardware, and documentation; procedural issues; and conformance to agreed upon standards in order to: 4 Minimiz
24、e the possibility of major outages and service interruptions that can affect our collective customers service, Maintain and improve the reliability, security, capacity, and performance of our interconnected networks, Meet or exceed the expectations of our “customers“. Such information sharing may al
25、so serve to reduce the need for repetitive or redundant testing. 2 BASIC PREMISES Telecommunications Service Providers and Vendors/Manufacturers have an obligation to their collective Customers to cooperatively provide assurance for the integrity of the public switched telephone network. Information
26、 associated with testing and/or problem/failure scenarios of the network can and will provide invaluable assistance when shared with other Service Providers and/or Vendors/Manufacturers. The sharing and use of this information may: Minimize and/or prevent failures Minimize and/or prevent degradation
27、 of the network Minimize and/or prevent reoccurrence of the same problem in another network Assist in problem resolution 3 CRITERIA FOR SHARING INFORMATION Information uncovered by any Service Provider or Vendor/Manufacturer which reveals the potential for loss of service or compromise in the reliab
28、ility, security, capacity, or performance in a single network or interconnected networks should be proactively shared with those parties whose networks and/or products may be impacted by the problem. 4 OPERATING PRINCIPLES The party(ies) identifying a problem should determine/agree on the source/cau
29、se of the problem prior to communicating the source/cause to other parties. No party(ies) should divulge information concerning a problem/failure that is believed to be attributable to a Vendor/Manufacturer or Service Provider without first obtaining written permission to disclose such information f
30、rom the Vendor/Manufacturer or Service Provider in question. The party(ies) uncovering an actual or potential problem are in a unique position to see that the problem is communicated to the appropriate parties and resolved. Although they may not bear responsibility for the problem and/or may not be
31、in a position to actually share the appropriate information, the party(ies) uncovering a potential problem should assume a proactive role in encouraging those parties in a position to share the information to follow the guidelines outlined in this document. Vendors/Manufacturers should research all
32、troubles/issues referred to them to ensure that any similar or related troubles/issues in other platforms are addressed. In addition Vendor/Manufacturers should research all generic troubles/issues made available to the industry (e.g., IITP reports) to ensure that these anomalies are not replicated
33、in their product(s) or platform(s). Implementation of these guidelines represents a cooperative effort on the part of industry participants to assure the reliability and security of the interconnected telecommunications networks. It may occur that in the interest of 5 promoting network reliability,
34、parties may exchange information about their networks/products that could be used in a negative fashion against that companies image, products or network. Use of such information for purposes of securing a competitive advantage is contrary to the spirit and intent of these guidelines. Misuse of info
35、rmation provided under these guidelines may jeopardize subsequent information exchange. Each industry participant has an individual responsibility to develop and maintain procedures for reporting events related to network security. 5 SCOPE The scope of this Document includes the exchange of informat
36、ion between the following parties: A Vendor/Manufacturer and its Customer(s) A Vendor/Manufacturer and its Customer and that Customers interconnected Service Providers Vendors/Manufacturers Access Service Providers Access Service Providers and Access Service Customers The exchange of information bet
37、ween the following parties is explicitly outside the scope of this Document: Access Service Customers/Providers and the FCC Access Service Customers This Document is intended both to supplement existing practices and to establish new practices for information exchange. The following list is intended
38、 to represent a complete list of sources of information for sharing. The identified sources include: Service Provider Stand alone Testing environment Compatibility testing between Service Providers Service Provider daily operations Service Provider outage reports and analysis Service Provider and/or
39、 Vendor/Manufacturer documentation Service Provider Security Reports and Analysis Vendor/Manufacturer development testing Vendor/Manufacturer trouble information reports and analysis Vendor/Manufacturer trouble resolution reports Observed ambiguities or differences in requirements interpretations 6
40、6 SERVICE PROVIDER RESPONSIBILITIES This section describes the responsibilities of Access Service Providers and Access Service Customers in the area of information exchange. Service Provider sharing of information is subject to the “General Operating Principles“ described in Section 4 of this Docume
41、nt. 6.1 Service Provider Stand Alone Testing Environment Any testing results obtained by the Service Provider that identify defects or potential defects with a Vendor/Manufacturer product should be communicated to the Vendor/Manufacturer within 1 business day of the completion of testing analysis. W
42、here conformance to accepted industry standards is in question the Service Provider should inform/consult with their Vendor/Manufacturer within 1 business day of such a determination. 6.2 Compatibility Testing Between Service Providers Where compatibility testing between interconnected Service Provi
43、ders identifies an incompatibility or problem due for example to translations, differences in software releases, software changes, network architecture, and/or differences in requirements interpretations between Vendor/Manufacturer products, they should work individually or cooperatively to ascertai
44、n the cause of the problem. Once identified they should initiate information sharing to potentially affected Carriers/Vendor/Manufacturers as per these guidelines. 6.3 Service Provider Daily Operation Any problems encountered during the normal course of day-to-day operations that are identified as r
45、esulting in whole or part from problem(s) with the Vendor/Manufacturers product should be communicated to the Vendor/Manufacturer within 1 business day of such a determination. The information to be shared is described in Section 9. Problems that are identified as other than a Vendor/Manufacturers p
46、roduct and have the potential to cause loss of service or compromise in the reliability, security, capacity, or performance in an interconnected network should be communicated by the identifying Service Provider to potentially affected Service Provider(s). These problem should be referred within 1 b
47、usiness day of such a determination, or in the case of security, in accordance with internal company or inter company security procedures. 6.4 Service Providers Where a breach of network security has been experienced and it has been determined to be a Vendor/Manufacturer Hardware/Software problem, t
48、he Service Provider shall notify their Vendor/Manufacturer in accordance with their internal company and inter-company security procedures. 6.5 Documentation When the utilization of Standards or Methods and Procedures identifies a problem with Service Provider and/or Vendor/Manufacturer documentatio
49、n that could result in the loss of service or compromise in the reliability, security, capacity, or performance of the network, should be reported to the issuing company. This problem should be referred within 1 business day, or in the case of security, in accordance with internal company or inter company security procedures. 7 The company that issued the methods and procedures should evaluate the identified problem and initiate a correction. The correction should be provided to all known users of the affected docume
