name: HS-DPCCH
full_form: Dedicated Physical Control Channel (uplink) for HS-DSCH
context: A: N_max_dpdch = 0, where N_max_dpdch is the maximum number of configured uplink DPDCHs The UE sends the 1st HS-DPCCH and 2nd HS-DPCCH on the same channelization code. The channelization code is the same code as that is currently used for the legacy HS-DPCCH. The 1st HS-DPCCH is sent on the Q branch and the 2nd HS-DPCCH is sent on the I branch. Option B: N_max_dpdch = 1 The channelization code for the 1st HS-DPCCH is the same code as that is currently used for the legacy HS-DPCCH. The channelization code for the 2nd HS-DPCCH is a different code from that is currently used for the legacy HS-DPCCH. The 1st HS-DPCCH is sent on the Q branch and the 2nd HS-DPCCH is sent on the I or Q branch. When the UE is configured back to SC-HSDPA mode, it switches to the channelization code/branch that is currently used for the legacy HS-DPCCH. Option C: N_max_dpdch = 1 The UE sends the 1st HS-DPCCH and 2nd HS-DPCCH on the same channelization code. The channelization code is not the same code as that
description: The Dedicated Physical Control Channel (uplink) for High-Speed Downlink Packet Access Shared Channel (HS-DSCH), referred to as HS-DPCCH, is a specific channel used in the uplink direction. It is utilized by the User Equipment (UE) to send control information related to the downlink data transmission on the HS-DSCH. The context highlights different options for configuring and transmitting HS-DPCCHs, including the use of the same or different channelization codes and branches (I or Q), depending on the value of N_max_dpdch.
explanation: The abbreviation HS-DPCCH is classified as a Channel based on its role in facilitating control information exchange between the UE and the network for downlink data transmission. The context from 3GPP TS 25.825 specifically discusses the configuration, transmission, and switching of HS-DPCCHs under different scenarios, solidifying its classification as a channel within the telecommunication system.
section_title: 4.3.2.1.1	HS-DPCCH
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Connection,I-Connection,I-Connection,I-Connection,O,O,O,B-Connection,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O