5 Compatibility of MExE MS’s and applications

02.573GPPMobile Station Application Execution Environment (MExE) Service description Stage 1TS

5.1 MExE classmarks

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

The objective is to:

– classify the capabilities of a MExE MS to support MExE applications and applets; and

– identify the class of MExE MS on which a MExE application and applet may be supported.

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

5.2 MS MExE classmarks

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

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

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

5.3 Application and applet MExE classmarks

MExE applications and applets will be developed to execute in one or more classes of MExE MS’s. In order for MExE applications and applets to be properly supported by a MExE MS, the application and applet shall identify the minimum functional capabilities required of a MExE MS, as defined by the MS’s MExE Classmark.

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

– MExE Application “A” is defined as a MExE Classmark 1 application;

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

– MExE Application “B” is 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 MS’s only.

– MExE Application “C” is defined as a MExE Classmark 2 and Classmark 3 application;

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

– MExE Application “D” is defined as a MExE Classmark 1, Classmark 2 and Classmark 3 application;

the application is identified as suitable for execution on MExE Classmark 1, Classmark 2 and Classmark 3 MS’s.

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

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

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