aluable as possible for the users. Therefore we add to the fundamental plans VAS and IN on the income side and economy of service (Chapter 5, Sections 5.6 and 5.7) on the cost side. As mentioned before IN functions are basically regarded as parts of advanced fundamental plans and do not appear explicitly. VAS and EoS get separate boxes in the overall 'Packet factory' in Figure 8.18. It should be noted that many FPs are necessary at the service layer, with or without support from IN functions implemented in the service layer. EoS includes such cost-efficiency measures as payload compression, e.g. MPEG-4, header compression (especially ROHC), caching and content-based routing. In addition to the boxes shown in Figure 8.18 there are service-supporting middleware/framework functions (see for example Chapter 9, Section 9.3). Other cost-efficiency measures deal with multiplexing and IP aggregation. In this con- text, competitiveness would imply implementing a future-safe architecture, composing Service plan 'Dynamic process' (thick frame indicates separate chapters) (business based) Packet handling control (packet design and/or network) 8, 9, 10 Chapter Service layer VAS resources* QoS incl. numbering routing interconnect adaptations Appl. Access Produced packet logic Chapter "Economy FP signal- Access of service" ling, incl. Development track security dependent functions charging HTTP, SMTP layers (mutual dependence conn. control VS. service plan) Protocol store Billing *Including processing dimension with Java, Net Figure 8.18 Pedagogical support for understanding packet creation and propagation - many other FPs are possible, as mentioned in Chapter 3 Service Implementation an attractive service plan, choosing appropriate service layer enablers and 'Economy of service' functions, and finally tuning the FP 'knobs' for best security, quality and cost efficiency. The service-layer enablers and more about FPs will be covered later. As indicated in Figure 8.17 QoS, security and interconnect FPs are covered in separate cha