02.573GPPMobile Station Application Execution Environment (MExE) Service description Stage 1TS
9.1 MS platform independence
In order to support the objectives of MExE, the ME and SIM is required to have an architecture capable of supporting applications, applets and content in a standardised execution environment, independently of the MExE MS manufacturer.
As this specification is not required to propose a specific technology, it identifies the common platform requirements from the service subscriber’s and user’s standpoint.
The limitations of small devices may result in the provision of the full application execution environment only being available in sophisticated devices.
The high level execution environment requirements are identified in the subsequent subclauses.
9.2 Document mark-up language and other coding formats
In order to cater for a wide variety of ME’s with different display and input capabilities, support for both the standard Internet mark-up language and a content description language optimised for small display devices of low bandwith bearers shall be defined with the MExE specifications. Both languages may be implemented on any MExE MS. Standardised ways of coding content (i.e. images, phonebook, calendar etc.) shall be defined, however the support of such standardised content coding is optional.
In order to facilitate global use of MExE services, a standardised range of character sets for MExE services requires to be defined, and the capabilities of the user and applications to use them.
9.3 MExE APIs
MExE APIs may be defined covering aspects (e.g. Network APIs, Non-network API’s, Terminal APIs etc.) within a given MExE Classmark of MExE MS (ME an/or SIM), and the MExE MS shall support a core API to support the execution of MExE applications and applets. The core API is a the minimal set of API that is present on all MExE MS’s, providing the MExE execution environment in which applications and applets can execute, and is known as the Core MExE API. The Core MExE API consists of generic and GSM/UMTS specific aspects.
Applications and applets which have been designed to execute in this Core MExE API environment (and the optional GSM MExE APIs subsequently identified), will provide additional functions to the MExE MS.
In addition to the Core MExE API on an MExE MS, standardised MExE API extensions such as Network API (e.g. access to call control services, SMS etc.), Non-network GSM/UMTS-defined services API (e.g. security aspects, SIM phonebook etc.), Terminal API (e.g. power management, access to alerting function, phonebook, MMI, smartcard access etc.),shall be subsequently defined and may be supported by the MExE MS in order to further exploit GSM’s capabilities.
The standardised MExE API extensions shall include access to mobility information.