name: SPS
full_form: Semi-persistent Scheduling
context: providing the DCI format in the slot, and if HARQ-ACK information for the SPS PDSCH release and the SPS PDSCH receptions would be multiplexed in a same PUCCH, the UE does not expect to receive the SPS PDSCHs, does not generate HARQ-ACK information for the SPS PDSCH receptions, and generates a HARQ-ACK information bit for the SPS PDSCH release. If a UE is configured to receive SPS PDSCH(s) in a slot for SPS configuration(s), the UE does not expect to receive a PDCCH providing a DCI format in the slot to indicate SPS PDSCH release of these SPS configuration(s), if HARQ-ACK information for the SPS PDSCH release and the SPS PDSCH reception(s) would map to different PUCCHs. If a UE detects a DCI format 1_1 indicating - SCell dormancy without scheduling a PDSCH reception, as described in clause 10.3, and - is provided pdsch-HARQ-ACK-Codebook = dynamic or pdsch-HARQ-ACK-Codebook-r16 the UE generates a HARQ-ACK information bit as described in clause 9.1.3 for a DCI format 1_1 indicating SCell
description: Semi-persistent Scheduling (SPS) is a procedure used in the 5G New Radio (NR) system to manage the transmission of downlink data. It involves the use of a specific type of scheduling, where the UE is configured to receive PDSCHs in a semi-persistent manner, without the need for dynamic scheduling.
explanation: The context describes SPS as a procedure within the 5G NR system that governs the transmission of downlink data using a specific scheduling method. This clearly indicates that SPS is a defined set of rules and actions, classifying it as a Procedure.
section_title: 9.1HARQ-ACK codebook determination
biotag_Context: O,O,B-Message,O,O,O,O,O,O,B-Protocol,O,O,O,B-Procedure,B-Connection,O,O,O,B-Procedure,B-Connection,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Protocol,O,O,O,B-Procedure,B-Connection,O,O,O,O,B-Protocol,O,O,O,O,B-Procedure,B-Connection,O,O,O,B-Device,O,O,O,O,B-Procedure,O,O,O,O,O,B-Procedure,O,O,B-Device,O,O,O,O,O,O,B-Connection,O,O,B-Message,O,O,O,O,O,O,B-Procedure,B-Connection,O,O,O,B-Procedure,O,O,B-Protocol,O,O,O,B-Procedure,B-Connection,O,O,O,B-Procedure,B-Connection,O,O,O,O,O,O,O,O,B-Device,O,O,B-Message,O,O,O,O,B-Network Function,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,B-Network Function
biotag_Description: B-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Technology,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O