1. Better than E9-1-1: Possible Enhancements Enabled by the Next Generation Emergency Services Signaling Mary Brown (Cisco)

2. Beyond voice 911: an early look at new applications Mary L. Brown

3. When the “caller” is a data packet  Increasing recognition that emergency traffic will be a mix of voice & data, e.g., health records, sensors  Not all sensors will trigger emergency response or be connected to emergency command centers  But there are already examples of data communications in use triggering emergency response  Purpose today – list a few examples, discussion of likely scenarios, ask what questions these present Growth of sensor networks & data communications

4. Disclaimer  None of the following technologies are Cisco’s  All of the information about these was taken from public sources  Some of the vendors are in the room and are best equipped to answer your detailed questions  Not exhaustive…illustrative

5. Overview Emergency command center Own sensor network Other governmental sensor network Service provider network Privately established sensor networks Now “Tomorrow”

6. Listening for gunfire  “Shotspotter” uses audio sensors placed at various locations to plot the location of the sounds of gunfire  Locates gunfire to with 20-40 feet  Distinguishes it from other sounds  More than one gun fired  DC PD: System has identified 31 shootings and led to three arrests since its installation Deployment today: public safety’s own network

7. Traffic emergencies  Identifying 18-wheel trucks wrongly driving in fast lanes (New Jersey)  Monitoring and responding to traffic entering a ‘breakdown bay” in Sydney, Australia's new Lane Cove tunnel Deployment today: likely on a transportation department network or public safety network

8. Public safety examples  Tracking weather and air pollution in Cambridge MA (CitySense)  100 sensors to be deployed on light poles  Grant from the National Science Foundation  Harvard/BBN Technologies – developed the network  Sensors to alert public safety of flood conditions Mix of other governmental networks and public safety’s own network

9. Intelligent video systems  Scan for abnormal behavior and alert security personnel to respond  Airports: San Francisco International Airport, San Diego International Airport, and Salt Lake City International  City of San Diego example  16 cameras –18 pre-defined behaviors, including fallen persons, abandoned or removed objects, facility intrusion, and lurking or erratically- behaving individuals

10. Personal sensors  Used by emergency responders themselves (e.g., firefighting personnel)  Breath rate, heart rate, activity, posture and skin temperature are all monitored by the sensors in the strap  Remote monitoring by incident commander Deployment probably limited to public safety itself

11. Conclusions and questions  Data-only transmission is “early days”  But likely to grow over time  Vendor-specific solutions predominate  If IP-based, and at application layer, issues are fewer Are these problems only of “common look and feel” in applications? What locational requirements will develop and are they different from the ones already identified for voice? As these applications begin to originate on service provider networks, are there issues separate from voice that must be solved?