Method and device for node used for wireless communication

Abstract

The present application discloses a method and device for a node used for wireless communication. A first receiver receives configuration information of SPS PDSCHs; and the first receiver receives PDSCHs in a first PDSCH set, wherein the first PDSCH set comprises at least one PDSCH among multiple PDSCHs, and the multiple PDSCHs are all SPS PDSCHs in the same time slot. The first PDSCH set is dependent on the overlapping between at least two PDSCHs in a second PDSCH set; and which PDSCHs among the multiple PDSCHs being comprised in the second PDSCH set is related to whether the multiple PDSCHs overlap, in a first type of symbols, with a configured grant PUSCH, and the first type of symbols comprise a symbol which is indicated as a downlink symbol by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

Description

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

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

[0002] Using SPS (Semi-persistent scheduling) and PDSCH (Physical downlink shared channel) for downlink transmission is an effective way to reduce scheduling signaling overhead in wireless communications.

[0003] Summary of the Invention

[0004] When the symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and available for uplink transmission are configured to the UE, how to improve the processing method of the communication node in the scenario where multiple SPS PDSCHs exist in the same time slot is an important issue that needs to be considered in system optimization; the present application discloses a solution to the above problem. The present application can be applied to a variety of wireless communication scenarios, such as scenarios supporting full-duplex communication, scenarios supporting subband non-overlapping full-duplex communication, scenarios supporting only half-duplex communication, eMBB (Enhanced Mobile Broadband), URLLC (Ultra-Reliable Low-Latency Communications), Internet of Vehicles, Internet of Things, etc., and achieve similar technical effects. In addition, the use of a unified solution for different scenarios (including but not limited to scenarios supporting full-duplex communication, scenarios supporting subband non-overlapping full-duplex communication, scenarios supporting only half-duplex communication, eMBB, URLLC, Internet of Vehicles, Internet of Things) can also help reduce hardware complexity and cost, or improve performance. In the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

[0005] As an example, the interpretation of the terms in this application refers to the definitions of the 3GPP specification protocol TS38 series.

[0006] As an example, the interpretation of the terms in this application refers to the definitions of the TS37 series of specification protocols of 3GPP.

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

[0008] Receive SPS PDSCH configuration information;

[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, and the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols, and the first category of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[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: in a scenario supporting simultaneous configuration of SPS PDSCH and configuration of granted PUSCH on the first type of symbols, 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: supporting the simultaneous configuration of the SPS PDSCH and the configuration of the granted PUSCH on the first type of symbols, thereby improving resource utilization efficiency.

[0015] As an embodiment, the above method has the following benefits: it can effectively handle the overlap between the SPS PDSCH and the configured granted PUSCH on the first type of symbols, thereby improving configuration or scheduling flexibility.

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

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

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

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

[0020] The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH configured to be granted in at least one of the first-type symbols, the second PDSCH set does not include the target PDSCH.

[0021] As an embodiment, the benefits of the above method include: ensuring the transmission of the PUSCH granted in the first type of symbols, and improving the transmission efficiency of the uplink.

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

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

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

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

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

[0027] A first RRC signaling is received; the first RRC signaling indicates not to receive an SPS PDSCH that overlaps with a configured PUSCH in the first type of symbols.

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

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

[0030] HARQ-ACK information for the first PDSCH set is sent on a first PUCCH.

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

[0032] The method abandons sending HARQ-ACK information for PDSCHs other than the first PDSCH set among the multiple PDSCHs.

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

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

[0035] Send SPS PDSCH configuration information;

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

[0037] Among them, 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 overlap with the configured granted PUSCH in the first category of symbols, and the first category of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0039] The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH configured to be granted in at least one of the first-type symbols, the second PDSCH set does not include the target PDSCH.

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

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

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

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

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

[0045] A first RRC signaling is sent; the first RRC signaling indicates not to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

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

[0047] HARQ-ACK information for the first PDSCH set is received on a first PUCCH.

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

[0049] A first receiver receives configuration information of an SPS PDSCH;

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

[0051] Among them, 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 overlap with the configured granted PUSCH in the first category of symbols, and the first category of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0053] The second transmitter sends the configuration information of the SPS PDSCH;

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

