CN114223165B

CN114223165B - Method and device for determining repeated transmission resources

Info

Publication number: CN114223165B
Application number: CN201980099302.XA
Authority: CN
Inventors: 徐修强; 陈雁; 吕永霞
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-08-16
Filing date: 2019-08-16
Publication date: 2023-09-01
Anticipated expiration: 2039-08-16
Also published as: WO2021030943A1; CN114223165A

Abstract

A method and a device for determining repeated transmission resources are used for solving the problem that a terminal in the prior art cannot determine whether to execute slot-based or Mini-slot-based repeated transmission. The method comprises the following steps: and the terminal equipment determines at least one table item in the time domain resource allocation list, and determines the repeated transmission resource according to the determined table item. Each entry in the time domain resource allocation list is for configuring resources of one of the first type of retransmission and the second type of retransmission.

Description

Method and device for determining repeated transmission resources

Technical Field

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

Background

To improve the transmission reliability of the data packet, the 5G New Radio (NR) Release15 version supports repeated transmission based on time slots (slots-based), i.e. the terminal device may repeatedly send or receive a maximum of K transmissions of one data packet in consecutive K (K > =1) time slots (slots), where each slot is at most once, and the time domain resources for one transmission of the sent or received data packet are identical in the K slots.

To further reduce the data transmission delay, the 5g NR release16 version supports retransmission based on Mini-slots (Mini-based), i.e. the terminal device may repeatedly send the same or different redundancy versions of the same data packet multiple times in one slot.

When the terminal supports the repeated transmission of slot-based and the repeated transmission of Mini-slot-based at the same time, the terminal cannot determine whether to execute the repeated transmission of slot-based or Mini-slot-based only according to the two parameters of the initial symbol and the length indication value (start and length indicator value, SLIV) and the repeated times K.

Disclosure of Invention

The embodiment of the application provides a method and a device for determining repeated transmission resources, which are used for solving the problem that a terminal cannot determine whether to execute slot-based or Mini-slot-based repeated transmission in the prior art.

In a first aspect, a method for determining a retransmission resource according to an embodiment of the present application includes: and the terminal equipment determines at least one table item in the time domain resource allocation list, and determines the repeated transmission resource according to the determined table item. Each entry in the time domain resource allocation list is for configuring resources of one of the first type of retransmission and the second type of retransmission. In the embodiment of the application, the table entry of the time domain resource allocation list can indicate the repeated transmission mode, and when the terminal equipment determines the used table entry, the terminal equipment can execute the repeated transmission according to the repeated transmission mode corresponding to the table entry. Whether it is a dynamically authorized transmission or an unlicensed transmission (also referred to as a configuration authorized transmission (transmission with configured grant)) or a semi-persistent scheduling (semi-persistent scheduling, SPS) transmission, the terminal needs to determine which entry in the time domain resource allocation list is used, and thus the method for determining duplicate transmission resources according to the embodiment of the present application can be applied to various transmission scenarios. In addition, in the embodiment of the present application, the entry of the time domain resource allocation list may indicate the manner of repeated transmission, and may also indicate information such as SLIV, and thus, the repeated transmission manner and the information such as SLIV may be indicated by means of joint coding (joint coding), so that additional signaling overhead may not be required, and thus signaling overhead may be saved.

In one possible design, the entry may include information that may be used to indicate the type of retransmission. In the above design, by adding an item of information to the table entry to indicate the type of retransmission, the terminal device can determine which type of retransmission the table entry is used for configuring according to the information after determining the used table entry, and further can determine the specific structure of the retransmission resource.

In one possible design, the information, when valued at the first value, indicates a time slot based retransmission, i.e., the entry is used to configure the resources of the time slot based retransmission. The information, when valued at the second value, indicates a retransmission based on the mini-slot, i.e. the entry is used to configure the resources of the retransmission based on the mini-slot.

In one possible design, the entry may be used to configure time domain resources for a first type of retransmission when the entry includes information indicating a type of retransmission, and may be used to configure time domain resources for a second type of retransmission when the entry does not include information indicating a type of retransmission. By the above design, the terminal device can determine which type of retransmission is configured by including the information for indicating the type of retransmission in the table entry, and further can determine the specific structure of the retransmission resource.

In one possible design, the entry may be used to configure the time domain resources of the second type of retransmission when the entry includes information indicating the type of retransmission, and may be used to configure the time domain resources of the first type of retransmission when the entry does not include information indicating the type of retransmission. By the above design, the terminal device can determine which type of retransmission is configured by including the information for indicating the type of retransmission in the table entry, and further can determine the specific structure of the retransmission resource.

In one possible design, the terminal device may receive configuration information for the network device to send a time domain resource allocation list. Through the design, the network equipment can configure a time domain resource allocation list for the terminal equipment.

In one possible design, the terminal device may determine the time domain resource allocation list from among a plurality of time domain resource allocation lists before the terminal device determines the at least one entry in the time domain resource allocation list. With the above design, when the terminal device has a plurality of time domain resource allocation lists, the used time domain resource allocation list can be determined from the plurality of time domain resource allocation lists.

In one possible design, the first transmission type may be a time slot based retransmission and the second retransmission type may be a mini time slot based retransmission.

In a second aspect, a method for determining a retransmission resource according to an embodiment of the present application includes: the terminal equipment determines a time domain resource allocation list in a plurality of time domain resource allocation lists, and determines the time domain resource of repeated transmission according to the determined time domain resource allocation list. The plurality of time domain resource allocation lists comprise at least one first type list and at least one second type list, wherein the first type list is used for configuring resources of first type retransmission, and the second type list is used for configuring resources of second type retransmission. In the embodiment of the application, by associating the time domain resource allocation list with the repeated transmission mode, when the terminal equipment determines the used time domain resource allocation list, the terminal equipment can execute the repeated transmission according to the repeated transmission mode corresponding to the time domain resource allocation list. Whether it is a dynamic grant transmission or an unlicensed transmission or a semi-persistent scheduling (SPS) transmission, the terminal needs to determine which time domain resource allocation list to use, and thus the method for determining duplicate transmission resources according to the embodiment of the present application may be applicable to various transmission scenarios. In addition, in the embodiment of the present application, the time domain resource allocation list may indicate information such as SLIV in addition to the repeated transmission manner, and it is seen that the repeated transmission manner and the information such as SLIV are indicated by means of joint coding (joint coding), so that additional signaling overhead may not be required, and thus signaling overhead may be saved.

In one possible design, if the determined time domain resource allocation list is a first type list, the terminal device may determine the time domain resource of the repeated transmission according to the first type repeated transmission. If the determined time domain resource allocation list is the second type list, the terminal device may determine the time domain resource of the repeated transmission according to the second type repeated transmission. By the method, when the terminal equipment determines the time domain resource of repeated transmission, extra signaling overhead is not needed, so that the signaling overhead can be saved.

In one possible design, the plurality of time domain resource allocation lists may be configured by the network device for the terminal device through higher layer signaling.

