Pdsch-related method and apparatus in node used for wireless communication

Abstract

The present application discloses a PDSCH-related method and apparatus in a node used for wireless communication. A first receiver receives first signaling, the first signaling being used for scheduling a first PDSCH; and the first receiver receives the first PDSCH, wherein configuration parameters followed by REs for the rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type at least comprises full duplex and non-full duplex.

Description

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

[0001] This application claims priority to a Chinese patent application filed with the Patent Office of China on March 25, 2024, with application number 202410347662.X and application name “A method and device related to PDSCH in a node used for wireless communication”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] In existing NR (New Radio) systems, spectrum resources are statically divided into FDD (Frequency Division Duplex) and TDD (Time Division Duplex) spectrum. For TDD spectrum, both base stations and user equipment (UE) operate in half-duplex mode. This half-duplex mode avoids self-interference and mitigates the impact of cross-link interference (CLI), but it also leads to reduced resource utilization and increased latency. To address these issues, supporting flexible duplex modes or variable link directions (uplink, downlink, or flexible) in TDD or FDD spectrum is a possible solution. The 3rd Generation Partnership Project (3GPP) has agreed to conduct research on duplex technologies, specifically subband non-overlapping full-duplex (SBFD) mode for gNBs (NR Node Bs). Optimizing system design accordingly is a key component of this research.

[0004] PDSCH (Physical Downlink Shared Channel) transmission is an important aspect in wireless communications. Summary of the Invention

[0005] How to optimize the rate matching of PDSCH is a key issue that needs to be considered in system design; the present application discloses a solution to the above problem. It should be noted that the present application can be applicable to a variety of wireless communication scenarios, such as scenarios using the SBFD mode, scenarios using other types of full-duplex modes other than SBFD, scenarios using more flexible duplex modes, etc., and achieve similar technical effects. In addition, the use of a unified solution for different scenarios (including but not limited to scenarios using the SBFD mode, scenarios using other types of full-duplex modes other than SBFD, and scenarios using more flexible duplex modes) can also help reduce hardware complexity and cost, or improve performance. In the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

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

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

[0008] receiving first signaling, where the first signaling schedules a first PDSCH;

[0009] receiving the first PDSCH;

[0010] The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

[0011] As an embodiment, the problem to be solved by the present application includes: how to determine REs used for rate matching of PDSCH in a system configured with full-duplex symbols.

[0012] As an embodiment, the problem to be solved by the present application includes: how to optimize the resource mapping of the first PDSCH.

[0013] As an embodiment, the benefits of the above method include: being conducive to improving the efficiency of a communication system configured with full-duplex symbols.

[0014] As an embodiment, the above method has the following benefits: it is possible to apply different configuration parameters to different symbol allocations, which is beneficial for optimizing PDSCH rate matching and enhancing PDSCH transmission performance.

[0015] As an embodiment, the benefits of the above method include: being conducive to optimizing system scheduling.

[0016] As an embodiment, the advantages of the above method include: good compatibility with existing 3GPP protocols and small workload for standardization.

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

[0018] Whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, and the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

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

[0020] When at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0021] As an embodiment, the above method has the following benefits: it is able to fully map the PDSCH to available resources according to the symbol type of the symbols allocated to the PDSCH, which is beneficial to improving resource utilization efficiency.

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

[0023] The REs used for rate matching of the first PDSCH depend on whether a first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, the first parameter being a configuration parameter for PDSCH rate matching for full-duplex symbols.

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

[0025] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

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

[0027] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

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

[0029] The symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

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

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

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

[0033] Sending first signaling, where the first signaling schedules a first PDSCH;

[0034] Sending the first PDSCH;

[0035] The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

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

[0037] Whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, and the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

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

[0039] When at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

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

[0041] The REs used for rate matching of the first PDSCH depend on whether a first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, the first parameter being a configuration parameter for PDSCH rate matching for full-duplex symbols.

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

[0043] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

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

[0045] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

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

[0047] The symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

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

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

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

[0051] A first receiver receives a first signaling, where the first signaling schedules a first PDSCH;

[0052] The first receiver receives the first PDSCH;

[0053] The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

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

[0055] A second transmitter sends a first signaling, where the first signaling schedules a first PDSCH;

[0056] The second transmitter sends the first PDSCH;

[0057] The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0064] FIG6 shows a schematic diagram illustrating REs used for rate matching of the first PDSCH according to one embodiment of the present application;

[0065] FIG7 shows a schematic diagram illustrating REs used for rate matching of the first PDSCH according to one embodiment of the present application;

[0066] FIG8 is a schematic diagram illustrating that the configuration parameters followed by REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH according to one embodiment of the present application;

[0067] FIG9 is a schematic diagram illustrating that the configuration parameters followed by REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH according to one embodiment of the present application;

[0068] FIG10 shows a schematic diagram illustrating a first information block according to an embodiment of the present application;

[0069] FIG11 is a schematic diagram illustrating a full-duplex symbol and a non-full-duplex symbol according to an embodiment of the present application;

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

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

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

[0073] Example 1

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

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

[0076] In embodiment 1, the first signaling schedules the first PDSCH; the configuration parameters followed by the REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

[0077] As an embodiment, the first signaling is physical layer signaling.

[0078] As an embodiment, the first signaling is DCI (Downlink control information).

