Mobile Execution Environment MExE

1
Mobile Execution Environment (MExE)
2
References

• 3GPP TS 22.057 V4.0.0 (2000-10)
• Mobile Execution Environment (MExE) Service
  description
• 3GPP TS 23.057 V4.1.0 (2001-03)
• Mobile Execution Environment (MExE)
• Functional description

3
Outline

• Abbreviations
• MExE- Mobile Execution Environment
• MExE classmarks
• Generic MExE aspects
• General MExE requirements
• Access to MExE Service
• Example MExE services

4
Abbreviations

• ME Mobile Equipment
• MExE Mobile Execution Environment
• MMI Man Machine Interface
• UE User Equipment
• PLMN Public Land Mobile Network
• CLDC Connected Limited Device
  Configuration
• MIDP Mobile Information Device Profile

5
MExE- Mobile Execution Environment

• provides a standardised execution environment in
  an UE
• an ability to negotiate its supported
  capabilities with a MExE service provider
• allowing applications to be developed
  independently of any UE platform.

6
MExE classmarks

• The one-size-fits-all approach is unrealistic.
• The objective is to
• - classify the capabilities of a MExE UE to
  support MExE applications and applets and
• - Identify the class of MExE UE on which a
  MExE
• application and applet may be supported.
  
• The MExE Classmark is distinct and unrelated to
  the existing UE Classmark.

7
Generic MExE aspects

• MExE classmarks are defined
•   MExE classmark 1 - based on WAP
• This classmark supports small devices,
  typically witch limited
• display , processor and memory
  resources .
•     MExE classmark 2 - based on PersonalJava
• - provides and utilises a run-time
  system requiring more processing, storage,
  display and network resources, but supports more
  powerful applications and more flexible MMIs.
• MExE classmark 3 based on J2ME CLDC and
  MIDP environment
• supports Java applications running on
  resource constrained devices.

8
General MExE requirements(1/2)

• from the user's standpoint
• The user shall have
• user interface configuration management and
• 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 UE, and shall be offered the means of
  doing this. This management may be performed, for
  example, by a configuration capability profile.
• service management
• MExE shall provide the ability to customise
  the range of services offered to the subscriber.
• of the services offered to him by MExE.

9
General MExE requirements(2/2)

• from the MExE service providers standpoint
• Transfer of applications, applets and content
• The MExE service provider to transfer
  applications,
• applets and content between the MExE UE
  and the
• MExE service provider .
• Node types
• The MExE shall enable an expansion of
  services available to the
• user from various network node types.
• Subscriber data
• Subscription to MExE services shall be
  logically separate to subscription
• of network services
• Roaming subscribers
• Roaming MExE subscribers shall be
  able, as far as possible, to access
• their normal MExE services in their
  HPLMN.

10
Other requirements

• MExE bearer requirements
• Bearers available to MExE applications depend on
  those supported by the MExE UE that are
  available.
• MExE protocols requirements
• In order for MExE to be supported over the
  network, a set of standardised protocols is
  required to support interaction between the MExE
  UE and the MExE service environment.
• UE application execution environment requirements

11
Access to MExE Service-services execute on
remote servers
Request web page
12
Access to MExE Service-application downloaded
into the MExE client
i.e. Java applet
13
Access to MExE Service-service downloaded into
the MExE client
i.e. game service
14
Access to MExE Service-MExE handset to MExE
handset services
i.e. interactive games sharing of calendar
information
15
Example MExE services(1/3)

• Once they have been downloaded, these MExE
  services may then be configured, personalised and
  executed on the MExE handset by the user.
• 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.

16
Example MExE services(2/3)

• Applications
• Applications may be downloaded and installed on
  the MExE client to provide a wide range of
  standalone services.
• 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.

17
Example MExE services(3/3)

• Web browsing
• downloading and installing a web browser.
• E-mail
• downloading and installing an e-mail browser.
• Music players
• downloading and installing a music player
  application.
• Video players
• downloading and installing an appropriate video
  player application.