Granted Claim 1 · Element C
Matching engine and relevance determination
Partial / integration dependent
Granted claim language
Verbatim · US12039568B2 · Claim 1a matching engine configured to match the generated notifications to the user of a secondary user device according to analysis of the previously collected data regarding the user of the secondary user device such that notifications sent to the secondary user device are relevant to the user of the secondary user device; wherein:
Claim requirement
Technical interpretation — not claim languageThis is an important part of the granted architecture because notifications are not merely broadcast according to location. The claimed architecture uses previously collected user information in determining which notification is relevant to which consumer.
Publicly disclosed Woosmap functionality
Woosmap public material addresses contextualised notifications, user location behaviour, Zones of Interest, recurrent locations, tailored services and offers according to where people live or work, and integration of location events into customer-engagement workflows.
- Contextualised notifications
- User location behaviour
- Zones of Interest
- Recurrent locations
- Tailored services / offers
- Customer-engagement integrations
Claimed relevance path
- 01Previous user information
- 02Relevance / matching
- 03Selected notification
- 04Consumer
Potential complete relevance architecture
- 01Woosmap location and visit context
- 02Location event delivered to integrated platform
- 03Retailer CRM / customer-engagement platform
- 04Historical customer information applied
- 05User-specific communication selected
- 06Notification delivered to consumer device
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 — Get Started
Integration of the SDK into a business-controlled mobile application; identification of app-user location; local collection and storage of user locations and visits in the application database; and derivation of Zones of Interest, geographical and temporal clusters and recurrent locations.
View original source ↗Technical correspondence
Woosmap publicly describes behavioural and location categorisation and contextual notification workflows which may supply inputs to, or operate alongside, a relevance or matching layer. The public documentation reviewed does not itself adopt the terminology of a “matching engine”, and no such terminology is attributed to Woosmap in this review.
Evidentiary status
Matters for further review
The complete claimed matching function may be performed outside the Woosmap product boundary. Identifying where relevance is computed — and on what previously collected data — is the single most consequential item of diligence in the Claim 1 analysis.
Public evidence question
Whether the complete claimed relevance-matching function is performed by Woosmap software, or is completed through an integrated retailer CRM or customer-engagement platform, requires deployment-level confirmation.