Corporate Code

Description

The Corporate code is a unique identifier used in 3GPP networks to distinguish corporate entities for the purpose of personalized services and device management. It is stored in the GID2 file on the (U)SIM card and correspondingly on the Mobile Equipment (ME). When combined with the network code and Service Provider (SP) code, it forms a complete identifier that allows the network to recognize and apply specific policies or services tailored to that corporate customer. This mechanism is part of the broader corporate personalization framework, enabling a corporate customer to control which devices can access their services.

Architecturally, the Corporate code resides in the GID2 elementary file (EF_GID2) on the (U)SIM, which is defined in 3GPP TS 31.102. The ME reads this code during initialization and stores it locally. When the device attempts to access services, the network can compare the code received from the device with the expected value for that corporate entity. This allows the network to enforce access restrictions, apply specific billing or QoS policies, or enable value-added services exclusive to the corporation. The combination of network, SP, and corporate codes ensures global uniqueness, preventing conflicts between different corporate customers.

The Corporate code is particularly relevant in scenarios where a corporation provides mobile devices to its employees or customers. By embedding the code in the (U)SIM and ME, the corporation can ensure that only devices provisioned with the correct code can access its internal services or benefit from negotiated rates. This is often used in conjunction with corporate personalization, where the ME is locked to a specific set of (U)SIMs. The code also facilitates remote management, as the network can identify the corporate entity and push configuration updates or policies accordingly.

From a standardization perspective, the Corporate code has been present since Release 4 and is defined in 3GPP TS 21.905, the vocabulary specification. Its definition has remained largely stable, with only minor editorial changes such as the transition from "SIM" to "(U)SIM" to reflect the inclusion of USIM applications. This stability underscores its foundational role in corporate service offerings. The code is typically a fixed-length string or integer, and its format is specified in the (U)SIM file system to ensure interoperability across different ME and (U)SIM vendors.

In practice, the Corporate code is managed by the network operator or service provider in coordination with the corporate customer. It is provisioned onto the (U)SIM during personalization and stored on the ME during initial configuration. The code is not intended to be user-visible or modifiable, ensuring integrity. Its presence enables a range of enterprise services, from closed user groups to dedicated APNs, and is a key enabler for the corporate market segment in 3GPP networks.

Purpose & Motivation

The Corporate code exists to provide a standardized way to uniquely identify corporate entities within a mobile network, enabling personalized services and device management. Before its introduction, corporate customers had limited means to ensure that only authorized devices could access their services or to differentiate their traffic from that of regular subscribers. The Corporate code solves this by providing a unique identifier that can be embedded in the (U)SIM and ME, allowing the network to recognize the corporate entity and apply appropriate policies.

This identifier is crucial for enabling corporate personalization, where a corporation can lock devices to its own (U)SIMs, preventing unauthorized use. It also supports differentiated billing, QoS, and access control, allowing operators to offer tailored packages to enterprises. The combination with network and SP codes ensures global uniqueness, avoiding collisions between different corporate customers. The Corporate code thus addresses the need for a scalable, standardized mechanism to serve the enterprise market, which has distinct requirements compared to consumer subscribers.