1、 ATIS-0300021 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part III, Installation, Testing and Maintenance Responsibilities for SS7 Links and Trunks Attachment J SS7 Software Validation Version 12.0 ATIS is the leading technical planning and standards development organ
2、ization committed to the rapid development of global, market-driven standards for the information, 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 Wire
3、less Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle,
4、IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American 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
5、a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American 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
6、Next Generation Interconnection Interoperability Forum (NGIIF). The NGIIF addresses next-generation network interconnection and interoperability issues associated with emerging technologies. Specifically, it develops operational procedures which involve the network aspects of architecture, disaster
7、preparedness, installation, maintenance, management, reliability, routing, security, and testing 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 ch
8、anges to this document shall be made through the NGIIF issue resolution process. Note Regarding Previous 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 ver
9、sion of the NOF Reference Document is Issue 13. Disclaimer and Limitation of Liability The information 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 engineerin
10、g or other professional standards and applicable regulations. No recommendation as to products or 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 FU
11、RTHER NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE 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 EVE
12、NT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES THAT ANY AND ALL USE OF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0300021, NGIIF Reference Document, Part III, Installation and Maintenance
13、Responsibilities for SS7 Links and Trunks, Attachment J, SS7 Software Validation, Formerly NIIF 5016 The NGIIF Reference Document, Part III, Installation and Maintenance Responsibilities for SS7 Links and Trunks, Attachment J, SS7 Software Validation, is an ATIS standard developed by the NGIIF. Publ
14、ished 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. 2 No part of this publication may be reproduced in any form, in an electronic retrieval system or ot
15、herwise, 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. 3 SS7 SOFTWARE VALIDATION Table of Contents 1 GENERAL 5 1.1 PURPOSE . 5 1.2 DEFINITIONS . 5 1.3 PURPOSE OF SOFTWARE VALIDATION. 5
16、 2 BASIC PREMISES 5 3 OPERATING PRINCIPLES 6 4 CRITERIA FOR SERVICE PROVIDERS AND VENDOR/MANUFACTURERS . 6 5 SERVICE PROVIDER (ASP/ASC) REQUIREMENTS 6 5.1 WRITTEN REQUIREMENTS 6 5.2 STANDARDS INTERPRETATIONS 7 5.3 GENERAL NETWORK DOCUMENTATION . 7 5.4 NETWORK UNIQUENESS DOCUMENTATION 7 6 VENDOR/MANU
17、FACTURER SOFTWARE VALIDATION CRITERIA . 7 6.1 VENDOR/MANUFACTURER REQUIREMENTS . 7 7 VENDOR/MANUFACTURER PRODUCT IMPLEMENTATION . 7 7.1 OPTIONAL REQUIREMENTS . 8 7.2 CONFORMANCE TO REQUIREMENTS . 8 7.3 CROSS-PRODUCT IMPLEMENTATION . 8 8 VENDOR/MANUFACTURER PRODUCT TESTING . 8 8.1 TESTING ENVIRONMENT
18、 . 8 8.2 CONFORMANCE TO PRODUCT REQUIREMENTS . 8 8.3 PRODUCT PERFORMANCE . 9 8.4 SYSTEM FAULT TOLERANCE . 9 8.5 SYSTEM RECOVERY 9 8.6 METHODS AND PROCEDURES 9 8.7 REGRESSION TESTING . 9 8.8 FEATURE INTERACTION TESTING 9 8.9 MULTI-VENDOR INTEROPERABILITY 9 8.10 SOFTWARE UPDATES/CHANGES . 10 8.11 TEST
19、ING INFORMATION 10 9 VENDOR/MANUFACTURER PRODUCT DEPLOYMENT 10 9.1 PROBLEM RESOLUTION . 10 9.2 ROOT CAUSE ANALYSIS . 10 10 SERVICE PROVIDER TESTING/DEPLOYMENT . 10 10.1 INTEGRATION TESTING . 10 10.2 METHODS AND PROCEDURES 11 10.3 SOFTWARE UPDATE/CHANGES . 11 10.4 MULTI-VENDOR INTEROPERABILITY TESTIN
20、G 11 10.5 VENDOR/MANUFACTURER DOCUMENTATION 11 10.6 NEW SOFTWARE . 11 10.7 UPDATES 11 5 1 General 1.1 Purpose This document is intended to provide general guidelines for the Development and Validation of Software for use in the Telecommunications industry as it applies to Interconnected switching/si
21、gnaling nodes. It represents Network Interconnection Interoperability Forum (NGIIF) consensus arrived at by participating members consisting of Access Service Providers, Access Service Customers and Vendor/Manufacturers. Although aimed at SS7 software, the guidelines are deemed generally applicable
22、to other types of software in use by the Telecommunications Industry. This document does not replace or supersede any existing Contracts, Tariffs or any other legally binding documents. 1.2 Definitions For the purposes of this document the following terms apply: Vendor/Manufacturer refers to those c
23、ompanies that develop and supply software to the Telecommunications industry for switching/signaling node application. Service Provider refers to Access Service Providers and Access Service Customers purchasing software from Vendor/Manufacturers of telecommunications software products. Product: In t
24、he context of this document the term product shall be defined as the “software“ package under development or validation. Service Provider Product requirements: Capabilities as defined by the Service Provider and Industry standards which drive the development of the product. Product Implementation: T
25、he process by which the Service Provider Product requirements are incorporated into a soft-ware product whether or not it currently exists. 1.3 Purpose of Software Validation The purpose of software product validation as described in this document is to provide assurance to all users of software as
26、it applies to the telecommunications industry, that the software products perform according to “agreed upon“ service provider product requirements and that all reasonable care has been taken to identify and correct any anomalies that have the potential to negatively impact the operation of switching
27、/signaling nodes so that the quality of service is continually enhanced to meet or exceed the customers expectations. 2 Basic Premises Service Providers of telecommunications service have an obligation to their Customers to provide the highest standard of error free service. Vendor/Manufacturers of
28、telecommunications switching/signaling node software have a responsibility to the Service Providers of telecommunications services to provide the highest standard of error free software possible. An uncompromised focus on the development/validation of error free software will result in improved qual
29、ity and reliability of the switching/signaling nodes and networks. 6 3 Operating Principles Service Providers should have “agreed upon“ procedures in place with their Vendor/Manufacturers to provide continuous assurance for the quality of software prior to and after deployment in their respective sw
30、itching/signaling networks. When the need for information exchange is identified, such information should be shared in accordance with the guidelines outlined in the Network Interconnection Interoperability Forum (NGIIF) document, titled Information Sharing. For example, signaling anomalies identifi
31、ed in the NGIIF Internetwork Interoperability Test Plan (IITP) testing, or individual software customer problems as they relate to potential non-conformance with industry standards should be shared with the affected Service Provider. Vendor/Manufacturers should review their software development/vali
32、dation processes to continually enhance their capability to identify and fix potential software problems prior to deployment. The Vendor/Manufacturer and their respective Service Provider(s) should utilize knowledge gained during software product testing and deployment phases to augment their testin
33、g procedures, for the purpose of identifying and eliminating potential non-conformance prior to subsequent product to deployment. 4 Criteria for Service Providers and Vendor/Manufacturers In the subsections that follow, this document defines criteria that should be followed by the Service Provider a
34、nd/or Vendor/Manufacturer for software product validation throughout the development process, to achieve the general objectives defined in section 2 of this document. The following subsections are: Service Providers requirements Vendor/Manufacturers requirements Vendor/Manufacturers Implementation V
35、endor/Manufacturers Testing Service Providers Pre-deployment Testing Service Providers Deployment Testing 5 Service Provider (ASP/ASC) Requirements This section defines the responsibilities of the Service Providers in regard to providing their requirements to the Vendor/Manufacturer. 5.1 Written Req
36、uirements Service Providers should provide explicit written requirements for capabilities requested from their Vendor/Manufacturers. Service Providers should ensure that their requirements are clear and complete; these requirements may reference industry standards. Service Providers should define in
37、 writing those standards/requirements that they desire the capabilities to conform to. Specific documents and versions should be identified during the requirements phase. When the standards/requirements specifications used include optional capabilities, the Service Providers should identify in writi
38、ng those options desired. 7 5.2 Standards Interpretations If the Service Provider perceives a standard to be ambiguous, incorrect or flawed, (e.g., open to multiple interpretations), the Service Provider should document their required implementation as early in the requirements phase as possible. In
39、 addition the Service Provider should interface with the appropriate standards body to clarify any ambiguities. The Vendor/Manufacturer should review this information, and provide feedback to the Service Provider during the requirements phase. 5.3 General Network Documentation Service Providers may
40、provide documentation to their Vendor/Manufacturer before the end of the requirements phase describing their network environment. 5.4 Network Uniqueness Documentation This documentation may include any specific test scenarios or situations that may be unique to their network to the Vendor/Manufactur
41、er during the requirements phase. Where requirements are Service Provider specific, the Service Provider shall engage in dialogue with their Vendor/Manufacturer to ensure understanding of those requirements. 6 Vendor/Manufacturer Software Validation Criteria 6.1 Vendor/Manufacturer Requirements The
42、software validation criteria for the requirements are as follows: Known Non-conformance to Requirements - The Vendor/Manufacturer shall provide documentation to the Service Provider identifying all known/anticipated non-conformance(s) to Service Provider Product requirements. For example, a known no
43、n-conformance could exist when a Vendor/Manufacturer only implements a subset of a standard. The Service Provider should review this information, and provide prompt feedback to the Vendor/Manufacturer during the requirements phase. Standards Interpretations - If the Vendor/Manufacturer perceives a s
44、tandard to be ambiguous, incorrect or flawed, (e.g., open to multiple interpretations), the Vendor/Manufacturer should document their planned implementation as early in the requirements phase as possible. In addition the Vendor/Manufacturer should interface with the appropriate standards body for cl
45、arification of any ambiguities. The Service Provider should review this information, and provide feedback to the Vendor/Manufacturer during the requirements phase. Service Provider Changes/Upgrades - All Service Provider requirements including “agreed upon“ changes/upgrades will be documented by the
46、 Vendor/Manufacturer and Service Provider prior to completion of the requirements phase. 7 Vendor/Manufacturer Product Implementation The software validation criteria for Product Implementation are as follows: 8 7.1 Optional Requirements When Service Provider Product requirements include options (e.
47、g., optional parameters or procedures), the Vendor/Manufacturer should provide documentation to the Service Provider identifying which option(s), if any, the Vendor/Manufacturer plans to implement. The Service Provider should review this information, and provide feedback to the Vendor/Manufacturer p
48、roactively. 7.2 Conformance to Requirements The Vendor/Manufacturer should ensure that the software implemented conforms to all specified and “agreed upon“ requirements taking into consideration any documented non-conformance(s) and “agreed upon“ interpretations. The Vendor/Manufacturer shall docume
49、nt all known deviations from Service Provider requirements in regards to capability of the product being implemented. Such information should be provided to the Service Provider at commencement of the software implementation phase and on an ongoing basis. Service Providers should review such information and provide feedback to their Vendor/Manufacturer. 7.3 Cross-product Implementation The Vendor/Manufacturer should ensure that interoperability incompatibilities are not implemented between Switching/Signaling Nodes in their product line. 8 Vendor/Manufactur
