Glad you were able to answer your own question Erlina - definitely product order for the customer-facing aspects. Additional use case could be purchase of an eSIM for travel (instead of buying a roaming package).
But behind the scenes you need to consider which component will orchestrate this eSIM swap process, including the resource inventory update (TMF639). And where does the eSIM "come from" - Resource Pool, Resource Reservation.
------------------------------
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: Nov 09, 2022 03:13
From: Erlina Hennies
Subject: eSIM-Card Exchange (affect which APIs: TMF 622, 637, 639, 652?)
Ok, as we will implement it soon in the next sprint, we have decided to choose the POM, due to the next action of business processes that can conclude an exchange of eSim, such as TarifChange, etc. It can also be a family tarif is booked (in a accordance of eg. tariff change, new acquisition etc) then the so called TNV (Teilnehmerverhältnis / defined participation of the sim cards) that is defined by changing an eSim. (it will go all the way to the back ends of the current eco systems of mobile business). The sim card it self is of course part of inventory i.e. RessourceInventory must be also updated - if the service API is offered.
Thank you for some Telekoms Colleagues who gave me also some input and help as well as valuable discussions!
------------------------------
Erlina Hennies
Deutsche Telekom AG
------------------------------