ing different mobile applications. This situation does not help the adoption of new services. In order to overcome this limitation, service awareness can be introduced, both in the mobile terminal and in the GGSN hosting Core Network Planning and Optimisation the APN. In the latter case, new additional aspects should be considered during the planning phase of this type of GGSN node. 4.16.4 QoS Performance Management The previous section gives a good understanding of the complexity of handling QoS in the context of different users and different services, based on a simplified approach of utilising templates or profiles for predetermined sets of QoS parameters. This complexity has been an inherent part of the concept from the standardisation phase, a notable example being the different sets of parameters standardised in release 97/98 of the 3GPP specifications and the parameters standardised in release 99 of the same 3GPP specifications. Therefore, the different sets require a proper mapping between the parameters. However, the amount of parameters and their possible values, originally proposed for providing great flexibility during the service design, create such a large amount of possible combinations of parameters that it would potentially make the performance management of a given service impossible. In turn, without an adequate level of performance management capabilities, the task of ensuring consistent levels of service quality for a given application to subscribers is close to impossible. Moreover, without that kind of quality assurance, the ultimate goal of ensuring the quality of experience (QoE) of the subscriber is uncontrollable from the network perspective. Hence there is a need for an adequate setup for proper QoS performance management in the network. QoS performance management alone will not be sufficient to satisfy the QoE goals, since the QoE can only be quantified from the mobile station point of view, typically through end-to-end testing campaigns or mobile probes deployed in significant places