Consolidated claim chart
Claim 1 elements A–I on a single grid
| Ref | Limitation | Granted requirement | Woosmap public position | Source | Position | Open question |
|---|---|---|---|---|---|---|
| 1A | Primary user device associated with a retailer | Retailer-associated device executing code that establishes communication with consumer secondary devices and enables notification generation. | Geofencing SDK embedded in an enterprise/retailer mobile application on consumer devices. | Woosmap Geofencing SDK — Get Started | STRONG PUBLIC CORRESPONDENCE | Identity and location of the retailer-side executing system in a specific U.S. deployment. |
| 1B | Database of previously collected user data | A database of previously collected data in respect of users of the secondary user devices. | Locally stored user locations and visits; clustering, recurrent locations and Zones of Interest. | Woosmap Geofencing SDK — Get Started | STRONG PUBLIC CORRESPONDENCE | Whether the retained store is the database relied upon for notification selection. |
| 1C | Matching engine / relevance | Matching engine matching notifications to the user by analysis of previously collected data so notifications are relevant. | Behavioural context and contextual notification workflows; no “matching engine” terminology used. | Woosmap Geofencing — commercial use case page | PARTIAL CORRESPONDENCE | Whether relevance is computed by Woosmap or by an integrated CRM/engagement platform. |
| 1D | Geographic condition detection | Receiving notification when a secondary device is at a location, or within a specified region or distance of a geographic location. | Geofence monitoring with documented entry and exit events. | Woosmap Android SDK — Monitor Woosmap Assets guide | DIRECT PUBLIC EVIDENCE | Whether the region is specified by the consumer device in a given deployment. |
| 1E | Geographic location associated with the retailer | The geographical location is associated with the primary (retailer) user device. | Store geofences generated automatically from retailer stores hosted on the platform. | Woosmap Geofencing — SDK concepts documentation | DIRECT PUBLIC EVIDENCE | Which retailer store estates are hosted and monitored in the United States. |
| 1F | Retailer-entered demographic specifications | Notifications sent according to specifications entered by the retailer regarding demographics of preferred recipients. | Not disclosed within the Geofencing SDK reference reviewed. | Woosmap Geofencing — commercial use case page | NOT ESTABLISHED ON PRESENT PUBLIC RECORD | Whether retailer demographic criteria govern Woosmap-triggered notifications in deployments. |
| 1G | Location gating of delivery | Notifications sent only when the device satisfies the geographic condition. | Entry/exit events trigger push notifications and application actions. | Woosmap Geofencing — commercial use case page | DIRECT PUBLIC EVIDENCE | Whether parallel unconditional send paths also exist. |
| 1H | Temporal gating of delivery | Notifications sent only at a particular time, or within a particular period, as specified by the secondary device. | Time-based geofences, isochrones and ETA monitoring generating events. | Woosmap Distance API — Isochrone feature | DIRECT PUBLIC EVIDENCE | Whether travel-time thresholds correspond to the claimed consumer-specified time or period. |
| 1I | Automatic disablement / enablement | Communication automatically disabled when conditions are unmet and automatically enabled when both are met. | Automatic monitoring and condition-driven event generation feeding notification workflows. | Woosmap Geofencing — SDK concepts documentation | STRONG PUBLIC CORRESPONDENCE | Whether the disabling limb is implemented as a communication state rather than mere non-send. |