name: ANR
full_form: Automatic Neighbor Relation
context: of the 2DL/2UL and 3DL/2UL captured in TR 37.863-01-01 [5] and TR 37.863-02-01 [6] respectively. Therefore, no additional MSD requirement is needed. 6.68 DC_42E_n79A 6.68.1 Operating bands for DC Table 6.68.1-1: DC band combination of LTE 4DL/1UL + one NR band 6.68.2 Channel bandwidths per operating band for DC Table 6.68.2-1: Supported bandwidths per DC band combination of LTE 4DL/1UL + one NR band 6.68.3 Co-existence studies Co-existence studies of this 5DL/2UL DC configuration are already covered by those of the 2DL/2UL and 3DL/2UL captured in TR 37.863-01-01 [5] and TR 37.863-02-01 [6] respectively. Therefore, no additional study is needed. 6.68.4 âTIB and âRIB values For DC_42E_n79A, the TIB,c and RIB values are given in the tables below. Table 6.68.4-1: ÎTIB,c Table 6.68.4-2: ÎRIB 6.68.5 MSD As with 6.68.3, MSD of this 5DL/2UL DC configuration are already covered by those of the 2DL/2UL and 3DL/2UL captured in TR 37.863-01-01 [5] and TR 37.863-02-01 [6] respectively. Therefore,
description: The Automatic Neighbor Relation (ANR) Report Forwarding is a procedure used in the Universal Mobile Telecommunications System (UMTS) to forward ANR reports received over the Uu interface from one Radio Network Controller (RNC) to other involved Base RNCs. This procedure utilizes the RNSAP Direct Information Transfer method, enabling the transparent forwarding of ANR reports between RNCs for efficient neighbor relation management.
explanation: The context describes a specific process involving the forwarding of ANR reports between network components (RNCs), which aligns with the definition of a 'Procedure' in telecommunications. The detailed steps and conditions under which this forwarding occurs, such as using RNSAP Direct Information Transfer and handling abnormal conditions, further solidify its classification as a procedure.
section_title: 5.1.1	ANR Report Forwarding
biotag_Context: O,O,O,O,O,O,O,B-Specification,O,O,O,B-Specification,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O,B-Technology,O,O,O,B-Network,O,O,B-Connection,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,B-Technology,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,B-Specification,O,O,O,O
biotag_Description: O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,B-Miscellaneous,I-Miscellaneous,I-Miscellaneous,I-Miscellaneous,O,O,O,B-Procedure,O,O,O,O,B-Interface,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O