Joint ITU-T/IEEE Workshop on Carrier-class Ethernet · Joint ITU-T/IEEE Workshop on Carrier-class...

Geneva, 31 May – 01 June 2007 1

Joint ITU-T/IEEE Workshop on Carrier-class Ethernet

Dr. Hing-Kam LamAlcatel-Lucent

Rapporteur, ITU-T Q14/SG15

Management of Carrier-class Ethernet


Outline

Scope of the presentationRelevant SDOsStatus and overview of the standards activities


Scope of the presentation

Current status of Carrier-class Ethernet management in the standards

Cover Equipment-level management and Network-level management (NMS/EMS interface) Include management requirements, use cases, information models (protocol-neutral and protocol-specific)Address Ethernet over transport (EoT) network, Metro Ethernet network, and Passive optical network (EPON, GPON)

Also discuss the management of ASON-capable EoT network and consideration of DCN


Relevant SDOs & Forums (1/2)Produce management specifications

ITU-T SG15, Q14 & Q2Equipment-level management requirements and protocol-neutral info model for EoT NEGPON ONT management & control

ITU-T SG4, Q10Network-level mgmt requirements & analysis for EoT, MEN, EPON

TM Forum, mTOP (MTNM, MTOSI)Network-level & NE-level management requirements & solutions for Ethernet bridge and VLAN switching

Metro Ethernet Forum, Management sub-committeeExtended Network level & NE-specific management requirements; Ethernet LMI; Service OAM; Mgmt of Network Interface Device

IEEE 802.1 WGOAM protocol and state machinesProtocol-neutral info model & MIB modules (mainly for use by SNMP) for Ethernet layer-2 bridged networksMaintenance & enhancement of the Bridge-related MIB modules (from the concluded IETF BRIDGE-MIB WG)

IETF Ethernet Interface & Hub MIB WGMIB modules (mainly for use by SNMP) for EFM, EPON, & Ethernet-like interfaces


Relevant SDOs & Forums (2/2)Provide foundation specifications

ITU-T SG15, Q9, Q11, Q12EoT architecture, services framework, UNI & NNI interfaces, Ethernet equipment function blocks

ITU-T SG13, Q5OAM functions & mechanism of Ethernet-based carrier networks

IEEE 802.1 WG & 802.3 WGLocal and metropolitan area networks architecture, Bridge, Media access control (MAC), CSMA/CD, …


Management Specifications & Status (1/2)

EoT Equipment Management (Q14/15)G.8051/Y.1345 (G.eot-mgmt) “Requirements” (targeted for 6/2007) G.8052/Y.1346 (G.eot-mgmt-info) “Protocol-neutral info model” (TBS)

TMF Multi-Technology Network Management (MTNM) Release 3.5 (in Member Evaluation)

TMF 513 “Business Agreements” (Requirements, Use Cases)TMF 608 “Information Agreements” (Prot-neutral object model)TMF 814 “Solution Set” (CORBA/IDL)TMF 814A “Implementation Statement & Guidelines”

EoT, MEN, EPON, & GPON Network ManagementQ.840.1 (2/2007; Q10/4) “Reqt and Analysis for NMS-EMS Mgmt I/F of Ethernet over Transport and Metro Ethernet Network (EoT/MEN)”; Harmonized with MEF 7Q.838.1 (10/2004; Q10/4) “Reqt and analysis for the mgmt I/F of EPON”G.984.4 (6/2004; Q2/15) “GPON ONT mgmt & control I/F specification”

MEF Management SpecificationsMEF 15 (11/2005) “Reqt for Mgmt of Metro Ethernet Phase 1 Network Elements”MEF 7.1 (targeted for 12/2007) “NMS-EMS extensions for Service OAM and E-NNI” Building on Q.840.1; Harmonized with TMF MTNM Rel. 3.5MEF 16 (1/2006) “Requirements for Ethernet Local Management Interface”


