CN111770577A

CN111770577A - Method and device for determining transmission resources

Info

Publication number: CN111770577A
Application number: CN201910364667.2A
Authority: CN
Inventors: 徐修强; 陈雁; 吕永霞
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-03-30
Filing date: 2019-04-30
Publication date: 2020-10-13
Anticipated expiration: 2039-04-30
Also published as: CN111770577B

Abstract

In the method, a terminal and a network device may determine a time domain resource and an RV of one or more transmission occasions for transmitting a PUSCH or a PDSCH based on indication information indicating one entry in a time domain resource allocation table and the time domain resource allocation table. In the method, the table entry in the time domain resource allocation table may include information for indicating the RV, and in this case, the network device does not need to indicate the RV corresponding to the transmission opportunity through the DCI, so that the signaling overhead of the DCI may be reduced. The present application relates to the field of communications.

Description

Method and device for determining transmission resources

The present application claims priority of chinese patent application with application number 201910254156.5, entitled "method and apparatus for determining transmission resources" filed in 2019, 30/03.9, which is incorporated herein by reference in its entirety.

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for determining transmission resources.

Background

With the development of Virtual Reality (VR), Augmented Reality (AR), internet of things and other technologies, more and more terminals will be available in future networks, and the usage amount of network data will be increased continuously. Therefore, in the fifth generation (5G for short) communication system and the future evolution communication system, network resources become especially valuable, which needs to reduce signaling overhead as much as possible while satisfying communication requirements.

Disclosure of Invention

The application provides a method and a device for determining transmission resources, which can reduce signaling overhead of a communication system.

In order to achieve the purpose, the application provides the following technical scheme:

in a first aspect, a method for determining transmission resources is provided, including: the terminal receives indication information from network equipment, wherein the indication information is used for indicating one table entry in a time domain resource allocation table, and at least one table entry in the time domain resource allocation table comprises information used for indicating a plurality of time domain resources and information used for indicating one or more RVs; and the terminal determines the time domain resources and RVs of one or more transmission occasions for transmitting the PUSCH or the PDSCH according to the indication information and the time domain resource allocation table.

In the prior art, the table entry in the time domain resource allocation table is only used to determine the time domain resource of the transmission opportunity, and is not used to determine the RV used by the transmission opportunity, and the RV corresponding to each transmission opportunity needs to be additionally indicated by DCI. In the method provided in the first aspect, the entry in the time domain resource allocation table may include information for indicating an RV, and in this case, the network device does not need to indicate the RV corresponding to the transmission opportunity through the DCI, so that the signaling overhead of the DCI may be reduced.

In one possible implementation, the method further includes: the terminal receives configuration information from the network device, wherein the configuration information is used for configuring the time domain resource allocation table. The possible implementation mode can enable the terminal to obtain different time domain resource allocation tables possibly, thereby adapting to different requirements and improving the transmission efficiency.

In a possible implementation manner, the at least one entry in the time domain resource allocation table further includes a plurality of first offset values, and the plurality of first offset values are used to determine a time slot in which the time domain resource of the plurality of transmission occasions is located. In type1 uplink unlicensed transmission, the network device sends the value of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a time domain resource is located. To facilitate repeated transmission of data, information indicating a plurality of time domain resources may be included in one entry in the time domain resource allocation table. In this case, the terminal needs to determine the time slots where multiple time domain resources are located. At this time, the network device needs to send a plurality of values of timeDomainOffset through RRC signaling, so that the terminal determines the time slot in which the plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it needs to know the corresponding relationship between the values of the plurality of timeDomainOffset and the plurality of time domain resources, and therefore, the implementation process is complicated. According to the method, the time slots of the time domain resources of multiple transmission occasions are determined by configuring the first deviation values in the table entries in the time domain resource allocation table, so that the terminal can rapidly determine the time slots of the time domain resources, and the implementation complexity of the terminal is reduced.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value, and the method further includes: the terminal receives a PDCCH from the network equipment, the PDCCH carries DCI used for scheduling the PUSCH, the DCI carries the indication information, and the index of a time slot in which the DCI is located is n; correspondingly, the determining, by the terminal, the time domain resources of one or more transmission occasions for transmitting the PUSCH according to the indication information and the time domain resource allocation table includes: and the terminal determines the time slot where the time domain resource of the kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information and a second offset value contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

In a possible implementation manner, an index of a timeslot in which a time domain resource of a kth transmission opportunity of the one or more transmission opportunities is:

wherein u is_PUSCHParameter, u, characterizing the subcarrier spacing of the PUSCH_PDCCHIn order to characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the indication information, and C2 is a second offset value contained in the entry indicated by the indication information.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value, and the method further includes: the terminal receives a PDCCH from the network equipment, the PDCCH carries DCI used for scheduling the PDSCH, the DCI carries the indication information, and the index of a time slot in which the DCI is located is n; correspondingly, the determining, by the terminal, the time domain resources of one or more transmission occasions for transmitting the PDSCH according to the indication information and the time domain resource allocation table includes: and the terminal determines the time slot of the time domain resource of the kth transmission opportunity in the one or more transmission opportunities according to the subcarrier interval of the PDSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in a table entry indicated by the indication information and a second offset value contained in a table entry indicated by the indication information, wherein k is an integer greater than 0.

wherein u is_PDSCHFor characterizing subcarrier spacing of the PDSCHParameter u_PDCCHIn order to characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the indication information, and C2 is a second offset value contained in the entry indicated by the indication information.

In a possible implementation manner, the DCI further includes a redundancy version indication field, where when an entry indicated by the indication information includes information of RVs corresponding to multiple time domain resources for performing repeated transmission of data, the redundancy version indication field is used to determine the maximum number of the time domain resources for repeated transmission or the maximum number of times of the repeated transmission or the maximum number of time slots for the repeated transmission.

In one possible implementation, the method further includes: the terminal receives configuration information of uplink authorization-exempt transmission of type1 from the network equipment, wherein the configuration information comprises the configuration information of the indication information and a third offset value; and determining a time slot in which a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information, wherein k is an integer greater than 0. In type1 uplink unlicensed transmission, the value of timeDomainOffset is sent through RRC signaling so that the terminal determines a time slot in which a time domain resource is located. To facilitate repeated transmission of data, information indicating a plurality of time domain resources may be included in one entry in the time domain resource allocation table. In this case, the terminal needs to determine the time slots where multiple time domain resources are located. At this time, the network device needs to send a plurality of values of timeDomainOffset through RRC signaling, so that the terminal determines the time slot in which the plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it needs to know the corresponding relationship between the values of the plurality of timeDomainOffset and the plurality of time domain resources, and therefore, the implementation process is complicated. The method can enable the terminal to rapidly determine the time slots of the time domain resources at a plurality of transmission occasions by configuring a plurality of first offset values in the table entry in the time domain resource allocation table so as to determine the time slots of the time domain resources at a plurality of transmission occasions, thereby reducing the implementation complexity of the terminal.

In a possible implementation manner, at least one first time domain resource in the plurality of time domain resources corresponds to an RV with an index of 0, where the first time domain resource includes a time domain resource with a maximum number of symbols in the plurality of time domain resources. In the possible implementation manner, the time domain resource with the largest number of symbols in the multiple time domain resources corresponds to the RV0, so that more check bits are available in the data adopting RV0, and the decoding performance of the receiving end is improved.

In a possible implementation manner, values of the RV index corresponding to each of the at least one first time domain resource are cycled according to an arrangement of RV indexes in an RV sequence {0,2,3,1} or {0,3,0,3 }. In this possible implementation manner, when there are multiple time domain resources with the largest number of symbols in the multiple time domain resources, at least two time domain resources in the multiple time domain resources with the largest number of symbols correspond to different RVs. In this case, compared with the case that the same RV is used for all the time domain resources with the largest number of symbols, the decoding capability of the receiving end can be improved.

In a second aspect, a method for determining transmission resources is provided, including: the network equipment sends indication information to a terminal, wherein the indication information is used for indicating one table entry in a time domain resource allocation table, and at least one table entry in the time domain resource allocation table comprises information used for indicating a plurality of time domain resources and information used for indicating one or more RVs; the network device determines time domain resources and RVs of one or more transmission occasions for transmitting PUSCH or PDSCH based on the indication information and the time domain resource allocation table.

In the prior art, the table entry in the time domain resource allocation table is only used to determine the time domain resource of the transmission opportunity, and is not used to determine the RV used by the transmission opportunity, and the RV corresponding to each transmission opportunity needs to be additionally indicated by DCI. In the method provided by the second aspect, the entry in the time domain resource allocation table may include information for indicating an RV, and in this case, the network device does not need to indicate the RV corresponding to the transmission opportunity through the DCI, so that the signaling overhead of the DCI may be reduced.

In one possible implementation, the method further includes: and the network equipment sends configuration information to the terminal, wherein the configuration information is used for configuring the time domain resource allocation table. The possible implementation mode enables the base station to flexibly configure the time domain resource allocation table for the terminal, thereby adapting to different requirements and improving the transmission efficiency.

In a possible implementation manner, the at least one entry in the time domain resource allocation table further includes a plurality of first offset values, and the plurality of first offset values are used to determine a time slot in which the time domain resource of the plurality of transmission occasions is located. In type1 uplink unlicensed transmission, the value of timeDomainOffset is sent through RRC signaling so that the terminal determines a time slot in which a time domain resource is located. To facilitate repeated transmission of data, information indicating a plurality of time domain resources may be included in one entry in the time domain resource allocation table. In this case, the terminal needs to determine the time slots where multiple time domain resources are located. At this time, the network device needs to send a plurality of values of timeDomainOffset through RRC signaling, so that the terminal determines the time slot in which the plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it needs to know the corresponding relationship between the values of the plurality of timeDomainOffset and the plurality of time domain resources, and therefore, the implementation process is complicated. According to the method, the time slots of the time domain resources of multiple transmission occasions are determined by configuring the first deviation values in the table entries in the time domain resource allocation table, so that the terminal can rapidly determine the time slots of the time domain resources, and the implementation complexity of the terminal is reduced.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value, and the method further includes: the network equipment sends a PDCCH to the terminal, the PDCCH carries DCI used for scheduling the PUSCH, the DCI carries the indication information, and the index of a time slot in which the DCI is positioned is n; correspondingly, the network device determines time domain resources of one or more transmission occasions for transmitting the PUSCH based on the indication information and the time domain resource allocation table, including: and the network equipment determines the time slot of the time domain resource of the kth transmission opportunity in the one or more transmission opportunities according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information and a second offset value contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value, and the method further includes: the network equipment sends a PDCCH to the terminal, the PDCCH carries DCI used for scheduling the PDSCH, the DCI carries the indication information, and the index of a time slot in which the DCI is located is n; correspondingly, the network device determines time domain resources of one or more transmission occasions for transmitting the PDSCH based on the indication information and the time domain resource allocation table, including: the network device determines a time slot in which a time domain resource of a kth transmission opportunity in the one or more transmission opportunities is located according to a subcarrier interval of the PDSCH, a subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource included in a table entry indicated by the indication information, and a second offset value included in a table entry indicated by the indication information, where k is an integer greater than 0.

In one possible implementation, the kth of the one or more transmission occasionsThe index of the time slot in which the time domain resource of each transmission opportunity is:

wherein u is_PDSCHParameter, u, characterizing the subcarrier spacing of the PDSCH_PDCCHIn order to characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the indication information, and C2 is a second offset value contained in the entry indicated by the indication information.

In one possible implementation, the method further includes: the network equipment sends configuration information of uplink authorization-free transmission of type1 to the terminal, wherein the configuration information comprises the configuration information of the indication information and a third offset value; and determining a time slot in which a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information, wherein k is an integer greater than 0. In type1 uplink unlicensed transmission, the value of timeDomainOffset is sent through RRC signaling so that the terminal determines a time slot in which a time domain resource is located. To facilitate repeated transmission of data, information indicating a plurality of time domain resources may be included in one entry in the time domain resource allocation table. In this case, the terminal needs to determine the time slots where multiple time domain resources are located. At this time, the network device needs to send a plurality of values of timeDomainOffset through RRC signaling, so that the terminal determines the time slot in which the plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it needs to know the corresponding relationship between the values of the plurality of timeDomainOffset and the plurality of time domain resources, and therefore, the implementation process is complicated. According to the method, the time slots of the time domain resources of multiple transmission occasions are determined by configuring the first deviation values in the table entries in the time domain resource allocation table, so that the terminal can rapidly determine the time slots of the time domain resources, and the implementation complexity of the terminal is reduced.

In a third aspect, a method for determining transmission resources is provided, including: the terminal receives indication information from a network device, where the indication information is used to indicate one entry in a time domain resource allocation table, where at least one entry in the time domain resource allocation table includes information used to indicate multiple time domain resources and multiple first offset values, and the multiple first offset values are used to determine a time slot in which a time domain resource of the multiple transmission occasions is located; and the terminal determines the time domain resources of one or more transmission occasions for transmitting the PUSCH or the PDSCH according to the indication information and the time domain resource allocation table.

In type1 uplink unlicensed transmission, the value of timeDomainOffset is sent through RRC signaling so that the terminal determines the timeslot where a time domain resource is located. To facilitate repeated transmission of data, information indicating a plurality of time domain resources may be included in one entry in the time domain resource allocation table. In this case, the terminal needs to determine the time slots where multiple time domain resources are located. At this time, the network device needs to send a plurality of values of timeDomainOffset through RRC signaling, so that the terminal determines the time slot in which the plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it needs to know the corresponding relationship between the values of the plurality of timeDomainOffset and the plurality of time domain resources, and therefore, the implementation process is complicated. In the method provided in the third aspect, multiple first offset values are configured in the table entry in the time domain resource allocation table to determine the time slots in which the time domain resources of multiple transmission opportunities are located, so that the terminal can quickly determine the time slots in which the multiple time domain resources are located, and the implementation complexity of the terminal is reduced.

