WO2021030943A1 - 一种确定重复传输资源的方法及装置 - Google Patents

一种确定重复传输资源的方法及装置 Download PDF

Info

Publication number
WO2021030943A1
WO2021030943A1 PCT/CN2019/101022 CN2019101022W WO2021030943A1 WO 2021030943 A1 WO2021030943 A1 WO 2021030943A1 CN 2019101022 W CN2019101022 W CN 2019101022W WO 2021030943 A1 WO2021030943 A1 WO 2021030943A1
Authority
WO
WIPO (PCT)
Prior art keywords
repeated transmission
domain resource
time domain
type
entry
Prior art date
Application number
PCT/CN2019/101022
Other languages
English (en)
French (fr)
Inventor
徐修强
陈雁
吕永霞
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2019/101022 priority Critical patent/WO2021030943A1/zh
Priority to CN201980099302.XA priority patent/CN114223165B/zh
Publication of WO2021030943A1 publication Critical patent/WO2021030943A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path

Definitions

  • This application relates to the field of communication technology, and in particular, to a method and device for determining repeated transmission resources.
  • the 5G NR Release16 version supports Mini-slot-based repeated transmission, that is, the terminal device can repeatedly send the same or different redundancy of the same data packet multiple times in a slot. I version.
  • the terminal When the terminal supports both slot-based repetitive transmission and Mini-slot-based repetitive transmission, the terminal cannot be determined only based on the start symbol and length indicator value (SLIV) and the number of repetitions K. Perform slot-based or mini-slot-based repeated transmission.
  • SIV start symbol and length indicator value
  • the embodiments of the present application provide a method and device for determining repeated transmission resources, which are used to solve the problem that the terminal cannot determine whether to perform slot-based or mini-slot-based repeated transmission in the prior art.
  • an embodiment of the present application provides a method for determining repeated transmission resources, the method includes: a terminal device determines at least one entry in a time domain resource allocation list, and determines the repeated transmission resource according to the determined entry.
  • Each entry in the time domain resource allocation list is used to configure resources of one type of repeated transmission of the first type of repeated transmission and the second type of repeated transmission.
  • the entry of the time domain resource allocation list may indicate the repeated transmission mode.
  • the terminal needs to determine the use of the time domain resource allocation list Which entry in the, therefore, the method for determining repeated transmission resources given in the embodiment of the present application can be applied to various transmission scenarios.
  • the entries in the time domain resource allocation list can also indicate information such as SLIV. It can be seen that the repeated transmission mode and information such as SLIV are performed by joint coding. Indication, therefore, no additional signaling overhead may be required, thereby saving signaling overhead.
  • the table entry includes information that can be used to indicate the type of repeated transmission.
  • an item of information is added to the table entry to indicate the type of repetitive transmission, so that the terminal device can determine which type of repetitive transmission the table item is used for after determining the used table item according to the information, and then Determine the specific structure of repeated transmission resources.
  • the value of the information when the value of the information is the first value, it indicates time-slot-based repeated transmission, that is, the entry is used to configure resources for time-slot-based repeated transmission.
  • the information takes the second value, it indicates repeated transmission based on mini-slots, that is, the entry is used to configure resources for repeated transmission based on mini-slots.
  • the table entry when the table entry includes information for indicating the type of repeated transmission, the table entry can be used to configure the time domain resources of the first type of repeated transmission, and the table entry does not include information for indicating the type of repeated transmission At the time, this entry can be used to configure the time domain resource for the second type of repeated transmission.
  • the terminal device can determine which type of repeated transmission to configure by whether the table entry includes information for indicating the type of repeated transmission, and then can determine the specific structure of the repeated transmission resource.
  • the table entry when the table entry includes information for indicating the type of repeated transmission, the table entry can be used to configure the time domain resource of the second type of repeated transmission, and when the table entry does not include information for indicating the type of repeated transmission , The entry can be used to configure the time domain resources of the first type of repeated transmission.
  • the terminal device can determine which type of repeated transmission to configure by whether the table entry includes information for indicating the type of repeated transmission, and then can determine the specific structure of the repeated transmission resource.
  • the terminal device may receive the configuration information of the time domain resource allocation list sent by the network device.
  • the network device can configure the time domain resource allocation list for the terminal device.
  • the terminal device may determine the time domain resource allocation list from multiple time domain resource allocation lists.
  • the time domain resource allocation list used can be determined from the multiple time domain resource allocation lists.
  • the first transmission type may be repeated transmission based on time slots
  • the second repeated transmission type may be repeated transmission based on mini time slots.
  • an embodiment of the present application provides a method for determining repeated transmission resources.
  • the method includes: a terminal device determines a time domain resource allocation list among multiple time domain resource allocation lists, and allocates resources according to the determined time domain.
  • the list determines the time domain resources for repeated transmission.
  • the multiple time-domain resource allocation lists include at least one first-type list and at least one second-type list.
  • the first-type list is used to configure resources for the first type of repeated transmission
  • the second-type list is used to configure the second type of repeated transmission.
  • the transmitted resources is used to configure the first type of repeated transmission.
  • the terminal device by associating the time domain resource allocation list with the repeated transmission method, when the terminal device determines the time domain resource allocation list to be used, the terminal device can perform the repeated transmission method according to the time domain resource allocation list. Repeat transmission. Regardless of whether it is dynamically authorized transmission, authorization-free transmission, or semi-persistent scheduling (SPS) transmission, the terminal needs to determine which time domain resource allocation list to use. Therefore, the determination of repeated transmission resources given in the embodiment of this application The method can be applied to various transmission scenarios.
  • the time domain resource allocation list can indicate not only the repeated transmission mode, but also information such as SLIV. It can be seen that the repeated transmission mode and information such as SLIV are indicated by joint coding. Therefore, , No additional signaling overhead may be required, thereby saving signaling overhead.
  • the terminal device may determine the time domain resources for repeated transmission according to the first type of repeated transmission. If the determined time domain resource allocation list is the second type of list, the terminal device may determine the time domain resource for repeated transmission according to the second type of repeated transmission. In the above manner, when the terminal device determines the time-domain resource for repeated transmission, no additional signaling overhead may be required, thereby saving signaling overhead.
  • the multiple time domain resource allocation lists may be configured by the network device for the terminal device through high-level signaling.
  • the multiple time-domain resource allocation lists may be predefined.
  • the first transmission type may be repeated transmission based on time slots
  • the second repeated transmission type may be repeated transmission based on mini time slots.
  • the present application provides a device for determining repeated transmission resources.
  • the device may be a terminal device, or a chip or chipset in the terminal device.
  • the device may include a processing unit and a transceiving unit.
  • the processing unit may be a processor, and the transceiving unit may be a transceiver;
  • the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing unit The instructions stored in the storage module are executed, so that the terminal device executes the corresponding functions in the first aspect or the second aspect.
  • the processing unit may be a processor, and the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module to To enable the terminal device to perform the corresponding function in the first aspect, or the second aspect, or the third aspect, the storage module may be a storage module (for example, a register, a cache, etc.) in the chip or a chipset, or the A storage module (for example, read-only memory, random access memory, etc.) located outside the chip or chipset in the communication device.
  • a storage module for example, a register, a cache, etc.
  • the A storage module for example, read-only memory, random access memory, etc.
  • an apparatus for determining repeated transmission resources which includes a processor, a communication interface, and a memory.
  • the communication interface is used to transmit information, and/or messages, and/or data between the device and other devices.
  • the memory is used to store computer-executable instructions.
  • the processor executes the computer-executable instructions stored in the memory, so that the device executes any design in the first aspect or the first aspect, or the second
  • the method for determining repeated transmission resources according to any one of the aspect or the second aspect is designed.
  • a computer storage medium provided by an embodiment of the present application.
  • the computer storage medium stores program instructions.
  • the terminal device executes the first aspect of the embodiments of the present application and any of them. Possible design, or the second aspect or the method of any one of the second aspects.
  • a computer program product provided by an embodiment of the present application, when the computer program product runs on a communication device, causes the communication device to implement the first aspect of the embodiment of the present application and any possible design, or the second aspect or Any design method in the second aspect.
  • a chip provided by an embodiment of the present application is coupled with a memory to execute the first aspect and any possible design of the embodiment of the present application, or the second aspect or any design in the second aspect method.
  • Coupled in the embodiments of the present application means that two components are directly or indirectly combined with each other.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of time slot-based repeated transmission according to an embodiment of the application
  • FIG. 3 is a schematic diagram of repeated transmission based on mini time slots provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of a method for determining repeated transmission resources according to an embodiment of the application
  • FIG. 5 is a schematic diagram of a repeated transmission resource provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram of another repeated transmission resource provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of another method for determining repeated transmission resources according to an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of an apparatus for determining repeated transmission resources according to an embodiment of the application.
  • FIG. 9 is a schematic structural diagram of another device for determining repeated transmission resources according to an embodiment of the application.
  • the method for determining repeated transmission resources can be applied to various communication systems, for example, it can be an Internet of Things (IoT) system, a narrowband Internet of Things (NB-IoT) system, Long-term evolution (LTE) system, it can also be a fifth-generation (5G) communication system, it can also be a hybrid architecture of LTE and 5G, it can also be a 5G new radio (NR) system, and future communication development New communication systems and so on.
  • the first entity sends configuration information to another entity (referred to as the second entity)
  • the first entity sends data to the second entity or receives data sent by the second entity.
  • the second entity receives the configuration information sent by the first entity, and sends data to the first entity or receives data sent by the first entity according to the configuration information.
  • the terminal device involved in the embodiments of the present application is an entity on the user side for receiving or transmitting signals.
  • the terminal device may be a device that provides voice and/or data connectivity to the user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • the terminal device can also be another processing device connected to the wireless modem.
  • the terminal device can communicate with one or more core networks through a radio access network (RAN).
  • Terminal equipment can also be called wireless terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point (access point) , Remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), user equipment (user device), or user equipment (user equipment, UE), etc.
  • the terminal device can be a mobile terminal, such as a mobile phone (or called a "cellular" phone) and a computer with a mobile terminal.
  • a mobile terminal such as a mobile phone (or called a "cellular" phone) and a computer with a mobile terminal.
  • the terminal device can be a portable, pocket-sized, handheld, built-in computer or vehicle-mounted mobile device, which is compatible with wireless The access network exchanges language and/or data.
  • the terminal device can also be a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (personal digital assistant, PDA), and other equipment.
  • Common terminal devices include, for example: mobile phones, tablet computers, laptops, handheld computers, mobile internet devices (MID), wearable devices, such as smart watches, smart bracelets, pedometers, etc., but this application is implemented Examples are not limited to this.
  • the network device involved in the embodiments of the present application is an entity on the network side for transmitting and/or receiving signals, which can be used to convert received air frames and Internet protocol (IP) packets to each other , As a router between the terminal equipment and the rest of the access network, where the rest of the access network may include an IP network, etc.
  • the network equipment can also coordinate the attribute management of the air interface.
  • the network equipment can be an evolved Node B (eNB or e-NodeB) in LTE, a new radio controller (NR controller), or a gNode B (gNB) in a 5G system.
  • eNB evolved Node B
  • NR controller new radio controller
  • gNode B gNode B
  • Network equipment can cover 1 or more cells.
  • a communication system includes a network device and six terminal devices, taking UE1 to UE6 as examples.
  • UE1 to UE6 can send signals to network equipment on the uplink, and the network equipment can receive uplink signals sent by UE1 to UE6.
  • the network device can send configuration information to UE1-UE6.
  • UE4 to UE6 can also form a sub-communication system.
  • the configuration information sending entity and receiving entity can both be terminal devices.
  • terminal device 1 sends configuration information to terminal device 2 and receives the terminal device. 2 data sent; and terminal device 2 receives the configuration information sent by terminal device 1, and sends data to terminal device 1.
  • Fig. 1 is only a schematic diagram, and this application does not specifically limit the type of communication system, and the number and type of devices included in the communication system.
  • the embodiments of this application can be used for dynamic scheduling transmission, dynamic authorization transmission, semi-persistent scheduling transmission, semi-persistent scheduling transmission, authorization-free transmission, or scheduling-free transmission, or dynamic scheduling-free transmission, or dynamic-authorization-free transmission, or high-level configuration transmission , Or configure authorized transmission and other scenarios.
  • the embodiments of the present application can be used in uplink transmission scenarios and can also be used in downlink transmission scenarios.
  • the Release 15 version of 5G NR supports slot aggregation transmission and slot-based repetition transmission of data packets, in which slot aggregation transmission can be applied to Transmission based on dynamic scheduling, that is, physical downlink shared channel (PDSCH) transmission or physical uplink shared channel (PUSCH) transmission is scheduled by physical downlink control channel (PDCCH) Yes, the cyclic redundancy check (CRC) of the PDCCH can be used by the cell-radio network temporary identifier (C-RNTI), modulation and coding scheme-cell radio network temporary identifier (modulation and coding scheme C-RNTI, MCS-C-RNTI) etc. for scrambling.
  • C-RNTI cell-radio network temporary identifier
  • modulation and coding scheme-cell radio network temporary identifier modulation and coding scheme C-RNTI, MCS-C-RNTI
  • the slot-based repeated transmission can be applied to uplink data transmission without dynamic grant (UL data transmission without dynamic grant), and can also be referred to as configured grant (CG) transmission.
  • the terminal can determine the number of time slots for time slot aggregation transmission or the number of slot-based repeated transmissions through the high-level parameters issued by the base station. For example, the terminal can determine the downlink time according to the physical downlink shared channel aggregation factor (pdsch-AggregationFactor) issued by the base station. The number of time slots for slot aggregation transmission is determined according to the physical uplink shared channel aggregation factor (pusch-AggregationFactor) issued by the base station, and the number of time slots for uplink time slot aggregation transmission is determined according to the number of repeated transmissions K (rep-K). The number of repeated transmissions.
  • pdsch-AggregationFactor physical downlink shared channel aggregation factor
  • the number of time slots for slot aggregation transmission is determined according to the physical uplink shared channel aggregation factor (pusch-AggregationFactor) issued by the base station
  • the number of time slots for uplink time slot aggregation transmission
  • K is the value determined by pdsch-AggregationFactor, or pusch-AggregationFactor, or repK
  • a data packet is repeatedly transmitted (received or sent) K times, wherein each time slot transmits the data packet at most once, and in the K time slots, the time domain resources used to transmit the data packet (may be called The transmission occasion (TO) is exactly the same.
  • There are a total of 4 symbols from symbol 2 to symbol 5 and the terminal can send a PUSCH transmission on each of the 4 symbols from symbol 2 to symbol 5 in each of the K time slots.
  • the 5G NR Release16 version supports mini-slot-based aggregate transmission or mini-slot-based repetitive transmission, that is, the terminal can repeatedly send the same one in a slot.
  • the same or different redundancy versions of data packets For example, as shown in Figure 3, when K is 4, the first 3 of the 4 TOs of the 4 PUSCH transmissions of the same data packet are located in the symbols 2-5, 6-9, and 10- of time slot 1. 13. The last TO is located at symbols 0-3 of time slot 2. It can be seen that the first 3 TOs of the 4 TOs are all located in the same time slot.
  • the 5G NR Release 15 version only supports slot-based aggregation transmission (or slot-based repeated transmission), so when the terminal receives the start symbol and length indicator value (start and length indicator value) issued by the base station for configuring time domain resources, SLIV) and the number of repetitions K, the default is to determine K TOs in K consecutive time slots according to the slot-based aggregate transmission mode (or slot-based repetitive transmission) mode, where there is only one TO in each time slot, and Use these K TOs to perform K aggregate transmission or repeated transmission of the same data packet.
  • the terminal supports both slot-based aggregate transmission (or slot-based repeated transmission) and mini-slot-based aggregate transmission (or mini-slot-based repeated transmission), such as 5G NR Release16 version terminal, in this case .
  • the terminal cannot determine whether to perform slot-based aggregate transmission (or slot-based repeated transmission) or mini-slot-based aggregate transmission (or mini-slot-based repeated transmission) only based on the two parameters of SLIV and K, as shown in Figure 2 and As shown in Figure 3, when SLIV indicates that the start symbol index and the symbol length are divided into 2 and 4, and K is 4, the terminal can neither determine whether to perform slot-based repeated transmission as shown in Figure 2 or to perform mini-slot as shown in Figure 3. -based repeated transmission.
  • the base station can explicitly indicate aggregate transmission (or repeated transmission) through radio resource control (radio resource control, RRC) or downlink control information (DCI), For example, through 1 bit in RRC or DCI signaling, when the bit is 0, it can represent slot-based aggregation transmission (or slot-based repeated transmission), and when the bit is 1, it can represent mini-slot-based aggregation Transmission (or mini-slot-based repeated transmission).
  • RRC radio resource control
  • DCI downlink control information
  • the base station explicitly indicates aggregated transmission (or repeated transmission) through RRC or DCI will increase signaling overhead, especially DCI overhead.
  • the terminal can determine the mode of aggregate transmission (or repeated transmission) according to the mapping type (mapping type) indicated by the base station.
  • mapping type mapping type
  • the mapping type indicated by the base station is typeA
  • it can represent slot-based aggregate transmission.
  • typeB stands for mini-slot-based aggregate transmission (or mini-slot-based repeated transmission).
  • the method determined by the terminal according to the mapping type will limit scheduling, for example, slot-based aggregate transmission (or slot-based repeated transmission) cannot be used when mapping type B.
  • the terminal can determine the size of the license-free resource period P. For example, when P is less than K slots, perform mini-slot-based repeated transmission, otherwise perform slot-based repeated transmission.
  • this method is only suitable for unauthorized transmission and does not use dynamic authorization transmission scenarios.
  • the terminal determines according to the attributes of the PDCCH used to schedule PUSCH or PDSCH transmission, such as the type of radio network temporary identifier (RNTI) that scrambles the PDCCH, or the DCI format (format ), or control resource set (CORESET) type, search space (SS), etc. for sending PDCCH.
  • RNTI radio network temporary identifier
  • this method is only suitable for dynamic scheduling scenarios, not for authorization-free transmission scenarios, and will also impose restrictions on scheduling.
  • different DCI formats are used to indicate transmission methods, they will be used to indicate slot-based time slots.
  • the DCI format of aggregate transmission cannot be used to schedule the mini-slot-based aggregate transmission mode, and it will also increase the complexity of blind detection of the PDCCH by the terminal.
  • embodiments of the present application provide a method and device for determining repeated transmission resources.
  • the method and the device are based on the same technical idea. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • And/or describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are in an “or” relationship.
  • the following at least one (item) or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • At least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, c It can be single or multiple.
  • FIG. 4 is a flowchart of a method for determining repeated transmission resources provided in this application.
  • the method can be applied to a terminal device, and can also be applied to a chip or a chip set in a terminal device.
  • the following uses the terminal device as an example for description , The method includes:
  • the terminal device determines at least one entry in the time domain resource allocation list (or table), and each entry in the time domain resource allocation list is used to configure one of the first type of repeated transmission and the second type of repeated transmission Repetitive transfer type of resources.
  • the embodiments of the present application do not limit the relative position of multiple repeated transmissions of a data packet in a time slot and the size of the time domain resources occupied by each repeated transmission.
  • different times of repeated transmissions may be continuous in time or may be Discontinuous, the size of the time domain resources used for different times of repeated transmission may be the same or different.
  • the time domain resource used to transmit the data packet can be called TO.
  • a TO is used below to represent the time domain resource used for one transmission.
  • the repetitive transmission type here is only an exemplary description.
  • the repetitive transmission type in the embodiment of the present application is not limited to time slot-based repetitive transmission and mini time slot-based repetitive transmission. If other repetitive transmission types appear in the future development of communication, It can also be indicated by a similar method in this application.
  • the embodiments of this application are not limited to two types of repeated transmissions. In specific implementation, there can be more types of repeated transmissions (such as three or four or five or). Take three as an example. Each entry in the domain resource allocation list is used to configure resources of one type of repeated transmission in the first type of repeated transmission, the second type of repeated transmission, and the third type of repeated transmission, and so on. It is understandable that the time slot aggregation transmission is essentially a repetitive transmission.
  • the first transmission type is repeated transmission based on time slots
  • the second repeated transmission type is repeated transmission based on mini time slots.
  • each entry in the time-domain resource allocation list may indicate the type of repeated transmission, specifically, it may indicate the manner of repeated transmission by including information indicating the type of repeated transmission, or it may also be determined by whether to include The information used to indicate the type of repeated transmission indicates the manner of repeated transmission.
  • each entry can also contain information for indicating SLIV.
  • Each entry may also contain one or more of the following information: time domain offset, mapping type, number of repeated transmissions K, redundancy version (redundancy version, RV), and so on.
  • the information indicating the SLIV may include a start symbol S and a length L, where the start symbol S is used in repeated transmission to determine the start symbol of the TO for the first transmission, and the length L is used in repeated transmission.
  • the time domain offset K 2 may be used to indicate the time domain offset of the time domain resource position of the PUSCH transmission relative to the PDCCH used to schedule the PUSCH transmission.
  • the mapping type can be used to indicate the mapping type of PUSCH transmission, such as typeA or typeB. The difference between typeA and typeB lies in the time domain position of the front-load DMRS. For example, for type A, the Front-load DMRS is located at every The third OFDM symbol in each slot, or the third and fourth OFDM symbols. For type B, Front-load DMRS is located at the first OFDM symbol of each PUSCH, or the first and second OFDM symbols OFDM symbol.
  • the number of repeated transmissions K is used to indicate the maximum number of repeated transmissions (reception or transmission) of a data packet.
  • the time domain resource allocation list may include at least one row.
  • the time domain resource allocation list may include 16 rows, and each row may be regarded as an entry.
  • the time domain resource allocation list may include at least one column.
  • the time domain resource allocation list may include 4 columns, where each column may represent a type of information.
  • the first column may indicate the start symbol S
  • the second column may indicate the length L
  • the third column may indicate the mapping type
  • the fourth column may indicate the information used to indicate the repeated transmission mode, and so on.
  • a specific indication method may be that when the value of the information is the first value, it indicates the repeated transmission based on the time slot, that is, the entry It is used to configure the resources for time slot-based repeated transmission.
  • the information takes the second value, it indicates repeated transmission based on mini-slots, that is, the entry is used to configure resources for repeated transmission based on mini-slots.
  • this information can be called repetition scheme.
  • the repetition scheme value is type1, it represents the repetitive transmission method based on timeslots.
  • the repetition scheme value is type2, it represents repetition based on mini-slots. transfer method.
  • the repetition scheme is type1, it represents the repetitive transmission mode based on mini-slots, and when the repetition scheme is type2, it represents the repetitive transmission mode based on time slots. Exemplarily, it can be as shown in Table 1.
  • the sub-carrier spacing of PUSCH may be equal to 2 ⁇ ⁇ 15 kHz
  • the value of j may be related to the parameter ( ⁇ ) used to determine the sub-carrier spacing of PUSCH. For example, as shown in Table 2, when ⁇ takes the value When it is 0 or 1, j can be equal to 1, and when ⁇ is 2, j can be equal to 2.
  • repetition scheme Taking the value of repetition scheme as type1, it represents the repetitive transmission method based on time slot, and when the value of repetition scheme is type2, it represents the repetitive transmission method based on mini-slot as an example.
  • the indexes are 1 to 3.
  • the entries 8-13, 15, 16 are used to configure time domain resources based on timeslot repeated transmission, and the entries with indexes 2-7, 14 are used to configure time domain resources based on repeated transmission of mini-slots.
  • a specific indication method may be: when the table entry includes information for indicating the type of repeated transmission, the table item can be used for configuration When the time domain resource of the repeated transmission based on the time slot does not include the information used to indicate the type of repeated transmission, the table item can be used to configure the time domain resource of the repeated transmission based on the mini time slot. Or, when the entry includes information for indicating the type of repeated transmission, the entry can be used to configure the time domain resource for repeated transmission based on mini-slots. When the entry does not include information for indicating the type of repeated transmission, the entry It can be used to configure time-domain resources for time slot-based repeated transmission.
  • the value of the information can be arbitrary, and there is no specific limitation here. Exemplarily, it can be as shown in Table 3.
  • the sub-carrier spacing of PUSCH may be equal to 2 ⁇ ⁇ 15 kHz
  • the value of j may be related to the parameter ( ⁇ ) used to determine the sub-carrier spacing of PUSCH. For example, as shown in Table 2, when ⁇ takes When the value is 0 or 1, j can be equal to 1, and when ⁇ is 2, j can be equal to 2.
  • repetition scheme As 1, it represents the repetitive transmission method based on time slot, and when the repetition scheme is empty, it represents the repetitive transmission method based on mini time slot as an example.
  • the indexes are 1, 4-6
  • the entries of 10, 12, 15, and 16 are used to configure the time domain resources based on timeslot-based repeated transmission, and the entries with indexes of 2 ⁇ 3, 7-9, 11, 13, and 14 are used to configure the mini-slot-based Time domain resources for repeated transmission.
  • the "repetitive transmission” involved in the embodiments of this application can be understood as a terminal device that can repeatedly transmit (receive or send) a data packet K times in multiple consecutive time slots, where K is the number of repeated transmissions.
  • “repetitive transmission” can also be called “aggregated transmission”.
  • transmission scenarios such as dynamic scheduling or dynamic authorization, it can be called “aggregated transmission”.
  • semi-persistent scheduling semi-static In transmission scenarios such as scheduling, authorization-free, or scheduling-free, or dynamic scheduling-free, or dynamic-authorization-free, or high-level configuration, it can be called “repetitive transmission”.
  • “repetitive transmission” can also be named other, such as A. It should be understood that if A can realize the function of "repetitive transmission” in the embodiment of this application, A can also be understood as the implementation of this application. "Repeat transmission” in the example.
  • the terminal device determines at least one entry in the time domain resource allocation list, which can be implemented in the following manner:
  • the network device may send a time domain resource allocation parameter to the terminal device, where the time domain resource allocation parameter is used to indicate at least one table item.
  • the time domain resource allocation parameter may indicate the index of the table item.
  • the terminal device may determine the time domain resource allocation table entry to be used according to the time domain resource allocation parameter issued by the network device.
  • the time domain resource allocation parameter may be the Time domain resource assignment field in the DCI, or may be the RRC parameter timeDomainAllocation.
  • the terminal equipment is based on dynamic scheduling data transmission or authorized data transmission, or Type 2 uplink dynamic authorization-free transmission or downlink semi-persistent scheduling (Semi-Persistent Scheduling, SPS) transmission, etc.
  • the network device can instruct the terminal device which entry in the time domain resource allocation list to use for time domain resource allocation (that is, to determine the repeated transmission resource) through the DCI (such as the Time domain resource assignment field in the DCI).
  • the terminal device performs uplink transmission based on Type 1 uplink dynamic authorization-free, the network device can use RRC signaling (such as timeDomainAllocation IE) to instruct the terminal device to use which entry in the time domain resource allocation list for time domain resource allocation (also Is to determine the repeated transmission resources).
  • RRC signaling such as timeDomainAllocation IE
  • the terminal device determines a repeated transmission resource according to the determined entry.
  • the terminal device may determine the repeated transmission mode according to the entry, and determine the position of each TO during the repeated transmission. Specifically, if the entry is used to configure resources for time-slot-based repeated transmission, that is, the entry is used to indicate time-slot-based repeated transmission, the terminal device can determine that each of the multiple consecutive time slots includes at most For one TO, the positions of different TOs in respective time slots are exactly the same, and the number of the multiple time slots may be equal to the number of repeated transmissions. If the entry is used to configure resources for repeated transmission based on mini-slots, that is, the entry is used to indicate repeated transmissions based on mini-slots, the terminal device may determine that a slot may include multiple TOs.
  • the terminal device can determine each TO according to the SLIV in the table entry, the starting symbol of each TO is determined according to the S in the SLIV, and the number of symbols is according to The L in SLIV is determined.
  • the terminal device determines that multiple TOs can be included in a time slot.
  • the multiple TOs may be continuous or discontinuous in the time domain.
  • the time-frequency of the multiple TOs The size of the resources can be the same or different.
  • the start symbol of can be the next symbol of the Nth TO. If the number of symbols remaining from the start symbol in the slot where the start symbol of the N+1th TO is located is less than L, the N+1th TO can end at the last symbol of the slot.
  • the remaining symbols in the time slot where the start symbols of the N+1 TOs are located are not less than L, and the number of symbols contained in the N+1th time domain resource is also L.
  • the repetition scheme value When the repetition scheme value is type1, it represents a time slot-based repetitive transmission mode. When the repetition scheme value is type2, it represents Repetitive transmission method based on mini time slots.
  • the repetition scheme value For type A, Front-load DMRS is located at the third OFDM symbol (ie, symbol 2) in each slot, and for type B, Front-load DMRS is located at the first OFDM symbol of each PUSCH.
  • the terminal device can determine that the method of repeated transmission is repeated transmission based on time slots, and Front-load DMRS is located in each of K consecutive time slots On the symbol 2 of the time slot, where K is the number of repeated transmissions, assuming that K is equal to 4.
  • the time domain offset of the first repetitive transmission resource relative to the PDCCH used for scheduling the repetitive transmission resource is j, and the four TOs used for repetitive transmission are located in a total of 4 symbols from symbol 0 to symbol 3 in each slot. Therefore, the terminal device can transmit a data packet on symbol 0 to symbol 3 of each time slot respectively.
  • the terminal device can determine that the repeated transmission mode is repeated transmission based on mini-slots, and Front-load DMRS is located at the first of each PUSCH transmission.
  • K is the number of repeated transmissions, assuming that K is equal to 4.
  • the first repeated transmission resource (or the start symbol of the first repeated transmission resource or the time slot or subframe or frame where the first repeated transmission resource is located) is relative to the PDCCH (or the start symbol of the PDCCH) used to schedule the repeated transmission resource Or the termination symbol, or the time-domain offset of the time slot or subframe or frame where the PDCCH is located is j, and the first TO used for repeated transmission is located in the first time slot from symbol 4 to symbol 7 in total 4 symbols,
  • the second TO is located in the first time slot from symbol 8 to symbol 11, a total of 4 symbols
  • the third TO is located in the first time slot from symbol 12 to symbol 13, a total of 2 symbols
  • the fourth TO is located in the second
  • the symbols 0 to 1 of the time slot are 2 symbols
  • the fifth TO is located in the second time slot.
  • the symbols 0 to 3 of the second time slot are 4 symbols.
  • the resources used for repeated transmission ie Symbols 12 to 13 of the first time slot and symbols 0 to 1 of the second time slot
  • the third repetitive transmission is interrupted by the time slot boundary
  • the resources of the third repetitive transmission are divided into the first Three TOs and a fourth TO.
  • the first three TOs of the five TOs are all located in the same time slot. Therefore, the terminal device can use symbols 4 to 7, symbol 8 to symbol 11, symbol 12 to symbol 13, and symbol 0 to symbol 1, and symbol 2 of the second slot in the first slot.
  • ⁇ Symbol 5 carries out a transmission of data packets respectively.
  • the terminal device may determine the used time domain resource allocation list among multiple time domain resource allocation lists.
  • the multiple time-domain resource allocation lists may be configured by the network equipment for the terminal equipment through high-level signaling.
  • the high-level signaling may be RRC signaling. 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 the configuration information of the time domain resource allocation list sent by the network device.
  • at least one of the multiple 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 can be configured with time-slot-based repeated transmission and mini-slot-based A resource of the repeated transmission type in the repeated transmission, the table entry has a parameter that can indicate the type of the repeated transmission or the table entry is associated with the repeated transmission type.
  • the time-domain resource allocation list that meets the characteristics of the time-domain resource allocation list described in step S401 herein can be configured through the high-level parameter TimeDomainResourceAllocationList-r16IE (Information Element), for example, the time-domain resource allocation list that meets the time domain resource allocation list described in step S401 herein
  • the uplink time domain resource allocation list of the characteristic can be configured through the high-level parameter PUSCH-TimeDomainResourceAllocationList-r16.
  • time-domain resource allocation lists that do not meet (or do not fully meet) the characteristics of the time-domain resource allocation list described in step S401 of this article can be configured through other high-level parameters, for example, the uplink time-domain resource allocation in the standard version of 5G NR Release15 The list is configured by the high-level parameter PUSCH-TimeDomainResourceAllocationList IE.
  • the network device can 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 can meet the description of step S401 in this document.
  • the characteristics of the time domain resource allocation list can meet the description of step S401 in this document.
  • PUSCH-TimeDomainResourceAllocationList-r16 may be specifically as follows:
  • PUSCH-TimeDomainResourceAllocationList-r16 is used to configure a time-domain resource allocation list that meets the characteristics of the time-domain resource allocation list described in step S401 of this article, where the configured time-domain resource allocation list includes a maximum of 16 entries, PUSCH-TimeDomainResourceAllocation- r16 is used to configure each table item PUSCH-TimeDomainResourceAllocation-r16, in each table item, k2 is used to configure the time domain resource position of the PUSCH transmission relative to the time domain offset of the PDCCH used to schedule the PUSCH transmission.
  • mappingType is used to configure the mapping type of PUSCH transmission
  • startSymbolAndLength is used to configure the start symbol and length indicator value of the time domain resource
  • repetitionScheme is used to configure the repeated transmission mode (or called the repeated transmission type). It is understandable that each table item may also contain other types of parameters.
  • the multiple time domain resource allocation lists may be predefined.
  • the terminal device can use the predefined time domain resource allocation list.
  • One or more time-domain resource allocation lists are configured for the terminal device in a predefined manner. At least one time-domain resource allocation list meets the characteristics of the time-domain resource allocation list described in step S401 of this document, that is, each entry can be configured based on A resource of a type of repeated transmission in the repeated transmission of the time slot and the repeated transmission based on the mini-slot, the table item may indicate information of the type of the repeated transmission or the table item is associated with the type of the repeated transmission.
  • the predefined time-domain resource list A and time-domain resource list B where the time-domain resource list B can meet the characteristics of the time-domain resource allocation list described in step S401 herein, for example, the entries in the time-domain resource list B include For instructions indicating repeated transmission methods.
  • the terminal device may determine the used time domain resource allocation from the multiple time domain resource allocation lists List.
  • the terminal device may determine which time domain resource allocation list to use under the instruction of the network device.
  • the network device may indicate which time domain resource allocation list the terminal device uses through explicit indication information, and the indication information may be carried in RRC signaling, DCI signaling, or MAC CE signaling and sent to the terminal.
  • the network device may indicate which time-domain resource allocation list to use by the terminal device through one bit of RRC signaling, DCI signaling, or MAC CE signaling. For example, when the value of this bit is 1, the terminal device can be instructed to use the first time domain resource allocation list, and when the value of this bit is 0, the terminal device can be instructed to use the second time domain resource allocation list. Or, when the bit value is 0, the terminal device can be instructed to use the first time domain resource allocation list, and when the bit value is 1, the terminal device can be instructed to use the second time domain resource allocation list.
  • the network device can also implicitly indicate which list the terminal device uses.
  • the network device can use the transmission attribute of the PDCCH to indicate which list the terminal device uses.
  • the PDCCH here refers to the one used to send DCI.
  • PDCCH the DCI is used to schedule PUSCH or PDSCH
  • its transmission attribute may refer to the RNTI type of the CRC that scrambles the DCI, or the CORESET type where the PDCCH is located, or the search space type where the PDCCH is located, etc., such as different RNTI types, Different CORESET types and different search space types can represent different lists.
  • the terminal device can use the time domain resource allocation list by default.
  • the entries of the time domain resource allocation list may contain information indicating the repeated transmission mode or be associated with the repeated transmission mode.
  • the terminal device determines the table entry to be used, the terminal device can respond according to the table entry.
  • the repeated transmission mode performs repeated transmission (or determines time domain resources). Regardless of whether it is a dynamically authorized transmission, an authorization-free transmission, or a semi-persistent scheduling (SPS) transmission, the terminal needs to determine which entry in the time domain resource allocation list is used. Therefore, the embodiment of this application provides The method for determining repeated transmission resources can be applied to various transmission scenarios.
  • the entries in the time domain resource allocation list can also indicate information such as SLIV.
  • the repeated transmission mode and information such as SLIV are performed by joint coding. Indication, therefore, no additional signaling overhead may be required, thereby saving signaling overhead, and reducing the restriction on scheduling, and may not increase the complexity of blind detection of the PDCCH by the terminal device.
  • the method can be applied to a terminal device, and can also be applied to a chip or a chip set in a terminal device.
  • the following is an example of application to a terminal device.
  • the method includes:
  • the terminal device determines a time-domain resource allocation list from multiple time-domain resource allocation lists, where the multiple time-domain resource allocation lists include at least one first-type list and at least one second-type list, and the first-type list is used for configuration The first type of repeated transmission resources, and the second type list is used to configure the second type of repeated transmission resources.
  • the entries in the list of the first type may all be used to configure the resources of the first type of repeated transmission, or part of them may be used to configure the resources of the first type of repeated transmission. Further, if part of the entries in the first-type list is used to configure resources for the first-type repeated transmission, other entries in the first-type list can be used to configure resources for ordinary transmission.
  • the entries in the list of the second type may be all used to configure the resources of the second type of repeated transmission, or part of them may be used to configure the resources of the second type of repeated transmission.
  • the entry part in the second type list is used to configure the resources of the second type of repeated transmission
  • other entries in the second type list can be used to configure the resources of the ordinary transmission, where "ordinary transmission” can be It is understood as transmission without repeated transmission. It is understandable that the time slot aggregation transmission is essentially a repetitive transmission.
  • the embodiments of the present application do not limit the relative position of multiple repeated transmissions of a data packet in a time slot and the size of the time domain resources occupied by each repeated transmission.
  • different times of repeated transmissions may be continuous in time or may be Discontinuous, the size of the time domain resources used for different times of repeated transmission may be the same or different.
  • the time domain resource used to transmit the data packet can be called TO.
  • a TO is used below to represent the time domain resource used for one transmission.
  • the repetitive transmission type here is only an exemplary description.
  • the repetitive transmission type in the embodiment of the present application is not limited to time slot-based repetitive transmission and mini time slot-based repetitive transmission. If other repetitive transmission types appear in the future development of communication, It can also be indicated by a similar method in this application.
  • the embodiments of this application are not limited to two types of repeated transmissions. In specific implementations, there can also be more types of repeated transmissions (such as three or four or five or). Take three as an example.
  • the time-domain resource allocation lists include at least one first-type list, at least one second-type list, and at least one third-type list. The first-type list is used to configure resources for the first type of repeated transmission, and the second-type list is used to configure The second type of repeated transmission resources, and the third type list is used to configure the third type of repeated transmission resources.
  • the first transmission type is repeated transmission based on time slots
  • the second repeated transmission type is repeated transmission based on mini time slots.
  • each entry in the time domain resource allocation list may contain information used to indicate SLIV.
  • Each entry may also contain one or more of the following information: time domain offset, mapping type, number of repeated transmissions K, redundancy version (redundancy version, RV), and so on.
  • the information indicating the SLIV may include a start symbol S and a length L, where the start symbol S is used in repeated transmission to determine the start symbol of the TO for the first transmission, and the length L is used in repeated transmission. Determine the number of TO symbols.
  • the time domain offset K 2 may be used to indicate the time domain offset of the time domain resource position of the PUSCH transmission relative to the PDCCH used to schedule the PUSCH transmission.
  • the mapping type can be used to indicate the mapping type of PUSCH transmission, such as typeA or typeB.
  • the difference between typeA and typeB lies in the time domain position of the front-load DMRS.
  • the Front-load DMRS is located at every The third OFDM symbol in each slot, or the third and fourth OFDM symbols.
  • Front-load DMRS is located at the first OFDM symbol of each PUSCH, or the first and second OFDM symbols OFDM symbol.
  • the number of repeated transmissions K is used to indicate the maximum number of repeated transmissions (reception or transmission) of a data packet.
  • the time-domain resource allocation list may include at least one row.
  • the time-domain resource allocation list may include 16 rows, and each row can be regarded as an entry.
  • the time domain resource allocation list may include at least one column.
  • the time domain resource allocation list may include 4 columns, where each column may represent a type of information.
  • the first column may indicate the start symbol S
  • the second column may indicate the length L
  • the third column may indicate the mapping type, and so on. As shown in Table 4.
  • the sub-carrier spacing of PUSCH may be equal to 2 ⁇ ⁇ 15 kHz
  • the value of j may be related to the parameter ( ⁇ ) used to determine the sub-carrier spacing of PUSCH. For example, as shown in Table 2, when ⁇ takes When the value is 0 or 1, j can be equal to 1, and when ⁇ is 2, j can be equal to 2.
  • the terminal device may determine which time domain resource allocation list to use under the instruction of the network device.
  • the network device may indicate which time domain resource allocation list the terminal device uses through explicit indication information, and the indication information may be carried in RRC signaling, DCI signaling, or MAC CE signaling and sent to the terminal.
  • the network device may indicate which time-domain resource allocation list to use by the terminal device through one bit of RRC signaling, DCI signaling, or MAC CE signaling. For example, when the value of this bit is 1, the terminal device can be instructed to use the first time domain resource allocation list, and when the value of this bit is 0, the terminal device can be instructed to use the second time domain resource allocation list. Or, when the bit value is 0, the terminal device may be instructed to use the first time domain resource allocation list, and when the bit value is 1, the terminal device may be instructed to use the second time domain resource allocation list.
  • the network device can also implicitly indicate which list the terminal device uses.
  • the network device can use the transmission attribute of the PDCCH to indicate which list the terminal device uses.
  • the PDCCH here refers to the one used to send DCI.
  • PDCCH the DCI is used to schedule PUSCH or PDSCH
  • its transmission attribute may refer to the RNTI type of the CRC that scrambles the DCI, or the CORESET type where the PDCCH is located, or the search space type where the PDCCH is located, etc., such as different RNTI types, Different CORESET types and different search space types can represent different lists.
  • the terminal device can use the time domain resource allocation list.
  • the terminal device can use the indicated time domain resource allocation list.
  • the terminal device determines a time domain resource for repeated transmission according to the determined time domain resource allocation list.
  • the terminal device may determine the repeated transmission mode according to the used time domain resource allocation list, that is, determine the position of each TO during the repeated transmission. Specifically, if the time-domain resource allocation list is the first type of list, that is, the time-domain resource allocation list corresponds to timeslot-based repeated transmission, the terminal device can determine that each of the multiple consecutive timeslots includes at most once TO, and the positions of different TOs in respective time slots are exactly the same, the number of the multiple time slots may be equal to the number of repeated transmissions. If the time-domain resource allocation list is the second type of list, that is, the time-domain resource allocation list corresponds to repeated transmission based on mini-slots, the terminal device may determine that a slot may include multiple TOs.
  • the terminal device can determine each TO according to the SLIV in the table entry, the starting symbol of each TO is determined according to the S in the SLIV, and the number of symbols is according to The L in SLIV is determined.
  • the terminal device determines that multiple TOs can be included in a time slot, and the multiple TOs may be continuous or discontinuous in the time domain.
  • the size of the resources can be the same or different.
  • the terminal device may determine that the repeated transmission mode is time slot-based repeated transmission. Taking entry 3 in Table 4 as an example, the terminal device can determine that the Front-load DMRS is located on the symbol 2 of each of the K consecutive time slots, where K is the number of repeated transmissions, assuming that K is equal to 4.
  • the time domain offset of the first repetitive transmission resource relative to the PDCCH used for scheduling the repetitive transmission resource is j, and the 4 TOs used for repetitive transmission are respectively located in a total of 4 symbols from symbol 0 to symbol 3 in each slot. Therefore, the terminal device can transmit a data packet on symbol 0 to symbol 3 of each time slot respectively.
  • the terminal device can determine that the manner of repeated transmission is repeated transmission based on mini-slots. Taking entry 5 in Table 4 as an example, the terminal device can determine that the Front-load DMRS is located on the first symbol of each PUSCH transmission in K consecutive time slots, where K is the number of repeated transmissions, assuming that K is equal to 4. .
  • the first repeated transmission resource (or the start symbol of the first repeated transmission resource or the time slot or subframe or frame where the first repeated transmission resource is located) is relative to the PDCCH (or the start symbol of the PDCCH) used to schedule the repeated transmission resource Or the termination symbol, or the time-domain offset of the time slot or subframe or frame where the PDCCH is located is j, and the first TO used for repeated transmission is located in the first time slot from symbol 4 to symbol 7 in total 4 symbols,
  • the second TO is located in the first time slot from symbol 8 to symbol 11, a total of 4 symbols
  • the third TO is located in the first time slot from symbol 12 to symbol 13, a total of 2 symbols
  • the fourth TO is located in the second
  • the time slot has 2 symbols from 0 to 1, and the fifth TO is located in the second time slot.
  • the third repeated transmission is interrupted by the slot boundary, and the third repeated transmission
  • the resources are divided into the third TO and the fourth TO.
  • the terminal device can use the 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 of the second slot.
  • Data packets are transmitted once on 2 to 5 respectively.
  • the multiple time-domain resource allocation lists may be configured by the network equipment for the terminal equipment through high-level signaling.
  • the high-level signaling may be RRC signaling. 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 the configuration information of the time domain resource allocation list sent by the network device.
  • at least one time-domain resource allocation list in the multiple time-domain resource allocation lists corresponds to timeslot-based repetitive transmission (that is, including at least one first-type list), and at least one time-domain resource allocation list corresponds to mini-slot-based repetition Transmission (ie including at least one second type list).
  • the time domain resource allocation list corresponding to repeated transmission based on mini-slots can be configured through the high-level parameter TimeDomainResourceAllocationList-r16.
  • the uplink time domain resource allocation list corresponding to repeated transmission based on mini-slots can be configured through the high-level parameter PUSCH -TimeDomainResourceAllocationList-r16 for configuration.
  • the time domain resource allocation list corresponding to timeslot-based repeated transmission can be configured through other high-level parameters.
  • the uplink time domain resource allocation list in Release 15 is configured by the high-level parameter PUSCH-TimeDomainResourceAllocationList IE.
  • the network device can 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 can meet the description of step S401 in this document.
  • the characteristics of the time domain resource allocation list can meet the description of step S401 in this document.
  • the multiple time domain resource allocation lists may be predefined.
  • the terminal device can use the predefined time domain resource allocation list.
  • the terminal device by associating the time domain resource allocation list with the repeated transmission method, when the terminal device determines the time domain resource allocation list to be used, the terminal device can perform the repeated transmission method according to the time domain resource allocation list.
  • Repeat transmission or determine time domain resources. Regardless of whether it is dynamically authorized transmission, authorization-free transmission, or semi-persistent scheduling (SPS) transmission, the terminal needs to determine which time domain resource allocation list to use. Therefore, the determination of repeated transmission resources given in the embodiment of this application
  • the method can be applied to various transmission scenarios.
  • the time domain resource allocation list can indicate not only the repeated transmission mode, but also information such as SLIV. It can be seen that the repeated transmission mode and information such as SLIV are indicated by joint coding. Therefore, , No additional signaling overhead may be required, thereby saving signaling overhead, and reducing scheduling restrictions, and may not increase the complexity of blind detection of the PDCCH by the terminal device.
  • 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.
  • the embodiment of the present application provides an apparatus for determining repeated transmission resources.
  • the device for determining repeated transmission resources can be specifically used to implement the method executed by the terminal device in the embodiments of FIG. 4 to FIG. 7.
  • the device may be the terminal device itself, or the chip or chip set in the terminal device or the chip used in the terminal device. Perform part of the related method function.
  • the structure of the apparatus for determining repeated transmission resources may be as shown in FIG. 8, including a processing unit 801 and a transceiver unit 802. Among them, the transceiver unit 802 is used to transmit data and/or code instructions to the processing unit.
  • the processing unit is configured to execute by calling the code instructions transmitted by the transceiver unit: determine at least one entry in the time domain resource allocation list, and each entry in the time domain resource allocation list is used to configure the first type of repeated transmission and the second A type of repetitive transmission resource in type repetitive transmission; the repetitive transmission resource is determined according to the table entry.
  • the table entry may include information for indicating the type of repeated transmission.
  • the table entry when the table entry includes information used to indicate the type of repeated transmission, the table entry can be used to configure the time domain resources of the first type of repeated transmission. When the table entry does not include information used to indicate the type of repeated transmission, the table entry Used to configure time domain resources for the second type of repeated transmission. Or, when the table entry includes information for indicating the type of repeated transmission, the table entry can be used to configure the time domain resources of the second type of repeated transmission, and when the table entry does not include information for indicating the type of repeated transmission, the table entry is used for configuration The first type of repeated transmission of time domain resources.
  • the transceiver unit 802 may also be used to receive configuration information of the time domain resource allocation list sent by the network device.
  • the processing unit 801 before determining at least one entry in the time domain resource allocation list, may also be used to determine a time domain resource allocation list from multiple time domain resource allocation lists.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, there may be other division methods.
  • the functional modules in the various embodiments of the present application may be integrated into one process. In the device, it can also exist alone physically, or two or more modules can be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It can be understood that, for the function or implementation of each module in the embodiment of the present application, reference may be made to the related description of the method embodiment.
  • the device for determining the repeated transmission resource may be as shown in FIG. 9, and the device may be a terminal device or a chip in the terminal device.
  • the device may include a processor 901, a communication interface 902, and a memory 903.
  • the processing unit 801 may be a 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, and so on.
  • the communication interface 902 may be a transceiver, an interface circuit such as a transceiver circuit, etc., or a transceiver chip, etc.
  • the device further includes: a memory 903, configured to store a program executed by the processor 901.
  • the memory 903 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and may also be a volatile memory (volatile memory), such as random access memory (random access memory). -access memory, RAM).
  • the memory 903 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the processor 901 is configured to execute the program code stored in the memory 903, and is specifically configured to execute the actions of the above-mentioned processing unit 801, which will not be repeated in this application.
  • the communication interface 902 is specifically configured to perform the actions of the above-mentioned transceiver unit 802, which will not be repeated in this application.
  • connection medium between the aforementioned communication interface 902, the processor 901, and the memory 903 is not limited in the embodiment of the present application.
  • the memory 903, the processor 901, and the communication interface 902 are connected by a bus 904 in FIG. 9.
  • the bus is represented by a thick line in FIG. 9.
  • the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the embodiment of the present invention also provides a computer-readable storage medium for storing computer software instructions required to execute the above-mentioned processor, which contains a program required to execute the above-mentioned processor.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, an SSD).
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种确定重复传输资源的方法及装置，用于解决现有技术中终端无法确定执行slot-based还是Mini-slot-based的重复传输的问题。该方法包括：终端设备在时域资源分配列表中确定至少一个表项，并根据确定的该表项确定重复传输资源。时域资源分配列表中的每个表项用于配置第一类型重复传输和第二类型重复传输中的一种重复传输类型的资源。

