Method and apparatus related to SPS pdsch in node used for wireless communication

Abstract

The present application discloses a method and apparatus related to an SPS PDSCH in a node used for wireless communication. A first receiver receives first signaling, the first signaling comprising configuration information of a PUCCH; and the first receiver receives a PDSCH in a target PDSCH set, the target PDSCH set comprising at least one PDSCH in a plurality of PDSCHs. The target PDSCH set depends on overlapping conditions between at least two PDSCHs in a first PDSCH set, and the first PDSCH set comprises which PDSCHs in the plurality of PDSCHs are related to whether the plurality of PDSCHs are overlapped with a first-type PUCCH. The first-type PUCCH is in a first-type time-domain resource, and the first-type time-domain resource is a time-domain resource other than a symbol indicated as uplink by an uplink / downlink TDD configuration signaling.

Description

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

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

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

[0003] In existing NR 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 duplex technologies, specifically the proposed Subband Non-Overlapping Full Duplex (SBFD) mode for gNB (NR Node B). In this mode, the same symbol will be used for uplink in part of the frequency resources and for downlink in another part of the frequency resources, thereby improving resource utilization and reducing latency.

[0004] Using SPS (Semi-persistent scheduling) and PDSCH (Physical downlink shared channel) for downlink transmission is an effective means of reducing control signaling overhead in wireless communications. Summary of the Invention

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

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

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

[0008] receiving first signaling, where the first signaling includes configuration information of a PUCCH;

[0009] receiving a PDSCH in a target PDSCH set, wherein the target PDSCH set includes at least one PDSCH among the plurality of PDSCHs;

[0010] Among them, the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, the first PDSCH set includes which PDSCHs in the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in the first type of time domain resources, and the first type of time domain resources are time domain resources other than the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0011] As an embodiment, the problem to be solved by the present application includes: how to determine an SPS PDSCH to be received among multiple SPS PDSCHs.

[0012] As an embodiment, the problem to be solved by the present application includes: how to enhance the processing of the SPS PDSCH in a system configuration that allows overlap between the SPS PDSCH and the first type of PUCCH.

[0013] As an embodiment, the problem to be solved by this application includes: how to improve resource utilization efficiency.

[0014] As an embodiment, the characteristics of the above method include: the first node determines the first PDSCH set based on whether the multiple PDSCHs overlap with the first type of PUCCH; such characteristics are conducive to resolving the time domain conflict between the transmission of the first type of PUCCH and the reception of SPS PDSCH.

[0015] As an embodiment, the above method has the following benefits: supporting simultaneous configuration of the SPS PDSCH and the first type of PUCCH in the first type of time domain resources, thereby improving resource utilization efficiency.

[0016] As an embodiment, the benefits of the above method include: being able to effectively handle the overlap between the SPS PDSCH and the first type of PUCCH in the first type of time domain resources, thereby improving configuration or scheduling flexibility.

[0017] As an embodiment, the benefits of the above method include: for a system with higher configuration flexibility (allowing overlap between SPS PDSCH and the first type of PUCCH), it is beneficial to ensure the transmission of UCI (Uplink control information) carried by the first type of PUCCH and enhance the robustness of the system.

[0018] As an embodiment, the benefits of the above method include: being conducive to supporting full-duplex operation at least on the base station side.

[0019] As an embodiment, the benefits of the above method include: being conducive to reducing scheduling delay.

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

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

[0022] The PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving overlap with the first type of PUCCH.

[0023] As an embodiment, the benefits of the above method include: being conducive to resolving the time domain conflict between the transmission of the first type of PUCCH and the reception of the SPS PDSCH.

[0024] As an embodiment, the above method has the following benefits: it is helpful to ensure the transmission reliability of the UCI carried by the first type of PUCCH.

[0025] As an embodiment, the benefits of the above method include: it is helpful to reduce the processing complexity of the first node.

[0026] As an embodiment, the benefits of the above method include: reducing the demand for the capabilities of the first node and saving equipment costs.

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

[0028] The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with one of the first-type PUCCHs, the first PDSCH set does not include the target PDSCH.

[0029] As an embodiment, the characteristics of the above method include: the first node determines whether the first PDSCH includes the target PDSCH according to an overlap condition between the target PDSCH and the first type of PUCCH.

[0030] As an embodiment, the benefits of the above method include: ensuring the transmission performance of the first type of PUCCH in the first type of time domain resources, and improving the transmission efficiency of the uplink.

[0031] As an embodiment, the above method has the following benefits: it is helpful to ensure the transmission reliability of the UCI carried by the first type of PUCCH.

[0032] As an embodiment, the benefits of the above method include: it is helpful to reduce the processing complexity of the first node.

[0033] As an embodiment, the benefits of the above method include: reducing the demand for the capabilities of the first node and saving equipment costs.

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

[0035] The target PDSCH set is a subset of the first PDSCH set.

[0036] As an embodiment, the benefits of the above method include: improving the utilization efficiency of the SPS PDSCH.

[0037] As an embodiment, the benefits of the above method include: enhancing the processing capability of multiple SPS PDSCHs in the same time slot.

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

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

[0040] As an embodiment, the benefits of the above method include: improving the reliability of configuration.

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

[0042] One first-type PUCCH overlapped with at least one PDSCH among the multiple PDSCHs is transmitted.

[0043] As an embodiment, the characteristics of the above method include: when the multiple PDSCHs overlap with the first type of PUCCH, the transmission of the first type of PUCCH is prioritized.

[0044] As an embodiment, the benefits of the above method include: being conducive to improving uplink performance.

[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 and 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] Sending first signaling, where the first signaling includes PUCCH configuration information;

[0052] Sending a PDSCH in a target PDSCH set, where the target PDSCH set includes at least one PDSCH among the multiple PDSCHs;

[0053] Among them, the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, the first PDSCH set includes which PDSCHs in the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in the first type of time domain resources, and the first type of time domain resources are time domain resources other than the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

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

[0055] The PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving overlap with the first type of PUCCH.

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

[0057] The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with one of the first-type PUCCHs, the first PDSCH set does not include the target PDSCH.

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

[0059] The target PDSCH set is a subset of the first PDSCH set.

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

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

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

[0063] A first-type PUCCH overlapping with at least one PDSCH among the plurality of PDSCHs is received.

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

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

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

[0067] A first receiver receives first signaling, where the first signaling includes configuration information of a PUCCH;

[0068] The first receiver receives a PDSCH in a target PDSCH set, where the target PDSCH set includes at least one PDSCH among a plurality of PDSCHs;

[0069] Among them, the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, the first PDSCH set includes which PDSCHs in the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in the first type of time domain resources, and the first type of time domain resources are time domain resources other than the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

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

[0071] A second transmitter sends a first signaling, where the first signaling includes configuration information of a PUCCH;

[0072] The second transmitter transmits a PDSCH in a target PDSCH set, where the target PDSCH set includes at least one PDSCH among the multiple PDSCHs;

[0073] Among them, the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, the first PDSCH set includes which PDSCHs in the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in the first type of time domain resources, and the first type of time domain resources are time domain resources other than the symbols indicated as uplink by the uplink and downlink TDD configuration signaling. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0079] FIG6 is a schematic diagram illustrating a situation in which a target PDSCH set depends on an overlap between at least two PDSCHs in a first PDSCH set according to an embodiment of the present application;

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

