Data transmission method, data reception method and device

Abstract

The embodiments of the present application provide a data transmission method, a data reception method and an apparatus. The data reception method includes: a terminal device receives first downlink control information for scheduling a PDSCH (201); and the terminal device receives one or more PDSCHs among the PDSCHs scheduled by the first downlink control information (202).

Description

[Technical field]

[0001] TECHNICAL FIELD Embodiments of the present application relate to the field of communications technology. [Background technology]

[0002] A Physical Downlink Shared Channel (PDSCH) is a type of physical downlink channel in a wireless communication system and is used to carry downlink data. A Physical Uplink Shared Channel (PUSCH) is a type of physical uplink channel in a wireless communication system and is used to carry uplink data.

[0003] The PDSCH and the PUSCH can be scheduled by downlink control information (DCI). The DCI for scheduling the PDSCH or the PUSCH includes at least an information field (or fields) for indicating the resource of the PDSCH. In the current new radio (NR) system, a plurality of DCI formats for scheduling the PDSCH or the PUSCH are defined, such as, but not limited to, DCI format 1_0 (for scheduling the PDSCH), DCI format 0_0 (for scheduling the PUSCH), DCI format 1_1 (for scheduling the PDSCH), DCI format 0_1 ​​(for scheduling the PUSCH), DCI format 1_2 (for scheduling the PDSCH), and DCI format 0_2 (for scheduling the PUSCH). Different specific information and / or sizes included in the DCI of different DCI formats meet different scheduling requirements.

[0004] The PDSCH and PUSCH may be semi-statically configured (or semi-statically scheduled) or semi-persistently scheduled. In NR, the semi-statically configured or semi-persistently scheduled PDSCH is, for example, referred to as an SPS PDSCH. The semi-statically configured or semi-persistently scheduled PUSCH is, for example, referred to as a CG PUSCH. In some cases, after the network device provides the SPS or CG configuration via RRC signaling, it is necessary to further activate the SPS or CG configuration by DCI so that the terminal device receives the SPS PDSCH or transmits the CG PUSCH accordingly.

[0005] It should be noted that the above description of the technical background is provided to clearly and completely explain the technical aspects of the present application and to facilitate the understanding of those skilled in the art, and it cannot be considered that the technical aspects are known to those skilled in the art just because they are described in the background section of the present application. Summary of the Invention [Problem to be solved by the invention]

[0006] The inventor has discovered that a technology for scheduling a plurality of PDSCHs / PUSCHs using one DCI is under consideration, and furthermore, in the conventional technology, it is assumed that only one PDSCH / PUSCH can be scheduled using one DCI, and furthermore, such DCI supports semi-static or semi-persistent scheduling of the PDSCH or PUSCH, and supports dynamic retransmission for data corresponding to the semi-static or semi-persistent scheduling, but does not consider how to support semi-static or semi-persistent scheduling of the PDSCH or PUSCH, and whether to support dynamic retransmission for data corresponding to the semi-static or semi-persistent scheduling, when one DCI (or DCI format) may schedule a plurality of PDSCHs / PUSCHs. [Means for solving the problem]

[0007] In order to solve the above problems, embodiments of the present application provide a data transmission method, a data reception method, and an apparatus for scheduling multiple PDSCHs / PUSCHs using one DCI, and further supporting semi-static or semi-persistent scheduling of the PDSCHs or PUSCHs when one DCI (or DCI format) can schedule multiple PDSCHs / PUSCHs, and supporting dynamic retransmission of data corresponding to the semi-static or semi-persistent scheduling.

[0008] According to one aspect of an embodiment of the present application, there is provided a data receiving device configured in a terminal device, the data receiving device including: a first receiving unit that receives first downlink control information for scheduling a PDSCH; and a second receiving unit that receives one or more PDSCHs among the PDSCHs scheduled by the first downlink control information PDSCH.

[0009] According to another aspect of an embodiment of the present application, there is provided a data receiving device configured in a terminal device, the data receiving device including: a first receiving unit that receives a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and a second receiving unit that receives second downlink control information for activating an SPS configuration, wherein the first configuration parameter is applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0010] According to another aspect of an embodiment of the present application, there is provided a data transmission device configured in a terminal device, the data transmission device including: a first receiving unit that receives third downlink control information for scheduling a PUSCH; and a transmitting unit that transmits one or more PUSCHs among the PUSCHs scheduled by the third downlink control information.

[0011] One of the beneficial effects of the embodiment of the present application is as follows: According to the embodiment of the present application, it is possible to support scheduling of multiple PDSCHs / PUSCHs by one DCI, and further, when one DCI (or DCI format) can schedule multiple PDSCHs / PUSCHs, it is possible to support semi-static or semi-persistent scheduling of PDSCHs or PUSCHs, and it is possible to support dynamic retransmission for data corresponding to semi-static or semi-persistent scheduling. Furthermore, when one DCI format (e.g., DCI format 1_1 or DCI format 0_1) is configured to be able to schedule multiple PDSCHs or PUSCHs, the SPS or CG configuration can be activated / deactivated using the DCI format, or the DCI format can be used to schedule dynamic retransmission for data corresponding to semi-static or semi-persistent scheduling. That is, the DCI format can be used not only to support semi-static or semi-persistent scheduling of PDSCHs or PUSCHs, but also to support dynamic scheduling. In this way, when SPS or CG is configured and the above DCI format is configured to be able to schedule a plurality of PDSCHs or PUSCHs, the UE does not need to blindly detect another DCI format other than the DCI format used to semi-statically or semi-persistently schedule the PDSCHs or PUSCHs and / or to support dynamic retransmission of data corresponding to the semi-static or semi-persistent scheduling for the downlink or uplink, and only needs to blindly detect the DCI format. This reduces the complexity of the UE detecting and receiving the PDCCH and can reduce power consumption. Meanwhile, the flexibility of the configuration and resource scheduling can be increased for the network device.

[0012] With reference to the following description and drawings, specific embodiments of the present application are disclosed in detail, showing the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not restrictive in scope. Within the spirit and terms of the appended claims, the embodiments of the present application include many changes, modifications and equivalents.

[0013] Features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments, may be combined with feature information in the other embodiments, or may substitute for features in the other embodiments.

[0014] It should be emphasized that the term "comprising" when used in this specification refers to the presence of features, wholes, steps or assemblies, but does not exclude the presence or addition of one or more other features, wholes, steps or assemblies.

[0015] Elements and features described in one drawing or one embodiment of the present application may be combined with elements and feature information shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar symbols may be used to indicate corresponding parts in several drawings and to indicate corresponding parts used in multiple embodiments. [Brief description of the drawings]

[0016] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present application; [Diagram 2] FIG. 2 is a schematic diagram of a data receiving method according to an embodiment of the present application; [Diagram 3] 1 is a schematic diagram of a data scheduling method according to an embodiment of the present application; [Figure 4] FIG. 2 is a schematic diagram of a data transmission method according to an embodiment of the present application; [Diagram 5] 1 is a schematic diagram of a data scheduling method according to an embodiment of the present application; [Figure 6] 1 is a schematic diagram of a data receiving device according to an embodiment of the present application; [Figure 7] FIG. 2 is another schematic diagram of a data receiving device according to an embodiment of the present application. [Figure 8] FIG. 11 is yet another schematic diagram of a data receiving device according to an embodiment of the present application. [Figure 9] 1 is a schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 10] FIG. 2 is another schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 11] FIG. 2 is another schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 12] 1 is a schematic diagram of a data transmission device according to an embodiment of the present application; [Figure 13] 1 is a schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 14] FIG. 2 is another schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 15] FIG. 2 is yet another schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 16] FIG. 2 is another schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 17] FIG. 2 is yet another schematic diagram of a data scheduling device according to an embodiment of the present application; [Figure 18] 1 is a schematic diagram of a terminal device according to an embodiment of the present application; [Figure 19] 1 is a schematic diagram of a configuration of a network device according to an embodiment of the present application. [Figure 20] FIG. 2 is a schematic diagram of a slot structure. [Figure 21] FIG. 2 is a schematic diagram of a frame structure. [Figure 22] 1 is a schematic diagram of time domain resources in which a PDCCH / DCI for activating an SPS exists, and time domain resources of a PDSCH indicated by a PDCCH / DCI for activating an SPS. [Diagram 23]1 is a schematic diagram of time domain resources of DCI format 1_1 for activating SPS and PDSCH activated by the DCI. [Figure 24] A schematic diagram of DCI format 1_1 for scheduling retransmission for SPS and PDSCH scheduled by the DCI. [Diagram 25] 1 is a schematic diagram of slots in which DCI format 1_1 exists for activating SPS, slots in which SPS PDSCH activated by DCI format 1_1 exists, and corresponding HARQ process IDs. [Figure 26] FIG. 2 is another schematic diagram of a HARQ process ID corresponding to an SPS PDSCH; [Figure 27] A schematic diagram of time domain resources in which PDCCH / DCI exists for activating CG, and time domain resources of PUSCH indicated by PDCCH / DCI for activating CG. [Figure 28] 1 is a schematic diagram of time domain resources in which DCI format 1_1 exists for activating a CG, and a PUSCH activated by the DCI. [Figure 29] 1 is a schematic diagram of DCI format 1_1 for scheduling retransmission for a CG, and a PUSCH scheduled by the DCI. [Diagram 30] 1 is a schematic diagram of slots in which DCI format 1_1 for activating a CG is present, slots in which a CG PUSCH activated by DCI format 1_1 is present, and corresponding HARQ process IDs. [Diagram 31] FIG. 13 is another schematic diagram of a HARQ process ID corresponding to a CG PUSCH. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] The above and other features of the present application will become apparent from the following specification with reference to the drawings. Particular embodiments of the present application are specifically disclosed in the specification and drawings, showing some embodiments in which the principles of the present application may be employed. It is to be understood that the present application is not limited to the disclosed embodiments, but rather, the present application includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0018] In the examples of the present application, the terms "first", "second", etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited to these terms. The term "and / or" includes any and all combinations of one or more of the associated listed terms. Terms such as "including", "comprising", "having", etc. refer to the presence of a stated feature, element, part or assembly, but do not exclude the presence or addition of one or more other features, elements, parts or assemblies.

[0019] In the examples of this application, the singular forms "a," "the," and the like, include the plural and should be understood broadly to mean "a type of," or "a type of," and not limited to the meaning of "one." Furthermore, the term "said" includes both the singular and the plural, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood as "at least in part according to," and the term "based on" should be understood as "at least in part based on," unless the context clearly indicates otherwise.

[0020] In embodiments of the present application, the terms "communications network" or "wireless communication network" refer to a network conforming to any suitable communications standard, such as, for example, Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0021] Moreover, communication between devices in the communication system may be accomplished via any generation of communication protocols, which may include, but are not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other currently known or later developed communication protocols.

[0022] In the embodiments of the present application, the term "network device" refers to a device that allows a terminal device to access a communication network and provides services to the terminal device in a communication system, for example. 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 mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), and other devices.

[0023] A base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), 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., femeto, pico, etc.), an Integrated Access and Backhaul (IAB) node, an IAB-DU, or an IAB-donor. Furthermore, the term "base station" may include some or all of these functions, and each base station may provide communication coverage to 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. Unless confusion arises, the terms "cell" and "base station" are interchangeable.

[0024] In the embodiments of the present application, 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 referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), an IAB-MT, a station, etc.

[0025] The terminal device may include, but is not limited to, a cellular 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.

[0026] Furthermore, in a scenario such as the Internet of Things (IoT), the terminal device may be a device or apparatus that performs monitoring or measurement, and may include, but is 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.

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

[0028] In the following description, unless confusion occurs, the terms "uplink control signal" and "uplink control information (UCI)" or "Physical Uplink Control Channel (PUCCH)" are interchangeable, and the terms "uplink data signal" and "uplink data information" or "Physical Uplink Shared Channel (PUSCH)" are interchangeable. The terms "downlink control signal" and "downlink control information (DCI)" or "Physical Downlink Control Channel (PDCCH)" are interchangeable, and the terms "downlink data signal" and "downlink data information" or "Physical Downlink Shared Channel (PDSCH)" are interchangeable.

[0029] Furthermore, the transmission or reception of a PUSCH may be understood as the transmission or reception of uplink data carried by the PUSCH, the transmission or reception of a PUCCH may be understood as the transmission or reception of uplink information (e.g., UCI) carried by the PUCCH, the transmission or reception of a PDSCH may be understood as the transmission or reception of downlink data carried by the PDSCH, and the transmission or reception of a PDCCH may be understood as the transmission or reception of downlink information (e.g., DCI) carried by the PDCCH.

[0030] In the embodiment of the present application, the higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, and the RRC signaling may include, for example, an RRC message, such as a Master Information Block (MIB), system information, a dedicated RRC message, or an RRC information element (RRC IE), or an information field (or an information field) included in the RRC message or the RRC information element. The higher layer signaling may be, for example, further Medium Access Control (MAC) signaling, or may be referred to as a MAC control element (MAC CE). However, the present application is not limited thereto.

[0031] The following describes a scenario in the embodiment of the present application through an example, but the present application is not limited thereto.

[0032] Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application, and will be described by taking a terminal device and a network device as an example. As shown in Fig. 1, a communication system 100 may include a network device 101 and terminal devices 102 and 103. For convenience, Fig. 1 takes only two terminal devices and one network device as an example for description, but the embodiment of the present application is not limited thereto.

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

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

[0035] In the prior art, SPS and CG may support aggregation / repetition. For SPS PDSCH, if pdsch-AggregationFactor is included in SPS configuration (sps-Config), it is repeated the number of times set by the pdsch-AggregationFactor. If pdsch-AggregationFactor is not included in SPS configuration (sps-Config) but pdsch-AggregationFactor is included in PDSCH configuration (pdsch-Config), it is repeated the number of times set by pdsch-AggregationFactor in the PDSCH configuration. For CG PUSCH, if numberOfRepetitions is included in TDRA (Time Domain Resource Allocation) configuration indicated by DCI for activating the CG PUSCH, it is repeated the number of times set by the numberOfRepetitions. If the TDRA setting specified by the DCI that activates the CG does not include numberOfRepetitions (including cases where activation by DCI is not required), but the CG configuration (ConfiguredGrantConfig) includes repK, the CG will be repeated the number of times set by repK.

[0036] Meanwhile, retransmission of SPS and CG may also support aggregation / repetition. This retransmission is scheduled by DCI. The CRC of the DCI is scrambled by CS-RNTI, and NDI=1. For SPS retransmission, if the PDSCH configuration (pdsch-Config) includes pdsch-AggregationFactor, it is repeated the number of times set by pdsch-AggregationFactor in the PDSCH configuration. For CG retransmission, if the TDRA configuration specified by DCI includes numberOfRepetitions, it is repeated the number of times set by numberOfRepetitions. If the TDRA configuration specified by DCI does not include numberOfRepetitions, but the PUSCH configuration (pusch-Config) includes pusch-AggregationFactor, it is repeated the number of times set by pusch-AggregationFactor.

[0037] However, the above conventional technology assumes that only one PDSCH / PUSCH can be scheduled by one DCI, but does not consider the case where multiple PDSCHs / PUSCHs can be scheduled by one DCI.

[0038] On the other hand, in Rel-17 (version 17), according to the discussion so far, in order to support scheduling of multiple PDSCHs by one DCI, one TDRA table may be configured for DCI format 1_1, and one or more rows in the TDRA table each include multiple SLIVs, and the SLIVs correspond one-to-one to the PDSCHs. In this way, multiple PDSCHs may be scheduled by using DCI format 1_1 and indicating rows including multiple SLIVs. In this case, if pdsch-AggregationFactor is included in the PDSCH configuration (pdsch-Config), the pdsch-AggregationFactor is not used for DCI format 1_1.

[0039] Similarly, to support scheduling of multiple PUSCHs by one DCI, one TDRA table may be configured for DCI format 0_1, and one or more rows in the TDRA table each include multiple SLIVs, and the SLIVs correspond one-to-one to the PUSCHs. In this way, multiple PUSCHs may be scheduled by using DCI format 0_1 ​​and indicating rows including multiple SLIVs. In this case, if pdsch-AggregationFactor is included in the PUSCH configuration (pusch-Config), the pdsch-AggregationFactor is not used for DCI format 1_1.

[0040] However, in the above discussion, there is no case where DCI format 1_1 and DCI format 0_1 ​​can be used for SPS activation and retransmission, and CG activation and retransmission, respectively. According to the above conventional technology and discussion, it is not possible to determine whether the SPS PDSCH (or the PDSCH corresponding to the activated SPS) activated by the DCI format 1_1 and DCI format 0_1 ​​supports aggregation / repetition.

[0041] The inventors have found that, when DCI format 1_1 and DCI format 0_1 ​​configure the TDRA table, on the one hand, there is currently no method for using DCI format 1_1 and DCI format 0_1 ​​for SPS retransmission and CG retransmission, respectively, and on the other hand, assuming that the DCI format 1_1 and DCI format 0_1 ​​are used for SPS activation and retransmission, and CG activation and retransmission, respectively, according to the above prior art and discussion, the SPS PDSCH (or the PDSCH corresponding to the activated SPS) activated by the DCI format 1_1 and DCI format 0_1, or the PDSCH corresponding to the activated SPS, ... It has been found that for data retransmissions corresponding to SPS or CG scheduled by 0_1 (carried by dynamically scheduled PDSCH and PUSCH, respectively), it is not possible to determine whether / how to support aggregation / repetition, that is, under the assumption, there is currently no definitive solution for whether / how to support aggregation / repetition, and the terminal device is unable to determine whether an aggregation / repetition scheme is adopted, and therefore data may not be received or transmitted correctly.

[0042] The present application has been provided to address the above issues.

[0043] In the embodiment of the present application, the DCI needs to indicate the time domain resource of the PDSCH / PUSCH when scheduling the PDSCH / PUSCH or activating the SPS / CG. Generally, the DCI includes an information field for indicating the time domain resource of the PDSCH / PUSCH, which indicates the time domain resource of the PDSCH / PUSCH according to an applied (or corresponding) time domain resource allocation table, (TDRA) table (or referred to as PDSCH / PUSCH TDRA, or simply referred to as TDRA table). The information field is, for example, a time domain resource assignment field. Specifically, the information field may indicate an index in the TDRA table of the time domain resource assignment configuration (or simply referred to as TDRA configuration). For example, the TDRA table is a TDRA table applied to the DCI, and the information field indicates the time domain resource of the PDSCH by indicating an index (row index, for example, the value of the row index is 1 or more) corresponding to a TDRA configuration in the TDRA table applied to the DCI; in other words, the DCI schedules the PDSCH by indicating a TDRA configuration in the TDRA table applied to it. For example, a value m (assuming m is an integer 0 or more) of the information field of the DCI corresponds to a TDRA configuration indicating that the index of the TDRA table applied to the DCI is m+1 (i.e., the m+1th row). The time domain resource allocation table is predefined or configured by RRC signaling. When the TDRA table is configured by RRC signaling, for example, the index value corresponding to the m+1th TDRA configuration configured by the RRC signaling is m+1, that is, when the value of the information field is m, it corresponds to the m+1th TDRA configuration configured by the RRC signaling.

[0044] In the embodiment of the present application, the time domain resource allocation table includes at least one row, and hereinafter, for convenience of description, one row is referred to as one TDRA configuration, that is, the TDRA table includes at least one TDRA configuration. One TDRA configuration includes at least one time domain resource configuration (or referred to as PDSCH / PUSCH time domain resource configuration), which at least includes a symbol position (start symbol+length) configuration within a slot. In addition, one PDSCH / PUSCH TDRA configuration may further include at least one slot offset (for example, referred to as K0) configuration, where K0 is the slot offset between PDSCH / PUSCH and PDCCH / PUCCH, and the K0 configuration is included in the PDSCH / PUSCH time domain resource configuration or is not included in the PDSCH / PUSCH time domain resource configuration. The one TDRA configuration may further include other information included in the PDSCH / PUSCH time domain resource configuration or not included in the PDSCH / PUSCH time domain resource configuration, and the embodiments of the present application are not limited thereto. Here, the symbol position configuration in the slot includes, for example, a start and length indicator (SLIV), and the SLIV corresponds to a valid combination of a starting symbol (S) and a length (L), or corresponds to, for example, a starting symbol configuration and a length configuration, and the starting symbol configuration and the length configuration are a valid combination.

[0045] In some embodiments, to support scheduling of multiple PDSCHs / PUSCHs using one DCI, new RRC signaling (e.g., pdsch-TimeDomainAllocationListForMultiPDSCH or pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for PDSCH, and pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainAllocationListForMultiPUSCH-r17 for PUSCH) may support configuring a time domain resource allocation table to support scheduling of multiple (i.e., multiple) PDSCHs / PUSCHs using one DCI, where the time domain resource allocation table includes at least one time domain resource allocation configuration for scheduling multiple (i.e., multiple) PDSCHs / PUSCHs, and the time domain resource allocation configuration includes, for example, multiple SLIVs corresponding to each PDSCH / PUSCH.

[0046] In some embodiments, the time domain resource allocation configuration includes one time domain offset K0 configuration, where K0 represents a slot offset between an initial PDSCH / PUSCH and a PDCCH / PUCCH carrying DCI that schedules the PDSCH / PUSCH.

[0047] In some embodiments, the time domain resource allocation configuration includes multiple (i.e., multiple) K0 configurations. For example, the configuration includes multiple K0s corresponding to one PDSCH / PUSCH, each K0 representing a slot offset between a corresponding PDSCH / PUSCH and a PDCCH / PUCCH for scheduling the PDSCH / PUSCH, or the K0s may be included in the PDSCH / PUSCH time domain resource configuration and have a one-to-one correspondence with each SLIV, thereby determining the slot positions of multiple PDSCHs / PUSCHs in order.

[0048] In some embodiments, when one time domain resource allocation configuration is configured to schedule multiple PDSCH / PUSCHs in consecutive slots, the configuration includes one time domain offset K0 configuration, where K0 represents, for example, a slot offset between a first PDSCH / PUSCH and a PDCCH / PUCCH carrying DCI for scheduling the PDSCH / PUSCH.When one time domain resource allocation configuration is used to schedule multiple PDSCHs / PUSCHs in non-consecutive slots, the time domain resource allocation configuration includes multiple (i.e., multiple) time domain offset K0 configurations. For example, the configuration may include multiple K0s each corresponding to one PDSCH / PUSCH, each representing a slot offset between a corresponding PDSCH / PUSCH and a PDCCH / PUCCH for scheduling the PDSCH / PUSCH; alternatively, the K0s may be included in the PDSCH / PUSCH time domain resource configuration and have a one-to-one correspondence with each SLIV, thereby determining the slot positions of multiple PDSCHs / PUSCHs in order.

[0049] In some embodiments, when the TDRA table is configured for the downlink, the TDRA table applies to / supports DCI format 1_1. When the TDRA table is configured for the uplink, the TDRA table applies to / supports DCI format 0_1. The TDRA table is configured separately for the downlink and the uplink.

[0050] In some embodiments, the terminal device determines a time domain resource allocation table to be applied to a DCI (or a DCI with DL grant / assignment). The terminal device may further determine a time domain resource allocation table to be applied to the DCI based on a first list, where one column of the first list corresponds to the above-mentioned indication information (e.g., pdsch-TimeDomainAllocationListForMultiPDSCH or pdsch-TimeDomainAllocationListForMultiPDSCH-r17 for PDSCH, pusch-TimeDomainAllocationListForMultiPUSCH or pusch-TimeDomainAllocationListForMultiPUSCH-r17 for PUSCH) for setting a TDRA table to support scheduling multiple PDSCHs / PUSCHs by one DCI. The indication information is included in, for example, PDSCH / PUSCH-Config / . That is, the terminal device determines a PDSCH / PUSCH time domain resource allocation table applied to DCI for scheduling PDSCH / PUSCH based on the first list from a PDSCH / PUSCH time domain resource allocation (TDRA) table that is predefined or set by higher layer signaling. Taking DCI as DCI formats 1_0 and 1_1 as an example, the following Table 1 is an example of the first list.

