ATIS 0300010-2015 Next Generation Interconnection Interoperability (NGIIF) Reference Document Part II Installation and Maintenance Responsibilities Switched Access Services Feature.pdf

1、 ATIS-0300010 ATIS Standard on - NEXT GENERATION INTERCONNECTION INTEROPERABILITY FORUM (NGIIF) REFERENCE DOCUMENT: PART 11, INSTALLATION AND MAINTENANCE RESPONSIBILITIES SWITCHED ACCESS SERVICES FEATURED GROUP B, C, AND D As a leading technology and solutions development organization, the Alliance

2、for Telecommunications 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, network functions virtualization, big data analytics, clo

3、ud 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 u

4、se 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

5、global initiative, a member of and major U.S. contributor to 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 c

6、ode you dialed. Please check the code and try again or call your long distance company for assistance.“ _ 3For toll free, YY can be any of the following: 99, 88, 77, 66, 55, 44, 33, 22, and 00 when assigned. ATIS-0300010 9 Subsequent to the end of the 3-digit to 4-digit CIC Expansion Transition peri

7、od, 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-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

8、 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 Service Center (NSC) The NGIIF recommends immediate reporting of non circuit-specific troubles via telephone in order to facilitate the rapid resto

9、ral of service. The NSC, or other regionally designated centers, will be the contact point for non-circuit specific trouble reports from the ASCs. The ASP will provide the ASC with a contact number, escalation, and guidelines for the reporting of non-circuit specific troubles. The NSC will provide s

10、tatus and feedback to the reporting ASC, when requested. 6 Network Modification Notification A Network Modification is any type of planned equipment, software, trunk or facility activity that has the potential to significantly affect interconnected networks (e.g. rearrangement of existing network el

11、ements, switch homing arranges, SS7 rehoming) The NGIIF has developed the following guidelines outlining the medium by which internetwork affecting maintenance activity notification and the time frame prior to the planned activity will be provided to the interconnected company: Notification, when po

12、ssible, should be made at least five (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 companys appropriate notification center. Contac

13、t information is included in the NGIIF Service Provider Contact Directory. An example of a notification form is located in the NM Section, Part VI, of the NGIIF Reference Document. Notifications that are made via the LERG Network modifications (such as a rehome) will have a LERG effective date. Any

14、network modification not completed or rescheduled prior to the LERG effective date may result in routing errors, blocked or incomplete calls etc. ATIS-0300010 10 Any network modification which has a LERG effective date must be completed by the LERG effective date. If rescheduled prior to the LERG ef

15、fective date it is recommended that an emergency notification request be submitted to iconectiv TRA. NOTE: Effective dates rescheduled seven (7) days prior to the LERG effective date can be entered into BIRRDS by the AOCN. However, effective dates rescheduled less than seven (7) days prior to the LE

16、RG effective date must be entered into BIRRDS by iconectiv TRA. Any network modification that will not be completed by the LERG effective date 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 LERG effective

17、 date. It is recommended that an emergency notification request be submitted to Telcordia TRA. The originating service provider may elect to have their AOCN contact iconectiv TRA directly and have TRA “zap” the records with the current view thereby returning the records to what they were prior to th

18、e most recent LERG effective date of the previous view. The originating companys AOCN will then update the LERG with the new effective date. The originating companys AOCN will then issue an emergency notification request to iconectiv TRA When the zapping method is used it significantly increases the

19、 probability that the “zapped” record changes may be missed by the 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. When network modifications are s

20、cheduled that could significantly affect traffic between directly interconnected networks, it is recommended that the affected ASPs and ASCs notify each other prior to the event. The following information should be exchanged at the time of notification: Originator, (company name/contact number) Affe

21、cted 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 Modification Suspension Periods Due to the volumes of traffic and the potential for negative impacts to the Network, the following table identif

22、ies when Network Modifications should not be performed. ATIS-0300010 11 Table 1 - Network Modification Suspension Time Periods Network Modification Suspension Time Periods Event Start of Suspension Period (Inclusive) End of Suspension Period (Inclusive) Mothers Day SATURDAY MONDAY Fathers Day SATURD

23、AY 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) will not occur during the above mentioned time periods unless agreed to by the interconnecting companies. Emergency exceptions s

24、hould be coordinated. 7 Telecommunications Service Priority (TSP) Guidelines The TSP system provides for the priority treatment of NS/EP telecommunication services in order to prioritize their installation and maintenance. For more information, refer to ATIS-0300109, Next Generation Interconnection

25、Interoperability Forum (NGIIF) - NGN Reference Document - Emergency Services. 8 Switched Access Service Installation 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 fro

26、m each ASP through an ICSC (Interconnection Customer Service Center) or equivalent negotiation. The ICSC work 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

27、 intervals either on a standard or individual case basis. Ordering procedures are described in the Access Services Tariff. During the installation period, all ASC inquiries will be referenced by ASP order number and trunk identification number. ATIS-0300010 12 To mitigate inadvertent loopbacks, 64kb

28、 data services should be provisioned with loopback recognition timers. Where loopback recognition timers are an ordering option 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

29、the ASC to arrange for suitable equipment space in a safe working area and for suitable electrical power, if required, at 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 avail

30、able to work with ASP personnel. 8.3 Pre-service Testing Each company is responsible for pre-service testing to ensure that 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

31、 service with or without performing cooperative acceptance testing. Prior to the due date, the ASP will contact the ASC and 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 nor

32、mal and additional acceptance testing (as specified on the order). Test equipment compatibility should be verified at this 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

33、 completed, whether or not cooperative acceptance testing was performed, the trunk will be Made-Busy to prevent false seizures 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 Mak

34、e Busy. At the time of acceptance testing, the ASP personnel will not test directly with the ASC unless otherwise directed. 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

35、 If the ASC is neither available nor ready to perform normal installation acceptance tests at the scheduled 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, nor

36、mal acceptance tests are: 3-Tone Slope Loss DC Continuity Operational Signaling Balance (ERL-SRL) C-Message Noise C-Notched Noise NOTE: See flowchart Figure 1- Acceptance Testing Decision Chart ATIS-0300010 13 8.5 Switched Digital Data Access Service (56Kbs, 64KBS, ISDN Primary a minimum pattern len

37、gth of 200 bytes for S3 and S4 is suggested. ATIS-0300010 15 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 Rout

38、ing acceptance testing for those arrangements not covered by Section 7 D, E or F - 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

39、billing records. 8.7.1 Access Service Customer (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 p

40、rovide answer supervision. The ASC shall initiate 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 r

41、outing has taken place for the trunk group 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 exi

42、sting trunk group, the ASP shall perform a 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

43、purposes. In addition the ASP shall ensure 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 sho

44、uld record the name of the ASC representative 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 fur

45、nish all the required information to the ICSC or equivalent, including any additional labor charges. ATIS-0300010 17 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 trans

46、lation messages entered, order tracking documents 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

47、 ASC to determine the extent of the required 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. Request for non-scheduled testing will be handled as

48、 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 period due to ASP caused

49、 problems. Upon completion of the rearrangement, the ASP and the ASC may perform cooperative tests to determine that the rearrangement meets service requirements. 8.11 Coordinated Conversions Coordinated conversions are processes that may be used to facilitate changes requested by the ASC(s) that involves the reuse of a portion of the ASP provided equipment and/or facilities previously assigned. Coordinated conversions require the issuance and processing of related disconnect and connect orders, and coordination of these orders th