Pdsch receiving method, pdsch sending method, apparatus and communication system

Abstract

Provided in the embodiments of the present application are a PDSCH receiving method, a PDSCH sending method, an apparatus and a communication system. A method comprises: a terminal device receives configuration information at least used for configuring a first time domain resource and / or a second time domain resource, wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource; the terminal device receives downlink control information (DCI) scheduling a plurality of PDSCHs, wherein whether one PDSCH among the plurality of PDSCHs has a corresponding HARQ process ID is dependent on the first time domain resource and / or the second time domain resource; and the terminal device sends one or more of the PDSCHs among the plurality of PDSCHs having corresponding HARQ process IDs.

Description

PDSCH reception and transmission method, apparatus, and communication system TECHNICAL FIELD

[0001] The present application relates to the field of communication technology. BACKGROUND

[0002] In the prior art, for a time division duplex (TDD) frequency band, uplink transmission can only occur in an uplink time period, and when a limited or small uplink time period is allocated, there will be problems of small coverage range, small capacity and large latency of uplink. For a frequency division duplex (FDD) frequency band, uplink transmission can only occur in an uplink carrier, and when a limited or small uplink carrier is allocated, there will also be problems of small coverage range, small capacity and large latency of uplink.

[0003] It should be noted that the above introduction to the technical background is only for the convenience of clearly and completely describing the technical solutions of the present application and facilitating the understanding of those skilled in the art. The above technical solutions cannot be considered as known to those skilled in the art merely because they are described in the background section of the present application.

[0004] SUMMARY

[0005] In order to improve the capacity and coverage of uplink transmission and reduce the latency of uplink transmission, in a TDD frequency band or a downlink frequency band of an FDD frequency band, a network device can work in a full duplex mode at certain time positions, for example, the network device simultaneously receives and transmits in different frequency domain resources in a corresponding carrier (of the TDD frequency band or the downlink frequency band of the FDD frequency band). This working mode is referred to as sub-band non-overlapping full duplex (SBFD) for example, but is not limited thereto. For the convenience of description, the time domain resources in this working mode are referred to as first time domain resources (or also referred to as SBFD symbols), and other time domain resources are referred to as second time domain resources (or also referred to as non-SBFD symbols).

[0006] On the other hand, multiple physical downlink shared channels (PDSCHs) can be scheduled by one downlink control information (DCI), which can be referred to as multi-PDSCH scheduled by a single DCI. For a terminal device, the scheduled PDSCHs can be in SBFD symbols or non-SBFD symbols. Currently, there is no solution for how to allocate a hybrid automatic repeat reQuest (HARQ) process ID and how to send / receive the PDSCHs.

[0007] To solve at least one of the above problems, embodiments of the present application provide a PDSCH receiving and sending method, device, and communication system.

[0008] According to an aspect of embodiments of the present application, a PDSCH receiving method is provided, comprising:

[0009] The terminal device receives configuration information used at least for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0010] The terminal device receives downlink control information (DCI) used for scheduling multiple PDSCHs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0011] The terminal device receives one or more PDSCHs of the multiple PDSCHs having a corresponding HARQ process ID.

[0012] According to another aspect of embodiments of the present application, a PDSCH receiving device is provided, comprising:

[0013] A receiver receives configuration information used at least for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0014] The receiver receives downlink control information (DCI) for scheduling a plurality of PDSCHs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0015] The receiver further receives one or more of the plurality of PDSCHs having a corresponding HARQ process ID.

[0016] According to another aspect of embodiments of the present application, a PDSCH receiving method is provided, comprising:

[0017] The network device transmits configuration information for configuring at least a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0018] The network device transmits downlink control information (DCI) for scheduling a plurality of PDSCHs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0019] The network device further transmits one or more of the plurality of PDSCHs having a corresponding HARQ process ID.

[0020] According to another aspect of embodiments of the present application, a PDSCH receiving apparatus is provided, comprising:

[0021] The transmitter transmits configuration information for configuring at least a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink;

[0022] The transmitter transmits downlink control information (DCI) for scheduling a plurality of PDSCHs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0023] The transmitter further transmits one or more of the plurality of PDSCHs having a corresponding HARQ process ID.

[0024] According to another aspect of embodiments of the present application, a communication system is provided, comprising:

[0025] A terminal device receives configuration information at least for configuring a first time domain resource and / or a second time domain resource; wherein at the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is out of the first time domain resource; receives a downlink control information (DCI) for scheduling a plurality of PDSCHs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and receives one or more of the plurality of PDSCHs having the corresponding HARQ process ID;

[0026] A network device transmits configuration information at least for configuring a first time domain resource and / or a second time domain resource; transmits a downlink control information (DCI) for scheduling a plurality of PDSCHs; and transmits one or more of the plurality of PDSCHs having a corresponding HARQ process ID.

[0027] One of the beneficial effects of the embodiments of the present application is that the terminal device receives one or more of the plurality of PDSCHs having the corresponding HARQ process ID, wherein whether one of the plurality of PDSCHs has the corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. Thus, the network device can work in full duplex mode (simultaneous receiving and transmitting), and the terminal device can also receive and transmit signals using the corresponding resources when the network device works in full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the flexibility of resource allocation and resource utilization.

[0028] Specific embodiments of the application are disclosed herein, and represented in the accompanying drawings, illustrating the principles of the application in a manner that can be employed by those skilled in the art. It is understood that the embodiments of the application are not limited in scope to the specific embodiments described herein. Embodiments of the application include many alterations, modifications and equivalents that are within the scope of the appended claims and their spirit.

[0029] Features described and / or illustrated with respect to one implementation can be used in one or more other implementations in the same or similar manner, in combination with or in place of features in other implementations.

[0030] It should be emphasized that the term "comprises / comprising" when used in this specification is taken to mean the presence of stated features, integers, steps or components but not the exclusion of one or more other features, integers, steps, components or groups thereof. BRIEF DESCRIPTION OF DRAWINGS

[0031] Elements and features depicted in one drawing or embodiment of the application can be combined with elements and features depicted in one or more other drawings or embodiments, as can be desired. That is, some salient features of the drawings can be combined with one another in order to obtain a more general description of the application, as well as provide a complete description of certain embodiments of the application. In the drawings, like numerals refer to like parts through several views.

[0032] The accompanying drawings are included to provide a further understanding of embodiments of the application, and are incorporated in and constitute a part of this specification, illustrate embodiments of the application, and together with the description serve to explain the principles of the application. It is to be understood that other embodiments can be taken without departing from the scope of the application, and that the drawings are, therefore, to be regarded as illustrative rather than restrictive.

[0033] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the application;

[0034] FIG. 2 is a schematic diagram of a PDSCH receiving method according to an embodiment of the application;

[0035] FIG. 3 is an example diagram of time domain resources according to an embodiment of the application;

[0036] FIG. 4 is an example diagram of uplink available PRBs according to an embodiment of the application;

[0037] FIG. 5 is another example diagram of uplink available PRBs according to an embodiment of the application;

[0038] FIG. 6 is another example diagram of uplink available PRBs according to an embodiment of the application;

[0039] FIG. 7 is an example diagram of downlink available PRBs according to an embodiment of the application;

[0040] FIG. 8 is another example diagram of downlink available PRBs according to an embodiment of the application;

[0041] FIG. 9 is another example diagram of downlink available PRBs according to an embodiment of the application;

[0042] FIG. 10 is an example diagram of PDSCH scheduling according to an embodiment of the application;

[0043] FIG. 11 is another example diagram of PDSCH scheduling according to an embodiment of the application;

[0044] FIG. 12 is another example diagram of PDSCH scheduling according to an embodiment of the application;

[0045] FIG. 13 is another example diagram of PDSCH scheduling according to an embodiment of the application;

[0046] FIG. 14 is an example diagram of PDSCH receiving according to an embodiment of the application;

[0047] FIG. 15 is another example diagram of PDSCH being received according to embodiments of the present application;

[0048] FIG. 16 is another example diagram of PDSCH being received according to embodiments of the present application;

[0049] FIG. 17 is another example diagram of PDSCH being received according to embodiments of the present application;

[0050] FIG. 18 is another example diagram of PDSCH being received according to embodiments of the present application;

[0051] FIG. 19 is another example diagram of PDSCH being received according to embodiments of the present application;

[0052] FIG. 20 is another example diagram of PDSCH being received according to embodiments of the present application;

[0053] FIG. 21 is another example diagram of PDSCH being received according to embodiments of the present application;

[0054] FIG. 22 is a schematic diagram of a method for transmitting PDSCH according to embodiments of the present application;

[0055] FIG. 23 is a schematic diagram of a device for receiving PDSCH according to embodiments of the present application;

[0056] FIG. 24 is a schematic diagram of a device for transmitting PDSCH according to embodiments of the present application;

[0057] FIG. 25 is a schematic diagram of a network device according to embodiments of the present application;

[0058] FIG. 26 is a schematic diagram of a terminal device according to embodiments of the present application. DETAILED DESCRIPTION

[0059] The foregoing and other features of the present application are hereinafter more fully described, realized in the descriptions of particular embodiments thereof, reference being had to the accompanying drawings. In the descriptions of the embodiments of the present application, specific terminology is employed for the sake of clarity. However, the application is not intended to be limited to the specific embodiments described, but rather, is intended to cover modifications, alternatives and equivalents thereof that fall within the scope of the appended claims.

[0060] In the embodiments of the present application, the terms "first", "second", and the like are used to distinguish different elements from one another, but do not indicate spatial arrangement or temporal order of the elements, and the elements should not be limited by these terms. The term "and / or" includes any one and all combinations of the associated listed terms. The terms "comprise", "include", "have", and the like, mean the presence of the stated feature, element, component, or the like, but do not exclude the presence or addition of one or more other features, elements, components, or the like.

[0061] In the embodiments of the present application, the singular form "a", "an" and "the" include the plural form, should be broadly understood as "one" or "a kind of", and not limited to the meaning of "one"; in addition, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least partially according to", and the term "based on" should be understood as "at least partially based on", unless the context clearly indicates otherwise.

[0062] In the embodiments of the present application, the term "communication network" or "wireless communication network" can refer to a network that conforms to any communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.

[0063] In addition, the communication between devices in the communication system can be carried out according to any stage communication protocol, which can include but is not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, New Radio (NR), 6G, etc., and / or other currently known or to be developed in the future. Communication protocol.

[0064] In the embodiments of the present application, the term "network device" refers to, for example, a device that accesses a terminal device to a communication network and provides services for the terminal device in a communication system. The network device can include but is not limited to the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0065] A base station can include, but is not limited to, a NodeB (or NB), an evolved NodeB (or eNB), and a 5G base station (or gNB), an IAB donor, and the like, and can further include a remote radio head (RRH), a remote radio unit (RRU), a relay, or a low power node (e.g., a femto, a pico, and the like). Also, the term "base station" can include some or all functions of them, and each base station can provide communication coverage for a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0066] In embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, which can also be referred to as "terminal equipment" (TE). The terminal equipment can be fixed or mobile, and can also be referred to as a mobile station (MS), a terminal, a user, a subscriber station (SS), an access terminal (AT), a station, a mobile terminal (MT), and the like.

[0067] The terminal equipment can include, but is not limited to, the following devices: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a machine type communication device, a laptop computer, a cordless phone, a smartphone, a smartwatch, a digital camera, and the like.

[0068] For another example, in an Internet of Things (IoT) scenario or the like, the terminal equipment can also be a machine or device that performs monitoring or measurement, which can include, but is not limited to, the following devices: a machine type communication (MTC) terminal, a vehicle-mounted communication terminal, a device to device (D2D) terminal, a machine to machine (M2M) terminal, and the like.

[0069] In addition, the term "network side" or "network device side" refers to the side of the network, which can be a certain base station, or can include one or more network devices as above. The term "user side" or "terminal side" or "terminal device side" refers to the side of the user or terminal, which can be a certain UE, or can include one or more terminal devices as above. In this paper, "device" can refer to network device or terminal device without special indication.

[0070] In the following description, the terms "uplink control signal" and "uplink control information (UCI, Uplink Control Information)" or "physical uplink control channel (PUCCH, Physical Uplink Control Channel)" can be interchangeable without causing confusion, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH, Physical Uplink Shared Channel)" can be interchangeable;

[0071] The terms "downlink control signal" and "downlink control information (DCI, Downlink Control Information)" or "physical downlink control channel (PDCCH, Physical Downlink Control Channel)" can be interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH, Physical Downlink Shared Channel)" can be interchangeable.

[0072] In addition, the uplink signal can include uplink data signal and / or uplink control signal and / or PRACH and / or SRS, etc., and can also be referred to as uplink transmission (UL transmission) or uplink information or uplink channel. Transmitting / receiving the uplink transmission on the uplink resource can be understood as transmitting / receiving the uplink transmission using the uplink resource. The downlink signal can include downlink data signal and / or downlink control signal and / or synchronization signal (SS, such as PSS / SSS) and / or broadcast channel (PBCH) and / or SSB (SS / PBCH block, including PSS, SSS and PBCH and its DMRS) and / or CSI-RS, etc., and can also be referred to as downlink transmission (DL transmission) or downlink information or downlink channel. Transmitting / receiving the downlink transmission on the downlink resource can be understood as transmitting / receiving the downlink transmission using the downlink resource.

[0073] In the embodiments of the present application, the high layer signaling may, for example, be radio resource control (RRC) signaling; the RRC signaling may, for example, include an RRC message, for example, include broadcast / common RRC message / signaling (for example, master information block (MIB), system information), dedicated RRC message / signaling; or an RRC information element (RRC IE); or information fields included in the RRC message or the RRC information element (or information fields included in the information fields). The high layer signaling may, for example, also be medium access control (MAC) signaling; or be referred to as a MAC control element (MAC CE). However, the present application is not limited thereto. The names of the signaling (for example, RRC message, information element IE, information field, high layer parameter, etc.) used in the embodiments of the present application are only examples, and other names may also be used, and the embodiments of the present application are not limited thereto.

[0074] In the embodiments of the present application, multiple means at least two, or two or more than two.

[0075] In the embodiments of the present application, predefined means defined by a protocol or determined according to a rule defined by a protocol, without additional configuration. Configuration / indication means that the network device is directly or indirectly configured / indicated by high layer signaling and / or physical layer signaling. The configuration / indication may, for example, be configured / indicated by introducing a high layer parameter in the high layer signaling, and the high layer parameter means information fields and / or information elements / units / members (IEs) in the high layer signaling. The physical layer signaling may, for example, be control information (DCI) carried by a physical downlink control channel or control information carried by a sequence, but is not limited thereto.

[0076] For ease of description, the following describes a base station as an example of an access network device. In the following description, “if”, “in the case of” and “when” may be used interchangeably without causing confusion. For resources in the frequency domain, “carrier” and “resource grid” may be interchangeable, “subcarrier spacing configuration (SCS) μ” and “subcarrier spacing (SCS) Δf” may be interchangeable. “Subcarrier spacing” and “numerology” may be interchangeable. “Resource block”, “RB” and “PRB”, “physical resource block”, “common resource block (CRB)” may be interchangeable. Configuration / indication / provision / given may be interchangeable. “Index” and “ID” may be interchangeable.

[0077] The scenarios of the embodiments of the present application are described below by way of examples, but the present application is not limited thereto.

[0078] FIG. 1 is a schematic diagram of a communication system of the embodiments of the present application, which schematically illustrates the case taking the terminal device and the network device as examples. As shown in FIG. 1, the communication system 100 can include a network device 101 and terminal devices 102 and 103. For simplicity, FIG. 1 only takes two terminal devices and one network device as examples for illustration, but the embodiments of the present application are not limited thereto.

[0079] In the embodiments of the present application, the network device 101 and the terminal devices 102 and 103 can perform existing services or future implementable services transmission. For example, these services can include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0080] Among them, the terminal device 102 can send data to the network device 101, for example, using authorized or unlicensed transmission mode. The network device 101 can receive data sent by one or more terminal devices 102, and feed back information to the terminal device 102, such as acknowledgement ACK / non-acknowledgement NACK information, etc., so that the terminal device 102 can confirm the end of the transmission process, or can further perform new data transmission, or can perform data retransmission.

[0081] Among them, the network device 101 can use unicast or groupcast or broadcast mode to send data to the terminal device 102 and / or the terminal device 103. The terminal device 102 can receive data sent by one or more network devices (such as dual connectivity or multi-connectivity) through downlink or the terminal device 103 through sidelink.

[0082] It is worth noting that FIG. 1 shows that both terminal devices 102 and 103 are within the coverage of the network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 can be out of the coverage of the network device 101, or one terminal device 102 is within the coverage of the network device 101 while the other terminal device 103 is out of the coverage of the network device 101.

[0083] In the following description, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH; transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH. In addition, the content in the brackets is explanatory or optional, " / " means "and / or", and the application is not limited thereto. Various embodiments of the embodiments of the application will be described below in conjunction with the accompanying drawings. These embodiments are only exemplary and not limiting to the application.

[0084] Embodiments of the first aspect

[0085] Embodiments of the application provide a PDSCH receiving method, which is described from the terminal device side.

[0086] FIG. 2 is a schematic diagram of a PDSCH receiving method according to an embodiment of the application. As shown in FIG. 2, the method comprises:

[0087] 201, the terminal device receives configuration information used for configuring at least a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is used for uplink and a second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0088] 202, the terminal device receives downlink control information (DCI) used for scheduling multiple PDSCHs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0089] 203, the terminal device receives one or more PDSCHs with a corresponding HARQ process ID.

[0090] It is worth noting that the above FIG. 2 only schematically illustrates the embodiments of the application, but the application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above description, and the application is not limited to the description of the above FIG. 2.

[0091] In some embodiments, the terminal device can be an SBFD-aware device; the application is not limited thereto. For example, in the initial access process and / or in the random access process and / or in the capability information reporting, the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE).

[0092] For example, the SBFD-aware UE has capability related to SBFD operation, including one or more of the following: being able to know SBFD configuration, e.g., configuration of SBFD time domain resource (e.g., SBFD symbol) and frequency domain resource (e.g., UL subband / UL usable RBs, DL subband / DL usable RBs); being able to transmit uplink signal on (DL) SBFD symbol.

[0093] In some embodiments, the DCI for scheduling multiple PDSCHs is, for example, DCI format 1_1, but the present application is not limited thereto.

[0094] The time domain resource related to the embodiments of the present application is first schematically described as follows.

[0095] In some embodiments, the first time domain resource is a time domain resource for (supporting) full-duplex (e.g., SBFD) operation, the second time domain resource is a time domain resource not for (supporting) full-duplex operation (or not for full-duplex operation, e.g., non-SBFD), and the time locations of the first time domain resource and the second time domain resource are different.

[0096] In some embodiments, in the first time domain resource, the network device simultaneously receives and transmits in different frequency domain resources in the corresponding carrier (of the TDD frequency band or the downlink frequency band of the FDD frequency band), and in the second time domain resource, the network device only receives or transmits in the carrier.

[0097] In some embodiments, the first time domain resource refers to a time domain resource having / corresponding to SBFD subbands, or a time domain resource in which SBFD subbands are located, and the second time domain resource refers to a time domain resource not having / corresponding to SBFD subbands. The SBFD subbands include, for example, DL subband(s) and / or uplink subband(s).

[0098] In some embodiments, the time resource unit includes, for example, a symbol, and / or a slot, and / or a sub-slot, and / or a mini-slot, and / or a symbol group, and / or a slot group, and / or a subframe, and / or a frame, and / or ms, and / or s, etc., but is not limited thereto. For example, the number of symbols included in a sub-slot and a mini-slot is less than or equal to the number of slots included in a slot, a symbol group includes one or more (continuous or discontinuous) symbols, and a slot group includes one or more (continuous or discontinuous) slots, but is not limited thereto.

[0099] In some embodiments, the first time domain resource, for example, can also be referred to as SBFD resource, and the second time domain resource, for example, can also be referred to as non-SBFD resource. The SBFD resource, for example, includes SBFD time resource units, such as SBFD time slots and / or symbols, and the non-SBFD resource, for example, includes non-SBFD time resource units, such as non-SBFD time slots and / or symbols.

[0100] In some embodiments, a downlink symbol, for example, is a symbol configured as downlink by tdd-UL-DL-ConfigurationCommon, an uplink symbol, for example, is a symbol configured as uplink by tdd-UL-DL-ConfigurationCommon, a flexible symbol, for example, is a symbol neither configured as downlink nor configured as uplink by tdd-UL-DL-ConfigurationCommon, or is a symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, or is a symbol configured as flexible by tdd-UL-DL-ConfigurationCommon when tdd-UL-DL-ConfigurationCommon is provided, or is all symbols when tdd-UL-DL-ConfigurationCommon is not provided (no uplink / downlink subband is configured).

[0101] In some embodiments, a SBFD symbol, for example, is a symbol with SBFD / DL / UL subbands, for example, including DL SBFD symbol and / or Flexible SBFD symbol, but not limited to. For example, when only one TDD-UL-DL pattern is configured, the period is the same as the TDD-UL-DL pattern period configured by dl-UL-Transmission Periodicity in TDD-UL-DL-ConfigCommon; when two TDD-UL-DL patterns are configured, the period is the same as the sum of the two TDD-UL-DL pattern periods configured by dl-UL-Transmission Periodicity in TDD-UL-DL-ConfigCommon.

[0102] In some embodiments, the non-SBFD symbol is a symbol other than the SBFD symbol, or, a symbol other than the SBFD symbol and the first gap symbol, e.g., a symbol without SBFD / DL / UL subbands. For example, including a Full-DL symbol, and / or, a Full-UL symbol, and / or, a Full-flexible symbol, and / or, the first gap symbol; wherein the first gap symbol is a gap symbol between the non-SBFD symbol and the SBFD symbol, but not limited thereto.

[0103] In some embodiments, the DL SBFD symbol / SBFD DL symbol is a SBFD symbol configured within a DL symbol, or, a SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon.

[0104] In some embodiments, the Flexible SBFD symbol / SBFD Flexible symbol is a SBFD symbol configured within a Flexible symbol, or, a SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon.

[0105] In some embodiments, the Full-DL symbol / DL-only symbol / DL non-SBFD symbol / non-SBFD DL symbol is a non-SBFD symbol configured within a DL symbol, or, a non-SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon.

[0106] In some embodiments, the Full-UL symbol / UL-only symbol / UL non-SBFD symbol / non-SBFD UL symbol is a non-SBFD symbol configured within a UL symbol, or, a non-SBFD symbol configured as uplink by tdd-UL-DL-ConfigurationCommon.

[0107] In some embodiments, assuming that a SBFD symbol will not be configured in a UL symbol, the Full-UL symbol is equivalent to a UL symbol.

[0108] In some embodiments, a Full-flexible symbol / Flexible-only symbol / Flexible non-SBFD symbol / non-SBFD Flexible symbol is a symbol that is configured within a flexible symbol, or a non-SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, or a non-SBFD symbol that is neither configured as downlink by tdd-UL-DL-ConfigurationCommon nor configured as uplink by tdd-UL-DL-ConfigurationCommon, or a non-SBFD symbol configured as flexible. The meaning of flexible symbol can also refer to the aforementioned embodiments.

[0109] In some embodiments, a slot can include SBFD symbols and non-SBFD symbols, or only SBFD symbols, or only non-SBFD symbols.

[0110] FIG. 3 is an example diagram of time domain resources according to embodiments of the present disclosure. As shown in FIG. 3, a period can include a plurality of different symbols. FIG. 3 exemplarily illustrates time domain resources according to embodiments of the present disclosure, but is not limited thereto.

[0111] The frequency domain resources involved in embodiments of the present disclosure are described below.

[0112] In the first time domain resource, the first frequency domain resource is for uplink and the second frequency domain resource is for downlink. For example, the first frequency domain resource is an uplink subband (UL subband) in a SBFD symbol, and the second frequency domain resource is a downlink subband (DL subband) in the SBFD symbol. The terms "subband" and "frequency domain resource unit set" can be interchangeable.

[0113] In some embodiments, the first frequency domain resource and the second frequency domain resource are in a time division duplex (TDD) frequency band (or uppaired spectrum), or in a downlink frequency band of a frequency division duplex (FDD) frequency band (paired spectrum), or in an uplink frequency band of the FDD frequency band, or in a supplemental uplink (SUL) frequency band.

[0114] In some embodiments, for UL, the cell-specific frequency location of UL subband can be configured separately for each SCS (in SCS-SpecificCarrierList for UL), or in other words, the cell-specific UL subband can be configured separately for each SCS configuration. For each SCS configuration, the reference starting PRB is the PRB determined by the SCS configuration and offsetToCarrier corresponding to the subcarrier spacing, for example, one / most one UL subband can be configured, but not limited thereto.

[0115] In some embodiments, for UL BWP, the uplink usable PRBs / RBs can be determined as the intersection between the (cell-specific) UL subband and the UL BWP (in SBFD symbols), i.e., implicitly configured, for example, referred to as first uplink usable PRBs.

[0116] In some embodiments, for one UL BWP, the uplink usable PRBs are determined according to the UL subband configured for the same SCS as the SCS of the UL BWP. For example, if the SCS of one UL BWP is 15 kHz, the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband configured for 15 kHz SCS. If the SCS of one UL BWP is 30 kHz, the corresponding UL usable PRBs are the intersection between the UL BWP and the uplink subband configured for 30 kHz SCS.

[0117] FIG. 4 is an example diagram of uplink usable PRBs according to an embodiment of the present application, as shown in FIG. 4, the UL BWP and the UL subband overlap, and the UL usable PRBs are the intersection between the two (in SBFD symbols).

[0118] FIG. 5 is another example diagram of uplink usable PRBs according to an embodiment of the present application, as shown in FIG. 5, the UL BWP includes the UL subband in the frequency domain, and the UL usable PRBs are the intersection between the two (in SBFD symbols).

[0119] In FIGS. 4 and 5, the UL subband therein represents the uplink subband configured for the SCS corresponding to the UL BWP, for example, but the present application is not limited thereto.

[0120] In some embodiments, for UL BWP, the uplink usable PRBs / RBs can be explicitly configured in the UL BWP (in SBFD symbols), for example, referred to as second uplink usable PRBs.

[0121] In some embodiments, when configured with both the first uplink available PRBs and the second uplink available PRBs, the second uplink available PRBs are employed.

[0122] In some embodiments, the second uplink available PRBs are configured based on the first uplink available PRBs. For example, the second uplink available PRBs include PRBs other than unavailable PRBs in the first uplink available PRBs. For another example, the second uplink available PRBs include the first uplink available PRBs and other available PRBs other than the first uplink available PRBs.

[0123] FIG. 6 is another example diagram of uplink available PRBs according to embodiments of the present disclosure. As shown in FIG. 6, the UL usable PRBs are explicitly configured in the UL BWP.

[0124] In some embodiments, for DL, the cell-specific frequency locations of DL subbands can be configured separately for each SCS (in SCS-SpecificCarrierList), or in other words, the cell-specific UL subbands are configured separately for each SCS. For each SCS configuration, the reference starting PRB is the PRB determined by the SCS configuration and the offsetToCarrier corresponding to the subcarrier spacing, and for example, one / two DL subbands can be configured, but the present disclosure is not limited thereto.

[0125] In some embodiments, for the downlink available PRBs / RBs (DL usable PRBs / RBs) of a DL BWP, the intersection between the (cell-specific) DL subbands and the DL BWP (in SBFD symbols) can be determined, or in other words, the DL usable PRBs are implicitly configured, for example, referred to as the first downlink available PRBs.

[0126] In some embodiments, the downlink available PRBs of a DL BWP are determined according to the UL subbands configured for the same SCS as the SCS of the DL BWP. For example, if the SCS of a DL BWP is 15 kHz, the corresponding DL available PRBs are the intersection between the DL BWP and the downlink subbands configured for the SCS of 15 kHz. If the SCS of a DL BWP is 30 kHz, the corresponding DL available PRBs are the intersection between the DL BWP and the downlink subbands configured for the SCS of 30 kHz.

[0127] FIG. 7 is an example diagram of downlink usable PRBs in an embodiment of the present application, as shown in FIG. 7, the DL BWP and the DL subband overlap, and the DL usable PRBs are the intersection between the two (in the SBFD symbol).

[0128] FIG. 8 is another example diagram of downlink usable PRBs in an embodiment of the present application, as shown in FIG. 8, the DL BWP includes the DL subband in the frequency domain, and the DL usable PRBs are the intersection between the two (in the SBFD symbol).

[0129] In FIG. 7 and FIG. 8, the DL subband therein represents, for example, a downlink subband configured with a SCS corresponding to the DL BWP, but the present application is not limited thereto.

[0130] In some embodiments, for the downlink usable PRBs / RBs of the DL BWP, the second downlink usable PRBs can be explicitly configured in the DL BWP (in the SBFD symbol), for example, referred to as the second downlink usable PRBs.

[0131] In some embodiments, when the first downlink usable PRBs and the second downlink usable PRBs are configured at the same time, the second downlink usable PRBs are adopted.

[0132] In some embodiments, the second downlink usable PRBs are configured based on the first downlink usable PRBs. For example, the PRBs that are not available in the first downlink usable PRBs are configured, and the second downlink usable PRBs include the PRBs in the first downlink usable PRBs except the PRBs that are not available. For another example, other available PRBs other than the first downlink usable PRBs are configured, and the second downlink usable PRBs include the first downlink usable PRBs and the other available PRBs.

[0133] FIG. 9 is another example diagram of downlink usable PRBs in an embodiment of the present application, as shown in FIG. 9, the DL usable PRBs are explicitly configured in the DL BWP.

[0134] The time-frequency resources are described above, and the PDSCH in an embodiment of the present application is described below.

