T Rec G.874 201007 S!!PDF e

I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
ITU-T G.874
TELECOMMUNICATION (07/2010)
STANDARDIZATION SECTOR
OF ITU
SERIES G: TRANSMISSION SYSTEMS AND MEDIA,

DIGITAL SYSTEMS AND NETWORKS
Digital networks – Optical transport networks
Management aspects of optical transport

network elements
Recommendation ITU-T G.874

ITU-T G-SERIES RECOMMENDATIONS
TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS
INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100–G.199

GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER- G.200–G.299
TRANSMISSION SYSTEMS
INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE G.300–G.399
SYSTEMS ON METALLIC LINES
GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS G.400–G.449
ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC
LINES
COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450–G.499
TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS G.600–G.699
DIGITAL TERMINAL EQUIPMENTS G.700–G.799
DIGITAL NETWORKS G.800–G.899
General aspects G.800–G.809
Design objectives for digital networks G.810–G.819
Quality and availability targets G.820–G.829
Network capabilities and functions G.830–G.839
SDH network characteristics G.840–G.849
Management of transport network G.850–G.859
SDH radio and satellite systems integration G.860–G.869
Optical transport networks G.870–G.879
DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900–G.999
MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE – GENERIC AND USER- G.1000–G.1999
RELATED ASPECTS
TRANSMISSION MEDIA CHARACTERISTICS G.6000–G.6999
DATA OVER TRANSPORT – GENERIC ASPECTS G.7000–G.7999
PACKET OVER TRANSPORT ASPECTS G.8000–G.8999
ACCESS NETWORKS G.9000–G.9999
For further details, please refer to the list of ITU-T Recommendations.

Management aspects of optical transport network elements
Summary
Recommendation ITU-T G.874 addresses management aspects of optical transport network elements
containing transport functions of one or more of the layer networks of the optical transport network.
The management of the optical layer networks is separable from that of its client layer networks so
that the same means of management can be used regardless of the client. The management functions
for fault management, configuration management and performance monitoring are specified.
The 2008 revision of this Recommendation has updated the management information to align with
Recommendation ITU-T G.798, reorganized the sections to align with the structure of
Recommendation ITU-T G.7710/Y.1701, and replaced the generic text with pointers to
Recommendation ITU-T G.7710/Y.1701.
The 2010 revision of this Recommendation has added the management of new transport functions
that have been introduced in the 2010 revision of Recommendation ITU-T G.798, including
OPSMnk_TT, OPSM/OTUk-a_A, and ODUk for k=0, 2e, 4, and flex.
History
Edition Recommendation Approval Study Group
1.0 ITU-T G.874 2001-11-29 15
2.0 ITU-T G.874 2008-03-29 15
3.0 ITU-T G.874 2010-07-29 15
Rec. ITU-T G.874 (07/2010) i

FOREWORD
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of
telecommunications, information and communication technologies (ICTs). The ITU Telecommunication
Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical,
operating and tariff questions and issuing Recommendations on them with a view to standardizing
telecommunications on a worldwide basis.
The World Telecommunication Standardization Assembly (WTSA), which meets every four years,
establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on
these topics.
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
In some areas of information technology which fall within ITU-T's purview, the necessary standards are
prepared on a collaborative basis with ISO and IEC.
NOTE
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a
telecommunication administration and a recognized operating agency.
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain
mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the
Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some
other obligatory language such as "must" and the negative equivalents are used to express requirements. The
use of such words does not suggest that compliance with the Recommendation is required of any party.
INTELLECTUAL PROPERTY RIGHTS

ITU draws attention to the possibility that the practice or implementation of this Recommendation may
involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence,
validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others
outside of the Recommendation development process.
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property,
protected by patents, which may be required to implement this Recommendation. However, implementers
are cautioned that this may not represent the latest information and are therefore strongly urged to consult the
TSB patent database at http://www.itu.int/ITU-T/ipr/.
 ITU 2011
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the
prior written permission of ITU.
ii Rec. ITU-T G.874 (07/2010)

CONTENTS
Page
1 Scope ............................................................................................................................ 1
2 References..................................................................................................................... 1
3 Terms and definitions ................................................................................................... 3
3.1 Terms defined elsewhere ................................................................................ 3
4 Abbreviations and acronyms ........................................................................................ 4
5 Conventions .................................................................................................................. 8
6 OTN management functions ......................................................................................... 8
6.1 OTN network management architecture ........................................................ 9
6.2 OTN equipment management function .......................................................... 13
6.3 Information flows over management points (MPs) ........................................ 14
7 Fault management ......................................................................................................... 15
7.1 Fault management applications ...................................................................... 15
7.2 Fault management functions........................................................................... 16
8 Configuration management .......................................................................................... 26
8.1 Hardware ........................................................................................................ 26
8.2 Software .......................................................................................................... 26
8.3 Protection switching ....................................................................................... 26
8.4 Trail termination ............................................................................................. 26
8.5 Adaptation ...................................................................................................... 29
8.6 Connection ...................................................................................................... 37
8.7 DEG thresholds .............................................................................................. 38
8.8 XXX_Reported ............................................................................................... 38
8.9 Alarm severity ................................................................................................ 38
8.10 Alarm reporting control (ARC) ...................................................................... 39
8.11 PM thresholds ................................................................................................. 39
8.12 Tandem connection monitoring (TCM) activations ....................................... 39
8.13 Date and Time ................................................................................................ 39
8.14 Control function.............................................................................................. 40
9 Account management ................................................................................................... 40
10 Performance management ............................................................................................ 40
10.1 Performance management applications .......................................................... 41
10.2 Performance management functions .............................................................. 43
11 Security management.................................................................................................... 44
Appendix I – Management information for CM ...................................................................... 45
Appendix II – Management information for PM ..................................................................... 47
Rec. ITU-T G.874 (07/2010) iii

Management aspects of optical transport network elements
1 Scope
This Recommendation addresses management aspects of optical transport network elements
containing transport functions of one or more layer networks of the optical transport network (OTN)
as described in [ITU-T G.709]. The management of optical layer networks is separable from that of
its client layer networks; therefore, the same means of management can be used regardless of the
client. The management functions for fault management, configuration management, account
management, performance management and security management are specified.
This Recommendation describes the management network organizational model for communication
between an element management layer (EML) operations system and the optical equipment
management function within an OTN network element.
The architecture described in this Recommendation for the management of optical transport
networks is based upon the following considerations:
– The management view of network element functional elements should be uniform whether
those elements form part of an inter-domain interface or part of an intra-domain interface.
Those properties necessary to form such a uniform management view are to be included in
this Recommendation.
– Optical layer network entities (OLNEs) refer to trail termination, adaptation, connection
functions as described in [ITU-T G.872].
– A network element may only contain optical layer network entities.
– A network element may contain both optical layer network entities (OLNEs) and client
layer network entities (CLNEs).
– Client layer entities are managed as part of their own logical domain (e.g., SDH
management network).
– CLNEs and OLNEs may or may not share a common message communications function
(MCF) and management application function (MAF) depending on application.
– CLNEs and OLNEs may or may not share same agent.
2 References
The following ITU-T Recommendations and other references contain provisions which, through
reference in this text, constitute provisions of this Recommendation. At the time of publication, the
editions indicated were valid. All Recommendations and other references are subject to revision;
users of this Recommendation are therefore encouraged to investigate the possibility of applying the
most recent edition of the Recommendations and other references listed below. A list of the
currently valid ITU-T Recommendations is regularly published. The reference to a document within
this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
[ITU-T G.709] Recommendation ITU-T G.709/Y.1331 (2009), Interfaces for the Optical
Transport Network (OTN).
[ITU-T G.784] Recommendation ITU-T G.784 (2008), Management aspects of synchronous
digital hierarchy (SDH) transport network elements.
[ITU-T G.798] Recommendation ITU-T G.798 (2010), Characteristics of optical transport
network hierarchy equipment functional bocks.
Rec. ITU-T G.874 (07/2010) 1

[ITU-T G.805] Recommendation ITU-T G.805 (2000), Generic functional architecture of
transport networks.
[ITU-T G.806] Recommendation ITU-T G.806 (2009), Characteristics of transport equipment –
Description methodology and generic functionality.
[ITU-T G.826] Recommendation ITU-T G.826 (2002), End-to-end error performance
parameters and objectives for international, constant bit-rate digital paths and
connections.
[ITU-T G.870] Recommendation ITU-T G.870/Y.1352 (2008), Terms and definitions for optical
transport networks (OTN), plus Amendment 1 (2009).
[ITU-T G.872] Recommendation ITU-T G.872 (2001), Architecture of optical transport
networks, plus Amendment 1 (2003).
[ITU-T G.873.1] Recommendation ITU-T G.873.1 (2006), Optical Transport Network (OTN):
Linear protection.
[ITU-T G.874.1] Recommendation ITU-T G.874.1 (2002), Optical transport network (OTN):
Protocol-neutral management information model for the network element view.
[ITU-T G.7710] Recommendation ITU-T G.7710/Y.1701 (2007), Common equipment
management function requirements.
[ITU-T G.7712] Recommendation ITU-T G.7712/Y.1703 (2008), Architecture and specification
of data communication network.
[ITU-T M.20] Recommendation ITU-T M.20 (1992), Maintenance philosophy for
telecommunication networks.
[ITU-T M.2120] Recommendation ITU-T M.2120 (2002), International multi-operator paths,
sections and transmission systems fault detection and localization procedures.
[ITU-T M.2140] Recommendation ITU-T M.2140 (2000), Transport network event correlation.
[ITU-T M.3010] Recommendation ITU-T M.3010 (2000), Principles for a telecommunications
management network, plus Amendments 1 (2003) and 2 (2005).
[ITU-T M.3013] Recommendation ITU-T M.3013 (2000), Considerations for a
telecommunications management network.
[ITU-T M.3100] Recommendation ITU-T M.3100 (2005), Generic network information model.
[ITU-T Q.822] Recommendation ITU-T Q.822 (1994), Stage 1, stage 2 and stage 3 description
for the Q3 interface – Performance management.
[ITU-T X.700] Recommendation ITU-T X.700 (1992), Management framework for Open
Systems Interconnection (OSI) For CCITT applications.
[ITU-T X.701] Recommendation ITU-T X.701 (1997) | ISO/IEC 10040:1998, Information
technology – Open Systems Interconnection – Systems management overview.
[ITU-T X.721] Recommendation ITU-T X.721 (1992) | ISO/IEC 10165-2:1992, Information
technology – Open Systems Interconnection − Structure of management
information: Definition of management information.
technology – Open Systems Interconnection − Systems Management: Alarm
reporting function, plus Amendment 1 (1995).
2 Rec. ITU-T G.874 (07/2010)

technology – Open Systems Interconnection − Systems Management: Log control
function, plus Amendment 1 (1995).
technology – Open Systems Interconnection − Systems management: Software
management function.
3 Terms and definitions
3.1 Terms defined elsewhere

This Recommendation uses the following terms defined elsewhere:
3.1.1 agent: [ITU-T X.701]
3.1.2 aggregate audible/visual indicators: [ITU-T M.3100]
3.1.3 alarm reporting: [ITU-T M.3100]
3.1.4 alarm reporting control: [ITU-T M.3100]
3.1.5 alarm reporting control interval: [ITU-T M.3100]
3.1.6 atomic function: [ITU-T G.806]
3.1.7 data communications channel (DCC): [ITU-T G.784]
3.1.8 data communication network (DCN): [ITU-T G.7712]
3.1.9 embedded control channel (ECC): [ITU-T G.7712]
3.1.10 general communication channel: [ITU-T G.709]
3.1.11 general management communications overhead: [ITU-T G.709]
3.1.12 inhibited: [ITU-T M.3100]
3.1.13 inter-domain interface (IrDI): [ITU-T G.872]
3.1.14 intra-domain interface (IaDI): [ITU-T G.872]
3.1.15 local craft terminal (LCT): [ITU-T G.7710]
3.1.16 managed entity: [ITU-T M.3100]
3.1.17 managed object: [ITU-T X.700]
3.1.18 managed object class: [ITU-T X.701]
3.1.19 managed resource: [ITU-T M.3100]
3.1.20 managed resource-specific: [ITU-T M.3100]
3.1.21 management application function (MAF): [ITU-T G.7710]
3.1.22 management interface: [ITU-T M.3100]
3.1.23 management point (MP): [ITU-T G.806]
3.1.24 manager: [ITU-T X.701]
3.1.25 message communication function: [ITU-T M.3013]
3.1.26 network element: [ITU-T M.3010]
3.1.27 network element function: [ITU-T M.3010]
3.1.28 operations system (OS): [ITU-T M.3010]
Rec. ITU-T G.874 (07/2010) 3

3.1.29 OTN network element (O.NE): [ITU-T G.870]
3.1.30 OTN management network (O.MN): [ITU-T G.870]
3.1.31 OTN management subnetwork (O.MSN): [ITU-T G.870]
3.1.32 persistence interval: [ITU-T M.3100]
3.1.33 Q interface: [ITU-T M.3010]
3.1.34 qualified problem: [ITU-T M.3100]
3.1.35 reset threshold report: [ITU-T M.3100]
3.1.36 threshold report: [ITU-T M.3100]
3.1.37 timed interval: [ITU-T M.3100]
3.1.38 unit audible/visual indicator: [ITU-T M.3100]
3.1.39 workstation function: [ITU-T M.3010]
4 Abbreviations and acronyms

