Resource Determination Method, Apparatus and Terminal

Abstract

The present application discloses a resource determination method, apparatus, and terminal, belonging to the field of communication technologies. The specific implementation solution includes: receiving a first DCI; the first DCI is a non-backoff DCI format, and at least one row index in the time-domain resource allocation table associated with the non-backoff DCI format indicates the time-domain transmission resources of multiple physical uplink shared channels (PUSCH); the first DCI is used to schedule the transmission of PUSCH on an unlicensed band; determining the time-domain resource allocation table used when transmitting PUSCH according to the following: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and the scrambling identifier of the first DCI. Thus, when using a DCI in the non-backoff DCI format to schedule the transmission of PUSCH on an unlicensed band, the time-domain resource allocation table used when transmitting PUSCH can be clarified.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a method, apparatus, and terminal for resource determination. Background Art

[0002] In the prior art, it is possible to support Downlink Control Information (DCI) in a non-backoff DCI format to schedule the transmission of a Physical Uplink Shared Channel (PUSCH) on an unlicensed band. However, in this case, it is not clear which time-domain resource allocation table to use for transmitting the PUSCH. Summary of the Invention

[0003] The objective of the embodiments of this application is to provide a method, apparatus, and terminal for resource determination, so as to solve the problem that when using DCI in a non-backoff DCI format to schedule the transmission of a PUSCH on an unlicensed band, it is not clear which time-domain resource allocation table to use for transmitting the PUSCH.

[0004] To solve the above technical problem, this application is implemented as follows:

[0005] In a first aspect, a method for resource determination is provided, which is applied to a terminal and includes:

[0006] Receiving a first DCI; wherein the first DCI is in a non-backoff DCI format, and at least one row index in the time-domain resource allocation table associated with the non-backoff DCI format indicates the time-domain transmission resources of multiple PUSCHs; the first DCI is used to schedule the transmission of a PUSCH on an unlicensed band;

[0007] Determining the time-domain resource allocation table used when transmitting the PUSCH according to the following: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and the scrambling identifier of the first DCI.

[0008] In a second aspect, a resource determination apparatus is provided, which is applied to a terminal.

[0009] A receiving module, configured to receive a first DCI; wherein the first DCI is in a non-backoff DCI format, and at least one row index in the time-domain resource allocation table associated with the non-backoff DCI format indicates the time-domain transmission resources of multiple PUSCHs; the first DCI is used to schedule the transmission of a PUSCH on an unlicensed band;

[0010] A determining module, configured to determine the time-domain resource allocation table used when transmitting the PUSCH according to the following: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and the scrambling identifier of the first DCI.

[0011] In a third aspect, a terminal is provided, which includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the resource determination method described in the first aspect are implemented.

[0012] In a fourth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the resource determination method described in the first aspect are implemented.

[0013] In a fifth aspect, a chip is provided, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the resource determination method described in the first aspect.

[0014] In an embodiment of the present application, after receiving a first DCI, the first DCI is in a non-backoff DCI format. At least one row index in the time-domain resource allocation table associated with the non-backoff DCI format indicates the time-domain transmission resources of multiple PUSCHs. For the first DCI to schedule the transmission of PUSCH on an unlicensed band, the time-domain resource allocation table used when transmitting the PUSCH can be determined according to whether the transmission scheduled by the first DCI is an initial transmission or a retransmission and / or the scrambling identifier of the first DCI. Thus, the time-domain resource allocation table used when transmitting the PUSCH in this case can be clarified. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a block diagram of a wireless communication system provided by an embodiment of the present application;

[0016] Figure 2 is a flowchart of a resource determination method provided by an embodiment of the present application;

[0017] Figure 3A is a schematic diagram of a time-domain resource allocation table in Example 1 of the present application;

[0018] Figure 3B is a schematic diagram of a time-domain resource allocation table in Example 2 of the present application;

[0019] Figure 4 is a schematic structural diagram of a resource determination device provided by an embodiment of the present application;

[0020] Figure 5 is a schematic structural diagram of a terminal provided by an embodiment of the present application;

[0021] Figure 6 is a schematic structural diagram of another terminal provided by an embodiment of the present application. DETAILED DESCRIPTION

[0022] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0023] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are usually of the same type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, the "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally means that the related objects before and after are in an "or" relationship.

[0024] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. However, the following description describes the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0025] Figure 1A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle user equipment (Vehicle User Equipment, VUE), a pedestrian user equipment (Pedestrian User Equipment, PUE), etc. terminal-side devices. Wearable devices include: bracelets, earphones, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can be a base station or a core network. Among them, the base station can be referred to as Node B, evolved Node B, access point, base transceiver station (Base Transceiver Station, BTS), radio base station, radio transceiver, basic service set (Basic Service Set, BSS), extended service set (Extended Service Set, ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0026] To facilitate the understanding of the embodiments of the present application, the following content is first described.

[0027] In future communication systems, the unlicensed band can be used as a supplement to the licensed band to help operators expand the capacity of services. Since the unlicensed band is shared by multiple radio access technologies (RATs), such as Wi-Fi, radar, LTE-based Licensed-Assisted Access (LTE-LAA), etc., in some countries or regions, the use of the unlicensed band must comply with regulatory regulations to ensure that all devices can fairly share this resource, such as Listen Before Talk (LBT), Maximum Channel Occupancy Time (MCOT), etc. When a transmission node needs to send information, it is required to first perform LBT on the specified wireless channel and conduct Energy Detection (ED) on the surrounding wireless transmission environment. When the energy is below a certain threshold, the channel is determined to be idle, and then transmission can begin. Otherwise, the channel is determined to be busy, and the transmission node cannot send. The transmission node can be a base station, UE, Wi-Fi AP, etc. After the transmission node starts transmission, the occupied channel time cannot exceed the MCOT.

[0028] For the uplink transmission mode, it can be divided into dynamic grant based and configured grant based. Further, the uplink transmission of Configured Grant (CG) is divided into two subtypes: Type 1 (such as Type 1 PUSCH transmissions with a configured grant) and Type 2 (such as Type 2 PUSCH transmissions with a configured grant). Among them, all transmission parameters of the Type 1 PUSCH transmission with a configured grant are semi-statically configured by the higher layer, and its transmission resources appear periodically. For the Type 2 PUSCH transmission with a configured grant, its transmission parameters are jointly configured and indicated by the higher layer and the physical layer. The higher layer mainly semi-statically configures the period of the transmission resources, and the physical layer mainly indicates transmission parameters such as Modulation and Coding Scheme (MCS), specific time-frequency resources, and the number of transmission layers.