In one possible implementation, the method further includes: the terminal receives configuration information from the network device, wherein the configuration information is used for configuring the time domain resource allocation table.

In one possible implementation, the one or more transmissionsThe index of the slot in which the time domain resource of the kth transmission opportunity is located is:

wherein u is_PUSCHParameter, u, characterizing the subcarrier spacing of the PUSCH_PDCCHIn order to characterize the parameter of the sub-carrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the indication letter, and C2 is a second offset value contained in the entry indicated by the indication information.

In one possible implementation, the method further includes: the terminal receives configuration information of uplink authorization-exempt transmission of type1 from the network equipment, wherein the configuration information comprises the configuration information of the indication information and a third offset value; and determining a time slot in which a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

In a fourth aspect, a method for determining transmission resources is provided, including: the network equipment sends indication information to a terminal, wherein the indication information is used for indicating one table entry in a time domain resource allocation table, at least one table entry in the time domain resource allocation table comprises information used for indicating a plurality of time domain resources and a plurality of first offset values, and the plurality of first offset values are used for determining time slots of the time domain resources of the plurality of transmission opportunities; the network device determines time domain resources for one or more transmission occasions for transmitting PUSCH or PDSCH based on the indication information and the time domain resource allocation table.

In type1 uplink unlicensed transmission, the value of timeDomainOffset is sent through RRC signaling so that the terminal determines a time slot in which a time domain resource is located. To facilitate repeated transmission of data, information indicating a plurality of time domain resources may be included in one entry in the time domain resource allocation table. In this case, the terminal needs to determine the time slots where multiple time domain resources are located. At this time, the network device needs to send a plurality of values of timeDomainOffset through RRC signaling, so that the terminal determines the time slot in which the plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it needs to know the corresponding relationship between the values of the plurality of timeDomainOffset and the plurality of time domain resources, and therefore, the implementation process is complicated. In the method provided in the fourth aspect, the multiple first offset values are configured in the table entry in the time domain resource allocation table to determine the time slots in which the time domain resources of multiple transmission opportunities are located, so that the terminal can quickly determine the time slots in which the multiple time domain resources are located, and the implementation complexity of the terminal is reduced.

In one possible implementation, the method further includes: and the network equipment sends configuration information to the terminal, wherein the configuration information is used for configuring the time domain resource allocation table.

In a fifth aspect, an apparatus for determining transmission resources is provided, including: a communication unit and a processing unit; the communication unit is configured to receive indication information from a network device, where the indication information is used to indicate one entry in a time domain resource allocation table, and at least one entry in the time domain resource allocation table includes information indicating multiple time domain resources and information indicating one or more RVs; and the processing unit is configured to determine, according to the indication information and the time domain resource allocation table, time domain resources and RVs of one or more transmission occasions for transmitting the PUSCH or the PDSCH.

In a possible implementation manner, the communication unit is further configured to receive configuration information from the network device, where the configuration information is used to configure the time domain resource allocation table.

In a possible implementation manner, the at least one entry in the time domain resource allocation table further includes a plurality of first offset values, and the plurality of first offset values are used to determine a time slot in which the time domain resource of the plurality of transmission occasions is located.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value; the communication unit is further configured to receive a PDCCH from the network device, where the PDCCH carries DCI for scheduling the PUSCH, the DCI carries the indication information, and an index of a time slot in which the DCI is located is n; the processing unit is specifically configured to: and determining a time slot in which a time domain resource of a kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in an entry indicated by the indication information and a second offset value contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value; the communication unit is further configured to receive a PDCCH from the network device, where the PDCCH carries DCI for scheduling the PDSCH, the DCI carries the indication information, and an index of a time slot in which the DCI is located is n; the processing unit is specifically configured to: determining a time slot in which a time domain resource of a kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PDSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

wherein u is_PDSCHSubcarrier spacing to characterize the PDSCHParameter of (a), u_PDCCHIn order to characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the indication information, and C2 is a second offset value contained in the entry indicated by the indication information.

In a possible implementation manner, the communication unit is further configured to receive, from the network device, configuration information of uplink grant-free transmission of type1, where the configuration information includes configuration information of the indication information and a third offset value; and determining a time slot in which a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

In a possible implementation manner, at least one first time domain resource in the plurality of time domain resources corresponds to an RV with an index of 0, where the first time domain resource includes a time domain resource with a maximum number of symbols in the plurality of time domain resources.

In a possible implementation manner, values of the RV index corresponding to each of the at least one first time domain resource are cycled according to an arrangement of RV indexes in an RV sequence {0,2,3,1} or {0,3,0,3 }.

In a sixth aspect, an apparatus for determining transmission resources is provided, including: a communication unit and a processing unit; the communication unit is configured to send indication information to a terminal, where the indication information is used to indicate one entry in a time domain resource allocation table, and at least one entry in the time domain resource allocation table includes information used to indicate multiple time domain resources and information used to indicate one or more RVs; the processing unit is configured to determine, based on the indication information and the time domain resource allocation table, a time domain resource and an RV of one or more transmission occasions for transmitting a PUSCH or a PDSCH.

In a possible implementation manner, the communication unit is further configured to send configuration information to the terminal, where the configuration information is used to configure the time domain resource allocation table.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value; the communication unit is further configured to send a PDCCH to the terminal, where the PDCCH carries DCI for scheduling the PUSCH, the DCI carries the indication information, and an index of a time slot in which the DCI is located is n; the processing unit is specifically configured to: and determining a time slot in which a time domain resource of a kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in an entry indicated by the indication information and a second offset value contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

In a possible implementation manner, each entry in the time domain resource allocation table further includes a second offset value; the communication unit is further configured to send a PDCCH to the terminal, where the PDCCH carries DCI for scheduling the PDSCH, the DCI carries the indication information, and an index of a time slot in which the DCI is located is n; the processing unit is specifically configured to: determining a time slot in which a time domain resource of a kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PDSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

In a possible implementation manner, the communication unit is further configured to send configuration information of uplink grant-free transmission of type1 to the terminal, where the configuration information includes the configuration information of the indication information and a third offset value; and determining a time slot in which a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

In a seventh aspect, an apparatus for determining transmission resources is provided, where the apparatus has the function of implementing any one of the methods provided in the third aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions. For example, the apparatus may comprise a communication unit for performing the actions of the processing in the third aspect (e.g. actions other than transmitting and/or receiving) and a processing unit for performing the actions of the transmitting and/or receiving in the third aspect. Optionally, the actions performed by the communication unit are performed under the control of the processing unit. Optionally, the communication unit includes a sending unit and a receiving unit, in this case, the sending unit is configured to perform the sending action in the third aspect, and the receiving unit is configured to perform the receiving action in the third aspect. The device may be in the form of a chip product.

In an eighth aspect, an apparatus for determining transmission resources is provided, and the apparatus has the function of implementing any one of the methods provided in the fourth aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more units corresponding to the above functions. For example, the apparatus may include a communication unit to perform the acts of processing in the fourth aspect (e.g., acts other than transmitting and/or receiving) and a processing unit to perform the acts of transmitting and/or receiving in the fourth aspect. Optionally, the actions performed by the communication unit are performed under the control of the processing unit. Optionally, the communication unit includes a sending unit and a receiving unit, in this case, the sending unit is configured to perform the sending action in the fourth aspect, and the receiving unit is configured to perform the receiving action in the fourth aspect. The device may be in the form of a chip product.

In a ninth aspect, an apparatus for determining transmission resources is provided, including: a processor. The processor is connected with the memory, and the memory is used for storing computer-executable instructions, and the processor executes the computer-executable instructions stored in the memory, thereby implementing any one of the methods provided by the first, second, third or fourth aspects. The memory and the processor may be integrated together or may be separate devices. If the latter is the case, the memory may be located within the apparatus for determining transmission resources or may be located outside the apparatus for determining transmission resources.

In one possible implementation, the processor includes logic circuitry and further includes at least one of an input interface and an output interface. Wherein the output interface is used for executing the sent action in the corresponding method, and the input interface is used for executing the received action in the corresponding method.

In a possible implementation, the means for determining transmission resources further comprises a communication interface and a communication bus, the processor, the memory and the communication interface being connected by the communication bus. The communication interface is used for executing the actions of transceiving in the corresponding method. The communication interface may also be referred to as a transceiver. Optionally, the communication interface comprises at least one of a transmitter and a receiver, in which case the transmitter is configured to perform the act of transmitting in the respective method and the receiver is configured to perform the act of receiving in the respective method.

In one possible implementation, the means for determining the transmission resources are present in the production form of a chip.

In a tenth aspect, there is provided a communication system comprising: the apparatus for determining transmission resources provided in the fifth aspect and the apparatus for determining transmission resources provided in the sixth aspect; alternatively, the apparatus for determining transmission resources provided in the seventh aspect and the apparatus for determining transmission resources provided in the eighth aspect.

In an eleventh aspect, there is provided a computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform any one of the methods provided in the first, second, third or fourth aspects.

In a twelfth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any one of the methods provided in the first, second, third or fourth aspects.

For technical effects brought by any implementation manner of the fifth aspect to the twelfth aspect, reference may be made to technical effects brought by corresponding implementation manners of the first aspect to the fourth aspect, and details are not described here.

It should be noted that, all possible implementation manners of any one of the above aspects may be combined without departing from the scope of the claims.

Drawings

Fig. 1 is a schematic diagram illustrating a network architecture according to an embodiment of the present application;

fig. 2 and fig. 3 are schematic diagrams of time domain resources occupied by data according to an embodiment of the present application, respectively;

fig. 4 is a flowchart of a method for determining transmission resources according to an embodiment of the present application;

fig. 5 and fig. 6 are schematic diagrams of time domain resources occupied by multiple data according to an embodiment of the present application, respectively;

fig. 7 is a flowchart of a method for determining transmission resources according to an embodiment of the present application;

fig. 8 is a schematic diagram illustrating a communication device according to an embodiment of the present disclosure;

fig. 9 and fig. 10 are respectively a schematic hardware structure diagram of a communication apparatus according to an embodiment of the present application;

fig. 11 is a schematic hardware structure diagram of a terminal according to an embodiment of the present disclosure;

fig. 12 is a schematic hardware structure diagram of a network device according to an embodiment of the present application.

Detailed Description

In the description of this application, "/" means "or" unless otherwise stated, for example, A/B may mean A or B. "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. Further, "at least one" means one or more, "a plurality" means two or more. The terms "first", "second", and the like do not necessarily limit the number and execution order, and the terms "first", "second", and the like do not necessarily limit the difference.

It is noted that, in the present application, words such as "exemplary" or "for example" are used to mean exemplary, illustrative, or descriptive. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The technical scheme provided by the embodiment of the application can be applied to various communication systems. For example, a Long Term Evolution (LTE) communication system, a New Radio (NR) communication system using a 5G communication technology, a future evolution system or a multiple communication convergence system, and so on.

The technical scheme provided by the embodiment of the application can be applied to various communication scenes. For example, the scenarios include machine to machine (M2M), macro and micro communication, enhanced mobile broadband (eMBB), ultra-reliable and ultra-low latency communication (URLLC), massive internet of things communication (mtc), internet of things (IoT), and industrial internet of things (IIoT).

Fig. 1 is a schematic diagram of a communication system to which the technical solution provided by the present application is applied. The communication system may comprise at least one network device (only 1 shown in fig. 1) and at least one terminal (6 shown in fig. 1, respectively terminal 1 to terminal 6). One or more of terminals 1-6 may communicate with a network device to transmit one or more of data (uplink data and/or downlink data) and signaling. In addition, the terminals 4 to 6 may also form another communication system to which the technical solution provided by the present application is applied, in which case, the sending entity and the receiving entity are both terminals. For example, the terminals 4 to 6 may constitute a car networking system, and the terminal 4 may transmit data or signaling to the terminal 5, and the terminal 5 receives the data or signaling transmitted by the terminal 4.

For convenience of description, the following description is given by taking an example that the technical solution provided by the embodiment of the present application is applied between a network device and a terminal. It can be understood that, when the technical solution provided in the embodiment of the present application is applied between two terminals (denoted as terminal a and terminal B), the network device in each embodiment is replaced by terminal a, and the terminal is replaced by terminal B.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation on the technical solution provided in the embodiment of the present application. As can be known to those skilled in the art, with the evolution of network architecture and the emergence of new service scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

A network device is an entity on the network side for transmitting signals, or receiving signals, or both. The network device may be a device deployed in a Radio Access Network (RAN) to provide a wireless communication function for a terminal, for example, a base station. The network device may be a macro base station, a micro base station (also referred to as a small station), a relay station, an Access Point (AP), or the like in various forms, and may also include a control node in various forms, such as a network controller. The control node may be connected to a plurality of base stations, and configure resources for a plurality of terminals under the coverage of the plurality of base stations. In systems using different radio access technologies, the names of devices that function as base stations may differ. For example, a global system for mobile communication (GSM) or Code Division Multiple Access (CDMA) network may be referred to as a Base Transceiver Station (BTS), a Wideband Code Division Multiple Access (WCDMA) network may be referred to as a base station (NodeB), an LTE system may be referred to as an evolved base station (eNB or eNodeB), and a 5G or NR communication system may be referred to as a next generation base station (NodeB), and the present application does not limit specific names of the base stations. The network device may also be a wireless controller in a Cloud Radio Access Network (CRAN) scene, a network device in a Public Land Mobile Network (PLMN) for future evolution, a transmission and reception node (TRP for short), and the like.

