Multi-SIM: The Jargon

I had been having some discussions regarding Multi-SIM phones and there is a bit of misunderstanding so here is my clarification about them. Anyway, a lot of information is just an understanding so feel free to correct any mistakes you think I may have made.

This post is about multiple SIM cards, physical UICC cards rather than single UICC with multiple SIM applications. We will look at Dual IMSI later on in the post. In case you do not know about the multiple SIM applications in a UICC, see this old post here. In this post, I will refer to UICC cards as SIM cards to avoid confusion.

Back in the old days, the Dual-SIM phones allowed only one SIM on standby at any time. The other SIM was switched off. If someone would call the number that was switched off, a message saying that the number is switched off would come or it would go in the voicemail. To make this SIM in standby, you would have to select it from the Menu. The first SIM is now switched off. The way around it was to have one SIM card calls forwarded the other when switched off. This wasn't convenient and efficient, money wise. The reason people use multiple SIM phones is to have cheaper calls using different SIMs. So in this case forwarding calls from one SIM to another wont be cost effective. These type of phones were known as Dual SIM Single Standby or DSSS. These devices had a single transceiver.

So as the technology got cheaper and more power efficient, the new multi-SIM devices could incorporate two receivers but only one transmitter was used. The main reason being that using two transmitters would consume much more power. As a result, these devices can now have both the SIM's on standby at the same time. These kind of devices were known as Dual SIM Dual Standby or DSDS. Wikipedia also calls then Dual SIM Standby or DSS. This concept could be extended further to Triple SIM Triple Standby or TSTS in case of the device with three SIM cards and Quad SIM Quad Standby or QSQS in case of four SIM cards. One thing to remember is that when a call is received and a SIM becomes active, the other SIM cards become inactive for the duration of the call. A workaround for that situation is to forward the call to the other SIM card in case if its unavailable. Though this will work for DSDS, it may not be that straightforward in case of TSTS and QSQS due to more than two SIM cards being present.

Another category of devices that are now available are the Dual SIM Dual Active or DSDA. In this case there are two transceivers in the device. Both the SIM cards are active at the same time so each SIM card can handle the call independently of each other. It would even be possible to conference both these calls.

With the prices of calls falling, there is no longer a real need for multiple SIM cards. One SIM card is generally sufficient. It may be useful though to have multiple IMSI on the SIM card. The different IMSI would have different country and network code. For example, a person in in UK can have one IMSI with the home network code and one with say a US operator IMSI. This IMSI could only be programmed by the home operator. When the person is in UK he could receive calls on his UK number or on the US number which would be routed to his UK number. For a person in US calling the US number, this is a national call rather than an international one. When the person is roaming in the US, his US IMSI would behave like non-roaming case while the calls to the UK number would be forwarded to the US number.

Security and other development on the Embedded SIM

Its no surprise that GSMA has started working on Embedded SIM specifications. With M2M getting more popular every day, it would make sense to have the SIM (or UICC) embedded in them during the manufacturing process. The GSMA website states:

The GSMA’s Embedded SIM delivers a technical specification to enable the remote provisioning and management of Embedded SIMs to allow the “over the air” provisioning of an initial operator subscription and the subsequent change of subscription from one operator to another.

The Embedded SIM is a vital enabler for Machine to Machine (M2M) connections including the simple and seamless mobile connection of all types of connected vehicles. In the M2M market the SIM may not easily be changed via physical access to the device or may be used in an environment that requires a soldered connection, thus there is a need for ‘over the air’ provisioning of the SIM with the same level of security as achieved today with traditional “pluggable” SIM. It is not the intention for the Embedded SIM to replace the removable SIM currently used as the removable SIM still offers many benefits to users and operators in a number of different ways – for example, the familiarity of the form factor, easy of portability, an established ecosystem and proven security model.

The last time I talked about embedded SIM was couple of years back, after the ETSI security workshop here. Well, there was another of these workshops recently and an update to these information.