[0079] As an embodiment, the first signaling is in DCI format.

[0080] As an embodiment, the first signaling is PDCCH (Physical Downlink Control Channel).

[0081] As an embodiment, the advantages of the above method include: small scheduling delay.

[0082] As an embodiment, the first signaling provides downlink assignment.

[0083] As an embodiment, the first signaling is signaling for scheduling the first PDSCH.

[0084] As an embodiment, the first signaling schedules the first PDSCH, including: the first signaling dynamically schedules the first PDSCH.

[0085] As an embodiment, the first signaling schedules the first PDSCH, including: the first PDSCH is an SPS PDSCH (Semi-Persistent Scheduling PDSCH, semi-persistent scheduling PDSCH), and the first signaling is used to configure the semi-persistent scheduling corresponding to the first PDSCH.

[0086] As an embodiment, the REs used for rate matching of the first PDSCH include multiple REs (Resource Elements).

[0087] As an embodiment, the RE used for rate matching of the first PDSCH includes: REs (Resource Element(s)) declared as not available for PDSCH in the physical resource blocks corresponding to the virtual resource blocks allocated to the first PDSCH, as indicated by the configuration parameters for PDSCH rate matching.

[0088] As an embodiment, the REs used for rate matching of the first PDSCH include: REs declared as unavailable for PDSCH in the resource mapping of the first PDSCH and indicated by the configuration parameters followed by the REs used for rate matching of the first PDSCH.

[0089] As an embodiment, the RE used for rate matching of the first PDSCH includes: REs declared as unavailable for PDSCH in the physical resource block corresponding to the virtual resource block allocated to the first PDSCH, as indicated by the configuration parameters followed by the RE used for rate matching of the first PDSCH.

[0090] As an embodiment, a configuration parameter for PDSCH rate matching is a parameter configured for performing PDSCH rate matching; this configuration parameter is either applied to the rate matching of the first PDSCH, or is not applied to the rate matching of the first PDSCH but is applied to the rate matching of PDSCHs other than the first PDSCH.

[0091] As an embodiment, the configuration parameters followed by the REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0092] Whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, and the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0093] As an embodiment, whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0094] When at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH.

[0095] As an embodiment, the configuration parameters followed by the REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0096] When at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0097] As an embodiment, the configuration parameters followed by the REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0098] The REs used for rate matching of the first PDSCH depend on whether a first parameter is configured and a symbol type of at least one symbol allocated to the first PDSCH, the first parameter being a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0099] As an embodiment, the configuration parameters followed by the REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0100] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching.

[0101] As an embodiment, the configuration parameters followed by the REs for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0102] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

[0103] As an embodiment, the RE used for rate matching of the first PDSCH depends on whether the first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, including:

[0104] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching.

[0105] As an embodiment, the RE used for rate matching of the first PDSCH depends on whether the first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, including:

[0106] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

[0107] As an embodiment, in the present application: the symbols allocated to the first PDSCH are all symbols allocated to the first PDSCH in the time domain.

[0108] As an embodiment, the at least one symbol allocated to the first PDSCH is in the time domain.

[0109] As an embodiment, the time domain resource allocation field in the first signaling in the present application indicates the symbols allocated to the first PDSCH.

[0110] As an embodiment, the symbol allocated to the first PDSCH is a symbol in the time domain.

[0111] As an embodiment, a symbol allocated to the first PDSCH is an OFDM (Orthogonal Frequency Division Multiplex) symbol.

[0112] As an embodiment, the symbol allocated to the first PDSCH is a symbol in a time slot.

[0113] As an embodiment, all symbols allocated to the first PDSCH are full-duplex symbols, or all symbols allocated to the first PDSCH are non-full-duplex symbols.

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

[0115] As an embodiment, all symbols allocated to the first PDSCH are full-duplex symbols, or all symbols allocated to the first PDSCH are non-full-duplex symbols, or the symbols allocated to the first PDSCH include full-duplex symbols and non-full-duplex symbols.

[0116] Example 2

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

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

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

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

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

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

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

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

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

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

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

[0128] Example 3

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

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

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

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

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

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

[0135] Example 4

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

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

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

[0139] During transmission from the first communication device 410 to the second communication device 450, upper layer data packets from the core network are provided to the controller / processor 475 at the first communication device 410. The controller / processor 475 implements L2 layer functionality. During transmission from the first communication device 410 to the second communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 performs coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450, as well as mapping signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, which is then provided to a different antenna 420.

[0140] During transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives a signal via its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signal and reference signal are demultiplexed by the receive processor 456, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial stream destined for the second communication device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communications device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the first communications device 410 to the second communications device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 layer for L3 processing.

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

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

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

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

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

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

[0147] As an embodiment, the second communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 450 device at least: receives first signaling, the first signaling scheduling a first PDSCH; receives the first PDSCH; wherein the configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, the symbol type including at least full-duplex and non-full-duplex.

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

[0149] As an embodiment, the second communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, the actions including: receiving a first signaling, the first signaling scheduling a first PDSCH; receiving the first PDSCH; wherein the configuration parameters followed by the RE for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

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

[0151] 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 first signaling, the first signaling scheduling a first PDSCH; sends the first PDSCH; wherein the configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, the symbol type including at least full-duplex and non-full-duplex.

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

