Mobile Execution Environment Executable

Description

The MExE executable is a core concept in the 3GPP Mobile Execution Environment (MExE) framework. It refers to one or more applets, applications, or content that conform to the MExE specification and are capable of executing on any MExE device that conforms to the appropriate classmark. In essence, a MExE executable is the actual software or content that is downloaded and run on the MExE UE. This could be a Java applet, a native application, or any other executable content that adheres to the MExE standards. The executable is designed to be portable across different MExE devices, provided they meet the minimum capabilities defined by the classmark associated with the executable.

The MExE executable is defined in 3GPP specifications 21.905 (Vocabulary) and 23.057 (MExE Stage 2). The concept was introduced in Release 99 (R99) and has evolved slightly over time. In R99 and Rel-4, the definition stated that an executable is an applet, application, or executable content that conforms to the MExE specification and may execute on the ME (Mobile Equipment). Starting from Rel-5, the wording changed to emphasize that it is one or more applet, application, or content that may execute on any MExE device conforming to the appropriate classmark. This change reflects a broader scope, acknowledging that executables can be composed of multiple components and that they are intended to run on any compliant device, not just a specific ME.

The MExE executable is the unit of deployment in the MExE service environment. When a user requests a service or application, the MExE server provides the executable to the UE. The UE then executes it within the MExE execution environment, which provides a secure and controlled runtime. The executable may interact with the UE's resources, such as display, memory, and network interfaces, through standardized APIs. The MExE specification defines the security model, lifecycle management, and interoperability requirements for these executables. This ensures that executables from different sources can run on the same device without compromising security or stability.

The relationship between a MExE executable and a MExE Classmark is crucial. An executable is typically associated with one or more classmarks that indicate the minimum device capabilities required to run it. For example, an executable that uses advanced 3D graphics might require a high-end classmark, while a simple text-based application might run on a lower classmark. When a UE requests an executable, the MExE server can check the UE's classmark and deliver an appropriate version of the executable, or deny the request if the UE does not meet the requirements. This ensures that the user experience is not degraded by attempting to run an executable on an underpowered device.

MExE executables can be delivered through various mechanisms, including HTTP, WAP, or other bearer technologies. The MExE specification defines the procedures for downloading, installing, and updating executables. It also defines how executables are managed, including their activation, deactivation, and removal. The MExE executable is thus a fundamental building block of the MExE ecosystem, enabling the distribution of rich applications and services to mobile devices in a standardized and interoperable manner. Despite the evolution of mobile application platforms, the MExE executable concept remains a historical reference for understanding how 3GPP envisioned mobile application execution.

Purpose & Motivation

The MExE executable was created to provide a standardized format for mobile applications and content that could be executed across different devices and networks. Before MExE, mobile applications were often device-specific and had to be developed separately for each handset model. This fragmentation made it difficult for developers to reach a wide audience and for operators to offer consistent services. The MExE executable solves this by defining a common execution environment and a set of rules that ensure an executable can run on any compliant device. This reduces development costs and increases the potential market for mobile applications.

The executable concept also addresses security and trust. In an open mobile environment, users may download applications from various sources. The MExE specification includes security mechanisms that allow the UE to verify the authenticity and integrity of executables before execution. This protects users from malicious software and ensures that only authorized applications run on the device. The MExE executable is thus not just a piece of code but a managed entity with a defined lifecycle and security context.

Furthermore, the MExE executable enables dynamic service delivery. Operators and service providers can offer new applications and updates over the air, without requiring users to manually install software. This is essential for keeping mobile services fresh and competitive. The executable can be tailored to the device's capabilities through the classmark mechanism, ensuring optimal performance. The MExE executable thus represents an early attempt to create an app store-like ecosystem within the 3GPP framework, paving the way for later mobile application platforms.