[0051] Table 1: Applicable PDSCH time domain resource allocation for DCI format 1_0 and DCI format 1_1

[0052] [Table 1] TIFF2025504210000003.tif97170 In the embodiment of the present application, the DCI indicates multiple (i.e., multiple) PDSCH / PUSCHs, which means that the DCI (or the second information field in the DCI) indicates a time domain resource allocation configuration for scheduling the multiple PDSCH / PUSCHs. The time domain resource allocation configuration has already been described, so the description is omitted here.

[0053] In the embodiment of the present application, the DCI scheduling multiple (i.e., multiple) PDSCH / PUSCH means that the DCI indicates multiple PDSCH / PUSCH, or that the multiple PDSCH / PUSCHs indicated by the DCI include multiple valid PDSCH / PUSCHs, or that the multiple PDSCH / PUSCHs indicated by the DCI indicate a PDSCH / PUSCH with a corresponding HARQ process (or HARQ process ID). Here, the valid PDSCH and / or the PDSCH with the corresponding HARQ process means, for example, a PDSCH that does not overlap with a semi-statically configured uplink symbol, and / or a dynamically configured uplink symbol, and / or a semi-statically configured symbol with uplink transmission, and / or a reserved symbol, and / or an interval symbol. An active PUSCH and / or a PUSCH with a corresponding HARQ process means, for example, a PUSCH that does not overlap with a semi-statically configured downlink symbol, and / or a symbol corresponding to an SSB, and / or a symbol corresponding to CORSET#0, and / or a dynamically configured downlink symbol, and / or a symbol where a semi-statically configured downlink transmission exists, and / or a reserved symbol, and / or an interval symbol. Here, an active PDSCH / PUSCH and a PDSCH / PUSCH with a corresponding HARQ process may be the same or different.For different cases, for example, a valid PDSCH means, for example, a PDSCH that does not overlap with semi-statically configured uplink symbols, a valid PUSCH means, for example, a PUSCH that does not overlap with semi-statically configured downlink symbols, and / or symbols corresponding to SSBs, and / or symbols corresponding to CORSET#0, a PDSCH with a corresponding HARQ process means, for example, a PDSCH that does not overlap with semi-statically configured uplink symbols, and / or symbols corresponding to SSBs, and / or symbols corresponding to CORSET#0, and / or dynamically configured downlink symbols, and a PUSCH with a corresponding HARQ process means, for example, a PUSCH that does not overlap with semi-statically configured downlink symbols, and / or symbols corresponding to SSBs, and / or symbols corresponding to CORSET#0, and / or dynamically configured downlink symbols. In other words, if the PDSCH indicated by the DCI overlaps with a semi-statically configured uplink symbol, and / or a dynamically configured uplink symbol, and / or a symbol where a semi-statically configured uplink transmission exists, and / or a reserved symbol, and / or an interval symbol, the PDSCH is an invalid PDSCH, and / or the PDSCH does not have a corresponding HARQ process (or a HARQ process ID).Furthermore, for example, if the PUSCH indicated by the DCI overlaps with a semi-statically configured downlink symbol, and / or a symbol corresponding to an SSB, and / or a symbol corresponding to CORSET#0, and / or a dynamically configured downlink symbol, and / or a symbol where a semi-statically configured downlink transmission exists, and / or a reserved symbol, and / or an interval symbol, the PUSCH is an invalid PUSCH, and / or the PUSCH does not have a corresponding HARQ process (or a HARQ process ID).

[0054] For example, assuming that a valid PDSCH and / or a PDSCH with a corresponding HARQ process means a PDSCH that does not overlap with a semi-statically configured uplink symbol, if a PDSCH overlaps / collides with a semi-statically configured uplink symbol, the PDSCH does not have a corresponding HARQ process (or HARQ process ID). Normally, the base station does not transmit the PDSCH, and the UE does not receive the PDSCH. Conversely, if a PDSCH does not overlap / collide with a semi-statically configured uplink symbol, the PDSCH has a corresponding HARQ process (or HARQ process ID).

[0055] Figure 20 is a schematic diagram of a slot structure, and assumes that one slot contains 14 symbols. Figure 21 is a schematic diagram of a frame structure, and assumes that one frame contains 10 subframes, and that one subframe contains different numbers of slots according to different subcarrier spacings (SCS). The subcarrier spacings in Figure 21 are merely examples, and are not limiting.

[0056] FIG. 22 is a schematic diagram of a time domain resource in which a PDCCH / DCI for activating an SPS exists, and a time domain resource of a PDSCH indicated by the PDCCH / DCI for activating an SPS. In FIG. 22, it is assumed that the PDSCH is not repeated. FIG. 23 is a schematic diagram of a time domain resource in which a DCI format 1_1 for activating an SPS exists, and a PDSCH activated by the DCI, and in FIG. 23, it is assumed that the PDSCH is repeated based on the pdsch-AggregationFactor in the pdsch-Config. FIG. 24 is a schematic diagram of a DCI format 1_1 for scheduling retransmission for an SPS, and a PDSCH scheduled by the DCI, and in FIG. 24, it is assumed that the PDSCH is repeated based on the pdsch-AggregationFactor in the pdsch-Config. Figure 25 is a schematic diagram of slots in which DCI format 1_1 for activating SPS exists, slots in which SPS PDSCH activated by DCI format 1_1 exists, and corresponding HARQ process IDs. Figure 26 is another schematic diagram of HARQ process IDs corresponding to SPS PDSCHs, in which it is assumed that there is only one SPS PDSCH (repeated or not repeated) in one period, and different periodic cycles correspond to different HARQ process IDs.

[0057] FIG. 27 is a schematic diagram of a time domain resource in which a PDCCH / DCI for activating a CG exists, and a time domain resource of a PUSCH indicated by the PDCCH / DCI for activating a CG, where it is assumed that the PUSCH is not repeated in FIG. 27. FIG. 28 is a schematic diagram of a time domain resource in which a DCI format 1_1 for activating a CG exists, and a PUSCH activated by the DCI, where it is assumed that the PUSCH is repeated based on the pusch-AggregationFactor in the pusch-Config in FIG. 28. FIG. 29 is a schematic diagram of a DCI format 1_1 for scheduling retransmission for a CG, and a PUSCH scheduled by the DCI, where it is assumed that the PUSCH is repeated based on the pusch-AggregationFactor in the pusch-Config in FIG. 29. FIG. 30 is a schematic diagram of a slot in which a DCI format 1_1 for activating a CG exists, a slot in which a CG PUSCH activated by the DCI format 1_1 exists, and a corresponding HARQ process ID. FIG. 31 is another schematic diagram of HARQ process IDs corresponding to CG PUSCHs, in which it is assumed that there is only one CG PUSCH (repeated or not) in one period, and different periodic cycles correspond to different HARQ process IDs.

[0058] Examples of the present application will now be described with reference to the drawings and specific embodiments.

[0059] In the embodiments of the present application, "when...", "in the case of...", "for the case of...", and "when..." indicate that it is based on a certain condition, some conditions or states, and these forms of expression are interchangeable. Furthermore, the "instruction" may be to explicitly include some information to perform notification, or to perform notification implicitly by some features, and the like. Furthermore, descriptions such as "DCI", "DCI format", and "DCI format" have the same meaning and are interchangeable. Furthermore, descriptions such as "may be scheduled", "can be scheduled", and "used for scheduling" have the same meaning and are interchangeable.

[0060] Example of the first aspect In the embodiment of the present application, a data receiving method is provided and described from the terminal device side.

[0061] FIG. 2 is a schematic diagram of a data receiving method according to an embodiment of the present application. As shown in FIG. 2, the method includes: 201: A terminal device receives first downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH); and 202: The terminal device receives one or more PDSCHs among the PDSCHs scheduled by the first DCI.

[0062] According to an embodiment of the present application, a terminal device receives one or more PDSCHs scheduled by a first DCI, thereby supporting scheduling of multiple PDSCHs by one DCI, and further supporting semi-static or semi-persistent scheduling of PDSCHs when one DCI (or DCI format) can schedule multiple PDSCHs, as well as supporting dynamic retransmission of data corresponding to the semi-static or semi-persistent scheduling.

[0063] In some embodiments, when a terminal device receives multiple PDSCHs among the PDSCHs scheduled by the first DCI, the data (i.e., the transport blocks TB) carried by different PDSCHs among the multiple PDSCHs are different, and thus one DCI can support indicating transmission by different transport blocks.

[0064] In some embodiments, the first DCI is DCI format 1_1, ie, the network device schedules multiple PDSCHs according to DCI format 1_1.

[0065] In some embodiments, the first DCI includes one NDI (New Data Indication) field or two NDI fields, and when the first DCI includes two NDI fields, each NDI field corresponds to one TB. For example, the first DCI includes a first NDI field and / or a second NDI field, and when the first DCI includes a first NDI field and a second NDI field, the first NDI field and the second NDI field correspond to the first TB and the second TB, respectively. Thus, the TB may be indicated via the NDI field.

[0066] In the above embodiment, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0067] In some embodiments, when the CRC of the first DCI is scrambled by the CS-RNTI, the number of bits included in the first NDI field and / or the second NDI field is: The maximum number of PDSCHs that can be scheduled by the first DCI (i.e., the maximum number of SLIVs included in one row in the TDRA table corresponding to the first DCI); The number of PDSCHs scheduled by the first DCI (i.e., the number of SLIVs included in the row indicated by the first DCI), and It may be determined based on at least one of the number of valid PDSCHs scheduled by the first DCI (ie, the number of valid SLIVs included in the row indicated by the first DCI).

[0068] Thus, the first NDI field and / or the second NDI field may include one bit or multiple bits, specifically depending on at least one of the above determining factors.

[0069] In some other embodiments, when the CRC of the first DCI is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field only have one bit. For example, when two TBs are configured, the first DCI includes one NDI field, and the NDI field is one bit, or the first DCI includes two NDI fields, and the number of bits of the NDI field corresponding to each TB is 1. In this embodiment, the number of bits of the NDI field does not depend on the determining factor of the above embodiment.

[0070] In some embodiments, one or more rows in the TDRA table corresponding to a first DCI include multiple SLIVs corresponding to multiple PDSCHs, thereby achieving scheduling of multiple PDSCHs by the first DCI.

[0071] In the above embodiment, in some embodiments, the first DCI is not used to schedule the retransmission of the SPS, i.e., the terminal device does not want the CRC of the first DCI to be scrambled by the CS-RNTI. In some embodiments, the value of the first NDI field and / or the second NDI field of the first DCI is 1. In some embodiments, the first DCI schedules multiple PDSCHs. In some embodiments, the first DCI schedules multiple valid PDSCHs. In some embodiments, the NDI field (the first NDI field and / or the second NDI field) of the first DCI includes multiple bits with a value of 1. In some embodiments, the HARQ process ID corresponding to the multiple PDSCHs scheduled by the first DCI is one of one or more HARQ process IDs for the SPS configuration. In some embodiments, the HARQ process ID corresponding to the one or more PDSCHs scheduled by the first DCI is not one of one or more HARQ process IDs for the SPS configuration. The various embodiments described above may be implemented individually or in any combination.

[0072] In the above embodiment, the value of the first NDI field and / or the second NDI field is 1, but is not limited thereto.

[0073] The first NDI field includes one bit, and the value of the one bit is 1; or The first NDI field includes a plurality of bits, and one or more specific bit values ​​of the first NDI field are 1, or at least one bit value of the first NDI field is 1, or all bit values ​​of the first NDI field are 1, or The second NDI field includes one bit, and the value of the one bit is 1; or The second NDI field includes a plurality of bits, and one or more specific bit values ​​of the second NDI field are 1, or at least one bit value of the second NDI field is 1, or all bit values ​​of the second NDI field are 1.

[0074] In some embodiments of the present application, the CRC of the first DCI is scrambled by the CS-RNTI, the first DCI schedules only one PDSCH (i.e., the first DCI indicates a row in the corresponding TDRA table that contains one SLIV), and the terminal device receives only the one PDSCH.

[0075] For example, when the above TDRA table is configured for DCI format 1_1 (first DCI), when a UE receives DCI format 1_1 in which the CRC is scrambled by the CS-RNTI and NDI=1 (in the case of two TBs, each TB corresponds to one NDI field, and all are 1 or the NDI field corresponding to one of them (e.g., the first TB) is 1), the DCI can only indicate a row including one SLIV and cannot indicate a row including multiple SLIVs. That is, the DCI can only indicate or schedule one PDSCH.

[0076] In this example, the HARQ process ID indicated in the DCI may correspond to the PDSCH. The HARQ process ID may be in the HARQ process group for SPS configuration, but the present application is not limited thereto, and the HARQ process ID indicated in the DCI may have other embodiments, specifically, as mentioned above, the description is omitted here.

[0077] In some embodiments of the present application, the CRC of the first DCI is scrambled by the CS-RNTI, and the first DCI schedules multiple PDSCHs (i.e., the first DCI indicates a row in a corresponding TDRA table that includes multiple SLIVs).

[0078] In the above embodiment, the terminal device HARQ process ID corresponding to PDSCH, The bit value of the NDI field corresponding to the PDSCH, and Based on at least one of whether the PDSCH collides with a semi-statically configured uplink symbol, The terminal device may determine whether to receive a PDSCH among the multiple PDSCHs scheduled by the first DCI. For example, the terminal device receives only one PDSCH among the multiple PDSCHs based on whether the PDSCH collides with a semi-statically configured uplink symbol.

[0079] In this example, the one PDSCH may be the first PDSCH or the last PDSCH among the above-mentioned multiple PDSCHs, may be the only valid PDSCH among the above-mentioned multiple PDSCHs, may be the only PDSCH among the above-mentioned multiple PDSCHs whose corresponding NDI field value is 1, or may be the only PDSCH among the above-mentioned multiple PDSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration. The present application is not limited thereto, and the one PDSCH may be another one or any combination of the above.

[0080] This will be described below with a concrete example.

[0081] When the above TDRA table is configured for DCI format 1_1 (first DCI), when the UE receives DCI format 1_1 in which CRC is scrambled by CS-RNTI and NDI=1 or "1"s (for the case of two TBs, each TB corresponds to one NDI field, and all are 1 or "1"s, or the NDI field corresponding to one of them (e.g., the first TB) is 1 or "1"s) and indicates a row including multiple SLIVs, i.e., the DCI may indicate or schedule multiple PDSCHs. The UE receives only one of the PDSCHs, for example, the first PDSCH or the last PDSCH on the time series, and / or the only valid PDSCH (e.g., a PDSCH that does not collide with a semi-statically configured uplink symbol), and / or the only PDSCH with a corresponding NDI bit of 1, and / or a PDSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for the SPS configuration.

[0082] In this example, the HARQ process ID indicated by the first DCI may correspond to the one PDSCH (regardless of whether the PDSCH is the first PDSCH), or the HARQ process ID indicated by the first DCI corresponds to the first valid PDSCH among the multiple PDSCHs, and the terminal device determines the HARQ process ID corresponding to the one PDSCH (regardless of whether the PDSCH is the first PDSCH) based on the HARQ process ID.

[0083] In this example, the HARQ process ID corresponding to the one PDSCH may be one of one or more HARQ process IDs for the SPS configuration, i.e., may be in a HARQ process ID group for the SPS configuration.

[0084] In this example, the one PDSCH may be a valid PDSCH.

[0085] In this example, the first PDSCH may be the first PDSCH scheduled by the first DCI, or the first valid PDSCH scheduled by the first DCI. Similarly, the last PDSCH may be the last PDSCH scheduled by the first DCI, or the last valid PDSCH scheduled by the first DCI. Here, the first PDSCH scheduled by the first DCI is also the PDSCH (valid PDSCH) corresponding to the first SLIV of the row indicated by the first DCI, and similarly, the last PDSCH scheduled by the first DCI is also the PDSCH (valid PDSCH) corresponding to the last SLIV of the row indicated by the first DCI.

[0086] In this example, only one valid PDSCH is received for the UE, i.e., the PDSCH indicated / scheduled by the DCI can only include one valid PDSCH, i.e., the UE does not want multiple valid PDSCHs indicated / scheduled in the DCI, and the UE receives only this one PDSCH.

[0087] In this example, for the UE, only one PDSCH with a corresponding NDI bit of 1 is received, and the NDI field of the DCI contains only one bit with a value of 1, i.e., the UE does not want the NDI field of the DCI to contain multiple bits with a value of 1. The UE receives only this one PDSCH.

[0088] In this example, the UE does not receive an invalid PDSCH, and the invalid PDSCH does not have a corresponding HARQ process ID.

[0089] In this example, for other (active) PDSCHs (if any), the UE does not receive or cancels reception of the other (active) PDSCHs, which may or may not correspond to a HARQ process ID (i.e., the UE determines or does not determine the HARQ process ID of the other (active) PDSCHs).

[0090] Further, for example, based on the HARQ process ID corresponding to the PDSCH, the terminal device only receives the PDSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for the SPS configuration.

[0091] This will be described below with a concrete example.

[0092] When the above TDRA table is configured for DCI format 1_1 (first DCI), when a UE receives DCI format 1_1 in which CRC is scrambled by CS-RNTI and NDI=1 or "1"s (in the case of two TBs, each TB corresponds to one NDI field, and all are 1 or "1"s, or the NDI field corresponding to one of them (e.g., the first TB) is 1 or "1"s), and indicates a row including multiple SLIVs, i.e., the DCI may indicate / schedule multiple PDSCHs. The UE receives only PDSCHs whose corresponding HARQ process IDs are in the HARQ process group for the SPS configuration.

[0093] In this example, the HARQ process ID indicated in the DCI corresponds to the first valid PDSCH, and the UE determines the HARQ process ID of the valid PDSCH based on the indication.

[0094] In this example, the UE does not receive a PDSCH whose corresponding HARQ process ID does not exist in the HARQ process group for the SPS configuration.

[0095] In this example, the UE does not receive the invalid PDSCH, and the invalid PDSCH does not have a corresponding HARQ process ID.

[0096] Furthermore, for example, based on the HARQ process ID corresponding to the PDSCH, the terminal device receives all valid PDSCHs among the above-mentioned multiple PDSCHs.

[0097] Here, in one example, the HARQ process IDs corresponding to all valid PDSCHs must be one of the one or more HARQ process IDs for the SPS configuration.

[0098] This will be described below with a concrete example.

[0099] When the above TDRA table is configured for DCI format 1_1 (first DCI), when a UE receives DCI format 1_1 in which CRC is scrambled by CS-RNTI and NDI=1 or "1"s (in the case of two TBs, each TB corresponds to one NDI field, and all are 1 or "1"s, or the NDI field corresponding to one of them (e.g., the first TB) is 1 or "1"s), and indicates a row including multiple SLIVs, i.e., the DCI may indicate / schedule multiple PDSCHs. All HARQ process ID(s) corresponding to valid PDSCH(s) included in multiple PDSCHs indicated / scheduled by the DCI must be in the HARQ process group for the SPS configuration. That is, the UE does not want the HARQ process ID(s) corresponding to any one of the valid PDSCH(s) indicated / scheduled in the DCI to be in the HARQ process group for the SPS configuration.

[0100] Here, in another example, a PDSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for an SPS configuration and / or whose corresponding NDI field bit value is 0 is transmitted for the first time.

[0101] This will be described below with a concrete example.

[0102] When the above TDRA table is configured for DCI format 1_1 (first DCI), if the UE receives DCI format 1_1 with CRC scrambled by CS-RNTI and NDI=1 or "1"s and indicates a row including multiple SLIVs, i.e., the DCI may indicate / schedule multiple PDSCHs. The UE receives all valid PDSCH(s) and for PDSCHs whose corresponding HARQ process ID(s) are not in the HARQ process group for the SPS configuration, the UE considers it as the first transmission.

[0103] In this example, the HARQ process ID corresponding to only one or at least one of all valid PDSCHs is one of one or more HARQ process IDs for the SPS configuration, i.e., only one or at least one of the HARQ process ID(s) corresponding to the valid PDSCH(s) included in the multiple PDSCHs indicated / scheduled by the DCI is in the HARQ process group for the SPS configuration, where the valid PDSCH(s) corresponding to the HARQ process ID(s) are retransmitted.

[0104] In the above two examples, the HARQ process ID indicated by the DCI corresponds to the first valid PDSCH, and the UE determines the HARQ process ID of the valid PDSCHs based on the indication.

[0105] In the above two examples, the UE receives all valid PDSCH(s).

[0106] Further, for example, based on the bit value of the NDI field corresponding to the PDSCH, the terminal device receives only the PDSCH whose corresponding NDI field bit value is 1, or the terminal device receives all valid PDSCHs and considers that it will retransmit the PDSCH whose corresponding NDI field bit value is 1, and considers that it will transmit the PDSCH whose corresponding NDI field bit value is 0 for the first time.

[0107] This will be described below with a concrete example.

[0108] When the above TDRA table is configured for DCI format 1_1 (first DCI), the UE receives DCI format 1_1 whose CRC is scrambled by the CS-RNTI and indicates a row including multiple SLIVs, where the NDI bit corresponding to one or more SLIVs is 1 (for the case of two TBs, each TB corresponds to one NDI field, and the corresponding bits in the two NDI fields of the one or more SLIVs are all 1, or the corresponding bit in one of them (e.g., the first TB) is 1), i.e., the DCI may indicate or schedule multiple PDSCHs, and the NDI bit corresponding to one or more PDSCHs is 1).

[0109] In this example, the UE receives only PDSCHs corresponding to NDI bit=1, or alternatively, the UE receives all valid PDSCH(s) and for any PDSCHs with corresponding NDI bit=0, the UE considers them to be first-time transmissions.

[0110] In this example, the bit value of the NDI field corresponding to only one or at least one of all valid PDSCHs is 1.

[0111] In some embodiments of the present application, the terminal device may further receive a PDSCH configuration (pdsch-Config) including a first configuration parameter (e.g., pdsch-AggregationFactor) for configuring the number of repetitions, and if the CRC of the first DCI is scrambled by the CS-RNTI, the first configuration parameter is applied to the first DCI. That is, when the above TDRA table is configured for DCI format 1_1 (first DCI), if the UE receives a PDSCH scheduled by a DCI format in which the CRC is scrambled by the CS-RNTI and NDI=1 or NDI=0, if the PDSCH configuration (pdsch-Config) includes pdsch-AggregationFactor, the number of repetitions is set by the pdsch-AggregationFactor.

[0112] In the above embodiment, the first configuration parameter is applied to the first DCI, which refers to the first configuration parameter being applied to one or more PDSCHs among the PDSCHs scheduled by the first DCI.

[0113] For example, each PDSCH scheduled by the first DCI is repeated a number of times set by the first configuration parameter, and / or each valid PDSCH scheduled by the first DCI is repeated a number of times set by the first configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first DCI that is to be received by the terminal device is repeated a number of times set by the first configuration parameter, and / or the first DCI schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the first configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first DCI, and the one PDSCH is repeated a number of times set by the first configuration parameter.

[0114] In some embodiments of the present application, the terminal device may further receive a PDSCH configuration (pdsch-Config) including a first configuration parameter (e.g., pdsch-AggregationFactor) for configuring the number of repetitions, and if the CRC of the first DCI is scrambled by the CS-RNTI, the first configuration parameter is not applied to the first DCI.

