 terminal. Each menu item belonging to the browser points to a byte code string that is executed when the user selects that menu item. QoS ASPECTS 9.9.1 End-to-End QoS Negotiation and Policy Requirements The main QoS negotiation and policy requirements can be summarized as follows (see other requirements in [7]: The UMTS R4 and R5 QoS negotiation mechanisms used for providing end-to-end QoS will be backward compatible with UMTS Release 99. It will not make any as- sumptions about the situation in external networks, which are not within the scope 5 GSM 03.48. Towards IP Based Networks of 3GPP specifications, or about application layer signalling protocols and applica- tions, which may be used on terminal equipment attached to mobile terminals. The UMTS network shall be able to negotiate end-to-end QoS also for mobile ter- minals and applications, which are not able to use QoS negotiation mechanisms other than the ones provided by UMTS. Thus, no changes to non-UMTS specific QoS negotiation mechanisms will occur. The UMTS policy mechanisms described in TS 23.060 will be used for control of the UMTS bearers, and the interaction between UMTS bearer services and IP bearer services will only occur at the translation function in the UE and GGSN. 9.9.2 QoS End-to-End Functional Architecture In the following we describe the base line QoS architecture outlined in [7]; hence, we should also note here that QoS for R4 and R5 remain also under consolidation in the 3GPP specifications. Nonetheless, we shall provide implementation examples. To provide QoS end-to-end, we manage the QoS within each domain. Thus we use an IP BS manager to control the external IP bearer service. Due to the different techniques applied within the IP network, this communicates to the UMTS BS manager through the translation function. To enable coordination between events in the application layer and resource manage- ment in the IP bearer layer, there exists an element called IP policy control as a logical policy decision element. It is also possible to 