[0029] It should be noted that the retransmission of CG PUSCH can be scheduled based on DCI, that is, both fallback DCI formats such as DCI format 0_0 and non-fallback DCI formats such as DCI format 0_1 can be used to schedule the retransmission of CG PUSCH. The cyclic redundancy check (CRC) of this DCI format 0_0 and DCI format 0_1 is scrambled using the configured scheduling-radio network temporary identity (CS-RNTI), and the value of the new data indication (NDI) field in the DCI is set to 1. When the CG PUSCH retransmission is DCI-scheduled, for its higher-layer parameters, except for the parameters related to uplink power and modulation and coding scheme which use the parameters of CG PUSCH, other parameters use the parameters of DG PUSCH. It can be considered that the retransmission of CGPUSCH is a dynamically scheduled transmission.

[0030] For the uplink repeated transmission type, the mechanism of slot-based repeated transmission is called PUSCH repetitionType A, that is, K repeated transmissions need to occupy K slots, and the time resources (transmission start positions) occupied by data transmission in each slot are the same. If the number of repeated transmissions is greater than 1, the data can only be transmitted in a single layer (single-layer). The mechanism of sub-slot-based repeated transmission is called PUSCH repetition Type B, that is, K nominal repeated transmissions can be continuously transmitted "back-to-back" in one slot. When the time-domain resource of a nominal transmission crosses the slot boundary or there are invalid or unavailable resources or symbols in this time-domain resource, such as downlink symbols, this nominal transmission will be divided into multiple actual repeated transmissions by the slot or invalid resources and symbols.

[0031] 1) For the time-domain resource allocation of a single PUSCH (Single-PUSCH) in the unlicensed band (such as NR-U), whether it is DG PUSCH or CG PUSCH, if the activated or scheduled DCI format is the fallback DCI format, that is, DCI format 0_0, the terminal can only transmit 1 PUSCH. Correspondingly, each row of the time-domain resource allocation table configured by the higher layer only determines the time-domain resources of a single PUSCH.

[0032] Furthermore, for Type 1 CG PUSCH, the time-domain resources of the authorized-scheduled PUSCH are determined by the higher-layer parameter timeDomainAllocation. The value m of timeDomainAllocation provides the row index m + 1 pointing to the determined time-domain resource allocation table (determine whether this time-domain resource allocation table is associated with DCI format 0_0 or DCI format 0_1 according to other higher-layer parameters of Type 1 CG PUSCH).

[0033] For Type 2 CG PUSCH, the time-domain resources of the authorized-scheduled PUSCH are determined by the time-domain resource allocation field in the activated DCI format. The determined time-domain resource allocation table is associated with the activated DCI format. That is, if the activated DCI is DCI format 0_0, the time-domain resource allocation table used is the one associated with DCI format 0_0 configured by the higher layer. If the activated DCI is DCI format 0_1, the time-domain resource allocation table used is the one associated with DCI format 0_1 configured by the higher layer.

[0034] 2) For the time-domain resource allocation of the multi-PUSCH for dynamic scheduling (DG) in the unlicensed band (such as NR-U), this multi-PUSCH is scheduled by a single DCI and can only use non-fallback DCI formats (non-fallback DCI formats), that is, the uplink DCI format(s) other than DCI format 0_0, such as DCI format 0_1. Scheduling 1 to multiple consecutive PUSCHs in time can save the overhead of the base station sending DCI, reduce the UE's need to perform LBT, and reduce the need to introduce multiple uplink-downlink switching points within the channel occupancy time (COT) initiated by the base station.

[0035] The time-domain resource allocation table associated with the non-backoff DCI format, such as DCI format 0_1 (taking DCI format 0_1 as an example here, but not limited to this, applicable to all non-backoff DCI formats), is configured by the higher layer. Each row of this time-domain resource allocation table can determine the time-domain resource allocation of one to multiple PUSCHs (up to 8 at most). Each PUSCH corresponds to a separate pair of start and length indicator values (SLIV) and demodulation reference signal (DM-RS) mapping type. The K2 parameter in each row indicates the slot offset of the slot where the first PUSCH is located relative to the slot where the scheduling DCI is located. DCI format 0_1 indicates the scheduling of one to multiple PUSCHs determined by a certain row in the time-domain resource allocation table configured by the higher layer by indicating the index of a certain row, and the number of scheduled PUSCHs is determined by the number of valid SLIVs in this row.

[0036] 3) For the time-domain resource allocation of the authorized scheduling (CG) of Multi-PUSCH in the unlicensed band (such as NR-U), for the transmission of Type1 CG PUSCH and Type2 CG PUSCH, the network side configures the higher layer parameters cg-nrofSlots-r16 and cg-nrofPUSCH-InSlot-r16 for the terminal. Among them, cg-nrofSlots-r16 indicates the number of consecutive slots allocated in the CG period. cg-nrofPUSCH-InSlot-r16 indicates how many consecutive CG-PUSCH candidate transmission positions are allocated within one slot. SLIV indicates the start symbol S and the transmission length L of the first CG PUSCH in the transmission slot of CG. For all consecutive CG-PUSCH candidate transmission positions within one slot, their transmission lengths are the same. In cg-nrofSlots-r16 consecutive slots, the CG PUSCH candidate transmission positions and lengths are the same, that is, the transmission lengths of Multi-PUSCH are the same.

[0037] In the unlicensed band (such as NR-U), the transmission of multiple different CG PUSCHs can be supported, and the time-domain transmission lengths of these multiple different CG PUSCHs are the same, that is, L is the same. In addition, the transmission of multiple different DG PUSCHs can also be supported, but the time-domain transmission lengths of these multiple different DG PUSCHs can be different, that is, the time-domain resource allocation table associated with the configured DCI format 0_1 has a separate pair (S, L) for each scheduled PUSCH, and the Ls of multiple PUSCHs can be different.

[0038] Therefore, in addition to solving the above problems to be solved, the present application also needs to solve the following specific problems: 1) When the activation of CGPUSCH or PUSCH carrying semi-persistent channel state information (SP-CSI) uses DCI format 0_1, it is not clear which time-domain resource allocation table indicated by the time-domain resource allocation field in the activation DCI is (associated with which DCI format) to ensure that the transmission lengths of different CG PUSCs or PUSCHs carrying SP-CSI are the same. 2) When the retransmission of CG PUSCH uses DCI format 0_1, it is not clear whether the corresponding DCI can schedule the retransmissions of multiple different CG PUSCHs or only the retransmission of 1 CG PUSCH, nor is it clear which time-domain resource allocation table is for the one or more CG-PUSCHs scheduled for retransmission (associated with which DCI format).

