6 General MExE requirements

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

6.1 High level MExE requirements

The high level requirements of MExE are as follows:

– the means for MExE service provider specific services to be supported by all mobiles of a particular class (i.e. the need for a common set of APIs and development tools), and accessible across a range of networks;

– provide the user with a more sophisticated user interfaces (e.g. browser-like) with a rich variety of MMI concepts to control and invoke services (i.e. softkeys, icons, voice recognition etc.);

– the user’s and MExE service providers capability to control the “look and feel” of applications and applets;

– the ability of the user to personalise the user interface;

– the ability of the user to personalise services;

– provide support of a wide variety of applications and applets;

– provide the means for MExE service providers to authenticate MExE subscribers;

– provide the user access to Internet and Intranet based applications and applets (via both standard Internet and Wireless optimised protocols);

– the means to transfer applications, applets and content automatically or on demand to a MExE MS from a MExE service provider, and upgrade existing applications across the GSM network;

– the means to support direct MExE MS to MExE MS interaction of MExE services;

– the need for an inherent security architecture such that both the MExE MS and MExE server sides of a connection are authenticated (possibly by a brokerage server), and have access to a range of encryption and security functions in order to maintain the security and integrity of the GSM network. The MExE service provider shall maintain security of subscribers personal data and GSM network data, with all aspects relating to GSM security being centred on the SIM;

– the ability for the MExE service provider to charge subscribers for MExE service provider provided MExE services, at connect time, when downloading, or on usage;

– the means for MExE service provider specific applications and applets on the MExE MS to communicate with other GSM network nodes (e.g. a SCP);

– the ability to provide information to MExE service providers (e.g. location information of MS’ for use with location dependent services);

– the means for MExE service providers and their applications and applets to determine MExE MS capabilities (i.e. MExE Classmark, technology, supported bearers according to network capabilities and GSM subscription etc.). (This shall be used by MExE servers to adapt application and applet transfer to MExE MS capabilities, and shall be used by applications and applets whilst running to adapt their behaviour to the MS’s capabilites.);

– the opportunity for MExE service providers to apply expertise and software developed for other platforms;

– provision of APIs and tools to develop MExE services which are applicable for MExE MS’;

– the means for the user to manage (i.e. identify version, delete, modify, save etc.) the applications, applets and content on the MExE MS;

– the means for the user to control acceptance (i.e. by Security Level, level of trust etc.) of applications, applets and content transferred to the MExE MS. (It shall be possible for the user to finely control a trusted application or applet’s access rights on the MExE MS, such as reading/writing/deletion of files stored on the MExE MS.).

Some of the above requirements are subsequently elaborated.

6.2 Requirements description from the user’s standpoint

MExE provides an improvement in the capabilities of an MS, as well as an extended range of services available to the user from, or via, the network. The user shall have

– user interface configuration management; and

– service management;

of the services offered to him by MExE.

6.2.1 User interface configuration management

User interface configuration management refers to the behaviour of the MExE MS, and the ability of the user to modify the MExE MS to behave in the manner he is accustomed to, or wishes the MExE MS to, present itself to the user. It does not refer to the services which interact with the network, but the way in which the MExE MS interacts with the user.

Users expect MExE MSs to offer an increasing range of capabilities which need not be ubiquitously present on each MExE MS, depending on the technological limitations of the MExE MS. The user shall be able to manage the user interface configuration of the MExE MS. For example, some user’s may require a voice-controlled MMI, whilst others may have the need for a specialised presentation on the MExE MS display or preset function keys regardless of the application or applet which is running. Management of the user interface configuration will permit a user to move from MExE MS to MExE MS and exploit the technological capabilities of each class of MExE MS, with the use of varying services downloaded from the network, as required.

The user shall be able to identify (either directly or indirectly) the user interface configuration he wishes to add, modify or delete on his MExE MS, and shall be offered the means of doing this. This management may be performed, for example, by a configuration capability profile.

In taking this action, it shall be possible to determine whether the user interface configuration is already resident on the ME, or whether it requires to be obtained from the SIM or the network. The modifications which may be requested by the user could result in, for example, differing display characteristics being employed, redefinition of keys, modification of the “look and feel” of the user interface, touch screen facility, extensions to existing functions or the capability to automate some functions.

