ice enablers To be added for example: Single Sign On, WAP (MExE), XML middleware notification, directory access, charging, security, QoS, service configuration, service activation, service execution, network access. (Registration, discovery) Figure 8.20 Service enabler position in the network Service Implementation opens up a new range of applications based on this feature, where you might for example have a taxi ordering application that knows in which city you are. Other examples of enabler support in terminals are multimedia messaging service (MMS), video playback and Bluetooth. All of these enablers open up a new set of appli- cations for the user. Just as the networks themselves have migrated by adding first GPRS and then 3 G, these enablers add more and more applications capabilities step by step. WAP and SMS were followed by enhanced message service (EMS, see Chapter 5) and SyncML (see below). Even more recent are Java and MMS and video playback. See Table 8.1. From the application point of view this is what decides what the GPRS and 3 G applications will be, not primarily the networks themselves. This means that you can actually know what categories of applications there will be in 3 G networks by knowing what enablers the 3 G terminals will support. The goal of SyncML is that the devices will be entirely plug-and-play with any data stored on any network, enabling a device to synchronize and update with any database, in any location, at any time. Without the ability to access and manipulate accurate data at any time and from any place, mobile devices lose their value. The challenge is to develop mobile applications that are accessible on multiple handheld devices in areas of intermittent wireless coverage, which will still allow users to access data with a 'change once - update everywhere' feature. See also Chapter 5. Table 8.1 Four sample enablers Enabler Handset/Network Main added Example support needed capability applications WAP 1.1/2.0 Handset and network Transactions and Buy cinema tickets, viewing 