[0039] In the embodiments of the present application, for the coexistence of the time-domain resource allocation table for multi-PUSCH (PUSCH-TimeDomainResourceAllocationListForMultiPUSCH) and the time-domain resource allocation table for DCI format 0_1 (pusch-TimeDomainAllocationList-ForDCIformat0_1), there may be but are not limited to any of the following situations:

[0040] Situation 1: The high layer is not supported to configure PUSCH-TimeDomainResourceAllocationListForMultiPUSCH and pusch-TimeDomainAllocationList-ForDCIformat0_1 simultaneously.

[0041] Scenario 2: If the repetition type of pusch-TimeDomainAllocationList-ForDCIformat0_1 configured by the higher layer is PUSCH repetition Type B, the higher layer is not supported to configure PUSCH-TimeDomainResourceAllocationListForMultiPUSCH and pusch-TimeDomainAllocationList-ForDCIformat0_1 simultaneously; otherwise, the higher layer can configure PUSCH-TimeDomainResourceAllocationListForMultiPUSCH and pusch-TimeDomainAllocationList-ForDCIformat0_1 simultaneously.

[0042] Scenario 3: If the repetition type of pusch-TimeDomainAllocationList-ForDCIformat0_1 configured by the higher layer is PUSCH repetition Type B or PUSCH repetition Type A, and the higher layer configures the number of repetitions (numberofrepetition) in the time domain resource allocation table, the higher layer is not supported to configure PUSCH-TimeDomainResourceAllocationListForMultiPUSCH and pusch-TimeDomainAllocationList-ForDCIformat0_1 simultaneously; otherwise, the higher layer can configure PUSCH-TimeDomainResourceAllocationListForMultiPUSCH and pusch-TimeDomainAllocationList-ForDCIformat0_1 simultaneously.

[0043] The resource determination method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings, through specific embodiments and their application scenarios.

[0044] Please refer to Figure 2 , Figure 2 which is a flowchart of a resource determination method provided by an embodiment of the present invention. This method is applied to a terminal. As Figure 2 shown, the method includes the following steps:

[0045] Step 21: Receive the first DCI.

[0046] Among them, the first DCI is a non-backoff DCI format, and at least one row index in the time-domain resource allocation table associated with the non-backoff DCI format indicates the time-domain transmission resources of multiple PUSCHs. The first DCI is used to schedule the transmission of PUSCH on an unlicensed band.

[0047] Step 22: Determine the time-domain resource allocation table used when transmitting PUSCH according to the following: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and the scrambling identifier of the first DCI.

[0048] It should be noted that the scrambling identifier of the first DCI includes, but is not limited to, CS-RNTI, SP-CSI-RNTI, etc. When the scrambling identifier of the first DCI is CS-RNTI, the first DCI can activate or schedule the transmission of CG PUSCH. When the scrambling identifier of the first DCI is SP-CSI-RNTI, the first DCI can activate or schedule the transmission of PUSCH carrying SP-CSI.

[0049] In the resource determination method of the embodiments of the present application, after receiving the first DCI, the terminal can determine the time-domain resource allocation table used when transmitting PUSCH according to whether the transmission scheduled by the first DCI is an initial transmission or a retransmission and / or the scrambling identifier of the first DCI. Thus, the time-domain resource allocation table used when transmitting PUSCH can be clarified.

[0050] In one implementation, for the configuration of cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16, and / or the frequency band where the Type 2 CG PUSCH is located is an unlicensed band, when a non-backoff DCI format such as DCIformat 0_1 is used to activate the Type 2 CG PUSCH, or to activate the PUSCH carrying SP-CSI, and at least one row index in the time-domain resource allocation table configured by the higher layer associated with the DCIformat 0_1 indicates the time-domain transmission resources (S, L) of the PUSCH including multiple different transport blocks (TBs), the Ls of the multiple different PUSCHs can be the same or different, and the UE can determine the time-domain resource allocation table used when transmitting PUSCH according to at least one of the following:

[0051] 1) The type of operating frequency band (whether it is an unlicensed band or shared spectrum channel access);

[0052] 2) Specific RRC parameters (such as cg-nrofPUSCH-InSlot-r16, cg-nrofSlots-r16): Whether this parameter is configured or the value of this parameter is a specific value;

[0053] 3) Scrambling identifier of DCI; such as CS-RNTI, SP-CSI-RNTI, etc.;

[0054] 4) Whether the transmission scheduled by DCI is an initial transmission or a retransmission.

[0055] In the embodiments of the present application, when the transmission scheduled by the first DCI is an initial transmission and the scrambling identifier of the first DCI is CS-RNTI or SP-CSI-RNTI, the terminal can determine to use the time-domain resource allocation table associated with the non-fallback DCI format (i.e., the DCI format of the first DCI), or determine to use the time-domain resource allocation table associated with the fallback DCI format (DCI format 0_0). The time-domain resource allocation table associated with the DCI format 0_0 can be optionally the time-domain resource allocation table associated with the uplink DCI format 0_0 received in the UE-specific search space.

[0056] Optionally, after determining to use the time-domain resource allocation table associated with the non-fallback DCI format, the terminal can use at least one of the following to transmit CG PUSCH or PUSCH carrying SP-CSI:

[0057] 1) The time-domain transmission resource of the predefined PUSCH in the time-domain resource allocation table associated with the non-fallback DCI format.

[0058] For example, after the user / terminal UE determines to use the time-domain resource allocation table associated with the non-fallback DCI format, it can only use the time-domain transmission resource of 1 predefined PUSCH, that is, the S and L of the specific PUSCH, and ignore other PUSCH time-domain transmission resources.

[0059] Optionally, the above predefined PUSCH can be any one of the following:

[0060] Ⅰ. The first PUSCH indicated by the time-domain resource allocation table associated with the non-fallback DCI format;

[0061] II. The first valid PUSCH indicated by the time-domain resource allocation table associated with this non-backoff DCI format. That is, the time-domain transmission resource of this PUSCH has not become invalid for other reasons, such as the presence of downlink (DL) symbols or downlink transmissions in the indicated time-domain transmission resource, or the indicated time-domain transmission resource is indicated as unavailable / invalid by other higher-layer configured or dynamically scheduled signaling.

[0062] 2) The time-domain transmission resource of the PUSCH indicated by the first row index in the time-domain resource allocation table associated with the non-backoff DCI format, where the first row index indicates the time-domain transmission resource of a PUSCH.

