13 Network interworking
22.0573GPPMobile Execution Environment (MExE)Service descriptionStage 1TS
All services offered in co-operation with other networks shall continue to be offered in combination with MExE. This includes the basic services, supplementary services and network features.
The interworking characteristics of individual MExE services with other networks is outside the scope of this specification.
Annex A (informative):
Example MExE services
Overview
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 3rd 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 3rd 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 3rd 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 3rd 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..
Example MExE services
Once they have been downloaded, these MExE services may then be configured, personalised and executed on the MExE handset by the user. A MExE handset may support a diverse range of services, providing a dynamic and evolutionary set of facilities to users. The support of this unlimited range of new services, will convert a mobile handset from being a device which simply makes and receives calls and messages, into a multifunctional leisure and business device.
An analogy may be made with a personal computer, where the user can install and configure any type of application that he so chooses, establish multimedia call sessions, and convert the laptop into a multi-faceted device (e.g. slideshow presenter, video box, music jukebox, arcade games machine, protocol analyser, e-mail, messaging and information server etc.). In fact, MExE may simply be considered to be similar to a small computer supporting wireless telecommunications capabilities.
Manufacturers are expected to produce MExE devices with different levels of resources, memory and processing power to exploit the growing number of applications and market niches.
The list of possible services that may be supported by a MExE client is virtually unlimited, and the following are example services that could be supported by a MExE client.
Applications
Applications may be downloaded and installed on the MExE client to provide a wide range of standalone services.
The user downloads and installs the software into the MExE client, configuring and installing it as required. Examples of such applications are phonebooks, diaries, planners providing similar functionality to current popular handheld PDA devices. Likewise, games may also be downloaded and installed providing similar functionality to current popular handheld games devices and other entertainment and leisure services.
Additionally, interactive working with other devices and servers (i.e. on-line gaming, gambling, messaging etc.) could also be generically supported.
Browsers
Applications may be downloaded and installed on the MExE client to support browser functionality already experienced by many users today with personal computers. Examples of this are internet and e-mail browsers.
Web browsing
A MExE client can be used by the user as an internet/intranet web browser by downloading and installing a web browser.
Just like the internet browser on a personal computer at home or in the office, the user is able to access the internet/intranet. Similar to accessing the internet via a personal computer, the user is able to surf the web viewing pages, images, animation and download content using standard internet HTTP and HTML protocols. By interaction with the installed web browser, the user is also able to customise his web browser to present the internet/intranet to the user in his accustomed way.
A user can convert his MExE client into an e-mail handler by downloading and installing an e-mail browser.
Working the same way as an e-mail browser on his desk bound personal computer, the user is able to send and receive messages on the move. As with existing personal computer implementations e-mails with audio, visual and textual attachments may be exchanged with an e-mail server, using the standard e-mail SMTP, POP3 and IMAP4 protocols. Directly supported by the e-mail browser on the MExE client, the user may personalise his e-mail service and manage e-mails on remote e-mail servers.
Players
Players are a specialised type of application which the user may install on the MExE client. These players enable content to presented to the user in a specific manner, depending on the content format. Audio and video players are examples of such specialised applications.
Music players
A MExE client may also be used by the user as a portable music player by downloading and installing a music player application.
Once the music player application is installed, the user is then able to download music content using popular music formats available from the internet or third party servers.
Similar to the player applications already available on the internet and personal computers today, the user may be able to play popular music formats like MP3. Further, specialised music content may also be played by downloading and installing the appropriate compliant player.
By downloading and installing a music player, the user is able to obtain functionality from the MExE client similar to current popular handheld music devices.
Video players
Similar to the music player, a MExE client may also be used by the user as a portable video player by downloading and installing an appropriate video player application.
Once the video player application is installed, the user is then able to download video content using popular music formats like MPEG4 available from the internet or third party servers.
Annex B (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
Work Item |
|
Jun 1999 |
22.057 |
R99 |
Transferred to 3GPP SA1 |
8.0.0 |
3.0.0 |
||||||
|
SP-05 |
SP-99479 |
S1-99619 |
22.057 |
001 |
R99 |
D |
Editorial changes for alignment |
3.0.0 |
3.0.1 |
||
|
SP-09 |
SP-000381 |
S1-000626 |
22.057 |
002 |
R4 |
D |
Mobile Execution Environment |
3.0.1 |
4.0.0 |
||
|
SP-09 |
SP-000388 |
S1-000428 |
22.057 |
004 |
R4 |
D |
MExE Release 2000 |
3.0.1 |
4.0.0 |
||
|
SP-09 |
SP-000388 |
S1-000428 |
22.057 |
005 |
R4 |
B |
MExE Classmark updates |
3.0.1 |
4.0.0 |
||
|
SP-09 |
SP-000388 |
S1-000628 |
22.057 |
003 |
R5 |
B |
MExE support of multimedia services |
3.0.1 |
5.0.0 |
||
|
SP-11 |
SP-010043 |
S1-010202 |
22.057 |
006 |
Rel-5 |
B |
MeXE service discovery |
5.0.0 |
5.1.0 |
MEXE-ENHANC |
|
|
SP-13 |
SP-010440 |
S1-010629 |
22.057 |
007 |
Rel-5 |
F |
Generic requirements for support of multiple MExE classmarks |
5.1.0 |
5.2.0 |
MEXE-ENHANC |
|
|
SP-15 |
SP-020045 |
S1-020457 |
22.057 |
009 |
– |
Rel-5 |
A |
Editorial CR to correct terms and references |
5.2.0 |
5.3.0 |
CORRECT |
|
22.057 |
– |
– |
Rel-5 |
Correction to history box |
5.3.0 |
5.3.1 |
|||||
|
SP-16 |
SP-020246 |
S1-021057 |
22.057 |
010 |
Rel-5 |
F |
CR to 22.057 on Correction usage of MExE application |
5.3.0 |
5.4.0 |
MEXE-ENHANC |
|
|
SP-26 |
SP-040744 |
S1-040997 |
22.057 |
Rel-6 |
Updated from Rel-5 to Rel-6 |
5.4.0 |
6.0.0 |
||||
|
SP-36 |
22.057 |
Rel-7 |
Updated from Rel-6 to Rel-7 |
6.0.0 |
7.0.0 |
||||||
|
SP-42 |
– |
– |
Rel-8 |
Updated from Rel-7 to Rel-8 |
7.0.0 |
8.0.0 |
|||||
|
SP-46 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-9 by MCC |
8.0.0 |
9.0.0 |
|
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-11 by MCC |
10.0.0 |
11.0.0 |
|
|
2014-10 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|