name: SAI
full_form: Service Area Identity
context: after a PDCCH monitoring occasion where the UE detects a DCI format scheduling the PUSCH transmission. If a UE multiplexes HARQ-ACK information in a PUSCH transmission that is scheduled by a DCI format that includes a SAI field, the UE generates the HARQ-ACK codebook as described in clause 16.5.1.1 when a value of the SAI field in the DCI format is . The UE does not generate a HARQ-ACK codebook for multiplexing in the PUSCH transmission when unless the UE generates HARQ-ACK information only for - PSFCH reception occasions associated with PSSCH transmissions corresponding to a SL configured grant, or - PSFCH reception occasions associated with PSSCH transmissions that are scheduled by a DCI format 3_0 with a counter SAI field value of 1, in the set of occasions for candidate PSSCH transmissions with corresponding PSFCH reception occasions as described in clause 16.5.1. if the SAI field in the DCI format is set to '0'; otherwise, .
description: Service Area Identity (SAI) is a parameter used in the context of HARQ-ACK codebook generation for PUSCH transmissions. It is included as a field in DCI formats and influences whether the UE generates a HARQ-ACK codebook for multiplexing in the PUSCH transmission.
explanation: The provided context from 3GPP TS 38.213 highlights SAI's role in determining when a UE generates a HARQ-ACK codebook, making it a critical network attribute for operation and thus classifying it as a Parameter.
section_title: 16.5.1.2Type-1 HARQ-ACK codebook in physical uplink shared channel
biotag_Context: O,O,B-Connection,O,O,O,O,B-Device,O,O,B-Message,O,O,O,B-Connection,O,O,O,B-Device,O,B-Protocol,O,O,O,B-Connection,O,O,O,O,O,O,B-Message,O,O,O,O,B-Parameter,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Message,O,O,O,O,B-Device,O,O,O,O,B-Protocol,O,O,O,O,O,B-Connection,O,O,O,O,B-Device,O,B-Protocol,O,O,O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,B-Technology,O,O,O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Message,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Message,O,O,O,O,O,O,O
biotag_Description: B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,B-Connection,O