Granted Claim 1 · Element D
Geographic condition — device within a specified region or distance
Very strong
Granted claim language
Verbatim · US12039568B2 · Claim 1receive a notification when the one or more secondary user devices are located at a particular location, or within a specified region or distance in relation to 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 retailer-side system is informed when the consumer device satisfies a defined spatial condition relative to a geographic location tied to that system. The condition may be a point location, a region, or a distance threshold.
Publicly disclosed Woosmap functionality
Woosmap defines geofencing as the monitoring of a geographic area in order to recognise the presence of a device inside a boundary, and documents boundary-crossing events generated when a user enters or exits the geofence. The Android guide publishes the event identifiers woos_geofence_entered_event and woos_geofence_exited_event.
- Circular geofences
- Store geofences
- POI geofences
- Latitude / longitude regions
- Dynamic geofences
- Entry events
- Exit events
Woosmap geographic condition detection
- 01Store
- 02Geofence
- 03Consumer device
- 04Enter / exit detection
- 05Event
Public evidence
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 ↗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 ↗Technical correspondence
The limitation is directed to the receipt of a location-condition signal. Woosmap’s own developer documentation describes precisely that mechanism, names the emitted events, and publishes them as part of the standard SDK surface rather than as a bespoke customer configuration.
Relevance to the granted claim architecture
“Location is not merely analytics within the Woosmap architecture. The monitored location condition can itself generate a software event capable of changing downstream application behaviour.”
Evidentiary status
Matters for further review
The claim recites the region or distance being “as specified by the one or more secondary user devices”. Whether consumer-side specification of the monitored region occurs in particular deployments is not established by the SDK documentation alone.