Granted Claim 10 · Method step A
Establishing communication and sending notifications between retailer and consumer devices
Strong — deployment confirmation required
Granted claim language
Verbatim · US12039568B2 · Claim 10establishing communication between a primary user device associate with a retailer and one or more secondary user devices associated with a consumer and sending, by the primary user device, operable to access and execute computer instruction code, notifications to the one or more secondary user devices, subsequent to accessing a database of previously collected data in respect of users of the secondary user devices;
Claim requirement
Technical interpretation · not claim languageThe method opens with an operational, not merely structural, requirement: a communicative relationship must be established between retailer-associated infrastructure and consumer-associated devices, and notifications must be sent over that relationship. The sending operation is expressly sequenced after the database-access operation, so the claimed method presupposes a functioning retailer-to-consumer channel through which conditioned notifications later travel.
Publicly disclosed Woosmap functionality
Woosmap publicly documents the Geofencing SDK as a component integrated into a business-controlled mobile application, identifying the location of application users on their own devices and emitting events that the surrounding application can act upon. The Geofencing sample architecture published by Woosmap shows notifications generated when users enter or exit geofences around monitored Points of Interest.
- SDK embedded in the customer's mobile application
- Consumer-device location identified on device
- Enter / exit events on monitored POIs
- Events surfaced to the application via listener callbacks
- Notification workflows driven by those events
Publicly disclosed operational chain
- 01Retailer / enterprise application
- 02Woosmap Geofencing SDK
- 03Consumer mobile device
- 04Location event
- 05Application / engagement workflow
- 06Notification
Attribution of the claimed method step
Only where the public evidence permitsRetailer / Woosmap customer application
Publicly documentedWoosmap documents the SDK being integrated into a business or enterprise mobile application controlled by the customer.
Woosmap Geofencing SDK
Publicly documentedDocumented as the software identifying app-user location on the consumer device and emitting location events.
Consumer device
Publicly documentedThe SDK is documented as running on the end user's mobile device.
Retailer-side notification infrastructure
Not establishedWhich system in a given deployment issues the outbound notification, and whether it is retailer-operated, is not resolved by the public documentation.
Public evidence
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 ↗Woosmap (developers.woosmap.com)
Woosmap Geofencing — SDK concepts documentation
Definition of geofencing as monitoring of a geographic area to recognise device presence within a boundary; enter/exit boundary-crossing events; geofences representing a store, competitor store, neighbourhood or other point of interest; automatically generated store geofences; and isochrone (time-based) geofences monitored against estimated time of arrival.
View original source ↗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 ↗Technical correspondence
The public documentation establishes both endpoints contemplated by the step — retailer-controlled application infrastructure and consumer-associated devices — and establishes a documented technical pathway by which location events produced on the consumer device drive application and notification workflows. What Woosmap documents, however, is the supply of technology capable of supporting that relationship. Whether the complete claimed method operation is performed is a question about the retailer's deployed application, not about the SDK in isolation.
Evidence of United States performance
Matters for further reviewIs there public evidence that a United States retailer operates a deployment in which the Woosmap-enabled application establishes the retailer-to-consumer notification channel described by this step?
United States deployment evidence
Technical correspondence
Evidentiary limitation
Distinguish Woosmap providing the technology from the retailer's application performing the complete claimed method.