Folie 1

1
Transport equipment andnetwork
management Presentation for the T-MPLS JWT
2
Recommendation Overview
commonequipment management requirements
G.7710
general
G.806
circuit based
packet based
equipment management requirements
G.8051(EoT)
G.874(OTN)
G.784(SDH)
G.8151(T-MPLS)
G.8121
equipmentspecification(Q.9/15)
protocol neutral information model NE view
G.8052(EoT)
G.874.1(OTN)
G.774(SDH)
G.8152(T-MPLS)
architectureandspecification of DCN
G.7712
3
G.7710

• TitleCommon equipment management function
  requirements
• Summary
• addresses the Equipment Management Functions
  (EMFs) inside a transport Network Element that
  are common to multiple technologies
• common applications are- Date Time- Fault
  Management- Configuration Management- Account
  Management- Performance Management- Security
  Management
• applications result in the specification of
  common EMF functions and their requirements

4
G.7710 Equipment Management Functions
Figure 5/G.7710/Y.1701 ? Equipment Management
Function process block diagram
5
G.7710 Configuration Management
Figure 22/G.7710/Y.1701 ? Configuration
Management inside the EMF
6
G.7710 Fault Management
Figure 7/G.7710/Y.1701 ? Fault Management inside
the EMF
7
Performance Monitoring inside the EMF (G.7710)
8
Performance Monitoring inside the EMF (G.7710)
9
G.806

• TitleCharacteristics of transport equipment
  Description methodology and generic functionality
• Summary
• specifies a methodology to describe equipment for
  transport networks- based on transport
  processing functions- based on architectural
  entities defined in Recommendation G.805
• defines generic atomic and compound functions
• specifies generic functionality, processes and
  overall performance objectives for transport
  networks
• specifies the Information provided by the atomic
  functions which can be used for Management

10
G.806 atomic functions
Figure 5-1/G.806 Atomic functions and reference
points
11
Generic info flow (G.806) Transport Atomic Fn ?
MP ? Equipment Mgmt Fn
12
Generic info flow (G.806) Transport Atomic Fn ?
MP ? Equipment Mgmt Fn (cont)
13
G.8121

• TitleCharacteristics of T-MPLS equipment
  functional blocks
• Summary
• specifies a library of functional building blocks
  for the T-MPLS layer network

14
G.8121 atomic functions
Figure 1/G.8121/Y.1381 MPLS atomic functions
15
T-MPLS Trail Termination Sink function
(TM2_TT_Sk)Fig.9-4 Table 1 /G.8121
16
ODUk to T-MPLS adaptation sink function
(ODUkP/TM_A_Sk)Fig.45 Table 11 /G.8121 Amd.1
17
G.8151

• TitleManagement aspects of the T-MPLS network
  element
• Summary
• addresses management aspects of the
  Transport-MPLS capable Network Element
• management of Transport-MPLS layer networks is
  separable from that of its client layer ? client
  layer independent
• management functions are- Fault Management-
  Configuration Management- Performance
  Monitoring- Security Management

18
G.8151 (cont.)

• T-MPLS equipment functions (per currently
  specified in G.8121)
• T-MPLS layer connection function,
• T-MPLS layer trail termination functions,
• T-MPLS server to T-MPLS client adaptation
  functions,
• T-MPLS server to Ethernet client adaptation
  functions,
• SDH server to T-MPLS client adaptation functions,
• PDH server to T-MPLS client adaptation functions,
  and
• OTN sever to T-MPLS client adaptation functions.

19
G.8152

• TitleRequirements and Analysis for
  protocol-neutral Information Model of T-MPLS for
  Network Element Management
• Summary
• specifies the North Bound Interface of the
  Network Element to the Element Management System
  (EMS) in a protocol-neutral style
• identifies TMN managed entities
• follows the interface specification methodology
  described in M.3020
• follows TMN principles specified in M.3010
• follows the T-MPLS architecture principles
  specified in Recommendation G.8110.1
• management functions are- Fault Management-
  Configuration Management- Performance Monitoring
• specification contains- requirements- use
  cases- information model using the Unified
  Modeling Language (UML).

20
G.8152 information model
21
G.7712

• TitleArchitecture and specification of Data
  Communication Network (DCN)
• Summary
• defines the architecture requirements for a DCN
• supports distributed management communications
  related to TMN- Management Communication Network
  (MCN)- Signaling Communication Network (SCN)
• supports distributed control plane
  communications(e.g., signaling and routing)
  related to ASON
• supports distributed communications(e.g.,
  Orderwire or Voice Communications, Software
  Download)
• considers networks that are- IP-only-
  OSI-only- mixed (i.e., support both IP and OSI)
• specifies interworking between parts of the DCN
  supporting IP-only, parts supporting OSI-only,
  and parts supporting both IP and OSI

22
Communication Channels
OS
OS
MD
common terminology
NE
NE
LAN
NE
ECC
ECC
ECC
NE
ECC
NE
NE
DCN
OS
OS
OS
OS
T-MPLS specific terminologies
MD
MD
NE
NE
NE
NE
LAN
LAN
NE
MCC
NE
SCC
MCC
SCC
MCC
SCC
NE
NE
MCC
SCC
NE
NE
NE
NE
MCN
SCN
management communication
Management Communication Network (MCN)
Signalling Communication Network (SCN)
Data Communication Network (DCN)
ECC Embedded Communication ChannelMCC Management
Communication ChannelSCC Signalling
Communication Channel