ATIS 0300022-2011 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part III Installation Testing and Maintenance Responsibilities for SS7 Links and Trunk.pdf

《ATIS 0300022-2011 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part III Installation Testing and Maintenance Responsibilities for SS7 Links and Trunk.pdf》由会员分享，可在线阅读，更多相关《ATIS 0300022-2011 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part III Installation Testing and Maintenance Responsibilities for SS7 Links and Trunk.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0300022 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part III, Installation, Testing and Maintenance Responsibilities for SS7 Links and Trunks Attachment K, Dual STP Failure Prevention Procedures (Formerly NIIF 5017) Version 12.0 ATIS is the leading technical pla

2、nning and standards development organization 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,

3、 Energy Efficiency, IP-Based and Wireless 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, Ma

4、chine-to-Machine, Connected Vehicle, 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

5、 and Telecommunications Sectors, and 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

6、 Industry Solutions (ATIS) sponsored 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 netwo

7、rk aspects of architecture, disaster 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 transi

8、tion to emerging technologies. All changes 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

9、 maintained by Bellcore. The last version 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 accordan

10、ce with generally accepted engineering 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, GO

11、VERNMENTAL RULE OR REGULATION, AND FURTHER 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, WIT

12、H RESPECT TO ANY CLAIM, AND IN NO EVENT 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-0300022, NGIIF Reference Document, Pa

13、rt III, Installation and Maintenance Responsibilities for SS7 Links and Trunks, Attachment K, Dual STP Failure Prevention Procedures, Formerly NIIF 5017 The NGIIF Reference Document, Part III, Installation and Maintenance Responsibilities for SS7 Links and Trunks, Attachment K, Dual STP Failure Prev

14、ention Procedures, is an ATIS standard developed 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

15、 reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . 2 Printed in the United States of America. 3 Dual STP Failure Prevention Procedures Table of Contents 1 GE

16、NERAL 4 1.1 PURPOSE . 4 1.2 DEFINITIONS . 4 2 BASIC PREMISES 4 3 SCOPE OF THIS DOCUMENT 5 4 SS7 COMPONENT IDENTIFICATION . 5 5 DECLARING ORGANIZATIONS 5 6 NOC/SCC JOINT RESPONSIBILITIES 5 7 STP MAINTENANCE WORK GROUP RESPONSIBILITIES . 6 8 INTERCONNECTION RESPONSIBILITIES . 6 9 ORGANIZATION IDENTIFI

17、CATION 6 10 COMMUNICATIONS 7 11 AWARENESS TRAINING . 7 12 ATTACHMENTS 7 13 ATTACHMENT 1, SIMPLEX/DUPLEX OUTAGE/RESTORATION NOTIFICATION FORM . 8 14 ATTACHMENT 2, EXAMPLE OF STICKER AND TAGS . 10 15 ATTACHMENT 3, TABLE 1 SS7 STICKERS, TAGS AND DUMMY PLUGS . 11 16 ATTACHMENT 4, LISTING OF ESSENTIAL EQ

18、UIPMENT/FACILITIES 12 16.1 SS7 COMPONENT IDENTIFICATION LISTING . 12 4 1 General The NGIIF recommends that each STP Owner/Operator have in place a written procedure to assist in the prevention of Dual STP failures. This section outlines a minimum set of “recommended” guidelines. 1.1 Purpose This doc

19、ument provides guidance to operators and maintenance organizations of Signaling Transfer Points (STP) in the telecommunications industry. Suggested work functions and preventative measures are included in this document that should be performed and or taken in order to minimize the potential for loss

20、 of an STP and the subsequent customer impact. This document is generic in principle, and should be modified to meet particular companies operating needs and procedures. Acronyms describing systems or work centers are provided for example only. Where organizational structures differ from company to

21、company it is recommended, where applicable that the responsibilities and actions outlined in this document be assigned and performed by the appropriate organization. This document does not replace or supersede any existing con tracts, tariffs or any other legally binding document. 1.2 Definitions F

22、or the purpose of this document the following definitions shall apply: Duplex Condition - A condition in which the both STPs are in service and in a stable call processing condition. Simplex Condition - A condition in which a single STP has failed (simplex condition). Essential Equipment - That equi

23、pment that has been deemed necessary to maintain the health of the SS7 network. SCC - Switching Control Center (surveillance center Tier 1 support). The Center that has operational responsibility for surveillance of the STPs and SS7 compatible switches in their respective geographical areas. SNCC/SN

24、SC/SEAC - Signaling Network Control Center/Signaling Network Support Center/Signaling Engineering & Administration Center. The site with overall responsibility for the maintenance and control of the Signaling Network. NOC - Network Operations Center (Tier II Support). The center that provides Survei

25、llance and Support for the entire network which includes the Signaling Network (SS7). 2 Basic Premises STP owner/operators have an obligation to ensure the integrity of the signaling network by having in place the appropriate organizational structure, guidelines for maintenance personal and procedur

26、e for the restoration of STPs in the event of a network failure. Proactive provisioning, identification and marking of all facilities that affect the integrity of the SS7 network can and will reduce the risk of accidental network events. Wherever possible provisioning arrangements should segregate C

27、CS7 DS0 signals from non-CCS7 DS0s on a DS1 to ensure the integrity of the CCS7 network. 5 This document addresses suggested process enhancements to current processes associated with the maintenance of STPs and their environments. 3 Scope of this Document The scope of this document is restricted to:

28、 The identification of SS7 related equipment Associated organizational responsibilities to declare a Duplex/Simplex condition (Internally and Externally) Maintenance of network integrity during an incident STP node simplex outages 4 SS7 Component Identification All STP and SCP communications equipme

29、nt that supports CCS links or systems that support communications equipment should be marked with SS7 stickers or tag indications to avoid accidental outages (see Attachment 4). Main Frame Link appearances should be identified using tags and stickers. Bare pins, should be protected, where possible,

30、with red slip on covers. The DSX bay appearance of all SS7 links should be equipped with red “dummy“ plugs. Each plug should be inscribed with the letters CCS or SS7. As new equipment is added to the network that has a direct impact on the integrity of the STPs they should be identified and marked a

31、ppropriately, in addition they should be added to the list of critical equipment listings. Responsible organizations should perform a review of critical equipment at least every six months to provide assurance for the integrity of the STPs. 5 Declaring Organizations This is section describes the res

32、ponsibilities of the NSMC (SEAC, SNCC/SNSC), Tier II support organizations associated with an STP Simplex/Duplex alert condition. In the event of an STP simplex condition, the Network Operations Center (SEAC, SNCC/SNSC) is responsible for declaring a failure of the STP mated pairs. The Network Opera

33、tions Center (SEAC, SNCC/SNSC) is also responsible for declaring a return to service of the mated STP pair. When a Simplex condition requirement has been met, the NOC is responsible for notifying the SCC supporting the remaining work ing STP and declaring a Simplex condition. 6 NOC/SCC Joint Respons

34、ibilities This section describes the responsibilities of the NOC, SCC in the event of a Simplex/Duplex condition associated with an STP. NOC, SCC personnel are responsible for notifying the appropriate internal organizations and levels of management of a Simplex condition. 6 When the Out of Service

35、STP has recovered and is in a stable condition, the NOC is responsible for declaring a Duplex condition by notifying the same SCC contact as used to declare the Simplex condition. All NOC, SCCs shall maintain an EMERGENCY PROCEDURES and contact listings document for notification purposes, the contac

36、t listings should be updated as soon as changes are identified and on a six month basis, a verification of those contact listings should be performed. It is recommended that the Emergency Procedures and Contact list be kept in an “SS7 Emergency Procedures Binder“ at the appropriate NOC, SCC work sta

37、tion. Copies of this document should be provided to the NOC, SCC duty supervisor for use in the event of an emergency. The NOC, SCC is responsible for the identification of all associated equipment that is deemed essential for the integrity of the STP and the SS7 network (see attachment 4). 7 STP Ma

38、intenance Work Group Responsibilities This section outlines the responsibilities of the organization that maintains the STPs. In an STP environment (e.g., physical plant), when a Simplex condition exist, all routine work in the mate STP location shall cease, in addition all applicable work being per

39、formed in any location considered essential to maintaining the health of the working STP shall be suspended. All routine software input on the working STP must be suspended at the appropriate time during a Simplex condition, and should only resume once a Duplex condition has been declared. Where wor

40、k that is underway that is deemed critical, such work shall be completed. At that point all further work shall cease. When this situation arises notification shall be made to the controlling SCC. When a node is isolated from the working STP during a Simplex condition the link(s) should be restored t

41、o service immediately. If links are out of service at the working STP but no nodes are isolated or experiencing congestion due to links being out of service, the links should not be restored until a Duplex condition has been declared. When a Simplex condition has been declared, it is the responsibil

42、ity of the personnel at the site of the working STP to ensure that all work activities being performed that may impact the STP are aware of the condition and that all related work operations are suspended. 8 Interconnection Responsibilities This section outlines the responsibility the company experi

43、encing the STP outage has in regards to notifying their interconnected parties. Where it has been determined that there is a direct interconnection to an ASC/ASP the company declaring the Simplex/Duplex condition should contact the interconnected parties as soon as possible and inform them of the si

44、tuation. 9 Organization Identification This section covers the identification of some of those organizations that may need to be informed in the event of a Simplex condition. The organization that has the responsibility for the maintenance of the STP is responsible for identifying those organization

45、s that need to be informed of the Simplex/Duplex condition. 7 All locations/work groups identified as being essential to the integrity of the STP and SS7 network shall provide an emergency contact number to the NOC, SCC. 10 Communications This section outlines responsibilities for the establishment

46、of communications prior to a Simplex condition being declared. All service providers should have in place an internal methodology to communicate in the event that the Public Switched network is in a degraded condition or completely out of service. In addition as recommended by the Network Interconne

47、ction Interoperability Forum all service providers should subscribed to an emergency communications network to assist in facilitating the restoration of the network node that is out of service. In the event of a Simplex/Duplex condition being declared the appropriate organizations as determined by e

48、ach provider should be notified immediately in accordance with locally determined procedures. 11 Awareness Training This section covers recommendations for awareness training associated with the prevention of a dual STP failure. An awareness training program should be implemented to educate all work

49、 groups of the impact a failed STP may have in their respective network. The awareness training should include a detailed review of the locally produced dual STP failure prevention document. 12 Attachments This section lists all of the attachments which should be associated with this document. Attachment 1 - Simplex/Duplex Outage/Restoration Notification form Attachment 2 - Example of Sticker and Tags Attachment 3 - Table 1 SS7 Stickers, Tags and Dummy Plugs Attachment 4 - Listing of Essential Equipment/Facilities 8 13 Attachment 1, Simplex/Duplex Outage/Restoration Notificat