Management Specifications & Status (2/2)IEEE Ethernet management information & data models

802.1AB (2005) Station & MAC Connectivity Discovery: Info model & MIB modules (mainly for use by SNMP) for layer-2 bridged network topology management802.1ad (2005) Virtual Bridged LAN Amd.4: Info model & MIB modules (mainly for use by SNMP) for bridged provider network management802.1ag (WG ballot) Connectivity Fault Management: OAM protocol and MIB modules (SNMP) for bridge and LAN connectivity fault management802.1D (2004) Media Access Control (MAC) Bridge: Information model for layer-2 bridged network management802.1Q (2005) Virtually Bridged LAN: Information model for layer-2 bridged network and VLAN management

IETF EFM, EPON, & Ethernet-like interface mgmt data modelsManaged Objects of EPON (12/2006 in RFC-editor queue): MIB modules (mainly for use by SNMP) for managing EPON devices and interfacesEthernet in the First Mile Copper Interfaces MIB (3/2007 v7 in IETF LC)Definitions and Managed Objects for OAM Functions on Ethernet Like Interfaces(3/2007 v6 approved by IESG as Proposed Standard)RFC 3621 (12/2003) Power Ethernet MIB: Power source managementRFC 3635 (9/2003) Ethernet-like Interface MIBRFC 3637 (9/2003) Ethernet WAN MIB: WIS managementRFC 4836 (4/2007) MAU MIB: 802.3 MAU management (obsoletes 3636)


Management of EoT

Carrier CDomain

Carrier ADomain

Carrier BDomain

NE NE NE NE NE NE

EthernetClient

EthernetClient

...

Virtual Concatenation Group (21 STS-1 or 7 VC-4)

......

GbE GbE

Ethernet Transport (e.g., SONET/SDH, MPLS, ETH, ETY)

NE-level management:Ethernet equipment, core transport (e.g., SONET/SDH) equipment, Ethernet over transport adaptation using GFP/VCAT/LCASEthernet frame management at LAN and WAN ports

Network-level management:Ethernet services: Private Line, Virtual Private Line, Virtual LAN, Virtual Private LANVLAN ID, C-tag, S-tag, CoS, CoS profile, CoS performance, Bandwidth (TMF: Traffic Conditioning) profile

VCATLCAS

GFP-FVCATLCAS

GFP-F

Ethernet


Management of Ethernet over Transport (EoT) with Control plane

Carrier CDomain

OIF UNI OIF E-NNI OIF UNI

Carrier ADomain

Carrier BDomain

OIF E-NNINE NE NE NE NE NE

EthernetClient

EthernetClient

Ethernet Layer Call/Connection Flow

SONET/SDH Layer Call/Connection Flow

UNI-N UNI-N UNI-CUNI-C

EthernetSONET/SDH

In addition to those in the previous slidesControl plane management:

Control plane infrastructure: Signaling services, Routing services, Discovery services Call, Connection, Transport plane resources in control plane view

Transport / Control / Management planes inter-working:MP & CP inter-workingTransport resource allocation & migration between MP & CP and maintenance

Ethernet


EoT Specification Relationships in ITU-T

EoT Equipment FunctionG.8021

EoT Equipment MgmtG.8051 (G.eot-mgmt)

Common Equip. Mgmt. Function G.7710

Common Equip. FunctionG.806

EoT Equp. Mgmt ModelG.8052 (G.eot-mgmt-info)

TMN FunctionsM.3400

TMN ArchitectureM.3010

Generic Info ModelM.3100

DCN Architecture & ReqtsG.7712

Lower Layer Protocol Profiles Q.811

Upper Layer Protocol Profiles Q.812

Ethernet UNI & NNIG.8012

OAM mechanismsY.1731

Ethernet TerminologyG.8001

Ethernet ArchitectureG.8010

Ethernet ProtectionG.8031 / G.8032

Ethernet ServicesG.8011 / G.8011.1

EoT/MEN EMS/NMS I/FQ.840.1