This Recommendation uses the following abbreviations and acronyms:
1second 1-second pulse
AcPT Accepted PT
AcSTAT Accepted STAT
AcTI Accepted TTI
AdminState Administrative State
AIS Alarm Indication Signal
ALM ALarM reporting
AP Access Point
APR Automatic Power Reduction
APRCntrl Automatic Power Reduction Control
ARC Alarm Reporting Control
AutoMS Automatic configuration of the Multiplex Structure
BDI Backward Defect Indicator
BDI-O Backward Defect Indicator Overhead
BDI-P Backward Defect Indicator Payload
BIAE Backward Incoming Alignment Error
CBRx Constant Bit Rate signal of bit rate [range] x
CLNE Client Layer Network Entity
COMMS OH general management Communications Overhead
CP Connection Point
CTP Connection Termination Point
DCC Data Communications Channel
DCN Data Communication Network
4 Rec. ITU-T G.874 (07/2010)

DS Defect Second
DS-O Defect Second Overhead
DS-P Defect Second Payload
DEG Degraded defect
DEGM DEG consecutive 1-second monitoring intervals
DEGThr DEG 1-second EBC threshold
DTDL Defect Type and Defect Location
EBC Errored Block Count
ECC Embedded Control Channel
EMF Equipment Management Function
EMS Element Management System
ExDAPI Expected Destination Access Point Identifier
ExMSI Expected Multiplex Structure Identifier
ExSAPI Expected Source Access Point Identifier
ExtCMD External Command
F Far-end
FCAPS Fault, Configuration, Accounting, Performance and Security management
FDI Forward Defect Indicator
FDI-O Forward Defect Indicator Overhead
FDI-P Forward Error Correction Payload
FEC Forward Error Correction
FECEn Forward Error Correction Enabled
FECCorrErr Forward Error Correction Corrected Errors
FOP Failure of Protocol
FOP-PM Failure of Protocol; Provisioning Mismatch
FOP-NR Failure of Protocol; No Response
GCC General Communication Channel
GCCAccess General Communication Channel Access
GCCCont General Communication Channel Continue
GetAcTI Get Accepted Trail Trace Identifier
GFC Generic Flow Control
GNE Gateway Network Element
HEC Header Error Control
HoTime Hold-off Time
IAE Incoming Alignment Error
IaDI Intra-Domain Interface
IrDI Inter-Domain Interface
Rec. ITU-T G.874 (07/2010) 5

LAN Local Area Network
LCD Loss of Cell Delineation
LCK Locked defect
LOA Loss of Alignment
LOF Loss of Frame
LOFLOM Loss of Frame and (Loss of) Multiframe
LOFOTL Loss of Frame of Optical Lane
LOL Loss of Lane alignment
LOM Loss of Multiframe
LOS Loss of Signal
LOS-O Loss of Signal Overhead
LOS-P Loss of Signal Payload
LSS Loss of pseudo-random bit Sequence lock
LTC Loss of Tandem Connection
MAF Management Application Function
MCF Message Communications Function
MCN Management Communication Network
MI Management Information
MIB Management Information Base
MO Managed Object
MP Management Point
MSI Multiplex Structure Identifier
MSIM Multiplex Structure Identifier Mismatch
NALM No ALaRm reporting
NALM-CD No ALaRm reporting, CountDown
NALM-NR No ALaRm reporting, NotReady
NALM-QI No ALaRm reporting, Qualified Inhibit
NALM-TI No ALaRm reporting, Timed Inhibit
NE Network Element
NEF Network Element Function
NT Network Terminal
OCh Optical Channel
OChr Optical Channel with reduced functionality
OCI Open Connection Indication
ODU Optical Data Unit
ODUi Optical Data Unit of level i
ODU[i]j Optical Data Unit of level j and i (i is optional; i < j)
6 Rec. ITU-T G.874 (07/2010)

ODUj Optical Data Unit of level j
ODUj[/i] Optical Data Unit of level j or i (i is optional; i < j)
ODUk Optical Data Unit of level k, k=0, 1, 2, 2e, 3, 4, flex
ODUkP Optical Data Unit of level k, Path, k=0, 1, 2, 2e, 3, 4, flex
ODUkT Optical Data Unit of level k, Tandem connection sub-layer, k=0, 1, 2, 2e, 3, 4, flex
ODUkTm ODUkT non-intrusive monitoring function, k=0, 1, 2, 2e, 3, 4, flex
OLNE Optical Layer Network Entity
O.MN OTN Management Network
OMS Optical Multiplex Section
O.MSN OTN Management Subnetwork
OMSn Optical Multiplex Section of level n
O.NE OTN Network Element
OOS Optical transport module Overhead Signal
OPSn Optical Physical Section of level n, n=0, 16, 32
OPSMnk OPS Muti-lane, k=3, 4; n=4
OS Operations System
OSC Optical Supervisory Channel
OSI Open Systems Interconnection
OTH Open Transport Hierarchy
OTL Optical channel Transport Lane
OTLk.n. Optical Transmission Lane of OTUk lane number n
OTM Optical Transport Module
OTN Optical Transport Network
OTS Optical Transmission Section
OTSn Optical Transmission Section of level n
OTU Optical Transmission Unit
OTUk Optical Transmission Unit of level k, k=1, 2, 3, 4
OTUkV Optical Transmission Unit of level k, functional standardized, k=1, 2, 3, 4
PLM PayLoad Mismatch
PMC Performance Monitoring Clock
PPP Point-to-Point Protocol
ProtType Protection Type
PRBS Pseudo-Random Bit Sequence
PT Payload Type
RSn Regenerator Section of level n
RTC Real Time Clock
RTR Reset Threshold Report
Rec. ITU-T G.874 (07/2010) 7

SCN Signalling Communication Network
SDH Synchronous Digital Hierarchy
Sk Sink
So Source
SSF Server Signal Fail
SSF-O Server Signal Fail Overhead
SSF-P Server Signal Fail Payload
STAT Status field
TCP Termination Connection Point
TI Trace Identifier
TIM Trace Identifier Mismatch
TIMActDis Trace Identifier Mismatch consequent Actions Disabled
TIMDetMo Trace Identifier Mismatch Detection Mode
TMN Telecommunications Management Network
TP Termination Point
TPusgActive TP usage measurement Active
TR Threshold Report
TSE Test Sequence Error
TT Trail Termination
TTI Trail Trace Identifier
TTP Trail Termination Point
TTPSk Trail Termination Point Sink
TTPSo Trail Termination Point Source
TxMSI Transmitted Multiplex Structure Identifier
TxTI Transmitted Trail Trace Identifier
VcPLM Virtual concatenation Payload Mismatch
VP Virtual Path
VPI Virtual Path Identifier
5 Conventions
In this Recommendation, O.MN stands for OTN management network, O.MSN for OTN
management subnetwork, O.NE for OTN NE and FFS for further study.
6 OTN management functions

See clause 6 of [ITU-T G.7710] for the generic architecture for managing transport equipment.
OTN-specific management architecture is described below.
8 Rec. ITU-T G.874 (07/2010)

6.1 OTN network management architecture
The transport layer networks of the optical transport network (OTN) are described in
[ITU-T G.872] and [ITU-T G.709]. The management of the OTN layer networks is separable from
that of its client layer networks so that the same means of management can be used regardless of the
client.
6.1.1 Relationship between TMN, O.MN and O.MSN
The OTN management network (O.MN) may be partitioned into OTN management subnetworks
(O.MSNs). The inter-relationship between a management network, its subnetworks and a TMN as
generically described in clause 6 of [ITU-T G.7710] is applicable to OTN.
6.1.2 Access to the O.MSN
See clause 6.1.2 of [ITU-T G.7710] for the generic requirements.
6.1.3 O.MSN requirements
See clause 6.1.3 of [ITU-T G.7710] for the generic requirements.
In addition, the O.MSN allows for the support of the following:
1) O.NEs must support management communications functions. The message
communications function of an O.NE initiates/terminates (in the sense of the lower protocol
layers), forwards, or otherwise processes management messages over ECCs, or over other
data communications network interfaces. The OTN allows the ECC options of using the
general management communication overhead (COMMS OH) or the general
communication channels (GCC).
− All O.NEs are required to terminate the COMMS OH, see clause 6.1.4. In OSI terms,
this means that each NE must be able to perform the functions of an end system.
− All O.NEs are required to terminate the OTUk GCC0, see clause 6.1.4, to connect to
O.NEs (e.g., OTH NTs) that are equipped with OTM-0 and/or OTM-nr interfaces only.
− O.NEs may also be required to forward management messages between ports according
to routing control information held in the O.NE. In OSI terms, this means that some
O.NEs may be required to perform the functions of an intermediate system.
− In addition to supporting interfaces for the COMMS OH and GCC, an O.NE may also
be required to support other DCN interfaces.
2) OTN inter-site communications. The inter-site or inter-office communications link between
O.NEs will normally be formed from the COMMS OH.
3) OTN intra-site communications. Within a particular site, O.NEs may communicate via an
intra-site COMMS OH or via an LAN.
Each O.MSN must have at least one O.NE/mediation device that is connected to an OS. This O.NE
is termed a gateway network element (GNE). The GNE should be able to perform an intermediate
system network layer forwarding function for COMMS OH messages destined for any end system
in the O.MSN. Messages passing between the OS and any of the end systems in the subnetwork are
routed through the GNE and, in general, other intermediate systems.
The use of the general communication channels (GCC) for management communications is within
the scope of this Recommendation, see clause 6.1.4.
6.1.4 O.MSN data communications network
Refer to clause 6.1.4 of [ITU-T G.7710] for the generic requirements.
The main ECC for OTN is considered to be the COMMS OH in the OTM-n signal (see
clause 15.1.7 of [ITU-T G.709]). The COMMS OH is carried in the OTM overhead signal (OOS),
Rec. ITU-T G.874 (07/2010) 9

which in turn is carried in the optical supervisory channel (OSC). This COMMS-based ECC is
equivalent to the SDH STM-N MS-DCC. The use of a GCC as an ECC is typically used when one
has to reach a remote CPE or a remote subnetwork, and on OTM-0 and OTM-nr type interfaces
(OTUk GCC0).
6.1.4.1 General communication channel (GCC)
The OTN supports three general communication channels (GCCs):
1) GCC0
2) GCC1
3) GCC2
Figure 6-1 illustrates a network scenario consisting of two operators. Operator B provides an ODUk
service to operator A (i.e., operator B transports the ODUk frame which begins and ends in operator
A's domain). According to [ITU-T G.709], only a subset of the ODUk overhead (e.g., path
monitoring, etc.) is guaranteed to be passed through operator B's network. Other overheads, such as
tandem connection monitoring overhead, as well as GCC1 and GCC2 are subject to the service
level agreement made between operator A and operator B.
Operator A Operator B Operator A
3R 3R 3R 3R 3R 3R
OTUk[V] OTUk OTUk[V] OTUk OTUk[V]
ODUk
GCC0 Channel never crosses GCC0 GCC0 GCC0 GCC0 GCC0

administrative domains since
it operates between OTUk
termination points
Example a) or
GCC1
Contract allows GCC1 to pass
through Operator B but not
GCC2 GCC2
Example b) GCC1
Contract allows GCC2 to pass
through Operator B but not
GCC1 GCC2 or
Example c) GCC1 or
Contract allows GCC1 and
GCC2 to pass through
Operator B GCC2 or
Example d) GCC1
Neither GCC1 nor GCC2 are
allowed to pass -through GCC2
Operator B
T1546140-02
Figure 6-1 − GCC contract scenarios
10 Rec. ITU-T G.874 (07/2010)

