Application Application application server objects objects objects communicate via OSA API with framework and service Client Client Client capability servers application A application B application C The framework cares for Service Service Event Integrity authentication/authorization subscription discovery notification management of applications. Additionally SC servers can Authorization register their SC features Authentication Service registration User interation Call control Mobility Connectivity messaging management Service capability servers Generic Connectivity provide SC features (= bundle call control Generic status manager of interface classes) 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 