High density location-based service zone management for a geographic region

Disclosed are various embodiments for managing which location-based service zones to monitor when the number location-based service zones within a geographic region exceed the amount the device can support. An active zone defining a geographic region and location-based service zones within the geographic region is provided by another computing device. When the number of location-based service zones meets or exceeds a predefined threshold, a subset of the location-based service zones is selected for monitoring according to a current device location and/or other parameters.

BACKGROUND

Geographic fences, or “geofences,” and beacons can be used for marketing purposes with respect to location-based services. For example, geofences can be used to provide notifications to a mobile device when the mobile device enters a geographic region defined by the boundaries of a geofence. Likewise, when a mobile device is physically close to a beacon broadcasting a wireless signal, the mobile device can receive the broadcasted signal and a notification may be triggered. The notifications associated with geofences and/or beacons may relate to the location-based services.

DETAILED DESCRIPTION

The present disclosure relates to various systems and methods for managing location-based service zones (e.g., geofences, beacons, etc.) being monitored by a client device. Some embodiments of the present disclosure relate to receiving a comprehensive set of location-based service zones within a dynamically sized region surrounding a user device and dynamically filtering the location-based service zones to determine a subset of the location-based service zones within the dynamically sized region to monitor. The filtering may be based on a variety of factors such as, for example, device limitations, current location, previously monitored location-based service zones, device speed, device direction, user interaction history, aggregate user interaction history, etc.

Examples of location-based service zones include geographic fences (“geofences”) and beacons. A geofence can be defined as a virtual geographic boundary, such as the combination of a geographic coordinate and a radius. For example, a geofence may define an area in which a user may experience a location-based service associated with a particular provider. The geofenced area can be formed or defined by a virtual perimeter surrounding the area corresponding to the particular location-based service that a user may want to experience. An interior area of a geofence may be any suitable size and any suitable shape. The virtual perimeter can correspond to a two-dimensional or a three-dimensional perimeter. For example, if the provider relates to a delivery service, a two-dimensional perimeter can include an area centered on the delivery location, while a three-dimensional perimeter may include a height or altitude of the delivery location. As another example, a three-dimensional perimeter may use height or altitude in order to situate the geofence on a particular floor or suite of a building.

A beacon may include a device configured to broadcast a wireless signal. Using the example of the delivery service, a provider device may include a beacon that broadcasts a wireless signal related to the location of the provider device. When a user device is within a proximity of a beacon, the user device can receive the wireless signal, thereby triggering an event notification associated with the beacon (e.g., displaying a message, notifying the provider device of proximate location, etc.).

Providers of services (e.g., mobile store, mobile delivery service, brick-and-mortar store, etc.) may create location-based service zones to initiate user experiences relative to the services. In one non-limiting example, a provider may be associated with a merchant selling items at mobile delivery locations. Each delivery location may be associated with a respective location-based service zone. For example, when the merchant is selling the items at location A, a geofence may be created that defines a boundary surrounding the merchant location. When a user device that is monitoring the geofence crosses the boundary defined by the geofence, the client device may recognize the geofence and perform actions associated with the geofence (e.g., display message including merchant location, send notification to provider to prepare items for pickup, etc.).

One embodiment of the present disclosure relates to selecting a subset of location-based service zones to monitor within an active zone when the number of location-based service zones exceeds limitations of a client device that limit the number of location-based service zones the client device can monitor. An active zone is a dynamically sized geographic area that contains a comprehensive set of location-based service zones and is created by a server computing device. A client device can receive the active zone containing the location-based service zones from an active zone management system and monitor the location-service zones included in the active zone. When the number of location-based service zones within a particular active zone exceeds the limitations of the client device, the client device can select a subset of the location-based service zones within the active zone to monitor. Accordingly, the subset of the location-based service zones is a selection of a portion of the location-based service zones that were included in the active zone provided by the server computing device.

