terminal and perform high security operations. Web applications are downloaded to the SIM card using standard protocols. Once the SIM card receives a web application from a content provider, the web application is Service Network executed, resulting in a number of SIM toolkit commands sent to the mobile phone, allowing interaction with the user. Mobile Execution Environment (MExE) MExE is a standardized execution environment in a mobile device. The aim of MExE is to provide a comprehensive and standardized environment on mobile terminals, for execution of operator or service provider specific applications. MExE is designed as full application execution environment and builds a Java Virtual Machine into the client mobile terminal. MExE enables a standardized open architecture for the MS (mobile station) includ- ing content and application download mechanisms and an environment to execute those applications. ETSI has determined that two technologies should be accommodated within the MExE framework: Wireless application protocol (WAP), which brings Internet content and advanced ser- vices to digital mobile phones and other mobile terminals. Java, which brings platform independence and built-in network awareness. On the network side, MExE comprises the WAP gateway. 9.7 THE NEEDS OF THE USER DOMAIN In this book the user is queen/king, SO these needs are crucial. Important needs are: Consumers: ease of use, single sign-on functionality, personalization, availability, secu- rity and service range. Business: Cost-efficient internal processes, mobility, personalization, IS and IT out- sourcing. 9.7.1 EASY-TO-USE-SERVICES The services must be easy to use, for example according to the 0,1,2,3 solution with single sign on to content in a personalized portal: 0. No manuals needed for configuration. Device Management and configuration are per- formed by means of an OTA server. 1. One-button access to mobile Internet (AAA, single sign-on, MSISDN forwarding, handsets with a mobile Internet button and support for OTA or equivalen