name: RNL
full_form: Radio Network Layer
context: Virtual resource blocks of distributed type are mapped to physical resource blocks as described below. Table 6.2.3.2-1: RB gap values The parameter is given by Table 6.2.3.2-1. For , only one gap value is defined and . For , two gap values and are defined. Whether or is signaled as part of the downlink scheduling assignment as described in TS 36.212 [3]. Virtual resource blocks of distributed type are numbered from 0 to, where for and for . Consecutive VRB numbers compose a unit of VRB number interleaving, where for and for . Interleaving of VRB numbers of each interleaving unit is performed with 4 columns and rows, where , and is RBG size as described in TS 36.213 [4]. VRB numbers are written row by row in the rectangular matrix, and read out column by column. nulls are inserted in the last rows of the 2nd and 4th column, where . Nulls are ignored when reading out. The VRB numbers mapping to PRB numbers including interleaving is derived as follows: For even slot number ; , where , and
description: The Radio Network Layer (RNL) is a protocol layer responsible for managing radio network-related signaling and communication between different network elements, such as RNCs (Radio Network Controllers) and HNB-GWs (Home NodeB Gateways). It utilizes services provided by the SCCP (Signaling Connection Control Part) for connectivity between these elements. The RNL protocol is used for exchanging addressing information, performing mapping between RNA level and SCCP level, and managing connection-oriented signaling.
explanation: The context describes the usage of RNL signaling between an RNC and a HNB-GW, utilizing services provided by the SCCP. This indicates that RNL is a protocol responsible for radio network-related communication, which falls under the category of Protocol.
section_title: 7.3.3.1	General
biotag_Context: 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,B-Specification,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,B-Connection,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,B-Parameter,O,O,O,O,B-Specification,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,B-Connection,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,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,O,O,O,B-Network,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Protocol,O,O,O,O,O