Unattended Resilience and Provisioning with ASON/GMPLS

A step-by-step rollout based on market demand and technology development

A white paper issued by: Siemens Communication Fixed Networks Transport

Summary
As networks become larger and more complex, managing the network efficiently, with the level of response that customers demand, is a constant challenge. Network operators responsible for hundreds of diverse nodes need the ability to respond dynamically when failures occur or to provision a service, without the delays associated with configuring the network manually. Self-managed networks based on standards are a business imperative, using unattended control mechanisms that span the equipment and networks of multiple vendors. Automatically Switched Optical Network (ASON) together with Generalized Multi-Protocol Label Switching (GMPLS) provide an architecture and suite of protocols that enable automatic provisioning of network resources in multi-technology, multi-vendor optical networks. Together, they enable a level of unattended management across multiple domains that cannot be achieved by traditional network management systems used to support the equipment of individual vendors. This paper examines ASON/GMPLS market trends and technology developments, and how the Siemens roll-out strategy aligns with both. The paper begins with a brief introduction to ASON, and GMPLS, as well as related standards that together enable unattended switching and control. An example then illustrates how operators might use the technology to offer attractive new services to their customers. Finally, the paper examines the Siemens portfolio and implementation strategy, including the role of the transport network management system in bringing ASON intelligence to layers where a GMPLS control plane is not available. For network operators, the approach enables end-to-end ASON automation today, and an efficient transition to self-managed networks.

Contents

Introduction 1. 2. 3. 4. Benefits of ASON/GMPLS Application Example: Automated Resilience Services Where does ASON/GMPLS Make Sense? (and When?) Siemens Strategy for ASON/GMPLS

2 3 4 7 9 12

Conclusion: Evolving to Agile Networks

Introduction
The development of a standard framework for unattended network management has been a collaborative effort by three different standards bodies:
ASON is an architecture that enables automated switching in multivendor/layer transport networks. GMPLS is a suite of protocols for implementing an ASON control plane. It extends MPLS protocols with additional labels for switching in SDH and DWDM networks. The UNI and E-NNI protocols enable end-to-end provisioning across multiple network layers and domains.

ASON is an architecture defined by the International Telecommunications Union Telecommunications (ITU-T) that enables automated switching in multi-vendor transport networks spanning optical and electrical layers. A network administrator can specify the start point, end point and required bandwidth, and the ASON intelligence within the network elements automatically provisions the path through the network, configuring the cross-connects and allocating bandwidth for the requested service. Changes to the network, such as new nodes, are discovered automatically without requiring intervention by the user. The ASON architecture defines three different planes for network transport, control and management: The transport plane includes all the network elements and fibers that make the physical connection for traffic to flow. The control plane is where ASON brings intelligence to an optical transport network, in the form of middleware that takes control of the network based on policies defined in the management plane. The control plane discovers the network topology, distributes connection requests through the network, allocates necessary resources and provides status updates back to the management plane. The management plane handles user requests for setting up, tearing down, modifying and monitoring connections through the optical network, as well as management of the other two planes. This function is performed by an ASON-enabled network management system.

GMPLS is a suite of protocols for implementing an ASON control plane on optical network elements, as defined by the Internet Engineering Task Force (IETF). It extends MPLS protocols developed for packet switching with additional labels for switching in SDH and DWDM networks. GMPLS provides the intelligence that allows network elements to automatically implement policies specified in the network management system. Where a network management system requires intervention by an administrator (for example, to allocate additional capacity), a GMPLScontrolled network is able to act on its own, dynamically configuring endto-end circuits across multiple layers and equipment types. While in theory, other protocols could emerge for implementing ASON, no other approaches are currently used or envisioned. Therefore people tend to use the terms ASON and GMPLS synonymously, even though one 2

