Project materials can be found here
Name of Use Case: Third Party Operational Domain Manager
Participants : Telstra
Description:
- A standards-based approach that allows a service provider to have a network automation platform for composite or white labelled services managed by specific/ Third Party “ domain managers
- ONAP provides Operations Domain Management (ODM) and other complementary capabilities to ensure full automation of the E2E lifecycle management of the service via federation
- Services are exposed and consumed via Network as a Service (NaaS) w”hich is an abstraction layer above the operational domains and exposes the services to BSS
- Consistent way of consuming 3rd party services for service providers like Telstra
- ONAP will facilitate service operations value chain across C2M, P2O, O2A, T2R for third party domain via federation
- Substitutes multiple handovers between parties/teams and applications to enable zero touch automation
BUSINESS DRIVER
This section describes Business Drivers for this Use Case.
Executive Summary - This use case will provide ONAP capability to be operational domain manager for third party services. Service providers will be able to use ONAP to provide end to end automation for composite or white labelled services which could be provided and managed by third parties. This use case will enable federated catalog and orchestration management. In case of Tier 1 / Brownfield operators, it’s likely that ONAP might need to interface with existing automation solutions for specific domains.
Business Impact The use case provides a generic capability in ONAP for seamlessly on-boarding services from partner (or specific ) domain catalog. Lack of this capability leads to manual creation of partner services in ONAP which is time consuming and error prone. With introduction of this capability, ONAP will be able to consume domain specific service definitions via Open APIs and publish the same to run time components. Next phase of this use case will extend the operational domain manager capabilities to support complete entire service operations value chain (across C2M, P2O, O2A, T2R) for “Third Party” or Domain specific services via federation.
Business Markets - Following can be potential candidates for Third Party (or Partner) Domains which can be managed by ONAP.
- Fixed Broadband Service,
- Managed Network Service from other Service Providers (Telco Peers)
- Hybrid cloud ecosystem of private and public clouds from Multiple Cloud Service Providers
- A special case could be composite in house services which include service components managed by a existing domain manager
This use case is also relevant to Single Operator (Single Domain Manager ) environment (e.g. If an operator wants to move its catalog from test to production )
This will be very relevant for automation of digital services delivered via diverse 5G Ecosystem (B2B2X Models) for vertical industry solutions
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.
All this will essentially bring down time to market significantly for partner services.
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.
PNF/VNF : Preference will be to use Fixed Broadband Access Service and associated network functions as reference for this use case. Clearwater IMS will be the backup option
Work Flows:
The use case is being divided into sub use cases in order to limit the scope of changes for F 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.
POST nbi/api/v3/serviceSpecification
Request body –ONAP compatible Service CSAR / (json ??)
CSAR contents:
RFSS for Partner Domain Service
2 – ONAP Ext API updates SDC catalog by invoking internal SDC API
POST sdc/v2/catalog/services
3 – Ext API notifies Third party after successful update within ONAP
4 – Service Decomposition happens in SDC (any manual updates e.g. creating composite service)
SDC updates other ONAP components (which have registered with SDC DMaaP) with catalog details
5a – SO pulls SDC catalog details
5b – AAI pulls inventory details
Ext API also notifies northbound systems (BSS/NaaS) after successful import of the service catalog into ONAP.
5c - BSS retrieves catalog information from ONAP
Order Activation Summary
6 – BSS submit order using TMF 641 Service Ordering API, that is exposed by ONAP Ext API
7 – ONAP Ext API submits the request to ONAP SO
8 – ONAP SO decomposes the service and submits the request by invoking Ext API (This is similar to what is being proposed for CCVPN use case as well. This maintains that only Ext API interacts with outside world and other ONAP components do not)
9 – ONAP Ext API invokes the Third Party Ordering API
Sub Use Case 1 (targeted for F Release)
Import Service Catalog
Below sequence diagrams are depicting the Catalog Sync functionality in more detail:
High level flow of the activities for importing an external Service Catalog into ONAP with Payload Detail
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 (yet to be analyzed and scoped)
Work Commitment:
Telstra team will work on SDC. We welcome partner contributions into this usecase.
The details of changes are being discussed with the PTLs