WO2024067002A1 - 控制信息的监听方法及装置 - Google Patents

控制信息的监听方法及装置 Download PDF

Info

Publication number
WO2024067002A1
WO2024067002A1 PCT/CN2023/117448 CN2023117448W WO2024067002A1 WO 2024067002 A1 WO2024067002 A1 WO 2024067002A1 CN 2023117448 W CN2023117448 W CN 2023117448W WO 2024067002 A1 WO2024067002 A1 WO 2024067002A1
Authority
WO
WIPO (PCT)
Prior art keywords
shared channel
physical shared
retransmission timer
terminal
duration
Prior art date
Application number
PCT/CN2023/117448
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 WO2024067002A1 publication Critical patent/WO2024067002A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the present application relates to the field of wireless communications, and in particular to a method for monitoring control information.
  • a retransmission timer is started to receive retransmission scheduling information from a network device during the operation of the retransmission timer.
  • a retransmission timer is started to receive retransmission scheduling information from a network device during the operation of the retransmission timer.
  • a retransmission timer is started to receive retransmission scheduling information from a network device during the operation of the retransmission timer.
  • the current configuration of the retransmission timer is not reasonable, which affects the retransmission performance.
  • the embodiments of the present application provide a communication method and apparatus that can adjust the duration of a retransmission timer according to the number of at least one physical shared channel, so that the duration of the retransmission timer is configured more reasonably to improve the performance of data retransmission of at least one physical shared channel.
  • a communication method which can be executed by a terminal; or, it can also be executed by a module applied in the terminal, such as a chip, a chip system or a circuit, and can also be implemented by a logic module or software that can realize all or part of the terminal functions, without limitation.
  • a module applied in the terminal such as a chip, a chip system or a circuit
  • a logic module or software that can realize all or part of the terminal functions, without limitation.
  • the following is an example of execution by a terminal.
  • the method includes: receiving first control information from a network device for indicating data transmission of at least one physical shared channel; determining the duration of a retransmission timer according to the number of the at least one physical shared channel, the duration of the retransmission timer being the maximum duration of monitoring the second control information, the second control information being used to schedule data retransmission of the at least one physical shared channel; starting the retransmission timer, and monitoring the second control information within the duration of the retransmission timer.
  • the terminal can adjust the duration of the retransmission timer according to the number of at least one physical shared channel, so that the duration of the retransmission timer is more reasonable, thereby improving the data retransmission performance of at least one physical shared channel.
  • the method further includes: receiving configuration information from the network device, where the configuration information is used to configure multiple candidate durations of the retransmission timer.
  • the terminal may determine the duration of the retransmission timer from a plurality of candidate durations configured by the network device according to the number of at least one physical shared channel.
  • determining the duration of the retransmission timer based on the number of the at least one physical shared channel includes: determining the duration of the retransmission timer corresponding to the number of the at least one physical shared channel from the multiple candidate durations based on the number of the at least one physical shared channel.
  • the terminal may determine, among multiple candidate durations, a candidate duration corresponding to the number of at least one physical shared channel as the duration of the retransmission timer.
  • the duration of the retransmission timer is greater than the duration of the retransmission timer when the number of at least one physical shared channel is a second value, wherein the first value is greater than the second value.
  • the duration of the retransmission timer determined by the terminal is large, and if the number of at least one physical shared channel is small, the duration of the retransmission timer determined by the terminal is short. It can be understood that the greater the number of at least one physical shared channel, the greater the possibility of data retransmission, and the terminal may be scheduled to retransmit multiple times. At this time, the terminal determines a larger duration for the retransmission timer, which can prevent the retransmission of some channels in the at least one physical shared channel from being unable to be scheduled in time, thereby affecting the retransmission performance.
  • the physical shared channel is a physical uplink shared channel
  • starting the retransmission timer includes: starting the retransmission timer at time a+T1, where a is the time corresponding to the last physical shared channel of the at least one physical shared channel, and T1 is the duration configured by the network device.
  • the terminal may start the retransmission timer after sending the last physical shared channel of at least one physical shared channel, thereby shortening the time the terminal is in an active state and further reducing the power consumption of the terminal.
  • the physical shared channel is a physical uplink shared channel
  • the number of the at least one physical shared channel is greater than 1
  • starting the retransmission timer includes: starting the retransmission timer at time b+T2, where b is the time corresponding to the last physical shared channel actually sent in the at least one physical shared channel, and T2 is the duration configured by the network device.
  • the terminal can start the retransmission timer at a time after the time domain position of the last physical shared channel actually sent, thereby shortening the time the terminal is in an active state and further reducing the power consumption of the terminal.
  • the method further includes: sending indication information to the network device, where the indication information is used to indicate the last physical shared channel actually sent.
  • the terminal may indicate the last physical shared channel actually sent to the network device, so that the network device determines the last physical shared channel actually sent and further determines when to send retransmission indication information to the terminal.
  • the retransmission timer is a retransmission timer corresponding to the last physical shared channel; or, the retransmission timer is a retransmission timer corresponding to the at least one physical shared channel; or, the retransmission timer corresponds one-to-one to the at least one physical shared channel.
  • the terminal in the case where the retransmission timer is the retransmission timer corresponding to the last physical shared channel, the terminal can maintain a retransmission timer, thereby reducing the complexity of the terminal.
  • the terminal does not stop the retransmission timer no matter which physical shared channel the terminal receives the second control information corresponding to, until the retransmission timer times out, so that the terminal has time to receive the second control information corresponding to all physical shared channels that need to be retransmitted.
  • the terminal stops the retransmission timer corresponding to the physical shared channel to which the terminal receives the second control information, so that the terminal has time to receive the second control information corresponding to all physical shared channels that need to be retransmitted, and does not continue to maintain the retransmission timer when the second control information corresponding to at least one physical shared channel is received, thereby reducing the power consumption of the terminal.
  • the physical shared channel is a physical downlink shared channel
  • the method further includes: sending feedback information to the network device, the feedback information being used to indicate whether data transmission on the at least one physical shared channel is successful; starting the retransmission timer, including: starting the retransmission timer at time c+T3, where c is the time at which the feedback information is sent, and T3 is the duration configured by the network device.
  • the terminal may start the retransmission timer after sending the feedback information.
  • a communication method is provided, which can be executed by a network device; or, it can also be executed by a module applied to the network device, such as a chip, a chip system or a circuit, and can also be implemented by a logic module or software that can realize all or part of the network device functions, without limitation.
  • a module applied to the network device such as a chip, a chip system or a circuit
  • a logic module or software that can realize all or part of the network device functions, without limitation.
  • the following is an example of execution by a network device.
  • the method includes: sending first control information to a terminal, the first control information is used to indicate the data transmission of at least one physical shared channel; determining the duration of a retransmission timer according to the number of the at least one physical shared channel, the duration of the retransmission timer is the maximum duration of the terminal listening to the second control information, and the second control information is used to schedule the data retransmission of the at least one physical shared channel; starting the retransmission timer, and sending the second control information to the terminal within the duration of the retransmission timer.
  • the network device can adjust the duration of the retransmission timer according to the number of at least one physical shared channel, so that the duration of the retransmission timer is more reasonable, thereby improving the data retransmission performance of at least one physical shared channel.
  • the method further includes: sending configuration information to the terminal, where the configuration information is used to configure multiple candidate durations of the retransmission timer.
  • the network device can configure multiple candidate durations of the retransmission timer for the terminal so that the terminal The duration of the retransmission timer is determined according to the number of at least one physical shared channel among multiple candidate durations.
  • determining the duration of the retransmission timer based on the number of the at least one physical shared channel includes: determining the duration of the retransmission timer corresponding to the number of the at least one physical shared channel from the multiple candidate durations based on the number of the at least one physical shared channel.
  • the network device may determine, among multiple candidate durations, a candidate duration corresponding to the number of at least one physical shared channel as the duration of the retransmission timer.
  • the duration of the retransmission timer is greater than the duration of the retransmission timer when the number of the at least one physical shared channel is a second value, wherein the first value is greater than the second value.
  • the network device determines a larger duration for the retransmission timer, which can avoid the retransmission of some channels in at least one physical shared channel not being scheduled in time, affecting the retransmission performance.
  • the network device determines a smaller duration for the retransmission timer, which can reduce the power consumption of the terminal while ensuring the retransmission performance.
  • the physical shared channel is a physical uplink shared channel
  • starting the retransmission timer includes: starting the retransmission timer at time a+T1, where a is the time corresponding to the last physical shared channel of the at least one physical shared channel, and T1 is a first preset duration.
  • the network device may start the retransmission timer after sending the last physical shared channel of at least one physical shared channel, thereby shortening the time that the terminal is in an active state and further reducing the power consumption of the terminal.
  • the physical shared channel is a physical uplink shared channel
  • the number of the at least one physical shared channel is greater than 1
  • the retransmission timer is started, including: starting the retransmission timer at time b+T2, where b is the time corresponding to the last physical shared channel actually received in the at least one physical shared channel, and T2 is a second preset duration.
  • the network device may start the retransmission timer at a time after the time domain position of the last physical shared channel actually sent, thereby shortening the time the terminal is in an active state and further reducing the power consumption of the terminal.
  • the method further includes: receiving indication information from the terminal, where the indication information is used to indicate the last physical shared channel actually received.
  • the network device may determine the last physical shared channel actually received according to the indication information, and further determine when to send the retransmission indication information to the terminal.
  • the retransmission timer is a retransmission timer corresponding to the last physical shared channel; or, the retransmission timer is a retransmission timer corresponding to the at least one physical shared channel; or, the retransmission timer corresponds one-to-one to the at least one physical shared channel.
  • the network device in the case where the retransmission timer is the retransmission timer corresponding to the last physical shared channel, the network device can maintain a retransmission timer, thereby reducing the complexity of the network device.
  • the network device will not stop the retransmission timer no matter which physical shared channel the network device has sent the second control information corresponding to until the retransmission timer times out, so that the network device has time to send the second control information corresponding to all physical shared channels that need to be retransmitted.
  • the network device stops the retransmission timer corresponding to the physical shared channel to which the network device has sent the second control information, so that the network device has time to send the second control information corresponding to all physical shared channels that need to be retransmitted, and will not continue to maintain the retransmission timer when all the second control information corresponding to at least one physical shared channel has been received.
  • the physical shared channel is a physical downlink shared channel
  • the method also includes: receiving feedback information from the terminal, the feedback information is used to indicate whether the data transmission on the at least one physical shared channel is successful; starting the retransmission timer, including: starting the retransmission timer at time c+T3, where c is the time when the feedback information is received, and T3 is a third preset duration.
  • the network device may start a retransmission timer after receiving the feedback information.
  • a communication device for implementing the above method.
  • the communication device can be the terminal in the first aspect.
  • the communication device may be a terminal, or a device including the above-mentioned terminal, or a module in the terminal in the above-mentioned first aspect, such as a chip, a chip system or a circuit, or a logical module or software implementation that can realize part or all of the terminal functions; or, the communication device may be a network device in the above-mentioned second aspect, or a device including the above-mentioned network device, or a module in the network device in the above-mentioned second aspect, such as a chip, a chip system or a circuit, or a logical module or software implementation that can realize part or all of the network device functions.
  • the communication device includes a module, unit, or means corresponding to the implementation of the above-mentioned method, and the module, unit, or means may be implemented by hardware, software, or by executing the corresponding software implementation by hardware.
  • the hardware or software includes one or more modules or units corresponding to the above-mentioned functions.
  • the communication device may include a transceiver module and a processing module.
  • the transceiver module which may also be referred to as a transceiver unit, is used to implement the sending and/or receiving functions in any of the above aspects and any possible implementations thereof.
  • the transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the processing module may be used to implement the processing functions in any of the above aspects and any possible implementations thereof.
  • the processing module may be, for example, a processor.
  • the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in any of the above aspects and any possible implementations thereof.
  • a communication device comprising: a processor; the processor is used to couple with a memory, and after reading the instruction in the memory, execute the method as described in any of the above aspects according to the instruction.
  • the communication device can be the terminal in the above first aspect, or a device including the above terminal, or a module in the terminal in the above first aspect, such as a chip, a chip system or a circuit, or a logic module or software implementation that can realize part or all of the terminal functions; or the communication device can be the network device in the above second aspect, or a device including the above network device, or a module in the network device in the above second aspect, such as a chip, a chip system or a circuit, or a logic module or software implementation that can realize part or all of the network device functions.
  • the communication device further includes a memory, and the memory is used to store necessary program instructions and data.
  • the communication device is a chip or a chip system.
  • the communication device when it is a chip system, it can be composed of a chip, or it can include a chip and other discrete devices.
  • a communication device comprising: a processor and an interface circuit; the interface circuit is used to receive a computer program or instruction and transmit it to the processor; the processor is used to execute the computer program or instruction so that the communication device executes the method described in any of the above aspects.
  • the communication device can be the terminal in the above first aspect, or a device including the above terminal, or a module in the terminal in the above first aspect, such as a chip, a chip system or a circuit, or a logic module or software implementation that can realize part or all of the terminal functions; or, the communication device can be the network device in the above second aspect, or a device including the above network device, or a module in the network device in the above second aspect, such as a chip, a chip system or a circuit, or a logic module or software implementation that can realize part or all of the network device functions.
  • the communication device is a chip or a chip system.
  • the communication device when it is a chip system, it can be composed of a chip, or it can include a chip and other discrete devices.
  • a computer-readable storage medium wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer can execute the method described in any one of the above aspects.
  • a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in any one of the above aspects.
  • a communication system which includes a terminal for executing the method described in the first aspect and a network device for executing the method described in the second aspect.
  • a communication system which includes a terminal and a network device, the network device being used to send first control information indicating data transmission of at least one physical shared channel to the terminal; the terminal being used to receive the first control information from the network device; the terminal being further used to determine the duration of a retransmission timer based on the number of the at least one physical shared channel, the duration of the retransmission timer being the maximum duration for monitoring second control information, the second control information being used to schedule data retransmission of the at least one physical shared channel; the terminal being further used to start the retransmission timer and monitor the second control information within the duration of the retransmission timer.
  • the network device is further used to send configuration information for configuring multiple candidate durations of the retransmission timer to the terminal; and the terminal is further used to receive the configuration information from the network device.
  • the terminal is also used to determine the duration of the retransmission timer based on the number of the at least one physical shared channel, including: the terminal determines the duration of the retransmission timer corresponding to the number of the at least one physical shared channel from the multiple candidate durations based on the number of the at least one physical shared channel.
  • the duration of the retransmission timer is greater than the duration of the retransmission timer when the number of the at least one physical shared channel is a second value, wherein the first value is greater than the second value.
  • the physical shared channel is a physical uplink shared channel
  • the terminal is also used to start the retransmission timer, including: the terminal starts the retransmission timer at time a+T1, where a is the time corresponding to the last physical shared channel of the at least one physical shared channel, and T1 is the duration configured by the network device.
  • the physical shared channel is a physical uplink shared channel
  • the number of the at least one physical shared channel is greater than 1
  • the terminal is also used to start the retransmission timer, including: the terminal starts the retransmission timer at time b+T2, where b is the time corresponding to the last physical shared channel actually sent in the at least one physical shared channel, and T2 is the duration configured by the network device.
  • the terminal is further configured to send indication information indicating the last physical shared channel actually sent to the network device; and the network device is further configured to receive the indication information from the terminal.
  • the retransmission timer is a retransmission timer corresponding to the last physical shared channel; or, the retransmission timer is a retransmission timer corresponding to the at least one physical shared channel; or, the retransmission timer corresponds one-to-one to the at least one physical shared channel.
  • the physical shared channel is a physical downlink shared channel
  • the terminal is further used to send feedback information to the network device to indicate whether the data transmission on the at least one physical shared channel is successful;
  • the network device is further used to receive the feedback information from the terminal;
  • the terminal is further used to start the retransmission timer, including: the terminal starts the retransmission timer at time c+T3, where c is the time when the feedback information is sent, and T3 is the duration configured by the network device.
  • a communication method is provided, which can be executed by a terminal/network device; or, it can also be executed by a module applied to the terminal/network device, such as a chip, a chip system or a circuit, and can also be implemented by a logic module or software that can realize all or part of the terminal/network device functions, without limitation.
  • a network device and a terminal are used to execute the method as an example for introduction.
  • the communication method includes: the network device sends a first control information for indicating the data transmission of at least one physical shared channel to the terminal; the terminal receives the first control information from the network device; the terminal determines the duration of the retransmission timer according to the number of the at least one physical shared channel, and the duration of the retransmission timer is the maximum duration of monitoring the second control information, and the second control information is used to schedule the data retransmission of the at least one physical shared channel; the terminal starts the retransmission timer and monitors the second control information within the duration of the retransmission timer.
  • the network device sends configuration information for configuring multiple candidate durations of the retransmission timer to the terminal; and the terminal receives the configuration information from the network device.
  • the terminal determines the duration of the retransmission timer based on the number of the at least one physical shared channel, including: the terminal determines the duration of the retransmission timer corresponding to the number of the at least one physical shared channel from the multiple candidate durations based on the number of the at least one physical shared channel.
  • the duration of the retransmission timer is greater than the duration of the retransmission timer when the number of the at least one physical shared channel is a second value, wherein the first value is greater than the second value.
  • the physical shared channel is a physical uplink shared channel
  • the terminal starts the retransmission timer, including: the terminal starts the retransmission timer at time a+T1, where a is the time corresponding to the last physical shared channel of the at least one physical shared channel, and T1 is the duration configured by the network device.
  • the physical shared channel is a physical uplink shared channel
  • the number of the at least one physical shared channel is greater than 1
  • the terminal starts the retransmission timer, including: the terminal starts the retransmission timer at time b+T2, where b is the time corresponding to the last physical shared channel actually sent in the at least one physical shared channel, and T2 is the duration configured by the network device.
  • the terminal sends indication information for indicating the last physical shared channel actually sent to the network device; and the network device receives the indication information from the terminal.
  • the retransmission timer is a retransmission timer corresponding to the last physical shared channel; or, the retransmission timer is a retransmission timer corresponding to the at least one physical shared channel; or, the retransmission timer corresponds one-to-one to the at least one physical shared channel.
  • the physical shared channel is a physical downlink shared channel
  • the terminal sends feedback information to the network device to indicate whether the data transmission on the at least one physical shared channel is successful; the network device receives the feedback information from the terminal; the terminal starts the retransmission timer, including: the terminal starts the retransmission timer at time c+T3, where c is the time when the feedback information is sent, and T3 is the duration configured by the network device.
  • the technical effects brought about by any possible implementation method in the third to tenth aspects can refer to the technical effects brought about by any aspect in the first to second aspects or different possible implementation methods in any aspect, and will not be repeated here.
  • FIG1 is a schematic diagram of discontinuous reception (DRX);
  • FIG2 is a schematic diagram of a drx-InactivityTimer
  • FIG3A is a schematic diagram of drx-HARQ-RTT-TimerDL and drx-RetransmissionTimerDL;
  • FIG3B is a schematic diagram of drx-HARQ-RTT-TimerUL and drx-RetransmissionTimerUL;
  • FIG4A is a schematic diagram of downlink control information (DCI) scheduling PUSCH;
  • DCI downlink control information
  • FIG4B is a schematic diagram of DCI scheduling PDSCH
  • FIG5 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
  • FIG6 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application.
  • FIG7 is a flow chart of a communication method provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • the fifth generation (5G) new radio (NR) standard introduces DRX technology.
  • DRX technology can be used for power saving.
  • the basic mechanism of DRX technology is to configure the DRX cycle for the terminal.
  • the DRX cycle includes an activation period (on duration) and a sleep period (opportunity for DRX).
  • the terminal is in an active state during the activation period and can send and receive data normally.
  • the sleep period it has the opportunity to enter the sleep state and not receive PDCCH to reduce power consumption.
  • PDCCH acknowledgment signals
  • a terminal in the sleep state can receive PDSCH sent on a periodically configured downlink subframe.
  • the terminal receives PDCCH during the active period, it means that the terminal may need to send and receive data in the next period of time, so the terminal can start or restart drx-InactivityTimer.
  • the terminal is in the active state and continues to monitor PDCCH.
  • the terminal starts the drx-InactivityTimer with a duration of t2.
  • the terminal is in the active state in the t1 and t2 time periods and can monitor PDCCH.
  • DRX hybrid automatic repeat request (HARQ) round-trip time (RTT) timer (drx-HARQ-RTT-Timer) and DRX retransmission timer (drx-RetransmissionTimer)
  • drx-HARQ-RTT-Timer can be divided into a DRX HARQ RTT uplink (up link, UL) timer (drx-HARQ-RTT-TimerUL) and a DRX HARQ RTT downlink (down link, DL) timer (drx-HARQ-RTT-TimerDL) according to the transmission direction of the data.
  • drx-RetransmissionTimer can also be divided into a DRX retransmission uplink timer (drx-RetransmissionTimerUL) and a DRX retransmission downlink timer (drx-RetransmissionTimerDL) according to the transmission direction of the data.
  • the terminal if the terminal receives a PDCCH indicating a downlink transmission, or receives a PDSCH of an SPS (at this time without an accompanying transmission PDCCH), and the terminal fails to receive data, the network device needs to retransmit the data. After feeding back a HARQ negative acknowledgment (not-acknowledgement, NACK) message, the terminal can start drx-HARQ-RTT-TimerDL for the corresponding HARQ process.
  • NACK HARQ negative acknowledgment
  • the duration of drx-HARQ-RTT-TimerDL can be used to indicate the minimum duration that the terminal expects to receive HARQ retransmission indication information, that is, during the drx-HARQ-RTT-TimerDL period, the terminal does not expect to receive DL retransmission indication information.
  • the terminal may start the drx-RetransmissionTimerDL.
  • the duration of the drx-RetransmissionTimerDL may indicate the maximum duration for the terminal to receive the DL retransmission indication information. That is, during the drx-RetransmissionTimerDL, the terminal is in an activated state and may receive PDCCH and/or PDSCH, such as receiving DL retransmission indication information.
  • the terminal if the terminal receives a PDCCH indicating uplink transmission or receives a PUSCH of CG (at this time, there is no transmission PDCCH), and after completing the PUSCH transmission, the terminal starts drx-HARQ-RTT-TimerUL for the corresponding HARQ process.
  • the duration of drx-HARQ-RTT-TimerUL can indicate the minimum duration that the terminal expects to receive the HARQ retransmission indication information, that is, during drx-HARQ-RTT-TimerUL, the terminal does not expect to receive UL retransmission indication information.
  • the terminal starts drx-RetransmissionTimerUL.
  • the duration of drx-RetransmissionTimerUL can indicate the maximum duration that the terminal receives the UL retransmission indication information.
  • the terminal is in an activated state and receives PDCCH indicating PUSCH retransmission.
  • a scheme is proposed for scheduling multiple PDSCHs or multiple PUSCHs by DCI, so that the terminal can avoid frequent monitoring of DCI, thereby reducing the power consumption and complexity of the terminal.
  • the terminal will start drx-HARQ-RTT-TimerUL after each PUSCH transmission is completed. After the drx-HARQ-RTT-TimerUL times out, the terminal will start drx-RetransmissionTimerUL and continue to monitor PDCCH during the operation of drx-RetransmissionTimerUL. Specifically, it can be shown in Figure 4A.
  • h1 represents the duration of drx-HARQ-RTT-TimerUL corresponding to the first PUSCH scheduled by DCI
  • r1 represents the duration of drx-RetransmissionTimerUL corresponding to the first PUSCH scheduled by DCI
  • h2 represents the duration of drx-HARQ-RTT-TimerUL corresponding to the second PUSCH scheduled by DCI
  • r2 represents the duration of drx-RetransmissionTimerUL corresponding to the second PUSCH scheduled by DCI.
  • h3 represents the duration of drx-HARQ-RTT-TimerUL corresponding to the third PUSCH scheduled by DCI
  • r3 represents the duration of drx-RetransmissionTimerUL corresponding to the third PUSCH scheduled by DCI.
  • the terminal For a DCI scheduling multiple PDSCHs, if the terminal is configured with DRX, the HARQ-NACK information of multiple PDSCHs will be fed back on the same PUCCH. After the terminal feeds back the HARQ-NACK information, it will start the drx-HARQ-RTT-TimerDL corresponding to the HARQ process. After the drx-HARQ-RTT-TimerDL times out, the terminal will start the drx-RetransmissionTimerDL, that is, the drx-HARQ-RTT-TimerDL corresponding to multiple PDSCHs overlap in the time domain, and the drx-RetransmissionTimerDL corresponding to multiple PDSCHs also overlap in the time domain.
  • h represents the duration of the drx-HARQ-RTT-TimerUL corresponding to the multiple PDSCHs scheduled by the DCI
  • r represents the duration of the drx-RetransmissionTimerUL corresponding to the multiple PDSCHs scheduled by the DCI.
  • the communication system can be a long term evolution (LTE) system, a 5G communication system, a Wi-Fi system, a communication system related to the third generation partnership project (3GPP), a future evolving communication system (such as: the sixth generation (6th generation, 6G) communication system, etc.), or a system integrating multiple systems, etc., without limitation.
  • LTE long term evolution
  • 5G communication system a 5G communication system
  • Wi-Fi a wireless local area network
  • 3GPP third generation partnership project
  • future evolving communication system such as: the sixth generation (6th generation, 6G) communication system, etc.
  • 6G sixth generation
  • system integrating multiple systems etc.
  • the communication system 50 may include one or more network devices 501 (only one is shown) and terminals 502-504 that can communicate with the network device 501.
  • the network device can provide wireless access services to the terminal.
  • each network device corresponds to a service
  • the service coverage area is a service coverage area.
  • the terminal entering the area can communicate with the network device through the Uu port to receive the wireless access service provided by the network device.
  • the service coverage area can include one or more cells.
  • the terminal and the network device can communicate through the Uu port link.
  • the Uu port link can be divided into UL and DL according to the direction of the data transmitted thereon. Uplink data sent from the terminal to the network device can be transmitted on the UL, and downlink data transmitted from the network device to the terminal can be transmitted on the DL.
  • the terminal 503 is located in the coverage area of the network device 501, the network device 501 can send downlink data to the terminal 503 through the DL, and the terminal 503 can send uplink data to the network device 501 through the UL.
  • the network device in the embodiment of the present application can be any device with wireless transceiver function. Including but not limited to: the evolved base station (NodeB or eNB or e-NodeB, evolutional Node B) in LTE, the base station (gNodeB or gNB) or the transmission receiving point/transmission reception point (TRP) in NR, the base station of the subsequent evolution of 3GPP, the access node in the Wi-Fi system, the wireless relay node, the wireless backhaul node, etc.
  • the base station can be: a macro base station, a micro base station, a micro-micro base station, a small station, a relay station, or a balloon station, etc.
  • the base station can include one or more co-sited or non-co-sited TRPs.
  • the network device can also be a wireless controller in the cloud radio access network (CRAN) scenario.
  • the network device can also be a centralized unit (CU) and/or a distributed unit (DU).
  • the network device may also be a server, a wearable device, a machine communication device, or a vehicle-mounted device, etc.
  • the following is an example of a network device being a base station.
  • the multiple network devices may be base stations of the same type or different types.
  • the base station may communicate with the terminal or communicate with the terminal through a relay station.
  • the terminal may communicate with multiple base stations of different technologies.
  • the terminal may communicate with a base station supporting an LTE network or a base station supporting a 5G network, and may also support dual connections with a base station of an LTE network and a base station of a 5G network.
  • a device for realizing the function of a network device may be a network device; or it may be a device capable of supporting the network device to realize the function, such as a chip system, which may be installed in the network device or used in combination with the network device.
  • the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • the method provided in the embodiment of the present application is described by taking the device for realizing the function of a network device as an example that the network device is a network device.
  • terminal 502 terminal 503 or terminal 504 is a device with wireless transceiver function.
  • the terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).
  • the terminal can also be called a terminal device, and the terminal device can be a user equipment (UE), wherein the UE includes a handheld device, a vehicle-mounted device, a wearable device or a computing device with a wireless communication function.
  • the UE can be a mobile phone, a tablet computer or a computer with a wireless transceiver function.
  • the terminal device can also be a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, or a wireless terminal in a smart home, etc.
  • the device for realizing the function of the terminal can be a terminal; it can also be a device that can support the terminal to realize the function, such as a chip system, which can be installed in the terminal or used in combination with the terminal.
  • the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • the method provided in the embodiment of the present application is described by taking the device for realizing the function of the terminal as an example.
  • the terminal may be a wearable device.
  • Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that apply wearable technology to intelligently design and develop wearable devices for daily wear, such as gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories.
  • a wearable device is not only a hardware device, but also a device that realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include devices with full functions, large sizes, and devices that can realize complete or partial functions without relying on smartphones, such as smart watches, etc., as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
  • the terminal may be a terminal in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • MTC machine type communication
  • the terminal of the present application may be an on-board module, on-board module, on-board component, on-board chip or on-board unit built into the vehicle as one or more components or units.
  • the vehicle may implement the method of the present application through the built-in on-board module, on-board module, on-board component, on-board chip or on-board unit.
  • the method provided in the embodiment of the present application can be applied to multimedia services with strong real-time performance and large data capacity requirements, such as video transmission, cloud gaming (CG) and extended reality (XR).
  • XR includes virtual reality (VR) and augmented reality (AR).
  • the terminal in the embodiment of the present application can also be a head mounted display (HMD) or smart glasses (such as VR glasses, AR glasses), etc., without limitation.
  • HMD head mounted display
  • smart glasses such as VR glasses, AR glasses
  • the communication system 50 shown in Figure 5 is only used as an example and is not used to limit the technical solution of the present application. Those skilled in the art should understand that in the specific implementation process, the communication system 50 may also include other devices, and the number of network devices and terminals may also be determined according to specific needs without limitation.
  • each network element or device in Figure 5 of the embodiment of the present application can also be referred to as a communication device, which can be a general device or a special device, and the embodiment of the present application does not make any specific limitations on this.
  • each network element or device e.g., network device 501, terminal 502, terminal 503, or terminal 504 in FIG. 5 of the embodiment of the present application can be implemented by one device, or by multiple devices together, or by one or more functional modules in one device, and the embodiment of the present application does not specifically limit this. It is understandable that the above functions can be network elements in hardware devices, or software functions running on dedicated hardware, or a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).
  • a platform e.g., a cloud platform
  • each network element or device shown in FIG5 can adopt the composition structure shown in FIG6, or include the components shown in FIG6.
  • FIG6 is a schematic diagram of the hardware structure of a communication device applicable to an embodiment of the present application.
  • the communication device 60 includes at least one processor 601 and at least one communication interface 604, which are used to implement the method provided in an embodiment of the present application.
  • the communication device 60 may also include a communication line 602 and a memory 603.
  • Processor 601 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication link 602 may include a path to transmit information between the above-mentioned components, such as a bus.
  • the communication interface 604 is used to communicate with other devices or communication networks.
  • the communication interface 604 can be any transceiver-like device, such as an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, a transceiver, a pin, a bus, or a transceiver circuit.
  • RAN radio access network
  • WLAN wireless local area network
  • the memory 603 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
  • the memory may exist independently and be coupled to the processor 601 through the communication line 602.
  • the memory 603 may also be integrated with the processor 601.
  • the memory provided in the embodiment of the present application may generally have non-volatility.
  • the memory 603 is used to store the computer execution instructions involved in executing the scheme provided in the embodiment of the present application, and the execution is controlled by the processor 601.
  • the processor 601 is used to execute the computer execution instructions stored in the memory 603, so as to implement the method provided in the embodiment of the present application.
  • the processor 601 may also perform the processing-related functions in the method provided in the following embodiment of the present application, and the communication interface 604 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiment of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 6 .
  • the communication device 60 may include multiple processors, such as the processor 601 and the processor 607 in FIG6.
  • processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (such as computer program instructions).
  • the communication device 60 may further include an output device 605 and/or an input device 606.
  • the output device 605 is coupled to the processor 601 and can display information in a variety of ways.
  • the output device 605 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
  • the input device 606 is coupled to the processor 601 and can receive user input in a variety of ways.
  • the input device 606 may be a mouse, a keyboard, a touch screen device, or a sensor device.
  • composition structure shown in FIG6 does not constitute a limitation on the communication device.
  • the communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
  • transmission can be understood as sending and/or receiving according to the specific context.
  • Transmission can be a noun or a verb.
  • transmission is often used instead of sending and/or receiving.
  • the phrase “transmitting PUSCH” can be understood as “sending PUSCH” from the perspective of the terminal, and can be understood as “receiving PUSCH” from the perspective of the base station.
  • transmitting PUSCH/PDSCH can be understood by those skilled in the art as “transmitting information carried in PUSCH/PDSCH”.
  • A/B can indicate A or B
  • a and/or can be used to describe that there are three relationships between the associated objects, for example, A and/or B can indicate: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • expressions similar to "at least one of A, B and C" or “at least one of A, B or C” are usually used to indicate any of the following: A exists alone; B exists alone; C exists alone; A and B exist at the same time; A and C exist at the same time; B and C exist at the same time; A, B and C exist at the same time.
  • the above uses A, B and C as examples to illustrate the optional items of the item.
  • the words “first”, “second” and the like may be used to distinguish between technical features with the same or similar functions.
  • the words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like do not necessarily limit the differences.
  • the words “exemplary” or “for example” are used to represent examples, illustrations or explanations, and any embodiment or design described as “exemplary” or “for example” should not be interpreted as being more preferred or more advantageous than other embodiments or design.
  • the use of words such as “exemplary” or “for example” is intended to present related concepts in a concrete way for easy understanding.
  • the terminal and/or the network device may perform some or all of the steps in the embodiments of the present application, and these steps are only examples, and the embodiments of the present application may also perform other steps or variations of various steps.
  • the various steps may be performed in different orders presented in the embodiments of the present application, and it is possible that not all of the steps in the embodiments of the present application need to be performed.
  • a communication method is provided for an embodiment of the present application.
  • a network device and a terminal are used as examples to illustrate the method, but the present application does not limit the execution subject of the interaction diagram.
  • the network device in Figure 7 may also be a chip, a chip system, or a processor that supports the network device to implement the method, or a logic module or software that can implement all or part of the network device functions;
  • the terminal in Figure 7 may also be a chip, a chip system, or a processor that supports the terminal to implement the method, or a logic module or software that can implement all or part of the terminal functions.
  • the communication method may include the following steps:
  • S701 The network device sends first control information to the terminal.
  • the terminal receives the first control information from the network device.
  • the network device may be the network device 501 in the communication system 50 shown in FIG5 .
  • the terminal may be any terminal in the communication system 50 shown in FIG5 , for example, the terminal 502 .
  • the first control information may be used to indicate data transmission of at least one physical shared channel, wherein the physical shared channel may be a PUSCH or a PDSCH.
  • the first control information indicating data transmission of at least one PUSCH can be understood as the first control information scheduling at least one PUSCH.
  • the first control information indicating data transmission of at least one PDSCH can be understood as the first control information scheduling at least one PDSCH.
  • the first control information is DCI.
  • the terminal After receiving the DCI, the terminal can perform data transmission on at least one physical shared channel according to the DCI.
  • the DCI includes indication information of at least one PDSCH time-frequency resource. After receiving the DCI, the terminal receives at least one PDSCH on the time-frequency resource. If the physical shared channel is PUSCH, the DCI includes indication information of at least one PUSCH time-frequency resource. After receiving the DCI, the terminal sends at least one PUSCH on the time-frequency resource.
  • the first control information is included in a configuration message of semi-static scheduling, such as a radio resource control (RRC) message or a DCI.
  • RRC radio resource control
  • the terminal may perform data transmission on at least one physical shared channel according to the configuration message of semi-static scheduling; or, after receiving the configuration message of semi-static scheduling, the terminal does not perform data transmission on at least one physical shared channel first, and then performs transmission after receiving an activation message (such as DCI) for activating the configuration message of the semi-static scheduling.
  • an activation message such as DCI
  • the first control information is included in the RRC message, and the first control information includes indication information of at least one PDSCH time-frequency resource.
  • the terminal After receiving the RRC message from the network device and receiving the DCI for activating at least one PDSCH configured by the RRC message, the terminal receives at least one PDSCH on the time-frequency resource.
  • the first control information is included in an RRC message or a DCI, and the first control information includes indication information of a time-frequency resource of at least one PUSCH.
  • the terminal After receiving an RRC message or a DCI from a network device, the terminal sends at least one PUSCH on the time-frequency resource.
  • the first control information is included in an RRC message, and the first control information includes indication information of a time-frequency resource of at least one PUSCH. After receiving an RRC message from a network device and receiving a DCI for activating at least one PUSCH configured by the RRC message, the terminal sends at least one PUSCH on the time-frequency resource.
  • the terminal determines the duration of the retransmission timer according to the number of at least one physical shared channel.
  • the duration of the retransmission timer is the maximum duration of monitoring the second control information.
  • the second control information can be used to schedule data retransmission of at least one physical shared channel.
  • the retransmission timer is drx-RetransmissionTimerDL
  • the retransmission timer is drx-RetransmissionTimerUL. It should be understood that in specific applications, the retransmission timer can also have other naming methods, which are not specifically limited in the embodiments of the present application.
  • the greater the number of at least one physical shared channel the greater the possibility of data retransmission, and the terminal may To be scheduled for multiple retransmissions.
  • the terminal sets the duration of the retransmission timer too short, the retransmission of some channels in at least one physical shared channel will not be scheduled in time, affecting the retransmission performance. Therefore, in an embodiment of the present application, the more the number of at least one physical shared channel, the longer the duration of the retransmission timer, and the fewer the number of at least one physical shared channel, the shorter the duration of the retransmission timer.
  • the duration of the retransmission timer is greater than the duration of the retransmission timer when the number of at least one physical shared channel is a second value.
  • the first value is greater than the second value.
  • the terminal is in an activated state within the duration of the retransmission timer and needs to monitor the PDCCH, so the power consumption of the terminal should also be considered when determining the duration of the retransmission timer.
  • both the retransmission performance and the power consumption of the terminal should be taken into account.
  • the terminal determines the duration of the retransmission timer according to the number of at least one physical shared channel and the corresponding relationship.
  • the correspondence between the number of at least one physical shared channel and the duration of the retransmission timer may be shown in Table 1.
  • the duration of any retransmission timer corresponds to a number range. If the number of at least one physical shared channel is 1 or 2, the duration of the retransmission timer is t1, if the number of at least one physical shared channel is 3 or 4, the duration of the retransmission timer is t2, and if the number of at least one physical shared channel is 5 or 6, the duration of the retransmission timer is t3.
  • the correspondence between the number of at least one physical shared channel and the duration of the retransmission timer may be shown in Table 2.
  • the duration of any retransmission timer corresponds to the number of a physical shared channel. If the number of at least one physical shared channel is 1, the duration of the retransmission timer is t1, if the number of at least one physical shared channel is 2, the duration of the retransmission timer is t2, and if the number of at least one physical shared channel is 3, the duration of the retransmission timer is t3.
  • the correspondence between the number of at least one physical shared channel and the duration of the retransmission timer may be shown in Table 3.
  • Table 3 if the number of at least one physical shared channel is 1, the duration of the retransmission timer is t1, and if the number of at least one physical shared channel is greater than 1, the duration of the retransmission timer is t2.
  • Tables 1, 2 and 3 are merely examples of the correspondence between the number of at least one physical shared channel and the duration of the retransmission timer. In specific applications, the correspondence between the number of at least one physical shared channel and the duration of the retransmission timer may also be in other forms without limitation.
  • the network device sends configuration information to the terminal.
  • the terminal receives the configuration information from the network device.
  • the configuration information can be used to configure multiple candidate durations of the retransmission timer.
  • the configuration information includes the multiple candidate durations of the retransmission timer.
  • multiple may refer to greater than or equal to 2.
  • the terminal may determine the duration of the retransmission timer according to the multiple candidate durations configured by the configuration information and the number of at least one physical shared channel.
  • the terminal determines, according to the number of at least one physical shared channel, from a plurality of candidate durations, a duration of a retransmission timer corresponding to the number of at least one physical shared channel.
  • the terminal can determine that the duration of the retransmission timer corresponding to the number of at least one physical shared channel is t1 according to the above Table 1, and the terminal can determine that the duration of the retransmission timer corresponding to the number of at least one physical shared channel is t2 according to the above Table 2.
  • the terminal can determine, based on the above Table 3, that the duration of the retransmission timer corresponding to the number of at least one physical shared channel is t2; if the configuration information includes t1 and t2, and the number of at least one physical shared channel is 1, the terminal can determine, based on the above Table 3, that the duration of the retransmission timer corresponding to the number of at least one physical shared channel is t1.
  • the network device determines the duration of the retransmission timer according to the number of at least one physical shared channel. In this way, the network device can know when the terminal is in an activated state to receive the second control information. The network device can send the second control information to the terminal within the duration of the retransmission timer.
  • the process of the network device determining the duration of the retransmission timer according to the number of at least one physical shared channel can refer to the corresponding description of the terminal determining the duration of the retransmission timer according to the number of at least one physical shared channel, which is not repeated here.
  • S703 The terminal starts a retransmission timer, and monitors the second control information within the duration of the retransmission timer.
  • the terminal can be configured to start the retransmission timers corresponding to multiple PUSCHs at the same time. In this way, the time that the terminal is in an active state can be shortened, so the power consumption of the terminal can be reduced.
  • the terminal can start the retransmission timer corresponding to each PUSCH in multiple PUSCHs at the same time, or start the retransmission timer corresponding to a certain PUSCH in multiple PUSCHs, or start a retransmission timer to monitor the corresponding second control information of multiple PUSCHs.
  • the retransmission timer is a retransmission timer corresponding to the last physical shared channel; or, the retransmission timer is a retransmission timer corresponding to at least one physical shared channel; or, the retransmission timer corresponds to at least one physical shared channel one-to-one.
  • the last physical shared channel is the last physical shared channel in at least one physical shared channel, or, the last physical shared channel is the last physical shared channel actually sent in at least one physical shared channel.
  • the retransmission timer corresponding to the last physical shared channel can be understood as the terminal starting the retransmission timer corresponding to the last physical shared channel, and not starting the retransmission timers of other physical shared channels except the last physical shared channel in at least one physical shared channel.
  • the terminal can receive the second control information within the duration of the retransmission timer.
  • the terminal stops the retransmission timer and enters a dormant state, which may cause the terminal to fail to receive the second control information corresponding to other physical shared channels.
  • the retransmission timer corresponding to at least one physical shared channel can be understood as the terminal starting a retransmission timer for at least one physical shared channel.
  • the terminal can receive the second control information within the duration of the retransmission timer.
  • the terminal does not stop the retransmission timer until the retransmission timer times out, so that the terminal has time to receive the second control information corresponding to all physical shared channels that need to be retransmitted.
  • the retransmission timer has not timed out, and the terminal will not stop the retransmission timer, which will increase the power consumption of the terminal.
  • the one-to-one correspondence between the retransmission timer and the at least one physical shared channel can be understood as the terminal starting the retransmission timer for each physical shared channel in the at least one physical shared channel.
  • the terminal can Furthermore, the terminal stops the retransmission timer corresponding to the physical shared channel to which the terminal receives the second control information, so that the terminal can receive the second control information corresponding to all the physical shared channels that need to be retransmitted in time, and will not continue to maintain the retransmission timer when the second control information corresponding to at least one physical shared channel is received, thereby reducing the power consumption of the terminal.
  • the terminal starts the retransmission timer at time a+T1, where a is the time corresponding to the last physical shared channel of at least one physical shared channel, and T1 is a first preset duration, which is a duration configured by the network device.
  • T1 is the duration of drx-HARQ-RTT-TimerUL.
  • the terminal starts the drx-HARQ-RTT-TimerUL timer, and after the drx-HARQ-RTT-TimerUL times out, starts the retransmission timer.
  • the retransmission timer corresponding to the third PUSCH is started, or the retransmission timers corresponding to 3 PUSCHs are started, or the retransmission timers corresponding to each of the 3 PUSCHs are started.
  • the terminal is in an active state during the A2 time period.
  • the terminal starts the retransmission timer at time b+T2.
  • b is the time corresponding to the last physical shared channel actually sent in the at least one physical shared channel
  • T2 is the second preset duration, which is the duration configured by the network device.
  • T2 is the duration of drx-HARQ-RTT-TimerUL.
  • the terminal starts the drx-HARQ-RTT-TimerUL timer after the second PUSCH is sent, and starts the retransmission timer after the drx-HARQ-RTT-TimerUL times out.
  • the retransmission timer corresponding to the second PUSCH is started, or the retransmission timers corresponding to the three PUSCHs are started, or the retransmission timer corresponding to each of the three PUSCHs is started.
  • the terminal can indicate to the network device which physical shared channel is the last physical shared channel actually sent, so that the network device determines when to send the second control information to the terminal.
  • the terminal sends indication information to the network device.
  • the network device receives the indication information from the terminal.
  • the indication information may be used to indicate the last physical shared channel actually sent by the terminal, or the indication information may be used to indicate the last physical shared channel actually received by the network device.
  • the time-frequency resources corresponding to the indication information are the same as the time-frequency resources corresponding to the last physical shared channel actually sent. That is, the terminal sends the indication information through the time-frequency resources corresponding to the last physical shared channel actually sent.
  • the indication information includes 1 bit, and if the value of the 1 bit is 1, it means that the physical shared channel with the same time-frequency resources as the time-frequency resources corresponding to the indication information is the last physical shared channel actually sent.
  • the time-frequency resources corresponding to the indication information are the same as the time-frequency resources corresponding to the first physical shared channel in at least one physical shared channel. That is, the terminal sends the indication information through the time-frequency resources corresponding to the first physical shared channel in at least one physical shared channel.
  • the indication information may include an identifier of the last physical shared channel actually sent, or the indication information includes the number of physical shared channels actually sent, so that the network device determines the last physical shared channel actually sent by the terminal based on the indication information.
  • the terminal sends feedback information to the network device.
  • the network device receives feedback information from the terminal.
  • the feedback information may be used to indicate whether data transmission on at least one physical shared channel is successful.
  • the feedback information includes indication information corresponding to each physical shared channel of at least one physical shared channel, where the indication information indicates whether data transmission on the physical shared channel corresponding to the indication information is successful.
  • the feedback information includes 1-bit indication information.
  • the 1-bit indication information is used to indicate whether the data transmission on at least one physical shared channel is successful. For example, if the data transmission on each physical shared channel in at least one physical shared channel is successful, the 1-bit indication information indicates that the data transmission on at least one physical shared channel is successful; if the data transmission on at least one physical shared channel in at least one physical shared channel fails, the 1-bit indication information indicates that the data transmission on at least one physical shared channel fails.
  • the terminal starts the retransmission timer at time c+T3, where c is the time of sending the feedback information, and T3 is the third preset duration, which is the duration configured by the network device.
  • the terminal after sending the feedback information, the terminal starts the drx-HARQ-RTT-TimerDL timer, and after the drx-HARQ-RTT-TimerDL times out, starts the retransmission timer.
  • the network device starts a retransmission timer and sends the second control information to the terminal within the duration of the retransmission timer.
  • the process of the network device starting the retransmission timer is similar to the process of the terminal starting the retransmission timer. Therefore, the corresponding description of the terminal starting the retransmission timer can be referred to and will not be repeated here.
  • the actions of the network device or terminal in the above S701-S703 can be executed by the processor 601 in the communication device 60 shown in Figure 6 calling the application code stored in the memory 603, and the embodiment of the present application does not impose any limitation on this.
  • the terminal can determine the duration of the retransmission timer according to the number of at least one physical shared channel. For example, when the number of at least one physical shared channel is large, the duration of the retransmission timer is determined to be long, and when the number of at least one physical shared channel is small, the duration of the retransmission timer is determined to be short. In this way, the duration of the retransmission timer can be configured more reasonably to improve the performance of data retransmission of at least one physical shared channel.
  • the methods and/or steps implemented by the terminal can also be implemented by components that can be used for the terminal (such as chips or circuits); the methods and/or steps implemented by the network device can also be implemented by components that can be used for the network device (such as chips or circuits).
  • the embodiment of the present application also provides a communication device, which can be a terminal in the above method embodiment, or a device including the above terminal, or a component that can be used for the terminal; or, the communication device can be a network device in the above method embodiment, or a device including the above network device, or a component that can be used for the network device.
  • the above terminal device or network device, etc. includes a hardware structure and/or software module corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.
  • the processing performed by the above terminal is not limited to being performed by only a single network element, and the processing performed by the above network device is not limited to being performed by only a single network element.
  • the processing performed by the network device can be performed by at least one of the CU, DU and remote unit (RU).
  • the embodiment of the present application can divide the functional modules of the terminal or network device according to the above method example.
  • each functional module can be divided according to each function, or two or more functions can be integrated into one processing module.
  • the above integrated module can be implemented in the form of hardware or in the form of software functional modules. It can be understood that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.
  • FIG8 shows a schematic diagram of the structure of a communication device 80.
  • the communication device 80 includes a processing module 801 and a transceiver module 802.
  • the processing module 801 which may also be referred to as a processing unit, is used to perform operations other than transceiver operations, and may be, for example, a processing circuit or a processor.
  • the communication device 80 may further include a storage module (not shown in FIG. 8 ) for storing program instructions and data.
  • the communication device 80 is used to implement the functions of the terminal.
  • the communication device 80 is, for example, the embodiment shown in FIG7 .
  • the transceiver module 802 is used to receive first control information from a network device.
  • the first control information is used to indicate data transmission of at least one physical shared channel.
  • the transceiver module 802 can be used to execute S701.
  • the processing module 801 is used to determine the duration of the retransmission timer according to the number of at least one physical shared channel, the duration of the retransmission timer is the maximum duration of monitoring the second control information, and the second control information is used to schedule data retransmission of at least one physical shared channel.
  • the processing module 801 can be used to execute S702.
  • the processing module 801 is further configured to start a retransmission timer and monitor the second control information within the duration of the retransmission timer through the transceiver module 802.
  • the processing module 801 may be configured to execute S703.
  • the transceiver module 802 is further configured to receive configuration information from a network device, where the configuration information is used to configure multiple candidate durations of a retransmission timer.
  • the processing module 801 is specifically configured to determine, according to the number of at least one physical shared channel, from a plurality of candidate durations, a duration of a retransmission timer corresponding to the number of at least one physical shared channel.
  • the duration of the retransmission timer is greater than the duration of the retransmission timer when the number of at least one physical shared channel is a second value, wherein the first value is greater than the second value.
  • the physical shared channel is a physical uplink shared channel
  • the processing module 801 is specifically used to start the retransmission timer at time a+T1, where a is the time corresponding to the last physical shared channel of at least one physical shared channel, and T1 is the duration configured by the network device.
  • the physical shared channel is a physical uplink shared channel
  • the number of at least one physical shared channel is greater than 1
  • the processing module 801 is specifically used to start the retransmission timer at time b+T2
  • b is the time corresponding to the last physical shared channel actually sent in at least one physical shared channel
  • T2 is the duration configured by the network device.
  • the transceiver module 802 is further configured to send indication information to the network device, where the indication information is used to indicate the last physical shared channel actually sent.
  • the retransmission timer is a retransmission timer corresponding to the last physical shared channel; or, the retransmission timer is a retransmission timer corresponding to at least one physical shared channel; or, the retransmission timer corresponds one-to-one to at least one physical shared channel.
  • the physical shared channel is a physical downlink shared channel
  • the transceiver module 802 is also used to send feedback information to the network device, where the feedback information is used to indicate whether the data transmission on at least one physical shared channel is successful
  • the processing module 801 is specifically used to start the retransmission timer at time c+T3, where c is the time when the feedback information is sent, and T3 is the duration configured by the network device.
  • the communication device 80 is used to implement the function of a network device.
  • the communication device 80 is, for example, the network device described in the embodiment shown in FIG.
  • the transceiver module 802 is used to send first control information to the terminal, where the first control information is used to indicate data transmission of at least one physical shared channel.
  • the transceiver module 802 can be used to execute S701.
  • Processing module 801 is used to determine the duration of a retransmission timer according to the number of at least one physical shared channel, where the duration of the retransmission timer is the maximum duration for the terminal to monitor second control information, and the second control information is used to schedule data retransmission of at least one physical shared channel.
  • the processing module 801 is further configured to start a retransmission timer, and send the second control information to the terminal through the transceiver module 802 within the duration of the retransmission timer.
  • the transceiver module 802 is further configured to send configuration information to the terminal, where the configuration information is used to configure multiple candidate durations of the retransmission timer.
  • the processing module 801 is specifically configured to determine, according to the number of at least one physical shared channel, from a plurality of candidate durations, a duration of a retransmission timer corresponding to the number of at least one physical shared channel.
  • the duration of the retransmission timer is greater than the duration of the retransmission timer when the number of at least one physical shared channel is a second value, wherein the first value is greater than the second value.
  • the physical shared channel is a physical uplink shared channel
  • the processing module 801 is specifically configured to start the retransmission timer at time a+T1, where a is the time corresponding to the last physical shared channel of at least one physical shared channel, and T1 is a first preset duration.
  • the physical shared channel is a physical uplink shared channel
  • the number of at least one physical shared channel is greater than 1
  • the processing module 801 is specifically used to start the retransmission timer at time b+T2
  • b is the time corresponding to the last physical shared channel actually received in at least one physical shared channel
  • T2 is the second preset duration.
  • the transceiver module 802 is further configured to receive indication information from the terminal, where the indication information is used to indicate the last physical shared channel actually received.
  • the retransmission timer is a retransmission timer corresponding to the last physical shared channel; or, the retransmission timer is a retransmission timer corresponding to at least one physical shared channel; or, the retransmission timer corresponds one-to-one to at least one physical shared channel.
  • the physical shared channel is a physical downlink shared channel
  • the transceiver module 802 is also used to receive feedback information from the terminal, and the feedback information is used to indicate whether the data transmission on at least one physical shared channel is successful
  • the processing module 801 is specifically used to start the retransmission timer at time c+T3, where c is the time of receiving the feedback information, and T3 is the third preset duration.
  • the communication device 80 may be in the form shown in Figure 6.
  • the processor 601 in Figure 6 may call the computer-executable instructions stored in the memory 603 to enable the communication device 80 to execute the method described in the above method embodiment.
  • the functions/implementation processes of the processing module 801 and the transceiver module 802 in FIG8 can be implemented by the processor 601 in FIG6 calling the computer execution instructions stored in the memory 603.
  • the functions/implementation processes of the processing module 801 in FIG8 can be implemented by the processor 601 in FIG6 calling the computer execution instructions stored in the memory 603
  • the functions/implementation processes of the transceiver module 802 in FIG8 can be implemented by the communication interface 604 in FIG6.
  • one or more of the above modules or units can be implemented by software, hardware or a combination of the two.
  • the software exists in the form of computer program instructions and is stored in a memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built into an SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • it can further include necessary hardware accelerators, such as field programmable gate arrays (FPGA), PLDs (programmable logic devices), or logic circuits that implement dedicated logic operations.
  • FPGA field programmable gate arrays
  • PLDs programmable logic devices
  • the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.
  • DSP digital signal processing
  • MCU microcontroller unit
  • an artificial intelligence processor an ASIC
  • SoC SoC
  • FPGA field-programmable gate array
  • PLD programmable gate array
  • a dedicated digital circuit a hardware accelerator or a non-integrated discrete device
  • an embodiment of the present application further provides a chip system, including: at least one processor and an interface, the at least one processor is coupled to a memory through the interface, and when the at least one processor executes a computer program or instruction in the memory, the method in any of the above method embodiments is executed.
  • the chip system also includes a memory.
  • the chip system can be composed of chips, or it can include chips and other discrete devices, which is not specifically limited in the embodiments of the present application.
  • an embodiment of the present application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be completed by a computer program to instruct the relevant hardware, and the program can be stored in the above computer-readable storage medium. When the program is executed, it may include the processes of the above method embodiments.
  • the computer-readable storage medium can be an internal storage unit of the communication device of any of the above embodiments, such as a hard disk or memory of the communication device.
  • the above computer-readable storage medium can also be an external storage device of the above communication device, such as a plug-in hard disk equipped on the above communication device, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc.
  • the above computer-readable storage medium can also include both the internal storage unit of the above communication device and an external storage device.
  • the above computer-readable storage medium is used to store the above computer program and other programs and data required by the above communication device.
  • the above computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.
  • the present application also provides a computer program product. All or part of the processes in the above method embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in the above computer program product. When the program is executed, it can include the processes of the above method embodiments.
  • the embodiment of the present application further provides a computer instruction. All or part of the processes in the above method embodiment can be completed by computer instructions to instruct related hardware (such as a computer, processor, terminal or network device, etc.).
  • the program can be stored in the above computer-readable storage medium or in the above computer program product.
  • an embodiment of the present application further provides a communication system, including: the network device and terminal in the above embodiment.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be 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 be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

