Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 9-1-1 Selective Routing Denver / Colorado.

Similar presentations


Presentation on theme: "1 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 9-1-1 Selective Routing Denver / Colorado."— Presentation transcript:

1 1 LOCAL NETWORK SERVICES... Lead with Local 06/14/ Selective Routing Denver / Colorado

2 2 LOCAL NETWORK SERVICES... Lead with Local 06/14/ Selective Routing Introduction 1. The CLEC network is designed to accommodate ANI failure. Each trunk group serves a specific default PSAP based on an assigned Emergency Service Number (ESN). 2. An area code and exchange (NPA-NXX) may be used ubiquitously within a rate center which results in telephone numbers (TN) within the NPA-NXX being assigned within multiple default PSAP jurisdictions. 3. ALI records are submitted by the CLECs on day of customer install. The ALI submission results in TN/ESN processing in the SR by the ILEC the next day or thereafter. 4. Where multiple default PSAPs exist within a rate center boundary, line class screening is employed in the CLEC switch to guide a call to a designated CLEC trunk group. 5. When the calling party's number is not determinable by the Selective Router (SR), the call is directed to the PSAP associated with the CLEC trunk group. 6. Where multiple default PSAPs exist within a rate center boundary and when the ALI has not been processed to the SR, NPA-NXX (or NPA-NXX-N) wildcards increase the likelihood of routing to an inappropriate PSAP.

3 3 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market Default Routing Tactical Proposal Recommendation –For Rate Centers with multiple default PSAP boundaries, use current technology available in the DMS 100 to route calls based on Trunk Group in the case where when TN/ESN not found in the SRDB. oRemove NPA-NXX and NPA-NXX-X wildcards in the SRDB. oReload the SRDB with all TN/ESN records (based on ALI DB records). Challenges –To improve load time, determine whether the DMS 100 will accept an SRDB table load from a single restore (over a single night) instead of processing individual TNs in serial (which would take days or weeks). –Regarding incremental costs, determine impacts on existing (Qwest/ICO) network design (as in the case of Remote/Hosts), impacts on switch upgrades, and impacts to the number of channels at affected PSAPs. –To fund costs, identify cost recovery mechanisms (through CO PUC). –To maintain current arrangement where reasonable, determine whether it is desirable/possible to support wildcards for some rate centers while removing wildcards for others. –To ensure follow-up, identify actions to be taken when NRF in SRDB. –To reduce the possibility of a antiquated ALI records appearing at the PSAP, identify whether customer disconnects should result in a delete request in the SRDB.

4 4 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market Default Routing Strategic Proposal Seek a CO PUC Recommendation –Request that the Colorado PUC commission a recommendation with support from industry subject matter experts. oCase study: Atlanta established Multi-jurisdictional-PSAPs as a result of Rate Center Consolidations. oCase study: Minneapolis utilizes trunk group based default routing. Request NENA Develop a Comprehensive Default Routing Standard –Seek a Default Routing standard which includes consideration of Rate Centers which include multiple Default PSAPs. Request Intrado Develop a Near-Real-Time ALIDB/SRDB Update Capability –Request near-real-time updates of both the ALIDB and SRDB. Review Other Qwest Options –Implement Lucent (5Es) as was the case in Minneapolis

5 5 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market Default Routing Call Scenario with ANI and ALI MSAG is Dialed SCENARIO DATA Customer Address: Within Default Area "A" Customer Rate Center: Consolidated Customer TN: Customer's Primary ESN: 001 (based on ALI) Customer's Default ESN: 200 (based on TG) Service Effective: 03/01/ Dialed: 03/08/2002 Police Fire Ambulance Police Fire Ambulance PSAP ESN 002 Default Area "A" PSAP ESN 001 Police Fire Ambulance Police Fire Ambulance Default Area "B" Default PSAP ESN 200 PSAP ESN Database E9-1-1 Control Office Default PSAP ESN 300 PSAP ESN 004 CALL FLOW 1: Call routed over primary facility trunk group : Call received by 911SR with ANI. 3: TN look up performed in SRDB. 4: TN found. 5: ESN determined to be : Call routed to Primary PSAP associated with ESN : Caller information presented on console. SRDB End Office Trunk Group 933 ESN 300 Trunk Group 922 ESN 200 SRDB ESN ESN ESN ESN 004 Note: All numeric data is fictitious

