Data receiving method and device

Abstract

An embodiment of the present invention provides a data reception method, a data transmission method, and an apparatus, which include: a step of receiving, by a terminal device, downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), where the DCI includes a first information field for indicating time domain resources of at least two (M) first PDSCHs; and a step of receiving, by the terminal device, at least one (N) second PDSCH.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present invention relates to the field of communications technology. [Background technology]

[0002] A Physical Downlink Shared Channel (PDSCH) is a type of physical downlink channel for carrying downlink data in a wireless communication system. The PDSCH may be scheduled by downlink control information (DCI). The DCI for scheduling the PDSCH includes at least information indicating the resource of the PDSCH. In the current new radio (NR) system, multiple DCI formats for scheduling the PDSCH, such as DCI format 1_0, DCI format 1_1, DCI format 1_2, etc., are defined, and DCI of different DCI formats includes different specific information and / or size to meet different scheduling requirements. Note that the above description of the background art is merely for the purpose of more clearly and completely describing the configuration of the present invention, and is described for the understanding of those skilled in the art. These configurations are described in the background art of the present invention, so it should not be interpreted as being known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]

[0003] In the current NR system, only one PDSCH can be scheduled for one DCI. As discovered by the inventors of the present invention, in some cases, such a scheduling method has a problem that the load of monitoring the DCI (PDCCH) is high for the terminal device, and the complexity and power consumption of the device are also high.

[0004] For example, how to support the NR system to operate at higher frequencies (52.6 GHz or higher) is currently being considered, and data transmission at higher frequencies will face more serious problems such as phase noise. Therefore, in order to overcome problems such as phase noise, it may be necessary to adopt a larger subcarrier spacing (e.g., 240 kHz, 480 kHz, 960 kHz, etc.) to support data transmission at higher frequencies, while the larger subcarrier spacing means a shorter symbol length. If the current frame structure design of NR (one slot contains 14 symbols) is used as is, the larger subcarrier spacing means a shorter slot length. On the other hand, if the above scheduling method is adopted to support the terminal equipment (UE) receiving at least one PDSCH in each slot, the UE needs to monitor DCI in each slot. In this way, if the above larger subcarrier spacing is adopted, the slot length will be shortened, and the number of DCI monitoring times per unit time of the UE will increase. In other words, the load of DCI monitoring on the UE will increase, and the implementation complexity and power consumption of the UE will increase.

[0005] In view of at least one of the above problems, embodiments of the present invention provide a method and apparatus for receiving data. [Means for solving the problem]

[0006] In one aspect of an embodiment of the present invention, a data receiving device applicable to a terminal device is provided, the data receiving device including: a first receiving unit that receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), the DCI including a first information field for indicating time domain resources of at least two (M) first PDSCHs; and a second receiving unit that receives at least one (N) second PDSCH.

[0007] In another aspect of an embodiment of the present invention, a data transmission device applied to a network device is provided, the data transmission device including: a third transmission unit that transmits downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) to a terminal device, the DCI including a first information field for indicating time domain resources of at least two (M) first PDSCHs; and a fourth transmission unit that transmits at least one (N) second PDSCH to the terminal device.

[0008] One of the advantageous effects of the embodiment of the present invention is as follows: Multiple PDSCHs can be scheduled by one DCI, which can reduce the DCI monitoring burden of the terminal device, and reduce power consumption and complexity.

[0009] As shown in the following description and drawings, specific embodiments of the present invention are disclosed in detail to show how the principles of the present invention can be employed. However, the scope of the embodiments of the present invention is not limited to these. The embodiments of the present invention include modifications, alterations, and equivalents within the spirit and scope of the appended claims.

[0010] Features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments and may be combined with or substituted for features in the other embodiments.

[0011] It should be noted that in this text, the term "including" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief description of the drawings]

[0012] Elements and features depicted in one drawing and one embodiment of the present invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may designate corresponding elements in multiple drawings and may designate corresponding elements used in more than one embodiment. [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a schematic diagram of a data receiving method according to an embodiment of the present invention; [Figure 3A] 3A-3C are schematic diagrams of time domain locations of at least two (M) first PDSCHs according to an embodiment of the present invention. [Figure 3B] 3A-3C are schematic diagrams of time domain locations of at least two (M) first PDSCHs according to an embodiment of the present invention. [Figure 3C] 3A-3C are schematic diagrams of time domain locations of at least two (M) first PDSCHs according to an embodiment of the present invention. [Figure 4A] 4A and 4B are schematic diagrams of time domain locations of at least two (M) first PDSCHs according to an embodiment of the present invention. [Figure 4B] 4A and 4B are schematic diagrams of time domain locations of at least two (M) first PDSCHs according to an embodiment of the present invention. [Figure 5A] 5A-5G are schematic diagrams of one of the time domain locations of at least one (N) second PDSCH in accordance with an embodiment of the present invention. [Figure 5B] 5A-5G are schematic diagrams of one of the time domain locations of at least one (N) second PDSCH in accordance with an embodiment of the present invention. [Figure 5C] 5A-5G are schematic diagrams of one of the time domain locations of at least one (N) second PDSCH in accordance with an embodiment of the present invention. [Figure 5D] 5A-5G are schematic diagrams of one of the time domain locations of at least one (N) second PDSCH in accordance with an embodiment of the present invention. [Figure 5E]5A-5G are schematic diagrams of one of the time domain locations of at least one (N) second PDSCH in accordance with an embodiment of the present invention. [Figure 5F] 5A-5G are schematic diagrams of one of the time domain locations of at least one (N) second PDSCH in accordance with an embodiment of the present invention. [Figure 5G] 5A-5G are schematic diagrams of one of the time domain locations of at least one (N) second PDSCH in accordance with an embodiment of the present invention. [Figure 6A] FIG. 13 is a schematic diagram of a HARQ process identifier of at least one (N) second PDSCH in an embodiment of the present invention. [Figure 6B] 4 is a schematic diagram of HARQ process identifiers of at least two (M) first PDSCHs in an embodiment of the present invention; FIG. [Figure 7A] 7A to 7F are schematic diagrams of slots for HARQ-ACK feedback according to an embodiment of the present invention. [Figure 7B] 7A to 7F are schematic diagrams of slots for HARQ-ACK feedback according to an embodiment of the present invention. [Figure 7C] 7A to 7F are schematic diagrams of slots for HARQ-ACK feedback according to an embodiment of the present invention. [Figure 7D] 7A to 7F are schematic diagrams of slots for HARQ-ACK feedback according to an embodiment of the present invention. [Figure 7E] 7A to 7F are schematic diagrams of slots for HARQ-ACK feedback according to an embodiment of the present invention. [Figure 7F] 7A to 7F are schematic diagrams of slots for HARQ-ACK feedback according to an embodiment of the present invention. [Figure 8] FIG. 2 is another schematic diagram of a data transmission method according to an embodiment of the present invention; [Figure 9] 1 is a schematic diagram of a data receiving device according to an embodiment of the present invention; [Figure 10] FIG. 2 is another schematic diagram of a data transmission device according to an embodiment of the present invention. [Figure 11] FIG. 2 is a schematic diagram of a network device according to an embodiment of the present invention. [Figure 12] FIG. 2 is a schematic diagram of a terminal device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be adopted are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims. Each embodiment of the present invention will be described below with reference to the drawings. These embodiments are merely illustrative and do not limit the present invention.

[0014] In embodiments of the present invention, the terms "first", "second", etc. are used in the title to distinguish different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "including", "comprising", "having", etc. refer to the presence of listed features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0015] In the embodiments of the present invention, the singular forms "a", "the", etc., include the plural forms and should be understood broadly as "one kind" or "a class", and are not limited to "one". In addition, the term "said" should be understood to include both the singular and the plural forms, unless the context clearly indicates otherwise. In addition, the term "described in" should be understood to mean "described at least in part", and the term "based on" should be understood to mean "based at least in part on", unless the context clearly indicates otherwise.

[0016] In an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as, for example, Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0017] Additionally, communications between devices in a communication system may occur according to any stage of communication protocols, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G, New Radio (NR), and / or other currently known or future developed communication protocols.

[0018] In the embodiment of the present invention, the term "network device" refers to a device in a communication system, for example, allowing a terminal device to access the communication system and providing a service to the terminal device. The network device may include, but is not limited to, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0019] Among them, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), etc., as well as a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay, or a low power node (e.g., femto, pico, etc.). Also, the term "base station" may include some or all of the functions thereof, and each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and / or its coverage area depending on the context in which the term is used.

[0020] In the embodiment of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to an apparatus that accesses a communication network and receives a network service via, for example, a network device. The terminal apparatus may be fixed or mobile, and may be called a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.

[0021] Among them, the terminal device may include, but is not limited to, a mobile phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a smartphone, a smart watch, a digital camera, and the like.

[0022] For example, in a scenario such as the Internet of Things (IoT), the user equipment may be a monitoring or measuring device or equipment, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0023] Furthermore, the term "network side" or "network device side" refers to the side of a network, which may be a base station or may include one or more of the network devices mentioned above. The term "user side" or "terminal side" or "terminal device side" refers to the side of a user or terminal, which may be a UE or may include one or more of the terminal devices mentioned above. In this specification, unless otherwise specified, "device" may refer to a network device or may refer to a terminal device.

[0024] Furthermore, the term "network side" or "network device side" refers to the side of a network, which may be a base station or a core network device, or may include one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the side of a user or terminal, which may be one UE, or may include one or more terminal devices as described above. In this specification, unless otherwise specified, "device" may refer to a network device or may refer to a terminal device.

[0025] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" may be interchanged unless confusion arises. Also, the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" may be interchanged. The terms "downlink control signal" and "downlink control information (DCI)" or "Physical Downlink Control Channel (PDCCH)" may be interchanged. The terms "down data signal" and "downlink data information" or "Physical Downlink Shared Channel (PDSCH)" may be interchanged.

[0026] Moreover, the transmission or reception of a PUSCH may mean the transmission or reception of uplink data carried by the PUSCH, the transmission or reception of a PUCCH may mean the transmission or reception of uplink information carried by the PUCCH (e.g., UCI), the transmission or reception of a PRACH may mean the transmission or reception of a preamble carried by the PRACH, the transmission or reception of a PDSCH may mean the transmission or reception of downlink data carried by the PDSCH, and the transmission or reception of a PUCCH may mean the transmission or reception of downlink information carried by the PUCCH (e.g., DCI).

[0027] In the embodiment of the present invention, the higher layer signaling may be, for example, Radio Resource Control (RRC) signaling. For example, it may be referred to as an RRC message, and may include, for example, a Master Information Block (MIB), system information, and a dedicated RRC message. Alternatively, it may be referred to as an RRC information element (RRC IE). The higher layer signaling may be, for example, a Medium Access Control (MAC) signaling. Alternatively, it may be referred to as a MAC control element (MAC CE). However, the present invention is not limited thereto.

