l NRT service classes use the same web traffic model: page size is 50 kbyte of a constant distribution. each Node B carries 8 elastic traffic flows per service class. The QoS objectives of dimensioning are defined in Table 8.4. For each service class the required application end-to-end QoS is specified in terms of a desired end-to-end delay factor. In the investigated examples, three scenarios are simulated each with a different setting of QoS requirements for the five service classes. Service Class DiffServ PHB Interactive - NRT RAB 64 kbps Interactive - NRT RAB 128 kbps Interactive - NRT RAB 256 kbps Interactive - NRT RAB 384 kbps Background - HSPA (2 Mbps) Table 8.2: Service classes and their mapped DiffServ PHBs WRED Parameters minth maxth exp.w. weight Table 8.3: WRED and WFQ Parameters Figure 8.14 presents the resultant dimensioning results for the last mile link. Every point in the curves represents one scenario in Table 8.4 with a different setting of QoS requirements for dimensioning. For each scenario, in order to dimension the last mile link and the backbone link individually, the target delay factor of each link needs to be determined. Based on the proposed approach (3) for QoS allocations presented in section 8.3.2, given the desired end- to-end delay factor per service class defined in the Table 8.4, the individual target delay factor of the last mile link and the backbone link for each service class can be derived from equation (8.6). 8.4 Dimensioning for Elastic Traffic in IP-Based UTRAN Target end-to-end delay factor as Service Class QoS requirement per service class Scenario 1 Scenario 2 Scenario 3 AF11- RAB 64 kbps AF21- RAB 128 kbps AF31 RAB 256 kbps AF41- RAB 384 kbps BE HSPA Table 8.4: QoS requirements per service class for IP RAN dimensioning In Figure 8.14, the graph (a) presents the dimensioned last mile link capacities for different QoS requirements derived from the analytical calculations and in addition the ones obtained from simulations. The analytical solutions are achieved according