[0081] FIG8 shows a schematic diagram illustrating a first PDSCH set according to an embodiment of the present application;

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

[0083] FIG10 shows a schematic diagram illustrating a first PDSCH set according to an embodiment of the present application;

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

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

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

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

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

[0089] In embodiment 1, the first node in the present application receives first signaling in step 101; and receives a PDSCH in a target PDSCH set in step 102.

[0090] In embodiment 1, the first signaling includes configuration information of PUCCH; the target PDSCH set includes at least one PDSCH among multiple PDSCHs; the target PDSCH set depends on the overlap between at least 2 PDSCHs in the first PDSCH set, the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0091] As an embodiment, the first signaling includes dynamic signaling.

[0092] As an embodiment, the first signaling includes layer 1 (Layer 1, L1) signaling.

[0093] As an embodiment, the first signaling includes physical layer signaling.

[0094] As an embodiment, the first signaling includes physical layer control signaling.

[0095] As an embodiment, the first signaling includes DCI (Downlink Control Information).

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

[0097] As an embodiment, the first signaling includes a PUCCH resource indicator field in a DCI.

[0098] As an embodiment, the first signaling is transmitted on a downlink.

[0099] As an embodiment, the first signaling is in PDCCH (Physical Downlink Control CHannel, physical downlink control channel)

[0100] is transmitted.

[0101] As an embodiment, the benefits of the above method include: improving the timeliness of transmission of the first signaling.

[0102] As an embodiment, the first signaling includes higher layer signaling.

[0103] As an embodiment, the first signaling includes MAC (Radio Resource Control) signaling.

[0104] As an embodiment, the first signaling includes one or more MAC CEs (Medium Access Control layer Control Element).

[0105] As an embodiment, the first signaling includes one or more fields in a MAC CE.

[0106] As an embodiment, the first signaling includes RRC (Radio Resource Control) signaling.

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

[0108] As an embodiment, the first signaling includes one or more RRC IEs (Radio Resource Control layer Information Element).

[0109] As an embodiment, the first signaling includes one or more fields in an RRC IE.

[0110] As an embodiment, the first signaling is cell-common.

[0111] As an embodiment, the first signaling is cell-specific.

[0112] As an embodiment, the first signaling is group-common.

[0113] As an embodiment, the first signaling is user equipment (UE)-dedicated.

[0114] As an embodiment, the first signaling is configured per subband.

[0115] As an embodiment, the first signaling is configured per (per) BWP (BandWidth Part, partial bandwidth).

[0116] As an embodiment, the first signaling is used to configure common PUCCH resources.

[0117] As an embodiment, the first signaling includes one or more fields in the ServingCellConfigCommon IE.

[0118] As an embodiment, the first signaling includes one or more fields in the BWP-UplinkCommon IE.

[0119] As an embodiment, the first signaling includes one or more fields in the PUCCH-ConfigCommon IE.

[0120] As an embodiment, the first signaling is used to configure dedicated PUCCH resources.

[0121] As an embodiment, the first signaling includes one or more fields in the ServingCellConfig IE.

[0122] As an embodiment, the first signaling includes one or more fields in the BWP-UplinkDedicated IE.

[0123] As an embodiment, the first signaling includes one or more fields in the PUCCH-Config IE.

[0124] As an embodiment, the benefits of the above method include: improving the transmission reliability of the first signaling.

[0125] As an embodiment, the first signaling includes configuration information of PUCCH, including: the first signaling is used to configure PUCCH resources.

[0126] As an embodiment, the first signaling includes configuration information of PUCCH, including: at least one PUCCH resource used by the first type PUCCH is configured by the first signaling.

[0127] As an embodiment, the first signaling includes configuration information of the PUCCH, including: the first signaling at least indicates a time domain resource allocated to one of the first type PUCCHs.

[0128] As an embodiment, the PUCCH configuration information refers to the configuration information of PUCCH resources.

[0129] As an embodiment, the PUCCH configuration information includes a PUCCH format.

[0130] As an embodiment, the PUCCH configuration information includes a PUCCH resource index.

[0131] As an embodiment, the PUCCH configuration information includes configuration information of PUCCH time domain resources.

[0132] As an embodiment, the PUCCH configuration information includes configuration information of PUCCH frequency domain resources.

[0133] As an embodiment, the multiple PDSCHs include at most 8 PDSCHs.

[0134] As an embodiment, the multiple PDSCHs include at most 16 PDSCHs.

[0135] As an embodiment, the multiple PDSCHs include at most 32 PDSCHs.

[0136] As an embodiment, the multiple PDSCHs are respectively configured by multiple SPS-Configs.

[0137] As an embodiment, the multiple PDSCHs are respectively activated by multiple DCIs (Downlink control information).

[0138] As an embodiment, the multiple PDSCHs are on the same serving cell.

[0139] As an embodiment, any PDSCH among the multiple PDSCHs does not overlap with the PDSCH scheduled by the DCI in the time domain.

[0140] As an embodiment, the first node receives all PDSCHs in the target PDSCH set.

[0141] As an embodiment, receiving a PDSCH means: receiving a wireless signal through the PDSCH.

[0142] As an embodiment, receiving a PDSCH means including: receiving at least one transport block in the PDSCH.

[0143] As an embodiment, the PDSCHs in the target PDSCH set are all SPS (Semi-Persistent Scheduling) PDSCHs.

[0144] As an embodiment, the PDSCHs in the first PDSCH set are all SPS PDSCHs.

[0145] As an embodiment, the benefits of the above method include: being conducive to reducing control signaling overhead.

[0146] As an embodiment, any PDSCH in the target PDSCH set is one of the multiple PDSCHs.

[0147] As an embodiment, the overlapping between the at least two PDSCHs in the first PDSCH set is in terms of the time domain.

[0148] As an embodiment, the overlapping condition between the at least two PDSCHs in the first PDSCH set includes: whether one PDSCH in the first PDSCH set overlaps with other PDSCHs in the first PDSCH set in the time domain.

[0149] As an embodiment, the overlapping condition between any two PDSCHs in the first PDSCH set includes: whether the two PDSCHs overlap in the time domain.

[0150] As an embodiment, an SPS PDSCH is a PDSCH without a corresponding PDCCH (Physical downlink control channel) transmission.

[0151] As an embodiment, when one PDSCH in the first PDSCH set overlaps with at least one of the remaining PDSCHs in the first PDSCH set in the time domain and the one PDSCH in the first PDSCH set does not overlap with any of the remaining PDSCHs in the first PDSCH set in the frequency domain, the target PDSCH set includes the one PDSCH in the first PDSCH set; otherwise, the target PDSCH set does not include the one PDSCH in the first PDSCH set.

[0152] As an embodiment, the above method has the following benefits: it is advantageous to improve downlink transmission efficiency by utilizing SPS PDSCHs that overlap in the time domain.

[0153] As an embodiment, when one PDSCH in the first PDSCH set does not overlap with any other PDSCH in the first PDSCH set in the time domain, the target PDSCH set includes the one PDSCH in the first PDSCH set.

[0154] As an embodiment, the overlapping situation between the at least two PDSCHs in the first PDSCH set includes: one PDSCH in the first PDSCH set overlaps with several PDSCHs in the first PDSCH set in the time domain.

