ASON-GMPLS Control Planes Overview

Converged and Optical Networks Sept 30th, 2008 Brussels Hans-Martin Foisel Deutsche Telekom

Outline

ASON/GMPLS control plane concepts Involved SDOs Architectural principles of control plane enabled transport networks Control plane enabled services Future transport network evolution Business impact of control planes Control plane deployments Summary

Components of Control Plane enabled Network Domains

Management plane
CP MANAGEMENT

DCN

CONTROL PLANE

Data plane

Intelligent TN introduce ...

A distributed Control Plane
Signaling protocols for dynamic setup and teardown of connections

Routing protocols for automatic routing

Building on concepts/protocols from the data world

Key Concepts Derived from the Data World

Distributed processing/knowledge/storage Directory services

Open Distributed Processing Standardized route determination and topology dissemination protocols Routing information exchange mechanisms

E.g., DNS, X.500

Flexibility in binding time decisions Difference between provisioning and auto-discovery Security based upon logical versus physical barriers E.g., authentication, integrity, encryption Differentiate between provisioning and more dynamic connection management Survivability Distributed restoration using signaling

E.g., RIP, OSPF, BGP, IS-IS/ES-IS

Leveraging Existing Protocol Solutions Caveats

Internet serving community of users with common goals and mutual trust: Classical Internet architecture When taking protocol solutions developed for the classical Internet, they bring along associated underlying principles and architectural aspects Commercialization of the Internet:
More Business Critical Infrastructure & Availability Requirements

Transport business & operational requirements:

Control plane architecture enabling boundaries for policy and information sharing

Outline

ASON/GMPLS control plane concepts Involved SDOs Architectural principles of control plane enabled transport networks Control plane enabled services Future transport network evolution Business impact of control planes Control plane deployments Summary

Control Plane Standards

Recommendations RFCs Interoperability results, IA: E-NNI, UNI Carrier requirements

ITU-T

IETF

ASON architecture Control plane management Use cases

OIF

GMPLS protocols Ethernet service definitions Technical Specifications

TMF

MEF

Protocols and Architectures

Control Plane capabilities are implemented in protocols, whose elements can be combined to support different architectures/implementations Different SDOs contribute various protocol elements and architectural components
IA Rec. RFC

RFC

RFC

RFC

Control Plane Solutions

RFC

RFC RFC RFC IA IA Rec.

IETF

OIF

ITU-T

Control Plane Specifications - Example

ITU-T
Requirements & Architecture AutoDiscovery G.8080 G.7714 G.7714.1 RFC 4204 RFC 4207

IETF
RFC 3495

TMF
TMF 509

Signaling

G.7713

G.7713.2

RFC 3474 RFC 3946

RFC 3473 RFC 4208

ENNI 1.0 UNI 1.0 E-NNI OSPF 1.0

ENNI 2.0 UNI 2.0

Routing

G.7715

G.7715.1 G.7715.2

RFC 4202

OIF

DCN/SCN

G.7712

Management

G.7718

G.7718.1

GMPLS MIB RFCs

TMF
TMF 814

Outline

ASON/GMPLS control plane concepts Involved SDOs Architectural principles of control plane enabled transport networks Control plane enabled services Future transport network evolution Business impact of control planes Control plane deployments Summary

G.805 Foundation Elements Transport Resources

Introduction of automated control doesnt remove/change the attributes of transport resources Control Plane needs to be able to configure the same attributes Introduction of automated control doesnt modify the functional components that exist within the transport plane

Optical Control Plane Fundamental Architecture Principles (1)

Decouple services from service delivery mechanisms

Wide range of network infrastructure options Network operator specific optimizations Wide range of survivability options Network operator specific approaches

Decouple QoS from realization mechanisms

Introduce call construct, which reflects a service association that is distinct from infrastructure/realization mechanisms

Optical Control Plane Fundamental Architecture Principles (2)

Provide boundaries of policy and information sharing Range of network operator business models Varying trust relationships among users and providers, among users, among providers Targeted solutions, scalability considerations (scope of information dissemination), etc.

Establish modular architecture with interfaces at policy decision points

Optical Control Plane Fundamental Architecture Principles (3)

Provide for various distributions of control functionality among physical platforms Different distributions of routing and signaling control Fully centralized to fully distributed system designs Decouple topology of the controlled network from that of the network supporting control plane communications (SCN) The transmission medium may be different for control plane messages and transport plane data

Identifiers to distinguish transport resources from, and among, signaling and routing control entities, and SCN addresses

ITU-T ASON Architecture Calls and Connections

Objective: Support ability to offer enhanced/new types of transport services facilitated by:

