System and method for geofencing

• US 9,973,891 B2
• Filed: 10/21/2016
• Issued: 05/15/2018
• Est. Priority Date: 10/23/2015
• Status: Active Grant

• Current Assignee: Kodiak Networks (Motorola Solutions, Inc.)
• Original Assignee: Kodiak Networks (Motorola Solutions, Inc.)
• Inventors: Patel, Krishnakant M, Dash, Debabrata, Ayyasamy, Ravi, Chandana, Pratap, Setti, Bharat Ram, Gaffar, Sayyad, Nerlikar, Rohit Ashok, Kandula, Ramu
• Primary Examiner(s): Nealon, William
• Application Number:
  US15/331,559
• Publication Number:
  US 20170118592A1
• Time in Patent Office: 571 Days
• Field of Search: 4554561
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/022 with dynamic range variability
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/027 using movement velocity, acceleration information
• CPC Class Codes: H04W 4/06 Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 64/006 with additional information processing, e.g. for direction or speed determination

Abstract

A system and method for geofencing includes sending, by the location management server, location data collection criteria and location data reporting criteria to a first location-aware client; and receiving, by the location management server, location data from the first location-aware client, the location data collected by the first location-aware client according to the location data collection criteria, the location data received from the first location-aware client according to the location data reporting criteria.

Claims

1. A method, by a location management server, comprising:

receiving, by the location management server, a request from a supervisory location-aware client of a plurality of location-aware clients, each of the location-aware clients Participating in a first push-to-talk (PTT) call;

sending, by the location management server, location data collection criteria and location data reporting criteria to a first location-aware client of the location-aware clients;

receiving, by the location management server, location data from the first location-aware client, the location data collected by the first location-aware client according to the location data collection criteria, the location data received from the first location-aware client according to the location data reporting criteria; and

modifying, by the location management server, the first PIT call according to the received location data.

2. The method of claim 1, wherein the location data collection criteria and the location data reporting criteria are the same.

3. The method of claim 1, wherein sending the location data collection criteria and the location data reporting criteria comprises:

storing, by the location management server, the location data collection criteria and the location data reporting criteria in a database (DB) cluster accessible to the location management server, the location data collection criteria and the location data reporting criteria each stored in an observable data field of the DB cluster.

4. The method of claim 1, wherein receiving the location data from the first location-aware client comprises:

observing, by the location management server, synchronization of the location data from a first local database at the first location-aware client into a database (DB) cluster accessible to the location management server.

5. The method of claim 1, wherein the location data collection criteria specifies a frequency of location data collection by the first location-aware client as a function of at least one of:

time elapsed, distance traveled by the first location-aware client, velocity of the first location-aware client, acceleration of the first location-aware client, altitude of the first location-aware client, access network events of the first location-aware client, environmental sensor events of the first location-aware client, and health sensor events of the first location-aware client.

6. The method of claim 1, wherein the location data reporting criteria specifies a frequency of location data reporting by the first location-aware client as a function of at least one of:

time elapsed, distance traveled by the first location-aware client, velocity of the first location-aware client, acceleration of the first location-aware client, altitude of the first location-aware client, access network events of the first location-aware client, environmental sensor events of the first location-aware client, and health sensor events of the first location-aware client.

7. The method of claim 1, wherein the location data comprises a geographic latitude and longitude of the first location-aware client, wherein the location data further comprises a timestamp of the location data, an indication of events causing the location data to be collected by the first location-aware client, network information for the first location-aware client, or a combination thereof.

8. The method of claim 1, further comprising:

evaluating, by the location management server, the location data received from the first location-aware client to determine a current location-state of the first location-aware client with respect to a geofence, the current location-state indicating whether the first location-aware client has entered the geofence, has exited the geofence, is inside of the geofence, or is outside of the geofence; and

performing, by the location management server, one or more actions in accordance with the current location-state of the first location-aware client.

9. The method of claim 8, wherein the one or more actions performed by the location management server comprise:

sending, by the location management server, to each of the location-aware clients participating in the first PIT call, a notification indicating the current location-state of the first location-aware client with respect to the geofence, or a current location of the first location-aware client.