[0155] As an embodiment, when one PDSCH in the first PDSCH set overlaps with the remaining up to N PDSCHs in the first PDSCH set in the time domain, the target PDSCH set does not include the one PDSCH in the first PDSCH set; when one PDSCH in the first PDSCH set overlaps with the remaining more than N PDSCHs in the first PDSCH set in the time domain, the target PDSCH set includes the one PDSCH in the first PDSCH set; N is a configurable positive integer greater than 1.

[0156] As an embodiment, the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, including: the steps of determining the target PDSCH set from the first PDSCH set refer to steps 0 (Step 0) to 3 (Step 3) in Section 5.1 of 3GPP TS 38.214.

[0157] As an embodiment, the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH (Physical Uplink Control CHannel).

[0158] As an embodiment, the first PDSCH set includes which PDSCHs in the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, including:

[0159] The PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving overlap with the first type of PUCCH.

[0160] As an embodiment, the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, including: the PDSCHs in the first PDSCH set are: among the multiple PDSCHs, at least excluding (excluding) the PDSCHs after overlapping with the first type of PUCCH.

[0161] As an embodiment, the PDSCHs in the first PDSCH set are all: among the multiple PDSCHs, at least the PDSCHs after resolving the overlap with the symbols indicated as uplink by the uplink and downlink TDD configuration signaling in the same time slot, and the overlap with the first type of PUCCH.

[0162] As an embodiment, the PDSCHs in the first PDSCH set are: among the multiple PDSCHs, at least resolving the overlap with the symbols indicated as uplink by the uplink and downlink TDD configuration signaling in the same time slot, and excluding the PDSCH after the PDSCH overlapping with the first type of PUCCH.

[0163] As an embodiment, for any PDSCH among the multiple PDSCHs, whether it overlaps with the first type of PUCCH is in terms of the time domain.

[0164] As an embodiment, in the present application, the overlap between two or more PDSCHs, or between a PDSCH and a PUCCH, is in terms of the time domain.

[0165] As an embodiment, the first type of PUCCH that overlaps with any PDSCH among the multiple PDSCHs in the time domain occupies at least part of the time domain resources in the same time slot.

[0166] As an embodiment, the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, including: the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH with higher priority.

[0167] As an embodiment, the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, including: the PDSCHs in the first PDSCH set are all: among the multiple PDSCHs, at least the PDSCHs after resolving the overlap with the first type of PUCCH with a higher priority.

[0168] As an embodiment, the first PDSCH set includes which PDSCHs among the multiple PDSCHs and is related to whether the multiple PDSCHs overlap with the first type of PUCCH, including: the PDSCHs in the first PDSCH set are all: among the multiple PDSCHs, at least excluding (excluding) the PDSCHs that overlap with the first type of PUCCH with a higher priority.

[0169] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the first type of PUCCH with the same priority: the first node independently determines whether the first PDSCH set includes the target PDSCH.

[0170] As an embodiment, when an SPS PDSCH and a first type PUCCH occupy at least one same target symbol in the time domain, and the at least one same occupied target symbol is in the first type of time domain resources, the SPS PDSCH overlaps with the first type PUCCH.

[0171] As an embodiment, when at least a portion of the first-type time domain resources is occupied by both an SPS PDSCH and a first-type PUCCH, the SPS PDSCH overlaps with the first-type PUCCH.

[0172] As an embodiment, when an SPS PDSCH occupies at least one target symbol in the first type of time domain resources in the time domain, and at least one of the target symbols in the occupied first type of time domain resources has time domain overlap with a first type of PUCCH, this SPS PDSCH overlaps with this first type of PUCCH.

[0173] As an embodiment, when an SPS PDSCH occupies at least one target symbol in the first type of time domain resources in the time domain, and at least one of the target symbols in the occupied first type of time domain resources overlaps with at least one symbol occupied by a first type PUCCH in the time domain, this SPS PDSCH overlaps with this first type PUCCH.

[0174] As an embodiment, when the time domain resources occupied by an SPS PDSCH are included in the first type of time domain resources, and the SPS PDSCH has a time domain overlap with a first type of PUCCH, the SPS PDSCH overlaps with the first type of PUCCH.

[0175] As an embodiment, when the time domain resources allocated to a PDSCH / PUCCH include one symbol, the PDSCH / PUCCH occupies the symbol in the time domain.

[0176] As an embodiment, when the time domain resources occupied by a PDSCH / PUCCH include one symbol, the PDSCH / PUCCH occupies this symbol in the time domain.

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

[0178] As an embodiment, when a PDSCH / PUCCH overlaps with a symbol in the time domain, the PDSCH / PUCCH occupies the symbol in the time domain.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0205] As an embodiment, the first type of time domain resources includes at least one symbol.

[0206] As an embodiment, the first type of time domain resources are time domain resources other than symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0207] As an embodiment, the symbols indicated as uplink by the uplink and downlink TDD configuration signaling do not belong to the first type of time domain resources.

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

[0209] As an embodiment, the symbols indicated as downlink by the uplink and downlink TDD configuration signaling and available for uplink transmission belong to the first type of time domain resources.

[0210] As an embodiment, the first type of time domain resources is configurable.

[0211] As an embodiment, which symbols indicated as downlink by the uplink and downlink TDD configuration signaling belong to the first type of time domain resources are configurable.

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

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

[0214] As an embodiment, which symbols indicated as downlink by the uplink and downlink TDD configuration signaling do not belong to the first type of time domain resources are configurable.

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

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

[0217] As an embodiment, the first type of time domain resources includes symbols configured to be flexible.

[0218] As an embodiment, whether the symbols indicated as flexible by the uplink and downlink TDD configuration signaling belong to the first type of time domain resources is configurable.

[0219] As an embodiment, there is at least one symbol indicated as flexible by the uplink and downlink TDD configuration signaling and belongs to the first type of time domain resources.

[0220] As an embodiment, the first information block includes configuration information of the first type of time domain resources.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0253] As a sub-embodiment of the above embodiment, the first information block includes part or all of the fields in DCI format 2_10.

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

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

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

[0257] As a sub-embodiment of the above embodiment, whether the symbols used for SS / PBCH block (synchronization signal and physical broadcast channel block) reception belong to the first type of time domain resources is configured by the first information block.

[0258] As a sub-embodiment of the above embodiment, the benefits of the above method include: being conducive to ensuring the reception performance of the SS / PBCH block through reasonable configuration.

[0259] As a sub-embodiment of the above embodiment, the first information block is received before the first signaling.

[0260] As a sub-embodiment of the above embodiment, the first information block is received after the first signaling.

[0261] As a sub-embodiment of the above embodiment, the first information block and the first signaling are received simultaneously.

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

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

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

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

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

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

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

[0269] As an embodiment, the time domain resources occupied by any PUCCH cannot have a portion belonging to the first category of time domain resources and another portion not belonging to the first category of time domain resources.

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

[0271] As an embodiment, a PUCCH is the first type of PUCCH, or is a PUCCH other than the first type of PUCCH.

[0272] As an embodiment, whether a PUCCH is the first type of PUCCH depends on the configuration information of the PUCCH.

[0273] As an embodiment, whether a PUCCH is a PUCCH other than the first type of PUCCH depends on the configuration information of the PUCCH.

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

[0275] As an embodiment, the first type of PUCCH in this application and the multiple PDSCHs are on the same serving cell.

[0276] As an embodiment, the first type of PUCCH in the present application and the multiple PDSCHs are in the same serving cell or different serving cells.

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

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

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

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

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

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

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

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

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

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

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

[0288] As an embodiment, the first node receives the PDSCH in the target PDSCH set.

[0289] As an embodiment, the first node does not receive a PDSCH that belongs to the first PDSCH set and does not belong to the target PDSCH set.

[0290] As an embodiment, the first node does not receive the PDSCH in the multiple PDSCHs that does not belong to the target PDSCH set.

[0291] As an embodiment, there are no overlapping PDSCHs in the target PDSCH set.

[0292] As an embodiment, the meaning that one of the multiple PDSCHs overlaps with one of the first-type PUCCHs includes: the PDSCH overlaps with the PUCCH resources configured for the first-type PUCCH.

[0293] As an embodiment, the meaning that a PDSCH among the multiple PDSCHs does not overlap with a first-type PUCCH includes: this PDSCH does not overlap with the PUCCH resources configured for this first-type PUCCH.

[0294] As an embodiment, the multiple PDSCHs are all SPS PDSCHs.

[0295] As an embodiment, the multiple PDSCHs do not have corresponding PDCCH transmissions.

[0296] As an embodiment, the multiple PDSCHs are all on the same serving cell.

[0297] As an embodiment, the multiple PDSCHs are all PDSCHs in the same time slot.

[0298] As an embodiment, in the present application, the overlap between the multiple PDSCHs and the first type of PUCCH refers to overlap in the time domain.

[0299] As an embodiment, the first PDSCH set includes which PDSCHs among the multiple PDSCHs depend on whether the multiple PDSCHs overlap with the first type of PUCCH.

[0300] As an embodiment, the first PDSCH set includes which PDSCHs in the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, including:

[0301] The PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving overlap with the first type of PUCCH.

[0302] Example 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0329] As an embodiment, the user equipment includes NCR (Network Controlled Repeater)-MT.

[0330] As an embodiment, the user equipment includes NCR-Fwd (Forwarding).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0358] As an embodiment, the base station device includes NCR-Fwd.

[0359] Example 3

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

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

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

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

[0364] As an embodiment, the first signaling in the present application is generated in the MAC sublayer 302.

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

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

[0367] As an embodiment, the PDSCH in this application is generated in the PHY351.

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

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

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

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

[0372] Example 4

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0387] 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 first signaling, the first signaling including configuration information of PUCCH; receives PDSCH in a target PDSCH set, the target PDSCH set including at least one PDSCH among multiple PDSCHs; wherein the target PDSCH set depends on the overlap between at least 2 PDSCHs in the first PDSCH set, the first PDSCH set including which PDSCHs among the multiple PDSCHs is related to whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in a first type of time domain resource, and the first type of time domain resource is a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

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

[0389] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: receiving a first signaling, the first signaling including configuration information of the PUCCH; receiving a PDSCH in a target PDSCH set, the target PDSCH set including at least one PDSCH among multiple PDSCHs; wherein the target PDSCH set depends on the overlap between at least 2 PDSCHs in the first PDSCH set, the first PDSCH set including which PDSCHs among the multiple PDSCHs is related to whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in a first type of time domain resource, and the first type of time domain resource is a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

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

[0391] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends a first signaling, the first signaling including configuration information of a PUCCH; sends a PDSCH in a target PDSCH set, the target PDSCH set including at least one PDSCH among a plurality of PDSCHs; wherein the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, the first PDSCH set including which PDSCHs among the plurality of PDSCHs is related to whether the plurality of PDSCHs overlap with a first type of PUCCH, and one of the first type of PUCCHs is in a first type of time domain resource, the first type of time domain resource being a time domain resource other than a symbol indicated as an uplink by the uplink and downlink TDD configuration signaling.

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

[0393] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: sending a first signaling, the first signaling including the configuration information of the PUCCH; sending a PDSCH in a target PDSCH set, the target PDSCH set including at least one PDSCH among multiple PDSCHs; wherein the target PDSCH set depends on the overlap between at least 2 PDSCHs in the first PDSCH set, the first PDSCH set including which PDSCHs among the multiple PDSCHs is related to whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in a first type of time domain resource, and the first type of time domain resource is a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

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

[0395] 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 signaling in this application.

[0396] 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 signaling in this application.

[0397] 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 PDSCH in the target PDSCH set in the present application.

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

[0399] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to send the first type PUCCH in this application.

[0400] 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, and the memory 476} is used to receive the first type of PUCCH in this application.

[0401] Example 5

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

[0403] The first node U1 receives the first signaling in step S511; receives the PDSCH in the target PDSCH set in step S512; and sends the first-type PUCCH overlapping with at least one PDSCH in the multiple PDSCHs in step S51A.

[0404] The second node U2 sends a first signaling in step S521; sends a PDSCH in a target PDSCH set in step S522; and receives a PUCCH of the first type overlapping with at least one PDSCH in the multiple PDSCHs in step S52A.

[0405] In embodiment 5, the first signaling includes configuration information of PUCCH, and the target PDSCH set includes at least one PDSCH among multiple PDSCHs; the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, and the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH. The first type of PUCCH is configured by higher-layer parameters, and one of the first type of PUCCHs is in the first type of time domain resources, and the first type of time domain resources is the time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling, and the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated; the target PDSCH set is a subset of the first PDSCH set; the PDSCHs in the first PDSCH set are: among the multiple PDSCHs, at least the PDSCH after the overlap with the first type of PUCCH is resolved.

[0406] As a sub-embodiment of embodiment 5, the first node U1 sends a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs.

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

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

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

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

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

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

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

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

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

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

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

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

[0419] As an embodiment, the sending / receiving of the uplink and downlink TDD configuration signaling is after the first signaling.

[0420] As an embodiment, the uplink and downlink TDD configuration signaling and the first signaling are sent / received simultaneously.

[0421] As an embodiment, the sending / receiving of the uplink and downlink TDD configuration signaling occurs before the first information block in this application.

[0422] As an embodiment, the sending / receiving of the uplink and downlink TDD configuration signaling is after the first information block in this application.

[0423] As an embodiment, the uplink and downlink TDD configuration signaling and the first information block in this application are sent / received simultaneously.

[0424] As an embodiment, the multiple PDSCHs are configured by the second node to the first node.

[0425] As an embodiment, the steps in the dashed box F1 exist.

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

[0427] As an embodiment, based on the configuration information of the PUCCH, the second node configures the first type of PUCCH to the first node.

[0428] As an embodiment, the steps in the dashed box F1 do not exist.

[0429] Example 6

[0430] Embodiment 6 illustrates a schematic diagram illustrating a situation in which a target PDSCH set depends on the overlap between at least two PDSCHs in a first PDSCH set according to an embodiment of the present application, as shown in FIG6 .

[0431] In embodiment 6, the target PDSCH set is composed of survivor PDSCHs (survivor PDSCH(s)) obtained by the following steps:

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

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

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

[0435] Step 3: Repeat steps 1 and 2 until Q is an empty set, or j is equal to the number of unicast / multicast PDSCHs supported by the first node in one time slot.

[0436] As an embodiment, the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, including: the target PDSCH set is determined by a first method, and the first method is a method that has an equivalent effect to the method of obtaining the first PDSCH set through steps 0 to 3 in Example 6.

[0437] As an embodiment, the target PDSCH set is a subset of the first PDSCH set, and there are no overlapping PDSCHs in the target PDSCH set.

[0438] Example 7

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

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

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

[0442] As an embodiment, the first type of time domain resources is configurable.

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

[0444] As an embodiment, whether a symbol indicated as downlink by the uplink / downlink TDD configuration signaling is available for uplink transmission is indicated by DCI.

[0445] As an embodiment, the advantages of the above method include: a small delay in the configuration taking effect.

[0446] As an embodiment, whether a symbol indicated as downlink by the uplink / downlink TDD configuration signaling is available for uplink transmission is configured by higher layer signaling.

[0447] As an embodiment, whether a symbol indicated as downlink by the uplink / downlink TDD configuration signaling is available for uplink transmission is indicated by MAC CE.

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

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

[0450] As an embodiment, the capability to be used for uplink transmission includes: being used for at least PUSCH (Physical Uplink Shared CHannel) transmission.

[0451] As an embodiment, the signal that can be used for uplink transmission includes: at least being used for PUCCH (Physical Uplink Control CHannel) transmission.

[0452] As an embodiment, the capability to be used for uplink transmission includes: being used for at least SRS (Sounding Reference Signal) transmission.

[0453] As an embodiment, the channel that can be used for uplink transmission includes: at least one of PUSCH transmission, PUCCH transmission, PRACH (Physical Random Access CHannel) transmission and SRS transmission.

[0454] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for at least two of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0455] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for at least three of PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0456] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for PUSCH transmission, PUCCH transmission, PRACH transmission and SRS transmission.

[0457] As an embodiment, the signal that can be used for uplink transmission includes: signal that can be used for UL-SCH (Uplink Shared Channel(s)) transmission.

[0458] As an embodiment, the symbols indicated as uplink by the uplink and downlink TDD configuration signaling do not belong to the first type of time domain resources.

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

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

[0461] As an embodiment, there is at least one symbol indicated as flexible by uplink and downlink TDD configuration signaling and belongs to the first type of time domain resources.

[0462] As an embodiment, whether a symbol indicated as flexible by uplink and downlink TDD configuration signaling belongs to the first type of time domain resources is configurable.

[0463] As an embodiment, whether a symbol indicated as flexible by uplink and downlink TDD configuration signaling belongs to the first type of time domain resources is configured by RRC signaling.

[0464] As an embodiment, whether a symbol indicated as flexible by the uplink and downlink TDD configuration signaling belongs to the first type of time domain resources is indicated by MAC CE.

[0465] As an embodiment, whether a symbol indicated as flexible by uplink and downlink TDD configuration signaling belongs to the first type of time domain resources is indicated by DCI.

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

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

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

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

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

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

[0472] As an embodiment, the benefits of the above method include: being conducive to optimizing the allocation of transmission resources under the condition that at least one of tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is configured.

[0473] Example 8

[0474] Embodiment 8 illustrates a schematic diagram of a first PDSCH set according to an embodiment of the present application, as shown in FIG8 .

[0475] In embodiment 8, the PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving overlap with the first type of PUCCH.

[0476] As an embodiment, the PDSCHs in the first PDSCH set are all: the PDSCHs among the multiple PDSCHs, excluding at least the PDSCHs that overlap with the first type of PUCCH.

[0477] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the first type of PUCCH, the first PDSCH set does not include the target PDSCH.

[0478] As an embodiment, the above method has the following benefits: in a scenario where the SPS PDSCH and the first type of PUCCH overlap, the transmission performance of the first type of PUCCH is guaranteed, thereby improving the transmission efficiency of the uplink.

[0479] As an embodiment, the target PDSCH is any PDSCH among the multiple PDSCHs.

[0480] As an embodiment, the target PDSCH overlaps with a first-type PUCCH, which means that the target PDSCH overlaps with the first-type PUCCH in at least one symbol indicated as downlink by the uplink-downlink TDD configuration signaling and can be used for uplink transmission.

[0481] As an embodiment, the target PDSCH overlaps with one of the first-type PUCCHs in at least one symbol indicated as downlink by the uplink-downlink TDD configuration signaling and available for uplink transmission, or the target PDSCH does not overlap with one of the first-type PUCCHs.

[0482] As an embodiment, the first node does not want the following situation to occur: the target PDSCH overlaps with one of the first types of PUCCHs, and the target PDSCH and this first type of PUCCH do not overlap in any symbol indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0483] As an embodiment, the multiple PDSCHs have the same priority as the first type of PUCCH.

[0484] As an embodiment, the above method has the following benefits: in a scenario where the SPS PDSCH and the first type of PUCCH with the same priority overlap, the transmission performance of the first type of PUCCH is guaranteed, thereby improving the uplink transmission efficiency.

[0485] As an embodiment, the PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving overlap with the first type of PUCCH with a higher priority.

[0486] As an embodiment, the PDSCHs in the first PDSCH set are all: the PDSCHs among the multiple PDSCHs, excluding at least the PDSCHs that overlap with the first type of PUCCH with a higher priority.

[0487] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the first type of PUCCH with a higher priority, the first PDSCH set does not include the target PDSCH.

[0488] As an embodiment, the benefits of the above method include: ensuring the transmission of the first type of PUCCH with a higher priority, and improving the transmission efficiency of the uplink.

[0489] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the first type of PUCCH with the same priority, the first PDSCH set does not include the target PDSCH.

[0490] As an embodiment, the above method has the following benefits: in a scenario where the SPS PDSCH and the first type of PUCCH with the same priority overlap, the transmission performance of the first type of PUCCH is guaranteed, thereby improving the uplink transmission efficiency.

[0491] As an embodiment, the priority of an SPS PDSCH is predefined.

[0492] As an embodiment, the priority of an SPS PDSCH is configurable.

[0493] As an embodiment, the priority of an SPS PDSCH is configured by higher layer parameters.

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

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

[0496] As an embodiment, the priority of an SPS PDSCH is one of a plurality of different priorities.

[0497] As an embodiment, a priority of the first type PUCCH is predefined.

[0498] As an embodiment, a priority of the first type PUCCH is determined by the first node.

[0499] As an embodiment, the priority of the first type PUCCH is configurable.

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

[0501] As an embodiment, the priority of the first type PUCCH is configured by phy-PriorityIndex.

[0502] As an embodiment, the priority of the first type PUCCH is one of multiple different priorities.

[0503] As an embodiment, when the target PDSCH and a first-type PUCCH have the same priority index, the target PDSCH and the first-type PUCCH have the same priority.

[0504] As an embodiment, when the target PDSCH has a priority index of 1 and one of the first-type PUCCHs has a priority index of 0, the first-type PUCCH has a lower priority than the target PDSCH.

[0505] As an embodiment, when the target PDSCH has a priority index of 0 and one of the first-type PUCCHs has a priority index of 1, the first-type PUCCH has a higher priority than the target PDSCH.

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

[0507] As an embodiment, the priority of the target PDSCH is one of a plurality of predefined or configurable different priorities.

[0508] Example 9

[0509] Embodiment 9 illustrates a schematic diagram of a first PDSCH set according to an embodiment of the present application, as shown in FIG9 .

[0510] In embodiment 9, the PDSCHs in the first PDSCH set are all: among the multiple PDSCHs, at least the PDSCHs after resolving the overlap with the configured granted PUSCH in the first type of time domain resources.

