03 — Integration architecture
Documented integration architecture
Each stage is drawn from published Woosmap or platform documentation, and mapped to the corresponding limitation of each independent claim.
Stage
Public basis
Cl. 1
Cl. 10
Cl. 19
The commercial party operating the application and defining the commercial objective.
Business-controlled application into which the Geofencing SDK is embedded.
Installable library distributed for Android and iOS, initialised inside the host application.
Secondary device whose location is identified and monitored on-device.
Retained locations and visits, clustered into recurrent locations and Zones of Interest.
Monitored region associated with a store or commercial point of interest.
Time-based and isochrone geofences monitored against estimated time of arrival.
woos_geofence_entered_event, woos_geofence_exited_event, woos_POI_event, woos_Visit_event, woos_zoi_classified_entered_event.
Documented event payload including idStore, city, zipCode, tags, types and user_properties.[field_name].
Third-party platform receiving the event as a custom or entry event. Outside the Woosmap SDK boundary.
Automation and journey composition performed by the engagement platform operator, not by Woosmap.
Communication issued as a consequence of the location and time conditions being satisfied.
Delivery of the notification to the same device whose position was monitored.
This diagram describes a publicly documented technical data path. It is not a statement that any third-party platform, or any customer of any platform, performs or is responsible for any act under the granted patent. Those are matters for patent counsel.