[0153] As an embodiment, the first communication device 410 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: sending a first signaling, wherein the first signaling schedules a first PDSCH; sending the first PDSCH; wherein the configuration parameters followed by the RE for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

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

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

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

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

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

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

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

[0161] As an embodiment, at least one of {the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller / processor 459, the memory 460, the data source 467} is used to send the first HARQ-ACK bit block in the present application.

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

[0163] Example 5

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

[0165] The first node U1 receives the first signaling in step S511; receives the first PDSCH in step S512; and sends the first HARQ-ACK bit block in step S513.

[0166] The second node U2 sends a first signaling in step S521; sends a first PDSCH in step S522; and receives a first HARQ-ACK bit block in step S523.

[0167] In embodiment 5, the first signaling schedules the first PDSCH; the configuration parameters followed by the RE for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex; when a symbol is indicated as downlink by the uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by the uplink and downlink TDD configuration signaling, this symbol is a non-full-duplex symbol; the uplink and downlink TDD configuration signaling includes at least one of tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0168] As a sub-embodiment of embodiment 5, the configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0169] Whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, and the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0170] As a sub-embodiment of embodiment 5, the configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0171] When at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0172] As a sub-embodiment of embodiment 5, the configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0173] The REs used for rate matching of the first PDSCH depend on whether a first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, the first parameter being a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0174] As a sub-embodiment of embodiment 5, the configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0175] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0176] As a sub-embodiment of embodiment 5, the configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, including:

[0177] When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

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

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

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

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

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

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

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

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

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

[0187] As an embodiment, the first parameter is configured, and the configuration of the first parameter is before the sending / receiving of the uplink / downlink TDD configuration signaling.

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

[0189] As an embodiment, the first parameter is configured, including: the second node configuring the first parameter to the first node.

[0190] As an embodiment, the first parameter is configured, including: the first node receives a signaling, and the signaling includes configuration information of the first parameter.

[0191] As an embodiment, the first parameter is configured to include:

[0192] The second node sends a signaling including configuration information of the first parameter; the first node receives the signaling.

[0193] As an embodiment, the first parameter is not configured, including: the second node does not configure the first parameter to the first node.

[0194] As an embodiment, the second node configures the second parameter to the first node.

[0195] As an embodiment, the second parameter is configured, and the configuration of the second parameter is before the sending / receiving of the uplink / downlink TDD configuration signaling.

[0196] As an embodiment, the second parameter is configured, and the configuration of the second parameter is after the sending / receiving of the uplink / downlink TDD configuration signaling.

[0197] As an embodiment, the configuration of the first parameter (when the first parameter is configured), the configuration of the second parameter, and the configuration of the uplink and downlink TDD configuration signaling are all before the sending / receiving of the first signaling.

[0198] As an embodiment, the configuration of the first parameter (when the first parameter is configured), the configuration of the second parameter, and the configuration of the uplink and downlink TDD configuration signaling can be performed in order of each other.

[0199] As an embodiment, the first HARQ-ACK bit block is sent in PUCCH.

[0200] As an embodiment, the first HARQ-ACK bit block includes at least one HARQ-ACK bit.

[0201] As an embodiment, the first HARQ-ACK bit block includes a HARQ-ACK (Hybrid Automatic Repeat reQuest-ACKnowledgement) bit for the first PDSCH.

[0202] As an embodiment, the first HARQ-ACK bit block includes a HARQ-ACK bit indicating whether the transport block in the first PDSCH is correctly decoded.

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

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

[0205] Example 6

[0206] Embodiment 6 illustrates a schematic diagram of REs used for rate matching of the first PDSCH according to an embodiment of the present application, as shown in FIG6 .

[0207] In embodiment 6, the REs used for rate matching of the first PDSCH include: REs declared as not available for PDSCH indicated by a configuration parameter for PDSCH rate matching in resource mapping of the first PDSCH.

[0208] As an embodiment, the REs used for rate matching of the first PDSCH are REs declared as unusable for PDSCH as indicated by a configuration parameter for PDSCH rate matching in resource mapping of the first PDSCH.

[0209] As an embodiment, the RE used for rate matching of the first PDSCH is an RE declared as unavailable for PDSCH in the physical resource block corresponding to the virtual resource block allocated to the first PDSCH, as indicated by the configuration parameters for PDSCH rate matching.

[0210] As an embodiment, the complex-valued modulation symbol generated by the codeword transmitted by the first PDSCH is not mapped to the RE used for rate matching of the first PDSCH.

[0211] As an embodiment, when the first PDSCH performs rate matching and resource mapping, the RE used for rate matching of the first PDSCH is skipped.

[0212] Example 7

[0213] Embodiment 7 illustrates a schematic diagram of REs used for rate matching of the first PDSCH according to an embodiment of the present application, as shown in FIG7. In FIG7, a large rectangular box includes multiple REs, and the first PDSCH is mapped to at least part of the time-frequency resources in the large rectangular box; all gray-filled boxes collectively represent the REs used for rate matching of the first PDSCH, and the first PDSCH is not mapped to any gray-filled box.

[0214] In Example 7, the first PDSCH is mapped to the RE in the large rectangular box in FIG. 7 that meets all conditions in the first condition set; the first condition set includes: any gray-filled box that does not belong to FIG. 7.

[0215] As an embodiment, the first condition set further includes: the corresponding virtual resource block is allocated to the first PDSCH.

[0216] As an embodiment, the first condition set further includes: the corresponding physical resource block is declared to be available for PDSCH.

[0217] As an embodiment, the first condition set further includes: not used for PT-RS (Phase-Tracking Reference Signal, phase tracking reference signal).

[0218] As an embodiment, the first condition set further includes: a DM-RS (Demodulation Reference Signal) not used for the first PDSCH associated with it or a DM-RS of other co-scheduled UEs.

[0219] As an embodiment, the first condition set also includes: not used for target CSI-RS (Channel State Information Reference Signal); the target CSI-RS is a non-zero-power CSI-RS (non-zero-power CSI-RS), and the target CSI-RS is configurable.

[0220] Example 8

[0221] Embodiment 8 illustrates a schematic diagram illustrating that the configuration parameters followed by REs for rate matching of the first PDSCH according to an embodiment of the present application depend on the symbol type of at least one symbol allocated to the first PDSCH, as shown in FIG8 .

[0222] In Example 8, when at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0223] As an embodiment, when at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the second parameter is not used for rate matching of the first PDSCH; the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

[0224] As an embodiment, the benefits of the above method include: improving the configuration flexibility of PDSCH rate matching.

[0225] As an embodiment, the RE indicated by the first parameter is applied to rate matching of the first PDSCH, including:

[0226] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the first parameter in resource mapping of the first PDSCH.

[0227] As an embodiment, the RE indicated by the first parameter is applied to rate matching of the first PDSCH, including:

[0228] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the first parameter in a physical resource block corresponding to a virtual resource block allocated to the first PDSCH.

[0229] As an embodiment, the RE indicated by the first parameter is not used for rate matching of the first PDSCH, including: resource mapping of the first PDSCH does not depend on the configuration of the first parameter.

[0230] As an embodiment, the RE indicated by the first parameter is not used for rate matching of the first PDSCH, including: the RE used for rate matching of the first PDSCH is not affected by the first parameter.

[0231] As an embodiment, when the RE indicated by the first parameter is applied to rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH complies with at least the first parameter.

[0232] As an embodiment, when the RE indicated by the first parameter is not used for rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH does not follow the first parameter.

[0233] As an embodiment, when the RE used for rate matching of the first PDSCH does not comply with the first parameter, the RE used for rate matching of the first PDSCH complies with configuration parameters for PDSCH rate matching other than the first parameter.

[0234] As an embodiment, when a parameter is used to configure resource mapping of a PDSCH in a full-duplex symbol, the parameter is a configuration parameter for the full-duplex symbol.

[0235] As an embodiment, when configuration of a parameter is applicable to a PDSCH on a full-duplex symbol, the parameter is a configuration parameter for the full-duplex symbol.

[0236] As an embodiment, the first parameter is a higher layer parameter.

[0237] As an embodiment, the first parameter is a parameter of the RRC layer.

[0238] As an embodiment, the configuration of the first parameter is applicable to rate matching of PDSCH on full-duplex symbols.

[0239] As an embodiment, the first parameter is a parameter for configuring a rate matching mode of a PDSCH for full-duplex symbols.

[0240] As an embodiment, the name of the first parameter includes rateMatchPattern.

[0241] As an embodiment, the name of the first parameter includes rateMatchPatternToAddModList.

[0242] As an embodiment, the first parameter is a parameter for configuring zero-power CSI-RS resources (Zero-Power (ZP) CSI-RS resources) for full-duplex symbols.

[0243] As an embodiment, the name of the first parameter includes p-ZP-CSI-RS-ResourceSet.

[0244] As an embodiment, the name of the first parameter includes sp-ZP-CSI-RS-ResourceSet.

[0245] As an embodiment, the name of the first parameter includes aperiodic-ZP-CSI-RS-ResourceSetsToAddModList.

[0246] As an embodiment, the second parameter is a higher layer parameter.

[0247] As an embodiment, the second parameter is a parameter of the RRC layer.

[0248] As an embodiment, the second parameter is a configuration parameter other than the first parameter.

[0249] As an embodiment, the second parameter is configured.

[0250] As an embodiment, the first parameter is a parameter for configuring a rate matching mode of the PDSCH for full-duplex symbols, and the second parameter is a parameter for configuring a rate matching mode of the PDSCH other than the first parameter.

[0251] As an embodiment, the name of the first parameter includes rateMatchPattern, and the name of the second parameter includes rateMatchPattern.

[0252] As an embodiment, the name of the first parameter includes rateMatchPatternToAddModList, and the name of the second parameter includes rateMatchPatternToAddModList.

[0253] As an embodiment, the first parameter is a parameter for configuring zero-power CSI-RS resources for full-duplex symbols, and the second parameter is a parameter for configuring zero-power CSI-RS resources other than the first parameter.

[0254] As an embodiment, the name of the first parameter includes p-ZP-CSI-RS-ResourceSet, and the name of the second parameter includes p-ZP-CSI-RS-ResourceSet.

[0255] As an embodiment, the name of the first parameter includes sp-ZP-CSI-RS-ResourceSet, and the name of the second parameter includes sp-ZP-CSI-RS-ResourceSet.

[0256] As an embodiment, the name of the first parameter includes aperiodic-ZP-CSI-RS-ResourceSetsToAddModList, and the name of the second parameter includes aperiodic-ZP-CSI-RS-ResourceSetsToAddModList.

