RAN1201: Fractional DPCH Fractional DPCH (F-DPCH) shares the DL dedicated code channel which carries L1 TPC bits

of HSDPA users. DL L1 signaling of up to 10 HSDPA users are time-multiplexed on the same SF256 DL code channel. By sharing the SF256 channel, the number of HS-PDSCH or R99 codes can be increased. Besides the increased spreading code efficiency, the F-DPCH reduces the downlink L1 control overhead. This increases the average HSDPA cell throughput. Fractional DPCH is supported by Rel7 and newer UEs. With F-DPCH configured, that is, replacing the downlink DPCCH, the signaling radio bearers (SRB) are always mapped to HSPA. F-DPCH includes transmit power control (TPC) bits but excludes TFCI and pilot bits: TFCI bits are no longer required because there is no DPDCH, and pilot bits are no longer required because TPC bits are used for SIR measurements. Faster signaling on HSPA reduces RRC signaling latency which allows roughly ~1s HSPA call setup times.

Figure 11: Fractional DPCH slot The FDPCHEnabled parameter must be set to enabled to switch both F-DPCH and SRB on HSPA capabilities, but only if:

The state of the CPC (continuous packet connectivity) license is On. HSDPA is enabled in the cell using RNP HSDPAEnabled parameter. HSUPA is enabled in the cell using RNP HSUPAEnabled parameter. Node B type is defined as WBTS using RNP NBAPCommMode parameter.

F-DPCH code tree optimization can be enabled if HSDPA dynamic code allocation is active with FDPCHCodeChangeEnabled parameter. The RNC databuild parameters associated with the F-DPCH transmit power are PtxFDPCHMax, PtxFDPCHMin, PtxOffsetFDPCHSHO. F-DPCH setup procedure is set by FDPCHSetup parameter. CPICH Ec/I0 must exceed the value defined by the CPICHECNOSRBHSPA parameter when establishing SRB on HSPA. To ensure a good reliability, the following F-DPCH & HSPA SRB allocation rules are applied:

F-DPCH should be allocated whenever possible, that is, not only if CPC or CS voice over HSPA require it. The RNC should allocate the F-DPCH if: o UE supports Release 7 F-DPCH. o Release 7 F-DPCH is enabled in all cells of the current DCH active set. o E-DCH active set is equal to DCH active set. o F-DPCH is allowed for the used service as defined by the FDPCHAndSRBOnHSPATC parameter. o Any services which require DCH do not exist (AMR on DCH). o HS-DSCH is allocated or is possible to allocate for the UE. o E-DCH is allocated or is possible to allocate for the UE. o SRB can be mapped to HS-DSCH. o SRB can be mapped to E-DCH. o Free F-DPCH slot format is available. SRB can be allocated to HSUPA with 10 ms TTI only if HSDPA is allocated in the downlink.

If HSDPA is not allocated in the downlink, SRB can be allocated to HSUPA with 2 ms TTI, that is, HSUPA/DCH configuration is possible. SRB can be allocated to HSDPA only if F-DPCH can be allocated. If the UE is in soft handover, the CPICH Ec/I0 of the HSDPA serving cell must be relatively strong compared to the active set cell with the highest CPICH Ec/I0. The CPICH Ec/I0 of the HSDPA serving cell must be at least equal to CPICH Ec/I0 of the active set cell with the highest CPICH Ec/I0 - HSDPASRBWindow. There must be at least one cell in the active set with a CPICH RSCP greater than the threshold defined by CPICHRSCPThreSRBHSDPA parameter. If HSPDA is already allocated then the serving cell must have a CPICH RSCP which is greater than the threshold defined by CPICHRSCPThreSRBHSDPA parameter.

The RNC continuously monitors the rules for F-DPCH allocation. Channel type switching from F-DPCH to DPCH is triggered if any of them are not fulfilled while a F-DPCH is allocated. Likewise, channel type switching from DPCH to F-DPCH is triggered if they are all fulfilled while a DPCH is allocated. The minimum interval between two consecutive FDPCH allocations for a specific UE is defined by the FDPCHAllocMinInterval parameter. A timer is started for this minimum interval after switching from F-DPCH to DPCH and the timer is stopped if a RAB establishment procedure is initiated, that is, F-DPCH allocation is not restricted during RAB establishment. Feature requirement: