Definition
Remote signaling (Remote Signaling, YX) originates from the "Four Remotes" (telemetry, remote signaling, remote control, remote regulation) in power systems, referring to the technology of remotely collecting switch quantities and status signals of devices (such as on/off, fault/normal). Remote signaling data is discrete (0/1), in contrast to telemetry (analog values such as voltage, current). In IoT scenarios, remote signaling is used for gun status, door lock status, device status of charging stations, breaker status and fault alerts of power equipment. Remote signaling can be collected via polling or event-triggered reporting, and remote control commands can be issued via push.
Remote telemetry (RTU) differs from remote meter reading in that RTU focuses on status while remote meter reading focuses on consumption; it is similar to status reporting , but RTU emphasizes power/industrial terminology. In cross-border scenarios, RTU data is reported back via IoT SIM cards, and one card for multiple countries ensures cross-border device RTU data collection.
Technical Features and Architecture
The RTU technical architecture includes: collection layer — collecting device switch quantities and status signals, supporting IEC 61850 , Modbus, and proprietary protocols; transmission layer — reporting RTU data to the platform via cellular networks, narrowband , etc.; platform layer — monitoring platform , Device Management Platform receives RTU data to trigger fault alarms , exception alarms ; control layer — extensible remote control (sending switch commands). In combination with energy monitoring , RTU is the basis for energy equipment status monitoring; in combination with charging operation platforms , RTU supports the status monitoring of EV charging stations. In cross-border scenarios, RTU data must support unified access for devices in multiple countries.
RTU status changes can trigger event-driven reporting to reduce invalid transmissions.
Application in IoT and cross-border scenarios
Telemetry is widely applied to: EV charging stations——the connection status of EV charging stations, charging stations guns, door locks, equipment status, fault alarms, reported to charging operation platforms; electric power and energy——energy monitoring, microgrids, the circuit breaker and switch status of IEC 61850 devices; industrial IoT——status monitoring of production line equipment, base stations and so on; cross-border deployment——remote telemetry collection of overseas EV charging stations and overseas power equipment. Cross-border charging networks and global energy monitoring rely on telemetry to achieve remote status monitoring, and multi-country one card[[30]] ensures cross-border telemetry reporting.
SimtoLink provides a stable connection for IoT devices in telemetry scenarios, covering 200+ countries and regions, supporting cross-border charging stations and energy monitoring scenarios.
Telesignaling Changes, Timestamps, and Quality Bits
Telesignaling is a switch quantity seen from a distance: closed or open, normal or alarm, connector mated or not. It expresses a state and a change of state. It does not express continuous quantities such as voltage, current, or energy. A complete change should contain the point number, the new state, the time of the change, and the quality. Quality says whether the state can be trusted, for example a failed acquisition circuit, a test substitution, or a held value after communications were lost. Without quality, the platform cannot tell a breaker that really opened from a loose acquisition wire that reads as open. Double-point signaling uses two bits for closed, open, and an intermediate state. The intermediate state means the mechanism is moving or the contacts disagree. It must not be collapsed into an ordinary 0 or 1.
The time of a change should be stamped by the device or the local unit where the change happened, not filled in by a cross-border platform when the message arrives. A slow network delivers several changes together. If they overwrite one another in arrival order, the sequence of a trip and a reclose is reversed, and incident analysis loses its basis. Debounce filters a string of false changes caused by contact bounce. The debounce time must be shorter than the interval of a real operation. If it is too long, two real operations merge into one. Connector state, door lock, and fault lamp on a charger are telesignaling. Output power is telemetry. They can be sent together, but they cannot share one point-table entry.
When Change-of-State Reporting Is Worth Turning On
Change-of-state reporting is worth turning on when the point table already defines single-point or double-point, quality, and the source of the timestamp, a local clock is available, communications can send the event within the delay the service allows after the change, and the platform deduplicates by point number plus timestamp. A slow process that only needs the state now can be checked with a periodic general interrogation, and does not need an event for every bounce. A trip, an emergency stop, and a door opening need order, so they should travel as events. General interrogation is only for lining up after a missed report. If delay on a cross-border link is often longer than the window allowed for judging order, store the order locally as an event queue, and have the platform replay by the timestamps in the queue, not by the time of receipt.
An Analog Limit Stuffed into a Telesignaling Point
A common mistake is to define high voltage or high temperature directly as a telesignaling point. The threshold changes, but there is no new point number or timestamp, and the history cannot explain why the alarm was raised then. Another is a general interrogation slower than the operating interval, so between two changes the platform always sees the old state. A third is that after communications fail the last closed state is held and the quality is still good, so dispatch believes the device is normal. The intermediate state of a double point is displayed as an alarm storm. Debounce that is too long leaves a short emergency stop with no record. A fourth is that point numbers of several chargers are reused during integration, and charger A's connector state is written onto charger B. The point table should keep the threshold version of a limit alarm separate from the telesignaling point. During an outage, set quality to invalid, and do not let an invalid point enter an interlock. Order events by the device timestamp, and keep point numbers unique across the site.
A change to the point-number table keeps a version number. Historical changes are still interpreted with the point number and quality of that time. After a new version goes live, an event queue that is not finished continues to be parsed with the old version until the queue is empty.