Method and device used in node for wireless communication

Abstract

The present application discloses a method and device used in a node for wireless communication. A first receiver receives first RRC signaling, wherein the first RRC signaling comprises at least configuration information of a first SPS PDSCH; a first transmitter sends a first HARQ-ACK bit block on a first PUCCH, wherein the first HARQ-ACK bit block comprises at least one HARQ-ACK bit; whether the first HARQ-ACK bit block comprises the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps a configured grant PUSCH in a first-type symbol, and the first-type symbol comprises a symbol which is indicated as a downlink symbol by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

Description

A method and device used in a node for wireless communication Technical Field

[0001] 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

[0002] 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.

[0003] Configured Granted (CG) and Semi-Persistent Scheduling (SPS) are used for uplink and downlink transmissions, respectively, and are two effective mechanisms in NR to reduce signaling overhead, transmission latency, and power consumption.

[0004] HARQ (Hybrid Automatic Repeat reQuest) is an effective mechanism to improve transmission reliability and reduce transmission delay in NR.

[0005] Summary of the Invention

[0006] When a new symbol type is introduced to support a communication mode, and this new symbol type supports the configuration of overlapping SPS PDSCH (Physical Downlink Shared Channel) and the configuration of granted PUSCH (Physical Uplink Shared Channel), how to improve the HARQ-ACK (Hybrid Automatic Repeat reQuest-ACKnowledgement) feedback for SPS PDSCH 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 mode, 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 mode) 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.

[0007] 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.

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

[0009] receiving first RRC signaling, where the first RRC signaling includes configuration information of at least a first SPS PDSCH;

[0010] Sending a first HARQ-ACK bit block on a first PUCCH, where the first HARQ-ACK bit block includes at least one HARQ-ACK bit;

[0011] Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0013] As an embodiment, the problem to be solved by the present application includes: in a scenario supporting the configuration of overlapping SPS PDSCH and configuration of granted PUSCH on the first type of symbols, how to improve the resource utilization efficiency of PUCCH used to send HARQ-ACK information for SPS PDSCH.

[0014] As an embodiment, the problem to be solved by the present application includes: how to improve the reporting of HARQ-ACK information for SPS PDSCH in a scenario supporting the configuration of overlapping SPS PDSCH and configuration of granted PUSCH on the first type of symbols.

[0015] As an embodiment, the above method has the following benefits: supporting the configuration of overlapping SPS PDSCHs and configuration of granted PUSCHs on the first type of symbols, thereby improving resource utilization efficiency.

[0016] As an embodiment, the benefits of the above method include: improving configuration or scheduling flexibility.

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

[0018] As an embodiment, the above method has the following benefits: facilitating support for full-duplex operation (non-overlapping sub-bands or other types) at least on the base station side.

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

[0020] When the first SPS PDSCH does not need to be received due to overlapping with the PUSCH configured with grant in the first type of symbols, the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0021] As an embodiment, the benefits of the above method include: improving the reporting performance of HARQ-ACK information for SPS PDSCH.

[0022] As an embodiment, the benefits of the above method include: saving HARQ-ACK feedback overhead.

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

[0024] When a first condition is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with the configured granted PUSCH in the first type of symbols.

[0025] As an embodiment, the benefits of the above method include: improving the reporting performance of HARQ-ACK information for SPS PDSCH.

[0026] As an embodiment, the benefits of the above method include: saving HARQ-ACK feedback overhead.

[0027] As an embodiment, the advantages of the above method include: the workload required for standardization is small.

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

[0029] The first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlapping with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCHs received in a time slot, and 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.

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

[0031] Second RRC signaling is received; the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

[0032] As an embodiment, the benefits of the above method include: improving configuration flexibility and facilitating optimization of uplink and downlink resource usage.

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

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

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

[0036] The first node reports HARQ-ACK information only for the SPS PDSCH in the first PUCCH.

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

[0038] Sending first RRC signaling, where the first RRC signaling includes at least configuration information of a first SPS PDSCH;

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

[0040] Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0042] When the first SPS PDSCH does not need to be received due to overlapping with the PUSCH configured with grant in the first type of symbols, the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

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

[0044] When a first condition is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with the configured granted PUSCH in the first type of symbols.

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

[0046] The first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlapping with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCHs received in a time slot, and 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.

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

[0048] Sending a second RRC signaling; the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

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

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

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

[0052] The first PUCCH only carries HARQ-ACK information for the SPS PDSCH.

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

[0054] A first receiver receives first RRC signaling, where the first RRC signaling includes at least configuration information of a first SPS PDSCH;

[0055] A first transmitter sends a first HARQ-ACK bit block on a first PUCCH, where the first HARQ-ACK bit block includes at least one HARQ-ACK bit.

[0056] Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0058] A second transmitter sends a first RRC signaling, where the first RRC signaling includes at least configuration information of a first SPS PDSCH;

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

[0060] Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] 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:

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

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

[0064] 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;

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

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

[0067] FIG6 shows a schematic diagram illustrating a first type of symbol according to an embodiment of the present application;

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

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

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

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

[0072] FIG11 shows a schematic diagram illustrating a second RRC signaling according to an embodiment of the present application;

[0073] FIG12 shows a flowchart of generating a first HARQ-ACK bit block according to one embodiment of the present application;

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

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

[0076] 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.

[0077] Example 1

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

[0079] In embodiment 1, the first node in the present application receives a first RRC signaling in step 101; and sends a first HARQ-ACK bit block on a first PUCCH in step 102.

[0080] In embodiment 1, the first RRC signaling includes configuration information of at least the first SPS PDSCH; the first HARQ-ACK bit block includes at least one HARQ-ACK bit; whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured PUSCH in the first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0081] As an embodiment, the first RRC signaling includes an RRC message (RRC message(s)).

[0082] As an embodiment, the first RRC signaling is an IE.

[0083] As an embodiment, the first RRC signaling includes at least one field in at least one IE (Information Element).

[0084] As an embodiment, the first RRC signaling is a field in an IE.

[0085] As an embodiment, the first RRC signaling is an RRC IE.

[0086] As an embodiment, the first RRC signaling includes an RRC parameter.

[0087] As an embodiment, the first RRC signaling is used to configure SPS (Semi-Persistent Scheduling) PDSCH.

[0088] As an embodiment, an SPS PDSCH is a PDSCH without a corresponding PDCCH (Physical Downlink Control CHannel) transmission.

[0089] As an embodiment, the first RRC signaling is SPS-Config.

[0090] As an embodiment, the first RRC signaling includes at least one SPS-Config.

[0091] As an embodiment, the first RRC signaling includes multiple SPS-Configs respectively configured with different SPS PDSCH configuration indexes.

[0092] 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 first PUCCH on the first service cell.

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

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

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

[0096] 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0109] 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.

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

[0111] 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.

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

[0113] 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.

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

[0115] 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.

[0116] 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 on the first PUCCH (Physical Uplink Control CHannel).

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

[0118] As an embodiment, the first HARQ-ACK bit block is sent on the first 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.

[0119] As an embodiment, at least the first HARQ-ACK bit block is sent on the first PUCCH after CRC addition, 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.

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

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

[0122] As an embodiment, the first HARQ-ACK bit block includes only one HARQ-ACK bit.

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

[0124] 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.

[0125] 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.

[0126] 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 downlink time slots respectively.

[0127] 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.

[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 the same SPS PDSCH configuration.

[0129] 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).

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

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

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

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

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

[0135] 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.

[0136] As an embodiment, whether the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH depends on whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbols.

[0137] As an embodiment, when the first SPS PDSCH is not received due to overlapping with the configured granted PUSCH in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bits for the first SPS PDSCH.

[0138] As an embodiment, when an SPS PDSCH needs to be received, the first node receives the SPS PDSCH; when an SPS PDSCH does not need to be received, the first node does not receive the SPS PDSCH.

[0139] As an embodiment, when the first SPS PDSCH is not in the first type of symbol, or the first SPS PDSCH is in the first type of symbol and has no time domain overlap with the configured PUSCH, the first SPS PDSCH does not overlap with the configured PUSCH in the first type of symbol.

[0140] As an embodiment, when the first SPS PDSCH does not occupy the first type of symbols in the time domain, the first SPS PDSCH does not overlap with the configured granted PUSCH in the first type of symbols.

[0141] As an embodiment, when the first SPS PDSCH occupies at least one first-category symbol in the time domain and the first SPS PDSCH has no time-domain overlap with the configured granted PUSCH in each of the occupied first-category symbols, the first SPS PDSCH does not overlap with the configured granted PUSCH in the first-category symbol.

[0142] As an embodiment, when the first SPS PDSCH occupies at least one first-category symbol in the time domain and the first SPS PDSCH has time domain overlap with the configured granted PUSCH in the at least one first-category symbol occupied, the first SPS PDSCH overlaps with the configured granted PUSCH in the first-category symbol.

[0143] As an embodiment, when the first SPS PDSCH and a configured and granted PUSCH occupy at least one same first-category symbol, the first SPS PDSCH and the configured and granted PUSCH overlap on the first-category symbol.

[0144] As an embodiment, when at least part of the time domain resources included in a first-category symbol is occupied by both the first SPS PDSCH and a configuration grant, the first SPS PDSCH and the PUSCH of the configuration grant overlap on the first-category symbol.

[0145] As an embodiment, when the time domain resources allocated to an SPS PDSCH include one symbol, the SPS PDSCH occupies the symbol in the time domain.

[0146] As an embodiment, when the time domain resources occupied by an SPS PDSCH include one symbol, the SPS PDSCH occupies this symbol in the time domain.

[0147] As an embodiment, when the time domain resources allocated to an SPS PDSCH overlap with a symbol, the SPS PDSCH occupies the symbol in the time domain.

[0148] As an embodiment, when an SPS PDSCH overlaps with a symbol in the time domain, the SPS PDSCH occupies the symbol in the time domain.

[0149] As an embodiment, when the time domain resources allocated to a configured and granted PUSCH include one symbol, the configured and granted PUSCH occupies this symbol in the time domain.

[0150] As an embodiment, when the time domain resources occupied by a PUSCH granted by a configuration include one symbol, the PUSCH granted by this configuration occupies this symbol in the time domain.

[0151] As an embodiment, when the time domain resources allocated to a configured and granted PUSCH overlap with a symbol, the configured and granted PUSCH occupies this symbol in the time domain.

[0152] As an embodiment, when a PUSCH granted by a configuration overlaps with a symbol in the time domain, the PUSCH granted by the configuration occupies the symbol in the time domain.

[0153] As an embodiment, the PUSCH granted by the configuration in this application and the first PDSCH are on the same serving cell.

[0154] As an embodiment, the PUSCH granted by the configuration in this application and the first PDSCH are on the same serving cell or different serving cells.

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

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

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

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

[0159] As an embodiment, in the present application, the overlap between the first SPS PDSCH and the configured granted PUSCH refers to: the overlap between the first SPS PDSCH and the configured granted PUSCH in the time domain.

[0160] As an embodiment, when the first SPS PDSCH does not need to be received due to overlapping with the dynamically scheduled PUSCH in the first type of symbols, the first HARQ-ACK bit block may include HARQ-ACK bits for the first SPS PDSCH.

[0161] As an embodiment, the benefits of the above method include: avoiding / alleviating the impact of the dynamically scheduled PUSCH on the generation of the first HARQ-ACK bit block, and improving the robustness of the HARQ-ACK feedback.

[0162] As an embodiment, when the first SPS PDSCH does not need to be received because it overlaps with the configured granted PUSCH in the first category of symbols, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; otherwise, the first HARQ-ACK bit block does not include HARQ-ACK bits for the first SPS PDSCH.

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

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

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

[0166] Example 2

[0167] 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, an HSS (Home Subscriber Server) / 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.

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

[0169] As an embodiment, the UE 201 is a user equipment (UE).

[0170] As an embodiment, the UE 201 is a base station (BS).

[0171] As an embodiment, the UE 201 is a relay device.

[0172] As an embodiment, the UE 201 is a gateway device.

[0173] As an embodiment, the node 203 corresponds to the second node in this application.

[0174] As an embodiment, the node 203 is a base station device.

[0175] As an embodiment, the node 203 is a user equipment.

[0176] As an embodiment, the node 203 is a relay device.

[0177] As an embodiment, the node 203 is a gateway device.

[0178] Typically, the UE 201 is a user equipment, and the node 203 is a base station device.

[0179] Typically, the UE 201 is a user equipment, and the node 203 is a user equipment.

[0180] Typically, the UE 201 is a base station device, and the node 203 is a base station device.

[0181] As an embodiment, the user equipment supports a more flexible duplex mode or a full-duplex mode (non-overlapping sub-bands or other types).

[0182] As an embodiment, the user equipment supports transmission of a non-terrestrial network (NTN).

[0183] As an embodiment, the user equipment supports transmission via a terrestrial network (Terrestrial Network).

[0184] As an embodiment, the user equipment includes an aircraft.

[0185] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0186] As an embodiment, the user equipment includes a vessel.

[0187] As an embodiment, the user equipment includes an Internet of Things terminal.

[0188] As an embodiment, the user equipment includes a terminal of the Industrial Internet of Things.

[0189] As an embodiment, the user equipment includes a device that supports low-latency and high-reliability transmission.

[0190] As an embodiment, the user equipment includes a test device.

[0191] As an embodiment, the user equipment includes a signaling tester.

[0192] As an embodiment, the user equipment includes an IAB (Integrated Access and Backhaul)-MT.

[0193] As an embodiment, the base station device supports a more flexible duplex mode or a full-duplex mode (non-overlapping sub-bands or other types).

[0194] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0195] As an embodiment, the base station device supports transmission of a terrestrial network.

[0196] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0197] As an embodiment, the base station device includes a Node B (NB).

[0198] As an embodiment, the base station device includes a gNB.

[0199] As an embodiment, the base station device includes an eNB.

[0200] As an embodiment, the base station device includes ng-eNB.

[0201] As an embodiment, the base station device includes an en-gNB.

[0202] As an embodiment, the base station device includes a CU (Centralized Unit).

[0203] As an embodiment, the base station device includes a DU (Distributed Unit).

[0204] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

[0205] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.

[0206] As an embodiment, the base station device includes a micro cell base station.

[0207] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0208] As an embodiment, the base station device includes a home base station (Femtocell).

[0209] As an embodiment, the base station device includes a flying platform device.

[0210] As an embodiment, the base station device includes a satellite device.

[0211] As an embodiment, the base station device includes a testing device.

[0212] As an embodiment, the base station equipment includes a signaling tester.

[0213] As an embodiment, the base station device includes a gateway device.

[0214] As an embodiment, the base station device includes an IAB-node.

[0215] As an embodiment, the base station device includes an IAB-donor.

[0216] As an embodiment, the base station device includes an IAB-donor-CU.

[0217] As an embodiment, the base station device includes an IAB-donor-DU.

[0218] As an embodiment, the base station device includes an IAB-DU.

[0219] As an embodiment, the base station device includes an IAB-MT.

[0220] Example 3

[0221] 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. L2305 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 inter-zone mobility support for 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.).

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

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

[0224] As an embodiment, the first RRC signaling in the present application is generated in the RRC sublayer 306.

[0225] As an embodiment, the second RRC signaling in the present application is generated in the RRC sublayer 306.

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

[0227] As an embodiment, the first PUCCH in this application is generated by the PHY301.

[0228] As an embodiment, the PUSCH granted by the configuration in this application is generated in the PHY351.

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

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

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

[0232] Example 4

[0233] 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.

[0234] 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 .

[0235] 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 .

[0236] 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 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 and non-codebook-based precoding, and beamforming 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 (IFFT) to generate a physical channel carrying 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.

[0237] 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.

[0238] 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.

[0239] 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.

[0240] 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 .

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

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

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

[0244] 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.

[0245] 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.

[0246] 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.

[0247] 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 a first RRC signaling, the first RRC signaling including configuration information of at least a first SPS PDSCH; sends a first HARQ-ACK bit block on a first PUCCH, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein, whether the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in a first type of symbol, the first type of symbol including symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission.

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

[0249] 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 a first RRC signaling, the first RRC signaling including configuration information of at least a first SPS PDSCH; sending a first HARQ-ACK bit block on a first PUCCH, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein, whether the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in a first type of symbol, the first type of symbol including symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0251] 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 a first RRC signaling, the first RRC signaling including configuration information of at least a first SPS PDSCH; receives a first HARQ-ACK bit block on a first PUCCH, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein, whether the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with a configured granted PUSCH in a first type of symbol, the first type of symbol including symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission.

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

[0253] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: sending a first RRC signaling, the first RRC signaling including configuration information of at least a first SPS PDSCH; receiving a first HARQ-ACK bit block on a first PUCCH, the first HARQ-ACK bit block including at least one HARQ-ACK bit; wherein, whether the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in a first type of symbol, the first type of symbol including symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0255] 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 first RRC signaling in this application.

[0256] 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 first RRC signaling in this application.

[0257] 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 second RRC signaling in the present application.

[0258] 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 second RRC signaling in this application.

[0259] 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 on the first PUCCH in the present application.

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

[0261] Example 5

[0262] Example 5 illustrates a signal transmission flow chart according to one embodiment of the present application, as shown in Figure 5 . In Figure 5 , communication between the first node U1 and the second node U2 occurs via an air interface. In Figure 5 , the steps within the dashed box F1 are optional. It should be noted that the order in this example does not limit the signal transmission sequence and implementation order in this application.

[0263] The first node U1 receives the first RRC signaling in step S511; receives the second RRC signaling in step S51A; and sends the first HARQ-ACK bit block on the first PUCCH in step S512.

[0264] The second node U2 sends a first RRC signaling in step S521; sends a second RRC signaling in step S52A; and receives a first HARQ-ACK bit block on the first PUCCH in step S522.

[0265] In embodiment 5, the first RRC signaling includes configuration information of at least a first SPS PDSCH; the first HARQ-ACK bit block includes at least one HARQ-ACK bit, whether the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbol, the first type of symbol includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated; when the first condition is met, the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with the configured granted PUSCH in the first type of symbol; when the first SPS When the PDSCH does not need to be received because it overlaps with the PUSCH configured with grant in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

[0266] As a sub-embodiment of Example 5, the first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCHs received in a time slot, and an SPS PDSCH that does not need to be received due to overlap with at least one symbol indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0267] As a sub-embodiment of embodiment 5, the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

[0268] As a sub-embodiment of embodiment 5, the first node reports HARQ-ACK information only for the SPS PDSCH in the first PUCCH.

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

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

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

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

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

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

[0275] 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.

[0276] 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.

[0277] 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.

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

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

[0280] As an embodiment, in the first HARQ-ACK bit block, the HARQ-ACK bits for the SPS PDSCH are sorted after the HARQ-ACK bits for the PDSCH scheduled by the DCI.

[0281] As an embodiment, the first PUCCH also carries HARQ-ACK information for the PDSCH scheduled by the DCI.

[0282] As an embodiment, for the HARQ-ACK bits sent on the first PUCCH: the HARQ-ACK bits for the SPS PDSCH are ordered after the HARQ-ACK bits for the PDSCH scheduled by the DCI.

[0283] As an embodiment, a HARQ-ACK bit in the present application is a HARQ-ACK information bit.

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

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

[0286] As an embodiment, the uplink / downlink TDD configuration signaling is sent / received before the first RRC signaling.

[0287] As an embodiment, at least a portion of the uplink and downlink TDD configuration signaling is sent / received after the first RRC signaling.

[0288] As an embodiment, the steps in the dashed box F1 in FIG. 5 exist.

[0289] As an embodiment, the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

[0290] As an embodiment, the second RRC signaling is sent / received before the first RRC signaling.

[0291] As an embodiment, the second RRC signaling is sent / received after the first RRC signaling.

[0292] As an embodiment, the second RRC signaling and the first RRC signaling are sent / received together.

[0293] As an embodiment, the uplink / downlink TDD configuration signaling is sent / received before the second RRC signaling.

[0294] As an embodiment, at least a portion of the uplink and downlink TDD configuration signaling is sent / received after the second RRC signaling.

[0295] As an embodiment, the steps in the dotted box F1 in FIG. 5 do not exist.

[0296] Example 6

[0297] Example 6 illustrates a schematic diagram of the first type of symbols according to an embodiment of the present application, as shown in FIG6 .

[0298] In embodiment 6, the first type of symbols includes symbols indicated as downlink symbols by uplink / downlink TDD configuration signaling and usable for uplink transmission.

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

[0300] As an embodiment, the uplink and downlink TDD configuration signaling includes higher layer signaling.

[0301] As an embodiment, the uplink and downlink TDD configuration signaling includes semi-static signaling.

[0302] As an embodiment, the uplink and downlink TDD configuration signaling includes cell common signaling.

[0303] As an embodiment, the uplink and downlink TDD configuration signaling includes UE group common signaling.

[0304] As an embodiment, the uplink and downlink TDD configuration signaling includes UE-specific signaling.

[0305] As an embodiment, the link direction configuration configured by the uplink and downlink TDD configuration signaling is applicable to the entire frequency band occupied by the serving cell.

[0306] As an embodiment, the link direction configuration configured by the uplink and downlink TDD configuration signaling is applicable to the entire carrier to which it belongs.

[0307] As an embodiment, the uplink and downlink TDD configuration signaling includes RRC signaling.

[0308] As an embodiment, the uplink and downlink TDD configuration signaling includes one or more RRC IEs.

[0309] As an embodiment, the uplink and downlink TDD configuration signaling includes multiple RRC IEs.

[0310] As an embodiment, the uplink and downlink TDD configuration signaling includes one or more fields of each RRC IE in multiple RRC IEs.

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

[0312] As an embodiment, the uplink and downlink TDD configuration signaling is one or more fields in an RRC IE.

[0313] As an embodiment, the uplink and downlink TDD configuration signaling is signaling indicating the link direction of the symbol.

[0314] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationCommon, and the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission are the first type of symbols.

[0315] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationCommon but available for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0316] As an embodiment, the uplink and downlink TDD configuration signaling is tdd-UL-DL-ConfigurationDedicated, and the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission are the first type of symbols.

[0317] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationDedicated but available for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0318] As an embodiment, the uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission are the first type of symbols.

[0319] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated but can be used for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0320] As an embodiment, any of the first-category symbols are symbols that can be used for uplink transmission.

[0321] As an embodiment, the expression "can be used for uplink transmission" means: can be used for at least PUSCH (Physical Uplink Shared CHannel) transmission.

[0322] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission and PUCCH (Physical Uplink Control CHannel) transmission.

[0323] As an embodiment, the expression "can be used for uplink transmission" means: can be used for PUSCH transmission, PUCCH transmission, and SRS (Sounding Reference Signal) transmission.

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

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

[0326] As an embodiment, the first symbol is a symbol indicated as a downlink symbol by the uplink and downlink TDD configuration signaling; if the first symbol can be used for uplink transmission, the first symbol is the first type of symbol; otherwise, the first symbol is not the first type of symbol.

[0327] As an embodiment, the symbols indicated as uplink symbols by the uplink and downlink TDD configuration signaling are not the first type of symbols.

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

[0329] As an embodiment, there is at least one symbol determined as a flexible symbol by uplink and downlink TDD configuration signaling and belongs to the first category of symbols.

[0330] As an embodiment, whether a symbol determined as a flexible symbol by the uplink / downlink TDD configuration signaling is the first type of symbol is indicated by a first information block.

[0331] As an embodiment, the first information block is carried by higher layer signaling.

[0332] As an embodiment, the first information block is carried by RRC (Radio Resource Control) signaling.

[0333] As an embodiment, the first information block includes information in at least one RRC IE (Information Element).

[0334] As an embodiment, the first information block includes part or all of the fields included in an RRC IE.

[0335] As an embodiment, the first information block includes part or all of the fields included in each RRC IE in multiple RRC IEs.

[0336] As an embodiment, the first information block includes part or all of the fields included in a SIB (System Information Block).

[0337] As an embodiment, the first information block includes part or all of the fields included in the MIB (Master Information Block).

[0338] As an embodiment, the first information block includes part or all of the fields included in SIB1 (System Information Block 1).

[0339] As an embodiment, the first information block includes part or all of the fields included in RMSI (Remaining Minimum System Information).

[0340] As an embodiment, the first information block is cell-common.

[0341] As an embodiment, the first information block is cell-specific.

[0342] As an embodiment, the first information block is group-common.

[0343] As an embodiment, the first information block is user equipment (UE)-dedicated.

[0344] As an embodiment, the first information block is configured per subband.

[0345] As an embodiment, the first information block is configured per BWP (BandWidth Part).

[0346] As an embodiment, the name of the RRC signaling carrying the first information block includes "tdd".

[0347] As an embodiment, the name of the RRC signaling carrying the first information block includes "DL".

[0348] As an embodiment, the name of the RRC signaling carrying the first information block includes "UL".

[0349] As an embodiment, the name of the RRC signaling carrying the first information block includes "Config".

[0350] As an embodiment, the name of the RRC signaling carrying the first information block includes "SBFD".

[0351] As an embodiment, the name of the RRC signaling carrying the first information block includes "subband".

[0352] As an embodiment, the name of the RRC signaling carrying the first information block includes "duplex".

[0353] As an embodiment, the first information block is carried by a MAC CE (Medium Access Control layer Control Element).

[0354] As an embodiment, the first information block includes information in at least one MAC CE.

[0355] As an embodiment, the first information block is carried by dynamic signaling.

[0356] As an embodiment, the first information block is carried by physical layer signaling.

[0357] As an embodiment, the first information block is carried by DCI (Downlink Control Information).

[0358] As an embodiment, the first information block includes information in at least one RRC IE and information in at least one DCI.

[0359] As an embodiment, the first information block includes part or all of the fields in a DCI format.

[0360] As an embodiment, the first information block includes part or all of the fields in DCI format 2_X, where X is a non-negative integer.

[0361] As an embodiment, the first information block includes part or all of the fields in DCI format 2_8.

[0362] As an embodiment, the first information block is used to configure SBFD (SubBand non-overlapping Full Duplex) time slots or symbols.

[0363] As an embodiment, the first information block is used to configure a time slot or symbol supporting full duplex.

[0364] As an embodiment, whether the symbol used for SS / PBCH block (SS / PBCH block, synchronization signal and physical broadcast channel block) reception is the first type of symbol is configured by the first information block.

[0365] As an embodiment, the above method has the following benefits: it is helpful to ensure the reception performance of the SS / PBCH block through reasonable configuration.

[0366] As an embodiment, the symbols used for SS / PBCH block (synchronization signal and physical broadcast channel block) reception are not the first type of symbols.

[0367] As an embodiment, the first information block is received before the uplink and downlink TDD configuration signaling.

[0368] As an embodiment, the first information block is received after the uplink and downlink TDD configuration signaling.

[0369] As an embodiment, the first information block and the uplink and downlink TDD configuration signaling are received simultaneously.

[0370] As an embodiment, there is at least one symbol determined as a flexible symbol by uplink and downlink TDD configuration signaling that does not belong to the first category of symbols.

[0371] Example 7

[0372] Embodiment 7 illustrates a schematic diagram of various SPS PDSCHs according to an embodiment of the present application, as shown in FIG7 .

[0373] In embodiment 7, the multiple PDSCHs include at least an SPS PDSCH that does not need to be received due to overlapping with a PUSCH configured for grant in the first type of symbols.

[0374] As an embodiment, the multiple PDSCHs include at least an SPS PDSCH that overlaps with a configured PUSCH in the first type of symbols.

[0375] As an embodiment, the priority of any SPS PDSCH that overlaps with the configured PUSCH in the first type of symbols is the same as the priority of the configured PUSCH.

[0376] As an embodiment, when the first SPS PDSCH overlaps with the configured granted PUSCH in at least one of the first category symbols: the first condition is not met, the first SPS PDSCH does not need to be received by the first node, and the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0377] As an embodiment, the above method has the following benefits: in a scenario where an SPS PDSCH with the same priority and a configured PUSCH overlap in the first type of symbols, transmission of the configured PUSCH is ensured, thereby improving uplink transmission efficiency.

[0378] As an embodiment, the benefits of the above method include: in the scenario where SPS PDSCH with the same priority and the configured granted PUSCH overlap in the first type of symbols, the feedback efficiency of HARQ-ACK is improved and the feedback overhead of HARQ-ACK is saved.

[0379] As an embodiment, when the first SPS PDSCH overlaps with the configured PUSCH in at least one symbol indicated as a downlink symbol by the uplink and downlink TDD configuration signaling and can be used for uplink transmission: the first condition is not met, the first SPS PDSCH does not need to be received by the first node, and the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0380] As an embodiment, the benefits of the above method include: ensuring the transmission of the granted PUSCH configured in the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission, thereby improving the uplink transmission efficiency.

[0381] As an embodiment, the benefits of the above method include: in the scenario where the SPS PDSCH and the configured granted PUSCH overlap in the symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission, the HARQ-ACK feedback efficiency is improved and the HARQ-ACK feedback overhead is saved.

[0382] As an embodiment, when the first SPS PDSCH does not overlap with the configured granted PUSCH in the first category of symbols: the first SPS PDSCH does not belong to the first type of PDSCH among the multiple PDSCHs; the first type of PDSCH is an SPS PDSCH that does not need to be received because it overlaps with the configured granted PUSCH in the first category of symbols.

[0383] As an embodiment, when the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbols: the first SPS PDSCH belongs to the first type of PDSCH among multiple PDSCHs, and the first SPS PDSCH does not need to be received by the first node.

[0384] As an embodiment, the multiple PDSCHs include at least an SPS PDSCH that overlaps with a PUSCH with a higher priority configuration grant in the first type of symbols.

[0385] As an embodiment, when the first SPS PDSCH overlaps with a PUSCH with a higher priority configuration grant in at least one of the first category symbols: the first condition is not met, the first SPS PDSCH does not need to be received by the first node, and the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0386] As an embodiment, the benefits of the above method include: ensuring the transmission of the PUSCH with a configuration grant having a higher priority in the first type of symbols, and improving the transmission efficiency of the uplink.

[0387] As an embodiment, the benefits of the above method include: in the scenario where the SPS PDSCH with higher priority and the configured granted PUSCH overlap in the first type of symbols, the feedback efficiency of HARQ-ACK is improved and the feedback overhead of HARQ-ACK is saved.

[0388] As an embodiment, when the first SPS PDSCH overlaps with a configured granted PUSCH with the same priority in at least one of the first category symbols: the first condition is not met, and the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0389] As an embodiment, the above method has the following benefits: in a scenario where an SPS PDSCH with the same priority and a configured PUSCH overlap in the first type of symbols, transmission of the configured PUSCH is ensured, thereby improving uplink transmission efficiency.

[0390] As an embodiment, the benefits of the above method include: in the scenario where SPS PDSCH with the same priority and the configured granted PUSCH overlap in the first type of symbols, the feedback efficiency of HARQ-ACK is improved and the feedback overhead of HARQ-ACK is saved.

[0391] As an embodiment, when the first SPS PDSCH does not overlap with the configured granted PUSCH of higher priority or the same priority in the first category of symbols: the first SPS PDSCH does not belong to the first type of SPS PDSCH among the multiple PDSCHs; the first type of PDSCH is an SPS PDSCH that does not need to be received because it overlaps with the configured granted PUSCH in the first category of symbols.

[0392] As an embodiment, when the first SPS PDSCH does not overlap with a configured PUSCH of higher priority in the first category symbol and the first SPS PDSCH overlaps with a configured PUSCH with the same priority in at least one of the first category symbols: the first SPS PDSCH does not belong to the first type of SPS PDSCH among the multiple PDSCHs; the first type of PDSCH is an SPS PDSCH that does not need to be received because it overlaps with the configured PUSCH in the first category symbol.

[0393] As an embodiment, when the first SPS PDSCH does not overlap with a configured PUSCH of higher priority or the same priority in the first category of symbols and the first SPS PDSCH overlaps with a configured PUSCH with lower priority in at least one of the first category of symbols: the first SPS PDSCH does not belong to the first type of SPS PDSCH among the multiple PDSCHs; the first type of PDSCH is an SPS PDSCH that does not need to be received because it overlaps with the configured PUSCH in the first category of symbols.

[0394] As an embodiment, the priority of an SPS PDSCH is configured by the corresponding SPS-Config.

[0395] As an embodiment, the priority of an SPS PDSCH is determined by the configured corresponding harq-CodebookID.

[0396] As an embodiment, the priority of a PUSCH granted by a configuration is configured by phy-PriorityIndex.

[0397] As an embodiment, when the first SPS PDSCH and a configured granted PUSCH have the same priority index, the first SPS PDSCH and the configured granted PUSCH have the same priority.

[0398] As an embodiment, when the first SPS PDSCH has a priority index of 1 and a configured granted PUSCH has a priority index of 0, the configured granted PUSCH has a lower priority than the first SPS PDSCH.

[0399] As an embodiment, when the first SPS PDSCH has a priority index of 0 and a configured granted PUSCH has a priority index of 1, the configured granted PUSCH has a higher priority than the first SPS PDSCH.

[0400] As an embodiment, the benefits of the above method include: making full use of the priority index already defined by 3GPP and reducing the workload of standardization.

[0401] As an embodiment, the priority of the first SPS PDSCH is one of a plurality of predefined or configurable different priorities, and the priority of a configured granted PUSCH is one of the plurality of different priorities.

[0402] Example 8

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

[0404] In the eighth embodiment, the plurality of SPS PDSCHs include at least an SPS PDSCH that does not need to be received among a plurality of overlapping SPS PDSCHs in any time slot.

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

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

[0407] 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:

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

[0409] 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;

[0410] 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;

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

[0412] 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.

[0413] 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 between the symbols indicated as uplink symbols by tdd-UL-DLConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in any time slot.

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

[0415] 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 occupies the first type of symbols in the time domain and occupies at least part of the frequency domain resources that do not belong to the first frequency band resources.

[0416] As an embodiment, the benefits of the above method include: improving the utilization efficiency of SPS PDSCH occupying the first type of symbols in the time domain while avoiding interference of SPS PDSCH transmission in the first type of symbols with transmission on frequency domain resources outside the first frequency band resources.

[0417] As an embodiment, when the time domain resources allocated to a PDSCH include a first-category symbol, the PDSCH occupies the first-category symbol in the time domain.

[0418] As an embodiment, when the time domain resources occupied by a PDSCH include a first-category symbol, the PDSCH occupies the first-category symbol in the time domain.

[0419] As an embodiment, when the time domain resources allocated to a PDSCH overlap with a first-category symbol, the PDSCH occupies the first-category symbol in the time domain.

[0420] As an embodiment, when a PDSCH overlaps with a first-category symbol in the time domain, the PDSCH occupies the first-category symbol in the time domain.

[0421] As an embodiment, a PDSCH occupying the first type of symbols in the time domain means that the time domain resources occupied by this PDSCH are in at least one of the first type of symbols.

[0422] As an embodiment, a PDSCH occupies only the first category of symbols in the time domain, or occupies only symbols other than the first category of symbols, or occupies at least one of the first category of symbols and at least one symbol other than the first category of symbols.

[0423] As an embodiment, in the present application, any PDSCH occupies only the first category of symbols in the time domain, or only occupies symbols other than the first category of symbols.

[0424] As an embodiment, the benefits of the above method include: reducing the complexity of system design.

[0425] As an embodiment, when the time domain resources allocated to a PDSCH include a symbol other than the first category of symbols, the PDSCH occupies the symbol other than the first category of symbols in the time domain.

[0426] As an embodiment, when the time domain resources occupied by a PDSCH include a symbol other than the first category of symbols, the PDSCH occupies the symbol other than the first category of symbols in the time domain.

[0427] As an embodiment, when the time domain resources allocated to a PDSCH overlap with a symbol outside the first category of symbols, the PDSCH occupies the symbol outside the first category of symbols in the time domain.

[0428] As an embodiment, when a PDSCH overlaps with a symbol other than the first category of symbols in the time domain, the PDSCH occupies the symbol other than the first category of symbols in the time domain.

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

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

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

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

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

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

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

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

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

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

[0439] As an embodiment, the second PDSCH set is a subset of the first PDSCH set, and the second PDSCH set includes SPS PDSCHs that do not need to be received among a plurality of overlapping SPS PDSCHs in any time slot.

[0440] As an embodiment, the target PDSCH is a PDSCH in the first PDSCH set; when the target PDSCH is the SPS PDSCH that needs to be received determined by the first method, the second PDSCH set does not include the target PDSCH; otherwise, the second PDSCH set includes the target PDSCH.

[0441] As an embodiment, when the first SPS PDSCH belongs to the second PDSCH set: the first condition is not met, the first SPS PDSCH does not need to be received by the first node, and the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0442] As an embodiment, the benefits of the above method include: enhancing the processing of multiple overlapping SPS PDSCHs in the same time slot, improving the utilization efficiency and transmission reliability of SPS PDSCH

[0443] As an embodiment, the benefits of the above method include: improving the feedback efficiency of HARQ-ACK and saving the feedback overhead of HARQ-ACK.

[0444] Example 9

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

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

[0447] 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.

[0448] 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.

[0449] 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 (TransportBlocks) 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 cell j The subcarrier spacing configuration is defined by the high-level parameter subcarrierSpacing; for the mth TB, V j,m 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' is the number of scheduled code blocks in 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.

[0450] As an embodiment, for the j-th serving cell, when the second condition is met and the second data rate condition is not met, the first node does not need to receive PDSCH in the j-th serving cell. The second 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. MCS >W. Among them I MCS 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 second 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,m The calculation formula is Where A is the number of bits of the m-th TB, C is the total number of code blocks (code block(s)) of the m-th TB, and C' is the number of scheduled code blocks of 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.

[0451] As an embodiment, when any sub-condition of the second condition is met, the second condition is met.

[0452] As an embodiment, when the second condition is not satisfied or the second data rate condition is satisfied, whether the first node needs 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;

[0453] 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.

[0454] 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.

[0455] As an embodiment, when the first SPS PDSCH belongs to a PDSCH that does not need to be received based on the UE capability for the number of PDSCH receptions in a time slot: the first condition is not met, the first SPS PDSCH does not need to be received by the first node, and the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0456] As an embodiment, the above method has the following benefits: it is advantageous to receive the first SPS PDSCH according to the number of PDSCH receptions in a time slot supported by the first node.

[0457] As an embodiment, the benefits of the above method include: improving the feedback efficiency of HARQ-ACK and saving the feedback overhead of HARQ-ACK.

[0458] Example 10

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

[0460] In the tenth embodiment, the plurality of SPS PDSCHs include at least 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.

[0461] As an embodiment, when the first SPS PDSCH overlaps with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot: the first condition is not met, the first SPS PDSCH does not need to be received by the first node, and the first HARQ-ACK bit block does not include a HARQ-ACK bit for the first SPS PDSCH.

[0462] As an embodiment, the above method has the following benefits: reducing / avoiding the interference caused by the transmission of the SPS PDSCH to the symbols indicated as uplink in the same time slot.

[0463] As an embodiment, the benefits of the above method include: improving the feedback efficiency of HARQ-ACK and saving the feedback overhead of HARQ-ACK.

[0464] Example 11

[0465] Embodiment 11 illustrates a schematic diagram of the second RRC signaling according to an embodiment of the present application, as shown in FIG11 .

[0466] In embodiment 11, the first node receives second RRC signaling; the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

[0467] As an embodiment, the first node considers the impact of the configured granted PUSCH on the first HARQ-ACK bit block in the process of determining the first HARQ-ACK bit block only when the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbol.

[0468] As an embodiment, the value range of the second RRC signaling includes 2 values, and the 2 values ​​respectively indicate: not receiving the SPS PDSCH that overlaps with the configured PUSCH in the first type of symbols, and not sending the configured PUSCH that overlaps with the SPS PDSCH in the first type of symbols.

[0469] As an embodiment, the first receiver receives a second RRC signaling; the second RRC signaling at least indicates that there is no need to receive the SPS PDSCH that overlaps with the PUSCH with a higher priority configuration grant in the first type of symbols.

[0470] As an embodiment, the benefits of the above method include: improving configuration flexibility and facilitating optimization of uplink and downlink resource usage.

[0471] As an embodiment, the first node considers the impact of the configured granted PUSCH on the first HARQ-ACK bit block in the process of determining the first HARQ-ACK bit block only when the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH with a higher priority in the first category of symbols.

[0472] As an embodiment, the first node considers the impact of the configured granted PUSCH on the first HARQ-ACK bit block in the process of determining the first HARQ-ACK bit block only when the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH with the same priority in the first category of symbols.

[0473] As an embodiment, the value range of the second RRC signaling includes 2 values, one of the 2 values ​​at least indicates that the SPS PDSCH that overlaps with the PUSCH with a higher priority configuration grant in the first category of symbols is not received, and the other of the 2 values ​​indicates that the PUSCH with a configuration grant that overlaps with the SPS PDSCH in the first category of symbols is not sent.

[0474] Example 12

[0475] Example 12 illustrates a flowchart of generating a first HARQ-ACK bit block according to an embodiment of the present application, as shown in Figure 12.

[0476] In Example 12, in step S1201, is the number of serving cells (serving cell(s)) configured for the first node; in step S1202, set is the number of SPS PDSCH configurations (configuration(s)) configured for the first node in the cth serving cell; in step S1203, set is the number of downlink time slots for SPS PDSCH reception on the c-th serving cell for multiplexing HARQ-ACK information on PUCCH; in step S1204, j=0 is set, where j is the index of the HARQ-ACK information bit; in step S1205, c=0 is set, where c is the index of the serving cell, corresponding to the RRC index of the cell sorted from low to high; in step S1206, s=0 is set, where s is the SPS PDSCH configuration index, corresponding to the RRC index of the SPS PDSCH configuration sorted from low to high; in step S1207, n is set D =0, where n D Corresponding time slot index; in step S1208, determining whether the first condition is satisfied (in step S1208 and the following step S1209: the first SPS PDSCH is occupied time slot n D , for SPS PDSCH configuration s, SPS PDSCH on serving cell c;), if satisfied, execute step S1209, if not satisfied, jump to step S1211; in step S1209, the HARQ-ACK bit for the first SPS PDSCH is used as the bit with index j in the first HARQ-ACK bit block; in step S1210, j=j+1; in step S1211, n D =n D +1; determine the loop condition in step S1212 Is it satisfied? If so, jump back to step S1208. If not, execute step S1213. In step S1213, s=s+1. In step S1214, determine the loop condition. Is it satisfied? If so, jump back to step S1207. If not, execute step S1215. In step S1215, c=c+1. In step S1216, determine the loop condition. Is it satisfied? If so, jump back to step S1206; if not, end.

[0477] The above-mentioned Example 12 is a non-limiting implementation.

[0478] As an embodiment, the first node may adopt other implementation methods that have equivalent effects to the above-mentioned embodiment 12 to generate the first HARQ-ACK bit block.

[0479] As an embodiment, when the first SPS PDSCH is in the time slot n D When the first SPS PDSCH occupies the time slot n D .

[0480] As an embodiment, when at least part of the time domain resources occupied by the first SPS PDSCH is in the time slot n D When the first SPS PDSCH occupies the time slot n D .

[0481] As an embodiment, the first SPS PDSCH is an SPS PDSCH in a first time slot set associated with an SPS PDSCH configuration with a configuration index of s on the c-th serving cell, and the first time slot set includes a time slot index of n. D time slot.

[0482] As an embodiment, the first time slot set only includes the time slot index n D time slot.

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

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

[0485] As an embodiment, the first time slot set is composed of time slot n D -M+1 to time slot n D The number of these time slots is M, and the M is configurable.

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

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

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

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

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

[0491] As an embodiment, the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with a configured granted PUSCH in the first type of symbols.

[0492] As an embodiment, the benefits of the above method include: improving the reporting performance of HARQ-ACK information for SPS PDSCH.

[0493] As an embodiment, the benefits of the above method include: saving HARQ-ACK feedback overhead.

[0494] As an embodiment, the advantages of the above method include: the workload required for standardization is small.

[0495] As an embodiment, the first condition includes multiple sub-conditions; the expression "the first condition is satisfied" means that all the multiple sub-conditions are satisfied.

[0496] As an embodiment, the first sub-condition is one of the multiple sub-conditions; the first sub-condition is: the first SPS PDSCH does not overlap with the configured granted PUSCH in the first type of symbols.

[0497] As an embodiment, the first sub-condition is one of the multiple sub-conditions; the first sub-condition is: the first SPS PDSCH does not belong to any SPS PDSCH among multiple SPS PDSCHs; the multiple SPS PDSCHs include an SPS PDSCH that does not need to be received because it overlaps with the configured granted PUSCH in the first category of symbols.

[0498] As an embodiment, the multiple SPS PDSCHs are all SPS PDSCHs that do not need to be received.

[0499] 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.

[0500] 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.

[0501] 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.

[0502] As an embodiment, the multiple SPS PDSCHs further include: an SPS PDSCH that does not need to be received because it occupies frequency domain resources outside the first frequency band resources in the first type of symbols; the first frequency band resources are configurable.

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

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

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

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

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

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

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

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

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

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

[0513] As an embodiment, the second sub-condition is one of the multiple sub-conditions; the second sub-condition is: the HARQ-ACK information for the first SPS PDSCH is associated with the first PUCCH.

[0514] As an embodiment, when a PUCCH is reserved for sending the HARQ-ACK information for the first SPS PDSCH, the HARQ-ACK information for the first SPS PDSCH is associated with this PUCCH.

[0515] As an embodiment, when one PUCCH is reserved for multiplexing of HARQ-ACK information including the HARQ-ACK information for the first SPS PDSCH, the HARQ-ACK information for the first SPS PDSCH is associated with this PUCCH.

[0516] As an embodiment, when the first node is configured to feed back the HARQ-ACK information for the first SPS PDSCH in the time slot where the first PUCCH is located, the HARQ-ACK information for the first SPS PDSCH is associated with the first PUCCH.

[0517] As an embodiment, when the first condition is met and the first SPS PDSCH does not need to be received due to overlapping with the dynamically scheduled PUSCH in the first type of symbols, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH.

[0518] As an embodiment, the benefits of the above method include: avoiding / alleviating the impact of the dynamically scheduled PUSCH on the generation of the first HARQ-ACK bit block, and improving the robustness of the HARQ-ACK feedback.

[0519] Example 13

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

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

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

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

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

[0525] 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).

[0526] 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.

[0527] 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.

[0528] 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.

[0529] 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.

[0530] 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.

[0531] 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.

[0532] 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.

[0533] 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.

[0534] 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.

[0535] 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.

[0536] As an embodiment, the first receiver A01 receives a first RRC signaling, and the first RRC signaling includes configuration information of at least a first SPS PDSCH; the first transmitter A02 sends a first HARQ-ACK bit block on a first PUCCH, and the first HARQ-ACK bit block includes at least one HARQ-ACK bit; wherein, whether the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0537] As an embodiment, when the first SPS PDSCH does not need to be received due to overlapping with the configured granted PUSCH in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

[0538] As an embodiment, when a first condition is met, the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first type of symbol.

[0539] As an embodiment, the first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCHs received in a time slot, and an SPS PDSCH that does not need to be received due to overlap with at least one symbol indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0540] As an embodiment, the first receiver A01 receives a second RRC signaling; the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

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

[0542] As an embodiment, the first transmitter A02 reports HARQ-ACK information only for SPS PDSCH in the first PUCCH.

[0543] Example 14

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

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

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

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

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

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

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

[0551] 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.

[0552] 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.

[0553] 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.

[0554] 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.

[0555] 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.

[0556] 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.

[0557] 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.

[0558] 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.

[0559] 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.

[0560] 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.

[0561] As an embodiment, the second transmitter B01 sends a first RRC signaling, and the first RRC signaling includes configuration information of at least a first SPS PDSCH; the second receiver B02 receives a first HARQ-ACK bit block on a first PUCCH, and the first HARQ-ACK bit block includes at least one HARQ-ACK bit; wherein, whether the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in a first type of symbol, and the first type of symbol includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0562] As an embodiment, when the first SPS PDSCH does not need to be received due to overlapping with the configured granted PUSCH in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

[0563] As an embodiment, when a first condition is met, the first HARQ-ACK bit block includes a HARQ-ACK bit for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first type of symbol.

[0564] As an embodiment, the first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCHs received in a time slot, and an SPS PDSCH that does not need to be received due to overlap with at least one symbol indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0565] As an embodiment, the second transmitter B01 sends a second RRC signaling; the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

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

[0567] As an embodiment, the first PUCCH only carries HARQ-ACK information for the SPS PDSCH.

[0568] 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.

[0569] 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: include: A first receiver receives a first RRC signaling, wherein the first RRC signaling includes at least configuration information of a first SPS PDSCH; A first transmitter sends a first HARQ-ACK bit block on a first PUCCH, where the first HARQ-ACK bit block includes at least one HARQ-ACK bit; Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

2. The first node according to claim 1, characterized in that: When the first SPS PDSCH does not need to be received due to overlapping with the PUSCH configured with grant in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

3. The first node according to claim 1 or 2, characterized in that: When a first condition is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with a configured granted PUSCH in the first type of symbols.

4. The first node according to claim 3, characterized in that: The first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCH receptions in a time slot, and an SPS PDSCH that does not need to be received due to overlap with at least one symbol indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

5. The first node according to any one of claims 1 to 4, characterized in that: The first receiver receives a second RRC signaling, wherein the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

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

7. The first node according to any one of claims 1 to 6, characterized in that: The first node reports HARQ-ACK information only for the SPS PDSCH in the first PUCCH.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first RRC signaling, where the first RRC signaling includes at least configuration information of a first SPS PDSCH; A second receiver receives a first HARQ-ACK bit block on a first PUCCH, where the first HARQ-ACK bit block includes at least one HARQ-ACK bit; Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

9. The second node according to claim 8, characterized in that: When the first SPS PDSCH does not need to be received due to overlapping with the PUSCH configured with grant in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

10. The second node according to claim 8 or 9, characterized in that: When a first condition is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with a configured granted PUSCH in the first type of symbols.

11. The second node according to claim 10, characterized in that: The first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCH receptions in a time slot, and an SPS PDSCH that does not need to be received due to overlap with at least one symbol indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

12. The second node according to any one of claims 8 to 11, characterized in that: The second transmitter sends a second RRC signaling, wherein the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

13. The second node according to any one of claims 8 to 12, characterized in that: The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

14. The second node according to any one of claims 8 to 13, characterized in that: The first PUCCH only carries HARQ-ACK information for the SPS PDSCH.

15. A method in a first node for wireless communication, characterized in that: include: receiving first RRC signaling, wherein the first RRC signaling includes configuration information of at least a first SPS PDSCH; Sending a first HARQ-ACK bit block on a first PUCCH, wherein the first HARQ-ACK bit block includes at least one HARQ-ACK bit; Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

16. The method in the first node according to claim 15, characterized in that: When the first SPS PDSCH does not need to be received due to overlapping with the PUSCH configured with grant in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

17. The method in the first node according to claim 15 or 16, characterized in that: When a first condition is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with a configured granted PUSCH in the first type of symbols.

18. The method in the first node according to claim 17, characterized in that: The first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlap with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCH receptions in a time slot, and an SPS PDSCH that does not need to be received due to overlap with at least one symbol indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

19. The method in the first node according to any one of claims 15 to 18, characterized in that: include: A second RRC signaling is received; the second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

20. The method in the first node according to any one of claims 15 to 19, characterized in that: The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

21. The method in the first node according to any one of claims 15 to 20, characterized in that: The first node reports HARQ-ACK information only for the SPS PDSCH in the first PUCCH.

22. A method in a second node for wireless communication, characterized in that: include: Sending a first RRC signaling, where the first RRC signaling includes at least configuration information of a first SPS PDSCH; Receiving a first HARQ-ACK bit block on a first PUCCH, the first HARQ-ACK bit block comprising at least one HARQ-ACK bit; Among them, whether the first HARQ-ACK bit block includes the HARQ-ACK bit for the first SPS PDSCH is related to whether the first SPS PDSCH overlaps with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

23. The method in the second node according to claim 22, characterized in that: When the first SPS PDSCH does not need to be received due to overlapping with the PUSCH configured with grant in the first type of symbols, the first HARQ-ACK bit block does not include the HARQ-ACK bit for the first SPS PDSCH.

24. The method in the second node according to claim 22 or 23, characterized in that: When a first condition is met, the first HARQ-ACK bit block includes HARQ-ACK bits for the first SPS PDSCH; the first condition includes: the first SPS PDSCH is not an SPS PDSCH that does not need to be received due to overlapping with a configured granted PUSCH in the first type of symbols.

25. The method in the second node according to claim 24, characterized in that: The first condition includes: the first SPS PDSCH does not belong to any of the multiple SPS PDSCHs; the multiple SPS PDSCHs include at least: an SPS PDSCH that does not need to be received due to overlapping with the configured granted PUSCH in the first category of symbols, an SPS PDSCH that does not need to be received among the multiple overlapping SPS PDSCHs in any time slot, an SPS PDSCH that does not need to be received based on the UE capability for the number of PDSCH receptions in a time slot, and 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.

26. The method in the second node according to any one of claims 22 to 25, characterized in that: include: Sending a second RRC signaling; The second RRC signaling indicates that there is no need to receive the SPS PDSCH that overlaps with the PUSCH configured to be granted in the first type of symbols.

27. The method in the second node according to any one of claims 22 to 26, characterized in that: The uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

28. The method in the second node according to any one of claims 22 to 27, characterized in that: The first PUCCH only carries HARQ-ACK information for the SPS PDSCH.

Images