SPS pdsch-related method and device for node used for wireless communication

Abstract

The present application discloses an SPS PDSCH-related method and device for a node used for wireless communication. A first receiver receives configuration information of at least a first SPS PDSCH. A first transmitter determines and sends a first HARQ-ACK bit block, the first HARQ-ACK bit block comprising at least one HARQ-ACK bit, wherein the determination of the first HARQ-ACK bit block depends on an overlapping condition between the first SPS PDSCH and a first-type PUCCH, one first-type PUCCH is in a first-type time-domain resource, and the first-type time-domain resource is a time-domain resource comprising symbols other than a symbol indicated by uplink-downlink TDD configuration signaling as an uplink.

Description

A method and apparatus related to SPS PDSCH in a node used for wireless communication

[0001] This application claims priority to a Chinese patent application filed with the Patent Office of China on January 4, 2024, with application number 202410015143.3 and invention name “A method and apparatus related to SPS PDSCH in a node used for wireless communication”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to a transmission method and apparatus for wireless signals in a wireless communication system supporting a cellular network. Background Art

[0003] In existing NR (New Radio) systems, spectrum resources are statically divided into FDD (Frequency Division Duplex) and TDD (Time Division Duplex) spectrum. For TDD spectrum, both base stations and user equipment (UE) operate in half-duplex mode. This half-duplex mode avoids self-interference and mitigates the impact of cross-link interference (CLI), but it also leads to reduced resource utilization and increased latency. To address these issues, supporting flexible duplex modes or variable link directions (uplink, downlink, or flexible) in TDD or FDD spectrum has become a possible solution. The 3GPP (3rd Generation Partnership Project) RAN (Radio Access Network) 1#103e meeting agreed to research on duplex technologies, specifically the proposed Subband Non-Overlapping Full Duplex (SBFD) mode for gNB (NR Node B). In this mode, the same symbol will be used for uplink in part of the frequency resources and for downlink in another part of the frequency resources, thereby improving resource utilization and reducing latency.

[0004] SPS (Semi-Persistent Scheduling) is an effective mechanism to reduce signaling overhead, transmission delay and power consumption. Summary of the Invention

[0005] For systems with higher configuration flexibility, how to improve HARQ-ACK (Hybrid Automatic Repeat reQuest-ACKnowledgement) feedback is an important issue worthy of consideration; the present application discloses a solution to the above problem. It should be noted that the present application can be applicable to a variety of wireless communication scenarios, such as scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, scenarios supporting only half-duplex modes, etc., and achieve similar technical effects. In addition, the use of a unified solution for different scenarios (including but not limited to scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, scenarios supporting only half-duplex modes) can also help reduce hardware complexity and cost, or improve performance. In the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

[0006] Where necessary, the interpretation of the terms in this application may refer to the description of the 3GPP specification protocols TS37 series and TS38 series.

[0007] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0008] receiving configuration information of at least a first SPS PDSCH;

[0009] Determining and sending a first HARQ-ACK bit block, where the first HARQ-ACK bit block includes at least one HARQ-ACK bit;

[0010] The determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0011] As an embodiment, the problem to be solved by the present application includes: how to enhance HARQ-ACK feedback under a system configuration that allows overlap between SPS PDSCH (Physical Downlink Shared Channel) and the first type of PUCCH.

[0012] As an embodiment, the problem to be solved by this application includes: how to improve the feedback efficiency of HARQ-ACK.

[0013] As an embodiment, the problem to be solved by this application includes: how to improve HARQ-ACK feedback for SPS PDSCH.

[0014] As an embodiment, the problem to be solved by the present application includes: how to determine the first HARQ-ACK bit block.

[0015] As an embodiment, the benefits of the above method include: being conducive to enhancing HARQ-ACK feedback under the condition of good configuration flexibility (allowing SPS PDSCH and PUCCH to overlap in time domain resources outside the symbols indicated as uplink by uplink and downlink TDD configuration signaling).

[0016] As an embodiment, the benefits of the above method include: improving the resource utilization efficiency of PUCCH.

[0017] As an embodiment, the above method has the following benefits: it is advantageous to optimize system performance under full-duplex operation (operation(s)) (non-overlapping sub-bands or other types) at least on the base station side.

[0018] As an embodiment, the advantages of the above method include: good compatibility with existing 3GPP protocols and small workload for standardization.

[0019] As an embodiment, in the above method, the first type of PUCCH only occupies time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling. This feature is conducive to reducing the complexity of system design.

[0020] According to one aspect of the present application, the above method is characterized in that:

[0021] The first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH when a first set of conditions is met; the first set of conditions includes a first condition, and the first condition depends on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0022] As an embodiment, the benefits of the above method include: being conducive to optimizing the problem of which SPS PDSCH HARQ-ACK bits are included in the first HARQ-ACK bit block.

[0023] According to one aspect of the present application, the above method is characterized in that:

[0024] The first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; and one SPS PDSCH among the multiple SPS PDSCHs is an SPS PDSCH overlapping with the first type of PUCCH.

[0025] As an embodiment, the benefits of the above method include: performing HARQ-ACK feedback for a valid SPS PDSCH, thereby improving HARQ-ACK feedback efficiency or robustness.

[0026] According to one aspect of the present application, the above method is characterized in that:

[0027] When the first SPS PDSCH overlaps with the first-type PUCCH, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH.

[0028] As an embodiment, the benefits of the above method include: effectively reducing HARQ-ACK feedback overhead.

[0029] According to one aspect of the present application, the above method is characterized in that:

[0030] The first type of PUCCH is configured by higher layer parameters.

[0031] As an embodiment, the benefits of the above method include: avoiding the impact of the dynamically scheduled PUCCH on the determination of the first HARQ-ACK bit block, which is conducive to ensuring the consistency of the understanding of the bits included in the first HARQ-ACK bit block by both communicating parties.

[0032] According to one aspect of the present application, the above method is characterized in that:

[0033] The first type of time domain resources includes symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0034] As an embodiment, the benefits of the above method include: improving uplink capacity.

[0035] As an embodiment, combined with the above features, the method disclosed in the present application is conducive to achieving a comprehensive enhancement effect of high configuration flexibility, high HARQ-ACK feedback performance, and high uplink capacity.

[0036] As an embodiment, the benefits of the above method include: it is helpful to ensure the effective transmission of the first type of PUCCH that occupies the symbols (symbol(s)) indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0037] As an embodiment, the benefits of the above method include: it is facilitating the application of the solution disclosed in this application in a full-duplex operating system, thereby improving system efficiency.

[0038] According to one aspect of the present application, the above method is characterized in that:

[0039] The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0040] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0041] Sending configuration information of at least a first SPS PDSCH;

[0042] receiving a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit;

[0043] The determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0044] According to one aspect of the present application, the above method is characterized in that:

[0045] The first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH when a first set of conditions is met; the first set of conditions includes a first condition, the first condition depending on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0046] According to one aspect of the present application, the above method is characterized in that:

[0047] The first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; and one SPS PDSCH among the multiple SPS PDSCHs is an SPS PDSCH overlapping with the first type of PUCCH.

[0048] According to one aspect of the present application, the above method is characterized in that:

[0049] When the first SPS PDSCH overlaps with the first-type PUCCH, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH.

[0050] According to one aspect of the present application, the above method is characterized in that:

[0051] The first type of PUCCH is configured by higher layer parameters.

[0052] According to one aspect of the present application, the above method is characterized in that:

[0053] The first type of time domain resources includes symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0054] According to one aspect of the present application, the above method is characterized in that:

[0055] The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0056] The present application discloses a first node used for wireless communication, characterized by comprising:

[0057] A first receiver receives configuration information of at least a first SPS PDSCH;

[0058] A first transmitter determines and sends a first HARQ-ACK bit block, where the first HARQ-ACK bit block includes at least one HARQ-ACK bit;

[0059] The determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0060] The present application discloses a second node used for wireless communication, characterized by comprising:

[0061] A second transmitter transmits configuration information of at least a first SPS PDSCH;

[0062] A second receiver receives a first HARQ-ACK bit block, where the first HARQ-ACK bit block includes at least one HARQ-ACK bit;

[0063] The determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0065] FIG1 shows a processing flow chart of a first node according to an embodiment of the present application;

[0066] FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0067] FIG3 shows a schematic diagram of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0068] FIG4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0069] FIG5 shows a signal transmission flow chart according to an embodiment of the present application;

[0070] FIG6 is a schematic diagram illustrating that determination of a first HARQ-ACK bit block depends on overlap between a first SPS PDSCH and a first type of PUCCH according to one embodiment of the present application;

