Mobile Station Application Execution Environment (MExE) Java and WAPETSI/SMG4 and 3GPP
MExE - Classmarks MExE Classmark 1 : WAP MExE Classmark 2 : Java + 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 Why is MExE importantto WAP ?
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.
Priveleged access to functionality 3rd. Party service providers 3rd. Party developers Internet! operators Service connectivity Downloadable applications and service connectivity Downloadable applications MExE phone VAS Applications
WAP for Low Bandwidth Web Server WAP Server Internet WAP services Via Web proxy GSM MExE phone WAP protocol stack WML Browser
Intermediate Web Server Web services WAP Server WAP services Internet WAP services Via Web proxy GSM Data call IP via PPP Internet Protocol WAP stack HTML /WML Browser MExE phone
WAP & Java for High Bandwidth, IP Web Server Web services WAP Server WAP services Internet , WML content HTTP request, HTML content IP MExE phone Internet Protocol HTML /WML Browser
Compact Currently being implemented WML Script Java 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 Convenience Power
Comparison on capability ability to access phone capability Java WAP Now 2000/1 Future
User Profile - MExE Vision Functionality • 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 Work in Progress 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 transferof user profiles and actual mechanisms for transfer.