A terminal is an entity on the user side for receiving signals, or transmitting signals, or both. The terminal is used to provide one or more of voice services and data connectivity services to the user. A terminal may also be referred to as a User Equipment (UE), a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal may be a Mobile Station (MS), a subscriber unit (subscriber unit), an unmanned aerial vehicle (drone), an IoT device, a Station (ST) in a Wireless Local Area Network (WLAN), a cellular phone (cellular phone), a smart phone (smart phone), a cordless phone, a wireless data card, a tablet computer, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a laptop computer (laptop computer), a Machine Type Communication (MTC) terminal, a handheld device having a wireless communication function, a computing device, or other processing device connected to a wireless modem, a vehicle-mounted device, and a wearable smart device (also called a wearable smart device). The terminal may also be a terminal in a next generation communication system, e.g. a terminal in a 5G communication system or a terminal in a PLMN for future evolution, a terminal in an NR communication system, etc.

In order to facilitate understanding of the present application, a brief description of some concepts related to the embodiments of the present application will be provided herein.

1. Time slot

In NR, 1 slot contains 14 Orthogonal Frequency Division Multiplexing (OFDM) symbols (hereinafter, referred to as symbols) for a normal (normal) Cyclic Prefix (CP). For extended CP, 1 slot contains 12 symbols.

For convenience of description, in the embodiment of the present application, if not specifically stated, 1 slot includes 14 symbols. In the slot, 14 symbols are numbered in order from small to large, the smallest number is 0, and the largest number is 13. In the embodiment of the present application, the symbol with index (i.e., number) i is denoted as symbol # i, and one slot includes symbols #0 to # 13. In the present application, a time slot with an index (i.e., number) j will be referred to as a time slot # j hereinafter. j is an integer of 0 or more, and i is an integer of 0 or more and 13 or less.

2. Transmission scenario applicable to the application

The transmission scenario applicable to the present application includes: uplink transmission based on dynamic Scheduling, downlink transmission based on Semi-Persistent Scheduling (SPS for short), and uplink grant-free transmission.

The uplink grant-free transmission refers to: the uplink transmission of the terminal does not need to be completed by dynamic scheduling of the network equipment. Specifically, when uplink data arrives (in the embodiment of the present application, data arrival means that data is processed and can be sent), the terminal does not need to send a Scheduling Request (SR) to the network device and wait for a dynamic grant (dynamic grant) of the network device, but may directly send the uplink data to the network device by using a transmission resource pre-allocated by the network device and a specified transmission parameter.

The uplink grant-free transmission may also be referred to as: uplink non-scheduling transmission, uplink non-dynamic grant transmission (UL data transmission with dynamic grant), uplink non-dynamic scheduling transmission, Configured Grant (CG) transmission, transmission of higher layer configuration, and the like.

Uplink grant-free transmission is classified into two types: a Physical Uplink Shared Channel (PUSCH) transmission (type 1PUSCH transmission with an access configured grant, or PUSCH transmission with a type 1configured grant, or type 1configured grant PUSCH transmission) based on the first type of configuration grant and a PUSCH transmission (type 2PUSCH transmission with a configured grant, or PUSCH transmission with a type 2configured grant, or type 2configured grant).

The existing configuration mode of PUSCH transmission based on the first type of configuration authorization is as follows: the network device configures all transmission resources and transmission parameters for the terminal through higher layer parameters (e.g., ConfiguredGrantConfig). For example: a period of a time domain resource, an open loop power control related parameter, a waveform, a Redundancy Version (RV) sequence, a repetition number, a frequency hopping pattern, a resource allocation type, a number of hybrid automatic repeat request (HARQ) processes, a demodulation reference signal (DMRS) related parameter, a Modulation and Coding Scheme (MCS) table, a Resource Block Group (RBG) size, and all transmission resources and transmission parameters including a time domain resource, a frequency domain resource, and an MCS. After receiving the high-level parameters, the terminal can immediately use the configured transmission parameters to carry out PUSCH transmission on the configured time-frequency resources.

The existing configuration mode of PUSCH transmission based on the second type of configuration grant is divided into the following two steps: first, the network device configures part of the transmission resources and transmission parameters to the terminal through higher layer parameters (e.g., ConfiguredGrantConfig). For example: the method comprises the steps of time domain resource period, open loop power control related parameters, waveform, RV sequence, repetition times, frequency hopping mode, resource allocation type, HARQ process number, DMRS related parameters, MCS table and RBG size. Then, the network device sends Downlink Control Information (DCI) to the terminal, so that the terminal activates PUSCH transmission authorized based on the second type of configuration and simultaneously configures transmission resources and transmission parameters including time domain resources, frequency domain resources, DMRS related parameters, MCS, and the like. It should be noted that the PUSCH transmission of the second type configuration grant can be used after being activated.

Hereinafter, the PUSCH transmission based on the first type of configuration grant is referred to as type1 uplink unlicensed transmission, and the PUSCH transmission based on the second type of configuration grant is referred to as type2 uplink unlicensed transmission.

3. Transmission opportunity (TO for short)

The transmission opportunity includes time domain resources for transmitting data once. One transmission opportunity includes one or more symbols. When there are multiple transmission occasions for repeated transmission, multiple identical data are repeatedly transmitted on multiple transmission occasions. At this time, one data transmission on one transmission opportunity may be referred to as one repetition transmission. The multiple identical data refers to multiple identical or different RVs obtained after the same information bit is subjected to channel coding.

4. Repeat transmission (Repetition) and Slot aggregation (Slot aggregation) transmission

In order to improve the transmission reliability of data, the NR communication system supports time slot aggregation transmission and repeat transmission of data, where the time slot aggregation transmission and the repeat transmission both refer to transmission of multiple copies of the same data, and are defined by different names only because of different application transmission scenarios. Among them, a transmission scheme for transmitting a plurality of identical data based on dynamic scheduling is called slot aggregation transmission. The transmission of multiple copies of the same data based on SPS or uplink grant-free is referred to as repeat transmission. The SPS-based repeated transmission may also be referred to as a bundling (bundling) transmission.

Because a transmission timing for transmitting a PUSCH or a Physical Downlink Shared Channel (PDSCH) for one time cannot include a slot boundary (slot boundary) and a DL/UL switching point (DL/UL switching point). Therefore, when time slot aggregation transmission or repeated transmission is carried out, the transmission opportunity containing different symbol numbers is used by supporting the repeated transmission of different times, so that the available symbols in the time slot are fully utilized, and the purposes of reducing the transmission delay of data and improving the transmission reliability are achieved. Here, the slot boundary refers to a boundary between two slots. The uplink/downlink symbol switching point is a boundary between an uplink symbol and a downlink symbol. The available symbol refers to a symbol that can be used for PUSCH or PDSCH transmission, and whether one symbol is available or not, depending on the context of the application. For example, for downlink data transmission, the uplink symbols are unavailable symbols. For uplink data transmission, the downlink symbols are unavailable symbols.

For example, in a time-division multiplexing (TDD) system, referring to fig. 2, it is assumed that a network device configures, through DCI, the 1 st symbol (i.e., symbol #0) and the 8 th symbol (i.e., symbol #7) in a slot as downlink symbols (denoted by D), configures the 2 nd symbol (i.e., symbol #1) and the 9 th symbol (i.e., symbol #8) as flexible symbols (denoted by F), and configures other symbols as uplink symbols (denoted by U). When the uplink data is ready at the 12 th symbol (i.e., symbol #11) of slot #1, to reduce latency, it should be allowed to transmit from the 13 th symbol (i.e., symbol #12) of slot # 1. Otherwise, the transmission of the uplink data needs to wait until the 3 rd symbol (i.e. symbol #2) of the slot #2 can start, and a delay of 4 symbols is introduced, which is not acceptable for the URLLC service with extremely sensitive delay. To ensure the reliability of data transmission simultaneously, assuming that 10 symbols are required for multiple repeated transmission of the uplink data, the uplink data may be repeated 3 times starting from the 13 th symbol (i.e., symbol #12) of slot #1 and ending at the 12 th symbol (i.e., symbol #11) of slot #2, as shown in fig. 2. Wherein, the 1 st repetition is located on the 13 th symbol (i.e., symbol #12) and the 14 th symbol (i.e., symbol #13) of the slot #1, the 2 nd repetition is located on the 3 rd symbol (i.e., symbol #2) to the 7 th symbol (i.e., symbol #6) of the slot #2, and the 3 rd repetition is located on the 10 th symbol (i.e., symbol #9) to the 12 th symbol (i.e., symbol #11) of the slot # 2.

5. Existing time domain resource allocation tables

The time domain resource allocation table is used for allocating time domain resources.

In NR, the network device configures a time domain resource allocation table for the terminal through high layer signaling, where the table includes at most 16 rows (entries) (i.e., 16 entries). After configuring the Time domain resource allocation table, referring to table 1, for uplink transmission based on dynamic scheduling, downlink transmission based on SPS, and type2 uplink unlicensed transmission, the network device may use DCI (e.g., Time domain resource assignment field in DCI) to indicate which row of resources in the Time domain resource allocation table is allocated to the terminal. For type1 uplink unlicensed transmission, the network device may use Radio Resource Control (RRC) signaling (e.g., a time domain allocation IE parameter in the RRC signaling) to indicate which row of resources in the time domain resource allocation table is allocated to the terminal.

TABLE 1

Each row in the time domain resource allocation table for uplink transmission contains 3 parameters: k₂Mapping type (mappingType), starting symbol and length (startSymbolAndLength). Wherein, K₂Time domain offset for PUSCH transmission. The time slot of the PUSCH transmission may be slot # (n1+ K)₂) Where n1 is the slot where the DCI scheduling PUSCH is located. The mapping type is used to indicate the mapping type of the PUSCH transmission, and the mapping type may be mapping type a or mapping type B. The Start symbol and Length are also called Start and Length Indicator Value (SLIV) and are used to determine a Start symbol S (i.e. a first symbol in the time domain resource) and a Length L (i.e. the time domain resource includes the first symbol) of the allocated time domain resource in a slot (i.e. the time domain resource includes the first symbol in the time domain resource)The number of symbols) of (a).

Each row in the time domain resource allocation table for downlink transmission contains 3 parameters: k₀Mapping type, starting symbol and length. Wherein, K₀Time domain offset for PDSCH transmission. The time slot for PDSCH transmission may be time slot # (n2+ K)₀) Where n2 is a time slot where DCI scheduling PDSCH is located. The mapping type is used to indicate a mapping type of PDSCH transmission, and the mapping type may be mapping type a or mapping type B. The starting symbol and length are also referred to as SLIV, and are used to determine a starting symbol S (i.e., the first symbol in the time domain resource) and a length L (i.e., the number of symbols included in the time domain resource) of the allocated time domain resource in a slot.

If the network device does not configure the time domain resource allocation table for the terminal through the high layer signaling, the terminal uses a default table. For example, the default uplink time domain resource allocation table may be tables 6.1.2.1.1-2, 6.1.2.1.1-3, 6.1.2.1.1-4 in 3GPP TS 38.214. The default downlink time domain resource allocation table may be tables 5.1.2.1.1-2, 5.1.2.1.1-3, 5.1.2.1.1-4, 5.1.2.1.1-5 in 3gpp ts 38.214.

For example, the table 6.1.2.1.1-2 in the default uplink time domain resource allocation table contains details as shown in table 2. The value of j in table 2 is related to the uplink subcarrier spacing, and specifically, see table 3.

TABLE 2

TABLE 3

u_PUSCH	j
		0	1
1	1
		2	2

Note: u. of_PUSCHIs a parameter used to characterize the uplink subcarrier spacing. 0, 1, and 2 in the left column of table 3 each represent an uplink subcarrier spacing.

On the basis that the terminal knows 16 combinations configured or default through RRC signaling, for type1 uplink unlicensed transmission, the network device indicates one of the 16 combinations to the terminal through RRC signaling (e.g., a timedomainalllocation parameter in RRC signaling), since the type1 uplink unlicensed transmission has a special RRC parameter (e.g., timeDomainOffset) indicating slot offset, in which case the terminal determines the starting slot of the unlicensed transmission resource according to the timeDomainOffset, for example, when the value indicated by the timeDomainOffset is 100, the terminal determines that the unlicensed transmission resource starts from slot # 100. Therefore, for type1 uplink unlicensed transmission, the terminal does not use K in the combination₂。

6. Existing method for determining RV adopted by repeatedly transmitted data

In order to enable a receiving end to improve decoding capability by using a combined receiving method of Incremental Redundancy (IR), a network device may configure different times of repeated transmissions to use different RVs. In the prior art, the RV used for the repeated transmission of different times is determined using the following method:

for time slot aggregation transmission based on dynamic scheduling, the RV adopted by each PDSCH transmission or PUSCH transmission passes through the index p (0 ≦ p) of the transmission opportunity corresponding to the transmission<K, K is a slot aggregation factor, i.e., the number of slots for repeated transmission) and RV indicated by the RV indication field in DCI for scheduling PDSCH or PUSCH_idCommon determination, rv_idRefers to the index of the RV. For example, as in 3GPP TS38.214In the above, the RV corresponding to the transmission timing with index p for transmitting PDSCH is identified in table 4, and the RV corresponding to the transmission timing with index p for transmitting PUSCH is identified in table 5. "mod" in tables 4 and 5 means "remainder". The transmission opportunity with index p may also be referred to as the p-th transmission opportunity.