[0115] In the above embodiment, the first configuration parameter is not applied to the first DCI, which means that the first configuration parameter is not applied to any one of the PDSCHs scheduled by the first DCI.

[0116] For example, when the above TDRA table is set for DCI format 1_1 (first DCI), if the UE receives a PDSCH scheduled by a DCI format in which the CRC is scrambled by the CS-RNTI and NDI=1 or NDI=0, if the PDSCH configuration (pdsch-Config) includes a pdsch-AggregationFactor, the PDSCH is not repeated the number of times set by the pdsch-AggregationFactor. Here, if the first DCI adopts another DCI format (the TDRA table corresponding to another format is different from the above TDRA table, for example, each row in the TDRA table corresponding to another format includes only one SLIV), for example, DCI format 1_0 / 1_2, the PDSCH is repeated the number of times set by the pdsch-AggregationFactor.

[0117] In the above example, in one embodiment, the PDSCH scheduled by the first DCI is not repeated, regardless of whether the SPS configuration includes the pdsch-AggregationFactor.

[0118] In the above embodiment, in another embodiment, if the SPS configuration includes the pdsch-AggregationFactor, the PDSCH scheduled by the first DCI is repeated according to the pdsch-AggregationFactor.

[0119] In this embodiment, the terminal device may receive an SPS configuration including a second configuration parameter (eg, pdsch-AggregationFactor) for configuring the number of repetitions, where the second configuration parameter is applied to the first DCI.

[0120] In this embodiment, the second configuration parameter is applied to the first DCI, which refers to the second configuration parameter being applied to one or more of the PDSCHs scheduled by the first DCI.

[0121] For example, each PDSCH scheduled by the first DCI is repeated a number of times set by the second configuration parameter, and / or each valid PDSCH scheduled by the first DCI is repeated a number of times set by the second configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first DCI that should be received by the terminal device is repeated a number of times set by the second configuration parameter, and / or the first DCI schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first DCI, and the one PDSCH is repeated a number of times set by the second configuration parameter.

[0122] In this embodiment, the SPS configuration (sps-config) is the SPS configuration corresponding to the PDSCH (corresponding SPS PDSCH). For example, if only one sps-config is configured in the UE, the sps-config is the SPS configuration corresponding to the PDSCH (corresponding SPS PDSCH). Furthermore, for example, if the UE configures and activates only multiple SPS configurations, the UE determines the SPS configuration corresponding to the PDSCH (corresponding SPS PDSCH) based on, for example, the HARQ process ID corresponding to the PDSCH. Furthermore, for example, if the HARQ process ID corresponding to the PDSCH is shared by multiple SPS configurations, the pdsch-AggregationFactor refers to, for example, the largest pdsch-AggregationFactor included in the multiple SPS configurations.

[0123] In an embodiment of the present application, the SPS configuration may further include an information field (or fields) of the corresponding HARQ process ID range, such as nrofHARQ-Processes, harq-ProcID-Offset, etc., that is used by the base station to indicate / the UE to determine.

[0124] In the embodiments of the present application, with regard to aggregation / repetition of SPS PDSCH, in some embodiments, the terminal device may further receive a PDSCH configuration (pdsch-Config) including a first configuration parameter (e.g., pdsch-AggregationFactor) for setting the number of repetitions. Furthermore, the terminal device may further receive a second DCI for activating the SPS configuration, the first configuration parameter is applied to the second DCI, and one or more rows in the TDRA table corresponding to the second DCI include multiple SLIVs.

[0125] In the above embodiment, applying the first configuration parameter to the second DCI includes repeating an SPS PDSCH corresponding to the second DCI according to the first configuration parameter, where the SPS PDSCH corresponding to the second DCI refers to, for example, a PDSCH (SPS PDSCH) scheduled by an SPS configuration activated by the second DCI, or an SPS PDSCH activated by the second DCI.

[0126] For example, when the above TDRA table is set for DCI format 1_1 (second DCI), if pdsch-AggregationFactor is included in the PDSCH configuration (pdsch-Config) for a PDSCH scheduled by the SPS configuration and activated by DCI format 1_1 (i.e., SPS PDSCH), the PDSCH is repeated the number of times set by the pdsch-AggregationFactor. The SPS PDSCH does not have a corresponding PDCCH, and the PDCCH is a PDCCH that carries DCI for scheduling the PDSCH.

[0127] In the embodiment of the present application, with respect to aggregation / repetition of SPS PDSCH, in some other embodiments, the terminal device may further receive a PDSCH configuration (pdsch-Config) including a first configuration parameter (e.g., pdsch-AggregationFactor) for setting the number of repetitions. Furthermore, the terminal device may further receive a second DCI for activating the SPS configuration, where the first configuration parameter is not applied to the second DCI, and one or more rows in the TDRA table corresponding to the second DCI include multiple SLIVs.

[0128] In the above embodiment, the first configuration parameter is not applied to the second DCI, which means that the first configuration parameter is not applied to any one of the SPS PDSCHs corresponding to the second DCI.

[0129] For example, when the above TDRA table is set for DCI format 1_1 (second DCI), if the PDSCH configuration (pdsch-Config) includes pdsch-AggregationFactor for a PDSCH (i.e., SPS PDSCH) scheduled by the SPS configuration and activated by DCI format 1_1, the number of times set by the pdsch-AggregationFactor is repeated. The SPS PDSCH does not have a corresponding PDCCH, and the PDCCH is a PDCCH that carries a DCI for scheduling the PDSCH. Here, when the second DCI adopts another DCI format (the TDRA table corresponding to the other format is different from the above TDRA table, for example, each row in the TDRA table corresponding to the other format includes only one SLIV), for example, DCI format 1_0 / 1_2, etc., the number of times set by the pdsch-AggregationFactor is repeated.

[0130] In the above example, in one embodiment, the SPS PDSCH corresponding to the second DCI is not repeated, regardless of whether the SPS configuration includes the pdsch-AggregationFactor.

[0131] In the above embodiment, in another embodiment, if the SPS configuration includes the pdsch-AggregationFactor, the SPS PDSCH corresponding to the second DCI is repeated according to the pdsch-AggregationFactor.

[0132] In this embodiment, the terminal device may receive an SPS configuration including a second configuration parameter (eg, pdsch-AggregationFactor) for configuring the number of repetitions, where the second configuration parameter is applied to the second DCI.

[0133] In this embodiment, the second configuration parameter is applied to the second DCI, which refers to the second configuration parameter being applied to one or more of the SPS PDSCHs corresponding to the second DCI.

[0134] For example, each SPS PDSCH corresponding to the second DCI is repeated a number of times set by the second configuration parameter, and / or each valid SPS PDSCH corresponding to the second DCI is repeated a number of times set by the second configuration parameter, and / or each SPS PDSCH among the SPS PDSCHs corresponding to the second DCI that the terminal device should receive is repeated a number of times set by the second configuration parameter, and / or the second DCI corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second DCI, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0135] The above various embodiments are merely illustrative of the embodiments of the present application, and the present application is not limited thereto, and appropriate modifications may be further made based on the above various embodiments. For example, the above various embodiments may be used individually, or one or more of the above various embodiments may be combined.

[0136] In an embodiment of the present application, the terminal device may further receive a PDCCH / DCI for activating / deactivating SPS, for example, the terminal device validates the validity of the PDCCH / DCI by: 1. It is scrambled by the CS-RNTI (more specifically, the CRC corresponding to the DCI format is scrambled by the CS-RNTI); 2. Set the NDI field to "0", 3. If the DFI field is present, it shall be set to "0"; 4. For activation, if the PDSCH-to-HARQ_feedback timing indicator field is present, it cannot provide an inapplicable value (e.g., -1); and 5. (If the TDRA table applicable to the corresponding DCI format includes at least one row of TDRA configuration including multiple SLIV configurations or is DCI format 1_1) It may be confirmed according to at least one or more of the following that the TDRA configuration / row / row index indicated by the Time domain resource assignment field includes / corresponds to only one PDSCH / SLIV.

[0137] In an embodiment of the present application, with regard to SPS activation, if only one configuration for the SPS PDSCH is provided, the validity of the DCI may further depend on the HARQ process number field and the RV field.

[0138] Here, with regard to the RV field, when a TDRA table applied to a DCI format (for example, DCI format 1_1) corresponding to the DCI includes at least one row of TDRA configuration including multiple SLIV configurations, when the TDRA configuration indicated by the Time domain resource assignment field includes / supports only one PDSCH, the Redundancy version field of the DCI corresponding to one TB includes two bits. When one TB is configured in the DCI format, only one Redundancy version field is included in the DCI, and the bits of the Redundancy version field are all set to "0" or all set to "1". When two TBs are configured in the DCI format, the DCI includes Redundancy version fields (one-to-one correspondence) corresponding to each of the two TBs, and the bits of the Redundancy version field corresponding to each of the two TBs are all set to "0" or all set to "1". Or, all bits in the redundancy version field corresponding to one TB (e.g., the first TB) are set to "0", and all bits in the redundancy version field corresponding to another TB (e.g., the second TB) are set to "1". For example, (if the SPS supports only one TB), the first TB is enabled and the second TB is disabled, and all bits in the redundancy version field corresponding to the first TB are set to "0", and all bits in the redundancy version field corresponding to the second TB are set to "1". Furthermore, (if the SPS supports only two TBs), the bits in the redundancy version field corresponding to each of the two TBs are set to all "0" or all "1", as shown in Table 2 below.

[0139] [Table 2] Furthermore, when multiple configurations for SPS PDSCH are provided, the validity of the DCI further depends on the RV field, and the further description regarding the configuration of the RV field is the same as the above activation case for only one configuration for SPS PDSCH, as shown in Table 3 below.

[0140] [Table 3] Meanwhile, the HARQ process number field (for the case where multiple configurations for SPS PDSCH are provided) is used to indicate the SPS configuration index activated by the DCI, which may be associated / corresponding to one or multiple configurations for SPS PDSCH.

[0141] In an embodiment of the present application, regarding SPS deactivation, if only one configuration for SPS PDSCH is provided (or only one SPS PDSCH is configured), the validity of the DCI may further depend on the HARQ process number field, the RV field, the Modulation and coding scheme field, and the Frequency domain resource assignment field.

[0142] Here, with regard to the RV field, when a TDRA table applied to a DCI format (for example, DCI format 1_1) corresponding to the DCI includes at least one row of TDRA configuration including multiple SLIV configurations, if the TDRA configuration indicated by the DCI includes / supports only one PDSCH, the redundancy version field of the DCI corresponding to one TB includes two bits. When one TB is configured in the DCI format, only one redundancy version field is included in the DCI, and the bits of the redundancy version field are all set to "0" or all set to "1". When two TBs are configured in the DCI format, the DCI includes a redundancy version field (one-to-one correspondence) corresponding to each of the two TBs, and the bits of the redundancy version field corresponding to each of the two TBs are all set to "0" or all set to "1". As shown in Table 4 below.

[0143] [Table 4] When multiple configurations for SPS PDSCH are provided, the validity of the DCI further depends on the RV field, the Modulation and coding scheme field, and the Frequency domain resource assignment field, and the further description on the configuration of the RV field is the same as the above deactivation case for only one configuration for SPS PDSCH, as shown in Table 5 below.

[0144] [Table 5] Meanwhile, the HARQ process number field (for the case where multiple configurations for SPS PDSCH are provided) is used to indicate the SPS configuration index deactivated by the DCI, which may be associated / corresponding to one or multiple configurations for SPS PDSCH.

[0145] According to the method of the embodiment of the present application, it is possible to support scheduling of multiple PDSCHs by one DCI, and further, when one DCI (or DCI format) can schedule multiple PDSCHs, it is possible to support semi-static or semi-persistent scheduling of PDSCHs, as well as to support dynamic retransmission of data corresponding to semi-static or semi-persistent scheduling.

[0146] Example of the second aspect In the embodiments of the present application, a data scheduling method is provided and described from the network device side. This method is a process on the network device side corresponding to the method of the embodiment of the first aspect, and the same contents as those of the embodiment of the first aspect will not be described again.

[0147] 3 is a schematic diagram of a data scheduling method according to an embodiment of the present application. As shown in FIG. 3, the method includes: 301: The method includes a network device sending first downlink control information for scheduling one or more PDSCHs.

[0148] In some embodiments, when the network device transmits a plurality of PDSCHs among the PDSCHs scheduled by the first downlink control information, the data carried by different PDSCHs among the plurality of PDSCHs is different.

[0149] In some embodiments, the first downlink control information is in DCI format 1_1.

[0150] In some embodiments, the first downlink control information includes a first NDI field and / or a second NDI field, and when the first downlink control information includes a first NDI field and a second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0151] In some embodiments, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0152] In some embodiments, the number of bits included in the first NDI field and / or the second NDI field is: A maximum number of PDSCHs that can be scheduled by the first downlink control information; The number of PDSCHs scheduled by the first downlink control information, and The determination is based on at least one of the number of valid PDSCHs scheduled by the first downlink control information.

[0153] In some embodiments, when the CRC of the first downlink control information is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits, and when the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0154] In some embodiments, one or more rows in the TDRA table corresponding to the first downlink control information includes multiple SLIVs.

[0155] In some embodiments, the first downlink control information schedules one PDSCH, and / or the first NDI field and / or the second NDI field of the first downlink control information have a value of 1, and / or the first downlink control information schedules multiple PDSCHs, and / or the first downlink control information schedules multiple valid PDSCHs, and / or the NDI field of the first downlink control information includes multiple bits with a value of 1, and / or the HARQ process ID corresponding to the multiple PDSCHs scheduled by the first downlink control information is one of one or more HARQ process IDs for an SPS configuration, and / or the HARQ process ID corresponding to the one or more PDSCHs scheduled by the first downlink control information is not one of one or more HARQ process IDs for an SPS configuration.

[0156] In some embodiments, the CRC of the first downlink control information is scrambled by a CS-RNTI, and the first downlink control information schedules only one PDSCH.

[0157] In some embodiments, the CRC of the first downlink control information is scrambled by a CS-RNTI, the first downlink control information schedules a plurality of PDSCHs, and the network device transmits one PDSCH of the plurality of PDSCHs scheduled by the first downlink control information, or the network device transmits a PDSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration, or the network device transmits all valid PDSCHs of the plurality of PDSCHs scheduled by the first downlink control information, or the network device transmits a PDSCH whose corresponding NDI field has a bit value of 1, or the network device transmits all valid PDSCHs and considers a PDSCH whose corresponding NDI field has a bit value of 1 to be retransmitted and considers a PDSCH whose corresponding NDI field has a bit value of 0 to be transmitted for the first time.

[0158] In some embodiments, the one PDSCH is the first or last PDSCH of the multiple PDSCHs, and / or the one PDSCH is the only valid PDSCH of the multiple PDSCHs, and / or the one PDSCH is the only PDSCH of the multiple PDSCHs whose corresponding NDI field value is 1, and / or the one PDSCH is the only PDSCH of the multiple PDSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration.

[0159] In some embodiments, the HARQ process ID indicated by the first downlink control information corresponds to the one PDSCH, or the HARQ process ID indicated by the first downlink control information corresponds to a first valid PDSCH among the multiple PDSCHs, and the terminal device determines the HARQ process ID corresponding to the one PDSCH based on the HARQ process ID.

[0160] In some embodiments, the HARQ process ID corresponding to the one PDSCH is one of one or more HARQ process IDs for an SPS configuration.

[0161] In some embodiments, the one PDSCH is a valid PDSCH.

[0162] In some embodiments, the first PDSCH is the first PDSCH scheduled by the first downlink control information or the first valid PDSCH scheduled by the first downlink control information, and the last PDSCH is the last PDSCH scheduled by the first downlink control information or the last valid PDSCH scheduled by the first downlink control information.

[0163] In some embodiments, the HARQ process IDs corresponding to all the valid PDSCHs must be one of one or more HARQ process IDs for an SPS configuration.

[0164] In some embodiments, a PDSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for an SPS configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0165] In some embodiments, the HARQ process ID corresponding to only one or at least one of all the enabled PDSCHs is one of one or more HARQ process IDs for an SPS configuration.

[0166] In some embodiments, the bit value of the NDI field corresponding to only one or at least one of all valid PDSCHs is one.

[0167] In some embodiments, the method further comprises: The network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and The method further includes: a CRC of the first downlink control information is scrambled by a CS-RNTI; and the first configuration parameter is applied to the first downlink control information.

[0168] In some embodiments, applying the first configuration parameter to the first downlink control information includes applying the first configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0169] In some embodiments, each PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first downlink control information that is to be received by a terminal device is repeated a number of times set by the first configuration parameter, and / or the first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the first configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the first configuration parameter.

[0170] In some embodiments, the method further comprises: The network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and The method further includes: a CRC of the first downlink control information is scrambled by a CS-RNTI; and the first configuration parameter is not applied to the first downlink control information.

[0171] In some embodiments, not applying the first configuration parameter to the first downlink control information includes not applying the first configuration parameter to any of the PDSCHs scheduled by the first downlink control information.

[0172] In some embodiments, the method further comprises: the network device sending an SPS configuration including a second configuration parameter for configuring a number of repetitions; and The method further includes applying the second configuration parameter to the first downlink control information.

[0173] In some embodiments, applying the second configuration parameter to the first downlink control information includes applying the second configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0174] In some embodiments, each PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first downlink control information that is to be received by a terminal device is repeated a number of times set by the second configuration parameter, and / or the first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the second configuration parameter.

[0175] In some embodiments, the method further comprises: The network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and The network device further includes sending second downlink control information for activating an SPS configuration, the first configuration parameter being applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information including multiple SLIVs.

[0176] In some embodiments, applying the first configuration parameter to the second downlink control information includes repeating an SPS PDSCH corresponding to the second downlink control information in response to the first configuration parameter.

[0177] In some embodiments, the method further comprises: The network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and The network device further includes sending second downlink control information for activating an SPS configuration, the first configuration parameter is not applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information includes multiple SLIVs.

[0178] In some embodiments, not applying the first configuration parameter to the second downlink control information includes not applying the first configuration parameter to any one of the SPS PDSCHs corresponding to the second downlink control information.

[0179] In some embodiments, the method further comprises: the network device sending an SPS configuration including a second configuration parameter for configuring a number of repetitions; and The second configuration parameter is further applied to the second downlink control information.

[0180] In some embodiments, applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0181] In some embodiments, each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information that should be received by the terminal device is repeated a number of times set by the second configuration parameter, and / or the second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0182] The above various embodiments are merely illustrative of the embodiments of the present application, and the present application is not limited thereto, and appropriate modifications may be further made based on the above various embodiments. For example, the above various embodiments may be used individually, or one or more of the above various embodiments may be combined.

[0183] According to the method of the embodiment of the present application, it is possible to support scheduling of multiple PDSCHs by one DCI, and further, when one DCI (or DCI format) can schedule multiple PDSCHs, it is possible to support semi-static or semi-persistent scheduling of PDSCHs, and it is possible to support dynamic retransmission of data corresponding to semi-static or semi-persistent scheduling. Furthermore, it is possible to increase the flexibility of configuration and resource scheduling for network devices.

[0184] Example of the third aspect In the embodiment of the present application, a data transmission method is provided and described from the terminal device side.

[0185] FIG. 4 is a schematic diagram of a data transmission method according to an embodiment of the present application. As shown in FIG. 4, the data transmission method according to an embodiment of the present application includes: 401: A terminal device receives third downlink control information for scheduling a PUSCH; and 402: The terminal device transmits one or more PUSCHs among the PUSCHs scheduled by the third downlink control information.

[0186] According to an embodiment of the present application, a terminal device transmits one or more PUSCHs scheduled by a third DCI, thereby supporting scheduling of multiple PUSCHs by one DCI, and further supporting semi-static or semi-persistent scheduling of PUSCHs when one DCI (or DCI format) can schedule multiple PUSCHs, as well as supporting dynamic retransmission of data corresponding to semi-static or semi-persistent scheduling.

[0187] In some embodiments, when a terminal device transmits multiple PUSCHs among the PUSCHs scheduled by the third DCI, the data (i.e., the transport block TB) carried by different PUSCHs among the multiple PUSCHs is different. Thus, one DCI can support indicating transmission by different transport blocks.

[0188] In some embodiments, the third DCI is DCI format 0_1, ie, the network device schedules multiple PUSCHs according to DCI format 0_1.

[0189] In some embodiments, the third DCI includes one NDI (New Data Indication) field or two NDI fields, and when the third DCI includes two NDI fields, each NDI field corresponds to one TB. For example, the third DCI includes a first NDI field and / or a second NDI field, and when the third DCI includes a first NDI field and a second NDI field, the first NDI field and the second NDI field correspond to the first TB and the second TB, respectively. Thus, a TB may be indicated via the NDI field.

[0190] In the above embodiment, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0191] In some embodiments, when the CRC of the third DCI is scrambled by the CS-RNTI, the number of bits included in the first NDI field and / or the second NDI field is: The maximum number of PUSCHs that can be scheduled by the third DCI (i.e., the maximum number of SLIVs included in one row in the TDRA table corresponding to the third DCI); The number of PUSCHs scheduled by the third DCI (i.e., the number of SLIVs included in the row indicated by the third DCI), and It may be determined based on at least one of the number of valid PUSCHs scheduled by the third DCI (i.e., the number of valid SLIVs included in the row indicated by the third DCI).

[0192] Thus, the first NDI field and / or the second NDI field may include one bit or multiple bits, specifically depending on at least one of the above determining factors.

[0193] In some other embodiments, when the CRC of the 3rd DCI is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field only have one bit. For example, when two TBs are configured, the 3rd DCI includes one NDI field, and the NDI field is one bit, or the 3rd DCI includes two NDI fields, and the number of bits of the NDI field corresponding to each TB is 1. In this embodiment, the number of bits of the NDI field does not depend on the determining factor of the above embodiment.

[0194] In some embodiments, one or more rows in the TDRA table corresponding to a third DCI include multiple SLIVs corresponding to multiple PUSCHs, thereby realizing scheduling of multiple PUSCHs by the third DCI.

[0195] In the above embodiment, in some embodiments, the 3rd DCI is not used to schedule the retransmission of the CG, i.e., the terminal device does not want the CRC of the 3rd DCI to be scrambled by the CS-RNTI. In some embodiments, the first NDI field and / or the second NDI field of the 3rd DCI have a value of 1. In some embodiments, the 3rd DCI schedules multiple PUSCHs. In some embodiments, the 3rd DCI schedules multiple valid PUSCHs. In some embodiments, the NDI field (the first NDI field and / or the second NDI field) of the 3rd DCI includes multiple bits with a value of 1. In some embodiments, the HARQ process ID corresponding to the multiple PUSCHs scheduled by the 3rd DCI is one of the one or more HARQ process IDs for the CG configuration. In some embodiments, the HARQ process ID corresponding to the one or more PUSCHs scheduled by the 3rd DCI is not one of the one or more HARQ process IDs for the CG configuration. The various embodiments described above may be implemented individually or in any combination.

[0196] In the above embodiment, the value of the first NDI field and / or the second NDI field is 1, but is not limited thereto.

[0197] The first NDI field includes one bit, and the value of the one bit is 1; or The first NDI field includes a plurality of bits, and one or more specific bit values ​​of the first NDI field are 1, or at least one bit value of the first NDI field is 1, or all bit values ​​of the first NDI field are 1, or The second NDI field includes one bit, and the value of the one bit is 1; or The second NDI field includes a plurality of bits, and one or more specific bit values ​​of the second NDI field are 1, or at least one bit value of the second NDI field is 1, or all bit values ​​of the second NDI field are 1.

