PLM Domain Functional Overview

Contents

• Overview
• Partner Relationship Management (PRM)
• Partner Integration Hub (PIH)
• Revision History

Overview

The following architectural diagram shows how the Partner Relationship Management (PRM) and the Partner Integration Hub (PIH) components are functionally integrated into the MarketONE PLM domain. The PRM component contains a User Interface. This interface consists, in part, in the CSP Admin UI and the Partner Self Care UI. Both of these UIs can be used to look at the components that make up Partner Onboarding and Settlements (this includes products, contracts, agreements, settlement rules, revenue settlements, reconciliation, settlement reports, and financial reports).

In turn, the PIH component contains two sets of integrations: integrations to the over-the-top (OTT) providers, and integrations to the communications service provider (CSP) or the operator downstream backend. Some of these backend systems will be components of the MarketONE platform, while others may not be since they may choose to use a different identity system and a different billing platform.

Partner Relationship Management (PRM)

The partner management component is used to maintain the configuration components of MarketONE. In particular, it manages the creation of products that an OTT offers. Consider the following example. In the case of Netflix, they may offer the following two plans: an individual plan and a family plan. These two plans are two separate products. All of the agreements, and contracts, and revenue shares, and the settlement of transactions that are part of these products are created and managed using the partner management component. When a transaction comes in the partner management component directs the transaction into the right partner code, and then splits the charges into the one that is the agreement for OTTs, and the one that is the agreement for operators based on the actual contract that exists. Anything that has to do with the creation of products, the creation of OTTs, settlements, and financial settlements between the two entities of the operator and the OTT, are done using the partner management component.

Partner Integration Hub (PIH)

The partner integration hub component is used for backend integrations. In particular, it has northbound integrations to all of the OTTs and southbound integrations to the operator's backend system. Northbound integrations (like when communication with the OTT is required to create the user, and when the OTT needs to call to validate an account), are processed with the APIs that are exposed to the OTT. The partner integration hub also has APIs that are used for the downstream applications (which is for the BSS systems).

To see how this is to the advantage of companies like NXT (for example), assume that twenty OTTs are pre-integrated into the MarketONE platform. The MarketONE solution that is offered to these companies already contains integrations to the OTTs (including settlement and provisioning), it functions as the user orchestration engine, and it does the subscription management for their services. And as far as subscriptions are concerned, subscription management will manage them for the customers of NXT, but not for customers of the OTT. This is so because they might be using their own subscription management system for services that are not billed through the operator (by using a credit card, for example).

Revision History

Version	Description
2019.08	Initial release.
2019.09	Updated the Amdocs PLM architecture diagram.
2019.12	Added Contents and Revision History sections.