1. Photonic Model (ONF Share)
Stephane St-Laurent
December 06, 2018 (V15)

2. Scope
Provides background slides to define photonic model in context of TAPI
Provides feedback from work done in Facebook TIP (Service Media Channel Connection)
Use some of the OpenROADM Terminology to define the different node type (ROADM, Degree, Share Risk Group Add/Drop (SRG))

3. Photonic Definition
Media Channel: optical spectrum bandwidth between end points in the photonic layer
Network Medial Channel (NMC): continuous optical spectrum between end points in the photonic layer to represent the optical spectrum intended to carry a signal from an OTSi
Service Media Channel (SMC): continuous optical spectrum between end points in the photonic layer obtain through optical filter that serve NMC (optionally SMC)
Assembly: group of media channel (Network or Service Media Channel) managed as a single entity

4. Definition (Media Channel – SMC and NMC)
Service Media Channel (SMC)
Continuous spectrum bandwidth define by lower and upper frequency
Could be aligned on ITU grid (could be 6.25 GHz)
Include guardband (could be 6.25 GHz and it is technology dependent)
SMC are indivisible when using WSS technology (port to port where the NMC have to be routed together)
SMC could contain 0 to n NMC
SMC could be requested at a domain level to represent the contiguous spectrum offered by an optical domain
Network Media Channel (NMC)
Continuous spectrum bandwidth used to represent the signal component generated by an optical transmitter
Define by center frequency and width or lower frequency and upper frequency
Do no require to be aligned to ITU grid but are technology dependent (channel power monitor and transmitter capability)
Should not overlap guard-band of SMC

5. Why Service Media Channel with multiple NMC?
Topology
Single ( 1 NMC per SMC)
Spectral
Efficiency
Same as Fixed Grid
Routing
SMC could be added or dropped from any port ( any SRG to any SRG port)
Usage
Network with predominant mesh traffic pattern
Multiple (N x NMC per SMC)
Improved spectral efficiency compared to fixed grid
(could be 12.5/37.5 = 33%)
SMC are routed from A to Z in the network with all their contained NMC
Point-to-point DCI, Network with multiple traffic sharing the same co-routed A to Z end-point, Multi-carrier Transmitter

6. Service Media Channel (SMC)
A service media channel (SMC) is define by the optical spectrum between its lower frequency and its upper frequency
It contain guard bands (read only), a lowerGuardBand and an upperGuardBand, that represent a filter specification (will be define later)
The constraint apply to the possible value for the lower and upper frequency

7. Network Media Channel (NMC)
A network media channel (associated to the signal spectrum) is define by the optical spectrum between its lowerFrequency and its upperFrequency
It also provide a centerFrequency and its nmcSpectrumBandwidth
The constraints apply to the centerFrequency value

8. NMC Power Measurement
The measurement of the power need to be define by a bandwidth, It need to correlate between transponder (OTSi) and Optical Line System (NMC)
The nmcSpectrumBandwidth is used to measure the power associated to the signal between the lower and upper frequency

9. NMC detail
The transmitter (OTSi) own the accuracy of the signal center frequency so it could determine the required nmcSpectrumBandwidth (MHz) associated to the Network Media Channel (NMC)

10. Multiple NMC in an SMC
When multiple NMC could be contain inside one SMC, a user should be able to pass information so the NMC could be adjacent, or with some spacing, to each others
Adding some spectrum spacing could improve OSNR of the signal
Note: This provides to the Path Computation Engine (PCE) the information needed to allocate the center frequency to the NMCs. The PCE must still maintain the constraint associated to the centerFrequency that is defined by the transponder (OTSi) specification

11. Parameter used for multi-carrier SMC
Plan of Record (POR)
Spacing between NMC could be passed using nmcAdditionalSpectrum or nonAdjacentNmcSpectrum. One parameter need to be agree on. The nonAdjacentNmcSpectrum give a better understanding to evaluate non linear impairment (NLI).

12. Connectivity Services and PCE Allocation Center Frequency constraint related to OTSi
When a connectivity service receive a request with NMC information, the request could contain constraint on the center frequency associated to the transmitter. The center frequency could be limited, by the equipment, to support only center frequency as define in standard. There is fixed grid, flexible grid and grid less model
ITU G (02/2012) define constraint based on GridType (Fixed Grid and Flexible Grid)
The equation associated to the nominal center frequency (in THz) could be generalized to:
193.1 (THz) + n * granularity, where n is a positive or negative integer including 0
Where granularity set for
Fixed Grid is [ , 0.025, 0.05, 0.1] THz
Flexible Grid is [ ] THz
This could be generalized so granularity is defined as a predefine set to cover a wider set of center frequency values
granularity [ , , , 0.025, 0.05, 0.1, 0.2, 0.4] THz
It is also required to support a grid less GridType (Grid Less) center frequency
A custom value define in MHz, as example 100 ( in MHz) could be used for the granularity with the same equation assuming that it is related to THz.
So, we could define a acceptable custom granularity value (integer) from a range define in a specification [1, max] (MHz) (max TBD)
The nominal center frequency (in THz) will be
n * gridLessGranularity
Where gridLessGranularity is [integer] (MHz).
The constraint of the transmitter need also to provide the minimum and maximum center frequency associated to the capabilities of the OTSi.
minimumSupportedCenterFrequency
maximumSupportedCenterFrequency
The request, when supporting multiple NMC in an SMC ( Spectrum Optimization), could also provides a restriction on the channel adjacency
nonAdjacentNmcSpectrum (MHz)

13. Center Frequency constraint related to NMC
The NMC constraint associated to the center frequency are associated to the granularity
The 2 examples on the left show case of granularity of 25 or GHz
It is all associated to the equation:
n * granularity

14. SMCs Constraint SMC spectrum do not overlap
The SMC frequency of 2 adjacent SMCs could be however equal
upperFrequency (uf) of SMC1 could be equal to the lowerFrequency (lf) of the adjacent SMC2

15. Media Channel Pool
A media channel pool define the spectrum that is supported by the pool
This is define as a list of MC pool specifications

16. Parameter for SMC Pool Specification
The Media Channel Pool provides the supportableSpectum [lf, uf] parameter. This is to expose what the node-edge-point (NEP) pool is capable.
Connection are between connection- end-point (CEP) and capability of the connection will be expose through constraint (gridType, granularity, etc)
SMC CEP could be define from the pool supportableSpectrum but cannot extend outside the pool spectrum limit. The frequency value associated to the SMC CEP could be however equal to the limit of the pool spectrum.

17. Upper and Lower Frequency constraint related to SMC
A forwarding domain can expose, through topology, the constrain associated to the SMC granularity for the lower and upper frequency
The 2 examples on the left show case of granularity of 12.5 or 25 GHz

18. SMC granularity and gridType Constraint

19. Transponder/OLS Use Case Disaggregated Model