[0198] In some embodiments of the present application, the CRC of the third DCI is scrambled by the CS-RNTI, the third DCI schedules only one PUSCH (i.e., the third DCI indicates a row in the corresponding TDRA table that contains one SLIV), and the terminal device transmits only the one PUSCH.

[0199] For example, when the above TDRA table is configured for DCI format 0_1 ​​(third DCI), when a UE receives DCI format 0_1 ​​in which the CRC is scrambled by the CS-RNTI and NDI=1 (in the case of two TBs, each TB corresponds to one NDI field, and the NDI field corresponding to one of them (e.g., the first TB) is 1), the DCI can only indicate a row including one SLIV, and cannot indicate a row including multiple SLIVs. That is, the DCI can only indicate or schedule one PUSCH.

[0200] In this example, the HARQ process ID indicated in the DCI may correspond to the PUSCH. The HARQ process ID may be in the HARQ process group for the CG configuration, but the present application is not limited thereto, and the HARQ process ID indicated in the DCI may have other embodiments, specifically, as mentioned above, the description is omitted here.

[0201] In some embodiments of the present application, the CRC of the third DCI is scrambled by the CS-RNTI, and the third DCI schedules multiple PUSCHs (i.e., the third DCI indicates a row in the corresponding TDRA table that contains multiple SLIVs).

[0202] In the above embodiment, the terminal device HARQ process ID corresponding to PUSCH, The bit value of the NDI field corresponding to the PUSCH, Whether the PUSCH collides with the semi-statically configured downlink symbol; Whether PUSCH will collide with SSB, and Based on at least one of whether the PUSCH collides with CORESET#0, It determines whether or not to transmit a PUSCH among a plurality of PUSCHs scheduled by the third DCI.

[0203] For example, based on whether the PUSCH collides with a semi-statically configured downlink symbol, the terminal device transmits only one PUSCH of the multiple PUSCHs.

[0204] In this example, the one PUSCH may be the first PUSCH or the last PUSCH of the above-mentioned multiple PUSCHs, may be the only valid PUSCH of the above-mentioned multiple PUSCHs, may be the only PUSCH of the above-mentioned multiple PUSCHs whose corresponding NDI field value is 1, or may be the only PUSCH of the above-mentioned multiple PUSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration. The present application is not limited thereto, and the above-mentioned one PUSCH may be another one or any combination of the above.

[0205] In some embodiments, the SSB refers to an SSB configured by RRC signaling (eg, ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon).

[0206] In some embodiments, CORECET#0 is configured by the MIB.

[0207] This will be described below with a concrete example.

[0208] When the above TDRA table is configured for DCI format 0_1 ​​(third DCI), when the UE receives DCI format 0_1 ​​in which CRC is scrambled by CS-RNTI and NDI=1 or "1"s (for two TBs, each TB corresponds to one NDI field, and all are 1 or "1"s, or the NDI field corresponding to one of them (e.g., the first TB) is 1 or "1"s) and indicates a row including multiple SLIVs, that is, the DCI may indicate or schedule multiple PUSCHs. The UE transmits only one of the PUSCHs, for example, the first PUSCH or the last PUSCH on the time series, and / or the only valid PUSCH (e.g., a PUSCH that does not collide with a semi-statically configured uplink symbol), and / or the only PUSCH with the corresponding NDI bit set to 1, and / or the PUSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for the CG configuration.

[0209] In this example, the HARQ process ID indicated by the third DCI may correspond to the one PUSCH (regardless of whether the PUSCH is the first PUSCH), or the HARQ process ID indicated by the third DCI corresponds to the first valid PUSCH among the multiple PUSCHs, and the terminal device determines the HARQ process ID corresponding to the one PUSCH (regardless of whether the PUSCH is the first PUSCH) based on the HARQ process ID.

[0210] In this example, the HARQ process ID corresponding to the one PUSCH may be one of one or more HARQ process IDs for the CG configuration, i.e., may be in a HARQ process ID group for the CG configuration.

[0211] In this example, the one PUSCH may be a valid PUSCH.

[0212] In this example, the first PUSCH may be the first PUSCH scheduled by the third DCI, or the first valid PUSCH scheduled by the third DCI. Similarly, the last PUSCH may be the last PUSCH scheduled by the third DCI, or the last valid PUSCH scheduled by the third DCI. Here, the first PUSCH scheduled by the third DCI is also the PUSCH (valid PUSCH) corresponding to the first SLIV of the row indicated by the third DCI, and similarly, the last PUSCH scheduled by the third DCI is also the PUSCH (valid PUSCH) corresponding to the last SLIV of the row indicated by the third DCI.

[0213] In this example, only one valid PUSCH is transmitted to the UE, i.e., the PUSCH indicated / scheduled by the DCI can only include one valid PUSCH, i.e., the UE does not want multiple valid PUSCHs indicated / scheduled in the DCI. The UE transmits only this one PUSCH.

[0214] In this example, the UE transmits only one PUSCH with a corresponding NDI bit of 1, and the NDI field of the DCI contains only one bit with a value of 1, i.e., the UE does not want the NDI field of the DCI to contain multiple bits with a value of 1. The UE transmits only this one PUSCH.

[0215] In this example, the UE does not transmit an invalid PUSCH, and the invalid PUSCH does not have a corresponding HARQ process ID.

[0216] In this example, for other (valid) PUSCHs (if any), the UE either does not transmit or cancels the transmission of the other (valid) PUSCHs, which may or may not correspond to a HARQ process ID (i.e., the UE either determines or does not determine a HARQ process ID for the other (valid) PUSCHs).

[0217] Further, for example, based on the HARQ process ID corresponding to the PUSCH, the terminal device transmits only the PUSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for the CG configuration.

[0218] This will be described below with a concrete example.

[0219] When the above TDRA table is configured for DCI format 0_1 ​​(third DCI), when the UE receives DCI format 0_1 ​​in which the CRC is scrambled by the CS-RNTI and NDI=1 or "1"s (in the case of two TBs, each TB corresponds to one NDI field, and all are 1 or "1"s, or the NDI field corresponding to one of them (e.g., the first TB) is 1 or "1"s), and indicates a row including multiple SLIVs, i.e., the DCI may indicate / schedule multiple PUSCHs. The UE transmits only PUSCHs whose corresponding HARQ process IDs are in the HARQ process group for the CG configuration.

[0220] In this example, the HARQ process ID indicated in the DCI corresponds to the first valid PUSCH, and the UE determines the HARQ process ID of the valid PUSCH based on the indication.

[0221] In this example, the UE does not transmit a PUSCH whose corresponding HARQ process ID is not present in the HARQ process group for the CG configuration.

[0222] In this example, the UE does not transmit an invalid PUSCH, and the invalid PUSCH does not have a corresponding HARQ process ID.

[0223] Furthermore, for example, based on the HARQ process ID corresponding to the PUSCH, the terminal device transmits all valid PUSCHs among the above-mentioned multiple PUSCHs.

[0224] Here, in one example, the HARQ process IDs corresponding to all valid PUSCHs must be one of the one or more HARQ process IDs for the CG configuration.

[0225] This will be described below with a concrete example.

[0226] When the above TDRA table is configured for DCI format 0_1 ​​(third DCI), when a UE receives DCI format 0_1 ​​in which CRC is scrambled by CS-RNTI and NDI=1 or "1"s (in the case of two TBs, each TB corresponds to one NDI field, and all are 1 or "1"s, or the NDI field corresponding to one of them (e.g., the first TB) is 1 or "1"s), and indicates a row including multiple SLIVs, that is, the DCI may indicate / schedule multiple PUSCHs. All HARQ process ID(s) corresponding to valid PUSCH(s) included in multiple PUSCHs indicated / scheduled by the DCI must be in the HARQ process group for the CG configuration. That is, the UE does not want the HARQ process ID(s) corresponding to any one of the valid PUSCH(s) indicated / scheduled in the DCI to not be in the HARQ process group for the CG configuration.

[0227] Here, in another example, a PUSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for a CG configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0228] This will be described below with a concrete example.

[0229] When the above TDRA table is configured for DCI format 0_1 ​​(third DCI), if the UE receives DCI format 0_1 ​​with CRC scrambled by CS-RNTI and NDI=1 or "1"s and indicates a row including multiple SLIVs, i.e., the DCI may indicate / schedule multiple PUSCHs. The UE transmits all valid PUSCH(s), and for PUSCHs whose corresponding HARQ process ID(s) are not in the HARQ process group for the CG configuration, the UE considers it as the first transmission.

[0230] In this example, the HARQ process ID corresponding to only one or at least one of all valid PUSCHs is one of one or more HARQ process IDs for a CG configuration, i.e., only one or at least one of the HARQ process ID(s) corresponding to the valid PUSCH(s) included in the multiple PUSCHs indicated / scheduled by the DCI is in the HARQ process group for the CG configuration, where the valid PUSCH(s) corresponding to the HARQ process ID(s) are retransmitted.

[0231] In the above two examples, the HARQ process ID indicated by the DCI corresponds to the first valid PUSCH, and the UE determines the HARQ process ID of the valid PUSCHs based on the indication.

[0232] In the above two examples, the UE transmits all valid PUSCH(s).

[0233] Further, for example, based on the bit value of the NDI field corresponding to the PUSCH, the terminal device transmits only the PUSCH whose corresponding NDI field bit value is 1, or the terminal device transmits all valid PUSCHs and retransmits the PUSCH whose corresponding NDI field bit value is 1, and transmits the PUSCH whose corresponding NDI field bit value is 0 for the first time.

[0234] This will be described below with a concrete example.

[0235] When the above TDRA table is configured for DCI format 0_1 ​​(third DCI), when a UE receives DCI format 0_1 ​​in which the CRC is scrambled by the CS-RNTI and indicates a row including multiple SLIVs, i.e., the NDI bit corresponding to the one or more SLIVs is 1 (for the case of two TBs, each TB corresponds to one NDI field, and the corresponding bits in the two NDI fields of the one or more SLIVs are all 1, or the corresponding bit in one of them (e.g., the first TB) is 1), i.e., the DCI may indicate or schedule multiple PUSCHs, and the NDI bit corresponding to the one or more PUSCHs is 1.

[0236] In this example, the UE transmits only PUSCHs corresponding to NDI bit=1, or alternatively, the UE transmits all valid PUSCH(s) and for any PUSCHs with corresponding NDI bit=0, the UE considers them to be transmitting for the first time.

[0237] In this example, the bit value of the NDI field corresponding to only one or at least one of all valid PUSCHs is 1.

[0238] In some embodiments of the present application, the terminal device may further receive a PUSCH configuration (PUSCH-Config) including a third configuration parameter (e.g., PUSCH-AggregationFactor) for configuring the number of repetitions, and when the CRC of the third DCI is scrambled by the CS-RNTI, the third configuration parameter is applied to the third DCI. That is, when the above TDRA table is configured for DCI format 0_1 ​​(third DCI), when the UE transmits a PUSCH scheduled by DCI format 0_1 ​​with the CRC scrambled by the CS-RNTI and NDI=1 or NDI=0, if the PUSCH configuration (PUSCH-Config) includes PUSCH-AggregationFactor, the PUSCH is repeated the number of times set by the PUSCH-AggregationFactor.

[0239] In the above embodiment, the third configuration parameter is applied to the third DCI, which refers to the third configuration parameter being applied to one or more PUSCHs among the PUSCHs scheduled by the third DCI.

[0240] For example, each PUSCH scheduled by the third DCI is repeated a number of times set by the third configuration parameter, and / or each valid PUSCH scheduled by the third DCI is repeated a number of times set by the third configuration parameter, and / or each PUSCH among the PUSCHs scheduled by the third DCI that is to be transmitted by the terminal device is repeated a number of times set by the third configuration parameter, and / or the third DCI schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the third configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third DCI, and the one PUSCH is repeated a number of times set by the third configuration parameter.

[0241] In some embodiments of the present application, the terminal device may further receive a PUSCH configuration (PUSCH-Config) including a third configuration parameter (e.g., PUSCH-AggregationFactor) for configuring the number of repetitions, and if the CRC of the third DCI is scrambled by the CS-RNTI, the third configuration parameter is not applied to the third DCI.

[0242] In the above embodiment, the third configuration parameter is not applied to the third DCI, which means that the third configuration parameter is not applied to any of the PUSCHs scheduled by the third DCI.

[0243] For example, when the above TDRA table is set for DCI format 0_1 ​​(third DCI), if a UE transmits a PUSCH scheduled by DCI format 0_1 ​​with CRC scrambled by CS-RNTI and NDI=1 or NDI=0, if a PUSCH-AggregationFactor is included in the PUSCH configuration (PUSCH-Config), the PUSCH is not repeated the number of times set by the PUSCH-AggregationFactor. Here, if the third DCI adopts another DCI format (the TDRA table corresponding to another format is different from the above TDRA table, for example, each row in the TDRA table corresponding to another format includes only one SLIV), for example, DCI format 1_0 / 1_2, the PUSCH is repeated the number of times set by the PUSCH-AggregationFactor.

[0244] In the above embodiment, in one embodiment, the PUSCH scheduled by the third DCI is not repeated, regardless of whether the PUSCH-AggregationFactor is included in the CG configuration.

[0245] In the above embodiment, in another embodiment, if the CG configuration includes the PUSCH-AggregationFactor, the PUSCH scheduled by the third DCI is repeated according to the PUSCH-AggregationFactor.

[0246] In this embodiment, the terminal device may receive a CG configuration including a fourth configuration parameter (eg, repK) for configuring the number of repetitions, and the fourth configuration parameter is applied to the third DCI.

[0247] In this embodiment, the fourth configuration parameter is applied to the third DCI, which refers to the fourth configuration parameter being applied to one or more of the PUSCHs scheduled by the third DCI.

[0248] For example, each PUSCH scheduled by the 3rd DCI is repeated a number of times set by the fourth configuration parameter, and / or each valid PUSCH scheduled by the 3rd DCI is repeated a number of times set by the fourth configuration parameter, and / or each PUSCH among the PUSCHs scheduled by the 3rd DCI that is to be transmitted by the terminal device is repeated a number of times set by the fourth configuration parameter, and / or the 3rd DCI schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the 3rd DCI, and the one PUSCH is repeated a number of times set by the fourth configuration parameter.

[0249] In this embodiment, the CG configuration (CG-config) is a CG configuration corresponding to the PUSCH (corresponding CG PUSCH). For example, if only one CG-config is configured in the UE, the CG-config is a CG configuration corresponding to the PUSCH (corresponding CG PUSCH). Furthermore, for example, if the UE configures and activates only multiple CG configurations, the UE determines the CG configuration corresponding to the PUSCH (corresponding CG PUSCH) based on, for example, a HARQ process ID corresponding to the PUSCH. Furthermore, for example, if the HARQ process ID corresponding to the PUSCH is shared by multiple CG configurations, the PUSCH-AggregationFactor refers to, for example, the largest PUSCH-AggregationFactor included in the multiple CG configurations.

[0250] In an embodiment of the present application, the CG configuration may further include an information field (or fields) of the corresponding HARQ process ID range, such as nrofHARQ-Processes, harq-ProcID-Offset, etc., that is used by the base station to indicate / the UE to determine.

[0251] In the embodiments of the present application, with regard to aggregation / repetition of CG PUSCH, in some embodiments, the terminal device may further receive a PUSCH configuration (PUSCH-Config) including a third configuration parameter (e.g., PUSCH-AggregationFactor) for setting the number of repetitions. Furthermore, the terminal device may further receive a fourth DCI for activating the CG configuration, the third configuration parameter is applied to the fourth DCI, and one or more rows in the TDRA table corresponding to the fourth DCI include multiple SLIVs.

[0252] In the above embodiment, applying the third configuration parameter to the fourth DCI includes that the CG PUSCH corresponding to the fourth DCI is repeated according to the third configuration parameter, where the CG PUSCH corresponding to the fourth DCI refers to, for example, a PUSCH (CG PUSCH) scheduled by a CG configuration activated by the fourth DCI, or a CG PUSCH activated by the fourth DCI.

[0253] For example, when the above TDRA table is set for DCI format 0_1 ​​(fourth DCI), if a PUSCH-AggregationFactor is included in the PUSCH configuration (PUSCH-Config) for a PUSCH scheduled by a CG configuration and activated by DCI format 0_1 ​​(i.e., a CG PUSCH), the PUSCH is repeated the number of times set by the PUSCH-AggregationFactor. The CG PUSCH does not have a corresponding PDCCH, and the PDCCH is a PDCCH that carries a DCI for scheduling the PUSCH.

[0254] In the embodiment of the present application, with respect to the aggregation / repetition of the CG PUSCH, in some other embodiments, the terminal device may further receive a PUSCH configuration (PUSCH-Config) including a third configuration parameter (e.g., PUSCH-AggregationFactor) for setting the number of repetitions. Furthermore, the terminal device may further receive a fourth DCI for activating the CG configuration, the third configuration parameter is not applied to the fourth DCI, and one or more rows in the TDRA table corresponding to the fourth DCI include multiple SLIVs.

[0255] In the above embodiment, the third configuration parameter is not applied to the fourth DCI, which means that the third configuration parameter is not applied to any one of the CG PUSCHs corresponding to the fourth DCI.

[0256] For example, when the above TDRA table is set for DCI format 0_1 ​​(fourth DCI), if the PUSCH configuration (PUSCH-Config) includes a PUSCH-AggregationFactor for a PUSCH (i.e., a CG PUSCH) scheduled by a CG configuration and activated by DCI format 0_1, the PUSCH is repeated the number of times set by the PUSCH-AggregationFactor. The CG PUSCH does not have a corresponding PDCCH, and the PDCCH is a PDCCH that carries a DCI for scheduling the PUSCH. Here, when the fourth DCI adopts another DCI format (the TDRA table corresponding to another format is different from the above TDRA table, for example, each row in the TDRA table corresponding to another format includes only one SLIV), for example, DCI format 1_0 / 1_2, the PUSCH is repeated the number of times set by the PUSCH-AggregationFactor.

[0257] In the above embodiment, in one embodiment, the CG PUSCH corresponding to the fourth DCI is not repeated, regardless of whether the CG configuration includes the above PUSCH-AggregationFactor.

[0258] In the above embodiment, in another embodiment, if the CG configuration includes the PUSCH-AggregationFactor, the CG PUSCH corresponding to the fourth DCI is repeated according to the PUSCH-AggregationFactor.

[0259] In this embodiment, the terminal device may receive a CG configuration including a fourth configuration parameter (eg, repK) for configuring the number of repetitions, which is applied to the fourth DCI.

[0260] In this embodiment, the fourth configuration parameter is applied to the fourth DCI, which refers to the fourth configuration parameter being applied to one or more of the CG PUSCHs corresponding to the fourth DCI.

[0261] For example, each CG PUSCH corresponding to the fourth DCI is repeated a number of times set by the fourth configuration parameter, and / or each valid CG PUSCH corresponding to the fourth DCI is repeated a number of times set by the fourth configuration parameter, and / or each CG PUSCH among the CG PUSCHs corresponding to the fourth DCI that should be transmitted by the terminal device is repeated a number of times set by the fourth configuration parameter, and / or the fourth DCI corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth DCI, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0262] The above various embodiments are merely illustrative of the embodiments of the present application, and the present application is not limited thereto, and appropriate modifications may be further made based on the above various embodiments. For example, the above various embodiments may be used individually, or one or more of the above various embodiments may be combined.

[0263] In an embodiment of the present application, the terminal device may further receive a PDCCH / DCI for activating / deactivating the CG, for example, the terminal device validates the validity of the PDCCH / DCI by: 1. It is scrambled by the CS-RNTI (more specifically, the CRC corresponding to the DCI format is scrambled by the CS-RNTI); 2. Set the NDI field to "0", 3. If the DFI field is present, it shall be set to "0"; 4. For activation, if the PUSCH-to-HARQ_feedback timing indicator field is present, it cannot provide an inapplicable value (e.g., -1); and 5. (If the TDRA table applicable to the corresponding DCI format includes at least one row of TDRA configuration including multiple SLIV configurations or is DCI format 1_1) It may be confirmed according to at least one or more of the following that the TDRA configuration / row / row index indicated by the Time domain resource assignment field includes / corresponds to only one PUSCH / SLIV.

[0264] In an embodiment of the present application, with respect to CG activation, if only one configuration for CG PUSCH is provided, the validity of the DCI may further depend on the HARQ process number field and the RV field.

[0265] Here, with regard to the RV field, when a TDRA table applied to a DCI format (for example, DCI format 1_1) corresponding to the DCI includes at least one row of TDRA configuration including multiple SLIV configurations, when the TDRA configuration indicated by the Time domain resource assignment field includes / supports only one PDSCH, the Redundancy version field of the DCI corresponding to one TB includes two bits. When one TB is configured in the DCI format, only one Redundancy version field is included in the DCI, and the bits of the Redundancy version field are all set to "0" or all set to "1". When two TBs are configured in the DCI format, the DCI includes Redundancy version fields (one-to-one correspondence) corresponding to each of the two TBs, and the bits of the Redundancy version field corresponding to each of the two TBs are all set to "0" or all set to "1". Or, all bits in the Redundancy version field corresponding to one TB (e.g., the first TB) are set to "0", and all bits in the Redundancy version field corresponding to another TB (e.g., the second TB) are set to "1". For example, (if the CG supports only one TB), the first TB is enabled and the second TB is disabled, and all bits in the Redundancy version field corresponding to the first TB are set to "0", and all bits in the Redundancy version field corresponding to the second TB are set to "1". Furthermore, (if the CG supports only two TBs), the bits in the Redundancy version field corresponding to each of the two TBs are set to all "0" or all "1". As shown in Table 2 above.

[0266] Furthermore, when multiple configurations for CG PUSCH are provided, the validity of the DCI further depends on the RV field, and the further description regarding the configuration of the RV field is the same as the above activation case for only one configuration for CG PUSCH, as shown in Table 3 above.

[0267] Meanwhile, the HARQ process number field is used to indicate the CG configuration index activated by the DCI (if multiple configurations for CG PUSCH are provided), which may be associated / corresponding to one or multiple configurations for CG PUSCH.

[0268] In an embodiment of the present application, with regard to CG deactivation, if only one configuration for CG PUSCH is provided (or only one CG PUSCH is configured), the validity of the DCI may further depend on the HARQ process number field, the RV field, the Modulation and coding scheme field, and the Frequency domain resource assignment field.

[0269] Here, with regard to the RV field, when a TDRA table applied to a DCI format (for example, DCI format 1_1) corresponding to the DCI includes at least one row of TDRA configuration including multiple SLIV configurations, if the TDRA configuration indicated by the DCI includes / supports only one PDSCH, the redundancy version field of the DCI corresponding to one TB includes two bits. When one TB is configured in the DCI format, only one redundancy version field is included in the DCI, and the bits of the redundancy version field are all set to "0" or all set to "1". When two TBs are configured in the DCI format, the DCI includes a redundancy version field (one-to-one correspondence) corresponding to each of the two TBs, and the bits of the redundancy version field corresponding to each of the two TBs are all set to "0" or all set to "1". As shown in Table 4 above.

[0270] When multiple configurations for CG PUSCH are provided, the validity of the DCI further depends on the RV field, the Modulation and coding scheme field, and the Frequency domain resource assignment field, and the further description on the configuration of the RV field is the same as the above deactivation case for only one configuration for CG PUSCH, as shown in Table 5 above.

[0271] Meanwhile, the HARQ process number field (if multiple configurations for CG PUSCH are provided) is used to indicate the CG configuration index deactivated by the DCI, which may be associated / corresponding to one or multiple configurations for CG PUSCH.

