02. Musings on IP-MPLS Network Architecture for IR
02. Musings on IP-MPLS Network Architecture for IR
carrier. The CSC architecture is designed so that infrastructure. These services have different require-
the CSC backbone carrier only needs to know about ment in terms of quality of services (QoS) and delay
internal routes available within the divisions backbone performances. The IP/MPLS network is expected to
network in order to provide connectivity between all carry these traffics from one point to another with the
the customer carrier routers. The division’s network specified performance criterion. The IP/MPLS point
doesn’t need to know about any backbone carrier inter- of presence will be at every station where the different
nal routes since no communication is required between VPNs should be terminated.
the divisions routers and the backbone carrier routers.
The customer traffic of the division’s network will be
2.8 Quality of Service
label switched within the backbone carrier network (as
if VPN traffic within its own VRF), meaning that the The quality of service that is required for various ser-
backbone carrier routers do not need to know about vices to work on the IP/MPLS backbone of Indian Rail-
routes that belong to end customers connected to the ways will have to de carefully defined. Various traffic
division’s network - as if the backbone carrier routers will have to be carefully classified into various traffic
are Label Switched Routers (LSRs) for the customer classes and associated with a delay performance profile
carrier network. This makes CSC architecture highly so that the network will function as expected. One of
scalable and secure. the most challenging aspects is to ensure that the QoS
is respected across MPLS domains (i.e. MPLS network
Another advantage of CSC lies in the fact that the of each division). For this purpose, QoS will have to be
divisions operation does not depends on the service standardized and implemented across the divisions in
provider of the backbone carrier. Hence, divisions a uniform manner so that the same works seamlessly.
need not coordinate with the service providers when- This will also have to gel with the QoS requirement of
ever they have to do any service provisioning in their Kavach and LTE networks.
network. This brings in independence as well as self-
sufficiency.
3 Railway’s Network Interoperability
2.7 Multiple Networks – VPNs
Such a large network as Railways will obviously have
The IP/MPLS backbone network will be carrying all the routers of different make. Thus, the challenge of in-
network services of Indian Railways like ticketing net- teroperability of the different makes of routers provid-
work, LTE traffic, Kavach traffic, FOIS traffic, Passen- ing proper QoS and delay performance for the different
ger Information, Railnet, Voice traffic (Railway phone), VPNs it is required to support always remain. For the
Video traffic etc. Mostly L2 VPN and L3 VPN will be purpose of interoperability, it is therefore preferrable
used for carrying these traffics over Railway’s MPLS that in one MPLS domain, routers of only one OEM
be used to avoid the interoperability challenge. How-
ever, the interoperability between different domains has
been defined in the RDSO’s TAN version 2.0 and it also
specifies that the interoperability testing must be en- Shri Rakesh Ranjan, with an
sured by Railways while procuring these routers. Fig- experience of 26 years in Rail-
ure 5 shows the interoperability architecture as defined ways Signaling and Telecom-
the TAN v2.0. munication in Indian Rail-
ways is currently working as
Chief Signal Engineer – I in
4 Conclusion ECR, Hajipur. He has var-
ied experience majorly cover-
The IP/MPLS network of Railways will be complex
ing project execution, policy
and critical network. It is the future communica-
formulation, training, network
tion network of Railways for providing integrated
design, research and develop-
high-bandwidth, high-speed connectivity. With the
ment, operation and mainte-
Railways adopting Auto-Signalling, IoT based main-
nance of signalling and tele-
tenance and Kavach, the reach of this network will
com gears. He is a strong advocate of open-source
have to be extended in the block sections as well in the
movement – both hardware and software. His current
future. The networks are being commissioned now but
interest includes work on open hardware and software
the challenge of migrating the services and managing
for programmable logic controller to be used in In-
the same from multiple network operation centres
dian railways for alert-based maintenance of signalling
remains. The migration can be done in many different
gears.
ways. Should we continue to use L2 circuits or migrate
the services to L3-VPN? Pros and cons for these
approaches will have to be carefully evaluated and a
scheme for the same will have to be finalised. Those
Railways that have installed their MPLS networks
like SWR and NFR can relate their experiences and
suggest methodologies. IRISET will have to play a
vital role in training the telecom manpower make them
comfortable in the new technology and upgrade their
skill to be able to manage and maintain this network.