1 / 14

Mobile Station Application Execution Environment (MExE) Java and WAP ETSI/SMG4 and 3GPP

Mobile Station Application Execution Environment (MExE) Java and WAP ETSI/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.

joie
Download Presentation

Mobile Station Application Execution Environment (MExE) Java and WAP ETSI/SMG4 and 3GPP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mobile Station Application Execution Environment (MExE) Java and WAPETSI/SMG4 and 3GPP

  2. MExE - Classmarks MExE Classmark 1 : WAP MExE Classmark 2 : Java + WAP

  3. 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 ?

  4. 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. 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

  6. Bandwidth

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

  8. 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

  9. 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

  10. WAP & JavaComparison

  11. 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

  12. Comparison on capability ability to access phone capability Java WAP Now 2000/1 Future

  13. MExE - User Profile/Capability Negotiation Alignment with WAP Forum

  14. 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.

More Related