US12039568B2View granted patent ↗

Granted United States Patent · US12039568B2

Open Questions Tracker

What remains to be established, limitation by limitation

Every recited limitation is listed with its current evidence status, the outstanding diligence question, the deployment position where one exists, and direct links to the evidence card and to each original public source. Claim 19 is shown first; the tracker can be switched to Claim 1 or Claim 10, or read across all three.

Download Claim 19 PDF ↓6 limitations require further evidence
Claim
Status

Showing 9 of 27 limitations · sources accessed 26 August 2026

Claim 19 · 19A

A non-transitory computer readable medium including instructions stored therein

DIRECT PUBLIC EVIDENCE

Very strong software-architecture relevance

Open question

Which specific stored instruction set in a given United States deployment — SDK, host application, server component or engagement-platform configuration — is said to carry the complete recited step sequence?

Deployment position

Appears satisfied in Deployment 01 on the public deployment record.

Evidence relied upon

Open the evidence card

19A evidence card →Deployment linkage →Evidence library →

Claim 19 · 19B

Instructions accessing a database of previously collected data

STRONG PUBLIC CORRESPONDENCE

Strong — construction and deployment dependent

Open question

Do not assume that historical location data satisfies every possible construction of "previously collected data". Which data store is accessed, by which instructions, and immediately prior to which sending operation, remains a deployment question.

Deployment position

No deployment case file presently evidences this limitation.

Evidence relied upon

Open the evidence card

19B evidence card →Deployment linkage →Evidence library →

Claim 19 · 19C

Instructions matching notifications for relevance by a matching engine

PARTIAL CORRESPONDENCE

Partial — integration dependent

Open question

In a given deployment, which software component analyses previously collected data regarding the particular user, and does its output determine which notification is sent?

Deployment position

No deployment case file presently evidences this limitation.

Evidence relied upon

Open the evidence card

19C evidence card →Deployment linkage →Evidence library →

Claim 19 · 19D

Instructions processing consumer-device location relative to a geographical location

DIRECT PUBLIC EVIDENCE

Very strong — publicly documented executable behaviour

Open question

Is the monitored region in a relevant deployment specified by or on behalf of the secondary user devices, as the granted language requires?

Deployment position

Appears satisfied in Deployment 01, Deployment 02 on the public deployment record.

Evidence relied upon

Open the evidence card

19D evidence card →Deployment linkage →Evidence library →

Claim 19 · 19E

Instructions applying retailer-entered specifications regarding consumer demographics

PARTIAL CORRESPONDENCE

Partial — deployment dependent

Open question

What specifications does a retailer actually enter in a relevant United States deployment, and are they demographic specifications governing which consumers are preferred to receive notifications?

Deployment position

No deployment case file presently evidences this limitation.

Evidence relied upon

Open the evidence card

19E evidence card →Deployment linkage →Evidence library →

Claim 19 · 19F

Instructions gating the sending operation on the geographic condition

DIRECT PUBLIC EVIDENCE

Very strong — condition evaluated by executable software

Open question

Is the outbound communication in a relevant deployment conditioned on the geographic event, or does the event serve only as one input among several?

Deployment position

Appears satisfied in Deployment 01, Deployment 02 on the public deployment record.

Evidence relied upon

Open the evidence card

19F evidence card →Deployment linkage →Evidence library →

Claim 19 · 19G

Executable location + time logic

STRONG PUBLIC CORRESPONDENCE

Strong — temporal software publicly documented

Open question

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?

Deployment position

Appears satisfied in Deployment 02 on the public deployment record.

Evidence relied upon

  • 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.

  • 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.

  • 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.

Open the evidence card

19G evidence card →Deployment linkage →Evidence library →

Claim 19 · 19H

Instructions automatically disabling and enabling communication

STRONG PUBLIC CORRESPONDENCE

Strong potential correspondence — deployment dependent

Open question

Do the executable instructions in a specific deployment implement the precise claimed condition whereby communication is disabled until the required conditions are satisfied and automatically enabled when they are satisfied?

Deployment position

Appears satisfied in Deployment 02 on the public deployment record.

Evidence relied upon

Open the evidence card

19H evidence card →Deployment linkage →Evidence library →

Claim 19 · 19I

Instructions allowing sending of the relevant notification

DIRECT PUBLIC EVIDENCE

Very strong for software-driven notification capability

Open question

In a relevant United States deployment, is the delivered notification the output of the claimed relevance-matching and conditional-gating instructions, rather than of unrelated campaign logic?

Deployment position

Appears satisfied in Deployment 01 on the public deployment record.

Evidence relied upon

Open the evidence card

19I evidence card →Deployment linkage →Evidence library →

Basis of the recorded status

Each status records the state of the public evidentiary record only, and no limitation recorded here has been construed by counsel. Where a limitation requires deployment-level confirmation or is not established on the present public record, the matter identified is one for further legal and technical review.