Está en la página 1de 4

ONF Liaison Statement

Date 12 January 2018

Subject ONF Technical Recommendations TR-512 v1.3.1-info

To ITU-T SG15:
Kam Lam (Q14/15 Rapporteur)
Scott Mansfield (Q14/15 Associate Rapporteur)

Kevin Vachon (MEF COO)
Shahar Steiff (LSO Committee Co-Chair)
Chris Purdy (LSO Committee Co-Chair)
Scott Mansfield (LSO RA Editor)
Andy Mayer (LSO RA Editor)
John Strassner (MEF CIM Editor)
Andrea Mazzini (MEF NRM Editor)
MEF Liaisons

CC Timon Sloane (ONF Vice President of Marketing and Ecosystem)

Reply to

From Nigel Davis (OIMT Co-Chair)

Kam Lam (OIMT Co-Chair)

Dear colleagues,

The ONF Open Information Modeling & Tooling (OIMT) team would like to share with ITU-T SG15
and MEF the TR-512 v1.3.1-info release. This release has been approved by the OIMT Technical
Steering Team (TST).

The attached zip file consists of the following:

- a ReadMe.txt file
- a TR-512.1_v1.3.1_OnfCoreIm-Overview.pdf file
- a ModelDescription folder, which contains a suite of model description documents
- a OnfModel folder, which contains the Papyrus UML model files and Profile files
- an UmlFigures folder, which contains the PNG images of the figures being used in
the description documents
The TR-512 v1.3.1-info release includes a suite of documents and the XMI-encoded UML model
developed using the open source Papyrus tooling. The description documents are built on those
of V1.2 as shown in the following table.

TR-512 Suite Core IM Relation to V1.2

TR-512.1 Overview & Structure Additions
TR-512.2 Forwarding & Termination Additions
TR-512.3 Foundation Minor additions
TR-512.4 Topology Additions
TR-512.5 Resilience Additions/moves
TR-512.6 Physical Minor additions
TR-512.7 Specification Additions
TR-512.8 Control New
New but not being
TR-512.9 OAM published in V1.3.1
TR-512.10 Operation Patterns New
TR-512.11 Processing Construct, Control Domain New
TR-512.A.1 Appendix (A series) overview New
TR-512.A.2 Model Structural Patterns & Architecture New
TR-512.A.3 Rationale of Models New
TR-512.A.4 Analogue and Media (L0) examples New
TR-512.A.5 Circuit Switched (L1 & L2) examples New
New but not being
TR-512.A.6 Packet Switched (L2 & L3) examples published in V1.3.1
New but not being
TR-512.A.7 Control and Signaling examples published in V1.3.1
TR-512.A.8 Timing & Synchronization examples New
TR-512.A.9 Processing Construct examples New
TR-512.A.10 Specification examples New
New document but
many examples are
TR-512.A.11 Resilience examples from 512.5 in V1.2
New but not being
TR-512.A.12 Application (L4 and above) examples published in V1.3.1
TR-512.DD Data Dictionary Was 512.8 in V1.2
TR-512.TM Terminology Mapping Was 512.9 in V1.2
TR-512.FE Future Enhancement Was 512.10 in V1.2
TR-512.GT Gendoc Templates Was 512.11 in V1.2

Here is a summary of major updates from v1.2 to v1.3.1

 General

o Change to document structure:

 To focus numeric series on describing the model
 Adding an appendix ("A") series that provides further
 Adding a "double letter" series to capture ongoing
model support material
o Clean up of model structure
 Forwarding and Termination
o Photonic/Media model including examples in an Appendix
o Deprecating of NE, SdnController and NetworkControlDomain
(replaced by the Control model and
ProcessingConstruct/ConstraintDomain (see below)
o LtpHasServerLtp is changed from composition to aggregation
 Foundation
o Enhancements to the state model
 Topology
o FdPort added to model as an optional
o Aggregation of FD by FD via
HigherLeeFdEncompassesLowerLevelFDs allows for many FDs
to aggregate the same subordinate FD and this is reflected in
the FcHasLowerLevelFc association multiplicity
o Added explanation of use of model to support:
 Serial-Compound Link
 Inverse Multiplexing
 Transitional Link
 Multi-Port Links
 State depedency
o Added a clarification of the definition of Link
o Explained the relationship between topology and the new
control model
o Enhanced the explanation of the approach of using the FC to
represent the Call
o Added explanation of the Resource-Service Continuum
 Resilience
o G.8032 model with examples of use in an Appendix
o Use of scheme spec concept
o Timing protection
 Equipment
o Upgrade of some classes and attributes from experimental to
preliminary or mature
o Integration with PC model providing an enhanced support for
"Equipment protection" (via a model of function resilience)
 Specification
o Improved introductory material
o Refinements to the model to improve the decoupling of
specification from the specified class
o Addition of scheme spec concept
 Addition of the Control model
o In conjunction with Processing Construct and Constraint
Domain (see below) this provides:
 A full consistent model of control
 A replacement for the NE
 Addition of Operations Pattern model
o This provides a generalized model of operations for an
outcome-oriented interaction
 Addition of Processing Construct (PC) and Constraint Domain (CD)
o This provides a generalized representation of functionality
beyond Forwarding and Termination
 Addition of supporting information on patterns underpinning the

ONF appreciates the close collaboration with ITU-T SG15 and MEF in the development of the
CoreModel and would like to take this opportunity to thank ITU-T SG15 and MEF again for their
continuous valuable input and the active participation of many individual experts in the OIMT,
OTCC TAPI, OT-IM and IISOMI discussions.

Kam LAM, Co-Chair OIMT Project
Nigel Davis, Co-Chair OIMT Project

- ONF TR-512 v1.3.1-info


Microsoft Word 97 -
2003 Document