Granted Claim 19 · Software element A
A non-transitory computer readable medium including instructions stored therein
Very strong software-architecture relevance
Granted claim language
Verbatim · US12039568B2 · Claim 1919. A non-transitory computer readable medium including instructions stored therein executable by one or more processors to perform the steps of:
establishing communication between a primary user device associated with the retailer and one or more secondary user devices associated with a consumer and 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 languageClaim 19 is directed to the artefact in which the instructions reside, not to a machine or to a sequence of acts. The limitation requires (i) a non-transitory medium, (ii) instructions stored in that medium, and (iii) executability of those instructions by one or more processors to perform the recited steps. The analysis therefore begins with whether executable software of the relevant character is publicly documented as being supplied, stored and executed at all.
Publicly disclosed Woosmap functionality
Woosmap publishes installation and initialisation documentation for the Geofencing SDK on Android and iOS. The Android guide documents a Gradle dependency on the published SDK artefact and initialisation of the SDK inside the host application's activity; the iOS guide documents CocoaPods and Swift Package Manager distribution and initialisation of the geofence manager from the application delegate. The documentation is addressed to a developer integrating the library into a business-controlled mobile application which is then installed on, and executed by, consumer mobile devices.
- Published package dependency for Android
- CocoaPods / Swift Package Manager distribution for iOS
- Documented initialisation instructions
- Library executed inside the host application process
- Application installed on consumer mobile devices
- Foreground and background execution documented
Granted claim architecture
- 01Non-transitory computer readable medium
- 02Instructions stored therein
- 03Executable by one or more processors
- 04To perform the recited steps
Publicly documented software-instruction chain
- 01Woosmap SDK
- 02Software library
- 03Integrated into mobile application
- 04Stored application / SDK code
- 05Executed by mobile-device processor
- 06Location / geofence operations
Execution environment and component attribution
- Woosmap SDK
The SDK is the distributed software library containing the relevant instructions.
- Retailer application
Woosmap documents integration of the library into the customer's own mobile application.
- Consumer mobile device
The host application, and therefore the SDK code, is documented as running on the end user's device.
Source evidence
Published Woosmap code extractsView technical evidence＋
dependencies {
implementation 'com.webgeoservices.woosmapgeofencing:woosmap-mobile-sdk:+'
}Executable library declared as a dependency of the host application build.
View original ↗use_frameworks!
pod 'WoosmapGeofencing'SDK supplied as a binary framework linked into the application.
View original ↗Public evidence
Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — Android setup and initialisation guide
Distribution of the Geofencing SDK as an installable Android library (Gradle dependency on com.webgeoservices.woosmapgeofencing:woosmap-mobile-sdk), initialisation of the SDK within the host application, a location-ready listener callback delivering computed device locations to application code, and foreground / background execution controls.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — iOS setup and initialisation guide
Distribution of the Geofencing SDK as an iOS framework via CocoaPods and Swift Package Manager, initialisation of WoosmapGeofenceManager from the application delegate, background monitoring control and tracking enablement instructions executed on the consumer device.
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 distributes executable SDK components designed to be incorporated into mobile applications and executed on consumer devices. This establishes a directly relevant software-instruction layer for further comparison with the granted computer-readable-medium claim. It is not, and is not presented as, a conclusion that the medium claim is satisfied: Claim 19 requires instructions executable to perform every recited step in combination.
Distribution of executable software is relevant context. It is not itself a finding on the claim.
Evidentiary status and matters for further review
Matters for further review
Which specific stored instruction set in a given United States deployment — SDK, host application, server component or engagement-platform configuration — is said to carry the complete recited step sequence?