[0028] The following describes an embodiment scenario of the present invention with reference to an example, but the present invention is not limited thereto.

[0029] 1 is a schematic diagram of a communication system according to an embodiment of the present invention, and illustrates an example of a user device and a network device. As shown in FIG. 1, a communication system 100 may include a network device 101 and terminal devices 102 and 103. For convenience of explanation, FIG. 1 illustrates two terminal devices and one network device as an example, but the embodiment of the present invention is not limited thereto.

[0030] In an embodiment of the present invention, existing services or future services can be performed between the network device 101 and the terminal devices 102, 103. For example, these services include, but are not limited to, enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC) and related communications for terminal devices with reduced capabilities.

[0031] 1 shows that both of the two terminal devices 102 and 103 are located within the coverage area of ​​the network device 101, but the present invention is not limited to this. Both of the two terminal devices 102 and 103 may not be located within the coverage area of ​​the network device 101, or one of the terminal devices 102 may be located within the coverage area of ​​the network device 101 and the other terminal device 103 may be located outside the coverage area of ​​the network device 101.

[0032] In the embodiment of the present invention, the transport blocks (e.g., one or two transport blocks) carried by different PDSCHs are different, so in the following, "multiple PDSCHs" or "at least two PDSCHs" refers to different PDSCHs carrying different transport blocks. More specifically, the transport blocks carried by different PDSCHs correspond to different HARQ processes, where different HARQ processes have different HARQ process identifiers.

[0033] In the conventional scheme, one DCI can only schedule one PDSCH, but cannot schedule multiple PDSCHs. On the other hand, the embodiment of the present invention can schedule multiple PDSCHs by one DCI, where each PDSCH carries a different transport block (non-overlapping), which can reduce the burden of DCI monitoring on the terminal device, and reduce power consumption and complexity.

[0034] Each embodiment will be described below.

[0035] <Example 1> The embodiment of the present invention provides a data receiving method, which is described from the terminal device side.

[0036] 2 is a schematic diagram of a data receiving method according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps:

[0037] Step 201: A terminal device receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), the DCI including a first information field for indicating at least two (M) first PDSCH time domain resources.

[0038] Step 202: The terminal device receives at least one (N) second PDSCH.

[0039] In some aspects, the DCI format of the DCI for scheduling the PDSCH may be DCI format 1_0, DCI format 1_1, DCI format 1_2, or a new DCI format that has been additionally introduced, and embodiments of the present invention are not limited thereto.

[0040] In some aspects, the DCI for scheduling the PDSCH may be scrambled by a Cell-Radio Network Temporary Identifier (C-RNTI), a Modulation and Coding Scheme C-RNTI (MCS-C-RNTI), a Configuration Scheduling RNTI (CS-RNTI), a Temporary C-RNTI (TC-RNTI), a System Information RNTI (SI-RNTI), a Random Access RNTI (RA-RNTI), an MsgB-RNTI, a Paging RNTI (P-RNTI), or a new RNTI additionally introduced, and the embodiments of the present invention are not limited thereto.

[0041] In some aspects, the first PDSCH is a PDSCH indicated by the DCI, and may also be referred to as an indicated PDSCH or a nominal PDSCH. The time domain resources of at least two (M) first PDSCHs (hereinafter abbreviated as M first PDSCHs, where M is 2 or more) are contiguous or non-contiguous, the number of time domain symbols of different first PDSCHs is the same or different, and the time domain resource of each first PDSCH is in one slot or not in one slot, but the embodiment of the present invention is not limited thereto.

[0042] In some aspects, the network device side may configure a time domain relationship list (also referred to as a PDSCH time domain resource allocation list) between the PDSCH and the PDCCH through higher layer signaling. For example, the network device transmits an RRC message including first configuration information, the first configuration information including at least one first information element, where one first information element is used to configure the time domain relationship between the PDSCH and the PDCCH, for example, the first configuration information is PDSCH-TimeDomainResourceAllocationList, the first information element is PDSCH-TimeDomainResourceAllocation, and the first configuration information is included in, for example, pdsch-ConfigCommon or pdsch-Config.

[0043] In some aspects, the DCI includes a first information field for indicating at least two (M) time domain resources of the first PDSCH, the first information field being, for example, a time domain resource assignment field, and the first information field includes a fifth number (E) of bits, the fifth number may be configured or predefined, and embodiments of the present invention are not limited thereto. A decimal value corresponding to the fifth number of bits is a value of the first information field, and the value of the first information field is used to indicate which first information element in the first information field the DCI indicates. For example, the value of the first information field is 0 and is used to indicate the first first information element in the first information field, the value of the first information field is 1 and is used to indicate the second first information element in the first information field, and other cases are similar, and examples are omitted here.

[0044] In the following, the method of determining the indicated at least two (M) first PDSCHs based on the first information field and the first configuration information is further described.

[0045] In some aspects, when the above first information field is used to indicate time domain resources of at least two (M) first PDSCHs, the value of the first information field corresponds to one first information element, which is used to configure a time domain relationship between the M first PDSCHs and a PDCCH for carrying DCI.

[0046] In some aspects, the first information element may include a fourth number (D) of information (e.g., nrOfSlots), where the fourth number represents the number of slots corresponding to the first information element, where the value of the first information field corresponds to one first information element, where the one first information element is used to configure a time-domain relationship between the M first PDSCHs and a PDCCH for carrying DCI, and where the fourth number D included in the first information element is M.

[0047] In the above aspect, the first information element includes information (e.g., k0) for configuring a slot offset (K0) between the PDSCH and the PDCCH. For example, k0 indicates a slot offset between a start time domain position of the D first PDSCHs and the PDCCH, i.e., a slot offset between a first PDSCH of the D first PDSCHs and the PDCCH. For example, assuming that a PDCCH used to carry the above-mentioned DCI is transmitted in slot n, a start time domain position of the D first PDSCHs is transmitted in slot n+K0, i.e., a first PDSCH of the D first PDSCHs is transmitted in slot n+K0. In addition, the first information element may further include information for configuring a PDSCH mapping type (e.g., mappingType) and / or information for configuring a time domain resource of the PDSCH (i.e., including a symbol of the PDSCH, e.g., a start symbol and length (SLIV) of the PDSCH) (e.g., startSymbolAndLength), and the same PDSCH mapping type and start symbol and length may be applied to determine the D first PDSCH time domain resources.

