name: AMD
full_form: AM Data
context: 7.1.2.3.2.1 Test Purpose (TP) (1) with { UE in RRC_CONNECTED state } ensure that { when { UE receives a 18 bit SN configured AMD PDU containing a SI field set to 00 } then { UE correctly decodes the received AMD PDU or AMD PDU segment } } (2) with { UE in RRC_CONNECTED state } ensure that { when { UE receives a 18 bit SN configured AMD PDU containing a SI field set to 01 } then { UE correctly decodes the received AMD PDU or AMD PDU segment } } (3) with { UE in RRC_CONNECTED state } ensure that { when { UE receives a 18 bit SN configured AMD PDU containing a SI field set to 11 and SO field } then { UE correctly decodes the received AMD PDU or AMD PDU segment } } (4) with { UE in RRC_CONNECTED state } ensure that { when { UE receives a 18 bit SN configured AMD PDU containing a SI field set to 10 and SO field } then { UE correctly decodes the received AMD PDU or AMD PDU segment } } (5) with { UE in RRC_CONNECTED state } ensure that { when { UE has UL RLC SDU to send and the UL Grant is
description: AM Data (AMD) is a protocol used for data transmission within the Radio Link Control (RLC) layer of 3GPP specifications. It handles the segmentation and reassembly of data packets, utilizing fields like Segmentation Info (SI) to manage these processes.
explanation: AMD is classified as a Protocol because it defines specific rules and procedures for data transmission and management within the RLC layer. Its function in segmenting and reassembling data packets, guided by fields like SI, aligns with the core characteristics of a protocol.
section_title: 7.1.2.3.2AM RLC / 18-bit SN / Segmentation and reassembly / Segmentation Info (SI) field
biotag_Context: O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,O,B-Protocol,B-Connection,O,O,B-Miscellaneous,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Protocol,B-Connection,O,B-Protocol,B-Connection,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,O,B-Protocol,B-Connection,O,O,B-Miscellaneous,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Protocol,B-Connection,O,B-Protocol,B-Connection,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,O,B-Protocol,B-Connection,O,O,B-Miscellaneous,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Device,O,O,O,O,B-Protocol,B-Connection,O,B-Protocol,B-Connection,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,O,B-Protocol,B-Connection,O,O,B-Miscellaneous,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Device,O,O,O,O,B-Protocol,B-Connection,O,B-Protocol,B-Connection,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Device,O,B-Connection,B-Protocol,B-Parameter,O,O,O,O,B-Connection,O,O
biotag_Description: B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O