[0257] As an embodiment, the RE indicated by the second parameter is applied to rate matching of the first PDSCH, including:

[0258] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the second parameter in resource mapping of the first PDSCH.

[0259] As an embodiment, the RE indicated by the second parameter is applied to rate matching of the first PDSCH, including:

[0260] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the second parameter in a physical resource block corresponding to a virtual resource block allocated to the first PDSCH.

[0261] As an embodiment, the RE indicated by the second parameter is not used for rate matching of the first PDSCH, including: resource mapping of the first PDSCH does not depend on the configuration of the second parameter.

[0262] As an embodiment, the RE indicated by the second parameter is not used for rate matching of the first PDSCH, including: the RE used for rate matching of the first PDSCH is not affected by the second parameter.

[0263] As an embodiment, when the RE indicated by the second parameter is applied to rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH complies with at least the second parameter.

[0264] As an embodiment, when the RE indicated by the second parameter is not used for rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH does not follow the second parameter.

[0265] As an embodiment, the symbol type of a full-duplex symbol is full-duplex, and the symbol type of a non-full-duplex symbol is non-full-duplex.

[0266] As an embodiment, there is no symbol that is both a full-duplex symbol and a non-full-duplex symbol.

[0267] As an embodiment, the symbol types only include full-duplex and non-full-duplex; when a symbol is not a full-duplex symbol, the symbol is a non-full-duplex symbol.

[0268] As an embodiment, the symbol type also includes symbol types other than full-duplex and non-full-duplex.

[0269] As an embodiment, when a symbol is indicated by uplink / downlink TDD configuration signaling as downlink and can be used for uplink transmission, the symbol is a full-duplex symbol.

[0270] As an embodiment, the benefits of the above method include: improving uplink performance.

[0271] As an embodiment, when a symbol is indicated as uplink by uplink / downlink TDD configuration signaling, the symbol is a non-full-duplex symbol.

[0272] As an embodiment, when a symbol is configured to be usable for full-duplex operation, the symbol is a full-duplex symbol; when a symbol is configured not to be used for full-duplex operation, the symbol is a non-full-duplex symbol.

[0273] As an embodiment, when a symbol is configured to be usable for full-duplex operation, the symbol is a full-duplex symbol; when a symbol is not configured to be usable for full-duplex operation, the symbol is a non-full-duplex symbol.

[0274] As an embodiment, the symbol used for the SBFD operation is a symbol of a full-duplex symbol type.

[0275] As an embodiment, the symbols not used for the SBFD operation are symbols of a non-full-duplex symbol type.

[0276] As an embodiment, SBFD symbols are full-duplex symbols, and non-SBFD symbols are non-full-duplex symbols.

[0277] As an embodiment, when the first PDSCH is in a full-duplex time slot, the symbols allocated to the first PDSCH are all full-duplex symbols.

[0278] As a sub-embodiment of the above embodiment, all symbols in a full-duplex time slot are full-duplex symbols.

[0279] As an embodiment, when the first PDSCH is in a non-full-duplex time slot, the symbols allocated to the first PDSCH are all non-full-duplex symbols.

[0280] As a sub-embodiment of the above embodiment, all symbols in a non-full-duplex time slot are non-full-duplex symbols.

[0281] Example 9

[0282] Embodiment 9 illustrates a schematic diagram illustrating that the configuration parameters followed by REs for rate matching of the first PDSCH according to an embodiment of the present application depend on the symbol type of at least one symbol allocated to the first PDSCH, as shown in FIG9 .

[0283] In embodiment 9, when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

[0284] As an embodiment, the benefits of the above method include: improving the configuration flexibility of PDSCH rate matching.

[0285] As an embodiment, the above method has the following benefits: it is helpful to save signaling overhead while ensuring PDSCH transmission performance.

[0286] As an embodiment, the benefits of the above method include: improving the robustness of the system.

[0287] As an embodiment, when the symbols allocated to the first PDSCH are all non-full-duplex symbols and the first parameter is configured, the RE indicated by the first parameter is not used for rate matching of the first PDSCH.

[0288] As an embodiment, the benefits of the above method include: improving the configuration flexibility of PDSCH rate matching.

[0289] As an embodiment, when the first parameter is not configured: regardless of whether the symbols allocated to the first PDSCH include full-duplex symbols, the REs indicated by the second parameter are applied to rate matching of the first PDSCH.

[0290] As an embodiment, the RE indicated by the first parameter is applied to rate matching of the first PDSCH, including:

[0291] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the first parameter in resource mapping of the first PDSCH.

[0292] As an embodiment, the RE indicated by the first parameter is applied to rate matching of the first PDSCH, including:

[0293] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the first parameter in a physical resource block corresponding to a virtual resource block allocated to the first PDSCH.

[0294] As an embodiment, the RE indicated by the first parameter is not used for rate matching of the first PDSCH, including: resource mapping of the first PDSCH does not depend on the configuration of the first parameter.

[0295] As an embodiment, the RE indicated by the first parameter is not used for rate matching of the first PDSCH, including: the RE used for rate matching of the first PDSCH is not affected by the first parameter.

[0296] As an embodiment, when the RE indicated by the first parameter is applied to rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH complies with at least the first parameter.

