Sending Application

Description

The Sending Application is a functional entity defined in 3GPP specifications that is responsible for generating an Application Message to be sent to a receiving entity. In the context of the USAT (USIM Application Toolkit) and related specifications, the Sending Application is specifically identified as the USAT Interpreter or the Gateway. This entity initiates communication by creating messages that may contain commands, data, or requests, which are then transmitted over the network or within the device.

The concept is defined in 3GPP TS 22.048 and TS 23.048, which cover security mechanisms for USAT and other applications, as well as TS 31.114, which specifies the USAT Interpreter. The USAT Interpreter is a component within the USIM that executes USAT commands and generates responses or new commands. The Gateway, on the other hand, acts as an intermediary between the USIM and external entities, such as network servers or other applications. Together, these entities form the Sending Application when they generate messages.

In a typical USAT scenario, the Sending Application generates an Application Message that includes a header, payload, and possibly security parameters. The message is then passed to the transport layer for delivery. The receiving entity, which could be another application on the same card, a network server, or a remote device, processes the message according to its content. The Sending Application must ensure that the message is correctly formatted and, if required, secured using mechanisms such as Sender Identification or integrity protection.

The architecture supporting the Sending Application is modular, allowing different applications to act as senders. This flexibility is important for enabling a wide range of services, from remote management of the USIM to value-added services like mobile payments or location-based services. The Sending Application can be triggered by various events, such as a command from the network, a timer expiry, or a user action. It then generates the appropriate message and initiates transmission.

In the broader context of 3GPP, the Sending Application is part of the application layer that sits above the transport and network layers. It interacts with other entities through well-defined interfaces, ensuring interoperability across different vendors and implementations. As networks evolve towards 5G and IoT, the role of the Sending Application remains relevant, particularly in scenarios involving embedded SIMs (eSIM) and remote provisioning, where secure and reliable message exchange is critical.

Purpose & Motivation

The Sending Application was defined to provide a clear and standardized role for the entity that originates application messages in USAT and related environments. Prior to its definition, the process of generating and sending messages was not formally specified, leading to potential interoperability issues and security gaps. By identifying the Sending Application as a distinct entity, 3GPP enabled consistent implementation across different devices and networks.

The primary problem it solves is the need for a well-defined originator of application messages. In USAT, the USIM card can initiate actions independently of the mobile equipment, such as sending an SMS or launching a browser. The Sending Application is the component that generates the corresponding messages. Without a clear definition, it would be difficult to ensure that messages are properly formatted, secured, and routed. The Sending Application provides a focal point for message generation, allowing security mechanisms like Sender Identification to be applied consistently.

Historically, the Sending Application was introduced in Release 5 as part of the USAT security framework. It addressed the limitations of earlier ad-hoc approaches by providing a formal specification. In Release 8, the definition was expanded to explicitly include the USAT Interpreter and the Gateway, reflecting the growing complexity of USAT applications and the need to clarify the roles of these components. This evolution highlights the ongoing effort to standardize and secure application-level communication in mobile networks.