[0135] In an embodiment of the present application, one DCI can schedule multiple PDSCHs (which can be referred to as multi-PDSCH scheduled by a single DCI). The positions of the PDSCHs scheduled by the DCI can be divided into the following cases:

[0136] --The multiple PDSCHs are all only in the SBFD symbol;

[0137] --The multiple PDSCHs are all only in the non-SBFD symbol;

[0138] -- multiple PDSCHs in SBFD symbols and non-SBFD symbols and each PDSCH either in SBFD symbols or in non-SBFD symbols (i.e., part of the multiple PDSCHs in SBFD symbols and another part of the multiple PDSCHs in non-SBFD symbols);

[0139] -- multiple PDSCHs in SBFD symbols and non-SBFD symbols and at least one PDSCH in both SBFD symbols and non-SBFD symbols (i.e., at least one PDSCH overlaps with SBFD symbols and non-SBFD symbols).

[0140] It is worth noting that the above division is made for the convenience of description, but the present application is not limited thereto. For example, only part of the above cases can be included, two or more of the above cases can be combined, and other cases can be added.

[0141] In some embodiments, frequency domain resource allocation (FDRA) can be separately provided for PDSCHs overlapping with SBFD symbols and PDSCHs in non-SBFD symbols. Among them, PDSCHs overlapping with SBFD symbols include PDSCHs in SBFD symbols and / or PDSCHs in which part of PDSCHs are in SBFD symbols and another part of PDSCHs are in non-SBFD symbols.

[0142] For example, separate FDRA configurations / indications / interpretations can be provided for SBFD symbols and non-SBFD symbols, respectively. For example, an FDRA field is included in the DCI scheduling the PDSCH, and the UE determines the frequency domain resources of the PDSCHs overlapping with the SBFD symbols and the frequency domain resources of the PDSCHs in the non-SBFD symbols according to the FDRA field, respectively. For another example, 2 FDRA fields are included in the DCI, and the 2 FDRA fields respectively indicate the frequency domain resources of the PDSCHs overlapping with the SBFD symbols and the frequency domain resources of the PDSCHs in the non-SBFD symbols.

[0143] For example, a FDRA configuration / indication is provided for one symbol type (SBFD symbol or non-SBFD symbol), and RB offset(s) configuration / indication / determination is used to determine the resources for other symbol types. For example, a FDRA field is included in the DCI scheduling PDSCH, which indicates the frequency domain resources of the PDSCH in non-SBFD symbols. For the PDSCH overlapping with SBFD symbols, the UE determines the frequency domain resources according to the RB offset(s) between the (start PRB of the) DL usable PRBs and the (start PRB of the) corresponding DL BWP. Or, the UE determines the frequency domain resources of the PDSCH overlapping with SBFD symbols according to the RB offset(s) between the (start PRB of the) PDSCH overlapping with SBFD symbols and the (start PRB of the) frequency domain resources of the PDSCH in non-SBFD symbols, which is indicated by the base station (e.g., through higher layer signaling or the DCI).

[0144] FIG. 10 is an example diagram of PDSCH scheduling according to an embodiment of the application. As shown in FIG. 10, for example, the resources of PDSCH 1 and PDSCH 4 can be provided by FDRA configuration / indication, and the resources of PDSCH 2 and PDSCH 3 can be determined by RB offset(s) configuration / indication / determination.

[0145] For example, a common FDRA configuration / indication is provided, and for the PDSCH overlapping with the RBs outside of the DL usable PRBs in SBFD symbols, only the allocated PRBs within the DL usable PRBs are considered valid. For example, a FDRA field is included in the DCI scheduling PDSCH, which is applied to all scheduled PDSCH, that is, the frequency domain resources indicated for all PDSCH are the same, but for the PDSCH overlapping with SBFD symbols, the part of the resources outside of the DL usable PRBs is invalid.

[0146] FIG. 11 is another example diagram of PDSCH scheduling according to an embodiment of the application. As shown in FIG. 11, for example, the resources of PDSCH 1 to PDSCH 4 can be provided by FDRA configuration / indication, but the part of the resources of PDSCH 2 and PDSCH 3 outside of the DL usable PRBs is invalid.

[0147] In some embodiments, a common frequency domain resource allocation (FDRA) can be provided for PDSCHs overlapping with SBFD symbols and PDSCHs in non-SBFD symbols. For example, one FDRA field is included in the DCI scheduling the PDSCHs, which is applied to all scheduled PDSCHs, that is, the frequency domain resources indicated for all PDSCHs are the same.

[0148] For example, the gNB does not schedule any PDSCH in the SBFD symbols of one slot to overlap with PRBs other than the DL available PRBs, or the UE does not expect any PDSCH in the SBFD symbols of one slot to overlap with PRBs other than the DL available PRBs.

[0149] FIG. 12 is another example diagram of PDSCH scheduling according to an embodiment of the present application. As shown in FIG. 12, none of the PDSCHs (e.g., PDSCH 2 and PDSCH 3) in the SBFD symbols overlap with PRBs other than the DL available PRBs.

[0150] For another example, the gNB can schedule PDSCHs overlapping with SBFD symbols to overlap with PRBs other than the DL available PRBs.

[0151] FIG. 13 is another example diagram of PDSCH scheduling according to an embodiment of the present application. As shown in FIG. 13, the PDSCHs (e.g., PDSCH 2 and PDSCH 3) in the SBFD symbols are scheduled to overlap with PRBs other than the DL available PRBs. Whether these PDSCHs are actually received (transmitted) can be determined by the terminal device (network device), for example.

[0152] The above describes the PDSCH scheduling schematically, and the following describes how the terminal device receives the PDSCH. In the following description, the terminal device side “receives the PDSCH” is taken as an example for description, and the network device side “transmits the PDSCH” can also be taken as an example for description.

[0153] In the embodiments of the present application, the X information can be used to indicate the link direction (DL / UL) of the SBFD symbols, which can be tdd-UL-DL-ConfigurationDedicated, but is not limited thereto, and can also be other information, for example. The Y information can be used to indicate the link direction of the (flexible) non-SBFD symbols, which can be tdd-UL-DL-ConfigurationCommon (for example, the symbols indicated as UL by the tdd-UL-DL-ConfigurationCommon belong to the non-SBFD symbols and the link direction is uplink), and / or tdd-UL-DL-ConfigurationDedicated, but is not limited thereto, and can also be other information, for example.

[0154] In some embodiments, the PDSCH reception is restricted in the first time domain resource (SBFD symbols), the terminal device can only receive (alternatively, the network device can only transmit) PDSCHs in the first time domain resource, cannot / is not allowed to receive PDSCHs in the second time domain resource overlapped with the PDSCHs scheduled by the DCI, the PDSCHs (in the PDSCHs with corresponding HARQ-process ID) overlapped with the second time domain resource cannot / is not allowed to be received. For example, the PDSCH receptions are restricted to SBFD symbols only (hereinafter referred to as case 1). For this case, the terminal device can perform operation 1 as follows.

[0155] Operation 1:

[0156] The terminal device receives (alternatively, the network device transmits) PDSCHs that do not overlap with SSB symbols, and / or do not overlap with the second time domain resource (non-SBFD symbols), and / or are in the first time domain resource (SBFD symbols) and do not overlap with PRBs other than the downlink usable PRBs (or the second frequency domain resource), and / or do not overlap with symbols indicated as uplink by the indicated information (X information),

[0157] and / or,

[0158] The terminal device does not receive (alternatively, the network device does not transmit) PDSCHs that overlap with SSB symbols, and / or overlap with the second time domain resource (non-SBFD symbols), and / or are in the first time domain resource (SBFD symbols) and overlap with PRBs other than the downlink usable PRBs (or the second frequency domain resource), and / or overlap with symbols indicated as uplink by the indicated information (X information);

[0159] and / or,

[0160] The terminal device does not expect to exist PDSCHs that are in the first time domain resource (SBFD symbols) and overlap with PRBs other than the downlink usable PRBs, and / or the terminal device does not expect to exist PDSCHs that overlap with both the first time domain resource (SBFD symbols) and the second time domain resource (non-SBFD symbols).

[0161] For example, assume that PDSCH in SBFD symbols can overlap with RBs outside of DL usable RBs, then the UE does not receive PDSCHs overlapping with SSB and / or non-SBFD symbols and / or PDSCHs overlapping with SBFD symbols and overlapping with RBs outside of DL usable RBs (including PDSCHs in SBFD symbols and overlapping with SSB), and / or, the UE only receives PDSCHs in SBFD symbols and not overlapping with SSB and not overlapping with RBs outside of DL usable RBs.

[0162] For another example, assume that PDSCH in SBFD symbols must be within DL usable RBs (e.g., gNB does not schedule PDSCHs overlapping with SBFD symbols and overlapping with RBs outside of DL usable RBs, or, UE does not expect PDSCHs overlapping with SBFD symbols and overlapping with RBs outside of DL usable RBs), then the UE does not receive PDSCHs overlapping with SSB and / or non-SBFD symbols, and / or, the UE only receives PDSCHs in SBFD symbols and not overlapping with SSB.

[0163] FIG. 14 is an example diagram of PDSCH receptions according to an embodiment of the application, as shown in FIG. 14, the terminal device only receives PDSCHs in SBFD symbols and not overlapping with SSB (i.e., PDSCH 2), while PDSCH 1, PDSCH 3 and PDSCH 4 are not received.

[0164] In some embodiments, the PDSCH receptions are restricted in the second time-domain resources (non-SBFD symbols), that is, the terminal device can only receive (alternatively, the network device can only transmit) PDSCHs in the second time-domain resources, and cannot / is not allowed to receive PDSCHs overlapping with the first time-domain resources among the multiple PDSCHs scheduled by the DCI, the PDSCHs overlapping with the first time-domain resources (among the PDSCHs with corresponding HARQ-process IDs) cannot / is not allowed to be received. For example, the PDSCH receptions are restricted to non-SBFD symbols only (hereinafter referred to as case 2). For this case, the terminal device can perform operation 2 as follows.

[0165] Operation 2:

[0166] The terminal device receives (alternatively, the network device transmits) the PDSCH as follows: not overlapping with the SSB, and / or, not overlapping with the first time domain resource (SBFD symbol), and / or, not overlapping with the second time domain resource (non-SBFD symbol) for uplink, and / or, not overlapping with the symbol indicated as uplink by the indicated information (Y information);

[0167] and / or,

[0168] The terminal device does not receive (alternatively, the network device does not transmit) the PDSCH as follows: overlapping with the SSB, and / or, overlapping with the first time domain resource (SBFD symbol), and / or, overlapping with the second time domain resource (non-SBFD symbol) for uplink, and / or, overlapping with the symbol indicated as uplink by the indicated information (Y information);

[0169] and / or,

[0170] The terminal device does not expect the PDSCH to overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0171] For example, the UE does not receive the PDSCH overlapping with the SBFD symbol and / or the SSB and / or the DL non-SBFD symbol and / or the symbol indicated as uplink by the Y information, and / or, the UE only receives the PDSCH in the non-SBFD symbol and not overlapping with the SSB and / or the DL non-SBFD symbol and / or the symbol indicated as uplink by the Y information.

[0172] FIG. 15 is another example diagram of the PDSCH received by the terminal device according to the embodiments of the present application, as shown in FIG. 15, the terminal device receives the PDSCH (i.e., PDSCH 4) in the non-SBFD symbol and not overlapping with the SSB and / or the DL non-SBFD symbol and / or the symbol indicated as uplink by the Y information, while the PDSCH 1, the PDSCH 2 and the PDSCH 3 are not received.

[0173] In some embodiments, the terminal device can / be allowed to receive PDSCHs in the first time domain resources and the second time domain resources, i.e., in the DCI scheduled multiple PDSCHs, the PDSCHs in the first time domain resources (if any) and / or the PDSCHs in the second time domain resources (if any), but cannot / be not allowed to receive the PDSCHs (if any) that overlap both the first time domain resources and the second time domain resources, the PDSCHs (with corresponding HARQ-process ID) that overlap both the first time domain resources and the second time domain resources cannot / be not allowed to be received. For example, the PDSCHs receptions can be across SBFD symbols and non-SBFD symbols and each has either all SBFD or all non-SBFD symbols (hereinafter referred to as case 3). For this case, the terminal device can perform operation 3 as follows.

[0174] Operation 3:

[0175] The terminal device receives (alternatively, the network device transmits) the PDSCHs that do not overlap with the SSB and / or the second time domain resources for uplink (UL non-SBFD symbols), and / or do not overlap both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or are in the first time domain resources (SBFD symbols) and do not overlap the PRBs other than the downlink usable PRBs (or the second frequency domain resources), and / or do not overlap the symbols indicated by the indicated information as uplink;

[0176] and / or,

[0177] The terminal device does not receive (alternatively, the network device does not transmit) the PDSCHs that overlap with the SSB, and / or overlap with the second time domain resources for uplink (UL non-SBFD symbols), and / or overlap both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or are in the first time domain resources (SBFD symbols) and overlap the PRBs other than the downlink usable PRBs (or the second frequency domain resources), and / or overlap the symbols indicated by the indicated information as uplink;

[0178] and / or,

[0179] The terminal device does not expect PDSCH that overlaps with PRBs outside of the first time domain resource (SBFD symbol) and the downlink usable PRBs (or the second frequency domain resource), and / or the terminal device does not expect PDSCH that overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0180] For example, assuming that PDSCH in SBFD symbols can overlap with RBs outside of the DL usable RBs, PDSCH can overlap with both SBFD symbols and non-SBFD symbols, the UE does not receive PDSCH that overlaps with SSB and / or non-SBFD symbols and / or in SBFD symbols and with RBs outside of the DL usable RBs (including PDSCH in SBFD symbols and overlapping with SSB) and / or PDSCH that overlaps with both SBFD symbols and non-SBFD symbols, and / or the UE only receives PDSCH that does not overlap with SSB and / or UL non-SBFD symbols, does not overlap with both SBFD symbols and non-SBFD symbols, when overlapping with SBFD symbols, does not overlap with RBs outside of the DL usable RBs.

[0181] FIG. 16 is another example diagram of PDSCH being received according to embodiments of the application, as shown in FIG. 16, the terminal device only receives PDSCH (i.e., PDSCH 4) that does not overlap with SSB and / or UL non-SBFD symbols, does not overlap with both SBFD symbols and non-SBFD symbols, when overlapping with SBFD symbols, does not overlap with RBs outside of the DL usable RBs, while PDSCH 1, PDSCH 2, and PDSCH 3 are not received.

[0182] For another example, assuming that PDSCH in SBFD symbols is always within the DL usable RBs (e.g., gNB does not schedule PDSCH that overlaps with SBFD symbols and overlaps with RBs outside of the DL usable RBs, or the UE does not expect PDSCH that overlaps with SBFD symbols and overlaps with RBs outside of the DL usable RBs), PDSCH can overlap with both SBFD symbols and non-SBFD symbols, the UE does not receive PDSCH that overlaps with SSB and / or non-SBFD symbols and / or PDSCH that overlaps with both SBFD symbols and non-SBFD symbols, and / or the UE only receives PDSCH that does not overlap with SSB and / or UL non-SBFD symbols and does not overlap with both SBFD symbols and non-SBFD symbols.

