es) to messaging applications. SCSs are Multi-party logical, not physical entities call control location Multimedia location call control CAMEL Generic user Conference Enterprise interaction call control emergency network location Different kind of network entities/servers realize the functions physically, which Location are offered by SC servers HLR/GPS through their SC features UMTS/GPRS/EDGE Figure 9.7 Framework functions are situated between applications and the SCSs. Very often the 'WAP layer' is included in SCS and service enablers will be treated here: SAT and MExE. WAP is briefly treated in Chapter 5. OMA uses the name service enabler as well. SIM Application Toolkit (SAT) SAT offers the flexibility to update the SIM to alter the services and download new services over the air (OTA). For example, network operators can remotely provision the user's wireless terminal by sending codes embedded in short messages from the server. Within the SAT specification, SMS is a key mechanism for personalizing the SIM in each user's phone. A SAT browser resident on the SIM card can execute different Internet applications. SAT-enabled terminals are able to access the same services as WAP terminals. SAT comprises two components: SAT in the network. SAT browser in the terminal. SAT connects to Internet applications via HTTP. SAT makes it possible to download applications to the 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 executi