Method and apparatus for node used for wireless communication

Abstract

The present application discloses a method and apparatus for a node used for wireless communication. A first receiver receives first RRC signaling and a first information block, wherein at least one symbol is indicated as a downlink symbol by the first RRC signaling; and the first receiver receives a PDSCH in a first PDSCH set, wherein the first PDSCH set comprises at least one PDSCH among a plurality of PDSCHs, and the plurality of PDSCHs are SPS PDSCHs in a same time slot. The first PDSCH set depends on an overlapping condition between at least two PDSCHs in a second PDSCH set; which PDSCHs among the plurality of PDSCHs being comprised in the second PDSCH set is related to whether the plurality of PDSCHs occupy a first type of symbols in a time domain; whether at least one downlink symbol indicated by the first RRC signaling belongs to the first type of symbols depends on the first information block.

Description

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

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

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

[0003] In the NR downlink, Semi-Persistent Scheduling (SPS) is supported. Unlike dynamic scheduling, SPS periodically allocates radio resources to specific terminals, significantly reducing signaling overhead, transmission latency, and terminal power consumption.

[0004] Summary of the Invention

[0005] When a new symbol type is introduced to support a communication mode, how to enhance the processing of multiple SPS PDSCHs (Physical Downlink Shared CHannels) in the same time slot is an important issue worthy of consideration in system design; the present application discloses a solution to the above problem. It should be noted that the present application can be applied to a variety of wireless communication scenarios, such as scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, scenarios supporting only half-duplex modes, etc., and achieve similar technical effects. In addition, the use of a unified solution for different scenarios (including but not limited to scenarios using SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, scenarios supporting only half-duplex modes) can also help reduce hardware complexity and cost, or improve performance. In the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily.

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

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

[0008] receiving first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling;

[0009] Receiving a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH from a plurality of PDSCHs, where the plurality of PDSCHs are all SPS PDSCHs in a same time slot;

[0010] Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

[0011] As an embodiment, the problem to be solved by this application includes: how to improve the utilization efficiency of SPS PDSCH.

[0012] As an embodiment, the problem to be solved by the present application includes: how to determine the SPS PDSCH to be received by the first node among multiple SPS PDSCHs in the same time slot.

[0013] As an embodiment, the problem to be solved by the present application includes: for the scenario where the first type of symbols are configured, how to enhance the processing of multiple SPS PDSCHs in the same time slot.

[0014] As an embodiment, the benefits of the above method include: for the scenario where the first type of symbols are configured, the utilization efficiency of the SPS PDSCH is improved.

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

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

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

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

[0019] The target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

[0020] As an embodiment, the benefits of the above method include: reducing / avoiding interference caused by the transmission of the SPS PDSCH in the first type of symbols to transmissions on frequency domain resources outside the first frequency domain resource set.

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

[0022] Each PDSCH in the second PDSCH set is a PDSCH obtained after at least processing overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

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

[0024] The first PDSCH set is a subset of the second PDSCH set, and there are no overlapping PDSCHs in the first PDSCH set.

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

[0026] The first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

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

[0028] The symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

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

[0030] As an embodiment, the above method has the following benefits: facilitating support for (non-overlapping sub-bands or other types of) full-duplex mode, and enhancing the collision handling capability of multiple SPS PDSCHs in the same time slot in (non-overlapping sub-bands or other types of) full-duplex mode.

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

[0032] Sending a first PUCCH;

[0033] The first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

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

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

[0036] Sending first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling;

[0037] Sending a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH from a plurality of PDSCHs, where the plurality of PDSCHs are all SPS PDSCHs in the same time slot;

[0038] Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

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

[0040] The target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

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

[0042] Each PDSCH in the second PDSCH set is a PDSCH obtained after at least processing overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

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

[0044] The first PDSCH set is a subset of the second PDSCH set, and there are no overlapping PDSCHs in the first PDSCH set.

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

[0046] The first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

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

[0048] The symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

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

[0050] receiving a first PUCCH;

[0051] The first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

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

[0053] A first receiver receives first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling;

