hitecture. The architecture is capable of supporting any type of network service that the network provider is willing to support. User View The users subscribe to SLAs in sets of network services like 'inexpensive service', 'exclusive pack', etc. This service pack in terms of network level services is called the 'network view of the user profile' (NVUP), which basically contains the subscribed network-level services and the user identification. Entities of the QoS Architecture QoS Entities at the Network Level There are basically three different entities that interoperate in order to ensure QoS provision at the network level. They are the MT, AR and QoSB. Mobile Terminal (MT) The mobile terminal consists of: an enhanced IPv6 stack, able to perform marking according to the user-subscribed services; a networking control panel able to perform AAA (authentication, Authorisation and accounting) reg- istration/deregistration); a mobile terminal networking manager who will take the decision to execute the handover and attach procedures, based on information received from the user and information received from the networking devices (WCDMA, WLAN, Ethernet drivers); a radio convergence function that interfaces with the radio layer, in compliance with the IP-level QoS requirements. Access Router (AR) The access router consists of: an enhanced IPv6 stack with IPSec and DiffServ filtering, implementing basic transport, authentication and security functionalities, added with QoS-related functions (dropping, shaping, scheduling); a fast handover (FHO) module, implementing fast handover procedures in an MIPL (mobile IP for Linux) distribution, added with proper QoS-related signalling; an AAA attendant, responsible for all communication with the AAAC, acting on behalf of the MT to establish initial user registration and basic security functionalities; Fourth Generation Mobile Networks a QoS attendant, able to configure QoS policies in the stack and interoperate with context transfer mechanisms: - for exchanging FHO metering data