In one possible design, the plurality of time domain resource allocation lists may be predefined.

In a third aspect, the present application provides an apparatus for determining retransmission resources, where the apparatus may be a terminal device, or may be a chip or a chipset in the terminal device. The apparatus may include a processing unit and a transceiving unit. When the apparatus is a terminal device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the apparatus may further include a memory module, which may be a memory; the storage module is configured to store instructions, and the processing unit executes the instructions stored in the storage module, so that the terminal device performs the corresponding functions in the first aspect or the second aspect. When the apparatus is a chip or a chipset within a communication device, the processing unit may be a processor and the transceiver unit may be an input/output interface, pins or circuitry, etc.; the processing unit executes instructions stored in a memory module, which may be a memory module (e.g. a register, a cache, etc.) within the chip or chipset, or a memory module (e.g. a read only memory, a random access memory, etc.) located outside the chip or chipset within the communication device, to cause the terminal device to perform the corresponding functions in the first aspect, the second aspect, or the third aspect.

In a fourth aspect, an apparatus for determining a retransmission resource is provided, including: a processor, a communication interface, and a memory. The communication interface is used to transfer information, and/or messages, and/or data between the device and other devices. The memory is configured to store computer-executable instructions that, when executed by the apparatus, cause the apparatus to perform the method of determining duplicate transmission resources as described in any one of the first aspect or the second aspect.

In a fifth aspect, an embodiment of the present application provides a computer storage medium storing program instructions that, when executed on a terminal device, cause the terminal device to perform the method of the first aspect and any possible design thereof, or the second aspect or any design thereof.

In a sixth aspect, embodiments of the present application provide a computer program product for causing a communication device to perform the method of the first aspect of embodiments of the present application and any one of its possible designs, or of the second aspect or any one of its designs, when the computer program product is run on the communication device.

In a seventh aspect, embodiments of the present application provide a chip, coupled to a memory, for performing the method of the first aspect of embodiments of the present application and any possible designs thereof, or of the second aspect or any designs thereof.

In addition, the technical effects brought about by the third aspect to the seventh aspect may be referred to the description of the first aspect or the second aspect, and are not repeated here.

It should be noted that "coupled" in the embodiments of the present application means that two components are directly or indirectly combined with each other.

Drawings

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

fig. 2 is a schematic diagram of a time slot based retransmission according to an embodiment of the present application;

fig. 3 is a schematic diagram of a retransmission scheme based on mini time slots according to an embodiment of the present application;

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

fig. 5 is a schematic diagram of a retransmission resource according to an embodiment of the present application;

fig. 6 is a schematic diagram of another retransmission resource according to an embodiment of the present application;

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

Fig. 8 is a schematic structural diagram of an apparatus for determining retransmission resources according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another apparatus for determining retransmission resources according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings.

The method for determining the repeated transmission resources can be applied to various communication systems, for example, an internet of things (internet of things, ioT) system, a narrowband internet of things (narrow band internet of things, NB-IoT) system, a long term evolution (long term evolution, LTE) system, a fifth generation (5G) communication system, a hybrid architecture of LTE and 5G, a new wireless (NR) system of 5G, a new communication system in future communication development, and the like. As long as there is one entity (referred to as a first entity) in the communication system sending configuration information to another entity (referred to as a second entity) and the first entity sending data to the second entity or receiving data sent by the second entity. Correspondingly, the second entity receives the configuration information sent by the first entity, and sends data to the first entity or receives the data sent by the first entity according to the configuration information.

The terminal device in the embodiment of the application is an entity for receiving or transmitting signals at the user side. The terminal device may be a device providing voice and/or data connectivity to a user, e.g., a handheld device having wireless connectivity, an in-vehicle device, etc. The terminal device may also be other processing device connected to the wireless modem. The terminal device may communicate with one or more core networks via a radio access network (radio access network, RAN). The terminal device may also be referred to as a wireless terminal, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile), remote station (remote station), access point (access point), remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), user device (user equipment), or User Equipment (UE), etc. The terminal device may be a mobile terminal, such as a mobile telephone (or "cellular" telephone) and a computer with a mobile terminal, e.g. a portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile device, which exchanges speech and/or data with the radio access network. For example, the terminal device may also be a personal communication services (personal communication service, PCS) phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), or the like. Common terminal devices include, for example: a cell phone, tablet computer, notebook computer, palm computer, mobile internet device (mobile intemet device, MID), wearable device, such as a smart watch, smart bracelet, pedometer, etc., but embodiments of the application are not limited thereto.

The network device according to the embodiment of the present application is an entity on the network side for transmitting and/or receiving signals, and may be used to convert a received air frame and an IP (internet protocol) packet into each other, which is used as a router between the terminal device and the rest of the access network, where the rest of the access network may include an IP network and so on. The network device may also coordinate attribute management for the air interface. For example, the network device may be an evolved base station (evolutional Node B, eNB or e-NodeB) in LTE, a new radio controller (new radio controller, NR controller), a gNode B (gNB) in 5G system, a centralized network element (new radio base station), a remote radio module, a micro base station, a relay, a distributed network element (distributed unit), a receiving point (transmission reception point, TRP) or a transmission point (transmission point, TP), or any other wireless access device, but the embodiment of the present application is not limited thereto. A network device may cover 1 or more cells.

Referring to fig. 1, a communication system according to an embodiment of the present application includes a network device and six terminal devices, taking UE1 to UE6 as an example. In the communication system, UE1 to UE6 may transmit signals to a network device on an uplink, and the network device may receive uplink signals transmitted by UE1 to UE 6. Meanwhile, the network device may send configuration information to UE1-UE 6. In addition, UE4 to UE6 may also form a sub-communication system, where the configuration information sending entity and the receiving entity may both be terminal devices, for example, in an internet of vehicles system, where terminal device 1 sends configuration information to terminal device 2 and receives data sent by terminal device 2; and the terminal device 2 receives the configuration information transmitted from the terminal device 1 and transmits data to the terminal device 1. Fig. 1 is merely a schematic diagram, and the present application is not particularly limited to the type of communication system, and the number, type, etc. of devices included in the communication system.

The embodiment of the application can be used for scenes such as dynamic scheduling transmission, dynamic authorization transmission, semi-persistent scheduling transmission, semi-static scheduling transmission, authorization-free transmission, scheduling-free transmission, dynamic authorization-free transmission, high-level configuration transmission, configuration authorization transmission and the like. The embodiment of the application can be used for uplink transmission scenes and downlink transmission scenes.

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 to the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided in the embodiments of the present application is applicable to similar technical problems.

