name: AAL5
full_form: ATM Adaptation Layer type 5
context: The following results reflect the relative cell throughput gain of E-DCH (EUL), with 2ms TTI, HARQ and a Node-B scheduler, over the system with DCH (Rel-99 assumptions), with 10 ms TTI, long scheduling period and centralized scheduler. The system configuration is shown in Table 9.4.1.1.1. The TTI is 2ms. Other assumptions are listed in Annex A3. The MCS for E-DCH is shown in Annex 2.2.1. The key differences between R99 and E-DCH parameters are summarized in Table 9.6.1.1.1. Table 9.6.1.1.1 The following figures present the system performance in terms of average cell throughput, fairness and RoT overshoot, defined as Probability {RoT > 7dB}. Figure 9.6.1.1.1 and Figure 9.6.1.1.2 compare the cell throughput with E-DCH (2ms TTI, PF scheduler), Rel-99 (nominal TFCS, PF scheduler) and Rel-99 (nominal TFCS, DL Sinr scheduler) with the assumptions shown above. It is seen that compared to Rel-99 with nominal TFCS with PF scheduler, the system performance with E-DCH improves by 70% at 4.5 dB
description: The ATM Adaptation Layer type 5 (AAL5) is a protocol used for transporting IP packets containing Implementation Specific O&M signalling data between Node B and RNC over an ATM transport network. It operates according to ITU-T Recommendation I.363.5 and utilizes virtual circuits to establish associations with IP addresses in peer nodes, enabling the carriage of IP packets via Classical IP over ATM protocols as specified in IETF RFC 2225 and Multiprotocol Encapsulation over AAL5 as outlined in IETF RFC 2684.
explanation: AAL5 is classified as a Protocol due to its role in adapting and transporting IP packets over an ATM network, adhering to specific recommendations and standards such as ITU-T Recommendation I.363.5 and IETF RFCs 2225 and 2684. The context highlights AAL5's functionality within the protocol stack for Implementation Specific O&M transport between Node B and RNC in the case of ATM transport option.
section_title: 4.3.1	ATM Transport Option
biotag_Context: O,O,O,O,O,O,O,O,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,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,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,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-Parameter,O,O,O,O,B-Parameter,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,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,B-Network Function,O,O,B-Specification,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,B-Specification,O,O,O,O,B-Organization,B-Specification,O,O,O,O,O,B-Protocol,O,O,O,B-Organization,B-Specification,O