MExE -> What is MExE?

In addition to the use of standardised network services (e.g. call forwarding, call barring, CCBS, call diversion etc.), MExE provides additional capabilities to control telephony events and manipulate standardised network services in a user-friendly manner.

A MExE handset provides the generic capability to negotiate and interact with services (in the form of applications and content) in servers, other handsets and internet/intranet WebPages etc.  Further, MExE provides standardised execution environments to which 3^rd party software developers may write services to execute directly in the MExE handsets.  

MExE provides the user with a more sophisticated user interfaces (e.g. browsers) with a rich variety of MMI concepts to personalise, 

control and invoke services (e.g.. softkeys, icons, voice recognition etc.).  Additionally downloaded services provide users with the capability to control the “look and feel” of services.

MExE also brings security to the support of 3^rd party services in the wireless handset.  With security domains reserved for network operators, handset manufacturers, and third parties , the source and content of downloaded services may be authenticated by the MExE client.  The provision of such a security model enables the user to control whether services are installed, configure which functions may be performed by services, and to identify the extent of permissions granted to services.  The protection of user data and resources help prevent attacks from potentially fraudulent services.

This annex gives an overview of how new 3^rd generation services may be supported by MExE handsets, and gives some examples of possible services that may be supported on them.  The ability to support some services may depend on the physical handset resources available to the MExE services, the classmark of the MExE client, and handset manufacturers may provide a range of handsets aimed at supporting different types of services.

Access to MExE services

There are several ways in which these new 3^rd generation MExE services may be supported, and the following scenarios give an overview of the possible scenarios.

·         services execute on remote servers

The services are provisioned and execute on remote servers, WebPages etc., to which the MExE client establishes a connection.  The MExE client uses the services as provided by those remote servers. The MExE client effectively receives content (i.e. secured personal financial information) from the remote application which is presented to the user in the MExE client.

·         application downloaded into the MExE client

The services are provisioned and execute on remote servers, to which the MExE client establishes a connection.  The MExE client downloads an application which acts as a local browser to interact with the remotely provided service.  The user interacts with and uses the remote servers via the downloaded application.  An example of such a service would be access to an internet/intranet page.

·         service downloaded into the MExE handset

The services are available from remote servers, to which the MExE client establishes a connection.  The MExE user downloads whichever services he desires from the remote servers, and installs, provisions and configures them on the MExE client.  These services execute directly on the handset, without necessarily relying on servers to support the service. An example of such a service would be a game.

·         MExE handset to MExE handset services

MExE handsets may wish to establish connections with each other to provide, receive and use interactive services. This direct MExE client to MExE client interaction of MExE services and any combination of the preceding scenarios may have been used to download services to the MExE client. These services may execute directly on the handset, without necessarily relying on servers to support the service.  An example of such a service would be interactive games, sharing of calendar information, etc..

<<< MExE Home           Links on MExE>>>