20. Disaggregated Use Case: Single OTSi per interface
The OTSiG could contains 1 or multiple OTSi
The OTSiG could be provided to the ROADM using multiple interface

21. Disaggregated Use Case: Multiple OTSi per interface
The OTSiG could contains 1 or multiple OTSi
The OTSiG could be provided to the ROADM using multiple interface
Each interface could contains multiple OTSi

22. Disaggregated: Transponder/ Photonic
The OAM channel need to use the OCN and have an OCC between the photonic NE and the Transponder
Needed:
Interface and Protocol to manage:
OTSi TxTransmitPower
OTSi CentralWavelength (For restauration handle by Photonic SDN)
Enable/Disable ???
And to Retrieve Capabilities:
OTSi TxTransmitPower range
OTSi CentralWavelength Tuneability (Range [ lowerFreq,upperFreq]) in MHz

23. TAPI Topology Service

24. Stack (simple case) From the bottom
PHY: Represent the resource available from a physical view
OTS:
OMS:
SMC:
NMC:

26. 3 use cases of stack

27. With SMCA and NMCA NEP Pool (Media Channel Pool):
Spectrum that could be split into different group using filter (static or dynamic). It provide the resource
NEP Assembly (Group Pool)
Pool to contain the CEP Assembly that represent group connection end-point
The service media channel (SMC) contains the continuous spectrum associated to the NMC service. It is not divisible.
SMC contain the spectrum of associated NMC, NMC could be added/removed
SMC could contain SMC also

28. Detail view
View of all the pointer in TAPI

29. NEP and CEP in a node (Example 1)
One SMCA with one NMCA

30. NEP and CEP (Example 2)
One SMCA with one NMCA

31. NEP and CEP

32. NEP and CEP
Multiple SMCA

33. Sharing port
When sharing port, the SMC connection have multiple cep pointer (fcport)

35. Transmission segment (C only)

37. Transmission Segment (C &L)

39. Stacking of SMC (2 domains)

40. TAPI Connectivity Service

41. TAPI Photonic Layer: Connectivity Services Use Case
The Orchestrator may want to do a connectivity services for a single domain or a multi-domain. In a single domain, it may not force a specific allocation to the spectrum associated to a connectivity service, so it is required to let’s the SDN controller the possibility to assign the spectrum for the services
For a multi-domain SDN controller, the orchestrator may request one of the SDN controller to propose one allocation and force this allocation on the other SDN Controller. For sure that it will have use the PCE service on all of them to find a set of joint spectrum and associated constrain before. It this case, it shall be possible to force the location of the spectrum to the service
The request could be categorized as:
Without spectrum location
With spectrum location
The orchestrator could also made a request that is focused on the NMCA information so the SMC is allocated by the SDN controller and nearly no constrain are associated to the SMC
The orchestrator could also made a request that is focus on an SMCA. It may be the case when only SMC passband is needed or the passband will be used to contain current or future NMCA/NMC. This type of request may contain NMCAs information
Those request could be categorized as:
NMC oriented service
SMC oriented service

42. Connectivity Services and PCE Allocation Example Single NMCA in NMC oriented request
The user made a request to allocate spectrum for an NMCA of 4 NMC of GHz through connectivity service
In case A, the users could pass constraint to force the 4 NMC to be inside the same SMC
In case B, there is no spectrum optimization requested and the OLS domain is constraint to FixedGrid (as example 50GHz)
In case C, Spectrum optimization is requested/default, however, there is not enough bandwidth to allocate the 4 NMC together, but only 3 NMC together.
Could also include
nonAdjacentNmcSpectrum
Constraint

43. Connectivity Services and PCE Allocation Example Multiple NMCA in NMC oriented request
The user made a request to allocate spectrum for 2 NMCA with 2 NMC each having 37.5 GHz width through connectivity service
In case A, the users could pass constraint to force the 2 NMCA to be inside the same SMC
In case B, there is no spectrum optimization requested and the OLS domain is constraint to FixedGrid (as example 50GHz). This should be requested however as 2 connectivity services, one per NMCA
In case C, spectrum optimization is requested, however, each NMCA should have independent SMC. This should be requested however as 2 connectivity services, one per NMCA

44. Connectivity Services and PCE Allocation Example SMCA oriented request
The user made a request to allocate spectrum for an SMCA of 1 SMC with a spectrumBandwidth of 100 GHz through SMC connectivity service
Case A: Without Spectrum Frequency Location
The user specify the bandwidth for the SMC, the PCE will find where to place it. The user could also add a constraint so the selected lowerFrequency of the SMC will be on a specific grid
Case B: With Spectrum Frequency Location
The user specify the location of the lower and upper frequency to be assign to the SMC. This can only be done when the user known that the network is able to support the granularity associated to the lower and upper frequency

45. Connectivity Services and PCE Allocation Example SMCA request with NMCA (using PCE)
There could be two models for requesting SMC and NMC
Case A: (Hierarchical SMCA-NMCA)
The user made an SMC request for an passband and the SMC will be allocated by the PCE. The request need also to contain the NMCA information for 2 carriers that could be also allocated by the PCE. This is a free form allocation but the request is hierarchical, the SMC connectivity service contain an SMCA with 1 SMC and the SMCA also contain NMCA information with the 2 NMC. SMCA Connectivity Service Update should also provide the ability to add NMC to the NMCA.
Case B: (Separated related request)
The user create a SMC connectivity service for a passband. The user later on create a NMC service that will relate to an SMC service instance. The NMC service needs to contain that reference. The PCE is still responsible to allocate the NMC in the SMC.
Case A
Case B

46. Connectivity Services and PCE Allocation Example SMCA request with NMCA (using NMC center-frequency)
Case A
Case B
There could be two models for requesting fixed location of NMC inside SMC
Case A: Relative Spectrum Frequency Location
Since the SMC allocation is not fixed, the NMC need to be related to the appropriate SMC
Case B: Absolute Spectrum Frequency Location
Since the SMC lower and upper frequency of SMCs are fixed, the NMC could be provided using absolute position.
It is also possible to use relative position.
We need to look at which model should be supported

47. Connectivity Services and PCE Allocation Example SMCA request with NMCA (using NMC lower-frequency)
Case A
Case B
There could be two models for requesting fixed location of NMC inside SMC
Case A: Relative Spectrum Frequency Location
Since the SMC allocation is not fixed, the NMC need to be related to the appropriate SMC
Case B: Absolute Spectrum Frequency Location
Since the SMC lower and upper frequency of SMCs are fixed, the NMC could be provided using absolute position.
It is also possible to use relative position.
We need to look at which model should be supported

