UICC and USIM in 3GPP Release 8 and Release 9

In good old days of GSM, SIM was physical card with GSM "application" (GSM 11.11)

In the brave new world of 3G+, UICC is the physical card with basic logical functionality (based on 3GPP TS 31.101) and USIM is 3G application on a UICC (3GPP TS 31.102). The UICC can contain multiple applications like the SIM (for GSM), USIM and ISIM (for IMS). There is an interesting Telenor presentation on current and future of UICC which may be worth the read. See references below.

UICC was originally known as "UMTS IC card". The incorporation of the ETSI UMTS activities into the more global perspective of 3GPP required a change of this name. As a result this was changed to "Universal Integrated Circuit Card". Similarly USIM (UMTS Subscriber Identity Module) changed to Universal Subscriber Identity Module.

The following is from the 3G Americas Whitepaper on Mobile Broadband:

UICC (3GPP TS 31.101) remains the trusted operator anchor in the user domain for LTE/SAE, leading to evolved applications and security on the UICC. With the completion of Rel-8 features, the UICC now plays significant roles within the network.

Some of the Rel-8 achievements from standards (ETSI, 3GPP) are in the following areas:

USIM (TS 31.102)
With Rel-8, all USIM features have been updated to support LTE and new features to better support non-3GPP access systems, mobility management, and emergency situations have been adopted.

The USIM is mandatory for the authentication and secure access to EPC even for non-3GPP access systems. 3GPP has approved some important features in the USIM to enable efficient network selection mechanisms. With the addition of CDMA2000 and HRPD access technologies into the PLMN, the USIM PLMN lists now enable roaming selection among CDMA, UMTS, and LTE access systems.

Taking advantage of its high security, USIM now stores mobility management parameters for SAE/LTE. Critical information like location information or EPS security context is to be stored in USIM rather than the device.

USIM in LTE networks is not just a matter of digital security but also physical safety. The USIM now stores the ICE (In Case of Emergency) user information, which is now standardized. This feature allows first responders (police, firefighters, and emergency medical staff) to retrieve medical information such as blood type, allergies, and emergency contacts, even if the subscriber lies unconscious.

3GPP has also approved the storage of the eCall parameters in USIM. When activated, the eCall system establishes a voice connection with the emergency services and sends critical data including time, location, and vehicle identification, to speed up response times by emergency services. ECalls can be generated manually by vehicle occupants or automatically by in-vehicle sensors.

TOOLKIT FEATURES IMPROVEMENT (TS 31.111)
New toolkit features have been added in Rel-8 for the support of NFC, M2M, OMA-DS, DM and to enhance coverage information.

The contactless interface has now been completely integrated with the UICC to enable NFC use cases where UICC applications proactively trigger contactless interfaces.

Toolkit features have been updated for terminals with limited capabilities (e.g. datacard or M2M wireless modules). These features will be notably beneficial in the M2M market where terminals often lack a screen or a keyboard.

UICC applications will now be able to trigger OMA-DM and DS sessions to enable easier device support and data synchronization operations, as well as interact in DVB networks.

Toolkit features have been enriched to help operators in their network deployments, particularly with LTE. A toolkit event has been added to inform a UICC application of a network rejection, such as a registration attempt failure. This feature will provide important information to operators about network coverage. Additionally, a UICC proactive command now allows the reporting of the signal strength measurement from an LTE base station.

CONTACT MANAGER
Rel-8 defined a multimedia phone book (3GPP TS 31.220) for the USIM based on OMA-DS and its corresponding JavaCard API (3GPP TS 31.221).

REMOTE MANAGEMENT EVOLUTION (TS 31.115 AND TS 31.116)
With IP sessions becoming prominent, an additional capability to multiplex the remote application and file management over a single CAT_TP link in a BIP session has been completed. Remote sessions to update the UICC now benefit from additional flexibility and security with the latest addition of the AES algorithm rather than a simple DES algorithm.