To improve the transmission reliability of the data packet, release15 version of 5G NR supports slot aggregation (slot aggregation) transmission and slot-based (slot-based) repetition transmission (repetition) of the data packet, where the slot aggregation transmission may be adapted for dynamic scheduling based transmission, i.e. physical downlink shared channel (physical downlink shared channel, PDSCH) transmission or physical uplink shared channel (physical uplink shared channel, PUSCH) transmission is scheduled by a physical downlink control channel (physical downlink control channel, PDCCH), the cyclic redundancy check (cyclic redundancy check, CRC) of which may be scrambled by a cell-radio network temporary identity (cell-radio network temporary identifier, C-RNTI), modulation and coding scheme-cell-radio network temporary identity (modulation and coding scheme C-RNTI, MCS-C-RNTI), etc. The slot-based retransmission may be applicable to uplink dynamic grant-free transmission (UL data transmission without dynamic grant), and may also be referred to as Configured Grant (CG) transmission.

The terminal may determine the number of time slots of the time slot aggregation transmission or the number of slot-based retransmission through a higher layer parameter issued by the base station, for example, the terminal may determine the number of time slots of the downlink time slot aggregation transmission according to a physical downlink shared channel aggregation factor (pdsch-aggregation factor) issued by the base station, determine the number of time slots of the uplink time slot aggregation transmission according to a physical uplink shared channel aggregation factor (pusch-aggregation factor) issued by the base station, and determine the number of uplink slot-based retransmission according to the number of retransmission K (rep-K). Whether slot-based repeat transmission or slot aggregation transmission, the terminal repeatedly transmits (receives or transmits) one data packet K times in consecutive K (K > =1) (K is the aforementioned value determined by pdsch-aggregation factor, or PUSCH-aggregation factor, or repK), where the data packet is transmitted once per slot, and the time domain resources (which may be referred TO as transmission occasions (transmission occasion, TO)) for transmitting the data packet are identical in K slots, for example, as shown in fig. 2, k=4, and the PUSCH transmission resources configured by the terminal for transmitting one data packet (referred TO herein as one PUSCH transmission) are located in symbol 2 TO symbol 5 of the slot for 4 symbols, and the terminal may transmit one PUSCH transmission on symbol 2 TO symbol 5 in each slot of the K slots for 4 symbols.

In order to further reduce the data transmission delay, the 5g NR release16 version supports mini-slot-based (mini-slot-based) aggregate transmission or mini-slot-based retransmission, i.e. the terminal may repeatedly send the same or different redundancy versions of the same data packet in one slot. For example, as shown in fig. 3, when K is 4, the terminal sends the first 3 of 4 TOs of 4 PUSCH transmissions of the same packet, where the first 3 TOs are respectively located in symbols 2-5, 6-9, and 10-13 of slot 1, and the last TO is located in symbols 0-3 of slot 2, and it can be seen that the first 3 TOs of 4 TOs are all located in the same slot.

The 5g NR release15 version only supports slot-based aggregation transmission (or slot-based retransmission), so when the terminal receives a start symbol and a length indication value (start and length indicator value, SLIV) issued by the base station and used for configuring a time domain resource and the number of repetitions K, it defaults TO determine K TOs in K consecutive time slots according TO the slot-based aggregation transmission mode (or slot-based retransmission mode), where only one TO in each time slot, and uses the K TOs TO perform K aggregation transmission or retransmission on the same data packet. But when the terminal supports both slot-based aggregated transmission (or slot-based retransmission) and mini-slot-based aggregated transmission (or mini-slot-based retransmission), for example, the terminal of release16 version of the 5g NR, in this case, the terminal cannot determine whether to perform slot-based aggregated transmission (or slot-based retransmission) or mini-slot-based aggregated transmission (or mini-slot-based retransmission) according to only two parameters, i.e., the slot and the slot indicate that the start symbol index and the symbol length are divided into 2 and 4, and the K is 4, as shown in fig. 2 and 3, or the terminal cannot determine whether to perform slot-based retransmission as shown in fig. 2 or mini-slot-based retransmission as shown in fig. 3.

One possible solution to the above problem is: the base station may explicitly indicate the aggregate transmission (or the retransmission) through radio resource control (radio resource control, RRC) or downlink control information (downlink control information, DCI), for example, through 1 bit in RRC or DCI signaling, when the bit takes 0, may represent the slot-based aggregate transmission (or slot-based retransmission), and when the bit takes 1, may represent the mini-slot-based aggregate transmission (or mini-slot-based retransmission). However, the base station may increase signaling overhead, especially DCI overhead, by explicitly indicating the aggregated transmission (or repeated transmission) through RRC or DCI.

Another possible solution is: the terminal may determine a manner of aggregation transmission (or retransmission) according to a mapping type (mapping type) indicated by the base station, for example, may represent slot-based aggregation transmission (or slot-based retransmission) when the mapping type indicated by the base station is typeA, and typeB represents mini-slot-based aggregation transmission (or mini-slot-based retransmission). However, in this manner, the terminal may impose a limitation on scheduling according to the manner in which the mapping type is determined, for example, slot-based aggregated transmission (or slot-based repeated transmission) cannot be used at the time of mapping type b, and so on.

Yet another possible solution is: the terminal may determine according to the size of the unlicensed resource period P, for example, when P is smaller than K slots, perform mini-slot-based retransmission, or perform slot-based retransmission. However, this approach is only applicable to unlicensed transmissions, and does not use dynamic licensed transmission scenarios.

Yet another possible solution is: the terminal determines, for example, a radio network temporary identity (radio network temporary identifier, RNTI) type, or DCI format (format), or control resource set (control resource set, core) type, search Space (SS), etc. of a transmission PDCCH according to an attribute of the PDCCH for scheduling PUSCH or PDSCH transmission. However, this method is only suitable for a dynamic scheduling scenario, is not suitable for an unlicensed transmission scenario, and also brings limitation to scheduling, for example, when different DCI formats are used to indicate a transmission method, the DCI format used to indicate slot-based slot aggregation transmission cannot be used to schedule a mini-slot-based aggregation transmission method, and also increases complexity of blind detection of PDCCH by a terminal.

Based on this, the embodiment of the application provides a method and a device for determining repeated transmission resources. The method and the device are based on the same technical conception, and because the principle of solving the problems by the method and the device is similar, the implementation of the device and the method can be mutually referred to, and the repeated parts are not repeated.

It should be understood that in embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one (item) below" or the like, refers to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, a and b, a and c, b and c, or a, b and c, wherein a, b and c can be single or multiple.

In addition, it should be understood that in the description of the present application, the words "first," "second," and the like are used merely for distinguishing between the descriptions and not for indicating or implying any relative importance or order.

The method for determining the repeated transmission resource provided by the embodiment of the application is specifically described below with reference to the accompanying drawings.

Embodiment one:

referring to fig. 4, a flowchart of a method for determining a repetition transmission resource according to the present application is provided, where the method may be applied to a terminal device, and may also be applied to a chip or a chipset in the terminal device, and the method is described below by taking application to the terminal device as an example, and includes:

s401, the terminal equipment determines at least one table item in a time domain resource allocation list (or table), wherein each table item in the time domain resource allocation list is used for configuring the resource of one repeated transmission type in the first type repeated transmission and the second type repeated transmission.

