I think we can say that an implemented eSIM is a LogicalResource. So if you represent the eSIM in your resource inventory, then TMF639 will work for you. But actual activation/provisioning would presumably be done via TMF702, resource activation/configuration.
Hope it helps
------------------------------
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: Jul 04, 2023 07:53
From: Caui Leal
Subject: eSIM Architecture (SM-DP+ Integration) (Download com Confirm Order)
Imagine that I have a scenario which a system, can be a ordering or a activation system, need to integrate to a component that will abstract the complexity of many SM-DP+ systems of any vendor and will expose a Allocate and Install operation to provide a allocation profile function and ocupation profile function. Therefore, after a mobile plan and a eSIM have been sold my fulfillment system or a ordering system will integrate to that component (little eSIM Manager) to perform Allocate Profile and Install Profile, besides a amount of other fulfillment steps. Based on that scenario, my question is, which TMF should that component exposed? I'm prone to use TMF 639, because for me profiles can be handle as resources. However, I couldn't found any reference architecture handling that point.
#CustomerExperience
#DigitalEcosystems
#DigitalTransformationMaturity
#IoTandSmartCity
#OpenDigitalArchitecture
#General
------------------------------
Caui Leal
Telefonica Brasil S.A.
------------------------------