48. TAPI Photonic Layer: Connectivity Services Use Case Using Declarative Request
It is possible to define an SDN model where the Orchestrator use TAPI to control multiple controller that expose their topology and do not have PCE service. In this situation, the connectivity service, exposed by the controller, is more like a declarative request then an intent request. In this situation, the orchestrator is implementing the PCE since it has enough knowledge about the network. The Orchestrator will assign the spectrum for the services to the underlying controller.
The request could be categorized as:
A declarative connectivity service request with spectrum frequency location
The orchestrator could made request that are focused to:
Pre-allocate resource (SMC only, to support stacked SMC).
Pre-allocate resource (SMC only, to support future NMC)
Allocate SMCA with NMCA

49. Connectivity Services (SMCA only) Using Declarative Request
Provide all the spectrum location
SMCA could contains one or multiple SMC

50. Connectivity Services (SMCA with NMCA) Using Declarative Request
Provide all the spectrum location
SMCA could contains one or multiple SMC
SMCA could contains 1 or more NMCA
Each NMCA could contains 1 or more NMC

51. Connectivity Services for Photonic Model
The current model of Connectivity Service need to support hierarchical structure to provide the ability to include NMC inside SMC in the request. There is few use case for that:
Submarine application are very spectrum optimized and the orchestrator could pass very define information associated to the structure of the SMC-NMC
A transponder could be optimized to have an SMC that reserve spectrum for future NMC. The User only need to update the SMC connectivity service.
An SDN Controller expose detailed topology of its controlled domain and the Orchestrator pass on a very declarative request since it allocate the spectrum.

52. TAPI Photonic Layer: Connectivity Services Use Case
Request to a single domain use case (SDN use internal PCE)
It shall be possible to request connectivity service to an OLS to do:
Create/Delete an NMCA oriented service
Create SMCA service (without NMC information)
To serve other SMCA oriented service
To serve other NMCA oriented service
Delete SMCA service (that are free of NMCA services)
In more advance use cases
Create/Delete NMCA service to an existing SMCA service
Update existing NMCA service to add/remove NMC
Create/Delete service with multiple NMCA to an SMCA composed of a single SMC

53. Initial View (OLS) to use connectivity services
The node contains all the SMCA/SMC MC pools
Exposing the SMCA SIP could be sufficient from a connectivity service point of view but when the SMCA reference multiple SMC pool, then the SIP of the PHY (the access port) is needed.
For that reason, photonic model always require the SIP of SMCA and the SIP of the PHY

54. Initial View (OLS) The node (domain) contains all the SMCA/SMC MC pool
Exposing only the SMCA could be sufficient from a connectivity service point of view
The topology can expose encapsulated topology to provide detail associated the connectivity service constraint

55. Create/Delete NMCA connectivity services
When a NMCA service is requested, it should create the supporting SMCA (1)
Information about the number of NMC(s) and their characteristic shall be provided per NMC
nmcSpectrumBandwidth
gridType (center frequency of OTSi)
granularity (center frequency of OTSi)
nonAdjacentNmcSpectrum (optional)
Information about the associated NEP should be provided
When an NMCA services is deleted, it should delete the NMCA and the supporting SMCA (1)

56. Create/Delete NMCA connectivity services Full Detail
Here is a representation of the context after the realization of the request in all the topology element

57. Create SMCA service (without NMC information)
It should be possible to create an SMCA service without providing detail of the NMC
Information about the number of SMC and its characteristic shall be provided
The bandwidth information shall contain the desired SMC spectrum bandwidth
This is mostly used in the case of an SMCA with a single SMC

58. Using in a declarative fashion

59. Using in a intent fashion

65. CIM Model with LTP

66. ROADM to ROADM (OMS with ILA)#1
ROADM #2 F F
OMS
OMS-MC Connection
ILA
OMS Con F F F F
OTS-MC Connection
OTS-MC Connection
OTS
Strand
Strand t o o R t o o R

67. CIM or TAPI and the Node FC Schema
ROADM #1
CIM or TAPI Model
Include LTP or CEP and NEP F
OMS-MC Connection
Optical ForwardingConstruct Schema
“Present the realization through Equipment with FC”
This is connected together with a link between the 2 FC or are related to the same fcport in the schema F
OTS-MC Connection
OPM (OMS, OTS) view at the demarcation point t

68. CIM or TAPI and the Node FC Schema
ILA
OMS Con F F
CIM or TAPI Model
Include LTP or CEP and NEP
OTS
OTS R t
Optical ForwardingConstruct Schema
“Present the realization through Equipment with FC”

69. ROADM to ROADM (Trib to Trib SMC) (No OTS view)
SMC-MC Connection
ROADM#1
ROADM#3
ROADM#2
SMC Con
SMC Con
SMC Con
OMS F F F F F F
OMS-MC Connection
OMS-MC Connection
Strand
Strand R t o o R t o o R t
Tributary (Add/Drop) port

70. CIM or TAPI and the Node FC Schema (No OTS View)
CIM or TAPI Model
Include LTP or CEP and NEP
ROADM#2
SMC Con F F
OMS
OMS
OMS-MC Connection
OMS-MC Connection
Strand o o
Strand R t o o
At the ROADM node view
Optical ForwardingConstruct Schema
“Present the realization through Equipment with FC”

71. CIM or TAPI and the Node FC Schema (No OTS View)
SMC-MC Connection
ROADM#1
A Sink Port could provides multiple SMC Connection
SMC Con
CIM or TAPI Model
Include LTP or CEP and NEP
OMS
OMS without OSC but with OCC (BDI-P) F F
NULL FC since point to the same FC port in this case
OMS-MC Connection
Strand R t o o
Tributary (Add/Drop) port
At the network view
Optical ForwardingConstruct Schema
“Present the realization through Equipment with FC”

72. Trib Port with Multiple SMC Connection
A port of a terminal ROADM could be the sink of multiple SMC connection

73. Trib Port with Multiple SMC Connection
SMC-MC Connection #1
SMC-MC Connection #2
SMC Con
ROADM#1
SMC Con
A Sink Port could provides multiple SMC Connection
CIM or TAPI Model
Include LTP or CEP and NEP F F
OMS
OMS-MC Connection
Tributary (Add/Drop) port R
Strand t o o

74. Multiple Trib port with one SMC Connection

75. Multiple Trib port with one SMC Connection
The SMC connection could be from multiple port
The Constraint belong to the NEP, there is one NEP per port
In a colorless/directionless (CD) implementation, multiple port share spectrum resource. This could be exposed through an aggregated NEP
So, there could be multiple FC source port
SMC-MC Connection
ROADM#1
SMC Con F
OMS F F
OMS-MC Connection
Strand R R t o o
Tributary (Add/Drop) ports

