Geographical Position Supply Chain


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Geographical Position Supply Chain

    1. 1. Geographical Position Supply Chain Steinar Hidle Andresen (Assisted by Bjørn Næss, Tommy Rafos and Jan Morten Henriksen) Norwegian Network Research Seminar 2004 NTNU
    2. 2. Classes of users <ul><li>Stationary user (device): </li></ul><ul><ul><li>User is connected to the network at a fixed, long-term-stable geographic location. Examples include a home PC or a payphone. </li></ul></ul><ul><li>Nomadic user (device): </li></ul><ul><ul><li>User is connected to the network temporarily, for relatively short durations, but does not move significantly during the lifetime of a network connection or during the emergency call. Examples include a laptop using an 802.11 hotspot or a desk IP phone that is moved from one cubicle to another. </li></ul></ul><ul><li>Mobile user (device): </li></ul><ul><ul><li>User who changes geographic location and possibly their network attachment point during an emergency call. </li></ul></ul>
    3. 3. Stationary User Location (Traditional Approach) PSAP (Public Safety Answering Point) Network Provider Emergency Call 1. Emergency call <CLI and A- number> Provider’s or national database 2. Location Request <CLI> 3. Location Data <CLI, Address> CLI: Calling Line Identification
    4. 4. Mobile User Location (main traditional approach) Enterprise Fleet Management Centre GPS enabled device Reporting position by SMS or GPRS Example: Trondheim Taxi Fleet
    5. 5. Mobile User Location (proposed approach for E-merge calls) PSAP (Public Safety Answering Point) <ul><li>Emergency call </li></ul><ul><li>Position conveyed in the UUS fields </li></ul><ul><li>(PUSH) </li></ul>GSM/GPS enabled device Problem: Most operators has disabled the UUS feature due to misuse. This function has to be reconsidered. Petition has been sent to the 3 G. PSAP (Public Safety Answering Point)
    6. 6. Mobile and Nomadic user location determined by the infrastructure PSAP Location Systems 2. Location Request <A-number/SIP address> 3. Location Data <A-number, Geographical Coordinates> GSM with no GPS Laptop or IP phone with WLAN 1. Emergency call <A- number > 1. Emergency call <SIP address>
    7. 7. Geographical Position Supply Chain Architecture - Producer side GPoS ( G eographical Po sition S ervice) GSM UMTS WLAN Network Dependent Data Extraction ND (Navigation Devices) Units with on-board computation of position, e.g GPS/GNSS based LAN (by cable) Fixed line CS Network Dependent Data Extraction Network Dependent Data Extraction Network Dependent Data Extraction Network Dependent Data Extraction Network Dependent Access Gateway Req/Response Interface. SLAs with Multiple Service Providers/ ND owners SIP Telephony?
    8. 8. Geographical Position Supply Chain Architecture – Consumer Side May feature different levels of data rendering according to authorisation. Also possible to provide anonymous data for statistical purposes GPoS Data assembly, authorisation, and control Statistical Services SLA ” Blue light” Services Emergency and Public Preparedness SLA Commercial ASPs (Serves groups of “subscribers”) SLA GPos for the individual (oneself) SLA
    9. 9. Geographical Position Service (Server) <ul><li>Should be regarded as a “Trusted Entity” in the network </li></ul><ul><li>Provides a ”point” for legal audition and control. </li></ul><ul><li>Provides a common unified access point to authorised geographical position data for: </li></ul><ul><ul><li>“ Blue light” services (Police, Fire brigade, Ambulance). Authorisation to track everyone. </li></ul></ul><ul><ul><li>Application Service Providers: stolen property tracing, fleet management systems, etc. Authorisation to track “subscribers”. </li></ul></ul><ul><ul><li>Single user applications: providing navigational services, Navigational assistant for the blind, etc.. Authorisation to track “oneself”. </li></ul></ul><ul><ul><li>Statistical data (e.g. link driving times on in the road network), data about the individuals to be hided. </li></ul></ul><ul><li>Hides the details of technology and networks/ acts as a “Fire Wall” to prevent unauthorised access to the data providers. </li></ul>
    10. 10. Geographical Position Service <ul><li>From a market perspective a GPoS will benefit 3. Party Service Developers and Providers by </li></ul><ul><ul><ul><li>hiding the technological details of data acquisition </li></ul></ul></ul><ul><ul><ul><li>giving a stable platform for implementation </li></ul></ul></ul><ul><li>This may foster a rapid and strong development of the services offered. </li></ul><ul><li>A GPoS can be realised as </li></ul><ul><ul><li>a centralised server, managed by an authorised party, or </li></ul></ul><ul><ul><li>alternatively in a distributed fashion as modules installed at the premises of the network service providers. In this latter case, the function should act as it where centralised (providing a universal service like e.g. the DNS does). </li></ul></ul>
    11. 11. Geographical Position Supply Architecture -Main Principle INTERROGATING THE DEVICE ITSELF GPoS User device obtains its own location Admin domain/ Network Dependent Access Gateway Local Adm. Location Service Location Request/ response GPS SLA or Location Request/ response Screening?
    12. 12. Geographical Position Supply Architecture Optional Principle INTERROGATING THE LOCAL POSITION SERVICE GPoS Local Adm. Location Service SLA Location Request/response Surveillance/ reporting
    13. 13. Geographical Position Supply Implementation Sample GPoS Network Administration System (NAV) SLA POSNAV (local GPoS) Surveillance/ reporting
    14. 14. Geographical Position Supply Implementation Sample INTERROGATING THE DEVICE ITSELF User device obtains its own location GPS GPoS GPS module SLA 2 Network Administration System (NAV) SLA 1 POSNAV (local GPoS) Surveillance / reporting Location update Location request/response
    15. 15. What are we currently doing? <ul><li>3 persons are busy designing and implementing </li></ul><ul><ul><li>The “framework” and a prototype lab version of the server including interfaces to: </li></ul></ul><ul><ul><ul><li>Production side: </li></ul></ul></ul><ul><ul><ul><ul><li>ITEA’s Network Administration System (NAV). </li></ul></ul></ul></ul><ul><ul><ul><ul><li>GPS enabled GSM phones </li></ul></ul></ul></ul><ul><ul><ul><li>Consuming side: </li></ul></ul></ul><ul><ul><ul><ul><li>AMK (Health emergency Communication Centre) at St. Olavs Hospital </li></ul></ul></ul></ul><ul><ul><ul><ul><li>A simple web based map application on the user side. </li></ul></ul></ul></ul><ul><li>Tools </li></ul><ul><ul><li>Specification </li></ul></ul><ul><ul><ul><li>UML and XMLschema </li></ul></ul></ul><ul><ul><li>Implementation, </li></ul></ul><ul><ul><ul><li>the server is programmed in Java and runs on a Linux server </li></ul></ul></ul><ul><ul><ul><li>we also considering to implement/use </li></ul></ul></ul><ul><ul><ul><ul><li>IETF Geopriv specification, </li></ul></ul></ul></ul><ul><ul><ul><ul><li>The requirements established by the Norwegian authorities, for emergency calls </li></ul></ul></ul></ul><ul><ul><ul><ul><li>OpenGIS (a Geographical Markup Language version) </li></ul></ul></ul></ul>
    16. 16. What are we aiming at <ul><li>A beta specification and a prototype implementation by 31. of Dec. 2004 </li></ul><ul><ul><li>(we have offered a demonstration at the NTNU/TEKNA seminar in January) </li></ul></ul><ul><li>Utilising the platform as a lab-tool for further studies in </li></ul><ul><ul><li>architecture (also security issues) - with a special focus on IP solutions </li></ul></ul><ul><ul><li>how to “produce” location data </li></ul></ul><ul><ul><li>how to use location data (including business models) </li></ul></ul><ul><li>Developing the concept or the “product” for deployment and use in normal networks - not only for the lab (financial support applied for) </li></ul>
    17. 17. Our contact network <ul><li>The Norwegian Post and Tele Authority </li></ul><ul><li>ITEA (Data and Telecom administration at NTNU) </li></ul><ul><li>Uninett (c/o Faltinsen) </li></ul><ul><li>ETSI’s EMTEL work with liaisons to e. g.: </li></ul><ul><ul><li>The European E-merge consortium </li></ul></ul><ul><ul><li>IETF’s Working groups. on Geopriv and Sipping (c/o Schulzrinne) </li></ul></ul><ul><ul><li>NENA (The “911” organisation in the US) </li></ul></ul>
    18. 18. Back up slides
    19. 19. Indication of the emergency caller's location ETSI SR 002 180 V1.1.1 (2003-12), Special Report Requirements for communication of citizens with authorities/organizations in case of distress (emergency call handling) Paragraph: <ul><li>Each emergency call should be accompanied with information that enables the emergency control centre to determine the caller's location at the time of calling. This information may be a geographical address or a set of geographical co-ordinates. The information should be accessible by the emergency control centre via a standardized interface after the initial contact is made. Location information should be accessible for as long as the emergency lasts. </li></ul><ul><li>NOTE 1: This information is required and has importance in the case of co-ordinating disaster relief. The impact this requirement has on the Network operator may vary on a national basis. The PSAP/Emergency Control Centre may only make requests for Location information in conjunction with an emergency call. </li></ul><ul><li>Typically, location information is based on the CLI received with the call for wireline networks, and on the geographical co-ordinates of the caller for wireless networks. For roaming cordless terminals due to emergency provision of the home base station CLI may be desirable. </li></ul>
    20. 20. Indication of the emergency caller's location <ul><li>NOTE 2: due to the support for Number portability or the inter-working with VoIP services determinating location information solely from the CLI may be impossible with some database arrangements, where the interrogation of the data is dependant on the network operator's database requested. </li></ul><ul><li>Recommendations 4 and 9 of the commission recommendation C(2003)2657 are quoted below: </li></ul><ul><li>4. &quot;For every emergency call made to the European emergency call number 112, public telephone network operators should, initiated by the network, forward (push) to public safety answering points the best information available as to the location of the caller, to the extent technically feasible&quot;. </li></ul><ul><li>9. &quot;For each emergency call for which the subscriber or user number has been identified, public telephone network operators should provide the capability to public safety answering points and emergency services of renewing the location information through a call back functionality (pulling)for the purpose of handling the emergency.&quot; </li></ul>
    21. 21. Current Geopriv drafts <ul><li>&quot;Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information&quot;, Henning Schulzrinne, 6-Oct-04. </li></ul><ul><li>&quot;A Document Format for Expressing Privacy Preferences for Location Information&quot;, Henning Schulzrinne, 6-Oct-04.) </li></ul><ul><li>&quot;A Presence-based GEOPRIV Location Object Format&quot;, Jon Peterson, 10-Sep-04.. </li></ul><ul><li>&quot;A Presence Architecture for the Distribution of GEOPRIV Location Objects&quot;, Jon Peterson, 9-Sep-04.. </li></ul><ul><li>&quot;A Document Format for Expressing Privacy Preferences&quot;, Henning Schulzrinne, 6-Oct-04. </li></ul><ul><li>&quot;Carrying Location Objects in RADIUS&quot;, Hannes Tschofenig, 6-Oct-04. (94758 bytes) </li></ul>
    22. 22. Coming IETF WG Sipping Emergency Drafts <ul><li>Emergency Services for Internet Telephony Systems <draft-schulzrinne-sipping-emergency-arch-02> </li></ul><ul><li>Requirements for Session Initiation Protocol (SIP)-based Emergency Calls <draft-schulzrinne-sipping-emergency-req-01> </li></ul>
    23. 23. Geographical Position Supply Implementation Sample INTERROGATING THE DEVICE ITSELF User device obtains its own location GPS GPoS GPoS GPS SLA 2 Location update 1. User updates its location from GPS 2. User sends a Location update to GPoS GPS 3. GPoS GPS may allow other GPoS users to lookup this users position, according to the SLA GPS GPS
    24. 24. Geographical Position Supply Implementation Sample INTERROGATING THE DEVICE ITSELF User device obtains its own location GPS GPoS Network Administration System (NAV) SLA 1 POSNAV (local GPoS) Surveillance / reporting Location request/response X <ul><li>A nomadic user visits a foreign network domain. There is no GPS available. </li></ul><ul><li>It sends an Location request to a local GPoS. E.g. POSNAV. </li></ul>GPS
    25. 25. Geographical Position Supply Implementation Sample Two possible scenarios User device obtains its own location GPoS GPoS GPS SLA 2 Network Administration System (NAV) SLA 1 POSNAV (local GPoS) Surveillance / reporting Location update Location request/response GPS
    26. 26. SIP emergency call User device obtains its own location GPS SIP Server GPoS INVITE (posdata as payload) Location request/response This may be needed to verify the posdata GPoS is used as demonstrated in the two scenarios ECC/PSAP ECC: Emergency Control Center GPS