PRESENTATION

434 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
434
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

PRESENTATION

  1. 1. Ernst Langmantel Technical Director, Austrian Regulatory Authority for Broadcasting and Telecommunication (RTR GmbH) The opinions expressed in this presentation are the personal views of the author and do not prejudge decisions of the Austrian regulatory authority Internet / Next Generation Emergency Calls
  2. 2. Contents <ul><li>Basic Service Architecture Elements </li></ul><ul><li>Legacy networks (PSTN/ISDN, GSM/UMTS) </li></ul><ul><ul><li>Architecture – Outgoing Calls – Emergency Calls </li></ul></ul><ul><li>Internet </li></ul><ul><ul><li>Architecture – Outgoing Calls – Emergency Calls </li></ul></ul><ul><li>NGN (ITU/ETSI) </li></ul><ul><ul><li>Architecture – Outgoing Calls – Emergency Calls </li></ul></ul><ul><li>IETF/Internet and ITU/ETSI NGN – Synergies ? </li></ul>
  3. 3. Basic Service Architecture Elements
  4. 4. Terminal Terminal Networks and Terminals Transport Network Edge [Terminals, Application servers] Network of Networks Service Connectivity, Signalling
  5. 5. Terminal Media Streams / User Data Path Terminal Transport Network Edge [Terminals, Application servers] Network of Networks Service Connectivity, Signalling
  6. 6. Terminal Signalling Terminal Transport Network Edge [Terminals, Application servers] Network of Networks Service Connectivity, Signalling
  7. 7. Legacy networks (PSTN/ISDN, GSM/UMTS) Architecture – Outgoing Calls – Emergency Calls
  8. 8. Transport Service Connectivity, Signalling PSTN /ISDN, GSM/UMTS – Architecture [simplified] Service control and physical routing points combined in “Telephone Exchanges” Without service interconnection ( service interoperability ) between networks the service area is restricted to area of individual networks
  9. 9. g Caller / Called in Home Network Service Connectivity, Signalling H H PSTN /ISDN, GSM/UMTS – Outgoing/ Emergency Call [simplified] In case of emergency calls national emergency routing information is retrieved locally in the telephone exchange or from a national data base Transport
  10. 10. H Service Connectivity V H Caller in Visited Network GSM/UMTS – Roaming Outgoing /Emergency Calls [simplified] Call control in visited network In case of emergency calls national emergency routing information is retrieved locally in the telephone exchange or from a national data base Transport PSAP
  11. 11. Internet Architecture – Outgoing Calls – Emergency Calls
  12. 12. Transport (IP-Packets) Service Connectivity, Signalling Internet Services - Architecture [simplified] ONLY IP-Interoperability necessary for GLOBAL service area ! Service control (call control) at the network edge. NO CONTROL of network transport by service control
  13. 13. Service Connectivity, Signalling Internet VoIP - Outgoing Call [simplified] Global service area without service interoperability between providers “ Home Position” IP-interoperability between networks Transport (IP-Packets)
  14. 14. Service Connectivity, Signalling Internet VoIP – Outgoing Call [simplified] IP-Interoperability between networks Different Service/Application Providers Transport (IP-Packets) Interoperability between services/ applications of network edge, not relevant for networks
  15. 15. Service Connectivity, Signalling Internet VoIP - Emergency Call Solution (ECRIT) [simplified] LoST fully distributed international emergency routing data base Location & type of emergency PSAP UrI Where do I get PSAP Url in visited country? Type of emergency & location Transport (IP-Packets) H H PSAP
  16. 16. LoST Functionality ( Lo cation-to- S ervice T ranslation Protocol) <ul><ul><li>Satisfies the requirements (draft-ietf-ecrit-requirements) for mapping protocols </li></ul></ul><ul><ul><li>Civic as well as geospatial queries </li></ul></ul><ul><ul><ul><li>civic address validation </li></ul></ul></ul><ul><ul><li>Recursive and iterative resolution </li></ul></ul><ul><ul><li>Fully distributed and hierarchical deployment </li></ul></ul><ul><ul><ul><li>can be split by any geographic or civic boundary </li></ul></ul></ul><ul><ul><ul><li>same civic region can span multiple LoST servers </li></ul></ul></ul><ul><ul><li>Indicates errors in civic location data  debugging </li></ul></ul><ul><ul><ul><li>but provides best-effort resolution </li></ul></ul></ul><ul><ul><li>Supports overlapping service regions </li></ul></ul><ul><li>Source: SDO Emergency Services Coordination Workshop (5./6.10.2006, Columbia University, New York), A Lo cation-to- S ervice T ranslation Protocol (LoST)- Mapping Protocol Architecture, Ted Hardie, Andrew Newton, Henning Schulzrinne, Hannes Tschofenig </li></ul>
  17. 17. LoST Conclusions <ul><li>Mapping is core component of emergency calling problem </li></ul><ul><li>LoST fully international and distributed </li></ul><ul><ul><li>tries to avoid “who runs the root” problem </li></ul></ul><ul><li>optimized for efficient use in mobile end systems </li></ul><ul><li>Source : SDO Emergency Services Coordination Workshop (5./6.10.2006, Columbia University, New York), A Lo cation-to- S ervice T ranslation Protocol (LoST)- Mapping Protocol Architecture, Ted Hardie, Andrew Newton, Henning Schulzrinne, Hannes Tschofenig </li></ul>
  18. 18. NGN (ITU/ETSI) Architecture – Outgoing Calls – Emergency Calls
  19. 19. Physical Transport (IP Packets) Service Connectivity, Signalling NGN – Architecture [simplified] Service control and physical routing in DIFFERENT network elements but fierce control of transport resources by service control within individual networks. Without service interconnection (service interoperability) the service area is restricted to area of individual networks (same as in legacy circuit switched networks)
  20. 20. NGN (IMS) - Outgoing Call [simplified] Roaming User (Exception for Emergency Calls!) Call control for roaming user from “Home Position” (Internet-like) BUT via visited network Caller in visited network Physical Transport (IP-Packets) H Service Connectivity V H
  21. 21. Physical Transport (IP-Packets) NGN (IMS) - Emergency Call NGN [simplified] Roaming User H Service Connectivity V Home Position lacks knowledge of caller location and national emergency routing in visited country Caller in visited network PSAP
  22. 22. Physical Transport (IP-Packets) H Service Connectivity V H In case of emergency calls also in NGN (like in GSM/UMTS) invocation of call control in visted network including access to national emergency routing information to PSAP. NGN (IMS) - Emergency Call NGN [simplified] Roaming User Caller in visited network PSAP
  23. 23. IETF/Internet and ITU/ETSI NGN – Synergies ?
  24. 24. One “Emergency (IP-)World” ? <ul><li>A lot of synergies regarding ITU/ETSI NGN and IETF Internet standards are already in place because 3GPP standardisation is done in collaboration with IETF and NGN built on 3GPP specs. </li></ul><ul><li>Global routing database (LoST) is key element in IETF ECRIT concept. </li></ul><ul><li>Global IETF emergency call routing database should also be able to serve 3GPP and NGN needs. </li></ul><ul><li>No basic change to current basic NGN architecture necessary if NGN reuses IETF data base. NGN Location Retrieval Function (LRF) could access LoST. </li></ul><ul><li>The goal: </li></ul><ul><li>Only one place for the emergency organisations to put their routing requirements data ! </li></ul><ul><li>“ Single point of truth” </li></ul><ul><li>Can the two worlds come together ? </li></ul>
  25. 25. Further Information <ul><li>NGN </li></ul><ul><ul><li>ETSI NGN, IMS emergency session standards </li></ul></ul><ul><ul><ul><ul><li>ETSI TS 102 424 (2005-09) – Requirements for the NGN network to support emergency communication from citizen to authority </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Draft ETSI TS 182 009 (version 12.07.2006) – NGN Architecture to support emergency communication from citizen to authority </li></ul></ul></ul></ul><ul><ul><ul><ul><li>ETSI TS 102 164 (2006-09) – Emergency Location Protocols </li></ul></ul></ul></ul><ul><ul><li>G. Camarillo, M. A. Garcia-Martin, The 3G IP Multimedia Subssystem (IMS), Wiley 2006 </li></ul></ul><ul><li>IETF / ECRIT – Emergency Context Resolution using Internet Technologies </li></ul><ul><ul><li>http://www.ietf.org/html.charters/ecrit-charter.html </li></ul></ul><ul><ul><li>A Wiki page that points to the most important documents: http://www.tschofenig.com/twiki/bin/view/EmergencyServices/EcritReviews (including link to SDO Emergency Services Coordination Workshop (ESW06)) </li></ul></ul><ul><li>IETF : http:// edu.ietf.org / </li></ul>
  26. 26. <ul><li>Thank you very much for your attention ! </li></ul>

×