Granted Claim 19 · Software element I
Instructions allowing sending of the relevant notification
Very strong for software-driven notification capability
Granted claim language
Verbatim · US12039568B2 · Claim 19… to thereby allow sending of notifications to the one or more secondary user devices.
Claim requirement
Technical interpretation — not claim languageThe 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.
Publicly disclosed Woosmap functionality
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
Publicly documented delivery chain
- 01Software condition satisfied
- 02Event generated
- 03Notification workflow
- 04Consumer device
- 05Contextual communication
Execution environment and component attribution
- 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.
Public evidence
Woosmap (woosmap.com)
Woosmap Geofencing — commercial use case page
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.
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 ↗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 ↗Technical correspondence
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 and matters for further review
Matters for further review
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?