1. OTSi Termination Model
Karthik Sethuraman
NEC Corporation of America
Sept 19, 2017

2. TAPI End Point Model Overview
Modeling of Termination, Adaptation and Monitoring processes in TAPI

3. TAPI Mapping from ITU-T
CP = Connection Point
AP = Access Point
TCP =Termination Connection Point
TTP = Trail Termination Point
CTP = Connection Termination Point
LTP = Logical Termination Point
NEP = Node Edge Point
CEP = Connection End Point
= Adaptation
= Termination
= Flexible connection F
= Fixed connection m
= List of supported
client types/layers n
= Number of supported
instances per client type

4. Layer Protocol cases in ONF Core IM (fig 4-3)
Key to encapsulated Structure in LP
Cases not used in this slide deck
Encapsulated FC
Full Layer, Fixed
Adjustable Encapsulated FC
Fixed Encapsulated FC F
CP (port) [Is G.805 CP]
Can be associated with FC
TCP (port) [Is G.805 TCP]
Full Layer, Flexible (with
Optional Exposed CP)
AP [Is G.805 AP]
Association to another LP (may be inter LTP)
Note: If not shown at the top of an LTP means the LTP does not expose signal, e.g. monitor TP
Exposed TCP F
Dual CP Pool (encapsulating zero length link)
Exposed CP with layer content rearranged
(note: has n encapsulated sub-layer CPs)
Peer CP
Exposed CP
Adapter
with pool
Pool only
Concatenating Adapter (alternative)
Concatenating Adapter
Concatenatable Exposed TCP (alternative)
Concatenatable Exposed TCP

5. TAPI LTP Template – Basic Arrangements
ODU (10x10G)
ETH, SDH, LO-ODU…
(10G)
Node
NodeEdgePoint
Device
Connection X
ServiceInterfacePoint
Link
Link Connection*
Transitional Link
Layer Protocol
ConnectionEndPoint
ODU p n m
ODU (100G)
ODU (100G)
ODU (10G)
NEP Aggregates NEPs
(same layer, capacity pool)
CEP has-server NEP
(same layer)
CEP has-client NEP
(same-layer multiplexing or different layers)
NEP connects-to NEP in another Node via Link
(same layer)
(a)
(b) F
CEP connects-to-peer CEP via explicit Connection
(same layer) – exposed CP
NEP connects-to NEP in another Node via Transitional Link
(different layer) F
(a)
(b)   F F F
CEP connects-to CEP in another Node via Link Connection
(same layer)
CEP connects-to-peer CEP via Encapsulated XC
(same layer) – terminate-and-map or fixed-mapping cases
* Link Connection is not explicitly modeled in TAPI

6. OTSi LTP (CEP/NEP) Arrangement in TAPIF
OTU_ODU AdapPac
OTU TermPac
OTU CEP
Other OTSi
Client NEP(s)
OTU CtpPac
n=1
OTU PoolPac
OTU NEP
OTSiA_OTU AdapPac
OTSi TerminationPac [1..*]
selectedNominalCentralFrequency
supportableNominalCentralFrequency [1..*]
selectedApplicationIdentifier
supportableApplicationIdentifer [1..*]
OTSiA CEP
n=1
OTSiG CtpPac
selectedFrequencySlot [1..*]
OTSiA NEP
OTSiA PoolPac
supportableFrequencySlot [0..*]
occupiedFrequencySlot [0..*]

7. OTSi Subnet (Node) Arrangement in TAPI
OTSiA Connection
OTSiA CEP
n=1..*
OTSiA NEP
OTSiA CEP
Port L1
OTSiA Link
OTSiA Conn
OTSiA Node
n=1
OTSiA NEP
OTSiA CEP
OTSiA Connection
n=1..*
OTSiA NEP
Port D1
Port L2
OTSiA Link
XOR – all possible alternatives for an OTSi assembly (OTSiG + O) – as per ITU-T G.872, the entire assembly has to be switched/terminated as a group