GCC0 is a channel between OTUk termination points and therefore does not cross administrative
domains, since an IrDI interface supports 3R points on either end of the interface. Example a)
illustrates a scenario where the contract between operators A and B only allows GCC1 to pass
through operator B's network. In such a scenario, operator B may use GCC2 within its own
network. Example b) illustrates a scenario where the contract between operators A and B only
allows GCC2 to pass through operator B's network. In this scenario, operator B may use GCC1
within its own network. Example c) illustrates a scenario where the contract between operators A
and B allows both GCC1 and GCC2 to pass through operator B's network. In this scenario,
operator B cannot use GCC1 or GCC2. Example d) illustrates a scenario where the contract
between operators A and B does not allow GCC1 or GCC2 to pass through operator B's network. In
this scenario, operator B can use both GCC1 and GCC2 within its own network.
6.1.4.1.1 GCC physical characteristics
The OTUk general communication channel 0 (GCC0) shall operate as a single message channel
between OTUk termination points using the OTUk overhead bytes located in row 1, columns 11
and 12 of the OTUk overhead. The bit rate of the GCC0 depends on the rate of the OTUk. For an
OTU1, the GCC0 channel shall operate at 326.723 kbit/s. For an OTU2, the GCC0 channel shall
operate at 1312.405 kbit/s. For an OTU3, the GCC0 channel shall operate at 5271.864 kbit/s.
The ODUk GCC1 shall operate as a single message channel between any two network elements
with access to the ODUk frame structure using the ODU overhead bytes located in row 4,
columns 1 and 2 of the ODUk overhead. The bit rate of the GCC1 depends on the rate of the ODUk.
For an ODU1, the GCC1 channel shall operate at 326.723 kbit/s. For an ODU2, the GCC1 channel
shall operate at 1312.405 kbit/s. For an ODU3, the GCC1 channel shall operate at 5271.864 kbit/s.
The ODUk GCC2 shall operate as a single message channel between any two network elements
with access to the ODUk frame structure using the ODU overhead bytes located in row 4,
columns 3 and 4 of the ODUk overhead. The bit rate of the GCC2 depends on the rate of the ODUk.
For an ODU2, the GCC1 channel shall operate at 326.723 kbit/s. For an ODU2, the GCC2 channel
shall operate at 1312.405 kbit/s. For an ODU3, the GCC2 channel shall operate at 5271.864 kbit/s.
6.1.4.1.2 GCC data link layer protocol
When used for management applications, the data link protocol PPP provides point-to-point
connections between nodes of the underlying transmission network. Mapping of OTN data-link
layer frame into the GCC is specified in [ITU-T G.7712].
6.1.4.1.3 Support of MCN and SCN separation
In some network deployment scenarios it might be desirable to have separation of MCN and SCN,
such as separately enabling/disabling of the MCN and SCN traffic on each DCN interface. This
might include scenarios where the SCN spans across multiple network domains. The following
mechanisms can be used to meet such application requirement.
– GCC1 and GCC2 can be used simultaneously and separately via two parallel independent
instances of the ODUkP/COMMS_A function. For these two instances, one must be
configured as GCC1 (MI_GCCAccess = "GCC1") while the other instance must be
configured as GCC2 (MI_GCCAccess = "GCC2"). The two COMMS_CPs can then be
assigned to the MCN and SCN, respectively.
Rec. ITU-T G.874 (07/2010) 11

COMMS_CP COMMS_CP
(for GCC1) (for GCC2)
ODUkP/ ODUkP/ ODUkP/

COMMS COMMS client
ODUkP_AP ODUkP_AP ODUkP_AP
ODUkP
ODUkP_TCP
G.874(10)_F6-2
Figure 6-2 − COMMS (GCC1 and GCC2) access at ODUkP access point
(Enhancement to Figure 14-70 of [ITU-T G.798])
– GCC1 and GCC2 can be used simultaneously and separately via two cascaded independent
instances of the ODUk/COMMS_AC atomic function. For these two instances, one must be
configured as GCC1 (MI_GCCAccess = "GCC1") while the other instance must be
configured as GCC2 (MI_GCCAccess = "GCC2"). The two COMMS_CPs can then be
assigned to the MCN and SCN, respectively.
COMMS_CP
(for GCC1)
ODUk/COMMS
COMMS_CP
ODUk_CP (for GCC2)
ODUk/COMMS
G.874(10)_F6-3
Figure 6-3 − ODUk_CP expansion for COMMS access for GCC1 and GCC2
(Enhancement to Figure 14-75 of [ITU-T G.798])
– In case where there is limitation in the ODUk layer network deployment such that GCC1
and GCC2 cannot be used separately and simultaneously, it is necessary to have at least two
HO ODUk connections between the two NEs (if possible) such that the GCC of one HO
ODUk connection can be used as MCC and the GCC of the other HO ODUk connection
can be used as SCC.
12 Rec. ITU-T G.874 (07/2010)

– In case where there is limitation in the ODUk layer network deployment such that GCC1
and GCC2 cannot be used separately and simultaneously and it is also not possible to have
two HO ODUk connections between the two NEs, mechanisms such as deep packet
inspection would be needed if the MCC and the SCC are sharing that single GCC. This
would however mean that the MCC/SCC messages need to be analysed beyond OSI
layer 3.
6.1.4.2 General management communications overhead (COMMS OH)
The general management communications overhead (COMMS OH) is defined in [ITU-T G.709].
6.1.4.2.1 COMMS OH physical characteristics
The COMMS OH is a logical element within the OTM overhead signal (OOS). It provides general
management communications between two optical network elements with access to the OOS. As
such, the COMMS OH supports the ECC of the OTN optical supervisory channel (OSC). The OOS
is transported via the OSC.
The specific physical frame structure and coding for the COMMS OH is outside the scope of
[ITU-T G.709] and therefore not standardized.
6.1.4.2.2 COMMS OH data link layer protocol
The adaptation of COMMS OH data link layer into the physical layer is for further study.
6.1.5 Management of DCN
See [ITU-T G.7710] for the generic requirements.
6.1.6 Remote log-in
6.1.7 Relationship between technology domains
6.2 OTN equipment management function

This clause provides an overview of the minimum functions which are required to support
inter-vendor O.NE management including single-ended maintenance of O.NEs within an O.MSN,
or between communicating peer O.NEs across a network interface. Single-ended maintenance is the
ability to access remotely located O.NEs to perform maintenance functions (see [ITU-T G.7710] for
the performance management applications).
It should be noted that the management functions have been categorized according to the
classifications given in [ITU-T X.700].
Protocol-neutral specifications of the management application functions, in terms of managed
objects classes, attributes and message specification, are provided in [ITU-T G.874.1].
The OTN equipment management function (EMF) (see Figure 6-4) provides the means through
which the OTN network element function (NEF) is managed by an internal or external manager. If
a network element (NE) contains an internal manager, this manager will be part of the OTN EMF.
The OTN EMF interacts with the other atomic functions (refer to [ITU-T G.798]) by exchanging
information across the management point (MP) reference points. See [ITU-T G.806] and
[ITU-T G.798] for more information on atomic functions and on MPs. The OTN EMF contains a
number of functions that provide a data reduction mechanism on the information received across the
MP reference points. The outputs of these functions are available to the agent via the network
element resources and management application functions (MAFs) which represent this information
as managed objects.
Rec. ITU-T G.874 (07/2010) 13

Figure 6-4 − Optical equipment management function
Network element resources provide event processing and storage. The MAF processes the
information provided to and by the NE resources. The agent converts this information to
management messages and responds to management messages from the manager by performing the
appropriate operations on the managed objects.
This information to and from the agent is passed across the V reference point to the message
communications function (MCF).
6.3 Information flows over management points (MPs)

The information flows described in this clause are functional. The existence of these information
flows in the equipment will depend on the functionality provided by the O.NE and the options
selected.
The information flow over the MP reference points that arises from anomalies and defects detected
in the atomic functions is described in specific detail for each atomic function in [ITU-T G.798].
Note that these information flows and associated functions apply equally to both the client and
supervisory channel due to the independent nature of these signals. This implies neither that the
supervisory channel shall provide all the functions described nor that [ITU-T G.798] will provide
the details of which functions are available.
The information flow over the MP reference points that arises from provisioning and reporting data
is described in specific details for each atomic function in [ITU-T G.798]. The information listed
under the input column refers to the provisioning data that is passed from the OTN EMF to the
atomic functions. The information listed under the output column refers to the reports passed to the
OTN EMF from the atomic functions.
14 Rec. ITU-T G.874 (07/2010)

7 Fault management
Fault management is a set of functions which enables the detection, isolation and correction of
abnormal operation of the telecommunication network and its environment. It provides facilities for
the performance of the maintenance phases from [ITU-T M.20]. The quality assurance
measurements for fault management include component measurements for reliability, availability
and survivability.
7.1 Fault management applications

See [ITU-T G.7710] for a description of the basic fault management applications.
7.1.1 Supervision
The supervision process describes the way in which the actual occurrence of a disturbance or fault
is analysed for the purpose of providing an appropriate indication of performance and/or detected
fault condition to maintenance personnel. The supervision philosophy is based on the concepts
underlying the functional model of [ITU-T G.805] and [ITU-T G.872] and the alarm reporting
function of [ITU-T X.733].
The five basic supervision categories are related to transmission, quality of service, processing,
equipment and environment. These supervision processes are able to declare fault causes, which
need further validation before the appropriate alarm is reported. See [ITU-T G.7710] for additional
discussion of these categories.
The O.NE shall indicate to the OS when a termination point is no longer able to supervise the signal
(e.g., implementing equipment has a fault or loss of power).
7.1.1.1 Transmission supervision
See [ITU-T G.7710] for a description of transmission supervision.
7.1.1.2 Quality of Service supervision
See [ITU-T G.7710] for a description of quality of service supervision.
7.1.1.3 Processing supervision
See [ITU-T G.7710] for a description of processing supervision.
7.1.1.4 Hardware supervision
See [ITU-T G.7710] for a description of hardware supervision.
7.1.1.5 Environment supervision
See [ITU-T G.7710] for a description of environment supervision.
7.1.2 Validation
See [ITU-T G.7710] for a description of fault cause validation.
7.1.3 Alarm handling
7.1.3.1 Severity assignment
See [ITU-T G.7710] for a description of severity categories.
7.1.3.2 Alarm reporting control
Alarm reporting control (ARC) provides an automatic in-service provisioning capability.
The following ARC states may be specified for a managed entity:
ALM ALarM reporting; alarm reporting is turned on.
Rec. ITU-T G.874 (07/2010) 15

NALM No ALarM reporting; alarm reporting is turned off.
NALM-CD No ALarM reporting, CountDown; this is a sub-state of NALM-QI and performs the
persistence timing countdown function when the managed entity is qualified problem
free.
NALM-NR No ALarM reporting, NotReady; this is a sub-state of NALM-QI and performs a
wait function until the managed entity is qualified problem free.
NALM-QI No ALarM reporting, Qualified Inhibit; alarm reporting is turned off until the
managed entity is qualified problem free for a specified persistence interval.
NALM-TI No ALarM reporting, Timed Inhibit; alarm reporting is turned off for a specified
timed interval.
Alarm reporting may be turned off (using NALM, NALM-TI or NALM-QI) on a per-managed
entity basis to allow sufficient time for customer testing and other maintenance activities in an
"alarm free" state. Once a managed entity is ready, alarm reporting is automatically turned on (to
ALM). The managed entity may be automatically turned on either by using NALM-TI or
NALM-QI and allowing the resource to transition out automatically, or by invoking first the NALM
state from an EMS and, when maintenance activity is done, invoking the ALM state. This later
automation is carried out by the EMS. For further details relating to ARC, see [ITU-T M.3100].
7.1.3.3 Reportable failures
See [ITU-T G.7710] for a description of reportable failures.
7.1.3.4 Alarm reporting
Alarm surveillance is concerned with the detection and reporting of relevant events and conditions,
which occur in the network. In a network, events and conditions detected within the equipment and
incoming signals should be reportable. In addition, a number of events external to the equipment
should also be reportable. Alarms are indications that are automatically generated by an NE as a
result of the declaration of a failure. The OS shall have the ability to define which events and
conditions generate autonomous reports, and which shall be reported on request.
The following alarm-related functions shall be supported:
1) autonomous reporting of alarms;
2) request for reporting of all alarms;
3) reporting of all alarms;
4) allow or inhibit autonomous alarm reporting;
5) reporting on request status of allow or inhibit alarm reporting;
6) control of the termination point mode of termination points;
7) reporting of protection switch events.
7.1.3.4.1 Local reporting
See [ITU-T G.7710] for a description of local reporting.
7.1.3.4.2 TMN reporting
See [ITU-T G.7710] for a description of TMN reporting.
7.2 Fault management functions

Figure 7-1 contains the functional model of fault management inside the OTN EMF. This model is
consistent with the alarm flow functional model, specified in [ITU-T M.3100]. It must be noted that
it does not address configuration aspects relating to fault management, the full ARC functional
16 Rec. ITU-T G.874 (07/2010)

model, nor does it define where all possible event report parameters get assigned. Figure 7-1 is
intended only to illustrate which well-known functions are impacted by ARC, and which are not,
and to provide a generalized alarm flow view.
Fault management
Alarm severity assignment profile
ARC information
UNA Unit alarms
Fault cause Failure Reportable failure Network

element alarms
PRS SEV ARC REP NEA
cZZZ-value fZZZ-value fZZZ-value
rZZZ-value
Management applications function

fZZZ-severity Station alarms
rZZZ-severity STA
fZZZ-value
Atomic functions
fZZZ-severity TEP
fZZZ-arc
Alarm
synchronization
ASY
rZZZ-value
Query
rZZZ-severity LOG Report
TMN alarm event
TAN notifications
Current problem list

CPL
AST Alarm status
Operational state
OPS
NE-RTC
Date and time functions
G.874(10)_F7-1
Figure 7-1 − Fault management within the OTN NEF

7.2.1 Fault cause persistency function – PRS
The defect correlations provide a data reduction mechanism on the fault and performance
monitoring primitives' information presented at the MP reference points.
The fault cause persistency function will provide a persistency check on the fault causes (that are
reported across the MP reference points) before it declares that a fault cause is a failure. In addition
to the transmission failures, hardware failures with signal transfer interruption are also reported at
the input of the fault cause function for further processing. See Figure 7-2.
Symbol
cZZZ-value MP fZZZ-value
(Fault cause) PRS (Failure)
NE-RTC
G.874(10)_F7-2
Figure 7-2 − Fault cause persistency function
Rec. ITU-T G.874 (07/2010) 17