Landscapes

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

Abstract

控制信息的监听方法及装置，涉及无线通信领域。在该控制信息的监听方法中，终端可以接收来自网络设备的用于指示至少一个物理共享信道的数据传输，根据至少一个物理共享信道的数量确定重传定时器的时长。其中，重传定时器的时长为终端监听第二控制信息的最大时长，第二控制信息用于调度至少一个物理共享信道的数据重传。这样，重传定时器的时长可以根据至少一个物理共享信道的数量调整，使得重传定时器的时长被配置得更为合理，以提高至少一个物理共享信道的数据重传的性能。

Description

控制信息的监听方法及装置
“本申请要求于2022年9月28日提交国家知识产权局、申请号为202211192583.3、发明名称为“控制信息的监听方法及装置”的专利申请的优先权，其全部内容通过引用结合在本申请中”。
技术领域
本申请涉及无线通信领域，尤其涉及控制信息的监听方法。
背景技术
在通信系统中，终端接收指示下行传输的物理下行控制信道(physical downlink control channel，PDCCH)或者接收半持续调度(semi-persistent scheduling，SPS)的物理下行共享信道(physical downlink shared channel，PDSCH)，并且终端接收数据失败，会启动重传定时器，以在重传定时器运行期间接收来自网络设备的重传调度信息。类似的，终端接收到指示上行传输的PDCCH，或者接收到配置授权(configured grant，CG)的物理上行共享信道(physical uplink shared channel，PUSCH)，并完成PUSCH的传输之后，会启动重传定时器，以在重传定时器运行期间接收来自网络设备的重传调度信息。然而，目前重传定时器的配置并不合理，影响重传性能。
发明内容
本申请实施例提供通信方法及装置，可以根据至少一个物理共享信道的数量调整重传定时器的时长，使得重传定时器的时长被配置得更为合理，以提高至少一个物理共享信道的数据重传的性能。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种通信方法，该方法可以由终端执行；或者，也可以由应用于终端中的模块，例如芯片、芯片系统或电路执行，还可以由能实现全部或部分终端功能的逻辑模块或软件实现，对此不作限定。为了便于描述，下面以由终端执行为例进行说明。该方法包括：接收来自网络设备的用于指示至少一个物理共享信道的数据传输的第一控制信息；根据该至少一个物理共享信道的数量确定重传定时器的时长，该重传定时器的时长为监听第二控制信息的最大时长，该第二控制信息用于调度该至少一个物理共享信道的数据重传；启动该重传定时器，并在该重传定时器的时长内监听该第二控制信息。
基于上述第一方面提供的方法，终端可以根据至少一个物理共享信道的数量调整重传定时器的时长，使得重传定时器的时长更为合理，进而提高至少一个物理共享信道的数据重传的性能。
在一种可能的实现方式中，该方法还包括：接收来自该网络设备的配置信息，该配置信息用于配置该重传定时器的多个候选时长。
基于上述可能的实现方式，终端可以根据至少一个物理共享信道的数量，在网络设备配置的多个候选时长中确定重传定时器的时长。
在一种可能的实现方式中，根据该至少一个物理共享信道的数量确定重传定时器的时长，包括：根据该至少一个物理共享信道的数量在该多个候选时长中，确定与该至少一个物理共享信道的数量对应的重传定时器的时长。
基于上述可能的实现方式，终端可以将多个候选时长中，与至少一个物理共享信道的数量对应的候选时长确定为重传定时器的时长。
在一种可能的实现方式中，至少一个物理共享信道的数量为第一数值的情况下，重传定时器的时长大于至少一个物理共享信道的数量为第二数值的情况下，重传定时器的时长，其中，该第一数值大于该第二数值。
基于上述可能的实现方式，若至少一个物理共享信道的数量较大，终端确定的重传定时器的时长较大，至少一个物理共享信道的数量较小，终端确定的重传定时器的时长较短。可以理解的，至少一个物理共享信道的数量越多，进行数据重传的可能性就越大，终端可能要被调度多次重传。 此时，终端为重传定时器确定一个较大的时长，可以避免至少一个物理共享信道中的某些信道的重传来不及调度，影响重传性能。至少一个物理共享信道的数量越少，进行数据重传的可能性就越小，终端可能要被调度重传的次数越少。此时，终端为重传定时器确定一个较小的时长，在保证重传性能的情况下，还能降低终端的功耗可。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，启动该重传定时器，包括：在a+T1时刻启动该重传定时器，该a为该至少一个物理共享信道的最后一个物理共享信道对应的时刻，该T1为该网络设备配置的时长。
基于上述可能的实现方式，终端可以在发送至少一个物理共享信道的最后一个物理共享信道之后启动重传定时器，缩短了终端处于激活状态的时间，进而降低了终端的功耗。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，该至少一个物理共享信道的数量大于1，该启动该重传定时器，包括：在b+T2时刻启动该重传定时器，该b为该至少一个物理共享信道中实际发送的最后一个物理共享信道对应的时刻，该T2为该网络设备配置的时长。
基于上述可能的实现方式，终端可以在实际发送的最后一个物理共享信道的时域位置之后的时刻启动重传定时器，缩短了终端处于激活状态的时间，进而降低了终端的功耗。
在一种可能的实现方式中，该方法还包括：向该网络设备发送指示信息，该指示信息用于指示该实际发送的最后一个物理共享信道。
基于上述可能的实现方式，终端可以向网络设备指示实际发送的最后一个物理共享信道，以便网络设备确定实际发送的最后一个物理共享信道，进而确定何时向终端发送重传指示信息。
在一种可能的实现方式中，该重传定时器为该最后一个物理共享信道对应的重传定时器；或者，该重传定时器为该至少一个物理共享信道对应的重传定时器；或者，该重传定时器与该至少一个物理共享信道一一对应。
基于上述可能的实现方式，在重传定时器为该最后一个物理共享信道对应的重传定时器的情况下，终端可以维护一个重传定时器，降低了终端的复杂度。在重传定时器为该至少一个物理共享信道对应的重传定时器的情况下，终端无论接收到哪个物理共享信道对应的第二控制信息，都不停止重传定时器，直至重传定时器超时，以使得终端来得及接收到所有需要重传的物理共享信道对应的第二控制信息。在重传定时器与该至少一个物理共享信道一一对应的情况下，终端接收到哪个物理共享信道对应的第二控制信息，终端就停止哪个物理共享信道对应的重传定时器，既来得及接收到所有需要重传的物理共享信道对应的第二控制信息，又不会在至少一个物理共享信道对应的第二控制信息都接收到的情况下，继续维护重传定时器，能够降低终端的功耗。
在一种可能的实现方式中，该物理共享信道为物理下行共享信道，该方法还包括：向该网络设备发送反馈信息，该反馈信息用于指示该至少一个物理共享信道上的数据传输是否成功；启动该重传定时器，包括：在c+T3时刻启动该重传定时器，该c为发送该反馈信息的时刻，该T3为该网络设备配置的时长。
基于上述可能的实现方式，终端可以在发送反馈信息后启动重传定时器。
第二方面，提供了一种通信方法，该方法可以由网络设备执行；或者，也可以由应用于网络设备中的模块，例如芯片、芯片系统或电路执行，还可以由能实现全部或部分网络设备功能的逻辑模块或软件实现，对此不作限定。为了便于描述，下面以由网络设备执行为例进行说明。该方法包括：向终端发送第一控制信息，该第一控制信息用于指示至少一个物理共享信道的数据传输；根据该至少一个物理共享信道的数量确定重传定时器的时长，该重传定时器的时长为该终端监听第二控制信息的最大时长，该第二控制信息用于调度该至少一个物理共享信道的数据重传；启动该重传定时器，并在该重传定时器的时长内向该终端发送该第二控制信息。
基于上述第二方面提供的方法，网络设备可以根据至少一个物理共享信道的数量调整重传定时器的时长，使得重传定时器的时长更为合理，进而提高至少一个物理共享信道的数据重传的性能。
在一种可能的实现方式中，该方法还包括：向该终端发送配置信息，该配置信息用于配置该重传定时器的多个候选时长。
基于上述可能的实现方式，网络设备可以为终端配置重传定时器的多个候选时长，以便终端 在多个候选时长中、根据至少一个物理共享信道的数量确定重传定时器的时长。
在一种可能的实现方式中，根据该至少一个物理共享信道的数量确定重传定时器的时长，包括：根据该至少一个物理共享信道的数量在该多个候选时长中，确定与该至少一个物理共享信道的数量对应的重传定时器的时长。
基于上述可能的实现方式，网络设备可以将多个候选时长中，与至少一个物理共享信道的数量对应的候选时长确定为重传定时器的时长。
在一种可能的实现方式中，该至少一个物理共享信道的数量为第一数值的情况下，该重传定时器的时长大于该至少一个物理共享信道的数量为第二数值的情况下，该重传定时器的时长，其中，该第一数值大于该第二数值。
基于上述可能的实现方式，若至少一个物理共享信道的数量较大，网络设备确定的重传定时器的时长较大，至少一个物理共享信道的数量较小，网络设备确定的重传定时器的时长较短。可以理解的，至少一个物理共享信道的数量越多，进行数据重传的可能性就越大，终端可能要被调度多次重传。此时，网络设备为重传定时器确定一个较大的时长，可以避免至少一个物理共享信道中的某些信道的重传来不及调度，影响重传性能。至少一个物理共享信道的数量越少，进行数据重传的可能性就越小，终端可能要被调度重传的次数越少。此时，网络设备为重传定时器确定一个较小的时长，在保证重传性能的情况下，还能降低终端的功耗可。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，启动该重传定时器，包括：在a+T1时刻启动该重传定时器，该a为该至少一个物理共享信道的最后一个物理共享信道对应的时刻，该T1为第一预设时长。
基于上述可能的实现方式，网络设备可以在发送至少一个物理共享信道的最后一个物理共享信道之后启动重传定时器，缩短了终端处于激活状态的时间，进而降低了终端的功耗。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，该至少一个物理共享信道的数量大于1，启动该重传定时器，包括：在b+T2时刻启动该重传定时器，该b为该至少一个物理共享信道中实际接收的最后一个物理共享信道对应的时刻，该T2为第二预设时长。
基于上述可能的实现方式，网络设备可以在实际发送的最后一个物理共享信道的时域位置之后的时刻启动重传定时器，缩短了终端处于激活状态的时间，进而降低了终端的功耗。
在一种可能的实现方式中，该方法还包括：接收来自该终端的指示信息，该指示信息用于指示该实际接收的最后一个物理共享信道。
基于上述可能的实现方式，网络设备可以根据指示信息确定实际接收的最后一个物理共享信道，进而确定何时向终端发送重传指示信息。
在一种可能的实现方式中，该重传定时器为该最后一个物理共享信道对应的重传定时器；或者，该重传定时器为该至少一个物理共享信道对应的重传定时器；或者，该重传定时器与该至少一个物理共享信道一一对应。
基于上述可能的实现方式，在重传定时器为该最后一个物理共享信道对应的重传定时器的情况下，网络设备可以维护一个重传定时器，降低了网络设备的复杂度。在重传定时器为该至少一个物理共享信道对应的重传定时器的情况下，网络设备无论发送了哪个物理共享信道对应的第二控制信息，都不停止重传定时器，直至重传定时器超时，以使得网络设备来得及发送所有需要重传的物理共享信道对应的第二控制信息。在重传定时器与该至少一个物理共享信道一一对应的情况下，网络设备发送了哪个物理共享信道对应的第二控制信息，网络设备就停止哪个物理共享信道对应的重传定时器，既来得及发送所有需要重传的物理共享信道对应的第二控制信息，又不会在至少一个物理共享信道对应的第二控制信息都接收到的情况下，继续维护重传定时器。
在一种可能的实现方式中，该物理共享信道为物理下行共享信道，该方法还包括：接收来自该终端的反馈信息，该反馈信息用于指示该至少一个物理共享信道上的数据传输是否成功；启动该重传定时器，包括：在c+T3时刻启动该重传定时器，该c为接收该反馈信息的时刻，该T3为第三预设时长。
基于上述可能的实现方式，网络设备可以在接收到反馈信息后启动重传定时器。
第三方面，提供了一种通信装置用于实现上述方法。该通信装置可以为上述第一方面中的终 端，或者包含上述终端的装置，或者为上述第一方面中的终端中的模块，如芯片、芯片系统或电路，或者为能实现部分或全部终端功能的逻辑模块或软件实现；或者，该通信装置可以为上述第二方面中的网络设备，或者包含上述网络设备的装置，或者为上述第二方面中的网络设备中的模块，如芯片、芯片系统或电路，或者为能实现部分或全部网络设备功能的逻辑模块或软件实现。该通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
结合上述第三方面，在一种可能的实现方式中，该通信装置可以包括收发模块和处理模块。该收发模块，也可以称为收发单元，用以实现上述任一方面及其任意可能的实现方式中的发送和/或接收功能。该收发模块可以由收发电路，收发机，收发器或者通信接口构成。该处理模块，可以用于实现上述任一方面及其任意可能的实现方式中的处理功能。该处理模块例如可以为处理器。
结合上述第三方面，在一种可能的实现方式中，收发模块包括发送模块和接收模块，分别用于实现上述任一方面及其任意可能的实现方式中的发送和接收功能。
第四方面，提供了一种通信装置，包括：处理器；该处理器用于与存储器耦合，并读取存储器中的指令之后，根据该指令执行如上述任一方面所述的方法。该通信装置可以为上述第一方面中的终端，或者包含上述终端的装置，或者为上述第一方面中的终端中的模块，如芯片、芯片系统或电路，或者为能实现部分或全部终端功能的逻辑模块或软件实现；或者，该通信装置可以为上述第二方面中的网络设备，或者包含上述网络设备的装置，或者为上述第二方面中的网络设备中的模块，如芯片、芯片系统或电路，或者为能实现部分或全部网络设备功能的逻辑模块或软件实现。
结合上述第四方面，在一种可能的实现方式中，该通信装置还包括存储器，该存储器，用于保存必要的程序指令和数据。
结合上述第四方面，在一种可能的实现方式中，该通信装置为芯片或芯片系统。可选的，该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
第五方面，提供了一种通信装置，包括：处理器和接口电路；接口电路，用于接收计算机程序或指令并传输至处理器；处理器用于执行所述计算机程序或指令，以使该通信装置执执行如上述任一方面所述的方法。该通信装置可以为上述第一方面中的终端，或者包含上述终端的装置，或者为上述第一方面中的终端中的模块，如芯片、芯片系统或电路，或者为能实现部分或全部终端功能的逻辑模块或软件实现；或者，该通信装置可以为上述第二方面中的网络设备，或者包含上述网络设备的装置，或者为上述第二方面中的网络设备中的模块，如芯片、芯片系统或电路，或者为能实现部分或全部网络设备功能的逻辑模块或软件实现。
结合上述第五方面，在一种可能的实现方式中，该通信装置为芯片或芯片系统。可选的，该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
第六方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
第七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
第八方面，提供了一种通信系统，该通信系统包括用于执行上述第一方面所述的方法的终端、以及用于执行上述第二方面所述的方法的网络设备。
第九方面，提供了一种通信系统，该通信系统包括终端和网络设备，该网络设备，用于向该终端发送用于指示至少一个物理共享信道的数据传输的第一控制信息；该终端，用于接收来自网络设备的第一控制信息；该终端，还用于根据该至少一个物理共享信道的数量确定重传定时器的时长，该重传定时器的时长为监听第二控制信息的最大时长，该第二控制信息用于调度该至少一个物理共享信道的数据重传；该终端，还用于启动该重传定时器，并在该重传定时器的时长内监听该第二控制信息。
在一种可能的实现方式中，该网络设备，还用于向该终端发送用于配置该重传定时器的多个候选时长的配置信息；该终端，还用于接收来自该网络设备的配置信息。
在一种可能的实现方式中，该终端，还用于根据该至少一个物理共享信道的数量确定重传定时器的时长，包括：该终端根据该至少一个物理共享信道的数量在该多个候选时长中，确定与该至少一个物理共享信道的数量对应的重传定时器的时长。
在一种可能的实现方式中，该至少一个物理共享信道的数量为第一数值的情况下，该重传定时器的时长大于该至少一个物理共享信道的数量为第二数值的情况下，该重传定时器的时长，其中，该第一数值大于该第二数值。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，该终端，还用于启动该重传定时器，包括：该终端在a+T1时刻启动该重传定时器，该a为该至少一个物理共享信道的最后一个物理共享信道对应的时刻，该T1为该网络设备配置的时长。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，该至少一个物理共享信道的数量大于1，该终端，还用于启动该重传定时器，包括：该终端在b+T2时刻启动该重传定时器，该b为该至少一个物理共享信道中实际发送的最后一个物理共享信道对应的时刻，该T2为该网络设备配置的时长。
在一种可能的实现方式中，该终端，还用于向该网络设备发送用于指示该实际发送的最后一个物理共享信道的指示信息；该网络设备，还用于接收来自该终端的该指示信息。
在一种可能的实现方式中，该重传定时器为该最后一个物理共享信道对应的重传定时器；或者，该重传定时器为该至少一个物理共享信道对应的重传定时器；或者，该重传定时器与该至少一个物理共享信道一一对应。
在一种可能的实现方式中，该物理共享信道为物理下行共享信道，该终端，还用于向该网络设备发送用于指示该至少一个物理共享信道上的数据传输是否成功的反馈信息；该网络设备，还用于接收来自该终端的该反馈信息；该终端，还用于启动该重传定时器，包括：该终端在c+T3时刻启动该重传定时器，该c为发送该反馈信息的时刻，该T3为该网络设备配置的时长。
第十方面，提供了一种通信方法，该方法可以由终端/网络设备执行；或者，也可以由应用于终端/网络设备中的模块，例如芯片、芯片系统或电路执行，还可以由能实现全部或部分终端/网络设备功能的逻辑模块或软件实现，对此不作限定。这里以网络设备和终端执行该方法作为示例进行介绍。该通信方法包括：网络设备向终端发送用于指示至少一个物理共享信道的数据传输的第一控制信息；该终端接收来自网络设备的第一控制信息；该终端根据该至少一个物理共享信道的数量确定重传定时器的时长，该重传定时器的时长为监听第二控制信息的最大时长，该第二控制信息用于调度该至少一个物理共享信道的数据重传；该终端启动该重传定时器，并在该重传定时器的时长内监听该第二控制信息。
在一种可能的实现方式中，该网络设备向该终端发送用于配置该重传定时器的多个候选时长的配置信息；该终端接收来自该网络设备的配置信息。
在一种可能的实现方式中，该终端根据该至少一个物理共享信道的数量确定重传定时器的时长，包括：该终端根据该至少一个物理共享信道的数量在该多个候选时长中，确定与该至少一个物理共享信道的数量对应的重传定时器的时长。
在一种可能的实现方式中，该至少一个物理共享信道的数量为第一数值的情况下，该重传定时器的时长大于该至少一个物理共享信道的数量为第二数值的情况下，该重传定时器的时长，其中，该第一数值大于该第二数值。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，该终端启动该重传定时器，包括：该终端在a+T1时刻启动该重传定时器，该a为该至少一个物理共享信道的最后一个物理共享信道对应的时刻，该T1为该网络设备配置的时长。
在一种可能的实现方式中，该物理共享信道为物理上行共享信道，该至少一个物理共享信道的数量大于1，该终端启动该重传定时器，包括：该终端在b+T2时刻启动该重传定时器，该b为该至少一个物理共享信道中实际发送的最后一个物理共享信道对应的时刻，该T2为该网络设备配置的时长。
在一种可能的实现方式中，该终端向该网络设备发送用于指示该实际发送的最后一个物理共享信道的指示信息；该网络设备接收来自该终端的该指示信息。
在一种可能的实现方式中，该重传定时器为该最后一个物理共享信道对应的重传定时器；或者，该重传定时器为该至少一个物理共享信道对应的重传定时器；或者，该重传定时器与该至少一个物理共享信道一一对应。
在一种可能的实现方式中，该物理共享信道为物理下行共享信道，该终端向该网络设备发送用于指示该至少一个物理共享信道上的数据传输是否成功的反馈信息；该网络设备接收来自该终端的该反馈信息；该终端启动该重传定时器，包括：该终端在c+T3时刻启动该重传定时器，该c为发送该反馈信息的时刻，该T3为该网络设备配置的时长。
其中，第三方面至第十方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面至第二方面中任一方面或任一方面中不同可能的实现方式所带来的技术效果，此处不再赘述。
可以理解的是，在方案不矛盾的前提下，上述各个方面中的方案均可以结合。
附图说明
图1为非连续接收(discontinuous reception，DRX)的示意图；
图2为drx-InactivityTimer的示意图；
图3A为drx-HARQ-RTT-TimerDL和drx-RetransmissionTimerDL的示意图；
图3B为drx-HARQ-RTT-TimerUL和drx-RetransmissionTimerUL的示意图；
图4A为下行控制信息(downlink control information，DCI)调度PUSCH的示意图；
图4B为DCI调度PDSCH的示意图；
图5为本申请实施例提供的通信系统架构示意图；
图6为本申请实施例提供的通信装置的硬件结构示意图；
图7为本申请实施例提供的通信方法的流程示意图；
图8为本申请实施例提供的通信装置的结构示意图。
具体实施方式
在介绍本申请实施例之前，对本申请实施例涉及的相关技术术语进行解释说明。可以理解的是，这些解释说明是为了让本申请实施例更容易被理解，而不应该视为对本申请实施例所要求的保护范围的限定。
1、DRX
第五代(5th generation，5G)新空口(new radio，NR)标准引入了DRX技术。DRX技术可以用于省电(power saving)。DRX技术的基本机制是给终端配置DRX周期(DRX cycle)。如图1所示，DRX周期包括激活期(on duration)和休眠期(opportunity for DRX)。终端在激活期处于激活状态，能够正常收发数据，在休眠期有机会进入休眠状态，不接收PDCCH，以减少功耗。应理解，终端进入休眠状态后，虽然不接收PDCCH，但是可以接收来自其它物理信道的数据，如PDSCH或确认信号(acknowledge，ACK)等。例如：在SPS中，处于休眠状态的终端可以接收周期性配置的下行子帧上发送的PDSCH。
2、DRX去激活定时器(drx-InactivityTimer)
若终端在激活期接收到PDCCH，则表示终端在接下来一段时间可能要收发数据，因此终端可以启动或重启drx-InactivityTimer。在drx-InactivityTimer期间终端处于激活状态，继续监听PDCCH。如图2所示，若终端在t1时间段内接收到PDCCH，则终端启动时长为t2的drx-InactivityTimer。终端在t1和t2时间段内处于激活状态，能够监听PDCCH。
3、DRX混合自动重传请求(hybrid automatic repeat request，HARQ)往返时间(round-trip time，RTT)定时器(drx-HARQ-RTT-Timer)和DRX重传定时器(drx-RetransmissionTimer)
本申请实施例中，drx-HARQ-RTT-Timer可以根据数据的传输方向分为DRX HARQ RTT上行链路(up link，UL)定时器(drx-HARQ-RTT-TimerUL)和DRX HARQ RTT下行链路(down link，DL)定时器(drx-HARQ-RTT-TimerDL)。类似的，drx-RetransmissionTimer也可以根据数据的传输方向分为DRX重传上行定时器(drx-RetransmissionTimerUL)和DRX重传下行定时器(drx-RetransmissionTimerDL)。
首先，介绍drx-HARQ-RTT-TimerDL和drx-RetransmissionTimerDL。
如图3A所示，如果终端收到一个指示下行传输的PDCCH，或者收到SPS的PDSCH(此时没有伴随着传输PDCCH)，并且终端的数据接收失败，网络设备就需要重传数据。在反馈HARQ否定确认(not-acknowledgement，NACK)消息之后，终端可以为相应的HARQ进程启动drx-HARQ-RTT-TimerDL。drx-HARQ-RTT-TimerDL的时长可以用于表示终端期望收到用于HARQ重传指示信息的最小时长，即在drx-HARQ-RTT-TimerDL期间，终端不期望接收DL重传指示信息。当drx-HARQ-RTT-TimerDL超时，终端可以启动drx-RetransmissionTimerDL，drx-RetransmissionTimerDL的时长可以表示终端接收到DL重传指示信息的最大时长，即在drx-RetransmissionTimerDL期间，终端处于激活状态，可以接收PDCCH和/或PDSCH，如接收DL重传指示信息。
下面介绍drx-HARQ-RTT-TimerUL和drx-RetransmissionTimerUL。
如图3B所示，如果终端收到一个指示上行传输的PDCCH或者收到CG的PUSCH(此时没有伴随着传输PDCCH)，并且完成PUSCH传输之后，终端为相应的HARQ进程启动drx-HARQ-RTT-TimerUL，drx-HARQ-RTT-TimerUL的时长可以表示终端期望收到用于HARQ重传指示信息的最小时长，即在drx-HARQ-RTT-TimerUL期间，终端不期望接收UL重传指示信息。当drx-HARQ-RTT-TimerUL超时，终端启动drx-RetransmissionTimerUL，drx-RetransmissionTimerUL的时长可以表示终端接收到UL重传指示信息的最大时长。在drx-RetransmissionTimerUL期间，终端处于激活状态，接收PDCCH指示PUSCH重传。
在通信系统中，提出了一个DCI调度多个PDSCH或者多个PUSCH的方案。这样，可以避免终端频繁监听DCI，从而降低终端的功耗和复杂度。
对于一个DCI调度多个PUSCH的情况，如果终端配置了DRX，那么每个PUSCH传输完成后，终端会启动drx-HARQ-RTT-TimerUL。在drx-HARQ-RTT-TimerUL超时后，终端会启动drx-RetransmissionTimerUL，并在drx-RetransmissionTimerUL运行期间，持续监听PDCCH。具体的，可以如图4A所示。图4A中，h1表示DCI调度的第一个PUSCH对应的drx-HARQ-RTT-TimerUL的时长，r1表示DCI调度的第一个PUSCH对应的drx-RetransmissionTimerUL的时长。h2表示DCI调度的第二个PUSCH对应的drx-HARQ-RTT-TimerUL的时长，r2表示DCI调度的第二个PUSCH对应的drx-RetransmissionTimerUL的时长。h3表示DCI调度的第三个PUSCH对应的drx-HARQ-RTT-TimerUL的时长，r3表示DCI调度的第三个PUSCH对应的drx-RetransmissionTimerUL的时长。
对于一个DCI调度多个PDSCH，如果终端配置了DRX，那么多个PDSCH的HARQ-NACK信息在同一个PUCCH上反馈。终端反馈了HARQ-NACK信息后，会启动HARQ进程对应的drx-HARQ-RTT-TimerDL。在drx-HARQ-RTT-TimerDL超时后，终端会启动drx-RetransmissionTimerDL，即多个PDSCH对应的drx-HARQ-RTT-TimerDL在时域上是交叠的，多个PDSCH对应的drx-RetransmissionTimerDL在时域上也是交叠的。具体的，可以如图4B所示。图4B中，h表示DCI调度的多个PDSCH对应的drx-HARQ-RTT-TimerUL的时长，r表示DCI调度的多个PDSCH对应的drx-RetransmissionTimerUL的时长。
下面结合附图对本申请实施例的实施方式进行详细描述。
本申请实施例提供的方法可用于各种通信系统。例如该通信系统可以为长期演进(long term evolution，LTE)系统、5G通信系统、Wi-Fi系统、第三代合作伙伴计划(3rd generation partnership project，3GPP)相关的通信系统、未来演进的通信系统(如：第六代(6th generation，6G)通信系统等)、或多种系统融合的系统等，不予限制。下面以图5所示通信系统50为例，对本申请实施例提供的方法进行描述。图5仅为示意图，并不构成对本申请提供的技术方案的适用场景的限定。
如图5所示，为本申请实施例提供的通信系统50的架构示意图。图5中，通信系统50可以包括一个或多个网络设备501(仅示出了1个)以及可以与网络设备501进行通信的终端502-终端504。
在图5中，网络设备可以为终端提供无线接入服务。具体来说，每个网络设备都对应一个服 务覆盖区域，进入该区域的终端可通过Uu口与网络设备通信，以此来接收网络设备提供的无线接入服务。可选地，该服务覆盖区域可以包括一个或多个小区。终端与网络设备之间可以通过Uu口链路通信。其中，Uu口链路可以根据其上传输的数据的方向分为UL和DL。UL上可以传输从终端向网络设备发送的上行数据，DL上可以传输从网络设备向终端传输的下行数据。例如：图5中，终端503位于网络设备501的覆盖区域内，网络设备501可以通过DL向终端503发送下行数据，终端503可通过UL向网络设备501发送上行数据。
本申请实施例中的网络设备，例如：网络设备501可以是任意一种具有无线收发功能的设备。包括但不限于：LTE中的演进型基站(NodeB或eNB或e-NodeB，evolutional Node B)，NR中的基站(gNodeB或gNB)或收发点(transmission receiving point/transmission reception point，TRP)，3GPP后续演进的基站，Wi-Fi系统中的接入节点，无线中继节点，无线回传节点等。基站可以是：宏基站，微基站，微微基站，小站，中继站，或，气球站等。多个基站可以支持上述提及的同一种技术的网络，也可以支持上述提及的不同技术的网络。基站可以包含一个或多个共站或非共站的TRP。网络设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器。网络设备还可以是集中单元(centralized unit，CU)，和/或，分布单元(distributed unit，DU)。网络设备还可以是服务器，可穿戴设备，机器通信设备、或车载设备等。以下以网络设备为基站为例进行说明。所述多个网络设备可以为同一类型的基站，也可以为不同类型的基站。基站可以与终端进行通信，也可以通过中继站与终端进行通信。终端可以与不同技术的多个基站进行通信，例如，终端可以与支持LTE网络的基站通信，也可以与支持5G网络的基站通信，还可以支持与LTE网络的基站以及5G网络的基站的双连接。本申请实施例中，用于实现网络设备的功能的装置可以是网络设备；也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中或者和网络设备匹配使用。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的方法中，以用于实现网络设备的功能的装置是网络设备为例，描述本申请实施例提供的方法。
本申请实施例中的终端，例如：终端502、终端503或终端504是一种具有无线收发功能的设备。终端可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。终端还可以称为终端设备，终端设备可以是用户设备(user equipment，UE)，其中，UE包括具有无线通信功能的手持式设备、车载设备、可穿戴设备或计算设备。示例性地，UE可以是手机(mobile phone)、平板电脑或带无线收发功能的电脑。终端设备还可以是工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(smart city)中的无线终端、或智慧家庭(smart home)中的无线终端等等。本申请实施例中，用于实现终端的功能的装置可以是终端；也可以是能够支持终端实现该功能的装置，例如芯片系统，该装置可以被安装在终端中或者和终端匹配使用。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的方法中，以用于实现终端的功能的装置是终端为例，描述本申请实施例提供的方法。
作为示例而非限定，在本申请中，终端可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。例如，可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能的设备。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能的设备，例如：智能手表等，以及包括只专注于某一类应用功能，需要和其它设备如智能手机配合使用的设备，如各类进行体征监测的智能手环、智能首饰等。
在本申请中，终端可以是物联网(internet of things，IoT)系统中的终端，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。本申请中的终端可以是机器类型通信(machine type communication，MTC)中的终端。本申请的终端可以是作为一个或多个部件或者单元而内置于车辆的车载模块、车载模组、车载部件、车载芯片或者车载单元，车辆通过内置的所述车载模块、车载模组、车载部件、车载芯片或者车载单元可以实施本申请的方法。
可选的，本申请实施例提供的方法可应用于实时性强、数据容量要求大的多媒体业务，如视频传输、云游戏(cloud gaming，CG)和扩展现实(extended reality，XR)等业务中。其中XR包括虚拟现实(virtual reality，VR)和增强现实(augmented reality，AR)。因此，本申请实施例中的终端还可以是头戴式显示器(head mounted display，HMD)或者智能眼镜(如VR眼镜、AR眼镜)等，不予限制。
图5所示的通信系统50仅用于举例，并非用于限制本申请的技术方案。本领域的技术人员应当明白，在具体实现过程中，通信系统50还可以包括其他设备，同时也可根据具体需要来确定网络设备和终端的数量，不予限制。
可选的，本申请实施例图5中的各网元或设备(例如网络设备501、终端502、终端503或终端504)也可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例图5中的各网元或设备(例如网络设备501、终端502、终端503或终端504)的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者硬件与软件的结合，或者平台(例如，云平台)上实例化的虚拟化功能。
在具体实现时，图5所示的各网元或设备(例如网络设备501、终端502、终端503或终端504等)都可以采用图6所示的组成结构，或者包括图6所示的部件。图6所示为可适用于本申请实施例的通信装置的硬件结构示意图。该通信装置60包括至少一个处理器601和至少一个通信接口604，用于实现本申请实施例提供的方法。该通信装置60还可以包括通信线路602和存储器603。
处理器601可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路602可包括一通路，在上述组件之间传送信息，例如总线。
通信接口604，用于与其他设备或通信网络通信。通信接口604可以是任何收发器一类的装置，如可以是以太网接口、无线接入网(radio access network，RAN)接口、无线局域网(wireless local area networks，WLAN)接口、收发器、管脚、总线、或收发电路等。
存储器603可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路602与处理器601相耦合。存储器603也可以和处理器601集成在一起。本申请实施例提供的存储器通常可以具有非易失性。
其中，存储器603用于存储执行本申请实施例提供的方案所涉及的计算机执行指令，并由处理器601来控制执行。处理器601用于执行存储器603中存储的计算机执行指令，从而实现本申请实施例提供的方法。或者，可选的，本申请实施例中，也可以是处理器601执行本申请下述实施例提供的方法中的处理相关的功能，通信接口604负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。
作为一种实施例，处理器601可以包括一个或多个CPU，例如图6中的CPU0和CPU1。
作为一种实施例，通信装置60可以包括多个处理器，例如图6中的处理器601和处理器607。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
作为一种实施例，通信装置60还可以包括输出设备605和/或输入设备606。输出设备605和处理器601耦合，可以以多种方式来显示信息。例如，输出设备605可以是液晶显示器(liquid crystal display，LCD)，发光二极管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备606和处理器601耦合，可以以多种方式接收用户的输入。例如，输入设备606可以是鼠标、键盘、触摸屏设备或传感设备等。
可以理解的，图6中示出的组成结构并不构成对该通信装置的限定，除图6所示部件之外，该通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
下面将结合附图，对本申请实施例提供的方法进行描述。下述实施例中的各网元可以具备图6所示部件，不予赘述。
可以理解的是，本申请实施例中，“传输”可以根据具体的上下文理解为发送和/或接收。“传输”可以是名词，也可以是动词。在不强调动作的执行主体时，常常用“传输”代替发送和/或接收。例如，短语“传输PUSCH”，从终端的角度来看，可以理解为“发送PUSCH”，而从基站的角度来看，可以理解为“接收PUSCH”。另外，需要指出的是“传输PUSCH/PDSCH”，本领域技术人员可以理解为“传输承载在PUSCH/PDSCH中的信息”。
可以理解的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
可以理解的是，在本申请实施例中，“/”可以表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；“和/或”可以用于描述关联对象存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。此外，类似于“A、B和C中的至少一项”或“A、B或C中的至少一项”的表述通常用于表示如下中任一项：单独存在A；单独存在B；单独存在C；同时存在A和B；同时存在A和C；同时存在B和C；同时存在A、B和C。以上是以A、B和C共三个元素进行举例来说明该项目的可选用条目，当表述中具有更多元素时，该表述的含义可以按照前述规则获得。
为了便于描述本申请实施例的技术方案，在本申请实施例中，可以采用“第一”、“第二”等字样对功能相同或相似的技术特征进行区分。该“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。在本申请实施例中，“示例性的”或者“例如”等词用于表示例子、例证或说明，被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
可以理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。可以理解，在本申请的各种实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
可以理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下会做出相应的处理，并非是限定时间，且也不要求实现时一定要有判断的动作，也不意味着存在其它限定。
本申请中的“同时”可以理解为在相同的时间点，也可以理解为在一段时间段内，还可以理解为在同一个周期内。
可以理解，本申请实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，比如其当前所基于的方案，而独立实施，解决相应的技术问题，达到相应的效果，也可以在某些场景下，依据需求与其他特征进行结合。相应的，本申请实施例中给出的装置也可以相应的实现这些特征或功能，在此不予赘述。
可以理解的，本申请实施例中同一个步骤或者具有相同功能的步骤或者技术特征在不同实施 例之间可以互相参考借鉴。
可以理解的，本申请实施例中，终端和/或网络设备可以执行本申请实施例中的部分或全部步骤，这些步骤仅是示例，本申请实施例还可以执行其它步骤或者各种步骤的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部步骤。
如图7所示，为本申请实施例提供的一种通信方法，图7中以网络设备和终端作为该交互示意的执行主体为例来示意该方法，但本申请并不限制该交互示意的执行主体。例如，图7中的网络设备也可以是支持该网络设备实现该方法的芯片、芯片系统、或处理器，还可以是能实现全部或部分网络设备功能的逻辑模块或软件；图7中的终端也可以是支持该终端实现该方法的芯片、芯片系统、或处理器，还可以是能实现全部或部分终端功能的逻辑模块或软件。该通信方法可以包括如下步骤：
S701：网络设备向终端发送第一控制信息。相应的，终端接收来自网络设备的第一控制信息。
其中，网络设备可以是图5所示的通信系统50中的网络设备501。终端可以是图5所示通信系统50中的任意一个终端，例如为终端502。
本申请实施例中，第一控制信息可以用于指示至少一个物理共享信道的数据传输。其中，物理共享信道可以是PUSCH或者PDSCH。
本申请实施例中，第一控制信息指示至少一个PUSCH的数据传输可以理解为第一控制信息调度至少一个PUSCH。第一控制信息指示至少一个PDSCH的数据传输可以理解为第一控制信息调度至少一个PDSCH。
一种可能的设计，第一控制信息为DCI。终端接收到DCI后，可以根据DCI进行至少一个物理共享信道的数据传输。
作为一种示例，若物理共享信道是PDSCH，该DCI包括至少一个PDSCH的时频资源的指示信息。终端接收到DCI后，在该时频资源上接收至少一个PDSCH。若物理共享信道是PUSCH，该DCI包括至少一个PUSCH的时频资源的指示信息。终端接收到DCI后，在该时频资源上发送至少一个PUSCH。
另一种可能的设计，第一控制信息包括在半静态调度的配置消息中，如包括在无线资源控制(radio resource control，RRC)消息或DCI中。终端接收到半静态调度的配置消息后，可以根据半静态调度的配置消息，进行至少一个物理共享信道的数据传输；或者，终端接收到半静态调度的配置消息后，先不进行至少一个物理共享信道的数据传输，在接收到激活该半静态调度的配置消息的激活消息(如DCI)后，再进行传输。
作为一种示例，若物理共享信道是PDSCH，第一控制信息包括在RRC消息中，第一控制信息包括至少一个PDSCH的时频资源的指示信息。终端在接收到来自网络设备的RRC消息，并且接收到用于激活该RRC消息配置的至少一个PDSCH的DCI后，在该时频资源上接收至少一个PDSCH。
作为另一种示例，若物理共享信道是PUSCH，第一控制信息包括在RRC消息或DCI中，第一控制信息包括至少一个PUSCH的时频资源的指示信息。终端接收到来自网络设备的RRC消息或DCI后，在该时频资源上发送至少一个PUSCH。或者，第一控制信息包括在RRC消息中，第一控制信息包括至少一个PUSCH的时频资源的指示信息。终端接收到来自网络设备的RRC消息，并且接收到用于激活该RRC消息配置的至少一个PUSCH的DCI后，在该时频资源上发送至少一个PUSCH。
S702：终端根据至少一个物理共享信道的数量确定重传定时器的时长。
本申请实施例中，重传定时器的时长为监听第二控制信息的最大时长。第二控制信息可以用于调度至少一个物理共享信道的数据重传。
作为一种示例，若物理共享信道是PDSCH，则重传定时器为drx-RetransmissionTimerDL，若物理共享信道是PUSCH，则重传定时器为drx-RetransmissionTimerUL。应理解，在具体应用中，重传定时器还可以有其他的命名方式，本申请实施例不进行具体限定。
可以理解的，至少一个物理共享信道的数量越多，进行数据重传的可能性就越大，终端可能 要被调度多次重传。此时，若终端将重传定时器的时长设置的太短会导致至少一个物理共享信道中的某些信道的重传来不及调度，影响重传性能。因此，在本申请实施例中，至少一个物理共享信道的数量越多，重传定时器的时长越长，至少一个物理共享信道的数量越少，重传定时器的时长越短。即：至少一个物理共享信道的数量为第一数值的情况下，重传定时器的时长大于至少一个物理共享信道的数量为第二数值的情况下，重传定时器的时长。其中，第一数值大于第二数值。
应理解，终端在重传定时器的时长内，处于激活状态，要监听PDCCH，所以在确定重传定时器的时长时还要考虑到终端的功耗。重传定时器的时长越长，终端的功耗越大，重传定时器的时长越短，终端的功耗越小。也就是说，在确定重传定时器的时长时，应当兼顾重传性能和终端的功耗。
一种可能的设计，至少一个物理共享信道的数量与重传定时器的时长有对应关系，终端根据至少一个物理共享信道的数量和该对应关系，确定重传定时器的时长。
作为一种示例，至少一个物理共享信道的数量与重传定时器的时长的对应关系可以如表1所示。在表1中，任意一个重传定时器的时长都对应一个数量范围。若至少一个物理共享信道的数量为1或2，则重传定时器的时长为t1，若至少一个物理共享信道的数量为3或4，则重传定时器的时长为t2，若至少一个物理共享信道的数量为5或6，则重传定时器的时长为t3。
表1
作为另一种示例，至少一个物理共享信道的数量与重传定时器的时长的对应关系可以如表2所示。在表2中，任意一个重传定时器的时长都对应一个物理共享信道的数量。若至少一个物理共享信道的数量为1，则重传定时器的时长为t1，若至少一个物理共享信道的数量为2，则重传定时器的时长为t2，若至少一个物理共享信道的数量为3，则重传定时器的时长为t3。
表2
作为另一种示例，至少一个物理共享信道的数量与重传定时器的时长的对应关系可以如表3所示。在表3中，若至少一个物理共享信道的数量为1，则重传定时器的时长为t1，若至少一个物理共享信道的数量大于1，则重传定时器的时长为t2。
表3
可以理解的，上述表1、表2和表3仅是至少一个物理共享信道的数量与重传定时器的时长的对应关系的示例，在具体应用中，至少一个物理共享信道的数量与重传定时器的时长的对应关系还可以是其他形式的，不予限制。
可选的，在S702之前，网络设备向终端发送配置信息。相应的，终端接收来自网络设备的配置信息。其中，该配置信息可以用于配置重传定时器的多个候选时长，例如，配置信息包括该多 个候选时长。本申请实施例中，多个可以指大于或等于2个。此时，终端可以根据配置信息配置的多个候选时长和至少一个物理共享信道的数量，确定重传定时器的时长。
一种可能的实现方式，终端根据至少一个物理共享信道的数量在多个候选时长中，确定与至少一个物理共享信道的数量对应的重传定时器的时长。
作为一种示例，若配置信息包括t1、t2和t3，至少一个物理共享信道的数量为2，则终端根据上述表1，可以确定与至少一个物理共享信道的数量对应的重传定时器的时长为t1，终端根据上述表2，可以确定与至少一个物理共享信道的数量对应的重传定时器的时长为t2。
作为另一种示例，若配置信息包括t1和t2，至少一个物理共享信道的数量为2，则终端根据上述表3，可以确定与至少一个物理共享信道的数量对应的重传定时器的时长为t2；若配置信息包括t1和t2，至少一个物理共享信道的数量为1，则终端根据上述表3，可以确定与至少一个物理共享信道的数量对应的重传定时器的时长为t1。
可选的，网络设备根据至少一个物理共享信道的数量确定重传定时器的时长。这样，网络设备就可以知道终端在什么时候处于激活状态，来接收第二控制信息。网络设备可以在重传定时器的持续时间内，向终端发送第二控制信息。网络设备根据至少一个物理共享信道的数量确定重传定时器的时长的过程，可以参考终端根据至少一个物理共享信道的数量确定重传定时器的时长的对应描述，在此不做赘述。
S703：终端启动重传定时器，并在重传定时器的时长内监听第二控制信息。
可以理解的，物理共享信道是PUSCH和物理共享信道是PDSCH的情况下，终端启动重传定时器的过程不同，下面进行具体阐述。
情况1：物理共享信道是PUSCH。
在图4A对应的描述中介绍了：对于一个DCI调度多个PUSCH，如果终端配置了DRX，那么每个PUSCH传输完成后，终端会启动drx-HARQ-RTT-TimerUL。在drx-HARQ-RTT-TimerUL超时后，终端会启动drx-RetransmissionTimerUL，并在drx-RetransmissionTimerUL运行期间，持续监听PDCCH。那么，对于图4A的方案，终端在A1时间段内都处于激活状态，终端的功耗较大。为了降低终端的功耗，可以配置终端在同一时刻启动多个PUSCH对应的重传定时器。这样，可以缩短终端处于激活状态的时间，所以能够降低终端的功耗。
可以理解的，终端在同一时刻可以启动多个PUSCH中每个PUSCH对应的重传定时器，或者启动多个PUSCH中的某一个PUSCH对应的重传定时器，或者启动一个重传定时器，用于监控多个PUSCH的对应的第二控制信息。
一种可能的设计，重传定时器为最后一个物理共享信道对应的重传定时器；或者，重传定时器为至少一个物理共享信道对应的重传定时器；或者，重传定时器与至少一个物理共享信道一一对应。其中，最后一个物理共享信道为至少一个物理共享信道中的最后一个物理共享信道，或者，最后一个物理共享信道为至少一个物理共享信道中实际发送的最后一个物理共享信道。
本申请实施例中，重传定时器为最后一个物理共享信道对应的重传定时器可以理解为终端启动最后一个物理共享信道对应的重传定时器，而不启动至少一个物理共享信道中除最后一个物理共享信道之外的其他物理共享信道的重传定时器。在这种情况下，终端可以在重传定时器的持续时间内接收第二控制信息。但是，若终端先接收到最后一个物理共享信道对应的第二控制信息，终端停止重传定时器，进入休眠状态，会导致终端可能接收不到其他物理共享信道对应的第二控制信息。
本申请实施例中，重传定时器为至少一个物理共享信道对应的重传定时器可以理解为终端为至少一个物理共享信道启动一个重传定时器。在这种情况下，终端可以在重传定时器的持续时间内接收第二控制信息。而且，终端无论接收到哪个物理共享信道对应的第二控制信息，都不停止重传定时器，直至重传定时器超时，以使得终端来得及接收到所有需要重传的物理共享信道对应的第二控制信息。但是，在至少一个物理共享信道对应的第二控制信息都接收到的情况下，重传定时器还没有超时，终端也不会停止重传定时器，会增加终端的功耗。
本申请实施例中，重传定时器与至少一个物理共享信道一一对应可以理解为终端为至少一个物理共享信道中的每个物理共享信道启动重传定时器。在这种情况下，终端可以在重传定时器的 持续时间内接收第二控制信息。而且，终端接收到哪个物理共享信道对应的第二控制信息，终端就停止哪个物理共享信道对应的重传定时器，既来得及接收到所有需要重传的物理共享信道对应的第二控制信息，又不会在至少一个物理共享信道对应的第二控制信息都接收到的情况下，继续维护重传定时器，能够降低终端的功耗。
一种可能的实现方式，终端在a+T1时刻启动重传定时器。其中，a为至少一个物理共享信道的最后一个物理共享信道对应的时刻，T1为第一预设时长，第一预设时长为网络设备配置的时长。例如，T1为drx-HARQ-RTT-TimerUL的时长。
作为一种示例，对于图4A，终端在第三个PUSCH发送完成后，启动drx-HARQ-RTT-TimerUL定时器，在drx-HARQ-RTT-TimerUL超时后，启动重传定时器。如：启动第三个PUSCH对应重传定时器，或者启动3个PUSCH对应的重传定时器，或者启动与3个PUSCH中每个PUSCH对应的重传定时器。在本示例中，终端在A2时间段内处于激活状态。
另一种可能的实现方式，若至少一个物理共享信道的数量大于1，终端在b+T2时刻启动重传定时器。其中，b为至少一个物理共享信道中实际发送的最后一个物理共享信道对应的时刻，T2为第二预设时长，第二预设时长为网络设备配置的时长。例如，T2为drx-HARQ-RTT-TimerUL的时长。
作为一种示例，对于图4A，若终端实际发送的最后一个物理共享信道为第二个PUSCH，则终端在第二个PUSCH发送完成后，启动drx-HARQ-RTT-TimerUL定时器，在drx-HARQ-RTT-TimerUL超时后，启动重传定时器。如：启动第二个PUSCH对应的重传定时器，或者启动3个PUSCH对应的重传定时器，或者启动与3个PUSCH中每个PUSCH对应的重传定时器。
可以理解的，对于终端在b+T2时刻启动重传定时器的方案，终端可以向网络设备指示哪一个物理共享信道是实际发送的最后一个物理共享信道，以便网络设备确定何时向终端发送第二控制信息。
一种可能的实现方式，终端向网络设备发送指示信息。相应的，网络设备接收来自终端的指示信息。其中，指示信息可以用于指示终端实际发送的最后一个物理共享信道，或者指示信息可以用于指示网络设备实际接收的最后一个物理共享信道。
作为一种示例，指示信息对应的时频资源与实际发送的最后一个物理共享信道对应的时频资源相同。即终端通过实际发送的最后一个物理共享信道对应的时频资源发送指示信息。该指示信息包括1比特，若该1比特的值为1，则表示与该指示信息对应的时频资源相同的物理共享信道为实际发送的最后一个物理共享信道。
作为另一种示例，指示信息对应的时频资源与至少一个物理共享信道中第一个物理共享信道对应的时频资源相同。即终端通过至少一个物理共享信道中第一个物理共享信道对应的时频资源发送指示信息。该指示信息可以包括实际发送的最后一个物理共享信道的标识，或者，该指示信息包括实际发送的物理共享信道的数量，以便网络设备根据该指示信息确定终端实际发送的最后一个物理共享信道。
情况2：物理共享信道是PDSCH。
对于情况2，在S703之前，终端向网络设备发送反馈信息。相应的，网络设备接收来自终端的反馈信息。其中，反馈信息可以用于指示至少一个物理共享信道上的数据传输是否成功。
作为一种示例，反馈信息包括与至少一个物理共享信道中每个物理共享信道对应的指示信息，该指示信息指示与该指示信息对应的物理共享信道上的数据传输是否成功。
作为另一种示例，反馈信息包括1比特指示信息。该1比特指示信息用于指示至少一个物理共享信道上的数据传输是否成功。例如，若至少一个物理共享信道中每个物理共享信道上的数据传输都成功，则该1比特指示信息指示至少一个物理共享信道上的数据传输成功；若至少一个物理共享信道中至少一个物理共享信道上的数据传输失败，则该1比特指示信息指示至少一个物理共享信道上的数据传输失败。
一种可能的实现方式，终端在c+T3时刻启动重传定时器。其中，c为发送反馈信息的时刻，T3为第三预设时长，第三预设时长为网络设备配置的时长。
作为一种示例，终端在发送完反馈信息后，启动drx-HARQ-RTT-TimerDL定时器，在drx-HARQ-RTT-TimerDL超时后，启动重传定时器。
可选的，网络设备启动重传定时器，并在重传定时器的时长内向终端发送第二控制信息。其中，网络设备启动重传定时器的过程与终端启动重传定时器的过程类似，因此，可以参考终端启动重传定时器的对应描述，在此不做赘述。
其中，上述S701-S703中的网络设备或者终端的动作可以由图6所示的通信装置60中的处理器601调用存储器603中存储的应用程序代码来执行，本申请实施例对此不做任何限制。
基于图7所示的方法，终端可以根据至少一个物理共享信道的数量确定重传定时器的时长，例如，当至少一个物理共享信道的数量较多时，确定的重传定时器的时长较长，当至少一个物理共享信道的数量较少时，确定的重传定时器的时长较短。如此，可以使得重传定时器的时长被配置得更为合理，以提高至少一个物理共享信道的数据重传的性能。
本申请上文中提到的各个实施例之间在方案不矛盾的情况下，均可以进行结合，不作限制。
可以理解的，以上各个实施例中，由终端实现的方法和/或步骤，也可以由可用于终端的部件(例如芯片或者电路)实现；由网络设备实现的方法和/或步骤，也可以由可用于网络设备的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置可以为上述方法实施例中的终端，或者包含上述终端的装置，或者为可用于终端的部件；或者，该通信装置可以为上述方法实施例中的网络设备，或者包含上述网络设备的装置，或者为可用于网络设备的部件。可以理解的是，上述终端设备或者网络设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法操作，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
应理解的是，上述仅以终端和网络设备为例描写各个网元之间的交互。实际上，上述终端所执行的处理并不限于仅由单一网元执行，上述网络设备所执行的处理也并不限于仅由单一网元执行。例如，网络设备所执行的处理可以分别由CU、DU和远端单元(remote unit，RU)中的至少一个执行。
本申请实施例可以根据上述方法示例对终端或网络设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。可以理解的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图8示出了一种通信装置80的结构示意图。通信装置80包括处理模块801和收发模块802。处理模块801，也可以称为处理单元用于执行除了收发操作之外的操作，例如可以是处理电路或者处理器等。收发模块802，也可以称为收发单元用于执行收发操作，例如可以是收发电路，收发机，收发器或者通信接口等。
在一些实施例中，该通信装置80还可以包括存储模块(图8中未示出)，用于存储程序指令和数据。
示例性地，通信装置80用于实现终端的功能。通信装置80例如为图7所示的实施例。
其中，收发模块802，用于接收来自网络设备的第一控制信息。其中，第一控制信息用于指示至少一个物理共享信道的数据传输。例如，收发模块802可以用于执行S701。
处理模块801，用于根据至少一个物理共享信道的数量确定重传定时器的时长，重传定时器的时长为监听第二控制信息的最大时长，第二控制信息用于调度至少一个物理共享信道的数据重传。例如，处理模块801可以用于执行S702。
处理模块801，还用于启动重传定时器，并通过收发模块802在重传定时器的时长内监听第二控制信息。例如，处理模块801可以用于执行S703。
一种可能的实现方式，收发模块802，还用于接收来自网络设备的配置信息，配置信息用于配置重传定时器的多个候选时长。
一种可能的实现方式，处理模块801，具体用于根据至少一个物理共享信道的数量在多个候选时长中，确定与至少一个物理共享信道的数量对应的重传定时器的时长。
一种可能的实现方式，至少一个物理共享信道的数量为第一数值的情况下，重传定时器的时长大于至少一个物理共享信道的数量为第二数值的情况下，重传定时器的时长，其中，第一数值大于第二数值。
一种可能的实现方式，物理共享信道为物理上行共享信道，处理模块801，具体用于在a+T1时刻启动重传定时器，a为至少一个物理共享信道的最后一个物理共享信道对应的时刻，T1为网络设备配置的时长。
一种可能的实现方式，物理共享信道为物理上行共享信道，至少一个物理共享信道的数量大于1，处理模块801，具体用于在b+T2时刻启动重传定时器，b为至少一个物理共享信道中实际发送的最后一个物理共享信道对应的时刻，T2为网络设备配置的时长。
一种可能的实现方式，收发模块802，还用于向网络设备发送指示信息，指示信息用于指示实际发送的最后一个物理共享信道。
一种可能的实现方式，重传定时器为最后一个物理共享信道对应的重传定时器；或者，重传定时器为至少一个物理共享信道对应的重传定时器；或者，重传定时器与至少一个物理共享信道一一对应。
一种可能的实现方式，物理共享信道为物理下行共享信道，收发模块802，还用于向网络设备发送反馈信息，反馈信息用于指示至少一个物理共享信道上的数据传输是否成功；处理模块801，具体用于在c+T3时刻启动重传定时器，c为发送反馈信息的时刻，T3为网络设备配置的时长。
当用于实现终端的功能时，关于通信装置80所能实现的其他功能，可参考图7所示的实施例的相关介绍，不多赘述。
或者，示例性地，通信装置80用于实现网络设备的功能。通信装置80例如为图7所示的实施例所述的网络设备。
其中，收发模块802，用于向终端发送第一控制信息，第一控制信息用于指示至少一个物理共享信道的数据传输。例如，收发模块802可以用于执行S701。
处理模块801，用于根据至少一个物理共享信道的数量确定重传定时器的时长，重传定时器的时长为终端监听第二控制信息的最大时长，第二控制信息用于调度至少一个物理共享信道的数据重传。
处理模块801，还用于启动重传定时器，并通过收发模块802在重传定时器的时长内向终端发送第二控制信息。
一种可能的实现方式，收发模块802，还用于向终端发送配置信息，配置信息用于配置重传定时器的多个候选时长。
一种可能的实现方式，处理模块801，具体用于根据至少一个物理共享信道的数量在多个候选时长中，确定与至少一个物理共享信道的数量对应的重传定时器的时长。
一种可能的实现方式，至少一个物理共享信道的数量为第一数值的情况下，重传定时器的时长大于至少一个物理共享信道的数量为第二数值的情况下，重传定时器的时长，其中，第一数值大于第二数值。
一种可能的实现方式，物理共享信道为物理上行共享信道，处理模块801，具体用于在a+T1时刻启动重传定时器，a为至少一个物理共享信道的最后一个物理共享信道对应的时刻，T1为第一预设时长。
一种可能的实现方式，物理共享信道为物理上行共享信道，至少一个物理共享信道的数量大于1，处理模块801，具体用于在b+T2时刻启动重传定时器，b为至少一个物理共享信道中实际接收的最后一个物理共享信道对应的时刻，T2为第二预设时长。
一种可能的实现方式，收发模块802，还用于接收来自终端的指示信息，指示信息用于指示实际接收的最后一个物理共享信道。
一种可能的实现方式，重传定时器为最后一个物理共享信道对应的重传定时器；或者，重传定时器为至少一个物理共享信道对应的重传定时器；或者，重传定时器与至少一个物理共享信道一一对应。
一种可能的实现方式，物理共享信道为物理下行共享信道，收发模块802，还用于接收来自终端的反馈信息，反馈信息用于指示至少一个物理共享信道上的数据传输是否成功；处理模块801，具体用于在c+T3时刻启动重传定时器，c为接收反馈信息的时刻，T3为第三预设时长。
当用于实现网络设备的功能时，关于通信装置80所能实现的其他功能，可参考图7所示的实施例的相关介绍，不多赘述。
在一个简单的实施例中，本领域的技术人员可以想到通信装置80可以采用图6所示的形式。比如，图6中的处理器601可以通过调用存储器603中存储的计算机执行指令，使得通信装置80执行上述方法实施例中所述的方法。
示例性的，图8中的处理模块801和收发模块802的功能/实现过程可以通过图6中的处理器601调用存储器603中存储的计算机执行指令来实现。或者，图8中的处理模块801的功能/实现过程可以通过图6中的处理器601调用存储器603中存储的计算机执行指令来实现，图8中的收发模块802的功能/实现过程可以通过图6中的通信接口604来实现。
可以理解的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上系统)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
可选的，本申请实施例还提供了一种芯片系统，包括：至少一个处理器和接口，该至少一个处理器通过接口与存储器耦合，当该至少一个处理器执行存储器中的计算机程序或指令时，使得上述任一方法实施例中的方法被执行。在一种可能的实现方式中，该芯片系统还包括存储器。可选的，该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
可选的，本申请实施例还提供了一种计算机可读存储介质。上述方法实施例中的全部或者部分流程可以由计算机程序来指令相关的硬件完成，该程序可存储于上述计算机可读存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。计算机可读存储介质可以是前述任一实施例的通信装置的内部存储单元，例如通信装置的硬盘或内存。上述计算机可读存储介质也可以是上述通信装置的外部存储设备，例如上述通信装置上配备的插接式硬盘，智能存储卡(smart media card，SMC)，安全数字(secure digital，SD)卡，闪存卡(flash card)等。进一步地，上述计算机可读存储介质还可以既包括上述通信装置的内部存储单元也包括外部存储设备。上述计算机可读存储介质用于存储上述计算机程序以及上述通信装置所需的其他程序和数据。上述计算机可读存储介质还可以用于暂时地存储已经输出或者将要输出的数据。
可选的，本申请实施例还提供了一种计算机程序产品。上述方法实施例中的全部或者部分流程可以由计算机程序来指令相关的硬件完成，该程序可存储于上述计算机程序产品中，该程序在执行时，可包括如上述各方法实施例的流程。
可选的，本申请实施例还提供了一种计算机指令。上述方法实施例中的全部或者部分流程可以由计算机指令来指令相关的硬件(如计算机、处理器、终端或网络设备等)完成。该程序可被存储于上述计算机可读存储介质中或上述计算机程序产品中。
可选的，本申请实施例还提供了一种通信系统，包括：上述实施例中的网络设备和终端。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁， 仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (25)

  1. 一种通信方法，其特征在于，所述方法包括：
    接收来自网络设备的第一控制信息，所述第一控制信息用于指示至少一个物理共享信道的数据传输；
    根据所述至少一个物理共享信道的数量确定重传定时器的时长，所述重传定时器的时长为监听第二控制信息的最大时长，所述第二控制信息用于调度所述至少一个物理共享信道的数据重传；
    启动所述重传定时器，并在所述重传定时器的时长内监听所述第二控制信息。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收来自所述网络设备的配置信息，所述配置信息用于配置所述重传定时器的多个候选时长。
  3. 根据权利要求2所述的方法，其特征在于，所述根据所述至少一个物理共享信道的数量确定重传定时器的时长，包括：
    根据所述至少一个物理共享信道的数量在所述多个候选时长中，确定与所述至少一个物理共享信道的数量对应的重传定时器的时长。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，
    所述至少一个物理共享信道的数量为第一数值的情况下，所述重传定时器的时长大于所述至少一个物理共享信道的数量为第二数值的情况下，所述重传定时器的时长，其中，所述第一数值大于所述第二数值。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述物理共享信道为物理上行共享信道，所述启动所述重传定时器，包括：
    在a+T1时刻启动所述重传定时器，所述a为所述至少一个物理共享信道的最后一个物理共享信道对应的时刻，所述T1为所述网络设备配置的时长。
  6. 根据权利要求1-4中任一项所述的方法，其特征在于，所述物理共享信道为物理上行共享信道，所述至少一个物理共享信道的数量大于1，所述启动所述重传定时器，包括：
    在b+T2时刻启动所述重传定时器，所述b为所述至少一个物理共享信道中实际发送的最后一个物理共享信道对应的时刻，所述T2为所述网络设备配置的时长。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    向所述网络设备发送指示信息，所述指示信息用于指示所述实际发送的最后一个物理共享信道。
  8. 根据权利要求5-7中任一项所述的方法，其特征在于，
    所述重传定时器为所述最后一个物理共享信道对应的重传定时器；或者，
    所述重传定时器为所述至少一个物理共享信道对应的重传定时器；或者，
    所述重传定时器与所述至少一个物理共享信道一一对应。
  9. 根据权利要求1-4中任一项所述的方法，其特征在于，所述物理共享信道为物理下行共享信道，所述方法还包括：
    向所述网络设备发送反馈信息，所述反馈信息用于指示所述至少一个物理共享信道上的数据传输是否成功；
    所述启动所述重传定时器，包括：在c+T3时刻启动所述重传定时器，所述c为发送所述反馈信息的时刻，所述T3为所述网络设备配置的时长。
  10. 一种通信方法，其特征在于，所述方法包括：
    向终端发送第一控制信息，所述第一控制信息用于指示至少一个物理共享信道的数据传输；
    根据所述至少一个物理共享信道的数量确定重传定时器的时长，所述重传定时器的时长为所述终端监听第二控制信息的最大时长，所述第二控制信息用于调度所述至少一个物理共享信道的数据重传；
    启动所述重传定时器，并在所述重传定时器的时长内向所述终端发送所述第二控制信息。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    向所述终端发送配置信息，所述配置信息用于配置所述重传定时器的多个候选时长。
  12. 根据权利要求11所述的方法，其特征在于，所述根据所述至少一个物理共享信道的数量 确定重传定时器的时长，包括：
    根据所述至少一个物理共享信道的数量在所述多个候选时长中，确定与所述至少一个物理共享信道的数量对应的重传定时器的时长。
  13. 根据权利要求10-12中任一项所述的方法，其特征在于，
    所述至少一个物理共享信道的数量为第一数值的情况下，所述重传定时器的时长大于所述至少一个物理共享信道的数量为第二数值的情况下，所述重传定时器的时长，其中，所述第一数值大于所述第二数值。
  14. 根据权利要求10-13中任一项所述的方法，其特征在于，所述物理共享信道为物理上行共享信道，所述启动所述重传定时器，包括：
    在a+T1时刻启动所述重传定时器，所述a为所述至少一个物理共享信道的最后一个物理共享信道对应的时刻，所述T1为第一预设时长。
  15. 根据权利要求10-13中任一项所述的方法，其特征在于，所述物理共享信道为物理上行共享信道，所述至少一个物理共享信道的数量大于1，所述启动所述重传定时器，包括：
    在b+T2时刻启动所述重传定时器，所述b为所述至少一个物理共享信道中实际接收的最后一个物理共享信道对应的时刻，所述T2为第二预设时长。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    接收来自所述终端的指示信息，所述指示信息用于指示所述实际接收的最后一个物理共享信道。
  17. 根据权利要求14-16中任一项所述的方法，其特征在于，
    所述重传定时器为所述最后一个物理共享信道对应的重传定时器；或者，
    所述重传定时器为所述至少一个物理共享信道对应的重传定时器；或者，
    所述重传定时器与所述至少一个物理共享信道一一对应。
  18. 根据权利要求10-13中任一项所述的方法，其特征在于，所述物理共享信道为物理下行共享信道，所述方法还包括：
    接收来自所述终端的反馈信息，所述反馈信息用于指示所述至少一个物理共享信道上的数据传输是否成功；
    所述启动所述重传定时器，包括：
    在c+T3时刻启动所述重传定时器，所述c为接收所述反馈信息的时刻，所述T3为第三预设时长。
  19. 一种通信装置，其特征在于，包括用于执行如权利要求1至9中任一项所述方法的单元或模块。
  20. 一种通信装置，其特征在于，包括用于执行如权利要求10-18中任一项所述方法的单元或模块。
  21. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求1至9中任一项所述的方法。
  22. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求10至18中任一项所述的方法。
  23. 一种计算机可读存储介质，其上存储有计算机程序或指令，其特征在于，所述计算机程序或指令被执行时使得计算机执行如权利要求1至9中任一项所述的方法或者如权利要求10至18中任一项所述的方法。
  24. 一种计算机程序产品，所述计算机程序产品中包括计算机程序代码，其特征在于，当所述计算机程序代码在计算机上运行时，使得计算机实现权利要求1至9中任一项所述的方法或者实现权利要求10至18中任一项所述的方法。
  25. 一种通信系统，其特征在于，包括如权利要求19和20所述的装置，或者包括如权利要求21和22所述的装置。