76. TAPI Model V1 (partial view, lower)
SMCA Connection
CEP
CEP
CEP
Passband [lowerfreq, upperfreq]
CTP_pac n
OMS-C MC Link (in GHz)
MC Pool
Pool_pac
NEP 1
Adapt_pac F
CEP
Layer=Photonic
Total Capacity=spectrum
Supported Spectrum Type = SMCA
Max # CTP instances=120
OMS-C (C-Band)
Term_pac
Passband [lowerfreq, upperfreq]
CTP_pac 1
OTS-C MC Link (in GHz)
MC Pool
Pool_pac
NEP 1
Adapt_pac F
CEP
Layer=Photonic
Total Capacity=spectrum{lf,uf)
Supported Spectrum Type = OMS-C
Max # CTP instances=1
OTS-C (C-Band)
Term_pac
Passband [lowerfreq, upperfreq]
CTP_pac 4
OTSG MC Link (in GHz)
MC Pool
Pool_pac
NEP 1 F
CEP
Layer=Photonic
Total Capacity=spectrum
Supported Spectrum Type = OTS-C, OTS-L,OSC, OTDR
Max # CTP instances=1,1,1,1
MIP
Down MEP
Up MEP
Need to add Raman also, TBD
CTP_pac
Media Pool
Pool_pac
NEP

77. TAPI model V1 (partial view, over OMS)
NMC Connection
NMC
CEP
CEP
CEP
Provide visibility at each NMC band
Passband [lowerfreq, upperfreq]
CTP_pac
The Spectrum is the effective spectrum, filter less guardband n
MC Pool
Pool_pac
NEP
Layer=Photonic
Total Capacity=spectrum [lf,uf]
Supported Spectrum Type = NMC
Max # CTP instances=120
SMC Connection 1
SMC
CEP
Provide visibility at each SMC band
Band [ lowerfreq, upperfreq]
Passband [lowerfreq, upperfreq]
CTP_pac n
Layer=Photonic
Total Capacity=spectrum [lf,uf]
Supported Spectrum Type = SMC
Max # CTP instances=120
???
Pool_pac?
NEP 1
SMCA Connection
CEP
Could be a UpMEP or a MIP
CTP_pac n
OMS-C MC Link (in GHz)
MC Pool
Pool_pac
NEP 1
Adapt_pac F
CEP
Layer=Photonic
Total Capacity=spectrum
Supported Spectrum Type = SMCA
Max # CTP instances=120
Term_pac
Passband [lowerfreq, upperfreq]
CTP_pac

78. TAPI model V1 at Edge node (partial view, over OMS)
CEP
OTSiA
NEP
OTSi
CEP
CEP
CEP
OTSi Connection
Passband [lowerfreq, upperfreq]
CTP_pac 1
MC Pool
Pool_pac
NEP
NMC Connection
CEP
CEP
CEP
NMC
Passband [lowerfreq, upperfreq]
CTP_pac n
MC Pool
Pool_pac
NEP
Layer=Photonic
Total Capacity=spectrum [lf,uf]
Supported Spectrum Type = NMC
Max # CTP instances=120
SMC Connection 1
SMC
CEP
Provide visibility at each SMC band
Band [ lowerfreq, upperfreq]
Passband [lowerfreq, upperfreq]
CTP_pac n
MC Pool
Pool_pac
NEP
Layer=Photonic
Total Capacity=spectrum [lf,uf]
Supported Spectrum Type = SMC
Max # CTP instances=120 1
SMCA Connection
CEP
Could be a UpMEP or a MIP
Passband [lowerfreq, upperfreq]
CTP_pac n
OMS-C MC Link (in GHz)
MC Pool
Pool_pac
NEP
Layer=Photonic
Total Capacity=spectrum
Supported Spectrum Type = SMCA
Max # CTP instances=120 1

79. TAPI model V2 (partial view, over OMS)
NMC Connection
NMC
CEP
CEP
CEP
Provide visibility at each NMC band
Passband [lowerfreq, upperfreq]
CTP_pac
The Spectrum is the effective spectrum, filter less guardband n
MC Pool
Pool_pac
NEP
Layer=Photonic
Total Capacity=spectrum [lf,uf]
Supported Spectrum Type = NMC
Max # CTP instances=120
SMC Connection 1
SMC
CEP
Provide visibility at each SMC band
Band [ lowerfreq, upperfreq]
Passband [lowerfreq, upperfreq]
CTP_pac n
Supported Spectrum Type = SMC
Max # CTP instances=120 1
SMCA Connection
CEP
Could be a UpMEP or a MIP
CTP_pool pac n
OMS-C MC Link (in GHz)
MC Pool
Pool_pac
NEP 1
Adapt_pac F
CEP
Layer=Photonic
Total Capacity=spectrum
Supported Spectrum Type = SMCA
Max # CTP instances=120
Term_pac
Passband [lowerfreq, upperfreq]
CTP_pac

80. TAPI model V2 (partial view, over OMS)
NMCA Connection
CEP
Supported Spectrum Type = NMC
Max # CTP instances=120
Could be a UpMEP or a MIP
CTP_pool pac
NMC Connection n
NMC
CEP
CEP
CEP
Provide visibility at each NMC band
Passband [lowerfreq, upperfreq]
CTP_pac
The Spectrum is the effective spectrum, filter less guardband n
Layer=Photonic
Total Capacity=spectrum [lf,uf]
Supported Spectrum Type = NMC
Max # CTP instances=120
MC Pool
Pool_pac
NEP
SMC Connection 1
SMC
CEP
Provide visibility at each SMC band
Band [ lowerfreq, upperfreq]
Passband [lowerfreq, upperfreq]
CTP_pac n
Supported Spectrum Type = SMC
Max # CTP instances=120 1
SMCA Connection
CEP
Could be a UpMEP or a MIP
CTP_pool pac n
OMS-C MC Link (in GHz)
MC Pool
Pool_pac
NEP 1
Adapt_pac F
CEP
Layer=Photonic
Total Capacity=spectrum
Supported Spectrum Type = SMCA
Max # CTP instances=120
Term_pac
Passband [lowerfreq, upperfreq]
CTP_pac

81. TAPI model V2 for Add/Drop (partial view, over OMS)
NMC Connection
NMC
CEP
CEP
CEP
Provide visibility at each NMC band
Passband [lowerfreq, upperfreq]
CTP_pac
The Spectrum is the effective spectrum, filter less guardband n
MC Pool
Pool_pac
NEP
Layer=Photonic
Total Capacity=spectrum [lf,uf]
Supported Spectrum Type = NMC
Max # CTP instances=120
SMC Connection 1
SMC
CEP
Provide visibility at each SMC band
Band [ lowerfreq, upperfreq]
Passband [lowerfreq, upperfreq]
CTP_pac n
Supported Spectrum Type = SMC
Max # CTP instances=120
SMCA Connection
CEP
The SMCA CEP could have multiple source MC pool (NEP) for the add/drop interface
CTP_pool pac n n
NEP
OMS-C MC Link (in GHz)
MC Pool
Pool_pac
MC Pool
Pool_pac
NEP 1 1
Adapt_pac F
CEP
Adapt_pac F
CEP
Layer=Photonic
Total Capacity=spectrum
Supported Spectrum Type = SMCA
Max # CTP instances=120
Term_pac
Term_pac
CTP_pac
CTP_pac