[0063] For example, after the user / terminal UE determines to use the time-domain resource allocation table associated with this non-backoff DCI format, it can only use the row index that schedules one PUSCH.

[0064] 3) The time-domain transmission resource of the PUSCH indicated by the second row index in the time-domain resource allocation table associated with the non-backoff DCI format, where the second row index indicates the time-domain transmission resources of multiple PUSCHs, and the transmission lengths of these multiple PUSCHs are the same.

[0065] For example, after the user / terminal UE determines to use the time-domain resource allocation table associated with this non-backoff DCI format, it can only use the row index that schedules multiple PUSCHs and the transmission lengths of these multiple PUSCHs are all the same.

[0066] In this way, by means of the above three time-domain transmission resources, it can be ensured that the transmission lengths of different CG PUSCHs or PUSCHs carrying SP-CSI are the same, and thus, on the premise of ensuring the flexibility of network scheduling / configuration, it can be ensured that the network side and the terminal side have the same understanding of the time-domain resources used.

[0067] Optionally, the situations where the terminal determines to use the time-domain resource allocation table associated with the backoff DCI format can include any one of the following:

[0068] 1) When the time-domain resource allocation table associated with the backoff DCI format is configured, or when both the time-domain resource allocation table associated with the non-backoff DCI format and the time-domain resource allocation table associated with the backoff DCI format are configured, determine to use the time-domain resource allocation table associated with the backoff DCI format.

[0069] 2) When the preset high-layer parameters are configured, determine to use the time-domain resource allocation table associated with the fallback DCI format. The preset high-layer parameters limit that the terminal does not support the time-domain resource allocation table associated with the non-fallback DCI format. At this time, only the fallback DCI format can be used to activate and / or deactivate the uplink configured transmission, and the non-fallback DCI format cannot be used to activate and / or deactivate the uplink configured transmission, and the time-domain resource allocation table associated with the fallback DCI format is used.

[0070] For example, for the configuration of cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16, or the band where the PUSCH is located is an unlicensed band, the terminal does not support the DCI scrambled by CS-RNTI / SP-CSI-RNTI to activate the transmission of CG-PUSCH and the PUSCH carrying SP-CSI.

[0071] For instance, for Figure 3A the time-domain resource allocation table associated with the DCI format 0_1 shown in, when transmitting the PUSCH, it is possible to select only one time-domain transmission resource of the PUSCH indicated by row index 1 for transmission, or select one time-domain transmission resource of the PUSCH indicated by row index 1 and the time-domain transmission resources with the same transmission length (L = 4) of multiple PUSCHs indicated by row index 2, or directly select the time-domain resource allocation table associated with this DCI format 0_1 for transmission.

[0072] In the embodiments of the present application, when the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the terminal can determine to use the time-domain resource allocation table associated with the non-fallback DCI format (i.e., the DCI format of the first DCI), or determine to use the time-domain resource allocation table associated with the fallback DCI format (DCI format 0_0) when retransmitting a previously failed CG PUSCH, or only supporting the retransmission of a previously failed CG PUSCH.

[0073] Optionally, after determining to use the time-domain resource allocation table associated with the non-fallback DCI format, the terminal can use at least one of the following to retransmit the previously failed CG PUSCH:

[0074] 1) The predefined time-domain transmission resources of the PUSCH in the time-domain resource allocation table associated with the non-fallback DCI format.

[0075] For example, after the user / terminal UE determines to use the time-domain resource allocation table associated with the non-backoff DCI format, it can only use the predefined time-domain transmission resources of 1 PUSCH, that is, the S and L of the specific PUSCH, and ignores other time-domain transmission resources of the PUSCH.

[0076] Optionally, the above predefined PUSCH can be any one of the following:

[0077] Ⅰ. The first PUSCH indicated by the time-domain resource allocation table associated with the non-backoff DCI format;

[0078] Ⅱ. The first valid PUSCH indicated by the time-domain resource allocation table associated with the non-backoff DCI format.

[0079] 2) The time-domain transmission resources of the PUSCH indicated by the first row index in the time-domain resource allocation table associated with the non-backoff DCI format, and the first row index indicates the time-domain transmission resources of one PUSCH.

[0080] For example, after the user / terminal UE determines to use the time-domain resource allocation table associated with the non-backoff DCI format, it can only use the row index that schedules 1 PUSCH.

[0081] 3) The time-domain transmission resources of the PUSCH indicated by the second row index in the time-domain resource allocation table associated with the non-backoff DCI format, and the second row index indicates the time-domain transmission resources of multiple PUSCHs, and the transmission lengths of the multiple PUSCHs are the same.

[0082] For example, after the user / terminal UE determines to use the time-domain resource allocation table associated with the non-backoff DCI format, it can only use the row index that schedules multiple PUSCHs and the transmission lengths of the multiple PUSCHs are the same.

[0083] For example, Figure 3B For the time-domain resource allocation table associated with DCI format 0_1 shown in, where U represents the uplink time slot, D represents the downlink time slot, and F represents the special time slot. When retransmitting PUSCH#2, the time-domain transmission resources with the same transmission length (L = 4) of multiple PUSCHs indicated by row index3 can be selected, but since there is a downlink (D) in the first time-domain transmission resource, it is abandoned; or the first valid PUSCH time-domain resource can be used to retransmit PUSCH#2, with a transmission length of 5, and the previous time-domain transmission resources are invalid due to the presence of a downlink (D).

[0084] Optionally, in the case of retransmitting a previously transmitted CG PUSCH that failed, the cases where the terminal determines to use the time-domain resource allocation table associated with the fallback DCI format may include any of the following:

[0085] 1) When the time-domain resource allocation table associated with the fallback DCI format is configured, or when both the time-domain resource allocation table associated with the non-fallback DCI format and the time-domain resource allocation table associated with the fallback DCI format are configured, determine to use the time-domain resource allocation table associated with the fallback DCI format.

[0086] 2) When the terminal is configured with a preset high-layer parameter, determine to use the time-domain resource allocation table associated with the fallback DCI format; the preset high-layer parameter is used to restrict the terminal from supporting the time-domain resource allocation table associated with the non-fallback DCI format.

[0087] In the embodiments of the present application, when the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the terminal determines to use the time-domain resource allocation table associated with the non-fallback DCI format when it supports retransmitting multiple previously transmitted CG PUSCHs that failed, and the sequence numbers of the Hybrid Automatic Repeat reQuest (HARQ) processes of the multiple previously transmitted CG PUSCHs that failed increase or decrease continuously by a step of 1.

