Management of ASON- -capable capable Management of ASON Network - PowerPoint PPT Presentation

I nternational Telecom m unication Union ITU-T Management of ASON- -capable capable Management of ASON Network and its Control Plane Network and its Control Plane H. Kam LAM Lucent Technologies I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6

Outline ITU-T Benefit of AS ON-capable Network o Management Requirements o How these requirements are being o addressed Challenge and Issues o I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2

ASON Capabilities ITU-T o Automatic route design • Path computation done by the network o Automatic connection management • S etup / Modification / Release • Restoration / Protection o Automated resource management • Transport topology & capacity discovery • Connectivity verification I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 3

ASON Benefits ITU-T o S implified connectivity provisioning OPEX • Path computation done by the network • Reduce complex planning and designs • Increase accuracy of the process o Efficient network resource utilization CAPEX • Reduce static dedicated protection through dynamic shared restoration o Rapid service turn-up Revenue • Timely support of bandwidth-on-demand services • Provide new revenue opportunities I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 4

ASON – An enabler for NGN realization ITU-T 3rd Party Application Providers ANI Service stratum Application Functions Services Management Functions Control Service User Service User Profiles Profiles Service Control Functions Transport User Network Resource and Network Resource and Resource and End-User Function Attachment Admission Profiles Attachment Admission Admission Other Networks Control Functions Control Functions Control Functions Control Functions Control Functions Transport Control Functions Transport Control Functions Media Handling Functions Gateway Edge Gateway Core Transport Access Network F Functions Functions Functions Functions UNI Transport Functions NNI Transport stratum Control Management Media I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 5

Context of ASON Managem ent ITU-T Management plane s Directs t Directs c e r i D Reports Supports Supports Data communication network Reports R e p o r t s Supports Directs Reports Control plane Transport plane I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 6

View s of Transport resources ITU-T SNP Relationship between the architectural entities in CP Transport plane, Management plane, and Control plane Adaptation CTP TTP Subnetwork Trail Termination TCP SNP SNP Link Connection SNC SNC Link Connection Transport entities Adaptation function Trail Termination function CP: Connection point TCP: Termination connection point Trail Control plane view Management plane view SNP: Subnetwork Point TTP: Trail Termination Point SNPP: SNP Pool CTP: Connection Termination Point SNPP Link I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 7

How ASON m anagem ent is being addressed ITU-T SMS NMS G.7718 TMF MTNM EMS G.7718.1 Control Plane Network Element Transport Plane I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 8

G.7 7 1 8 ASON Managem ent requirem ents ITU-T o Configuration management • Control plane resources —Identifiers, addresses, prot ocol parameters (signaling & routing) … • Routing areas — RA hierarchies, (dis)aggregation, assignment of CP resources • Transport resources (in control plane view) — (de)allocation, names and identifiers, discovery, topology, resource and capacity inventory • Call and connection — setup(S PC)/ modification/ release • Policy o Fault management • Control plane components, resource/ connection/ call (service), o Performance management • Control plane components o Accounting management • Usage and call details record o Security management I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 9

G.7 7 1 8 .1 – Routing service classes ITU-T I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 0

G.7 7 1 8 .1 ( cont.) – Signaling service classes ITU-T I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 1

G.7 7 1 8 .1 ( cont.) – Discovery service classes ITU-T I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 2

TMF 5 1 3 / 6 0 8 / 8 1 4 – CP Managem ent ITU-T o Version 3.5 – CP & Ethernet management • TMF 513 – Requirements & Use cases • TMF 608 – Protocol-neutral model (UML) • TMF 814 – CORBA solution o Adopt the v3.0 approach • Multi-layer —ML-RA ( MLSN ), ML-S NPP, ML-S NPP Link, … • Re-use of S NC —Connection o Call – for AS ON and Ethernet management I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 3

G.8 0 5 Layered Model and MTNM Sim plification ITU-T Simplified G.805 Fragment G.805 Fragment Simplified TCP CP SNC Client to server adaptation AP Trail Termination I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 4

MTNM m ulti-layered Model ITU-T Basic ITU-T G.805 structures MTNM Model G.805 Adaptation PTP G.805 Trail Termination CTP G.805 Connection Point SNC G.805 Termination Connection Point TerminationMode G.805 relationship Naming/containment G.805 relationship G.805 relationship (may be SNC) G.805 SNC (may be relationship) I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 5

MTNM Control plane m anagem ent: Scenario # 0 ITU-T EMS Domain = MLSN, Routing Area is not seen at NMS-EMS i/f, basic reference scenario #0 NMS MTNM Version 3.0 EMS EMS Domain Connection ASON Signalling controller MLSN ME ME ME ME ME ME ME ME ME Edge PTP Edge PTP Routing Area Connection, modeled as a “network routed” SNC I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 6

MTNM Control plane m anagem ent: Scenario # 1 ITU-T EMS Domain = MLSN of Routing Area type, centralized CC, reference scenario #1 NMS EMS EMS Domain Connection ASON Signalling controller MLSN / Routing Area ME ME ME ME ME ME ME ME ME Edge PTP , Edge PTP , Routing Area internal PTP Dumb interface Dumb interface Connection / SNC I-NNI interface I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 7

MTNM Control plane m anagem ent: Scenario # 2 ITU-T EMS Domain = MLSN of Routing Area type, distributed CC, reference scenario #2 NMS EMS Domain EMS MLSN / Routing Area CC CC CC CC ME CC ME CC ME ME ME ME CC CC ME ME Edge PTP , I-NNI interface Routing Area Dumb interface Connection / SNC I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 8

MTNM Control plane m anagem ent: Scenario # 3 ITU-T Three levels routing hierarchy, EMS Domain = top level MLSN of Routing Area type, centralized CC per Routing Area, reference scenario #3 NMS EMS Domain Routing Area 1 EMS Top level MLSN Connection ASON Signalling controller Routing Area 1.1 (level 1) Routing Area 1.2 (level 1) CC CC ME ME ME ME ME ME ME ME SNC 2 Edge PTP , E-NNI interface I-NNI interface SNC 1 Dumb interface End to End SNC I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 9

MTNM Control plane m anagem ent: Scenario # 4 ITU-T Three levels routing hierarchy, one EMS per Routing Area of intermediate level, reference scenario #4 NMS Routing Area 1 EMS1 Top level MLSN EMS2 ASON Signalling Connection Routing Area 1.1 controller (level 1) Routing Area 1.2 (level 1) EMS Domain CC CC ME ME ME ME ME ME ME ME E-NNI interface Edge PTP , End to End SNC Dumb interface SNC 1 SNC 2 I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 0

MTNM Control plane m anagem ent: Scenario # 5 ITU-T Three levels hierarchy, all MLRAs are wider than EMS Domain, distributed CC, reference scenario #5 NMS Routing Area 1 EMS Domain 1 EMS EMS Domain n EMS Top level MLSN EMS EMS EMS EMS EMS Domain 2 EMS EMS CC CC CC CC ME CC ME CC ME ME ME ME CC CC ME ME Edge PTP , Dumb interface Routing Area 1.2 SNC 1 E-NNI (level 1) Routing Area 1.1 End to End SNC (level 1) SNC 2 I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 1

MTNM Control plane m anagem ent: Scenario # 6 ITU-T Routing Area Island, reference scenario #6 Routing Area 1 “legacy” MLSN EMS Domain Top level MLSN ME ME ME ME ME ME ME ME MLSN SNC Dumb Interface I-NNI Routing Area SNPP Link (level 0), SNPP Link (level 1) Connection/SNC single ended I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 2