NE-level managementManage the transport plane functions and control plane functions of the NE, including provisioning, monitoring, processing, and reporting of the input and output Management Information (MI)

Network Element Function (NEF)

Equipment Management Function

(EMF)ManagementApplication

Function (MAF)Date/TimeFunctions

Date/TimeInterface

MgmtPlane

Interface

Local Alarm I/F

Age

nt

MessageComm.Function(MCF)

Date/TimeCommunication

Local AlarmCommunication

fromexternal

Time source

Mgmt PlaneCommunication

to / fmEMS,NMS

to localalarm

Tran

spor

t Ato

mic

Fun

ctio

n

FaultMgmt

ConfigMgmt

AccountMgmt

Perform.Mgmt

SecurityMgmt

ControlPlane

Interface

Control PlaneCommunication

to / fmControlPlane

to / fmLCT

Man

agem

ent

Info

rmat

ion

(MI)

Equ

ipm

ent

Con

trol

Func

tion

Man

agem

ent

Info

rmat

ion

(MI)

Date & Time management (local real time clock and performance monitoring clock)Data communication for MCN and SCNFault management

Transmission supervision (Continuity, Connectivity, Signal quality, Payload type, Multiplex structure, Alignment, Protocol, Single-ended, Alarm suppression, etc.)QoS supervisionHardware, processing, & environmental supervisionAlarm handling (Severity assignment, Alarm reporting control, Alarm reporting)

Performance managementNear-end and Far-end PMBring-into-service, QoS, Maintenance, AvailabilityPM data collection, Scheduling, Thresholding, Reporting, Retrieval

Security management

MO Managed Object

ManagementInformation Base MO MO

MIBMOMOMO


NE-level management in G.8051 (G.eot-mgmt)

Built on G.7710 common equipment management function requirementsManage the Provisioning & Monitoring of EoT processes in the EoTtransport functionsEoT processes

OAM-related processes (CC, LM, DM, 1DM, TST, LCK, …)Queuing, Filtering, 802.3 protocol, MAC length check processes

EoT functionsETH (Ethernet MAC layer)

Flow forwarding, flow termination, connection, diagnostic, & TCS (traffic conditioning/shaping) functions

ETYn (Ethernet PHY layer) Trail termination function

Adaptation functionsETH server to ETH clientETYn server to ETH clientPDH server to ETH clientSDH server to ETH clientOTN server to ETH client

ETH link aggregation functionMapping functions

GFP-F-based mapping of Ethernet into SDHGFP-T-based mapping of Gigabit Ethernet code words into VC-4-Xv

MI

MI

MI

MI

ProcessProcessProcessProcessProcessProcessProcess

Transport function


Example:VC-n / ETH Adaptation Sink function (Sn/ETH_A_Sk)

ETH_CI

Sn/ETH_A_Sk_MI

Sn_AI

Sn/ETH_A_SkETH_PI

(ETHTF_PP)

(ETHF_PP)

To ETH_FP

To ETH_TFP

ETH_RI

ETH_TFP: ETH_CI_Data ETH_CI_SSF

ETH_FP: ETH_CI_Data ETH_CI_SSF

ETH_RP: ETH_RI_RSF

Sn/ETH_A_Sk_MI:Sn/ETH_A_Sk_MI_AcSL; Sn/ETH_A_Sk_MI_AcEXI Sn/ETH_A_Sk_MI_AcUPI; Sn/ETH_A_Sk_MI_cPLM Sn/ETH_A_Sk_MI_cLFD; Sn/ETH_A_Sk_MI_cUPM Sn/ETH_A_Sk_MI_cEXM; Sn/ETH_A_Sk_MI_cCSF Sn/ETH_A_Sk_MI_pErrors

Sn_AP: Sn_AI_Data Sn_AI_ClocK Sn_AI_FrameStart Sn_AI_TSF

ETHF_PP: ETH_PI_Data

