WO2022151383A1 - 一种上行传输方法及装置 - Google Patents

一种上行传输方法及装置 Download PDF

Info

Publication number
WO2022151383A1
WO2022151383A1 PCT/CN2021/072238 CN2021072238W WO2022151383A1 WO 2022151383 A1 WO2022151383 A1 WO 2022151383A1 CN 2021072238 W CN2021072238 W CN 2021072238W WO 2022151383 A1 WO2022151383 A1 WO 2022151383A1
Authority
WO
WIPO (PCT)
Prior art keywords
time domain
uplink data
network device
data channel
time
Prior art date
Application number
PCT/CN2021/072238
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/CN2021/072238 priority Critical patent/WO2022151383A1/zh
Publication of WO2022151383A1 publication Critical patent/WO2022151383A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present application relates to the field of communication technologies, and in particular, to an uplink transmission method and apparatus.
  • the terminal device sends uplink data to the network device, which can be sent through a physical uplink shared channel (PUSCH).
  • PUSCH repetition type A repetition type A
  • the terminal device repeats K times in units of new radio (NR) time slots when sending PUSCH
  • PUSCH repetition type B repetition type B
  • the terminal device sends the PUSCH, it repeats K times in units of the continuous symbol length of the PUSCH indicated by the network device, wherein the PUSCH repetition type, the continuous symbol length of the PUSCH and the number of repetitions of the PUSCH (K)
  • the terminal device can be obtained from the network device It is known from the transmission parameters of the delivered PUSCH.
  • the repeated transmission of PUSCH is affected by the time slot structure, cancellation indication (CI) and other factors. Some PUSCH repetitions will be cancelled or ignored, and the actual number of PUSCH repetitions will be less than the number of PUSCH repetitions indicated by the network device. PUSCH transmission performance.
  • the present application provides an uplink transmission method and apparatus to solve the problem that the actual number of repetitions of uplink data channels such as PUSCH during uplink transmission is less than the number of repetitions indicated by network equipment, which affects the transmission performance of uplink data channels.
  • an embodiment of the present application provides an uplink transmission method.
  • the method can be performed by a terminal device.
  • the method includes: receiving first indication information and second indication information from a network device, where the first indication information indicates an uplink Repetition type and repetition times of the data channel, the second indication information indicates a time slot offset; determine the starting time domain unit capable of sending the uplink data channel according to the time slot offset; use the starting time domain Unit starts, and it is determined that M first time domain units send the uplink data channel to the network device, wherein, from the starting time domain unit to the Mth first time domain unit, there are consecutive N units A time domain unit, wherein the N time domain units include Q second time domain units that do not transmit the uplink data channel, the M is greater than or equal to the number of repetitions indicated by the network device, and the Q is less than or equal to N-M, in the case that the repetition type is repetition type A, each time domain unit in the N time domain units is a time slot, and in the case that the repetition type is repetition type B, the
  • the uplink transmission mode of uplink data channels such as PUSCH is adjusted, so that the repetition times of the uplink data channels actually sent by the terminal equipment are not less than the repetition times of the uplink data channels indicated by the network equipment, which is beneficial to improve Transmission performance of uplink data channels such as PUSCH.
  • the time domain resources of the uplink data channel sent in each first time domain unit are not fully occupied by the demodulation reference signal DM-RS; or, in each first time domain unit
  • the number of uplink symbols of the uplink data channel sent in the network device is not less than half of the first number indicated by the network device; or, the uplink data carried in the uplink data channel sent in each first time domain unit
  • the number of occupied uplink symbols is not less than half of the first number indicated by the network device.
  • the time domain resources of the sent uplink data channel are not the first time domain unit occupied by the demodulation reference signal DM-RS, or the uplink data channel of the sent uplink data channel.
  • the number of symbols is not less than half of the first time domain unit indicated by the network device, or the number of uplink symbols occupied by the uplink data carried in the transmitted uplink data channel is not less than the first number indicated by the network device.
  • Half of the first time domain units, the number M of which is not less than the repetition times of the uplink data channel indicated by the network device, is conducive to ensuring that a sufficient amount of uplink data is carried through the uplink data channel, thereby improving the reliability of uplink data transmission.
  • the method further includes: receiving third indication information from the network device, where the third indication information indicates a configuration of a redundancy version RV, and the configuration of the RV includes G candidate RVs ;
  • Sending the uplink data channel to the network device in N-Q third time domain units includes: sending the uplink data channel to the network device in the N-Q third time domain units according to the configuration of the RV.
  • the uplink data channel sent on the time domain unit i uses the RV corresponding to i in the G candidate RVs, wherein, i is 0, 1, 2, 3...N-Q-1.
  • the terminal device when the terminal device sends the uplink data channel according to the RV configuration of the network device, it is beneficial for the network device to decode the uplink data channel.
  • the uplink data channel sent on the time domain unit i uses the channel corresponding to i-z in the G candidate RVs.
  • RV where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the first i in the N-Q third time domain units
  • the number of fourth time-domain units included in the time-domain unit, where the fourth time-domain unit is the starting symbol position of the uplink data channel that does not satisfy the transmission in the first i time-domain units, and the position is the network device
  • the indicated starting symbol position and the transmitted length of the uplink data channel are the time domain units of the continuous symbol length indicated by the network device.
  • the fourth time domain unit is the starting symbol position of the uplink data channel that does not satisfy the sending in the first i time domain units is the starting symbol position indicated by the network device, the sending The length of the uplink data channel is the length of consecutive symbols indicated by the network device, and the time domain unit of the first type of RV is used, and the first type of RV is an RV that supports self-decoding.
  • the sent uplink data channel is the continuous symbol length indicated by the network device, and the uplink data channel sent by the time domain unit behind the time domain unit still uses the time domain unit to send the RV used by the uplink data channel or the used support self-decoding RV, until the uplink data channel sent by the subsequent time domain unit can carry more data volume, for example, until the subsequent time domain unit satisfies that the starting symbol position of the sent uplink data channel is the starting symbol position indicated by the network device ,
  • the length of the sent uplink data channel is the length of consecutive symbols indicated by the network device, and the next RV is continued to be used, which is beneficial to improve the transmission performance of the uplink data channel.
  • the uplink data channel sent on the time domain unit i uses the channel corresponding to i-z in the G candidate RVs.
  • RV where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the first i in the N-Q third time domain units
  • the number of fifth time-domain units included in the domain unit, where the fifth time-domain unit is the number of uplink symbols of the uplink data channel sent in the first i time-domain units that is less than the number indicated by the network device. One-half the number of time-domain cells.
  • the fifth time domain unit is that the number of uplink symbols of the uplink data channel sent in the first i time domain units is less than half of the first number indicated by the network device, and the first number is used.
  • a time domain unit with a small amount of data carried in the sent uplink data channel such as a time domain unit in which the number of uplink symbols of the sent uplink data channel is less than half of the first number indicated by the network device
  • this time The uplink data channel sent by the time domain unit after the domain unit still uses the RV used by the time domain unit to send the uplink data channel or the RV used to support self-decoding, until the uplink data channel sent by the subsequent time domain unit can carry the RV.
  • the number of uplink symbols of the uplink data channel sent by the subsequent time domain unit is not less than half of the first number indicated by the network device, and continuing to use the next RV is conducive to improving the transmission performance of the uplink data channel.
  • the uplink data channel sent on the time domain unit i uses the channel corresponding to i-z in the G candidate RVs.
  • RV where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the first i in the N-Q third time domain units
  • the sixth time domain unit is that the number of uplink symbols occupied by the uplink data carried in the uplink data channel sent in the first i time domain units is less than the first number indicated by the network device. and use time domain units of the first type of RV, which are RVs that support self-decoding.
  • the number of uplink symbols occupied by the uplink data carried in the sent uplink data channel is less than half of the first number indicated by the network device.
  • the time domain unit the uplink data channel sent by the time domain unit behind the time domain unit still uses the time domain unit to send the RV used by the uplink data channel or the RV used to support self-decoding, until the following time domain unit sends
  • the uplink data channel can carry a large amount of data, for example, the number of uplink symbols occupied by the uplink data carried in the uplink data channel sent by the subsequent time domain unit is not less than half of the first number indicated by the network device , continue to use the next RV, which is beneficial to improve the transmission performance of the uplink data channel.
  • the N-Q third time domain units include that the starting symbol position of the uplink data channel that does not satisfy the sending is the starting symbol position indicated by the network device, the sending uplink data channel
  • the length of the data channel is a time domain unit of the length of consecutive symbols indicated by the network device.
  • the time domain unit that does not satisfy the starting symbol position and continuous symbol length of the uplink data channel indicated by the network device can also send the uplink data channel, which is beneficial to improve the utilization rate of the uplink symbol resources.
  • an embodiment of the present application provides an uplink transmission device, the device has a function of implementing the first aspect or any possible method in the design of the first aspect, and the function may be implemented by hardware or by The hardware executes the corresponding software implementation.
  • the hardware or software includes one or more units (modules) corresponding to the above functions, such as a transceiver unit and a processing unit.
  • the device may be a chip or an integrated circuit.
  • the apparatus includes a processor and an interface circuit, the processor is coupled to the interface circuit, and is used for implementing the method described in the above first aspect or any possible design of the first aspect function.
  • the interface circuit can be a transceiver or an input-output interface.
  • the apparatus may further comprise a memory storing a program executable by the processor for implementing the functions of the method described in the first aspect or any possible design of the first aspect above.
  • the apparatus may be a terminal device.
  • embodiments of the present application provide a computer-readable storage medium on which a computer program or instruction is stored.
  • the computer program or instruction When the computer program or instruction is run on a computer, the computer can execute the first aspect or the first any possible design method of the aspect.
  • an embodiment of the present application provides a computer program product, including a computer program or an instruction, when the computer program or instruction is run on a computer, the first aspect or any of the possible first aspects can be implemented. method described in the design.
  • an embodiment of the present application further provides a chip system, where the chip system includes: a processor and an interface, where the processor is configured to call and run an instruction from the interface, and when the processor executes the instruction, it can The method described in the above first aspect or any possible design of the first aspect is implemented.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a PUSCH transport block coding process provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of a redundant version application provided by an embodiment of the present application.
  • FIG. 4 is one of schematic diagrams of PUSCH mapping patterns provided by an embodiment of the present application.
  • FIG. 5 is the second schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 6 is a third schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 7 is a fourth schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 8 is a fifth schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of an uplink transmission method provided by an embodiment of the present application.
  • FIG. 10 is a sixth schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 11 is a seventh schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 12 is an eighth schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 13 is a ninth schematic diagram of a PUSCH mapping pattern provided by an embodiment of the present application.
  • FIG. 14 is one of the schematic diagrams of RV applications provided by the embodiment of the present application.
  • FIG. 15 is the second schematic diagram of the RV application provided by the embodiment of the present application.
  • FIG. 16 is the third schematic diagram of the RV application provided by the embodiment of the present application.
  • FIG. 17 is a schematic diagram of an uplink transmission apparatus provided by an embodiment of the present application.
  • FIG. 18 is the second schematic diagram of an uplink transmission apparatus provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as a fifth generation (5th generation, 5G) mobile communication system or a new radio (NR) system, or applied to future communication systems or other similar Communication systems, such as 6G systems, etc.
  • the structure of the communication system to which the embodiments of the present application are applied may be as shown in FIG. 1
  • the communication system includes a network device and at least one terminal device (the terminal device 1 and the terminal device 2 shown in FIG. 1 ) , and may also include core network equipment.
  • the terminal equipment can be connected with the network equipment in a wireless manner, and the network equipment can be connected with the core network equipment in a wireless or wired manner.
  • the core network device and the network device may be independent and different physical devices, or the functions of the core network device and the logical functions of the network device may be integrated on the same physical device, or they may be a physical device.
  • the device integrates the functions of part of the core network device and the function of part of the network device.
  • Terminal equipment can be fixed or movable.
  • the wireless link between the above devices can communicate through licensed spectrum (licensed spectrum), can also communicate through unlicensed spectrum (unlicensed spectrum), and can also communicate through licensed spectrum and unlicensed spectrum at the same time.
  • the wireless link between the devices can communicate through the frequency spectrum below 6 gigahertz (GHz), and can also communicate through the frequency spectrum above 6GHz, and can also use the frequency spectrum below 6GHz and the frequency spectrum above 6GHz to communicate at the same time.
  • This application does not limit the spectrum resources used by the wireless link.
  • the above communication system can be applied to downlink signal transmission (also referred to as downlink transmission), uplink signal transmission (also referred to as uplink transmission), or device to device (device to device, D2D) signals Transmission (may also be referred to as sideline transmission).
  • the sending device is a network device, and the corresponding receiving device is a terminal device.
  • the sending device is a terminal device, and the corresponding receiving device is a network device.
  • D2D signal transmission the sending device is a terminal device, and the corresponding receiving device is also a terminal device.
  • FIG. 1 is only an example of the architecture of a communication system, and the communication system may also include other devices, such as a wireless relay device and a wireless backhaul device, which are not shown in FIG. 1 .
  • the embodiments of the present application do not limit the number of network devices, core network devices, and terminal devices included in the communication system.
  • a terminal device is a device with wireless transceiver functions, which can communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
  • the terminal device may also be referred to as a terminal (terminal), user equipment (UE), a mobile station (mobile station, MS), a mobile terminal (mobile terminal, MT), and the like.
  • a network device also called an access network device or a wireless access network device, is a device that provides a wireless communication function for a terminal device and can be used to communicate with the terminal device.
  • radio access network equipment includes but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), Node B ( node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit) , BBU), transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), mobile switching center, base station in future mobile communication system or wireless fidelity (wireless fidelity, WiFi) access in system Nodes, etc., the present application does not limit the specific technology and specific device form adopted by the network device.
  • network equipment and terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle; can also be deployed on water; can also be deployed in the air on aircraft, balloons and artificial satellites.
  • This application does not limit the application scenarios of network devices and terminal devices.
  • time slot (slot), a time slot is defined in NR to consist of 14 orthogonal frequency division multiplexing (orthogonal frequency-division multiplexing, OFDM) symbols, for the convenience of description, in the subsequent description of this application, also The OFDM symbol is simply referred to as a symbol and will not be described otherwise.
  • a time slot can include downlink symbols (downlink symbols), uplink symbols (uplink symbols), and flexible symbols (flexible symbols), and downlink symbols cannot be used for uplink transmission; uplink symbols cannot be used for downlink transmission; and flexible symbols are both Can be used for downlink or uplink transmission.
  • NR supports one time slot for uplink transmission, recorded as uplink (uplink, U) slot; supports one time slot for downlink transmission, recorded as downlink (downlink, D) time slot; also supports one time slot with both uplink and downlink configuration, denoted as special (special, S) time slot. If a time slot is all downlink symbols, the time slot is called a downlink time slot, and if a time slot is all uplink symbols, the time slot is called an uplink time slot. If a time slot contains two or more types of symbols among uplink symbols, downlink symbols and flexible symbols, the time slot is called a special time slot.
  • a typical time division duplex (time division duplex, TDD) system slot configuration format including DDDSU, DDDSUDDSUU, DDDDDDDDUU, etc.
  • the time slot is repeated according to the format of DDDSU, DDDSUDDSUU, etc.
  • network equipment in NR supports three signaling methods for notifying terminal equipment of uplink and downlink resources:
  • Dynamic signaling informs the scheduled terminal equipment: The terminal equipment monitors the downlink control signaling, and performs uplink or downlink transmission according to the scheduling grant or scheduling allocation in the downlink control signaling.
  • RRC radio resource control
  • SFI dynamic slot format indicator
  • SFI can indicate whether a symbol is a downlink, uplink or flexible symbol in one or more time slots.
  • SFI cannot change the semi-static RRC signaling and the uplink and downlink configuration of the uplink and downlink dynamic signaling configuration.
  • the slot format may be indicated by the slot formats for normal cyclic prefix shown in Table 1 below.
  • the left side in Table 1 is the format index, and the right side is the specific symbol allocation in a time slot under this index, where "D" represents the downlink symbol, "U” represents the uplink symbol, and "F” represents the flexible symbol, symbol number in a slot represents the symbol number in the slot.
  • the uplink channel includes physical uplink control channel (physical uplink control channel, PUCCH), PUSCH and physical random access channel (physical random access channel, PRACH); uplink signal includes sounding reference signal (sounding reference signal) signal, SRS), demodulation reference signal (demodulation reference signal, DM-RS), and phase tracking reference signal (phase-tracking reference signal, PT-RS).
  • the uplink DM-RS is transmitted along with the PUCCH and the PUSCH, and its time-frequency resources occupy a part of the PUCCH or the PUSCH.
  • PUSCH there are three types of PUSCH transmission in NR:
  • Each PUSCH transmission is scheduled with the physical layer indicating downlink control information (DCI).
  • DCI downlink control information
  • Configured grant Type 1 Semi-static scheduling, the terminal device receives the high-level configuration from the network device (including the high-level parameter configuredGrantConfig of rrc-ConfiguredUplinkGrant), and does not receive the physical layer indication DCI, which is called “configured" in the protocol.
  • Uplink grant (configured uplink grant)" wherein, rrc-ConfiguredUplinkGrant represents the uplink grant of the radio resource control configuration, and configuredGrantConfig represents the configuration grant configuration.
  • the upper layer of the network device configures some semi-persistent resources for the terminal device. If the terminal device has uplink data to send, it can use these resources to send the PUSCH; if there is no uplink data to send, the PUSCH is not sent.
  • Configured grant Type 2 The terminal device first receives the high-level configuration (excluding the high-level parameter configuredGrantConfig of rrc-ConfiguredUplinkGrant), and then instructs the physical layer to activate or deactivate the DCI, which is called "uplink based on L1 signaling configuration" in the protocol.
  • Road Grant (configured uplink grant based on L1 signalalling)".
  • the upper layer of the network device configures some semi-persistent resources for the terminal device, and then activates/deactivates it by the physical layer signaling of the network device: the behavior of the terminal device when activated is similar to the second PUSCH transmission; , these resources cannot be used.
  • the PUSCH transport block goes through the coding process shown in FIG. 2 .
  • the information sender can add a cyclic redundancy check (CRC) code to the transport block (TB), divide the transport block with the CRC code added into one or more code blocks, and then divide the obtained The code block adds the CRC code.
  • CRC cyclic redundancy check
  • channel coding is performed on the code block to which the CRC code is added, and after channel coding, the obtained code block is subjected to rate matching, including repetition or puncturing, to match the number of bits of the air interface resource. After that, code block concatenation is performed, and finally the transmission can be completed.
  • the bit rate of the mother code for channel coding is generally 1/3 or 1/5. Bits after channel coding (such as bits in a code block obtained after channel coding) are subjected to rate matching, that is, repetition or puncturing is performed to match the number of bits of the air interface resource. Different RVs may be used for rate matching, and different RVs may contain different channel-coded bits.
  • Ncb the bit length after channel coding
  • the corresponding information bit length is 1/3Ncb
  • the corresponding air interface bit number is 4/9Ncb (that is, the mother code rate 1/3 divided by the code rate R, the code rate R can be It is understood as the number of air interface bits/the number of bits of the mother code)
  • the encoded bits corresponding to different RVs that is, different RV versions, such as RV0, RV1, RV2, RV3 are shown in the rectangular area corresponding to the RV in Figure 3. out.
  • the information bit before the encoding of the mother code is called the system bit.
  • the first 1/3 bit after encoding is the system bit. If you want to self-decode (self-decoding means that according to this RV, it may be possible to successfully decode without combining other RVs), then the RV needs to contain a complete system bit. As shown in Figure 3, RV0 contains a complete system bit. Self-decoding is supported.
  • the PUSCH repetition type (type) in NR is divided into two types: PUSCH repetition type A and PUSCH repetition type B.
  • the former is adopted in the standard Rel-15 version, and the latter is newly introduced in the standard Rel-16 version. of.
  • the time slot K s in which the terminal device starts to transmit PUSCH is determined by K 2 , where K 2 is the time slot offset, and K s can be determined by the following formula.
  • n represents the time slot where the scheduled DCI is located
  • ⁇ PUSCH represents the subcarrier spacing configuration of the PUSCH
  • ⁇ PDCCH represents the subcarrier spacing configuration of the physical downlink control channel (PDCCH)
  • PDCCH represents the subcarrier spacing configuration offset of PDCCH
  • PUSCH represents the subcarrier spacing configuration offset of PUSCH.
  • PUSCH repetition type A is repeated K times in a time slot, and the start symbol (S) is the start position of the relative time slot; L is the number of consecutive symbols allocated to PUSCH, starting from S; S and L are determined by the start and length The indicator (start and length indicator, SLIV) to decide.
  • K>1 the same symbol assignment is applied over K consecutive slots.
  • PUSCH repetition type B is repeated K times in the unit of L indicated by the network device, and the start symbol (S) is the start position of the relative time slot; L is the number of consecutive symbols allocated to PUSCH, starting from S; S and L are respectively It is given by the start symbol (start symbol) and length (length) of the index row of the resource allocation table.
  • PUSCH repetition type B is more flexible than PUSCH repetition type A. There may be a repetition (repetition) crossing the slot boundary, or a repetition containing invalid symbols (invalid symbol(s)). In this case, the repetition will be Split occurs. In the protocol, the repetition before splitting is called nominal repetition (nominal repetition), and the repetition after splitting is called actual repetition (actual repetition).
  • the number of repetitions K indicated by the network device refers to the total number of nominal repetitions.
  • 4 nominal repetitions are split into 6 actual repetitions due to the existence of slot boundaries.
  • the terminal device regards the S and L defined in Table 2 below as a valid allocation, referring to Table 6.1.2.1-1 in the 3GPP protocol: valid S and L combination (valid S and L combinations).
  • the terminal device will repeat the TB in K consecutive time slots, and each time slot in the K consecutive time slots applies the same symbol allocation.
  • Redundancy version for PUSCH transmission where rv id indicated by the DCI scheduling the PUSCH represents the rv id indicated by the DCI scheduling the PUSCH, rv id to be applied to n th transmission occasion (repetition type A) or n th actual repetition (repetition type B) represents the rv id applied to the nth transmission occasion (repetition type A) or the nth actual repetition (repetition type B).
  • the RV is applied to the nth actual repetition (including the omitted actual repetition), which is determined according to Table 3 above.
  • PUSCH repetition type A In addition, in the discussion of standard Rel-17 coverage enhancement (CE), in order to make better use of uplink symbols, some companies proposed the enhancement of PUSCH repetition type A, including: increasing the maximum number of repetitions; based on the available uplink time slots Calculate the number of repetitions; and flexible symbol resource allocation for different time slots (that is, different numbers of uplink symbol resources can be allocated for different time slots), and write a technical report (TR) in the RAN1#103-e conference. Also for PUSCH repetition type A, some companies propose to transmit DM-RS in special time slots and perform channel estimation across time slots/repetitions, that is, DMRS-bundling.
  • the DCI format (format) 2_4 is used to notify the terminal device to cancel the corresponding uplink transmission physical resource block (PRB) and symbol, which transmits one or more cancellation indications (cancellation indication, CI).
  • DCI format 2_4 is for the CI of the serving cell, and is suitable for PUSCH transmission or SRS transmission in the serving cell. This application mainly focuses on the impact on PUSCH transmission.
  • the terminal device When the terminal device detects DCI format 2_4, if it indicates that on the corresponding PRB and symbol, it overlaps with the time-frequency resources of the PUSCH repeated transmission, then cancel a PUSCH transmission, or an actual repetition of a PUSCH transmission. After the terminal device detects the DCI format 2_4, the PUSCH appears before the cancellation instruction effective time (T proc,2 ), and the terminal device does not have time to process the CI and will transmit the PUSCH. If the terminal device cancels a PUSCH transmission based on the indication of DCI format 2_4, the terminal device does not expect to be scheduled by the second DCI format, and transmits PUSCH again on the symbol of the canceled PUSCH transmission.
  • T proc,2 cancellation instruction effective time
  • PUSCH repetition type A when K s determined by K 2 indicates a certain time slot, and K time slots from this time slot, including time slots that do not meet SLIV, time slots that cancel PUSCH transmission due to CI etc., PUSCH will not be transmitted on these time slots, and the actual number of repeated transmissions of PUSCH repetition type A is less than K, which will cause the transmission performance of PUSCH to decrease; in addition, RV has nothing to do with the actual repeated transmission on the time slot.
  • An RV that can support self-decoding (such as RV0) may reduce the number of times of transmission, or even not send it, reducing the transmission performance of the PUSCH. As shown in FIG.
  • the nominal repetition does not contain actual repetitions, and the number of symbols actually transmitted in the row will also be reduced, resulting in poor PUSCH performance.
  • L>1 the actual repetition of a single symbol omitted, and the actual repetition canceled by the influence of CI will also reduce the number of symbols actually transmitted and reduce the transmission performance of PUSCH.
  • the RV has nothing to do with whether there is actual repeated transmission in the actual repetition, and the RV (such as RV0) that can support self-decoding may reduce the number of transmissions, or even not send, which reduces the transmission performance of the PUSCH.
  • the uplink symbols can be counted directly, and the repeated transmission will not stop until K*L symbols are used for uplink transmission, and the RV is used according to the transmission timing of the actual transmission; for the PUSCH repetition type B. Directly count the uplink symbols, and stop the repeated transmission until K*L symbols are used for uplink transmission.
  • the RV is used according to the actual repetition of the actual transmission, but the repeated transmission of PUSCH is affected by the time slot structure, CI, etc., and directly Upstream symbol counting is very complex and difficult to implement.
  • the purpose of this application is to provide an uplink transmission scheme.
  • the uplink data channel is, for example, an uplink data channel of the physical layer, such as PUSCH, or can also be an uplink data channel of other layers, such as an uplink data channel of the MAC layer, etc.
  • the uplink data channel is PUSCH as an example, and the resources of the uplink data channel are also taken as an example of the PUSCH resources. That is, the PUSCH described later can be replaced with an uplink data channel.
  • FIG. 9 is a schematic diagram of an uplink transmission method provided by an embodiment of the present application, and the method includes:
  • the terminal device receives first indication information and second indication information from the network device, where the first indication information indicates the repetition type and repetition number of the PUSCH, and the second indication information indicates the time slot offset.
  • the network device may configure PUSCH transmission parameters for the terminal device through RRC signaling, DCI, and the like.
  • the network device can send the first indication information to the terminal device to indicate the repetition type and repetition number (K) of the PUSCH through RRC signaling or DCI, etc., and send the second indication information to the terminal device to indicate the time slot offset (K 2 ), Such as the slot offset of PUSCH.
  • the network device can also send the indication information to the terminal device through RRC signaling or DCI for indicating the starting symbol position (S) and the continuous symbol length (L) of the PUSCH.
  • the network device can pass The RRC signaling or DCI sends the SLIV to the terminal equipment to indicate the starting symbol position (S) and the continuous symbol length (L) of the PUSCH of the terminal equipment.
  • the terminal device determines, according to the time slot offset, a starting time domain unit capable of sending the PUSCH.
  • the time domain unit when the PUSCH repetition type is repetition type A, the time domain unit is a time slot; when the PUSCH repetition type is repetition type B, the time domain unit is at least one symbol smaller than one time slot .
  • the time slot (K s ) in which the terminal device starts to transmit PUSCH is determined by the time slot offset (K 2 ), and the specific terminal device is determined according to the time slot offset (K 2 )
  • K 2 the time slot offset
  • the terminal device After the terminal device determines the time slot to start transmitting PUSCH, in the case of PUSCH repetition type A, the terminal device can use the time slot that starts to transmit PUSCH as the starting time domain unit that can transmit PUSCH, and can start the PUSCH according to the terminal device PUSCH starting symbol position. , and further determine the start symbol that can send the PUSCH in the start time domain unit.
  • the terminal device can repeat the first actual repetition of the start symbol that can transmit PUSCH in the time slot that starts transmitting PUSCH according to the time slot that starts transmitting PUSCH and the position of the terminal device's PUSCH start symbol As a starting time domain unit, at least one symbol less than or equal to one slot is included in the actual repetition.
  • the terminal device determines M first time domain units to send the PUSCH to the network device.
  • N time domain units there are consecutive N time domain units from the starting time domain unit to the Mth first time domain unit, and the N time domain units include Q second time domain units that do not send PUSCH , the M is greater than or equal to the number of repetitions indicated by the network device, the Q is less than or equal to N-M, and M, N, and Q are integers.
  • the terminal device in addition to sending the PUSCH to the network device in the M first time domain units, the terminal device for N-M time domain units other than the M first time domain units in the N time domain units domain unit, the terminal device may not send the PUSCH at all, or may send the PUSCH to the network device in some or all of the N-M time domain units.
  • the terminal device may also transmit the PUSCH by using some or all of the time-domain units including uplink symbols in the N-M time-domain units.
  • the time domain unit is a time slot.
  • the terminal device can only count the first time slot that has sent PUSCH and satisfies certain PUSCH transmission conditions, until the first time slot.
  • the number M of slots is greater than or equal to the number of repetitions of the PUSCH indicated by the network device.
  • the terminal device may determine M according to the number of repetitions (K) indicated by the network device. For example, if M is determined to be equal to K, the specific method of determining M according to the number of repetitions (K) indicated by the network device may be defined by the protocol or by the network device. It is indicated that the embodiments of the present application are not limited. The following describes with specific examples:
  • the first time slot is the time slot in which the terminal device sends the PUSCH to the network device.
  • the terminal device for a time slot that satisfies the SLIV of PUSCH, although the network device sends a CI to the terminal device indicating that the time slot contains a symbol that cannot perform uplink transmission, the terminal device has already started to send PUSCH before the effective time of the CI. Then the terminal device normally sends PUSCH in this time slot, the value of m is +1, that is, for a certain time slot, if the network device sends the effective time of CI to the terminal device, after the terminal device starts to send PUSCH, the terminal device can consider this time slot. Symbols that are not indicated by CI include symbols that cannot be transmitted upstream.
  • the terminal device can also use the uplink symbol contained in the time slot to send the PUSCH, that is, for each time slot starting from the initial time slot, If the time slot does not meet the SLIV of PUSCH, but contains uplink symbols and the time slot is not indicated by CI to contain symbols that cannot be used for uplink transmission, the terminal device can also send the PUSCH to the network device in this time slot (including the uplink symbols) , and set m+1.
  • the first time slot is a time slot of the PUSCH sent by the terminal device to the network device that is not fully occupied by the DM-RS.
  • the time slot in which the terminal device sends the PUSCH to the network device may satisfy the SLIV of the PUSCH, or may not satisfy the SLIV of the PUSCH.
  • the time domain resources of the PUSCH sent by the terminal equipment to the network equipment are all occupied by the DM-RS, and the value of m+0;
  • the terminal equipment sends to the network equipment
  • the time domain resources of the PUSCH are not all occupied by the DM-RS, the value of m+1;
  • the fourth time slot in Figure 10 the time domain resources of the PUSCH sent by the terminal device to the network device are not all occupied by the DM-RS, m
  • m The value of +1; until m equals M.
  • the first time slot is a time slot in which the number of uplink symbols of the PUSCH sent by the terminal device to the network device is not less than half of the first number indicated by the network device.
  • the time slot in which the terminal device sends the PUSCH to the network device may satisfy the SLIV of the PUSCH, or may not satisfy the SLIV of the PUSCH.
  • the number of uplink symbols of the PUSCH sent by the terminal device to the network device is not less than half of the first number indicated by the network device, The value of m+1; in the second time slot in Figure 11, the number of uplink symbols of the PUSCH sent by the terminal device to the network device is less than half of the first number indicated by the network device, the value of m+0; the third time slot in Figure 11 time slots, the number of uplink symbols of the PUSCH sent by the terminal device to the network device is not less than half of the first number indicated by the network device, the value of m+1; in the fourth time slot in Figure 11, the terminal device sends to the network device The number of uplink symbols of the PUSCH is not less than half of the first number indicated by the network device, the value of m+1; until m is equal to M.
  • the first time slot is a time slot in which the number of uplink symbols occupied by the uplink data carried in the PUSCH sent by the terminal device to the network device is not less than half of the first number indicated by the network device.
  • the time slot in which the terminal device sends the PUSCH to the network device may satisfy the SLIV of the PUSCH, or may not satisfy the SLIV of the PUSCH.
  • the number of symbols (uplink symbols not occupied by DM-RS) is not less than half of the first number indicated by the network device, then the value of m+1; if the uplink data carried in the PUSCH sent by the terminal device to the network device in this timeslot
  • the number of occupied uplink symbols is less than half of the first number indicated by the network device (including not sending PUSCH to the network device), then the value of m+0 until m is equal to M, where the first number can be the PUSCH indicated by the network device
  • the continuous symbol length (L) of can also be indicated by the network device through RRC signaling, DCI, etc.
  • the time domain unit is the actual repetition.
  • the terminal device can only count the first actual repetition that has sent the PUSCH and satisfies certain PUSCH transmission conditions, until the first actual repetition.
  • the number M of repetitions is greater than or equal to the number of repetitions of the PUSCH indicated by the network device.
  • the terminal device may determine the number M of the first actual repetitions according to the number of repetitions (K) of the PUSCH indicated by the network device, for example, M may be equal to K, or the number of nominal repetitions corresponding to the M first actual repetitions may be equal to K , Specifically, the manner of determining M according to the number of repetitions (K) indicated by the network device may be defined by the protocol, or may be indicated by the network device, which is not limited in this embodiment of the present application. The following is combined with specific examples to illustrate:
  • the first actual repetition is the actual repetition in which the terminal device sends the PUSCH to the network device.
  • the number of repetitions corresponding to the M first actual repetitions equal to the number of repetitions (K) of the PUSCH indicated by the network device as an example, as shown in FIG. , compared with the existing uplink transmission scheme, the number of repetitions is not calculated for the actual repetition 1 and actual repetition 2 (nominal repetition 1 and nominal repetition 2) in which PUSCH is not sent in the existing uplink transmission scheme, which is conducive to ensuring that a sufficient number of Uplink data, thereby improving transmission performance.
  • the first actual repetition is the actual repetition of the PUSCH sent by the terminal device to the network device that is not fully occupied by the DM-RS.
  • the first actual repetition is an actual repetition in which the number of uplink symbols of the PUSCH sent by the terminal device to the network device is not less than half of the first number indicated by the network device.
  • the actual repetition is that the number of uplink symbols of the PUSCH sent by the terminal device to the network device is not less than half of the first number indicated by the network device, and the value of m is +1;
  • the number of uplink symbols of PUSCH is less than half of the first number indicated by the network device, the value of m+0; the fifth actual repetition in Figure 13, the number of uplink symbols of PUSCH
  • the first actual repetition is an actual repetition in which the number of uplink symbols occupied by the uplink data carried in the PUSCH sent by the terminal device to the network device is not less than half of the first number indicated by the network device.
  • the number of symbols is not less than half of the first number indicated by the network device, then the value of m+1; if the number of uplink symbols occupied by the uplink data carried in the PUSCH sent by the actual repeat terminal device to the network device is less than the number indicated by the network device half of the first number (including not sending PUSCH to the network device), then the value of m + 0 until m is equal to M, where the first number can be the continuous symbol length (L) of the PUSCH indicated by the network device, or can be determined by The network equipment is indicated by RRC signaling, DCI, etc.
  • the terminal device sends the RV used by the PUSCH to the network device in the N-Q third time domain units, which can be based on the third indication from the network device.
  • the configuration of the RV indicated by the information is determined, wherein the configuration of the RV includes G candidate RVs, and G can be a value such as 4 or 6.
  • the network device may send the third indication information to the terminal device through RRC signaling, DCI, and the like.
  • the network device may use the RV configuration manner shown in Table 3 above to indicate the RV configuration to the terminal device.
  • the PUSCH sent on the time domain unit i uses the RV corresponding to i in the G candidate RVs, where i is 0, 1, 2, 3...N-Q-1.
  • each time domain unit in the NQ third time domain units can be used as a transmission opportunity, Used for RV determination.
  • Time domain unit 0 in the NQ third time domain units is transmission opportunity 0
  • time domain unit 1 is transmission opportunity 1
  • time domain unit 2 is transmission opportunity 2
  • ... time domain unit NQ-1 is transmission opportunity NQ-1;
  • each time-domain unit in the NQ third time-domain units may be used as an actual repetition for RV determination.
  • time domain unit 0 is actual repetition
  • time domain unit 1 is actual repetition 1
  • time domain unit 2 is actual repetition 2, . . .
  • time domain unit NQ-1 is actual repetition NQ-1.
  • the indicated 4 candidate RVs are RV0, RV2, RV3, RV1.
  • the data sent on the time domain unit i The PUSCH uses the RV corresponding to i in the 4 candidate RVs, which can be specifically determined according to the value of i mod 4.
  • the PUSCH sent on the time domain unit 0 in the NQ third time domain units uses RV0, time domain unit 1 PUSCH sent on RV2 is used.
  • each time domain unit in the N-Q third time domain units can be used as a transmission opportunity for RV determination; for PUSCH repetition type B, N-Q third time domain units Each time domain cell in the cell can be used as an actual repetition for RV determination.
  • the PUSCH sent on the time domain unit i uses the RV corresponding to i-z in the G candidate RVs, where i is 0, 1, 2, 3...N-Q -1, when i is 0, z is 0; when i is not 0, z is the number of fourth time-domain units included in the first i time-domain units in the N-Q third time-domain units.
  • the four time domain units are the time domains in which the first i time domain units do not meet the requirement that the starting symbol position of the sent PUSCH is the starting symbol position indicated by the network device, and the length of the sent PUSCH is the continuous symbol length indicated by the network device. unit. (Applies to PUSCH transmission type A).
  • the indicated 4 candidate RVs are RV0, RV2, RV3, RV1, and the first 2 of the NQ third time domain units
  • the number of the fourth time-domain units included in the domain unit is 1, and the value of the RV used by time-domain unit 2 in the NQ third time-domain units to send the PUSCH is the RV corresponding to 2-1, that is, RV2.
  • the fourth time-domain unit may also be only the starting symbol position of the PUSCH that does not meet the requirements in the first i time-domain units to be sent is the starting symbol position indicated by the network device, and the length of the sent PUSCH is The continuous symbol length indicated by the network equipment, and the time domain unit of the first type of RV is used, and the first type of RV is an RV that supports self-decoding, such as RV0 including the complete system bit in FIG. 3 .
  • the third indication information uses rv id in Table 3, where rv id is 0 as an example, where RV0 and RV3 are RVs that support self-decoding.
  • the PUSCH sent on time domain unit 0 uses the RV corresponding to 0, that is, RV0.
  • Time domain unit 0 is a time domain unit that does not satisfy the starting symbol position of the sent PUSCH as the starting symbol position indicated by the network device, the length of the sent PUSCH is the continuous symbol length indicated by the network device, and the first type of RV is used,
  • the PUSCH sent on time domain unit 1 still uses the RV corresponding to 0, that is, RV0.
  • the time domain unit 2 is a time domain unit that satisfies that the starting symbol position of the sent PUSCH is the starting symbol position indicated by the network device, and the length of the sent PUSCH is the continuous symbol length indicated by the network device.
  • the PUSCH sent on the time domain unit 2 Use the RV corresponding to 1, ie RV2.
  • the PUSCH sent on the time domain unit i uses the RV corresponding to i-z in the G candidate RVs, where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the fifth time domain included in the first i time domain units in the N-Q third time domain units
  • the number of units, the fifth time domain unit is a time domain unit in which the number of uplink symbols of the PUSCH sent in the first i time domain units is less than half of the first number indicated by the network device. (Applicable to PUSCH transmission type A and PUSCH transmission type B).
  • the fifth time domain unit may only be that the number of uplink symbols of the PUSCH sent in the first i time domain units is less than half of the first number indicated by the network device, and the A time domain unit of a type of RV, the first type of RV being an RV that supports self-decoding.
  • the PUSCH sent on time domain unit 0 uses the RV corresponding to 0, that is, RV0.
  • Time domain unit 0 is a time domain unit in which the number of uplink symbols of the sent PUSCH is not less than half of the first number indicated by the network device, and the PUSCH sent on time domain unit 1 uses an RV corresponding to 1, that is, RV2.
  • Time domain unit 1 is that the number of uplink symbols of the PUSCH sent is less than half of the first number indicated by the network device, but the time domain unit of the first type of RV is not used, and the PUSCH sent on time domain unit 2 uses the RV corresponding to 2, Namely RV3.
  • Time domain unit 2 is a time domain unit in which the number of uplink symbols of the PUSCH sent is not less than half of the first number indicated by the network device, and the PUSCH sent on time domain unit 3 uses the RV corresponding to 3, that is, RV1.
  • Mode 3 For the time domain unit i in the N-Q third time domain units, the PUSCH sent on the time domain unit i uses the RV corresponding to i-z in the G candidate RVs, where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the sixth time domain included in the first i time domain units in the N-Q third time domain units
  • the number of units, the sixth time domain unit is when the number of uplink symbols occupied by the uplink data carried in the PUSCH sent in the first i time domain units is less than half of the first number indicated by the network device domain unit.
  • the sixth time domain unit is that the number of uplink symbols occupied by the uplink data carried in the PUSCH sent in the first i time domain units is less than the first number indicated by the network device and use time domain units of the first type of RV, which are RVs that support self-decoding.
  • the PUSCH sent on time domain unit 0 uses the RV corresponding to 0, that is, RV0.
  • the number of uplink symbols occupied by the uplink data carried in the PUSCH sent by time domain unit 0 is less than half of the first number indicated by the network device, and the first type of RV is used, and the PUSCH sent by time domain unit 1 still uses the corresponding 0 RV, or RV0.
  • the number of uplink symbols occupied by the uplink data carried in the PUSCH sent by the time domain unit 1 is not less than half of the first number indicated by the network device, and the PUSCH sent by the time domain unit 2 uses the RV corresponding to 1, that is, RV2.
  • the number of uplink symbols occupied by the uplink data carried in the PUSCH sent by the time domain unit 2 is less than half of the first number indicated by the network device, but the first type of RV is not used, and the PUSCH sent by the time domain unit 3 uses the corresponding 2 RV, or RV3.
  • the number of uplink symbols occupied by the uplink data carried in the PUSCH sent by the time domain unit 3 is not less than half of the first number indicated by the network device, and the PUSCH sent by the time domain unit 4 uses the RV corresponding to 3, that is, RV1.
  • the network device After receiving the PUSCH from the terminal device, the network device can obtain the uplink data carried in the PUSCH from the PUSCH.
  • each network element includes a corresponding hardware structure and/or software module (or unit) for performing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • FIG. 17 and FIG. 18 are schematic structural diagrams of possible uplink transmission apparatuses provided by embodiments of the present application. These uplink transmission apparatuses can be used to implement the functions of the terminal equipment in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.
  • the uplink transmission apparatus may be the terminal device in FIG. 9 , or may be a module (eg, a chip) applied to the terminal device.
  • the uplink transmission apparatus 1700 may include: a processing unit 1702 and a transceiver unit 1703 , and may also include a storage unit 1701 .
  • the uplink transmission apparatus 1700 is configured to implement the function of the terminal device in the method embodiment shown in FIG. 9 above.
  • the processing unit 1702 is used to implement corresponding processing functions.
  • the transceiver unit 1703 is used to support the communication between the uplink transmission device 1700 and other network entities.
  • the storage unit 1701 is used for storing program codes and/or data of the uplink transmission apparatus 1700 .
  • the transceiving unit 1703 may include a receiving unit and/or a sending unit, respectively configured to perform receiving and sending operations.
  • the transceiver unit 1703 is configured to receive the first indication information and the second indication information from the network device, the first indication information Indicates the repetition type and repetition times of the uplink data channel, and the second indication information indicates a time slot offset;
  • the processing unit 1702 is configured to determine a starting time domain unit capable of sending the uplink data channel according to the time slot offset The processing unit 1702 is further configured to start with the initial time domain unit, and determine that M first time domain units send the uplink data channel to the network device through the transceiver unit 1703, wherein the The starting time domain unit is continuous N time domain units from the Mth first time domain unit, and the N time domain units include Q second time domain units that do not transmit the uplink data channel unit, the M is greater than or equal to the number of repetitions indicated by the network device, the Q is less than or equal to N-M, and in the case that the repetition type is repetition type A, each of the N
  • the time domain resources of the uplink data channel sent in each first time domain unit are not fully occupied by the demodulation reference signal DM-RS; or, in each first time domain unit
  • the number of uplink symbols of the uplink data channel sent in the network device is not less than half of the first number indicated by the network device; or, the uplink data carried in the uplink data channel sent in each first time domain unit
  • the number of occupied uplink symbols is not less than half of the first number indicated by the network device.
  • the transceiver unit 1703 is further configured to receive third indication information from the network device, where the third indication information indicates the configuration of the redundancy version RV, and the configuration of the RV includes G candidate RVs;
  • the transceiver unit 1703 sends the uplink data channel to the network device in the N-Q third time domain units: specifically configured to send the N-Q third time domain units to the network device according to the configuration of the RV.
  • the uplink data channel is sent.
  • the uplink data channel sent on the time domain unit i uses the channel corresponding to i in the G candidate RVs RV, where i is 0, 1, 2, 3...N-Q-1.
  • the uplink data channel sent on the time domain unit i uses the channel corresponding to i-z in the G candidate RVs.
  • RV where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the first i in the N-Q third time domain units
  • the number of fourth time-domain units included in the time-domain unit, where the fourth time-domain unit is the starting symbol position of the uplink data channel that does not satisfy the transmission in the first i time-domain units, and the position is the network device
  • the indicated starting symbol position and the transmitted length of the uplink data channel are the time domain units of the continuous symbol length indicated by the network device.
  • the fourth time domain unit is the starting symbol position of the uplink data channel that does not meet the requirements for sending in the first i time domain units is the starting symbol position indicated by the network device
  • the length of the transmitted uplink data channel is the length of consecutive symbols indicated by the network device, and the time domain unit of the first type of RV is used, and the first type of RV is an RV that supports self-decoding.
  • the uplink data channel sent on the time domain unit i uses the channel corresponding to i-z in the G candidate RVs.
  • RV where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the first i in the N-Q third time domain units
  • the number of fifth time-domain units included in the domain unit, where the fifth time-domain unit is the number of uplink symbols of the uplink data channel sent in the first i time-domain units that is less than the number indicated by the network device. One-half the number of time-domain cells.
  • the fifth time domain unit is that the number of uplink symbols of the uplink data channel sent in the first i time domain units is less than half of the first number indicated by the network device, And use the time domain unit of the first type of RV, which is an RV that supports self-decoding.
  • the uplink data channel sent on the time domain unit i uses the channel corresponding to i-z in the G candidate RVs.
  • RV where i is 0, 1, 2, 3...N-Q-1, when i is 0, z is 0; when i is not 0, z is the first i in the N-Q third time domain units
  • the sixth time domain unit is that the number of uplink symbols occupied by the uplink data carried in the uplink data channel sent in the first i time domain units is less than the number indicated by the network device and use time domain units of the first type of RV, which are RVs that support self-decoding.
  • the N-Q third time domain units include that the starting symbol position of the uplink data channel that does not satisfy the sending is the starting symbol position indicated by the network device, the sending uplink data channel
  • the length of the data channel is a time domain unit of the length of consecutive symbols indicated by the network device.
  • the uplink data channel is a physical uplink shared channel PUSCH.
  • the communication device 1800 includes a processor 1810 and an interface circuit 1820 .
  • the processor 1810 and the interface circuit 1820 are coupled to each other.
  • the interface circuit 1820 can be a transceiver or an input-output interface.
  • the communication apparatus 1800 may further include a memory 1830 for storing instructions executed by the processor 1810 or input data required by the processor 1810 to execute the instructions or data generated after the processor 1810 executes the instructions.
  • the processor 1810 is used to implement the function of the above-mentioned processing unit 1702
  • the interface circuit 1820 is used to implement the function of the above-mentioned transceiver unit 1703 .
  • the terminal device chip When the above uplink transmission device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments.
  • the terminal device chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, and the information is sent by the network device to the terminal device; or, the terminal device chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal device antenna) to send information, the information is sent by the terminal equipment to the network equipment.
  • modules such as a radio frequency module or an antenna
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable aate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (programmable ROM) , PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), registers, hard disks, removable hard disks, CD-ROMs or known in the art in any other form of storage medium.
  • An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the ASIC may be located in a network device or in an end device.
  • the processor and the storage medium may also exist in the network device or the terminal device as discrete components.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs or instructions.
  • the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment, or other programmable apparatus.
  • the computer program or 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 program or instructions may be downloaded from a website, computer, A server or data center transmits by wire or wireless to another website site, 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, data center, or the like that integrates one or more available media.
  • the usable medium can be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); it can also be a semiconductor medium, such as a solid state drive (solid state drive). , SSD).
  • a magnetic medium such as a floppy disk, a hard disk, and a magnetic tape
  • an optical medium such as a digital video disc (DVD)
  • DVD digital video disc
  • it can also be a semiconductor medium, such as a solid state drive (solid state drive). , SSD).