In one exemplary illustration, there may be two types of retransmission, one based on a time slot, i.e., one transmission of at most one data packet in one time slot, and the other based on a mini-time slot, i.e., there may be multiple retransmissions of one data packet in one time slot. The embodiment of the application does not limit the relative position of repeated transmission of one data packet in one time slot and the size of time domain resources occupied by repeated transmission each time, for example, repeated transmission of different times can be continuous or discontinuous in time, and the sizes of the time domain resources used by repeated transmission of different times can be the same or different. In the repeated transmission, the time domain resource for transmitting the data packet may be referred TO as TO, and for convenience of description, the time domain resource for one transmission is denoted by one TO.

It should be understood that the retransmission types are only exemplary, and the retransmission types in the embodiments of the present application are not limited to the retransmission types based on time slots and the retransmission types based on mini time slots, and may be indicated by similar methods in the present application if other retransmission types occur in future communication developments. In addition, the embodiment of the present application is not limited to two types of retransmission, and in a specific implementation, there may be more types of retransmission (such as three types, four types, or five types), and three types of retransmission are taken as examples, and each entry in the time domain resource allocation list is used to configure a type of retransmission resource in the first type of retransmission, the second type of retransmission, the third type of retransmission, and so on. It will be appreciated that a slot aggregate transmission is also essentially a type of retransmission.

For descriptive convenience, the first transmission type is a slot-based retransmission and the second retransmission type is a mini-slot-based retransmission.

In a specific implementation, each entry in the time domain resource allocation list may indicate a type of retransmission, and specifically may indicate a manner of retransmission by including information for indicating a type of retransmission, or may indicate a manner of retransmission by including information for indicating a type of retransmission or not. In addition, each entry may also contain information indicating a SLIV. Each entry may also contain one or more of the following information: time domain offset, mappingtype, number of retransmissions K, redundancy version (redundancy version, RV), etc. The information indicating the SLIV may include a start symbol S for determining a start symbol of a TO for a first transmission in the repeated transmission and a length L for determining a number of symbols of the TO in the repeated transmission. The time domain offset K2 may be used to indicate a time domain offset of a time domain resource location of a PUSCH transmission relative to a PDCCH used to schedule the PUSCH transmission. mapping type may be used to indicate the mapping type of PUSCH transmission, such as typeA or typeB, where typeA and typeB differ in that the time domain positions of the preamble (Front-load) DMRS are different, e.g., for type a, the Front-load DMRS is located at the 3 rd OFDM symbol, or at the 3 rd and 4 th OFDM symbols, or at the 1 st OFDM symbol, or at the 1 st and 2 nd OFDM symbols, in each slot, and for typeB, the Front-load DMRS is located at the 1 st OFDM symbol, or at the 1 st and 2 nd OFDM symbols, in each PUSCH. The number of repeated transmissions K is used to indicate the maximum number of repeated transmissions (reception or transmission) of one data packet.

Wherein the time domain resource allocation list may comprise at least one row, e.g. the time domain resource allocation list may comprise 16 rows, each row may be regarded as an entry. The time domain resource allocation list may comprise at least one column, e.g. the time domain resource allocation list may comprise 4 columns, wherein each column may represent one kind of information. For example, a first column may represent a start symbol S, a second column may represent a length L, a third column may represent a mapping type, a fourth column may represent information indicating a repeated transmission manner, and so on.

When the entry indicates the manner of repeating transmission by including information for indicating the type of repeating transmission, a specific indication method may be that the information indicates the repeating transmission based on the time slot when the value of the information is the first value, that is, the entry is used to configure the resource of the repeating transmission based on the time slot. The information, when valued at the second value, indicates a retransmission based on the mini-slot, i.e. the entry is used to configure the resources of the retransmission based on the mini-slot. Illustratively, this information may be referred to as a repeat pattern (repeat pattern), representing a slot-based repeat pattern when repetition scheme is of type1, and representing a mini-slot-based repeat pattern when repetition scheme is of type 2. Alternatively, repetition scheme represents a retransmission scheme based on mini slots when it is type1, and repetition scheme represents a retransmission scheme based on slots when it is type 2. For example, it may be as shown in table 1.

TABLE 1

In one implementation, the subcarrier spacing of PUSCH may be equal to 2 ^μ The value of x 15khz, j may be related to a parameter (μ) for determining the subcarrier spacing of PUSCH, e.g., j may be equal to 1 when μ is 0 or 1 and j may be equal to 2 when μ is 2, as shown in table 2.

TABLE 2

Taking the example of the retransmission scheme based on time slots when repetition scheme is of type1 and the example of the retransmission scheme based on mini time slots when repetition scheme is of type2, table 1 includes entries with indexes 1-3, 8-13, 15 and 16 for configuring time domain resources of the retransmission scheme based on time slots, and entries with indexes 2-7 and 14 for configuring time domain resources of the retransmission scheme based on mini time slots.

When the table entry indicates the manner of repeating transmission by including information for indicating the type of repeating transmission, a specific indication manner may be that when the table entry includes information for indicating the type of repeating transmission, the table entry may be used to configure time domain resources for time slot based repeating transmission, and when the table entry does not include information for indicating the type of repeating transmission, the table entry may be used to configure time domain resources for mini time slot based repeating transmission. Alternatively, the entry may be used to configure time domain resources for a mini-slot based retransmission when the entry includes information indicating a type of retransmission, and may be used to configure time domain resources for a slot based retransmission when the entry does not include information indicating a type of retransmission. When the table entry includes information for indicating the type of retransmission, the value of the information may be arbitrary, which is not particularly limited herein. For example, it may be as shown in table 3.

TABLE 3 Table 3

In one implementation, the subcarrier spacing of PUSCH may be equal to 2 ^μ The value of x 15khz, j may be related to a parameter (μ) for determining the subcarrier spacing of PUSCH, e.g., j may be equal to 1 when μ is 0 or 1 and j may be equal to 2 when μ is 2, as shown in table 2 above.

Taking the example of the retransmission scheme based on time slots when repetition scheme is 1 and the example of the retransmission scheme based on mini time slots when repetition scheme is empty, table 3 has entries with indexes 1, 4-6, 10, 12, 15, 16 for configuring time domain resources based on time slot retransmission, and entries with indexes 2-3, 7-9, 11, 13, 14 for configuring time domain resources based on mini time slot retransmission.

It should be noted that "retransmission" according to the embodiment of the present application may be understood that a terminal device may retransmit (receive or transmit) a data packet K times in a plurality of consecutive time slots, where K is the number of retransmission times, and in practical application, "retransmission" may also be referred to as "aggregate transmission", and, for example, may be referred to as "aggregate transmission" in a transmission scenario such as dynamic scheduling or dynamic grant, and may be referred to as "retransmission" in a transmission scenario such as semi-persistent scheduling, semi-static scheduling, unlicensed, or exempt from scheduling, or exempt from dynamic grant, or higher layer configuration. Of course, in future communication systems, "retransmission" may be named as other, for example, a, and it should be understood that if a may implement the function of "retransmission" in the embodiment of the present application, a may also be considered as "retransmission" in the embodiment of the present application.

