Application Protocol

Description

The Application Protocol is a concept defined in 3GPP specifications 21.905, 22.112, and 31.121. It serves as the communication ruleset between an application system (such as a remote server) and the USAT Gateway (typically located in the (U)SIM card or terminal). The protocol ensures that data exchanged between these entities is formatted, transmitted, and interpreted correctly. It operates above the transport layer and is responsible for the semantics of the application-level dialogue, including command and response structures, error handling, and session management.

In the context of the USAT (USIM Application Toolkit), the Application Protocol enables the card to interact with external application systems. For example, a remote server can send commands to the card to update files, request information, or trigger actions. The USAT Gateway acts as an intermediary, translating between the Application Protocol and the card's internal interfaces. The protocol defines the message formats, the sequence of exchanges, and the security mechanisms (often leveraging the Application Message concept) to protect the data.

Key components include the application system (e.g., an OTA server), the USAT Gateway, and the transport network. The Application Protocol is independent of the transport, meaning it can run over SMS, HTTP, or other bearers. This flexibility is achieved by encapsulating the protocol data units within transport-specific messages. The protocol also supports various security levels, ensuring that sensitive operations are protected against eavesdropping and tampering.

The definition of Application Protocol has evolved over releases. Initially, in R99, it was defined as 'Protocol to convey data between the content system and the USAT Gateway.' In Rel-4, the definition changed to 'The set of procedures required by the application.' This broader definition emphasizes that the protocol encompasses not just data conveyance but the entire set of procedures that an application needs to perform its functions. In Rel-5, the definition reverted to the data conveyance wording, but with 'application system' instead of 'content system.' From Rel-9 onwards, the definition stabilized as 'The set of procedures required by the application,' reflecting a more abstract and comprehensive view.

This evolution shows a shift from a narrow transport-focused definition to a broader procedural definition. The current definition highlights that the Application Protocol is not just about moving data but about enabling the complete behavior of an application, including command sequences, state management, and error recovery. This is essential for complex applications such as remote file management, security domain updates, and value-added services.

In practice, the Application Protocol is implemented in both the application system and the USAT Gateway. It relies on lower-layer protocols for transport and may use the Application Message for secure encapsulation. The protocol's procedures are defined in specifications like 22.112 (USAT) and 31.121 (USIM test specification), ensuring interoperability across different vendors and networks.

Purpose & Motivation

The Application Protocol exists to standardize communication between application systems and USAT Gateways, ensuring interoperability and enabling remote management of (U)SIM cards. Before its introduction, proprietary protocols hindered multi-vendor deployments and limited the ability to offer advanced services. The protocol provides a common language for commands and responses, allowing applications to be developed independently of the underlying transport and card implementation.

It solves the problem of secure and reliable data exchange over various bearers by defining a consistent set of procedures. This is crucial for OTA provisioning, where network operators need to update card content, manage subscriptions, and deploy new services without physical access to the card. The protocol also supports security mechanisms, such as authentication and encryption, to protect sensitive data.

The evolution of the definition reflects a growing understanding of the protocol's role. The initial focus on data conveyance was expanded to include the entire set of procedures required by an application, acknowledging that communication is not just about data but about the sequence of interactions that achieve a goal. This broader definition aligns with the increasing complexity of applications and the need for robust, stateful protocols.