WO2024032077A1 - 上行传输方法和通信装置 - Google Patents

上行传输方法和通信装置 Download PDF

Info

Publication number
WO2024032077A1
WO2024032077A1 PCT/CN2023/095210 CN2023095210W WO2024032077A1 WO 2024032077 A1 WO2024032077 A1 WO 2024032077A1 CN 2023095210 W CN2023095210 W CN 2023095210W WO 2024032077 A1 WO2024032077 A1 WO 2024032077A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink data
time
uplink
timer
terminal
Prior art date
Application number
PCT/CN2023/095210
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 华为技术有限公司
Publication of WO2024032077A1 publication Critical patent/WO2024032077A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity

Definitions

  • the present application relates to the field of communications, and in particular, to an uplink transmission method and a communications device.
  • Extended reality is a multimedia service with strong real-time performance and large data capacity requirements.
  • XR includes virtual reality (VR), augmented reality (AR) and cloud gaming (CG).
  • VR virtual reality
  • AR augmented reality
  • CG cloud gaming
  • the fifth generation mobile communications technology (5th generation mobile networks, 5G) new radio (NR) standard introduces discontinuous reception (DRX) technology for power saving.
  • the basic mechanism of DRX is to configure the DRX cycle for the terminal.
  • the terminal normally monitors the physical downlink control channel (PDCCH).
  • PDCCH physical downlink control channel
  • Two timers, drx-HARQ-RTT-TimerUL and drx-Retransmisson-TimerUL are defined in DRX for uplink data retransmission processing. Specifically, after the terminal transmits the physical uplink shared channel (PUSCH), the drx-HARQ-RTT-TimerUL timer will be started. After the timer times out, the drx-Retransmisson-TimerUL timer will be started. The terminal needs to be in drx -Listen to PDCCH during the Retransmisson-TimerUL timer. Then, if the terminal itself is in sleep state during the drx-Retransmisson-TimerUL timer, it needs to wake up and listen to the PDCCH, which will increase the power consumption of the terminal.
  • PUSCH physical uplink shared channel
  • This application provides an uplink transmission method and communication device, which can save or reduce the power consumption of the terminal.
  • an uplink transmission method is provided.
  • the method can be executed by a terminal, or by components of the terminal (such as a processor, a chip, or a chip system, etc.), or by a device that can realize all or part of the terminal functions.
  • Logic module or software implementation can be executed by a terminal, or by components of the terminal (such as a processor, a chip, or a chip system, etc.), or by a device that can realize all or part of the terminal functions.
  • Logic module or software implementation can be executed by a terminal, or by components of the terminal (such as a processor, a chip, or a chip system, etc.), or by a device that can realize all or part of the terminal functions.
  • the method includes: sending uplink data to a network device and starting a first timer; when the first condition is met, starting a second timer at time t1, and monitoring the uplink data before the second timer times out or stops. retransmission authorization.
  • the duration of the first timer is the shortest duration before the retransmission authorization for the uplink data is expected to be received.
  • t1 t2+T
  • t2 represents the time when the first timer times out
  • T represents the time interval between the time when the first timer times out and the start time of the next activation period.
  • the first condition is: the time when the first timer times out is in the inactive period, and the time interval is less than the remaining scheduling time of the uplink data.
  • the activation period refers to the period when the PDCCH needs to be monitored, and the inactive period refers to the period when the PDCCH does not need to be monitored.
  • the first timer may be started at the end of the last symbol of the uplink data.
  • the remaining scheduling time of the uplink data refers to the remaining scheduling time of the uplink data at the moment when the first timer times out.
  • the time when the first timer (such as drx-HARQ-RTT-TimerUL) times out is in the inactive period, and between the time when the first timer times out and the start time of the next activation period If the time interval is less than the remaining scheduling time of the uplink data, the second timer (such as drx-RetransmissionTimerUL) may not be started when the first timer times out, but the second timer may be started in the next activation period.
  • the terminal Since the terminal does not need to enter the activation state to monitor the retransmission authorization for the uplink data when the first timer expires, and the terminal already needs to monitor the PDCCH in the next activation period, turning on the second timer in the next activation period will not cause any problems. Additional power consumption is required, so the method provided by this application can save power consumption.
  • the method may also include: if the second condition is met, starting a second timer at the moment when the first timer times out, and listening for the response to the second timer before the second timer times out or stops. Retransmission authorization of upstream data.
  • the second condition is: the time when the first timer times out is in the activation period, or the time when the first timer times out is in the inactive period, and the time interval is greater than or equal to the remaining scheduling time of the uplink data.
  • the uplink data can be retransmitted in a timely manner to avoid the delay caused by untimely scheduling. Uplink data is invalid.
  • the method may further include: receiving configuration information from the network device. Further, it can be determined according to the configuration information that when the first condition is met, the second timer is started at time t1.
  • the method may also include: receiving configuration information from the network device. Further, it may be determined according to the configuration information that when the second condition is met, the second timer is started at the moment when the first timer times out.
  • the configuration information may be carried through physical layer signaling or high-layer signaling.
  • the physical layer signaling can be downlink control information (DCI).
  • the high-level signaling may be medium access control control element (MAC CE) or radio resource control (radio resource control, RRC) signaling.
  • MAC CE medium access control control element
  • RRC radio resource control
  • the configuration information may be jointly determined through physical layer signaling and high-layer signaling.
  • MAC CE or RRC can configure a candidate set, and DCI can indicate a candidate content in the candidate set.
  • the network device can flexibly configure the triggering method of starting the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • an uplink transmission method is provided.
  • the method can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation are examples of the network functions.
  • the method includes: receiving uplink data from a terminal and starting a first timer; if the first condition is met, starting a second timer at time t1, and sending a message to the terminal before the second timer times out or stops. Superior Authorization for retransmission of row data. If the second condition is met, the second timer is started when the first timer times out, and a retransmission authorization for the uplink data is sent to the terminal before the second timer times out or stops.
  • the duration of the first timer is the shortest duration before the terminal expects to receive a retransmission authorization for the uplink data.
  • t1 t2+T
  • t2 represents the time when the first timer times out
  • T represents the time interval between the time when the first timer times out and the start time of the next activation period.
  • the first condition is: the time when the first timer times out is in the inactive period, and the time interval is less than the remaining scheduling time of the uplink data.
  • the second condition is: the moment when the first timer times out is in the active period; or the moment when the first timer times out is in the inactive period, and the time interval is greater than or equal to the remaining scheduling time of the uplink data.
  • the activation period refers to the period when the PDCCH needs to be monitored, and the inactive period refers to the period when the PDCCH does not need to be monitored.
  • the first timer may be started at the end of the last symbol of the uplink data.
  • the remaining scheduling time of the uplink data refers to the remaining scheduling time of the uplink data at the moment when the first timer times out.
  • the time when the first timer times out is in the inactive period, and the time interval between the time when the first timer times out and the start time of the next activation period is less than the remaining scheduling time of the uplink data.
  • the second timer may not be started when the first timer times out, but the second timer may be started in the next activation period. Since the terminal does not need to enter the activation state to monitor the retransmission authorization for the uplink data when the first timer expires, and the terminal already needs to monitor the PDCCH in the next activation period, turning on the second timer in the next activation period will not cause any problems. Additional power consumption is required, so the method provided by this application can save power consumption.
  • the uplink data can be retransmitted in a timely manner to avoid causing the uplink data to be retransmitted due to untimely scheduling. Invalid.
  • the method before receiving the uplink data from the terminal, may also include: if the first condition is met, sending first uplink authorization information to the terminal; if the second condition is met, Send the second uplink authorization information to the terminal. Wherein, the first uplink authorization information and the second uplink authorization information are both used to schedule the uplink data.
  • the first uplink grant information indicates a first modulation and coding scheme (MCS)
  • the second uplink grant information indicates a second MCS.
  • the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS, and/or the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS.
  • the first uplink grant information indicates a first transmission resource
  • the second uplink grant information indicates a second transmission resource
  • the first transmission resource is less than the second transmission resource
  • the first uplink authorization information indicates that the uplink data is not to be repeatedly transmitted during the first transmission
  • the second uplink authorization information indicates that the uplink data is to be repeatedly transmitted during the first transmission
  • the method may also include: sending configuration information to the terminal.
  • the configuration information instructs the terminal to start the second timer at time t1 if the first condition is met, and to start the second timer at the time when the first timer times out if the second condition is met. .
  • the network device can flexibly configure the triggering method of starting the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • an uplink transmission method is provided.
  • the method can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation are examples of the network functions.
  • the method includes: when the first condition is met, sending first uplink authorization information to the terminal; when the second condition is met, sending second uplink authorization information to the terminal; receiving uplink data from the terminal and starting First timer.
  • the duration of the first timer is the shortest duration before the terminal expects to receive a retransmission authorization for the uplink data.
  • the first uplink authorization information and the second uplink authorization information are both used for scheduling uplink data.
  • the first uplink authorization information indicates the first MCS
  • the second uplink authorization information indicates the second MCS.
  • the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS, and/or the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS.
  • the first condition is: the time when the first timer times out is in the inactive period, and the time interval is less than the time interval between the time when the first timer times out and the start time of the next activation period.
  • the second condition is: the moment when the first timer times out is in the active period, or the moment when the first timer times out is in the inactive period, and the time interval is greater than or equal to the remaining scheduling time of the uplink data.
  • the uplink transmission method provided by this application determines whether the time when the first timer times out and the start of the next activation period are within the range of the remaining scheduling time on the premise that the time when the first timer times out is in the inactive period.
  • the reliability of uplink transmission can be dynamically adjusted to better match services and improve service capacity. For example, when the time when the first timer times out is not within the remaining scheduling time from the start of the next activation period, by configuring reasonable parameters to improve the reliability of uplink transmission, retransmissions can be avoided as much as possible, so that Ensure that XR data is transmitted correctly before failure to improve user experience.
  • the first uplink grant information also indicates a first transmission resource
  • the second uplink grant information also indicates a second transmission resource, where the first transmission resource is less than the second transmission resource.
  • the reliability of uplink transmission can be dynamically adjusted by configuring transmission resources of different sizes in different scenarios.
  • the first uplink authorization information also indicates that the uplink data is not to be repeatedly transmitted during the first transmission, and the second uplink authorization information indicates that the uplink data is to be repeatedly transmitted during the first transmission.
  • the reliability of uplink transmission can be dynamically adjusted by configuring whether repeated transmission is required in different scenarios.
  • the method may also include: if the first condition is met, starting a second timer at time t1, and sending a message for the uplink data to the terminal before the second timer times out or stops. Heavy transmission authorization; if the second condition is met, the second timer is started when the first timer times out, and a retransmission authorization for the uplink data is sent to the terminal before the second timer times out or stops.
  • t1 t2+T
  • t2 represents the time when the first timer times out
  • T represents the time interval.
  • the method may also include: sending configuration information to the terminal.
  • the configuration information instructs the terminal to start the second timer at time t1 if the first condition is met, and to start the second timer at the time when the first timer times out if the second condition is met. .
  • the network device can flexibly configure the triggering method of starting the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • an uplink transmission method is provided.
  • the method can be executed by the terminal, or by components of the terminal (such as a processor, a chip, or a chip system, etc.), or by a device that can realize all or part of the terminal functions.
  • Logic module or software implementation can be executed by the terminal, or by components of the terminal (such as a processor, a chip, or a chip system, etc.), or by a device that can realize all or part of the terminal functions. Logic module or software implementation.
  • the method includes: sending uplink data to a network device; when the time interval between the time when the uplink data is sent and the start time of the next activation period is less than the remaining scheduling time of the uplink data, at the start of the next activation period Monitor the retransmission authorization for the uplink data at all times until the retransmission authorization for the uplink data is detected or until the end of the next activation period.
  • the activation period refers to the period when the PDCCH needs to be monitored, and the inactive period refers to the period when the PDCCH does not need to be monitored.
  • the remaining scheduling time of the uplink data refers to the remaining scheduling time of the uplink data at the moment when the uplink data is sent.
  • the time when the uplink data is completely sent may be the end time of the last symbol of the uplink data.
  • the terminal when the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data, it can monitor during the next activation period.
  • Retransmission authorization for the uplink data so there is no need to start the first timer (for example, drx-HARQ-RTT-TimerUL) and the second timer (for example, drx-RetransmissionTimerUL), nor does it need to wait until the second timer times out
  • the retransmission authorization for the uplink data is monitored in advance, thereby saving the power consumption of the terminal.
  • the method may further include: when the time interval between the time when the uplink data is sent and the start time of the next activation period is greater than or equal to the remaining scheduling time of the uplink data, before sending Start the first timer when the uplink data is completed, start the second timer when the first timer times out, and monitor the retransmission authorization for the uplink data before the second timer times out or stops.
  • the duration of the server is the shortest length of time before it expects to receive a retransmission authorization for the uplink data.
  • the first timer expires when the time interval expires.
  • the uplink data can be scheduled for retransmission in time to avoid failure of the uplink data due to untimely scheduling.
  • the method may also include: receiving configuration information from the network device. Further, it can be determined according to the configuration information that when the time interval is less than the remaining scheduling time, the retransmission authorization for the uplink data is monitored at the beginning of the next activation period until the retransmission authorization for the uplink data is heard or until The next activation period ends.
  • the method may also include: receiving configuration information from the network device. Further, it is determined according to the configuration information that when the time interval is greater than or equal to the remaining scheduling time, the first timer is started at the moment when the uplink data is sent.
  • the configuration information may be carried through physical layer signaling or high-layer signaling.
  • physical layer signaling can be DCI.
  • high-level signaling can be MAC CE or RRC signaling.
  • the configuration information may be jointly determined through physical layer signaling and high-layer signaling.
  • MAC CE or RRC can configure a candidate set, and DCI can indicate a candidate content in the candidate set.
  • network equipment can flexibly configure the triggering method of starting the first timer and/or the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • an uplink transmission method is provided.
  • the method can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions.
  • Logic module or software implementation can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions. Logic module or software implementation.
  • the method includes: receiving uplink data from a terminal; when the time interval between the time when the uplink data is received and the start time of the next activation period is less than the remaining scheduling time of the uplink data, and the uplink data is not successfully received, Send a retransmission authorization for the uplink data to the terminal before the end of the next activation period; the time interval between the time when the uplink data is received and the start time of the next activation period is greater than or equal to the remaining scheduling time of the uplink data , and if the uplink data is not successfully received, the first timer is started when the uplink data is received, and the second timer is started when the first timer times out, and before the second timer times out or stops.
  • a retransmission authorization for the uplink data is sent to the terminal, and the duration of the first timer is the shortest time before the terminal expects to receive the retransmission authorization for the uplink data.
  • time when the network device receives the uplink data is the same as the time when the terminal completes sending the uplink data.
  • the terminal when the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data, it can monitor during the next activation period.
  • Retransmission authorization for the uplink data so there is no need to start the first timer (for example, drx-HARQ-RTT-TimerUL) and the second timer (for example, drx-RetransmissionTimerUL), nor does it need to wait until the second timer times out
  • the retransmission authorization for the uplink data is monitored in advance, thereby saving the power consumption of the terminal.
  • the second timer is started at the time when the first timer times out.
  • the uplink data can be retransmitted and scheduled in time to avoid the failure of the uplink data due to untimely scheduling.
  • the method before receiving uplink data from the terminal, may also include: when the time interval is less than the remaining scheduling time, sending the first uplink authorization information to the terminal; If the remaining scheduling time is greater than or equal to the remaining scheduling time, the second uplink authorization information is sent to the terminal. in, Both the first uplink authorization information and the second uplink authorization information are used to schedule the uplink data.
  • the first uplink authorization information indicates the first MCS
  • the second uplink authorization information indicates the second MCS.
  • the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS, and/or the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS.
  • the first uplink grant information indicates a first transmission resource
  • the second uplink grant information indicates a second transmission resource
  • the first transmission resource is less than the second transmission resource
  • the first uplink authorization information indicates that the uplink data is not to be repeatedly transmitted during the first transmission
  • the second uplink authorization information indicates that the uplink data is to be repeatedly transmitted during the first transmission
  • the network device can dynamically adjust the reliability of the uplink transmission by judging whether the time interval between this moment and the start of the next activation period is within the range of the remaining scheduling time when receiving uplink data, so as to be able to compare Good matching business, improve business capacity. For example, when the time when the network device receives the uplink data is not within the remaining scheduling time from the start of the next activation period, by configuring reasonable parameters to improve the reliability of the uplink transmission, retransmissions can be avoided as much as possible, so that Ensure that XR data is transmitted correctly before failure to improve user experience.
  • the method may also include: sending configuration information to the terminal.
  • the configuration information indicates that when the time interval is less than the remaining scheduling time, the terminal monitors the retransmission authorization for the uplink data at the beginning of the next activation period until it monitors the retransmission authorization for the uplink data or Until the end of the next activation period, and if the time interval is greater than or equal to the remaining scheduling time, the first timer is started at the moment when the uplink data is received.
  • network equipment can flexibly configure the triggering method of starting the first timer and/or the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • the sixth aspect provides an uplink transmission method.
  • the method can be executed by the network, or by components of the network (such as processors, chips, or chip systems, etc.), or by a device that can realize all or part of the network functions. Logic module or software implementation.
  • the method includes: when the time interval between the moment when the uplink data is received and the start time of the next activation period is less than the remaining scheduling time of the uplink data, sending the first uplink authorization information to the terminal, and when the time interval is greater than or equal to In the case of the remaining scheduling time, the second uplink authorization information is sent to the terminal; and the uplink data from the terminal is received.
  • the first uplink authorization information and the second uplink authorization information are both used to schedule the uplink data.
  • the first uplink authorization information indicates the first MCS
  • the second uplink authorization information indicates the second MCS.
  • the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS
  • the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS.
  • time when the network device receives the uplink data is the same as the time when the terminal completes sending the uplink data.
  • the network device can dynamically adjust the reliability of the uplink transmission by judging whether the time interval between this moment and the start of the next activation period is within the range of the remaining scheduling time at the moment when the uplink data is received. , so that it can better match the business and improve the business capacity. For example, when the time when the network device receives the uplink data is not within the remaining scheduling time from the start of the next activation period, by configuring reasonable parameters to improve the reliability of the uplink transmission, retransmissions can be avoided as much as possible, so that Ensure that XR data is transmitted correctly before failure to improve user experience.
  • the first uplink grant information also indicates a first transmission resource
  • the second uplink grant information also indicates a second transmission resource, where the first transmission resource is less than the second transmission resource.
  • the reliability of uplink transmission can be dynamically adjusted by configuring transmission resources of different sizes in different scenarios.
  • the first uplink authorization information also indicates that the uplink data is not to be repeatedly transmitted during the first transmission, and the second uplink authorization information indicates that the uplink data is to be repeatedly transmitted during the first transmission.
  • the reliability of uplink transmission can be dynamically adjusted by configuring whether repeated transmission is required in different scenarios.
  • the method may further include: when the time interval is less than the remaining scheduling time and the uplink data is not successfully received, sending a message for the uplink data to the terminal in the next activation period.
  • Retransmission authorization if the time interval is greater than or equal to the remaining scheduling time and the uplink data is not successfully received, the first timer is started at the moment when the uplink data is received, and is started at the moment when the first timer times out. the second timer, and sends a retransmission authorization for the uplink data to the terminal before the second timer times out or stops.
  • the duration of the first timer is the shortest time before the terminal expects to receive a retransmission authorization for the uplink data. duration.
  • the terminal can monitor the uplink data during the next activation period.
  • Retransmit authorization so there is no need to start the first timer (eg, drx-HARQ-RTT-TimerUL) and the second timer (eg, drx-RetransmissionTimerUL), and there is no need to listen for the uplink before the second timer expires.
  • Data retransmission authorization can save the power consumption of the terminal.
  • the second timer is started at the time when the first timer times out.
  • the uplink data can be retransmitted and scheduled in time to avoid the failure of the uplink data due to untimely scheduling.
  • the method may further include: sending configuration information to the terminal.
  • the configuration information indicates that when the time interval is less than the remaining scheduling time, the terminal monitors the retransmission authorization for the uplink data at the beginning of the next activation period until it monitors the retransmission authorization for the uplink data or Until the end of the next activation period, and if the time interval is greater than or equal to the remaining scheduling time, the first timer is started at the moment when the uplink data is received.
  • network equipment can flexibly configure the triggering method of starting the first timer and/or the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • a seventh aspect provides a communication device, including a module or unit for performing: the method in the first aspect or any possible implementation of the first aspect, or the fourth aspect or any one of the fourth aspects.
  • a communication device including a module or unit for performing the method in the second aspect or any one of the possible implementations of the second aspect, or the third aspect or any one of the possible implementations of the third aspect.
  • Modules or units of the method in the implementation, or modules or units of the method in the fifth aspect or any possible implementation of the fifth aspect, or modules or units of the sixth aspect or any possible implementation of the sixth aspect The module or unit of the method.
  • a communication device including a processor, the processor is coupled to a memory, and the memory is For storing computer programs or instructions, the processor is used to execute the computer programs or instructions stored in the memory to implement: the first aspect or the method in any possible implementation of the first aspect, or the fourth aspect or any of the fourth aspects. A method among possible implementations.
  • the device further includes a memory coupled to the processor.
  • processors there are one or more processors, and/or one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the device is a terminal.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip of the terminal.
  • the communication interface may be an input/output interface.
  • a communication device including a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions, and the processor is used to execute the computer programs or instructions stored in the memory to achieve: the second aspect or the third aspect.
  • the method in any of the possible implementations of the second aspect, or the method of the third aspect or any of the possible implementations of the third aspect, or the method of the fifth aspect or any of the possible implementations of the fifth aspect , or the sixth aspect or the method in any possible implementation manner of the sixth aspect.
  • the device further includes a memory coupled to the processor.
  • processors there are one or more processors, and/or one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the device is a network device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip in a network device.
  • the communication interface may be an input/output interface.
  • a processor including: an input circuit, an output circuit and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method in any of the above aspects or any possible implementation of any aspect.
  • the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times.
  • This application does not limit the specific implementation methods of the processor and various circuits.
  • a communication system including the aforementioned terminal and/or network device.
  • a computer program product includes: a computer program (which can also be called a code, or an instruction).
  • a computer program which can also be called a code, or an instruction.
  • the computer program When the computer program is run, it causes the computer to perform any of the above aspects or any one of the above.
  • a computer-readable storage medium stores a computer program (which can also be called a code, or an instruction).
  • a computer program which can also be called a code, or an instruction.
  • the computer program When the computer program is run on a computer, it causes the computer to perform any of the above tasks.
  • a method in any possible implementation of one aspect or any aspect.
  • a chip including a processor for calling and running a computer program from a memory, so that the communication device installed with the chip executes any of the above aspects or any of the possible implementations of any of the aspects. method within the method.
  • Figure 1 is a schematic diagram of an example communication system provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of XR video frame arrival provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of a DRX cycle provided by an embodiment of the present application.
  • Figure 4 is a schematic diagram of a DRX cycle provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of downlink retransmission processing provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of uplink retransmission processing provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of an uplink transmission method provided by an embodiment of the present application.
  • Figure 8 is a timing diagram of an example of data transmission provided by an embodiment of the present application.
  • Figure 9 is a timing diagram of another example of data transmission provided by an embodiment of the present application.
  • Figure 10 is a timing diagram of another example of data transmission provided by the embodiment of the present application.
  • Figure 11 is a schematic flow chart of an uplink transmission method provided by an embodiment of the present application.
  • Figure 12 is a schematic flow chart of an uplink transmission method provided by an embodiment of the present application.
  • Figure 13 is a schematic flow chart of an uplink transmission method provided by an embodiment of the present application.
  • Figure 14 is a timing diagram of an example of data transmission provided by the embodiment of the present application.
  • Figure 15 is a timing diagram of another example of data transmission provided by the embodiment of the present application.
  • Figure 16 is a schematic flow chart of an uplink transmission method provided by an embodiment of the present application.
  • Figure 17 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • Figure 18 is a schematic block diagram of another communication device provided by an embodiment of the present application.
  • Figure 19 is a schematic structural diagram of an example terminal provided by an embodiment of the present application.
  • Figure 20 is a schematic structural diagram of an example of network equipment provided by an embodiment of the present application.
  • A/B can mean A or B; “and/or” in this application only means It is an association relationship that describes related objects. It means that there can be three relationships.
  • a and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. Among them, A and B Can be singular or plural.
  • plural means two or more than two. “At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple .
  • words such as “first” and “second” are used to distinguish identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as “first” and “second” do not refer to the quantity and execution. The row order is limited, and the words “first”, “second” and so on are not necessarily different.
  • LTE long term evolution
  • 5G fifth generation
  • NR new radio
  • the terminal in the embodiment of this application may refer to (user equipment, UE), station, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal , wireless communications equipment, user agent or user device.
  • the terminal may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or a device with wireless communication capabilities Handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in 5G networks or terminals in future evolved public land mobile communications networks (public land mobile network, PLMN), etc.,
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • Handheld devices computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in 5G networks or terminals in future evolved public land mobile communications networks (public land mobile network, PLMN), etc.
  • the network device in the embodiment of the present application may be a device used to communicate with a terminal.
  • the network device may be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (TRP), or a next generation base station (next generation NodeB, gNB) in a 5G mobile communication system , base stations in future mobile communication systems or access points (APs) in WiFi systems, etc.
  • the network device can also be a module or unit that completes part of the functions of the base station.
  • it can be a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU).
  • the network device can also be a wireless controller, a relay station, an access point, a vehicle-mounted device, a wearable device, or other communication systems that will evolve in the future in a cloud radio access network (CRAN) scenario.
  • CRAN cloud radio access network
  • the terminal or network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • This hardware layer includes hardware such as central processing unit (CPU), memory management unit (MMU) and memory (also called main memory).
  • the operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux operating system, Unix operating system, Android operating system, iOS operating system or windows operating system, etc.
  • This application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided by the embodiment of the present application, as long as the program that records the code of the method provided by the embodiment of the present application can be run to provide according to the embodiment of the present application.
  • the execution subject of the method provided by the embodiment of the present application can be a terminal or a network device, or a functional module in the terminal or network device that can call a program and execute the program.
  • various aspects or features of the present application may be implemented as methods, apparatus, or articles of manufacture using standard programming and/or engineering techniques.
  • article of manufacture encompasses a computer program accessible from any computer-readable device, carrier or medium.
  • computer-readable media may include, but are not limited to: magnetic storage devices (eg, hard disks, floppy disks, tapes, etc.), optical disks (eg, compact discs (CD), digital versatile discs (DVD)) etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (erasable programmable read-only memory, EPROM), card, stick or key drive, etc.).
  • various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • machine-readable medium may include, but is not limited to, wireless channels and various other media capable of storing, containing and/or carrying instructions and/or data.
  • Figure 1 shows a schematic block diagram of a communication system suitable for this application.
  • the communication system 100 may include at least one terminal, such as the terminal 110 shown in FIG. 1 ; the communication system 100 may also include at least one network device, such as the network device 120 shown in FIG. 1 . Signals can be transmitted between the terminal 110 and the network device 120.
  • the signal sent by the network device 120 to the terminal 110 is called downlink (DL) transmission (or downlink communication), and the signal sent by the terminal 110 to the network device 120 is called uplink (uplink). , UL) transmission (or uplink communication).
  • DL downlink
  • uplink uplink
  • UL uplink communication
  • the communication system shown in Figure 1 may also include more network nodes, such as more terminals or network devices, and the embodiments of the present application will not be shown one by one in the figure.
  • the business model usually arrives periodically based on the frame rate. For example, see the XR video frame arrival diagram shown in Figure 2.
  • a video with a frame rate of 60 frames per second (FPS) ideally arrives at a frame every 16.67 milliseconds. Because the generation and arrival of data packets for XR transmission services and video transmission services are not continuous.
  • FPS frames per second
  • listening to the downlink control signaling of network equipment in each time slot is beneficial to receiving uplink authorization or downlink data, but it also brings a cost to the terminal in terms of power consumption.
  • DRX discontinuous reception
  • each DRX cycle consists of a wake-up period (On Duration) and a sleep period (Opportunity for DRX).
  • On Duration the terminal monitors and receives PDCCH.
  • Opportunity for DRX period the terminal has the opportunity to enter the sleep state and does not receive PDCCH to reduce power consumption.
  • the terminal in the dormant state only does not receive PDCCH, but can receive data from other physical channels, such as physical downlink shared channel (PDSCH), acknowledgment signal (acknowledge, ACK), etc.
  • PDSCH physical downlink shared channel
  • ACK acknowledgment signal
  • ACK acknowledgment signal
  • each terminal can be configured with two DRX cycles: short DRX cycle (shortDRX-Cycle) and long DRX cycle (longDRX-Cycle).
  • short DRX cycle shortDRX-Cycle
  • long DRX cycle longDRX-Cycle
  • FIG. 4 shows an example of a short DRX cycle and a long DRX cycle. At any time, the terminal can only use one configuration of the short DRX cycle and the long DRX cycle.
  • DRX is also configured with two parameters, drx-RetransmissionTimerDL and drx-HARQ-RTT-TimerDL, for downlink data retransmission processing, and two parameters, drx-RetransmissionTimerUL and drx-HARQ-RTT-TimerUL, for uplink data retransmission processing. transfer processing.
  • Each downstream process corresponds to a drx-RetransmissionTimerDL and a drx-HARQ-RTT-TimerDL
  • each upstream process corresponds to A drx-RetransmissionTimerUL and a drx-HARQ-RTT-TimerUL.
  • Figure 5 shows a schematic diagram of an example of downlink retransmission processing.
  • the terminal receives the PDSCH according to the received PDCCH. If the terminal does not successfully receive the PDSCH, it sends a negative acknowledgment (negative acknowledgment, NACK) for the PDSCH to the network device. Moreover, after sending NACK, the terminal turns on drx-HARQ-RTT-TimerDL. During the operation of drx-HARQ-RTT-TimerDL, the network device will not perform retransmission scheduling for the PDSCH. The retransmission scheduling for the PDSCH will not be performed until drx-HARQ-RTT-TimerDL times out.
  • NACK negative acknowledgment
  • the terminal enters the inactive state and does not listen to the PDCCH.
  • the terminal turns on drx-RetransmissionTimerDL, enters the activation state, and starts monitoring the network side for retransmission authorization of the PDSCH.
  • the terminal monitors the retransmission authorization for the PDSCH, it stops the timing of drx-RetransmissionTimerDL, and receives the retransmitted PDSCH according to the retransmission authorization for the PDSCH.
  • Figure 6 shows a schematic diagram of an example of uplink retransmission processing.
  • the terminal sends PUSCH according to the received PDCCH. Regardless of whether the network device successfully receives the PUSCH, after sending the PUSCH, the terminal will turn on drx-HARQ-RTT-TimerUL. During the operation of drx-HARQ-RTT-TimerUL, the network device will not perform retransmission scheduling for the PUSCH. The retransmission scheduling for the PUSCH will not be performed until drx-HARQ-RTT-TimerUL times out. Therefore, during the operation of drx-HARQ-RTT-TimerUL, the terminal enters the inactive state and does not listen to the PDCCH.
  • the terminal When drx-HARQ-RTT-TimerUL times out, the terminal turns on drx-RetransmissionTimerUL, enters the activation state, and starts monitoring the network side for retransmission authorization of the PUSCH.
  • the terminal detects the retransmission authorization for the PUSCH, it stops the timing of drx-RetransmissionTimerUL, and retransmits the PUSCH according to the retransmission authorization for the PUSCH.
  • XR business mainly includes VR, AR, and CG.
  • VR and CG need to upload pose or control information.
  • pose or control information is uploaded periodically, and the cycle is generally 4ms.
  • video frames also need to be uploaded.
  • Common video frame rates are 30FPS, 60FPS, 90FPS, 120FPS, etc., and the corresponding periods are 33.33ms, 16.67ms, 11.11ms, 8.33ms, etc.
  • XR video frames need to be transmitted within a given delay. Exceeding the given delay will result in failure to render on the terminal side and server side.
  • the data packet delay budget for uplink AR transmission is generally 30ms
  • the data packet delay budget for attitude or control information is generally 10ms.
  • DRX is configured according to the downlink service transmission pattern (traffic pattern) (for example, cycle 16.67ms). Uplink attitude or control data is more frequent (for example, the period is 4ms). If the terminal has to monitor the PDCCH during the drx-Retransmisson-TimerUL period that is started when the drx-HARQ-RTT-TimerUL times out after each PUSCH transmission, it will cause greater power consumption.
  • traffic pattern for example, cycle 16.67ms
  • Uplink attitude or control data is more frequent (for example, the period is 4ms).
  • this application provides an uplink transmission solution.
  • drx-Retransmisson-TimerUL When the uplink data can be delayed to be retransmitted in the next activation period, drx-Retransmisson-TimerUL will no longer be started after the uplink data is transmitted this time.
  • An activation period starts drx-Retransmisson-TimerUL. Since the terminal does not need to activate drx-Retransmisson-TimerUL, it does not need to enter the activation state to monitor PDCCH when drx-HARQ-RTT-TimerUL times out, and the terminal already needs to monitor PDCCH during the next activation period and enable drx- Retransmisson-TimerUL will not bring additional power consumption, so the solution provided by this application can save power consumption.
  • Activation period (DRX active time): During this period, the terminal needs to monitor PDCCH.
  • the activation period may include an On Duration period, a drx-RetransmissionTimerDL run period, and a drx-RetransmissionTimerUL run period.
  • Inactive time (DRX inactive time): During this period, the terminal does not need to monitor PDCCH.
  • the inactive period may include a drx-HARQ-RTT-TimerDL running period, a drx-HARQ-RTT-TimerUL running period, a drx-InactivityTimer running period, and other periods that do not require monitoring of the PDCCH.
  • drx-InactivityTimer is not mentioned in this application, but reference can be made to the prior art.
  • the first timer It can be drx-HARQ-RTT-TimerUL, or it can be a timer with the same function as drx-HARQ-RTT-TimerUL.
  • the duration of the first timer is the shortest duration before a retransmission authorization for the uplink data is expected to be received. That is to say, the earliest the terminal can receive the retransmission authorization for the uplink data is after the first timer times out, or in other words, the earliest the network device can send the retransmission authorization for the uplink data is after the first timer times out.
  • the first timer is drx-HARQ-RTT-TimerUL
  • the duration of the first timer is the duration of drx-HARQ-RTT-TimerUL.
  • the retransmission grant for the uplink data may refer to the PDCCH or DCI that schedules the retransmission of the uplink data.
  • the period during which the first timer is running is an inactive period, that is, during the period when the first timer is running, the terminal does not need to monitor the PDCCH, and accordingly, the network device does not send the PDCCH.
  • the second timer It can be drx-Retransmisson-TimerUL, or it can be a timer with the same function as drx-Retransmisson-TimerUL.
  • the network device may send the retransmission schedule for the uplink data before the second timer times out, and accordingly, the terminal may monitor the retransmission schedule for the uplink data before the second timer times out. Once the terminal monitors the retransmission schedule for uplink data, the second timer can stop timing.
  • the network device receives uplink data:
  • the network device receives uplink data means that the network device attempts to receive uplink data on the resource configured to send the uplink data to the terminal, but the result of the reception may be that the network device receives the uplink data sent by the terminal. , it may also be that the network device did not receive the uplink data sent by the terminal.
  • the network device also needs to demodulate or decode the uplink data. If the network device correctly demodulates or decodes the uplink data, it is said that the network device has correctly received the uplink data. If the network device does not demodulate or decode this upstream data correctly, it is said to be a network device reception error. If the network device does not receive the uplink data or receives the uplink data but receives an error, the network device will schedule retransmission of the uplink data.
  • the failure of the network device to successfully receive the uplink data described in this article includes two situations: the network device does not receive the uplink data and the network device receives the uplink data but receives an error. Successful reception of uplink data by a network device means that the network device correctly receives the uplink data.
  • the network device in the schematic flow chart may also be a chip, chip system, or processor that supports the network device to implement the method, or may be a logic module or software that can realize all or part of the network device functions;
  • schematic flow chart The terminal in the figure may also be a chip, chip system, or processor that supports the terminal to implement the method, or may be capable of realizing all or part of the terminal functions.
  • Logic modules or software are examples of the network device in the schematic flow chart.
  • Figure 7 is a schematic flow chart of an uplink transmission method provided by this application.
  • the method 200 may include S210 and S220.
  • S210 The terminal sends uplink data to the network device and starts the first timer. Accordingly, the network device receives the uplink data and starts the first timer.
  • the terminal sends uplink data according to the schedule of the network device, and can start the first timer after sending the uplink data.
  • the network device receives the uplink data.
  • the first timer is started if the network device does not successfully receive the uplink data. In another example, the first timer is started regardless of whether the network device successfully receives the uplink data.
  • the uplink data may be PUSCH, or in other words, the uplink data is carried or carried in PUSCH.
  • the first timer may be started after the last symbol of the uplink data is sent/received.
  • the first timer is drx-HARQ-RTT-TimerUL
  • the starting time of the first timer is the starting time of drx-HARQ-RTT-TimerUL in the prior art.
  • the retransmitted uplink data can be exactly the same as the uplink data, or the retransmitted uplink data has the same content as the uplink data, but the redundancy version (RV) version may not affect the decoding of the uplink data.
  • the rest of the content can be different.
  • S220 If the first condition is met, the terminal starts the second timer at time t1, and monitors the retransmission authorization for the uplink data before the second timer times out or stops.
  • the network device starts the second timer at time t1, and sends a retransmission authorization for the uplink data to the terminal before the second timer times out or stops.
  • the first condition is: the time t2 when the first timer times out is in the inactive period, and the time interval T is less than the remaining scheduling time of the uplink data.
  • the terminal can start the second timer at the start time t1 of the next activation period, and listen for retransmission authorization for the uplink data before the second timer times out or stops.
  • the network device does not successfully receive the uplink data sent by the terminal in S210, it starts the second timer at time t1, and sends a retransmission authorization for the uplink data to the terminal before the second timer times out or stops.
  • the network device may start the second timer or not. However, regardless of whether the second timer is started or not, the network device does not need to schedule the terminal pair. Retransmission of the uplink data.
  • the next activation period may refer to a period that needs to monitor the PDCCH after the moment when the first timer times out and is closest in time to the moment when the first timer times out.
  • the next activation period may be the drx-RetransmissionTimerDL running period after and closest in time to the moment when the first timer times out.
  • the next activation period may also refer to: the On Duration period after the moment when the first timer times out and is closest in time to the moment when the first timer times out.
  • the moment when the next activation period starts may refer to the starting position of the first symbol of the next activation period.
  • the remaining scheduling time of the uplink data refers to the remaining scheduling time of the uplink data at the moment when the first timer times out. between. This uplink data has transmission delay requirements. If the uplink data has not been scheduled within the remaining scheduling time, the uplink data becomes invalid.
  • a packet delay budget may be used to represent the transmission delay requirement of the uplink data. For example, assuming that the PDB is 30ms, then the uplink data needs to be scheduled within 30ms. If the uplink data has not been scheduled for more than 30ms, the uplink data will be invalid.
  • the terminal can obtain the PDB through the core network device (the network device is configured through Qos rules), and the terminal itself can sense that at the moment when the first timer times out, the uplink data reaches the cache (for example, RLC cache) ), so the remaining scheduling time can be calculated as PDB-t.
  • the network device can obtain the PDB through the core network device (configured through Qos profile).
  • the terminal reports through scheduling request (SR), buffer status report (BSR), or new media access control control unit (MAC) control unit (control element, CE), etc.
  • SR scheduling request
  • BSR buffer status report
  • MAC media access control unit
  • CE media access control unit
  • the terminal can report the remaining scheduling time of the uplink data to the network device.
  • Monitoring the retransmission authorization for the uplink data before the second timer times out or stops means: monitoring the retransmission authorization for the uplink data from when the second timer is started. If the retransmission authorization for the uplink data is monitored before the second timer times out, then after the retransmission authorization for the uplink data is monitored, the timing of the second timer is stopped. If no retransmission authorization for the uplink data is detected, when the second timer times out, the timer is stopped.
  • the time interval between the drx-HARQ-RTT-TimerUL timeout time t2 and the start time t1 of the next activation period is T
  • the remaining scheduling time of the uplink data is T1
  • T ⁇ T1 the time interval between the drx-HARQ-RTT-TimerUL timeout time t2 and the start time t1 of the next activation period.
  • the terminal since the terminal itself is in an inactive period at time t2, in order to save power consumption, the terminal may not start drx-RetransmissionTimerUL at time t2, but start drx-RetransmissionTimerUL at time t1.
  • the terminal monitors the retransmission authorization for the uplink data, and once the terminal monitors the retransmission authorization for the uplink data, it stops the timing of drx-RetransmissionTimerUL. After the terminal monitors the retransmission authorization for the uplink data, it can retransmit the uplink data based on the retransmission authorization.
  • the moment when the first timer times out is in the inactive period, and the time interval between the moment when the first timer times out and the start of the next activation period is less than the remaining uplink data
  • the second timer may not be started when the first timer times out, but the second timer may be started in the next activation period. Since the terminal does not need to enter the activation state to monitor the retransmission authorization for the uplink data when the first timer expires, and the terminal already needs to monitor the PDCCH in the next activation period, turning on the second timer in the next activation period will not cause any problems. Additional power consumption is required, so the method provided by this application can save power consumption.
  • the method 200 may further include:
  • S230 If the second condition is met, start the second timer at time t2 when the first timer times out, and listen for retransmission authorization for the uplink data before the second timer times out or stops.
  • the network device starts the second timer at time t2 when the first timer times out, and sends a retransmission authorization for the uplink data to the terminal before the second timer times out or stops.
  • the second condition is: the time t2 when the first timer times out is in the activation period, or the time t2 when the first timer times out is in the inactive period, and the time interval T is greater than (or greater than or equal to) the uplink data. Remaining scheduling time T2. It should be understood that failure to satisfy the first condition means satisfying the second condition.
  • the terminal can start the second timer at time t2 and listen for retransmission authorization for the uplink data before the second timer times out or stops.
  • the second timer is started at time t2, and a retransmission authorization for the uplink data is sent to the terminal before the second timer times out or stops. If the network device successfully receives the uplink data sent by the terminal in S210, the network device may or may not start the second timer, but the network device does not need to schedule the terminal to retransmit the uplink data.
  • the terminal is located in drx-RetransmissionTimerDL at drx-HARQ-RTT-TimerUL timeout time t2. Since the terminal itself is in the activation period at time t2, it can turn on drx-RetransmissionTimerUL at time t2 and monitor the retransmission authorization for the uplink data at drx-RetransmissionTimerUL. Moreover, once the terminal monitors the retransmission authorization for the uplink data , then stop the timing of drx-RetransmissionTimerUL. After the terminal monitors the retransmission authorization for the uplink data, it can retransmit the uplink data based on the retransmission authorization.
  • the time interval between the drx-HARQ-RTT-TimerUL timeout time t2 and the next activation period start time t1 (that is, the drx-RetransmissionTimerDL start time) is T, and the remaining scheduling time of the uplink data is T1, T>T1. Then, if the uplink data is not retransmitted within T1, the uplink data will be invalid. Therefore, drx-RetransmissionTimerUL can be started at time t2 regardless of whether time t2 is in the activation period.
  • the terminal monitors the retransmission authorization for the uplink data, and once the terminal monitors the retransmission authorization for the uplink data, it stops the timing of drx-RetransmissionTimerUL. After the terminal monitors the retransmission authorization for the uplink data, it can retransmit the uplink data based on the retransmission authorization.
  • the time when the first timer times out is in the inactive period, and the time interval between the time when the first timer times out and the start time of the next activation period is greater than (or, greater than or equal to) the remaining scheduling of the uplink data.
  • the uplink data can be retransmitted in a timely manner to avoid Failure to schedule in time causes the uplink data to become invalid.
  • this application does not limit the timing for the terminal or network device to determine whether the first condition and/or the second condition is met.
  • the terminal or network device can determine whether the third timer is satisfied when the first timer expires.
  • a condition can also be determined at other times to determine whether the first condition is met. For example, it can be determined at the starting time of the first timer whether the first condition is met.
  • the method may further include:
  • S201 The network device sends configuration information to the terminal.
  • the terminal receives configuration information from the network device. After receiving the configuration information, the terminal executes S220 or S230 after executing S210 according to the configuration information.
  • the configuration information may instruct the terminal to start the second timer at time t1 if the first condition is met, and to start the second timer at time t2 when the first timer times out if the second condition is met.
  • the configuration information can indicate whether the triggering method is conditional triggering or direct triggering.
  • Conditional triggering means: after the first timer times out, it is judged whether the terminal meets the first condition. If the first condition is met, the second timer is started at time t1. If the first condition is not met, that is, the second condition is met, then The second timer is started at time t2 when the first timer times out. In this way, the timer can indirectly instruct the terminal to start the second timer at time t1 if the first condition is met, and to start the second timer at time t2 when the first timer expires if the second condition is met. Start the second timer. In addition, if the triggering mode is direct triggering, there is no need to determine whether the first condition is met, and the second timer is started directly at the time t2 when the first timer times out.
  • the configuration information may be carried through physical layer signaling (such as DCI) or higher layer signaling (such as MAC CE or RRC signaling).
  • physical layer signaling such as DCI
  • higher layer signaling such as MAC CE or RRC signaling
  • a field for example, the Retransmission-Trigger field
  • the Retransmission-Trigger field can be added to the RRC signaling, or 1 bit of information can be added to the DCI to indicate the triggering method.
  • the configuration information may be jointly determined through physical layer signaling and high-layer signaling.
  • MAC CE or RRC can configure a trigger mode candidate set, and DCI can indicate conditional triggering in the trigger mode candidate set.
  • RRC configures a trigger mode candidate set, and the MAC CE can indicate condition triggering in the trigger mode candidate set.
  • RRC configures a set of trigger mode candidate sets, MAC CE indicates the trigger mode candidate set, and DCI can indicate condition triggering in the trigger mode candidate set.
  • the network device can flexibly configure the triggering method of starting the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • Figure 11 is a schematic flow chart of an uplink transmission method provided by this application.
  • the method 300 describes different operations performed by the terminal under different conditions from the perspective of the terminal.
  • the method 300 may include one or more steps from S301 to S306.
  • S304 is executed. If the condition triggers the activation of Retransmission-Timer-UL, S303 is executed.
  • S302 is an optional step.
  • the terminal may not execute S302, but in S301 Then execute S303.
  • the terminal needs to further determine whether it is in the DRX active state at the time when drx-HARQ-RTT-TimerUL times out. If the terminal is in the DRX active state when drx-HARQ-RTT-TimerUL times out, execute S304; if the terminal is in the DRX inactive state when drx-HARQ-RTT-TimerUL times out, execute S305.
  • S304 Start drx-RetransmissionTimerUL when drx-HARQ-RTT-TimerUL times out, and monitor PDCCH for retransmission of the PUSCH during drx-RetransmissionTimerUL operation.
  • S305 Determine whether the time interval T between the time when drx-HARQ-RTT-TimerUL times out and the next DRX active is greater than the remaining scheduling time of the PUSCH.
  • time interval T is greater than the PUSCH remaining scheduling time, perform S304. If the time interval T is less than the PUSCH remaining scheduling time, perform S306.
  • S306 Turn on drx-RetransmissionTimerUL at the beginning of the next activation period, and monitor the PDCCH for retransmission of the PUSCH during the operation of drx-RetransmissionTimerUL.
  • the terminal can no longer wake up frequently to monitor PDCCH without affecting the service capacity, thereby saving the terminal's power consumption.
  • This application also provides an uplink transmission method, which can improve the reliability of uplink data transmission. This method is explained below.
  • Figure 12 is a schematic flow chart of an uplink transmission method provided by this application.
  • the method 400 may include S410 to S430.
  • S410 The network device determines whether the terminal meets the first condition or the second condition.
  • Step S410 is executed when or before the network device schedules uplink data.
  • the network device actually predicts whether the terminal satisfies the first condition or the second condition.
  • the uplink scheduling DCI here is the uplink authorization information in step S420, that is, the first uplink authorization information or the second uplink authorization information.
  • the second uplink grant information is only valid within the current semi-static resource period.
  • the network device in S410 may deviate from the actual result. For example, the network device schedules another downlink transmission after executing S410. If there is no such downlink transmission, the time when the first timer times out is in the inactive period. After the downlink transmission occurs, the time when the first timer times out happens to be in the downlink transmission period. Transmission within the corresponding drx-RetransmissionTimerDL period.
  • S420 The network device sends uplink authorization information to the terminal.
  • the terminal receives uplink authorization information from the network device.
  • the network device may first determine whether the terminal meets the first condition or the second condition, and then determine to send the uplink authorization information based on the determination result.
  • the uplink authorization information is used to schedule the uplink data, and the terminal can send the uplink data according to the uplink authorization information.
  • the uplink authorization information may include one or more of the following: MCS, transmission resources, or whether to repeatedly transmit the uplink data when transmitting the uplink data for the first time.
  • the transmission resources may be time-frequency resources.
  • the MCS is the first MCS. If the second condition is met, the MCS is the second MCS. That is to say, under different conditions, network equipment configures different MCS for terminals.
  • the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS, and/or the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS. In this way, when the second condition is met, the terminal can improve the reliability of the uplink transmission by performing uplink transmission according to the second MCS.
  • the transmission resource is the first transmission resource. If the second condition is met, the transmission resource is the second transmission resource.
  • the first transmission resources are less than the second transmission resources. That is to say, under different conditions, network equipment configures different transmission resource sizes for terminals. By configuring more transmission resources when the second condition is met, the reliability of uplink transmission can be improved.
  • the uplink data is not transmitted repeatedly when the uplink data is transmitted for the first time. If the second condition is met, the uplink data is repeatedly transmitted when the uplink data is transmitted for the first time. In this way, by repeatedly transmitting the uplink data when the uplink data is transmitted for the first time when the second condition is met, the reliability of the uplink transmission can be improved.
  • the uplink authorization information when the uplink authorization information includes the first MCS, the first transmission resource and/or the uplink data is not transmitted repeatedly when the uplink data is transmitted for the first time, the uplink authorization information can also be recorded as: first Upstream authorization information.
  • the uplink authorization information includes the second MCS, the second transmission resource and/or the uplink data is repeatedly transmitted when the uplink data is transmitted for the first time, the uplink authorization information may also be recorded as: second uplink authorization information.
  • the second uplink authorization information is DCI.
  • the second uplink authorization information may be scrambled using a new configured scheduling (CS) RNTI, such as CS-RNTI-New.
  • CS configured scheduling
  • Each domain of the second uplink authorization information can be configured according to the existing activated DCI Format.
  • the second uplink authorization information can be scrambled using cs-RNTI, and the field format of the DCI specific field is changed, so that the second uplink authorization information is only valid within the current semi-static resource period.
  • S430 The terminal sends uplink data to the network device according to the uplink authorization information and starts the first timer. Accordingly, the network device receives the uplink data and starts the first timer.
  • the terminal uses the MCS, transmission resources in the uplink authorization information, and/or the transmission mode (ie, repeated transmission/non-repeated transmission) when transmitting the uplink data for the first time to transmit the uplink data.
  • the transmission mode ie, repeated transmission/non-repeated transmission
  • the uplink transmission method determines whether the time when the first timer times out is within the remaining time from the start of the next activation period under the premise that the time when the first timer times out is in the inactive period.
  • the reliability of uplink transmission can be dynamically adjusted, so that the business can be better matched and the business capacity can be improved. For example, when the time when the first timer times out is not within the remaining scheduling time from the start of the next activation period, by configuring reasonable parameters to improve the reliability of uplink transmission, retransmissions can be avoided as much as possible, so that Ensure that XR data is transmitted correctly within the PDB and improve user experience.
  • method 400 can be combined with method 200, that is, after S430, S220 or S230 in method 200 can also be performed. In this way, the power saving effect achieved by method 200 can also be achieved.
  • This application also provides an uplink transmission method.
  • This method uses the following method: when the time interval between the moment when the terminal completes sending the uplink data and the start of the next activation period is less than the remaining scheduling time of the uplink data, in the next activation period Internally monitors the retransmission authorization for the uplink data, so that it is no longer necessary to start the first timer (such as drx-HARQ-RTT-TimerUL) and the second timer (such as drx-RetransmissionTimerUL), thus saving the terminal's power consumption.
  • the first timer such as drx-HARQ-RTT-TimerUL
  • the second timer such as drx-RetransmissionTimerUL
  • Figure 13 is a schematic flow chart of an uplink transmission method provided by this application.
  • the method 500 may include S510 and S520.
  • S510 The terminal sends uplink data to the network device.
  • the network device receives uplink data from the terminal.
  • the terminal sends uplink data according to the schedule of the network device, and accordingly, the network device attempts to receive the uplink data. If the network device receives the uplink data, it demodulates or decodes the data to determine whether the uplink data is successfully received.
  • the uplink data may be PUSCH, or in other words, the uplink data is carried or carried in PUSCH.
  • the next activation period will A retransmission authorization for the uplink data is sent to the terminal within the period.
  • the network device receives the uplink data according to the scheduling information for the uplink data. If the network device fails to successfully receive the uplink data at the time when the terminal completes sending the uplink data, it determines whether the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is less than the remaining schedule of the uplink data. time. If the time interval between the time when the terminal completes sending the uplink data and the start of the next activation period is less than the remaining scheduling time of the uplink data, the network device will no longer start the first timer and the second timer, but will A retransmission authorization for the uplink data is sent to the terminal within the period.
  • the terminal can determine whether the time interval between the time when it finishes sending the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data. If the time interval is less than the remaining scheduling time of the uplink data, the terminal no longer starts the first timer and the second timer, but monitors the retransmission authorization for the uplink data in the next activation period. If the terminal detects a retransmission authorization for the uplink data during the activation period, it retransmits the uplink data according to the retransmission authorization.
  • the time when the network device receives the uplink data is the same as the time when the terminal completes sending the uplink data.
  • the time when the terminal completes sending the uplink data may be the end time of the last symbol of the uplink data.
  • the time when the terminal finishes sending the uplink data can be the end time of symbol 9 or the start time of symbol 10.
  • the network device The time when the uplink data is received may be the end time of symbol 9 or the start time of symbol 10.
  • the next activation period may refer to a period that needs to monitor the PDCCH after the time when the terminal completes sending the uplink data and is closest in time to the time.
  • the next activation period may be the drx-RetransmissionTimerDL running period or the On Duration period that is closest in time to the moment when the terminal completes sending the uplink data.
  • the next activation period may also refer to: the On Duration period after the moment when the terminal completes sending the uplink data and is closest in time to this moment.
  • the moment when the next activation period starts may refer to the starting position of the first symbol of the next activation period.
  • the remaining scheduling time of the uplink data refers to the remaining scheduling time of the uplink data at the moment when the terminal completes sending the uplink data.
  • This uplink data has transmission delay requirements. If the uplink data has not been scheduled within the remaining scheduling time, the uplink data becomes invalid.
  • the PDB can be used to represent the transmission delay requirement of the uplink data. For example, assuming that the PDB is 30ms, then the uplink data needs to be scheduled within 30ms. If the uplink data has not been scheduled for more than 30ms, the uplink data will be invalid.
  • the terminal can obtain the PDB through the core network device (the network device is configured through Qos rules), and the terminal itself can sense that when the terminal completes sending the uplink data, after the uplink data reaches the cache (buffer) The waiting time t, so the remaining scheduling time can be calculated as PDB-t.
  • the network device can obtain the PDB through the core network device (configured through Qos profile).
  • the terminal reports the waiting delay t after the uplink data reaches the buffer through SR, BSR, or new MAC CE.
  • the remaining scheduling time can be calculated through PDB-t.
  • the terminal can report the remaining scheduling time of the uplink data to the network device.
  • the retransmitted uplink data may be exactly the same as the uplink data, or the retransmitted uplink data may have the same content as the uplink data, but the redundancy version (RV) version may not affect other contents decoded of the uplink data. Can be different.
  • RV redundancy version
  • the remaining scheduling time of the uplink data described in this method is equal to the sum of the remaining scheduling time described in the method 200 and the first timer duration.
  • the time interval between the time t1 when the terminal completes sending the uplink data and the start time t2 of the next activation period (ie, the drx-RetransmissionTimerDL period shown in the figure) is T, and the remaining scheduling time of the uplink data is T1, and T ⁇ T1. Then, even if the uplink data is retransmitted in the next activation period, if the transmission timing is set appropriately, the uplink data will not become invalid, that is, the uplink data can be delayed to retransmission in the next activation period.
  • the terminal since the terminal itself is in an inactive period at time t2, in order to save power consumption, the terminal may not retransmit the uplink data based on drx-HARQ-RTT-TimerUL and drx-RetransmissionTimerUL, but monitor the uplink data at time t2. retransmission authorization. If the terminal detects a retransmission authorization for the uplink data within the next activation period, it retransmits the uplink data based on the retransmission authorization.
  • the moment when the terminal finishes sending the uplink data and the next If the time interval between the start moments of each activation period is less than the remaining scheduling time of the uplink data, the retransmission authorization for the uplink data can be monitored in the next activation period. In this way, there is no need to start the first timer (for example, drx-HARQ-RTT-TimerUL) and the second timer (for example, drx-RetransmissionTimerUL), and there is no need to listen for the retransmission of the uplink data before the second timer expires. transfer authorization, thereby saving the power consumption of the terminal.
  • drx-HARQ-RTT-TimerUL for example, drx-RetransmissionTimerUL
  • the method may further include:
  • S530 If the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is greater than or equal to the remaining scheduling time of the uplink data, the terminal starts the first timing at the time when it completes sending the uplink data. timer, and starts the second timer when the first timer times out, and listens for retransmission authorization for the uplink data before the second timer times out or stops.
  • the network device will send the uplink data after the terminal has finished sending it.
  • start the first timer when the uplink data is generated start the second timer when the first timer times out, and send a retransmission authorization for the uplink data to the terminal before the second timer times out or stops.
  • the network device receives the uplink data according to the scheduling information for the uplink data. If the network device fails to receive the uplink data successfully at the time of receiving the uplink data, it determines whether the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data. If the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is greater than or equal to the remaining scheduling time of the uplink data, the network device starts the first timer at the time when the terminal completes sending the uplink data, The second timer is started when the first timer times out, and a retransmission authorization for the uplink data is sent during the running of the second timer.
  • the terminal can determine whether the time interval between the time when it finishes sending the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data. If the time interval is greater than or equal to the remaining scheduling time of the uplink data, the network device starts the first timer when the uplink data is sent, starts the second timer when the first timer times out, and starts the second timer when the uplink data is sent. During the running of the second timer, the retransmission authorization for the uplink data is monitored. If the terminal detects the retransmission authorization for the uplink data during the running of the second timer, it retransmits the uplink data according to the retransmission authorization.
  • the network device may start the first timer and/or the second timer, or may not start the first timer and/or the second timer.
  • the time interval between the time t1 when the terminal completes sending the uplink data and the start time t2 of the next activation period is T, and the remaining scheduling time of the uplink data is T1. And T>T1. Then, if the uplink data is not retransmitted within T1, the uplink data will be invalid. Therefore, drx-HARQ-RTT-TimerUL may be started at time t1, and drx-RetransmissionTimerUL may be started at time t3 when the first timer expires.
  • the terminal monitors the retransmission authorization for the uplink data, and once the terminal monitors the retransmission authorization for the uplink data, it stops the timing of drx-RetransmissionTimerUL. After the terminal monitors the retransmission authorization for the uplink data, it can According to the retransmission authorization, the uplink data is retransmitted.
  • the second timer is started at the moment when the first timer times out.
  • the timer can schedule retransmission of the uplink data in time to avoid failure of the uplink data due to untimely scheduling.
  • this application does not limit the timing for the terminal or network device to determine whether the time interval between the time when the terminal completes sending the uplink data and the start of the next activation period is less than the remaining scheduling time of the uplink data.
  • the terminal or network device can make a judgment when the terminal finishes sending the uplink data, or when the scheduling information of the uplink data is obtained.
  • the method may further include:
  • S501 The network device sends configuration information to the terminal.
  • the terminal receives configuration information from the network device. After receiving the configuration information, the terminal executes S520 or S530 after executing S510 according to the configuration information.
  • the configuration information indicates that when the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data, the terminal monitors the uplink data at the start time of the next activation period. until the retransmission authorization for the uplink data is detected or until the end of the next activation period.
  • the time interval between the moment when the terminal completes sending the uplink data and the start of the next activation period is greater than or equal to the remaining scheduling time of the uplink data
  • the first timer is started at the moment when the uplink data is sent, and
  • the second timer is started when the first timer times out, and the retransmission authorization for the uplink data is monitored before the second timer times out or is stopped.
  • the configuration information can indicate whether the triggering method is conditional triggering or direct triggering.
  • Conditional triggering refers to: at the moment when the uplink data is sent, it is judged whether the time interval between the moment when the terminal sends the uplink data and the start of the next activation period is less than the remaining scheduling time of the uplink data. If the terminal sends the uplink data The time interval between time and the start time of the next activation period is less than the remaining scheduling time of the uplink data, then the terminal monitors the retransmission authorization for the uplink data at the start time of the next activation period until it hears the retransmission authorization for the uplink data. Or until the end of the next activation period.
  • the terminal starts the first timer when the uplink data is sent, starts the second timer when the first timer times out, and monitors the retry of the uplink data before the second timer times out or stops. Pass authorization.
  • the timer can indirectly instruct the terminal to monitor the timing of retransmission authorization for the uplink data by directly indicating condition triggering.
  • the triggering method is direct triggering, it is not necessary to determine whether the time interval between the time when the terminal completes sending the uplink data and the start of the next activation period is less than the remaining scheduling time of the uplink data at the time when the uplink data is sent.
  • the first timer is started when the uplink data is sent, and the second timer is started at t2 when the first timer times out.
  • the configuration information may be carried through physical layer signaling (such as DCI) or higher layer signaling (such as MAC CE or RRC signaling).
  • physical layer signaling such as DCI
  • higher layer signaling such as MAC CE or RRC signaling
  • a field for example, the Retransmission-Trigger field
  • the Retransmission-Trigger field can be added to the RRC signaling, or 1 bit of information can be added to the DCI to indicate the triggering mode.
  • the configuration information may be jointly determined through physical layer signaling and high-layer signaling.
  • MAC CE or RRC can configure a trigger mode candidate set, and DCI can indicate conditional triggering in the trigger mode candidate set.
  • RRC configures a trigger mode candidate set, and the MAC CE can indicate condition triggering in the trigger mode candidate set.
  • RRC configures a set of trigger mode candidate sets, MAC CE indicates the trigger mode candidate set, and DCI can indicate condition triggering in the trigger mode candidate set.
  • the network device can flexibly configure the triggering method of starting the first timer and/or the second timer to the terminal according to actual needs, which can better adapt to the needs of different scenarios.
  • This application also provides an uplink transmission method, which can improve the reliability of uplink data transmission. This method is explained below.
  • Figure 16 is a schematic flow chart of an uplink transmission method provided by this application.
  • the method 600 may include S610 to S630.
  • Method 600 involves the same concepts as method 500, such as the time when the terminal completes sending uplink data, the next activation period, the start time of the next activation period, and the remaining scheduling time of the uplink data. You can refer to method 500. corresponding description.
  • S610 The network device determines whether the third condition is met when receiving the uplink data.
  • the third condition refers to: the time interval between the time when the terminal completes sending the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data.
  • S620 The network device sends uplink authorization information to the terminal.
  • the terminal receives uplink authorization information from the network device.
  • the network device may first determine whether the terminal meets the third condition, and then determine to send the uplink authorization information based on the determination result.
  • the uplink authorization information is used to schedule the uplink data, and the terminal can send the uplink data according to the uplink authorization information.
  • the uplink authorization information may include one or more of the following: MCS, transmission resources, or whether to repeatedly transmit the uplink data when transmitting the uplink data for the first time.
  • the transmission resources may be time-frequency resources.
  • the MCS is the first MCS. If the third condition is not met, the MCS is the second MCS. That is to say, under different conditions, network equipment configures different MCS for terminals.
  • the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS, and/or the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS. In this way, when the third condition is not satisfied, the terminal can improve the reliability of the uplink transmission by performing uplink transmission according to the second MCS.
  • the transmission resource when the third condition is met, the transmission resource is the first transmission resource. If the third condition is not met, the transmission resource is the second transmission resource. The first transmission resources are less than the second transmission resources. That is to say, under different conditions, network equipment configures different transmission resource sizes for terminals. By configuring more transmission resources when the third condition is not met, the reliability of uplink transmission can be improved.
  • the uplink data is not transmitted repeatedly when the uplink data is transmitted for the first time. If the third condition is not met, the uplink data is repeatedly transmitted when the uplink data is transmitted for the first time. In this way, by repeatedly transmitting the uplink data when the uplink data is transmitted for the first time when the third condition is not satisfied, the reliability of the uplink transmission can be improved.
  • the uplink authorization information when the uplink authorization information includes the first MCS, the first transmission resource and/or the uplink data is not transmitted repeatedly when the uplink data is transmitted for the first time, the uplink authorization information can also be recorded as: first superior line authorization information.
  • the uplink authorization information includes the second MCS, the second transmission resource and/or the uplink data is repeatedly transmitted when the uplink data is transmitted for the first time, the uplink authorization information may also be recorded as: second uplink authorization information.
  • the second uplink grant information is only valid within the current semi-static resource period.
  • the second uplink authorization information is DCI.
  • the second uplink grant information may be scrambled using a new RNTI, such as CS-RNTI-New.
  • Each domain of the second uplink authorization information can be configured according to the existing activated DCI Format.
  • the second uplink authorization information may be scrambled using cs-RNTI, and the field format of the DCI specific field may be changed.
  • S630 The terminal sends uplink data to the network device according to the uplink authorization information. Accordingly, the network device receives the uplink data.
  • the terminal uses the MCS, transmission resources in the uplink authorization information, and/or the transmission mode (ie, repeated transmission/non-repeated transmission) when transmitting the uplink data for the first time to transmit the uplink data.
  • the transmission mode ie, repeated transmission/non-repeated transmission
  • the network device can dynamically adjust the uplink transmission time by judging whether the time interval between this time and the start time of the next activation period is within the range of the remaining scheduling time when it receives the uplink data.
  • the reliability of transmission can better match services and improve service capacity. For example, when the time when the network device receives the uplink data is not within the remaining scheduling time from the start of the next activation period, by configuring reasonable parameters to improve the reliability of the uplink transmission, retransmissions can be avoided as much as possible, so that Ensure that XR data is transmitted correctly within the PDB and improve user experience.
  • method 600 can be combined with method 500, that is, after S630, S520 or S530 in method 500 can also be performed. In this way, the power saving effect achieved by method 500 can also be achieved.
  • embodiments of the present application also provide corresponding devices, and the devices include corresponding units or modules for executing the above embodiments.
  • the module may be software, hardware, or a combination of software and hardware.
  • FIG 17 is a schematic diagram of a communication device 700 provided by this application.
  • the device 700 may include: an interface module 701 and a processing module 702.
  • a storage module 703 may also be included.
  • one or more modules as shown in Figure 17 may be implemented by one or more processors, or by one or more processors and memories; or by one or more processors and a transceiver; or may be implemented by one or more processors, memories, and transceivers, which are not limited in the embodiments of the present application.
  • the processor, memory, and transceiver can be set separately or integrated.
  • the device 700 has the function of implementing the terminal described in the embodiments of this application.
  • the device 700 includes modules or units or means (means) corresponding to the terminal executing the terminal-related steps described in the embodiments of this application.
  • the functions or Units or means can be implemented by software, or by hardware, or by hardware executing corresponding software implementation, or by a combination of software and hardware. For details, reference may be made to the corresponding descriptions in the foregoing corresponding method embodiments.
  • the device has the function of implementing the network equipment described in the embodiments of this application.
  • the device includes modules or units or means (means) corresponding to the network equipment performing the steps involved in the network equipment described in the embodiments of this application.
  • the functions or units or means can be realized by software, or by hardware, or by hardware executing corresponding software, or by a combination of software and hardware. detailed Further reference may be made to the corresponding descriptions in the foregoing corresponding method embodiments.
  • each module in the device 700 in the embodiment of the present application can be used to perform operations performed by the terminal in the method 200.
  • the device 700 may include an interface module 701 and a processing module 702.
  • the interface module 701 is configured to send uplink data to the network device and start a first timer, where the duration of the first timer is the shortest duration before a retransmission authorization for the uplink data is expected to be received.
  • the processing module 702 is also configured to start the second timer at the moment when the first timer times out, and start the second timer at the time when the second condition is met. Monitor the retransmission authorization for the uplink data before the second timer times out or stops.
  • the second condition is: the time when the first timer times out is in the activation period, or the time when the first timer times out is in the activation period. An inactive period, and the time interval is greater than or equal to the remaining scheduling time of the uplink data.
  • the interface module 701 is also configured to receive configuration information from the network device; the processing module 702 is specifically configured to determine based on the configuration information that when the first condition is met, in The time t1 starts the second timer.
  • the interface module 701 is also configured to receive configuration information from the network device; the processing module 702 is specifically configured to determine based on the configuration information that when the second condition is met, in The second timer is started when the first timer times out.
  • each module in the apparatus 700 in the embodiment of the present application can be used to perform operations performed by the network device in the method 200.
  • the device 700 may include an interface module 701 and a processing module 702.
  • the interface module 701 is used to receive uplink data from the terminal and start a first timer.
  • the duration of the first timer is when the terminal expects to receive the uplink data.
  • the minimum amount of time before retransmission is authorized.
  • the processing module 702 is configured to start a second timer at time t1 when the first condition is met, and control the interface module 701 to send a message for the uplink data to the terminal before the second timer times out or stops.
  • the first condition is: the time when the first timer times out is in the inactive period, and the time interval is less than the remaining scheduling time of the uplink data; and, when the second condition is met, In this case, start the second timer when the first timer times out, and control the interface module 701 to send a retransmission of the uplink data to the terminal before the second timer times out or stops.
  • the second condition is: the time when the first timer times out is in the activation period; or, the time when the first timer times out is in the inactive period, and the time interval is greater than or equal to the uplink data remaining scheduling time.
  • the interface module 701 is also configured to: when the first condition is met, send first uplink authorization information to the terminal, where the first uplink authorization information is used to Scheduling The uplink data and the first uplink authorization information indicate a first modulation and coding strategy MCS; when the second condition is met, second uplink authorization information is sent to the terminal, and the second uplink authorization information is For scheduling the uplink data, the second uplink grant information indicates a second MCS, wherein the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS, and/or the third MCS The code rate corresponding to one MCS is greater than the code rate corresponding to the second MCS.
  • the interface module 701 is also configured to: when the first condition is met, send first uplink authorization information to the terminal, where the first uplink authorization information is used to Scheduling the uplink data, the first uplink authorization information indicating a first transmission resource; when the second condition is met, sending second uplink authorization information to the terminal, the second uplink authorization information is used to The uplink data is scheduled, and the second uplink grant information indicates second transmission resources, wherein the first transmission resources are less than the second transmission resources.
  • the interface module 701 is also configured to: send configuration information to the terminal, where the configuration information indicates that the terminal, if the first condition is met, at the time t1 starts the second timer, and if the second condition is met, the second timer is started at the moment when the first timer times out.
  • each module in the apparatus 700 in the embodiment of this application can be used to perform operations performed by the network device in the method 400.
  • the device 700 may include an interface module 701 and a processing module 702.
  • the interface module 701 is configured to: when the first condition is met, send first uplink authorization information to the terminal, the first uplink authorization information is used to schedule uplink data, and the first uplink authorization information indicates a first modulation and coding strategy MCS, the first condition is: the time when the first timer times out is in the inactive period, and the time interval is less than the remaining scheduling time of the uplink data, and the time interval is the time when the first timer times out and the time when the downlink data expires.
  • the uplink grant information indicates a second MCS, where the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS, and/or the code rate corresponding to the first MCS is greater than the second MCS.
  • the code rate corresponding to MCS, the second condition is: the moment when the first timer times out is in the activation period, or the moment when the first timer times out is in the inactive period, and the time interval is greater than or equal to The remaining scheduling time of the uplink data; receiving the uplink data from the terminal and starting the first timer.
  • the duration of the first timer is the time the terminal expects to receive a retransmission authorization for the uplink data. The previous minimum duration.
  • the first uplink authorization information also indicates a first transmission resource
  • the second uplink authorization information also indicates a second transmission resource, wherein the first transmission resource is less than The second transmission resource.
  • the processing module 702 is also configured to start the second timer when the first timer times out when the second condition is met, and control the interface module 701 to stop when the second timer times out or stops. forward to the terminal for the above Authorization for retransmission of row data.
  • the interface module 701 is also configured to: send configuration information to the terminal, where the configuration information indicates that the terminal, if the first condition is met, at the time t1 starts the second timer, and if the second condition is met, the second timer is started at the moment when the first timer times out.
  • each module in the device 700 in the embodiment of the present application can be used to perform operations performed by the terminal in the method 500.
  • the device 700 may include an interface module 701 and a processing module 702.
  • the interface module 701 is used to send uplink data to the network device;
  • the processing module 702 is used to provide the remaining scheduling of the uplink data when the time interval between the time when the interface module 701 completes sending the uplink data and the start time of the next activation period is less than the remaining schedule of the uplink data.
  • the retransmission authorization for the uplink data is monitored at the beginning of the next activation period until the retransmission authorization for the uplink data is detected or until the end of the next activation period.
  • the processing module 702 starts the first timer when the interface module 701 completes sending the uplink data, and starts the second timer when the first timer times out, and when the second timer times out or Before stopping, listen for a retransmission authorization for the uplink data, and the duration of the first timer is the shortest duration before the retransmission authorization for the uplink data is expected to be received.
  • the interface module 701 is also configured to receive configuration information from the network device; the processing module 702 is specifically configured to determine based on the configuration information that the time interval is less than the remaining scheduling time. In this case, the retransmission authorization for the uplink data is monitored at the beginning of the next activation period until the retransmission authorization for the uplink data is detected or until the end of the next activation period.
  • the interface module 701 is also configured to receive configuration information from the network device; the processing module 702 is specifically configured to determine, according to the configuration information, that the time interval is greater than or equal to the remaining schedule. In the case of time, the first timer is started when the uplink data is sent.
  • each module in the apparatus 700 in the embodiment of this application can be used to perform operations performed by the network device in the method 500.
  • the device 700 may include an interface module 701 and a processing module 702.
  • the interface module 701 is configured to: receive uplink data from the terminal; when the time interval between the time of receiving the uplink data and the start time of the next activation period is less than the remaining scheduling time of the uplink data, and all the uplink data is not successfully received.
  • a retransmission authorization for the uplink data is sent to the terminal before the end of the next activation period.
  • the processing module 702 is configured to: when the time interval between the time when the uplink data is received and the start time of the next activation period is greater than or equal to the remaining scheduling time of the uplink data, and the uplink data is not successfully received, The first timer is started when the uplink data is received, and the second timer is started when the first timer times out, and the control interface module 701 sends a message to the terminal before the second timer times out or stops. A retransmission authorization for the uplink data is sent, and the duration of the first timer is the shortest duration before the terminal expects to receive the retransmission authorization for the uplink data.
  • the interface module 701 is also configured to: when the time interval is less than the remaining scheduling time, send the first uplink authorization information to the terminal. Grant information is used to schedule the uplink data, and the first uplink grant information indicates a first modulation and coding strategy MCS; when the time interval is greater than or equal to the remaining scheduling time, send a second uplink data to the terminal. Grant information, the second uplink grant information is used to schedule the uplink data, the second uplink grant information indicates a second MCS, wherein the modulation order corresponding to the first MCS is greater than the modulation order corresponding to the second MCS. The modulation order, and/or the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS.
  • the interface module 701 is also configured to: when the time interval is less than the remaining scheduling time, send the first uplink authorization information to the terminal.
  • Authorization information is used to schedule the uplink data, and the first uplink authorization information indicates a first transmission resource; when the time interval is greater than or equal to the remaining scheduling time, send second uplink authorization information to the terminal , the second uplink grant information is used to schedule the uplink data, and the second uplink grant information indicates second transmission resources, wherein the first transmission resources are less than the second transmission resources.
  • the interface module 701 is also configured to: send configuration information to the terminal, where the configuration information indicates that the terminal, when the time interval is less than the remaining scheduling time, Monitor the retransmission authorization for the uplink data at the beginning of the next activation period until the retransmission authorization for the uplink data is heard or until the end of the next activation period, and when the time interval is greater than or If equal to the remaining scheduling time, the first timer is started at the moment when the uplink data is received.
  • each module in the apparatus 700 in the embodiment of the present application can be used to perform operations performed by the network device in the method 600.
  • the device 700 may include an interface module 701 and a processing module 702.
  • the interface module 701 is configured to: when the time interval between the time when the uplink data is received and the start time of the next activation period is less than the remaining scheduling time of the uplink data, send the first uplink authorization information to the terminal, and the first The uplink grant information is used to schedule the uplink data, and the first uplink grant information indicates a first modulation and coding strategy MCS; when the time interval is greater than or equal to the remaining scheduling time, send a second modulation and coding strategy to the terminal.
  • the second uplink grant information is used to schedule the uplink data
  • the second uplink grant information indicates a second MCS, wherein the modulation order corresponding to the first MCS is greater than that corresponding to the second MCS
  • the modulation order, and/or the code rate corresponding to the first MCS is greater than the code rate corresponding to the second MCS; receiving the uplink data from the terminal.
  • the first uplink authorization information also indicates a first transmission resource
  • the second uplink authorization information also indicates a second transmission resource, wherein the first transmission resource is less than The second transmission resource.
  • the interface module 701 is also configured to: when the time interval is less than the remaining scheduling time and the uplink data is not successfully received, in the next activation period Send a retransmission authorization for the uplink data to the terminal; when the time interval is greater than or equal to the remaining scheduling time and the uplink data is not successfully received, start at the moment when the uplink data is received. a first timer, start a second timer when the first timer expires, and send a retransmission authorization for the uplink data to the terminal before the second timer times out or stops, so The duration of the first timer is the shortest duration before the terminal expects to receive a retransmission authorization for the uplink data.
  • the interface module 701 is also used to: send Configuration information, the configuration information indicates that when the time interval is less than the remaining scheduling time, the terminal monitors the retransmission authorization for the uplink data at the beginning of the next activation period until it monitors the retransmission authorization for the uplink data.
  • FIG 18 is a schematic diagram of a communication device 800 provided by this application.
  • the device 800 may be a network device, a terminal, a chip, a chip system, or a processor that supports a network device to implement the above method, or a chip, a chip system, or a processor that supports a terminal to implement the above method. wait.
  • the device 800 can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.
  • the device 800 may include one or more processors 801, which may also be referred to as processing units, and may implement certain control functions.
  • the processor 801 may be a general-purpose processor or a special-purpose processor. For example, it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data.
  • the central processor can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, DU or CU, etc.), execute software programs, and process Software program data.
  • the processor 801 can also store instructions and/or data 803, and the instructions and/or data 803 can be executed by the processor, so that the device 800 executes the method described in the above embodiment. Methods.
  • the processor 801 may include a transceiver unit for implementing reception and transmission functions.
  • the transceiver unit may be a transceiver circuit, an interface, an interface circuit, or a transceiver circuit used to implement receiving and transmitting functions.
  • the receive and send functions can be separate or integrated.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing codes/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.
  • the device 800 may include a circuit, which may implement the sending or receiving or communication functions in the foregoing method embodiments.
  • the device 800 may include one or more memories 802, on which instructions 804 may be stored, and the instructions may be executed on the processor, so that the device 800 performs the steps described in the above method embodiments. method.
  • data may also be stored in the memory.
  • instructions and/or data may also be stored in the processor.
  • the processor and memory can be provided separately or integrated together. For example, the corresponding relationships described in the above method embodiments may be stored in the memory or in the processor.
  • the device 800 may also include a transceiver 805 and/or an antenna 806.
  • the processor 801 may be called a processing unit and controls the device 800 .
  • the transceiver 805 may be called a transceiver unit, a transceiver, a transceiver circuit, a transceiver, etc., and is used to implement transceiver functions.
  • the processor and transceiver described in this application can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits RFICs, mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board (PCB), electronic equipment, etc.
  • the processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide-semiconductor (NMOS), P-type metal Oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (Bipolar Junction Transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), Gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS N-type metal oxide-semiconductor
  • PMOS P-type metal Oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs Gallium
  • the device described in the above embodiments may be a network device or a terminal, but the scope of the device described in this application is not limited thereto, and the structure of the device may not be limited by FIG. 18 .
  • the device may be a stand-alone device or may be part of a larger device.
  • the device may be: (1) an independent integrated circuit IC, a chip, or a chip system or a subsystem; (2) a collection of one or more ICs.
  • the IC collection may also include Storage components for storing data and/or instructions; (3) ASICs, such as modems (MSM); (4) Modules that can be embedded in other devices; (5) Receivers, terminals, smart terminals, cellular phones, wireless devices , handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.; (6) Others, etc.
  • ASICs such as modems (MSM)
  • MSM modems
  • Modules that can be embedded in other devices
  • (6) Others etc.
  • FIG. 19 provides a schematic structural diagram of a terminal.
  • terminal 900 includes a processor, a memory, a control circuit, an antenna, and an input and output device.
  • the processor is mainly used to process communication protocols and communication data, control the entire terminal, execute software programs, and process data of software programs.
  • Memory is mainly used to store software programs and data.
  • Radio frequency circuits are mainly used for conversion of baseband signals and radio frequency signals and processing of radio frequency signals.
  • Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users.
  • the processor can read the software program in the storage unit, parse and execute the instructions of the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit processes the baseband signal to obtain the radio frequency signal and sends the radio frequency signal out in the form of electromagnetic waves through the antenna. .
  • the radio frequency circuit receives the radio frequency signal through the antenna.
  • the radio frequency signal is further converted into a baseband signal and the baseband signal is output to the processor.
  • the processor converts the baseband signal into data and processes the data. .
  • Figure 19 shows only one memory and processor.
  • the memory may also be called a storage medium or a storage device, which is not limited in this embodiment of the present invention.
  • the processor can include a baseband processor and a central processor.
  • the baseband processor is mainly used to process communication protocols and communication data.
  • the central processor is mainly used to control the entire terminal and execute software. Programs, which process data for software programs.
  • the processor in Figure 19 integrates the functions of the baseband processor and the central processor.
  • the baseband processor and the central processor can also be independent processors and are interconnected through technologies such as buses.
  • a terminal may include multiple baseband processors to adapt to different network standards, the terminal may include multiple central processors to enhance its processing capabilities, and various components of the terminal may be connected through various buses.
  • the baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing communication protocols and communication data can be built into the processor, or can be stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.
  • the antenna and the control circuit with the transceiver function can be regarded as the transceiver unit 911 of the terminal 900
  • the processor with the processing function can be regarded as the processing unit 912 of the terminal 900
  • the terminal 900 includes a transceiver unit 911 and a processing unit 912.
  • the transceiver unit may also be called a transceiver, a transceiver, a transceiver device, etc.
  • the device used to implement the receiving function in the transceiver unit 911 can be regarded as a receiving unit, and the device used to implement the transmitting function in the transceiver unit 911 can be regarded as a sending unit, that is, the transceiving unit 911 includes a receiving unit and sending unit.
  • the receiving unit may also be called a receiver, a receiver, a receiving circuit, etc.
  • the sending unit may be called a transmitter, a transmitter, a transmitting circuit, etc.
  • the above-mentioned receiving unit and sending unit may be one unit integrated together, or may be multiple independent units.
  • the above-mentioned receiving unit and sending unit may be located in one geographical location, or may be dispersed in multiple geographical locations.
  • Figure 20 is a schematic structural diagram of a network device 1000 provided by an embodiment of the present application.
  • the above-mentioned device 700 or device 800 may be configured in the network device 1000.
  • the device 700 or the device 800 itself may be the network device 1000.
  • the network device 1000 can perform the operations performed by the network device in the above method embodiment.
  • the network device 1000 may include one or more radio frequency units, such as a remote radio unit (RRU) 1100 and one or more baseband units (BBU) (also called digital unit, DU). )1200.
  • the RRU 1100 may be called a transceiver unit, a transceiver, a transceiver circuit, a transceiver, etc., and may include at least one antenna 1110 and a radio frequency unit 1120.
  • the RRU 1100 part is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals and baseband signals.
  • the BBU 1200 part is mainly used for baseband processing, controlling network equipment 1000, etc.
  • the RRU 1100 and the BBU 1200 can be physically set together or physically separated, that is, a distributed base station.
  • the BBU 1200 is the control center of the network device 1000, which can also be called a processing unit. It is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, etc.
  • the BBU (processing unit) 1200 can be used to control the network device 1000 to perform the operation process of the sending end or the receiving end in the above method embodiment.
  • the BBU 1200 can be composed of one or more single boards. Multiple single boards can jointly support a single access standard wireless access network (such as an LTE system or a 1G system), or can support different access networks respectively. standard wireless access network.
  • the BBU 1200 also includes memory 1210 and a processor 1220.
  • the memory 1210 is used to store necessary instructions and data.
  • the processor 1220 is used to control the network device 1000 to perform necessary actions, for example, to control the network device 1000 to perform the operation process of the sending end or the receiving end in the above method embodiment.
  • the memory 1210 and processor 1220 may serve one or more single boards. In other words, the memory and processor can be set independently on each board. It is also possible for multiple boards to share the same memory and processor. In addition, necessary circuits can also be installed on each board.
  • SoC system-on-chip
  • all or part of the functions of part 1200 and part 1100 can be implemented by SoC technology, for example, by a base station function chip Implementation, the base station function chip integrates processor, memory, antenna interface and other devices.
  • the program of the base station related functions is stored in the memory, and the processor executes the program to realize the related functions of the base station.
  • the base station function chip can also read the memory external to the chip to implement related functions of the base station.
  • each step in the method embodiment provided in this application can be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid duplication, This will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the computer program product includes: computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute various steps or processes executed by the terminal in any of the above method embodiments. .
  • the computer program product includes: computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to perform various steps performed by the network device in any of the above method embodiments or process.
  • This application also provides a computer-readable storage medium that stores program code.
  • the program code When the program code is run on a computer, it causes the computer to perform various steps performed by the terminal in any of the above method embodiments. or process.
  • This application also provides a computer-readable storage medium that stores program code.
  • the program code When the program code is run on a computer, it causes the computer to execute each of the steps performed by the network device in any of the above method embodiments. steps or processes.
  • This application also provides a communication system, which includes a terminal and a network device.
  • transceiver unit or transceiver performs the steps of receiving or sending in the method embodiment, and other steps except sending and receiving may be performed by the processing unit or processor.
  • a component may be, but is not limited to, a process, a processor, an object, an executable file, a thread of execution, a program and/or a computer running on a processor.
  • applications running on the computing device and the computing device may be components.
  • One or more components can reside in a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. Additionally, these components can execute from various computer-readable storage media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component, a local system, a distributed system, and/or a network, such as the Internet, which interacts with other systems via signals) Communicate through local and/or remote processes.
  • data packets eg, data from two components interacting with another component, a local system, a distributed system, and/or a network, such as the Internet, which interacts with other systems via signals
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions (programs). When the computer program instructions (program) are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium or may be retrieved from a computer-readable storage medium.
  • Reading a storage medium and transmitting it to another computer-readable storage medium may be transmitted from a website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.) to another website, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (SSD)), etc.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

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