ETHTF_PP: ETH_PI_Data

Sn/ETH_A_Sk_MI:Sn/ETH_A_Sk_MI_FilterConfig Sn/ETH_A_Sk_MI_CSF_Reported Sn/ETH_A_Sk_MI_MAC_Length

OutputsInputs

Fig.11-3 & Table 12-2 /G.8021


Processing of EoT Fault Cause for Fault Management in NE

PRS SEV ARC REP

STA

NEA

Tra

nsp

ort

Ato

mic

Funct

ions

Fault cause

cSSFcLCKcMMGcUNMcUNPcUNPricUNLcDEGcRDIcPLLcTLLcLOScPLMcLFDcUMPcEXMcCSF

Failure

fZZZ-value fZZZ-valuefZZZ-severity

fZZZ-valuefZZZ-severityfZZZ-arc

Reportable failure

Man

agem

ent

Applic

atio

n F

unct

ion

TEP

ASY

fZZZ-valuefZZZ-severity

LOG

TAN

UNA

CPL

AST

OPS

Alarm severity assignment info

Alarm reporting control info

Unit alarms

NE alarms

Station alarms

Alarm synchronization

QueryReport

TMN alarm notifications

Current problem list

Alarm status

Operational state

fZZZ-valuefZZZ-severity

FaultManagement

Date & Time functionsNE-RTC


MEME

ME

ME

ME

ME MEME

EMS Domain

SNC 1 SNC 2

EMS1

NMS

EMS2

End to End Subnetwork Connection (SNC)

Trail

Link Connection

Subnetwork

SNC SNC

Network-level managementManagement solutions for

Resource discovery and inventory: discover, query, notify changes, & DB re-syncResource provisioning: Termination point (terminate/map mode, transmission parameters), topological link (creation), …Connection management: create, activate, add route, re-route, modify, remove route, deactivate, delete, …Protection management: Protection group, invoke protection switch Fault management: alarm notification, acknowledgement, retrieval, reconciles active alarms, root cause analysis, …Performance management: collection, retrieval, reporting, thresholding …


MEF-15 for Metro Ethernet NE Management

Requirements for managing Metro Ethernet (ME) NE (Phase 1)ME NE is a Provider Edge NE supporting carrier-class Ethernet Services

UNI Types 1, Ethernet Virtual Connections (EVC – FDFr), EVC Endpoints (FP) Configuration, MEF-10 Ethernet services and Service attributes, Performance measurements

ConfigurationNotification of local configuration mgmt activity and state changes Configuration backup & recovery NE installation & configuration, software loading, transport layer port configuration, MAU transport termination configurationService mgmt (bandwidth profile, ETH UNI, EVC FP) Status and control (state change, activation/deactivation of NE fn)

FaultAlarm reporting control, Alarm monitoring, Alarm logging, Fault localization and test, Fault recovery

PerformanceGeneral performance, traffic counters & reporting, thresholdingData collection control

SecurityIdentification/authentication of usersSession control, Resource access controlSecurity administration and audit


Q.840.1 for EoT & Metro Ethernet Network management

Requirements and analysis for the NMS/EMS interface for managing EoT & ME NetworksFocus on ETH layer over dedicated/private or shared/virtual bandwidth provided by the transport layer (SDH/SONET, PDH, ATM, MPLS, OTH, ETY, etc.)Provide a model for VLAN-based Ethernet services, including G.8011 EPL, EVPL, EPLAN, EVPLAN, and MEF-6 E-line and E-LAN servicesCover network view and service (customer) view and NE-level information exchanged at the NMS/EMS I/F

Network view management: Discovery of FD, FPP, FPP linksFPP and ELMI: Creation/deletion/modification/retrieval

Service view management: FDFr/EVC: discovery, provisioning, release, retrieval, add/remove FPsBandwidth profile, Service class profile, Performance profile: create/delete/modify/retrieval

Fault management: generic approachPerformance management: performance data sets for