[0088] Further, after determining to use the time-domain resource allocation table associated with the non-fallback DCI format, the terminal may retransmit the multiple previously transmitted CG PUSCHs that failed by using the time-domain transmission resources of the PUSCH indicated by the third row index in the time-domain resource allocation table associated with the non-fallback DCI format; wherein, the third row index is indicated by the first DCI, and the number of the time-domain transmission resources of the PUSCH indicated by the third row index is greater than or equal to the number of the multiple previously transmitted CG PUSCHs that failed.

[0089] For example, for Type 1 CG PUSCH and / or Type 2 CG PUSCH configured on the NR unlicensed band, when the non-fallback DCI format received by the UE, such as DCI format 0_1, is used to schedule the retransmission of Type 1 or Type 2 CG PUSCH, and at least one row index in the time-domain resource allocation table associated with the DCI format 0_1 configured by the high layer indicates the time-domain transmission resources (S, L) of multiple different PUSCHs, then:

[0090] (1) If the retransmission of the CG PUSCH only supports retransmitting one previously transmitted CG PUSCH that failed, the UE determines to use the time-domain resource allocation table associated with the non-fallback DCI format, or determines to use the time-domain resource allocation table associated with the fallback DCI format. The specific method is as shown above and will not be elaborated here.

[0091] (2) If the indexes of the HARQ processes of multiple previously transmitted CG PUSCHs that failed increase or decrease continuously in steps of 1, the retransmission can support these multiple previously transmitted CG PUSCHs that failed; otherwise, it only supports retransmitting one previously transmitted CG PUSCH that failed. That is, if there are multiple SLIVs in the resource allocation table indicated by the base station, it means that the indexes (HARQ Process Number, HPN) of the HARQ processes of these multiple retransmitted PUSCHs are continuous; otherwise, the base station can only indicate a single SLIV in the resource allocation table and cannot indicate multiple SLIVs.

[0092] In an implementation, if multiple CG PUSCHs with continuous HARQ process indexes are retransmitted, each scheduled retransmitted CG-PUSCH has a separate pair (S, L), and the Ls of multiple PUSCHs can be the same or different.

[0093] In the embodiments of this application, when the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the terminal can determine to use the time-domain resource allocation table associated with the non-fallback DCI format (i.e., the DCI format of the first DCI). Then, according to multiple first indication fields included in the first DCI, using the first time-domain transmission resource, retransmit the first CG PUSCH and ignore the second CG PUSCH and the second time-domain transmission resource corresponding to the second CG PUSCH; where each first indication field corresponds to a CG PUSCH, the first indication field corresponding to the first CG PUSCH is a preset value, and the first indication field corresponding to the second CG PUSCH is not a preset value; the first time-domain transmission resource and the second time-domain transmission resource are: the time-domain transmission resources of the PUSCH indicated by the fourth-row index indicated by the first DCI in the time-domain resource allocation table associated with the non-fallback DCI format.

[0094] Optionally, the above first indication field can be selected as the New Data Indication (NDI) field, or can also be other fields, and there is no limitation on this.

[0095] For example, if the retransmission of the CG PUSCH can support retransmitting one or more previously failed CG PUSCHs, in the DCI scheduling the retransmission, each PUSCH has an independent NDI field and a Redundancy Version (RV) field. When NDI = 1 (and RV is not equal to 0), for the PUSCH corresponding to the user retransmission, its resources are indicated by the corresponding SLIV; when NDI = 0 (and RV is equal to 0), the user ignores the corresponding PUSCH and the SLIV corresponding to the PUSCH.

[0096] As an alternative embodiment, for the method of PUSCH resource allocation associated with the DCI format 0_1 scrambled by the CS-RNTI for activation, which configures cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16, and / or the band where the PUSCH is located is an unlicensed band, the same or different methods as those for the PUSCH resource allocation associated with the DCI format 0_1 scrambled by the CS-RNTI for retransmission can be adopted.

[0097] For example: for the configuration of cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16, or the band where the PUSCH is located is an unlicensed band, the PUSCH resource allocation table associated with the DCI format 0_1 scrambled by the CS-RNTI for activation is the same as the PUSCH resource allocation table associated with the DCI format 0_0, or is the resource allocation table for a single PUSCH (when both the single and multi-PUSCH resource allocation tables are configured); the PUSCH resource allocation table associated with the DCI format 0_1 scrambled by the CS-RNTI for retransmission is the same as the PUSCH resource allocation table associated with the DCI format 0_1 scrambled by the C-RNTI, or is the resource allocation table for a multi-PUSCH (when both the single and multi-PUSCH resource allocation tables are configured).

[0098] It should be noted that for the resource determination method provided in the embodiments of this application, the execution subject can be a resource determination device, or a control module in the resource determination device for executing the resource determination method. In the embodiments of this application, the resource determination method is executed by the resource determination device as an example to illustrate the resource determination device provided in the embodiments of this application.

[0099] Please refer to Figure 4 , Figure 4The following is a schematic structural diagram of a resource determination device provided by an embodiment of the present invention, which is applied to a terminal. For example, Figure 4 As shown, the resource determination device 40 includes:

[0100] A receiving module 41, configured to receive a first DCI; wherein, the first DCI is a non-backoff DCI format, and at least one row index in the time domain resource allocation table associated with the non-backoff DCI format indicates the time domain transmission resources of multiple PUSCHs; the first DCI is used to schedule the transmission of PUSCH on an unlicensed frequency band;

[0101] A determining module 42, configured to determine the time domain resource allocation table used when transmitting PUSCH according to the following: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and the scrambling identifier of the first DCI.

[0102] Optionally, when the transmission scheduled by the first DCI is an initial transmission and the scrambling identifier of the first DCI is CS-RNTI or SP-CSI-RNTI, the determining module 42 is specifically configured to:

[0103] Determine to use the time domain resource allocation table associated with the non-backoff DCI format;

[0104] Or, determine to use the time domain resource allocation table associated with the backoff DCI format.

[0105] Optionally, after determining to use the time domain resource allocation table associated with the non-backoff DCI format, the device further includes:

[0106] A transmission module, configured to, after determining to use the time domain resource allocation table associated with the non-backoff DCI format, transmit a CG PUSCH or a PUSCH carrying SP-CSI by using at least one of the following:

[0107] The pre-defined time domain transmission resources of PUSCH in the time domain resource allocation table associated with the non-backoff DCI format;

