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

▶
management of ason capable capable management of ason
SMART_READER_LITE
LIVE PREVIEW

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

Jan 19, 2023 160 likes •450 views

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

slide-1
SLIDE 1

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6

I nternational Telecom m unication Union

ITU-T

Management of ASON Management of ASON-

  • capable

capable Network and its Control Plane Network and its Control Plane

  • H. Kam LAM

Lucent Technologies

slide-2
SLIDE 2

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2

ITU-T

Outline

  • Benefit of AS

ON-capable Network

  • Management Requirements
  • How these requirements are being

addressed

  • Challenge and Issues
slide-3
SLIDE 3

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 3

ITU-T

ASON Capabilities

  • Automatic route design
  • Path computation done by the network
  • Automatic connection management
  • S

etup / Modification / Release

  • Restoration / Protection
  • Automated resource management
  • Transport topology & capacity discovery
  • Connectivity verification
slide-4
SLIDE 4

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 4

ITU-T

ASON Benefits

  • S

implified connectivity provisioning

  • Path computation done by the network
  • Reduce complex planning and designs
  • Increase accuracy of the process
  • Efficient network resource utilization
  • Reduce static dedicated protection through

dynamic shared restoration

  • Rapid service turn-up
  • Timely support of bandwidth-on-demand

services

  • Provide new revenue opportunities

OPEX CAPEX Revenue

slide-5
SLIDE 5

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 5

ITU-T

ASON – An enabler for NGN realization

Transport stratum Service stratum

Control Media NNI UNI Other Networks End-User Function

Management Functions

Services Control

Management

Application Functions

Gateway F

Service Control Functions

Service User Profiles

Service User Profiles Transport User Profiles

Resource and Admission Control Functions

Edge Functions Gateway Functions Core Transport Functions Media Handling Functions

Transport Functions ANI

3rd Party Application Providers

Access Network Functions

Network Attachment Control Functions

Transport Control Functions

Resource and Admission Control Functions Network Attachment Control Functions

Transport Control Functions

Resource and Admission Control Functions

slide-6
SLIDE 6

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 6

ITU-T

Context of ASON Managem ent

Transport plane Management plane Control plane Data communication network

Directs Reports Directs R e p

  • r

t s D i r e c t s Reports Directs Reports Supports Supports Supports

slide-7
SLIDE 7

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 7

ITU-T

View s of Transport resources

Trail Link Connection SNP Link Connection Subnetwork SNC SNC Trail Termination TCP Adaptation SNP TTP SNP CP CTP

Management plane view TTP: Trail Termination Point CTP: Connection Termination Point Control plane view SNP: Subnetwork Point SNPP: SNP Pool SNPP Link

Relationship between the architectural entities in Transport plane, Management plane, and Control plane

Transport entities Adaptation function Trail Termination function CP: Connection point TCP: Termination connection point

slide-8
SLIDE 8

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 8

ITU-T

How ASON m anagem ent is being addressed

Network Element

EMS NMS Transport Plane Control Plane SMS

G.7718 G.7718.1 TMF MTNM

slide-9
SLIDE 9

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 9

ITU-T

G.7 7 1 8 ASON Managem ent requirem ents

  • 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
  • Fault management
  • Control plane components, resource/ connection/ call (service),
  • Performance management
  • Control plane components
  • Accounting management
  • Usage and call details record
  • Security management
slide-10
SLIDE 10

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 0

ITU-T

G.7 7 1 8 .1 – Routing service classes

slide-11
SLIDE 11

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 1

ITU-T

G.7 7 1 8 .1 ( cont.) – Signaling service classes

slide-12
SLIDE 12

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 2

ITU-T

G.7 7 1 8 .1 ( cont.) – Discovery service classes

slide-13
SLIDE 13

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 3

ITU-T

TMF 5 1 3 / 6 0 8 / 8 1 4 – CP Managem ent

  • Version 3.5 – CP & Ethernet management
  • TMF 513 – Requirements & Use cases
  • TMF 608 – Protocol-neutral model (UML)
  • TMF 814 – CORBA solution
  • Adopt the v3.0 approach
  • Multi-layer