[0048] For example, this first configuration information may be represented using the abstract syntax ASN.1 data format as follows: PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { k0 INTEGER(0..32) mappingType ENUMERATED {typeA, typeB} startSymbolAndLength INTEGER (0..127) nrOfSlots INTEGER(1..8) In some aspects, the first information element may include information (e.g., nrOfPDSCHs) for configuring a first number (A) representing the number of first PDSCHs corresponding to the first information element. When the first information field is used to indicate time domain resources of at least two (M) first PDSCHs, the value of the first information field corresponds to one first information element, which is used to configure a time domain relationship between the M first PDSCHs and a PDCCH for carrying DCI, and the first number A included in the one first information element is M.

[0049] In the above aspect, the first information element includes information (e.g., k0) for configuring a slot offset (K0) between the PDSCH and the PDCCH. For example, k0 indicates a slot offset between a start time domain position of the A first PDSCHs and the PDCCH, i.e., a slot offset between the first PDSCH of the A first PDSCHs and the PDCCH. For example, assuming that the PDCCH for carrying the above DCI is transmitted in slot n, the start time domain position of the A first PDSCHs is transmitted in slot n+K0, i.e., the first PDSCH of the A first PDSCHs is transmitted in slot n+K0. In addition, the first information element may include information (e.g., mappingType) for configuring a PDSCH mapping type and / or information (e.g., startSymbolAndLength) for configuring a time domain resource of the PDSCH (i.e., a symbol of the PDSCH, e.g., a start symbol and length (SLIV) of the PDSCH are included). For example, the first configuration information may be expressed in an ASN.1 data format using an abstract syntax as follows: PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { k0 INTEGER(0..32) mappingType ENUMERATED {typeA, type B} startSymbolAndLength INTEGER (0..127) nrOfPDSCHs INTEGER(1..8) Here, SEQUENCE represents an ordered set of corresponding information, SIZE represents the number of elements in the corresponding SEQUENCE set, and INTEGER() and ENUMERATED() represent the value type and value range of the corresponding information. For specific details, you may refer to the ASN.1 grammar, and the explanation of this will be omitted here.

[0050] In the above aspect, the same PDSCH mapping type, starting symbol and length may be applied to determine the A first PDSCH time domain resources. Alternatively, the PDSCH mapping type, starting symbol and length are applied to determine the first first PDSCH time domain resource among the above-mentioned A first PDSCHs, and the remaining (A-1) first PDSCH time domain resources have the same length as the first first PDSCH time domain resource and are sequentially mapped to consecutive symbols.

[0051] 3A to 3C are schematic diagrams of time domain positions of M (M=4 in the figures) first PDSCHs. As shown in FIG. 3A, the M first PDSCHs apply the same PDSCH mapping type, start symbol and length configuration, for example, have the same time domain length, and are continuous in the time domain. Also, the time domain resource of one first PDSCH is in one slot. As shown in FIG. 3B, the M first PDSCHs apply the same PDSCH mapping type, start symbol and length configuration, for example, have the same time domain length, are discontinuous in the time domain, and the time domain resource of another first PDSCH is in one slot. As shown in FIG. 3C, the first one of the M first PDSCHs applies a PDSCH mapping type and a starting symbol and length configuration, and the remaining first PDSCHs have the same time domain length as the first first PDSCH and are sequentially mapped to consecutive symbols, that is, the time domain lengths of the M first PDSCHs are the same and are consecutive in the time domain, but one first PDSCH is in one slot or not in one slot.

[0052] In some aspects, the first information element may include at least one second information element (e.g., PDSCH-Allocation or startSymbolAndLength) for configuring time domain resources of the PDSCH (i.e., symbols of the PDSCH, e.g., start symbol and length (SLIV) of the PDSCH). The number of second information elements included in each first information element may be the same or different. In other words, the first information element may include at most a first predefined value (e.g., maxNrofMultiplePDSCHs) of second information elements, where the first predefined value is predefined and is greater than 1. The second information element is used to configure the time domain resources of one PDSCH. The value of the first information field corresponds to one first information element. The first information element is used to configure a time domain relationship between the M first PDSCHs and a PDCCH for carrying DCI, i.e., the first information element includes at least two (M) second information elements, and each second information element is used to configure a time domain resource of one first PDSCH, respectively.

[0053] In the above aspect, the second information element includes a PDSCH mapping type (mappingType) and a start symbol and length (startSymbolAndLength) configuration. That is, the time domain resource of each first PDSCH is determined by applying the respective PDSCH mapping type and start symbol and length configuration (in the corresponding second information element). For example, the first configuration information may be expressed in the following data format using the abstract syntax ASN.1: PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { k0 INTEGER(0..32) pdschAllocationList SEQUENCE (SIZE(1..maxNrofMultiplePDSCHs)) OF PDSCH-Allocation, ... } PDSCH-Allocation ::= SEQUENCE { mappingType ENUMERATED {typeA, typeB} startSymbolAndLength INTEGER (0..127) ... } Alternatively, the second information element includes a start symbol and length configuration (startSymbolAndLength), and the first information element includes a PDSCH mapping type configuration (mappingType). That is, the time domain resource of each first PDSCH applies the start symbol and length configuration (in the corresponding second information element) but is determined by applying the same PDSCH mapping type configuration. For example, the first configuration information may be expressed in the following data format using the abstract syntax ASN.1: PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { k0 INTEGER(0..32) mappingType ENUMERATED {typeA, type B} pdschAllocationList SEQUENCE (SIZE(1..maxNrofMultiplePDSCHs)) OF PDSCH-Allocation, ... } PDSCH-Allocation ::= SEQUENCE { startSymbolAndLength INTEGER (0..127) ... }of 4A-4B are schematic diagrams of time domain locations of M first PDSCHs. As shown in FIG. 4A, M first PDSCH time domain resources are determined by applying respective PDSCH mapping type configurations and starting symbol and length configurations. For example, the time domain lengths may be the same or different, may be contiguous or discontinuous in the time domain, and the other first PDSCH time domain resources are in one slot. As shown in FIG. 4B, M first PDSCH time domain resources apply the same PDSCH mapping type configuration but respective starting symbol and length configurations. For example, the time domain lengths may be the same or different, may be contiguous in the time domain, and the other first PDSCH time domain resources are in one slot.

[0054] In some aspects, the network device may configure slot offset values ​​(K0) between the multiple PDSCHs and the PDCCH through higher layer signaling, i.e., the M first PDSCH time domain resources may apply their respective (K0) information to determine the slots in which they are located. For example, the information of the slot offset (K0) between the PDSCH and the PDCCH may be included in the second information element, and the M first PDSCH time domain resources may apply their respective (K0) information to determine the slots in which they are located, but the description thereof will be omitted here.

[0055] The above describes an example in which a time domain relationship list (PDSCH time domain resource allocation list) between PDSCH and PDCCH is configured on the network device side by higher layer signaling, but the embodiment of the present invention is not limited to this. For example, time domain resources of multiple PDSCHs may be configured via a predefined time domain relationship list between PDSCH and PDCCH. The configuration of one line is similar to the configuration of one first information element described above, and the description thereof will be omitted here.

[0056] The following further describes how to determine at least one (N) second PDSCH.

[0057] In some aspects, the second PDSCHs are actual scheduled PDSCHs (e.g. scheduled PDSCHs, actual PDSCHs), and the first PDSCHs are actual PDSCHs, where N=M, and both N and M are equal to or greater than 2; in other words, the M first PDSCHs indicated by the DCI are actual scheduled N second PDSCHs.

[0058] In some aspects, the terminal device may determine at least one (N) second PDSCH based on at least one of a semi-statically configured transmission direction (i.e., information for semi-statically configuring the transmission direction), a configured PRACH resource, information for dynamically scheduling uplink transmission or dynamically configuring the transmission direction, a configured invalid symbol, or whether it is a cross slot. Each of these is described below.

[0059] In some aspects, the semi-static configuration is that the base station is configured by higher layer signaling at the cell level / user-dedicated level. The information for semi-statically configuring the transmission direction is, for example, tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the transmission direction of one time unit (e.g., symbol, slot, subframe) may be semi-statically configured as uplink, downlink, or flexible. Here, the time unit that is not explicitly configured as uplink or downlink is the time unit configured as flexible. When determining the N second PDSCHs based on the semi-statically configured transmission direction, if at least one symbol of the first PDSCH is semi-statically configured as uplink (i.e., a PDSCH that cannot receive downlink), the first PDSCH is not taken as the second PDSCH. In other words, the terminal device does not receive the first PDSCH. For example, if at least one symbol of the first PDSCH indicated by the above DCI in one slot of a plurality of slots (assuming that there is one first PDSCH in one slot) is semi-statically configured as an uplink, the terminal device does not receive the first PDSCH in the slot. Figure 5A is a schematic diagram of at least one second PDSCH. As shown in Figure 5A, it is assumed that one symbol in the first PDSCH in the second slot in the figure is semi-statically configured as an uplink, and other symbols in the figure are not configured as an uplink, and the first PDSCH does not function as a second PDSCH.

[0060] Alternatively, when at least one symbol of the first PDSCH is semi-statically configured as an uplink, the second PDSCH corresponds to the first PDSCH one-to-one (M=N), and the slot in which the second PDSCH is located is the same as or different from the slot in which the corresponding first PDSCH is located. For example, one first PDSCH includes an uplink symbol that is semi-statically arranged, and the one first PDSCH and the subsequent first PDSCH are postponed to the time domain position in which the nearest first PDSCH is located in the time domain that is not semi-statically configured as an uplink symbol in the time domain, and the first PDSCH that is not postponed and the postponed first PDSCH are at least one (N) second PDSCH. Figure 5B is a schematic diagram of at least one second PDSCH. As shown in FIG. 5B, a certain symbol of the first PDSCH in the second slot in the figure is semi-statically configured as an uplink, and other symbols in the figure are not semi-statically configured as uplinks, and the starting position of the first PDSCH is postponed to the starting position of the first PDSCH in the next slot, and the PDSCHs after the first PDSCH are sequentially postponed in a similar manner, and the first PDSCH in the first slot and the first PDSCH after adjusting the time domain position are at least one second PDSCH.

[0061] Alternatively, if at least one symbol of the first PDSCH is semi-statically configured as an uplink, the first PDSCH is divided into at least two (O) third PDSCHs that do not include the at least one uplink symbol, and the divided at least two third PDSCHs and the first PDSCH that does not include an uplink symbol are at least one (N) second PDSCH, that is, N=M-1+O. Figure 5C is a schematic diagram of at least one second PDSCH. As shown in Figure 5C, a symbol of the first PDSCH in the second slot in the figure is semi-statically configured as an uplink, and the other symbol in the figure is not configured as an uplink, and the first PDSCH is divided into two third PDSCHs that do not include an uplink symbol, and the undivided first PDSCH and the two third PDSCHs are at least one second PDSCH.

[0062] In some aspects, when determining the N second PDSCHs based on the configured PRACH resources, if a PRACH is configured for at least one symbol of the first PDSCH and / or the at least one symbol of the first PDSCH is a symbol among a third number (e.g., the third number is predefined, for example) of symbols (e.g., referred to as interval symbols) before the configured PRACH, the first PDSCH does not function as a second PDSCH. FIG. 5D is a schematic diagram of the at least one second PDSCH. As shown in FIG. 5D, if a PRACH is configured for at least one symbol of the first PDSCH in the second slot in the figure and the at least one symbol of the first PDSCH is a symbol among a third number (e.g., the number is predefined, for example) of symbols (e.g., referred to as interval symbols) before the configured PRACH, the first PDSCH does not function as a second PDSCH, in other words, the terminal device does not receive the first PDSCH.

[0063] In some aspects, the transmission direction may be configured as uplink, downlink, or flexible by information for dynamically configuring the transmission direction. Here, a time unit that is not explicitly configured as uplink or downlink by the information is a flexibly configured time unit. When determining N second PDSCHs based on information for dynamically scheduling uplink transmission or information for dynamically configuring the transmission direction, when at least one symbol in the first PDSCH is dynamically scheduled for uplink transmission by the information or the transmission direction is dynamically configured as uplink by the information, the first PDSCH is not the second PDSCH, in other words, the terminal device does not receive the first PDSCH. Alternatively, the second PDSCH has a one-to-one correspondence with the first PDSCH, and the slot in which the second PDSCH is located is the same as or different from the slot in which the first PDSCH is located. Alternatively, the first PDSCH is divided into at least two third PDSCHs not including the at least one uplink symbol, and the at least two divided third PDSCHs and the first PDSCH not including the uplink symbol are set as at least one (N) second PDSCH. For each of the above-mentioned aspects and the above-mentioned semi-static configuration aspect, for example, refer to Figures 5A to 5C, and description thereof will be omitted here.

[0064] In the above aspect, information for dynamically scheduling uplink transmissions (e.g., DCI of DCI format 0_0 or DCI format 0_1 ​​or DCI format 0_2) or information for dynamically configuring a transmission direction (e.g., DCI of DCI format 2_0) is transmitted before the DCI, otherwise the UE does not determine a second PDSCH based on the information or does not take the information into account when determining at least one second PDSCH.

[0065] Alternatively, in the above aspect, information for dynamically scheduling uplink transmission (e.g., DCI of DCI format 0_0 or DCI format 0_1 ​​or DCI format 0_2) or information for dynamically configuring a transmission direction (e.g., DCI of DCI format 2_0) is transmitted a certain time period (the certain time period is, for example, predefined) before the DCI, and otherwise the UE does not determine a second PDSCH based on this information or does not take this information into account when determining at least one second PDSCH.

[0066] In some aspects, if the time domain resource of the first PDSCH spans slots (i.e., occupies two adjacent slots), the first PDSCH does not function as the second PDSCH. In other words, the terminal device does not receive the first PDSCH. Alternatively, the first PDSCH that spans slots is divided into at least two third PDSCHs that do not span slots (i.e., are in one slot), and the at least two divided third PDSCHs and the first PDSCH that does not span slots are at least one (N) second PDSCH. Figures 5E and 5F are schematic diagrams of at least one second PDSCH. As shown in Figure 5E, the first PDSCH in the third slot and the fourth slot spans slots, and the first PDSCH in the third slot and the fourth slot does not function as a second PDSCH, and as shown in Figure 5F, the first PDSCH in the third slot and the fourth slot spans slots, and the PDSCH in the third slot is split into two third PDSCHs that do not span slots, and neither of the two split third PDSCHs spans slots.

[0067] In some aspects, when determining at least one second PDSCH based on the configured invalid symbol, when at least one symbol of the first PDSCH is configured to be invalid (i.e., the PDSCH cannot receive downlink), the first PDSCH does not function as the second PDSCH, or the second PDSCH corresponds to the first PDSCH one-to-one (M=N), and the slot in which the second PDSCH is located is the same as or different from the slot in which the first PDSCH is located. Alternatively, the first PDSCH is divided into at least two (O) third PDSCHs not including at least one invalid symbol, and the divided at least two third PDSCHs and the first PDSCH not including the invalid symbol are set as at least one (N) second PDSCH, i.e., N=M-1+O. For each of the above aspects and the above semi-static configuration aspect, for example, reference can be made to FIG. 5A to FIG. 5C, and description thereof will be omitted here.

[0068] In some aspects, the terminal device may determine the invalid symbol based on at least one of the semi-statically configured transmission direction (i.e., information for semi-statically configuring the transmission direction), the configured PRACH resource, the information for dynamically scheduling the uplink transmission or dynamically configuring the transmission direction, and the configured invalid symbol. For example, the semi-statically configured uplink symbol may be determined to be an invalid symbol, and / or the PRACH resource configured symbol may be determined to be an invalid symbol, and / or the symbol of a third number of symbols (e.g., referred to as interval symbols) before the PRACH is configured (e.g., the third number is predefined, for example) before the PRACH is configured may be determined to be an invalid symbol, and / or the information used to dynamically schedule the uplink transmission may determine the symbol for which the uplink transmission is dynamically scheduled to be an invalid symbol, and / or the information used to dynamically configure the transmission direction may determine the symbol for which the uplink transmission is dynamically scheduled to be an invalid symbol, and / or the invalidly configured symbol may be determined to be an invalid symbol. If the first PDSCH includes the determined invalid symbol, the first PDSCH does not function as the second PDSCH, or the second PDSCH corresponds to the first PDSCH one-to-one (M=N), and the time slot in which the second PDSCH exists is the same as or different from the time slot in which the first PDSCH exists, or the first PDSCH is divided into at least two (O) third PDSCHs that do not include at least one invalid symbol, and the divided at least two third PDSCHs and the first PDSCH that does not include an invalid symbol function as at least one (N) second PDSCH. Specific aspects are the same as those described above, and their description will be omitted here.

[0069] The above elements for determining at least one (N) second PDSCH or determining invalid symbols may be implemented alone or in combination, and embodiments of the present invention are not limited thereto.

[0070] In some aspects, the value of N does not exceed the maximum number of the number of first PDSCHs corresponding to each of the above first information elements, or the value of N does not exceed M. FIG. 5G is a schematic diagram of at least one second PDSCH. Assuming that the value of N does not exceed M, as shown in FIG. 5G, when the value of M is 4, the number N of the second PDSCHs is at most 4. Although described here as an example, the embodiment of the present invention is not limited thereto.

[0071] The following further describes other information fields that may be included in this DCI.

[0072] In some aspects, the DCI further includes a second information field indicating the RV and / or a third information field indicating the NDI. The second information field may be a redundancy version field, and the third information field may be a new data indicator field. The size of the second information field and / or the third information field is related to the second number, and the second number is the maximum number of the first PDSCHs corresponding to all the first information elements, such as the maximum number of the second information elements included in all the first information elements in the first configuration information, or the maximum number of the first numbers included in all the first information elements in the first configuration information. For example, the bits of the second information field and / or the third information field correspond to the first PDSCH. For example, the LSB of the third information field corresponds to the first first PDSCH, and the 2nd LSB corresponds to the second first PDSCH (if this DCI indicates the second first PDSCH). Also, for example, the bits of the second information field and / or the third information field correspond to the second PDSCH. For example, the LSB of the third information field corresponds to the first second PDSCH, and the 2nd LSB corresponds to the second second PDSCH (when this DCI actually schedules the second second PDSCH), and so on.

[0073] In some aspects, the DCI further includes a fourth information field, which may be a HARQ process number field. The fourth information field is used to indicate a Hybrid Automatic Repeat Request (HARQ) process ID. The HARQ process ID is a HARQ process ID of one of the at least two (M) first PDSCHs, or a HARQ process ID of one of the at least one (N) second PDSCHs. The following describes each of them.

[0074] In some aspects, the HARQ process identifier is a HARQ process identifier of one of the at least one (N) second PDSCHs, and the terminal device employs a predefined method to determine the HARQ process identifiers of the other (N-1) second PDSCHs.

[0075] In the above aspect, one second PDSCH may be the first of N second PDSCHs. According to the scheduling order of at least one second PDSCH, the HARQ process identifier is incremented or added by 1, and then a modulo is calculated to determine the HARQ process identifiers of the remaining (N-1) second PDSCHs. For example, the HARQ process identifier indicated by the fourth information field is X (X is a value from 0 to Y), where X is the HARQ process identifier of the first second PDSCH of the at least one (N) second PDSCH, and the HARQ process identifier of the nth (n is greater than 1) second PDSCH is mod(X+n-1, (outside 1) TIFF0007597213000001.tif18153), (outside 2) TIFF0007597213000002.tif19153 is the number of HARQ processes of the corresponding serving cell, which is predefined or configured by the base station via higher layer signaling.

[0076] In the above aspect, the method may preferably further include a step (not shown) in which the physical layer of the terminal device reports HARQ information of at least one (N) second PDSCH to an upper layer. The HARQ information includes a HARQ process identifier of at least one (N) second PDSCH, and may further include an NDI, an RV, or a transmission block size (TBS).

[0077] Figure 6A is a schematic diagram of the HARQ process identifier of at least one (N) second PDSCH. As shown in Figure 6A, the HARQ process identifier indicated by the fourth information field is 0, that is, the HARQ process identifier of the first second PDSCH (first slot) is 0, the HARQ process identifier of the second second PDSCH (third slot) is 1, and the HARQ process identifier of the third second PDSCH (fourth slot) is 2. The physical layer of the terminal device reports the HARQ information of the above three second PDSCHs to the upper layer, and the HARQ information includes the HARQ processes 0, 1, and 2 of the above three second PDSCHs.

[0078] In some aspects, the HARQ process identifier is a HARQ process identifier of one of the at least two (M) first PDSCHs, and the terminal device determines the HARQ process identifiers of the other (M-1) first PDSCHs using a predefined method.

[0079] In the above aspect, the one first PDSCH may be one of the first of M first PDSCHs. According to the order of the at least two (M) first PDSCHs, the HARQ process identifier is incremented or added by 1, and then a modulo is obtained to determine the HARQ process identifiers of the remaining (M-1) first PDSCHs. For example, the HARQ process identifier indicated by the fourth information field is X (X is a value from 0 to Y), where X is the HARQ process identifier of the first first PDSCH of the at least two (M) first PDSCHs, and the HARQ process identifier of the nth (n is greater than 1) first PDSCH is mod(X+n-1, Y), where Y is the number of HARQ processes.

[0080] In the above aspect, the method may further include a step (not shown, optional) in which the physical layer of the terminal device reports HARQ information of at least two (M) first PDSCHs to an upper layer. The HARQ information includes HARQ process identification information of the first PDSCH, and may further include NDI, RV, or transmission block size (TBS).

[0081] In the above aspect, the method may further include a step (not shown, optional) in which the physical layer of the terminal device reports invalid HARQ process identifiers among the at least two (M) HARQ process identifiers of the first PDSCH to a higher layer. The invalid HARQ process identifiers are HARQ process identifiers with no corresponding data. The terminal device may ignore information bits of NDI and / or information bits of RV indicating the first PDSCH in the second information field and / or the third information field in the DCI.

[0082] In the above aspect, the method may further include a step (not shown, optional) in which the physical layer of the terminal device does not report HARQ information of the first PDSCH that is not the second PDSCH of the at least two first PDSCHs to the upper layer. In other words, the physical layer of the terminal device may report HARQ information of the first PDSCH of the second PDSCH (actual scheduled PDSCH) to the upper layer.

[0083] Figure 6B is a schematic diagram of the HARQ process identifiers of at least two first PDSCHs. As shown in Figure 6B, the HARQ process identifier indicated by the fourth information field is 0, that is, the HARQ process identifier of the first first PDSCH (first slot) is 0, the HARQ process identifier of the second first PDSCH (second slot) is 1, the HARQ process identifier of the third first PDSCH (third slot) is 2, and the HARQ process identifier of the fourth first PDSCH (fourth slot) is 3. The physical layer of the terminal device reports the HARQ information of the above four first PDSCHs to the upper layer, and the HARQ information includes at least the HARQ processes 0, 1, 2, and 3 of the above four first PDSCHs. Alternatively, when the second first PDSCH is not actually scheduled (i.e., when the second first PDSCH is not the second PDSCH), the physical layer of the terminal device reports HARQ information of the first, third and fourth first PDSCHs to the upper layer, where the HARQ information includes HARQ processes 0, 2 and 3 of at least the above three first PDSCHs.

[0084] In some aspects, the DCI may further include a fifth information field. The fifth information field may be a HARQ-ACK timing indicator (ie, PDSCH-to-HARQ_feedback timing indicator) field for indicating feedback timing k of HARQ-ACK information. Alternatively, the DCI may not include the fifth information field. The terminal device receives second configuration information (e.g., dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 for DCI format 1_2) configured by higher layer signaling, and the second configuration information indicates feedback timing k of HARQ-ACK information.

[0085] In some aspects, the method may further include the terminal device feeding back HARQ acknowledgement (HARQ-ACK) information (optional, not shown). For example, the terminal device transmits the HARQ-ACK information in a slot with index n+k (slot n+k), where the slot with index n (slot n) is an end slot of the at least two (M) first PDSCHs or an end slot of a last first PDSCH of the at least two (M) first PDSCHs, or the slot with index n (slot n) is an end slot of the at least one (N) second PDSCH or an end slot of a last second PDSCH of the at least one (N) second PDSCH, where n and k are integers greater than 0, as described in detail below.

[0086] In some aspects, when the terminal device transmits HARQ-ACK information using a semi-static HARQ-ACK codebook (i.e., Type-1 HARQ-ACK codebook), the slot of index n (slot n) is the end slot of at least two (M) first PDSCHs or the end slot of the last first PDSCH of the at least two (M) first PDSCHs (the uplink slot index corresponding to the downlink end slot n' of the PDSCH is n), and k is the offset between the feedback slot of the HARQ-ACK information and slot n. Here, the method of generating the semi-static codebook can refer to the prior art, and the description thereof will be omitted here. For example, the codebook may be a Type-2 HARQ-ACK codebook or a Type-3 HARQ-ACK codebook. FIG. 7A is a schematic diagram of a HARQ-ACK feedback slot. As shown in FIG. 7A, slot n (uplink slot) is the end slot of the last first PDSCH (i.e., the uplink slot corresponding to the downlink end slot of the last first PDSCH), and the feedback slot of the HARQ-ACK information is n+k.

[0087] In some aspects, when the terminal device transmits HARQ-ACK information using a dynamic HARQ-ACK codebook (i.e., Type-2 HARQ-ACK codebook), the slot of index n (slot n) is the end slot of at least one (N) second PDSCH or the end slot of the last second PDSCH of the at least one (N) second PDSCH (the uplink slot index corresponding to the downlink end slot n' of the PDSCH is n), and k is the offset between the feedback slot of the HARQ-ACK information and slot n. Here, the method of generating the dynamic codebook can refer to the prior art, and the description thereof will be omitted here. For example, the codebook may be a Type-1 HARQ-ACK codebook or a Type-3 HARQ-ACK codebook. FIG. 7B is a schematic diagram of a HARQ-ACK feedback slot. As shown in FIG. 7B, slot n (uplink slot) is the end slot of the last second PDSCH (i.e., the uplink slot corresponding to the downlink end slot of the last second PDSCH), and the feedback slot of the HARQ-ACK information is n+k.

[0088] In the above embodiment, the feedback timing of HARQ-ACK information is described, but in the embodiment of the present invention, since the generation of HARQ-ACK information requires a certain processing time, even if the feedback timing of HARQ-ACK information is reached, HARQ-ACK information may not be generated. The following will further describe the feedback content of this HARQ-ACK information, in other words, it may further determine which PDSCH's HARQ-ACK information is included in this HARQ-ACK information based on the above processing time.

[0089] In some aspects, the terminal device transmits HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of at least one (N) second PDSCH. An interval between a last symbol of the last second PDSCH of the at least one (N) second PDSCH or a last symbol of the at least one (N) second PDSCH and a first symbol of the physical uplink channel is equal to or greater than a first time. If an interval between a last symbol of the last second PDSCH of the at least one (N) second PDSCH or a last symbol of the at least one (N) second PDSCH and a first symbol of the physical uplink channel is shorter than the first time, the terminal device does not feed back the HARQ-ACK information of the at least one (N) second PDSCH. That is, when the terminal device feeds back HARQ-ACK information of at least one (N) second PDSCH, the first symbol (uplink symbol) of the physical uplink channel should not start before symbol L1. L1 represents the uplink symbol corresponding to the first time after the last symbol of at least one (N) second PDSCH. FIG. 7C is a schematic diagram of the HARQ-ACK of feedback. As shown in FIG. 7C, the interval between the last symbol of the last second PDSCH and the first symbol of the physical uplink channel is a first time (e.g. T proc,1 For example, the first time may be predefined, preconfigured, or calculated by a parameter, and the details may refer to the prior art, and the description thereof will be omitted here.

[0090] In some aspects, the terminal device transmits HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of at least one (P) fourth PDSCH. The at least one (P) fourth PDSCH is at least one (P) PDSCH of the at least one (N) second PDSCH. Here, an interval between a last symbol of the last second PDSCH of each fourth PDSCH and a first symbol of the physical uplink channel is equal to or greater than a first time. An interval between a last symbol of each other second PDSCH of the above N second PDSCHs except for the P fourth PDSCHs and a first symbol of the physical uplink channel is less than the first time, and the terminal device does not feed back HARQ-ACK information of each other second PDSCH. In other words, for one second PDSCH, if the interval between the last symbol of the one second PDSCH and the first symbol of the physical uplink channel is equal to or greater than the first time, the terminal device provides HARQ-ACK information of the one second PDSCH, otherwise, does not provide HARQ-ACK information of the one second PDSCH. The processing manner for each second PDSCH is similar, and the description thereof is omitted here. Figure 7D is a schematic diagram of HARQ-ACK feedback. As shown in Figure 7D, when the interval between the last symbol of the second second PDSCH and the first symbol of the physical uplink channel is smaller than the first time, the interval between the last symbol of the first second PDSCH and the first symbol of the physical uplink channel is larger than the first time, the terminal device feeds back the HARQ-ACK information of the first second PDSCH, and does not feed back the HARQ-ACK information of the second second PDSCH. For example, the first time is predefined, pre-set, or obtained by parameter calculation, and for specific details, reference can be made to the prior art, and the description thereof will be omitted here.

[0091] In some aspects, the terminal device transmits HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of at least one (N) second PDSCH. An interval between the last symbol of each second PDSCH among the at least one (N) second PDSCH and the first symbol of the physical uplink channel is equal to or greater than a first time. In other words, an interval between the first symbol of the physical uplink channel and the last symbol of any second PDSCH is equal to or greater than a first time, and the first times corresponding to different second PDSCHs may be the same or different. FIG. 7E is a schematic diagram of HARQ-ACK feedback. As shown in Figure 7E, the interval between the last symbol of each secondary PDSCH and the first symbol of the physical uplink channel is greater than the first time, and the terminal device feeds back HARQ-ACK information of the first and second secondary PDSCHs, but the first time corresponding to the first secondary PDSCH and the first time corresponding to the second secondary PDSCH have different lengths. The first time may be predefined, preconfigured, or calculated by a parameter.

[0092] In some aspects, the terminal device transmits HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of at least one (N) second PDSCH. An interval between a last symbol of the last first PDSCH of the at least two (M) first PDSCHs or a last symbol of the at least two (M) first PDSCHs and a first symbol of the physical uplink channel is equal to or greater than a first time. If an interval between a last symbol of the last first PDSCH of the at least two (M) first PDSCHs or a last symbol of the at least two (M) first PDSCHs and a first symbol of the physical uplink channel is smaller than the first time, the terminal device does not feed back HARQ-ACK information of the at least one (N) second PDSCH. That is, when the terminal device feeds back HARQ-ACK information of at least one (N) second PDSCH, the first symbol (uplink symbol) of the physical uplink channel should not start before symbol L1. Here, L1 represents an uplink symbol corresponding to a first time after the last symbol of at least two (M) first PDSCHs. FIG. 7F is a schematic diagram of HARQ feedback. As shown in FIG. 7F, the interval between the last symbol of the last first PDSCH and the first symbol of the physical uplink channel is equal to or greater than the first time. For example, the first time may be predefined, preconfigured, or calculated by a parameter. For details, the prior art may be referred to, and the description thereof will be omitted here.

[0093] In the above aspect, the physical uplink channel may be a physical uplink control channel or a physical uplink shared channel, and the embodiment of the present invention is not limited thereto; the first symbol (uplink symbol) position of the physical uplink channel may be determined according to conventional technology, and the embodiment of the present invention is not limited thereto.

[0094] It should be noted that the above FIG. 2 is merely a schematic illustration of an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between various steps may be appropriately adjusted, some other steps may be added, and some steps may be removed. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of the above FIG. 2.

[0095] The above embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, each of the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0096] According to this embodiment, since multiple PDSCHs can be scheduled by one DCI, the burden of DCI monitoring on the terminal device can be reduced, and power consumption and complexity can be reduced.

[0097] <Example 2> The embodiment of the present invention provides a data transmission method, and will be described from the perspective of a network device. Here, the description of the same contents as in the first embodiment will be omitted.

[0098] 8 is another schematic diagram of a data transmission method according to an embodiment of the present invention. As shown in FIG. 8, the method includes the following steps:

[0099] Step 801: A network device sends downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) to a terminal device. The DCI includes a first information field for indicating at least two (M) first PDSCH time domain resources.

[0100] Step 802: The network device transmits at least one (N) second PDSCH to the terminal device.

[0101] In some aspects, steps 801 and 802 correspond to steps 201 and 202 in the first embodiment, and a description of the overlapping contents will be omitted.

[0102] In some aspects, the contents of DCI, the meanings of the first PDSCH and the second PDSCH, how the DCI indicates the first PDSCH, how the second PDSCH is determined, etc. may refer to Example 1, and the description thereof will be omitted here.

[0103] According to this embodiment, since multiple PDSCHs can be scheduled by one DCI, the burden of DCI monitoring on the terminal device can be reduced, and power consumption and complexity can be reduced.

[0104] <Example 3> An embodiment of the present invention provides a data receiving device. The device may be, for example, a terminal device, or one or more elements or components configured in the terminal device. Descriptions of the same contents as those in the first embodiment will be omitted.

[0105] 9 is a schematic diagram of a data receiving device according to an embodiment of the present invention. As shown in FIG. 9, the data receiving device 900 includes the following units:

[0106] The first receiving unit 901 receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH). The DCI includes a first information field for indicating at least two (M) time domain resources of the first PDSCH.

[0107] The second receiving unit 902 receives at least one (N) second PDSCH.

[0108] In some aspects, the aspects of the first receiving unit 901 and the second receiving unit 902 can refer to steps 201 to 202 in the first embodiment, and will not be described repeatedly.

[0109] In some aspects, the DCI further includes a fourth information field for indicating a HARQ process identifier, where the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one of the at least one (N) second PDSCHs.

[0110] For example, one second PDSCH is a first one of at least one (N) second PDSCHs.

[0111] In this embodiment, the device further comprises the following parts:

[0112] A first determining unit (not shown, optional) determines a HARQ process identifier of at least one (N) second PDSCH based on the fourth information field.

[0113] A first reporting unit (not shown, optional) reports HARQ information of at least one (N) second PDSCH to a higher layer in the physical layer of the terminal device.

[0114] In some aspects, the DCI further includes a fourth information field for indicating a HARQ process identifier, where the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one of the at least two (M) first PDSCHs.

[0115] For example, one first PDSCH is a first of at least two (M) first PDSCHs.

[0116] In this embodiment, the device further includes the following parts:

[0117] A second determining unit (not shown, optional) determines HARQ process identifiers of the at least two (M) first PDSCHs based on the fourth information field.

[0118] A second reporting unit (not shown, optional) reports invalid HARQ process identifiers among the at least two (M) HARQ process identifiers of the first PDSCH to a higher layer in the physical layer of the terminal device.

[0119] In some embodiments, the apparatus further comprises the following parts:

[0120] A first transmitter (not shown, optional) transmits HARQ-ACK information in a slot with index n+k (slot n+k). The slot with index n (slot n) is the end slot of the at least two (M) first PDSCHs or the end slot of the last first PDSCH of the at least two (M) first PDSCHs. For example, the first transmitter transmits HARQ-ACK information using a semi-static HARQ-ACK codebook, but the present embodiment is not limited thereto.

[0121] In some embodiments, the apparatus further comprises the following parts:

[0122] The second transmitting unit transmits HARQ-ACK information in a slot (slot n+k) with index n. The slot (slot n) with index n is the end slot of the at least one (N) second PDSCH or the end slot of the last second PDSCH among the at least one (N) second PDSCH. The second transmitting unit transmits HARQ-ACK information using a dynamic HARQ-ACK codebook, but the present embodiment is not limited thereto.

[0123] The specific aspects of the above-mentioned first determination unit, second determination unit, first reporting unit, second reporting unit, first transmission unit, and second transmission unit may refer to the aspects of Example 1 and will not be described here.

[0124] In some aspects, the first transmitter or the second transmitter transmits HARQ-ACK information on a physical uplink channel, where the HARQ-ACK information includes HARQ-ACK information of at least one (N) second PDSCH.

[0125] The interval between the last symbol of the last second PDSCH of the at least one (N) second PDSCH or the last symbol of the at least one (N) second PDSCH and the first symbol of the physical uplink channel is equal to or greater than the first time.

[0126] In some aspects, the first PDSCH is a second PDSCH, and the number N of the second PDSCHs is equal to the number M of the first PDSCHs.

[0127] In some embodiments, the apparatus further comprises the following parts:

[0128] A third receiving unit (not shown, optional) receives first configuration information including at least one first information element, the first information element including at least one second information element.

[0129] The value of the first information field corresponds to one first information element in the first configuration information, and the one first information element is used to configure a time domain relationship between the at least two (M) first PDSCHs and a PDCCH carrying DCI.

[0130] In some embodiments, the apparatus further comprises the following parts:

[0131] A fourth receiving unit (not shown, optional) receives first configuration information including at least one first information element, the first information element including information of a first number, the first number indicating the number of first PDSCHs corresponding to the first information element.

[0132] For a specific form of the first configuration information, reference can be made to the embodiment of the first embodiment, and it will not be described here.

[0133] In some aspects, the DCI further includes a second information field indicating the RV and / or a third information field indicating the NDI, and a size of the second information field and / or the third information field is related to a second number, the second number being a maximum number of the numbers of first PDSCHs corresponding to all the first information elements in the first configuration information, where the maximum number is a maximum number of the numbers of second information elements included in all the first information elements in the first configuration information, or a maximum number of the first numbers included in all the first information elements in the first configuration information.

[0134] In some embodiments, the apparatus further comprises the following parts:

[0135] A third determination unit (not shown, optional) determines at least one (N) second PDSCH based on at least one of a semi-statically configured transmission direction, a configured PRACH resource, information for dynamically scheduling uplink transmission or dynamically configuring a transmission direction, a configured invalid symbol, or whether it is a cross slot. A specific embodiment of the third determination unit may refer to the aspects of Example 1 and will not be described here.

[0136] The above-mentioned embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments can be used alone, or one or more of the above-mentioned embodiments can be used in combination.

[0137] Although only the components or modules related to the present invention have been described above, the present invention is not limited thereto. The data receiving device 900 may further include other components or modules. For specific contents of these components or modules, reference may be made to the related art.

[0138] Furthermore, for convenience of explanation, Fig. 9 only exemplarily illustrates the connection relationships or signal directions between various components or modules, but it is clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned various components or modules may be implemented by hardware devices such as a processor, a memory, a transmitter, and a receiver, and the present invention is not limited thereto.

[0139] According to this embodiment, since multiple PDSCHs can be scheduled by one DCI, the burden of DCI monitoring on the terminal device can be reduced, and power consumption and complexity can be reduced.

[0140] <Example 4> An embodiment of the present invention provides a data transmission device. The device may be, for example, a network device, or one or more elements or components configured in the network device. Descriptions of the same contents as those in the second embodiment will be omitted.

[0141] 10 is another schematic diagram of a data transmission device according to an embodiment of the present invention. As shown in FIG. 10, a data transmission device 1000 includes the following units:

[0142] The third transmitting unit 1001 transmits downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) to a terminal device. The DCI includes a first information field for indicating at least two (M) first PDSCH time domain resources.

[0143] The fourth transmitting unit 1002 transmits at least one (N) second PDSCH to the terminal device.

[0144] In some aspects, specific aspects of the third transmitting unit 1001 and the fourth transmitting unit 1002 can refer to steps 801 to 802 of the embodiment, and a description of the overlapping contents will be omitted.

[0145] The above-mentioned embodiments are merely illustrative of the present invention, and the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, each of the above-mentioned embodiments can be used alone, or one or more of the above-mentioned embodiments can be used in combination.

[0146] Although only the components or modules related to the present invention have been described above, the present invention is not limited thereto. The data transmission device 1000 may further include other components or modules. For specific contents of these components or modules, reference may be made to related art.

[0147] Furthermore, for convenience of explanation, Fig. 10 only exemplarily illustrates the connection relationships or signal directions between various components or modules, but it is clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned various components or modules may be implemented by hardware devices such as a processor, a memory, a transmitter, and a receiver, and the present invention is not limited thereto.

[0148] According to this embodiment, since multiple PDSCHs can be scheduled by one DCI, the burden of DCI monitoring on the terminal device can be reduced, and power consumption and complexity can be reduced.

[0149] <Example 5> The embodiment of the present invention further provides a communication system, and may refer to FIG. 1. Description of the same contents as those in the first to fourth embodiments will be omitted.

[0150] In some aspects, the communication system 100 may include at least a terminal device 102 and a network device 101 .

[0151] In some aspects, the terminal device 102 receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) transmitted by the network device 101, where the DCI includes a first information field for indicating time domain resources of the at least two (M) first PDSCHs. The terminal device 102 receives at least one (N) second PDSCH transmitted by the network device 101.

