Implementing dynamically modifiable geo-fencing based on conditions of cellular networks

By dynamically adjusting the radius of the cellular network geofence, the alarm delay problem caused by changes in cellular network connectivity is solved, ensuring that the alarms of mobile devices in the area of ​​sufficient signal strength are transmitted in a timely manner, and the response speed and security are improved.

CN118923136APending Publication Date: 2024-11-08PALO ALTO NETWORKS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380029170.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-21
Filing Date
2023-03-07
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Changes in cellular network connectivity lead to delays or missed alerts when crossing geofences, resulting in delays in response actions and even security issues.

Method used

Using dynamically modified geofencing services, adjust the radius of geofen based on observed cellular network conditions, dynamically adjust the geofen by recording error conditions and analyzing signal strength data to ensure that the equipment is in an area with sufficient signal strength and ensure the alarm. Timely generation and transmission.

Benefits of technology

Effectively reduces alarm delays, improves the response speed of geofences across events, and ensures security and accuracy, especially when cellular network signals are unstable.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923136A_ABST
    Figure CN118923136A_ABST
Patent Text Reader

Abstract

A geo-fence service establishes an initial geo-fence for monitoring devices connected to a cellular network. Upon receiving a notification generated and transmitted by a device spanning the geo-fence, the service determines a positional difference of the device at the time of notification generation and transmission based on coordinates included in the notification. A location difference satisfying a criterion indicates that the geo-fence corresponds to a geo-location where cellular network connectivity is poor. The service modifies the geo-fence radius based on available signal strength data and implements the resulting modified geo-fence. After the first radius modification, the service determines a network connectivity quality at a geographic location corresponding to the internally tracked shadow geo-fence, and modifies the geo-fence radius if the device coordinates indicate that the shadow geo-fence corresponds to an area with sufficient connectivity. The geo-fence radius modification will continue until the geo-fence returns to its initial configuration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication networks and services utilizing location information.

[0002] Geofencing is a technology that establishes a virtual perimeter to monitor the location of a device relative to a geographic area. With geofencing, radio frequency identification (RFID), Wi-Fi, global positioning system (GPS) data, or cellular data is used to monitor the location of a device that has location services enabled. One or more actions, such as an alert, can be defined that are triggered when it is determined that a device has crossed the virtual perimeter established by geofencing. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Various aspects of the disclosure may be better understood by reference to the following drawings.

[0004] Figure 1 A conceptual diagram of dynamically modifying a geofence based on observed cellular network conditions.

[0005] Figure 2 is a conceptual diagram of a geofence undergoing geofence modification to return to its initial configuration.

[0006] Figure 3 is a flow diagram of example operations for implementing dynamically modifiable geo-fencing for devices connected to a cellular network.

[0007] Figure 4 is a flow diagram of example operations for modifying geo-fence parameters based on cellular network signal strength.

[0008] Figure 5 is a flow diagram of example operations for returning from modified geofence parameters to original geofence parameters based on observed cellular network connectivity.

[0009] Figure 6 is a flow diagram of example operations for creating and maintaining a heat map indicating cellular network signal strength.

[0010] Figure 7 An example computer system with a dynamically modifiable geo-fencing service is depicted. DETAILED DESCRIPTION

[0011] The following description includes example systems, methods, techniques, and program flows that embody various aspects of the present disclosure. However, it should be understood that the present disclosure can be implemented without these specific details. For example, in an illustrative example, the present disclosure relates to implementing dynamically modifiable geo-fencing on a software-defined wide area network (SD-WAN) edge router, where the edge router is a mobile / cellular router. Aspects of the present disclosure may also be applied to other devices connected to a cellular network or mobile / cellular routers that are not configured as SD-WAN edge routers. In other instances, well-known instruction instances, protocols, structures, and techniques are not shown in detail in order not to confuse the description.

[0012] the term

[0013] For efficiency and ease of explanation, this description uses abbreviated terms related to cloud technology. When referring to "the cloud", this description refers to the resources of the cloud service provider. For example, the cloud may cover the cloud service provider's servers, virtual machines, and storage devices. More generally, customer-accessible cloud service provider resources are resources owned / managed by the cloud service provider entity and accessible through a network connection. Typically, access is made through an application programming interface or software development kit provided by the cloud service provider.

[0014] Unless specifically stated otherwise, use of the phrase "at least one of" before a list with the conjunction "and" should not be viewed as an exclusive list and should not be interpreted as a category list with one item from each category. A clause reciting "at least one of A, B, and C" may be violated by only one listed item, a plurality of listed items, one or more items in the list and another unlisted item.

[0015] Overview

[0016] Due to variations in cellular network connectivity, it can be challenging to effectively provide geo-fencing services for mobile network devices (e.g., mobile / cellular routers). Alerts generated by geo-fence entry / exit events may be delayed or missed due to poor or temporary loss of network connectivity at the location corresponding to the geo-fence. If a mobile network device crosses a geo-fence at a location with poor network connectivity, such as due to a temporary network outage, delivery of an alert indicating an exit / entry event to a service monitoring the location of the mobile network device over the cellular network may be delayed. As a result, response actions taken by customers or other owners of mobile network devices to resolve geo-fence crossing events may also be delayed. In some instances, delays in alerts triggered by geo-fence entry or exit events may pose security issues.

[0017] A geofence service is described herein for implementing dynamically modifiable geofences based on conditions of an observed cellular network. For geofences provided for an SD-WAN, the geofence service can be executed as part of an SD-WAN controller to implement geofences on edge routers including mobile / cellular routers. The geofence service establishes a geofence with an initial configuration that includes a center location of the geofence and a radius relative to the center location. An alert sent to the geofence service by a device that crosses the geofence indicates two device locations captured by the device's location-based service (e.g., with GPS coordinates): the location where the alert was generated, which substantially corresponds to a location along the geofence; and the location where the alert was transmitted to the geofence service via a cellular network. When the device has a sufficiently strong connection to the cellular network, it is expected that these locations are substantially similar. However, location differences indicating a delay between alert generation and transmission may be attributed to poor or no signal of the cellular network across the geofence. The geofence service records an error condition when such a difference is identified. Once a specified number of error conditions (i.e., 1 to N error conditions) are recorded, a modification of the geofence radius is triggered. The geofence service modifies the geofence radius based on available signal strength data such that the modified geofence corresponds to a location where the signal strength of the cellular network is increased.

[0018] After this first radius modification, the geofence service determines network connectivity based on similar analysis of the device location between alert generation and transmission, and identifies delays in internal alert transmissions at locations corresponding to multiple internally tracked "shadow" geofences. These geofences are considered shadow geofences because they overlay actual, implemented geofences, but are used only internally by the geofence service and are not presented to or configured by the customer. Shadow geofences are configured to have a radius that can be between the value of the modified geofence radius and the initial geofence radius, so that subsequently triggered geofence modifications are used to restore the geofence radius to or closer to the radius specified in the initial configuration of the geofence. When a device crosses a shadow geofence and triggers an alert to the geofence service, if the device location change between alert generation and transmission for the shadow geofence is small (i.e., not an error condition), the geofence service modifies the radius of the actual geofence based on the radius of the crossed shadow geofence. Geofence modifications triggered based on shadow geofences are ongoing until the radius returns to its original value and the initially configured geofence can be implemented again because the corresponding connectivity to the cellular network is restored.

[0019] Example diagram

[0020] Figure 1is a conceptual diagram of dynamically modifying a geo-fence based on observed conditions of a cellular network. Mobile router 101 connects to cellular network 106 and creates Wi-Fi network 104. Mobile router 101 creates Wi-Fi network 104 by converting cellular signals of cellular network 106 into Wi-Fi signals. Wi-Fi network 104 is a wireless local area network (WLAN) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 technical standard. Cellular network 106 can be a 4G network, a 4G Long Term Evolution (LTE) network, a 5G network, etc. Mobile router 101 allows Wi-Fi compatible devices within range of Wi-Fi network 104 to connect to Wi-Fi network 104 and access the Internet through cellular network 106. Therefore, Internet access relies on mobile router 101 having a strong enough signal for cellular network 106.

[0021] The mobile router 101 is configured and managed by a controller 103. The controller 103 may be an SD-WAN controller executing in a cloud environment (e.g., as a cloud-based service). The controller 103 and the mobile router 101 may communicate bidirectionally via a cellular network 106 to which the mobile router 101 is connected. A dynamically modifiable geo-fence service 105 (hereinafter referred to as "service 105") is executed as part of the controller 103. The service 105 has configured the mobile router 101 with a geo-fence configuration 121, by which a geo-fence 114 is implemented for the mobile router 101. The mobile router 101 has previously selected its location-based service 117 for geo-fencing, such as by downloading software as part of configuring the mobile router 101 as an edge router managed by the controller 103. The geo-fence configuration 121 may be downloaded as part of this initial configuration of the mobile router 101. The location-based service 117 is hereinafter referred to as performing geo-fence operations related to the mobile router 101 (e.g., detecting geo-fence exit events).

[0022] The geo-fence configuration 121 indicates the parameters 115 of the geo-fence 114 (hereinafter referred to as "geofence parameters 115"), which include the reference point 110 and the radius 102. Figure 114 as having a value of R. The geofence configuration 121 may also specify a geofence exit event (i.e., crossing the geofence 114 to exit the virtual fenced area) as a trigger condition that, if met, triggers an alert to the service 105. After the geofence configuration 121 is downloaded to the mobile router 101, if the mobile router 101 exits the "geo-fenced" area enclosed by the geofence 114, the location-based service 117 will alert the service 105 of the geofence exit event. The geofence parameters 115 and other aspects of the geofence configuration 121 may have been specified by a customer, such as the owner of the mobile router 101. For example, the customer may have input the geofence parameters 115 and an indication of an exit event as an alert trigger into a user-facing component of the service 105, after which the service 105 generates the geofence configuration 121 based on the input configuration parameters and pushes the geofence configuration 121 to the mobile router 101 and any other served devices. As another example, a customer may have installed geofence configuration 121 on service 105, so geofence configuration 121 may be pushed to mobile router 101 and any other served devices.

[0023] The service 105 also maintains and / or has access to signal strength data 109 for the cellular network 106. The service 105 may have obtained the signal strength data 109 from an Internet service provider (“ISP”) that provides Internet access via the cellular network 106. Alternatively or additionally, the service 105 may construct and maintain the signal strength data 109 when a monitored device including the mobile router 101 transmits an alert including its current location and corresponding signal strength to the service 105. The signal strength data 109 may be maintained locally by the service 105, or may be stored in an external location accessible to the service 105 (e.g., a repository maintained on an external server such as a cloud server).

[0024] Figure 1 Annotated with a series of letters AD. These letters represent operational stages. Although these stages are in order for this example, these stages illustrate an example to aid understanding of the present disclosure and should not be used to limit the claims. Subject matter falling within the scope of the claims may vary in order and in some operations.

[0025] In stage A, a geo-fence exit event for mobile router 101 triggers the generation of alert 111, which is transmitted to service 105 via cellular network 106. When mobile router 101 crosses geo-fence 114, location-based service 117 detects the geo-fence exit event. Geofence configuration 121 further configures location-based service 117 to determine and include data corresponding to the generation of alert 111 and the transmission of alert 111 via cellular network 106. When alert 111 is generated locally by location-based service 117, location-based service 117 captures first coordinates 108A of mobile router 101 (e.g., using GPS), which first coordinates 108A correspond to the location where mobile router 101 exits geo-fence 114, and includes first coordinates 108A in alert 111. In a scenario such as Figure 1 In some of the depicted examples, location-based service 117 may also determine signal strength 112, which indicates the strength of the cellular network 106 signal measured by mobile router 101 at a location corresponding to first coordinate 108A. Location-based service 117 may generate alert 111 with first coordinate 108A and signal strength 112 as data. Prior to transmitting alert 111 to service 105 over cellular network 106, location-based service 117 captures second coordinate 108B of mobile router 101, second coordinate 108B corresponding to the location of mobile router 101 when alert 111 was transmitted over cellular network 106. Location-based service 117 may add second coordinate 108B as metadata to alert 111.

[0026] Under expected conditions of cellular network 106 (where mobile router 101 has a sufficiently strong connection to cellular network 106), first and second coordinates 108A-B should be substantially similar due to an insignificant delay between generating and transmitting alert 111. However, if the signal measured by mobile router 101 is weak or non-existent at the location corresponding to the geofence exit event (i.e., indicated by first coordinate 108A), then there may be a delay between the local generation of alert 111 and the transmission of alert 111 over cellular network 106. Including coordinates indicating the location of mobile router 101 when alert 111 was generated and transmitted facilitates analyzing whether there is such a delay, which is performed in stage B.

[0027] At stage B, service 105 receives and analyzes alert 111 based on criteria 107 for modifying geofence 114. Modifying a geofence refers to redefining the geofence by modifying its radius. Criteria 107 indicates one or more criteria that, if met, triggers modification of geofence 114. Criteria 107 may include at least a first threshold corresponding to a distance between locations corresponding to alert generation and transmission; a distance exceeding the threshold indicates that insufficient signal strength of cellular network 106 may be causing a delay between generation and transmission of the alert. Service 105 identifies first and second coordinates 108A-B from alert 111 and calculates a distance between them for evaluation against the first threshold indicated by criteria 107. If the distance exceeds the threshold, as is assumed in this example, service 105 records an error condition (e.g., in a data structure maintained for recording error conditions).

[0028] To prevent premature modification of the geofence due to a temporary loss or reduction in signal strength, the criteria 107 may further include a second threshold corresponding to a maximum count of error conditions that should be recorded before triggering a geofence modification. As an example, the criteria 107 may further provide that the geofence should be modified after more than five error conditions have been recorded. Thus, after recording an error condition, the service 105 evaluates the count of error conditions that have been recorded against the second threshold; if the second threshold is exceeded, a geofence modification is triggered due to the satisfaction of the criteria 107. This example assumes that an error condition recorded after the distance between the first and second coordinates 108A-B exceeds the error condition count threshold triggers the service 105 to modify the geofence 114.