[0108] The time domain transmission resources of the PUSCH indicated by the first row index in the time domain resource allocation table associated with the non-backoff DCI format; wherein, the first row index indicates the time domain transmission resources of one PUSCH;

[0109] The time domain transmission resources of the PUSCH indicated by the second row index in the time domain resource allocation table associated with the non-backoff DCI format; wherein, the second row index indicates the time domain transmission resources of multiple PUSCHs, and the transmission lengths of the multiple PUSCHs are the same.

[0110] Optionally, the pre-defined PUSCH is any one of the following:

[0111] The first PUSCH indicated by the time domain resource allocation table associated with the non-backoff DCI format;

[0112] The first valid PUSCH indicated by the time domain resource allocation table associated with the non-backoff DCI format.

[0113] Optionally, the determining module 42 is further configured to perform any one of the following:

[0114] When the time domain resource allocation table associated with the backoff DCI format is configured, or when both the time domain resource allocation table associated with the non-backoff DCI format and the time domain resource allocation table associated with the backoff DCI format are configured, determine to use the time domain resource allocation table associated with the backoff DCI format;

[0115] When a preset high-layer parameter is configured, determine to use the time domain resource allocation table associated with the backoff DCI format; wherein, the preset high-layer parameter is used to restrict the terminal from not supporting the time domain resource allocation table associated with the non-backoff DCI format.

[0116] Optionally, when the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module 42 is specifically configured to:

[0117] In the case that the terminal supports retransmitting a previously transmitted failed CG PUSCH, determine to use the time domain resource allocation table associated with the non-backoff DCI format, or determine to use the time domain resource allocation table associated with the backoff DCI format.

[0118] Optionally, the resource determining device 40 further includes:

[0119] A first retransmission module, configured to, after determining to use the time domain resource allocation table associated with the non-backoff DCI format, retransmit the previously transmitted failed CG PUSCH by using at least one of the following:

[0120] The time domain transmission resource of the predefined PUSCH in the time domain resource allocation table associated with the non-backoff DCI format;

[0121] The time domain transmission resource of the PUSCH indicated by the first row index in the time domain resource allocation table associated with the non-backoff DCI format; wherein, the first row index indicates the time domain transmission resource of a PUSCH;

[0122] The time domain transmission resource of the PUSCH indicated by the second row index in the time domain resource allocation table associated with the non-backoff DCI format; wherein, the second row index indicates the time domain transmission resources of multiple PUSCHs, and the transmission lengths of the multiple PUSCHs are the same.

[0123] Optionally, when the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module 42 is specifically configured to:

[0124] When the terminal supports retransmitting multiple previously failed CG PUSCHs, and the sequence numbers of the HARQ processes of the multiple previously failed CG PUSCHs are continuously incremented or decremented by 1, determine to use the time-domain resource allocation table associated with the non-backoff DCI format.

[0125] Optionally, the resource determining device 40 further includes:

[0126] A second retransmission module, configured to, after determining to use the time-domain resource allocation table associated with the non-backoff DCI format, retransmit the multiple previously failed CG PUSCHs by using the time-domain transmission resources of the PUSCH indicated by the third row index in the time-domain resource allocation table associated with the non-backoff DCI format; wherein, the third row index is indicated by the first DCI, and the number of the time-domain transmission resources of the PUSCH indicated by the third row index is greater than or equal to the number of the multiple previously failed CG PUSCHs.

[0127] Optionally, when the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module 42 is specifically configured to:

[0128] Determine to use the time-domain resource allocation table associated with the non-backoff DCI format.

[0129] Further, the resource determining device 40 further includes:

[0130] A processing module, configured to, according to multiple first indication fields included in the first DCI, retransmit the first CG PUSCH by using first time-domain transmission resources, and ignore the second CG PUSCH and the second time-domain transmission resources corresponding to the second CG PUSCH;

[0131] wherein each of the first indication fields corresponds to a CG PUSCH, the first indication field corresponding to the first CG PUSCH is a preset value, and the first indication field corresponding to the second CG PUSCH is not a preset value; the first time-domain transmission resources and the second time-domain transmission resources are resources in the time-domain transmission resources of the PUSCH indicated by the fourth row index indicated by the first DCI in the time-domain resource allocation table associated with the non-backoff DCI format.

[0132] The resource determination device in the embodiments of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include, but is not limited to, the types of the above-listed terminal 11, and the non-mobile terminal can be a server, a Network Attached Storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc., which are not specifically limited in the embodiments of the present application.

[0133] The resource determination device in the embodiments of the present application can be a device with an operating system. The operating system can be the Android operating system, the iOS operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

[0134] The resource determination device 40 provided in the embodiments of the present application can implement Figure 2 each process implemented by the method embodiments shown, and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0135] Optionally, as Figure 5 shown, the embodiments of the present application further provide a terminal 50, including a processor 51, a memory 52, a program or instruction stored on the memory 52 and executable on the processor 51. When the program or instruction is executed by the processor 51, it implements each process of the method embodiments shown above Figure 2 and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0136] Figure 6 It is a schematic diagram of the hardware structure of a terminal for implementing the embodiments of the present application.

[0137] The terminal 600 includes, but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, and a processor 610, etc.

[0138] Those skilled in the art can understand that the terminal 100 can further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 610 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 6 The terminal structure shown in

[0139] It should be understood that in the embodiments of the present application, the input unit 604 may include a Graphics Processing Unit (GPU) 6041 and a microphone 6042. The GPU 6041 processes the image data of static pictures or videos obtained by an image capturing device (such as a camera) in the video capture mode or the image capture mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. The other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0140] In the embodiments of the present application, after receiving the downlink data from the network side device, the radio frequency unit 601 processes it and sends it to the processor 610; in addition, it sends the uplink data to the network side device. Generally, the radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0141] The memory 609 can be used to store software programs or instructions and various data. The memory 609 mainly includes a program or instruction storage area and a data storage area. Among them, the program or instruction storage area can store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 609 may include a high-speed random access memory, and may also include a non-volatile memory. Among them, the non-volatile memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid state storage devices.

[0142] The processor 610 may include one or more processing units; optionally, the processor 610 may integrate an application processor and a modulation and demodulation processor. Among them, the application processor mainly processes the operating system, user interface, applications or instructions, etc., and the modulation and demodulation processor mainly processes wireless communications, such as a baseband processor. It can be understood that the above modulation and demodulation processor may not be integrated into the processor 610.

