Independent Claim 19

19. A non-transitory computer readable medium including instructions stored therein executable by one or more processors to perform the steps of: establishing communication between a primary user device associated with the retailer and one or more secondary user devices associated with a consumer and sending, by the primary user device, notifications to the one or more secondary user devices, subsequent to accessing a database of previously collected data in respect of users of the secondary user devices;

• Verbatim granted claim language of US12039568B2, reproduced without edit.

Claim 19 is directed to the artefact in which the instructions reside, not to a machine or to a sequence of acts. The limitation requires (i) a non-transitory medium, (ii) instructions stored in that medium, and (iii) executability of those instructions by one or more processors to perform the recited steps. The analysis therefore begins with whether executable software of the relevant character is publicly documented as being supplied, stored and executed at all.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap publishes installation and initialisation documentation for the Geofencing SDK on Android and iOS. The Android guide documents a Gradle dependency on the published SDK artefact and initialisation of the SDK inside the host application's activity; the iOS guide documents CocoaPods and Swift Package Manager distribution and initialisation of the geofence manager from the application delegate. The documentation is addressed to a developer integrating the library into a business-controlled mobile application which is then installed on, and executed by, consumer mobile devices.

• Published package dependency for Android
• CocoaPods / Swift Package Manager distribution for iOS
• Documented initialisation instructions
• Library executed inside the host application process
• Application installed on consumer mobile devices
• Foreground and background execution documented

Documented execution: Woosmap SDK; Retailer application; Consumer mobile device.

• Woosmap SDK — The SDK is the distributed software library containing the relevant instructions.
• Retailer application — Woosmap documents integration of the library into the customer's own mobile application.
• Consumer mobile device — The host application, and therefore the SDK code, is documented as running on the end user's device.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Geofencing SDK — Android setup and initialisation guide ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Distribution of the Geofencing SDK as an installable Android library (Gradle dependency on com.webgeoservices.woosmapgeofencing:woosmap-mobile-sdk), initialisation of the SDK within the host application, a location-ready listener callback delivering computed device locations to application code, and foreground / background execution controls.

  https://developers.woosmap.com/products/geofencing-sdk/android-sdk/guides/setup/

• Woosmap Geofencing SDK — iOS setup and initialisation guide ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Distribution of the Geofencing SDK as an iOS framework via CocoaPods and Swift Package Manager, initialisation of WoosmapGeofenceManager from the application delegate, background monitoring control and tracking enablement instructions executed on the consumer device.

  https://developers.woosmap.com/products/geofencing-sdk/ios-sdk/guides/setup/

• Woosmap Geofencing SDK — Get Started ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Integration of the SDK into a business-controlled mobile application; identification of app-user location; local collection and storage of user locations and visits in the application database; and derivation of Zones of Interest, geographical and temporal clusters and recurrent locations.

  https://developers.woosmap.com/products/geofencing-sdk/get-started/

Woosmap publicly distributes executable SDK components designed to be incorporated into mobile applications and executed on consumer devices. This establishes a directly relevant software-instruction layer for further comparison with the granted computer-readable-medium claim. It is not, and is not presented as, a conclusion that the medium claim is satisfied: Claim 19 requires instructions executable to perform every recited step in combination.

• Evidentiary status: DIRECT PUBLIC EVIDENCE — Very strong software-architecture relevance

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?

• Technical correspondence is documented; the matter identified above remains for confirmatory technical diligence.

… sending, by the primary user device, notifications to the one or more secondary user devices, subsequent to accessing a database of previously collected data in respect of users of the secondary user devices;

• Verbatim granted claim language of US12039568B2, reproduced without edit.

From the software perspective the limitation requires instructions that perform an access operation against persisted data previously collected in respect of the users of the consumer devices. Three executable sub-operations are implied: collection, persistence, and retrieval of the persisted records as an antecedent to the sending operation. The existence of data alone is insufficient — Claim 19 concerns instructions that store and read it.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap documents device-side visit collection, persistence and retrieval. On Android a visit listener callback is documented as invoked when a visit is collected, and stored visit and Zone of Interest records are read from a local database accessor. On iOS a visit service delegate receives collected visits, with documented read and erase operations over the persisted visit and ZOI collections. Woosmap expressly states that, when the Zones of Interest feature is activated, the SDK stores and clusters historical location data on the device for each user, deriving approximate home and office locations from the time distribution of clusters.

