name: DRX
full_form: Discontinuous Reception
context: The ANR Report Forwarding uses RNSAP Direct Information Transfer procedure for sending of the ANR Report received over the Uu interface to the involved Base RNCs. Figure 5.1.1-1 ANR Report Forwarding Using the RNSAP: Direct Information Transfer procedure, the RNC receiving an ANR report over Uu may forward the ANR report to RNCs involved as Base RNCs in neighbour relations of the ANR report. The ANR report received in the RRC message over Uu is transparently forwarded in the RNSAP message. The receiving RNC extracts the neighbouring ANR cell information concerning the Base RNC from the Logged ANR Report Info list contained in the ANR Report over Uu, and includes the whole RRC message in RNSAP L3 Information IE. Abnormal conditions: When an RNC receives an ANR report outside the defined services of the ANR Report Distribution function, or if the ANR Report Distribution from the sender of the report has been suspended as described in 5.1.2, local error handling in the receiving RNC
description: Discontinuous Reception (DRX) is a procedure used in the High-Speed Downlink Shared Channel (HS-DSCH) operation to manage the discontinuous reception of data by the User Equipment (UE) in the CELL_FACH state. The DRX operation involves the UE receiving HS-DSCH data in bursts, with periods of inactivity in between, to conserve power and reduce interference. The procedure is initialized when an inactivity timer expires, and the UE receives HS-DSCH data for a configured length of time before entering a period of inactivity.
explanation: The context describes the DRX operation as a process involving timers, burst lengths, and inactivity periods, which are all characteristic of a procedure. The text explains how the DRX operation is initialized, how it works, and what conditions trigger its start, indicating that DRX is a specific sequence of operations rather than a protocol, network function, or technology.
section_title: 14.4.2	HS-DSCH DRX operation with second DRX cycle in CELL_FACH
biotag_Context: O,B-Procedure,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Interface,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,B-Interface,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Procedure,O,O,O,O,B-Protocol,O,O,B-Interface,O,O,O,O,O,B-Protocol,O,O,O,B-Network Function,O,O,O,B-Procedure,O,O,O,O,O,B-Network Function,O,O,O,B-Procedure,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,B-Protocol,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function
biotag_Description: B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,B-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,B-Procedure,O,O,O,B-Device,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,B-Device,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O