refers to the architecture and the other to an implementation of it. This is an important distinction because it is possible to reap some of the benefits of ASON before a GMPLS control plane is deployed. (This will be discussed later in this paper.) UNI and E-NNI: In addition to the ITU and IETF, there is a third standards organization involved, the Optical Internetworking Forum (OIF), which has defined interfaces based on the ASON model to enable interoperability across disparate networks. These include the User-toNetwork Interface (UNI), enabling interconnection of client devices with network elements in the OTN, and the Exterior Network-to-Network Interface (E-NNI) for bridging multiple networks. Together, the UNI and ENNI protocols enable end-to-end provisioning across multiple network layers and domains. Figure 1 shows how these elements work together. A Layer 2 switch in the metropolitan area network (MAN) in the lower left needs to connect to a switch in a second MAN in the middle. The switch uses the UNI to signal to the ASON/GMPLS domain that a connection is needed. The control plane then establishes the requested connectivity. When the same switch needs to connect to a destination which cannot be reached by the GMPLS domain, the connection is established using the network management system.
Figure 1: ASON/GMPLS Scenario. For the nonGMPLS domain, the network management system sets up the path; for the GMPLS enabled domain, the management system signals to the control plane to set up the path.

TNM

GMPLS domain MNS managed domain

UNI

MAN MAN MAN

1. Benefits of ASON/GMPLS
Implementing ASON/GMPLS enables agile networks that allow operators to be fast on their feet in response to error conditions or service requests. Operators can offer new services such as automatic restoration and end-to-end bandwidth on demand, while reducing manpower and other costs. Benefits include:

ASON/GMPLS allows to reducte operational cost through automating processes, to reduce capital cost through more efficient network utilization and to increase revenues through fast and flexible service provisioning.

Reduced Op-Ex (automated processes replace manual intervention) Ability to set up and release connections automatically Topology auto-discovery Rapid circuit provisioning, including multi-vendor scenarios

Reduced CapEx (through more efficient network utilization) Meshed restoration (automated resilience mechanisms based on meshed restoration consume fewer network resources than traditional 1+1 protection) Resilience against multiple failures (these become more likely as traffic volumes, range of applications, number of network nodes and distance between connections continue to grow) Automated, real time resource management Automated traffic engineering (e.g. load balancing optimizes equipment usage and traffic volumes)

Increased revenue (through fast and flexible service provisioning) Bandwidth on demand Different classes of resilience in the transport layer

2. Application Example: Automated Resilience Services

Lets see how some of these benefits can be achieved in a sample application. Automated protection and restoration the overall term is resilience is a main driver for ASON, because the capabilities are so clearly superior to traditional protection mechanisms. In addition to fast restoration in case of failure, ASON enables operators to offer a new class of resilience services to their customers, allowing much greater differentiation than traditional methods, which amount to either full 1+1 protection, or no protection whatsoever. Various options for automated resilience can also be much more economical than traditional 1+1 protection, which requires reserving a dedicated backup path through the network, as well as manual intervention by an engineer to implement it. For example a leading U.K. carrier has found that it can run its business using about 30% fewer resources for automated resilience than their previous 1+1 protection. This figure is representative for Tier 1 and 2 operators worldwide.

Different resilience mechanisms such as dynamic source reroute, pre-planned shared restoration and GMPLS based 1+1 protection can be combined to offer a range of novel protection services.

GMPLS automated protection enables a variety of resilience options, involving different tradeoffs of restoration speed, cost and protection certainty: Dynamic source reroute (reroute upon failure): The slowest, lowest level of protection, which involves looking for a new connection when the primary connection is lost. Resources for the new connection will be allocated assuming they are available. This approach saves the most network resources, but takes the most time of the different options. Also, since there are no preallocated or defined network resources, there is no guarantee that a path will be available when it is needed. Pre-planned shared restoration: The backup path may be preestablished, but resources are not allocated. The same resources can be used as back-up for multiple traffic demands to fall back on in case of trouble. Once the backup path is switched in the event of failure, alternate resources are brought into place to protect the remaining traffic paths. GMPLS-based 1+1 protection: provides the fastest, most assured level of protection, maintaining a dedicated back-up path which is automatically activated using GMPLS. This mechanism is equivalent to conventional 1+1 protection.

The combination of these three mechanisms sets up a range of protection services that an operator can sell to their customers as part of a service level agreement. For example, a hypothetical suite of resilience schemes might look something like this: Unprotected Bronze service (Dynamic Source Reroute, restoration time: < 1s) Silver Service (GMPLS based 1+1 protection, restoration time: < 50 ms) Gold Service (Protection against double failure (see below), permanent pre-planned shared restoration plus reroute, restoration time: first failure : < 100 ms; second failure: < 1s) Diamond Service (Protection against double failure, permanent GMPLS based 1+1 protection plus reroute, restoration time: first failure : < 50 ms; second failure)

