name: RFCI
full_form: RFC Indicator
context: The baseline antenna configuration for uplink single-user MIMO is two transmit antennas at the UE and two receive antennas at the Cell site. The use of both open loop transmit diversity techniques based on block codes as well as cyclic shift diversity, open-loop and closed-loop MIMO techniques, e.g. spatial division multiplexing (SDM) and precoding, should be considered. For the closed-loop mode, techniques for reducing signaling overhead should be evaluated. The possibility for single user higher-order uplink MIMO (more than two TX/RX antennas) should be considered. Transmit antenna selection at the UE, which assumes fewer RF chains than the number of transmit antennas (e.g. 1 RF chain and 2 transmit antennas), should be considered to potentially lower the UE complexity. The possibility for SDMA should also be considered. A specific example of SDMA corresponds to a (2x2) multi-user MIMO, where two UEs, each of which transmitting on a single antenna, share the same time and frequency
description: The RFC Indicator (RFCI) is an identifier used in the context of CS User Plane handling after SRNS Relocation. It refers to a specific index or value allocated for a bearer, which is stored and mapped by the HNB-GW to ensure consistent data rates between the source HNB and the target MSC.
explanation: The context highlights the role of RFCI in managing bearer-specific information and ensuring seamless communication during SRNS relocation. The mention of 'stored RFCI allocation' and 'RFCI Mapping function' indicates that RFCI serves as a unique identifier for data rate management, thus classifying it as an Identifier.
section_title: A.11.3	CS User Plane handling after the finalisation of SRNS Relocation
biotag_Context: O,O,O,O,O,O,O,B-Technology,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,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-Technology,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Technology,O,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
biotag_Description: O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,B-Mode,B-Protocol,I-Protocol,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O