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

1

LOCAL NETWORK SERVICES . . . Lead with Local

06/14/2002

9-1-1Selective RoutingDenver / Colorado

2


06/14/2002

9-1-1 Selective RoutingIntroduction

1. 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).

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 9-1-1 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 9-1-1 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


06/14/2002

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.

o Remove NPA-NXX and NPA-NXX-X wildcards in the SRDB.o 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.

4


06/14/2002

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.

o Case study: Atlanta established Multi-jurisdictional-PSAPs as a result of Rate Center Consolidations.

o 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

5


06/14/2002

Denver Market 9-1-1 Default RoutingCall Scenario with ANI and ALI

MSAG

9-1-1 isDialed

SCENARIO DATACustomer Address:

Within Default Area "A"Customer Rate Center:

ConsolidatedCustomer TN:

303-333-1000Customer's Primary ESN:

001 (based on ALI)Customer's Default ESN:

200 (based on TG)Service Effective:

03/01/20029-1-1 Dialed:

03/08/2002

PoliceFire

Ambulance

PoliceFire

Ambulance

PSAPESN 002

Default Area "A"

PSAPESN 001

PoliceFire

Ambulance

PoliceFire

Ambulance

Default Area "B"

DefaultPSAPESN 200

PSAPESN 003

9-1-1Database

E9-1-1ControlOffice

DefaultPSAPESN 300

PSAPESN 004

CALL FLOW1: 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.

SRDB

EndOffice

Trunk Group 933ESN 300


SRDB303-333-1000 ESN 001303-333-1922 ESN 003303-333-2050 ESN 200303-333-2111 ESN 004

Note: All numeric data is fictitious

6


06/14/2002

Denver Market 9-1-1 Default RoutingCall Scenario without ANI

MSAG

9-1-1 isDialed



UnknownCustomer TN:

UnknownCustomer's Primary ESN:

Look up not possibleCustomer's Default ESN:

200 (based on TG)Service Effective:

03/01/20029-1-1 Dialed:

03/08/2002

Default Area "A"

PoliceFire

Ambulance

PoliceFire

Ambulance

Default Area "B"

PSAPESN 003

9-1-1Database

DefaultPSAPESN 300

PSAPESN 004

CALL FLOW1: 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 2005: Call routed to PSAP associated with ESN 200.6: Caller information not presented on console.7: Caller queried for location information.

SRDB

EndOffice


PoliceFire

Ambulance

PoliceFire

Ambulance

PSAPESN 002

PSAPESN 001

DefaultPSAPESN 200

E9-1-1ControlOfficeTrunk Group 933

ESN 300


7


06/14/2002

Denver Market 9-1-1 Default RoutingCall Scenario with ANI and without ALI - PROPOSED

MSAG

9-1-1 isDialed





001Customer's Default ESN:

200Service Effective:

03/01/20029-1-1 Dialed:

03/02/2002

Default Area "A"

PoliceFire

Ambulance

PoliceFire

Ambulance

Default Area "B"

PSAPESN 003

9-1-1Database

DefaultPSAPESN 300

PSAPESN 004

CALL FLOW1: 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 2005: Call routed to PSAP associated with ESN 200.6: Caller information not presented on console.7: Caller queried for location information.

SRDB

EndOffice


PoliceFire

Ambulance

PoliceFire

Ambulance

PSAPESN 002

PSAPESN 001

DefaultPSAPESN 200


ESN 300

SRDB303-333-1000 ESN 001303-333-1922 ESN 003303-333-2050 ESN 200303-333-2111 ESN 004


8


06/14/2002

Denver Market 9-1-1 Default RoutingCall Scenario with ANI and without ALI - ACTUAL

MSAG

9-1-1 isDialed





UnknownCustomer's Default ESN:

200 (known based on TG)Service Effective:

03/01/20029-1-1 Dialed:

03/02/2002

Default Area "A"

PoliceFire

Ambulance

PoliceFire

Ambulance

Default Area "B"

PSAPESN 003

9-1-1Database

PSAPESN 004

CALL FLOW1: 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

SRDB

EndOffice


PoliceFire

Ambulance

PoliceFire

Ambulance

PSAPESN 002

PSAPESN 001

DefaultPSAPESN 200


ESN 300

SRDB303-333 ESN 300303-333-1000 ESN 001303-333-1922 ESN 003303-333-2050 ESN 200303-333-2111 ESN 004

DefaultPSAPESN 300


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

Documents

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