Protection Against Double Failure Protection against double failure has traditionally been economically unfeasible because it required two distinct back-up paths, in effect 1+1+1 5

Resilience mechansims such as source reroute or re-etablishing a shared back-up path after the occurrence of the first failure allow to provide protection against double or even multiple failures.

protection. Since the backup path is usually longer than the working path, such a scenario consumes too many network resources and is rarely implemented in working networks. One of the key benefits of GMPLS protection is the ability to offer economical protection against double failure by automatically configuring backup paths through a mesh network. This is good news for network operators dealing with continually growing traffic, the greater risk of multiple failures and more severe consequences if they occur. Carriers are also able to implement new strategies for dealing with double failures, based on the logic that double failures are fortunately rate, but single failures happen quite frequently. Therefore it makes sense to protect against the first failure with a very fast reaction time, while a second failure can be addressed with a slower restoration approach such as a dynamic source reroute that requires fewer network resources. Figures 2 and 3 provide an example of a Gold restoration service with multiple levels of resilience in a GMPLS-enabled domain. In this example, resilience involves a combination of pre-planned restoration paths (which are shared by multiple working paths) along with dynamic reroute.
H

Figure 2: The primary working path (red) and the first preplanned restoration path (green). (The restoration path is a shared protection link shared by multiple working paths.)

F C Edge Node A UNI A NNI B E Edge Node

D G

G1

Traffic flow Pre-planned shared restoration path

Siemens hiT 7070/7080 MSPP

Characteristics:

The following sequence illustrates how an automated restoration service might work as multiple failures occur: A failure occurs in the primary path (such as between nodes H and G in Figure 2.) Traffic from the former working path automatically switches to a preplanned restoration path. Meanwhile, a new pre-planned shared restoration path is activated. Additional restoration paths can be set up to handle additional failures as often as the operator chooses, as long as resources are available. When a second failure occurs in the new primary path, traffic automatically switches to the second preplanned restoration 6

path. In this example, no additional disjoint restoration paths are available. When a third failure occurs, dynamic source reroute is initiated upon receipt of a failure indication signal to find a new path through the network.

Figure 3: The link between node A and G is 1+1 protected as long as defined paths are available. When a third failure occurs (in this case between nodes B and E), no additional restoration paths are available in this example. Upon receipt of a Failure Indication Signal (FIS), dynamic source reroute is initiated to find a new path through the network.

F C Edge Node A UNI A NNI Edge Node

FI
B E

G1

Traffic flow Pre-planned shared restoration path FIS: Failure Indication Signal
Siemens hiT 7070/7080 MSPP

Characteristics:

3. Where does ASON/GMPLS Make Sense? (and When?)

There are two main applications where ASON will have significant benefits in the near term (through 2008): automated restoration and automated provisioning. However, technology developments and market conditions are considerably different in the SDH and DWDM layers, dictating different deployment strategies and timeframes for these different areas of the network. Automated Restoration (Resilience) Automated restoration requires a mesh topology (multiple potential paths between two endpoints), rather than a ring network or a number of individual point to point links. This involves installing a cross-connect switching matrix an inherent feature of mesh networks. In SDH networks, electrical switching technology is widely available and re-configuring a network to a mesh is relatively straightforward. The fewer number of network elements that have to be upgraded, the smaller the investment. The VC-4 core grooming layer has by far the fewest number of network elements in SDH networks, one main reason which it has been the logical area for the first wave of ASON/GMPLS deployments. The other reason is because potential benefits are greatest in the core 7

Preconditions for an introduction of an ASON/GMPLS control plane are a meshed network topology for restoration and a high traffic churn for automated provisioning.

layer, since it has the most traffic, and the greatest demand for protection and other automated services. In DWDM networks, implementing a mesh network requires installing photonic cross-connects for switching channels between fibers as well as installing ROADMs (re-configurable optical add/drop multiplexer) for adding or dropping traffic. However, photonic cross-connects are just starting to see commercial availability, with resulting very high prices. There are also other challenges that complicate mesh restoration in optical networks, such as the availability and high cost of spare bandwidth for resilience. Therefore, installing a GMPLS control plane in the DWDM layer to support mesh restoration does not make economic sense until prices drop significantly both for switching elements as well as bandwidth. Automated Provisioning To make economic sense, unattended provisioning requires high traffic churn, where services are being provisioned, torn down, or redirected at a high rate. This is common in SDH core grooming networks, which typically have thousands of different services competing for bandwidth. However, in DWDM networks, the number of services is usually much lower (20 per node might be considered high) for tasks like aggregating the SDH layer or connecting routers in a backbone network (ISP peering). Without a critical mass of services, there is usually not a compelling need for automated provisioning.

