Summary - ITU-T G.875 (12/2024) - Optical transport network: Protocol-neutral management information model for the network element view

Summary - G.875 (12/2024) - Optical transport network: Protocol-neutral management information model for the network element view

Recommendation ITU-T G.875 (ex. ITU-T G.874.1) provides a protocol-neutral management information model for managing network elements in the optical transport network (OTN). The model contains the managed entities and their properties that are useful for describing the information exchanged across interfaces defined in the ITU-T M.3010 telecommunication management network (TMN) architecture. The protocol-neutral management information model shall be used as the base for defining protocol-specific management information models, for example, common management information service element (CMISE), common object request broker architecture (CORBA) and simple network management protocol (SNMP) information models. Mapping from the protocol-neutral entities into protocol-specific objects is a decision of the specific protocol modelling design and should be described in the protocol-specific information model Recommendations.
The 2012 revision of this Recommendation updated the management information model to support the management of the new transport functions that were introduced in the 2010 revision of Recommendation ITU-T G.798 and also to support the management requirements enhancement introduced in the 2010 revision of Recommendation ITU-T G.874.
Amendment 1 enhanced the model to cover delay measurement (DM), automatic protection switching (APS) configuration, tributary slot configuration, and optical data unit (ODU) type and rate configuration, and to remove the counting of incoming alignment errors (IAEs) and backward incoming alignment errors (BIAEs).
Amendment 2 added: (1) the use of an organizationally unique identifier (OUI) to the description of the attributes selectedApplicationIdentifier and supportableApplicationIdentifierList; and (2) sub-classes the OTN current data and history data object classes from the ITU-T Q.822 current data and history data object classes.
The 2016 revision of this Recommendation has incorporated Amendment 1 and Amendment 2, and in addition the following updates: (1) changes the unified modelling language (UML) modelling tool from RSA to open source Papyrus tool; (2) updates the ITU-T G.874.1 information model to align with the ITU-T G.7711 v2.0 core information model; (3) drops subclassing the termination point (TP) classes from ITU-T M.3160; and (4) supports the additional management requirements in Recommendation ITU-T G.874.
The 2018 revision of this Recommendation up-versions the UML model tool to Papyrus v3.2.0 and the profile to v0.2.13, updates the object class mapping figures to align with ITU-T G.798, updates the model for ODU, optical transport unit (OTU), FlexO, optical tributary signal group – overhead (OTSiG-O), optical channel – overhead (OCh-O), optical multiplex section – overhead (OMS-O), and optical transmission section – overhead (OTS-O), adds Annex A for the OTN specification model, deprecates the OTU CTP, OChr and optical physical section (OPS) (OPSn, OPSMnk, OPS0) layer object classes to align with Recommendation ITU-T G.798.
The 2020 revision of this Recommendation up-versions the UML model tool to Papyrus v4.1.0 and the profile to v0.2.17; updates and cleans up the model for ODU, adding support for ODUCn, ODU delay measurement, GCC1/2 management, ODU clients (aligning with Recommendation ITU-T G.709 v6), OTU and FlexO; adds the model for generic framing procedure (GFP) management; deprecates duplicated attributes and associations; un-deprecates the OTU CTP object classes and fixes some other errors.
This 2024 revision updates ITU-T G.875 to harmonize the text and diagrams with ITU-T G.798 Revision 7, G.874 Amendment 2, G.876 Amendment 1, G.8052 Revision 4 and G.8152 Revision 3, and then updates the UML model with OTU25(u)/ODU25(u), OTU50(u)/ODU50(u), FlexO and new clients related object classes. It also enhances the performance monitoring fragments and fault management fragments, such as NIM related object classes. Lastly, it also provides some clean-up for the whole UML model, such as adjusting navigation arrows, etc.