[0183] FIG. 17 is another example diagram of PDSCHs being received according to embodiments of the application, as shown in FIG. 17, the terminal device receives PDSCH 2 and PDSCH 4, where part of the RBs of PDSCH 2 are considered invalid; while neither PDSCH 1 nor PDSCH 3 is received.

[0184] For yet another example, assuming that PDSCH in SBFD symbols is always within DL usable RBs (e.g., gNB does not schedule PDSCH that overlaps with SBFD symbols and RBs outside of DL usable RBs, or UE does not expect PDSCH that overlaps with SBFD symbols and RBs outside of DL usable RBs), PDSCH does not overlap with both SBFD symbols and non-SBFD symbols (e.g., UE does not expect PDSCH that overlaps with both SBFD symbols and non-SBFD symbols), the UE does not receive PDSCH that overlaps with SSB and / or non-SBFD symbols, and / or the UE only receives PDSCH that does not overlap with SSB and / or UL non-SBFD symbols.

[0185] FIG. 18 is another example diagram of PDSCHs being received according to embodiments of the application, as shown in FIG. 18, the terminal device only receives PDSCH 2, PDSCH 3, and PDSCH 4, while PDSCH 1 is not received.

[0186] For yet another example, assuming that PDSCH in SBFD symbols is always within DL usable RBs (e.g., gNB does not schedule PDSCH that overlaps with SBFD symbols and RBs outside of DL usable RBs, or UE does not expect PDSCH that overlaps with SBFD symbols and RBs outside of DL usable RBs), PDSCH does not overlap with both SBFD symbols and non-SBFD symbols (e.g., UE does not expect PDSCH that overlaps with both SBFD symbols and non-SBFD symbols), the UE does not receive PDSCH that overlaps with SSB and / or non-SBFD symbols, and / or the UE only receives PDSCH that does not overlap with SSB and / or UL non-SBFD symbols.

[0187] FIG. 19 is another example diagram of PDSCHs being received according to embodiments of the application, as shown in FIG. 19, the terminal device only receives PDSCH 3 and PDSCH 4, while PDSCH 1, PDSCH 2 are not received.

[0188] In some embodiments, the multiple PDSCH receptions can be in the first time domain resources and the second time domain resources, and include a case that a PDSCH reception overlaps with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), or in other words, a PDSCH of the multiple PDSCHs that overlaps with both the first time domain resources and the second time domain resources can be received. That is, among the multiple PDSCHs scheduled by the DCI, the terminal device can / is allowed to receive a PDSCH (if any) in the first time domain resources and / or a PDSCH (if any) in the second time domain resources and / or a PDSCH (if any) that overlaps with both the first time domain resources and the second time domain resources. For example, the PDSCH receptions can be across SBFD symbols and non-SBFD symbols, include a PDSCH overlapping with both SBFD symbols and non-SBFD symbols (hereinafter referred to as case 4). For this case, the terminal device can perform operation 4 as follows.

[0189] Operation 4:

[0190] The terminal device receives (alternatively, the network device transmits) a PDSCH that does not overlap with an SSB and / or a second time domain resource for uplink (DL non-SBFD symbol), and / or overlaps with the first time domain resources (SBFD symbols) and does not overlap with a PRB other than a downlink usable PRB (DL usable PRB), and / or does not overlap with a symbol indicated by the indicated information as uplink;

[0191] and / or,

[0192] The terminal device does not receive (alternatively, the network device does not transmit) a PDSCH that overlaps with an SSB, and / or overlaps with a second time domain resource for uplink (UL non-SBFD symbol), and / or overlaps with the first time domain resources (SBFD symbols) and overlaps with a PRB other than a downlink usable PRB (DL usable PRB), and / or overlaps with a symbol indicated by the indicated information as uplink;

[0193] and / or,

[0194] The terminal device does not expect a PDSCH that overlaps with the first time domain resources (SBFD symbols) and overlaps with a PRB other than a downlink usable PRB (DL usable PRB).

[0195] For example, assuming that PDSCHs overlapping with SBFD symbols can overlap with RBs outside of DL usable RBs (e.g., alternatively, overlap with the boundaries of DL usable RBs), the UE does not receive PDSCHs overlapping with SSBs and / or UL non-SBFD symbols, and / or PDSCHs overlapping with SBFD symbols and overlapping with RBs outside of DL usable RBs, and / or the UE only receives PDSCHs not overlapping with SSBs and / or UL non-SBFD symbols, and, when overlapping with SBFD symbols, not overlapping with RBs outside of DL usable RBs.

[0196] FIG. 20 is another example diagram of PDSCHs being received according to embodiments of the application, as shown in FIG. 20, the terminal device only receives PDSCH 4, and PDSCH 1, PDSCH 2, PDSCH 3 are not received.

[0197] For example, assuming that PDSCHs overlapping with SBFD symbols must be within DL usable RBs (e.g., gNB does not schedule PDSCHs overlapping with SBFD symbols and overlapping with RBs outside of DL usable RBs, or the UE does not expect PDSCHs overlapping with SBFD symbols and overlapping with RBs outside of DL usable RBs to exist), the UE does not receive PDSCHs overlapping with SSBs and / or UL non-SBFD symbols, and / or the UE only receives PDSCHs not overlapping with SSBs and / or UL non-SBFD symbols.

[0198] FIG. 21 is another example diagram of PDSCHs being received according to embodiments of the application, as shown in FIG. 21, the terminal device only receives PDSCH 2, PDSCH 3, PDSCH 4, wherein part of the RBs of PDSCH 2 and PDSCH 3 are considered invalid; and PDSCH 1 is not received.

[0199] The above illustrates the case of PDSCHs being received, wherein case 1 to case 4 and operation 1 to operation 4 are only classifications for convenience of explanation, and the application is not limited to these classifications. The application is further described below.

[0200] In some embodiments, the capability of the terminal device includes whether to support one or more of case 1 to case 4, or one or more of operation 1 to operation 4. For example, the terminal device supports case 1 and case 2, or operation 1 and operation 2, and optionally supports case 3 and / or case 4, or operation 3 and / or operation 4. When the terminal device supports operation 3 and / or operation 4, the corresponding capability information is reported, otherwise it is not reported.

[0201] In some embodiments, the capability of the terminal device includes whether to support receiving PDSCH or downlink signal overlapped with both SBFD symbol and non-SBFD symbol. For example, the terminal device optionally supports receiving PDSCH or downlink signal overlapped with both SBFD symbol and non-SBFD symbol. When the terminal device supports, the corresponding capability information is reported, otherwise, it is not reported. When not supported, the corresponding case 4 / operation 4 is also not supported.

[0202] In some embodiments, which case (e.g., case 1 to case 4 as mentioned above) is allowed / applied can be predefined. For example, when the PDSCH scheduled by the DCI includes PDSCH overlapped with SBFD symbol and RBs outside DL usable RBs, case 2 is applied and operation 2 as mentioned above is performed. For another example, the base station can indicate which cases as mentioned above are allowed / applied, e.g., configured / indicated by RRC signaling and / or MAC CE and / or DCI.

[0203] For another example, which case (e.g., case 1 to case 4 as mentioned above) is allowed / applied is limited by the capability of the UE, e.g., if the terminal device does not support case 3 / operation 3, case 3 / operation 3 is not allowed / applied, if the terminal device does not support case 4 / operation 4 or does not support receiving PDSCH or downlink signal overlapped with both SBFD symbol and non-SBFD symbol, case 4 / operation 4 is not allowed / applied.

[0204] In some embodiments, the terminal device determines the PDSCH with corresponding HARQ process ID in the plurality of PDSCHs according to the higher layer signaling and / or the DCI and / or the reference PDSCH and / or the capability of the terminal device, and / or receives one or more PDSCHs in the plurality of PDSCHs with corresponding HARQ process ID.

[0205] In some examples, the reference PDSCH is a predetermined or indicated one of the PDSCHs scheduled by the DCI, or a predetermined or indicated one of the PDSCHs as follows: PDSCH not overlapped with SSB and / or second time domain resource for uplink (UL non-SBFD symbol), and / or PDSCH not overlapped with both first time domain resource (SBFD symbol) and second time domain resource (non-SBFD symbol), and / or PDSCH overlapped with first time domain resource (SBFD symbol) and not overlapped with PRB outside downlink usable PRB (DL usable PRB), and / or PDSCH not overlapped with symbol indicated by the indicated information as uplink.

[0206] For example, the reference PDSCH is predefined as follows: the first PDSCH scheduled by the DCI, or, the first PDSCH which does not overlap with SSB and / or UL non-SBFD symbol and / or does not overlap with both SBFD symbol and non-SBFD symbol and / or does not overlap with RBs outside of DL usable PRBs when overlapping with SBFD symbol.

[0207] For example, if the reference PDSCH is in SBFD symbol, the PDSCH which overlaps with non-SBFD symbol does not have HARQ process ID, and / or, (determined as case 1), operation 1 described above is performed.

[0208] For another example, if the reference PDSCH is in non-SBFD symbol, the PDSCH which overlaps with SBFD symbol does not have HARQ process ID, and / or, (determined as case 2), operation 2 described above is performed.

[0209] For yet another example, if the reference PDSCH overlaps with both SBFD symbol and non-SBFD symbol or starts from SBFD symbol to end at non-SBFD symbol, (determined as case 4), operation 4 described above is performed.

[0210] In some embodiments, the terminal device does not expect the reference PDSCH to overlap with both SBFD symbol and non-SBFD symbol.

[0211] The following first illustrates an optional mode 1 (option 1) of embodiments of the present application.

[0212] It is worth noting that in the following description, each configuration will be described as an example. The first configuration to the fourth configuration can be carried by the same signaling together with the configuration information shown in FIG. 2, can be carried by different signaling (including high layer signaling and / or DCI) respectively, or can not be carried by signaling (for example, it is a default configuration); the present application is not limited to this.

[0213] In some embodiments, when the following configurations or information are carried by high layer signaling, they are respectively included in an IE (e.g., ServingCellConfigCommonSIB) or an IE (e.g., ServingCellConfigCommon) for configuring cell-specific parameters of a cell, and / or in an IE (e.g., ServingCellConfig) for configuring a cell, and / or in an IE (e.g., BWP-DownlinkCommon) for configuring common parameters of a DL BWP, and / or in an IE (e.g., BWP-DownlinkDedicated) for configuring dedicated (UE specific) parameters of a DL BWP, and / or in an IE (e.g., PDSCH-Config) for configuring UE-specific (applicable to one BWP) PDSCH parameters.

[0214] In some embodiments, the terminal device receives a first configuration or a second configuration from the network device; the first configuration indicates that PDSCH receptions are all in the first time domain resources or all in the second time domain resources, and the second configuration indicates that PDSCH receptions can be in the first time domain resources and the second time domain resources.

[0215] In some embodiments, when the second configuration is not received and / or the terminal device does not support case 3 / operation 3 (and / or case 4 / operation 4), the first configuration is used by default.

[0216] For example, the first configuration indicates that PDSCH receptions are all in the first time domain resources or all in the second time domain resources (The PDSCH receptions are restricted to SBFD symbols only or non-SBFD symbols only); the second configuration indicates that PDSCH receptions can be in the first time domain resources and / or the second time domain resources (The PDSCH receptions can be in SBFD symbols and non-SBFD symbols).

[0217] Among them, since the first configuration includes the aforementioned case 1 and case 2, and for one received DCI scheduling multiple PDSCHs, the terminal device needs to uniquely determine whether operation 1 or operation 2 should be used. Since the second configuration includes the aforementioned case 3 and case 4, and for one received DCI scheduling multiple PDSCHs, the terminal device needs to uniquely determine whether operation 3 or operation 4 should be used.

[0218] In some embodiments, in the case of the first configuration information, for example, the terminal device is provided with the first configuration by high layer signaling or adopts the first configuration by default, according to the reference PDSCH and / or the first information provided by MAC signaling and / or DCI, (determine whether it is case 1 or case 2), and then determine the PDSCH with the corresponding HARQ process ID in the plurality of PDSCHs (if the conditions that the PDSCH with the corresponding HARQ process ID should meet are different for case 1 and case 2), and / or, the PDSCHs that will be received or not received in the plurality of PDSCHs (that is, operation 1 or operation 2 is adopted),

[0219] Among them, the first information indicates that the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with the first time domain resource (that is, the PDSCH reception is in the first time domain resource, corresponding to case 1), or does not receive the PDSCHs that overlap with the second time domain resource (that is, the PDSCH reception is in the second time domain resource, corresponding to case 2).

[0220] For example, if the reference PDSCH is in the SBFD symbol, the PDSCH that overlaps with the non-SBFD symbol does not have a HARQ process ID, and / or (determined as case 2,) the aforementioned operation 1 is performed.

[0221] For another example, if the reference PDSCH is in the non-SBFD symbol, the PDSCH that overlaps with the SBFD symbol does not have a HARQ process ID, and / or (determined as case 2,) the aforementioned operation 2 is performed.

[0222] For another example, if the first information indicates that the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with the first time domain resource, the aforementioned operation 1 is performed, and if the first information indicates that the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with the second time domain resource, the aforementioned operation 2 is performed.

[0223] In some embodiments, in the case of the second configuration, the terminal device, in the case that the second configuration is provided by high layer signaling, determines (whether it is case 3 or case 4) according to the reference PDSCH and / or the second information provided by high layer signaling and / or DCI, and then determines the PDSCH with the corresponding HARQ process ID in the plurality of PDSCHs (if the conditions that the PDSCH with the corresponding HARQ process ID should meet are different for case 3 and case 4), and / or the PDSCHs that will be received or not received in the plurality of PDSCHs (that is, operation 3 or operation 4 is adopted),

[0224] The second information is used to indicate that the terminal device receives the PDSCHs in the plurality of PDSCHs that overlap both the first time domain resource and the second time domain resource (if any), or indicates that the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap both the first time domain resource and the second time domain resource (if any).

[0225] For example, if the second information indicates that the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap both the first time domain resource and the second time domain resource (if any), operation 3 is performed, and if the first information indicates that the terminal device receives the PDSCHs in the plurality of PDSCHs that overlap both the first time domain resource and the second time domain resource (if any), operation 4 is performed.

[0226] The following further illustrates an optional mode 2 (option 2) of the embodiments of the present application.

[0227] In some embodiments, the terminal device receives the first configuration or the second configuration from the network device; the first configuration indicates that the PDSCH reception is in the first time domain resource or in the second time domain resource, and the second configuration indicates that the PDSCH reception can be in the first time domain resource and the second time domain resource, and each PDSCH is in the first time domain resource or in the second time domain resource.

