WO2022017301A1 - 用于非授权频段的pusch重复传输调度方法及装置、存储介质、终端 - Google Patents

用于非授权频段的pusch重复传输调度方法及装置、存储介质、终端 Download PDF

Info

Publication number
WO2022017301A1
WO2022017301A1 PCT/CN2021/106976 CN2021106976W WO2022017301A1 WO 2022017301 A1 WO2022017301 A1 WO 2022017301A1 CN 2021106976 W CN2021106976 W CN 2021106976W WO 2022017301 A1 WO2022017301 A1 WO 2022017301A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduled
pusch
scheduled pusch
dci
time domain
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2021/106976
Other languages
English (en)
French (fr)
Inventor
周欢
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Ziguang Zhanrui Communication Technology Co Ltd
Original Assignee
Beijing Ziguang Zhanrui Communication Technology Co Ltd
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 Beijing Ziguang Zhanrui Communication Technology Co Ltd filed Critical Beijing Ziguang Zhanrui Communication Technology Co Ltd
Publication of WO2022017301A1 publication Critical patent/WO2022017301A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a method and device, a storage medium and a terminal for PUSCH repeated transmission scheduling in an unlicensed frequency band.
  • NR New Radio
  • LBT listen before talk
  • the physical downlink data channel also known as the physical downlink shared channel, Physical Downlink Shared Channel, PDSCH for short
  • the uplink feedback channel are in different continuous occupancy time (Continuous of Time, referred to as COT).
  • the NR (NR-Unlicensed, NR-U) of the licensed spectrum supports a downlink scheduling signaling that can schedule multiple Physical Uplink Shared Channel (PUSCH) signaling at the same time, which is called a single DCI scheduling multiple PUSCH (multiple PUSCHs scheduled by a single DCI).
  • PUSCH Physical Uplink Shared Channel
  • each PUSCH has a corresponding New Data Indicator (NDI for short) field and a Redundancy Version (Redundancy Version, RV for short) field.
  • NDI New Data Indicator
  • RV Redundancy Version
  • HARQ Hybrid Automatic Repeat reQuest
  • the time domain resource allocation mechanism has an independent start and length indication value (Start and Length Indication Valve, SLIV for short) and a mapping type for each scheduled PUSCH.
  • Start and Length Indication Valve Start and Length Indication Valve
  • mapping type for each scheduled PUSCH.
  • the specific number of PUSCHs scheduled by a single DCI is directly determined by the number of valid SLIVs in a row in the Time Domain Recourse Allocation (TDRA) table notified through the DCI.
  • TDRA Time Domain Recourse Allocation
  • the prior art can schedule multiple PUSCHs through DCI in an unlicensed spectrum, it does not support a PUSCH repeated transmission mechanism.
  • the existing technical implementation that cannot support repeated PUSCH transmission obviously cannot meet the service requirements, which affects the user experience.
  • the technical problem solved by the present invention is how to realize the repeated transmission of the PUSCH in the unlicensed spectrum.
  • an embodiment of the present invention provides a PUSCH repeated transmission scheduling method for an unlicensed frequency band, including: receiving DCI, wherein the DCI schedules one or more PUSCHs, and the PUSCH scheduled by the DCI is recorded as scheduling PUSCH, and at least one of the scheduled PUSCHs is repeated transmission; the time domain starting position and length of each scheduled PUSCH are determined according to the DCI; for each scheduled PUSCH, according to the time domain starting position and length of the scheduled PUSCH, and the time domain starting position of the next scheduled PUSCH to determine the number of repeated transmissions of the scheduled PUSCH.
  • the method further includes: determining, according to the DCI, the number of repeated transmissions of the last scheduled PUSCH.
  • the determining the time domain starting position and length of each scheduled PUSCH according to the DCI includes: searching a time domain resource indication table according to the index number indicated by the DCI, so as to determine the time domain starting position of each scheduled PUSCH.
  • the time domain resource indication table includes at least one row, wherein each row indicates the time domain start position and length of at least one scheduled PUSCH, and the rows of the time domain resource indication table correspond to index numbers one-to-one.
  • each row in the time domain resource indication table further indicates the number of repeated transmissions of the last scheduled PUSCH in the at least one scheduled PUSCH corresponding to this row.
  • each row in the time domain resource indication table further indicates the respective mapping type of at least one scheduled PUSCH corresponding to this row.
  • each row indicating the time domain start position and length of the at least one scheduled PUSCH includes: each row indicating the time slot offset of the at least one scheduled PUSCH relative to the DCI or the previous scheduled PUSCH. , and the respective SLIV of the at least one scheduled PUSCH; or, each row indicates the respective slot offsets of the at least one scheduled PUSCH relative to the DCI or the previous scheduled PUSCH, and the starting point in the corresponding slot start symbol and length.
  • the scheduled PUSCH is used to carry data of the URLLC service or the eMBB service.
  • Determining the number of repeated transmissions of the scheduled PUSCH by the starting position includes: determining the number of times between the time slot where the time domain starting position of the next scheduled PUSCH is located and the time slot where the time domain starting position of the scheduling PUSCH is located.
  • the number of time slots is determined as the number of repeated transmissions of the scheduled PUSCH; wherein, the time domain position in the corresponding time slot during each repeated transmission of the scheduled PUSCH is determined according to the time domain start position and length of the scheduled PUSCH.
  • Determining the number of repeated transmissions of the scheduled PUSCH by the starting position includes: determining the number of times between the time slot where the time domain starting position of the next scheduled PUSCH is located and the time slot where the time domain starting position of the scheduling PUSCH is located. The number of symbols is divided by the length of the scheduled PUSCH to obtain the number of repeated transmissions of the scheduled PUSCH.
  • the DCI is used to trigger aperiodic CSI reporting, and the method further includes: multiplexing the aperiodic CSI in one or more scheduled PUSCHs scheduled by the DCI, and the first scheduled PUSCH on one repeated transmission; or, multiplexing the aperiodic CSI in one or more scheduled PUSCHs scheduled by the DCI, and on the second-to-last repeated transmission of the first scheduled PUSCH; or, combining the non-periodic CSI
  • the periodic CSI is multiplexed on one or more scheduled PUSCHs scheduled by the DCI, and the second-to-last scheduled PUSCH is on the first repeated transmission; or, the aperiodic CSI is multiplexed on one or more scheduled PUSCHs of the DCI scheduling.
  • the second-to-last scheduled PUSCH is repeatedly transmitted; or, the aperiodic CSI is multiplexed in one or more scheduled PUSCHs scheduled by the DCI, and the last scheduled PUSCH is On the first repeated transmission; or, multiplexing the aperiodic CSI in one or more scheduled PUSCHs scheduled by the DCI, and on the penultimate repeated transmission of the last scheduled PUSCH;
  • the periodic CSI is multiplexed on the penultimate repeated transmission in the one or more scheduled PUSCHs scheduled by the DCI; or, the aperiodic CSI is multiplexed on the one or more scheduled PUSCHs scheduled by the DCI.
  • an embodiment of the present invention further provides a PUSCH repeated transmission scheduling device for an unlicensed frequency band, including: a receiving module, configured to receive DCI, wherein the DCI schedules one or more PUSCHs, and the DCI
  • the scheduled PUSCH is denoted as scheduled PUSCH, and at least one scheduled PUSCH is repeated transmission;
  • the first determination module is used to determine the time domain starting position and length of each scheduled PUSCH according to the DCI;
  • the second determination module for each scheduled PUSCH For a scheduled PUSCH, the number of times of repeated transmission of the scheduled PUSCH is determined according to the time domain starting position and length of the scheduled PUSCH and the time domain starting position of the next scheduled PUSCH.
  • an embodiment of the present invention further provides a storage medium on which a computer program is stored, and the computer program executes the steps of the above method when the computer program is run by a processor.
  • an embodiment of the present invention further provides a terminal, including the above device, or including a memory and a processor, where the memory stores a computer program that can run on the processor, and the processor runs The computer program executes the steps of the above-described method.
  • An embodiment of the present invention provides a PUSCH repeated transmission scheduling method for an unlicensed frequency band, including: receiving DCI, wherein the DCI schedules one or more PUSCHs, denoting the PUSCH scheduled by the DCI as a scheduling PUSCH, and at least one of the The scheduled PUSCH is repeated transmission; the time domain start position and length of each scheduled PUSCH are determined according to the DCI; for each scheduled PUSCH, according to the time domain start position and length of the scheduled PUSCH, and the next scheduled PUSCH The starting position in the time domain determines the number of repeated transmissions of the scheduled PUSCH.
  • this embodiment can realize repeated transmission of PUSCH in the unlicensed frequency band, and when the PUSCH that is allowed to be repeatedly transmitted is scheduled through DCI, the number of repeated transmissions of the scheduled PUSCH can be effectively determined, which further improves the reliability of service transmission in the unlicensed frequency band. High reliability and low latency.
  • the total duration of repeatable transmission of the earlier scheduled PUSCH is determined according to the time domain starting positions of the two scheduled PUSCHs before and after, and then the number of repeated transmissions is calculated according to the length of a single transmission of the earlier scheduled PUSCH.
  • the number of repeated transmissions of the PUSCH authorized for uplink transmission this time can be quickly determined with low computational complexity.
  • the time domain position of each repeated transmission can also be determined synchronously, so as to transmit data on the scheduled PUSCH of each repeated transmission.
  • the DCI is used to trigger aperiodic CSI reporting, and the method further includes: multiplexing the aperiodic CSI in one or more scheduled PUSCHs scheduled by the DCI, and the first scheduled PUSCH for the first time On repeated transmission; or, multiplexing the aperiodic CSI in one or more scheduled PUSCHs scheduled by the DCI, and on the second-to-last repeated transmission of the first scheduled PUSCH; or, combining the aperiodic CSI Multiplexing on one or more scheduled PUSCHs scheduled by the DCI, on the first repeated transmission of the penultimate scheduled PUSCH; or multiplexing the aperiodic CSI on one or more scheduled PUSCHs scheduled by the DCI In the scheduled PUSCH, the second-to-last scheduled PUSCH is repeatedly transmitted; or, the aperiodic CSI is multiplexed in one or more scheduled PUSCHs scheduled by the DCI, and the last scheduled PUSCH is the first scheduled PUSCH.
  • the second-to-last repeated transmission or, multiplex the aperiodic CSI in one or more scheduled PUSCHs scheduled by the DCI, and on the second-to-last repeated transmission of the last scheduled PUSCH; or, combine the aperiodic CSI Multiplexing on the second-to-last repeated transmission in the one or more scheduled PUSCHs scheduled by the DCI; or, multiplexing the aperiodic CSI on the first one of the one or more scheduled PUSCHs scheduled by the DCI repeated transmissions.
  • the specific multiplexing time domain position of the aperiodic CSI on the repeated transmission PUSCH can be further determined.
  • 1 is a time domain resource allocation diagram for scheduling PUSCH in the prior art
  • FIG. 2 is a flowchart of a method for scheduling repeated PUSCH transmission in an unlicensed frequency band according to an embodiment of the present invention
  • FIG. 3 is a time domain resource allocation diagram of a typical application scenario of an embodiment of the present invention.
  • FIG. 4 is a time domain resource allocation diagram of another typical application scenario of an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a PUSCH repeated transmission scheduling apparatus for an unlicensed frequency band according to an embodiment of the present invention.
  • the DCI format for scheduling the PUSCH in the NR system includes DCI0_0, DCI0_1 and DCI0_2.
  • a time domain resource assignment (Time domain resource assignment) field may be included to notify the user equipment (User Equipment, UE for short) of the time domain resource location of the PUSCH authorized to use.
  • the DCI used to schedule the PUSCH may indicate a row index to the UE's dedicated table for time domain resources.
  • This table provides Orthogonal Frequency Division Multiplexing (OFDM) symbols for PUSCH transmission, which can include a starting OFDM symbol (denoted as S) and an allocated OFDM symbol length (denoted as L) (collectively referred to as SLIV), the time slot offset K2 between DCI and PUSCH, and the mapping type of PUSCH (Type A (Type A) or Type B (Type B)) can also be provided, as shown in Table 1.
  • OFDM Orthogonal Frequency Division Multiplexing
  • Table 1 shows the allowed symbol start positions (S) and lengths (L) under different mapping types of PUSCH.
  • the 5G URLLC technology achieves a user plane delay of 0.5 milliseconds for both uplink and downlink between the base station and the terminal.
  • the delay refers to the time it takes to successfully transmit an application-layer Internet Protocol (Internet Protocol, IP for short) data packet or message.
  • IP Internet Protocol
  • it refers to the time taken from the sender's 5G wireless protocol layer entry point, via 5G wireless transmission, to the receiver's 5G wireless protocol layer exit point.
  • the delay comes from both uplink and downlink directions.
  • the main technologies of 5G URLLC to achieve low latency include: introducing smaller time resource units, such as mini-slots; uplink access adopts a scheduling-free mechanism, and terminals can directly access the channel; supporting asynchronous processes, In order to save uplink time synchronization overhead; adopt fast automatic repeat request (HARQ) and fast dynamic scheduling.
  • HARQ fast automatic repeat request
  • the NR base station (gNB) will configure or indicate the priority of its transmission, such as high-priority or low-priority services.
  • one DCI in NR-U can schedule multiple PUSCHs at the same time.
  • the time domain resource allocation mechanism for multiple scheduled PUSCHs is that each PUSCH has an independent SLIV and a mapping type.
  • the specific number of PUSCHs scheduled by a single DCI is directly determined by the time domain resource allocation notified through the DCI. , referred to as TDRA) table (as shown in Table 2) in a row of the number of valid SLIV decision.
  • the time domain resource allocation of the three scheduled PUSCHs is shown in FIG. 1 .
  • the Physical Downlink Control Channel (PDCCH for short) is used to carry DCI, and assuming that the DCI indicates index number 0, it can be determined according to the relevant information of the row corresponding to index number 0 in Table 2,
  • the time slot offset (slot offset, denoted as K2) between the PUSCH scheduled by the DCI and the DCI is 1 time slot.
  • the DCI since the DCI is located in time slot n, it can be determined that the initial time slot in the time domain for scheduling the PUSCH is time slot n+1.
  • the time domain position of the first scheduled PUSCH is a total of 10 symbols from the 4th symbol to the 13th symbol of time slot n+1.
  • the time domain position of the third scheduled PUSCH is a total of 13 symbols from the 0th symbol to the 12th symbol of time slot n+3.
  • the starting symbol position and length of each PUSCH scheduled by the DCI, and the time slot offset of the first scheduled PUSCH relative to the DCI can be determined.
  • Multiple PUSCHs scheduled by DCI are transmitted consecutively.
  • a DCI for scheduling uplink grants can simultaneously schedule uplink data and trigger aperiodic-channel state information (Aperiodic-Channel State Information, A-CSI for short) reporting.
  • A-CSI Aperiodic-Channel State Information
  • the prior art only supports scheduling of multiple PUSCHs through DCI in an unlicensed frequency band, but does not support repeated transmission of PUSCHs.
  • services such as Ultra-reliable and Low Latency Communications (Ultra-reliable and Low Latency Communications, URLLC) and Enhanced Mobile Broadband (eMBB) services transmitted through unlicensed frequency bands, reliability and latency
  • URLLC Ultra-reliable and Low Latency Communications
  • eMBB Enhanced Mobile Broadband
  • an embodiment of the present invention provides a PUSCH repeated transmission scheduling method for an unlicensed frequency band, including: receiving DCI, wherein the DCI schedules one or more PUSCHs, and the PUSCH scheduled by the DCI is recorded as scheduling PUSCH, and at least one of the scheduled PUSCHs is repeated transmission; the time domain starting position and length of each scheduled PUSCH are determined according to the DCI; for each scheduled PUSCH, according to the time domain starting position and length of the scheduled PUSCH, and the time domain starting position of the next scheduled PUSCH to determine the number of repeated transmissions of the scheduled PUSCH.
  • this embodiment can realize repeated transmission of PUSCH in the unlicensed frequency band, and when the PUSCH that is allowed to be repeatedly transmitted is scheduled through DCI, the number of repeated transmissions of the scheduled PUSCH can be effectively determined, which further improves the reliability of service transmission in the unlicensed frequency band. High reliability and low latency.
  • the total duration of repeatable transmission of the earlier scheduled PUSCH is determined according to the time domain starting positions of the two scheduled PUSCHs before and after, and then the number of repeated transmissions is calculated according to the length of a single transmission of the earlier scheduled PUSCH.
  • the number of repeated transmissions of the PUSCH authorized for uplink transmission this time can be quickly determined with low computational complexity.
  • the time domain position of each repeated transmission can also be determined synchronously, so as to transmit data on the scheduled PUSCH of each repeated transmission.
  • FIG. 2 is a flowchart of a method for scheduling repeated PUSCH transmission in an unlicensed frequency band according to an embodiment of the present invention.
  • this embodiment can be applied to a scenario of unlicensed spectrum and continuous scheduling of multiple PUSCHs. Further, the PUSCH repeated transmission scheduled in this embodiment can be used to carry data of URLLC services, eMBB services, and other services with high reliability and low latency requirements transmitted in unlicensed frequency bands.
  • This embodiment can introduce a PUSCH repeated transmission mechanism and an aperiodic CSI multiplexing mechanism based on PUSCH repeated transmission based on the mechanism of scheduling multiple PUSCH grants through a single DCI.
  • the PUSCH repeated transmission scheduling method for an unlicensed frequency band provided by the following steps S201 to S203 can be executed by a chip with a data transmission function in the user equipment, or can be executed by a baseband chip in the user equipment. .
  • the method for scheduling repeated PUSCH transmission in an unlicensed frequency band described in this embodiment may include the following steps:
  • Step S201 receiving DCI, wherein the DCI schedules one or more PUSCHs, denoting the PUSCH scheduled by the DCI as a scheduled PUSCH, and at least one of the scheduled PUSCHs is repeated transmission;
  • Step S202 determining the time domain starting position and length of each scheduled PUSCH according to the DCI
  • Step S203 for each scheduled PUSCH, determine the number of repeated transmissions of the scheduled PUSCH according to the time domain start position and length of the scheduled PUSCH and the time domain start position of the next scheduled PUSCH.
  • the DCI may be carried through the PDCCH.
  • the specific number of PUSCHs scheduled by the DCI may be determined according to the number of SLIVs recorded in the corresponding row of the time domain resource indication table by the index number indicated in the DCI.
  • the format of the time domain resource indication table may be similar to the format of Table 2 above.
  • the specific number of the PUSCH scheduled by the DCI can be in the time domain resource indication table according to the index number indicated in the DCI. The number of start symbol and length pairs recorded for the corresponding line is determined.
  • only some PUSCHs may support repeated transmission, or all PUSCHs may support repeated transmission.
  • the time interval between the two scheduled PUSCHs before and after it can be determined whether the earlier scheduled PUSCH among the two scheduled PUSCHs has enough time domain resources for repeated transmission. For example, if the last OFDM symbol occupied by the first scheduled PUSCH and the starting OFDM symbol of the second scheduled PUSCH are adjacent to each other, it can be determined that the first scheduled PUSCH does not support repeated transmission.
  • the repeated transmission type of the scheduled PUSCH may be the PUSCH repetition type A, that is, the time slot aggregation transmission specified in the protocol version 15 (Release 15, Rel-15 for short).
  • the repeated transmission type of the scheduled PUSCH may be PUSCH repetition type B, that is, enhanced PUSCH transmission specified in protocol version 16 (Release 16, Rel-16 for short).
  • PUSCH repetition using PUSCH repetition type B can be performed across time slots and can be repeated multiple times within a time slot; while PUSCH repetition using PUSCH repetition type A is performed within a time slot. Can only be repeated once.
  • the step S202 may include the step of: searching the time domain resource indication table according to the index number indicated by the DCI to determine the time domain starting position and length of each scheduled PUSCH, the time domain resource indication The table includes at least one row, wherein each row indicates the time domain start position and length of at least one scheduled PUSCH, and the rows of the time domain resource indication table correspond to index numbers one-to-one.
  • the time domain resource indication table described in this embodiment is improved compared to Table 2 used in the prior art.
  • Table 3 exemplarily shows a possible representation form of the time domain resource indication table described in this embodiment. Specifically, a row of the time-domain resource indication table simultaneously indicates one or more time-domain resources SLIV of scheduled PUSCH, the slot offset of each scheduled PUSCH relative to DCI, the mapping type of each scheduled PUSCH, and the last scheduled PUSCH Number of repeat transfers.
  • the number of repeated transmissions of the last scheduled PUSCH among all the PUSCH scheduled by the DCI can be directly determined by looking up the table.
  • each scheduled PUSCH corresponds to one slot offset; while each row in Table 2 is configured with only one slot offset.
  • the time domain start position of the scheduled PUSCH may include the time slot position where the scheduled PUSCH is located, and the start symbol in the corresponding time slot.
  • the slot position where each scheduled PUSCH is located may be determined according to the slot offset of each scheduled PUSCH relative to the DCI. Further, the starting OFDM symbol in the corresponding time slot is determined according to the SLIV of each scheduled PUSCH.
  • the time domain resource indication table may be configured through radio resource control (Radio Resource Control, RRC for short) signaling.
  • the DCI indicates through the index number which row in the time domain resource indication table is scheduled by the UE this time. There are several SLIVs in this row, which means that the UE is authorized several scheduled PUSCHs this time, and the number of repeated transmissions of each scheduled PUSCH can be determined by executing step S203.
  • the step S203 may include the step of: comparing the time slot where the time domain starting position of the next scheduled PUSCH is located with the selected time slot.
  • the number of time slots between the time slots where the time domain starting position of the scheduled PUSCH is located is determined as the number of repeated transmissions of the scheduled PUSCH; wherein, the time domain in the corresponding time slot when the scheduled PUSCH is repeatedly transmitted each time The position is determined according to the time domain start position and length of the scheduled PUSCH.
  • the time slot offset of the first scheduled PUSCH relative to DCI is 1, indicating that the first scheduled PUSCH is located in time slot n+1; the second scheduled PUSCH relative to the time slot offset of DCI is 2, indicating that the second scheduled PUSCH is located in time slot n+2; the time slot offset of the third scheduled PUSCH relative to the DCI is 4, indicating that the third scheduled PUSCH is located in time slot n+4.
  • the first scheduled PUSCH and the second scheduled PUSCH are consecutive in time slots, the first scheduled PUSCH is not repeatedly transmitted. That is, the first scheduled PUSCH is sent once in slot n+1. Specifically, the 4th to 13th OFDM symbols of time slot n+1 are occupied.
  • the second scheduled PUSCH is sent twice in time slot n+2 and time slot n+3. Specifically, the 0-13th OFDM symbols of time slot n+2 and time slot n+3 are occupied.
  • the third scheduled PUSCH which is the last scheduled PUSCH granted this time, is only sent once in time slot n+4. Specifically, the 0-12th OFDM symbols of time slot n+4 are occupied.
  • the time slot offset recorded in the time domain resource indication table may refer to the time slot offset between the corresponding scheduled PUSCH and the previous scheduled PUSCH.
  • this row indicates that the DCI has scheduled two scheduled PUSCHs, wherein the first scheduled PUSCH has a slot offset of 1 relative to the DCI, and the second scheduled PUSCH is relative to the first scheduled PUSCH.
  • the slot offset of a scheduled PUSCH is 2.
  • the time-domain resource indication table shown in Table 4 may be further rewritten on the basis of Table 3.
  • Table 4 exemplarily shows another possible representation form of the time domain resource indication table described in this embodiment. Specifically, a row of the time domain resource indication table simultaneously indicates the start symbol and length of the respective time domain resources of one or more scheduled PUSCHs, the slot offset of each scheduled PUSCH relative to the DCI, and the mapping type of each scheduled PUSCH, and the number of repeated transmissions of the last scheduled PUSCH.
  • the number of repeated transmissions of the last scheduled PUSCH among all the PUSCH scheduled by the DCI can be directly determined by looking up the table.
  • Table 3 The difference between Table 3 and Table 4 is that the repeated transmission type of scheduled PUSCH in Table 3 is repetition type A, so SLIV is used to jointly indicate the start symbol and length of scheduled PUSCH; the repeated transmission type of scheduled PUSCH in Table 4 is repetition type B , thus indicating the start symbol and length of the scheduled PUSCH, respectively.
  • each row in Table 4 indicates the respective slot offset of the at least one scheduled PUSCH relative to the DCI or the previous scheduled PUSCH, and the start symbol and length within the corresponding slot. Thereby, the time domain starting position of each scheduled PUSCH can be determined.
  • the symbol occupancy status of the scheduled PUSCH in the time slot can be determined.
  • the time domain starting position of each scheduled PUSCH can be determined.
  • the step S203 may include the step of: comparing the time slot located at the time domain start position of the next scheduled PUSCH with the all The number of symbols between the time slots where the time domain starting position of the scheduled PUSCH is located is divided by the length of the scheduled PUSCH to obtain the number of repeated transmissions of the scheduled PUSCH.
  • the time domain starting position of the first scheduled PUSCH is the 0th OFDM symbol of time slot n+1, and the length is 2 OFDM symbols;
  • the time domain starting position of the second scheduled PUSCH is time slot n+1
  • the fourth OFDM symbol is 2 OFDM symbols in length;
  • the time domain start position of the third scheduled PUSCH is the sixth OFDM symbol in time slot n+2, and the length is 2 OFDM symbols.
  • the first scheduled PUSCH is repeatedly transmitted twice within the time slot n+1. Specifically, the 0-1st OFDM symbols and the 2-3rd OFDM symbols of the time slot n+1 are occupied.
  • the second scheduled PUSCH is repeatedly transmitted 8 times in time slot n+1 and time slot n+2.
  • the 10th to 11th OFDM symbols, the 12th to 13th OFDM symbols of timeslot n+1, the 0th to 1st OFDM symbols of timeslot n+2, the 2nd to 3rd OFDM symbols of timeslot n+2 are The 4th to 5th OFDM symbols of slot n+2.
  • the third scheduled PUSCH is repeatedly transmitted 4 times in time slot n+2. Specifically occupy the 6th to 7th OFDM symbols of timeslot n+2, the 8th to 9th OFDM symbols of timeslot n+2, the 10th to 11th OFDM symbols of timeslot n+2, and the 10th to 11th OFDM symbols of timeslot n+2. 12-13th OFDM symbols.
  • the scheduled PUSCH may be used to carry the data of the URLLC service or the eMBB service.
  • the DCI may also be used to trigger aperiodic CSI reporting.
  • the method described in this embodiment may further include the step of: multiplexing the aperiodic CSI in one or more scheduled PUSCHs scheduled by the DCI, on the first repeated transmission of the first scheduled PUSCH.
  • the first scheduled PUSCH is transmitted in the 4th to 13th OFDM symbols occupying time slot n+1. Also, as shown in FIG. 4 , the first transmission of the PUSCH is scheduled for the first transmission of the 0-1th OFDM symbol in the time slot n+1.
  • the first repeated transmission refers to the first actual repeated transmission. For example, in each time slot of repeated transmission, if at least one symbol in a time slot is a downlink symbol, the PUSCH of this time slot is not sent.
  • the aperiodic CSI may be multiplexed in one or more scheduled PUSCHs scheduled by the DCI, and the second-to-last repeated transmission of the first scheduled PUSCH may be multiplexed.
  • the first transmission of the PUSCH is scheduled for the first transmission of the 0-1 th OFDM symbol in the time slot n+1.
  • the second-to-last repeated transmission refers to the second-to-last actual repeated transmission.
  • the aperiodic CSI may be multiplexed in one or more scheduled PUSCHs scheduled by the DCI, and the second-to-last scheduled PUSCH is the first repeated transmission.
  • the first repeated transmission of the PUSCH is scheduled for the second scheduled transmission of the 0-13th OFDM symbols of the time slot n+2.
  • the first transmission of the PUSCH is scheduled for the second transmission in the 4th to 5th OFDM symbol transmissions occupying time slot n+1.
  • the aperiodic CSI may be multiplexed in one or more scheduled PUSCHs scheduled by the DCI, and the second-to-last repeated transmission of the second-to-last scheduled PUSCH.
  • the first repeated transmission of the PUSCH is scheduled for the second scheduled transmission of the 0-13th OFDM symbols of the time slot n+2.
  • the second to last transmission of the PUSCH is scheduled for the second to third OFDM symbol transmissions occupying time slot n+2.
  • the aperiodic CSI may be multiplexed in one or more scheduled PUSCHs scheduled by the DCI, and the last scheduled PUSCH is on the first repeated transmission.
  • the first repeated transmission of the PUSCH is scheduled for the third scheduling of the 0-12th OFDM symbol transmission occupying time slot n+4.
  • the first transmission of the PUSCH is scheduled for the third transmission in the 6-7th OFDM symbol transmission occupying the time slot n+2.
  • the aperiodic CSI may be multiplexed in one or more scheduled PUSCHs scheduled by the DCI, and the last scheduled PUSCH is transmitted on the penultimate repeat transmission.
  • the third scheduled transmission of the 10th to 11th OFDM symbols occupying time slot n+2 is the penultimate transmission of the PUSCH.
  • the aperiodic CSI may be multiplexed on the second-to-last repeated transmission in the one or more scheduled PUSCHs of the DCI schedule.
  • the penultimate repeat transmission of this variation indicates the penultimate repeat transmission of all scheduled PUSCHs.
  • the total of the 3 scheduled PUSCHs transmitted in the 0-13th OFDM symbols of the time slot n+3 is repeated for the second-to-last repeated transmission.
  • the 3 scheduled PUSCHs transmitted in the 10th to 11th OFDM symbols occupying time slot n+2 are repeatedly transmitted for the second to last time in total.
  • the aperiodic CSI may be multiplexed on the first repeated transmission in the one or more scheduled PUSCHs scheduled by the DCI.
  • the first repeated transmission of this variation indicates the first repeated transmission of all scheduled PUSCHs.
  • this embodiment can realize repeated transmission of PUSCH in the unlicensed spectrum, and can effectively determine the number of repeated transmissions of the scheduled PUSCH when the PUSCH permitted for repeated transmission is scheduled through the DCI, further improving the reliability of service transmission in the unlicensed frequency band. High reliability and low latency.
  • the total duration of repeatable transmission of the earlier scheduled PUSCH is determined according to the time domain starting positions of the two scheduled PUSCHs before and after, and then the number of repeated transmissions is calculated according to the length of a single transmission of the earlier scheduled PUSCH.
  • the number of repeated transmissions of the PUSCH authorized for uplink transmission this time can be quickly determined with low computational complexity.
  • the time domain position of each repeated transmission can also be determined synchronously, so as to transmit data on the scheduled PUSCH of each repeated transmission.
  • the specific multiplexing time domain position of the aperiodic CSI on the repeated transmission PUSCH can be further determined.
  • FIG. 5 is a schematic structural diagram of a PUSCH repeated transmission scheduling apparatus for an unlicensed frequency band according to an embodiment of the present invention.
  • the PUSCH repeated transmission scheduling apparatus 5 for an unlicensed frequency band described in this embodiment can be used to implement the method and technical solutions described in the embodiments described in FIG. 2 to FIG. 4 .
  • the apparatus 5 for scheduling repeated PUSCH transmission in an unlicensed frequency band described in this embodiment may include: a receiving module 51, configured to receive DCI, wherein the DCI schedules one or more PUSCHs, and the DCI
  • the scheduled PUSCH is denoted as scheduled PUSCH, and at least one scheduled PUSCH is repeated transmission;
  • the first determination module 52 is used to determine the time domain starting position and length of each scheduled PUSCH according to the DCI;
  • the second determination module 53 For each scheduled PUSCH, the number of times of repeated transmission of the scheduled PUSCH is determined according to the time domain start position and length of the scheduled PUSCH and the time domain start position of the next scheduled PUSCH.
  • the above-mentioned PUSCH repeated transmission scheduling device 5 for an unlicensed frequency band may correspond to a chip with a data transmission function in the user equipment, or a chip with a data processing function, such as a system-on-chip (System-On-Chip) a-Chip, abbreviated as SOC), baseband chip, etc;
  • a system-on-chip System-On-Chip
  • SOC system-On-Chip
  • each module/unit included in each device and product described in the above embodiments it may be a software module/unit, a hardware module/unit, or a part of a software module/unit, a part of which is a software module/unit. is a hardware module/unit.
  • each module/unit included therein may be implemented by hardware such as circuits, or at least some modules/units may be implemented by a software program.
  • Running on the processor integrated inside the chip the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the chip module, the modules/units contained therein can be They are all implemented by hardware such as circuits, and different modules/units can be located in the same component (such as a chip, circuit module, etc.) or in different components of the chip module, or at least some modules/units can be implemented by software programs.
  • the software program runs on the processor integrated inside the chip module, and the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the terminal, each module contained in it
  • the units/units may all be implemented in hardware such as circuits, and different modules/units may be located in the same component (eg, chip, circuit module, etc.) or in different components in the terminal, or at least some of the modules/units may be implemented in the form of software programs Realization, the software program runs on the processor integrated inside the terminal, and the remaining (if any) part of the modules/units can be implemented in hardware such as circuits.
  • an embodiment of the present invention further discloses a storage medium on which a computer program is stored, and when the computer program is run by a processor, the method and technical solutions described in the embodiments shown in FIG. 2 to FIG. 4 are executed.
  • the storage medium may include a computer-readable storage medium such as a non-volatile memory or a non-transitory memory.
  • the storage medium may include ROM, RAM, magnetic or optical disks, and the like.
  • an embodiment of the present invention also discloses a terminal, including a memory and a processor, the memory stores a computer program that can run on the processor, and the processor executes the above diagram when running the computer program. 2 to the technical solutions of the methods described in the embodiments shown in FIG. 4 .
  • the terminal may be a UE, such as a 5G UE.
  • the terminal may include the PUSCH repeated transmission scheduling apparatus 5 for the unlicensed frequency band shown in FIG. 5 .

