Public evidence organised by technical capability

Geofencing

Monitoring of a geographic area to recognise device presence within a boundary.

Establishes the primary conditional-geography mechanism relied upon across the granted claim architecture.

Relevant claims

Claims 1, 10, 19

Relevant elements

1D, 1G

Store geofences

Geofences representing a store, competitor store, neighbourhood or point of interest, including automatically generated store geofences.

Ties the monitored region to a retailer environment rather than an arbitrary coordinate.

Relevant claims

Claims 1, 10, 19

Relevant elements

1E

Device location

Identification and monitoring of app-user device location by the SDK.

Establishes determination of the consumer device position on which every geographic condition depends.

Relevant claims

Claims 1, 10, 19

Relevant elements

1A, 1D

Visits / historical data

Local collection and storage of user locations and visits in the application database.

Distinguishes retained behavioural records from transient positioning, which is the subject of the previously-collected-data limitation.

Relevant claims

Claims 1, 10, 19

Relevant elements

1B

Zones of Interest

Derivation of Zones of Interest and recurrent locations from stored location history.

Behavioural categorisation capable of supplying inputs to a relevance determination.

Relevant claims

Claims 1, 10, 19

Relevant elements

1B, 1C

Temporal clustering

Geographical and temporal clustering computed over stored user location history.

Time-structured analysis of retained location data, relevant to combined location and temporal architecture.

Relevant claims

Claims 1, 10, 19

Relevant elements

1B, 1H

Time-based geofencing

Time-based geofences and recurrent geofences alongside distance-based geofences.

Temporal logic operates as a first-class monitoring mode together with the location condition.

Relevant claims

Claims 1, 10, 19

Relevant elements

1H

Isochrone / ETA

Isochrone polygons representing areas reachable within a given travel time; ETA monitoring between user and destination.

Woosmap expressly characterises an isochrone as a time-based geofence, combining temporal and geographic conditions.

Relevant claims

Claims 1, 10, 19

Relevant elements

1H

Automatic events

woos_geofence_entered_event and woos_geofence_exited_event emitted on boundary crossing.

Automated condition detection without human intervention, relevant to automatic enablement.

Relevant claims

Claims 1, 10, 19

Relevant elements

1D, 1G, 1I

Notifications

Contextualised push notifications delivered at the right time and in the right place.

Downstream communication is a consequence of a satisfied monitored condition rather than a scheduled send.

Relevant claims

Claims 1, 10, 19

Relevant elements

1G, 1I

Retail use cases

Retail, geomarketing and offer-targeting use cases, including tailoring by where users live or work.

Commercial positioning of the location layer within retailer marketing architectures.

Relevant claims

Claims 1, 10, 19; dependent claim 2

Relevant elements

1C, 1F

Customer engagement integrations

Click & collect and curbside workflows built on ETA-based arrival detection and order-readiness sequencing.

Deployment narrative where Woosmap events are consumed by an integrated engagement platform — the layer where several open questions may be resolved.

Relevant claims

Claims 1, 10, 19; dependent claim 7

Relevant elements

1F, 1H, 1I