CN111770577B

CN111770577B - Method and device for determining transmission resources

Info

Publication number: CN111770577B
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: 2023-12-08
Anticipated expiration: 2039-04-30
Also published as: CN111770577A

Abstract

The application provides a method and a device for determining transmission resources, in the method, a terminal and network equipment can determine time domain resources and RV for transmitting one or more transmission occasions of a PUSCH or a PDSCH based on indication information indicating one table item 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 RV, in this case, the network device does not need to indicate the RV corresponding to the transmission opportunity through DCI, so that signaling overhead of DCI may be reduced. The application relates to the technical field of communication.

Description

Method and device for determining transmission resources

The present application claims priority from chinese patent office, application number 201910254156.5, application name "method and apparatus for determining transmission resources" filed on 30/03/2019, the entire contents of which are incorporated herein by reference.

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 (augmented reality, AR) and internet of things technologies, more and more terminals will be available in the future, and the usage of network data will also be continuously increased. Therefore, in the fifth generation (5G) communication system and the future evolution communication system, network resources become particularly precious, which needs to reduce the signaling overhead as much as possible while meeting the 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 above purpose, the present application provides the following technical solutions:

in a first aspect, a method for determining transmission resources is provided, including: the terminal receives indication information from the network equipment, wherein the indication information is used for indicating one table item in a time domain resource allocation table, and at least one table item in the time domain resource allocation table comprises information for indicating a plurality of time domain resources and information for indicating one or more RVs; and the terminal determines time domain resources and RV 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, table entries in the time domain resource allocation table are only used for determining time domain resources of transmission opportunities, and are not used for determining the RVs adopted by the transmission opportunities, and the RVs corresponding to each transmission opportunity also need to be indicated in addition by DCI. In the method provided in the first aspect, the table entry in the time domain resource allocation table may include information for indicating RV, in this case, the network device does not need to indicate the RV corresponding to the transmission opportunity through DCI, so 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. By the possible implementation mode, the terminal can possibly obtain different time domain resource allocation tables, so that different requirements are met, and the transmission efficiency is improved.

In one possible implementation, the at least one entry in the time domain resource allocation table further includes a plurality of first offset values, where 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. In type1 uplink unlicensed transmission, the network device sends a 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 slot in which the plurality of time domain resources are located. At this time, the network device needs to send values of a plurality of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it is also required to know the correspondence between the values of the plurality of timeDomainOffset and the plurality of time domain resources, so the implementation process is complex. According to the method, the time slots where the time domain resources of the transmission opportunities are located are determined by configuring the plurality of first offset values in the table items in the time domain resource allocation table, so that the time slots where the time domain resources are located can be determined rapidly by the terminal, 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, wherein the PDCCH carries DCI for scheduling the PUSCH, the DCI carries the indication information, and the index of a time slot where the DCI is positioned is n; correspondingly, the terminal determines the time domain resource of one or more transmission occasions for transmitting the PUSCH according to the indication information and the time domain resource allocation table, and the method comprises the following steps: the terminal determines a time slot in which 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 of the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in the entry indicated by the indication information, where k is an integer greater than 0.

In one possible implementation, the index of the time slot in which the time domain resource of the kth transmission opportunity of the one or more transmission opportunities is located is:wherein u is _PUSCH To characterize the parameters of the sub-carrier spacing of the PUSCH, u _PDCCH In 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, wherein the PDCCH carries DCI for scheduling the PDSCH, the DCI carries the indication information, and the index of a time slot where the DCI is positioned is n; correspondingly, the terminal determines the time domain resource of one or more transmission occasions for transmitting the PDSCH according to the indication information and the time domain resource allocation table, and the method comprises the following steps: the terminal determines a time slot in which 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 PDSCH, the subcarrier interval of the PDCCH, the n, a first offset value of the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in the entry indicated by the indication information, where k is an integer greater than 0.

In one possible implementation, the index of the time slot in which the time domain resource of the kth transmission opportunity of the one or more transmission opportunities is located is:wherein u is _PDSCH To characterize the parameters of the subcarrier spacing of the PDSCH, u _PDCCH In 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 manner, the DCI further includes a redundancy version indication field, where the 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 used to determine a maximum number of the time domain resources for repeated transmission or a maximum number of the repeated transmission or a maximum number of time slots for repeated transmission.

In one possible implementation, the method further includes: the terminal receives configuration information of uplink unlicensed transmission of type1 from the network equipment, wherein the configuration information comprises the indication information and configuration information of a third offset value; and determining a time slot where a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value of a corresponding kth time domain resource contained in an entry indicated by the indication information, wherein k is an integer greater than 0. In type1 uplink unlicensed transmission, a 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 slot in which the plurality of time domain resources are located. At this time, the network device needs to send values of a plurality of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it is also required to know the correspondence between the values of the plurality of timeDomainOffset and the plurality of time domain resources, so the implementation process is complex. According to the method, the time slots where the time domain resources of the transmission opportunities are located can be determined by configuring the plurality of first offset values in the table items in the time domain resource allocation table, so that the time slots where the time domain resources are located can be determined rapidly by the terminal, and the implementation complexity of the terminal is reduced.

In one possible implementation manner, at least one first time domain resource in the plurality of time domain resources corresponds to RV with index of 0, wherein the first time domain resource is a time domain resource containing the largest number of symbols in the plurality of time domain resources. According to the possible implementation mode, the time domain resource with the largest symbol number in the plurality of time domain resources corresponds to RV0, so that more check bits in the data adopting RV0 can be used, and the decoding performance of the receiving end is improved.

In one possible implementation manner, the values of the RV indexes corresponding to the respective first time domain resources in the at least one first time domain resource are cyclically arranged according to the RV indexes in the RV sequence {0, 2, 3, 1} or {0,3,0,3 }. In this possible implementation manner, in the case that there are multiple time domain resources with the largest number of symbols in the multiple time domain resources, at least two time domain resources with the largest number of symbols in the multiple time domain resources correspond to different RVs. In this case, compared with the case where the plurality of time domain resources with the largest number of symbols all adopt the same RV, the decoding capability of the receiving end can be improved.

In a second aspect, a method for determining transmission resources is provided, comprising: the network equipment sends indication information to the terminal, wherein the indication information is used for indicating one table item in a time domain resource allocation table, and at least one table item in the time domain resource allocation table comprises information for indicating a plurality of time domain resources and information for indicating one or more RVs; the network device determines time domain resources and RVs for 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, table entries in the time domain resource allocation table are only used for determining time domain resources of transmission opportunities, and are not used for determining the RVs adopted by the transmission opportunities, and the RVs corresponding to each transmission opportunity also need to be indicated in addition by DCI. In the method provided in the second aspect, the table entry in the time domain resource allocation table may include information for indicating RV, in this case, the network device does not need to indicate RV corresponding to the transmission opportunity through DCI, so signaling overhead of 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 manner enables the base station to flexibly configure the time domain resource allocation table for the terminal, thereby adapting to different requirements and improving transmission efficiency.

In one possible implementation, the at least one entry in the time domain resource allocation table further includes a plurality of first offset values, where 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. In type1 uplink unlicensed transmission, a 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 slot in which the plurality of time domain resources are located. At this time, the network device needs to send values of a plurality of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it is also required to know the correspondence between the values of the plurality of timeDomainOffset and the plurality of time domain resources, so the implementation process is complex. According to the method, the time slots where the time domain resources of the transmission opportunities are located are determined by configuring the plurality of first offset values in the table items in the time domain resource allocation table, so that the time slots where the time domain resources are located can be determined rapidly by the terminal, 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, wherein the PDCCH carries DCI for scheduling the PUSCH, the DCI carries the indication information, and the index of a time slot where the DCI is positioned is n; accordingly, the network device determines, based on the indication information and the time domain resource allocation table, time domain resources for one or more transmission occasions for transmitting PUSCH, including: the network device determines a time slot in which 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 of the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in the entry indicated by the indication information, where k is an integer greater than 0.

In one possible implementation, the index of the time slot in which the time domain resource of the kth transmission opportunity of the one or more transmission opportunities is located is:wherein u is _PUSCH To characterize the sub-carrier spacing of the PUSCH Parameters u _PDCCH In 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 network equipment sends a PDCCH to the terminal, wherein the PDCCH carries DCI for scheduling the PDSCH, the DCI carries the indication information, and the index of a time slot where the DCI is positioned is n; accordingly, the network device determines, based on the indication information and the time domain resource allocation table, time domain resources for one or more transmission occasions for transmitting PDSCH, 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 of a corresponding kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in the entry indicated by the indication information, where k is an integer greater than 0.

In one possible implementation, the method further includes: the network equipment sends configuration information of uplink unlicensed transmission of type1 to the terminal, wherein the configuration information comprises the indication information and configuration information of a third offset value; and determining a time slot where a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value of a corresponding kth time domain resource contained in an entry indicated by the indication information, wherein k is an integer greater than 0. In type1 uplink unlicensed transmission, a 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 slot in which the plurality of time domain resources are located. At this time, the network device needs to send values of a plurality of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it is also required to know the correspondence between the values of the plurality of timeDomainOffset and the plurality of time domain resources, so the implementation process is complex. According to the method, the time slots where the time domain resources of the transmission opportunities are located are determined by configuring the plurality of first offset values in the table items in the time domain resource allocation table, so that the time slots where the time domain resources are located can be determined rapidly by the terminal, and the implementation complexity of the terminal is reduced.