[0272] According to the method of the embodiment of the present application, it is possible to support scheduling of multiple PUSCHs by one DCI, and further, when one DCI (or DCI format) can schedule multiple PUSCHs, it is possible to support semi-static or semi-persistent scheduling of PUSCHs, and it is possible to support dynamic retransmission of data corresponding to semi-static or semi-persistent scheduling.

[0273] Example of the fourth aspect In the embodiments of the present application, a data scheduling method is provided and described from the network device side. This method is a process on the network device side corresponding to the method according to the embodiments of the third aspect, and the same contents as those of the embodiments of the third aspect will not be described again.

[0274] 5 is a schematic diagram of a data scheduling method according to an embodiment of the present application. As shown in FIG. 5, the method includes: 501: The method includes a network device sending third downlink control information for scheduling one or more PUSCHs.

[0275] In some embodiments, when the network device receives a plurality of PUSCHs among the PUSCHs scheduled by the third downlink control information, the data carried by different PUSCHs among the plurality of PUSCHs are different.

[0276] In some embodiments, the third downlink control information is in DCI format 0_1.

[0277] In some embodiments, the third downlink control information includes a first NDI field and / or a second NDI field, and when the third downlink control information includes the first NDI field and the second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0278] In some embodiments, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0279] In some embodiments, the number of bits included in the first NDI field and / or the second NDI field is: A maximum number of PUSCHs that can be scheduled by the third downlink control information; The number of PUSCHs scheduled by the third downlink control information, and The number of valid PUSCHs scheduled by the third downlink control information is determined based on at least one of the number of valid PUSCHs scheduled by the third downlink control information.

[0280] In some embodiments, when the CRC of the third downlink control information is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits, and when the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0281] In some embodiments, one or more rows in the TDRA table corresponding to the third downlink control information includes a plurality of SLIVs.

[0282] In some embodiments, the third downlink control information schedules one PUSCH, and / or the first NDI field and / or the second NDI field of the third downlink control information have a value of 1, and / or the third downlink control information schedules multiple PUSCHs, and / or the third downlink control information schedules multiple valid PUSCHs, and / or the NDI field of the third downlink control information includes multiple bits with a value of 1, and / or a HARQ process ID corresponding to the multiple PUSCHs scheduled by the third downlink control information is one of one or more HARQ process IDs for a CG configuration, and / or a HARQ process ID corresponding to the one or more PUSCHs scheduled by the third downlink control information is not one of one or more HARQ process IDs for a CG configuration.

[0283] In some embodiments, the CRC of the third downlink control information is scrambled by a CS-RNTI, and the third downlink control information schedules only one PUSCH.

[0284] In some embodiments, the CRC of the third downlink control information is scrambled by a CS-RNTI, the third downlink control information schedules a plurality of PUSCHs, and the network device receives one PUSCH of the plurality of PUSCHs scheduled by the third downlink control information, or the network device receives a PUSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration, or the network device receives all valid PUSCHs of the plurality of PUSCHs scheduled by the third downlink control information, or the network device receives a PUSCH whose corresponding NDI field has a bit value of 1, or the network device receives all valid PUSCHs and considers a PUSCH whose corresponding NDI field has a bit value of 1 to be retransmitted and considers a PUSCH whose corresponding NDI field has a bit value of 0 to be transmitted for the first time.

[0285] In some embodiments, the one PUSCH is the first or last PUSCH of the multiple PUSCHs, and / or the one PUSCH is the only valid PUSCH of the multiple PUSCHs, and / or the one PUSCH is the only PUSCH of the multiple PUSCHs whose corresponding NDI field value is 1, and / or the one PUSCH is the only PUSCH of the multiple PUSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration.

[0286] In some embodiments, the HARQ process ID indicated by the third downlink control information corresponds to the one PUSCH, or the HARQ process ID indicated by the third downlink control information corresponds to a first valid PUSCH among the multiple PUSCHs, and the terminal device determines the HARQ process ID corresponding to the one PUSCH based on the HARQ process ID.

[0287] In some embodiments, the HARQ process ID corresponding to the one PUSCH is one of one or more HARQ process IDs for a CG configuration.

[0288] In some embodiments, the one PUSCH is a valid PUSCH.

[0289] In some embodiments, the first PUSCH is the first PUSCH scheduled by the third downlink control information or the first valid PUSCH scheduled by the third downlink control information, and the last PUSCH is the last PUSCH scheduled by the third downlink control information or the last valid PUSCH scheduled by the third downlink control information.

[0290] In some embodiments, the HARQ process IDs corresponding to all the valid PUSCHs must be one of one or more HARQ process IDs for a CG configuration.

[0291] In some embodiments, a PUSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for a CG configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0292] In some embodiments, the HARQ process ID corresponding to only one or at least one of all the valid PUSCHs is one of one or more HARQ process IDs for a CG configuration.

[0293] In some embodiments, the bit value of the NDI field corresponding to only one or at least one of all valid PUSCHs is one.

[0294] In some embodiments, the method further comprises: The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The CRC of the third downlink control information is scrambled by a CS-RNTI, and the third configuration parameter is applied to the third downlink control information.

[0295] In some embodiments, applying the third configuration parameter to the third downlink control information includes applying the third configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0296] In some embodiments, each PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or each PUSCH among the PUSCHs scheduled by the third downlink control information that is to be transmitted by a terminal device is repeated a number of times set by the third configuration parameter, and / or the third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the third configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the third configuration parameter.

[0297] In some embodiments, the method further comprises: The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The CRC of the third downlink control information is scrambled by a CS-RNTI, and the third configuration parameter is not applied to the third downlink control information.

[0298] In some embodiments, not applying the third configuration parameter to the third downlink control information includes not applying the third configuration parameter to any of the PUSCHs scheduled by the third downlink control information.

[0299] In some embodiments, the method further comprises: the network device sending a CG configuration including a fourth configuration parameter for configuring a number of iterations; and The fourth configuration parameter is further applied to the third downlink control information.

[0300] In some embodiments, applying the fourth configuration parameter to the third downlink control information includes applying the fourth configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0301] In some embodiments, each PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each PUSCH to be transmitted by a terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or the third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the fourth configuration parameter.

[0302] In some embodiments, the method further comprises: The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The network device further includes sending fourth downlink control information for activating a CG configuration, the third configuration parameter being applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information including multiple SLIVs.

[0303] In some embodiments, applying the third configuration parameter to the fourth downlink control information includes repeating a CG PUSCH corresponding to the fourth downlink control information in response to the third configuration parameter.

[0304] In some embodiments, the method further comprises: The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The network device further includes sending fourth downlink control information for activating a CG configuration, the third configuration parameter is not applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information includes multiple SLIVs.

[0305] In some embodiments, not applying the third configuration parameter to the fourth downlink control information includes not applying the third configuration parameter to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0306] In some embodiments, the method further comprises: the network device sending a CG configuration including a fourth configuration parameter for configuring a number of iterations; and The fourth configuration parameter is further applied to the fourth downlink control information.

[0307] In some embodiments, applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0308] In some embodiments, each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information that should be transmitted by a terminal device is repeated a number of times set by the fourth configuration parameter, and / or the fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0309] The above various embodiments are merely illustrative of the embodiments of the present application, and the present application is not limited thereto, and appropriate modifications may be further made based on the above various embodiments. For example, the above various embodiments may be used individually, or one or more of the above various embodiments may be combined.

[0310] According to the method of the embodiment of the present application, it is possible to support scheduling of multiple PUSCHs by one DCI, and further, when one DCI (or DCI format) can schedule multiple PUSCHs, it is possible to support semi-static or semi-persistent scheduling of PUSCHs, and it is possible to support dynamic retransmission of data corresponding to semi-static or semi-persistent scheduling. Furthermore, it is possible to increase the flexibility of configuration and resource scheduling for network devices.

[0311] Example of the fifth aspect In an embodiment of the present application, a data receiving device is provided. The device may be, for example, a terminal device, or may be one or a part of a component or assembly configured in a terminal device. The device according to the embodiment of the present application corresponds to the method according to the embodiment of the first aspect, and the same content as the embodiment of the first aspect will not be described again.

[0312] FIG. 6 is a schematic diagram of an example of a data receiving device according to an embodiment of the present application. As shown in FIG. 6, the data receiving device 600 includes: A first receiving unit 601 for receiving first downlink control information for scheduling a PDSCH; and a second receiving unit 602 for receiving one or more PDSCHs among the PDSCHs scheduled by the first downlink control information.

[0313] In some embodiments, when the second receiving unit 602 receives multiple PDSCHs among the PDSCHs scheduled by the first downlink control information, the data carried by different PDSCHs among the multiple PDSCHs are different.

[0314] In some embodiments, the first downlink control information is in DCI format 1_1.

[0315] In some embodiments, the first downlink control information includes a first NDI field and / or a second NDI field, and when the first downlink control information includes a first NDI field and a second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0316] In some embodiments, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0317] In some embodiments, the number of bits included in the first NDI field and / or the second NDI field is: A maximum number of PDSCHs that can be scheduled by the first downlink control information; The number of PDSCHs scheduled by the first downlink control information, and The determination is based on at least one of the number of valid PDSCHs scheduled by the first downlink control information.

[0318] In some embodiments, when the CRC of the first downlink control information is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits, and when the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0319] In some embodiments, one or more rows in the TDRA table corresponding to the first downlink control information includes multiple SLIVs.

[0320] In some embodiments, the terminal device does not want the CRC of the first downlink control information to be scrambled by the CS-RNTI, and / or the first NDI field and / or the second NDI field of the first downlink control information to have a value of 1, and / or the terminal device schedules multiple PDSCHs by the first downlink control information, and / or the terminal device schedules multiple valid PDSCHs by the first downlink control information, and / or the NDI field of the first downlink control information includes multiple bits with a value of 1, and / or the HARQ process ID corresponding to the multiple PDSCHs scheduled by the first downlink control information is one of one or more HARQ process IDs for an SPS configuration, and / or the terminal device does not want the HARQ process ID corresponding to the one or more PDSCHs scheduled by the first downlink control information to be not one of one or more HARQ process IDs for an SPS configuration.

[0321] In some embodiments, the CRC of the first downlink control information is scrambled by a CS-RNTI, the first downlink control information schedules only one PDSCH, and the terminal device receives the one PDSCH.

[0322] In some embodiments, the CRC of the first downlink control information is scrambled with a CS-RNTI, and the first downlink control information schedules a plurality of PDSCHs.

[0323] In the above embodiment, the second receiving unit 602: HARQ process ID corresponding to PDSCH, The bit value of the NDI field corresponding to the PDSCH, and Based on at least one of whether the PDSCH collides with a semi-statically configured uplink symbol, It determines whether or not to receive a PDSCH among a plurality of PDSCHs scheduled by the first downlink control information.

[0324] In some embodiments, the second receiving unit 602 receives only one PDSCH of the multiple PDSCHs.

[0325] For example, the one PDSCH is the first or last PDSCH among the multiple PDSCHs, and / or the one PDSCH is the only valid PDSCH among the multiple PDSCHs, and / or the one PDSCH is the only PDSCH among the multiple PDSCHs whose corresponding NDI field value is 1, and / or the one PDSCH is the only PDSCH among the multiple PDSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration.

[0326] In some embodiments, the HARQ process ID indicated by the first downlink control information corresponds to the one PDSCH, or the HARQ process ID indicated by the first downlink control information corresponds to a first valid PDSCH among the multiple PDSCHs, and the terminal device determines the HARQ process ID corresponding to the one PDSCH based on the HARQ process ID.

[0327] In some embodiments, the HARQ process ID corresponding to the one PDSCH is one of one or more HARQ process IDs for an SPS configuration.

[0328] In some embodiments, the one PDSCH is a valid PDSCH.

[0329] In some embodiments, the first PDSCH is the first PDSCH scheduled by the first downlink control information or the first valid PDSCH scheduled by the first downlink control information, and the last PDSCH is the last PDSCH scheduled by the first downlink control information or the last valid PDSCH scheduled by the first downlink control information.

[0330] In some other embodiments, the second receiving unit 602 only receives a PDSCH whose corresponding HARQ process ID is one of the one or more HARQ process IDs for the SPS configuration.

[0331] In some other embodiments, the second receiving unit 602 receives all valid PDSCHs of the plurality of PDSCHs.

[0332] In some embodiments, the HARQ process IDs corresponding to all the valid PDSCHs must be one of one or more HARQ process IDs for an SPS configuration.

[0333] In some embodiments, a PDSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for an SPS configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0334] In some embodiments, the HARQ process ID corresponding to only one or at least one of all the enabled PDSCHs is one of one or more HARQ process IDs for an SPS configuration.

[0335] Further, in some embodiments, the second receiving unit 602 only receives a PDSCH whose corresponding NDI field has a bit value of 1, or the second receiving unit 602 receives all valid PDSCHs and considers that it will retransmit a PDSCH whose corresponding NDI field has a bit value of 1, and that it will transmit a PDSCH whose corresponding NDI field has a bit value of 0 for the first time.

[0336] In some embodiments, the bit value of the NDI field corresponding to only one or at least one of all valid PDSCHs is one.

[0337] In some embodiments, as shown in FIG. 6, the device 600 includes: Further including a third receiving unit 603 for receiving a PDSCH configuration including a first configuration parameter for configuring a repetition number, wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first configuration parameter is applied to the first downlink control information.

[0338] In some embodiments, applying the first configuration parameter to the first downlink control information includes applying the first configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0339] For example, each PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first downlink control information that should be received by the terminal device is repeated a number of times set by the first configuration parameter, and / or the first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the first configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the first configuration parameter.

[0340] In some embodiments, as shown in FIG. 6, the device 600 includes: Further including a fourth receiving unit 604 for receiving a PDSCH configuration including a first configuration parameter for configuring a repetition number, wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first configuration parameter is applied to the first downlink control information.

[0341] In some embodiments, not applying the first configuration parameter to the first downlink control information includes not applying the first configuration parameter to any of the PDSCHs scheduled by the first downlink control information.

[0342] In some embodiments, as shown in FIG. 6, the device 600 includes: The fifth receiving unit 605 further includes receiving an SPS configuration including a second configuration parameter for configuring a number of repetitions, the second configuration parameter being applied to the second downlink control information.

[0343] In some embodiments, applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the scheduled PDSCHs by the first downlink control information.

[0344] For example, each PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first downlink control information that should be received by the terminal device is repeated a number of times set by the second configuration parameter, and / or the first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the first configuration parameter.

[0345] In some further embodiments, as shown in FIG. 6, the device 600 includes: a sixth receiving unit 606 for receiving a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and a seventh receiving unit 607 for receiving second downlink control information for activating an SPS configuration, wherein the first configuration parameter is applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0346] In some embodiments, applying the first configuration parameter to the second downlink control information includes repeating an SPS PDSCH corresponding to the second downlink control information in response to the first configuration parameter.

[0347] Also, in some embodiments, as shown in FIG. 6, the device 600 may include: an eighth receiving unit 608 for receiving a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and a ninth receiving unit 609 for receiving second downlink control information for activating an SPS configuration, wherein the first configuration parameter is not applied to the second downlink control information, and one or more rows in the TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0348] In some embodiments, not applying the first configuration parameter to the second downlink control information includes not applying the first configuration parameter to any one of the SPS PDSCHs corresponding to the second downlink control information.

[0349] In some embodiments, as shown in FIG. 6, the device 600 includes: The method further includes a tenth receiving unit 610 for receiving an SPS configuration including a second configuration parameter for configuring a number of repetitions, the second configuration parameter being applied to the first downlink control information.

[0350] In some embodiments, applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0351] For example, each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information that the terminal device should receive is repeated a number of times set by the second configuration parameter, and / or the second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0352] 7 is a schematic diagram of another example of a data receiving device according to an embodiment of the present application. As shown in FIG. 7, the data receiving device 700 includes: a first receiving unit 701 for receiving a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and a second receiving unit 702 for receiving second downlink control information for activating an SPS configuration, wherein the first configuration parameters are applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0353] In some embodiments, applying the first configuration parameter to the second downlink control information includes repeating an SPS PDSCH corresponding to the second downlink control information in response to the first configuration parameter.

[0354] 8 is a schematic diagram of another example of a data receiving device according to an embodiment of the present application. As shown in FIG. 8, the data receiving device 800 includes: A first receiving unit 801 for receiving a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; A second receiving unit 802 for receiving second downlink control information for activating an SPS configuration, wherein the first configuration parameter is not applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0355] In some embodiments, not applying the first configuration parameter to the second downlink control information includes not applying the first configuration parameter to any one of the SPS PDSCHs corresponding to the second downlink control information.

[0356] In some embodiments, as shown in FIG. 8, the device 800 includes: Further included is a third receiving unit 803 for receiving an SPS configuration including a second configuration parameter for configuring a number of repetitions, wherein the second configuration parameter is applied to the second downlink control information.

[0357] In some embodiments, applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0358] For example, each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information that the terminal device should receive is repeated a number of times set by the second configuration parameter, and / or the second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0359] In an embodiment of the present application, a data scheduling device is further provided. The device may be, for example, a network device, or may be one or a part of a component or assembly configured in a network device. The device according to the embodiment of the present application corresponds to the method according to the embodiment of the second aspect, and the same content as the embodiment of the second aspect will not be described again.

[0360] 9 is a schematic diagram of an example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 9, the data scheduling device 900 includes: It includes a first transmitting unit 901 for transmitting first downlink control information for scheduling one or more PDSCHs.

[0361] In some embodiments, when the network device transmits a plurality of PDSCHs among the PDSCHs scheduled by the first downlink control information, the data carried by different PDSCHs among the plurality of PDSCHs is different.

[0362] In some embodiments, the first downlink control information is in DCI format 1_1.

[0363] In some embodiments, the first downlink control information includes a first NDI field and / or a second NDI field, and when the first downlink control information includes a first NDI field and a second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0364] In some embodiments, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0365] In some embodiments, the number of bits included in the first NDI field and / or the second NDI field is: A maximum number of PDSCHs that can be scheduled by the first downlink control information; The number of PDSCHs scheduled by the first downlink control information, and The determination is based on at least one of the number of valid PDSCHs scheduled by the first downlink control information.

[0366] In some embodiments, when the CRC of the first downlink control information is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits, and when the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0367] In some embodiments, one or more rows in the TDRA table corresponding to the first downlink control information includes multiple SLIVs.

[0368] In some embodiments, the first downlink control information schedules one PDSCH, and / or the first NDI field and / or the second NDI field of the first downlink control information have a value of 1, and / or the first downlink control information schedules multiple PDSCHs, and / or the first downlink control information schedules multiple valid PDSCHs, and / or the NDI field of the first downlink control information includes multiple bits with a value of 1, and / or the HARQ process ID corresponding to the multiple PDSCHs scheduled by the first downlink control information is one of one or more HARQ process IDs for an SPS configuration, and / or the HARQ process ID corresponding to the one or more PDSCHs scheduled by the first downlink control information is not one of one or more HARQ process IDs for an SPS configuration.

[0369] In some embodiments, the CRC of the first downlink control information is scrambled by a CS-RNTI, and the first downlink control information schedules only one PDSCH.

[0370] In some embodiments, a CRC of the first downlink control information is scrambled by a CS-RNTI, the first downlink control information schedules a plurality of PDSCHs, and the network device transmits one PDSCH of the plurality of PDSCHs scheduled by the first downlink control information, or the network device transmits a PDSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration, or the network device transmits all valid PDSCHs of the plurality of PDSCHs scheduled by the first downlink control information, or the network device transmits a PDSCH whose corresponding NDI field has a bit value of 1, or the network device transmits all valid PDSCHs and considers a PDSCH whose corresponding NDI field has a bit value of 1 to be retransmitted and a PDSCH whose corresponding NDI field has a bit value of 0 to be transmitted for the first time. In some embodiments, the one PDSCH is the first or last PDSCH of the multiple PDSCHs, and / or the one PDSCH is the only valid PDSCH of the multiple PDSCHs, and / or the one PDSCH is the only PDSCH of the multiple PDSCHs whose corresponding NDI field value is 1, and / or the one PDSCH is the only PDSCH of the multiple PDSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration.

[0371] In some embodiments, the HARQ process ID indicated by the first downlink control information corresponds to the one PDSCH, or the HARQ process ID indicated by the first downlink control information corresponds to a first valid PDSCH among the multiple PDSCHs, and the terminal device determines the HARQ process ID corresponding to the one PDSCH based on the HARQ process ID.

[0372] In some embodiments, the HARQ process ID corresponding to the one PDSCH is one of one or more HARQ process IDs for an SPS configuration.

[0373] In some embodiments, the one PDSCH is a valid PDSCH.

[0374] In some embodiments, the first PDSCH is the first PDSCH scheduled by the first downlink control information or the first valid PDSCH scheduled by the first downlink control information, and the last PDSCH is the last PDSCH scheduled by the first downlink control information or the last valid PDSCH scheduled by the first downlink control information.

[0375] In some embodiments, the HARQ process IDs corresponding to all the valid PDSCHs must be one of one or more HARQ process IDs for an SPS configuration.

[0376] In some embodiments, a PDSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for an SPS configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0377] In some embodiments, the HARQ process ID corresponding to only one or at least one of all the enabled PDSCHs is one of one or more HARQ process IDs for an SPS configuration.

[0378] In some embodiments, the bit value of the NDI field corresponding to only one or at least one of all valid PDSCHs is one.

[0379] In some embodiments, as shown in FIG. 9, the device 900 includes: Further including a second transmitting unit 902 for transmitting a PDSCH configuration including a first configuration parameter for configuring a repetition number, wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first configuration parameter is applied to the first downlink control information.

[0380] In some embodiments, applying the first configuration parameter to the first downlink control information includes applying the first configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0381] In some embodiments, each PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first downlink control information that is to be received by the terminal device is repeated a number of times set by the first configuration parameter, and / or the first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the first configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the first configuration parameter.

[0382] In some embodiments, as shown in FIG. 9, the device 900 includes: Further including a third transmitting unit 903 for transmitting a PDSCH configuration including a first configuration parameter for configuring a repetition number, wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first configuration parameter is not applied to the first downlink control information.

[0383] In some embodiments, not applying the first configuration parameter to the first downlink control information includes not applying the first configuration parameter to any of the PDSCHs scheduled by the first downlink control information.

[0384] In some embodiments, as shown in FIG. 9, the device 900 includes: The method further includes a fourth sending unit 904 for sending an SPS configuration including a second configuration parameter for configuring a number of repetitions, the second configuration parameter being applied to the first downlink control information.

[0385] In some embodiments, applying the second configuration parameter to the first downlink control information includes applying the second configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0386] In some embodiments, each PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or each PDSCH among the PDSCHs scheduled by the first downlink control information that is to be received by a terminal device is repeated a number of times set by the second configuration parameter, and / or the first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the second configuration parameter.

[0387] In some embodiments, as shown in FIG. 9, the device 900 includes: a fifth transmitting unit 905 for transmitting a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and a sixth transmitting unit 906 for transmitting second downlink control information for activating an SPS configuration, wherein the first configuration parameter is applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0388] In some embodiments, applying the first configuration parameter to the second downlink control information includes repeating an SPS PDSCH corresponding to the second downlink control information in response to the first configuration parameter.

[0389] In some embodiments, as shown in FIG. 9, the device 900 includes: a seventh transmitting unit 907 for transmitting a PDSCH configuration including a first configuration parameter for configuring the number of repetitions; and an eighth transmitting unit 908 for transmitting second downlink control information for activating an SPS configuration, wherein the first configuration parameter is not applied to the second downlink control information, and one or more rows in the TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0390] In some embodiments, not applying the first configuration parameter to the second downlink control information includes not applying the first configuration parameter to any one of the SPS PDSCHs corresponding to the second downlink control information.