Landscapes

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

Abstract

一种用于非授权频段的PUSCH重复传输调度方法及装置、存储介质、终端，所述方法包括：接收DCI，其中，所述DCI调度一个或多个PUSCH，且其中至少一个调度PUSCH为重复传输；根据所述DCI确定每一调度PUSCH的时域起始位置和长度；对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。通过本发明方案能够在非授权频谱中实现PUSCH的重复传输，且在通过DCI调度允许重复传输的PUSCH时，能够有效确定调度PUSCH的重复传输次数，进一步改善在非授权频段中业务传输的高可靠性和低时延。

Description

用于非授权频段的PUSCH重复传输调度方法及装置、存储介质、终端
本申请要求2020年7月22日提交中国专利局、申请号为202010712468.9、发明名称为“用于非授权频段的PUSCH重复传输调度方法及装置、存储介质、终端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体地涉及一种用于非授权频段的PUSCH重复传输调度方法及装置、存储介质、终端。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，简称3GPP)标准组织已研究在非授权频谱上如何部署新空口(New Radio，简称NR，也可称为新无线)网络，从而达到公平有效地利用非授权频谱，提高NR系统的数据传输速率的目的。非授权频谱的数据传输均需要采用先听再说(listen before talk，简称LBT)机制，以减少对其它系统的影响。
针对非授权频谱中物理下行数据信道(也可称为物理下行共享信道，Physical Downlink Shared Channel，简称PDSCH)与上行反馈信道处于不同连续占用时长(Continuous of Time，简称COT)的情形，应用于非授权频谱的NR(NR-Unlicensed，简称NR-U)支持一个下行调度信令可以同时调度多个物理上行共享信道(Physical Uplink Shared Channel，简称PUSCH)信令的方式，称为单个DCI调度多个PUSCH(multiple PUSCHs scheduled by a single DCI)。
在这种调度方式中，每个PUSCH均有对应的新数据指示(New Data Indicator，简称NDI)域及冗余版本(Redundancy Version，简称 RV)域。混合自动重传请求(Hybrid Automatic Repeat reQuest，简称HARQ)进程标识(Identification，简称ID)只有一个，对应第一个调度的PUSCH，后续调度PUSCH依次使用前一个调度PUSCH的HARQ进程ID+1。
在这种调度方式中，时域资源分配机制为每个调度PUSCH均有一个独立起始和长度指示值(Start and Length Indication Valve，简称SLIV)及映射类型。单个DCI具体调度的PUSCH数量，是直接由通过所述DCI通知的时域资源分配(Time domain recourse allocation，简称TDRA)表格中某行的有效SLIV个数决定的。
现有技术虽然可以在非授权频谱中通过DCI调度多个PUSCH，但并不支持PUSCH重复传输机制。当需要在非授权频段中传输对可靠性和时延要求较严格的业务数据时，现有无法支持PUSCH重复传输的技术实现显然无法满足业务需求，影响用户体验。
发明内容
本发明解决的技术问题是如何在非授权频谱中实现PUSCH的重复传输。
为解决上述技术问题，本发明实施例提供一种用于非授权频段的PUSCH重复传输调度方法，包括：接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；根据所述DCI确定每一调度PUSCH的时域起始位置和长度；对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。
可选的，所述方法还包括：根据所述DCI确定最后一个调度PUSCH的重复传输次数。
可选的，所述根据所述DCI确定每一调度PUSCH的时域起始位置和长度包括：根据所述DCI指示的索引号查找时域资源指示表， 以确定每一调度PUSCH的时域起始位置和长度，所述时域资源指示表包括至少一行，其中每行指示至少一个调度PUSCH的时域起始位置和长度，所述时域资源指示表的行与索引号一一对应。
可选的，所述时域资源指示表中的每行还指示这一行对应的至少一个调度PUSCH中最后一个调度PUSCH的重复传输次数。
可选的，所述时域资源指示表中的每行还指示这一行对应的至少一个调度PUSCH各自的映射类型。
可选的，所述每行指示至少一个调度PUSCH的时域起始位置和长度包括：所述每行指示所述至少一个调度PUSCH各自相对于所述DCI或前一调度PUSCH的时隙偏置，以及所述至少一个调度PUSCH各自的SLIV；或者，所述每行指示所述至少一个调度PUSCH各自相对于所述DCI或前一调度PUSCH的时隙偏置，以及在对应时隙内的起始符号和长度。
可选的，所述调度PUSCH用于承载URLLC业务或eMBB业务的数据。
可选的，当所述调度PUSCH的重复传输类型为PUSCH重复类型A时，所述对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数包括：将位于所述下一调度PUSCH的时域起始位置所处时隙与所述调度PUSCH的时域起始位置所处时隙之间的时隙数量，确定为所述调度PUSCH的重复传输次数；其中，所述调度PUSCH每次重复传输时在对应时隙内的时域位置根据所述调度PUSCH的时域起始位置和长度确定。
可选的，当所述调度PUSCH的重复传输类型为PUSCH重复类型B时，所述对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数包括：将位于所述下一调度PUSCH的时 域起始位置所处时隙与所述调度PUSCH的时域起始位置所处时隙之间的符号数量，除以所述调度PUSCH的长度，以得到所述调度PUSCH的重复传输次数。
可选的，所述DCI用于触发非周期CSI上报，所述方法还包括：将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的第一次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的倒数第二次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的第一次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的倒数第二次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的第一次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的倒数第二次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的倒数第二次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的第一次重复传输上。
为解决上述技术问题，本发明实施例还提供一种用于非授权频段的PUSCH重复传输调度装置，包括：接收模块，用于接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；第一确定模块，用于根据所述DCI确定每一调度PUSCH的时域起始位置和长度；第二确定模块，对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。
为解决上述技术问题，本发明实施例还提供一种存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行上述方法的 步骤。
为解决上述技术问题，本发明实施例还提供一种终端，包括上述装置，或者包括存储器和处理器，所述存储器上存储有能够在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述方法的步骤。
与现有技术相比，本发明实施例的技术方案具有以下有益效果：
本发明实施例提供一种用于非授权频段的PUSCH重复传输调度方法，包括：接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；根据所述DCI确定每一调度PUSCH的时域起始位置和长度；对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。
由此，本实施方案能够在非授权频谱中实现PUSCH的重复传输，且在通过DCI调度允许重复传输的PUSCH时，能够有效确定调度PUSCH的重复传输次数，进一步改善在非授权频段中业务传输的高可靠性和低时延。具体而言，根据前后两个调度PUSCH的时域起始位置来确定靠前的调度PUSCH可以重复传输的总时长，进而根据靠前的调度PUSCH单次传输的长度来计算得到重复传输次数。采用本实施方案，能够以较低的运算复杂度快速确定本次被授权进行上行传输的PUSCH的重复传输次数。进一步，在确定重复传输次数的同时，还能同步确定每次重复传输的时域位置，以便在各重复传输的调度PUSCH上传输数据。
进一步，所述DCI用于触发非周期CSI上报，所述方法还包括：将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的第一次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的倒数第二次重复传输上；或者，将所述非周期CSI复用在 所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的第一次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的倒数第二次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的第一次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的倒数第二次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的倒数第二次重复传输上；或者，将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的第一次重复传输上。
由此，在非授权频谱中DCI调度多个支持重复传输的PUSCH的场景中，当DCI触发非周期CSI上报时，能够进一步确定非周期CSI在重复传输PUSCH上的具体复用时域位置。
附图说明
图1是现有技术中调度PUSCH的时域资源分配图；
图2是本发明实施例一种用于非授权频段的PUSCH重复传输调度方法的流程图；
图3是本发明实施例一个典型应用场景的时域资源分配图；
图4是本发明实施例另一个典型应用场景的时域资源分配图；
图5是本发明实施例一种用于非授权频段的PUSCH重复传输调度装置的结构示意图。
具体实施方式
如背景技术所言，现有技术虽然可以在非授权频谱中通过DCI调度多个PUSCH，但并不支持PUSCH重复传输机制。
具体而言，NR系统中调度PUSCH的DCI格式包含DCI0_0、DCI0_1和DCI0_2。无论哪一种DCI格式，均可以包含时域资源分配 (Time domain resource assignment)字段，用于通知用户设备(User Equipment，简称UE)被授权使用的PUSCH的时域资源位置。
例如，用于调度PUSCH的DCI可以指示一个指向UE时域资源专用表格的行索引。该表格提供用于PUSCH传输的正交频分复用(Orthogonal Frequency Division Multiplexing，简称OFDM)符号，可以包含起始OFDM符号(记作S)和分配的OFDM符号长度(记作L)(统称为SLIV)，还可以提供DCI和PUSCH之间的时隙偏置K2，还可以提供PUSCH的映射类型(类型A(Type A)或类型B(Type B))，如表1所示。
表1
Figure PCTCN2021106976-appb-000001
表1示出PUSCH不同映射类型下允许采用的符号起始位置(S)和长度(L)。
在5G NR通信系统中支持高可靠低延时(Ultra Reliable&Low Latency Communication，简称URLLC)业务。5G URLLC技术实现了基站与终端间上下行均为0.5毫秒的用户面时延。该时延是指：成功传送应用层互联网协议(Internet Protocol，简称IP)数据包或消息所花费的时间。具体是指，从发送方5G无线协议层入口点，经由5G无线传输，到接收方5G无线协议层出口点所花费的时间。其中，时延来自于上行链路和下行链路两个方向。
5G URLLC实现低时延的主要技术包括：引入更小的时间资源单位，如微时隙(mini-slot)；上行接入采用免调度许可的机制，终端可直接接入信道；支持异步过程，以节省上行时间同步开销；采用快速自动请求重传(HARQ)和快速动态调度等。为实现高优先级下行业务的快速反馈，NR基站(gNB)会配置或指示其传输的优先级，如高优先级或低优先级业务。
目前，NR-U中支持一个DCI可以同时调度多个PUSCH。调度的多个PUSCH的时域资源分配机制为每个PUSCH均有一个独立SLIV及映射类型，单个DCI具体调度的PUSCH数量，是直接由通过所述DCI通知的时域资源分配(Time domain recourse allocation，简称TDRA)表格(如表2所示)中某行的有效SLIV的数量决定的。
表2
Figure PCTCN2021106976-appb-000002
以表2中索引号index＝0为例，当DCI指示索引号0时，可以确定共调度了3个PUSCH，结合表1，由各自SLIV可以确定3个PUSCH的起始符号和长度分别为(S,L)＝(4,10),(0,14),(0,13)。相应的，三个调度PUSCH的时域资源分配如图1所示。
参考图1和表2，物理下行控制信道(Physical Downlink Control Channel，简称PDCCH)用于承载DCI，假设所述DCI指示索引号0，则根据表2中索引号0对应行的相关信息可以确定，所述DCI调度的PUSCH与DCI之间的时隙偏置(slot offset，记作K2)为1个时隙。相应的，由于DCI位于时隙n，因此可以确定调度PUSCH的时域初始时隙为时隙n+1。
第一个调度PUSCH的起始符号和长度(S,L)＝(4,10)，对应表2中索引号0对应行记录的SLIV1和映射类型1。具体到图1，第一个调度PUSCH的时域位置即为时隙n+1的第4个符号到第13个符号共 计10个符号。
第二个调度PUSCH的起始符号和长度(S,L)＝(0,14)，对应表2中索引号0对应行记录的SLIV2和映射类型2。具体到图1，第二个调度PUSCH的时域位置即为时隙n+2的第0个符号到第13个符号共计14个符号。
第三个调度PUSCH的起始符号和长度(S,L)＝(0,13)，对应表2中索引号0对应行记录的SLIV3和映射类型3。具体到图1，第三个调度PUSCH的时域位置即为时隙n+3的第0个符号到第12个符号共计13个符号。
也就是说，根据表2可以确定DCI调度的每个PUSCH的起始符号位置和长度，以及第一个调度PUSCH相对于DCI的时隙偏置。DCI调度的多个PUSCH是连续传输的。
另一方面，一个用于调度上行授权的DCI可以同时调度上行数据及触发非周期信道状态信息(Aperiodic-Channel State Information，简称A-CSI)上报。在现有技术中，当一个DCI调度多个PUSCH时，非周期CSI复用在倒数第二个调度PUSCH上。
综上，现有技术仅支持在非授权频段通过DCI调度多个PUSCH，但并不支持PUSCH重复传输。对于诸如通过非授权频段传输的超高可靠与低时延通信(Ultra-reliable and Low Latency Communications，简称URLLC)业务和增强移动带宽(Enhanced Mobile Broadband，简称eMBB)业务这类对可靠性和时延要求较严格的业务，现有技术的这种不支持可能导致在非授权频段传输这类业务的数据时无法达到这类业务所要求的高可靠性和低时延。
为解决上述技术问题，本发明实施例提供一种用于非授权频段的PUSCH重复传输调度方法，包括：接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；根据所述DCI确定每一调度 PUSCH的时域起始位置和长度；对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。
由此，本实施方案能够在非授权频谱中实现PUSCH的重复传输，且在通过DCI调度允许重复传输的PUSCH时，能够有效确定调度PUSCH的重复传输次数，进一步改善在非授权频段中业务传输的高可靠性和低时延。具体而言，根据前后两个调度PUSCH的时域起始位置来确定靠前的调度PUSCH可以重复传输的总时长，进而根据靠前的调度PUSCH单次传输的长度来计算得到重复传输次数。采用本实施方案，能够以较低的运算复杂度快速确定本次被授权进行上行传输的PUSCH的重复传输次数。进一步，在确定重复传输次数的同时，还能同步确定每次重复传输的时域位置，以便在各重复传输的调度PUSCH上传输数据。
为使本发明的上述目的、特征和有益效果能够更为明显易懂，下面结合附图对本发明的具体实施例做详细的说明。
图2是本发明实施例一种用于非授权频段的PUSCH重复传输调度方法的流程图。
具体而言，本实施方案可以应用于非授权频谱且多PUSCH连续调度场景。进一步而言，本实施方案调度的PUSCH重复传输可以用于承载在非授权频段传输的URLLC业务、eMBB业务，以及其他具有高可靠性和低时延要求的业务的数据。
本实施方案能够在通过单个DCI调度多个PUSCH授权的机制基础上，引入PUSCH重复传输机制，以及基于PUSCH重复传输的非周期CSI复用机制。
在具体实施中，下述步骤S201～步骤S203所提供的用于非授权频段的PUSCH重复传输调度方法可以由用户设备中的具有数据传输功能的芯片执行，也可以由用户设备中的基带芯片执行。
具体地，参考图2，本实施例所述用于非授权频段的PUSCH重复传输调度方法可以包括如下步骤：
步骤S201，接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；
步骤S202，根据所述DCI确定每一调度PUSCH的时域起始位置和长度；
步骤S203，对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。
在一个具体实施中，DCI可以通过PDCCH承载。
具体而言，DCI调度的PUSCH的具体数量可以根据DCI中指示的索引号在时域资源指示表中对应行所记录的SLIV数量确定。其中，所述时域资源指示表可以与上述表2的格式相类似。
或者，当PUSCH采用协议版本16(Release-16，简称Rel-16)规定的重复类型B进行重复传输时，DCI调度的PUSCH的具体数量可以根据DCI中指示的索引号在时域资源指示表中对应行所记录的起始符号和长度对的数量确定。
在一个具体实施中，DCI调度的多个PUSCH中，可以仅部分PUSCH支持重复传输，也可以所有PUSCH均支持重复传输。
具体而言，根据前后两个调度PUSCH之间的时间间隔，可以确定前后两个调度PUSCH中靠前的调度PUSCH是否具有足够的时域资源来进行重复传输。例如，若第一个调度PUSCH所占用的最后一个OFDM符号和第二个调取PUSCH的起始OFDM符号是相邻的，则可以确定第一个调度PUSCH不支持重复传输。
在一个具体实施中，所述调度PUSCH的重复传输类型可以为 PUSCH重复类型A，即协议版本15(Release 15，简称Rel-15)规定的时隙聚合传输。或者，所述调度PUSCH的重复传输类型可以为PUSCH重复类型B，即协议版本16(Release 16，简称Rel-16)规定的增强PUSCH传输。
两种重复传输类型的区别在于，采用PUSCH重复类型B进行的PUSCH重复可以跨时隙进行，且一个时隙内可以多次重复传输；而采用PUSCH重复类型A进行的PUSCH重复在一个时隙内只能重复一次。
在一个具体实施中，所述步骤S202可以包括步骤：根据所述DCI指示的索引号查找时域资源指示表，以确定每一调度PUSCH的时域起始位置和长度，所述时域资源指示表包括至少一行，其中每行指示至少一个调度PUSCH的时域起始位置和长度，所述时域资源指示表的行与索引号一一对应。
具体而言，为支持本实施例所述PUSCH的重复传输调度，本实施例所述时域资源指示表相对于现有技术所采用的表2进行了改进。
表3时域资源指示表
Figure PCTCN2021106976-appb-000003
表3示例性的展示本实施例所述时域资源指示表的一种可能的表现形式。具体而言，时域资源指示表的一行同时指示一个或多个调 度PUSCH的时域资源SLIV、各个调度PUSCH相对于DCI的时隙偏置、各个调度PUSCH的映射类型，以及最后一个调度PUSCH的重复传输次数。
因此，根据DCI指示的索引号，可以直接查表确定DCI调度的所有PUSCH中最后一个调度PUSCH的重复传输次数。
表3与表2的区别在于，表3的每一行中，每一调度PUSCH均对应有一个时隙偏置；而表2中每一行仅配置一个时隙偏置。
在一个具体实施中，调度PUSCH的时域起始位置可以包括调度PUSCH所处时隙位置，以及在对应时隙内的起始符号。
例如，结合表3，对于每行指示的至少一个调度PUSCH，可以根据各调度PUSCH相对于所述DCI的时隙偏置来确定各调度PUSCH所处时隙位置。进一步，根据各调度PUSCH的SLIV确定在对应时隙内的起始OFDM符号。
在一个具体实施中，时域资源指示表可以是通过无线资源控制(Radio Resource Control，简称RRC)信令配置的。由DCI通过索引号指示UE本次调度的是时域资源指示表中的第几行。该行有几个SLIV，即表示UE本次被授权了几个调度PUSCH，其中每一调度PUSCH的重复传输次数则可以通过执行步骤S203确定。
在一个具体实施中，当所述调度PUSCH的重复传输类型为PUSCH重复类型A时，所述步骤S203可以包括步骤：将位于所述下一调度PUSCH的时域起始位置所处时隙与所述调度PUSCH的时域起始位置所处时隙之间的时隙数量，确定为所述调度PUSCH的重复传输次数；其中，所述调度PUSCH每次重复传输时在对应时隙内的时域位置根据所述调度PUSCH的时域起始位置和长度确定。
在一个典型的应用场景中，根据表3的时域资源分配方案，索引号index＝0的时域资源分配可以如图3所示。
具体而言，当DCI指示索引号0时，可以确定一共有3个调度 PUSCH，且由各自在表3中记录的SLIV可得到3个调度PUSCH的起始符号和长度分别为(S,L)＝(4,10),(0,14),(0,13)。
进一步，继续参考表3，第一个调度PUSCH相对于DCI的时隙偏置为1，表明第一个调度PUSCH位于时隙n+1；第二个调度PUSCH相对于DCI的时隙偏置为2，表明第二个调度PUSCH位于时隙n+2；第三个调度PUSCH相对于DCI的时隙偏置为4，表明第三个调度PUSCH位于时隙n+4。
进一步，由于第一个调度PUSCH和第二个调度PUSCH在时隙上是连续的，因此第一个调度PUSCH没有重复传输。也即，第一个调度PUSCH在时隙n+1内发送一次。具体占用时隙n+1的第4-13个OFDM符号。
由于第二个调度PUSCH和第三个调度PUSCH之间存在2个时隙，因此第二个调度PUSCH存在重复传输。也即，第二个调度PUSCH在时隙n+2和时隙n+3内发送2次。具体占用时隙n+2和时隙n+3的第0-13个OFDM符号。
由于表2中索引号0对应的重复传输次数＝1，因此，作为本次授权的最后一个调度PUSCH的第三个调度PUSCH仅在时隙n+4发送一次。具体占用时隙n+4的第0-12个OFDM符号。
在一个变化例中，时域资源指示表中记录的时隙偏置，可以是指对应的调度PUSCH与前一调度PUSCH之间的时隙偏置。
以表3中索引号index＝2对应的行为例，该行指示DCI调度了2个调度PUSCH，其中第一个调度PUSCH相对于DCI的时隙偏置为1，第二个调度PUSCH相对于第一个调度PUSCH的时隙偏置为2。
在另一个具体实施中，对于采用PUSCH重复类型B进行重复传输的调度PUSCH，可以在表3的基础上进一步改写得到表4所示时域资源指示表。
表4时域资源指示表
Figure PCTCN2021106976-appb-000004
表4示例性的展示本实施例所述时域资源指示表的另一种可能的表现形式。具体而言，时域资源指示表的一行同时指示一个或多个调度PUSCH各自的时域资源的起始符号和长度、各个调度PUSCH相对于DCI的时隙偏置、各个调度PUSCH的映射类型，以及最后一个调度PUSCH的重复传输次数。
因此，根据DCI指示的索引号，可以直接查表确定DCI调度的所有PUSCH中最后一个调度PUSCH的重复传输次数。
表3与表4的区别在于，表3中调度PUSCH的重复传输类型为重复类型A，因此采用SLIV联合指示调度PUSCH的起始符号和长度；表4中调度PUSCH的重复传输类型为重复类型B，因此分别指示调度PUSCH的起始符号和长度。
进一步，表4中的每行指示所述至少一个调度PUSCH各自相对于所述DCI或前一调度PUSCH的时隙偏置，以及在对应时隙内的起始符号和长度。由此可以确定每一调度PUSCH的时域起始位置。
例如，根据表4中每行针对每一调度PUSCH分别指示的起始符号和长度，可以确定调度PUSCH在时隙内的符号占用情况。结合表4中每行针对每一调度PUSCH分别指示的时隙偏置，可以确定每一 调度PUSCH的时域起始位置。
在一个具体实施中，当所述调度PUSCH的重复传输类型为PUSCH重复类型B时，所述步骤S203可以包括步骤：将位于所述下一调度PUSCH的时域起始位置所处时隙与所述调度PUSCH的时域起始位置所处时隙之间的符号数量，除以所述调度PUSCH的长度，以得到所述调度PUSCH的重复传输次数。
在一个典型的应用场景中，根据表4的时域资源分配方案，索引号index＝0的时域资源分配可以如图4所示。
具体而言，当DCI指示索引号0时，可以确定一共有3个调度PUSCH，由表4中记录的索引号为0的行中各个调度PUSCH的时隙偏置、起始符号和长度，可以得到如图4所示的重复传输调度资源分配结果。
其中，第一个调度PUSCH的时域起始位置为时隙n+1的第0个OFDM符号，长度为2个OFDM符号；第二个调度PUSCH的时域起始位置为时隙n+1的第4个OFDM符号，长度为2个OFDM符号；第三个调度PUSCH的时域起始位置为时隙n+2的第6个OFDM符号，长度为2个OFDM符号。
由于第一个调度PUSCH的时域起始位置和第二个调度PUSCH的时域起始位置之间一共有4个OFDM符号，且第一个调度PUSCH的长度为2个OFDM符号。因此，可以确定第一个调度PUSCH在时隙n+1内重复发送2次。具体占用时隙n+1的第0-1个OFDM符号，以及第2-3个OFDM符号。
由于第二个调度PUSCH的时域起始位置和第三个调度PUSCH的时域起始位置之间一共有46个OFDM符号，且第二个调度PUSCH的长度为2个OFDM符号。因此，可以确定第二个调度PUSCH在时隙n+1和时隙n+2内重复发送8次。具体占用时隙n+1的第4-5个OFDM符号、时隙n+1的第6-7个OFDM符号、时隙n+1的第8-9 个OFDM符号、时隙n+1的第10-11个OFDM符号、时隙n+1的第12-13个OFDM符号、时隙n+2的第0-1个OFDM符号、时隙n+2的第2-3个OFDM符号以及时隙n+2的第4-5个OFDM符号。
由于表4指示第三个调度PUSCH的重复传输次数为4次，因此，第三个调度PUSCH在时隙n+2重复发送4次。具体占用时隙n+2的第6-7个OFDM符号、时隙n+2的第8-9个OFDM符号、时隙n+2的第10-11个OFDM符号以及时隙n+2的第12-13个OFDM符号。
在一个具体实施中，所述调度PUSCH可以用于承载URLLC业务或eMBB业务的数据。
在一个具体实施中，所述DCI还可以用于触发非周期CSI上报。
相应的，本实施例所述方法还可以包括步骤：将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的第一次重复传输上。
如图3中占用时隙n+1的第4-13个OFDM符号传输的第一个调度PUSCH。又如图4中占用时隙n+1的第0-1个OFDM符号传输的第一个调度PUSCH的第一次传输。
进一步，所述第一次重复传输是指第一次实际重复传输。例如，在重复传输的各个时隙内，如果一个时隙内至少有一个符号为下行符号，则该时隙的PUSCH不发送。
在一个变化例中，可以将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的倒数第二次重复传输上。
如图4中占用时隙n+1的第0-1个OFDM符号传输的第一个调度PUSCH的第一次传输。
进一步，所述倒数第二次重复传输是指倒数第二次实际重复传输。
在一个变化例中，可以将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的第一次重复传输上。
如图3中占用时隙n+2的第0-13个OFDM符号传输的第二个调度PUSCH的第一次重复传输。
又如图4中占用时隙n+1的第4-5个OFDM符号传输的第二个调度PUSCH的第一次传输。
在一个变化例中，可以将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的倒数第二次重复传输上。
如图3中占用时隙n+2的第0-13个OFDM符号传输的第二个调度PUSCH的第一次重复传输。
又如图4中占用时隙n+2的第2-3个OFDM符号传输的第二个调度PUSCH的倒数第二次传输。
在一个变化例中，可以将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的第一次重复传输上。
如图3中占用时隙n+4的第0-12个OFDM符号传输的第三个调度PUSCH的第一次重复传输。
又如图4中占用时隙n+2的第6-7个OFDM符号传输的第三个调度PUSCH的第一次传输。
在一个变化例中，可以将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的倒数第二次重复传输上。
如图4中占用时隙n+2的第10-11个OFDM符号传输的第三个调度PUSCH的倒数第二次传输。
在一个变化例中，可以将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的倒数第二次重复传输上。
本变化例的倒数第二次重复传输指示所有调度PUSCH的倒数第二次重复传输。
如图3中占用时隙n+3的第0-13个OFDM符号传输的3个调度PUSCH总的倒数第二次重复传输。
又如图4中占用时隙n+2的第10-11个OFDM符号传输的3个调度PUSCH总的倒数第二次重复传输。
在一个变化例中，可以将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的第一次重复传输上。
本变化例的第一次重复传输指示所有调度PUSCH的首次重复传输。
如图3中占用时隙n+1的第4-13个OFDM符号传输的3个调度PUSCH总的首次重复传输。
又如图4中占用时隙n+1的第0-1个OFDM符号传输的3个调度PUSCH总的首次重复传输。
由此，本实施方案能够在非授权频谱中实现PUSCH的重复传输，且在通过DCI调度允许重复传输的PUSCH时，能够有效确定调度PUSCH的重复传输次数，进一步改善在非授权频段中业务传输的高可靠性和低时延。具体而言，根据前后两个调度PUSCH的时域起始位置来确定靠前的调度PUSCH可以重复传输的总时长，进而根据靠前的调度PUSCH单次传输的长度来计算得到重复传输次数。采用本实施方案，能够以较低的运算复杂度快速确定本次被授权进行上行传输的PUSCH的重复传输次数。进一步，在确定重复传输次数的同时，还能同步确定每次重复传输的时域位置，以便在各重复传输的调度PUSCH上传输数据。
在非授权频谱中DCI调度多个支持重复传输的PUSCH的场景中，当DCI触发非周期CSI上报时，能够进一步确定非周期CSI在重复传输PUSCH上的具体复用时域位置。
图5是本发明实施例一种用于非授权频段的PUSCH重复传输调度装置的结构示意图。本领域技术人员理解，本实施例所述用于非授权频段的PUSCH重复传输调度装置5可以用于实施上述图2至图4所述实施例中所述的方法技术方案。
具体地，参考图5，本实施例所述用于非授权频段的PUSCH重复传输调度装置5可以包括：接收模块51，用于接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；第一确定模块52，用于根据所述DCI确定每一调度PUSCH的时域起始位置和长度；第二确定模块53，对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。
关于所述用于非授权频段的PUSCH重复传输调度装置5的工作原理、工作方式的更多内容，可以参照上述图2至图4中的相关描述，这里不再赘述。
在具体实施中，上述的用于非授权频段的PUSCH重复传输调度装置5可以对应于用户设备中具有数据传输功能的芯片，或者对应于具有数据处理功能的芯片，例如片上系统(System-On-a-Chip，简称SOC)、基带芯片等；或者对应于用户设备中包括具有数据传输功能芯片的芯片模组；或者对应于具有数据处理功能芯片的芯片模组，或者对应于用户设备。
在具体实施中，关于上述实施例中描述的各个装置、产品包含的各个模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。
例如，对于应用于或集成于芯片的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片模组内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于终端的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于终端内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。
进一步地，本发明实施例还公开一种存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行上述图2至图4所示实施例中所述的方法技术方案。优选地，所述存储介质可以包括诸如非挥发性(non-volatile)存储器或者非瞬态(non-transitory)存储器等计算机可读存储介质。所述存储介质可以包括ROM、RAM、磁盘或光盘等。
进一步地，本发明实施例还公开一种终端，包括存储器和处理器，所述存储器上存储有能够在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述图2至图4所示实施例中所述的方法技术方案。具体地，所述终端可以为UE，如5G UE。或者，终端可以包括上述图5所示的用于非授权频段的PUSCH重复传输调度装置5。
虽然本发明披露如上，但本发明并非限定于此。任何本领域技术 人员，在不脱离本发明的精神和范围内，均可作各种更动与修改，因此本发明的保护范围应当以权利要求所限定的范围为准。

