rk for standardized business documents such as B2B) business documents are sent as XML (eXtensible Mark-up Language) based messages as a standard. The XML documents are structured in the same way as traditional electronic data interchange (EDI) documents, in order to facilitate the migration from EDI to CBL based systems. XML web services are a tool for service interchange (service here stands for a functional software module). XML web services could become, for the service layer, what IP is for the transport layer. This will have impact on terminals as well. 9.8 THE NEEDS OF THE SERVICE NETWORK OWNER 9.8.1 TELECOM BUSINESS DOMAIN The main needs are: Support for business development and planning - business layer in the TMN (telecom- munications management network) pyramid for the service network. Service Network Services with common functions Service layer Single-sign-on Common charging Common O&M Common directory Common provisioning Telecom grade: Scalability and redundancy Security and manageability Figure 9.8 Cost efficiency in the service network. A third dimension is provided by for example location-based services, which can be combined with the vertical services Service extensions to stay competitive - new enablers. Reduced OPEX, CAPEX. A future-safe framework and service infrastructure. FAB support 9.8.2 COMMON USE OF RESOURCES A common use of the resources and processes provided by the service network gives a better ROCE. See Figures 9.8 and 9.9. The common resource goal is most applicable for public service networks. Enterprise service networks tend to be more tailored, and even more vertical. The common resource goal is most applicable for public service networks. Enterprise service networks tend to be more tailored, and even more vertical. Management The business 'pyramid' is under transformation (see Figure 9.10). When services beyond voice take a larger part of the overall service market, service and business management will start migrating to the service layer. Development, launching, billing and ma