5 Compatibility of MExE UE’s and applications

22.0573GPPMobile Execution Environment (MExE)Service descriptionStage 1TS

5.1 MExE classmarks

Given the wide ranging hardware capabilities of MExE UE’s, together with the development of MExE executables, a MExE classification shall be supported to determine their respective capability and compatibility. The MExE classification shall apply both to UE’s, and MExE executables.

The objective is to:

– classify the capabilities of a MExE UE to support MExE executables; and

– identify the class of MExE UE on which a MExE executable may be supported.

The concept of a MExE Classmark is introduced to manage the MExE UE and MExE executable classification and compatibility. The MExE Classmark is distinct and unrelated to the existing UE Classmark. The use of MExE Classmarks shall be supported during the capability negotiation between the MExE service provider and the MExE UE.

5.2 UE MExE classmarks

A given MExE Classmark shall identify a category of MExE UE supporting MExE functionality with a minimum level of processing, memory, display and interactive capabilities.

Specification of different MExE Classmarks enables use of a variety of technologies to support MExE functionality.

A given MExE Classmark identifies support by a MExE UE for a defined level of MExE functionality. This does not necessarily imply support of other MExE Classmarks. A MExE UE may support multiple MExE Classmarks.

The minimum level of capabilities for each MExE Classmark is beyond the scope of this Stage 1 service description. As UE development evolves and more sophisticated devices (or indeed simpler devices) become available, further UE MExE Classmarks shall be definable to identify UE’s capable of supporting improved (or additional) MExE functionality.

A given MExE UE Classmark identifies support by a MExE UE for a defined level of MExE functionality, but does not necessarily imply support of other levels of MExE Classmark. A MExE UE may also support multiple MExE Classmarks.

5.3 MExE executables and MExE classmarks

MExE executables will be developed to execute in one or more classes of MExE UE’s. In order for MExE executables to be properly supported by a MExE UE, the MExE executable shall identify the minimum functional capabilities required of a MExE UE, as defined by the UE’s MExE Classmark.

MExE executables shall be designated by the same classes of MExE UE’s on which they may be executed. Examples of the classification of MExE executables are as follows:-

– a MExE executable can be defined as a MExE Classmark 1 application;

the application is identified as suitable for execution on MExE Classmark 1 UE’s only.

– a MExE executable can be defined as a MExE Classmark 2 application;

the application is identified as suitable for execution on MExE Classmark 2 MS’s only.

– a MExE executable can be defined as a MExE Classmark 1 and Classmark 2 application;

the application is identified as suitable for execution on MExE Classmark 1 and Classmark 2 UE’s only.

The above example list is neither complete nor exhaustive.

If a MExE executable is capable of being supported by other classes of MExE UE’s (with reduced or enhanced capabilities), it is the responsibility of the MExE service provider to re-classify the MExE executable accordingly.

MExE executables defined by a MExE service provider to a given class of MExE UE, shall be supportable by all MExE UE’s of that class regardless of MExE UE manufacturer. MExE executables shall operate on differing MExE UE of the same MExE UE class without modification.

It shall be possible for MExE service providers to make the same MExE executables available in the network for different classes of MExE UE. It is desirable that MexE executables are backward compatible within a given technology and for a given UE Classmark; however such backward compatibility is out of scope of this specification.