TABLE 4

TABLE 5

For SPS or uplink unlicensed retransmission, the RV used for retransmission of a PUSCH is determined by an index p of a transmission opportunity corresponding to the transmission (0< p ≦ K, where K is the number of times of retransmission) and an RV sequence configured by a parameter repK-RV (for example, may be {0,0, 0} or {0,3,0,3} or {0,2,3,1}) by a higher layer. For example, the RV employed for PUSCH transmission on a transmission occasion with index p is the (mod (p-1,4) +1) th value in the configured RV sequence. For example, if the RV sequence configured by the parameter repK-RV at the higher layer of the network device is {0,2,3,1}, based on the example shown in fig. 2, according to the RV determination method adopted in the prior art for repeated transmission, see fig. 3, RV0, RV2, and RV3 are respectively adopted for 3 times of repeated transmission in fig. 3. In the embodiment of the present application, RV0 refers to RV with index 0, RV2 refers to RV with index 2, RV3 refers to RV with index 3, and RV1 refers to RV with index 1.

For convenience of description, timeslot aggregation transmission and repeat transmission are collectively referred to as repeat transmission in this embodiment. As shown in fig. 4, a method for determining transmission resources provided in an embodiment of the present application includes:

400. the terminal determines a time domain resource allocation table to use.

A plurality of time domain resource allocation tables may exist in the terminal, and the plurality of time domain resource allocation tables may include: a default time domain resource allocation table, and/or a time domain resource allocation table configured by the network device. At least one of the plurality of time domain resource allocation tables satisfies the following condition: at least one entry in the time domain resource allocation table includes information indicating a plurality of time domain resources and information indicating one or more RVs. The time domain resource allocation table referred to in the following of the embodiments of the present application is a time domain resource allocation table satisfying this condition. In a case that the plurality of time domain resource allocation tables include a time domain resource allocation table configured by the network device, optionally, the method further includes: the network device sends the configuration information to the terminal. Accordingly, the terminal receives configuration information from the network device. The configuration information is used to configure a time domain resource allocation table. Wherein at least one entry in the time domain resource allocation table comprises information indicating a plurality of time domain resources and information indicating one or more RVs.

The configuration information may be carried in RRC signaling or Media Access Control (MAC) control element (MAC CE) signaling or DCI.

In step 400, the time domain resource allocation table determined by the terminal to use may be default or configured for the terminal by the network device.

Step 400 may be implemented in one or more of the following ways one to four when embodied.

The first mode is that the terminal determines according to the indication information (marked as first indication information) issued by the network device through RRC signaling or MAC CE signaling or DCI.

Wherein, the first indication information may directly indicate a time domain resource allocation table used by the terminal. For example, the network device may carry the first indication information through a Time domain resource allocation parameter (e.g., a Time domain resource allocation field in DCI or a Time domain allocation IE parameter in RRC), specifically, one bit (bit) may be added to indicate a Time domain resource allocation table used by the terminal, or a specific Time domain resource allocation table may be used when the Time domain resource allocation parameter takes a specific value or values.

And secondly, the terminal determines a used time domain resource allocation table according to the type of a Radio Network Temporary Identifier (RNTI), wherein the RNTI is used for scrambling a Cyclic Redundancy Check (CRC) of a Physical Downlink Control Channel (PDCCH).

In the second mode, different RNTIs may correspond to different time domain resource allocation tables. In this case, the terminal may determine the type of RNTI of the CRC of the scrambled PDCCH through blind detection, and then determine the time domain resource allocation table corresponding to the RNTI of the CRC of the scrambled PDCCH as the used time domain resource allocation table.

And thirdly, the terminal determines a used time domain resource allocation table according to a DCI format (format), wherein the DCI is used for scheduling PUSCH or PDSCH transmission.

Wherein, the DCI format comprises: DCI format 0-0, DCI format 0-1, DCI format 1-1, etc.

In the third embodiment, different DCI formats may correspond to different time domain resource allocation tables. In this case, the terminal may determine the DCI format through blind detection, and then determine the time domain resource allocation table corresponding to the determined DCI format as the used time domain resource allocation table.

And fourthly, determining a used time domain resource allocation table according to the search space type of the PDCCH, wherein the PDCCH schedules PUSCH or PDSCH transmission.

Wherein the search space type of the PDCCH includes: a common search space, a terminal-specific search space, etc.

In the fourth mode, different PDCCH search spaces may correspond to different time domain resource allocation tables. In this case, the terminal may determine the search space type of the PDCCH in different search spaces through blind detection, and then determine the time domain resource allocation table corresponding to the determined search space type of the PDCCH as the used time domain resource allocation table.

Step 400 is an optional step.

401. The network device sends the indication information (marked as second indication information) to the terminal, and correspondingly, the terminal receives the second indication information from the network device.

Wherein the second indication information is used for indicating an entry in the time domain resource allocation table. The second indication information may also be referred to as time domain resource allocation information.

Wherein, the second indication information may be carried in RRC signaling or MAC CE signaling or DCI.

402. The network device determines time domain resources and RVs for one or more transmission occasions for transmitting the PUSCH or PDSCH based on the second indication information and the time domain resource allocation table.

In a specific implementation of step 402, the network device may determine the time domain resource and the RV of one or more transmission occasions according to the information for indicating the time domain resource and the information for indicating the RV in the time domain resource allocation table and the entry indicated by the second indication information.

Illustratively, taking type2 unlicensed transmission as an example, the time domain resources determined using the time domain resource allocation table shown in table 6 below and the corresponding RVs thereof are described.

If the slot in which the DCI for scheduling the PUSCH is located is slot #1, and the row index of the table entry indicated by the second indication information carried in the DCI is 2, the terminal device may determine three time domain resources according to the second indication information and table 6, where the three time domain resources are: symbols #2 to #11 in slot # (j +1), symbols #0 to #13 in slot # ((j +2) +1), and symbols #0 to #13 in slot # ((j +3) + 1). The RVs associated (or corresponding) to the three time domain resources (3 transmission occasions) are respectively: RV1, RV0 and RV 2.

TABLE 6

403. And the terminal determines the time domain resources and RVs of one or more transmission occasions for transmitting the PUSCH or the PDSCH according to the second indication information and the time domain resource allocation table.

The method for the terminal to determine the time domain resources and the RV of one or more transmission occasions is similar to that of the network device and is not described again.

The execution sequence of step 402 and step 403 is not sequential.

Optionally, after step 402, the method further includes: the network equipment adopts the corresponding RV to send downlink data on one or more transmission occasions, and the terminal adopts the corresponding RV to receive the downlink data on one or more transmission occasions; or, the terminal transmits the uplink data by using the corresponding RV at one or more transmission occasions, and the network device receives the uplink data by using the corresponding RV at one or more transmission occasions.

In the prior art, the table entry in the time domain resource allocation table is only used to determine the time domain resource of the transmission opportunity, and is not used to determine the RV used by the transmission opportunity, and the RV corresponding to each transmission opportunity needs to be additionally indicated by DCI. In the method provided by the embodiment of the present application, the entry in the time domain resource allocation table may include information for indicating the RV, and in this case, the network device does not need to indicate the RV corresponding to the transmission opportunity through the DCI any more, and the RV indication field originally existing in the DCI may be used for other indication functions, so that the signaling overhead of the DCI may be reduced.

In the above embodiment, a plurality of time domain resources indicated by one entry in the time domain resource allocation table may be used for repeated transmission of data.

The existing method for determining the RV corresponding to the time domain resource cannot ensure reliable transmission of the data packet. For example, referring to fig. 3, when the RV sequence configured by the network device is {0,2,3,1}, in 3 times of repeated transmissions of the uplink data, the time-domain resources included in the transmission opportunity with RV0 are the minimum (only 2 symbols), and are much smaller than the time-frequency resources included in the transmission opportunities with other RVs (for example, there are 5 symbols in the transmission opportunity with RV 2). In general, data using RV0 contains the most information bits (information bits refer to useful bits to be actually transmitted), but uses the least time domain resources, resulting in fewer check bits in data using RV 0. Therefore, the decoding performance of the network device may be degraded, and the transmission reliability of the data packet may not be ensured, especially the reliability requirement of the URLLC scenario may not be met.

In this case, optionally, for multiple time domain resources indicated by one entry in the time domain resource allocation table, at least one first time domain resource in the multiple time domain resources corresponds to an RV with an index of 0, where the first time domain resource includes the time domain resource with the largest number of symbols in the multiple time domain resources. According to the optional method, the time domain resource with the largest number of symbols in the multiple time domain resources corresponds to the RV0, so that more check bits can be contained in the data adopting the RV0, and the decoding performance of a receiving end is improved.

Further optionally, values of RV indexes corresponding to each first time domain resource in the at least one first time domain resource are cycled according to the arrangement of RV indexes in RV sequences {0,2,3,1} or {0,3,0,3 }. In the optional method, when there are multiple time domain resources with the largest number of symbols in the multiple time domain resources, at least two time domain resources in the multiple time domain resources with the largest number of symbols correspond to different RVs. In this case, compared with the case that the same RV is used for all the time domain resources with the largest number of symbols, the decoding capability of the receiving end can be improved.

In the prior art, when the RV corresponding to the transmission opportunity is determined, it needs to be determined according to table 4 or table 5, and the RV corresponding to the transmission opportunity cannot be configured flexibly.

For a plurality of time domain resources indicated by one entry in the time domain resource allocation table, the time slots in which the plurality of time domain resources are located may be implemented in the following manner (1) or manner (2).

Mode (1),

By configuration of K₂、K₀The value of timeDomainOffset is realized, namely different K is configured for different time domain resources₂Or K₀Or timeDomainOffset. Illustratively, the type2 unlicensed transmission is taken as an example. In Table 6, i.e. by configuring different K₂To determine the time slots in which the different time domain resources are located.

For example, in Type1 unlicensed transmission, the method for determining time domain resources according to the method (1) is as follows:

an entry of the time domain resource allocation table configured by the network device or the default time domain resource allocation table contains the parameter K2. In an embodiment, the entry may further include a value combination of S and L (e.g., the value combination of S and L in the entry shown in table 7), and the value combination may be used to determine (or indicate) a time domain resource. In another embodiment, the table entry may further include a plurality of combinations of values of S and L (e.g., a plurality of combinations of S and L in the table entry shown in table 7), and each combination of values may be used to determine (or indicate) one time domain resource.

The terminal determines an entry in a time domain resource allocation table according to a time domain resource allocation (timeDomainAllocation) parameter in an RRC signaling for configuring the Type1 unlicensed transmission; and determining the time domain resource (transmission opportunity) for the Type1 unlicensed transmission according to the value of K2 associated with the determined table entry and the value of a time domain resource offset (timeDomainOffset) parameter in the RRC signaling. In a specific implementation manner, the terminal determines a time domain resource start symbol of a transmission opportunity according to the following formula one or formula two, where the determined transmission opportunity is a first transmission opportunity in an nth (N > ═ 0) time domain period:

the formula I is as follows:

[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number inthe frame×numberOfSymbolsPerSlot)+symbol number in the slot]＝((timeDomainOffset+K₂)×numberOfSymbolsPerSlot+S+N×periodicity)modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)；

the formula II is as follows:

[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number inthe frame×numberOfSymbolsPerSlot)+symbol number in the slot]＝(timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity)modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)。

in the above formula, sfn (system Frame number) is the system Frame number of the Frame; the number of time slots contained in each frame is numberOfSlotsPerFrame; the number of symbols contained in each time slot is numofsymbospersSlot; slot number in the frame is the index of the slot in the frame; symbol number in the slot is an index of a symbol in the slot(ii) a The period is a time domain period, and the size of the period can be obtained according to the period parameter in the RRC signaling for configuring Type1 unlicensed transmission; s is the initial symbol index of the first transmission opportunity in the time domain period, that is, the index of the initial symbol of the first time domain resource indicated by the information in the determined table entry, or the associated minimum K in the table entry₂A starting symbol index of a time domain resource of values. In this embodiment, if a position of a symbol in a time domain resource is such that any one of the above formulas is satisfied, the symbol is a starting symbol of a first transmission opportunity in a certain time domain period. The time domain position of the symbol may be characterized collectively by the index of the symbol in the slot, the index of the slot in the frame, and the system frame number of the frame.

Optionally, after determining the slot index y of the first transmission opportunity in the time domain period, the terminal determines the slot indexes of other transmission opportunities in the time domain period according to the following method: y + (K)₂-K_{2_min}). Wherein, K₂K associated with the transmission opportunity₂The transmission timing may be associated with K in the determined table entry₂Obtained of K_{2_min}K associated with the first time domain resource (transmission opportunity) in the time domain period₂I.e. the K associated with the first time domain resource in the determined table entry₂Or the minimum K associated with the determined table entry₂The value is obtained.

Mode (2),

The indication is aided by a new parameter. In this case, optionally, at least one entry in the time domain resource allocation table further includes a plurality of first offset values (denoted as m). The plurality of first offset values are used to determine a time slot in which a time domain resource of the plurality of transmission occasions is located. For example, it is used to determine the time slot in which the start symbol of the time domain resource is located, or it is used to determine the time slot in which the end symbol of the time domain resource is located, or it is used to determine the time slots in which all the symbols of the time domain resource are located. The first offset value may also be referred to as slot map (mappingToSlot) information.

