US20050251326A1 - Web service for mobile device tracking - Google Patents
Web service for mobile device tracking Download PDFInfo
- Publication number
- US20050251326A1 US20050251326A1 US10/828,879 US82887904A US2005251326A1 US 20050251326 A1 US20050251326 A1 US 20050251326A1 US 82887904 A US82887904 A US 82887904A US 2005251326 A1 US2005251326 A1 US 2005251326A1
- Authority
- US
- United States
- Prior art keywords
- mobile device
- location
- location data
- client
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- 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/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/53—Network services using third party service providers
Definitions
- Tracking assets typically requires implementing conventional communication techniques, such as email and land-based or wireless calls, to directly or indirectly determine the location of an asset.
- an enterprise may have a need for tracking a business asset, such as an engineering team, during the course of employment.
- Upper management typically employs conventional means of tracking such as querying each member of the team via email. After coalescing this information, an enterprise is then in a position to make a management decision based on the availability of these assets.
- Current systems are limited in either their accuracy and/or the number of assets and recipients that they can economically service.
- a method and system for providing location data of a mobile device using a web service includes receiving location data associated with a mobile device, the mobile device operable to transmit a wireless signal including corresponding location data.
- a location request is received from a client using a web service. The location request comprising information identifying the mobile device and the client.
- a response to the location request is automatically communicated based on the location data associated with the mobile device.
- FIG. 1 illustrates one embodiment of a communications system including a server system for providing information based on location data;
- FIG. 3 is a flow diagram illustrating one embodiment of a method for providing information based on location data of a mobile device.
- FIG. 1 illustrates one embodiment of a communication system 100 that uses web services to provide information based on location data associated with a mobile device.
- Communication system 100 includes a mobile device system 110 , a location web services system 112 , a client system 114 , and a network 116 , such that systems 110 , 112 , and 114 are coupled via network 116 .
- location web services system 112 provides location data associated with mobile device system 110 to client system 114 .
- mobile device system 110 may transmit location data to location web services system 112 via network 116 .
- Location web services system 112 stores the location data and receives a request, such as an invocation or method call, from client system 114 for the location data. Based on the request and the location data, location web services system 112 transmits a response to client system 114 using network 116 .
- Network 116 is a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information that propagate through communication system 100 and may facilitate wireless and/or wireline communication between network devices.
- network 116 may facilitate wireless and wireline communication between mobile device system 110 and location web service system 112 .
- Network 116 offers a communicative interface between systems 110 , 112 , and 114 and may include one or more local area networks (LANs), wireless local area networks (WLANs), radio access networks (RANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of the global network known as the Internet, and/or any other communication system or systems at one or more locations that facilitates communications in a network environment.
- LANs local area networks
- WLANs wireless local area networks
- RANs radio access networks
- MANs metropolitan area networks
- WANs wide area networks
- Network 116 may implement a user datagram protocol (UDP)/internet protocol (UDP/IP) connection and use a transmission control protocol (TCP/IP) communication language protocol in particular embodiments of the present invention.
- Network 116 may communicate, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and other suitable information between network addresses.
- IP Internet Protocol
- ATM Asynchronous Transfer Mode
- Mobile device system 110 communicates with network 116 via a wireless link 117 .
- Mobile device system 110 may receive wireless requests from and transmit wireless responses to network 116 .
- Wireless link 117 may employ Transmission Control Protocol/Internet Protocol (TCP/IP) to convey signals between mobile device system 110 and network 116 .
- TCP/IP Transmission Control Protocol/Internet Protocol
- wireless link 117 may employ other suitable protocols for communicably coupling mobile device system 110 with network 116 .
- network 116 may include mobile device system 110 .
- Mobile device system 110 may comprise one or more mobile devices, wherein each mobile device is operable to communicate with network 116 .
- mobile device system 110 includes mobile device 130 .
- Mobile device 130 receives and decodes wireless signals to recover encoded data and request for information and transmits wireless signals to network 116 .
- Mobile device means any portable device operable to transmit a wireless signal.
- mobile device 130 may comprise a personal digital assistant (PDA), a cellular phone, a laptop computer, pager, automobile, or any other suitable processing device operable to receive and transmit wireless signals.
- PDA personal digital assistant
- mobile device 130 and “user of mobile device 130 ” may be used interchangeably, where appropriate, without departing from the scope of this disclosure.
- a user of mobile device 130 may be associate with an individual, a group, an enterprise, or any other suitable decision making body.
- mobile device 130 may comprise mobile device 130 .
- mobile device 130 includes a mobile interface 131 , a mobile processor 132 , and a mobile memory 134 .
- Mobile interface 131 is operable to receive input from and display information to a user of mobile device 130 .
- mobile interface 131 may include buttons, keys, a display, a graphical user interface, or any other suitable interface for receiving input from and/or displaying output to a user of mobile device 130 .
- mobile device 130 may comprises a wearable tag without a mobile interface 130 .
- Mobile processor 132 executes instructions and manipulates data to perform operations of mobile device 130 , such as a location awareness engine 136 and an agent 138 .
- FIG. 1 illustrates a single mobile processor 132 in mobile device 130 , multiple processors 132 may be used according to particular needs, and reference to processor 132 is meant to include multiple processors 132 where applicable.
- mobile device 130 includes location awareness engine 136 that provides location data associated with mobile device 130 based on any suitable method.
- Location data as used herein, means information that identifies a location of mobile device 130 .
- location data may include a longitude, a latitude, a street address, information identifying a base station, information identifying an access point, a radial distance from at least one base station, a radial distance from at least one access point, a signal strength, a signal-to-noise ratio, a time stamp, accuracy information, any combination of the foregoing, or any other suitable information that identifies or may be used to identify a location of mobile device 130 .
- location data includes a geographic location, a time stamp, and accuracy information. “Location data” and “processed location data,” i.e. information based on location data, may be used interchangeably, where appropriate.
- Location awareness engine 136 may use any suitable technique for determining location data of mobile device 130 .
- location awareness engine 136 may comprise a global positioning system (GPS) engine that performs a triangulation algorithm for determining the longitude and latitude of mobile device 130 based on at least three satellite broadcast signals. In this embodiment, if a fourth satellite broadcast signal is received and processed, then the altitude of mobile device 130 may additionally be determined.
- location awareness engine 136 may perform a triangulation algorithm based on signal strengths of cellular phone signals received by base stations.
- mobile device 130 may transmit a cellular phone signal encoding a request for signal strength information to the base stations receiving the request.
- Location awareness engine 136 may determine an approximate radial distance of each receiving base station based on the corresponding signal strength of the received signal. Based on at least three radial distances and knowing the location of the corresponding base stations, location awareness engine 136 may perform a triangulation algorithm to determine a location of mobile device 130 . In yet another embodiment, location awareness engine 136 may perform a triangulation algorithm based on signal strengths of wireless fidelity (Wi-Fi) or 802.11b signals received by access points or, alternatively, determine that mobile device 130 is within a certain radius of an access point (e.g., 100 meters). In this embodiment, mobile device 130 may transmit a radio frequency (RF) signal encoding a request for signal strength information to receiving access points.
- RF radio frequency
- Location awareness engine 136 may determine an approximate radial distance from the receiving access points based on the corresponding signal strengths of each received signal. Based on at least three radial distances and knowing the location of the corresponding access points, location awareness engine 136 may perform a triangulation algorithm to determine a location of mobile device 130 . It will be understood that location awareness engine 136 may use other suitable techniques to determine a location of mobile device 130 . For example, location awareness engine 136 may compare a physical model of a coverage area of a wireless network, such as a Wi-Fi network, and use signal variables, such as the signal-to-noise ratio and signal strength, to predict the likely location of mobile device 130 , which may not rely on triangulation.
- signal variables such as the signal-to-noise ratio and signal strength
- mobile device 130 may be a PDA transmitting an RF signal that is accurate within a 100 meter radius.
- location awareness engine 136 may rely on third generation (3G) mobile networks or other suitable technologies.
- 3G mobile networks include code-division multiple access (CDMA) 2000, wideband CDMA, and other versions based on the International Mobile Telecommunications (IMT)-2000, a standard developed by the International Telecommunication Union (ITU).
- Location awareness engine 136 may merely rely on the signal strength received by one base station or access point to determine a location of mobile device 130 within a radial distance.
- Location awareness engine 136 may include any hardware, software, firmware, or combination thereof operable to provide location data associated with mobile device 130 . It will be understood that location awareness engine 136 is illustrated as a single multi-task module, the features and functionality performed by this engine may be performed by multiple modules.
- Agent 138 comprises any engine, logic, or module operable to request location data from location awareness engine 136 and provide the location data to location web services system 112 .
- agent 138 may be based, at least in part, on software written in C++, Java, or any other suitable language.
- Agent 138 queries location awareness engine 136 for location data.
- mobile device may retrieve a mobile identifier from mobile memory 134 .
- Mobile identifier is any information that uniquely identifies mobile device 130 .
- Mobile identifier may additionally provide security information such that location awareness server system 112 may verify that responses identifying mobile device 130 were transmitted from mobile device 130 .
- agent 130 may encode a wireless signal with the location data and mobile identifier and transmit to the wireless signal network 116 via wireless link 117 .
- agent 138 may poll location awareness engine 136 based on polling information. Polling information may include a time interval for polling location awareness engine 136 , instructions as to what information is requested (e.g., time stamp, technique used to determine location, allowance of technique, etc.) or other suitable information that location web services system 112 may process.
- Mobile memory 134 may include any memory or data base module and may take the form of volatile or nonvolatile memory including, without limitation, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), removable media, or any other suitable local or remote memory or storage component.
- mobile memory 134 includes polling configuration file 140 and mobile device file 142 .
- Polling configuration file 140 comprises rules, instructions, algorithms, or any other directive used by mobile device 130 to poll a location awareness engine 136 for location data, as discussed in more detail below.
- polling configuration file 140 comprises different polling intervals at which agent 138 polls location awareness engine 136 to retrieve location data.
- the polling intervals may include time intervals associated with the location determination techniques employed, or any other information that location web services system 112 may use to process location data.
- File 140 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others.
- Mobile device file 142 comprises rules, instructions, algorithms, or any other directive used by mobile device 130 to identify and to secure wireless transmissions from mobile device 130 .
- mobile device file 142 comprises a mobile identifier.
- a mobile identifier identifies mobile device 130 , enabling location web services system 112 to associated location data with mobile device 130 .
- the mobile identifier may comprise an alphabetic, numeric, or alphanumeric code that is associated with mobile device 130 .
- Mobile device file 142 may additional comprise authentication features that enable location web services system 112 to verify that location data identified as associated with mobile device 130 was not sent from another device. Authentication features may prevent or lessen the possibility of inadvertent or illicit interference with communication system 100 .
- File 142 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others.
- Location web services system 112 is operable to receive, store, and process traffic from network 116 and transmit location responses 121 to client 118 . While web services system 112 is illustrated as disparate from network 116 , network 116 may include web services system 112 . Web services system 112 may comprise a plurality of network devices operable to process location data associated with mobile device 130 . In the illustrated embodiment, web services system 112 includes web services server 144 .
- Web services server 144 includes a server processor 146 and a server memory 148 .
- Server 144 comprises an electronic computing device operable to receive, transmit, process, and store data associated with system 100 .
- server 144 may comprise a general-purpose personal computer (PC), a Macintosh, a workstation, a UNIX-based computer, a server computer, or any other suitable device.
- server 144 comprises a web server.
- server 144 may comprise software and/or hardware in any combination suitable to process location data generated by and/or associated with mobile device 130 .
- web services server 144 may provide location data, provide processed location data, such as route, speed, or any other information generated by server 144 and based on location data, automatically communicating alerts in response to location data satisfying a criteria, or provide any other suitable web service based on location data.
- location data such as route, speed, or any other information generated by server 144 and based on location data
- automatically communicating alerts in response to location data satisfying a criteria or provide any other suitable web service based on location data.
- the term “automatically,” as used herein, generally means that the appropriate processing is substantially performed by at least a portion of an automated system.
- FIG. 1 only provides one example of computers that may be used with the disclosure.
- server 144 can be implemented using computers other than servers, as well as a server pool.
- the present disclosure contemplates computers other than general purpose computers as well as computers without conventional operating systems.
- the term computer is intended to include a personal computer, a workstation, network computer, or any other suitable processing device.
- Server 144 may be adapted to execute any operating system including UNIX, Windows, or any other suitable operating system.
- Server memory 148 may include any memory or database module and may take the form of volatile or non-volatile memory including, without limitation, magnetic media, optical media, RAM, ROM, removable media, or any other suitable local or remote memory or storage component.
- server memory 148 includes at least location record repository 156 , permission configuration file 162 , and monitoring configuration file 164 but may also include any other appropriate data.
- Location record repository 156 stores one or more mobile location records 158 .
- Location record repository 156 may receive mobile location records 158 through network 116 or from another process running on server 144 .
- Repository 156 may be any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and any other format operable to store one or more mobile location record 158 .
- each record 158 includes at least one data object 160 of any appropriate data type, including float, integer, currency, date, decimal, string, or any other numeric or non-numeric format.
- each record 158 includes a time identifier and location data.
- the time identifier identifies the time at which the location data was generated by mobile device 130 , such as, for example, a time stamp.
- Location data may include a location, a tolerance indicating the accuracy of the location, a technique identifier identifying the technique used by location awareness engine 136 to determine the location of mobile device 130 , information based on any combination of the foregoing, or other suitable information associated with mobile device 130 .
- Permission configuration file 162 comprises rules, instructions, algorithms, or any other directive used by server 144 to determine permissions granted to client 118 regarding location data associated with mobile device 130 .
- Permission configuration file 162 may be created, at least in part, by mobile device 130 , a third party, or any other suitable user of any computer in system 100 or loaded from a default table.
- File 162 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others.
- Monitoring configuration file 164 comprises rules, instructions, algorithms, or any other directive used by server 144 to monitor mobile device 130 .
- monitoring configuration file 164 comprises criteria that is compared to location data associated with mobile device 130 .
- criteria means any information that server processor 146 may compare to location data or processed location data.
- at least one criterion may include a determination of a location of mobile device 130 within a specified distance of a second mobile device.
- Another example of a criterion may include a determination of mobile device 130 arriving at a geographic location.
- Yet another example of a criterion may include a determination of mobile device 130 entering or exiting a geographic perimeter.
- File 164 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others.
- Server processor 146 executes instructions and manipulates data to perform operations of management server 144 .
- FIG. 1 illustrates a single processor 146 in server 144 , multiple processors 146 may be used according to particular needs, and reference to server processor 146 is meant to include multiple server processors 146 , where applicable.
- server processor 146 includes server interface 150 , web services 152 , and monitoring engine 154 .
- Server interface 150 may facilitate communication with mobile device system 110 and client system 114 via network 116 .
- server 144 may transmit location response 121 including location data to client 118 via network 116 .
- Interface 150 calibrates the reception of requests and the transmission of responses to these requests.
- interface 150 comprises logic encoded in software and/or hardware in a suitable combination and operable to communicate with network 116 via a link 125 . More specifically, interface 150 may comprise software supporting one or more communications protocols associated with link 125 and network 116 hardware operable to communicate physical signals.
- Web services 152 is operable to receive, decode, and respond to client request 119 .
- a “web service” is a web-based application that interacts with other web applications via network 116 using open standards, i.e., publicly available standards.
- SOAP Simple Object Access Protocol
- XML are current communication standards used in most web services.
- SOAP is a messaging protocol based on XML for accessing and promoting services on the World Wide Web.
- SOAP messages may be independent of operating systems used by system 100 and may be transmitted using a variety of Internet protocols, including Simple Mail Transfer Protocol (SMTP), Multipurpose Internet Mail Extensions (MIME), Hyper Text Transfer Protocol (HTTP), or any other suitable protocol.
- SMTP Simple Mail Transfer Protocol
- MIME Multipurpose Internet Mail Extensions
- HTTP Hyper Text Transfer Protocol
- web services employing SOAP do not provide web pages over network 116 but instead share business logic, data, and processes through a programmatic interface across network 116 .
- web services 152 receives and decodes a client request 119 for location data associated mobile device 130 .
- Web services 152 may extract information, including a client identifier, from client request 119 , identifying client 118 and mobile device 130 .
- web services 152 compares the client identifier to permission configuration file 162 to determine if client 118 has any permissions with regard to location data associated with the identified mobile device 130 . Based upon these permissions, web services 152 retrieves at least a portion of record 158 associated with the mobile device 130 .
- the location data comprises a longitude and a latitude with a statement of accuracy.
- the location data includes a route that mobile device 130 traveled between a first and a second location.
- the location data comprises a speed at which mobile device traveled over a period of time.
- Web services 152 transmits a location response 121 to client request 119 including the location data or processed location data.
- the location data or processed location data may be in any electronic format such as, for example, an XML document, flat files, CSV files, SQL tables or any other suitable format.
- Monitoring engine 154 monitors location data associated with mobile device 130 .
- monitoring engine 154 may be operable to monitor location data associated with mobile device 130 , compare the location data to criteria, and automatically transmit an alert in response to the location data satisfying the criteria.
- automatically means that the appropriate processing is performed by an automated system.
- server 144 may perform additional processes prior to transmitting the response, such as, for example, determining permissions associated with the requestor.
- Monitoring engine 154 may receive a request from monitoring engine 154 for monitoring mobile device 130 based on criteria stored in monitoring configuration file 164 . For example, monitoring engine 154 may automatically communicate an alert when mobile device 130 is within a specified distance of a location. Another example includes monitoring engine 154 may automatically communicate an alert when mobile device 130 leaves or exits a geographic parameter.
- Client system 114 is operable to request location data associated with mobile device 130 or information based on the location data from location web services system 112 . While client system 114 is illustrated as disparate from network 116 , network 116 may include client system 114 . Client system 114 may comprise a plurality of network devices operable to request location data associated with mobile device 130 via network 116 . For example, client system 114 may comprise a plurality of clients. In the illustrated embodiment, client system 116 includes a client 118 .
- Client 118 may include input devices, output devices, mass storage media, processors, memory, interfaces, communication ports, or other appropriate components for communicating client requests 119 to location web services system 112 and receiving responses via network 116 , such as location responses 121 .
- Client request 119 may include a location request and information identifying client 118 and mobile device 130 .
- the location request may include a request for location data, processed location data, such as speed, route, or other suitable information based on location data, a monitoring request, such as a request for alerts based on criteria, or other suitable information associated with mobile device 130 .
- a monitoring request is a request to monitor location data as compared to at least one criterion.
- Criteria means any information that location web services system 112 may compare to location data or processed location data.
- Location responses 121 may include location data, processed location data, alerts, or any other suitable information based on location data associated with mobile device 130 .
- client 118 includes graphical user interface (GUI) 120 , client processor 122 , and client memory 124 . It will be understood that there may be any number of clients 118 coupled to location web services system 112 .
- client 118 is intended to encompass a personal computer, workstation, network computer, kiosk, wireless data port, lap top computer, cellular phone, PDA, one or more processors within these or other devices, or any other suitable processing device.
- client 118 may include a third party application running on a processing device.
- client 118 and “user of client 118 ” may be used interchangeably without departing from the scope of this disclosure.
- client 118 may comprise a computer that includes an input device, such as a keypad, touch screen, mouse, or other device that can accept information and an output device that conveys information associated with the operation of system 100 , including digital data, visual information, or any other suitable information.
- Both the input device and output device may include fixed or removable storage media such as a magnetic computer disk, CD-ROM, or other suitable media to both receive input from and provide output to users of client 118 through a portion of a data display, namely GUI 120 .
- GUI 120 comprises a graphical user interface operable to allow the user of client 118 to interface with system 100 to receive data from web services system 112 .
- GUI 120 provides the user of client 118 with an efficient and user-friendly presentation of data provided by system 100 , such as charts and tables.
- GUI 120 may comprise a plurality of displays having interactive fields, pull-down lists, and buttons operated by the user.
- GUI 120 presents multiple tables according to requests by client 118 .
- the term graphical user interface may be used in the singular or in the plural to describe one or more graphical user interfaces in each of the displays of a graphical user interface.
- GUI 118 contemplates any graphical user interface, such as a generic web browser, that processes information in system 100 and efficiently presents the information to the user.
- Client memory 124 may include any memory or data base module and may take the form of volatile or nonvolatile memory including, without limitation, magnetic media, optical media, RAM, ROM, removable media, or any other suitable local or remote memory or storage component.
- mobile memory 134 includes client configuration file 128 .
- Client configuration file 128 comprises rules, instructions, algorithms, or any other directive used by client 118 to request services based on location data from web services system 112 .
- file 128 may include a client identifier that identifies client 118 and enables web services system 112 to associated client request 119 with client 118 .
- Client configuration file 128 may additional comprise authentication features that enable location web services system 112 to verify that client request 119 associated with client 118 was not sent from another device. Authentication features may prevent or lessen the possibility of inadvertent or illicit interference with communication system 100 .
- File 128 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others.
- Client processor 122 executes instructions and manipulates data to perform operations of client 118 .
- FIG. 1 illustrates a single processor 122 in client 118 , multiple processors 122 may be used according to particular needs, and reference to processor 122 is meant to include multiple processors 122 , where applicable.
- processor 122 includes network interface 126 .
- Network interface 126 may facilitate communication with network 116 .
- client 118 may generate a request to web services system 112 via network 116 for information based on location data associated with mobile device 130 .
- Interface 126 calibrates the transmission of these requests and the reception of responses to these requests.
- interface 126 comprising the logic encoded in software and/or hardware in a suitable combination and operable to communicate with network 116 via link 123 . More specifically, interface 126 may comprise software supporting one or more communication protocols associated with link 123 and network 116 hardware operable to communicate physical signals.
- server 144 receives locations data associated with mobile device 130 and stores the information in server memory 148 .
- Server 144 may receive a client request 119 from client 118 , including a location request and information that identifies the client 118 and mobile device 130 .
- Web services 152 compares the identified client 118 to permission configuration file 162 to determine what permissions client 118 may have with regard to location data associated with mobile device 130 . If the location request includes a monitoring request, Web services 152 forwards the monitoring request to monitoring engine 154 .
- Monitoring engine 154 may store criteria in monitoring configuration file 164 and periodically compare location data associated with mobile device 130 to the criteria. In response to any criterion being satisfied, monitoring engine 154 automatically transmits an alert to client 118 .
- web services 152 extracts the corresponding data from record 158 and generates a response to the location request. Web services 152 automatically transmits the location response 121 to client 118 . In one embodiment, web services 152 transmits an SOAP messaging based on XML comprising location data.
- FIG. 2A illustrates one embodiment of implementing mobile device 130 of system 100 .
- mobile device 130 includes a mobile processor 132 and a mobile memory 134 .
- mobile processor 132 includes location awareness engine 136 , mobile management engine 166 , and permission interface 168 .
- Location awareness engine 136 provides location data associated with mobile device 130 based on any suitable method.
- Mobile management engine 166 is operable to receive and decode server requests from server 144 and transmit responses to these requests. Additionally, mobile management engine 166 may query location awareness engine 136 in order to provide location data to server 144 .
- Permission interface 168 is operable to determine what permissions client 118 has with regard to location data associated with mobile device 130 .
- permission interface 168 is configured by an administrator remotely located from mobile device 130 in which case the administrator, not mobile device 130 , determines permissions of clients. It will be understood that these permissions may be In one embodiment, permission interface 168 receives a client identifier from mobile management engine 166 , which may be extracted from the server request.
- Mobile memory 134 includes client permission file 170 .
- Client permission file 170 comprises rules, instructions, algorithms, or any other directive delineating permissions granted to client 118 regarding location data associated with mobile device 130 .
- File 170 may be any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others.
- FIG. 2B illustrates one implementation of server 144 of system 100 .
- Server 144 includes server processor 146 and server memory 148 .
- Server memory 148 includes a polling configuration file 140 , a monitoring configuration file 164 , a permission configuration file 162 , and a location record repository 156 .
- location record repository 156 includes a plurality of records 158 , and each record 158 includes at least one data object 160 .
- Monitoring configuration file 164 may include rules, instructions, and algorithms, or any other directives used by server 144 to monitor mobile device 130 , which may include criteria as discussed above.
- Server processor 146 includes server agent 172 , web services 152 , and monitoring engine 154 .
- Server agent 172 is operable to poll location awareness engine 136 of mobile device 130 based on polling configuration file 140 .
- web services 152 is operable to receive and process client requests 119 and transmit location responses 121 based on location data associated with mobile device 130 .
- Monitoring engine 154 may monitor location data of mobile device 130 and compare location data of mobile device 130 to criteria stored in monitoring configuration file 164 . In response to location data satisfying a criterion, monitoring engine 154 may automatically communicate a response to client 118 .
- server agent 172 may transmit a server request for location data associated with mobile device 130 via network 116 .
- Mobile management engine 166 may receive and decode the server requests and forward a request for location data to location awareness engine 136 . Additionally, mobile management engine 166 may forward the server request to permission interface 168 . Permission interface 168 may extract permissions associated with the location data of mobile device 130 from client permission file 170 and forward them to mobile management engine 166 . Additionally, location awareness engine 136 may forward location data to mobile management engine 166 .
- Mobile management engine 166 receives location data and permissions and encodes a wireless signal to be transmitted over wireless link 117 to server 144 .
- Server agent 172 receives and decodes mobile device's 130 response and stores location data in location record repository 156 and permission information in permission configuration file 162 .
- Web services 152 receives and decodes client request 119 from client 118 , including requests for location data and monitoring requests. Monitoring requests are forwarded to monitoring engine 154 , which extracts criteria from the monitoring request. Each criterion is stored in monitoring configuration file 164 . Monitoring engine 154 monitors location data received from mobile device 130 , and in response to the location data satisfying at least one criterion, an alert is automatically communicating to client 118 .
- web services 152 extracts the relevant portion of the record 158 corresponding to the requested location data. Web services 152 may process the extracted portion of record 158 and encode a signal with location response 121 for transmission to client 118 .
- FIG. 3 illustrates a flowchart of an exemplary method 300 for monitoring location data associated with a mobile device 130 .
- Method 300 is described in respect to system 100 . However, any other suitable system may use method 300 to provide location data without departing from the scope of this disclosure.
- method 300 describes web services 152 receiving requests for location data from client 118 , processing the requests, and transmitting a response based on the location data of mobile device 130 .
- Method 300 begins at step 302 where web services 152 receives location data associated with mobile device 130 .
- Location data may be stored remotely or in memory. Additionally, web services 152 may poll, receive, or otherwise collect location data associated with mobile device 130 .
- web services 152 receives a client request 119 from client 118 .
- Client request 119 may include a request for location data or a request for monitoring a particular criterion.
- decisional step 306 if web services 152 does not identify the mobile device indicated in the client request 119 then, at step 308 , an error message is transmitted to client 118 indicating that mobile device 130 is not identified, at which point processing ends.
- web services 152 determines what permissions are available to client 118 regarding access to location data associated with mobile device 130 . In one embodiment, web services 152 compares the identified client 118 to permission configuration file 162 to determine what permissions are available to client 118 . If permission configuration file 162 does not grant client 118 permission to location data, web services 152 may transmit a permission request to mobile device 130 requesting permission for client 118 to have access to location data stored in location record repository 158 at step 312 .
- web services 152 transmits a denial of access to location data message to client 118 at step 316 , at which point processing ends. If permission is granted to client 118 via a response from mobile device 130 or from permission configuration file 162 , then at step 318 , web services 152 determines whether client request 119 includes a location request. If client request 119 includes a request for location data, then web services 152 transmits the corresponding location data to client 118 , as discussed in detail above, at step 320 . Method 300 proceeds to decisional step 322 . If monitoring request is not included in client request 119 , then method 300 ends.
- web services 152 extracts criteria from the request and stores the criteria in monitoring configuration file 164 at step 324 .
- decisional step 326 if at least one of the criterion is satisfied, then, at step 328 , an alert is automatically transmitted to client 118 . It will be understood that the criteria may be monitored by a single or separate processes.
- web services 152 receive additional location data from mobile device 130 at step 330 .
- web services 152 stores the additional location data in location record repository 156 .
- step 332 if at least one of the criterion is not satisfied, then method 300 returns to step 330 . If at least one of the criterion is satisfied, then method 300 proceeds to step 328 , at which point web services 152 transmits an alert to client 118 . At decisional step 336 , if all criteria are satisfied, method 300 ends. If at least one criterion is not satisfied, then method 300 returns to step 330 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Radar Systems Or Details Thereof (AREA)
Abstract
Description
- This disclosure relates generally to the field of wireless devices, and more particularly to a web service for mobile device tracking.
- Tracking assets, including individuals, typically requires implementing conventional communication techniques, such as email and land-based or wireless calls, to directly or indirectly determine the location of an asset. For example, an enterprise may have a need for tracking a business asset, such as an engineering team, during the course of employment. Upper management typically employs conventional means of tracking such as querying each member of the team via email. After coalescing this information, an enterprise is then in a position to make a management decision based on the availability of these assets. Current systems are limited in either their accuracy and/or the number of assets and recipients that they can economically service.
- A method and system for providing location data of a mobile device using a web service is provided. In one embodiment, a method for providing location data of a mobile device using a web service includes receiving location data associated with a mobile device, the mobile device operable to transmit a wireless signal including corresponding location data. A location request is received from a client using a web service. The location request comprising information identifying the mobile device and the client. A response to the location request is automatically communicated based on the location data associated with the mobile device.
-
FIG. 1 illustrates one embodiment of a communications system including a server system for providing information based on location data; -
FIG. 2A -B illustrates one embodiment of implementing web services server illustrated inFIG. 1 ; and -
FIG. 3 is a flow diagram illustrating one embodiment of a method for providing information based on location data of a mobile device. -
FIG. 1 illustrates one embodiment of acommunication system 100 that uses web services to provide information based on location data associated with a mobile device.Communication system 100 includes amobile device system 110, a locationweb services system 112, aclient system 114, and anetwork 116, such thatsystems network 116. In general, locationweb services system 112 provides location data associated withmobile device system 110 toclient system 114. For example,mobile device system 110 may transmit location data to locationweb services system 112 vianetwork 116. Locationweb services system 112 stores the location data and receives a request, such as an invocation or method call, fromclient system 114 for the location data. Based on the request and the location data, locationweb services system 112 transmits a response toclient system 114 usingnetwork 116. -
Network 116 is a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information that propagate throughcommunication system 100 and may facilitate wireless and/or wireline communication between network devices. For example,network 116 may facilitate wireless and wireline communication betweenmobile device system 110 and locationweb service system 112. Network 116 offers a communicative interface betweensystems Network 116 may communicate, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and other suitable information between network addresses. -
Mobile device system 110 communicates withnetwork 116 via awireless link 117.Mobile device system 110 may receive wireless requests from and transmit wireless responses tonetwork 116.Wireless link 117 may employ Transmission Control Protocol/Internet Protocol (TCP/IP) to convey signals betweenmobile device system 110 andnetwork 116. It will be understood thatwireless link 117 may employ other suitable protocols for communicably couplingmobile device system 110 withnetwork 116. Whilemobile device system 110 is illustrated as disparate fromnetwork 116,network 116 may includemobile device system 110.Mobile device system 110 may comprise one or more mobile devices, wherein each mobile device is operable to communicate withnetwork 116. In the illustrated embodiment,mobile device system 110 includesmobile device 130. -
Mobile device 130 receives and decodes wireless signals to recover encoded data and request for information and transmits wireless signals tonetwork 116. Mobile device, as used herein, means any portable device operable to transmit a wireless signal. It will be understood thatmobile device 130 may comprise a personal digital assistant (PDA), a cellular phone, a laptop computer, pager, automobile, or any other suitable processing device operable to receive and transmit wireless signals. Moreover, “mobile device 130” and “user ofmobile device 130” may be used interchangeably, where appropriate, without departing from the scope of this disclosure. A user ofmobile device 130 may be associate with an individual, a group, an enterprise, or any other suitable decision making body. Additionally, an asset, such an individual, a device, or any other physical object that is capable of being transported, may comprisemobile device 130. Referring to the illustrated embodiment,mobile device 130 includes amobile interface 131, amobile processor 132, and amobile memory 134.Mobile interface 131 is operable to receive input from and display information to a user ofmobile device 130. For example,mobile interface 131 may include buttons, keys, a display, a graphical user interface, or any other suitable interface for receiving input from and/or displaying output to a user ofmobile device 130. Alternatively,mobile device 130 may comprises a wearable tag without amobile interface 130. -
Mobile processor 132 executes instructions and manipulates data to perform operations ofmobile device 130, such as alocation awareness engine 136 and anagent 138. AlthoughFIG. 1 illustrates a singlemobile processor 132 inmobile device 130,multiple processors 132 may be used according to particular needs, and reference toprocessor 132 is meant to includemultiple processors 132 where applicable. In the illustrated embodiment,mobile device 130 includeslocation awareness engine 136 that provides location data associated withmobile device 130 based on any suitable method. Location data, as used herein, means information that identifies a location ofmobile device 130. For example, location data may include a longitude, a latitude, a street address, information identifying a base station, information identifying an access point, a radial distance from at least one base station, a radial distance from at least one access point, a signal strength, a signal-to-noise ratio, a time stamp, accuracy information, any combination of the foregoing, or any other suitable information that identifies or may be used to identify a location ofmobile device 130. In one embodiment, location data includes a geographic location, a time stamp, and accuracy information. “Location data” and “processed location data,” i.e. information based on location data, may be used interchangeably, where appropriate. -
Location awareness engine 136 may use any suitable technique for determining location data ofmobile device 130. For example,location awareness engine 136 may comprise a global positioning system (GPS) engine that performs a triangulation algorithm for determining the longitude and latitude ofmobile device 130 based on at least three satellite broadcast signals. In this embodiment, if a fourth satellite broadcast signal is received and processed, then the altitude ofmobile device 130 may additionally be determined. In another embodiment,location awareness engine 136 may perform a triangulation algorithm based on signal strengths of cellular phone signals received by base stations. In this embodiment,mobile device 130 may transmit a cellular phone signal encoding a request for signal strength information to the base stations receiving the request.Location awareness engine 136 may determine an approximate radial distance of each receiving base station based on the corresponding signal strength of the received signal. Based on at least three radial distances and knowing the location of the corresponding base stations,location awareness engine 136 may perform a triangulation algorithm to determine a location ofmobile device 130. In yet another embodiment,location awareness engine 136 may perform a triangulation algorithm based on signal strengths of wireless fidelity (Wi-Fi) or 802.11b signals received by access points or, alternatively, determine thatmobile device 130 is within a certain radius of an access point (e.g., 100 meters). In this embodiment,mobile device 130 may transmit a radio frequency (RF) signal encoding a request for signal strength information to receiving access points.Location awareness engine 136 may determine an approximate radial distance from the receiving access points based on the corresponding signal strengths of each received signal. Based on at least three radial distances and knowing the location of the corresponding access points,location awareness engine 136 may perform a triangulation algorithm to determine a location ofmobile device 130. It will be understood thatlocation awareness engine 136 may use other suitable techniques to determine a location ofmobile device 130. For example,location awareness engine 136 may compare a physical model of a coverage area of a wireless network, such as a Wi-Fi network, and use signal variables, such as the signal-to-noise ratio and signal strength, to predict the likely location ofmobile device 130, which may not rely on triangulation. In one embodiment,mobile device 130 may be a PDA transmitting an RF signal that is accurate within a 100 meter radius. Additionally,location awareness engine 136 may rely on third generation (3G) mobile networks or other suitable technologies. 3G mobile networks include code-division multiple access (CDMA) 2000, wideband CDMA, and other versions based on the International Mobile Telecommunications (IMT)-2000, a standard developed by the International Telecommunication Union (ITU).Location awareness engine 136 may merely rely on the signal strength received by one base station or access point to determine a location ofmobile device 130 within a radial distance.Location awareness engine 136 may include any hardware, software, firmware, or combination thereof operable to provide location data associated withmobile device 130. It will be understood thatlocation awareness engine 136 is illustrated as a single multi-task module, the features and functionality performed by this engine may be performed by multiple modules. -
Agent 138 comprises any engine, logic, or module operable to request location data fromlocation awareness engine 136 and provide the location data to locationweb services system 112. For example,agent 138 may be based, at least in part, on software written in C++, Java, or any other suitable language.Agent 138 querieslocation awareness engine 136 for location data. Prior to transmitting this data, mobile device may retrieve a mobile identifier frommobile memory 134. Mobile identifier, as used herein, is any information that uniquely identifiesmobile device 130. Mobile identifier may additionally provide security information such that locationawareness server system 112 may verify that responses identifyingmobile device 130 were transmitted frommobile device 130. After retrieving the mobile identifier,agent 130 may encode a wireless signal with the location data and mobile identifier and transmit to thewireless signal network 116 viawireless link 117. Alternatively,agent 138 may polllocation awareness engine 136 based on polling information. Polling information may include a time interval for pollinglocation awareness engine 136, instructions as to what information is requested (e.g., time stamp, technique used to determine location, allowance of technique, etc.) or other suitable information that locationweb services system 112 may process. -
Mobile memory 134 may include any memory or data base module and may take the form of volatile or nonvolatile memory including, without limitation, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), removable media, or any other suitable local or remote memory or storage component. In the illustrated embodiment,mobile memory 134 includespolling configuration file 140 andmobile device file 142. -
Polling configuration file 140 comprises rules, instructions, algorithms, or any other directive used bymobile device 130 to poll alocation awareness engine 136 for location data, as discussed in more detail below. In one embodiment,polling configuration file 140 comprises different polling intervals at whichagent 138 pollslocation awareness engine 136 to retrieve location data. The polling intervals may include time intervals associated with the location determination techniques employed, or any other information that locationweb services system 112 may use to process location data.File 140 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others. -
Mobile device file 142 comprises rules, instructions, algorithms, or any other directive used bymobile device 130 to identify and to secure wireless transmissions frommobile device 130. In one embodiment,mobile device file 142 comprises a mobile identifier. As discussed above, a mobile identifier identifiesmobile device 130, enabling locationweb services system 112 to associated location data withmobile device 130. In one embodiment, the mobile identifier may comprise an alphabetic, numeric, or alphanumeric code that is associated withmobile device 130.Mobile device file 142 may additional comprise authentication features that enable locationweb services system 112 to verify that location data identified as associated withmobile device 130 was not sent from another device. Authentication features may prevent or lessen the possibility of inadvertent or illicit interference withcommunication system 100.File 142 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others. - Location
web services system 112 is operable to receive, store, and process traffic fromnetwork 116 and transmitlocation responses 121 toclient 118. Whileweb services system 112 is illustrated as disparate fromnetwork 116,network 116 may includeweb services system 112.Web services system 112 may comprise a plurality of network devices operable to process location data associated withmobile device 130. In the illustrated embodiment,web services system 112 includesweb services server 144. -
Web services server 144 includes aserver processor 146 and aserver memory 148.Server 144 comprises an electronic computing device operable to receive, transmit, process, and store data associated withsystem 100. For example,server 144 may comprise a general-purpose personal computer (PC), a Macintosh, a workstation, a UNIX-based computer, a server computer, or any other suitable device. In the illustrated embodiment,server 144 comprises a web server. In short,server 144 may comprise software and/or hardware in any combination suitable to process location data generated by and/or associated withmobile device 130. For example,web services server 144 may provide location data, provide processed location data, such as route, speed, or any other information generated byserver 144 and based on location data, automatically communicating alerts in response to location data satisfying a criteria, or provide any other suitable web service based on location data. The term “automatically,” as used herein, generally means that the appropriate processing is substantially performed by at least a portion of an automated system. -
FIG. 1 only provides one example of computers that may be used with the disclosure. For example, althoughFIG. 1 provides one example ofserver 144 that may be used with the disclosure,server 144 can be implemented using computers other than servers, as well as a server pool. The present disclosure contemplates computers other than general purpose computers as well as computers without conventional operating systems. As used in this document, the term computer is intended to include a personal computer, a workstation, network computer, or any other suitable processing device.Server 144 may be adapted to execute any operating system including UNIX, Windows, or any other suitable operating system. -
Server memory 148 may include any memory or database module and may take the form of volatile or non-volatile memory including, without limitation, magnetic media, optical media, RAM, ROM, removable media, or any other suitable local or remote memory or storage component. In this embodiment,server memory 148 includes at leastlocation record repository 156,permission configuration file 162, andmonitoring configuration file 164 but may also include any other appropriate data.Location record repository 156 stores one or more mobile location records 158.Location record repository 156 may receivemobile location records 158 throughnetwork 116 or from another process running onserver 144.Repository 156 may be any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and any other format operable to store one or moremobile location record 158. - Generally, each record 158 includes at least one
data object 160 of any appropriate data type, including float, integer, currency, date, decimal, string, or any other numeric or non-numeric format. In one embodiment, each record 158 includes a time identifier and location data. The time identifier identifies the time at which the location data was generated bymobile device 130, such as, for example, a time stamp. Location data may include a location, a tolerance indicating the accuracy of the location, a technique identifier identifying the technique used bylocation awareness engine 136 to determine the location ofmobile device 130, information based on any combination of the foregoing, or other suitable information associated withmobile device 130. -
Permission configuration file 162 comprises rules, instructions, algorithms, or any other directive used byserver 144 to determine permissions granted toclient 118 regarding location data associated withmobile device 130.Permission configuration file 162 may be created, at least in part, bymobile device 130, a third party, or any other suitable user of any computer insystem 100 or loaded from a default table.File 162 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others. -
Monitoring configuration file 164 comprises rules, instructions, algorithms, or any other directive used byserver 144 to monitormobile device 130. In one embodiment,monitoring configuration file 164 comprises criteria that is compared to location data associated withmobile device 130. As discussed above, criteria means any information thatserver processor 146 may compare to location data or processed location data. For example, at least one criterion may include a determination of a location ofmobile device 130 within a specified distance of a second mobile device. Another example of a criterion may include a determination ofmobile device 130 arriving at a geographic location. Yet another example of a criterion may include a determination ofmobile device 130 entering or exiting a geographic perimeter.File 164 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others. -
Server processor 146 executes instructions and manipulates data to perform operations ofmanagement server 144. AlthoughFIG. 1 illustrates asingle processor 146 inserver 144,multiple processors 146 may be used according to particular needs, and reference toserver processor 146 is meant to includemultiple server processors 146, where applicable. In the illustrated embodiment,server processor 146 includesserver interface 150,web services 152, andmonitoring engine 154.Server interface 150 may facilitate communication withmobile device system 110 andclient system 114 vianetwork 116. In certain embodiments,server 144 may transmitlocation response 121 including location data toclient 118 vianetwork 116.Interface 150 calibrates the reception of requests and the transmission of responses to these requests. Generally,interface 150 comprises logic encoded in software and/or hardware in a suitable combination and operable to communicate withnetwork 116 via alink 125. More specifically,interface 150 may comprise software supporting one or more communications protocols associated withlink 125 andnetwork 116 hardware operable to communicate physical signals. -
Web services 152 is operable to receive, decode, and respond toclient request 119. In general, a “web service” is a web-based application that interacts with other web applications vianetwork 116 using open standards, i.e., publicly available standards. For example, Simple Object Access Protocol (SOAP) and XML are current communication standards used in most web services. SOAP is a messaging protocol based on XML for accessing and promoting services on the World Wide Web. SOAP messages may be independent of operating systems used bysystem 100 and may be transmitted using a variety of Internet protocols, including Simple Mail Transfer Protocol (SMTP), Multipurpose Internet Mail Extensions (MIME), Hyper Text Transfer Protocol (HTTP), or any other suitable protocol. Though, web services employing SOAP do not provide web pages overnetwork 116 but instead share business logic, data, and processes through a programmatic interface acrossnetwork 116. Regarding the illustrated embodiment,web services 152 receives and decodes aclient request 119 for location data associatedmobile device 130.Web services 152 may extract information, including a client identifier, fromclient request 119, identifyingclient 118 andmobile device 130. In one embodiment,web services 152 compares the client identifier topermission configuration file 162 to determine ifclient 118 has any permissions with regard to location data associated with the identifiedmobile device 130. Based upon these permissions,web services 152 retrieves at least a portion ofrecord 158 associated with themobile device 130. After extracting the relevant data objects 160,web services 152 processes the extracted data objects 160 to generate thelocation response 121. In one embodiment, the location data comprises a longitude and a latitude with a statement of accuracy. In another embodiment, the location data includes a route thatmobile device 130 traveled between a first and a second location. In yet another embodiment, the location data comprises a speed at which mobile device traveled over a period of time.Web services 152 transmits alocation response 121 toclient request 119 including the location data or processed location data. The location data or processed location data may be in any electronic format such as, for example, an XML document, flat files, CSV files, SQL tables or any other suitable format. -
Monitoring engine 154 monitors location data associated withmobile device 130. In one embodiment,monitoring engine 154 may be operable to monitor location data associated withmobile device 130, compare the location data to criteria, and automatically transmit an alert in response to the location data satisfying the criteria. As used herein, automatically means that the appropriate processing is performed by an automated system. Regarding automatically transmitting a response,server 144 may perform additional processes prior to transmitting the response, such as, for example, determining permissions associated with the requestor.Monitoring engine 154 may receive a request frommonitoring engine 154 for monitoringmobile device 130 based on criteria stored inmonitoring configuration file 164. For example,monitoring engine 154 may automatically communicate an alert whenmobile device 130 is within a specified distance of a location. Another example includesmonitoring engine 154 may automatically communicate an alert whenmobile device 130 leaves or exits a geographic parameter. -
Client system 114 is operable to request location data associated withmobile device 130 or information based on the location data from locationweb services system 112. Whileclient system 114 is illustrated as disparate fromnetwork 116,network 116 may includeclient system 114.Client system 114 may comprise a plurality of network devices operable to request location data associated withmobile device 130 vianetwork 116. For example,client system 114 may comprise a plurality of clients. In the illustrated embodiment,client system 116 includes aclient 118. -
Client 118 may include input devices, output devices, mass storage media, processors, memory, interfaces, communication ports, or other appropriate components for communicatingclient requests 119 to locationweb services system 112 and receiving responses vianetwork 116, such aslocation responses 121.Client request 119 may include a location request andinformation identifying client 118 andmobile device 130. The location request may include a request for location data, processed location data, such as speed, route, or other suitable information based on location data, a monitoring request, such as a request for alerts based on criteria, or other suitable information associated withmobile device 130. As used herein, a monitoring request is a request to monitor location data as compared to at least one criterion. Criteria, as used herein, means any information that locationweb services system 112 may compare to location data or processed location data.Location responses 121 may include location data, processed location data, alerts, or any other suitable information based on location data associated withmobile device 130. In the illustrated embodiment,client 118 includes graphical user interface (GUI) 120,client processor 122, andclient memory 124. It will be understood that there may be any number ofclients 118 coupled to locationweb services system 112. As used in this document,client 118 is intended to encompass a personal computer, workstation, network computer, kiosk, wireless data port, lap top computer, cellular phone, PDA, one or more processors within these or other devices, or any other suitable processing device. Alternatively,client 118 may include a third party application running on a processing device. Moreover, “client 118” and “user ofclient 118” may be used interchangeably without departing from the scope of this disclosure. For example,client 118 may comprise a computer that includes an input device, such as a keypad, touch screen, mouse, or other device that can accept information and an output device that conveys information associated with the operation ofsystem 100, including digital data, visual information, or any other suitable information. Both the input device and output device may include fixed or removable storage media such as a magnetic computer disk, CD-ROM, or other suitable media to both receive input from and provide output to users ofclient 118 through a portion of a data display, namelyGUI 120. -
GUI 120 comprises a graphical user interface operable to allow the user ofclient 118 to interface withsystem 100 to receive data fromweb services system 112. Generally,GUI 120 provides the user ofclient 118 with an efficient and user-friendly presentation of data provided bysystem 100, such as charts and tables.GUI 120 may comprise a plurality of displays having interactive fields, pull-down lists, and buttons operated by the user. In one embodiment,GUI 120 presents multiple tables according to requests byclient 118. It should be understood that the term graphical user interface may be used in the singular or in the plural to describe one or more graphical user interfaces in each of the displays of a graphical user interface. Further,GUI 118 contemplates any graphical user interface, such as a generic web browser, that processes information insystem 100 and efficiently presents the information to the user. -
Client memory 124 may include any memory or data base module and may take the form of volatile or nonvolatile memory including, without limitation, magnetic media, optical media, RAM, ROM, removable media, or any other suitable local or remote memory or storage component. In the illustrated embodiment,mobile memory 134 includesclient configuration file 128.Client configuration file 128 comprises rules, instructions, algorithms, or any other directive used byclient 118 to request services based on location data fromweb services system 112. Additionally, file 128 may include a client identifier that identifiesclient 118 and enablesweb services system 112 to associatedclient request 119 withclient 118.Client configuration file 128 may additional comprise authentication features that enable locationweb services system 112 to verify thatclient request 119 associated withclient 118 was not sent from another device. Authentication features may prevent or lessen the possibility of inadvertent or illicit interference withcommunication system 100.File 128 may be of any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others. -
Client processor 122 executes instructions and manipulates data to perform operations ofclient 118. AlthoughFIG. 1 illustrates asingle processor 122 inclient 118,multiple processors 122 may be used according to particular needs, and reference toprocessor 122 is meant to includemultiple processors 122, where applicable. In the illustrated embodiment,processor 122 includesnetwork interface 126.Network interface 126 may facilitate communication withnetwork 116. In certain embodiments,client 118 may generate a request toweb services system 112 vianetwork 116 for information based on location data associated withmobile device 130.Interface 126 calibrates the transmission of these requests and the reception of responses to these requests. Generally,interface 126 comprising the logic encoded in software and/or hardware in a suitable combination and operable to communicate withnetwork 116 vialink 123. More specifically,interface 126 may comprise software supporting one or more communication protocols associated withlink 123 andnetwork 116 hardware operable to communicate physical signals. - In one aspect of operation,
server 144 receives locations data associated withmobile device 130 and stores the information inserver memory 148.Server 144 may receive aclient request 119 fromclient 118, including a location request and information that identifies theclient 118 andmobile device 130.Web services 152 compares the identifiedclient 118 topermission configuration file 162 to determine whatpermissions client 118 may have with regard to location data associated withmobile device 130. If the location request includes a monitoring request,Web services 152 forwards the monitoring request tomonitoring engine 154.Monitoring engine 154 may store criteria inmonitoring configuration file 164 and periodically compare location data associated withmobile device 130 to the criteria. In response to any criterion being satisfied, monitoringengine 154 automatically transmits an alert toclient 118. If the location request does not include a monitoring request,web services 152 extracts the corresponding data fromrecord 158 and generates a response to the location request.Web services 152 automatically transmits thelocation response 121 toclient 118. In one embodiment,web services 152 transmits an SOAP messaging based on XML comprising location data. -
FIG. 2A illustrates one embodiment of implementingmobile device 130 ofsystem 100. In the illustrated embodiment,mobile device 130 includes amobile processor 132 and amobile memory 134. In this embodiment,mobile processor 132 includeslocation awareness engine 136,mobile management engine 166, andpermission interface 168.Location awareness engine 136, as discussed above, provides location data associated withmobile device 130 based on any suitable method.Mobile management engine 166 is operable to receive and decode server requests fromserver 144 and transmit responses to these requests. Additionally,mobile management engine 166 may querylocation awareness engine 136 in order to provide location data toserver 144.Permission interface 168 is operable to determine whatpermissions client 118 has with regard to location data associated withmobile device 130. In one embodiment,permission interface 168 is configured by an administrator remotely located frommobile device 130 in which case the administrator, notmobile device 130, determines permissions of clients. It will be understood that these permissions may be In one embodiment,permission interface 168 receives a client identifier frommobile management engine 166, which may be extracted from the server request. -
Mobile memory 134 includesclient permission file 170.Client permission file 170 comprises rules, instructions, algorithms, or any other directive delineating permissions granted toclient 118 regarding location data associated withmobile device 130.File 170 may be any suitable format including XML documents, flat files, CSV files, SQL tables, relational database tables, and others. -
FIG. 2B illustrates one implementation ofserver 144 ofsystem 100.Server 144 includesserver processor 146 andserver memory 148.Server memory 148 includes apolling configuration file 140, amonitoring configuration file 164, apermission configuration file 162, and alocation record repository 156. As discussed in detail above,location record repository 156 includes a plurality ofrecords 158, and each record 158 includes at least onedata object 160.Monitoring configuration file 164 may include rules, instructions, and algorithms, or any other directives used byserver 144 to monitormobile device 130, which may include criteria as discussed above.Server processor 146 includesserver agent 172,web services 152, andmonitoring engine 154.Server agent 172 is operable to polllocation awareness engine 136 ofmobile device 130 based onpolling configuration file 140. As discussed above,web services 152 is operable to receive and process client requests 119 and transmitlocation responses 121 based on location data associated withmobile device 130.Monitoring engine 154 may monitor location data ofmobile device 130 and compare location data ofmobile device 130 to criteria stored inmonitoring configuration file 164. In response to location data satisfying a criterion, monitoringengine 154 may automatically communicate a response toclient 118. - In one aspect of operation regarding
FIGS. 2A and 2B ,server agent 172 may transmit a server request for location data associated withmobile device 130 vianetwork 116.Mobile management engine 166 may receive and decode the server requests and forward a request for location data tolocation awareness engine 136. Additionally,mobile management engine 166 may forward the server request topermission interface 168.Permission interface 168 may extract permissions associated with the location data ofmobile device 130 fromclient permission file 170 and forward them tomobile management engine 166. Additionally,location awareness engine 136 may forward location data tomobile management engine 166.Mobile management engine 166 receives location data and permissions and encodes a wireless signal to be transmitted overwireless link 117 toserver 144.Server agent 172 receives and decodes mobile device's 130 response and stores location data inlocation record repository 156 and permission information inpermission configuration file 162.Web services 152 receives and decodesclient request 119 fromclient 118, including requests for location data and monitoring requests. Monitoring requests are forwarded tomonitoring engine 154, which extracts criteria from the monitoring request. Each criterion is stored inmonitoring configuration file 164.Monitoring engine 154 monitors location data received frommobile device 130, and in response to the location data satisfying at least one criterion, an alert is automatically communicating toclient 118. Regarding request for location data,web services 152 extracts the relevant portion of the record 158 corresponding to the requested location data.Web services 152 may process the extracted portion ofrecord 158 and encode a signal withlocation response 121 for transmission toclient 118. -
FIG. 3 illustrates a flowchart of anexemplary method 300 for monitoring location data associated with amobile device 130.Method 300 is described in respect tosystem 100. However, any other suitable system may usemethod 300 to provide location data without departing from the scope of this disclosure. Generally,method 300 describesweb services 152 receiving requests for location data fromclient 118, processing the requests, and transmitting a response based on the location data ofmobile device 130. -
Method 300 begins atstep 302 whereweb services 152 receives location data associated withmobile device 130. Location data may be stored remotely or in memory. Additionally,web services 152 may poll, receive, or otherwise collect location data associated withmobile device 130. Next, atstep 304,web services 152 receives aclient request 119 fromclient 118.Client request 119 may include a request for location data or a request for monitoring a particular criterion. Atdecisional step 306, ifweb services 152 does not identify the mobile device indicated in theclient request 119 then, atstep 308, an error message is transmitted toclient 118 indicating thatmobile device 130 is not identified, at which point processing ends. Ifmobile device 130 is identified byweb services 152, then, atdecisional step 310,web services 152 determines what permissions are available toclient 118 regarding access to location data associated withmobile device 130. In one embodiment,web services 152 compares the identifiedclient 118 topermission configuration file 162 to determine what permissions are available toclient 118. Ifpermission configuration file 162 does not grantclient 118 permission to location data,web services 152 may transmit a permission request tomobile device 130 requesting permission forclient 118 to have access to location data stored inlocation record repository 158 atstep 312. Atdecisional step 314, if permission is not granted bymobile device 130, thenweb services 152 transmits a denial of access to location data message toclient 118 atstep 316, at which point processing ends. If permission is granted toclient 118 via a response frommobile device 130 or frompermission configuration file 162, then atstep 318,web services 152 determines whetherclient request 119 includes a location request. Ifclient request 119 includes a request for location data, thenweb services 152 transmits the corresponding location data toclient 118, as discussed in detail above, atstep 320.Method 300 proceeds todecisional step 322. If monitoring request is not included inclient request 119, thenmethod 300 ends. If a monitoring request is included inclient request 119,web services 152 extracts criteria from the request and stores the criteria inmonitoring configuration file 164 atstep 324. Atdecisional step 326, if at least one of the criterion is satisfied, then, atstep 328, an alert is automatically transmitted toclient 118. It will be understood that the criteria may be monitored by a single or separate processes. Returning todecisional step 326, if none of the criteria are satisfied, thenweb services 152 receive additional location data frommobile device 130 atstep 330. Next, atstep 332,web services 152 stores the additional location data inlocation record repository 156. Atdecisional step 332, if at least one of the criterion is not satisfied, thenmethod 300 returns to step 330. If at least one of the criterion is satisfied, thenmethod 300 proceeds to step 328, at whichpoint web services 152 transmits an alert toclient 118. Atdecisional step 336, if all criteria are satisfied,method 300 ends. If at least one criterion is not satisfied, thenmethod 300 returns to step 330. - Although this disclosure has been described in terms of certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure.
Claims (34)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/828,879 US7647164B2 (en) | 2004-04-21 | 2004-04-21 | Web service for mobile device tracking |
PCT/US2005/013095 WO2005104570A2 (en) | 2004-04-21 | 2005-04-18 | Web service for mobile device tracking |
EP05742338.6A EP1745659B1 (en) | 2004-04-21 | 2005-04-18 | Web service for mobile device tracking |
EP19215888.9A EP3661163B1 (en) | 2004-04-21 | 2005-04-18 | Web service for mobile device tracking |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/828,879 US7647164B2 (en) | 2004-04-21 | 2004-04-21 | Web service for mobile device tracking |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050251326A1 true US20050251326A1 (en) | 2005-11-10 |
US7647164B2 US7647164B2 (en) | 2010-01-12 |
Family
ID=34967818
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/828,879 Active 2025-12-04 US7647164B2 (en) | 2004-04-21 | 2004-04-21 | Web service for mobile device tracking |
Country Status (3)
Country | Link |
---|---|
US (1) | US7647164B2 (en) |
EP (2) | EP1745659B1 (en) |
WO (1) | WO2005104570A2 (en) |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060018295A1 (en) * | 2004-07-26 | 2006-01-26 | Samsung Electronics Co., Ltd. | Location tracking method in coordinator-based wireless network |
US20060173782A1 (en) * | 2005-02-03 | 2006-08-03 | Ullas Gargi | Data access methods, media repository systems, media systems and articles of manufacture |
US20060184680A1 (en) * | 2005-02-14 | 2006-08-17 | Nokia Corporation | Location services for unlicensed mobile access |
US20060217131A1 (en) * | 2004-10-29 | 2006-09-28 | Skyhook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected access points within range of user device |
US20080076385A1 (en) * | 2006-09-26 | 2008-03-27 | Idt Corporation | Multi-mode wireless communication devices and systems for prepaid communication services |
US20080182593A1 (en) * | 2005-02-25 | 2008-07-31 | Jacob Sharony | System and Method for Asset Location in Wireless Networks |
US20080227462A1 (en) * | 2007-03-13 | 2008-09-18 | General Instrument Corporation | Methods and Apparatus for Locating Access Device |
US20080268870A1 (en) * | 2005-02-03 | 2008-10-30 | Cyril Houri | Method and System for Obtaining Location of a Mobile Device |
EP2023576A2 (en) * | 2007-04-12 | 2009-02-11 | Siemens Aktiengesellschaft | Method and system for providing services tailored for subscribers |
US20090063038A1 (en) * | 2007-08-30 | 2009-03-05 | Telenav, Inc. | Navigation system having location based service and temporal management |
US20090076875A1 (en) * | 2005-12-02 | 2009-03-19 | Modiv Media, Inc. | System for queue and service management |
US20110045801A1 (en) * | 2008-11-25 | 2011-02-24 | Parker Ii Lansing Arthur | System, method and program product for location based services, asset management and tracking |
US20110179429A1 (en) * | 2009-04-03 | 2011-07-21 | Hewlett-Packard Development Company Lp | Method and apparatus for network communications |
US20110239274A1 (en) * | 2005-04-26 | 2011-09-29 | Guy Heffez | Methods for acouiring an internet user's consent to be located and for authenticating the identity of the user using location information |
JP2012005119A (en) * | 2010-06-18 | 2012-01-05 | Nhn Corp | Method and system for acquiring position of terminal |
US8140094B2 (en) | 2005-02-22 | 2012-03-20 | Skyhook Wireless, Inc. | Continuous data optimization of new access points in positioning systems |
US20130031120A1 (en) * | 2011-07-25 | 2013-01-31 | Luca Passani | System and Method for using a Device Description Repository |
US8406785B2 (en) | 2009-08-18 | 2013-03-26 | Skyhook Wireless, Inc. | Method and system for estimating range of mobile device to wireless installation |
US8559974B2 (en) | 2010-06-11 | 2013-10-15 | Skyhook Wireless, Inc. | Methods of and systems for measuring beacon stability of wireless access points |
US8606294B2 (en) | 2010-10-05 | 2013-12-10 | Skyhook Wireless, Inc. | Method of and system for estimating temporal demographics of mobile users |
US20140344139A1 (en) * | 2013-05-15 | 2014-11-20 | Cellco Partnership D/B/A Verizon Wireless | Processing analytics data received by sensor devices |
US8983493B2 (en) | 2004-10-29 | 2015-03-17 | Skyhook Wireless, Inc. | Method and system for selecting and providing a relevant subset of Wi-Fi location information to a mobile client device so the client device may estimate its position with efficient utilization of resources |
US9103900B2 (en) | 2006-07-07 | 2015-08-11 | Skyhook Wireless, Inc. | System and method of gathering WLAN packet samples to improve position estimates of WLAN positioning device |
US9298897B2 (en) | 2011-06-22 | 2016-03-29 | Skyhook Wireless, Inc. | Method of and systems for privacy preserving mobile demographic measurement of individuals, groups and locations over time and space |
US9392406B2 (en) | 2005-02-03 | 2016-07-12 | Trueposition, Inc. | Method and system for location-based monitoring of a mobile device |
US20170041797A1 (en) * | 2009-10-15 | 2017-02-09 | At&T Intellectual Property I, L.P. | Management of access to service in an access point |
US9801033B1 (en) * | 2016-04-08 | 2017-10-24 | Vivint, Inc. | Family member tracking |
US9877195B2 (en) | 2008-05-13 | 2018-01-23 | At&T Mobility Ii Llc | Location-based services in a femtocell network |
US10021514B2 (en) | 2007-02-23 | 2018-07-10 | Locator IP, L.P. | Interactive advisory system for prioritizing content |
US10149126B2 (en) | 2006-07-12 | 2018-12-04 | At&T Intellectual Property I, L.P. | Pico-cell extension for cellular network |
US10362435B2 (en) | 2006-01-19 | 2019-07-23 | Locator IP, L.P. | Interactive advisory system |
US10411908B2 (en) | 2000-07-24 | 2019-09-10 | Locator IP, L.P. | Interactive advisory system |
US10499247B2 (en) | 2008-05-13 | 2019-12-03 | At&T Mobility Ii Llc | Administration of access lists for femtocell service |
AU2017279717B2 (en) * | 2006-01-19 | 2020-01-30 | Locator IP, L.P. | Interactive Advisory System |
US11265386B2 (en) * | 2014-03-07 | 2022-03-01 | Comcast Cable Communications, Llc | Location aware authorization system |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8499028B2 (en) * | 2005-02-23 | 2013-07-30 | International Business Machines Corporation | Dynamic extensible lightweight access to web services for pervasive devices |
US11308477B2 (en) | 2005-04-26 | 2022-04-19 | Spriv Llc | Method of reducing fraud in on-line transactions |
US11818287B2 (en) | 2017-10-19 | 2023-11-14 | Spriv Llc | Method and system for monitoring and validating electronic transactions |
US12086803B2 (en) | 2005-08-25 | 2024-09-10 | Spriv Llc | Method for authenticating internet users |
US20080174485A1 (en) * | 2007-01-24 | 2008-07-24 | Carani Sherry L | Tracking System and Method with Asset Tool Bar for Polling, Message, Historic Report, Location, Map and Geo Fence Features |
US11354667B2 (en) | 2007-05-29 | 2022-06-07 | Spriv Llc | Method for internet user authentication |
US12034863B2 (en) | 2009-01-21 | 2024-07-09 | Spriv Llc | Methods of authenticating the identity of a computer |
US20110227747A1 (en) * | 2010-03-19 | 2011-09-22 | Wirefree Corporation | Collision avoidance |
US11792314B2 (en) | 2010-03-28 | 2023-10-17 | Spriv Llc | Methods for acquiring an internet user's consent to be located and for authenticating the location information |
US8249621B2 (en) * | 2010-10-21 | 2012-08-21 | Google Inc. | Frequency of geographic location updates for an electronic device based on user communication |
US8831563B2 (en) * | 2011-02-04 | 2014-09-09 | CSC Holdings, LLC | Providing a service with location-based authorization |
US11978052B2 (en) | 2011-03-28 | 2024-05-07 | Spriv Llc | Method for validating electronic transactions |
EP2637365B1 (en) * | 2011-04-29 | 2018-06-13 | Huawei Technologies Co., Ltd. | Method for controlling internet services, and relevant device and system |
US9535154B2 (en) | 2011-09-12 | 2017-01-03 | Microsoft Technology Licensing, Llc | Cache-based location determination |
US20130226756A1 (en) * | 2012-02-23 | 2013-08-29 | Tata Consultancy Services Limited | System for debt collection workflow administration |
US9749206B2 (en) | 2012-10-30 | 2017-08-29 | Elwha Llc | Methods and systems for monitoring and/or managing device data |
US20140123325A1 (en) | 2012-11-26 | 2014-05-01 | Elwha Llc | Methods and systems for managing data and/or services for devices |
US9626503B2 (en) | 2012-11-26 | 2017-04-18 | Elwha Llc | Methods and systems for managing services and device data |
US9088450B2 (en) | 2012-10-31 | 2015-07-21 | Elwha Llc | Methods and systems for data services |
US9619497B2 (en) | 2012-10-30 | 2017-04-11 | Elwah LLC | Methods and systems for managing one or more services and/or device data |
US10091325B2 (en) | 2012-10-30 | 2018-10-02 | Elwha Llc | Methods and systems for data services |
US9786146B2 (en) | 2015-05-22 | 2017-10-10 | 3Si Security Systems, Inc. | Asset tracking device configured to selectively retain information during loss of communication |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5905461A (en) * | 1997-12-08 | 1999-05-18 | Neher; Timothy J | Global positioning satellite tracking device |
US6327535B1 (en) * | 2000-04-05 | 2001-12-04 | Microsoft Corporation | Location beaconing methods and systems |
US20020042277A1 (en) * | 2000-10-10 | 2002-04-11 | Smith Steven W. | Subscriber information service center (SISC) |
US6377810B1 (en) * | 1999-06-11 | 2002-04-23 | Motorola, Inc. | Method of operation of mobile wireless communication system with location information |
US6504503B1 (en) * | 2001-09-28 | 2003-01-07 | Intel Corporation | Peer-to-peer global positioning system |
US6594483B2 (en) * | 2001-05-15 | 2003-07-15 | Nokia Corporation | System and method for location based web services |
US6716101B1 (en) * | 2000-06-28 | 2004-04-06 | Bellsouth Intellectual Property Corporation | System and method for monitoring the location of individuals via the world wide web using a wireless communications network |
US6750883B1 (en) * | 2000-04-05 | 2004-06-15 | Microsoft Corporation | Identity-based context aware computing systems and methods |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000022860A1 (en) * | 1998-10-12 | 2000-04-20 | Janus Friis Degnbol | A method and a system for transmitting data between units |
AU1967200A (en) | 1999-11-23 | 2001-06-04 | Nokia Corporation | Method for enabling a user to be notified of his/her positioning requests |
-
2004
- 2004-04-21 US US10/828,879 patent/US7647164B2/en active Active
-
2005
- 2005-04-18 EP EP05742338.6A patent/EP1745659B1/en active Active
- 2005-04-18 WO PCT/US2005/013095 patent/WO2005104570A2/en active Application Filing
- 2005-04-18 EP EP19215888.9A patent/EP3661163B1/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5905461A (en) * | 1997-12-08 | 1999-05-18 | Neher; Timothy J | Global positioning satellite tracking device |
US6377810B1 (en) * | 1999-06-11 | 2002-04-23 | Motorola, Inc. | Method of operation of mobile wireless communication system with location information |
US6327535B1 (en) * | 2000-04-05 | 2001-12-04 | Microsoft Corporation | Location beaconing methods and systems |
US6750883B1 (en) * | 2000-04-05 | 2004-06-15 | Microsoft Corporation | Identity-based context aware computing systems and methods |
US6716101B1 (en) * | 2000-06-28 | 2004-04-06 | Bellsouth Intellectual Property Corporation | System and method for monitoring the location of individuals via the world wide web using a wireless communications network |
US20020042277A1 (en) * | 2000-10-10 | 2002-04-11 | Smith Steven W. | Subscriber information service center (SISC) |
US6594483B2 (en) * | 2001-05-15 | 2003-07-15 | Nokia Corporation | System and method for location based web services |
US6504503B1 (en) * | 2001-09-28 | 2003-01-07 | Intel Corporation | Peer-to-peer global positioning system |
Cited By (88)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10411908B2 (en) | 2000-07-24 | 2019-09-10 | Locator IP, L.P. | Interactive advisory system |
US11108582B2 (en) | 2000-07-24 | 2021-08-31 | Locator IP, L.P. | Interactive weather advisory system |
US20100189082A1 (en) * | 2004-07-26 | 2010-07-29 | Samsung Electronics Co., Ltd. | Location tracking method in coordinator-based wireless network |
US20060018295A1 (en) * | 2004-07-26 | 2006-01-26 | Samsung Electronics Co., Ltd. | Location tracking method in coordinator-based wireless network |
US8538453B2 (en) * | 2004-07-26 | 2013-09-17 | Samsung Electronics Co., Ltd. | Location tracking method in coordinator-based wireless network |
US8504057B2 (en) * | 2004-07-26 | 2013-08-06 | Samsung Electronics Co., Ltd. | Location tracking method in coordinator-based wireless network |
US8478297B2 (en) | 2004-10-29 | 2013-07-02 | Skyhook Wireless, Inc. | Continuous data optimization of moved access points in positioning systems |
US9554247B2 (en) | 2004-10-29 | 2017-01-24 | Skyhook Wireless, Inc. | Techniques for computing location of a mobile device based on observed Wi-Fi access points |
US8538457B2 (en) | 2004-10-29 | 2013-09-17 | Skyhook Wireless, Inc. | Continuous data optimization of moved access points in positioning systems |
US9369884B2 (en) | 2004-10-29 | 2016-06-14 | Skyhook Wireless, Inc. | Techniques for computing location of a mobile device based on observed Wi-Fi access points |
US20060217131A1 (en) * | 2004-10-29 | 2006-09-28 | Skyhook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected access points within range of user device |
US9398558B2 (en) | 2004-10-29 | 2016-07-19 | Skyhook Wireless, Inc. | Continuous data optimization of moved access points in positioning systems |
US10080208B2 (en) | 2004-10-29 | 2018-09-18 | Skyhook Wireless, Inc. | Techniques for setting quality attributes of access points in a positioning system |
US7769396B2 (en) * | 2004-10-29 | 2010-08-03 | Skyhook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected access points within range of user device |
US8965412B2 (en) * | 2004-10-29 | 2015-02-24 | Skyhook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected access points within range of user device |
US7818017B2 (en) * | 2004-10-29 | 2010-10-19 | Skyhook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected wireless signal stations within range of user device |
US8983493B2 (en) | 2004-10-29 | 2015-03-17 | Skyhook Wireless, Inc. | Method and system for selecting and providing a relevant subset of Wi-Fi location information to a mobile client device so the client device may estimate its position with efficient utilization of resources |
US20130184003A1 (en) * | 2004-10-29 | 2013-07-18 | Skybook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected access points within range of user device |
US20080139217A1 (en) * | 2004-10-29 | 2008-06-12 | Skyhook Wireless, Inc. | Location-based services that choose location algorithms based on number of detected wireless signal stations within range of user device |
US9918295B2 (en) | 2004-10-29 | 2018-03-13 | Skyhook Wireless, Inc. | Techniques for computing location of a mobile device using calculated locations of Wi-Fi access points from a reference database |
US8031657B2 (en) | 2004-10-29 | 2011-10-04 | Skyhook Wireless, Inc. | Server for updating location beacon database |
US8837363B2 (en) | 2004-10-29 | 2014-09-16 | Skyhook Wireless, Inc. | Server for updating location beacon database |
US8630664B2 (en) | 2004-10-29 | 2014-01-14 | Skyhook Wireless, Inc. | Access point database |
US10390178B2 (en) | 2005-02-03 | 2019-08-20 | Skyhook Holding, Inc. | Techniques for wireless position determination utilizing a collaborative database |
US8565788B2 (en) * | 2005-02-03 | 2013-10-22 | Mexens Intellectual Property Holding Llc | Method and system for obtaining location of a mobile device |
US20060173782A1 (en) * | 2005-02-03 | 2006-08-03 | Ullas Gargi | Data access methods, media repository systems, media systems and articles of manufacture |
US10798525B2 (en) | 2005-02-03 | 2020-10-06 | Skyhook Holding, Inc. | Techniques for wireless position determination utilizing a collaborative database |
US9392406B2 (en) | 2005-02-03 | 2016-07-12 | Trueposition, Inc. | Method and system for location-based monitoring of a mobile device |
US9402154B2 (en) | 2005-02-03 | 2016-07-26 | Trueposition, Inc. | Methods for providing location of wireless devices using Wi-Fi |
US11388549B2 (en) | 2005-02-03 | 2022-07-12 | Skyhook Holding, Inc. | Techniques for wireless position determination utilizing a collaborative database |
US20080268870A1 (en) * | 2005-02-03 | 2008-10-30 | Cyril Houri | Method and System for Obtaining Location of a Mobile Device |
US10129697B2 (en) | 2005-02-03 | 2018-11-13 | Trueposition, Inc. | Techniques for wireless position determination utilizing a collaborative database |
US20060184680A1 (en) * | 2005-02-14 | 2006-08-17 | Nokia Corporation | Location services for unlicensed mobile access |
US8244272B2 (en) | 2005-02-22 | 2012-08-14 | Skyhook Wireless, Inc. | Continuous data optimization of moved access points in positioning systems |
US9037162B2 (en) | 2005-02-22 | 2015-05-19 | Skyhook Wireless, Inc. | Continuous data optimization of new access points in positioning systems |
US8140094B2 (en) | 2005-02-22 | 2012-03-20 | Skyhook Wireless, Inc. | Continuous data optimization of new access points in positioning systems |
US7778649B2 (en) * | 2005-02-25 | 2010-08-17 | Symbol Technologies, Inc. | System and method for asset location in wireless networks |
US20080182593A1 (en) * | 2005-02-25 | 2008-07-31 | Jacob Sharony | System and Method for Asset Location in Wireless Networks |
US20110239274A1 (en) * | 2005-04-26 | 2011-09-29 | Guy Heffez | Methods for acouiring an internet user's consent to be located and for authenticating the identity of the user using location information |
US8640197B2 (en) * | 2005-04-26 | 2014-01-28 | Guy Heffez | Methods for acquiring an internet user's consent to be located and for authenticating the identity of the user using location information |
US9064359B2 (en) * | 2005-12-02 | 2015-06-23 | Modiv Media, Inc. | System for queue and service management |
US20090076875A1 (en) * | 2005-12-02 | 2009-03-19 | Modiv Media, Inc. | System for queue and service management |
US10362435B2 (en) | 2006-01-19 | 2019-07-23 | Locator IP, L.P. | Interactive advisory system |
AU2017279717B2 (en) * | 2006-01-19 | 2020-01-30 | Locator IP, L.P. | Interactive Advisory System |
US9279877B2 (en) | 2006-07-07 | 2016-03-08 | Skyhook Wireless, Inc. | Technique for using cached information with a WLAN positioning system to obtain an estimate of a position of a mobile device |
US9103900B2 (en) | 2006-07-07 | 2015-08-11 | Skyhook Wireless, Inc. | System and method of gathering WLAN packet samples to improve position estimates of WLAN positioning device |
US10149126B2 (en) | 2006-07-12 | 2018-12-04 | At&T Intellectual Property I, L.P. | Pico-cell extension for cellular network |
US20080076385A1 (en) * | 2006-09-26 | 2008-03-27 | Idt Corporation | Multi-mode wireless communication devices and systems for prepaid communication services |
US7983712B2 (en) * | 2006-09-26 | 2011-07-19 | Idt Corporation | Multi-mode wireless communication devices and systems for prepaid communication services |
US10616708B2 (en) | 2007-02-23 | 2020-04-07 | Locator Ip, Lp | Interactive advisory system for prioritizing content |
US10021514B2 (en) | 2007-02-23 | 2018-07-10 | Locator IP, L.P. | Interactive advisory system for prioritizing content |
US20080227462A1 (en) * | 2007-03-13 | 2008-09-18 | General Instrument Corporation | Methods and Apparatus for Locating Access Device |
EP2023576A3 (en) * | 2007-04-12 | 2012-08-08 | Siemens Aktiengesellschaft | Method and system for providing services tailored for subscribers |
EP2023576A2 (en) * | 2007-04-12 | 2009-02-11 | Siemens Aktiengesellschaft | Method and system for providing services tailored for subscribers |
US8751146B2 (en) * | 2007-08-30 | 2014-06-10 | Telenav, Inc. | Navigation system having location based service and temporal management |
US20090063038A1 (en) * | 2007-08-30 | 2009-03-05 | Telenav, Inc. | Navigation system having location based service and temporal management |
US9877195B2 (en) | 2008-05-13 | 2018-01-23 | At&T Mobility Ii Llc | Location-based services in a femtocell network |
US9930526B2 (en) | 2008-05-13 | 2018-03-27 | At&T Mobility Ii Llc | Interface for access management of femto cell coverage |
US10499247B2 (en) | 2008-05-13 | 2019-12-03 | At&T Mobility Ii Llc | Administration of access lists for femtocell service |
US10225733B2 (en) | 2008-05-13 | 2019-03-05 | At&T Mobility Ii Llc | Exchange of access control lists to manage femto cell coverage |
US20110045801A1 (en) * | 2008-11-25 | 2011-02-24 | Parker Ii Lansing Arthur | System, method and program product for location based services, asset management and tracking |
US20110179429A1 (en) * | 2009-04-03 | 2011-07-21 | Hewlett-Packard Development Company Lp | Method and apparatus for network communications |
US9237415B2 (en) | 2009-08-18 | 2016-01-12 | Skyhook Wireless, Inc. | Method and system for estimating range of mobile device to wireless installation |
US8406785B2 (en) | 2009-08-18 | 2013-03-26 | Skyhook Wireless, Inc. | Method and system for estimating range of mobile device to wireless installation |
US10645582B2 (en) * | 2009-10-15 | 2020-05-05 | At&T Intellectual Property I, L.P. | Management of access to service in an access point |
US20170041797A1 (en) * | 2009-10-15 | 2017-02-09 | At&T Intellectual Property I, L.P. | Management of access to service in an access point |
US8971915B2 (en) | 2010-06-11 | 2015-03-03 | Skyhook Wireless, Inc. | Systems for and methods of determining likelihood of mobility of reference points in a positioning system |
US8630657B2 (en) | 2010-06-11 | 2014-01-14 | Skyhook Wireless, Inc. | Systems for and methods of determining likelihood of reference point identity duplication in a positioning system |
US9521512B2 (en) | 2010-06-11 | 2016-12-13 | Skyhook Wireless, Inc. | Determining a designated wireless device lacks a fixed geographic location and using the determination to improve location estimates |
US8971923B2 (en) | 2010-06-11 | 2015-03-03 | Skyhook Wireless, Inc. | Methods of and systems for measuring beacon stability of wireless access points |
US8559974B2 (en) | 2010-06-11 | 2013-10-15 | Skyhook Wireless, Inc. | Methods of and systems for measuring beacon stability of wireless access points |
US8700053B2 (en) | 2010-06-11 | 2014-04-15 | Skyhook Wireless, Inc. | Systems for and methods of determining likelihood of relocation of reference points in a positioning system |
US9014715B2 (en) | 2010-06-11 | 2015-04-21 | Skyhook Wireless, Inc. | Systems for and methods of determining likelihood of atypical transmission characteristics of reference points in a positioning system |
JP2012005119A (en) * | 2010-06-18 | 2012-01-05 | Nhn Corp | Method and system for acquiring position of terminal |
US8606294B2 (en) | 2010-10-05 | 2013-12-10 | Skyhook Wireless, Inc. | Method of and system for estimating temporal demographics of mobile users |
US9031580B2 (en) | 2010-10-05 | 2015-05-12 | Skyhook Wireless, Inc. | Method of and system for estimating temporal demographics of mobile users |
US9467807B2 (en) | 2010-10-05 | 2016-10-11 | Skyhook Wireless, Inc. | Estimating demographics associated with a selected geographic area |
US10304086B2 (en) | 2011-06-22 | 2019-05-28 | Skyhook Wireless, Inc. | Techniques for estimating demographic information |
US9298897B2 (en) | 2011-06-22 | 2016-03-29 | Skyhook Wireless, Inc. | Method of and systems for privacy preserving mobile demographic measurement of individuals, groups and locations over time and space |
US9058404B2 (en) | 2011-07-25 | 2015-06-16 | Scientiamobile, Inc. | System and method for using a device description repository |
US9547727B2 (en) * | 2011-07-25 | 2017-01-17 | Scientiamobile, Inc. | System and method for using a device description repository |
US20130031120A1 (en) * | 2011-07-25 | 2013-01-31 | Luca Passani | System and Method for using a Device Description Repository |
US9779394B2 (en) * | 2013-05-15 | 2017-10-03 | Cellco Partnership | Processing analytics data received by sensor devices |
US20140344139A1 (en) * | 2013-05-15 | 2014-11-20 | Cellco Partnership D/B/A Verizon Wireless | Processing analytics data received by sensor devices |
US11265386B2 (en) * | 2014-03-07 | 2022-03-01 | Comcast Cable Communications, Llc | Location aware authorization system |
US20220150259A1 (en) * | 2014-03-07 | 2022-05-12 | Comcast Cable Communications, Llc | Location Aware Authorization System |
US11848999B2 (en) * | 2014-03-07 | 2023-12-19 | Comcast Cable Communications, Llc | Location aware authorization system |
US9801033B1 (en) * | 2016-04-08 | 2017-10-24 | Vivint, Inc. | Family member tracking |
Also Published As
Publication number | Publication date |
---|---|
EP3661163A1 (en) | 2020-06-03 |
WO2005104570A2 (en) | 2005-11-03 |
US7647164B2 (en) | 2010-01-12 |
EP3661163B1 (en) | 2021-01-20 |
WO2005104570A3 (en) | 2006-02-09 |
EP1745659A2 (en) | 2007-01-24 |
EP1745659B1 (en) | 2020-03-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7647164B2 (en) | Web service for mobile device tracking | |
US9602604B2 (en) | Managing web services data and presence data | |
KR100641978B1 (en) | Group notification system and method for indicating the proximity between individuals or groups | |
US9813870B2 (en) | Using location-based request data for identifying beacon locations | |
US7409428B1 (en) | Systems and methods for messaging to multiple gateways | |
US8073461B2 (en) | Geo-tagged journal system for location-aware mobile communication devices | |
US10425422B1 (en) | Message content modification devices and methods | |
US8965988B1 (en) | System and method for providing an event-based and shared page connectivity platform | |
US20080183828A1 (en) | Communication system | |
US8954514B2 (en) | System and method for displaying time-sensitive alerts in a mobile device | |
US10313482B2 (en) | Method, device and system for providing services based on location information and terminal device thereon | |
US20100293255A1 (en) | Open information transmitting method, open information transmitting system, central device and recording medium | |
TWI441535B (en) | Method for using geographic signal fingerprint cluster to implement end-to-end message push | |
AU2015205906A1 (en) | Released offender geospatial location information clearinghouse | |
US20090313325A1 (en) | Distributed Technique for Cascaded Data Aggregation in Parallel Fashion | |
US20070126581A1 (en) | Method and apparatus for providing presence information using radio frequency identification technique | |
US20190236734A1 (en) | Communications systems, methods, and devices | |
Humaïra et al. | An Adaptive Communication Model for Android Bus Tracking App | |
Cheung et al. | Alert-based hiker status system | |
EP1222648A1 (en) | Internet-based multiple objects tracking system | |
Browall et al. | A location based service platform: for the next generation of mobile devices, including intelligent position updates | |
JP2004336361A (en) | Location dependent information waiting system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: COMPUTER ASSOCIATES THINK, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:REEVES, SIMON;REEL/FRAME:015252/0819 Effective date: 20040416 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: GOOGLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COMPUTER ASSOCIATES THINK, INC.;REEL/FRAME:028801/0049 Effective date: 20120330 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: GOOGLE LLC, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:GOOGLE INC.;REEL/FRAME:044101/0610 Effective date: 20170929 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |