Open APIs

 View Only

  • 1.  Activiate eSIM - resource relationship

    Posted Oct 03, 2023 10:49

    Hi,

    There is a use case to activiate eSIM by replacing existing sim/eSIM, or moving eSIM from 1 device to another device.  I would like to understand the resource relationship in TMF702 Resource Activation.

    Consumer sends (1) original SIM/eSIM's ICCID, (2) original SIM/eSIM's device eid (3) target device eid, (4) target device IMEI, 

    Is this the correct relationship type for the resources?

    {
      "description": "activiateICCID",
      "resourceRelationship": [
        {
          "relationshipType": "targets",
          "resource": {
            "id": "<Target_EID>",
            "@type": "EID",
        },
    {
          "relationshipType": "targets",
          "resource": {
            "id": "<Target_IMEI>",
            "@type": "IMEI",
        },
        {
          "relationshipType": "reliesOn",
          "resource": {
            "id": "<Source_EID>",
            "@type": "EID",
        },
    {
          "relationshipType": "reliesOn",
          "resource": {
            "id": "<Source_ICCID>",
            "@type": "ICCID",
        },
      ],
      "@type": "ICCID", 
      "@baseType": "Resource"
    }



    ------------------------------
    Keven Chan
    Rogers Communications Inc.
    ------------------------------


  • 2.  RE: Activiate eSIM - resource relationship

    Posted Oct 11, 2023 14:44

    Hi team,

    Any help or feedback is appreciated thanks!



    ------------------------------
    Keven Chan
    Rogers Communications Inc.
    ------------------------------



  • 3.  RE: Activiate eSIM - resource relationship

    Posted Oct 15, 2023 04:35

    Hi Keven,

    Here is some hints may help :

    In the TMF702 Resource Activation and Configuration Management, the relationship between resources plays a crucial role. The relationship type you've provided seems to indicate the transition of a SIM/eSIM from one device to another.

    Here's a breakdown of the relationships you've described:

    1. targets: This relationship type implies that the action or configuration is aimed at the specified resource. In this case, you're targeting the new device's EID (Embedded SIM ID) and IMEI (International Mobile Equipment Identity) for activation.

    2. reliesOn: This relationship type suggests a dependency. The activation of the new device or eSIM relies on the original device's EID and the original SIM/eSIM's ICCID (Integrated Circuit Card ID).

    Given the use case you described, the relationship seems appropriate:

    • The activation process targets the new device's EID and IMEI because you're aiming to activate the eSIM on this new device.

    • The activation process reliesOn the original device's EID and ICCID because these are the source resources from which the eSIM is being transitioned.

    However, one thing to consider is the order and the semantics of the relationships. Depending on the exact requirements and nuances of the TMF702 specification and your use case, you might need to refine the relationships further. For instance:

    • If the process requires deactivation of the original SIM/eSIM before activation on the new device, you might need additional relationship types or states to represent this.

    • Consideration on the state transitions (e.g., from 'inactive' to 'active') might be needed to capture the full lifecycle of the SIM/eSIM activation process.

    It's always a good idea to refer back to the TMF702 specification and possibly consult with a domain expert to ensure that the relationships and resource types are modeled correctly for your specific use case.

    Regards



    ------------------------------
    Mehmet Beyaz
    TTG Uluslararsi LTD
    ------------------------------

    Original Message


Related Content