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 framework machinery for services over all access systems. The framework sup- ports virtually any type of service, that is telecom, data, Internet, multimedia. Sometimes the framework is referred to as a middleware framework or the service network platform. The user domain. The domain of cooperating roles, such as content provider, value-added service provider, application provider etc. The domain of the core (and access) network. The domain of the IP network that connects the elements of the service network. Basic ideas and tasks of the service network are: To be a kind of spider that connects application providers, representing society needs and integration of telecommunications, with the users with their personal needs, with the service providers with their needs to be able to efficiently administer the exploding service area, and finally with the network for transport to the user. In the spider role, to ensure that everything works together based on interoperability between communication segments and providers. Employment of common utilization of resources for cost-efficiency reasons. Implementation of the OMA concept and/or Parlay3GPP Open System Architecture and Virtual Home Environment (OSA/VHE) towards application providers. Provision of access independence and personalization of the subscribed-to services to the user, catering for end-user integrity, privacy and