Proceedings 2002/2003 - IRSE
Proceedings 2002/2003 - IRSE
Proceedings 2002/2003 - IRSE
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
EURORADIO AND THE RBC 39<br />
4.7 DISCONNECTING<br />
After all this effort, it comes as a nice surprise that<br />
disconnection is quite painless – one of the<br />
applications decides to disconnect, the command<br />
ripples down the stack, and the protocol layers<br />
‘unpeel’ down to the physical, GSM-R, layer where<br />
one end hangs up.<br />
4.8 OTHER APPLICATIONS<br />
Well, fairly simple. What if you have made use of the<br />
excellent feature whereby a number of transport<br />
connections are provided over the single network<br />
connection? To avoid an impolite interruption to an<br />
ongoing connection, the network connection is not<br />
released until all the transport connections using it are<br />
released. Which, although a fine example of good<br />
manners, could cause a problem if the ETCS application<br />
would like to talk to a new RBC, and there is, say, a<br />
large, non-safety diagnostics dump still being sent to the<br />
last RBC. The solution of course is the same as in any<br />
polite conversation – keep your sentences short.<br />
4.9 NETWORK DISCONNECT<br />
It has also been known for the physical connection<br />
to break, ie for GSM to disconnect. How can this be<br />
handled? At present there is no option but to break<br />
down the other connected layers, and then start<br />
again. However, there are three solutions in the pipeline<br />
than can help shorten the time it takes to recover.<br />
The first is a network reconnection – this has the<br />
benefit of being relatively fast (say 5s to detect loss<br />
of connection, then another 5s to reconnect), as no<br />
reconstruction of the EuroRadio layers is needed.<br />
The second is a proposed modification to<br />
EuroRadio, called ‘fast reconnect’, where the safety<br />
layer is maintained while the lower layers are<br />
reconnected. This will save the three-way authentication<br />
handshake time, but not much else, and may<br />
not be worth developing to save some 1.2s.<br />
A third solution is GPRS, the General Packet Radio<br />
System, which has a completely different way of<br />
working from the normal GSM-R data call.<br />
5 GPRS – THE FUTURE<br />
There is an ongoing debate over GPRS as this<br />
paper is being written, so for completeness let’s look<br />
at some of the upsides/downsides of GPRS whilst<br />
the debate reaches a conclusion. But note, GPRS<br />
does not currently form part of the ERTMS – this is a<br />
look at the future.<br />
As we have seen, conventional GSM sets up a data<br />
call just like a voice call – an end-to-end connection.<br />
The other way of working is to set up a ‘virtual’<br />
connection that looks like a circuit to the upper layers,<br />
but at the lower layers consists of packets of<br />
information, fired off at intervals. Packets have to<br />
contain all the information necessary for the network to<br />
deliver them, but because they are only sent at<br />
intervals, there are gaps between them that allow other<br />
senders to transmit their information (see Figure 7).<br />
This is ideally suited to ‘bursty’ information, such<br />
as short occasional ATP messages, and gives the<br />
enormous benefit of allowing several trains to share<br />
the same channel – good news if you have a dense<br />
railway and are running out of channels.<br />
(application)<br />
SAFETY LAYER<br />
* TCP / UDP *<br />
* IP *<br />
(GSM-R)<br />
Figure 7 – GPRS changes<br />
There is a downside of course – the price you pay<br />
is an increase in transmission delay. How much<br />
depends on how much capacity you build into the<br />
system – the more you pay, the better the<br />
performance. Typically, it is expected to be about<br />
700ms instead of 400ms, but it will vary with load.<br />
However, there is another big plus – connection<br />
set up time effectively vanishes. When a GPRS<br />
mobile switches on, it ‘registers’ with the network –<br />
a time-consuming process similar to setting up a<br />
circuit connection. The difference is it only happens<br />
once, probably at the start of each day. Once<br />
registered, the mobile and the network are both<br />
aware of each other, and can initiate data<br />
transmission with only a very short delay to ensure<br />
no one else is transmitting. In between, the mobile<br />
and the network remember each other, for a<br />
configurable time up to hours. So as long as there is<br />
nothing to transmit, a train could go through a radio<br />
hole (accidental or deliberate) and not notice.<br />
This has many benefits, from base station<br />
maintenance through to a low-cost system with discontinuous<br />
radio coverage, but it will involve some<br />
major changes to the EuroRadio protocol stack, and<br />
should not be expected for maybe one to two years.<br />
However, by having the magic abbreviation ‘TCP/IP’<br />
cast over it, it will inevitably become the most<br />
popular protocol stack in use by the railways!<br />
6 CONCLUSION<br />
We have taken the opportunity in this paper of<br />
explaining a little more of the internal workings of<br />
EuroRadio and the RBC, with the emphasis on<br />
EuroRadio. While the concept of EuroRadio is simple<br />
to understand, there are some aspects of the way it<br />
works that anyone who uses it should be aware of.<br />
Similarly, the RBC is easy to understand on the<br />
surface, but this surface masks a level of complexity<br />
that is not visible from the specifications. Interoperability<br />
demands total compliance with a detailed<br />
internal and external specification for EuroRadio,<br />
whereas it is interface compliance, especially the<br />
train and interlocking interfaces, rather than internal<br />
functionality, that is essential for the RBC.<br />
7 REFERENCES<br />
Unisig document – Subset037 EuroRadio FIS.<br />
Unisig document – Subset064 Symmetric Key<br />
Management System Specification.