In some embodiments, the determining, by the terminal device, at least one entry in the time domain resource allocation list may be implemented by:

the network device may send a time domain resource allocation parameter to the terminal device, the time domain resource allocation parameter being used to indicate at least one entry, e.g. the time domain resource allocation parameter may indicate an index of the entry. The terminal device may determine the used time domain resource allocation table according to the time domain resource allocation parameters issued by the network device. In one exemplary illustration, the time domain resource allocation parameter may be Time domain resource assignment fields in DCI or RRC parameter timedomainalllocation, for example.

In a specific implementation manner, if the terminal device performs transmission based on dynamic scheduling data transmission or based on grant data transmission, or Type 2 uplink dynamic grant free transmission or downlink Semi-persistent scheduling (Semi-Persistent Scheduling, SPS) transmission, the network device may instruct, through DCI (e.g., time domain resource assignment fields in DCI), which entry in the time-domain resource allocation list is used by the terminal device to perform time-domain resource allocation (i.e., determine retransmission resources). If the terminal device performs uplink transmission based on Type 1 uplink dynamic grant, the network device may instruct the terminal device, through RRC signaling (e.g., timeDomainAllocation IE), which entry in the time domain resource allocation list is used for time domain resource allocation (i.e., determine retransmission resources).

S402, the terminal equipment determines the repeated transmission resources according to the determined table entry.

In some embodiments, the terminal device may determine the retransmission mode according TO the table entry, and determine a location of each TO in the retransmission process. Specifically, if the table entry is used TO configure the resources of the timeslot-based retransmission, i.e. the table entry is used TO indicate the timeslot-based retransmission, the terminal device may determine that each timeslot in the plurality of consecutive timeslots includes at most one TO, and positions of different TOs in the respective timeslots are identical, and the number of the plurality of timeslots may be equal TO the number of repeated transmissions. If the table entry is used TO configure the resource of the retransmission based on the mini slot, that is, the table entry is used TO indicate the retransmission based on the mini slot, the terminal device may determine that multiple TOs may be included in one slot.

In one exemplary illustration, when the retransmission scheme is slot-based retransmission, the terminal device may determine each TO according TO a slot in the table entry, where a start symbol of each TO is determined according TO S in the slot, and a number of symbols is determined according TO L in the slot.

When the retransmission scheme is based on mini time slot, the terminal device determines that multiple TOs can be contained in one time slot, the multiple TOs can be continuous or discontinuous in the time domain, and the time-frequency resources of the multiple TOs can be the same or different in size. For example, the terminal device may determine a first TO according TO the SLIV, a start symbol of the first TO is determined according TO S in the SLIV, a number of symbols is determined according TO L in the SLIV, and a start symbol of an n+1 (N > =1) th TO may be a next symbol of the N-th TO. If the number of symbols remaining from the start symbol in the time slot in which the start symbol of the n+1th TO is located is less than L, the n+1th TO may terminate in the last symbol of the time slot, and if the number of symbols remaining in the time slot in which the start symbol of the n+1th TO is located is not less than L, the number of symbols included in the n+1th time domain resource is also L.

For ease of understanding, the time domain resource allocation list shown in table 1 is taken as an example, where when repetition scheme is type1, a time slot-based retransmission scheme is represented, and when repetition scheme is type2, a mini time slot-based retransmission scheme is represented. For type a, the Front-load DMRS is located at the 3 rd OFDM symbol (i.e., symbol 2) in each slot, and for type B, the Front-load DMRS is located at the 1 st OFDM symbol of each PUSCH. As shown in fig. 5, if the terminal device determines that the entry with index 3 is used, the terminal device may determine that the manner of repeating transmission is based on the repeated transmission of the time slot, and the Front-load DMRS is located on symbol 2 of each of K consecutive time slots, where K is the number of repeated transmissions, and it is assumed that K is equal to 4. The first retransmission resource is offset in time domain by j with respect TO the PDCCH for scheduling the retransmission resource, and the 4 TOs for the retransmission are located in 4 symbols from symbol 0 TO symbol 3 of each slot, respectively. Thus, the terminal device may perform one transmission of the data packet on symbol 0 to symbol 3 of each slot, respectively.

As shown in fig. 6, if the terminal device determines that the table entry with index of 5 is used, the terminal device may determine that the retransmission mode is retransmission based on mini-slots, and the Front-load DMRS is located on the first symbol of each PUSCH transmission, where K is the number of repeated transmissions, and it is assumed that K is equal to 4. The time domain offset of the first retransmission resource (or the starting symbol of the first retransmission resource or the time slot or subframe or frame where the first retransmission resource is located) with respect TO the PDCCH (or the starting symbol or the ending symbol of the PDCCH or the time slot or subframe or frame where the PDCCH is located) for scheduling the retransmission resource is j, the first TO for the retransmission is located in the first time slot for 4 symbols 4 TO 7 symbols, the second TO is located in the first time slot for 4 symbols 8 TO 11 symbols, the third TO is located in the first time slot for 2 symbols 12 TO 13 symbols, the fourth TO is located in the second time slot for 0 TO 1 for 2 symbols, and the fifth TO is located in the second time slot for 4 symbols, wherein, due TO the fact that the resources for the retransmission at the time of the third retransmission (i.e., the first time slot for 12 TO 13 and the second time slot for 0 TO 1) span two time slots, the third retransmission is broken by the time slot boundary, and the third TO is located in the third TO the fourth TO. As can be seen in fig. 6, the first three TOs of the 5 TOs are all located in the same time slot. Thus, the terminal device may perform one transmission of the data packet on symbol 4 to symbol 7, symbol 8 to symbol 11, symbol 12 to symbol 13 of the first slot, symbol 0 to symbol 1 of the second slot, and symbol 2 to symbol 5 of the second slot, respectively.

In a specific implementation, before determining at least one entry in the time domain resource allocation list, the terminal device may determine the used time domain resource allocation list from a plurality of time domain resource allocation lists.

In one implementation, the plurality of time domain resource allocation lists may be configured by the network device for the terminal device through higher layer signaling, which may be RRC signaling, for example. That is, the network device may configure one or more time domain resource allocation lists for the terminal through RRC signaling, and the terminal device receives configuration information of the time domain resource allocation list transmitted by the network device. Wherein at least one time domain resource allocation list of the plurality of time domain resource allocation lists conforms to the characteristics of the time domain resource allocation list described in step S401 herein, that is, each entry may configure a resource of one type of repeated transmission of time slot-based repeated transmission and mini-slot-based repeated transmission, and a parameter indicating the type of repeated transmission exists in the entry or the entry is associated with the type of repeated transmission.

