US12039568B2View granted patent ↗

Dependent claims

Dependent claim subject matter

Claims 2–9 depend from independent Claim 1. Claims 11–18 and 20–27 track the same subject matter in method and computer-readable-medium form. Each dependent claim incorporates every limitation of its parent claim; the additional limitation is reproduced verbatim below and is not assessed in isolation from the parent claim.

2

Dependent claim 2

Notifications relating to retail information

STRONG PUBLIC CORRESPONDENCE

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the notifications relate to retail information.”

02 — Recorded position

The public Woosmap record describes location-triggered notification workflows in a retail context, including store-based geofencing and drive-to-store engagement material. The subject matter of the additional limitation corresponds to functionality expressly documented, subject to confirmation that a given deployment sends retail information rather than operational or logistical messaging.

03 — Public source relied upon

3

Dependent claim 3

Previously collected data including purchases made by the user

DEPLOYMENT-LEVEL CONFIRMATION REQUIRED

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the previously collected data includes purchases made by the user of the secondary user device.”

02 — Recorded position

Purchase history resides in the retailer customer-data or engagement platform rather than in the Woosmap Geofencing SDK. The documentation reviewed establishes event transmission into Salesforce Marketing Cloud, Braze, Batch and Airship, but does not itself establish the content of the profile data held in those systems. Confirmation requires deployment-level evidence.

03 — Public source relied upon

4

Dependent claim 4

Previously collected data including search queries as to goods or services

NOT ESTABLISHED ON PRESENT PUBLIC RECORD

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the previously collected data includes search queries initiated by the secondary user device in respect of goods and/or services.”

02 — Recorded position

The Geofencing SDK documentation reviewed does not disclose collection of search-query data in respect of goods or services. No correspondence is recorded on the present public record.

03 — Public source relied upon

No public source in the reviewed record supports correspondence with this additional limitation.

5

Dependent claim 5

Previously collected data including prior purchases at specified locations

DEPLOYMENT-LEVEL CONFIRMATION REQUIRED

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the previously collected data includes prior purchases made by the secondary user device at one or more geographical locations specified by the primary user device.”

02 — Recorded position

The limitation requires transaction history associated with retailer-specified geographic locations. Woosmap documentation establishes retailer-specified monitored locations, but the association of purchase history with those locations is a function of the retailer customer-data layer and is not established by the public Woosmap record.

03 — Public source relied upon

6

Dependent claim 6

Secondary user devices configured to send messages to the primary user device

DEPLOYMENT-LEVEL CONFIRMATION REQUIRED

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the one or more secondary user devices are further configured to send messages to the primary user device.”

02 — Recorded position

Return-path messaging is an application-level capability of the host application rather than a documented function of the Geofencing SDK. The SDK does transmit device-side events to server-side platforms; whether the integrated application affords consumer-to-retailer messaging requires deployment-level confirmation.

03 — Public source relied upon

7

Dependent claim 7

Reservation of products or scheduling of services

PARTIAL CORRESPONDENCE

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the one or more secondary user devices are further configured to reserve one or more products, or schedule one or more services, offered for sale by a retail establishment associated with the geographical location.”

02 — Recorded position

Woosmap retail material describes click-and-collect and order-collection workflows, and third-party interview material attributes order placement and preparation triggering to a Woosmap-enabled workflow. Correspondence is partial: ordering and reservation functions are performed by the retailer application, not by the SDK.

03 — Public source relied upon

8

Dependent claim 8

Effecting a payment transaction

NOT ESTABLISHED ON PRESENT PUBLIC RECORD

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the one or more secondary user devices are further configured to effect a payment transaction.”

02 — Recorded position

No correspondence is asserted. The public material reviewed does not establish that any Woosmap-integrated application effects a payment transaction.

03 — Public source relied upon

No public source in the reviewed record supports correspondence with this additional limitation.

9

Dependent claim 9

Automatic notification upon determination of presence in the specified region

DIRECT PUBLIC EVIDENCE

01 — Verbatim additional limitation

“A computer implemented system according to claim 1, wherein the primary user device automatically sends notifications to one or more secondary user devices upon determining that the one or more secondary user devices are located within the specified region of the geographical location associated with the primary user device.”

02 — Recorded position

Woosmap documents automatic generation of geofence entry events on determination that the device is within a monitored region, and automatic transmission of those events to engagement platforms configured to issue notifications. The documented behaviour corresponds directly to the subject matter of the additional limitation.

03 — Public source relied upon

Claims 11–18

Dependent on independent Claim 10 (method form)

Claims 11 to 18 track the subject matter of claims 2 to 9 in method form: retail information, previously collected purchase information, search-query data, purchases associated with geographic locations, consumer-to-retailer messaging, reservation or scheduling, payment transactions and automatic region-based notification. The correspondence analysis and the diligence gaps identified for claims 2–9 apply equally, with the additional matter of attributing each recited step to a performing actor in a given deployment.

Claims 20–27

Dependent on independent Claim 19 (computer-readable medium form)

Claims 20 to 27 track the same subject matter in computer-readable-medium form. Analysis focuses on the instructions distributed within the SDK and the integrated engagement platform, and on where those instructions are stored and executed in United States deployments.

Recorded positions describe technical correspondence between publicly disclosed functionality and the language of the granted claims. They are not determinations of infringement, validity or scope, each of which requires claim construction and deployment-level evidence.