1. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 Mobile Station Application Execution Environment (MExE) Java and WAP ETSI/SMG4 and 3GPP

2. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 MExE - Classmarks MExE Classmark 1 : WAP MExE Classmark 2 : Java + WAP

3. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 Why is MExE important to WAP ? MExE will be THE recognised execution environment for 3rd. Parties by 3G. MExE will support service capability for VHE - Virtual Home Environment. MExE is important for GSM/UMTS and 3G. MExE brings JavaPhone and WAP together. MExE requirements must be in sync with WAP

4. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 MExE-WAP Alignment 1. User Profile, Capability negotiation 2. Security - Execution, capabilities, certificate management/formats/infrastructure, domains/levels. 3. More input into MExE specs - (1), (2), WML and alignment of Java API’s. 4. WAP and MExE Timescales alignment. MExE - R98 - End of June 1999 MExE - R99 - End of December 2000.

5. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 Downloadable applications MExE phone 3rd. Party developers Downloadable applications and service connectivity operators 3rd. Party service providers Service connectivity Internet! VASApplications Priveleged access to functionality

6. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 Bandwidth

7. WAP for Low Bandwidth Via Web proxy WAP services WAP protocol stack WML Browser GSM MExE phone

8. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 Intermediate WAP services Internet Protocol WAP stack HTML /WML Browser Web services Data call IP via PPP Via Web proxy WAP services GSM MExE phone

9. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 WAP & Java for High Bandwidth, IP WAP services Internet Protocol HTML /WML Browser Web services IP, WML content HTTP request, HTML content MExE phone

10. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 WAP & Java Comparison

11. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 Platform Independent (as long as it is a phone) Functionality Platform Independent (as long as it is a phone) Functionality Industry Standard Large developer pool Compact Currently being implemented ConveniencePower

12. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 Comparison on capability ability to access phone capability Now2000/1Future Java WAP

13. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 MExE - User Profile/Capability Negotiation Alignment with WAP Forum

14. MExE - SMG4/3GPP T2 SWG1 - April 12 1999 User Profile - MExE Vision Moving from Handset A to Handset B (user preferences) Personal information such as voicemail number, language preference, etc (retrieved from network or SIM) Capability/Content negotiation - Hardware Profile, Software Support (images, video, audio, etc), some user preferences - Java - internet - http based mechanisms (ME based and not portable) WAP - input needed User profile formats. - No work (USE WAP EFFORT) Some work on capability negotiation tokens - need to align with W3C and WAP User profile transfer mechanisms - No work Java User Profile API’s - April 30, 1999 Secure transfer of user profiles and actual mechanisms for transfer. Functionality Work in Progress