Illustratively, the time domain resource allocation list conforming to the characteristics of the time domain resource allocation list described in step S401 herein may be configured by a high-level parameter TimeDomainResourceAllocationList-r16 IE (Information Element), for example, the uplink time domain resource allocation list conforming to the characteristics of the time domain resource allocation list described in step S401 herein may be configured by a high-level parameter PUSCH-TimeDomainResourceAllocationList-r 16. Other time domain resource allocation lists that do not (or do not fully) conform to the characteristics of the time domain resource allocation list described herein in step S401 may be configured by other higher layer parameters, e.g., the uplink time domain resource allocation list in the standard version of 5g NR release15 is configured by the higher layer parameter PUSCH-TimeDomainResourceAllocationList IE.

For example, the network device may configure two uplink time domain resource allocation lists for the terminal device through PUSCH-timedomainresourceAllocationList and PUSCH-timedomainresourceAllocationList-r16, respectively, where the time domain resource allocation list configured through PUSCH-timedomainResourceAllocationList-r16 may conform to the features of the time domain resource allocation list described in step S401 herein.

In one exemplary illustration, the PUSCH-TimeDomainResourceAllocationList-r16 may be specifically as follows:

wherein PUSCH-timedomainresourceAllocation List-r16 is used to configure a time domain resource allocation list that conforms to the characteristics of the time domain resource allocation list described herein in step S401, wherein the configured time domain resource allocation list includes at most 16 entries, PUSCH-timedomainresourceAllocation-r16 is used to configure each entry PUSCH-timedomainresourceAllocation-r16, and in each entry k2 is used to configure a time domain offset of a time domain resource location of a PUSCH transmission relative to a PDCCH used to schedule the PUSCH transmission. mapingtype is used to configure the mapping type of PUSCH transmission, startSymbolAndLength is used to configure the start symbol and length indication value of the time domain resource, and repetition scheme is used to configure the retransmission scheme (or referred to as the retransmission type). It will be appreciated that other types of parameters may also be included in each entry.

In another implementation, the plurality of time domain resource allocation lists may be predefined. The terminal device may use the predefined time domain resource allocation list when the network device does not configure the time domain resource allocation list for the terminal device through higher layer signaling. At least one time domain resource allocation list conforms to the characteristics of the time domain resource allocation list described in step S401 herein, that is, each entry may be configured with resources of one type of retransmission in the time slot-based retransmission and the mini-time slot-based retransmission, and information indicating the type of retransmission in the entry or the entry may be associated with the type of retransmission. For example, the predefined time domain resource list a and the time domain resource list B, where the time domain resource list B may conform to the characteristics of the time domain resource allocation list described in step S401 herein, for example, the entry of the time domain resource list B contains indication information for indicating the repeated transmission mode.

Further, when the network device configures the terminal device with or predefines a plurality of time domain resource allocation lists, the terminal device may determine the used time domain resource allocation list among the plurality of time domain resource allocation lists.

In a possible implementation, the terminal device may determine which time domain resource allocation list to use under the direction of the network device.

In one implementation, the network device may indicate which time domain resource allocation list is used by the terminal device through explicit indication information, where the indication information may be carried in RRC signaling or DCI signaling or MAC CE signaling and sent to the terminal. For example, when two time domain resource allocation lists are configured, the network device may indicate which time domain resource allocation list the terminal device uses through one bit of RRC signaling or DCI signaling or MAC CE signaling. For example, when the bit is valued at 1, the terminal device may be instructed to use the first time domain resource allocation list, and when the bit is valued at 0, the terminal device may be instructed to use the second time domain resource allocation list. Alternatively, the terminal device may be instructed to use the first time domain resource allocation list when the bit is valued at 0, and instruct the terminal device to use the second time domain resource allocation list when the bit is valued at 1.

In another implementation, the network device may also implicitly indicate which list the terminal device uses, e.g. the network device may use the transmission attribute of the PDCCH to indicate which list the terminal device uses, where PDCCH refers to the PDCCH used to transmit DCI, which is used to schedule PUSCH or PDSCH, the transmission attribute may refer to the RNTI type of CRC of the scrambling DCI, or the CORESET type where the PDCCH is located, or the search space type where the PDCCH is located, etc., e.g. different RNTI types, different CORESET types, different search space types may represent different lists.

Alternatively, when the network device configures only one time domain resource allocation list for the terminal device, or predefines one time domain resource allocation list, the terminal device may use the time domain resource allocation list by default.

In the embodiment of the application, the table entry of the time domain resource allocation list can have information indicating the repeated transmission mode or be associated with the repeated transmission mode, and when the terminal equipment determines the used table entry, the terminal equipment can execute the repeated transmission (or determine the time domain resource) according to the repeated transmission mode corresponding to the table entry. Whether it is a dynamically authorized transmission or an unlicensed transmission or a semi-persistent scheduling (SPS) transmission, the terminal needs to determine which entry in the time domain resource allocation list is used, so the method for determining the repeated transmission resources provided by the embodiment of the application can be suitable for various transmission scenarios. In addition, in the embodiment of the present application, the entry of the time domain resource allocation list may indicate the manner of repeated transmission, and may also indicate information such as SLIV, and thus, the repeated transmission manner and the information such as SLIV may be indicated by means of joint coding (joint coding), so that additional signaling overhead may not be required, thereby saving signaling overhead, reducing limitation on scheduling, and not increasing complexity of terminal equipment for PDCCH blind detection.

Embodiment two:

referring to fig. 7, a flowchart of a method for determining a repetition transmission resource according to the present application is provided, where the method may be applied to a terminal device, and may also be applied to a chip or a chipset in the terminal device, and the method is described below by taking application to the terminal device as an example, and includes:

s701, a terminal device determines a time domain resource allocation list in a plurality of time domain resource allocation lists, wherein the plurality of time domain resource allocation lists comprise at least one first type list and at least one second type list, the first type list is used for configuring resources of first type repeated transmission, and the second type list is used for configuring resources of second type repeated transmission.

The entries in the first type list may be used to configure the resources of the first type retransmission, or may be partially used to configure the resources of the first type retransmission. Further, if the entry portion in the first type list is used to configure the resources of the first type retransmission, other entries in the first type list may be used to configure the resources of the normal transmission. The entries in the second type list may be used entirely for configuring resources for the second type of retransmission, or may be used partially for configuring resources for the second type of retransmission. Further, if the entry portion in the second type list is used to configure the resources of the second type retransmission, then other entries in the second type list may be used to configure the resources of the normal transmission, where "normal transmission" may be understood as a transmission that does not employ a retransmission manner. It will be appreciated that a slot aggregate transmission is also essentially a type of retransmission.

It should be understood that the retransmission types are only exemplary, and the retransmission types in the embodiments of the present application are not limited to the retransmission types based on time slots and the retransmission types based on mini time slots, and may be indicated by similar methods in the present application if other retransmission types occur in future communication developments. In addition, in the embodiment of the present application, the types of retransmission are not limited to two types of retransmission, and in a specific implementation, there may be more types of retransmission (for example, three types, four types, five types, or a combination of three types).

