Definition
Boundary Alert is an alert event in IoT systems triggered by a platform or terminal when vehicles, personnel, or assets carrying positioning devices enter or exit a preset geofence. The boundary alert is based on location data (GPS, Beidou, base station positioning, etc.) and real-time comparison with the fence boundary, supporting various fence types such as circular, polygonal, and route-based. Alerts can be configured for entering the fence, exiting the fence, or both, and are pushed to operations personnel or business systems through the exception alert channel.
Boundary alerts are related to boundary push: the former focuses on alerts and monitoring, while the latter emphasizes information push triggered by a boundary crossing. In scenarios such as cross-border logistics and cross-border asset tracking, boundary alerts need to support international geofences and multi-timezone notifications.
Technical Features and Architecture
The architecture of boundary alerts includes: Fence Definition—configuring fence coordinates and types on the platform or terminal; Positioning Acquisition—the terminal obtains location via GPS, LBS, etc., and can report data back through cellular networks data transmission; Boundary Determination—algorithms for point-in-polygon relationships, distance to routes, etc.; Alert Trigger—triggered upon status change, with debounce settings to avoid frequent alerts; Notification—integration with push, SMS, Webhook, etc. Combined with Beacon, it can achieve precise indoor positioning and electronic fences.
In cross-border scenarios, geofences can be defined across countries/regions, and alerts need to consider time zones, languages, and local compliance requirements. Devices must support one card for multiple countries to ensure continuous positioning and reporting during cross-border travel.
Application in IoT and cross-border scenarios
Boundary alerts are widely used in: logistics and transportation —alerts when vehicles or containers leave the designated route or area; cross-border logistics need to monitor compliance for international transport; asset management —alerts when valuable assets or equipment leave authorized areas; personnel safety —alerts when personnel at construction sites or mines enter hazardous areas; charging station operation and maintenance — charging station alerts for device movement or unauthorized relocation. Cross-border charging networks, cross-border warehousing, and global fleet management scenarios all rely on boundary alerts for regional monitoring and risk warning.
SimtoLink provides stable IoT connectivity and positioning support for devices with boundary alerts, ensuring reliable alert reporting in cross-border scenarios.
A crossing fires only when the inside or outside state changes
A geofence alert is a change in the relationship between a position fix and a fence: an entry or an exit. It is not another report for every point that happens to lie inside the fence. The system has to remember, for each device, whether the last state was inside or outside, and it raises an alert only when that state flips. The fence may be a circle, a polygon, or a corridor along a route. In international transport, the error on a point is often larger than the margin at the fence boundary. Satellite positioning at a port or in an urban canyon can jump by tens of meters up to more than a hundred meters, and a base-station fix can be wrong by the scale of a cell. The alert logic therefore needs hysteresis or a confirmation count. A single instant of "the point fell inside the polygon" cannot be the only condition.
Before use, use one coordinate datum. The map the fence was drawn on and the coordinates the terminal reports must be the same datum. Otherwise a fixed offset leaves the device permanently a few meters to a few hundred meters outside the fence. The sample interval must be shorter than the time the device takes to cross the fence. A fast vehicle that reports a point only every few minutes may enter and leave again between two reports, and the state never flips. A point with poor positioning quality should be discarded or down-weighted. It must not be treated as equal to a high-accuracy point. The alert body should say whether this was an entry or an exit, which fence was used, and the time and the positioning source of the point. If a cross-border fence straddles both sides of a boundary, also confirm the device can keep reporting in both countries. Otherwise the exit event appears only after it registers again.
A shift in the coordinate datum is treated as already outside
A likely mistake is to draw the fence on one map and report coordinates in another. Devices near a port then false-alarm steadily. Another mistake is to raise an alert on every report, rather than only when the state changes. A vehicle working normally inside the fence keeps generating tickets. Another is a fence smaller than the positioning error. The device is stopped at the door, the point jumps from one side of the boundary to the other, and entry and exit alerts alternate. Guarding a fence the size of a warehouse door with a cell fix also false-alarms steadily, because the cell center is not on the door.
If historical points reported after a border crossing are processed in arrival order rather than sample time, a point from abroad can arrive first and a point from home later, and the fence state flips back and forth. Keep the sample time and the positioning source of each point, and let the state machine advance only by sample time. Points from a communications outage must be able to enter the state machine. Do not judge from only the first point after recovery. Whether the catch-up is complete can be compared with the data acquisition sequence numbers. Whether another path was available during the outage is a separate question, answered by whether the backup link had already taken over. The two explain "not reported" and "reported late" separately.
After the state machine restarts, do not assume the device is outside the fence. Establish inside or outside again from the first trusted point after the restart, and do not treat that establishment as a crossing. Historical points that were caught up should be inserted by sample time. If a flip appears after the insertion, mark the alert as judged after the fact, so duty staff are not sent out against the current time. After fence vertices are edited, do not replay old points against the new fence unless a historical recalculation has been asked for explicitly. When positioning falls back from satellite to a cell, pause flips until accuracy comparable to the scale of the fence is available again.