[0071] FIG7 is a schematic diagram illustrating a first condition according to an embodiment of the present application;

[0072] FIG8 is a schematic diagram illustrating various SPS PDSCHs according to an embodiment of the present application;

[0073] FIG9 shows a schematic diagram illustrating various SPS PDSCHs according to an embodiment of the present application;

[0074] FIG10 is a schematic diagram illustrating various SPS PDSCHs according to an embodiment of the present application;

[0075] FIG11 shows a schematic diagram illustrating a first type of time domain resources according to an embodiment of the present application;

[0076] FIG12 shows a schematic diagram illustrating a first type of PUCCH according to an embodiment of the present application;

[0077] FIG13 is a schematic diagram illustrating a first node sending a first type PUCCH according to an embodiment of the present application;

[0078] FIG14 shows a structural block diagram of a processing device in a first node device according to an embodiment of the present application;

[0079] FIG15 shows a structural block diagram of a processing device in a second node device according to an embodiment of the present application. DETAILED DESCRIPTION

[0080] The technical solution of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that, in the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other at will.

[0081] Example 1

[0082] Example 1 illustrates a processing flow chart of a first node according to an embodiment of the present application, as shown in FIG1 .

[0083] In embodiment 1, the first node in the present application receives configuration information of at least a first SPS PDSCH in step 101; determines a first HARQ-ACK bit block in step 102; and sends the first HARQ-ACK bit block in step 103.

[0084] In embodiment 1, the first HARQ-ACK bit block includes at least one HARQ-ACK bit; the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0085] As an embodiment, an SPS (Semi-Persistent Scheduling) PDSCH is a PDSCH without a corresponding PDCCH (Physical Downlink Control CHannel) transmission.

[0086] As an embodiment, the first node receives a first SPS PDSCH configuration, where the first SPS PDSCH configuration includes configuration information of the first SPS PDSCH.

[0087] As an embodiment, the first node receives multiple SPS PDSCH configurations, and one SPS PDSCH configuration among the multiple SPS PDSCH configurations includes configuration information of the first SPS PDSCH.

[0088] As an embodiment, the first node sends the first HARQ-ACK bit block on the target PUCCH (Physical Uplink Control CHannel).

[0089] As an embodiment, the first SPS PDSCH is an SPS PDSCH in a first time slot set associated with a first SPS PDSCH configuration on a first service cell, and the first time slot set includes a first time slot, which is a downlink time slot for the SPS PDSCH having HARQ-ACK information multiplexed to the target PUCCH on the first service cell.

[0090] As an embodiment, the first time slot set only includes the first time slot.

[0091] As an embodiment, the first set of time slots includes more than one time slot.

[0092] As an embodiment, the first time slot set is configurable.

[0093] As an embodiment, the first time slot set consists of the time slots from time slot n-M+1 to time slot n, where n is the time slot index of the first time slot, time slot n is the first time slot, and M is configurable.

[0094] As an embodiment, M is equal to or greater than 1.

[0095] As an embodiment, the M is configured by a parameter in SPS-Config.

[0096] As an embodiment, the M is configured by pdsch-AggregationFactor-r16.

[0097] As an embodiment, the M is configured by a parameter in PDSCH-config.

[0098] As an embodiment, the M is configured by pdsch-AggregationFactor.

[0099] As an embodiment, the first serving cell is a serving cell configured for the first node.

[0100] As an embodiment, the serving cell index of the first serving cell is equal to 0.

[0101] As an embodiment, the serving cell index of the first serving cell is greater than 0.

[0102] As an embodiment, the first SPS PDSCH configuration is configured for the first serving cell.

[0103] As an embodiment, the first SPS PDSCH configuration is a configuration for downlink semi-persistent transmission.

[0104] As an embodiment, the first SPS PDSCH configuration is configured by the first RRC signaling.

[0105] As an embodiment, the first SPS PDSCH configuration is configured by SPS-Config.

[0106] As an embodiment, when an SPS PDSCH configuration includes configuration information for an SPS PDSCH, the SPS PDSCH is associated with the SPS PDSCH configuration.

[0107] As an embodiment, for an SPS PDSCH, the allocated time domain resources are determined based on a periodicity indicated by the associated SPS PDSCH configuration.

[0108] As an embodiment, for an SPS PDSCH, the applied HARQ (Hybrid automatic repeat request) process number is determined based on the number of HARQ processes indicated by the associated SPS PDSCH configuration.

[0109] As an embodiment, one SPS PDSCH is activated for the associated SPS PDSCH configuration.

[0110] As an embodiment, the first SPS PDSCH configuration is configured for the first serving cell; for the first node, the first serving cell is configured with one or more SPS PDSCH configurations.

[0111] As an embodiment, the configuration information of the first SPS PDSCH includes an SPS PDSCH configuration index corresponding to the first SPS PDSCH.

[0112] As an embodiment, the configuration information of the first SPS PDSCH includes configuration information of the SPS PDSCH configuration associated with the first SPS PDSCH.

[0113] As an embodiment, the configuration information of the first SPS PDSCH includes a configuration parameter of the periodicity of the SPS.

[0114] As an embodiment, the configuration information of the first SPS PDSCH includes a configuration parameter of a HARQ process number.

[0115] As an embodiment, the first HARQ-ACK bit block is used to generate a first sequence, and the first sequence is sent after being mapped to a physical resource.

[0116] As an embodiment, the first HARQ-ACK bit block is sent after being at least sequence modulated and mapped to physical resources.

[0117] As an embodiment, the first HARQ-ACK bit block is sent after CRC addition, segmentation, code block CRC attachment, channel coding, rate matching, concatenation, scrambling, modulation, spreading, and mapping to at least part of physical resources.

[0118] As an embodiment, at least the first HARQ-ACK bit block is sent after CRC attachment, segmentation, code block CRC attachment, channel coding, rate matching, concatenation, scrambling, modulation, block-wise spreading, transform precoding and at least part of mapping to physical resources.

[0119] As an embodiment, the first HARQ-ACK bit block is used to generate a first sequence, and the first sequence is mapped to physical resources and then sent in the target PUCCH.

[0120] As an embodiment, the first HARQ-ACK bit block is sent on the target PUCCH after being at least sequence modulated and mapped to physical resources.

[0121] As an embodiment, the first HARQ-ACK bit block is sent on the target PUCCH after CRC addition, segmentation, code block CRC attachment, channel coding, rate matching, concatenation, scrambling, modulation, spreading, and mapping to at least part of physical resources.

[0122] As an embodiment, at least the first HARQ-ACK bit block is sent on the target PUCCH after CRC addition, segmentation, code block CRC attachment, channel coding, rate matching, concatenation, scrambling, modulation, block-wise spreading, transform precoding and mapping to physical resources.

[0123] As an embodiment, the HARQ-ACK bits in the first HARQ-ACK bit block are multiplexed onto the target PUCCH and then sent.

[0124] As an embodiment, the target PUCCH is only used to send HARQ-ACK information for the SPS PDSCH.

[0125] As an embodiment, the first node reports HARQ-ACK information only for SPSPDSCH in the target PUCCH.

[0126] As an embodiment, the first HARQ-ACK bit block includes one or more HARQ-ACK bits.

[0127] As an embodiment, the first HARQ-ACK bit block includes multiple HARQ-ACK bits.

[0128] As an embodiment, there are 2 HARQ-ACK bits in the first HARQ-ACK bit block, and these 2 HARQ-ACK bits are generated for different serving cells respectively.

[0129] As an embodiment, there are 2 HARQ-ACK bits in the first HARQ-ACK bit block, and the 2 HARQ-ACK bits are generated for different SPS PDSCH configurations respectively.

[0130] As an embodiment, there are 2 HARQ-ACK bits in the first HARQ-ACK bit block, and these 2 HARQ-ACK bits are generated for different downlink time slots respectively.

[0131] As an embodiment, there are 2 HARQ-ACK bits in the first HARQ-ACK bit block, and these 2 HARQ-ACK bits are generated for the same serving cell.

[0132] As an embodiment, there are 2 HARQ-ACK bits in the first HARQ-ACK bit block, and these 2 HARQ-ACK bits are generated for the same SPS PDSCH configuration.

[0133] As an embodiment, the first HARQ-ACK bit block is: in response to (in response to) more than one SPS PDSCH (Semi-Persistent Scheduling Physical Downlink Shared CHannel) HARQ-ACK bits (bits).

[0134] As an embodiment, the first HARQ-ACK bit block is a HARQ-ACK codebook.