[0029] As part of handling the alert 111, the service 105 also determines the signal strength 112 included in the alert 111 and updates the signal strength data 109 with an indication of the signal strength 112 and the corresponding location (i.e., the first coordinate 108A). In some examples, the signal strength data 109 can be maintained in a heat map, where different tones in the heat map correspond to different categories of signal strength. In this case, the service 105 can determine which category the signal strength 112 corresponds to, and classify the signal strength 112 into the determined category by associating the signal strength 112 with the corresponding tones indicating the category. In other examples, the signal strength measurements can be classified based on an evaluation against a classification standard when the signal strength data 109 is input, where each category is associated with a tones to be used to represent the signal strength. As another example, the signal strength data 109 can include multiple location indications (e.g., GPS coordinates) and the associated signal strength at each location. Each signal strength data 109 can be marked, labeled, or otherwise annotated with a signal strength category determined by the service 105 when inserted into the data set. For example, each signal strength data 109 may indicate GPS coordinates, a signal strength measurement determined from a received alert, and a label indicating a category into which service 105 classified the signal strength measurement.

[0030] At stage C, the service 105 determines a modification to the geofence 114 by modifying the radius 102 based on the signal strength data 109 for the cellular network 106. The service 105 determines a reduced geofence radius based on the analysis of the signal strength data 109, where the reduced radius is the next largest geofence radius corresponding to a location of sufficient signal strength. The service 105 initializes a radius value R' with the value of the radius 102, determines whether those signal strength data 109 corresponding to locations at a distance R' from the reference point 110 correspond to a sufficiently strong signal for the cellular network 106, and decrements the value of R' if the signal strength is insufficient. Analysis of the signal strength data 109 having decrementing values ​​R' is performed until the value of R' yields a finding of sufficient signal strength. As an example, if the radius 102 has a value of 1000 meters, and R' is to be decremented by 50 meters, the service 105 may determine and analyze those signal strength data 109 corresponding to locations 950 meters from the reference point 110, 900 meters from the reference point 110, and so on. Upon determining that radius R' corresponds to a location of sufficient signal strength, service 105 sets a modified radius 119 of geofence 114 with the value of R'.

[0031] Whether the signal strength of the cellular network 106 is sufficient may be based on criteria evaluated by the service 105 for a subset of the signal strength data 109 that corresponds to a geographic location bounded by a geofence of radius R'. For example, the service 105 may maintain a threshold indicating that a signal strength value is considered sufficient and that a signal strength value that fails to exceed the threshold is considered insufficient. As another example, if the signal strength data 109 is represented by a heat map, the service 105 may maintain an indication of a hue corresponding to a signal strength that is considered sufficient (e.g., a color representing a signal strength measurement that exceeds -85 dBm). Because the available signal strength measurements corresponding to a location of a geofence of radius R' may vary or be limited, the service 105 may determine that the signal strength corresponding to the radius R' is sufficient if a certain percentage, proportion, etc. of the associated signal strength measurements are considered sufficient. As an example, for a percentage of 80%, the service 105 may determine a subset of the signal strength data 109 corresponding to a location that is a distance R' from the reference point 110 and evaluate the measurements to determine whether at least 80% of the measurements indicate sufficient signal strength. In addition, service 105 can maintain a tolerance value so that locations corresponding to geofences with a radius of R' plus or minus the tolerance value are considered in the evaluation. The tolerance value can be expressed in the units in which R' is measured or in the units in which the location is indicated in the signal strength data, such as meters or seconds for latitude / longitude, respectively.

[0032] At stage D, the service 105 transmits an update to the mobile router 101 indicating the modified geo-fence parameters 113, which includes the modified radius 119. The update that the service transmits to the mobile router 101 may be a new configuration, such as an updated version of the geo-fence configuration 121 indicating the modified geo-fence parameters 113, or an update to the existing geo-fence configuration 121. Once the update has been received, the location-based service 117 installs the update including the modified geo-fence parameters 113 to the mobile router 101. The geo-fence implemented for the mobile router 101 will then have a radius given by the modified radius 119.

[0033] Figure 2 is a conceptual diagram of a geofence undergoing geofence modification to return to its initial configuration. Figure 2 The service 105 is depicted as implementing a geo-fence 214 for the mobile router 101, the geo-fence 214 having the same Figure 1The determined modified geofence parameters 113. The geofence configuration 121 also includes a plurality of radii 221 for a plurality of "shadow geofences." The geofences corresponding to the plurality of radii 221 are referred to as shadow geofences because these geofences are not customer-facing and trigger an alert for internal use by the service 105 when crossed. In addition, the shadow geofences overlay the geofence 214, or the geofence being implemented and defined by the modified geofence parameters 113. Each radius in the plurality of radii 221 is represented by the radius R with which the geofence was initially configured. The service 105 can transmit the plurality of radii 221 to the mobile router 101 as included as reference Figure 1 The modified geo-fence parameters 113 are described as part of the update so that a corresponding shadow geo-fence is implemented for internal alerts after the initial geo-fence modification.

[0034] To illustrate, Figure 2 An exemplary value for each radius 221 and a corresponding set of shadow geofences are depicted. Shadow geofence 205A corresponds to a geofence with a radius of R (i.e., radius 102). Shadow geofence 205B corresponds to a geofence with a radius value of 75% of R. Shadow geofence 205C corresponds to a geofence with a radius value of 50% of R. If mobile router 101 crosses any of shadow geofences 205A-C, a reference to the geofence 205A-C is generated. Figure 1 The coordinates and signal strength of the generated and transmitted notification are transmitted to the service 105 to help modify the geo-fence based on the observed connectivity with the cellular network 106. In contrast, if the mobile router 101 crosses the geo-fence 214, the generated alert can be presented to the client, and the geo-fence can be modified again based on the analysis of the location of the mobile router 101 indicated in the alert, as shown in reference Figure 1 described. Figure 2 The remainder of the description relates to the former case, where the mobile router 101 crosses one of the shadow geofences 205A-C.

[0035] Figure 2 Annotated with a series of letters AC. These letters represent operational stages. Although these stages are in order for this example, these stages illustrate an example to aid understanding of the present disclosure and should not be used to limit the claims. Subject matter falling within the scope of the claims may vary in order and in some operations.

[0036] In phase A, the mobile router 101 triggers the generation and transmission of an alert 211 to the service 105 for a geofence exit event for one of the shadow geofences 205A-C. Figure 1105 , the alert 211 includes two coordinates captured by the location-based service 117 (e.g., using GPS). The first coordinate 208A determined by the location-based service 117 indicates the location of the mobile router 101 when the mobile router 101 exited a corresponding one of the shadow geofences 205A-C and triggered the generation of the alert 211. The second coordinate 208B determined by the location-based service 117 indicates the location of the mobile router 101 just before the alert 211 was transmitted to the service 105 via the cellular network 106. The alert 211 also includes an indication of the signal strength 212 measured by the mobile router 101.

[0037] At stage B, the service 105 receives and analyzes the alert 211. The service 105 determines whether the criteria 107 for geofence modification are met based on the data / metadata of the alert 211. The service 105 also determines the signal strength 212 included in the alert 211 and updates the signal strength data 109 with an indication of the signal strength 212 and the corresponding location (i.e., the first coordinate 208A), similar to the reference 208. Figure 1 When the data / metadata of alert 211 is analyzed based on criteria 107, the geofence modification triggered by satisfying criteria 107 is used to return the radius to or closer to the value used for its initial configuration (i.e., radius 102). Thus, criteria 107 may include a first criterion for the initial parameter modification described above and a second criterion for subsequent parameter modifications.

