Granted Claim 19 · Software element D
Instructions processing consumer-device location relative to a geographical location
Very strong — publicly documented executable behaviour
Granted claim language
Verbatim · US12039568B2 · Claim 19receive a notification when the one or more secondary user devices are located at a particular location, or within a specified region or distance of a geographical location associated with the primary user device, as specified by the one or more secondary user devices; and
Claim requirement
Technical interpretation — not claim languageThe limitation requires executable instructions that obtain consumer-device location, compare it against a defined location, region or distance associated with the retailer, and produce a notification of that positional state. This is a computational comparison performed by software, not merely the availability of location data.
Publicly disclosed Woosmap functionality
Woosmap documents device-side location acquisition and geofence evaluation. Setup guides document a location-ready callback delivering each computed device location to the host application, and foreground/background execution controls. Region monitoring guides document registration of circular geofences around monitored places, a region-ready callback exposing region state, persisted region and region-log records, and named enter and exit events. Automatic generation of geofences around Woosmap store assets is separately documented.
- Device location callbacks
- Background location monitoring
- Store and POI geofence registration
- Boundary comparison performed on device
- woos_geofence_entered_event
- woos_geofence_exited_event
Publicly documented location-processing chain
- 01Device sensor / OS location service
- 02Woosmap SDK
- 03Location calculation
- 04Geofence comparison
- 05Boundary condition
- 06Software event
Execution environment and component attribution
- Consumer mobile device
Location acquisition and geofence evaluation are documented as device-side operations.
- Woosmap SDK
The SDK carries the location and region monitoring instructions and emits the resulting events.
- Woosmap service / API
Store and POI reference data used to define monitored regions is served by Woosmap APIs.
Source evidence
Published Woosmap code extractsView technical evidence＋
public class WoosLocationReadyListener implements Woosmap.LocationReadyListener {
public void LocationReadyCallback(Location location) {
onLocationCallback(location);
}
}Computed device location surfaced by SDK instructions to host-application code.
View original ↗Woosmap.getInstance().addGeofence(id, latLng, 100, "circle");Programmatic definition of a monitored region of specified radius.
View original ↗public class DataRegion: RegionsServiceDelegate {
public func updateRegions(regions: Set<CLRegion>) {
// monitored region state
}
}Region monitoring state exposed to the host application on iOS.
View original ↗Public evidence
Woosmap (developers.woosmap.com)
Woosmap Android SDK — Monitor places with custom geofence
Programmatic registration of circular geofences of specified radius, region-ready and region-log listener callbacks exposing boundary state to application code, and persistence and retrieval of region and region-log records on the consumer device.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap iOS SDK — Monitor places with custom geofence
Region service delegate instructions maintaining monitored region state on iOS, together with location, POI and region delegate registration performed at application launch.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Android SDK — Monitor Woosmap Assets guide
Publicly documented geofence event identifiers woos_geofence_entered_event and woos_geofence_exited_event emitted when a monitored asset geofence is crossed.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Geofencing — SDK concepts documentation
Definition of geofencing as monitoring of a geographic area to recognise device presence within a boundary; enter/exit boundary-crossing events; geofences representing a store, competitor store, neighbourhood or other point of interest; automatically generated store geofences; and isochrone (time-based) geofences monitored against estimated time of arrival.
View original source ↗Technical correspondence
The publicly documented instruction set performs precisely the class of operation the limitation describes: acquire device position, compare it against a retailer-associated region, and emit a notification of the resulting state. The correspondence is at the level of software function; whether the region in a deployment is the claimed region, and whether it is specified in the claimed manner, remains separate.
Evidentiary status and matters for further review
Matters for further review
Is the monitored region in a relevant deployment specified by or on behalf of the secondary user devices, as the granted language requires?