Granted Claim 10 · Method step D
Receiving notification that the secondary device is at the location, region or distance
Very strong technical correspondence
Granted claim language
Verbatim · US12039568B2 · Claim 10the primary user device is operable to execute computer instruction code to:
receive 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 must receive a machine notification that a consumer device has satisfied a geographic condition expressed relative to a retailer-associated geographical location. The operation is inbound and event-driven: satisfaction of the condition must itself produce a signal.
Publicly disclosed Woosmap functionality
Woosmap defines geofencing as monitoring of a geographic area in order to recognise when a device is inside a boundary, and documents enter and exit events on boundary crossing. Geofences are documented as representing a store, a competitor store, a neighbourhood or another point of interest, including automatically generated store geofences. The Android asset-monitoring guide publishes the event identifiers woos_geofence_entered_event and woos_geofence_exited_event.
- Geofences around stores and POIs
- Automatically generated store geofences
- Boundary-crossing detection
- woos_geofence_entered_event
- woos_geofence_exited_event
- Dynamic and isochrone geofences
Publicly documented event generation
- 01Consumer device
- 02Location monitoring
- 03Store / POI geofence
- 04Boundary condition
- 05Enter / exit event
Attribution of the claimed method step
Only where the public evidence permitsConsumer device
Publicly documentedLocation monitoring is documented as running on the user's device.
Woosmap Geofencing SDK
Publicly documentedDocumented as evaluating the boundary condition and emitting the named enter / exit events.
Woosmap Stores / POI data
Publicly documentedDocumented as the source of monitored store and POI geofences.
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 ↗Woosmap (woosmap.com)
Woosmap Geofencing — commercial use case page
Commercial description of geofencing triggering events on device entry or exit of a monitored region; contextualisation of push notifications at the right time and in the right place; support for distance-based, time-based, ETA/isochrone and recurrent geofences; and retail, geomarketing and offer-targeting use cases including tailoring by where users live or work.
View original source ↗Technical correspondence
This is not merely location analytics. The public SDK documentation demonstrates a computer-implemented process in which satisfying a geographic condition relative to a store or point of interest causes a named software event to be emitted and delivered to the surrounding application. That is the operational shape the step requires: a geographic state producing an inbound signal, rather than a report generated after the fact.
Evidence of United States performance
Matters for further reviewIs there public evidence that store-associated geofence events are generated and received within a relevant United States Woosmap deployment?
United States deployment evidence
Technical correspondence
Evidentiary limitation
The claim conditions the geographic parameters on specification by the secondary devices; the configuring party in a given deployment requires confirmation.