In a third aspect, a method for determining transmission resources is provided, 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, at least one table entry in the time domain resource allocation table comprises 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 time slots where the time domain resources of the plurality of transmission occasions are located; and the terminal determines time domain resources for transmitting one or more transmission occasions of 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 currently sent through RRC signaling so that the terminal determines the 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 slot in which the plurality of time domain resources are located. At this time, the network device needs to send values of a plurality of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it is also required to know the correspondence between the values of the plurality of timeDomainOffset and the plurality of time domain resources, so the implementation process is complex. In the method provided in the third aspect, a plurality of first offset values are configured in entries in the time domain resource allocation table, so that a time slot in which time domain resources of a plurality of transmission opportunities are located is determined, so that the terminal can quickly determine the time slot in which the 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 index of the time slot in which the time domain resource of the kth transmission opportunity of the one or more transmission opportunities is located is:wherein u is _PUSCH To characterize the parameters of the sub-carrier spacing of the PUSCH, u _PDCCH In order to characterize the parameter of the subcarrier spacing of the PDCCH, C1 is a first offset value of 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 terminal receives configuration information of uplink unlicensed transmission of type 1 from the network equipment, wherein the configuration information comprises the indication information and configuration information of a third offset value; and determining a time slot where a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value of a corresponding kth time domain resource contained in an 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 the 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 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 where the time domain resources of the plurality of transmission occasions are located; the network device determines time domain resources for transmitting one or more transmission occasions of PUSCH or PDSCH based on the indication information and the time domain resource allocation table.

In type1 uplink unlicensed transmission, a 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 slot in which the plurality of time domain resources are located. At this time, the network device needs to send values of a plurality of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it is also required to know the correspondence between the values of the plurality of timeDomainOffset and the plurality of time domain resources, so the implementation process is complex. According to the method provided by the fourth aspect, the plurality of first offset values are configured in the table items in the time domain resource allocation table to determine the time slots where the time domain resources of the plurality of transmission opportunities are located, so that the terminal can rapidly determine the time slots where the plurality of 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 used to indicate a plurality of time domain resources and information used to indicate one or more RVs; the processing unit is configured to determine, according to the indication information and the time domain resource allocation table, a time domain resource and RV for transmitting one or more transmission occasions of PUSCH or 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 one possible implementation, the at least one entry in the time domain resource allocation table further includes a plurality of first offset values, where 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.

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 slot where the DCI is located is n; the processing unit is specifically configured to: and determining a time slot in which 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 an entry indicated by the indication information and a second offset value contained in the entry indicated by the indication information, wherein k is an integer greater than 0.

In one possible implementation, the index of the time slot in which the time domain resource of the kth transmission opportunity of the one or more transmission opportunities is located is:wherein u is _PUSCH To characterize the parameters of the sub-carrier spacing of the PUSCH, u _PDCCH To characterize the parameters of the subcarrier spacing of the PDCCH, C1 is the fingerAnd C2 is a second offset value contained in the table item 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; 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 slot where the DCI is located is n; the processing unit is specifically configured to: and determining a time slot in which 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 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 the 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 receive, from the network device, configuration information of an uplink unlicensed transmission of type 1, where the configuration information includes the indication information and configuration information of a third offset value; and determining a time slot where a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value of a corresponding kth time domain resource contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

In one possible implementation manner, at least one first time domain resource in the plurality of time domain resources corresponds to RV with index of 0, wherein the first time domain resource is a time domain resource containing the largest number of symbols in the plurality of time domain resources.

In one possible implementation manner, the values of the RV indexes corresponding to the respective first time domain resources in the at least one first time domain resource are cyclically arranged according to the RV indexes in the 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 RV for transmitting one or more transmission occasions of PUSCH or 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 slot where the DCI is located is n; the processing unit is specifically configured to: and determining a time slot in which 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 an entry indicated by the indication information and a second offset value contained in the entry indicated by the indication information, wherein k is an integer greater than 0.

In one possible implementation, the index of the time slot in which the time domain resource of the kth transmission opportunity of the one or more transmission opportunities is located is: Wherein u is _PUSCH To characterize the parameters of the sub-carrier spacing of the PUSCH, u _PDCCH In 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; 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 slot where the DCI is located is n; the processing unit is specifically configured to: and determining a time slot in which 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 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 the entry indicated by the indication information, wherein k is an integer greater than 0.

In one possible implementation, the one or more transmissions The index of the time slot in which the time domain resource of the kth transmission opportunity in the opportunities is located is:wherein u is _PDSCH To characterize the parameters of the subcarrier spacing of the PDSCH, u _PDCCH In 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 send configuration information of uplink unlicensed transmission of type 1 to the terminal, where the configuration information includes the indication information and configuration information of a third offset value; and determining a time slot where a kth transmission opportunity in the one or more transmission opportunities is located according to the third offset value and a first offset value of a corresponding kth time domain resource contained in an entry indicated by the indication information, wherein k is an integer greater than 0.

In a seventh aspect, there is provided an apparatus for determining transmission resources, the apparatus having functionality to implement any of the methods provided in the third aspect. The functions 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 functions described above. 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 transmission and/or reception) and a processing unit for performing the actions of the transmission and/or reception in the third aspect. Optionally, the actions performed by the communication unit are performed under control of the processing unit. Optionally, the communication unit includes a transmitting unit for performing the act of transmitting in the third aspect and a receiving unit for performing the act of receiving in the third aspect. The device may exist in the form of a chip product.

In an eighth aspect, there is provided an apparatus for determining transmission resources, the apparatus having functionality to implement any of the methods provided in the fourth aspect. The functions 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 functions described above. For example, the apparatus may comprise a communication unit for performing the actions of the processing in the fourth aspect (e.g. actions other than transmission and/or reception) and a processing unit for performing the actions of the transmission and/or reception in the fourth aspect. Optionally, the actions performed by the communication unit are performed under control of the processing unit. Optionally, the communication unit includes a transmitting unit for performing the act of transmitting in the fourth aspect and a receiving unit for performing the act of receiving in the fourth aspect. The device may exist 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 to a memory for storing computer-executable instructions, the processor executing the computer-executable instructions stored in the memory to implement any one of the methods provided in the first, second, third or fourth aspects. The memory and the processor may be integrated together or may be separate devices. In the latter case, the memory may be located within the means for determining transmission resources or may be located outside the means 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 for performing the act of transmitting in the respective method and the input interface is for performing the act of receiving in the respective method.

In one 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 the 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 for performing the act of transmitting in the respective method and a receiver for performing the act of receiving in the respective method.

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

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 run 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 of the methods provided in the first, second, third or fourth aspects.

Technical effects caused by any implementation manner of the fifth aspect to the twelfth aspect may be referred to technical effects caused by corresponding implementation manners of the first aspect to the fourth aspect, and are not described herein.

The various possible implementations of any of the foregoing aspects may be combined without contradiction between the schemes.

Drawings

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

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

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 various data according to an embodiment of the present application;

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 of a communication device according to an embodiment of the present application;

fig. 9 and fig. 10 are schematic hardware structures of a communication device according to an embodiment of the present application;

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

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

Detailed Description

In the description of the present application, "/" means "or" unless otherwise indicated, for example, A/B may mean A or B. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. Furthermore, "at least one" means one or more, and "a plurality" means two or more. The terms "first," "second," and the like do not limit the number and order of execution, and the terms "first," "second," and the like do not necessarily differ.

In the present application, the words "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts 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 (long term evolution, LTE) communication system, a New Radio (NR) communication system employing 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, machine-to-machine (machine to machine, abbreviated as M2M), macro-micro communication, enhanced mobile broadband (enhanced mobile broadband, abbreviated as eMBB), ultra-reliable and ultra-low latency communication (ultra-low & low latency communication, abbreviated as URLLC), mass internet of things communication (massive machine type communication, abbreviated as mctc), internet of things (internet of things, abbreviated as IoT), industrial internet of things (IoT, abbreviated as IIoT), and the like.

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

For convenience of description, the following description will take the application of the technical solution provided in the embodiment of the present application between a network device and a terminal as an example. It can be understood that, when the technical solution provided in the embodiments 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 embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application. As can be known to those skilled in the art, with the evolution of the network architecture and the appearance of new service scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.

