Use Case Authors:
China Mobile, Huawei, VDF
NOTE: More participants are welcome.
Description:
Business Driver:
It is CMCC's strategy to realize big connection and provide a high-speed, flexible and intelligent service for high-value customers. Furthermore, CMCC also plans to provide instant, flexible VPN service for SMB companies.
The current SOTN has some obvious disadvantages, such as:
- Manual labor is highly needed in service scheduling and resource maintenance which is time-consuming and costly.
- With the high demand for large bandwidth in private line, the expansion to OTN is required. The network needs to be reconstructed under this condition.
- There is no bridge or platform to connect different service providers.
Also, there are urgent demands for:
- Real-time resource update.
- OTN equipment operation and scheduling for different vendors.
- Multi-constrained end-to-end route computation.
- Multi-domain end-to-end service providing.
- Multi-domain network end-to-end survivability.
- Supply SMB companies with VPN service on demand, instantly, flexibly
- Deploy VPN service by overlay mode , untouch carrier network
- “One-click open”and “One-stop”, automatically deploy enterprise VPN service
- Self-service order for client-side CPE, self-delivery client-side CPE
- Provide various value-added service on client-side SD-CPE and cloud side
Considering the above aspects, we plan to make a combination of SOTN and ONAP in virtue of the strong orchestration ability of ONAP, which is called CCVPN(Cross Domain and Cross Layer VPN), to realize a unified management and scheduling of resource and services, and also to deploy services automatically. OTN super controller can be realized as a module of ONAP(SDN-C). In this way, multi-domain cooperation is achieved as well as resource and service automatically providing.
In this use case, our focus is not only restricted to resource, but also services from end to end. Scenarios includes 'SOTN only', SD-VAN and international private line. But at present, 'SOTN only' is at our 1 priority, which is called Phase1 in the following.
Three phases in the whole plan:
- PHASE1: Combine SOTN with ONAP, to manage and orchestrate services automatically.
- PHASE2: Take both SOTN and SD-VAN into account, and combine them with ONAP.
- PHASE3: Build up the international private line, to realize the connection between ONAPs.
Specific sub-use cases are:
- Service onboarding
- Service configuration
- Service termination
- Auto-scaling based on fault and performance (stretch goal)
- fault detection and auto-healing (stretch goal)
- data correlation and analytics (stretch goal)
Topology Diagram
Work Flows(TBD)
Workflow in Phase1:
Brief description:
After the ONAP brought in, users can forward client service via a unified customer self-service portal. ONAP orchestrator will send out channel built request to SOTN Controller after checking the service request and OTN resource state. Then a private channel is built. Domain controller will finish resource configuration on the basis of ONAP request.
Platform Requirements
PNF Onboard (abstract topology)
Deploy Artifacts for physical network
Cross-Operators interwork (MEF etc.)
Tenant management
Project Impact
PHASE1:
- SDC - PNF resource onboarding, new resource type for OTN VPN network (L1-L2), site Design support (link to tenant etc.)
- SO/OOF - service orchestration & homing based on abstract topology
- SDNC - integrated with 3rdcontroller, New DG for provision to site & VPN network, sync abstractor topology into A&AI
- UUI - E2E service provision(need support for tenant & site)
- A&AI - DM for PNF, support for abstract topology & tenant
- ESR - external controller?OTN controller in phase 1?
PHASE2+:
- ESR - SD WAN controller & external OSS?inventory etc.?
- External API - cross operator’s service interwork
- Policy/DCAE- E2E close-Loop for cross domain service
- VF-C/APP-C - VNF deployment & management when need