Service Activation

Contents

Overview

As part of the purchase of an over-the-top (OTT) digital service, MarketONE delivers a pre-built process that consists in capturing the customer request, confirming the purchase, enabling service monetization, and the entitlement of the user for the service. If it is required, a provisioning integration request can also be sent to the OTT provider backend for the MarketONE user.

Supported Capabilities

MarketONE user orchestration is delivered as part of the MarketONE User Management (ULM) domain. The ULM process engine contains pre-built processes that capture the purchase and then orchestrate the subscription activation in the MarketONE Subscription Management (SLM) domain. Service activation is performed via the MarketONE Partner Management (PLM) domain. The ULM domain also integrates with the other BSS systems (if needed) to hand off the request for any fulfillment required. The ULM domain maintains the entitlements of the end user to the services purchased, as well as allowing the user to share their services with other members of the household and family (within the restrictions of the services). While the ULM domain orchestrates the entire experience, the subscription lifecycle management is maintained in the SLM domain and the provisioning of the service at the OTT provider backend is done via the PLM domain. The PLM domain maintains the integration with the OTT and keeps them in sync in case the interfaces are updated by either party.

The following service activation scenarios are supported by MarketONE:

  • Creating a new active user on the OTT via OTT integration.
  • Creating a new active user on the OTT website via deep linking.
  • Associating an existing user account on the OTT service to the new payment method at the time of purchase.
  • Disconnecting or canceling a subscriber on the OTT service.

Most of the integrations are done between the PLM domain and the OTT applications and systems using standard published APIs. However, in cases where the size of the OTT warrants integration to their specific APIs, modifications to the the PLM domain integration layer can be made to make the experience as seamless as possible.

Recommended Experience

User Orchestration

The ULM domain has pre-built processes that deliver end-to-end experiences from onboarding a user, associating an account, provisioning a service, delegating, sharing, and managing consent. These processes are leveraged by the MarketONE digital store when the user selects an action. The ULM domain then orchestrates the process, and with the pre-integration into the PLM domain and the SLM domain, it manages the entire lifecycle of the process. In cases where the user action necessitates an orchestration or an activity on the legacy BSS, the ULM domain can be integrated into the legacy BSS as well. The details of the integration to the legacy stack will be dependent on the specific customer and the use cases. Components which are part of MarketONE should be orchestrated by the ULM domain alone to leverage the best practices and integrations out-of-the-box (OOTB).

Service Activation

Service activation into the OTT backend is managed by the PLM domain. The ULM domain makes the request into the PLM domain at the specific step of the process where OTT activation is needed, and based on the OOTB integrations between the PLM domain and the OTT backend, the service is activated. The PLM domain comes with a prescriptive set of APIs which can be used for the integration with the OTT backend. These APIs range from creating the OTT product, initiating a payment transaction, and creating and associating a user account into the OTT backend application.

It is recommended that most OTTs leverage the OOTB MarketONE APIs for integration into the platform. These APIs are available as part of a software development kit (SDK) which can be consumed by the OTT and can be integrated into the ecosystem. Leveraging these APIs will not only yield to faster onboarding, but also to extending the reach of the OTTs to the broader set of customers on the Amdocs MarketONE platform.

In certain cases Amdocs will support changes to the PLM domain (for large digital OTTs like Netflix and Spotify). It is important to note however, that while changes to the APIs can be done, the end-to-end experience has to be consistent based on the APIs exposed by MarketONE to ensure a frictionless end user engagement.

Revision History

Version Description
2020.03 Added this topic.