[0391] In some embodiments, as shown in FIG. 9, the device 900 includes: The method further includes a ninth sending unit 909 for sending an SPS configuration including a second configuration parameter for configuring a number of repetitions, the second configuration parameter being applied to the second downlink control information.

[0392] In some embodiments, applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0393] In some embodiments, each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information that should be received by the terminal device is repeated a number of times set by the second configuration parameter, and / or the second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0394] 10 is a schematic diagram of another example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 10, the data scheduling device 1000 includes: a first transmitting unit 1001 for transmitting a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and a second transmitting unit 1002 for transmitting second downlink control information for activating an SPS configuration, wherein the first configuration parameters are applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0395] In some embodiments, applying the first configuration parameter to the second downlink control information includes repeating an SPS PDSCH corresponding to the second downlink control information in response to the first configuration parameter.

[0396] 11 is a schematic diagram of yet another example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 11, the data scheduling device 1100 includes: A first transmitting unit 1101 for transmitting a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and a second transmitting unit 1102 for transmitting second downlink control information for activating an SPS configuration, wherein the first configuration parameter is not applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information include multiple SLIVs.

[0397] In some embodiments, not applying the first configuration parameter to the second downlink control information includes not applying the first configuration parameter to any one of the SPS PDSCHs corresponding to the second downlink control information.

[0398] In some embodiments, as shown in FIG. 11, the device 1100 includes: The method further includes a third sending unit 1103 for sending an SPS configuration including a second configuration parameter for configuring a repetition number, where the second configuration parameter is applied to the second downlink control information.

[0399] In some embodiments, applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0400] In some embodiments, each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or each SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information that should be received by the terminal device is repeated a number of times set by the second configuration parameter, and / or the second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter, and / or the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0401] The above is merely an illustrative description of the embodiments of the present application, and the present application is not limited thereto, and appropriate modifications may be further made based on the various embodiments described above. For example, the various embodiments described above may be used individually, or one or more of the various embodiments described above may be combined.

[0402] In the above, only various components or modules related to the present application have been described, but the present application is not limited thereto. The data receiving devices 600-800 and the data scheduling devices 900-1100 may further include other components or modules, and the specific contents of these components or modules may refer to the related art. Furthermore, the above various components or modules may be realized by hardware equipment such as a processor, a memory, a transmitter, a receiver, etc. The implementation of the present application is not limited thereto.

[0403] According to the device of the embodiment of the present application, it is possible to support scheduling of multiple PDSCHs by one DCI, and further, when one DCI (or DCI format) can schedule multiple PDSCHs, it is possible to support semi-static or semi-persistent scheduling of PDSCHs, and it is possible to support dynamic retransmission of data corresponding to semi-static or semi-persistent scheduling. Furthermore, it is possible to increase the flexibility of configuration and resource scheduling for network devices.

[0404] Example of the sixth aspect In an embodiment of the present application, a data transmission device or a data scheduling device is provided. The device may be, for example, a terminal device, or may be one or a part of a component or assembly configured in a terminal device. The device according to the embodiment of the present application corresponds to the method according to the embodiment of the third aspect, and the same content as the embodiment of the third aspect will not be described again.

[0405] FIG. 12 is a schematic diagram of an example of a data transmission device according to an embodiment of the present application. As shown in FIG. 12, the data transmission device 1200 includes: A first receiving unit 1201 for receiving third downlink control information for scheduling a PUSCH; a transmitting unit 1202 for transmitting one or more PUSCHs among the PUSCHs scheduled by the third downlink control information.

[0406] In some embodiments, when the transmitting unit 1202 transmits a plurality of PUSCHs among the PUSCHs scheduled by the third downlink control information, the data carried by different PUSCHs among the plurality of PUSCHs are different. In some embodiments, the third downlink control information is in DCI format 0_1.

[0407] In some embodiments, the third downlink control information includes a first NDI field and / or a second NDI field, and when the third downlink control information includes the first NDI field and the second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0408] In some embodiments, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0409] In some embodiments, the number of bits included in the first NDI field and / or the second NDI field is: A maximum number of PUSCHs that can be scheduled by the third downlink control information; The number of PUSCHs scheduled by the third downlink control information, and The number of valid PUSCHs scheduled by the third downlink control information is determined based on at least one of the number of valid PUSCHs scheduled by the third downlink control information.

[0410] In some embodiments, when the CRC of the third downlink control information is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits, and when the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0411] In some embodiments, one or more rows in the TDRA table corresponding to the third downlink control information includes a plurality of SLIVs.

[0412] In the above embodiment, the terminal device does not want the CRC of the third downlink control information to be scrambled by a CS-RNTI, and / or the value of the first NDI field and / or the second NDI field of the third downlink control information to be 1, and / or a plurality of PUSCHs to be scheduled by the third downlink control information, and / or a plurality of valid PUSCHs to be scheduled by the third downlink control information, and / or the NDI field of the third downlink control information includes a plurality of bits having a value of 1, and / or the HARQ process ID corresponding to the plurality of PUSCHs scheduled by the third downlink control information is one of one or more HARQ process IDs for a CG configuration, and / or the HARQ process ID corresponding to the one or more PUSCHs scheduled by the third downlink control information is not one of one or more HARQ process IDs for a CG configuration.

[0413] In some embodiments, the CRC of the third downlink control information is scrambled by a CS-RNTI, the third downlink control information schedules only one PUSCH, and the transmitting unit 1202 transmits the one PUSCH.

[0414] In some embodiments, the CRC of the third downlink control information is scrambled with a CS-RNTI, and the third downlink control information schedules a plurality of PUSCHs.

[0415] In some embodiments, the transmitting unit 1202 may include: HARQ process ID corresponding to PUSCH, The bit value of the NDI field corresponding to the PUSCH, Whether the PUSCH collides with the semi-statically configured downlink symbol; Whether PUSCH will collide with SSB, and Based on at least one of whether the PUSCH collides with CORESET#0, It determines whether or not to transmit a PUSCH among a plurality of PUSCHs scheduled by the third downlink control information.

[0416] In some embodiments, the transmitting unit 1202 transmits only one PUSCH of the multiple PUSCHs.

[0417] In the above embodiments, the one PUSCH is the first or last PUSCH among the multiple PUSCHs, and / or the one PUSCH is the only valid PUSCH among the multiple PUSCHs, and / or the one PUSCH is the only PUSCH among the multiple PUSCHs whose corresponding NDI field value is 1, and / or the one PUSCH is the only PUSCH among the multiple PUSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration.

[0418] In the above examples, in some embodiments, the HARQ process ID indicated by the third downlink control information corresponds to the one PUSCH, or the HARQ process ID indicated by the third downlink control information corresponds to a first valid PUSCH among the multiple PUSCHs, and the terminal device determines the HARQ process ID corresponding to the one PUSCH based on the HARQ process ID.

[0419] In the above example, in some embodiments, the HARQ process ID corresponding to one PUSCH is one of one or more HARQ process IDs for a CG configuration.

[0420] In the above example, in some embodiments, the one PUSCH is a valid PUSCH.

[0421] In the above examples, in some embodiments, the first PUSCH is the first PUSCH scheduled by the third downlink control information or the first valid PUSCH scheduled by the third downlink control information, and the last PUSCH is the last PUSCH scheduled by the third downlink control information or the last valid PUSCH scheduled by the third downlink control information.

[0422] In some other embodiments, the transmitting unit 1202 transmits only the PUSCH whose corresponding HARQ process ID is one of the one or more HARQ process IDs for the CG configuration.

[0423] In some other embodiments, the transmitting unit 1202 transmits all valid PUSCHs of the plurality of PUSCHs.

[0424] In the above example, in some embodiments, the HARQ process IDs corresponding to all the valid PUSCHs must be one of one or more HARQ process IDs for a CG configuration.

[0425] In the above examples, in some embodiments, a PUSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for a CG configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0426] In the above example, in some embodiments, the HARQ process ID corresponding to only one or at least one of all the valid PUSCHs is one of one or more HARQ process IDs for a CG configuration.

[0427] Further, in some embodiments, the transmitting unit 1202 transmits only PUSCHs whose corresponding NDI field bit value is 1, or the transmitting unit 1202 transmits all valid PUSCHs and considers retransmitting PUSCHs whose corresponding NDI field bit value is 1, and considers PUSCHs whose corresponding NDI field bit value is 0 to be transmitted for the first time.

[0428] In the above example, in some embodiments, the bit value of the NDI field corresponding to only one or at least one of all valid PUSCHs is 1.

[0429] In some embodiments, as shown in FIG. 12, the device 1200 includes: Further including a second receiving unit 1203 for receiving a PUSCH configuration including a third configuration parameter for configuring a repetition number, wherein a CRC of the third downlink control information is scrambled by a CS-RNTI, and the third configuration parameter is applied to the third downlink control information.

[0430] In the above embodiment, applying the third configuration parameter to the third downlink control information includes applying the third configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0431] In the above embodiment, each PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or each PUSCH to be transmitted by the terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or the third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the third configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the third configuration parameter.

[0432] In some embodiments, as shown in FIG. 12, the device 1200 includes: Further including a third receiving unit 1204 for receiving a PUSCH configuration including a third configuration parameter for configuring a repetition number, wherein a CRC of the third downlink control information is scrambled by a CS-RNTI, and the third configuration parameter is not applied to the third downlink control information.

[0433] In the above embodiment, the third configuration parameter is not applied to the third downlink control information including the third configuration parameter is not applied to any one of the PUSCHs scheduled by the third downlink control information.

[0434] In the above example, in some embodiments, as shown in FIG. 12, the device 1200 includes: Further comprising a fourth receiving unit 1205 for receiving a CG configuration including a fourth configuration parameter for configuring a number of repetitions, the fourth configuration parameter being applied to the third downlink control information.

[0435] In the above embodiment, applying the fourth configuration parameter to the third downlink control information includes applying the fourth configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0436] In the above embodiment, each PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each PUSCH to be transmitted by the terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or the third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the fourth configuration parameter.

[0437] In some embodiments, as shown in FIG. 12, the device 1200 includes: A fifth receiving unit 1206 receives a PUSCH configuration including a third configuration parameter for configuring a repetition number; and a sixth receiving unit 1207 for receiving fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information include multiple SLIVs.

[0438] In the above embodiment, applying the third configuration parameter to the fourth downlink control information includes repeating a CG PUSCH corresponding to the fourth downlink control information according to the third configuration parameter.

[0439] In some embodiments, as shown in FIG. 12, the device 1200 includes: A seventh receiving unit 1208 receives a PUSCH configuration including a third configuration parameter for configuring a repetition number; and an eighth receiving unit 1209 for receiving fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is not applied to the fourth downlink control information, and one or more rows in the TDRA table corresponding to the fourth downlink control information include multiple SLIVs.

[0440] In the above embodiment, the third configuration parameter is not applied to the fourth downlink control information including the third configuration parameter is not applied to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0441] In the above example, in some embodiments, as shown in FIG. 12, the device 1200 includes: The ninth receiving unit 1210 further includes a CG configuration including a fourth configuration parameter for configuring a number of repetitions, the fourth configuration parameter being applied to the fourth downlink control information.

[0442] In the above embodiment, applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0443] In the above embodiment, each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information that the terminal device should transmit is repeated a number of times set by the fourth configuration parameter, and / or the fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0444] 13 is a schematic diagram of an example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 13, the data scheduling device 1300 includes: A first receiving unit 1301 for receiving a PUSCH configuration including a third configuration parameter for configuring a repetition number; and a second receiving unit 1302 for receiving fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information include a plurality of SLIVs.

[0445] In some embodiments, applying the third configuration parameter to the fourth downlink control information includes repeating a CG PUSCH corresponding to the fourth downlink control information according to the third configuration parameter.

[0446] 14 is a schematic diagram of another example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 14, a data receiving device 1400 includes: A first receiving unit 1401 for receiving a PUSCH configuration including a third configuration parameter for configuring a repetition number; and a second receiving unit 1402 for receiving fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is not applied to the fourth downlink control information, and one or more rows in the TDRA table corresponding to the fourth downlink control information include multiple SLIVs.

[0447] In some embodiments, not applying the third configuration parameter to the fourth downlink control information includes not applying the third configuration parameter to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0448] In some embodiments, as shown in FIG. 14, the device 1400 includes: The fourth downlink control information further includes a third receiving unit 1403 for receiving a CG configuration including a fourth configuration parameter for configuring a number of repetitions, the fourth configuration parameter being applied to the fourth downlink control information.

[0449] In some embodiments, applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0450] For example, each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information that the terminal device should transmit is repeated a number of times set by the fourth configuration parameter, and / or the fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0451] In an embodiment of the present application, a data scheduling apparatus is further provided, which may be, for example, a network device, or may be one or a part of a component or assembly configured in a network. The apparatus according to the embodiment of the present application corresponds to the method according to the embodiment of the fourth aspect, and the same content as the embodiment of the fourth aspect will not be described again.

[0452] FIG. 15 is a schematic diagram of an example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 15, the data scheduling device 1500 includes: The first transmitting unit 1501 includes a first transmitting unit for transmitting third downlink control information for scheduling one or more PUSCHs.

[0453] In some embodiments, when the network device receives a plurality of PUSCHs among the PUSCHs scheduled by the third downlink control information, the data carried by different PUSCHs among the plurality of PUSCHs are different.

[0454] In some embodiments, the third downlink control information is in DCI format 0_1.

[0455] In some embodiments, the third downlink control information includes a first NDI field and / or a second NDI field, and when the third downlink control information includes the first NDI field and the second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0456] In some embodiments, the value of the first NDI field and / or the second NDI field is 0 or 1.

[0457] In some embodiments, the number of bits included in the first NDI field and / or the second NDI field is: A maximum number of PUSCHs that can be scheduled by the third downlink control information; The number of PUSCHs scheduled by the third downlink control information, and The number of valid PUSCHs scheduled by the third downlink control information is determined based on at least one of the number of valid PUSCHs scheduled by the third downlink control information.

[0458] In some embodiments, when the CRC of the third downlink control information is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits, and when the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0459] In some embodiments, one or more rows in the TDRA table corresponding to the third downlink control information includes a plurality of SLIVs.

[0460] In some embodiments, the third downlink control information schedules one PUSCH, and / or the first NDI field and / or the second NDI field of the third downlink control information have a value of 1, and / or the third downlink control information schedules multiple PUSCHs, and / or the third downlink control information schedules multiple valid PUSCHs, and / or the NDI field of the third downlink control information includes multiple bits with a value of 1, and / or a HARQ process ID corresponding to the multiple PUSCHs scheduled by the third downlink control information is one of one or more HARQ process IDs for a CG configuration, and / or a HARQ process ID corresponding to the one or more PUSCHs scheduled by the third downlink control information is not one of one or more HARQ process IDs for a CG configuration.

[0461] In some embodiments, the CRC of the third downlink control information is scrambled by a CS-RNTI, and the third downlink control information schedules only one PUSCH.

[0462] In some embodiments, the CRC of the third downlink control information is scrambled by a CS-RNTI, the third downlink control information schedules a plurality of PUSCHs, and the network device receives one PUSCH among the plurality of PUSCHs scheduled by the third downlink control information, or the network device receives a PUSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration, or the network device receives all valid PUSCHs among the plurality of PUSCHs scheduled by the third downlink control information, or the network device receives a PUSCH whose corresponding NDI field has a bit value of 1, or the network device receives all valid PUSCHs and considers a PUSCH whose corresponding NDI field has a bit value of 1 to be retransmitted and considers a PUSCH whose corresponding NDI field has a bit value of 0 to be transmitted for the first time.

[0463] In some embodiments, the one PUSCH is the first or last PUSCH of the multiple PUSCHs, and / or the one PUSCH is the only valid PUSCH of the multiple PUSCHs, and / or the one PUSCH is the only PUSCH of the multiple PUSCHs whose corresponding NDI field value is 1, and / or the one PUSCH is the only PUSCH of the multiple PUSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration.

[0464] In some embodiments, the HARQ process ID indicated by the third downlink control information corresponds to the one PUSCH, or the HARQ process ID indicated by the third downlink control information corresponds to a first valid PUSCH among the multiple PUSCHs, and the terminal device determines the HARQ process ID corresponding to the one PUSCH based on the HARQ process ID.

[0465] In some embodiments, the HARQ process ID corresponding to the one PUSCH is one of one or more HARQ process IDs for a CG configuration.

[0466] In some embodiments, the one PUSCH is a valid PUSCH.

[0467] In some embodiments, the first PUSCH is the first PUSCH scheduled by the third downlink control information or the first valid PUSCH scheduled by the third downlink control information, and the last PUSCH is the last PUSCH scheduled by the third downlink control information or the last valid PUSCH scheduled by the third downlink control information.

[0468] In some embodiments, the HARQ process IDs corresponding to all the valid PUSCHs must be one of one or more HARQ process IDs for a CG configuration.

[0469] In some embodiments, a PUSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for a CG configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0470] In some embodiments, the HARQ process ID corresponding to only one or at least one of all the valid PUSCHs is one of one or more HARQ process IDs for a CG configuration.

[0471] In some embodiments, the bit value of the NDI field corresponding to only one or at least one of all valid PUSCHs is one.

[0472] In some embodiments, as shown in FIG. 15, the device 1500 includes: Further including a second transmitting unit 1502 for transmitting a PUSCH configuration including a third configuration parameter for configuring a repetition number, wherein a CRC of the third downlink control information is scrambled by a CS-RNTI, and the third configuration parameter is applied to the third downlink control information.

[0473] In some embodiments, applying the third configuration parameter to the third downlink control information includes applying the third configuration parameter to one or more PUSCHs scheduled by the third downlink control information.

[0474] Each PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or each PUSCH to be transmitted by the terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or the third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the third configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the third configuration parameter.

[0475] In some embodiments, as shown in FIG. 15, the device 1500 includes: Further including a third transmitting unit 1503 for transmitting a PUSCH configuration including a third configuration parameter for configuring a repetition number, wherein a CRC of the third downlink control information is scrambled by a CS-RNTI, and the third configuration parameter is not applied to the third downlink control information.

[0476] In some embodiments, not applying the third configuration parameter to the third downlink control information includes not applying the third configuration parameter to any of the PUSCHs scheduled by the third downlink control information.

[0477] In some embodiments, as shown in FIG. 15, the device 1500 includes: The third downlink control information further includes a fourth sending unit 1504 for sending a CG configuration including a fourth configuration parameter for configuring a number of repetitions, the fourth configuration parameter being applied to the third downlink control information.

[0478] In some embodiments, applying the fourth configuration parameter to the third downlink control information includes applying the fourth configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0479] In some embodiments, each PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each PUSCH among the PUSCHs scheduled by the third downlink control information that is to be transmitted by a terminal device is repeated a number of times set by the fourth configuration parameter, and / or the third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the fourth configuration parameter.

[0480] In some embodiments, as shown in FIG. 15, the device 1500 includes: a fifth sending unit 1505 for sending a PUSCH configuration including a third configuration parameter for configuring a number of repetitions; and a sixth transmitting unit 1506 for transmitting fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information include multiple SLIVs.

[0481] In some embodiments, applying the third configuration parameter to the fourth downlink control information includes repeating a CG PUSCH corresponding to the fourth downlink control information in response to the third configuration parameter.

[0482] In some embodiments, as shown in FIG. 15, the device 1500 includes: a seventh sending unit 1507 for sending a PUSCH configuration including a third configuration parameter for configuring a number of repetitions; and an eighth transmitting unit 1508 for transmitting fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is not applied to the fourth downlink control information, and one or more rows in the TDRA table corresponding to the fourth downlink control information include multiple SLIVs.

[0483] In some embodiments, not applying the third configuration parameter to the fourth downlink control information includes not applying the third configuration parameter to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0484] In some embodiments, as shown in FIG. 15, the device 1500 includes: The ninth sending unit 1509 further includes a CG configuration including a fourth configuration parameter for configuring a number of repetitions, the fourth configuration parameter being applied to the fourth downlink control information.

[0485] In some embodiments, applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0486] In some embodiments, each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information that should be transmitted by a terminal device is repeated a number of times set by the fourth configuration parameter, and / or the fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0487] 16 is a schematic diagram of another example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 16, the data scheduling device 1600 includes: a first transmitting unit 1601 for transmitting a PUSCH configuration including a third configuration parameter for configuring a repetition number; and a second transmitting unit 1602 for transmitting fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information include multiple SLIVs.

[0488] In some embodiments, applying the third configuration parameter to the fourth downlink control information includes repeating a CG PUSCH corresponding to the fourth downlink control information in response to the third configuration parameter.

[0489] 17 is a schematic diagram of another example of a data scheduling device according to an embodiment of the present application. As shown in FIG. 17, the data scheduling device 1700 includes: a first transmitting unit 1701 for transmitting a PUSCH configuration including a third configuration parameter for configuring a repetition number; and a second transmitting unit 1702 for transmitting fourth downlink control information for activating a CG configuration, wherein the third configuration parameter is not applied to the fourth downlink control information, and one or more rows in the TDRA table corresponding to the fourth downlink control information include multiple SLIVs.

[0490] In some embodiments, not applying the third configuration parameter to the fourth downlink control information includes not applying the third configuration parameter to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0491] In some embodiments, as shown in FIG. 17, the device 1700 includes: The method further includes a third sending unit 1703 for sending a CG configuration including a fourth configuration parameter for configuring a number of repetitions, where the fourth configuration parameter is applied to the fourth downlink control information.

[0492] In some embodiments, applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0493] In some embodiments, each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or each CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information that should be transmitted by a terminal device is repeated a number of times set by the fourth configuration parameter, and / or the fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter, and / or the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0494] The above is merely an illustrative description of the embodiments of the present application, and the present application is not limited thereto, and appropriate modifications may be further made based on the various embodiments described above. For example, the various embodiments described above may be used individually, or one or more of the various embodiments described above may be combined.

[0495] In the above, only various components or modules related to the present application have been described, but the present application is not limited thereto. The data transmitting device 1200 and the data scheduling devices 1300 to 1700 may further include other components or modules, and the specific contents of these components or modules may refer to the related art. Furthermore, the above various components or modules may be realized by hardware equipment such as a processor, a memory, a transmitter, and a receiver. The implementation of the present application is not limited thereto.

[0496] According to the method of the embodiment of the present application, it is possible to support scheduling of multiple PUSCHs by one DCI, and further, when one DCI (or DCI format) can schedule multiple PUSCHs, it is possible to support semi-static or semi-persistent scheduling of PUSCHs, and it is possible to support dynamic retransmission of data corresponding to semi-static or semi-persistent scheduling. Furthermore, it is possible to increase the flexibility of configuration and resource scheduling for network devices.

[0497] Example of the seventh aspect In an embodiment of the present application, a communication system is provided, including a network device and a terminal device.

[0498] In some embodiments, the terminal device is configured to perform the method according to an embodiment of the first aspect and the network device is configured to perform the method according to an embodiment of the second aspect.

[0499] In some embodiments, the terminal device is configured to perform the method described in the embodiment of the third aspect and the network device is configured to perform the method described in the embodiment of the fourth aspect.

[0500] Each method has been described in detail in the embodiments of the first to fourth aspects, and the contents thereof are incorporated herein, so description thereof will be omitted.

[0501] In the embodiment of the present application, a terminal device is further provided, which may be, for example, a UE, but the present application is not limited thereto and may be other terminal devices.

[0502] Fig. 18 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Fig. 18, the terminal device 1800 may include a processor 1801 and a memory 1802, where the memory 1802 stores data and programs and is coupled to the processor 1801. It should be noted that the diagram is exemplary, and other types of structures may be used to supplement or replace the structures so as to realize telecommunication functions or other functions.