Illustratively, referring to tables 7 and 8, table 7 shows the possible occurrence of the time domain resource allocation table for uplink transmissionOne entry. Table 8 shows a possible entry in the time domain resource allocation table for downlink transmission. In Table 7, K₂M is the first offset value. In Table 8, K₀M is the first offset value.

TABLE 7

TABLE 8

The tables 6 to 8 may be default tables in a standard protocol, and may also be tables configured for the terminal by the network device through signaling (e.g., RRC signaling). An example of a network device configuring a PUSCH time domain resource allocation table (e.g., table 7) for a terminal through higher layer signaling (e.g., RRC signaling) is given below:

the PUSCH-TimeDomainResourceAllocation information element is an information element used for configuring a PUSCH time domain resource allocation table in a high layer in RRC signaling. The information unit may include the following information:

information 1,

“PUSCH-TimeDomainResourceAllocationList::＝SEQUENCE(SIZE(1..maxNrofUL-Allocations))OF PUSCH-TimeDomainResourceAllocation”

The information 1 means that the uplink time domain resource allocation table configured by the higher layer includes one or more entries. Specifically, the PUSCH-timedomainresource allocation list refers to an uplink time domain resource allocation table configured in a higher layer. maxNrofUL-Allocations is the maximum number of entries contained in the uplink time domain resource allocation table. The PUSCH-timedomainresource allocation refers to an entry in the uplink time domain resource allocation table.

Information 2,

k2INTEGER(0..32)OPTIONAL,--Need S”

Information 2 refers to a k2 included in an entry in the uplink time domain resource allocation table, and the value of k2 is 0 to 32. k2 is information of the second offset value.

Information 3,

“TimeDomainResourceAllocationPerRepetitionList::＝SEQUENCE(SIZE(1..maxNrofRepetition))OF TimeDomainResourceAllocationPerRepetition”

The information 3 refers to information of multiple time domain resources for repeated transmission contained in one table entry in the uplink time domain resource allocation table configured by the higher layer. maxNrofRepetition refers to the maximum number of time domain resources configured in one table entry.

Information 4,

The information 4 is used for configuring information contained in one time domain resource for repeated transmission in one table entry. Specifically, the timedomainresource allocation repetition refers to a time domain resource for repeated transmission in one table entry. The time domain resource includes: mappingType (i.e., information of mapping type of PUSCH), startsymbol and length (information of starting symbol and length of time domain resource), RV (information of RV corresponding to time domain resource), mappingToSlot (i.e., information of first offset value (m) used for determining a time slot where the time domain resource is located).

Other tables may also be configured in a similar manner, and are not described in detail herein.

The implementation of the method (2) is different in different transmission scenarios, and is described below by cases 1 to 3, respectively.

Case 1, dynamically scheduled PUSCH transmission or type2 uplink unlicensed transmission

In case 1, the method for a terminal or a network device to determine time domain resources of one or more transmission occasions includes: and determining a time slot in which the time domain resource of the kth transmission opportunity in one or more transmission opportunities is located according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, n, a first offset value corresponding to the kth time domain resource contained in a table entry indicated by the second indication information and a second offset value contained in a table entry indicated by the second indication information, wherein k is an integer greater than 0.

In this case, the method may further include: the network device transmits the PDCCH to the terminal. Accordingly, the terminal receives the PDCCH from the network device. The PDCCH carries DCI used for scheduling the PUSCH, the DCI carries second indication information, and the index of a time slot in which the DCI is located is n. It should be noted that, for type2 uplink unlicensed transmission, DCI for activating type2 uplink unlicensed transmission may also be understood as DCI for scheduling PUSCH.

Illustratively, the index of the slot in which the time domain resource of the kth transmission opportunity of the one or more transmission opportunities is:

wherein u is_PUSCHParameter for characterizing the subcarrier spacing of PUSCH, u_PDCCHTo characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the second indication information, and C2 is a second offset value contained in the entry indicated by the second indication information.

Illustratively, assume that the slot in which the DCI is located is slot # n, u_PUSCH＝u_PDCCHThe entry indicated by the second indication information is the entry shown in table 7 (in this case, K₂0). Then, referring to fig. 5, the terminal may determine 3 transmission opportunities, the first transmission opportunity being located on slot # (n +0+0), i.e., symbol #12 through symbol #13 of slot # n, with RV 2. The second transmission opportunity is located at slot # (n +0+1), i.e., symbol #2 to symbol #6 of slot # (n +1), and the RV used is RV 0. The third transmission opportunity is located in slot # (n +0+1), i.e., symbol #9 to symbol #11 of slot # (n +1), and RV is RV 3.

Case 2, PDSCH transmission or Downlink SPS transmission based on dynamic scheduling

In case 2, the method for a terminal or a network device to determine time domain resources of one or more transmission occasions includes: and determining a time slot in which the time domain resource of the kth transmission opportunity in one or more transmission opportunities is located according to the subcarrier interval of the PDSCH, the subcarrier interval of the PDCCH, n, a first offset value corresponding to the kth time domain resource contained in a table entry indicated by second indication information and a second offset value contained in a table entry indicated by the second indication information, wherein k is an integer larger than 0.

In this case, the method may further include: the network device transmits the PDCCH to the terminal. Correspondingly, the terminal receives the PDCCH from the network device, the PDCCH carries the DCI for scheduling the PDSCH, the DCI carries the second indication information, and the index of the time slot in which the DCI is located is n. It should be noted that, for downlink SPS transmission, DCI for activating downlink SPS transmission may also be understood as DCI for scheduling PDSCH.

wherein u is_PDSCHParameter, u, characterizing the subcarrier spacing of PDSCH_PDCCHTo characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the second indication information, and C2 is a second offset value contained in the entry indicated by the second indication information.

Illustratively, assume that the slot in which the DCI is located is slot # n, u_PDSCH＝u_PDCCHThe entry indicated by the second indication information is the entry shown in table 8 (in this case, K₀0). Then, referring to fig. 5, the terminal may determine 3 transmission opportunities, the first transmission opportunity being located on slot # (n +0+0), i.e., symbol #12 through symbol #13 of slot # n, with RV 2. The second transmission opportunity is located at slot # (n +0+1), i.e., symbol #2 to symbol #6 of slot # (n +1), and the RV used is RV 0. The third transmission opportunity is located in slot # (n +0+1), i.e., symbol #9 to symbol #11 of slot # (n +1), and R is usedV is RV 3.

Case 3, type1 uplink grant-free transmission

In case 3, a time slot in which a kth transmission opportunity of the one or more transmission opportunities is located is determined according to the third offset value and the first offset value corresponding to the kth time domain resource included in the table entry indicated by the second indication information, where k is an integer greater than 0. The third offset value is the value of timeDomainOffset.

In this case, the method further includes: and the network equipment sends the configuration information of the uplink authorization-free transmission of the type1 to the terminal. Accordingly, the terminal receives the configuration information of the uplink grant-free transmission of the type1 from the network equipment. The configuration information includes configuration information of the second indication information and the third offset value.

Illustratively, the slot in which the kth transmission opportunity of the one or more transmission opportunities is located is: and the third offset value + the first offset value corresponding to the kth time domain resource contained in the table entry indicated by the second indication information, wherein k is an integer greater than 0.

For example, assuming that the third offset value is n, the entry indicated by the second indication information is the entry shown in table 7. Then, referring to fig. 5, the terminal may determine 3 transmission opportunities, the first transmission opportunity being located on slot # (n +0), i.e., symbol #12 through symbol #13 of slot # n, with RV being RV 2. The second transmission opportunity is located on symbols #2 to #6 of slot # (n +1), with RV being RV 0. The third transmission opportunity is located on symbol #9 to symbol #11 of slot # (n +1), and RV is taken as RV 3.

For PUSCH transmission or type2 uplink grant-free transmission based on dynamic scheduling (i.e. case 1 above), and PDSCH transmission based on dynamic scheduling or downlink transmission based on SPS (i.e. case 2 above), optionally, the DCI further includes a redundancy version indication field, where the redundancy version indication field is used to determine the maximum number of time domain resources for repeated transmission or the maximum number of times of repeated transmission or the maximum number of time slots for repeated transmission. The DCI refers to DCI for dynamically scheduling PUSCH transmission or PDSCH transmission, or DCI for activating Type2 uplink grant-free transmission or downlink SPS transmission. In the embodiment of the present application, the DCI for scheduling PUSCH transmission may be a DCI for dynamically scheduling PUSCH, or may be a DCI for activating Type2 uplink grant-free transmission; the DCI for scheduling PDSCH transmission may be a DCI for dynamically scheduling PDSCH transmission, or may be a DCI for activating downlink SPS-based transmission; the dynamically scheduled PUSCH transmission and the Type2 uplink unlicensed transmission are both referred to as PUSCH transmission, and the dynamically scheduled PDSCH transmission and the SPS-based downlink transmission are both referred to as PDSCH transmission.

The redundancy version indication field included in the DCI is originally used to indicate the RV corresponding to the time domain resource. In the embodiment of the present application, the information of the RV corresponding to the time domain resource can be obtained through the time domain resource allocation table. Thus, the redundancy version indication field may serve other purposes. For example, when the one or more transmission occasions are only used for partial repeated transmission, the redundancy version indication field may be used to determine the maximum number of time domain resources for repeated transmission or the maximum number of repeated transmissions or the maximum number of time slots for repeated transmission.

Optionally, the DCI for scheduling PUSCH transmission or PDSCH transmission does not include the redundancy version indication field, but includes a repeated transmission number indication field for determining the maximum number of time domain resources for repeated transmission or the maximum number of repeated transmissions or the maximum number of slots for repeated transmission.

In one possible implementation, the value indicated by the redundancy version indication field or the repeated transmission number indication field in the DCI is X (an integer greater than 1). The terminal determines that the maximum number of the time domain resources for the repeated transmission is X × K or the maximum number of times of the repeated transmission is X × K, and determines that the maximum number of time slots used for the repeated transmission is X × Y. The K transmission occasions over the Y time slots may be determined according to an entry in the time domain resource allocation table, where the number of K depends on the number of combinations of S and L in the entry.

Optionally, the positions of the K transmission opportunities determined by the terminal in the X1 × Y +1 th slot to the (X1+1) × Y slots (Y slots in total) in the Y slots are identical to the positions of the K transmission opportunities determined by the terminal in the 1 st slot to the Y slot (Y slots in total). Wherein X1 is more than or equal to 1 and less than or equal to X-1.

For example, referring to fig. 6, the terminal may determine the transmission timing in slot # (n +2) and slot # (n +3) according to the value of X and the transmission timing determined by the terminal in slot # n and slot # (n + 1). Here, the positions of the 3 transmission opportunities determined by the terminal in the slot # n and the slot # (n +1) are the same as the positions of the 3 transmission opportunities determined by the terminal in the slot # (n +2) and the slot # (n + 3).

Compared with the prior art, the method and the device can realize the dynamic indication of the repeated transmission times by configuring the repeated transmission times through the high-level signaling. On one hand, the repeated transmission times can be adjusted more quickly according to the channel conditions, so that the transmission reliability or the resource utilization rate and the like are improved. On the other hand, the number of repeated transmissions is determined by using the existing redundancy version indication field, and the DCI signaling overhead can not be increased.

In addition to determining the value of X through the redundancy version indication field or the retransmission number indication field in the DCI, the network device may also indicate the value of X through RRC signaling (e.g., parameter repK or pusch-aggregation factor or pdsch-aggregation factor in the RRC signaling) or MAC CE signaling or DCI.

In another possible implementation manner, the DCI for scheduling PUSCH transmission or PDSCH transmission may not include the repeat transmission number indication field, or the existing repeat transmission number indication field in the DCI is used for other indication purposes, in this embodiment, the repeat transmission number is specifically the number of time domain resources indicated by one entry in the time domain resource allocation table, that is, the number of value combinations of S and L in the entry. For example, taking table 6 as a time domain resource allocation table as an example, when the terminal device determines the time domain resource, the table entry with the index "1" in table 6 is used, and the number of times of the repeated transmission is specifically the number of value combinations of S and L in the table entry with the index "1", that is, "3". It should be noted that, the number of the value combinations of S and L in different entries in the time domain resource allocation table may be the same or different, and the embodiment of the present application is not limited.

It should be noted that, when the preset condition is satisfied, the terminal uses the original redundancy version indication field in the received DCI as the maximum number of time domain resources for determining the repeated transmission or the maximum number of times of the repeated transmission or the maximum number of time slots of the repeated transmission, or considers that the received DCI does not include the redundancy version indication field but includes the repeated transmission number indication field. . The preset condition may be one or more of the following conditions:

condition 1, the terminal determines that at least one entry in the used time domain resource allocation table includes information indicating a plurality of time domain resources and information indicating one or more RVs.

Condition 2, the table entry indicated by the second indication information contains information for indicating one or more RVs; or, the entry indicated by the second indication information includes information of RVs corresponding to a plurality of time domain resources for performing repeated data transmission.

Condition 3, the terminal receives indication information issued by the network device through RRC signaling or MAC CE signaling or DCI, where the indication information is used to indicate that the redundancy version indication field is used to determine the maximum number of time domain resources for repeated transmission or the maximum number of times of repeated transmission or the maximum number of time slots for repeated transmission; or, the indication information is used to indicate that the original redundancy version indication field does not exist but exists, or used to indicate that the redundancy version indication field is replaced by the repeated transmission number indication field.

And 4, the terminal determines that the RNTI of the CRC of the scrambled PDCCH is a specific RNTI. The PDCCH carries DCI for scheduling PUSCH or PDSCH transmissions.

