GSM Session

Description

The GSM session is a concept defined in 3GPP specifications 21.905 and 31.121 that refers to the part of a card session dedicated to GSM operation. A card session, in the context of a UICC (Universal Integrated Circuit Card), is the logical connection between the card and the terminal (e.g., mobile equipment) that allows applications on the card to be accessed. The GSM session specifically encompasses the procedures and data exchanges required for GSM (2G) network access, including authentication, ciphering, and subscriber data management. This session is established when the terminal powers up and the card is activated, and it remains active as long as the card is powered and the GSM application is selected.

The GSM session is crucial for backward compatibility, as it allows modern UICCs to support legacy GSM networks while also hosting other applications such as USIM (for UMTS) and ISIM (for IMS). The session is managed by the card's operating system, which ensures that GSM-specific commands and responses are routed appropriately. For example, when the terminal sends a GSM-specific command like RUN GSM ALGORITHM, it is handled within the GSM session. The session also includes the management of GSM files (e.g., EF_AD, EF_IMSI) and the execution of GSM security algorithms.

In terms of architecture, the GSM session is part of the overall card session, which can be multiplexed among different applications. The terminal selects the GSM application (AID A0000000871002) to initiate the GSM session. Once selected, the session provides access to GSM-specific files and functions. The session can be terminated when the terminal switches to another application or when the card is reset. The GSM session is defined in 3GPP TS 31.121, which specifies the UICC-terminal interface for GSM, and in 21.905, which provides the vocabulary.

The GSM session has evolved over releases, but its definition has remained largely unchanged, reflecting its stable role in supporting GSM. It is a foundational concept for ensuring that UICCs can serve multiple generations of networks. As networks evolve towards 5G, the GSM session remains relevant for fallback and roaming scenarios, although its usage is declining. Nevertheless, it is a key part of the card session model that enables multi-application UICCs.

Purpose & Motivation

The GSM session exists to provide a dedicated logical channel for GSM operations on a UICC, ensuring that legacy GSM procedures can be executed independently of other applications. This separation is necessary because a UICC can host multiple applications (e.g., USIM, ISIM), and each requires its own session context. Without the GSM session, the terminal would not be able to distinguish between GSM-specific commands and those for other applications, leading to conflicts and errors. The GSM session solves this by defining a clear boundary: when the GSM application is selected, the card session is dedicated to GSM, and all commands are interpreted in that context.

Historically, when SIM cards were introduced for GSM, they were single-application cards. As UICCs emerged to support multiple applications, the need for session management became apparent. The GSM session concept was introduced to allow a UICC to emulate a GSM SIM while also supporting other applications. This was particularly important during the transition from 2G to 3G, where dual-mode terminals needed to access both GSM and UMTS services. The GSM session ensures that the terminal can perform GSM authentication and access GSM files without interfering with USIM operations.

The GSM session also facilitates interoperability and roaming, as GSM networks are still widely used globally. Even in the era of 5G, many devices fall back to GSM for voice calls in areas with limited coverage. Thus, the GSM session remains a relevant part of the UICC architecture, providing a standardized way to handle GSM operations within a multi-application card.