tween the user and the content source. The business models are not yet stable. This meeting point for users and the different actors in the value chain is a melting pot of technologies, from general computing trends to telecom-oriented technique. Let us look at all the standard bodies that are involved in service layer matters: here we find 3GPP, W3C, IETF, Parlay, ETSI and OMA, to take a number of important ones. One of the hottest technical areas is software as a service, such as web services. This is a promising area, indeed. However, it needs further standardization and implies some security and QoS risks when software from different sources need to cooperate. Company business technique is found in the idea of the Open Market Alliance (OMA), which offers enabling technology for delivering relevant, end-to-end high-performance services (see Figure 9.4). OMA was formed on 12 June 2002, but it is already a very important player in the area. 9.4 SERVICE NETWORK DOMAIN AND PRINCIPLES The service network can be structured into a number of 'domains' that cooperate and fill the original space in the interfaces between the converging parties. A domain is justified provided it gives smooth support to the business. Let us take some examples of needs: Service Network The user needs support to securely sign on to the network, to upgrade the terminal with new applications, and to communicate with sufficient QoS. A personal portal is also appreciated. The application provider and value-added service provider do not know the network, and need assistance to utilize all the possible enablers when creating new applications (there are other media industry oriented roles as well). The actor running the service network needs support from an IP network to get all necessary servers to cooperate properly. All domains in this chapter appear in Figures 9.3 or 9.4. The service network owner domain has two shapes: the technical solution domain and the management function domain. The technical solution ideally provides a common service fr