on throughput is achieved. In order to achieve more than 90% of the application throughput, the MDCR need to be set higher than 1200kbps. So it is basically a choice of network operation to decide the MDCR rate based on its predefined QoS target. If the transport network performance is more important, then a smaller MDCR is adequate. If the end user application performance is the main target of dimensioning, the MDCR rate needs to be configured to a relative higher value. Appendix Dimensioning with VS. without Traffic Separation This section presents the results of dimensioning of the lub link, which transmits the HSDPA and Rel99 traffic either with or without Traffic Separation (TS) technique. In the following example, Rel99 traffic contains 50% web traffic (web traffic model is defined in Table 1) and 50% voice traffic with AMR codec. The voice model is given in Table 5.2. HSDPA consists of purely web traffic. In the following results, we fix the Rel99 traffic load and gradually increase the offered HSDPA traffic to the lub link, and investigate the bandwidth demand for transferring the combined HSDPA and Rel99 traffic satisfying the predefined QoS targets of both traffic types. In this example, the QoS target for Rel99 traffic is 1% packet discard ratio and for HSDPA 95% normalized application throughput. Figure A.24(a) shows the required lub link bandwidth over different offered UTRAN traffic loads in kbps. The offered UTRAN traffic is the total sum of traffic entering UTRAN network including HSDPA and Rel99. It shows that with the increased traffic demand, the required lub bandwidth to achieve the predefined QoS targets is increasing. It can be also obviously seen that, the required lub bandwidth for the traffic separation scenario is much lower than that for the case without traffic separation. Therefore it is concluded that applying the traffic separation technique brings a significant bandwidth saving for the lub dimensioning, which reduces the transport cost. The required capacity can be also expressed i