Claim 10 — consolidated method chart
Steps 10A–10I on a single grid
| Claim step | Granted requirement | Woosmap operation | Performing component | Public source | Correspondence | U.S. evidence status |
|---|---|---|---|---|---|---|
| 10A Communication | Establish retailer-to-consumer communication and send notifications after accessing prior data | SDK embedded in the customer application, monitoring consumer-device location and driving notification workflows | Retailer application · Woosmap SDK · consumer device | Woosmap Geofencing SDK — Get Started ↗ | STRONG PUBLIC CORRESPONDENCE | DEPLOYMENT EVIDENCE REQUIRED |
| 10B Prior user data | Access a database of previously collected data regarding secondary-device users | Visits, time spent, recurrence and Zones of Interest, with historical location data stored and clustered on device | Woosmap SDK · on-device storage | Woosmap Geofencing SDK — Visits and Zone of Interest ↗ | STRONG PUBLIC CORRESPONDENCE | DEPLOYMENT EVIDENCE REQUIRED |
| 10C Matching / relevance | Notifications matched by a matching engine on analysis of the previously collected data | Contextual ZOI and visit signals transmitted with user properties into a customer-engagement platform | Woosmap SDK · engagement platform (matching engine not established) | Woosmap Geofencing SDK — Salesforce Marketing Cloud integration ↗ | PARTIAL CORRESPONDENCE | INTEGRATION EVIDENCE REQUIRED |
| 10D Location event | Receive notification when the device is at the location, region or distance | Store and POI geofences emitting woos_geofence_entered_event / woos_geofence_exited_event | Consumer device · Woosmap SDK | Woosmap Android SDK — Monitor Woosmap Assets guide ↗ | DIRECT PUBLIC EVIDENCE | PUBLICLY ESTABLISHED |
| 10E Retailer targeting | Send according to retailer-entered specifications regarding consumer demographics | user_properties.[field_name] and contact keys transmitted alongside location events | Woosmap SDK · engagement platform (retailer criteria not established) | Woosmap Geofencing SDK — Salesforce Marketing Cloud integration ↗ | PARTIAL CORRESPONDENCE | INTEGRATION EVIDENCE REQUIRED |
| 10F Geographic gating | Notifications sent only when the geographic condition is satisfied | No event outside the monitored region; boundary crossing generates the triggering event | Woosmap SDK · engagement platform trigger | Woosmap Geofencing — SDK concepts documentation ↗ | DIRECT PUBLIC EVIDENCE | DEPLOYMENT EVIDENCE REQUIRED |
| 10G Temporal gating | Notifications sent only at the time or period specified by the secondary devices | Time-based and isochrone geofences on ETA; visit duration and temporal clustering | Woosmap SDK · Distance API | Woosmap Distance API — Isochrone feature ↗ | STRONG PUBLIC CORRESPONDENCE | DEPLOYMENT EVIDENCE REQUIRED |
| 10H Automatic enable / disable | Communication automatically disabled and enabled on the location and time state | Automatic event generation and entry / custom-event transmission into automation and journey composers | Woosmap SDK connector · engagement platform | Woosmap Geofencing SDK — Batch integration ↗ | STRONG PUBLIC CORRESPONDENCE | DEPLOYMENT EVIDENCE REQUIRED |
| 10I Notification delivery | Allow sending of the relevant notification to the consumer device | Notifications generated on entry to or exit from monitored POIs; campaign and journey delivery | Retailer application · engagement platform · consumer device | Woosmap Geofencing — commercial use case page ↗ | DIRECT PUBLIC EVIDENCE | DEPLOYMENT EVIDENCE REQUIRED |