Open APIs

Hi,

How would you implement the process of enabling/registering of a new prepaid product/subscription?

The subscription is pre-provisioned and present in the product inventory prior to a customer buying a starter package with sim in a store. When the customer uses the simcard the first time, she is connected to customer support in order to register/validate her identity. After this step, she can continue using the subscription freely.

Our proposal is to support this by first creating (or locating) the party in Party Management, then do a patch of the product in Product Inventory with a reference to the related party (with role user).

Does this sound reasonable, or is there any other TMF API operation(s) available that could facilitate this registration/activation process?

Thank you,

Paul Austdal

------------------------------
Paul Austdal
Telia Company
------------------------------

On Sep 07, 2021 03:04 @Paul Austdal wrote:
​} How would you implement the process of enabling/registering of a new prepaid product/subscription?

Did you consider the lifecycle management in TMF637?  You might keep the Product in Pending Active state until identity registration is complete. Maybe that conflicts with order management?

Either way changes need to occur in the Production block so that she is no longer redirected to customer service. You might have a Service characteristic for redirect.

------------------------------
Vance Shipley
SigScale
------------------------------

Hi Paul
An interesting one, this. Probably the best approach would be to draw out some sequence diagrams showing the flows at the various phases of this pre-activation:

• Setting up the initial supply/delivery of the SIMs and correlating the IMSIs with the corresponding MSISDN (presumably some batch process)
• Setting up the pre-provisioning so that the mobile product is placed into the inventory (but not associated with a customer, or perhaps creating a dummy customer for each product) and doing the magic in the network (HLR/HSS/5G).
• First call, this would presumably result in a Product Order to coordinate the changes in the Product to assign to the customer, collect customer details, etc.

Would be valuable to hear from @Ludovic Robert, and maybe also the ODA use cases team headed by @Sylvie Demarest, for their views on these flows.

​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Original Message:
Sent: Sep 08, 2021 01:04
From: Vance Shipley
Subject: Registering/enabling a new prepaid product/subscription

On Sep 07, 2021 03:04 @Paul Austdal wrote:
​} How would you implement the process of enabling/registering of a new prepaid product/subscription?

Did you consider the lifecycle management in TMF637?  You might keep the Product in Pending Active state until identity registration is complete. Maybe that conflicts with order management?

Either way changes need to occur in the Production block so that she is no longer redirected to customer service. You might have a Service characteristic for redirect.

------------------------------
Vance Shipley
SigScale
------------------------------

Hello,

to complement suggestions from @Jonathan Goldberg (ODA use case) and @Vance Shipley (TMF637) use case #8 is as good as it gets. It's postpaid but hopefully good enough!​​


------------------------------
Matthieu Hattab
Altibox AS
------------------------------

Original Message:
Sent: Sep 12, 2021 09:52
From: Jonathan Goldberg
Subject: Registering/enabling a new prepaid product/subscription

Hi Paul
An interesting one, this. Probably the best approach would be to draw out some sequence diagrams showing the flows at the various phases of this pre-activation:

• Setting up the initial supply/delivery of the SIMs and correlating the IMSIs with the corresponding MSISDN (presumably some batch process)
• Setting up the pre-provisioning so that the mobile product is placed into the inventory (but not associated with a customer, or perhaps creating a dummy customer for each product) and doing the magic in the network (HLR/HSS/5G).
• First call, this would presumably result in a Product Order to coordinate the changes in the Product to assign to the customer, collect customer details, etc.

Would be valuable to hear from @Ludovic Robert, and maybe also the ODA use cases team headed by @Sylvie Demarest, for their views on these flows.

​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------


Original Message:
Sent: Sep 08, 2021 01:04
From: Vance Shipley
Subject: Registering/enabling a new prepaid product/subscription

On Sep 07, 2021 03:04 @Paul Austdal wrote:
​} How would you implement the process of enabling/registering of a new prepaid product/subscription?

Did you consider the lifecycle management in TMF637?  You might keep the Product in Pending Active state until identity registration is complete. Maybe that conflicts with order management?

Either way changes need to occur in the Production block so that she is no longer redirected to customer service. You might have a Service characteristic for redirect.

------------------------------
Vance Shipley
SigScale