Definition
CBTC (Communication-Based Train Control) is a rail transit signaling control system centered on continuous, high-capacity bidirectional wireless communication between train and ground. Unlike traditional track-circuit-based fixed block systems, CBTC achieves moving block through positioning and communication, allowing trains to report their location and speed to the ground control center in real time, while the ground issues Movement Authority (MA) to trains, thereby shortening train intervals, increasing capacity, and reducing wayside equipment costs.
CBTC is a core subject of international standards such as IEC 62280 and IEEE 1474 and is widely used in subways, light rail, commuter rail, and cross-border railways. Train-to-ground communication generally uses LTE-M, 5G, or dedicated wireless (such as Wi-Fi 802.11p), requiring low latency, high reliability, and anti-interference capabilities, and is closely related to IoT and vehicular networking technologies.
Technical Features and Architecture
The typical CBTC architecture includes: Onboard Subsystem (VOBC)——responsible for train positioning, speed measurement, brake control, and communication with the ground; Zone Controller (ZC)——calculates movement authority based on train position; Data Communication System (DCS)——train-ground wireless and backbone network; Automatic Train Supervision (ATS)——operation dispatching and timetable management. Positioning methods include transponder + speed measurement, RTK satellite positioning, inertial navigation, and combinations thereof to meet centimeter-level accuracy requirements.
Train-to-ground communication needs to meet safety integrity level SIL4 and should adopt redundant, encrypted, and fail-safe designs. In cross-border railway scenarios, the frequency bands and certification requirements of different countries vary widely, so a one card for multiple countries or multi-mode communication solution is needed to ensure continuous cross-border communication for trains.
Application in IoT and cross-border scenarios
The application of CBTC in IoT and cross-border scenarios includes: urban rail transit—automation of subways and light rail operations, reducing manual intervention; cross-border railways—China-Europe freight trains, cross-border high-speed rail, etc., requiring unified communication and signaling standards, with CBTC supporting international interconnection; smart urban rail—combined with data collection and Device Management Platform, enabling fault prediction and energy consumption optimization. SimtoLink provides stable IoT connectivity for onboard train communication modules and ground wireless equipment, supporting reliable CBTC train-to-ground communication in cross-border scenarios.
Movement authority depends on a train-to-ground link with bounded delay
CBTC replaces track-circuit occupancy in fixed block with continuous train-to-ground communication. The train sends position and speed to the zone controller. The zone controller computes how far the train is allowed to go. That permission is called a movement authority, and the communications system carries it back to the train. The train runs only inside the authority. Communication here is not an extra monitoring channel. It is part of the interlocking logic, so it needs an explicit upper bound on delay, a safe-side action after packet loss, and redundant paths that are independent of each other. A public IoT SIM in an international project can carry non-safety services such as passenger information and equipment-status collection. It cannot be treated as the bearer of movement authority merely because it can also get online.
Conditions of use are set by the safety design of the line, not by the data rate of a network card. Between train and ground there are usually redundant radios, a bounded end-to-end delay, a policy that leads to a safe brake after failure, and addresses and priority kept apart from the passenger network. Positioning has to meet the error the system requires. Satellite positioning on its own generally has to be combined with balises, speed measurement, or another method. The accuracy of ordinary asset tracking is not a substitute. A cross-border line also has to handle radio bands, equipment approval, and the join between ground networks in the two countries. Authority must not break because a public roaming attach starts over when the train crosses. Any sharing that changes the delay, such as putting authority and management video on one bearer with no priority, does not meet the conditions of use for this kind of system.
Carrying movement authority on a public roaming session
A likely mistake is to carry movement authority on an ordinary roaming IoT link. Public attach, address assignment, and a cross-border handover have no determined upper bound on time. Once the attach starts over, the authority times out, and the train can only take the safe-side brake. That is not something a larger timeout can hide for long. Another mistake is passenger radio and control radio sharing an antenna, a power supply, or backhaul. Congestion or a fault on the passenger side drags the control side down with it. Another is holding train position with satellite positioning alone, and continuing, under the logic of a ground tracker, after the error grows in a tunnel or a station. Uploading collected train status after a delay, and calling that communication-based control, also mixes monitoring up with control.
If the control link has to change ground networks at a border, the change must be proven inside the system design. It cannot depend on the automatic network selection of consumer roaming. When investigating an attached service that is not safety-related, look at equipment-status collection and the authority channel separately. An interruption of the first should not be explained directly as a failed authority. An interruption of the second should be handled under the safety logic. Whether redundancy is truly independent depends on whether the antenna, the spectrum, and the ground backhaul are separate, not only on the train having two SIMs. The switch time of the standby path also has to be proven on its own. Do not reuse the experience of a few seconds from an ordinary backup link.
Attached status collection may use an ordinary IoT connection, but the severity of a collection outage must not be made the same as an authority timeout. Otherwise one dropout of the passenger-information system is treated as a safety event. A border trial should record the actual time the authority channel took to switch, and compare it with the design bound. If it exceeds the bound, stay on the safe side. Do not loosen the bound temporarily in order to pass the trial. Whether redundancy is independent also depends on whether power and antenna are separate. Two SIMs sharing one feed point are not independent. Non-safety traffic needs a ceiling, so it does not crowd out a monitoring channel that still has to be kept.