Granted Claim 10 · Method step I
Allowing the relevant notification to be sent to the consumer device
Very strong for event-driven notification capability
Granted claim language
Verbatim · US12039568B2 · Claim 10… to thereby allow sending of notifications to the one or more secondary user devices.
Claim requirement
Technical interpretation · not claim languageThe method concludes with the permitted sending operation: the relevant, matched notification reaching the consumer device once both conditions are satisfied. This step closes the loop opened by the establishing-communication step.
Publicly disclosed Woosmap functionality
Woosmap's published sample application and commercial use-case material describe notifications generated when a user enters or exits monitored Points of Interest, and describe contextualising push notifications at the right time and in the right place. The engagement integrations document those events driving campaigns and journeys that deliver the consumer communication.
- Notification on POI enter / exit in the sample application
- Push notifications contextualised by place and time
- Retail offer and click & collect workflows
- Campaign / journey delivery via engagement platforms
Publicly documented delivery chain
- 01Location / context event
- 02Engagement logic
- 03Consumer communication
Attribution of the claimed method step
Only where the public evidence permitsRetailer / customer application
Publicly documentedDocumented as receiving SDK events and issuing the in-app or push notification.
Customer-engagement platform
Publicly documentedDocumented as the campaign and journey execution environment for Woosmap-triggered communications.
Consumer device
Publicly documentedDocumented recipient of the resulting notification.
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 (woosmap.com blog)
Click & Collect: why brands need it and how geofencing maximises the experience
Retail deployment narrative for ETA-based customer arrival detection, order-readiness workflows and curbside/click-and-collect notification sequences built on geofencing events.
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 ↗Technical correspondence
Event-driven notification capability is comprehensively documented in the public record. The complete claim method nevertheless requires all limitations to be established: capability at the delivery step does not establish performance of the preceding matching, targeting and conditional-communication operations.
Evidence of United States performance
Matters for further reviewIs there public evidence of Woosmap-triggered consumer notifications actually delivered within a relevant United States deployment?
United States deployment evidence
Technical correspondence
Evidentiary limitation
Complete claim method requires all limitations to be established.