Automatic provisioning of transport network connections Span one or more managerial/administrative domains

Involves both a Service and Connection perspective Call : Support the provisioning of end-to-end services while preserving the independent nature of the various businesses involved Connection : Automatically provision network connections (in support of a service) that span one or more managerial/administrative domains

ITU-T ASON Architecture Domains

ASON domains represent generalization of existing traditional concepts

Transport definitions of administrative/management domains Internet administrative regions Administrative and/or managerial responsibilities Trust relationships, addressing schemes Distributions of control functionality Infrastructure capabilities, survivability techniques, etc.

Domains may express differing:

Domains are established by network operator policies

ITU-T ASON Architecture Interfaces (1)

Service demarcation points are where call control is provided Inter-domain interfaces are service demarcation points
UNI Service Demarcation Point

Provider management system

User
Router

IP/MPLS
Router

Management Plane

Ethernet/ ATM / FR SONET / SDH / OTN

Router

Call Control

*Call Control Optical Control Plane

Provider network

Transport Plane

Design modularized around open interfaces at domain boundaries

UNI, E-NNI, I-NNI

ITU-T ASON Architecture Interfaces (2)

UNI
NE

E-NNI

UNI
NE

Provider A

NE

Provider B

NE

UNI separates the concerns of the user and provider:

3.6 Modularity is good. If you can keep things separate, do so. - RFC 1548 Objects referenced are User objects, and are named in User terms

I-NNI

Domain 1

E-NNI

UNI enables:

E-NNI

Domain 2

Client driven end-to-end service activation Multi-vendor inter-working Multi-client IP, Ethernet, TDM, etc. Multi-service SONET/SDH, Ethernet, etc. Service monitoring interface for SLA management

ITU-T ASON Architecture Interfaces (3)

UNI-C UNI-N

UNI

UNI-N UNI-C

UNI

E-NNI
NE

Provider A

NE

NE

Provider B

NE

E-NNI enables:

End-to-end service activation Multi-vendor inter-working Multi-carrier inter-working Independence of survivability schemes for each domain

I-NNI

Domain 1

E-NNI

E-NNI

Domain 2

I-NNI supports:

Intra-domain connection establishment Explicit connection operations on individual switches

ITU-T ASON Architecture Call Control & Interfaces

Call state is maintained at network access points, and at key network transit points where it is necessary or desirable to apply policy Calls that span multiple domains are comprised of call segments, with call control provided at service demarcation points (UNI/E-NNI) One or more connections are established in support of individual call segments, with scope of connection control typically limited to a single call segment
UNI
NE

Domain A
NE

E-NNI
NE

Domain B
NE

UNI

CALL

UNI Call Segment

Domain A Call Segment

E-NNI Call Segment

Domain B Call Segment

UNI Call Segment

CONNECTIONS

Outline

ASON/GMPLS control plane concepts Involved SDOs Architectural principles of control plane enabled transport networks Control plane enabled services Future transport network evolution Business impact of control planes Control plane deployments Summary

Components of Control Plane enabled Network Domains

Management plane
CP MANAGEMENT

DCN

CONTROL PLANE

Data plane

Optical Control Plane Service Permanent Connection

All intra-/inter-domain calls and connections are provisioned by Management Plane actions
Management plane Management plane Management plane Management plane

DCN

DCN

DCN

DCN

Data plane

Data plane

Data plane

Data plane

C1

Provisioned

TN1

Provisioned

TN2

Provisioned

C2

Permanent connection
C: Client network domain TN:Transport Network provider domain

Optical Control Plane Service Soft Permanent Connection

Management plane of a transport network provider domain is initiating a call/connection

SPC initiating domain
Management plane functions
Management plane functions
CP management

Management plane functions

CP management

Management plane functions

CP management

DCN

DCN

DCN

DCN

Control plane functions

Control plane functions

Control plane functions

Data plane functions

Data plane functions

Data plane functions

Data plane functions

C1 Permanent connection

TN1

E-NNI
Switched connection

TN2 Permanent connection

C2

Soft Permanent Connection (SPC)

C: Client network domain TN:Transport network provider domain

Optical Control Plane Service Switched Connection

Management plane of a client domain is initiating a call/connection

SC initiating domain
Management plane functions
CP management

Management plane functions

CP management

Management plane functions

CP management

Management plane functions

CP management

DCN

DCN Control plane functions

DCN

DCN

Control plane functions

Control plane functions

Control plane functions

Data plane functions

Data plane functions

Data plane functions

Data plane functions

C1

TN1

TN2

C2

UNI

E-NNI

UNI

Switched connection
C: Client network domain TN:Transport Network provider domain

Outline

