Granted Claim 10 · Method step F
Notifications sent only when the geographic condition is satisfied
Very strong technical correspondence
Granted claim language
Verbatim · US12039568B2 · Claim 10only when the one or more secondary user devices are located at the particular location, or within the specified region or distance in relation to the geographical location; and
Claim requirement
Technical interpretation · not claim languageThis limitation is restrictive rather than enabling. Sending must be confined to the period in which the geographic condition holds; presence of the capability to send on a geofence event is insufficient unless sending is also withheld in the absence of that condition.
Publicly disclosed Woosmap functionality
Woosmap documents that no boundary event is produced while a device remains outside a monitored geofence, and that crossing the boundary generates the named enter event which is delivered to the application. The integration documentation records that these location events can be transmitted as custom events into engagement systems, where they act as triggers within automation and journey composers.
- No event while outside the monitored region
- Boundary crossing produces the event
- Event delivered to the host application
- Event usable as an automation / journey trigger
Conditional event behaviour
- 01Outside geofence — no entry event
- 02Device crosses boundary
- 03Geofence condition satisfied
- 04Event generated
- 05Downstream action / notification
Attribution of the claimed method step
Only where the public evidence permitsWoosmap Geofencing SDK
Publicly documentedDocumented as evaluating the geographic condition and emitting an event only on boundary crossing.
Customer-engagement platform
Publicly documentedDocumented as consuming the event as a trigger for downstream automation.
Deployment notification logic
Not establishedWhether the outbound notification is itself conditioned on the event, rather than merely correlated with it, is implementation-specific.
Public evidence
Woosmap (developers.woosmap.com)
Woosmap Geofencing — SDK concepts documentation
Definition of geofencing as monitoring of a geographic area to recognise device presence within a boundary; enter/exit boundary-crossing events; geofences representing a store, competitor store, neighbourhood or other point of interest; automatically generated store geofences; and isochrone (time-based) geofences monitored against estimated time of arrival.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Android SDK — Monitor Woosmap Assets guide
Publicly documented geofence event identifiers woos_geofence_entered_event and woos_geofence_exited_event emitted when a monitored asset geofence is crossed.
View original source ↗Woosmap (developers.woosmap.com)
Woosmap Geofencing SDK — Batch integration
Transmission of Woosmap Geofencing SDK events from Geofences, POI, Visits and ZOI contexts to Batch as custom events, expressly usable as a Custom Event trigger in the Automation and Journey composers.
View original source ↗Technical correspondence
The publicly documented behaviour is conditional by construction: the event exists only where the geographic condition is satisfied, so any workflow triggered by that event is necessarily gated on the condition. This aligns closely with the restrictive form of the limitation.
Evidence of United States performance
Matters for further reviewIs there public evidence that notification delivery in a United States deployment is conditioned upon the Woosmap geofence event?
United States deployment evidence
Technical correspondence
Evidentiary limitation
Deployment analysis must confirm that notification delivery itself is conditioned upon the Woosmap event in the implementation under review.