[0297] As an embodiment, when the RE indicated by the first parameter is not used for rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH does not follow the first parameter.

[0298] As an embodiment, when the RE used for rate matching of the first PDSCH does not comply with the first parameter, the RE used for rate matching of the first PDSCH complies with configuration parameters for PDSCH rate matching other than the first parameter.

[0299] As an embodiment, when a parameter is used to configure resource mapping of a PDSCH in a full-duplex symbol, the parameter is a configuration parameter for the full-duplex symbol.

[0300] As an embodiment, when configuration of a parameter is applicable to a PDSCH on a full-duplex symbol, the parameter is a configuration parameter for the full-duplex symbol.

[0301] As an embodiment, the first parameter is a higher layer parameter.

[0302] As an embodiment, the first parameter is a parameter of the RRC layer.

[0303] As an embodiment, the configuration of the first parameter is applicable to rate matching of PDSCH on full-duplex symbols.

[0304] As an embodiment, the first parameter is a parameter for configuring a rate matching mode of a PDSCH for full-duplex symbols.

[0305] As an embodiment, the name of the first parameter includes rateMatchPattern.

[0306] As an embodiment, the name of the first parameter includes rateMatchPatternToAddModList.

[0307] As an embodiment, the first parameter is a parameter for configuring zero-power CSI-RS resources for full-duplex symbols.

[0308] As an embodiment, the name of the first parameter includes p-ZP-CSI-RS-ResourceSet.

[0309] As an embodiment, the name of the first parameter includes sp-ZP-CSI-RS-ResourceSet.

[0310] As an embodiment, the name of the first parameter includes aperiodic-ZP-CSI-RS-ResourceSetsToAddModList.

[0311] As an embodiment, the second parameter is a higher layer parameter.

[0312] As an embodiment, the second parameter is a parameter of the RRC layer.

[0313] As an embodiment, the second parameter is at least applicable to rate matching of PDSCH on non-full-duplex symbols.

[0314] As an embodiment, the second parameter is configured.

[0315] As an embodiment, the second node configures the second parameter to the first node.

[0316] As an embodiment, the first parameter is a parameter for configuring a rate matching mode of the PDSCH for full-duplex symbols, and the second parameter is a parameter for configuring a rate matching mode of the PDSCH other than the first parameter.

[0317] As an embodiment, the name of the first parameter includes rateMatchPattern, and the name of the second parameter includes rateMatchPattern.

[0318] As an embodiment, the name of the first parameter includes rateMatchPatternToAddModList, and the name of the second parameter includes rateMatchPatternToAddModList.

[0319] As an embodiment, the first parameter is a parameter for configuring zero-power CSI-RS resources for full-duplex symbols, and the second parameter is a parameter for configuring zero-power CSI-RS resources other than the first parameter.

[0320] As an embodiment, the name of the first parameter includes p-ZP-CSI-RS-ResourceSet, and the name of the second parameter includes p-ZP-CSI-RS-ResourceSet.

[0321] As an embodiment, the name of the first parameter includes sp-ZP-CSI-RS-ResourceSet, and the name of the second parameter includes sp-ZP-CSI-RS-ResourceSet.

[0322] As an embodiment, the name of the first parameter includes aperiodic-ZP-CSI-RS-ResourceSetsToAddModList, and the name of the second parameter includes aperiodic-ZP-CSI-RS-ResourceSetsToAddModList.

[0323] As an embodiment, the RE indicated by the second parameter is applied to rate matching of the first PDSCH, including:

[0324] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the second parameter in resource mapping of the first PDSCH.

[0325] As an embodiment, the RE indicated by the second parameter is applied to rate matching of the first PDSCH, including:

[0326] The REs used for rate matching of the first PDSCH include REs declared as unusable for PDSCH and indicated by the second parameter in a physical resource block corresponding to a virtual resource block allocated to the first PDSCH.

[0327] As an embodiment, the RE indicated by the second parameter is not used for rate matching of the first PDSCH, including: resource mapping of the first PDSCH does not depend on the configuration of the second parameter.

[0328] As an embodiment, the RE indicated by the second parameter is not used for rate matching of the first PDSCH, including: the RE used for rate matching of the first PDSCH is not affected by the second parameter.

[0329] As an embodiment, when the RE indicated by the second parameter is applied to rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH complies with at least the second parameter.

[0330] As an embodiment, when the RE indicated by the second parameter is not used for rate matching of the first PDSCH, the RE used for rate matching of the first PDSCH does not follow the second parameter.

[0331] As an embodiment, the symbol type of a full-duplex symbol is full-duplex, and the symbol type of a non-full-duplex symbol is non-full-duplex.

[0332] As an embodiment, there is no symbol that is both a full-duplex symbol and a non-full-duplex symbol.

[0333] As an embodiment, the symbol types only include full-duplex and non-full-duplex; when a symbol is not a full-duplex symbol, the symbol is a non-full-duplex symbol.

[0334] As an embodiment, the symbol type also includes symbol types other than full-duplex and non-full-duplex.

[0335] As an embodiment, when a symbol is indicated by uplink / downlink TDD configuration signaling as downlink and can be used for uplink transmission, the symbol is a full-duplex symbol.

[0336] As an embodiment, the benefits of the above method include: improving uplink performance.

[0337] As an embodiment, when a symbol is indicated as uplink by uplink / downlink TDD configuration signaling, the symbol is a non-full-duplex symbol.

