name: SCPICH
full_form: Secondary Common Pilot Channel
context: Most frequent error cases: - NACK is detected as an ACK. The NW starts afresh with new data in the HARQ process. The data block is discarded in the NW and lost. Retransmission is left up to higher layers. - ACK is detected as a NACK: If the network retransmits the data block, the UE will re-send an ACK to the network. If in this case the transmitter at the network sends an abort indicator by incrementing the New Packet Indicator, the receiver at the UE will continue to process the data block as in the normal case. - [A threshold to detect lost status message is up to NW implementation. If detection is possible, better performance is achieved by defaulting to a NACK.] - If a CRC error on the shared control channel is detected, UE receives no data and sends no status report. If the absence of the status report is detected, NW can retransmit the block.
description: The Secondary Common Pilot Channel (SCPICH) is a type of channel used in the context of beamforming in cellular networks. It is assigned per beam and plays a crucial role in scenarios where the Node-B uses either 'grid-of-fixed-beams' or 'flexible-beam' mode. The SCPICH is utilized for UE transition between beams, requiring higher layer signaling to inform the UE about the need to use another SCPICH.
explanation: SCPICH is classified as a Channel because it facilitates communication and measurement reporting between Node-B and RNC, specifically in beamforming scenarios where it is assigned per beam. The context emphasizes its role in handling UE transitions and signaling requirements.
section_title: 7.2	RAN WG3
biotag_Context: O,O,O,O,O,B-Message,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Message,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,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,B-Network,O,O,O,O
biotag_Description: O,B-Connection,I-Connection,I-Connection,I-Connection,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,B-Connection,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O