[0054] The first receiver receives a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH from a plurality of PDSCHs, where the plurality of PDSCHs are all SPS PDSCHs in a same time slot;

[0055] Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

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

[0057] a second transmitter, transmitting first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling;

[0058] The second transmitter transmits a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH from a plurality of PDSCHs, and the plurality of PDSCHs are all SPS PDSCHs in a same time slot;

[0059] Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0067] FIG7 is a schematic diagram showing the relationship between symbols indicated as downlink symbols by the first RRC signaling and the first type of symbols according to an embodiment of the present application;

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

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

[0070] FIG10 is a schematic diagram illustrating HARQ-ACK feedback performed by a first node according to an embodiment of the present application;

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

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

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

[0074] Example 1

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

[0076] In embodiment 1, the first node in the present application receives a first RRC signaling and a first information block in step 101; and receives a PDSCH in a first PDSCH set in step 102.

[0077] In embodiment 1, at least one symbol is indicated as a downlink symbol by the first RRC signaling; the first PDSCH set includes at least one PDSCH among multiple PDSCHs, and the multiple PDSCHs are all SPS PDSCHs in the same time slot; the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, and the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

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

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

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

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

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

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

[0084] As an embodiment, the first RRC signaling includes time domain configuration information.

[0085] As an embodiment, the first RRC signaling includes UL / DL (Uplink / Downlink) TDD (Time Division Duplex) configuration information.

[0086] As an embodiment, the first RRC signaling includes tdd-UL-DL-ConfigurationCommon.

[0087] As an embodiment, the first RRC signaling is tdd-UL-DL-ConfigurationCommon.

[0088] As an embodiment, the name of the first RRC signaling includes tdd-UL-DL-ConfigurationCommon.

[0089] As an embodiment, the first RRC signaling includes tdd-UL-DL-ConfigurationCommon.

[0090] As an embodiment, the first RRC signaling is tdd-UL-DL-ConfigurationCommon.

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

[0092] As an embodiment, the first RRC signaling is tdd-UL-DL-ConfigurationDedicated.

[0093] As an embodiment, the name of the first RRC signaling includes tdd-UL-DL-ConfigurationDedicated.

[0094] As an embodiment, the first RRC signaling includes tdd-UL-DL-ConfigurationDedicated.

[0095] As an embodiment, the first RRC signaling includes tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0096] As an embodiment, the above method has the following benefits: it is beneficial to optimize the allocation of transmission resources under the condition that at least tdd-UL-DL-ConfigurationDedicated is configured.

[0097] As an embodiment, the first information block includes physical layer signaling.

[0098] As an embodiment, the first information block includes DCI (Downlink Control Information, downlink control information).

[0099] As an embodiment, the first information block includes at least one field in a DCI format.

[0100] As an embodiment, the first information block is DCI.

[0101] As an embodiment, the first information block is a field in a DCI format.

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

[0103] As an embodiment, the first information block includes higher layer signaling.

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

[0105] As an embodiment, the higher layer signaling includes MAC CE.

[0106] As an embodiment, the higher layer includes at least one layer above the physical layer.

[0107] As an embodiment, the first information block includes a MAC CE (Medium Access Control layer Control Element).

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

[0109] As an embodiment, the first information block includes an RRC message (RRC message(s)).

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

[0111] As an embodiment, the first information block is a MAC CE.

[0112] As an embodiment, the first information block is a field in a MAC CE.

[0113] As an embodiment, the first information block is an RRC IE.

[0114] As an embodiment, the first information block is a field in an IE.

[0115] As an embodiment, the first information block is RRC signaling.

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

[0117] As an embodiment, the name of the first information block includes subband.

[0118] As an embodiment, the name of the first information block includes SBFD.

[0119] As an embodiment, the first information block includes configuration information for at least one frequency band resource.

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

[0121] As an embodiment, the first information block includes configuration information of the symbol type.

[0122] As an embodiment, the first information block includes configuration information of resources for full-duplex operation (sub-band non-overlapping or other types).

[0123] As an embodiment, the first information block includes configuration information of resources for full-duplex mode (non-overlapping sub-bands or other types).

[0124] As an embodiment, the first information block does not include tdd-UL-DL-ConfigurationCommon.

[0125] As an embodiment, the first information block is RRC signaling other than the first RRC signaling.

[0126] As an embodiment, the first RRC signaling is received before the first information block.

[0127] As an embodiment, the first RRC signaling is received after the first information block.

[0128] As an embodiment, the first RRC signaling and the first information block are received simultaneously.

[0129] As an embodiment, the first RRC signaling indicates the link direction of at least one symbol.

[0130] As an embodiment, the first RRC signaling indicates a symbol as a downlink symbol (Downlink symbol) or one of the uplink symbols.

[0131] As an embodiment, the first RRC signaling indicates a symbol as one of a downlink symbol, an uplink symbol, or a flexible symbol.

[0132] As an embodiment, the multiple PDSCHs are all SPS (Semi-Persistent Scheduling) PDSCHs.

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

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

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

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

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

[0138] As an embodiment, the multiple PDSCHs are respectively activated by multiple DCIs (Downlink Control Information).

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

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

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

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

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

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

[0145] As an embodiment, each PDSCH in the first PDSCH set is one of the multiple PDSCHs.

[0146] As an embodiment, the PDSCHs in the second PDSCH set are all SPS PDSCHs.

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

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

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

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

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

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

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

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

[0155] As an embodiment, the statement "the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set" means: the steps for determining the first PDSCH set from the second PDSCH set refer to steps 0 (Step 0) to step 3 (Step 3) in Section 5.1 of 3GPP TS 38.214.

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

[0157] As an embodiment, the second PDSCH set includes which PDSCHs among the multiple PDSCHs, depending on whether the multiple PDSCHs occupy the first type of symbols in the time domain.

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

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

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

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

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

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

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

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

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

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

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

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

[0170] As an embodiment, the statement "whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block" means: whether a symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

[0171] As an embodiment, the statement "whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block" means: whether multiple symbols indicated as downlink symbols by the first RRC signaling are the first type of symbols depends on the first information block.

[0172] As an embodiment, the first information block is used to determine whether one or more symbols indicated as downlink symbols by the first RRC signaling are the first type of symbols.

[0173] As an embodiment, whether one or more symbols indicated as downlink symbols by the first RRC signaling are the first type of symbols is determined by the configuration of the first information block.

[0174] As an embodiment, the symbols other than the symbols configured by the first information block to be usable for full-duplex operation (non-overlapping subbands or other types) and indicated as downlink symbols by the first RRC signaling are not the first type of symbols.

[0175] As an embodiment, the symbols configured by the first information block to be usable for (sub-band non-overlapping or other types of) full-duplex operation and indicated as downlink symbols by the first RRC signaling are the first type of symbols.

[0176] As an embodiment, any of the first-category symbols is a symbol configured by the first information block to be usable for (sub-band non-overlapping or other types of) full-duplex operation.

[0177] As an embodiment, the symbols configured by the first information block other than the symbols for the (non-overlapping sub-band or other types) full-duplex mode and indicated as downlink symbols by the first RRC signaling are not the first type of symbols.

[0178] As an embodiment, the symbols configured by the first information block for full-duplex mode (non-overlapping sub-bands or other types) and indicated as downlink symbols by the first RRC signaling are the first type of symbols.

[0179] As an embodiment, any of the first-type symbols is configured by the first information block as a symbol for a (non-overlapping sub-band or other type) full-duplex mode.

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

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

[0182] As an embodiment, a symbol in the present application is an OFDM symbol.

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

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

[0185] As an embodiment, the target PDSCH is one of the multiple PDSCHs; whether the second PDSCH set includes the target PDSCH depends on whether the target PDSCH occupies the first type of symbols in the time domain.

[0186] As an embodiment, the target PDSCH is one of the multiple PDSCHs; whether the second PDSCH set includes the target PDSCH is related to whether the target PDSCH occupies the first type of symbols in the time domain and the frequency domain resources occupied by the target PDSCH.