UNI Anomalies, UNI traffic, Ingress/Egress traffic management, Congestion discards, ELMI


EPON & GPON management

Q.838.1 for EPON managementRequirements & analysis for the NMS/EMS I/FThe EMS manages the individual EPON-supporting NEs & the networks among themEPON-specific managed entities

EPON NE, OLT, ONU, ONT, Passive splitter, Physical port of OLT, ONU, ONTMAC bridge matrix, spanning tree, & bridge port; …

Cover configuration, performance, fault, & loopbackFault management: generic approachPerformance mgmt: Data from OLT, ONU, ONT for

Ethernet ports, PON ports, E1 ports, & VLAN portsG.984.4 for GPON management

Provides the ONT Mgmt & Control Interface (OMCI) specification for GPON systemsSpecifies protocol-neutral MIB for mgmt exchange between OLT and ONTCovers ONT management & control channel, protocol, & detailed messages


TMF MTNM Specifications for Multi-Technology Network Management

Multi Transport TechnologiesSDH/SONET, OTH, PDH, ATM, FR, DSL, Ethernet, …

Network-level and element-level managementNMS/EMS interface

Full specifications Requirements & use cases: TMF 513 (BA) Analysis (protocol-neutral object model): TMF 608 (IA) Protocol-specific Solution: TMF814 (SS-CORBA/IDL)Implementation statements & Guideline: TMF814ASupporting documents

Release 3.5 enhancement Ethernet bridge and VLAN managementOptical control plane management


TMF MTNM Release 3.5 for Carrier-class Ethernet management

Release 3.5 enhancement provides a framework for supporting connectionless technology management (See supporting document SD1-44) and compliant with generic concepts in G.809 and G.8010

SD1-44 “Connectionless Technology Management”Address the management of Ethernet MAC layer (ETH) and related technologies as defined in G.8011 and MEF-10

Point-to-point service (EPL & EVPL): in compliance with MEF-10Multipoint service (EPLAN, EVPLAN): will require future alignment with MEF-10 phase 2

Target at managing Ethernet over traditional or next generation transport networkThe model is designed to complement and integrates seamlessly with the existing G.805-based MTNM Rel. 3.0 (connection-oriented) technologiesSimilar modeling activities from Q.840.1 and MEF-15 have been considered for consistency


MTNM Rel 3.5 for Carrier-class Ethernet Mgmt –Capabilities

EPL, EVPL, EPLAN, EVPLANLink aggregationPoint-to-point Call

Represent connectionless connectivity between NEs provisioningInclude control plane option and diverse routes

Multipoint topological linksRepresent RPR transport connectivity

CPTP (connectionless port TP) provisioningFixed MFD modeling (e.g., directly mapped EPL services)VLAN-unaware routing per IEEE 802.1DC-VLAN based tagging as per IEEE 802.1QS-VLAN based tagging as per IEEE 802.1adPort (UNI/NNI), C-VLAN/EVC and/or CoS (802.1p) based classificationSpanning Tree managementIngress traffic conditioningC-Tag/S-Tag translationIntegrated or separate transport (SDH/SONET etc.) and Ethernet EMSs


MTNM future support for Carrier-class Ethernet management

Non S-VLAN based tagging (e.g., Pseudo-wire encapsulation)Egress and internal Traffic ConditioningHandling of mutual influence of bandwidth configuration within one portSplitting and merging of MFD and FDModeling of client side of an UNI (per MEF-10)XML Solution Set (integration with TMF MTOSI)New packet transport technologies (including PBB-TE and T-MPLS)Ethernet layer termination


DCN consideration for Management and Control

G.8051 (G.eot-mgmt) describes the EoT network management architecture within TMN, including EoT management network (E.MN) and EoT management sub-network (E.MSN). G.7712 is being updated to incorporate the MCN and SCN aspects of the DCN for new packet transport technologies, e.g. EoT and T-MPLSSame approach for EoT and T-MPLS