The ETSI presentation is not embedded here but is available on Slideshare here. As the slide says:

An embedded UICC is a “UICC which is not easily accessible or replaceable, is not intended to be removed or replaced in the terminal, and enables the secure changing of subscriptions” (ETSI TS 103 383)

Finally, Embedded SIM should not be confused with Soft-SIM. My last post on Soft-SIM, some couple of years back here, has over 15K views which shows how much interest is there in the soft SIM. As the slide says:

Soft or Virtual SIM is a completely different concept that does not use existing SIM hardware form factors and it raises a number of strong security issues:

• Soft SIM would store the Operator secret credentials in software within the Mobile device operating system - the same system that is often attacked to modify the handset IMEI, perform SIM-Lock hacking and ‘jail-break’ mobile OS’s
• Operators are very concerned about the reduction in security of their credentials through the use of Soft SIM. Any SIM approach not based on a certified hardware secure element will be subject to continual attack by the hacking community and if compromised result in a serious loss of customer confidence in the security of Operator systems
• Multiple Soft SIM platforms carrying credentials in differing physical platforms, all requiring security certification and accreditation would become an unmanageable overhead – both in terms of resource, and proving their security in a non-standardised virtual environment

The complete GSMA presentation is as follows:

GSMA Embedded SIM from Zahid Ghadialy

You may also like my old paper:

• M2M, Cellular and Small Cells

Different flavours of SRVCC (Single Radio Voice Call Continuity)

Single Radio Voice Call Continuity (SRVCC) has been quietly evolving with the different 3GPP releases. Here is a quick summary of these different flavors

In its simplest form, SRVCC comes into picture when an IMS based VoLTE call is handed over to the existing 2G/3G network as a normal CS call. SRVCC is particularly important when LTE is rolled out in small islands and the operator decided to provide VoLTE based call when in LTE. An alternative (used widely in practice) is to use CS Fallback (CSFB) as the voice option until LTE is rolled out in a wider area. The main problem with CSFB is that the data rates would drop to the 2G/3G rates when the UE falls back to the 2G/3G network during the voice call.

The book "LTE-Advanced: A Practical Systems Approach to Understanding 3GPP LTE Releases 10 and 11 Radio Access Technologies" by Sassan Ahmadi has some detailed information on SRVCC, the following is an edited version from the book:

SRVCC is built on the IMS centralized services (ICS) framework for delivering voice and messaging services to the users regardless of the type of network to which they are attached, and for maintaining service continuity for moving terminals.

To support GSM and UMTS, some modifications in the MSC server are required. When the E-UTRAN selects a target cell for SRVCC handover, it needs to indicate to the MME that this handover procedure requires SRVCC. Upon receiving the handover request, the MME triggers the SRVCC procedure with the MSC server. The MSC then initiates the session transfer procedure to IMS and coordinates it with the circuit-switched handover procedure to the target cell.

Handling of any non-voice packet-switched bearer is by the packet-switched bearer splitting function in the MME. The handover of non-voice packet-switched bearers, if performed, is according to a regular inter-RAT packet-switched handover procedure.

When SRVCC is enacted, the downlink flow of voice packets is switched toward the target circuit-switched network. The call is moved from the packet-switched to the circuit-switched domain, and the UE switches from VoIP to circuit-switched voice.

3GPP Rel-10 architecture has been recommended by GSMA for SRVCC because it reduces both voice interruption time during handover and the dropped call rate compared to earlier configurations. The network controls and moves the UE from E-UTRAN to UTRAN/GERAN as the user moves out of the LTE network coverage area. The SRVCC handover mechanism is entirely network-controlled and calls remain under the control of the IMS core network, which maintains access to subscribed services implemented in the IMS service engine throughout the handover process. 3GPP Rel-10 configuration includes all components needed to manage the time-critical signaling between the user’s device and the network, and between network elements within the serving network, including visited networks during roaming. As a result, signaling follows the shortest possible path and is as robust as possible, minimizing voice interruption time caused by switching from the packet-switched core network to the circuit-switched core network, whether the UE is in its home network or roaming. With the industry aligned around the 3GPP standard and GSMA recommendations, SRVCC-enabled user devices and networks will be interoperable, ensuring that solutions work in many scenarios of interest.

