g Empowerment Social communication The same productivity tools wherever they work Safety Figure 8.3 Main user demands Chapter 2 - user-related inputs from chapter 2 - some main user demands are shown in Figure 8.3. Chapter 3 - network-related inputs - the converged structure with media industry input ('person to content'). Architecture: traffic system with control plane and user plane. Management system. H 248. IPv6. API. FP: numbering, routing, switching, synchronization and other plans are necessary. Dimensioning aspects. Chapter 4 - business-related inputs - role(s), business rules, ROCE, OPEX, CAPEX, revenue generation, cost efficiency. Agility in time to market increases market share. Chapter 5 - service plan related inputs - service plan, service classes, business- based features: compression of header, ROHC, compression of payload, charging, need for middleware, impact on core and access network. Service Implementation Chapter 6 - security-related inputs - security goal, enablers and implementation. Chapter 7 - QoS-related inputs - QoS goal, enablers and implementation 8.2 CHAPTER STRUCTURE This chapter examines the support for a vast service plan from a number of angles, starting with the target network (Figure 8.4). In reality, the approach of describing a target network is like shooting at a moving target, with a need for a continuous update. However, the alternative of managing without any kind of target makes focusing almost impossible. In fact the target network used in this book has been partly described in the previous chapters, in particular in Chapter 3. It could be called the 'horizontal, all-access network'. There is also a need for a systematic approach. Figure 8.5 provides support. The struc- ture of this chapter is mapped onto parts of the ITU diagram. However, products and price lists are not treated in this book. The main modifications/additions are: 'Service plan' and 'service enablers' have been added. 'GoS' (grade of service) has been replaced by 'QoS' and 'Digitalization process + ISDN