Project materials can be found here...
Proposal
Name of Use Case:
Third Party Operational Domain Manager
Use Case Authors:
Telstra
Description:
A
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:
- National Broadband Network (NBN) [Ref: https://www.nbnco.com.au/] Fixed Broadband Service,
- Managed Network Service from Service Providers
- Telco peers
- Multiple Cloud Service Providers to support a hybrid cloud ecosystem of private and public clouds
- 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 and orchestration being conducted by the 3rd party within its domain
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:
...
- 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>
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
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
The flow steps
Catalog Sync Summary
1 – External Third party domain exports it service catalog details to Telstra. Telstra orchestrator ONAP exposes TMF Open API 633 Service Catalog API via ONAP Ext API component. Third Party Domain leverages the API 633 to POST the Service Catalog payload.
...
4 – BSS/NaaS retrieves Service catalog details from ONAP
Order Activation Summary
5 – BSS submit order using TMF 641 Service Ordering API, that is exposed by ONAP Ext API
...
Sequence Diagram for 3rd Party Catalog Sync – with Payload Detail
Sub Use Case 2 (planned for
...
G release)
Automated VNF Life Cycle Management – to cater for change management, incident management and version/configuration management
...
- 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
...
A&AI (change to A&AI will be analyzed as part of next phase of the use-case, for cross domain inventory management)
Work Commitment:
Telstra team will work on SDC and Ext API changes. We welcome partner contributions into this usecase.
...