Along with the introduction of the LTE radio access network, 3GPP also standardized SRVCC in Rel-8 specifications to provide seamless service continuity when a UE performs a handover from the E-UTRAN to UTRAN/GERAN. With SRVCC, calls are anchored in the IMS network while the UE is capable of transmitting/ receiving on only one of those access networks at a given time, where a call anchored in the IMS core can continue in UMTS/GSM networks and outside of the LTE coverage area. Since its introduction in Rel-8, the SRVCC has evolved with each new release, a brief summary of SRVCC capability and enhancements are noted below

3GPP Rel-8: Introduces SRVCC for voice calls that are anchored in the IMS core network from E-UTRAN to CDMA2000 and from E-UTRAN/UTRAN (HSPA) to UTRAN/GERAN circuit-switched. To support this functionality, 3GPP introduced new protocol interface and procedures between MME and MSC for SRVCC from E-UTRAN to UTRAN/GERAN, between SGSN and MSC for SRVCC from UTRAN (HSPA) to UTRAN/GERAN, and between the MME and a 3GPP2-defined interworking function for SRVCC from E-UTRAN to CDMA 2000.

• 3GPP Rel-9: Introduces the SRVCC support for emergency calls that are anchored in the IMS core network. IMS emergency calls, placed via LTE access, need to continue when SRVCC handover occurs from the LTE network to GSM/UMTS/CDMA2000 networks. This evolution resolves a key regulatory exception. This enhancement supports IMS emergency call continuity from E-UTRAN to CDMA2000 and from E-UTRAN/UTRAN (HSPA) to UTRAN/ GERAN circuit-switched network. Functional and interface evolution of EPS entities were needed to support IMS emergency calls with SRVCC.

• 3GPP Rel-10: Introduces procedures of enhanced SRVCC including support of mid-call feature during SRVCC handover (eSRVCC); support of SRVCC packet-switched to circuit-switched transfer of a call in alerting phase (aSRVCC); MSC server-assisted mid-call feature enables packet-switched/ circuit-switched access transfer for the UEs not using IMS centralized service capabilities, while preserving the provision of mid-call services (inactive sessions or sessions using the conference service). The SRVCC in alerting phase feature adds the ability to perform access transfer of media of an instant message session in packet-switched to circuit-switched direction in alerting phase for access transfers.

• 3GPP Rel-11: Introduces two new capabilities: single radio video call continuity for 3G-circuit-switched network (vSRVCC); and SRVCC from UTRAN/GERAN to E-UTRAN/HSPA (rSRVCC). The vSRVCC feature provides support of video call handover from E-UTRAN to UTRAN-circuitswitched network for service continuity when the video call is anchored in IMS and the UE is capable of transmitting/receiving on only one of those access networks at a given time. Service continuity from UTRAN/GERAN circuitswitched access to E-UTRAN/HSPA was not specified in 3GPP Rel-8/9/10. To overcome this drawback, 3GPP Rel-11 provided support of voice call continuity from UTRAN/GERAN to E-UTRAN/HSPA. To enable video call transfer from E-UTRAN to UTRAN-circuit-switched network, IMS/EPC is evolved to pass relevant information to the EPC side and S5/S11/Sv/Gx/Gxx interfaces are enhanced for video bearer-related information transfer. To support SRVCC from GERAN to E-UTRAN/HSPA, GERAN specifications are evolved to enable a mobile station and base station sub-system to support seamless service continuity when a mobile station hands over from GERAN circuit-switched access to EUTRAN/ HSPA for a voice call. To support SRVCC from UTRAN to EUTRAN/ HSPA, UTRAN specifications are evolved to enable the RNC to perform rSRVCC handover and to provide relative UE capability information to the RNC.