The control of the “look and feel” of MExE applications and applets to customise their level of functionality and appearance may be possible by the MExE service provider, network operator (where the MExE service provider is not the network operator) and the user. The aspects of the application or applet which may be customisable are determined by the MExE service provider as an integral part of the MExE application or applet.

The user interface configuration management which is specific to the ME shall be stored on the ME, and user interface configuration management which is generic to ME’s may be stored in the network or on the SIM.

The definition of the user interface configuration management which may be offered to the user is outside the scope of this service description.

6.2.2 Service management

MExE shall provide the ability to customise the range of services offered to the subscriber. The subscriber’s ability to configure the services available on the MExE MS shall be dynamic, as the range of services required may differ depending on the network, time and location that the user finds himself in. For example, a subscriber may require access to services offering financial support when attending a business meeting, however later in the day he may need access to travel information and booking facilities when re-arranging his travel home.

A common address across all PLMN supporting MExE shall be available, from which the user shall be able to request the range of MExE services available he is registered in, if the PLMN supports MExE. The downloading of services may be autonomously controlled by the MExE MS to update existing service access on the mobile, or to download new services. The management of these services may be defined by the subscriber directly or under the control of the MExE MS’s capabilities organised on the MExE MS (i.e. a user may be particularly interested in unified messaging services, and require the availability of such services to be made available to him).

The user shall be able to determine and manage which MExE applications, applets and content may be transferred to the MExE MS (i.e. in terms of their security level, source of the applications etc.), determine and manage which MExE applications, applets and content are currently resident and usable on the MExE MS (e.g. when roaming some services may not be available to the user), and delete MExE applications, applets and content on the MExE MS.

The definition of the applications, applets and content which may be offered to the user is outside the scope of this specification.

6.3 Requirements description from the MExE service provider’s standpoint

6.3.1 Transfer of applications, applets and content

A common mechanism shall be available to perform the transfer of applications, applets and content between MExE MSs’ and the MExE service provider.

The common transfer mechanism shall permit applications, applets and content (according to the appropirate MExE Sercurity Level) to be transferred to the MExE MS.

It shall be possible for the MExE service provider to:-

– transfer applications, applets and content between the MExE MS and the MExE service provider (which may be initiated by either party);

– request the version of applications, applets and content on the MExE MS;

– identify the MExE MS’ capabilities;

– support a request from the MExE MS for information on the (local) services which may be transferred from the network.

Some of these functions may be used by the MExE service provider either individually, or together to automatically update previously transferred services.

6.3.2 Network node types

The introduction of MExE shall enable an expansion of services available to the user from various network node types.

The MExE MS shall be able to communicate with the various network node types in the MExE service environment, allowing access to intelligent nodes to process service requests from the MExE MS.

6.3.3 Subscriber data

Subscription to MExE services shall be logically separate to subscription of GSM services. A subscriber may have a MExE subscription to multiple MExE service providers. It may also be possible for the subscriber to interrogate such subscription registration (with a suitable means of authorisation), depending on PLMN support.

6.3.4 Roaming subscribers

Roaming MExE subscribers shall be able, as far as possible, to access their normal MExE services in their HPLMN.

As usual when roaming, it cannot be ensured that the VPLMN can provide the subscriber access to the same MExE services (e.g. applications, applets and content) as he is accustomed to. However, in the VPLMN additional MExE services may be available, depending on network capabilities. Service continuity when roaming is dependent on the availability of the services in the VPLMN, and is outside the scope of this specification.

The operation of the transferred applications, applets and content may be location dependent, and their behaviour when in an different location is outside the scope of this specification.

The following forms of MExE subscriber roaming are identified:-

– roaming between networks (HPLMN  VPLMN);

– roaming between visited networks (VPLMN  VPLMN);

– regional roaming within a network (within the HPLMN or VPLMN).

There may be a need to distinguish between the above types of roaming from a MExE services management perspective, as the operation of location dependent MExE services may be affected when the MExE subscriber roams beyond the boundaries of a PLMN or region.