1. CMCC Laboratory test of SOTN Northbound interface based on TAPI 2.0

2. Orchestrator(ONAP based)
The SDN based transport network in China Mobile
Orchestrator(ONAP based)
APPs for customer
APPs for operator
Resources
management
Performance
management
fault
management
Possible positions of TAPI 2.0
TAPI like interface defined by CMCC ②
Control Plane
SOTN S-Controller
SPTN S-Controller ①
Backbone OTN
D-Controller
Metro OTN
D-Controller
Backbone PTN
D-Controller/OMC
Metro PTN
D-Controller/OMC
Access PTN
D-Controller/OMC
South bound interface
Enterprise
Leased line
SPTN
SOTN
Vendor C
Access
PTN
Vendor A
Backbone
PTN
Vendor B
Metro
PTN
Vendor A
Backbone
OTN
Vendor B
Metro
OTN
LTE backhaul

3. CMCC Laboratory test Configuration
Super Controller
（CMCC/CAICT）
DCN（out-of-band）
Domain Controller A
Domain Controller B
OTU2/
STM-64
OTU2/
STM-64/
10GE
OTN/SDH Instrument
NE1
NE2
NE1
NE2
OTU4 Gray Interface
ETH Data Instrument
10GE
NE5
NNI
NE5
OTU4 Gray Interface
Opto electric hybrid cross OTN device
NNI
NE3
NE4
NE3
NE4

4. CMCC Laboratory test items
No.
Test items
Test result 1 
Multi-domain topology and resources management
Network topology query and collection
pass 2 
Network topology update 3 
Multi-domain route compute function
Multi-domain route compute 4 
Include and exclude specific network resources 5 
Route optimization objective 6 
Multi-domain connectivity management function
End-to-end connection creation and deletion
10GE CBR/STM-64/OTU2 7 
EPL/EVPL 8 
EP-LAN/EVP-LAN 9 
Service bandwidth adjustment
Bandwidth adjustment
10 
Service SLA adjustment
No-protection to Dynamic restoration
11 
No-protection to end-to-end 1plus1
12 
Scheduled reservation service
13 
Multi-domain protection and restoration function
Per-domain restoration
Permanent 1plus1
14 
1plus1 with Restoration
15 
Pre-calculation Restoration
16 
Dynamic restoration
17 
End-to-end restoration
End-to-end 1plus1
18 
End-to-end dynamic restoration
19 
Electro-Optical coordination
Create service to drive optical and electric layer pipeline establishment

5. Topology abstraction and query
Each ETH UNI port, ODU UNI port and inter-domain ODU NNI port associated with a SIP SC DC
Super Controller
（CMCC/CAICT）
getTopologyList{}
ETH1
200ok: Topology{
eth-node,
odu-node,
och-node,
eth-odu-transitional-link,
odu-och-transitional-link}
NBI
ETH-ODU transitional link
{from multi ETH UNI port to one ODU NEP}
Node of each layer
Inter-layer link
Domain Controller A
ODU1
NNI
getTopologyDetails{eth-node.uuid}
200ok
getTopologyDetails{odu-node.uuid}
NE1
NE2
200ok
NNI
Topo、node
getTopologyDetails{och-node.uuid}
OCH1
NE5
200ok
NEP
Inner-layer node and link
Link
SIP
Topology query sequence
Transitional link
NE3
NE4

6. L2 switch Ethernet serviceSC DC
createConnectivityService{ETH.SIP1, ODU.SIP2}
200ok:
service{uuid, [connection.uuid1…..]}
IncludeETH connection.uuid , the ODU connection.uuid and the OCh connection.uuid
getConnectionDetails{ODU.connection.uuid}
200ok:
ODU connection with the route ,which include the list of CEP.uuid
getConnectionEndPointOfRoute{route.uuid}
200ok:
The route details, which include the list of CEP,
indicate the TS-detail in the route-hop
Service creation sequence
The ODUk, EPL/EVPL, EP-LAN/EVP-LAN service use same sequence, with different parameters..
Type
LayerPorotcolName
ServiceType
IsExclusiveService
ODUk
ODU
P2P
true
EPL
ETH
EVPL
MP2MP
false
EP-LAN
EVP-LAN
How to set the vlan id, vlan type{C-TAG, S-TAG}, vlan action{PUSH, POP} should be defined in the TAPI 2.0.

7. Scheduled reservation service
Super Controller
（CMCC/CAICT）
SC sends the service creation request with Scheduled information
DCN（out-of-band）
Domain Controller A
Domain Controller A
The SC and DC should be time synchronized in order to create and delete the connection at the same time.
If there is requirements for the time synchronization information to be defined in the TAPI 2.0.

8. Service bandwidth and SLA modification
Use the updateConnectivityService interface for the bandwidth and SLA modification.
No-protection to 1plus1
Bandwidth adjustment
No-protection to Dynamic-restoration
updateConnectivityService{
Service uuid,
Modification type,
Requested bandwidth}
updateConnectivityService{
Service uuid,
Modification type,
Modified resilience type}
updateConnectivityService{
Service uuid,
Modification type,
Modified resilience type,
Port and TS-detail in protection route}

9. Multi-domain service restoration policy
If the SC send the policy to DC
When the inner-link fault is occurred, the DC know if the restoration is triggered by the DC or by the SC SC SC DC DC DC DC
Per-domain-restoration
End-to-end restoration

10. Multi-domain restoration test result
updateService{}
Alarm-notify SC
DC1
DC2
updateService{}
Alarm-notify
Alarm.perceivedServityType=Critical
SC send updateConnectivityService to DC1 and DC2,
Service restore the backup route.
Alarm.perceivedServityType=Cleared
Service revert to the nominal route.
Link fault location
Restore time
Inner-domin
104ms~997ms
Inter-domin
2.9s

11. Summary and suggestions
TAPI 2.0 is used in the lab test, the basic functions work well
The interoperation test between different vendors’ systems with TAPI look good
We hope TAPI 2.0 can be compliant with the information model with PTN which defined by CMCC.
Some new functions such as S-Vlan and C-Vlan is needed
The interface to control ROADM can be considered