Method and device for node used for wireless communication

Abstract

The present application discloses a method and device for a node used for wireless communication. A first receiver receives uplink and downlink TDD configuration signaling; and a first transmitter generates first HARQ-ACK information on the basis of a first receiving group, wherein the first receiving group is associated with a plurality of PDSCHs. When the first receiving group is associated with at least one PDSCH other than a first-type PDSCH, a first node assumes that a transport block provided by the first-type PDSCH is correctly received; when the first receiving group is only associated with the first-type PDSCH, the first HARQ-ACK information is NACK. A first-type symbol comprises a symbol indicated by the uplink and downlink TDD configuration signaling as a downlink symbol and capable of being used for uplink transmission, and the first-type PDSCH depends on the first-type symbol.

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] For wireless communications using high-frequency bands (e.g., bands between 52.6 GHz and 71 GHz), 3GPP introduced in NR Release 17 a scheduling method in which a single DCI (Downlink Control Information) signaling schedules multiple PDSCHs (Physical Downlink Shared CHannels).

[0004] Summary of the Invention

[0005] In a scenario where symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission are configured, how to generate group-based HARQ-ACK (Hybrid Automatic Repeat request ACKnowledge) information for multiple PDSCHs is an important issue that needs to be considered for enhancing HARQ-ACK feedback; the present application discloses a solution to the above problem. It should be noted that the present application can be applied 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 combined with each other arbitrarily.

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

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

[0008] Receive uplink and downlink TDD configuration signaling;

[0009] generating first HARQ-ACK information based on a first receiving group, the first receiving group being associated with a plurality of PDSCHs;

[0010] In which, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

[0011] As an embodiment, the problem to be solved by the present application includes: how to generate HARQ-ACK information.

[0012] As an embodiment, the problem to be solved by the present application includes: in a scenario where the first type of symbols is configured, how the first node generates the first HARQ-ACK information according to the first receiving group.

[0013] As an embodiment, the above method is applicable to a scenario in which the first node determines the HARQ-ACK feedback for grouping the scheduled PDSCH; for a group associated with multiple PDSCHs, the first node can determine the HARQ-ACK information generated for this group based on whether this group is only associated with the first type of PDSCH, wherein the first type of PDSCH includes a PDSCH affected by symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission; the benefits of the above method include: making full use of the configuration information of symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and can be used for uplink transmission, thereby improving the HARQ-ACK feedback effect.

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

[0015] As an embodiment, the benefits of the above method include: improving the robustness of HARQ-ACK feedback.

[0016] As an embodiment, the benefits of the above method include: improving the flexibility of base station scheduling, and facilitating support for full-duplex operation (operation(s)) (non-overlapping sub-bands or other types) at least on the base station side.

[0017] As an embodiment, the above method has the following advantages: based on the existing 3GPP technical specification version, the required changes are small, and it is simple and effective.

[0018] As an embodiment, the benefits of the above method include: avoiding the impact of the unreceived PDSCH on the HARQ-ACK feedback result.

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

[0020] As an embodiment, the benefits of the above method include: improving the reliability of downlink data transmission.

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

[0022] The first type of PDSCH includes a PDSCH that meets each condition in a first condition set; the first condition set includes: overlapping with at least one first type of symbol.

[0023] As an embodiment, the characteristics of the above method include: the first node determines the HARQ-ACK information generated for a group based on whether the group is only associated with the PDSCH overlapping with the first type of symbols; the benefits of the above method include: the indication efficiency of the HARQ-ACK information is high.

[0024] As an embodiment, the benefits of the above method include: improving the flexibility of base station scheduling, and facilitating support for full-duplex operation (operation(s)) (non-overlapping sub-bands or other types) at least on the base station side.

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

[0026] As an embodiment, the benefits of the above method include: being helpful in solving the overlap problem between PDSCH and the first type of symbols.

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

[0028] The first condition set further includes: occupying at least one RB belonging to a target frequency band resource; and the target frequency band resource is configurable.

[0029] As an embodiment, the benefits of the above method include: improving the flexibility of base station scheduling, and facilitating support for full-duplex operation (operation(s)) (non-overlapping sub-bands or other types) at least on the base station side.

[0030] As an embodiment, the benefits of the above method include: reducing the complexity of processing by the first node.

[0031] As an embodiment, the benefits of the above method include: reducing the interference caused by the transmission of PDSCH in the first type of symbols to the transmission on the target frequency band resources.

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

[0033] When the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: generation of the first HARQ-ACK information depends on whether the transport block provided by the at least one PDSCH is correctly received.

[0034] As an embodiment, the benefits of the above method include: improving the reliability of downlink data transmission.

[0035] As an embodiment, the benefits of the above method include: improving the robustness of HARQ-ACK feedback.

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

[0037] receiving a first DCI format and a first PDSCH set, wherein the first DCI format schedules the first PDSCH set;

[0038] The first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

[0039] As an embodiment, the benefits of the above method include: being conducive to improving resource utilization.

[0040] As an embodiment, the benefits of the above method include: reducing the number of blind detections on the PDCCH (Physical Downlink Control CHannel).

[0041] As an embodiment, the benefits of the above method include: reducing the complexity of implementing the first node.

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

[0043] The first receiving group is a PDSCH receiving group.

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

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

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

[0047] As an embodiment, the above method has the following benefits: it is facilitating redefinition of cell-specific downlink symbols.

[0048] As an embodiment, the benefits of the above method include: facilitating redefinition of UE-specific downlink symbols.

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

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

[0051] Send uplink and downlink TDD configuration signaling;

[0052] receiving at least first HARQ-ACK information;

[0053] In which, the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generator of the first HARQ-ACK information assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

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

[0055] The first type of PDSCH includes a PDSCH that meets each condition in a first condition set; the first condition set includes: overlapping with at least one first type of symbol.

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

[0057] The first condition set further includes: occupying at least one RB belonging to a target frequency band resource; and the target frequency band resource is configurable.

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

[0059] When the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: generation of the first HARQ-ACK information depends on whether the transport block provided by the at least one PDSCH is correctly received.

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

[0061] Send a first DCI format and a first PDSCH set, where the first DCI format schedules the first PDSCH set;

[0062] The first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

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

[0064] The first receiving group is a PDSCH receiving group.

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

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

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

[0068] A first receiver receives uplink and downlink TDD configuration signaling;

[0069] A first transmitter generates first HARQ-ACK information based on a first receiving group, where the first receiving group is associated with a plurality of PDSCHs;

[0070] In which, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

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

[0072] A second transmitter sends uplink and downlink TDD configuration signaling;

[0073] a second receiver, receiving at least first HARQ-ACK information;

[0074] In which, the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generator of the first HARQ-ACK information assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0082] FIG7 shows a schematic diagram illustrating a first type of PDSCH and a first condition set according to an embodiment of the present application;

[0083] FIG8 is a schematic diagram illustrating first HARQ-ACK information and CBG-based HARQ-ACK information according to one embodiment of the present application;

[0084] FIG9 shows a schematic diagram illustrating generating first HARQ-ACK information according to one embodiment of the present application;

[0085] FIG10 shows a schematic diagram illustrating a first receiving group according to an embodiment of the present application;

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

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

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

[0089] Example 1

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

[0091] In embodiment 1, the first node in the present application receives uplink and downlink TDD configuration signaling in step 101; and generates first HARQ-ACK information based on the first receiving group in step 102.

[0092] In embodiment 1, the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

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

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

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

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

[0097] As an embodiment, the uplink and downlink TDD configuration signaling includes user equipment (UE)-dedicated signaling.

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

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

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

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

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

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

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

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

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

[0107] As an embodiment, the uplink and downlink TDD configuration signaling includes time domain configuration information.