Conditional 5, the terminal determines that the DCI format for scheduling the PUSCH or PDSCH is a specific format.

Condition 6, the terminal receives PDCCH on a specific type of search space, where the PDCCH carries DCI for scheduling PUSCH or PDSCH transmission. An embodiment of the present application further provides a method for determining transmission resources, as shown in fig. 7, including:

700. the terminal determines a time domain resource allocation table to use.

The specific implementation of step 700 is referred to above as step 400.

The time domain resource allocation table in this embodiment is different from the time domain resource allocation table in the above embodiment in that at least one entry in the time domain resource allocation table includes information for indicating a plurality of time domain resources and a plurality of first offset values, and the plurality of first offset values are used for determining a time slot in which the time domain resources of the plurality of transmission occasions are located, but do not include information for indicating an RV.

In a case that the plurality of time domain resource allocation tables include a time domain resource allocation table configured by the network device, optionally, the method further includes: (11) the network device sends the configuration information to the terminal. Accordingly, the terminal receives configuration information from the network device. The configuration information is used to configure a time domain resource allocation table. For further description of the configuration information, see above, no further description is provided here.

701. And the network equipment sends the third indication information to the terminal. The terminal receives the third indication information from the network device.

Wherein the third indication information is used for indicating an entry in the time domain resource allocation table. The third indication information may be carried in RRC signaling or MAC CE signaling or DCI.

702. The network device determines time domain resources for one or more transmission occasions for transmitting the PUSCH or PDSCH based on the third indication information and the time domain resource allocation table.

703. And the terminal determines the time domain resources of one or more transmission occasions for transmitting the PUSCH or the PDSCH according to the third indication information and the time domain resource allocation table.

In specific implementation of steps 702 and 703, the network device may determine the time domain resources of one or more transmission occasions according to the information indicating the time domain resources in the table entry indicated by the third indication information in the time domain resource allocation table. The information indicating the time domain resources may include: value of timeDomainOffset, K₂、K₀S, L and a first offset value.

In type1 uplink unlicensed transmission, the value of timeDomainOffset is sent through RRC signaling so that the terminal determines the timeslot where a time domain resource is located. To facilitate repeated transmission of data, information indicating a plurality of time domain resources may be included in one entry in the time domain resource allocation table. In this case, the terminal needs to determine the time slots where multiple time domain resources are located. At this time, the network device needs to send a plurality of values of timeDomainOffset through RRC signaling, so that the terminal determines the time slot in which the plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it needs to know the corresponding relationship between the values of the plurality of timeDomainOffset and the plurality of time domain resources, and therefore, the implementation process is complicated. According to the method provided by the embodiment of the application, the plurality of first offset values are configured in the table entry in the time domain resource allocation table to determine the time slots of the time domain resources of the plurality of transmission occasions, so that the terminal can rapidly determine the time slots of the plurality of time domain resources, and the implementation complexity of the terminal is reduced.

For multiple time domain resources indicated by one entry in the time domain resource allocation table, the time slots in which the multiple time domain resources are located may be in the mode (1) or the mode (2).

Mode (1),

By configuring an existing K₂、K₀The value of timeDomainOffset is realized, namely different K is configured for different time domain resources₂Or K₀Or timeDomainOffset. Illustratively, the type2 unlicensed transmission is taken as an example. In the above Table 6, namely, by configuring different K₂To determine the time slots in which the different time domain resources are located.

Mode (2),

An example of a network device configuring a PUSCH time domain resource allocation table for a terminal through higher layer signaling (e.g., RRC signaling) is given below:

information 1,

Information 2,

k2INTEGER(0..32)OPTIONAL,--Need S”

Information 3,

Information 4,

The information 4 is used for configuring information contained in one time domain resource for repeated transmission in one table entry. Specifically, the timedomainresource allocation repetition refers to a time domain resource for repeated transmission in one table entry. The time domain resource includes: mappingType (i.e., information of mapping type of PUSCH), startsymbol and length (i.e., information of starting symbol and length of time domain resource), mappingToSlot (i.e., information of first offset value (m) used to determine a slot where the time domain resource is located).

In case 1, the method for a terminal or a network device to determine time domain resources of one or more transmission occasions includes: and determining a time slot in which the time domain resource of the kth transmission opportunity in one or more transmission opportunities is located according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, n, a first offset value corresponding to the kth time domain resource contained in a table entry indicated by the third indication information and a second offset value contained in a table entry indicated by the third indication information, wherein k is an integer greater than 0.

In this case, the method may further include: the network device transmits the PDCCH to the terminal. Accordingly, the terminal receives the PDCCH from the network device. The PDCCH carries DCI used for scheduling the PUSCH, the DCI carries third indication information, and the index of a time slot in which the DCI is located is n.

wherein u is_PUSCHParameter for characterizing the subcarrier spacing of PUSCH, u_PDCCHTo characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the third indication letter, and C2 is a second offset value contained in the entry indicated by the third indication information.

In case 2, the method for a terminal or a network device to determine time domain resources of one or more transmission occasions includes: and determining a time slot in which the time domain resource of the kth transmission opportunity in one or more transmission opportunities is located according to the subcarrier interval of the PDSCH, the subcarrier interval of the PDCCH, n, a first offset value corresponding to the kth time domain resource contained in a table entry indicated by the third indication information and a second offset value contained in a table entry indicated by the third indication information, wherein k is an integer greater than 0.

In this case, the method may further include: the network device transmits the PDCCH to the terminal. Correspondingly, the terminal receives the PDCCH from the network device, the PDCCH carries DCI for scheduling the PDSCH, the DCI carries third indication information, and an index of a time slot in which the DCI is located is n.

wherein u is_PDSCHParameter, u, characterizing the subcarrier spacing of PDSCH_PDCCHTo characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value corresponding to the kth time domain resource contained in the entry indicated by the third indication information, and C2 is a second offset value contained in the entry indicated by the third indication information.

Case 3, type1 uplink grant-free transmission

In case 3, a time slot in which a kth transmission opportunity of the one or more transmission opportunities is located is determined according to a third offset value and a first offset value corresponding to the kth time domain resource included in the table entry indicated by the third indication information, where k is an integer greater than 0. The third offset value is the value of timeDomainOffset.

In this case, the method further includes: and the network equipment sends the configuration information of the uplink authorization-free transmission of the type1 to the terminal. Accordingly, the terminal receives the configuration information of the uplink grant-free transmission of the type1 from the network equipment. The configuration information includes configuration information of the third indication information and the third offset value.

Illustratively, the slot in which the kth transmission opportunity of the one or more transmission opportunities is located is: and the third offset value + the first offset value corresponding to the kth time domain resource contained in the table entry indicated by the third indication information, where k is an integer greater than 0. For further description of the mode (1) and the mode (2), see above, and are not described herein again.

Optionally, the DCI further includes a redundancy version indication field, where the redundancy version indication field is used to determine a maximum number of time domain resources for repeated transmission or a maximum number of times of repeated transmission or a maximum number of slots of repeated transmission.

Optionally, the DCI does not include the redundancy version indication field, but includes a repeated transmission number indication field for determining a maximum number of time domain resources for repeated transmission or a maximum number of repeated transmissions or a maximum number of slots for repeated transmission.

After the time domain resource and RV are determined according to the method shown in the foregoing embodiment, data may be transmitted or received on the determined time domain resource. For example, for downlink transmission, the network device may send downlink data on the determined time domain resource using the RV corresponding thereto, and the terminal receives the downlink data sent by the network device on the determined time domain resource according to the RV corresponding thereto; for uplink transmission, the terminal may use the RV corresponding to the terminal to transmit uplink data on the determined time domain resource, and the network device receives the uplink data transmitted by the terminal according to the RV corresponding to the network device on the determined time domain resource.

The embodiment of the present application further provides a method for determining transmission resources, including:

a terminal receives DCI from network equipment, wherein the DCI is used for dynamically scheduling PUSCH transmission or PDSCH transmission, or is used for activating Type2 uplink authorization-free transmission or activating SPS-based downlink transmission; determining a time domain resource allocation table and an item in the time domain resource allocation table according to the DCI; and determining the time domain resources for PUSCH transmission or PDSCH transmission according to the information contained in the determined table entry. In the present application, the dynamically scheduled PUSCH transmission and the Type2 uplink grant-free transmission are both referred to as PUSCH transmission, and the PDSCH transmission and the SPS-based downlink transmission are both referred to as PDSCH transmission.

A plurality of time domain resource allocation tables may exist in the terminal, and the plurality of time domain resource allocation tables may include: a default time domain resource allocation table (e.g., a time domain resource allocation table specified by a standard protocol), and/or a time domain resource allocation table configured by the network device. When the time domain resource allocation tables are configured by the network device, the configuration method may adopt the configuration method mentioned in the foregoing embodiments, which is not described herein again.

Optionally, each time domain resource allocation table is associated with one retransmission time, and the retransmission times associated with different time domain resource allocation tables may be the same or different.

In an embodiment, each entry of the time domain resource allocation table contains information of the number of repeated transmissions, but different entries contain the same information of the number of repeated transmissions.

In another embodiment, the time domain resource allocation table does not contain information of the number of retransmissions, but rather specifies that the table is associated with a number of retransmissions outside the table. In this embodiment, since one time domain resource allocation table is only associated with one retransmission time, different entries are associated with the same retransmission time for the same time domain resource allocation table, and when the retransmission time is needed, the terminal may determine, for example, directly use the retransmission time associated with the time domain resource allocation table according to the repetition time associated with the time domain resource allocation table used for determining the time domain resource.

Optionally, the time domain resource allocation table may not be associated with the number of repeated transmissions, where the number of repeated transmissions is determined by an entry in the time domain resource allocation table, for example, implicitly indicated according to the number of time domain resources indicated by the entry, or the entry includes the number of repeated transmissions. In an implementation manner, the number of the time domain resources indicated by the entry is specifically the number of the value combination of S and L. It should be noted that, the number of the value combinations of S and L in different entries in the time domain resource allocation table may be the same or different, and the embodiment of the present application is not limited. If the table entry in the time domain resource allocation table contains the number of times of retransmission, the values of the number of times of retransmission contained in different table entries may be the same or different, and the embodiment of the present application is not limited.

At least one entry in the time domain resource allocation table includes information for determining (or indicating) one or more time domain resources and information of a RV associated with the one or more time domain resources. It is to be understood that the table entry of the time domain resource allocation table may further include other types of information, for example, a PUSCH mapping type, and the present application is not limited thereto. In an example, the time domain resource allocation table may be in the form shown in tables 6 to 8, or a column is added to the table in the form shown in table 2 to indicate the RV information associated with each table entry.

The terminal receives DCI from a network device, where the DCI includes a time domain resource allocation (time domain) field, and the time domain resource allocation field may be used to determine a time domain resource for PUSCH transmission or a time domain resource for PDSCH transmission, and specifically, the time domain resource allocation field includes a bit for indicating one entry in a time domain resource allocation table. For Type2 unlicensed uplink transmission, the terminal receives DCI for activating Type2 unlicensed uplink transmission, and determines a time domain resource for Type2 unlicensed uplink transmission according to a time domain resource allocation domain in the DCI. For SPS-based downlink transmission, a terminal receives DCI for activating the SPS-based downlink transmission, and determines time domain resources for the SPS-based downlink transmission according to a time domain resource allocation domain in the DCI

The time domain resource allocation table to be used may be determined using any of the methods provided in any of the following embodiments.

Example one

In this embodiment, the terminal determines a time domain resource allocation table for PUSCH transmission or PDSCH transmission among the plurality of time domain resource allocation tables according to the redundancy version indication field in the DCI. The DCI format for scheduling PUSCH transmission and the DCI format for scheduling PDSCH in this embodiment may be the same as the existing DCI format for scheduling PUSCH transmission (e.g., DCI format 0_0 and DCI format 0_1) and the existing DCI format for scheduling PDSCH transmission (e.g., DCI format1_0 and DCI format1_ 1), respectively, but the redundancy version indication field in these formats does not indicate the redundancy version any more, but is used to indicate the time domain resource allocation table.

In an embodiment, a part of bits in the redundancy version indication field is used to indicate a time domain resource allocation table, for example, when there are 2 time domain resource allocation tables (table a, table B), the terminal determines a used table according to one bit in an RV indication field (for example, in an existing DCI format, the RV indication field occupies two bits), for example, when the value of the bit is 0, it indicates that the used table is table a; when the value of this bit is B, it indicates that the table used is table 2. The one bit may be any one bit in the RV indication field, for example, the first bit or the second bit.

Another way to achieve this is that all bits in the redundancy version indication field are used to indicate the time domain resource allocation table. For example, if there are 4 time domain resource allocation tables (table a, table B, table C, and table D), and all bits in the RV indication field indicate the used time domain resource allocation table, for example, if all bits of the RV indication field take values of 00, 01, 10, and 11, it indicates that the used time domain resource allocation tables are table a, table B, table C, and table D, respectively.

Optionally, when the preset condition is met, the terminal determines the time domain resource allocation table for PUSCH transmission or PDSCH transmission according to the redundancy version indication field in the DCI. In one embodiment, the preset condition includes any one of the following four conditions:

condition a: the terminal receives indication information issued by the base station through RRC signaling or MAC CE or DCI, and the indication information is used for indicating that the interpretation mode of the DCI is the interpretation mode provided by the embodiment of the invention.

Condition B: and the RNTI of the CRC which scrambles the PDCCH carrying the DCI is a preset RNTI.

Condition C: the PDCCH carrying the DCI is received in a specific search space.