[0503] For example, the processor 1801 may be arranged to execute a program to implement a method according to an embodiment of the first or third aspect.

[0504] As shown in Fig. 18, the terminal device 1800 may further include a communication module 1803, an input unit 1804, a display 1805, and a power source 1806. Here, the functions of the above components are similar to those of the prior art, and the description thereof will be omitted here. Note that the terminal device 1800 does not need to include all the components shown in Fig. 18, and the above components are not essential. Furthermore, the terminal device 1800 may further include components not shown in Fig. 18, and may refer to the prior art.

[0505] In an embodiment of the present application, a network device is further provided, which may be, for example, a base station, but the present application is not limited thereto and may be other network devices.

[0506] Fig. 19 is a schematic diagram of a network device according to an embodiment of the present application. As shown in Fig. 19, the network device 1900 may include a processor 1901 and a memory 1902, and the memory 1902 is coupled to the processor 1901. Here, the memory 1902 can store various data, and further stores a program for processing information, and executes the program under the control of the processor 1901.

[0507] For example, the processor 1901 may be configured to execute a program to implement a method according to an embodiment of the second or fourth aspect.

[0508] Furthermore, as shown in Fig. 19, the network device 1900 may further include a transceiver 1903 and an antenna 1904. Here, the functions of the above components are similar to those of the prior art, and the description is omitted here. Note that the network device 1900 does not need to include all the components shown in Fig. 19. Furthermore, the network device 1900 may further include components not shown in Fig. 19, and may refer to the prior art.

[0509] In an embodiment of the present application, there is further provided a computer program, wherein, when said program is executed in a terminal device, said program causes said terminal device to perform a method according to an embodiment of the first or third aspect.

[0510] In an embodiment of the present application, a storage medium is provided having stored thereon a computer program, wherein the computer program causes a terminal device to execute the method according to the embodiment of the first or third aspect.

[0511] In an embodiment of the present application, there is further provided a computer program, wherein, when running said program in a network device, said program causes said terminal device to perform a method according to an embodiment of the second or fourth aspect.

[0512] In an embodiment of the present application, a storage medium is provided having a computer program stored thereon, wherein the computer program causes a network device to perform a method according to an embodiment of the second or fourth aspect.

[0513] The above-mentioned apparatus and method of the present application may be realized by hardware or a combination of hardware and software. The present application relates to a computer readable program which, when executed by a logic element, causes the logic element to realize the above-mentioned apparatus or components or to realize the various methods or steps described above. The present application further relates to a storage medium, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc., on which the above-mentioned program is stored.

[0514] The methods / apparatuses described with reference to the embodiments of the present application may be embodied directly as hardware, software modules executed by a processor, or a combination of both. For example, one or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams shown in the figures 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 figures. These hardware modules may be realized by implementing these software modules in hardware using, for example, a field programmable gate array (FPGA).

[0515] The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from and write information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may reside in an ASIC. The software module may be stored in a memory of the mobile terminal, or in a memory card that can be inserted into the mobile terminal. For example, if a device (e.g., a mobile terminal) uses a relatively large capacity MEGA-SIM card or a large capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large capacity flash memory device.

[0516] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams depicted in the figures 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 depicted in the figures and / or one or more combinations of functional blocks may be implemented with a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0517] Although the present application has been described above with reference to specific embodiments, it is obvious to those skilled in the art that the above description is merely illustrative and does not limit the scope of protection of the present application. Those skilled in the art may make various modifications and amendments to the present application based on the spirit and principles of the present application, and these modifications and amendments are also within the scope of the present application.

[0518] The following supplementary notes are further disclosed regarding the embodiments including the above examples.

[0519] 1. A terminal device receives first downlink control information for scheduling a PDSCH; and A data reception method comprising: the terminal device receiving one or more PDSCHs among PDSCHs scheduled by the first downlink control information.

[0520] 2. The method according to Supplementary Note 1, in which when the terminal device receives a plurality of PDSCHs among the PDSCHs scheduled by the first downlink control information, data carried by different PDSCHs among the plurality of PDSCHs is different.

[0521] 3. The method described in Supplementary Note 1, wherein the first downlink control information is DCI format 1_1.

[0522] 4. The method described in Supplementary Note 1, wherein the first downlink control information includes a first NDI field and / or a second NDI field, and when the first downlink control information includes a first NDI field and a second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0523] 5. The method of claim 4, wherein the value of the first NDI field and / or the second NDI field is 0 or 1.

[0524] 6. The number of bits included in the first NDI field and / or the second NDI field is A maximum number of PDSCHs that can be scheduled by the first downlink control information; The number of PDSCHs scheduled by the first downlink control information, and The method of claim 4, wherein the number of valid PDSCHs scheduled by the first downlink control information is determined based on at least one of the number of valid PDSCHs scheduled by the first downlink control information.

[0525] 7. When the CRC of the first downlink control information is scrambled by the CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits; 7. The method of claim 4 or 6, wherein the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0526] 8. The method of claim 1, wherein one or more rows in the TDRA table corresponding to the first downlink control information includes multiple SLIVs.

[0527] 9. The terminal device is configured such that the CRC of the first downlink control information is scrambled by the CS-RNTI, and / or The value of the first NDI field and / or the second NDI field of the first downlink control information is 1, and / or A plurality of PDSCHs are scheduled by the first downlink control information, and / or A plurality of valid PDSCHs are scheduled by the first downlink control information; and / or The NDI field of the first downlink control information includes a plurality of bits having a value of 1; and / or The HARQ process IDs corresponding to the multiple PDSCHs scheduled by the first downlink control information are one of one or more HARQ process IDs for an SPS configuration; and / or The method described in Supplementary Note 8, wherein the HARQ process ID corresponding to one or more PDSCHs scheduled by the first downlink control information is not desired to be one of the one or more HARQ process IDs for an SPS configuration.

[0528] 10. A method according to any one of Supplementary Notes 1 to 9, wherein the CRC of the first downlink control information is scrambled by a CS-RNTI, the first downlink control information schedules only one PDSCH, and the terminal device receives the one PDSCH.

[0529] 11. The method according to any one of Supplementary Notes 1 to 9, wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first downlink control information schedules a plurality of PDSCHs.

[0530] 12. The terminal device HARQ process ID corresponding to PDSCH, The bit value of the NDI field corresponding to the PDSCH, and Based on at least one of whether the PDSCH collides with a semi-statically configured uplink symbol, The method of claim 11, further comprising: determining whether to receive a PDSCH among a plurality of PDSCHs scheduled by the first downlink control information.

[0531] 13. The method according to claim 11, wherein the terminal device receives only one PDSCH out of the plurality of PDSCHs.

[0532] 14. The one PDSCH is the first PDSCH or the last PDSCH of the plurality of PDSCHs; and / or The one PDSCH is the only valid PDSCH among the plurality of PDSCHs; and / or The one PDSCH is the only PDSCH among the plurality of PDSCHs whose corresponding NDI field has a value of 1; and / or 14. The method of claim 13, wherein the one PDSCH is the only PDSCH among the plurality of PDSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration.

[0533] 15. The HARQ process ID indicated by the first downlink control information corresponds to one PDSCH, or The method described in Supplementary Note 14, wherein the HARQ process ID indicated by the first downlink control information corresponds to a first valid PDSCH among the multiple PDSCHs, and the terminal device determines a HARQ process ID corresponding to the one PDSCH based on the HARQ process ID.

[0534] 16. The method of claim 14, wherein the HARQ process ID corresponding to the one PDSCH is one of one or more HARQ process IDs for an SPS configuration.

[0535] 17. The method of claim 14, wherein the one PDSCH is a valid PDSCH.

[0536] 18. The first PDSCH is a first PDSCH scheduled by the first downlink control information, or a first valid PDSCH scheduled by the first downlink control information; 15. The method of claim 14, wherein the last PDSCH is the last PDSCH scheduled by the first downlink control information or the last valid PDSCH scheduled by the first downlink control information.

[0537] 19. The method according to Supplementary Note 11, in which the terminal device receives only a PDSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration.

[0538] 20. The method according to claim 11, wherein the terminal device receives all valid PDSCHs among the plurality of PDSCHs.

[0539] 21. The method of claim 20, wherein the HARQ process IDs corresponding to all the valid PDSCHs must be one of one or more HARQ process IDs for an SPS configuration.

[0540] 22. The method of claim 20, wherein a PDSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for an SPS configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0541] 23. The method of claim 20, wherein the HARQ process ID corresponding to only one or at least one of all valid PDSCHs is one of one or more HARQ process IDs for an SPS configuration.

[0542] 24. The terminal device receives only a PDSCH whose corresponding NDI field has a bit value of 1, or The method described in Supplementary Note 11, in which the terminal device receives all valid PDSCHs and considers that it retransmits PDSCHs with a bit value of 1 in the corresponding NDI field, and considers that it transmits PDSCHs with a bit value of 0 in the corresponding NDI field for the first time.

[0543] 25. The method of claim 24, wherein the bit value of the NDI field corresponding to only one or at least one of all valid PDSCHs is 1.

[0544] 26. The terminal device receives a PDSCH configuration including a first configuration parameter for configuring a repetition number; and 2. The method of claim 1, further comprising: a CRC of the first downlink control information being scrambled by a CS-RNTI; and the first configuration parameter being applied to the first downlink control information.

[0545] 27. The method of claim 26, wherein applying the first configuration parameter to the first downlink control information includes applying the first configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0546] 28. Each PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or Each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or Each PDSCH to be received by the terminal device among the PDSCHs scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or The first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times as configured by the first configuration parameter; and / or The method according to claim 26 or 27, wherein the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the first configuration parameter.

[0547] 29. The terminal device receives a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and 2. The method of claim 1, further comprising: a CRC of the first downlink control information is scrambled by a CS-RNTI; and the first configuration parameter is not applied to the first downlink control information.

[0548] 30. The method of claim 29, wherein not applying the first configuration parameter to the first downlink control information includes not applying the first configuration parameter to any one of the PDSCHs scheduled by the first downlink control information.

[0549] 31. The terminal device receives an SPS configuration including a second configuration parameter for configuring a number of repetitions; and 30. The method of claim 29, further comprising applying the second configuration parameter to the first downlink control information.

[0550] 32. The method of claim 31, wherein applying the second configuration parameter to the first downlink control information includes applying the second configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0551] 33. Each PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or Each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or Each PDSCH to be received by the terminal device among the PDSCHs scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or The first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the second configuration parameter; and / or The method according to claim 31 or 32, wherein the terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the second configuration parameter.

[0552] 34. The terminal device receives a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; The terminal device receives second downlink control information for activating an SPS configuration; and 2. The method of claim 1, further comprising: the first configuration parameter is applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information includes multiple SLIVs.

[0553] 35. The first configuration parameter is applied to the second downlink control information, 35. The method of claim 34, comprising repeating an SPS PDSCH corresponding to the second downlink control information according to the first configuration parameter.

[0554] 36. The terminal device receives a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; The terminal device receives second downlink control information for activating an SPS configuration; and 2. The method of claim 1, further comprising: the first configuration parameter is not applied to the second downlink control information; and one or more rows in a TDRA table corresponding to the second downlink control information includes multiple SLIVs.

[0555] 37. The first configuration parameter is not applied to the second downlink control information, 37. The method of claim 36, comprising: the first configuration parameter not being applied to any one of SPS PDSCHs corresponding to the second downlink control information.

[0556] 38. The terminal device receives an SPS configuration including a second configuration parameter for configuring a number of repetitions; and 37. The method of claim 36, further comprising applying the second configuration parameter to the second downlink control information.

[0557] 39. The method of claim 38, wherein applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0558] 40. Each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or Each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter; and / or Each SPS PDSCH to be received by the terminal device among the SPS PDSCHs corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or The second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter; and / or 40. The method of claim 36 or 39, wherein the terminal device receives only one SPS PDSCH among SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0559] 41. A terminal device receives a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; The terminal device receives second downlink control information for activating an SPS configuration; and The method of receiving data, comprising: applying the first configuration parameter to the second downlink control information; and one or more rows in a TDRA table corresponding to the second downlink control information including a plurality of SLIVs.

[0560] 42. The first configuration parameter is applied to the second downlink control information, 42. The method of claim 41, comprising repeating an SPS PDSCH corresponding to the second downlink control information according to the first configuration parameter.

[0561] 43. A terminal device receives a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; The terminal device receives second downlink control information for activating an SPS configuration; and The data receiving method includes the first configuration parameter not being applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information including a plurality of SLIVs.

[0562] 44. The first configuration parameter is not applied to the second downlink control information, 44. The method of claim 43, comprising: the first configuration parameter not being applied to any one of SPS PDSCHs corresponding to the second downlink control information.

[0563] 45. The terminal device receives an SPS configuration including a second configuration parameter for configuring a number of repetitions; and 44. The method of claim 43, further comprising applying the second configuration parameter to the second downlink control information.

[0564] 46. ​​The method of claim 45, wherein applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0565] 47. Each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or Each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter; and / or Each SPS PDSCH to be received by the terminal device among the SPS PDSCHs corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or The second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter; and / or 47. The method according to claim 43 or 46, wherein the terminal device receives only one SPS PDSCH among SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0566] 1A. A data scheduling method, comprising: a network device transmitting first downlink control information for scheduling one or more PDSCHs.

[0567] 2A. The method of claim 1A, wherein when the network device transmits multiple PDSCHs among the PDSCHs scheduled by the first downlink control information, the data carried by different PDSCHs among the multiple PDSCHs is different.

[0568] 3A. The method described in Appendix 1A, wherein the first downlink control information is DCI format 1_1.

[0569] 4A. The method described in Appendix 1A, wherein the first downlink control information includes a first NDI field and / or a second NDI field, and when the first downlink control information includes a first NDI field and a second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0570] 5A. The method of claim 4A, wherein the value of the first NDI field and / or the second NDI field is 0 or 1.

[0571] 6A. The number of bits included in the first NDI field and / or the second NDI field is A maximum number of PDSCHs that can be scheduled by the first downlink control information; The number of PDSCHs scheduled by the first downlink control information, and The method of claim 4A, wherein the determined number of valid PDSCHs is determined based on at least one of the number of valid PDSCHs scheduled by the first downlink control information.

[0572] 7A. When the CRC of the first downlink control information is scrambled by CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits; 4. The method of claim 4A or 6A, wherein the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0573] 8A. The method of claim 1A, wherein one or more rows in the TDRA table corresponding to the first downlink control information includes multiple SLIVs.

[0574] 9A. The first downlink control information schedules one PDSCH, and / or The value of the first NDI field and / or the second NDI field of the first downlink control information is 1, and / or A plurality of PDSCHs are scheduled by the first downlink control information, and / or A plurality of valid PDSCHs are scheduled by the first downlink control information; and / or The NDI field of the first downlink control information includes a plurality of bits having a value of 1; and / or The HARQ process IDs corresponding to the multiple PDSCHs scheduled by the first downlink control information are one of one or more HARQ process IDs for an SPS configuration; and / or The method of claim 8A, wherein a HARQ process ID corresponding to one or more PDSCHs scheduled by the first downlink control information is not one of one or more HARQ process IDs for an SPS configuration.

[0575] 10A. The method of claim 1A, wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first downlink control information schedules only one PDSCH.

[0576] 11A. The CRC of the first downlink control information is scrambled by a CS-RNTI, and the first downlink control information schedules a plurality of PDSCHs; The network device transmits one PDSCH among the plurality of PDSCHs scheduled by the first downlink control information; or The network device transmits a PDSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration; or The network device transmits all valid PDSCHs among the multiple PDSCHs scheduled by the first downlink control information; or The network device transmits a PDSCH with a bit value of 1 in the corresponding NDI field; or The method according to claim 1A, wherein the network device transmits all valid PDSCHs and regards PDSCHs with a bit value of 1 in the corresponding NDI field as retransmitting, and regards PDSCHs with a bit value of 0 in the corresponding NDI field as transmitting for the first time.

[0577] 12A. The one PDSCH is the first PDSCH or the last PDSCH of the plurality of PDSCHs; and / or The one PDSCH is the only valid PDSCH among the plurality of PDSCHs; and / or The one PDSCH is the only PDSCH among the plurality of PDSCHs whose corresponding NDI field has a value of 1; and / or The method of claim 11A, wherein the one PDSCH is the only PDSCH among the plurality of PDSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration.

[0578] 13A. The HARQ process ID indicated by the first downlink control information corresponds to one PDSCH, or The method described in Supplementary Note 12A, in which the HARQ process ID indicated by the first downlink control information corresponds to a first valid PDSCH among the multiple PDSCHs, and the terminal device determines a HARQ process ID corresponding to the one PDSCH based on the HARQ process ID.

[0579] 14A. The method of claim 12A, wherein the HARQ process ID corresponding to the one PDSCH is one of one or more HARQ process IDs for an SPS configuration.

[0580] 15A. The method of claim 12A, wherein the one PDSCH is a valid PDSCH.

[0581] 16A. The first PDSCH is a first PDSCH scheduled by the first downlink control information, or a first valid PDSCH scheduled by the first downlink control information; The method of claim 12A, wherein the last PDSCH is a last PDSCH scheduled by the first downlink control information or a last valid PDSCH scheduled by the first downlink control information.

[0582] 17A. The method of claim 11A, wherein the HARQ process IDs corresponding to all the valid PDSCHs must be one of one or more HARQ process IDs for an SPS configuration.

[0583] 18A. The method according to Supplementary Note 11A, wherein a PDSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for an SPS configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0584] 19A. The method of claim 11A, wherein the HARQ process ID corresponding to only one or at least one of all the valid PDSCHs is one of one or more HARQ process IDs for an SPS configuration.

[0585] 20A. The method of claim 11A, wherein the bit value of the NDI field corresponding to only one or at least one of all valid PDSCHs is 1.

[0586] 21A. The network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and The method of claim 1A, further comprising: a CRC of the first downlink control information being scrambled by a CS-RNTI; and the first configuration parameter being applied to the first downlink control information.

[0587] 22A. The method of claim 21A, wherein applying the first configuration parameter to the first downlink control information includes applying the first configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0588] 23A. Each PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or Each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or Each PDSCH to be received by the terminal device among the PDSCHs scheduled by the first downlink control information is repeated a number of times set by the first configuration parameter, and / or The first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times as configured by the first configuration parameter; and / or The method according to any one of appendixes 21A and 22A, wherein a terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the first configuration parameter.

[0589] 24A. The network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and The method of claim 1A, further comprising: a CRC of the first downlink control information is scrambled by a CS-RNTI; and the first configuration parameter is not applied to the first downlink control information.

[0590] 25A. The method described in Appendix 24A, wherein not applying the first configuration parameter to the first downlink control information includes not applying the first configuration parameter to any one of the PDSCHs scheduled by the first downlink control information.

[0591] 26A. The network device transmits an SPS configuration including a second configuration parameter for configuring a number of repetitions; and 24B. The method of claim 24A, further comprising applying the second configuration parameter to the first downlink control information.

[0592] 27A. The method of claim 26A, wherein applying the second configuration parameter to the first downlink control information includes applying the second configuration parameter to one or more of the PDSCHs scheduled by the first downlink control information.

[0593] 28A. Each PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or Each valid PDSCH scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or Each PDSCH to be received by the terminal device among the PDSCHs scheduled by the first downlink control information is repeated a number of times set by the second configuration parameter, and / or The first downlink control information schedules only one PDSCH, and the one PDSCH is repeated a number of times set by the second configuration parameter; and / or The method according to any one of appendixes 26A and 27A, wherein a terminal device receives only one PDSCH among the PDSCHs scheduled by the first downlink control information, and the one PDSCH is repeated a number of times set by the second configuration parameter.

[0594] 29A. The network device transmits a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; and The method of claim 1A, further comprising: the network device sending second downlink control information for activating an SPS configuration, the first configuration parameter being applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information including multiple SLIVs.

[0595] 30A. The method of claim 29A, wherein applying the first configuration parameter to the second downlink control information includes repeating an SPS PDSCH corresponding to the second downlink control information in response to the first configuration parameter.

[0596] 31A. The network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and The method of claim 1A, further comprising: the network device sending second downlink control information for activating an SPS configuration, the first configuration parameter not being applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information including multiple SLIVs.

[0597] 32A. The method of claim 31A, wherein not applying the first configuration parameter to the second downlink control information includes not applying the first configuration parameter to any one of SPS PDSCHs corresponding to the second downlink control information.

[0598] 33A. The network device transmits an SPS configuration including a second configuration parameter for configuring a number of repetitions; and 31B. The method of claim 31A, further comprising applying the second configuration parameter to the second downlink control information.

[0599] 34A. The method of claim 33A, wherein applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0600] 35A. Each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or Each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter; and / or Each SPS PDSCH to be received by the terminal device among the SPS PDSCHs corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or The second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter; and / or The method according to any one of Supplementary Note 31A and 34A, wherein the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0601] 36A. A network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and A data scheduling method comprising: the network device transmitting second downlink control information for activating an SPS configuration, the first configuration parameter being applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information including multiple SLIVs.

[0602] 37A. The method of claim 36A, wherein applying the first configuration parameter to the second downlink control information includes repeating an SPS PDSCH corresponding to the second downlink control information in response to the first configuration parameter.

[0603] 38A. A network device transmits a PDSCH configuration including a first configuration parameter for configuring a repetition number; and A data scheduling method comprising: the network device sending second downlink control information for activating an SPS configuration, the first configuration parameter not being applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information including multiple SLIVs.

[0604] 39A. The method of claim 38A, wherein not applying the first configuration parameter to the second downlink control information includes not applying the first configuration parameter to any one of the SPS PDSCHs corresponding to the second downlink control information.

[0605] 40A. The network device transmits an SPS configuration including a second configuration parameter for configuring a number of repetitions; and 38A, further comprising: the second configuration parameter being applied to the second downlink control information.

[0606] 41A. The method of claim 40A, wherein applying the second configuration parameter to the second downlink control information includes applying the second configuration parameter to one or more of the SPS PDSCHs corresponding to the second downlink control information.

[0607] 42A. Each SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or Each valid SPS PDSCH corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter; and / or Each SPS PDSCH to be received by the terminal device among the SPS PDSCHs corresponding to the second downlink control information is repeated a number of times set by the second configuration parameter, and / or The second downlink control information corresponds to only one SPS PDSCH, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter; and / or The method according to any one of Supplementary Note 38A and 41A, wherein the terminal device receives only one SPS PDSCH among the SPS PDSCHs corresponding to the second downlink control information, and the one SPS PDSCH is repeated a number of times set by the second configuration parameter.

[0608] 1C. A terminal device receives third downlink control information for scheduling a PUSCH; and A data transmission method comprising: transmitting, by the terminal device, one or more PUSCHs among PUSCHs scheduled by the third downlink control information.

[0609] 2C. The method according to Supplementary Note 1C, in which when the terminal device transmits a plurality of PUSCHs among the PUSCHs scheduled by the third downlink control information, data carried by different PUSCHs among the plurality of PUSCHs is different.

[0610] 3C. The method described in Appendix 1C, wherein the third downlink control information is DCI format 0_1.

[0611] 4C. The method described in Appendix 1C, wherein the third downlink control information includes a first NDI field and / or a second NDI field, and when the third downlink control information includes the first NDI field and the second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0612] 5C. The method of claim 4C, wherein the value of the first NDI field and / or the second NDI field is 0 or 1.

[0613] 6C. The number of bits included in the first NDI field and / or the second NDI field is A maximum number of PUSCHs that can be scheduled by the third downlink control information; The number of PUSCHs scheduled by the third downlink control information, and The method according to claim 4C, wherein the number of valid PUSCHs scheduled by the third downlink control information is determined based on at least one of the number of valid PUSCHs scheduled by the third downlink control information.

