Crisis Calling in SIP .


24 views
Uploaded on:
Category: Medical / Health
Description
Emergency Calling in SIP. Henning Schulzrinne (with Anshuman Rawat, Matthew Mintz-Habib, Amrita Rajagopal and Xiaotao Wu) Dept. of Computer Science Columbia University hgs@cs.columbia.edu. Overview. VoIP emergency communications What makes emergency calling hard? Stages of deployment
Transcripts
Slide 1

Crisis Calling in SIP Henning Schulzrinne (with Anshuman Rawat, Matthew Mintz-Habib, Amrita Rajagopal and Xiaotao Wu) Dept. of Computer Science Columbia University hgs@cs.columbia.edu Emergency calling

Slide 2

Overview VoIP crisis correspondences What makes crisis calling hard? Phases of arrangement I1: speedy fixes I2: in reverse good I3: end-to-end IP Initial model NENA + IETF endeavors Emergency calling

Slide 3

VoIP crisis interchanges crisis call crisis ready ("backwards 911") dispatch community coordination Emergency calling

Slide 4

E911 TANDEM OFFICE SUBSCRIBER SRDB END OFFICE ANI PSAP COMMON EQUIPMENT ALI HOST ATTENDENT POSITIONS 7 3 7 2 5 4 5 6 1 Current wireline calls dial 911, 112 course call to right PSAP outline to municipal area (Brian Rosen) Emergency calling

Slide 5

MSC ESNE (Selective Router) Cellsite An i D i (ISUP) CAMA CRDB PSAP E 12 E 3 (ANSI-41) (ANSI-41) E 11 (LSP) PDE MPC ESME (ALI Database) E 5 E 2 (ESP) MSC Mobile Switching Center MPC Mobile Position Center CRDB Coordinate Routing Database PDE Position Determining Entity Wireless (Phase II) Calls (Brian Rosen) Emergency calling

Slide 6

Components of crisis calling now move all IP Contact understood number or identifier 112 911 112 911 dial 112, 911 flag sos@ Route call to area fitting PSAP specific switch VPC DNS Deliver exact area to call taker to dispatch crisis telephone number  area (ALI query) in-band  enter  area in-band Emergency calling

Slide 7

What makes VoIP 112/911 hard? Crisis calling

Slide 8

The center issue VSP sees crisis call however does not know guest area ISP/IAP knows client area yet does not handle call Emergency calling

Slide 9

More than agony… Multimedia from the guest video catch from mobile phones video for communication via gestures content informing and continuous content for the hard of hearing Data conveyance guest information: floor arrange, hazardous materials information, medicinal cautions estimation information input: car accident information, EKGs, … Delivering video to the guest e.g., CPR preparing Load adjusting and excess as of now just restricted auxiliary PSAP VoIP can exchange over-burden calls anyplace Location conveyance convey area with sent and exchanged calls different area objects (city + geo) Emergency calling

Slide 10

Core long haul necessities Media-impartial voice (+TDD) to start with, IM and video later Work in frameworks without a voice benefit supplier numerous undertakings will give their own nearby voice administrations Allow down-stream call information access and additionally access to other "tertiary" information about the occurrence Globally deployable autonomous of national crisis number (9-1-1, 1-1-2, and so on.) regard jurisdictional limits – minimize requirement for cross-jurisdictional coordination permit use regardless of the possibility that gear and administration suppliers are not neighborhood travel, imported hardware, far-flung areas Testable: evident city addresses ("MSAG approval") call course approval Secure and dependable Emergency calling

Slide 11

Staged sending ~6,134 PSAPs in North America normal 2-3 dynamic call takers every some serve town, some huge parts of a state just ~30% of PSAPs can get geo organizes 30-40% might be voice just numerous utilizing 1970s telecom innovation "CAMA" (administrator) trunks constrained to conveying 8 (territorial) or 10 digits (national) of data as of now confronting weight from supporting cell administrations Phase I (cell tower and face) and Phase II (guest geo area) EU: littler number of PSAPs, yet frequently without area conveyance Initial rendition ("I1"): dial 10-digit regulatory number like telematics administrations does not convey guest area to PSAP Emergency calling

Slide 12

Three phases to VoIP 911 Emergency calling

Slide 13

IP space Emergency Services Provider Network PSTN E9 - 1 - 1 Selective Call server/Router ESGW(s ) intermediary server VPC SRDB VPC DHCP ALI DB ESZ DB LIS RDB MSAG VDB DBMS DNS I2 engineering (draft) Routing Proxy & Redirect server(s ) v6 v4 v5 v4 E9 - 1 - 1 PSAP Selective Router v1 IP Domain v2 User Agent v - e2 v0 v8 v3 area data benefit v7 VoIP situating focus steering database approval database Emergency calling

Slide 14

I3: Location-based call directing – UA knows its area GPS INVITE sips:sos@ 48° 49\' N 2° 29\' E outbound intermediary server DHCP 48° 49\' N 2° 29\' E  Paris fire division Emergency calling

Slide 15

