Inter-Service Provider LNP Operations Flows – Narratives Page 1 of 48 Version 4.01 Narratives: Following are the textual descriptions of the Inter-Service Provider Local Number Portability (LNP) Operations Flows. These Narratives (Version 4.0) provide a detailed description of each process step within the attached LNP Operations Flows (Version 4.0). NANC Flows v4.0 - 10-16-2009.ppt Legend: Local Service Provider (LSP) = Any provider (e.g., voice provider, data provider) that administers and bills local exchange and related services for the end user. The following terms identify LSPs with specific roles during the porting process: • New Local Service Provider (NLSP) - The local provider of record following the completion of the porting process. • Old Local Service Provider (OLSP) - The local provider of record prior to the porting process. Network Service Provider (NSP) = Carrier that provides the facilities and switch/equipment components needed to make up an end user’s local telecommunications service. The following terms identify NSPs with specific roles during the porting process: • New Network Service Provider (NNSP) - The network provider of record following the completion of the porting process. • Old Network Service Provider (ONSP) - The network provider of record prior to the porting process. CSR = Customer Service Record DSL = Digital Subscriber Loop FOC = Firm Order Confirmation FRS = Functional Requirements Specification ICP = Inter-carrier Communication Process IIS = Interoperability Interface Specifications LSMS = Local Service Management System LSR = Local Service Request NPAC = Number Portability Administration Center PSTN = Public Switched Telephone Network SOA = Service Order Activation SP = Service Provider SV = Subscription Version TN = Telephone Number “via the SOA interface” = generic description for one of the following: the SOA CMIP association, LTI, or contacting NPAC personnel WPR = Wireless Port Request WPRR = Wireless Port Request Response Inter-Service Provider LNP Operations Flows – Narratives Page 2 of 48 Version 4.01 NOTE: Pursuant to FCC Order 07-188, released on November 8, 2007, and FCC Order 09-41, released on May 13, 2009, Local Number Portability (LNP) obligations are extended to interconnected Voice over Internet Protocol (VoIP) providers. In paragraph 8 of FCC Order 09-41, the FCC ruled the following: “Thus, we require all entities subject to our LNP rules, including interconnected VoIP providers and their numbering partners, to complete port requests for simple wireline-to-wireline and simple intermodal ports within one Business Day, unless a longer period is requested by the new provider or the customer elects otherwise.” The North American Numbering Council (NANC) identifies three classes of interconnected VoIP providers, defined as follows: 1. Class 1: A standalone interconnected VoIP provider that obtains numbering resources directly from the North American Numbering Plan Administrator (NANPA) and the Pooling Administrator (PA) and connects directly to the Public Switched Telephone Network (PSTN) (i.e., not through a PSTN Service Provider partner’s end office switch). Class 1 standalone interconnected VoIP providers must follow the appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Network Service Provider (NNSP) or Old Network Service Provider (ONSP), whichever is applicable. 2. Class 2: An interconnected VoIP provider that partners with a facilities-based Public Switched Telephone Network (PSTN) Service Providers to obtain numbering resources and connectivity to the PSTN via the Service Provider partner’s switch. A Class 2 interconnected VoIP provider is not considered a reseller in the context of the FCC definition of a Simple Port (refer to FCC Order 07-188 and FCC Order 09-41 for Simple Port definition). Class 2 interconnected VoIP providers must follow the appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Local Service Provider (NLSP) or Old Local Service Provider (OLSP), whichever is applicable. 3. Class 3: A non-facilities-based reseller of interconnected VoIP services that utilizes the numbering resources and facilities of another interconnected VoIP provider (analogous to the “traditional” PSTN reseller). A Class 3 interconnected VoIP provider is not considered a reseller in the context of the FCC definition of a Simple Port (refer to FCC Order 07-188 and FCC Order 09-41for Simple Port definition). Class 3 interconnected VoIP providers must follow the appropriate Wireline-Wireline/Intermodal Flows (Simple or Non-Simple, whichever is applicable) for the LNP provisioning process, serving as the New Local Service Provider (NLSP) or Old Local Service Provider (OLSP), whichever is applicable. Inter-Service Provider LNP Operations Flows – Narratives Page 3 of 48 Version 4.01 NOTE: The FCC has allowed that One Business Day porting must be implemented either within 9 months of the NANC report to the FCC, or for carriers which qualify, implemented within 15 months (FCC 09- 41, para 12). The Local Number Portability Administration Working Group (LNPA WG) provisioning flows and One Business Day definition require reciprocal implementation where carriers must only port-in at the interval which that carrier also ports-out. NOTE: Service Providers are not precluded from exceeding the requirements set forth in the NANC LNP Provisioning Flows. For example, no provider is required to allow activation on a non-Business Day (Saturday, Sunday or Old Service Provider Company-Defined Holiday). However, a non-Business Day activation may be performed as long as both Service Providers agree and any Service Provider activating a port on a non-Business Day understands the porting out Service Provider may not have, and is not required to have, operational support available on days not defined as Business Days. In agreeing to non-Business Day activations, the Old (porting out) Service Provider may require that the Local Service Request (LSR)/Firm Order Confirmation (FOC) and the New (porting in) Service Provider NPAC Create message be due-dated for the appropriate normal Business Day in order to ensure that the end user's service is maintained. Inter-Service Provider LNP Operations Flows – Narratives Page 4 of 48 Version 4.01 Port Type Determination Figure 1 Flow Step Description 1. START: End User Contact with NLSP • The process begins with an end user requesting service from the NLSP. • It is assumed that prior to entering the provisioning process the involved NPA/NXX was opened for porting (If code is not open, refer to Inter- Service Provider LNP Operations Flows – Code Opening Process, Figure 16.). 2. End User agrees to change to NLSP • End user agrees to change to NLSP and requests retention of current telephone number (TN). 3. NLSP obtains end user authorization • NLSP obtains verifiable authority (e.g., Letter of Authorization – [LOA], third-party verification – [TPV], etc.) from end user to act as the official agent on behalf of the end user. The OLSP cannot require a physical copy of the end user authorization to be provided before processing the Customer Service Request (CSR) or the port request. The NLSP is responsible for demonstrating verifiable authority in the case of a dispute. 4. Is this a Wireless- Wireless Port? • If Yes, go to Step 5. • If No, go to Step 6. 5. ICP – Service Provider Communication • Inter-Service Provider LNP Operations Flows – Wireless ICP Process, Figure 2, Step 1. Inter-Service Provider LNP Operations Flows – Narratives Page 5 of 48 Version 4.01 Flow Step Description 6. (Optional) NLSP requests CSR from OLSP • As an optional step, the NLSP requests a Customer Service Record (CSR) from the OLSP. A service agreement between the NLSP and OLSP may or may not be required for CSR. • NOTE: CSRs are not available from wireless carriers. • The Old SP shall not require the New SP to have previously obtained a CSR before they will accept an LSR from the New SP. For those New SPs that choose not to obtain a CSR, they understand that there is heightened risk that their LSR may not be complete and accurate. This is not intended to preclude those providers who provide an ordering GUI from including a step involving a real-time CSR pull within that process, as long as an alternate ordering process is available that does not require a CSR being pulled. • CSRs, if requested and available, must be returned within 24 clock hours, unless otherwise negotiated between service providers, excluding weekends and Old Service Provider holidays. • Any of the end user validation fields required by the Old SP on an incoming LSR must be available on the CSR, excluding end user requested and assigned password/PIN. • Only passwords/PINs requested and assigned by the end user may be utilized as an end user validation field on an incoming LSR by the Old Network Service Provider/Old Local Service Provider. Any service provider assigned password/PIN may not be utilized as a requirement in order to obtain a CSR. 7. BROADBAND – (optional) Broadband/DSL Verification • Inter-Service Provider LNP Operations Flows – Broadband/DSL Verification Process, Figure 3, Step 1. 8. Does NLSP consider this a Simple Port? • If Yes, go to Step 9. • The New SP (the NLSP and/or the NNSP whichever is applicable) must make every reasonable effort to verify that the port request is in fact a Simple Port request, e.g., pulling a CSR if available, or asking the appropriate questions of the end user, etc. • If No, go to Step 10. 9. SIMPLE LSR- FOC – Service Provider Communication • Inter-Service Provider LNP Operations Flows - Wireline Simple Port LSR/FOC Process, Figure 4, Step 1. 10. NON-SIMPLE LSR-FOC – Service Provider Communication • Inter-Service Provider LNP Operations Flows - Wireline Non-Simple Port LSR/FOC Process, Figure 5, Step 1. 11. MAIN – Main Porting Flow • Inter-Service Provider LNP Operations Flows – Main Porting Flow, Figure 6, Step 1. 12. End Inter-Service Provider LNP Operations Flows – Narratives Page 6 of 48 Version 4.01 Wireless ICP Service Provider Communication Figure 2 Flow Step Description 1. Is NLSP a Reseller? • This is the entry point from the Inter-Service Provider LNP Operations Flows – Port Type Determination, Figure 1, Step 5. • The NLSP determines if customer is porting all TN(s). • If Yes, go to Step 2. • If No, go to Step 3. 2. NLSP sends WPR or WPR information to NNSP for resale service • NLSP (Reseller) sends a WPR (Wireless Port Request) or WPR information to the NNSP (may vary slightly depending on provider agreement between the involved service providers). • For wireless to wireless service providers the WPR/WPRR (Wireless Port Request/Wireless Port Request Response) initial response time frame is 30 minutes. • The due date of the first TN ported in an NPA-NXX is no earlier than 5 Business Days after a confirming WPRR receipt date. • The due date for a TN ported in an NPA-NXX which has TNs already ported is no earlier than 2 business hours after a confirming WPRR receipt date/time or as currently determined by NANC. 3. NNSP sends WPR to ONSP • The NNSP notifies the ONSP of the port request using the WPR. • ICP response interval, currently set to 30 minutes, begins from acknowledgment being received by NNSP from ONSP, and not at the time the WPR is sent from the NNSP to the ONSP. 4. Is a Type 1 wireless number involved? • If Yes, go to Step 5. • If No, go to Step 7. 5. NON-SIMPLE LSR-FOC – Service Provider Communication • Inter-Service Provider LNP Operations Flows - Wireline Non-Simple Port LSR/FOC Process, Figure 5, Step 1. 6. Return to Figure 1 • Return to Port Type Determination flow Figure 1, Step 5. 7. Is OLSP a Reseller? • If Yes, go to Step 8. • If No, go to Step10. 8. ONSP sends WPR or WPR information to OLSP • The ONSP notifies the OLSP of the port request using the WPR or WPR information. 9. OLSP sends WPRR or WPRR information to ONSP • The OLSP sends the ONSP the WPRR or WPRR information. 10. ONSP sends WPRR to NNSP • ONSP sends the WPRR to the NNSP. • IC terminates upon receipt of WPRR by NNSP. Inter-Service Provider LNP Operations Flows – Narratives Page 7 of 48 Version 4.01 Flow Step Description 11. Is NLSP a Reseller? • If Yes, go to Step 12. • If No, go to Step 13. 12. NNSP forwards WPRR or WPRR information to NLSP • The NNSP sends the WPRR or WPRR information to the NLSP. 13. Is WPRR a Delay? • If Yes, go to Step 14. • If No, go to Step 15. 14. Is OLSP a Reseller? • If Yes, go to Step 9. • If No, go to Step 10. 15. Is WPRR confirmed? • If Yes, go to Step 17. • If No, go to Step 16 – WPRR must be a Resolution Required. 16. WPRR is a resolution response • Return to Step 1. 17. Return to Figure 1 • Return to Port Type Determination flow Figure 1, Step 5. Inter-Service Provider LNP Operations Flows – Narratives Page 8 of 48 Version 4.01 Broadband/DSL Verification Process (optional) Figure 3 Flow Step Description 1. Has it been determined that broadband/DSL is on the line? • If Yes, go to Step 6. • If No, go to Step 2. 2. Is broadband/DSL service required for new voice service? • If Yes, go to Step 3. • If No, go to Step 10. 3. NLSP notifies End User to acquire new broadband/DSL service • End User could obtain broadband/DSL service from NLSP, if available, or from another service provider. 4. NLSP awaits End User response providing broadband/DSL service due date. • This is to ensure that End User has obtained the broadband/DSL service that is necessary for their new voice service. 5. NLSP continues Port Request with LSR due date on or after broadband/DSL service due date • This is to ensure that new broadband/DSL service is available when the port is activated in order for End User to have voice service. 6. Does End User wish to retain existing broadband/DSL service? • If Yes, go to Step 7. • If No, go to Step 2. 7. Does OLSP offer standalone broadband/DSL service? • If Yes, go to Step 9. • If No, go to Step 8. 8. NLSP notifies End User to acquire new broadband/DSL service if desired. • Go to Step 2. Inter-Service Provider LNP Operations Flows – Narratives Page 9 of 48 Version 4.01 Flow Step Description 9. Does OLSP automatically convert End User to standalone broadband/DSL service? • If Yes, go to Step 10. • If No, go to Step 8. 10. Return to Figure 1 • Return to Port Type Determination flow Figure 1, Step 7. Inter-Service Provider LNP Operations Flows – Narratives Page 10 of 48 Version 4.01 Wireline Simple Port LSR/FOC Process Figure 4 Flow Step Description 1. Is NLSP a Class 2 or Class 3 Interconnected VoIP Provider? • If Yes, go to Step 2. • If No, go to Step 3. 2. NLSP sends LSR or LSR information to NNSP for the Interconnected VoIP service • NLSP sends an LSR or LSR Information to the NNSP fulfilling all requirements of any service agreement between the involved service providers. The LSR process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). 3. NNSP sends LSR to ONSP • The NNSP notifies the ONSP of the port using the LSR and sends the information via an electronic gateway, FAX, email, or manual means. The LSR process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). NOTE: The New SP (the NLSP and/or the NNSP whichever is applicable) must make every reasonable effort to verify that the port request is in fact a Simple Port request, e.g., pulling a CSR if available, or asking the appropriate questions of the end user, etc. 4. Is OLSP a Class 2 or Class 3 Interconnected VoIP Provider? • If Yes, go to Step 5 • If No, go to Step 7 5. Notify Provider – (conditional) ONSP sends LSR or LSR information to OLSP (Figure 8) • (conditional, based on any service agreement between the involved service providers) – ONSP sends an LSR, LSR Information to the OLSP) fulfilling all requirements. The LSR process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). • Communication between the ONSP and the OLSP with regard to the port must not delay the validation or processing of the port request. 6. (conditional) OLSP sends FOC or FOC information to ONSP • (conditional, based on any service agreement between the involved service providers) – The OLSP notifies the ONSP of the port using the FOC and sends the information via an electronic gateway, FAX, email, or other means. The LSR/FOC process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). The information required on the FOC may vary based on the carriers involved. • Communication between the ONSP and the OLSP with regard to the port must not delay the validation or processing of the port request. Inter-Service Provider LNP Operations Flows – Narratives Page 11 of 48 Version 4.01 Flow Step Description 7. Does ONSP agree this is a Simple Port? • If Yes, go to step 13. • If No, go to step 8. 8. Is the LSR complete and accurate? • If Yes, go to step 9. • If No, go to step 11. 9. Will the ONSP FOC current LSR with a different Due Date? • If Yes, go to Step 10. • If No, go to Step 11. Inter-Service Provider LNP Operations Flows – Narratives Page 12 of 48 Version 4.01 Flow Step Description 10. ONSP sends FOC with appropriate Due Date for Non- Simple Port to NNSP • ONSP sends the Firm Order Confirmation (FOC, local response) with the appropriate Due Date for Non-Simple Port to the NNSP for the porting LSR. • For wireline-to-wireline ports, and ports between wireline and wireless service providers, the following requirements apply for the interval to respond to an LSR: If the New SP-requested due date is 1-2 Business Days after LSR receipt, the Firm Order Confirmation (FOC) or Reject (whichever is applicable) is due within 4 hours. Refer to the attached chart for LSR Response Due Time: Final Business Week Chart_16Oct2009.do If the New SP-requested due date is 3 or more Business Days after LSR receipt, the Firm Order Confirmation (FOC) or Reject (whichever is applicable) is due within 24 clock hours, excluding weekends and Old Service Provider-defined holidays. In instances where the LSR indicates the port request is Non- Simple based on the current FCC definition and rule for a Simple Port, the Old SP must return a FOC or appropriate response within 24 clock hours, excluding weekends and Old Service Provider-defined holidays. • It is the responsibility of the ONSP to contact the NNSP if the ONSP is unable to meet the required interval for transmitting the FOC. If the FOC is not received by the NNSP within the required interval, then the NNSP may contact the ONSP. • The due date of the first TN ported in an NPA-NXX is no earlier than five (5) Business Days after FOC receipt date. • The LSR/FOC process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). The information required on the FOC may vary based on the carriers involved. 11. ONSP rejects LSR back to NNSP. • The ONSP has determined that this is a Non-Simple Port request and does not FOC with a Due Date that is appropriate for a Non-Simple Port. As a result, the ONSP rejects the LSR back to the NNSP in the appropriate timeframe indicated in Step 10. 12. NON-SIMPLE LSR-FOC – Service Provider Communication • Inter-Service Provider LNP Operations Flows - Wireline Non-Simple Port LSR/FOC Process, Figure 5, Step 1. Inter-Service Provider LNP Operations Flows – Narratives Page 13 of 48 Version 4.01 Flow Step Description 13. Is the LSR complete and accurate? • If Yes, go to Step 15. • If No, go to Step 14. 14. ONSP rejects LSR to NNSP. • ONSP sends a Reject Notification to the NNSP due to insufficient data on the LSR. • Return to Figure 4, Step 1. 15. ONSP sends FOC confirming Simple Port Request to NNSP. • ONSP sends the Firm Order Confirmation (FOC, local response) to the NNSP for the porting LSR. • For wireline to wireline ports, and ports between wireline and wireless service providers, the following requirements apply for the interval to respond to an LSR: If the New SP-requested due date is 1-2 Business Days after LSR receipt, the Firm Order Confirmation (FOC) or Reject (whichever is applicable) is due within 4 hours. Refer to the attached chart for LSR Response Due Time: Final Business Week Chart_16Oct2009.do If the New SP-requested due date is 3 or more Business Days after LSR receipt, the Firm Order Confirmation (FOC) or Reject (whichever is applicable) is due within 24 clock hours, excluding weekends and Old Service Provider-defined holidays. In instances where the LSR indicates the port request is Non- Simple based on the current FCC definition and rule for a Simple Port, the Old SP must return a FOC or appropriate response within 24 clock hours, excluding weekends and Old Service Provider-defined holidays. • The due date of the first TN ported in an NPA-NXX is no earlier than five (5) Business Days after FOC receipt date. Any subsequent port in that NPA NXX will have a due date no earlier than three (3) Business Days after FOC receipt. • The LSR/FOC process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). The information required on the FOC may vary based on the carriers involved. 16. Is NLSP a Class 2 or Class 3 Interconnected VoIP Provider? • If Yes, go to Step 17. • If No, go to Step 18. Inter-Service Provider LNP Operations Flows – Narratives Page 14 of 48 Version 4.01 Flow Step Description 17. NNSP sends FOC or FOC information to NLSP. • NNSP sends FOC or FOC Information to NLSP fulfilling all requirements of any service agreement between the involved service providers. The LSR/FOC process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). 18. Return to Figure 1 • Return to Port Type Determination flow Figure 1, Step 9. Inter-Service Provider LNP Operations Flows – Narratives Page 15 of 48 Version 4.01 Wireline Non-Simple Port LSR/FOC Process Figure 5 Flow Step Description 1. Is End User porting all TNs? • The NLSP determines if customer is porting all TN(s). • If Yes, go to Step 3. • If No, go to Step 2. 2. NLSP notes “Not all TNs are being ported” in the remarks section of LSR • The NLSP makes a note in the remarks section of the LSR to identify that the End User is not porting all TN(s). This can affect the due date interval due to account rearrangements necessary prior to service order issuance. 3. Is NLSP a Reseller or Class 2 or 3 Interconnected VoIP Provider? • If Yes, go to Step 4. • If No, go to Step 5. 4. NLSP sends LSR or LSR information to NNSP for resale or VoIP Interconnection service • NLSP (Reseller or Class 2 or 3 Interconnected VoIP Provider) sends an LSR or LSR Information to the NNSP fulfilling all requirements of any service agreement between the involved service providers. The LSR process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). 5. NNSP sends LSR to ONSP • The NNSP notifies the ONSP of the port using the LSR and sends the information via an electronic gateway, FAX, email, or manual means. The LSR process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). 6. Has the ONSP determined the LSR is incomplete or inaccurate? • If Yes, go to Step 7. • If No, go to Step 8. 7. ONSP rejects LSR back to NNSP • ONSP sends a Reject Notification to the NNSP due to insufficient or inaccurate data on the LSR. • Return to Figure 5, Step 1. 8. Is OLSP a Reseller or Class 2 or 3 Interconnected VoIP Provider or is a Type 1 wireless number involved? • If Yes, go to Step 9. • If No, go to Step 13. Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 16 of 48 Version 4.01 Flow Step Description 9. Notify Provider – (conditional) ONSP sends LSR, LSR information, to OLSP • (conditional, based on any service agreement between the involved service providers) – ONSP sends an LSR, LSR Information to the OLSP (Reseller or Class 2 or 3 Interconnected VoIP Provider or if a Type 1 number is involved) fulfilling all requirements. The LSR process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). • Communication between the ONSP and the OLSP with regard to the port must not delay the validation or processing of the port request. • Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification – Figure 8. 10. Has the OLSP determined the LSR is incomplete or inaccurate? • If Yes, go to Step 11. • If No, go to Step 12. 11. OLSP rejects LSR back to ONSP • OLSP sends a Reject Notification to the ONSP due to insufficient or inaccurate data on the LSR. • Return to Figure 5, Step 1. 12. (conditional) OLSP sends FOC or FOC information to ONSP • (conditional, based on any service agreement between the involved service providers) – The OLSP notifies the ONSP of the porting using the FOC and sends the information via an electronic gateway, FAX, email, or other means. The LSR/FOC process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). The information required on the FOC may vary based on the carriers involved. • Communication between the ONSP and the OLSP with regard to the port must not delay the validation or processing of the port request. Inter-Service Provider LNP Operations Flows – Narratives Page 17 of 48 Version 4.01 Flow Step Description 13. ONSP sends FOC to NNSP • ONSP sends the Firm Order Confirmation (FOC, local response) to the NNSP for the porting LSR. • For wireline to wireline service providers, and between wireline and wireless service providers, the requirement is that the FOC is returned within 24 clock hours, excluding weekends and Old Service Provider- defined holidays. It is the responsibility of the ONSP to contact the NNSP if the ONSP is unable to meet the 24 clock hour requirement (excluding weekends and Old Service Provider-defined holidays) for transmitting the FOC. If the FOC is not received by the NNSP within 24 clock hours (excluding weekends and Old Service Provider-defined holidays), then the NNSP may contact the ONSP. • The due date of the first TN ported in an NPA-NXX is No earlier than five (5) Business Days after FOC receipt date. Any subsequent port in that NPA NXX will have a due date No earlier than three (3) Business Days after FOC receipt. • It is assumed that the porting interval is not in addition to intervals for other requested services (e.g., unbundled loops) related to the porting request. The interval becomes the longest single interval required for the services requested. • The LSR/FOC process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). The information required on the FOC may vary based on the carriers involved. 14. Is NLSP a Reseller or Class 2 or 3 Interconnected VoIP Provider? • If Yes, go to Step 15. • If No, go to Step 16. 15. NNSP forwards FOC or FOC information to NLSP • NNSP forwards FOC or FOC Information to NLSP fulfilling all requirements of any service agreement between the involved service providers. The LSR/FOC process is defined by the Ordering and Billing Forum (OBF) and the electronic interface by the Telecommunications Industry Forum (TCIF). The information required on the FOC may vary based on the carriers involved. 16. Return to Figure 1 • Return to Port Type Determination flow Figure 1, Step 10. Inter-Service Provider LNP Operations Flows – Narratives Page 18 of 48 Version 4.01 Main Porting Flow Figure 6 Flow Step Description 1. Are NNSP and ONSP the same SP? • If Yes, go to Step 2. • If No, go to Step 4. 2. Is NPAC processing required? • If Yes, go to Step 3. • If No, go to Step14. 3. Perform intra- provider port or modify existing SV • ??SP enters intra-provider SV create data into the NPAC via the SOA interface for porting of end user in accordance with the NANC FRS and the NANC IIS. Upon completion of intra-provider port, Return to Port Type Determination flow Figure 1, Step 11. 4. NNSP coordinates all porting activities • The NNSP must coordinate porting timeframes with the ONSP, and both provide appropriate messages to the NPAC. Upon completion of the LSR/FOC or ICP Process, and when ready to initiate service orders, go to Step 5. 5. NNSP and ONSP create and process service orders • Upon completion of the LSR/FOC or ICP Process, the NNSP and ONSP create and process service orders through their internal service order systems, based on information provided in the LSR/FOC or WPR/WPRR. 6. Create – Service Provider Port Request • Inter-Service Provider LNP Operations Flows – Subscription Version Create Flow, Figure 7. 7. Was port request canceled? • The port can be canceled by the ONSP, the NNSP, or automatically by an NPAC process. • If Yes, go to Step 12. • If No, go to Step 8. Inter-Service Provider LNP Operations Flows – Narratives Page 19 of 48 Version 4.01 Flow Step Description 8. Did ONSP place the order in Conflict? • Check Concurrence Flag. If concurred, the ONSP agrees to the port. If not concurred, a conflict cause code as defined in the FRS, is designated. ONSP makes a concerted effort to contact NNSP prior to placing SV in conflict. • For wireline Simple Ports, the conflict request can be initiated up to the later of a.) the tunable time (Simple Port Conflict Restriction Window, current value of 9:00pm in the predominate time zone of the NPAC region where the number is being ported) one Business Day before the Due Date or b.) the T2 Timer (Final Concurrence Window tunable parameter) has expired. • For wireline Non-Simple Ports, the conflict request can be initiated up to the later of a.) the tunable time (Conflict Restriction Window, current value of 12:00pm) one Business Day before the Due Date or b.) the T2 Timer (Final Concurrence Window tunable parameter) has expired. • For wireless SPs using short timers for this SV, the conflict request can be initiated up to the time the T2 Timer (Final Concurrence Window tunable parameter) has expired. • If Yes, go to Step 11. • If No, go to Step 9. 9. NNSP coordinates physical changes with ONSP • The NNSP has the option of requesting a coordinated order. This is also the re-entry point from the Inter-Service Provider LNP Operations Flows – Conflict Flow for the Service Creation Provisioning Process, tie point BB, Figure 11. • If coordination is requested on the LSR, an indication of Yes or No for the application of a 10-digit trigger is required. If No coordination indication is given, then by default, the 10-digit trigger is applied if technically feasible. If the NNSP requests a coordinated order and specifies ‘No’ on the application of the 10-digit trigger, the ONSP uses the 10-digit trigger at its discretion. Inter-Service Provider LNP Operations Flows – Narratives Page 20 of 48 Version 4.01 Flow Step Description 10. Is the unconditional 10 digit trigger being used or does ONSP query on every call? • The unconditional 10-digit trigger is assigned to a number on a donor switch during the transition period when the number is physically moved from donor switch to recipient switch. During this period it is possible for the TN to reside in both donor and recipient switches at the same time. • For both Simple and Non-Simple Ports, the ONSP must deploy the 10- digit trigger in the donor switch, if technically feasible, or monitor the NPAC for activation in order to trigger the disconnect, or carriers perform a database query for every call origination. • A 10-digit trigger is applied by the ONSP no later than 11:59pm the day prior to the due date. • The unconditional 10-digit trigger may be applied by the NNSP. • If Yes, go to Inter-Service Provider LNP Operations Flows - Provisioning with Unconditional 10-Digit Trigger - tie point AA, Figure 10. • If No, go to Inter-Service Provider LNP Operations Flows - Provisioning without Unconditional 10-digit Trigger - tie point A, Figure 9. 11. NPAC logs request to place the order in conflict, including cause code • Go to Inter-Service Provider LNP Operations Flows - Conflict Flow for the Service Creation Provisioning Process - tie point B, Figure 11. 12. Notify Provider – NPAC notifies NNSP and ONSP that port is canceled • Upon cancellation, NPAC logs this information, and changes the subscription status to canceled. Both SPs are notified of the change in the subscription status via the SOA interface. • For the notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. • Both SPs take appropriate action related to internal work orders. 13. Notify Provider – (conditional) ONSP sends loss notification to OLSP • (conditional, , based on any service agreement between the involved service providers) – A loss notification may be sent to the OLSP. The specific timing will be based on the requirements of any service agreement between the involved service providers. It is necessary for the OLSP to terminate the End User’s service for the ported TN(s) after the port is completed. • Communication between the ONSP and the OLSP with regard to the port must not delay the validation or processing of the port request • This is also the re-entry point from various flows, tie point Z. 14. Return to Figure 1 • Return to Port Type Determination flow Figure 1, Step 11. Inter-Service Provider LNP Operations Flows – Narratives Page 21 of 48 Version 4.01 Subscription Version Create Flow Figure 7 Flow Step Description 1. NNSP and ONSP Notify NPAC with Create message • Due date of the create message is the due date on the FOC, where wireline due date equals date and wireless due date equals date and time. For porting between wireless and wireline, the wireline due date applies. Any change of due date to the NPAC is usually the result of a change in the FOC due date. • SPs enter SV data into the NPAC via the SOA interface for porting of End User in accordance with the NANC FRS and the NANC IIS. • The NPAC/SMS expects to receive matching SV Create messages from the ONSP and the NNSP when facilitating porting of a telephone number. However, to prevent the possibility of the ONSP unnecessarily delaying a port, two timers were developed and referred to as T1 and T2. If the ONSP does not send a matching SV create message to the NPAC, the NNSP can proceed with porting the telephone number after both timers expire. Some service providers choose not to send the concurring SV create, but rather allow the timers to expire. The LNPA Working Group concludes that all service providers should send the matching SV create messages to the NPAC/SMS. This will facilitate expeditious porting of telephone numbers and is more efficient than merely allowing timers to expire. The increased efficiency is especially beneficial in meeting the FCC mandated 1-day interval for Simple Ports. [Note that the order in which the ONSP and NNSP create messages arrive at the NPAC/SMS is immaterial.] • With regard to the population of the Due Time on the New SP and Old SP NPAC Create messages, current industry practices for both Mechanized SOA and Low Tech Interface (LTI) users will be maintained for Simple Ports. The New SP should not activate a port before midnight (00:00:00) local time of the Due Date unless it has been verified with the Old SP that the port could be activated early without impacting the customer's service. Failing to verify first that the Old SP has completed all necessary steps in the port-out process, e.g., established the 10-Digit Unconditional Trigger, resolved any order fallout in systems, etc., could result in the customer's service being negatively impacted, such as inability to receive all of their calls. Inter-Service Provider LNP Operations Flows – Narratives Page 22 of 48 Version 4.01 Flow Step Description 2. Is Create message valid? • NPAC validates data to ensure value formats and consistency as defined in the FRS. This is not a comparison between NNSP and ONSP messages. • If Yes, go to Step 4. If this is the first valid create message, the T1 Timer (Initial Concurrence Window tunable parameter) is started. SV Create Notifications are sent to both the ONSP and NNSP. • If No, go to Step 3. 3. NPAC notifies appropriate Service Provider that create message is invalid • If the data is not valid, the NPAC sends error Notification to the SP for correction. • The SP, upon Notification from the NPAC, corrects the data and resubmits to the NPAC. Re-enter at Step 1. 4. NPAC starts T1 timer • Upon receipt of the first valid create message, the NPAC starts the T1 Timer (Initial Concurrence Window tunable parameter). The value for the T1 Timer is configurable (one of three values) for SPs. Wireline and Intermodal ports will use either long or medium timers. The current value for the long timer (typically any wireline-involved Non-Simple porting) is nine (9) NPAC business hours. The current value for the medium timer (typically any wireline-involved Simple porting) is three (3) NPAC business hours. The current value for the short timer (typically wireless- to-wireless porting) is one (1) NPAC business hour. 5. T1 expired? • Short business hours (for wireline-involved Non-Simple porting) are defined as 7a-7p CT Monday through Friday, excluding NPAC-defined Holidays (Business Day start at 13:00/12:00 GMT, duration of 12 hours). • Medium business hours (for wireline-involved Simple porting) are defined as 7a-12a Monday through Friday, excluding NPAC-defined Holidays in the predominant time zone for each NPAC region (Business Day start at NE/MA/SE [eastern time zone] 1312:00/1211:00 GMT, MW/SW/Canadian [central time zone] 1413:00/1312:00 GMT, WE [mountain time zone] 1514:00/1413:00 GMT, WC [west coast time zone] 1615:00/1514:00 GMT, duration of 17 hours). • Long business hours (for wireless-to-wireless porting) are planned for 9a- 9p in the predominant time zone for each NPAC region (Business Day start – NE/MA/SE 14:00/13:00 GMT, MW/SW/Canadian 15:00/14:00 GMT, WE 16:00/15:00 GMT, WC 17:00/16:00 GMT, duration of 12 hours). • Short Business Days are currently defined as Monday through Friday, except holidays, and Long Business Days are currently defined as Sunday through Saturday (seven days a week), except holidays. Holidays and business hours are defined for each NPAC Region. • If Yes, go to Step 10. • If No, go to Step 6. 6. Received Second Create? • If Yes, go to Step 7. • If No, return to Step 5. 7. Is Create message valid? • If Yes, go to Step 8. • If No, go to Step 9. Field Field Field Field Field Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 23 of 48 Version 4.01 Flow Step Description 8. Return to Figure 6 • The porting process continues. • Return to Main Porting Flow Figure 6, Create Process, Step 6. 9. NPAC notifies appropriate Service Provider that Create message is invalid • The NPAC informs the SP of an invalid create. If necessary, the notified Service Provider coordinates the correction. • Return to Step 5. 10. NPAC notifies NNSP and ONSP that T1 has expired, and then starts T2 Timer • The NPAC informs the NNSP and ONSP of the expiration of the T1 Timer. • Upon expiration, the NPAC starts the T2 Timer (Final Concurrence Window tunable parameter). Inter-Service Provider LNP Operations Flows – Narratives Page 24 of 48 Version 4.01 Flow Step Description 11. T2 Expired? • The NPAC provides a T2 Timer (Final Concurrence Window tunable parameter) that is defined as the number of hours after the expiration of the T1 Timer. • The value for the T2 Timer is configurable (one of three values) for SPs. Wireline and Intermodal ports will use either long or medium timers. The current value for the long timer (typically any wireline-involved Non- Simple porting) is nine (9) NPAC business hours. The current value for the medium timer (typically any wireline-involved Simple porting) is three (3) NPAC business hours. The current value for the short timer (typically wireless-to-wireless porting) is one (1) NPAC business hour. • Short business hours (for wireline-involved Non-Simple porting) are defined as 7a-7p CT Monday through Friday, excluding NPAC-defined Holidays (Business Day start at 13:00/12:00 GMT, duration of 12 hours). • Medium business hours (for wireline-involved Simple porting) are defined as 7a-12a Monday through Friday, excluding NPAC-defined Holidays in the predominant time zone for each NPAC region (Business Day start at NE/MA/SE [eastern time zone] 1312:00/1211:00 GMT, MW/SW/Canadian [central time zone] 1413:00/1312:00 GMT, WE [mountain time zone] 1514:00/1413:00 GMT, WC [west coast time zone] 1615:00/1514:00 GMT, duration of 17 hours). • Long business hours (for wireless-to-wireless porting) are planned for 9a- 9p in the predominant time zone for each NPAC region (Business Day start – NE/MA/SE 14:00/13:00 GMT, MW/SW/Canadian 15:00/14:00 GMT, WE 16:00/15:00 GMT, WC 17:00/16:00 GMT, duration of 12 hours). • Short Business Days are currently defined as Monday through Friday, except holidays, and Long Business Days are currently defined as Sunday through Saturday (seven days a week), except holidays. Holidays and business hours are defined for each NPAC Region. • If Yes, go to Step 15. • If No, go to Step 12. 12. Receives Second Create? • If Yes, go to Step 13. • If No, return to Step 11. 13. Is Create message valid? • If Yes, go to Step 19. • If No, go to Step 14. 14. NPAC notifies appropriate service provider that Create message is invalid • The NPAC notifies the service provider that errors were encountered during the validation process. • Return to Step 11. 15. Did NNSP send Create? • If Yes, go to Step 20. • If No, go to Step 16. Field Field Field Field Field Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 25 of 48 Version 4.01 Flow Step Description 16. NPAC notifies NNSP and ONSP that T2 has expired • The NPAC notifies both NNSP and ONSP of T2 expiration. 17. Has cancel window for pending SVs expired? • If Yes, go to Step 18. • If No, return to Step 12. 18. Notify Provider – NPAC notifies NNSP and ONSP that port is canceled • The SV is canceled by NPAC by tunable parameter (30 days). Both SPs take appropriate action related to internal work orders. • For the Notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type1 Notification, Figure 8. 19. Return to Figure 6 • Return to Main Porting Flow Figure 6, Create Process, Step 6. 20. NPAC notifies ONSP that porting proceeds under the control of the NNSP • A Notification message is sent to the ONSP noting that the porting is proceeding in the absence of any message from the ONSP. Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 26 of 48 Version 4.01 Reseller/Interconnected VoIP Provider/Type 1 Notification Flow Figure 8 Flow Step Description 1. Is OLSP a Reseller or a Class 2 or 3 Interconnected VoIP Provider or is a Type 1 wireless number involved? • If Yes, go to Step 2. • If No, go to Step 4. 2. Does OLSP need message? • If Yes, go to Step 3. • If No, go to Step 4. 3. ONSP sends or provides information and/or message to OLSP • ?NSP (Network Provider) sends or provides information and/or message to the OLSP (Reseller or Class 2/3 Interconnected VoIP Provider or wireline provider providing Type 1 arrangement) fulfilling all requirements of any service agreement between the involved service providers. 4. Is NLSP a Reseller or Class 2 or 3 Interconnected VoIP Provider? • If Yes, go to Step 5. • If No, go to Step 7. 5. Does NLSP need message? • If Yes, go to Step 6. • If No, go to Step 7. 6. NNSP sends or provides information and/or message to NLSP • ?NSP (Network Provider) sends or provides information and/or message to the NLSP (Reseller or Class 2 or 3 Interconnected VoIP Provider) fulfilling all requirements of any service agreement between the involved service providers. 7. Return • Return to previous flow. Field Field Field Field Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 27 of 48 Version 4.01 Provisioning Without Unconditional 10-Digit Trigger Flow A, Figure 9 Flow Step Description NOTE: Steps 1 and 2 are worked concurrently. 1. NNSP activates port (locally) • This is the entry point from the Inter-Service Provider LNP Operations Flows – Main Porting Flow, tie point A, Figure 6. • The Wireline NNSP activates its own switch translations. • As an optional step, the Wireless NNSP activates its own switch/HLR configuration including assignment of Mobile Station Identifier (MSID). NOTE: Steps 2 and 3 may be worked concurrently. 2. NNSP and ONSP make physical changes (where necessary) • Wireline physical changes may or may not be coordinated. Coordinated physical changes are based on inter-connection agreements between the involved service providers. • Mobile Station (handset) changes are completed. • The NNSP is now providing dial tone to ported end user. 3. NNSP notifies NPAC to activate the port • The NNSP sends an activate message to the NPAC via the SOA interface. • No NPAC SV may activate before the SV due date/time. • If not done in step 1 above, the Wireless NNSP activates its own switch/HLR configuration including assignment of Mobile Station Identifier (MSID). NOTE: Steps 4, 5, 6, and 7 may be concurrent, but at a minimum should be completed ASAP. 4. NPAC downloads (real time) to all service providers • The NPAC broadcasts new SV data to all SP LSMSs in the serving area in accordance with the NANC FRS and NANC IIS. The Service Control Point (SCP) Applications and Global Title Translations (GTT) Function for Number Portability requirements are defined by T1S1.6. 5. NPAC records date and time in history file • The NPAC records the current date and time as the Activation Date and Time stamp, at the start of the broadcast. The Activation Complete Timestamp is based on the first LSMS that successfully acknowledged receipt of new SV. 6. ONSP removes translations in the switch/HLR • The Wireline ONSP initiates the removal of translations either at designated Due Date and Time, or if the order was designated as coordinated, upon receipt of a call from the NNSP. • The Wireless ONSP initiates the removal of the subscriber record from the switch/HLR after the activation of the port. • It is necessary for the OLSP to terminate the End User’s service for the ported TN(s) after the port is completed. Inter-Service Provider LNP Operations Flows – Narratives Page 28 of 48 Version 4.01 Flow Step Description 7. NPAC logs failures and non- responses and notifies the NNSP and ONSP • The NPAC resends the activation to an LSMS that did not acknowledge receipt of the request, based on the retry tunable and retry interval. The number of NPAC SMS attempts to send is a tunable parameter for which the current setting is one (1) attempt, in which case no retry attempts are performed. Once this cycle is completed, NPAC personnel, when requested, investigate possible problems. In addition, the NPAC sends a Notification via the SOA interface to both NNSP and ONSP with a list of LSMSs that failed activation. 8. All service providers update routing databases (real time download) • This is an internal process and is performed in accordance with the Service Control Point (SCP) Applications and GTT Function for Number Portability requirements as defined by ATIS T1S1.6 (within 15 minutes). 9. NNSP may verify completion • The NNSP may make test calls to verify that calls to ported numbers complete as expected. Z. End • Return to Main Porting Flow, tie point Z, Figure 6. Inter-Service Provider LNP Operations Flows – Narratives Page 29 of 48 Version 4.01 Provisioning With Unconditional 10-Digit Trigger Flow AA, Figure 10 Flow Step Description 1. ONSP activates unconditional 10 digit trigger in the switch • This is the entry point from the Inter-Service Provider LNP Operations Flows – Main Porting Flow, tie point AA, Figure 6. • For both Simple and Non-Simple Ports, the wireline ONSP must deploy the 10-digit trigger in the donor switch, if technically feasible, or monitor the NPAC for activation in order to trigger the disconnect, or carriers perform a database query for every call origination. • A 10-digit trigger is applied by the ONSP no later than 11:59pm the day prior to the due date. • The unconditional 10-digit trigger may optionally be applied by the NNSP. NOTE: Steps 2 and 3 may be worked concurrently. 2. NNSP activates switch translations • The NNSP activates its own switch translations. 3. NNSP and ONSP make physical changes (where necessary) • Any physical work or changes are made by either NNSP or ONSP, as necessary. • Physical changes may or may not be coordinated. Coordinated physical changes are based on inter-connection agreements between the involved service providers. • The NNSP is now providing dial-tone to ported in user 4. NNSP notifies NPAC to activate the port • The NNSP sends an activate message via the SOA interface to the NPAC. • No NPAC SV may activate before the SV due date/time. NOTE: Steps 5, 6, and 7 may be concurrent, but at a minimum should be completed ASAP. 5. NPAC downloads (real time) to all service providers • The NPAC broadcasts new SV data to all SPs in the serving area in accordance with the NANC FRS and NANC IIS. The Service Control Point (SCP) Applications and GTT Function for Number Portability requirements are defined by T1S1.6. 6. NPAC records date and time in history file • The NPAC records the current date and time as the Activation Date and Time stamp, at the start of the broadcast. The Activation Complete Timestamp is based on the first LSMS that successfully acknowledged receipt of new subscription version. 7. NPAC logs failures and non- responses and notifies the NNSP and ONSP • The NPAC resends the activation to a Local SMS that did not acknowledge receipt of the request, based on the retry tunable and retry interval. The number of NPAC attempts to send is a tunable parameter for which the current setting is one (1) attempt, in which case no retry attempts are performed. Once this cycle is completed NPAC personnel, when requested, investigate possible problems. In addition, the NPAC sends a Notification via the SOA interface to both the NNSP and ONSP with a list of LSMSs that failed activation. Inter-Service Provider LNP Operations Flows – Narratives Page 30 of 48 Version 4.01 Flow Step Description 8. All service providers update routing data (real time download) • This is an internal process and is performed in accordance with the Service Control Point (SCP) Applications and GTT Function for Number Portability requirements as defined by ATIS T1S1.6 (within 15 minutes). 9. ONSP removes appropriate translations • After update of its databases the ONSP removes translations associated with the ported TN(s). The removal of these translations (1.) will not be done until the old Service Provider has evidence that the port has occurred, or (2.) will not be scheduled earlier than 11:59 PM one day after the due date, or (3.) will be scheduled for 11:59 PM on the due date, but can be changed by an LSR supplement received no later than 9:00 PM local time on the due date. This LSR supplement must be submitted in accordance with local practices governing LSR exchange, including such communications by telephone, fax, etc. • It is necessary for the OLSP to terminate the End User’s service for the ported TN(s) after the port is completed. 10. NNSP may verify completion • The NNSP may make test calls to verify that calls to ported numbers complete as expected. Z. End • Return to Main Porting Flow, tie point Z, Figure 6. Inter-Service Provider LNP Operations Flows – Narratives Page 31 of 48 Version 4.01 Conflict Flow For The Service Creation Provisioning Process Flow B, Figure 11 Flow Step Description 1. Is conflict restricted? • The conflict flow is entered through the Provisioning process flow (Main Porting Flow) through tie point (B), Figure 6, when the ONSP enters a concurrence flag of “No”, and designates a conflict cause code. • Conflict is restricted (i.e., SV may not be placed into conflict by the ONSP) if one of the following: • The ONSP previously placed the subscription into conflict, or • The ONSP never sent a create message for this subscription, or • The request was initiated too late: • For wireline Simple Ports, the request was initiated after the tunable time (Simple Port Conflict Restriction Window, current value of 9:00pm in the predominate time zone of the NPAC region where the number is being ported) one Business Day before the Due Date and T2 Timer (Final Concurrence Window tunable parameter) has expired. • For wireline Non-Simple Ports, the request was initiated after the tunable time (Conflict Restriction Window, current value of 12:00) one Business Day before the Due Date and T2 Timer (Final Concurrence Window tunable parameter) has expired. • For wireless SPs using short timers for this SV, the request was initiated after the T2 Timer (Final Concurrence Window tunable parameter) has expired. • If Yes, go to Step 2. • If No, go to Step 3. 2. NPAC rejects the conflict request • NPAC notifies SP of rejection. • The porting process resumes as normal, proceeding to the Provisioning process flow (Main Porting Flow) at tie point BB, Figure 6. 3. Notify Provider – NPAC changes the subscription status to conflict and notifies NNSP and ONSP • For the notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. • Both SPs take appropriate action related to internal work orders. • SVs may be modified while in the conflict state (e.g., due date), by either the NNSP or ONSP. 4. NNSP contacts ONSP to resolve conflict. If no agreement is reached, begin normal escalation • The escalation process is defined in the inter-company agreements between the involved service providers. Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 32 of 48 Version 4.01 Flow Step Description 5. Was conflict resolved within conflict expiration window? • From the time an SV is placed in conflict, there is a tunable window (Conflict Expiration Window, current value of 30-calendar day limit after the due date) after which it is removed from the NPAC database. If it is resolved within the tunable window, go to Step 7; if not, the subscription request will “time out” and go to Step 6. 6. Notify Provider – NPAC initiates cancellation and notifies NNSP and ONSP • For the Notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure8. • Both SPs take appropriate action related to internal work orders. 7. Was port request canceled to resolve conflict? • Conflict resolution initiates one of two actions: 1) cancellation of the subscription, or 2) resumption of the service creation provisioning process. If the conflict is resolved by cancellation of the subscription, then proceed to the Cancellation Flows for Provisioning Process through tie point C, Figure 12. If the conflict is otherwise resolved, go to Step 8. 8. Was resolution message from ONSP? • If Yes, go to Step 9. • If No, go to Step 10. 9. Notify Provider – NPAC notifies the NNSP and ONSP of “conflict off” via SOA • For the Notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. • NPAC notifies both SPs of the change in SV status. The porting process resumes as normal, proceeding to the Provisioning process flow (Main Porting Flow) at tie point BB, Figure 6. 10. Did NNSP send resolution message during the restriction window? • If conflict was resolved within tunable business hours (current values of six hours for wireline-involved Non-Simple Ports [Long Conflict Resolution New Service Provider Restriction], two hours for wireline- involved Simple Ports [Medium Conflict Resolution New Service Provider Restriction], and six hours for wireless [Short Conflict Resolution New Service Provider Restriction] ), only the ONSP may notify NPAC of “conflict off”. If conflict was resolved after tunable hours, either the NNSP or ONSP may notify NPAC of “conflict off”. • In order for the porting process to continue at least one SP must remove the SV from conflict. • If Yes, go to Step 11. • If No, go to Step 12. 11. NPAC rejects the conflict resolution request from NNSP • NPAC sends an error to the NNSP indicating conflict resolution is not valid at this point in time. • Return to Step 5. 12. Was the Conflict Cause Code 50 or 51? • If Yes, go to Step 11. • If No, go to Step 9. Z. End • Return to Main Porting Flow, tie point Z, Figure 6. Field Field Field Field Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 33 of 48 Version 4.01 Cancellation Flows For Provisioning Process Cancel Flow, Figure 12 Introduction A service order and/or subscription may be canceled through the following processes: • The end user contacts the NLSP or OLSP and requests cancellation of their porting request. • Conflict Flow For The Service Creation Provisioning Process – Flow B, Figure 11: As a result of the Conflict Resolution process (at tie-point C) the NLSP and OLSP agree to cancel the SV and applicable service orders. Flow Step Description 1. End User request to cancel • The Cancellation Process may begin with an End User requesting cancellation of their pending port. The Cancellation process flow applies only to that period of time between SV creation, and either activation or cancellation of the porting request. If activation completed and the End User wishes to revert back to the former SP, it is accomplished via the Provisioning Process. 2. Did End User contact NLSP? • The end user contacts either the NLSP or OLSP to cancel the porting request. Only the NLSP or OLSP can initiate this transaction, not another SP. • The contacted SP gathers information necessary for sending the supplemental request to the other SP noting cancellation, and for sending the cancellation request to NPAC. • If Yes, go to Step 3. • If No, go to Step 7. 3. Is NLSP a Reseller or Class 2 or 3 Interconnected VoIP Provider? • If Yes, go to Step 4. • If No, go to Step 5. 4. NLSP sends cancel request to NNSP • The NLSP notifies the NNSP, via their inter-company interface, indicating that the porting request is to be canceled. 5. NNSP sends SUPP to ONSP noting cancellation as soon as possible and prior to activation • The NNSP fills out and sends the supplemental request form to the ONSP via their inter-company interface, indicating cancellation of the porting request. 6. NNSP sends cancel request to the NPAC • The NNSP notifies the NPAC, via the SOA interface, indicating the porting request is to be canceled. Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 34 of 48 Version 4.01 Flow Step Description 7. OLSP obtains End User authorization • The OLSP obtains actual authority from the End User to act as the official agent on behalf of the End User to cancel the porting request. The OLSP is responsible for demonstrating such authority as necessary. 8. Is OLSP a Reseller or Class 2 or 3 Interconnected VoIP Provider? • If Yes, go to Step 9. • If No, go to Step 10. 9. OLSP sends cancel request to ONSP • The OLSP notifies the ONSP, via their inter-company interface, indicating that the porting request is to be canceled. 10. ONSP sends cancel request to NPAC • The OLSP, contacted directly by the End User or notified by the NNSP via their inter-company interface, sends a cancellation message to the ONSP, via their inter-company interface. • The ONSP notifies the NPAC, via the SOA interface, indicating the porting request is to be canceled. • The ONSP takes appropriate action related to internal work orders. 11. Did the provider requesting cancel send a Create message to NPAC? • This is the entry point from the Inter-Service Provider LNP Operations Flows – Conflict Flow For The Service Creation Provisioning Process, tie point C, Figure 11. • This cancellation message is accepted by the NPAC only if the ONSP had previously created during the SV creation. If the ONSP does not send a create message to the NPAC for this SV, it cannot subsequently send a cancellation message. • If Yes, go to Step 13. • If No, go to Step 12. 12. NPAC rejects the cancel request • NPAC sends an error via the SOA interface indicating that a cancel request cannot be sent for an SV that did not have a matching create from that SP. 13. Did both NNSP and ONSP send Create message to NPAC? • The NPAC tests for receipt of cancellation messages from the two SPs based on which SP had previously sent a message into the NPAC. Since the ONSP create is optional for SV creation, if the ONSP did not send a message during the creation process, the ONSP input during cancellation is not accepted by the NPAC. Similarly, if during the SV creation process only the ONSP sent a message, and not the NNSP, only the ONSP input is accepted when canceling an order. • If Yes, go to Step 15. • If No, go to Step 14. 14. Notify Provider – NPAC updates subscription to cancel, logs status change, and notifies NNSP and ONSP • For the Notification process, refer to Inter-Service Provider LNP Operations Flows –Reseller/Class 2 or 3 Interconnected VoIP Provider/Type 1 Notification, Figure 8. • For a “non-concurred” SV, when the first cancellation message is received, the NPAC sets the SV status directly to cancel, and proceeds to tie point Z. Both NNSP and ONSP are notified of this change in status via the SOA interface. Field Field Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 35 of 48 Version 4.01 Flow Step Description 15. Notify Provider – NPAC updates subscription to cancel-pending, logs status change, and notifies NNSP and ONSP • For the Notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Class 2 or 3 Interconnected VoIP Provider/Type 1 Notification, Figure 8. • For a “concurred” SV, when the first cancellation message is received, the NPAC sets the SV status to cancel-pending. Both NNSP and ONSP are notified of this change in status via the SOA interface. 16. Did NNSP send cancel to NPAC? • If Yes, go to Step 17. • If No, go to Step 21. 17. Did NPAC receive cancel ACK from ONSP within first cancel window timer? • The NPAC applies a nine (9)-business hour [tunable parameter] time limit on receiving cancellation acknowledgment messages from both SPs. This is referred to as the Cancellation-Initial Concurrence Window. The ACK is optional for the SP that initiated the cancel request. • Short business hours are defined as 7a-7p CT (Business Day start at 13:00/12:00 GMT, duration of 12 hours). • Medium business hours (for wireline-involved Simple porting) are defined as 7a-12a Monday through Friday, excluding NPAC-defined Holidays in the predominant time zone for each NPAC region (Business Day start at NE/MA/SE [eastern time zone] 1312:00/1211:00 GMT, MW/SW/Canadian [central time zone] 1413:00/1312:00 GMT, WE [mountain time zone] 1514:00/1413:00 GMT, WC [west coast time zone] 1615:00/1514:00 GMT, duration of 17 hours). • Long business hours are planned for 9a-9p in the predominant time zone for each NPAC region (Business Day start – NE/MA/SE 14:00/13:00 GMT, MW/SW/Canadian 15:00/14:00 GMT, WE 16:00/15:00 GMT, WC 17:00/16:00 GMT, duration of 12 hours). • Short Business Days are currently defined as Monday through Friday, except holidays, and Long Business Days are currently defined as Sunday through Saturday (seven days a week), except holidays. Holidays and business hours are defined for each NPAC Region. • If Yes, go to Step 20. • If No, go to Step 18. 18. NPAC notifies ONSP that cancel ACK is missing • The Cancellation-Initial Concurrence Window starts with receipt of the first cancellation message at NPAC. When this timer expires, the NPAC requests the missing information from ONSP via the SOA interface. Only “concurred” subscriptions reach this point in the process flow. Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 36 of 48 Version 4.01 Flow Step Description 19. NPAC waits for either cancel ACK from ONSP or expiration of second cancel window timer • The NPAC applies an additional nine (9) business hour [tunable parameter] time limit on receiving cancellation acknowledgment messages from both Service Providers. This is referred to as the Cancellation-Final Concurrence Window. The ACK is optional for the SP that initiated the cancel request. • Short business hours are defined as 7a-7p CST (Business Day start at 13:00 GMT, duration of 12 hours). • Medium business hours (for wireline-involved Simple porting) are defined as 7a-12a Monday through Friday, excluding NPAC-defined Holidays in the predominant time zone for each NPAC region (Business Day start at NE/MA/SE [eastern time zone] 1312:00/1211:00 GMT, MW/SW/Canadian [central time zone] 1413:00/1312:00 GMT, WE [mountain time zone] 1514:00/1413:00 GMT, WC [west coast time zone] 1615:00/1514:00 GMT, duration of 17 hours). • Long business hours are planned for 9a-9p in the predominant time zone for each NPAC region (Business Day start – NE/MA/SE 8a-8p CST, MW/SW 9a-9p CST, WE 10a-10p CST, WC 11a-11p CST, duration of 12 hours). • Short Business Days are currently defined as Monday through Friday, except holidays, and Long Business Days are currently defined as Sunday through Saturday (seven days a week), except holidays. Holidays and business hours are defined for each NPAC Region. • Either upon receipt of the concurring ACK notification or the expiration of the second cancel window timer, go to Step 20. 20. Notify Provider – NPAC updates subscription to cancel, logs cancel and notifies NNSP and ONSP • For the notification process, refer to Inter-Service Provider LNP Operations Flows –Reseller/Class 2 or 3 Interconnected VoIP Provider/Type 1 Notification, Figure 8. • The porting request is canceled by changing the subscription status to canceled. Both Service Providers are notified of the cancellation via the SOA interface. Field Inter-Service Provider LNP Operations Flows – Narratives Page 37 of 48 Version 4.01 Flow Step Description 21. Did NPAC receive cancel ACK from NNSP within first cancel window timer? • The NPAC applies a nine (9)-business hour [tunable parameter] time limit on receiving cancellation acknowledgment messages from both SPs. This is referred to as the Cancellation-Initial Concurrence Window. The ACK is optional for the SP that initiated the cancel request. • Short business hours are defined as 7a-7p CT (Business Day start at 13:00/12:00 GMT, duration of 12 hours). • Medium business hours (for wireline-involved Simple porting) are defined as 7a-12a Monday through Friday, excluding NPAC-defined Holidays in the predominant time zone for each NPAC region (Business Day start at NE/MA/SE [eastern time zone] 1312:00/1211:00 GMT, MW/SW/Canadian [central time zone] 1413:00/1312:00 GMT, WE [mountain time zone] 1514:00/1413:00 GMT, WC [west coast time zone] 1615:00/1514:00 GMT, duration of 17 hours). • Long business hours are planned for 9a-9p in the predominant time zone for each NPAC region (Business Day start – NE/MA/SE 14:00/13:00 GMT, MW/SW/Canadian 15:00/14:00 GMT, WE 16:00/15:00 GMT, WC 17:00/16:00 GMT, duration of 12 hours). • Short Business Days are currently defined as Monday through Friday, except holidays, and Long Business Days are currently defined as Sunday through Saturday (seven days a week), except holidays. Holidays and business hours are defined for each NPAC Region. • If Yes, go to Step 20. • If No, go to Step 22. 22. NPAC notifies NNSP that cancel ACK is missing • The Cancellation-Initial Concurrence Window starts with receipt of the first cancellation message at NPAC. When this timer expires, the NPAC requests the missing information from NNSP via the SOA interface. Only “concurred” subscriptions reach this point in the process flow. Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 38 of 48 Version 4.01 Flow Step Description 23. Did NPAC receive cancel ACK from NNSP within second cancel window timer? • The NPAC applies an additional nine (9)-business hour [tunable parameter] time limit on receiving cancellation acknowledgment messages from both SPs. This is referred to as the Cancellation-Final Concurrence Window. The ACK is optional for the SP that initiated the cancel request. • Short business hours are defined as 7a-7p CT (Business Day start at 13:00/12:00 GMT, duration of 12 hours). • Medium business hours (for wireline-involved Simple porting) are defined as 7a-12a Monday through Friday, excluding NPAC-defined Holidays in the predominant time zone for each NPAC region (Business Day start at NE/MA/SE [eastern time zone] 1312:00/1211:00 GMT, MW/SW/Canadian [central time zone] 1413:00/1312:00 GMT, WE [mountain time zone] 1514:00/1413:00 GMT, WC [west coast time zone] 1615:00/1514:00 GMT, duration of 17 hours). • Long business hours are planned for 9a-9p in the predominant time zone for each NPAC region (Business Day start – NE/MA/SE 14:00/13:00 GMT, MW/SW/Canadian 15:00/14:00 GMT, WE 16:00/15:00 GMT, WC 17:00/16:00 GMT, duration of 12 hours). • Short Business Days are currently defined as Monday through Friday, except holidays, and Long Business Days are currently defined as Sunday through Saturday (seven days a week), except holidays. Holidays and business hours are defined for each NPAC Region. • If Yes, go to Step 20. • If No notification is received prior to second cancel window timer expiration, proceed to tie-point CC, “Cancellation Ack Missing from New Provider Provisioning Process”, Figure 13. Z. End • Return to Main Porting Flow, tie point Z, Figure 6. Field Inter-Service Provider LNP Operations Flows – Narratives 1 Disconnect Date: Date the telephone number or numbers are no longer associated between an End User and the current Service Provider. 2 Effective Release Date: Date the telephone number reverts back to NPA/NXX holder/owner. Page 39 of 48 Version 4.01 Cancellation Ack Missing from New Provider Provisioning Process Figure 13 Flow Step Description Note that the Cancellation Conflict process flow is reached only for “concurred” subscriptions. 1. Notify Provider – NPAC updates subscription to conflict, logs conflict, and notifies NNSP and ONSP • This is the entry point from the Inter-Service Provider LNP Operations Flows – Cancellation Flow For Provisioning Process, tie point CC, Figure 12. • If the NNSP does not provide a cancellation notification message to NPAC, in spite of a Cancellation LSR from the ONSP and a reminder message from NPAC, the subscription is placed in a conflict state. NPAC also writes the proper conflict cause code to the subscription record, and notifies both SPs, with proper conflict cause code, of the change in status via the SOA interface. • For the notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. • Both SPs take appropriate action related to internal work orders. 2. Did NPAC receive cancel message from NNSP? • Only “missing cancellation ACK from New SP” subscriptions reach this point in the process flow. The subscription will transition to pending or cancel. • With the subscription in conflict, it is only the NNSP who controls the transaction. The NNSP makes a concerted effort to contact the ONSP prior to proceeding. • If Yes, go to Step 3. • If No, go to Step 5. 3. NNSP notifies NPAC to cancel subscription • The NNSP may decide to cancel the subscription. If so, they notify NPAC of this decision via the SOA interface. 4. Notify Provider – NPAC updates subscription to cancel, logs cancel, and notifies NNSP and ONSP • Following notification by the NNSP to cancel the subscription, NPAC logs this information, and changes the subscription status to canceled. Both SPs are notified of the change in the subscription status via the SOA interface. • For the Notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. • Both SPs take appropriate action related to internal work orders. • Return to Main Porting Flow, tie point Z, Figure 6. Field Field Inter-Service Provider LNP Operations Flows – Narratives 1 Disconnect Date: Date the telephone number or numbers are no longer associated between an End User and the current Service Provider. 2 Effective Release Date: Date the telephone number reverts back to NPA/NXX holder/owner. Page 40 of 48 Version 4.01 Flow Step Description 5. Has conflict expiration window expired? • At this point in the process flow, the subscription status is conflict, and is awaiting conflict resolution or the expiration of the tunable window (Conflict Expiration Window, current value of 30 days). • If Yes, go to Step 6. • If No, go to Step 7. 6. Notify Provider – NPAC updates subscription to cancel, logs cancel, and notifies NNSP and ONSP • After no response from the NNSP for 30 calendar days regarding this particular subscription, NPAC changes the status to canceled and notifies both SPs of the change in status via the SOA interface. • For the notification process, refer to Inter-Service Provider LNP Operations Flows – – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. • Both SPs take appropriate action related to internal work orders. • Return to Main Porting Flow, tie point Z, Figure 6. 7. Did NPAC receive resolve conflict message from NNSP • The NNSP may choose to proceed with the porting process, in spite of a cancellation message from the ONSP. As both SPs are presumably basing their actions on the End User’s request, and each is apparently getting a different request from that End User, each should ensure the accuracy of the request. • If the NNSP decides to proceed with the porting, they send a resolved conflict message via the SOA interface. • It is the responsibility of the NNSP to contact the ONSP, to request that related work orders which support the porting process are performed. The ONSP must support the porting process. • If Yes, go to Step 8. • If No, return to Step 2. 8. Has NNSP conflict resolution restriction expired? • At this point in the process flow, the subscription status is conflict, and is awaiting conflict resolution or the expiration of the tunable window (current values of six hours for wireline-involved Non-Simple Ports [Long Conflict Resolution New Service Provider Restriction], two hours for wireline-involved Simple Ports [Medium Conflict Resolution New Service Provider Restriction], and six hours for wireless [Short Conflict Resolution New Service Provider Restriction]). • The conflict resolution restriction window is only applicable the first time a subscription is placed into conflict, whether the conflict is invoked by the NPAC due to this process, or placed into conflict by the ONSP. • If Yes, go to Step 9. • If No, go to Step 10. 9. Notify Provider – NPAC notifies NNSP and ONSP of ‘conflict off’ via SOA • For the Notification process, refer to Inter-Service Provider LNP Operations Flows – – Reseller/Interconnected VoIP Provider/Type 1 Notification , Figure 8. • NPAC notifies both SPs of the change in subscription status. The porting process resumes as normal, at tie-point BB, Figure 6. Field Field Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives 1 Disconnect Date: Date the telephone number or numbers are no longer associated between an End User and the current Service Provider. 2 Effective Release Date: Date the telephone number reverts back to NPA/NXX holder/owner. Page 41 of 48 Version 4.01 Flow Step Description 10. NPAC rejects the resolve conflict request from NNSP • The NNSP has sent the resolve conflict message before the expiration of the conflict resolution restriction window. NPAC returns an error message back via the SOA interface. • Return to Step 2. Inter-Service Provider LNP Operations Flows – Narratives 1 Disconnect Date: Date the telephone number or numbers are no longer associated between an End User and the current Service Provider. 2 Effective Release Date: Date the telephone number reverts back to NPA/NXX holder/owner. Page 42 of 48 Version 4.01 Disconnect Process for Ported Telephone Numbers Figure 14 Flow Step Description 1. End User initiates disconnect • The End User provides disconnect date and negotiates intercept treatment with current SP. 2. Is NLSP a Reseller or Class 2 or 3 Interconnected VoIP Provider? • If Yes, go to Step 3. • If No, go to Step 4. 3. NLSP sends disconnect request to NNSP • Current Local SP sends disconnect request to current Network SP, per inter-company processes. 4. NNSP initiates disconnect • NNSP initiates disconnect of service based on request from NLSP or End User. • NNSP initiates disconnect of service based on regulatory authority(s). 5. NNSP arranges intercept treatment when applicable • NNSP arranges intercept treatment as negotiated with the end user, or, when the disconnect is SP initiated, per internal processes. 6. NNSP creates and processes service order • NNSP follows existing internal process flows to ensure the disconnect within its own systems. 7. NNSP notifies NPAC of disconnect date 1 and indicates effective release date 2 • NNSP notifies NPAC of disconnect date via the SOA interface and indicates effective release date, which defines when the broadcast occurs. • If no effective release date is given, the broadcast from the NPAC is immediate. The maximum interval between disconnect date and effective release date is 18 months. 8. Has effective release date been reached? • If Yes, go to Step 9. • If No, repeat Step 8. 9. NPAC broadcasts subscription deletion to all applicable providers • On effective release date, the NPAC broadcasts SV deletion to all applicable SPs via the LSMS interface. 10. Notify Provider – NPAC notifies code/block holder of disconnected TN(s), disconnect and release dates • On effective release date, the NPAC notifies code/block holder of the disconnected TN(s), effective release and disconnect dates via the SOA interface. Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives 1 Disconnect Date: Date the telephone number or numbers are no longer associated between an End User and the current Service Provider. 2 Effective Release Date: Date the telephone number reverts back to NPA/NXX holder/owner. Page 43 of 48 Version 4.01 Flow Step Description 11. NPAC deletes TN(s) from active database • On effective release date, the NPAC removes telephone number from NPAC database. 12. End Inter-Service Provider LNP Operations Flows – Narratives Page 44 of 48 Version 4.01 Audit Process Figure15 Flow Step Description 1. Service Provider requests an audit from NPAC • An SP may request an audit to assist in resolution of a repair problem reported by an End User. Prior to the audit request, the SP completes internal analysis as defined by company procedures and, if another SP is involved, attempts to jointly resolve the trouble in accordance with inter- company agreements between the involved service providers. Failing to resolve the trouble following these activities, the SP requests an audit. 2. NPAC issues queries to appropriate LSMSs • The NPAC issues queries to the LSMSs involved in the customer port. 3. NPAC compares own subscription version to LSMS subscription version • Upon receipt of the LSMS subscription version, the comparison of the NPAC and LSMS subscription versions is made to determine if there are discrepancies between the two databases. • If an LSMS does not respond, it is excluded from the audit. 4. NPAC downloads updates to LSMSs with subscription version differences • If inaccurate routing data is found, the NPAC broadcasts the correct subscription version data to any involved SPs networks to correct inaccuracies. 5. Are all audits completed? • If Yes, go to Step 6. • If No, return to Step 4. 6. Notify Provider – NPAC reports audit completion and discrepancies to requestor • The NPAC reports to the requesting SP following completion of the audit to allow the SP to close the trouble ticket. • Upon request, the NPAC provides ad hoc reports to SPs that wish to determine which SPs are launching audit queries to their LSMS. Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. 7. End Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 45 of 48 Version 4.01 Code Opening Process Figure 16 Flow Step Description 1. NPA-NXX holder notifies NPAC of NPA-NXX Code(s) being opened for porting • The SP responsible for the NPA-NXX being opened must notify the NPAC via the SOA or LSMS interface within a regionally agreed upon time frame. • In the case of numbers that use a Type 1 wireless interconnection, the corresponding NPA-NXX needs to be opened by the Old Wireline SP. 2. NPAC updates its NPA-NXX database • The NPAC updates its databases to indicate that the NPA-NXX has been opened for porting. 3. NPAC sends notice of code opening to all Service Providers • The NPAC provides advance notice via the object creation message of the scheduled opening of NPA-NXX code(s) via the SOA and LSMS interface. Currently the NPAC vendor is also posting the NPA-NXX openings to the secure website. 4. End Inter-Service Provider LNP Operations Flows – Narratives Page 46 of 48 Version 4.01 First TN Ported in NPA-NXX Figure 17 Flow Step Description 1. NPAC successfully processes create request for TN subscription version • SP notifies the NPAC of SV creation for a TN in an NPA-NXX. 2. NPAC successfully processes create request for NPA- NXX-X • NPAC successfully processes an NPA-NXX-X for a Number Pool Block. 3. First Subscription Version activity in NPA-NXX? • If Yes, go to Step 4. • If No, go to Step 5. 4. Notify Provider – NPAC sends notification of first TN ported to all providers via SOA and LSMS • When the NPAC receives the first SV create request in an NPA-NXX, it will broadcast a “heads-up” notification to all SPs via the SOA and LSMS interfaces. Upon receipt of the NPAC message, all SPs, within five (5) Business Days, will complete the opening for the NPA-NXX code for porting in all switches. • Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. 5. End Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 47 of 48 Version 4.01 Cancel-Undo Process Figure 18 Flow Step Description 1. Provider requests a cancel-undo • The Cancel-Pending Undo Process may begin with a Service Provider requesting the reversal (undo) of an in-progress cancel for their cancel- pending port. 2. Is the subscription in cancel-pending status? • If Yes, go to Step 4. • If No, go to Step 3. 3. NPAC rejects the cancel-undo request • NPAC sends an error to the requesting SP indicating the current SV status is not valid for a cancel-undo request. • Go to Step 6. 4. Did the provider requesting a cancel-undo issue a cancel for this subscription? • If Yes, go to Step 5. • If No, repeat Step 3. 5. Notify Provider – NPAC updates subscription to status prior to cancel and notifies NNSP and ONSP • Upon cancel-undo, NPAC logs this information, and changes the subscription status to the status prior to the cancel (either pending or conflict). Both SPs are notified of the change in the subscription status via the SOA interface. • For the notification process, refer to Inter-Service Provider LNP Operations Flows – Reseller/Interconnected VoIP Provider/Type 1 Notification, Figure 8. • Both SPs take appropriate action related to internal work orders. 6. End Field Field Field Field Inter-Service Provider LNP Operations Flows – Narratives Page 48 of 48 Version 4.01 Tunable Name Current Tunable Value T1, Short Initial Concurrence Window 1 hour T1, Medium Initial Concurrence Window 3 hours T1, Long Initial Concurrence Window 9 hours T2, Short Final Concurrence Window 1 hour T2, Medium Final Concurrence Window 3 hours T2, Long Final Concurrence Window 9 hours Conflict Restriction Window 12:00pm (Noon) Simple Port Conflict Restriction Window 21:00 Conflict Expiration Window 30 days Long Conflict Resolution New Service Provider Restriction 6 hours Medium Conflict Resolution New Service Provider Restriction 2 hours Short Conflict Resolution New Service Provider Restriction 6 hours Long Cancellation-Initial Concurrence Window 9 hours Medium Cancellation-Initial Concurrence Window 9 hours Short Cancellation-Initial Concurrence Window 9 hours Long Cancellation-Final Concurrence Window 9 hours Medium Cancellation-Final Concurrence Window 9 hours Short Cancellation-Final Concurrence Window 9 hours Short Business Day Start 07:00 CT Short Business Day Duration 12 hours Medium Business Day Start 07:00 predominate TZ Medium Business Day Duration 17 hours Long Business Day Start 09:00 predominate TZ Long Business Day Duration 12 hours