A network device is an entity on the network side that sends signals or receives signals or both. The network device may be a device deployed in a radio access network (radio access network, RAN for short) to provide wireless communication functionality for the terminal, e.g. a base station. The network device may be a macro base station, a micro base station (also called a small station), a relay station, an Access Point (AP) or the like in various forms, and may also include various forms of control nodes, such as a network controller. The control node can be connected with a plurality of base stations and can configure resources for a plurality of terminals covered by the plurality of base stations. In systems employing different radio access technologies, the names of base station capable devices may vary. For example, the global system for mobile communications (global system for mobile communication, GSM) or code division multiple access (code division multiple access, CDMA) network may be referred to as a base transceiver station (base transceiver station, BTS) and the wideband code division multiple access (wideband code division multiple access, WCDMA) network may be referred to as a base station (NodeB), the LTE system may be referred to as an evolved NodeB (eNB or eNodeB), the 5G communication system or the NR communication system may be referred to as a next generation base station node (next generation node base station, gNB), and the specific name of the base station is not limited by the present application. The network device may also be a wireless controller in the cloud wireless access network (cloud radio access network, abbreviated CRAN) scenario, a network device in a public land mobile network (public land mobile network, abbreviated PLMN) that evolves in the future, a transmission receiving node (transmission and reception point, abbreviated TRP), etc.

A terminal is an entity on the user side for receiving signals or transmitting signals or both. The terminal is for providing one or more of a voice service and a data connectivity service to the user. A terminal may also be called 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 (MS), a drone, an IoT device, a Station (ST) in a wireless local area network (wireless local area networks, WLAN), a cellular phone (cellular phone), a smart phone (smart phone), a cordless phone, a wireless data card, a tablet, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital processing (personal digital assistant, PDA) device, a laptop (machine type communication, MTC) terminal, a handheld device with wireless communication capability, a computing device, or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device (may also be referred to as a wearable smart device). The terminal may also be a terminal in a next generation communication system, for example, a terminal in a 5G communication system or a terminal in a future evolved PLMN, a terminal in an NR communication system, etc.

To facilitate an understanding of the present application, some concepts related to the embodiments of the present application are briefly described herein.

1. Time slots

In NR, 1 slot contains 14 orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) symbols (hereinafter, referred to as symbols) for a normal (normal) Cyclic Prefix (CP). For an extended (extended) CP,1 slot contains 12 symbols.

For convenience of description, in the embodiment of the present application, 1 slot contains 14 symbols unless specifically described. In the time 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 addition, the present application hereinafter refers to a slot with index (i.e., number) j as slot #j. j is an integer of 0 or more, and i is an integer of 0 or more and 13 or less.

2. Transmission scene applicable to the application

The transmission scene applicable to the application comprises: uplink transmission based on dynamic scheduling, downlink transmission based on Semi-persistent scheduling (Semi-Persistent Scheduling, abbreviated as SPS) and uplink unlicensed transmission.

The uplink unlicensed transmission means that: the uplink transmission of the terminal is not required to be completed through the dynamic scheduling of the network equipment. Specifically, when uplink data arrives (in the embodiment of the present application, the data arrives already processed and can be sent), the terminal does not need to send a scheduling request (scheduling request, abbreviated as SR) to the network device and wait for dynamic grant (dynamic grant) of the network device, but can directly send the uplink data to the network device using the transmission resource and the designated transmission parameter pre-allocated by the network device.

The uplink unlicensed transmission may also be referred to as: uplink scheduling-free transmission, uplink dynamic grant transmission (UL data transmission without dynamic grant), uplink dynamic scheduling-free transmission, configured Grant (CG) transmission, higher layer configured transmission, and the like.

Uplink unlicensed transmissions fall into two categories: physical uplink shared channel (physical uplink shared channel, abbreviated PUSCH) transmission based on a first type of configuration grant (type 1PUSCH transmission with a configured grant, or PUSCH transmission with type 1 configured grant, or type 1 configured grant PUSCH transmission) and PUSCH transmission based on a second type of configuration grant (type 2 PUSCH transmission with a configured grant, or PUSCH transmission with type 2 configured grant, or type 2 configured grant PUSCH transmission).

The existing PUSCH transmission configuration mode based on the first type of configuration authorization is as follows: the network device configures the terminal with all transmission resources and transmission parameters through higher layer parameters, such as configurable grantconfigug. For example: the method comprises the steps of a period of time domain resources, open loop power control related parameters, waveforms, redundancy version (redundancy version, RV for short), repetition times, frequency hopping modes, resource allocation types, the number of hybrid automatic repeat request (hybrid automatic repeat request, HARQ for short), demodulation reference signal (de-modulation reference signal, DMRS for short) related parameters, a modulation coding scheme (modulation and coding scheme, MCS for short) table, a resource block group (resource block group, RBG for short) size, all transmission resources and transmission parameters including time domain resources, frequency domain resources, MCS and the like. After receiving the higher layer parameters, the terminal can immediately use the configured transmission parameters to perform PUSCH transmission on the configured time-frequency resources.

The existing configuration mode of PUSCH transmission based on the second type of configuration authorization is divided into the following two steps: first, the network device configures a portion of transmission resources and transmission parameters to the terminal through higher layer parameters (e.g., configurable grantconfig). 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. Thereafter, the network device transmits downlink control information (downlink control information, abbreviated DCI) (e.g., configuration-specific DCI) to the terminal, so that the terminal activates PUSCH transmission based on the second type of configuration grant and simultaneously configures transmission resources and transmission parameters including time domain resources, frequency domain resources, DMRS-related parameters, MCS, etc. It should be noted that, the PUSCH transmission authorized by the second type of configuration can only be used after being activated.

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

3. Transmission opportunity (transmission occasion, TO for short)

The transmission opportunity includes a time domain resource for transmitting the data once. One transmission occasion includes one or more symbols. When there are a plurality of transmission opportunities and the plurality of transmission opportunities are used for repeated transmission, a plurality of identical data are repeatedly transmitted on the plurality of transmission opportunities. At this time, one data transmission on one transmission occasion may be referred to as one repetition transmission. The multiple identical data refer to multiple identical or different RVs obtained after the same information bit is channel coded.

4. Repetition (Repetition) and Slot aggregation (Slot aggregation) transmissions

In order to improve the transmission reliability of data, the timeslot aggregation transmission and the repeated transmission of data are supported in the NR communication system, and the timeslot aggregation transmission and the repeated transmission refer to transmission of multiple identical data, and only because of different transmission scenes of applications, different names are defined. The transmission mode of transmitting multiple identical data based on dynamic scheduling is called time slot aggregation transmission. The transmission mode of transmitting multiple identical data based on SPS or uplink grant is called repeated transmission. SPS-based repeat transmissions may also be referred to as bundling (bundling) transmissions.