For example, different types of client devices may have limitations as to the number of location-based service zones the client device can support. The client device limitations may be imposed by the client device in order to optimize power usage, memory usage, and/or processor usage of the client device. In some embodiments, the client device may apply a set of filtering rules, analyze the different location-based service zones within the active zone, and select a subset of the location-based service zones based on factors such as, for example, a current location of the client device, recently broken location-based service zones being monitored by the client device (e.g., exiting or entering a location-based service zone), device speed, device direction, user interaction history, aggregate user interaction history, and/or any other factor as can be appreciated.

FIG. 1is a drawing depicting an example scenario showing a subset of location-based service zones100within an active zone103that are being monitored by a client device106according to various embodiments of the present disclosure. In this example, the client device106corresponds to a handheld mobile device (e.g., a tablet, a smartphone, etc.). The location-based service zones100can comprise geofences109(e.g.,109a,109b,109c,109d,109e), beacons112(e.g.,112a,112b,112c,112d), and/or any other types of location-based service zones100as can be appreciated.

The active zone103is created by the active zone management system115being executed on at least one computing device118according to at least a location of the client device106. An active zone103is created to encompass the client device location according to a predefined radius. For example, in some embodiments, the active zone103may be created having a center at the location of the client device106and a radius of some predetermined value (e.g., 1 kilometer (km), 5 km, 25 km, etc.). Once the active zone103is created, location-based service zones100within the active zone103may be identified. In some embodiments, the radius has a minimum predefined value (e.g., 1 km, 3 km). This minimum predefined value may be based on device limitations, design choice, precision capabilities for identifying location-based service zones, and/or any other factor as can be appreciated.

The active zone management system115may create an active zone103and transmit active zone data117(e.g., geographic parameters, location-based service zone parameters, etc.) to the active zone filter application124being executed on the client device106. The active zone103can be created with respect to a client device location127. The client device location127can be determined and/or estimated according to coordinates provided by the client device106, location-based service zone entry and/or exit history, and/or any other way of determining and/or estimating a device location127.

In some embodiments, the client device106may request an active zone103from the computing device118. In other embodiments, the active zone management system115may send an active zone103to the client device106without a request from the client device106. For example, the active zone management system115may generate and send an active zone103to the client device106periodically. In another example, the active zone management system115may send an active zone103to the client device upon detection of an exit from a previously monitored active zone103. The exit from a previously monitored active zone103can be determined according to a device location127being received from the client device106, a trigger notification received from the client device106indicating that the client device106has exited the geographic region defining the active zone103, and/or any other factor as can be appreciated.

Upon creation of the active zone103, the active zone management system115transmits active zone data117to the client device106. The active zone data117includes the data associated with an active zone103created for the client device106and by the active zone management system115. The active zone data117may include geofence parameters230(FIG. 2), beacon parameters233(FIG. 2), aggregate interaction data215(FIG. 2), and/or any other type of data that can be appreciated.

In some embodiments, the active zone data117includes parameters for a quantity of location-based service zones100that exceeds a device supported threshold. The device supported threshold may be defined according to client device limitations that may be imposed by the client device106in order to optimize power usage, memory usage, and/or processor usage of the client device106. For example, a particular client device106may only be able to monitor fifty (50) location-based service zones100at a given time. As such, if the active zone103provided by the active zone management system115includes a quantity of location-based service zones100that exceeds the quantity supported by the client device106, the number of location-based service zones100within the provided active zone103will need to be reduced for monitoring.

When the quantity of location-based service zones100exceeds a predefined threshold, the active zone filter application124can select a subset of location-based service zones100to be monitored. For example, inFIG. 1, the active zone103includes multiple geofences109and multiple beacons112. However, only a subset of geofences109and beacons112are being monitored (e.g.,109a,109b,109c,112a,112b). These geofences109and beacons112are defined by solid lines while the geofences109and beacons112that are not being monitored (e.g.,109d,109e,112c,112d) are defined by dashed lines.