• Visit created from device location
• Visit persisted in local storage
• Historical visits retrievable by the application
• Geographical and temporal clustering
• Zone of Interest derived from clusters
• Behavioural context exposed to the host application

Documented execution: Consumer mobile device; Woosmap SDK.

• Consumer mobile device — Woosmap states that historical location data is stored and clustered on the device for each user.
• Woosmap SDK — Visit detection, persistence, clustering and ZOI derivation are documented SDK operations.
• Not established: NOT ESTABLISHED FROM PUBLIC EVIDENCE — Whether a retailer-side database of previously collected consumer data is accessed before notification sending is not addressed by the SDK documentation.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Geofencing SDK — Visits and Zone of Interest ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/visits-zoi/

• Woosmap Android SDK — Monitor user visits guide ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Implementation-level documentation for the SDK's embedded visit algorithm on Android, including persistence of visit records and derivation of Zones of Interest from collected location data.

  https://developers.woosmap.com/products/geofencing-sdk/android-sdk/guides/monitor-user-visits/

• Woosmap iOS SDK — Monitor user visits guide ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Implementation-level documentation for collecting, storing, retrieving and processing visit records and Zone of Interest data on iOS consumer devices.

  https://developers.woosmap.com/products/geofencing-sdk/ios-sdk/guides/monitor-user-visits/

Woosmap's public material documents executable instructions that collect, persist, retrieve and analyse historical location information on the consumer device. That is a software layer of the same technical character as the previously collected data access recited by Claim 19. It does not follow that historical location records are the previously collected data contemplated by the claim, nor that the access occurs in the recited sequence within any deployment.

• Evidentiary status: STRONG PUBLIC CORRESPONDENCE — Strong — construction and deployment dependent

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.

• Technical correspondence is documented; the matter identified above remains for confirmatory technical diligence.

wherein the notifications sent to the secondary user device are matched, by a matching engine, to the user of the secondary user device according to analysis of the previously collected data regarding the user of the secondary user device such that the notifications sent to the secondary user device are relevant to the user of the secondary user device; and further wherein:

• Verbatim granted claim language of US12039568B2, reproduced without edit.

The limitation requires instructions constituting, or invoking, a matching engine which analyses the previously collected data and selects a notification relevant to that particular user. Two software properties must be present: an analysis operation over the prior data, and a selection operation whose output is the notification subsequently sent.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap documents integration instructions that transmit SDK-derived context into customer-engagement platforms. The Salesforce Marketing Cloud integration documents transmission of events from four context types — Geofences, POI, Visits and ZOI — to trigger an Entry Event, with connector initialisation using event definition keys such as woos_geofence_entered_event, woos_POI_event, woos_Visit_event and woos_zoi_classified_entered_event, and event data fields including user_properties.[field_name]. Comparable custom-event transmission is documented for Braze and for Batch, where events are expressly usable as Custom Event triggers in the Automation and Journey composers.

• Named event definition keys
• Contact key association
• user_properties.[field_name] transmitted with events
• Entry Event triggering in Marketing Cloud
• Custom-event triggers in Braze and Batch

Documented execution: Woosmap SDK; Customer-engagement platform.

• Woosmap SDK — Connector instructions within the SDK are documented as emitting the events and associated properties.
• Customer-engagement platform — Event ingestion and journey entry are documented platform-side operations.
• Not established: NOT ESTABLISHED FROM PUBLIC EVIDENCE — No public material establishes instructions performing the complete claimed matching operation over previously collected data.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Geofencing SDK — Salesforce Marketing Cloud integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

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

  https://developers.woosmap.com/products/geofencing-sdk/integration/marketing-cloud/

• Woosmap Geofencing SDK — Braze integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/integration/braze/

• Woosmap Geofencing SDK — Batch integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/integration/batch/