[0187] As an embodiment, the target PDSCH is one of the multiple PDSCHs; whether the second PDSCH set includes the target PDSCH depends on whether the target PDSCH occupies the first type of symbols in the time domain, and whether the frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set; the first frequency domain resource set is configurable.

[0188] As an embodiment, the benefits of the above method include: it is conducive to achieving: improving the utilization efficiency of the SPS PDSCH occupying the first type of symbols in the time domain while avoiding interference of the transmission of SPS PDSCH in the first type of symbols with the transmission on frequency domain resources outside the first frequency domain resource set.

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

[0190] Example 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0244] Example 3

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

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

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

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

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

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

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

[0252] As an embodiment, a PDSCH in the present application is generated in the PHY 351 .

[0253] As an embodiment, a PUCCH in the present application is generated in the PHY 301 .

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

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

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

[0257] Example 4

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0272] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 450 device at least: receives a first RRC signaling and a first information block, at least one symbol is indicated as a downlink symbol by the first RRC signaling; receives a PDSCH in a first PDSCH set, the first PDSCH set includes at least one PDSCH among a plurality of PDSCHs, the plurality of PDSCHs are all SPS PDSCHs in the same time slot; wherein the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, which PDSCHs among the plurality of PDSCHs included in the second PDSCH set are related to whether the plurality of PDSCHs occupy a first type of symbol in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

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

[0274] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receiving a first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling; receiving a PDSCH in a first PDSCH set, the first PDSCH set including at least one PDSCH among a plurality of PDSCHs, the plurality of PDSCHs being SPS PDSCHs in the same time slot; wherein the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set including which PDSCHs among the plurality of PDSCHs is related to whether the plurality of PDSCHs occupy a first type of symbol in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

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

[0276] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends a first RRC signaling and a first information block, at least one symbol is indicated as a downlink symbol by the first RRC signaling; sends a PDSCH in a first PDSCH set, the first PDSCH set includes at least one PDSCH among a plurality of PDSCHs, the plurality of PDSCHs are all SPS PDSCHs in the same time slot; wherein the first PDSCH set depends on the overlap between at least two PDSCHs in a second PDSCH set, which PDSCHs among the plurality of PDSCHs included in the second PDSCH set are related to whether the plurality of PDSCHs occupy a first type of symbol in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

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

[0278] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, and the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending a first RRC signaling and a first information block, at least one symbol is indicated as a downlink symbol by the first RRC signaling; sending a PDSCH in a first PDSCH set, the first PDSCH set includes at least one PDSCH among multiple PDSCHs, and the multiple PDSCHs are all SPS PDSCHs in the same time slot; wherein, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, and the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

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

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

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

[0282] 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 information block in the present application.

[0283] 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 information block in this application.

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

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

[0286] 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 PUCCH in this application.

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

[0288] Example 5

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

[0290] The first node U1 receives the first RRC signaling and the first information block in step S511; receives the PDSCH in the first PDSCH set in step S512; and sends the first PUCCH in step S51A.

[0291] The second node U2 sends a first RRC signaling and a first information block in step S521; sends a PDSCH in a first PDSCH set in step S522; and receives a first PUCCH in step S52A.

[0292] In embodiment 5, at least one symbol is indicated as a downlink symbol by the first RRC signaling, and the first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, which PDSCHs in the multiple PDSCHs included in the second PDSCH set are related to whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block; the first PDSCH set is a subset of the second PDSCH set, and there are no mutually overlapping PDSCHs in the first PDSCH set; each PDSCH in the second PDSCH set is a PDSCH after at least processing the overlap between the symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot;

[0293] As a sub-embodiment of embodiment 5, the symbols configured by the first information block to be usable for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

[0294] As a sub-embodiment of embodiment 5, the first information block is RRC signaling.

[0295] As a sub-embodiment of embodiment 5, the first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

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

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

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

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

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

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

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

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

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

[0305] As an embodiment, the first information block is received / sent before the first RRC signaling.