Abstract

本申请提供了一种上行传输方法和通信装置，涉及通信领域。该方法中，终端向网络设备发送上行数据并启动第一定时器，并在第一定时器超时的时刻t2处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔T小于该上行数据的剩余调度时间的情况下，在时刻t1启动第二定时器，并在第二定时器超时或停止前监听针对该上行数据的重传授权。其中，第一定时器的时长为期望收到针对该上行数据的重传授权之前的最短时长，t1＝t2+T。该方案在上行数据可以被延迟到下一个激活时段重传的情况下，不再在本次传输该上行数据后启动第二定时器，而在下一个激活时段启动第二定时器，可以节省功耗。

Description

上行传输方法和通信装置
本申请要求于2022年08月10日提交国家知识产权局、申请号为202210964540.6、申请名称为“上行传输方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种上行传输方法和通信装置。
背景技术
扩展现实(extended reality，XR)是一种实时性强、数据容量要求较大的多媒体业务。XR包括虚拟现实(virtual reality，VR)、增强现实(augmented reality，AR)和云游戏(cloud gaming，CG)。随着XR设备(如VR眼镜、AR眼镜)的轻量化，在保证用户体验的基础上，需要更多地考虑功耗设备的功耗问题。
第五代移动通信技术(5th generation mobile networks，5G)新空口(new radio，NR)标准引入了非连续接收(discontinuous reception，DRX)技术用于省电(power saving)。DRX的基本机制是给终端配置DRX周期(DRX cycle)，其中在On Duration时段，终端正常监听物理下行控制信道(physical downlink control channel，PDCCH)，在其他时段，终端有机会进入休眠状态，不接收PDCCH以减少功耗。
DRX中定义了drx-HARQ-RTT-TimerUL和drx-Retransmisson-TimerUL这两个定时器，用于上行数据重传处理。具体地，终端传输物理上行共享信道(physical uplink shared channel，PUSCH)后会启动drx-HARQ-RTT-TimerUL定时器，该定时器超时后，会启动drx-Retransmisson-TimerUL定时器，终端需要在drx-Retransmisson-TimerUL定时器期间监听PDCCH。那么，如果在drx-Retransmisson-TimerUL定时器期间，终端本身处于休眠状态，则需要唤醒监听PDCCH，这将增加终端的功耗。
发明内容
本申请提供了一种上行传输方法和通信装置，能够节省或降低终端的功耗。
第一方面，提供了一种上行传输方法，该方法可以由终端执行，也可以由终端的部件(例如处理器、芯片、或芯片系统等)执行，还可以由能实现全部或部分终端功能的逻辑模块或软件实现。
该方法包括：向网络设备发送上行数据并启动第一定时器；在满足第一条件的情况下，在时刻t1启动第二定时器，并在第二定时器超时或停止前监听针对该上行数据的重传授权。其中，第一定时器的时长为期望收到针对该上行数据的重传授权之前的最短时长。t1＝t2+T，t2表示第一定时器超时的时刻，T表示第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔。第一条件为：第一定时器超时的时刻处于非激活时段，且该时间间隔小于该上行数据的剩余调度时间。
激活时段是指需要监听PDCCH的时段，非激活时段是指不需要监听PDCCH的时段。
示例性的，第一定时器可以在该上行数据的最后一个符号的结束时刻启动。
应理解，该上行数据的剩余调度时间是指在第一定时器超时的时刻该上行数据的剩余调度时间。
根据本申请提供的上行传输方法，在第一定时器(如，drx-HARQ-RTT-TimerUL)超时的时刻处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以不在第一定时器超时时启动第二定时器(如，drx-RetransmissionTimerUL)，而在下一个激活时段启动第二定时器。由于终端不需要在第一定时器超时时进入激活状态来监听针对该上行数据的重传授权，且下一个激活时段终端本来就需要监听PDCCH，在下一个激活时段开启第二定时器也不会带来额外功耗，因此本申请提供的方法能够节省功耗。
在一些可能的实现方式中，该方法还可以包括：在满足第二条件的情况下，在第一定时器超时的时刻启动第二定时器，并在第二定时器超时或停止前监听针对该上行数据的重传授权。其中，所述第二条件为：第一定时器超时的时刻处于激活时段，或者，第一定时器超时的时刻处于非激活时段，且该时间间隔大于或等于该上行数据的剩余调度时间。
基于该方案，在第一定时器超时的时刻处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于上行数据的剩余调度时间的情况下，或者，在第一定时器超时的时刻处于激活时段的情况下，通过在第一定时器超时的时刻启动第二定时器，可以及时对该上行数据进行重传调度，避免由于调度不及时导致该上行数据失效。
在一些可能的实现方式中，该方法还可以包括：接收来自网络设备的配置信息。进一步地，可以根据该配置信息确定在满足第一条件的情况下，在时刻t1启动所述第二定时器。
在一些可能的实现方式中，该方法还可以包括：接收来自网络设备的配置信息。进一步地，可以根据配置信息确定在满足所述第二条件的情况下，在第一定时器超时的时刻启动所述第二定时器。
在一个示例中，该配置信息可以通过物理层信令或者高层信令携带。比如，物理层信令可以是下行控制信息(downlink control information，DCI)。比如，高层信令可以是媒体接入控制控制单元(medium access control control element，MAC CE)或无线资源控制(radio resource control，RRC)信令。
在另一示例中，该配置信息可以通过物理层信令和高层信令联合确定。例如，MAC CE或RRC可以配置候选集合，DCI可以指示候选集合中的一个候选内容。
基于上述方案，网络设备可以根据实际需求灵活向终端配置第二定时器开启的触发方式，能更好地适应不同场景需求。
第二方面，提供了一种上行传输方法，该方法可以由网络执行，也可以由网络的部件(例如处理器、芯片、或芯片系统等)执行，还可以由能实现全部或部分网络功能的逻辑模块或软件实现。
该方法包括：接收来自终端的上行数据并启动第一定时器；在满足第一条件的情况下，在时刻t1启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上 行数据的重传授权。在满足第二条件的情况下，在第一定时器超时的时刻启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上行数据的重传授权。
其中，第一定时器的时长为终端期望收到针对该上行数据的重传授权之前的最短时长。t1＝t2+T，t2表示第一定时器超时的时刻，T表示第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔。
第一条件为：第一定时器超时的时刻处于非激活时段，且该时间间隔小于该上行数据的剩余调度时间。第二条件为：第一定时器超时的时刻处于激活时段；或者，第一定时器超时的时刻处于非激活时段，且该时间间隔大于或等于该上行数据的剩余调度时间。
激活时段是指需要监听PDCCH的时段，非激活时段是指不需要监听PDCCH的时段。
示例性的，第一定时器可以在该上行数据的最后一个符号的结束时刻启动。
应理解，该上行数据的剩余调度时间是指在第一定时器超时的时刻该上行数据的剩余调度时间。
根据本申请提供的上行传输方法，在第一定时器超时的时刻处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以不在第一定时器超时时启动第二定时器，而在下一个激活时段启动第二定时器。由于终端不需要在第一定时器超时时进入激活状态来监听针对该上行数据的重传授权，且下一个激活时段终端本来就需要监听PDCCH，在下一个激活时段开启第二定时器也不会带来额外功耗，因此本申请提供的方法能够节省功耗。另外，在第一定时器超时的时刻处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于上行数据的剩余调度时间的情况下，或者，在第一定时器超时的时刻处于激活时段的情况下，通过在第一定时器超时的时刻启动第二定时器，可以及时对该上行数据进行重传调度，避免由于调度不及时导致该上行数据失效。
在一些可能的实现方式中，在接收来自终端的上行数据之前，该方法还可以包括：在满足第一条件的情况下，向终端发送第一上行授权信息；在满足第二条件的情况下，向终端发送第二上行授权信息。其中，第一上行授权信息和第二上行授权信息均用于调度该上行数据。
在一个示例中，第一上行授权信息指示第一调制编码策略(modulation and coding scheme，MCS)，第二上行授权信息指示第二MCS。第一MCS对应的调制阶数大于第二MCS对应的调制阶数，和/或，第一MCS对应的码率大于第二MCS对应的码率。
在另一个示例中，第一上行授权信息指示第一传输资源，第二上行授权信息指示第二传输资源，第一传输资源少于第二传输资源。
在又一个示例中，第一上行授权信息指示该上行数据在首次传输时不重复传输，第二上行授权信息指示该上行数据在首次传输时重复传输。
基于该方案，通过在第一定时器超时的时刻处于非激活时段的前提下，判断第一定时器超时的时刻距离下一个激活时段的开始时刻是否在剩余调度时间的范围内，可以通过配置不同的授权信息，动态调整上行传输的可靠性，从而能够较好的匹配业务， 提升业务容量。比如，在第一定时器超时的时刻距离下一个激活时段的开始时刻不在剩余调度时间的范围内的情况下，通过配置合理的参数来提高上行传输的可靠性，可以尽量避免重传，从而可以保证XR的数据在失效前正确传输，提升用户体验。
在一些可能的实现方式中，该方法还可以包括：向终端发送配置信息。其中，该配置信息指示终端在满足第一条件的情况下，在时刻t1启动所述第二定时器，以及在满足第二条件的情况下，在第一定时器超时的时刻启动第二定时器。
基于上述方案，网络设备可以根据实际需求灵活向终端配置第二定时器开启的触发方式，能更好地适应不同场景需求。
第三方面，提供了一种上行传输方法，该方法可以由网络执行，也可以由网络的部件(例如处理器、芯片、或芯片系统等)执行，还可以由能实现全部或部分网络功能的逻辑模块或软件实现。
该方法包括：在满足第一条件的情况下，向终端发送第一上行授权信息；在满足第二条件的情况下，向终端发送第二上行授权信息；接收来自所述终端的上行数据并启动第一定时器。
其中，第一定时器的时长为终端期望收到针对该上行数据的重传授权之前的最短时长。第一上行授权信息和第二上行授权信息均用于调度上行数据。其中，第一上行授权信息指示第一MCS，第二上行授权信息指示第二MCS。第一MCS对应的调制阶数大于第二MCS对应的调制阶数，和/或，第一MCS对应的码率大于第二MCS对应的码率。
第一条件为：第一定时器超时的时刻处于非激活时段，且时间间隔小于第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔。第二条件为：第一定时器超时的时刻处于激活时段，或者，第一定时器超时的时刻处于非激活时段，且该时间间隔大于或等于该上行数据的剩余调度时间。
本申请提供的上行传输方法，通过在第一定时器超时的时刻处于非激活时段的前提下，判断第一定时器超时的时刻距离下一个激活时段的开始时刻是否在剩余调度时间的范围内，可以动态调整上行传输的可靠性，从而能够较好的匹配业务，提升业务容量。比如，在第一定时器超时的时刻距离下一个激活时段的开始时刻不在剩余调度时间的范围内的情况下，通过配置合理的参数来提高上行传输的可靠性，可以尽量避免重传，从而可以保证XR的数据在失效前正确传输，提升用户体验。
在一些可能的实现方式中，第一上行授权信息还指示第一传输资源，第二上行授权信息还指示第二传输资源，其中，第一传输资源少于第二传输资源。
基于该方案，通过在不同场景下配置不同大小的传输资源，可以动态调整上行传输的可靠性。
在一些可能的实现方式中，第一上行授权信息还指示该上行数据在首次传输时不重复传输，第二上行授权信息指示该上行数据在首次传输时重复传输。
基于该方案，通过在不同场景下配置是否需要重复传输，可以动态调整上行传输的可靠性。
在一些可能的实现方式中，该方法还可以包括：在满足第一条件的情况下，在时刻t1启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上行数据的重 传授权；在满足第二条件的情况下，在第一定时器超时的时刻启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上行数据的重传授权。其中，t1＝t2+T，t2表示第一定时器超时的时刻，T表示该时间间隔。
基于该方案，在第一定时器超时的时刻处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以不在第一定时器超时时启动第二定时器，而在下一个激活时段启动第二定时器。由于终端不需要在第一定时器超时时进入激活状态来监听针对该上行数据的重传授权，且下一个激活时段终端本来就需要监听PDCCH，在下一个激活时段开启第二定时器也不会带来额外功耗，因此本申请提供的方法能够节省功耗。
在一些可能的实现方式中，该方法还可以包括：向终端发送配置信息。其中，该配置信息指示终端在满足第一条件的情况下，在时刻t1启动所述第二定时器，以及在满足第二条件的情况下，在第一定时器超时的时刻启动第二定时器。
基于上述方案，网络设备可以根据实际需求灵活向终端配置第二定时器开启的触发方式，能更好地适应不同场景需求。
第四方面，提供了一种上行传输方法，该方法可以由终端执行，也可以由终端的部件(例如处理器、芯片、或芯片系统等)执行，还可以由能实现全部或部分终端功能的逻辑模块或软件实现。
该方法包括：向网络设备发送上行数据；在发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间的情况下，在该下一个激活时段开始时刻监听针对该上行数据的重传授权直至监听到针对该上行数据的重传授权或者直至该下一个激活时段结束。
激活时段是指需要监听PDCCH的时段，非激活时段是指不需要监听PDCCH的时段。
应理解，该上行数据的剩余调度时间是指在发送完该上行数据的时刻该上行数据的剩余调度时间。
示例性的，发送完该上行数据的时刻可以是该上行数据的最后一个符号的结束时刻。
根据本申请提供的上行传输方法，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以在该下一个激活时段内监听针对该上行数据的重传授权，从而不需要启动第一定时器(如，drx-HARQ-RTT-TimerUL)和第二定时器(如，drx-RetransmissionTimerUL)，也不需要在第二定时器超时前监听针对该上行数据的重传授权，从而能够节省终端的功耗。
在一些可能的实现方式中，该方法还可以包括：在发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于该上行数据的剩余调度时间的情况下，在发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器超时或停止前监听针对该上行数据的重传授权，第一定时器的时长为期望收到针对该上行数据的重传授权之前的最短时长。
基于该方案，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于上行数据的剩余调度时间的情况下，通过在第一定时器超时的时 刻启动第二定时器，可以及时对该上行数据进行重传调度，避免由于调度不及时导致该上行数据失效。
在一些可能的实现方式中，该方法还可以包括：接收来自网络设备的配置信息。进一步地，可以根据该配置信息确定在该时间间隔小于该剩余调度时间的情况下，在下一个激活时段开始时刻监听针对该上行数据的重传授权直至监听到针对该上行数据的重传授权或者直至下一个激活时段结束。
在一些可能的实现方式中，该方法还可以包括：接收来自网络设备的配置信息。进一步地，根据该配置信息确定在该时间间隔大于或等于该剩余调度时间的情况下，在发送完该上行数据的时刻启动第一定时器。
在一个示例中，该配置信息可以通过物理层信令或者高层信令携带。比如，物理层信令可以是DCI。比如，高层信令可以是MAC CE或RRC信令。
在另一示例中，该配置信息可以通过物理层信令和高层信令联合确定。例如，MAC CE或RRC可以配置候选集合，DCI可以指示候选集合中的一个候选内容。
基于该方案，网络设备可以根据实际需求灵活向终端配置第一定时器和/或第二定时器开启的触发方式，能更好地适应不同场景需求。
第五方面，提供了一种上行传输方法，该方法可以由网络执行，也可以由网络的部件(例如处理器、芯片、或芯片系统等)执行，还可以由能实现全部或部分网络功能的逻辑模块或软件实现。
该方法包括：接收来自终端的上行数据；在接收该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间，且未成功接收该上行数据的情况下，在该下一个激活时段结束前向该终端发送针对该上行数据的重传授权；在接收该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于该上行数据的剩余调度时间，且未成功接收该上行数据的情况下，在接收该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器超时或停止前向该终端发送针对该上行数据的重传授权，第一定时器的时长为终端期望收到针对该上行数据的重传授权之前的最短时长。
应理解，网络设备接收该上行数据的时刻与终端发送完该上行数据的时刻相同。
根据本申请提供的上行传输方法，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以在该下一个激活时段内监听针对该上行数据的重传授权，从而不需要启动第一定时器(如，drx-HARQ-RTT-TimerUL)和第二定时器(如，drx-RetransmissionTimerUL)，也不需要在第二定时器超时前监听针对该上行数据的重传授权，从而能够节省终端的功耗。此外，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于上行数据的剩余调度时间的情况下，通过在第一定时器超时的时刻启动第二定时器，可以及时对该上行数据进行重传调度，避免由于调度不及时导致该上行数据失效。
在一些可能的实现方式中，在接收来自终端的上行数据之前，该方法还可以包括：在该时间间隔小于该剩余调度时间的情况下，向该终端发送第一上行授权信息；在该时间间隔大于或等于该剩余调度时间的情况下，向终端发送第二上行授权信息。其中， 第一上行授权信息和第二上行授权信息均用于调度该上行数据。
在一个示例中，第一上行授权信息指示第一MCS，第二上行授权信息指示第二MCS。第一MCS对应的调制阶数大于第二MCS对应的调制阶数，和/或，第一MCS对应的码率大于第二MCS对应的码率。
在另一个示例中，第一上行授权信息指示第一传输资源，第二上行授权信息指示第二传输资源，第一传输资源少于第二传输资源。
在又一个示例中，第一上行授权信息指示该上行数据在首次传输时不重复传输，第二上行授权信息指示该上行数据在首次传输时重复传输。
基于该方案，网络设备通过在接收上行数据的时刻，判断该时刻与下一个激活时段开始时刻之间的时间间隔是否在剩余调度时间的范围内，可以动态调整上行传输的可靠性，从而能够较好的匹配业务，提升业务容量。比如，在网络设备接收上行数据的时刻距离下一个激活时段的开始时刻不在剩余调度时间的范围内的情况下，通过配置合理的参数来提高上行传输的可靠性，可以尽量避免重传，从而可以保证XR的数据在失效前正确传输，提升用户体验。
在一些可能的实现方式中，该方法还可以包括：向该终端发送配置信息。其中，该配置信息指示该终端在该时间间隔小于该剩余调度时间的情况下，在该下一个激活时段开始时刻监听针对该上行数据的重传授权直至监听到针对该上行数据的重传授权或者直至该下一个激活时段结束，以及，在该时间间隔大于或等于该剩余调度时间的情况下，在接收该上行数据的时刻启动第一定时器。
基于该方案，网络设备可以根据实际需求灵活向终端配置第一定时器和/或第二定时器开启的触发方式，能更好地适应不同场景需求。
第六方面，提供了一种上行传输方法，该方法可以由网络执行，也可以由网络的部件(例如处理器、芯片、或芯片系统等)执行，还可以由能实现全部或部分网络功能的逻辑模块或软件实现。
该方法包括：在接收上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间的情况下，向终端发送第一上行授权信息，在该时间间隔大于或等于该剩余调度时间的情况下，向终端发送第二上行授权信息；接收来自该终端的该上行数据。
其中，第一上行授权信息和第二上行授权信息均用于调度该上行数据。第一上行授权信息指示第一MCS，第二上行授权信息指示第二MCS。第一MCS对应的调制阶数大于第二MCS对应的调制阶数，和/或，第一MCS对应的码率大于第二MCS对应的码率。
应理解，网络设备接收上行数据的时刻与终端发送完该上行数据的时刻相同。
本申请提供的上行传输方法，网络设备通过在接收上行数据的时刻，判断该时刻与下一个激活时段开始时刻之间的时间间隔是否在剩余调度时间的范围内，可以动态调整上行传输的可靠性，从而能够较好的匹配业务，提升业务容量。比如，在网络设备接收上行数据的时刻距离下一个激活时段的开始时刻不在剩余调度时间的范围内的情况下，通过配置合理的参数来提高上行传输的可靠性，可以尽量避免重传，从而可以保证XR的数据在失效前正确传输，提升用户体验。
在一些可能的实现方式中，第一上行授权信息还指示第一传输资源，第二上行授权信息还指示第二传输资源，其中，第一传输资源少于第二传输资源。
基于该方案，通过在不同场景下配置不同大小的传输资源，可以动态调整上行传输的可靠性。
在一些可能的实现方式中，第一上行授权信息还指示该上行数据在首次传输时不重复传输，第二上行授权信息指示该上行数据在首次传输时重复传输。
基于该方案，通过在不同场景下配置是否需要重复传输，可以动态调整上行传输的可靠性。
在一些可能的实现方式中，该方法还可以包括：在该时间间隔小于该剩余调度时间，且未成功接收该上行数据的情况下，在该下一个激活时段内向该终端发送针对该上行数据的重传授权；在该时间间隔大于或等于该剩余调度时间，且未成功接收该上行数据的情况下，在接收该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器超时或停止前向该终端发送针对该上行数据的重传授权，第一定时器的时长为终端期望收到针对该上行数据的重传授权之前的最短时长。
基于该方案，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以在该下一个激活时段内监听针对该上行数据的重传授权，从而不需要启动第一定时器(如，drx-HARQ-RTT-TimerUL)和第二定时器(如，drx-RetransmissionTimerUL)，也不需要在第二定时器超时前监听针对该上行数据的重传授权，从而能够节省终端的功耗。此外，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于上行数据的剩余调度时间的情况下，通过在第一定时器超时的时刻启动第二定时器，可以及时对该上行数据进行重传调度，避免由于调度不及时导致该上行数据失效。
在一些可能的实现方式中，在该向该终端发送针对该上行数据的重传授权之前，该方法还可以包括：向该终端发送配置信息。其中，该配置信息指示该终端在该时间间隔小于该剩余调度时间的情况下，在该下一个激活时段开始时刻监听针对该上行数据的重传授权直至监听到针对该上行数据的重传授权或者直至该下一个激活时段结束，以及在该时间间隔大于或等于该剩余调度时间的情况下，在接收该上行数据的时刻启动第一定时器。
基于该方案，网络设备可以根据实际需求灵活向终端配置第一定时器和/或第二定时器开启的触发方式，能更好地适应不同场景需求。
第七方面，提供了一种通信装置，包括用于执行：第一方面或第一方面中任一种可能实现方式中的方法的模块或单元，或第四方面或第四方面中任一种可能实现方式中的方法的模块或单元。
第八方面，提供了一种通信装置，包括用于执行第二方面或第二方面中任一种可能实现方式中的方法的模块或单元、或第三方面或第三方面中任一种可能实现方式中的方法的模块或单元、或第五方面或第五方面中任一种可能实现方式中的方法的模块或单元、或第六方面或第六方面中任一种可能实现方式中的方法的模块或单元。
第九方面，提供了一种通信装置，包括处理器，处理器与存储器耦合，存储器用 于存储计算机程序或指令，处理器用于执行存储器存储的计算机程序或指令，以实现：第一方面或第一方面中任一种可能实现方式中的方法、或第四方面或第四方面中任一种可能实现方式中的方法。
在一种可能的实现方式中，该装置还包括与处理器耦合的存储器。
在一种可能的实现方式中，处理器为一个或多个，和/或，存储器为一个或多个。
在一种可能的实现方式中，存储器可以与处理器集成在一起，或者存储器与处理器分离设置。
在一种可能的实现方式中，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为终端。示例性的，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为终端的芯片。示例性的，该通信接口可以是输入/输出接口。
第十方面，提供了一种通信装置，包括处理器，处理器与存储器耦合，存储器用于存储计算机程序或指令，处理器用于执行存储器存储的计算机程序或指令，以实现：第二方面或第二方面中任一种可能实现方式中的方法、或第三方面或第三方面中任一种可能实现方式中的方法、或第五方面或第五方面中任一种可能实现方式中的方法、或第六方面或第六方面中任一种可能实现方式中的方法。
在一种可能的实现方式中，该装置还包括与处理器耦合的存储器。
在一种可能的实现方式中，处理器为一个或多个，和/或，存储器为一个或多个。
在一种可能的实现方式中，存储器可以与处理器集成在一起，或者存储器与处理器分离设置。
在一种可能的实现方式中，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为网络设备。示例性的，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为网络设备中的芯片。示例性的，该通信接口可以是输入/输出接口。
第十一方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。该处理电路用于通过该输入电路接收信号，并通过该输出电路发射信号，使得该处理器执行上述任一方面或任一方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请对处理器及各种电路的具体实现方式不做限定。
第十二方面，提供了一种通信系统，包括前述的终端和/或网络设备。
第十三方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当该计算机程序被运行时，使得计算机执行上述任一方面或任一方面中任一种可能实现方式中的方法。
第十四方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)，当计算机程序在计算机上运行时，使得计算机执行上述任一方面或任一方面中任一种可能实现方式中的方法。
第十五方面，提供了一种芯片，包括处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的通信装置执行上述任一方面或任一方面中任一种可能实现方式中的方法。
附图说明
图1是本申请实施例提供的一例通信系统的示意图；
图2是本申请实施例提供的一种XR视频帧到达示意图；
图3是本申请实施例提供的一种DRX周期示意图；
图4是本申请实施例提供的一种DRX周期示意图；
图5是本申请实施例提供的一种下行重传处理示意图；
图6是本申请实施例提供的一种上行重传处理示意图；
图7是本申请实施例提供的一种上行传输方法的示意性流程图；
图8是本申请实施例提供的一例传输数据的时序示意图；
图9是本申请实施例提供的另一例传输数据的时序示意图；
图10是本申请实施例提供的又一例传输数据的时序示意图；
图11是本申请实施例提供的一种上行传输方法的示意性流程图；
图12是本申请实施例提供的一种上行传输方法的示意性流程图；
图13是本申请实施例提供的一种上行传输方法的示意性流程图；
图14是本申请实施例提供的一例传输数据的时序示意图；
图15是本申请实施例提供的另一例传输数据的时序示意图；
图16是本申请实施例提供的一种上行传输方法的示意性流程图；
图17是本申请实施例提供的一种通信装置的示意性框图；
图18是本申请实施例提供的另一种通信装置的示意性框图；
图19是本申请实施例提供的一例终端的示意性结构图；
图20是本申请实施例提供的一例网络设备的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执 行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
应理解，本申请中，“在……情况下”、“如果……”、“当……时”、“若……”等类似的描述可以替换使用。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、第五代(5th Generation，5G)移动通信系统、新无线(New Radio，NR)以及未来可能出现的其他移动通信系统等。
本申请实施例中的终端可以指(user equipment，UE)、站点(station)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端等，本申请实施例对此并不限定。
本申请实施例中的网络设备可以是用于与终端通信的设备。例如，该网络设备可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、未来移动通信系统中的基站或WiFi系统中的接入节点(access point，AP)等。再如，该网络设备也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)或者分布式单元(distributed unit，DU)。又如，该网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、中继站、接入点、车载设备、可穿戴设备、未来演进的其他通信系统中的接入网设备等。本申请对网络设备所采用的具体技术和具体设备形态不做限定。
在本申请实施例中，终端或网络设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端或网络设备，或者，是终端或网络设备中能够调用程序并执行程序的功能模块。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于:磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable  programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
图1示出了适用于本申请的一种通信系统的示意性框图。如图1所示，该通信系统100可以包括至少一个终端，例如图1所示的终端110；该通信系统100还可以包括至少一个网络设备，例如图1所示的网络设备120。终端110与网络设备120之间可以传输信号，其中，网络设备120向终端110发送信号称为下行(downlink，DL)传输(或下行通信)，终端110向网络设备120发送信号称为上行(uplink，UL)传输(或上行通信)。本申请提供的技术方案可以应用于上行传输。
应理解，图1所示的通信系统中还可以包括更多的网络节点，例如更多的终端或网络设备，本申请实施例在图中不再一一示出。
对于XR传输业务和视频传输业务，其业务模型通常是根据帧率，周期性到达。例如，参见图2所示的XR视频帧到达示意图，一个帧率为60帧每秒(frame per second，FPS)的视频，理想情况下，每隔16.67毫秒到达一个画面帧。由于XR传输业务和视频传输业务的数据包的产生和到达并不是连续的。在终端侧，从延迟的角度看，每个时隙侦听网络设备的下行控制信令，对接收上行授权或者下行数据是有好处的，但同时也给终端带来了功耗上的代价。为了降低终端功耗，在没有数据传输的时候，可以通过停止接收PDCCH(此时会停止PDCCH盲检)来降低功耗，从而提升电池使用时间。5G新空口(new radio，NR)标准引入的非连续接收(discontinuous reception，DRX)技术可实现省电(power saving)功能。
DRX的基本机制是为终端配置DRX周期(DRX cycle)。参见图3所示的DRX周期，每个DRX周期由唤醒期(On Duration)和休眠期(Opportunity for DRX)组成。在On Duration时段，终端监听并接收PDCCH，在Opportunity for DRX时段，终端有机会进入休眠状态，不接收PDCCH以减少功耗。处于休眠状态的终端，只是不接收PDCCH，但是可以接收来自其它物理信道的数据，如物理下行共享信道(physical downlink shared channel，PDSCH)、确认信号(acknowledge，ACK)等。例如，在半持续调度(semi-persistent scheduling，SPS)中，处于休眠状态的终端可以接收周期性配置的下行子帧上发送的PDSCH。
DRX周期的选择需要考虑电池节约与延迟之间的平衡。从一个方面讲，长DRX周期有益于延长终端的电池使用时间。从另一个方面讲，当有新的数据传输时，一个更短的DRX周期有益于更快的响应。为了满足上述需求，每个终端可以配置两个DRX周期：短DRX周期(shortDRX-Cycle)和长DRX周期(longDRX-Cycle)。例如，如图4示出了短DRX周期和长DRX周期的一个示例。在任一时刻，终端只能使用短DRX周期和长DRX周期中的一种配置。
DRX中还配置了drx-RetransmissionTimerDL和drx-HARQ-RTT-TimerDL两个参数，用于下行数据重传处理，以及，drx-RetransmissionTimerUL和drx-HARQ-RTT-TimerUL两个参数，用于上行数据重传处理。每个下行进程都对应一个drx-RetransmissionTimerDL和一个drx-HARQ-RTT-TimerDL，每个上行进程都对应 一个drx-RetransmissionTimerUL和一个drx-HARQ-RTT-TimerUL。下面分别结合图5和图6对这几个定时器进行说明。
图5示出了一例下行重传处理示意图。参见图5，终端根据接收到的PDCCH接收PDSCH，如果终端未成功接收该PDSCH，则向网络设备发送针对该PDSCH的否定应答(negative acknowledgement，NACK)。并且，终端在发送NACK后，开启drx-HARQ-RTT-TimerDL。在drx-HARQ-RTT-TimerDL运行期间，网络设备不会对该PDSCH进行重传调度，针对该PDSCH的重传调度在drx-HARQ-RTT-TimerDL超时后才会进行。因此，在drx-HARQ-RTT-TimerDL运行期间，终端进入非激活状态，不监听PDCCH。当drx-HARQ-RTT-TimerDL超时时，终端开启drx-RetransmissionTimerDL，进入激活状态，开始监听网络侧对该PDSCH的重传授权。当终端监听到针对该PDSCH的重传授权，则停止drx-RetransmissionTimerDL的计时，并根据针对该PDSCH的重传授权，接收重传的PDSCH。
图6示出了一例上行重传处理示意图。参见图6，终端根据接收到的PDCCH发送PUSCH，无论网络设备是否成功接收该PUSCH，在发送完PUSCH之后，终端都会开启drx-HARQ-RTT-TimerUL。在drx-HARQ-RTT-TimerUL运行期间，网络设备不会对该PUSCH进行重传调度，针对该PUSCH的重传调度在drx-HARQ-RTT-TimerUL超时后才会进行。因此，在drx-HARQ-RTT-TimerUL运行期间，终端进入非激活状态，不监听PDCCH。当drx-HARQ-RTT-TimerUL超时时，终端开启drx-RetransmissionTimerUL，进入激活状态，开始监听网络侧对该PUSCH的重传授权。当终端监听到针对该PUSCH的重传授权，则停止drx-RetransmissionTimerUL的计时，并根据针对该PUSCH的重传授权，重传PUSCH。
XR业务主要包括VR、AR、CG。上行传输时，VR和CG需要上传姿态(pose)或控制(control)信息，通常姿态或控制信息是周期性上传，且周期一般为4ms。对于AR业务，除了需要上传姿态和控制信息，还需要上传视频帧，常见视频帧率为30FPS、60FPS、90FPS、120FPS等，对应的周期为33.33ms、16.67ms、11.11ms、8.33ms等。XR视频帧需要在给定时延内进行传输，超过给定的时延则会导致无法在终端侧、服务器侧渲染。上行AR传输的数据包时延预算一般为30ms，姿态或控制信息的数据包时延预算一般为10ms。
DRX按照下行的业务传输样式(traffic pattern)进行配置(例如，周期16.67ms)。上行姿态或控制的数据更加频繁(比如，周期为4ms)。如果每次传输PUSCH后终端都要在drx-HARQ-RTT-TimerUL超时时启动的drx-Retransmisson-TimerUL期间监听PDCCH，将会带来较大的功耗。
有鉴于此，本申请提供了一种上行传输方案，在上行数据可以被延迟到下一个激活时段重传的情况下，不再在本次传输该上行数据后启动drx-Retransmisson-TimerUL，而在下一个激活时段启动drx-Retransmisson-TimerUL。由于终端不需要启动drx-Retransmisson-TimerUL，因此不需要在drx-HARQ-RTT-TimerUL超时时进入激活状态来监听PDCCH，且下一个激活时段终端本来就需要监听PDCCH，在下一个激活时段开启drx-Retransmisson-TimerUL也不会带来额外功耗，因此本申请提供的方案能够节省功耗。
本申请中涉及的激活时段、非激活时段、第一定时器和第二定时器参见下述说明。
1、激活时段(DRX active time)：在该时段内，终端需要监听PDCCH。
例如，激活时段可以包括On Duration时段、drx-RetransmissionTimerDL运行时段、以及drx-Retransmisson-TimerUL运行时段。
2、非激活时段(DRX inactive time)：在该时段内，终端不需要监听PDCCH。
例如，非激活时段可以包括drx-HARQ-RTT-TimerDL运行时段、drx-HARQ-RTT-TimerUL运行时段、drx-InactivityTimer运行时段以及其他不需要监听PDCCH的时段。应理解，drx-InactivityTimer在本申请中未提及，但可参见现有技术。
3、第一定时器：可以是drx-HARQ-RTT-TimerUL，也可以是与drx-HARQ-RTT-TimerUL作用相同的定时器。
第一定时器的时长为期望收到针对该上行数据的重传授权之前的最短时长。也就是说，终端最早能够在第一定时器超时后收到针对该上行数据的重传授权，或者说，网络设备最早在第一定时器超时后发送针对该上行数据的重传授权。比如，第一定时器为drx-HARQ-RTT-TimerUL，则第一定时器的时长为drx-HARQ-RTT-TimerUL的时长。所述针对该上行数据的重传授权可以指调度该上行数据重传的PDCCH或DCI。
第一定时器运行期间的时段为非激活时段，即在第一定时器运行期间，终端不需要监听PDCCH，相应地，网络设备也不发送PDCCH。
4、第二定时器：可以是drx-Retransmisson-TimerUL，也可以是与drx-Retransmisson-TimerUL作用相同的定时器。
网络设备可以在第二定时器超时之前发送针对上行数据的重传调度，相应地，终端可以在第二定时器超时前监听针对上行数据的重传调度。终端一旦监听到针对上行数据的重传调度，第二定时器可以停止计时。
5、网络设备接收上行数据：网络设备接收上行数据是指网络设备在其向终端配置的发送该上行数据的资源上试图接收上行数据，但接收的结果可能是网络设备接收到了终端发送的上行数据，也可能是网络设备没有接收到终端发送的上行数据。另外，如果网络设备接收到了终端发送的上行数据，网络设备还需要对上行数据进行解调或解码，如果网络设备正确解调或解码该上行数据，则称网络设备正确接收到该上行数据。如果网络设备未正确解调或解码该上行数据，则称网络设备接收错误。如果网络设备没有接收到该上行数据或者虽然接收到了上行数据但接收错误，则网络设备将调度该上行数据的重传。
应理解，本文中描述的网络设备未成功接收上行数据包括网络设备没有接收到该上行数据和网络设备虽然接收到了上行数据但接收错误这两种情况。网络设备成功接收上行数据是指网络设备正确接收到该上行数据。
下面结合相应流程图，对本申请提供的方案进行详细说明。可以理解，本申请提供的示意性流程图中主要以网络设备和终端作为该交互示意的执行主体为例来示意该方法，但本申请并不限制交互示意的执行主体。例如，示意性流程图中的网络设备也可以是支持该网络设备实现该方法的芯片、芯片系统、或处理器，还可以是能实现全部或部分网络设备功能的逻辑模块或软件；示意性流程图中的终端也可以是支持该终端实现该方法的芯片、芯片系统、或处理器，还可以是能实现全部或部分终端功能的 逻辑模块或软件。
图7是本申请提供的一种上行传输方法的示意性流程图。该方法200可以包括S210和S220。
S210，终端向网络设备发送上行数据并启动第一定时器。相应地，网络设备接收上行数据并启动第一定时器。
具体地，终端根据网络设备的调度发送上行数据，并且可以在发送该上行数据后启动第一定时器。相应地，网络设备接收该上行数据。在一个示例中，若网络设备未成功接收该上行数据，则启动第一定时器。在另一个示例中，无论网络设备是否成功接收该上行数据，都启动第一定时器。
该上行数据可以是PUSCH，或者说，该上行数据承载或携带在PUSCH中。
示例性的，第一定时器可以在该上行数据的最后一个符号发送/接收后启动。比如，第一定时器为drx-HARQ-RTT-TimerUL，第一定时器的开启时机为现有技术中drx-HARQ-RTT-TimerUL的开启时机。
需要说明的是，重传的上行数据可以与该上行数据完全相同，或者重传的上行数据与该上行数据的内容相同，但冗余(redundancy version，RV)版本或不影响对该上行数据解码的其他内容可以不同。
S220，在满足第一条件的情况下，终端在时刻t1启动第二定时器，并在第二定时器超时或停止前监听针对该上行数据的重传授权。
相应地，在满足第一条件的情况下，网络设备在时刻t1启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上行数据的重传授权。
其中，第一条件为：第一定时器超时的时刻t2处于非激活时段，且时间间隔T小于该上行数据的剩余调度时间。该时间间隔T为第一定时器超时的时刻t2与下一个激活时段开始时刻t1之间的时间间隔，即T＝t1-t2，或t1＝t2+T。
也就是说，如果第一定时器超时的时刻t2处于非激活时段，且第一定时器超时的时刻t2与下一个激活时段开始时刻t1之间的时间间隔T小于该上行数据的剩余调度时间T，则终端可以在下一个激活时段开始时刻t1启动第二定时器，并在第二定时器超时或停止前监听针对该上行数据的重传授权。相应地，如果网络设备未成功接收终端在S210中发送的上行数据，则在时刻t1启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上行数据的重传授权。如果网络设备成功接收终端在S210中发送的上行数据，那么网络设备可以启动第二定时器，也可以不启动第二定时器，但无论是否启动第二定时器，网络设备都不需要调度终端对该上行数据的重传。
下一个激活时段可以是指：在第一定时器超时的时刻之后且在时间上距离第一定时器超时的时刻最近的需要监听PDCCH的时段。比如，下一个激活时段可以是第一定时器超时的时刻之后且在时间上距离第一定时器超时的时刻最近的drx-RetransmissionTimerDL运行时段。下一个激活时段还可以是指：在第一定时器超时的时刻之后且在时间上距离第一定时器超时的时刻最近的On Duration时段。
示例性的，下一个激活时段开始的时刻可以是指下一个激活时段的第一个符号的起始位置。
上行数据的剩余调度时间是指在第一定时器超时的时刻该上行数据的剩余调度时 间。该上行数据具有传输时延要求。若该上行数据在其剩余调度时间内还没有被调度，则该上行数据失效。在一个示例中，可以用分组时延预算(packet delay budget，PDB)表示该上行数据的传输时延要求。例如，假设PDB为30ms，那么，该上行数据需要在30ms内被调度，如果该上行数据超过30ms还没有被调度，则该上行数据失效。
本领域技术人员可以理解，对于终端侧，终端可以通过核心网设备获取PDB(网络设备通过Qos rules配置)，终端本身可以感知在第一定时器超时的时刻，上行数据到达缓存(比如，RLC缓存)后的等待时间t，因此可以计算出剩余调度时间为PDB-t。对于网络设备侧，一种方式中，网络设备可以通过核心网设备获取PDB(通过Qos profile配置)。终端通过调度请求(scheduling request，SR)、缓存状态报告(buffer status report，BSR)、或者新的媒体接入控制控制单元(medium access control，MAC)控制单元(control element，CE)等方式来上报上行数据到达buffer后已经等待的时延t，剩余调度时间则可以通过PDB-t来计算。另一种方式中，终端可以向网络设备上报上行数据的剩余调度时间。
在第二定时器超时或停止前监听针对该上行数据的重传授权是指：从第二定时器开启时监听针对该上行数据的重传授权。如果在第二定时器超时前监听到针对该上行数据的重传授权，则在监听到针对该上行数据的重传授权后，停止第二定时器的计时，如果在第二定时器超时时都未监听到针对该上行数据的重传授权，则在第二定时器超时时，停止该定时器的计时。
下面以第一定时器为drx-HARQ-RTT-TimerUL，第二定时器为drx-RetransmissionTimerUL为例，结合图8所示的一例传输数据的时序图，对S220进行说明。
参见图8，drx-HARQ-RTT-TimerUL超时时刻t2与下一个激活时段(即，On Duration时段)开始时刻t1之间的时间间隔为T，该上行数据的剩余调度时间为T1，且T＜T1。那么，即使在下一个激活时段重传该上行数据，如果传输时机设置合适，该上行数据也不会失效，即该上行数据可以被延迟到下一个激活时段重传。并且，由于终端在时刻t2本身处于非激活时段，因此，为节省功耗，终端可以不在时刻t2启动drx-RetransmissionTimerUL，而在时刻t1启动drx-RetransmissionTimerUL。在drx-RetransmissionTimerUL运行期间，终端监听针对该上行数据的重传授权，并且，终端一旦监听到针对该上行数据的重传授权，则停止drx-RetransmissionTimerUL的计时。终端监听到针对该上行数据的重传授权后，可以根据该重传授权，对该上行数据进行重传。
综上，根据本申请提供的上行传输方法，在第一定时器超时的时刻处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以不在第一定时器超时时启动第二定时器，而在下一个激活时段启动第二定时器。由于终端不需要在第一定时器超时时进入激活状态来监听针对该上行数据的重传授权，且下一个激活时段终端本来就需要监听PDCCH，在下一个激活时段开启第二定时器也不会带来额外功耗，因此本申请提供的方法能够节省功耗。
在一些实施例中，该方法200还可以包括：
S230，在满足第二条件的情况下，在第一定时器超时的时刻t2启动第二定时器，并在第二定时器超时或停止前监听针对该上行数据的重传授权。相应地，网络设备在第一定时器超时的时刻t2启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上行数据的重传授权。
其中，第二条件为：第一定时器超时的时刻t2处于激活时段，或者，第一定时器超时的时刻t2处于非激活时段，且时间间隔T大于(或者，大于或等于)该上行数据的剩余调度时间T2。应理解，不满足第一条件即为满足第二条件。
具体地，如果第一定时器超时的时刻t2处于非激活时段，且第一定时器超时的时刻t2与下一个激活时段开始时刻t1之间的时间间隔T大于(或者，大于或等于)该上行数据的剩余调度时间T，或者，如果时刻t2处于激活时段，则终端可以在时刻t2启动第二定时器，并在第二定时器超时或停止前监听针对该上行数据的重传授权。相应地，如果网络设备未成功接收终端在S210中发送的上行数据，则在时刻t2启动第二定时器，并在第二定时器超时或停止前向终端发送针对该上行数据的重传授权。如果网络设备成功接收终端在S210中发送的上行数据，那么网络设备可以启动也可以不启动第二定时器，但网络设备不需要调度终端对该上行数据的重传。
下面以第一定时器为drx-HARQ-RTT-TimerUL，第二定时器为drx-RetransmissionTimerUL为例，结合图9和图10所示的传输数据的时序图，对S230进行说明。
参见图9，终端在drx-HARQ-RTT-TimerUL超时时刻t2位于drx-RetransmissionTimerDL内。由于终端本身在时刻t2就处于激活时段，因此可以在时刻t2开启drx-RetransmissionTimerUL，并在drx-RetransmissionTimerUL监听针对该上行数据的重传授权，并且，终端一旦监听到针对该上行数据的重传授权，则停止drx-RetransmissionTimerUL的计时。终端监听到针对该上行数据的重传授权后，可以根据该重传授权，对该上行数据进行重传。
参见图10，drx-HARQ-RTT-TimerUL超时时刻t2与下一个激活时段开始时刻t1(即，drx-RetransmissionTimerDL开始时刻)之间的时间间隔为T，且该上行数据的剩余调度时间为T1，T＞T1。那么，如果不在T1内重传该上行数据，该上行数据将失效。因此，无论时刻t2是否处于激活时段，都可以在时刻t2启动drx-RetransmissionTimerUL。在drx-RetransmissionTimerUL运行期间，终端监听针对该上行数据的重传授权，并且，终端一旦监听到针对该上行数据的重传授权，则停止drx-RetransmissionTimerUL的计时。终端监听到针对该上行数据的重传授权后，可以根据该重传授权，对该上行数据进行重传。
基于该方案，在第一定时器超时的时刻处于非激活时段，且第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔大于(或者，大于或等于)上行数据的剩余调度时间的情况下，或者，在第一定时器超时的时刻处于激活时段的情况下，通过在第一定时器超时的时刻启动第二定时器，可以及时对该上行数据进行重传调度，避免由于调度不及时导致该上行数据失效。
需要说明的是，本申请对终端或网络设备判断是否满足第一条件和/或第二条件的时机不作限定。比如，终端或网络设备可以在第一定时器超时的时刻判断是否满足第 一条件，也可以在其他时刻判断是否满足第一条件，比如可以在第一定时器的起始时刻判断是否满足第一条件。
在一些实施例中，在S210之前，该方法还可以包括：
S201：网络设备向终端发送配置信息。
相应地，终端接收来自网络设备的配置信息。终端接收到该配置信息后，根据该配置信息，在执行S210后，执行S220或S230。
其中，该配置信息可以指示终端在满足第一条件的情况下，在时刻t1启动第二定时器，在满足第二条件的情况下，在第一定时器超时的时刻t2启动第二定时器。
比如，该配置信息可以指示触发方式为条件触发还是直接触发。条件触发是指：在第一定时器超时后判断终端是否满足第一条件，如果满足第一条件，则在时刻t1启动第二定时器，如果不满足第一条件，即满足第二条件，则在第一定时器超时的时刻t2启动第二定时器。这样，定时器可以通过直接指示条件触发来间接指示终端在满足第一条件的情况下，在时刻t1启动第二定时器，在满足第二条件的情况下，在第一定时器超时的时刻t2启动第二定时器。另外，如果触发方式为直接触发，不需要判断是否满足第一条件，直接在第一定时器超时的时刻t2启动第二定时器。
在一个示例中，该配置信息可以通过物理层信令(比如DCI)或者高层信令(比如MAC CE或RRC信令)携带。
比如，在配置授权(configured grant，CG)类型(Type)1模式下，可以在RRC信令中可以添加一个字段(例如，重传触发Retransmission-Trigger字段)。或者，在CG Type2模式下，可以在RRC信令中添加Retransmission-Trigger字段，也可以在DCI中增加1比特(bit)信息，用来指示触发方式。
在另一示例中，该配置信息可以通过物理层信令和高层信令联合确定。例如，MAC CE或RRC可以配置触发方式候选集合，DCI可以指示触发方式候选集合中的条件触发。或者，RRC配置触发方式候选集合，MAC CE可以指示触发方式候选集合中的条件触发。或者，RRC配置触发方式候选集合的集合，MAC CE指示触发方式候选集合，DCI可以指示触发方式候选集合中的条件触发。
基于上述方案，网络设备可以根据实际需求灵活向终端配置第二定时器开启的触发方式，能更好地适应不同场景需求。
下面结合图11描述本申请提供的方法200的一个具体示例。
图11是本申请提供的一种上行传输方法的示意性流程图。该方法300从终端的角度描述了终端在不同条件下所执行的不同操作。该方法300可以包括S301至S306的一个或多个步骤。
S301，在终端配置了DRX的情况下，在传输完PUSCH后的第一个符号启动drx-HARQ-RTT-TimerUL定时器。
S302，在drx-HARQ-RTT-TimerUL定时器超时时，判断drx-HARQ-RTT-TimerUL超时后直接触发还是条件触发drx-RetransmissionTimerUL的启动。
若直接触发drx-RetransmissionTimerUL的启动，则执行S304。若条件触发Retransmission-Timer-UL的启动，则执行S303。
应理解，S302为可选步骤。在方法300中，终端也可以不执行S302，而在S301 之后执行S303。
S303，确定drx-HARQ-RTT-TimerUL超时时是否处于激活时段。
比如，若配置drx-HARQ-RTT-TimerUL超时后条件触发drx-RetransmissionTimerUL的启动，则终端需要对其在drx-HARQ-RTT-TimerUL超时的时刻是否是DRX active状态做进一步的判断。若终端在drx-HARQ-RTT-TimerUL超时时是DRX active状态，则执行S304；若终端在drx-HARQ-RTT-TimerUL超时时是DRX inactive状态，则执行S305。
S304，在drx-HARQ-RTT-TimerUL超时时启动drx-RetransmissionTimerUL，并在drx-RetransmissionTimerUL运行期间监听针对该PUSCH重传的PDCCH。
应理解，如果在监听到针对该PUSCH重传的PDCCH，则停止drx-RetransmissionTimerUL的计时。如果drx-RetransmissionTimerUL超时且还没有监听到针对该PUSCH重传的PDCCH，则在下一个激活时间继续监听针对该PUSCH重传的PDCCH。
还应理解，终端在执行完S304之后不再执行下述S305和S306。
S305，判断drx-HARQ-RTT-TimerUL超时的时刻距离下一个DRX active的时间间隔T是否大于该PUSCH的剩余调度时间。
若时间间隔T大于该PUSCH剩余调度时间，则执行S304。若时间间隔T小于该PUSCH剩余调度时间，则执行S306。
S306，在下一个激活时段的开始时刻开启drx-RetransmissionTimerUL，并在drx-RetransmissionTimerUL运行期间监听针对该PUSCH重传的PDCCH。
通过上述条件触发drx-RetransmissionTimerUL启动的方案，在不影响业务容量的前提下，终端可以不再频繁地醒来监听PDCCH，从而能够节省终端的功耗。
本申请还提供了一种上行传输方法，该方法可以提高上行数据传输可靠性。下面对该方法进行说明。
图12是本申请提供的一种上行传输方法的示意性流程图。该方法400可以包括S410至S430。
S410，网络设备确定终端是否满足第一条件或第二条件。
关于第一条件和第二条件可以参见方法200中步骤S220和S230中的相应描述。
步骤S410在网络设备调度上行数据时或之前执行，S410中网络设备实际上是预测终端是否满足第一条件或第二条件。这两个条件中涉及的第二定时器的开始时刻、第一定时器超时的时刻(也是第二定时器开始的时刻)t2可以通过当前时刻T0，K2(上行调度DCI和所调度的PUSCH的间隔)，以及第一定时器的时长计算得出。即，t2＝T0+K2+drx-HARQ-RTT-TimerUL。这里的上行调度DCI为步骤S420中的上行授权信息，即第一上行授权信息或第二上行授权信息。在一个示例中，在半静态调度的场景下，第二上行授权信息仅在当前半静态资源周期内有效。
应理解，网络设备在S410中确定的结果可能和实际结果有偏差。比如，网络设备执行S410后又调度了一次下行传输，若无该下行传输，第一定时器超时的时刻处于非激活时段，在该下行传输发生后，第一定时器超时的时刻正好位于该下行传输对应的drx-RetransmissionTimerDL时段内。
S420，网络设备向终端发送上行授权信息。相应地，终端接收来自网络设备的上行授权信息。
具体地，网络设备可以首先判断终端是否满足第一条件或者第二条件，再根据判断结果判断发送上行授权信息。该上行授权信息用于调度该上行数据，终端可以根据该上行授权信息，发送所述上行数据。
其中，该上行授权信息可以包括下述中的一种或多种：MCS、传输资源、或者否在首次传输该上行数据时重复传输该上行数据。该传输资源可以是时频资源。
在一个示例中，在满足第一条件的情况下，该MCS为第一MCS。在满足第二条件的情况下，该MCS为第二MCS。也就是说，在不同条件下，网络设备为终端配置的MCS不同。
第一MCS对应的调制阶数大于第二MCS对应的调制阶数，和/或，第一MCS对应的码率大于第二MCS对应的码率。这样，在满足第二条件的情况下，终端通过根据第二MCS进行上行传输，可以提高上行传输的可靠性。
在另一个示例中，在满足第一条件的情况下，该传输资源为第一传输资源。在满足第二条件的情况下，该传输资源为第二传输资源。其中，第一传输资源少于第二传输资源。也就是说，在不同条件下，网络设备为终端配置的传输资源大小不同。通过在满足第二条件的情况下配置较多的传输资源，可以提高上行传输的可靠性。
在又一个示例中，在满足第一条件的情况下，在首次传输该上行数据时不重复传输该上行数据。在满足第二条件的情况下，在首次传输该上行数据时重复传输该上行数据。这样，通过在满足第二条件的情况下在首次传输该上行数据时重复传输该上行数据，可以提高上行传输的可靠性。
需要说明的是，在该上行授权信息包括第一MCS、第一传输资源和/或在首次传输该上行数据时不重复传输该上行数据的情况下，该上行授权信息也可以记作：第一上行授权信息。在该上行授权信息包括第二MCS、第二传输资源和/或在首次传输该上行数据时重复传输该上行数据的情况下，该上行授权信息也可以记作：第二上行授权信息。
在半静态调度场景下，第二上行授权信息为DCI。在一个示例中，第二上行授权信息可以采用一种新的配置调度(configured scheduling，CS)RNTI加扰，例如CS-RNTI-New。第二上行授权信息各个域可以按照现有的激活DCI Format进行配置。在另一个示例中，第二上行授权信息可以采用cs-RNTI加扰，并更改DCI特定域的字段格式，从而使得第二上行授权信息仅在当前半静态资源周期内有效。
S430，终端根据上行授权信息，向网络设备发送上行数据并启动第一定时器。相应地，网络设备接收上行数据并启动第一定时器。
即，终端采用该上行授权信息中的MCS、传输资源、和/或在首次传输该上行数据时的传输方式(即，重复传输/不重复传输)传输该上行数据。
应理解，关于终端发送上行数据并启动第一定时器的操作可以参考方法200中的S210。
综上，本申请提供的上行传输方法，通过在第一定时器超时的时刻处于非激活时段的前提下，判断第一定时器超时的时刻距离下一个激活时段的开始时刻是否在剩余 调度时间的范围内，可以动态调整上行传输的可靠性，从而能够较好的匹配业务，提升业务容量。比如，在第一定时器超时的时刻距离下一个激活时段的开始时刻不在剩余调度时间的范围内的情况下，通过配置合理的参数来提高上行传输的可靠性，可以尽量避免重传，从而可以保证XR的数据在PDB内正确传输，提升用户体验。
在一些实施例中，方法400可以和方法200结合，即在S430之后，还可以执行方法200中的S220或S230。这样，还可以达到方法200所能达到的节省功耗的效果。
本申请还提供了一种上行传输方法，该方法通过在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，在下一个激活时段内监听针对该上行数据的重传授权，这样可以不再需要启动第一定时器(如，drx-HARQ-RTT-TimerUL)和第二定时器(如，drx-RetransmissionTimerUL)，从而能够节省终端的功耗。
图13是本申请提供的一种上行传输方法的示意性流程图。该方法500可以包括S510和S520。
S510，终端向网络设备发送上行数据。相应地，网络设备接收来自终端的上行数据。
具体地，终端根据网络设备的调度发送上行数据，相应地，网络设备试图接收该上行数据。若网络设备接收到该上行数据，则对该数据进行解调或解码，以确定是否成功接收该上行数据。
应理解，该上行数据可以是PUSCH，或者说，该上行数据承载或携带在PUSCH中。
S520，终端在发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间的情况下，在下一个激活时段开始时刻监听针对该上行数据的重传授权直至监听到针对该上行数据的重传授权或者直至下一个激活时段结束。
相应地，网络设备在其接收该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间，且网络设备未成功接收该上行数据的情况下，在下一个激活时段内向终端发送针对该上行数据的重传授权。
具体地，网络设备根据对上行数据的调度信息，接收上行数据。网络设备在终端发送完该上行数据的时刻未成功接收该上行数据的情况下，确定终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔是否小于该上行数据的剩余调度时间。若终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间，则网络设备不再启动第一定时器和第二定时器，而在下一个激活时段内向终端发送针对该上行数据的重传授权。相应地，终端可以判断其发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔是否小于该上行数据的剩余调度时间。若该时间间隔小于该上行数据的剩余调度时间，则终端不再启动第一定时器和第二定时器，而在下一个激活时段内监听针对该上行数据的重传授权。若终端在该激活时段内监听到针对该上行数据的重传授权，则根据该重传授权重传该上行数据。
应理解，网络设备接收该上行数据的时刻与终端发送完该上行数据的时刻相同。 示例性的，终端发送完该上行数据的时刻可以是该上行数据的最后一个符号的结束时刻。例如，假设网络设备调度终端在某一时隙的符号2至符号9发送该上行数据，那么终端发送完该上行数据的时刻可以是符号9的结束时刻或者符号10的开始时刻，相应地，网络设备接收该上行数据的时刻可以是符号9的结束时刻或者符号10的开始时刻。
示例性的，下一个激活时段可以是指：在终端发送完该上行数据的时刻之后且在时间上距离该时刻最近的需要监听PDCCH的时段。比如，下一个激活时段可以是终端发送完该上行数据的时刻之后且在时间上距离该时刻最近的drx-RetransmissionTimerDL运行时段或On Duration时段。下一个激活时段还可以是指：在终端发送完该上行数据的时刻之后且在时间上距离该时刻最近的On Duration时段。
示例性的，下一个激活时段开始的时刻可以是指下一个激活时段的第一个符号的起始位置。
上行数据的剩余调度时间是指在终端发送完该上行数据的时刻该上行数据的剩余调度时间。该上行数据具有传输时延要求。若该上行数据在其剩余调度时间内还没有被调度，则该上行数据失效。在一个示例中，可以用PDB表示该上行数据的传输时延要求。例如，假设PDB为30ms，那么，该上行数据需要在30ms内被调度，如果该上行数据超过30ms还没有被调度，则该上行数据失效。
本领域技术人员可以理解，对于终端侧，终端可以通过核心网设备获取PDB(网络设备通过Qos rules配置)，终端本身可以感知在终端发送完该上行数据的时刻，上行数据到达缓存(buffer)后的等待时间t，因此可以计算出剩余调度时间为PDB-t。对于网络设备侧，一种方式中，网络设备可以通过核心网设备获取PDB(通过Qos profile配置)。终端通过SR、BSR、或者新的MAC CE等方式来上报上行数据到达buffer后已经等待的时延t，剩余调度时间则可以通过PDB-t来计算。另一种方式中，终端可以向网络设备上报上行数据的剩余调度时间。
另外，重传的上行数据可以与该上行数据完全相同，或者重传的上行数据与该上行数据的内容相同，但冗余(redundancy version，RV)版本或不影响对该上行数据解码的其他内容可以不同。
还应理解，该方法中描述的上行数据的剩余调度时间等于方法200中描述的剩余调度时间与第一定时器时长之和。
下面结合图14所示的一例传输数据的时序图，对S520进行举例说明。
参见图14，终端发送完该上行数据的时刻t1与下一个激活时段(即，图中所示的drx-RetransmissionTimerDL时段)开始时刻t2之间的时间间隔为T，该上行数据的剩余调度时间为T1，且T＜T1。那么，即使在下一个激活时段重传该上行数据，如果传输时机设置合适，该上行数据也不会失效，即该上行数据可以被延迟到下一个激活时段重传。并且，由于终端在时刻t2本身处于非激活时段，因此，为节省功耗，终端可以不基于drx-HARQ-RTT-TimerUL和drx-RetransmissionTimerUL进行上行数据重传，而在时刻t2监听针对该上行数据的重传授权。终端如果在该下一个激活时段内监听到针对该上行数据的重传授权，则根据该重传授权，对该上行数据进行重传。
综上，根据本申请提供的上行传输方法，在终端发送完该上行数据的时刻与下一 个激活时段开始时刻之间的时间间隔小于上行数据的剩余调度时间的情况下，可以在下一个激活时段内监听针对该上行数据的重传授权。这样不再需要启动第一定时器(如，drx-HARQ-RTT-TimerUL)和第二定时器(如，drx-RetransmissionTimerUL)，也不需要在第二定时器超时前监听针对该上行数据的重传授权，从而能够节省终端的功耗。
在一些实施例中，该方法还可以包括：
S530，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于该上行数据的剩余调度时间的情况下，终端在发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器超时或停止前监听针对所述上行数据的重传授权。
相应地，网络设备在接收该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于该上行数据的剩余调度时间，且未成功接收该上行数据的情况下，在终端发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器超时或停止前向终端发送针对该上行数据的重传授权。
具体地，网络设备根据对上行数据的调度信息，接收上行数据。网络设备在接收该上行数据的时刻未成功接收该上行数据的情况下，确定终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔是否小于该上行数据的剩余调度时间。若终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于该上行数据的剩余调度时间，则网络设备在终端发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器运行期间发送针对该上行数据的重传授权。相应地，终端可以判断其发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔是否小于该上行数据的剩余调度时间。若该时间间隔大于或等于该上行数据的剩余调度时间，则网络设备在发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器运行期间监听针对该上行数据的重传授权。若终端在第二定时器运行期间监听到针对该上行数据的重传授权，则根据该重传授权重传该上行数据。
需要说明的是，在网络设备接收该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于该上行数据的剩余调度时间的情况下，若网络设备成功接收该上行数据的情况下，网络设备可以启动第一定时器和/或第二定时器，也可以不启动第一定时器和/或第二定时器。
下面以第一定时器为drx-HARQ-RTT-TimerUL，第二定时器为drx-RetransmissionTimerUL为例，结合图15所示的传输数据的时序图，对S530进行说明。
参见图15，终端发送完该上行数据的时刻t1与下一个激活时段(即，图中所示的唤醒期)开始时刻t2之间的时间间隔为T，该上行数据的剩余调度时间为T1，且T＞T1。那么，如果不在T1内重传该上行数据，该上行数据将失效。因此，可以在时刻t1启动drx-HARQ-RTT-TimerUL，并在第一定时器超时时刻t3启动drx-RetransmissionTimerUL。在drx-RetransmissionTimerUL运行期间，终端监听针对该上行数据的重传授权，并且，终端一旦监听到针对该上行数据的重传授权，则停止drx-RetransmissionTimerUL的计时。终端监听到针对该上行数据的重传授权后，可以 根据该重传授权，对该上行数据进行重传。
基于该方案，在终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于上行数据的剩余调度时间的情况下，通过在第一定时器超时的时刻启动第二定时器，可以及时对该上行数据进行重传调度，避免由于调度不及时导致该上行数据失效。
需要说明的是，本申请对终端或网络设备判断终端发送完该上行数据的时刻与下一个激活时段开始时刻之间的时间间隔是否小于该上行数据的剩余调度时间的时机不作限定。比如，终端或网络设备可以在终端发送完该上行数据的时刻进行判断，也可以在获得该上行数据的调度信息时判断。
在一些实施例中，在S510之前，该方法还可以包括：
S501：网络设备向终端发送配置信息。
相应地，终端接收来自网络设备的配置信息。终端接收到该配置信息后，根据该配置信息，在执行S510后，执行S520或S530。
其中，该配置信息指示在终端发送完上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间的情况下，终端在下一个激活时段开始时刻监听针对该上行数据的重传授权直至监听到针对该上行数据的重传授权或者直至下一个激活时段结束。在终端发送完上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于该上行数据的剩余调度时间的情况下，在发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器超时或停止前监听针对所述上行数据的重传授权。
比如，该配置信息可以指示触发方式为条件触发还是直接触发。条件触发是指：在发送完该上行数据的时刻判断终端发送完上行数据的时刻与下一个激活时段开始时刻之间的时间间隔是否小于该上行数据的剩余调度时间，如果终端发送完上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间，则终端在下一个激活时段开始时刻监听针对该上行数据的重传授权直至监听到针对该上行数据的重传授权或者直至下一个激活时段结束。否则，终端在发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻启动第二定时器，以及在第二定时器超时或停止前监听针对所述上行数据的重传授权。这样，定时器可以通过直接指示条件触发来间接指示终端监听针对该上行数据的重传授权的时机。另外，如果触发方式为直接触发，不需要在发送完该上行数据的时刻判断终端发送完上行数据的时刻与下一个激活时段开始时刻之间的时间间隔是否小于该上行数据的剩余调度时间，直接在发送完该上行数据的时刻启动第一定时器，并在第一定时器超时的时刻t2启动第二定时器。
在一个示例中，该配置信息可以通过物理层信令(比如DCI)或者高层信令(比如MAC CE或RRC信令)携带。
比如，在配置授权(configured grant，CG)类型(Type)1模式下，可以在RRC信令中可以添加一个字段(例如，重传触发Retransmission-Trigger字段)。或者，在CG Type2模式下，可以在RRC信令中添加Retransmission-Trigger字段，也可以在DCI中增加1比特(bit)信息，用来指示触发方式。
在另一示例中，该配置信息可以通过物理层信令和高层信令联合确定。例如，MAC CE或RRC可以配置触发方式候选集合，DCI可以指示触发方式候选集合中的条件触发。或者，RRC配置触发方式候选集合，MAC CE可以指示触发方式候选集合中的条件触发。或者，RRC配置触发方式候选集合的集合，MAC CE指示触发方式候选集合，DCI可以指示触发方式候选集合中的条件触发。
基于上述方案，网络设备可以根据实际需求灵活向终端配置第一定时器和/或第二定时器开启的触发方式，能更好地适应不同场景需求。
本申请还提供了一种上行传输方法，该方法可以提高上行数据传输可靠性。下面对该方法进行说明。
图16是本申请提供的一种上行传输方法的示意性流程图。该方法600可以包括S610至S630。方法600中涉及的与方法500中相同的概念，比如，终端发送完上行数据的时刻、下一个激活时段、下一个激活时段开始时刻、以及该上行数据的剩余调度时间等，可以参考方法500中的相应描述。
S610，网络设备在接收该上行数据的时刻，确定是否满足第三条件。
第三条件是指：终端发送完上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于该上行数据的剩余调度时间。
S620，网络设备向终端发送上行授权信息。相应地，终端接收来自网络设备的上行授权信息。
具体地，网络设备可以首先判断终端是否满足第三条件，再根据判断结果判断发送上行授权信息。该上行授权信息用于调度该上行数据，终端可以根据该上行授权信息，发送所述上行数据。
其中，该上行授权信息可以包括下述中的一种或多种：MCS、传输资源、或者否在首次传输该上行数据时重复传输该上行数据。该传输资源可以是时频资源。在一个示例中，在满足第三条件的情况下，该MCS为第一MCS。在不满足第三条件的情况下，该MCS为第二MCS。也就是说，在不同条件下，网络设备为终端配置的MCS不同。
第一MCS对应的调制阶数大于第二MCS对应的调制阶数，和/或，第一MCS对应的码率大于第二MCS对应的码率。这样，在不满足第三条件的情况下，终端通过根据第二MCS进行上行传输，可以提高上行传输的可靠性。
在另一个示例中，在满足第三条件的情况下，该传输资源为第一传输资源。在不满足第三条件的情况下，该传输资源为第二传输资源。其中，第一传输资源少于第二传输资源。也就是说，在不同条件下，网络设备为终端配置的传输资源大小不同。通过在不满足第三条件的情况下配置较多的传输资源，可以提高上行传输的可靠性。
在又一个示例中，在满足第三条件的情况下，在首次传输该上行数据时不重复传输该上行数据。在不满足第三条件的情况下，在首次传输该上行数据时重复传输该上行数据。这样，通过在不满足第三条件的情况下在首次传输该上行数据时重复传输该上行数据，可以提高上行传输的可靠性。
需要说明的是，在该上行授权信息包括第一MCS、第一传输资源和/或在首次传输该上行数据时不重复传输该上行数据的情况下，该上行授权信息也可以记作：第一上 行授权信息。在该上行授权信息包括第二MCS、第二传输资源和/或在首次传输该上行数据时重复传输该上行数据的情况下，该上行授权信息也可以记作：第二上行授权信息。
在一个示例中，在半静态调度的场景下，第二上行授权信息仅在当前半静态资源周期内有效。
在半静态调度场景下，第二上行授权信息为DCI。在一个示例中，第二上行授权信息可以采用一种新的RNTI加扰，例如CS-RNTI-New。第二上行授权信息各个域可以按照现有的激活DCI Format进行配置。在另一个示例中，第二上行授权信息可以采用cs-RNTI加扰，并更改DCI特定域的字段格式。
S630，终端根据上行授权信息，向网络设备发送上行数据。相应地，网络设备接收上行数据。
即，终端采用该上行授权信息中的MCS、传输资源、和/或在首次传输该上行数据时的传输方式(即，重复传输/不重复传输)传输该上行数据。
综上，本申请提供的上行传输方法，网络设备通过在其接收上行数据的时刻，判断该时刻与下一个激活时段开始时刻之间的时间间隔是否在剩余调度时间的范围内，可以动态调整上行传输的可靠性，从而能够较好的匹配业务，提升业务容量。比如，在网络设备接收上行数据的时刻距离下一个激活时段的开始时刻不在剩余调度时间的范围内的情况下，通过配置合理的参数来提高上行传输的可靠性，可以尽量避免重传，从而可以保证XR的数据在PDB内正确传输，提升用户体验。
在一些实施例中，方法600可以和方法500结合，即在S630之后，还可以执行方法500中的S520或S530。这样，还可以达到方法500所能达到的节省功耗的效果。
对应于上述方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述实施例相应的单元或模块。所述模块可以是软件，也可以是硬件，或者是软件和硬件结合。
图17是本申请提供的一种通信装置700的示意图。该装置700可以包括：接口模块701和处理模块702。可选地，还可以包括存储模块703。
在一种可能的设计中，如图17中的一个或者多个模块可能由一个或者多个处理器来实现，或者由一个或者多个处理器和存储器来实现；或者由一个或多个处理器和收发器实现；或者由一个或者多个处理器、存储器和收发器实现，本申请实施例对此不作限定。所述处理器、存储器、收发器可以单独设置，也可以集成。
所述装置700具备实现本申请实施例描述的终端的功能，比如，所述装置700包括终端执行本申请实施例描述的终端涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段(means)可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现，还可以通过软件和硬件结合的方式实现。详细可进一步参考前述对应方法实施例中的相应描述。
或者，所述装置具备实现本申请实施例描述的网络设备的功能，比如，所述装置包括所述网络设备执行本申请实施例描述的网络设备涉及步骤所对应的模块或单元或手段(means)，所述功能或单元或手段(means)可以通过软件实现，或者通过硬件实现，也可以通过硬件执行相应的软件实现，还可以通过软件和硬件结合的方式实现。详细 可进一步参考前述对应方法实施例中的相应描述。
示例性的，本申请实施例中的装置700中各个模块可以用于执行方法200中终端所执行的操作。
在一种可能的实施方式中，装置700可包括接口模块701和处理模块702。接口模块701用于向网络设备发送上行数据并启动第一定时器，所述第一定时器的时长为期望收到针对所述上行数据的重传授权之前的最短时长。处理模块702用于在满足第一条件的情况下，在时刻t1启动第二定时器，并在所述第二定时器超时或停止前监听针对所述上行数据的重传授权，其中，t1＝t2+T，t2表示所述第一定时器超时的时刻，T表示时间间隔，所述时间间隔为所述第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔，所述第一条件为：所述第一定时器超时的时刻处于非激活时段，且所述时间间隔小于所述上行数据的剩余调度时间。
在上述装置700某些可能的实施方式中，处理模块702还用于在满足第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器，并在所述第二定时器超时或停止前监听针对所述上行数据的重传授权，所述第二条件为：所述第一定时器超时的时刻处于激活时段，或者，所述第一定时器超时的时刻处于非激活时段，且所述时间间隔大于或等于所述上行数据的剩余调度时间。
在上述装置700某些可能的实施方式中，接口模块701还用于接收来自网络设备的配置信息；处理模块702具体用于根据所述配置信息确定在满足所述第一条件的情况下，在所述时刻t1启动所述第二定时器。
在上述装置700某些可能的实施方式中，接口模块701还用于接收来自网络设备的配置信息；处理模块702具体用于根据所述配置信息确定在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器。
示例性的，本申请实施例中的装置700中各个模块可以用于执行方法200中网络设备所执行的操作。
在一种可能的实施方式中，装置700可包括接口模块701和处理模块702。
在上述装置700某些可能的实施方式中，接口模块701用于接收来自终端的上行数据并启动第一定时器，所述第一定时器的时长为所述终端期望收到针对所述上行数据的重传授权之前的最短时长。处理模块702用于在满足第一条件的情况下，在时刻t1启动第二定时器，并控制接口模块701在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，其中，t1＝t2+T，t2表示所述第一定时器超时的时刻，T表示时间间隔，所述时间间隔为所述第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔，所述第一条件为：所述第一定时器超时的时刻处于非激活时段，且所述时间间隔小于所述上行数据的剩余调度时间；以及，在满足第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器，并控制接口模块701在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，所述第二条件为：所述第一定时器超时的时刻处于激活时段；或者，所述第一定时器超时的时刻处于非激活时段，且所述时间间隔大于或等于所述上行数据的剩余调度时间。
在上述装置700某些可能的实施方式中，接口模块701还用于：在满足所述第一条件的情况下，向所述终端发送第一上行授权信息，所述第一上行授权信息用于调度 所述上行数据，所述第一上行授权信息指示第一调制编码策略MCS；在满足所述第二条件的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率。
在上述装置700某些可能的实施方式中，接口模块701还用于：在满足所述第一条件的情况下，向所述终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一传输资源；在满足所述第二条件的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二传输资源，其中，所述第一传输资源少于所述第二传输资源。
在上述装置700某些可能的实施方式中，接口模块701还用于：向所述终端发送配置信息，所述配置信息指示所述终端在满足所述第一条件的情况下，在所述时刻t1启动所述第二定时器，以及在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器。
示例性的，本申请实施例中的装置700中各个模块可以用于执行方法400中网络设备所执行的操作。
在一种可能的实施方式中，装置700可包括接口模块701和处理模块702。接口模块701用于：在满足第一条件的情况下，向终端发送第一上行授权信息，所述第一上行授权信息用于调度上行数据，所述第一上行授权信息指示第一调制编码策略MCS，所述第一条件为：第一定时器超时的时刻处于非激活时段，且时间间隔小于所述上行数据的剩余调度时间，所述时间间隔为所述第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔；在满足第二条件的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率，所述第二条件为：所述第一定时器超时的时刻处于激活时段，或者，所述第一定时器超时的时刻处于非激活时段，且所述时间间隔大于或等于所述上行数据的剩余调度时间；接收来自所述终端的上行数据并启动所述第一定时器，所述第一定时器的时长为所述终端期望收到针对所述上行数据的重传授权之前的最短时长。
在上述装置700某些可能的实施方式中，所述第一上行授权信息还指示第一传输资源，所述第二上行授权信息还指示第二传输资源，其中，所述第一传输资源少于所述第二传输资源。
在上述装置700某些可能的实施方式中，处理模块702用于在满足所述第一条件且未成功接收所述上行数据的情况下，在时刻t1启动第二定时器，并控制接口模块701在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，其中，t1＝t2+T，t2表示所述第一定时器超时的时刻，T表示所述时间间隔。处理模块702还用于在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器，并控制接口模块701在所述第二定时器超时或停止前向所述终端发送针对所述上 行数据的重传授权。
在上述装置700某些可能的实施方式中，接口模块701还用于：向所述终端发送配置信息，所述配置信息指示所述终端在满足所述第一条件的情况下，在所述时刻t1启动所述第二定时器，以及在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器。
示例性的，本申请实施例中的装置700中各个模块可以用于执行方法500中终端所执行的操作。
在一种可能的实施方式中，装置700可包括接口模块701和处理模块702。接口模块701用于向网络设备发送上行数据；处理模块702用于在接口模块701在发送完所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于所述上行数据的剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束。
在上述装置700某些可能的实施方式中，在接口模块701发送完所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于所述上行数据的剩余调度时间的情况下，处理模块702在接口模块701发送完所述上行数据的时刻，启动第一定时器，并在所述第一定时器超时的时刻启动第二定时器，以及在所述第二定时器超时或停止前监听针对所述上行数据的重传授权，所述第一定时器的时长为期望收到针对所述上行数据的重传授权之前的最短时长。
在上述装置700某些可能的实施方式中，接口模块701还用于接收来自网络设备的配置信息；处理模块702具体用于根据所述配置信息确定在所述时间间隔小于所述剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束。
在上述装置700某些可能的实施方式中，接口模块701还用于接收来自网络设备的配置信息；处理模块702具体用于根据所述配置信息确定在所述时间间隔大于或等于所述剩余调度时间的情况下，在发送完所述上行数据的时刻启动所述第一定时器。
示例性的，本申请实施例中的装置700中各个模块可以用于执行方法500中网络设备所执行的操作。
在一种可能的实施方式中，装置700可包括接口模块701和处理模块702。接口模块701用于：接收来自终端的上行数据；在所述接收所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于所述上行数据的剩余调度时间，且未成功接收所述上行数据的情况下，在所述下一个激活时段结束前向所述终端发送针对所述上行数据的重传授权。处理模块702用于在接收所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于所述上行数据的剩余调度时间，且未成功接收所述上行数据的情况下，在接收所述上行数据的时刻启动第一定时器，并在所述第一定时器超时的时刻启动第二定时器，以及控制接口模块701在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，所述第一定时器的时长为终端期望收到针对所述上行数据的重传授权之前的最短时长。
在上述装置700某些可能的实施方式中，接口模块701还用于：在所述时间间隔小于所述剩余调度时间的情况下，向所述终端发送第一上行授权信息，所述第一上行 授权信息用于调度所述上行数据，所述第一上行授权信息指示第一调制编码策略MCS；在所述时间间隔大于或等于所述剩余调度时间的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率。
在上述装置700某些可能的实施方式中，接口模块701还用于：在所述时间间隔小于所述剩余调度时间的情况下，向所述终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一传输资源；在所述时间间隔大于或等于所述剩余调度时间的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二传输资源，其中，所述第一传输资源少于所述第二传输资源。
在上述装置700某些可能的实施方式中，接口模块701还用于：向所述终端发送配置信息，所述配置信息指示所述终端在所述时间间隔小于所述剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束，以及，在所述时间间隔大于或等于所述剩余调度时间的情况下，在接收所述上行数据的时刻启动所述第一定时器。
示例性的，本申请实施例中的装置700中各个模块可以用于执行方法600中网络设备所执行的操作。
在一种可能的实施方式中，装置700可包括接口模块701和处理模块702。接口模块701用于：在接收上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于所述上行数据的剩余调度时间的情况下，向终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一调制编码策略MCS；在所述时间间隔大于或等于所述剩余调度时间的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率；接收来自所述终端的所述上行数据。
在上述装置700某些可能的实施方式中，所述第一上行授权信息还指示第一传输资源，所述第二上行授权信息还指示第二传输资源，其中，所述第一传输资源少于所述第二传输资源。
在上述装置700某些可能的实施方式中，接口模块701还用于：在所述时间间隔小于所述剩余调度时间，且未成功接收所述上行数据的情况下，在所述下一个激活时段内向所述终端发送针对所述上行数据的重传授权；在所述时间间隔大于或等于所述剩余调度时间，且未成功接收所述上行数据的情况下，在接收所述上行数据的时刻启动第一定时器，并在所述第一定时器超时的时刻启动第二定时器，以及在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，所述第一定时器的时长为终端期望收到针对所述上行数据的重传授权之前的最短时长。
在上述装置700某些可能的实施方式中，接口模块701还用于：向所述终端发送 配置信息，所述配置信息指示所述终端在所述时间间隔小于所述剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束，以及在所述时间间隔大于或等于所述剩余调度时间的情况下，在接收所述上行数据的时刻启动所述第一定时器。
图18是本申请提供的一种通信装置800的示意图。该装置800可以是网络设备，也可以是终端，也可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端实现上述方法的芯片、芯片系统、或处理器等。该装置800可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
该装置800可以包括一个或多个处理器801，所述处理器801也可以称为处理单元，可以实现一定的控制功能。所述处理器801可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端、终端芯片，DU或CU等)进行控制，执行软件程序，处理软件程序的数据。
在一种可选的设计中，处理器801也可以存有指令和/或数据803，所述指令和/或数据803可以被所述处理器运行，使得该装置800执行上述方法实施例中描述的方法。
在另一种可选的设计中，处理器801中可以包括用于实现接收和发送功能的收发单元。例如该收发单元可以是收发电路，或者是接口，或者是接口电路，或者是用于实现接收和发送功能的收发电路。接收和发送功能可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在又一种可能的设计中，装置800可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。
可选地，该装置800中可以包括一个或多个存储器802，其上可以存有指令804，所述指令可在所述处理器上被运行，使得该装置800执行上述方法实施例中描述的方法。可选地，所述存储器中还可以存储有数据。可选地，处理器中也可以存储指令和/或数据。所述处理器和存储器可以单独设置，也可以集成在一起。例如，上述方法实施例中所描述的对应关系可以存储在存储器中，或者存储在处理器中。
可选地，该装置800还可以包括收发器805和/或天线806。所述处理器801可以称为处理单元，对该装置800进行控制。所述收发器805可以称为收发单元、收发机、收发电路或者收发器等，用于实现收发功能。
本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor,CMOS)、N型金属氧化物半导体(metal oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(Bipolar Junction Transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、 砷化镓(GaAs)等。
以上实施例描述中的装置可以是网络设备或者终端，但本申请中描述的装置的范围并不限于此，而且装置的结构可以不受图18的限制。装置可以是独立的设备或者可以是较大设备的一部分。例如所述装置可以是：(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据和/或指令的存储部件；(3)ASIC，例如调制解调器(MSM)；(4)可嵌入在其他设备内的模块；(5)接收机、终端、智能终端、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；(6)其他等等。
图19提供了一种终端的结构示意图。为了便于说明，图19仅示出了终端的主要部件。如图19所示，终端900包括处理器、存储器、控制电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对整个终端进行控制，执行软件程序，处理软件程序的数据。存储器主要用于存储软件程序和数据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当终端开机后，处理器可以读取存储单元中的软件程序，解析并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行处理后得到射频信号并将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端时，射频电路通过天线接收到射频信号，该射频信号被进一步转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
为了便于说明，图19仅示出了一个存储器和处理器。在实际的终端中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本发明实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端进行控制，执行软件程序，处理软件程序的数据。图19中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端可以包括多个基带处理器以适应不同的网络制式，终端可以包括多个中央处理器以增强其处理能力，终端的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
在一个例子中，可以将具有收发功能的天线和控制电路视为终端900的收发单元911，将具有处理功能的处理器视为终端900的处理单元912。如图19所示，终端900包括收发单元911和处理单元912。收发单元也可以称为收发器、收发机、收发装置等。可选的，可以将收发单元911中用于实现接收功能的器件视为接收单元，将收发单元911中用于实现发送功能的器件视为发送单元，即收发单元911包括接收单元和 发送单元。示例性的，接收单元也可以称为接收机、接收器、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。可选的，上述接收单元和发送单元可以是集成在一起的一个单元，也可以是各自独立的多个单元。上述接收单元和发送单元可以在一个地理位置，也可以分散在多个地理位置。
图20为本申请实施例提供的一种网络设备1000的结构示意图。上述装置700或者装置800可以配置在该网络设备1000中。或者，该装置700或者装置800本身可以即为该网络设备1000。或者说，该网络设备1000可以执行上述方法实施例中网络设备执行的操作。
网络设备1000可以包括一个或多个射频单元，如远端射频单元(remote radio unit，RRU)1100和一个或多个基带单元(baseband unit，BBU)(也可称为数字单元，digital unit，DU)1200。该RRU 1100可以称为收发单元、收发机、收发电路、或者收发器等等，其可以包括至少一个天线1110和射频单元1120。该RRU 1100部分主要用于射频信号的收发以及射频信号与基带信号的转换。该BBU 1200部分主要用于进行基带处理，对网络设备1000进行控制等。该RRU 1100与BBU 1200可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
该BBU 1200为网络设备1000的控制中心，也可以称为处理单元，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如该BBU(处理单元)1200可以用于控制网络设备1000执行上述方法实施例中关于发送端或接收端的操作流程。
在一个示例中，该BBU 1200可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE系统，或1G系统)，也可以分别支持不同接入制式的无线接入网。该BBU 1200还包括存储器1210和处理器1220。该存储器1210用以存储必要的指令和数据。该处理器1220用于控制网络设备1000进行必要的动作，例如用于控制网络设备1000执行上述方法实施例中关于发送端或接收端的操作流程。该存储器1210和处理器1220可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
在一种可能的实施方式中，随着片上系统(system-on-chip，SoC)技术的发展，可以将1200部分和1100部分的全部或者部分功能由SoC技术实现，例如由一颗基站功能芯片实现，该基站功能芯片集成了处理器、存储器、天线接口等器件，基站相关功能的程序存储在存储器中，由处理器执行程序以实现基站的相关功能。可选的，该基站功能芯片也能够读取该芯片外部的存储器以实现基站的相关功能。
应理解，图20示例的网络设备的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的基站结构的可能。
应理解，在一种可能的设计中，本申请提供的方法实施例中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复， 这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行上述任一方法实施例中终端所执行的各个步骤或流程。
本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行上述任一方法实施例中网络设备所执行的各个步骤或流程。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述任一方法实施例中终端所执行的各个步骤或流程。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述任一方法实施例中网络设备所执行的各个步骤或流程。
本申请还提供一种通信系统，其包括终端和网络设备。
上述各个装置实施例和方法实施例完全对应，由相应的模块或单元执行相应的步 骤，例如收发单元或收发器执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元或处理器执行。
在本申请的实施例中，各术语及英文缩略语均为方便描述而给出的示例性举例，不应对本申请构成任何限定。本申请并不排除在已有或未来的协议中定义其它能够实现相同或相似功能的术语的可能。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读存储介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以基于前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，各功能单元的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令(程序)。在计算机上加载和执行所述计算机程序指令(程序)时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可 读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (34)

  1. 一种上行传输方法，其特征在于，所述方法包括：
    向网络设备发送上行数据并启动第一定时器，所述第一定时器的时长为期望收到针对所述上行数据的重传授权之前的最短时长；
    在满足第一条件的情况下，在时刻t1启动第二定时器，并在所述第二定时器超时或停止前监听针对所述上行数据的重传授权，其中，t1＝t2+T，t2表示所述第一定时器超时的时刻，T表示时间间隔，所述时间间隔为所述第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔，所述第一条件为：所述第一定时器超时的时刻处于非激活时段，且所述时间间隔小于所述上行数据的剩余调度时间。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    在满足第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器，并在所述第二定时器超时或停止前监听针对所述上行数据的重传授权，所述第二条件为：所述第一定时器超时的时刻处于激活时段，或者，所述第一定时器超时的时刻处于非激活时段，且所述时间间隔大于或等于所述上行数据的剩余调度时间。
  3. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的配置信息；
    其中，所述在满足第一条件的情况下，在时刻t1启动第二定时器，包括：
    根据所述配置信息确定在满足所述第一条件的情况下，在所述时刻t1启动所述第二定时器。
  4. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的配置信息；
    其中，所述在满足第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器，包括：
    根据所述配置信息确定在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器。
  5. 一种上行传输方法，其特征在于，所述方法包括：
    接收来自终端的上行数据并启动第一定时器，所述第一定时器的时长为所述终端期望收到针对所述上行数据的重传授权之前的最短时长；
    在满足第一条件的情况下，在时刻t1启动第二定时器，并在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，其中，t1＝t2+T，t2表示所述第一定时器超时的时刻，T表示时间间隔，所述时间间隔为所述第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔，所述第一条件为：所述第一定时器超时的时刻处于非激活时段，且所述时间间隔小于所述上行数据的剩余调度时间；
    在满足第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器，并在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，所述第二条件为：所述第一定时器超时的时刻处于激活时段；或者，所述第一定时器超时的时刻处于非激活时段，且所述时间间隔大于或等于所述上行数据的剩余调度时间。
  6. 如权利要求5所述的方法，其特征在于，在接收来自终端的上行数据之前，所述方法还包括：
    在满足所述第一条件的情况下，向所述终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一调制编码策略MCS；
    在满足所述第二条件的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率。
  7. 如权利要求5所述的方法，其特征在于，在接收来自终端的上行数据之前，所述方法还包括：
    在满足所述第一条件的情况下，向所述终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一传输资源；
    在满足所述第二条件的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二传输资源，其中，所述第一传输资源少于所述第二传输资源。
  8. 如权利要求5-7中任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端发送配置信息，所述配置信息指示所述终端在满足所述第一条件的情况下，在所述时刻t1启动所述第二定时器，以及在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器。
  9. 一种上行传输方法，其特征在于，所述方法包括：
    在满足第一条件的情况下，向终端发送第一上行授权信息，所述第一上行授权信息用于调度上行数据，所述第一上行授权信息指示第一调制编码策略MCS，所述第一条件为：第一定时器超时的时刻处于非激活时段，且时间间隔小于所述上行数据的剩余调度时间，所述时间间隔为所述第一定时器超时的时刻与下一个激活时段开始时刻之间的时间间隔；
    在满足第二条件的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率，所述第二条件为：所述第一定时器超时的时刻处于激活时段，或者，所述第一定时器超时的时刻处于非激活时段，且所述时间间隔大于或等于所述上行数据的剩余调度时间；
    接收来自所述终端的上行数据并启动所述第一定时器，所述第一定时器的时长为所述终端期望收到针对所述上行数据的重传授权之前的最短时长。
  10. 如权利要求9所述的方法，其特征在于，所述第一上行授权信息还指示第一传输资源，所述第二上行授权信息还指示第二传输资源，其中，所述第一传输资源少于所述第二传输资源。
  11. 如权利要求9或10所述的方法，其特征在于，所述方法还包括：
    在满足所述第一条件的情况下，在时刻t1启动第二定时器，并在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，其中，t1＝t2+T，t2表示所述第一定时器超时的时刻，T表示所述时间间隔；
    在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器，并在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权。
  12. 如权利要求11所述的方法，其特征在于，所述方法还包括：
    向所述终端发送配置信息，所述配置信息指示所述终端在满足所述第一条件的情况下，在所述时刻t1启动所述第二定时器，以及在满足所述第二条件的情况下，在所述第一定时器超时的时刻启动所述第二定时器。
  13. 一种上行传输方法，其特征在于，所述方法包括：
    向网络设备发送上行数据；
    在发送完所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于所述上行数据的剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束。
  14. 如权利要求13所述的方法，其特征在于，所述方法还包括：
    在发送完所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于所述上行数据的剩余调度时间的情况下，在发送完所述上行数据的时刻启动第一定时器，并在所述第一定时器超时的时刻启动第二定时器，以及在所述第二定时器超时或停止前监听针对所述上行数据的重传授权，所述第一定时器的时长为期望收到针对所述上行数据的重传授权之前的最短时长。
  15. 如权利要求13所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的配置信息；
    其中，所述在发送完所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于所述上行数据的剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束，包括：
    根据所述配置信息确定在所述时间间隔小于所述剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束。
  16. 如权利要求14所述的方法，其特征在于，所述方法还包括：
    接收来自网络设备的配置信息；
    其中，所述在发送完所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于所述上行数据的剩余调度时间的情况下，在发送完所述上行数据的时刻启动第一定时器，包括：
    根据所述配置信息确定在所述时间间隔大于或等于所述剩余调度时间的情况下，在发送完所述上行数据的时刻启动所述第一定时器。
  17. 一种上行传输方法，其特征在于，所述方法包括：
    接收来自终端的上行数据；
    在接收所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于所述上行数据的剩余调度时间，且未成功接收所述上行数据的情况下，在所述下一个激活时段结束前向所述终端发送针对所述上行数据的重传授权；
    在接收所述上行数据的时刻与下一个激活时段开始时刻之间的时间间隔大于或等于所述上行数据的剩余调度时间，且未成功接收所述上行数据的情况下，在接收所述上行数据的时刻启动第一定时器，并在所述第一定时器超时的时刻启动第二定时器，以及在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，所述第一定时器的时长为终端期望收到针对所述上行数据的重传授权之前的最短时长。
  18. 如权利要求17所述的方法，其特征在于，在接收来自终端的上行数据之前，所述方法还包括：
    在所述时间间隔小于所述剩余调度时间的情况下，向所述终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一调制编码策略MCS；
    在所述时间间隔大于或等于所述剩余调度时间的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率。
  19. 如权利要求17所述的方法，其特征在于，在接收来自终端的上行数据之前，所述方法还包括：
    在所述时间间隔小于所述剩余调度时间的情况下，向所述终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一传输资源；
    在所述时间间隔大于或等于所述剩余调度时间的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二传输资源，其中，所述第一传输资源少于所述第二传输资源。
  20. 如权利要求17-19中任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端发送配置信息，所述配置信息指示所述终端在所述时间间隔小于所述剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束，以及，在所述时间间隔大于或等于所述剩余调度时间的情况下，在接收所述上行数据的时刻启动所述第一定时器。
  21. 一种上行传输方法，其特征在于，所述方法包括：
    在接收上行数据的时刻与下一个激活时段开始时刻之间的时间间隔小于所述上行数据的剩余调度时间的情况下，向终端发送第一上行授权信息，所述第一上行授权信息用于调度所述上行数据，所述第一上行授权信息指示第一调制编码策略MCS；
    在所述时间间隔大于或等于所述剩余调度时间的情况下，向所述终端发送第二上行授权信息，所述第二上行授权信息用于调度所述上行数据，所述第二上行授权信息指示第二MCS，其中，所述第一MCS对应的调制阶数大于所述第二MCS对应的调制阶数，和/或，所述第一MCS对应的码率大于所述第二MCS对应的码率；
    接收来自所述终端的所述上行数据。
  22. 如权利要求21所述的方法，其特征在于，所述第一上行授权信息还指示第一传输资源，所述第二上行授权信息还指示第二传输资源，其中，所述第一传输资源少 于所述第二传输资源。
  23. 如权利要求21或22所述的方法，其特征在于，所述方法还包括：
    在所述时间间隔小于所述剩余调度时间，且未成功接收所述上行数据的情况下，在所述下一个激活时段内向所述终端发送针对所述上行数据的重传授权；
    在所述时间间隔大于或等于所述剩余调度时间，且未成功接收所述上行数据的情况下，在接收所述上行数据的时刻启动第一定时器，并在所述第一定时器超时的时刻启动第二定时器，以及在所述第二定时器超时或停止前向所述终端发送针对所述上行数据的重传授权，所述第一定时器的时长为终端期望收到针对所述上行数据的重传授权之前的最短时长。
  24. 如权利要求23所述的方法，其特征在于，在所述向所述终端发送针对所述上行数据的重传授权之前，所述方法还包括：
    向所述终端发送配置信息，所述配置信息指示所述终端在所述时间间隔小于所述剩余调度时间的情况下，在所述下一个激活时段开始时刻监听针对所述上行数据的重传授权直至监听到针对所述上行数据的重传授权或者直至所述下一个激活时段结束，以及在所述时间间隔大于或等于所述剩余调度时间的情况下，在接收所述上行数据的时刻启动所述第一定时器。
  25. 一种通信装置，其特征在于，所述装置用于执行如权利要求1-4中任一项或13-16中任一项所述的方法。
  26. 一种通信装置，其特征在于，所述装置用于执行如权利要求5-8中任一项、9-12中任一项、或者17-20中任一项所述的方法。
  27. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求1-4中任一项或13-16中任一项所述的方法。
  28. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求5-8中任一项、9-12中任一项、或者17-20中任一项所述的方法。
  29. 一种存储介质，其上存储有计算机程序或指令，其特征在于，所述计算机程序或指令被执行时使得计算机执行如权利要求1-4中任一项或13-16中任一项所述的方法。
  30. 一种存储介质，其上存储有计算机程序或指令，其特征在于，所述计算机程序或指令被执行时使得计算机执行如权利要求5-8中任一项、9-12中任一项、或者17-20中任一项所述的方法。
  31. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得所述计算机执行如权利要求1-4中任一项或13-16中任一项所述的方法。
  32. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得所述计算机执行如权利要求5-8中任一项、9-12中任一项、或者17-20中任一项所述的方法。
  33. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的通信设备执行如权利要求1-4中任一项或13-16中任一 项所述的方法。
  34. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的通信装置执行如权利要求5-8中任一项、9-12中任一项、或者17-20中任一项所述的方法。
PCT/CN2023/095210 2022-08-10 2023-05-19 上行传输方法和通信装置 WO2024032077A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210964540.6A CN117641527A (zh) 2022-08-10 2022-08-10 上行传输方法和通信装置
CN202210964540.6 2022-08-10

Publications (1)

Publication Number Publication Date
WO2024032077A1 true WO2024032077A1 (zh) 2024-02-15

Family

ID=89850613

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/095210 WO2024032077A1 (zh) 2022-08-10 2023-05-19 上行传输方法和通信装置

Country Status (2)

Country Link
CN (1) CN117641527A (zh)
WO (1) WO2024032077A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020107479A1 (zh) * 2018-11-30 2020-06-04 Oppo广东移动通信有限公司 一种传输数据的方法、终端设备和网络设备
US20210014028A1 (en) * 2018-04-04 2021-01-14 Huawei Technologies Co., Ltd. Discontinuous reception communication method and communications apparatus, communications device, and communications system
WO2021022494A1 (zh) * 2019-08-06 2021-02-11 Oppo广东移动通信有限公司 通信方法、装置及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210014028A1 (en) * 2018-04-04 2021-01-14 Huawei Technologies Co., Ltd. Discontinuous reception communication method and communications apparatus, communications device, and communications system
WO2020107479A1 (zh) * 2018-11-30 2020-06-04 Oppo广东移动通信有限公司 一种传输数据的方法、终端设备和网络设备
WO2021022494A1 (zh) * 2019-08-06 2021-02-11 Oppo广东移动通信有限公司 通信方法、装置及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
FUJITSU: "Remaining details on HARQ RTT and Retransmission Timer for SL DRX", 3GPP TSG RAN WG2 MEETING #115 ELECTRONIC R2-2107653, 6 August 2021 (2021-08-06), XP052034301 *

Also Published As

Publication number Publication date
CN117641527A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
WO2019192342A1 (zh) 非连续接收的通信方法、装置、通信设备和通信系统
CN109952789A (zh) 一种省电信号模式的使用方法、装置及终端
WO2020156378A1 (zh) 接收参考信号的方法、发送参考信号的方法和装置
WO2021180098A1 (zh) 无线通信方法和通信装置
WO2021056136A1 (zh) 监听wus的方法、发送信息的方法及设备
WO2017041276A1 (zh) 一种数据传输方法、终端及ran设备
WO2020063896A1 (zh) 信号处理的方法和装置
WO2021170136A1 (zh) 一种通信方法及装置
WO2020063782A1 (zh) 一种通信方法及装置
WO2022067549A1 (zh) 无线通信的方法和设备
WO2021232944A1 (zh) 一种通信传输的方法、装置及系统
WO2024032077A1 (zh) 上行传输方法和通信装置
US20240023130A1 (en) Method, apparatus and computer program
KR20230128028A (ko) 사용자 장비에 대한 향상된 불연속 수신 및 절전
US11864112B2 (en) Apparatus, method and computer program
WO2024032322A1 (zh) 信号传输方法与装置
WO2023246588A1 (zh) 一种通信方法及装置
WO2024032222A1 (zh) 一种通信方法及装置
WO2022237663A1 (zh) 一种侧行链路sl通信的方法和装置
WO2023165449A1 (zh) 一种通信方法及装置
WO2024017094A1 (zh) 非连续接收的管理方法、通信系统及装置
WO2024174270A1 (zh) 一种通信方法及装置
WO2024092576A1 (zh) 一种定时器的启动方法及装置
WO2022205993A1 (zh) 一种数据重传方法及相关设备
WO2022151284A1 (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: 23851307

Country of ref document: EP

Kind code of ref document: A1