Public documentation establishes a software pathway by which Woosmap-derived user and location context can be transmitted into software capable of determining subsequent customer-engagement actions. The complete claimed matching operation remains integration and deployment dependent. Salesforce Marketing Cloud, Braze and Batch are not characterised here as the claimed matching engine; the public record establishes the transport of context, not the selection logic applied to it.

• Evidentiary status: PARTIAL CORRESPONDENCE — Partial — integration dependent

receive a notification when the one or more secondary user devices are located at a particular location, or within a specified region or distance of a geographical location associated with the primary user device, as specified by the one or more secondary user devices; and

• Verbatim granted claim language of US12039568B2, reproduced without edit.

The limitation requires executable instructions that obtain consumer-device location, compare it against a defined location, region or distance associated with the retailer, and produce a notification of that positional state. This is a computational comparison performed by software, not merely the availability of location data.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap documents device-side location acquisition and geofence evaluation. Setup guides document a location-ready callback delivering each computed device location to the host application, and foreground/background execution controls. Region monitoring guides document registration of circular geofences around monitored places, a region-ready callback exposing region state, persisted region and region-log records, and named enter and exit events. Automatic generation of geofences around Woosmap store assets is separately documented.

• Device location callbacks
• Background location monitoring
• Store and POI geofence registration
• Boundary comparison performed on device
• woos_geofence_entered_event
• woos_geofence_exited_event

Documented execution: Consumer mobile device; Woosmap SDK; Woosmap service / API.

• Consumer mobile device — Location acquisition and geofence evaluation are documented as device-side operations.
• Woosmap SDK — The SDK carries the location and region monitoring instructions and emits the resulting events.
• Woosmap service / API — Store and POI reference data used to define monitored regions is served by Woosmap APIs.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Android SDK — Monitor places with custom geofence ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Programmatic registration of circular geofences of specified radius, region-ready and region-log listener callbacks exposing boundary state to application code, and persistence and retrieval of region and region-log records on the consumer device.

  https://developers.woosmap.com/products/geofencing-sdk/android-sdk/guides/monitor-pois/

• Woosmap iOS SDK — Monitor places with custom geofence ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Region service delegate instructions maintaining monitored region state on iOS, together with location, POI and region delegate registration performed at application launch.

  https://developers.woosmap.com/products/geofencing-sdk/ios-sdk/guides/monitor-pois/

• Woosmap Android SDK — Monitor Woosmap Assets guide ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Publicly documented geofence event identifiers woos_geofence_entered_event and woos_geofence_exited_event emitted when a monitored asset geofence is crossed.

  https://developers.woosmap.com/products/geofencing-sdk/android-sdk/guides/monitor-woosmap-assets/

• Woosmap Geofencing — SDK concepts documentation ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/geofencing/

The publicly documented instruction set performs precisely the class of operation the limitation describes: acquire device position, compare it against a retailer-associated region, and emit a notification of the resulting state. The correspondence is at the level of software function; whether the region in a deployment is the claimed region, and whether it is specified in the claimed manner, remains separate.

• Evidentiary status: DIRECT PUBLIC EVIDENCE — Very strong — publicly documented executable behaviour

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

• Technical correspondence is documented; the matter identified above remains for confirmatory technical diligence.

send notifications to the one or more secondary user devices according to one or more specifications entered by the retailer regarding one or more demographics of the one or more consumers to which one or more notifications are preferred to be sent, wherein the one or more notifications are sent:

• Verbatim granted claim language of US12039568B2, reproduced without edit.

The limitation requires instructions that condition the sending operation on retailer-entered specifications concerning consumer demographics. Two software properties are required: an input mechanism by which the retailer enters those specifications, and evaluation of them at or before the point of sending.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap documents an event payload carrying user-associated properties into customer-engagement platforms. The Marketing Cloud integration documents contact-key association and event data fields including user_properties.[field_name]; Braze and Batch integrations document custom events with associated properties. Audience, segmentation and journey configuration reside in the engagement platform and in the retailer's own application configuration.

• Woosmap event properties
• user_properties.[field_name]
• Contact key association
• Retailer application configuration
• Platform segmentation and journey inputs