[0306] As an embodiment, the first information block is received / sent after the first RRC signaling.

[0307] As an embodiment, the first information block and the first RRC signaling are received / sent together.

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

[0309] As an embodiment, the first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

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

[0311] Example 6

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

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

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

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

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

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

[0318] As an embodiment, the statement "the first PDSCH set depends on the overlapping between at least two PDSCHs in the second PDSCH set" means: the first 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.

[0319] Example 7

[0320] Embodiment 7 illustrates a schematic diagram of the relationship between symbols indicated as downlink symbols by the first RRC signaling and the first type of symbols according to an embodiment of the present application, as shown in FIG7 .

[0321] In embodiment 7, the symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

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

[0323] As an embodiment, the first RRC signaling is tdd-UL-DL-ConfigurationCommon, and the symbols configured by the first information block to be usable for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

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

[0325] As an embodiment, the first RRC signaling is tdd-UL-DL-ConfigurationDedicated, and the symbols configured by the first information block to be usable for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

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

[0327] As an embodiment, the first RRC signaling includes tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and the symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

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

[0329] As an embodiment, any of the first-category symbols is a symbol configured by the first information block to be usable for uplink transmission.

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

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

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

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

[0334] As an embodiment, the expression "can be used for uplink transmission" means: can be used for transmission of UL-SCH (Uplink Shared CHannel(s)).

[0335] As an embodiment, the first symbol is a symbol indicated as a downlink symbol by the first RRC signaling; if the first symbol is configured by the first information block to be available for uplink transmission, the first symbol is the first type of symbol; otherwise, the first symbol is not the first type of symbol.

[0336] As an embodiment, the symbol indicated as an uplink symbol by the first RRC signaling is not the first type of symbol.

[0337] As an embodiment, whether the symbol indicated as a flexible symbol by the first RRC signaling is the first type of symbol is configured by the first information block.

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

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

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

[0341] Example 8

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

[0343] In embodiment 8, the PDSCHs in the second PDSCH set are all: among the multiple PDSCHs, at least the PDSCHs that occupy the first type of symbols in the time domain and occupy at least part of the frequency domain resources that do not belong to the first frequency domain set are processed.

[0344] As an embodiment, the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least excluding the PDSCHs that occupy the first type of symbols in the time domain and occupy at least part of the frequency domain resources that do not belong to the first frequency domain set.

[0345] As an embodiment, the benefits of the above method include: reducing / avoiding interference caused by the transmission of the SPS PDSCH in the first type of symbols to transmissions on frequency domain resources outside the first frequency domain resource set.

[0346] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and all frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set, the target PDSCH is in the second PDSCH set.

[0347] As an embodiment, the benefits of the above method include: improving the utilization efficiency of the SPS PDSCH occupying the first type of symbols in the time domain.

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

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

[0350] As an embodiment, each PDSCH in the second PDSCH set is one of the multiple PDSCHs.

[0351] As an embodiment, each PDSCH in the second PDSCH set is a PDSCH after at least resolving overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

[0352] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps in the time domain with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot, the target PDSCH is not in the second PDSCH set.

[0353] As an embodiment, the target PDSCH is one of the multiple PDSCHs; whether the target PDSCH is in the second PDSCH set is related to whether the frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set; the first frequency domain resource set is configurable.

[0354] As an embodiment, when the target PDSCH occupies at least one of the first-type symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

[0355] As an embodiment, when the target PDSCH occupies at least one of the first category symbols in the time domain and all frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set, the target PDSCH is in the second PDSCH set; the first frequency domain resource set is configurable.

[0356] As an embodiment, when the target PDSCH occupies only the first type of symbols in the time domain and all frequency domain resources occupied by the target PDSCH belong to the first frequency domain resource set, the target PDSCH is in the second PDSCH set; the first frequency domain resource set is configurable.

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

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

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

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

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

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

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

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

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

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

[0367] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain, the target PDSCH is in the second PDSCH set.

[0368] As a sub-embodiment of the above embodiment, when the target PDSCH occupies only symbols outside the first category of symbols in the time domain and does not overlap with the symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot in the time domain, the target PDSCH is not in the second PDSCH set.