[0152] An embodiment of the present invention further provides a network device, which may be, for example, a base station, but the present invention is not limited thereto and may be other network devices.

[0153] Fig. 11 is a schematic diagram of a network device according to an embodiment of the present invention. As shown in Fig. 11, the network device 1100 may include a processor 1110 (e.g., a central processing unit (CPU)) and a memory 1120, and the memory 1120 is connected to the processor 1110. The memory 1120 may store various data, and further stores an information processing program 1130, and executes the program 1130 under the control of the processor 1110.

[0154] For example, the processor 1110 may be configured to execute a program for implementing the data transmission method described in Example 2. For example, the processor 1110 may be configured to transmit downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) to a terminal device, where the DCI includes a first information field for indicating time domain resources of at least two (M) first PDSCHs, and transmit at least one (N) second PDSCH to the terminal device.

[0155] Also, as shown in Fig. 11, the network device 1100 may further include a transceiver 1140 and an antenna 1150. The functions of the above members are similar to those of the prior art, and the description thereof will be omitted here. It is not necessary for the network device 1100 to include all the units shown in Fig. 11. Also, the network device 1100 may further include units not shown in Fig. 11, and may refer to the prior art.

[0156] The embodiment of the present invention further provides a terminal device, but the present invention is not limited thereto and may be other devices.

