WO2021027963A1 - 一种定时器控制方法、装置及系统 - Google Patents

一种定时器控制方法、装置及系统 Download PDF

Info

Publication number
WO2021027963A1
WO2021027963A1 PCT/CN2020/109599 CN2020109599W WO2021027963A1 WO 2021027963 A1 WO2021027963 A1 WO 2021027963A1 CN 2020109599 W CN2020109599 W CN 2020109599W WO 2021027963 A1 WO2021027963 A1 WO 2021027963A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq processes
harq
downlink control
terminal device
data transmission
Prior art date
Application number
PCT/CN2020/109599
Other languages
English (en)
French (fr)
Inventor
李军
罗之虎
王宏
单宝堃
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20852287.0A priority Critical patent/EP4017131A4/en
Publication of WO2021027963A1 publication Critical patent/WO2021027963A1/zh
Priority to US17/672,379 priority patent/US20220173842A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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]
    • 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/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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
    • H04L1/1848—Time-out mechanisms
    • 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
    • H04L1/1864—ARQ related signaling
    • 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
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • 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
    • 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
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a timer control method, device and system in a wireless communication system.
  • a discontinuous reception (DRX) function is usually used.
  • the terminal device In order to save power consumption of the terminal device and improve the endurance capability of the terminal device, a discontinuous reception (DRX) function is usually used.
  • the terminal device When using the DRX function, the terminal device only needs to monitor or receive downlink information or downlink data within the time period specified by the system. In other time periods, the terminal device may not need to monitor or receive downlink information or downlink data, or even shut down or deactivate it. All or part of the receiving function, so as to achieve the purpose of power saving.
  • the terminal device maintains some timers related to the DRX function, and determines whether it needs to monitor or receive downlink information or downlink data according to the state of the timer, for example, the timer is running (run) or timer is expired (expired).
  • the network device also maintains a corresponding timer for the terminal device, and determines whether to send downlink information or downlink data to the terminal device according to the status of the timer.
  • Hybrid automatic repeat request is a technology that combines correction and automatic repeat request methods.
  • the receiving end of data or information feeds back an acknowledgement message (acknowledge, ACK) or negative response (Negative acknowledgement, NACK), the sender of data or information can decide whether to retransmit.
  • acknowledgement message acknowledgement message
  • NACK negative response
  • the sender of data or information can decide whether to retransmit.
  • the embodiments of the present application provide a timer control method, device, and system to reduce the power consumption of terminal equipment and improve the endurance of terminal equipment.
  • the embodiments of the present application provide a timer control method, which can be applied to a wireless communication device.
  • the wireless communication device may be a terminal device, or a structure or device in the terminal device, such as a chip or a chip. System or circuit system, etc.
  • the method includes: monitoring a physical downlink control channel, acquiring downlink control information in the physical downlink control channel, if the downlink control information indicates N hybrid automatic repeat request HARQ process data transmission, and the terminal device is configured with N In the HARQ process, where N is an integer greater than or equal to 2, the discontinuous reception inactivity timer is not started or the discontinuous reception inactivity timer is stopped.
  • the terminal device When the number of HARQ processes used for data transmission indicated by the downlink control information is equal to the number of HARQ processes configured by the terminal device, it means that the terminal device has no HARQ available for data transmission, so the network device will not use other HARQ processes to the terminal.
  • the device sends downlink control information. At this time, the terminal device may not start or stop the discontinuous reception inactivity timer, thereby avoiding the terminal device from monitoring the physical downlink control channel because the discontinuous reception inactivity timer is running.
  • the method further includes that if the downlink control information indicates data transmission of M HARQ processes, data of at least one HARQ process in the data transmission of the M HARQ processes is newly transmitted, and
  • the terminal device is configured with N HARQ processes, where M is an integer greater than or equal to 1, N is an integer greater than or equal to 2, and M is less than N, then the discontinuous reception inactivity timer is started or restarted.
  • the conditions for starting or restarting the discontinuous reception inactivity timer only include the situation that there are still available HARQ processes, which can avoid starting the discontinuous reception inactivity timer when no other HARQ processes are available, thereby further avoiding inactivity due to discontinuous reception
  • the timer is in the running state so that the terminal equipment monitors the physical downlink control channel.
  • the method further includes that if the downlink control information indicates data transmission of M HARQ processes, data of at least one HARQ process in the data transmission of the M HARQ processes is newly transmitted, except for all data transmissions. Except when the terminal device is configured with M HARQ processes, start or restart the discontinuous reception inactivity timer, where M is an integer greater than or equal to 1. In the condition of starting or restarting the discontinuous reception inactivity timer, it is excluded to start the discontinuous reception inactivity timer when no other HARQ process is available, so as to further avoid the terminal device from monitoring the physical condition because the discontinuous reception inactivity timer is running. Downlink control channel.
  • the downlink control information indicating data transmission of M HARQ processes includes: the downlink control information indicating uplink data transmission of M HARQ processes, or the downlink control information indicating data transmission of M HARQ processes Downlink data transmission.
  • the N is less than or equal to the number of HARQ processes supported by the terminal device.
  • the terminal device may report the number of HARQ processes it supports to the network device, so that the network device configures the number of HARQ processes according to the support capability of the terminal device.
  • the terminal device is configured with N HARQ processes, including: the terminal device is configured with N uplink HARQ processes and/or is configured with N downlink HARQ processes.
  • the downlink control information indicates the data transmission of N HARQ processes, including: the downlink control information indicates the uplink data transmission of the N HARQ processes, or the downlink control information indicates Downlink data transmission of N HARQ processes.
  • the method further includes monitoring the physical downlink control channel after starting or restarting the discontinuous reception inactivity timer.
  • the embodiments of the present application provide a timer control method, which can be applied to a wireless communication device.
  • the wireless communication device may be a network device, or a structure or device in the network device, such as a chip or a chip. System or circuit system, etc.
  • the method includes: sending downlink control information to a terminal device on a physical downlink control channel, if the downlink control information indicates data transmission of N hybrid automatic repeat request HARQ processes, and the terminal device is configured with N HARQ processes, Where N is an integer greater than or equal to 2, the discontinuous reception inactivity timer maintained for the terminal device is not started or the discontinuous reception inactivity timer maintained for the terminal device is stopped.
  • the network equipment can maintain the corresponding DRX-related timers for the terminal equipment, so that the status of the communication parties can be kept consistent.
  • the network device may determine whether to send downlink control information to the terminal device according to the status of the discontinuous reception inactivity timer maintained for the terminal device.
  • the method further includes that if the downlink control information indicates data transmission of M HARQ processes, the data of at least one HARQ process in the data transmission of the M HARQ processes is newly transmitted, and
  • the terminal device is configured with N HARQ processes, where M is an integer greater than or equal to 1, N is an integer greater than or equal to 2, and M is less than N, then start or restart the non-continuous maintenance of the terminal device Receive inactivity timer.
  • the method further includes that if the downlink control information indicates data transmission of M HARQ processes, the data of at least one HARQ process in the data transmission of the M HARQ processes is newly transmitted, except for all data transmissions. Except when the terminal device is configured with M HARQ processes, start or restart the discontinuous reception inactivity timer maintained for the terminal device, where M is an integer greater than or equal to 1.
  • the downlink control information indicating data transmission of M HARQ processes includes: the downlink control information indicates uplink data transmission of M HARQ processes, or the downlink control information indicates the data transmission of M HARQ processes. Downlink data transmission.
  • the N is less than or equal to the number of HARQ processes supported by the terminal device.
  • the terminal device is configured with N HARQ processes, including: the terminal device is configured with N uplink HARQ processes and/or is configured with N downlink HARQ processes.
  • the downlink control information indicates the data transmission of N HARQ processes, including: the downlink control information indicates the uplink data transmission of the N HARQ processes, or the downlink control information indicates the data transmission of the N HARQ processes. Downlink data transmission.
  • the method further includes: after starting or restarting the discontinuous reception inactivity timer maintained for the terminal device, sending the downlink carried on the physical downlink control channel to the terminal device Control information.
  • a communication device which may be a terminal device, or a structure or device provided in the terminal device, for example, a chip, a chip system, or a circuit system.
  • the communication device includes at least one processor, and the at least one processor is configured to be coupled with a memory, read and execute instructions in the memory, so as to implement as described in the first aspect or any possible design of the first aspect Methods.
  • the communication device further includes the memory.
  • the communication device may further include a transceiver device for supporting the communication device to transmit information or data.
  • inventions of the present application provide a communication device.
  • the communication device may be a network device, or a structure or device provided in the network device, such as a chip, a chip system, or a circuit system.
  • the communication device includes at least one processor, and the at least one processor is configured to be coupled with a memory, read and execute instructions in the memory, so as to implement as described in the second aspect or any possible design of the second aspect Methods.
  • the communication device further includes the memory.
  • the communication device may further include a transceiver device for supporting the communication device to transmit information or data.
  • an embodiment of the present application provides a communication device for implementing the first aspect or any one of the possible design methods in the first aspect, including corresponding functional modules, such as a processing unit, a transceiver unit Etc., respectively, used to implement the steps in the above method.
  • an embodiment of the present application provides a communication device for implementing the second aspect or any one of the possible design methods in the second aspect, including corresponding functional modules, such as a processing unit, a transceiver unit Etc., respectively, used to implement the steps in the above method.
  • an embodiment of the present application provides a communication system, which includes a terminal device in any possible design of the third aspect or the third aspect, and any possible design of the fourth aspect or the fourth aspect.
  • the communication system may be a narrowband Internet of Things system.
  • an embodiment of the present application provides a communication system, which includes the communication device of the fifth aspect and the communication device of the sixth aspect.
  • the communication system may be a narrowband Internet of Things system.
  • an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the first aspect and any one of the possible designs in the first aspect are implemented , Or the second aspect and any one of the possible design methods of the second aspect.
  • the embodiments of the present application provide a computer program product, when the computer program product is run by a computer, it can enable the computer to implement the above-mentioned first aspect and any one of the possible design methods in the first aspect, Or the second aspect and any one of the possible design methods of the second aspect.
  • this application describes a timer control method, device and system, which aim to reduce the time for terminal equipment to monitor downlink information or downlink data through timer control, thereby reducing the power consumption of the terminal equipment.
  • FIG. 1 is a schematic diagram of a communication system provided by an embodiment of this application.
  • FIG. 2 is a schematic diagram of a DRX cycle provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram of a timer control method provided by an embodiment of the application.
  • FIG. 5 is a flowchart of another timer control method provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of another timer control method provided by an embodiment of this application.
  • FIG. 7 is a schematic diagram of another timer control method provided by an embodiment of the application.
  • FIG. 8 is a schematic diagram of still another timer control method provided by an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the application.
  • the embodiments of this application can be applied to various communication systems, for example, can be applied to Narrowband Internet of Things (NB-IoT) systems, Internet of Things (IoT) systems, and machine type communication (machine type communication) , MTC) system, enhanced Machine Type Communication (eMTC) system, long term evolution (LTE) system, evolved LTE system (LTE-Advanced, LTE-A), fifth-generation mobile communication Technology (fifth generation, 5G) or new radio (new radio, NR) system, or new communication system emerging in the development of future communication, etc.
  • NB-IoT Narrowband Internet of Things
  • IoT Internet of Things
  • machine type communication machine type communication
  • MTC machine type communication
  • eMTC enhanced Machine Type Communication
  • LTE long term evolution
  • LTE-A evolved LTE system
  • 5G fifth-generation mobile communication Technology
  • new radio new radio
  • the timer control method provided in the embodiments of the present application can be used.
  • Fig. 1 is a communication system applicable to the embodiments of this application.
  • the communication system shown in Fig. 1 includes a network device and six terminal devices. Any one of terminal devices 1-terminal device 6 can be connected to the network The device sends uplink information or uplink data, and can also receive downlink information or downlink data sent by a network device.
  • the terminal devices can also form subsystems and exchange information or data, for example, wireless communication between the terminal device 5 and the terminal device 4.
  • Fig. 1 is only a schematic diagram, and does not specifically limit the type of the communication system, and the number and types of devices included in the communication system.
  • system and “network” in the embodiments of the present application can be used interchangeably, and the terms “field” and “domain” can be used interchangeably.
  • Multiple refers to two or more than two. In the embodiments of the present application, “multiple” may also be understood as “at least two”.
  • At least one can be understood as one or more, for example, one, two or more. For example, including at least one means including one, two or more, and does not limit which ones are included. For example, including at least one of A, B and C, then the included can be A, B, C, A and B, A and C, B and C, or A and B and C.
  • At least two can be understood as two or more.
  • Terminal equipment including communication devices that provide users with voice and/or data connectivity.
  • the communication device may communicate with network equipment, such as core network equipment, via a radio access network (RAN), and exchange voice and/or data.
  • the terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), mobile station (mobile), remote Station (remote station), access point (access point, AP), remote terminal equipment (remote terminal), access terminal equipment (access terminal), user terminal equipment (user terminal), user agent (user agent), user equipment (user device), mobile phones (or “cellular” phones), computers with mobile terminal equipment, portable, pocket-sized, handheld, computer-built or vehicle-mounted mobile devices, smart wearable devices, personal communication services ( Personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, or personal digital assistants (personal digital assistants, PDAs) and other devices.
  • PCS Personal communication service
  • the communication device may also include various capacity-limited devices, such as devices with low power consumption, devices with limited storage capabilities, or devices with limited computing capabilities, such as barcode identification devices, radio frequency identification (RFID) Information sensing equipment such as devices, sensing devices, global positioning system (GPS) devices, laser scanning devices.
  • RFID radio frequency identification
  • the communication device may also include structures or devices built into various terminal devices (for example, any of the above-mentioned devices), such as a chip, a chip system, or a circuit system, etc., where the chip system includes at least one chip, and may also include Other discrete circuit devices.
  • Network equipment which can also be called network-side equipment, includes communication devices deployed on the network side that perform wireless communication with terminal equipment.
  • the communication device may be an access network device or a core network device, or a structure or device built into the network device, such as a chip, a chip system, or a circuit system, etc., where the chip system includes at least one chip, and may also include other discrete The circuit device.
  • the communication device may include various forms of base stations, access points, etc., or routers.
  • the communication device may include a long term evolution (LTE) system or an evolved base station (evolutional NodeB, eNB or e-NodeB) in an evolved LTE system (LTE-Advanced, LTE-A), or may include
  • LTE long term evolution
  • eNB evolved base station
  • e-NodeB evolved LTE system
  • LTE-A evolved LTE system
  • gNB next generation node B
  • NR new radio
  • 5G may also include the access network (radio access network, RAN) Centralized unit (CU) or distributed unit (DU) and so on.
  • RAN radio access network
  • CU Centralized unit
  • DU distributed unit
  • DRX cycle Discontinuous reception
  • the terminal device can determine whether it needs to monitor or receive downlink information or data according to the DRX cycle (DRX cycle).
  • a DRX cycle includes two time periods: On Duration and Opportunity for DRX.
  • the terminal device will start a duration timer (for example, OnDurationTimer).
  • the duration of the timer is the active time.
  • the terminal device usually needs to be Monitor or receive downlink information or downlink data during the active time, such as monitoring the physical downlink control channel.
  • the terminal device may not monitor the downlink information or downlink data, thereby achieving the purpose of power saving.
  • Discontinuous reception inactivity timer is a timer related to DRX.
  • the running time of the timer is the active time, and the terminal device needs to monitor or receive downlink information or downlink data.
  • Physical downlink control channels including channels used to send downlink control information.
  • channels used to send downlink control information Including but not limited to downlink control channels in LTE, LTE-A, 5G or NR systems, such as physical downlink control channels (PDCCH), and downlink control channels in NB-IoT systems, such as narrow-band physical downlink control channels (narrowband physical downlink control channel, NPDCCH), the downlink control channel in the MTC or eMTC system, such as the MTC physical downlink control channel (MPDCCH), etc.
  • the physical downlink shared channel includes a channel used to send downlink information or downlink service data.
  • downlink shared channels in LTE, LTE-A, 5G or NR systems such as physical downlink shared channels (PDSCH), downlink shared channels in NB-IoT systems, such as narrow-band physical downlink shared channels (narrowband physical downlink shared channel, NPDSCH), MTC or eMTC system downlink shared channel, such as MTC physical downlink shared channel (MTC physical downlink shared channel, MPDSCH), etc.
  • the physical uplink shared channel includes a channel used to send uplink information or uplink service data.
  • uplink shared channels in LTE, LTE-A, 5G or NR systems such as physical uplink shared channels (PUSCH), and uplink shared channels in NB-IoT systems, such as narrow-band physical uplink shared channels (narrowband physical uplink shared channel, NPUSCH), the uplink shared channel in the MTC or eMTC system, such as MTC physical uplink shared channel (MPUSCH), etc.
  • PUSCH physical uplink shared channels
  • NB-IoT systems such as narrow-band physical uplink shared channels (narrowband physical uplink shared channel, NPUSCH)
  • NPUSCH narrow-band physical uplink shared channel
  • MTC MTC physical uplink shared channel
  • Downlink control information including information used to carry downlink control messages.
  • the downlink control information may be used to send configuration information of the network device to the terminal device, or used to schedule the transmission of uplink data or downlink data.
  • Downlink control information includes, but is not limited to, downlink control information (DCI) in systems such as NB-IoT, MTC or eMTC, LTE, LTE-A, 5G, or NR.
  • DCI downlink control information
  • the downlink control information can be carried on the physical downlink control channel.
  • Hybrid automatic repeat request process is the process from the network device scheduling a data transmission to the data sending end receiving ACK or NACK feedback, or from the network device scheduling a data transmission to the end of a predetermined length of time the process of.
  • the number of HARQ processes refers to the number of concurrent HARQ processes.
  • the terminal device For the HARQ process of downlink data transmission, the terminal device usually feeds back ACK or NACK to the network device.
  • a time length can be preset between the network device and the terminal device. When the time length is over, the terminal device can recognize a data transmission of a HARQ process. The end of the time length can be judged by a timer.
  • HARQ round trip time timer (HARQ RTT timer) is used to judge whether the time length is over.
  • the network device may not feed back ACK or NACK to the terminal device, but directly realize the new transmission or retransmission of data through scheduling.
  • the network device and the terminal device can preset a time length as a HRAQ process
  • the end of a data transmission can be judged by a timer.
  • the uplink hybrid automatic repeat request round trip time timer (UL HARQ RTT timer) can be used to determine Whether the length of time is over.
  • Transport block refers to the payload (payload) during data transmission.
  • the downlink control information may be used to schedule data transmission of at least one transmission block.
  • the transmission of one transport block will use one HARQ process.
  • One data transmission of one HARQ process may include at least one transmission block.
  • Uplink data transmission refers to terminal equipment sending data or messages to network equipment
  • downlink data transmission refers to network equipment sending data or messages to terminal equipment
  • sidelink data transmission refers to data or message transmission between terminal equipment. send.
  • the new transmission of data refers to the first transmission of a transmission block
  • the retransmission of data refers to the non-first transmission of a transmission block.
  • the "information” mentioned in the embodiments of this application includes control information, configuration information, signaling information, and other information used for transmission between network equipment and terminal equipment or between terminal equipment and terminal equipment.
  • the "data” mentioned in the embodiments of the present application includes service data transmitted between network equipment and terminal equipment or between terminal equipment and terminal equipment.
  • the terminal device can according to the data transmission status of the HARQ process, for example, whether the feedback of ACK or NACK is completed, whether the agreed time length is reached, or whether retransmission is required, etc. Determine whether to monitor downlink information or downlink data based on the time period of the DRX cycle.
  • the embodiment of the present application provides a timer control method.
  • the timer is related to DRX.
  • the terminal device can control the number of HARQ processes and the number of HARQ processes scheduled in the downlink control information. Timer, so that it is easier to determine whether it is necessary to monitor downlink information or downlink data, further reducing the power consumption of the terminal device, and improving the endurance of the terminal device.
  • the following line information is downlink control information
  • the timer related to DRX is a discontinuous reception inactivity timer as an example to introduce the specific embodiments provided in this application. It is understandable that the embodiments provided in this application can also be applied to monitoring and control of other downlink information or downlink data, and can also be applied to other DRX-related timer control.
  • FIG. 3 is a schematic diagram of a timer control method provided by this application.
  • This method can be applied to terminal equipment or network equipment.
  • the discontinuous reception inactivity timer (that is, the DRX inactivity timer) is a timer maintained internally by the terminal device for its own DRX mechanism.
  • the DRX inactivity timer is a timer maintained by the network device for a specific terminal device to determine the DRX status of the terminal device. In the embodiment of this application, it is also referred to as "maintenance for the terminal device".
  • DRX inactivity timer is also referred to as "maintenance for the terminal device".
  • DCI is downlink control information indicating N HARQ processes used for data transmission, and it can also be understood that the DCI indicates or schedules N HARQ processes for data transmission.
  • HARQ 0 is data transmission using the first HARQ
  • HARQ N-1 is data transmission using the Nth HARQ.
  • data transmissions using N HARQs can be continuous in the time domain. It can also be discontinuous.
  • the method includes: if the downlink control information indicates the data transmission of N HARQ processes, and the terminal is configured with N HARQ processes, where N is an integer greater than or equal to 2, then not starting the DRX inactivity timer or stopping the DRX inactivity timing Device.
  • the DRX inactivity timer without starting or stopping the action of the DRX inactivity timer, it can be executed when the number of HARQ processes indicated by the downlink control information is determined.
  • the specific execution time point may be in the process of sending or receiving or analyzing the downlink control information (for example, decoding), or may be executed after the sending or receiving or analyzing of the downlink control information is completed.
  • the time when the transmission of the downlink control information is completed or the time when the reception of the downlink control information is completed is taken as the time point when the DRX inactivity timer action is not started or stopped for description.
  • the method may further include: determining the number of HARQ processes used for data transmission indicated by the downlink control information and the number of HARQ processes configured by the terminal device.
  • determining the number of HARQ processes for data transmission indicated by the downlink control information can be completed when the network device determines the scheduling information for the terminal device, or determines or generates the downlink control information. Determining the number of HARQ processes configured by the terminal device can also be completed when the network device determines the HARQ configuration information of the terminal device or sends the HARQ configuration information to the terminal device.
  • determining the number of HARQ processes configured by the terminal device can also be completed when determining its own HARQ configuration information or receiving HARQ configuration information sent by the network device to the terminal device.
  • the number of HARQ processes used for data transmission indicated by the downlink control information may be the number of HARQ processes used for data transmission indicated in one downlink control information, and one downlink control information refers to the terminal equipment
  • the received downlink control information with the same content may be understood as a piece of downlink control information in the physical downlink control channel. It may also be the number of HARQ processes used for data transmission indicated in multiple downlink control information. For example, when the terminal device is configured with two HARQ processes, when the terminal device receives two different downlink control information, this The two downlink control information respectively indicate that the first HARQ process is used for uplink data transmission and the second HARQ process is used for uplink data transmission. It can be considered that these two downlink control information indicate two HARQ processes for data transmission.
  • the data transmission indicated in the downlink control information may be uplink data transmission, downlink data transmission, or side link data transmission.
  • the downlink control information can indicate the data transmission of N HARQ processes, including: the downlink control information indicates the transmission of at least N transport blocks, and each transport block of the at least N transport blocks uses one HARQ process for transmission, and each HARQ process It can be used to transmit at least one of at least N transmission blocks.
  • the transmission of any one of the at least N transmission blocks may be new transmission or retransmission. Different transmission blocks can be transmitted using different HARQ processes, and can also be transmitted using the same HARQ process.
  • the N HARQ processes used for data transmission indicated by the control information refer to N HARQ processes all used for uplink data transmission, or N HARQ processes all used for downlink data transmission, or both N HARQ processes transmitted on the side link.
  • the number of HARQ processes configured by the terminal device refers to the number of concurrent HARQ processes configured by the network device for the terminal device, or agreed upon by the network device and the terminal, that the terminal device can use simultaneously.
  • the number of HARQ processes configured by the terminal device may be the number of uplink HARQ processes, the number of downlink HARQ processes, or the number of side link HARQ processes. That is, when the terminal device has N HARQ processes, it can be understood that the terminal device can use N HARQ processes in the uplink, and/or the terminal device can use N HARQ processes in the downlink.
  • the uplink data transmission and the downlink data transmission may be performed in the same time period, such as a full-duplex working mode, or may be performed in different time periods, such as a half-duplex working mode.
  • the number of HARQ processes configured by the terminal device is less than or equal to the number of HARQ processes supported by the terminal device.
  • the number of HARQ processes supported by the terminal device refers to the capability of the terminal device itself, that is, the maximum number of concurrent concurrent HARQ processes that the terminal device can support.
  • the terminal device can report the number of HARQ processes it supports as capability information to the network device through signaling or messages, and the network device can configure the number of HARQ processes for the terminal device according to the capability information reported by the terminal device.
  • Not starting or stopping the DRX inactivity timer can be understood as making the DRX inactivity timer in an inactive state, that is, the terminal device will not monitor the downlink information or downlink data because of the DRX inactivity timer.
  • the terminal device can stop monitoring downlink information or downlink data, thereby achieving the purpose of saving power.
  • the terminal equipment When the terminal equipment is configured with N HARQ processes, and the downlink control information also indicates the data transmission of the N HARQ processes, it means that all the N HARQ processes have been scheduled (or occupied), and the terminal equipment can no longer More HARQ processes are used for data transmission. Specifically, if these N HARQ processes are all used for uplink data transmission, it means that there will be no downlink information scheduling terminal equipment to use other HARQ processes for uplink data transmission. If these N HARQ processes are all used for downlink data transmission, It means that no more downlink information or downlink data using other HARQ processes will be sent to the terminal device.
  • the terminal device can stop the DRX inactivity timer to avoid the terminal device from continuing to monitor downlink information or downlink data because the DRX inactivity timer is still running.
  • stopping the DRX inactivity timer does not mean stopping the monitoring of downlink information or downlink data.
  • the terminal device can also determine whether it can stop monitoring the downlink information or downlink data in combination with the running status of other DRX-related timers. If there is no other DRX-related timer indicating that the terminal device needs to monitor the downlink information or downlink data, the terminal device can stop monitoring the downlink information or downlink data, thereby achieving the purpose of power saving.
  • not starting the DRX inactivity timer may be embodied in different control modes in different scenarios. If the current DRX inactivity timer is not in the running state, not starting the timer means keeping the current DRX inactivity timer in the inactive state. If the current DRX inactivity timer is in the running state, not starting the timer may include not restarting the DRX inactivity timer or stopping the DRX inactivity timer.
  • the restart timer in the embodiment of the present application refers to restarting timing from the configured duration of the timer.
  • not starting or stopping the DRX inactivity timer can be achieved by setting the duration of the DRX inactivity timer to zero. That is, regardless of the length of the original DRX inactivity timer configuration, when it is necessary not to start or stop the DRX inactivity timer, the duration of the DRX inactivity timer is set to 0, so that the DRX inactivity timer is not started or stopped.
  • the purpose of the active timer but in other situations where the DRX inactivity timer needs to be started or restarted, the original configured DRX inactivity timer duration is still used.
  • the method provided in the embodiment of the present application further includes:
  • the terminal device is configured with N HARQ processes, where, M is an integer greater than or equal to 1, N is an integer greater than or equal to 2, and M is less than N, then the discontinuous reception inactivity timer is started or restarted.
  • the method provided in an embodiment of the present application further includes:
  • the downlink control information indicates the data transmission of M HARQ processes
  • the data of at least one HARQ process in the data transmission of the M HARQ processes is newly transmitted, except that the terminal device is configured with M HARQ processes. Otherwise, start or restart the discontinuous reception inactivity timer, where M is an integer greater than or equal to 1.
  • the M HARQ processes used for data transmission indicated by the control information refer to M HARQ processes all used for uplink data transmission, or M HARQ processes all used for downlink data transmission, or both M HARQ processes transmitted on the side link.
  • the M HARQ processes for data transmission indicated by the control information refer to the M HARQ processes that are all used for uplink data transmission, or all are used for downlink data transmission Or M HARQ processes that are used for sidelink transmission.
  • the terminal device When the number of HARQ processes for data transmission indicated by the downlink control information is less than the number of HARQ processes configured by the terminal, it means that the terminal device still has available HARQ processes. At the same time, if there is a new transmission in the indicated HARQ process, there will be data in the future The possibility of transmission is also great, that is, there may be downlink information or downlink data that uses other HARQ processes to be sent to the terminal device. At this time, the DRX inactivity timer is started or restarted to allow the terminal device to start monitoring the downlink information or Downlink data to avoid losing information or data.
  • the terminal device monitors the physical downlink control channel at the same time when the terminal device starts or restarts the DRX inactivity timer, or after the timer is started or restarted.
  • the network device may send downlink information or downlink data to the terminal device
  • the downlink information is downlink control information
  • the downlink control information may be carried on the physical downlink control channel.
  • the onDurationTimer can be stopped.
  • Fig. 4 shows a flowchart when a terminal device implements the method provided in the embodiment of the present application.
  • the terminal equipment monitors the physical downlink control channel.
  • the terminal device obtains the downlink control information in the physical downlink control channel.
  • the terminal device does not start DRX inactivity Timer or stop DRX inactivity timer.
  • Fig. 5 shows a flowchart when a network device implements the method provided in the embodiment of the present application.
  • the network device sends downlink control information to the terminal device on the physical downlink control channel.
  • the DRX maintained for the terminal device is not started The inactivity timer or stop the DRX inactivity timer maintained for the terminal device.
  • FIG. 6 is a schematic diagram of another timer control method provided by an embodiment of the present application.
  • the bottom line information is downlink control information (DCI), and the terminal device is configured with two HARQ processes as an example for description.
  • DCI downlink control information
  • the terminal device is configured with two HARQ processes as an example for description.
  • This method can be used for terminal equipment or network equipment.
  • the timers in Figure 6 are their own DRX-related timers maintained internally by the terminal equipment.
  • the timers in Figure 6 Each timer is a DRX-related timer of the terminal device maintained by the network device for the terminal device.
  • the durations of the several timers involved in FIG. 6 may be pre-arranged between the network device and the terminal device, or the network device may be configured to the terminal device through configuration information.
  • onDurationTimer is the duration timer of the terminal device.
  • the network device can send downlink control information to the terminal device, and the terminal device monitors the physical downlink control channel.
  • DCI A is a piece of downlink control information sent by a network device to a terminal device.
  • the downlink control information is used to indicate (or schedule) the data transmission of two HARQ processes, which are HARQ 0 and HARQ 1 shown in Figure 6, respectively.
  • at least one of TB 0 and TB 1 is a new transmission.
  • the network device stops the onDurationTimer of the terminal device after completing the transmission of the DCI A.
  • the terminal device also stops the onDurationTimer maintained by itself after receiving the DCI A.
  • the terminal equipment is configured with two HARQ processes. DCI A schedules these two HARQ processes. Because there are no other HARQ processes available, the network equipment will no longer send downlink control information to the terminal equipment.
  • the network equipment and the terminal The device does not start the DRX inactivity timer. If there is no other timer status indicating that the terminal device needs to monitor the physical downlink control channel, the terminal device can stop monitoring the physical downlink control channel, thereby saving power.
  • the terminal device will send TB 0 and TB 1 on the time-frequency domain resources indicated in DCI A, correspondingly, The network equipment will receive TB 0 and TB 1 on the time-frequency domain resources indicated in DCI A.
  • TB 0 and TB 1 may be carried on a physical uplink shared channel, such as NPUSCH, and specifically may be NPUSCH format 1 (NPUSCH format 1).
  • the HARQ round-trip time timer in the example in Figure 6 is an uplink HARQ round-trip time timer (UL HARQ RTT Timer). In this case, both the network device and the terminal device determine whether the data transmission of each HARQ process ends according to the HARQ round trip time timer.
  • the network device will send TB 0 and TB 1 on the time-frequency domain resources indicated in DCI A, correspondingly, The terminal device will receive TB 0 and TB 1 on the time-frequency domain resources indicated in DCI A.
  • TB 0 and TB 1 can be carried on a physical downlink shared channel, such as NPDSCH.
  • the terminal can also send the ACK or NACK feedback of TB 0 and the ACK or NACK feedback of TB 1 to the network equipment on the time-frequency domain resources indicated in DCI A according to whether TB 0 and TB 1 are correctly received.
  • the network device receives the ACK or NACK feedback of TB 0 and TB1 on the time-frequency domain resources indicated in DCI A.
  • the ACK or NACK feedback of TB 0 and TB1 may be carried on a physical uplink shared channel, such as NPUSCH, and specifically may be NPUSCH format 2 (NPUSCH format 2).
  • NPUSCH format 2 NPUSCH format 2.
  • the TB 0 ACK/NACK and TB 1 ACK/NACK shown in Fig. 6 are only applicable when TB 0 and TB 1 are transmission blocks for downlink data transmission.
  • TB 0 and TB 1 are continuously transmitted in the time domain.
  • the time domain resources used by TB 0 and TB 1 may not be continuous.
  • HARQ 0 is TB
  • HARQ 1 is TB 1.
  • HARQ 0 can also be TB 1
  • HARQ 1 is TB 0.
  • the HARQ process numbers and the TB numbers in the embodiments of the present application are only exemplary descriptions, and this application does not limit them, nor does it limit the corresponding relationship between the HARQ process numbers and the TB numbers.
  • the HARQ round trip time timer for HARQ 0 is started.
  • the time point b is the time when the network device completes the transmission or reception of TB 0.
  • the time point b is the time when the terminal device completes the reception or transmission of TB 0.
  • the HARQ round trip time timer for HARQ 1 is started.
  • the time point c is the time when the network device completes the transmission or reception of TB1
  • the time point c is the time when the terminal device completes the reception or transmission of TB1.
  • the network device will no longer send downlink control information to the terminal device, and the terminal device will not monitor the physical downlink control channel.
  • the terminal device can monitor the physical downlink control channel, because the HARQ round trip time timer of HARQ 0 expires, which means that the data transmission of HARQ 0 has ended.
  • the terminal device may receive the downlink control information indicating the new transmission or retransmission of HARQ 0 during the operation of the DRX inactivity timer.
  • the HARQ round trip time timer of HARQ 1 expires, and the DRX inactivity timer is restarted.
  • the terminal equipment starts to monitor the physical downlink control channel.
  • DCI B is another downlink control information sent by the network device to the terminal device.
  • the downlink control information is used to indicate (or schedule) the data transmission of two HARQ processes, which are HARQ 0 and HARQ 1 shown in Figure 6, respectively.
  • HARQ 0 and HARQ 1 shown in Figure 6, respectively.
  • each HARQ process is used to send a transport block, namely TB 2 and TB 3 in Figure 6.
  • TB 2 and TB 3 may be two transmission blocks for uplink data transmission, or two transmission blocks for downlink data transmission.
  • For the specific transmission mode refer to the above transmission mode description of TB 0 and TB 1.
  • the network device completes the transmission of DCI B or the terminal device completes the reception of DCI B.
  • the terminal equipment is configured with two HARQ processes. DCI B schedules these two HARQ processes. Because there are no other HARQ processes available, the network equipment will no longer send downlink control information to the terminal equipment.
  • the network equipment and the terminal All devices stop the running DRX inactivity timer. If there are no other timers that indicate that the terminal device needs to monitor the physical downlink control channel, the terminal device can stop monitoring the physical downlink control channel to save power.
  • FIG. 7 is a schematic diagram of another timer control method provided by an embodiment of the present application.
  • the terminal device will maintain a HARQ round trip time timer to run for each HARQ process, and the network device will also maintain a HARQ round trip time timer for each HARQ process of the terminal device accordingly.
  • the terminal device and the network device are using the HARQ process for data transmission.
  • the HARQ round-trip time timer expires, it means that the data transmission on the HARQ process ends, and the DRX inactivity timer will start or restart. Therefore, the length of the HARQ round-trip time timer determines when to start or restart the DRX inactivity timer .
  • this method can also be used to control other timers with similar functions to the HARQ round trip timer.
  • HARQ 0 and HARQ 1 scheduled by DCI A are two HARQ processes used for downlink data transmission.
  • M is the transmission duration of TB 1, which can be identified by the number of subframes.
  • M can be from the beginning of the first subframe of transmission of TB1 to the end of the last subframe of transmission of TB1 (the last subframe of transmission of TB1 is recorded as subframe n), that is, M is equal to the value used to transmit TB1 Number of subframes.
  • M may also start from the last subframe of transmitting TB 0 to the end of subframe n, at this time M is equal to the number of subframes used for transmitting TB 1 plus 1.
  • k is the interval between subframe n and the first subframe used to transmit the ACK or NACK feedback of TB 0, and k can also be represented by the number of subframes.
  • X represents the X subframes after the last subframe (denoted as subframe p) in which the ACK or NACK feedback of TB 1 is transmitted.
  • the value of X mainly considers the processing of the physical uplink shared channel carrying ACK or NACK by the network equipment, for example NPUSCH, the time required.
  • X may also be X subframes after subframe p-1.
  • deltaPDCCH is the interval between the Xth subframe after subframe p or subframe p-1 and the first subframe of the next physical downlink control channel timing, because subframe p or X+th subframe after subframe p-1
  • One subframe is not necessarily one physical downlink control channel opportunity.
  • a physical downlink control channel opportunity (PDCCH occasion) is the starting position of a search space (search space).
  • the HARQ round trip time timer of HARQ 0 can be started when the transmission of TB 1 is completed, for example, the time point b shown in FIG. 7.
  • the length of the HARQ round trip time timer of HARQ 0 M+k+N+X+deltaPDCCH.
  • the HARQ round trip time timer of HARQ 0 can be started when the transmission of TB 0 is completed, for example, as shown in Figure 7 Time point a.
  • the value of X can be 1, 2, 3, or 4.
  • the starting position of the HARQ round-trip time timer of HARQ 0 may be the same as the starting time point of the HARQ round-trip time timer of HARQ 1 (time point b as shown in FIG. 7), or may be different.
  • the time point of the HARQ round trip time timer of HARQ 0 can be the same as the time point of the HARQ round trip time timer of HARQ 1 (time point c shown in Figure 7).
  • the time point of the timeout may be different. the same.
  • the length of the HARQ round trip time timer of HARQ 0 may be the same as the length of the HARQ round trip time timer of HARQ 1, or may be different.
  • the duration of the round-trip time timer of HARQ 0 and HARQ 1 is different, which can be achieved by setting the value of X to be different. Of course, the value of X can also be the same.
  • FIG. 8 is a schematic diagram of still another timer control method provided by an embodiment of the present application.
  • the method is used as an example for the HARQ round-trip time timer for description. Similarly, this method can also be used to control other timers with similar functions to the HARQ round trip timer.
  • HARQ 0 and HARQ 1 scheduled by DCI A are two HARQ processes used for uplink data transmission.
  • TB 0 and TB 1 are transmitted through the physical uplink shared channel, for example, NPUSCH format 1.
  • the terminal equipment and the network equipment will also maintain a HARQ round trip time timer for each HARQ process.
  • terminal equipment and network equipment are using the HARQ process for uplink data transmission.
  • the length of the HARQ round-trip time timer determines when to start or restart the DRX inactivity timer.
  • M is the transmission duration of TB 1, that is, from the beginning of the first subframe of transmitting TB 1 to the end of the last subframe of transmitting TB 1 (the last subframe of transmitting TB 1 is recorded as subframe n ), that is, M is equal to the number of subframes used to transmit TB1.
  • M may also start from the last subframe of transmitting TB 0 to the end of subframe n, that is, M is equal to the number of subframes used for transmitting TB 1 plus 1.
  • X is the X subframes after the last subframe (denoted as subframe p) of the transmission of TB 1, and the value of X mainly considers the time required for the network device to process the physical uplink shared channel, such as NPUSCH.
  • X may also be X subframes after subframe p-1.
  • deltaPDCCH is the interval between the Xth subframe after subframe p or subframe p-1 and the first subframe of the next physical downlink control channel timing, because subframe p or X+th subframe after subframe p-1
  • One subframe is not necessarily one physical downlink control channel opportunity.
  • the timer can be started when the transmission of TB 1 is completed, for example, at the time point b shown in FIG. 8.
  • the length of the HARQ round trip time timer of HARQ 0 M+X+deltaPDCCH, at this time, the HARQ round trip time timer of HARQ 0 can be started when the transmission of TB 0 is completed, for example, the time point a shown in FIG. 8.
  • the value of X mentioned above can be 1, 2, 3 or 4.
  • the value of X can also be related to M. For example, when M is greater than or equal to the threshold Z, the value of X is X1. When M is less than the threshold Z, X takes the value X2, where Z can be 2 or 3, and X1 can be Is 1, 2, 3 or 4, X2 can be 1, 2, 3, or 4, and X1 is smaller than X2.
  • the value of X can be 1, 2, 3 or 4.
  • the value of X can also be related to M. For example, when M is greater than or equal to the threshold Z, the value of X is X1, and when M is less than the threshold Z, X takes the value X2, where Z can be 2 or 3, X1 It can be 1, 2, 3, or 4, X2 can be 1, 2, 3, or 4, and X1 is smaller than X2.
  • the starting position of the HARQ round-trip time timer of HARQ 0 may be the same as the starting time point of the HARQ round-trip time timer of HARQ 1 (time point b as shown in FIG. 8), or may be different.
  • the time point of the HARQ round trip time timer of HARQ 0 can be the same as the time point of the HARQ round trip time timer of HARQ 1 (time point c shown in Figure 8), when the HARQ round trip time timer of HARQ 0
  • the duration of the HARQ round-trip time timer of HARQ 1 is set to be different and/or the starting time of the HARQ round-trip time timer of HARQ 0 and the HARQ round-trip time timer of HARQ 1 are different
  • the time point of the timeout may be different. the same.
  • the length of the HARQ round trip time timer of HARQ 0 may be the same as the length of the HARQ round trip time timer of HARQ 1, or may be different.
  • the duration of the round-trip time timer of HARQ 0 and HARQ 1 is different, which can be achieved by setting the value of X to be different. Of course, the value of X can also be the same.
  • HARQ round trip time timer can also be called uplink HARQ round trip time timer (UL HARQ RTT Timer).
  • the timer control method provided in Fig. 7 or Fig. 8 adjusts the timeout point of the HARQ round-trip time fixed time to the beginning of the next physical downlink control channel opportunity, avoiding when the timeout point of the HARQ round-trip time timer falls on The time period of non-physical downlink control channel timing, or the time period when the terminal device is transmitting uplink data. During these time periods, the network device will not send downlink information or downlink data to the terminal device, and the terminal device does not need to be in these time periods. Monitor downlink information or downlink data within a time period.
  • each communication device such as a terminal device, a network device, etc.
  • each communication device may include hardware structures and/or software modules corresponding to each function in order to implement the above functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Different methods can be used for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of this application.
  • Figure 9 shows a schematic structural diagram of a possible communication device involved in the above embodiment
  • the communication apparatus may be a terminal device, for example, may be a user equipment (UE).
  • the communication device may also be a device or a circuit structure built in a terminal device, for example, it may be a circuit system, a chip, or a chip system.
  • the chip system described in the embodiment of the present application includes at least one chip, and may also include other discrete devices or circuit structures.
  • the communication device may also be a network device, for example, it may be a base station or a network side device for wireless communication with a terminal device.
  • the communication device may also be a device or a circuit structure built in a network device, for example, it may be a circuit system, a chip, or a chip system.
  • the chip system described in the embodiment of the present application includes at least one chip, and may also include other discrete devices or circuit structures.
  • the communication device includes at least one processor 901, and the processor 901 is configured to couple with a memory and execute instructions stored in the memory to implement the instructions provided in the embodiments of the present application.
  • the processor 901 may execute the code in the memory to realize the control operation of the DRX-related timer, for example, monitor the physical downlink control channel, and obtain the downlink control information in the physical downlink control channel. If the downlink control information indicates N HARQ processes
  • the terminal device is configured with N HARQ processes, where N is an integer greater than or equal to 2, does not start the DRX inactivity timer or stops the DRX inactivity timer, etc.
  • controlling the transmission of downlink control information on the physical downlink control channel if the downlink control information indicates data transmission of N HARQ processes and the terminal device is configured with N HARQ processes, where N is greater than or equal to 2 Integer, do not start the DRX inactivity timer maintained for the terminal device or stop the DRX inactivity timer maintained for the terminal device, etc.
  • the communication device may further include a memory 902, which is coupled to the aforementioned at least one processor 901 and is configured to store program instructions.
  • the memory 902 may also be used to store information and/or data according to the needs of the communication device, for example, to store timer configuration information or timer-related data related to the embodiment of the present application.
  • the communication device may further include a transceiver 903, and the transceiver 903 is configured to support the communication device to send or receive information or data that needs to be transmitted.
  • the transceiver 903 can be used to send downlink control information to the terminal device, and when the communication device is a terminal device, the transceiver 903 can be used to receive downlink control information sent by the network device. .
  • the communication device when the communication device is a terminal device or a network device, the communication device may further include at least one antenna 904 for receiving or sending wireless signals.
  • the at least one processor 901 may be a processing device with a circuit structure or a processing device integrated in a chip.
  • the memory 902 may be a storage medium or storage device integrated inside the chip, or may be an independent storage medium or storage device deployed outside the chip.
  • the transceiver device 903 can be implemented in a specific circuit structure, chip pins, and other forms.
  • the at least one processor 904 of the aforementioned communication device may be a central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processor (digital signal processor, DSP), and an application-specific integrated circuit (application-specific integrated circuit).
  • circuit ASIC
  • FPGA field programmable gate array
  • the at least one processor 904 may also be a combination that implements computing functions, for example, including a microprocessor or a combination of more than one microprocessor, a combination of a digital signal processor and a microprocessor, and so on.
  • FIG. 9 only shows the simplified design of the communication device provided by the embodiment of the present application.
  • the communication device may also include any number of transceivers, transmitters, receivers, processors, memories, etc., and may also include other required software or hardware structures. This application does not limit the specific components of the communication device. The concrete realization form of the structure.
  • the steps of the method or algorithm described in conjunction with the disclosure of this application can be implemented in a hardware manner, or implemented in a manner that at least one processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (erasable programmable read-only memory, EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard drives, mobile hard drives, compact discs read-only memory, CDs -ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in an application specific integrated circuit.
  • the application specific integrated circuit may be located in the communication device.
  • the processor and the storage medium may also exist as discrete components in the communication device.
  • the functions described in this application can be implemented by hardware, software, firmware or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Abstract

本申请涉及无线通信技术领域，尤其涉及一种定时器控制的方法、装置和系统。本申请提供了一种定时器控制的方法，包括在下行控制信息指示N个混合自动重传请求HARQ进程的数据传输，且终端设备配置了N个HARQ进程的时候，其中N为大于或等于2的整数，不启动非连续接收不活动定时器或者停止非连续接收不活动定时器。本申请旨在通过定时器的控制，减少终端设备监测下行信道或下行数据的时间，从而减少终端设备的耗电。

Description

一种定时器控制方法、装置及系统 技术领域
本申请涉及无线通信技术领域，尤其涉及无线通信系统中的定时器控制方法、装置和系统。
背景技术
在无线通信系统中，为了节省终端设备的耗电提升终端设备的续航能力，通常会使用非连续接收(discontinuous reception，DRX)功能。在使用DRX功能时，终端设备仅需要在系统规定的时间段内监测或者接收下行信息或下行数据，在其他时间段内，终端设备可以无需监测或者接收下行信息或下行数据，甚至关闭或去激活全部或部分接收功能，从而达到省电的目的。
终端设备会维护一些与DRX功能相关的定时器，并根据定时器的状态，例如，定时器运行(run)或者定时器失效(expired)，来确定是否需要监测或者接收下行信息或下行数据。网络设备也会为终端设备维护相应的定时器，并根据定时器的状态确定是否向终端设备发送下行信息或下行数据。
混合自动重传请求(hybrid automatic repeat request，HARQ)，是一种结合纠错(correction)与自动重传请求方法的技术，通过数据或信息的接收端反馈应答消息(acknowledge，ACK)或否定应答(negative acknowledgement，NACK)，数据或信息的发送端可以决定是否需要进重传。
随着终端设备能力的提升，终端设备可以支持的HARQ进程(HARQ process)数越来越多，在终端设备可以支持多个HARQ进程的情况下，如何控制DRX相关的定时器，使得终端设备可以更好的利用DRX技术延长续航时间，成为亟待解决的问题。
发明内容
本申请实施例提供一种定时器控制方法、装置及系统，用以减少终端设备的耗电，提升终端设备的续航能力。
第一方面，本申请实施例提供一种定时器控制方法，该方法可应用于无线通信装置，该无线通信装置可以是终端设备，也可以是终端设备中的结构或装置，例如，芯片、芯片系统或者电路系统等。该方法包括：监测物理下行控制信道，获取所述物理下行控制信道中的下行控制信息，若所述下行控制信息指示N个混合自动重传请求HARQ进程的数据传输，且终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，则不启动非连续接收不活动定时器或者停止非连续接收不活动定时器。当下行控制信息指示的用于数据传输的HARQ进程的数量等于终端设备配置的HARQ进程数时，说明终端设备已经没有HARQ可以用于数据传输，因此网络设备也不会再使用其他HARQ进程向终端设备发送下行控制信息，此时，终端设备可以不启动或者停止非连续接收不活动定时器，从而避免因为非连续接收不活动定时器处于运行状态而使终端设备监测物理下行控制信道。
在一个可能的设计中，所述方法还包括若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，且所述终端设备 配置了N个HARQ进程，其中，M为大于或等于1的整数，N为大于或等于2的整数，且M小于N，则启动或重启所述非连续接收不活动定时器。在启动或重启非连续接收不活动定时器的条件中仅包含仍然存在可用HARQ进程的情况，可以避免无其他HARQ进程可用时启动非连续接收不活动定时器，从而进一步避免因为非连续接收不活动定时器处于运行状态而使终端设备监测物理下行控制信道。
在一个可能的设计中，所述方法还包括若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，除了所述终端设备配置了M个HARQ进程的情况之外，启动或重启所述非连续接收不活动定时器，其中M为大于或等于1的整数。在启动或重启非连续接收不活动定时器的条件中排除无其他HARQ进程可用时启动非连续接收不活动定时器，从而进一步避免因为非连续接收不活动定时器处于运行状态而使终端设备监测物理下行控制信道。
在一个可能的设计中，所述下行控制信息指示M个HARQ进程的数据传输，包括：所述下行控制信息指示M个HARQ进程的上行数据传输，或者所述下行控制信息指示M个HARQ进程的下行数据传输。
在一个可能的设计中，所述N小于或等于所述终端设备支持的HARQ进程数。可选的，终端设备可以将其支持的HARQ进程数上报给网络设备，以便网络设备根据终端设备的支持能力配置HARQ进程数。
在一个可能的设计中，所述终端设备配置了N个HARQ进程，包括：所述终端设备配置了N个上行HARQ进程和/或配置了N个下行HARQ进程。
在一个可能的设计中，所述下行控制信息指示N个混合自动重传请求HARQ进程的数据传输，包括：所述下行控制信息指示N个HARQ进程的上行数据传输，或者所述下行控制信息指示N个HARQ进程的下行数据传输。
在一个可能的设计中，所述方法还包括启动或重启所述非连续接收不活动定时器后，监测物理下行控制信道。
第二方面，本申请实施例提供一种定时器控制方法，该方法可应用于无线通信装置，该无线通信装置可以是网络设备，也可以是网络设备中的结构或装置，例如，芯片、芯片系统或者电路系统等。该方法包括：在物理下行控制信道上发送下行控制信息给终端设备，若所述下行控制信息指示N个混合自动重传请求HARQ进程的数据传输，且所述终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，则不启动为所述终端设备维护的非连续接收不活动定时器或者停止为所述终端设备维护的非连续接收不活动定时器。网络设备可以为终端设备维护相应的DRX相关的定时器，以便通信双方状态的保持一致。网络设备可以根据为终端设备维护的非连续接收不活动定时器的状态，确定是否向终端设备发送下行控制信息。
一种可能的设计中，所述方法还包括若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，且所述终端设备配置了N个HARQ进程，其中，M为大于或等于1的整数，N为大于或等于2的整数，且M小于N，则启动或重启为所述终端设备维护的所述非连续接收不活动定时器。
一种可能的设计中，所述方法还包括若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，除了所述终端设备配置了M个HARQ进程的情况之外，启动或重启为所述终端设备维护的所述非连续接收不活动定时器，其中M为大于或等于1的整数。
一种可能的设计中，所述下行控制信息指示M个HARQ进程的数据传输，包括：所述下行 控制信息指示M个HARQ进程的上行数据传输，或者所述下行控制信息指示M个HARQ进程的下行数据传输。
一种可能的设计中，所述N小于或等于所述终端设备支持的HARQ进程数。
一种可能的设计中，所述终端设备配置了N个HARQ进程，包括：所述终端设备配置了N个上行HARQ进程和/或配置了N个下行HARQ进程。
一种可能的设计中，所述下行控制信息指示N个HARQ进程的数据传输，包括：所述下行控制信息指示N个HARQ进程的上行数据传输，或者所述下行控制信息指示N个HARQ进程的下行数据传输。
一种可能的设计中，所述方法还包括：在启动或重启为所述终端设备维护的所述非连续接收不活动定时器后，向所述终端设备发送承载在物理下行控制信道上的下行控制信息。第三方面，本申请实施例提供一种通信装置，该通信装置可以是终端设备，也可以是设置在终端设备中的结构或装置，例如，芯片、芯片系统或者电路系统等。该通信装置包括至少一个处理器，所述至少一个处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如第一方面或第一方面任一种可能的设计中所述的方法。
在一个可能的设计中，所述通信装置还包括所述存储器。
在一个可能的设计中，所述通信装置还可以包括收发装置，用于支持所述通信装置进行信息或者数据的传输。
第四方面，本申请实施例提供一种通信装置，该通信装置可以是网络设备，也可以是设置在网络设备中的结构或装置，例如，芯片、芯片系统或者电路系统等。该通信装置包括至少一个处理器，所述至少一个处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如第二方面或第二方面任一种可能的设计中所述的方法。
在一个可能的设计中，所述通信装置还包括所述存储器。
在一个可能的设计中，所述通信装置还可以包括收发装置，用于支持所述通信装置进行信息或者数据的传输。
第五方面，本申请实施例提供一种通信装置，用于实现上述第一方面或第一方面中的任意一种可能的设计中的方法，包括相应的功能模块，例如包括处理单元、收发单元等，分别用于实现以上方法中的步骤。
第六方面，本申请实施例提供一种通信装置，用于实现上述第二方面或第二方面中的任意一种可能的设计中的方法，包括相应的功能模块，例如包括处理单元、收发单元等，分别用于实现以上方法中的步骤。
第七方面，本申请实施例提供一种通信系统，该系统包括上述第三方面或第三方面的任一可能的设计中的终端设备，和，上述第四方面或第四方面的任一可能的设计中的网络设备。可选的，所述通信系统可以为窄带物联网系统。
第八方面，本申请实施例提供一种通信系统，该系统包括上述第五方面的通信装置，和，上述第六方面的通信装置。可选的，所述通信系统可以为窄带物联网系统。
第九方面，本申请实施例提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现第一方面以及第一方面中的任意一种可能的设计中的方法，或者第二方面以及第二方面中的任意一种可能的设计中的方法。
第十方面，本申请实施例提供一种计算机程序产品，当所述计算机程序产品被计算机运行时，可以使得计算机实现上述第一方面以及第一方面中的任意一种可能的设计中的方法，或者第二方面以及第二方面中的任意一种可能的设计中的方法。
相较于现有技术，本申请描述了一种定时器控制方法、装置和系统，旨在通过定时器的控制减少终端设备监测下行信息或下行数据的时间，从而减少终端设备的耗电。
附图说明
图1为本申请实施例提供的一种通信系统示意图；
图2为本申请实施例提供的一种DRX周期示意图；
图3为本申请实施例提供的一种定时器控制的方法示意图；
图4为本申请实施例提供的一种定时器控制的方法的流程图；
图5为本申请实施例提供的另一种定时器控制的方法的流程图；
图6为本申请实施例提供的另一种定时器控制的方法示意图；
图7为本申请实施例提供的又一种定时器控制的方法示意图；
图8为本申请实施例提供的再一种定时器控制的方法示意图；
图9为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例可以适用于各类通信系统，例如，可以适用于窄带物联网(Narrowband Internet of Things，NB-IoT)系统、物联网(Internet of Things，IoT)系统、机器类通信(machine type communication，MTC)系统，增强型机器类通信(enhanced Machine Type Communication，eMTC)系统、长期演进(long term evolution，LTE)系统、演进的LTE系统(LTE-Advanced，LTE-A)、第五代移动通信技术(fifth generation，5G)或新无线(new radio，NR)系统、或未来通信发展中出现的新的通信系统等。只要通信系统中存在通信装置需要使用DRX技术以及HARQ技术，或者类似于DRX或者HARQ的通信技术，并需要维护与DRX相关的定时器，均可以采用本申请实施例提供的定时器控制方法。
图1为本申请实施例可应用的一种通信系统，在图1所示出的通信系统中包括网络设备和六个终端设备，终端设备1-终端设备6中的任一终端设备可以向网络设备发送上行信息或上行数据，也可以接收网络设备发送的下行信息或下行数据。此外，终端设备之间还可以组成子系统，并进行信息或数据的交互，例如，终端设备5和终端设备4之间的无线通信。图1仅是一种示意图，并不对通信系统的类型，以及通信系统内包括的设备的数量、类型等进行具体限定。本申请实施例描述的网络架构以及业务场景是为了说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例中的术语“系统”和“网络”可被互换使用，以及术语“字段”和“域”可被互换使用。“多个”是指两个或两个以上，本申请实施例中也可以将“多个”理解为“至少两个”。“至少一个”，可理解为一个或多个，例如理解为一个、两个或更多个。例如，包括至少一个，是指包括一个、两个或更多个，而且不限制包括的是哪几个，例如，包括A、B和C中的至少一个，那么包括的可以是A，B，C，A和B，A和C，B和C，或A和B和C。“至少两个”，可理解为两个或更多个。同理，对于“至少一种”等描述的理解，也是类似的。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独 存在A，同时存在A和B，或单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。除非有相反的说明，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。
以下，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
1)终端设备，包括向用户提供语音和/或数据连通性的通信装置。该通信装置可以经无线接入网(radio access network，RAN)与网络设备，例如核心网设备，进行通信，交换语音和/或数据。该终端设备可以包括用户设备(user equipment，UE)、无线终端设备、移动终端设备、用户单元(subscriber unit)、用户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point，AP)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、用户装备(user device)、移动电话(或称为“蜂窝”电话)、具有移动终端设备的计算机，便携式、袖珍式、手持式、计算机内置的或者车载的移动装置、智能穿戴式设备、个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、或个人数字助理(personal digital assistant，PDA)等设备。该通信装置还可以包括各种能力受限设备，例如功耗较低的设备、存储能力有限的设备，或计算能力有限的设备等，例如，条码识别装置、射频识别(radio frequency identification，RFID)装置、传感装置、全球定位系统(global positioning system，GPS)装置、激光扫描装置等信息传感设备。该通信装置还可以包括内置于各种终端设备(例如，上述任一种设备)中的结构或装置，例如，芯片、芯片系统或者电路系统等，其中，芯片系统包括至少一个芯片，还可以包括其他分立的电路器件。
2)网络设备，也可以称为网络侧设备，包括与终端设备进行无线通信的，部署在网络侧的通信装置。该通信装置可以是接入网设备或者核心网设备，或者内置于网络设备中的结构或装置，例如，芯片、芯片系统或者电路系统等，其中，芯片系统包括至少一个芯片，还可以包括其他分立的电路器件。该通信装置可以包括各种形式的基站、接入点等、或路由器等。例如，该通信装置可以包括长期演进(long term evolution，LTE)系统或演进的LTE系统(LTE-Advanced，LTE-A)中的演进型基站(evolutional NodeB，eNB或e-NodeB)，也可以包括第五代移动通信技术(fifth generation，5G)或新无线(new radio，NR)系统中的下一代节点B(next generation nodeB，gNB)，还可以包括接入网(radio access network，RAN)中的集中式单元(centralized unit，CU)或分布式单元(distributed unit，DU)等等。
3)非连续接收(discontinuous reception，DRX)，在本申请实施例中，终端设备可以根据DRX周期(DRX cycle)确定是否需要监测或者接收下行信息或数据。如图2所示，一个DRX周期包括持续时间(On Duration)和非连续接收机会(Opportunity for DRX)两个时间段。在持续时间内，如果有空闲的HARQ进程未被使用，则终端设备会启动持续时间定时器(例如，OnDurationTimer)，持续时间定时器运行的时间为活动时间(active time)，终端设备通常需要在活动时间内监测(monitor)或接收下行信息或下行数据，例如监测物理下行控制信道。在非连续接收机会时间段内，终端设备可以不监测下行信息或下行数据，从而达到省电的目的。
4)非连续接收不活动定时器(DRX inactivity timer)，是一个与DRX相关的定时器， 该定时器运行的时间为活动时间，终端设备需要监测或者接收下行信息或者下行数据。
5)物理下行控制信道，包括用于发送下行控制信息的信道。包括但不限于LTE、LTE-A、5G或NR系统中的下行控制信道，如物理下行控制信道(physical downlink control channel，PDCCH)，NB-IoT系统中的下行控制信道，如窄带物理下行控制信道(narrowband physical downlink control channel，NPDCCH)，MTC或eMTC系统中的下行控制信道，如MTC物理下行控制信道(MTC physical downlink control channel，MPDCCH)，等等。物理下行共享信道，包括用于发送下行信息或者下行业务数据的信道。包括但不限于LTE、LTE-A、5G或NR系统中的下行共享信道，如物理下行共享信道(physical downlink shared channel，PDSCH)，NB-IoT系统中的下行共享信道，如窄带物理下行共享信道(narrowband physical downlink shared channel，NPDSCH)，MTC或eMTC系统中的下行共享信道，如MTC物理下行共享信道(MTC physical downlink shared channel，MPDSCH)，等等。物理上行共享信道，包括用于发送上行信息或者上行业务数据的信道。包括但不限于LTE、LTE-A、5G或NR系统中的上行共享信道，如物理上行共享信道(physical uplink shared channel，PUSCH)，NB-IoT系统中的上行共享信道，如窄带物理上行共享信道(narrowband physical uplink shared channel，NPUSCH)，MTC或eMTC系统中的上行共享信道，如MTC物理上行共享信道(MTC physical uplink shared channel，MPUSCH)，等等。
6)下行控制信息，包括用于承载下行控制消息的信息。该下行控制信息可以用于发送网络设备给终端设备的配置信息，或者用于调度上行数据或者下行数据的传输。下行控制信息包括但不限于NB-IoT、MTC或eMTC、LTE、LTE-A、5G或NR等系统中的下行控制信息(downlink control information，DCI)。下行控制信息可以承载在物理下行控制信道上。
7)混合自动重传请求进程(HARQ process)，是从网络设备调度一次数据传输到数据发送端接收到ACK或NACK反馈的过程，或者是从网络设备调度一次数据传输到一个预定的时间长度结束的过程。HARQ进程数是指并发的HARQ进程的数目。对于下行数据传输的HARQ进程，终端设备通常会反馈ACK或者NACK给网络设备，网络设备和终端设备之间可以预定一个时间长度，该时间长度结束，则终端设备可以认定一个HARQ进程的一次数据传输的结束，该时间长度的判断可以通过定时器来实现，例如，使用HARQ往返时间定时器(HARQ round trip time timer，HARQ RTT timer)来判断该时间长度是否结束。对于上行数据传输的HARQ进程，网络设备可以不反馈ACK或NACK给终端设备，而是直接通过调度实现数据的新传或者重传，网络设备和终端设备可以预定一个时间长度，作为一个HRAQ进程的一次数据传输的结束，该时间长度的判断可以通过定时器来实现，例如，使用上行混合自动重传请求往返时延定时器(uplink hybrid automatic repeat request round trip time timer，UL HARQ RTT timer)来判断该时间长度是否结束。
8)传输块(transport block，TB)，是指数据传输过程中的净荷(payload)。下行控制信息可以用于调度至少一个传输块的数据传输。一个传输块的传输会使用一个HARQ进程。一个HARQ进程的一次数据传输可以包含至少一个传输块。
9)数据传输，包括上行数据传输、下行数据传输或侧行链路(sidelink)数据传输，也包括数据的新传或者重传。通常，上行数据传输是指终端设备向网络设备发送数据或消息，下行数据传输是指网络设备向终端设备发送数据或消息，侧行链路数据传输是指终端设备之间进行的数据或消息的发送。数据的新传是指一个传输块的首次传输，数据的重传是指一个传输块的非首次传输。
10)本申请实施例中所述的“信息”包括控制信息、配置信息、信令信息等用于网络设 备和终端设备之间或者终端设备与终端设备之间传输的信息。本申请实施例中所述的“数据”包括网络设备与终端设备之间或者终端设备与终端设备之间传输的业务数据等。
以下，基于更多的附图，对本申请提供的实施例进行描述。
当终端设备仅支持一个HARQ进程的时候，终端设备可以根据该HARQ进程的数据传输状态，例如，是否完成了ACK或NACK的反馈、是否到达了约定的时间长度、或者是否需要重传等，并结合DRX周期所处的时间段来决定是否监测下行信息或下行数据。
随着无线通信技术的发展，终端设备可以支持的HARQ进程数不断提升，且在一个下行控制信息中也可以调度多于一个的HARQ进程。终端设备要根据多个并发HARQ进程的状态并结合DRX周期所处的时间段来决定是否监测下行信息或者下行数据。基于此，本申请实施例提供了一种定时器的控制方法，该定时器与DRX相关，通过该方法，终端设备可以根据下行控制信息中调度的HARQ进程数以及配置的HARQ进程数来控制该定时器，从而更加简单的确定是否需要监测下行信息或者下行数据，进一步减少终端设备的耗电，提升终端设备的续航能力。
下面，以下行信息为下行控制信息，与DRX相关的定时器为非连续接收不活动定时器为例，介绍本申请所提供的具体实施例。可以理解的，本申请提供的实施例还可以应用于对其他下行信息或下行数据的监测控制，也可以应用于其他与DRX相关的定时器控制。
图3为本申请提供的一种定时器控制的方法示意图。该方法可以应用于终端设备或者网络设备。当该方法应用于终端设备时，非连续接收不活动定时器(即DRX不活动定时器)是终端设备内部维护的用于自身DRX机制的定时器。当该方法应用于网络设备时，DRX不活动定时器，是网络设备针对具体的终端设备维护的用于判断终端设备DRX状态的定时器，本申请实施例中也称为“为终端设备维护的DRX不活动定时器”。
图3中，DCI为指示用于数据传输的N个HARQ进程的下行控制信息，也可以理解为该DCI指示或者调度了N个HARQ进程用于数据传输。图3中，HARQ 0为使用第一个HARQ进行的数据传输，HARQ N-1为使用第N个HARQ进行的数据传输，其中，使用N个HARQ进行的数据传输之间在时域上可以连续也可以不连续。
该方法包括：如果下行控制信息指示N个HARQ进程的数据传输，且终端配置了N个HARQ进程，其中N为大于或等于2的整数，则不启动DRX不活动定时器或者停止DRX不活动定时器。
具体的，不启动或停止DRX不活动定时器的动作，可以确定了下行控制信息指示的HARQ进程数就执行。其具体执行的时间点，可以在下行控制信息发送或接收或解析(例如，译码)的过程中，也可以是完成了下行控制信息的发送或接收或解析之后再执行。本申请实施例中，以完成下行控制信息的发送的时刻或者完成下行控制信息的接收的时刻作为不启动或者停止DRX不活动定时器动作执行的时间点为例进行说明。
可选的，该方法还可以包括：确定下行控制信息指示的用于数据传输的HARQ进程的个数以及终端设备配置的HARQ进程数。
当该方法应用于网络设备时，确定下行控制信息指示的用于数据传输的HARQ进程的个数可以在网络设备确定对终端设备的调度信息，或者确定或生成下行控制信息的同时就完成。确定终端设备配置的HARQ进程个数，也可以在网络设备确定该终端设备的HARQ配置信息，或者向该终端设备发送HARQ配置信息的时候就完成。
当该方法应用于终端设备时，确定终端设备配置的HARQ进程个数，也可以在确定自身的HARQ配置信息，或者在接收到网络设备向终端设备发送的HARQ配置信息的时候就完成。
在本申请实施例中，下行控制信息指示的用于数据传输的HARQ进程数，可以是一个下行控制信息中所指示的用于数据传输的HARQ进程的个数，一个下行控制信息是指终端设备所接收到的内容相同的下行控制信息，或者可以理解为是物理下行控制信道中的一个下行控制信息。也可以是在多个下行控制信息中所指示的用于数据传输的HARQ进程的个数，例如，当终端设备配置了两个HARQ进程，当终端设备接收到了两个不同的下行控制信息，这两个下行控制信息分别指示了使用第一个HARQ进程进行上行数据传输和使用第二HARQ进程进行上行数据传输，则可以认为这两个下行控制信息指示了两个用于数据传输的HARQ进程。
下行控制信息中指示的数据传输，可以是上行数据传输、下行数据传输或者侧行链路数据传输。
下行控制信息可以指示N个HARQ进程的数据传输，包括：下行控制信息指示至少N个传输块的传输，该至少N个传输块中的每一个传输块使用一个HARQ进程进行传输，每个HARQ进程可以用于传输至少N个传输块中的至少一个传输块。至少N个传输块的中的任一个传输块的传输可以是新传也可以是重传。不同的传输块可以使用不同的HARQ进程进行传输，也可以使用相同的HARQ进程进行传输。
可选的，所述控制信息指示的用于数据传输的N个HARQ进程，是指均用于上行数据传输的N个HARQ进程，或者均用于下行数据传输的N个HARQ进程，或者均用于侧行链路传输的N个HARQ进程。
在本申请实施例中，终端设备配置的HARQ进程数，是指网络设备为终端设备配置的，或者网络设备和终端约定的，终端设备可以使用的同时并发的HARQ进程的个数。也就是说，终端设备在同一时间段内，可以同时使用的HARQ进程的个数，但是在这一时间段内，不同的HARQ进程可以处于不同的状态，例如，如果终端设备配置了两个HARQ进程，那么同时使用这两个HARQ进程的时候，可以一个HARQ进程处在数据传输的过程中，而另一个HARQ进程处于等待ACK或NACK反馈的过程中。
终端设备配置的HARQ进程数，可以是上行HARQ进程数，也可以是下行HARQ进程数，还可以是侧行链路HARQ进程数。也就是说，当终端设备了N个HARQ进程，可以理解为，终端设备在上行可以使用N个HARQ进程，和/或终端设备在下行可以使用N个HARQ进程。其中，上行数据传输和下行数据传输可以在同一时间段内进行，例如全双工的工作方式，也可以在不同时间段内进行，例如，半双工的工作方式。
可选的，终端设备配置的HARQ进程数，小于或者等于终端设备支持的HARQ进程数。终端设备支持的HARQ进程数，是指终端设备本身所具有的能力，也就是终端设备可以支持的最多的同时并发的HARQ进程个数。终端设备可以通过信令或者消息将自己支持的HARQ进程数作为能力信息上报给网络设备，网络设备可以根据终端设备上报的该能力信息，为终端设备配置HARQ进程数。
不启动或者停止DRX不活动定时器，可以理解为使该DRX不活动定时器处于不运行状态，也就是终端设备不会因为该DRX不活动定时器而进行下行信息或者下行数据的监测，如果此时其他DRX相关的定时器也没有指示终端设备需要处于活动时间或者需要监测下行信息或者下行数据，则终端设备可以停止监测下行信息或者下行数据，从而达到省电的目的。
当终端设备配置了N个HARQ进程，而下行控制信息也指示了N个HARQ进程的数据传输，则说明这N个HARQ进程已经全部被调度(或者说被占用)，终端设备此时已经不能再用更多的HARQ进程进行数据传输了。具体而言，如果这N个HARQ进程均用于上行数据传输，则说明不会再有下行信息调度终端设备使用其他HARQ进程进行上行数据发送，如果这N个HARQ 进程均用于下行数据传输，则说明不会再有使用其他HARQ进程的下行信息或者下行数据发送给该终端设备。因此，如果此时DRX不活动定时器正在运行，终端设备可以停止DRX不活动定时器，以避免终端设备因为DRX不活动定时器还在运行而继续监测下行信息或者下行数据。可选的，停止DRX不活动定时器，并不意味着停止监测下行信息或者下行数据，终端设备还可以结合其他DRX相关的定时器的运行状态来确定是否可以停止监测下行信息或者下行数据。如果没有其他DRX相关的定时器指示终端设备需要监测下行信息或者下行数据，终端设备可以停止监测下行信息或下行数据，从而达到省电的目的。
在本申请实施例中，不启动DRX不活动定时器在不同场景下可以体现为不同的控制方式。若当前DRX不活动定时器没有处在运行状态，则不启动该定时器则意味着保持当前DRX不活动定时器的不运行状态。若当前DRX不活动定时器处于运行状态，则不启动该定时器可以包括不重启DRX不活动定时器或者停止DRX不活动定时器。本申请实施例中的重启定时器，是指从定时器被配置的时长开始重新计时。
在一个具体的实施方式中，不启动或者停止DRX不活动定时器，可以通过将DRX不活动定时器的时长设置为0来实现。即，无论原来DRX不活动定时器配置的时长是多少，在上述需要不启动或者停止DRX不活动定时器的时候，将DRX不活动定时器的时长设置为0，以便实现不启动或者停止DRX不活动定时器的目的，但在其他需要启动或者重启DRX不活动定时器的情况下，还是使用原来配置的DRX不活动定时器的时长。
在一个具体的实施方式中，本申请实施例提供的方法还包括：
若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，且所述终端设备配置了N个HARQ进程，其中，M为大于或等于1的整数，N为大于或等于2的整数，且M小于N，则启动或重启所述非连续接收不活动定时器。
在另一个具体的实施方式中，本申请实施例提供的方法还包括：
若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，除了所述终端设备配置了M个HARQ进程HARQ进程的情况之外，启动或重启所述非连续接收不活动定时器，其中M为大于或等于1的整数。可选的，所述控制信息指示的用于数据传输的M个HARQ进程，是指均用于上行数据传输的M个HARQ进程，或者均用于下行数据传输的M个HARQ进程，或者均用于侧行链路传输的M个HARQ进程。
结合上述两个具体的实施方式，可选的，所述控制信息指示的用于数据传输的M个HARQ进程，是指均用于上行数据传输的M个HARQ进程，或者均用于下行数据传输的M个HARQ进程，或者均用于侧行链路传输的M个HARQ进程。
当下行控制信息指示的用于数据传输的HARQ进程数小于终端配置的HARQ进程数，说明终端设备仍有可用的HARQ进程，同时，如果被指示的HARQ进程中有新传，则后续还有数据需要传输的可能性也很大，也就是还有可能有使用其他HARQ进程的下行信息或者下行数据发送给终端设备，此时启动或者重启DRX不活动定时器，可以让终端设备开始监测下行信息或者下行数据，以免丢失信息或者数据。
结合上述两个具体的实施方式，可选的，在终端设备启动或重启所述DRX不活动定时器的同时，或者启动或重启该定时器之后，终端设备监测物理下行控制信道。
结合上述两个具体的实施方式，可选的，在网络设备启动或重启所述DRX不活动定时器的同时，或者启动或重启该定时器之后，网络设备可以向终端设备发送下行信息或者下行数 据，当下行信息为下行控制信息时，该下行控制信息可以承载在物理下行控制信道上。
可选的，如果下行控制信息指示至少一个HARQ进程的传输，可以停止onDurat ionTimer。
图4给出了终端设备实施本申请实施例提供的方法时的流程图。
在401部分，终端设备监测物理下行控制信道。
在402部分，终端设备获取所述物理下行控制信道中的下行控制信息。
在403部分，若所述下行控制信息指示N个HARQ进程的数据传输且所述终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，则所述终端设备不启动DRX不活动定时器或者停止DRX不活动定时器。
具体的，当终端设备实现本申请实施例所提供的方法时，可以参考图3所对应的实施例中的描述，此处不再赘述。
图5给出了网络设备实施本申请实施例提供的方法时的流程图。
在501部分，网络设备在物理下行控制信道上发送下行控制信息给终端设备。
在502部分，若所述下行控制信息指示N个HARQ进程的数据传输且所述终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，不启动为所述终端设备维护的DRX不活动定时器或者停止为所述终端设备维护的DRX不活动定时器。
具体的，当网络设备实现本申请实施例所提供的方法时，可以参考图3所对应的实施例中的描述，此处不再赘述。
图6是本申请实施例提供的又一种定时器控制方法示意图。
图6所示的实施例中，以下行信息为下行控制信息(DCI)，终端设备配置了两个HARQ进程为例进行说明。该方法可以用于终端设备或者网络设备，用于终端设备时，图6中的几个定时器是终端设备内部维护的自身的DRX相关的定时器，用于网络设备时，图6中的几个定时器是网络设备为终端设备维护的该终端设备的DRX相关的定时器。图6中所涉及的几个定时器的时长，可以由网络设备和终端设备之间预先约定，或者网络设备通过配置信息配置给终端设备。
如图6所示，假设在本实施例所涉及的时间范围的起始，onDurationTimer处于运行状态。onDurationTimer为终端设备的持续时间定时器，在该定时器运行期间，网络设备可以向终端设备发送下行控制信息，终端设备监控物理下行控制信道。
DCI A为网络设备发送给终端设备的一个下行控制信息，该下行控制信息用于指示(或调度)两个HARQ进程的数据传输，分别为图6中所示的HARQ 0和HARQ 1，其中，以每个HARQ进程用于发送一个传输块为例，即图6中的TB 0和TB 1。可选的，TB 0和TB 1中至少有一个是新传。
如图6中所示的时间点a，网络设备在完成DCI A的发送，停止终端设备的onDurationTimer，相应的，终端设备在接收完DCI A后也停止自身维护的onDurationTimer。终端设备配置了两个HARQ进程，DCI A调度了这两个HARQ进程，因为没有其他可用的HARQ进程，网络设备不会再向终端设备发送下行控制信息，则在时间点a，网络设备和终端设备都不启动DRX不活动定时器，如果没有其他定时器的状态显示终端设备需要监测物理下行控制信道，则终端设备可以停止监测物理下行控制信道，从而达到省电的目的。
如果DCI A调度的HARQ 0和HARQ 1是两个用于上行数据传输的HARQ进程，则接下来，终端设备会在DCI A中指示的时频域资源上发送TB 0和TB 1，相应的，网络设备会在DCI A中指示的时频域资源上接收TB 0和TB 1。TB 0和TB 1可以承载在物理上行共享信道上，例如NPUSCH，具体可以为NPUSCH格式1(NPUSCH format 1)。此时图6示例中的HARQ往返时 间定时器为上行HARQ往返时间定时器(UL HARQ RTT Timer)。在此情况下，网络设备和终端设备都根据HARQ往返时间定时器来确定每个HARQ进程的此次数据传输是否结束。
如果DCI A调度的HARQ 0和HARQ 1是两个用于下行数据传输的HARQ进程，则接下来，网络设备会在DCI A中指示的时频域资源上发送TB 0和TB 1，相应的，终端设备会在DCI A中指示的时频域资源上接收TB 0和TB 1。TB 0和TB 1可以承载在物理下行共享信道上，例如NPDSCH。在此情况下，终端还可以根据是否正确接收了TB 0和TB 1，在DCI A中指示的时频域资源上发送TB 0的ACK或NACK反馈以及TB 1的ACK或NACK反馈给网络设备，即图6中所示的TB 0 ACK/NACK以及TB 1 ACK/NACK。相应的，网络设备在DCI A中指示的时频域资源上接收TB 0和TB1的ACK或NACK反馈。TB 0和TB1的ACK或NACK反馈可以承载在物理上行共享信道上，例如NPUSCH，具体可以为NPUSCH格式2(NPUSCH format 2)。图6中所示的TB 0 ACK/NACK以及TB 1 ACK/NACK仅适用于TB 0和TB 1为下行数据传输的传输块的情况。
图6中的示例，TB 0和TB 1在时域上是连续传输的，在实际应用时，TB 0和TB 1所使用的时域资源也可以不连续。
图6中的示例，HARQ 0上是TB 0，HARQ 1上是TB 1，在实际应用时，HARQ 0上也可以是TB 1，HARQ 1上是TB 0。本申请实施例中的HARQ进程的编号以及TB的编号仅为示例性说明，本申请对其不做限定，对HARQ进程编号与TB编号的对应关系也不做限定。
在如图6所示的时间点b，启动针对HARQ 0的HARQ往返时间定时器。当该方法应用于网络设备时，时间点b是网络设备完成TB 0的发送或接收的时间，当该方法应用于终端设备时，时间点b是终端设备完成TB 0的接收或发送的时间。在HARQ 0的HARQ往返时间定时器运行期间，因为此次HARQ进程还没有完成也没有更多的HARQ进程可用，网络设备不会再向终端设备发送下行控制信息，终端设备不会监测物理下行控制信道。
在如图6所示的时间点c，启动针对HARQ 1的HARQ往返时间定时器。当该方法应用于网络设备时，时间点c是网络设备完成TB 1的发送或接收的时间，当该方法应用于终端设备时，时间点c是终端设备完成TB 1的接收或发送的时间。在HARQ 1的HARQ往返时间定时器运行期间，因为此次HARQ进程还没有完成也没有更多的HARQ进程可用，网络设备不会再向终端设备发送下行控制信息，终端设备不会监测物理下行控制信道。
在如图6所示的时间点d，HARQ 0的HARQ往返时间定时器超时，启动DRX不活动定时器。此时终端设备可以监测物理下行控制信道，因为HARQ 0的HARQ往返时间定时器超时，意味着HARQ 0的数据传输已经结束。终端设备可以在DRX不活动定时器运行期间接收指示HARQ 0的新传或者重传的数据传输的下行控制信息。
在如图6所示的时间点e，HARQ 1的HARQ往返时间定时器超时，重启DRX不活动定时器。终端设备开始监测物理下行控制信道。
DCI B为网络设备发送给终端设备的又一个下行控制信息，该下行控制信息用于指示(或调度)两个HARQ进程的数据传输，分别为图6中所示的HARQ 0和HARQ 1，其中，以每个HARQ进程用于发送一个传输块为例，即图6中的TB 2和TB 3。TB 2和TB 3可以是两个上行数据传输的传输块，也可以是两个下行数据传输的传输块，具体的传输方式可以参考上述TB 0和TB 1的传输方式描述。
在如图6所示的时间点f，网络设备完成DCI B的发送或者终端设备接收完DCI B。终端设备配置了两个HARQ进程，DCI B调度了这两个HARQ进程，因为没有其他可用的HARQ进程，网络设备不会再向终端设备发送下行控制信息，则在时间点f，网络设备和终端设备都停止 正在运行的DRX不活动定时器，如果没有其他定时器的状态显示终端设备需要监测物理下行控制信道，则终端设备可以停止监测物理下行控制信道，从而达到省电的目的。
图7是本申请实施例提供的又一种定时器控制的方法示意图。下面以该方法作用于HARQ往返时间定时器为例，进行说明。终端设备会针对每一个HARQ进程维护一个HARQ往返时间定时器运行，网络设备也会相应的为终端设备的每一个HARQ进程维护一个HARQ往返时间定时器。在对应某一个HARQ进程的HARQ往返时间定时器运行期间，终端设备以及网络设备正在使用该HARQ进程进行数据传输。当HARQ往返时间定时器超时，表示该HARQ进程上的本次数据传输结束，DRX不活动定时器会启动或者重启，因此HARQ往返时间定时器的长度决定了何时启动或者重启DRX不活动定时器。类似的，该方法还可以用于控制其他与HARQ往返时间定时器功能类似的定时器。
以DCI A调度的HARQ 0和HARQ 1是两个用于下行数据传输的HARQ进程为例。
如图7所示，M为TB 1的传输时长，该时长可以用子帧的个数来标识。M可以是从传输TB 1的第一个子帧开始到传输TB 1的最后一个子帧结束(传输TB 1的最后一个子帧记为子帧n)，即，M等于用于传输TB 1的子帧个数。M也可以是从传输TB 0的最后一个子帧开始到子帧n结束，此时M等于用于传输TB 1的子帧个数加1。k为子帧n与用于传输TB 0的ACK或NACK反馈的第一个子帧之间的间隔，k也可以用子帧的个数来表示。k也可以是子帧n-1与用于传输TB 0的ACK或NACK反馈的第一个子帧之间的间隔。N为用于传输TB 0和TB 1的ACK或NACK反馈的总传输时长，也可以用子帧的个数来表示。N包括TB 0的反馈传输时长与TB 1的反馈传输时长之和，如果TB 0的反馈传输时长和TB 1的反馈传输时长相同，例如都为Q，则N＝2Q。X表示传输TB 1的ACK或NACK反馈的最后一个子帧(记为子帧p)之后的X个子帧，X的取值主要考虑的是网络设备处理承载ACK或NACK的物理上行共享信道，例如NPUSCH，所需的时间。X还可以是子帧p-1之后的X个子帧。deltaPDCCH为子帧p或者子帧p-1之后的第X个子帧与下一个物理下行控制信道时机的第1个子帧之间的间隔，因为子帧p或者子帧p-1之后的第X+1个子帧不一定是一个物理下行控制信道时机。一个物理下行控制信道时机(PDCCH occasion)是一个搜索空间(search space)的起始位置。
如图7所示，作为一个示例，HARQ 0的HARQ往返时间定时器的长度包括k，N，X以及deltaPDCCH，即HARQ 0的HARQ往返时间定时器的长度＝k+N+X+deltaPDCCH，此时，HARQ 0的HARQ往返时间定时器可以在TB 1传输完成时启动，例如，图7所示的时间点b。或者，HARQ 0的HARQ往返时间定时器的长度＝M+k+N+X+deltaPDCCH，此时，HARQ 0的HARQ往返时间定时器可以在TB 0传输完成时启动，例如，图7所示的时间点a。其中，上述X的取值可以为1，2，3或者4。
HARQ 1的HARQ往返时间定时器的长度包括k，N，X以及deltaPDCCH，即HARQ 1的HARQ往返时间定时器的长度＝k+N+X+deltaPDCCH，其中，X的取值可以为1，2，3或者4。
应当理解，HARQ 0的HARQ往返时间定时器的起始位置可以和HARQ 1的HARQ往返时间定时器的启动的时间点相同(如图7所示的时间点b)，也可以不相同。HARQ 0的HARQ往返时间定时器的超时的时间点可以和HARQ 1的HARQ往返时间定时器的超时的时间点相同(如图7所示的时间点c)，当HARQ 0的HARQ往返时间定时器和HARQ 1的HARQ往返时间定时器的时长设置为不同和/或，HARQ 0的HARQ往返时间定时器和HARQ 1的HARQ往返时间定时器的启动时刻不同的时候，其超时的时间点也可以不相同。HARQ 0的HARQ往返时间定时器的长度可以和HARQ 1的HARQ往返时间定时器的长度相同，也可以不相同。HARQ 0和HARQ 1的往返时间定时器的时长不同，可以通过将X的取值设置的不相同来实现。当然，X的取值 也可以是相同的。
图8是本申请实施例提供的再一种定时器控制的方法示意图。下面以该方法作用于HARQ往返时间定时器为例，进行说明。类似的，该方法还可以用于控制其他与HARQ往返时间定时器功能类似的定时器。
以DCI A调度的HARQ 0和HARQ 1是两个用于上行数据传输的HARQ进程为例。此时，TB 0和TB 1通过物理上行共享信道，例如NPUSCH格式1，发送。与下行数据传输类似，在上行数据传输过程中，终端设备和网络设备也都会分别为每一个HARQ进程维护一个HARQ往返时间定时器。在对应某一个HARQ进程的HARQ往返时间定时器运行期间，终端设备以及网络设备正在使用该HARQ进程进行上行数据传输。当HARQ往返时间定时器超时，该HARQ进程上的本次数据传输结束，DRX不活动定时器会启动或者重启，因此HARQ往返时间定时器的长度决定了何时启动或者重启DRX不活动定时器。
如无特别说明，如下的用于表示时长的变量都可以通过子帧的个数来表示。
如图8所示，M为TB 1的传输时长，即从传输TB 1的第一个子帧开始到传输TB 1的最后一个子帧结束(传输TB 1的最后一个子帧记为子帧n)，即，M等于用于传输TB 1的子帧个数。M也可以从传输TB 0的最后一个子帧开始到子帧n结束，即M等于用于传输TB 1的子帧个数加1。X为传输TB 1的最后一个子帧(记为子帧p)之后的X个子帧，X的取值主要考虑的是网络设备处理物理上行共享信道，例如NPUSCH，所需的时间。X也可以是子帧p-1之后的X个子帧。deltaPDCCH为子帧p或者子帧p-1之后的第X个子帧与下一个物理下行控制信道时机的第1个子帧之间的间隔，因为子帧p或者子帧p-1之后的第X+1个子帧不一定是一个物理下行控制信道时机。
如图8所示，作为一种示例，HARQ 0的HARQ往返时间定时器的长度包括X以及deltaPDCCH，即HARQ 0的HARQ往返时间定时器的长度＝X+deltaPDCCH，此时HARQ 0的HARQ往返时间定时器可以在完成TB 1的传输时启动例如，图8所示的时间点b。或者，HARQ 0的HARQ往返时间定时器的长度＝M+X+deltaPDCCH，此时HARQ 0的HARQ往返时间定时器可以在完成TB 0的传输时启动，例如，图8所示的时间点a。其中，上述X的取值可以为1，2，3或4。X的取值还可以和M有关，例如，当M大于等于阈值Z时，X的取值为X1，当M小于阈值Z时，X取值为X2，其中Z可以为2或3，X1可以为1，2，3或4，X2可以为1，2，3或4，且X1小于X2。
HARQ 1的HARQ往返时间定时器的长度包括X以及deltaPDCCH，即HARQ 1的HARQ往返时间定时器的长度＝X+deltaPDCCH。其中，X的取值可以为1，2，3或4。X的取值还可以和M有关，例如，当M大于等于阈值Z时，X的取值为X1，当M小于阈值Z时，X取值为X2，其中，Z可以为2或3，X1可以为1，2，3或4，X2可以为1，2，3或4，且X1小于X2。
应当理解，HARQ 0的HARQ往返时间定时器的起始位置可以和HARQ 1的HARQ往返时间定时器的启动的时间点相同(如图8所示的时间点b)，也可以不相同。HARQ 0的HARQ往返时间定时器的超时的时间点可以和HARQ 1的HARQ往返时间定时器的超时的时间点相同(如图8所示的时间点c)，当HARQ 0的HARQ往返时间定时器和HARQ 1的HARQ往返时间定时器的时长设置为不同和/或的HARQ 0的HARQ往返时间定时器和HARQ 1的HARQ往返时间定时器的启动时刻不同的时候，其超时的时间点也可以不相同。HARQ 0的HARQ往返时间定时器的长度可以和HARQ 1的HARQ往返时间定时器的长度相同，也可以不相同。HARQ 0和HARQ 1的往返时间定时器的时长不同，可以通过将X的取值设置的不相同来实现。当然，X的取值也可以是相同的。当DCI A调度的是上行时，HARQ往返时间定时器也可以称为上行HARQ往 返时间定时器(UL HARQ RTT Timer)。
图7或图8所提供的定时器控制方法，将HARQ往返时间定时间的超时时间点调整到了下一次物理下行控制信道时机的一开始，避免了当HARQ往返时间定时器的超时时间点落在非物理下行控制信道时机的时间段，或者落在终端设备正在进行上行数据传输的时间段内，在这些时间段内，网络设备不会向终端设备发送下行信息或者下行数据，终端设备无需在这些时间段内监测下行信息或者下行数据。因此，避免HARQ往返时间定时器的超时时间点落在这些时间段内，就避免了因为需要启动DRX不活动定时器而导致终端设备监测下行信息或者下行数据，从而达到了终端设备省电的目的。
可以理解的，本申请所提供的各个实施例可以独立应用于通信装置或通信系统中，也可以相互结合应用于通信装置或通信系统中。例如，图7或图8所对应的实施例，可以与图3至图6中任一图所对应的实施例结合使用。
上述本申请提供的实施例中，分别从各个通信装置本身、以及从各个通信装置之间交互的角度对本申请实施例提供的方法进行了介绍。可以理解的是，各个通信装置，例如终端设备、网络设备等，为了实现上述功能，可以包含执行各个功能相应的硬件结构和/或软件模块。结合本文中所公开的实施例描述的各示例的部分及步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图9示出了上述实施例中所涉及的一种可能的通信装置的结构示意图
该通信装置可以是一种终端设备，例如，可以是用户设备(UE)。该通信装置也可以是内置在终端设备中的装置或电路结构，例如，可以是电路系统、芯片或芯片系统。其中，本申请实施例所述的芯片系统包括至少一个芯片，还可以包括其他分立器件或者电路结构。
该通信装置还可以是一种网络设备，例如，可以是基站或者用于与终端设备进行无线通信的网络侧设备。该通信装置还可以是内置在网络设备中的装置或电路结构，例如，可以是电路系统、芯片或芯片系统。其中，本申请实施例所述的芯片系统包括至少一个芯片，还可以包括其他分立器件或者电路结构。
如图9所示，在一个具体的示例中，该通信装置包括至少一个处理器901，该处理器901用于与存储器耦合并执行存储器中所存储的指令，以实现本申请实施例中所提供的方法。例如，处理器901可以执行存储器中的代码从而实现对DRX相关定时器的控制操作，例如，监测物理下行控制信道，获取物理下行控制信道中的下行控制信息，若下行控制信息指示N个HARQ进程的数据传输且终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，不启动DRX不活动定时器或者停止DRX不活动定时器，等等。再如，控制下行控制信息在物理下行控制信道上的发送，若所述下行控制信息指示N个HARQ进程的数据传输且所述终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，不启动为所述终端设备维护的DRX不活动定时器或者停止为所述终端设备维护的DRX不活动定时器，等等。
在一个具体的示例中，该通信装置还可以包括存储器902，该存储器与上述至少一个处理器901耦合，用于存储程序指令。该存储器902还可以用于根据通信装置的需要存储信息和/或数据等，例如，存储与本申请实施例相关的定时器配置信息或定时器相关数据等。
在一个具体的示例中，该通信装置还可以包括收发器903，该收发器903用于支持该通信装置发送或者接收需要传输的信息或数据。例如，当该通信装置为网络设备时，该收发器903可以用于发送下行控制信息给终端设备，当该通信装置为终端设备时，该收发器903可 以用于接收网络设备发送的下行控制信息。
在一个具体的示例中，该通信装置为终端设备或者网络设备时，该通信装置还可以包括用于接收或者发送无线信号的至少一个天线904。
在一个具体的示例中，该通信装置为电路系统、芯片或者芯片系统时，所述至少一个处理器901可以是具有电路结构的处理装置或者集成在芯片中的处理装置。可选的，该通信装置为芯片或者芯片系统时，所述存储器902可以是集成在芯片内部的存储介质或存储器件，也可以是部署在芯片之外的独立的存储介质或存储器件。可选的，该通信装置为电路系统、芯片或者芯片系统时，所述收发装置903可以通过具体的电路结构、芯片管脚等形式实现。
可选的，上述通信装置的至少一个处理器904可以是中央处理单元(central processing unit，CPU)，通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框、模块、电路或功能。所述至少一个处理器904也可以是实现计算功能的组合，例如包含一个微处理器或多于一个微处理器的组合，数字信号处理器和微处理器的组合等。
图9仅仅示出了本申请实施例提供的通信装置的简化设计。在实际应用中，所述通信装置还可以包括任意数量的收发器、发射器、接收器、处理器、存储器等，也可以包括其他所需的软件或者硬件结构，本申请不限定通信装置中具体结构的具体实现形式。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由至少一个处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read-only memory，EPROM)、电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(compact disc read-only memory，CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。可选的，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于专用集成电路中。另外，该专用集成电路可以位于所述通信装置中。当然，处理器和存储介质也可以作为分立组件存在于所述通信装置中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。

Claims (29)

  1. 一种定时器控制方法，其特征在于，包括：
    监测物理下行控制信道；
    获取所述物理下行控制信道中的下行控制信息；
    若所述下行控制信息指示N个混合自动重传请求HARQ进程的数据传输，且终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，则停止非连续接收不活动定时器。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，且所述终端设备配置了N个HARQ进程，其中，M为大于或等于1的整数，N为大于或等于2的整数，且M小于N，则启动或重启所述非连续接收不活动定时器。
  3. 如权利要求1所述的方法，其特征在于，还包括：
    若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，除了所述终端设备配置了M个HARQ进程的情况之外，启动或重启所述非连续接收不活动定时器，其中M为大于或等于1的整数。
  4. 如权利要求3所述的方法，其特征在于，所述下行控制信息指示M个HARQ进程的数据传输，包括：
    所述下行控制信息指示M个HARQ进程的上行数据传输，或者所述下行控制信息指示M个HARQ进程的下行数据传输。
  5. 如权利要求1至4任一项所述的方法，其特征在于，所述N小于或等于所述终端设备支持的HARQ进程数。
  6. 如权利要求1至5任一项所述的方法，其特征在于，所述终端设备配置了N个HARQ进程，包括：所述终端设备配置了N个上行HARQ进程和/或配置了N个下行HARQ进程。
  7. 如权利要求1至6任一项所述的方法，其特征在于，所述下行控制信息指示N个混合自动重传请求HARQ进程的数据传输，包括：
    所述下行控制信息指示N个HARQ进程的上行数据传输，或者所述下行控制信息指示N个HARQ进程的下行数据传输。
  8. 如权利要求2至4任一项所述的方法，其特征在于，所述方法还包括：
    启动或重启所述非连续接收不活动定时器后，监测物理下行控制信道。
  9. 如权利要求1-8任一项所述的方法，其特征在于，所述N等于2，且所述2个HARQ进程与2个传输块TB对应，所述方法还包括：
    设置所述终端设备的HARQ往返时间定时器的长度为(k+2Q+1+deltaPDCCH)个子帧的时长，其中，k为子帧n与用于传输所述2个TB中的第一个TB的ACK或NACK反馈的第一个子帧之间的间隔，其中，子帧n为用于传输所述2个TB中的第二个TB的最后一个子帧，所述第一个TB和第二个TB的传输反馈时长相同，Q为所述传输反馈时长，deltaPDCCH为子帧p之后的第1个子帧与下一个物理下行控制信道时机的第1个子帧之间的间隔，其中，子帧p为用于传输所述第二个TB的ACK或NACK反馈的最后一个子帧，其中，所述第一个TB在所述第二个TB之前传输。
  10. 如权利要求1-8任一项所述的方法，其特征在于，所述N等于2，且所述2个HARQ进程与2个传输块TB对应，所述方法还包括：
    设置所述终端设备的上行HARQ往返时间定时器的长度等于(1+deltaPDCCH)个子帧的时长，其中，deltaPDCCH为子帧p之后的第1个子帧与下一个物理下行控制信道时机的第1个子帧之间的间隔，子帧p为所述2个TB中的第二个TB的最后一个子帧，其中，所述第二个TB为所述2个TB中最后传输的TB。
  11. 一种定时器控制方法，其特征在于，包括：
    在物理下行控制信道上发送下行控制信息给终端设备；
    若所述下行控制信息指示N个混合自动重传请求HARQ进程的数据传输，且所述终端设备配置了N个HARQ进程，其中N为大于或等于2的整数，则停止为所述终端设备维护的非连续接收不活动定时器。
  12. 如权利要求11所述的方法，其特征在于，还包括：
    若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，且所述终端设备配置了N个HARQ进程，其中，M为大于或等于1的整数，N为大于或等于2的整数，且M小于N，则启动或重启为所述终端设备维护的所述非连续接收不活动定时器。
  13. 如权利要求11所述的方法，其特征在于，还包括：
    若所述下行控制信息指示M个HARQ进程的数据传输，所述M个HARQ进程的数据传输中至少有一个HARQ进程的数据是新传，除了所述终端设备配置了M个HARQ进程的情况之外，启动或重启为所述终端设备维护的所述非连续接收不活动定时器，其中M为大于或等于1的整数。
  14. 如权利要求13所述的方法，其特征在于，所述下行控制信息指示M个HARQ进程的数据传输，包括：
    所述下行控制信息指示M个HARQ进程的上行数据传输，或者所述下行控制信息指示M个HARQ进程的下行数据传输。
  15. 如权利要求11至14任一项所述的方法，其特征在于，所述N小于或等于所述终端设备支持的HARQ进程数。
  16. 如权利要求11至15任一项所述的方法，其特征在于，所述终端设备配置了N个HARQ进程，包括：所述终端设备配置了N个上行HARQ进程和/或配置了N个下行HARQ进程。
  17. 如权利要求11至16任一项所述的方法，其特征在于，所述下行控制信息指示N个HARQ进程的数据传输，包括：
    所述下行控制信息指示N个HARQ进程的上行数据传输，或者所述下行控制信息指示N个HARQ进程的下行数据传输。
  18. 如权利要求12至14任一项所述的方法，其特征在于，所述方法还包括：
    在启动或重启为所述终端设备维护的所述非连续接收不活动定时器后，向所述终端设备发送承载在物理下行控制信道上的下行控制信息。
  19. 如权利要求11-18任一项所述的方法，其特征在于，所述N等于2，且所述2个HARQ进程与2个传输块TB对应，所述方法还包括：
    设置为所述终端设备维护的HARQ往返时间定时器的长度为(k+2Q+1+deltaPDCCH)个子帧的时长，其中，k为子帧n与用于传输所述2个TB中的第一个TB的ACK或NACK反馈的第一个子帧之间的间隔，其中，子帧n为用于传输所述2个TB中的第二个TB的最后一个子帧，所述第一个TB和第二个TB的传输反馈时长相同，Q为所述传输反馈时长，deltaPDCCH为子帧p之后的第1个子帧与下一个物理下行控制信道时机的第1个子帧之间的间隔，其中，子帧p为用于传输所述第二个TB的ACK或NACK反馈的最后一个子帧，其中，所述第一个TB在所述第二个TB之前传输。
  20. 如权利要求11-18任一项所述的方法，其特征在于，所述N等于2，且所述2个HARQ进程与2个传输块TB对应，所述方法还包括：
    设置为所述终端设备维护的上行HARQ往返时间定时器的长度等于(1+deltaPDCCH)个子帧的时长，其中，deltaPDCCH为子帧p之后的第1个子帧与下一个物理下行控制信道时机的第1个子帧之间的间隔，子帧p为所述2个TB中的第二个TB的最后一个子帧，其中，所述第二个TB为所述2个TB中最后传输的TB。
  21. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求1-10任一项所述的方法。
  22. 如权利要求21所述的通信装置，其特征在于，还包括所述存储器。
  23. 如权利要求21或22所述的通信装置，其特征在于，所述通信装置为终端设备。
  24. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现如权利要求11-20任一项所述的方法。
  25. 如权利要求24所述的通信装置，其特征在于，还包括所述存储器。
  26. 如权利要求24或25所述的通信装置，其特征在于，所述通信装置为网络设备。
  27. 一种计算机可读存储介质，包括指令，当所述指令被运行时，使得如权利要求1-10 任一项所述的方法被执行。
  28. 一种计算机可读存储介质，包括指令，当所述指令被运行时，使得如权利要求11-20任一项所述的方法被执行。
  29. 一种通信系统，其特征在于，包括如权利要求21-23任一项所述的通信装置和如权利要求24-26任一项所述的通信装置。
PCT/CN2020/109599 2019-08-15 2020-08-17 一种定时器控制方法、装置及系统 WO2021027963A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20852287.0A EP4017131A4 (en) 2019-08-15 2020-08-17 METHOD, APPARATUS, AND TIMER CONTROL SYSTEM
US17/672,379 US20220173842A1 (en) 2019-08-15 2022-02-15 Timer control method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910755801.1 2019-08-15
CN201910755801.1A CN112399435B (zh) 2019-08-15 2019-08-15 一种定时器控制方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/672,379 Continuation US20220173842A1 (en) 2019-08-15 2022-02-15 Timer control method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2021027963A1 true WO2021027963A1 (zh) 2021-02-18

Family

ID=74570313

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/109599 WO2021027963A1 (zh) 2019-08-15 2020-08-17 一种定时器控制方法、装置及系统

Country Status (4)

Country Link
US (1) US20220173842A1 (zh)
EP (1) EP4017131A4 (zh)
CN (1) CN112399435B (zh)
WO (1) WO2021027963A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022205479A1 (zh) * 2021-04-02 2022-10-06 Oppo广东移动通信有限公司 定时器状态更改方法、装置、终端及存储介质
WO2023279308A1 (zh) * 2021-07-07 2023-01-12 Oppo广东移动通信有限公司 确定drx激活期的方法及终端设备
CN113630218B (zh) * 2021-08-12 2022-10-25 惠州Tcl云创科技有限公司 一种数据传输处理方法、装置、移动终端及存储介质
CN116017376A (zh) * 2021-10-21 2023-04-25 华为技术有限公司 一种通信方法、通信装置及通信系统
CN116488777A (zh) * 2022-01-11 2023-07-25 大唐移动通信设备有限公司 一种非连续接收定时器控制方法、装置、终端及网络设备
CN117014109A (zh) * 2022-04-25 2023-11-07 华为技术有限公司 一种通信方法及装置
WO2023245594A1 (zh) * 2022-06-24 2023-12-28 Oppo广东移动通信有限公司 无线通信方法、终端设备以及网络设备
CN117412358A (zh) * 2022-07-08 2024-01-16 华为技术有限公司 一种通信方法以及通信装置
CN115835345A (zh) * 2022-10-18 2023-03-21 RealMe重庆移动通信有限公司 Harq进程的分配方法、装置、基站及存储介质
CN116389940A (zh) * 2023-03-31 2023-07-04 广西上善若水发展有限公司 基于eDRX通讯技术的水表远程抄表方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625432A (zh) * 2011-01-28 2012-08-01 华为技术有限公司 一种非连续接收的方法和装置
WO2014109769A1 (en) * 2013-01-14 2014-07-17 Nokia Corporation Improved handling of control signaling
CN105722195A (zh) * 2011-01-28 2016-06-29 华为技术有限公司 一种非连续接收的方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018101823A (ja) * 2015-04-28 2018-06-28 シャープ株式会社 端末装置、基地局装置、通信方法、および、集積回路
US11239955B2 (en) * 2017-01-27 2022-02-01 Telefonaktiebolaget Lm Ericsson (Publ) Supporting multiple hybrid automatic repeat request processes
US20190053206A1 (en) * 2017-08-10 2019-02-14 Alireza Babaei Control channel monitoring

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625432A (zh) * 2011-01-28 2012-08-01 华为技术有限公司 一种非连续接收的方法和装置
CN105722195A (zh) * 2011-01-28 2016-06-29 华为技术有限公司 一种非连续接收的方法和装置
WO2014109769A1 (en) * 2013-01-14 2014-07-17 Nokia Corporation Improved handling of control signaling

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4017131A4 *

Also Published As

Publication number Publication date
CN112399435B (zh) 2022-10-04
CN112399435A (zh) 2021-02-23
EP4017131A4 (en) 2022-10-12
US20220173842A1 (en) 2022-06-02
EP4017131A1 (en) 2022-06-22

Similar Documents

Publication Publication Date Title
WO2021027963A1 (zh) 一种定时器控制方法、装置及系统
JP6575783B2 (ja) ユーザ端末の方法及びユーザ端末
WO2019192342A1 (zh) 非连续接收的通信方法、装置、通信设备和通信系统
US8265080B2 (en) System and method for retransmissions in a discontinuous reception configured system
US10594447B2 (en) Data transmission method, terminal, and ran device
WO2018082716A1 (zh) 传输信息的方法、网络设备和终端设备
WO2021120013A1 (zh) 监听唤醒信号的方法、终端设备和网络设备
US20220039013A1 (en) Method and device for discontinuous reception
WO2021056136A1 (zh) 监听wus的方法、发送信息的方法及设备
US20230309018A1 (en) Power Efficient Downlink Control Information Framework for Cellular Communication
WO2021155603A1 (zh) 基于drx的侧行反馈方法及相关装置
WO2023165449A1 (zh) 一种通信方法及装置
WO2022205445A1 (zh) 一种数据重传方法及相关设备
WO2022150975A1 (zh) 一种通信方法及装置
WO2023134394A1 (zh) 一种非连续接收定时器控制方法、装置、终端及网络设备
US20240007229A1 (en) Sidelink communication method and apparatus
WO2021003628A1 (zh) 定时器的处理方法和装置
CN116569645A (zh) 配置与非连续接收相对应的资源
CN115134943A (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: 20852287

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020852287

Country of ref document: EP

Effective date: 20220315