[0228] For example, the first configuration is the same as the first configuration in Option 1, and the second configuration includes case 3. For the first configuration, the method described in Option 1 can be referred to, and for the second configuration, operation 3 is performed.

[0229] The following further illustrates an optional mode 3 (option 3) of the embodiments of the present application.

[0230] In some embodiments, the terminal device receives the first configuration, the second configuration or the third configuration from the network device; the first configuration indicates that the PDSCH receptions are all in the first time domain resource, the second configuration indicates that the PDSCH receptions are all in the second time domain resource, and the third configuration indicates that the PDSCH receptions can be in the first time domain resource and the second time domain resource.

[0231] For example, for the first configuration (corresponding to the aforementioned case 1), the terminal device performs the aforementioned operation 1, and for the second configuration (corresponding to the aforementioned case 2), the terminal device performs the aforementioned operation 2. The third configuration is the same as the second configuration in Option 1, and for the third configuration, the method described in Option 1 for the corresponding second configuration can be referred to.

[0232] The following further illustrates an optional mode 4 (option 4) of the embodiments of the present application.

[0233] The terminal device receives the first configuration, the second configuration, the third configuration or the fourth configuration from the network device; the first configuration indicates that the PDSCH receptions are all in the first time domain resource, the second configuration indicates that the PDSCH receptions are all in the second time domain resource, the third configuration indicates that the PDSCH receptions can be in the first time domain resource and the second time domain resource and each PDSCH reception is either in the first time domain resource or in the second time domain resource, and the fourth configuration indicates that multiple PDSCH receptions can be in the first time domain resource and the second time domain resource and a PDSCH (if any) that overlaps with both the first time domain resource and the second time domain resource can be received.

[0234] For example, for the first configuration (corresponding to the aforementioned case 1), the terminal device performs the aforementioned operation 1, and for the second configuration (corresponding to the aforementioned case 2), the terminal device performs the aforementioned operation 2. For the third configuration (corresponding to the aforementioned case 3), the terminal device performs the aforementioned operation 3, and for the second configuration (corresponding to the aforementioned case 4), the terminal device performs the aforementioned operation 4.

[0235] The above illustrates various embodiments of the present application, but the present application is not limited thereto. For example, in each option, if the UE is not signaled with a certain configuration, one of the other configurations can be used by default. For another example, the above optional modes can be partially combined. For another example, other embodiments can also be used as needed. The above is a simple description of options 2 to 5 for the sake of simplicity, and the present application is not limited thereto, and specific implementations can also refer to Option 1 and the aforementioned embodiments.

[0236] The following further illustrates the HARQ process ID.

[0237] In some embodiments, the terminal device allocates a HARQ process ID for the received at least one PDSCH. In addition, a HARQ process ID can be allocated for the non-received PDSCH, or a HARQ process ID can not be allocated for the non-received PDSCH.

[0238] For example, for case 1, the PDSCH overlapping with the second time domain resource is not transmitted, which can be allocated or not allocated a HARQ process ID, that is, has or does not have a HARQ process ID. For example, for case 2, the PDSCH overlapping with the first time domain resource is not transmitted, which can be allocated or not allocated a HARQ process ID, that is, has or does not have a HARQ process ID.

[0239] For example, for the PDSCH that the UE needs to receive, the corresponding HARQ process ID must be allocated, and for the PDSCH that the UE does not receive, the HARQ process ID can be allocated or not allocated. Among them, the PDSCH allocated with the HARQ process ID at least does not overlap with the SSB and / or UL non-SBFD symbol, and / or does not overlap with the symbol indicated as uplink by Y information when the PDSCH is within the non-SBFD symbol, and / or does not overlap with the RBs outside the DL usable RBs and / or the symbol indicated as uplink by X information when the PDSCH overlaps and / or is within the SBFD symbol, and / or does not overlap with both the SBFD symbol and the non-SBFD symbol.

[0240] In some embodiments, the PDSCHs that are transmitted among the plurality of PDSCHs have corresponding HARQ process IDs, and the PDSCHs that are not transmitted do not have corresponding HARQ process IDs.

[0241] For example, for case 1, the PDSCH transmitted in operation 1 has a corresponding HARQ process ID, and the PDSCH that is not transmitted does not have a corresponding HARQ process ID. For example, for case 2, the PDSCH transmitted in operation 2 has a corresponding HARQ process ID, and the PDSCH that is not transmitted does not have a corresponding HARQ process ID.

[0242] In some embodiments, whether a PDSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource, including: if the PDSCH overlaps with the second time domain resource for uplink, the PDSCH does not have a corresponding HARQ process ID.

[0243] In some embodiments, whether a PDSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource, including:

[0244] If a PDSCH overlaps with the second time domain resource (DL non-SBFD symbol) for uplink, the PDSCH does not have a corresponding HARQ process ID, and / or,

[0245] If a PDSCH overlaps with the first time domain resource (SBFD symbol), the PDSCH does not have a corresponding HARQ process ID, and / or,

[0246] If a PDSCH overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), the PDSCH does not have a corresponding HARQ process ID, and / or,

[0247] If a PDSCH overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), the PDSCH does not have a corresponding HARQ process ID, and / or,

[0248] If a PDSCH overlaps with the first time domain resource (SBFD symbol) and overlaps with a frequency domain resource other than the downlink available PRB (DL usable PRB), the PDSCH does not have a corresponding HARQ process ID.

[0249] In some embodiments, the PDSCH with a corresponding HARQ process ID is a PDSCH that:

[0250] does not overlap with an SSB, and / or, does not overlap with the second time domain resource (DL non-SBFD symbol) for uplink, and / or, does not overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or, overlaps with the first time domain resource (SBFD symbol) and does not overlap with a PRB other than the downlink available PRB (DL usable PRB), and / or, does not overlap with a symbol indicated by the indicated information as uplink.

[0251] In some embodiments, the terminal device further determines, according to the PDSCH reception restriction, the HARQ process ID corresponding to one or more of the plurality of PDSCHs, and / or receives one or more of the plurality of PDSCHs having the corresponding HARQ process ID.

[0252] In some examples, the PDSCH reception restriction comprises: the terminal device does not receive (alternatively, the network device does not transmit) the PDSCH of the plurality of PDSCHs overlapping with the second time domain resource (e.g. corresponding to the aforementioned case 1, but not limited thereto), and / or the terminal device does not receive (alternatively, the network device does not transmit) the PDSCH of the plurality of PDSCHs overlapping with the first time domain resource (e.g. corresponding to the aforementioned case 2, but not limited thereto), and / or the terminal device does not receive (alternatively, the network device does not transmit) the PDSCH of the plurality of PDSCHs overlapping with both the first time domain resource and the second time domain resource (e.g. corresponding to the aforementioned case 1 / case 2 / case 3, but not limited thereto).

[0253] In some embodiments, the PDSCH reception restriction is indicated and / or determined according to at least one of: RRC signaling, MAC signaling, DCI, reference PDSCH, or capability of the terminal device. The specific method may, for example, refer to the aforementioned configurations and information, but is not limited thereto.

[0254] In some embodiments, under different PDSCH reception restrictions, the PDSCH of the plurality of PDSCHs having the corresponding HARQ process ID needs to satisfy the same condition. For example, for 2 or more of the aforementioned case 1 to case 4, the PDSCH having the corresponding HARQ process ID needs to satisfy the same condition (or said to be defined the same), e.g. needs to satisfy the intersection of the conditions corresponding to the received PDSCH in the corresponding operation (including not overlapping with SSB, etc.).

[0255] In some embodiments, under different PDSCH reception restrictions, the PDSCH of the plurality of PDSCHs having the corresponding HARQ process ID needs to satisfy different conditions. For example, for 2 of the aforementioned case 1 to case 4, the PDSCH having the corresponding HARQ process ID needs to satisfy different conditions (or said to be defined differently), e.g. respectively satisfies the conditions corresponding to the received PDSCH in the corresponding operation (including not overlapping with SSB, etc.).

[0256] In some embodiments, the terminal device determines the HARQ process ID corresponding to one or more PDSCHs of the plurality of PDSCHs and / or receives one or more PDSCHs of the plurality of PDSCHs having the corresponding HARQ process ID according to the RRC signaling and / or the MAC signaling and / or the DCI and / or the reference PDSCH and / or the capability of the terminal device.

[0257] In some embodiments, the HARQ process ID indicated by the DCI is applied to the first PDSCH of the plurality of PDSCHs having the corresponding HARQ process ID, and for each subsequent PDSCH having the corresponding HARQ process ID, the HARQ process ID is obtained by performing a modulo operation on the number of HARQ processes for the PDSCH in the scheduling order and sequentially adding 1. The number of HARQ processes is provided by the parameter nrofHARQ-ProcessesForPDSCH or nrofHARQ-ProcessesForPDSCH-v1700, but is not limited thereto, for example, it can also be other parameters or a default value, for example, 8.

[0258] Table 1 and Table 2 respectively show an example of the HARQ process ID according to the embodiments of the present application.

[0259] Table 1

[0260] Table 2

[0261] Table 1 and Table 2 exemplarily illustrate the HARQ process ID according to the embodiments of the present application, but are not limited thereto.

[0262] In some embodiments, the PDSCHs of the plurality of PDSCHs having the corresponding HARQ process ID do not overlap with the SSB symbol, and / or do not overlap with the second time domain resource for uplink (UL non-SBFD symbol), and / or do not overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or overlap with the first time domain resource (SBFD symbol) and do not overlap with the frequency domain resource other than the downlink available PRB (DL usable PRB) (or the second frequency domain resource), and / or do not overlap with the symbol indicated by the indicated information (x / y) as uplink, and / or start from the SBFD symbol and end at the non-SBFD symbol, and / or start from the non-SBFD symbol and end at the SBFD symbol.

[0263] In some embodiments, a PDSCH in the plurality of PDSCHs has a corresponding HARQ process ID if: not overlapping with the SSB symbol, and / or, not overlapping with the second time domain resource for uplink (UL non-SBFD symbol), and / or, not overlapping with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or, overlapping with the first time domain resource (SBFD symbol) and not overlapping with the frequency domain resource other than the downlink usable PRB (DL usable PRB) (or the second frequency domain resource), and / or, not overlapping with the symbol indicated by the indicated information (x / y) as uplink, and / or, starting from the SBFD symbol and ending at the non-SBFD symbol, and / or, starting from the non-SBFD symbol and ending at the SBFD symbol.

[0264] In some embodiments, a PDSCH in the plurality of PDSCHs does not have a corresponding HARQ process ID if: overlapping with the SSB symbol, and / or, overlapping with the second time domain resource for uplink (UL non-SBFD symbol), and / or, overlapping with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or, overlapping with the first time domain resource (SBFD symbol) and overlapping with the frequency domain resource other than the downlink usable PRB (DL usable PRB) (or the second frequency domain resource), and / or, overlapping with the symbol indicated by the indicated information as uplink, and / or, not starting from the SBFD symbol and ending at the non-SBFD symbol, and / or, not starting from the non-SBFD symbol and ending at the SBFD symbol.

[0265] In some embodiments, a PDSCH in the plurality of PDSCHs does not have a corresponding HARQ process ID if: overlapping with the SSB symbol, and / or, overlapping with the second time domain resource for uplink (UL non-SBFD symbol), and / or, overlapping with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or, overlapping with the first time domain resource (SBFD symbol) and overlapping with the frequency domain resource other than the downlink usable PRB (DL usable PRB) (or the second frequency domain resource), and / or, overlapping with the symbol indicated by the indicated information as uplink, and / or, not starting from the SBFD symbol and ending at the non-SBFD symbol, and / or, not starting from the non-SBFD symbol and ending at the SBFD symbol.

[0266] The above only describes the steps or processes related to the present application, but the present application is not limited thereto. The method of the embodiments of the present application can also include other steps or processes, and the specific content of these steps or processes can be referred to the related technology.

[0267] The above embodiments are only illustrative of the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above embodiments. For example, the above embodiments can be used alone or one or more of the above embodiments can be combined.

[0268] As can be seen from the above embodiments, the terminal device receives one or more PDSCHs with corresponding HARQ process IDs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. Thus, the network device can work in a full duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to transceive signals when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0269] Embodiments of the second aspect

[0270] The embodiments of the present application provide a PDSCH transmission method, which is described from the side of the network device. The same content as the embodiments of the first aspect will not be described again.

[0271] FIG. 22 is a schematic diagram of a PDSCH transmission method according to an embodiment of the present application. As shown in FIG. 22, the method comprises:

[0272] 2201, the network device transmits configuration information used at least for configuring a first time domain resource and / or a second time domain resource; wherein the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink in the first time domain resource, and the second time domain resource is outside the first time domain resource;

[0273] 2202, the network device transmits downlink control information (DCI) used for scheduling a plurality of PDSCHs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0274] 2203, the network device transmits one or more PDSCHs with corresponding HARQ process IDs.

[0275] It is worth noting that the above FIG. 22 only schematically illustrates the embodiments of the present application, but the present application is not limited thereto. For example, the execution order between the operations can be appropriately adjusted, and in addition, some operations can be added or some operations can be reduced. Those skilled in the art can appropriately modify the above content, and the present application is not limited to the above FIG. 22.

[0276] In some embodiments, at the first time domain resource, the network device can transmit a downlink signal to a terminal device at the first frequency domain resource, receive an uplink signal transmitted by another terminal device on a frequency domain resource other than the first frequency domain resource, and / or receive an uplink signal transmitted by a terminal device at the second frequency domain resource and transmit a downlink signal to another terminal device on a frequency domain resource other than the second frequency domain resource. So that the network device supports the simultaneous existence / occurrence / conduct of downlink and uplink.

[0277] In some embodiments, the network device can also transmit various configuration information / indication information to the terminal device, and can also receive feedback information / reporting information from the terminal device, which is not limited in the present application.

[0278] In some embodiments, the network device can determine the HARQ process ID corresponding to the PDSCH with the corresponding HARQ process ID.

[0279] In some embodiments, the HARQ process ID indicated by the DCI is applied to the first PDSCH with the corresponding HARQ process ID in the plurality of PDSCHs, and for each subsequent PDSCH with the corresponding HARQ process ID, the HARQ process ID is sequentially added 1 after the modulo operation of the number of HARQ processes for the PDSCH in the scheduling order.

[0280] In some embodiments, the PDSCH with the corresponding HARQ process ID in the plurality of PDSCHs does not overlap with the SSB symbol, and / or does not overlap with the second time domain resource for uplink (UL non-SBFD symbol), and / or does not overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or overlaps with the first time domain resource (SBFD symbol) and does not overlap with the frequency domain resource other than the downlink available PRB (DL usable PRB) (or the second frequency domain resource), and / or does not overlap with the symbol indicated by the indication information (x / y) as uplink, and / or starts from the SBFD symbol and ends at the non-SBFD symbol, and / or starts from the non-SBFD symbol and ends at the SBFD symbol.