[0038] The service 105 determines the distance between the locations corresponding to the first coordinate 208A and the second coordinate 208B, and evaluates the distance against the threshold indicated by the criteria 107. The threshold against which the distance determined from the internal alert triggered by the shadow geofence exit event is evaluated may indicate the same distance as the threshold employed for the initial distance evaluation described above. However, in this case, the service 105 evaluates the distance between the first and second coordinates 208A-B against the threshold to determine whether the distance is below the threshold, and therefore there is no substantial delay between the generation and transmission of the alert 211. If the distance is below the threshold, then those criteria 107 implemented for the shadow geofence exit event are met.

[0039] This example assumes that the distance between the locations identified by the first and second coordinates 208A-B is below a threshold specified by the criteria 107, which triggers a geofence modification by again modifying the geofence radius. When the mobile router 101 crosses one of the shadow geofences 205A-C and ultimately triggers a geofence modification, the geofence is modified to have a radius corresponding to the radius of the shadow geofence that was crossed. For example, if the mobile router 101 crosses the shadow geofence 205B, the service 105 determines the modification to the radius based on a radius having a value of 75% of the initial radius R. The service 105 determines the value of the modified radius 213 based on the radius of the shadow geofence that was crossed and triggered the alert 211, Figure 2 208A”. Service 105 may determine a value for modified radius 213 based on a distance between reference point 110 and the location identified by first coordinate 208A or based on an indication of a shadow geofence included in alert 211.

[0040] At stage C, service 105 transmits an update to mobile router 101 indicating modified geofence parameters 223, including modified radius 213. The update that service 105 transmits to mobile router 101 may be a new configuration, such as an updated version of geofence configuration 121 indicating modified geofence parameters 223, or an update to an existing geofence configuration 121. Mobile router 101 installs the update including the modified geofence parameters 223, and geofence 214 is thereby modified to have a modified radius 213 having a value of R". Gradual geofence modification, aided by internal alerts triggered by crossing shadow geofences 205A-C, may continue until connectivity is restored at the original geofence location and the geofence radius may be restored to the radius 102 with which it was configured.

[0041] Figure 1-2 Examples of dynamically modifiable geofences are described, where a geofence exit event is a trigger for alert generation and transmission. In other examples, a geofence entry event can be a trigger. In such examples, rather than Figure 1 Restrict geofencing as described and as referenced Figure 2 Rather than implementing a shadow geofence having a radius measured to be smaller than the originally configured radius as described, the geofence may be extended based on the signal strength data during the first geofence modification event. The radius of the shadow geofence subsequently implemented by service 105 may be larger than the radius of the initially configured geofence (e.g., 150% and 175% of the initially configured geofence) such that subsequent geofence modification events serve to gradually restore to the initial geofence.

[0042] Although Figure 1 and Figure 2For simplicity and to aid understanding, the controller 103 is depicted as managing the mobile router 101, but the controller 103 can manage multiple devices (e.g., multiple edge routers). For example, in addition to the mobile router 101, the controller 103 can manage multiple mobile routers and / or other compatible devices that have been loaded. Devices can be grouped according to characteristics, where the characteristics of the device can include a service provider (e.g., an ISP of a cellular network), a device type, an antenna deployment (e.g., an internal antenna or an external antenna), or any other device metadata indicating characteristics that can affect the strength of the connection to the cellular network. The controller 103 can maintain or access metadata for the loaded mobile routers, which includes these characteristics related to cellular network connectivity. In order to configure multiple devices for dynamically modifiable geo-fences, the service 105 pushes the geo-fence configuration 121 to the multiple devices. The service 105 can then receive alerts based on any of these devices crossing the geo-fence, which can originate from any of the multiple devices. The service 105 modifies the parameters of the geofence as described above and transmits the modified geofence parameters to devices having characteristics that are the same or similar (e.g., at least partially the same) as the characteristics of the device from which the alert originated, where similar characteristics are defined as one or more metadata common between the devices.

[0043] Figure 3-6 is a flow chart of example operations for implementing dynamically modifiable geo-fencing based on conditions of a cellular network. For consistency with the previous figures, the example operations are described with reference to a dynamically modifiable geo-fencing service (hereinafter referred to as the "geofencing service"). The names chosen for the program code are not limitations on the claims. The structure and organization of the program may vary depending on the platform, programmer / architect preference, programming language, etc. In addition, the names of code units (procedures, modules, methods, functions, etc.) may vary for the same reasons and may be arbitrary.

[0044] Example operations involve implementing dynamically modifiable geo-fencing for one or more devices connected to a cellular network. The devices may be SD-WAN edge devices connected to the cellular network, such as mobile routers (also referred to as cellular routers) deployed as edge routers. In an implementation of dynamically modifiable geo-fencing for such SD-WAN edge devices, a geo-fencing service is executed as part of an SD-WAN controller.

[0045] In addition, the example operation assumes that the geofence service has access to signal strength data for the cellular network. The signal strength data may have been obtained from an ISP providing the cellular network and / or from monitored devices that periodically transmit signal strength data to the service (e.g., as part of an alert transmitted to the service for a geofence crossing event). The signal strength data indicates the signal strength of the cellular network associated with various geographic locations. For example, the signal strength data may be represented by a signal strength value associated with an indication of a location (e.g., GPS coordinates), which may be a single value or a range of values. As another example, the signal strength data may be represented by an indication of signal quality and an associated location, where the signal strength has been previously mapped to a corresponding indication of signal quality (e.g., by an ISP or service).

[0046] Figure 3 is a flow diagram of example operations for implementing dynamically modifiable geo-fencing for devices connected to a cellular network. Initial geo-fence establishment refers to the initial configuration of a geo-fence implemented for one or more devices connected to a cellular network. The geo-fence may be initially configured by a customer or other owner of one or more devices based on selecting a central location (e.g., a headquarters location) for measuring the geo-fence and a radius of the geo-fence, such as by a user-facing component of an SD-WAN controller on which the geo-fencing service executes.

[0047] In box 301, the geofence service configures a geofence with a first set of parameters. The initial configuration parameters of the geofence include a center point around which the geofence is formed and a radius of the geofence. The geofence parameters may have been specified by the owner of the device being monitored via the geofence. For example, in an implementation of geofencing for an SD-WAN edge router, the geofence parameters may have been entered into a user-facing component of the SD-WAN controller on which the geofence service executes. As another example, the geofence configuration including the geofence parameters may have been installed on the geofence service (e.g., by being installed on a controller). The geofence configuration including the initial configuration parameters may also specify whether a geofence entry or geofence exit should trigger an alarm. The geofence configuration to be installed should further specify that a notification generated in response to crossing a geofence will include two coordinates captured by the device's location-based service, wherein the first coordinate is captured when crossing the geofence and the second coordinate is captured just before the notification is transmitted to the geofence service over the cellular network.

[0048] In box 303, the geofence service pushes the geofence configuration to the devices to be monitored. Each of the one or more devices to be monitored is a device connected to a cellular network, such as a mobile / cellular router. The geofence service can communicate with each device to be monitored (e.g., via a cellular network). For example, in an implementation where the geofence service is executed as part of an SD-WAN controller, each device to be monitored has been loaded with the controller. The geofence service pushes the geofence configuration to each loaded device. When the geofence configuration is installed to each device, the device's location-based service can then monitor the device location and detect geofence entry / exit events that trigger notification generation. The geofence radius can be configured as a parameterized value that is initialized with the value specified at box 301.

[0049] In box 305, the geofence service waits for a notification triggered by a device crossing a geofence. The notification triggered by the device crossing a geofence is transmitted to the geofence service via a cellular network. In box 307, the geofence service receives a notification that includes device coordinates corresponding to the generation and transmission of the notification. The installation of the geofence configuration configures the device to utilize location-based services to capture different coordinates as part of handling geofence crossing events and include the coordinates as data and / or metadata in the generated notification. The first coordinate included in the notification indicates the location of the device when the geofence was crossed and the generation of the notification was triggered. The second coordinate indicates the location of the device just before the notification was transmitted to the geofence service via the cellular network. The geofence service can determine these two coordinates from the notification based on corresponding data and / or metadata fields.

[0050] At block 309, the geofence service determines the distance between the device locations corresponding to the generation and transmission of the notification. The geofence service can calculate the distance based on using a distance formula with each coordinate as an input. If the device's connection to the cellular network was strong enough when the device crossed the geofence, the locations should be substantially similar. A poor signal from the cellular network received by the device may result in a delay between the local generation of the notification and the transmission of the notification to the geofence service over the cellular network, which would be captured as a difference between the coordinates indicating continued movement of the device after crossing the geofence but before sufficient signal was obtained and the notification could be transmitted.

[0051] At block 311, the geofence service determines whether the distance exceeds a threshold. The threshold corresponds to the distance traveled between notification generation and transmission, which, if exceeded, may indicate poor connectivity with a cellular network in the geographic location at the geofence site, which results in a delay in notifying the geofence service that the geofence has been crossed. If the distance does not exceed the threshold, operations continue at block 305, where the geofence service waits to receive another notification. If the distance exceeds the threshold, operations continue at block 313.

[0052] At block 313, the geofence service logs an error condition for the geofence. The geofence service may maintain an indication of the error conditions logged for the geofence in a data structure. The data structure may indicate or be associated with the configured geofence parameters to distinguish error conditions logged for different geofence configurations (e.g., different radius values ​​for the geofence).

[0053] At block 315, the geofence service determines whether the number of error conditions logged for the geofence exceeds a threshold. The geofence service may implement an additional threshold that indicates a maximum number of error conditions allowed before modifying the geofence, such as due to repeated delays in the transmission of notifications indicating geofence crossing events. The threshold may specify that one or more error conditions are allowed. The geofence service evaluates the number of error conditions logged for the geofence against this threshold. If the number of error conditions does not exceed the threshold, operation continues at block 305, where the geofence service waits to receive another notification. Otherwise, if the number of error conditions exceeds the threshold, operation continues at block 317.

[0054] At block 317, the geofence service modifies the parameters of the geofence based on the signal strength of the cellular network. Figure 4 Example operations are described for modifying geo-fence parameters based on cellular network signal strength.

[0055] Reference now Figure 4 At block 401, the geofence service retrieves signal strength data for a geographic area that at least partially overlaps with the geofence area. The signal strength data indicates the signal strength of the cellular network at various locations that at least partially overlap / include the geofence area. If a provider of the cellular network (e.g., an ISP) has made the signal strength data available to the geofence service, the geofence service may retrieve the signal strength data from the provider. Alternatively or additionally, as described with reference to Figure 6 As described, when the geo-fencing service receives a notification including a signal strength measurement, the geo-fencing service can construct and maintain a set of signal strength data. The signal strength data can be stored in a map such that the signal strength measurements are stored in association with their corresponding geographic locations. As another example, the signal strength data can be maintained in a heat map, where the signal strength measurements have been classified into one of a plurality of categories indicating signal strengths with corresponding representations (e.g., hues) in the heat map.

[0056] At block 402, the geofence service initializes the geofence radius R for signal strength analysis with the value of the initially configured geofence radius. n As an example, if the geofence is initially configured with a radius of 1000 meters, then R nThe value of is initialized to a value of 1000. The geofence service may determine the initial geofence radius setting based on a geofence configuration installed thereon and initially provided to the monitored device.

[0057] At block 403, the geo-fence service determines the region corresponding to the radius R. n The signal strength at the location of the geo-fence. Corresponding to a radius of R n The location of a geofence is defined by a radius R measured from the center point. n The geographic location (e.g., in terms of coordinates) of the boundaries formed by the geofence. The geofence service determines the boundaries corresponding to the radius R. n The signal strength data stored in association with these locations of the geo-fence, for example, corresponds to a position with a radius of R n The geofence service may further determine signal strength data for a set of GPS coordinates corresponding to a geofence. Because signal strength data may not be available for a specific location corresponding to the geofence, but may be stored in association with nearby locations, the geofence service may further determine signal strengths for locations within a given distance of the location corresponding to the geofence. For example, the geofence service may determine signal strength data already stored for locations corresponding to the geofence and locations within 1 degree of latitude and / or longitude of those locations. The determined signal strengths may be represented as a value (e.g., decibel-milliwatts (dBm)) and / or a label, tag, etc. indicating signal quality. Alternatively or additionally, if the data is represented using a heat map, the determined signal strengths may be represented using a color indicating signal quality.

[0058] At block 405, the geo-fence service determines the region corresponding to the radius R. nWhether the signal strength of the geo-fence is sufficient. The geo-fence service analyzes the determined signal strength data based on one or more criteria for determining that the signal strength in the area corresponding to the geo-fence is sufficient. If the majority (e.g., 85%) of the signal strength data determined to correspond to the geo-fence has a specified quality level or meets a signal strength threshold, the criterion may indicate that the signal strength is sufficient, where the value of "majority" is a configurable percentage, fraction, etc. As an example, the criterion may indicate that the signal strength is sufficient if at least 85% of the signal strength measurements are between 0 and -90 dBm and / or are associated with a label, mark, etc. indicating good or sufficient signal quality. For example, if the signal strength data is maintained in a heat map, the mark / label indicating good or sufficient signal quality may indicate a color (e.g., green) for signal strength measurements classified as "good". The geo-fence service in this example will determine whether at least 85% of the signal strength data determined to correspond to the geo-fence is marked / labeled with a color indicating good or sufficient signal strength. If the signal strength is insufficient, the operation continues at box 407. If the signal strength is sufficient, the operation continues at box 409.

[0059] At block 407, the geo-fencing service sends R n The value of R is modified by the specified amount. n The value of R n Increase or decrease by a configurable amount (e.g. 50 or 100 meters). n Whether it is incremented or decremented depends on whether the geofence exit or entry event triggers the notification. For example, if the geofence exit event triggers the notification, R n Operations continue at 403 with another determination and analysis of signal strength in the area corresponding to the geo-fence having the modified radius value.

[0060] At block 409, the geo-fencing service uses R n The Geofence service uses R n Update the geofence radius by the value so that the geofence will consist of a radius of R measured from the center point. n The geofence service may use R to update the radius value by generating a configuration update to update the radius value, or by generating a new geofence configuration and transmitting the updated or new geofence configuration to the monitored device. n As an example, if the geofence radius is indicated as a parameterized value in the geofence configuration, the configuration update may update the geofence radius by R n The value of is indicated as the parameter value of the geo-fence radius. As a result, the monitored device will be updated after the configuration for geo-fence update is installed if it crosses the modified radius R nThe geofence service may also determine the monitored device for which the geofence was modified based on the metadata of the device from which the notification originated. For example, the geofence service may transmit the configuration for the geofence modification to the device that sent the notification and any other devices associated with the same service provider as the device.

