Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • Archived Deliveries
Skip to end of metadata
Go to start of metadata

TAPI Reference Implementation Agreement


TAPI SDK



  • 2.1.4 - No longer planned.
    • 2.1.3 patch version only if required/agreed.


  • 2.2.0 - 2019, July
    • TAPI/releases/tag/v2.2.0
    • Not backward compatible with Version 2.1.3
    • Equipment inventory model (new feature)
    • Routing & Resilience Constraints fixes/updates
      • Some of the constraints were changed to read-write from read-only
      • Minor structural changes (related Topology/Connectivity constraints)
    • OAM, Notification Framework updates
      • OAM Job structure refactoring and renaming
      • OAM/Threshold profile
      • Threshold/PM parameter
      • Alarm/TCA linkage to Threshold/PM parameter
    • Topology Model update
      • added TopologyAggregatesNEP association
      • marked NodeAggregatesNEP as deprecated
      • renamed Node.ownedNodeEdgePoint to Node.nodeEdgePoint
    • ETH Technology model updates
      • mainly OAM based on MEF NRM-OAM requirements, review and feedback
    • Photonic model updates
      • mainly power control management & photonic-layer-qualifier labels


  • 2.3 RC1 - 2021, May
    • TAPI/releases/tag/v2.3-RC1
    • Not backward compatible with Version 2.1.3
    • Resilience enhancements (already available on 2.1.x branch for review)
    • ENNI Plug-In model formalized (NEP SAPI)
    • OTS-OMS model
      • Flexibility to allow base/unspecified and/or OTS and/or OMS encapsulations, i.e. a single CEP instance may include all "layers" or two ones or single one.
      • OTS, OMS, MC are essentially different aggregations of Media Channels, agreed to keep only MediaChannelConnectionEndPointSpec class, with OTS/OMS/MC specific packages.
    • DIGITAL_OTN replaces ODU Layer Protocol Name.
    • Connectivity Service Provisioning - see related scenarios in otcc2020.AM.001_TAPI_Photonic_Model_Evolution.pptx

      • OTU(+ODUCn) CEP/CSEP as single point for OTU/OTSiA ConnectivityService provisioning

      • DSR/ODU multiplexing over ODU (server layer constraints for simple provisioning scenarios).

      • ENNI/INNI Asymmetric service provisioning for simple multi-domain scenarios.

      • ServerConstraint package for more complex scenarios.
      • Layer Protocol Name and Qualifier added to the Connectivity Service
    • OAM enhancements: Digital OTN OAM
    • OtsiCapabilityPac augments NEP (through new OtsiNodeEdgePointSpec). Added maxNumOfOtsi, integer.
    • More options for OTSi and MC provisioning, e.g. either central frequency or spectrum or capacity or floating bandwidth.
    • Decoupling of Alarm/TCA model from OAM model, new TapiFm module (TR-547 V1.1 - UC 16a, 16b)
    • Quality, e.g. add missing comments to UML
    • Streaming Nigel Davis - replicate feature from TAPI 2.1.3
    • Equipment Model Nigel Davis - Feature alignment wiith TAPI 2.1.3
      • Check eqp object types for notification
    • Routing Constraint enhancement
      • Connection (existing flows)
      • "Explicit route" flag (declarative option)
    • Simplified transmission capability feature - otcc2020.AM.002-Transmission_Capability.pptx
      • Added to the NEP:
        a. supportedMuxSequences: MultiplexingSequence [1..]
        b. availableMuxSequences: MultiplexingSequence [1..]
        c. baseLayerProtocolQualifier: LayerProtocolQualifier [1]
    • Move to "deprecated" state all the RPCs
    • Remove the "presence" statement (of context container) from YANG TapiCommon module.
    • Edit the YAML Connectivity module to amend the POST body.
    • See also otcc2020.AM.005_TAPI_Enhancements.pptx for a snapshot of the agreements


  • 2.3 - 2021, August
    • TAPI/releases/tag/v2.3
    • Not backward compatible with Version 2.1.3
    • Not suitable for adoption, with bugs!
    • Integration of Streaming and Fault Management
      • Same Alarm/TCA data types augment Notification and Streaming classes.
      • For TAPI 2.3 the Object Creation model will still be different for Notification and Streaming. Postpone to TAPI 2.4 further discussion.
    • Quality: diagram adjustments, Gendoc PDF file (TapiUmlGendoc_v2_3.pdf) now includes also associations.


  • 2.3.1 Pre release - 2021, October
    • v2.3.1
    • Not backward compatible with Version 2.1.3
    • Not suitable for adoption
    • Integration of Streaming and Fault Management

      • Now TapiStreaming behaves similarly to TapiNotification, i.e. it is positioned at the core of the TAPI model.

      • TapiStreaming has been disaggregated: Each technology agnostic module specifies its own augments to Streaming (and Notification).
      • All technology agnostic modules will import both TapiNotification and TapiStreaming.
      • Object Creation model is now aligned for both Notification and Streaming.
        • Generic "object content" attribute has been kept for backward compatibility.
    • Loopback - added LOOPBACK_TERMINAL and LOOPBACK_FACILITY Oam Job Types, applicable to Connection End Points.
      • The provisioning of loopback on NEPs ("port" loopback) is postponed.
    • Bug fixings
    • For more details see TAPI213vs23rc1Vs23Vs231.pdf



  • No labels