Inputs and outputs
Table 7-1 − Inputs/outputs for the fault cause persistency function

Atomic functions Input (fault cause) Output (failure)
OTSn_TT_Sk cTIM fTIM
cBDI fBDI
cBDI-O fBDI-O
cBDI-P fBDI-P
cLOS-O fLOS-O
cLOS-P fLOS-P
cLOS fLOS
OMSn_TT_Sk cBDI fBDI
cBDI-O fBDI-O
cBDI-P fBDI-P
cSSF fSSF
cSSF-O fSSF-O
cSSF-P fSSF-P
cLOS-P fLOS-P
OMSnP_TT_Sk cSSF fSSF
cSSF-O fSSF-O
cSSF-P fSSF-P
OPSn_TT_Sk cLOS-P fLOS-P
OPSMnk_TT_Sk cLOS fLOS
cLOL fLOL
OPSM/OTUk-a_A_Sk cLOS fLOS
cLOM fLOM
OPSM/OTUk-b_A_Sk cLOS fLOS
cLOM fLOM
OCh_TT_Sk cLOS-P fLOS-P
cSSF fSSF
cSSF-P fSSF-P
cSSF-O fSSF-O
cOCI fOCI
OChr_TT_Sk cLOS fLOS
cSSF-P fSSF-P
OCh/OTUk-a_A_Sk cLOF fLOF
cLOM fLOM
OCh/OTUk-b_A_Sk cLOF fLOF
cLOM fLOM
OCh/OTUk-v_A_Sk cLOF fLOF
cLOM fLOM
OCh/OTUkV_A_Sk cLOF fLOF
cLOM (multiframe OTUkV only) fLOM
OCh/RSn_A_Sk cLOF fLOF
OTUk_TT_Sk cTIM fTIM
cDEG fDEG
cBDI fBDI
cSSF fSSF
18 Rec. ITU-T G.874 (07/2010)

OTUkV_TT_Sk cTIM fTIM
cDEG fDEG
cBDI fBDI
cSSF fSSF
OTUkV/ODUk_A_Sk (If loss of cLOA fLOA
alignment supervision is performed)
ODUk_C cFOP-PM fFOP-PM
cFOP-NR fFOP-NR
ODUkP_TT_Sk cOCI fOCI
cTIM fTIM
cDEG fDEG
cBDI fBDI
cSSF fSSF
cLCK fLCK
ODUkP/CBRx_A_Sk cPLM fPLM
cCSF fCSF
ODUkP/VP_A_Sk cPLM fPLM
cLCD fLCD
ODUkP/NULL_A_Sk cPLM fPLM
ODUkP/PRBS_A_Sk cPLM fPLM
cLSS fLSS
ODUkP/RSn_A_Sk cPLM fPLM
cLOF fLOF
ODUkP/ODU[i]j_A_Sk cPLM fPLM
cMSIM[n+m] fMSIM[n+m]
cLOFLOM fLOFLOM
ODUkP/ODUj-21_A_Sk cPLM fPLM
cMSIM[i] fMSIM[i]
cLOFLOM[i] fLOFLOM[i]
ODUkT_TT_Sk cOCI fOCI
cTIM fTIM
cDEG fDEG
cBDI fBDI
cSSF fSSF
cLCK fLCK
cLTC fLTC
ODUkTm_TT_Sk cOCI fOCI
cTIM fTIM
cDEG fDEG
cBDI fBDI
cSSF fSSF
cLCK fLCK
cLTC fLTC
ODUkP-Xv/ODUkP-X-L_A_Sk cPLM[1..XMR] fPLM[1..XMR]
ODUkP-X-L/CBRx_A_Sk cVcPLM fVcPLM
Rec. ITU-T G.874 (07/2010) 19

ODUkP-X-L/RSn_A_Sk cVcPLM fVcPLM
cLOF fLOF
ODUkP-X-L/VP_A_Sk cVcPLM fVcPLM
cLCD fLCD
ODUkP-X-L/NULL_A_Sk cVcPLM fVcPLM
ODUkP-X-L/PRBS_A_Sk cVcPLM fVcPLM
cLSS fLSS
OSx_TT_Sk cLOS fLOS
Process
The equipment management function within the network element performs a persistency check on
the fault causes before it declares a fault cause a failure.
A transmission failure (fXXX) shall be declared if the fault cause persists continuously for
2.5 ± 0.5 s. The failure shall be cleared if the fault cause is absent continuously for 10 ± 0.5 s.
Transmission failures associated with the three types (termination, adaptation and connection) of
transport atomic functions are listed in Table 7-1.
The failure declaration and clearing shall be time stamped. The time stamp shall indicate the time at
which the fault cause is activated at the input of the fault cause persistency (i.e., defect-to-failure
integration) function, and the time at which the fault cause is deactivated at the input of the fault
cause persistency function.
7.2.2 Severity assignment function – SEV
See [ITU-T G.7710] for a description of the severity assignment function.
7.2.3 Alarm reporting control function – ARC
The alarm reporting-control (ARC) function allows a management system to control the alarm
reporting on a per-managed entity basis as defined in [ITU-T M.3100].
The alarms that can be controlled with this function are defined for each atomic function in
[ITU-T G.798].
The ARC states that may be specified for a managed entity are defined in clause 7.1.3.2. For O.NE:
– The ALM state is required for all managed entities that can detect alarms.
– In addition, at least one of the states: NALM, NALM-TI or NALM-QI must be supported.
– If NALM-QI is supported, then NALM-NR is required and NALM-CD is optional.
In Table 7-2 below, for each managed entity a subset of the plausible failures (defined in Table 7-1)
are selected as qualified problems. These qualified problems are recommended as they are deemed
essential to the operability of the subject managed entity. Note that for each managed entity, one or
more of the qualified problems could then be further selected by the management system to be
included in the ARC list (see clause 7.2.3 of [ITU-T G.7710]) for controlling the reporting of alarm
for the entity. When an entity is put in the ARC state of NALM-QI, alarm reporting for the entity is
turned off until the managed entity is free of all the failures specified in the ARC list.
Default ARC state is also specified for each managed entity. If the ARC function is supported by
the O.NE and an ARC state is not explicitly provisioned from the management system for the
managed entity, then the default ARC specified in Table 7-2 should be in effect.
20 Rec. ITU-T G.874 (07/2010)

Table 7-2 − ARC specifications for the OTN
Qualified QoS Default ARC state
Atomic function
problems reporting value constraints
OTSn_TT_Sk fTIM FFS ALM
fBDI
fBDI-P
fLOS-P
fLOS
OMSn_TT_Sk fBDI FFS ALM
fBDI-P
fSSF
fSSF-P
fLOS-P
OMSnP_TT_Sk fSSF FFS ALM
fSSF-P
OPSn_TT_Sk fLOS-P FFS ALM
OPSMnk_TT_Sk fLOS FFS ALM
fLOL
OPSM/OTUk-a_A_Sk fLOF FFS ALM
fLOM
OPSM/OTUk-b_A_Sk fLOF FFS ALM
fLOM
OCh_TT_Sk fLOS-P FFS ALM
fSSF
fSSF-P
fOCI
OChr_TT_Sk fLOS FFS ALM
fSSF-P
OCh/OTUk-a_A_Sk fLOF FFS ALM
fLOM
OCh/OTUk-b_A_Sk fLOF FFS ALM
fLOM
OCh/OTUkV_A_Sk fLOF FFS ALM
fLOM
OCh/RSn_A_Sk fLOF FFS ALM
OTUk_TT_Sk fTIM FFS ALM
fDEG
fBDI
fSSF
OTUkV_TT_Sk fTIM FFS ALM
fDEG
fBDI
fSSF
OTUkV/ODUk_A_Sk fLOA FFS ALM
ODUk_C fFOP-PM FFS ALM
fFOP-NR
Rec. ITU-T G.874 (07/2010) 21

Table 7-2 − ARC specifications for the OTN
Qualified QoS Default ARC state
Atomic function
problems reporting value constraints
ODUkP_TT_Sk fOCI FFS ALM
fTIM
fDEG
fBDI
fSSF
fLCK
ODUkP/CBRx_A_Sk fPLM FFS ALM
fCSF FFS FFS
ODUkP/VP_A_Sk fPLM FFS ALM
fLCD
ODUkP/NULL_A_Sk fPLM FFS ALM
ODUkP/PRBS_A_Sk fPLM FFS ALM
fLSS
ODUkP/RSn_A_Sk fPLM FFS ALM
fLOF
ODUkP/ODU[i]j_A_Sk fPLM FFS ALM
fMSIM[n+m]
fLOFLOM
ODUkT_TT_Sk fOCI FFS ALM
fTIM
fDEG
fBDI
fSSF
fLCK
fLTC
ODUkTm_TT_Sk fOCI FFS ALM
fTIM
fDEG
fBDI
fSSF
fLCK
fLTC
ODUkP-Xv/ODUkP-X-L_A_Sk fPLM[1..XMR] FFS ALM
ODUkP-X-L/CBRx_A_Sk fVcPLM FFS ALM
ODUkP-X-L/RSn_A_Sk fVcPLM FFS ALM
fLOF
ODUkP-X-L/VP_A_Sk fVcPLM FFS ALM
fLCD
ODUkP-X-L/NULL_A_Sk fVcPLM FFS ALM
ODUkP-X-L/PRBS_A_Sk fVcPLM FFS ALM
fLSS
OSx_TT_Sk fLOS FFS ALM
7.2.4 Reportable failure function – REP

See [ITU-T G.7710] for a description of the reportable failure function.
22 Rec. ITU-T G.874 (07/2010)

7.2.5 Unit alarm function – UNA
See [ITU-T G.7710] for a description of the unit alarm function.
7.2.6 Network element alarm function – NEA
See [ITU-T G.7710] for a description of the network alarm function.
7.2.7 Station alarm function – STA
See [ITU-T G.7710] for a description of the station alarm function.
7.2.8 TMN event pre-processing function – TEP
See [ITU-T G.7710] for a description of the TMN event pre-processing alarm function.
7.2.9 Alarm synchronization function – ASY
See [ITU-T G.7710] for a description of the alarm synchronization function.
7.2.10 Logging function – LOG
Alarm history management is concerned with the recording of alarms. Historical data shall be
stored in registers in the NE. Each register contains all the parameters of an alarm message.
Registers shall be readable on demand or periodically. The OS can define the operating mode of the
registers as wrapping, or stop, when full. The OS may also flush the registers or stop recording at
any time.
NOTE – Wrapping is the deletion of the earliest record to allow a new record when a register is full.
Flushing is the removal of all records in the register. See [ITU-T X.735] for additional details.
See [ITU-T G.7710] for a description of the logging function.
7.2.11 TMN alarm event notification function – TAN
See [ITU-T G.7710] for a description of the TMN alarm event notification function.
7.2.12 Current problem list function – CPL
See [ITU-T G.7710] for a description of the current problem list function.
7.2.13 Alarm status function – AST
See [ITU-T G.7710] for a description of the alarm status function.
7.2.14 Operational state function – OPS
See [ITU-T G.7710] for a description of the operational state function.
Table 7-3 lists the failures that could influence the operational state of the related objects.
Table 7-3 − Input and output signals of the operational state

function for OTN
Operational state output
Failure input
Atomic function (enabled/disabled) of the
(fZZZ-value)
trail object class
OTSn_TT_Sk fTIM Enabled
fBDI Enabled
fBDI-P Enabled
fLOS-P Disabled
fLOS Disabled
Rec. ITU-T G.874 (07/2010) 23

function for OTN
Failure input
(fZZZ-value)
trail object class
OMSn_TT_Sk fBDI Enabled
fBDI-P Enabled
fSSF Enabled
fSSF-P Enabled
fLOS-P Disabled
OMSnP_TT_Sk fSSF Enabled
fSSF-P Enabled
OPSn_TT_Sk fLOS-P Disabled
OPSMnk_TT_Sk fLOS Disabled
fLOL Disabled
OPSM/OTUk-a_A_Sk fLOF Disabled
fLOM Disabled
OPSM/OTUk-b_A_Sk fLOF Disabled
fLOM Disabled
OCh_TT_Sk fLOS-P Disabled
fSSF Enabled
fSSF-P Enabled
fOCI Enabled
OChr_TT_Sk fLOS Disabled
fSSF-P Enabled
OCh/OTUk-a_A_Sk fLOF Disabled
fLOM Disabled
OCh/OTUk-b_A_Sk fLOF Disabled
fLOM Disabled
OCh/OTUkV_A_Sk fLOF Disabled
fLOM Disabled
OCh/RSn_A_Sk fLOF Disabled
OTUk_TT_Sk fTIM Enabled
fDEG Enabled
fBDI Enabled
fSSF Enabled
OTUkV_TT_Sk fTIM Enabled
fDEG Enabled
fBDI Enabled
fSSF Enabled
OTUkV/ODUk_A_Sk fLOA Disabled
ODUk_C fFOP-PM Disabled
fFOP-NR Disabled
24 Rec. ITU-T G.874 (07/2010)