Description

一种确定重复传输资源的方法及装置 技术领域
本申请涉及通信技术领域，特别涉及一种确定重复传输资源的方法及装置。
背景技术
为提高数据包的传输可靠性，5G新空口(new radio，NR)Release15版本支持基于时隙(slot-based)的重复传输，即终端设备可以在连续的K(K>＝1)个时隙(slot)中，重复发送或接收一个数据包的最多K次传输，其中每个slot最多一次，且K个slot中，用于发送或接收数据包的一次传输的时域资源完全相同。
为进一步降低数据传输时延，5G NR Release16版本支持基于迷你时隙(Mini-slot-based)的重复传输，即终端设备可以在一个slot内可以多次重复发送同一个数据包的相同或不同冗余版本。
当终端同时支持slot-based的重复传输和Mini-slot-based的重复传输时，终端仅根据起始符号和长度指示值(start and length indicator value，SLIV)和重复次数K这两个参数无法确定执行slot-based还是Mini-slot-based的重复传输。
发明内容
本申请实施例提供了一种确定重复传输资源的方法及装置，用于解决现有技术中终端无法确定执行slot-based还是Mini-slot-based的重复传输的问题。
第一方面，本申请实施例提供的一种确定重复传输资源的方法，该方法包括：终端设备在时域资源分配列表中确定至少一个表项，并根据确定的该表项确定重复传输资源。时域资源分配列表中的每个表项用于配置第一类型重复传输和第二类型重复传输中的一种重复传输类型的资源。本申请实施例中，时域资源分配列表的表项可以指示重复传输的方式，当终端设备确定使用的表项时，终端设备可以根据该表项相应的重复传输方式执行重复传输。不论是动态授权的传输还是免授权传输(也被称为配置授权的传输(transmission with configured grant))或半静态调度(semi-persistent scheduling，SPS)传输，终端都需要确定使用时域资源分配列表中的哪个表项，因此，本申请实施例所给出的确定重复传输资源的方法可以适用于各种传输场景。另外，本申请实施例中，时域资源分配列表的表项除了可以指示重复传输的方式，还可以指示SLIV等信息，可见，重复传输方式与SLIV等信息通过联合编码(joint coding)的方式进行指示，因此，可以不需要额外的信令开销，从而可以节省信令开销。
在一种可能的设计中，表项包括可以用于指示重复传输类型的信息。上述设计中，通过在表项中增加一项信息来指示重复传输类型，从而终端设备在确定所使用的表项后可以根据该信息确定该表项用于配置哪种类型的重复传输，进而可以确定重复传输资源的具体结构。
在一种可能的设计中，该信息取值为第一值时指示基于时隙的重复传输，即该表项用于配置基于时隙的重复传输的资源。该信息取值为第二值时指示基于迷你时隙的重复传输，即该表项用于配置基于迷你时隙的重复传输的资源。
在一种可能的设计中，表项包括用于指示重复传输类型的信息时，该表项可以用于配置第一类型重复传输的时域资源，表项未包括用于指示重复传输类型的信息时，该表项可以用于配置第二类型重复传输的时域资源。通过上述设计中，终端设备可以通过表项中是否包括用于指示重复传输类型的信息来确定该用于配置哪种类型的重复传输，进而可以确定重复传输资源的具体结构。
在一种可能的设计中，表项包括用于指示重复传输类型的信息时，表项可以用于配置第二类型重复传输的时域资源，表项未包括用于指示重复传输类型的信息时，表项可以用于配置第一类型重复传输的时域资源。通过上述设计中，终端设备可以通过表项中是否包括用于指示重复传输类型的信息来确定该用于配置哪种类型的重复传输，进而可以确定重复传输资源的具体结构。
在一种可能的设计中，终端设备可以接收网络设备发送时域资源分配列表的配置信息。通过上述设计，网络设备可以为终端设备配置时域资源分配列表。
在一种可能的设计中，在终端设备在时域资源分配列表中确定至少一个表项之前，终端设备可以在多个时域资源分配列表中确定时域资源分配列表。通过上述设计，当终端设备有多个时域资源分配列表时，可以在该多个时域资源分配列表中确定所使用的时域资源分配列表。
在一种可能的设计中，第一传输类型可以为基于时隙的重复传输，第二重复传输类型可以为基于迷你时隙的重复传输。
第二方面，本申请实施例提供的一种确定重复传输资源的方法，该方法包括：终端设备在多个时域资源分配列表中确定一个时域资源分配列表，并根据确定的时域资源分配列表确定重复传输的时域资源。其中，多个时域资源分配列表包括至少一个第一类列表和至少一个第二类列表，第一类列表用于配置第一类型重复传输的资源，第二类列表用于配置第二类型重复传输的资源。本申请实施例中，通过将时域资源分配列表与重复传输的方式进行关联，当终端设备确定使用的时域资源分配列表时，终端设备可以根据该时域资源分配列表相应的重复传输方式执行重复传输。不论是动态授权的传输还是免授权传输或半静态调度(semi-persistent scheduling，SPS)传输，终端都需要确定使用哪个时域资源分配列表，因此，本申请实施例所给出的确定重复传输资源的方法可以适用于各种传输场景。另外，本申请实施例中，时域资源分配列表除了可以指示重复传输的方式，还可以指示SLIV等信息，可见，重复传输方式与SLIV等信息通过联合编码(joint coding)的方式进行指示，因此，可以不需要额外的信令开销，从而可以节省信令开销。
在一种可能的设计中，若确定的时域资源分配列表为第一类列表，则终端设备可以根据第一类型重复传输确定重复传输的时域资源。若确定的时域资源分配列表为第二类列表，则终端设备可以根据第二类型重复传输确定重复传输的时域资源。通过上述方式，终端设备确定重复传输的时域资源时，可以不需要额外的信令开销，从而可以节省信令开销。
在一种可能的设计中，该多个时域资源分配列表可以是网络设备通过高层信令为终端设备配置的。
在一种可能的设计中，该多个时域资源分配列表可以是预定义的。
在一种可能的设计中，第一传输类型可以为基于时隙的重复传输，第二重复传输类型可以为基于迷你时隙的重复传输。
第三方面，本申请提供一种确定重复传输资源的装置，该装置可以是终端设备，也可 以是终端设备内的芯片或芯片组。该装置可以包括处理单元和收发单元。当该装置是终端设备时，该处理单元可以是处理器，该收发单元可以是收发器；该装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理单元执行该存储模块所存储的指令，以使终端设备执行上述第一方面、或第二方面中相应的功能。当该装置是通信设备内的芯片或芯片组时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储模块所存储的指令，以使终端设备执行上述第一方面、或第二方面、或第三方面中相应的功能，该存储模块可以是该芯片或芯片组内的存储模块(例如，寄存器、缓存等)，也可以是该通信设备内的位于该芯片或芯片组外部的存储模块(例如，只读存储器、随机存取存储器等)。
第四方面，提供了一种确定重复传输资源的装置，包括：处理器、通信接口和存储器。通信接口用于该装置与其他装置之间传输信息、和/或消息、和/或数据。该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述第一方面或第一方面中任一设计、或者第二方面或第二方面中任一设计所述的确定重复传输资源的方法。
第五方面，本申请实施例提供的一种计算机存储介质，该计算机存储介质存储有程序指令，当程序指令在终端设备上运行时，使得终端设备执行本申请实施例第一方面及其任一可能的设计、或者第二方面或第二方面中任一设计的方法。
第六方面，本申请实施例提供的一种计算机程序产品，当计算机程序产品在通信设备上运行时，使得通信设备本申请实施例第一方面及其任一可能的设计、或者第二方面或第二方面中任一设计的方法。
第七方面，本申请实施例提供的一种芯片，所述芯片与存储器耦合，执行本申请实施例第一方面及其任一可能的设计、或者第二方面或第二方面中任一设计的方法。
另外，第三方面至第七方面所带来的技术效果可参见上述第一方面或第二方面的描述，此处不再赘述。
需要说明的是，本申请实施例中“耦合”是指两个部件彼此直接或间接地结合。
附图说明
图1为本申请实施例提供的一种通信系统的架构示意图；
图2为本申请实施例提供的一种基于时隙的重复传输的示意图；
图3为本申请实施例提供的一种基于迷你时隙的重复传输的示意图；
图4为本申请实施例提供的一种确定重复传输资源的方法的流程示意图；
图5为本申请实施例提供的一种重复传输资源的示意图；
图6为本申请实施例提供的另一种重复传输资源的示意图；
图7为本申请实施例提供的另一种确定重复传输资源的方法的流程示意图；
图8为本申请实施例提供的一种确定重复传输资源的装置的结构示意图；
图9为本申请实施例提供的另一种确定重复传输资源的装置的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步 地详细描述。
本申请提供的确定重复传输资源的方法可以应用于各类通信系统中，例如，可以是物联网(internet of things，IoT)系统、窄带物联网(narrow band internet of things，NB-IoT)系统、长期演进(long term evolution，LTE)系统，也可以是第五代(5G)通信系统，还可以是LTE与5G混合架构、也可以是5G新无线(new radio，NR)系统，以及未来通信发展中出现的新的通信系统等。只要通信系统中存在一个实体(称为第一实体)向另一实体(称为第二实体)发送配置信息，并且第一实体向第二实体发送数据、或接收第二实体发送的数据。对应的，第二实体接收第一实体发送的配置信息，并根据该配置信息向第一实体发送数据、或接收第一实体发送的数据。
本申请实施例中涉及的终端设备，是用户侧的一种用于接收或发射信号的实体。终端设备可以是一种向用户提供语音和/或数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。终端设备也可以是连接到无线调制解调器的其他处理设备。终端设备可以通过无线接入网(radio access network，RAN)与一个或多个核心网进行通信。终端设备也可以称为无线终端、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、用户设备(user device)、或用户设备(user equipment，UE)等等。终端设备可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，终端设备还可以是个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、等设备。常见的终端设备例如包括：手机、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，例如智能手表、智能手环、计步器等，但本申请实施例不限于此。
本申请实施例中所涉及的网络设备，是网络侧的一种用于发射和/或接收信号的实体，可以用于将收到的空中帧与网络协议(internet protocol，IP)分组进行相互转换，作为终端设备与接入网的其余部分之间的路由器，其中接入网的其余部分可以包括IP网络等。网络设备还可以协调对空中接口的属性管理。例如，网络设备可以是LTE中的演进型基站(evolutional Node B，eNB或e-NodeB)，还可以是新无线控制器(new radio controller，NR controller)，可以是5G系统中的gNode B(gNB)，可以是集中式网元(centralized unit)，可以是新无线基站，可以是射频拉远模块，可以是微基站，可以是中继(relay)，可以是分布式网元(distributed unit)，可以是接收点(transmission reception point，TRP)或传输点(transmission point，TP)或者任何其它无线接入设备，但本申请实施例不限于此。网络设备可以覆盖1个或多个小区。
参阅图1所示，为本申请实施例提供的一种通信系统，该通信系统包括网络设备和六个终端设备，以UE1～UE6为例。在该通信系统中，UE1～UE6可以在上行链路上向网络设备发送信号，网络设备可以接收UE1～UE6发送的上行信号。同时，网络设备可以向UE1-UE6发送配置信息。此外，UE4～UE6也可以组成一个子通信系统，此时，配置信息发送实体和接收实体可以都是终端设备，例如车联网系统中，终端设备1向终端设备2发送配置信息， 并且接收终端设备2发送的数据；而终端设备2接收终端设备1发送的配置信息，并向终端设备1发送数据。图1仅是一种示意图，本申请并不对通信系统的类型，以及通信系统内包括的设备的数量、类型等进行具体限定。
本申请实施例可用于动态调度传输、动态授权传输、半持续调度传输、半静态调度传输、免授权传输、或免调度传输、或免动态调度传输、或免动态授权传输、或高层配置的传输、或配置授权的传输等场景。本申请实施例可用于上行传输场景，也可以用于下行传输场景。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
为提高数据包的传输可靠性，5G NR的Release15版本支持数据包的时隙聚合(slot aggregation)传输和基于时隙的(slot-based)重复传输(repetition)，其中时隙聚合传输可以适用于基于动态调度的传输，即物理下行共享信道(physical downlink shared channel，PDSCH)传输或物理上行共享信道(physical uplink shared channel，PUSCH)传输是由物理下行控制信道(physical downlink control channel，PDCCH)所调度的，该PDCCH的循环冗余校验(cyclic redundancy check，CRC)可以被小区无线网络临时标识(cell-radio network temporary identifier，C-RNTI)、调制和编码方案-小区无线网络临时标识(modulation and coding scheme C-RNTI，MCS-C-RNTI)等进行加扰。而slot-based的重复传输则可以适用于上行免动态授权传输(UL data transmission without dynamic grant)，也可以称为配置的授权(configured grant，CG)传输。
终端可以通过基站下发的高层参数确定时隙聚合传输的时隙数或slot-based重复传输的次数，例如，终端可以根据基站下发的物理下行共享信道聚合因子(pdsch-AggregationFactor)确定下行时隙聚合传输的时隙数，根据基站下发的物理上行共享信道聚合因子(pusch-AggregationFactor)确定上行时隙聚合传输的时隙数，根据重复传输次数K(rep-K)确定上行slot-based重复传输的次数。不管是slot-based重复传输还是时隙聚合传输，终端都是在连续的K(K>＝1)(K即为前述由pdsch-AggregationFactor，或pusch-AggregationFactor，或repK确定的值)个时隙中，重复传输(接收或发送)一个数据包K次，其中，每个时隙最多传输该数据包一次，且K个时隙中，用于传输该数据包的时域资源(可称之为传输时机(transmission occasion，TO))完全相同，例如，如图2所示，K＝4，终端被配置的用于发送一次数据包(这里称为一次PUSCH传输)的PUSCH传输资源位于时隙的符号2到符号5共4个符号，则终端可以在K个时隙中的每个时隙中的符号2到符号5共4个符号上各发送一次PUSCH传输。
为了进一步降低数据传输时延，5G NR Release16版本支持基于迷你时隙的(mini-slot-based)聚合传输或mini-slot-based重复传输，即终端可以在一个slot内可以多次重复发送同一个数据包的相同或不同冗余版本。例如，如图3所示，当K为4时，终端发送同一个数据包的4次PUSCH传输的4个TO中前3个分别位于时隙1的符号2-5、6-9、10-13，最后一个TO位于时隙2的符号0-3，可见，4次TO的前3个TO都位于同一个时隙内。
5G NR Release15版本仅支持slot-based聚合传输(或slot-based重复传输)，因此当终端接收到基站下发的用于配置时域资源的起始符号和长度指示值(start and length indicator  value，SLIV)和重复次数K时，默认按照slot-based聚合传输方式(或slot-based重复传输)方式在K个连续的时隙中确定K个TO，其中每个时隙中仅有一个TO，并使用这K个TO对同一个数据包进行K次聚合传输或重复传输。但是当终端同时支持slot-based聚合传输(或slot-based重复传输)和mini-slot-based聚合传输(或mini-slot-based重复传输)时，例如5G NR Release16版本的终端，这种情况下，终端仅根据SLIV和K这两个参数无法确定执行slot-based聚合传输(或slot-based重复传输)还是mini-slot-based聚合传输(或mini-slot-based重复传输)，例如图2和图3所示，SLIV指示起始符号索引和符号长度分为2和4、K为4时，终端既无法确定是执行如图2的slot-based重复传输，还是执行如图3的mini-slot-based重复传输。
针对上述问题，一种可能的解决方法为：基站可以通过无线资源控制(radio resource control，RRC)或下行控制信息(downlink control information，DCI)显式的指示聚合传输(或重复传输)的方式，例如通过RRC或者DCI信令中的1个比特，当该比特取0的时候可以代表slot-based聚合传输(或slot-based重复传输)，当该比特取1时可以代表mini-slot-based聚合传输(或mini-slot-based重复传输)。但是，基站通过RRC或DCI显式的指示聚合传输(或重复传输)的方式，会增加信令开销，尤其DCI的开销。
另一种可能的解决方法为：终端可以根据基站指示的映射类型(mapping type)确定聚合传输(或重复传输)的方式，例如，当基站指示的mapping type为typeA时可以代表slot-based聚合传输(或slot-based重复传输)，typeB代表mini-slot-based聚合传输(或mini-slot-based重复传输)。但是，这种方式中，终端根据mapping type确定的方式，会给调度带来限制，例如mapping typeB时不能使用slot-based聚合传输(或slot-based重复传输)等。
还有一种可能的解决方法为：终端可以根据免授权资源周期P的大小确定，例如P小于K个slot时，执行mini-slot-based重复传输，否则执行slot-based重复传输。但是，这种方式仅适用于免授权传输，不使用动态授权传输场景。
还有另一种可能的解决方法为：终端根据用于调度PUSCH或PDSCH传输的PDCCH的属性确定，例如加扰PDCCH的无线网络临时标识(radio network temporary identifier，RNTI)类型、或DCI格式(format)、或发送PDCCH的控制资源集合(control resource set，CORESET)类型、搜索空间(search space，SS)等。但是这种方式仅适用于动态调度场景，不适用于免授权传输场景，同时也会对调度带来限制，例如使用不同的DCI format来指示传输方式时，会导致用于指示slot-based时隙聚合传输的DCI format不能用于调度mini-slot-based聚合传输方式，也会增加终端对PDCCH盲检测的复杂度。
基于此，本申请实施例提供一种确定重复传输资源的方法及装置。其中，方法和装置是基于同一技术构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
应理解，本申请实施例中“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A、B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一(项)个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b或c中的至少一项(个)，可以表示：a，b，c，a和b，a和c，b和c，或a、b和c，其中a、b、c可以是单个，也可以是多个。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
下面结合附图对本申请实施例提供的确定重复传输资源的方法进行具体说明。
实施例一：
参见图4，为本申请提供的确定重复传输资源的方法的流程图，该方法可以应用于终端设备，也可以应用于终端设备中的芯片或者芯片组，下面以应用于终端设备为例进行说明，该方法包括：
S401，终端设备在时域资源分配列表(或表格)中确定至少一个表项，时域资源分配列表中的每个表项用于配置第一类型重复传输和第二类型重复传输中的一种重复传输类型的资源。
一种示例性说明中，重复传输类型可以有两种，一种是基于时隙的重复传输，即一个时隙中最多只有一个数据包的一次传输，另一种是基于迷你时隙的重复传输，即一个时隙中可以有一个数据包的多次重复传输。本申请实施例对一个时隙内一个数据包的多次重复传输的相对位置以及每次重复传输所占用的时域资源大小不做限定，例如不同次的重复传输可以在时间上连续也可以是不连续，不同次的重复传输所使用的时域资源的大小可以相同，也可以不同。其中，重复传输中，用于传输数据包的时域资源可称之为TO，为了方便描述，下面用一个TO来表示用于一次传输的时域资源。
应理解，这里重复传输类型仅为示例性说明，本申请实施例中重复传输类型并不仅限于基于时隙的重复传输和基于迷你时隙的重复传输，若未来通信发展中出现其他重复传输类型，也可以通过本申请类似的方法进行指示。并且，本申请实施例中不仅限于两种重复传输类型，在具体实施中，重复传输类型也可以有更多(如三种或四种或五种或……)，以三种为例，时域资源分配列表中的每个表项用于配置第一类型重复传输、第二类型重复传输、第三类型重复传输中的一种重复传输类型的资源，等等。可以理解的是，时隙聚合传输实质上也是一种重复传输。
为了描述上的方便，下面将第一传输类型为基于时隙的重复传输，第二重复传输类型为基于迷你时隙的重复传输。
具体实施中，时域资源分配列表中的每个表项可以指示重复传输的类型，具体可以是通过包括用于指示重复传输类型的信息来指示重复传输的方式，或者，也可以是通过是否包括用于指示重复传输类型的信息来指示重复传输的方式。此外，每个表项还可以包含用于指示SLIV的信息。每个表项也可以包含如下一种或多种信息：时域偏置、mapping type、重复传输次数K、冗余版本(redundancy version，RV)等等。其中，指示SLIV的信息可以包括起始符号S和长度L，其中，起始符号S用于在重复传输中用于确定首次传输的TO的起始符号，长度L用于在重复传输中用于确定TO的符号数。时域偏置K 2可以用于指示PUSCH传输的时域资源位置相对于用于调度该PUSCH传输的PDCCH的时域偏置。mapping type可以用于指示PUSCH传输的映射类型，如typeA或typeB，typeA和typeB的区别在于，前置(Front-load)DMRS的时域位置不同，例如，对于type A，Front-load DMRS位于每个时隙中第3个OFDM符号，或第3和第4共两个OFDM符号，对于type B，Front-load DMRS位于每次PUSCH的第1个OFDM符号，或第1和第2共两个OFDM符号。重复传输次数K，用于指示重复传输(接收或发送)一个数据包的最大次数。
其中，时域资源分配列表可以包括至少一行，例如，时域资源分配列表可以包括16行， 每一行可以看做是一个表项。时域资源分配列表可以包括至少一列，例如，时域资源分配列表可以包括4列，其中，每一列可以表示一种信息。例如，第一列可以表示起始符号S，第二列可以表示长度L，第三列可以表示mapping type，第四列可以表示用于指示重复传输方式的信息，等等。
表项通过包括用于指示重复传输类型的信息来指示重复传输的方式时，一种具体的指示方法可以为，该信息取值为第一值时指示基于时隙的重复传输，即该表项用于配置基于时隙的重复传输的资源。该信息取值为第二值时指示基于迷你时隙的重复传输，即该表项用于配置基于迷你时隙的重复传输的资源。示例性的，该信息可以称为重复方式(repetition scheme)，当repetition scheme取值为type1时，代表基于时隙的重复传输方式，当repetition scheme取值为type2时，代表基于迷你时隙的重复传输方式。或者，当repetition scheme取值为type1时，代表基于迷你时隙的重复传输方式，当repetition scheme取值为type2时，代表基于时隙的重复传输方式。示例性的，可以如表1所示。
表1
Figure PCTCN2019101022-appb-000001
一种实现方式中，PUSCH的子载波间隔可以等于2 μ×15kHz，j的值可以与用于确定PUSCH的子载波间隔的参数(μ)有关，例如，如表2所示，当μ取值为0或1时，j可以等于1，μ取值为2时，j可以等于2。
表2
μ j
0 1
1 1
2 2
以当repetition scheme取值为type1时，代表基于时隙的重复传输方式，当repetition scheme取值为type2时，代表基于迷你时隙的重复传输方式为例，表1中，索引为1～3、8～13、15、16的表项用于配置基于时隙的重复传输的时域资源，索引为2～7、14的表项用于配置基于迷你时隙的重复传输的时域资源。
表项通过是否包括用于指示重复传输类型的信息来指示重复传输的方式时，一种具体的指示方式可以为，表项包括用于指示重复传输类型的信息时，该表项可以用于配置基于时隙的重复传输的时域资源，表项未包括用于指示重复传输类型的信息时，该表项可以用于配置基于迷你时隙的重复传输的时域资源。或者，表项包括用于指示重复传输类型的信息时，该表项可以用于配置基于迷你时隙的重复传输的时域资源，表项未包括用于指示重复传输类型的信息时，表项可以用于配置基于时隙的重复传输的时域资源。表项中包括用于指示重复传输类型的信息时，该信息的取值可以为任意，这里不做具体限定。示例性的，可以如表3所示。
表3
Figure PCTCN2019101022-appb-000002
一种实现方式中，PUSCH的子载波间隔可以等于2 μ×15kHz，j的值可以与用于确定PUSCH的子载波间隔的参数(μ)有关，例如，如上述表2所示，当μ取值为0或1时，j可以等于1，μ取值为2时，j可以等于2。
以当repetition scheme取值为1时，代表基于时隙的重复传输方式，当repetition scheme为空时，代表基于迷你时隙的重复传输方式为例，表3中，索引为1、4～6、10、12、15、16的表项用于配置基于时隙的重复传输的时域资源，索引为2～3、7～9、11、13、14的表项 用于配置基于迷你时隙的重复传输的时域资源。
需要说明的是，本申请实施例所涉及“重复传输”可以理解为终端设备可以在连续的多个时隙中，重复传输(接收或发送)一个数据包K次，其中，K为重复传输次数，在实际应用中，“重复传输”也可以称为“聚合传输”，示例性的，在动态调度、或者动态授权等传输场景中，可以称为“聚合传输”，在半持续调度、半静态调度、免授权、或免调度、或免动态调度、或免动态授权、或高层配置等传输场景中，可以称为“重复传输”。当然，在未来通信系统中，也可以将“重复传输”命名为其他，例如A，应理解，若A可以实现本申请实施例中“重复传输”的功能，也可以将A理解为本申请实施例中的“重复传输”。
一些实施例中，终端设备在时域资源分配列表中确定至少一个表项，可以通过如下方式实现：
网络设备可以向终端设备发送时域资源分配参数，该时域资源分配参数用于指示至少一个表项，例如，时域资源分配参数可以指示表项的索引。终端设备可以根据网络设备下发的时域资源分配参数来确定所使用的时域资源分配表项。一种示例性说明中，例如时域资源分配参数可以是DCI中的Time domain resource assignment域，也可以是RRC参数timeDomainAllocation。
一种具体的实现方式中，如果终端设备是基于动态调度数据传输或基于授权数据传输，或Type 2上行免动态授权传输或下行半静态调度(Semi-Persistent Scheduling，SPS)传输等方式进行传输的，网络设备可以通过DCI(如DCI中的Time domain resource assignment域)指示终端设备使用时域资源分配列表中的哪一个表项进行时域资源分配(也就是确定重复传输资源)。如果终端设备是基于Type 1上行免动态授权进行上行传输的，网络设备可以通过RRC信令(如timeDomainAllocation IE)指示终端设备使用时域资源分配列表中的哪一个表项进行时域资源分配(也就是确定重复传输资源)。
S402，终端设备根据确定的表项确定重复传输资源。
一些实施例中，终端设备可以根据该表项确定重复传输方式，确定重复传输过程中每个TO的位置。具体来说，若该表项用于配置基于时隙的重复传输的资源，即该表项用于指示基于时隙的重复传输，终端设备可以确定多个连续时隙中每个时隙最多包括一次TO，不同TO在各自时隙中的位置完全相同，该多个时隙的数量可以等于重复传输的次数。若该表项用于配置基于迷你时隙的重复传输的资源，即该表项用于指示基于迷你时隙的重复传输，终端设备可以确定一个slot内可以包括多个TO。
一种示例性说明中，重复传输方式为基于时隙的重复传输时，终端设备可以根据表项中的SLIV确定每个TO，每个TO的起始符号根据SLIV中的S确定，符号数根据SLIV中的L确定。
当重复传输方式为基于迷你时隙的重复传输时，终端设备确定在一个时隙内可以包含用多个TO，该多个TO在时域可以连续也可以不连续，该多个TO的时频资源的大小可以相同也可以不同。例如，终端设备可以根据SLIV确定第一个TO，该第一个TO的起始符号根据SLIV中的S确定，符号数根据SLIV中的L确定，第N+1(N>＝1)个TO的起始符号可以为第N个TO的下一个符号。如果第N+1个TO的起始符号所在的时隙内自该起始符号起剩余的符号的数量不足L时，第N+1个TO可以终止于该时隙的最后一个符号，如果第N+1个TO的起始符号所在的时隙内剩余的符号不少于L，则第N+1个时域资源包含的符号数也为L。
为了便于理解，以表1所示的时域资源分配列表为例进行说明，其中，当repetition  scheme取值为type1时，代表基于时隙的重复传输方式，当repetition scheme取值为type2时，代表基于迷你时隙的重复传输方式。对于type A，Front-load DMRS位于每个时隙中第3个OFDM符号(即符号2)，对于type B，Front-load DMRS位于每次PUSCH的第1个OFDM符号。如图5所示，若终端设备确定使用索引为3的表项时，终端设备可以确定重复传输的方式为基于时隙的重复传输，并且，Front-load DMRS位于K个连续时隙的每个时隙的符号2上，其中，K为重复传输的次数，假设K等于4。首个重复传输资源相对于用于调度该重复传输资源的PDCCH的时域偏置为j，用于重复传输的中4个TO分别位于每个时隙的符号0到符号3共4个符号。从而，终端设备可以分别在每个时隙的符号0到符号3上进行数据包的一次传输。
如图6所示，若终端设备确定使用索引为5的表项时，终端设备可以确定重复传输的方式为基于迷你时隙的重复传输，并且，Front-load DMRS位于每次PUSCH传输的第一个符号上，其中，K为重复传输的次数，假设K等于4。首个重复传输资源(或者首个重复传输资源的起始符号或者首个重复传输资源所在的时隙或子帧或帧)相对于用于调度该重复传输资源的PDCCH(或者PDCCH的起始符号或终止符号，或者PDCCH所在的时隙或子帧或帧)的时域偏置为j，用于重复传输的第一个TO位于第一个时隙的符号4到符号7共4个符号，第二个TO位于第一个时隙的符号8到符号11共4个符号，第三个TO位于第一个时隙的符号12到符号13共2个符号，第四个TO位于第二个时隙的符号0～1共2个符号，第五个TO位于第二个时隙的符号0到符号3共4个符号，其中，由于第三次重复传输时用于重复传输的资源(即第一个时隙的符号12～13以及第二个时隙的符号0～1)跨越两个时隙，第三次重复传输被时隙边界打断，第三次重复传输的资源分为第三个TO和第四个TO。从图6中可以看出，5个TO的前三个TO都位于同一个时隙内。从而，终端设备可以在第一个时隙的符号4到符号7、符号8到符号11、符号12到符号13、第二个时隙的符号0到符号1、第二个时隙的符号2～符号5上分别进行数据包的一次传输。
在具体实施中，终端设备在时域资源分配列表中确定至少一个表项之前，可以在多个时域资源分配列表中确定所使用的时域资源分配列表。
一种实现方式中，该多个时域资源分配列表可以是网络设备通过高层信令为终端设备配置的，示例性的，高层信令可以是RRC信令。即，网络设备可以通过RRC信令为终端配置一个或多个时域资源分配列表，终端设备接收网络设备发送时域资源分配列表的配置信息。其中，该多个时域资源分配列表中至少一个时域资源分配列表符合本文步骤S401描述的时域资源分配列表的特征，即每个表项可以配置基于时隙的重复传输和基于迷你时隙的重复传输中的一种重复传输类型的资源，表项中存在可以指示重复传输的类型的参数或者表项与重复传输类型关联。
示例性的，符合本文步骤S401描述的时域资源分配列表的特征的时域资源分配列表可以通过高层参数TimeDomainResourceAllocationList-r16IE(Information Element)进行配置，例如，符合本文步骤S401描述的时域资源分配列表的特征的上行时域资源分配列表可以通过高层参数PUSCH-TimeDomainResourceAllocationList-r16进行配置。其他不符合(或者不完全符合)本文步骤S401描述的时域资源分配列表的特征的时域资源分配列表可以通过其他高层参数进行配置，例如，5G NR Release15的标准版本中的上行时域资源分配列表由高层参数PUSCH-TimeDomainResourceAllocationList IE配置。
例如，网络设备可以分别通过PUSCH-TimeDomainResourceAllocationList和 PUSCH-TimeDomainResourceAllocationList-r16为终端设备配置两个上行时域资源分配列表，其中，通过PUSCH-TimeDomainResourceAllocationList-r16配置的时域资源分配列表可以符合本文步骤S401描述的时域资源分配列表的特征。
一种示例性说明中，PUSCH-TimeDomainResourceAllocationList-r16具体可以如下：
Figure PCTCN2019101022-appb-000003
其中，PUSCH-TimeDomainResourceAllocationList-r16用于配置符合本文步骤S401描述的时域资源分配列表的特征的时域资源分配列表，其中，配置的时域资源分配列表包括最多16个表项，PUSCH-TimeDomainResourceAllocation-r16用于配置每个表项PUSCH-TimeDomainResourceAllocation-r16，在每个表项中，k2用于配置PUSCH传输的时域资源位置相对于用于调度该PUSCH传输的PDCCH的时域偏置。mappingType用于配置PUSCH传输的映射类型，startSymbolAndLength用于配置时域资源的起始符号和长度指示值，repetitionScheme用于配置重复传输方式(或者称为重复传输类型)。可以理解的是，每个表项中还可以包含其他类型的参数。
另一种实现方式中，该多个时域资源分配列表可以是预定义的。当网络设备没有通过高层信令为终端设备配置时域资源分配列表时，终端设备可以使用预定义的时域资源分配列表。通过预定义的方式为终端设备配置一个或多个时域资源分配列表中，至少有一个时域资源分配列表符合本文步骤S401描述的时域资源分配列表的特征，即每个表项可以配置基于时隙的重复传输和基于迷你时隙的重复传输中的一种重复传输类型的资源，表项中可以指示重复传输的类型的信息或者表项与重复传输的类型关联。例如预定义的时域资源列表A和时域资源列表B，其中，时域资源列表B可以符合本文步骤S401描述的时域资源分配列表的特征，例如时域资源列表B的表项中包含用于指示重复传输方式的指示信息。
进一步的，当网络设备为终端设备配置多个时域资源分配列表，或者预定义多个时域资源分配列表时，终端设备可以在多个时域资源分配列表中确定所使用的时域资源分配列表。
一种可能的实施方式中，终端设备可以在网络设备的指示下确定要使用哪一个时域资源分配列表。
一种实现方式中，网络设备可以通过显式的指示信息指示终端设备使用哪个时域资源分配列表，该指示信息可以携带在RRC信令或DCI信令或MAC CE信令中下发给终端。示例性的，当配置两个时域资源分配列表时，网络设备可以通过RRC信令或DCI信令或MAC CE信令的一个比特来指示终端设备使用哪个时域资源分配列表。例如，当该比特取值为1时，可以指示终端设备使用第一个时域资源分配列表，当该比特取值为0时，指示终端设备使用第二个时域资源分配列表。或者，当该比特取值为0时，可以指示终端设备使用第 一个时域资源分配列表，当该比特取值为1时，指示终端设备使用第二个时域资源分配列表。
另一种实现方式中，网络设备还可以通过隐式的方式指示终端设备使用哪个列表，例如网络设备可以使用PDCCH的发送属性来指示终端设备使用哪个列表，这里的PDCCH是指用于发送DCI的PDCCH，该DCI用于调度PUSCH或PDSCH，其发送属性可以是指加扰DCI的CRC的RNTI类型、或者该PDCCH所在的CORESET类型、或者该PDCCH所在的搜索空间类型等，例如不同的RNTI类型、不同的CORESET类型、不同的搜索空间类型可以代表不同的列表。
可选的，当网络设备仅为终端设备配置一个时域资源分配列表，或者预定义一个时域资源分配列表时，终端设备可以默认使用该时域资源分配列表。
本申请实施例中，时域资源分配列表的表项中可以存在指示重复传输的方式的信息或者与重复传输方式关联，当终端设备确定使用的表项时，终端设备可以根据该表项相应的重复传输方式执行重复传输(或确定时域资源)。不论是动态授权的传输还是免授权传输或半静态调度(semi-persistent scheduling，SPS)传输，终端都需要确定使用时域资源分配列表中的哪个表项，因此，本申请实施例所给出的确定重复传输资源的方法可以适用于各种传输场景。另外，本申请实施例中，时域资源分配列表的表项除了可以指示重复传输的方式，还可以指示SLIV等信息，可见，重复传输方式与SLIV等信息通过联合编码(joint coding)的方式进行指示，因此，可以不需要额外的信令开销，从而可以节省信令开销，并且，可以降低对调度的限制，并且可以不增加终端设备对PDCCH盲检测的复杂度。
实施例二：
参见图7，为本申请提供的确定重复传输资源的方法的流程图，该方法可以应用于终端设备，也可以应用于终端设备中的芯片或者芯片组，下面以应用于终端设备为例进行说明，该方法包括：
S701，终端设备在多个时域资源分配列表中确定一个时域资源分配列表，多个时域资源分配列表包括至少一个第一类列表和至少一个第二类列表，第一类列表用于配置第一类型重复传输的资源，第二类列表用于配置第二类型重复传输的资源。
其中，第一类列表中的表项可以全部用于配置第一类型重复传输的资源，也可以部分用于配置第一类型重复传输的资源。进一步的，若第一类列表中的表项部分用于配置第一类型重复传输的资源，则该第一类列表中的其他表项可以用于配置普通传输的资源。第二类列表中的表项可以全部用于配置第二类型重复传输的资源，也可以部分用于配置第二类型重复传输的资源。进一步的，若第二类列表中的表项部分用于配置第二类型重复传输的资源，则该第二类列表中的其他表项可以用于配置普通传输的资源，这里“普通传输”可以理解为不采用重复传输方式的传输。可以理解的是，时隙聚合传输实质上也是一种重复传输。
一种示例性说明中，重复传输类型可以有两种，一种是基于时隙的重复传输，即一个时隙中最多只有一个数据包的一次传输，另一种是基于迷你时隙的重复传输，即一个时隙中可以有一个数据包的多次重复传输。本申请实施例对一个时隙内一个数据包的多次重复传输的相对位置以及每次重复传输所占用的时域资源大小不做限定，例如不同次的重复传输可以在时间上连续也可以是不连续，不同次的重复传输所使用的时域资源的大小可以相同，也可以不同。其中，重复传输中，用于传输数据包的时域资源可称之为TO，为了方便 描述，下面用一个TO来表示用于一次传输的时域资源。
应理解，这里重复传输类型仅为示例性说明，本申请实施例中重复传输类型并不仅限于基于时隙的重复传输和基于迷你时隙的重复传输，若未来通信发展中出现其他重复传输类型，也可以通过本申请类似的方法进行指示。并且，本申请实施例中不仅限于两种重复传输类型，在具体实施中，重复传输类型也可以有更多(如三种或四种或五种或……)，以三种为例，多个时域资源分配列表包括至少一个第一类列表和至少一个第二类列表和至少一个第三类列表，第一类列表用于配置第一类型重复传输的资源，第二类列表用于配置第二类型重复传输的资源，第三类列表用于配置第三类型重复传输的资源。
为了描述上的方便，下面将第一传输类型为基于时隙的重复传输，第二重复传输类型为基于迷你时隙的重复传输。
具体实施中，时域资源分配列表中的每个表项可以包含用于指示SLIV的信息。每个表项还可以包含如下一种或多种信息：时域偏置、mapping type、重复传输次数K、冗余版本(redundancy version，RV)等等。其中，指示SLIV的信息可以包括起始符号S和长度L，其中，起始符号S用于在重复传输中用于确定首次传输的TO的起始符号，长度L用于在重复传输中用于确定TO的符号数。时域偏置K 2可以用于指示PUSCH传输的时域资源位置相对于用于调度该PUSCH传输的PDCCH的时域偏置。mapping type可以用于指示PUSCH传输的映射类型，如typeA或typeB，typeA和typeB的区别在于，前置(Front-load)DMRS的时域位置不同，例如，对于type A，Front-load DMRS位于每个时隙中第3个OFDM符号，或第3和第4共两个OFDM符号，对于type B，Front-load DMRS位于每次PUSCH的第1个OFDM符号，或第1和第2共两个OFDM符号。重复传输次数K，用于指示重复传输(接收或发送)一个数据包的最大次数。
其中，时域资源分配列表可以包括至少一行，例如，时域资源分配列表可以包括16行，每一行可以看做是一个表项。时域资源分配列表可以包括至少一列，例如，时域资源分配列表可以包括4列，其中，每一列可以表示一种信息。例如，第一列可以表示起始符号S，第二列可以表示长度L，第三列可以表示mapping type，等等。如表4所示。
表4
Figure PCTCN2019101022-appb-000004
Figure PCTCN2019101022-appb-000005
一种实现方式中，PUSCH的子载波间隔可以等于2 μ×15kHz，j的值可以与用于确定PUSCH的子载波间隔的参数(μ)有关，例如，如上述表2所示，当μ取值为0或1时，j可以等于1，μ取值为2时，j可以等于2。
一些实施例中，终端设备可以在网络设备的指示下确定要使用哪一个时域资源分配列表。
一种实现方式中，网络设备可以通过显式的指示信息指示终端设备使用哪个时域资源分配列表，该指示信息可以携带在RRC信令或DCI信令或MAC CE信令中下发给终端。示例性的，当配置两个时域资源分配列表时，网络设备可以通过RRC信令或DCI信令或MAC CE信令的一个比特来指示终端设备使用哪个时域资源分配列表。例如，当该比特取值为1时，可以指示终端设备使用第一个时域资源分配列表，当该比特取值为0时，指示终端设备使用第二个时域资源分配列表。或者，当该比特取值为0时，可以指示终端设备使用第一个时域资源分配列表，当该比特取值为1时，指示终端设备使用第二个时域资源分配列表。
另一种实现方式中，网络设备还可以通过隐式的方式指示终端设备使用哪个列表，例如网络设备可以使用PDCCH的发送属性来指示终端设备使用哪个列表，这里的PDCCH是指用于发送DCI的PDCCH，该DCI用于调度PUSCH或PDSCH，其发送属性可以是指加扰DCI的CRC的RNTI类型、或者该PDCCH所在的CORESET类型、或者该PDCCH所在的搜索空间类型等，例如不同的RNTI类型、不同的CORESET类型、不同的搜索空间类型可以代表不同的列表。
一些实施例中，若终端设备有默认使用的时域资源分配列表，终端设备可以使用该时域资源分配列表。当终端设备接收到网络设备指示的时域资源分配列表时，终端设备可以使用指示的时域资源分配列表。
S702，终端设备根据确定的时域资源分配列表确定重复传输的时域资源。
一些实施例中，终端设备可以根据使用的时域资源分配列表来确定重复传输方式，也就是确定重复传输过程中每个TO的位置。具体来说，若该时域资源分配列表是第一类列表，也就是该时域资源分配列表对应基于时隙的重复传输，终端设备可以确定多个连续时隙中每个时隙最多包括一次TO，且不同TO在各自时隙中的位置完全相同，该多个时隙的数量可以等于重复传输的次数。若该时域资源分配列表是第二类列表，也就是该时域资源分配列表对应基于迷你时隙的重复传输，终端设备可以确定一个slot内可以包括多个TO。
一种示例性说明中，重复传输方式为基于时隙的重复传输时，终端设备可以根据表项中的SLIV确定每个TO，每个TO的起始符号根据SLIV中的S确定，符号数根据SLIV中的L确定。
当重复传输方式为基于迷你时隙的重复传输时，终端设备确定在一个时隙内可以包含用多个TO，该多个TO在时域可以连续也可以不连续，该多个TO的时频资源的大小可以相同也可以不同。例如，终端设备可以根据SLIV确定第一个TO，该第一个TO的起始符号根 据SLIV中的S确定，符号数根据SLIV中的L确定，第N+1(N>＝1)个TO的起始符号可以为第N个TO的下一个符号。如果第N+1个TO的起始符号所在的时隙内自该起始符号起剩余的符号的数量不足L时，第N+1个TO可以终止于该时隙的最后一个符号，如果第N+1个TO的起始符号所在的时隙内剩余的符号不少于L，则第N+1个时域资源包含的符号数也为L。
为了便于理解，以表4所示时域资源分配列表为例进行说明，其中，对于type A，Front-load DMRS位于每个时隙中第3个OFDM符号(即符号2)，对于type B，Front-load DMRS位于每次PUSCH的第1个OFDM符号。如图5所示，若表4所示的时域资源分配列表对应基于时隙的重复传输时，终端设备可以确定重复传输的方式为基于时隙的重复传输。以表4中的表项3为例，终端设备可以确定Front-load DMRS位于K个连续时隙的每个时隙的符号2上，其中，K为重复传输的次数，假设K等于4。首个重复传输资源相对于用于调度该重复传输资源的PDCCH的时域偏置为j，用于重复传输的4个TO分别位于每个时隙的符号0到符号3共4个符号。从而，终端设备可以分别在每个时隙的符号0到符号3上进行数据包的一次传输。
如图6所示，若表4所示的时域资源分配列表对应基于迷你时隙的重复传输时，终端设备可以确定重复传输的方式为基于迷你时隙的重复传输。以表4中的表项5为例，终端设备可以确定Front-load DMRS位于K个连续时隙的每次PUSCH传输的第一个符号上，其中，K为重复传输的次数，假设K等于4。首个重复传输资源(或者首个重复传输资源的起始符号或者首个重复传输资源所在的时隙或子帧或帧)相对于用于调度该重复传输资源的PDCCH(或者PDCCH的起始符号或终止符号，或者PDCCH所在的时隙或子帧或帧)的时域偏置为j，用于重复传输的第一个TO位于第一个时隙的符号4到符号7共4个符号，第二个TO位于第一个时隙的符号8到符号11共4个符号，第三个TO位于第一个时隙的符号12到符号13共2个符号，第四个TO位于第二个时隙的符号0～1共2个符号，第五个TO位于第二个时隙的符号2到符号5共4个符号，第三次重复传输被时隙边界打断，第三次重复传输的资源分为第三个TO和第四个TO。从图6中可以看出，5个TO的前三个TO都位于同一个时隙内。从而，终端设备可以在第一个时隙的符号4到符号7、符号8到符号11、符号12到符号13、第二个时隙的符号0到符号1、以及第二个时隙的符号2到符号5上分别进行数据包的一次传输。
一种实现方式中，该多个时域资源分配列表可以是网络设备通过高层信令为终端设备配置的，示例性的，高层信令可以是RRC信令。即，网络设备可以通过RRC信令为终端配置一个或多个时域资源分配列表，终端设备接收网络设备发送时域资源分配列表的配置信息。其中，该多个时域资源分配列表中至少一个时域资源分配列表对应基于时隙的重复传输(即包括至少一个第一类列表)，至少一个时域资源分配列表对应基于迷你时隙的重复传输(即包括至少一个第二类列表)。
示例性的，对应基于迷你时隙的重复传输的时域资源分配列表可以通过高层参数TimeDomainResourceAllocationList-r16进行配置，例如，对应基于迷你时隙的重复传输的上行时域资源分配列表可以通过高层参数PUSCH-TimeDomainResourceAllocationList-r16进行配置。对应基于时隙的重复传输的时域资源分配列表可以通过其他高层参数进行配置，例如，Release15版本中的上行时域资源分配列表由高层参数PUSCH-TimeDomainResourceAllocationList IE配置。
例如，网络设备可以分别通过PUSCH-TimeDomainResourceAllocationList和PUSCH-TimeDomainResourceAllocationList-r16为终端设备配置两个上行时域资源分配列 表，其中，通过PUSCH-TimeDomainResourceAllocationList-r16配置的时域资源分配列表可以符合本文步骤S401描述的时域资源分配列表的特征。
另一种实现方式中，该多个时域资源分配列表可以是预定义的。当网络设备没有通过高层信令为终端设备配置时域资源分配列表时，终端设备可以使用预定义的时域资源分配列表。通过预定义的方式为终端设备配置一个或多个时域资源分配列表中至少一个时域资源分配列表对应基于时隙的重复传输(即包括至少一个第一类列表)，至少一个时域资源分配列表对应基于迷你时隙的重复传输(即包括至少一个第二类列表)。
本申请实施例中，通过将时域资源分配列表与重复传输的方式进行关联，当终端设备确定使用的时域资源分配列表时，终端设备可以根据该时域资源分配列表相应的重复传输方式执行重复传输(或确定时域资源)。不论是动态授权的传输还是免授权传输或半静态调度(semi-persistent scheduling，SPS)传输，终端都需要确定使用哪个时域资源分配列表，因此，本申请实施例所给出的确定重复传输资源的方法可以适用于各种传输场景。另外，本申请实施例中，时域资源分配列表除了可以指示重复传输的方式，还可以指示SLIV等信息，可见，重复传输方式与SLIV等信息通过联合编码(joint coding)的方式进行指示，因此，可以不需要额外的信令开销，从而可以节省信令开销，并且，可以降低对调度的限制，并且可以不增加终端设备对PDCCH盲检测的复杂度。
需要说明的是，本申请实施例中基于迷你时隙的重复传输中，相邻两个TO可以在时域上可以连续，也可以间隔一个或多个符号，本申请不做具体限定。
基于与方法实施例的同一发明构思，本申请实施例提供一种确定重复传输资源的装置。确定重复传输资源的装置具体可以用于实现图4至图7的实施例中终端设备执行的方法，该装置可以是终端设备本身，也可以是终端设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。该确定重复传输资源的装置的结构可以如图8所示，包括处理单元801以及收发单元802。其中，收发单元802用于向处理单元传输数据和/或代码指令等。处理单元，用于通过调用收发单元传输的代码指令执行：在时域资源分配列表中确定至少一个表项，时域资源分配列表中的每个表项用于配置第一类型重复传输和第二类型重复传输中的一种重复传输类型的资源；根据表项确定重复传输资源。
一种示例，表项可以包括用于指示重复传输类型的信息。
另一种示例，表项包括用于指示重复传输类型的信息时，表项可以用于配置第一类型重复传输的时域资源，表项未包括用于指示重复传输类型的信息时，表项用于配置第二类型重复传输的时域资源。或者，表项包括用于指示重复传输类型的信息时，表项可以用于配置第二类型重复传输的时域资源，表项未包括用于指示重复传输类型的信息时，表项用于配置第一类型重复传输的时域资源。
一些实施例中，收发单元802，还可以用于接收网络设备发送时域资源分配列表的配置信息。
另一些实施例中，处理单元801，在时域资源分配列表中确定至少一个表项之前，还可以用于：在多个时域资源分配列表中确定时域资源分配列表。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。可以理解的是， 本申请实施例中各个模块的功能或者实现可以进一步参考方法实施例的相关描述。
一种可能的方式中，确定重复传输资源的装置可以如图9所示，该装置可以是终端设备或者终端设备中的芯片。该装置可以包括处理器901，通信接口902，存储器903。其中，处理单元801可以为处理器901。收发单元802可以为通信接口902。
处理器901，可以是一个中央处理单元(central processing unit，CPU)，或者为数字处理单元等等。通信接口902可以是收发器、也可以为接口电路如收发电路等、也可以为收发芯片等等。该装置还包括：存储器903，用于存储处理器901执行的程序。存储器903可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器903是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
处理器901用于执行存储器903存储的程序代码，具体用于执行上述处理单元801的动作，本申请在此不再赘述。通信接口902具体用于执行上述收发单元802的动作，本申请在此不再赘述。
本申请实施例中不限定上述通信接口902、处理器901以及存储器903之间的具体连接介质。本申请实施例在图9中以存储器903、处理器901以及通信接口902之间通过总线904连接，总线在图9中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本发明实施例还提供了一种计算机可读存储介质，用于存储为执行上述处理器所需执行的计算机软件指令，其包含用于执行上述处理器所需执行的程序。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如SSD)等。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (17)

  1. 一种确定重复传输资源的方法，其特征在于，所述方法包括：
    终端设备在时域资源分配列表中确定至少一个表项，所述时域资源分配列表中的每个表项用于配置第一类型重复传输和第二类型重复传输中的一种重复传输类型的资源；
    所述终端设备根据所述表项确定重复传输资源。
  2. 如权利要求1所述的方法，其特征在于，所述表项包括用于指示重复传输类型的信息。
  3. 如权利要求1所述的方法，其特征在于，所述表项包括用于指示重复传输类型的信息时，所述表项用于配置所述第一类型重复传输的时域资源，所述表项未包括用于指示重复传输类型的信息时，所述表项用于配置所述第二类型重复传输的时域资源；或者
    所述表项包括用于指示重复传输类型的信息时，所述表项用于配置所述第二类型重复传输的时域资源，所述表项未包括用于指示重复传输类型的信息时，所述表项用于配置所述第一类型重复传输的时域资源。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收网络设备发送所述时域资源分配列表的配置信息。
  5. 如权利要求1至4任一项所述的方法，其特征在于，在终端设备在时域资源分配列表中确定至少一个表项之前，所述方法还包括：
    终端设备在多个时域资源分配列表中确定所述时域资源分配列表。
  6. 一种确定重复传输资源的装置，其特征在于，所述装置包括：
    存储器，用于存储代码指令；
    处理器，用于调用所述存储器存储的代码指令执行：
    在时域资源分配列表中确定至少一个表项，所述时域资源分配列表中的每个表项用于配置第一类型重复传输和第二类型重复传输中的一种重复传输类型的资源；
    根据所述表项确定重复传输资源。
  7. 如权利要求6所述的装置，其特征在于，所述表项包括用于指示重复传输类型的信息。
  8. 如权利要求6所述的装置，其特征在于，所述表项包括用于指示重复传输类型的信息时，所述表项用于配置所述第一类型重复传输的时域资源，所述表项未包括用于指示重复传输类型的信息时，所述表项用于配置所述第二类型重复传输的时域资源；或者
    所述表项包括用于指示重复传输类型的信息时，所述表项用于配置所述第二类型重复传输的时域资源，所述表项未包括用于指示重复传输类型的信息时，所述表项用于配置所述第一类型重复传输的时域资源。
  9. 如权利要求6至8任一项所述的装置，其特征在于，所述装置还包括收发器；
    所述收发器，用于接收网络设备发送所述时域资源分配列表的配置信息。
  10. 如权利要求6至9任一项所述的装置，其特征在于，所述处理器，在时域资源分配列表中确定至少一个表项之前，还用于：
    在多个时域资源分配列表中确定所述时域资源分配列表。
  11. 一种芯片，其特征在于，所述芯片包括通信接口以及处理器；
    所述通信接口，用于接收代码指令，并传输到所述处理器；
    所述处理器，用于调用所述通信接口传输的代码指令以执行：
    在时域资源分配列表中确定至少一个表项，所述时域资源分配列表中的每个表项用于配置第一类型重复传输和第二类型重复传输中的一种重复传输类型的资源；
    根据所述表项确定重复传输资源。
  12. 如权利要求11所述的芯片，其特征在于，所述表项包括用于指示重复传输类型的信息。
  13. 如权利要求11所述的芯片，其特征在于，所述表项包括用于指示重复传输类型的信息时，所述表项用于配置所述第一类型重复传输的时域资源，所述表项未包括用于指示重复传输类型的信息时，所述表项用于配置所述第二类型重复传输的时域资源；或者
    所述表项包括用于指示重复传输类型的信息时，所述表项用于配置所述第二类型重复传输的时域资源，所述表项未包括用于指示重复传输类型的信息时，所述表项用于配置所述第一类型重复传输的时域资源。
  14. 如权利要求11至13任一项所述的芯片，其特征在于，所述通信接口，还用于接收网络设备发送所述时域资源分配列表的配置信息。
  15. 如权利要求11至14任一项所述的芯片，其特征在于，所述处理器，在时域资源分配列表中确定至少一个表项之前，还用于：
    在多个时域资源分配列表中确定所述时域资源分配列表。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储程序或指令，所述程序或所述指令在被一个或多个处理器读取并执行时可实现权利要求1至5任一项所述的方法。
  17. 一种计算机程序产品，其特征在于，当所述计算机程序产品在终端设备上运行时，使得所述终端设备执行权利要求1至5任一所述的方法。