6 6 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market Default Routing Call Scenario without ANI MSAG is Dialed SCENARIO DATA Customer Address: Within Default Area "A" Customer Rate Center: Unknown Customer TN: Unknown Customer's Primary ESN: Look up not possible Customer's Default ESN: 200 (based on TG) Service Effective: 03/01/ Dialed: 03/08/2002 Default Area "A" Police Fire Ambulance Police Fire Ambulance Default Area "B" PSAP ESN Database Default PSAP ESN 300 PSAP ESN 004 CALL FLOW 1: Call routed over primary facility trunk group : Call received by 911SR without ANI. 3: TN look up fails in SRDB. 4: Trunk Group ESN determined to be 200 5: Call routed to PSAP associated with ESN : Caller information not presented on console. 7: Caller queried for location information. SRDB End Office Trunk Group 922 ESN 200 Police Fire Ambulance Police Fire Ambulance PSAP ESN 002 PSAP ESN 001 Default PSAP ESN 200 E9-1-1 Control Office Trunk Group 933 ESN 300 Note: All numeric data is fictitious

7 7 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market Default Routing Call Scenario with ANI and without ALI - PROPOSED MSAG is Dialed SCENARIO DATA Customer Address: Within Default Area "A" Customer Rate Center: Consolidated Customer TN: Customer's Primary ESN: 001 Customer's Default ESN: 200 Service Effective: 03/01/ Dialed: 03/02/2002 Default Area "A" Police Fire Ambulance Police Fire Ambulance Default Area "B" PSAP ESN Database Default PSAP ESN 300 PSAP ESN 004 CALL FLOW 1: Call routed over primary facility trunk group : Call received by 911SR with ANI. 3: TN look up fails in SRDB. 4: Trunk Group ESN determined to be 200 5: Call routed to PSAP associated with ESN : Caller information not presented on console. 7: Caller queried for location information. SRDB End Office Trunk Group 922 ESN 200 Police Fire Ambulance Police Fire Ambulance PSAP ESN 002 PSAP ESN 001 Default PSAP ESN 200 E9-1-1 Control Office Trunk Group 933 ESN 300 SRDB ESN ESN ESN ESN 004 Note: All numeric data is fictitious

8 8 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 Denver Market Default Routing Call Scenario with ANI and without ALI - ACTUAL MSAG is Dialed SCENARIO DATA Customer Address: Within Default Area "A" Customer Rate Center: Consolidated Customer TN: Customer's Primary ESN: Unknown Customer's Default ESN: 200 (known based on TG) Service Effective: 03/01/ Dialed: 03/02/2002 Default Area "A" Police Fire Ambulance Police Fire Ambulance Default Area "B" PSAP ESN Database PSAP ESN 004 CALL FLOW 1: Call routed over primary facility trunk group : Call received by 911SR with ANI. 3: TN look up does not find 10 digit entry in SRDB. 4: NPA-NXX look up finds entry for of ESN : Call routed to PSAP associated with ESN : Caller information not presented on console. 7: Caller queried for location information. 8: Call transferred to separate jurisdiction SRDB End Office Trunk Group 922 ESN 200 Police Fire Ambulance Police Fire Ambulance PSAP ESN 002 PSAP ESN 001 Default PSAP ESN 200 E9-1-1 Control Office Trunk Group 933 ESN 300 SRDB ESN ESN ESN ESN ESN 004 Default PSAP ESN 300 Note: All numeric data is fictitious


Download ppt "1 LOCAL NETWORK SERVICES... Lead with Local 06/14/2002 9-1-1 Selective Routing Denver / Colorado."

Similar presentations


Ads by Google