name: AMD
full_form: Acknowledged Mode Data
context: This clause presents link evaluation of uplink DCH enhancements described in clause 8 (Solution 2). In this clause, the simulation results for UL ET based on TFCI transmission are presented. The simulation results of Legacy R99 based on TFCI transmission are also presented for comparison. Link performance of Legacy R99 and that of ET are presented in Table 9.5-1 and Table 9.5-2 for "single link" case, and in Table 9.5-3 and Table 9.5-4 for "two links SHO (soft handover)" case, respectively. The Ec/No benefit for ET against Legacy R99 is summarized in Table 9.5-5. Table 9.5-1 - Link Performance for "single link" case of Legacy R99 based on TFCI transmission Table 9.5-2 - Link Performance for "single link" case of ET based on TFCI transmission Table 9.5-3 - Link Performance for "two links SHO" case of Legacy R99 based on TFCI transmission Table 9.5-4 - Link Performance for "two links SHO" case of ET based on TFCI transmission Table 9.5-5 - Link Performance of ET based on TFCI
description: Acknowledged Mode Data (AMD) refers to a type of data transmission mode in 3GPP specifications, specifically within the Radio Link Control (RLC) protocol. In this mode, data is transmitted with acknowledgement, ensuring reliable delivery of packets. The AMD PDUs (Protocol Data Units) are subject to specific rules for submission to lower layers, including restrictions on sequence numbers and transmission priorities.
explanation: The context describes how AMD operates within the RLC protocol, outlining its role in reliable data transmission through acknowledgements and specific rules governing its handling. This points to AMD being a type of message exchanged between network components for signaling and data transfer.
section_title: 11.3.2.2	Submission of AMD PDUs to lower layer
biotag_Context: O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Procedure,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Specification,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-Procedure,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Parameter,O,O,O,O,O,O,O,B-Procedure,O,O,B-Parameter
biotag_Description: B-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,O,B-Organization,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O