Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 6 Next »

Project materials can be found here...

Proposal 

Name of Use Case:

Third Party Operational Domain Manager

Use Case Authors:

Telstra

Description:

ONAP ODM in the ecosystem


A standards-based approach that supports on-boarding third party domains and third party service management.

Following can be potential candidates for Third Party Domains which can be managed by ONAP:

  • NBN Fixed Broadband Service,
  • Managed Network Service
  • Telco peers
  • Multiple Cloud Service Providers
  • Etc.


ONAP provides Operations Domain Management (ODM) and other complementary capabilities to ensure full automation of the E2E life-cycle management of the service

Services are exposed and consumable via common gateway depicted as Network as a Service (NaaS) layer in figure above.

Consistent way of consuming 3rd party services from the Service provider

LCM and assurance events are triggered by the 3rd party service, and remediation response are executed.

Substitutes multiple handovers between parties/teams and applications to enable zero touch automation

 

Users and Benefit:

Beneficiaries – Third Party Domains

Third Party Domain manger will play a significant role in on-boarding partner domains.

The Service Catalog of the Partner Domain will be made available to the Service Provider in few hours.

Once catalog is on-boarded ONAP can publish the Service details to BSS and it can be used for ordering Partner Domain services.


VNF:

TBD

< list the VNFs this use case will automate/impact/use, be both generic like EPC and specific in terms of software used e.g. which EPC code or vendor product>


Work Flows:

The use case is being divided into sub use cases in order to limit the scope of changes for E release.

Sub Use Case 1 (targeted for E Release)

Import Service Catalog

Submit Order

Instantiation of VNF

Interaction Flow

  • Third Party Catalog import
  • Publish Catalog
  • Submit an O2A order
  • Fulfill the order

This sequence diagram depicts external catalog sync into SDC followed by order request from BSS


High level flow of the activities for the importing an external Service Catalog into ONAP


Sub Use Case 2 (planned for F release)

VNF Life Cycle Management

Service Assurance for Third Party Domains

Control Automation:

Following items for VNF LCM and Service Assurance for Third Party Domain are being considered for the next phase of the use case for F release

  • The service life cycle management action can trigger for:
    • CM: change management (capacity increase to meet scaling demands);
    • IM: incident management (problem identification and fix); and
    • VM: version/config. management (VNFs’ adaptation to topology/config changes during run time of the service)
  • Remediation actions are executed automatically using ONAP as ODM


Project Impact:

Projects impacted as part of sub use case 1

  • SDC
    • In order to import the Service Catalog, Service load will have to be sent to SDC from Ext API.
    • JSON representation of the Service load needs to be identified and agreed with SDC team
  • Ext API
    • TMF 633 POST needs to be implemented in Ext API
    • Invoking the Third party Ordering API

Work Commitment:

Telstra team will work on SDC and Ext API changes.

The details of changes are being discussed with the PTLs






  • No labels