name: FTP
full_form: File Transfer Protocol
context: user plane interruption is to fine-tune the parameters to accelerate the execution of the SCC procedure. In this case, a trade-off can be observed: If the network is parameterized to react to rapidly-changing channel conditions, it will be able to cope with the degradation of the CPICH Ec/No of the serving cell in urban canyon environments. However, in macro cell environments, there will be an increased risk of a ping-pong handover effect. Alternatively, the network can perform an enhanced serving cell change (eSCC), which has been standardized in Rel-8 and is described in 3GPP TS 25.308 [12]. The eSCC procedure features the concept of target cell pre-configuration, which adds robustness to the HS-DSCH SCC procedure by allowing the network to send the HS-DSCH SCC command over the source cell as an RRC message and/or over the target cell as an HS-SCCH order. Yet another technique to reduce the amount of lost packets is to bicast the voice packets from the RNC to the source and target
description: The File Transfer Protocol (FTP) is a standard protocol used for transferring files between systems over the internet. In the context of 3GPP TS 37.901, FTP is utilized as a reference system configuration for embedded testing in User Equipment (UE). The FTP client resides on the UE under test and requires an FTP application to be installed, meeting specific requirements such as file transfer in binary mode, computation of throughput, automation interface, and avoidance of hidden optimizations that might impact throughput.
explanation: FTP is classified as a Protocol because it defines a set of rules and procedures for transferring files between systems. The text explicitly states its use as a 'reference system configuration' and highlights its role in embedded testing within User Equipment (UE), further emphasizing its function as a protocol.
section_title: B.2.3.1	FTP Reference System Configuration
biotag_Context: 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,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,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,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Network Function,O,O,O,O,O,O,O,O,B-Connection,B-Network Function,O,O,O,O,O,O,O,B-Protocol,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,O,O,B-Network Function,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,B-Protocol,O,O,O,O,B-Device,O,O,O,O,O,B-Protocol,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