Granted Claim 10 · Method step G
Location + time — notifications sent only at the specified time or period
Strong technical correspondence
Granted claim language
Verbatim · US12039568B2 · Claim 10only at a particular time, or within a particular period of time, as specified by the one or more secondary user devices,
Claim requirement
Technical interpretation · not claim languageThe temporal limitation operates cumulatively with the geographic one: satisfaction of the location condition alone is not sufficient. The claim further attributes specification of the time or period to the secondary user devices, so both the temporal gate and its source are material.
Publicly disclosed Woosmap functionality
Woosmap publicly demonstrates temporal processing in more than one technical context. In real time, it documents isochrone and time-based geofences monitored against estimated time of arrival rather than distance alone. Historically, it documents visits with assessable duration, temporal patterns in stored location data, and the time distribution of clusters used to classify Zones of Interest.
- Time-based geofences
- Isochrone geofences
- ETA monitoring
- Visits with assessable duration
- Temporal patterns in stored data
- ZOI temporal clustering
Real-time temporal logic
- 01Current location
- 02Destination
- 03ETA
- 04Time-based geofence
- 05Event
Historical temporal logic
- 01Visits
- 02Start time / end time / duration
- 03Temporal pattern
- 04Zone of Interest
Attribution of the claimed method step
Only where the public evidence permitsWoosmap Distance API
Publicly documentedDocumented as computing isochrone polygons and travel-time reachability.
Woosmap Geofencing SDK
Publicly documentedDocumented as monitoring time-based geofences against ETA and as clustering visits by time distribution.
Secondary-user temporal preference surface
Not establishedNo public document establishes consumer specification of the notification time or period contemplated by the claim.
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 Distance API — Isochrone feature
Computation of isochrone polygons representing areas reachable within a given travel time, supporting time-based rather than purely distance-based catchment logic.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — Visits and Zone of Interest
Detection of when and where a user has spent time (visits) without explicit monitoring; assessment of time spent on each visit; definition of Zones of Interest as places where a user recurrently spends time; and the express statement that, when the Zones of Interest feature is activated, the SDK stores and clusters historical location data on the device for each user, identifying approximate home and office locations from the time distribution of clusters. Also publishes consumer context examples including commuting home and leaving the office for a click & collect order.
View original source ↗Woosmap (woosmap.com blog)
Click & Collect: why brands need it and how geofencing maximises the experience
Retail deployment narrative for ETA-based customer arrival detection, order-readiness workflows and curbside/click-and-collect notification sequences built on geofencing events.
View original source ↗Technical correspondence
Woosmap publicly demonstrates substantial location-plus-time functionality across two independent technical pathways. The remaining question is whether a particular implementation uses that temporal functionality in the specific notification-gating relationship required by Claim 10 — and whether the time or period is specified by the consumer, as the claim recites.
Location + time
Temporal processing is publicly demonstrated in two independent Woosmap contexts — real-time ETA gating and historical visit clustering — which is why this limitation is treated as a focal point of the review.
Evidence of United States performance
Matters for further reviewIs there public evidence that a United States deployment gates notification sending on a temporal condition in combination with the location condition?
United States deployment evidence
Technical correspondence
Claim-element correspondence
Claim satisfaction requires deployment confirmation
Evidentiary limitation
ETA computation and temporal clustering do not of themselves satisfy the requirement that the notification be sent only at a particular time or period specified by the secondary user.