function for OTN
Failure input
(fZZZ-value)
trail object class
ODUkP_TT_Sk fOCI Enabled
fTIM Enabled
fDEG Enabled
fBDI Enabled
fSSF Enabled
fLCK Enabled
ODUkP/CBRx_A_Sk fPLM FFS
fCSF FFS
ODUkP/VP_A_Sk fPLM FFS
fLCD Disabled
ODUkP/NULL_A_Sk fPLM FFS
ODUkP/PRBS_A_Sk fPLM FFS
fLSS FFS
ODUkP/RSn_A_Sk fPLM FFS
fLOF Disabled
ODUkP/ODU[i]j_A_Sk fPLM FFS
fMSIM[n+m] FFS
fLOFLOM Disabled
ODUkT_TT_Sk fOCI Enabled
fTIM Enabled
fDEG Enabled
fBDI Enabled
fSSF Enabled
fLCK Enabled
fLTC FFS
ODUkTm_TT_Sk fOCI Enabled
fTIM Enabled
fDEG Enabled
fBDI Enabled
fSSF Enabled
fLCK Enabled
fLTC FFS
ODUkP-Xv/ODUkP-X-L_A_Sk fPLM[1..XMR] FFS
ODUkP-X-L/CBRx_A_Sk fVcPLM FFS
ODUkP-X-L/RSn_A_Sk fVcPLM FFS
fLOF Disabled
ODUkP-X-L/VP_A_Sk fVcPLM FFS
fLCD Disabled
ODUkP-X-L/NULL_A_Sk fVcPLM FFS
ODUkP-X-L/PRBS_A_Sk fVcPLM FFS
fLSS FFS
OSx_TT_Sk fLOS Disabled
Rec. ITU-T G.874 (07/2010) 25

7.2.15 External events
For further study.
8 Configuration management
See [ITU-T G.7710] for the generic requirements for configuration management. OTN-specific
specifications, if needed, are explicitly described.
8.1 Hardware
See [ITU-T G.7710] for a description of hardware management.
8.2 Software
See [ITU-T G.7710] for a description of software management.
8.3 Protection switching

See [ITU-T G.7710] for a description of protection switching management.
8.4 Trail termination

See [ITU-T G.7710] for a description of trail termination management.
This function allows a user to provision and monitor the operation of the OTN trail termination
process.
A trail trace identifier (TTI) at the OTS layer is useful to ensure proper fibre connection between
network elements, in particular in meshed network topology with optical cross connects that have
several line input ports and several line output ports.
TTIs are also a means for the OS to deduce the network topology at OTS layer first, and then at
OMS and OCh level. Specifically, the OS gets the list of source and sink TTIs of all network
elements and can automatically deduce the trails at the OTS layer by a comparison of the expected
TTIs of the sink objects and the TTIs sent from the source objects. Then, as there is only one
instance of an OMS connection point and one instance of an OMS TTP, the OS can deduce
automatically the topology at the OMS layer. A similar method may be applied at the OCh level
from the list of existing ochCTP (which are named by omsTTP).
The TTIs received are used at the network element level to detect wrong fibre connection and
generate an OTS trail trace identifier mismatch alarm if the accepted value is different from the
expected value.
The trail trace identifier at the OCh layer is necessary to check that the signal received by a sink
originates from the intended source. To be able to localize the cross connection responsible for a
trail trace identifier mismatch, the expected and the received OCh TTIs are needed at the sink.
The received OCh TTI is used at the network element level to detect wrong OCh connections and to
generate an OCH trail trace identifier mismatch alarm.
The MI signals listed in the following table are communicated between the EMF and the OTN trail
termination process across the management point within the O.NE.
26 Rec. ITU-T G.874 (07/2010)

Table 8-1 − Trace identifier-related provisioning and reporting
MI signal Value range Default value
OTSn_TT_So Provisioning
OTSn_TT_So_MI_TxTI According to [ITU-T G.709] Not applicable
OTSn_TT_So_MI_APRCntrl Enable, Disable Enable
OTSn_TT_Sk Provisioning
OTSn_TT_Sk_MI_ExSAPI According to [ITU-T G.709] Not applicable
OTSn_TT_Sk_MI_ExDAPI According to [ITU-T G.709] Not applicable
OTSn_TT_Sk_MI_GetAcTI According to [ITU-T G.798] Not applicable
OTSn_TT_Sk_MI_TIMDetMo According to [ITU-T G.798] FFS
OTSn_TT_Sk_MI_TIMActDis True, false True
OTSn_TT_Sk_MI_1second According to [ITU-T G.798] Not applicable
OMSn_TT_Sk Provisioning
OMSn_TT_Sk_MI_1second According to [ITU-T G.798] Not applicable
OTUk_TT_So Provisioning
OTUk_TT_So_MI_TxTI According to [ITU-T G.709] Not applicable
OTUk_TT_Sk Provisioning
OTUk_TT_Sk_MI_ExSAPI According to [ITU-T G.709] Not applicable
OTUk_TT_Sk_MI_ExDAPI According to [ITU-T G.709] Not applicable
OTUk_TT_Sk_MI_GetAcTI According to [ITU-T G.798] Not applicable
OTUk_TT_Sk_MI_TIMDetMo According to [ITU-T G.798] FFS
OTUk_TT_Sk_MI_TIMActDis True, false True
OTUk_TT_Sk_MI_DEGThr 0%..100%; see Table 7-1 of 30%
[ITU-T G.806]
OTUk_TT_Sk_MI_DEGM 2-10; see Table 7-1 of 10
[ITU-T G.806]
OTUk_TT_Sk_MI_1second According to [ITU-T G.798] Not applicable
OTUkV_TT_So Provisioning
OTUkV_TT_So_MI_TxTI According to [ITU-T G.709] Not applicable
OTUkV_TT_Sk Provisioning
OTUkV_TT_Sk_MI_ExSAPI According to [ITU-T G.709] Not applicable
OTUkV_TT_Sk_MI_ExDAPI According to [ITU-T G.709] Not applicable
OTUkV_TT_Sk_MI_GetAcTI According to [ITU-T G.798] Not applicable
OTUkV_TT_Sk_MI_TIMDetMo According to [ITU-T G.798] FFS
OTUkV_TT_Sk_MI_TIMActDis Enabled, disabled Disabled
OTUkV_TT_Sk_MI_DEGThr 0%..100%; see Table 7-1 of 30%
[ITU-T G.806]
OTUkV_TT_Sk_MI_DEGM 2-10; see Table 7-1 of 10
[ITU-T G.806]
OTUkV_TT_Sk_MI_1second According to [ITU-T G.798] Not applicable
Rec. ITU-T G.874 (07/2010) 27

ODUkP_TT_So Provisioning
ODUkP_TT_So_MI_TxTI According to [ITU-T G.709] Not applicable
ODUkP_TT_So_MI_DM_Source According to [ITU-T G.709] Not applicable
ODUkP_TT_So_MI_DMValue According to [ITU-T G.709] Not applicable
ODUkP_TT_Sk Provisioning
ODUkP_TT_Sk_MI_ExSAPI According to [ITU-T G.709] Not applicable
ODUkP_TT_Sk_MI_ExDAPI According to [ITU-T G.709] Not applicable
ODUkP_TT_Sk_MI_GetAcTI According to [ITU-T G.798] Not applicable
ODUkP_TT_Sk_MI_TIMDetMo According to [ITU-T G.798] FFS
ODUkP_TT_Sk_MI_ TIMActDis Enabled, disabled Disabled
ODUkP_TT_Sk_MI_DM_Source According to [ITU-T G.709] Not applicable
ODUkP_TT_Sk_MI_DMValue According to [ITU-T G.709] Not applicable
ODUkT_TT_So Provisioning
ODUkT_TT_So_MI_TxTI According to [ITU-T G.709] Not applicable
ODUkT_TT_So_MI_DM_Source According to [ITU-T G.709] Not applicable
ODUkT_TT_So_MI_DMValue According to [ITU-T G.709] Not applicable
ODUkT_TT_Sk Provisioning
ODUkT_TT_Sk_MI_ExSAPI According to [ITU-T G.709] Not applicable
ODUkT_TT_Sk_MI_ExDAPI According to [ITU-T G.709] Not applicable
ODUkT_TT_Sk_MI_GetAcTI According to [ITU-T G.798] Not applicable
ODUkT_TT_Sk_MI_TIMDectMo According to [ITU-T G.798] FFS
ODUkT_TT_Sk_MI_TIMActDis Enabled, disabled Disabled
ODUkT_TT_Sk_MI_DEGThr 0%..100%; See Table 7-1 of 30%
[ITU-T G.806]
ODUkT_TT_Sk_MI_DEGM 2-10; see Table 7-1 of 10
[ITU-T G.806]
ODUkT_TT_Sk_MI_1second According to [ITU-T G.798] Not applicable
ODUkT_TT_Sk_MI_DM_Source According to [ITU-T G.709] Not applicable
ODUkT_TT_Sk_MI_DMValue According to [ITU-T G.709] Not applicable
ODUkT_TT_Sk Reporting
ODUkT_TT_Sk_MI_AcTI According to [ITU-T G.709] Not applicable
ODUkTm_TT_Sk Provisioning
ODUkTm_TT_Sk_MI_Level 1..6 Not applicable
ODUkTm_TT_Sk_MI_ExSAPI According to [ITU-T G.709] Not applicable
ODUkTm_TT_Sk_MI_ExDAPI According to [ITU-T G.709] Not applicable
ODUkTm_TT_Sk_MI_GetAcTI According to [ITU-T G.798] Not applicable
ODUkTm_TT_Sk_MI_TIMDectMo According to [ITU-T G.798] FFS
ODUkTm_TT_Sk_MI_TIMActDis Enabled, disabled Disabled
28 Rec. ITU-T G.874 (07/2010)

ODUkTm_TT_Sk_MI_DEGThr 0%..100%; see Table 7-1 of 30%
[ITU-T G.806]
ODUkTm_TT_Sk_MI_DEGM 2-10; see Table 7-1 of 10
[ITU-T G.806]
ODUkTm_TT_Sk_MI_1second According to [ITU-T G.798] Not applicable
ODUkTm_TT_Sk Reporting
ODUkTm_TT_Sk_MI_AcTI According to [ITU-T G.709] Not applicable
OSx_TT_So Provisioning
OSx_TT_So_MI_APRCntrl (Notes 1 and 2) Enable, disable Enable
NOTE 1 – If APR is required.
NOTE 2 – The APRCntrl commands depend on the specific APR process.
The EMF shall support the following functions:
– provisioning the trail termination management information;
– retrieving the trail termination management information;
– notifying the changes of the trail termination management information;
– receiving the monitored trail termination management information.
For the management of the connectivity at OTS layer, the following trail trace identifier attributes
are recommended:
1) otsTTIsent attribute in every otsTTPsource (get – replace);
2) otsTTIexpected attribute in every otsTTPsink (get – replace);
3) otsTTIreceived attribute in every otsTTPsink (get – replace).
For the management of the connectivity at OCH layer, the following trail trace identifier attributes
are recommended:
1) ochTTIsent attribute in every ochTTPsource (get – replace);
2) ochTTIexpected attribute in every ochTTPsink and ochCTPsink (get – replace);
3) ochTTIreceived attribute in every ochTTPsink and ochCTPsink (get only).
8.5 Adaptation
See [ITU-T G.7710] for a description of adaptation management.
An access point that has multiple adaptation functions connected to it, thereby allowing different
clients to be transported via the server signal, requires a mechanism for the selection of the active
client.
The adaptation function allows a user to provision and monitor the operation of the OTN adaptation
processes.
The activation/deactivation of adaptation functions is via MI_Active signals.
Both OMS/OCh_A and OCh/Application_A will report on request from the OTN EMF the value of
the received and accepted payload type indication signal via the MI_AcPTI.
Rec. ITU-T G.874 (07/2010) 29

OCh_AP AP Id = API
OCh_TT TCP Id = AP Id
OCh_TCP
OCh_CP
CP Id = AP Id/CN
OMS_AP
TCP Id = AP Id
OMS_TCP
OTS_AP
TCP Id = AP Id
OTS_TCP
T1546210-02
Figure 8-1 − CP and TCP identification scheme
The MI signals listed in Table 8-2 are communicated between the EMF and the adaptation
processes across the management point within the OTN NE.
Table 8-2 − Provisioning and reporting for adaptation functions

OPSM/OTUk-a_A_So Provisioning
OPSM/OTUk-a_A_So_MI_Active True, false False
OPSM/OTUk-b_A_So Provisioning
OPSM/OTUk-b_A_So_MI_Active True, false False
OPSM/OTUk-a_A_Sk Provisioning
OPSM/OTUk-a_A_Sk_MI_FECEn (not for OTU4) True, false True
OPSM/OTUk-a_A_Sk_MI_Active True, false False
OPSM/OTUk-a_A_Sk_MI_1second According to Not applicable
[ITU-T G.798]
OPSM/OTUk-b_A_Sk Provisioning
OPSM/OTUk-b_A_Sk_MI_Active True, false False
OCh/OTUk-a_A_So Provisioning
OCh/OTUk-a_A_So_MI_Active True, false False
OCh/OTUk-b_A_So Provisioning
OCh/OTUk-b_A_So_MI_Active True, false False
OCh/OTUk-a_A_Sk Provisioning
OCh/OTUk-a_A_Sk_MI_FECEn True, false True
OCh/OTUk-a_A_Sk_MI_Active True, false False
OCh/OTUk-a_A_Sk_MI_1second According to Not applicable
[ITU-T G.798]
30 Rec. ITU-T G.874 (07/2010)

OCh/OTUk-b_A_Sk Provisioning
OCh/OTUk-b_A_Sk_MI_Active True, false False
OCh/OTUk-v_A_So Provisioning
OCh/OTUk-v_A_So_MI_Active True, false False
OCh/OTUk-v_A_Sk Provisioning
OCh/OTUk-v_A_Sk_MI_FECEn True, false True
OCh/OTUk-v_A_Sk_MI_Active True, false False
OCh/OTUk-v_A_Sk_MI_1second According to Not applicable
[ITU-T G.798]
OCh/OTUkV_A_So Provisioning
OCh/OTUkV_A_So_MI_Active True, false False
OCh/OTUkV_A_Sk Provisioning
OCh/OTUkV_A_Sk_MI_Active True, false False
OCh/OTUkV_A_Sk_MI_1second (Note 1) According to Not applicable
[ITU-T G.798]
OCh/CBRx_A_So Provisioning
OCh/CBRx_A_So_MI_Active True, false False
OCh/CBRx_A_Sk Provisioning
OCh/CBRx_A_Sk_MI_Active True, false False
OCh/RSn_A_So_Provisioning
OCh/RSn_A_So_MI_Active True, false False
OCh/RSn_A_Sk_Provisioning
OCh/RSn_A_Sk_MI_Active True, false False
OTUk/ODUk_A_So_Provisioning
OTUk/ODUk_A_So_MI_AdminState LOCKED, Not Not LOCKED
LOCKED
OTUk/ODUk_A_Sk_Provisioning
OTUk/ODUk_A_Sk_MI_AdminState LOCKED, Not Not LOCKED
LOCKED
OTUkV/ODUk_A_So_Provisioning
OTUkV/ODUk_A_So_MI_AdminState LOCKED, Not Not LOCKED
LOCKED
OTUkV/ODUk_A_Sk_Provisioning
OTUkV/ODUk_A_Sk_MI_AdminState LOCKED, Not Not LOCKED
LOCKED
OTUk/COMMS_A_So_Provisioning
OTUk/COMMS_A_So_MI_Active True, false False
OTUk/COMMS_A_Sk_Provisioning
OTUk/COMMS_A_Sk_MI_Active True, false False
Rec. ITU-T G.874 (07/2010) 31

OTUkV/COMMS_A_So_Provisioning
OTUkV/COMMS_A_So_MI_Active True, false False
OTUkV/COMMS_A_Sk_Provisioning
OTUkV/COMMS_A_Sk_MI_Active True, false False
ODUkP/CBRx-a_A_So_Provisioning
ODUkP/CBRx-a_A_So_MI_Active, k=1, 2, 2e, 3; (Note 2) True, false False
ODUkP/CBRx-b_A_So_Provisioning
ODUkP/CBRx-b_A_So_MI_Active, k=1, 2, 2e, 3; (Note 2) True, false False
ODUkP/CBRx_A_Sk_Provisioning
ODUkP/CBRx_A_Sk_MI_Active, k=1, 2, 2e, 3; (Note 2) True, false False
ODUkP/CBRx_A_Sk Reporting
ODUkP/CBRx_A_Sk_MI_AcPT, k=1, 2, 2e, 3; (Note 2) According to Not applicable
[ITU-T G.709]
ODUkP/CBRx-g_A_So Provisioning
ODUkP/CBRx_A_So_MI_Active, k=1, 2, 2e, 3; (Note 2) True, false False
ODUkP/CBRx-g _A_Sk Provisioning
ODUkP/CBRx_A_Sk_MI_Active, k=1, 2, 2e, 3; (Note 2) True, false False
ODUkP/CBRx_A_Sk_MI_Enable_PCSL_Section_Mon True, false False
ODUkP/CBRx-g _A_Sk Reporting
ODUkP/CBRx_A_Sk_MI_AcPT, k=1, 2, 2e, 3; (Note 2) According to Not applicable
[ITU-T G.709]
ODU0P/CBRx_A_So Provisioning
ODU0P/CBRx_A_So_MI_Active, k=0; (Note 3) True, false False
ODU0P/CBRx_A_Sk Provisioning
ODU0P/CBRx_A_Sk_MI_Active, k=0; (Note 3) True, false False
ODU0P/CBRx_A_Sk Reporting
ODU0P/CBRx_A_Sk_MI_AcPT, k=0; (Note 3) According to Not applicable
[ITU-T G.709]
ODUkP/VP_A_So Provisioning
ODUkP/VP_A_So_MI_Active, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_So_MI_CellDiscardActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_So_MI_TPusgActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_So_MI_GFCActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_So_MI_VPI-KActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk Provisioning
ODUkP/VP_A_Sk_MI_Active, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk_MI_CellDiscardActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk_MI_TPusgActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk_MI_VPIrange, k=1, 2, 2e, 3 0..4095 Not applicable
32 Rec. ITU-T G.874 (07/2010)

ODUkP/VP_A_Sk_MI_HECactive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk_MI_GFCactive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk_MI_DTDLuseEnabled, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk_MI_VPI-KActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk_MI_VPIK_SAISActive, k=1, 2, 2e, 3 True, false False
ODUkP/VP_A_Sk Reporting
ODUkP/VP_A_Sk_MI_AcPT, k=1, 2, 2e, 3 According to Not applicable
[ITU-T G.709]
ODUkP/NULL_A_So Provisioning
ODUkP/NULL_A_So_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUkP/NULL_A_So_MI_Nominal_Bitrate_and_Tolerance According to Not applicable
[ITU-T G.709]
ODUkP/NULL_A_Sk_Provisioning
ODUkP/NULL_A_Sk_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUkP/NULL_A_Sk Reporting
ODUkP/NULL_A_Sk_MI_AcPT, k=0, 1, 2, 2e, 3, 4, flex According to Not applicable
[ITU-T G.709]
ODUkP/PRBS _A_So Provisioning
ODUkP/PRBS _A_So_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUkP/PRBS_A_So_MI_Nominal_Bitrate_and_Tolerance According to Not applicable
[ITU-T G.709]
ODUkP/PRBS_A_Sk Provisioning
ODUkP/PRBS_A_Sk_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUkP/PRBS_A_Sk Reporting
ODUkP/PRBS_A_Sk_MI_AcPT, k=0, 1, 2, 2e, 3, 4, flex According to Not applicable
[ITU-T G.709]
ODUkP/RSn-a_A_So Provisioning
ODUkP/RSn-a_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP/RSn-b_A_So Provisioning
ODUkP/RSn-b_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP/RSn_A_Sk Provisioning
ODUkP/RSn_A_Sk_MI_Active, k=1, 2, 3 True, false False
ODUkP/RSn_A_Sk Reporting
ODUkP/RSn_A_Sk_MI_AcPT, k=1, 2, 3 According to Not applicable
[ITU-T G.709]
ODUkP/ODU[i]j_A_So Provisioning
ODUkP/ODU[i]j_A_So_MI_Active True, false False
ODUkP/ODU[i]j_A_So_MI_AdminState[n+m] LOCKED, Not Not LOCKED
LOCKED
Rec. ITU-T G.874 (07/2010) 33

ODU3P/ODU12_A_So Provisioning
ODU3P/ODU12_A_So_MI_TxMSI According to Not applicable
Table 14-30 of
[ITU-T G.798]
ODUkP/ODU[i]j_A_Sk Provisioning
ODUkP/ODU[i]j_A_Sk_MI_Active True, false False
ODUkP/ODU[i]j_A_Sk_MI_AdminState[n+m] LOCKED, Not Not LOCKED
LOCKED
ODU3P/ODU12_A_Sk Provisioning
ODU3P/ODU12_A_Sk_MI_ExMSI[n+m] According to Not applicable
Table 14-32 of
[ITU-T G.798]
ODUkP/ODU[i]j_A_Sk Reporting
ODUkP/ODU[i]j_A_Sk_MI_AcPT According to Not applicable
[ITU-T G.709]
ODUkP/ODU[i]j_A_Sk_MI_AcMSI[n+m] According to Not applicable
[ITU-T G.709]
ODUkP/ODUj-21_A_So Provisioning
ODUkP/ODUj-21_A_So_MI_Active True, false False
ODUkP/ODUj-21_A_So_MI_TxMSI According to Not applicable
Table 14-33 of
[ITU-T G.798]
ODUkP/ODUj-21_A_So_MI_ AcPT According to Not applicable
[ITU-T G.709]
ODUkP/ODUj-21_A_Sk Provisioning
ODUkP/ODUj-21_A_Sk_MI_Active True, false False
ODUkP/ODUj-21_A_Sk_MI_TxMSI According to Not applicable
Table 14-33 of
[ITU-T G.798]
ODUkP/ODUj-21_A_Sk Reporting
ODUkP/ODUj-21_A_Sk_MI_AcPT According to Not applicable
[ITU-T G.709]
ODUkP/ODUj-21_A_Sk_MI_AcMSI According to Not applicable
[ITU-T G.709]
ODUkP/COMMS_A_So Provisioning
ODUkP/COMMS_A_So_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUkP/COMMS_A_So_MI_GCCAccess, k=0, 1, 2, 2e, 3, 4, GCC1, GCC2, Not applicable
flex GCC1+GCC2
ODUkP/COMMS_A_Sk Provisioning
ODUkP/COMMS_A_Sk_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUkP/COMMS_A_Sk_MI_GCCAccess, k=0, 1, 2, 2e, 3, 4, GCC1, GCC2, Not applicable
flex GCC1+GCC2
34 Rec. ITU-T G.874 (07/2010)

ODUk/COMMS_AC_So Provisioning
ODUk/COMMS_AC_So_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUk/COMMS_AC_So_MI_GCCAccess, k=0, 1, 2, 2e, 3, 4, GCC1, GCC2, Not applicable
flex GCC1+GCC2
ODUk/COMMS_AC_Sk Provisioning
ODUk/COMMS_AC_Sk_MI_Active, k=0, 1, 2, 2e, 3, 4, flex True, false False
ODUk/COMMS_AC_Sk_MI_GCCAccess, k=0, 1, 2, 2e, 3, 4, GCC1, GCC2, Not applicable
flex GCC1+GCC2
ODUk/COMMS_AC_Sk_MI_GCCCont, k=0, 1, 2, 2e, 3, 4, True, false True
flex
ODUkT/ODUk_A_So Provisioning
ODUkT/ODUk_A_So_MI_AdminState, k=0, 1, 2, 2e, 3, 4, LOCKED, Not Not LOCKED
flex LOCKED
ODUkT/ODUk_A_Sk Provisioning
ODUkT/ODUk_A_Sk_MI_AdminState, k=0, 1, 2, 2e, 3, 4, LOCKED, Not Not LOCKED
flex LOCKED
ODUkP-Xv/ODUkP-X-L_A_So Provisioning
ODUkP-Xv/ODUkP-X-L_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP-Xv/ODUkP-X-L_A_Sk Reporting
ODUkP-Xv/ODUkP-X-L_A_Sk_MI_AcPT[1..XMR] , k=1, 2, According to Not applicable
3 [ITU-T G.709]
ODUkP-Xv/ODUkP-X-L_A_Sk_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/CBRx-a_A_So Provisioning
ODUkP-X-L/CBRx-a_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/CBRx-b_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/CBRx_A_Sk Provisioning
ODUkP-X-L/CBRx_A_Sk_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/CBRx_A_Sk Reporting
ODUkP-X-L/CBRx_A_Sk_MI_AcVcPT, k=1, 2, 3 According to Not applicable
[ITU-T G.709]
ODUkP-X-L/RSn-a_A_So Provisioning
ODUkP-X-L/RSn-a_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/RSn-b_A_So Provisioning
ODUkP-X-L/RSn-b_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/RSn_A_Sk Provisioning
ODUkP-X-L/RSn_A_Sk_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/RSn_A_Sk Reporting
ODUkP-X-L/RSn_A_Sk_MI_AcVcPT, k=1, 2, 3 According to Not applicable
[ITU-T G.709]
ODUkP-X-L/VP_A_So Provisioning
ODUkP-X-L/VP_A_So_MI_Active, k=1, 2, 3 True, false False
Rec. ITU-T G.874 (07/2010) 35

