US12039568B2View granted patent ↗

Granted United States Patent · US12039568B2

Independent Claim 10

Computer-implemented method

Independent Claim 10 protects a computer-implemented method combining retailer-to-consumer communications, previously collected consumer information, relevance matching, geographic conditions, retailer targeting criteria, temporal conditions and automatic conditional communication.

Granted — United StatesView granted claim ↗
10H

Granted Claim 10 · Method step H

Automatic disabling and enabling of the communication

STRONG PUBLIC CORRESPONDENCE

Strong — deployment dependent

01

Granted claim language

Verbatim · US12039568B2 · Claim 10

such that the communication between the one or more secondary user devices and the primary user device is:

automatically disable when the one or more secondary user devices are not located at the particular location, or located outside the specified region or distance in relation to the geographical location, and outside the specified time, or period of time, to thereby prevent sending of notifications to the one or more secondary user devices, and

automatically enabled when the one or more secondary user devices are located at the particular location, or within the specified region of distance in relation to the geographical location, and at the specified time, or within the specified period of time, to thereby allow sending of notifications to the one or more secondary user devices.

02

Claim requirement

Technical interpretation · not claim language

The concluding limitation requires the communication channel itself to change state automatically as a function of the location and time conditions: disabled — and therefore preventing sending — when the conditions are absent, and enabled when they are satisfied. Automation is express; a manual or operator-driven change of state would not satisfy the limitation.

03

Publicly disclosed Woosmap functionality

Woosmap documents automatic, condition-driven event generation and the transmission of those events into downstream engagement systems. The Marketing Cloud connector is documented as performing the API call to trigger an Entry Event on the named Woosmap events; the Batch integration documents Woosmap events being used as a Custom Event trigger in the Automation and Journey composers; the Braze integration documents custom events tied back to push messaging campaigns.

  • Geofence / ETA condition evaluated automatically
  • SDK event emitted without operator action
  • Connector performs the platform API call
  • Entry event / custom event received
  • Automated journey or campaign action

Condition state 1 — communication disabled

  1. 01Location = false and / or time = false
  2. 02Communication disabled
  3. 03Notification prevented

Condition state 2 — communication enabled

  1. 01Location = true and time = true
  2. 02Communication enabled
  3. 03Notification allowed
04

Attribution of the claimed method step

Only where the public evidence permits

Woosmap Geofencing SDK

Publicly documented

Documented as generating events automatically upon condition satisfaction and as running the connector API call.

Customer-engagement platform

Publicly documented

Documented as receiving entry / custom events and executing automated journey logic.

Communication enable / disable mechanism

Not established

The public record establishes event-driven triggering; it does not establish a channel-state mechanism of the kind the claim recites.

05

Public evidence

Woosmap (developers.woosmap.com)

Woosmap Geofencing SDK — Salesforce Marketing Cloud integration

Transmission of Woosmap Geofencing SDK events to Salesforce Marketing Cloud from four context types — Geofences, POI, Visits and ZOI — to trigger an Entry Event; connector initialisation with EventDefinitionKeys for woos_geofence_entered_event, woos_geofence_exited_event, woos_POI_event, woos_Visit_event, woos_zoi_classified_entered_event and woos_zoi_classified_exited_event; and event data fields including user_properties.[field_name].

View original source ↗

Woosmap (developers.woosmap.com)

Woosmap Geofencing SDK — Batch integration

Transmission of Woosmap Geofencing SDK events from Geofences, POI, Visits and ZOI contexts to Batch as custom events, expressly usable as a Custom Event trigger in the Automation and Journey composers.

View original source ↗

Woosmap (developers.woosmap.com)

Woosmap Geofencing SDK — Braze integration

Transmission of Woosmap Geofencing SDK events from Geofences, POI, Visits and ZOI contexts to Braze as custom events with associated properties, tied back to push messaging campaigns.

View original source ↗
06

Technical correspondence

Public documentation establishes automated condition-driven event generation and transmission into downstream engagement systems. The exact communication enable / disable logic must be confirmed within the relevant deployment. An event trigger is not to be treated as legally identical to the patent's communication enabling and disabling mechanism, although the practical effect — no notification absent the condition, notification upon the condition — is the behaviour the claim describes.

Woosmap operational chain

Geofence / ETA condition → automatic SDK event → engagement entry event → automated journey or action.

07

Evidence of United States performance

Matters for further review

Is there public evidence of automatic enabling and disabling of retailer-to-consumer communication on combined location and time state in a United States deployment?

United States deployment evidence

DEPLOYMENT EVIDENCE REQUIRED

Technical correspondence

STRONG PUBLIC CORRESPONDENCE
← Previous step · 10G — Temporal GatingNext step · 10I — Notification Delivery →