PCT/CN2023/117448 2022-09-28 2023-09-07 控制信息的监听方法及装置 WO2024067002A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211192583.3 2022-09-28
CN202211192583.3A CN117793922A (zh) 2022-09-28 2022-09-28 控制信息的监听方法及装置

Publications (1)

Publication Number Publication Date
WO2024067002A1 true WO2024067002A1 (zh) 2024-04-04

Family

ID=90385640

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/117448 WO2024067002A1 (zh) 2022-09-28 2023-09-07 控制信息的监听方法及装置

Country Status (2)

Country Link
CN (1) CN117793922A (zh)
WO (1) WO2024067002A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111757436A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种非连续接收的方法及设备
CN112154693A (zh) * 2018-05-10 2020-12-29 上海诺基亚贝尔股份有限公司 监测pdcch以用于获取上行链路harq-ack反馈
CN114175549A (zh) * 2019-07-26 2022-03-11 高通股份有限公司 非连续接收的混合自动重传请求(harq)处理
WO2022077174A1 (zh) * 2020-10-12 2022-04-21 Oppo广东移动通信有限公司 无线通信方法和设备
CN114451064A (zh) * 2019-10-09 2022-05-06 Oppo广东移动通信有限公司 非连续接收的方法、终端设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112154693A (zh) * 2018-05-10 2020-12-29 上海诺基亚贝尔股份有限公司 监测pdcch以用于获取上行链路harq-ack反馈
CN111757436A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种非连续接收的方法及设备
CN114175549A (zh) * 2019-07-26 2022-03-11 高通股份有限公司 非连续接收的混合自动重传请求(harq)处理
CN114451064A (zh) * 2019-10-09 2022-05-06 Oppo广东移动通信有限公司 非连续接收的方法、终端设备及存储介质
WO2022077174A1 (zh) * 2020-10-12 2022-04-21 Oppo广东移动通信有限公司 无线通信方法和设备