[0135] As an embodiment, the first HARQ-ACK bit block is a semi-static HARQ-ACK codebook.

[0136] As an embodiment, the first HARQ-ACK bit block is a dynamic HARQ-ACK codebook.

[0137] As an embodiment, the first HARQ-ACK bit block is a HARQ-ACK codebook only for SPS PDSCH reception.

[0138] As an embodiment, one HARQ-ACK bit in the first HARQ-ACK bit block is a HARQ-ACK information bit.

[0139] As an embodiment, any HARQ-ACK bit in the first HARQ-ACK bit block is generated for one serving cell, one SPS PDSCH configuration, and one downlink time slot.

[0140] As an embodiment, the determination of the first HARQ-ACK bit block includes: determining whether the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH.

[0141] As an embodiment, if the HARQ-ACK bit for the first SPS PDSCH is assigned to the bit in the first HARQ-ACK bit block, the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH; otherwise, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

[0142] As an embodiment, the first SPS PDSCH is any SPS PDSCH that complies with a first feature set.

[0143] As an embodiment, the first node independently determines a plurality of SPS PDSCHs including all SPS PDSCHs that meet a first feature set, and the first SPS PDSCH is any one of the determined plurality of SPS PDSCHs.

[0144] As an embodiment, the first feature set includes at least one feature; and conforming to the first feature set means conforming to each feature in the first feature set.

[0145] As an embodiment, the first feature set includes only one feature.

[0146] As an embodiment, the first feature set includes multiple features.

[0147] As an embodiment, one of the features in the first feature set is: activated by a DCI (Downlink control information) format.

[0148] As an embodiment, one of the features in the first feature set is that the corresponding HARQ-ACK information is associated with the target PUCCH.

[0149] As an embodiment, one of the features in the first feature set is that the corresponding HARQ-ACK information is configured to be multiplexed into the target PUCCH.

[0150] As an embodiment, in order to determine the first HARQ-ACK bit block, each SPS PDSCH examined is an SPS PDSCH that meets the first feature set.

[0151] As an embodiment, each HARQ-ACK bit included in the first HARQ-ACK bit block is a HARQ-ACK bit for an SPS PDSCH that conforms to the first feature set.

[0152] As an embodiment, the overlapping condition between the first SPS PDSCH and the first type of PUCCH includes: whether the first SPS PDSCH overlaps with the first type of PUCCH or not.

[0153] As an embodiment, in the present application, the overlapping between the first SPS PDSCH and the first type of PUCCH is in terms of the time domain.

[0154] As an embodiment, in the present application, the first SPS PDSCH and the first type of PUCCH overlap / do not overlap, which means that the first SPS PDSCH and the first type of PUCCH overlap / do not overlap in the time domain.

[0155] As an embodiment, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH depends on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0156] As an embodiment, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH depends on whether the first SPS PDSCH overlaps with the first type of PUCCH.

[0157] As an embodiment, the first HARQ-ACK bit block includes at least one HARQ-ACK bit for the first SPS PDSCH, and the first HARQ-ACK bit block includes the at least one HARQ-ACK bit for the first SPS PDSCH relying on the first SPS PDSCH not overlapping with the first type PUCCH.

[0158] As an embodiment, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH, and the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH depending on the overlap of the first SPS PDSCH with the first type PUCCH.

[0159] As an embodiment, the determination of expressing the first HARQ-ACK bit block as depending on the overlap between the first SPS PDSCH and the first type of PUCCH includes:

[0160] The first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH when a first set of conditions is met; the first set of conditions includes a first condition, and the first condition depends on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0161] As an embodiment, the determination of the first HARQ-ACK bit block depends on whether the first set of conditions is met.

[0162] As an embodiment, if the first SPS PDSCH overlaps with at least 8 of the first-type PUCCHs, the first HARQ-ACK bit block includes 3 repetitions of the HARQ-ACK bit for the first SPS PDSCH; if the first SPS PDSCH overlaps with less than 8 and at least 5 of the first-type PUCCHs, the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH (without repetition); otherwise, the first HARQ-ACK bit block includes 16 repetitions of the HARQ-ACK bit for the first SPS PDSCH.

[0163] As an embodiment, if the first SPS PDSCH overlaps with at least 12 of the first-type PUCCHs, the first HARQ-ACK bit block includes 3 repetitions of the HARQ-ACK bit for the first SPS PDSCH; if the first SPS PDSCH overlaps with less than 12 and at least 3 of the first-type PUCCHs, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH; otherwise, the first HARQ-ACK bit block includes 8 repetitions of the HARQ-ACK bit for the first SPS PDSCH.

[0164] As an embodiment, based on the configuration, there are one or more PUCCHs belonging to the first category of PUCCHs.

[0165] As an embodiment, any of the first-type PUCCHs is in the first-type time domain resources.

[0166] As an embodiment, a first-type PUCCH in the first-type time-domain resources is in terms of the time domain.

[0167] As an embodiment, a first-type PUCCH is in the first-type time domain resources, including: time domain resources allocated to the first-type PUCCH are all included in the first-type time domain resources.

[0168] As an embodiment, a first-type PUCCH is in the first-type time domain resources, including: from the time domain point of view, the PUCCH resources used for this first-type PUCCH are within the first-type time domain resources.

[0169] As an embodiment, a first-type PUCCH in the first-type time domain resources includes: symbols allocated to the first-type PUCCH are all symbols included in the first-type time domain resources.

[0170] As an embodiment, at least a portion of the first-type PUCCH exists in a symbol (symbol(s)) indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission.

[0171] As an embodiment, a symbol in the present application is a time domain symbol.

[0172] As an embodiment, a symbol in the present application is an OFDM (Orthogonal frequency division multiplex) symbol.

[0173] As an embodiment, a symbol in the present application is a symbol in a time slot.

[0174] As an embodiment, a symbol in the present application includes a time duration in the time domain.

[0175] As an embodiment, the HARQ-ACK information for the first SPS PDSCH is associated with the target PUCCH.

[0176] As an embodiment, the first SPS PDSCH is on a serving cell index configured for the first node.

[0177] As an embodiment, the first SPS PDSCH is in a downlink time slot.

[0178] As an embodiment, the first type of time domain resources does not include symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0179] Example 2

[0180] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in FIG2 . FIG2 illustrates a network architecture 200 of a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system. The 5G NR / LTE / LTE-A network architecture 200 may be referred to as a 5G System (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5G Core Network (5G Core Network) / EPC (Evolved Packet Core) 210, a Home Subscriber Server (HSS) / UDM (Unified Data Management) 220, and an Internet service 230. 5GS / EPS can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP (Transmitter Receiver Point), or some other appropriate terminology. Node 203 provides an access point to 5GC / EPC 210 for UE 201.Examples of UE 201 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. Node 203 connects to the 5GC / EPC 210 via the S1 / NG interface. The 5GC / EPC 210 includes the MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, the S-GW (Service Gateway) / UPF (User Plane Function) 212, and the P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that handles signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF 212, which itself is connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet Services 230. The Internet Services 230 includes the operator's corresponding Internet Protocol services, which may include the Internet, Intranet, IMS (IP Multimedia Subsystem), and packet switching services.

[0181] As an embodiment, the UE201 corresponds to the first node in this application.

[0182] As an embodiment, the gNB203 corresponds to the second node in this application.

[0183] As an embodiment, the UE201 corresponds to the first node in this application, and the gNB203 corresponds to the second node in this application.

[0184] As an embodiment, the gNB203 is a macro cellular base station.

[0185] As an embodiment, the gNB203 is a micro cell base station.

[0186] As an embodiment, the gNB203 is a picocell (PicoCell) base station.

[0187] As an embodiment, the gNB203 is a home base station (Femtocell).

[0188] As an embodiment, the gNB203 is a base station device that supports large delay difference.

[0189] As an embodiment, the gNB203 is a flying platform device.

[0190] As an embodiment, the gNB203 is a satellite device.

[0191] Example 3

[0192] Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in FIG3 . FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 illustrates the radio protocol architecture for a first communication node device (a UE, a gNB, or an RSU (Roadside Unit) in a V2X (Vehicle to Everything) network, an onboard device, or an onboard communication module) and a second communication node device (a gNB, a UE, or an RSU in a V2X network, an onboard device, or an onboard communication module), or the control plane 300 between two UEs using three layers: Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). L1 is the lowest layer and implements various PHY (physical layer) signal processing functions. L1 will be referred to herein as PHY 301. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first communication node device and the second communication node device and the two UEs through PHY301. L2 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second communication node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first communication node device between the second communication node devices. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell between first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in L3 of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling between the second communication node device and the first communication node device.The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture for the first and second communication node devices in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300, including the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355. However, the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping QoS (Quality of Service) flows and data radio bearers (DRBs) to support service diversity. Although not shown, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., an IP (Internet Protocol) layer) terminating at the P-GW on the network side and an application layer terminating at the other end of the connection (e.g., a remote UE, a server, etc.).

[0193] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the first node in this application.

[0194] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the second node in this application.

[0195] As an embodiment, the configuration information of the SPS PDSCH in the present application is generated in the RRC sublayer 306 .

[0196] As an embodiment, the configuration information of the SPS PDSCH in the present application is generated in the MAC sublayer 302 .

[0197] As an embodiment, the configuration information of the SPS PDSCH in this application is generated in the PHY 301 .

[0198] As an embodiment, the uplink and downlink TDD configuration signaling in this application is generated in the RRC sublayer 306.

[0199] As an embodiment, the first SPS PDSCH in this application is generated by the PHY351.

[0200] As an embodiment, the first HARQ-ACK bit block in the present application is generated in the MAC sublayer 302.

[0201] As an embodiment, the first HARQ-ACK bit block in the present application is generated by the PHY301.

[0202] As an embodiment, the target PUCCH in this application is generated in the PHY301.

[0203] As an embodiment, the first type of PUCCH in this application is generated in the PHY301.

[0204] As an embodiment, the higher layer in this application refers to a layer above the physical layer.

[0205] As an embodiment, the higher layer in the present application includes a MAC layer.

[0206] As an embodiment, the higher layer in the present application includes an RRC layer.

[0207] Example 4

[0208] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in Figure 4. Figure 4 is a block diagram of a first communication device 410 and a second communication device 450 communicating with each other in an access network.

[0209] The first communications device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 , and an antenna 420 .

[0210] The second communication device 450 includes a controller / processor 459 , a memory 460 , a data source 467 , a transmit processor 468 , a receive processor 456 , a multi-antenna transmit processor 457 , a multi-antenna receive processor 458 , a transmitter / receiver 454 and an antenna 452 .

[0211] During transmission from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 layer functionality. During transmission from the first communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and allocation of radio resources to the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 performs coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform (Inverse Fast Fourier Transform). Transform (IFFT) is used to generate a physical channel that carries a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, which is then provided to a different antenna 420.

[0212] During transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives a signal via its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signal and reference signal are demultiplexed by the receive processor 456, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial stream destined for the second communication device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communications device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the first communications device 410 to the second communications device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 layer for L3 processing.

[0213] During transmission from the second communication device 450 to the first communication device 410, a data source 467 is used at the second communication device 450 to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission functionality at the first communication device 410 described in the transmission from the first communication device 410 to the second communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the first communication device 410. The transmit processor 468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 457, the stream is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a RF symbol stream before providing it to the antenna 452.

[0214] During transmission from the second communication device 450 to the first communication device 410, the functionality at the first communication device 410 is similar to the reception functionality at the second communication device 450 described for transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives RF signals via its corresponding antenna 420, converts the received RF signals into baseband signals, and provides the baseband signals to the multi-antenna receive processor 472 and the receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement L1 layer functionality. The controller / processor 475 implements L2 layer functionality. The controller / processor 475 may be associated with a memory 476 storing program codes and data. The memory 476 may be referred to as a computer-readable medium. During transmission from the second communication device 450 to the first communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0215] As an embodiment, the first node in the present application includes the second communication device 450 , and the second node in the present application includes the first communication device 410 .

[0216] As a sub-embodiment of the above embodiment, the first node is a user equipment, and the second node is a relay node.

[0217] As a sub-embodiment of the above embodiment, the first node is a user equipment, and the second node is a base station device.

[0218] As a sub-embodiment of the above embodiment, the first node is a relay node, and the second node is a base station device.

[0219] As a sub-embodiment of the above embodiment, the second communication device 450 includes: at least one controller / processor; the at least one controller / processor is responsible for HARQ operation.

[0220] As a sub-embodiment of the above embodiment, the first communication device 410 includes: at least one controller / processor; the at least one controller / processor is responsible for HARQ operation.

[0221] As a sub-embodiment of the above embodiment, the first communication device 410 includes: at least one controller / processor; the at least one controller / processor is responsible for using positive acknowledgment (ACK) and / or negative acknowledgment (NACK) protocol for error detection to support HARQ operation.

[0222] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 450 device at least: receives configuration information of at least a first SPS PDSCH; determines and sends a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by uplink and downlink TDD configuration signaling.

[0223] As a sub-embodiment of the above embodiment, the second communication device 450 corresponds to the first node in this application.

[0224] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating an action when executed by at least one processor, the action including: receiving configuration information of at least a first SPS PDSCH; determining and sending a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, a first type of PUCCH in a first type of time domain resource, the first type of time domain resource being a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0225] As a sub-embodiment of the above embodiment, the second communication device 450 corresponds to the first node in this application.

[0226] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends configuration information of at least a first SPS PDSCH; receives a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by uplink and downlink TDD configuration signaling.

[0227] As a sub-embodiment of the above embodiment, the first communication device 410 corresponds to the second node in this application.

[0228] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates actions when executed by at least one processor, the actions including: sending configuration information of at least a first SPS PDSCH; receiving a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein, the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, a first type of PUCCH is in a first type of time domain resource, and the first type of time domain resource is a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0229] As a sub-embodiment of the above embodiment, the first communication device 410 corresponds to the second node in this application.

[0230] As an embodiment, at least one of {the antenna 452, the receiver 454, the multi-antenna reception processor 458, the reception processor 456, the controller / processor 459, the memory 460, the data source 467} is used to receive the configuration information of at least the first SPS PDSCH in the present application.

[0231] As an embodiment, at least one of {the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475, the memory 476} is used to send the configuration information of the at least first SPS PDSCH in this application.

[0232] As an embodiment, at least one of {the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, the data source 467} is used to receive the uplink and downlink TDD configuration signaling in this application.

[0233] As an embodiment, at least one of {the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller / processor 475, the memory 476} is used to send the uplink and downlink TDD configuration signaling in this application.

[0234] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to determine the first HARQ-ACK bit block in the present application.

[0235] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to send the first HARQ-ACK bit block in the present application.

[0236] As an embodiment, at least one of {the antenna 420, the receiver 418, the multi-antenna receiving processor 472, the receiving processor 470, the controller / processor 475, the memory 476} is used to receive the first HARQ-ACK bit block in the present application.

[0237] Example 5

[0238] Embodiment 5 illustrates a signal transmission flow chart according to an embodiment of the present application, as shown in FIG5. In FIG5, the first node U1 and the second node U2 communicate with each other via an air interface.

[0239] The first node U1 receives configuration information of at least a first SPS PDSCH in step S511; determines a first HARQ-ACK bit block in step S511A; and sends the first HARQ-ACK bit block in step S512.

[0240] The second node U2 sends configuration information of at least the first SPS PDSCH in step S521; and receives the first HARQ-ACK bit block in step S522.

[0241] In embodiment 5, the first HARQ-ACK bit block includes at least one HARQ-ACK bit; the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources are time domain resources other than the symbols indicated as uplink by the uplink and downlink TDD configuration signaling; when the first condition set is met, the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH; the first condition set includes a first condition, and the first condition depends on the overlap between the first SPS PDSCH and the first type of PUCCH; the first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; one of the multiple SPS PDSCHs is: an SPS PDSCH overlapping with the first type of PUCCH PDSCH; the first type of PUCCH is configured by higher layer parameters; the first type of time domain resources includes symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0242] As a sub-embodiment of embodiment 5, when the first SPS PDSCH overlaps with the first type of PUCCH, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH.

[0243] As a sub-embodiment of embodiment 5, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0244] As an embodiment, the first node U1 is the first node in this application.

[0245] As an embodiment, the second node U2 is the second node in this application.

[0246] As an embodiment, the first node U1 is a UE.

[0247] As an embodiment, the second node U2 is a base station.

[0248] As an embodiment, the air interface between the second node U2 and the first node U1 is a Uu interface.

[0249] As an embodiment, the air interface between the second node U2 and the first node U1 includes a cellular link.

[0250] As an embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between a base station device and a user equipment.

[0251] As an embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between a satellite device and a user equipment.

[0252] As an embodiment, the air interface between the second node U2 and the first node U1 includes a wireless interface between a relay device and a user equipment.

[0253] As an embodiment, the first HARQ-ACK bit block does not include HARQ-ACK bits for the PDSCH scheduled by the DCI.

[0254] As an embodiment, the first HARQ-ACK bit block includes at least one HARQ-ACK bit for the PDSCH scheduled by the DCI.

[0255] As an embodiment, the first node U1 receives the uplink and downlink TDD configuration signaling.

[0256] As an embodiment, the second node U2 sends the uplink and downlink TDD configuration signaling.

[0257] As an embodiment, the uplink / downlink TDD configuration signaling is sent / received before the configuration information of at least the first SPS PDSCH.

[0258] As an embodiment, the sending / receiving of the uplink / downlink TDD configuration signaling is after the configuration information of the at least first SPS PDSCH.

[0259] As an embodiment, the first type of PUCCH is configured by the second node to the first node.

[0260] As an embodiment, the second node needs to make an assumption about how the first HARQ-ACK bit block is determined in order to perform reception of the first HARQ-ACK bit block.

[0261] As an embodiment, the first condition set is satisfied, the second node sends the first SPS PDSCH, and the first node receives the first SPS PDSCH.

[0262] As an embodiment, when the first node receives the first SPS PDSCH: the reception of the first SPS PDSCH is after the reception of the uplink and downlink TDD configuration signaling, after the reception of the configuration information of at least the first SPS PDSCH, and before the determination of the first HARQ-ACK bit block.

[0263] As an embodiment, the first condition set is satisfied, the second node independently determines whether to send or not send the first SPS PDSCH, and the first node attempts to receive the first SPS PDSCH.

[0264] As an embodiment, if the first condition set is not satisfied, the second node does not send the first SPS PDSCH, and the first node does not need to receive the first SPS PDSCH.

[0265] As an embodiment, the first condition set is not satisfied, the second node independently determines whether to send or not to send the first SPS PDSCH, and the first node does not need to receive the first SPS PDSCH.

[0266] As an embodiment, when any condition in the first condition set is not met, the first condition set is not met.

[0267] Example 6

[0268] Embodiment 6 illustrates a schematic diagram illustrating that the determination of the first HARQ-ACK bit block according to an embodiment of the present application depends on the overlap between the first SPS PDSCH and the first type of PUCCH, as shown in FIG6 .

[0269] In embodiment 6, when a first set of conditions is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first set of conditions includes a first condition, and the first condition depends on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0270] As an embodiment, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH only when a first set of conditions is met; the first set of conditions includes a first condition, and the first condition depends on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0271] As an embodiment, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH, including: the HARQ-ACK bits for the first SPS PDSCH are assigned to bits in the first HARQ-ACK bit block.

[0272] As an embodiment, the first condition set being satisfied means that each condition in the first condition set is satisfied.

[0273] As an embodiment, the first condition set only includes the first condition.

[0274] As an embodiment, the first condition set only includes multiple conditions.

[0275] As an embodiment, the first condition set further includes a second condition, wherein the second condition is: the HARQ-ACK information for the first SPS PDSCH is associated with the target PUCCH; and the first HARQ-ACK bit block is sent in the target PUCCH.

[0276] As an embodiment, the PUCCH associated with the HARQ-ACK information of the first SPS PDSCH is configurable.

[0277] As an embodiment, when the HARQ-ACK information for the first SPS PDSCH is configured to be multiplexed onto the target PUCCH, the HARQ-ACK information for the first SPS PDSCH is associated with the target PUCCH.

[0278] As an embodiment, the first condition includes: the first SPS PDSCH overlaps with at least 8 first-type PUCCHs.

[0279] As an embodiment, the first condition includes: the first SPS PDSCH is an SPS PDSCH other than at least one SPS PDSCH; and one SPS PDSCH among the at least one SPS PDSCH is an SPS PDSCH overlapping with the first type of PUCCH.

[0280] As an embodiment, the first condition includes: the first SPS PDSCH is an SPS PDSCH other than at least one SPS PDSCH; and one SPS PDSCH among the at least one SPS PDSCH is an SPS PDSCH that does not need to be received due to overlap with the first type of PUCCH.

[0281] As an embodiment, the at least one SPS PDSCH includes only one type of SPS PDSCH.

[0282] As an embodiment, the at least one SPS PDSCH includes multiple SPS PDSCHs.

[0283] As an embodiment, the first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; and one SPS PDSCH among the multiple SPS PDSCHs is an SPS PDSCH overlapping with the first type of PUCCH.

[0284] As an embodiment, the first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; and one SPS PDSCH among the multiple SPS PDSCHs is an SPS PDSCH that does not need to be received due to overlap with the first type of PUCCH.

[0285] As an embodiment, the statement that the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs means that the first SPS PDSCH does not belong to any SPS PDSCH among the multiple SPS PDSCHs.

[0286] As an embodiment, the first condition is met and the first node receives the first SPS PDSCH; or, the first condition is not met and the first node does not need to receive the first SPS PDSCH.

[0287] As an embodiment, when the first condition is met, the first SPS PDSCH is not an SPS PDSCH that overlaps with the first type of PUCCH.

[0288] As an embodiment, the multiple SPS PDSCHs do not need to be received.

[0289] As an embodiment, when the first condition set is not met, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH.

[0290] A non-limiting implementation of determining the first HARQ-ACK bit block is given below:

[0291] (1) Setup is the number of serving cells (serving cell(s)) configured for the first node; (2) setting is the number of SPS PDSCH configurations (SPS PDSCH configuration(s)) configured for the first node for serving cell c; (3) setting is the number of downlink time slots received by the SPS PDSCH on the serving cell c with HARQ-ACK information multiplexed on the target PUCCH; (4) set j = 0, where j is the index of the HARQ-ACK bit; (5) set c = 0, where c is the index of the serving cell (a lower one corresponds to a lower RRC index of the corresponding cell); (6) set s = 0, where s is the SPS PDSCH configuration index (a lower one corresponds to a lower RRC index of the corresponding SPS PDSCH configuration); (7) set n D =0, where n D Corresponding time slot index; (8) judging whether the first condition set is satisfied (in (8) and the following (9): the first SPS PDSCH is time slot n D , for SPS PDSCH configuration s, SPS PDSCH on serving cell c), if satisfied, execute (9) and (10), otherwise, skip (9) and jump directly to (10); (9) assign the HARQ-ACK bit for the first SPS PDSCH to a bit as the bit with index j in the first HARQ-ACK bit block, and execute j=j+1; (10) n D =n D +1; (11) Determine the loop condition Is it satisfied? If so, jump back to (8), otherwise execute (12); (12) s = s + 1; (13) Determine the loop condition Is it satisfied? If so, jump back to (7), otherwise execute (14); (14) c = c + 1; (15) Determine the loop condition Is it satisfied? If so, jump back to (6), otherwise end.

[0292] As an embodiment, the first node may generate the first HARQ-ACK bit block in other ways that have an equivalent effect to the above-mentioned determination method.

[0293] Example 7

[0294] Example 7 illustrates a schematic diagram of the first condition according to an embodiment of the present application, as shown in FIG7 .

[0295] In embodiment 7, the first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; and one SPS PDSCH among the multiple SPS PDSCHs is an SPS PDSCH that does not need to be received due to overlap with the first type of PUCCH.

[0296] As an embodiment, the benefits of the above method include: performing HARQ-ACK feedback for a valid SPS PDSCH, thereby improving HARQ-ACK feedback efficiency or robustness.

[0297] As an embodiment, the first condition is: the first SPS PDSCH is an SPS PDSCH other than the multiple SPS PDSCHs.

[0298] As an embodiment, in the present application, an SPS PDSCH overlaps / does not overlap with the first type of PUCCH means: the SPS PDSCH overlaps / does not overlap with the first type of PUCCH in the time domain.

[0299] As an embodiment, based on configuration, there are zero, one or more SPS PDSCHs belonging to one SPS PDSCH among the multiple SPS PDSCHs.

[0300] As an embodiment, the multiple SPS PDSCHs further include: an SPS PDSCH that does not need to be received among multiple overlapping SPS PDSCHs in any time slot.

[0301] As an embodiment, the plurality of SPS PDSCHs further include: an SPS PDSCH that does not need to be received based on a UE capability for the number of PDSCHs received in one time slot.

[0302] As an embodiment, the multiple SPS PDSCHs further include: an SPS PDSCH that does not need to be received due to overlapping with at least one symbol indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0303] As an embodiment, the multiple SPS PDSCHs further include: an SPS PDSCH overlapping with the first type CG PUSCH.

[0304] As an embodiment, the multiple SPS PDSCHs further include: an SPS PDSCH that does not need to be received due to overlapping with the first type CG PUSCH.

