Mobile Execution Environment Subscriber

Description

The MExE subscriber is defined in 3GPP TS 21.905 and TS 22.057 as the owner of a subscription who has entered into an agreement with a MExE service provider for MExE services. This definition establishes the commercial and technical relationship between the end-user and the service provider within the Mobile Execution Environment framework. The term is deliberately scoped to exclude access to MExE services through other types of networks, meaning that the MExE subscriber relationship is specific to the 3GPP-defined MExE service environment.

In the MExE architecture, the subscriber is the entity that consumes MExE services, which may include application downloads, secure transactions, location-based services, and other mobile value-added services. The MExE subscriber relationship is established through a subscription agreement, which typically involves the subscriber's home network operator and one or more MExE service providers. The agreement defines the terms of service, including quality of service, billing arrangements, and security requirements.

The MExE subscriber concept is important because it distinguishes between the technical subscriber identity (the IMSI stored on the SIM/USIM) and the commercial subscriber relationship. A MExE subscriber may have multiple devices or subscriptions, but the MExE service agreement is tied to the subscription. This distinction is crucial for service provisioning, authentication, and billing in the MExE framework.

From a technical perspective, the MExE subscriber is identified by the subscription credentials stored on the UICC. When the subscriber accesses MExE services, the network authenticates the subscription using standard 3GPP authentication procedures (e.g., AKA for USIM). The MExE service provider may then use additional authentication mechanisms, such as the MExE SIM certificate, to verify the subscriber's identity for specific services. The MExE subscriber's service profile, which defines the services they are entitled to access, is typically stored in the home network's subscription database (e.g., HLR/HSS) and may be shared with MExE service providers through standard interfaces.

The definition explicitly states that access to MExE services through other types of networks is out of scope. This means that if a subscriber accesses MExE services via a non-3GPP network (e.g., Wi-Fi or fixed broadband), they are not considered a MExE subscriber under this definition. This scoping was likely intended to keep the MExE specifications focused on 3GPP access technologies, although in practice MExE services may be accessible via other networks through separate agreements.

The MExE subscriber term has been maintained unchanged from Release 4 through Release 19, reflecting the stability of the underlying MExE service concept. Although MExE services have largely been superseded by modern application ecosystems (e.g., app stores and OTT services), the term remains part of the 3GPP vocabulary and is referenced in specifications related to mobile service provisioning and security.

Purpose & Motivation

The MExE subscriber term was created to define the commercial and technical relationship between end-users and MExE service providers within the 3GPP framework. Before its introduction, there was no standardised way to describe the entity that consumes MExE services, which led to ambiguity in specifications and service descriptions. By defining the MExE subscriber as the owner of a subscription with an agreement with a MExE service provider, 3GPP provided a clear reference point for service provisioning, authentication, and billing.

The term also serves to scope the MExE specifications to 3GPP access networks. By explicitly excluding access via other types of networks, the definition ensures that MExE services are designed and specified with 3GPP access technologies in mind. This was important in the early 2000s when 3GPP was focused on standardising mobile services for cellular networks, and other access technologies (e.g., Wi-Fi) were not yet integrated into the 3GPP ecosystem.

Historically, the MExE subscriber concept emerged from the broader MExE initiative, which aimed to create a standardised execution environment for mobile applications. The subscriber term was part of the vocabulary needed to describe the service model, where subscribers enter into agreements with service providers for specific services. Although the MExE framework has been largely overtaken by events, the term remains a useful reference for understanding the evolution of mobile service models in 3GPP.