Claims (12)

  1. 一种用于非授权频段的PUSCH重复传输调度方法，其特征在于，包括：
    接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；
    根据所述DCI确定每一调度PUSCH的时域起始位置和长度；
    对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    根据所述DCI确定最后一个调度PUSCH的重复传输次数。
  3. 根据权利要求1所述的方法，其特征在于，所述根据所述DCI确定每一调度PUSCH的时域起始位置和长度包括：
    根据所述DCI指示的索引号查找时域资源指示表，以确定每一调度PUSCH的时域起始位置和长度，所述时域资源指示表包括至少一行，其中每行指示至少一个调度PUSCH的时域起始位置和长度，所述时域资源指示表的行与索引号一一对应。
  4. 根据权利要求3所述的方法，其特征在于，所述时域资源指示表中的每行还指示这一行对应的至少一个调度PUSCH中最后一个调度PUSCH的重复传输次数。
  5. 根据权利要求3所述的方法，其特征在于，所述每行指示至少一个调度PUSCH的时域起始位置和长度包括：
    所述每行指示所述至少一个调度PUSCH各自相对于所述DCI或前一调度PUSCH的时隙偏置，以及所述至少一个调度PUSCH各 自的SLIV；或者，
    所述每行指示所述至少一个调度PUSCH各自相对于所述DCI或前一调度PUSCH的时隙偏置，以及在对应时隙内的起始符号和长度。
  6. 根据权利要求1所述的方法，其特征在于，所述调度PUSCH用于承载URLLC业务或eMBB业务的数据。
  7. 根据权利要求1所述的方法，其特征在于，当所述调度PUSCH的重复传输类型为PUSCH重复类型A时，所述对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数包括：
    将位于所述下一调度PUSCH的时域起始位置所处时隙与所述调度PUSCH的时域起始位置所处时隙之间的时隙数量，确定为所述调度PUSCH的重复传输次数；
    其中，所述调度PUSCH每次重复传输时在对应时隙内的时域位置根据所述调度PUSCH的时域起始位置和长度确定。
  8. 根据权利要求1所述的方法，其特征在于，当所述调度PUSCH的重复传输类型为PUSCH重复类型B时，所述对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定所述调度PUSCH的重复传输次数包括：
    将位于所述下一调度PUSCH的时域起始位置所处时隙与所述调度PUSCH的时域起始位置所处时隙之间的符号数量，除以所述调度PUSCH的长度，以得到所述调度PUSCH的重复传输次数。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述DCI用于触发非周期CSI上报，所述方法还包括：
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的第一次重复传输上；或者
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，第一个调度PUSCH的倒数第二次重复传输上；或者
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的第一次重复传输上；或者
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，倒数第二个调度PUSCH的倒数第二次重复传输上；或者
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的第一次重复传输上；或者
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中，最后一个调度PUSCH的倒数第二次重复传输上；或者
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的倒数第二次重复传输上；或者
    将所述非周期CSI复用在所述DCI调度的一个或多个调度PUSCH中的第一次重复传输上。
  10. 一种用于非授权频段的PUSCH重复传输调度装置，其特征在于，包括：
    接收模块，用于接收DCI，其中，所述DCI调度一个或多个PUSCH，将DCI调度的PUSCH记作调度PUSCH，并且其中至少一个调度PUSCH为重复传输；
    第一确定模块，用于根据所述DCI确定每一调度PUSCH的时域起始位置和长度；
    第二确定模块，对于每一调度PUSCH，根据所述调度PUSCH的时域起始位置和长度，以及下一调度PUSCH的时域起始位置确定 所述调度PUSCH的重复传输次数。
  11. 一种存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器运行时执行权利要求1至9任一项所述方法的步骤。
  12. 一种终端，包括上述权利要求10所述的装置，或者包括存储器和处理器，所述存储器上存储有能够在所述处理器上运行的计算机程序，其特征在于，所述处理器运行所述计算机程序时执行权利要求1至9任一项所述方法的步骤。
