International Telecommunication Union
ITU-T
Management of ASON-capable
Network and its Control Plane
H. Kam LAM
Lucent Technologies
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
Outline
ITU-T
o
o
o
o
Benefit of ASON-capable Network
Management Requirements
How these requirements are being
addressed
Challenge and Issues
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
2
ASON Capabilities
ITU-T
o Automatic route design
• Path computation done by the network
o Automatic connection management
• Setup / Modification / Release
• Restoration / Protection
o Automated resource management
• Transport topology & capacity discovery
• Connectivity verification
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
3
ASON Benefits
ITU-T
o Simplified 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
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
4
ASON – An enabler for NGN realization
3rd Party Application Providers
Application Functions
Services
Control
Service
ServiceUser
Profiles
Profiles
Service Control Functions
Transport User
Profiles
End-User Function
Management Functions
Service stratum
ANI
Network
Attachment
Resource and
Admission
Control Functions
Control Functions
Other Networks
ITU-T
Transport Control Functions
Media Handling
Functions
Access Network
Functions
UNI
Edge
Functions
Gateway
Gateway
F
Functions
Core Transport
Functions
Transport Functions
NNI
Transport stratum
Management
Control
Media
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
5
Context of ASON Management
ITU-T
Di
re
Re
po
rts
Data communication Supports
network
rts
po
Re
Control plane
cts
re
Di
Reports
Supports
Directs
cts
Management plane
Supports
Directs
Reports
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
Transport plane
6
Views of Transport resources
ITU-T
SNP
CP
Relationship between the architectural entities in
Transport plane, Management plane, and Control plane
Adaptation
CTP
TTP
Subnetwork
Trail Termination
TCP
SNP
SNC
SNC
Link Connection
Transport entities
Adaptation function
Trail Termination function
CP: Connection point
TCP: Termination connection point
Management plane view
TTP: Trail Termination Point
CTP: Connection Termination Point
SNP Link Connection
Control plane view
SNP: Subnetwork Point
SNPP: SNP Pool
SNPP Link
Trail
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
7
How ASON management is being addressed
ITU-T
SMS
NMS
G.7718
TMF MTNM
EMS
G.7718.1
Control Plane
Network Element
Transport Plane
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
8
G.7718 ASON Management requirements
ITU-T o Configuration management
• Control plane resources
—Identifiers, addresses, protocol 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(SPC)/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
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
9
G.7718.1 – Routing service classes
ITU-T
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
10
G.7718.1 (cont.) – Signaling service classes
ITU-T
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
11
G.7718.1 (cont.) – Discovery service classes
ITU-T
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
12
TMF 513/608/814 – CP Management
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-SNPP, ML-SNPP Link, …
• Re-use of SNC
— Connection
o Call – for ASON and Ethernet management
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
13
G.805 Layered Model and MTNM Simplification
ITU-T
Simplified
G.805 Fragment
G.805 Fragment
Simplified
TCP
CP
SNC
Client to server
adaptation
AP
Trail Termination
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
14
MTNM multi-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)
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
15
MTNM Control plane management: 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
controller
ASON Signalling
MLSN
ME
ME
ME
ME
ME
ME
ME
ME
ME
Edge PTP
Edge PTP
Routing Area Connection, modeled as
a “network routed” SNC
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
16
MTNM Control plane management: Scenario #1
ITU-T
EMS Domain = MLSN of Routing Area type, centralized CC, reference scenario #1
NMS
EMS
EMS Domain
Connection
controller
MLSN /
Routing Area
ME
ME
ME
ME
ME
ME
ME
ME
Edge PTP,
Dumb interface
ASON Signalling
internal PTP
I-NNI interface
ME
Routing Area
Connection / SNC
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
Edge PTP,
Dumb interface
17
MTNM Control plane management: Scenario #2
ITU-T
EMS Domain = MLSN of Routing Area type, distributed CC, reference scenario #2
NMS
EMS Domain
EMS
MLSN /
Routing Area
ME
CC
CC
CC
CC
ME
CC
ME
ME
ME
CC
ME
Edge PTP,
Dumb interface
ME
CC
CC
ME
Routing Area
Connection / SNC
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
I-NNI interface
18
MTNM Control plane management: 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
Top level MLSN
EMS
Connection
controller
ASON Signalling
Routing Area 1.1
(level 1)
Routing Area 1.2
(level 1)
CC
CC
ME
ME
ME
ME
ME
ME
Edge PTP,
Dumb interface
ME
ME
SNC 2
SNC 1
End to End SNC
E-NNI interface
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
I-NNI interface
19
MTNM Control plane management: Scenario #4
ITU-T
Three levels routing hierarchy, one EMS per Routing Area of intermediate level, reference scenario #4
NMS
Routing Area 1
Top level MLSN
EMS1
Connection
controller
Routing Area 1.1
(level 1)
ASON Signalling
EMS2
Routing Area 1.2
(level 1)
EMS Domain
CC
CC
ME
ME
ME
ME
ME
ME
Edge PTP,
Dumb interface
ME
End to End SNC
ME
E-NNI interface
SNC 1
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
SNC 2
20
MTNM Control plane management: Scenario #5
ITU-T
Three levels hierarchy, all MLRAs are wider than EMS Domain, distributed CC, reference scenario #5
NMS
EMS Domain 1
EMS
EMS
EMS
EMS
EMS
EMS
EMS
EMS
EMS Domain 2
CC
CC
CC
ME
Routing Area 1
Top level MLSN
CC
CC
ME
ME
EMS Domain n
CC
ME
ME
ME
CC
CC
ME
Edge PTP,
Dumb interface
SNC 1
Routing Area 1.1
(level 1)
ME
Routing Area 1.2
(level 1)
E-NNI
End to End SNC
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
SNC 2
21
MTNM Control plane management: Scenario #6
ITU-T
Routing Area Island, reference scenario #6
“legacy” MLSN
Routing Area 1
Top level MLSN
EMS Domain
ME
ME
ME
ME
ME
ME
ME
ME
MLSN SNC
Dumb Interface
SNPP Link (level 0),
single ended
Routing Area
Connection/SNC
I-NNI
SNPP Link (level 1)
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
22
Use cases
ITU-T
o MLRA Discovery and Inventory
•Retrieve MLRA(s) (UC_4)
—MLSN Mgr:: getMultiLayerSubnetwork () // given
the name, return the object details
—Ems Mgr:: getAllMLRAs () // get all MLSNs which
are RA, including routing nodes
—Ems Mgr:: getAllTopLevelSubnetworks () // both
MLSN & MLRA
•Retrieve MLRAs that are subordinate to a
specified MLRA (UC_28)
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
23
Use cases (cont.)
ITU-T
o MLSNPP Link Discovery and Inventory
• Retrieve MLSNPP Links (UC_5)
• Retrieve available MLSNPP Link capacity (UC_6)
o MLSNPP Discovery and Inventory
• Retrieve MLSNPPs (UC_27)
• Notify change in capacity available to the
Control Plane – resulting from commissioning /
decommissioning of resources (UC_1)
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
24
Use cases (cont.)
ITU-T
o 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 (SPC and SC)
(UC_8)
•Notify deleted Calls and Connections (SPC and
SC) (UC_9)
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
25
Use cases (cont.)
ITU-T
o 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/SNPP/TNA (UC_26)
• Set diversity and co-routing parameters of an
existing call (UC_33)
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
26
Use cases (cont.)
ITU-T
o Provisioning
• Assign UNI MLSNPP Link to a Signaling Controller (UC_10)
• Set UNI signaling protocol and parameters (UC_11)
• Modify signaling parameters (UC_11b)
• Enable the UNI signaling for a MLSNPP Link (UC_12)
• Disable the UNI signaling for a MLSNPP Link (UC_13)
• De-assign a UNI MLSNPP Link from a Signaling Controller
(UC_14)
• Assign TNA Names to components of an MLSNPP (UC_15)
• Assign TNA Names to components of an MLSNPP Link (UC_32)
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
27
Challenge
ITU-T
o Issues for further study
• Management plane (MP) and Control plane (CP) interworking and integration
• Transport resource allocation and migration
• Maintenance of transport resources that are CP-allocated
• Call & connection migration
• …
o colaboration among forums (SG15, TMF, OIF, IETF)
• SG15 & TMF: role and responsibility
• SG15 & OIF: ASON architecture and requirements
• SG15 & IETF: Protocols MIBs and info models
ITU-T Workshop “NGN and its Transport Networks“
Kobe, 20-21 April 2006
28