Maintenance CAS = Customer administration Acc. and billing Location Presence Messaging Application Etc. system proxy General framework, middleware Figure 9.4 The spider role of the service network based on an OMA structure Whereas Chapter 8 primarily is a technique integrator in this book, Chapter 9 is an overall integrator. Chapters 2 and 4 become especially important now because of the spider role of the service layer and its main component, the service network. As mentioned before, the service network is a product of the converging telecom, datacom and media industries. The first stage was the functions of the ISP, as the tele- com intermediary between 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 