[0055] Among them, 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 overlap with the configured granted PUSCH in the first category of symbols, and the first category of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

[0066] FIG10 shows a schematic diagram illustrating a first RRC signaling according to an embodiment of the present application;

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

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

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

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

[0071] Example 1

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

[0073] In embodiment 1, the first node in the present application receives configuration information of the SPS PDSCH in step 101; and receives the PDSCH in the first PDSCH set in step 102.

[0074] In embodiment 1, 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 2 PDSCHs in the second PDSCH set, and the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols, and the first category of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0075] As an embodiment, the SPS PDSCH configuration information is configuration information of the RRC layer.

[0076] As an embodiment, the SPS PDSCH configuration information includes at least one SPS-Config.

[0077] As an embodiment, the SPS PDSCH configuration information includes configuration information of the multiple PDSCHs.

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

[0079] As an embodiment, the SPS PDSCH configuration information includes configuration information of the SPS period.

[0080] As an embodiment, the SPS PDSCH configuration information includes configuration information of SPS HARQ (Hybrid automatic repeat request) process IDs (HARQ process IDs).

[0081] As an embodiment, the SPS PDSCH configuration information includes configuration information of an MCS (Modulation and coding scheme) table for SPS.

[0082] As an embodiment, the SPS PDSCH configuration information includes indexes of multiple SPS configurations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0102] As an embodiment, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and depends on whether the multiple PDSCHs overlap with a configured granted PUSCH (Physical uplink shared channel) in the first type of symbols.

[0103] As an embodiment, the statement "Which PDSCHs among the multiple PDSCHs are included in the second PDSCH set is related to whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols" means: the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least the PDSCHs after processing the overlap with the configured granted PUSCH in the first category of symbols.

[0104] As an embodiment, the statement "which PDSCHs among the multiple PDSCHs are included in the second PDSCH set is related to whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols" means: the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least excluding the PDSCHs after the PDSCH that overlaps with the configured granted PUSCH in the first category of symbols.

[0105] As an embodiment, the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least the PDSCHs that have processed the overlap with the symbols indicated as uplink symbols by the uplink and downlink TDD (Time Division Duplex) configuration signaling in the same time slot, and the PDSCHs after overlapping with the configured granted PUSCH in the first category of symbols.

[0106] As an embodiment, the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least the PDSCHs that overlap with the symbols indicated as uplink symbols by the uplink and downlink TDD configuration signaling in the same time slot are processed, and the PDSCHs after the PDSCH that overlaps with the configured granted PUSCH in the first category of symbols are excluded.

[0107] As an embodiment, for any PDSCH among the multiple PDSCHs, whether it overlaps with the configured granted PUSCH in the first type of symbols is in terms of the time domain.

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

[0109] As an embodiment, a PUSCH that is configured to overlap with any PDSCH among the multiple PDSCHs in the time domain occupies at least part of the time domain resources in the same time slot.

[0110] As an embodiment, the statement "Which PDSCHs among the multiple PDSCHs are included in the second PDSCH set is related to whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols" means: Which PDSCHs among the multiple PDSCHs are included in the second PDSCH set is related to whether the multiple PDSCHs overlap with the configured granted PUSCH with a higher priority in the first category of symbols.

[0111] As an embodiment, the statement "which PDSCHs among the multiple PDSCHs are included in the second PDSCH set is related to whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols" means: the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least the PDSCHs after processing the overlap with the configured granted PUSCH with higher priority in the first category of symbols.

[0112] As an embodiment, the statement "which PDSCHs among the multiple PDSCHs are included in the second PDSCH set is related to whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols" means: the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least excluding the PDSCHs after the PDSCH that overlaps with the configured granted PUSCH with a higher priority in the first category of symbols.

[0113] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a configured PUSCH with the same priority in at least one of the first category symbols: the first node determines by itself whether the second PDSCH set includes the target PDSCH.

[0114] As an embodiment, when an SPS PDSCH and a configured and granted PUSCH occupy at least one identical first-type symbol in the time domain, the SPS PDSCH overlaps with the configured and granted PUSCH in at least one first-type symbol.

[0115] As an embodiment, when at least part of the time domain resources included in a first-category symbol is occupied by both an SPS PDSCH and a configured PUSCH, the SPS PDSCH overlaps with the configured PUSCH in at least one first-category symbol.

[0116] As an embodiment, when an SPS PDSCH occupies at least one of the first-category symbols in the time domain and the at least one of the first-category symbols occupied by this SPS PDSCH in the time domain overlaps with a configured and granted PUSCH in the time domain, this SPS PDSCH overlaps with the configured and granted PUSCH in at least one of the first-category symbols.

[0117] As an embodiment, when an SPS PDSCH occupies at least one of the first-category symbols in the time domain and the at least one of the first-category symbols occupied by this SPS PDSCH in the time domain overlaps with at least one symbol occupied by a configured and granted PUSCH in the time domain, this SPS PDSCH overlaps with the configured and granted PUSCH in at least one of the first-category symbols.

[0118] As an embodiment, when the time domain resources occupied by an SPS PDSCH are included in at least one of the first type of symbols and this SPS PDSCH has time domain overlap with a configured PUSCH, this SPS PDSCH overlaps with the configured PUSCH in at least one of the first type of symbols.

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

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

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

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

[0123] As an embodiment, the PUSCH granted by the configuration in this application and the multiple PDSCHs are on the same serving cell.

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

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

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

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

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

[0129] Example 2

[0130] Example 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in FIG2 .

[0131] FIG2 illustrates a diagram of a network architecture 200 for 5G NR, LTE (Long-Term Evolution), and LTE-A (Long-Term Evolution Advanced) systems. The 5G NR or LTE network architecture 200 may be referred to as an EPS (Evolved Packet System) 200 or some other suitable terminology. The EPS 200 may include one or more UEs (User Equipment) 201, an NG-RAN (Next Generation Radio Access Network) 202, an EPC (Evolved Packet Core) / 5G-CN (5G-Core Network) 210, a Home Subscriber Server (HSS) 220, and an Internet service provider 230. The EPS may interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented herein may be extended to networks providing circuit-switched services or other cellular networks. The NG-RAN includes an NR Node B (gNB) 203 and other gNBs 204. The gNB 203 provides user and control plane protocol termination towards the UE 201. The gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). The gNB 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 receive node), or some other appropriate terminology. The gNB 203 provides an access point to the EPC / 5G-CN 210 for the UE 201. Examples of UE 201 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, 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 IoT 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, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology. gNB 203 is connected to EPC / 5G-CN 210 via an S1 / NG interface.EPC / 5G-CN210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / UPF (User Plane Function) 211, other MME / AMF / UPF214, S-GW (Service Gateway) 212 and P-GW (Packet Data Network Gateway) 213. MME / AMF / UPF211 is the control node that handles signaling between UE201 and EPC / 5G-CN210. Generally, MME / AMF / UPF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW212, which itself is connected to P-GW213. P-GW213 provides UE IP address allocation and other functions. P-GW213 is connected to Internet service 230. Internet services 230 include operator-specific Internet protocol services, which may include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

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

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

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

[0135] As an embodiment, the gNB203 is a macrocellular base station.

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

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

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

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

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

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

[0142] Example 3

[0143] 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 (UE, gNB, or RSU in V2X) and a second communication node device (gNB, UE, or RSU in V2X), or the control plane 300 between two UEs, using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the first and second communication node devices, as well as the two UEs, via PHY 301. The L2 layer 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second communication node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides support for inter-zone mobility of the first communication node device between the second communication node devices. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. 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) in a cell between the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in 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 layer) and Layer 2 (L2 layer). The radio protocol architecture for the first communication node device and the second communication node device in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for 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 an SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and data radio bearers (DRBs) to support service diversity. Although not shown in the figure, the first communication node device may have several upper layers above the L2 layer 355, including a network layer (e.g., an IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

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

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

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

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

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

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

[0150] As an embodiment, a PUSCH in the present application is generated in the PHY351.

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

[0152] Example 4

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

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

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

[0156] 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 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based 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 the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier 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, and then provides it to a different antenna 420.

[0157] During transmission from the first communications device 410 to the second communications device 450, each receiver 454 at the second communications device 450 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 receive processor 456 demultiplexes the physical layer data signal and reference signal, 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 streams destined for the second communications 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.

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

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

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

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

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

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

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

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

[0166] 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 acknowledgement (ACK) and / or negative acknowledgement (NACK) protocols for error detection to support HARQ operations.

[0167] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 450 device at least: receives configuration information of the SPS PDSCH; receives the PDSCH in the 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 2 PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0169] 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 configuration information of the SPS PDSCH; 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 2 PDSCHs in the second PDSCH set, the second PDSCH set including which PDSCHs among the plurality of PDSCHs are related to whether the plurality of PDSCHs overlap with the configured granted PUSCH in a first category of symbols, the first category of symbols including symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0171] As an embodiment, the first communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The first communication device 410 device at least: sends configuration information of the SPS PDSCH; sends the PDSCH in the 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 2 PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

[0173] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: sending configuration information of the SPS PDSCH; sending the PDSCH in the first PDSCH set, the first PDSCH set including at least one PDSCH among multiple PDSCHs, the multiple PDSCHs all being SPS PDSCHs in the same time slot; wherein the first PDSCH set depends on the overlap between at least 2 PDSCHs in the second PDSCH set, the second PDSCH set including which PDSCHs among the multiple PDSCHs are related to whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols, the first category of symbols including symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

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

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

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

[0177] 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 configuration information of the SPSPDSCH in this application.

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

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

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

[0181] 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 HARQ-ACK information for the first PDSCH set in the present application on the first PUCCH in the present application.

[0182] 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 HARQ-ACK information for the first PDSCH set in the present application on the first PUCCH in the present application.

[0183] Example 5

[0184] Example 5 illustrates a signal transmission flow chart according to an embodiment of the present application, as shown in FIG5 . In FIG5 , communication between the first node U1 and the second node U2 is performed via an air interface. In FIG5 , the steps within dashed blocks F1 and F2 are optional. In particular, the order of the step pairs {S521, S511} and {S52A, S51A} in FIG5 does not represent a specific temporal sequence.

[0185] The first node U1 receives configuration information of the SPS PDSCH in step S511; receives first RRC signaling in step S51A; receives PDSCH in the first PDSCH set in step S512; and sends HARQ-ACK information for the first PDSCH set on the first PUCCH in step S51B.

[0186] The second node U2 sends configuration information of the SPS PDSCH in step S521; sends a first RRC signaling in step S52A; sends a PDSCH in a first PDSCH set in step S522; and receives HARQ-ACK information for the first PDSCH set on a first PUCCH in step S52B.

[0187] In embodiment 5, the first PDSCH set includes at least one PDSCH among a plurality of PDSCHs, and the plurality of PDSCHs are all SPS in the same time slot. PDSCH; 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 are related to whether the multiple PDSCHs overlap with the configured PUSCH in the first type of symbols, the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission, the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated; the first PDSCH set is a subset of the second PDSCH set, and there are no PDSCHs that overlap with each other in the first PDSCH set; the PDSCHs in the second PDSCH set are: among the multiple PDSCHs, at least the PDSCHs after processing the overlap with the configured PUSCH in the first type of symbols / excluding the PDSCHs that overlap with the configured PUSCH in the first type of symbols.

[0188] As a sub-embodiment of embodiment 5, the first node U1 abandons sending HARQ-ACK information for PDSCHs outside the first PDSCH set among the multiple PDSCHs.

[0189] As a sub-embodiment of embodiment 5, the first RRC signaling indicates that an SPS PDSCH overlapping with a configured granted PUSCH in the first type of symbols is not received.

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

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

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

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

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

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

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

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

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

[0199] As an embodiment, the sending / receiving of the configuration information of the SPS PDSCH occurs before the first RRC signaling.

