Page History

...

Work Flows

Workflow in Phase1:

Image RemovedImage Added

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.

...

• SDC    – PNF resource onboarding (include: CPE and physical network which can provide MEF EPL service and can be designed as abstract resource)

  SO/OOF – service orchestration & homing based on abstract topology(for the physical network)

  SDNC - integrated with 3^rd controller, New DG for provision to CPE & physical network, sync abstractor topology for the physical network and store it into A&AI

  UUI      - E2E service provision(need support for tenant & site)

  A&AI    - DM  DM for PNF, DM for abstract topology of physical network, use travel query tor all resource related to special service

  ESR     - external controller?OTN controller in phase 1?, external inventory OSS to provide reference between physical location information and CPE or UNI/NNI of physical network, or external link between different physical network domain(stretch goal)

  DCAE   - collect the event data for MEF EPL service or from PNF.

  VF-C/APP-C –VNF deployment & management when need

• External APIs   - external controller?OTN controller in phase 1?, external inventory OSS to provide reference between physical location information and CPE or UNI/NNI of physical network, or external link between different physical network domain(stretch goal)

• Modeling       - the modeling for PNF and abstract topology for physical network

PHASE2+:

• ESR            - SD WAN controller & external OSS: inventory/order etc.
• External API - cross operator’s service interwork
• Policy           - E2E close-Loop for cross domain service

...

Attachments: