Group Identifier (level 2)

Description

Group Identifier level 2 (GID2) is a complementary identifier to GID1, defined within the 3GPP UICC and USIM specifications. It resides in its own dedicated elementary file, EF(GID2), within the file system of the USIM application on the UICC. Like GID1, GID2 is a network-provisioned data field, written by the mobile operator, and its format and meaning are operator-specific. The presence of two group identifiers allows for multi-dimensional or hierarchical grouping of subscribers.

From a technical perspective, GID2 operates identically to GID1 in terms of access mechanisms. The mobile equipment or the network accesses it by issuing a READ BINARY command for the file identifier of EF(GID2). The USIM application retrieves the stored bytes and returns them. The network infrastructure, such as the MSC, SGSN, or MME, can read this identifier during attachment procedures and include it in signaling messages to the HSS. The HSS can then use the combination of GID1 and GID2, or each independently, to reference a subscriber profile that dictates service parameters.

Architecturally, GID2 adds a second axis for subscriber classification within the core network's service logic. For example, an operator might use GID1 to denote the service plan type (e.g., consumer, business, M2M) and GID2 to indicate a sub-group within that plan, such as a specific corporate customer ID, a device type category, or a geographical service zone. This enables more complex and granular policy decisions. Network functions like the Policy and Charging Rules Function (PCRF) can use these identifiers to select the appropriate Quality of Service (QoS) and charging rules.

Its role in the network is to provide enhanced flexibility for subscriber management and service differentiation. While GID1 offers a primary grouping, GID2 allows for a secondary, orthogonal classification. This is crucial for sophisticated service offerings, layered access controls, and detailed analytics. It supports scenarios where a subscriber belongs to multiple overlapping groups (e.g., a vehicle belonging to both a 'fleet management' group and a 'high-priority data' group) without needing to merge these concepts into a single identifier, thus preserving clarity in operational and business support systems.

Purpose & Motivation

GID2 was created to address the limitation of having only a single group identifier (GID1), which proved insufficient for the complex service bundling and multi-tiered subscriber management strategies that emerged as mobile networks evolved. Operators needed a way to apply multiple, independent classification criteria to a single subscription. For instance, a subscription could be part of a corporate account (first group) and also have a specific feature bundle like international roaming enabled (second group). Using only GID1 would force the encoding of both attributes into one value, making logic cumbersome and inflexible.

The introduction of GID2 provided a straightforward solution: a second, independent field on the SIM for categorization. This was motivated by the growing diversity of mobile services and devices in the early 3G era (Release 4). It solved the problem of creating hierarchical or multi-faceted group policies. With two identifiers, operators could design a more logical and scalable group structure—using one for a primary business relationship and the other for a technical or service-specific classification.

This evolution reflected the need for greater expressiveness in subscriber profiles directly on the SIM card. GID2, alongside GID1, empowered operators to implement sophisticated service logic without constant queries to backend databases during routine procedures. It enabled efficient, SIM-driven triggering of network features for complex commercial offerings, machine-type communication deployments with varied service tiers, and partnerships where subscribers needed identities in multiple overlapping domains. Essentially, GID2 provided the granularity needed for the next generation of segmented mobile services.

Key Features

• Stored in the separate EF(GID2) elementary file on the USIM/UICC
• Provides a secondary, operator-defined grouping criterion independent of GID1
• Accessed via standard UICC command interface for reading elementary files
• Enables multi-dimensional or hierarchical subscriber categorization
• Allows for complex service logic and policy rules based on multiple group memberships
• Supports granular service differentiation for advanced commercial and M2M offerings

Evolution Across Releases

Defining Specifications