[0281] In some embodiments, a PDSCH in the plurality of PDSCHs has a corresponding HARQ process ID if: does not overlap with SSB symbols, and / or, does not overlap with the second time domain resources for uplink (UL non-SBFD symbols), and / or, does not overlap with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or, overlaps with the first time domain resources (SBFD symbols) and does not overlap with frequency domain resources other than downlink usable PRBs (DL usable PRBs) (or the second frequency domain resources), and / or, does not overlap with symbols indicated by the indicated information (x / y) as uplink, and / or, starts from SBFD symbols and ends at non-SBFD symbols, and / or, starts from non-SBFD symbols and ends at SBFD symbols.

[0282] In some embodiments, a PDSCH in the plurality of PDSCHs does not have a corresponding HARQ process ID if: overlaps with SSB symbols, and / or, overlaps with the second time domain resources for uplink (UL non-SBFD symbols), and / or, overlaps with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or, overlaps with the first time domain resources (SBFD symbols) and overlaps with frequency domain resources other than downlink usable PRBs (DL usable PRBs) (or the second frequency domain resources), and / or, overlaps with symbols indicated by the indicated information as uplink, and / or, does not start from SBFD symbols and ends at non-SBFD symbols, and / or, does not start from non-SBFD symbols and ends at SBFD symbols.

[0283] In some embodiments, a PDSCH in the plurality of PDSCHs does not have a corresponding HARQ process ID if: overlaps with SSB symbols, and / or, overlaps with the second time domain resources for uplink (UL non-SBFD symbols), and / or, overlaps with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or, overlaps with the first time domain resources (SBFD symbols) and overlaps with frequency domain resources other than downlink usable PRBs (DL usable PRBs) (or the second frequency domain resources), and / or, overlaps with symbols indicated by the indicated information as uplink, and / or, does not start from SBFD symbols and ends at non-SBFD symbols, and / or, does not start from non-SBFD symbols and ends at SBFD symbols.

[0284] In some embodiments, the network device further determines, according to the PDSCH transmission limitation, the HARQ process ID corresponding to one or more of the plurality of PDSCHs and / or transmits one or more of the plurality of PDSCHs having the corresponding HARQ process ID.

[0285] In some embodiments, the PDSCH transmission limitation comprises:

[0286] the network device does not transmit (alternatively, the terminal device does not receive) the PDSCH of the plurality of PDSCHs overlapping with the second time domain resource; and / or

[0287] the network device does not transmit (alternatively, the terminal device does not receive) the PDSCH of the plurality of PDSCHs overlapping with the first time domain resource; and / or

[0288] the network device does not transmit (alternatively, the terminal device does not receive) the PDSCH of the plurality of PDSCHs overlapping with both the first time domain resource and the second time domain resource.

[0289] In some embodiments, the PDSCH transmission limitation is determined according to at least one of: RRC signaling, MAC signaling, DCI, a reference PDSCH, or a capability of the terminal device.

[0290] In some embodiments, under different PDSCH transmission limitations, the PDSCHs of the plurality of PDSCHs having the corresponding HARQ process ID need to satisfy the same condition.

[0291] In some embodiments, under different PDSCH transmission limitations, the PDSCHs of the plurality of PDSCHs having the corresponding HARQ process ID need to satisfy different conditions.

[0292] In some embodiments, the PDSCH of the plurality of PDSCHs (of the PDSCHs having the corresponding HARQ process ID) overlapping with the second time domain resource is not transmitted;

[0293] The network device transmits (alternatively, the terminal device receives) the PDSCH as follows: not overlapping with the SSB symbol, and / or, not overlapping with the second time domain resource (non-SBFD symbol), and / or, in the first time domain resource (SBFD symbol) and not overlapping with the PRB outside the downlink usable PRB (or the second frequency domain resource), and / or, not overlapping with the symbol indicated as uplink by the indicated information (X information),

[0294] and / or,

[0295] The network device does not transmit (alternatively, the terminal device does not receive) the PDSCH as follows: overlapping with the SSB symbol, and / or, overlapping with the second time domain resource (non-SBFD symbol), and / or, in the first time domain resource (SBFD symbol) and overlapping with the PRB outside the downlink usable PRB (or the second frequency domain resource), and / or, overlapping with the symbol indicated as uplink by the indicated information (X information);

[0296] and / or,

[0297] The terminal device does not expect (alternatively, the network device does not schedule) the PDSCH existing in the first time domain resource (SBFD symbol) and overlapping with the PRB outside the downlink usable PRB (or the second frequency domain resource), and / or, the terminal device does not expect (alternatively, the network device does not schedule) the PDSCH existing overlapping with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0298] In some embodiments, the PDSCH (in the PDSCH with the corresponding HARQ-process ID) overlapping with the first time domain resource is not transmitted in the plurality of PDSCHs;

[0299] The network device transmits (alternatively, the terminal device receives) the PDSCH as follows: not overlapping with the SSB, and / or, not overlapping with the first time domain resource (SBFD symbol), and / or, not overlapping with the second time domain resource (non-SBFD symbol) for uplink, and / or, not overlapping with the symbol indicated as uplink by the indicated information (Y information);

[0300] and / or,

[0301] The network device does not transmit (alternatively, the terminal device does not receive) the PDSCH as follows: overlapping with the SSB, and / or, overlapping with the first time domain resource (SBFD symbol), and / or, overlapping with the second time domain resource (non-SBFD symbol) for uplink, and / or, overlapping with the symbol indicated as uplink by the indicated information (Y information);

[0302] and / or,

[0303] The terminal device does not expect (alternatively, the network device does not schedule) the existence of a PDSCH that overlaps both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0304] In some embodiments, the PDSCH that overlaps both the first time domain resource and the second time domain resource among the plurality of PDSCHs (among the PDSCHs with corresponding HARQ-process IDs) is not transmitted;

[0305] The network device transmits (alternatively, the terminal device receives) a PDSCH that does not overlap with an SSB and / or a second time domain resource (DL non-SBFD symbol) for uplink, and / or, does not overlap both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or, is in the first time domain resource (SBFD symbol) and does not overlap a PRB other than a downlink usable PRB (DL usable PRB) (or a second frequency domain resource), and / or, does not overlap a symbol indicated as uplink by indicated information;

[0306] and / or,

[0307] The network device does not transmit (alternatively, the terminal device does not receive) a PDSCH that overlaps with an SSB, and / or, overlaps a second time domain resource (UL non-SBFD symbol) for uplink, and / or, overlaps both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or, is in the first time domain resource (SBFD symbol) and overlaps a PRB other than a downlink usable PRB (DL usable PRB) (or a second frequency domain resource), and / or, overlaps a symbol indicated as uplink by indicated information;

[0308] and / or,

[0309] The terminal device does not expect (alternatively, the network device does not schedule) the existence of a PDSCH that is in the first time domain resource (SBFD symbol) and overlaps a PRB other than a downlink usable PRB (DL usable PRB) (or a second frequency domain resource), and / or, the existence of a PDSCH that overlaps both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0310] In some embodiments, the PDSCH that overlaps both the first time domain resource and the second time domain resource among the plurality of PDSCHs (among the PDSCHs with corresponding HARQ-process IDs) can be transmitted;

[0311] The network device transmits (alternatively, the terminal device receives) the PDSCHs that do not overlap with the SSB and / or the second time domain resource for uplink (UL non-SBFD symbol) and / or overlap with the first time domain resource (SBFD symbol) and do not overlap with the PRB other than the downlink usable PRB (DL usable PRB) (or the second frequency domain resource) and / or do not overlap with the symbol indicated as uplink by the indicated information.

[0312] And / or,

[0313] The network device does not transmit (alternatively, the terminal device does not receive) the PDSCHs that overlap with the SSB and / or overlap with the second time domain resource for uplink (UL non-SBFD symbol) and / or overlap with the first time domain resource (SBFD symbol) and overlap with the PRB other than the downlink usable PRB (DL usable PRB) (or the second frequency domain resource) and / or overlap with the symbol indicated as uplink by the indicated information.

[0314] And / or,

[0315] The terminal device does not expect (alternatively, the network device does not schedule) the PDSCHs that overlap with the first time domain resource (SBFD symbol) and overlap with the PRB other than the downlink usable PRB (DL usable PRB).

[0316] In some embodiments, the transmitted PDSCHs in the plurality of PDSCHs have corresponding HARQ process IDs, and the non-transmitted PDSCHs do not have corresponding HARQ process IDs.

[0317] In some embodiments, the network device determines the HARQ process IDs corresponding to one or more PDSCHs in the plurality of PDSCHs and / or transmits one or more PDSCHs in the plurality of PDSCHs with corresponding HARQ process IDs according to the RRC signaling and / or MAC signaling and / or DCI and / or reference PDSCH and / or capability of the terminal device.

[0318] In some embodiments, the network device, in the case that the first configuration is provided by the RRC signaling and / or MAC signaling, determines the PDSCHs in the plurality of PDSCHs with corresponding HARQ process IDs and / or the PDSCHs in the plurality of PDSCHs to be received or not to be received according to the reference PDSCH and / or the first information provided by the MAC signaling and / or DCI.

[0319] The first configuration indicates that PDSCH transmission is in the first time domain resource or the second time domain resource, and the first information indicates that the network device does not send (alternatively, the terminal device does not receive) a PDSCH in the multiple PDSCHs that overlaps with the first time domain resource or a PDSCH in the multiple PDSCHs that overlaps with the second time domain resource.

[0320] In some embodiments, the reference PDSCH is a predetermined or indicated one of the DCI-scheduled PDSCHs, or a predetermined or indicated one of the PDSCHs as follows:

[0321] a PDSCH that does not overlap with the SSB and / or the second time domain resource for uplink (UL non-SBFD symbol), and / or a PDSCH that does not overlap with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol), and / or a PDSCH that overlaps with the first time domain resource (SBFD symbol) and does not overlap with a PRB other than the downlink available PRB (DL usable PRB) (or the second frequency domain resource), and / or a PDSCH that does not overlap with a symbol indicated by the indicated information as uplink.

[0322] In some embodiments, the network device, in a case where the second configuration is provided by RRC signaling and / or MAC signaling, determines, according to the reference PDSCH and / or the second information provided by the RRC signaling and / or the MAC signaling and / or the DCI, a PDSCH in the multiple PDSCHs that has a corresponding HARQ process ID, and / or a PDSCH in the multiple PDSCHs that is to be received or not to be received,

[0323] The second configuration indicates that PDSCH transmission can be in the first time domain resource and / or the second time domain resource; and the second information is used to indicate that the network device transmits (alternatively, the terminal device receives) a PDSCH in the multiple PDSCHs that overlaps with both the first time domain resource and the second time domain resource, or indicates that the network device does not transmit (alternatively, the terminal device does not receive) a PDSCH in the multiple PDSCHs that overlaps with both the first time domain resource and the second time domain resource.

[0324] The above only describes the steps or processes related to the present application, but the present application is not limited thereto. The method of the embodiments of the present application can also include other steps or processes, and the specific content of these steps or processes can be referred to the related technology.

[0325] The above embodiments only exemplarily describe the embodiments of the present application, but the present application is not limited thereto, and can be appropriately modified on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0326] As can be seen from the above embodiments, the network device transmits one or more PDSCHs with corresponding HARQ process IDs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. In this way, the network device can work in a full duplex mode (simultaneous reception and transmission), and the terminal device can also receive and transmit signals using the corresponding resources when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0327] Embodiments of the third aspect

[0328] Embodiments of the present application provide a PDSCH receiving device. The device may, for example, be a terminal device, or one or more components or assemblies configured in the terminal device. The same content as the embodiments of the first aspect will not be described again.

[0329] FIG. 23 is a schematic diagram of a PDSCH receiving device according to an embodiment of the present application. Since the principle of solving the problem of the device is the same as that of the method of the embodiments of the first aspect, the specific implementation thereof can refer to the embodiments of the first aspect, and the same content will not be described repeatedly. As shown in FIG. 23, the PDSCH receiving device 2300 includes a receiver 2301 and a processor 2302, and can further include a transmitter 2303.

[0330] In some embodiments, the receiver 2301 receives configuration information used at least for configuring the first time domain resource and / or the second time domain resource; wherein in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource;

[0331] The receiver 2301 receives downlink control information (DCI) used for scheduling multiple PDSCHs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource;

[0332] The receiver 2301 further receives one or more PDSCHs with corresponding HARQ process IDs.

[0333] In some embodiments, the HARQ process ID indicated by the DCI is applied to the first PDSCH among the multiple PDSCHs with corresponding HARQ process ID, and for each subsequent PDSCH with corresponding HARQ process ID, the HARQ process ID is the modulo operation of the scheduling order on the number of HARQ processes for PDSCHs plus 1 in turn.

[0334] In some embodiments, the PDSCHs with corresponding HARQ process ID among the multiple PDSCHs do not overlap with SSB symbols, and / or, do not overlap with the second time domain resources for uplink (UL non-SBFD symbols), and / or, do not overlap with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or, overlap with the first time domain resources (SBFD symbols) and do not overlap with the frequency domain resources other than the downlink usable PRBs (or the second frequency domain resources), and / or, do not overlap with the symbols indicated as uplink by the indicated information (x / y), and / or, start from the SBFD symbols and end at the non-SBFD symbols, and / or, start from the non-SBFD symbols and end at the SBFD symbols.

[0335] In some embodiments, the PDSCHs with corresponding HARQ process ID among the multiple PDSCHs do not overlap with SSB symbols, and / or, do not overlap with the second time domain resources for uplink (UL non-SBFD symbols), and / or, do not overlap with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or, overlap with the first time domain resources (SBFD symbols) and do not overlap with the frequency domain resources other than the downlink usable PRBs (or the second frequency domain resources), and / or, do not overlap with the symbols indicated as uplink by the indicated information (x / y), and / or, start from the SBFD symbols and end at the non-SBFD symbols, and / or, start from the non-SBFD symbols and end at the SBFD symbols.

[0336] In some embodiments, the PDSCHs in the plurality of PDSCHs that do not have a corresponding HARQ process ID overlap with SSB symbols, and / or overlap with the second time-domain resources (UL non-SBFD symbols) for uplink, and / or overlap with both the first time-domain resources (SBFD symbols) and the second time-domain resources (non-SBFD symbols), and / or overlap with the first time-domain resources (SBFD symbols) and overlap with frequency-domain resources other than downlink usable PRBs (DL usable PRBs), and / or overlap with symbols indicated as uplink by the indicated information, and / or do not start from SBFD symbols and end at non-SBFD symbols, and / or do not start from non-SBFD symbols and end at SBFD symbols.

[0337] In some embodiments, the PDSCHs in the plurality of PDSCHs that do not have a corresponding HARQ process ID overlap with SSB symbols, and / or overlap with the second time-domain resources (UL non-SBFD symbols) for uplink, and / or overlap with both the first time-domain resources (SBFD symbols) and the second time-domain resources (non-SBFD symbols), and / or overlap with the first time-domain resources (SBFD symbols) and overlap with frequency-domain resources other than downlink usable PRBs (DL usable PRBs), and / or overlap with symbols indicated as uplink by the indicated information, and / or do not start from SBFD symbols and end at non-SBFD symbols, and / or do not start from non-SBFD symbols and end at SBFD symbols.