[0061] Figure 5 is a flow chart of example operations for returning to original geofence parameters from modified geofence parameters based on observed cellular network connectivity. After modifying the parameters of a geofence implemented for a device connected to a cellular network in response to determining that the geofence corresponds to a location with poor signal strength, it may be desirable to return to the original geofence configuration once sufficient signal has been restored. The example operations describe returning to the original geofence configuration in accordance with the embodiment of the present invention. Figure 3-4 The modified geofence radius is then returned to the original geofence configuration.

[0062] At box 501, the geofence service establishes one or more shadow geofences with corresponding radii. The geofence service can establish a shadow geofence by transmitting a new geofence configuration or an update to an existing geofence configuration to the monitored device, wherein the new geofence configuration or the update to the existing geofence configuration indicates one or more radii of the shadow geofence and the center point at which the radii are measured. The shadow geofence is so called because the alert generated by the device crossing the shadow geofence is for internal use by the geofence service and is not configured or presented to the customer or owner of the device. In addition, the radius of the shadow geofence can be expressed relative to the radius of the initially configured geofence (e.g., as a fraction, percentage, etc.) and can include reference information such as the radius of the shadow geofence. Figure 4 The determined modified radius is a value between the original geofence radius, resulting in an inner tracked geofence that can be considered a "shadow" of the implemented geofence. As an example, the shadow geofence radius can correspond to 50%, 75%, and 100% of the original radius, or for a geofence initially configured with a 1000 meter radius, it can correspond to 500 meters, 750 meters, and 1000 meters.

[0063] In box 503, the geofence service waits for a notification triggered by a monitored device crossing a shadow geofence. Shadow geofences override actual implemented geofences, so a device crossing any geofence will trigger a notification to the geofence service. The geofence service can distinguish between shadow geofence and actual geofence crossing events to determine whether to indicate the geofence crossing event to the customer / owner of the device or to analyze data / metadata associated with the crossing event to help modify the parameters of the implemented geofence. For example, a notification transmitted from a device may indicate a geofence that was crossed, from which the geofence service can determine whether the indicated geofence is an actual geofence or a shadow geofence. As another example, the geofence service can determine the distance from a center point to the location where the geofence indicated in the notification was crossed (e.g., based on applying a distance formula), and determine whether the distance corresponds to the radius of the shadow geofence or the radius of the actual implemented geofence. If the notification indicates that an actual geofence was crossed rather than a shadow geofence, the geofence service, as described in reference to FIG. Figure 3 The notification is handled as described beginning at block 307 .

[0064] At block 505, the geofence service receives a notification including device coordinates corresponding to the generation and transmission of the notification. The notification generated and transmitted to the geofence service when the device crosses a shadow geofence includes data / metadata similar to the notification generated after crossing an actual configured geofence (e.g., as described above with reference to 307). Thus, the notification includes first coordinates determined by the location-based service of the corresponding device when the geofence was crossed, and second coordinates determined when the notification was transmitted over the cellular network.

[0065] At box 507, the geofence service determines the distance between the device locations corresponding to the generation and transmission of the notification, such as by calculating the distance between the coordinates using a distance formula. At box 509, the geofence service determines whether the distance exceeds a threshold. The geofence service can evaluate the distance between the generation and transmission of the notification corresponding to the shadow geofence against the same threshold as the evaluation used to trigger the initial geofence modification, or can maintain additional thresholds for evaluation associated with the shadow geofence. Using this evaluation, a distance that does not exceed the threshold indicates that the quality of the connection to the cellular network at the location corresponding to the shadow geofence is sufficient, and the geofence can be modified to correspond to the shadow geofence. If the distance exceeds the threshold, the operation continues at box 503, where the geofence service waits to receive another notification. If the distance does not exceed the threshold, connectivity to the cellular network may have improved, and the operation continues at box 511.

[0066] At box 511, the geofence service determines whether the parameters of the shadow geofence correspond to the parameters of the geofence originally configured. If the shadow geofence has the same radius as the geofence initially configured before the geofence parameters were modified, and there was no substantial delay between the generation and transmission of the notification, sufficient connectivity at the location of the initially configured geofence may have been restored. The geofence service can make this determination based on information included in the notification. For example, the geofence service can determine whether the distance between the location where the geofence was crossed (i.e., as indicated by the corresponding coordinates) and the center point is substantially equal to the initial geofence radius. If the parameters of the shadow geofence being crossed correspond to the parameters of the geofence initially configured, operation continues at box 517. Otherwise, the geofence is another shadow geofence, and operation continues at box 513.

[0067] In box 513, the geofence service updates the radius of the implemented geofence with the radius value of the shadow geofence. The geofence service updates the geofence radius using the radius value of the shadow geofence to modify the implemented geofence again. As an example, in the case where a geofence exit event triggers a notification, if the radius of the implemented geofence is 500 meters and the device crosses a shadow geofence with a radius of 750 meters, the radius of the geofence to be implemented is modified from 500 meters to 750 meters. The geofence service can update the geofence radius by generating a configuration update to update the radius value, or by generating a new geofence configuration and transmitting the updated or new geofence configuration to the monitored device. As an example, if the geofence radius is indicated as a parameterized value in the geofence configuration, the configuration update can indicate the value of the shadow geofence radius as the parameter value of the geofence radius.

[0068] At box 517, the geofence service reverts to implementing the geofence with the original parameters. Returning to the previous example, if the geofence was initially configured with a radius of 1000 meters, the geofence service returns the radius of the implemented geofence to 1000 meters. The geofence service can generate a new geofence configuration or geofence configuration update that is transmitted to the monitored device indicating the original geofence radius and indicating that the shadow geofence should no longer trigger notifications. For example, the geofence service can disable the shadow geofence trigger for the device in the configuration update.

[0069] After returning to the initially configured geofence implementation, upon receiving subsequent notifications from devices crossing the geofence, the geofence service may perform additional geofence modifications, as described in reference to Figure 3-5 Specifically, the geofence service may modify the repeated reference for the first subsequent geofence Figure 3-4analysis described, and then if connectivity to the cellular network is as in reference Figure 5 The improved configuration described above restores the geofence to the initially configured geofence. Thus, a dynamically modifiable geofence is being implemented for one or more devices, where geofence modifications are informed based on the device's connectivity to a cellular network.

[0070] Additionally, the evaluation of a received notification and / or any resulting geofence modifications may be implemented as a synchronous operation. If the geofence service receives another notification while evaluating a notification and performing any parameter modifications, such as Figure 3-5 As described in the example operation of , the geofence service can queue the notification so that the corresponding evaluation and parameter modification are performed when the ongoing evaluation is completed. Queuing the received notifications for synchronous evaluation and parameter modification ensures that the notifications are handled in the order in which they are received, thereby ensuring that the error conditions recorded are accurate and preventing conflicting configuration updates from being delivered to the device for which the geofence is implemented.

[0071] Figure 6 is a flowchart of example operations for creating and maintaining a heat map indicating cellular network signal strength. As described above, a geofence service can modify the radius of a geofence based on data indicating the signal strength of a cellular network at various locations so that the geofence corresponds to an area with sufficient signal strength to transmit a notification triggered by a geofence crossing event to the geofence service via the cellular network. The signal strength data can be obtained from an ISP or other provider of a cellular network. Alternatively or additionally, an implementation can utilize signal strength data obtained directly from a device for which the geofence is being implemented. When configuring a device to notify the geofence service upon entering or exiting a geofence crossing, whether an actual geofence or a shadow geofence, the geofence service can also configure the device to include the signal strength of the connection to the cellular network in the generated alert (e.g., as data or metadata for the alert). As now described, the geofence service can utilize the signal strength data to construct a heat map indicating signal strength over a geographic area corresponding to the geofence, or to enhance an existing heat map with new data reflecting observed network conditions.

[0072] At block 601, the geofence service initializes a heat map to visually represent signal strength at various locations. Initializing the heat map may include defining ranges of signal strength measurements (e.g., in dBm) that indicate signal quality, and assigning a color to each range represented by the heat map. As an example, the geofence service may initialize the heat map with three signal strength measurement ranges that correspond to signal qualities that may be considered good, acceptable, and poor, such as the following ranges: -85 dBm and lower, between -85 dBm and -100 dBm, and -100 dBm and higher, respectively. Example colors that may be assigned to the signal strength measurement ranges are red (for a range indicating poor signal quality), yellow (for a range indicating acceptable signal quality), and green (for a range indicating good signal quality).

[0073] At block 603, the geofence service receives an alert from a device that has crossed a geofence. Figure 3 and Figure 5 As described, the alert may correspond to a geofence entry / exit event for an actual geofence or a shadow geofence. As described above, the alert includes an indication of the device location corresponding to the alert generation and transmission. The alert data or metadata additionally includes a value reflecting the measured signal strength of the cellular network at the location where the device crossed the geofence or the notification was transmitted to the geofence service. The device on which the geofence is implemented has been configured to determine the measured signal strength based on locally stored data and include the signal strength in the alert triggered by the geofence entry / exit event (e.g., as specified in the geofence configuration installed on the device).

[0074] At box 605, the geofence service determines a signal strength measurement and a corresponding location included in the alert. The geofence service determines the signal strength measurement and the device location based on the corresponding data / metadata fields in the alert. The signal strength measurement can be expressed in decibels or decibel milliwatts, depending on the representation used for the cellular network. The device location determined based on the alert can be the location corresponding to the generation of the alert or the transmission of the alert (referred to as the "first coordinate" and "second coordinate" respectively above), depending on whether the device determines the measured signal strength as part of generating or transmitting the notification.

[0075] At box 607, the geofence service updates the heat map to indicate the signal strength measurement and the corresponding location. The geofence service adds the signal strength measurement to the heat map so that the corresponding visual representation of the signal strength is stored in the entry corresponding to the location. For example, if the signal strength measured at the first location is -113dBm, which falls within the range of differential signal strengths defined for the heat map and corresponds to the color red, the geofence service updates the entry corresponding to the first location with the value -113dBm and the color red as its visual representation. The geofence service may store the signal strength measurements and associated colors determined for each location for entries corresponding to locations within a specific distance of the location (e.g., based on latitude and / or longitude). Returning to the previous example, the geofence service may update the entry in the heat map for the first location with the value -113dBm and the associated color red, and update the entry corresponding to the location within 1 second of the latitude and longitude of the first location. Operations continue at box 603 to continue building the heat map as additional signal strength data is obtained.

[0076] Determining the signal strength data included in the received alert and using the signal strength data to construct a heat map may be as follows: Figure 6 The geofence service may be performed as part of a geofence parameter modification operation as described herein. For example, upon receiving an alert transmitted from a device that has crossed a customer-configured geofence or shadow geofence, the geofence service may determine an indication of the device's location and signal strength data included in the alert. The geofence service may be performed as described herein. Figure 6 Updating the cellular network signal strength heat map with the received signal strength data as described above, and at least partially in parallel or concurrently as described in reference Figure 3-5 Indications of device location are analyzed as described to determine whether to modify parameters of the geofence.

[0077] Although Figure 6Described are example operations for building and maintaining a heat map for storing signal strength measurements tagged or annotated with a signal quality indicator, but implementations may use other representations of signal strength data. For example, a geofence service may maintain or have access to a repository storing associations between locations (e.g., GPS coordinates) and signal strength measurements. The geofence service inserts the location and corresponding signal strength measurement determined based on the received alert into the repository. The service may evaluate each signal strength measurement based on the criteria for marking or marking the measurement, and mark or annotate the location and signal strength measurement accordingly based on the criteria met before inserting into the repository. For example, the geofence service may evaluate the signal strength measurement based on one or more ranges corresponding to the signal quality, as also described at box 601. Once the range into which the signal strength measurement falls is determined, the geofence service marks or annotates the signal strength measurement and location with a signal quality indicator corresponding to the range. Therefore, in this example, each entry in the repository indicates a location, a signal strength measurement corresponding to the location, and a tag / marker indicating the signal strength quality at the location.

[0078] Variants

[0079] The flowchart is provided to aid understanding of the illustration and is not intended to limit the scope of the claims. The flowchart depicts example operations that may be varied within the scope of the claims. Additional operations may be performed; fewer operations may be performed; the operations may be performed in parallel; and the operations may be performed in a different order. For example, referring to Figure 6 , if multiple alarms are received, the operations described in blocks 603-607 may be performed in parallel or concurrently. It will be understood that each block of the flowchart illustration and / or block diagram and the combination of blocks in the flowchart illustration and / or block diagram may be implemented by program code. The program code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable machine or device.

[0080] As will be appreciated, aspects of the present disclosure may be embodied as systems, methods, or program codes / instructions stored in one or more machine-readable media. Thus, aspects may take the form of hardware, software (including firmware, resident software, microcode, etc.), or a combination of software and hardware aspects, all of which are generally referred to herein as "circuits," "modules," or "systems." The functionality presented as individual modules / units in the example illustrations may be organized differently depending on any of the platform (operating system and / or hardware), application ecosystem, interface, programmer preference, programming language, administrator preference, etc.

[0081] Any combination of one or more machine-readable media may be utilized. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable storage medium may be, for example, but not limited to, a system, device, or apparatus that employs any one or combination of electronic, magnetic, optical, electromagnetic, infrared, or semiconductor technologies to store program code. More specific examples (a non-exhaustive list) of machine-readable storage media would include the following: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a machine-readable storage medium may be any tangible medium that is capable of containing or storing a program used by or in conjunction with an instruction execution system, device, or apparatus. A machine-readable storage medium is not a machine-readable signal medium.

