name: USCH
full_form: Uplink Shared CHannel
context: Figure 21 shows the protocol model for the USCH transport channel when the Controlling and Serving RNC are co-incident. Figure 21: USCH Co-incident Controlling and Serving RNC The Shared MAC (MAC-c/sh) entity in the RNC receives MAC-c/sh PDU from the peer MAC-c/sh entity in the UE using the services of the Interworking Function in the Node B, and the USCH Frame Protocol (USCH FP) entity. The USCH FP entity in the Node B adds header information to form a USCH FP PDU that is transported to the RNC over a transport bearer. An Interworking Function (IWF) in the Node B interworks the received USCH PHY entity into an USCH frame to be transmitted by the USCH FP entity over the Iub interface. USCH scheduling is performed by MAC-c/sh in UE and by C-RRC in the CRNC. Figure 22 shows the protocol model for the USCH transport channel with separate Controlling and Serving RNC. In this case, Iur USCH Frame Protocol is used to interwork the MAC-c/sh at the Controlling RNC with the MAC-d at the Serving
description: The Uplink Shared Channel (USCH) is a transport channel in the Universal Mobile Telecommunications System (UMTS) that carries uplink user data and control information between the User Equipment (UE) and the Radio Network Controller (RNC). It is responsible for transporting MAC-c/sh PDUs from the UE to the RNC, where they are processed by the Shared MAC entity. The USCH uses the services of the Interworking Function in the Node B to interwork with the USCH Frame Protocol entity, which adds header information to form a USCH FP PDU that is transported over a transport bearer.
explanation: The context describes the protocol model for the USCH transport channel, highlighting its role in transporting uplink user data and control information between the UE and RNC. The mention of MAC-c/sh PDUs, Interworking Function, and USCH Frame Protocol entity further supports the classification as a Channel.
section_title: 11.2.6	USCH Transport Channel [TDD]
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-Network Function,I-Network Function,O,O,O,O,O,O,B-Connection,B-Protocol,I-Protocol,O,O,O,O,B-Connection,B-Protocol,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,B-Connection,B-Protocol,B-Connection,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Connection,B-Miscellaneous,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,B-Protocol,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Device,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,O,O,B-Network Function,I-Network Function,O,O,B-Protocol,O,O,O
biotag_Description: O,B-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,B-Miscellaneous,I-Miscellaneous,I-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,O,O,O,O,B-Network Function,I-Network Function,O,O,B-Network Function,I-Network Function,O,O,O,O,B-Connection,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,B-Connection,B-Protocol,B-Connection,O,O,O,O,O,O,O