Granted Claim 19 · Software element G
Executable location + time logic
Strong — temporal software publicly documented
Granted claim language
Verbatim · US12039568B2 · Claim 19only 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 limitation requires instructions that evaluate a temporal condition in conjunction with the geographic condition, and that permit sending only within the specified time or period. Time must therefore be a computed input to the same gating logic, not merely metadata recorded alongside a location.
Publicly disclosed Woosmap functionality
Woosmap documents two distinct executable temporal pathways. The first is predictive: device location and a destination are supplied to travel-time computation, producing an ETA and supporting isochrone-based regions defined by travel time rather than distance. The second is historical: each visit carries an arrival time, a departure time and a duration, and temporal distribution across clusters is used in deriving Zones of Interest, from which approximate home and office locations are identified.
- Travel-time and ETA computation
- Isochrone regions defined by time
- Visit arrival and departure times
- Visit duration
- Temporal clustering
- Time-derived Zone of Interest classification
ETA / isochrone pathway
- 01Device location
- 02Destination
- 03Travel-time calculation
- 04ETA
- 05Time-based geofence
- 06Event
Historical temporal processing
- 01Visit
- 02Arrival time
- 03Departure time
- 04Duration
- 05Temporal cluster
- 06Zone of Interest
Execution environment and component attribution
- Woosmap service / API
Travel-time and isochrone computation is documented at API level.
- Woosmap SDK
Visit timing and temporal clustering are documented device-side SDK operations.
- Consumer mobile device
Visit records and clusters are documented as stored and processed on the device.
Public evidence
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 (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
Woosmap publicly demonstrates software processing of temporal information in conjunction with geographic information. The existence of ETA, duration and temporal-clustering software does not by itself establish that the precise time or period condition recited in Claim 19 is implemented in a particular notification workflow.
Evidentiary status and matters for further review
Claim-element correspondence
Deployment confirmation required
Matters for further review
Is a time or period condition specified by or on behalf of the consumer device, and evaluated together with the geographic condition, in a relevant United States deployment?