[0143] Among them, a radio frequency unit 601 is configured to receive a first DCI. Among them, the first DCI is a non-backoff DCI format, and at least one row index in the time domain resource allocation table associated with the non-backoff DCI format indicates the time domain transmission resources of multiple PUSCHs. The first DCI is used to schedule the transmission of PUSCH on an unlicensed frequency band.

[0144] A processor 610 is configured to determine a time domain resource allocation table used when transmitting PUSCH according to the following: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and the scrambling identifier of the first DCI.

[0145] The terminal 600 provided in the embodiments of the present application can implement Figure 2 each process implemented by the method embodiment shown and achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0146] The embodiments of the present application further provide a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements the above Figure 2 each process of the method embodiment shown and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0147] Among them, the processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc, etc.

[0148] The embodiments of the present application further provide a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a network-side device program or instruction to implement the above Figure 2 each process of the method embodiment shown and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0149] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip.

[0150] It should be noted that in this article, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without more limitations, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including such element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0151] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions for causing a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0152] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them fall within the protection scope of the present application.

Claims

1. A resource determination method, applied to a terminal, characterized in that, including: receiving first downlink control information (DCI); wherein, the first DCI is in a non-backoff DCI format, and at least one row index in a time domain resource allocation table associated with the non-backoff DCI format indicates time domain transmission resources of multiple physical uplink shared channels (PUSCH); the first DCI is used to schedule the PUSCH to be transmitted on an unlicensed frequency band; determining a time domain resource allocation table used when transmitting the PUSCH according to: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and a scrambling identifier of the first DCI; wherein, the time domain resource allocation table used when transmitting the PUSCH is associated with the non-backoff DCI format or a backoff DCI format; wherein, when the transmission scheduled by the first DCI is an initial transmission and the scrambling identifier of the first DCI is a configured scheduling radio network temporary identifier (CS-RNTI), the determining the time domain resource allocation table used when transmitting the PUSCH includes: determining to use the time domain resource allocation table associated with the non-backoff DCI format; the method further includes: transmitting a configured grant PUSCH (CG PUSCH) by using the time domain transmission resources of the PUSCH indicated by a first row index in the time domain resource allocation table associated with the non-backoff DCI format; wherein, the first row index indicates the time domain transmission resources of one PUSCH.

2. The method according to claim 1, characterized in that, the method further includes: transmitting a CG PUSCH by using at least one of the following: the time domain transmission resources of a predefined PUSCH in the time domain resource allocation table associated with the non-backoff DCI format; the time domain transmission resources of the PUSCH indicated by a second row index in the time domain resource allocation table associated with the non-backoff DCI format; wherein, the second row index indicates the time domain transmission resources of multiple PUSCH, and the transmission lengths of the multiple PUSCH are the same.

3. The method according to claim 2, wherein the predefined PUSCH is any one of the following: the first PUSCH indicated by the time domain resource allocation table associated with the non-backoff DCI format; the first valid PUSCH indicated by the time domain resource allocation table associated with the non-backoff DCI format.

4. The method according to claim 1, characterized in that the determining the time domain resource allocation table used when transmitting the PUSCH further includes any one of the following: when a time domain resource allocation table associated with a backoff DCI format is configured, or when both the time domain resource allocation table associated with the non-backoff DCI format and the time domain resource allocation table associated with the backoff DCI format are configured, determining to use the time domain resource allocation table associated with the backoff DCI format; when a preset higher layer parameter is configured, determining to use the time domain resource allocation table associated with the backoff DCI format; wherein, the preset higher layer parameter is used to restrict that the terminal does not support the time domain resource allocation table associated with the non-backoff DCI format.

5. The method according to claim 1, characterized in that, when the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining the time domain resource allocation table used when transmitting the PUSCH includes: In the case where the terminal supports retransmitting a previously transmitted failed CG PUSCH, determine to use the time-domain resource allocation table associated with the non-fallback DCI format, or determine to use the time-domain resource allocation table associated with the fallback DCI format.

6. The method according to claim 5, wherein After determining to use the time-domain resource allocation table associated with the non-fallback DCI format, the method further includes: Retransmit the previously transmitted failed CG PUSCH by using at least one of the following: The time-domain transmission resource of the predefined PUSCH in the time-domain resource allocation table associated with the non-fallback DCI format; The time-domain transmission resource of the PUSCH indicated by the first row index in the time-domain resource allocation table associated with the non-fallback DCI format; wherein, the first row index indicates the time-domain transmission resource of a PUSCH; The time-domain transmission resource of the PUSCH indicated by the second row index in the time-domain resource allocation table associated with the non-fallback DCI format; wherein, the second row index indicates the time-domain transmission resources of multiple PUSCHs, and the transmission lengths of the multiple PUSCHs are the same.

7. The method according to claim 1, wherein When the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determination of the time-domain resource allocation table used when transmitting the PUSCH includes: In the case where the terminal supports retransmitting multiple previously transmitted failed CG PUSCHs and the hybrid automatic repeat request (HARQ) process indexes of the multiple previously transmitted failed CG PUSCHs are continuously incremented or continuously decremented by a step of 1, determine to use the time-domain resource allocation table associated with the non-fallback DCI format.

8. The method according to claim 7, characterized in that After determining to use the time-domain resource allocation table associated with the non-fallback DCI format, the method further includes: Retransmit the multiple previously transmitted failed CG PUSCHs by using the time-domain transmission resource of the PUSCH indicated by the third row index in the time-domain resource allocation table associated with the non-fallback DCI format; wherein, the third row index is indicated by the first DCI, and the number of the time-domain transmission resources of the PUSCH indicated by the third row index is greater than or equal to the number of the multiple previously transmitted failed CG PUSCHs.

9. The method according to claim 1, characterized in that, When the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determination of the time-domain resource allocation table used when transmitting the PUSCH includes: Determine to use the time-domain resource allocation table associated with the non-fallback DCI format; After determining to use the time-domain resource allocation table associated with the non-fallback DCI format, the method further includes: According to multiple first indication fields included in the first DCI, retransmit the first CG PUSCH by using the first time-domain transmission resource, and ignore the second CG PUSCH and the second time-domain transmission resource corresponding to the second CG PUSCH; wherein, each of the first indication fields corresponds to a CG PUSCH, the first indication field corresponding to the first CG PUSCH is a preset value, and the first indication field corresponding to the second CG PUSCH is not a preset value; The first time-domain transmission resource and the second time-domain transmission resource are resources in the time-domain transmission resource of the PUSCH indicated by the fourth row index indicated by the first DCI in the time-domain resource allocation table associated with the non-backoff DCI format.