[0338] In some embodiments, the processor 2302 further determines, according to the PDSCH reception restriction, the HARQ process ID corresponding to one or more PDSCHs in the plurality of PDSCHs, and / or the receiver 2301 further receives one or more PDSCHs in the plurality of PDSCHs that have a corresponding HARQ process ID,

[0339] wherein the PDSCH reception restriction comprises:

[0340] the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with the second time-domain resources; and / or

[0341] the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with the first time-domain resources; and / or

[0342] the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with both the first time-domain resources and the second time-domain resources.

[0343] In some embodiments, the PDSCH reception restriction is determined according to at least one of: RRC signaling, MAC signaling, DCI, a reference PDSCH, or a capability of the terminal device.

[0344] In some embodiments, under different PDSCH reception restrictions, the conditions that the PDSCHs with corresponding HARQ process IDs in the plurality of PDSCHs need to satisfy are the same.

[0345] In some embodiments, under different PDSCH reception restrictions, the conditions that the PDSCHs with corresponding HARQ process IDs in the plurality of PDSCHs need to satisfy are different.

[0346] In some embodiments, the PDSCHs (in the plurality of PDSCHs (with corresponding HARQ-process IDs)) that overlap with the second time-domain resources are not transmitted;

[0347] The receiver 2301 receives the PDSCHs that do not overlap with the SSB symbols, and / or, do not overlap with the second time-domain resources (non-SBFD symbols), and / or, are in the first time-domain resources (SBFD symbols) and do not overlap with the PRBs other than the downlink usable PRBs (or the second frequency-domain resources), and / or, do not overlap with the symbols indicated as uplink by the indicated information (X information),

[0348] and / or,

[0349] The receiver 2301 does not receive the PDSCHs that overlap with the SSB symbols, and / or, overlap with the second time-domain resources (non-SBFD symbols), and / or, are in the first time-domain resources (SBFD symbols) and overlap with the PRBs other than the downlink usable PRBs (or the second frequency-domain resources), and / or, overlap with the symbols indicated as uplink by the indicated information (X information);

[0350] and / or,

[0351] The terminal device does not expect the PDSCHs that are in the first time-domain resources (SBFD symbols) and overlap with the PRBs other than the downlink usable PRBs (or the second frequency-domain resources), and / or, the terminal device does not expect the PDSCHs that overlap with both the first time-domain resources (SBFD symbols) and the second time-domain resources (non-SBFD symbols).

[0352] In some embodiments, the PDSCHs (in the plurality of PDSCHs (with corresponding HARQ-process IDs)) that overlap with the first time-domain resources are not transmitted;

[0353] The receiver 2301 receives a PDSCH that does not overlap with an SSB, and / or does not overlap with the first time-domain resource (SBFD symbol), and / or does not overlap with the second time-domain resource (non-SBFD symbol) for uplink, and / or does not overlap with a symbol indicated as uplink by the indicated information (Y information);

[0354] and / or,

[0355] The receiver 2301 does not receive a PDSCH that overlaps with an SSB, and / or overlaps with the first time-domain resource (SBFD symbol), and / or overlaps with the second time-domain resource (non-SBFD symbol) for uplink, and / or overlaps with a symbol indicated as uplink by the indicated information (Y information);

[0356] and / or,

[0357] The terminal device does not expect a PDSCH that overlaps with both the first time-domain resource (SBFD symbol) and the second time-domain resource (non-SBFD symbol) to exist.

[0358] In some embodiments, a PDSCH that overlaps with both the first time-domain resource and the second time-domain resource (in a PDSCH with a corresponding HARQ-process ID) is not transmitted among the plurality of PDSCHs;

[0359] The receiver 2301 receives a PDSCH that does not overlap with an SSB and / or the second time-domain resource (DL non-SBFD symbol) for uplink, and / or does not overlap with both the first time-domain resource (SBFD symbol) and the second time-domain resource (non-SBFD symbol), and / or is in the first time-domain resource (SBFD symbol) and does not overlap with a PRB other than a downlink usable PRB (or a second frequency-domain resource), and / or does not overlap with a symbol indicated as uplink by the indicated information;

[0360] and / or,

[0361] The receiver 2301 does not receive a PDSCH that overlaps with an SSB, and / or overlaps with the second time-domain resource (UL non-SBFD symbol) for uplink, and / or overlaps with both the first time-domain resource (SBFD symbol) and the second time-domain resource (non-SBFD symbol), and / or is in the first time-domain resource (SBFD symbol) and overlaps with a PRB other than a downlink usable PRB (or a second frequency-domain resource), and / or overlaps with a symbol indicated as uplink by the indicated information;

[0362] and / or,

[0363] The terminal device does not expect a PDSCH that overlaps with the first time domain resource (SBFD symbol) and a PRB other than the downlink usable PRB (or the second frequency domain resource), and / or a PDSCH that overlaps with both the first time domain resource (SBFD symbol) and the second time domain resource (non-SBFD symbol).

[0364] In some embodiments, a PDSCH that overlaps with both the first time domain resource and the second time domain resource among the plurality of PDSCHs (a PDSCH with a corresponding HARQ-process ID) can be transmitted.

[0365] The receiver 2301 receives a PDSCH that does not overlap with an SSB and / or a second time domain resource for uplink (UL non-SBFD symbol), and / or overlaps with the first time domain resource (SBFD symbol) and does not overlap with a PRB other than the downlink usable PRB (or the second frequency domain resource), and / or does not overlap with a symbol indicated by the indicated information as uplink.

[0366] and / or,

[0367] The receiver 2301 does not receive a PDSCH that overlaps with an SSB, and / or overlaps with a second time domain resource for uplink (UL non-SBFD symbol), and / or overlaps with the first time domain resource (SBFD symbol) and overlaps with a PRB other than the downlink usable PRB (or the second frequency domain resource), and / or overlaps with a symbol indicated by the indicated information as uplink.

[0368] and / or,

[0369] The terminal device does not expect a PDSCH that overlaps with the first time domain resource (SBFD symbol) and a PRB other than the downlink usable PRB (or the second frequency domain resource).

[0370] In some embodiments, a PDSCH that is transmitted among the plurality of PDSCHs has a corresponding HARQ process ID, and a PDSCH that is not transmitted does not have a corresponding HARQ process ID.

[0371] In some embodiments, the processor 2302 determines the HARQ process IDs corresponding to one or more of the plurality of PDSCHs according to the RRC signaling and / or the MAC signaling and / or the DCI and / or the reference PDSCH and / or the capability of the terminal device, and / or the receiver 2301 receives one or more of the plurality of PDSCHs having the corresponding HARQ process IDs.

[0372] In some embodiments, the processor 2302 determines the PDSCHs having the corresponding HARQ process IDs in the plurality of PDSCHs according to the reference PDSCH and / or the first information provided by the MAC signaling and / or the DCI, and / or the PDSCHs to be received or not to be received in the plurality of PDSCHs, in a case that a first configuration is provided by the RRC signaling and / or the MAC signaling,

[0373] wherein the first configuration indicates that the PDSCH receptions are all in the first time domain resources or in the second time domain resources, and the first information indicates that the terminal device does not receive the PDSCHs in the plurality of PDSCHs overlapping with the first time domain resources or the PDSCHs overlapping with the second time domain resources.

[0374] In some embodiments, the reference PDSCH is a predetermined or indicated one of the DCI scheduled PDSCHs, or a predetermined or indicated one of the PDSCHs as follows:

[0375] a PDSCH not overlapping with the SSB and / or the second time domain resources for uplink (UL non-SBFD symbols), and / or a PDSCH not overlapping with both the first time domain resources (SBFD symbols) and the second time domain resources (non-SBFD symbols), and / or a PDSCH overlapping with the first time domain resources (SBFD symbols) and not overlapping with the PRBs other than the downlink usable PRBs (or the second frequency domain resources), and / or a PDSCH not overlapping with the symbols indicated by the indicated information as uplink.

[0376] In some embodiments, the processor 2302 determines the PDSCHs having the corresponding HARQ process IDs in the plurality of PDSCHs according to the reference PDSCH and / or the second information provided by the RRC signaling and / or the MAC signaling and / or the DCI, and / or the PDSCHs to be received or not to be received in the plurality of PDSCHs, in a case that a second configuration is provided by the RRC signaling and / or the MAC signaling,

[0377] The second configuration indicates that the PDSCH reception can be in the first time domain resource and / or the second time domain resource; and the second information is used to indicate the terminal device to receive a PDSCH of the multiple PDSCHs that overlaps both the first time domain resource and the second time domain resource, or to indicate the terminal device not to receive the PDSCH of the multiple PDSCHs that overlaps both the first time domain resource and the second time domain resource.

[0378] It is worth noting that only the components or modules related to the present application are described above, but the present application is not limited thereto. The PDSCH receiving apparatus 2300 of the embodiments of the present application can also include other components or modules, and the specific content of these components or modules can be referred to the related art.

[0379] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 23, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc.; the present application is not limited thereto.

[0380] The above embodiments are only exemplarily described, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0381] As can be seen from the above embodiments, the terminal device receives one or more PDSCHs with corresponding HARQ process IDs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. Thus, the network device can work in a full duplex mode (simultaneous reception and transmission), and the terminal device can also use the corresponding resources to transceive signals when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0382] Embodiments of the fourth aspect

[0383] The embodiments of the present application provide a PDSCH sending apparatus. The apparatus can be a network device, or can be one or more components or components configured in the network device, and the same content as the embodiments of the third aspect will not be described herein.

[0384] FIG. 24 is a schematic diagram of a PDSCH sending device according to an embodiment of the present application. Since the principle of solving the problem of the device is the same as that of the method of the first and second embodiments, the specific implementation can refer to the first and second embodiments, and the same content will not be repeated. As shown in FIG. 24, the PDSCH sending device 2400 includes a transmitter 2401 and a processor 2402, and can further include a receiver 2403.

[0385] The transmitter 2401 sends configuration information for configuring at least the first time domain resource and / or the second time domain resource; wherein in the first time domain resource, the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink, and the second time domain resource is outside the first time domain resource.

[0386] The transmitter 2401 sends downlink control information (DCI) for scheduling multiple PDSCHs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0387] The transmitter 2401 further sends one or more of the PDSCHs having a corresponding HARQ process ID in the multiple PDSCHs.

[0388] It is worth noting that only the components or modules related to the present application are described above, but the present application is not limited thereto. The PDSCH receiving device 2400 of the embodiments of the present application can further include other components or modules, and the specific content of these components or modules can refer to related technologies.

[0389] In addition, for the sake of simplicity, only the connection relationship or signal path between the components or modules is exemplarily shown in FIG. 24, but those skilled in the art should understand that various related technologies such as bus connection can be used. The above components or modules can be realized by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.

[0390] The above embodiments are only exemplarily described, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0391] From the above embodiments, the network device transmits one or more PDSCHs with corresponding HARQ process IDs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource. In this way, the network device can work in a full duplex mode (simultaneous receiving and transmitting), and the terminal device can also receive and transmit signals using the corresponding resources when the network device works in the full duplex mode, which can improve the capacity and coverage of uplink transmission, reduce the latency of uplink transmission, and improve the resource allocation flexibility and resource utilization.

[0392] Embodiments of the fifth aspect

[0393] Embodiments of the present application also provide a communication system, which can refer to FIG. 1, and the same content as the embodiments of the first to fourth aspects will not be repeated.

[0394] In some embodiments, the communication system 100 can at least include:

[0395] The terminal device receives configuration information at least for configuring the first time domain resource and / or the second time domain resource; wherein the first frequency domain resource is used for uplink and the second frequency domain resource is used for downlink in the first time domain resource, and the second time domain resource is outside the first time domain resource; receives downlink control information (DCI) for scheduling multiple PDSCHs, wherein whether one of the multiple PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and receives one or more PDSCHs in the multiple PDSCHs with corresponding HARQ process IDs.

[0396] The network device transmits configuration information at least for configuring the first time domain resource and / or the second time domain resource; transmits downlink control information (DCI) for scheduling multiple PDSCHs; and transmits one or more PDSCHs in the multiple PDSCHs with corresponding HARQ process IDs.

[0397] Embodiments of the present application also provide a network device, which can be a base station for example, but the present application is not limited thereto, and can also be other network devices.

[0398] FIG. 25 is a schematic diagram of the network device according to an embodiment of the present application. As shown in FIG. 25, the network device 2500 can include a processor 2510 (such as a central processing unit CPU) and a memory 2520; the memory 2520 is coupled to the processor 2510. The memory 2520 can store various data; in addition, it also stores a program 2530 for information processing, and executes the program 2530 under the control of the processor 2510.

[0399] For example, the processor 2510 can be configured to execute programs to implement the method according to the embodiments of the second aspect.

[0400] In addition, as shown in FIG. 25, the network device 2500 can further include a transceiver 2540, an antenna 2550, and the like; wherein the functions of the above components are similar to those of the prior art, which will not be repeated here. It is worth noting that the network device 2500 does not necessarily include all the components shown in FIG. 25; in addition, the network device 2500 can also include components not shown in FIG. 25, which can be referred to the prior art.

[0401] The embodiments of the present application also provide a terminal device, but the present application is not limited thereto, and can also be other devices.

[0402] FIG. 26 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 26, the terminal device 2600 can include a processor 2610 and a memory 2620; the memory 2620 stores data and programs and is coupled to the processor 2610. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunication functions or other functions.

[0403] For example, the processor 2610 can be configured to execute programs to implement the method according to the embodiments of the first aspect.

[0404] As shown in FIG. 26, the terminal device 2600 can further include a communication module 2630, an input device 2640, a display 2650, and a power supply 2660. Wherein the functions of the above components are similar to those of the prior art, which will not be repeated here. It is worth noting that the terminal device 2600 does not necessarily include all the components shown in FIG. 26; the above components are not essential; in addition, the terminal device 2600 can also include components not shown in FIG. 26, which can be referred to the prior art.

[0405] The embodiments of the present application also provide a computer readable program, wherein when the program is executed in the network device, the program causes the computer to execute the method according to the embodiments of the second aspect in the network device.

[0406] The embodiments of the present application also provide a storage medium storing a computer readable program, wherein the computer readable program causes the computer to execute the method according to the embodiments of the second aspect in the network device.

[0407] The embodiments of the present application also provide a computer readable program, wherein when the program is executed in the terminal device, the program causes the computer to execute the method according to the embodiments of the first aspect in the terminal device.

[0408] The embodiment of the present application further provides a storage medium storing a computer readable program, wherein the computer readable program causes a computer to execute the method in the embodiment of the first aspect in a terminal device.

[0409] The apparatus and method described above can be implemented by hardware, or by hardware in combination with software. The present application relates to a computer readable program which, when executed by a logic component, causes the logic component to implement the apparatus or constituent components described above, or causes the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, or the like. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, or the like.