[0305] As an embodiment, when the first SPS PDSCH is not an SPS PDSCH other than the multiple SPS PDSCHs, the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0306] As an embodiment, the benefits of the above method include: effectively reducing HARQ-ACK feedback overhead.

[0307] Example 8

[0308] Embodiment 8 illustrates a schematic diagram of various SPS PDSCHs according to an embodiment of the present application, as shown in FIG8 .

[0309] In the eighth embodiment, the multiple SPS PDSCHs further include: an SPS PDSCH that does not need to be received among multiple overlapping SPS PDSCHs in any time slot.

[0310] As an embodiment, in this application, whether SPS PDSCHs overlap or not is viewed from the time domain.

[0311] As an embodiment, the multiple overlapping SPS PDSCHs in any time slot are for the same serving cell.

[0312] As an embodiment, the SPS PDSCH that needs to be received among the multiple overlapping SPS PDSCHs in any time slot is a survivor PDSCH (survivor PDSCH(s)) obtained by the following steps:

[0313] Step 0: Set j = 0, where j is the number of PDSCHs selected for decoding; Q represents the first PDSCH set;

[0314] Step 1: The first node receives the PDSCH with the lowest SPS configuration index (sps-ConfigIndex) in the Q, sets j=j+1; and regards the received PDSCH as a surviving PDSCH;

[0315] Step 2: Exclude the one surviving PDSCH in step 1 and any other PDSCHs (at least partially) overlapping with the one surviving PDSCH in step 1 from the Q;

[0316] Step 3: Repeat steps 1 and 2 until Q is an empty set.

[0317] As an embodiment, the SPS PDSCH that needs to be received among the multiple overlapping SPS PDSCHs in any time slot is determined by a first method, which is a method with an equivalent effect to the method of obtaining the SPS PDSCH that needs to be received among the multiple overlapping SPS PDSCHs in any time slot through steps 0 to 3 in Example 8.

[0318] As an embodiment, each PDSCH in the first PDSCH set is a PDSCH among the multiple overlapping SPS PDSCHs in the any time slot, at least after resolving the overlap with the symbols indicated as uplink by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the any time slot.

[0319] As an embodiment, each PDSCH in the first PDSCH set is a PDSCH among the multiple overlapping SPS PDSCHs in any time slot, at least after resolving the overlap with the first type of PUCCH.

[0320] As an embodiment, each PDSCH in the first PDSCH set is the PDSCH after at least resolving the overlap between the multiple overlapping SPS PDSCHs in any time slot and the symbols indicated as uplink by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in any time slot, and the first type of PUCCH.

[0321] As an embodiment, each PDSCH in the first PDSCH set is a PDSCH among the multiple overlapping SPS PDSCHs in any time slot, at least after resolving the overlap with the first type CG PUSCH.

[0322] As an embodiment, each PDSCH in the first PDSCH set is the PDSCH after resolving the overlap between the multiple overlapping SPS PDSCHs in any time slot, the symbols indicated as uplink by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in any time slot, the first type PUCCH, and the first type CG PUSCH.

[0323] As an embodiment, each PDSCH in the first PDSCH set is among the multiple overlapping SPS PDSCHs in any time slot, at least resolving the PDSCH that belongs to the first category of time domain resources in the time domain and occupies at least part of the frequency domain resources that do not belong to the first frequency band resources.

[0324] As an embodiment, each PDSCH in the first PDSCH set is among the multiple overlapping SPS PDSCHs in any time slot, at least excluding the PDSCH that belongs to the first category of time domain resources in the time domain and occupies at least part of the frequency domain resources that do not belong to the first frequency band resources.

[0325] As an embodiment, the first frequency band resources include at least one RB (Resource Block).

[0326] As an embodiment, the first frequency band resources include at least one PRB (Physical Resource Block).

[0327] As an embodiment, the first frequency band resources are continuous in the frequency domain.

[0328] As an embodiment, the first frequency band resources are discontinuous in the frequency domain.

[0329] As an embodiment, the first frequency band resources are configured for downlink transmission.

[0330] As an embodiment, the first frequency band resource includes a sub-band for downlink transmission within a BWP (BandWidth Part).

[0331] As an embodiment, the first frequency band resources are configured for full-duplex operation (sub-band non-overlapping or other types).

[0332] As an embodiment, the benefits of the above method include: facilitating support for full-duplex operation (sub-band non-overlapping or other types).

[0333] As an embodiment, the first frequency band resource is configured by RRC signaling.

[0334] As an embodiment, the first frequency band resource is configured by a MAC CE (Medium Access Control layer Control Element).

[0335] Example 9

[0336] Embodiment 9 illustrates a schematic diagram of various SPS PDSCHs according to an embodiment of the present application, as shown in FIG9 .

[0337] In the ninth embodiment, the plurality of SPS PDSCHs further include an SPS PDSCH that does not need to be received based on a UE capability for the number of PDSCHs received in one slot.

[0338] As an embodiment, the UE capability for the number of PDSCH receptions in a time slot is reported by the first node to the base station.

[0339] As an embodiment, in any time slot, when the number of PDSCHs exceeds the UE capability for the number of PDSCHs received in one time slot, the first node does not need to receive the PDSCHs in the any time slot.

[0340] As an embodiment, in a cell group, in the jth serving cell, j=0, 1, 2, ..., J-1, for time slot s j At any given time point, if the first data rate condition is not satisfied at the given time point, the first node does not need the time slot s in the j-th serving cell. j The first data rate condition is Where J is the number of configured serving cells belonging to a frequency range; for the j-th serving cell, M is the time slot s j The number of TBs (Transport Blocks) transmitted; is the time slot s in the jth serving cell j The duration of The calculation formula is where μ(j) is the time slot s in the j-th serving cellj The subcarrier spacing configuration is defined by the high-level parameter subcarrierSpacing; for the mth TB, V j,B The calculation formula is Where A is the number of bits in the m-th TB, C is the total number of code blocks (code block(s)) in the m-th TB, and C D is the number of code blocks scheduled for the m-th TB, It is a mathematical operation rounded down; the unit of DataRate is Mbps (Megabits per second), and the DataRate is calculated by summing the maximum data rates of all carriers in any signal band combination and feature set within the frequency range consistent with the configured serving cell. The calculation formula of the DataRate is shown in Section 4.1.2 of 3GPP TS 38.306.

[0341] As an embodiment, for the j-th serving cell, when the target condition is met and the target data rate condition is not met, the first node does not need to receive PDSCH in the j-th serving cell. The target condition includes any one of the sub-conditions: processingType2Enabled in the high-level parameter PDSCH-ServingCellConfig IE is configured for the j-th serving cell and is configured as "enable", or the first node in the j-th serving cell supports unicast (unicast) and MBS (Multicast and Broadcast Services) of FDM (Frequency Division Multiplexing), or at least one I for a PDSCH of unicast or multicast NHO >W. Among them I NHO is an MCS (Modulation and Coding Scheme) index, W is taken according to the MCS table used by the first node, when the first node uses Tables 5.1.3.1-1 and 5.1.3.1-3 in 3GPP TS 38.214, the value of W is 28, when the first node uses Table 5.1.3.1-2 in 3GPP TS 38.214, the value of W is 27, when the first node uses Table 5.1.3.4 in 3GPP TS 38.214, the value of W is 26. The target data rate condition is Where L is the number of symbols allocated to PDSCH; M is the number of TBs of PDSCH; is the duration of a time slot, the The calculation formula is Where μ is the subcarrier spacing configuration of PDSCH, which is defined by the high-level parameter subcarrierSpacing, is the number of symbols in a time slot; for the mth TB, V j,B The calculation formula is Where A is the number of bits in the m-th TB, C is the total number of code blocks (code block(s)) in the m-th TB, and C D is the number of code blocks scheduled for the m-th TB, It is a mathematical operation rounded down; the unit of DataRateCC is Mbps (Megabits per second). The DataRate is calculated based on the maximum data rate of a carrier in any signal frequency band combination and feature set consistent with the configured serving cell within the frequency range of the serving cell. The calculation formula of the DataRateCC is shown in Section 4.1.2 of 3GPP TS 38.306.

[0342] As an embodiment, when any one of the sub-conditions of the target condition is met, the target condition is met.

[0343] As an embodiment, when the target condition is not satisfied or the target data rate condition is satisfied, whether the first node needs to use the time slot s in the j-th serving cell j Receiving the PDSCH is related to whether the first data rate condition is met;

