1、 ATIS-0300010 ATIS Standard on - Next Generation Interconnection Interoperability (NGIIF) Reference Document: Part II, Installation and Maintenance Responsibilities Switched Access Services Feature Group B, C, and D As a leading technology and solutions development organization, the Alliance for Tel
2、ecommunications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, 5G, network functions virtualization, big data analytics, cloud
3、services, device solutions, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use
4、cases, software toolkits, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M glo
5、bal initiative, a member of the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. Notice of Disclaimer your call cannot be completed with the access code you dialed. Please check the
6、code and try again or call your long-distance company for assistance.“ Subsequent to the end of the 3-digit to 4-digit CIC expansion transition period, the following announcement should be used when an invalid carrier access code is dialed: “Your call cannot be completed as dialed. If you dialed a 5
7、-digit code, it has changed. Please redial adding a one and a zero before the 5-digit code, or for assistance, contact the carrier you are trying to use.” Any announcement associated with the end of the 5-digit CAC permissive dialing period should be played at a minimum until July 1, 1999. 5 Network
8、 Service Center (NSC) The NGIIF recommends immediate reporting of non-circuit-specific troubles via telephone in order to facilitate the rapid restoral of service. The NSC, or other regionally designated centers, will be the contact point for non-circuit specific trouble reports from the ASCs. The A
9、SP will provide the ASC with a contact number, escalation, and guidelines for the reporting of non-circuit specific troubles. The NSC will provide status and feedback to the reporting ASC, when requested. 6 Network Modification Notification A Network Modification is any type of planned equipment, so
10、ftware, trunk, or facility activity that has the potential to significantly affect interconnected networks (e.g. rearrangement of existing network elements, switch homing arranges, SS7 rehoming). The NGIIF has developed the following guidelines outlining the medium by which internetwork affecting ma
11、intenance activity notification and the time frame prior to the planned activity will be provided to the interconnected company: 2 For Toll-Free, YY can be any of the following: 99, 88, 77, 66, 55, 44, 33, 22, and 00 when assigned. ATIS-0300010 9 Notification, when possible, should be made at least
12、five (5) working days prior to the planned change activity. Notification should be made in the form of: o E-mail (recommended where available) o FAX o Telephone call Notification should be provided to the affected companys appropriate notification center. Contact information is included in the NGIIF
13、 Service Provider Contact Directory.3 An example of a notification form can be found in ATIS-0300026, Next Generation Interconnection Interoperability (NGIIF) Reference Document: Part VI, Network Management Guidelines. Notifications that are made via the LERG Routing Guide Network modifications (suc
14、h as a rehome) will have an effective date in the LERG Routing Guide. Any network modification not completed or rescheduled prior to the effective date in the LERG Routing Guide may result in routing errors, blocked, or incomplete calls etc. Any network modification which has an effective date in th
15、e LERG Routing Guide must be completed by the effective date in the LERG Routing Guide. If rescheduled prior to the effective date in the LERG Routing Guide, it is recommended that an emergency notification request be submitted to iconectiv. NOTE: Effective dates rescheduled seven (7) days prior to
16、the effective date in the LERG Routing Guide can be entered into BIRRDS by the AOCN. However, effective dates rescheduled less than seven (7) days prior to the effective date in the LERG Routing Guide must be entered into BIRRDS by iconectiv. Any network modification that will not be completed by th
17、e effective date in the LERG Routing Guide by the service provider initiating the change will be required to update BIRRDS to return the network entries back to what it was prior to the effective date in the LERG Routing Guide. It is recommended that an emergency notification request be submitted to
18、 iconectiv. The originating service provider may elect to have their AOCN contact iconectiv directly to “zap” the records with the current view thereby returning the records to what they were prior to the most recent effective date in the LERG Routing Guide of the previous view The originating compa
19、nys AOCN will then update the LERG Routing Guide with the new effective date The originating companys AOCN will then issue an emergency notification request to iconectiv. When the zapping method is used, it significantly increases the probability that the “zapped” record changes may be missed by the
20、 industry and interconnected companies will not react. This may result in network outages and or blocked calls because other service providers were unaware that the proposed changes did not take place. 3 The Service Provider Contact Directory and instructions for gaining access to the Directory can
21、be accessed on ATISs website: http:/www.atis.org/01_committ_forums/ngiif/contact-directories/. ATIS-0300010 10 When network modifications are scheduled that could significantly affect traffic between directly interconnected networks, it is recommended that the affected ASPs and ASCs notify each othe
22、r prior to the event. The following information should be exchanged at the time of notification: Originator, (company name/contact number) Affected Network Element Date and Time of the Change Expected Duration Traffic Types Affected During Change Description of the Work to be Completed. 6.1 Network
23、Modification Suspension Periods Due to the volumes of traffic and the potential for negative impacts to the Network, the following table identifies when Network Modifications should not be performed. Table 1 - Network Modification Suspension Time Periods Network Modification Suspension Time Periods
24、Event Start of Suspension Period (Inclusive) End of Suspension Period (Inclusive) Mothers Day SATURDAY MONDAY Fathers Day SATURDAY SUNDAY Thanksgiving (US Only) WEDNESDAY MONDAY Christmas 12/22 12/26 New Years 12/31 1/1 Network modifications (e.g. Generic Changes, Parameter Changes, Switch Rehomes)
25、will not occur during the above-mentioned time periods unless agreed to by the interconnecting companies. Emergency exceptions should be coordinated. ATIS-0300010 11 7 Telecommunications Service Priority (TSP) Guidelines The TSP system provides for the priority treatment of NS/EP telecommunication s
26、ervices in order to prioritize their installation and maintenance. For more information, refer to ATIS-0300104, Next Generation Interconnection Interoperability Forum (NGIIF) NGN Reference Document - NGN Basics, Emergency Services, NGN Testing, and Network Survivability. 8 Switched Access Service In
27、stallation 8.1 Switched Access Service (SAS) Order Activity Switched Access Service (SAS) Order Activity, or equivalent, is an Access Service Negotiation. The ASC will order the required SAS from each ASP through an ICSC (Interconnection Customer Service Center) or equivalent negotiation. The ICSC w
28、ork group will handle inquiries and orders. The ICSC work group is to serve as a point of contact for the access service needs of Interexchange Customers. The ASP will negotiate the SAS due date intervals either on a standard or individual case basis. Ordering procedures are described in the Access
29、Services Tariff. During the installation period, all ASC inquiries will be referenced by ASP order number and trunk identification number. To mitigate inadvertent loopbacks, 64kb data services should be provisioned with loopback recognition timers. Where loopback recognition timers are an ordering o
30、ption for such services, this option should be selected. 8.2 Establishing an Interface It is the responsibility of the ASC to designate the POT. It is also the responsibility of the ASC to arrange for suitable equipment space in a safe working area and for suitable electrical power, if required, at
31、the POT. The space furnished shall be accessible to ASP personnel during normal working hours for installation and maintenance purposes. If necessary, ASC personnel will be available to work with ASP personnel. 8.3 Pre-service Testing Each company is responsible for pre-service testing to ensure tha
32、t their circuit segments have been installed correctly, prior to cooperative acceptance tests. 8.4 Cooperative Acceptance Testing - Analog The ASC has the option of accepting the service with or without performing cooperative acceptance testing. Prior to the due date, the ASP will contact the ASC an
33、d advise when the SAS will be ready for turn up. If the ASC requests cooperative acceptance tests, the ASP will schedule a mutually agreeable date and time and coordinate all normal and additional acceptance testing (as specified on the order). Test equipment compatibility should be verified at this
34、 time. In the event that the ASC does not request cooperative testing, the ASP will perform their own testing and not test directly with the ASC. Once acceptance testing has been completed, whether or not cooperative acceptance testing was performed, the trunk will be Made-Busy to prevent false seiz
35、ures from affecting the switching machines. It will be necessary for the ASC to coordinate with the designated ASP (both ends of their overall service) for the removal of the Make Busy. At the time of acceptance testing, the ASP personnel will not test directly with the ASC unless otherwise directed
36、. Once the acceptance tests have been completed on the SAS, the ASP will “make-busy” the termination to prevent selection and false seizures from affecting the switching machines. ATIS-0300010 12 If the ASC is neither available nor ready to perform normal installation acceptance tests at the schedul
37、ed time and does not request the ASP personnel to reschedule such tests by the due date, the ASP will consider the order complete on the due date. Unless otherwise specified in local tariffs, normal acceptance tests are: 3-Tone Slope Loss DC Continuity Operational Signaling Balance (ERL-SRL) C-Messa
38、ge Noise C-Notched Noise. NOTE: See Figure 1, Acceptance Testing Decision Chart. 8.5 Switched Digital Data Access Service (56Kbs, 64KBS, ISDN Primary a minimum pattern length of 200 bytes for S3 and S4 is suggested. 4 Table A.1 in ATIS-0100510, Digital Services for Rates Up to and Including DS3-Spec
39、ifications. ATIS-0300010 14 8.5.2 Switched Digital Data Services Acceptance/ Maintenance Requirements (56kbs, 64kbs, ISDN Primary Service Class Screening). Traffic Routing Acceptance testing requirements vary accordingly. If either the ASP or ASC require Traffic Routing acceptance testing for those
40、arrangements not covered by clause 8.4 - terms, conditions and procedures should be negotiated on an individual case basis. Outlined below are guidelines associated with Call Through Testing to provide assurance for the appropriate routing and generation of billing records. 8.7.1 Access Service Cust
41、omer (ASC): When establishing a new trunk group or engaging in a rearrangement of an existing trunk group, the ASC shall perform, at a minimum, a call through test to a number furnished by the ASP. The switch supporting the furnished telephone number shall provide answer supervision. The ASC shall i
42、nitiate test call(s) to ensure that correct Automatic Message Accounting (AMA) recording and routing occurs. The scheduling of this call(s) shall be negotiated by the interconnecting companies so that the ASP can validate that the correct AMA recording and routing has taken place for the trunk group
43、 under test. The validation results, or the acknowledgment that routing and recording is functioning, shall be provided to the ASP upon request. 8.7.2 Access Service Provider (ASP): When establishing a new trunk group or engaging in a rearrangement of an existing trunk group, the ASP shall perform a
44、 call through test at a minimum. The switch supporting the furnished telephone number used for testing purposes shall provide answer supervision. The ASP, upon completion of the call through test(s), shall validate that this call(s) was recorded for billing purposes. In addition, the ASP shall ensur
45、e that the call is routed over the correct trunk group. The validation results or the acknowledgment that routing and recording is functioning shall be provided to the ASC upon request. 8.8 Completions Upon acceptance of the SAS order by the ASC, the ASPC should record the name of the ASC representa
46、tive accepting the order and the basis of the acceptance, for example: Cooperative Acceptance Testing criteria being satisfied Automatic tests, where available, being completed Without acceptance testing. The ASP should report the order as completed and furnish all the required information to the IC
47、SC or equivalent, including any additional labor charges. ATIS-0300010 16 8.9 SAS Disconnects Prior to performing disconnect activity, the ASC or ASP should be contacted to coordinate disconnect activities. When the trunks are removed from service and translation messages entered, order tracking doc
48、uments should be updated, and the ASC or ASP notified. 8.10 SAS Rearrangements SAS rearrangements may include ASC and/or ASP changes in switching and/or facility assignments. When the rearrangement requires physical work by the ASP, the ASP shall contact the ASC to determine the extent of the requir
49、ed coordination. If, however, the rearrangement can be accomplished solely by the ASC, requests for trunk(s) make-busy will be handled as specified in the section titled Trouble Detection Responsibilities. Requests for non-scheduled testing will be handled as specified in the section titled Additional Billing. A sufficient time period should be agreed upon for all entities to complete rearrangement work and appropriate tests. Credit allowance rules will only apply when trunks are out of service for a duration, which exceeds this per
