Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/02—Services making use of location information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/40—Network security protocols
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/52—Network services specially adapted for the location of the user terminal
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L69/164—Adaptation or special uses of UDP protocol
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/02—Services making use of location information
  • H04W4/023—Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/02—Services making use of location information
  • H04W4/024—Guidance services
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

• Connection-oriented protocols establish a communication session between two network endpoints and then deliver a stream of data in the same order that it was sent from one endpoint to the other.
• Connection-oriented protocols are usually reliable, meaning that their ability to deliver data is more reliable. This reliability usually results from the protocol providing notifications to the sender regarding whether or not the data was delivered, and the sender resending lost information.
• Reliable protocols typically incur more overhead than unreliable protocols, and as a result, are slower and less scalable. Examples of reliable, connection-oriented protocols include Transmission Control Protocol (TCP), Hypertext Transfer Protocol (HTTP), and Session Initiation Protocol (SIP).
• TCP Transmission Control Protocol
• HTTP Hypertext Transfer Protocol
• SIP Session Initiation Protocol
• the present invention includes an architecture and a two-layer communication protocol that provides timely location updates via an unreliable protocol, and also provides a subscription mechanism that allows a location-aware application on a mobile device to act not only on its own real-time location, but also on the real-time location of other mobile devices in the system.
• FIGS. 3 is a flowchart illustrating the communication exchange between mobile devices and a server when location data for the mobile devices is obtained directly from the mobile device in accordance with an embodiment of the present invention.
• Occasional messages from the server to the mobile device may be used to confirm an open connection as well as pass specific data flow- control commands to the mobile device. These messages may be sent using a reliable or unreliable protocol. For an extremely light weight design, these messages may be initiated by the server via a protocol such as UDP if direct IP-addressing of the mobile device is supported on the network. Otherwise for networks that do not support server-initiated "push" IP communication, the mobile application may occasionally initiate and tear-down a TCP connection to receive a quick response from the server.
• the position of multiple mobile devices may be monitored visually via a map on a web page.
• An asynchronous method e.g. AJAX
• AJAX asynchronous method
• the architecture may be implemented using Java Micro Edition (Java ME) on GPS-enabled mobile devices, including mobile phones, in coordination with an application server (e.g. Glassfish).
• Java ME Java Micro Edition
• Many algorithms may run in the mobile phone application, including, for example, a Location-Aware State Machine (described in U.S. Patent Serial No. 12,245,072, which is incorporated herein by reference), a Critical Point method (described in U.S. Patent Serial No. 12,196,673, which is incorporated herein by reference), and an adaptive location data buffering method.
• an unreliable protocol e.g. UDP
• the server begins sending real-time location data to mobile device A via an unreliable protocol (e.g. UDP) as soon as it is able to retrieve the location data from its database (operation 125).
• Mobile Device A will receive the real-time location data and make application-level decisions based on the data.
• an unreliable protocol e.g. UDP
• mobile device A requests a subscription to mobile device B's location and includes its own contact information (e.g. current URI, network address, port number) in the data transmission via a reliable protocol (e.g. SIP, HTTP, TCP) (operation 325).
• a reliable protocol e.g. SIP, HTTP, TCP
• Mobile device B either grants or denies the request, and sends the decision information back to mobile device A via a reliable protocol (e.g. SIP, HTTP, TCP) (operation 330). If mobile device B grants the request, it begins sending its own real-time location data to mobile device A via an unreliable protocol (e.g. UDP) (operation 335). This subscription will continue until mobile device A unsubscribes via a reliable protocol (e.g.
• the mobile application may occasionally query the server using an reliable protocol (e.g. HTTP) to check the position of the transit vehicle and wait until the vehicle is within a certain distance threshold of the phone (e.g. 1500 meters) before requesting the subscription.
• the phone will then contact the transit vehicle and request a subscription to the transit vehicle's location and include its own contact information. If the transit vehicle accepts this subscription, it will start sending real-time location data via an unreliable protocol (e.g. UDP) that represents the position of the vehicle that the mobile application is subscribed to.
• UDP unreliable protocol
• All modules are translucent to the location-aware application, meaning that the application can also directly access underlying APIs (e.g. Location API) if necessary, to access functionality not controlled directly by the framework.
• underlying APIs e.g. Location API
• Device-side software can fuse data from multiple technologies (e.g. Wi-Fi, cellular signals, etc.) to estimate the current position of the device when location data from primary positioning systems are unavailable. While traditional dead-reckoning relies on accelerometers to estimate the device's movement, the Position Estimation module utilizes real-time and historical data to produce an intelligent estimate of the user's real-time position.
• technologies e.g. Wi-Fi, cellular signals, etc.
• the Position Estimation module utilizes real-time and historical data to produce an intelligent estimate of the user's real-time position.
• LAISYCTM also supports subscriptions to real-time locations of other mobile entities (e.g. vehicles). Session Management processes incoming UDP data containing real-time subscription location information and passes this information to the application.
• Path Prediction uses spatial representations of a user's historical trips along with their current position to predict the paths they may take in the immediate future. Because human travel behavior is highly repetitive in both space and time, it is highly likely that a user's next trip will overlap with one of their historical trips. A spatial database is used to perform a series of intersection queries between the user's realtime location/path and buffers surrounding their previously recorded paths.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Mobile Radio Communication Systems (AREA)
• Communication Control (AREA)
• Computer And Data Communications (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=42101181

Family Applications (1)

Country Status (4)

Families Citing this family (29)

Family Cites Families (13)

• 2009
  • 2009-10-07 EP EP09819811A patent/EP2345300A2/de not_active Withdrawn
  • 2009-10-07 CA CA2739914A patent/CA2739914A1/en not_active Abandoned
  • 2009-10-07 WO PCT/US2009/059825 patent/WO2010042609A2/en active Application Filing
• 2011
  • 2011-04-07 US US13/082,094 patent/US8725831B2/en not_active Expired - Fee Related

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events