Aspects such as the separation of management and control plane communication flows and the multiplexing of these flows with user traffic is being addressed in a technology independent manner. This includes traffic conditioning and shaping functions for the SCN and MCN flows that may be needed for communication channels thatdo not provide a bandwidth limitation like e.g. the DCCs in SONET/SDH.

Y.1731 defines an EoT MCC for maintenance communication between peer Maintenance Entity Group (MEG) End Points (MEP)

MCC/SCC option for management and signaling will require the existence of MEP, which might not be desirable in some cases. Q14/15 is exploring also other possible options, including ECC in the PHY layer


Thank you!


Acronyms and AbbreviationsARC Alarm Reporting Control functionASON Automatically Switched Optical NetworkAST Alarm Status functionASY Alarm Synchronization functionBA Business AgreementCPL Current Problem List functionCORBA Common Object Request Broker ArchitectureCP Control PlaneCPTP Connectionless Port Termination Point (Bridge Port)CSMA/CD Carrier Sense Multiple Access / Collision DetectionCTP Connection Termination PointDCN Data Communication NetworkDSL Digital Subscriber LineEMS Element Management SystemEoT Ethernet over TransportEPON Ethernet Passive Optical NetworkFD Flow DomainFDFr Flow Domain FragmentEFM Ethernet in the First MileFP Flow PointFTP Floating Termination PointGFP Generic Framing ProcedureGPON Gigabit-capable Passive Optical NetworkIA Information AgreementIDL Interface Definition LanguageIS Implementation StatementLAN Local Area NetworkLCAS Link Capacity Adjustment SchemeLOG event notification Logging functionMAC Media Access ControlMAN Metropolitan Area NetworkMAU Media Attachment UnitMCN Management Communication NetworkMEN Metro Ethernet NetworkMFD Matrix Flow Domain (Bridge)MFDFr Matrix Flow Domain FragmentMIB Management Information BaseMP Management PlaneMTNM Multi Technology Network Management

mTOP multi Technology OSS ProgramMTOSI Multi Technology Operations System InterfaceNE Network ElementNEA Network Element Alarm functionNNI Network to Network InterfaceNMS Network Management SystemOAM Operations Administration MaintenanceOLT Optical Line TerminationONT Optical Network TerminationOPS Operational State functionOS Operations SystemOSS Operations Support SystemOTN Optical Transport NetworkPRS Persistency filterPTP Physical Termination PointREP Reportable failure functionRTC Real Time ClockSCN Signaling Communication NetworkSD Supporting DocumentSDH Synchronous Digital HierarchySDO Standards Defining OrganizationSEV Severity assignment functionSNC Sub-Network ConnectionSNMP Simple Network Management ProtocolSONET Synchronous Optical NETworkSS Solution SetSTA Station alarms functionTAN TMN Alarm event Notification functionTEP TMN Event Processing functionTMF TeleManagement ForumTMN Telecommunication Management NetworkVC Virtual Container (in SDH)VCAT Virtual ConcatenationVLAN Virtual Local Area NetworkUNA Unit Alarm functionUNI User to Network InterfaceWG Working GroupWIS WAN Interface Sub-layerXML eXtensible Markup Language


"simple" scenario* Ethernet client layer* Single MTNM interface* Multiple Multi-layer sub-networks (MLSN)

CTP

CTP

CTP1

CTP2

MLSN 1

TL a

MLSN 2

CTP

CTP

CTP

CTP

CTP

CTP

CTP

CTP

CTP

CTP

MLSN 3 MLSN 4

CTP4

CTP3

SNC

SNC

TL b TL cNamingPointer

CPTP(PTP)

MFDFrFP

(CTP)MFD1

FlowDomain

MFD2

MFDFr CPTP(PTP)

FP(CTP)

FP(CTP)

FP(CTP)

TL 1

FDFr

CPTP1(FTP1)

CPTP2(FTP2)

EMS

MTNM

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

