3GPP TSG RAN WG1 Meeting #57 R1-09xxxx
San Francisco, USA, 4 – 8 May, 2009
General
1417 !"#$:,* C* E141177F
The document was presented by Sharad Sambhwani from Qualcomm and proposes a set of working assumptions as a
framework for guiding design pertaining to the operation of DC-HSUPA. The topics covered included carrier allocation,
physical channel and TTI configurations, synchronizations procedures, CPC, active set definitions.
Discussion (Question / Comment): Ericsson (also Samsung) have concern w.r.t the carrier specific TTI configuration
complexity. In addition, Ericsson commented whether UE control activation as described was needed and that UE
category issue shall be left to RAN2 discussion. Although mostly aligned with the content of Qualcomm’s contribution,
NSN raised the question whether both TTI was actually needed (in their view only 2ms TTI shall be considered).
Decision: Document is noted.
14117> !"#$!$! C* 9
The document was presented by (…) from Qualcomm and studies the interaction of DC-HSUPA and CPC, and draws the
following conclusions, when two adjacent uplinks are configured with the same TTI length:
Proposal 1: The 2 uplinks for a DC-HSUPA system have the same DTX status.
Proposal 2: UE_DTX_cycle_1 and UE_DTX_cycle_2 are common across two uplink adjacent carriers.
Proposal 3: UE_DTX_DRX_offset is common across two uplink adjacent carriers.
Proposal 4: Inactivity_threshold_for_UE_DTX_cycle_2 is common across two uplink adjacent carriers.
Proposal 5: Default SG in DTX Cycle 2 is common across two uplink adjacent carriers.
Proposal 6: UE_DTX_long_preamble is common across two uplink adjacent carriers.
Proposal 7: UE_DPCCH_burst_1 and UE_DPCCH_burst_1 are common across two uplink adjacent carriers.
Proposal 8: Uplink DPCCH slot format information is configurable per uplink carrier.
Proposal 9: MAC_DTX_cycle and MAC_Inactivity_threshold are common across two uplink adjacent carriers.
Proposal 10: UE_DRX_Grant_Monitoring and Inactivity_threshold_for_UE_Grant_Monitoring are common
across two uplink adjacent carriers.
Proposal 11: CPC_Enabling_Delay is common across two uplink adjacent carriers.
Discussion (Question / Comment): .
Decision: Document is noted.
141))8 '*1*** !"#$ # 9
The document was presented by Youngbum Kim from Samsung and draws the following conclusions:
Proposal 1: The same frame timing of E-DPCCH, E-DPDCH(s), and DPCCH between different uplink carriers
Proposal 2: The coding for E-DCH remains unchanged from SC-HSUPA.
Proposal 3: Trigger radio link failure/restore procedures only based on the primary uplink carrier.
Proposal 4: DC-HSUPA applies only in CELL_DCH.
Proposal 5: Transmit the E-RGCH/E-HICH/E-AGCH corresponding to the primary and secondary uplink carrier
on its corresponding downlink carrier respectively.
Proposal 6: Discuss and decide if it is necessary to support transmitting E-RGCH/E-HICH/E-AGCH
corresponding to both primary and secondary uplink carrier on a single downlink carrier.
Discussion (Question / Comment): .
Decision: Document is noted.
141517 !"#$* 9
The document was presented by Johan Hultell from Ericsson and mainly deals with the structure of the control channels
and the handling of the deactivation (reactivation) of secondary cells. Regarding these matters, for a UE configured in DC-
HSUPA mode, the proposals are:
Proposal 1: The E-HICH, E-AGCH, E-RGCH, and (F-)DPCH should be transmitted on each individual downlink
carrier.
Proposal 2: E-DPCCH and DPCCH should be transmitted on each individual uplink carrier.
Proposal 3: HS-DPCCH should be transmitted on the anchor uplink carrier only.
Proposal 4: The anchor downlink and uplink carriers should be paired.
Proposal 5: The network should control activation and deactivation of secondary carriers. The UE should be
notified by means of HS-SCCH orders transmitted on the anchor carrier.
12