Documented execution: Woosmap SDK; Customer-engagement platform.

• Woosmap SDK — Connector instructions transmit events with user-associated properties.
• Customer-engagement platform — Audience, segmentation and journey logic are documented platform capabilities.
• Not established: Retailer application — Which property values are populated is determined by the retailer's own integration code.
• Not established: NOT ESTABLISHED FROM PUBLIC EVIDENCE — No public material establishes retailer-entered demographic specifications of the kind recited.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Geofencing SDK — Salesforce Marketing Cloud integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

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

  https://developers.woosmap.com/products/geofencing-sdk/integration/marketing-cloud/

• Woosmap Geofencing SDK — Braze integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/integration/braze/

A software pathway exists by which retailer-controlled, user-associated attributes travel alongside location events into systems that decide what is communicated. The distinction to preserve is between the documented transport mechanism and the claimed demographic specification: the former is publicly established, the latter is not.

• Evidentiary status: PARTIAL CORRESPONDENCE — Partial — deployment dependent

only when the one or more secondary user devices are located at the particular location, or within the specified region or distance in relation to the geographical location; and

• Verbatim granted claim language of US12039568B2, reproduced without edit.

The limitation is a software gate. The instructions must produce no sending while the device is outside the region, and must permit sending on the boundary condition being satisfied. What matters is that the condition is evaluated by executable code rather than by human judgement.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap's documented region monitoring implements exactly this state machine: no region event is produced while the device remains outside a monitored region; a boundary crossing produces an enter event, and departure produces an exit event. Region logs are persisted, and the events are published under named identifiers used by downstream integrations.

• No event outside the monitored region
• Enter event on boundary crossing
• Exit event on departure
• Region log persistence
• Named events consumed downstream

Documented execution: Consumer mobile device; Woosmap SDK.

• Consumer mobile device — The boundary test is documented as evaluated on the device.
• Woosmap SDK — SDK instructions perform the comparison and emit the event.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Android SDK — Monitor places with custom geofence ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Programmatic registration of circular geofences of specified radius, region-ready and region-log listener callbacks exposing boundary state to application code, and persistence and retrieval of region and region-log records on the consumer device.

  https://developers.woosmap.com/products/geofencing-sdk/android-sdk/guides/monitor-pois/

• Woosmap Geofencing — SDK concepts documentation ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/geofencing/

• Woosmap Android SDK — Monitor Woosmap Assets guide ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Publicly documented geofence event identifiers woos_geofence_entered_event and woos_geofence_exited_event emitted when a monitored asset geofence is crossed.

  https://developers.woosmap.com/products/geofencing-sdk/android-sdk/guides/monitor-woosmap-assets/

The publicly documented software behaves as a conditional gate on geography, which is the technical character of this limitation. Whether the downstream communication in a deployment is itself gated by that event — rather than merely informed by it — is a configuration question.

• Evidentiary status: DIRECT PUBLIC EVIDENCE — Very strong — condition evaluated by executable software

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

• Technical correspondence is documented; the matter identified above remains for confirmatory technical diligence.

only at a particular time, or within a particular period of time, as specified by the one or more secondary user devices,

• Verbatim granted claim language of US12039568B2, reproduced without edit.

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

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

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

Documented execution: Woosmap service / API; Woosmap SDK; Consumer mobile device.

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

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Distance API — Isochrone feature ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  Computation of isochrone polygons representing areas reachable within a given travel time, supporting time-based rather than purely distance-based catchment logic.

  https://developers.woosmap.com/products/distance-api/features/isochrone/

• Woosmap Geofencing SDK — Visits and Zone of Interest ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/visits-zoi/

• Woosmap Geofencing — SDK concepts documentation ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/geofencing/

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: STRONG PUBLIC CORRESPONDENCE — Strong — temporal software publicly documented

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?

• Technical correspondence is documented; the matter identified above remains for confirmatory technical diligence.

such that the communication between the one or more secondary user devices and the primary user device is, automatically disabled 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 or 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.

• Verbatim granted claim language of US12039568B2, reproduced without edit.

This is the decisive software limitation. The instructions must implement a two-state communication gate whose transitions are automatic and determined by the conjunction of the geographic and temporal conditions: disabled — and therefore preventing sending — outside those conditions, and enabled when both are satisfied.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap documents automatic event generation on geographic and ETA conditions, and integration instructions transmitting those events into engagement platforms where they act as triggers. The Marketing Cloud integration documents Entry Event triggering; Braze receives custom events tied to messaging campaigns; Batch expressly documents the events as Custom Event triggers in the Automation and Journey composers. In each case entry into the communication workflow is automatic on receipt of the event.

• Automatic event generation
• Entry Event triggering
• Custom-event triggers
• Automation and journey composers
• Campaign execution on trigger

Documented execution: Woosmap SDK; Customer-engagement platform.

• Woosmap SDK — Event generation and connector transmission are documented SDK operations.
• Customer-engagement platform — Trigger-based journey entry and communication execution are documented platform behaviour.
• Not established: NOT ESTABLISHED FROM PUBLIC EVIDENCE — No public material establishes instructions implementing the recited automatic disabling state in a deployment.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Geofencing SDK — Salesforce Marketing Cloud integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

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

  https://developers.woosmap.com/products/geofencing-sdk/integration/marketing-cloud/

• Woosmap Geofencing SDK — Braze integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/integration/braze/

• Woosmap Geofencing SDK — Batch integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/integration/batch/

A trigger-based architecture in which no event means no communication, and an event automatically initiates communication, is technically analogous to the claimed enable/disable gate. Analogy is not identity: the claim requires the conjunction of location and time, and requires the disabling state as an express software condition.

• Evidentiary status: STRONG PUBLIC CORRESPONDENCE — Strong potential correspondence — deployment dependent

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?

• Technical correspondence is documented; the matter identified above remains for confirmatory technical diligence.

… to thereby allow sending of notifications to the one or more secondary user devices.

• Verbatim granted claim language of US12039568B2, reproduced without edit.

The final limitation requires that, on the conditions being satisfied, the instructions permit and effect delivery of the relevant notification to the consumer device. The software property required is execution of the communication, not merely capability.

• Reading of the granted wording used to frame the search for corresponding public disclosure. No assertion of scope beyond the granted text.

Woosmap's published geofencing material shows notifications generated when users enter or exit monitored places, and describes retail workflows in which arrival detection drives contextual application actions and customer notifications. The engagement-platform integrations document the events driving campaign and journey delivery to the same consumer devices on which the SDK executes.

• Event-driven notification generation
• Contextual application actions
• Campaign and journey delivery
• Delivery to the consumer device

Documented execution: Customer-engagement platform; Retailer application; Consumer mobile device.

• Customer-engagement platform — Journey and campaign execution on event receipt is documented.
• Retailer application — The host application is documented as acting on SDK events, including presenting notifications.
• Consumer mobile device — Delivery target for the resulting communication.

Each statement above traces to the following published documents, cited in full in the evidence library.

• Woosmap Geofencing — commercial use case page ↗

  Woosmap (woosmap.com) · accessed 26 August 2026

  Commercial description of geofencing triggering events on device entry or exit of a monitored region; contextualisation of push notifications at the right time and in the right place; support for distance-based, time-based, ETA/isochrone and recurrent geofences; and retail, geomarketing and offer-targeting use cases including tailoring by where users live or work.

  https://www.woosmap.com/use-case/geofencing

• Woosmap Geofencing — SDK concepts documentation ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/geofencing/

• Woosmap Geofencing SDK — Batch integration ↗

  Woosmap (developers.woosmap.com) · accessed 26 August 2026

  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.

  https://developers.woosmap.com/products/geofencing-sdk/integration/batch/

Software-driven notification execution on location events is publicly documented and directly relevant to this limitation. Complete Claim 19 correspondence requires the entire independent claim to be analysed as a combination, not merely the notification operation in isolation.

• Evidentiary status: DIRECT PUBLIC EVIDENCE — Very strong for software-driven notification capability

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?

• Technical correspondence is documented; the matter identified above remains for confirmatory technical diligence.