[0338] As an embodiment, when a symbol is configured to be usable for full-duplex operation, the symbol is a full-duplex symbol; when a symbol is configured not to be used for full-duplex operation, the symbol is a non-full-duplex symbol.

[0339] As an embodiment, when a symbol is configured to be usable for full-duplex operation, the symbol is a full-duplex symbol; when a symbol is not configured to be usable for full-duplex operation, the symbol is a non-full-duplex symbol.

[0340] As an embodiment, the symbol used for the SBFD operation is a symbol of a full-duplex symbol type.

[0341] As an embodiment, the symbols not used for the SBFD operation are symbols of a non-full-duplex symbol type.

[0342] As an embodiment, SBFD symbols are full-duplex symbols, and non-SBFD symbols are non-full-duplex symbols.

[0343] As an embodiment, when the first PDSCH is in a full-duplex time slot, the symbols allocated to the first PDSCH are all full-duplex symbols.

[0344] As a sub-embodiment of the above embodiment, all symbols in a full-duplex time slot are full-duplex symbols.

[0345] As an embodiment, when the first PDSCH is in a non-full-duplex time slot, the symbols allocated to the first PDSCH are all non-full-duplex symbols.

[0346] As a sub-embodiment of the above embodiment, all symbols in a non-full-duplex time slot are non-full-duplex symbols.

[0347] Example 10

[0348] Embodiment 10 illustrates a schematic diagram of a first information block according to an embodiment of the present application, as shown in FIG10 .

[0349] In embodiment 10, the first node determines whether a first information block is configured, and the first information block includes at least the first parameter.

[0350] As an embodiment, the first information block includes higher layer parameters.

[0351] As an embodiment, the first information block includes RRC layer parameters.

[0352] As an embodiment, the first information block is the information element to which the first parameter belongs.

[0353] As an embodiment, the first information block is an information element used to configure PDSCH parameters.

[0354] As an embodiment, the first information block is configured to the first node by the second node; or, the first information block is not configured.

[0355] As an embodiment, when the first information block is not configured, the first parameter is not configured.

[0356] As an embodiment, when the first node does not receive the first information block, the first information block is not configured.

[0357] As an embodiment, when the first node receives the first information block but the first information block does not include configuration information of the first parameter, the first parameter is not configured.

[0358] As an embodiment, when the first node receives the first information block and the first information block includes configuration information of the first parameter, the first parameter is configured.

[0359] As an embodiment, the first information block is the first parameter.

[0360] As an embodiment, the first node determines whether the first parameter is configured.

[0361] Example 11

[0362] Embodiment 11 illustrates a schematic diagram of full-duplex symbols and non-full-duplex symbols according to an embodiment of the present application, as shown in FIG11 .

[0363] In embodiment 11, when a symbol is indicated as downlink by uplink / downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink / downlink TDD configuration signaling, this symbol is a non-full-duplex symbol.

[0364] As an embodiment, the symbols indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission are full-duplex symbols.

[0365] As an embodiment, combined with the above features, the method disclosed in the present application is conducive to improving the transmission performance or resource utilization efficiency of PDSCH on symbols indicated as downlink by the uplink and downlink TDD configuration signaling and available for uplink transmission.

[0366] As an embodiment, any full-duplex symbol is a symbol indicated as a downlink symbol by the uplink / downlink TDD configuration signaling and can be used for uplink transmission.

[0367] As an embodiment, there is a full-duplex symbol that is not indicated as a downlink symbol by the uplink / downlink TDD configuration signaling and can be used for uplink transmission.

[0368] As an embodiment, whether a flexible symbol is a full-duplex symbol is configurable.

[0369] As an embodiment, whether a flexible symbol is a full-duplex symbol is configured by RRC signaling.

[0370] As an embodiment, there is one flexible symbol configured as a full-duplex symbol.

[0371] As an embodiment, a symbol indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission is indicated as downlink by the uplink / downlink TDD configuration signaling, and this symbol can be used for uplink transmission.

[0372] As an embodiment, there is at least one symbol indicated as a downlink symbol by the uplink / downlink TDD configuration signaling that is not a full-duplex symbol.

[0373] As an embodiment, whether a symbol indicated as a downlink symbol by the uplink / downlink TDD configuration signaling is a full-duplex symbol is configurable.

[0374] As an embodiment, whether a downlink symbol indicated by the uplink and downlink TDD configuration signaling is a full-duplex symbol is configured by RRC signaling.

[0375] As an embodiment, the symbols indicated by the uplink / downlink TDD configuration signaling as downlink symbols and unavailable for uplink transmission are not full-duplex symbols.

[0376] As an embodiment, the symbols indicated as downlink by the uplink / downlink TDD configuration signaling and available for uplink transmission are full-duplex symbols; the symbols indicated as downlink by the uplink / downlink TDD configuration signaling and unavailable for uplink transmission are non-full-duplex symbols.

[0377] As an embodiment, symbols indicated as uplink by the uplink / downlink TDD configuration signaling are not available for downlink transmission.

[0378] As an embodiment, the signal that can be used for uplink transmission includes: at least being used for PUSCH (Physical Uplink Shared CHannel, physical uplink shared channel) transmission (transmission(s)).