In implementations, each entry in the time domain resource allocation list may contain information indicating a SLIV. Each entry may also contain one or more of the following information: time domain offset, mapping type, number of retransmissions K, redundancy version (redundancy version, RV), etc. The information indicating the SLIV may include a start symbol S for determining a start symbol of a TO for a first transmission in the repeated transmission and a length L for determining a number of symbols of the TO in the repeated transmission. The time domain offset K2 may be used to indicate a time domain offset of a time domain resource location of a PUSCH transmission relative to a PDCCH used to schedule the PUSCH transmission. mapping type may be used to indicate the mapping type of PUSCH transmission, such as typeA or typeB, where typeA and typeB differ in that the time domain positions of the preamble (Front-load) DMRS are different, e.g., for typeA, the Front-load DMRS is located at the 3 rd OFDM symbol, or at the 3 rd and 4 th two OFDM symbols, in each slot, and for type B, the Front-load DMRS is located at the 1 st OFDM symbol, or at the 1 st and 2 nd two OFDM symbols, in each PUSCH. The number of repeated transmissions K is used to indicate the maximum number of repeated transmissions (reception or transmission) of one data packet.

Wherein the time domain resource allocation list may comprise at least one row, e.g. the time domain resource allocation list may comprise 16 rows, each row may be regarded as an entry. The time domain resource allocation list may comprise at least one column, e.g. the time domain resource allocation list may comprise 4 columns, wherein each column may represent one kind of information. For example, a first column may represent a start symbol S, a second column may represent a length L, a third column may represent a mappingtype, and so on. As shown in table 4.

TABLE 4 Table 4

In some embodiments, the terminal device may determine which time domain resource allocation list to use under the direction of the network device.

In some embodiments, if the terminal device has a default time domain resource allocation list, the terminal device may use the time domain resource allocation list. When the terminal device receives the time domain resource allocation list indicated by the network device, the terminal device may use the indicated time domain resource allocation list.

S702, the terminal equipment determines the time domain resource of repeated transmission according to the determined time domain resource allocation list.

In some embodiments, the terminal device may determine the retransmission scheme, that is, determine the location of each TO in the retransmission process, according TO the used time domain resource allocation list. Specifically, if the time domain resource allocation list is a first type list, that is, the time domain resource allocation list corresponds TO a time slot based retransmission, the terminal device may determine that each time slot of the plurality of consecutive time slots includes at most one TO, and positions of different TOs in the respective time slots are identical, and the number of the plurality of time slots may be equal TO the number of repeated transmissions. If the time domain resource allocation list is the second type list, that is, the time domain resource allocation list corresponds TO retransmission based on mini time slots, the terminal device may determine that multiple TOs may be included in one slot.

For ease of understanding, the time domain resource allocation list shown in table 4 is taken as an example, where the Front-load DMRS is located at the 3 rd OFDM symbol (i.e., symbol 2) in each slot for type a, and located at the 1 st OFDM symbol of each PUSCH for type B. As shown in fig. 5, if the time domain resource allocation list shown in table 4 corresponds to a time slot based retransmission, the terminal device may determine that the retransmission mode is a time slot based retransmission. Taking table entry 3 in table 4 as an example, the terminal device may determine that the Front-loadDMRS is located on symbol 2 of each of K consecutive slots, where K is the number of repeated transmissions, assuming that K is equal to 4. The first retransmission resource is offset by j with respect TO the time domain of the PDCCH for scheduling the retransmission resource, and 4 TOs for retransmission are located at 4 symbols from symbol 0 TO symbol 3 of each slot, respectively. Thus, the terminal device may perform one transmission of the data packet on symbol 0 to symbol 3 of each slot, respectively.

As shown in fig. 6, if the time domain resource allocation list shown in table 4 corresponds to the retransmission based on the mini slot, the terminal device may determine that the retransmission mode is the retransmission based on the mini slot. Taking table 5 in table 4 as an example, the terminal device may determine that the Front-load DMRS is located on the first symbol of each PUSCH transmission of K consecutive slots, where K is the number of repeated transmissions, assuming that K is equal to 4. The time domain offset of the first repeated transmission resource (or the starting symbol of the first repeated transmission resource or the time slot or subframe or frame where the first repeated transmission resource is located) relative TO the PDCCH (or the starting symbol or the ending symbol of the PDCCH or the time slot or subframe or frame where the PDCCH is located) for scheduling the repeated transmission resource is j, the first TO is located in 4 symbols from symbol 4 TO symbol 7 of the first time slot for repeated transmission, the second TO is located in 4 symbols from symbol 8 TO symbol 11 of the first time slot, the third TO is located in 2 symbols from symbol 12 TO symbol 13 of the first time slot, the fourth TO is located in 2 symbols from symbol 0 TO 1 of the second time slot, the fifth TO is located in 4 symbols from symbol 2 TO symbol 5 of the second time slot, the third repeated transmission is broken by the time slot boundary, and the third repeated transmission resource is divided into the third TO and the fourth TO. As can be seen in fig. 6, the first three TOs of the 5 TOs are all located in the same time slot. Thus, the terminal device may perform one transmission of the data packet on symbol 4 to symbol 7, symbol 8 to symbol 11, symbol 12 to symbol 13 of the first slot, symbol 0 to symbol 1 of the second slot, and symbol 2 to symbol 5 of the second slot, respectively.

In one implementation, the plurality of time domain resource allocation lists may be configured by the network device for the terminal device through higher layer signaling, which may be RRC signaling, for example. That is, the network device may configure one or more time domain resource allocation lists for the terminal through RRC signaling, and the terminal device receives configuration information of the time domain resource allocation list transmitted by the network device. Wherein at least one time domain resource allocation list of the plurality of time domain resource allocation lists corresponds to a time slot based retransmission (i.e., includes at least one first class list) and at least one time domain resource allocation list corresponds to a mini-slot based retransmission (i.e., includes at least one second class list).

For example, the time domain resource allocation list corresponding to the mini-slot based retransmission may be configured by the high layer parameter timedomainresourceaallocationlist-r 16, for example, the uplink time domain resource allocation list corresponding to the mini-slot based retransmission may be configured by the high layer parameter PUSCH-timedomainresourceaallocationlist-r 16. The time domain resource allocation list corresponding to the slot-based retransmission may be configured by other higher layer parameters, for example, the uplink time domain resource allocation list in Release15 version is configured by the higher layer parameter PUSCH-TimeDomainResourceAllocationList IE.

In another implementation, the plurality of time domain resource allocation lists may be predefined. The terminal device may use the predefined time domain resource allocation list when the network device does not configure the time domain resource allocation list for the terminal device through higher layer signaling. At least one time domain resource allocation list of the one or more time domain resource allocation lists is configured for the terminal device in a predefined manner to correspond to a time slot based retransmission (i.e. comprising at least one first class list) and at least one time domain resource allocation list corresponds to a mini-slot based retransmission (i.e. comprising at least one second class list).