These preconditions are met in VC-4 core grooming and metro core layer but not yet in the DWDM layer.

Automatic provisioning of network services also requires the availability and affordability of idle network resources needed to create the automated services. This is more likely to be an issue in DWDM networks, since with the current high cost of bandwidth, it is expensive to leave idle (and not earning revenue). Because of current pricing models and limited number of services, automated provisioning in DWDM network, while technically feasible, is not yet economically viable, except in a few limited applications. The general introduction of GMPLS into DWDM networks will be appropriate when: DWDM relevant transport (2.5G and above) achieves a critical mass of services and photonic mesh topologies DWDM networks evolve from point-to-point to a photonic mesh (ROADM, PXC, tunable lasers and filters) Pre-provisioning of channel equipment and availability of idle network resources makes economic sense, since without available resources, automatic provisioning capability (bandwidth on demand) is pointless. There is a lower-layer client asking for the service. Otherwise, fast provisioning is easily accomplished using a good network

management system. (This is another reason why it makes sense to first deploy a GMPLS control plane in the VC-4 layer.) In contrast to DWDM, these conditions have already been met in the VC-4 core grooming switch layer, and therefore ASON is widely implemented in this layer. These conditions are also met in the metro core layer, where the first implementations are underway.

4. Siemens Strategy for ASON/GMPLS

The Siemens deployment strategy for ASON/GMPLS includes an ASON-enabled product family, a phased roll-out for the control plane and an advanced network management system that provides ASON automation in layers where the control plane is not yet available.

The Siemens deployment strategy for ASON/GMPLS includes an ASONenabled product family, a phased roll-out for the control plane and an advanced network management system that provides ASON automation in layers where the control plane is not yet available. ASON-Enabled Product Family With its SURPASS family of multi-service provisioning platforms, Siemens provides next generation SDH and multi-haul DWDM systems for building converged transmission networks. All models are ASON enabled equipped with automated switching capabilities that are invoked using the GMPLS control plane (if available) or with the Siemens transport network management system. VC-4 Core Grooming Layer: The SN 16000 optical switching platform is an OEM product from strategic partner Sycamore Networks that is fully integrated into the Siemens Transport Networks portfolio. The unit concatenates VC-4 signals to deliver end-to-end services while supporting meshed restoration and fast service provisioning. VC-4 Regional/Metro Layer: The SURPASS hiT 7070/7080 handles the full range of network applications in the regional and metro core. It can be configured as an UHC feeder, a terminal multiplexer, an add-drop multiplexer, a cross-connect or a terminal in many different point-to-point, multipoint, chain and ring topologies. DWDM Layer: The SURPASS hiT 7300/7500 handles all types of services in a single multi-haul DWDM platform. Building blocks include terminals, optical line repeaters, OADMs and ROADMs to accommodate any network size and architecture. Photonic crossconnects are also available to create a reconfigurable meshed topology.

The Siemens deployment strategy consists of three stages: Introduction of a control plane into the VC-4 core grooming layer since 2005, into the metro core layer in 2007 and into the DWDM layer in 2008.