Landscapes

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

Abstract

本申请涉及通信技术领域，公开了一种上行传输方法及装置，该方法包括：终端设备接收来自网络设备的第一指示信息和第二指示信息，所述第一指示信息指示上行数据信道的重复类型和重复次数，所述第二指示信息指示时隙偏移；根据所述时隙偏移确定能够发送所述上行数据信道的起始时域单元；以所述起始时域单元开始，确定出M个第一时域单元向所述网络设备发送所述上行数据信道，其中，从所述起始时域单元开始到第M个第一时域单元为止为连续的N个时域单元，所述N个时域单元中包括Q个未发送所述上行数据信道的第二时域单元，所述M大于或等于所述网络设备指示的所述重复次数，所述Q小于或等于N-M。用以提高上行数据信道的传输性能。

Description

一种上行传输方法及装置 技术领域
本申请涉及通信技术领域，特别涉及一种上行传输方法及装置。
背景技术
目前，终端设备向网络设备发送上行数据，可通过物理上行共享信道(physical uplink shared channel，PUSCH)发送。另外，为了提高PUSCH的传输性能，对于PUSCH重复类型A(repetition type A)，终端设备在发送PUSCH时，以新无线(NR)时隙为单位重复K次；对于PUSCH重复类型B(repetition type B)，终端设备在发送PUSCH时，以网络设备指示的PUSCH的连续符号长度为单位重复K次，其中PUSCH重复类型、PUSCH的连续符号长度以及PUSCH的重复次数(K)，终端设备可以从网络设备下发的PUSCH的传输参数中获知。
然而，PUSCH重复传输受时隙结构、取消指示(cancellation indication，CI)等因素影响，部分PUSCH重复会被取消或者忽略掉，PUSCH的实际重复次数会少于网络设备指示的PUSCH的重复次数，影响PUSCH的传输性能。
发明内容
本申请提供一种上行传输方法及装置，用以解决在上行传输时PUSCH等上行数据信道的实际重复次数会少于网络设备指示的重复次数，影响上行数据信道的传输性能的问题。
第一方面，本申请实施例提供一种上行传输方法，该方法可由终端设备来执行，该方法包括：接收来自网络设备的第一指示信息和第二指示信息，所述第一指示信息指示上行数据信道的重复类型和重复次数，所述第二指示信息指示时隙偏移；根据所述时隙偏移确定能够发送所述上行数据信道的起始时域单元；以所述起始时域单元开始，确定出M个第一时域单元向所述网络设备发送所述上行数据信道，其中，从所述起始时域单元开始到第M个第一时域单元为止为连续的N个时域单元，所述N个时域单元中包括Q个未发送所述上行数据信道的第二时域单元，所述M大于或等于所述网络设备指示的所述重复次数，所述Q小于或等于N-M，在所述重复类型为重复类型A的情况下，所述N个时域单元中每个时域单元为时隙，在所述重复类型为重复类型B的情况下，所述N个时域单元中每个时域单元为小于或等于一个时隙的至少一个符号。可选的，所述上行数据信道为PUSCH。
在本申请实施例中，对PUSCH等上行数据信道的上行传输方式进行了调整，使得终端设备真实发送的上行数据信道的重复次数不少于网络设备指示的上行数据信道的重复次数，有利于提高PUSCH等上行数据信道的传输性能。
在一种可能的设计中，在每个第一时域单元中发送的所述上行数据信道的时域资源未被解调参考信号DM-RS全部占用；或，在每个第一时域单元中发送的所述上行数据信道的上行符号的数量不小于所述网络设备指示的第一数量的一半；或，在每个第一时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量不小于所述网络设备指示的第一数量的一半。
上述设计中，在终端设备在发送上行数据信道时，要求发送的上行数据信道的时域资 源未被解调参考信号DM-RS全部占用的第一时域单元，或发送的上行数据信道的上行符号的数量不小于网络设备指示的第一数量的一半的第一时域单元，或发送的上行数据信道中承载的上行数据所占用的上行符号的数量不小于所述网络设备指示的第一数量的一半的第一时域单元，其数量M不小于网络设备指示的上行数据信道的重复次数，有利于保障通过上行数据信道承载了足够数量的上行数据，从而提高上行数据传输的可靠性。
在一种可能的设计中，所述方法还包括：接收来自所述网络设备的第三指示信息，所述第三指示信息指示冗余版本RV的配置，所述RV的配置包含G个候选RV；在N-Q个第三时域单元向所述网络设备发送所述上行数据信道包括：根据所述RV的配置在所述N-Q个第三时域单元向所述网络设备发送所述上行数据信道。可选的，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i对应的RV，其中，i为0，1，2，3…N-Q-1。
上述设计中，终端设备根据网络设备的RV配置，发送上行数据信道时，有利于网络设备对上行数据信道的解码。
在一种可能的设计中，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中，i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第四时域单元的数量，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。可选的，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
上述设计中，对于发送的上行数据信道中承载的数据量较少的时域单元，如不满足发送的上行数据信道的起始符号位置为网络设备指示的起始符号位置、发送的上行数据信道的长度为网络设备指示的连续符号长度的时域单元，该时域单元后面的时域单元发送的上行数据信道仍使用该时域单元发送上行数据信道所使用的RV或所使用的支持自解码的RV，直至后面的时域单元发送的上行数据信道中可以承载较多的数据量，如直至后面的时域单元满足发送的上行数据信道的起始符号位置为网络设备指示的起始符号位置、发送的上行数据信道的长度为网络设备指示的连续符号长度，继续采用下一RV，有利于提高上行数据信道的传输性能。
在一种可能的设计中，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第五时域单元的数量，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。可选的，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
上述设计中，对于发送的上行数据信道中承载的数据量较少的时域单元，如发送的上行数据信道的上行符号的数量小于网络设备指示的第一数量的一半的时域单元，该时域单 元后面的时域单元发送的上行数据信道仍使用该时域单元发送上行数据信道所使用的RV或所使用的支持自解码的RV，直至后面的时域单元发送的上行数据信道中可以承载较多的数据量，如直至后面的时域单元发送的上行数据信道的上行符号的数量不小于网络设备指示的第一数量的一半，继续采用下一RV，有利于提高上行数据信道的传输性能。
在一种可能的设计中，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第六时域单元的数量，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。可选的，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
上述设计中，对于发送的上行数据信道中承载的数据量较少的时域单元，如发送的上行数据信道中承载的上行数据所占用的上行符号的数量小于网络设备指示的第一数量的一半的时域单元，该时域单元后面的时域单元发送的上行数据信道仍使用该时域单元发送上行数据信道所使用的RV或所使用的支持自解码的RV，直至后面的时域单元发送的上行数据信道中可以承载较多的数据量，如直至后面的时域单元发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量不小于网络设备指示的第一数量的一半，继续采用下一RV，有利于提高上行数据信道的传输性能。
在一种可能的设计中，所述N-Q个第三时域单元中包括不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。
上述设计中，不满足网络设备指示的上行数据信道的起始符号位置和连续符号长度的时域单元也可以发送上行数据信道，有利于提高上行符号资源的利用率。
第二方面，本申请实施例提供一种上行传输装置，该装置具有实现上述第一方面或者第一方面的任一种可能的设计中方法的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元(模块)，比如包括收发单元和处理单元。
在一个可能的设计中，该装置可以是芯片或者集成电路。
在一个可能的设计中，该装置包括处理器和接口电路，所述处理器与所述接口电路耦合，用于实现上述第一方面或者第一方面的任一种可能的设计中所述的方法的功能。可以理解的是，接口电路可以为收发器或输入输出接口。该装置还可以包括存储器，所述存储器存储有可被处理器执行的用于实现上述第一方面或者第一方面的任一种可能的设计中所述的方法的功能的程序。
在一个可能的设计中，该装置可以为终端设备。
第三方面，本申请实施例提供一种计算机可读存储介质，其上存储有计算机程序或指令，当该计算机程序或指令在计算机上运行时，使得所述计算机执行上述第一方面或第一方面的任一种可能的设计中的方法。
第四方面，本申请实施例提供一种计算机程序产品，包括计算机程序或指令，当所述计算机程序或指令在计算机上运行时，可以实现上述第一方面或者第一方面的任一种可能 的设计中所述的方法。
第五方面，本申请实施例还提供芯片系统，所述芯片系统包括：处理器和接口，所述处理器用于从所述接口调用并运行指令，当所述处理器执行所述指令时，可以实现上述第一方面或者第一方面的任一种可能的设计中所述的方法。
上述第二方面至第五方面所能达到的技术效果请参照上述第一方面所能达到的技术效果，这里不再重复赘述。
附图说明
图1为本申请实施例提供的通信系统架构示意图；
图2为本申请实施例提供的PUSCH传输块编码过程示意图；
图3为本申请实施例提供的冗余版本应用示意图；
图4为本申请实施例提供的PUSCH映射图案示意图之一；
图5为本申请实施例提供的PUSCH映射图案示意图之二；
图6为本申请实施例提供的PUSCH映射图案示意图之三；
图7为本申请实施例提供的PUSCH映射图案示意图之四；
图8为本申请实施例提供的PUSCH映射图案示意图之五；
图9为本申请实施例提供的上行传输方法示意图；
图10为本申请实施例提供的PUSCH映射图案示意图之六；
图11为本申请实施例提供的PUSCH映射图案示意图之七；
图12为本申请实施例提供的PUSCH映射图案示意图之八；
图13为本申请实施例提供的PUSCH映射图案示意图之九；
图14为本申请实施例提供的RV应用示意图之一；
图15为本申请实施例提供的RV应用示意图之二；
图16为本申请实施例提供的RV应用示意图之三；
图17为本申请实施例提供的上行传输装置示意图之一；
图18为本申请实施例提供的上行传输装置示意图之二。
具体实施方式
本申请实施例的技术方案可以应用于各种通信系统，例如第五代(5th generation，5G)移动通信系统或新无线(new radio，NR)系统，或者应用于未来的通信系统或其它类似的通信系统，如6G系统等。具体的，本申请实施例所应用的通信系统的结构可以如图1所示，该通信系统中包括网络设备和至少一个终端设备(如图1中所示出的终端设备1和终端设备2)，还可以包括核心网设备。终端设备可以通过无线的方式与网络设备连接，网络设备可以通过无线或有线方式与核心网设备连接。另外，可以理解的是，核心网设备与网络设备可以是独立的不同的物理设备，也可以是将核心网设备的功能与网络设备的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分核心网设备的功能和部分的网络设备的功能。终端设备可以是固定位置的，也可以是可移动的。上述各设备间的无线链路可以通过授权频谱(licensed spectrum)进行通信，也可以通过免授权频谱(unlicensed spectrum)进行通信，还可以同时通过授权频谱和免授权频谱进行通信。设备 间的无线链路可以通过6吉兆赫(gigahertz，GHz)以下的频谱进行通信，也可以通过6GHz以上的频谱进行通信，还可以同时使用6GHz以下的频谱和6GHz以上的频谱进行通信。本申请对无线链路所使用的频谱资源不做限定。
上述通信系统可以适用于下行信号传输(也可称为下行传输)，也可以适用于上行信号传输(也可以称为上行传输)，还可以适用于设备到设备(device to device，D2D)的信号传输(也可以称为侧行传输)。对于下行信号传输，发送设备是网络设备，对应的接收设备是终端设备。对于上行信号传输，发送设备是终端设备，对应的接收设备是网络设备。对于D2D的信号传输，发送设备是终端设备，对应的接收设备也是终端设备。
应理解，图1只是一种通信系统的架构示例，该通信系统中还可以包括其它设备，如还可以包括无线中继设备和无线回传设备，在图1中未画出。本申请实施例对通信系统中包括的网络设备的数量、核心网设备以及终端设备的数量不做限定。
为了便于本领域技术人员理解，下面对本申请实施例中的部分用语进行解释说明。
1)、终端设备，是一种具有无线收发功能的设备，可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。所述终端设备也可以称为终端(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。
2)、网络设备，也称接入网设备或无线接入网设备，是一种为终端设备提供无线通信功能的设备，可用于与终端设备进行通信。无线接入网设备例如包括但不限于：5G中的下一代基站(gnodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心、未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等，本申请对网络设备所采用的具体技术和具体设备形态不做限定。
其中，网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请对网络设备和终端设备的应用场景不做限定。
3)、时隙(slot)，在NR中定义一个时隙由14个正交频分多址(orthogonal frequency-division multiplexing，OFDM)符号构成，为了方便描述，在本申请后续描述中也可将OFDM符号简称为符号，不再另行说明。其中，一个时隙中可以包括下行符号(downlink symbols)、上行符号(uplink symbols)、和灵活符号(flexible symbols)，下行符号不能用于上行传输；上行符号不能用于下行传输；而灵活符号既可用于下行传输也可用于上行传输。NR支持一个时隙用于上行传输，记为上行(uplink，U)slot；支持一个时隙用于下行传输，记为下行(downlink，D)时隙；也支持一个时隙既有上行也有下行的配置，记为特殊(special，S)时隙。如果一个时隙全部为下行符号，则该时隙称为下行时隙，如果一个时隙全部为上行符号，则该时隙称为上行时隙。如果一个时隙包含上行符号、下行符号、灵活符号中的两种及两种以上类型的符号，则该时隙称为特殊时隙。典型的时分复用(time division duplex，TDD)系统时隙配置格式，包括DDDSU、DDDSUDDSUU、DDDDDDDDUU等。即时隙按照DDDSU、DDDSUDDSUU等格式重复。
目前，NR中网络设备支持三种通知终端设备上下行资源的信令方式：
(1)动态信令通知被调度的终端设备：终端设备监听下行控制信令，根据下行控制信令里的调度授权或调度分配来进行上行或下行传输。
(2)半静态无线资源控制(radio resource control，RRC)信令通知：该模式把符号划分为下行符号、上行符号以及灵活符号。对灵活符号，终端设备依然需要监听调度控制信令，根据调度信息进行上行或下行传输。
(3)一组终端设备共享的动态时隙格式指示(slot format indicator，SFI)：SFI可以指示一个或多个时隙中，符号是下行、上行还是灵活符号。但SFI不能改变半静态RRC信令，以及上下行动态信令配置的上下行配置。
其中，时隙格式可以由下表1所示的普通循环前缀的时隙格式(slot formats for normal cyclic prefix)指示。其中表1中左侧是格式(format)索引，右侧是在该索引下，一个时隙中具体的符号分配，其中“D”代表下行符号，“U”代表上行符号，“F”代表灵活符号，symbol number in a slot代表时隙中的符号编号。
Figure PCTCN2021072238-appb-000001
Figure PCTCN2021072238-appb-000002
表1
4)、PUSCH传输，在NR中上行信道包括物理上行控制信道(physical uplink control  channel，PUCCH)、PUSCH以及物理随机接入信道(physical random access channel，PRACH)；上行信号包括探测参考信号(sounding reference signal，SRS)、解调参考信号(demodulation reference signal，DM-RS)、以及相位跟踪参考信号(phase-tracking reference signal，PT-RS)。其中，上行DM-RS伴随PUCCH和PUSCH传输，其时频资源占用了PUCCH或PUSCH的一部分。对于PUSCH，在NR中PUSCH传输分为三种：
(1)基于动态调度的PUSCH传输：每次PUSCH传输，都用物理层指示下行控制信息(downlink control information，DCI)进行调度。在此种传输中，终端设备每接收到网络设备的一次上行调度，就进行一次PUSCH传输。
(2)配置许可(configured grant)Type 1：半静态调度，终端设备接收来自网络设备的高层配置(包含rrc-ConfiguredUplinkGrant的高层参数configuredGrantConfig)，不接收物理层指示DCI，协议中称为“配置的上行链路授权(configured uplink grant)”，其中，rrc-ConfiguredUplinkGrant表示无线资源控制配置的上行链路授权，configuredGrantConfig表示配置授权配置。在此种传输中，网络设备的高层给终端设备配置了一些半持续资源，终端设备如果有上行数据需要发送，就可以利用这些资源发送PUSCH；如果没有上行数据需要发送，则不进行PUSCH发送。
(3)configured grant Type 2：终端设备先接收高层配置(不包含rrc-ConfiguredUplinkGrant的高层参数configuredGrantConfig)，再由物理层指示DCI激活或者去激活，协议中称为“基于L1信令配置的上行链路授权(configured uplink grant based on L1 signalling)”。此种传输中，网络设备的高层给终端设备配置了一些半持续资源，然后由网络设备的物理层信令激活/去激活：激活时终端设备的行为和第二种PUSCH传输类似；没有激活时，这些资源不能使用。
5)、传输块发送过程和冗余版本(redundancy version，RV)。在NR中PUSCH传输块要经过图2所示的编码过程。信息发送端可为传输块(transport block，TB)添加循环冗余校验(cyclic redundancy check，CRC)码，将添加了CRC码的传输块分割为一个或多个码块，再为分割得到的码块添加CRC码。接着对添加了CRC码的码块进行信道编码，在信道编码后，再将得到的码块进行速率匹配，包括重复或者打孔，以匹配空口资源的比特数。之后再进行码块级联，最后可完成发送。
其中，信道编码的母码码率一般为1/3或者1/5。信道编码之后的比特(bit)(如上述信道编码后得到的码块中的bit)会进行速率匹配，也就是进行重复或者打孔，以匹配空口资源的bit数。速率匹配可以使用不同的RV，不同的RV包含的信道编码后的bit可能不同。图3给了一个示例，码率为R＝3/4，母码码率为1/3。记Ncb为信道编码后的bit长度，则对应的信息bit长度为1/3Ncb，对应的空口bit数为4/9Ncb(即为母码码率1/3除以码率R，码率R可以理解为空口比特数/母码比特数)，不同的RV(也即不同的RV版本，如RV0，RV1，RV2，RV3)对应的编码后的bit在图3中以该RV对应的矩形区域示出。
需要注意的是母码编码前的信息bit称为系统bit，在1/3码率的母码编码中，编码后的前1/3bit即系统bit。如果想自解码(自解码是指根据本次RV，不需要联合其他RV，就可能可以译码成功)，则该RV需要包含完整的系统bit，如图3所示RV0包含完整的系统bit，支持自解码。
6)、PUSCH重复传输。NR中PUSCH重复(repetition)类型(type)分为两种：分别是PUSCH重复类型A以及PUSCH重复类型B，前者是标准Rel-15版本中采用的，后 者是标准Rel-16版本中新引入的。终端设备开始传输PUSCH的时隙K s由K 2决定，K 2为时隙偏移，K s可以采用如下公式确定。
Figure PCTCN2021072238-appb-000003
其中，n表示调度的DCI所在的时隙，μ PUSCH表示PUSCH的子载波间隔配置，μ PDCCH表示物理下行控制信道(physical downlink control channel，PDCCH)的子载波间隔配置，
Figure PCTCN2021072238-appb-000004
表示PDCCH载波聚合的时隙偏移，μ offset,PDCCH表示PDCCH的子载波间隔配置偏移，
Figure PCTCN2021072238-appb-000005
表示PUSCH载波聚合的时隙偏移，μ offset,PUSCH表示PUSCH的子载波间隔配置偏移。
PUSCH重复类型A以时隙为单位重复K次，起始符号(S)是相对时隙的开始位置；L是分配给PUSCH的，从S开始的连续符号个数；S与L由开始与长度指示(start and length indicator，SLIV)来决定。在K>1时，在K个连续时隙上应用相同的符号分配。协议中规定有效的S与L组合的设计，使得PUSCH重复类型A不会出现单个重复跨越时隙边界(boundary)。以S＝0，L＝10，K＝4为例，其映射图案如图4所示，可见PUSCH重复类型A，单个重复不会跨过时隙边界。
PUSCH重复类型B以网络设备指示的L为单位重复K次，起始符号(S)是相对时隙的开始位置；L是分配给PUSCH的，从S开始的连续符号个数；S与L分别由资源分配表索引行的起始符号(start symbol)和长度(length)给出。PUSCH重复类型B相比较PUSCH重复类型A更为灵活，可能会出现一个重复(repetition)跨越时隙边界，或一个重复中包含无效符号(invalid symbol(s))的情况，此时，该重复会出现分裂。协议中将分裂前的重复称为名义重复(nominal repetition)，将分裂后的重复称为实际重复(actual repetition)，网络设备指示的重复次数K指的是名义重复的总次数。当S＝11，L＝7，K＝4时，其映射图案如图5所示。由上图可见，4次名义重复，由于时隙边界的存在，分裂成6次实际重复。
当PUSCH重复类型B的重复遇到无效符号，比如下行符号时，名义重复会首先将这些无效符号去掉。如果一个名义重复中的潜在有效符号数大于0，那么该名义重复会包括一个或多个实际重复，每个实际重复利用连续的有效符号传输(除非L＝1，否则单符号的实际重复被忽略)。如图6所示，D代表下行符号、U代表上行符号，F代表灵活符号，S＝0，L＝7，K＝2时，2次名义重复，由于无效符号(图6中无效符号为下行符号)的存在，分裂成3次实际重复，且用于PUSCH传输的有效符号数目也降低。
对于PUSCH的S与L组合，终端设备将以下表2中定义的S和L视为有效分配，参照3GPP协议中表(table)6.1.2.1-1:有效的S和L组合(valid S and L combinations)。
Figure PCTCN2021072238-appb-000006
Figure PCTCN2021072238-appb-000007
表2
7)、PUSCH重复传输时的冗余版本。
NR中PUSCH重复类型A，终端设备会在K个连续时隙中重复TB，这K个连续时隙中的每个时隙都应用相同的符号分配。RV会被应用在传输块的第n个传输时机(transmission occasion)，n＝0，1，…K-1，根据下表3确定，可参照3GPP协议中表6.1.2.1-2用于PUSCH传输的冗余版本(redundancy version for PUSCH transmission)，其中rv id indicated by the DCI scheduling the PUSCH表示调度PUSCH的DCI指示的rv id，rv id to be applied to n th transmission occasion(repetition type A)or n th actual repetition(repetition type B)表示应用于第n个传输时机(重复类型A)或第n个实际重复(重复类型B)的rv id。
Figure PCTCN2021072238-appb-000008
表3
对PUSCH重复类型A，如果时隙中的符号不满足SLIV，或受到取消指示(cancellation indication，CI)的影响，在这个时隙中的PUSCH传输会被省略(omitted)。
对PUSCH重复类型B，单符号的实际重复会被省略(除非L＝1)，受CI影响的实际重复也被省略。PUSCH重复类型B中，RV被应用到第n个实际重复上(包括被省略的实际重复)，根据上表3确定。
另外，在标准Rel-17覆盖增强(coverage enhancement，CE)的讨论中，为了更好地利用上行符号，有公司提出PUSCH重复类型A的增强，包括：增加最大重复次数；基于可用的上行时隙计算重复次数；以及不同时隙的灵活符号资源分配(也就是不同时隙可分配不同数目的上行符号资源)，在RAN1#103-e会议中写入技术报告(technical report，TR)。同样针对PUSCH重复类型A，有公司提出在特殊时隙发送DM-RS，并跨时隙/重复进行信道估计，即DMRS-捆绑(bundling)。在Rel-17覆盖增强(coverage enhancement，CE)的讨论中，为了更好地利用上行符号，也公司提出PUSCH重复类型B的增强，包括：跨 越时隙边界/无效符号的实际PUSCH传输；长度大于14符号的实际重复；以及RV增强，在RAN1#103-e会议中也写入了TR。
8)、取消指示。DCI格式(format)2_4用来通知终端设备取消相应上行传输的物理资源块(physical resource block，PRB)和符号，其传输一个或多个取消指示(cancellation indication，CI)。DCI format 2_4针对服务小区的CI，适用于服务小区中的PUSCH传输或SRS传输，本申请主要关注对于PUSCH传输的影响。
终端设备检测到DCI format 2_4时，如果其指示在相应的PRB与符号(symbol)上，与PUSCH重复传输的时频资源有重叠，那么取消掉一次PUSCH传输，或一次PUSCH传输的一次实际重复。当终端设备检测到DCI format 2_4后，PUSCH在取消指示生效时间(T proc,2)之前出现，则终端设备来不及处理CI，会传输PUSCH。如果基于DCI format 2_4的指示，终端设备取消掉一次PUSCH传输，那么终端设备不期望被第二个DCI format调度，在被取消掉的PUSCH传输的符号上，再传输PUSCH。
对于PUSCH重复类型A，当K 2决定的K s指示到某个时隙，而自该时隙起的K个时隙，其中包括不满足SLIV的时隙、受CI影响取消PUSCH传输的时隙等，则不会在这些时隙上传输PUSCH，PUSCH重复类型A的实际重复传输次数也就小于K，从而造成PUSCH的传输性能下降；此外，RV和时隙上有没有实际重复传输没有关系，可以支持自解码的RV(如RV0)可能会减少发送次数，甚至不发送，降低PUSCH的传输性能。如图7所示，S＝0，L＝10，rv id＝0，传输时机n+2(用于原PUSCH重复n+2的发送)中因包含被CI指示的符号而取消PUSCH的传输，RV0不发送。
对于PUSCH重复类型B，如果K个名义重复中的某一个或多个名义重复没有有效符号，则该名义重复不包含实际重复，实际上行传输的符号数目也就会减小，从而造成PUSCH的性能下降；而L>1时省略的单符号实际重复，以及受CI影响取消的实际重复，也会造成实际上行传输的符号数目减少，降低PUSCH的传输性能。此外，RV和实际重复上有没有实际重复传输没有关系，可以支持自解码的RV(如RV0)可能会减少发送次数，甚至不发送，降低PUSCH的传输性能。如图8所示，当S＝0，L＝7，rv id＝0时，实际重复1因仅包括一个上行符号被忽略，RV0不发送，实际重复2中因包含被CI指示的符号而取消，RV2不发送，影响PUSCH的传输性能。
此外，虽然有公司指出对于PUSCH重复类型A，可以直接对上行符号计数，直到利用了K*L个符号上行传输，才停止重复发送，同时RV按照实际发送的传输时机来使用；对于PUSCH重复类型B，直接对上行符号计数，直到利用了K*L个符号上行传输，才停止重复发送，同时RV按照实际发送的实际重复来使用，但是PUSCH重复传输受时隙结构、CI等影响，直接对上行符号计数实现复杂度很高，难以实现。
本申请旨在提供一种上行传输方案，通过调整PUSCH等上行数据信道重复传输时重复次数以及RV的计算方式，解决PUSCH等上行数据信道重复传输受时隙结构、CI等影响，会取消、忽略掉一些重复，影响PUSCH等上行数据信道的传输性能的问题。
需要理解的是，本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。另外，除非有 相反的说明，本申请实施例提及“第一”、“第二”等序数词用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度，并且“第一”、“第二”的描述也并不限定对象一定不同。在本申请中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。在本申请中，“示例性的”或者“例如”等词用于表示例子、例证或说明，被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
下面将结合附图，对本申请实施例进行详细描述。在本申请各实施例中，上行数据信道例如为物理层的上行数据信道，例如PUSCH，或者也可以是其他层的上行数据信道，例如MAC层的上行数据信道等，在后文各个实施例的介绍中，均以上行数据信道是PUSCH为例，那么上行数据信道的资源也就以PUSCH的资源为例。即，后文所述的PUSCH均能替换为上行数据信道。
图9为本申请实施例提供的一种上行传输方法示意图，该方法包括：
S901：终端设备接收来自网络设备的第一指示信息和第二指示信息，所述第一指示信息指示PUSCH的重复类型和重复次数，所述第二指示信息指示时隙偏移。
网络设备可以通过RRC信令、DCI等为终端设备配置PUSCH的传输参数。例如：网络设备可以通过RRC信令或DCI等向终端设备发送第一指示信息指示PUSCH的重复类型和重复次数(K)，向终端设备发送第二指示信息指示时隙偏移(K 2)，如PUSCH的时隙偏移。另外，网络设备还可以通过RRC信令或DCI向终端设备发送用于指示PUSCH的起始符号位置(S)与连续符号长度(L)的指示信息，如对于PUSCH重复类型A，网络设备可以通过RRC信令或DCI向终端设备发送SLIV指示终端设备PUSCH的起始符号位置(S)与连续符号长度(L)。
S902：所述终端设备根据所述时隙偏移确定能够发送所述PUSCH的起始时域单元。
在本申请实施例中，在PUSCH重复类型为重复类型A的情况下，时域单元为时隙；在PUSCH重复类型为重复类型B的情况下，时域单元为小于一个时隙的至少一个符号。无论是PUSCH重复类型A，还是PUSCH重复类型B，终端设备开始传输PUSCH的时隙(K s)均由时隙偏移(K 2)决定，具体终端设备根据时隙偏移(K 2)确定开始传输PUSCH的时隙(K s)的方式，可以参照上述PUSCH重复传输部分的介绍，不再赘述。
终端设备确定开始传输PUSCH的时隙后，在PUSCH重复类型A的情况，终端设备可以将开始传输PUSCH的时隙作为能够发送PUSCH的起始时域单元，并可以根据终端设备PUSCH起始符号位置，进一步确定起始时域单元中能够发送PUSCH的起始符号。在PUSCH重复类型B的情况下，终端设备可以根据开始传输PUSCH的时隙以及终端设备PUSCH起始符号位置，将开始传输PUSCH的时隙中能够发送PUSCH的起始符号开始的第一个实际重复作为起始时域单元，在实际重复中包括小于或等于一个时隙的至少一个符号。
S903：所述终端设备以所述起始时域单元开始，确定出M个第一时域单元向所述网络设备发送所述PUSCH。
其中，从所述起始时域单元开始到第M个第一时域单元为止为连续的N个时域单元，所述N个时域单元中包括Q个未发送PUSCH的第二时域单元，所述M大于或等于所述 网络设备指示的所述重复次数，所述Q小于或等于N-M，M、N、Q为整数。
在一种可能的实施中，终端设备除了在M个第一时域单元向网络设备发送PUSCH之外，对于N个时域单元中除所述M个第一时域单元之外的N-M个时域单元，终端设备可以均不发送PUSCH，也可以在N-M个时域单元中的部分或全部时域单元向网络设备发送PUSCH。例如：PUSCH重复传输的增强的场景下，终端设备也可以利用N-M个时域单元中包含上行符号的部分或全部时域单元发送PUSCH。
在PUSCH重复类型A的情况下，时域单元为时隙，为了提高PUSCH的传输性能，终端设备可以仅对发送了PUSCH、且满足一定PUSCH发送条件的第一时隙进行计数，直至第一时隙的数量M大于或等于网络设备指示的PUSCH的重复次数。其中，终端设备可以根据网络设备指示的重复次数(K)确定M，如确定M等于K，具体的根据网络设备指示的重复次数(K)确定M的方式可以由协议定义，也可以由网络设备指示，本申请实施例不作限定。下面结合具体示例进行说明：
方式一：第一时隙为终端设备向网络设备发送了PUSCH的时隙。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始时隙开始的每个时隙，如果该时隙终端设备向网络设备发送了PUSCH，则m的值+1；如果该时隙终端设备未向网络设备发送PUSCH，则m的值+0，直至m等于M，M大于或等于网络设备指示的重复次数。那么对于方式一，从起始时隙到第M个第一时隙为止连续的N个时隙中终端设备向网络设备发送的PUSCH的重复次数为M次，不小于网络设备指示的重复次数(K)。
作为一种示例，假设对于不满足PUSCH的SLIV的时隙(即时隙中的符号不满足SLIV)，终端设备不发送PUSCH，终端设备初始化m＝0，从起始时隙开始的每个时隙，如果该时隙满足PUSCH的SLIV且未被CI指示包含不能进行上行传输的符号，则终端设备在该时隙上根据PUSCH的SLIV向网络设备发送PUSCH，并将m的值+1；如果该时隙不满足PUSCH的SLIV或被CI指示包含不能进行上行传输的符号，则终端设备在该时隙上不发送PUSCH，m的值+0，直至m的值等于M。
需要理解的是，对于满足PUSCH的SLIV的时隙，虽然网络设备向终端设备发送了CI指示该时隙包含不能进行上行传输的符号，但是在CI的生效时间之前，终端设备已经开始发送PUSCH，则终端设备正常在该时隙发送PUSCH，m的值+1，也即对于某一时隙如果网络设备向终端设备发送了CI的生效时间在终端设备开始发送PUSCH之后，终端设备可以认为该时隙未被CI指示包含不能进行上行传输的符号。
另外，为了充分利用上行资源，如果对于不满足PUSCH的SLIV的时隙，终端设备也可以利用该时隙中包含的上行符号发送PUSCH，也即对于从起始时隙开始的每个时隙，如果该时隙不满足PUSCH的SLIV，但是包含上行符号且该时隙未被CI指示包含不能进行上行传输的符号，则终端设备也可以在该时隙(包含的上行符号)向网络设备发送PUSCH，并将m+1。
方式二：第一时隙为终端设备向网络设备发送的PUSCH的未被DM-RS全部占用的时隙。其中，终端设备向网络设备发送PUSCH的时隙可以满足PUSCH的SLIV，也可以不满足PUSCH的SLIV。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始时隙开始的每个时隙，如果该时隙终端设备向网络设备发送的PUSCH的时域资源未被DM-RS全部占用，则m的值+1；如果该时隙终端设备未向网络设备发送PUSCH，或向网络设备发送的PUSCH的 时域资源被DM-RS全部占用，则m的值+0，直至m等于M。
以终端设备向网络设备发送PUSCH的时隙可以不满足SLIV为例，如图10所示，S＝0，L＝10，只有一组单符号DM-RS，位置在符号2(pos2)。终端设备可以初始化m＝0，从起始时隙(图10中第一个时隙)开始，终端设备向网络设备发送的PUSCH的时域资源未被DM-RS全部占用，m的值+1；图10中第二个时隙，终端设备向网络设备发送的PUSCH的时域资源被DM-RS全部占用，m的值+0；图10中第三个时隙，终端设备向网络设备发送的PUSCH的时域资源未被DM-RS全部占用，m的值+1；图10中第四个时隙，终端设备向网络设备发送的PUSCH的时域资源未被DM-RS全部占用，m的值+1；直至m等于M。
方式三：第一时隙为终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半的时隙。其中，终端设备向网络设备发送PUSCH的时隙可以满足PUSCH的SLIV，也可以不满足PUSCH的SLIV。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始时隙开始的每个时隙，如果该时隙终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，则m的值+1；如果该时隙终端设备向网络设备发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半(包括未向网络设备发送PUSCH)，则m的值+0，直至m等于M，其中第一数量可以为网络设备指示的PUSCH的连续符号长度，也可以由网络设备通过RRC信令、DCI等指示。
以终端设备向网络设备发送PUSCH的时隙可以不满足SLIV、第一数量为网络设备指示的PUSCH的连续符号长度(L)为例，如图11所示，S＝0，L＝12。终端设备可以初始化m＝0，从起始时隙(图11中第一个时隙)开始，终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，m的值+1；图11中第二个时隙，终端设备向网络设备发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半，m的值+0；图11中第三个时隙，终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，m的值+1；图11中第四个时隙，终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，m的值+1；直至m等于M。
方式四：第一时隙为终端设备向网络设备发送的PUSCH中承载的上行数据所占用的上行符号的数量不小于网络设备指示的第一数量的一半的时隙。其中，终端设备向网络设备发送PUSCH的时隙可以满足PUSCH的SLIV，也可以不满足PUSCH的SLIV。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始时隙开始的每个时隙，如果该时隙终端设备向网络设备发送的PUSCH中承载的上行数据所占用的上行符号(未被DM-RS占用的上行符号)的数量不小于网络设备指示的第一数量的一半，则m的值+1；如果该时隙终端设备向网络设备发送的PUSCH中承载的上行数据所占用的上行符号的数量小于网络设备指示的第一数量的一半(包括未向网络设备发送PUSCH)，则m的值+0，直至m等于M，其中第一数量可以为网络设备指示的PUSCH的连续符号长度(L)，也可以由网络设备通过RRC信令、DCI等指示。
在PUSCH重复类型B的情况下，时域单元为实际重复，为了提高PUSCH的传输性能，终端设备可以仅对发送了PUSCH、且满足一定PUSCH发送条件的第一实际重复进行计数，直至第一实际重复的数量M大于或等于网络设备指示的PUSCH的重复次数。其中， 终端设备可以根据网络设备指示的PUSCH的重复次数(K)，确定第一实际重复的数量M，如M可以等于K，也可以是M个第一实际重复对应的名义重复的数量等于K，具体的，根据网络设备指示的重复次数(K)确定M的方式可以由协议定义，也可以由网络设备指示，本申请实施例不作限定。下面结合具体示例进行说明：
方式一：第一实际重复为终端设备向网络设备发送了PUSCH的实际重复。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始实际重复开始的每个实际重复，如果该实际重复终端设备向网络设备发送了PUSCH，则m的值+1；如果该实际重复终端设备未向网络设备发送PUSCH，则m的值+0，直至m等于M，M大于或等于网络设备指示的重复次数(K)。那么对于方式一从起始实际重复到第M个第一实际重复为止连续的N个实际重复中终端设备向网络设备发送的PUSCH的重复次数为M次，不小于网络设备指示的重复次数(K)。
以M个第一实际重复对应的名义重复的数量等于网络设备指示的PUSCH的重复次数(K)为例，如图12所示，S＝7，L＝7，对于本申请的上行传输方式一，相对于现有上行传输方案，对于现有上行传输方案中未发送PUSCH的实际重复1和实际重复2(名义重复1和名义重复2)不计算重复次数，有利于保障通过PUSCH承载足够数量的上行数据，从而提高传输性能。
方式二：第一实际重复为终端设备向网络设备发送的PUSCH的未被DM-RS全部占用的实际重复。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始实际重复开始的每个实际重复，如果该实际重复终端设备向网络设备发送的PUSCH的时域资源未被DM-RS全部占用，则m的值+1；如果该实际重复终端设备未向网络设备发送PUSCH，或向网络设备发送的PUSCH的时域资源被DM-RS全部占用，则m的值+0，直至m等于M。
方式三：第一实际重复为终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半的实际重复。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始实际重复开始的每个实际重复，如果该实际重复终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，则m的值+1；如果该实际重复终端设备向网络设备发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半(包括未向网络设备发送PUSCH)，则m的值+0，直至m等于M，其中第一数量可以为网络设备指示的PUSCH的连续符号长度(L)，也可以由网络设备通过RRC信令、DCI等指示。
如图13所示，S＝6，L＝8，第一数量等于L为例。终端设备可以初始化m＝0，从起始实际重复(图13中第一个实际重复)开始，终端设备向网络设备发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半，m的值+0；图13中第二个实际重复，终端设备向网络设备发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半，m的值+0；图13中第三个实际重复，终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，m的值+1；图13中第四个实际重复，终端设备向网络设备发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半，m的值+0；图13中第五个实际重复，终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，m的值+1；图13中第六个实际重复，终端设备向网络设备发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半，m 的值+1；直至m等于M。
方式四：第一实际重复为终端设备向网络设备发送的PUSCH中承载的上行数据所占用的上行符号的数量不小于网络设备指示的第一数量的一半的实际重复。
在一种可能的实施中，终端设备可以初始化m＝0，对于从起始实际重复开始的每个实际重复，如果该实际重复终端设备向网络设备发送的PUSCH中承载的上行数据所占用的上行符号的数量不小于网络设备指示的第一数量的一半，则m的值+1；如果该实际重复终端设备向网络设备发送的PUSCH中承载的上行数据所占用的上行符号的数量小于网络设备指示的第一数量的一半(包括未向网络设备发送PUSCH)，则m的值+0，直至m等于M，其中第一数量可以为网络设备指示的PUSCH的连续符号长度(L)，也可以由网络设备通过RRC信令、DCI等指示。
在N个时域单元中除Q个未发送PUSCH的第二时域单元之外，终端设备在N-Q个第三时域单元向网络设备发送PUSCH使用的RV，可以根据来自网络设备通过第三指示信息指示的RV的配置来确定，其中RV的配置包含G个候选RV，G可以为4、6等值。作为一种示例：第三指示信息网络设备可以通过RRC信令、DCI等发送给终端设备。作为一种示例，网络设备可以采用上述表3所示的RV配置方式向终端设备指示RV的配置。
在一种可能的实施中，对于N-Q个第三时域单元中的时域单元i，时域单元i上发送的PUSCH使用G个候选RV中i对应的RV，其中，i为0，1，2，3…N-Q-1。
作为一种示例，参照表3以第三指示信息采用rv id，指示4个候选RV为例，对于PUSCH重复类型A，N-Q个第三时域单元中每个时域单元可以作为一个传输时机，用于RV的确定。N-Q个第三时域单元中的时域单元0为传输时机0、时域单元1为传输时机1、时域单元2为传输时机2，…时域单元N-Q-1为传输时机N-Q-1；对于PUSCH重复类型B，N-Q个第三时域单元中每个时域单元可以作为一个实际重复，用于RV的确定。N-Q个第三时域单元中的时域单元0为实际重复0、时域单元1为实际重复1、时域单元2为实际重复2，…时域单元N-Q-1为实际重复N-Q-1。参照表3所示，假设rv id为0，则指示的4个候选RV为RV0，RV2，RV3，RV1，对于M个第一时域单元中的时域单元i，时域单元i上发送的PUSCH使用所述4个候选RV中i对应的RV，具体可以根据i mod 4的值确定，例如在N-Q个第三时域单元中的时域单元0上发送的PUSCH使用RV0、时域单元1上发送的PUSCH使用RV2。
另外，考虑到部分时域单元发送的PUSCH中承载的数据量较少，为了避免承载的数据量较少的PUSCH使用支持自解码的RV影响PUSCH的传输性能，在本申请实施例中，对于承载的数据量较少的PUSCH使用的RV，可以在下一时域单元发送PUSCH时重复使用，下面结合具体实现方式进行说明。另外，需要理解的是，对于PUSCH重复类型A，N-Q个第三时域单元中每个时域单元可以作为一个传输时机，用于RV的确定；对于PUSCH重复类型B，N-Q个第三时域单元中每个时域单元可以作为一个实际重复，用于RV的确定。
方式一：对于N-Q个第三时域单元中的时域单元i，时域单元i上发送的PUSCH使用G个候选RV中i-z对应的RV，其中，i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为N-Q个第三时域单元中前i个时域单元中包括的第四时域单元的数量，所述第四时域单元为所述前i个时域单元中不满足发送的PUSCH的起始符号位置为网络设 备指示的起始符号位置、发送的PUSCH的长度为网络设备指示的连续符号长度的时域单元。(适用于PUSCH传输类型A)。
作为一种示例：仍参照表3所示，假设i为2，rv id为0，则指示的4个候选RV为RV0，RV2，RV3，RV1，N-Q个第三时域单元中前2个时域单元中包括的第四时域单元的数量为1，则N-Q个第三时域单元中时域单元2发送PUSCH使用的RV的值为2-1对应的RV，即RV2。
在一种可能的实施中，第四时域单元还可以仅为前i个时域单元中不满足发送的PUSCH的起始符号位置为网络设备指示的起始符号位置、发送的PUSCH的长度为网络设备指示的连续符号长度，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV，如图3中包含完整系统bit的RV0。
作为一种示例，以终端设备按照图10所示进行PUSCH的发送为例，第三指示信息采用表3中的rv id，rv id为0为例，其中RV0和RV3为支持自解码的RV。如图14所示，时域单元0上发送的PUSCH使用0对应的RV，即RV0。时域单元0为不满足发送的PUSCH的起始符号位置为网络设备指示的起始符号位置、发送的PUSCH的长度为网络设备指示的连续符号长度，且使用第一类RV的时域单元，时域单元1上发送的PUSCH仍使用0对应的RV，即RV0。时域单元2为满足发送的PUSCH的起始符号位置为网络设备指示的起始符号位置、发送的PUSCH的长度为网络设备指示的连续符号长度的时域单元，时域单元2上发送的PUSCH使用1对应的RV，即RV2。
方式二：对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的PUSCH使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第五时域单元的数量，所述第五时域单元为所述前i个时域单元中发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半的时域单元。(适用于PUSCH传输类型A和PUSCH传输类型B)。
在一种可能的实施中，所述第五时域单元还可以仅为所述前i个时域单元中发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
作为一种示例，以终端设备按照图11所示进行PUSCH的发送为例，S＝0，L＝12，第三指示信息采用表3中的rv id，rv id为0为例，其中RV0和RV3为支持自解码的RV。如图15所示，时域单元0上发送的PUSCH使用0对应的RV，即RV0。时域单元0为发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半的时域单元，时域单元1上发送的PUSCH使用1对应的RV，即RV2。时域单元1为发送的PUSCH的上行符号的数量小于网络设备指示的第一数量的一半，但未使用第一类RV的时域单元，时域单元2上发送的PUSCH使用2对应的RV，即RV3。时域单元2为发送的PUSCH的上行符号的数量不小于网络设备指示的第一数量的一半的时域单元，时域单元3上发送的PUSCH使用3对应的RV，即RV1。
方式三：对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的PUSCH使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第六时域单元的数量，所述第六时域单元为所述前i个时域单元中发送的PUSCH中承载的上 行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。
在一种可能的实施中，所述第六时域单元为所述前i个时域单元中发送的PUSCH中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
作为一种示例，以终端设备按照图13所示进行PUSCH的发送为例，S＝0，L＝12，第三指示信息采用表3中的rv id，rv id为0为例，其中RV0和RV3为支持自解码的RV。如图16所示，时域单元0上发送的PUSCH使用0对应的RV，即RV0。时域单元0发送的PUSCH中承载的上行数据所占用的上行符号的数量小于网络设备指示的第一数量的一半，且使用第一类RV，时域单元1上发送的PUSCH仍使用0对应的RV，即RV0。时域单元1发送的PUSCH中承载的上行数据所占用的上行符号的数量不小于网络设备指示的第一数量的一半，时域单元2上发送的PUSCH使用1对应的RV，即RV2。时域单元2发送的PUSCH中承载的上行数据所占用的上行符号的数量小于网络设备指示的第一数量的一半，但未使用第一类RV，时域单元3上发送的PUSCH使用2对应的RV，即RV3。时域单元3发送的PUSCH中承载的上行数据所占用的上行符号的数量不小于所述网络设备指示的第一数量的一半，时域单元4上发送的PUSCH使用3对应的RV，即RV1。
网络设备接收来自终端设备的PUSCH后，即可从PUSCH中获取PUSCH中承载的上行数据。
上述主要从网络设备和终端设备之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，为了实现上述功能，各网元包括了执行各个功能相应的硬件结构和/或软件模块(或单元)。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图17和图18为本申请的实施例提供的可能的上行传输装置的结构示意图。这些上行传输装置可以用于实现上述方法实施例中终端设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该上行传输装置可以是图9中的终端设备，还可以是应用于终端设备的模块(如芯片)。
如图17所示。上行传输装置1700可以包括：处理单元1702和收发单元1703，还可以包括存储单元1701。上行传输装置1700用于实现上述图9中所示的方法实施例中终端设备的功能。
一种可能的设计中，处理单元1702用于实现相应的处理功能。收发单元1703用于支持上行传输装置1700与其他网络实体的通信。存储单元1701，用于存储上行传输装置1700的程序代码和/或数据。可选地，收发单元1703可以包括接收单元和/或发送单元，分别用于执行接收和发送操作。
当上行传输装置1700用于实现图9所示的方法实施例中终端设备的功能时：收发单元1703，用于接收来自网络设备的第一指示信息和第二指示信息，所述第一指示信息指示上行数据信道的重复类型和重复次数，所述第二指示信息指示时隙偏移；处理单元1702，用于根据所述时隙偏移确定能够发送所述上行数据信道的起始时域单元；所述处理单元1702，还用于以所述起始时域单元开始，确定出M个第一时域单元通过所述收发单元1703 向所述网络设备发送所述上行数据信道，其中，从所述起始时域单元开始到第M个第一时域单元为止为连续的N个时域单元，所述N个时域单元中包括Q个未发送所述上行数据信道的第二时域单元，所述M大于或等于所述网络设备指示的所述重复次数，所述Q小于或等于N-M，在所述重复类型为重复类型A的情况下，所述N个时域单元中每个时域单元为时隙，在所述重复类型为重复类型B的情况下，所述N个时域单元中每个时域单元为小于或等于一个时隙的至少一个符号。
在一种可能的设计中，在每个第一时域单元中发送的所述上行数据信道的时域资源未被解调参考信号DM-RS全部占用；或，在每个第一时域单元中发送的所述上行数据信道的上行符号的数量不小于所述网络设备指示的第一数量的一半；或，在每个第一时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量不小于所述网络设备指示的第一数量的一半。
在一种可能的设计中，所述收发单元1703，还用于接收来自所述网络设备的第三指示信息，所述第三指示信息指示冗余版本RV的配置，所述RV的配置包含G个候选RV；
所述收发单元1703在N-Q个第三时域单元向所述网络设备发送所述上行数据信道时：具体用于根据所述RV的配置在所述N-Q个第三时域单元向所述网络设备发送所述上行数据信道。
在一种可能的设计中，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i对应的RV，其中，i为0，1，2，3…N-Q-1。
在一种可能的设计中，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中，i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第四时域单元的数量，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。
在一种可能的设计中，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
在一种可能的设计中，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第五时域单元的数量，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。
在一种可能的设计中，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
在一种可能的设计中，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2， 3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第六时域单元的数量，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。
在一种可能的设计中，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
在一种可能的设计中，所述N-Q个第三时域单元中包括不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。
在一种可能的设计中，所述上行数据信道为物理上行共享信道PUSCH。
有关上述处理单元1702和收发单元1703更详细的描述可以直接参考图9所示的方法实施例中相关描述直接得到，这里不加赘述。
如图18所示，通信装置1800包括处理器1810和接口电路1820。处理器1810和接口电路1820之间相互耦合。可以理解的是，接口电路1820可以为收发器或输入输出接口。可选的，通信装置1800还可以包括存储器1830，用于存储处理器1810执行的指令或存储处理器1810运行指令所需要的输入数据或存储处理器1810运行指令后产生的数据。
当通信装置1800用于实现图9所示的方法时，处理器1810用于实现上述处理单元1702的功能，接口电路1820用于实现上述收发单元1703的功能。
当上述上行传输装置为应用于终端设备的芯片时，该终端设备芯片实现上述方法实施例中终端设备的功能。该终端设备芯片从终端设备中的其它模块(如射频模块或天线)接收信息，该信息是网络设备发送给终端设备的；或者，该终端设备芯片向终端设备中的其它模块(如射频模块或天线)发送信息，该信息是终端设备发送给网络设备的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable aate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于网络设备或终端设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产 品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘(digital video disc，DVD)；还可以是半导体介质，例如，固态硬盘(solid state drive，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。

Claims (27)

  1. 一种上行传输方法，其特征在于，包括：
    接收来自网络设备的第一指示信息和第二指示信息，所述第一指示信息指示上行数据信道的重复类型和重复次数，所述第二指示信息指示时隙偏移；
    根据所述时隙偏移确定能够发送所述上行数据信道的起始时域单元；
    以所述起始时域单元开始，确定出M个第一时域单元向所述网络设备发送所述上行数据信道，其中，从所述起始时域单元开始到第M个第一时域单元为止为连续的N个时域单元，所述N个时域单元中包括Q个未发送所述上行数据信道的第二时域单元，所述M大于或等于所述网络设备指示的所述重复次数，所述Q小于或等于N-M，在所述重复类型为重复类型A的情况下，所述N个时域单元中每个时域单元为时隙，在所述重复类型为重复类型B的情况下，所述N个时域单元中每个时域单元为小于或等于一个时隙的至少一个符号。
  2. 如权利要求1所述的方法，其特征在于，在每个第一时域单元中发送的所述上行数据信道的时域资源未被解调参考信号DM-RS全部占用；或，
    在每个第一时域单元中发送的所述上行数据信道的上行符号的数量不小于所述网络设备指示的第一数量的一半；或，
    在每个第一时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量不小于所述网络设备指示的第一数量的一半。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    接收来自所述网络设备的第三指示信息，所述第三指示信息指示冗余版本RV的配置，所述RV的配置包含G个候选RV；
    在N-Q个第三时域单元向所述网络设备发送所述上行数据信道包括：
    根据所述RV的配置在所述N-Q个第三时域单元向所述网络设备发送所述上行数据信道。
  4. 如权利要求3所述的方法，其特征在于，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i对应的RV，其中，i为0，1，2，3…N-Q-1。
  5. 如权利要求3所述的方法，其特征在于，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中，i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第四时域单元的数量，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。
  6. 如权利要求5所述的方法，其特征在于，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
  7. 如权利要求3所述的方法，其特征在于，对于所述N-Q个第三时域单元中的时域 单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第五时域单元的数量，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。
  8. 如权利要求7所述的方法，其特征在于，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
  9. 如权利要求3所述的方法，其特征在于，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第六时域单元的数量，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。
  10. 如权利要求9所述的方法，其特征在于，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
  11. 如权利要求3-10中任一项所述的方法，其特征在于，所述N-Q个第三时域单元中包括不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。
  12. 如权利要求1-11中任一项所述的方法，其特征在于，所述上行数据信道为物理上行共享信道PUSCH。
  13. 一种上行传输装置，其特征在于，包括：处理单元和收发单元；
    所述收发单元，用于接收来自网络设备的第一指示信息和第二指示信息，所述第一指示信息指示上行数据信道的重复类型和重复次数，所述第二指示信息指示时隙偏移；
    所述处理单元，用于根据所述时隙偏移确定能够发送所述上行数据信道的起始时域单元；
    所述处理单元，还用于以所述起始时域单元开始，确定出M个第一时域单元通过所述收发单元向所述网络设备发送所述上行数据信道，其中，从所述起始时域单元开始到第M个第一时域单元为止为连续的N个时域单元，所述N个时域单元中包括Q个未发送所述上行数据信道的第二时域单元，所述M大于或等于所述网络设备指示的所述重复次数，所述Q小于或等于N-M，在所述重复类型为重复类型A的情况下，所述N个时域单元中每个时域单元为时隙，在所述重复类型为重复类型B的情况下，所述N个时域单元中每个时域单元为小于或等于一个时隙的至少一个符号。
  14. 如权利要求13所述的装置，其特征在于，在每个第一时域单元中发送的所述上行数据信道的时域资源未被解调参考信号DM-RS全部占用；或，
    在每个第一时域单元中发送的所述上行数据信道的上行符号的数量不小于所述网络设备指示的第一数量的一半；或，
    在每个第一时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符 号的数量不小于所述网络设备指示的第一数量的一半。
  15. 如权利要求13或14所述的装置，其特征在于，所述收发单元，还用于接收来自所述网络设备的第三指示信息，所述第三指示信息指示冗余版本RV的配置，所述RV的配置包含G个候选RV；
    所述收发单元在N-Q个第三时域单元向所述网络设备发送所述上行数据信道时：具体用于根据所述RV的配置在所述N-Q个第三时域单元向所述网络设备发送所述上行数据信道。
  16. 如权利要求15所述的装置，其特征在于，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i对应的RV，其中，i为0，1，2，3…N-Q-1。
  17. 如权利要求15所述的装置，其特征在于，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中，i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第四时域单元的数量，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。
  18. 如权利要求17所述的装置，其特征在于，所述第四时域单元为所述前i个时域单元中不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
  19. 如权利要求15所述的装置，其特征在于，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第五时域单元的数量，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。
  20. 如权利要求19所述的装置，其特征在于，所述第五时域单元为所述前i个时域单元中发送的所述上行数据信道的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
  21. 如权利要求15所述的装置，其特征在于，对于所述N-Q个第三时域单元中的时域单元i，所述时域单元i上发送的所述上行数据信道使用所述G个候选RV中i-z对应的RV，其中i为0，1，2，3…N-Q-1，当i为0时，z为0；当i不为0时，z为所述N-Q个第三时域单元中前i个时域单元中包括的第六时域单元的数量，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半的时域单元。
  22. 如权利要求21所述的装置，其特征在于，所述第六时域单元为所述前i个时域单元中发送的所述上行数据信道中承载的上行数据所占用的上行符号的数量小于所述网络设备指示的第一数量的一半，且使用第一类RV的时域单元，所述第一类RV为支持自解码的RV。
  23. 如权利要求15-22中任一项所述的装置，其特征在于，所述N-Q个第三时域单元中包括不满足发送的所述上行数据信道的起始符号位置为所述网络设备指示的起始符号位置、发送的所述上行数据信道的长度为所述网络设备指示的连续符号长度的时域单元。
  24. 如权利要求13-23中任一项所述的装置，其特征在于，所述上行数据信道为物理上行共享信道PUSCH。
  25. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1-12中任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1-12中任一项所述的方法。
  27. 一种芯片系统，其特征在于，所述芯片系统包括：
    处理器和接口，所述处理器用于从所述接口调用并运行指令，当所述处理器执行所述指令时，实现如权利要求1-12中任一项所述的方法。
PCT/CN2021/072238 2021-01-15 2021-01-15 一种上行传输方法及装置 WO2022151383A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/072238 WO2022151383A1 (zh) 2021-01-15 2021-01-15 一种上行传输方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/072238 WO2022151383A1 (zh) 2021-01-15 2021-01-15 一种上行传输方法及装置

Publications (1)

Publication Number Publication Date
WO2022151383A1 true WO2022151383A1 (zh) 2022-07-21

Family

ID=82447735

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/072238 WO2022151383A1 (zh) 2021-01-15 2021-01-15 一种上行传输方法及装置

Country Status (1)

Country Link
WO (1) WO2022151383A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110611958A (zh) * 2019-08-16 2019-12-24 中兴通讯股份有限公司 传输资源配置方法、装置和计算机存储介质
WO2020167650A1 (en) * 2019-02-13 2020-08-20 Idac Holdings, Inc. Physical uplink shared channel transmissions
CN111866920A (zh) * 2019-04-30 2020-10-30 中国信息通信研究院 一种物理上行共享信道发送方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020167650A1 (en) * 2019-02-13 2020-08-20 Idac Holdings, Inc. Physical uplink shared channel transmissions
CN111866920A (zh) * 2019-04-30 2020-10-30 中国信息通信研究院 一种物理上行共享信道发送方法和设备
CN110611958A (zh) * 2019-08-16 2019-12-24 中兴通讯股份有限公司 传输资源配置方法、装置和计算机存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "PUSCH enhancements for URLLC", 3GPP DRAFT; R1-1906329, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, 4 May 2019 (2019-05-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 9, XP051708364 *
VIVO: "Discussion on solutions for PUSCH coverage enhancement", 3GPP DRAFT; R1-2007680, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 17 October 2020 (2020-10-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051939837 *

Similar Documents

Publication Publication Date Title
KR102341820B1 (ko) 무선 통신 시스템에서 채널 액세스를 위한 장치 및 방법
US20210274494A1 (en) Uplink control information transmission method and apparatus
CN110999365B (zh) 传输数据的方法和终端设备
EP3787216A1 (en) Configuration of downlink transmissions
KR20190112806A (ko) Dmrs 송신 방법 및 통신 기기
KR102158655B1 (ko) 무선 통신 방법, 네트워크 기기, 사용자 장비 및 시스템
CN111436128A (zh) 传输上行信息的方法和通信装置
KR102543108B1 (ko) 서비스를 전송하기 위한 방법, 이동국 및 네트워크 기기
CN106550445B (zh) 无线通信中的一种低延迟的方法和装置
US11540254B2 (en) Apparatus and method for allocating resources in wireless communication system
KR20210126607A (ko) 전송 및 수신 동작을 수행하는 사용자 장비 및 시스템
CN113039858A (zh) 无线通信系统中用于基于子带的信道接入的方法和装置
CN111756506A (zh) 传输上行信息的方法和通信装置
US20200351056A1 (en) Method and apparatus for determining channel access procedure in wireless communication system
KR20200080864A (ko) 무선 통신 시스템에서 채널 접속을 위한 장치 및 방법
CN112956267B (zh) 用于无线通信系统中的无线电资源分配的方法和装置
KR20210066663A (ko) 무선 통신 시스템에서 슬롯 구조 지시 방법 및 장치
EP2870811B1 (en) Method and network node for allocating resources of an uplink subframe
US11924854B2 (en) Method and apparatus for uplink data information transmission in wireless communication system
WO2020220253A1 (zh) 一种信息传输方法和通信设备
WO2022041419A1 (zh) 一种通信方法与装置
CN115039359A (zh) 用于资源分配的系统和方法
KR20220100961A (ko) 취소를 표시하는 정보를 결정하기 위한 시스템들 및 방법들
JP2021532652A (ja) 基地局、ユーザ機器、回線、移動通信システム及び方法
WO2018201919A1 (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: 21918587

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

Country of ref document: EP

Kind code of ref document: A1