[0157] Fig. 12 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in Fig. 12, the terminal device 1200 may include a processor 1210 and a memory 1220, where the memory 1220 stores data and programs and is connected to the processor 1210. It should be noted that this diagram is exemplary, and other types of structures may be used to supplement or replace this structure to realize communication functions or other functions.

[0158] For example, the processor 1210 may execute a program to realize the data reception method described in Example 1. For example, the processor 1210 may be configured to receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), where the DCI includes a first information field for indicating time domain resources of at least two (M) first PDSCHs, and receive at least one (N) second PDSCH.

[0159] Also, as shown in Fig. 12, the terminal device 1200 may further include a communication module 1230, an input unit 1240, a display 1250, a power supply 1260, and the like. Here, the functions of the above units are similar to those of the prior art, and the description thereof will be omitted here. It is not necessary for the terminal device 1200 to include all the units shown in Fig. 12. Also, the terminal device 1200 may further include units not shown in Fig. 12, and may refer to the prior art.

[0160] In an embodiment of the present invention, there is further provided a computer-readable program, which, when executed in a terminal device, causes the terminal device to execute the data receiving method according to the first embodiment.

[0161] An embodiment of the present invention further provides a storage medium having a computer-readable program stored therein, the program, when executed, causing a terminal device to execute the data receiving method described in embodiment 1.

[0162] An embodiment of the present invention further provides a computer-readable program, which, when executed in a network device, causes the network device to perform the data transmission method according to the second embodiment.

[0163] An embodiment of the present invention further provides a storage medium having a computer-readable program stored thereon, the program, when executed, causing a network device to perform the data transmission method described in embodiment 2.

[0164] The above-mentioned apparatus and method of the present invention may be realized by hardware or by a combination of hardware and software.The present invention relates to a computer readable program which, when executed by a logic unit, causes the logic unit to realize the above-mentioned apparatus or components, or to realize the above-mentioned various methods or steps.The present invention relates to a storage medium for storing the above-mentioned program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0165] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in the drawings, or one or more combinations of the functional block diagrams, may correspond to each software module in a computer program flow, or each hardware module. These software modules may correspond to each step shown in the drawings. These hardware modules may be realized by implementing these software modules in hardware, for example, using a field programmable gate array (FPGA).

[0166] The software module may 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 hard disk, a CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor so that the processor reads information from the storage medium and writes information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal, or in a memory card inserted in the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a MEGA-SIM card or a large capacity flash memory device with a relatively large capacity, the software module may be stored in the MEGA-SIM card or the large capacity flash memory device.

[0167] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with 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, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof to perform the functions described herein. One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0168] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.