10. The method of claim 9, wherein sending the notification comprises:

storing, by the location management server, a document indicating the notification in a database (DB) cluster accessible to the location management server, the document stored in an observable data field of the DB cluster, each of the location-aware clients synchronizing with the location management server in response to the document being stored in the observable data field.

11. The method of claim 9, wherein the geofence is a virtual boundary established with respect to an anchor point tracked by the location management server, the anchor point being one of stationary or in motion.

12. The method of claim 1, further comprising:

receiving, by the location management server, a request from the supervisory location-aware client for the location data collected by the first location-aware client, the location data collection criteria and the location data reporting criteria sent to the first location-aware client in response to receiving the request.

13. The method of claim 12, wherein receiving the request from the supervisory location-aware client for the location data comprises:

observing, by the location management server, synchronization of the request from a second local database at the supervisory location-aware client into a database (DB) cluster accessible to the location management server.

14. The method of claim 12, wherein the request from the supervisory location-aware client indicates at least one of the location data collection criteria and the location data reporting criteria.

15. The method of claim 12, wherein the request from the supervisory location-aware client indicates a definition of a geofence, and further indicates instructions to filter the location data from the first location-aware client according to a current location-state of the first location-aware client with respect to the geofence, the current location-state indicating whether the first location-aware client has entered the geofence, has exited the geofence, is inside of the geofence, or is outside of the geofence.

16. The method of claim 15, further comprising:

determining, by the location management server, the current location-state of the first location-aware client with respect to the geofence; and

executing the instructions indicated by the request from the supervisory location-aware client.

17. The method of claim 15, further comprising:

transmitting, by the location management server, the definition of the geofence and the instructions to the first location-aware client.

18. A method, by a first location-aware client, comprising:

receiving, by the first location-aware client, location data collection criteria and location data reporting criteria from a location management server;

collecting, by the first location-aware client, location data in accordance with location data collection criteria;

storing, by the first location-aware client, the location data in a first local database at the first location-aware client;

reporting, by the first location-aware client, at least a portion of the location data to the location management server in accordance with the location data reporting criteria; and

modifying, by the first location-aware client, the location data reporting criteria in response to participation by the first location-aware client in a first push-to-talk (PTT) call.

19. The method of claim 18, further comprising:

receiving, by the first location-aware client, a definition of a geofence, the geofence being a virtual boundary established with respect to an anchor point; and

determining, by the first location-aware client, a current location-state of the first location-aware client with respect to the geofence by evaluating the location data collected by the first location-aware client, the current location-state indicating whether the first location-aware client has entered the geofence, has exited the geofence, is inside of the geofence, or is outside of the geofence.

20. The method of claim 19, further comprising:

receiving, by the first location-aware client, a set of instructions from the location management server, each of the set of instructions associated with a predetermined location-state; and

executing, by the first location-aware client, an instruction of the set of instructions in response to the predetermined location-state of the instruction corresponding to the current location-state of the first location-aware client, after collecting the location data.

21. The method of claim 20, wherein the set of instructions includes a directive to report the current location-state of the first location-aware client to the location management server.

22. The method of claim 20, wherein the set of instructions includes a directive to report at least a portion of the location data in accordance with the location data reporting criteria.

23. The method of claim 20, wherein the set of instructions includes a directive to perform one or more actions, the one or more actions including one of sending a message to the location management server, and invoking a service at the first location-aware client.

24. The method of claim 20, wherein receiving the set of instructions from the location management server comprises:

observing, by the first location-aware client, synchronization of the set of instructions from a DB cluster accessible to the location management server into the first local database.

25. The method of claim 20, wherein receiving the set of instructions from the location management server comprises:

receiving, by the first location-aware client, a multicast transmission including the set of instructions.

26. The method of claim 25, wherein the multicast transmission is an Evolved Multimedia Broadcast Multicast Services (eMBMS) transmission.

27. The method of claim 19, wherein receiving the definition of the geofence comprises:

observing, by the first location-aware client, synchronization of the definition of the geofence from a DB cluster accessible to the location management server into the first local database.