[0511] As an embodiment, the PDSCHs in the first PDSCH set are all: the PDSCHs among the multiple PDSCHs, excluding at least the PDSCH that overlaps with the configured granted PUSCH in the first type of time domain resources.

[0512] As an embodiment, the multiple PDSCHs have the same priority as the configured granted PUSCH.

[0513] As an embodiment, the benefits of the above method include: in the scenario where SPS PDSCH with the same priority and the configured granted PUSCH overlap in the first type of time domain resources, the transmission of the configured granted PUSCH is guaranteed, thereby improving the uplink transmission efficiency.

[0514] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the configured granted PUSCH in the first type of time domain resources, the first PDSCH set does not include the target PDSCH.

[0515] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the configured PUSCH in at least one symbol indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission, the first PDSCH set does not include the target PDSCH.

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

[0517] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the configured PUSCH in at least one symbol indicated as flexible and available for uplink transmission by the uplink and downlink TDD configuration signaling, the first PDSCH set does not include the target PDSCH.

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

[0519] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH is a first-category PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first-category PDSCH and the target PDSCH neither overlaps with the first-category PUCCH nor overlaps with the configured granted PUSCH in the first-category time domain resources, the first PDSCH set includes the target PDSCH; whether the target PDSCH is the first-category PDSCH is related to whether the target PDSCH overlaps with a symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0520] In an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH nor overlaps with the configured granted PUSCH in the first type of time domain resources:

[0521] When the target PDSCH is a first type of PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first type of PDSCH, the first PDSCH set includes the target PDSCH; whether the target PDSCH is the first type of PDSCH is related to whether the target PDSCH overlaps with the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0522] As an embodiment, when the target PDSCH overlaps with a symbol indicated as uplink by uplink / downlink TDD configuration signaling, the target PDSCH is the first type of PDSCH.

[0523] As an embodiment, the benefits of the above method include: reducing / avoiding the interference caused by the transmission of the SPS PDSCH to the symbols indicated as uplink.

[0524] As an embodiment, whether the target PDSCH is the first type of PDSCH is related to whether the frequency domain resources occupied by the target PDSCH belong to a first frequency domain resource set; the first frequency domain resource set is configurable.

[0525] As an embodiment, when at least part of the time domain resources occupied by the target PDSCH belong to the first category of time domain resources and at least part of the frequency domain resources occupied by the target PDSCH do not belong to the first frequency domain resource set, the target PDSCH is the first category of PDSCH; the first frequency domain resource set is configurable.

[0526] As an embodiment, when at least part of the time domain resources occupied by the target PDSCH belong to the first category of time domain resources and all frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set, the target PDSCH is not the first category of PDSCH; the first frequency domain resource set is configurable.

[0527] As an embodiment, when all time domain resources occupied by the target PDSCH belong to the first category of time domain resources and all frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set, the target PDSCH is not the first category of PDSCH; the first frequency domain resource set is configurable.

[0528] As an embodiment, all time domain resources occupied by any PDSCH belong to the first category of time domain resources, or, all time domain resources occupied by any PDSCH do not belong to the first category of time domain resources, or, a part of the time domain resources occupied by any PDSCH belong to the first category of time domain resources, and the other part does not belong to the first category of time domain resources.

[0529] As an embodiment, in the present application, all time domain resources occupied by any PDSCH belong to the first category of time domain resources, or all time domain resources occupied by any PDSCH do not belong to the first category of time domain resources.

[0530] As an embodiment, in the present application, the time domain resources occupied by any PDSCH cannot have a portion belonging to the first category of time domain resources and another portion not belonging to the first category of time domain resources.

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

[0532] As an embodiment, the target PDSCH is any PDSCH among the multiple PDSCHs.

[0533] As an embodiment, the first frequency domain resource set includes at least one RB (Resource block).

[0534] As an embodiment, the first frequency domain resource set includes at least one PRB (Physical resource block).

[0535] As an embodiment, the first frequency domain resource set is continuous in the frequency domain.

[0536] As an embodiment, the first frequency domain resource set is discontinuous in the frequency domain.

[0537] As an embodiment, the first frequency domain resource set is configured for downlink transmission.

[0538] As an embodiment, the first frequency domain resource set includes a sub-band for downlink transmission within a BWP (Bandwidth part).

[0539] As an embodiment, the first set of frequency domain resources is configured for full-duplex operation (sub-band non-overlapping or other types).

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

[0541] As an embodiment, the first frequency domain resource set is configured by RRC signaling.

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

[0543] Example 10

[0544] Embodiment 10 illustrates a schematic diagram of a first PDSCH set according to an embodiment of the present application, as shown in FIG10 .

[0545] In embodiment 10, the PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving overlap with a PUSCH with a higher priority configuration grant in the first type of time domain resources.

[0546] As an embodiment, the PDSCHs in the first PDSCH set are all: the PDSCHs among the multiple PDSCHs, excluding at least the PDSCHs that overlap with the PUSCHs with a higher priority configuration grant in the first type of time domain resources.

[0547] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH with a higher priority configuration grant in the first type of time domain resources, the first PDSCH set does not include the target PDSCH.

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

[0549] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a configured and granted PUSCH with the same priority in at least one of the first-type time domain resources, the first PDSCH set does not include the target PDSCH.

[0550] As an embodiment, the benefits of the above method include: in the scenario where SPS PDSCH with the same priority and the configured granted PUSCH overlap in the first type of time domain resources, the transmission of the configured granted PUSCH is guaranteed, thereby improving the uplink transmission efficiency.

[0551] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH with a higher priority nor overlaps with a configured PUSCH with a higher priority in the first type of time domain resources:

[0552] When the target PDSCH is a first type of PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first type of PDSCH, the first PDSCH set includes the target PDSCH; whether the target PDSCH is the first type of PDSCH is related to whether the target PDSCH overlaps with the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0553] In one embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH with a higher priority or the same priority, nor overlaps with a configured PUSCH with a higher priority or the same priority in the first type of time domain resources:

[0554] When the target PDSCH is a first type of PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first type of PDSCH, the first PDSCH set includes the target PDSCH; whether the target PDSCH is the first type of PDSCH is related to whether the target PDSCH overlaps with the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0555] As an embodiment, the above method has the following benefits: on the premise of ensuring the transmission of the first type of PUCCH with higher priority and the same priority, the resource utilization efficiency of the SPS PDSCH is improved.

[0556] As an embodiment, the above method has the following benefits: on the premise of ensuring the transmission of PUSCHs with higher priority and configurations with the same priority, the resource utilization efficiency of the SPS PDSCH is improved.

[0557] In an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH nor overlaps with the configured granted PUSCH in the first type of time domain resources:

[0558] When the target PDSCH is a first type of PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first type of PDSCH, the first PDSCH set includes the target PDSCH; whether the target PDSCH is the first type of PDSCH is related to whether the target PDSCH overlaps with the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0559] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH with a higher priority nor overlaps with a PUSCH with a higher priority configuration grant in the first type of time domain resources, and the target PDSCH overlaps with the first type of PUCCH with the same priority:

[0560] When the target PDSCH is a first-type PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first-type PDSCH, the first PDSCH set includes the target PDSCH.

[0561] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH with a higher priority nor overlaps with a PUSCH with a higher priority in the first type of time domain resources, and the target PDSCH overlaps with a PUSCH with the same priority in the first type of time domain resources:

[0562] When the target PDSCH is a first-type PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first-type PDSCH, the first PDSCH set includes the target PDSCH.

[0563] As an embodiment, the above method has the following benefits: on the premise of ensuring the transmission of the first type of PUCCH with a higher priority, the resource utilization efficiency of the SPS PDSCH is improved.

[0564] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH with a higher priority or the same priority, nor overlaps with a configured PUSCH with a higher priority or the same priority in the first type of time domain resources, and the target PDSCH overlaps with the first type of PUCCH with a lower priority:

[0565] When the target PDSCH is a first-type PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first-type PDSCH, the first PDSCH set includes the target PDSCH.

[0566] As an embodiment, the above method has the following benefits: on the premise of ensuring the transmission of the PUSCH with a configuration grant having a higher priority, the resource utilization efficiency of the SPS PDSCH is improved.

[0567] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH neither overlaps with the first type of PUCCH with a higher priority or the same priority, nor overlaps with a PUSCH with a higher priority or the same priority in the first type of time domain resources, and the target PDSCH overlaps with a PUSCH with a lower priority in the first type of time domain resources:

[0568] When the target PDSCH is a first-type PDSCH, the first PDSCH set does not include the target PDSCH; when the target PDSCH is not the first-type PDSCH, the first PDSCH set includes the target PDSCH.

[0569] As an embodiment, the above method has the following benefits: on the premise of ensuring the transmission of the first type of PUCCH with higher priority and the same priority, the resource utilization efficiency of the SPS PDSCH is improved.

[0570] As an embodiment, the above method has the following benefits: on the premise of ensuring the transmission of PUSCHs with higher priority and configurations with the same priority, the resource utilization efficiency of the SPS PDSCH is improved.

[0571] As an embodiment, the priority of a PUSCH granted by a configuration is predefined.

[0572] As an embodiment, the priority of a PUSCH granted by a configuration is configurable.

[0573] As an embodiment, the priority of a PUSCH granted by a configuration is configured by a higher layer parameter.

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

[0575] As an embodiment, the priority of a PUSCH granted by a configuration is one of multiple different priorities.

[0576] As an embodiment, when the target PDSCH and a configured granted PUSCH have the same priority index, the target PDSCH and the configured granted PUSCH have the same priority.

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

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

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

[0580] As an embodiment, whether the target PDSCH is the first type of PDSCH depends on whether the target PDSCH overlaps with a symbol indicated as uplink by uplink and downlink TDD configuration signaling.

[0581] As an embodiment, when the target PDSCH overlaps with a symbol indicated as uplink by uplink / downlink TDD configuration signaling, the target PDSCH is the first type of PDSCH.

[0582] As an embodiment, the benefits of the above method include: reducing / avoiding the interference caused by the transmission of the SPS PDSCH to the symbols indicated as uplink.

[0583] As an embodiment, when the target PDSCH does not overlap with a symbol indicated as uplink by uplink / downlink TDD configuration signaling, the target PDSCH is not the first type of PDSCH.

[0584] As an embodiment, whether the target PDSCH is the first type of PDSCH is related to whether the frequency domain resources occupied by the target PDSCH belong to a first frequency domain resource set; the first frequency domain resource set is configurable.

[0585] As an embodiment, when at least part of the time domain resources occupied by the target PDSCH belong to the first category of time domain resources and at least part of the frequency domain resources occupied by the target PDSCH do not belong to the first frequency domain resource set, the target PDSCH is the first category of PDSCH; the first frequency domain resource set is configurable.

[0586] As an embodiment, when at least part of the time domain resources occupied by the target PDSCH belong to the first category of time domain resources and all frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set, the target PDSCH is not the first category of PDSCH; the first frequency domain resource set is configurable.

[0587] As an embodiment, when all time domain resources occupied by the target PDSCH belong to the first category of time domain resources and all frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set, the target PDSCH is not the first category of PDSCH; the first frequency domain resource set is configurable.

[0588] As an embodiment, all time domain resources occupied by any PDSCH belong to the first category of time domain resources, or, all time domain resources occupied by any PDSCH do not belong to the first category of time domain resources, or, a part of the time domain resources occupied by any PDSCH belong to the first category of time domain resources, and the other part does not belong to the first category of time domain resources.

[0589] As an embodiment, in the present application, all time domain resources occupied by any PDSCH belong to the first category of time domain resources, or all time domain resources occupied by any PDSCH do not belong to the first category of time domain resources.

[0590] As an embodiment, in the present application, the time domain resources occupied by any PDSCH cannot have a portion belonging to the first category of time domain resources and another portion not belonging to the first category of time domain resources.

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

[0592] As an embodiment, the target PDSCH is any PDSCH among the multiple PDSCHs.

[0593] As an embodiment, the first frequency domain resource set includes at least one RB.

[0594] As an embodiment, the first frequency domain resource set includes at least one PRB.

[0595] As an embodiment, the first frequency domain resource set is continuous in the frequency domain.

[0596] As an embodiment, the first frequency domain resource set is discontinuous in the frequency domain.

[0597] As an embodiment, the first frequency domain resource set is configured for downlink transmission.

[0598] As an embodiment, the first frequency domain resource set includes a sub-band for downlink transmission within a BWP.

[0599] As an embodiment, the first set of frequency domain resources is configured for full-duplex operation (sub-band non-overlapping or other types).

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

[0601] As an embodiment, the first frequency domain resource set is configured by RRC signaling.

[0602] As an embodiment, the first frequency domain resource set is configured by MAC CE.

[0603] Example 11

[0604] Embodiment 11 illustrates a schematic diagram of the first type of PUCCH according to an embodiment of the present application, as shown in FIG11 .

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

[0606] As an embodiment, the benefits of the above method include: improving the reliability of the first type of PUCCH configuration.

[0607] As an embodiment, the higher layer refers to a layer above the physical layer.

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

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

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

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

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

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

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

[0615] As an embodiment, the first type of PUCCH includes a PUCCH configured for periodic CSI (Channel State Information) reporting.

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

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

[0618] Example 12

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

[0620] In embodiment 12, the first node transmits a PUCCH of the first type that overlaps with at least one PDSCH among the plurality of PDSCHs.

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

[0622] As an embodiment, the benefits of the above method include: reducing interference between uplink and downlink, and improving uplink transmission performance.

[0623] As an embodiment, the sending of a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs includes: sending a first signal on a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs.

[0624] As a sub-embodiment of the above embodiment, the first signal includes a wireless signal.

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

[0626] As a sub-embodiment of the above embodiment, the first signal includes a baseband signal.

[0627] As a sub-embodiment of the above embodiment, the first signal is a transmission signal on an uplink.

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

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

[0630] As a sub-embodiment of the above embodiment, the first signal includes a signal for sending UCI (Uplink Control Information).

[0631] As a sub-embodiment of the above embodiment, the first signal includes a signal for sending HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement) information.

[0632] As a sub-embodiment of the above embodiment, the first signal includes a signal used for sending CSI (Channel state information).

[0633] As a sub-embodiment of the above embodiment, the first signal includes a signal for sending a Scheduling Request (SR).

[0634] As an embodiment, the sending of a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs includes: sending a signal including UCI bits output after at least sequence generation (Sequence generation) and mapping to physical resources (Mapping to physical resources) on a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs.

