22.0573GPPMobile Execution Environment (MExE)Service descriptionStage 1TS
In order for MExE to be supported over the network, a set of standardised protocols is required to support interaction between the MExE UE and the MExE service environment.
As this specification is not required to propose a specific technology, it identifies the MExE protocols requirements from the service subscriber’s and user’s standpoint. The MExE protocols refers to any protocol layer above the 3GPP system bearers, which interfaces between the MExE service environment and the MExE UE.
The functional capabilities, information flows, signalling system protocols and switching functions needed to implement the service described in this Stage 1 specification will be identified by subsequent specifications at the Stage 2 and Stage 3 levels.
The high level MExE protocols requirements are identified in the subsequent subclauses.
8.1 Optimised Wireless Access
A primary goal of MExE is to provide access to Internet and Intranet services, the standard Internet applications, security and transport protocols shall be one possible set of MExE protocols which is supported. It is noted that these protocols may not cover all the requirements identified in this specification for all classes of ME’s.
A set of application, security and transport protocols optimised for wireless access, and compliant to MExE requirements, shall be specified and form part of the MExE standards.
MExE UE’s shall be able to support either or both of these sets of protocols.
8.2 Wireless network independence
The upper layers of the MExE protocols shall be independent of the type of underlying wireless network so that applications and applets do not need to take into account the specific nature of networks. In particular, lower layers shall provide a generic access API to network bearers so that application and applet developers do not have to cater for the supported underlying bearers. It shall be possible for applications and applets to request specific bearer services and be notified accordingly if they are not available.
The transport layer of the MExE protocols may however be adapted to support the specific features of the underlying bearers. The MExE protocols shall have the ability to use all the underlying bearer services which the MExE UE is capable of supporting.
8.3 Scaleable and extendible protocols
The MExE protocols shall support a scaleable and extendible environment for application and applet development in mobile communication devices. It shall provide a set of generic, non-UE or service-dependent, features. Saleability of the MExE protocols applies to both the MExE UE (e.g. where simple devices do not require the extensive protocols support possibly required by more sophisticated devices) and the network.
The MExE protocols shall support both low bandwidth bearers (e.g. SUE, USSD etc.) as well as medium bandwidth bearers (e.g. anything up to 64kb/s). The introduction of new bearers shall be supported, allowing applications and applets to automatically benefit from their capabilities.
The MExE protocols shall support existing servers and applications and applets, and provide a stable platform for future application development.
8.4 Service independence
The MExE protocols shall be independent of the services communicated over the protocols. The modification in the range of services, or addition of new services, offered over the network shall not be restricted by the MExE protocols.
8.5 Network node type independence
The MExE protocols shall be independent of the network node type(s) being communicated with over the protocols. The MExE protocols shall support the evolution of network node types in a PLMN.
8.6 Enquiry and notification of MExE capabilities
The MExE protocols shall support a generic technology-independent means for the notification by the MExE UE to a MExE server, or enquiry from the MExE server to the MExE UE, of the supported MExE capabilities consisting of:
– MExE Classmark (mandatory, MExE server to MExE UE);
the supported class of MExE UE;
– MExE technology (mandatory, MExE server to MExE UE);
the supported types of MExE UE technology to support MExE services;
– terminal characteristics (optional, MExE UE from MExE server, following MExE server enquiry);
further details of the supportable characteristics (i.e. screen size, MMI capabilities, supportable bearer services, toolkits etc. as constrained by the network, terminal, subscription and user preferences).
In existing networks it may not be possible to determine the network capabilities (i.e. supported bearers) and subscription options of the subscriber.
The above notification by the MExE UE or the MExE server are supported at service initiation, dynamically during the provision of such a service, and following a change in the quality of service (i.e. following a handover, change of network, degradation of service, change in quality of service).
The notification mechanism shall flexibly support notification of the MExE UE, and be able to accommodate future evolution of MExE UE equipment.
8.7 UE request of services information
The MExE protocols shall support a notification from the PLMN or a request from the MExE UE to the PLMN, for information on the (local) services which may be transferred from the PLMN. The information from the PLMN may take the form of listing the services, or references to a PLMN entity (either internal or external to the PLMN) where the available services may be determined.
8.8 Support of transfer protocols
The MExE protocols shall support the capability to transfer new applications and applets to the MExE UE as required. The protocols shall support both user initiated and MExE server initiated transfer of several types of data (content description pages, procedural logic, images, libraries etc.), and be able to indicate the type of data being transferred.
Each specific MExE technology shall be support a standardised transfer mechanism for that MExE technology.