The active zone filter application124may select the subset of location-based service zones100according to factors, including, for example, current location of the client device106, location-based service zones recently entered into or exited by the client device106, device speed, device direction, user interaction history, aggregate user interaction history, and/or any other factor as can be appreciated. Using the example ofFIG. 1, the active zone filter application124has selected a group of location-based service zones100that are clustered in the same general area of the active zone103. In this example, the subset of location-based service zones100may be determined according to their respective proximity to the client device106and/or the direction and/or speed of movement of the client device106.

In some embodiments, the active zone filter application124may determine that the subset of location-based service zones100needs to be updated. For example, the active zone filter application124may determine that the client device location127has changed such that one or all of the location-based service zones100are no longer preferred with respect to the other location-based service zones100within the active zone103that are not being monitored. As such, the active zone filter application124may re-evaluate the location-based service zones100and generate a new subset of location-based service zones100within the active zone103. Because the client device106already has data associated with location-based service zones100included in the active zone103, the client device106will not have to connect with the at least computing device118while still within the geographic region of the active zone103. In some embodiments, the active zone filter application124may determine that that the subset of location-based service zones100need to be updated in response to detecting that the client device106has exited a particular location-based service zone100, thereby changing the device location127of the client device106.

In some embodiments, the active zone filter application124may detect that the client device106has exited the active zone103and may request an updated active zone103from the active zone management system115. For example, the active zone filter application124may detect that the client device106has exited the active zone103in response to detecting that the client device106has exited a particular location-based service zone100that may border the geographic boundaries of the active zone103.

In the following discussion, a general description of the system and its components is provided, followed by a discussion of the operation of the same.

With reference toFIG. 2, shown is a networked environment200according to various embodiments. The networked environment200includes a computing environment203and a client device106which are in data communication with each other via a network121. The network121includes, for example, the Internet, intranets, extranets, wide area networks (WANs), local area networks (LANs), wired networks, wireless networks, cable networks, satellite networks, or other suitable networks, etc., or any combination of two or more such networks.

Various applications and/or other functionality may be executed in the computing environment203according to various embodiments. Also, various data is stored in a data store206that is accessible to the computing environment203. The data store206may be representative of a plurality of data stores206as can be appreciated. The data stored in the data store206, for example, is associated with the operation of the various applications and/or functional entities described below.

The components executed on the computing environment203, for example, include an active zone management system115, and other applications, services, processes, systems, engines, or functionality not discussed in detail herein. The active zone management system115is executed to create active zones103for a particular computing device. An active zone103is a dynamically sized geographic area that contains a comprehensive set of location-based service zones100that are selected with respect to a particular client device106and/or user account. In some embodiments, the active zone management system115can create and dynamically size an active zone103to include location-based service zones100that are specific to a particular client device106and client device limitations. The active zone management system115can identify location-based service zones100within the created active zone103. The active zone management system115can be configured to update and modify the active zones100based at least in part on a change in client device location, time restrictions associated with the location-based service zones100, additions of location-based service zones100, removal of location-based service zones100, change in location-based service zone parameters, and/or any other factor as can be appreciated.

The data stored in the data store206includes, for example, device data209, provider data212, aggregate interaction data215, and potentially other data. The device data209includes data associated with different client devices106. The device data209may include user account information218, location data221, active zone(s)103, and/or any other data associated with a client device106.

The user account information218may comprise information related to one or more user accounts associated with the client device106. For example, the user account information218may include a username, a first and last name, and/or other identify information. The location data221represents a geographic location of the client device106. The location data221may be determined according to geographic coordinates provided to the computing environment203from the client device106. In other embodiments, the location data221may be determined according to recently triggered and/or broken location-based service zones100by the client device106. For example, when a client device106enters and/or exits a particular location-based service zone100, the client device106may be configured to send a trigger event notification227to the computing environment203. As such, the location data221can be determined according to the geographic parameters of the triggered location-based service zone100.

