80 likes | 240 Views
9-1-1 Selective Routing Denver / Colorado. 9-1-1 Selective Routing Introduction. The CLEC 9-1-1 network is designed to accommodate ANI failure. Each trunk group serves a specific default PSAP based on an assigned Emergency Service Number (ESN).
E N D
9-1-1 Selective RoutingIntroduction • The CLEC 9-1-1 network is designed to accommodate ANI failure. Each trunk group serves a specific default PSAP based on an assigned Emergency Service Number (ESN). • 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. • 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. • 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 9-1-1 trunk group. • 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 9-1-1 trunk group. • 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.
Denver Market 9-1-1 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. • Remove NPA-NXX and NPA-NXX-X wildcards in the SRDB. • Reload 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.
Denver Market 9-1-1 Default Routing Strategic Proposal • Seek a CO PUC Recommendation • Request that the Colorado PUC commission a recommendation with support from industry subject matter experts. • Case study: Atlanta established Multi-jurisdictional-PSAPs as a result of Rate Center Consolidations. • Case 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
Denver Market 9-1-1 Default RoutingCall Scenario with ANI and ALI Default Area "A" 9-1-1 is Dialed End Office SRDB 303-333-1000 ESN 001 303-333-1922 ESN 003 303-333-2050 ESN 200 303-333-2111 ESN 004 PSAP ESN 001 Police Fire Ambulance Trunk Group 922 ESN 200 Default PSAP ESN 200 SCENARIO DATA Customer Address: Within Default Area "A" Customer Rate Center: Consolidated Customer TN: 303-333-1000 Customer's Primary ESN: 001 (based on ALI) Customer's Default ESN: 200 (based on TG) Service Effective: 03/01/2002 9-1-1 Dialed: 03/08/2002 E9-1-1 Control Office Trunk Group 933 ESN 300 Police Fire Ambulance SRDB PSAP ESN 002 Default Area "B" 9-1-1 Database Police Fire Ambulance PSAP ESN 003 MSAG CALL FLOW 1: Call routed over primary facility trunk group 922. 2: Call received by 911SR with ANI. 3: TN look up performed in SRDB. 4: TN found. 5: ESN determined to be 001. 6: Call routed to Primary PSAP associated with ESN 001. 7: Caller information presented on console. Default PSAP ESN 300 Police Fire Ambulance PSAP ESN 004 Note: All numeric data is fictitious
Denver Market 9-1-1 Default RoutingCall Scenario without ANI Default Area "A" 9-1-1 is Dialed End Office PSAP ESN 001 Police Fire Ambulance Trunk Group 922 ESN 200 Default PSAP ESN 200 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/2002 9-1-1 Dialed: 03/08/2002 E9-1-1 Control Office Trunk Group 933 ESN 300 Police Fire Ambulance SRDB PSAP ESN 002 Default Area "B" 9-1-1 Database Police Fire Ambulance PSAP ESN 003 MSAG CALL FLOW 1: Call routed over primary facility trunk group 922. 2: 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 200. 6: Caller information not presented on console. 7: Caller queried for location information. Default PSAP ESN 300 Police Fire Ambulance PSAP ESN 004 Note: All numeric data is fictitious
Denver Market 9-1-1 Default RoutingCall Scenario with ANI and without ALI - PROPOSED Default Area "A" 9-1-1 is Dialed End Office SRDB 303-333-1000 ESN 001 303-333-1922 ESN 003 303-333-2050 ESN 200 303-333-2111 ESN 004 PSAP ESN 001 Police Fire Ambulance Trunk Group 922 ESN 200 Default PSAP ESN 200 SCENARIO DATA Customer Address: Within Default Area "A" Customer Rate Center: Consolidated Customer TN: 303-333-1000 Customer's Primary ESN: 001 Customer's Default ESN: 200 Service Effective: 03/01/2002 9-1-1 Dialed: 03/02/2002 E9-1-1 Control Office Trunk Group 933 ESN 300 Police Fire Ambulance SRDB PSAP ESN 002 Default Area "B" 9-1-1 Database Police Fire Ambulance PSAP ESN 003 MSAG CALL FLOW 1: Call routed over primary facility trunk group 922. 2: 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 200. 6: Caller information not presented on console. 7: Caller queried for location information. Default PSAP ESN 300 Police Fire Ambulance PSAP ESN 004 Note: All numeric data is fictitious
Denver Market 9-1-1 Default RoutingCall Scenario with ANI and without ALI - ACTUAL Default Area "A" 9-1-1 is Dialed End Office SRDB 303-333 ESN 300 303-333-1000 ESN 001 303-333-1922 ESN 003 303-333-2050 ESN 200 303-333-2111 ESN 004 PSAP ESN 001 Police Fire Ambulance Trunk Group 922 ESN 200 Default PSAP ESN 200 SCENARIO DATA Customer Address: Within Default Area "A" Customer Rate Center: Consolidated Customer TN: 303-333-1001 Customer's Primary ESN: Unknown Customer's Default ESN: 200 (known based on TG) Service Effective: 03/01/2002 9-1-1 Dialed: 03/02/2002 E9-1-1 Control Office Trunk Group 933 ESN 300 Police Fire Ambulance SRDB PSAP ESN 002 Default Area "B" 9-1-1 Database Police Fire Ambulance PSAP ESN 003 MSAG CALL FLOW 1: Call routed over primary facility trunk group 922. 2: 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 303-333 of ESN 300. 5: Call routed to PSAP associated with ESN 300. 6: Caller information not presented on console. 7: Caller queried for location information. 8: Call transferred to separate jurisdiction Default PSAP ESN 300 Police Fire Ambulance PSAP ESN 004 Note: All numeric data is fictitious