opefully give the reader a feeling of animation. Traffic cases are often described as sequential processes, and can be used to further support the process thinking. The traffic case in Chapter 8, section 8.10 contains many fundamental plans, indicated in Figure 9.2 with a darker shade. This figure also indicates the early position of the service layer in the flow, by means of a thick arrow. Regarding the business side the following references in other chapters are relevant examples. Chapter 1 - Easy-to-use, affordable, making life easier (Mäkitalo), society-oriented ser- vices (Malm, Thorngren). Chapter 2 - No specific answer on consumers is possible. The human end user as a traffic generator is relevant. Regarding consumers in general it is recommended to start by testing the market using existing systems (see Malm, Thorngren in Chapter 1). Chapter 2 - xSP according to Table 2.1. Also IS/IT outsourcing, support to internal processes, mobile enterprise and enterprise processes (SCM, ERP, CRM). Chapter 4 - Figures 4.2 and 4.3 are pertinent. Much of Section 4.4 is relevant, in particular the introduction. Figure 4.15 and terminology, such as HE-VASP and MVNO. Figures 4.25 and 4.26 and consequences for the service layer. The main part of Section 4.6 is relevant as well. 9.3 WHAT IS A SERVICE NETWORK? A service network is a logical IP-based network for end-user services that goes 'beyond voice'. Service networks serve public subscribers as well as enterprises and society. The Service Network Service network Application server server management Business support server server Network management CRM customer rel. server system management Directory CAS customer adm. system user profile Charging control IP infrastructure Portal BGW billing gateway (backbone) engine Pre/post processing cost control node Personal Notification service environment support WAP-GW management Charging support Application Mobile support PSTN,ISDN E-pay Bearer access Internet VAS service enablers IN services CONTROL CONNECTIVITY Figure 9.3 An exam