ODUkP-X-L/VP_A_So_MI_CellDiscardActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_So_MI_TPusgActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_So_MI_GFCActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_So_MI_VPI-KActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk Provisioning
ODUkP-X-L/VP_A_Sk_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk_MI_CellDiscardActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk_MI_TPusgActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk_MI_VPIrange, k=1, 2, 3 0..4095 Not applicable
ODUkP-X-L/VP_A_Sk_MI_HECactive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk_MI_GFCactive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk_MI_DTDLuseEnabled, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk_MI_VPI-KActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk_MI_VPI-K_SAISActive, k=1, 2, 3 True, false False
ODUkP-X-L/VP_A_Sk Reporting
ODUkP-X-L/VP_A_Sk_MI_AcVcPT, k=1, 2, 3 According to Not applicable
[ITU-T G.709]
ODUkP-X-L/NULL _A_So Provisioning
ODUkP-X-L/NULL_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/NULL_A_Sk Provisioning
ODUkP-X-L/NULL_A_Sk_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/NULL_A_Sk Reporting
ODUkP-X-L/NULL_A_Sk_MI_AcVcPT, k=1, 2, 3 According to Not applicable
[ITU-T G.709]
ODUkP-X-L/PRBS-a_A_So Provisioning
ODUkP-X-L/PRBS-a_A_So_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/PRBS_A_Sk Provisioning
ODUkP-X-L/PRBS_A_Sk_MI_Active, k=1, 2, 3 True, false False
ODUkP-X-L/PRBS_A_Sk Reporting
ODUkP-X-L/PRBS_A_Sk_MI_AcVcPT, k=1, 2, 3 According to Not applicable
[ITU-T G.709]
NOTE 1 – If the OTUkV has multiframe.
NOTE 2 – x = 2G5, 10G, 10G3, 40G.
NOTE 3 – 0 ≤ x ≤ 1.25G.

– provisioning the flow forwarding management information;
– retrieving the flow forwarding management information;
– notifying the changes of the flow forwarding management information.
36 Rec. ITU-T G.874 (07/2010)

8.6 Connection
See [ITU-T G.7710] for a description of connection management.
This function allows a user to provision the operation of an OTN connection process.
The MI signals listed in Table 8-3 are communicated from the EMF to the connection process
through the management point.
Table 8-3 − Provisioning and reporting for connection functions

OMSnP_C Provisioning
OMSnP_C_MI_OperType Revertive, non-revertive Revertive
OMSnP_C_MI_WTR 5..12 minutes FFS
OMSnP_C_MI_HoTime 0..10 seconds in steps of 100 ms FFS
OMSnP_C_MI_ExtCMD -- (Command) Not applicable
OMSnP_C_MI_TSF-ODis True, false False
OCh_C Provisioning
OCh_C_MI_MatrixControl Connect, disconnect Not applicable
Per protection group:
OCh_C_MI_OperType Revertive, non-revertive Revertive
OCh_C_MI_WTR 5..12 minutes FFS
OCh_C_MI_HoTime 0..10 seconds in steps of 100 ms FFS
OCh_C_MI_ExtCMD -- (Command) Not applicable
OCh_C_ MI_TSF-ODis True, false False
ODUk_C Provisioning
ODUk_C_MI_MatrixControl Connect, disconnect Not applicable
Per protection group:
ODUk_C_MI_ProtType According to clause 8.4 of 000x
[ITU-T G.873.1].
ODUk_C_MI_OperType Revertive, non-revertive Revertive
ODUk_C_MI_WTR 5..12 minutes FFS
ODUk_C_MI_HoTime 0..10 seconds in steps of 100 ms FFS
ODUk_C_MI_ExtCMD -- (Command) Not applicable
ODUk_C_MI_APSChannel (Note) 0..7 (for Path, TCM1..6, Section) Not applicable
ODUk_C_MI_SDEnable True, false True
NOTE – For SNC protection with APS protocol.

– provisioning of the connection management information;
– retrieving the connection management information;
– notifying the changes of the connection management information.
Reconfigurable network elements provide connection capabilities at the OCh layer. Cross
connections can be configured between client add ports and line output ports, or between line input
ports and client drop ports, or between line input ports and line output ports (straight through matrix
connections).
NOTE 1 − A matrix connection between a client add port and a client drop port is not useful from a network
provisioning point of view as it does not carry a signal through the optical core network, but it can be useful
for loop back test purposes.
Rec. ITU-T G.874 (07/2010) 37

The following management functions are identified.
1) Get connectivity capabilities
Because reconfigurable network elements may have static cross connection restrictions, the
OS should be aware of these restrictions.
This function gives an overview of the fabric's static capability to connect termination
points. This is done by identifying one or more sets of termination points which can be
connected among each other.
Restrictions of connectivity may be caused by principal design of the switch matrix or by
the fact that not all sink termination points are fully reachable from all source termination
points. One example for restricted connectivity capability is a missing frequency
conversion function in an all-optical network.
This function should not take limited processing capacity, usage or current problems into
account. These additional restrictions have to be considered dynamically by the OS.
2) Report connectivity changes of an optical cross connect
The availability of frequency converters in a cross connect may change. As a consequence,
the connectivity sets (sets of TPs that can be connected by the fabric) may change. The NE
has to send a report when the connectivity of the fabric changes.
NOTE 2 − After receiving a report about connectivity changes, the OS may again get all
connectivity sets to update its connectivity topology.
3) Create a unidirectional point-to-point cross connection
A unidirectional point-to-point cross connection can be created between:
a) One ochCTPsink and one ochCTPsource (straight through); in case of connection
monitoring via och adapter.
b) One ochCTPsink and one ochTTPsink (drop).
c) One ochTTPsource and one ochCTPsource (add).
d) One ochTTPsource and one ochTTPsink (for loop back test purposes).
A cross connection object is created and a report on this creation has to be sent to the OS.
4) Remove a unidirectional point-to-point cross connection
This action disconnects the ochXTPs connected together. The cross connection object is
deleted and a report on this deletion has to be sent to the OS.
5) Suspend/resume traffic on a point-to-point cross connection
This function provides the possibility to suspend and resume traffic on a point-to-point
cross connection to put it out of service (suspend) or to put it in service (resume). This
change has to be reported to the OS.
6) Get all point-to-point cross connections
This action returns the list of all point-to-point cross connections created.
8.7 DEG thresholds

See [ITU-T G.7710] for a description of DEG thresholds configuration.
8.8 XXX_Reported
XXX_Reported is not applicable to O.NEs.
8.9 Alarm severity

See [ITU-T G.7710] for a description of alarm severity configuration functions.
38 Rec. ITU-T G.874 (07/2010)

8.10 Alarm reporting control (ARC)
See [ITU-T G.7710] for a description of alarm reporting control configuration functions.
8.11 PM thresholds
See [ITU-T G.7710] for a description of PM thresholds configuration functions.
8.12 Tandem connection monitoring (TCM) activations

See [ITU-T G.7710] for a description of TCM activations configuration functions.
8.13 Date and Time

The date and time functions within the OTN EMF comprise the local real time clock (RTC)
function and the performance monitoring clock (PMC) function. The message communication
function within the OTN NEF shall be capable of setting the local real time clock function.
The date and time values are incremented by a free-running local clock, or by an external timing
source. The FCAPS functions need date and time information, e.g., to time stamp event reports.
They obtain this information from the date and time function.
8.13.1 Date and time applications
[ITU-T G.7710] identifies three date and time applications. These are:
– time-stamping;
– performance monitoring clock signals;
– activity scheduling.
The OTN NEF functional requirements for these applications are specified in the following clauses.
8.13.1.1 Time-stamping
See [ITU-T G.7710] for a description of the time-stamping application.
8.13.1.2 Performance monitoring clock signals
See [ITU-T G.7710] for a description of the PMC signals.
8.13.1.3 Activity scheduling
See [ITU-T G.7710] for a description of the activity scheduling.
8.13.2 Date and time functions
There are three date and time functions defined. The local real time clock (RTC) function is
required for time-stamping and activity scheduling. The local real time clock alignment function is
required for aligning the clock with an external time reference. The performance monitoring clock
(PMC) function, in addition to RTC, is typical for digital counter measurements.
8.13.2.1 Local real time clock function
The local real time clock function is specified in [ITU-T G.7710].
8.13.2.2 Local real time clock alignment function with external time reference
The local real time clock alignment function with external time reference is specified in
[ITU-T G.7710].
8.13.2.3 Performance monitoring clock function
The performance monitoring clock function is specified in [ITU-T G.7710].
Rec. ITU-T G.874 (07/2010) 39

8.14 Control function
The ODUkT_TCMC functions are responsible for the activation/deactivation of a TCM trail. An
ODUkT_TCMC function is connected to the ODUkT_TT and ODUkT/ODUk_A functions at the
TCM control points (TCMCP) as shown in Figure 14-93 of [ITU-T G.798].
Currently only an ODUkT_TCMC function for manual activation/deactivation via the management
is defined. ODUkT_TCMC functions for automatic activation are for further study.
The MI signals listed in Table 8-4 are communicated from the EMF to the Connection process
through the management point.
Table 8-4 − Provisioning and reporting for control functions

ODUkT_TCMCm Provisioning
ODUkT_TCMCm_MI_Level 1..6 Not applicable
ODUkT_TCMCm_MI_ModeSo OPERATIONAL, MONITOR, FFS
TRANSPARENT
ODUkT_TCMCm_MI_ModeSk OPERATIONAL, MONITOR, FFS
TRANSPARENT
ODUkT_TCMCm Reporting
ODUkT_TCMCm_MI_AcSTATSo[1..6] According to clause 15.8.2.2.5 of Not applicable
[ITU-T G.709]
ODUkT_TCMCm_MI_AcSTATSk[1..6] According to clause 15.8.2.2.5 of Not applicable
[ITU-T G.709]

– provisioning of the control management information;
– retrieving the control management information;
– notifying the changes of the control management information.
9 Account management
Account management is for further study.
10 Performance management
See [ITU-T G.7710] for the generic requirements for performance management. OTN-specific
management requirements are described below.
Note that, due to the frame synchronous mapping between an ODUkP and an ODUkT and between
an ODUk and an OTUk, a frame slip that already exists at the source of the ODUkT or the OTUk
trail is also detected at the sink of the ODUkT and the OTUk trail. This frame slip will result in bit
error detection at the trail termination sink, even if the trail contains no errors. In order to suppress
these bit errors, incoming alignment error (IAE) and backward incoming alignment error (BIAE)
signalling is supported in the OTN. IAE is generated at the trail source if a frame slip is detected. It
is transmitted to the trail sink to suppress the bit errors. BIAE is the signalling for the reverse
direction and is used to suppress the backward error indication. Due to the detection, propagation
and signalling delay, no fixed time relation between the occurrence of bit errors and the detection of
the IAE exists. Therefore, bit errors detected in the current or previous second are wrong and must
be suppressed if IAE is detected.
40 Rec. ITU-T G.874 (07/2010)

The following rules apply:
– If pBIAE is active, the F_DS and the F_EBC values of the previous and the current second
must be discarded.
– If pIAE is active, the N_ DS, the F_DS, the N_EBC and the F_EBC values for the previous
and the current second must be discarded.
Note that the previous second must be discarded due to the delay of the IAE information coming
from the remote source.
10.1 Performance management applications

See [ITU-T G.7710] for the generic description for performance management applications.
10.1.1 Concepts of "near-end" and "far-end"
See [ITU-T G.7710] for a description of near-end and far-end concepts.
10.1.2 Maintenance
See [ITU-T G.7710] for a description of performance management for maintenance.
10.1.3 Bringing-into-service
See [ITU-T G.7710] for a description of bringing-into-service.
10.1.4 Quality of service
See [ITU-T G.7710] for a description of quality of service.
10.1.5 Availability
See [ITU-T G.7710] for a description of availability.
10.1.6 Reporting
See [ITU-T G.7710] for a description of reporting.
As soon as a threshold is reached or crossed in a 15-minute/24-hour period for a given performance
measurement, a threshold report (TR) is generated.
As an option for 15-minute periods, an alternative method of threshold reporting can be used.
When, for the first time, a threshold is reached or crossed for a given performance measurement, a
threshold report is generated. No threshold reports will be generated in subsequent 15-minute
periods until a clear threshold is undercrossed for the performance measurement. Then, a reset
threshold report (RTR) is generated.
Performance data shall be reportable across the NE/OS interface automatically upon reaching or
crossing a performance-monitoring threshold.
10.1.6.1 Performance data collection
See [ITU-T G.7710] for the generic description of performance data collection.
Counter-based performance data collection refers to the measurement counting associated with each
of the performance measurements and any additional performance parameter defined in this
Recommendation.
Two types of performance data collection are possible:
– A collection as specified in [ITU-T M.2120], i.e., based on information of each direction of
transport independently. This type is further referred to as performance data collection for
maintenance purposes.
Rec. ITU-T G.874 (07/2010) 41

