name: RETAP
full_form: Remote Electrical Tilting Application Part
context: there is a very small difference between LHR and IHR mechanisms so that there is limited impact regarding the system capacity. Table 5.3.1.4-1: Call drop ratio for 30 and 60 km/h In table 5.3.1.4-2, if the network only perform x transmissions (x is 2, 3 or 4), the call drop ratio will be lower if there are more transmissions. If the network perform x+y transmissions, the call drop ratio will be further reduced, e.g. 4.32% for IHR (2) and 2.78 for IHR (2+2). For increased power for HS-DSCH transmission mode, the call drop ratio is lower than the IHR (2) mode, but higher than all other IHR modes. In the simulation, most of call drops happen in bad radio condition, and the network may not have available power for HS-DSCH transmission(s), so the effect is compromised. Table 5.3.1.4-2: Call drop ratio for different HARQ retransmission numbers (60 km/h) Based on the above results, there are the following observations: - The IHR mechanism could improve call drop ratio when UE radio condition
description: RETAP (Remote Electrical Tilting Application Part) refers to a set of messages used for communication between devices, specifically primary and secondary devices, within the context of Layer 2 transmission. These messages are categorized into two types: Class 1, which involves initiating messages that require a response from the receiving device to complete an action, and Class 2, where no response is expected after sending the initiating message. All RETAP messages adhere to a standard basic format as outlined in Table 5.1.1 of the specification.
explanation: The context explicitly states that RETAP consists of messages exchanged between devices for Layer 2 transmission purposes. The classification into Class 1 and Class 2 messages, along with the mention of a standardized format, reinforces its categorization as a 'Message' entity within telecommunications.
section_title: 5.1	Elementary procedure format
biotag_Context: O,O,O,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,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-Procedure,O,O,O,O,B-Procedure,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,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,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Device,O,O
biotag_Description: B-Message,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-Protocol,I-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,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O