name: FACH
full_form: Forward Access Channel
context: Figure 15 shows the protocol model for the FACH transport channel when the Controlling and Serving RNC are co-incident. Figure 15: FACH Co-incident Controlling and Serving RNC The Common MAC (MAC-c/sh/m) entity in the RNC transfers MAC-c PDU to the peer MAC-c entity in the UE using the services of the FACH Frame Protocol (FACH FP) entity. The FACH Frame Protocol entity adds header information to form a FACH FP PDU which is transported to the Node B over a transport bearer. An Interworking Function (IWF) in the Node B interworks the FACH frame received by FACH Frame Protocol (FACH FP) entity into the PHY entity. FACH scheduling is performed by MAC-c/sh/m in the CRNC. Figure 16 shows the protocol model for the FACH transport channel with separate Controlling and Serving RNC. In this case, Iur FACH Frame Protocol is used to interwork the Common MAC (MAC-c) at the Controlling RNC with the Dedicated MAC (MAC-d) at the Serving RNC. Figure 16: FACH: Separate Controlling and Serving RNC
description: The Forward Access Channel (FACH) is a transport channel in the UMTS network, responsible for carrying control information from the network to the user equipment. It is used for downlink transmission and plays a crucial role in the communication process between the Radio Network Controller (RNC) and the Node B. The FACH Frame Protocol entity adds header information to form a FACH FP PDU which is then transported over a transport bearer.
explanation: The context describes FACH as a channel responsible for transporting control information within the UMTS network, aligning with the definition of a Channel entity type.
section_title: 11.2.3	FACH Transport Channel
biotag_Context: O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,B-Connection,O,O,O,B-Network Function,I-Network Function,O,O,B-Protocol,O,O,O,O,B-Network Function,O,O,B-Connection,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Connection,B-Protocol,I-Protocol,O,O,O,O,B-Connection,B-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Connection,B-Protocol,B-Connection,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,O,O,B-Connection,O,O,O,B-Connection,B-Protocol,I-Protocol,O,O,O,O,O,B-Miscellaneous,O,B-Connection,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,B-Connection,B-Protocol,I-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function
biotag_Description: O,B-Connection,I-Connection,I-Connection,O,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,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,B-Connection,B-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Connection,B-Protocol,B-Connection,O,O,O,O,O,O,O,O