The active zone(s)103may include parameters for the active zones103for the particular client device106that contain the comprehensive set of location-based service zones100specifically selected for the particular device106in view of the device limitations, whether a service associated with a location-based service zone100is user-targeted (e.g., a single user) or broadly targeted (e.g., multiple users), an active status of a particular location-based service zones100, an opt-in status by the client device106for the respective service, and/or any other factor as can be appreciated.

The provider data212includes data associated with the providers of the location-based service zones100. The provider data212includes geofence(s)109, beacon(s)112, and/or any other data associated with the providers. The geofence109represents the virtual geographic boundaries related to the services of the provider. The geofence109includes geofence parameters230and/or any other type of data associated with the geofence109. The geofence parameters230may include one or more coordinates associated with the geographic location, a radius of the interior area, perimeter specifications for non-circular areas, messages to be presented to the user of a client device106one a client device is within the boundary (e.g., “Sale at XYZ Store. Stop in and receive 50% off one item.”), an active time, an active date, a unique token identifier, and/or other parameters associated with the geofence109.

The beacon(s)112represent the devices configured to broadcast wireless signals. The beacon(s)112include beacon parameters233that include the beacon identifier that a client device106can use to access the wireless signal broadcasted from the beacon112when the client device106is within the range to receive the broadcasted signal.

The aggregate interaction data215includes data associated with the interaction history of multiple users. For example, as location-based service zones100are triggered, the active zone management system115and/or other application executed within the computing environment203may log user interaction associated with each of the triggers. However, while a user may trigger a particular location-based service zone100, the user may not interact with the services associated with the location-based service zone100(e.g., purchase product). The aggregate interaction data215may include data associated with multiple users and may be used to determine a probability that a user may interact with a particular location-based service zone100. For example, if that there are two different location-based service zones100in a particular geographic area, the aggregate interaction data215may indicate that more users interact with the location-based service zone100associated with service A than interact with the location-based service zone100associated with service B. In some embodiments, the aggregate interaction data215may be included with the active zone data117provided to the client device106. The client device106can use the aggregate interaction data215as a factor in selecting a subset of location-based service zones100to monitor from an active zone103.

The client device106may be configured to execute various applications such as an active zone filter application124, a client application239, and/or other applications. The client application239may be executed in a client device106, for example, to access network content served up by the computing environment203and/or other servers, thereby rendering a user interface241on the display236. To this end, the client application239may comprise, for example, a browser, a dedicated application, etc., and the user interface241may comprise a network page, an application screen, etc. The client device106may be configured to execute applications beyond the client application239such as, for example, email applications, social networking applications, word processors, spreadsheets, and/or other applications.

The active zone filter application124is executed to select a subset of location-based service zones100included in an active zone103received from the active zone management system115according to various embodiments of the present disclosure. Some geographic regions may contain a dense amount of location-based service zones100. When the active zone filter application124receives an active zone103containing more location-based service zones100than are supported by the client device106, the active zone filter application124may select a subset of location-based service zones100included in the received active zone103according to a variety of factors such as, for example, current location of the client device106, recently broken location-based service zones100by the client device106, device speed, device direction, user history, aggregate user history, and/or any other factor as can be appreciated. In some embodiments, the active zone filter application124may assign a score to each of the location-based service zones100included in the received active zone103based at least in part on the above factors and filtering rules251. The location-based service zones100can be ranked and the highest ranked location-based service zones100within the device-supported threshold can be included in the subset of location-based service zones100to be monitored. The active zone filter application100may also determine when to update the subset of location-based service zones100and/or request a new active zone103from the active zone management system115.

