...
- 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 for third party domain via federation
- Substitutes multiple handovers between parties/teams and applications to enable zero touch automation
BUSINESS DRIVER
...
Product Modeling and Distribution:
Work Flows:
This sequence diagram depicts external catalog sync into SDC followed by order request from BSS
The flow steps
...
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
...
- Onboard the service in ONAP SDC as a Service, will require updates to Service onboarding API (proposed)
Sample payload
Possible Approaches for 3rd Party Catalog payload Option
...
- Leveraging existing approach for Ext API / NBI
- ExtAPI / NBI will send the JSON in SDC compatible format for its Consumption in v1/catalog/services
Sample payload
Structure of SDC generated TOSCA CSAR
Payload Option 12: CSAR
- Potential reuse from TOSCA onboarding Project in SDC
- This might alter existing Ext API / NBI approach
- There would be additional implementation at Third Party end to generate higher level TOSCA
...