LTE Quick Reference                                   Go Back To Index    Home : www.sharetechnote.com

 

 

 

 

eSIM/Electronic SIM/Embedded SIM

 

This is called by many different names. Some say embedded SIM, some say Electronic SIM and other say eSIM. There would be other names coming out until the industry standard is finalized and adopted widely in the area. Whatever we call, the fundamental idea of this SIM is to distribute the SIM (UICC) as a non-removable/fixed component of a user device (e.g, M2M terminal, Mobile Phone etc). The device manufacturer program the SIM card to load different set of informations required by specific situation (e.g, location, network operator etc)

 

I will call this as eSIM throughout this page since 'e' can imply many different things(e.g, it can imply 'Electronic', 'Embedded' and even 'Enhanced').

 

 

Why eSIM ?

 

For some people especially who is working on modem development and device testing, it would sound like counter-intuitive evolution path because 'anything fixed/non-removable' may imply 'less flexibility and less controllability'. Then how come this kind of concept is getting more and more frequently talked about (as of Aug 2015).

In engineering, for anything coming out anew, there is some reason/motivation. What is the reason/motivation for this new concept of SIM ?

I think the biggest motivation is related to M2M/IoT devices.

  • Unlike the mobile phone (Smart Phone), most of the M2M/IoT device is not easily reacheable and even it is reacheable, you may not be able to easily decap and plug in SIM card. So a new idea came out to implement UICC as a fixed chipset attached to each device.  
  • If we implement it as a fixed chip to a device, we would come across a big problem. In most cases, you would not know exactly what kind of informated should be stored in the chip(SIM) by the time when the device is manufactured. You would not know which network operator the device is sold to and which location they are installed. So you have to make it programmable, so that we just program it depending on different requirement in stead of changing the SIM card.
  • There is some mechanical issues as well. The removable type of SIM would not be suitable for those product under consistent vibration like automobile or some industrial environment since the electrical contact of the removable card would not be as robust as eSIM card with soldered electrical contact
  • Another important motivation for eSIM card is cost issue. According to the report from GSMA the cost of the removable SIM card would be almost 10 times as high as eSIM card
  • Lastly we can think of logistic issues as well. Think of what you need to do when you want to bring your mobile phone into the area with no roaming or too expensive roaming. In that case you would need to order a local SIM card from a local operator and manually change the SIM card on your phone. Similar thing happens when you want to change the subscribing network operators as well. If you are in similar situation with the mobile connectivity in your car, the situation can be even more cumbersome. You would order a new SIM card and bring the car to the dealer shop just to replace SIM card. Automotive manufacturer would not allow you to change those card on your own due to possible electrical issues from inappropriate SIM card changes

In short, Anyway there seem to be many reasons for moving towards eSIM cards

Is it going to be used only for M2M device ? It doesn't seem to be restricted to M2M/IoT device only and there seems to be some trends towards adopting this technology to mobile phone as well. Read following articles.

 

 

How to program (provision) the SIM ?

 

Now the question is how you can load information (profile) into each eSIM card within the device ? The simplest idea is to implement a special programming port directly connected to the eSIM and electrically load the information into it, but the ideal (final goal) would be to load the information (profile) over the air (this is called 'Remote Provisioning').

 

The critical issues is how to design/implement a remote provisioning. Since this remote provisioning should be applicable to devices from various vendors and applicable to different network operators, there should be some international standard and very detailed procedures (protocols) should be defined. For now, GSMA is leading this activity. Even though the specification is not finalized yet (as of Aug 2015), you can have pretty detailed idea of Remote Provisioning process from GSMA document : Embedded SIM Remote Provisioning Architecture (Visit Reference [1] to find the document)

 

 

eUICC Architecture/Information Flow

 

Following is overall Architecture and Information flow modified from GSMA Technical Specification. (I just a couple of items below the dotted line. Everything above the dotted line is exactly same as in GSMA Technical Specification : Figure 1 in GSMA-Embedded-SIM-Remote-Provisioning-Architecture-Version-1.1).

 

Probably the most of the readers including myself are not very familiar with each of these entities for now (Aug 2015) and inter-relations of each of these entities are also quite complicated.  Most of the people would be interested (or involved) in only a couple of path shown here. I will just keep updating the descriptions of possible path combinations (interactions) among these entities as I learn along.

 

    Figure 1 : Functional Arichitecture of eSIM Operation

 

< Path Example 1 : (1), (2), (3) >

 

Probably this can be a kind of minimum functional flow.

First, SM-DP should get the necessary tools or services from EUM (eUICC Manufacturer) that is required to program the eUICC.

Next, SM-DP should get input data from MNO (Mobile Network Operator) that will be used to create a Profile (or Many Profiles) for the target eUICC. Some examples of the input data are as follows.

  • Quantity of Profiles to be created
  • IMSI Value(s) or Range
  • ICCID Value(s) or Range
  • Unpersonalized Profile Type(s)
  • Information about target eUICC(s), e.g, EID

 

 

How SM-SR communicate to eUICC ?

 

How SM-SR can communicate to eUICC ? This is the point that I am personally most interested in (You may be more interested in other parts). This communication is supposed to be over-the-air ? Then you might ask 'what kind of OTA technology' and which specific Radio message will be used to carry these information.

I think this should be determined by each MNO and each MNO would use different technology. GSMA Specification mentions of some of possibile mechanism as follows. (In Ref [1], the section A.2 MNO-SM-DP Interface describes as follows).

    All relavant known information on the Target eUICC and its SM-SR e.g:

    • The method to be supported by SM-SR to communicate with eUICC (e.g, support of SMS and/or RAM over HTTP(s) over LTE/EPS)

Once this OTA mechanism is determined, the higher level protocol is relatively clearly defined in the following sections in following sections of Ref [1]

  • 3.5.1 eUICC Registration at SM-SR
  • 3.5.3 Profile Ordering
  • 3.5.4 Profile Download and Installation
  • 3.5.5 Master Delete
  • 3.5.6 Profile Enabling
  • 3.5.7 Profile Enabling via SM-DP
  • 3.5.8 Profile Disabling
  • 3.5.9 ISD-P Deletion
  • 3.5.10 ISD-P Deletion via SM-DP
  • 3.5.11 SM-SR Change

 

 

What is in a Profile ?

 

A Profile is a set of UICC parameters that is required to attach a Network and perform various functions that the device subscribes. There are roughly three Categories of informaton as follows. (Based on the section 3.4.1 of GSMA Specification (Ref [1]))

    i) Authentication/Security Algorithm Parameters : Algorithms would be Milenage in most of the live network. or it can be 3GPP Test algorithm if it is configured for test. The parameters would be as follows.

    • OPc
    • ri
    • ci
    • K

    ii) Policy Rules attached to the Profile

    iii) Other UICC Parameters described TS 31.102 (Many of these parameters might be related to Policy Rules)

 

 

Common Use Case

 

As of now (Sep 2015), there is no international standard about eUICC Profile update method that is commonly adopted even though there are some cases where eUICC are used in terms of hardware. So, the use model listed here would be a kind of idea level.

 

Case 1 : eSIM is embedded in the device and IMEI (device ID) & ICCID (UICC Serial Number) is informed to end user (or a specific Service Center). And then, the end user (or Service Center) can ask Network Operator (MNO) to activate of eUICC.

 

 

Reference :