Beruflich Dokumente
Kultur Dokumente
Objective
This is a non-proprietary white paper authored by network operators.
The key objective for this white paper is to outline the benefits, enablers and challenges for
IP and Optical convergence and the rationale for encouraging an international collaboration
to accelerate development and deployment of interoperable solutions based on high
volume industry standard data and control plane solutions.
Page 1 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
Table of Contents
1 Executive Summary 3
2 Introduction 5
2.1 Definitions 5
2.2 Challenges to be addressed 7
3 Use cases for IP/Optical Convergence 9
3.1 Packet and Optical data plane integration 9
3.2 Packet and OTN integration in the Core 11
3.2.1 LSR switching-enabled optical core 11
3.2.2 Ethernet switching-enabled optical core 12
3.2.3 LSR router by-pass 13
3.3 Multilayer Control and Resilience 13
3.3.1 Automated IP/DWDM network operation 13
3.3.2 Multilayer resilience 15
3.4 Multilayer Planning and Management 18
4 Technology Enablers for IP and Optical Convergence 19
4.1 Pluggable Optics 19
4.2 Black Link 20
4.3 Control plane 21
4.4 SDN 22
4.5 Hybrid switching matrix 22
5 Recommendations /Call for action 23
6 Acronyms 24
Page 2 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
1 Executive Summary
The main goal of this white paper is to identify the most relevant use cases and technical
requirements for IP&OC (IP and Optical Convergence). IP&OC can be achieved through
multiple angles: data plane integration (colored interfaces), multilayer control and
resilience, multilayer planning and management.
All of these pieces are not necessarily put in place at once. A network operator, making its
way to IP&OC, does not need to deploy these capabilities all at once. The network type,
topology and size, the network operation processes, the network life cycle (in place, to be
replaced, new deployment) and the network migration steps will have a clear influence on
the need for one, several or all of these capabilities. At the end of this document, a table
provides the interest level per contributing network operator for each of the identified use
cases.
Carriers are at a crossroad with their IP and Optical access, aggregation and core
networks. Beyond the need to bring new services and service models faster to the market,
they need to cope with the steady growth of traffic coming from IP services and content-
centric applications. This is done using easier to manage infrastructures that radically
reduce the operational complexity. Minimizing CAPEX and OPEX for these infrastructures
is another point of emphasis for the operators. Additional influences include cultural
changes related to convergent technologies and architectures within operators
organizations. Technological advances enable more flexible and service-aware networking
(e.g. SDN & NFV) beyond the static connectivity models of the past.
Next-generation multi-service networks have to provide high bandwidth to interconnect
data centers, while, at the same time, providing for simplified operations and easing
capacity upgrades. Beyond the common approach to overprovision the network by
increasing capacity and installing more forwarding capacity, new ways of optimizing the
design are required to better accommodate traffic growth.
Most of todays existing Core and Backhaul transport networks rely on an optical transport
layer based on WDM. Thanks to optical technology evolution, we are migrating towards an
agile transparent WDM infrastructure based on ROADM. IP/MPLS network stands out as
the main client layer of this flexible optical infrastructure.
Depending on different business and service models, there are two main core network
architectures all around the world:
Packet over DWDM networks where OTN is exclusively used for framing purposes.
Packet/OTN/DWDM networks where transit traffic is mainly groomed/switched by OTN
multiplexing/switching network elements.
In both cases enhanced control, planning and management mechanisms shall enable a
better coordination between the transmission layer and its client layers (mainly IP),
improving network efficiency, thus contributing to TCO reduction. In particular, multilayer
resilience schemes are expected to minimize packet and optical back-up resources.
Data plane integration (i.e. colored optical transceivers in routers and packet switches) will
also be a major step towards higher network efficiency in Packet over DWDM networks.
All network operators signing this document, independently of their particular core network
architectures, declare their interest in IP and Optical convergence, including optimized
network control and planning.
Page 3 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
Different use cases for both data and control plane multilayer integration are described in
this document. However, current commercial solutions for IP and optical convergence, in
both data and control planes, present several shortcomings in terms of multivendor
interoperability which are currently limiting their application to single vendor networks.
This paper presents a set of technology enablers which would allow network operators to
overcome these shortcomings and allow a widespread introduction of integrated data and
control plane solutions in multivendor networks:
Black Link:
The existing standard ensures interoperability up to 10Gbit/s. For higher data rates,
standardized application codes (ITU-T G.698.2) are still missing. Multi-vendor
interoperability for 100G is less a technical issue (first interoperability tests have already
been successfully carried out); it is a question of willingness of vendors and operators to
move forward towards a new paradigm operating carrier networks. It is acknowledged that
the achievable distance is smaller for a multi-vendor interoperable interface as compared
to a proprietary interface. However, the target distance for a standardized interface should
not be too small from the very beginning. Black Link standardization and implementation
enables data plane integration in IP/OTN/DWDM networks.
Pluggable OTN transponders:
The integration of OTN framing, FEC and digital signal processing (DSP) into pluggable
optics would enable multivendor interoperability (e.g. compatible pluggable optics
integrated in different packet vendor nodes) and to extend data plane integration to long
reach deployments. This technology in combination with the Black Link approach could
enable network operators to have full interoperability vendor maps.
Multilayer control plane:
Multilayer operation, optimization and resilience mechanisms do not depend on data plane
integration but require multilayer control support. Most packet and optical system providers
are including basic UNI implementations in their control plane features. However, these
implementations are almost useless unless they are complemented with additional
standard control plane features enabling the use cases proposed in this document:
multilayer resilience, automatic network provisioning, alien wavelength restoration, etc.
Multivendor SDN:
SDN can help operators to reduce the CAPEX and OPEX in the networks, allowing greater
network flexibility, optimization of resources and the reduction of complexity in network
operation. However, SDN solutions currently in development are still rather monolithic, and
not well adapted to heterogeneous network environments in service provider networks.
There is a need for modular SDN architectures, based on open and standardized
interfaces between different SDN modules, allowing for a free choice of components and
suppliers. Open and standardized interfaces allow removing or reducing the dependency
on proprietary element management systems, and solving the problem of vendor lock-in for
the operators.
Page 4 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
2 Introduction
Main technical aspects addressed in this paper are
1. Packet and optical data plane integration by the use of fixed/tunable colored DWDM
interfaces into the IP routers and switches.
2. Multilayer control and resilience: enabling automated interworking between both IP
and optical network control functionalities (e.g. resilience mechanisms). In the case of
packet-optical integration, for example, the multi-layer control plane allows to automatically
select the wavelength used by the integrated transponder.
3. Multilayer planning and management to handle both IP and optical layers as a
seamless network where services are planned with the right path across layers (optimizing
the resources used, the cost and the latency) and with the right level of end-to-end
recovery (optimizing SLA conformance).
2.1 Definitions
Page 5 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
Multilayer planning
With the IP layer being the main client of the optical network, the optimization of one layer
independently of the other layer is no longer viable if network operators want to achieve a
global optimization. Today, this multi-layer optimization is done rather manually based on
extraction of data from each layer and by using tools with limited scope (single layer, single
vendor).
Page 6 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
IP&OC would help network operator to handle both layers as a seamless network, where
services are planned with the right path across layers (optimizing the resources used, the
cost and the latency) and with the right level of end-to-end recovery (optimizing SLA
conformance). Tools with an entire view on both layers would also help in running fault
simulation scenario and analysis on a global context.
Control plane
IP link provisioning over optical networks is a basic operation which typically requires long
operational workflows (see Figure 2).
Page 7 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
In order to solve this problem, most packet and optical system providers are including
GMPLS UNI in their control plane features. GMPLS UNI, as defined in RFC4208 allows
specifying the explicit route of the path. That is, the packet router can include the details of
the route. However, how does the packet node know the details of the route to be
requested is not standardized yet. Thus, with basic standard UNI either the end points
(source and destination) are specified, or a route (obtained by external means) is provided.
There is no way to include additional constraints in the UNI request.
Page 8 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
Figure 3 shows the network scenario based on optical fiber rings to interconnect between
Aggregation exchange Routers (AXR) and Packet Core Routers (PCR). AXRs aggregate
business and residential customers using 100GBit/s interfaces towards the main PoP-
Locations.
Page 9 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
AXR PCR
EDFA
Coupler/ Coupler/
Splitter Splitter
EDFA EDFA
Network
Coupler/ Coupler/
Splitter Splitter
EDFA EDFA
EDFA
PCR
AXR
Figure 3: Passive optical bus infrastructure based on splitters/couplers providing
connectivity to data centers
Page 10 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
operate networks will foster the integration on the control and management perspective as
well.
In todays metro core node architecture, connectivity to remote locations in distant cities is
achieved through the use of two complementary platforms that are completely physically
and logically separate:
- The long-haul optical platform in charge of switching wavelengths in the optical
domain (ROADM function) as well as circuits in the electrical domain (OTN cross-
connect function)
- The core packet platform in charge of switching MPLS-labeled packets also in the
electrical domain (Label Switch Router function)
In the 2 to 3 year future we envision that these two platforms will collapse into one single
platform with the optical platform being enhanced to also support MPLS switching.
On the OTN function it is likely that OTN switching, as opposed to the simpler OTN
multiplexing, will be required for some time. This is due to the need to efficiently deal with
high-speed leased line services (e.g. 10Gbps today) that the MPLS packet transport layer
will not be able to transport because of scaling limit, even when considering the statistical
multiplexing benefit.
Figure 4 shows metro areas connecting to the long-haul optical core enhanced with LSR
packet switching capability.
(metro B)
L2 CPE
L2 service L2/L3 PE LSR/P
L2 access & LSR-enabled
aggregation optical core
(metro A) (metro C)
L2 service
OTN switching
Fill-in the high speed waves
Packet switching
MPLS switching (LSR)
No LER (VPN, VPLS, GRE, MC), no BGP
CP protocols (IS-IS, OSPF, TE, LDP, RSVP)
Page 11 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
In terms of expected benefits, reducing the number & types of physical platforms and
simplifying the overall service architecture shall make the operations easier; improve the
various lead times to deliver and maintain the services; reduce the service unit costs;
reduce the operational and capital expenditure costs.
Another side benefit envisaged with packet and optical switching integration in the core is
the multi-layer integration of the control plane itself. The physical integration of optical and
packet switching functions will enable a true multi-layer control plane (single IGP protocol,
single optical & packet GMPLS provisioning protocol, etc.) that will also results in simplified
operations.
The described IPoDWDM solution in section 3.1 achieves cost reduction by eliminating the
grey optics and the transponder used in separate router and DWDM systems. On the other
hand, another approach called POTN/WDM (packet and optical transport network) is also
interesting for operators who require more flexible migration in terms of IP and TDM
services.
With the ability to accommodate multiple services (both IP and TDM) in a single integrated
platform, the POTN/WDM solution transforms separated traditional WDM transport and IP
core networks into a single integrated transport core with multilayer switching and services.
The POTN/WDM basically consists of three layers PTN, OTN, and WDM, and provides
scalable and flexible cross-connection of high-performance PTN/OTN switching through its
universal switching fabric. First, the PTN (packet transport network) layer implementing
MPLS-TP, PBB-TE, or pure Ethernet supports grooming IP services at port or sub-port
level (e.g., VLAN) with its standard OAM and protection mechanisms. Additionally, its
carrier-Ethernet capabilities support a wide range of services such as E-Line, E-Tree, E-
LAN and E-Access based on the MEF (Metro Ethernet Forum) Carrier Ethernet
certifications. On the other hand, the OTN (optical transport network) layer efficiently
multiplexes both packet and TDM services with higher client signal rates (1G, 2.5G, 10G,
40G, 100G). With more enhanced OAM and protection schemes than legacy
SONET/SDH, OTN provides sub-lambda grooming for maximizing wavelength utilization
and greater flexibility. Finally, the WDM (wavelength division multiplexing) layer offers high
bandwidth capacity to meet traffic growth with its reconfigurable optical add-drop
multiplexing (ROADM) technology where client service can be transported over any
wavelength in any direction. The highly efficient photonic layer enables operators to lower
transport network costs by eliminating unnecessary optical-to-electrical-to-optical (OEO)
conversions.
One addresses that the multi-layer integration of the POTN/WDM approach is somewhat
complicate by the multi-layer architecture compared to other IP and optical integration
solutions such as IPoDWDM. However, the POTN/WDM has the flexibility to support both
packet and TDM services with abundant OAM and protection schemes provided at each
layer. Actually, the integrated universal switch fabric does not separate OTN and PTN
switching. Rather, it is capable of performing native packet and circuit switching
Page 12 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
In summary, the POTN/WDM integrates both packet and optical capabilities including
carrier-Ethernet, OTN, ROADM, and DWDM all in a single box. This multi-layer integration
effectively reduces TCO (total cost of ownership) compared to traditional multi-box core
network designs and increases revenue opportunities by offering customers more flexible
network services.
Another potential use of the packet and OTN integration in the Core is the possibility to
transform the OTN+WDM network as a P router. If a transmission network is used as a P
router, then direct PE-to-PE connectivity can be achieved. This full-mesh per say
provides minimum RTT on PE-to-PE connectivity while minimizing the CAPEX on the
transmission network since there is no need to deploy nation-wide lambda (for PE-P-PE
connectivity) to interconnect two adjacent region PEs.
Page 13 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
IP and optical layer, so the network operator can configure the network in a faster way and
reduce the costs of this process.
Page 14 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
shall note that the required OTN switching function can be embedded in the WDM
Platform. The bandwidth used on the transport network can be adjusted dynamically with
no traffic hit thanks to Hitless Adjustment of ODUflex (HAO), through IP and transport
Control plane interactions.
Convergence in this case improves flexibility, and provides transmission bandwidth sharing
through different clients (higher layer / Business customers).
Page 15 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
One peculiarity exists for backbone networks, which is not often mentioned but
nevertheless is an important property and in practice often applied by operators. In reality
the network infrastructure, as shown in Figure 5 above, is physically implemented twice in
order to guarantee failure robustness. That means for resilience purposes the operator
builds a so-called A and a B variant of the IP core network which mutually protect each
other. As a consequence, every given IP PoP consists of an A and a B site. For example,
the doubling strategy has an impact on working and backup paths. In case of a link failure
in the A network, there always exists a straightforward backup route in the B network.
Both paths have to be mutually disjoint, though they follow similar geographical routes
through the country. Therefore, also latency is usually similar.
This network architecture requires three main ingredients at least:
Firstly, an agile DWDM layer with colourless and directionless, ROADMs provides
faster service provisioning. Those photonic devices are also used for resilience
switching at the physical layer (L0).
Secondly, an integrated multi-layer packet-optical control plane offers a software-
based flexibility including path selection in case of a network failure and signalling
functionalities. An efficient integrated CP solution also comprises just the right
amount of information exchange between the packet and optical layer. In the early
days of the network, operators tend to run some processes manually in order to
gain experience before migrating towards a fully automated control as the final goal.
Thirdly, a standard interface allows configuring all IP routers using the same
protocol. The advent of multi-layer control plane may ease the configuration of the
MPLS and the GMPLS equipment. IP layer services also require configurations that
go beyond control plane functionalities. After a failure, adding new routes or
changing the metrics in the IP layer can help to optimize the IP topology.
Page 16 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
Considering interactions between IP and transmission CP, higher layer has the possibility
to set up automatically some adjacencies in case of network failures, providing automated
network reconfiguration. This use case potentially applies to any IP network relying on a
flexible WDM / OTN network.
User-to-Network Interfaces (UNI) between IP and optical networks enable requesting for
connections on demand, after a failure happens in the IP layer. This allows minimizing the
number of IP resources for backup purposes.
Page 17 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
support an optical restoration when there is a failure in any segment of the transport
network.
IP Node 1 IP Node 2
router router
vendor vendor
B B
T R
x x
Vendor Vendor
B R T B
x x
Page 18 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
When Multilayer Control is introduced new paradigms may be adopted in terms of circuit
design depending on the adopted model (peer, overlay, border, augmented) and the
adoption of Packet/Optical data plane integration. The various combinations of control
interconnection with data plane integration must be carefully evaluated to fully understand
their impact on management aspects and how their behaviors impact on a carrier
organization. E.g. if we consider the Border Multilayer Control model with Packet/Optical
Data Plane Integration it is likely that layer 2/layer3 components of the IP device have all
information required to route the light paths across the DWDM network. Depending on
carrier specific requirements, the knowledge of routing must be provided to the DWDM
management system that needs therefore to be able to access such information onto the
IP device beyond the layer 0/layer 1 components.
A further level of management integration, not considered in this document, is related to
the fully integration of the management systems of the two technologies (IP and DWDM)
that can bring to a better overall manageability of the network. The complexity of this
integration is quite high because the different paradigms this network operate and it is not
clear how deep this integration can be pursued. From a practical point of view it should be
carefully evaluated the impacts of likely increased OPEX in qualifying the overall integrated
management system because traditionally the IP layer is faster changing. Some examples
of proprietary integrated systems already exist on the marked but this implies to buy the
overall system from the same vendor (the entire IP and optical networks) that can
considerably impact the evolution of a carrier network. On the other hand, it is worth noting
the benefits of an integrated management system that can speed up and simplify the
provisioning process, the fault management and the planning process. A converged
management system is expected to simplify end-to-end multi-layers operations reducing
the global network TCO. Some manufactures have already in their offer management
platforms that cover both IP and optics segments in a single vendor environment and the
others are moving toward this solution. These unified platforms allow fast end-to-end
service provisioning, improves the visibility of multi-layer network and reduce the time
needed for troubleshooting. However this approach implies to use IP and transport
platforms from the same manufacturer, creating dependencies that constrain network
evolutions. Additionally, it brings a significant risk of increasing part of the OPEX, through
the different upgrades and associated release qualifications since IP Routers implies a
higher number of release updates than pure transport equipments.
Avoiding proprietary management system suite would favor the integration into a
converged OSS benefiting from open interfaces to IP layer and more specifically today to
transmission layer.
It is therefore recommended to start working on standard solutions to enable converged
network management systems.
Page 19 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
It would also allow mixed colored/grey scenarios where one of the light-path endpoints is a
colored pluggable while the other is a regular optical system transponder with a grey
interface towards the router. This would imply the use of GFEC (for interoperability
between the vendors) and may limit the maximum reach application scope to
metro/regional networks.
This synergy can be achieved by the concept indicated in Figure 8. Routers/switches are
connected to a layer- optical network (L-ON), i.e. to an optically transparent network
composed of fibers, optical amplifiers, OADMs, etc. According to the black-link (BL)
approach the line-side single channel DWDM optical interfaces SS and RS must be fully
standardized thus enabling data plane integration (in particular the elimination of grey
interfaces and related transponders) along with multi-vendor interoperability (because the
routers and the L-ON can be provided by different vendors A, B, C). An open access to
standardized reference points E1 at the ingress of the Optical Transmitter Interface (OTI)
and E2 at the egress of the Optical Receiver Interface (ORI) must be requested by
operators and ensured by the vendors in order to avoid a vendor-lock for integrated
coloured interfaces. The corresponding Ethernet physical interfaces (Eth Phy) have already
been standardized up to 100 GbE. The line-side BL optical interfaces SS and RS have
already been standardized up to 10 Gbit/s data rate in ITU-T G.698.2. The definition plus
specification of parameters for 100G BL application codes in G.698.2 is in progress.
Page 20 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
The approach indicated above is intended to satisfy the needs of all involved parties for the
use cases under consideration. In cases where ultra-long transmission distances are
required one may use just the interoperable interfaces E1 and E2 and connect there an
OTI/ORI from any vendor which can be implemented in the most efficient way by the
corresponding vendor. In cases of medium-reach distances coloured integrated BL
interfaces (with standardized parameters at SS and RS) without using transponders - are
expected to be very efficient. The network management (NM) plus control plane (CP) must
be sufficiently flexible to incorporate such different use cases and related implementations.
Page 21 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
4.4 SDN
Software Defined Networking (SDN) and network programmability are hoped to offer the
ability to direct application service requests towards the IP/MPLS network, which may be
converged with the optical layer. The claim of the SDN approach is to help operators to
reduce the CAPEX and OPEX in the networks, thanks to the optimization of the resources
and the reduction of the complexity in the operation of the network. However, the emerging
SDN controllers in the market are based on OpenDayLight, which is not adapted to current
heterogeneous network environments. Such SDN solutions are like black-boxes and their
deployments would lead to different problems for the operator: vendor lock-in (solutions in
the market are mono-vendor), lack of support with proprietary protocols, problems to
support end to end multi-vendor path establishment... There is a need for modular SDN
architectures based on standard interfaces between different SDN modules, which could
be implemented by different vendors, in order to solve the problem of vendor lock-in for the
operators.
Page 22 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
Table below summarizes the specific interest across the different Proposed Use cases
Telecom Italia
Telefonica
Bouygues
Orange
COLT
KDDI
CU
DT
Page 23 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
++ ++
Automated Operation
+ + + +
Adaptation to Traffic evolution
+ ++ ++ ++
Low cost Disaster recovery + +++ ++
6 Acronyms
Page 24 of 25
WHITE PAPER
IP and Optical Convergence: Use Cases and
Technical Requirements
Page 25 of 25