Description
The Bearer Independent Protocol (BIP) is a mechanism defined in 3GPP TS 22.038 and catalogued in TS 21.905 by which the Mobile Equipment (ME) provides (U)SIM applications resident on the UICC with access to the data bearers supported by the ME and the network. In other words, BIP is the abstraction layer that allows an applet running inside the SIM card to open, use and close data connections through the handset without knowing or caring whether the underlying transport is GPRS, UMTS PS, LTE EPS, 5G, SMS, or a local link such as Bluetooth or USB.
Architecturally, BIP sits between the UICC and the ME and is realised through a set of proactive UICC commands defined in ETSI TS 102 223 (the Card Application Toolkit, CAT). The card issues a command such as OPEN CHANNEL, specifying a transport type (e.g. packet data service, local link, or default bearer), buffer sizes and, optionally, an APN or destination address. The ME then establishes the bearer, and the card can subsequently issue SEND DATA, RECEIVE DATA, GET CHANNEL STATUS and CLOSE CHANNEL commands. Data arriving from the network is delivered to the card via the ENVELOPE (Data Available) mechanism, and the card can also be notified of channel status changes. The ME acts as a proxy: it owns the radio connection and the PDP/PDU session, while the card owns the application logic and the endpoint addressing.
BIP is fundamental to Over-The-Air (OTA) management of the UICC. Remote management platforms (e.g. OTA servers operated by the home operator) can push applets, update files, or change subscription parameters by opening a BIP channel to a server address held in the card. Because BIP is bearer independent, the same card application works across 2G, 3G, 4G and 5G handsets without modification. This is especially valuable for M2M and IoT SIMs, where the card may need to autonomously contact a management server, and for roaming scenarios where the card must reach a home server over whatever access is available.
Key components include the UICC (hosting the BIP-capable applet and the BIP configuration in EF_BIP or similar files), the ME (implementing the terminal side of the CAT/BIP commands and mapping them to bearers), and the network (providing the actual packet data connectivity and addressing). The protocol also supports multiple simultaneous channels, buffer management, and error reporting back to the card, which allows robust application-level retry logic.
In the broader network, BIP does not define new radio or core-network interfaces; it is a card-terminal interface protocol. Its role is to make the UICC an active, networked entity rather than a passive credential store. This underpins modern eSIM/remote provisioning concepts (where the card must fetch profiles), operator applets for self-care, and secure element-based services. Because the definition has remained stable from Rel-8 through Rel-19, BIP is a mature, backward-compatible foundation that continues to serve new generations of terminals and cards.
Purpose & Motivation
BIP exists to solve a fundamental limitation of early smart cards: a UICC applet had no way to communicate with the outside world except through SMS or by asking the user to dial. That made remote management slow, expensive and technology-specific. BIP was created so that card applications could use the handset's data bearers directly, turning the SIM into an active network client.
The motivation was threefold. First, OTA management of SIM cards needed a scalable, IP-capable transport rather than SMS-PP, which is bandwidth-limited and costly. Second, M2M and IoT deployments required SIMs that could autonomously contact management servers without user interaction. Third, the industry needed bearer independence so that the same card application would work across GPRS, UMTS, LTE and later 5G without re-issuing cards.
By abstracting the bearer behind a standard command set, BIP decouples card application development from radio technology evolution. It also enables new business models such as operator applets, secure-element services and remote profile provisioning, all of which rely on the card being able to reach a server on its own initiative.
What changed in its specifications
The latest release-to-release comparison of specifications that define Bearer independent protocol. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-5 added USAT definitions, proactive key press indication, ISIM reference, and removed network-specific bearer and communication control restrictions.
Full comparison in TS 22.038 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Bearer independent protocol, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.038 vj00 | USIM Application Toolkit (USAT) Stage 1 | Rel-19 read |