NTT Docomo has a presentation on SRVCC and eSRVCC which is embedded below:

Improvement of VoLTE Domain HO with Operators Vision from Zahid Ghadialy

3GPP Rel-12 and Future Security Work

Here is the 3GPP presentation from the 9th ETSI Security workshop. Quite a few bits on IMS and IMS Services and also good to see new Authentication algorithm TUAK as an alternative to the widely used Milenage algorithm.

3GPP Rel-12 Security, and Future 3GPP Security Work from Zahid Ghadialy

My observations on Mobiles and OTT Apps in India

What a change 2 years can make. The last time I was in India, people were reluctant to use data, smartphones were far and few and even those smartphones were just status symbols rather than for actual 'smart' use.

This time a lot of things were very different. I found that there was a Phablet craze going on. No sooner were people starting to get used to these big screen devices they realised how many things they could do. The well to do were buying Samsung devices and the people who did not want to spend big bucks were content with the little known brands.

The Domo phablet on the left in the picture above costs around ₹8000 (£80/$130) and the Maxx on the right is roughly ₹5500 (£55/$90). Both these come with 1 year warranty.

There were also quite a few ads using celebrities promoting Phablets. Its good to see people spending on these devices. Unlike UK where most of these devices are subsidised on a contract, people in India prefer pre-paid option and buying the phone outright.

I have to admit that even though I am a fan of these big screen devices, I find the Samsung Galaxy Tab just a bit too big for the use as a phone (see pic above).

It was also good to see that people have embraced the 3G data usage as well. I got a 6GB package for roughly ₹1000 (£10/$16). I found that people complained about the speeds and were prepared to pay more for 4G (faster data rates). I also noticed that a few people were not aware of Wi-Fi and the fixed broadband. I was told that the fixed broadband was capped, offered similar prices and could be quite unreliable. I guess Wireless is helping in India where the fixed Infrastructure may still be an issue in many places.

I have to mention here that I did not meet anyone who was using an iPhone. This could be due to iPhone being ridiculously expensive and people may be thinking why pay a high price for such a small screen. A comparison of iPhone prices worldwide showed that the price of iPhone 5S as % of GDP per capita (PPP) is the highest in India. See here.


Another area of observation was SMS and OTT apps. I remember spending a lot of time trying to convince people to use OTT apps for messaging as it would be cheaper for International messages. Well, now it seems everyone has adopted it whole heartedly. One of the problems with SMS in India is that you get too much Spam SMS and sometimes the operators are the culprits. There is no way to send a stop for these SMS messages. With OTT Apps, you know who is sending you messages and you can block the offenders.

There are many OTT Apps which are popular like Hike, Line, WeChat, WhatsApp, etc. The winner though is undoubtedly WhatsApp. I met an acquaintance whose has stopped using emails for business and now relies completely on WhatsApp. Then there were others who loved it because of Group chat facility.

There were many reasons why WhatsApp is a winner. Along with a simple interface and Group chat facility, one of the other reasons pointed out was that the facility to see when the person was last online was very useful. Recently WhatsApp introduced facility to send Voice messages. This helped it acquire some of the WeChat users.

It was good to see the beginnings of the mobile revolution in India. Wonder what my next trip will show me.

Please note that this article is based on what I observed in Mumbai among friends and family. In no way should this be treated as  detailed research.

LTE-Broadcast (eMBMS) may fail again

I recently wrote a blog post for the Cisco SP Mobility blog on why the Cellular Broadcast may fail again (complete article embedded below). My main point is that small screen devices are not really suitable for mobile TV kind of applications. The larger devices like tablets are but since they do not contain the (U)SIM card, its not possible for them to receive cellular broadcast signals.

Anyway, I came across this picture below from the recent Ericsson Mobility report:

This highlights my point that more people are now preferring to watch videos over the tablets as compared to the smaller smartphone screens. Even though the other diagrams in the article does show a significant amount of users using their smartphones for viewing movies and long clips, my belief is that this will reduce over the time as the tablet share increases

A recent Business Insider article says that "One In Every 5 People In The World Own A Smartphone, One In Every 17 Own A Tablet". Once the users move to using bigger screens, their preferences on how they watch videos will definitely change.

A real interesting chart would be to show users viewing habits based on the screen size. Phablets are generally classified as smartphones but can be substitutes for tablets in many scenarios. They could definitely help the Mobile TV viewing habits on the smartphones.

Anyway, here is the complete article:

2014 Mobile Internet Prediction Survey

Interesting presentation by Chetan Sharma listing what we can expect in 2014. Slide 9 as shown in the picture above highlights the breakthrough categories. Good to see that LTE-B ('B' for broadcast) has not made it into this list. My guess is that connected cars and wearable computing will be in the news constantly throughout the year.

The complete presentation as follows:

The futuristic concept of 'Smart Batteries'

I did a presentation in the Cambridge Wireless Future technology SIG about what we call 'Smart Batteries'. The presentation is self-explanatory and is embedded below. I would be interested in hearing your thoughts about this idea.

Smart Batteries from eXplanoTech

Other links if you want to dig further on batteries:

• Li-Ion vs Li-Poly, plus how do Lithium batteries work anyway?
• Lithium-ion Batteries - Apple
• Battle of the smartphone batteries - Daily Mail
• New battery alternative emerges for hybrid cars
• Technology companies charge towards next generation battery future
• Light-weight body parts will be the battery of future cars
• These transparent solar cells provide 50% more battery life for your phone — and ‘infinite’ standby time
• Smartphone battery life: 2 problems, 4 fixes (Smartphones Unlocked)
• New lithium-ion battery design that’s 2,000 times more powerful, recharges 1,000 times faster
• The Power Treadmill

Top 15 blog posts from 2013

Here is a list of most popular blog posts from 2013. In descending order:

1. VoLTE Bearers
2. C-RAN Architecture and Challenges
3. What is WebRTC and where does it fit with LTE and IMS
4. 5G: Your Questions Answered
5. LTE-A: Downlink Transmission Mode 9 (TM-9)
6. 3GPP Rel.11 Technology Introduction whitepaper
7. New Carrier Type (NCT) in Release-12 and Band 29
8. Key challenges with automatic Wi-Fi / Cellular handover
9. The Relentless Rise of Mobile Technology
10. Access Class Barring in LTE using System Information Block Type 2
11. LTE-B, LTE-C, ... , LTE-X
12. China Mobile: A peek at 5G
13. Summary of Network Security Conference (#NetworkSecurity) 2013
14. Quick summary on LTE and UMTS / HSPA Release-12 evolution by 3GPP
15. Introduction to M2M and its developments in LTE

Advancements in Congestion control technology for M2M

NTT Docomo recently published a new article (embedded below) on congestion control approaches for M2M. In their own words:

Since 3GPP Release 10 (Rel. 10) in 2010, there has been active study of technical specifications to develop M2M communications further, and NTT DOCOMO has been contributing proactively to creating these technical specifications. In this article, we describe two of the most significant functions standardized between 3GPP Rel. 10 and Rel. 11: the M2M Core network communications infrastructure, which enables M2M service operators to introduce solutions more easily, and congestion handling technologies, which improve reliability on networks accommodating a large number of terminals.

Complete article as follows:

Core Network Infrastructure and Congestion Control Technology for M2M Communications from Zahid Ghadialy

Other related posts:

• Rise of the "Thing"
• Access Class Barring in LTE using System Information Block Type 2
• Extended Access Barring (EAB) in Release 11 to avoid MTC overload
• RAN mechanisms to avoid CN overload due to MTC
• Service Specific Access Control (SSAC) in 3GPP Release 9