Granted Claim 19 · Software element B
Instructions accessing a database of previously collected data
Strong — construction and deployment dependent
Granted claim language
Verbatim · US12039568B2 · Claim 19… sending, by the primary user device, 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 languageFrom the software perspective the limitation requires instructions that perform an access operation against persisted data previously collected in respect of the users of the consumer devices. Three executable sub-operations are implied: collection, persistence, and retrieval of the persisted records as an antecedent to the sending operation. The existence of data alone is insufficient — Claim 19 concerns instructions that store and read it.
Publicly disclosed Woosmap functionality
Woosmap documents device-side visit collection, persistence and retrieval. On Android a visit listener callback is documented as invoked when a visit is collected, and stored visit and Zone of Interest records are read from a local database accessor. On iOS a visit service delegate receives collected visits, with documented read and erase operations over the persisted visit and ZOI collections. 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, deriving approximate home and office locations from the time distribution of clusters.
- Visit created from device location
- Visit persisted in local storage
- Historical visits retrievable by the application
- Geographical and temporal clustering
- Zone of Interest derived from clusters
- Behavioural context exposed to the host application
Publicly documented data pathway
- 01Device location
- 02Visit created
- 03Visit stored
- 04Historical visits
- 05Clustering
- 06Zone of Interest
- 07Behavioural context
Execution environment and component attribution
- Consumer mobile device
Woosmap states that historical location data is stored and clustered on the device for each user.
- Woosmap SDK
Visit detection, persistence, clustering and ZOI derivation are documented SDK operations.
- NOT ESTABLISHED FROM PUBLIC EVIDENCE
Whether a retailer-side database of previously collected consumer data is accessed before notification sending is not addressed by the SDK documentation.
Source evidence
Published Woosmap code extractsView technical evidence＋
public class WoosVisitReadyListener implements Woosmap.VisitReadyListener {
public void VisitReadyCallback(Visit visit) {
// this method is called when a visit is collected
}
}Event handler invoked by SDK instructions when a visit record is created.
View original ↗ZOI[] ZOIList = WoosmapDb.getInstance(mContext, true).getZOIsDAO().getAllZois();Retrieval of persisted ZOI records from device-side storage.
View original ↗public func readVisits() -> Array<Visit> {
return Visits.getAll()
}Documented read access over persisted historical visit records.
View original ↗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 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 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 ↗Technical correspondence
Woosmap's public material documents executable instructions that collect, persist, retrieve and analyse historical location information on the consumer device. That is a software layer of the same technical character as the previously collected data access recited by Claim 19. It does not follow that historical location records are the previously collected data contemplated by the claim, nor that the access occurs in the recited sequence within any deployment.
Evidentiary status and matters for further review
Matters for further review
Do not assume that historical location data satisfies every possible construction of "previously collected data". Which data store is accessed, by which instructions, and immediately prior to which sending operation, remains a deployment question.