PCT/CN2019/101022 2019-08-16 2019-08-16 一种确定重复传输资源的方法及装置 WO2021030943A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/101022 WO2021030943A1 (zh) 2019-08-16 2019-08-16 一种确定重复传输资源的方法及装置
CN201980099302.XA CN114223165B (zh) 2019-08-16 2019-08-16 一种确定重复传输资源的方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/101022 WO2021030943A1 (zh) 2019-08-16 2019-08-16 一种确定重复传输资源的方法及装置

Publications (1)

Publication Number Publication Date
WO2021030943A1 true WO2021030943A1 (zh) 2021-02-25

Family

ID=74659507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/101022 WO2021030943A1 (zh) 2019-08-16 2019-08-16 一种确定重复传输资源的方法及装置

Country Status (2)

Country Link
CN (1) CN114223165B (zh)
WO (1) WO2021030943A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115333703A (zh) * 2021-05-11 2022-11-11 维沃移动通信有限公司 Pusch重复传输方法和设备
WO2023185433A1 (zh) * 2022-03-31 2023-10-05 华为技术有限公司 通信方法和通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737045A (zh) * 2017-04-19 2018-11-02 华为技术有限公司 重复传输的方法及装置
CN109952735A (zh) * 2016-11-04 2019-06-28 三星电子株式会社 无线蜂窝通信系统中延迟减少的自适应重传方法和设备
WO2019139733A1 (en) * 2018-01-12 2019-07-18 At&T Intellectual Property I, L.P. Improving uplink coverage for 5g or other next generation network using multi-slot frequency hopping
CN110392433A (zh) * 2018-04-20 2019-10-29 电信科学技术研究院有限公司 一种数据传输方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7826438B1 (en) * 2004-04-26 2010-11-02 Marvell International Ltd. Circuits, architectures, systems, methods, algorithms and software for reducing contention and/or handling channel access in a network
CN107197528B (zh) * 2016-03-14 2020-12-25 华为技术有限公司 一种资源调度和分配的方法和装置
CN108307517B (zh) * 2017-01-12 2020-01-07 维沃移动通信有限公司 一种资源调度指示方法、网络设备及终端设备
KR102536946B1 (ko) * 2017-09-21 2023-05-25 삼성전자주식회사 무선통신 시스템에서 제어 정보 송수신 방법 및 장치
CN117651335A (zh) * 2017-09-30 2024-03-05 华为技术有限公司 信息传输方法和装置
KR20200086667A (ko) * 2017-11-10 2020-07-17 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 Harq 번호 결정 방법, 네트워크 장치, 단말 및 컴퓨터 저장 매체
CN110035529B (zh) * 2018-01-12 2021-07-16 华为技术有限公司 一种资源配置的方法和通信装置
US11025456B2 (en) * 2018-01-12 2021-06-01 Apple Inc. Time domain resource allocation for mobile communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109952735A (zh) * 2016-11-04 2019-06-28 三星电子株式会社 无线蜂窝通信系统中延迟减少的自适应重传方法和设备
CN108737045A (zh) * 2017-04-19 2018-11-02 华为技术有限公司 重复传输的方法及装置
WO2019139733A1 (en) * 2018-01-12 2019-07-18 At&T Intellectual Property I, L.P. Improving uplink coverage for 5g or other next generation network using multi-slot frequency hopping
CN110392433A (zh) * 2018-04-20 2019-10-29 电信科学技术研究院有限公司 一种数据传输方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; User Equipment (UE) radio access capabilities (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.306, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V15.0.0, 4 January 2018 (2018-01-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 14, XP051392361 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115333703A (zh) * 2021-05-11 2022-11-11 维沃移动通信有限公司 Pusch重复传输方法和设备
WO2023185433A1 (zh) * 2022-03-31 2023-10-05 华为技术有限公司 通信方法和通信装置

Also Published As

Publication number Publication date
CN114223165B (zh) 2023-09-01
CN114223165A (zh) 2022-03-22

Similar Documents

Publication Publication Date Title
WO2020143750A1 (zh) 侧行参考信号的传输方法和通信装置
WO2019214596A1 (zh) 参数确定的方法、监控方法、通信装置
TWI713402B (zh) 業務傳輸的方法和裝置
WO2022028311A1 (zh) 一种物理下行控制信道增强方法、通信装置及系统
WO2018202059A1 (zh) 传输控制信道的方法、网络设备、网络控制器和终端设备
WO2018228500A1 (zh) 一种调度信息传输方法及装置
WO2019192345A1 (zh) 一种时域资源分配方法及装置
WO2020029858A1 (zh) 一种信息传输方法和装置
WO2020200035A1 (zh) 传输上行控制信息的方法及装置
WO2018137672A1 (zh) 下行控制信息发送和接收方法及设备
WO2021164482A1 (zh) 信息接收方法、信息发送方法及设备
WO2020199854A1 (zh) 确定传输资源的方法及装置
WO2019029014A1 (zh) 通信方法、终端设备和网络设备
CN106465368A (zh) 一种子带资源确定装置及方法
WO2019080486A1 (zh) 控制信息的处理方法及系统、第一设备、第二设备
WO2021027947A1 (zh) 一种通信方法及装置
WO2020164639A1 (zh) 一种随机接入方法、设备及系统
WO2019047632A1 (zh) 用于传输下行数据的资源的确定和配置方法、终端和基站
WO2020030025A1 (zh) 用于上报csi的方法和装置
WO2020200176A1 (zh) 确定传输资源的方法及装置
WO2021030943A1 (zh) 一种确定重复传输资源的方法及装置
WO2019062151A1 (zh) 一种资源指示方法、通信装置及网络设备
WO2021088028A1 (zh) 一种资源配置方法及装置
WO2021228252A1 (zh) 一种缓存确定方法及装置
WO2019137011A1 (zh) 一种通信方法及上行资源确定方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19941829

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19941829

Country of ref document: EP

Kind code of ref document: A1