Granted Claim 19 · Software element F
Instructions gating the sending operation on the geographic condition
Very strong — condition evaluated by executable software
Granted claim language
Verbatim · US12039568B2 · Claim 19only 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 languageThe limitation is a software gate. The instructions must produce no sending while the device is outside the region, and must permit sending on the boundary condition being satisfied. What matters is that the condition is evaluated by executable code rather than by human judgement.
Publicly disclosed Woosmap functionality
Woosmap's documented region monitoring implements exactly this state machine: no region event is produced while the device remains outside a monitored region; a boundary crossing produces an enter event, and departure produces an exit event. Region logs are persisted, and the events are published under named identifiers used by downstream integrations.
- No event outside the monitored region
- Enter event on boundary crossing
- Exit event on departure
- Region log persistence
- Named events consumed downstream
Publicly documented conditional state machine
- 01Outside region — software state
- 02Device location update
- 03Boundary test
- 04Inside region
- 05Enter event
- 06Downstream software action
Execution environment and component attribution
- Consumer mobile device
The boundary test is documented as evaluated on the device.
- Woosmap SDK
SDK instructions perform the comparison and emit the event.
Source evidence
Published Woosmap code extractsView technical evidence＋
public class WoosRegionLogReadyListener implements Woosmap.RegionLogReadyListener {
public void RegionLogReadyCallback(RegionLog regionLog) {
// region log event data
}
}Boundary transitions surfaced to the application as discrete software events.
View original ↗Public evidence
Woosmap (developers.woosmap.com)
Woosmap Android SDK — Monitor places with custom geofence
Programmatic registration of circular geofences of specified radius, region-ready and region-log listener callbacks exposing boundary state to application code, and persistence and retrieval of region and region-log records on the consumer device.
View original source ↗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 ↗Technical correspondence
The publicly documented software behaves as a conditional gate on geography, which is the technical character of this limitation. Whether the downstream communication in a deployment is itself gated by that event — rather than merely informed by it — is a configuration question.
Evidentiary status and matters for further review
Matters for further review
Is the outbound communication in a relevant deployment conditioned on the geographic event, or does the event serve only as one input among several?