Shared channel transmission and HARQ-ACK feedback methods, terminal and network side device
By employing specific rules to determine shared channel transmission and HARQ-ACK feedback under invalid transmission opportunities, the transmission details and feedback issues of PXSCH and PDSCH are resolved, communication performance is improved and feedback overhead is reduced, and the integrity and uplink coverage of SBFD are enhanced.
Patent Information
- Application Number
- PCT/CN2026/095607
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing technologies lack clear solutions for the transmission details of the Physical Shared Channel (PXSCH) and the HARQ-ACK feedback operation of the PDSCH, especially regarding the handling of invalid transmission opportunities.
A shared channel transmission and HARQ-ACK feedback method is provided. By executing Rule 1 and Rule 2 respectively through the terminal and network-side equipment, HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed or only allowed to be multiplexed in the same HARQ-ACK codebook. This refines the details of shared channel transmission under invalid transmission opportunities and controls the HARQ-ACK feedback overhead.
It improves communication performance, reduces HARQ-ACK feedback overhead, ensures the integrity and feasibility of SBFD operation, shortens uplink latency, and enhances uplink coverage.
Smart Images

Figure CN2026095607_12112026_PF_FP_ABST
Abstract
Description
Shared channel transmission and HARQ-ACK feedback methods, terminals and network-side equipment
[0001] Cross-references to related applications
[0002] This application is based on and claims priority to Chinese Patent Application No. 202510598937.1, filed on May 9, 2025, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of communication technology, and more specifically, to a shared channel transmission and HARQ-ACK feedback method, a terminal, and network-side equipment. Background Technology
[0004] In related technologies, support for two configuration schemes (Configuration 1 and Configuration 2) has been discussed and established, along with the concept and determination method of invalid or valid symbol types when using Configuration 1, and the handling method for invalid transmission opportunities. However, there are currently no clear solutions for some transmission details of the Physical Shared Channel (PXSCH) and the HARQ-ACK feedback operation of PDSCH. Summary of the Invention
[0005] This application provides a shared channel transmission and HARQ-ACK feedback method, terminal, and network-side equipment, which can solve the problems of physical shared channel (PXSCH) transmission and PDSCH HARQ-ACK feedback in related technologies.
[0006] Firstly, a shared channel transmission and HARQ-ACK feedback method is provided, executed by a terminal, the method comprising:
[0007] If there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the terminal performs a first operation, the first operation including at least one of the following:
[0008] Determine the physical shared channel that needs to be transmitted;
[0009] When the target physical shared channel is a physical downlink shared channel (PDSCH), one of the following rules is used to determine the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit:
[0010] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0011] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0012] Secondly, a shared channel transmission and HARQ-ACK feedback method is provided, executed by a network-side device, the method comprising:
[0013] If there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the network-side device performs a second operation, which includes at least one of the following:
[0014] Determine the physical shared channel that needs to be transmitted;
[0015] The network-side device receives the HARQ-ACK codebook from the terminal within the first uplink time domain unit. The HARQ-ACK codebook is determined by the terminal using one of the following rules:
[0016] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0017] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0018] Thirdly, a shared channel transmission and HARQ-ACK feedback device is provided, including:
[0019] The first processing module is configured to perform a first operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the first operation including at least one of the following:
[0020] Determine the physical shared channel that needs to be transmitted;
[0021] When the target physical shared channel is a physical downlink shared channel (PDSCH), one of the following rules is used to determine the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit:
[0022] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0023] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0024] Fourthly, a shared channel transmission and HARQ-ACK feedback device is provided, comprising:
[0025] The second processing module is configured to perform a second operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the second operation including at least one of the following:
[0026] Determine the physical shared channel that needs to be transmitted;
[0027] The network-side device receives the HARQ-ACK codebook from the terminal within the first uplink time domain unit. The HARQ-ACK codebook is determined by the terminal using one of the following rules:
[0028] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0029] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0030] Fifthly, a shared channel transmission and HARQ-ACK feedback apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.
[0031] In a sixth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.
[0032] In a seventh aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to perform a first operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the first operation including at least one of the following:
[0033] Determine the physical shared channel that needs to be transmitted;
[0034] When the target physical shared channel is a physical downlink shared channel (PDSCH), one of the following rules is used to determine the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit:
[0035] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0036] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0037] Eighthly, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.
[0038] A ninth aspect provides a network-side device, including a processor and a communication interface, wherein the processor is configured to perform a second operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to a target physical shared channel, the second operation including at least one of the following:
[0039] Determine the physical shared channel that needs to be transmitted;
[0040] The receiving terminal sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook within the first uplink time domain unit. This HARQ-ACK codebook is determined by the terminal using one of the following rules:
[0041] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0042] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0043] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.
[0044] Eleventhly, a wireless communication system is provided, comprising: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the method as described in the first aspect, and the network-side device can be used to perform the steps of the method as described in the second aspect.
[0045] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.
[0046] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the shared channel transmission and HARQ-ACK feedback method as described in the first aspect, or to implement the steps of the shared channel transmission and HARQ-ACK feedback method as described in the second aspect.
[0047] In the embodiments of this application, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal performs at least one of determining the physical shared channel that needs to be transmitted and determining the HARQ-ACK codebook fed back in the first uplink time domain unit using rule one or rule two. By determining the shared channel that needs to be transmitted and determining the HARQ-ACK codebook according to the corresponding rules, the details of the shared channel transmission are refined, and the HARQ-ACK feedback overhead can be controlled or reduced, thereby improving communication performance. Attached Figure Description
[0048] Figure 1 is a block diagram of a wireless communication system applicable to an embodiment of this application;
[0049] Figure 2 is one of the flowcharts of the shared channel transmission and HARQ-ACK feedback method provided in the embodiments of this application;
[0050] Figure 3 is a second schematic flowchart of the shared channel transmission and HARQ-ACK feedback method provided in the embodiments of this application;
[0051] Figure 4 is one of the structural schematic diagrams of the shared channel transmission and HARQ-ACK feedback device provided in the embodiments of this application;
[0052] Figure 5 is a second schematic diagram of the shared channel transmission and HARQ-ACK feedback device provided in the embodiment of this application;
[0053] Figure 6 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0054] Figure 7 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application;
[0055] Figure 8 is a schematic diagram of the hardware structure of a network-side device that implements an embodiment of this application. Detailed Implementation
[0056] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0057] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0058] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.
[0059] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.
[0060] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.
[0061] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.
[0062] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).
[0063] The following explains the technical terms and related technologies involved in the embodiments of this application.
[0064] I. Flexible duplex (SBFD)
[0065] When deploying traditional cellular networks, based on available spectrum and service characteristics, either FDD (Frequency Division Duplex) or TDD (Time Division Duplex) duplexing methods can be used. With FDD, uplink and downlink transmissions operate on different frequencies, do not interfere with each other, and can occur simultaneously. With TDD, uplink and downlink transmissions operate on the same frequency, interleaving in a time-division manner. Each duplexing method has its advantages and disadvantages.
[0066] To more flexibly utilize limited spectrum resources, dynamically match service demands, improve resource utilization efficiency, and enhance data transmission performance such as uplink coverage and latency, a flexible duplexing method is proposed. One such method is a frequency domain non-overlapping sub-band full duplex (SBFD):
[0067] 1. Full-duplex on the network side
[0068] From the network's perspective, uplink and downlink transmissions can occur simultaneously in different frequency domain subbands. To avoid interference between uplink and downlink, a certain guardband can be reserved between frequency domain subbands corresponding to different transmission directions (e.g., uplink and downlink subbands).
[0069] 2. Terminal-side half-duplex or full-duplex
[0070] When the terminal supports half-duplex, only uplink or downlink transmission can occur at any given time; both cannot happen simultaneously. This cell duplex mode can also be called Duplex mode 1 or gNB SBFD mode. Understandably, in this case, uplink and downlink transmissions on the network side can only be performed for different terminals at any given time.
[0071] When the terminal supports full-duplex, similar to the network side, uplink and downlink transmissions can occur simultaneously in different frequency subbands. This cell duplex mode can also be called Duplex mode 2 or UE SBFD mode.
[0072] II. SBFD Configuration
[0073] Currently, cell-level configuration of time-frequency locations for SBFD subbands is supported on a single TDD carrier, and this cell-level configuration can be broadcast in SIB1.
[0074] Cell-level configuration based on the time-domain location of SBFD subbands can distinguish between SBFD symbols and non-SBFD symbols: Symbols configured with SBFD subbands can be called SBFD symbols, while Symbols without SBFD subbands can be called non-SBFD symbols.
[0075] III. SBFD Operation
[0076] 1. Two configurations
[0077] For SBFD-aware UEs, and for uplink (UL) transmissions and downlink (DL) receptions across SBFD and non-SBFD symbols in different time slots (the same configuration or indication information corresponds to at least one transmission / reception; in this at least one transmission / reception, each transmission / reception within a single time slot either occupies all SBFD symbols or occupies all non-SBFD symbols), one of the following configuration schemes (configuration scheme 1 or configuration scheme 2) needs to be provided for the SBFD-aware UE.
[0078] Configuration 1: Transmission / reception is only allowed in SBFD symbols or non-SBFD symbols and cannot span between the two symbol types; that is, each transmission / reception in at least one transmission / reception corresponding to the same configuration or indication information must occupy a symbol of the same type (or be located in a symbol of the same type), where the symbol type is either SBFD symbol or non-SBFD symbol.
[0079] Configuration 2: Transmission / reception can span SBFD symbols and non-SBFD symbols; that is, different transmissions / receptions in at least one transmission / reception corresponding to the same configuration or indication information can occupy different types of symbols (or be located in different types of symbols).
[0080] Support for Configuration 2 depends on terminal capabilities; Configuration 1 is the default capability.
[0081] Configuration 2 can be configured independently for each uplink bandwidth portion (UL BWP) or downlink bandwidth portion (DL BWP) of the SBFD-aware UE.
[0082] Configuration 1 or Configuration 2 for a specific DL BWP is only applicable to PDSCH reception within that DL BWP.
[0083] Configuration 1 or Configuration 2 for a specific UL BWP configuration applies to PUCCH and PUSCH transmissions within that UL BWP. For SRS, only Configuration 1 applies.
[0084] 2. Rules for determining the valid symbol types in Configuration 1
[0085] For Configuration 1, the valid symbol types are determined as follows:
[0086] 1) For semi-static configurations of transmission / reception that do not involve activating DCI, the valid symbol type is explicitly configured by RRC.
[0087] Not applicable to PDCCH.
[0088] The valid symbol types for Type 1 CG PUSCH are configured in the rrc-ConfiguredUplinkGrant parameter of ConfiguredGrantConfig.
[0089] The valid symbol type for PUCCH used in SR is configured in ScheduleRequestResourceConfig.
[0090] 2) For dynamically scheduled transmission / reception, the valid symbol type is determined based on the symbol type of the first transmission / reception opportunity indicated by the scheduling DCI.
[0091] The first transmit / receive opportunity indicated by the scheduling DCI is not allowed or is not expected to be mapped to either SBFD symbol or non-SBFD symbol.
[0092] 3) For type 2 CG PUSCH and SPS PDSCH
[0093] The valid symbol type of a type 2 CG PUSCH is determined by the symbol type of the first CG PUSCH associated with the activated DCI.
[0094] The valid symbol type of an SPS PDSCH is determined by the symbol type of the first SPS PDSCH associated with the activated DCI.
[0095] 4) For PUSCH retransmission Type B
[0096] The valid symbol type for Type 2 CG PUSCH is determined by the symbol type of the first actual repeated transmission associated with the activated DCI.
[0097] The valid symbol type of a dynamically scheduled PUSCH is determined by the symbol type of the first actual repeated transmission opportunity indicated by the scheduling DCI.
[0098] 5) For CSI reports associated with periodic / semi-persistent CSI-RS, the valid symbol type for CSI derivation is configured in CSI-ReportConfig.
[0099] 6) The valid symbol type of the PUSCH carrying SP-CSI is determined by the symbol type of the first PUSCH transmission opportunity associated with the activation of DCI.
[0100] 7) The valid symbol type of the PUCCH carrying SP-CSI is configured in the semiPersistentOnPUCCH parameter of CSI-ReportConfig.
[0101] 8) The valid symbol type of the PUCCH carrying P-CSI is configured in the periodic parameter of CSI-ReportConfig.
[0102] 3. UE behavior for invalid symbol types
[0103] For Configuration 1, the UE's handling behavior for invalid symbol types is as follows:
[0104] For the following transmission types, the UE will postpone transmission in the invalid symbol type (or postpone transmission in the symbol corresponding to the invalid symbol type): PUSCH repetition type A using available slot count; Aperiodic SRS using available slot count (A-SRS); TBoMS (Multi-Slot TB Processing); PUCCH repetition.
[0105] For the following transmission or reception types, the UE will drop transmissions / receptions in invalid symbol types (or, transmissions / receptions located in symbols corresponding to invalid symbol types): CG PUSCHs that do not use TBoMS and do not use PUSCH repetition type A based on available slot counts; SPS PDSCHs; Periodic / Semi-Persistent (P / SP) SRSs; Periodic / Semi-Persistent (P / SP) CSI-RSs; Periodic / Semi-Persistent (P / SP) PUCCHs; PUSCHs carrying SP-CSI (Semi-Persistent CSI); PUSCH repetition type A that does not use available slot counts; multiple PUSCHs / PDSCHs scheduled by a single DCI; PDSCH repetition.
[0106] 4. UE behavior regarding transmission opportunities mapped to both SBFD and non-SBFD symbol types within a single time slot.
[0107] For a single physical channel / signal transmission opportunity mapped to SBFD symbols and non-SBFD symbols within a single time slot:
[0108] For the following transmission types, if a transmission opportunity is mapped to both SBFD and non-SBFD symbol types within a single time slot, the UE will postpone the transmission corresponding to this transmission opportunity: PUSCH repetition type A using available time slot count; A-SRS using available time slot count; TBoMS (Multi-Slot TB Processing); PUCCH repetition.
[0109] For the following transmit / receive types, if a transmit / receive opportunity is mapped to both SBFD and non-SBFD symbol types within a single time slot, the UE will drop the transmit / receive corresponding to this transmit / receive opportunity: CG PUSCH without TBoMS and without PUSCH repetition type A based on available time slot count; SPS PDSCH; Periodic / Semi-Persistent (P / SP) SRS; Periodic / Semi-Persistent (P / SP) CSI-RS; Periodic / Semi-Persistent (P / SP) PUCCH; PUSCH carrying SP-CSI (Semi-Persistent CSI); PUSCH repetition type A without using available time slot count; multiple PUSCH / PDSCH scheduled by a single DCI; PDSCH repetition.
[0110] IV. HARQ-ACK Feedback in NR
[0111] In NR, most shared channel transmissions support HARQ retransmission. For Unicast PDSCH reception (including dynamically scheduled PDSCH reception and SPS PDSCH reception), when the UE receives a PDSCH (with or without repetition transmission; when without repetition transmission, only a single PDSCH reception is included; when with repetition transmission, multiple PDSCH receptions can be included based on the configured repetition factor, where each PDSCH reception corresponds to a single PDSCH repetition), it can send a HARQ-ACK corresponding to this PDSCH to the network side to indicate whether the UE has successfully decoded the TB carried by this PDSCH (when the HARQ-ACK value is ACK, it indicates that the UE has successfully decoded the TB carried by this PDSCH; when the HARQ-ACK value is NACK, it indicates that the UE has not yet successfully decoded the TB carried by this PDSCH). In addition, when a UE successfully detects a PDCCH that is not scheduled for PDSCH reception (for example, the DCI carried by this PDCCH is used to indicate TCI state update, SPS release, SCell dormancy, etc.), it can also send back the corresponding HARQ-ACK to the network side, setting the value to ACK to indicate that the UE has successfully detected this PDCCH.
[0112] Generally, the UE uses HARQ-ACK bits to send a HARQ-ACK response to the network, where a value of 1 indicates ACK and a value of 0 indicates NACK. Determining at least one HARQ-ACK bit into a HARQ-ACK bit sequence according to predefined rules is called constructing a HARQ-ACK codebook; correspondingly, a HARQ-ACK bit sequence can also be called a HARQ-ACK codebook, and different predefined rules correspond to different HARQ-ACK codebook types. The following types of HARQ-ACK codebooks are introduced in NR:
[0113] Type-1 HARQ-ACK codebook: It is based on high-level parameters configured in a semi-static manner, including the TDRA table and K1 set, and is not affected by dynamic DCI indications. It can also be called a semi-static HARQ-ACK codebook.
[0114] Type-2 HARQ-ACK codebook: It is constructed based on the actual PDCCH detection situation of the UE. It also generally involves serially numbering the PDCCH sent by the network side / detected by the UE (for example, performing DAI counting), and can also be called dynamic HARQ-ACK codebook.
[0115] Enhanced Type-2 HARQ-ACK codebook: Based on the Type-2 HARQ-ACK codebook, a PDSCH group dimension is further introduced (currently supporting up to two PDSCH groups); each PDSCH group follows the corresponding operations of the Type-2 HARQ-ACK codebook, and further supports NFI (New Feedback Indicator) indication and cross-PDSCH group feedback triggering, which can realize unlimited HARQ-ACK retransmissions for each PDSCH group.
[0116] Type-3 HARQ-ACK codebook: The HARQ-ACK codebook is determined from the perspective of HARQ processes, and the codebook contains the HARQ-ACK bits corresponding to all downlink HARQ processes configured by each of the Serving cells corresponding to the current PUCCH group.
[0117] Enhanced Type-3 HARQ-ACK codebook: Based on the Type-3 HARQ-ACK codebook, the configuration of the Serving cell corresponding to the codebook and the range of downlink HARQ processes involved on each configured Serving cell can be controlled as needed. Currently, each PUCCH group supports configuring up to 8 different configured Serving cells and downlink HARQ process ranges, with each range corresponding to a single Enhanced Type-3 HARQ-ACK codebook. The network side can control the UE to feed back a configured Enhanced Type-3 HARQ-ACK codebook at a certain time as needed, thereby satisfying the HARQ-ACK feedback requirements while controlling the HARQ-ACK feedback overhead.
[0118] In related technologies, support for two configurations (Configuration 1 and Configuration 2) has been discussed and established, along with the concept and determination method of invalid or valid symbol types when Configuration 1 is applied, and the handling method for invalid transmission opportunities. However, there are currently no clear solutions for some transmission details of the Physical Shared Channel (PXSCH) and the HARQ-ACK feedback operation of PDSCH.
[0119] This application provides specific and feasible solutions for some transmission details of PXSCH and HARQ-ACK feedback operation of PDSCH. These solutions can control or reduce HARQ-ACK feedback overhead and ensure the integrity and feasibility of SBFD operation, thereby achieving performance improvements such as reduced uplink latency and enhanced uplink coverage in SBFD.
[0120] The shared channel transmission and HARQ-ACK feedback method, terminal, and network-side equipment provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.
[0121] In this application, the Physical Shared Channel (PXSCH) can be either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).
[0122] In this application, an invalid transmission opportunity is an invalid transmission opportunity (Invalid PXSCH occasion) corresponding to a physical shared channel, which can be either an Invalid PDSCH occasion or an Invalid PUSCH occasion.
[0123] In this application, a valid transmission opportunity is a valid transmission opportunity (Valid PXSCH occasion) corresponding to a physical shared channel, which can be either a Valid PDSCH occasion or a Valid PUSCH occasion.
[0124] In this application, a PXSCH occasion is determined to be an Invalid PXSCH occasion when a predefined condition is met, as described below.
[0125] In this application, a time-domain unit can also be called a time period, which can correspond to a period of time in the time domain. For example, communication between the terminal and the network-side device can be at the time-domain unit granularity. For example, a time-domain unit can be a time slot, symbol, subframe, radio frame, micro-time slot, mini-time slot, etc., without limitation.
[0126] In this application, the time-domain cell type for a given Valid PXSCH occasion is the time-domain cell type corresponding to any or all of the time-domain cells it occupies. Optionally, when the time-domain cell is symbolic, the time-domain cell type is a symbolic type. For ease of description, the term "symbol type" will be used to refer to the time-domain cell type in some places below, which does not constitute a limitation on the time-domain cell type.
[0127] In this application, transmission can be understood as sending and / or receiving.
[0128] In this application, the first time-domain unit can be a time slot.
[0129] In this application, the first uplink time domain unit can be a UL slot, such as a PUCCH slot.
[0130] In this application, the first downlink time-domain unit can be a DL slot.
[0131] Figure 2 is a flowchart illustrating one of the shared channel transmission and HARQ-ACK feedback methods provided in this application embodiment. As shown in Figure 2, the method includes:
[0132] Step 200: If there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the terminal performs a first operation, the first operation including at least one of the following:
[0133] Step 1: Determine the physical shared channel to be used for transmission;
[0134] Operation 2: When the target physical shared channel is the physical downlink shared channel (PDSCH), the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit is determined using one of the following rules:
[0135] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0136] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0137] For rule two, a certain HARQ-ACK codebook contains only HARQ-ACK information corresponding to PDSCH of one symbol type. This symbol type can be understood as the symbol type of this HARQ-ACK codebook.
[0138] In the embodiments of this application, there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, and the determined physical shared channels that need to be transmitted can be understood as a subset of the target physical shared channels.
[0139] The terminal uses rule one or rule two to determine the HARQ-ACK codebook and feeds back the HARQ-ACK codebook in the first uplink time domain unit.
[0140] The shared channel transmission and HARQ-ACK feedback method provided in this application, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, performs at least one of the following: determining the physical shared channel that needs to be transmitted and determining the HARQ-ACK codebook to be fed back in the first uplink time domain unit using rule one or rule two. By determining the shared channel transmission that needs to be transmitted and determining the HARQ-ACK codebook according to the corresponding rules, the details of the shared channel transmission are refined, and the HARQ-ACK feedback overhead can be controlled or reduced, thereby improving communication performance.
[0141] The following describes the method for determining invalid PXSCH occasions.
[0142] In some embodiments, the target transmission opportunity is a single transmission opportunity among the transmission opportunities corresponding to the target physical shared channel.
[0143] Optionally, a target transmission opportunity is determined to be an invalid transmission opportunity if it satisfies at least one of the following time-domain relationships:
[0144] Case 1: The time domain overlaps with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit. This can also be understood as the target transmission opportunity overlapping with both types of time domain units, namely SBFD time domain unit and non-SBFD time domain unit, or having time domain overlap with both.
[0145] Case 2: Time domain units that completely overlap with invalid time domain unit types can also be understood as the target transmission opportunity only overlapping with time domain units that correspond to invalid time domain unit types, or the time domain units occupied or overlapped by the target transmission opportunity in the time domain all correspond to invalid time domain unit types;
[0146] Optionally, if the target transmission opportunity is a single Physical Uplink Shared Channel (PUSCH) transmission opportunity, the detection of whether the target transmission opportunity completely overlaps with the time domain of the time domain of the invalid time domain type is performed only if the target transmission opportunity has an invalid time domain type.
[0147] Specifically, if the target transmission opportunity satisfies at least one of the following conditions, it is determined that the target transmission opportunity has an invalid time domain unit type:
[0148] The uplink activation bandwidth configuration or application configuration scheme 1 corresponding to the target transmission opportunity;
[0149] The target transmission opportunity is a single configured authorized CG PUSCH transmission opportunity;
[0150] The target transport opportunity corresponds to a first PUSCH, and the first PUSCH satisfies any of the following: the first PUSCH is a dynamically licensed DG PUSCH, and is one of multiple DG PUSCHs scheduled by a single DCI; the first PUSCH is a DG PUSCH or a CG PUSCH, and applies at least one of the following transport mechanisms: PUSCH repetition type A, PUSCH repetition type B, and transport block over multiple slots (TBoMS).
[0151] Optionally, if the target transmission opportunity is a single physical downlink shared channel (PDSCH) transmission opportunity, the detection of whether the target transmission opportunity completely overlaps with the time domain of the time domain of the invalid time domain type is performed only if the target transmission opportunity has an invalid time domain type.
[0152] Specifically, if the target transmission opportunity satisfies at least one of the following conditions, it is determined that the target transmission opportunity has an invalid time domain unit type:
[0153] The downlink active bandwidth portion of the target transmission opportunity corresponds to BWP configuration or application configuration scheme 1;
[0154] The target transmission opportunity is a single semi-persistent scheduling (SPS) PDSCH transmission opportunity.
[0155] The target transmission opportunity corresponds to the first PDSCH, and the first PDSCH satisfies any of the following: the first PDSCH is a DG PDSCH and is one of multiple DG PDSCHs scheduled by a single DCI; the first PDSCH is a DG PDSCH or an SPS PDSCH and applies repeated transmission of the PDSCH.
[0156] Case 3: When the target transmission opportunity corresponds to a physical uplink shared channel (PUSCH), the time domain overlaps with the semi-static downlink time domain unit or the synchronization signal block time domain unit.
[0157] The target transmission opportunity corresponds to a Physical Uplink Shared Channel (PUSCH), which can be understood as the target transmission opportunity being a PUSCH occasion.
[0158] Optionally, the semi-static downlink time-domain unit is a semi-static DL symbol. Optionally, the synchronization signal block time-domain unit is an SSB symbol.
[0159] The overlap of time domains with semi-static DL symbols can also be understood as a time domain collision or overlap with symbols that are indicated as downlinks by the higher-level parameters tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
[0160] The overlap of the time domain with the SSB symbol can also be understood as a time domain collision or overlap with the SSB symbol indicated by the higher-level parameter ssb-PositionsInBurst.
[0161] Case 4: When the target transmission opportunity corresponds to a PDSCH, the time domain overlaps with the semi-static uplink time domain unit.
[0162] The target transmission opportunity corresponds to a PDSCH, which can be understood as the target transmission opportunity being a PDSCH occasion.
[0163] Optionally, the semi-static uplink time domain unit is a semi-static UL symbol.
[0164] The overlap of the temporal domain with a semi-static UL symbol can also be understood as a temporal collision or overlap with a symbol that is indicated as an uplink by the higher-level parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.
[0165] In this application embodiment, a method for determining invalid transmission opportunities is provided. When there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal performs at least one of the following: determining the physical shared channel that needs to be transmitted and determining the HARQ-ACK codebook fed back in the first uplink time domain unit using rule one or rule two. By determining the shared channel that needs to be transmitted and determining the HARQ-ACK codebook according to the corresponding rules, the details of the shared channel transmission are refined, and the HARQ-ACK feedback overhead can be controlled or reduced, thereby improving communication performance.
[0166] In some embodiments, determining the physical shared channel to be transmitted satisfies at least one of the following:
[0167] 1) When a single downlink control information (DCI) schedules at least one physical shared channel transmission opportunity, the terminal does not expect each physical shared channel transmission opportunity scheduled by the DCI to be determined as an invalid transmission opportunity;
[0168] Optionally, the single DCI schedules at least one physical shared channel transmission opportunity, including at least one of the following:
[0169] The single DCI schedules a single physical shared channel on a single scheduled serving cell that is not subject to duplicate transmissions, and the single physical shared channel corresponds to a single transmission opportunity.
[0170] The single DCI schedules a single physical shared channel for repeated transmission on a single scheduled serving cell, and the single physical shared channel corresponds to multiple transmission opportunities.
[0171] The single DCI schedules one or more physical shared channels that are not used for duplicate transmissions on a single scheduled serving cell, and each scheduled physical shared channel corresponds to a single transmission opportunity.
[0172] The single DCI schedules one or more physical shared channels on the scheduled serving cells, and schedules a single physical shared channel with or without repeated transmission on each scheduled serving cell, the single physical shared channel corresponding to at least one transmission opportunity.
[0173] For any scheduled DCI, the UE does not expect that each PXSCH occasion scheduled by this DCI will be judged as Invalid.
[0174] 2) When the terminal is configured with multiple semi-persistent scheduling (SPS) PDSCHs in a single first downlink time domain unit on a serving cell, the terminal determines the remaining SPS PDSCHs, without considering SPS PDSCHs whose corresponding transmission opportunities are determined to be invalid transmission opportunities.
[0175] When a UE configures multiple SPS PDSCHs within a single DL slot on a Serving cell, the UE does not consider SPS PDSCHs that are determined to be invalid PDSCH occasions when determining the Survivor SPS PDSCH.
[0176] For example, the UE can perform the following operations:
[0177] If, in a time slot, there are multiple Physical Downlink Shared Channels (PDSCHs) on a serving cell that do not have corresponding Physical Downlink Control Channel (PDCCH) transmissions, then after processing the overlap of symbols indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in this time slot, and excluding PDSCHs that overlap with both SBFD and non-SBFD symbols, or completely overlap with symbols corresponding to illegal symbol types, the UE will receive one or more PDSCHs without corresponding PDCCH transmissions in this time slot according to the following provisions.
[0178] Step 0: Set j = 0, where j is the number of Physical Downlink Shared Channels (PDSCHs) to be decoded. Q is the set of active PDSCHs that do not have corresponding Physical Downlink Control Channel (PDCCH) transmissions within this time slot.
[0179] Step 1: The UE receives a single PDSCH with the smallest sps-ConfigIndex configuration value within the Q set and increments the j value by 1. This received PDSCH is then stored as the PDSCH.
[0180] Step 2: Remove the remaining PDSCH from Step 1 and any other PDSCH that overlaps (even partially overlaps) with the remaining PDSCH from the Q set.
[0181] Step 3: Repeat steps 1 and 2 until the Q set is empty or j equals the number of unicast / multicast PDSCHs that the UE supports receiving in a single time slot.
[0182] In this application embodiment, a method for determining the physical shared channel to be transmitted is provided, which refines the details of the shared channel transmission and can ensure that the terminal and network-side devices have a consistent understanding of the physical shared channel to be transmitted, thereby ensuring the effectiveness and reliability of the physical shared channel transmission.
[0183] In some embodiments, determining the HARQ-ACK codebook includes at least one of the following:
[0184] Determine the time-domain unit type corresponding to the HARQ-ACK codebook;
[0185] When the HARQ-ACK codebook contains only SPS HARQ-ACK, the terminal, in determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, excludes the first SPS PDSCH, or sets the SPS HARQ-ACK bit corresponding to the first SPS PDSCH to NACK. The first SPS PDSCH is the SPS PDSCH whose corresponding transmission opportunity is determined to be an invalid transmission opportunity.
[0186] If the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information;
[0187] If the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, then according to the target information, the corresponding second codebook construction operation is performed;
[0188] The target information includes at least one of the following:
[0189] PDSCH scheduling type;
[0190] The HARQ-ACK codebook needs to provide feedback on whether the transmission opportunity corresponding to the PDSCH with the corresponding HARQ-ACK information has been determined as an invalid transmission opportunity.
[0191] Specifically, the UE performs the corresponding codebook construction operation for the following HARQ-ACK codebooks:
[0192] 1) SPS HARQ-ACK only
[0193] When constructing the SPS HARQ-ACK bit sequence to be fed back within a specified PUCCH slot, if the UE determines that it needs to feed back the corresponding SPS PDSCH with HARQ-ACK within the specified PUCCH slot, it may exclude the SPS PDSCH corresponding to the Invalid PDSCH occasion, or set the SPS HARQ-ACK bit corresponding to the SPS PDSCH corresponding to the Invalid PDSCH occasion to NACK.
[0194] 2) Type-1 HARQ-ACK codebook
[0195] When constructing the Type-1 HARQ-ACK codebook fed back within the specified PUCCH slot, the following situations can be distinguished to perform the corresponding operations:
[0196] For Single PDSCH scheduling: During the construction of the codebook, when determining the set of SLIVs used to determine the Occasion set, SLIVs corresponding to Invalid PDSCH occasions are excluded.
[0197] For Multi-PDSCH scheduling: it can distinguish whether Time domain bundling is enabled and execute the corresponding codebook construction operation accordingly.
[0198] 3) Type-2 HARQ-ACK codebook
[0199] For Single PDSCH scheduling, based on Operation 1 above, the mechanism in related technologies can be used. Optionally, for the HARQ-ACK bit in the Type-2 HARQ-ACK codebook determined by the terminal that corresponds to the Invalid PDSCH occasion or Invalid PDSCH, the terminal directly sets it to NACK; otherwise, the terminal sets the value of the corresponding HARQ-ACK bit in the Type-2 HARQ-ACK codebook based on the decoding result of the Valid PDSCH occasion or Valid PDSCH.
[0200] For Multi-PDSCH scheduling, it is possible to distinguish whether Time domain bundling is enabled and execute the corresponding codebook construction operation accordingly.
[0201] In the embodiments of this application, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal uses rule one or rule two to determine the HARQ-ACK codebook to be fed back in the first uplink time domain unit. For different HARQ-ACK codebook types, the UE performs corresponding codebook construction operations, which can control or reduce HARQ-ACK feedback overhead, thereby improving the flexibility of HARQ-ACK feedback and reducing HARQ-ACK feedback resource overhead, so as to improve the efficiency of system resource utilization.
[0202] The following section introduces the method for determining the time-domain unit type corresponding to the HARQ-ACK codebook. For ease of description, the following explanation uses Symbol type as an example. When the time-domain unit is of other types, corresponding substitutions can be made.
[0203] It should be noted that, optionally, determining the time-domain unit type corresponding to the HARQ-ACK codebook can be performed only when determining the HARQ-ACK codebook using rule two.
[0204] In some embodiments, the time-domain cell type of the HARQ-ACK codebook satisfies one of the following:
[0205] 1) The time-domain cell type of the HARQ-ACK codebook is the time-domain cell type of the target PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook;
[0206] Optionally, the target PDSCH includes at least one of the following:
[0207] a) The target PDSCH is all PDSCHs that feed back corresponding HARQ-ACK information in the HARQ-ACK codebook;
[0208] Generally, network-side configuration and / or scheduling can ensure that the Symbol type of the PDSCH (either DG PDSCH or SPS PDSCH) that feeds back the corresponding HARQ-ACK information within the same PUCCH slot is consistent. Accordingly, the UE expects the Symbol type of the PDSCH that feeds back the corresponding HARQ-ACK information within the same PUCCH slot to be consistent.
[0209] b) The target PDSCH is the PDSCH with the earliest or latest first target time among the PDSCHs that feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook. The first target time includes one of the following: the start time or end time of the PDSCH, or the start time or end time of the first time domain unit in which the PDSCH is located.
[0210] Optionally, the target PDSCH can be the earliest / latest DG PDSCH or SPS PDSCH at the first target time.
[0211] c) The target PDSCH is the PDSCH with the earliest or latest second target time among the PDSCHs that feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook. The second target time includes one of the following: the start time or end time of the second DCI, the start time or end time of the control resource set CORESET that transmits the second DCI, and the start time or end time of the first time domain unit where the CORESET that transmits the second DCI is located.
[0212] The second DCI here can be understood as the scheduling DCI, which is used to schedule the PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook.
[0213] 2) The time-domain unit type of the HARQ-ACK codebook is indicated by the first DCI that triggers the terminal to feed back the HARQ-ACK codebook;
[0214] Optionally, the first DCI that triggers the terminal to feed back the HARQ-ACK codebook includes at least one of the following:
[0215] The DCI schedules the PDSCH and instructs the terminal to feed back the HARQ-ACK information corresponding to the PDSCH within the first uplink time domain unit;
[0216] The terminal is triggered to feed back a Type-3 HARQ-ACK codebook or an enhanced Type-3 HARQ-ACK codebook via DCI within the first uplink time domain unit;
[0217] The terminal is triggered to perform a HARQ-ACK codebook retransmission DCI within the first uplink time domain unit.
[0218] Optionally, the first uplink time domain unit is a PUCCH slot.
[0219] Optionally, the time-domain cell type of the HARQ-ACK codebook can be explicitly indicated by an independent indicator field in the DCI, or implicitly indicated by other indicator fields in the DCI (such as the K1 indicator field, PRI indicator field, etc.).
[0220] Optionally, in the presence of multiple first DCIs, the time-domain unit types indicated by the multiple first DCIs are consistent, or the time-domain unit type of the HARQ-ACK codebook is the time-domain unit type indicated by the last first DCI among the multiple first DCIs.
[0221] 3) The time-domain unit type of the HARQ-ACK codebook is the time-domain unit type of the uplink physical channel carrying the HARQ-ACK codebook.
[0222] Optionally, the uplink physical channel may be a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
[0223] Optionally, when the uplink physical channel is PUCCH, the PUCCH resource corresponding to the PUCCH includes one of the following:
[0224] a) Public HARQ-ACK PUCCH resources;
[0225] For example, the PUCCH resource indicated by the parameter pucch-ResourceCommon in the configuration IE PUCCH-ConfigCommon.
[0226] b) Configure PUCCH resources for carrying SPS HARQ-ACK;
[0227] For example, the PUCCH resource is indicated by the following configuration parameters: n1PUCCH-AN in the IE SPS-Config or sps-PUCCH-AN-List-r16 in the IE PUCCH-Config.
[0228] c) Configure PUCCH resources to carry the HARQ-ACK codebook containing DG HARQ-ACK information;
[0229] For example, the PUCCH resource indicated by the configuration parameter PUCCH-ResourceSet.
[0230] Here, PUSCH can be understood as the PUSCH that reuses the HARQ-ACK codebook when Intra-UE UCI multiplexing occurs and HARQ-ACK is multiplexed onto PUSCH.
[0231] It is understandable that when the HARQ-ACK codebook is determined using Rule 2 mentioned above, the UE will only reuse the HARQ-ACK information corresponding to the PDSCH of the same time domain unit type in the same HARQ-ACK codebook.
[0232] The behavior of the UE is described below for various HARQ-ACK codebooks.
[0233] I. Construction of SPS HARQ-ACK bit sequence
[0234] When the HARQ-ACK codebook contains only SPS HARQ-ACK, the terminal, in determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, performs at least one of the following for the second SPS PDSCH:
[0235] 1) When using rule one, perform the following operation: if the first transmission opportunity satisfies the first time-domain relationship, determine the first transmission opportunity as an invalid transmission opportunity;
[0236] Understandably, when using Rule 1, it is determined whether each SPS PDSCH occasion corresponding to a certain SPS PDSCH is an Invalid PDSCH occasion based on at least one of Case 1, Case 2 (only when the corresponding DL active BWP configuration or application Configuration 1) and Case 4 mentioned above.
[0237] 2) When using rule two, perform at least one of the following operations: if the first transmission opportunity satisfies the first time-domain relationship, determine the first transmission opportunity as an invalid transmission opportunity; if the time-domain unit type corresponding to the first transmission opportunity is different from the time-domain unit type corresponding to the HARQ-ACK codebook, determine the first transmission opportunity as an invalid transmission opportunity.
[0238] Understandably, when Rule 2 is applied, it is determined whether each SPS PDSCH occasion corresponding to a given SPS PDSCH is an Invalid PDSCH occasion based on at least one of Case 1, Case 2 (only when the corresponding DL active BWP configuration or application Configuration 1) and Case 4 mentioned above; and / or, when the time-domain cell type of a given SPS PDSCH occasion is different from the time-domain cell type of the SPS HARQ-ACK bit sequence, it is determined to be an Invalid PDSCH occasion.
[0239] 3) If each transmission opportunity corresponding to the second SPS PDSCH is determined to be an invalid transmission opportunity, the second SPS PDSCH shall be used as the first SPS PDSCH.
[0240] It is understandable that when any SPS PDSCH occasion corresponding to a certain SPS PDSCH is determined to be an Invalid PDSCH occasion, there is no need to feed back the corresponding HARQ-ACK for this SPS PDSCH, or the HARQ-ACK bit corresponding to this SPS PDSCH can be directly set to NACK.
[0241] For this SPS PDSCH, the HARQ-ACK bit corresponding to it can be directly set to NACK. This can be done by constructing the codebook in the existing way and only modifying the HARQ-ACK bit value setting operation.
[0242] 4) If at least one transmission opportunity corresponding to the second SPS PDSCH is not determined to be an invalid transmission opportunity, the HARQ-ACK information corresponding to the second SPS PDSCH is fed back into the HARQ-ACK codebook;
[0243] It is understandable that when at least one SPS PDSCH occasion corresponding to a certain SPS PDSCH is not determined to be an Invalid PDSCH occasion, a corresponding HARQ-ACK needs to be sent for this SPS PDSCH.
[0244] The number of SPS PDSCH occasions corresponding to one SPS PDSCH is based on the repetition factor of its application. Sure.
[0245] Wherein, the second SPS PDSCH is a time-domain feedback offset based on transmission time and application, and it is expected that any SPS PDSCH corresponding to HARQ-ACK information will be fed back within the first uplink time-domain unit;
[0246] It should be noted that the transmission time here can be the end time of the SPS PDSCH, or the end time of the time slot in which the SPS PDSCH is located. The applied time-domain feedback offset is K1 applied by the SPS PDSCH when feeding back the corresponding HARQ-ACK information, indicated by activating or reactivating DCI, or configured by RRC signaling.
[0247] The first transmission opportunity is any one of the transmission opportunities corresponding to the second SPS PDSCH;
[0248] The first time-domain relationship includes at least one of the following:
[0249] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0250] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0251] It overlaps with the time domain of the semi-static uplink time domain unit.
[0252] For example, when rule one is adopted, and no corresponding HARQ-ACK is required for an SPS PDSCH that is determined to be invalid for any given SPS PDSCH occasion, the UE can perform the following pseudocode-based operation when constructing the SPS HARQ-ACK bit sequence:
[0253] The translations of the above pseudocode are shown below:
[0254] In the embodiments of this application, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal uses rule one or rule two to determine the HARQ-ACK codebook fed back in the first uplink time domain unit. For the HARQ-ACK codebook that only contains SPS HARQ-ACK, the terminal excludes the SPS PDSCH corresponding to the invalid transmission opportunity, which can control or reduce the HARQ-ACK feedback overhead, thereby improving the flexibility of HARQ-ACK feedback and reducing the HARQ-ACK feedback resource overhead, so as to improve the efficiency of system resource utilization.
[0255] II. Construction of Type-1 HARQ-ACK codebook under Single PDSCH scheduling
[0256] In some embodiments, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0257] When the scheduling type of the PDSCH is a single PDSCH scheduling, determine the time domain resource allocation record set corresponding to each first downlink time domain unit associated with the Type-1 HARQ-ACK codebook on each serving cell, determine the transmission opportunity subset corresponding to the first downlink time domain unit based on the time domain resource allocation record set, and generate the corresponding HARQ-ACK bit for each transmission opportunity in the transmission opportunity subset.
[0258] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the first time-domain resource allocation record:
[0259] 1) When using Rule 1 or Rule 2, perform the following operation: if the second transmission opportunity satisfies the second time-domain relationship, determine the second transmission opportunity as an invalid transmission opportunity;
[0260] 2) If each transmission opportunity corresponding to the first time domain resource allocation record is determined to be an invalid transmission opportunity, the first time domain resource allocation record shall be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit;
[0261] Wherein, the first time domain resource allocation record is any one of the time domain resource allocation record sets corresponding to the first downlink time domain unit; the initial value of the time domain resource allocation record set corresponding to the first downlink time domain unit is the time domain resource allocation record set determined based on the application's Time Domain Resource Allocation (TDRA) table;
[0262] The second transmission opportunity is any one of the transmission opportunities corresponding to the first time-domain resource allocation record;
[0263] The second time-domain relationship includes at least one of the following:
[0264] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0265] It overlaps with the time domain of the semi-static uplink time domain unit.
[0266] Optionally, the first downlink time-domain unit is a DL slot.
[0267] Optionally, a time-domain resource allocation record can be a Start and Length Indicator Value (SLIV). The following explanation uses SLIVs as the example of a time-domain resource allocation record. Correspondingly, a set of time-domain resource allocation records can be a set of SLIVs.
[0268] Understandably, when using Rule 1 or Rule 2, the terminal determines whether each PDSCH occasion corresponding to a certain SLIV is an Invalid PDSCH occasion based on at least one of Case 1 and Case 4 mentioned above. When any PDSCH occasion corresponding to a certain SLIV is determined to be an Invalid PDSCH occasion, this SLIV is removed from the SLIV set corresponding to its DL slot.
[0269] It is understandable that the number of PDSCH occasions corresponding to a certain SLIV is based on a defined maximum repetition factor. Determine if the parameter pdsch-AggregationFactor-r16 is provided to the UE in SPS-Config, or the parameter pdsch-AggregationFactor is provided in PDSCH-Config, and there is no line in pdsch-TimeDomainAllocationList and pdsch-TimeDomainAllocationListDCI-1-2 that contains the parameter repetitionNumber in PDSCH-TimeDomainResourceAllocation-r16. It should be the maximum value of the parameter pdsch-AggregationFactor-r16 in SPS-Config, or the parameter pdsch-AggregationFactor in PDSCH-Config; otherwise... ).
[0270] For example, when the UE determines the SLIV set corresponding to a certain DL slot, it can perform the operation corresponding to the following pseudocode:
[0271] The translations of the above pseudocode are shown below:
[0272] In this embodiment of the application, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal uses rule one or rule two to determine the HARQ-ACK codebook fed back in the first uplink time domain unit. For the Type-1 HARQ-ACK codebook, when the PDSCH scheduling type is single PDSCH scheduling, the terminal excludes the time domain resource allocation records corresponding to invalid transmission opportunities, which can control or reduce HARQ-ACK feedback overhead, thereby improving the flexibility of HARQ-ACK feedback and reducing HARQ-ACK feedback resource overhead, so as to improve the efficiency of system resource utilization.
[0273] III. Construction of Type-1 HARQ-ACK codebook under Multi-PDSCH scheduling
[0274] (a) Disable Time Domain Bundling
[0275] In some embodiments, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0276] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, the following operations are performed for each serving cell: Based on the application's time-domain feedback offset set and time-domain resource allocation (TDRA) table, determine the extended time-domain feedback offset set and the complete set of time-domain resource allocation records; determine the time-domain resource allocation record set corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell; determine the transmission opportunity subset corresponding to the first downlink time-domain unit based on the time-domain resource allocation record set; and generate the corresponding HARQ-ACK bits for each transmission opportunity in the transmission opportunity subset.
[0277] First, let's explain some of the terms used below:
[0278] The second time-domain resource allocation record is any one of the time-domain resource allocation records in the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, for example, the second time-domain resource allocation record is the second SLIV.
[0279] The initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the complete set of time-domain resource allocation records;
[0280] The third transmission opportunity is the single transmission opportunity (PDSCH occasion) corresponding to the second time-domain resource allocation record;
[0281] The third time-domain relationship includes at least one of the following:
[0282] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0283] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0284] It overlaps with the time domain of the semi-static uplink time domain unit.
[0285] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, for the second time-domain resource allocation record, at least one of the following is performed:
[0286] 1) When using Rule 1, perform the following operation: if the third transmission opportunity satisfies the third time-domain relationship, determine the third transmission opportunity as an invalid transmission opportunity;
[0287] It is understood that, when using Rule 1, it is determined whether a single PDSCH occasion corresponding to the second time-domain resource allocation record is an Invalid PDSCH occasion based on at least one of Case 1, Case 2, and Case 4.
[0288] It should be noted that multi-PDSCH scheduling and PDSCH repetition cannot be supported simultaneously. In other words, no row in the TDRA table that supports multi-PDSCH scheduling should apply a repetition factor.
[0289] Optionally, when the third time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the third transmission opportunity as an invalid transmission opportunity when the third transmission opportunity satisfies the third time-domain relationship includes at least one of the following:
[0290] a) If the downlink active bandwidth portion corresponding to the third transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation shall be performed: if the third transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the third transmission opportunity shall be determined as an invalid transmission opportunity.
[0291] It is understandable that, when determining whether a single PDSCH occasion corresponding to the second time-domain resource allocation record is an invalid PDSCH occasion based on Case 2, the determination of whether a single PDSCH occasion corresponding to the second time-domain resource allocation record is an invalid PDSCH occasion is only actually based on Case 2 when the corresponding DL active BWP configuration or application Configuration 1 is used.
[0292] b) For each time-domain feedback offset in the time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record.
[0293] Optionally, the time-domain feedback offset is K1, and the time-domain feedback offset set is set K1.
[0294] Understandably, for each K1 in the K1 set, it is determined whether the target row in the TDRA table is a schedulable row, where the target row is any row in the TDRA table. If the target row is a schedulable row, the starting time-domain resource allocation record (starting SLIV) of the target row is further determined, as well as the Symbol type (assuming it is the application Symbol type) of the single PDSCH occasion corresponding to this starting time-domain resource allocation record.
[0295] If the single transmission opportunity corresponding to the first time-domain resource allocation record configured in the target row does not overlap with both the sub-band full-duplex SBFD time-domain unit and the non-SBFD time-domain unit in the time domain, the target row is determined to be a schedulable row.
[0296] Understandably, if the single PDSCH occasion corresponding to the first SLIV configured in a line is determined to be an Invalid PDSCH occasion based on Case 1, then this line is determined to be an unschedulable line; otherwise, this line is determined to be a schedulable line.
[0297] Wherein, the starting time-domain resource allocation record is the first time-domain resource allocation record in the schedulable row, or the starting time-domain resource allocation record is the first target time-domain resource allocation record in the schedulable row, wherein the target time-domain resource allocation record is the time-domain resource allocation record for which the corresponding single transmission opportunity does not overlap with the time domain of the semi-static uplink time-domain unit.
[0298] It is understandable that the first SLIV in a schedulable line, or the first SLIV in a single PDSCH occasion that is determined to be a valid PDSCH occasion based on Case 4 (which requires a Valid SLIV), is taken as the starting SLIV for this line.
[0299] c) If the second time-domain resource allocation record is used as the starting time-domain resource allocation record in at least one schedulable row of the TDRA table, the third transmission opportunity is determined to be a valid transmission opportunity.
[0300] d) If the second time-domain resource allocation record is included in at least one schedulable row of the TDRA table and the second time-domain resource allocation record is not used as the starting time-domain resource allocation record in any of the at least one schedulable rows, perform the following operations: if the time-domain unit type of the third transmission opportunity is different from the application time-domain unit type of any of the at least one schedulable rows, determine the third transmission opportunity as an invalid transmission opportunity; or, if the time-domain unit type of the third transmission opportunity is the same as the application time-domain unit type of at least one of the at least one schedulable rows, determine the third transmission opportunity as a valid transmission opportunity.
[0301] Understandably, if a second SLIV is contained in at least one schedulable line but is not used as the starting SLIV in any of these schedulable lines, and the Symbol type of the single PDSCH occasion corresponding to the second SLIV is different from the application Symbol type of any schedulable line in which the second SLIV is located, then the single PDSCH occasion corresponding to the second SLIV is determined to be an Invalid PDSCH occasion. Otherwise, if the Symbol type of the single PDSCH occasion corresponding to the second SLIV is the same as the application time-domain unit type of at least one schedulable line in which the second SLIV is located, then the single PDSCH occasion corresponding to the second SLIV is determined to be a Valid PDSCH occasion.
[0302] e) If the second time-domain resource allocation record is not included in any schedulable row of the TDRA table, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0303] Understandably, if the second SLIV is not included in any schedulable line, the single PDSCH occasion corresponding to the second SLIV is determined to be an Invalid PDSCH occasion.
[0304] Wherein, the target row is any row in the TDRA table, and the application time domain unit type of the schedulable row is the time domain unit type of a single transmission opportunity corresponding to the starting time domain resource allocation record of the schedulable row;
[0305] 2) When using rule two, perform at least one of the following operations: if the third transmission opportunity satisfies the third time-domain relationship, determine the third transmission opportunity as an invalid transmission opportunity; if the time-domain unit type of the third transmission opportunity is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, determine the third transmission opportunity as an invalid transmission opportunity.
[0306] Understandably, when using Rule 2, it is determined whether a single PDSCH occasion corresponding to a certain SLIV is an Invalid PDSCH occasion based on at least one of Case 1, Case 2, and Case 4; and / or, if the Symbol type of a single PDSCH occasion corresponding to a certain SLIV is different from the Symbol type of the Type-1 HARQ-ACK codebook, the single PDSCH occasion corresponding to this SLIV is determined to be an Invalid PDSCH occasion.
[0307] 3) If a single transmission opportunity corresponding to the second time-domain resource allocation record is determined to be an invalid transmission opportunity, the second time-domain resource allocation record shall be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit;
[0308] Optionally, when a single PDSCH occasion corresponding to a certain SLIV is determined to be an invalid PDSCH occasion, this SLIV is removed from the SLIV set corresponding to the DL slot.
[0309] 4) If the second time-domain resource allocation record cannot feed back the corresponding HARQ-ACK information in the first uplink time-domain unit based on any row of the TDRA table where the second time-domain resource allocation record is located and any time-domain feedback offset, the second time-domain resource allocation record shall be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0310] Optionally, if a SLIV fails to send a corresponding HARQ-ACK within a specified PUCCH slot based on its row in the TDRA table and any K1, this SLIV is removed from the SLIV set corresponding to its DL slot. This can be understood as following the corresponding operation in related technologies (i.e., when the parameter pdsch-TimeDomainAllocationListForMultiPDSCH is provided to the UE, and the SLIV is located in slot n based on row r). 0,k +n D The HARQ-ACK information corresponding to the PDSCH time-domain resources within the slot n cannot be displayed. U During internal feedback, row r is excluded from the row set R.
[0311] In this embodiment, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal uses rule one or rule two to determine the HARQ-ACK codebook fed back in the first uplink time domain unit. For the Type-1 HARQ-ACK codebook, when the PDSCH scheduling type is multi-PDSCH scheduling and time domain binding is disabled, the terminal excludes time domain resource allocation records that are determined to be invalid transmission opportunities for the corresponding single transmission opportunity or time domain resource allocation records that cannot feed back the corresponding HARQ-ACK information in the first uplink time domain unit. This can control or reduce HARQ-ACK feedback overhead, thereby improving the flexibility of HARQ-ACK feedback and reducing HARQ-ACK feedback resource overhead, so as to improve the efficiency of system resource utilization.
[0312] (ii) Enable Time Domain Bundling
[0313] In some embodiments, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0314] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, the following operations are performed for each serving cell: only the last time-domain resource allocation record of each row in the application's TDRA table is retained; the set of time-domain resource allocation records corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell is determined; based on the set of time-domain resource allocation records, a subset of transmission opportunities corresponding to the first downlink time-domain unit is determined; and for each transmission opportunity in the subset of transmission opportunities, the corresponding HARQ-ACK bits are generated.
[0315] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the third time-domain resource allocation record:
[0316] 1) When using Rule 1, perform the following operation: if the fourth transmission opportunity satisfies the fourth time-domain relationship, determine the fourth transmission opportunity as an invalid transmission opportunity;
[0317] 2) When using rule two, perform at least one of the following operations: if the fourth transmission opportunity satisfies the fourth time-domain relationship, determine the fourth transmission opportunity as an invalid transmission opportunity; if the application time-domain unit type of any schedulable row corresponding to the third time-domain resource allocation record is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, determine each transmission opportunity corresponding to the third time-domain resource allocation record as an invalid transmission opportunity.
[0318] 3) If each transmission opportunity corresponding to the third time domain resource allocation record is determined to be an invalid transmission opportunity, the third time domain resource allocation record shall be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit;
[0319] Wherein, the third time-domain resource allocation record is any time-domain resource allocation record in the time-domain resource allocation record set; the initial value of the time-domain resource allocation record set is a set consisting of the last time-domain resource allocation record of each row in the TDRA table;
[0320] The fourth transmission opportunity is any one of the at least one transmission opportunities corresponding to the third time-domain resource allocation record;
[0321] The application time-domain unit type of the schedulable row is the time-domain unit type of a single transmission opportunity corresponding to the initial time-domain resource allocation record of the schedulable row;
[0322] The fourth time-domain relation includes at least one of the following:
[0323] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0324] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0325] It overlaps with the time domain of the semi-static uplink time domain unit.
[0326] When time domain bundling is enabled, when the UE constructs the Type-1 HARQ-ACK codebook fed back in the first uplink time domain unit (e.g., specifying the PUCCH slot), it first retains only the Last SLIVs of each row in the TDRA table for each Serving cell, then determines the SLIV set corresponding to each DL slot associated with this Type-1 HARQ-ACK codebook on this Serving cell (the initial value of this SLIV set is the Last SLIV set), and determines the corresponding Occasion subset based on the SLIV set. Then, for each determined Occasion, it generates the corresponding HARQ-ACK bits. When determining the SLIV set corresponding to a certain DL slot, the UE performs at least one of the following (1) to (3):
[0327] (1) When using rule 1, determine whether at least one PDSCH occasion corresponding to a certain Last SLIV is an Invalid PDSCH occasion based on at least one of Case 1, Case 2 and Case 4.
[0328] It is important to note that a given Last SLIV corresponds to a single PDSCH occasion for each SLIV in the row containing it in the TDRA table (each row must have at least one SLIV configured). When this Last SLIV is the Last SLIV for multiple rows in the TDRA table, this Last SLIV corresponds to a single PDSCH occasion for each SLIV in each of those multiple rows.
[0329] (2) When rule 2 is used, determine whether at least one PDSCH occasion corresponding to a certain Last SLIV is an Invalid PDSCH occasion based on at least one of Case 1, Case 2 and Case 4; and / or, when the application Symbol type of any schedulable line corresponding to a certain Last SLIV is not the same as the Symbol type of the Type-1 HARQ-ACK codebook, determine all PDSCH occasions corresponding to this Last SLIV as Invalid PDSCH occasions.
[0330] (3) When all PDSCH occasions corresponding to a certain Last SLIV are determined to be Invalid PDSCH occasions, this Last SLIV is removed from the SLIV set corresponding to the DL slot.
[0331] When setting the HARQ-ACK bit value, for at least one PDSCH scheduled in a row of a DCI indicator TDRA table, only the PDSCH occasion corresponding to the single PDSCH occasion in this row that is determined to be an invalid PDSCH occasion participates in the Time domain bundling operation (e.g., performing a binary AND operation), or all PDSCH occasions in this row participate in the Time domain bundling operation, but the PDSCH occasion corresponding to the single PDSCH occasion that is determined to be an invalid PDSCH occasion is assumed to be correctly received (thus avoiding affecting the result of the binary AND operation); then, the UE sets the HARQ-ACK bit corresponding to the Occasion mapped in this row based on the operation result.
[0332] In some embodiments, when the fourth time-domain relationship includes time-domain overlap of time-domain units that completely correspond to invalid time-domain unit types, determining that the fourth transmission opportunity is an invalid transmission opportunity when the fourth transmission opportunity satisfies the fourth time-domain relationship includes at least one of the following:
[0333] If the downlink active bandwidth portion of the fourth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fourth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fourth transmission opportunity is determined to be an invalid transmission opportunity.
[0334] For each time-domain feedback offset in the application's time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record;
[0335] If none of the rows corresponding to the third time-domain resource allocation record are schedulable rows, then each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity.
[0336] The target row is any row in the TDRA table.
[0337] It is understandable that when determining whether at least one PDSCH occasion corresponding to a certain Last SLIV (i.e., the third time domain resource allocation record) is an Invalid PDSCH occasion based on Case 2, the UE performs at least one of the following (1) to (3):
[0338] (1) Only when the corresponding DL active BWP configuration or application Configuration 1 is the at least one PDSCH occasion corresponding to the reference SLIV actually determined as an Invalid PDSCH occasion based on Case 2;
[0339] (2) For each K1 in the K1 set, determine whether any row in the TDRA table is a schedulable row. If it is a schedulable row, further determine the starting SLIV of this row and the Symbol type (assuming it is the application Symbol type) of the single PDSCH occasion corresponding to this starting SLIV: If the single PDSCH occasion corresponding to the first SLIV configured in a row is determined to be an Invalid PDSCH occasion based on Case 1, then this row is determined to be an unschedulable row; otherwise, this row is determined to be a schedulable row. Take the first SLIV in a schedulable row, or the first SLIV among the SLIVs whose corresponding single PDSCH occasion is determined to be a Valid PDSCH occasion based on Case 4 (which requires a Valid SLIV), as the starting SLIV of this row;
[0340] (3) When any row corresponding to the third time domain resource allocation record in the TDRA table is not a schedulable row, determine that all PDSCH occasions corresponding to the third time domain resource allocation record are invalid PDSCH occasions; otherwise, determine that all PDSCH occasions corresponding to the third time domain resource allocation record are valid PDSCH occasions.
[0341] In this embodiment, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal uses rule one or rule two to determine the HARQ-ACK codebook fed back in the first uplink time domain unit. For the Type-1 HARQ-ACK codebook, when the PDSCH scheduling type is multi-PDSCH scheduling and time domain binding is enabled, the terminal excludes the time domain resource allocation records where each corresponding transmission opportunity is determined to be an invalid transmission opportunity. This can control or reduce the HARQ-ACK feedback overhead, thereby improving the flexibility of HARQ-ACK feedback and reducing the HARQ-ACK feedback resource overhead, so as to improve the efficiency of system resource utilization.
[0342] IV. Construction of the Type-2 HARQ-ACK codebook under Multi-PDSCH scheduling
[0343] In some embodiments, when the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, performing the corresponding second codebook construction operation based on the target information includes at least one of the following:
[0344] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, two HARQ-ACK sub-codebooks are constructed. In the process of constructing the two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate the HARQ-ACK bit corresponding to the scheduled PDSCH.
[0345] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, TB groups or PDSCH groups are divided based on higher-layer configuration parameters, and one or two HARQ-ACK subcodebooks are constructed. In the process of constructing the one or two HARQ-ACK subcodebooks, the following operations are performed for the first TB group or the first PDSCH group: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, it is determined whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and HARQ-ACK bits corresponding to the first TB group or the first PDSCH group are generated.
[0346] It is understandable that when the UE constructs the Type-2 HARQ-ACK codebook fed back within the specified PUCCH slot, it can distinguish between the following two cases and perform the corresponding operations respectively:
[0347] When time-domain binding is disabled, the UE can use a mechanism from related technologies to construct two HARQ-ACK sub-codebooks when constructing the Type-2 HARQ-ACK codebook fed back in the first uplink time-domain unit. Specifically, during the construction of these two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and generating the HARQ-ACK bits corresponding to the scheduled PDSCH.
[0348] When time domain bundling is enabled, the UE can use the existing protocol mechanism to construct the Type-2 HARQ-ACK codebook fed back within the first uplink time domain unit. This involves dividing the codebook into TB groups (when spatial bundling is disabled) or PDSCH groups (when spatial bundling is enabled) based on higher-layer configuration parameters, and constructing one or two HARQ-ACK sub-codebooks (when time domain bundling is disabled, or when time domain bundling is enabled and...). When constructing a Serving cell, two HARQ-ACK codebooks are constructed; otherwise, a single HARQ-ACK codebook is constructed. During the construction of the single or two HARQ-ACK sub-codebooks, the following operations are performed for the first TB group or the first PDSCH group: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate HARQ-ACK bits corresponding to the first TB group or the first PDSCH group. Wherein, the first TB group is one of at least one TB group divided based on higher-layer configuration parameters, and the first PDSCH group is one of at least one PDSCH group divided based on higher-layer configuration parameters.
[0349] The following explanations address the relevant concepts:
[0350] The fifth transmission opportunity is a single transmission opportunity corresponding to the scheduled PDSCH;
[0351] The fifth time-domain relation includes at least one of the following:
[0352] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0353] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0354] It overlaps with the time domain of the semi-static uplink time domain unit.
[0355] Determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity includes at least one of the following:
[0356] 1) When using Rule 1, perform the following operation: if the fifth transmission opportunity satisfies the fifth time-domain relationship, determine the fifth transmission opportunity as an invalid transmission opportunity;
[0357] It is understood that, when using Rule 1, it is determined whether the individual PDSCH occasion corresponding to the scheduled PDSCH is an invalid PDSCH occasion based on at least one of Case 1, Case 2 and Case 4 above.
[0358] When determining whether a single PDSCH occasion corresponding to the scheduled PDSCH is an Invalid PDSCH occasion based on Case 2, the following example is provided:
[0359] In some embodiments, when the fifth time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the fifth transmission opportunity as an invalid transmission opportunity when the fifth transmission opportunity satisfies the fifth time-domain relationship includes at least one of the following:
[0360] a) If the downlink active bandwidth portion corresponding to the fifth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation shall be performed: if the fifth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fifth transmission opportunity shall be determined as an invalid transmission opportunity.
[0361] That is, only when the corresponding DL active BWP configuration or application Configuration 1 is the case 2 used to determine whether the single PDSCH occasion corresponding to the reference PDSCH is an Invalid PDSCH occasion.
[0362] b) Determine the starting PDSCH of the target schedule and the application time-domain unit type of the target schedule, wherein the target schedule is a single schedule based on the multi-PDSCH scheduling TDRA table, the scheduled PDSCH is one of at least one PDSCH corresponding to the target schedule, and the HARQ-ACK information corresponding to the target schedule is fed back in the Type-2 HARQ-ACK codebook; the application time-domain unit type of the target schedule is the time-domain unit type of a single transmission opportunity corresponding to the starting PDSCH of the target schedule;
[0363] In some embodiments, determining the starting PDSCH for the target schedule includes one of the following:
[0364] The first PDSCH in at least one PDSCH corresponding to the target schedule is taken as the starting PDSCH of the target schedule;
[0365] The first valid PDSCH in at least one PDSCH corresponding to the target schedule is used as the starting PDSCH of the target schedule. The valid PDSCH is the single transmission opportunity that is determined to be a valid transmission opportunity and is the PDSCH corresponding to the target schedule.
[0366] For a given scheduling based on the Multi-PDSCH scheduling TDRA table (this scheduling is indicated by the DCI to a row in the Multi-PDSCH scheduling TDRA table, and the HARQ-ACK information corresponding to this scheduling is fed back in the codebook above), the PDSCH occasion corresponding to the first PDSCH of this scheduling will not be judged as an Invalid PDSCH occasion based on Case 1 (based on the Agreement: It is not expected that the first transmission / reception occasion indicated by scheduling DCI is mapped to both SBFD and non-SBFD symbols): the first PDSCH of this scheduling, or the first PDSCH among the PDSCHs whose single PDSCH occasion is determined to be a Valid PDSCH occasion based on Case 4 (which requires Valid PDSCH), is taken as the starting PDSCH of this scheduling; the Symbol type of the single PDSCH occasion corresponding to the starting PDSCH of this scheduling is taken as the application Symbol type of this scheduling.
[0367] c) If the scheduled PDSCH is the starting PDSCH of the target scheduling, determine the fifth transmission opportunity as a valid transmission opportunity.
[0368] When the scheduled PDSCH is used as the starting PDSCH for a certain scheduling, the single PDSCH occasion corresponding to the scheduled PDSCH is determined to be a Valid PDSCH occasion.
[0369] d) If the scheduled PDSCH is not used as the starting PDSCH in the target schedule, perform the following operations: if the time domain unit type of the fifth transmission opportunity is different from the application time domain unit type of the target schedule, determine the fifth transmission opportunity as an invalid transmission opportunity; if the time domain unit type of the fifth transmission opportunity is the same as the application time domain unit type of the target schedule, determine the fifth transmission opportunity as a valid transmission opportunity.
[0370] It is understood that, if the scheduled PDSCH is not used as the starting PDSCH for a certain scheduling, and the Symbol type of the single transmission opportunity corresponding to the scheduled PDSCH is different from the application Symbol type of this scheduling, the single PDSCH occasion corresponding to the scheduled PDSCH is determined to be an Invalid PDSCH occasion; otherwise, the single PDSCH occasion corresponding to the scheduled PDSCH is determined to be a Valid PDSCH occasion.
[0371] 2) When using rule two, perform at least one of the following operations: if the fifth transmission opportunity satisfies the fifth time-domain relationship, determine the fifth transmission opportunity as an invalid transmission opportunity; if the time-domain unit type of the fifth transmission opportunity is different from the time-domain unit type of the Type-2 HARQ-ACK codebook, determine the fifth transmission opportunity as an invalid transmission opportunity.
[0372] Understandably, when rule 2 is applied, it is determined whether a single PDSCH occasion corresponding to the scheduled PDSCH is an invalid PDSCH occasion based on at least one of Case 1, Case 2, and Case 4; and / or, when the Symbol type of a single PDSCH occasion corresponding to the scheduled PDSCH is different from the Symbol type of the Type-2 HARQ-ACK codebook, the single PDSCH occasion corresponding to the scheduled PDSCH is determined to be an invalid PDSCH occasion.
[0373] In some embodiments, generating the HARQ-ACK bits corresponding to the scheduled PDSCH includes:
[0374] If the fifth transmission opportunity is determined to be an invalid transmission opportunity, the HARQ-ACK bit corresponding to the scheduled PDSCH is set to NACK;
[0375] Understandably, when time-domain binding is disabled, during the construction of the HARQ-ACK codebook, the terminal performs the following operations for a scheduled PDSCH: determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and generating the HARQ-ACK bit corresponding to the scheduled PDSCH. Specifically, generating the HARQ-ACK bit corresponding to the scheduled PDSCH includes: if the fifth transmission opportunity is determined to be an invalid transmission opportunity, setting the HARQ-ACK bit corresponding to the scheduled PDSCH to NACK.
[0376] In some embodiments, generating the HARQ-ACK bits corresponding to the first TB group or the first PDSCH group includes:
[0377] In the case that the first TB group or the first PDSCH group corresponds to at least one valid PDSCH, the terminal assumes that any invalid PDSCH corresponding to the first TB group or the first PDSCH group is correctly received.
[0378] If each scheduled PDSCH corresponding to the first TB group or the first PDSCH group is determined to be an invalid PDSCH, the HARQ-ACK bit corresponding to the first TB group or the first PDSCH group is set to NACK.
[0379] Wherein, the valid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be a valid transmission opportunity, and the invalid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be an invalid transmission opportunity.
[0380] Understandably, when time-domain bundling is enabled, the terminal performs the following operations during the construction of the HARQ-ACK codebook for the first TB group or the first PDSCH group: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, determines whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and generates HARQ-ACK bits corresponding to the first TB group or the first PDSCH group. Generating HARQ-ACK bits corresponding to the first TB group or the first PDSCH group includes: when the first TB group or the first PDSCH group corresponds to at least one valid PDSCH, the terminal assumes that any invalid PDSCH corresponding to the first TB group or the first PDSCH group is correctly received, that is, when performing a binary AND operation for time-domain bundling, it assumes that the HARQ-ACK corresponding to this invalid PDSCH is ACK; when each scheduled PDSCH corresponding to the first TB group or the first PDSCH group is determined to be an invalid PDSCH, the HARQ-ACK bit corresponding to the first TB group or the first PDSCH group is set to NACK.
[0381] In this embodiment, when there are invalid transmission opportunities among the transmission opportunities corresponding to the target physical shared channel, the terminal uses rule one or rule two to determine the HARQ-ACK codebook fed back in the first uplink time domain unit. For the Type-2 HARQ-ACK codebook, when the PDSCH scheduling type is multi-PDSCH scheduling, it distinguishes between disabling time domain binding and enabling time domain binding. When the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity, the terminal sets the HARQ-ACK bit corresponding to the scheduled PDSCH to NACK, thereby ensuring that the terminal and the network-side equipment have a completely consistent understanding of the HARQ-ACK bit values of the fed-back HARQ-ACK codebook, which can improve the reliability of HARQ-ACK feedback.
[0382] Figure 3 is a second schematic flowchart of the shared channel transmission and HARQ-ACK feedback method provided in the embodiments of this application. As shown in Figure 3, the shared channel transmission and HARQ-ACK feedback method includes:
[0383] Step 300: If there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the network-side device performs a second operation, the second operation including at least one of the following:
[0384] Determine the physical shared channel that needs to be transmitted;
[0385] The network-side device receives the HARQ-ACK codebook from the terminal within the first uplink time domain unit. The HARQ-ACK codebook is determined by the terminal using one of the following rules:
[0386] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0387] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0388] The shared channel transmission and HARQ-ACK feedback method provided in this application is executed by a network-side device. It belongs to the same inventive concept as the aforementioned terminal-side shared channel transmission and HARQ-ACK feedback method and can achieve the same technical effect. Therefore, the relevant content will not be repeated.
[0389] Optionally, a target transmission opportunity is determined to be an invalid transmission opportunity if it satisfies at least one of the following time-domain relationships:
[0390] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0391] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0392] When the target transmission opportunity corresponds to a physical uplink shared channel (PUSCH), it overlaps with the time domain of the semi-static downlink time domain unit or the synchronization signal block time domain unit.
[0393] When the target transmission opportunity corresponds to one PDSCH, it overlaps with the time domain of the semi-static uplink time domain unit.
[0394] The target transmission opportunity is a single transmission opportunity among the transmission opportunities corresponding to the target physical shared channel.
[0395] Optionally, the determination of the physical shared channel to be transmitted satisfies at least one of the following:
[0396] When scheduling at least one physical shared channel transmission opportunity through a single downlink control information (DCI), it is guaranteed that each physical shared channel transmission opportunity scheduled by the DCI will not be determined as an invalid transmission opportunity.
[0397] When multiple semi-persistent scheduling (SPS) PDSCHs are configured for the terminal in a single first downlink time domain unit on a serving cell, the network-side device determines the remaining SPS PDSCHs, without considering SPS PDSCHs whose corresponding transmission opportunities are determined to be invalid transmission opportunities.
[0398] Optionally, the HARQ-ACK codebook is determined by the terminal by performing at least one of the following:
[0399] Determine the time-domain unit type corresponding to the HARQ-ACK codebook;
[0400] When the HARQ-ACK codebook contains only SPS HARQ-ACK, the terminal, in determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, excludes the first SPS PDSCH, or sets the SPS HARQ-ACK bit corresponding to the first SPS PDSCH to NACK. The first SPS PDSCH is the SPS PDSCH whose corresponding transmission opportunity is determined to be an invalid transmission opportunity.
[0401] If the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information;
[0402] If the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, then according to the target information, the corresponding second codebook construction operation is performed;
[0403] The target information includes at least one of the following:
[0404] PDSCH scheduling type;
[0405] The HARQ-ACK codebook needs to provide feedback on whether the transmission opportunity corresponding to the PDSCH with the corresponding HARQ-ACK information has been determined as an invalid transmission opportunity.
[0406] Optionally, the time-domain unit type of the HARQ-ACK codebook satisfies one of the following:
[0407] The time-domain cell type of the HARQ-ACK codebook is the time-domain cell type of the target PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook;
[0408] The time-domain unit type of the HARQ-ACK codebook is indicated by the first DCI that triggers the terminal to feed back the HARQ-ACK codebook;
[0409] The time-domain unit type of the HARQ-ACK codebook is the time-domain unit type of the uplink physical channel carrying the HARQ-ACK codebook.
[0410] Optionally, the target PDSCH includes at least one of the following:
[0411] The HARQ-ACK codebook feeds back all PDSCHs corresponding to the HARQ-ACK information;
[0412] The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the earliest or latest PDSCH with the first target time. The first target time includes one of the following: the start time or end time of the PDSCH, or the start time or end time of the first time domain unit in which the PDSCH is located.
[0413] The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the earliest or latest PDSCH with the second target time. The second target time includes one of the following: the start time or end time of the second DCI, the start time or end time of the control resource set CORESET that sends the second DCI, and the start time or end time of the first time domain unit where the CORESET that sends the second DCI is located. The second DCI is used to schedule the PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook.
[0414] Optionally, the first DCI that triggers the terminal to feed back the HARQ-ACK codebook includes at least one of the following:
[0415] The DCI schedules the PDSCH and instructs the terminal to feed back the HARQ-ACK information corresponding to the PDSCH within the first uplink time domain unit;
[0416] The terminal is triggered to feed back a Type-3 HARQ-ACK codebook or an enhanced Type-3 HARQ-ACK codebook via DCI within the first uplink time domain unit;
[0417] The terminal is triggered to perform a HARQ-ACK codebook retransmission DCI within the first uplink time domain unit.
[0418] Optionally, if the HARQ-ACK codebook only contains SPS HARQ-ACK, when the terminal determines the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, it performs at least one of the following for the second SPS PDSCH:
[0419] When using rule one, the following operations are performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity is determined to be an invalid transmission opportunity;
[0420] When using rule two, at least one of the following operations shall be performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type corresponding to the first transmission opportunity is different from the time-domain unit type corresponding to the HARQ-ACK codebook, the first transmission opportunity shall be determined as an invalid transmission opportunity.
[0421] If each transmission opportunity corresponding to the second SPS PDSCH is determined to be an invalid transmission opportunity, the second SPS PDSCH shall be used as the first SPS PDSCH.
[0422] If at least one transmission opportunity corresponding to the second SPS PDSCH is not determined to be an invalid transmission opportunity, the HARQ-ACK information corresponding to the second SPS PDSCH is fed back in the HARQ-ACK codebook.
[0423] Wherein, the second SPS PDSCH is a time-domain feedback offset based on transmission time and application, and it is expected that any SPS PDSCH corresponding to HARQ-ACK information will be fed back within the first uplink time-domain unit;
[0424] The first transmission opportunity is any one of the transmission opportunities corresponding to the second SPS PDSCH;
[0425] The first time-domain relationship includes at least one of the following:
[0426] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0427] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0428] It overlaps with the time domain of the semi-static uplink time domain unit.
[0429] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0430] When the scheduling type of the PDSCH is a single PDSCH scheduling, determine the time domain resource allocation record set corresponding to each first downlink time domain unit associated with the Type-1 HARQ-ACK codebook on each serving cell, determine the transmission opportunity subset corresponding to the first downlink time domain unit based on the time domain resource allocation record set, and generate the corresponding HARQ-ACK bit for each transmission opportunity in the transmission opportunity subset.
[0431] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the first time-domain resource allocation record:
[0432] When using either Rule 1 or Rule 2, perform the following operation: if the second transmission opportunity satisfies the second time-domain relationship, determine the second transmission opportunity as an invalid transmission opportunity;
[0433] If each transmission opportunity corresponding to the first time domain resource allocation record is determined to be an invalid transmission opportunity, the first time domain resource allocation record will be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit.
[0434] Wherein, the first time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the time-domain resource allocation record set determined based on the application's time-domain resource allocation table;
[0435] The second transmission opportunity is any one of the transmission opportunities corresponding to the first time-domain resource allocation record;
[0436] The second time-domain relationship includes at least one of the following:
[0437] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0438] It overlaps with the time domain of the semi-static uplink time domain unit.
[0439] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0440] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, the following operations are performed for each serving cell: Based on the application's time-domain feedback offset set and time-domain resource allocation (TDRA) table, determine the extended time-domain feedback offset set and the complete set of time-domain resource allocation records; determine the time-domain resource allocation record set corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell; determine the transmission opportunity subset corresponding to the first downlink time-domain unit based on the time-domain resource allocation record set; and generate the corresponding HARQ-ACK bits for each transmission opportunity in the transmission opportunity subset.
[0441] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the second time-domain resource allocation record:
[0442] When using Rule 1, the following operation is performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0443] When using Rule 2, at least one of the following operations shall be performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the third transmission opportunity is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, the third transmission opportunity shall be determined as an invalid transmission opportunity.
[0444] If a single transmission opportunity corresponding to the second time-domain resource allocation record is determined to be an invalid transmission opportunity, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0445] If the second time-domain resource allocation record cannot feed back the corresponding HARQ-ACK information in the first uplink time-domain unit based on any row of the TDRA table where the second time-domain resource allocation record is located and any time-domain feedback offset, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0446] Wherein, the second time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the complete set of time-domain resource allocation records;
[0447] The third transmission opportunity is a single transmission opportunity corresponding to the second time-domain resource allocation record;
[0448] The third time-domain relationship includes at least one of the following:
[0449] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0450] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0451] It overlaps with the time domain of the semi-static uplink time domain unit.
[0452] Optionally, when the third time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the third transmission opportunity as an invalid transmission opportunity when the third transmission opportunity satisfies the third time-domain relationship includes at least one of the following:
[0453] Only when the downlink active bandwidth corresponding to the third transmission opportunity is configured or application configuration scheme 1 is applied, the following operation is performed: if the third transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0454] For each time-domain feedback offset in the time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record;
[0455] If the second time-domain resource allocation record is used as the starting time-domain resource allocation record in at least one schedulable row of the TDRA table, the third transmission opportunity is determined to be a valid transmission opportunity.
[0456] If the second time-domain resource allocation record is included in at least one schedulable row of the TDRA table and the second time-domain resource allocation record is not used as the starting time-domain resource allocation record in any of the at least one schedulable rows, the following operations are performed: if the time-domain unit type of the third transmission opportunity is different from the application time-domain unit type of any of the at least one schedulable rows, the third transmission opportunity is determined to be an invalid transmission opportunity; or, if the time-domain unit type of the third transmission opportunity is the same as the application time-domain unit type of at least one of the at least one schedulable rows, the third transmission opportunity is determined to be a valid transmission opportunity.
[0457] If the second time-domain resource allocation record is not included in any schedulable row of the TDRA table, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0458] Wherein, the target row is any row in the TDRA table, and the application time domain unit type of the schedulable row is the time domain unit type of a single transmission opportunity corresponding to the starting time domain resource allocation record of the schedulable row.
[0459] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0460] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, the following operations are performed for each serving cell: only the last time-domain resource allocation record of each row in the application's TDRA table is retained; the set of time-domain resource allocation records corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell is determined; based on the set of time-domain resource allocation records, a subset of transmission opportunities corresponding to the first downlink time-domain unit is determined; and for each transmission opportunity in the subset of transmission opportunities, the corresponding HARQ-ACK bits are generated.
[0461] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the third time-domain resource allocation record:
[0462] When using Rule 1, the following operation is performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity is determined to be an invalid transmission opportunity;
[0463] When using Rule 2, at least one of the following operations shall be performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity shall be determined as an invalid transmission opportunity; if the application time-domain unit type of any schedulable row corresponding to the third time-domain resource allocation record is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, each transmission opportunity corresponding to the third time-domain resource allocation record shall be determined as an invalid transmission opportunity.
[0464] If each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity, the third time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0465] Wherein, the third time-domain resource allocation record is any time-domain resource allocation record in the time-domain resource allocation record set; the initial value of the time-domain resource allocation record set is a set consisting of the last time-domain resource allocation record of each row in the TDRA table;
[0466] The fourth transmission opportunity is any one of the at least one transmission opportunities corresponding to the third time-domain resource allocation record;
[0467] The application time-domain unit type of the schedulable row is the time-domain unit type of a single transmission opportunity corresponding to the initial time-domain resource allocation record of the schedulable row;
[0468] The fourth time-domain relation includes at least one of the following:
[0469] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0470] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0471] It overlaps with the time domain of the semi-static uplink time domain unit.
[0472] Optionally, when the fourth time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the fourth transmission opportunity as an invalid transmission opportunity when the fourth transmission opportunity satisfies the fourth time-domain relationship includes at least one of the following:
[0473] If the downlink active bandwidth portion of the fourth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fourth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fourth transmission opportunity is determined to be an invalid transmission opportunity.
[0474] For each time-domain feedback offset in the application's time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record;
[0475] If none of the rows corresponding to the third time-domain resource allocation record are schedulable rows, then each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity.
[0476] The target row is any row in the TDRA table.
[0477] Optionally, when the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, performing the corresponding second codebook construction operation based on the target information includes at least one of the following:
[0478] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, two HARQ-ACK sub-codebooks are constructed. In the process of constructing the two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate the HARQ-ACK bit corresponding to the scheduled PDSCH.
[0479] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, TB groups or PDSCH groups are divided based on higher-layer configuration parameters, and one or two HARQ-ACK subcodebooks are constructed. In the process of constructing the one or two HARQ-ACK subcodebooks, for the first TB group or the first PDSCH group, the following operations are performed: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, it is determined whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and HARQ-ACK bits corresponding to the first TB group or the first PDSCH group are generated.
[0480] Determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity includes at least one of the following:
[0481] When using Rule 1, the following operation is performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity;
[0482] When using Rule 2, at least one of the following operations shall be performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the fifth transmission opportunity is different from the time-domain unit type of the Type-2 HARQ-ACK codebook, the fifth transmission opportunity shall be determined as an invalid transmission opportunity.
[0483] Wherein, the first TB group is one of the TB groups divided based on the high-level configuration parameters, and the first PDSCH group is one of the PDSCH groups divided based on the high-level configuration parameters.
[0484] The fifth transmission opportunity is a single transmission opportunity corresponding to the scheduled PDSCH;
[0485] The fifth time-domain relation includes at least one of the following:
[0486] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0487] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0488] It overlaps with the time domain of the semi-static uplink time domain unit.
[0489] Optionally, if the fifth time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, and the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity, including at least one of the following:
[0490] If the downlink active bandwidth portion of the fifth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fifth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fifth transmission opportunity is determined to be an invalid transmission opportunity.
[0491] The starting PDSCH of the target scheduling and the application time-domain unit type of the target scheduling are determined, wherein the target scheduling is a single scheduling based on the multi-PDSCH scheduling TDRA table, the scheduled PDSCH is one of at least one PDSCH corresponding to the target scheduling, and the HARQ-ACK information corresponding to the target scheduling is fed back in the Type-2 HARQ-ACK codebook; the application time-domain unit type of the target scheduling is the time-domain unit type of a single transmission opportunity corresponding to the starting PDSCH of the target scheduling.
[0492] If the scheduled PDSCH is used as the starting PDSCH of the target scheduling, the fifth transmission opportunity is determined to be a valid transmission opportunity.
[0493] If the scheduled PDSCH is not used as the starting PDSCH in the target schedule, the following operations are performed: if the time domain unit type of the fifth transmission opportunity is different from the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be an invalid transmission opportunity; if the time domain unit type of the fifth transmission opportunity is the same as the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be a valid transmission opportunity.
[0494] Optionally, generating the HARQ-ACK bits corresponding to the scheduled PDSCH includes:
[0495] If the fifth transmission opportunity is determined to be an invalid transmission opportunity, the HARQ-ACK bit corresponding to the scheduled PDSCH is set to NACK.
[0496] Optionally, generating the HARQ-ACK bits corresponding to the first TB group or the first PDSCH group includes:
[0497] In the case that the first TB group or the first PDSCH group corresponds to at least one valid PDSCH, the terminal assumes that any invalid PDSCH corresponding to the first TB group or the first PDSCH group is correctly received.
[0498] If each scheduled PDSCH corresponding to the first TB group or the first PDSCH group is determined to be an invalid PDSCH, the HARQ-ACK bit corresponding to the first TB group or the first PDSCH group is set to NACK.
[0499] Wherein, the valid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be a valid transmission opportunity, and the invalid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be an invalid transmission opportunity.
[0500] The shared channel transmission and HARQ-ACK feedback method provided in this application can be executed by a shared channel transmission and HARQ-ACK feedback device. This application uses the shared channel transmission and HARQ-ACK feedback device as an example to illustrate the shared channel transmission and HARQ-ACK feedback device provided in this application.
[0501] This application provides a shared channel transmission and HARQ-ACK feedback device. As an example, the shared channel transmission and HARQ-ACK feedback device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.
[0502] The shared channel transmission and HARQ-ACK feedback device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include a general-purpose processor, a special-purpose processor, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.
[0503] Specifically, Figure 4 is one of the structural schematic diagrams of the shared channel transmission and HARQ-ACK feedback device provided in the embodiments of this application. Referring to Figure 4, when the shared channel transmission and HARQ-ACK feedback device is a terminal or a component in a terminal, the shared channel transmission and HARQ-ACK feedback device 400 includes a first processing module 401, used to perform a first operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel. The first operation includes at least one of the following:
[0504] Determine the physical shared channel that needs to be transmitted;
[0505] When the target physical shared channel is a physical downlink shared channel (PDSCH), one of the following rules is used to determine the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit:
[0506] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0507] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0508] Optionally, a target transmission opportunity is determined to be an invalid transmission opportunity if it satisfies at least one of the following time-domain relationships:
[0509] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0510] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0511] When the target transmission opportunity corresponds to a physical uplink shared channel (PUSCH), it overlaps with the time domain of the semi-static downlink time domain unit or the synchronization signal block time domain unit.
[0512] When the target transmission opportunity corresponds to one PDSCH, it overlaps with the time domain of the semi-static uplink time domain unit.
[0513] The target transmission opportunity is a single transmission opportunity among the transmission opportunities corresponding to the target physical shared channel.
[0514] Optionally, the determination of the physical shared channel to be transmitted satisfies at least one of the following:
[0515] When a single downlink control information (DCI) schedules at least one physical shared channel transmission opportunity, the terminal does not expect each physical shared channel transmission opportunity scheduled by the DCI to be determined as an invalid transmission opportunity.
[0516] When the terminal is configured with multiple semi-persistent scheduling (SPS) PDSCHs in a single first downlink time domain unit on a serving cell, the terminal determines the remaining SPS PDSCHs, regardless of the SPS PDSCHs whose corresponding transmission opportunities are determined to be invalid transmission opportunities.
[0517] Optionally, determining the HARQ-ACK codebook includes at least one of the following:
[0518] Determine the time-domain unit type corresponding to the HARQ-ACK codebook;
[0519] When the HARQ-ACK codebook contains only SPS HARQ-ACK, in the process of determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, the first SPS PDSCH is excluded, or the SPS HARQ-ACK bit corresponding to the first SPS PDSCH is set to NACK, and the first SPS PDSCH is the SPS PDSCH whose corresponding transmission opportunity is determined to be an invalid transmission opportunity.
[0520] If the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information;
[0521] If the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, then according to the target information, the corresponding second codebook construction operation is performed;
[0522] The target information includes at least one of the following:
[0523] PDSCH scheduling type;
[0524] The HARQ-ACK codebook needs to provide feedback on whether the transmission opportunity corresponding to the PDSCH with the corresponding HARQ-ACK information has been determined as an invalid transmission opportunity.
[0525] Optionally, the time-domain unit type of the HARQ-ACK codebook satisfies one of the following:
[0526] The time-domain cell type of the HARQ-ACK codebook is the time-domain cell type of the target PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook;
[0527] The time-domain unit type of the HARQ-ACK codebook is indicated by the first DCI that triggers the terminal to feed back the HARQ-ACK codebook;
[0528] The time-domain unit type of the HARQ-ACK codebook is the time-domain unit type of the uplink physical channel carrying the HARQ-ACK codebook.
[0529] Optionally, the target PDSCH includes at least one of the following:
[0530] The HARQ-ACK codebook feeds back all PDSCHs corresponding to the HARQ-ACK information;
[0531] The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the earliest or latest PDSCH with the first target time. The first target time includes one of the following: the start time or end time of the PDSCH, or the start time or end time of the first time domain unit in which the PDSCH is located.
[0532] The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the PDSCH with the earliest or latest second target time. The second target time includes one of the following: the start time or end time of the second DCI, the start time or end time of the control resource set CORESET that sends the second DCI, and the start time or end time of the first time domain unit where the CORESET that sends the second DCI is located. The second DCI is used to schedule the PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook.
[0533] Optionally, the first DCI that triggers the terminal to feed back the HARQ-ACK codebook includes at least one of the following:
[0534] The DCI schedules the PDSCH and instructs the terminal to feed back the HARQ-ACK information corresponding to the PDSCH within the first uplink time domain unit;
[0535] The terminal is triggered to feed back a Type-3 HARQ-ACK codebook or an enhanced Type-3 HARQ-ACK codebook via DCI within the first uplink time domain unit;
[0536] The terminal is triggered to perform a HARQ-ACK codebook retransmission DCI within the first uplink time domain unit.
[0537] Optionally, if the HARQ-ACK codebook contains only SPS HARQ-ACK, during the process of determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, at least one of the following is performed for the second SPS PDSCH:
[0538] When using rule one, the following operations are performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity is determined to be an invalid transmission opportunity;
[0539] When using rule two, at least one of the following operations shall be performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type corresponding to the first transmission opportunity is different from the time-domain unit type corresponding to the HARQ-ACK codebook, the first transmission opportunity shall be determined as an invalid transmission opportunity.
[0540] If each transmission opportunity corresponding to the second SPS PDSCH is determined to be an invalid transmission opportunity, the second SPS PDSCH shall be used as the first SPS PDSCH.
[0541] If at least one transmission opportunity corresponding to the second SPS PDSCH is not determined to be an invalid transmission opportunity, the HARQ-ACK information corresponding to the second SPS PDSCH is fed back in the HARQ-ACK codebook.
[0542] Wherein, the second SPS PDSCH is a time-domain feedback offset based on transmission time and application, and it is expected that any SPS PDSCH corresponding to HARQ-ACK information will be fed back within the first uplink time-domain unit;
[0543] The first transmission opportunity is any one of the transmission opportunities corresponding to the second SPS PDSCH;
[0544] The first time-domain relationship includes at least one of the following:
[0545] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0546] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0547] It overlaps with the time domain of the semi-static uplink time domain unit.
[0548] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0549] When the scheduling type of the PDSCH is a single PDSCH scheduling, determine the time domain resource allocation record set corresponding to each first downlink time domain unit associated with the Type-1 HARQ-ACK codebook on each serving cell, determine the transmission opportunity subset corresponding to the first downlink time domain unit based on the time domain resource allocation record set, and generate the corresponding HARQ-ACK bit for each transmission opportunity in the transmission opportunity subset.
[0550] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the first time-domain resource allocation record:
[0551] When using either Rule 1 or Rule 2, perform the following operation: if the second transmission opportunity satisfies the second time-domain relationship, determine the second transmission opportunity as an invalid transmission opportunity;
[0552] If each transmission opportunity corresponding to the first time domain resource allocation record is determined to be an invalid transmission opportunity, the first time domain resource allocation record will be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit.
[0553] Wherein, the first time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the time-domain resource allocation record set determined based on the application's time-domain resource allocation table;
[0554] The second transmission opportunity is any one of the transmission opportunities corresponding to the first time-domain resource allocation record;
[0555] The second time-domain relationship includes at least one of the following:
[0556] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0557] It overlaps with the time domain of the semi-static uplink time domain unit.
[0558] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0559] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, the following operations are performed for each serving cell: Based on the application's time-domain feedback offset set and time-domain resource allocation (TDRA) table, determine the extended time-domain feedback offset set and the complete set of time-domain resource allocation records; determine the time-domain resource allocation record set corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell; determine the transmission opportunity subset corresponding to the first downlink time-domain unit based on the time-domain resource allocation record set; and generate the corresponding HARQ-ACK bits for each transmission opportunity in the transmission opportunity subset.
[0560] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the second time-domain resource allocation record:
[0561] When using Rule 1, the following operation is performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0562] When using Rule 2, at least one of the following operations shall be performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the third transmission opportunity is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, the third transmission opportunity shall be determined as an invalid transmission opportunity.
[0563] If a single transmission opportunity corresponding to the second time-domain resource allocation record is determined to be an invalid transmission opportunity, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0564] If the second time-domain resource allocation record cannot feed back the corresponding HARQ-ACK information in the first uplink time-domain unit based on any row of the TDRA table where the second time-domain resource allocation record is located and any time-domain feedback offset, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0565] Wherein, the second time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the complete set of time-domain resource allocation records;
[0566] The third transmission opportunity is a single transmission opportunity corresponding to the second time-domain resource allocation record;
[0567] The third time-domain relationship includes at least one of the following:
[0568] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0569] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0570] It overlaps with the time domain of the semi-static uplink time domain unit.
[0571] Optionally, when the third time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the third transmission opportunity as an invalid transmission opportunity when the third transmission opportunity satisfies the third time-domain relationship includes at least one of the following:
[0572] Only when the downlink active bandwidth corresponding to the third transmission opportunity is configured or application configuration scheme 1 is applied, the following operation is performed: if the third transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0573] For each time-domain feedback offset in the time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record;
[0574] If the second time-domain resource allocation record is used as the starting time-domain resource allocation record in at least one schedulable row of the TDRA table, the third transmission opportunity is determined to be a valid transmission opportunity.
[0575] If the second time-domain resource allocation record is included in at least one schedulable row of the TDRA table and the second time-domain resource allocation record is not used as the starting time-domain resource allocation record in any of the at least one schedulable rows, the following operations are performed: if the time-domain unit type of the third transmission opportunity is different from the application time-domain unit type of any of the at least one schedulable rows, the third transmission opportunity is determined to be an invalid transmission opportunity; or, if the time-domain unit type of the third transmission opportunity is the same as the application time-domain unit type of at least one of the at least one schedulable rows, the third transmission opportunity is determined to be a valid transmission opportunity.
[0576] If the second time-domain resource allocation record is not included in any schedulable row of the TDRA table, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0577] Wherein, the target row is any row in the TDRA table, and the application time domain unit type of the schedulable row is the time domain unit type of a single transmission opportunity corresponding to the starting time domain resource allocation record of the schedulable row.
[0578] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0579] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, the following operations are performed for each serving cell: only the last time-domain resource allocation record of each row in the application's TDRA table is retained; the set of time-domain resource allocation records corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell is determined; based on the set of time-domain resource allocation records, a subset of transmission opportunities corresponding to the first downlink time-domain unit is determined; and for each transmission opportunity in the subset of transmission opportunities, the corresponding HARQ-ACK bits are generated.
[0580] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the third time-domain resource allocation record:
[0581] When using Rule 1, the following operation is performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity is determined to be an invalid transmission opportunity;
[0582] When using Rule 2, at least one of the following operations shall be performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity shall be determined as an invalid transmission opportunity; if the application time-domain unit type of any schedulable row corresponding to the third time-domain resource allocation record is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, each transmission opportunity corresponding to the third time-domain resource allocation record shall be determined as an invalid transmission opportunity.
[0583] If each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity, the third time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0584] Wherein, the third time-domain resource allocation record is any time-domain resource allocation record in the time-domain resource allocation record set; the initial value of the time-domain resource allocation record set is a set consisting of the last time-domain resource allocation record of each row in the TDRA table;
[0585] The fourth transmission opportunity is any one of the at least one transmission opportunities corresponding to the third time-domain resource allocation record;
[0586] The application time-domain unit type of the schedulable row is the time-domain unit type of a single transmission opportunity corresponding to the initial time-domain resource allocation record of the schedulable row;
[0587] The fourth time-domain relation includes at least one of the following:
[0588] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0589] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0590] It overlaps with the time domain of the semi-static uplink time domain unit.
[0591] Optionally, when the fourth time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the fourth transmission opportunity as an invalid transmission opportunity when the fourth transmission opportunity satisfies the fourth time-domain relationship includes at least one of the following:
[0592] If the downlink active bandwidth portion of the fourth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fourth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fourth transmission opportunity is determined to be an invalid transmission opportunity.
[0593] For each time-domain feedback offset in the application's time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record;
[0594] If none of the rows corresponding to the third time-domain resource allocation record are schedulable rows, then each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity.
[0595] The target row is any row in the TDRA table.
[0596] Optionally, when the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, performing the corresponding second codebook construction operation based on the target information includes at least one of the following:
[0597] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, two HARQ-ACK sub-codebooks are constructed. In the process of constructing the two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate the HARQ-ACK bit corresponding to the scheduled PDSCH.
[0598] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, TB groups or PDSCH groups are divided based on higher-layer configuration parameters, and one or two HARQ-ACK subcodebooks are constructed. In the process of constructing the one or two HARQ-ACK subcodebooks, for the first TB group or the first PDSCH group, the following operations are performed: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, it is determined whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and HARQ-ACK bits corresponding to the first TB group or the first PDSCH group are generated.
[0599] Determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity includes at least one of the following:
[0600] When using Rule 1, the following operation is performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity;
[0601] When using Rule 2, at least one of the following operations shall be performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the fifth transmission opportunity is different from the time-domain unit type of the Type-2 HARQ-ACK codebook, the fifth transmission opportunity shall be determined as an invalid transmission opportunity.
[0602] Wherein, the first TB group is one of the TB groups divided based on the high-level configuration parameters, and the first PDSCH group is one of the PDSCH groups divided based on the high-level configuration parameters.
[0603] The fifth transmission opportunity is a single transmission opportunity corresponding to the scheduled PDSCH;
[0604] The fifth time-domain relation includes at least one of the following:
[0605] The time domain overlap with the sub-band full-duplex SBFD time domain unit and the non-SBFD time domain unit can also be understood as the time domain overlap with both types of time domain units, or the time domain overlap exists between both types.
[0606] The time domain overlap of time domain units that completely correspond to the invalid time domain unit type can also be understood as the time domain overlap of time domain units that only correspond to the invalid time domain unit type, or, the time domain units that occupy or overlap in the time domain all correspond to the invalid time domain unit type;
[0607] It overlaps with the time domain of the semi-static uplink time domain unit.
[0608] Optionally, if the fifth time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, and the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity, including at least one of the following:
[0609] If the downlink active bandwidth portion of the fifth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fifth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fifth transmission opportunity is determined to be an invalid transmission opportunity.
[0610] The starting PDSCH of the target scheduling and the application time-domain unit type of the target scheduling are determined, wherein the target scheduling is a single scheduling based on the multi-PDSCH scheduling TDRA table, the scheduled PDSCH is one of at least one PDSCH corresponding to the target scheduling, and the HARQ-ACK information corresponding to the target scheduling is fed back in the Type-2 HARQ-ACK codebook; the application time-domain unit type of the target scheduling is the time-domain unit type of a single transmission opportunity corresponding to the starting PDSCH of the target scheduling.
[0611] If the scheduled PDSCH is used as the starting PDSCH of the target scheduling, the fifth transmission opportunity is determined to be a valid transmission opportunity.
[0612] If the scheduled PDSCH is not used as the starting PDSCH in the target schedule, the following operations are performed: if the time domain unit type of the fifth transmission opportunity is different from the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be an invalid transmission opportunity; if the time domain unit type of the fifth transmission opportunity is the same as the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be a valid transmission opportunity.
[0613] Optionally, generating the HARQ-ACK bits corresponding to the scheduled PDSCH includes:
[0614] If the fifth transmission opportunity is determined to be an invalid transmission opportunity, the HARQ-ACK bit corresponding to the scheduled PDSCH is set to NACK.
[0615] Optionally, generating the HARQ-ACK bits corresponding to the first TB group or the first PDSCH group includes:
[0616] In the case that the first TB group or the first PDSCH group corresponds to at least one valid PDSCH, the terminal assumes that any invalid PDSCH corresponding to the first TB group or the first PDSCH group is correctly received.
[0617] If each scheduled PDSCH corresponding to the first TB group or the first PDSCH group is determined to be an invalid PDSCH, the HARQ-ACK bit corresponding to the first TB group or the first PDSCH group is set to NACK.
[0618] Wherein, the valid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be a valid transmission opportunity, and the invalid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be an invalid transmission opportunity.
[0619] The shared channel transmission and HARQ-ACK feedback device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG2 and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0620] Figure 5 is a second schematic diagram of the shared channel transmission and HARQ-ACK feedback device provided in an embodiment of this application. Referring to Figure 5, when the shared channel transmission and HARQ-ACK feedback device is a network-side device or a component in a network-side device, the shared channel transmission and HARQ-ACK feedback device 500 includes a second processing module 501, used to perform a second operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel. The second operation includes at least one of the following:
[0621] Determine the physical shared channel that needs to be transmitted;
[0622] The receiving terminal sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook within the first uplink time domain unit. This HARQ-ACK codebook is determined by the terminal using one of the following rules:
[0623] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0624] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0625] Optionally, a target transmission opportunity is determined to be an invalid transmission opportunity if it satisfies at least one of the following time-domain relationships:
[0626] Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units;
[0627] The time domains of time domains completely overlap with those of invalid time domain cell types;
[0628] When the target transmission opportunity corresponds to a physical uplink shared channel (PUSCH), it overlaps with the time domain of the semi-static downlink time domain unit or the synchronization signal block time domain unit.
[0629] When the target transmission opportunity corresponds to one PDSCH, it overlaps with the time domain of the semi-static uplink time domain unit.
[0630] The target transmission opportunity is a single transmission opportunity among the transmission opportunities corresponding to the target physical shared channel.
[0631] Optionally, the determination of the physical shared channel to be transmitted satisfies at least one of the following:
[0632] When scheduling at least one physical shared channel transmission opportunity through a single downlink control information (DCI), it is guaranteed that each physical shared channel transmission opportunity scheduled by the DCI will not be determined as an invalid transmission opportunity.
[0633] When multiple semi-persistent scheduling (SPS) PDSCHs are configured for the terminal in a single first downlink time domain unit on a serving cell, the network-side device determines the remaining SPS PDSCHs, without considering SPS PDSCHs whose corresponding transmission opportunities are determined to be invalid transmission opportunities.
[0634] Optionally, the HARQ-ACK codebook is determined by the terminal by performing at least one of the following:
[0635] Determine the time-domain unit type corresponding to the HARQ-ACK codebook;
[0636] When the HARQ-ACK codebook contains only SPS HARQ-ACK, in the process of determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, the first SPS PDSCH is excluded, or the SPS HARQ-ACK bit corresponding to the first SPS PDSCH is set to NACK, and the first SPS PDSCH is the SPS PDSCH whose corresponding transmission opportunity is determined to be an invalid transmission opportunity.
[0637] If the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information;
[0638] If the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, then according to the target information, the corresponding second codebook construction operation is performed;
[0639] The target information includes at least one of the following:
[0640] PDSCH scheduling type;
[0641] The HARQ-ACK codebook needs to provide feedback on whether the transmission opportunity corresponding to the PDSCH with the corresponding HARQ-ACK information has been determined as an invalid transmission opportunity.
[0642] Optionally, the time-domain unit type of the HARQ-ACK codebook satisfies one of the following:
[0643] The time-domain cell type of the HARQ-ACK codebook is the time-domain cell type of the target PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook;
[0644] The time-domain unit type of the HARQ-ACK codebook is indicated by the first DCI that triggers the terminal to feed back the HARQ-ACK codebook;
[0645] The time-domain unit type of the HARQ-ACK codebook is the time-domain unit type of the uplink physical channel carrying the HARQ-ACK codebook.
[0646] Optionally, the target PDSCH includes at least one of the following:
[0647] The HARQ-ACK codebook feeds back all PDSCHs corresponding to the HARQ-ACK information;
[0648] The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the earliest or latest PDSCH with the first target time. The first target time includes one of the following: the start time or end time of the PDSCH, or the start time or end time of the first time domain unit in which the PDSCH is located.
[0649] The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the PDSCH with the earliest or latest second target time. The second target time includes one of the following: the start time or end time of the second DCI, the start time or end time of the control resource set CORESET that sends the second DCI, and the start time or end time of the first time domain unit where the CORESET that sends the second DCI is located. The second DCI is used to schedule the PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook.
[0650] Optionally, the first DCI that triggers the terminal to feed back the HARQ-ACK codebook includes at least one of the following:
[0651] The DCI schedules the PDSCH and instructs the terminal to feed back the HARQ-ACK information corresponding to the PDSCH within the first uplink time domain unit;
[0652] The terminal is triggered to feed back a Type-3 HARQ-ACK codebook or an enhanced Type-3 HARQ-ACK codebook via DCI within the first uplink time domain unit;
[0653] The terminal is triggered to perform a HARQ-ACK codebook retransmission DCI within the first uplink time domain unit.
[0654] Optionally, if the HARQ-ACK codebook contains only SPS HARQ-ACK, during the process of determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, at least one of the following is performed for the second SPS PDSCH:
[0655] When using rule one, the following operations are performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity is determined to be an invalid transmission opportunity;
[0656] When using rule two, at least one of the following operations shall be performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type corresponding to the first transmission opportunity is different from the time-domain unit type corresponding to the HARQ-ACK codebook, the first transmission opportunity shall be determined as an invalid transmission opportunity.
[0657] If each transmission opportunity corresponding to the second SPS PDSCH is determined to be an invalid transmission opportunity, the second SPS PDSCH shall be used as the first SPS PDSCH.
[0658] If at least one transmission opportunity corresponding to the second SPS PDSCH is not determined to be an invalid transmission opportunity, the HARQ-ACK information corresponding to the second SPS PDSCH is fed back in the HARQ-ACK codebook.
[0659] Wherein, the second SPS PDSCH is a time-domain feedback offset based on transmission time and application, and it is expected that any SPS PDSCH corresponding to HARQ-ACK information will be fed back within the first uplink time-domain unit;
[0660] The first transmission opportunity is any one of the transmission opportunities corresponding to the second SPS PDSCH;
[0661] The first time-domain relationship includes at least one of the following:
[0662] Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units;
[0663] The time domains of time domains completely overlap with those of invalid time domain cell types;
[0664] It overlaps with the time domain of the semi-static uplink time domain unit.
[0665] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0666] When the scheduling type of the PDSCH is a single PDSCH scheduling, determine the time domain resource allocation record set corresponding to each first downlink time domain unit associated with the Type-1 HARQ-ACK codebook on each serving cell, determine the transmission opportunity subset corresponding to the first downlink time domain unit based on the time domain resource allocation record set, and generate the corresponding HARQ-ACK bit for each transmission opportunity in the transmission opportunity subset.
[0667] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the first time-domain resource allocation record:
[0668] When using either Rule 1 or Rule 2, perform the following operation: if the second transmission opportunity satisfies the second time-domain relationship, determine the second transmission opportunity as an invalid transmission opportunity;
[0669] If each transmission opportunity corresponding to the first time domain resource allocation record is determined to be an invalid transmission opportunity, the first time domain resource allocation record will be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit.
[0670] Wherein, the first time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the time-domain resource allocation record set determined based on the application's time-domain resource allocation table;
[0671] The second transmission opportunity is any one of the transmission opportunities corresponding to the first time-domain resource allocation record;
[0672] The second time-domain relationship includes at least one of the following:
[0673] Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units;
[0674] It overlaps with the time domain of the semi-static uplink time domain unit.
[0675] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0676] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, the following operations are performed for each serving cell: Based on the application's time-domain feedback offset set and time-domain resource allocation (TDRA) table, determine the extended time-domain feedback offset set and the complete set of time-domain resource allocation records; determine the time-domain resource allocation record set corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell; determine the transmission opportunity subset corresponding to the first downlink time-domain unit based on the time-domain resource allocation record set; and generate the corresponding HARQ-ACK bits for each transmission opportunity in the transmission opportunity subset.
[0677] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the second time-domain resource allocation record:
[0678] When using Rule 1, the following operation is performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0679] When using Rule 2, at least one of the following operations shall be performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the third transmission opportunity is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, the third transmission opportunity shall be determined as an invalid transmission opportunity.
[0680] If a single transmission opportunity corresponding to the second time-domain resource allocation record is determined to be an invalid transmission opportunity, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0681] If the second time-domain resource allocation record cannot feed back the corresponding HARQ-ACK information in the first uplink time-domain unit based on any row of the TDRA table where the second time-domain resource allocation record is located and any time-domain feedback offset, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0682] Wherein, the second time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the complete set of time-domain resource allocation records;
[0683] The third transmission opportunity is a single transmission opportunity corresponding to the second time-domain resource allocation record;
[0684] The third time-domain relationship includes at least one of the following:
[0685] Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units;
[0686] The time domains of time domains completely overlap with those of invalid time domain cell types;
[0687] It overlaps with the time domain of the semi-static uplink time domain unit.
[0688] Optionally, when the third time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the third transmission opportunity as an invalid transmission opportunity when the third transmission opportunity satisfies the third time-domain relationship includes at least one of the following:
[0689] Only when the downlink active bandwidth corresponding to the third transmission opportunity is configured or application configuration scheme 1 is applied, the following operation is performed: if the third transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0690] For each time-domain feedback offset in the time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record;
[0691] If the second time-domain resource allocation record is used as the starting time-domain resource allocation record in at least one schedulable row of the TDRA table, the third transmission opportunity is determined to be a valid transmission opportunity.
[0692] If the second time-domain resource allocation record is included in at least one schedulable row of the TDRA table and the second time-domain resource allocation record is not used as the starting time-domain resource allocation record in any of the at least one schedulable rows, the following operations are performed: if the time-domain unit type of the third transmission opportunity is different from the application time-domain unit type of any of the at least one schedulable rows, the third transmission opportunity is determined to be an invalid transmission opportunity; or, if the time-domain unit type of the third transmission opportunity is the same as the application time-domain unit type of at least one of the at least one schedulable rows, the third transmission opportunity is determined to be a valid transmission opportunity.
[0693] If the second time-domain resource allocation record is not included in any schedulable row of the TDRA table, the third transmission opportunity is determined to be an invalid transmission opportunity;
[0694] Wherein, the target row is any row in the TDRA table, and the application time domain unit type of the schedulable row is the time domain unit type of a single transmission opportunity corresponding to the starting time domain resource allocation record of the schedulable row.
[0695] Optionally, when the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, performing the corresponding first codebook construction operation based on the target information includes:
[0696] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, the following operations are performed for each serving cell: only the last time-domain resource allocation record of each row in the application's TDRA table is retained; the set of time-domain resource allocation records corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell is determined; based on the set of time-domain resource allocation records, a subset of transmission opportunities corresponding to the first downlink time-domain unit is determined; and for each transmission opportunity in the subset of transmission opportunities, the corresponding HARQ-ACK bits are generated.
[0697] In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the third time-domain resource allocation record:
[0698] When using Rule 1, the following operation is performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity is determined to be an invalid transmission opportunity;
[0699] When using Rule 2, at least one of the following operations shall be performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity shall be determined as an invalid transmission opportunity; if the application time-domain unit type of any schedulable row corresponding to the third time-domain resource allocation record is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, each transmission opportunity corresponding to the third time-domain resource allocation record shall be determined as an invalid transmission opportunity.
[0700] If each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity, the third time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit.
[0701] Wherein, the third time-domain resource allocation record is any time-domain resource allocation record in the time-domain resource allocation record set; the initial value of the time-domain resource allocation record set is a set consisting of the last time-domain resource allocation record of each row in the TDRA table;
[0702] The fourth transmission opportunity is any one of the at least one transmission opportunities corresponding to the third time-domain resource allocation record;
[0703] The application time-domain unit type of the schedulable row is the time-domain unit type of a single transmission opportunity corresponding to the initial time-domain resource allocation record of the schedulable row;
[0704] The fourth time-domain relation includes at least one of the following:
[0705] Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units;
[0706] The time domains of time domains completely overlap with those of invalid time domain cell types;
[0707] It overlaps with the time domain of the semi-static uplink time domain unit.
[0708] Optionally, when the fourth time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, determining the fourth transmission opportunity as an invalid transmission opportunity when the fourth transmission opportunity satisfies the fourth time-domain relationship includes at least one of the following:
[0709] If the downlink active bandwidth portion of the fourth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fourth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fourth transmission opportunity is determined to be an invalid transmission opportunity.
[0710] For each time-domain feedback offset in the application's time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record;
[0711] If none of the rows corresponding to the third time-domain resource allocation record are schedulable rows, then each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity.
[0712] The target row is any row in the TDRA table.
[0713] Optionally, when the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, performing the corresponding second codebook construction operation based on the target information includes at least one of the following:
[0714] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, two HARQ-ACK sub-codebooks are constructed. In the process of constructing the two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate the HARQ-ACK bit corresponding to the scheduled PDSCH.
[0715] When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, TB groups or PDSCH groups are divided based on higher-layer configuration parameters, and one or two HARQ-ACK subcodebooks are constructed. In the process of constructing the one or two HARQ-ACK subcodebooks, for the first TB group or the first PDSCH group, the following operations are performed: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, it is determined whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and HARQ-ACK bits corresponding to the first TB group or the first PDSCH group are generated.
[0716] Determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity includes at least one of the following:
[0717] When using Rule 1, the following operation is performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity;
[0718] When using Rule 2, at least one of the following operations shall be performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the fifth transmission opportunity is different from the time-domain unit type of the Type-2 HARQ-ACK codebook, the fifth transmission opportunity shall be determined as an invalid transmission opportunity.
[0719] Wherein, the first TB group is one of the TB groups divided based on the high-level configuration parameters, and the first PDSCH group is one of the PDSCH groups divided based on the high-level configuration parameters.
[0720] The fifth transmission opportunity is a single transmission opportunity corresponding to the scheduled PDSCH;
[0721] The fifth time-domain relation includes at least one of the following:
[0722] Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units;
[0723] The time domains of time domains completely overlap with those of invalid time domain cell types;
[0724] It overlaps with the time domain of the semi-static uplink time domain unit.
[0725] Optionally, if the fifth time-domain relationship includes time-domain overlap of time-domain units completely corresponding to invalid time-domain unit types, and the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity, including at least one of the following:
[0726] If the downlink active bandwidth portion of the fifth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fifth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fifth transmission opportunity is determined to be an invalid transmission opportunity.
[0727] The starting PDSCH of the target scheduling and the application time-domain unit type of the target scheduling are determined, wherein the target scheduling is a single scheduling based on the multi-PDSCH scheduling TDRA table, the scheduled PDSCH is one of at least one PDSCH corresponding to the target scheduling, and the HARQ-ACK information corresponding to the target scheduling is fed back in the Type-2 HARQ-ACK codebook; the application time-domain unit type of the target scheduling is the time-domain unit type of a single transmission opportunity corresponding to the starting PDSCH of the target scheduling.
[0728] If the scheduled PDSCH is used as the starting PDSCH of the target scheduling, the fifth transmission opportunity is determined to be a valid transmission opportunity.
[0729] If the scheduled PDSCH is not used as the starting PDSCH in the target schedule, the following operations are performed: if the time domain unit type of the fifth transmission opportunity is different from the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be an invalid transmission opportunity; if the time domain unit type of the fifth transmission opportunity is the same as the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be a valid transmission opportunity.
[0730] Optionally, generating the HARQ-ACK bits corresponding to the scheduled PDSCH includes:
[0731] If the fifth transmission opportunity is determined to be an invalid transmission opportunity, the HARQ-ACK bit corresponding to the scheduled PDSCH is set to NACK.
[0732] Optionally, generating the HARQ-ACK bits corresponding to the first TB group or the first PDSCH group includes:
[0733] In the case that the first TB group or the first PDSCH group corresponds to at least one valid PDSCH, the terminal assumes that any invalid PDSCH corresponding to the first TB group or the first PDSCH group is correctly received.
[0734] If each scheduled PDSCH corresponding to the first TB group or the first PDSCH group is determined to be an invalid PDSCH, the HARQ-ACK bit corresponding to the first TB group or the first PDSCH group is set to NACK.
[0735] Wherein, the valid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be a valid transmission opportunity, and the invalid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be an invalid transmission opportunity.
[0736] The shared channel transmission and HARQ-ACK feedback device provided in this application embodiment can implement the various processes implemented in the method embodiment of FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0737] Figure 6 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 6, this application embodiment also provides a communication device 600, including a processor 601 and a memory 602. The memory 602 stores a program or instructions that can run on the processor 601. For example, when the communication device 600 is a terminal, when the program or instructions are executed by the processor 601, they implement the various steps of the above-described shared channel transmission and HARQ-ACK feedback method embodiments and achieve the same technical effect. When the communication device 600 is a network-side device, when the program or instructions are executed by the processor 601, they implement the various steps of the above-described shared channel transmission and HARQ-ACK feedback method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here.
[0738] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG2. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the shared channel transmission and HARQ-ACK feedback device shown in FIG4. Specifically, FIG7 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.
[0739] The terminal 700 includes, but is not limited to, at least some of the following components: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.
[0740] Those skilled in the art will understand that the terminal 700 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. The terminal structure shown in Figure 7 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.
[0741] It should be understood that, in this embodiment, the input unit 704 may include a graphics processor 7041 and a microphone 7042. The graphics processor 7041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.
[0742] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 701 can transmit it to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network-side device. Typically, the radio frequency unit 701 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.
[0743] The memory 709 can be used to store software programs or instructions, as well as various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 709 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.
[0744] The processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into the processor 710.
[0745] Wherein, the processor 710 is configured to, when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, perform a first operation, the first operation including at least one of the following:
[0746] Determine the physical shared channel that needs to be transmitted;
[0747] When the target physical shared channel is a physical downlink shared channel (PDSCH), one of the following rules is used to determine the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit:
[0748] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0749] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0750] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the aforementioned terminal-side shared channel transmission and HARQ-ACK feedback method embodiments, and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.
[0751] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiment shown in FIG3. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.
[0752] Specifically, this application embodiment also provides a network-side device, which can be the shared channel transmission and HARQ-ACK feedback device shown in FIG5. FIG8 is a schematic diagram of the hardware structure of a network-side device implementing an embodiment of this application. As shown in FIG8, the network-side device 800 includes: an antenna 801, a radio frequency device 802, a baseband device 803, a processor 804, and a memory 805. The antenna 801 is connected to the radio frequency device 802. In the uplink direction, the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes the information to be transmitted and sends it to the radio frequency device 802. The radio frequency device 802 processes the received information and transmits it through the antenna 801.
[0753] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 803, which includes a baseband processor.
[0754] The baseband device 803 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG8. One of the chips is, for example, a baseband processor, which is connected to the memory 805 via a bus interface to call the program or instructions in the memory 805 to execute the network-side device operation shown in the above method embodiment.
[0755] The network-side device may also include a network interface 806, such as a Common Public Radio Interface (CPRI).
[0756] Wherein, the processor 804 is configured to perform a second operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the second operation including at least one of the following:
[0757] Determine the physical shared channel that needs to be transmitted;
[0758] The network-side device receives the HARQ-ACK codebook from the terminal within the first uplink time domain unit. The HARQ-ACK codebook is determined by the terminal using one of the following rules:
[0759] Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook;
[0760] Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
[0761] In addition, the network-side device 800 in this application embodiment also includes: a program or instructions stored in a memory 805 and executable on a processor 804. The processor 804 calls the program or instructions in the memory 805 to execute the methods executed by each module shown in FIG5 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.
[0762] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described shared channel transmission and HARQ-ACK feedback method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.
[0763] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.
[0764] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled. The processor is used to run programs or instructions to implement the various processes of the above-described shared channel transmission and HARQ-ACK feedback method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0765] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.
[0766] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described shared channel transmission and HARQ-ACK feedback method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.
[0767] This application also provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to perform the steps of the shared channel transmission and HARQ-ACK feedback method as described above, and the network-side device can be used to perform the steps of the shared channel transmission and HARQ-ACK feedback method as described above.
[0768] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
[0769] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.
[0770] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.
Claims
1. A shared channel transmission and HARQ-ACK feedback method, comprising: If there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the terminal performs a first operation, the first operation including at least one of the following: Determine the physical shared channel that needs to be transmitted; When the target physical shared channel is a physical downlink shared channel (PDSCH), one of the following rules is used to determine the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit: Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook; Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
2. The method according to claim 1, wherein, Also includes: The target transmission opportunity is determined to be the invalid transmission opportunity if it satisfies at least one of the following time-domain relationships: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; When the target transmission opportunity corresponds to a physical uplink shared channel (PUSCH), it overlaps with the time domain of the semi-static downlink time domain unit or the synchronization signal block time domain unit. When the target transmission opportunity corresponds to one PDSCH, it overlaps with the time domain of the semi-static uplink time domain unit. The target transmission opportunity is a single transmission opportunity among the transmission opportunities corresponding to the target physical shared channel.
3. The method according to claim 1 or 2, wherein, The determination of the physical shared channel to be transmitted includes at least one of the following: When a single downlink control information (DCI) schedules at least one physical shared channel transmission opportunity, the terminal does not expect each physical shared channel transmission opportunity scheduled by the DCI to be determined as an invalid transmission opportunity. When the terminal is configured with multiple semi-persistent scheduling (SPS) PDSCHs in a single first downlink time domain unit on a serving cell, the terminal determines the remaining SPS PDSCHs, regardless of the SPS PDSCHs whose corresponding transmission opportunities are determined to be invalid transmission opportunities.
4. The method according to any one of claims 1-3, wherein, The determination of the HARQ-ACK codebook includes at least one of the following: Determine the time-domain unit type corresponding to the HARQ-ACK codebook; When the HARQ-ACK codebook contains only SPS HARQ-ACK, the terminal, in determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, excludes the first SPS PDSCH, or sets the SPS HARQ-ACK bit corresponding to the first SPS PDSCH to NACK. The first SPS PDSCH is the SPS PDSCH whose corresponding transmission opportunity is determined to be an invalid transmission opportunity. If the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information; If the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, then according to the target information, the corresponding second codebook construction operation is performed; The target information includes at least one of the following: PDSCH scheduling type; The HARQ-ACK codebook needs to provide feedback on whether the transmission opportunity corresponding to the PDSCH with the corresponding HARQ-ACK information has been determined as an invalid transmission opportunity.
5. The method according to claim 4, wherein, The time-domain unit type of the HARQ-ACK codebook satisfies one of the following: The time-domain cell type of the HARQ-ACK codebook is the time-domain cell type of the target PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook; The time-domain unit type of the HARQ-ACK codebook is indicated by the first DCI that triggers the terminal to feed back the HARQ-ACK codebook; The time-domain unit type of the HARQ-ACK codebook is the time-domain unit type of the uplink physical channel carrying the HARQ-ACK codebook.
6. The method according to claim 5, wherein, The target PDSCH includes at least one of the following: The HARQ-ACK codebook feeds back all PDSCHs corresponding to the HARQ-ACK information; The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the earliest or latest PDSCH with the first target time. The first target time includes one of the following: the start time or end time of the PDSCH, or the start time or end time of the first time domain unit in which the PDSCH is located. The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the PDSCH with the earliest or latest second target time. The second target time includes one of the following: the start time or end time of the second DCI, the start time or end time of the control resource set CORESET that sends the second DCI, and the start time or end time of the first time domain unit where the CORESET that sends the second DCI is located. The second DCI is used to schedule the PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook.
7. The method according to claim 5, wherein, The first DCI that triggers the terminal to feed back the HARQ-ACK codebook includes at least one of the following: The DCI schedules the PDSCH and instructs the terminal to feed back the HARQ-ACK information corresponding to the PDSCH within the first uplink time domain unit; The terminal is triggered to feed back a Type-3 HARQ-ACK codebook or an enhanced Type-3 HARQ-ACK codebook via DCI within the first uplink time domain unit; The terminal is triggered to perform a HARQ-ACK codebook retransmission DCI within the first uplink time domain unit.
8. The method according to any one of claims 4-7, wherein, Also includes: When the HARQ-ACK codebook contains only SPS HARQ-ACK, the terminal, in determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, performs at least one of the following for the second SPS PDSCH: When using rule one, the following operations are performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity is determined to be an invalid transmission opportunity; When using rule two, at least one of the following operations shall be performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type corresponding to the first transmission opportunity is different from the time-domain unit type corresponding to the HARQ-ACK codebook, the first transmission opportunity shall be determined as an invalid transmission opportunity. If each transmission opportunity corresponding to the second SPS PDSCH is determined to be an invalid transmission opportunity, the second SPS PDSCH shall be used as the first SPS PDSCH. If at least one transmission opportunity corresponding to the second SPS PDSCH is not determined to be an invalid transmission opportunity, the HARQ-ACK information corresponding to the second SPS PDSCH is fed back in the HARQ-ACK codebook. Wherein, the second SPS PDSCH is a time-domain feedback offset based on transmission time and application, and it is expected that any SPS PDSCH corresponding to HARQ-ACK information will be fed back within the first uplink time-domain unit; The first transmission opportunity is any one of the transmission opportunities corresponding to the second SPS PDSCH; The first time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
9. The method according to any one of claims 4-7, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the scheduling type of the PDSCH is a single PDSCH scheduling, determine the time domain resource allocation record set corresponding to each first downlink time domain unit associated with the Type-1 HARQ-ACK codebook on each serving cell, determine the transmission opportunity subset corresponding to the first downlink time domain unit based on the time domain resource allocation record set, and generate the corresponding HARQ-ACK bit for each transmission opportunity in the transmission opportunity subset. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the first time-domain resource allocation record: When using either Rule 1 or Rule 2, perform the following operation: if the second transmission opportunity satisfies the second time-domain relationship, determine the second transmission opportunity as an invalid transmission opportunity; If each transmission opportunity corresponding to the first time domain resource allocation record is determined to be an invalid transmission opportunity, the first time domain resource allocation record will be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit. Wherein, the first time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the time-domain resource allocation record set determined based on the application's time-domain resource allocation table; The second transmission opportunity is any one of the transmission opportunities corresponding to the first time-domain resource allocation record; The second time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; It overlaps with the time domain of the semi-static uplink time domain unit.
10. The method according to any one of claims 4-7, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, the following operations are performed for each serving cell: Based on the application's time-domain feedback offset set and time-domain resource allocation (TDRA) table, determine the extended time-domain feedback offset set and the complete set of time-domain resource allocation records; determine the time-domain resource allocation record set corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell; determine the transmission opportunity subset corresponding to the first downlink time-domain unit based on the time-domain resource allocation record set; and generate the corresponding HARQ-ACK bits for each transmission opportunity in the transmission opportunity subset. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the second time-domain resource allocation record: When using Rule 1, the following operation is performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the third transmission opportunity is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, the third transmission opportunity shall be determined as an invalid transmission opportunity. If a single transmission opportunity corresponding to the second time-domain resource allocation record is determined to be an invalid transmission opportunity, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. If the second time-domain resource allocation record cannot feed back the corresponding HARQ-ACK information in the first uplink time-domain unit based on any row of the TDRA table where the second time-domain resource allocation record is located and any time-domain feedback offset, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. Wherein, the second time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the complete set of time-domain resource allocation records; The third transmission opportunity is a single transmission opportunity corresponding to the second time-domain resource allocation record; The third time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
11. The method according to claim 10, wherein, When the third time-domain relationship includes time-domain overlap of time-domain units that completely correspond to the invalid time-domain unit type, determining that the third transmission opportunity is an invalid transmission opportunity when the third transmission opportunity satisfies the third time-domain relationship includes at least one of the following: Only when the downlink active bandwidth corresponding to the third transmission opportunity is configured or application configuration scheme 1 is applied, the following operation is performed: if the third transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the third transmission opportunity is determined to be an invalid transmission opportunity; For each time-domain feedback offset in the time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record; If the second time-domain resource allocation record is used as the starting time-domain resource allocation record in at least one schedulable row of the TDRA table, the third transmission opportunity is determined to be a valid transmission opportunity. If the second time-domain resource allocation record is included in at least one schedulable row of the TDRA table and the second time-domain resource allocation record is not used as the starting time-domain resource allocation record in any of the at least one schedulable rows, the following operations are performed: if the time-domain unit type of the third transmission opportunity is different from the application time-domain unit type of any of the at least one schedulable rows, the third transmission opportunity is determined to be an invalid transmission opportunity; or, if the time-domain unit type of the third transmission opportunity is the same as the application time-domain unit type of at least one of the at least one schedulable rows, the third transmission opportunity is determined to be a valid transmission opportunity. If the second time-domain resource allocation record is not included in any schedulable row of the TDRA table, the third transmission opportunity is determined to be an invalid transmission opportunity; Wherein, the target row is any row in the TDRA table, and the application time domain unit type of the schedulable row is the time domain unit type of a single transmission opportunity corresponding to the starting time domain resource allocation record of the schedulable row.
12. The method according to any one of claims 4-7, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, the following operations are performed for each serving cell: only the last time-domain resource allocation record of each row in the application's TDRA table is retained; the set of time-domain resource allocation records corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell is determined; based on the set of time-domain resource allocation records, a subset of transmission opportunities corresponding to the first downlink time-domain unit is determined; and for each transmission opportunity in the subset of transmission opportunities, the corresponding HARQ-ACK bits are generated. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the third time-domain resource allocation record: When using Rule 1, the following operation is performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity shall be determined as an invalid transmission opportunity; if the application time-domain unit type of any schedulable row corresponding to the third time-domain resource allocation record is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, each transmission opportunity corresponding to the third time-domain resource allocation record shall be determined as an invalid transmission opportunity. If each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity, the third time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. Wherein, the third time-domain resource allocation record is any time-domain resource allocation record in the time-domain resource allocation record set; the initial value of the time-domain resource allocation record set is a set consisting of the last time-domain resource allocation record of each row in the TDRA table; The fourth transmission opportunity is any one of the at least one transmission opportunities corresponding to the third time-domain resource allocation record; The application time-domain unit type of the schedulable row is the time-domain unit type of a single transmission opportunity corresponding to the initial time-domain resource allocation record of the schedulable row; The fourth time-domain relation includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
13. The method according to claim 12, wherein, When the fourth time-domain relationship includes time-domain overlap of time-domain units that completely correspond to invalid time-domain unit types, determining that the fourth transmission opportunity is an invalid transmission opportunity when the fourth transmission opportunity satisfies the fourth time-domain relationship includes at least one of the following: If the downlink active bandwidth portion of the fourth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fourth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fourth transmission opportunity is determined to be an invalid transmission opportunity. For each time-domain feedback offset in the application's time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record; If none of the rows corresponding to the third time-domain resource allocation record are schedulable rows, then each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity. The target row is any row in the TDRA table.
14. The method according to any one of claims 4-7, wherein, When the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, the corresponding second codebook construction operation is performed according to the target information, including at least one of the following: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, two HARQ-ACK sub-codebooks are constructed. In the process of constructing the two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate the HARQ-ACK bit corresponding to the scheduled PDSCH. When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, TB groups or PDSCH groups are divided based on higher-layer configuration parameters, and one or two HARQ-ACK subcodebooks are constructed. In the process of constructing the one or two HARQ-ACK subcodebooks, for the first TB group or the first PDSCH group, the following operations are performed: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, it is determined whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and HARQ-ACK bits corresponding to the first TB group or the first PDSCH group are generated. Determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity includes at least one of the following: When using Rule 1, the following operation is performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the fifth transmission opportunity is different from the time-domain unit type of the Type-2 HARQ-ACK codebook, the fifth transmission opportunity shall be determined as an invalid transmission opportunity. Wherein, the first TB group is one of the TB groups divided based on the high-level configuration parameters, and the first PDSCH group is one of the PDSCH groups divided based on the high-level configuration parameters. The fifth transmission opportunity is a single transmission opportunity corresponding to the scheduled PDSCH; The fifth time-domain relation includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
15. The method according to claim 14, wherein, When the fifth time-domain relationship includes time-domain overlap of time-domain units that completely correspond to the invalid time-domain unit type, and the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity, including at least one of the following: If the downlink active bandwidth portion of the fifth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fifth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fifth transmission opportunity is determined to be an invalid transmission opportunity. Determine the starting PDSCH of the target schedule and the application time-domain unit type of the target schedule, wherein the target schedule is a single schedule based on the multi-PDSCH scheduling TDRA table, the scheduled PDSCH is one of the at least one PDSCH corresponding to the target schedule, and the HARQ-ACK information corresponding to the target schedule is fed back in the Type-2 HARQ-ACK codebook. The application time-domain unit type of the target scheduling is the time-domain unit type of a single transmission opportunity corresponding to the starting PDSCH of the target scheduling; If the scheduled PDSCH is used as the starting PDSCH of the target scheduling, the fifth transmission opportunity is determined to be a valid transmission opportunity. If the scheduled PDSCH is not used as the starting PDSCH in the target schedule, the following operations are performed: if the time domain unit type of the fifth transmission opportunity is different from the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be an invalid transmission opportunity; if the time domain unit type of the fifth transmission opportunity is the same as the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be a valid transmission opportunity.
16. The method according to claim 14 or 15, wherein, The generation of the HARQ-ACK bits corresponding to the scheduled PDSCH includes: If the fifth transmission opportunity is determined to be an invalid transmission opportunity, the HARQ-ACK bit corresponding to the scheduled PDSCH is set to NACK.
17. The method according to claim 14 or 15, wherein, The generation of HARQ-ACK bits corresponding to the first TB group or the first PDSCH group includes: In the case that the first TB group or the first PDSCH group corresponds to at least one valid PDSCH, the terminal assumes that any invalid PDSCH corresponding to the first TB group or the first PDSCH group is correctly received. If each scheduled PDSCH corresponding to the first TB group or the first PDSCH group is determined to be an invalid PDSCH, the HARQ-ACK bit corresponding to the first TB group or the first PDSCH group is set to NACK. Wherein, the valid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be a valid transmission opportunity, and the invalid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be an invalid transmission opportunity.
18. A shared channel transmission and HARQ-ACK feedback method, comprising: If there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the network-side device performs a second operation, which includes at least one of the following: Determine the physical shared channel that needs to be transmitted; The network-side device receives the HARQ-ACK codebook from the terminal within the first uplink time domain unit. The HARQ-ACK codebook is determined by the terminal using one of the following rules: Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook; Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
19. The method according to claim 18, wherein, The target transmission opportunity is determined to be the invalid transmission opportunity if it satisfies at least one of the following time-domain relationships: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; When the target transmission opportunity corresponds to a physical uplink shared channel (PUSCH), it overlaps with the time domain of the semi-static downlink time domain unit or the synchronization signal block time domain unit. When the target transmission opportunity corresponds to one PDSCH, it overlaps with the time domain of the semi-static uplink time domain unit. The target transmission opportunity is a single transmission opportunity among the transmission opportunities corresponding to the target physical shared channel.
20. The method according to claim 18, wherein, The determination of the physical shared channel to be transmitted satisfies at least one of the following: When scheduling at least one physical shared channel transmission opportunity through a single downlink control information (DCI), it is guaranteed that each physical shared channel transmission opportunity scheduled by the DCI will not be determined as an invalid transmission opportunity. When multiple semi-persistent scheduling (SPS) PDSCHs are configured for the terminal in a single first downlink time domain unit on a serving cell, the network-side device determines the remaining SPS PDSCHs, without considering SPS PDSCHs whose corresponding transmission opportunities are determined to be invalid transmission opportunities.
21. The method according to any one of claims 18-20, wherein, The HARQ-ACK codebook is determined by the terminal by performing at least one of the following: Determine the time-domain unit type corresponding to the HARQ-ACK codebook; When the HARQ-ACK codebook contains only SPS HARQ-ACK, the terminal, in determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, excludes the first SPS PDSCH, or sets the SPS HARQ-ACK bit corresponding to the first SPS PDSCH to NACK. The first SPS PDSCH is the SPS PDSCH whose corresponding transmission opportunity is determined to be an invalid transmission opportunity. If the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information; If the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, then according to the target information, the corresponding second codebook construction operation is performed; The target information includes at least one of the following: PDSCH scheduling type; The HARQ-ACK codebook needs to provide feedback on whether the transmission opportunity corresponding to the PDSCH with the corresponding HARQ-ACK information has been determined as an invalid transmission opportunity.
22. The method according to claim 21, wherein, The time-domain unit type of the HARQ-ACK codebook satisfies one of the following: The time-domain cell type of the HARQ-ACK codebook is the time-domain cell type of the target PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook; The time-domain unit type of the HARQ-ACK codebook is indicated by the first DCI that triggers the terminal to feed back the HARQ-ACK codebook; The time-domain unit type of the HARQ-ACK codebook is the time-domain unit type of the uplink physical channel carrying the HARQ-ACK codebook.
23. The method according to claim 22, wherein, The target PDSCH includes at least one of the following: The HARQ-ACK codebook feeds back all PDSCHs corresponding to the HARQ-ACK information; The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the earliest or latest PDSCH with the first target time. The first target time includes one of the following: the start time or end time of the PDSCH, or the start time or end time of the first time domain unit in which the PDSCH is located. The PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook is the PDSCH with the earliest or latest second target time. The second target time includes one of the following: the start time or end time of the second DCI, the start time or end time of the control resource set CORESET that sends the second DCI, and the start time or end time of the first time domain unit where the CORESET that sends the second DCI is located. The second DCI is used to schedule the PDSCH that feeds back the corresponding HARQ-ACK information in the HARQ-ACK codebook.
24. The method according to claim 22, wherein, The first DCI that triggers the terminal to feed back the HARQ-ACK codebook includes at least one of the following: The DCI schedules the PDSCH and instructs the terminal to feed back the HARQ-ACK information corresponding to the PDSCH within the first uplink time domain unit; The terminal is triggered to feed back a Type-3 HARQ-ACK codebook or an enhanced Type-3 HARQ-ACK codebook via DCI within the first uplink time domain unit; The terminal is triggered to perform a HARQ-ACK codebook retransmission DCI within the first uplink time domain unit.
25. The method according to any one of claims 21-24, wherein, When the HARQ-ACK codebook contains only SPS HARQ-ACK, the terminal, in determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, performs at least one of the following for the second SPS PDSCH: When using rule one, the following operations are performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity is determined to be an invalid transmission opportunity; When using rule two, at least one of the following operations shall be performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type corresponding to the first transmission opportunity is different from the time-domain unit type corresponding to the HARQ-ACK codebook, the first transmission opportunity shall be determined as an invalid transmission opportunity. If each transmission opportunity corresponding to the second SPS PDSCH is determined to be an invalid transmission opportunity, the second SPS PDSCH shall be used as the first SPS PDSCH. If at least one transmission opportunity corresponding to the second SPS PDSCH is not determined to be an invalid transmission opportunity, the HARQ-ACK information corresponding to the second SPS PDSCH is fed back in the HARQ-ACK codebook. Wherein, the second SPS PDSCH is a time-domain feedback offset based on transmission time and application, and it is expected that any SPS PDSCH corresponding to HARQ-ACK information will be fed back within the first uplink time-domain unit; The first transmission opportunity is any one of the transmission opportunities corresponding to the second SPS PDSCH; The first time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
26. The method according to any one of claims 21-24, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the scheduling type of the PDSCH is a single PDSCH scheduling, determine the time domain resource allocation record set corresponding to each first downlink time domain unit associated with the Type-1 HARQ-ACK codebook on each serving cell, determine the transmission opportunity subset corresponding to the first downlink time domain unit based on the time domain resource allocation record set, and generate the corresponding HARQ-ACK bit for each transmission opportunity in the transmission opportunity subset. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the first time-domain resource allocation record: When using either Rule 1 or Rule 2, perform the following operation: if the second transmission opportunity satisfies the second time-domain relationship, determine the second transmission opportunity as an invalid transmission opportunity; If each transmission opportunity corresponding to the first time domain resource allocation record is determined to be an invalid transmission opportunity, the first time domain resource allocation record will be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit. Wherein, the first time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the time-domain resource allocation record set determined based on the application's time-domain resource allocation table; The second transmission opportunity is any one of the transmission opportunities corresponding to the first time-domain resource allocation record; The second time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; It overlaps with the time domain of the semi-static uplink time domain unit.
27. The method according to any one of claims 21-24, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, the following operations are performed for each serving cell: Based on the application's time-domain feedback offset set and time-domain resource allocation (TDRA) table, determine the extended time-domain feedback offset set and the complete set of time-domain resource allocation records; determine the time-domain resource allocation record set corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell; determine the transmission opportunity subset corresponding to the first downlink time-domain unit based on the time-domain resource allocation record set; and generate the corresponding HARQ-ACK bits for each transmission opportunity in the transmission opportunity subset. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the second time-domain resource allocation record: When using Rule 1, the following operation is performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the third transmission opportunity is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, the third transmission opportunity shall be determined as an invalid transmission opportunity. If a single transmission opportunity corresponding to the second time-domain resource allocation record is determined to be an invalid transmission opportunity, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. If the second time-domain resource allocation record cannot feed back the corresponding HARQ-ACK information in the first uplink time-domain unit based on any row of the TDRA table where the second time-domain resource allocation record is located and any time-domain feedback offset, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. Wherein, the second time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the complete set of time-domain resource allocation records; The third transmission opportunity is a single transmission opportunity corresponding to the second time-domain resource allocation record; The third time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
28. The method according to claim 27, wherein, When the third time-domain relationship includes time-domain overlap of time-domain units that completely correspond to the invalid time-domain unit type, determining that the third transmission opportunity is an invalid transmission opportunity when the third transmission opportunity satisfies the third time-domain relationship includes at least one of the following: Only when the downlink active bandwidth corresponding to the third transmission opportunity is configured or application configuration scheme 1 is applied, the following operation is performed: if the third transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the third transmission opportunity is determined to be an invalid transmission opportunity; For each time-domain feedback offset in the time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record; If the second time-domain resource allocation record is used as the starting time-domain resource allocation record in at least one schedulable row of the TDRA table, the third transmission opportunity is determined to be a valid transmission opportunity. If the second time-domain resource allocation record is included in at least one schedulable row of the TDRA table and the second time-domain resource allocation record is not used as the starting time-domain resource allocation record in any of the at least one schedulable rows, the following operations are performed: if the time-domain unit type of the third transmission opportunity is different from the application time-domain unit type of any of the at least one schedulable rows, the third transmission opportunity is determined to be an invalid transmission opportunity; or, if the time-domain unit type of the third transmission opportunity is the same as the application time-domain unit type of at least one of the at least one schedulable rows, the third transmission opportunity is determined to be a valid transmission opportunity. If the second time-domain resource allocation record is not included in any schedulable row of the TDRA table, the third transmission opportunity is determined to be an invalid transmission opportunity; Wherein, the target row is any row in the TDRA table, and the application time domain unit type of the schedulable row is the time domain unit type of a single transmission opportunity corresponding to the starting time domain resource allocation record of the schedulable row.
29. The method according to any one of claims 21-24, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, the following operations are performed for each serving cell: only the last time-domain resource allocation record of each row in the application's TDRA table is retained; the set of time-domain resource allocation records corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell is determined; based on the set of time-domain resource allocation records, a subset of transmission opportunities corresponding to the first downlink time-domain unit is determined; and for each transmission opportunity in the subset of transmission opportunities, the corresponding HARQ-ACK bits are generated. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the third time-domain resource allocation record: When using Rule 1, the following operation is performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity shall be determined as an invalid transmission opportunity; if the application time-domain unit type of any schedulable row corresponding to the third time-domain resource allocation record is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, each transmission opportunity corresponding to the third time-domain resource allocation record shall be determined as an invalid transmission opportunity. If each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity, the third time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. Wherein, the third time-domain resource allocation record is any time-domain resource allocation record in the time-domain resource allocation record set; the initial value of the time-domain resource allocation record set is a set consisting of the last time-domain resource allocation record of each row in the TDRA table; The fourth transmission opportunity is any one of the at least one transmission opportunities corresponding to the third time-domain resource allocation record; The application time-domain unit type of the schedulable row is the time-domain unit type of a single transmission opportunity corresponding to the initial time-domain resource allocation record of the schedulable row; The fourth time-domain relation includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
30. The method according to claim 29, wherein, When the fourth time-domain relationship includes time-domain overlap of time-domain units that completely correspond to invalid time-domain unit types, determining that the fourth transmission opportunity is an invalid transmission opportunity when the fourth transmission opportunity satisfies the fourth time-domain relationship includes at least one of the following: If the downlink active bandwidth portion of the fourth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fourth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fourth transmission opportunity is determined to be an invalid transmission opportunity. For each time-domain feedback offset in the application's time-domain feedback offset set, determine whether the target row in the TDRA table is a schedulable row; if the target row is a schedulable row, determine the starting time-domain resource allocation record of the target row, and determine the time-domain unit type of the single transmission opportunity corresponding to the starting time-domain resource allocation record; If none of the rows corresponding to the third time-domain resource allocation record are schedulable rows, then each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity. The target row is any row in the TDRA table.
31. The method according to any one of claims 21-24, wherein, When the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, the corresponding second codebook construction operation is performed according to the target information, including at least one of the following: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, two HARQ-ACK sub-codebooks are constructed. In the process of constructing the two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate the HARQ-ACK bit corresponding to the scheduled PDSCH. When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, TB groups or PDSCH groups are divided based on higher-layer configuration parameters, and one or two HARQ-ACK subcodebooks are constructed. In the process of constructing the one or two HARQ-ACK subcodebooks, for the first TB group or the first PDSCH group, the following operations are performed: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, it is determined whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and HARQ-ACK bits corresponding to the first TB group or the first PDSCH group are generated. Determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity includes at least one of the following: When using Rule 1, the following operation is performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the fifth transmission opportunity is different from the time-domain unit type of the Type-2 HARQ-ACK codebook, the fifth transmission opportunity shall be determined as an invalid transmission opportunity. Wherein, the first TB group is one of the TB groups divided based on the high-level configuration parameters, and the first PDSCH group is one of the PDSCH groups divided based on the high-level configuration parameters. The fifth transmission opportunity is a single transmission opportunity corresponding to the scheduled PDSCH; The fifth time-domain relation includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
32. The method according to claim 31, wherein, When the fifth time-domain relationship includes time-domain overlap of time-domain units that completely correspond to the invalid time-domain unit type, and the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity, including at least one of the following: If the downlink active bandwidth portion of the fifth transmission opportunity is configured or the application configuration scheme 1 is applied, the following operation is performed: if the fifth transmission opportunity completely overlaps with the time domain of the time domain unit corresponding to the invalid time domain unit type, the fifth transmission opportunity is determined to be an invalid transmission opportunity. Determine the starting PDSCH of the target schedule and the application time-domain unit type of the target schedule, wherein the target schedule is a single schedule based on the multi-PDSCH scheduling TDRA table, the scheduled PDSCH is one of the at least one PDSCH corresponding to the target schedule, and the HARQ-ACK information corresponding to the target schedule is fed back in the Type-2 HARQ-ACK codebook. The application time-domain unit type of the target scheduling is the time-domain unit type of a single transmission opportunity corresponding to the starting PDSCH of the target scheduling; If the scheduled PDSCH is used as the starting PDSCH of the target scheduling, the fifth transmission opportunity is determined to be a valid transmission opportunity. If the scheduled PDSCH is not used as the starting PDSCH in the target schedule, the following operations are performed: if the time domain unit type of the fifth transmission opportunity is different from the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be an invalid transmission opportunity; if the time domain unit type of the fifth transmission opportunity is the same as the application time domain unit type of the target schedule, the fifth transmission opportunity is determined to be a valid transmission opportunity.
33. The method according to claim 31 or 32, wherein, The generation of the HARQ-ACK bits corresponding to the scheduled PDSCH includes: If the fifth transmission opportunity is determined to be an invalid transmission opportunity, the HARQ-ACK bit corresponding to the scheduled PDSCH is set to NACK.
34. The method according to claim 31 or 32, wherein, The generation of HARQ-ACK bits corresponding to the first TB group or the first PDSCH group includes: In the case that the first TB group or the first PDSCH group corresponds to at least one valid PDSCH, the terminal assumes that any invalid PDSCH corresponding to the first TB group or the first PDSCH group is correctly received. If each scheduled PDSCH corresponding to the first TB group or the first PDSCH group is determined to be an invalid PDSCH, the HARQ-ACK bit corresponding to the first TB group or the first PDSCH group is set to NACK. Wherein, the valid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be a valid transmission opportunity, and the invalid PDSCH is the scheduled PDSCH for a single transmission opportunity that is determined to be an invalid transmission opportunity.
35. A shared channel transmission and HARQ-ACK feedback device, comprising: The first processing module is configured to perform a first operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the first operation including at least one of the following: Determine the physical shared channel that needs to be transmitted; When the target physical shared channel is a physical downlink shared channel (PDSCH), one of the following rules is used to determine the hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook fed back in the first uplink time domain unit: Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook; Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
36. The apparatus according to claim 35, wherein, The determination of the HARQ-ACK codebook includes at least one of the following: Determine the time-domain unit type corresponding to the HARQ-ACK codebook; When the HARQ-ACK codebook contains only SPS HARQ-ACK, in the process of determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, the first SPS PDSCH is excluded, or the SPS HARQ-ACK bit corresponding to the first SPS PDSCH is set to NACK, and the first SPS PDSCH is the SPS PDSCH whose corresponding transmission opportunity is determined to be an invalid transmission opportunity. If the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information; If the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, then according to the target information, the corresponding second codebook construction operation is performed; The target information includes at least one of the following: PDSCH scheduling type; The HARQ-ACK codebook needs to provide feedback on whether the transmission opportunity corresponding to the PDSCH with the corresponding HARQ-ACK information has been determined as an invalid transmission opportunity.
37. The apparatus according to claim 36, wherein, When the HARQ-ACK codebook contains only SPS HARQ-ACK, during the process of determining the SPS PDSCH that needs to feed back the corresponding HARQ-ACK information in the HARQ-ACK codebook, at least one of the following is performed for the second SPS PDSCH: When using rule one, the following operations are performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity is determined to be an invalid transmission opportunity; When using rule two, at least one of the following operations shall be performed: if the first transmission opportunity satisfies the first time-domain relationship, the first transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type corresponding to the first transmission opportunity is different from the time-domain unit type corresponding to the HARQ-ACK codebook, the first transmission opportunity shall be determined as an invalid transmission opportunity. If each transmission opportunity corresponding to the second SPS PDSCH is determined to be an invalid transmission opportunity, the second SPS PDSCH shall be used as the first SPS PDSCH. If at least one transmission opportunity corresponding to the second SPS PDSCH is not determined to be an invalid transmission opportunity, the HARQ-ACK information corresponding to the second SPS PDSCH is fed back in the HARQ-ACK codebook. Wherein, the second SPS PDSCH is a time-domain feedback offset based on transmission time and application, and it is expected that any SPS PDSCH corresponding to HARQ-ACK information will be fed back within the first uplink time-domain unit; The first transmission opportunity is any one of the transmission opportunities corresponding to the second SPS PDSCH; The first time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
38. The apparatus according to claim 36, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the scheduling type of the PDSCH is a single PDSCH scheduling, determine the time domain resource allocation record set corresponding to each first downlink time domain unit associated with the Type-1 HARQ-ACK codebook on each serving cell, determine the transmission opportunity subset corresponding to the first downlink time domain unit based on the time domain resource allocation record set, and generate the corresponding HARQ-ACK bit for each transmission opportunity in the transmission opportunity subset. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the first time-domain resource allocation record: When using either Rule 1 or Rule 2, perform the following operation: if the second transmission opportunity satisfies the second time-domain relationship, determine the second transmission opportunity as an invalid transmission opportunity; If each transmission opportunity corresponding to the first time domain resource allocation record is determined to be an invalid transmission opportunity, the first time domain resource allocation record will be removed from the time domain resource allocation record set corresponding to the first downlink time domain unit. Wherein, the first time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the time-domain resource allocation record set determined based on the application's time-domain resource allocation table; The second transmission opportunity is any one of the transmission opportunities corresponding to the first time-domain resource allocation record; The second time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; It overlaps with the time domain of the semi-static uplink time domain unit.
39. The apparatus according to claim 36, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, the following operations are performed for each serving cell: Based on the application's time-domain feedback offset set and time-domain resource allocation (TDRA) table, determine the extended time-domain feedback offset set and the complete set of time-domain resource allocation records; determine the time-domain resource allocation record set corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell; determine the transmission opportunity subset corresponding to the first downlink time-domain unit based on the time-domain resource allocation record set; and generate the corresponding HARQ-ACK bits for each transmission opportunity in the transmission opportunity subset. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the second time-domain resource allocation record: When using Rule 1, the following operation is performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the third transmission opportunity satisfies the third time-domain relationship, the third transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the third transmission opportunity is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, the third transmission opportunity shall be determined as an invalid transmission opportunity. If a single transmission opportunity corresponding to the second time-domain resource allocation record is determined to be an invalid transmission opportunity, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. If the second time-domain resource allocation record cannot feed back the corresponding HARQ-ACK information in the first uplink time-domain unit based on any row of the TDRA table where the second time-domain resource allocation record is located and any time-domain feedback offset, the second time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. Wherein, the second time-domain resource allocation record is any one of the time-domain resource allocation record sets corresponding to the first downlink time-domain unit; the initial value of the time-domain resource allocation record set corresponding to the first downlink time-domain unit is the complete set of time-domain resource allocation records; The third transmission opportunity is a single transmission opportunity corresponding to the second time-domain resource allocation record; The third time-domain relationship includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
40. The apparatus according to claim 36, wherein, When the HARQ-ACK codebook is a Type-1 HARQ-ACK codebook, the corresponding first codebook construction operation is performed according to the target information, including: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, the following operations are performed for each serving cell: only the last time-domain resource allocation record of each row in the application's TDRA table is retained; the set of time-domain resource allocation records corresponding to each first downlink time-domain unit associated with the Type-1 HARQ-ACK codebook on the serving cell is determined; based on the set of time-domain resource allocation records, a subset of transmission opportunities corresponding to the first downlink time-domain unit is determined; and for each transmission opportunity in the subset of transmission opportunities, the corresponding HARQ-ACK bits are generated. In determining the set of time-domain resource allocation records corresponding to the first downlink time-domain unit, at least one of the following is performed for the third time-domain resource allocation record: When using Rule 1, the following operation is performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the fourth transmission opportunity satisfies the fourth time-domain relationship, the fourth transmission opportunity shall be determined as an invalid transmission opportunity; if the application time-domain unit type of any schedulable row corresponding to the third time-domain resource allocation record is different from the time-domain unit type of the Type-1 HARQ-ACK codebook, each transmission opportunity corresponding to the third time-domain resource allocation record shall be determined as an invalid transmission opportunity. If each transmission opportunity corresponding to the third time-domain resource allocation record is determined to be an invalid transmission opportunity, the third time-domain resource allocation record will be removed from the time-domain resource allocation record set corresponding to the first downlink time-domain unit. Wherein, the third time-domain resource allocation record is any time-domain resource allocation record in the time-domain resource allocation record set; the initial value of the time-domain resource allocation record set is a set consisting of the last time-domain resource allocation record of each row in the TDRA table; The fourth transmission opportunity is any one of the at least one transmission opportunities corresponding to the third time-domain resource allocation record; The application time-domain unit type of the schedulable row is the time-domain unit type of a single transmission opportunity corresponding to the initial time-domain resource allocation record of the schedulable row; The fourth time-domain relation includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
41. The apparatus according to claim 36, wherein, When the HARQ-ACK codebook is a Type-2 HARQ-ACK codebook, the corresponding second codebook construction operation is performed according to the target information, including at least one of the following: When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is disabled, two HARQ-ACK sub-codebooks are constructed. In the process of constructing the two HARQ-ACK sub-codebooks, for a scheduled PDSCH, the following operations are performed: determine whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; generate the HARQ-ACK bit corresponding to the scheduled PDSCH. When the PDSCH scheduling type is multi-PDSCH scheduling and time-domain binding is enabled, TB groups or PDSCH groups are divided based on higher-layer configuration parameters, and one or two HARQ-ACK subcodebooks are constructed. In the process of constructing the one or two HARQ-ACK subcodebooks, for the first TB group or the first PDSCH group, the following operations are performed: for each scheduled PDSCH corresponding to the first TB group or the first PDSCH group, it is determined whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity; and HARQ-ACK bits corresponding to the first TB group or the first PDSCH group are generated. Determining whether the transmission opportunity corresponding to the scheduled PDSCH is an invalid transmission opportunity includes at least one of the following: When using Rule 1, the following operation is performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity is determined to be an invalid transmission opportunity; When using Rule 2, at least one of the following operations shall be performed: if the fifth transmission opportunity satisfies the fifth time-domain relationship, the fifth transmission opportunity shall be determined as an invalid transmission opportunity; if the time-domain unit type of the fifth transmission opportunity is different from the time-domain unit type of the Type-2 HARQ-ACK codebook, the fifth transmission opportunity shall be determined as an invalid transmission opportunity. Wherein, the first TB group is one of the TB groups divided based on the high-level configuration parameters, and the first PDSCH group is one of the PDSCH groups divided based on the high-level configuration parameters. The fifth transmission opportunity is a single transmission opportunity corresponding to the scheduled PDSCH; The fifth time-domain relation includes at least one of the following: Time-domain overlap with sub-band full-duplex SBFD time-domain units and non-SBFD time-domain units; The time domain overlaps with the time domain of the time domain corresponding to the invalid time domain type; It overlaps with the time domain of the semi-static uplink time domain unit.
42. A shared channel transmission and HARQ-ACK feedback device, comprising: The second processing module is configured to perform a second operation when there is an invalid transmission opportunity among the transmission opportunities corresponding to the target physical shared channel, the second operation including at least one of the following: Determine the physical shared channel that needs to be transmitted; The receiving terminal sends a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook within the first uplink time domain unit. This HARQ-ACK codebook is determined by the terminal using one of the following rules: Rule 1: HARQ-ACK information corresponding to PDSCHs of multiple time-domain unit types is allowed to be reused in the same HARQ-ACK codebook; Rule 2: Only HARQ-ACK information corresponding to PDSCH of the same time-domain unit type is allowed to be reused in the same HARQ-ACK codebook.
43. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the shared channel transmission and HARQ-ACK feedback method as described in any one of claims 1 to 17.
44. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the shared channel transmission and HARQ-ACK feedback method as described in any one of claims 18 to 34.
45. A readable storage medium storing a program or instructions that, when executed by a processor, implement the shared channel transmission and HARQ-ACK feedback method as described in any one of claims 1 to 17, or implement the steps of the shared channel transmission and HARQ-ACK feedback method as described in any one of claims 18 to 34.
