r BE PHB, in addition there are 5 video and 11 voice user connections both are transmitted over EF PHB. The simulation scenario is composed of one Node B and one RNC (single lub scenario), and between them there are two IP DiffServ routers, which implements the DiffServ functions as explained in section 3.4.2.1. The QoS structure is shown in Figure 3.13. Table 7.2 gives the configuration of the WRED and WFQ parameters for different AF and BE PHBs. Service class Mapped to DiffServ PHB Conversational (voice) Streaming (video) Interactive -NRT RAB 64kbps Interactive - NRT 128kbps Interactive - NRT RAB 256kbps Interactive - NRT RAB 384kbps Background - HSPA (2 Mbps) Table 7.1: Traffic classes and their mapped PHBs Their traffic models are described below: (1) Interactive and Background Traffic Model - web application - Inactive period (reading/thinking time period): geometric distribution (mean = 5s) 7 Dimensioning for Single IP-Based lub - File/Page size: constant distribution of 25kbyte (2) Conversational Traffic Model - voice application - AMR Codec, with traffic model defined in Table 5.2 - Transport over UDP (3) Streaming Traffic Model - video application - 800bytes frame size - 10 frames /second - 64kbps coding rate - Transport over UDP WRED Parameters minth maxth exp.w. weight Table 7.2: WRED and WFQ Parameters The M/G/R/N-PS model is used in this case as the analytical model for dimensioning. Figure 7.2 compares the calculated application delay per PHB or RAB service using the M/G/R/N-PS model against the simulation results for the given scenario. It shows that for each PHB (AF or BE) and its serving NRT RAB service, given a certain lub link utilization, the calculated application delay matches well with the delay values from the simulations. It proves that the proposed analytical model gives an accurate estimation of the application performance for various service classes each with different RAB service and priorities. And moreover, it is observed that when the lub link is highly utilized, e.g. above 90% lin