function cater for the access to various network resources. See also the Chapter 9. The application level then becomes the 'melting pot' for all types of IP services/service com- binations, also providing an 'end-user personalized service environment' independent of access type. 3.11.2 MIDDLEWARE Another important part of the solution is the re-use of middleware for different applica- tions. Like service enablers it is positioned roughly between applications and the network connectivity. See Figure 3.37. This area is one of the key success areas. The term can be used in many contexts. For example, for B2B relationships such as e-commerce, the XML (eXtensible Markup Language) middleware may become the standard format. See Figure 3.38. IP is not middleware, rather an overlay technique at the top of the connectivity network. But the impact is similar to middleware: global networking across different underlying networks and a platform for applications. There are several core components in the service layer that can be reused in many solutions. The middleware ties terminals, networks and applications together. The middleware can vary in functionality from 'total middleware' making life simple but inflexible for application designers, to development studios with more work and more flexibility for the designers. For services delivery, the strong direct dependencies between the terminals and a service network are clear, and needs of combined application development for these are obvious. Understanding Changing Telecommunications - Building a Successful Telecom Business Terminals and Applications Applications appliances servers 3rd party 3rd party Generic development development applications based on API Service layer Content adaptation Middleware Middleware framework support Bearer Internet and other bearers adaptation Figure 3.37 Service enablers and middleware have similar positions Business relation User data Charges User segments FAB = Actor-user Content interface, with provision fulfilment, (Billing) Life stage or c