Maarten Vissers. Huawei

HUAWEI TECHNOLOGIES CO., LTD.

SDN Outside Data Center Developing its components

Maarten Vissers

Europe Research Center

Huawei Fixed Network

HUAWEI TECHNOLOGIES CO., LTD. Page 2

Carrier-grade SDN

Logically centralized SDN Controller

User SDN Controller

User SDN Controller

User SDN Controller

User SDN Controller

User Application

User Application


Carrier-grade SDN Features

Pre-SDN • Vendor controls applications that

provider can run in its network managers

• Provider controls static user connectivity

• Per domain, vendor, technology connectivity control

• Offline network planning

• Physical network management and control boxes

SDN • Provider controls applications running in its

SDN controllers – Retrieved from SDN APP Store

• User controls its dynamic connectivity via Bandwidth on Demand (BoD) and Virtual Transport Network (VTN) services

• End-to-end network topology & connectivity control; multi-vendor, multi-technology

• Online network engineering based on network sensor and planning information

• Management & Control Function Virtualization – In phase 2 the EMS, NMS, OSS, BSS, PCE and

SDN Controller functionality is virtualized into applications running in Virtual Machines (VM)


• Type 2 service defines dynamic connection service that is provided to customers based on their request, e.g. BoD. In this type of service, customers only have knowledge of the end points of the operator’s network, which looks like "one virtual NE " to the customer. Therefore, customers have very limited access to the operator’s network.

Type 2: Dynamic connection service with limited customer control

vNE

Client site B

Client site D

Client site C

Client site A

vPort 1

vPort 2

vPort 3

vPort 4

Figure 8-2 Type 2 service

Virtual Transport Network Services Service definition under development in OIF, draft in oif2014.269 Type 1: Fixed connection service (without customer control)


• Type 3 service specifies a fixed virtual network topology provided by operator over which customers are allowed to have full control of virtual connection setup/modification/deletion, e.g. include explicit routing on customer’s demand.

• Virtual network is pre-configured/negotiated between customer and owner of the physical network. Operator stays in full control and responsibility over physical NE and how to physically realize the virtual network.

Type 3: Fixed virtual network topology with customer connection control

vNE1

vNE2

vNE4

vNE3

Client site B

Client site D

Client site C

Client site A


• Type 4 service specifies dynamic creation/modification/deletion of virtual networks based on customer’s request.

• Virtual network is NO longer pre-configured between customer and owner of the physical network. Operator stays in full control and responsibility over physical NE and how to physically realize the virtual network.

vNE5

Client site B

Client site D

Client site C

Client site A

vNE1

vNE2

vNE4

vNE3


Type 4: Dynamic virtual network with customer connection control


Appl. User

NBI

BoD Service

DC SDN Controller (flow control)

NBI SBI

User User

NBI

SDN Orchestrator Ctlr

DC NEs

VTN Service

TN NEs

OSS

Qx

NBI NBI/SBI

User User

NBI

IP NEs

IP SDN Controller

(flow control)

SDN Orchestrator Ctlr

VTN Service

SDN Controller SDN Controller Client SDN Controller (connection control)

NBI NBI/SBI

NBI

TN NEs

Client: other carrier or

enterprise or service network

VTN Service

Transport SDN Controller (multi-layer connection control)

NBI/SBI

high performance, low latency control channels

‘low’ performance

control channels

Client SDN Controller (connection control)

NBI

NBI VTN Service

With or without GMPLS NBI: North Bound Interface NE: Network Element SBI: South Bound Interface OSS: Operations Support System (e.g. EMS, NMS) Qx: Network element management interface

SDN Control Architecture


network edge

metro, core, backbone network domains

SDN Controller Hierarchy Application Inter- & Intra-Controller Interfaces

NE NE

SDN Domain Controller

SBI (chip control

via e.g. OpenFlow)

NBI: Services N/W API NBI: Transport API

SDN User Controller

Thin NE

SDN NE Controller

(G.7710 EMF)

Thin NE

SDN NE Controller

(G.7710 EMF)

Thin NE

SDN NE Controller

(G.7710 EMF)

SDN Controller

Master Resource Data Base

Virtualizer

VN RDB

NCE PCE

PCE Coor-dina-tor

Virtualizer

VN RDB

PC

Restor. Restor.

API API

API API

API API

AP

I

API API

API

API API

API

API

API