– The collection as specified in [ITU-T G.826], i.e., based on information of both directions
of transport together. This type is further referred to as performance data collection for error
performance assessment purposes.
Counts are taken over fixed time periods of 15 minutes and 24 hours. Counting is stopped during
unavailable time.
Gauge-based performance data collection refers to the measurement gauge crossings associated
with each of the performance measurements and any additional performance parameter defined in
this Recommendation.
Performance history data is necessary to assess the recent performance of transmission systems.
Such information can be used to sectionalize faults and to locate the source of intermittent errors.
Historical data, in the form of performance measurement, may be stored in registers in the NE or in
mediation devices associated with the NE. For specific applications, for example when only quality
of service alarms are used, historical data may not be stored.
All the history registers shall be time stamped.
The history registers operate as follows:
– 15-minute registers:
The history of the 15-minute monitoring is contained in a stack of 16 registers per
monitored measurement. These registers are called the recent registers.
Every 15 minutes, the contents of the current registers are moved to the first of the recent
registers. When all 15-minute registers are used, the oldest information will be discarded.
– 24-hour registers:
The history of the 24-hour monitoring is contained in a single register per monitored
measurement. This register is called the recent register.
Every 24 hours the contents of the current registers are moved to the recent register.
10.1.6.2 History storage suppression
See [ITU-T G.7710] for a description of history storage suppression.
10.1.7 Thresholding
A thresholding mechanism can be used to generate an autonomous measurement report when the
performance of a transport entity falls below a predetermined level. The general strategy for the use
of thresholds is described in [ITU-T M.20]. Specific information for optical networks is for further
study. The thresholding mechanism is applicable only for the maintenance-based collection.
See [ITU-T G.7710] for a description of thresholding.
10.1.7.1 Threshold setting
The thresholds may be set in the NE via the OS. The OS shall be able to retrieve and change the
settings of the 15-minute and 24-hour thresholds.
The threshold values for measurements evaluated over the 15-minute period should be
programmable within the specified range.
10.1.7.2 Threshold reporting
As soon as a threshold is reached or crossed in a 15-minute/24-hour period for a given performance
measurement, a threshold report (TR) is generated.
As an option for 15-minute periods, an alternative method of threshold reporting can be used.
When, for the first time, a threshold is reached or crossed for a given performance measurement, a
threshold report is generated. No threshold reports will be generated in subsequent 15-minute
42 Rec. ITU-T G.874 (07/2010)

periods until a clear threshold is undercrossed for the performance measurement. Then, a reset
threshold report (RTR) is generated.
The detailed functioning of the threshold mechanisms is for further study.
Performance data shall be reportable across the NE/OS interface automatically upon reaching or
crossing a performance-monitoring threshold.
10.1.7.3 Evaluation for counters
See [ITU-T G.7710] for a generic description.
10.1.7.4 Evaluation for gauges
See [ITU-T G.7710] for a generic description.
10.2 Performance management functions

See [ITU-T G.7710] for generic requirements of performance management functions.
OTN NE provides the following PM management information.
Table 10-1 − PM management information

PM management information OTN function
OTSn_TT_Sk_MI_pN_DS-P
OTSn_TT_Sk_MI_pN_DS-O
OTSn_TT_Sk
OTSn_TT_Sk_MI_pF_DS-P
OTSn_TT_Sk_MI_pF_DS-O
OMSn_TT_Sk_MI_pN_DS-P
OMSn_TT_Sk_MI_pN_DS-O
OMSn_TT_Sk
OMSn_TT_Sk_MI_pF_DS-P
OMSn_TT_Sk_MI_pF_DS-O
OPSn_TT_Sk_MI_pN_DS-P OPSn_TT_Sk
OPSM/OTUk-a_A_Sk_MI_pFECcorrErr OPSM/OTUk-a_A_Sk
OCh/OTUk-a_A_Sk_MI_pFECcorrErr OCh/OTUk-a_A_Sk
OCh/OTUk-v_A_Sk_MI_pFECcorrErr OCh/OTUk-v_A_Sk
OCh/OTUkV_A_Sk_MI_pFECcorrErr (Note 1) OCh/OTUkV_A_Sk
OTUk_TT_Sk_MI_pN_EBC
OTUk_TT_Sk_MI_pN_DS
OTUk_TT_Sk_MI_pF_EBC
OTUk_TT_Sk
OTUk_TT_Sk_MI_pF_DS
OTUk_TT_Sk_MI_pBIAE
OTUk_TT_Sk_MI_pIAE
OTUkV_TT_Sk_MI_pN_EBC
OTUkV_TT_Sk_MI_pN_DS
OTUkV_TT_Sk_MI_pF_EBC
OTUkV_TT_Sk
OTUkV_TT_Sk_MI_pF_DS
OTUkV_TT_Sk_MI_pBIAE (Note 2)
OTUkV_TT_Sk_MI_pIAE (Note 2)
Rec. ITU-T G.874 (07/2010) 43

Table 10-1 − PM management information
PM management information OTN function
ODUkP_TT_Sk_MI_pN_EBC
ODUkP_TT_Sk_MI_pN_DS
ODUkP_TT_Sk_MI_pF_EBC ODUkP_TT_Sk
ODUkP_TT_Sk_MI_pF_DS
ODUkP_TT_Sk_MI_pN_delay
ODUkP/PRBS_A_Sk_MI_pN_TSE ODUkP/PRBS_A_Sk
ODUkT_TT_Sk_MI_pN_EBC
ODUkT_TT_Sk_MI_pN_DS
ODUkT_TT_Sk_MI_pF_EBC
ODUkT_TT_Sk_MI_pF_DS ODUkT_TT_Sk
ODUkT_TT_Sk_MI_pN_delay
ODUkT_TT_Sk_MI_pBIAE
ODUkT_TT_Sk_MI_pIAE
ODUkTm_TT_Sk_MI_pN_EBC
ODUkTm_TT_Sk_MI_pN_DS
ODUkTm_TT_Sk_MI_pF_EBC
ODUkTm_TT_Sk
ODUkTm_TT_Sk_MI_pF_DS
ODUkTm_TT_Sk_MI_pBIAE
ODUkTm_TT_Sk_MI_pIAE
ODUkP-X-L/PRBS_A_Sk_MI_pN_TSE ODUkP-X-L/PRBS_A_Sk
OSx_TT_Sk_MI_pN_DS OSx_TT_Sk
NOTE 1 – If the function performs FEC.
NOTE 2 – In case of frame-synchronous mapping of ODUk client signal.
– notifying of the PM management information.
11 Security management
For further study.
44 Rec. ITU-T G.874 (07/2010)

Appendix I
Management information for CM

(This appendix does not form an integral part of this Recommendation)
Regarding configuration management, the OTN network elements can be configured via the
following management information (MI) signals that are defined per atomic function in
[ITU-T G.798]:
– <atomic function name>_MI_Active
– <atomic function name>_MI_AutoMS
– <atomic function name>_MI_AdminState
– <atomic function name>_MI_APRCntrl
– <atomic function name>_MI_APSChannel
– <atomic function name>_MI_CellDiscardActive
– <atomic function name>_MI_DTDLuseEnabled
– <atomic function name>_MI_ExtCMD
– <atomic function name>_MI_ExDAPI
– <atomic function name>_MI_ExMSI
– <atomic function name>_MI_ExSAPI
– <atomic function name>_MI_FECEn
– <atomic function name>_MI_GCCAccess
– <atomic function name>_MI_GCCCont
– <atomic function name>_MI_GetAcTI
– <atomic function name>_MI_GFCActive
– <atomic function name>_MI_HECactive
– <atomic function name>_MI_HoTime
– <atomic function name>_MI_Level
– <atomic function name>_MI_MatrixControl
– <atomic function name>_MI_ModeSk
– <atomic function name>_MI_ModeSo
– <atomic function name>_MI_OperType
– <atomic function name>_MI_ProtType
– <atomic function name>_MI_SDEnable
– <atomic function name>_MI_TIMActDis
– <atomic function name>_MI_TIMDetMo
– <atomic function name>_MI_TPusgActive
– <atomic function name>_MI_TSF-ODis
– <atomic function name>_MI_TxMSI
– <atomic function name>_MI_TxTI
– <atomic function name>_MI_VPIrange
– <atomic function name>_MI_VPI-KActive
Rec. ITU-T G.874 (07/2010) 45

– <atomic function name>_MI_VPIK_SAISActive
– <atomic function name>_MI_WTR
Regarding configuration management, the OTN network elements can provide the configuration
data via the following management information (MI) signals that are defined per atomic function in
[ITU-T G.798]:
– <atomic function name>_MI_AcMSI
– <atomic function name>_MI_AcPT
– <atomic function name>_MI_AcPT[1..XMR]
– <atomic function name>_MI_AcTI
– <atomic function name>_MI_Active
– <atomic function name>_MI_AcSTATSk[1..6]
– <atomic function name>_MI_AcSTATSo[1..6]
– <atomic function name>_MI_AcVcPT
46 Rec. ITU-T G.874 (07/2010)

Appendix II
Management information for PM

(This appendix does not form an integral part of this Recommendation)
Regarding performance management, the OTN network elements can be configured via the
following management information (MI) signals that are defined per atomic function in
[ITU-T G.798]:
– <atomic function name>_MI_1second
– <atomic function name>_MI_DEGM
– <atomic function name>_MI_DEGThr
Regarding performance management, the OTN network elements can provide the performance data
via the following management information (MI) signals that are defined per atomic function in
[ITU-T G.798]:
– <atomic function name>_MI_pBIAE
– <atomic function name>_MI_pF_DS-O
– <atomic function name>_MI_pF_DS-P
– <atomic function name>_MI_pFECcorrErr
– <atomic function name>_MI_pF_EBC
– <atomic function name>_MI_pF_DS
– <atomic function name>_MI_pIAE
– <atomic function name>_MI_pN_DS-O
– <atomic function name>_MI_pN_DS-P
– <atomic function name>_MI_pN_EBC
– <atomic function name>_MI_pN_DS
– <atomic function name>_MI_pN_delay
– <atomic function name>_MI_pN_TSE
Rec. ITU-T G.874 (07/2010) 47

SERIES OF ITU-T RECOMMENDATIONS
Series A Organization of the work of ITU-T
Series D General tariff principles
Series E Overall network operation, telephone service, service operation and human factors
Series F Non-telephone telecommunication services
Series G Transmission systems and media, digital systems and networks

Series H Audiovisual and multimedia systems
Series I Integrated services digital network
Series J Cable networks and transmission of television, sound programme and other multimedia signals
Series K Protection against interference
Series L Construction, installation and protection of cables and other elements of outside plant
Series M Telecommunication management, including TMN and network maintenance
Series N Maintenance: international sound programme and television transmission circuits
Series O Specifications of measuring equipment
Series P Terminals and subjective and objective assessment methods
Series Q Switching and signalling
Series R Telegraph transmission
Series S Telegraph services terminal equipment
Series T Terminals for telematic services
Series U Telegraph switching
Series V Data communication over the telephone network
Series X Data networks, open system communications and security
Series Y Global information infrastructure, Internet protocol aspects and next-generation networks
Series Z Languages and general software aspects for telecommunication systems
Printed in Switzerland
Geneva, 2011

T Rec G.874 201007 S!!PDF e

Uploaded by

Copyright:

Available Formats

T Rec G.874 201007 S!!PDF e

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

T Rec G.874 201007 S!!PDF e

Uploaded by

Copyright:

Available Formats

I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n

SERIES G: TRANSMISSION SYSTEMS AND MEDIA,

Management aspects of optical transport

Recommendation ITU-T G.874

INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100–G.199

For further details, please refer to the list of ITU-T Recommendations.

Management aspects of optical transport network elements

Rec. ITU-T G.874 (07/2010) i

INTELLECTUAL PROPERTY RIGHTS

ii Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) iii

Management aspects of optical transport network elements

Rec. ITU-T G.874 (07/2010) 1

2 Rec. ITU-T G.874 (07/2010)

3 Terms and definitions

3.1 Terms defined elsewhere

Rec. ITU-T G.874 (07/2010) 3

4 Abbreviations and acronyms

4 Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) 5

6 Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) 7

6 OTN management functions

8 Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) 9

Operator A Operator B Operator A

GCC0 Channel never crosses GCC0 GCC0 GCC0 GCC0 GCC0

Figure 6-1 − GCC contract scenarios

10 Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) 11

ODUkP/ ODUkP/ ODUkP/

12 Rec. ITU-T G.874 (07/2010)

6.2 OTN equipment management function

Rec. ITU-T G.874 (07/2010) 13

6.3 Information flows over management points (MPs)

14 Rec. ITU-T G.874 (07/2010)

7.1 Fault management applications

Rec. ITU-T G.874 (07/2010) 15

7.2 Fault management functions

16 Rec. ITU-T G.874 (07/2010)

UNA Unit alarms

Fault cause Failure Reportable failure Network

Management applications function

Current problem list

AST Alarm status

Figure 7-1 − Fault management within the OTN NEF

Figure 7-2 − Fault cause persistency function

Rec. ITU-T G.874 (07/2010) 17

Table 7-1 − Inputs/outputs for the fault cause persistency function

18 Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) 19

20 Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) 21

7.2.4 Reportable failure function – REP

22 Rec. ITU-T G.874 (07/2010)

Table 7-3 − Input and output signals of the operational state

Rec. ITU-T G.874 (07/2010) 23

24 Rec. ITU-T G.874 (07/2010)

Rec. ITU-T G.874 (07/2010) 25