1. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 1 IP-Based Emergency Applications and Services for Next Generation Networks PEACE Prof. Tasos Dagiuklas* Dept. of Telecommunication Systems and Networks TEI of Mesolonghi Nafpaktos-Greece *also Senior Research Associate Dept. of Electrical and Computer Engineering University of Patras Patras-Greece

2. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 2 General Information  Project within the Joint FP7 ICT-Security Call  It was started on September 2008  Duration: 27 Months  Web Site: www.ict-peace.eu

3. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 3 Consortium

4. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 4 PEACE – Objectives (1)  Technical level –Specify and develop a framework for enhancing IMS with secure emergency services –Provide a general solution for secure communications in extreme emergency situations based on the IMS framework. –Integrate the PEACE framework with autonomic networking infrastructure in a secure and reliable manner in case of network collapse. In its normal mode of operation, PEACE nodes will act as an info-station based network, providing Peer-to-Peer (P2P) VoIP and video communications, as well as location aware services such as communicating weather, driving and traffic conditions, targeted infomercials delivery, real-time monitoring and road safety.

5. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 5 PEACE – Objectives (2)  Deployment/ business level –Evaluate the implications on the current emergency models of the PEACE concept, determine business plans for upgradeability / replacement and provide roadmaps for evolution.

6. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 6 PEACE - Challenges NGN/IMSAd-hoc networks Joint evaluation of the requirements Daily Emergency Applications Extreme Emergency Applications ConceptLevel PSAP ImplementationSecure Multimedia and P2P ImplementationLevel Integration Deployment and Evaluation Level Planning and deployment System Evaluation Functionality/Protocols ExtensionsArchitectures Emergency Risk Management And Coordination System

7. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 7 Daily versus Extreme Emergency Services  Extreme Emergency Services –When Network Collapse (e.g. Massive Fire, Flooding, Terrorist Attack) –It is used by Rescue Workers Civil Protection Agencies Fire brigade vehicles Ambulance vehicles  Daily Emergency Service –When Alert by people using All-IP Networking infrastructures –It is used by Police Fire-brigade

8. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 8 Technology Enablers  Daily Emergency Services –IMS Infrastructure –Application Servers –All-IP Networking Infrastructure –Security  Extreme Emergency Services –Ad-hoc networks –P2P Overlays –P2P Multimedia Streaming –Security  Emergency Risk Management and Coordination System –Handling Emergency Requests –Decisions Support System

9. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 9 Some Trends  Provide answer to the growing demand for emergency services in Next Generation (All-IP) Network –Solution Use applications platform in order to handle and manage emergency service Enhance the end-users clients to support this kind of vital services Support reliability (against failures and network break down ) and security (against attacks and abuse)  Provide answer to the need for emergency services in case of networks’ collapse –Solution Exploit the use of ad-hoc network to provide applications and services in emergency situations Investigate how the end-users can support emergency services in this kind of networking paradigm Support resilience and security by applying autonomic networking techniques

10. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 10 State of the Art  IP Multimedia Subsystem (IMS) has been standardised by both 3GPP and ETSI TISPAN as the subsystem to manage applications and services at both fixed and wireless access part

11. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 11 IP Multimedia Subsystems and Trends  How we can provide emergency services in IMS  How will provide emergency services in case of network collapse  Solution –To modify the IMS architecture for the support of emergency applications by developing the necessary components that provide, user location, public safety answering point, interfaces with PSTN, interfaces with other VoIP standards, failover techniques, overload handling, scalability, resistance to attacks and abuse –Use ad-hoc networks for the provisioning of extreme emergency applications in case of network collapse by investigating self- configuration and management if there is no support from infrastructure, self protection against attacks

12. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 12 Ad-hoc Networks  Study their availability/reliability by taking into account impairments at physical layer  Employ key management schemes to enforce security  Secure mechanisms at the routing level  Build trust establishments among different overlays  Apply security mechanisms on P2PSIP  Study P2P Video Communications over ad-hoc networks

13. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 13 PEACE Solution Daily Emergency Situations Extreme Emergency Services NGN infrastructure (IP network) IMS Service Platform Applications and services (e.g. VoIP) Reliability & Security on Signalling integration Integration with PSAPs QoS control Integration with fixed networks Ad-hoc solutions P2P Services Emergency Risk Management And Coordination System

14. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 14 PEACE Framework

15. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 15 Daily Emergency Service Requirements (1)  Unauthenticated emergency calls –Balancing between misuse and mistakes vs. real need PSAP workload –Service provider is not necessarily IP-connectivity provider (WiMAX, Wi-Fi, fixed) VoIP emergency call over internet without ISP subscription? VoIP emergency call over cellular without cellular subscription? IMS emergency call over cellular without cellular subscription?  Emergency callback –“just a normal call towards the user”  Local emergency numbers –Number distribution –multiple numbering scheme for different emergency services  Location of emergency calls –Routing to the PSAP responsible for users area –Dispatching the emergency service to correct address –Provision of network level location information -> who is allowed to receive location information (free)?  Confidentiality –User anonymity? –User location privacy?

16. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 16 Daily Emergency Service Requirements (2)

17. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 17 Extreme Emergency Service Requirements  How to perform emergency calls when network collapses –Distributed Architecture using Autonomic Networking Self Organizing, Reliability Security –Secure Communications over the ad-hoc nodes –P2P Overlay over Ad-hoc networks –VoIP and Video communications over Autonomous Networks

18. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 18 The Implementation – Functional Blocks PSAP in IMS NGN and IMS IMS Development Integration and trials Emergency in IMS Reliability in NGN/IMS Secure Com Autonomous Communications Ad-Hoc Development P2P over Ad-Hoc Multimedia over Ad-Hoc Networks Emergency Risk Management And Coordination System

19. Emergency Services Workshop, 21th-24 th of October, Vienna, Austria Page 19 Questions Email: ntan@teimes.gr, ntan@ece.upatras.gr