PCT/CN2021/106976 2020-07-22 2021-07-19 用于非授权频段的pusch重复传输调度方法及装置、存储介质、终端 Ceased WO2022017301A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010712468.9A CN113973337B (zh) 2020-07-22 2020-07-22 用于非授权频段的pusch重复传输调度方法及装置、存储介质、终端
CN202010712468.9 2020-07-22

Publications (1)

Publication Number Publication Date
WO2022017301A1 true WO2022017301A1 (zh) 2022-01-27

Family

ID=79584980

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/106976 Ceased WO2022017301A1 (zh) 2020-07-22 2021-07-19 用于非授权频段的pusch重复传输调度方法及装置、存储介质、终端

Country Status (2)

Country Link
CN (1) CN113973337B (zh)
WO (1) WO2022017301A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109565412A (zh) * 2016-08-01 2019-04-02 诺基亚技术有限公司 用于数据传输的控制资源的使用
US20190335488A1 (en) * 2018-02-15 2019-10-31 Intel Corporation Simultaneous harq-ack feedback and uplink transmission without dynamic grant
CN110913488A (zh) * 2019-11-22 2020-03-24 北京展讯高科通信技术有限公司 物理上行共享信道的调度方法及设备
CN111294937A (zh) * 2019-01-17 2020-06-16 北京展讯高科通信技术有限公司 数据传输方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11025456B2 (en) * 2018-01-12 2021-06-01 Apple Inc. Time domain resource allocation for mobile communication
CN110536459A (zh) * 2018-08-10 2019-12-03 中兴通讯股份有限公司 一种重复传输方法及装置、通信设备和存储介质
PL3834337T3 (pl) * 2018-08-10 2023-08-28 Telefonaktiebolaget Lm Ericsson (Publ) Przyznanie szeregowania łącza wstępującego dla wielu fizycznych kanałów współdzielonych łącza wstępującego
CN110460419B (zh) * 2019-08-09 2022-05-31 北京紫光展锐通信技术有限公司 上行数据发送方法及装置、存储介质、终端、基站

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109565412A (zh) * 2016-08-01 2019-04-02 诺基亚技术有限公司 用于数据传输的控制资源的使用
US20190335488A1 (en) * 2018-02-15 2019-10-31 Intel Corporation Simultaneous harq-ack feedback and uplink transmission without dynamic grant
CN111294937A (zh) * 2019-01-17 2020-06-16 北京展讯高科通信技术有限公司 数据传输方法及装置
CN110913488A (zh) * 2019-11-22 2020-03-24 北京展讯高科通信技术有限公司 物理上行共享信道的调度方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MODERATOR (APPLE INC.): "Summary of Email discussion [100b-e-NR-L1enh-URLLC-PUSCH- 04] on PUSCH enhancements for NR eURLLC (AI 7.2.5.3)", 3GPP TSG-RAN WG1 MEETING #100BIS-E; R1-2003006, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 2 May 2020 (2020-05-02), Online Meeting ;20200420 - 20200430, XP051879967 *