[0369] Example 9

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

[0371] In embodiment 9, each PDSCH in the second PDSCH set is a PDSCH after at least resolving overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

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

[0373] As an embodiment, each PDSCH in the second PDSCH set is one of the multiple PDSCHs.

[0374] As an embodiment, each PDSCH in the second PDSCH set processes (resolving) the overlap between symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot, and the PDSCH that occupies the first type of symbols in the time domain and occupies at least part of the frequency domain resources that are not in the first frequency domain set.

[0375] As an embodiment, each PDSCH in the second PDSCH set processes (resolving) the overlap between symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot, and excludes PDSCHs that occupy the first type of symbols in the time domain and occupy at least part of the frequency domain resources that are not in the first frequency domain set.

[0376] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps in the time domain with a symbol indicated as an uplink symbol by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot, the target PDSCH is not in the second PDSCH set.

[0377] Example 10

[0378] Embodiment 10 illustrates a schematic diagram of HARQ-ACK feedback performed by a first node according to an embodiment of the present application, as shown in FIG10 .

[0379] In embodiment 10, the first node sends a first PUCCH (Physical Uplink Control CHannel), and the first PUCCH carries HARQ-ACK (Hybrid Automatic Repeat reQuest Acknowledgement) information for the PDSCH in the first PDSCH set.

[0380] As an embodiment, the HARQ-ACK information for the PDSCH in the first PDSCH set includes HARQ-ACK information for each PDSCH in the first PDSCH set.

[0381] As an embodiment, the HARQ-ACK information for a PDSCH indicates whether the transport block received in the PDSCH has been correctly decoded, including positive acknowledgment (ACK) and / or negative acknowledgment (NACK).

[0382] As an embodiment, the HARQ-ACK information in the present application is represented by HARQ-ACK bits.

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

[0384] As an embodiment, the first PUCCH does not carry HARQ-ACK information for PDSCHs outside the first PDSCH set among the multiple PDSCHs.

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

[0386] As an embodiment, the benefits of the above method include: improving the reliability and efficiency of SPS PDSCH transmission.

[0387] Example 11

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0404] As an embodiment, the first receiver A01 receives a first RRC signaling and a first information block, and at least one symbol is indicated as a downlink symbol by the first RRC signaling; the first receiver A01 receives a PDSCH in a first PDSCH set, and the first PDSCH set includes at least one PDSCH among multiple PDSCHs, and the multiple PDSCHs are all SPS PDSCHs in the same time slot; wherein, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, and which PDSCHs among the multiple PDSCHs included in the second PDSCH set are related to whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

[0405] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

[0406] As an embodiment, each PDSCH in the second PDSCH set is a PDSCH after at least processing the overlap between the symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

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

[0408] As an embodiment, the first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0409] As an embodiment, the symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

[0410] As an embodiment, the first transmitter A02 sends a first PUCCH; wherein the first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

[0411] Example 12

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0429] As an embodiment, the second transmitter B01 sends a first RRC signaling and a first information block, and at least one symbol is indicated as a downlink symbol by the first RRC signaling; the second transmitter B01 sends a PDSCH in a first PDSCH set, and the first PDSCH set includes at least one PDSCH among multiple PDSCHs, and the multiple PDSCHs are all SPS PDSCHs in the same time slot; wherein, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, and which PDSCHs among the multiple PDSCHs included in the second PDSCH set are related to whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

[0430] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

[0431] As an embodiment, each PDSCH in the second PDSCH set is a PDSCH after at least processing the overlap between the symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

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

[0433] As an embodiment, the first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0434] As an embodiment, the symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are the first type of symbols.

[0435] As an embodiment, the second receiver B02 receives a first PUCCH; wherein the first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

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

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

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first RRC signaling and a first information block, wherein at least one symbol is indicated as a downlink symbol by the first RRC signaling; The first receiver receives a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH among a plurality of PDSCHs, and the plurality of PDSCHs are all SPS PDSCHs in a same time slot; Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