[0169] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above-mentioned examples. (Appendix 1) A data receiving method applied to a terminal device, comprising: receiving, by the terminal device, downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), the DCI including a first information field for indicating at least two (M) first PDSCH time domain resources; The method includes a step of the terminal device receiving at least one (N) second PDSCH. (Appendix 2) The method of claim 1, wherein the DCI further includes a fourth information field for indicating a HARQ process identifier, and the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one of the at least two (M) first PDSCHs. (Appendix 3) 3. The method of claim 2, wherein the one first PDSCH is a first of the at least two (M) first PDSCHs. (Appendix 4) 3. The method of claim 2, further comprising: determining a HARQ process identifier for the at least two (M) first PDSCHs. (Appendix 5) A method according to any one of Supplementary Notes 1 to 4, wherein the physical layer of the terminal device does not report HARQ information of a first PDSCH that is not a second PDSCH among the at least two (M) first PDSCHs to a higher layer. (Appendix 6) A method according to any one of Supplementary Notes 1 to 4, wherein the physical layer of the terminal device reports HARQ information of the at least one (N) second PDSCH to a higher layer. (Appendix 7) A method as described in any one of Supplementary Notes 1 to 4, further comprising a step of the physical layer of the terminal device reporting invalid HARQ process identifiers among the HARQ process identifiers of the at least two (M) first PDSCHs to a higher layer. (Appendix 8) 8. The method of claim 7, wherein the invalid HARQ process identifier is a HARQ process identifier for which there is no corresponding data. (Appendix 9) A method according to any one of Supplementary Notes 1 to 4, further comprising a step of the physical layer of the terminal device reporting HARQ information of the at least two (M) first PDSCHs to a higher layer. (Appendix 10) The method of claim 1, wherein the DCI further includes a fourth information field for indicating a HARQ process identifier, and the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one of the at least one (N) second PDSCHs. (Appendix 11) 11. The method of claim 10, wherein the one second PDSCH is a first one of the at least one (N) second PDSCH. (Appendix 12) 11. The method of claim 10, further comprising determining a HARQ process identifier for the at least one (N) second PDSCH. (Appendix 13) A method according to any one of Supplementary Notes 10 to 12, further comprising a step of the physical layer of the terminal device reporting HARQ information of the at least one (N) second PDSCH to a higher layer. (Appendix 14) The method according to any one of Supplementary Notes 1 to 13, further comprising a step of the terminal device transmitting HARQ-ACK information in a slot (slot n+k) with index n+k, wherein the slot (slot n) with index n is an end slot of the at least two (M) first PDSCHs or an end slot of a last first PDSCH of the at least two (M) first PDSCHs. (Appendix 15) The method described in Supplementary Note 14, wherein the terminal device transmits the HARQ-ACK information using a semi-static HARQ-ACK codebook. (Appendix 16) The method according to any one of Supplementary Notes 1 to 13, further comprising a step in which the terminal device transmits HARQ-ACK information in a slot (slot n+k) with index n+k, the slot (slot n) with index n being an end slot of the at least one (N) second PDSCH or an end slot of a last second PDSCH among the at least one (N) second PDSCH. (Appendix 17) The method described in Supplementary Note 16, wherein the terminal device transmits the HARQ-ACK information using a dynamic HARQ-ACK codebook. (Appendix 18) The terminal device transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (N) second PDSCH; 18. The method of any of claims 14 to 17, wherein an interval between a last symbol of the last of the at least one (N) second PDSCHs or a last symbol of the at least one (N) second PDSCHs and a first symbol of the physical uplink channel is equal to or greater than a first time. (Appendix 19) The terminal device transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (P) fourth PDSCH; 18. The method of any of claims 14 to 17, wherein the at least one (P) fourth PDSCH is at least one (P) PDSCH of the at least one (N) second PDSCH, and an interval between the last symbol of the last second PDSCH of each fourth PDSCH and the first symbol of the physical uplink channel is equal to or greater than a first time. (Appendix 20) The terminal device transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (N) second PDSCH; 18. The method of any of claims 14 to 17, wherein an interval between the last symbol of each of the at least one (N) second PDSCHs and the first symbol of the physical uplink channel is equal to or greater than a first time. (Appendix 21) The terminal device transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (N) second PDSCH; 18. The method of any of claims 14 to 17, wherein an interval between a last symbol of the last of the at least two (M) first PDSCHs or a last symbol of the at least two (M) first PDSCHs and a first symbol of the physical uplink channel is equal to or greater than a first time. (Appendix 22) The first PDSCH is the second PDSCH, 22. The method of claim 1, wherein the number N of second PDSCHs is equal to the number M of first PDSCHs. (Appendix 23) 23. The method of any of claims 1 to 22, wherein the time domain resources of the at least two (M) first PDSCHs include time domain resources of the at least one (N) second PDSCH. (Appendix 24) 24. The method of any of claims 1 to 23, wherein the at least two (M) first PDSCHs are contiguous or discontinuous. (Appendix 25) 25. The method of any of the preceding claims, wherein the number of time domain symbols of the at least two (M) first PDSCHs is the same or different. (Appendix 26) 26. The method of any of claims 1 to 25, wherein each first PDSCH of the at least two (M) first PDSCHs is in one slot or is not in one slot. (Appendix 27) The method further includes a step of receiving, by the terminal device, first configuration information including at least one first information element, the first information element including at least one second information element; 27. The method of claim 1, wherein a value of the first information field corresponds to one first information element in the first configuration information, and the one first information element is used to configure a time domain relationship between the at least two (M) first PDSCHs and a PDCCH carrying the DCI. (Appendix 28) 28. The method of claim 27, wherein each second information element of the one first information element includes time domain resource configuration information of one first PDSCH. (Appendix 29) 27. The method of any one of Supplementary Notes 1 to 26, further comprising a step of: the terminal device receiving first configuration information including at least one first information element, the first information element including information of a first number, the first number indicating the number of first PDSCHs corresponding to the first information element. (Appendix 30) 30. The method of claim 1, wherein the DCI further comprises a second information field indicating an RV and / or a third information field indicating an NDI, the size of the second information field and / or the third information field being related to a second number, the second number being a maximum number of first PDSCHs corresponding to all first information elements in the first configuration information. (Appendix 31) 31. The method of claim 30, wherein the maximum number is a maximum number of the second information elements included in all first information elements in the first configuration information, or a maximum number of the first numbers included in all first information elements in the first configuration information. (Appendix 32) 32. A method according to any of Supplementary Notes 1 to 31, in which the terminal device determines the at least one (N) second PDSCH based on at least one of a semi-statically configured transmission direction, a configured PRACH resource, information for dynamically scheduling uplink transmission or information for dynamically configuring a transmission direction, a configured invalid symbol, or whether it is a cross slot. (Appendix 33) If at least one symbol of the first PDSCH is semi-statically configured as an uplink or is configured as disabled, the first PDSCH is not the second PDSCH; or When at least one symbol of the first PDSCH is semi-statically configured as an uplink, the second PDSCH corresponds to the first PDSCH one-to-one, and the slot in which the second PDSCH is located is the same as or different from the slot in which the corresponding first PDSCH is located, or The method according to claim 32, wherein the first PDSCH is divided into at least two third PDSCHs not including at least one uplink symbol, and the at least two divided third PDSCHs and the first PDSCH not including an uplink symbol are defined as at least one (N) second PDSCH. (Appendix 34) 34. The method of claim 32 or 33, wherein if a PRACH is configured in at least one symbol of the first PDSCH or if at least one symbol is located a third number of symbols (e.g., referred to as an interval symbol) before a PRACH is configured, the first PDSCH is not the second PDSCH. (Appendix 35) If the time domain resource of the first PDSCH is a cross slot, the first PDSCH is not the second PDSCH; or A method according to any one of appendices 32 to 34, comprising splitting a first PDSCH that is a cross slot into at least two third PDSCHs that are not cross slots, and treating the at least two split third PDSCHs and the first PDSCH that is not a cross slot as at least one (N) second PDSCH. (Appendix 36) When at least one symbol of the first PDSCH is dynamically scheduled for uplink transmission or the transmission direction is dynamically configured as uplink or invalid, the first PDSCH is not the second PDSCH, or When at least one symbol of the first PDSCH is dynamically scheduled for uplink transmission or the transmission direction is dynamically configured as uplink or invalid, the second PDSCH corresponds to the first PDSCH one-to-one, and the slot in which the second PDSCH is located is the same as or different from the slot in which the corresponding first PDSCH is located, or The method according to any one of Supplementary Notes 32 to 35, wherein the first PDSCH is divided into at least two third PDSCHs not including at least one uplink symbol, and the at least two divided third PDSCHs and the first PDSCH not including an uplink symbol are defined as at least one (N) second PDSCH. (Appendix 37) 37. The method of claim 36, wherein the information for dynamically scheduling uplink transmission or the information for dynamically configuring the transmission direction is transmitted before the DCI. (Appendix 38) A data transmission method applied to a network device, comprising: The network device transmits downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) to a terminal device, the DCI including a first information field for indicating time domain resources of at least two (M) first PDSCHs; The method includes a step of the network device transmitting at least one (N) second PDSCH to the terminal device. (Appendix 39) A data receiving device applied to a terminal device, A first receiver for receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), the DCI including a first information field for indicating time domain resources of at least two (M) first PDSCHs; and a second receiving unit that receives at least one (N) second PDSCH. (Appendix 40) The apparatus of claim 39, wherein the DCI further includes a fourth information field for indicating a HARQ process identifier, and the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one of the at least two (M) first PDSCHs. (Appendix 41) The apparatus of claim 40, wherein the one first PDSCH is a first of the at least two (M) first PDSCHs. (Appendix 42) 41. The apparatus of claim 40, further comprising: a first determination unit configured to determine HARQ process identifiers for the at least two (M) first PDSCHs. (Appendix 43) The apparatus of any of Supplementary Notes 39 to 42, further comprising: a processing unit that does not report HARQ information of a first PDSCH that is not a second PDSCH among the at least two (M) first PDSCHs in a physical layer of the terminal device to a higher layer. (Appendix 44) 43. The apparatus of claim 39, further comprising: a first reporting unit configured to report HARQ information of the at least one (N) second PDSCH to a higher layer in a physical layer of the terminal device. (Appendix 45) The apparatus of any of Supplementary Notes 39 to 42, further comprising: a third reporting unit configured to report invalid HARQ process identifiers among the HARQ process identifiers of the at least two (M) first PDSCHs to a higher layer in a physical layer of the terminal device. (Appendix 46) 46. ​​The apparatus of claim 45, wherein the invalid HARQ process identifier is a HARQ process identifier for which there is no corresponding data. (Appendix 47) 43. The apparatus of claim 39, further comprising: a first reporting unit configured to report HARQ information of the at least two (M) first PDSCHs to a higher layer in a physical layer of the terminal device. (Appendix 48) The apparatus of claim 39, wherein the DCI further includes a fourth information field for indicating a HARQ process identifier, and the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one of the at least one (N) second PDSCHs. (Appendix 49) 49. The apparatus of claim 48, wherein the one second PDSCH is a first one of the at least one (N) second PDSCH. (Appendix 50) 49. The apparatus of claim 48, further comprising: a second determination unit configured to determine a HARQ process identifier for the at least one (N) second PDSCH. (Appendix 51) An apparatus as described in any of Supplementary Notes 48 to 50, further comprising: a second reporting unit that reports HARQ information of the at least one (N) second PDSCH to a higher layer in a physical layer of the terminal device. (Appendix 52) 52. The apparatus of any of Supplementary Notes 39 to 51, further comprising: a first transmitter configured to transmit HARQ-ACK information in a slot of index n+k (slot n+k), wherein the slot of index n (slot n) is an end slot of the at least two (M) first PDSCHs or an end slot of a last first PDSCH of the at least two (M) first PDSCHs. (Appendix 53) 53. The apparatus of claim 52, wherein the first transmitter transmits the HARQ-ACK information using a semi-static HARQ-ACK codebook. (Appendix 54) 52. The apparatus of any of Supplementary Notes 39 to 51, further comprising: a second transmitter configured to transmit HARQ-ACK information in a slot of index n+k (slot n+k), wherein the slot of index n (slot n) is an end slot of the at least one (N) second PDSCH or an end slot of a last second PDSCH of the at least one (N) second PDSCH. (Appendix 55) 55. The apparatus of claim 54, wherein the second transmitting unit transmits the HARQ-ACK information using a dynamic HARQ-ACK codebook. (Appendix 56) The first transmitter or the second transmitter transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (N) second PDSCH; 56. The apparatus of any of Supplementary Notes 52 to 55, wherein an interval between a last symbol of the last of the at least one (N) second PDSCHs or the last symbol of the at least one (N) second PDSCHs and a first symbol of the physical uplink channel is greater than or equal to a first time. (Appendix 57) The first transmitter or the second transmitter transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (P) fourth PDSCH; 56. The apparatus of any of claims 52 to 55, wherein the at least one (P) fourth PDSCH is at least one (P) PDSCH of the at least one (N) second PDSCH, and an interval between the last symbol of the last second PDSCH of each fourth PDSCH and the first symbol of the physical uplink channel is greater than or equal to a first time. (Appendix 58) The first transmitter or the second transmitter transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (N) second PDSCH; 56. The apparatus of any of claims 52 to 55, wherein an interval between the last symbol of each of the at least one (N) second PDSCHs and the first symbol of the physical uplink channel is greater than or equal to a first time. (Appendix 59) The first transmitter or the second transmitter transmits the HARQ-ACK information on a physical uplink channel, and the HARQ-ACK information includes HARQ-ACK information of the at least one (N) second PDSCH; 56. The apparatus of any of Supplementary Notes 52 to 55, wherein an interval between a last symbol of the last of the at least two (M) first PDSCHs or a last symbol of the at least two (M) first PDSCHs and a first symbol of the physical uplink channel is equal to or greater than a first time. (Appendix 60) The first PDSCH is the second PDSCH, 60. The apparatus of claim 39, wherein the number N of second PDSCHs is equal to the number M of first PDSCHs. (Appendix 61) 61. The apparatus of any of claims 39 to 60, wherein the time domain resources of the at least two (M) first PDSCHs include time domain resources of the at least one (N) second PDSCH. (Appendix 62) 62. The apparatus of any of claims 39 to 61, wherein the at least two (M) first PDSCHs are contiguous or discontinuous. (Appendix 63) 63. The apparatus of any of claims 39 to 62, wherein the number of time domain symbols of the at least two (M) first PDSCHs is the same or different. (Appendix 64) 64. The apparatus of any of claims 39 to 63, wherein each first PDSCH of the at least two (M) first PDSCHs is in one slot or is not in one slot. (Appendix 65) a third receiving unit configured to receive first configuration information including at least one first information element, the first information element including at least one second information element; 65. The apparatus of claim 39, wherein a value of the first information field corresponds to one first information element in the first configuration information, and the one first information element is used to configure a time domain relationship between the at least two (M) first PDSCHs and a PDCCH carrying the DCI. (Appendix 66) The apparatus of claim 65, wherein each second information element of the one first information element includes time domain resource configuration information of one first PDSCH. (Appendix 67) 65. The apparatus of any of claims 39 to 64, further comprising: a fourth receiver configured to receive first configuration information including at least one first information element, the first information element including a first number of information, the first number indicating a number of first PDSCHs corresponding to the first information element. (Appendix 68) 68. The apparatus of claim 39, wherein the DCI further comprises a second information field indicating an RV and / or a third information field indicating an NDI, the size of the second information field and / or the third information field being related to a second number, the second number being a maximum number of first PDSCHs corresponding to all first information elements in the first configuration information. (Appendix 69) 69. The apparatus of claim 68, wherein the maximum number is a maximum number of the second information elements included in all first information elements in the first configuration information, or a maximum number of the first numbers included in all first information elements in the first configuration information. (Appendix 70) 70. The apparatus of claim 39, further comprising a third decision unit configured to determine the at least one (N) second PDSCH based on at least one of a semi-statically configured transmission direction, a configured PRACH resource, information for dynamically scheduling uplink transmission or dynamically configuring a transmission direction, configured invalid symbols, or whether or not it is a cross slot. (Appendix 71) If at least one symbol of the first PDSCH is semi-statically configured as an uplink or is configured as disabled, the first PDSCH is not the second PDSCH; or When at least one symbol of the first PDSCH is semi-statically configured as an uplink, the second PDSCH corresponds to the first PDSCH one-to-one, and the slot in which the second PDSCH is located is the same as or different from the slot in which the corresponding first PDSCH is located, or The apparatus of claim 70, further comprising: dividing the first PDSCH into at least two third PDSCHs that do not include at least one uplink symbol; and defining the at least two divided third PDSCHs and the first PDSCH that does not include an uplink symbol as at least one (N) second PDSCH. (Appendix 72) 72. The apparatus of claim 70 or 71, wherein the first PDSCH is not the second PDSCH if a PRACH is configured in at least one symbol of the first PDSCH or if at least one symbol is located a third number of symbols (e.g., referred to as an interval symbol) before a PRACH is configured. (Appendix 73) If the time domain resource of the first PDSCH is a cross slot, the first PDSCH is not the second PDSCH; or An apparatus as described in any of Supplementary Notes 70 to 72, which divides a first PDSCH that is a cross slot into at least two third PDSCHs that are not cross slots, and defines the at least two divided third PDSCHs and the first PDSCH that is not a cross slot as at least one (N) second PDSCH. (Appendix 74) When at least one symbol of the first PDSCH is dynamically scheduled for uplink transmission or the transmission direction is dynamically configured as uplink or invalid, the first PDSCH is not the second PDSCH, or When at least one symbol of the first PDSCH is dynamically scheduled for uplink transmission or the transmission direction is dynamically configured as uplink or invalid, the second PDSCH corresponds to the first PDSCH one-to-one, and the slot in which the second PDSCH is located is the same as or different from the slot in which the corresponding first PDSCH is located, or The apparatus according to any one of Supplementary Notes 70 to 73, wherein the first PDSCH is divided into at least two third PDSCHs not including at least one uplink symbol, and the at least two divided third PDSCHs and the first PDSCH not including an uplink symbol are defined as at least one (N) second PDSCH. (Appendix 75) 75. The apparatus of claim 74, wherein the information for dynamically scheduling uplink transmission or the information for dynamically configuring the transmission direction is transmitted before the DCI. (Appendix 76) A data transmission device applied to a network device, A third transmitter that transmits downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) to a terminal device, the DCI including a first information field for indicating at least two (M) first PDSCH time domain resources; and a fourth transmitting unit that transmits at least one (N) second PDSCH to the terminal device.