Condition D: the format of the DCI is a specific format.

It is understood that the preset condition may be other conditions, as long as the condition is satisfied, the terminal interprets the function or meaning of the corresponding domain in DCI according to the method provided by the implementation of the present invention.

Example two

In this embodiment, the DCI does not carry a redundancy version indication field but carries a time domain resource allocation table indication field, where the time domain resource allocation table indication field indicates a time domain resource allocation table that needs to be used. And the terminal determines the time domain resource allocation table required to be used according to the time domain resource allocation table indication domain in the DCI.

Optionally, only when the preset condition (for example, any one of the conditions a to D) is satisfied, the terminal may consider that the received DCI includes the time domain resource allocation table indication field and does not include the redundancy version indication field.

EXAMPLE III

In this embodiment, the DCI does not include a redundancy version indication field, and the terminal determines a time domain resource allocation table to be used according to a predetermined part of bits in the time domain resource allocation field. For example, when there are 2 time domain resource allocation tables (table a, table B), the terminal determines the used table according to the bit located at the highest position in the time domain resource allocation field, for example, when the value of the bit is 0, table a is indicated, and when the value is 1, table 2 is indicated. For another example, when there are 4 time domain resource allocation tables (table a, table B, table C, table D), the terminal determines the table to be used from the 2 bits with the highest order in the time domain resource allocation domain, and for example, when the 2 bits take values of 00, 01, 10, and 11, the terminal instructs table a, table B, table C, and table D, respectively.

Optionally, only when the preset condition (for example, any one of the conditions a to D) is satisfied, the terminal may consider that the received DCI does not include the redundancy version indication field, and determine the time domain resource allocation table to be used according to the predetermined partial bits of the time domain resource allocation field in the DCI.

And determining a table entry in the determined time domain resource allocation table according to the time domain resource allocation domain, and determining the time domain resource for PUSCH transmission or PDSCH transmission according to the information in the table entry. In an embodiment, the terminal determines an entry in the determined time domain resource allocation table according to a predetermined part of bits in the time domain resource allocation table, for example, when the required time domain resource allocation table is determined according to the method provided in the third embodiment, the remaining bits in the time domain resource allocation table (i.e., bits that are not used for indicating the time domain resource allocation table) are used for indicating an entry in the determined time domain resource allocation table. For example, the time domain resource allocation field in the DCI occupies 6 bits, one value of two bits located at a high level is used to indicate one time domain resource allocation table in the multiple time domain resource allocation tables, and one value of four bits located at a low level is used to indicate one entry in the time domain resource allocation table.

Optionally, the terminal determines the number of times of retransmission associated with the terminal according to the determined time domain resource allocation table. Further, the terminal may send the PUSCH according to the determined time domain resource and the number of times of retransmission for PUSCH transmission, or receive the PDSCH according to the determined time domain resource and the number of times of retransmission for PDSCH transmission. Optionally, the terminal may further determine, according to the determined number of times of repeated transmission and the determined entry, a time domain resource used for PUSCH transmission or PDSCH transmission. The method for determining the time domain resource according to the repeated transmission book and the determined table entry may refer to the methods described in other embodiments in the present application, and details are not described here.

In this embodiment, the RV used for PUSCH or PDSCH transmission is determined by an entry in the time domain resource allocation table, so the RV indication field in the DCI is no longer needed to indicate the RV, and a bit of the RV indication field may be used to indicate other information, or the RV indication field is no longer set in the DCI. When different tables correspond to different repeated transmission times, the time domain resource allocation table used by the indication domain indication of the time domain resource allocation table replaced by the RV indication domain or the RV indication domain is the same as the repeated transmission times of the PUSCH or PDSCH indicated by the RV indication domain, that is, the dynamic indication of the repeated transmission times is realized on the premise of not increasing DCI signaling overhead. When the RV indication field is not set in the DCI any more, the saved bits may be used to indicate other information, which may not only achieve dynamic indication of other information, but also save signaling overhead.

a terminal receives DCI from network equipment, wherein the DCI is used for scheduling PUSCH transmission or PDSCH transmission; the terminal determines one table entry in a time domain resource allocation table according to the time domain allocation domain in the DCI; and determining the time domain resources used for the PUSCH transmission or the PDSCH transmission according to the information contained in the table entry.

There exists a time domain resource allocation table in the terminal, and the time domain resource allocation table may include: a default time domain resource allocation table (e.g., a time domain resource allocation table specified by a standard protocol), and/or a time domain resource allocation table configured by the network device. When the time domain resource allocation table is configured by the network device, the network device may directly configure the content of the time domain resource allocation table, and the configuration method may adopt the configuration method mentioned in the foregoing embodiments, which is not described herein again. In another embodiment, the network device may configure multiple time domain resource allocation tables for the terminal device, but indicate one valid time domain resource allocation table by carrying in RRC signaling or MAC CE) signaling or DCI.

At least one entry in the time domain resource allocation table includes information for determining (or indicating) one or more time domain resources and information for determining a RV associated with the one or more time domain resources. In one embodiment, each entry contains information of RV (index of RV or RV sequence or RV number). In another embodiment, a part of entries of the time domain resource allocation table contain information of RV, and the remaining entries do not contain information of RV.

It is to be understood that the table entry of the time domain resource allocation table may further include other types of information, for example, a PUSCH mapping type, and the present application is not limited thereto. In an example, the form of the time domain resource allocation table may be a table in the form shown in tables 6 to 8, or a column may be added to the table in the form shown in table 2 to indicate RV information associated with each entry, or some entries in the table in the form shown in table 2 may be added with information indicating RV while other entries do not include information indicating RV.

In an embodiment, the terminal determines an entry in a used time domain resource allocation table according to a partial bit in the RV indication field and the time domain resource allocation field. For example, the terminal determines an entry in the used time domain resource allocation table according to N +1 bits which are one bit in the RV indication domain and N bits in the time domain resource allocation domain, where N is a bit number included in the time domain resource allocation domain, and N is an integer whose value is greater than or equal to 1. The value of the N +1 bits indicates one entry in the time domain resource allocation table. For example, when N is 4, one Bit in the RV indication field and 4 bits of the time domain resource allocation field form 5 bits, where the Bit in the RV indication field is located at the Most Significant Bit (MSB) of the 5 bits, and when the value of the 5 bits is 00000, the first entry in the time domain resource allocation table is indicated, and when the value of the 5 bits is 10000, the 17 th entry in the time domain resource allocation table is indicated. Optionally, when a preset condition (as any one of the conditions a to D described above) is satisfied, the terminal determines, according to one bit in the RV indication field and N +1 bits of N bits in the time domain resource allocation field, an entry in the used time domain resource allocation table.

In another implementation manner, the terminal determines an entry in the used time domain resource allocation table according to all bits in the RV indication field and the time domain resource allocation field. For example, the terminal determines an entry in the used table according to all bits in the RV indication field and N +2 bits, which are N +2 bits of the N bits in the time domain resource allocation field, where N is a bit number included in the time domain resource allocation field, and N is an integer whose value is greater than or equal to 1. One value of the N +2 bits indicates a particular entry in the table. For example, when N is 4, all bits in the RV indication field and 4 bits of the time domain resource allocation field form 6 bits, where 2 bits in the RV indication field are located at the first two Most Significant Bits (MSB) of the 6 bits, the 6 bits indicate the first entry in the table when their value is 000000, and the 6 bits indicate the 33 th entry in the table when their value is 100000. Optionally, when a preset condition (as any one of the conditions a to D described above) is satisfied, the terminal determines, according to all bits in the RV indication field and N +2 bits in the N bits in the time domain resource allocation field, an entry in the used time domain resource allocation table.

In another implementation, the DCI does not include any RV indication field, and the terminal determines one entry in the time domain resource allocation table only according to the time domain resource allocation field.

In this embodiment, the RV used for PUSCH or PDSCH transmission is determined by an entry in the table, and therefore, the RV indication field in the DCI is not required to be reused to indicate the RV, but may be used to indicate an entry in the used time domain resource allocation table, thereby supporting more time domain resource allocation possibilities on the premise of not increasing DCI overhead, and making time domain resource allocation more flexible. The above-mentioned scheme of the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is to be understood that each network element, for example, the network device and the terminal, includes at least one of a hardware structure and a software module corresponding to each function for implementing the functions. Those of skill in the art would readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the network device and the terminal may be divided into the functional units according to the above method examples, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.

In the case of using an integrated unit, fig. 8 shows a schematic diagram of a possible structure of the communication device (denoted as the communication device 80) in the above embodiment, where the communication device 80 includes a processing unit 801 and a communication unit 802, and may further include a storage unit 803. The schematic structure diagram shown in fig. 8 can be used to illustrate the structures of the network device and the terminal involved in the above embodiments.

When the schematic structure shown in fig. 8 is used to illustrate the structure of the terminal in the above-described embodiment, the processing unit 801 is configured to control and manage the actions of the terminal, for example, the processing unit 801 is configured to support the terminal to perform the actions performed by the terminal in fig. 4, 400, 401, and 403, 800, 801, and 803 in fig. 8, and/or other processes described in this embodiment of the present application. The processing unit 801 may communicate with other network entities, e.g. with the network devices shown in fig. 4, via the communication unit 802. The storage unit 803 is used to store program codes and data of the terminal. In another embodiment, the processing unit 801 is configured to determine one time domain resource allocation table and one entry in the time domain resource allocation table according to the received DCI; and determining the time domain resources for PUSCH transmission or PDSCH transmission according to the information contained in the determined table entry. The communication unit is used for receiving the DCI.

When the schematic configuration diagram shown in fig. 8 is used to illustrate the configuration of the terminal in the above embodiment, the communication device 80 may be a terminal or a chip in the terminal.

When the schematic structure shown in fig. 8 is used to illustrate the structure of the network device in the foregoing embodiment, the processing unit 801 is configured to control and manage the actions of the network device, for example, the processing unit 801 is configured to support the network device to execute actions executed by the network device in 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or other processes described in this embodiment of the present application. The processing unit 801 may communicate with other network entities, e.g. with the terminal shown in fig. 4, via the communication unit 802. The storage unit 803 is used to store program codes and data of the network device. In another embodiment, the processing unit 801 is configured to generate DCI, where the DCI includes an indication field indicating a time domain resource allocation table and an entry in the time domain resource allocation table. The communication unit is used for transmitting the DCI.

When the schematic structure diagram shown in fig. 8 is used to illustrate the structure of the network device in the above embodiment, the communication device 80 may be a network device or a chip in a network device.

When the communication device 80 is a terminal or a network device, the processing unit 801 may be a processor or a controller, and the communication unit 802 may be a communication interface, a transceiver circuit, a transceiver device, or the like. The communication interface is a generic term, and may include one or more interfaces. The storage unit 803 may be a memory. When the communication device 80 is a chip within a terminal or a network device, the processing unit 801 may be a processor or a controller, and the communication unit 802 may be an input/output interface, a pin or a circuit, etc. The storage unit 803 may be a storage unit (e.g., a register, a cache memory, etc.) within the chip, or may be a storage unit (e.g., a read-only memory, a random access memory, etc.) located outside the chip within a terminal or a network device.

The communication unit may also be referred to as a transceiver unit. The antenna and the control circuit having a transmitting and receiving function in the communication apparatus 80 can be regarded as the communication unit 802 of the communication apparatus 80, and the processor having a processing function can be regarded as the processing unit 801 of the communication apparatus 80. Alternatively, a device in the communication unit 802 for implementing a receiving function may be regarded as a receiving unit, where the receiving unit is configured to perform the receiving step in the embodiment of the present application, and the receiving unit may be a receiver, a receiving circuit, and the like. The device for realizing the transmission function in the communication unit 802 may be regarded as a transmission unit for performing the steps of transmission in the embodiment of the present application, and the transmission unit may be a transmitter, a transmission circuit, or the like.

The integrated unit in fig. 8, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or make a contribution to the prior art, or all or part of the technical solutions may be implemented in the form of a software product stored in a storage medium, and including several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. A storage medium storing a computer software product comprising: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The elements in fig. 8 may also be referred to as modules, for example, the processing elements may be referred to as processing modules.

The embodiment of the present application further provides a schematic diagram of a hardware structure of a communication device (denoted as the communication device 90), and referring to fig. 9 or fig. 10, the communication device 90 includes a processor 901, and optionally, further includes a memory 902 connected to the processor 901.

The processor 901 may be a general processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs according to the present disclosure. The processor 901 may also include a plurality of CPUs, and the processor 901 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, or processing cores that process data (e.g., computer program instructions).

The memory 902 may be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, which is not limited in this respect by the embodiments of the present application. The memory 902 may be separate or integrated with the processor 901. The memory 902 may include, among other things, computer program code. The processor 901 is configured to execute the computer program code stored in the memory 902, thereby implementing the methods provided by the embodiments of the present application.

In a first possible implementation, referring to fig. 9, the communication device 90 further comprises a transceiver 903. The processor 901, memory 902 and transceiver 903 are connected by a bus. The transceiver 903 is used for communication with other devices or communication networks. Optionally, the transceiver 903 may include a transmitter and a receiver. The means in the transceiver 903 for performing the receiving function may be considered as a receiver, which is used for performing the receiving step in the embodiments of the present application. The means for implementing the transmitting function in the transceiver 903 may be regarded as a transmitter for performing the steps of transmitting in the embodiments of the present application.

Based on a first possible implementation manner, the schematic structure diagram shown in fig. 9 may be used to illustrate the structure of the network device or the terminal involved in the foregoing embodiments.