[0344] As an embodiment, the expression "whether the first node needs the time slot s in the j-th serving cell" j The term “receiving PDSCH on the jth serving cell is related to whether the first data rate condition is satisfied” means that when the first data rate condition is not satisfied, the first node does not need to receive the PDSCH in the time slot s in the jth serving cell. j Receive PDSCH.

[0345] As an embodiment, the above method has the following benefits: it is helpful to determine the number of PDSCH receptions in a time slot supported by the first node according to the restriction condition on the PDSCH data rate by the first node.

[0346] Example 10

[0347] Embodiment 10 illustrates a schematic diagram of various SPS PDSCHs according to an embodiment of the present application, as shown in FIG10 .

[0348] In the tenth embodiment, the multiple SPS PDSCHs further include: an SPS PDSCH that does not need to be received due to overlapping with a first type CG (Configured Grant) PUSCH.

[0349] As an embodiment, the benefits of the above method include: being conducive to ensuring the transmission of CG PUSCH.

[0350] As an embodiment, from the time domain perspective, any of the first-type CG PUSCHs is a CG PUSCH in the first-type time domain resources.

[0351] Example 11

[0352] Example 11 illustrates a schematic diagram of the first type of time domain resources according to an embodiment of the present application, as shown in Figure 11.

[0353] In embodiment 11, the first type of time domain resources includes symbols indicated as downlink by the uplink / downlink TDD configuration signaling and can be used for uplink transmission.

[0354] As an embodiment, the first type of time domain resources are symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0355] As an embodiment, the benefits of the above method include: being conducive to improving the utilization efficiency of the symbols indicated as downlink by the uplink and downlink TDD configuration signaling.

[0356] As an embodiment, the benefits of the above method include: improving uplink capacity.

[0357] As an embodiment, combined with the above features, the method disclosed in the present application is conducive to achieving a comprehensive enhancement effect of high configuration flexibility, high HARQ-ACK feedback performance, and high uplink capacity.

[0358] As an embodiment, the benefits of the above method include: it is helpful to ensure the effective transmission of the first type of PUCCH that occupies the symbols (symbol(s)) indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0359] As an embodiment, the benefits of the above method include: it is facilitating the application of the solution disclosed in this application in a full-duplex operating system, thereby improving system efficiency.

[0360] As an embodiment, a symbol indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission is indicated as downlink by the uplink / downlink TDD configuration signaling, and this symbol can be used for uplink transmission.

[0361] As an embodiment, the first type of time domain resources are symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0362] As an embodiment, the first type of time domain resources further includes flexible symbols (flexible symbol(s)).

[0363] As an embodiment, the first type of time domain resources includes symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission, and symbols indicated as flexible by the uplink and downlink TDD configuration signaling.

[0364] As an embodiment, there is at least one symbol indicated as downlink by the uplink and downlink TDD configuration signaling that does not belong to the first type of time domain resources.

[0365] As an embodiment, whether a symbol indicated as a downlink symbol by the uplink / downlink TDD configuration signaling can be used for uplink transmission is configurable.

[0366] As an embodiment, whether a downlink symbol indicated by the uplink / downlink TDD configuration signaling is usable for uplink transmission is configured by RRC signaling.

[0367] As an embodiment, the first type of time domain resources does not include symbols indicated as downlink by the uplink and downlink TDD configuration signaling and cannot be used for uplink transmission.

[0368] As an embodiment, whether a flexible symbol belongs to the first type of time domain resources is configurable.

[0369] As an embodiment, whether a flexible symbol belongs to the first category of time domain resources is configured by RRC signaling.

[0370] As an embodiment, the first type of time domain resources includes those configured for SBFD operation.

[0371] As an embodiment, the first type of time domain resources includes those configured for full-duplex operation.

[0372] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least PUCCH (Physical Uplink Control CHannel) transmission (transmission(s)).

[0373] As an embodiment, the expression "available for uplink transmission" means: available for at least PUSCH (Physical Uplink Shared CHannel) transmission (transmission(s)).

[0374] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least PUSCH and PUCCH transmission.

[0375] As an embodiment, combined with the above features, the method disclosed in this application is conducive to significantly improving the uplink data capacity of the system.

[0376] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least SRS (Sounding Reference Signal) transmission (transmission(s)).

[0377] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least one of PUSCH transmission, PUCCH transmission, PRACH (Physical Random Access CHannel) transmission (transmission(s)) and SRS transmission.

[0378] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least two of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0379] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least three of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0380] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0381] As an embodiment, the expression "available for uplink transmission" means: available for transmission of UL-SCH (Uplink Shared Channel(s)).

[0382] As an embodiment, the uplink / downlink TDD (Time Division Duplex) configuration signaling is signaling indicating the link direction of the symbol.

[0383] As an embodiment, the uplink and downlink TDD configuration signaling indicates at least one symbol as downlink.

[0384] As an embodiment, the uplink and downlink TDD configuration signaling indicates at least one symbol as uplink.

[0385] As an embodiment, the uplink and downlink TDD configuration signaling is RRC signaling.

[0386] As an embodiment, the benefits of the above method include: high reliability of signaling transmission.

[0387] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationCommon.

[0388] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationDedicated.

[0389] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0390] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0391] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0392] Example 12

[0393] Embodiment 12 illustrates a schematic diagram of the first type of PUCCH according to an embodiment of the present application, as shown in FIG12 .

[0394] In embodiment 12, the first type of PUCCH is configured by higher layer parameters.

[0395] As an embodiment, the higher layer includes an RRC layer.

[0396] As an embodiment, the higher layer includes a MAC layer.

[0397] As an embodiment, the first type of PUCCH is configured by RRC signaling.

[0398] As an embodiment, the first type of PUCCH is activated by MAC CE (Medium Access Control layer Control Element).

[0399] As an embodiment, the first type of PUCCH is configured by RRC signaling or activated by MAC CE.

[0400] As an embodiment, the first type of PUCCH is not activated by MAC CE.

[0401] As an embodiment, the first type of PUCCH is not triggered by DCI.

[0402] As an embodiment, the first type of PUCCH includes a PUCCH configured for periodic (aperiodic) CSI (Channel state information) reporting.

[0403] As an embodiment, the first type of PUCCH includes a PUCCH configured for semi-persistent CSI reporting.

[0404] As an embodiment, the first type of PUCCH includes a PUCCH configured for SR (Scheduling request) reporting.

[0405] Example 13

[0406] Embodiment 13 illustrates a schematic diagram illustrating a first node sending a first type PUCCH according to an embodiment of the present application, as shown in FIG13 .

[0407] In embodiment 13, the first SPS PDSCH overlaps with a first-type PUCCH, and the first node sends the first-type PUCCH overlapping with the first SPS PDSCH.

[0408] As an embodiment, the characteristics of the above method include: when the first SPS PDSCH overlaps with the first type of PUCCH, the transmission of the first type of PUCCH is prioritized; such characteristics are conducive to ensuring the transmission of UCI (Uplink control information) and improving the robustness of the system.

[0409] As an embodiment, sending a PUCCH means: sending UCI in the PUCCH.

[0410] Example 14

[0411] Embodiment 14 illustrates a structural block diagram of a processing device in a first node device, as shown in FIG14. In FIG14, the first node device processing device A00 includes a first receiver A01 and a first transmitter A02.

[0412] As an embodiment, the first node device A00 is a user equipment.

[0413] As an embodiment, the first node device A00 is a relay node.

[0414] As an embodiment, the first node device A00 is a vehicle-mounted communication device.

[0415] As an embodiment, the first node device A00 is a conventional user equipment.

[0416] As an embodiment, the first node device A00 is a UE with relevant configuration supporting full-duplex operation (non-overlapping sub-bands or other types).

[0417] As an embodiment, the first receiver A01 includes at least one of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0418] As an embodiment, the first receiver A01 includes at least the first five of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0419] As an embodiment, the first receiver A01 includes at least the first four of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0420] As an embodiment, the first receiver A01 includes at least the first three of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0421] As an embodiment, the first receiver A01 includes at least the first two of the antenna 452, receiver 454, multi-antenna receiving processor 458, receiving processor 456, controller / processor 459, memory 460 and data source 467 in Figure 4 of the present application.

[0422] As an embodiment, the first transmitter A02 includes at least one of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0423] As an embodiment, the first transmitter A02 includes at least the first five of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0424] As an embodiment, the first transmitter A02 includes at least the first four of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0425] As an embodiment, the first transmitter A02 includes at least the first three of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0426] As an embodiment, the first transmitter A02 includes at least the first two of the antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467 in FIG4 of the present application.