The client device106may store various data in a local data store243. The data stored in the location data store243may comprise for example, monitoring data246, active zone data117, interaction history249, filtering rules251, location data221, client support data254, and/or other data. The monitoring data246includes data associated with the subset of location-based service zones100within an active zone103that are being monitored at a particular instance. The monitoring data246includes the subset data253, which can include one or more coordinates associated with the geographic location, a radius of the interior area, perimeter specifications for non-circular areas, messages to be presented to the user of a client device106when a client device106is within the boundary (e.g., “Sale at XYZ Store. Stop in and receive 50% off one item.”), an active time, an active date, a unique token identifier, a beacon identifier that a client device106can use to access the wireless signal broadcasted from the beacon112when the client device106is within the range to receive the broadcasted signal, and/or any other parameter data associated with the selected subset of location-based service zones100within an active zone103.

The active zone data117includes the data associated with an active zone103created for the client device106and by the active zone management system115. The active zone data117may include geographic parameters defining the geographic region of the active zone103, location-based service zones100, aggregate interaction data215, and/or any other type of data that can be appreciated. The location-based service zones100may comprise the geofence parameters230and/or beacon parameters233for the location-based service zones100that were included in the active zone103created by the active zone management system115.

The interaction history249includes data associated with prior triggers and interactions with location-based service zones100. For example, the interaction history249may include data related to whether or not a user had an interaction with a service upon entering and/or exiting a particular location-based service zone100; for example, when a location-based service zone100was associated with a particular store. If the user associated with the client device106purchased an item at the store, the interaction history249would indicate the purchase of the item with respect to the location-based service zone100.

Likewise, if the user did not purchase an item at the store, the interaction history249may indicate the lack of the purchase at the store. The interaction history249may be used by the active zone filter application124in determining the subset of location-based service zones100within the received active zone103to monitor. In some embodiments, the interaction history249may include information pertaining to previously broken location-based service zones (e.g., exiting or entering a geofence parameter, no longer within distance to receive broadcasted beacon signal, etc.). This information can be used to estimate the direction, speed, and/or location of the client device at a given time.

The filtering rules251comprise rules associated with selecting the subset of location-based service zones100. In some embodiments, the filtering rules251may comprise algorithms such as a ranking algorithm, for example, for determining a priority of the location-based service zones100within the active zone103. For example, the filtering rules251may comprise weights to assign for various features associated with each location-based service zone100. Based on the assigned weights, the location-based service zones100that are identified within a created active zone103may be ranked and the highest ranked location-based service zones100that are within the maximum threshold supported by the client device106may be selected for the subsets.

In one embodiment, the filtering rules251may include weights to assign according to a level of probability of interaction. For example, if a first location-based service zone100has a higher probability of resulting in a user interaction over a second location-based service zone100according to the interaction history249and/or the aggregate interaction data215, the first location-based service zone100may be assigned a weight that is higher than a weight assigned to the second location-based service zone100. The filtering rules251may further comprise rules that can be applied to determine a distance threshold for considering a particular location-based service zone100. For example, the filtering rules251may indicate a particular distance threshold that a location-based service zone100must meet in relation to the client device location in order to be considered for inclusion in the subset.

The location data221corresponds to the location of the client device106at a particular instance. For example, the location data221may comprise geographic coordinates of the client device106. In other embodiments, the location data221may comprise an estimated location based at least in part on recently triggered and/or broken location-based service zones100. For example, if the client device106exited a particular location-based service zone100, the location data221can be estimated according to the geographic parameters of the particular location-based service zone100.

The device support data254includes a quantity of location-based service zones100supported by the client device106, and/or other features supported by the device. The client device limitations may be imposed by the client device in order to optimize power usage, memory usage, and/or processor usage of the client device106.

Referring now toFIG. 3, shown is a flowchart that provides one example of the operation of a portion of the active zone filter application124according to various embodiments. It is understood that the flowchart ofFIG. 3provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the active zone filter application124as described herein. As an alternative, the flowchart ofFIG. 3may be viewed as depicting an example of elements of a method implemented in the client device106(FIG. 1) according to one or more embodiments.

FIG. 3provides a non-limiting example of the functionality that may be performed by the active zone filter application124with respect to selecting a subset of location-based service zones100(FIG. 2) within an active zone103(FIG. 1) according to various embodiments of the present disclosure.

Beginning with box303, the active zone filter application124receives active zone data117(FIG. 1) from the computing device118(FIG. 1). The active zone data117includes the data associated with an active zone103(FIG. 1) created for the client device106and by the active zone management system115(FIG. 1). The active zone data117may include geofence parameters230(FIG. 2), beacon parameters233(FIG. 2), aggregate interaction data215, and/or any other type of data that can be appreciated. In some embodiments, the active zone data117is received in response to a request for an active zone103by the client device106. In other embodiments, the active zone data117is received without a request for the active zone103. For example, the computing device118may be configured to detect when the client device106has exited a previously created active zone103. Upon detection of the client device106exiting the previously created active zone103, the active zone management system115creates a new active zone103and provides the active zone data117to the client device106.

In box306, the active zone filter application124determines whether a number of location-based service zones100included in the active zone data117meets or exceeds a predefined threshold. In some embodiments, the predefined threshold is defined according to device limitations associated with the client device106. For example, client device A may be able to support twenty (20) location-based service zones and client device B may be able to support one-hundred (100) location-based service zones100. The client device limitations may be imposed by the client device106in order to optimize power usage, memory usage, and/or processor usage of the client device106. If the number of location-based service zones100is within the predefined threshold, the active zone filter application124proceeds to box309. In box309, the active zone filter application124initiates the monitoring of the location-based service zones100within the active zone103by the client device106.

If the number of location-based service zones100exceeds the predefined threshold, the active zone filter application124proceeds to box312. In box312, the active zone filter application124selects a subset of location-based service zones100within the active zone103to monitor. In some embodiments, the client device106may apply a set of filtering rules251, analyze the different location-based service zones100within the active zone103, and select a subset of the location-based service zones100based on factors such as, for example, current location of the client device106, location-based service zones100recently entered into and/or exited by the client device106, device speed, device direction, user history, aggregate user history, and/or any other factor as can be appreciated.

In some embodiments, the active zone filter application124may determine a client device location127according to a broken location-based service zone100that the client device106had been monitoring. By knowing the geographic parameters associated with the broken location-based service zone100, the client device location127can be estimated. In some embodiments, the active zone filter application124may select the subset of location-based service zones100according to a predefined distance from the estimated client device location127. For example, any location-based service zones100that are within fifty (50) yards (yds) from the client device location127may be selected for inclusion in the subset of location-based service zones100.

In some embodiments, the active zone filter application124applies filtering rules251to select the subset of location-based service zones100. For example, the filtering rules251may comprise algorithms such as a ranking algorithm, for example, to determine a priority of the location-based service zones100within the active zone103. In some embodiments, the filtering rules251may comprise weights to assign for various features associated with each location-based service zone100. Based on the assigned weights, the location-based service zones100that are identified within a created active zone103may be ranked, and the highest ranked location-based service zones100that are within the maximum threshold supported by the client device106may be selected for the subset. In another non-limiting example, the filtering rules251may indicate types of location-based service zones100that are not to be monitored. For example, the filtering rules251may indicate that any types of location-based service zones100that relate to coffee shops are to be removed from consideration.

In other embodiments, the active zone filter application124may analyze aggregate interaction data215and select the subset of location-based service zones100according to the aggregate interaction data215. For example, the aggregate interaction data215can be used to determine a probability that user will have an interaction with a particular location-based service zone100based on the interaction data of multiple users.

In some embodiments, the active zone filter application124may determine the speed and/or the direction of the client device106. This information may be used to determine a course associated with the client device106. As such, the subset of location-based service zones100may be selected according to the course associated with the client device106.

After selecting the subset of location-based service zones100, the active zone filter application124proceeds to box315. In box315, the active zone filter application124initiates monitoring of the subset of location-based service zones100from the active zone103. Upon initiating the monitoring of the location-based service zones100, this portion of the active zone filter application124ends.