Also Published As

Publication number Publication date
CN117793922A (zh) 2024-03-29

Similar Documents

Publication Publication Date Title
US20230034294A1 (en) Discontinuous Reception DRX Parameter Configuration Method and Apparatus
TWI603646B (zh) 用於上行鏈路下行鏈路重組態的不連續接收操作
WO2021180098A1 (zh) 无线通信方法和通信装置
WO2020221093A1 (zh) 搜索空间的监测、配置方法及装置
US20220224454A1 (en) Harq process control method and apparatus
US20230371118A1 (en) Communication method and device
WO2020063782A1 (zh) 一种通信方法及装置
WO2021204091A1 (zh) 一种清空缓存的方法及装置
US20230224091A1 (en) Wireless communication method and device
CN113992311A (zh) 用户设备装置和基站装置
US20240023015A1 (en) Sidelink transmission method and terminal
WO2021228237A1 (zh) 通信方法、装置及系统
US20240032142A1 (en) Sidelink transmission method and apparatus
US20230337320A1 (en) Wireless communication method and terminal device
WO2024067002A1 (zh) 控制信息的监听方法及装置
US10681759B2 (en) Paging schemes for peer-to-peer communications
WO2021072705A1 (zh) 无线通信的方法和设备
JP2024504648A (ja) 間欠受信制御方法及び装置
WO2022082806A1 (zh) 无线通信的方法和装置
US20180035376A1 (en) NAN Frame Buffering Indications
WO2022151407A1 (zh) 通信方法及装置
WO2024017094A1 (zh) 非连续接收的管理方法、通信系统及装置
WO2024007882A1 (zh) 一种通信方法以及通信装置
WO2024139566A1 (zh) 通信方法及装置
WO2022150975A1 (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: 23870241

Country of ref document: EP

Kind code of ref document: A1