[0427] As an embodiment, the first receiver A01 receives configuration information of at least a first SPS PDSCH; the first transmitter A02 determines and sends a first HARQ-ACK bit block, and the first HARQ-ACK bit block includes at least one HARQ-ACK bit; wherein, the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in a first type of time domain resource, and the first type of time domain resource is a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0428] As an embodiment, when a first set of conditions is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first set of conditions includes a first condition, and the first condition depends on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0429] As an embodiment, the first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; and one SPS PDSCH among the multiple SPS PDSCHs is an SPS PDSCH overlapping with the first type of PUCCH.

[0430] As an embodiment, when the first SPS PDSCH overlaps with the first type of PUCCH, the first HARQ-ACK bit block does not include the HARQ-ACK bits for the first SPS PDSCH.

[0431] As an embodiment, the first type of PUCCH is configured by higher layer parameters.

[0432] As an embodiment, the first type of time domain resources includes symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0433] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0434] As an embodiment, the first receiver A01 receives configuration information of at least a first SPS PDSCH; the first transmitter A02 determines and sends a first HARQ-ACK bit block, and the first HARQ-ACK bit block includes at least one HARQ-ACK bit; wherein, the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in the first type of time domain resources, and the first type of time domain resources is a time domain resource other than the symbol indicated as uplink by the uplink and downlink TDD configuration signaling, and the first type of time domain resources includes the symbol indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission; when the first condition set is met, the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH; the first condition set includes a first condition, and the first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; an SPS among the multiple SPS PDSCHs The PDSCH is an SPS PDSCH that does not need to be received due to overlapping with the first-type PUCCH.

[0435] As a sub-embodiment of the above embodiment, when the first SPS PDSCH overlaps with the first type of PUCCH, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH.

[0436] As a sub-embodiment of the above embodiment, the first type of PUCCH is configured by higher layer parameters.

[0437] As a sub-embodiment of the above embodiment, when the first SPS PDSCH overlaps with the first type of PUCCH, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH; the first type of PUCCH is configured by higher layer parameters.

[0438] As a sub-embodiment of the above embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0439] Example 15

[0440] Embodiment 15 illustrates a structural block diagram of a processing device in a second node device, as shown in FIG15. In FIG15, the second node device processing device B00 includes a second transmitter B01 and a second receiver B02.

[0441] As an embodiment, the second node device B00 is a base station.

[0442] As an embodiment, the second node device B00 is a satellite device.

[0443] As an embodiment, the second node device B00 is a relay node.

[0444] As an embodiment, the second node device B00 is a base station supporting full-duplex operation (non-overlapping sub-bands or other types).

[0445] As an embodiment, the second node device B00 is a base station that only supports half-duplex operation.

[0446] As an embodiment, the second node device B00 is one of a test device, a test equipment, and a test instrument.

[0447] As an embodiment, the second transmitter B01 includes at least one of the antenna 420, transmitter 418, multi-antenna transmission processor 471, transmission processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0448] As an embodiment, the second transmitter B01 includes at least the first five of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0449] As an embodiment, the second transmitter B01 includes at least the first four of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0450] As an embodiment, the second transmitter B01 includes at least the first three of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0451] As an embodiment, the second transmitter B01 includes at least the first two of the antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0452] As an embodiment, the second receiver B02 includes at least one of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0453] As an embodiment, the second receiver B02 includes at least the first five of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0454] As an embodiment, the second receiver B02 includes at least the first four of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0455] As an embodiment, the second receiver B02 includes at least the first three of the antenna 420, receiver 418, multi-antenna receiving processor 472, receiving processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0456] As an embodiment, the second receiver B02 includes at least the first two of the antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475 and memory 476 in FIG. 4 of the present application.

[0457] As an embodiment, the second transmitter B01 sends configuration information of at least a first SPS PDSCH; the second receiver B02 receives a first HARQ-ACK bit block, and the first HARQ-ACK bit block includes at least one HARQ-ACK bit; wherein, the determination of the first HARQ-ACK bit block depends on the overlap between the first SPS PDSCH and the first type of PUCCH, and the first type of PUCCH is in a first type of time domain resource, and the first type of time domain resource is a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0458] As an embodiment, when a first set of conditions is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first set of conditions includes a first condition, and the first condition depends on the overlap between the first SPS PDSCH and the first type of PUCCH.

[0459] As an embodiment, the first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; and one SPS PDSCH among the multiple SPS PDSCHs is an SPS PDSCH overlapping with the first type of PUCCH.

[0460] As an embodiment, when the first SPS PDSCH overlaps with the first type of PUCCH, the first HARQ-ACK bit block does not include the HARQ-ACK bits for the first SPS PDSCH.

[0461] As an embodiment, the first type of PUCCH is configured by higher layer parameters.

[0462] As an embodiment, the first type of time domain resources includes symbols indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0463] As an embodiment, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0464] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software functional module. This application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in this application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, transportation vehicles, vehicles, RSUs, wireless sensors, internet cards, Internet of Things terminals, RFID (Radio Frequency Identification) terminals, NB-IoT (Narrow Band Internet of Things) terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system equipment in this application include but are not limited to macrocell base stations, microcell base stations, small cell base stations, home base stations, relay base stations, eNB (evolved Node B), gNB, TRP, GNSS (Global Navigation Satellite System), relay satellites, satellite base stations, aerial base stations, RSUs, drones, test equipment, such as transceivers or signaling testers that simulate some functions of base stations, and other wireless communication equipment.

[0465] Those skilled in the art will appreciate that the present invention may be implemented in other specific forms without departing from its core or essential characteristics. Therefore, the presently disclosed embodiments should be considered in all respects as illustrative and not restrictive. The scope of the invention is determined by the appended claims, not the foregoing description, and all modifications that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A first node used for wireless communication, characterized in that, Comprising: A first receiver that receives configuration information of at least a first SPS PDSCH; A first transmitter that determines and transmits a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; Wherein, the determination of the first HARQ-ACK bit block depends on the overlapping situation between the first SPS PDSCH and a first type of PUCCH, and one of the first type of PUCCH is in a first type of time-domain resource, and the first type of time-domain resource is a time-domain resource other than the symbols indicated as the uplink by the uplink-downlink TDD configuration signaling.

2. The first node according to claim 1, wherein When a first set of conditions is satisfied, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first set of conditions includes a first condition, and the first condition depends on the overlapping situation between the first SPS PDSCH and the first type of PUCCH.

3. The first node according to claim 2, characterized in that, The first condition includes: the first SPS PDSCH is an SPS PDSCH other than multiple SPS PDSCHs; one of the multiple SPS PDSCHs is an SPS PDSCH that overlaps with the first type of PUCCH.

4. The first node according to any one of claims 1 to 3, characterized in that, When the first SPS PDSCH overlaps with the first type of PUCCH, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH.

5. The first node according to any one of claims 1 to 4, characterized in that The first type of PUCCH is configured by higher layer parameters.

6. The first node according to any one of claims 1 to 5, characterized in that, The first type of time-domain resource includes symbols indicated as the downlink by the uplink-downlink TDD configuration signaling and available for uplink transmission.

7. The first node according to any one of claims 1 to 6, characterized in that The uplink-downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

8. A second node used for wireless communication, characterized in that, Comprising: A second transmitter that transmits configuration information of at least a first SPS PDSCH; A second receiver that receives a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; Wherein, the determination of the first HARQ-ACK bit block depends on the overlapping situation between the first SPS PDSCH and a first type of PUCCH, and one of the first type of PUCCH is in a first type of time-domain resource, and the first type of time-domain resource is a time-domain resource other than the symbols indicated as the uplink by the uplink-downlink TDD configuration signaling.

9. A method used in a first node for wireless communication, characterized in that, Comprising: Receiving configuration information of at least a first SPS PDSCH; Determining and transmitting a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; Among them, the determination of the first HARQ-ACK bit block depends on the overlapping situation between the first SPS PDSCH and the first type of PUCCH. One of the first type of PUCCHs is in the first type of time-domain resources, and the first type of time-domain resources are time-domain resources other than the symbols indicated as the uplink by the uplink-downlink TDD configuration signaling.

10. A method in a second node for use in wireless communication, characterized in that, including: transmitting at least the configuration information of the first SPS PDSCH; receiving a first HARQ-ACK bit block, the first HARQ-ACK bit block including at least one HARQ-ACK bit; Among them, the determination of the first HARQ-ACK bit block depends on the overlapping situation between the first SPS PDSCH and the first type of PUCCH. One of the first type of PUCCHs is in the first type of time-domain resources, and the first type of time-domain resources are time-domain resources other than the symbols indicated as the uplink by the uplink-downlink TDD configuration signaling.

Images