Turning now toFIG. 4, shown is a flowchart that provides one example of the operation of a portion of the active zone filter application124according to various embodiments. It is understood that the flowchart ofFIG. 4provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the active zone filter application124as described herein. As an alternative, the flowchart ofFIG. 4may be viewed as depicting an example of elements of a method implemented in the client device106(FIG. 1) according to one or more embodiments.

FIG. 4provides a non-limiting example of the functionality that may be performed by the active zone filter application124with respect to prioritizing location-based service zones100(FIG. 1) to include in the active zone103(FIG. 1) when the quantity of location-based service zones100originally identified in the active zone103received from the computing device118(FIG. 1) exceeds the maximum threshold that the client device106can support according to various embodiments of the present disclosure.

Beginning with box403, the active zone filter application124identifies a location-based service zone100included within the active zone103received from the computing device118. At box406, the active zone filter application124analyzes the location-based service zone100and assigns a score to the location-based service zone100according to one or more factors. The one or more factors may include a type of service associated with the location-based service (e.g., retail, delivery, etc.), a distance between the location-based service zone100and a client device location127, a probability that a user interaction will occur based in part on user interaction history249and/or aggregate interaction data215, broken location-based service zones100, client device direction, client device speed, and/or any other factor as can be appreciated.

In some embodiments, the score is determined according to weights defined in the filtering rules251. For example, each factor may be given a particular weight, and the score for the location-based service zone100is based on a sum of weights assigned to each analyzed factor. In one non-limiting example, the location-based service zone A receives a weight of “1” for being within a predefined distance of the client device location127while location-based service zone B receives a weight of “0” for being outside a predefined distance of the client device location127. Further, assume that the probability of a user interaction with location-based service zone B is greater than the probability of user interaction with location-based service zone A, and that the weight assigned to location-based service zone B for the probability of user interaction is “5” while the weight assigned to location-based service zone A for the probability of user interaction is “2.” In this example, the score assigned to location-based service zone A may be “3” while the score for location-based service zone B may be “5.”

In box409, the active zone filter application124determines whether there are other location-based service zones100identified in the active zone103that have not been analyzed and/or given a score. If there are other location-based service zones100, the active zone filter application124returns to box403. Otherwise, the active zone filter application124proceeds to box412. In box412, the active zone filter application124ranks the location-based service zones100according to each respective score. In box415, the highest ranked location-based service zones100within the supported threshold of location-based service zones100are selected to be included in the subset of location-based service zones100for monitoring by the client device106. Upon selecting the subset of location-based service zones100for monitoring, this portion of the active zone filter application124ends.

Referring next toFIG. 5, shown is a flowchart that provides one example of the operation of a portion of the active zone filter application124according to various embodiments. It is understood that the flowchart ofFIG. 5provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the active zone filter application124as described herein. As an alternative, the flowchart ofFIG. 5may be viewed as depicting an example of elements of a method implemented in the client device106(FIG. 1) according to one or more embodiments.

FIG. 5provides a non-limiting example of the functionality that may be performed by the active zone filter application124with respect to modifying the active zones103(FIG. 2) and/or location-based service zones100for a particular client device106according to various embodiments of the present disclosure.

Beginning with box503, the active zone filter application124determines whether the client device106has exited (e.g., broken) a monitored location-based service zone100. If the client device106has exited a monitored location-based service zone100, the active zone filter application124proceeds to box506. Otherwise, the active zone filter application124continues to monitor the location-based service zones100to detect an exit.

In box506, the active zone filter application124estimates a client device location127. In some embodiments, the active zone filter application124estimates the client device location127based on the geographic parameters of the broken location-based service zone100. For example, when the location-based service zone100is detected as being broken in box503, the active zone filter application124can determine the geographic parameters defining the broken location-based service zone100and use the geographic parameters as an estimate of the client device location127. Similarly, if the client device106triggers a new location-based service zone100, the active zone filter application124can estimate a client device location127based at least in part on the geographic parameters of the new location-based service zone100. In some embodiments, the client device106can access geographic coordinates of its location, as can be appreciated.

