Granted Claim 10 · Method step B
Accessing a database of previously collected data regarding users of the secondary devices
Strong public correspondence
Granted claim language
Verbatim · US12039568B2 · Claim 10… 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 requires an access operation performed against a store of data previously collected in respect of the users of the consumer devices. Three sub-operations are implied: prior collection, persistence in a database, and retrieval of that persisted data as an antecedent to notification sending.
Publicly disclosed Woosmap functionality
Woosmap dedicates published documentation to Visits and Zones of Interest. It documents detection of when and where a user has spent time, assessment of the time spent on each visit, and identification of Zones of Interest as places where a user recurrently spends time. Woosmap expressly states that, when the Zones of Interest feature is activated, the SDK stores and clusters historical location data on the device for each user, and that from the time distribution of clusters the SDK identifies a user's approximate home and office locations after a few days.
- Visits detected without explicit monitoring
- Time spent at each visit assessed
- Recurrent locations identified
- Historical location data stored and clustered on device
- Geographical and temporal patterns derived
- Zones of Interest produced from those patterns
Publicly documented historical-data operation
- 01Current user
- 02Visits
- 03Historical location data
- 04Recurrence
- 05Geographical + temporal patterns
- 06Zone of Interest
Attribution of the claimed method step
Only where the public evidence permitsWoosmap Geofencing SDK
Publicly documentedDocumented as detecting visits, embedding a visit algorithm on Android, and clustering historical location data.
On-device storage
Publicly documentedWoosmap expressly documents that historical location data is stored and clustered on the device when ZOI is activated.
Consumer device
Publicly documentedVisit collection and clustering are documented as device-side operations.
Retailer-side database of consumer records
Not establishedWhether a deployment maintains a retailer-side database of the claimed previously collected data is not addressed by the SDK documentation.
Public evidence
Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — Visits and Zone of Interest
Detection of when and where a user has spent time (visits) without explicit monitoring; assessment of time spent on each visit; definition of Zones of Interest as places where a user recurrently spends time; and the express statement that, when the Zones of Interest feature is activated, the SDK stores and clusters historical location data on the device for each user, identifying approximate home and office locations from the time distribution of clusters. Also publishes consumer context examples including commuting home and leaving the office for a click & collect order.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap iOS SDK — Monitor user visits guide
Implementation-level documentation for collecting, storing, retrieving and processing visit records and Zone of Interest data on iOS consumer devices.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Android SDK — Monitor user visits guide
Implementation-level documentation for the SDK's embedded visit algorithm on Android, including persistence of visit records and derivation of Zones of Interest from collected location data.
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 documents computer-implemented collection, persistence, retrieval and analysis of historical user-location information. This provides substantial technical relevance to the claimed operation involving previously collected user data. It is materially stronger evidence than a generic statement that Woosmap uses location: the documentation identifies a persisted, clustered historical record attributable to an individual user. It does not follow that location history necessarily satisfies every possible construction of the claimed previously collected data, which may on some constructions extend to transactional or profile data.
Weight of this evidence
Woosmap expressly documents that historical location data is stored and clustered on the device when Zone of Interest functionality is activated.
Evidence of United States performance
Matters for further reviewIs there public evidence that visit and Zone of Interest collection is activated and accessed within a relevant United States Woosmap deployment?
United States deployment evidence
Technical correspondence