Claim 19 — software claim chart
Consolidated software correspondence
Each row links to the underlying element analysis and to the primary public source relied upon. Correspondence labels are qualitative.
| Claim element | Granted software requirement | Woosmap software component | Execution location | Public evidence | Correspondence | Open question |
|---|---|---|---|---|---|---|
| 19A | Instructions stored in a non-transitory medium and executable by one or more processors | Woosmap Geofencing SDK distributed as an installable library | Consumer device · retailer application | Woosmap Geofencing SDK — Android setup and initialisation guide ↗ | DIRECT PUBLIC EVIDENCE | Which stored instruction set is said to carry the complete recited step sequence? |
| 19B | Instructions accessing a database of previously collected user data | Visit collection, on-device storage, retrieval and ZOI clustering | Consumer device · Woosmap SDK | Woosmap Geofencing SDK — Visits and Zone of Interest ↗ | STRONG PUBLIC CORRESPONDENCE | Is historical location data the previously collected data on the relevant construction? |
| 19C | Matching-engine instructions determining relevance from the prior data | Event and user-property transport into engagement platforms | Woosmap SDK · engagement platform | Woosmap Geofencing SDK — Salesforce Marketing Cloud integration ↗ | PARTIAL CORRESPONDENCE | Which component performs the complete claimed matching operation? |
| 19D | Instructions processing device location against a retailer-associated region | Location callbacks, geofence registration and region monitoring | Consumer device · Woosmap SDK | Woosmap Android SDK — Monitor places with custom geofence ↗ | DIRECT PUBLIC EVIDENCE | Is the region specified in the manner the granted language requires? |
| 19E | Instructions applying retailer-entered demographic specifications | Event user properties and platform audience configuration | Engagement platform · retailer application | Woosmap Geofencing SDK — Salesforce Marketing Cloud integration ↗ | PARTIAL CORRESPONDENCE | What specifications does the retailer actually enter, and are they demographic? |
| 19F | Instructions permitting sending only on the geographic condition | Boundary evaluation producing enter and exit events | Consumer device · Woosmap SDK | Woosmap Geofencing — SDK concepts documentation ↗ | DIRECT PUBLIC EVIDENCE | Is the outbound communication itself gated by the event? |
| 19G | Instructions permitting sending only at the specified time or period | ETA and isochrone computation; visit duration and temporal clustering | Woosmap service · Woosmap SDK | Woosmap Distance API — Isochrone feature ↗ | STRONG PUBLIC CORRESPONDENCE | Is a claimed time condition evaluated together with the geographic condition? |
| 19H | Instructions automatically disabling and enabling the communication | Automatic event generation and trigger-based journey entry | Woosmap SDK · engagement platform | Woosmap Geofencing SDK — Batch integration ↗ | STRONG PUBLIC CORRESPONDENCE | Is the disabling state implemented as an express software condition? |
| 19I | Instructions allowing sending of the relevant notification | Event-driven notification and campaign execution | Engagement platform · retailer application · consumer device | Woosmap Geofencing — commercial use case page ↗ | DIRECT PUBLIC EVIDENCE | Is the delivered notification the output of the claimed gating instructions? |