Claims

1. A data receiving device applied to a terminal device, A first receiver for receiving downlink control information (DCI) for scheduling a plurality of physical downlink shared channels (PDSCHs), the DCI including a first information field for indicating time domain resources of the scheduled plurality of PDSCHs; A second receiving unit that receives a PDSCH that does not overlap with an UL symbol configured by a higher layer parameter among the scheduled PDSCHs, and / or does not receive a PDSCH that overlaps with an UL symbol configured by a higher layer parameter among the scheduled PDSCHs, The HARQ process identifier indicated by the DCI is applied to a first PDSCH among PDSCHs that do not overlap with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the HARQ process identifier is incremented by one for each subsequent PDSCH according to a scheduling order, and a modulo arithmetic operation of the number of HARQ processes for a corresponding cell is applied; The apparatus, wherein a HARQ process identifier is not incremented for a PDSCH that is not received if at least one symbol overlaps with a UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

2. 2. The apparatus of claim 1, wherein the DCI further includes a fourth information field for indicating a HARQ process identifier, and the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one PDSCH among PDSCHs that do not overlap with an UL symbol configured by the higher layer parameters.

3. The apparatus of claim 2 , wherein the one PDSCH is a first one of the PDSCHs that does not overlap with a UL symbol configured by the higher layer parameters.

4. The apparatus of claim 2 , further comprising: a first determiner configured to determine a HARQ process identifier of a PDSCH that does not overlap with a UL symbol configured by the higher layer parameter based on the fourth information field.

5. The device according to claim 2 , further comprising: a first reporting unit configured to report HARQ information of a PDSCH that does not overlap with a UL symbol configured by the higher layer parameters in a physical layer of the terminal device to a higher layer.

6. 2. The apparatus of claim 1, wherein the DCI further comprises a fourth information field for indicating a HARQ process identifier, and the HARQ process identifier indicated by the fourth information field is a HARQ process identifier of one PDSCH among the scheduled PDSCHs.

7. 7. The apparatus of claim 6, wherein the one PDSCH of the scheduled PDSCHs is a first one of the scheduled PDSCHs.

8. The apparatus of claim 6 , further comprising: a second determiner configured to determine HARQ process identifiers for the scheduled PDSCHs based on the fourth information field.

9. The apparatus of claim 1 , further comprising: a second reporting unit configured to report an invalid HARQ process identifier among the HARQ process identifiers of the scheduled PDSCHs to a higher layer in a physical layer of the terminal device.

10. 2. The apparatus of claim 1, further comprising: a first transmitter configured to transmit HARQ-ACK information in a slot with index n+k (slot n+k), where the slot with index n (slot n) is an end slot of the scheduled PDSCHs or an end slot of a last PDSCH of the scheduled PDSCHs.

11. The slot of index n (slot n) is the end slot of the scheduled PDSCHs or the end slot of the last PDSCH among the scheduled PDSCHs, The apparatus of claim 10 , wherein the first transmitter transmits the HARQ-ACK information using a semi-static HARQ-ACK codebook.

12. The slot of index n (slot n) is an end slot of a PDSCH that does not overlap with a UL symbol configured by the higher layer parameters or an end slot of the last PDSCH among the PDSCHs that do not overlap with a UL symbol configured by the higher layer parameters, The apparatus of claim 10 , wherein the first transmitter transmits the HARQ-ACK information using a dynamic HARQ-ACK codebook.

13. The first transmitter transmits the HARQ-ACK information on a physical uplink channel, the HARQ-ACK information including HARQ-ACK information of a PDSCH that does not overlap with a UL symbol configured by the higher layer parameters; 11. The apparatus of claim 10, wherein an interval between a last symbol of a last PDSCH among PDSCHs that do not overlap with an UL symbol configured by the higher layer parameters or a last symbol of a PDSCH that does not overlap with an UL symbol configured by the higher layer parameters and a first symbol of the physical uplink channel is equal to or greater than a first time.

14. a third receiver configured to receive first configuration information including at least one first information element, the first information element including at least one second information element; 2. The apparatus of claim 1, wherein a value of the first information field corresponds to a first information element in the first configuration information, the first information element being used to configure a time domain relationship between the scheduled PDSCHs and a PDCCH carrying the DCI.

15. 2. The apparatus of claim 1, further comprising: a fourth receiver configured to receive first configuration information including at least one first information element, the first information element including a first number of information, the first number indicating a number of the scheduled PDSCHs corresponding to the first information element.

16. 16. The apparatus of claim 15, wherein the DCI further comprises a second information field indicating an RV and / or a third information field indicating an NDI, a size of the second information field and / or the third information field being related to a second number, the second number being a maximum number of the scheduled PDSCHs corresponding to all first information elements in the first configuration information.

17. 17. The apparatus of claim 16, wherein the maximum number is a maximum number among numbers of second information elements included in all first information elements in the first configuration information, or a maximum number among the first numbers included in all first information elements in the first configuration information.

18. A data transmission device applied to a network device, A third transmitter for transmitting downlink control information (DCI) for scheduling a plurality of physical downlink shared channels (PDSCHs) to a terminal device, the DCI including a first information field for indicating time domain resources of the scheduled plurality of PDSCHs; A fourth transmission unit that transmits a PDSCH that does not overlap with an UL symbol configured by a higher layer parameter among the scheduled PDSCHs to the terminal device, and / or does not transmit a PDSCH that overlaps with an UL symbol configured by a higher layer parameter among the scheduled PDSCHs to the terminal device, The HARQ process identifier indicated by the DCI is applied to a first PDSCH among PDSCHs that do not overlap with an UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the HARQ process identifier is incremented by one for each subsequent PDSCH according to a scheduling order, and a modulo arithmetic operation of the number of HARQ processes for a corresponding cell is applied; The apparatus, wherein a HARQ process identifier is not incremented for a PDSCH that is not transmitted if at least one symbol overlaps with a UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

Images