Since a transmission opportunity for transmitting a PUSCH or a physical downlink shared channel (physical downlink shared channel, PDSCH) once cannot include a slot boundary (slot boundary) and an uplink/downlink symbol switching point (DL/UL switching point). Therefore, when the time slot is used for aggregation transmission or repeated transmission, the transmission opportunity containing different numbers of symbols is supported for 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. Where a slot boundary refers to the boundary of two slots. The uplink/downlink symbol switching point refers to the boundary between the uplink symbol and the downlink symbol. The available symbols refer to symbols that can be used for PUSCH or PDSCH transmission, whether one symbol is available or not, depending on the scenario 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-frequency multiplexing (time-division duplexing, abbreviated TDD) system, referring to fig. 2, it is assumed that a network device configures a 1 st symbol (i.e., symbol # 0) and an 8 th symbol (i.e., symbol # 7) in a slot as downlink symbols (denoted by D), configures a 2 nd symbol (i.e., symbol # 1) and a 9 th symbol (i.e., symbol # 8) as flexible symbols (denoted by F), and configures other symbols as uplink symbols (denoted by U) through DCI. To reduce the latency after the uplink data is ready at the 12 th symbol of slot #1 (i.e., symbol # 11), it should be allowed to start transmitting the uplink data from the 13 th symbol of slot #1 (i.e., symbol # 12). Otherwise, the transmission of the uplink data is not started until the 3 rd symbol of the slot #2 (i.e. symbol # 2), and a delay of 4 symbols is introduced, which is not acceptable for the llc traffic with extremely sensitive delay. To simultaneously ensure the reliability of data transmission, assuming that a total of 10 symbols are required for multiple repeated transmissions of the uplink data, the uplink data may be repeated 3 times in total starting from the 13 th symbol of slot #1 (i.e., symbol # 12) and ending from the 12 th symbol of slot #2 (i.e., symbol # 11), 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 to allocate time domain resources.

In NR, the network device configures a time domain resource allocation table for the terminal through higher layer signaling, where the table contains at most 16 rows (entries) (i.e., 16 entries). After configuring the time domain resource allocation table, referring to table 1, the network device may indicate which row of resources in the time domain resource allocation table are allocated to the terminal using DCI (e.g., time domain resource assignment field in DCI) for dynamic scheduling based uplink transmission, dynamic scheduling based downlink transmission, SPS based downlink transmission, and type2 uplink unlicensed transmission. For type1 uplink unlicensed transmission, the network device may use radio resource control (radio resource control, abbreviated RRC) signaling (e.g., timeDomainAllocation IE parameters in RRC signaling) to indicate which row of resources in the time domain resource allocation table are allocated for the terminal.

TABLE 1

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

Each row in the time domain resource allocation table for downlink transmission contains 3 parameters: k (K) ₀ The type of mapping, the start symbol and the length. Wherein K is ₀ Time domain offset for PDSCH transmission. The slot of PDSCH transmission may be slot# (n2+k) ₀ ) Where n2 is a slot in which 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 start symbol and length, also referred to as SLIV, are used to determine the start symbol S (i.e., the first symbol in the time domain resource) and the length L (i.e., the number of symbols the time domain resource contains) of the allocated time domain resource in the slot.

If the network device does not configure the time domain resource allocation table for the terminal through higher layer signaling, the terminal uses a default (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, table 6.1.2.1.1-2 in the default uplink time domain resource allocation table contains details see table 2. The value of j in table 2 relates to the uplink subcarrier spacing, and see table 3 for specific details.

TABLE 2

TABLE 3 Table 3

u _PUSCH	j
		0	1
1	1
		2	2

Note that: u (u) _PUSCH Is a parameter used to characterize the uplink subcarrier spacing. The left column 0, 1, 2 in table 3 each represents an uplink subcarrier spacing.

The basis of 16 default combinations or configuration through RRC signaling is known at the terminalFor type1 uplink unlicensed transmission, the network device indicates one of 16 combinations to the terminal through RRC signaling (e.g., a timedomainalllocation parameter in RRC signaling), and since type1 uplink unlicensed transmission has a special RRC parameter (e.g., timeDomainOffset) indicating a slot offset, the terminal determines a starting slot of an 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 in 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 repeated transmission data

In order to enable the receiving end to enhance the decoding capability by means of the combined receiving method of incremental redundancy (incremental redundancy, abbreviated as IR), the network device configures different repeated transmissions to use different RVs. In the prior art, the following method is used to determine the RV employed for different repeated transmissions:

For time slot aggregation transmission based on dynamic scheduling, the RV adopted by PDSCH transmission or PUSCH transmission passes through the index p (0+.p<K, K is a slot aggregation factor, i.e. the number of slots for repeated transmission) and RV indicated by RV indication field in DCI for scheduling PDSCH or PUSCH _id Co-determination, rv _id Refers to the index of RV. For example, as specified in 3gpp ts38.214, the RV corresponding to the transmission opportunity of index p for transmitting PDSCH is determined by table 4, and the RV corresponding to the transmission opportunity of index p for transmitting PUSCH is determined by table 5. "mod" in tables 4 and 5 means "remainder". The transmission occasion with index p may also be referred to as the p-th transmission occasion.

TABLE 4 Table 4

TABLE 5

For repeated transmission based on SPS or uplink grant, an index p (0<p +.k, K is the number of repeated transmission) of a transmission opportunity corresponding to the transmission time of the RV adopted by the repeated transmission of the PUSCH and an RV sequence (for example, may be {0, 0} or {0,3,0,3} or {0,2,3,1 }) configured by a high-level passing parameter repK-RV are determined together. For example, the RV employed for PUSCH transmission on a transmission occasion indexed p is the (mod (p-1, 4) +1) value in the configured RV sequence. For example, if the RV sequence configured by the network device higher-layer passing parameter repK-RV 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, in fig. 3, RV0, RV2, and RV3 are respectively adopted for 3 repeated transmissions. 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.

The embodiment of the application provides a method for determining transmission resources, and for convenience of description, time slot aggregation transmission and retransmission are collectively referred to as retransmission in the embodiment of the application. As shown in fig. 4, a method for determining transmission resources according to an embodiment of the present application includes:

400. the terminal determines the time domain resource allocation table used.

There may be a plurality of time domain resource allocation tables in the terminal, and the plurality of time domain resource allocation tables may include: a default time domain resource allocation table, and/or a network device configured time domain resource allocation table. 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 hereinafter in the embodiments of the present application is a time domain resource allocation table satisfying this condition. In the case where the plurality of time domain resource allocation tables comprises a network device configured time domain resource allocation table, optionally, the method further comprises: the network device sends configuration information to the terminal. Accordingly, the terminal receives configuration information from the network device. The configuration information is used to configure the time domain resource allocation table. Wherein 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 configuration information may be carried in RRC signaling or medium access control (medium access control, MAC) control element (MAC control element, MAC CE) signaling or DCI.

In step 400, the terminal determines that the time domain resource allocation table used may be default or configured for the terminal for the network device.

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

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

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 (for example, time domain resource assignment field in DCI or timeDomainAllocation IE parameter in RRC), and specifically may increase a bit (bit) to indicate a time domain resource allocation table used by the terminal, or may indicate that a specific time domain resource allocation table is used when the time domain resource allocation parameter takes a specific value or values.

In the second mode, the terminal determines a used time domain resource allocation table according to the type of the radio network temporary identifier (radio network temporary identifier, abbreviated as RNTI) used for scrambling the cyclic redundancy check (cyclic redundancy check, abbreviated as CRC) of the physical downlink control channel (physical downlink control channel, abbreviated as 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.

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

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

In the third aspect, 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 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.

The search space type of the PDCCH comprises: a common search space, a terminal-specific search space, etc.

In the fourth aspect, 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 through blind detection in different search spaces, 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 indication information (denoted as second indication information) to the terminal, and the terminal receives the second indication information from the network device accordingly.

The second indication information is used for indicating one table 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 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 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 entry indicated by the second indication information in the time domain resource allocation table.

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

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

TABLE 6

403. And the terminal determines time domain resources and RV 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 determining the time domain resource and RV of one or more transmission occasions by the terminal is similar to that of the network device, and will not be 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 corresponding RV to transmit downlink data on one or more transmission occasions, and the terminal adopts corresponding RV to receive the downlink data on one or more transmission occasions; or the terminal adopts the corresponding RV to send the uplink data on one or more transmission occasions, and the network equipment adopts the corresponding RV to receive the uplink data on one or more transmission occasions.

In the prior art, table entries in the time domain resource allocation table are only used for determining time domain resources of transmission opportunities, and are not used for determining the RVs adopted by the transmission opportunities, and the RVs corresponding to each transmission opportunity also need to be indicated in addition by DCI. In the method provided by the embodiment of the application, the table entry in the time domain resource allocation table can include information for indicating RV, in this case, the network device does not need to indicate the RV corresponding to the transmission opportunity through DCI, and the RV indication domain originally existing in the DCI can be used for other indication functions, so that the signaling overhead of the DCI can 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 guarantee 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 repeated transmissions of uplink data, the time domain resources included in the transmission opportunity using RV0 are minimal (only 2 symbols), which is far less than the time frequency resources included in the transmission opportunities using other RVs (e.g., there are 5 symbols in the transmission opportunity using RV 2). Typically, the 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 parity bits in the 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 guaranteed, and in particular, the reliability requirement of the URLLC scenario may not be satisfied.

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

Further optionally, the value of the RV index corresponding to each first time domain resource in the at least one first time domain resource is cyclic according to the arrangement of RV indexes in RV sequence {0, 2, 3, 1} or {0,3,0,3 }. In the alternative method, in the case that a plurality of time domain resources with the largest number of symbols exist in a plurality of time domain resources, at least two time domain resources with the largest number of symbols in the plurality of time domain resources correspond to different RVs. In this case, compared with the case where the plurality of time domain resources with the largest number of symbols all adopt the same RV, the decoding capability of the receiving end can be improved.

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

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

Mode (1),

By configuring K ₂ 、K ₀ Realization of the value of timeDomainOffset, i.e. for different time domain resources, different K's are configured ₂ Or K ₀ Or timeDomainOffset. Illustratively, 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.

In the example of Type1 unlicensed transmission, the method for determining the time domain resource according to the mode (1) is as follows:

one entry of the network device configured time domain resource allocation table or the default time domain resource allocation table contains parameter K2. In one embodiment, the entry may also contain a combination of values for S and L (e.g., the combination of S and L in the form entry shown in Table 7), which may be used to determine (or indicate) a time domain resource. In another embodiment, the entry may also contain multiple combinations of values for S and L (e.g., multiple combinations of S and L in the form entry shown in Table 7), each of which may be used to determine (or indicate) a time-domain resource.

The terminal determines an entry in a time domain resource allocation table according to a time domain resource allocation (timeDomainalllocation) parameter in RRC signaling for configuring Type1 unlicensed transmission; and determining the time domain resource (transmission opportunity) for Type1 unlicensed transmission according to the determined value of K2 associated with the 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:

Equation one:

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

formula II:

[(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in the 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; number ofslotsperframe is the number of slots contained per frame; number ofsymbolsper is the number of symbols contained per slot; slot number in the frame is the index of the slot in the frame; symbol number in the slot is the index of the symbol in the slot; the Periodicity is a time domain period, and the size of the Periodicity can be obtained according to the Periodicity parameter in the RRC signaling used for configuring Type1 unlicensed transmission; s is the index of the initial symbol of the first transmission opportunity in the time domain period, i.e. 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 ₂ The starting symbol index of the time domain resource of the value. In the embodiment of the present application, the position of a symbol in the time domain resource is such that any one of the above formulas is satisfied, and the symbol is the start symbol of the first transmission opportunity in a certain time domain period. The time domain position of the symbol may be determined by the index of the symbol in the slotThe index of the slot in the frame, and the system frame number of the frame are collectively characterized.

Optionally, after determining the slot index y where the first transmission opportunity is located in the time domain period, the terminal determines the slot indexes where other transmission opportunities are located in the time domain period according to the following method: y+ (K) ₂ -K _{2_min} ). Wherein K is ₂ K associated with the transmission opportunity ₂ Can be based on the K associated with the transmission opportunity in the determined entry ₂ Obtained, K _{2_min} K associated for the first time domain resource (transmission occasion) in the time domain period ₂ That is, K associated with the first time domain resource in the determined entry ₂ Or the minimum K associated in the determined entry ₂ Values.

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 comprises 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 opportunities is located. For example, for determining the time slot in which the starting symbol of the time domain resource is located, or for determining the time slot in which the ending symbol of the time domain resource is located, or for determining the time slot in which all symbols of the time domain resource are located. The first offset value may also be referred to as slot map (mappingToSlot) information.

For example, referring to tables 7 and 8, table 7 shows one entry that may occur in the uplink time domain resource allocation table. Table 8 shows one entry that may occur in the time domain resource allocation table for downlink transmission. In Table 7, K ₂ And m is the first offset value. In Table 8, K ₀ And m is the first offset value.

TABLE 7

TABLE 8

/>

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

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

information 1,

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

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

Information 2,

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

The information 2 refers to one k2 contained in one 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”

Information 3 refers to information of a plurality of time domain resources for repeated transmission contained in one entry in the uplink time domain resource allocation table of the higher layer configuration. maxNrofRepetition refers to the maximum number of time domain resources configured in an entry.

Information 4,

Information 4 is used to configure information contained in one time domain resource for repeated transmission in one entry. Specifically, timedomainresource allocation period refers to a time domain resource for repeated transmission in an entry. The time domain resource includes: mapingtype (i.e., information of a mapping type of PUSCH), startSymbolAndLength (i.e., information of a start symbol and a length of a time domain resource), RV (i.e., information of an RV corresponding to the time domain resource), mapingtoslot (i.e., information of a first offset value (m), which is used to determine a slot in which the time domain resource is located).

Other tables may be configured in a similar manner, and the present application will not be described in detail.

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

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

In case 1, the method for determining the time domain resource of one or more transmission occasions by the terminal or the network device 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, the first offset value of the corresponding kth time domain resource contained in the table item indicated by the second indication information and the second offset value contained in the table item indicated by the second indication information, wherein k is an integer greater than 0.

In this case, the above 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 for scheduling the PUSCH, the DCI carries second indication information, and the index of a time slot where the DCI is positioned is n. For the type2 uplink unlicensed transmission, DCI for activating the type2 uplink unlicensed transmission may also be understood as DCI for scheduling PUSCH.

Illustratively, the index of the time slot in which the time domain resource of the kth transmission occasion of the one or more transmission occasions is located is:wherein u is _PUSCH To characterize parameters of sub-carrier spacing of PUSCH, u _PDCCH In order to characterize the parameters 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.

Exemplary, assume that the slot in which DCI is located is slot #n, u _PUSCH ＝u _PDCCH The table entry indicated by the second indication information is the table entry shown in table 7 (at this time, K ₂ =0). Then referring to fig. 5, the terminal may determine 3 transmission occasions, where the first transmission occasion is located on symbol #12 to symbol #13 of slot # n, i.e. slot # n+0+0, and the RV used is RV2. The second transmission occasion is located on symbols #2 to #6 of slot # (n+0+1) i.e. slot # (n+1), and RV is RV0. The third transmission occasion is located on symbols #9 to #11 of slot # (n+0+1) i.e. slot # (n+1), and RV is RV3.

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

In case 2, the method for determining the time domain resource of one or more transmission occasions by the terminal or the network device 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 an entry indicated by the second indication information and a second offset value contained in the entry indicated by the second indication information, wherein k is an integer greater than 0.

In this case, the above method may further include: the network device transmits the PDCCH to the terminal. Correspondingly, the terminal receives the PDCCH from the network equipment, the PDCCH carries DCI for scheduling the PDSCH, the DCI carries second indication information, and the index of a time slot where the DCI is positioned is n. For the downlink SPS transmission, DCI for activating the downlink SPS transmission may also be understood as DCI for scheduling PDSCH.

Illustratively, the index of the time slot in which the time domain resource of the kth transmission occasion of the one or more transmission occasions is located is:wherein u is _PDSCH To characterize parameters of subcarrier spacing of PDSCH, u _PDCCH In order to characterize the parameters 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.

Exemplary, assume that the slot in which DCI is located is slot #n, u _PDSCH ＝u _PDCCH The table entry indicated by the second indication information is the table entry shown in table 8 (at this time, K ₀ =0). Then referring to fig. 5, the terminal may determine 3 transmission occasions, where the first transmission occasion is located on symbol #12 to symbol #13 of slot # n, i.e. slot # n+0+0, and the RV used is RV2. The second transmission occasion is located on symbols #2 to #6 of slot # (n+0+1) i.e. slot # (n+1), and RV is RV0. The third transmission occasion is located on symbols #9 to #11 of slot # (n+0+1) i.e. slot # (n+1), and RV is RV3.

Case 3, type1 uplink unlicensed transmission

In case 3, the time slot in which the 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 of the corresponding kth time domain resource contained in the 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 above method further includes: the network device sends configuration information of the type1 uplink unlicensed transmission to the terminal. Correspondingly, the terminal receives the configuration information of the uplink unlicensed transmission of the type1 from the network device. The configuration information includes configuration information of the second indication information and the third offset value.

Illustratively, the time slot in which the kth transmission occasion of the one or more transmission occasions is located is: the third offset value+the first offset value of the kth time domain resource contained in the entry indicated by the second indication information, k being an integer greater than 0.

For example, assume that the third offset value is n, and 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 occasions, where the first transmission occasion is located on symbols #12 to #13 of the slot # (n+0) instant #n, and the RV used is RV2. The second transmission opportunity is on symbols #2 through #6 of slot # (n+1), with RV being RV0. The third transmission occasion is located on symbol #9 to symbol #11 of slot # (n+1), and RV used is RV3.

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

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

Optionally, the DCI for scheduling PUSCH transmission or PDSCH transmission does not include a redundancy version indication field, but includes a number of repeated transmissions 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 redundancy version indication field or the retransmission number indication field in the DCI indicates that the value indicated by the redundancy version indication field is X (an integer greater than 1). And if the one or more transmission occasions are K transmission occasions positioned on Y time slots, the terminal determines that the maximum number of time domain resources for repeated transmission is X X K or the maximum number of repeated transmission is X X K, and determines that the maximum number of time slots used for repeated transmission is X X Y. The K transmission opportunities over the Y slots may be determined according to an entry in the time domain resource allocation table, and 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 Y time slots from the X1X y+1 time slot to the (X1+1) X Y time slot (Y time slots altogether) are identical to the positions of the K transmission opportunities determined by the terminal in the 1 st time slot to the Y time slot (Y time slots altogether). Wherein X1 is more than or equal to 1 and X-1 is more than or equal to 1.

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

Compared with the prior art, the method and the device for configuring the repeated transmission times through the high-layer signaling can realize dynamic indication of the repeated transmission times. On the 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, so that the DCI signaling overhead is not increased.

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

In another possible implementation, the DCI for scheduling PUSCH transmission or PDSCH transmission may not include the retransmission number indication field, or the existing retransmission number indication field in the DCI is used for other indication purposes, where the retransmission number is specifically the number of time domain resources indicated by an 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 an example of the time domain resource allocation table, when the terminal device determines the time domain resource, the table entry with the index of "1" in table 6 is used, and the number of repeated transmission times is specifically the number of value combinations of S and L in the table entry with the index of "1", that is, "3". It should be noted that the number of the combination of the values of S and L in different entries in the time domain resource allocation table may be the same or different, which is not limited by the embodiment of the present application.

When the preset condition is satisfied, the terminal uses the original redundancy version indication field in the received DCI as a determination of 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, 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.

The table entry indicated by the condition 2 and 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 the plurality of time domain resources for repeated transmission of the data.

The method comprises the following steps that 3, a terminal receives indication information issued by network equipment through RRC signaling or MAC CE signaling or DCI, wherein the indication information is used for indicating that a redundancy version indication domain is used for determining the maximum number of time domain resources for repeated transmission or the maximum number of repeated transmission or the maximum time slot number for repeated transmission; alternatively, the indication information is used to indicate that the original redundancy version indicating field does not exist but the above-mentioned retransmission number indicating field exists, or to indicate that the redundancy version indicating field is replaced with the retransmission number indicating field.

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

Condition 5, the terminal determines a DCI format for scheduling PUSCH or PDSCH to be a specific format.

Condition 6, the terminal is to receive a PDCCH on a specific type of search space, where the PDCCH carries DCI for scheduling PUSCH or PDSCH transmissions. The embodiment of the application also provides a method for determining transmission resources, as shown in fig. 7, which comprises the following steps:

700. the terminal determines the time domain resource allocation table used.

The specific implementation of step 700 is described above with reference to step 400.

The time domain resource allocation table in this embodiment differs 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 for determining a time slot in which the time domain resource of a plurality of transmission occasions is located, but does not include information for indicating RV.

In the case where the plurality of time domain resource allocation tables comprises a network device configured time domain resource allocation table, optionally, the method further comprises: (11) the network device transmitting the configuration information to the terminal. Accordingly, the terminal receives configuration information from the network device. The configuration information is used to configure the time domain resource allocation table. Other descriptions of this configuration information may be found above and are not repeated here.

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

The third indication information is used for indicating one table 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 transmitting one or more transmission occasions of 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 resource for transmitting one or more transmission occasions of the PUSCH or the PDSCH according to the third indication information and the time domain resource allocation table.

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

In type1 uplink unlicensed transmission, the value of timeDomainOffset is currently sent through RRC signaling so that the terminal determines the 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 slot in which the plurality of time domain resources are located. At this time, the network device needs to send values of a plurality of timeDomainOffset through RRC signaling, so that the terminal determines a time slot in which a plurality of time domain resources for repeated transmission are located. However, even if the terminal knows the values of the plurality of timeDomainOffset, it is also required to know the correspondence between the values of the plurality of timeDomainOffset and the plurality of time domain resources, so the implementation process is complex. The method provided by the embodiment of the application configures a plurality of first offset values in the table items in the time domain resource allocation table to determine the time slots of the time domain resources of a plurality of transmission occasions, so that the terminal can rapidly determine the time slots of the time domain resources and the implementation complexity of the terminal is reduced.

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

Mode (1),

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

Mode (2),

The following gives an example of configuring PUSCH time domain resource allocation tables for terminals by a network device through higher layer signaling (e.g., RRC signaling):

information 1,

Information 2,

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

Information 3,

Information 4,

Information 4 is used to configure information contained in one time domain resource for repeated transmission in one entry. Specifically, timedomainresource allocation period refers to a time domain resource for repeated transmission in an entry. The time domain resource includes: mapingtype (i.e., information of a mapping type of PUSCH), startSymbolAndLength (i.e., information of a start symbol and a length of a time domain resource), mapingtoslot (i.e., information of a first offset value (m) used to determine a slot in which the time domain resource is located).

In case 1, the method for determining the time domain resource of one or more transmission occasions by the terminal or the network device 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, the first offset value of the corresponding kth time domain resource contained in the table item indicated by the third indication information and the second offset value contained in the table item indicated by the third indication information, wherein k is an integer greater than 0.

In this case, the above 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 for scheduling the PUSCH, the DCI carries third indication information, and the index of a time slot where the DCI is positioned is n.

Illustratively, the index of the time slot in which the time domain resource of the kth transmission occasion of the one or more transmission occasions is located is: Wherein u is _PUSCH To characterize parameters of sub-carrier spacing of PUSCH, u _PDCCH In order to characterize the parameters 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.

In case 2, the method for determining the time domain resource of one or more transmission occasions by the terminal or the network device 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, the first offset value of the corresponding kth time domain resource contained in the table item indicated by the third indication information and the second offset value contained in the table item indicated by the third indication information, wherein k is an integer greater than 0.

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

Illustratively, the index of the time slot in which the time domain resource of the kth transmission occasion of the one or more transmission occasions is located is: Wherein u is _PDSCH To characterize parameters of subcarrier spacing of PDSCH, u _PDCCH In 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 third indication information, and C2 is a second offset value contained in the entry indicated by the third indication information.

Case 3, type1 uplink unlicensed transmission

In case 3, the time slot in which the 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 of the corresponding kth time domain resource contained 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 above method further includes: the network device sends configuration information of the type1 uplink unlicensed transmission to the terminal. Correspondingly, the terminal receives the configuration information of the uplink unlicensed transmission of the type1 from the network device. The configuration information includes third indication information and configuration information of a third offset value.

Illustratively, the time slot in which the kth transmission occasion of the one or more transmission occasions is located is: the third offset value+the first offset value of the kth time domain resource contained in the entry indicated by the third indication information, k being an integer greater than 0. Other descriptions of modes (1) and (2) can be found above, and are not repeated here.

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

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

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

The embodiment of the application also provides a method for determining the transmission resource, which comprises the following steps:

The terminal receives DCI from network equipment, wherein the DCI is used for dynamically scheduling PUSCH transmission or PDSCH transmission, or activating Type2 uplink unlicensed 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 time domain resources for PUSCH transmission or PDSCH transmission according to the information contained in the determined table entry. In the present application, both dynamically scheduled PUSCH transmission and Type2 uplink grant-free transmission are referred to as PUSCH transmission, and both PDSCH transmission and SPS-based downlink transmission are referred to as PDSCH transmission.

There may be a plurality of time domain resource allocation tables 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 network device configured time domain resource allocation table. When the plurality of time domain resource allocation tables are configured by the network device, the configuration method may be the configuration method mentioned in the foregoing embodiment, which is not described herein.

Optionally, each time domain resource allocation table is associated with one repeat transmission time, and the repeat transmission 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 retransmissions, but different entries contain the same information of the number of retransmissions.

In another embodiment, the time domain resource allocation table does not include information of the number of repeated transmissions, but rather the table is specified outside the table to be associated with one repeated transmission number. In this embodiment, since only one retransmission number is associated with one time domain resource allocation table, different entries are associated with the same retransmission number for the same time domain resource allocation table, and when the retransmission number is needed, the terminal may determine, according to the retransmission number associated with the time domain resource allocation table used for determining the time domain resource, for example, the retransmission number associated with the time domain resource allocation table is directly used.

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

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 an RV with which the one or more time domain resources are associated. It is to be appreciated that the entries of the time domain resource allocation table may also include other types of information, such as PUSCH mapping types, as the application is not limited. In an example, the time domain resource allocation table may be in the form of tables 6-8, or a column may be added to the form of table 2 to indicate RV information associated with each entry.

The terminal receives DCI from the network device, wherein the DCI includes a time domain resource allocation (time domain allocation) field, and the time domain resource allocation field may be used to determine a time domain resource of a PUSCH transmission or a time domain resource of a PDSCH transmission, and in particular, the time domain resource allocation field includes a bit for indicating an 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, the terminal receives DCI for activating the SPS-based downlink transmission, and determines time domain resources for SPS-based downlink transmission according to the time domain resource allocation domain determination in the DCI

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

Example 1

In this embodiment, the terminal determines a time domain resource allocation table for PUSCH transmission or PDSCH transmission from the above-mentioned 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 formats for scheduling PUSCH transmission (e.g., DCI format 0_0 and DCI format 0_1) and DCI formats for scheduling PDSCH transmission (e.g., DCI format 1_0 and DCI format 1_1), respectively, but redundancy version indication fields in these formats are no longer indicative of redundancy versions but are used to indicate a time domain resource allocation table.

In an embodiment, a portion of bits in the redundancy version indication field are 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, according to one bit in the RV indication field (for example, in the existing DCI format, the RV indication field occupies two bits), for example, when the bit takes a value of 0, it indicates that the table used 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 bit in the RV indication field, for example, the first bit may be the second bit.

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

Optionally, when the preset condition is met, the terminal determines a 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 conditions include 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, wherein 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: the RNTI of the CRC of the PDCCH carrying the DCI is scrambled as 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 to be understood that the preset condition may be other conditions, and as long as the condition is satisfied, the terminal interprets the function or meaning of the corresponding field in the DCI according to the method provided by the implementation of the present invention.

Example two

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

Alternatively, only if the above preset condition (e.g., any one of the above conditions a to D) is satisfied, the terminal considers 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 portion 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 table to be used according to the bit located at the highest position in the time domain resource allocation domain, for example, when the value of the bit is 0, the terminal indicates table a, and when the value is 1, the terminal indicates table 2. 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 according to the 2 bits located at the highest position in the time domain resource allocation domain, and for example, when the values of the 2 bits are 00, 01, 10, 11, respectively, the terminal indicates the table a, the table B, the table C, and the table D, respectively.

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

And determining an 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 entry. In an embodiment, the terminal determines an entry in the determined time domain resource allocation table according to a predetermined portion of bits in the time domain resource allocation domain, for example, when determining a required time domain resource allocation table according to the method provided in the third embodiment, remaining bits in the time domain resource allocation domain (i.e., bits not used to indicate the time domain resource allocation table) are used to indicate an entry in the determined time domain resource allocation table. For example, the time domain resource allocation field in DCI occupies 6 bits, and one value of two bits located at a high level is used to indicate one time domain resource allocation table of the plurality of time domain resource allocation tables, and one value of four bits located at a low level is used to indicate one entry of the time domain resource allocation table.

Optionally, the terminal determines the number of repeated transmissions 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 repeated transmissions for PUSCH transmission, or receive the PDSCH according to the determined time domain resource and the number of repeated transmissions for PDSCH transmission. Optionally, the terminal may further determine a time domain resource for PUSCH transmission or PDSCH transmission according to the determined number of repeated transmissions and the determined entry. 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 of the present application, which are not described herein.

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 exist and correspond to different repeated transmission times, the time domain resource allocation table used by the indication domain of the time domain resource allocation table which is replaced by the RV indication domain is indicated by the RV indication domain, which is equivalent to the repeated transmission times of the PUSCH or the PDSCH indicated by the RV indication domain, namely, 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 can be used for indicating other information, so that dynamic indication of other information can be realized, and signaling overhead can be saved.

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

There is one time domain resource allocation table in the terminal, and the one 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 network device configured time domain resource allocation table. When the one time domain resource allocation table is configured by the network device, the network device may directly configure the content of the one time domain source allocation table, and the configuration method may be the configuration method mentioned in the foregoing embodiment, 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 an RV with which the one or more time domain resources are associated. In one embodiment, each entry contains information for RV (index of RV or RV sequence or RV number). In another embodiment, a portion of the entries of the time domain resource allocation table contain information of the RV and none of the remaining entries contain information of the RV.

It is to be appreciated that the entries of the time domain resource allocation table may also include other types of information, such as PUSCH mapping types, as the application is not limited. In an example, the time domain resource allocation table may be in the form of tables 6-8, or a column of RV information associated with each entry may be added to the form of table 2, or some entries in the form of table 2 may be added with information indicating RV and other entries may not include information indicating RV.

In an embodiment, the terminal determines an entry in the used time domain resource allocation table according to a part of bits 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 one bit in the RV indication domain and n+1 bits in the time domain resource allocation domain, where N is the number of bits contained in the time domain resource allocation domain, and N is an integer with a value greater than or equal to 1. The value of n+1 bits indicates an entry in the time domain resource allocation table. For example, when n=4, the RV indicates that one bit in the domain and 4 bits in the time domain resource allocation domain form 5 bits, where the bit in the RV indicates that the bit in the domain is located in the most significant bit (Most Significant Bit, MSB) of the 5 bits, 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 indication is the 17 th entry in the time domain resource allocation table. Optionally, when a preset condition (any one of the conditions a to D described above) is satisfied, the terminal determines an entry in the used time domain resource allocation table according to one bit in the RV indication domain and n+1 bits in the N bits in the time domain resource allocation domain.

In another implementation, the terminal determines the 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 the table entry in the table to be used according to all bits in the RV indication domain and n+2 bits in the time domain resource allocation domain, where N is the number of bits contained in the time domain resource allocation domain and N is an integer with a value greater than or equal to 1. One value of the n+2 bits indicates a particular entry in the table. For example, when n=4, the total bits in the RV indicating field and the 4 bits in the time domain resource allocation field form 6 bits, where 2 bits in the RV indicating field are located in the first two most significant bits (Most Significant Bit, MSB) of the 6 bits, when the value of the 6 bits is 000000, the first entry in the table is indicated, and when the value of the 6 bits is 100000, the 33 th entry in the table is indicated. Optionally, when a preset condition (any one of the conditions a to D described above) is satisfied, the terminal determines an entry in the used time domain resource allocation table according to all bits in the RV indication domain and N bits in the time domain for n+2 bits.

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

In this embodiment, the RV used for PUSCH or PDSCH transmission is determined by an entry in the table, so that the RV indication field in the DCI is not required to be used to indicate the RV again, but may be used to indicate an entry in the used time domain resource allocation table, so that on the premise of not increasing DCI overhead, more time domain resource allocation possibilities are supported, and time domain resource allocation is more flexible. The scheme of the embodiment of the application is mainly introduced from the interaction angle among the network elements. It will be appreciated that each network element, e.g. network device and terminal, in order to implement the above-mentioned functions, comprises at least one of a corresponding hardware structure and software modules for performing each function. Those of skill in the art will 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 implemented as hardware or computer software driven 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.

The embodiment of the application can divide the functional units of the network equipment and the terminal according to the method example, for example, each functional unit can be divided corresponding to each function, and two or more functions can be integrated in one processing unit. The integrated units may be implemented in hardware or in software functional units. It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice.

In case of integrated units, fig. 8 shows a schematic diagram of one possible configuration of the communication device (denoted as communication device 80) involved in the above-described embodiment, which communication device 80 comprises a processing unit 801 and a communication unit 802, and may further comprise a storage unit 803. The structural diagram shown in fig. 8 may be used to illustrate the structures of the network devices and terminals involved in the above-described embodiments.

While the schematic structural diagram shown in fig. 8 is used to illustrate the structure of the terminal according to the above embodiment, the processing unit 801 is used to control and manage the actions of the terminal, for example, the processing unit 801 is used to support the terminal to perform 400, 401, and 403 in fig. 4, 800, 801, and 803 in fig. 8, and/or actions performed by the terminal in other processes described in the embodiments of the present application. The processing unit 801 may communicate with other network entities, for example with the network device shown in fig. 4, through a 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 a time domain resource allocation table, and an entry in the time domain resource allocation table according to the received DCI; and determining 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 structural diagram shown in fig. 8 is used to illustrate the structure of the terminal according to the above embodiment, the communication device 80 may be the terminal or a chip in the terminal.

While the schematic structural diagram shown in fig. 8 is used to illustrate the structure of the network device according to the above 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 perform 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or actions performed by the network device in other processes described in the embodiments of the present application. The processing unit 801 may communicate with other network entities, for example with the terminal shown in fig. 4, through a 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 for 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 structural diagram shown in fig. 8 is used to illustrate the structure of the network device according to the above embodiment, the communication apparatus 80 may be the network device or a chip in the 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 terminal or a chip in a network apparatus, the processing unit 801 may be a processor or a controller, and the communication unit 802 may be an input/output interface, pins or circuits, etc. The storage 803 may be a storage unit (e.g., a register, a cache, etc.) in the chip, or may be a storage unit (e.g., a read-only memory, a random access memory, etc.) located outside the chip in a terminal or a network device.

Wherein the communication unit may also be referred to as transceiver unit. The antenna and the control circuit having the transmitting and receiving function in the communication device 80 can be regarded as the communication unit 802 of the communication device 80, and the processor having the processing function can be regarded as the processing unit 801 of the communication device 80. Alternatively, the means for implementing the receiving function in the communication unit 802 may be regarded as a receiving unit, where the receiving unit is configured to perform the step of receiving in the embodiment of the present application, and the receiving unit may be a receiver, a receiving circuit, or the like. The means for implementing the transmission function in the communication unit 802 may be regarded as a transmission unit, which is used to perform 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 units of fig. 8 may be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as stand-alone products. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in the embodiments of the present application. The storage medium storing the computer software product includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The units in fig. 8 may also be referred to as modules, e.g., the processing units may be referred to as processing modules.

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

The processor 901 may be a general purpose central processing unit (central processing unit) CPU, microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application. Processor 901 may also include multiple CPUs, and 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 for processing data (e.g., computer program instructions).

The memory 902 may be a ROM or other type of static storage device, a RAM or other type of dynamic storage device that can store static information and instructions, or that can store information and instructions, or that can be an electrically erasable programmable read-only memory (EEPROM), a CD-ROM or other optical disk storage, a compact disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, 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, as embodiments of the application are not limited in this respect. The memory 902 may be provided separately or may be integrated with the processor 901. Wherein the memory 902 may contain computer program code. The processor 901 is configured to execute computer program codes stored in the memory 902, thereby implementing the method provided by the embodiment of the present application.

In a first possible implementation, see fig. 9, the communication device 90 further comprises a transceiver 903. The processor 901, the memory 902 and the transceiver 903 are connected by a bus. The transceiver 903 is used to communicate with other devices or communication networks. Alternatively, the transceiver 903 may include a transmitter and a receiver. The means for implementing the receiving function in the transceiver 903 may be regarded as a receiver for performing the steps of receiving in an embodiment 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 embodiment of the present application.

Based on a first possible implementation, the architecture diagram shown in fig. 9 may be used to illustrate the architecture of the network device or terminal involved in the above-described embodiments.

While the schematic structural diagram shown in fig. 9 is used to illustrate the structure of the terminal according to the above embodiment, the processor 901 is used to control and manage the actions of the terminal, for example, the processor 901 is used to support the terminal to perform 400, 401 and 403 in fig. 4, 800, 801 and 803 in fig. 8, and/or actions performed by the terminal in other processes described in the embodiments of the present application. The processor 901 may communicate with other network entities, such as with the network device shown in fig. 4, via the transceiver 903. The memory 902 is used for storing program codes and data of the terminal.

While the schematic structural diagram shown in fig. 9 is used to illustrate the structure of the network device involved in the above embodiment, the processor 901 is used to control and manage the actions of the network device, for example, the processor 901 is used to support the network device to perform 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or actions performed by the network device in other processes described in the embodiments of the present application. The processor 901 may communicate with other network entities, for example, 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 device.

In a second possible implementation, the processor 901 includes logic circuitry and at least one of an input interface and an output interface. Wherein the output interface is for performing the act of transmitting in the respective method and the input interface is for performing the act of receiving in the respective method.

Based on a second possible implementation, referring to fig. 10, the structural diagram shown in fig. 10 may be used to illustrate the structure of the network device or the terminal involved in the above embodiment.

While the schematic structural diagram shown in fig. 10 is used to illustrate the structure of the terminal according to the above embodiment, the processor 901 is used to control and manage the actions of the terminal, for example, the processor 901 is used to support the terminal to perform 400, 401 and 403 in fig. 4, 800, 801 and 803 in fig. 8, and/or actions performed by the terminal in other processes described in the embodiments of the present application. The processor 901 may communicate with other network entities, such as with the network device shown in fig. 4, through at least one of an input interface and an output interface. The memory 902 is used for storing program codes and data of the terminal.

While the schematic structural diagram shown in fig. 10 is used to illustrate the structure of the network device involved in the above embodiment, the processor 901 is used to control and manage the actions of the network device, for example, the processor 901 is used to support the network device to perform 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or actions performed by the network device in other processes described in the embodiments of the present application. The processor 901 may communicate with other network entities through at least one of an input interface and an output interface, for example, with the terminal shown in fig. 4. The memory 902 is used to store program codes and data for the network device.

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

Fig. 11 is a schematic 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 used for processing communication protocols and communication data, controlling the whole terminal, executing software programs, processing data of the software programs, for example, for controlling the terminal to execute 400, 401 and 403 in fig. 4, 800, 801 and 803 in fig. 8, and/or actions executed by the terminal in other processes described in the embodiments of the present application. The memory is mainly used for storing software programs and data. The control circuit (may also be referred to as a radio frequency circuit) is mainly used for converting a baseband signal and a radio frequency signal and processing the radio frequency signal. The control circuit together with the antenna, which may also be called a transceiver, is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used for receiving data input by a user and outputting data to the user.

When the terminal is started, the processor can read the software program in the memory, interpret and execute the instructions of the software program, and process the data of the software program. When data is required to be transmitted through the antenna, the processor carries out baseband processing on the data to be transmitted and then outputs a baseband signal to a control circuit in the control circuit, and the control circuit carries out radio frequency processing on the baseband signal and then transmits the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal, the control circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.

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

As an alternative implementation manner, the processor may include a baseband processor, which is mainly used to process the communication protocol and the communication data, and a central processor, which is mainly used to control the whole terminal, execute a software program, and process the data of the software program. The processor in fig. 11 integrates the functions of a baseband processor and a central processing unit, and those skilled in the art will appreciate that the baseband processor and the central processing unit may be separate processors, interconnected by bus technology, etc. Those skilled in the art will appreciate that a terminal may include multiple baseband processors to accommodate different network formats, and that a terminal may include multiple central processors to enhance its processing capabilities, with various components of the terminal being connectable via various buses. The baseband processor may also be referred to as a baseband processing circuit or 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 a memory in the form of a software program, which is executed by the processor to realize the baseband processing function.

Fig. 12 is a schematic hardware configuration of the network device 120. The network device 120 may include one or more radio frequency units, such as a remote radio frequency unit (remote radio unit, RRU) 1201 and one or more baseband units (BBU), which may also be referred to as Digital Units (DUs), 1202.

The RRU1201 may be referred to as a transceiver unit, transceiver circuitry, or transceiver, etc., which may include at least one antenna 1211 and a radio frequency unit 1212. The RRU1201 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals. The RRU1201 and BBU1202 may be physically located together or physically separate, e.g., 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 configured to perform baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and so on.

In one embodiment, the BBU1202 may be formed by one or more single boards, where the multiple single boards may support a single access indicated radio access network (e.g., an LTE network), or may support different access schemes of radio access networks (e.g., an LTE network, a 5G network, or other networks). The BBU1202 further comprises a memory 1221 and a processor 1222, wherein the memory 1221 is used for storing necessary instructions and data. The processor 1222 is configured to control the network device to perform the necessary actions. The memory 1221 and processor 1222 may service one or more boards. That is, the memory and the processor may be separately provided on each board. It is also possible that multiple boards share the same memory and processor. In addition, each single board can be provided with necessary circuits.

It should be appreciated that the network device 120 shown in fig. 12 is capable of performing 401 and 402 in fig. 4, 801 and 802 in fig. 8, and/or actions performed by the network device in other processes described in embodiments of the present application. The operations, functions, or both of the respective modules in the network device 120 are respectively configured to implement the respective flows in the above-described method embodiments. Reference is specifically made to the description of the above method embodiments, and detailed descriptions are omitted here as appropriate to avoid redundancy.

In implementation, each step in the method provided in the present embodiment may be implemented by an integrated logic circuit of hardware in a processor or an instruction in a software form. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. Other descriptions of the processor in fig. 11 and 12 may be referred to the description related to the processor in fig. 9 and 10, and will not be repeated.

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

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

The embodiment of the application also provides a communication system, which comprises: the network equipment and the terminal.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it 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. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, simply DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means from one website, computer, server, or data center. Computer readable storage media can be any available media that can be accessed by a computer or data storage devices including one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Although the application is described herein 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 study of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the "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 application has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the present application as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the application. It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A method of determining transmission resources, comprising:

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

and the terminal determines time domain resources and RV (RV) for transmitting one or more transmission occasions of a Physical Uplink Shared Channel (PUSCH) or a Physical Downlink Shared Channel (PDSCH) according to the indication information and the time domain resource allocation table.

2. The method according to claim 1, wherein the method further comprises:

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 according to 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, the plurality of first offset values being used to determine a time slot in which a time domain resource of the plurality of transmission occasions is 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) for scheduling the PUSCH, the DCI carries the indication information, and the index of a time slot where the DCI is positioned is n;

correspondingly, the terminal determines the time domain resource of one or more transmission occasions for transmitting the PUSCH according to the indication information and the time domain resource allocation table, and the method comprises the following steps:

the terminal determines a time slot in which 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 of the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in the entry indicated by the indication information, where k is an integer greater than 0.

5. The method of claim 4, wherein the index of the time slot in which the time domain resource of the kth one of the one or more transmission occasions is located is:wherein u is _PUSCH To characterize the parameters of the sub-carrier spacing of the PUSCH, u _PDCCH In 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.

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, wherein the PDCCH carries DCI for scheduling the PDSCH, the DCI carries the indication information, and the index of a time slot where the DCI is positioned is n;

correspondingly, the terminal determines the time domain resource of one or more transmission occasions for transmitting the PDSCH according to the indication information and the time domain resource allocation table, and the method comprises the following steps:

the terminal determines a time slot in which 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 PDSCH, the subcarrier interval of the PDCCH, the n, a first offset value of the kth time domain resource contained in an entry indicated by the indication information, and a second offset value contained in the entry indicated by the indication information, where k is an integer greater than 0.

7. The method of claim 6, wherein the index of the time slot in which the time domain resource of the kth one of the one or more transmission occasions is located is: Wherein u is _PDSCH To characterize the parameters of the subcarrier spacing of the PDSCH, u _PDCCH In order to characterize the parameters of the subcarrier spacing of the PDCCH, C1 is the corresponding kth time contained in the table entry indicated by the indication informationAnd C2 is a second offset value contained in the table item indicated by the indication information.

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

9. A method according to claim 3, characterized in that the method further comprises:

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

10. The method of claim 1, wherein at least a first one of the plurality of time domain resources corresponds to an RV with an index of 0, wherein the first time domain resource is the time domain resource of the plurality of time domain resources that contains the largest number of symbols.

11. The method of claim 10, wherein the value of the RV index corresponding to each of the at least one first time domain resource is cyclic 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 a plurality of time domain resources and information used to indicate one or more redundancy versions RV;

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

13. The apparatus of claim 12, wherein the device comprises a plurality of sensors,

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 according to 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, the plurality of first offset values being 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 where the DCI is located is n;

the processing unit is specifically configured to: and determining a time slot in which 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 an entry indicated by the indication information and a second offset value contained in the 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 time slot in which a time domain resource of a kth transmission occasion of the one or more transmission occasions is located is:wherein u is _PUSCH To characterize the parameters of the sub-carrier spacing of the PUSCH, u _PDCCH In 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.

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 slot where the DCI is located is n;

the processing unit is specifically configured to: and determining a time slot in which 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 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 the 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 time slot in which a time domain resource of a kth transmission occasion of the one or more transmission occasions is located is:wherein u is _PDSCH To characterize the parameters of the subcarrier spacing of the PDSCH, u _PDCCH In 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.

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

20. The apparatus of claim 14, wherein the device comprises a plurality of sensors,

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

21. The apparatus of claim 12, wherein at least one first time domain resource of the plurality of time domain resources corresponds to an RV with an index of 0, wherein the first time domain resource is the time domain resource of the plurality of time domain resources that contains the largest number of symbols.

22. The apparatus of claim 21, wherein the value of the index of RV corresponding to each of the at least one first time domain resource is cycled according to an arrangement of RV indices in RV sequence {0, 2, 3, 1} or {0,3,0,3 }.

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

the processor is connected to a memory for storing computer-executable instructions that the processor executes to cause the apparatus to implement the method of any one of claims 1-11.

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