10. The method according to claim 1, wherein When the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the time-domain resource allocation table used when determining the transmission of the PUSCH includes: Determine to use the time-domain resource allocation table associated with the non-backoff DCI format.

11. The method according to any one of claims 1 to 10, characterized in that, The PUSCH transmission is a Type 1C G PUSCH transmission and / or a Type 2C G PUSCH transmission.

12. A resource determination device, applied to a terminal, characterized in that, It includes: A receiving module, configured to receive a first DCI; wherein, the first DCI is a non-backoff DCI format, and at least one row index in the time-domain resource allocation table associated with the non-backoff DCI format indicates the time-domain transmission resources of multiple PUSCHs; the first DCI is used to schedule the PUSCH to be transmitted on an unlicensed frequency band; A determining module, configured to determine the time-domain resource allocation table used when transmitting the PUSCH according to the following: whether the transmission scheduled by the first DCI is an initial transmission or a retransmission, and the scrambling identifier of the first DCI; wherein, the time-domain resource allocation table used when transmitting the PUSCH is associated with the non-backoff DCI format or the backoff DCI format; Wherein, when the transmission scheduled by the first DCI is an initial transmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module is specifically configured to: Determine to use the time-domain resource allocation table associated with the non-backoff DCI format; The device further includes: A transmission module, configured to transmit an authorized scheduled C G PUSCH by using the time-domain transmission resource of the PUSCH indicated by the first row index in the time-domain resource allocation table associated with the non-backoff DCI format; wherein, the first row index indicates the time-domain transmission resource of a PUSCH.

13. The device according to claim 12, wherein The transmission module is further configured to transmit the C G PUSCH by using at least one of the following: The pre-defined time-domain transmission resource of the PUSCH in the time-domain resource allocation table associated with the non-backoff DCI format; The time-domain transmission resource of the PUSCH indicated by the second row index in the time-domain resource allocation table associated with the non-backoff DCI format; wherein, the second row index indicates the time-domain transmission resources of multiple PUSCHs, and the transmission lengths of the multiple PUSCHs are the same.

14. The device according to claim 13, characterized in that, The pre-defined PUSCH is any one of the following: The first PUSCH indicated by the time-domain resource allocation table associated with the non-backoff DCI format; The first valid PUSCH indicated by the time-domain resource allocation table associated with the non-backoff DCI format.

15. The device according to claim 12, characterized in that, The determining module is further configured to perform any one of the following: When the time-domain resource allocation table associated with the fallback DCI format is configured, or when the time-domain resource allocation table associated with the non-fallback DCI format and the time-domain resource allocation table associated with the fallback DCI format are both configured, determine to use the time-domain resource allocation table associated with the fallback DCI format; When a preset high-layer parameter is configured, determine to use the time-domain resource allocation table associated with the fallback DCI format; wherein, the preset high-layer parameter is used to restrict that the terminal does not support the time-domain resource allocation table associated with the non-fallback DCI format.

16. The device according to claim 12, characterized in that, When the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module is specifically configured to: When the terminal supports retransmitting a previously transmitted failed CG PUSCH, determine to use the time-domain resource allocation table associated with the non-fallback DCI format, or determine to use the time-domain resource allocation table associated with the fallback DCI format.

17. The device according to claim 16, characterized in that, The apparatus further includes: A first retransmission module, configured to, after determining to use the time-domain resource allocation table associated with the non-fallback DCI format, retransmit the previously transmitted failed CG PUSCH by using at least one of the following: The predefined time-domain transmission resource of the PUSCH in the time-domain resource allocation table associated with the non-fallback DCI format; The time-domain transmission resource of the PUSCH indicated by the first row index in the time-domain resource allocation table associated with the non-fallback DCI format; wherein, the first row index indicates the time-domain transmission resource of a PUSCH; The time-domain transmission resource of the PUSCH indicated by the second row index in the time-domain resource allocation table associated with the non-fallback DCI format; wherein, the second row index indicates the time-domain transmission resources of multiple PUSCHs, and the transmission lengths of the multiple PUSCHs are the same.

18. The device according to claim 12, wherein, When the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module is specifically configured to: When the terminal supports retransmitting multiple previously transmitted failed CG PUSCHs, and the sequence numbers of the HARQ processes of the multiple previously transmitted failed CG PUSCHs increase or decrease continuously with a step of 1, determine to use the time-domain resource allocation table associated with the non-fallback DCI format.

19. The device according to claim 18, wherein The apparatus further includes: A second retransmission module, configured to, after determining to use the time-domain resource allocation table associated with the non-fallback DCI format, retransmit the multiple previously transmitted failed CG PUSCHs by using the time-domain transmission resource of the PUSCH indicated by the third row index in the time-domain resource allocation table associated with the non-fallback DCI format; wherein, the third row index is indicated by the first DCI, and the number of the time-domain transmission resources of the PUSCH indicated by the third row index is greater than or equal to the number of the multiple previously transmitted failed CG PUSCHs.

20. The device according to claim 12, wherein, When the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module is specifically configured to: Determine to use the time-domain resource allocation table associated with the non-backoff DCI format; The apparatus further includes: A processing module, configured to retransmit a first CG PUSCH by using first time-domain transmission resources according to multiple first indication fields included in the first DCI, and ignore a second CG PUSCH and second time-domain transmission resources corresponding to the second CG PUSCH; Wherein each of the first indication fields corresponds to a CG PUSCH, the first indication field corresponding to the first CG PUSCH is a preset value, and the first indication field corresponding to the second CG PUSCH is not a preset value; The first time-domain transmission resources and the second time-domain transmission resources are resources in the time-domain transmission resources of the PUSCH indicated by the fourth row index indicated by the first DCI in the time-domain resource allocation table associated with the non-backoff DCI format.

21. The device according to claim 12, characterized in that, When the transmission scheduled by the first DCI is a retransmission and the scrambling identifier of the first DCI is CS-RNTI, the determining module is specifically configured to: determine to use the time-domain resource allocation table associated with the non-backoff DCI format.

22. The device according to any one of claims 12 to 21, characterized in that The PUSCH transmission is a Type 1 CG PUSCH transmission and / or a Type 2 CG PUSCH transmission.

23. A terminal, characterized in that, It includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the resource determination method according to any one of claims 1 to 11 are implemented.

24. A readable storage medium, characterized in that, A program or instruction is stored on the readable storage medium. When the program or instruction is executed by a processor, the steps of the resource determination method according to any one of claims 1 to 11 are implemented.

Images