82. TAPI model V3 (partial view, over OMS)
NMCA
NMCA Connection
CEP
Could be a UpMEP or a MIP
List of band [ lowerfreq, upperfreq]
CTP_pool pac
The Spectrum is the effective spectrum, filter less guardband provided by the list of SMC in the SMCA j
Layer=Photonic
Total Capacity=list of spectrum [lf,uf]
Supported Spectrum Type = NMCA
Max # CTP instances=j
MC Pool
Pool_pac
NEP 1
SMCA
SMCA Connection
CEP
Could be a UpMEP or a MIP
List of band [ lowerfreq, upperfreq]
CTP_pool pac n
Layer=Photonic
Total Capacity= spectrum [lf,uf] (could be a list)
Supported Spectrum Type = SMCA
Max # CTP instances=n
MC Pool
Pool_pac
NEP 1
Adapt_pac F
CEP
Term_pac
DownMEP (OMS) toward another node
OMS
Passband [lowerfreq, upperfreq]
CTP_pac

83. TAPI model V3 with OTSiA (partial view, over OMS)
OTSiA could use NMCA in a one-to-one relation, however, the OTSi signal could come from different interface, this relation need to be visible
OTSiA
OTSiA Connection
CEP
MIP for the OTSiA
List of signal [ centerFreq, width]
CTP_pool pac
The Spectrum is the spectrum associated to the list of NMC of the NMCA 1
Layer=OTSiA
Total Capacity=list of spectrum [lf,uf]
Supported Spectrum Type = OTSiA
Max # CTP instances=1
MC Pool
Pool_pac
NEP 1
NMCA
NMCA Connection
CEP
Could be a UpMEP or a MIP
List of band [ lowerfreq, upperfreq]
CTP_pool pac
The Spectrum is the effective spectrum, filter less guardband provided by the list of SMC in the SMCA j
Layer=Photonic
Total Capacity=list of spectrum [lf,uf]
Supported Spectrum Type = NMCA
Max # CTP instances=j
MC Pool
Pool_pac
NEP 1
SMCA
SMCA Connection
CEP
Could be a UpMEP or a MIP
List of band [ lowerfreq, upperfreq]
CTP_pool pac n
Layer=Photonic
Total Capacity= spectrum [lf,uf] (could be a list)
Supported Spectrum Type = SMCA
Max # CTP instances=n
MC Pool
Pool_pac
NEP 1
Adapt_pac F
CEP
Term_pac
DownMEP (OMS) toward another node
OMS
Passband [lowerfreq, upperfreq]
CTP_pac

84. TAPI model V4 (partial view, over OMS)
No OTSiA needed on Degree Interface
An SMCA could contain more then one NMCA
NMC
NMC Connection
The Spectrum is the effective spectrum, filter less guardband provided by the SMC
fcPort_pac
NMCA Connection n
CTP_pac
Band [lowerfreq, upperfreq]
NMCA 1
List of CEP [ CEP_Id]
CEP_Group 1
Layer=Photonic
Total Capacity=spectrum [lf,uf] (could be a list)
Supported Spectrum Type = NMC
Max # CTP instances=j n n
Layer=Photonic
Supported Spectrum Type Group = NMCA
Max # CTP instances=n
Pool Group
Pool_pac
MC Pool 1 n 1
SMC Connection
SMC
fcPort_pac n
SMCA Connection n
CTP_pac
Band [lowerfreq, upperfreq]
SMCA 1
List of CEP [ CEP_Id]
CEP_Group
Layer=Photonic
Total Capacity= spectrum [lf,uf] (could be a list)
Supported Spectrum Type = SMC
Max # CTP instances=n n n
Layer=Photonic
Supported Spectrum Type Group = SMCA
Max # CTP instances=n
Pool Group
Pool_pac
MC Pool 1 n 1 F
Adapt_pac
There is 1 PoolGroup per Degree (Line interface)
There is 1 PoolGroup for all the add/drop NEP of a ROADM node
Term_pac
OMS
DownMEP (OMS) toward another node
fcPort_pac
CTP_pac
Band [lowerfreq, upperfreq]

85. TAPI model V4 with OTSiA (partial view, over OMS)
No Connection needed n
CTP_pac
centerFrequency (MHz)
OTSiA 1
List of CEP [ CEP_Id]
CEP_Group 1
Layer=Photonic
Total Capacity=spectrum [lf,uf] (could be a list)
Supported Spectrum Type = NMC
Max # CTP instances=j
An SMCA could contain more then one NMCA 1
Pool Group n
Pool_pac
MC Pool 1
NMC
NMC Connection
The Spectrum is the effective spectrum, filter less guardband provided by the SMC 1
fcPort_pac
NMCA Connection 1 n
CTP_pac
Band [lowerfreq, upperfreq]
NMCA 1
List of CEP [ CEP_Id]
CEP_Group 1
Layer=Photonic
Total Capacity=spectrum [lf,uf] (could be a list)
Supported Spectrum Type = NMC
Max # CTP instances=j n n
Layer=Photonic
Supported Spectrum Type Group = NMCA
Max # CTP instances=n
Pool Group
Pool_pac
MC Pool 1 n 1
SMC Connection
SMC
fcPort_pac n
SMCA Connection n
CTP_pac
Band [lowerfreq, upperfreq]
SMCA 1
List of CEP [ CEP_Id]
CEP_Group
Layer=Photonic
Total Capacity= spectrum [lf,uf] (could be a list)
Supported Spectrum Type = SMC
Max # CTP instances=n n n
Layer=Photonic
Supported Spectrum Type Group = SMCA
Max # CTP instances=n
Pool Group
Pool_pac
MC Pool 1 n 1 F
Adapt_pac
There is 1 PoolGroup per Degree (Line interface)
There is 1 PoolGroup for all the add/drop NEP of a ROADM node
Term_pac
OMS
DownMEP (OMS) toward another node
fcPort_pac
CTP_pac
Band [lowerfreq, upperfreq]

