Project materials can be found here...

Proposal 

Name of Use Case:

...

Use Case Authors:

Telstra

Description:

BUSINESS DRIVER (Third Party Operational Domain Manager)

This section describes Business Drivers for this Use Case.

Executive Summary - 

• The Third party domain manager provides a standards-based approach that supports on-boarding third party domains and third party service management.

  
  

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

• It provides consistent way of consuming third party services from the Service provider and orchestration being conducted by the third party within its domain

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

• It substitutes multiple handovers between parties/teams and applications to enable zero touch automation

Business Impact - The use case provides a generic ability for seamlessly on-boarding partner domain catalog which can be leveraged by service providers using ONAP. Lack of this capability leads to manual creation of partner service catalogs which is time consuming and dependent on human intervention. With this capability, the partner catalogs will be available for placing orders for Partner Domain services very quickly. The future phase of this use case also plans to look at enhancing the operational domain manager capabilities for life cycle management and also managing assurance events  triggered by the third party service and execute remediation response.

Business Markets - 

• Following can be potential candidates for Third Party (or Partner) Domains which can be managed by ONAP:

  1. National Broadband Network (NBN) [Ref: https://www.nbnco.com.au/] Fixed Broadband Service,
  2. Managed Network Service from Service Providers
  3. Telco peers
  4. Multiple Cloud Service Providers to support a hybrid cloud ecosystem of private and public clouds
  5. Etc.
• This use case is also relevant to Single Operator environment (e.g. If an operator wants to move its catalog from test to production, it can use this import catalog capability to on board the catalog, without manually recreating it in the production ONAP instance.
  

Funding/Financial Impacts -

• This use case capability, once developed, can be used by any service provider deploying and using ONAP.  
• Third Party Domain manger will play a significant role in on-boarding partner domains in a uniform manner.
• The Service Catalog of the Partner Domain will be made available to the Service Provider in few hours, consumable via an abstraction layer (NaaS in Telstra context). 
  
• Once catalog is on-boarded ONAP can publish the Service details to BSS and it can be used for ordering Partner Domain services by the Service Provider.

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

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>

...