—ML-RA (MLSN), ML-S NPP, ML-S NPP Link, …

  • Re-use of S

NC

—Connection

  • Call – for AS

ON and Ethernet management

slide-14
SLIDE 14

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 4

ITU-T

G.8 0 5 Layered Model and MTNM Sim plification

AP CP TCP Trail Termination Client to server adaptation SNC Simplified G.805 Fragment Simplified G.805 Fragment

slide-15
SLIDE 15

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 5

ITU-T

G.805 Adaptation G.805 Trail Termination G.805 Connection Point G.805 Termination Connection Point G.805 relationship G.805 relationship G.805 relationship (may be SNC) G.805 SNC (may be relationship) PTP CTP SNC TerminationMode Naming/containment

Basic ITU-T G.805 structures MTNM Model

MTNM m ulti-layered Model

slide-16
SLIDE 16

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 6

ITU-T

ME

MTNM Version 3.0

ASON Signalling

ME ME ME ME

MLSN

ME ME ME ME Connection controller

Edge PTP Edge PTP

EMS Domain

EMS Domain = MLSN, Routing Area is not seen at NMS-EMS i/f, basic reference scenario #0

EMS

NMS Routing Area Connection, modeled as a “network routed” SNC

MTNM Control plane m anagem ent: Scenario # 0

slide-17
SLIDE 17

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 7

ITU-T

ME

EMS Domain

ME ME ME ME ME ME ME ME

Edge PTP, Dumb interface

MLSN / Routing Area EMS

NMS

EMS Domain = MLSN of Routing Area type, centralized CC, reference scenario #1

Edge PTP, Dumb interface Routing Area Connection / SNC ASON Signalling

Connection controller

internal PTP I-NNI interface

MTNM Control plane m anagem ent: Scenario # 1

slide-18
SLIDE 18

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 8

ITU-T

ME ME ME ME ME ME ME ME

CC CC CC CC CC CC CC CC

EMS Domain

Edge PTP, Dumb interface

EMS Domain = MLSN of Routing Area type, distributed CC, reference scenario #2

Routing Area Connection / SNC

EMS

NMS

MLSN / Routing Area

I-NNI interface

MTNM Control plane m anagem ent: Scenario # 2

slide-19
SLIDE 19

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 1 9

ITU-T

ME ME ME ME ME ME ME ME

EMS Domain

End to End SNC

SNC 1 SNC 2

ASON Signalling Edge PTP, Dumb interface

Routing Area 1 Top level MLSN

E-NNI interface

EMS

NMS

Connection controller

Three levels routing hierarchy, EMS Domain = top level MLSN of Routing Area type, centralized CC per Routing Area, reference scenario #3

Routing Area 1.1 (level 1)

CC CC

Routing Area 1.2 (level 1)

I-NNI interface

MTNM Control plane m anagem ent: Scenario # 3

slide-20
SLIDE 20

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 0

ITU-T

ME ME ME ME ME ME ME ME

EMS Domain

ASON Signalling

Connection controller

Edge PTP, Dumb interface

SNC 1 SNC 2

E-NNI interface

EMS1

NMS

EMS2

Three levels routing hierarchy, one EMS per Routing Area of intermediate level, reference scenario #4

End to End SNC

Routing Area 1 Top level MLSN Routing Area 1.1 (level 1) Routing Area 1.2 (level 1)

CC CC

MTNM Control plane m anagem ent: Scenario # 4

slide-21
SLIDE 21

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 1

ITU-T

ME ME ME ME ME ME ME ME

CC CC CC CC CC CC CC CC

EMS Domain 1

Edge PTP, Dumb interface

Three levels hierarchy, all MLRAs are wider than EMS Domain, distributed CC, reference scenario #5

End to End SNC

EMS

NMS

EMS EMS EMS EMS EMS EMS EMS EMS Domain 2 EMS Domain n

E-NNI

Routing Area 1.1 (level 1) Routing Area 1.2 (level 1) Routing Area 1 Top level MLSN

SNC 1 SNC 2

MTNM Control plane m anagem ent: Scenario # 5

slide-22
SLIDE 22

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 2

ITU-T

ME ME ME ME ME ME ME ME

MLSN SNC Routing Area Connection/SNC

Routing Area Island, reference scenario #6

I-NNI SNPP Link (level 1) Dumb Interface SNPP Link (level 0), single ended EMS Domain “legacy” MLSN Routing Area 1 Top level MLSN

MTNM Control plane m anagem ent: Scenario # 6

slide-23
SLIDE 23

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 3

ITU-T

Use cases

  • MLRA Discovery and Inventory
  • Retrieve MLRA(s) (UC_4)

— MLS N Mgr:: getMultiLayerS ubnetwork () / / given the name, return the obj ect details — Ems Mgr:: getAllMLRAs () / / get all MLS Ns which are RA, including routing nodes — Ems Mgr:: getAllTopLevelS ubnetworks () / / both MLS N & MLRA

  • Retrieve MLRAs that are subordinate to a

specified MLRA (UC_28)

slide-24
SLIDE 24

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 4

ITU-T

Use cases ( cont.)

  • MLS

NPP Link Discovery and Inventory

  • Retrieve MLS

NPP Links (UC_5)

  • Retrieve available MLS

NPP Link capacity (UC_6)

  • MLS

NPP Discovery and Inventory

  • Retrieve MLS

NPPs (UC_27)

  • Notify change in capacity available to the

Control Plane – resulting from commissioning / decommissioning of resources (UC_1)

slide-25
SLIDE 25

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 5

ITU-T

Use cases ( cont.)

  • Call Discovery and Inventory
  • Retrieve Calls and top level Connections

supporting each Call (UC_7)

  • Retrieve details of a Call (UC_35)
  • Notify new Calls and Connections (S

PC and S C) (UC_8)

  • Notify deleted Calls and Connections (S

PC and S C) (UC_9)

slide-26
SLIDE 26

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 6

ITU-T

Use cases ( cont.)

  • Call management
  • Establish a Call (UC_20)
  • Release a Call (UC_21)
  • Add connection(s) to an existing call (UC_22)
  • Remove connection(s) from with a call (UC_23)
  • Retrieve Calls and their top level Connections (UC_7)
  • Retrieve subordinate MLRA involved in the route of a

Connection (UC_24)

  • Retrieve route details of a specified Call within a

specified RA (UC_25)

  • Retrieve the ID/ Name of the Call supported by a

specified TP/ S NPP/ TNA (UC_26)

  • S

et diversity and co-routing parameters of an existing call (UC_33)

slide-27
SLIDE 27

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 7

ITU-T

Use cases ( cont.)

  • Provisioning
  • Assign UNI MLS

NPP Link to a S ignaling Controller (UC_10)

  • S

et UNI signaling protocol and parameters (UC_11)

  • Modify signaling parameters (UC_11b)
  • Enable the UNI signaling for a MLS

NPP Link (UC_12)

  • Disable the UNI signaling for a MLS

NPP Link (UC_13)

  • De-assign a UNI MLS

NPP Link from a S ignaling Controller (UC_14)

  • Assign TNA Names to components of an MLS

NPP (UC_15)

  • Assign TNA Names to components of an MLS

NPP Link (UC_32)

slide-28
SLIDE 28

I TU-T W orkshop “NGN and its Transport Netw orks“ Kobe, 2 0 -2 1 April 2 0 0 6 2 8

ITU-T

Challenge

  • Issues for further study
  • Management plane (MP) and Control plane (CP) inter-

working and integration

  • Transport resource allocation and migration
  • Maintenance of transport resources that are CP-allocated
  • Call & connection migration
  • …
  • colaboration among forums (S

G15, TMF, OIF, IETF)

  • S

G15 & TMF: role and responsibility

  • S

G15 & OIF: ASON architecture and requirements

  • S

G15 & IETF: Protocols MIBs and info models