[0200] As an embodiment, the sending / receiving of the configuration information of the SPS PDSCH is after the first RRC signaling.

[0201] As an embodiment, the configuration information of the SPS PDSCH is sent / received simultaneously with the first RRC signaling.

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

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

[0204] As an embodiment, the uplink / downlink TDD configuration signaling is sent / received before the configuration information of the SPS PDSCH and the first RRC signaling.

[0205] As an embodiment, at least a portion of the uplink / downlink TDD configuration signaling is sent / received after the configuration information of the SPS PDSCH or the first RRC signaling.

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

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

[0208] As an embodiment, the steps in the dashed box F2 exist.

[0209] As an embodiment, the steps in the dashed box F2 do not exist.

[0210] Example 6

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

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

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

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

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

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

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

[0218] Example 7

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

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

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

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

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

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

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

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

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

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

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

[0230] As an embodiment, when the uplink frequency domain resource is configured to one symbol, the one symbol is a symbol that can be used for uplink transmission.

[0231] As an embodiment, when the first node can use the configured uplink frequency domain resources on one symbol to perform uplink transmission, the one symbol is a symbol that can be used for uplink transmission.

[0232] As an embodiment, when the first node can be scheduled for uplink transmission on one symbol, the one symbol is a symbol available for uplink transmission.

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

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

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

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

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

[0238] As an embodiment, whether a symbol determined as a flexible symbol by uplink / downlink TDD configuration signaling is the first type of symbol is configured by RRC signaling.

[0239] As an embodiment, whether a symbol determined as a flexible symbol by the uplink and downlink TDD configuration signaling is the first type of symbol is indicated by a MAC CE.

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

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

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

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

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

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

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

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

[0248] Example 8

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

[0250] In embodiment 8, the PDSCHs in the second PDSCH set are all: among the multiple PDSCHs, at least the PDSCHs after processing the overlap with the configured granted PUSCH in the first type of symbols.

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

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

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

[0254] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the configured granted PUSCH in at least one of the first type symbols, the second PDSCH set does not include the target PDSCH.

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

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

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

[0258] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH does not overlap with the configured granted PUSCH in the first type of symbols:

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

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

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

[0262] 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 the first-type PDSCH; the first frequency domain resource set is configurable.

[0263] As an embodiment, when the target PDSCH occupies at least one first-type symbol in the time domain and all frequency-domain resources occupied by the target PDSCH belong to a first frequency-domain resource set, the target PDSCH is not the first-type PDSCH; the first frequency-domain resource set is configurable.

[0264] 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 not the first type of PDSCH; the first frequency domain resource set is configurable.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0278] As an embodiment, the first frequency domain resource set is configured for full-duplex operation.

[0279] As an embodiment, the benefits of the above method include: being conducive to supporting full-duplex operation.

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

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

[0282] Example 9

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

[0284] In embodiment 9, the PDSCHs in the second PDSCH set are all: among the multiple PDSCHs, at least the PDSCHs after processing the overlap with the PUSCH with higher priority configuration grant in the first type of symbols.

[0285] As an embodiment, the PDSCHs in the second PDSCH set are all: the PDSCHs among the multiple PDSCHs, excluding at least the PDSCH after the PDSCH that overlaps with the PUSCH with a higher priority configuration grant in the first type of symbols.

[0286] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH with a higher priority configuration grant in at least one of the first category symbols, the second PDSCH set does not include the target PDSCH.

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

[0288] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a configured and granted PUSCH with the same priority in at least one of the first category symbols, the second PDSCH set does not include the target PDSCH.

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

[0290] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH does not overlap with a PUSCH with a higher priority configuration grant in the first type of symbols:

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

[0292] In one embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH does not overlap with a PUSCH with a higher priority or the same priority in the first type of symbols:

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

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

[0295] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH does not overlap with the configured granted PUSCH in the first type of symbols:

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

[0297] In one embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH does not overlap with a PUSCH with a higher priority in the first category of symbols and the target PDSCH overlaps with a PUSCH with the same priority in at least one of the first category of symbols:

[0298] When the target PDSCH is a first-category PDSCH, the second PDSCH set does not include the target PDSCH; when the target PDSCH is not the first-category PDSCH, the second PDSCH set includes the target PDSCH.

[0299] In one embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH does not overlap with a PUSCH with a higher priority or the same priority in the first category of symbols and the target PDSCH overlaps with a PUSCH with a lower priority in at least one of the first category of symbols:

[0300] When the target PDSCH is a first-category PDSCH, the second PDSCH set does not include the target PDSCH; when the target PDSCH is not the first-category PDSCH, the second PDSCH set includes the target PDSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0314] 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 the first-type PDSCH; the first frequency domain resource set is configurable.

[0315] As an embodiment, when the target PDSCH occupies at least one of the first-type 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 not the first-type PDSCH; the first frequency domain resource set is configurable.

[0316] 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 not the first type of PDSCH; the first frequency domain resource set is configurable.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0330] As an embodiment, the first frequency domain resource set is configured for full-duplex operation.

[0331] As an embodiment, the benefits of the above method include: being conducive to supporting full-duplex operation.

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

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

[0334] Example 10

[0335] Embodiment 10 illustrates a schematic diagram of the first RRC signaling according to an embodiment of the present application, as shown in FIG10 .

[0336] In embodiment 10, the first node receives first RRC signaling; the first RRC signaling indicates not to receive an SPS PDSCH that overlaps with a configured granted PUSCH in the first type of symbols.

[0337] As an embodiment, the first node considers the impact of the configured granted PUSCH on the second PDSCH set in determining the second PDSCH set only when the first RRC signaling indicates not to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

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

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

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

[0341] As an embodiment, the first node considers the impact of the PUSCH with a higher priority configuration grant on the second PDSCH set in the process of determining the second PDSCH set only when the first RRC signaling indicates that the SPS PDSCH that overlaps with the PUSCH with a higher priority configuration grant in the first category of symbols is not received.

[0342] As an embodiment, the first node considers the impact of the PUSCH with the same priority configuration grant on the second PDSCH set in the process of determining the second PDSCH set only when the first RRC signaling indicates that the SPS PDSCH that overlaps with the PUSCH with the same priority configuration grant in the first category of symbols is not received.

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

[0344] Example 11

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

[0346] In embodiment 11, the first node sends HARQ-ACK (Hybrid automatic repeat request acknowledgement) information for the first PDSCH set on a first PUCCH (Physical uplink control channel).

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

[0348] As an embodiment, the HARQ-ACK information for a PDSCH indicates whether the transport block received in this PDSCH is correctly decoded.

[0349] As an embodiment, the first node only sends HARQ-ACK information for SPS PDSCH on the first PUCCH.

[0350] As an embodiment, the first node abandons sending HARQ-ACK information for PDSCHs outside the first PDSCH set among the multiple PDSCHs.

[0351] As an embodiment, the first node abandons sending HARQ-ACK information for PDSCHs outside the first PDSCH set among the multiple PDSCHs on the first PUCCH.

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

[0353] Example 12

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0370] As an embodiment, the first receiver A01 receives the configuration information of the SPS PDSCH; the first receiver A01 receives the PDSCH in the 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 2 PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols, and the first category of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0371] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the configured granted PUSCH in at least one of the first type symbols, the second PDSCH set does not include the target PDSCH.

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

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

[0374] As an embodiment, the first receiver A01 receives a first RRC signaling; the first RRC signaling indicates not to receive the SPS PDSCH that overlaps with the configured granted PUSCH in the first type of symbols.

[0375] As an embodiment, the first transmitter A02 sends HARQ-ACK information for the first PDSCH set on the first PUCCH.

[0376] As an embodiment, the first transmitter A02 abandons sending HARQ-ACK information for PDSCHs outside the first PDSCH set among the multiple PDSCHs.

[0377] Example 13

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0395] As an embodiment, the second transmitter B01 sends configuration information of the SPS PDSCH; the second transmitter B01 sends the PDSCH in the 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 2 PDSCHs in the second PDSCH set, the second PDSCH set includes which PDSCHs among the multiple PDSCHs and whether the multiple PDSCHs overlap with the configured granted PUSCH in the first category of symbols, and the first category of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