When the schematic structure shown in fig. 9 is used to illustrate the structure of the terminal in the above embodiments, the processor 901 is configured to control and manage the actions of the terminal, for example, the processor 901 is configured to support the terminal to execute the actions executed by the terminal in 400, 401, and 403 in fig. 4, 800, 801, and 803 in fig. 8, and/or other processes described in this embodiment. The processor 901 may communicate with other network entities, e.g., the network devices shown in fig. 4, via the transceiver 903. The memory 902 is used for storing program codes and data of the terminal.

When the schematic structure shown in fig. 9 is used to illustrate the structure of the network device in the foregoing embodiment, the processor 901 is configured to control and manage the actions of the network device, for example, the processor 901 is configured to support the network device to execute actions executed by the network device in 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or other processes described in this embodiment. The processor 901 may communicate with other network entities, e.g. with the terminal shown in fig. 4, via the transceiver 903. The memory 902 is used to store program codes and data for the network devices.

In a second possible implementation, the processor 901 includes logic circuits and at least one of an input interface and an output interface. Wherein the output interface is used for executing the sent action in the corresponding method, and the input interface is used for executing the received action in the corresponding method.

Based on the second possible implementation manner, referring to fig. 10, the schematic structure diagram shown in fig. 10 may be used to illustrate the structure of the network device or the terminal involved in the foregoing embodiments.

When the schematic structure shown in fig. 10 is used to illustrate the structure of the terminal in the above embodiments, the processor 901 is configured to control and manage the actions of the terminal, for example, the processor 901 is configured to support the terminal to execute the actions executed by the terminal in 400, 401, and 403 in fig. 4, 800, 801, and 803 in fig. 8, and/or other processes described in this embodiment. The processor 901 may communicate with other network entities, for example, with the network devices shown in fig. 4, through at least one of the input interface and the output interface. The memory 902 is used for storing program codes and data of the terminal.

When the schematic structure shown in fig. 10 is used to illustrate the structure of the network device in the foregoing embodiment, the processor 901 is configured to control and manage the actions of the network device, for example, the processor 901 is configured to support the network device to execute actions executed by the network device in 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or other processes described in this embodiment. The processor 901 may communicate with other network entities, for example, with the terminal shown in fig. 4, through at least one of the input interface and the output interface. The memory 902 is used to store program codes and data for the network devices.

In addition, the embodiment of the present application further provides a schematic diagram of a hardware structure of a terminal (denoted as terminal 110) and a network device (denoted as network device 120), which may specifically refer to fig. 11 and fig. 12, respectively.

Fig. 11 is a schematic diagram of a hardware structure of the terminal 110. For convenience of explanation, fig. 11 shows only main components of the terminal. As shown in fig. 11, the terminal 110 includes a processor, a memory, a control circuit, an antenna, and an input-output device.

The processor is mainly configured to process the communication protocol and the communication data, and control the entire terminal, execute the software program, process data of the software program, for example, to control the terminal to perform actions performed by the terminal in 400, 401, and 403 in fig. 4, 800, 801, and 803 in fig. 8, and/or other processes described in this embodiment of the present application. The memory is used primarily for storing software programs and data. The control circuit (also referred to as a radio frequency circuit) is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The control circuit and the antenna together, which may also be called a transceiver, are mainly used for transceiving radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are used primarily for receiving data input by a user and for outputting data to the user.

When the terminal is started, the processor can read the software program in the memory, interpret and execute the instruction of the software program, and process the data of the software program. When data needs to be sent through the antenna, the processor performs baseband processing on the data to be sent, and then outputs baseband signals to a control circuit in the control circuit, and the control circuit performs radio frequency processing on the baseband signals and then sends the radio frequency signals to the outside through the antenna in the form of electromagnetic waves. When data is sent to the terminal, the control circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data.

Those skilled in the art will appreciate that fig. 11 shows only one memory and processor for ease of illustration. In an actual terminal, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this application.

As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, where the baseband processor is mainly used to process a communication protocol and communication data, and the central processing unit is mainly used to control the whole terminal, execute a software program, and process data of the software program. The processor in fig. 11 integrates the functions of the baseband processor and the central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may also be independent processors, and are interconnected through a bus or the like. Those skilled in the art will appreciate that the terminal may include a plurality of baseband processors to accommodate different network formats, a plurality of central processors to enhance its processing capability, and various components of the terminal may be connected by various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.

Fig. 12 is a schematic diagram of a hardware structure of the network device 120. The network device 120 may include one or more radio frequency units, such as a Remote Radio Unit (RRU) 1201 and one or more baseband units (BBUs) (which may also be referred to as Digital Units (DUs)) 1202.

The RRU1201 may be referred to as a transceiver unit, transceiver, transceiving circuitry, or transceiver, etc., which may include at least one antenna 1211 and a radio frequency unit 1212. The RRU1201 is mainly used for transceiving radio frequency signals and converting radio frequency signals to baseband signals. The RRU1201 and the BBU1202 may be physically located together or separately, for example, a distributed base station.

The BBU1202 is a control center of a network device, and may also be referred to as a processing unit, and is mainly used for performing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like.

In an embodiment, the BBU1202 may be formed by one or more boards, and the boards may jointly support a radio access network (e.g., an LTE network) with a single access indication, or may respectively support radio access networks with different access schemes (e.g., an LTE network, a 5G network, or other networks). The BBU1202 also includes a memory 1221 and a processor 1222, the memory 1221 being configured to store necessary instructions and data. The processor 1222 is used to control the network devices to perform the necessary actions. The memory 1221 and processor 1222 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be appreciated that network device 120 shown in fig. 12 may be capable of performing actions by network devices in 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or other processes described in embodiments of the present application. The operations and functions, or the operations and functions, of the modules in the network device 120 are respectively configured to implement the corresponding flows in the above-described method embodiments. Specifically, reference may be made to the description of the above method embodiments, and the detailed description is appropriately omitted herein to avoid redundancy.

In implementation, the steps of the method provided by this embodiment may be implemented by hardware integrated logic circuits in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. Other descriptions about the processor in fig. 11 and 12 can refer to the description about the processor in fig. 9 and 10, and are not repeated.

Embodiments of the present application also provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform any of the above methods.

Embodiments of the present application also provide a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the methods described above.

An embodiment of the present application further provides a communication system, including: the network equipment and the terminal.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented using a software program, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are all or partially generated upon loading and execution of computer program instructions on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). Computer-readable storage media can be any available media that can be accessed by a computer or can comprise one or more data storage devices, such as servers, data centers, and the like, that can be integrated with the media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for determining transmission resources, comprising:

the terminal receives indication information from network equipment, wherein the indication information is used for indicating one table entry in a time domain resource allocation table, and at least one table entry in the time domain resource allocation table comprises information used for indicating a plurality of time domain resources and information used for indicating one or more Redundancy Versions (RV);

and the terminal determines the time domain resources and RV of one or more transmission occasions for transmitting the physical uplink shared channel PUSCH or the physical downlink shared channel PDSCH according to the indication information and the time domain resource allocation table.

2. The method of claim 1, further comprising:

the terminal receives configuration information from the network device, wherein the configuration information is used for configuring the time domain resource allocation table.

3. The method of claim 1 or 2, wherein the at least one entry in the time domain resource allocation table further comprises a plurality of first offset values, and the plurality of first offset values are used for determining a time slot in which the time domain resources of the plurality of transmission occasions are located.

4. The method of claim 3, wherein each entry in the time domain resource allocation table further comprises a second offset value, the method further comprising:

the terminal receives a Physical Downlink Control Channel (PDCCH) from the network equipment, wherein the PDCCH carries Downlink Control Information (DCI) used for scheduling the PUSCH, the DCI carries the indication information, and the index of a time slot in which the DCI is positioned is n;

correspondingly, the determining, by the terminal, the time domain resources of one or more transmission occasions for transmitting the PUSCH according to the indication information and the time domain resource allocation table includes:

and the terminal determines the time slot where the time domain resource of the kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information and a second offset value contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

5. The method of claim 4, wherein an index of a slot in which a time domain resource of a kth transmission opportunity of the one or more transmission opportunities is located is:

6. The method of claim 3, wherein each entry in the time domain resource allocation table further comprises a second offset value, the method further comprising:

the terminal receives a PDCCH from the network equipment, the PDCCH carries DCI used for scheduling the PDSCH, the DCI carries the indication information, and the index of a time slot in which the DCI is located is n;

correspondingly, the determining, by the terminal, the time domain resources of one or more transmission occasions for transmitting the PDSCH according to the indication information and the time domain resource allocation table includes:

and the terminal determines the time slot of the time domain resource of the kth transmission opportunity in the one or more transmission opportunities according to the subcarrier interval of the PDSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in a table entry indicated by the indication information and a second offset value contained in a table entry indicated by the indication information, wherein k is an integer greater than 0.

7. The method of claim 6, wherein the one or more transmissions are at a timeThe index of the time slot in which the time domain resource of the kth transmission opportunity is located is:

8. The method according to any one of claims 4 to 7, wherein the DCI further includes a redundancy version indication field, and when the entry indicated by the indication information includes information of RVs corresponding to multiple time domain resources for performing repeated transmission of data, the redundancy version indication field is used to determine the maximum number of time domain resources for the repeated transmission or the maximum number of times of the repeated transmission or the maximum number of time slots for the repeated transmission.

9. The method of claim 3, further comprising:

the terminal receives configuration information of uplink authorization-exempt transmission of type1 from the network equipment, wherein the configuration information comprises the configuration information of the indication information and a third offset value; and determining a time slot in which a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

10. The method of any one of claims 1-9, wherein at least one first time domain resource of the plurality of time domain resources corresponds to an RV with an index of 0, and wherein the first time domain resource comprises a largest number of symbols among the plurality of time domain resources.

11. The method of claim 10, wherein the index of the RV corresponding to each of the at least one first time domain resource takes values circularly according to an arrangement of RV indexes in RV sequences {0,2,3,1} or {0,3,0,3 }.

12. An apparatus for determining transmission resources, comprising: a communication unit and a processing unit;

the communication unit is configured to receive indication information from a network device, where the indication information is used to indicate one entry in a time domain resource allocation table, and at least one entry in the time domain resource allocation table includes information used to indicate multiple time domain resources and information used to indicate one or more redundancy versions RV;

and the processing unit is configured to determine, according to the indication information and the time domain resource allocation table, time domain resources and RVs of one or more transmission occasions for transmitting a physical uplink shared channel PUSCH or a physical downlink shared channel PDSCH.

13. The apparatus of claim 12,

the communication unit is further configured to receive configuration information from the network device, where the configuration information is used to configure the time domain resource allocation table.

14. The apparatus of claim 12 or 13, wherein the at least one entry in the time domain resource allocation table further comprises a plurality of first offset values, and wherein the plurality of first offset values are used to determine a time slot in which a time domain resource of the plurality of transmission occasions is located.

15. The apparatus of claim 14, wherein each entry in the time domain resource allocation table further comprises a second offset value;

the communication unit is further configured to receive a physical downlink control channel PDCCH from the network device, where the PDCCH carries downlink control information DCI for scheduling the PUSCH, the DCI carries the indication information, and an index of a time slot in which the DCI is located is n;

the processing unit is specifically configured to: and determining a time slot in which a time domain resource of a kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PUSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in an entry indicated by the indication information and a second offset value contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

16. The apparatus of claim 15, wherein an index of a slot in which a time domain resource of a kth transmission opportunity of the one or more transmission opportunities is:

17. The apparatus of claim 14, wherein each entry in the time domain resource allocation table further comprises a second offset value;

the communication unit is further configured to receive a PDCCH from the network device, where the PDCCH carries DCI for scheduling the PDSCH, the DCI carries the indication information, and an index of a time slot in which the DCI is located is n;

the processing unit is specifically configured to: determining a time slot in which a time domain resource of a kth transmission opportunity in the one or more transmission opportunities is located according to the subcarrier interval of the PDSCH, the subcarrier interval of the PDCCH, the n, a first offset value corresponding to the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

18. The apparatus of claim 17, wherein an index of a slot in which a time domain resource of a kth transmission opportunity of the one or more transmission opportunities is:

19. The apparatus according to any of claims 15-18, wherein the DCI further comprises a redundancy version indication field, and when an entry indicated by the indication information includes information of RVs corresponding to a plurality of time domain resources for performing repeated transmission of data, the redundancy version indication field is configured to determine a maximum number of the time domain resources for the repeated transmission or a maximum number of times of the repeated transmission or a maximum number of slots of the repeated transmission.

20. The apparatus of claim 14,

the communication unit is further configured to receive configuration information of uplink grant-less transmission of type1 from the network device, where the configuration information includes configuration information of the indication information and a third offset value; and determining a time slot in which a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value corresponding to the kth time domain resource contained in the table entry indicated by the indication information, wherein k is an integer greater than 0.

21. The apparatus of any one of claims 12-20, wherein at least one first time domain resource of the plurality of time domain resources corresponds to an RV with an index of 0, and wherein the first time domain resource comprises a largest number of symbols among the plurality of time domain resources.

22. The apparatus of claim 21, wherein the index of the RV corresponding to each of the at least one first time domain resource takes values circularly according to an arrangement of RV indexes in RV sequences {0,2,3,1} or {0,3,0,3 }.

23. An apparatus for determining transmission resources, comprising: a processor;

the processor is coupled to a memory for storing computer-executable instructions, the processor executing the computer-executable instructions stored by the memory to cause the apparatus to implement the method of any one of claims 1-11.

24. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1-11.

25. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-11.