I3 (long haul) design segments Common URL for crisis calls sips:sos@ home-area Convey nearby crisis number to gadgets Allow gadgets to get their area specifically by means of GPS in a roundabout way by means of DHCP (MAC  switch port  area database) on LAN by means of LLDP (802.1ab, TIA LLDP-MED) at first, regularly through manual setup Route calls to right goal utilizing turn upward as a part of gadget or intermediary Emergency calling

Slide 16

Location, area, area Location  find right PSAP & speed dispatch In the PSTN, neighborhood 9-1-1 calls remain geologically nearby In VoIP, no such region for VSPs most VSPs have near national scope Thus, not at all like landline and remote , require area data from the earliest starting point Unlike PSTN, voice benefit supplier doesn\'t have wire database data VSP needs help from get to supplier (DSL, link, WiMax, 802.11, … ) Emergency calling

Slide 17

Options for area conveyance L2: LLDP-MED (institutionalized variant of CDP + area information) occasional per-port communicate of setup data L3: DHCP for geospatial (RFC 3825) municipal (draft-ietf-geopriv-dhcp-common) L7: recommendations for recoveries by IP address by MAC address by identifier (passed on by DHCP or PPP) Emergency calling

Slide 18

DHCP for areas changed dhcpd (ISC) to create area data utilize MAC deliver backtracing to get area data 8:0:20:ab:d5:d DHCP server CDP + SNMP 8:0:20:ab:d5:d  458/17 DHCP reply: sta=DC loc=Rm815 lat=38.89868 long=77.03723 458/17  Rm. 815 458/18  Rm. 816 Emergency calling

Slide 19

Location-related issues Delivery How does call or end framework get area data? Approval Does the urban address exist and does it have a related PSAP? "MSAG approval" Verification Is this the genuine address of the client (as opposed to an endeavor to misdirect)? Protection Avoid uncovering area data to outsiders Avoid area divulgence outside a crisis call Emergency calling

Slide 20

Columbia/MapInfo model Goal: manufacture model VoIP SIP-based crisis calling framework including guest end framework call directing (DNS) PSAP foundation Use product segments where conceivable Test unwavering quality and excess Emergency calling

Slide 21

Components No support inferred – different segments likely will fill in too Emergency calling

Slide 22

Call steering Emergency calling

Slide 23

Call directing proposition DNS delineate to mark chain of importance penetrate down scan for geo IRIS whois-like query convention (registry) LUMP utilizes SOAP (web administrations) engineering for dependability no root server – P2P among section hubs Emergency calling

Slide 24

Detail: I3 - DNS-based determination DHCP INFORM psap.state.vt.gov SIP w/area MAC  loc Perl taste cgi script psap.state.vt.gov DNS NAPTR: addison.vt.us algonquin-dr.addison.vt.us … restrictive TCP-based convention 151.algonquin-dr.addison.vt.us.sos-arpa.net Emergency calling

Slide 25

IRIS-based determination <request xmlns="urn:ietf:params:xml:ns:iris1"> <searchSet> <findEconByCivic xmlns="urn:ietf"> <civilAddress> <country>US</country> <A1>New York</A1> <A3>New York</A3> <A6>Broadway</A6> </civilAddress> <service>police</service> </findEconByCivic> </searchSet> </request> IRIS = present day "whois" seek convention, over BEEP just indicates question, not upgrade <response xmlns="urn:ietf:params:xml:ns:iris1"> <resultSet> <answer> <emergencyContact xmlns="urn:ietf:" authority="nyc.example" registryType="econ1" entityClass="econ" entityName="nypd"> <displayName>NYPD</displayName> <uri>sip://nypd.example/</uri> </emergencyContact> </answer> </resultSet> </response> Emergency calling

Slide 26

LUMP: Location-to-URL Mapping VSP 1 bunch serving VSP 1 duplicate root data group serves VSP 2 123 Broad Ave Leonia Bergen County NJ US root hubs NJ US NY US sip:psap@leonianj.gov look referral Bergen County NJ US Leonia NJ US Emergency calling

Slide 27

3 rd party call control Emergency calling

Slide 28

3 rd Party Call Control Flow Emergency calling

Slide 29

Call taker setup SIPc customer gets calls GeoLynx programming shows guest area Emergency calling

Slide 30

GeoLynx shows area GeoLynx listens for charges from SIPc Emergency calling

Slide 31

INVITE REFER INVITE media information INVITE REFER INVITE media information Emergency call conferencing PSAP brings all related gatherings into a telephone call Hospital Fire division INVITE Conference server Recorder 3 rd party call control PSAP Caller Emergency calling

Slide 32

Scaling NENA: "assessed 200 million calls to 9-1-1 in the U.S. every year"  roughly 6.3 calls/second if 3 minute call, around 1,200 simultaneous calls average SIP intermediary server (e.g., sipd) on 1 GHz PC can deal with around 400 call entries/second along these lines, probably not going to be server-bound Emergency calling

Slide 33

Current institutionalization endeavors NENA (National Emergency Number Association) I2 and I3 design necessities in light of operational needs of PSAPs ETSI OCG – EMTEL exploratory – additionally crisis notice NRIC objectives and long haul engineering IETF: indi

Recommended
View more...