[0108] As an embodiment, the uplink and downlink TDD configuration signaling includes UL / DL (Uplink / Downlink) TDD (Time Division Duplexing) configuration information.

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

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

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

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

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

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

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

[0116] As an embodiment, the first receiving group is a PDSCH reception group (PDSCH reception group); when the first receiving group includes reception of one PDSCH, the first receiving group is associated with the one PDSCH.

[0117] As an embodiment, the first receiving group is a transport block group (TBG); when the first receiving group includes a transport block provided by a PDSCH, the first receiving group is associated with the PDSCH.

[0118] As an embodiment, when a PDSCH is mapped to the first receiving group according to a predefined rule, the first receiving group is associated with the one PDSCH.

[0119] As an embodiment, the above method has the following benefits: it is conducive to realizing time bundling of HARQ and saves HARQ-ACK feedback overhead.

[0120] As an embodiment, the benefits of the above method include: reducing the complexity of processing by the first node.

[0121] As an embodiment, the statement “the first receiving group is associated with multiple PDSCHs” means that the first receiving group is associated with at least two PDSCHs.

[0122] As an embodiment, if the first receiving group is associated with only one PDSCH, the first node does not use HARQ-based time domain bundling to generate the first HARQ-ACK information.

[0123] As an embodiment, if the first receiving group is associated with only one PDSCH, the generation of the first HARQ-ACK information is related to whether the one PDSCH associated with the first receiving group is a first type PDSCH.

[0124] As an embodiment, if the first receiving group is associated with only one PDSCH, the one PDSCH associated with the first receiving group is a first type of PDSCH, or is a PDSCH other than the first type of PDSCH.

[0125] As an embodiment, if the first receiving group is associated with only one PDSCH, when the one PDSCH associated with the first receiving group is the first type of PDSCH, the first HARQ-ACK information is NACK;

[0126] As an embodiment, if the first receiving group is associated with only one PDSCH, when the one PDSCH associated with the first receiving group is a PDSCH other than the first type of PDSCH, the generation of the first HARQ-ACK information depends on whether at least one transmission block provided by the PDSCH is correctly received.

[0127] As an embodiment, the statement "generating first HARQ-ACK information based on the first receiving group" means: generating first HARQ-ACK information based on a PDSCH other than the first type of PDSCH associated with the first receiving group.

[0128] As an embodiment, the statement "generating first HARQ-ACK information based on the first receiving group" means: generating first HARQ-ACK information based on the first type of PDSCH associated with the first receiving group.

[0129] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transport block provided by the first type of PDSCH is correctly received.

[0130] As an embodiment, the benefits of the above method include: avoiding the influence of the first type of PDSCH on the HARQ-ACK feedback result.

[0131] As an embodiment, when the first receiving group is associated only with the first type of PDSCH, the first HARQ-ACK information is NACK.

[0132] As an embodiment, when the first receiving group is associated only with the first type of PDSCH, the first HARQ-ACK information does not need to be generated based on HARQ spatial bundling and / or time bundling, and the first HARQ-ACK information is a NACK value.

[0133] As an embodiment, the benefits of the above method include: simplifying system design.

[0134] As an embodiment, if each PDSCH associated with the first receiving group is a first-type PDSCH, the first receiving group is only associated with the first-type PDSCH.

[0135] As an embodiment, the first HARQ-ACK information includes at least 1 HARQ-ACK information bit.

[0136] As an embodiment, the first HARQ-ACK information includes 1 HARQ-ACK information bit.

[0137] As an embodiment, the first HARQ-ACK information includes 1 or 2 HARQ-ACK information bits.

[0138] As an embodiment, the number of HARQ-ACK information bits included in the first HARQ-ACK information depends on the values ​​of the first RRC parameter and the second RRC parameter.

[0139] As a sub-embodiment of this embodiment, the first RRC parameter includes configuration information of the maximum number of code words that a single DCI may schedule.

[0140] As a sub-embodiment of this embodiment, the first RRC parameter indicates the reception of two transport blocks or the reception of one transport block.

[0141] As a sub-embodiment of this embodiment, the first RRC parameter configures the first node to receive two transport blocks or one transport block.

[0142] As a sub-embodiment of this embodiment, the name of the first RRC parameter includes at least one of maxNrofCodeWords and ScheduledByDCI.

[0143] As a sub-embodiment of this embodiment, the first RRC parameter includes maxNrofCodeWordsScheduledByDCI.

[0144] As a sub-embodiment of this embodiment, the first RRC parameter is maxNrofCodeWordsScheduledByDCI.

[0145] As a sub-embodiment of this embodiment, the first RRC parameter is an enumeration type.

[0146] As a sub-embodiment of this embodiment, the value of the first RRC parameter is at most 1.

[0147] As a sub-embodiment of this embodiment, the benefits of the above method include: being helpful in reducing DCI overhead.

[0148] As a sub-embodiment of this embodiment, the benefits of the above method include: being helpful in saving HARQ-ACK feedback overhead.

[0149] As a sub-embodiment of this embodiment, the value of the first RRC parameter is at most 2.

[0150] As a sub-embodiment of this embodiment, the benefits of the above method include: being conducive to supporting spatial multiplexing when the number of layers is greater than 4.

[0151] As a sub-embodiment of this embodiment, the second RRC parameter includes configuration information of HARQ spatial bundling.

[0152] As a sub-embodiment of this embodiment, the second RRC parameter indicates whether the first node performs HARQ space bundling.

[0153] As a sub-embodiment of this embodiment, the name of the second RRC parameter includes harq-ACK and SpatialBundling.

[0154] As a sub-embodiment of this embodiment, the name of the second RRC parameter also includes PUCCH or PUSCH.

[0155] As a sub-embodiment of this embodiment, the second RRC parameter includes one of harq-ACK-SpatialBundlingPUCCH and harq-ACK-SpatialBundlingPUSCH.

[0156] As a sub-embodiment of this embodiment, the second RRC parameter is harq-ACK-SpatialBundlingPUCCH or harq-ACK-SpatialBundlingPUSCH.

[0157] As a sub-embodiment of this embodiment, the second RRC parameter is an enumeration type.

[0158] As a sub-embodiment of this embodiment, the value of the second RRC parameter includes "true".

[0159] As a sub-embodiment of this embodiment, the benefits of the above method include: being helpful in saving HARQ-ACK feedback overhead.

[0160] As a sub-embodiment of this embodiment, when the first node is configured with the second RRC parameter, the first node performs HARQ space bundling; otherwise, the first node does not perform HARQ space bundling.

[0161] As an embodiment, the generation of the bits of the first HARQ-ACK information depends on how many transport blocks the first node is configured to receive.

[0162] As an embodiment, the generation of the bits of the first HARQ-ACK information depends on whether the first node performs HARQ space bundling.

[0163] As an embodiment, when the first node is configured to receive two transport blocks and does not perform HARQ space bundling, the first HARQ-ACK information includes at least one HARQ-ACK information bit.

[0164] As an embodiment, when the first node is configured to receive two transport blocks and HARQ space bundling is not performed, the first HARQ-ACK information is a NACK;

[0165] As an embodiment, when the first node is configured to receive one transport block, or the first node is configured to receive two transport blocks and perform HARQ space bundling, the first HARQ-ACK information only includes one HARQ-ACK information bit.

[0166] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the generation of the first HARQ-ACK information bits depends on the binary AND operation of the HARQ-ACK information bits corresponding to two transmission blocks of at least one PDSCH.

[0167] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: after performing a binary AND operation on the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH, the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by the DCI format, and replaces the maximum number of CBGs with the maximum number of PDSCH receiving groups, and on this basis generates the bits of the first HARQ-ACK information according to the method described in Section 9.1.1 of 3GPP TS 38.213.

[0168] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: after performing a binary AND operation on the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH, the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by the DCI format, and replaces the maximum number of CBGs with the maximum number of TBGs, and on this basis generates the bits of the first HARQ-ACK information according to the method described in Section 9.1.1 of 3GPP TS 38.213.

[0169] As an embodiment, the above method has the following benefits: HARQ feedback overhead is saved through HARQ spatial bundling.

[0170] As an embodiment, if the first node is configured to receive two transport blocks and the first node performs HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the generation of the first HARQ-ACK information bits depends on the binary AND operation of the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH; each PDSCH is each PDSCH other than the first type of PDSCH to which the first receiving group is associated.

[0171] As an embodiment, if the first node is configured to receive two transport blocks and the first node performs HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type PDSCH: after performing a binary AND operation on the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH, the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by a single DCI format, and replaces the maximum number of code block groups (CBG) with the maximum number of PDSCH receiving groups, and on this basis generates the bits of the first HARQ-ACK information according to the method described in Section 9.1.1 of 3GPP TS 38.213; each of the PDSCHs is each PDSCH other than the first type PDSCH to which the first receiving group is associated.

[0172] As an embodiment, the above method has the following advantages: HARQ feedback overhead is saved through HARQ space bundling and time bundling.

[0173] As an embodiment, if the first node is configured to receive two transport blocks and the first node performs HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type PDSCH: after performing a binary AND operation on the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH, the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by a single DCI format, and replaces the maximum number of code block groups with the maximum number of transport block groups, and on this basis generates the bits of the first HARQ-ACK information according to the method described in Section 9.1.1 of 3GPP TS 38.213; each of the PDSCHs is each PDSCH other than the first type PDSCH to which the first receiving group is associated.

[0174] As an embodiment, the above method has the following advantages: HARQ feedback overhead is saved through HARQ space bundling and time bundling.

[0175] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the generation of the first HARQ-ACK information bits depends on the HARQ-ACK information bits corresponding to the two transmission blocks of at least one PDSCH.

[0176] As an embodiment, the benefits of the above method include: disabling HARQ space bundling, thereby reducing latency.

[0177] As an embodiment, if the first node is configured to receive two transport blocks and the first node does not perform HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the first HARQ-ACK information includes two HARQ-ACK information bits, and the generation of the two HARQ-ACK information bits included in the first HARQ-ACK information depends on the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH; each PDSCH is each PDSCH other than the first type of PDSCH to which the first receiving group is associated.

[0178] As an embodiment, if the first node is configured to receive two transport blocks and the first node does not perform HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by a single DCI format, and replaces the maximum number of code block groups (CBG) with the maximum number of PDSCH receiving groups, and on this basis, generates the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH respectively according to the method described in Section 9.1.1 of 3GPP TS 38.213, and then connects (concatenates) the HARQ-ACK information bits corresponding to the second transport block to the HARQ-ACK information bits corresponding to the first transport block to generate the first HARQ-ACK information; each of the PDSCHs is each PDSCH other than the first type of PDSCH associated with the first receiving group.

[0179] As an embodiment, the benefits of the above method include: disabling HARQ spatial bundling, thereby reducing latency; and enabling HARQ time bundling, thereby saving HARQ feedback overhead.

[0180] As an embodiment, if the first node is configured to receive two transport blocks and the first node does not perform HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by a single DCI format, and replaces the maximum number of code block groups with the maximum number of transport block groups, and on this basis generates the HARQ-ACK information bits corresponding to the two transport blocks of each PDSCH respectively according to the method described in Section 9.1.1 of 3GPP TS 38.213, and then connects (concatenates) the HARQ-ACK information bits corresponding to the second transport block to the HARQ-ACK information bits corresponding to the first transport block to generate the first HARQ-ACK information; each of the PDSCHs is each PDSCH other than the first type of PDSCH associated with the first receiving group.

[0181] As an embodiment, the benefits of the above method include: disabling HARQ spatial bundling, thereby reducing latency; and enabling HARQ time bundling, thereby saving HARQ feedback overhead.

[0182] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the generation of the first HARQ-ACK information bits depends on the HARQ-ACK information bits corresponding to only one transmission block of at least one PDSCH.

[0183] As an embodiment, the benefits of the above method include: not enabling two-transport block transmission, reducing DCI overhead and saving HARQ feedback overhead.

[0184] As an embodiment, if the first node is configured to receive only one transport block and the first node does not perform HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the generation of the first HARQ-ACK information bit depends on the HARQ-ACK information bit corresponding to only one transport block in at least one PDSCH.

[0185] As an embodiment, if the first node is configured to receive only one transport block and the first node does not perform HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type PDSCH: the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by a single DCI format, and replaces the maximum number of code block groups (CBG) with the maximum number of PDSCH receiving groups, and on this basis, generates HARQ-ACK information bits corresponding to only one transport block of each PDSCH according to the method described in Section 9.1.1 of 3GPP TS 38.213, and then generates the first HARQ-ACK information based on the HARQ-ACK information bits corresponding to only one transport block; each PDSCH is each PDSCH other than the first type PDSCH associated with the first receiving group.

[0186] As an embodiment, the benefits of the above method include: saving HARQ feedback overhead through HARQ time bundling.

[0187] As an embodiment, if the first node is configured to receive only one transport block and the first node does not perform HARQ space bundling, then when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the first node replaces the number of code blocks in the transport block with the number of PDSCH receptions scheduled by a single DCI format, replaces the maximum number of code block groups with the maximum number of transport block groups, and on this basis generates HARQ-ACK information bits corresponding to only one transport block of each PDSCH according to the method described in Section 9.1.1 of 3GPP TS 38.213, and then generates the first HARQ-ACK information based on the HARQ-ACK information bits corresponding to only one transport block; each PDSCH is each PDSCH other than the first type of PDSCH to which the first receiving group is associated.

[0188] As an embodiment, the benefits of the above method include: saving HARQ feedback overhead through HARQ time bundling.

[0189] As an embodiment, in the present application, if the first node is configured to receive only one transport block, the first node does not perform HARQ space bundling.

[0190] As an embodiment, in the present application, if the first node is configured to receive two transport blocks, when the first node receives a PDSCH containing only one transport block, the HARQ-ACK information is associated with the first transport block, and the HARQ-ACK information generated by the first node for the second transport block depends on whether the first node performs HARQ space binding; when the first node does not perform HARQ space binding, the first node generates a NACK for the second transport block; otherwise, the first node generates an ACK for the second transport block.

[0191] As an embodiment, if the first node is configured to receive two transport blocks: whether the first node receives a PDSCH containing only one transport block depends at least on an enabling condition of transmission of two transport blocks.

[0192] As a sub-embodiment of this embodiment, the enabling conditions of the transmission of the two transport blocks include: enabling the transmission of the two transport blocks and disabling the transmission of the two transport blocks.

[0193] As a sub-embodiment of this embodiment, whether to enable transmission of two transport blocks is configurable.

[0194] As a sub-embodiment of this embodiment, whether to enable two transport block transmissions depends on the modulation and coding scheme index and the redundancy version number.

[0195] As an embodiment, if the first node is configured to receive two transport blocks: when the first node is not enabled to transmit two transport blocks, the first node receives a PDSCH containing only one transport block; otherwise, the first node receives a PDSCH containing two transport blocks.

[0196] As an embodiment, the first node transmits at least the first HARQ-ACK information.

[0197] As an embodiment, the first node generates a first HARQ-ACK information block, and the first HARQ-ACK information belongs to the first HARQ-ACK information block; wherein, the first HARQ-ACK information block includes HARQ-ACK information generated based on multiple receiving groups respectively, and the first receiving group is one of the multiple receiving groups.

[0198] As an embodiment, the first receiving group is any receiving group among the multiple receiving groups.

[0199] As an embodiment, the first receiving group is any receiving group among the multiple receiving groups that is associated with multiple PDSCHs.

[0200] As an embodiment, the first node sends the first HARQ-ACK information block.

[0201] As an embodiment, when a receiving group is associated with only one PDSCH and the only one PDSCH does not belong to the first category of PDSCH, the HARQ-ACK information generated based on this receiving group indicates whether the transport block provided by the only one PDSCH is correctly received; when a receiving group is associated with only one PDSCH and the only one PDSCH belongs to the first category of PDSCH, the HARQ-ACK information generated based on this receiving group is NACK.

[0202] As an embodiment, any one of the multiple receiving groups is a PDSCH receiving group; when one of the multiple receiving groups includes reception of one PDSCH, the one of the multiple receiving groups is associated with the one PDSCH.

[0203] As an embodiment, any one of the multiple receiving groups is a transport block group; when one of the multiple receiving groups includes a transport block provided by a PDSCH, the one of the multiple receiving groups is associated with the PDSCH.

[0204] As an embodiment, when a PDSCH is mapped to one of the multiple receiving groups according to a predefined rule, the one receiving group among the multiple receiving groups is associated with the one PDSCH.

[0205] As an embodiment, the first HARQ-ACK information block sent by the first node includes HARQ-ACK information generated based on multiple receiving groups respectively, and the first receiving group is one of the multiple receiving groups.

[0206] As an embodiment, the first HARQ-ACK information block sent by the first node is a second type (Type-2) HARQ-ACK codebook.

[0207] As an embodiment, the first HARQ-ACK information block sent by the first node includes at least one HARQ-ACK information bit.

[0208] As an embodiment, the first HARQ-ACK information block sent by the first node is carried by a first signal.

[0209] As a sub-embodiment of this embodiment, the first signal includes a wireless signal.

[0210] As a sub-embodiment of this embodiment, the first signal includes a radio frequency signal.

[0211] As a sub-embodiment of this embodiment, the first signal includes a baseband signal.

[0212] As a sub-embodiment of this embodiment, the first signal occupies a positive integer number of multi-carrier symbols in the time domain.

[0213] As a sub-embodiment of this embodiment, the first signal occupies a positive integer number of resource elements (RE) in the time-frequency domain.

[0214] As a sub-embodiment of this embodiment, the first signal is sent in a PUCCH (Physical Uplink Control CHannel).

[0215] As a sub-embodiment of this embodiment, the first signal is sent in a PUSCH (Physical Uplink Shared CHannel).

[0216] As an embodiment, the first HARQ-ACK information block sent by the first node is used to generate a first sequence, and the first sequence is mapped to physical resources and then sent on a PUCCH (Physical Uplink Control CHannel).

[0217] As an embodiment, all or part of the bits in the first HARQ-ACK information block sent by the first node are sent on the PUCCH after at least sequence modulation (Sequence modulation) and mapping to physical resources (Mapping to physical resources).

[0218] As an embodiment, all or part of the bits in the first HARQ-ACK information block to which the first HARQ-ACK information belongs are sent on the PUCCH after CRC addition, code block segmentation, code block CRC attachment, channel coding, rate matching, concatenation, scrambling, modulation, spreading, and mapping to at least part of physical resources.

[0219] As an embodiment, all or part of the bits in the first HARQ-ACK information block sent by the first node are sent on PUCCH after CRC addition, code block 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.

[0220] As an embodiment, all or part of the bits in the first HARQ-ACK information block sent by the first node undergo CRC addition, code block segmentation, code block CRC attachment, channel coding, rate matching, code block concatenation, scrambling, modulation, layer mapping, transform precoding, precoding, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and at least part of the modulation up-conversion before being sent on the PUSCH.

[0221] As an embodiment, all or part of the bits in the first HARQ-ACK information block sent by the first node are sent on the PUSCH after scrambling, modulation, layer mapping, antenna port mapping, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and modulation up-conversion.

[0222] As an embodiment, all or part of the bits in the first HARQ-ACK information block sent by the first node are sent on the PUSCH after undergoing CRC attachment, code block segmentation, code block CRC attachment, channel coding, rate matching, code block concatenation, scrambling, modulation, layer mapping, precoding, antenna port mapping, mapping to virtual resource blocks, mapping from virtual to physical resource blocks, multi-carrier symbol generation, and at least part of the modulation up-conversion.

[0223] As an embodiment, the first type of symbols also includes symbols indicated as uplink symbols by the uplink and downlink TDD configuration signaling.

[0224] As an embodiment, the symbols indicated as uplink symbols by the uplink and downlink TDD configuration signaling do not belong to the first category of symbols.

[0225] As an embodiment, the first type of symbols is configurable.

[0226] As an embodiment, which symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling belong to the first category of symbols is configurable.

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

[0228] As an embodiment, the benefits of the above method include: being conducive to improving uplink coverage and reducing latency.

[0229] As an embodiment, which symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling do not belong to the first category of symbols are configurable.

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

[0231] As an embodiment, the above method has the following benefits: it is helpful to reduce cross-link interference (Cross-Link Interference, CLI).

[0232] As an embodiment, whether the symbols indicated as flexible symbols by the uplink and downlink TDD configuration signaling belong to the first category of symbols is configurable.

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

[0234] As an embodiment, the first information block includes configuration information of the first type of symbols.

[0235] As a sub-embodiment of this embodiment, the first information block is carried by higher layer signaling.

[0236] As a sub-embodiment of this embodiment, the first information block is carried by RRC (Radio Resource Control) signaling.

[0237] As a sub-embodiment of this embodiment, the first information block includes information in at least one RRC IE (Information Element).

[0238] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in an RRC IE.

[0239] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in each of the multiple RRC IEs.

[0240] As a sub-embodiment of this embodiment, the first information block is cell-common.

[0241] As a sub-embodiment of this embodiment, the first information block is cell-specific.

[0242] As a sub-embodiment of this embodiment, the first information block is group-common.

[0243] As a sub-embodiment of this embodiment, the first information block is user equipment (UE)-dedicated.

[0244] As a sub-embodiment of this embodiment, the first information block is configured per sub-band.

[0245] As a sub-embodiment of this embodiment, the first information block is configured per (per) BWP (BandWidth Part, partial bandwidth).

[0246] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "tdd".

[0247] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "DL".

[0248] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "UL".

[0249] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "Config".

[0250] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "SBFD".

[0251] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "subband".

[0252] As a sub-embodiment of this embodiment, the name of the RRC signaling carrying the first information block includes "duplex".

[0253] As a sub-embodiment of this embodiment, the first information block is carried by a MAC CE (Medium Access Control layer Control Element).

[0254] As a sub-embodiment of this embodiment, the first information block includes information in at least one MAC CE.

[0255] As an embodiment, the benefits of the above method include: improving the transmission reliability of the information included in the first information block.

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

[0257] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in the MIB (Master Information Block).

[0258] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in SIB1 (System Information Block 1).

[0259] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields included in RMSI (Remaining Minimum System Information).

[0260] As a sub-embodiment of this embodiment, the benefits of the above method include: being conducive to supporting the configuration of the first type of symbols in a scenario before the RRC connection is established.

[0261] As a sub-embodiment of this embodiment, the first information block is carried by dynamic signaling.

[0262] As a sub-embodiment of this embodiment, the first information block is carried by physical layer signaling.

[0263] As a sub-embodiment of this embodiment, the first information block is carried by DCI (Downlink Control Information).

[0264] As a sub-embodiment of this embodiment, the first information block includes information in at least one RRC IE and information in at least one DCI.

[0265] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields in a DCI format.

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

[0267] As a sub-embodiment of this embodiment, the first information block includes part or all of the fields in DCI format2_8.

[0268] As a sub-embodiment of this embodiment, the benefits of the above method include: improving the timeliness of transmission of the information included in the first information block.

[0269] As a sub-embodiment of this embodiment, the first information block is used to configure SBFD (SubBand non-overlapping Full Duplex) time slots or symbols.

[0270] As a sub-embodiment of this embodiment, the first information block is used to configure a time slot or symbol supporting full-duplex.

[0271] As a sub-embodiment of this embodiment, whether the symbols used for SS / PBCH block (SS / PBCH block, synchronization signal and physical broadcast channel block) reception belong to the first category of symbols is configured by the first information block.

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

[0273] As a sub-embodiment of this embodiment, the first information block is received before the uplink and downlink TDD configuration signaling.

[0274] As a sub-embodiment of this embodiment, the first information block is received after the uplink and downlink TDD configuration signaling.

[0275] As a sub-embodiment of this embodiment, the first information block and the uplink and downlink TDD configuration signaling are received simultaneously.

[0276] As an embodiment, the first node receives the first information block.

[0277] As an embodiment, the second node sends the first information block.

[0278] Typically, PBCH (Physical Broadcast CHannel), PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal) form an SS / PBCH block in consecutive symbols.

[0279] As an embodiment, symbols used for SS / PBCH block (synchronization signal and physical broadcast channel block) reception do not belong to the first category of symbols.

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

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

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

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

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

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

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

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

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

[0289] As an embodiment, in terms of link direction, a symbol is indicated as one of an uplink symbol, a downlink symbol, or a flexible symbol.

[0290] As an embodiment, a symbol is indicated as one of an uplink symbol or a downlink symbol in terms of link direction.

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

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

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

[0294] As an embodiment, a symbol in the present application is a single-carrier symbol.

[0295] As an embodiment, a symbol in the present application is a multi-carrier symbol.

[0296] As an embodiment, a symbol in the present application is a SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol.

[0297] As an embodiment, a symbol in the present application is a FBMC (Filter Bank Multi Carrier) symbol.

[0298] As an embodiment, a symbol in the present application is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0299] As an embodiment, a symbol in the present application is obtained by performing OFDM symbol generation on the output of a transform precoding.

[0300] As an embodiment, a symbol in the present application is a DFT-s-OFDM (Discrete Fourier Transform spread OFDM) symbol.

[0301] As an embodiment, a symbol in the present application includes a CP-OFDM (Cyclic Prefix-OFDM) symbol.

[0302] As an embodiment, the statement "the first type of PDSCH depends on the first type of symbols" means that the first type of PDSCH depends on the overlapping of the PDSCH associated with the first receiving group and the first type of symbols.

[0303] As an embodiment, the statement "the first type of PDSCH depends on the first type of symbols" means that the first type of PDSCH depends on which PDSCHs among the PDSCHs associated with the first receiving group overlap with the first type of symbols in the time domain.

[0304] As an embodiment, the statement "the first type of PDSCH depends on the first type of symbols" means that the first type of PDSCH includes a PDSCH overlapping with the first type of symbols.

[0305] As an embodiment, the statement "the first type of PDSCH depends on the first type of symbol" means: the first type of PDSCH includes PDSCH that meets each condition in the first condition set; the first condition set includes: overlapping with at least one of the first type of symbols.

[0306] As an embodiment, the statement "the first type of PDSCH depends on the first type of symbol" means: judging whether the PDSCH associated with the first receiving group is the first type of PDSCH or a PDSCH other than the first type of PDSCH by whether the first condition set is met, and whether the first condition is met depends on the first type of symbol.

[0307] As an embodiment, the first type of PDSCH is a PDSCH that is not received.

[0308] As an embodiment, the first HARQ-ACK information is related to the first type of symbols.

[0309] As an embodiment, the generation of the first HARQ-ACK information depends on the first type of symbols.

[0310] As an embodiment, the generation of the first HARQ-ACK information depends on whether the PDSCH associated with the first receiving group is the first type of PDSCH, and whether the PDSCH associated with the first receiving group is the first type of PDSCH depends on the first type of symbols.

[0311] As an embodiment, the first HARQ-ACK information is HARQ-ACK information for the PDSCH associated with the first receiving group.

[0312] As an embodiment, a PDSCH that does not overlap with the first type of symbols and does not overlap with the uplink symbols indicated by the uplink and downlink TDD configuration signaling does not belong to the first type of PDSCH.

[0313] As an embodiment, a PDSCH that does not overlap with the uplink symbol indicated by the uplink and downlink TDD configuration signaling and only occupies frequency band resources configured for the downlink does not belong to the first type of PDSCH.

[0314] As an embodiment, the first node receives a first DCI format, and the first DCI format schedules at least the multiple PDSCHs associated with the first receiving group.

[0315] Example 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0369] Example 3

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

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

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

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

[0374] As an embodiment, the first information block in the present application is generated in the RRC sublayer 306.

[0375] As an embodiment, the first information block in the present application is generated in the MAC sublayer 302.

[0376] As an embodiment, the first information block in this application is generated by the PHY301.

[0377] As an embodiment, the first DCI format in this application is generated in PHY301.

[0378] As an embodiment, the first PDSCH set in the present application is generated by the PHY351.

[0379] As an embodiment, the first HARQ information in the present application is generated in the PHY 301 or the MAC sublayer 302 .

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

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

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

[0383] Example 4

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0398] 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 uplink and downlink TDD configuration signaling; generates first HARQ-ACK information based on a first receiving group, the first receiving group being associated with multiple PDSCHs; wherein, when the first receiving group is associated with at least one PDSCH other than a first type of PDSCH, the first node assumes that the transport block provided by the first type of PDSCH is correctly received; when the first receiving group is associated only with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbol.

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

[0400] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, and the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving uplink and downlink TDD configuration signaling; generating first HARQ-ACK information based on a first receiving group, and the first receiving group is associated with multiple PDSCHs; wherein, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

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

[0402] 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 uplink and downlink TDD configuration signaling; receives at least first HARQ-ACK information; wherein the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generator of the first HARQ-ACK information assumes that the transport block provided by the first type of PDSCH is correctly received; when the first receiving group is associated only with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbol.

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

[0404] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, which generates actions when executed by at least one processor, the actions including: sending uplink and downlink TDD configuration signaling; receiving at least first HARQ-ACK information; wherein, the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generator of the first HARQ-ACK information assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

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

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

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

[0408] 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 DCI format in this application.

[0409] 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 DCI format in the present application.

[0410] 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 PDSCH set in this application.

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

[0412] 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 generate the first HARQ-ACK information based on the first receiving group in the present application.

[0413] 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 at least the first HARQ-ACK information in the present application.

[0414] Example 5

[0415] Embodiment 5 illustrates a signal transmission flow chart according to an embodiment of the present application, as shown in FIG5 . In FIG5 , the first node U1 and the second node U2 communicate via an air interface. In FIG5 , the steps in the dotted box F1 are optional.

[0416] The first node U1 receives uplink and downlink TDD configuration signaling in step S511; receives the first DCI format in step S51A; receives the first PDSCH set in step S51B; generates first HARQ-ACK information based on the first receiving group in step S51C; and sends at least the first HARQ-ACK information in step S512.

[0417] The second node U2 sends uplink and downlink TDD configuration signaling in step S521; sends a first DCI format in step S52A; sends a first PDSCH set in step S52B; and receives at least the first HARQ-ACK information in step S522.

[0418] In embodiment 5, the first receiving group is associated with multiple PDSCHs, and the first PDSCH set includes the multiple PDSCHs to which the first receiving group is associated; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received, and the generation of the first HARQ-ACK information depends on whether the transmission block provided by at least one PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols; the first type of PDSCH includes PDSCHs that meet each condition in the first condition set; the first condition set includes: overlapping with at least one of the first type of symbols; the first condition set also includes: occupying at least one RB belonging to the target frequency band resources, and the target frequency band resources are configurable.

[0419] As a sub-embodiment of Embodiment 5, the first DCI format schedules the first PDSCH set, and the first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

[0420] As a sub-embodiment of embodiment 5, the first receiving group is a PDSCH receiving group.

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

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

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

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

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

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

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

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

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

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

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

[0432] As an embodiment, the first DCI format is received before the first PDSCH set.

[0433] As an embodiment, the uplink and downlink TDD configuration signaling is received before the first PDSCH set.

[0434] As an embodiment, the first DCI format is a DCI format 1_0.

[0435] As an embodiment, the first DCI format is a DCI format 1_1.

[0436] As an embodiment, the first DCI format is a DCI format 1_2.

[0437] As an embodiment, the first DCI format is a DCI format of either DCI format 1_1 or DCI format 1_2.

[0438] As an embodiment, the first DCI format includes one or more fields in a DCI format.

[0439] As an embodiment, the first DCI format is used to schedule the first PDSCH set.

[0440] As an embodiment, in the present application, the first DCI format supports scheduling multiple PDSCHs.

[0441] As an embodiment, the first DCI format supports PDSCH reception with two transport blocks.

[0442] As an embodiment, the first DCI format includes a modulation and coding scheme (MCS), a new data indicator (NDI), and a redundancy version (RV) field of at least one transport block.

[0443] As an embodiment, whether the first DCI format includes the modulation and coding scheme of two transport blocks, the new data indicator and the redundancy field is configurable.

[0444] As an embodiment, when the first node is configured to receive a PDSCH with two transport blocks, the first DCI format includes a modulation and coding scheme, a new data indicator, and a redundant field for two transport blocks, and supports PDSCH reception with two transport blocks; otherwise, the first DCI format includes a modulation and coding scheme, a new data indicator, and a redundant field for only one transport block, and does not support PDSCH reception with two transport blocks.

[0445] As an embodiment, the first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

[0446] As an embodiment, each PDSCH in the first PDSCH set is associated with one of a plurality of receiving groups according to configuration, and the first receiving group is one of the plurality of receiving groups.

[0447] As an embodiment, each PDSCH in the first PDSCH set is associated with only one receiving group among the multiple receiving groups, and each PDSCH associated with any receiving group among the multiple receiving groups belongs to the first PDSCH set.

[0448] As an embodiment, the benefits of the above method include: reducing the complexity of implementing the first node.

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

[0450] Example 6

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

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

[0453] As an embodiment, the benefits of the above method include: it is facilitating the use of symbols indicated as downlink symbols by the uplink and downlink TDD configuration signaling and available for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0454] 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 belong to the first category of symbols.

[0455] 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 and available for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0456] 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 belong to the first category of symbols.

[0457] 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 and available for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0458] 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 that can be used for uplink transmission belong to the first category of symbols.

[0459] 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 and available for uplink transmission to send physical channels and signals on the uplink, thereby improving the flexibility of uplink scheduling.

[0460] As an embodiment, the first symbol is a symbol indicated as a downlink symbol by the uplink and downlink TDD configuration signaling, and whether the first symbol belongs to the first category of symbols is configurable; if the first symbol can be used for uplink transmission, the first symbol belongs to the first category of symbols; otherwise, the first symbol does not belong to the first category of symbols.

[0461] As an embodiment, the symbol indicated as an uplink symbol by the uplink and downlink TDD configuration signaling does not belong to the first category of symbols.

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

[0463] As an embodiment, whether the symbols used for SS / PBCH block (synchronization signal and physical broadcast channel block) reception belong to the first category of symbols is configurable.

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

[0465] As an embodiment, the symbols used for SS / PBCH block reception do not belong to the first category of symbols.

[0466] Example 7

[0467] Embodiment 7 illustrates a schematic diagram of a first type of PDSCH and a first condition set according to an embodiment of the present application, as shown in FIG7 .

[0468] In embodiment 7, the first type of PDSCH includes a PDSCH that satisfies each condition in a first condition set; the first condition set includes: overlapping with at least one first type of symbol.

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

[0470] As an embodiment, the first condition set includes more than one condition.

[0471] As an embodiment, in the present application, when each condition in the first condition set is satisfied, the first condition set is satisfied; otherwise, the first condition set is not satisfied.

[0472] As an embodiment, the first condition set is used to determine whether the PDSCH associated with the first receiving group is an invalid PDSCH (invalid PDSCH).

[0473] As an embodiment, in the present application, the overlap between a PDSCH and the first type of symbols is viewed from the time domain.

[0474] As an embodiment, the expression "overlapping with at least one of the first-category symbols" means: overlapping with one of the first-category symbols in the time domain.

[0475] As an embodiment, the expression "overlapping with at least one of the first-category symbols" means: overlapping with multiple first-category symbols in the time domain.

[0476] As an embodiment, when the time domain resources allocated to a PDSCH include a first-type symbol, the PDSCH overlaps with the first-type symbol in the time domain.

[0477] As an embodiment, when the time domain resources occupied by a PDSCH overlap with a first-category symbol, the PDSCH overlaps with the first-category symbol in the time domain.

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

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

[0480] As an embodiment, in the present application, any PDSCH only overlaps with the first type of symbols in the time domain, or only overlaps with symbols other than the first type of symbols.

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

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

[0483] As an embodiment, when the time domain resources occupied by a PDSCH overlap with a symbol other than the first category of symbols, the PDSCH overlaps with the symbol other than the first category of symbols in the time domain.

[0484] As an embodiment, when the time domain resources allocated to a PDSCH overlap with a symbol other than the first category of symbols, the PDSCH overlaps with the symbol other than the first category of symbols in the time domain.

[0485] As an embodiment, the first receiving group is associated with a first PDSCH; for the first PDSCH, when the first condition set is met, the first PDSCH belongs to the first type of PDSCH; otherwise, the first PDSCH is a PDSCH outside the first type of PDSCH.

[0486] As an embodiment, the first PDSCH is any PDSCH associated with the first receiving group.

[0487] As an embodiment, the first condition set is used to determine whether the first PDSCH is the first type of PDSCH.

[0488] As an embodiment, the first condition is overlapping with at least one of the first-category symbols. When the first PDSCH does not overlap with any of the first-category symbols, the first condition is not met and the first condition set is not met. When the first PDSCH overlaps with at least one of the first-category symbols, the first condition is met. Whether the first condition set is met is related to whether other conditions in the first condition set are met.

[0489] As an embodiment, the first condition set further includes: occupying at least one RB belonging to the target frequency band resource; and the target frequency band resource is configurable.

[0490] As an embodiment, the expression "occupying at least one RB belonging to the target frequency band resources" means that all occupied frequency domain resources belong to the target frequency band resources.

[0491] As an embodiment, the expression "occupying at least one RB belonging to the target frequency band resources" means that at least part of the occupied frequency domain resources belong to the target frequency band resources.

[0492] As an embodiment, the expression "occupying at least one RB belonging to the target frequency band resources" means that at least one RB in the occupied frequency domain resources belongs to the target frequency band resources.

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

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

[0495] As an embodiment, the target frequency band resources are continuous in the frequency domain.

[0496] As an embodiment, the target frequency band resources are discontinuous in the frequency domain.

[0497] As an embodiment, the target frequency band resources are configured for uplink transmission.

[0498] As an embodiment, the target frequency band resource includes a sub-band for uplink transmission within a BWP (BandWidth Part).

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

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