Three-Stage Control Plane Roll-Out Siemens is introducing a GMPLS control plane in three stages, targeting network layers where automated resilience or provisioning can generate immediate revenues, based on technology readiness and market demand. Step 1: VC-4 core grooming layer (available since 2005) Virtually all initial control plane deployments have occurred in the SDH VC-4 grooming layer of national backbone networks. As mentioned earlier, there are two main reasons for this: far fewer network elements that require upgrading than lower SDH layers, and greater potential benefits due to the concentration of traffic. (Wide deployment in this layer has already occurred among tier 1/2 customers in the U.S., Europe and Asia Pacific.) Step 2: Metro core layer (available January 2007) More and more carriers are undergoing field trials of a control plane in the SDH metro core, and some vendors have already started commercial roll-outs. With its SURPASS hiT 7070/7080, Siemens offers a multi-service provisioning platform for regional/metro networks, with a GMPLS control plane commercially available starting in January 2007. Step 3: DWDM layer (available 2008) ASON/GMPLS in DWDM networks is still in the experimental stage. Unlike SDH/SONET networks, which have been around for years and have evolved into mesh topologies, DWDM topologies still are mostly peer-to-peer or ring based. There is also a lack of critical mass (in number of services, in available bandwidth, in distribution of equipment) that limits the feasibility of automated provisioning in most cases. Accordingly, Siemens is deferring deployment of a control plane in the DWDM layer until 2008, when the technology and market is expected to be ready for it.
Setting the Pace with ASON/GMPLS: The Siemens ASON/GMPLS strategy is framed by deep involvement in technology development, definition of standards and pilot projects since the late nineties: GMPLS live demos > CeBit 2001 > UNI interop test at SuperComm 2001 > ECOC 2001 BMBF projects (German ministry of education and research) > KOMNET 09/99 - 04/02: Metro ASON field trial > VIOLA 05/04 05/07: National multi-vendor ASON network EU funded projects > LION: Layering in Optical Networks (01/01 - 12/02) > CAPRICORN: Call Processing in Optical Core Networks (09/01 - 02/03) > NOBEL: Next generation Optical network for Broadband in Europe (01/04 12/05) GMPLS control plane pilot for photonic layer (COPLA) GMPLS control plane for metro core GMPLS control plane available in core grooming switch SN 16000

10

Transport Network Management System

The Siemens Transport Network Management System (TNMS) offers ASON intelligence such as auto-router for finding a path through the network and is able to take advantage of automation within the network elements even in layers where a control plane is not available.

The Siemens Transport Network Management System (TNMS) provides a central management system for Siemens complete optical transport portfolio (SDH, MSPP, core switches, DWDM). Together with the Siemens network elements, it offers more extensive ASON intelligence than other management systems, including an auto-router for finding a path through the network, point-and-click end-to-end provisioning, the ability to configure restoration routes and the ability to remotely switch wavelengths by software command. The TNMS is able to take advantage of automation within the network elements (for setting up a link, tearing down a link, commissioning equipment, etc.), even in layers where a control plane is not available. As a result, it can be used to automate endto-end service provisioning spanning all layers of the transport network, with the TNMS asking the control plane for the connection in the GMPLSenabled layers. Figure 4 illustrates the Siemens ASON portfolio in different layers of the transport network. The VC-4 core grooming switch and the metro core MSPP provide a GMPLS control plane, enabling automated restoration and service provisioning via UNI and multi-vendor interoperability via ENNI. The long-haul DWDM platforms are enabled with ASON intelligence in preparation for a future control plane rollout. The TNMS is shown managing the complete optical transport portfolio (SDH, MSPP, core switches, DWDM). As mentioned above, the TNMS allows much of the ASON automation built into the Siemens network elements to be enabled in layers where the control plane is not yet deployed.

Figure 4: Siemens Portfolio for ASON

TNMS

ASON intelligence
SURPASS hiT 7500 SURPASS hiT 7300 SN 16000

UNI NNI ASON Intelligence UNI

SURPASS hiT 7070/7080

GMPLS control plane

GMPLS control plane

ASON Intelligence Siemens network elements together with the TNMS provide ASON intelligence and control plane automation for planning, provisioning and maintenance activities. Examples include: Automated end-to-end provisioning Automated routing of protection paths Automated DCN routing (OSPF) Automated IP address assignment Automated equipment discovery Automated configuration of tunable laser

SURPASS hiT 70xx

CP

GbE

11

Conclusion: Evolving to Agile Networks

The ASON/GMPLS framework enables self-managed network interoperability and provisioning across multiple network layers and domains. Operators can provide the immediate service that customers increasingly demand and expect, without a corresponding increase in manpower. Siemens offers proven products, a clear implementation strategy and extensive experience to help operators make a rewarding transition to ASON. We provide a GMPLS control plane in the core grooming switch and regional/metro layers, together with ASON intelligence in the DWDM layer enabled by the TNMS. In the near future (2008), well have the control plane deployed in our long-haul DWDM platforms as well. The agile network is coming to life, and Siemens is helping our customers take advantage of it.

www.siemens.com/surpass
All rights reserved. All trademarks used are owned by Siemens or their respective owners.

Siemens AG 2005 Siemens AG Communications Hofmannstrae 51 D-81359 Mnchen

12