CONFIDENTIAL APPLICATION MANAGEMENT IN UICC FOR THIRD PARTIES
The security model in the UICC has been improved to allow the hosting of confidential (e.g. third party) applications. This enhancement was necessary to support new business models arising in the marketplace, with third party MVNOs, M-Payment and Mobile TV applications. These new features notably enable UICC memory rental, remote secure management of this memory and its content by the third party vendor, and support new business models supported by the Trusted Service Manager concept.

SECURE CHANNEL BETWEEN THE UICC AND TERMINAL
A secure channel solution has been specified that enables a trusted and secure communication between the UICC and the terminal. The secure channel is also available between two applications residing respectively on the UICC and on the terminal. The secure channel is applicable to both ISO and USB interfaces.

RELEASE 9 ENHANCEMENTS: UICC: ENABLING M2M AND FEMTOCELLS
The role of femtocell USIM is increasing in provisioning information for Home eNodeB, the 3GPP name for femtocell. USIMs inside handsets provide a simple and automatic access to femtocells based on operator and user-controlled Closed Subscriber Group list.

Work is ongoing in 3GPP for the discovery of surrounding femtocells using toolkit commands. Contrarily to macro base stations deployed by network operators, a femtocell location is out of the control of the operator since a subscriber can purchase a Home eNodeB and plug it anywhere at any time. A solution based on USIM toolkit feature will allow the operator to identify the femtocells serving a given subscriber. Operators will be able to adapt their services based on the femtocells available.

The upcoming releases will develop and capitalize on the IP layer for UICC remote application management (RAM) over HTTP or HTTPS. The network can also send a push message to UICC to initiate a communication using TCP protocol.

Additional guidance is also expected from the future releases with regards to the M2M dedicated form factor for the UICC that is currently under discussion to accommodate environments with temperature or mechanical constraints surpassing those currently specified by the 3GPP standard.

Some work is also expected to complete the picture of a full IP UICC integrated in IP-enabled terminal with the migration of services over EEM/USB and the capability for the UICC to register on multicast based services (such as mobile TV).

Further Reading:

• Business perspective and Mobile service offer through Future SIM - Telenor (http://www.ux.uis.no/atc08/workshop/Larsen.pdf)
• The role of the UICC in Long Term Evolution all IP networks - Gemalto (http://www.gemalto.com/telecom/download/lte_gemalto_whitepaper.pdf)
• Technical White Paper: Smart Card in IMS - 3G Americas (http://www.3gamericas.org/documents/GEM_WP_IMS.pdf)
• 3GPP TS 31.101: UICC-terminal interface; Physical and logical characteristics (http://www.3gpp.org/ftp/Specs/archive/31_series/31.101/)
• 3GPP TS 31.102: Universal Subscriber Identity Module (USIM) application (http://www.3gpp.org/ftp/Specs/archive/31_series/31.102/)
• 3GPP TS 31.111: Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) (http://www.3gpp.org/ftp/Specs/archive/31_series/31.111/)
• 3GPP TS 31.115: Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.115/)
• 3GPP TS 31.116: Remote APDU Structure for (U)SIM Toolkit applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.116/)
• 3GPP TS 31.220: Characteristics of the Contact Manager for 3GPP UICC applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.220/)
• 3GPP TS 31.221: Contact Manager Application Programming Interface (API); Contact Manager API for Java Card™ (http://www.3gpp.org/ftp/Specs/archive/31_series/31.221/)

Simplifying LTE/SAE Interfaces

Here is simplified diagram of LTE Interfaces from my upcoming training on LTE/SAE. Hope you find it useful.

India gets ready for 3G

So here comes 3G in India. It’s been long coming as the data needs were increasing rapidly in almost all the Indian states. With the existing cellular infrastructure not capable of holding huge traffic particular for data, arrival of 3G was imminent.

The Indian Department of Telecoms (DoT) has published its official timetable for the award of its 3G licences across the country as well as a breakdown of how the relevant spectrum will be allocated across the telecoms circles.

As expected, the state-owned operators BSNL and MTNL each have been reserved one block of 2x5MHz in each circle, with the exception of Rajasthan (State in North West India) which will have no 3G spectrum at all. The number of blocks of spectrum in the private auction differs depending on the circle (see the spectrum table, below).

The auction for the 15-year licences is planned for Jan. 15, 2009. In the majority of 3G service areas there is 25 MHz of paired frequency bandwidth available which relates to four blocks of 2x5 MHz spectrum available for auction in addition to the block reserved for the state-owned operators, Bharat Sanchar Nigam (BSNL) and Mahanagar Telephone Nigam (MTNL). Spectrum is rather limited in many other areas, including the major metro circle of Delhi where only two 2x5MHz blocks will be available to private operators.

All of the 3G spectrum will be in the 2.1 GHz band and in the 2.3 GHz and 2.5 GHz frequency bands, a separate auction for Broadband Wireless Access (WiMAX). In both these auctions, which will take place two days after the 3G auction, bidders are restricted to just one block of spectrum per service area.

The table below shows the proposed spectrum layout.

Service Area (Indian Cities or States)	Paired frequency bandwidth to be allotted	Paired frequency bandwidth to be allotted
Delhi	160	15
Mumbai	160	25
Kolkata	80	25
Maharashtra	160	25
Gujrat	160	15
Andhra Pradesh	160	25
Karnataka	160	25
Tamil Nadu	80	25
Kerela	80	25
Punjab	80	25
Haryana	80	25
Uttar Pradesh(e)	80	25
Uttar Pradesh (w)	80	10
Rajasthan	0	20
Madhya Pradesh	80	25
Bengal	80	25
Himachal Prades	30	25
Bihar	30	25
Orrisa	30	25
Assam	30	25
North East	30	5
Jammu And Kashmir	30	25

LTE Architecture: Flat or Not so Flat?

'Migrating to Flatter, All-IP Wireless Networks' claims this article in converge digest. People have been talking about this Flat architectures for some time now and I decided that it was time i clear my understanding on this.

While searching my library of infinite resources i finally hit the jackpot. Qualcomm presentation from LTE 2007 has an answer.


The flatness of an access network can be measured by the depth of its link layer-specific network element hierarchy.

Going back to the article mentioned earlier:

Despite the growth of carrier networks and the evolution of standards, voice and data communications have not evolved in synch. Carriers have historically added data communications as an afterthought to voice network architectures originally conceived in the circuit-switched era, resulting in complex hierarchical networks that support both voice and data.

This type of architecture is expensive, leading to high operating and capital expenditures for service providers and significantly lowering margins in a highly competitive industry. In addition, networks employing cobbled-together voice and data communications systems simply do not have the capacity to provide the rich multimedia services and omnipresent Internet access that today’s wireless customers demand.

To address these limitations, service providers are moving toward emerging all-IP wireless technologies that promise to reduce complexity, simplify the wireless core, and decrease service providers’ operational and capital expenses.

Currently there are several initiatives that operators are considering for building wireless IP networks:

· WiMAX End-to-End Network Systems Architecture: Defined by the WiMAX Forum Network Working Group (NWG) and leveraging the IEEE 802.16e WiMAX interface.
· Long Term Evolution (LTE): Being defined by the Third Generation Partnership Project (3GPP) and targeted as a successor to GSM-based technologies.
· Ultra Mobile Broadband (UMB): Being defined by the Third Generation Partnership Project 2 (3GPP2) and targeted as a successor to CDMA-based technologies.

All three of these architectures are similar in that they leverage a flat, user-plane, all-IP network architecture with fewer nodes that enables mobile operators to integrate the core with the access network, providing real-time multimedia and broadband IP services from the core to the mobile station. This flatter architecture results in reduced latencies and thus optimizes performance for real-time services such as voice and video.

So going back to the Qualcomm presentation and checking if the LTE part is as flat as claimed.

We can see that the LTE Network Architecture is Lumpy rather than flat. Even though it is an improvement from the Release 99 (or rather Release 6) its not as flat as claimed.

Sure this would be something to consider in case of 4G (IMT-Advanced).