[0501] As an embodiment, the target frequency band resources are configured by RRC signaling.

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

[0503] As an embodiment, the second condition is to occupy at least one RB belonging to the target frequency band resources. When all the frequency domain resources occupied by the first PDSCH do not belong to the target frequency band resources, the first condition is not met and the first condition set is not met; when the first PDSCH occupies at least one RB belonging to the target frequency band resources, the second condition is met. Whether the first condition set is met is related to whether other conditions in the first condition set are met.

[0504] As an embodiment, the first type of PDSCH also includes a PDSCH that overlaps with the uplink symbol indicated by the uplink and downlink TDD configuration signaling.

[0505] As an embodiment, in the present application, the overlap between a PDSCH and the first type of symbols is viewed from the time domain.

[0506] As an embodiment, in the present application, the overlap between a PDSCH and the uplink symbol indicated by the uplink and downlink TDD configuration signaling is viewed from the time domain.

[0507] As an embodiment, the uplink symbol indicated by the uplink and downlink TDD configuration signaling is a symbol other than the first type of symbols.

[0508] As an embodiment, when the time domain resources allocated to a PDSCH include an uplink symbol indicated by the uplink and downlink TDD configuration signaling, the PDSCH overlaps with the uplink symbol indicated by the uplink and downlink TDD configuration signaling in the time domain.

[0509] As an embodiment, when the time domain resources occupied by a PDSCH overlap with an uplink symbol indicated by the uplink and downlink TDD configuration signaling, the PDSCH overlaps with the uplink symbol indicated by the uplink and downlink TDD configuration signaling in the time domain.

[0510] As an embodiment, when the time domain resources allocated to a PDSCH overlap with an uplink symbol indicated by the uplink / downlink TDD configuration signaling, the PDSCH overlaps with the uplink symbol indicated by the uplink / downlink TDD configuration signaling in the time domain.

[0511] As an embodiment, whether the first PDSCH belongs to the first type of PDSCH depends on the overlap between the first PDSCH and the uplink symbol indicated by the uplink and downlink TDD configuration signaling.

[0512] As an embodiment, when the first PDSCH overlaps with the uplink symbol indicated by the uplink and downlink TDD configuration signaling in the time domain, the first PDSCH belongs to the first type of PDSCH.

[0513] As an embodiment, when the first PDSCH and the uplink symbol indicated by the uplink and downlink TDD configuration signaling do not overlap in the time domain: whether the first PDSCH belongs to the first type of PDSCH also depends on the overlap between the first PDSCH and the first type of symbol.

[0514] As an embodiment, when the first PDSCH does not overlap with the uplink symbol indicated by the uplink and downlink TDD configuration signaling in the time domain: if the first PDSCH overlaps with at least one of the first-type symbols and occupies at least one RB belonging to the target frequency band resources, the first PDSCH belongs to the first-type PDSCH; otherwise, the first PDSCH is a PDSCH other than the first-type PDSCH.

[0515] Example 8

[0516] Example 8 illustrates a schematic diagram of the first HARQ-ACK information and the CBG-based HARQ-ACK information according to an embodiment of the present application, as shown in Figure 8.

[0517] In embodiment 8, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the bit reuse method for generating the first HARQ-ACK information is based on the CBG-based HARQ-ACK information bit.

[0518] As an embodiment, the above method has the following advantages: based on the existing 3GPP technical specification version, the required changes are small, and it is simple and effective.

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

[0520] As an embodiment, the bits for generating the first HARQ-ACK information reuse the method for generating HARQ-ACK information bits based on CBG described in Section 9.1.1 of 3GPP TS 38.213; the expression "reuse" means: replacing some or all parameters and then using them.

[0521] As an embodiment, the number of code blocks in the transport block is replaced by the number of PDSCH receptions scheduled by the DCI format, the maximum number of CBGs is replaced by the maximum number of PDSCH reception groups or TBGs, and then the CBG-based HARQ-ACK information bit generation method described in section 9.1.1 of 3GPP TS 38.213 is used to generate the bits of the first HARQ-ACK information.

[0522] Example 9

[0523] Example 9 illustrates a schematic diagram of generating first HARQ-ACK information according to an embodiment of the present application, as shown in Figure 9.

[0524] In embodiment 9, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generation of the first HARQ-ACK information depends on whether the transport block provided by at least one PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK.

[0525] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, whether the transport block provided by the first type of PDSCH is correctly received does not affect the generation of the first HARQ-ACK information.

[0526] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, it is assumed that the transport block provided by the first type of PDSCH is correctly received.

[0527] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: if the transmission blocks provided by all PDSCHs associated with the first receiving group are correctly received, the first HARQ-ACK information is ACK, otherwise, the first HARQ-ACK information is NACK.

[0528] As an embodiment, the above method has the following advantages: good robustness.

[0529] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: if the transmission block provided by the at least one PDSCH to which the first receiving group is associated is correctly received, the first HARQ-ACK information is ACK, otherwise, the first HARQ-ACK information is NACK.

[0530] Example 10

[0531] Embodiment 10 illustrates a schematic diagram of a first receiving group according to an embodiment of the present application, as shown in FIG10 .

[0532] In embodiment 10, the first receiving group is a PDSCH reception group.

[0533] As an embodiment, the first receiving group is associated with multiple PDSCHs.

[0534] As an embodiment, the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, or is only associated with the first type of PDSCH.

[0535] As an embodiment, the first receiving group includes multiple PDSCH receptions.

[0536] As an embodiment, the multiple PDSCH receptions are for a serving cell.

[0537] As an embodiment, a PDSCH reception in the first receiving group includes at least one transport block.

[0538] As an embodiment, one PDSCH reception in the first receiving group includes only one transport block.

[0539] As an embodiment, one PDSCH reception in the first receiving group includes two transport blocks.

[0540] As an embodiment, in the present application, any PDSCH reception in the first receiving group includes only one transport block, or includes two transport blocks.

[0541] As an embodiment, the first receiving group is any receiving group among the multiple receiving groups.

[0542] As an embodiment, the first receiving group is any receiving group among the multiple receiving groups that is associated with multiple PDSCHs.

[0543] As an embodiment, the multiple receiving groups include at most 1 PDSCH receiving group.

[0544] As an embodiment, the multiple receiving groups include at most 2 PDSCH receiving groups.

[0545] As an embodiment, the multiple receiving groups include at most 4 PDSCH receiving groups.

[0546] As an embodiment, the multiple reception groups include at most 128 PDSCH reception groups.

[0547] As an embodiment, the maximum number of PDSCH reception groups included in the multiple reception groups is configurable.

[0548] As an embodiment, the maximum number of PDSCH receiving groups included in the multiple receiving groups is configured for HARQ time bundling.

[0549] As an embodiment, the first receiving group is a transport block group (TBG).

[0550] As an embodiment, the first receiving group is any transmission block group among multiple transmission block groups.

[0551] As an embodiment, the multiple transport block groups include at most 1 transport block group.

[0552] As an embodiment, the multiple transport block groups include at most 2 transport block groups.

[0553] As an embodiment, the multiple transport block groups include at most 4 transport block groups.

[0554] As an embodiment, the plurality of transport block groups includes at most 128 transport block groups.

[0555] As an embodiment, the maximum number of transport block groups included in the multiple transport block groups is configurable.

[0556] As an embodiment, the maximum number of transport block groups included in the multiple transport block groups is configured for HARQ time bundling.

[0557] As an embodiment, the first receiving group includes multiple transmission blocks, and the multiple transmission blocks are respectively provided by multiple PDSCHs.

[0558] As an embodiment, a PDSCH associated with the first receiving group provides at least one transport block.

[0559] As an embodiment, one PDSCH associated with the first receiving group provides only one transport block.

[0560] As an embodiment, one PDSCH associated with the first receiving group provides two transport blocks.

[0561] As an embodiment, whether a PDSCH associated with the first receiving group provides two transport blocks depends on whether the first node is configured to receive a PDSCH with two transport blocks, and also depends on whether the first node is enabled to transmit two transport blocks.

[0562] As an embodiment, when the first node is configured to receive a PDSCH with two transmission blocks and the first node is enabled to transmit two transmission blocks, one PDSCH associated with the first receiving group provides two transmission blocks; otherwise, one PDSCH associated with the first receiving group provides only one transmission block.

[0563] As an embodiment, in the present application, any PDSCH associated with the first receiving group provides only one transport block, or provides two transport blocks.

[0564] Example 11

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

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

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

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

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

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

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

[0572] 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 Figure 4 of the present application.

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

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

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

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

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

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

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

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

[0581] As an embodiment, the first receiver A01 receives uplink and downlink TDD configuration signaling; the first transmitter A02 generates first HARQ-ACK information based on a first receiving group, and the first receiving group is associated with multiple PDSCHs; wherein, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

[0582] As an embodiment, the first type of PDSCH includes a PDSCH that meets each condition in a first condition set; the first condition set includes: overlapping with at least one first type of symbol.

[0583] As an embodiment, the first condition set further includes: occupying at least one RB belonging to the target frequency band resource; and the target frequency band resource is configurable.

[0584] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the generation of the first HARQ-ACK information depends on whether the transport block provided by at least one PDSCH is correctly received.

[0585] As an embodiment, the first receiver A01 receives a first DCI format and a first PDSCH set, and the first DCI format schedules the first PDSCH set; wherein the first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

[0586] As an embodiment, the first receiving group is a PDSCH receiving group.

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

[0588] As an embodiment, the first transmitter A02 sends at least the first HARQ-ACK information.

[0589] As an embodiment, the first transmitter A02 generates the first HARQ-ACK information block in this application.

[0590] As an embodiment, the first transmitter A02 sends the first HARQ-ACK information block in this application.

[0591] Example 12

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0609] As an embodiment, the second transmitter B01 sends uplink and downlink TDD configuration signaling; the second receiver B02 receives at least first HARQ-ACK information; wherein, the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generator of the first HARQ-ACK information assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

[0610] As an embodiment, the first type of PDSCH includes a PDSCH that meets each condition in a first condition set; the first condition set includes: overlapping with at least one first type of symbol.

[0611] As an embodiment, the first condition set further includes: occupying at least one RB belonging to the target frequency band resource; and the target frequency band resource is configurable.

[0612] As an embodiment, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: the generation of the first HARQ-ACK information depends on whether the transport block provided by at least one PDSCH is correctly received.

[0613] As an embodiment, the second transmitter B02 sends a first DCI format and a first PDSCH set, and the first DCI format schedules the first PDSCH set; wherein the first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

[0614] As an embodiment, the first receiving group is a PDSCH receiving group.

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

[0616] As an embodiment, the second receiver B02 receives the first HARQ-ACK information block in this application.

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

[0618] 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 uplink and downlink TDD configuration signaling; A first transmitter generates first HARQ-ACK information based on a first receiving group, wherein the first receiving group is associated with a plurality of PDSCHs; Among them, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

2. The first node according to claim 1, characterized in that: The first type of PDSCH includes a PDSCH that satisfies each condition in a first condition set; the first condition set includes: overlapping with at least one of the first type of symbols.

3. The first node according to claim 2, characterized in that: The first condition set also includes: occupying at least one RB belonging to the target frequency band resource; and the target frequency band resource is configurable.

4. The first node according to any one of claims 1 to 3, characterized in that: When the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: generation of the first HARQ-ACK information depends on whether a transport block provided by at least one PDSCH is correctly received.

5. The first node according to any one of claims 1 to 4, characterized in that: include: The first receiver receives a first DCI format and a first PDSCH set, wherein the first DCI format schedules the first PDSCH set; The first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

6. The first node according to any one of claims 1 to 5, characterized in that: The first receiving group is a PDSCH receiving group.

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

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends uplink and downlink TDD configuration signaling; A second receiver receives at least first HARQ-ACK information; Among them, the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generator of the first HARQ-ACK information assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

9. The second node according to claim 8, characterized in that: The first type of PDSCH includes a PDSCH that satisfies each condition in a first condition set; the first condition set includes: overlapping with at least one of the first type of symbols.

10. The second node according to claim 9, characterized in that: The first condition set also includes: occupying at least one RB belonging to the target frequency band resource; and the target frequency band resource is configurable.

11. The second node according to any one of claims 8 to 10, characterized in that: When the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: generation of the first HARQ-ACK information depends on whether a transport block provided by at least one PDSCH is correctly received.

12. The second node according to any one of claims 8 to 11, characterized in that: include: The second transmitter sends a first DCI format and a first PDSCH set, wherein the first DCI format schedules the first PDSCH set; The first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

13. The second node according to any one of claims 8 to 12, characterized in that: The first receiving group is a PDSCH receiving group.

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

15. A method in a first node for wireless communication, characterized in that: include: Receiving uplink and downlink TDD configuration signaling; generating first HARQ-ACK information based on a first receiving group, the first receiving group being associated with a plurality of PDSCHs; Among them, when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the first node assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

16. The method in the first node according to claim 15, characterized in that: The first type of PDSCH includes a PDSCH that satisfies each condition in a first condition set; the first condition set includes: overlapping with at least one of the first type of symbols.

17. The method in the first node according to claim 16, characterized in that: The first condition set also includes: occupying at least one RB belonging to the target frequency band resource; and the target frequency band resource is configurable.

18. The method in the first node according to any one of claims 15 to 17, characterized in that: When the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: generation of the first HARQ-ACK information depends on whether a transport block provided by at least one PDSCH is correctly received.

19. The method in the first node according to any one of claims 15 to 18, characterized in that: include: receiving a first DCI format and a first PDSCH set, wherein the first DCI format schedules the first PDSCH set; The first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

20. The method in the first node according to any one of claims 15 to 19, characterized in that: The first receiving group is a PDSCH receiving group.

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

22. A method in a second node for wireless communication, characterized in that: include: Send uplink and downlink TDD configuration signaling; receiving at least first HARQ-ACK information; Among them, the first receiving group is associated with multiple PDSCHs; when the first receiving group is associated with at least one PDSCH other than the first type of PDSCH, the generator of the first HARQ-ACK information assumes that the transmission block provided by the first type of PDSCH is correctly received; when the first receiving group is only associated with the first type of PDSCH, the first HARQ-ACK information is NACK; 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, and the first type of PDSCH depends on the first type of symbols.

23. The method in the second node according to claim 22, characterized in that: The first type of PDSCH includes a PDSCH that satisfies each condition in a first condition set; the first condition set includes: overlapping with at least one of the first type of symbols.

24. The method in the second node according to claim 23, characterized in that: The first condition set also includes: occupying at least one RB belonging to the target frequency band resource; and the target frequency band resource is configurable.

25. The method in the second node according to any one of claims 22 to 24, characterized in that: When the first receiving group is associated with at least one PDSCH other than the first type of PDSCH: generation of the first HARQ-ACK information depends on whether a transport block provided by at least one PDSCH is correctly received.

26. The method in the second node according to any one of claims 22 to 25, characterized in that: include: Send a first DCI format and send a first PDSCH set, where the first DCI format schedules the first PDSCH set; The first PDSCH set includes the multiple PDSCHs associated with the first receiving group.

27. The method in the second node according to any one of claims 22 to 26, characterized in that: The first receiving group is a PDSCH receiving group.

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

Images