[0396] As an embodiment, the target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with the configured granted PUSCH in at least one of the first type symbols, the second PDSCH set does not include the target PDSCH.

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

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

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

[0400] As an embodiment, the second receiver B02 receives HARQ-ACK information for the first PDSCH set on the first PUCCH.

[0401] Those skilled in the art will appreciate that all or part of the steps in the above method can be performed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, the various module units in the above embodiment can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The first node device in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The second node device in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The user equipment, UE, or terminal in this application includes but is not limited to mobile phones, tablet computers, laptops, network cards, low-power devices, eMTC devices, NB-IoT devices, vehicle-mounted communication devices, aircraft, airplanes, drones, remote-controlled aircraft, and other wireless communication devices. The base station equipment or base station or network side equipment in this application includes but is not limited to macro cell base stations, micro cell base stations, home base stations, relay base stations, eNB, gNB, transmission receiving nodes TRP, GNSS, relay satellites, satellite base stations, aerial base stations, test devices, test equipment, test instruments and other equipment.

[0402] 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 configuration information of the SPS PDSCH; 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 overlap with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

2. The first node according to claim 1, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH configured to be granted in at least one of the first-type symbols, the second PDSCH set does not include the target PDSCH.

3. The first node according to claim 1 or 2, 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.

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

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

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

7. The first node according to claim 6, characterized in that: The first transmitter abandons sending HARQ-ACK information for PDSCHs outside the first PDSCH set among the multiple PDSCHs.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends configuration information of the SPS PDSCH; 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 overlap with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

9. The second node according to claim 8, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH configured to be granted in at least one of the first-type symbols, the second PDSCH set does not include the target PDSCH.

10. The second node according to claim 8 or 9, 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.

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

12. The second node according to any one of claims 8 to 11, characterized in that: The second transmitter sends a first RRC signaling; the first RRC signaling indicates not to receive the SPS PDSCH overlapping with the configured granted PUSCH in the first type of symbols.

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

14. A method in a first node for wireless communication, characterized in that: include: Receive SPS PDSCH configuration information; 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; 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 in the multiple PDSCHs and whether the multiple PDSCHs are in the first type of symbol and the configuration grant The first type of symbols is related to PUSCH overlap, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

15. The method in the first node according to claim 14, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH configured to be granted in at least one of the first-type symbols, the second PDSCH set does not include the target PDSCH.

16. The method in the first node according to claim 14 or 15, 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.

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

18. The method in the first node according to any one of claims 14 to 17, characterized in that: A first RRC signaling is received; the first RRC signaling indicates not to receive the SPS PDSCH overlapping with the configured granted PUSCH in the first type of symbols.

19. The method in the first node according to any one of claims 14 to 18, characterized in that: HARQ-ACK information for the first PDSCH set is sent on a first PUCCH.

20. The method in the first node according to claim 19, characterized in that: The method abandons sending HARQ-ACK information for PDSCHs other than the first PDSCH set among the multiple PDSCHs.

21. A method in a second node for wireless communication, characterized in that: include: Send SPS PDSCH configuration information; 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 overlap with the configured granted PUSCH in the first type of symbols, and the first type of symbols includes symbols indicated as downlink symbols by uplink and downlink TDD configuration signaling and can be used for uplink transmission.

22. The method in the second node according to claim 21, characterized in that: The target PDSCH is one of the multiple PDSCHs; when the target PDSCH overlaps with a PUSCH configured to be granted in at least one of the first-type symbols, the second PDSCH set does not include the target PDSCH.

23. The method in the second node according to claim 21 or 22, 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.

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

25. The method in the second node according to any one of claims 21 to 24, characterized in that: A first RRC signaling is sent; the first RRC signaling indicates not to receive the SPS PDSCH overlapping with the configured granted PUSCH in the first type of symbols.

26. The method in the second node according to any one of claims 21 to 25, characterized in that: HARQ-ACK information for the first PDSCH set is received on a first PUCCH.

Images