86. TAPI model V4 (partial view, over OMS) with OTSiA
No Connection needed n
CTP_pac
centerFrequency (MHz)
OTSiA 1
List of CEP [ CEP_Id]
CEP_Group 1 1
Layer=Photonic
Total Capacity=spectrum [lf,uf] (could be a list)
Supported Spectrum Type = NMC
Max # CTP instances=j 1
An SMCA could contain more then one NMCA
Pool Group 1 n
Pool_pac
MC Pool
NMC #1 Connection
NMC
The Spectrum is the effective spectrum, filter less guardband provided by the SMC
NMC #2 Connection 1 1
fcPort_pac
NMCA Connection 1 n
CTP_pac
Band [lowerfreq, upperfreq]
NMCA 1 1
List of CEP [ CEP_Id]
CEP_Group 1 n
Layer=Photonic
Total Capacity=spectrum [lf,uf] (could be a list)
Supported Spectrum Type = NMC
Max # CTP instances=j n n
Layer=Photonic
Supported Spectrum Type Group = NMCA
Max # CTP instances=n
Pool Group 1 n
Pool_pac
MC Pool 1 1
SMC Connection
Use Case: Multi-Carrier SMC
SMC
fcPort_pac n
SMCA Connection n
CTP_pac
Band [lowerfreq, upperfreq]
SMCA
List of CEP [ CEP_Id]
CEP_Group 1
Layer=Photonic
Total Capacity= spectrum [lf,uf] (could be a list)
Supported Spectrum Type = SMC
Max # CTP instances=n n n n
Layer=Photonic
Supported Spectrum Type Group = SMCA
Max # CTP instances=n
Pool Group
Pool_pac
MC Pool 1 n 1 1 F F
Adapt_pac
There is 1 PoolGroup per Degree (Line interface)
There is 1 PoolGroup for all the add/drop NEP of a ROADM node
Term_pac
OMS
DownMEP (OMS) toward another node
fcPort_pac
CTP_pac
Band [lowerfreq, upperfreq]

87. TAPI model V4 (partial view, over OMS) with OTSiA
No Connection needed n
CTP_pac
centerFrequency (MHz)
OTSiA 1
List of CEP [ CEP_Id]
CEP_Group 1 1
Layer=Photonic
Total Capacity=spectrum [lf,uf] (could be a list)
Supported Spectrum Type = NMC
Max # CTP instances=j 1
An SMCA could contain more then one NMCA
Pool Group 1 n
Pool_pac
MC Pool
NMC #1 Connection
NMC
The Spectrum is the effective spectrum, filter less guardband provided by the SMC
NMC #2 Connection 1 1
fcPort_pac 1 n
NMCA Connection
CTP_pac
Band [lowerfreq, upperfreq]
NMCA 1 1
List of CEP [ CEP_Id]
CEP_Group 1 n
Layer=Photonic
Total Capacity=spectrum [lf,uf] (could be a list)
Supported Spectrum Type = NMC
Max # CTP instances=j n n
Layer=Photonic
Supported Spectrum Type Group = NMCA
Max # CTP instances=n
Pool Group 1 n
Pool_pac
MC Pool
SMC #1 Connection 1 1
SMC #2 Connection
SMC
Use Case: Single-Carrier SMC
fcPort_pac n
SMCA Connection n
CTP_pac
Band [lowerfreq, upperfreq]
SMCA
List of CEP [ CEP_Id]
CEP_Group 1
Layer=Photonic
Total Capacity= spectrum [lf,uf] (could be a list)
Supported Spectrum Type = SMC
Max # CTP instances=n n n n
Layer=Photonic
Supported Spectrum Type Group = SMCA
Max # CTP instances=n
Pool Group
Pool_pac
MC Pool 1 n 1 1 F F
Adapt_pac
There is 1 PoolGroup per Degree (Line interface)
There is 1 PoolGroup for all the add/drop NEP of a ROADM node
Term_pac
OMS
DownMEP (OMS) toward another node
fcPort_pac
CTP_pac
Band [lowerfreq, upperfreq]

88. Transponder: Multi-OTSi with Single Carrier SMC
ROADM
OTSiA Placement???
It will also terminate the OCC and need to provides API for Control
OTSiA relation with NMCA, it is a one-to-one relation, OTSiA is just there to provide support for one MIP and OCC with transponder
OTSiA
OTUCn
NMCA
NMCA
NMCA
OTSiA
NMC
OTSi
NMC
NMC
NMC
SMCA
SMCA
SMCA
SMC
SMC
SMC
SMC
OMS
OMS
OMS
OMS Link
OMS
OTS
OTS
OTS Link
OMS Link
Add/Drop port

89. Optical Media Channel Service (Single Domain)
OMCS (the end-to-end Optical Media Channel Service)
ConnectivityService (SMCA)
Connection (SMCA)
UNI
UNI
Node
ServiceInterfacePoint
ServiceInterfacePoint
ConnectivityServiceEndPoint
ConnectivityServiceEndPoint
NodeEdgePoint
NodeEdgePoint
ConnectionEndPoint
ConnectionEndPoint

90. Optical Media Channel Service
The ConnectivityService provisioning shall include:
NMC bandwidth requirement
Constraint on center frequency
Constraint on list of NEP (Physical port)
Constrain on Center Frequency per NEP
SMCA MEP
UNI MEP
ConnectivityService
Connection
UNI
Connection is ended by “SMCA” CEPs
UNI
Node
UNI-N
UNI-N
MIP
Down MEP
Up MEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP n n n n
NEP
NEP
NEP
NEP 1 1 1 1
“SMCA”
CEP
“SMCA”
CEP
CEP
CEP
“SMCA”
“SMCA”
CEP
CEP n n n n
OMS Link
NEP
NEP
OMS Link
NEP
NEP
OMS Link 1 1 1 1
“UNI”
CEP
CEP
“INNI”
“INNI”
CEP
CEP
“UNI”
node 1 n
node
NEP
OTS Link
NEP 1 1
CEP
“INNI”
“INNI”
CEP

91. Optical Media Channel Service (Multi-Domain)
OMCS (the end-to-end Optical Media Channel Service)
OMCS (Domain1)
OMCS (Domain 2)
ConnectivityService
ConnectivityService
Connection
Connection
UNI
UNI
Node
E-NNI
Node
ServiceInterfacePoint
ServiceInterfacePoint
ServiceInterfacePoint
ServiceInterfacePoint
ConnectivityServiceEndPoint
ConnectivityServiceEndPoint
ConnectivityServiceEndPoint
ConnectivityServiceEndPoint
NodeEdgePoint
NodeEdgePoint
NodeEdgePoint
NodeEdgePoint
ConnectionEndPoint
ConnectionEndPoint
ConnectionEndPoint
ConnectionEndPoint
Note that end-to-end OMCS and domain OMCS are concepts of optical multi-domain Service model. In case of multi-operator scenario, the SP is responsible for end to end OMCS, each Operator is responsible for its domain OMCS. This implies that there are two levels of OAM, SP level and Op level.
The ConnectivityService must be provisioned considering these two levels.

92. node node ConnectivityService Connection UNI UNI-N ENNI ENNI Node
The ConnectivityService provisioning shall include:
NMC bandwidth requirement
Constraint on center frequency
SMCA MEP
SMCA MIP
UNI MEP
ENNI MEP (OMS)
ENNI MEP (OTS)
ConnectivityService
Connection
ENNI
UNI
Node
UNI-N
ENNI
Connection is ended by “EVC” CEPs
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP
CEP n n n n
NEP
NEP
NEP
NEP 1 1 1 1
“SMCA”
CEP
CEP
“SMCA”
CEP
CEP
CEP
“SMCA”
“SMCA”
CEP n n n n
OMS Link
NEP
NEP
OMS Link
NEP
NEP
OMS Link 1 1 1 1
“UNI”
CEP
CEP
“INNI”
“INNI”
CEP
CEP
“ENNI”
node 1 n n
node
NEP
OTS Link
NEP
NEP
OTS Link 1 1 1
CEP
“INNI”
“INNI”
CEP
CEP
“ENNI”
MIP
Down MEP
Up MEP