MTNM support of EoT Network-level management – Simple Scenario


"Complex case" scenario* Ethernet client layer* Multiple MTNM interfaces* Technology specific EMSes* Multiple MLSNsCPTP

(PTP)(M)FDFr

CPTP1(FTP1)

FP(CTP)

CTP

CTP

CTP1

CTP2

MFD 1

FD 1

MLSN 1a

TL TL

MLSN 1b

CTP4

CTP3

CTP

CTP

CTP

CTP

CTP

CTP

TL

CTP5

CTP6

MLSN 3 MLSN 2

MFD 2

FD 2

(M)FDFr CPTP(PTP)

CTP8

CTP7

ETHEMS1

MTNM

SDHEMS1

MTNM

NEManag.

NEManag.

off-networkTPs

NEManag.

NEManag.

ETHEMS2

MTNM

SDHEMS2

MTNM

SDHEMS3

MTNM

TL TL

CPTP2(FTP2)

FP(CTP)

FP(CTP)

FP(CTP)

TL 1 TL 2

NamingPointer

CPTP1(FTP1)

CPTP2(FTP2)

Pointer to off-network TPs

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

MTNM support of EoT Network-level mgmt– Complex Scenario


EMS EMS

Multi-technology management for Optical Control plane

Transport Plane

Control Plane

Man

agem

ent

Plan

e

G.7718.1

EMS

NMS

NetworkElement

G.7718

MTNM v3.5


"simple" Call scenario* Ethernet client layer* Single MTNM interface* Multiple MLSNs

CPTP(PTP)

MFDFrFP

(CTP)

CTP

CTP

CTP1

CTP2

MFD1

FlowDomain

MLSN 1

TL a

MLSN 2

CTP

CTP

CTP

CTP

CTP

CTP

CTP

CTP

CTP

CTP

MLSN 3 MLSN 4

MFD2

MFDFr CPTP(PTP)

CTP4

CTP3

SNC

SNC

FP(CTP)

FP(CTP)

FP(CTP)

Call

TL 1

top level Connection b

top level Connection a

top levelMLRA

FDFr

TL b TL cNamingPointer

CPTP1(FTP1)

CPTP2(FTP2)

EMS

MTNM

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

MTNM Support for Optical control plane – Simple Call Scenario


“Complex case" Call scenario* Ethernet client layer* Multiple MTNM interfaces* Technology specific EMSes* Multiple MLSNs

CPTP(PTP)

(M)FDFr

CPTP1(FTP1)

FP(CTP)

CTP

CTP

CTP1

CTP2

MFD 1

FD 1

MLSN 1a

TL TL

MLSN 1b

CTP4

CTP3

CTP

CTP

CTP

CTP

CTP

CTP

TL

CTP5

CTP6

MLSN 3 MLSN 2

MFD 2

FD 2

(M)FDFr CPTP(PTP)

CTP8

CTP7

ETHEMS1

MTNM

SDHEMS1

MTNM

NEManag.

NEManag.

off-networkTPs

NEManag.

NEManag.

ETHEMS2

MTNM

SDHEMS2

MTNM

SDHEMS3

MTNM

TL TL

CPTP2(FTP2)

FP(CTP)

FP(CTP)

FP(CTP)

Call 1 (fragment)

TL 1 TL 2

top level Connection b

top level Connection a top levelMLRA 1

Call 2 (frag)

NamingPointer

tl Connection c

tl Connection d

CPTP1(FTP1)

CPTP2(FTP2)

top levelMLRA 2

Pointer to off-network TPs

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

SNC

SNC

CC CC

CC CC

MTNM support for Optical CP– Complex Call Scenario

Joint ITU-T/IEEE Workshop on Carrier-class Ethernet · Joint ITU-T/IEEE Workshop on Carrier-class...

Documents

Transcript of Joint ITU-T/IEEE Workshop on Carrier-class Ethernet · Joint ITU-T/IEEE Workshop on Carrier-class...