name: CCPCH
full_form: Common Control Physical Channel
context: The Secondary CCPCH is used to carry FACH transport channels. For MBSFN IMB, there are two types of Secondary CCPCH: - Secondary CCPCH frame type 1; consists of 15 slots per radio frame - Secondary CCPCH frame type 2; consists of 3 slots (i.e. one sub-frame) per radio frame. Both of the Secondary CCPCH frame types may include TFCI in order to support multiple transport format combinations. It is the UTRAN that determines if a TFCI should be transmitted, hence making it mandatory for all UEs to support the use of TFCI. The structures of the Secondary CCPCH frame type 1 and Secondary CCPCH frame type 2 are shown in figure 18vA and figure 18viA, respectively. Physical channel bits of Secondary CCPCH frame type 1 slots are mapped to a QPSK signal point constellation whereas physical channel bits of Secondary CCPCH frame type 2 can be mapped either to QPSK or 16QAM signal point constellations. In the case of Secondary CCPCH frame type 2, the signal point constellation to be used for the
description: The Common Control Physical Channel (CCPCH) is a physical channel in UMTS networks that carries control information and signaling data between the network and user equipment. Specifically, the Secondary CCPCH is used to carry Forward Access Channel (FACH) transport channels and supports multiple transport format combinations through the use of Transport Format Combination Indicators (TFCI). It has two frame types: type 1 with 15 slots per radio frame and type 2 with 3 slots per radio frame, both of which may include TFCI. The physical channel bits are mapped to different signal point constellations depending on the frame type.
explanation: The context describes CCPCH's function within UMTS networks, focusing on its role in transmitting control information and signaling data. This aligns with the definition of a 'Channel' as a medium for communication within a telecommunications system.
section_title: 5.8.2.4	Secondary common control physical channel (S-CCPCH)
biotag_Context: O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Connection,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,B-Connection,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Connection,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,B-Technology,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Technology,O,B-Technology,O,O,O,O,O,O,O,O,B-Connection,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,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,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,O