Network Interconnection Interoperability (NIIF) Reference Document Part III@ Installation and Maintenance Responsibilities for SS7 Links and Trunks (Version 10.1)
"GENERAL This document outlines Access Service Customer (ASC) and Access Service Provider (ASP) responsibilities for the Signaling System 7 (SS7) interface between carriers. It deals with the physical interconnecting trunks and link(s) as well as the software necessary to support the use of the link(s) to transport SS7 messages between carriers. It is intended to be a living document to aid operations work forces. It does not replace or supersede Tariffs@ Contracts or any other legally binding documents. It is limited to procedures relating to the installation and maintenance of the SS7 trunks and link(s) and associated software used to interconnect and provide services between Interexchange and Access Service Providers. All networks which connect to ASCs and ASPs via SS7@ should be expected to recognize these operational guidelines@ as providers of public switched services regardless of whether or not they provide Public Switched Telephone Network services. For the purpose of this document@ the terms@ SS7 and CCS are interchangeable. The ASC@ for the purposes of this document@ is defined as the Interexchange Customer engaged for hire between two or more exchanges@ including interstate or foreign communication by wire or radio. The ASP@ for purposes of this document@ denotes a company engaged in the business of furnishing access service in a franchised territory. The Wireless Service Provider (WSP)@ for the purposes of this document@ is defined as those carriers engaged in Intra/Interstate communication via radio frequency. Local Service Provider (LSP) is defined as the Local Exchange Carrier (LEC) selling local interconnection service arrangement trunk(s) to another LEC. Local Service Customer (LSC) is defined as the LEC purchasing local interconnection service arrangement trunk(s) from another LEC. Where ASP/ASC interconnection statements are made or identified@ specific to their purpose@ WSP/LSP/LSC may be substituted as appropriate. In addition to other operational and technical agreements made at the Network Interconnection Interoperability Forum@ this document is being reissued to incorporate the following changes: ?Standardization of the Issue Number and publication date to agree with other sections of the NIIF Reference Document. ? Addition of a new Part III Attachment G - titled SS7 Diversity Validation Guidelines ? Addition of new document Part III Attachment H - titled ""SS7 Cause Codes Tones and Announcements."" The SS7 link(s) may be considered as a network enhancement for certain existing services between Interexchange and Access Service Providers as well as providing a transport to new services. The term node is used in this document to mean any SS7 capable network element without regard to its specific function i.e. Signal Transfer Point (STP)@ Signal Point (SP)@ Service Switching Point (SSP)@ Service Control Point (SCP). The software resident programs@ in both ASP and ASC interconnecting nodes for the purpose of providing services transported on SS7 link(s)@ will be referred to as applications. The NIIF has developed the following guidelines outlining the medium by which internetwork affecting maintenance activity notification will be provided to the interconnected company and the time frame prior to the planned activity: ?Notification when possible should be made at least 5 working days prior to the planned change activity. ?Notification should be made in the form of: - E-Mail (recommended where available)@ - FAX or@ - Telephone call. ?Notification should be provided to the affected company's appropriate notification center. Contact information is included in the NIIF Company Specific Contact Directory. An example of a notification form is located in the NM Section@ Part VI@ of the NIIF Reference Document. When network modifications are planned to any SS7 network element that has the potential of affecting traffic@ the ASP/ASC must notify the interconnecting carrier(s) of the planned change. Sufficient information should be exchanged to ensure that all parties understand: ?Affected Network Element ? Date and time of change ? Expected duration Traffic effect during change ? Potential hazards Compatibility test requirements and procedures should be considered. The need exists to install and maintain time of day clock settings to coordinated universal time standards for SS7 network elements. In the absence of automated clock update standards and systems@ it will be necessary to manually install and maintain time of day clock settings@ as follows: ?Internal Network Element (NE) clocks set to + or - 15 seconds from the Coordinated Universal Time (UTC) minute register would degrade service. ? Daily routine to check NE clock (e.g.@ 8 am) to UTC. ?Weekly routine to check clock source to National Institute of Science and Technology (NIST)@ e.g.@ WWV@ Naval Observatory. etc.@ to nearest second + or - 1 seconds. ? Upon initialization of NE (boot) there is a need to load time of day@ otherwise NE sets to 0000 hours 1/1/00 - (operationally sensitive.)"