In box509, the active zone filter application124determines whether the client device106is still within the active zone103. For example, the active zone data117include geographic parameters defining the geographic boundaries of the active zone103. If the client device location127is outside the defined geographic boundaries of the active zone103, the active zone filter application124proceeds to box512. Otherwise, the active zone filter application124proceeds to box518.

In box512, the active zone filter application124requests a new active zone103from the active zone management system115in the computing environment203. In box515, the active zone filter application124receives the new active zone103via the active zone data117transmitted over the network121. In box518, the active zone filter application124selects a new subset of location-based service zones100. The new subset of location-based service zones100can be based at least in part on based on factors such as, for example, current location of the client device106, location-based service zones100recently entered into and/or exited by the client device106, device speed, device direction, user history, aggregate user history, and/or any other factor as can be appreciated. In box521, the active zone filter application124initiates the monitoring of the location-based service zones100in the newly selected subset by the client device106. Once the client device106begins monitoring the new subset of location-based service zones100, this portion of the active zone filter application124ends.

With reference toFIG. 6, shown is a schematic block diagram of the computing environment203according to an embodiment of the present disclosure. The computing environment203includes one or more computing devices118. Each computing device118includes at least one processor circuit, for example, having a processor603and a memory606, both of which are coupled to a local interface609. To this end, each computing device118may comprise, for example, at least one server computer or like device. The local interface609may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated.

Stored in the memory606are both data and several components that are executable by the processor603. In particular, stored in the memory606and executable by the processor603are the active zone management system115, and potentially other applications. Also stored in the memory606may be a data store206and other data. In addition, an operating system may be stored in the memory606and executable by the processor603.

With reference toFIG. 7, shown is a schematic block diagram of the client device106according to an embodiment of the present disclosure. The client device106includes at least one processor circuit, for example, having a processor703, a memory706, and a display236, all of which are coupled to a local interface709. The local interface709may comprise, for example, a data bus with an accompanying address/control bus or other bus structure as can be appreciated.

Stored in the memory706are both data and several components that are executable by the processor703. In particular, stored in the memory706and executable by the processor703are the active zone filter application124, the client application239, and potentially other applications. Also stored in the memory706may be a local data store243and other data. In addition, an operating system may be stored in the memory706and executable by the processor703.

A number of software components are stored in the memory606,706and are executable by the processor603,703. In this respect, the term “executable” means a program file that is in a form that can ultimately be run by the processor603,703. Examples of executable programs may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of the memory606,706and run by the processor603,703, source code that may be expressed in proper format such as object code that is capable of being loaded into a random access portion of the memory606,706and executed by the processor603,703, or source code that may be interpreted by another executable program to generate instructions in a random access portion of the memory606,706to be executed by the processor603,703, etc. An executable program may be stored in any portion or component of the memory606,706including, for example, random access memory (RAM), read-only memory (ROM), hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (CD) or digital versatile disc (DVD), floppy disk, magnetic tape, or other memory components.

Also, the processor603,703may represent multiple processors603,703and/or multiple processor cores and the memory606,706may represent multiple memories606,706that operate in parallel processing circuits, respectively. In such a case, the local interface609,709may be an appropriate network that facilitates communication between any two of the multiple processors603,703, between any processor603,703and any of the memories606,706, or between any two of the memories606,706, etc. The local interface609,709may comprise additional systems designed to coordinate this communication, including, for example, performing load balancing. The processor603,703may be of electrical or of some other available construction.

Further, any logic or application described herein, including the active zone management system115and the active zone filter application124may be implemented and structured in a variety of ways. For example, one or more applications described may be implemented as modules or components of a single application. Further, one or more applications described herein may be executed in shared or separate computing devices or a combination thereof. For example, a plurality of the applications described herein may execute in the same computing device118, or in multiple computing devices118in the same computing environment203, or in the same client device106.