In the embodiment of the application, by associating the time domain resource allocation list with the repeated transmission mode, when the terminal equipment determines the used time domain resource allocation list, the terminal equipment can execute the repeated transmission (or determine the time domain resource) according to the repeated transmission mode corresponding to the time domain resource allocation list. Whether it is a dynamic grant transmission or an unlicensed transmission or a semi-persistent scheduling (SPS) transmission, the terminal needs to determine which time domain resource allocation list to use, so the method for determining duplicate transmission resources according to the embodiment of the present application can be applicable to various transmission scenarios. In addition, in the embodiment of the present application, the time domain resource allocation list may indicate, in addition to a retransmission manner, information such as a SLIV, and it is seen that the retransmission manner and the information such as the SLIV are indicated by means of joint coding (joint coding), so that additional signaling overhead may not be required, thereby saving signaling overhead, reducing limitation on scheduling, and not increasing complexity of terminal equipment for PDCCH blind detection.

It should be noted that, in the repeated transmission based on the mini-slot in the embodiment of the present application, two adjacent TOs may be continuous in the time domain or may be separated by one or more symbols, which is not specifically limited in the present application.

Based on the same inventive concept as the method embodiment, the embodiment of the application provides a device for determining repeated transmission resources. The means for determining the retransmission resources may be used in particular for implementing the method performed by the terminal device in the embodiments of fig. 4 to 7, and the means may be the terminal device itself or may be a chip or a chipset in the terminal device or a part of a chip for performing the functions of the relevant method. The apparatus for determining the retransmission resource may have a structure as shown in fig. 8, and includes a processing unit 801 and a transceiving unit 802. Wherein the transceiver unit 802 is configured to transmit data and/or code instructions, etc., to the processing unit. The processing unit is used for executing the code instruction transmitted by the calling receiving and transmitting unit: determining at least one table entry in a time domain resource allocation list, each table entry in the time domain resource allocation list being used for configuring resources of one of a first type of retransmission and a second type of retransmission; and determining the repeated transmission resources according to the table entry.

An example, an entry may include information indicating a type of retransmission.

In another example, the entry may be used to configure time domain resources for a first type of retransmission when the entry includes information indicating a type of retransmission, and to configure time domain resources for a second type of retransmission when the entry does not include information indicating a type of retransmission. Or when the table entry includes information for indicating the type of retransmission, the table entry may be used to configure time domain resources of the second type of retransmission, and when the table entry does not include information for indicating the type of retransmission, the table entry is used to configure time domain resources of the first type of retransmission.

In some embodiments, the transceiver unit 802 may be further configured to receive configuration information of a time domain resource allocation list sent by a network device.

In other embodiments, the processing unit 801, before determining the at least one entry in the time domain resource allocation list, may be further configured to: a time domain resource allocation list is determined among a plurality of time domain resource allocation lists.

The division of the modules in the embodiments of the present application is schematically only one logic function division, and there may be another division manner in actual implementation, and in addition, each functional module in each embodiment of the present application may be integrated in one processor, or may exist separately and physically, or two or more modules may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. It will be appreciated that the function or implementation of each module in the embodiments of the present application may further refer to the relevant description of the method embodiments.

In a possible manner, the means for determining the retransmission resource may be as shown in fig. 9, and the means may be the terminal device or a chip in the terminal device. The apparatus may include a processor 901, a communication interface 902, and a memory 903. The processing unit 801 may be the processor 901. The transceiver unit 802 may be a communication interface 902.

The processor 901 may be a central processing unit (central processing unit, CPU), or a digital processing unit, or the like. The communication interface 902 may be a transceiver, or may be an interface circuit such as a transceiver circuit, or may be a transceiver chip, or the like. The apparatus further comprises: a memory 903 for storing a program executed by the processor 901. The memory 903 may be a nonvolatile memory such as a Hard Disk Drive (HDD) or a Solid State Drive (SSD), or may be a volatile memory (RAM). Memory 903 is 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, but is not limited to such.

The processor 901 is configured to execute program codes stored in the memory 903, and specifically configured to execute the actions of the processing unit 801, which are not described herein. The communication interface 902 is specifically configured to perform the actions of the transceiver unit 802, which are not described herein.

The specific connection medium between the communication interface 902, the processor 901, and the memory 903 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 903, the processor 901 and the communication interface 902 are connected through a bus 904 in fig. 9, where the bus is indicated by a thick line in fig. 9, and the connection manner between other components is only schematically illustrated, and is not limited thereto. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 9, but not only one bus or one type of bus.

The embodiment of the application also provides a computer readable storage medium for storing computer software instructions required to be executed by the processor, and the computer readable storage medium contains a program required to be executed by the processor.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, 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, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., SSD), etc.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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 duplicate transmission resources, the method comprising:

the method comprises the steps that terminal equipment determines at least one table entry in a time domain resource allocation list, wherein each table entry in the time domain resource allocation list is used for configuring resources of one repeated transmission type in first-type repeated transmission and second-type repeated transmission;

the terminal equipment determines repeated transmission resources according to the table entry;

The table entry is used for configuring the time domain resource of the first type of repeated transmission when the table entry comprises information for indicating the type of repeated transmission, and is used for configuring the time domain resource of the second type of repeated transmission when the table entry does not comprise information for indicating the type of repeated transmission; or alternatively

The table entry is configured to configure the time domain resource of the second type of retransmission when the table entry includes information for indicating a type of retransmission, and is configured to configure the time domain resource of the first type of retransmission when the table entry does not include information for indicating a type of retransmission.

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

and the terminal equipment receives the configuration information of the time domain resource allocation list sent by the network equipment.

3. The method according to claim 1 or 2, wherein before the terminal device determines the at least one entry in the time domain resource allocation list, the method further comprises:

the terminal equipment determines a time domain resource allocation list in a plurality of time domain resource allocation lists.

4. An apparatus for determining duplicate transmission resources, the apparatus comprising:

A memory for storing code instructions;

a processor for invoking execution of the code instructions stored in the memory:

determining at least one entry in a time domain resource allocation list, each entry in the time domain resource allocation list being for configuring a resource of one of a first type of retransmission and a second type of retransmission;

determining repeated transmission resources according to the table entry;

5. The apparatus of claim 4, wherein the apparatus further comprises a transceiver;

the transceiver is configured to receive configuration information of the time domain resource allocation list sent by the network device.

6. The apparatus of claim 4 or 5, wherein the processor, prior to determining the at least one entry in the time domain resource allocation list, is further configured to:

the time domain resource allocation list is determined among a plurality of time domain resource allocation lists.

7. A chip, wherein the chip comprises a communication interface and a processor;

the communication interface is used for receiving the code instruction and transmitting the code instruction to the processor;

the processor is configured to invoke code instructions transmitted by the communication interface to execute:

determining repeated transmission resources according to the table entry;

8. The chip of claim 7, wherein the communication interface is further for receiving configuration information for a network device to send the time domain resource allocation list.

9. The chip of claim 7 or 8, wherein the processor, prior to determining the at least one entry in the time domain resource allocation list, is further configured to:

10. A computer readable storage medium, characterized in that it stores therein a program or instructions, which when read and executed by one or more processors, can implement the method of any of claims 1 to 3.