[0614] 7C. When the CRC of the third downlink control information is scrambled by CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits; 4C or 6C, wherein the first NDI field and / or the second NDI field includes multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0615] 8C. The method of claim 1C, wherein one or more rows in the TDRA table corresponding to the third downlink control information include multiple SLIVs.

[0616] 9C. The terminal device is configured such that the CRC of the third downlink control information is scrambled by the CS-RNTI, and / or The value of the first NDI field and / or the second NDI field of the third downlink control information is 1, and / or A plurality of PUSCHs are scheduled by the third downlink control information, and / or A plurality of valid PUSCHs are scheduled by the third downlink control information; and / or The NDI field of the third downlink control information includes a plurality of bits having a value of 1; and / or The HARQ process IDs corresponding to the multiple PUSCHs scheduled by the third downlink control information are one of one or multiple HARQ process IDs for a CG configuration; and / or The method described in Appendix 8C, wherein the HARQ process ID corresponding to one or more PUSCHs scheduled by the third downlink control information is not desired to be one of the one or more HARQ process IDs for a CG configuration.

[0617] 10C. A method according to any one of Supplementary Notes 1C to 9C, wherein the CRC of the third downlink control information is scrambled by a CS-RNTI, the third downlink control information schedules only one PUSCH, and the terminal device transmits the one PUSCH.

[0618] 11C. The method of any one of Supplementary Notes 1C to 9C, wherein a CRC of the third downlink control information is scrambled with a CS-RNTI, and the third downlink control information schedules a plurality of PUSCHs.

[0619] 12C. The terminal device HARQ process ID corresponding to PUSCH, The bit value of the NDI field corresponding to the PUSCH, Whether the PUSCH collides with the semi-statically configured downlink symbol; Whether PUSCH will collide with SSB, and Based on at least one of whether the PUSCH collides with CORESET#0, The method of claim 11C, determining whether to transmit a PUSCH among a plurality of PUSCHs scheduled by the third downlink control information.

[0620] 13C. The method of claim 11C, wherein the terminal device transmits only one PUSCH of the multiple PUSCHs.

[0621] 14C. The one PUSCH is the first PUSCH or the last PUSCH of the plurality of PUSCHs; and / or The one PUSCH is the only valid PUSCH among the plurality of PUSCHs; and / or The one PUSCH is the only PUSCH among the multiple PUSCHs whose corresponding NDI field has a value of 1; and / or The method of claim 13C, wherein the one PUSCH is only one of the multiple PUSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration.

[0622] 15C. The HARQ process ID indicated by the third downlink control information corresponds to one PUSCH, or The method described in Appendix 14C, wherein the HARQ process ID indicated by the third downlink control information corresponds to a first valid PUSCH among the multiple PUSCHs, and the terminal device determines a HARQ process ID corresponding to the one PUSCH based on the HARQ process ID.

[0623] 16C. The method of claim 14C, wherein the HARQ process ID corresponding to the one PUSCH is one of one or more HARQ process IDs for a CG configuration.

[0624] 17C. The method of claim 14C, wherein the one PUSCH is a valid PUSCH.

[0625] 18C. The first PUSCH is a first PUSCH scheduled by the third downlink control information, or a first valid PUSCH scheduled by the third downlink control information; The method of claim 14C, wherein the last PUSCH is a last PUSCH scheduled by the third downlink control information or a last valid PUSCH scheduled by the third downlink control information.

[0626] 19C. The method described in Appendix 11C, in which the terminal device transmits only a PUSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration.

[0627] 20C. The method of claim 11C, wherein the terminal device transmits all valid PUSCHs among the plurality of PUSCHs.

[0628] 21C. The method of claim 20C, wherein the HARQ process IDs corresponding to all the valid PUSCHs must be one of one or more HARQ process IDs for a CG configuration.

[0629] 22C. The method of claim 20C, wherein a PUSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for a CG configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0630] 23C. The method of claim 20C, wherein the HARQ process ID corresponding to only one or at least one of all valid PUSCHs is one of one or more HARQ process IDs for a CG configuration.

[0631] 24C. The terminal device transmits only a PUSCH whose corresponding NDI field has a bit value of 1, or The terminal device transmits all valid PUSCHs and regards a PUSCH with a bit value of 1 in the corresponding NDI field as being retransmitted, and regards a PUSCH with a bit value of 0 in the corresponding NDI field as being transmitted for the first time, as described in Supplementary Note 11C.

[0632] 25C. The method of claim 24C, wherein the bit value of the NDI field corresponding to only one or at least one of all valid PUSCHs is 1.

[0633] 26C. The terminal device receives a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The method of claim 1C, further comprising: a CRC of the third downlink control information being scrambled with a CS-RNTI; and the third configuration parameter being applied to the third downlink control information.

[0634] 27C. The method of claim 26C, wherein applying the third configuration parameter to the third downlink control information includes applying the third configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0635] 28C. Each PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or Each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or Each PUSCH to be transmitted by the terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or The third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the third configuration parameter; and / or The method according to claim 26C or 27C, wherein the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the third configuration parameter.

[0636] 29C. The terminal device receives a PUSCH configuration including a third configuration parameter for configuring a number of repetitions; and The method of claim 1C, further comprising: a CRC of the third downlink control information is scrambled by a CS-RNTI; and the third configuration parameter is not applied to the third downlink control information.

[0637] 30C. The method of claim 29C, wherein not applying the third configuration parameter to the third downlink control information includes not applying the third configuration parameter to any one of the PUSCHs scheduled by the third downlink control information.

[0638] 31C. The terminal device receives a CG configuration including a fourth configuration parameter for configuring a number of repetitions; and 29C. The method of claim 29C, further comprising applying the fourth configuration parameter to the third downlink control information.

[0639] 32C. The method of claim 31C, wherein applying the fourth configuration parameter to the third downlink control information includes applying the fourth configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0640] 33C. Each PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each PUSCH to be transmitted by the terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or The third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the fourth configuration parameter; and / or The method according to any one of appendix 31C and 32C, wherein the terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the fourth configuration parameter.

[0641] 34C. The terminal device receiving a PUSCH configuration including a third configuration parameter for configuring a number of repetitions; The terminal device receives fourth downlink control information for activating a CG configuration; and 1C, further comprising: the third configuration parameter being applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information including a plurality of SLIVs.

[0642] 35C. The third configuration parameter is applied to the fourth downlink control information, 34C, comprising: a CG PUSCH corresponding to the fourth downlink control information being repeated according to the third configuration parameter.

[0643] 36C. The terminal device receiving a PUSCH configuration including a third configuration parameter for configuring a number of repetitions; The terminal device receives fourth downlink control information for activating a CG configuration; and 1C, further comprising: the third configuration parameter not being applied to the fourth downlink control information; and one or more rows in a TDRA table corresponding to the fourth downlink control information including a plurality of SLIVs.

[0644] 37C. The third configuration parameter is not applied to the fourth downlink control information. The method of claim 36C, comprising: the third configuration parameter not being applied to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0645] 38C. The terminal device receives a CG configuration including a fourth configuration parameter for configuring the number of repetitions; and The method of Claim 36C, further comprising applying the fourth configuration parameter to the fourth downlink control information.

[0646] 39C. The method of claim 38C, wherein applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0647] 40C. Each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each CG PUSCH to be transmitted by the terminal device among the CG PUSCHs corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or The fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter; and / or The method according to any one of Supplementary Note 36C and 39C, wherein the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0648] 41C. The terminal device receives a PUSCH configuration including a third configuration parameter for configuring a repetition number; The terminal device receives fourth downlink control information for activating a CG configuration; and The data scheduling method includes applying the third configuration parameter to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information including a plurality of SLIVs.

[0649] 42C. The third configuration parameter is applied to the fourth downlink control information, 41C, comprising: a CG PUSCH corresponding to the fourth downlink control information being repeated according to the third configuration parameter.

[0650] 43C. The terminal device receives a PUSCH configuration including a third configuration parameter for configuring a repetition number; The terminal device receives fourth downlink control information for activating a CG configuration; and The data scheduling method includes: the third configuration parameter is not applied to the fourth downlink control information; and one or more rows in a TDRA table corresponding to the fourth downlink control information includes a plurality of SLIVs.

[0651] 44C. The third configuration parameter is not applied to the fourth downlink control information. The method of claim 43C, comprising: the third configuration parameter not being applied to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0652] 45C. The terminal device receives a CG configuration including a fourth configuration parameter for configuring the number of repetitions; and The method of claim 43C, further comprising applying the fourth configuration parameter to the fourth downlink control information.

[0653] 46C. The method of claim 45C, wherein applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0654] 47C. Each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each CG PUSCH to be transmitted by the terminal device among the CG PUSCHs corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or The fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter; and / or The method according to claim 43C or 46C, wherein the terminal device transmits only one CG PUSCH among the CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0655] 1D. A data scheduling method, including a network device transmitting third downlink control information for scheduling one or more PUSCHs.

[0656] 2D. The method of claim 1D, wherein when the network device receives a plurality of PUSCHs among the PUSCHs scheduled by the third downlink control information, the data carried by different PUSCHs among the plurality of PUSCHs are different.

[0657] 3D. The method of claim 1D, wherein the third downlink control information is DCI format 0_1.

[0658] 4D. The method of Appendix 1D, wherein the third downlink control information includes a first NDI field and / or a second NDI field, and when the third downlink control information includes the first NDI field and the second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

[0659] 5D. The method of claim 4D, wherein the value of the first NDI field and / or the second NDI field is 0 or 1.

[0660] 6D. The number of bits included in the first NDI field and / or the second NDI field is A maximum number of PUSCHs that can be scheduled by the third downlink control information; The number of PUSCHs scheduled by the third downlink control information, and The method according to claim 4D, wherein the number of valid PUSCHs scheduled by the third downlink control information is determined based on at least one of the number of valid PUSCHs scheduled by the third downlink control information.

[0661] 7D. When the CRC of the third downlink control information is scrambled by CS-RNTI, the first NDI field and / or the second NDI field includes one bit, or the first NDI field and / or the second NDI field includes multiple bits; 5. The method of claim 4D or 6D, wherein the first NDI field and / or the second NDI field comprises multiple bits, where only one bit is valid, or multiple bits are valid, or all bits are valid.

[0662] 8D. The method of claim 1D, wherein one or more rows in the TDRA table corresponding to the third downlink control information includes multiple SLIVs.

[0663] 9D. The third downlink control information schedules one PUSCH, and / or The value of the first NDI field and / or the second NDI field of the third downlink control information is 1, and / or A plurality of PUSCHs are scheduled by the third downlink control information, and / or A plurality of valid PUSCHs are scheduled by the third downlink control information; and / or The NDI field of the third downlink control information includes a plurality of bits having a value of 1; and / or The HARQ process IDs corresponding to the multiple PUSCHs scheduled by the third downlink control information are one of one or multiple HARQ process IDs for a CG configuration; and / or The method described in Supplementary Note 8D, wherein a HARQ process ID corresponding to one or more PUSCHs scheduled by the third downlink control information is not one of one or more HARQ process IDs for a CG configuration.

[0664] 10D. The method of claim 1D, wherein a CRC of the third downlink control information is scrambled by a CS-RNTI, and the third downlink control information schedules only one PUSCH.

[0665] 11D. The CRC of the third downlink control information is scrambled by a CS-RNTI, and the third downlink control information schedules a plurality of PUSCHs; The network device receives one PUSCH among the plurality of PUSCHs scheduled by the third downlink control information; or The network device receives a PUSCH whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration; or The network device receives all valid PUSCHs among the plurality of PUSCHs scheduled by the third downlink control information; or The network device receives a PUSCH with a bit value of 1 in the corresponding NDI field; or The method of claim 1D, wherein the network device receives all valid PUSCHs and considers PUSCHs with a bit value of 1 in the corresponding NDI field to be retransmitted and PUSCHs with a bit value of 0 in the corresponding NDI field to be transmitted for the first time.

[0666] 12D. The one PUSCH is the first PUSCH or the last PUSCH of the multiple PUSCHs; and / or The one PUSCH is the only valid PUSCH among the plurality of PUSCHs; and / or The one PUSCH is the only PUSCH among the multiple PUSCHs whose corresponding NDI field has a value of 1; and / or The method of claim 11D, wherein the one PUSCH is only one of the multiple PUSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for a CG configuration.

[0667] 13D. The HARQ process ID indicated by the third downlink control information corresponds to one PUSCH, or The method described in Supplementary Note 12D, wherein the HARQ process ID indicated by the third downlink control information corresponds to a first valid PUSCH among the multiple PUSCHs, and the terminal device determines a HARQ process ID corresponding to the one PUSCH based on the HARQ process ID.

[0668] 14D. The method of claim 12D, wherein the HARQ process ID corresponding to the one PUSCH is one of one or more HARQ process IDs for a CG configuration.

[0669] 15D. The method of claim 12D, wherein the one PUSCH is a valid PUSCH.

[0670] 16D. The first PUSCH is a first PUSCH scheduled by the third downlink control information, or a first valid PUSCH scheduled by the third downlink control information; The method of claim 12D, wherein the last PUSCH is a last PUSCH scheduled by the third downlink control information or a last valid PUSCH scheduled by the third downlink control information.

[0671] 17D. The method of claim 11D, wherein the HARQ process IDs corresponding to all the valid PUSCHs must be one of one or more HARQ process IDs for a CG configuration.

[0672] 18D. The method of claim 11D, wherein a PUSCH whose corresponding HARQ process ID is not one of the one or more HARQ process IDs for a CG configuration and / or whose corresponding NDI field has a bit value of 0 is transmitted for the first time.

[0673] 19D. The method of claim 11D, wherein the HARQ process ID corresponding to only one or at least one of all valid PUSCHs is one of one or more HARQ process IDs for a CG configuration.

[0674] 20D. The method of claim 11D, wherein the bit value of the NDI field corresponding to only one or at least one of all valid PUSCHs is 1.

[0675] 21D. The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The method of claim 1D, further comprising: a CRC of the third downlink control information being scrambled with a CS-RNTI; and the third configuration parameter being applied to the third downlink control information.

[0676] 22D. The method of claim 21D, wherein applying the third configuration parameter to the third downlink control information includes applying the third configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0677] 23D. Each PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or Each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or Each PUSCH to be transmitted by a terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the third configuration parameter, and / or The third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the third configuration parameter; and / or The method according to Supplementary Note 21D or 22D, wherein a terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the third configuration parameter.

[0678] 24D. The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The method of claim 1D, further comprising: a CRC of the third downlink control information is scrambled by a CS-RNTI; and the third configuration parameter is not applied to the third downlink control information.

[0679] 25D. The method of claim 24D, wherein the third configuration parameter is not applied to the third downlink control information, including the third configuration parameter not being applied to any one of the PUSCHs scheduled by the third downlink control information.

[0680] 26D. The network device transmits a CG configuration including a fourth configuration parameter for configuring a number of repetitions; and The method of claim 24D, further comprising applying the fourth configuration parameter to the third downlink control information.

[0681] 27D. The method of claim 26D, wherein applying the fourth configuration parameter to the third downlink control information includes applying the fourth configuration parameter to one or more of the PUSCHs scheduled by the third downlink control information.

[0682] 28D. Each PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each valid PUSCH scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each PUSCH to be transmitted by a terminal device among the PUSCHs scheduled by the third downlink control information is repeated a number of times set by the fourth configuration parameter, and / or The third downlink control information schedules only one PUSCH, and the one PUSCH is repeated a number of times set by the fourth configuration parameter; and / or The method according to Supplementary Note 26D or 27D, wherein a terminal device transmits only one PUSCH among the PUSCHs scheduled by the third downlink control information, and the one PUSCH is repeated a number of times set by the fourth configuration parameter.

[0683] 29D. The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The method of claim 1D, further comprising: the network device sending fourth downlink control information for activating a CG configuration, the third configuration parameter being applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information including multiple SLIVs.

[0684] 30D. The method of claim 29D, wherein applying the third configuration parameter to the fourth downlink control information includes repeating a CG PUSCH corresponding to the fourth downlink control information in accordance with the third configuration parameter.

[0685] 31D. The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and The method of claim 1D, further comprising: the network device sending fourth downlink control information for activating a CG configuration, the third configuration parameter not being applied to the fourth downlink control information, and one or more rows in a TDRA table corresponding to the fourth downlink control information including multiple SLIVs.

[0686] 32D. The method of claim 31D, wherein the third configuration parameter is not applied to the fourth downlink control information including the third configuration parameter being not applied to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0687] 33D. The network device transmits a CG configuration including a fourth configuration parameter for configuring a number of repetitions; and 31D, further comprising: the fourth configuration parameter being applied to the fourth downlink control information.

[0688] 34D. The method of claim 33D, wherein applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0689] 35D. Each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each CG PUSCH to be transmitted by the terminal device among the CG PUSCHs corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or The fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter; and / or The method according to Supplementary Note 31D or 34D, wherein a terminal device transmits only one CG PUSCH among CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0690] 36D. The network device transmits a PUSCH configuration including a third configuration parameter for configuring the number of repetitions; and A data scheduling method comprising: the network device sending fourth downlink control information for activating a CG configuration; the third configuration parameter being applied to the fourth downlink control information; and one or more rows in a TDRA table corresponding to the fourth downlink control information including multiple SLIVs.

[0691] 37D. The method of claim 36D, wherein applying the third configuration parameter to the fourth downlink control information includes repeating a CG PUSCH corresponding to the fourth downlink control information in accordance with the third configuration parameter.

[0692] 38D. The network device transmits a PUSCH configuration including a third configuration parameter for configuring a repetition number; and A data scheduling method comprising: the network device sending fourth downlink control information for activating a CG configuration; the third configuration parameter is not applied to the fourth downlink control information; and one or more rows in a TDRA table corresponding to the fourth downlink control information includes multiple SLIVs.

[0693] 39D. The method of claim 38D, wherein the third configuration parameter is not applied to the fourth downlink control information including the third configuration parameter being not applied to any one of the CG PUSCHs corresponding to the fourth downlink control information.

[0694] 40D. The network device transmits a CG configuration including a fourth configuration parameter for configuring a number of repetitions; and The method of Claim 38D, further comprising applying the fourth configuration parameter to the fourth downlink control information.

[0695] 41D. The method of claim 40D, wherein applying the fourth configuration parameter to the fourth downlink control information includes applying the fourth configuration parameter to one or more of the CG PUSCHs corresponding to the fourth downlink control information.

[0696] 42D. Each CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each valid CG PUSCH corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or Each CG PUSCH to be transmitted by the terminal device among the CG PUSCHs corresponding to the fourth downlink control information is repeated a number of times set by the fourth configuration parameter, and / or The fourth downlink control information corresponds to only one CG PUSCH, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter; and / or The method according to Supplementary Note 38D or 41D, wherein a terminal device transmits only one CG PUSCH among CG PUSCHs corresponding to the fourth downlink control information, and the one CG PUSCH is repeated a number of times set by the fourth configuration parameter.

[0697] 1E. A terminal device comprising a memory having a computer program stored therein and a processor configured to execute the computer program and to perform the method described in any one of appendices 1 to 47 and 1C to 47C.

[0698] 1F. A network device comprising: a memory having a computer program stored therein; and a processor configured to execute the computer program and to perform the method according to any one of claims 1A to 42A and 1D to 42D. 1G. A communication system including a network device according to claim 1F and a terminal device according to claim 1E.

Claims

1. A data receiving device configured in a terminal device, A first receiving unit for receiving first downlink control information for scheduling a PDSCH; a second receiving unit configured to receive one or more PDSCHs among the PDSCHs scheduled by the first downlink control information.

2. The apparatus of claim 1 , wherein the first downlink control information is DCI format 1_1.

3. 2. The device of claim 1, wherein the first downlink control information includes a first NDI field and / or a second NDI field, and when the first downlink control information includes the first NDI field and the second NDI field, the first NDI field and the second NDI field correspond to a first TB and a second TB, respectively.

4. The apparatus of claim 3 , wherein the value of the first NDI field and / or the second NDI field is 0 or 1.

5. The apparatus of claim 1 , wherein one or more rows in a TDRA table corresponding to the first downlink control information include multiple SLIVs.

6. The device of claim 1, wherein the CRC of the first downlink control information is scrambled by a CS-RNTI, the first downlink control information schedules only one PDSCH, and the terminal device receives the one PDSCH.

7. The apparatus of claim 1 , wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first downlink control information schedules a plurality of PDSCHs.

8. The second receiving unit is HARQ process ID corresponding to PDSCH, The bit value of the NDI field corresponding to the PDSCH, and Based on at least one of whether the PDSCH collides with a semi-statically configured uplink symbol, The apparatus according to claim 7 , further comprising: a first downlink control information unit configured to receive a PDSCH from among a plurality of PDSCHs scheduled by the first downlink control information;

9. The apparatus of claim 7 , wherein the second receiving unit receives only one PDSCH of the plurality of PDSCHs.

10. The one PDSCH is the first PDSCH or the last PDSCH of the plurality of PDSCHs; and / or The one PDSCH is the only valid PDSCH among the plurality of PDSCHs; and / or The one PDSCH is the only PDSCH among the plurality of PDSCHs whose corresponding NDI field has a value of 1; and / or 10. The apparatus of claim 9, wherein the one PDSCH is the only PDSCH among the plurality of PDSCHs whose corresponding HARQ process ID is one of one or more HARQ process IDs for an SPS configuration.

11. The first PDSCH is a first PDSCH scheduled by the first downlink control information, or a first valid PDSCH scheduled by the first downlink control information, The apparatus of claim 10 , wherein the last PDSCH is a last PDSCH scheduled by the first downlink control information or a last valid PDSCH scheduled by the first downlink control information.

12. The apparatus of claim 7 , wherein the second receiving unit receives all valid PDSCHs of the plurality of PDSCHs.

13. a third receiving unit for receiving a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; The apparatus of claim 1 , wherein a CRC of the first downlink control information is scrambled by a CS-RNTI, and the first configuration parameter is applied to the first downlink control information.

14. 14. The apparatus of claim 13, wherein applying the first configuration parameter to the first downlink control information comprises applying the first configuration parameter to one or more of PDSCHs scheduled by the first downlink control information.

15. A data receiving device configured in a terminal device, a first receiving unit for receiving a PDSCH configuration including a first configuration parameter for configuring a number of repetitions; a second receiving unit for receiving second downlink control information for activating an SPS configuration; The apparatus, wherein the first configuration parameter is applied to the second downlink control information, and one or more rows in a TDRA table corresponding to the second downlink control information includes a plurality of SLIVs.

16. The first configuration parameter is applied to the second downlink control information, The apparatus of claim 15 , further comprising: an SPS PDSCH corresponding to the second downlink control information being repeated according to the first configuration parameter.

17. A data transmission device configured in a terminal device, a first receiving unit for receiving third downlink control information for scheduling a PUSCH; a transmission unit for transmitting one or more PUSCHs among the PUSCHs scheduled by the third downlink control information.

18. The apparatus of claim 17 , wherein one or more rows in a TDRA table corresponding to the third downlink control information include multiple SLIVs.

19. a second receiving unit for receiving a PUSCH configuration including a third configuration parameter for configuring a number of repetitions; The apparatus of claim 17, wherein a CRC of the third downlink control information is scrambled by a CS-RNTI, and the third configuration parameter is applied to the third downlink control information.

20. 20. The apparatus of claim 19, wherein applying the third configuration parameter to the third downlink control information includes applying the third configuration parameter to one or more of PUSCHs scheduled by the third downlink control information.

Images