North American Emergency Services Brian Rosen Emergicom

9-1-1 Calls Single universal number for all networks throughout North America (wireline, wireless, …) Answered at one of ~6,134 Public Safety Answering Points Dispatched to tens of thousands of police/fire/emergency medical agencies A function of LOCAL government, not significantly controlled by state/federal governments – Often City or County – But often there are multiple PSAPs per county – Please don’t ask us to fix this, it’s been tried

PSAP Boundaries Every PSAP has a service area All calls from within that boundary must go to that PSAP PSAP boundaries do not necessarily lie on neat (e.g. City, County) boundaries The DEFINITION of a PSAP boundary is currently done on a street/number basis, which has been manually translated into a point/polygon form also Dealing with non-trivial boundaries is the big problem in routing calls

Wireline Calls SUBSCRIBER E911 TANDEM OFFICE END OFFICE ANI PSAP ATTENDENT POSITIONS COMMON EQUIPMENT SRDB ALI HOST

Wireline Calls Caller Dials End Office detects emergency calls and forwards to Selective Router tandem Caller phone number is looked up in SR DB to determine which PSAP to direct call to PSAP looks up caller phone number in ALI DB to display location and to determine Emergency Services Zone (combo of police, fire and EMS services)

ERDB & ALI DB Translates phone number to location & routing data Maintained by a designated service provider Carriers process service orders into ALI (and SR DB) for new/changed customers Location (to be associated with phone number) is VALIDATED against the Master Street Address Guide prior to entry in the ALI

MSAG Validation Database for locations Lists every address (actually an address range) in the area served by the local system Maintained by the local authority. Normally one MSAG per local authority (which often covers more than one PSAP), but there are exceptions Contains the ESN (code for ESZ) Indirectly specifies the PSAP to which the call is sent Implies the S/R (MSAG coverage doesn’t normally cross S/R service areas, but they do sometimes).

Wireless (Phase II) Calls MSC PDEMPC ESNE (Selective Router) ESME (ALI Database) CRDBPSAP E5E5 E 12 E3E3 E 11 E2E2 AiAi DiDi Cellsite (ESP) (ISUP) (ANSI-41) (LSP) (ANSI-41) CRDBCoordinate Routing Database PDEPosition Determining Entity MSCMobile Switching Center MPCMobile Position Center CAMA

Wireless Phase II calls Mobile Switching Center (MSC) queries Mobile Positioning Center (MPC) for routing MPC uses position information from PDE and CRDB to determine which PSAP Given which PSAP, the call is forwarded to the correct Selective Router based on a route code obtained from the CRDB A key (ESRK), which looks like a phone number, is assigned to the call The key has an entry in the SR DB and ALI that causes the S/R to route the call to the correct PSAP The location in the ALI for that key is updated dynamically to have the actual location (as well as the call back number, since the ALI is the key and not the calling party number The location is provided as lat/lon, not street address. The PSAPs deploy a Geographic Information Service that translates geo to civil; dispatch is always civil Location can be updated during the call. The PSAP asks (bids) and the ALI database responds

NENA “i2”

Gateway’s VoIP to selective router via a gateway (ESGW) Uses SIP with PIDF-LO to send location VoIP Positioning Center (VPC) queries a database (ERDB) with location to obtain a routing token (ESRN) and an ALI/SR DB key (ESQK) ESRN token will cause the call to go to the right port on the gateway, which means to the correct S/R ESQK will cause the call to go to the right PSAP ESQK location will be updated as with wireless Phase II to display the actual location