-
S T R A T E G I C W H I T E P A P E R
Two key issues are driving todays strategic-industry customers:
the need for cost reduction
and increased efficiency from their business operations in light
of limited funding and
the need to provide more services that need high bandwidth
without impacting existing
services. Some customers are considering migration from a
predominantly SDH/SONET
network to an IP/MPLS packet network. With a range of business
and network require-
ments, such as bandwidth, availability, traffic engineering and
security, customers can
migrate their networks in phases, fulfilling business
justifications for moving to IP/MPLS
that include CAPEX/OPEX reductions along with ease of
integration and network expansion.
Migration from SDH/SONET to IP/MPLS can be supported by the
Alcatel-Lucent IP/MPLS
product portfolio and end-to-end services throughout the
migration life cycle.
Strategic IndustriesMigrating SDH/SONET Networks to IP/MPLS
Networks
-
Table of contents
1 1. Introduction
1 2. Business and network requirements
1 2.1 Brownfield or greenfield
2 2.2 Multiplicity of services
2 2.3 Dedicated networks or a single multiservice network
2 2.4 Reliability (protection), availability, maintainability,
safety (RAMS) requirements
3 2.5 Traffic-engineering requirements
3 2.6 Security requirements
3 2.7 Operational requirements
4 3. Network technologies
4 3.1 SDH/SONET overview
5 3.2 IP/MPLS overview
7 4. Migrating from SDH/SONET to IP/MPLS
8 4.1 Phase 1: Adding IP/MPLS routers to the SDH/SONET
infrastructure
8 4.2 Phase 2: Switching TDM services onto the IP/MPLS
infrastructure
9 4.3 Phase 3: Removing the SDH/SONET infrastructure and
introducing WDM
10 5. Conclusion
11 6. Acronyms
11 7. Authors
-
Strategic Industries | Strategic White Paper 1
1. Introduction
Every strategic industry1 (SI) has various mission-critical
applications that are needed to run the business. Some applications
have run for many years and must continue to be supported. However,
with increasing demand for bandwidth and standardization of
interface types, these applications are moving from TDM for
Ethernet and IP, and the next-generation network infrastructure
must support them both. In addition, many industries have
applications that demand the highest level of reliability and
synchronization and small delay and jitter for example, with
teleprotection for utilities and signaling and Global System for
Mobile Communications - Railway (GSM-R) for rail.
The Alcatel-Lucent IP/Multi-Protocol Label Switching (MPLS)
solution has been tested and proven to seamlessly support all these
applications without any issues. The IP/MPLS network can support
these most critical and technically demanding applications and can
ensure that the applications receive the required bandwidth.
Because of these advantages, all other traffic, including corporate
voice, video and data, can be moved to the network. Figure 1 lists
some key SI applications.
Figure 1. Strategic industry key applications
2. Business and network requirements
To decide which technology to use, SI customers must first
understand their business and network requirements, as outlined in
the following subsections.
2.1 Brownfield or greenfieldIt is rare for an SI customer to
implement a greenfield communications project, but this may be the
case for a new metro or for a municipality that wants to invest in
a multiservice network. This is the most favorable configuration
for network-design engineers because they can define and implement,
in a single step, the preferred optimal network architecture.
However, in most cases the SI customer has already invested in
several networks, with each network dedicated to a subset of
applications for example, one network for TDM services, another one
dedicated to supervisory control and data acquisition (SCADA)
system-control services, and a third network for data services.
The designers aim in such cases is at least two-fold:
Todesignanetworkthatwillultimatelyaccommodateallthecustomersexistingandfutureservices
Todeviseamigrationstrategyinwhicheachserviceismigratedfromitscurrentnetworktothenew
convergent network. This second phase ends with the retirement of
legacy networks after all services have been migrated.
1 Strategic industry refers to the energy, transportation, smart
communities, defense, healthcare and industries.
Utilities
Transport
Oil and gas
Defense
Smart Communities
SCADA
Telemetry
Teleprotection
Signaling
Video Surveillance
-
Strategic Industries | Strategic White Paper2
2.2 Multiplicity of servicesOne key characteristic of SI
customers is that they use a broad variety of services with widely
different communications requirements. One way to differentiate
these services is by traffic content:
Voiceservices(forexample,telephony,teleconferences) Require
constant but moderate bandwidth (kb/s) with very short transmission
delay (100 ms) and limited jitter. Such services are usually
synchronous that is, the source and destination use the same master
clock.
Videoservices(forexample,videoconferencing,corporatevideoandvideosurveillance)
Require variable and significantly high bandwidth (Mb/s), short
transmission delays and limited jitter. These services are also
quite intolerant of error rate.
Data-basedservices(forexample,filetransferandcontroldatafromremotedevices)
Require bandwidths from very moderate (kb/s) to high (Mb/s). The
traffic is usually bursty with short periods of high activity
followed by long idle periods, and time constraints are usually
loose. These services are also tolerant of error rate because they
implement correction by retransmission or by redundancy of
information (forward error correction [FEC]).
Another way to differentiate is topological:
Someservicesarepoint-to-point,suchasinatelephonycircuit.
Someservicesarebetweenonesourceandmultipledestinations,suchasinvideosurveillance(point-to-multipoint).
Some of these services, such as computer communications, are
naturally packet-based. Others that were traditionally
circuit-based, such as TDM telephony, are now evolving to a packet
mode.
2.3 Dedicated networks or a single multiservice
networkTraditionally, each service was supported by a dedicated
network designed to meet its specific require-ments, but today a
single network must accommodate all requirements from all services.
The benefits of using a single convergent network are multiple,
dramatically reducing an organizations capital expenditures (CAPEX)
and operating expenditures (OPEX). For these cost-reduction
strategies to be viable, the network must satisfy the following
requirements:
Thenetworkmustbebasedoninternationalstandardsandallowformultivendorinteroperability.
ThenetworkmustbecapableofmeetingtheQualityofService(QoS)requirementsofthedifferentclasses
of services transported across it.
Thenetworkmustaccommodatenewservicesandbescalablethroughoutitslifecycle.Itisthereforemandatory
that the network be able to grow in function to support increased
traffic demands without disrupting existing services.
Thenetworkmustbeeasilymaintainable.SIcustomersneedamanagementsystemthatshieldsthemfrom
the complexities of the underlying technologies and provides
user-friendly operating interfaces.
2.4 Reliability (protection), availability, maintainability,
safety (RAMS) requirementsSI customers require solutions that are
suitable for providing mission-critical services: some or all
services must be up and running 24 hours a day/7 days a week. For
example, for railway operators using services such as GSM-R,
emergency telephony and railway signaling, there can be no
compromise on the availability of these services.
In the case of a public-safety organization using video
surveillance, emergency call centers and Terrestrial Trunked Radio
(TETRA) service, these services must also be available on a
continuous basis with no outages.
Service reliability must be considered from an end-to-end
perspective. It is possible to have a reliability requirement of
99.9999 percent, especially when human safety is at stake, such as
in a tunnel.
-
Strategic Industries | Strategic White Paper 3
2.5 Traffic-engineering requirementsOne traffic-engineering
requirement is to design the network to allow for the selection of
best path across the network by taking into consideration the
physical paths of the links and interfaces. For increased
reliability, a standby path should be physically isolated from the
primary path.
In addition, the network should be able to automatically choose
the pathway of least cost, fewest hops, and general traffic
predictability.
2.6 Security requirementsMany SI customers manage part of a
countrys critical infrastructure, such as utilities or
transportation. Communications networks are increasingly critical
for these sectors to continuously operate with reliability and
security.
The following trends and elements are driving security
requirements:
Evolutionfromseveralisolatednetworkstoasinglemultiservicenetwork,carryingtrafficwithvery
different security-risk profiles, such as SCADA and corporate
communications
Useofcommercialoff-the-shelfproductsandopenprotocolssuchasEthernetandIP
Internetconnectivityforemployees,connectingtothirdpartiessuchaspartnersandprovidingreal-time
information to the public
Requirementsforflexibilityandmobility,whicharedrivingremoteaccess
Regulatorycomplianceandcompliancewithrecognizedindustrybestpractices.
TheITU-TX.805securitymethodology(Securityarchitectureforsystemsprovidingend-to-endcommunications),
developed by Alcatel-Lucent Bell Labs, is one of the frameworks
that can be used to address communications network security.
2.7 Operational requirementsAn SI network operator must identify
and understand operational requirements before designing the
network, answering questions such as:
CanIeasilyscalemynetwork?
Willitmeetthelow-latencyrequirementformission-criticalapplications?
Willitbeflexibleenoughtodynamicallyaddnewapplications?
Some important operational requirements are described in this
section.
Scalability
In the changing SI environment, the communications network needs
to support an evolving set of business services, from
latency-sensitive TDM-based services to best-effort Internet-based
services. Growth of both service types and capacity should be
accommodated without a significant change in architecture.
Resiliency
SI customers build networks to provide mission-critical
communications with high-availability targets
(reliability/resiliency). These communications networks need to be
highly reliable and should provide uninterrupted voice and data
traffic.
Single failures should not impact the ability to quickly route
traffic around the failure, and the network must be designed to not
share common failure modes such as being susceptible to single
geographic-area events (for example, seismic activity). Subsecond
failover times are expected, enabling networks to quickly recover
from a failure and deliver greater than 99.999 percent availability
to ensure connectivity for mission-critical traffic.
-
Strategic Industries | Strategic White Paper4
Latency
Latency is a vital attribute of many services carried in
SI-customer networks today. A well-known example is teleprotection.
Teleprotection circuits must have low, predictable latency to
ensure timely fault detection and isolation. In many cases,
protection schemes have been in place for a long time and are based
on very basic communications protocols.
Other SI customers, such as railway operators, have similar
requirements although, in most cases, latency requirements are less
stringent than in the case of teleprotection.
Flexibility
As SI customers start exploiting their new communications
networks, new services will be discovered
withnewperformancerequirements.Thenetworkthereforeneedstobeflexibletocatertoanever-changing
mix of services.
Virtualization
An SI communications network must be built to ensure that
effective bandwidth can be allocated to provide for the virtual
isolation of various traffic types on a single infrastructure. The
network should be able to support different appli cations or user
groups in an environment that is private and unaffected by other
traffic.
Network management
Operations and maintenance tools should simplify the deployment
and day-to-day operation of a communications network. Operations
tools such as service and interface tests should allow for rapid
troubleshooting,enablingproactiveawarenessofthestateoftrafficflowstohelpminimizeservicedowntime.
The tools should also offer proactive surveillance, configuration,
validation and diagnoses to simplify problem resolution, reduce
configuration errors, and reduce troubleshooting time.
Management software should automate and simplify operations
management as well as support element management, network
commissioning, service provisioning and service assurance.
3. Network technologies
This section describes SDH/SONET and IP/MPLS technologies along
with the benefits of migration.
3.1 SDH/SONET overviewSONET is widely used in North America
whereas SDH is used in the rest of the world. SDH/SONET technology
enables a simple, deterministic and robust method of sharing
high-cost bearers across various physical and logical architectural
domains.
SDH/SONET offers an SI-customer bearer network a range of
benefits, and SI customers have relied heavily on SDH/SONET as a
critical building block in their networks. However, SDH/SONET has
limitations when supporting IP applications with various bandwidth
demands and performance requirements. Next-generation SDH offers
one way of introducing packet support in a network while continuing
to support TDM-based applications.
Support of legacy TDM protocols
Legacy TDM protocols and applications can coexist on the same
network equipment and path as Ethernet transport without
compromising performance for either. As an alternative to building
separate dedicated networks, optical multiservice products provide
the most risk-averse approaches to combining TDM and packet
traffic. For some applications, such as long-distance
teleprotection, this offers a realistic technology solution for
service consolidation.
-
Strategic Industries | Strategic White Paper 5
QoS
BecausetheoriginalEthernetframeisencapsulatedinitsentirety,QoSmarkingssuchasIEEE802.1pare
retained without corruption (preamble and start-of-frame delimiter
[SFD] excluded). Moreover, performance can be entirely
deterministic because link capacity is guaranteed.
Manageability
SDH/SONET systems have very strong operations, administration
and maintenance (OA&M) capabilities, a vital requirement for
the carrier markets in which they are often deployed. SDH/SONET
system-path overhead provides rich OA&M, including fault
detection, testing and performance monitoring.
Service availability/resiliency
Withthisencapsulationapproach,allthebenefitsofSDH/SONETpathprotectioncanbeleveraged.
Security
Ethernet over SDH/SONET may be provided with a dedicated virtual
circuit. In the case of Generic Framing Procedure (GFP), traffic
may be virtual LAN (VLAN)-tagged to provide another degree of
isolation. Moreover, because there is no requirement to use IP in
the SDH/SONET control plane, any denial of service (DoS) attempt
malicious or unintended is constrained to the related virtual
circuit.
Integration with legacy equipment and services (TDM support)
Integration is ensured as long as the relevant standards are
adhered to.
3.2 IP/MPLS overviewMPLS provides the ability to establish
connection-oriented paths over a connectionless IP network and
facilitates a mechanism to engineer network-traffic patterns
independently from routing tables.
In an MPLS network, data packets are assigned labels.
Packet-forwarding decisions are made solely on the content of the
label, without the need to examine the packet itself. This allows
the creation of end-to-end circuits across any type of transport
medium. MPLS can be implemented over several
typesofphysicalinfrastructure,includingoptical,SDH/SONET,WavelengthDivisionMultiplexing(WDM),andwireless.
MPLS was specifically designed to support Layer 2 and Layer 3
protocols and multiple traffic types and
priorities,withmanagementtoolstotest,troubleshootandmaintainahighlyreliable,flexiblenetwork.
Key benefits of IP/MPLS for SI customers are described
below.
Multiservice support
TheIP/MPLScommunicationsinfrastructureoffersaflexiblenetworkandserviceenvironmentthatenables
the continuing support of existing services while incorporating new
Ethernet and IP-based applications. These applications are
typically more efficient in terms of bandwidth usage when deployed
over an IP/MPLS infrastructure. All services converge at the
network access, where the required
MPLSpackethandlingsuchasencapsulationandQoScapabilitiesisexecuted.Differentapplications
are transported using dedicated virtual private networks (VPNs) in
a point-to-point, point-to-multipoint or multipoint-to-multipoint
manner. An IP/MPLS network also directly supports TDM-based
traffic.
-
Strategic Industries | Strategic White Paper6
Circuit Emulation Service over MPLS
Migrating legacy TDM systems and services is simple when taking
advantage of IP/MPLS Circuit Emulation Service (CES) functionality,
which allows for the gradual transition of legacy applications. CES
delivers the same quality of experience as the existing TDM network
infrastructure, with the same level of predictability. The IP/MPLS
network has a circuit-emulation interworking function that ensures
all information required by a TDM circuit is maintained across the
packet network. This provides a full transition to the packet
network over time while providing TDM service continuity.
MPLS support for L2 and L3 VPNs
Layer 2 and Layer 3 VPNs allow the virtualization of services in
the network and are provisioned between MPLS nodes. The VPNs are
configured as an overlay on the MPLS network and are capable of
supporting thousands of VPNs on a single physical infrastructure.
VPNs supported on Alcatel-Lucent routers and switches are Virtual
Leased Lines (VLLs), Virtual Private LAN Service (VPLS), and
IP-VPNs.
MPLS and traffic engineering
WithMPLSTrafficEngineering(MPLS-TE),networkoperatorscanautomaticallysetupapathdifferent
from the least-cost path selected by a routing protocol such as
Open Shortest Path First (OSPF). MPLS-TE incorporates metrics such
as delay and bandwidth to calculate the optimal path through the
network. The end result is a network with better latency
characteristics, bandwidth utilization and service
availability.
MPLS and deterministic reroute behavior
MPLS provides deterministic traffic behavior with the same
results as ATM networks and with reroute times which match that of
SDH/SONET-network recovery times. MPLS supports the Fast
Reroute(FRR)mechanism,whichcandeliverreroutetimesofunder50ms.
Bandwidth management and QoS
TheQoSofIP/MPLSeffectivelysupportstheconvergenceofmultipleservicesoveracommonpacket-based
infrastructure. IP/MPLS enables the network to discriminate among
various types of traffic based on a rich set of classification
attributes and prioritizes the transmission of higher-priority
traffic.FeaturessuchasHierarchicalQoS(H-QoS)alsoallowlower-prioritytraffictobursttofillavailable
bandwidth when higher-priority applications go idle.
H-QoSusesanadvancedschedulingmechanismtoimplementservicehierarchies,whichprovidemaximumisolationandfairnessacrossdifferenttrafficwhileoptimizinguplinkutilization.Withmultiplelevels
and instances of shaping, queuing and priority scheduling, the
IP/MPLS network can manage
trafficflowstoensurethatperformanceparametersforeachapplicationsuchasbandwidth,delayand
jitter are met.
Synchronization
In most TDM networks, synchronization is distributed in the
network using the SDH/SONET mechanisms built into the
physical-layer definition. To deliver the TDM service using a
packet network, the same synchronization must be achieved with
other means.
To enable the rapid migration of these networks, Synchronous
Ethernet (SyncE) provides the easiest, quickest way to achieve
frequency synchronization and to allow the benefits of an
Ethernet-network infrastructure to be realized without changing
existing TDM-network applications. The concept of SyncE is similar
to SDH/SONET system-timing capabilities.
-
Strategic Industries | Strategic White Paper 7
WithSyncE,networkelementsderivethephysical-layertransmitterclockfromahigh-qualityfrequency
reference using the physical Ethernet interfaces. This does not
affect the operation of and is transparent to the Ethernet
layers.
High availability
An IP/MPLS solution is designed around a high-availability
redundant architecture that incorporates key features such as
Non-Stop Routing (NSR), Non-Stop Services (NSS), and Link
Aggregation Group (LAG). Network stability is significantly
enhanced with NSR, which is the ability of the router, in the event
of a control-plane failure or a forced switchover, to continue to
forward packets using existing and dynamically updated forwarding
information.
Withnon-stoptechnology,thestandbycontrolcardimmediatelytakesoverinmilliseconds,withno
impact to applications running over the nodes. NSS features operate
rapidly and independently so that a control failure on one network
node is literally invisible to the overall network, with no
disturbance of IP-network topology: no routes need to reconverge,
and no additional protocols are needed in the network.
Pseudowire redundancy
Incorporating redundant Network Operations Center (NOC) sites is
a common approach to designing and building networks that are
capable of supporting disaster recovery. This can be achieved by
leveraging pseudowire redundancy, which allows operators to
provision both active and standby pseudowires (virtual MPLS
circuits) between a remote site and two NOC sites.
In the unlikely event that the primary NOC site fails,
remote-site traffic is automatically switched from the active to
the standby pseudowire, and connectivity is reestablished with the
backup NOC. MPLS circuits can be provisioned between the primary
and backup NOC sites to support server synchronization and
database-mirroring operations.
Superior troubleshooting capabilities
MPLS provides many useful tools, including the service ping
tool, which helps network operators to verify end-to-end
connectivity. Another useful MPLS OA&M tool is service
mirroring, which enables specific service traffic to be mirrored to
a local or remote destination for capture or analysis.
4. Migrating from SDH/SONET to IP/MPLS
To date, SI customers have relied on TDM- and SDH/SONET-based
networks because their applications were mostly TDM-based.
Reliability and predictable latency have made TDM-based
technologies
ideallysuitedforthispurpose.Withtheavailabilityofnext-generationapplications,SIcustomerswill
have to migrate their TDM applications to IP. Migration can occur
in various ways, but this paper describes only one of the methods:
moving from SDH/SONET to IP/MPLS.
To keep the disruption of existing services to a minimum, it is
recommended that the migration from SDH/SONET to MPLS take place in
phases. A three-phase migration is described below.
-
Strategic Industries | Strategic White Paper8
4.1 Phase 1: Adding IP/MPLS routers to the SDH/SONET
infrastructureDuring this phase, IP/MPLS routers are connected to
the SDH/SONET infrastructure, as shown in Figure 2. This allows the
introduction of new IP services and Ethernet connectivity while
continuing to support TDM services on the SDH/SONET infrastructure,
for cost savings and reduced disruption. Network operators also
have time to become familiar with IP/MPLS capabilities before
moving the TDM services. Effective utilization of the existing
SDH/SONET infrastructure ensures minimal or no disruption of
existing services while new services are added.
Figure 2. Adding IP/MPLS routers for IP and Ethernet
services
4.2 Phase 2: Switching TDM services onto the IP/MPLS
infrastructureAlcatel-Lucent IP/MPLS routers support traditional
TDM services including Synchronous Transport
Mode1/OpticalCarrier3(STM-1/OC-3),T1/E1,RS-232,V.35,X.21,andEandMcircuits(E&M)allowing
the migration of these services away from the SDH/SONET
infrastructure. This can be done in stages and with the coexistence
of various interface types. Services that have been satisfied with
traditional TDM interfaces can also be supported while new Ethernet
interfaces for these services are being introduced.
At this point, TDM services will likely be supported on the
existing multiplexer TDM equipment or on the IP/MPLS routers while
new IP and Ethernet services are supported on IP/MPLS routers, as
shown in Figure 3. At the end of this phase, all services should
have migrated to the IP/MPLS network.
Low-speedinterfaces(RS-232, E&M,and others)
Low-speed interfaces(RS-232, E&M, and others)
IP services
IP services
Ethernet services
Ethernet services
SDH/SONET SDH/SONET
PoS
PoS E1/T1
E1/T1
IP/MPLSrouter
TDMmultiplexer
SDH/SONET
SDH/SONET
IP/MPLS router
Low-speedinterfaces
(RS-232, E&M,and others)
IP services
Ethernet services PoS
E1/T1
IP/MPLSrouter
TDMmultiplexer
TDM multiplexer
Low-speed interfaces(RS-232, E&M, and others)IP services
Ethernet services
PoS E1/T1
IP/MPLS router TDM multiplexer
-
Strategic Industries | Strategic White Paper 9
Figure 3. Consolidating TDM services onto and through IP/MPLS
routers
4.3 Phase 3: Removing the SDH/SONET infrastructure and
introducing WDMAt this stage, the SDH/SONET network can be
completely removed and the fiber plant can be used to interconnect
IP/MPLS routers after all services have migrated onto the routers,
as shown in Figure 4. This simplifies network structure and
management while providing an infrastructure capable of supporting
new services and bandwidth requirements.
Figure 4. Consolidating access on IP/MPLS and removing
SDH/SONET
Low-speedinterfaces(RS-232, E&M,and others)
Low-speed interfaces(RS-232, E&M, and others)
Low-speed interfaces(RS-232, E&M, and others)
Low-speedinterfaces
(RS-232, E&M,and others)
IP services
IP services
IP services
IP services
Ethernet services
Ethernet services
Ethernet services
SDH/SONET SDH/SONETPoS
PoS
PoS
E1/T1
PoS
IP/MPLSrouter
TDM multiplexer
SDH/SONET
SDH/SONET
IP/MPLSrouter
Ethernet services
IP/MPLS router
E1/T1
TDM multiplexerIP/MPLS router
Low-speed interfaces(RS-232, E&M, and others)
Low-speed interfaces(RS-232, E&M, and others)
IP services
Ethernet services
Low-speed interfaces(RS-232, E&M, and others)
IP services
Ethernet services
Ethernet Ethernet
Ethernet Ethernet
IP/MPLSrouter
IP/MPLSrouter
IP/MPLSrouter
IP services
Ethernet services
Low-speed interfaces(RS-232, E&M, E1/T1, and others)
IP services
Ethernet services
IP/MPLSrouter
-
Strategic Industries | Strategic White Paper10
Alternatively, if a separate fiber backbone is needed, the
SDH/SONET equipment can be removed
andsimultaneouslyreplacedbyaWDMnetwork,withIP/MPLSroutersconnectedtoWDMequipment,asshowninFigure5.Thisisthecasewhenthedistancetorunfiberbetweennodesisquitelargeorif
there is a scarcity of fiber cables: running new fiber cables can
be quite costly. This can also be done in stages, allowing for
minimal service disruption.
Figure 5. Consolidating access on IP/MPLS and replacing
SDH/SONET with WDM
5. Conclusion
Migrating to an IP/MPLS network enables SI customers to gain the
network reliability that is needed to provide mission-critical
services. Moving to an IP/MPLS network provides the additional
benefit of supporting consolidated voice, data and video
applications that can be managed using configurable
QoSlevels,dependingonthetypeandpriorityoftrafficthatisbeingrouted.
Withdecadesofexperienceinnetworkmigrationandtransformation,Alcatel-Lucentoffersacomprehensive
product portfolio across IP and optical domains, along with a broad
array of profes-sional services that facilitate this important
transition for customers worldwide. Alcatel-Lucent is therefore
uniquely positioned to leverage its expertise in implementing
innovative, integrated solutions over an IP/MPLS network.
Low-speedinterfaces(RS-232, E&M,and others)
Low-speedinterfaces
(RS-232, E&M,and others)
Low-speed interfaces(RS-232, E&M, and others)
Low-speed interfaces(RS-232, E&M, E1/T1, and others)
IP services
IP services
IP services
IP services
Ethernet services
Ethernet services
Ethernet services
WDM WDMEthernetEthernet
Ethernet
Ethernet
IP/MPLSrouter
WDM
WDM
IP/MPLSrouter
Ethernet services
IP/MPLS router
IP/MPLS router
-
Strategic Industries | Strategic White Paper 11
6. Acronyms3G Third Generation
APTA American Public Transportation Association
ATM Asynchronous Transfer Mode
CAPEX capital expenditures
CATA Canadian Advanced Technology Alliance
CCTV closed-circuit television
CES Circuit Emulation Service
CPU central processing unit
DoS denial of service
E&M Ear & Mouth Signaling
E1 E-carrier system
FEC forward error correction
FRR Fast Reroute
GFP Generic Framing Procedure
GSM-R Global System for Mobile Communications - Railway
H-QoS Hierarchical quality of service
ICT Information and Communications Technology
IEEE Institute of Electrical and Electronics Engineers
IP Internet Protocol
IPTV IP Television
ITS Intelligent Transportation Systems Society
ITU-T Telecommunication Standardization Sector
L2, L3 Layer 2, Layer 3
LAG Link Aggregation Group
LAN local area network
MPLS Multi-Protocol Label Switching
MPLS-TE MPLS Traffic Engineering
NOC Network Operations Center
7. AuthorsPadma KamathSolution ManagerAlcatel-Lucent
Padma Kamath is a solution manager in the Alcatel-Lucent
Services Business Group, Strategic Industries Services Division,
with a focus on transportation sectors. Padma has spent 16 years in
various ICT roles, including R&D, program management, network
engineering, business development, and solutions design and
innovation. A member of Intelligent Transportation Systems Society
(ITS) America and ITS Canada, Padma began her career with Newbridge
Networks in 1994.
Padmas previous positions include software design and
integration; system design and engineering; and program manager.
Padma is a PMP and holds a B.Sc. (Physics, Chemistry and
Mathematics) from
theUniversityofMysore,India;aB.Sc.(ComputerScience)fromMcMasterUniversity,Hamilton,Canada;andanMBAfromtheRotmanSchoolofManagement,UniversityofToronto,Canada.
NRS1 Alcatel-Lucent Network Routing Specialist 1
certification
NSR Non-Stop Routing
NSS Non-Stop Services
OA&M Operations, administration and maintenance
OC-3 Optical Carrier 3
OPEX operating expenditures
OSPF Open Shortest Path First
PLM product line management
PMP Project Management Professional
QoS Quality of Service
RAMS reliability (protection), availability, maintainability,
safety
SCADA Supervisory Control And Data Acquisition
SDH Synchronous Digital Hierarchy
SFD start-of-frame delimiter
SI strategic industry
SONET Synchronous Optical Network
STM-1 Synchronous Transport Mode 1
SyncE Synchronous Ethernet
T1 T-carrier system
TDM Time Division Multiplexing
TETRA Terrestrial Trunked Radio
UMTS Universal Mobile Telecommunications System
UTC Utilities Telecom Council
VLAN virtual LAN
VLL Virtual Leased Line
VPLS Virtual Private LAN Service
VPN Virtual Private Network
WDM Wavelength Division Multiplexing
-
Strategic Industries | Strategic White Paper12
Fai LamSenior ManagerAlcatel-Lucent
In the Alcatel-Lucent IP Division, Fai Lam is responsible for
the marketing of IP/MPLS communication solutions, with a current
focus on industry markets, including utilities, transportation and
government.
Fai,whojoinedAlcatel-Lucentin1996,hasover18yearsexperienceintheICTindustry,andhispositions
have included product development, product line management,
business development and
marketing.FaiholdsaB.Eng.(ElectricalEngineering),fromtheUniversityofVictoria,Canada;anMBAfromtheUniversityofOttawa,Canada;andisaRegisteredProfessionalEngineerintheProvince
of Ontario, Canada.
Special thanks to the following for their key contributions to
this white paper: Albert Lespagnol, Dave Richards, and Annelies Van
Moffaert, Ph.D.
For more information about Alcatel-Lucent IP/MPLS products and
migration services, please visit www.alcatel-lucent.com or contact
your Customer Team representative.
-
www.alcatel-lucent.com Alcatel, Lucent, Alcatel-Lucent and the
Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other
trademarks are the property of their respective owners. The
information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained
herein. Copyright 2010 Alcatel-Lucent. All rights reserved.
SBG5677100802 (10)
1. Introduction2. Business and network requirements2.1
Brownfield or greenfield2.2 Multiplicity of services2.3 Dedicated
networks or a single multiservice network2.4 Reliability
(protection), availability, maintainability, safety (RAMS)
requirements2.5 Traffic-engineering requirements2.6 Security
requirements2.7 Operational requirements
3. Network technologies3.1 SDH/SONET overview3.2 IP/MPLS
overview
4. Migrating from SDH/SONET to IP/MPLS4.1 Phase 1: Adding
IP/MPLS routers to the SDH/SONET infrastructure4.2 Phase 2:
Switching TDM services onto the IP/MPLS infrastructure4.3 Phase 3:
Removing the SDH/SONET infrastructure and introducing WDM
5. Conclusion6. Acronyms7. Authors