FCE API

API

Decomposition of SDN Controller into some basic Applications and Interfaces

TC

API

NCC

CC

Intent Interface (II)

SDCS controller

EP

G

CE CE CE

SE SE SE

EP

G

CE CE CE

SE SE SE

FG

CE CE CE

FG

CE CE CE

II

II

Other clients

Other clients

SDN Network Controller



CE: Compute Element

NE: Network Element SE: Storage Element SDN: Software Defined Network SDCS: Software Defined Compute & Storage


Transport API specifications under development in ONF OT WG

• Topology APIs – Retrieve subnetworks

• Retrieve_Subnetwork_IDs • Retrieve_Subnetwork

– Retrieve links • Retrieve_Link_IDs • Retrieve_Aggregated_Link_IDs • Retrieve_Associated_Link_IDs • Retrieve_Link_parameters

– Retrieve logical termination points • Retrieve_LTP_IDs • Retrieve_Associated_LTP_IDs • Retrieve_LTP

• Service-request and Intent APIs – create_p2p_connectivity_service – modify_p2p_connectivity_service – delete_p2p_connectivity_service – retrieve_p2p_connectivity_services – retrieve_p2p_connectivity_service

• Connection control APIs – Create_p2p_connectivity_connection – Create_SNC – Delete_p2p_connectivity_connection – Delete_SNC – Retrieve_p2p_connectivity_connection – Maintenance_p2p_connectivity_connection – Notify_p2p_connectivity_connection – Modify_SNC

• Path computation APIs – Request_p2p_connectivity_path_computati

on – Request_p2p_connectivity_path_modificati

on – Request_TED_update – Maintenance_resync_TED

• Virtual network service APIs – create_virtual_network_service – modify_virtual_network_service – delete_virtual_network_service

TAPI draft in onf2015.087


Core model fragment • module-1 • module-2 • ….

Application 1 (e.g. storage) model fragment (e.g. from NBI project)

Forwarding technology (e.g. OTN) model fragment (e.g. from OT project)

Guidelines

Interface specif ic

Common process

Common Information Model

Interface specif ic

xxx model fragment (from yyy project)

Prune/refactor

View of the

common IM for a

particular purpose

Papyrus tool and GitHub Model structure UML Interface

specif ic Interface specif ic

Data schema for interface 1

Map

Data schema for interface 2

Map

Interface instance 1

Map

Interface instance 2

Map

ONF’s Common Information Model (CIM) framework Foundation for all APIs

e.g., Transport APIs, Services N/W APIs

2015/3/27 10 HUAWEI TECHNOLOGIES CO., LTD. Page 10

Standardized component definitions for SDN outside the data center will become available in 2015 and can be used as basis for SDN controller, SDN application and SDN service developments

Thank you www.huawei.com

Copyright©2013 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future product portfolio, new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in the predictive statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time without notice.


ONF’s Common IM Fragments and MODULES UML to DS Mapping

Guidelines

UML |

XML

UML |

JSON

Core Fragment and Modules

Foundation Forwarding

… Topology

WG-specific Fragments

Gui

delin

es

xx

xx

guid

e

Interface-specific Data Schemas

xx

xx

Interface-specific Encodings

mapping

mapping

mapping

guid e

pruning re-factoring



OTWG a

Purpose-specific IMs

NBIWG x

OTWG b

UML |

YANG

guid

e

guid

e

guid

e

ONF-Wide UML Information Model

UM

L M

odel

s

xxWG z

Interface Development Process Description

guid

e

guid

e

guid

e

guid

e

guid

e

guid

e

guid

e

xx

UML |

OF

Techn specific

…

App specific


Physical Infrastructure

Control Layer

Orchestrator Super Controller

Controls End-to-End Network

Virtual Control Virtual Control

15

DC Fabric DC Fabric Transport Network A Transport Network B

5 1

7

3 2

6 8 4 13 14

12

Transport SDN Controller A

DC SDN Controller DC SDN Controller

Infrastructure Layer

Virtual Control Virtual Control

3

6 7

1 DC

Transport SDN Controller B

16 DC 13 11

10

16 11 10

9

Client’s Virtual View & Control

of End-to-End Network

Virtual DC & Transport Network

Date post:	19-Jul-2015
Category:	Business
Upload:	-
View:	90 times
Download:	1 times

Maarten Vissers. Huawei

Business