ic voice traffic, CBR traffic class is elected for providing high QoS for the real time services and also a symmetric PCR is configured for both directions. On the HSDPA and HSUPA path, it allows an asymmetric configuration of UBR/UBR+ VPs or VCs, e.g. asymmetric PCR or MDCR Appendix settings, to support the asymmetric traffic property of HSPA traffic, i.e. HSDPA user data is only transmitted on the downlink and there is a small amount of inband signaling traffic on the uplink, and HSUPA user data is only transmitted on the uplink with a small amount of inband signaling on the downlink. To transport HSDPA, HSUPA and Rel99 traffic simultaneously in the UTRAN transport network, there are mainly four possible scenarios to be considered: (1) 3 VPs: 1 CBR VP for Rel99, 1 UBR/UBR+ VP for HSDPA, 1 UBR/UBR+ VP for HSUPA; (2) 2 VPs: 1 CBR VP for Rel99, 1 UBR/UBR+ VP for HSPA with separated VCs to transmit HSDPA and HSUPA; (3) 2 VPs: 1 CBR VP for Re199, 1 UBR/UBR+ VP for HSPA without separated VCs to transmit HSDPA and HSUPA; (4) 1 VP: 1 Common CBR VP or VC to carry all traffic types. Scenario 1 applies three VPs each transferring one traffic type. Scenario 2 and 3 uses two VPs: 1 VP is assigned for Rel99 and the other one for the HSPA traffic. For these two cases, the HSDPA data traffic will be mixed with HSUPA inband signaling traffic and the HSUPA data traffic will be mixed with HSDPA inband signaling traffic. The difference of scenario 2 and 3 is whether to use separate VCs for transmitting HSDPA and HSUPA traffic. With separated VCs, each UBR/UBR+ VC can be configured with different PCR or MDCR for HSDPA and HSUPA individually. Moreover, in order to protect the HSPA inband signaling traffic which has high priority, Cell Loss Priority bit (CLP) that is defined in the ATM cell header can be used to select which cell to discard in case of congestion: CLP=1: for low priority traffic, cell may be discarded by ATM network in case of congestion; CLP=0: for high priority traffic, cell should not be discarded by ATM network. S