2. The first node according to claim 1, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

3. The first node according to claim 1 or 2, characterized in that: Each PDSCH in the second PDSCH set is a PDSCH after at least processing overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

4. The first node according to any one of claims 1 to 3, characterized in that: The first PDSCH set is a subset of the second PDSCH set, and there are no mutually overlapping PDSCHs in the first PDSCH set.

5. The first node according to any one of claims 1 to 4, characterized in that: The first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

6. The first node according to any one of claims 1 to 5, characterized in that: The symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are symbols of the first category.

7. The first node according to any one of claims 1 to 6, characterized in that: include: A first transmitter sends a first PUCCH; The first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling; The second transmitter transmits a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH among a plurality of PDSCHs, and the plurality of PDSCHs are all SPS PDSCHs in a same time slot; Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

9. The second node according to claim 8, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

10. The second node according to claim 8 or 9, characterized in that: Each PDSCH in the second PDSCH set is a PDSCH after at least processing overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

11. The second node according to any one of claims 8 to 10, characterized in that: The first PDSCH set is a subset of the second PDSCH set, and there are no mutually overlapping PDSCHs in the first PDSCH set.

12. The second node according to any one of claims 8 to 11, characterized in that: The first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

13. The second node according to any one of claims 8 to 12, characterized in that: The symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are symbols of the first category.

14. The second node according to any one of claims 8 to 13, characterized in that: include: A second receiver receives a first PUCCH; The first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

15. A method in a first node for wireless communication, characterized in that: include: receiving first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling; Receiving a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH among a plurality of PDSCHs, where the plurality of PDSCHs are all SPS PDSCHs in a same time slot; Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

16. The method in the first node according to claim 15, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

17. The method in the first node according to claim 15 or 16, characterized in that: Each PDSCH in the second PDSCH set is a PDSCH after at least processing overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

18. The method in the first node according to any one of claims 15 to 17, characterized in that: The first PDSCH set is a subset of the second PDSCH set, and there are no mutually overlapping PDSCHs in the first PDSCH set.

19. The method in the first node according to any one of claims 15 to 18, characterized in that: The first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

20. The method in the first node according to any one of claims 15 to 19, characterized in that: The symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are symbols of the first category.

21. The method in the first node according to any one of claims 15 to 20, characterized in that: include: Sending a first PUCCH; The first PUCCH carries HARQ-ACK information for the PDSCH in the first PDSCH set.

22. A method in a second node for wireless communication, characterized in that: include: Sending a first RRC signaling and a first information block, at least one symbol being indicated as a downlink symbol by the first RRC signaling; Sending a PDSCH in a first PDSCH set, where the first PDSCH set includes at least one PDSCH among a plurality of PDSCHs, where the plurality of PDSCHs are all SPS PDSCHs in a same time slot; Among them, the first PDSCH set depends on the overlap between at least two PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs occupy the first type of symbols in the time domain, and whether at least one symbol indicated as a downlink symbol by the first RRC signaling is the first type of symbol depends on the first information block.

23. The method in the second node according to claim 22, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH occupies the first type of symbols in the time domain and at least part of the frequency domain resources occupied by the target PDSCH does not belong to the first frequency domain resource set, the target PDSCH is not in the second PDSCH set; the first frequency domain resource set is configurable.

24. The method in the second node according to claim 22 or 23, characterized in that: Each PDSCH in the second PDSCH set is a PDSCH after at least processing overlap with symbols indicated as uplink symbols by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the same time slot.

25. The method in the second node according to any one of claims 22 to 24, characterized in that: The first PDSCH set is a subset of the second PDSCH set, and there are no mutually overlapping PDSCHs in the first PDSCH set.

26. The method in the second node according to any one of claims 22 to 25, characterized in that: The first RRC signaling is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

27. The method in the second node according to any one of claims 22 to 26, characterized in that: The symbols configured by the first information block as being available for uplink transmission and indicated by the first RRC signaling as downlink symbols are symbols of the first category.

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

Images