93. OTSiA Connection
There is no need to make OTSiA connection on the optical line system unless OAM is used between transponder and Optical Line System
In such case, an OTSi CEP (CTP only) need to be instantiated to define the list of NMC used
Provide the mapping between SMCA to OTSiA for the MIP that will provides the FDI-P/FDI-O (OTSiA)

94. MC_PoolPac
Typedef:
passband = [lowerFrequency (MHz), upperFrequency (MHz)]
spectrumType: OTS,OMS,SMC,NMC,OTSi
frequencyGranularity: 100,50,25,12.5,6.25,3.125,0.001 in GHz
Channel plan: FixeGrid (cover 100,50,25,12.5), Flexgrid (cover 12.5, 6.25, 3.125), Gridless( cover 0.001)
opticalBandLabel [ c-band, l-band, c&l-band, undefined]
For OMS/SMC/NMC pool (as per Stephane definition of pool layer)
Supported MC Capabilities
Range Spec
List of [passband]
Bandwidth Spec (of the supported CEP)
Minimum channel width (MHz)
Maximum channel width (MHz)
Frequency Granularity
Guardband
Specified in MHz (could be 0)
Channel Plan and Granularity
opticalBandLabel

95. Reference for TAPI OAM Overhead Layer (Most of it is from G.798)

96. Overhead defined in G.798 (Missing stuff)
The G.798 does not cover:
OTS Band (ex. C and L)
OMS band (ex. C and L)
Service Media Channel
SMC
SMCG
SMCA
SMCG-O
Adaptation layer between SMCG-O/OTSiG-O
Modified adaptation layer in OMS-O/SMCG-O

97. Overhead Layer Overview

98. Overhead Layer Overview
The OTSiG-O may not be supported as presented here
The OTSiG-O may not have the TTP on a Transponder
For the OLS, the OTSiG-O may still be supported on the CTP

99. Overhead Layer Overview
OSC include OTS-O Overhead
OTS include OMS-O Overhead
OMS include OTSiG-O Overhead

100. Generic Layer Processing
From T-REC-G Generic layer fault processing Layer fault processing is concerned with the detection of failures within a layer network, the generation of consequent actions (for suppression of unwanted downstream alarms and remote information for upstream single-ended maintenance), and the report of probable fault causes to the management system. Figure 8-4 illustrates in general the atomic functions connection, trail termination and adaptation of a layer which perform their specific fault-processing tasks. The connection function, if present, can interconnect the adaptation and trail termination functions according to the signal flow shown. Note that not all features are supported by all layers. For the specific fault processing, see the layer‑specific functions.
Figure 8-4 – Generic layer fault processing

101. OSC Layer Function

102. OTS-O Layer Function
Optical is continuous, its effect is seen by all the downstream ME
All OTS ME see that all the optical signal is gone, except the ASE that could continue to accumulate (implementation related)

103. OTS-O Layer Function

104. OTS-O Layer Function (G.798 12/2017)

105. OMS-O Layer Function

106. OMS-O Layer Function

107. OMS-O Layer Function

108. OMS-O Layer Function

109. OTSiG-O Layer Function

110. ToDo Convert model to be similar to Generic OAM Add SMCG-O layer
Define MEP (Up/Down) and MIP Function
Add SMCG-O layer
Adaptation to NMCG-O
Add NMCG-O layer
Adaptation to OTSiG-O
Modify OMS-O adaptation to remove OTSiG-O and replace it with SMCG-O

111. Mapping from ITU-T and TMF Termination to ONF

112. Power Monitoring

113. OPM in ITU
Optical Power Measurement is define in ITU to monitor the total power associated to media channel, its mean that it is bound to select spectrum

114. OPM Location
Most implementation translate the location of the measurement point to a location at the demarcation point close to the pin (port)
This provides the best performance for EDFA gain and relate to the specification of the equipment
OpenROADM and Facebook TIP use that location for OPM

115. OPM in ITU
The T17-SG15-C-0521!R1!MSW-E contribution provide a example of OPM for an optical amplifier

116. Base Model
Need to monitor the power for each of the media channel

117. Model 1 (not good)
Could be represented using tap coupler and pin monitor in the FC chain
The implementation normally assume that the pin monitor is compensated to the demarcation point but this could not be obvious to deduct
In this implementation, it is not the right spectrum that is monitored
Not good, measurement is bound to media channel spectrum

118. Model 2
In this implementation, the OPM reflect the power associated to the spectrum. It is the optical power seen in the media channel
Again, translation is required to present the information at the demarcation point

119. Proposal to define FC to represent PD Sensor
PD Sensors FC contain filtered Pin Monitor
The FC expose no loss from the input to the output with translation (Other FC will be included to represent effective lost where it should be present in the schema)
It contain list of OPM with spectrum definition
They could be place in the FC chain where we want to see the measurement
FC port of other FC can delegate their measurement to that PD Sensor

120. PD Sensor
The FC port were the media channel start delegate the measurement to the PD Sensor FC
The sensor is located to the wanted point of measurement
It present a Band Power measurement

121. Flex Channel Monitor Sensor
Possible Location for Channel Monitor
Only requirement from ITU is to detect if an NMC is present to feed the OTSiA OAM
For Control, it will be preferable to report SMC and NMC at the Demarcation point

122. Band Monitor (SMC and NMC)
The NMC power need to be consistent with their client server relation.
It could be translated to the demarcation point
Reported Power is spectrum bounded

123. OPM Monitor location

124. OPM
The TAPI stack expose CTP and TTP, those CEP present OPM package and the location could be referred into the Optical FC Schema (OpenDevice Schema in Facebook TIP)
The OPM stack maintain the OPM validity because of the client-server relationship

125. Backup

126. 2 Layers (OTSiA and Service Media Channel)
OTSiA is associated to OTSi signal spectrum connection and the relevant OAM
Band Spectrum (or Service Media Channel (SMC)) is associated to optical spectrum used to support one or multiple NMC signal
Optical spectrum could be set (and potentially validated) before the existence of the OTSiA
An SMC group is a list of SMC to support an OTSiG connection. This could provides a one- to-one association between OTSiG and SMCG
In fact, it will be very desired to have mandatory one-to-one association

