1 / 19

Emergency Communications Seminar

Emergency Communications Seminar. Ken Carlberg ken . carlberg@jhu . edu Oct 14, 2004 Network Research Group University College London. Emergency. Abnormal and stressed conditions Causes: earthquakes, toxic spills, terrorism, back hoe, etc… Effect: stressed and/or broken resources

kasen
Download Presentation

Emergency Communications Seminar

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Emergency CommunicationsSeminar Ken Carlberg ken.carlberg@jhu.edu Oct 14, 2004 Network Research Group University College London

  2. Emergency • Abnormal and stressed conditions • Causes: earthquakes, toxic spills, terrorism, back hoe, etc… • Effect: stressed and/or broken resources • Break down of organization & communication • Actions • Response • Speed of response during and soon after incident is critical • Recovery

  3. PSTN General Public 911/999/112 Authorized access GETS (U.S.) GTPS (U.K.) Land Mobile Radio Private nets for First Responders Conventional Trunking Project 16a Project 25 Tetra (Europe) Broadcast TV/Radio Emergency Alert System (U.S.) Private systems Military AUTODIN AUTOVON Multi-Level Precedence & Preemption (ITU I.255.3) Internet I-Am-Alive (IAA) Database Dedicated Emergency Systems

  4. Draft Message Action Officer Classified Y Encode Message Action Officer Authorization Officer N Approved Released Y Y Log Message N N Discard Send Msg AUTODIN Message Network Autodin Switching Center (ASC) Ft. Thomas Elfin AFB Terminals Message Switch Ralf AFB Ft. Lollipop • Message Priorities: • Critical • Flash Override • Flash • Immediate • Priority • Routine

  5. 1) JANAP-128 2) RTTUZYUM 3) ZNR UUUU 4) R 020830Z FEB 82 5) FM Commander, Atlantic Fleet 6) TO USS SHIPA 7) BT 8) UNCLASS 9) Happy Birthday 10) BT 11) #0010 12) NNNN AUTODIN Message Line H E A D E R “R” routine Classification Message F O O T E R 139 characters -- 50b = 46 seconds -- 300b = 7.7 -- 9600b = 0.23

  6. Government Emergency Telecommunications System (GETS) • Design Principal • Contracted service with the PSTN (IXC’s and RBOCs) • High probability of call completion • Special queuing of call signaling, alternate carrier routing • User operation • Dial 710-xxx-xxxx non-geographic number • Dial PIN (authorization) • Set NS/EP bit in IAM/ISUP message (T1.631-1993, R1999) • Dial destination number • Key Elements • Probability instead of preemption • “Traveling” capability with distributed authority • Any-to-any model

  7. Government Telephony Preference Scheme (GTPS) • Users divided into 3 classes (1) Phone lines vital to war or national survival (2) Lines used for recovery from disasters (3) Everyone else • Operation • Affected users lose dial tone • Can receive calls, but cannot initiate them • Key Issues • Prioritization is fixed to phone line • Some-to-any model • Implicit authorization

  8. Extension of GETS to cellular Applied to subscriber-to-mobile switch link Constrained preemption 25% of in-progress call attempts can be preempted Call held in queue up to 30 sec Existing calls are not preempted Operation User dials *xx T-mobile (GSM) $0.75 per minute with $4.50 monthly service fee 5 levels of priority 0) Executive leadership 1) Disaster response (coordinators, directors) 2) Public health and law enforcement (senior command) 3) Public services (transportation, water, etc. leadership) 4) Disaster recovery (shelters, infrastructure coordinators) Wireless Priority Service

  9. 911 Switch EO Switch EO Switch 911 & Public Safety Access point (PSAP) PSAP #1 (Anne Arundel County) 410-555-1234 313 Main St LMR-AA 410-555-5678 10 W Lanvale St Verizon LMR-BC PSAP #2 (Baltimore City) • Many-to-one communication model • Multiple PSAPs per carrier • No authorization needed • Man-in-the-loop communication bridge

  10. I-Am-Alive • Developed in Japan under the WIDE project • Prompted by Kobe earthquake of ‘95 • Distributed database repository • Registration of people/users • Query • Mechanisms • Voice, Fax, Email, Web

  11. Autodin, GETS, GTPS, WPS Priority Schemes Binary (off/on) vs list Lists can be content-based, role-based, or combo Authority Fixed vs distributed Service Fixed vs distributed access From Any-to-any to few-to-any Probability versus preemption 999/112/911 No authentication required Many-to-one Television/Radio Single source broadcast LMR Any-to-any One-to-many Push-to-Talk Interesting Characteristics

  12. Sept 11: Telco Info • AT&T: 431 million call attempts, 101 million more than busiest day • Verizon: 300 million, 2 times normal • Mother’s day in the US is 30% increase • Cingular wireless: 400% increase in DC, 1000% increase in NYC • Cellular providers • NYC: 75% calls blocked, 92% at peak hour • DC: 56% of calls blocked • GETS Stats • 18,000 calls worldwide • 10,000 calls to WTC and Pentagon area • completion rate > 95%

  13. Sept 11: Internet Info • “Internet Under Crisis”: Post incident study • http://www.nas.edu • Internet did well. Problems seemed isolated at key access links of news content distributors (eg, CNN) • Pew Report: user experience survey • 43% experienced some trouble • 15% reported great difficulty • 20% gave up • 13% reported using Instant Messaging • CNN: • Average load jumped from 10M page views to 132M • Akamai • Traffic jump 300% • One Instant Messaging provider: 20% increase

  14. Google Stats

  15. Sept 11: JANET Trans-Atlantic link Average: 2,250,781 1,135,716 Average: 2,174,016 1,224,696 Diff/Avg (9/11): +0.4% 10% Diff/Avg (9/12):+4.4% -20% Misc TCP Misc UDP FTP DNS Web Other From US To US 40.42% 3.52 4.65 0.46 49.34 1.73 69.60% 0.66 7.97 0.47 18.55 2.75 10-Sept 40.36% 5.69 4.37 0.44 47.79 1.35 69.74% 1.49 8.64 0.44 14.80 4.89 11-Sept Trans-Atl Capacity – Feb, 02 (6) 155 Mb/s links 38.03% 9.53 4.18 0.45 46.78 1.03 66.38% 3.49 10.03 0.47 13.76 5.87 12-Sept

  16. What to Do? • Migration of emergency systems to IP based networks • Overprovision • Proponents point to complexity of QoS mechanisms, and cost effectiveness • Special Label / QoS / Traffic Engineer • Proponents indicate that over-provisioning may not be an option • Label or mark the traffic that is important and associated with an emergency • Difficult because of added layer of filtering; a new condition • QoS mechanisms to support Labeled traffic • Traffic Engineer to support (or operate in place of) QoS

  17. Internet Emergency Preparedness (IEPREP) Working Group • IETF WG focusing on Requirements, Framework, Best Common Practice documents • RFC-3689: General Requirements for Emergency Telecommunications Service (ETS) • RFC-3690: IP Telephony Requirements for ETS • draft-ietf-ieprep-framework-09.txt • draft-ietf-ieprep-domain-req-02.txt • draft-ietf-ieprep-domain-frame-02.txt • Security Framework draft – probably revised

  18. Related Work • draft-ietf-sip-resource-priority-04.txt • Introduces NameSpace.Value field to SIP • draft-baker-tsvwg-mlpp-that-works-02.txt • Target is for MLPP domain versus across Internet • Rebuttal against: • draft-pierce-tsvwg-assured-service-req-00.txt • draft-pierce-tsvwg-assured-service-arch-00.txt • draft-silverman-tsvwg-mlefphb-01.txt

  19. Thoughts to Consider • “Emergency” may be another argument for role-based networking • Condition-based networking? • Complimentary capabilities • Sensor networks • Overlay networks • Emergency management databases (eg, I-Am-Alive) • The role of priority, probability, and preemption • Influenced by ethics, laws/regulation, scaling • Security • The “magical” Internet minute?

More Related