[0635] As an embodiment, the sending of a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs includes: sending a signal including UCI bits that have been subjected to at least sequence modulation (Sequence modulation) and mapped to physical resources on a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs.

[0636] As an embodiment, the sending of a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs includes: sending a signal including UCI bits that are output after at least scrambling, modulation, and mapping to physical resources on a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs.

[0637] As an embodiment, the sending of a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs includes: sending a signal including UCI bits that are at least scrambled, modulated, transform precoded (Transform precoding), and mapped to physical resources on a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs.

[0638] As an embodiment, the sending of a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs includes: sending a signal including the output of UCI bits after at least scrambling, modulation, block-wise spreading, transform precoding, and mapping to physical resources on a first-type PUCCH overlapping with at least one PDSCH among the multiple PDSCHs.

[0639] As an embodiment, the first node does not wish to receive a PDSCH among the multiple PDSCHs that overlaps with the first type of PUCCH.

[0640] Example 13

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

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

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

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

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

[0646] As an embodiment, the first node device A00 is a UE with relevant configuration supporting full-duplex operation.

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

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

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

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

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

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

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

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

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

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

[0657] As an embodiment, the first receiver A01 receives a first signaling, which includes configuration information of the PUCCH; the first receiver A01 receives a PDSCH in a target PDSCH set, which includes at least one PDSCH among multiple PDSCHs; wherein the target PDSCH set depends on the overlap between at least two PDSCHs in the first PDSCH set, and the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in a first type of time domain resource, and the first type of time domain resource is a time domain resource outside the symbol indicated as uplink by the uplink and downlink TDD configuration signaling.

[0658] As an embodiment, the PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving the overlap with the first type of PUCCH.

[0659] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with one of the first-type PUCCHs, the first PDSCH set does not include the target PDSCH.

[0660] As an embodiment, the target PDSCH set is a subset of the first PDSCH set.

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

[0662] As an embodiment, the first transmitter A02 sends a first-type PUCCH that overlaps with at least one PDSCH among the multiple PDSCHs.

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

[0664] Example 14

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

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

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

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

[0669] As an embodiment, the second node device B00 is a base station supporting full-duplex operation.

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

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

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

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

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

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

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

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

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

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

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

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

[0682] As an embodiment, the second transmitter B01 sends a first signaling, which includes the configuration information of the PUCCH; sends the PDSCH in the target PDSCH set, and the target PDSCH set includes at least one PDSCH among multiple PDSCHs; wherein the target PDSCH set depends on the overlap between at least 2 PDSCHs in the first PDSCH set, and the first PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the first type of PUCCH, and one of the first type of PUCCHs is in the first type of time domain resources, and the first type of time domain resources are time domain resources outside the symbols indicated as uplink by the uplink and downlink TDD configuration signaling.

[0683] As an embodiment, the PDSCHs in the first PDSCH set are all: PDSCHs among the multiple PDSCHs after at least resolving the overlap with the first type of PUCCH.

[0684] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with one of the first-type PUCCHs, the first PDSCH set does not include the target PDSCH.

[0685] As an embodiment, the target PDSCH set is a subset of the first PDSCH set.

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

[0687] As an embodiment, the second receiver B02 receives a first-type PUCCH that overlaps with at least one PDSCH among the multiple PDSCHs.

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

[0689] Those skilled in the art will appreciate that all or part of the steps in the above method can be performed by instructing the 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, the various module units in the above embodiment can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The first node device in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The second node device in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The user equipment, UE, or terminal in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The base station equipment or base station or network side equipment in this application includes but is not limited to macro cell base stations, micro cell base stations, home base stations, relay base stations, eNB, gNB, transmission receiving nodes TRP, GNSS, relay satellites, satellite base stations, aerial base stations, test devices, test equipment, test instruments and other equipment.

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

Claims

1. A first node used for wireless communication, characterized in that, Comprising: A first receiver that receives a first signaling, where the first signaling includes configuration information of PUCCH; The first receiver receives a PDSCH in a target PDSCH set, where the target PDSCH set includes at least one PDSCH among a plurality of PDSCHs; Wherein, the target PDSCH set depends on an overlapping situation between at least two PDSCHs in a first PDSCH set, and the first PDSCH set includes which PDSCHs among the plurality of PDSCHs are related to whether the plurality of PDSCHs overlap with a first type of PUCCH. One first type of PUCCH is in a first type of time domain resource, and the first type of time domain resource is a time domain resource other than symbols indicated as the uplink by uplink-downlink TDD configuration signaling.

2. The first node according to claim 1, wherein The PDSCHs in the first PDSCH set are all: among the plurality of PDSCHs, the PDSCHs that have at least resolved the overlap with the first type of PUCCH.

3. The first node according to claim 1 or 2, characterized in that The target PDSCH is one PDSCH among the plurality of PDSCHs; when the target PDSCH overlaps with a first type of PUCCH, the first PDSCH set does not include the target PDSCH.

4. The first node according to any one of claims 1 to 3, characterized in that, The target PDSCH set is a subset of the first PDSCH set.

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

6. The first node according to any one of claims 1 to 5, characterized in that, Comprising: A first transmitter that transmits a first type of PUCCH that overlaps with at least one PDSCH among the plurality of PDSCHs.

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

8. A second node used for wireless communication, characterized in that, Comprising: A second transmitter that transmits a first signaling, where the first signaling includes configuration information of PUCCH; The second transmitter transmits a PDSCH in a target PDSCH set, where the target PDSCH set includes at least one PDSCH among a plurality of PDSCHs; Wherein, the target PDSCH set depends on an overlapping situation between at least two PDSCHs in a first PDSCH set, and the first PDSCH set includes which PDSCHs among the plurality of PDSCHs are related to whether the plurality of PDSCHs overlap with a first type of PUCCH. One first type of PUCCH is in a first type of time domain resource, and the first type of time domain resource is a time domain resource other than symbols indicated as the uplink by uplink-downlink TDD configuration signaling.

9. A method in a first node for use in wireless communication, characterized in that, Comprising: Receiving a first signaling, where the first signaling includes configuration information of PUCCH; Receiving a PDSCH in a target PDSCH set, where the target PDSCH set includes at least one PDSCH among a plurality of PDSCHs; Among them, the target PDSCH set depends on the overlapping situation between at least two PDSCHs in the first PDSCH set. The first PDSCH set includes which PDSCHs among the multiple PDSCHs are related to whether the multiple PDSCHs overlap with the first type of PUCCH. One first type of PUCCH is in the first type of time domain resource, and the first type of time domain resource is the time domain resource other than the symbols indicated as the uplink by the uplink and downlink TDD configuration signaling.

10. A method in a second node used for wireless communication, characterized in that, Including: Sending a first signaling, where the first signaling includes the configuration information of the PUCCH; Sending a PDSCH in the target PDSCH set, where the target PDSCH set includes at least one PDSCH among the multiple PDSCHs; Among them, the target PDSCH set depends on the overlapping situation between at least two PDSCHs in the first PDSCH set. The first PDSCH set includes which PDSCHs among the multiple PDSCHs are related to whether the multiple PDSCHs overlap with the first type of PUCCH. One first type of PUCCH is in the first type of time domain resource, and the first type of time domain resource is the time domain resource other than the symbols indicated as the uplink by the uplink and downlink TDD configuration signaling.

Images