Also Published As

Publication number Publication date
CN113973337B (zh) 2023-03-24
CN113973337A (zh) 2022-01-25

Similar Documents

Publication Publication Date Title
US12446033B2 (en) User equipment and system performing transmission and reception operations
US11711846B2 (en) Multiple starting and ending positions for scheduled downlink transmission on unlicensed spectrum
CN110024467B (zh) 冲突处理的方法、及其用户设备和基站
US11039448B2 (en) Resource scheduling method and apparatus
CN110149661B (zh) 信道传输方法和装置、网络设备及计算机可读存储介质
EP2176982B1 (en) Apparatus, method and computer program product for resource allocation to decrease signaling for retransmissions
EP3499981A1 (en) Terminal and communication method
US20200021388A1 (en) Data Sending Method and Apparatus and Data Receiving Method and Apparatus
CN105634688A (zh) 一种实现数据传输的方法及装置
CN113037455B (zh) 发送和接收信息的方法及装置
CN115623598A (zh) 信号传输方法及装置
CN110971362A (zh) 一种发现参考信号发送方法及装置
WO2022017301A1 (zh) 用于非授权频段的pusch重复传输调度方法及装置、存储介质、终端
CN119895758A (zh) Harq进程标识的确定方法、装置、设备和存储介质
CN114731666B (zh) 传输资源确定方法及相关装置
CN115189850B (zh) 上行控制信息复用方法及相关装置
CN121077866A (zh) 资源冲突处理方法、装置、终端及网络侧设备
JP2022509332A (ja) アップリンクリソース要求のための通信処理方法および関連するデバイス

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: 21847357

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: 21847357

Country of ref document: EP

Kind code of ref document: A1