You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Use Case Authors:

China Mobile, Huawei, VDF

NOTE: More participants are welcome.


Description:

The current SOTN(Software Optical Transport Network) has some obvious disadvantages:

  • 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.

Considering the above aspects and the advantages of ONAP, we want to explore the combination of ONAP with Cross Domain and Cross Layer VPN.

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

Priorities (TBD)

Work Commitment

  • No labels