ASON/GMPLS control plane concepts Involved SDOs Architectural principles of control plane enabled transport networks Control plane enabled services Future transport network evolution Business impact of control planes Control plane deployments Summary

Evolving Transport Network Standardization Overview

Characteristics OTN ODUk X X X X Done ITU-T G.709 Done RFC 4328 OIF UNI and E-NNI 2009 IEEE 802.1 In progress IETF, ITU-T, OIF 2009 ITU-T/IETF In progress IETF, ITU-T, OIF Various ITU-T Under study IETF, ITU-T, OIF Layer 2 PBB-TE Layer 2 MPLS-TP OTN All optical switching

TDM switching Packet switching All optical switching Data plane standards and specifications Control plane standards and specifications

Evolving TN Standardization Activities Multi-Layer Aspects #1

UNI
Client 1

Client layer call 1st server layer call

UNI
Client 2

Client Domain #1

Operator Domain

2nd server layer call

Client Domain #2

Evolving TN Standardization Activities Multi-Layer Aspects #2

Two layer examples: SONET/SDH over OTN Three layer examples Ethernet over VCAT over SONET/SDH Ethernet over VCAT over OTN Ethernet over VLAN over PBB Ethernet over VLAN over PBB-TE Ethernet over VLAN over T-MPLS (MPLS-TP tunnel)

Evolving TN Standardization Activities Multi-Layer Aspects Ethernet/VCAT/SDH

ECOC 2007 Berlin

Outline

ASON/GMPLS control plane concepts Involved SDOs Architectural principles of control plane enabled transport networks Control plane enabled services Future transport network evolution Business impact of control planes Control plane deployments Summary

The Challenge - Complex Network Realities

Carriers are living in heterogeneous network environments Multi-domain Multi-layer Heterogeneous environment resulting from mergers and acquisitions, company splits, multi-vendor NEs The need for interoperable solutions and seamless interworking even on global scale is increasing continuously!
Client Network A Optical Network B Optical Network A Client Network B

Client Network E

Optical Network C Client Network D Client Network C

The Promise - Save Money & Make Money Lower Costs & Increased Revenues

Bandwidth Services

Enhanced Network Efficiency

Operation Improvements

Service Enhancements

Control Plane Enables Service Enhancements

Improved customer satisfaction Faster provisioning New revenue opportunities New services:

On-demand provisioning Broadband Bandwidth on Demand services Optical VPN

Bandwidth Services

Enhanced Network Efficiency

SLA-based performance (QoS) Client self-service options Provides service differentiators

Service Enhancements

Operation Improvements

Control Plane Enables Operation Improvements

Faster service provisioning Simplified network design Reduced fallout rates Integrated testing capabilities Higher quality databases (NE to OSSs) Increased automation in operation support
Service Enhancements Bandwidth Services Enhanced Network Efficiency

Operation Improvements

Control Plane Enables Enhanced Network Efficiency

Auto-discovery (autorecognition) Mesh network topologies Improved network reliability and availability Flexible, robust protection and restoration Aligns with convergence of multi-layer network evolution path
Bandwidth Services Enhanced Network Efficiency

Service Enhancements

Operation Improvements

Outline

ASON/GMPLS control plane concepts Involved SDOs Architectural principles of control plane enabled transport networks Control plane enabled services Future transport network evolution Business impact of control planes Control plane deployments Summary

Control Plane Deployments Overview

Control plane is deployed across the globe in major carriers networks, enabling: Cost savings and faster provisioning through automation New services such as On-Demand-Bandwidth Mesh Restoration functionality for critical added reliability

Control Plane Deployments Examples

Carrier Networks AT&T: Optical Mesh Services Verizon: JiT Just in Time Services Trans-Atlantic/Pacific mesh optical networks, Research Networks Internet 2, USA SINET 3, Japan, National and international field trials European projects: NOBEL, MUPBED, PHOSPHORUS, Kei-han-na Open Lab, Japan DRAGON, USA VIOLA, German project,

Summary
ASON/GMPLS control plane is Following basic principles of transport networks Becoming mature step by step Has a significant business impact

Supporting on-demand services over intelligent optical transport networks Enables cost-effective end-to-end transport of high-speed data

The most preferable, standard based solution for seamless interworking in complex network environments, comprising
Multi-vendor network elements Multi-domain Multi-layer while maintaining the individual functionalities within network layers and domains

Thank You for your Kind Attention!

Acknowledgement: The author thanks all colleagues from the OIF for their work, which has been the basis for this presentation The responsibility for the content of this presentation is with the author For more information please visit: ITU-T: www.itu.int IETF: www.ietf.org OIF: www.oiforum.com Hans-Martin Foisel [email protected]