[0082] A machine-readable signal medium may include a propagated data signal having machine-readable program code embodied therein (e.g., in baseband or as part of a carrier wave). Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. A machine-readable signal medium may be any machine-readable medium that is not a machine-readable storage medium and that may communicate, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0083] Program code embodied on a machine-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0084] Program code / instructions may also be stored in a machine-readable medium, which may direct the machine to operate in a specific manner so that the instructions stored in the machine-readable medium produce an article of manufacture including instructions for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0085] Figure 7An example computer system with a dynamically modifiable geofence service is depicted. The computer system includes a processor 701 (which may include multiple processors, multiple cores, multiple nodes, and / or implement multithreading, etc.). The computer system includes a memory 707. The memory 707 can be system memory or any one or more of the possible implementations of the machine-readable medium described above. The computer system also includes a bus 703 and a network interface 705. The system also includes a dynamically modifiable geofence service 711. The dynamically modifiable geofence service 711 creates and maintains dynamically modifiable geofences implemented on one or more devices connected to a cellular network, where the geofences can be modified based on conditions of the cellular network identified from data obtained from the device. Any of the foregoing functions may be implemented in part (or in whole) in hardware and / or on the processor 701. For example, the functions may be implemented with a dedicated integrated circuit, in logic implemented in the processor 701, in a coprocessor on a peripheral device or card, etc. In addition, the implementation may include Figure 7 Fewer or additional components not shown (e.g., video cards, audio cards, additional network interfaces, peripheral devices, etc.) are included. Processor 701 and network interface 705 are coupled to bus 703. Although shown as coupled to bus 703, memory 707 may be coupled to processor 701.

[0086] Although various aspects of the present disclosure are described with reference to various implementations and utilizations, it will be understood that these aspects are illustrative and the scope of the claims is not limited to these aspects. In general, the techniques for implementing dynamically modifiable geo-fencing based on conditions of a cellular network as described herein can be implemented with facilities consistent with any one or more hardware systems. Many variations, modifications, additions, and improvements are possible.

[0087] Multiple instances may be provided as a single instance for the components, operations or structures described herein. Finally, the boundaries between the various components, operations and data stores are arbitrary to some extent, and specific operations are described in the context of specific illustrative configurations. Other allocations of functions are foreseeable and may fall within the scope of the present disclosure. In general, the structures and functions presented as separate components in the example configurations may be implemented as combined structures or components. Similarly, the structures and functions presented as single components may be implemented as separated components. These and other variations, modifications, additions and improvements may fall within the scope of the present disclosure.

Claims

1. A method comprising: implementing a first geo-fence having a radius of a first value on a device, wherein the device is connected to a cellular network; based on receiving an alert triggered by the device crossing a first geofence, determining whether a delay associated with receiving the alert satisfies a first criterion for modifying the radius based on a location indication identified in the alert; based on determining that the delay satisfies the first criterion, modifying the radius from the first value to a second value to create a second geo-fence; as well as Implement a second geo-fence for the device.

2. The method of claim 1 further comprising determining a distance between a first and a second location of the device indicated by the location indication, wherein the first location corresponds to a location at which an alert is generated locally on the device and the second location corresponds to a location at which the device transmits the alert via a cellular network, wherein the distance between the first and second locations indicates a delay associated with receiving the alert.

3. The method according to claim 2 also includes recording an error condition for the first geofence based on determining that the distance exceeds a first threshold indicated by a first criterion, wherein determining whether the delay meets the first criterion includes determining at least one of the following: determining whether the distance exceeds the first threshold and determining whether the count of error conditions recorded for the first geofence exceeds a second threshold.

4. The method according to any one of claims 1 to 3, further comprising: based on the modified radius, internally enforcing a plurality of geo-fences having corresponding radii of the plurality of radii on the device, wherein each of the plurality of geo-fences triggers an internal alarm when crossed; determining, based on receiving an internal alert triggered by the device crossing a third geofence in the plurality of geofences, whether a delay associated with receiving the internal alert satisfies a second criterion for modifying the radius; based on determining that the delay satisfies the second criterion, modifying the radius from the second value to a third value to create a third geo-fence; as well as Implement a third geo-fence for devices.

5. The method of claim 4 , wherein determining whether a delay associated with receiving an internal alert satisfies a second criterion comprises determining whether a distance between a first location where the internal alert is generated locally and a second location where the device transmits the alert via a cellular network is below a third threshold, wherein the internal alert indicates the first and second locations.

6. The method of claim 4, further comprising repeating the following operations until the radius returns to the first value: implementing a plurality of geo-fences, receiving an internal alert, determining that the delay satisfies a second criterion, and modifying the radius.

7. A method according to any one of claims 1-6, wherein modifying the radius from a first value to a second value includes analyzing data indicating the signal strength of the cellular network at multiple locations and determining that the signal strength of the cellular network at a first subset of the multiple locations corresponding to the second geo-fence is sufficient.

8. The method of claim 7, further comprising obtaining from the device at least a subset of the data indicative of a signal strength of a cellular network, wherein the alert received from the device comprises a signal strength measurement of the cellular network.

9. One or more non-transitory machine-readable media having program code stored thereon, the program code including instructions for: establishing a first geo-fence having a radius of a first value, wherein the first geo-fence is enforced for devices connected to the cellular network; determining, based on an analysis of device location data identified in a received alert triggered by the device crossing a first geofence, whether a delay in receiving the alert satisfies a first criterion for modifying the radius; based on the determination that the delay satisfies the first criterion, modifying the radius from the first value to a second value to create a second geo-fence; as well as An indication of a second value of the radius is transmitted to the device to implement a second geo-fence for the device.

10. The non-transitory machine-readable medium of claim 9, wherein the device location data indicates a first location of the device when the alert was generated and a second location of the device when the alert was transmitted over the cellular network, and wherein the instructions for determining whether the delay satisfies a first criterion include instructions for determining whether a distance between the first location and the second location exceeds a first threshold, And wherein the program code also includes instructions for recording an error condition for the first geofence based on a determination that the distance exceeds a first threshold, and wherein the instructions for determining whether the delay meets the first criterion include instructions for determining whether the count of error conditions recorded for the first geofence exceeds a second threshold.

11. The non-transitory machine-readable medium of claim 9 or 10, wherein the program code further comprises instructions for returning the radius to the first value based on a determination that connectivity with the cellular network has been restored at a location corresponding to the first geo-fence.

12. An apparatus comprising: processor; as well as A computer readable medium having instructions stored thereon, the instructions being executable by a processor to cause the apparatus to: implementing a first geo-fence having a radius of a first value for one or more devices, wherein each of the one or more devices is connected to a cellular network; based on receiving an alert triggered by a first device of the one or more devices crossing a first geofence, determining whether a delay associated with receiving the alert satisfies a first criterion for modifying the radius based on an indication of a location of the first device identified in the alert; based on the determination that the delay satisfies the first criterion, modifying the radius from the first value to a second value to create a second geo-fence; as well as A second geo-fence is implemented for the one or more devices.

13. An apparatus according to claim 12, wherein the first criterion includes a first threshold, and wherein instructions executable by the processor to enable the apparatus to determine whether the delay satisfies the first criterion include instructions executable by the processor to enable the apparatus to determine whether the distance between the location indications of the first device exceeds the first threshold, wherein the location indications of the first device include an indication of a first location at which an alert is generated locally at the first device and an indication of a second location at which the first device transmits the alert via a cellular network, and wherein the distance is between the first and second locations.

14. The device according to claim 13 further includes instructions executable by the processor to cause the device to record an error condition for the first geofence based on the determination that the distance exceeds a first threshold, and wherein the instructions executable by the processor to cause the device to determine that the delay satisfies the first criterion include instructions executable by the processor to cause the device to determine that the count of error conditions recorded for the first geofence exceeds a second threshold.

15. An apparatus according to any one of claims 12-14, wherein the instructions executable by the processor to cause the apparatus to modify the radius from a first value to a second value include instructions executable by the processor to cause the apparatus to modify the radius based on data indicating the signal strength of the cellular network at multiple locations.