28. The method of claim 19, wherein receiving the location data collection criteria and the location data reporting criteria from the location management server comprises:

observing, by the first location-aware client, synchronization of the location data collection criteria and the location data reporting criteria from a DB cluster accessible to the location management server into the first local database.

29. The method of claim 19, wherein receiving the location data collection criteria and the location data reporting criteria from the location management server comprises:

receiving, by the first location-aware client, a multicast transmission including the location data collection criteria and the location data reporting criteria.

30. The method of claim 29, wherein the multicast transmission is an Evolved Multimedia Broadcast Multicast Services (eMBMS) transmission.

31. The method of claim 19, further comprising:

receiving, by the first location-aware client, an update for the definition of the geofence.

32. The method of claim 31, wherein the update for the definition of the geofence comprises a change in location coordinates of the anchor point, shape of the geofence, size of the geofence, or a combination thereof.

33. The method of claim 19, wherein the anchor point of the geofence is static.

34. The method of claim 19, wherein the anchor point of the geofence is in motion.

35. The method of claim 19, wherein the geofence is a two-dimensional shape.

36. The method of claim 19, wherein the geofence is a three-dimensional shape.

37. A location management server comprising:

a processor; and

a computer readable storage medium storing programming for execution by the processor, the programming including instructions for;

receiving a request from a supervisory location-aware client of a plurality of location-aware clients, each of the location-aware clients participating in a first push-to-talk (PTT) call;

sending location data collection criteria and location data reporting criteria to a first location-aware client of the location-aware clients;

receiving location data from the first location-aware client, the location data collected by the first location-aware client according to the location data collection criteria, the location data received from the first location-aware client according to the location data reporting criteria; and

modifying the PIT call according to the received location data.

38. The location management server of claim 37, wherein the programming further includes instructions for:

evaluating the location data to determine a current location-state of the first location-aware client with respect to a geofence; and

performing an action according to the current location-state of the first location-aware client.

39. The location management server of claim 37, wherein the programming further includes instructions for:

indicating a definition of a geofence and instructions to the first location-aware client, the instructions executed by the first location-aware client in response to determining a current location-state of the first location-aware client with respect to the geofence.

40. The location management server of claim 37, wherein the instruction for sending the location data collection criteria and the location data reporting criteria comprises instructions for:

transmitting a multicast transmission indicating the location data collection criteria and the location data reporting criteria to each of the location-aware clients participating in the first PTT call.

41. The location management server of claim 37, wherein the instruction for sending the location data collection criteria and the location data reporting criteria comprises instructions for:

storing, by the location management server, a document indicating the location data collection criteria and the location data reporting criteria in a database (DB) cluster accessible to the location management server, the document stored in an observable data field of the DB cluster, the first location-aware client synchronizing with the location management server in response to the document being stored in the observable data field.

44. The location management server of claim 37, wherein the programming further includes instructions for:

receiving a request from the supervisory location-aware client for the location data collected by the first location-aware client, the location data collection criteria and the location data reporting criteria sent to the first location-aware client in response to receiving the request, wherein the request from the supervisory location-aware client indicates a definition of a geofence, and further indicates instructions to filter the location data from the first location-aware client according to a current location-state of the first location-aware client with respect to the geofence, the current location-state indicating whether the first location-aware client has entered the geofence, has exited the geofence, is inside of the geofence, or is outside of the geofence.

42. A first location-aware client comprising:

a processor; and

a computer readable storage medium storing programming for execution by the processor, the programming including instructions for;

receiving location data collection criteria and location data reporting criteria from a location management server;

collecting location data in accordance with location data collection criteria;

storing the location data in a first local database at the first location-aware client;

reporting at least a portion of the location data to the location management server in accordance with the location data reporting criteria; and

modifying the location data reporting criteria in response to participation by the first location-aware client in a first push-to-talk (PTT) call.

43. The first location-aware client of claim 42, wherein the programming includes further instructions for:

receiving a definition of a geofence definition and instructions corresponding to a current location-state of the first location-aware client; and

executing the instructions in response to determining the current location-state of the first location-aware client, the current location-state determined by evaluating the location data.