Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • A standards-based approach that supports third party service managementallows a service provider to have a automation platform for composite or white labelled services managed by specific domain managers
    • Fixed Broadband Access Service from third party
    • 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 lifecycle management of the service
  • Services are exposed and consumable via Network as a Service (NaaS) which is an abstraction layer above the operational domains and exposes the services to BSS
  • Consistent way of consuming 3rd party services from Service Providers
  • 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

...

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 provide ONAP capability to support 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 ability capability in ONAP for seamlessly on-boarding partner boarding services from partner (or specific ) domain catalog which can be leveraged by service providers using ONAP. Lack of this capability leads to manual creation of partner service catalogs services in ONAP which is time consuming and dependent on human interventionerror prone. With introduction of this capability, the partner catalogs will be available for placing orders for Partner Domain services very quickly. The future 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 also plans to look at enhancing will extend the operational domain manager capabilities for life cycle management and also managing assurance events  triggered by the third party service and execute remediation responseto 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

...

.

  • National Broadband Network (NBN) [Ref: https://www.nbnco.com.au/] Fixed Broadband Service,
  • Managed Network Service from other Service Providers (Telco peersMultiple Cloud Service Providers to support a hybrid Peers)
  • Hybrid cloud ecosystem of private and public clouds Etc.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 -

...