[0379] As an embodiment, combined with the above features, the method disclosed in this application is conducive to significantly improving the uplink capacity of the system.

[0380] As an embodiment, the signal that can be used for uplink transmission includes: at least signal that can be used for PUSCH and PUCCH (Physical Uplink Control CHannel, physical uplink control channel) transmission (transmission(s)).

[0381] As an embodiment, the data that can be used for uplink transmission includes: at least being used for PUSCH and PRACH transmission (transmission(s)).

[0382] As an embodiment, the data that can be used for uplink transmission includes: at least being used for PUCCH and PRACH transmission (transmission(s)).

[0383] As an embodiment, the data that can be used for uplink transmission includes: at least being used for PUSCH transmission, PUCCH transmission and PRACH transmission (transmission(s)).

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

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

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

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

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

[0389] As an embodiment, the uplink / downlink TDD (Time Division Duplex) configuration signaling is signaling indicating the link direction of the symbol.

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

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

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

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

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

[0395] As an embodiment, the benefits of the above method include: the uplink and downlink TDD configuration signaling can be applicable to multiple users, which is conducive to reducing control signaling overhead.

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

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

[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 uplink and downlink TDD configuration signaling includes tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated.

[0400] As an embodiment, when a symbol is indicated as uplink / downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, this symbol is a symbol indicated as uplink / downlink by the uplink / downlink TDD configuration signaling.

[0401] Example 12

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0418] As an embodiment, the first receiver A01 receives a first signaling, and the first signaling schedules a first PDSCH; the first receiver A01 receives the first PDSCH; wherein, the configuration parameters followed by the RE for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

[0419] As an embodiment, whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, and the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0420] As an embodiment, when at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0421] As an embodiment, the RE used for rate matching of the first PDSCH depends on whether a first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, wherein the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0422] As an embodiment, when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0423] As an embodiment, when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

[0424] As an embodiment, the symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

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

[0426] As an embodiment, the first transmitter A02 sends a first HARQ-ACK bit block; the first HARQ-ACK bit block includes HARQ-ACK bits for the first PDSCH.

[0427] Example 13

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0444] As an embodiment, the second transmitter B01 sends a first signaling, and the first signaling schedules a first PDSCH; the second transmitter B01 sends the first PDSCH; wherein, the configuration parameters followed by the RE for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

[0445] As an embodiment, whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, and the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0446] As an embodiment, when at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0447] As an embodiment, the RE used for rate matching of the first PDSCH depends on whether a first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, wherein the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0448] As an embodiment, when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

[0449] As an embodiment, when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH, and the RE indicated by the second parameter is not applied to the rate matching of the first PDSCH; when at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols, and the second parameter is a configuration parameter for PDSCH rate matching other than the first parameter.

[0450] As an embodiment, the symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

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

[0452] As an embodiment, the second receiver B02 receives a first HARQ-ACK bit block; the first HARQ-ACK bit block includes HARQ-ACK bits for the first PDSCH.

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

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

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first signaling, where the first signaling schedules a first PDSCH; The first receiver receives the first PDSCH; The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

2. The first node according to claim 1, wherein: Whether the RE indicated by the first parameter is applied to rate matching of the first PDSCH depends on the symbol type of at least one symbol allocated to the first PDSCH, and the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

3. The first node according to claim 1 or 2, characterized in that When at least one symbol allocated to the first PDSCH is a full-duplex symbol, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols, the RE indicated by the first parameter is not applied to the rate matching of the first PDSCH; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

4. The first node according to claim 1, characterized in that The REs used for rate matching of the first PDSCH depend on whether a first parameter is configured and the symbol type of at least one symbol allocated to the first PDSCH, the first parameter being a configuration parameter for PDSCH rate matching for full-duplex symbols.

5. The first node according to claim 1 or 4, characterized in that: When at least one symbol allocated to the first PDSCH is a full-duplex symbol and the first parameter is configured, the RE indicated by the first parameter is applied to the rate matching of the first PDSCH; when the symbols allocated to the first PDSCH are all non-full-duplex symbols or the first parameter is not configured, the RE indicated by the second parameter is applied to the rate matching of the first PDSCH, and the second parameter is a configuration parameter for PDSCH rate matching; the first parameter is a configuration parameter for PDSCH rate matching for full-duplex symbols.

6. The first node according to any one of claims 1 to 5, characterized in that: The symbol types only include full-duplex and non-full-duplex; when a symbol is indicated as downlink by uplink and downlink TDD configuration signaling and can be used for uplink transmission, this symbol is a full-duplex symbol; when a symbol is indicated as uplink by uplink and downlink TDD configuration signaling, this symbol is not a full-duplex symbol; when a symbol is not a full-duplex symbol, this symbol is a non-full-duplex symbol.

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

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first signaling, where the first signaling schedules a first PDSCH; The second transmitter sends the first PDSCH; The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

9. A method in a first node for wireless communication, characterized in that: include: receiving first signaling, where the first signaling schedules a first PDSCH; receiving the first PDSCH; The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

10. A method used in a second node of wireless communication, characterized in that: include: Sending first signaling, where the first signaling schedules a first PDSCH; Sending the first PDSCH; The configuration parameters followed by the REs used for rate matching of the first PDSCH depend on the symbol type of at least one symbol allocated to the first PDSCH, and the symbol type includes at least full-duplex and non-full-duplex.

Images