127. OTSiA and Service Media Channel (Separation)
T17-SG TD-WP3-0125!R1!MSW-E (Draft G.Media Discussion)
6 Functional architecture of optical media
The functionality of the optical media consists of constructs that can carry/propagate optical signals as well as elements that can operate on optical waves (e.g., filters). A key result of arranging and configuring these elements is the construction of network media channels, each of which can support an OTSi. The structure of an optical media network is provided in Figure 6-1 below.
[Editor note: needs further review.]
Optical tributary signals (OTSi) are each characterized by their central frequency and an application identifier (see [ITU‑T G.698.2]). The OTSi is depicted by the optical signal modulator/demodulator, as shown in Figure 5‑1.
Below the OTSi are the media constructs that provide the ability to configure the media channels (see clause 7.1.2). The nominal central frequency and width of a media channel is defined by its frequency slot (as defined in [ITU‑T G.694.1]). Each OTSi is guided to its destination by an independent network media channel.
Media channels must be configured before any OTSi can be carried. The effective frequency slot of a media channel is defined by the filters that are in the path of the media channel. The effective frequency slot may be sufficient to support more than one OTSi.
The media constructs and media element are described in clause 7, the OTSiA is described in clause 10.
An application identifier includes the application codes defined in the appropriate optical system Recommendations, as well as the possibility of proprietary identifiers. The identifier covers all aspects of the signal, including forward error correction, baud rate and modulation type.
A media channel that may carry multiple OTSi may be used to provide what is commonly called an "express" channel.
8.1 Assignment of signals to media channels
A media channel may be configured before it has been decided which OTSi will be allocated to it. As described in clause 7.1.2 the OTSi must be compatible with the network media channel that has been assigned.

128. Separation 10.1 Management of OTSiA connections
T17-SG TD-WP3-0125!R1!MSW-E (Draft G.Media Discussion)
10.1 Management of OTSiA connections
From a management control perspective, a request to carry an OTSiA should be considered as a single action. This action involves the configuration of the OTSi modulator and demodulator, the network media channels and the OTSiG‑O. Configuration of the network media channels includes the configuration of the media elements that encompass the media constructs (e.g., media subnetworks, As described above, the network media channel may be fully or partially configured before the OTSiA connection request is received.
flexible grid capable filters and possibly amplifiers) that are part of the serial concatenation of media channels that forms the network media channel.
Two simple cases for the configuration of a network element that includes a media subnetwork when an OTSiA connection request is received are described below:
1) Pre‑configured media elements: In this case the media channels in the media subnetwork and the associated filters are configured before the OTSiA connection request is received:
• The OTSiG‑O connection function and the OMS‑O MSI are configured.
• The media channel(s) in media subnetwork must be checked to verify that the correct ports are connected so that all members of the OTSiG are directed to and or from the same OMS media port. The associated filters are checked to ensure that frequency slot of each filter is compatible with the frequency slot requested for each OTSi.
• In general when the OTSiA is deleted, only the OTSiG‑O connection and OMS‑O MSI (for that OTSiG) should be removed, the configuration of the media elements should not be changed.
or:
2) The media elements are not configured:
• In this case, the media channels in the media subnetworks and filters are configured as a result of the OTSiA connection request. The media channels in the media subnetwork and the associated filters, the OTSiG‑O connection and the OMS‑O MSI are configured. The consistency checks described above should be performed.
• In general, deletion of the OTSiA should also result in the deletion of the OTSiG‑O connection the OMS‑O MSI. The media subnetwork and filter media channels should also be deleted, except in the case where a media channel is being used to support another network media channel.

129. PE1 ETH Device Node NodeEdgePoint ConnectionEndPoint
ETHClt
CTP
ETH
ETHInt
CTP
ETH X X X X
ETH
ETHInt
NEP
ETH
ETH SIP
(x10)
ETHClt
NEP
(x10)
Shim Layer = ETH
Total Pool Capacity=10G
supported granularity=10G
ETH
(100G) F
Shim Layer = ETH
Total Pool Capacity=10G
supported granularity=10G
ODU2
CEP
ODU
Shim Layer = ETH
Total Pool Capacity=100G
supported granularity=10G
ODU
ETHoODU
Node
NodeEdgePoint
Device
Connection X
ServiceInterfacePoint
Link
Link Connection*
Transitional Link
Layer Protocol
ConnectionEndPoint
ConnServiceEndPoint
ODU2
NEP
ODU
Shim Layer = ODU
Total Pool Capacity=100G
supported granularity=10G
ODU
POOL
ODU4
TTP
Shim Layer = ODU
Total Pool Capacity=100G
supported granularity=10G
ODU
ODU
ODU
ODU4
CTP
ODU
ODU
PE1
ODU4
NEP
Shim Layer = ODU
Total Pool Capacity=100G
supported granularity=100G
* Link Connection is not explicitly modeled in TAPI

130. OTSiA connections FD of the ROADM node and FD of the Degrees
Add/Drop and Express
Use this model or use a model where OTSiA are supported by SMCG
Optical node will do SMCG connection

131. Base Model (Reduce view of Service MC)
Reduced View of the optical service media channel
CEP of the NMC could be added and remove
The FC does not require to be present to support signal detection (Only the CEP of the NMC and SMC)

132. Aggregated and Disaggregated view (WSS) Direction 1
Combiner and Splitter force the use of Access port that Aggregate Access Port
Service Media Channel Layer
Aggregated view:
ROADM node
From Trib to Line
Disaggregated view
Degree
SRG

133. Aggregated and Disaggregated view (WSS) Direction 2
Combiner and Splitter force the use of Access port that Aggregate Access Port
Service Media Channel Layer

134. Degree to Degree (WSS to WSS)
Aggregated view
Service media channel at the ROADM node
Disaggregated view
Service media channel at the Degree node
Service media chanel at the SRG (Add/Drop Share Risk Group)

135. Aggregated and Disaggregated view (WSS-WSS) Direction 1
Aggregated view from client to line interface
One FC for the service media channel
Disaggregated view from Client to System and System to Line
One FC for the service media channel for the Degree
One FC for the service media channel for the SRG (Add/Drop Share Risk Group)

136. Aggregated and Disaggregated view (WSS-WSS) Direction 2

137. Aggregated and disaggregated view (Filter) Direction 1
Filter architecture
Like a 200GHz AWG

138. Aggregated and disaggregated view (Filter) Direction 2

139. FC contain FC with different LPN
From a FC perspective, an FC could contain FCs. Since it is a passband defined by a filter (static), we could add FC that define passband associated to service media channel (inner media channel)
Service MC is a client of Band FC defined by the fixe filter

140. Aggregated and disaggregated view (Filter) Direction 1 Alternate View
Separate the Service MC Pool to follow the filter definition
Add the FC at the service media Channel
Could not contain FC Spec that define attenuation because the Filter FC define the attenuation

141. Aggregated and disaggregated view (Filter) Direction 2 Alternate View
Separate the Service MC Pool to follow the filter definition

142. OMS and OTS with FC
Expansion Of OMS and OTS

144. Layer model