Mobile Execution Environment Server

Description

The MExE server is a key architectural component of the 3GPP Mobile Execution Environment (MExE) framework. It is defined as a node that supports MExE services in the MExE service environment. In essence, the MExE server acts as the application server or service provider within the MExE ecosystem. It is responsible for delivering MExE executables (applications, applets, or content) to MExE UEs, managing the lifecycle of these executables, and ensuring that they are compatible with the capabilities of the target devices. The MExE server may be operated by a mobile network operator, a third-party service provider, or an enterprise, and it can be located within the mobile operator's network or in an external network.

The MExE server is defined in 3GPP specifications 21.905 (Vocabulary), 22.057 (MExE Stage 1), and 23.057 (MExE Stage 2). The concept was introduced in Release 4 and has been maintained through subsequent releases up to Release 19, with the definition text remaining essentially unchanged. The MExE server interacts with the MExE UE through the MExE service environment, which provides the necessary protocols and interfaces for service discovery, negotiation, delivery, and execution. The server may also interact with other network elements, such as the MExE service environment's security and management functions, to ensure secure and reliable service delivery.

The primary function of the MExE server is to host and provide MExE executables. When a UE requests a service, the MExE server determines the appropriate executable based on the UE's MExE Classmark and other capabilities. It then delivers the executable to the UE, possibly after performing authentication and authorization checks. The server may also provide updates or patches to executables, and it can manage the activation and deactivation of services. In addition, the MExE server may offer value-added services such as billing, user profile management, and service personalization. The server is thus a central point for service delivery and management in the MExE architecture.

The MExE server also plays a role in the security of MExE services. It may authenticate itself to the UE and vice versa, and it can sign executables to ensure their integrity and authenticity. The server may also enforce security policies, such as restricting access to certain executables based on the user's subscription or the device's security capabilities. The MExE specification defines security mechanisms that can be implemented by the server and the UE to protect against malicious code and unauthorized access. This makes the MExE server a trusted entity in the MExE service environment.

From an architectural perspective, the MExE server can be seen as an application server that is specialized for the MExE framework. It may be implemented as a standalone server or integrated with other network functions. The MExE server communicates with the UE using standard protocols, such as HTTP or WAP, and it may use the MExE service environment's APIs to interact with the UE's execution environment. The server may also interface with the mobile network's core network elements, such as the GPRS support nodes, to manage the bearer connections. Overall, the MExE server is the cornerstone of the MExE service environment, enabling the delivery of rich mobile applications and services in a standardized and interoperable manner.

Purpose & Motivation

The MExE server was created to provide a centralized point for the delivery and management of mobile applications and services within the MExE framework. Before its introduction, mobile applications were often delivered through ad-hoc mechanisms, such as SMS or WAP push, without a standardized server-side component. This made it difficult to manage application versions, ensure compatibility with different devices, and provide a consistent user experience. The MExE server solves these problems by acting as a single point of contact for MExE services, allowing operators and service providers to control the distribution and execution of applications.

The server also addresses the need for security and trust in mobile application delivery. By centralizing the delivery process, the MExE server can enforce security policies, authenticate users and devices, and sign executables to prevent tampering. This is essential for protecting users from malicious software and for enabling secure mobile commerce and other sensitive applications. The MExE server can also provide billing and charging functions, allowing operators to monetize MExE services.

Furthermore, the MExE server enables dynamic service adaptation. It can tailor the delivered executable to the specific capabilities of the UE, as indicated by the MExE Classmark. This ensures that the application runs optimally on the device and that the user experience is not compromised by hardware limitations. The server can also manage the lifecycle of executables, including updates and removal, without requiring user intervention. This makes the MExE server a powerful tool for operators and service providers to offer a wide range of mobile services efficiently and securely. The MExE server thus represents an early vision of an app store and cloud service platform within the 3GPP ecosystem.