[0410] The method / apparatus described in combination with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figures and / or a combination of one or more of the functional block diagrams can correspond to each software module of a computer program flow, or to each hardware module. The software modules can correspond to each step shown in the figures, respectively. These hardware modules can be implemented by, for example, fixing the software modules using a field programmable gate array (FPGA).

[0411] The software modules can be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, so that the processor can read information from the storage medium, and can write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and the storage medium can be located in an ASIC. The software modules can be stored in a memory of the mobile terminal, or in a memory card which can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a MEGA-SIM card or a large capacity flash memory device, the software modules can be stored in the MEGA-SIM card or the large capacity flash memory device.

[0412] One or more of the functional blocks described in the figures and / or one or more combinations of the functional blocks can be implemented as a general- purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof, for performing the functions described in this disclosure. One or more of the functional blocks described in the figures and / or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0413] The present application has been described above with the attachment to the specific embodiments, but it should be clear to those skilled in the art that these descriptions are exemplary and are not a limitation on the scope of protection of the present application. Those skilled in the art can make various modifications and changes to the present application according to the spirit and principles of the present application, and these modifications and changes are within the scope of the present application.

[0414] In connection with the embodiments including the above embodiments, the following notes are also disclosed:

[0415] 1. A PDSCH receiving method, comprising:

[0416] A terminal device receives configuration information at least for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, and the second time domain resource is outside the first time domain resource;

[0417] The terminal device receives downlink control information (DCI) for scheduling a plurality of PDSCHs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0418] The terminal device receives one or more of the plurality of PDSCHs that have a corresponding HARQ process ID.

[0419] 2. A PDSCH transmitting method, comprising:

[0420] A network device transmits configuration information at least for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, and the second time domain resource is outside the first time domain resource;

[0421] The network device transmits downlink control information (DCI) for scheduling the plurality of PDSCHs, wherein whether one of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and

[0422] The network device transmits one or more of the PDSCHs of the plurality of PDSCHs that have a corresponding HARQ process ID.

[0423] 3. A terminal device comprising a memory and a processor, the memory storing a computer program, and the processor configured to execute the computer program to implement the PDSCH receiving method of the appended 1.

[0424] 4. A network device comprising a memory and a processor, the memory storing a computer program, and the processor configured to execute the computer program to implement the PDSCH transmitting method of the appended 2.

[0425] 5. A computer program product comprising at least a computer program, the computer program being executed by a processor to cause a terminal device to execute the PDSCH receiving method of the appended 1.

[0426] 6. A computer program product comprising at least a computer program, the computer program being executed by a processor to cause a network device to execute the PDSCH transmitting method of the appended 2.

Claims

A PDSCH receiving apparatus, comprising: a receiver configured to receive configuration information at least for configuring a first time domain resource and / or a second time domain resource; wherein in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, and the second time domain resource is outside the first time domain resource; the receiver is configured to receive downlink control information for scheduling a plurality of PDSCHs, wherein whether a PDSCH of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and the receiver is further configured to receive at least one PDSCH of the plurality of PDSCHs having a corresponding HARQ process ID. The apparatus of claim 1, wherein Whether a PDSCH has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource, comprising: if the PDSCH overlaps with the second time domain resource for uplink, the PDSCH does not have a corresponding HARQ process ID, and / or, if the PDSCH overlaps with the first time domain resource, the PDSCH does not have a corresponding HARQ process ID, and / or, if the PDSCH overlaps with both the first time domain resource and the second time domain resource, the PDSCH does not have a corresponding HARQ process ID, and / or, if the PDSCH overlaps with both the first time domain resource and the second time domain resource, the PDSCH does not have a corresponding HARQ process ID, and / or, if the PDSCH overlaps with the first time domain resource and overlaps with a frequency domain resource outside the PRB available for downlink, the PDSCH does not have a corresponding HARQ process ID. The apparatus of claim 1, wherein The apparatus further comprises: a processor configured to determine a corresponding HARQ process ID for a PDSCH having a corresponding HARQ process ID, wherein the HARQ process ID indicated by the downlink control information is applied to a first PDSCH of the plurality of PDSCHs having a corresponding HARQ process ID, and for each subsequent PDSCH having a corresponding HARQ process ID, the HARQ process ID is obtained by performing a modulo operation on a number of HARQ processes for the PDSCH in a scheduling order and sequentially adding 1. The apparatus of claim 1, wherein The PDSCHs of the plurality of PDSCHs having a corresponding HARQ process ID do not overlap with SSB symbols, and / or, do not overlap with the second time domain resource for uplink, and / or, do not overlap with both the first time domain resource and the second time domain resource, and / or, overlap with the first time domain resource and do not overlap with a frequency domain resource outside the PRB available for downlink, and / or, do not overlap with symbols indicated by the indicated information as uplink, and / or, start from an SBFD symbol and end at a non-SBFD symbol, and / or, start from a non-SBFD symbol and end at an SBFD symbol. The apparatus of claim 1, wherein The PDSCHs in the plurality of PDSCHs that do not overlap with the SSB symbols, and / or, do not overlap with the second time domain resources for uplink, and / or, do not overlap with both the first time domain resources and the second time domain resources, and / or, overlap with the first time domain resources and do not overlap with the frequency domain resources other than the PRBs available for downlink, and / or, do not overlap with the symbols indicated by the indicated information as uplink, and / or, start from the SBFD symbols and end at the non-SBFD symbols, and / or, start from the non-SBFD symbols and end at the SBFD symbols, have corresponding HARQ process IDs. The apparatus of claim 1, wherein The PDSCHs in the plurality of PDSCHs that overlap with the SSB symbols, and / or, overlap with the second time domain resources for uplink, and / or, overlap with both the first time domain resources and the second time domain resources, and / or, overlap with the first time domain resources and overlap with the frequency domain resources other than the PRBs available for downlink, and / or, overlap with the symbols indicated by the indicated information as uplink, and / or, do not start from the SBFD symbols and end at the non-SBFD symbols, and / or, do not start from the non-SBFD symbols and end at the SBFD symbols, do not have corresponding HARQ process IDs. The apparatus of claim 1, wherein The apparatus further includes: a processor that determines, according to a PDSCH reception restriction, corresponding HARQ process IDs of one or more PDSCHs in the plurality of PDSCHs; wherein the PDSCH reception restriction includes: the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with the second time domain resources; and / or the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with the first time domain resources; and / or the terminal device does not receive the PDSCHs in the plurality of PDSCHs that overlap with both the first time domain resources and the second time domain resources. The apparatus of claim 7, wherein The PDSCH reception restriction is indicated or determined according to at least one of: RRC signaling, MAC signaling, the downlink control information, a reference PDSCH, or a capability of the terminal device. The apparatus of claim 7, wherein Under different PDSCH reception restrictions, the PDSCHs in the plurality of PDSCHs that have corresponding HARQ process IDs need to satisfy the same conditions, or, Under different PDSCH reception restrictions, the PDSCHs in the plurality of PDSCHs that have corresponding HARQ process IDs need to satisfy different conditions. The apparatus of claim 1, wherein The PDSCHs in the plurality of PDSCHs that overlap with the second time domain resources are not received; the receiver receives the PDSCHs that do not overlap with the SSB symbols, and / or, do not overlap with the second time domain resources, and / or, are in the first time domain resources and do not overlap with the PRBs other than the PRBs available for downlink, and / or, do not overlap with the symbols indicated by the indicated information as uplink, and / or, the receiver does not receive the PDSCHs that overlap with the SSB symbols, and / or, overlap with the second time domain resources, and / or, are in the first time domain resources and overlap with the PRBs other than the PRBs available for downlink, and / or, overlap with the symbols indicated by the indicated information as uplink; and / or, The terminal device does not expect a PDSCH that overlaps with the first time domain resource and that overlaps with PRBs other than the downlink available PRBs in the first time domain resource, and / or the terminal device does not expect a PDSCH that overlaps with both the first time domain resource and the second time domain resource. The apparatus of claim 1, wherein The PDSCHs in the plurality of PDSCHs that overlap with the first time domain resource are not received; The receiver receives a PDSCH that does not overlap with an SSB, and / or that does not overlap with the first time domain resource, and / or that does not overlap with the second time domain resource for uplink, and / or that does not overlap with a symbol indicated by the indicated information as uplink; and / or, The receiver does not receive a PDSCH that overlaps with an SSB, and / or that overlaps with the second time domain resource for uplink, and / or that overlaps with both the first time domain resource and the second time domain resource, and / or that overlaps with a symbol indicated by the indicated information as uplink; and / or, The terminal device does not expect a PDSCH that overlaps with both the first time domain resource and the second time domain resource. The apparatus of claim 1, wherein The PDSCHs in the plurality of PDSCHs that overlap with both the first time domain resource and the second time domain resource are not received; The receiver receives a PDSCH that does not overlap with an SSB and / or the second time domain resource for uplink, and / or that does not overlap with both the first time domain resource and the second time domain resource, and / or that is in the first time domain resource and that does not overlap with PRBs other than the downlink available PRBs, and / or that does not overlap with a symbol indicated by the indicated information as uplink; and / or, The receiver does not receive a PDSCH that overlaps with an SSB, and / or that overlaps with the second time domain resource for uplink, and / or that overlaps with both the first time domain resource and the second time domain resource, and / or that overlaps with a symbol indicated by the indicated information as uplink; and / or, The terminal device does not expect a PDSCH that overlaps with both the first time domain resource and the second time domain resource. The PDSCHs in the plurality of PDSCHs that overlap with both the first time domain resource and the second time domain resource can be received; The apparatus of claim 1, wherein The receiver receives a PDSCH that does not overlap with an SSB and / or the second time domain resource for uplink, and / or that overlaps with the first time domain resource and that does not overlap with PRBs other than the downlink available PRBs, and / or that does not overlap with a symbol indicated by the indicated information as uplink; and / or, The receiver does not receive a PDSCH that overlaps with an SSB, and / or that overlaps with the second time domain resource for uplink, and / or that overlaps with the first time domain resource and that overlaps with PRBs other than the downlink available PRBs, and / or that overlaps with a symbol indicated by the indicated information as uplink; and / or, The terminal device does not expect a PDSCH that overlaps with the first time domain resource and that overlaps with PRBs other than the downlink available PRBs in the first time domain resource, and / or the terminal device does not expect a PDSCH that overlaps with both the first time domain resource and the second time domain resource. The PDSCHs in the plurality of PDSCHs that overlap with both the first time domain resource and the second time domain resource can be received; The receiver receives a PDSCH that does not overlap with an SSB and / or the second time domain resource for uplink, and / or that overlaps with the first time domain resource and that does not overlap with PRBs other than the downlink available PRBs, and / or that does not overlap with a symbol indicated by the indicated information as uplink; and / or, The receiver does not receive a PDSCH that overlaps with an SSB, and / or that overlaps with the second time domain resource for uplink, and / or that overlaps with the first time domain resource and that overlaps with PRBs other than the downlink available PRBs, and / or that overlaps with a symbol indicated by the indicated information as uplink; and / or, The terminal device does not expect a PDSCH that overlaps with the first time domain resource and that overlaps with PRBs other than the downlink available PRBs in the first time domain resource, and / or the terminal device does not expect a PDSCH that overlaps with both the first time domain resource and the second time domain resource. The apparatus of claim 1, wherein The received PDSCHs in the plurality of PDSCHs have corresponding HARQ process IDs, and the non-received PDSCHs do not have corresponding HARQ process IDs. The apparatus of claim 1, wherein The apparatus further comprises: a processor configured to determine, according to RRC signaling and / or MAC signaling and / or the downlink control information and / or a reference PDSCH and / or a capability of the terminal device, one or more PDSCHs in the plurality of PDSCHs that have corresponding HARQ process IDs, and / or receive one or more PDSCHs in the plurality of PDSCHs that have corresponding HARQ process IDs. The apparatus according to claim 15, wherein when the processor is provided with a first configuration by the RRC signaling and / or the MAC signaling, the processor is configured to determine, according to a reference PDSCH and / or first information provided by the MAC signaling and / or the downlink control information, PDSCHs in the plurality of PDSCHs that have corresponding HARQ process IDs, and / or PDSCHs in the plurality of PDSCHs that are to be received or not to be received, wherein the first configuration indicates that PDSCH receptions are all in the first time domain resources or all in the second time domain resources, and the first information indicates that the terminal device is not to receive PDSCHs in the plurality of PDSCHs that overlap with the first time domain resources or PDSCHs that overlap with the second time domain resources. The reference PDSCH is a predetermined or indicated one of the PDSCHs scheduled by the downlink control information, or a predetermined or indicated one of the PDSCHs that: The apparatus of claim 15, wherein do not overlap with SSBs and / or the second time domain resources for uplink, and / or do not overlap with both the first time domain resources and the second time domain resources, and / or overlap with the first time domain resources and do not overlap with PRBs other than downlink available PRBs, and / or do not overlap with symbols indicated by the indicated information as uplink. The apparatus according to claim 15, wherein when the processor is provided with a second configuration by the RRC signaling and / or the MAC signaling, the processor is configured to determine, according to a reference PDSCH and / or second information provided by the RRC signaling and / or the MAC signaling and / or the downlink control information, PDSCHs in the plurality of PDSCHs that have corresponding HARQ process IDs, and / or PDSCHs in the plurality of PDSCHs that are to be received or not to be received, wherein the second configuration indicates that PDSCH receptions can be in the first time domain resources and / or the second time domain resources; and the second information is used to indicate that the terminal device is to receive PDSCHs in the plurality of PDSCHs that overlap with both the first time domain resources and the second time domain resources, or to indicate that the terminal device is not to receive PDSCHs in the plurality of PDSCHs that overlap with both the first time domain resources and the second time domain resources. A PDSCH transmitting apparatus, comprising: ​ a transmitter that transmits configuration information for configuring at least a first time domain resource and / or a second time domain resource; wherein, in the first time domain resource, a first frequency domain resource is for uplink and a second frequency domain resource is for downlink, the second time domain resource is outside the first time domain resource; the transmitter transmits downlink control information for scheduling a plurality of PDSCHs, wherein whether a PDSCH of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and the transmitter further transmits one or more PDSCHs of the plurality of PDSCHs that have a corresponding HARQ process ID. A communication system comprising: a terminal device that receives configuration information for configuring at least a first time domain resource and / or a second time domain resource; receives downlink control information for scheduling a plurality of PDSCHs, wherein whether a PDSCH of the plurality of PDSCHs has a corresponding HARQ process ID is related to the first time domain resource and / or the second time domain resource; and receives one or more PDSCHs of the plurality of PDSCHs that have a corresponding HARQ process ID; a network device that transmits configuration information for configuring at least a first time domain resource and / or a second time domain resource; transmits downlink control information for scheduling a plurality of PDSCHs; and transmits one or more PDSCHs of the plurality of PDSCHs that have a corresponding HARQ process ID. ​

Images