WO2020029568A1 - 一种终端设备的休眠方法及装置 - Google Patents

一种终端设备的休眠方法及装置 Download PDF

Info

Publication number
WO2020029568A1
WO2020029568A1 PCT/CN2019/075084 CN2019075084W WO2020029568A1 WO 2020029568 A1 WO2020029568 A1 WO 2020029568A1 CN 2019075084 W CN2019075084 W CN 2019075084W WO 2020029568 A1 WO2020029568 A1 WO 2020029568A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
timer
sleep
running
signal indicating
Prior art date
Application number
PCT/CN2019/075084
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 US17/266,721 priority Critical patent/US11871349B2/en
Priority to EP19846376.2A priority patent/EP3826369A4/en
Publication of WO2020029568A1 publication Critical patent/WO2020029568A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0212Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216Power 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28Timers or timing mechanisms used in protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248Power 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0261Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/28Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and device for sleeping a terminal device.
  • the fifth generation (5G, 5G) new air interface (NR) technology follows the discontinuous reception (DRX) mechanism in long term evolution (LTE).
  • a base station is a DRX cycle configured by a terminal device (also called User Equipment (UE)) in a radio resource control (RRC) connection state.
  • the DRX cycle can be a long DRX cycle or a short DRX cycle.
  • Long DRX cycle is required by default and short DRX cycle is optional.
  • the UE will start a short cycle timer (ShortCycleTimer) when using a short DRX cycle. When the ShortCycleTimer times out, it is converted to a long DRX cycle.
  • ShortCycleTimer short cycle timer
  • the DRX cycle consists of an "On Duration” section and an "DRX Opportunity for DRX” section, where the UE monitors and receives the physical downlink control channel (PDCCH) during the "On Duration” time.
  • the UE may not monitor or receive the PDCCH to reduce power consumption.
  • the DRX mechanism includes a continuous timer (onDurationTimer or drx-onDurationTimer). At the beginning of each DRX cycle (that is, the start of onDuration of each DRX cycle), the UE needs to turn onDurationTimer. When the onDurationTimer times out, it means that the "onDuDuration" time ends. At this point, the UE enters "Opportunity for DRX" time.
  • the DRX mechanism also includes an activity timer (InactivityTimer or drx-InactivityTimer). Specifically, when the UE receives a PDCCH indicating a new transmission within the “onDuration” time, it is likely that the UE will It will continue to be scheduled by the base station for a period of time. The UE needs to start the InactivityTimer, and the UE needs to monitor and receive the PDCCH during the running time of the InactivityTimer. And, the DRX mechanism further includes a retransmission timer (RetransmissionTimer or drx-RetransmissionTimer).
  • RetransmissionTimer or drx-RetransmissionTimer
  • the RetransmissionTimer specifically includes an uplink RetransmissionTimer (RetransmissionTimerUL or drx-RetransmissionTimerUL) and a downlink RetransmissionTimer (RetransmissionTimerDL or drx-RetransmissionTimerDL).
  • the UE needs to monitor and receive the PDCCH during the operation of onDurationTimer, InactivityTimer, RetransmissionTimer (RetransmissionTimerUL, RetransmissionTimerDL).
  • the above time can be called the "Active Time” of DRX, and the UE needs to wake up (or wake up) to prepare Receive signaling and data.
  • the UE may not need to monitor and receive the PDCCH during the operation of the timer or in other special situations that need to be at the "activation time", which is called the "sleep time" of the DRX, and the UE may sleep.
  • C-RNTI cell radio network temporary identifier
  • the UE may not need to receive the PDCCH and can sleep, that is, the UE may wake up in vain during this time and consume the power consumption of monitoring the PDCCH in vain. So how to save power is an urgent problem.
  • an indication signal is introduced, and the indication signal can be used to implement that the UE enters sleep.
  • the current method can only instruct the UE to sleep according to the onDuration time or DRX cycle time specified in the existing DRX mechanism.
  • the InactivityTimer or RetransmissionTimer has been started, the UE will still maintain a period of activation time, which will still cause The power consumption of the UE increases. Therefore, the existing methods cannot save power consumption well.
  • the application provides a sleep method and device of a terminal device, which are used to achieve a requirement for saving power consumption.
  • the present application provides a method for sleeping a terminal device, the method including:
  • the terminal device does not receive a signal indicating wake-up within a preset time, if the activity timer InactivityTimer is running, the terminal device stops the InactivityTimer; or if the retransmission timer RetransmissionTimer is running, the terminal The device stops the RetransmissionTimer; or, if the InactivityTimer and the RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer; wherein the terminal device is configured to discontinuously receive DRX.
  • the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device does not receive a signal indicating wake-up within a preset time, which may specifically include: the terminal device receives within a preset time A sleep signal is received; or, the terminal device does not receive a wake-up signal within a preset time; or the terminal device receives an indication signal within the preset time, and the indication signal includes sleep indication information.
  • the terminal device can accurately determine that the terminal device has not received a signal indicating wake-up.
  • the terminal device stopping the InactivityTimer may specifically be that the terminal device is Stop the InactivityTimer when no signal indicating wake-up is received within a set time; or, the terminal device stops the InactivityTimer after receiving no signal indicating wake-up within a preset time; or, the terminal device is (currently) The InactivityTimer is stopped at the beginning of the next DRX cycle of the DRX cycle.
  • the terminal device stops the RetransmissionTimer, specifically It may be that the terminal device stops the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the terminal device may further perform: When the InactivityTimer is running, the terminal device resets the InactivityTimer; or, if the RetransmissionTimer is running, the terminal device resets the RetransmissionTimer; or, if the InactivityTimer and the RetransmissionTimer are running, the terminal The device resets the InactivityTimer and the RetransmissionTimer.
  • the InactivityTimer and / or the RetransmissionTimer need to be turned on next time, the InactivityTimer and / or the RetransmissionTimer can be timed from an initial value to avoid affecting the normal process.
  • the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL And one or more of a downlink retransmission timer RetransmissionTimerDL.
  • the terminal device stops the InactivityTimer, and The terminal device starts or restarts the short cycle timer ShortCycleTimer. In this way, when the terminal device stops the InactivityTimer in time, the original DRX mechanism is also maintained, and the terminal device can continue to use the short DRX cycle.
  • the terminal device stops the InactivityTimer, and The terminal device uses a long DRX cycle. This can make the terminal device more power-efficient.
  • the terminal device stops the ShortCycleTimer, or the terminal The device stops and resets the ShortCycleTimer. In this way, the terminal device can successfully switch from a short DRX cycle to a long DRX cycle.
  • the form of the signal may be a physical
  • the layer sequence can be either downlink control information (DCI), or medium access control (MAC) control elements (CE) (MAC), or media access Control (medium access control, MAC) protocol data unit (protocol data unit, PDU) (MAC PDU).
  • DCI downlink control information
  • MAC medium access control
  • CE control elements
  • MAC media access Control
  • PDU protocol data unit
  • the terminal device does not start or restart the InactivityTimer.
  • the A terminal device stops the persistent timer, or the terminal device stops and resets the persistent timer.
  • the present application provides a method for sleeping a terminal device.
  • the method includes:
  • the terminal device After receiving a signal indicating sleep from a communication device, the terminal device starts or restarts a sleep timer, and sleeps during the running of the sleep timer; wherein the terminal device sleeps during the running of the sleep timer includes: The terminal device does not monitor the physical downlink control channel PDCCH during the running of the sleep timer.
  • the terminal device can be truly hibernated, so that power consumption can be better saved and the demand for power saving can be met.
  • the sleeping of the terminal device during the running of the sleep timer may further include that the terminal device does not send during the running of the sleep timer.
  • Type-0-triggered SRS triggered by type 0 or the terminal device does not report channel state information CSI during the sleep timer operation; or the terminal device does not report channel state information CSI during the sleep timer operation Sending the type-0-triggered SRS and not reporting the CSI.
  • the type 0 triggering detection reference signal is periodic detection reference signal periodic SRS and semi-static detection reference signal semi-persistent SRS, and the terminal device does not send the type 0 triggering detection reference signal during the sleep timer operation.
  • type-0-triggered SRS that is, the terminal device does not send a periodic sounding reference signal periodic SRS and / or a semi-static sounding reference signal semi-persistent SRS during the sleep timer operation.
  • the terminal device can sleep more thoroughly, thereby saving power consumption even more.
  • the receiving, by the terminal device, a signal indicating sleep from the communication device may include: The terminal device receives a sleep signal from the communication device; or the terminal device receives an instruction signal from the communication device, and the instruction signal includes sleep instruction information.
  • the terminal device can accurately determine that a signal indicating sleep is received.
  • the terminal device receives the communication device from the communication device. Before the signal indicating sleep, the terminal device further receives a sleep duration configured by the communication device.
  • the terminal device can know the sleep duration, so that a subsequent configuration time for the sleep timer is the sleep duration.
  • the signal includes indication information, and The instruction indicates the sleep duration.
  • the terminal device can learn the sleep duration by using the instruction information, so that a subsequent configuration of a timing duration for a sleep timer is the sleep duration.
  • the terminal device before the terminal device receives a signal indicating sleep from the communication device, the terminal device receives The at least one duration configured by the communication device, and the sleep duration is one of the at least one duration.
  • the terminal device can obtain the sleep duration in the at least one duration by using the indication information.
  • the terminal device starts or restarts a sleep timer Previously, the timing duration of the sleep timer was configured as the sleep duration. In this way, the terminal device can sleep for the sleep duration.
  • the form of the signal may be a physical
  • the layer sequence can be either DCI or MAC CE or MAC PDU.
  • the communication device may be a network device, for example
  • the base station may also be another device, such as a terminal device.
  • the terminal device does not start or restart the activity timer InactivityTimer .
  • the present application provides a method for sleeping a terminal device, which method includes:
  • the terminal device stops the InactivityTimer if the activity timer InactivityTimer is running; or, if the retransmission timer RetransmissionTimer is running, the terminal device stops the RetransmissionTimer; Alternatively, if the InactivityTimer and the RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer; wherein the terminal device is configured to receive DRX discontinuously.
  • the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device receiving the signal indicating sleep may specifically include: the terminal device receiving the sleep signal; or the terminal device receiving An instruction signal, where the instruction signal includes sleep instruction information.
  • the terminal device can accurately determine that the terminal device receives a signal indicating sleep.
  • the terminal device stopping the InactivityTimer may specifically be that the terminal device is receiving Stopping the InactivityTimer when a signal indicating sleep is reached; or the terminal device stops the InactivityTimer after receiving a signal indicating sleep; or the terminal device stops at the beginning of the next DRX cycle of the (current) DRX cycle The InactivityTimer.
  • the terminal device stops the RetransmissionTimer, specifically It may be that the terminal device stops the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the terminal device may further perform: If the InactivityTimer is running, the terminal device resets the InactivityTimer; or if the RetransmissionTimer is running, the terminal device resets the RetransmissionTimer; or if the InactivityTimer and the RetransmissionTimer are running, the terminal device restarts Set the InactivityTimer and the RetransmissionTimer.
  • the InactivityTimer and / or the RetransmissionTimer need to be turned on next time, the InactivityTimer and / or the RetransmissionTimer can be timed from an initial value to avoid affecting the normal process.
  • the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL And one or more of a downlink retransmission timer RetransmissionTimerDL.
  • the terminal device stops the InactivityTimer, and The terminal device starts or restarts the short cycle timer ShortCycleTimer. In this way, when the terminal device stops the InactivityTimer in time, the original DRX mechanism is also maintained, and the terminal device can continue to use the short DRX cycle.
  • the terminal device stops the InactivityTimer, and The terminal device uses a long DRX cycle. This can make the terminal device more power-efficient.
  • the terminal device stops the ShortCycleTimer, or the terminal The device stops and resets the ShortCycleTimer. In this way, the terminal device can successfully switch from a short DRX cycle to a long DRX cycle.
  • the form of the signal may be a physical
  • the layer sequence can be either DCI or MAC CE or MAC PDU.
  • the terminal device does not start or restart the InactivityTimer.
  • the A terminal device stops the persistent timer, or the terminal device stops and resets the persistent timer.
  • the present application provides a method for sleeping a terminal device, the method including:
  • the terminal device receives an instruction message, the instruction message is used to instruct the terminal device to stop a specific timer; if a continuous timer onDurationTimer is running, the terminal device stops the onDurationTimer; or if an activity timer InactivityTimer is running, the A terminal device stops the InactivityTimer; or if the onDurationTimer and the InactivityTimer are running, the terminal device stops the onDurationTimer and the InactivityTimer; wherein the terminal device is configured with DRX.
  • the terminal device can be hibernated in time, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device stops the RetransmissionTimer, where the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL and One or more of a downlink retransmission timer RetransmissionTimerDL.
  • the indication message is a physical layer sequence, or DCI, or MAC, CE, or MAC PDU. .
  • the terminal device receives the instruction message, which may specifically When the terminal device uses a long DRX cycle, it receives the indication message.
  • the terminal device continues to use the long DRX cycle.
  • the terminal device receives the instruction message, which may specifically When the terminal device uses the short DRX cycle, it receives the indication message.
  • the terminal device continues to use the short DRX cycle.
  • the terminal device does not start or restart the short cycle timer ShortCycleTimer.
  • the terminal The device may also reset the onDurationTimer; if the InactivityTimer is running, the terminal device may also reset the InactivityTimer.
  • the InactivityTimer and / or the onDurationTimer need to be turned on next time, the InactivityTimer and / or the onDurationTimer can be timed from an initial value to avoid affecting the normal process.
  • the terminal device may also reset the RetransmissionTimer.
  • the RetransmissionTimer when the RetransmissionTimer needs to be turned on next time, the RetransmissionTimer can be timed from the initial value to avoid affecting the normal process.
  • the present application further provides a terminal device, where the terminal device includes:
  • the terminal device is configured to receive DRX discontinuously.
  • the receiving unit does not receive a signal indicating wake-up within a preset time, and is specifically configured to: receive a sleep signal within the preset time; Either a wake-up signal is not received within a preset time; or an indication signal is received within a preset time, the indication signal including sleep instruction information.
  • the processing unit stops the InactivityTimer, and is specifically configured to be in the (current) DRX cycle. Stop the InactivityTimer at the beginning of the next DRX cycle.
  • the processing unit stops the RetransmissionTimer, specifically Used to stop the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processing unit is further configured to: If the InactivityTimer is running, reset the InactivityTimer; or if the RetransmissionTimer is running, reset the RetransmissionTimer; or if the InactivityTimer and RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL And one or more of a downlink retransmission timer RetransmissionTimerDL.
  • the processing unit is further configured to stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processing unit is further configured to stop the InactivityTimer, and uses long DRX cycles.
  • the processing unit is further configured to stop the ShortCycleTimer if the short-cycle timer ShortCycleTimer is running, or, Stop and reset the ShortCycleTimer.
  • the form of the signal may be a physical
  • the layer sequence can be either DCI or MAC CE or MAC PDU.
  • the terminal device does not start or restart the InactivityTimer.
  • the The processing unit is further configured to stop the duration timer, or stop and reset the duration timer.
  • the present application further provides a terminal device, where the terminal device includes:
  • a receiving unit for receiving a signal indicating sleep from a communication device; a processing unit for starting or restarting a sleep timer and sleeping during the running of the sleep timer; wherein sleeping during the running of the sleep timer includes : Do not monitor the physical downlink control channel PDCCH during the sleep timer operation.
  • the sleeping of the processing unit during the running of the sleep timer further includes:
  • the receiving unit receives a signal indicating sleep from the communication device, and is specifically configured to: Receiving a sleep signal from the communication device; or receiving an instruction signal from the communication device, where the instruction signal includes sleep instruction information.
  • the receiving unit receives Before the device's signal indicating sleep, it is further configured to receive a sleep time configured by the communication device.
  • the signal includes indication information, and The instruction indicates the sleep duration.
  • the receiving unit is further configured to receive all signals before receiving a signal indicating sleep from the communication device.
  • the at least one duration configured by the communication device, and the sleep duration is one of the at least one duration.
  • the processing unit starts or restarts the sleep timing.
  • the controller is further configured to configure a timing duration of the sleep timer to be the sleep duration.
  • the form of the signal may be a physical
  • the layer sequence can be either DCI or MAC CE or MAC PDU.
  • the terminal device does not start or restart the activity timer InactivityTimer .
  • the present application further provides a terminal device, where the terminal device includes:
  • the terminal device is configured to receive DRX discontinuously.
  • the receiving unit receives a signal indicating sleep, and is specifically configured to: receive a sleep signal; or receive an instruction signal in the instruction signal. Contains hibernation instructions.
  • the processing unit stops the InactivityTimer, which is specifically used for the (current) DRX cycle. Stop the InactivityTimer at the beginning of the next DRX cycle.
  • the processing unit stops the RetransmissionTimer, specifically Used to stop the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processing unit is further configured to: If the InactivityTimer is running, reset the InactivityTimer; or if the RetransmissionTimer is running, reset the RetransmissionTimer; or if the InactivityTimer and RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL And one or more of a downlink retransmission timer RetransmissionTimerDL.
  • the processing unit is further configured to stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processing unit is further configured to stop the InactivityTimer, and uses long DRX cycles.
  • the processing unit is further configured to stop the ShortCycleTimer if the ShortCycleTimer is running, or stop and reset The ShortCycleTimer.
  • the form of the signal may be a physical
  • the layer sequence can be either DCI or MAC CE or MAC PDU.
  • the terminal device does not start or restart the InactivityTimer.
  • the The processing unit is further configured to stop the duration timer, or stop and reset the duration timer.
  • the present application further provides a terminal device, where the terminal device includes:
  • the processing unit is further configured to stop the RetransmissionTimer if a retransmission timer RetransmissionTimer is running, where the RetransmissionTimer is an uplink retransmission One or more of a timer RetransmissionTimerUL and a downlink retransmission timer RetransmissionTimerDL.
  • the indication message is a physical layer sequence, or DCI, or MAC, CE, or MAC PDU. .
  • the receiving unit receives an instruction message, and specifically uses When the processing unit uses a long DRX cycle, it receives the indication message.
  • a fourth possible implementation manner of the eighth aspect it is further configured to continue to use the long DRX cycle.
  • the terminal device receives the instruction message, which may specifically When the terminal device uses the short DRX cycle, it receives the indication message.
  • the terminal device continues to use the short DRX cycle.
  • the terminal device does not start or restart the short cycle timer ShortCycleTimer.
  • the present application further provides a terminal device, where the terminal device includes a transceiver, at least one memory, and at least one processor, where:
  • the transceiver is configured to transmit and receive signals when receiving a call from the processor; the processor is configured to be coupled to the memory, call a program in the memory, and perform the following steps: if the transceiver is at a preset time When no signal indicating wake-up is received, stop the InactivityTimer if the activity timer InactivityTimer is running; or stop the RetransmissionTimer if the retransmission timer RetransmissionTimer is running; or, if the InactivityTimer and the RetransmissionTimer are running Run, stop the InactivityTimer and the RetransmissionTimer.
  • the terminal device is configured to receive DRX discontinuously.
  • the transceiver does not receive a signal indicating wake-up within a preset time, and is specifically configured to: receive a sleep signal within a preset time; Either a wake-up signal is not received within a preset time; or an indication signal is received within a preset time, the indication signal including sleep instruction information.
  • the processor stops the InactivityTimer, which is specifically used for the (current) DRX cycle. Stop the InactivityTimer at the beginning of the next DRX cycle.
  • the processor stops the RetransmissionTimer, specifically Used to stop the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processor is further configured to: If the InactivityTimer is running, reset the InactivityTimer; or if the RetransmissionTimer is running, reset the RetransmissionTimer; or if the InactivityTimer and the RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL And one or more of a downlink retransmission timer RetransmissionTimerDL.
  • the processor is further configured to stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processor is further configured to stop the InactivityTimer, and uses long DRX cycles.
  • the processor is further configured to stop the ShortCycleTimer if the short-cycle timer ShortCycleTimer is running, or, Stop and reset the ShortCycleTimer.
  • the form of the signal may be a physical
  • the layer sequence can be either DCI or MAC CE or MAC PDU.
  • the processing is performed
  • the controller is further configured to stop the duration timer, or stop and reset the duration timer.
  • the present application further provides a terminal device, where the terminal device includes a transceiver, at least one memory, and at least one processor, where:
  • the transceiver is configured to receive a signal indicating sleep from a communication device when receiving a call from the processor; the processor is configured to be coupled to the memory, call a program in the memory, and perform the following steps: Starting or restarting a sleep timer and sleeping during the running of the sleep timer; wherein sleeping during the running of the sleep timer includes: not monitoring the PDCCH during the running of the sleep timer.
  • the processor sleeping during the sleep timer operation further includes: not sending a probe triggered by a type 0 during the sleep timer operation The reference signal type-0-triggered SRS; or the channel state information CSI is not reported during the sleep timer operation; or the type-0-triggered SRS is not transmitted during the sleep timer operation and the CSI is not reported .
  • the transceiver receives a signal indicating sleep from the communication device, and is specifically configured to: Receiving a sleep signal from the communication device; or receiving an instruction signal from the communication device, where the instruction signal includes sleep instruction information.
  • the transceiver receives Before the device's signal indicating sleep, it is further configured to receive a sleep time configured by the communication device.
  • the signal includes indication information, and The instruction indicates the sleep duration.
  • the transceiver is further configured to receive all signals before receiving a signal indicating sleep from the communication device.
  • the at least one duration configured by the communication device, and the sleep duration is one of the at least one duration.
  • the processor starts or restarts the sleep timing.
  • the controller is further configured to configure a timing duration of the sleep timer to be the sleep duration.
  • the form of the signal may be a physical
  • the layer sequence can be either DCI or MAC CE or MAC PDU.
  • the present application further provides a terminal device, where the terminal device includes a transceiver, at least one memory, and at least one processor, where:
  • the transceiver is configured to receive a signal when receiving a call from the processor; the processor is configured to be coupled to the memory, call a program in the memory, and execute the following steps: if the transceiver Upon receiving a signal indicating sleep, the terminal device stops the InactivityTimer if the activity timer InactivityTimer is running; or, if the retransmission timer RetransmissionTimer is running, the terminal device stops the RetransmissionTimer; or, if the InactivityTimer And the RetransmissionTimer is running, the terminal device stops the InactivityTimer and the RetransmissionTimer. Wherein, the terminal device is configured to receive DRX discontinuously.
  • the transceiver receives a signal indicating sleep, and is specifically configured to: receive a sleep signal; or receive an indication signal, the indication The signal contains sleep indication information.
  • the processor stops the InactivityTimer, and is specifically configured to (currently) The InactivityTimer is stopped at the beginning of the next DRX cycle of the DRX cycle.
  • the processor stops the RetransmissionTimer, specifically for stopping the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processor is further configured to: If the InactivityTimer is running, reset the InactivityTimer; or if the RetransmissionTimer is running, reset the RetransmissionTimer; or if the InactivityTimer and the RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is uplink retransmission One or more of a timer RetransmissionTimerUL and a downlink retransmission timer RetransmissionTimerDL.
  • the processor is further configured to: Stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processor is further configured to: Stop the InactivityTimer and use a long DRX cycle.
  • the processor is further configured to stop the ShortCycleTimer if the ShortCycleTimer is running, or stop and Reset the ShortCycleTimer.
  • the form of the signal may be A physical layer sequence can be either DCI or MAC CE or MAC PDU.
  • the processor is further configured to stop the duration timer, or stop and reset the duration timer.
  • the present application further provides a terminal device, where the terminal device includes a transceiver, at least one memory, and at least one processor, where:
  • the transceiver is configured to receive an instruction message when receiving a call from the processor, where the instruction message is used to instruct the terminal device to stop a specific timer, wherein the terminal device is configured to discontinuously receive DRX;
  • the processor is configured to be coupled to the memory, call a program in the memory, and execute the following steps: if the continuous timer onDurationTimer is running, stop the onDurationTimer; or, if the activity timer InactivityTimer is running, stop all Said InactivityTimer; or, if the onDurationTimer and the InactivityTimer are running, stop the onDurationTimer and the InactivityTimer.
  • the processor is further configured to: if a retransmission timer RetransmissionTimer is running, stop the RetransmissionTimer, where the RetransmissionTimer is uplink One or more of a retransmission timer RetransmissionTimerUL and a downlink retransmission timer RetransmissionTimerDL.
  • the indication message is a physical layer sequence, or DCI, or MAC, CE, Or MAC PDU.
  • the transceiver receives an indication message Is specifically used for the processor to receive the indication message when using a long DRX cycle.
  • a fourth possible implementation manner of the twelfth aspect it is further configured to continue to use the long DRX cycle.
  • the terminal device receives an instruction message Specifically, when the terminal device uses the short DRX cycle, it can receive the indication message.
  • the terminal device continues to use the short DRX cycle.
  • the terminal device does not start or restart the short cycle timer ShortCycleTimer.
  • the present application also provides a computer storage medium, where the computer storage medium stores computer-executable instructions, and the computer-executable instructions are used to cause the computer to execute the foregoing when called by the computer Either way.
  • the present application also provides a computer program product containing instructions that, when run on a computer, causes the computer to execute any one of the methods described above.
  • the present application further provides a chip, which is connected to a memory and is configured to read and execute program instructions stored in the memory to implement any one of the foregoing methods.
  • the present application also provides a method for indicating a status of a terminal device, the method including:
  • the terminal device receives a first message from the communication device, where the first message indicates time information for the terminal device to wake up or sleep; if the first message indicates time information for the terminal device to wake up, the terminal device is based on The time information wakes up; or, if the first message indicates time information of the terminal device sleeping, the terminal device sleeps based on the time information.
  • the terminal device can flexibly wake up or sleep according to the first message. And compared with the prior art, since the indication of the time information for the terminal device to sleep is introduced, the terminal device can be flexibly hibernated relative to the existing technology, so that power consumption can be better saved and the demand for power saving can be met.
  • the first message may include first indication information, and the first indication information indicates the time information.
  • the first message may indicate the time information of the terminal device waking up or sleeping through the first indication information.
  • the first message may include second indication information, and the second The instruction information indicates that the terminal device wakes up or sleeps.
  • the first message may use the second instruction information to implement an instruction for the terminal device to wake up or sleep.
  • the time information may be all The length of time the terminal device wakes up or sleeps; or, the time information may be the length of time before the terminal device wakes up or sleeps; or the time information may be the time when the terminal device wakes up or sleeps.
  • the wake-up or hibernation event of the terminal device can be flexibly indicated in multiple ways.
  • the time length may be: one or more milliseconds; or, one or more subframes; Or, one or more time slots; or, one or more discontinuous reception DRX cycles; or, one or more OnDuration; or, one or more paging occasions (PO); or, one or more Physical downlink control channel PDCCH monitoring opportunities; or, the length of time in milliseconds; or the length of time in subframes; or the length of time in slots; or, the discontinuous reception DRX cycle is The length of time in units; or the length of time in units of On Durations; or the length of time in units of paging opportunities; or the length of time in units of physical downlink control channel PDCCH monitoring opportunities.
  • the time length can be expressed in multiple ways, and the time length can be more flexible.
  • the first message may be MAC PDU or RRC signaling.
  • the first indication information may be carried in a media access control subheader of the MAC PDU
  • the first indication information may be carried in a MAC CE of the MAC PDU.
  • the first indication information can be successfully carried in the first message, so as to implement time information indicating that the terminal device wakes up or sleeps.
  • the first message may be a MAC PDU.
  • the second indication information may be carried in a media access control subheader of the MAC PDU
  • the second indication information may be carried in a MAC CE of the MAC PDU.
  • the second indication information may be successfully carried in the first message, so as to implement an instruction to wake up or sleep the terminal device.
  • the first message may be MAC PDU or RRC signaling.
  • the first message may be DCI.
  • the terminal device does not start or restart the activity timer. This saves operations.
  • the first The message indicates time information for the terminal device to sleep. If an activity timer is running, the terminal device stops the activity timer, or the terminal device stops and resets the activity timer. This can make the terminal device more power-efficient.
  • any one of the first to eleventh possible implementation manners of the sixteenth aspect in the thirteenth possible implementation manner of the sixteenth aspect, if the first The message indicates the time information for the terminal device to sleep. If the continuous timer is running, the terminal device stops the continuous timer, or the terminal device stops and resets the continuous timer. This can make the terminal device more power-efficient.
  • the present application further provides a terminal device, where the terminal device includes:
  • a receiving unit configured to receive a first message from a communication device, the first message indicating time information of the terminal device to wake up or sleep; a processing unit, configured to, if the first message indicates the time when the terminal device wakes up Information, wake up based on the time information; or, if the first message indicates time information of the terminal device sleeping, sleep based on the time information.
  • the first message includes first indication information, and the first indication information indicates the time information.
  • the first message includes second instruction information, and the second instruction The information indicates that the terminal device wakes up or sleeps.
  • the time information is the The length of time that the terminal device wakes up or sleeps; or the time information is the length of time before the terminal device wakes up or sleeps; or the time information is the time that the terminal device wakes up or sleeps ends.
  • the time length is: one or more milliseconds; or, one or more subframes; or , One or more time slots; or, one or more discontinuous reception DRX cycles; or, one or more OnDuration; or, one or more paging opportunities; or, one or more physical downlink control channel PDCCH monitoring Opportunity; or, the length of time in milliseconds; or the length of time in subframes; or the length of time in slots; or the length of time in discrete reception DRX cycles; or, The length of time in units of OnDurations; or the length of time in units of paging opportunities; or the length of time in units of physical downlink control channel PDCCH monitoring opportunities.
  • the first message is MAC PDU or RRC signaling.
  • the first indication information is carried in a media access control subheader of the MAC PDU, Alternatively, the first indication information is carried in a MAC CE of the MAC PDU.
  • the first message is a MAC PDU.
  • the second indication information is carried in a media access control subheader of the MAC PDU, Alternatively, the second indication information is carried in a MAC CE of the MAC PDU.
  • the first message is a MAC PDU or RRC signaling.
  • the first message is DCI .
  • the processing unit is further configured not to start or restart the activity timer.
  • any one of the first to eleventh possible implementation manners of the seventeenth aspect in the twelfth possible implementation manner of the seventeenth aspect, if the first The message indicates time information of the terminal device sleeping. If an activity timer is running, the processing unit is further configured to stop the activity timer, or the processing unit is further configured to stop and reset the activity timer. .
  • the processing unit is further configured to stop the continuous timer, or the processing unit is further configured to stop and reset the continuous timer. .
  • the processing unit is further configured to stop the retransmission timer, or the processing unit is further configured to stop and reset the retransmission timer. Transfer timer.
  • the present application further provides a terminal device, where the terminal device includes a transceiver, at least one memory, and at least one processor, where:
  • the transceiver is used for receiving and sending signals or messages when receiving a call from the processor; the processor is used for coupling with the memory, calling a program in the memory, and performing the following steps: controlling the transceiver to receive data from A first message of a communication device, the first message indicating time information for the terminal device to wake up or sleep; if the first message indicates time information for the terminal device to wake up, based on the time information; or If the first message indicates time information for the terminal device to sleep, it sleeps based on the time information.
  • the first message includes first indication information, and the first indication information indicates the time information.
  • the first message includes second instruction information, and the second instruction The information indicates that the terminal device wakes up or sleeps.
  • the time information is the The length of time that the terminal device wakes up or sleeps; or the time information is the length of time before the terminal device wakes up or sleeps; or the time information is the time that the terminal device wakes up or sleeps ends.
  • the time length is: one or more milliseconds; or, one or more subframes; or One or more time slots; or one or more discontinuous reception DRX cycles; or one or more OnDurations; or one or more paging opportunities (PO); or one or more Physical downlink control channel PDCCH monitoring opportunity; or, the length of time in milliseconds; or the length of time in subframes; or the length of time in slots; or the unit of discontinuous reception DRX cycle
  • the first message is MAC PDU or RRC signaling.
  • the first indication information is carried in a media access control subheader of the MAC PDU, Alternatively, the first indication information is carried in a MAC CE of the MAC PDU.
  • the first message is a MAC PDU.
  • the second indication information is carried in a media access control subheader of the MAC PDU, Alternatively, the second indication information is carried in a MAC CE of the MAC PDU.
  • the first message is a MAC PDU or RRC signaling.
  • the first message is DCI .
  • the processor is further configured to not start or restart the activity timer.
  • the processor is further configured to stop the activity timer, or the processor is further configured to stop and reset the activity timer. .
  • the processor is further configured to stop the continuous timer, or the processor is further configured to stop and reset the continuous timer. .
  • the processor is further configured to stop the retransmission timer, or the processor is further configured to stop and reset the retransmission timer. Transfer timer.
  • the present application further provides a computer storage medium, where the computer storage medium stores computer-executable instructions, and the computer-executable instructions are used to cause the computer to execute the foregoing when called by the computer Any of the methods mentioned in the sixteenth aspect.
  • the present application also provides a computer program product containing instructions that, when run on a computer, causes the computer to execute any one of the methods mentioned in the sixteenth aspect above.
  • the present application further provides a chip, which is connected to a memory, and is configured to read and execute program instructions stored in the memory to implement any of the aforementioned sixteenth aspects. method.
  • FIG. 1 is a schematic diagram of a DRX cycle provided by this application.
  • FIG. 2 is an architecture diagram of a communication system provided by the present application.
  • FIG. 3 is a flowchart of a sleep method of a terminal device provided by the present application.
  • FIG. 4 is a schematic diagram of a preset time of a monitoring signal provided by the present application.
  • FIG. 5 is a schematic diagram of a preset time of another monitoring signal provided by the present application.
  • FIG. 6 is a schematic diagram of a preset time of a monitoring signal provided by the present application.
  • FIG. 7 is a flowchart of another method for sleeping a terminal device provided by this application.
  • FIG. 8 is a flowchart of another sleep method for a terminal device provided by this application.
  • FIG. 9 is a flowchart of another method for sleeping a terminal device provided by this application.
  • FIG. 10 is a flowchart of another sleep method of a terminal device provided by this application.
  • FIG. 11 is a flowchart of another method for sleeping a terminal device provided by this application.
  • FIG. 12 is a flowchart of another sleep method of a terminal device provided by this application.
  • FIG. 13 is a flowchart of another sleep method of a terminal device provided by this application.
  • 15 is a flowchart of another method for sleeping a terminal device provided by this application.
  • 16 is a schematic structural diagram of a terminal device provided by this application.
  • FIG. 17 is a structural diagram of a terminal device provided by this application.
  • 21 is a schematic diagram of a first message provided by the present application.
  • FIG. 22 is a schematic diagram of a first message provided by the present application.
  • FIG. 23 is a schematic diagram of a first message provided by this application.
  • FIG. 24 is a schematic diagram of a first message provided by this application.
  • FIG. 25 is a schematic diagram of a first message provided by the present application.
  • the embodiments of the present application provide a sleep method and device of a terminal device, which are used to implement a requirement for saving power consumption.
  • the methods and devices described in this application are based on the same inventive concept. Since the principles of the methods and devices for solving problems are similar, the implementation of the devices and methods can be referred to each other, and duplicated details will not be repeated.
  • the DRX cycle may include an “OnDuration” part and an “Opportunity for DRX” part as shown in FIG. 1.
  • the terminal device monitors and receives the PDCCH during the “OnDuration” time, and the UE may not monitor or receive the PDCCH during the “Opportunity for DRX” time to reduce power consumption.
  • the DRX cycle can be divided into a short DRX cycle (Short DRX Cycle) or a long DRX cycle (Long DRX cycle). It should be noted that receiving the PDDCH by the terminal device means that the terminal device receives downlink control information (DCI) carried on the PDCCH.
  • DCI downlink control information
  • Wake-up signal which is used to instruct the terminal device to wake up. If no wake-up signal is received within a preset time, the terminal device is instructed to sleep by default.
  • Go-to-sleep signal used to instruct the terminal device to sleep. If no sleep signal is received within a preset time, the terminal device is instructed to wake up by default.
  • the "plurality (species)" in the embodiments of the present application refers to two (species) or two (species) or more.
  • the activity timers are shown as InactivityTimer
  • the retransmission timers are shown as RetransmissionTimer
  • the short-cycle timers are shown as ShortCycleTimer.
  • a possible communication system architecture used by the dormancy method of the terminal device provided in the embodiments of the present application may include a network open function network element, a policy control function network element, a data management network element, an application function network element, and a core network access And mobility management function network element, session management function network element, terminal equipment, access network equipment, user plane function network element and data network.
  • FIG. 2 shows a possible example of the architecture of the communication system, which specifically includes: NEF network element, PCF network element, UDM network element, AF network element, AMF network element, SMF network element, UE, and interface. Access network (AN) equipment, UPF network elements and data network (DN).
  • the AMF network element and the terminal device can be connected through the N1 interface
  • the AMF and the AN device can be connected through the N2 interface
  • the AN device and the UPF can be connected through the N3 interface
  • the SMF and the UPF can be connected through the N4 interface.
  • UPF and DN can be connected through N6 interface.
  • the interface name is only an example description, which is not specifically limited in the embodiment of the present application. It should be understood that the embodiment of the present application is not limited to the communication system shown in FIG. 2, and the names of the network elements shown in FIG. 2 are only used as an example here, and are not used in the architecture of the communication system applicable to the method of the present application. Limitation of included network elements. The functions of each network element or device in the communication system are described in detail below:
  • the terminal device can also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., which is a method for providing voice and / or data connectivity to users.
  • sexual equipment For example, the terminal device may include a handheld device with a wireless connection function, a vehicle-mounted device, a computing device, a mobile station (MS) or other processing device connected to a wireless modem, and the like, and an access network and one or Mobile terminals that communicate with multiple core networks.
  • the terminal device may be: a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a mobile Internet device (MID), a wearable device, a virtual reality (VR) device, and an enhanced device.
  • MID mobile Internet device
  • VR virtual reality
  • Augmented reality (AR) equipment wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, smart grid ), Wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes.
  • the terminal device described in FIG. 2 is shown by a UE, which is merely an example, and does not limit the terminal device.
  • the wireless access network may be an access network (AN) shown in FIG. 2 to provide wireless access services to the terminal device.
  • the access network device is a device in the communication system that connects the terminal device to a wireless network.
  • the access network device is a node in a wireless access network, and may also be called a base station, and may also be called a radio access network (RAN) node (or device).
  • RAN radio access network
  • access network equipment are: gNB, transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), node B (Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home NodeB, or home NodeB, HNB), baseband unit (base band unit (BBU), or wireless fidelity (Wifi) access point (AP).
  • TRP transmission reception point
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station e.g., home NodeB, or home NodeB, HNB
  • BBU baseband unit
  • Wifi wireless fidelity
  • the data network such as the data network (DN) shown in FIG. 2, may be the Internet, the IP Multi-media Service (IMS) network, or the regional network (that is, a local network, such as mobile Edge computing (mobile edge computing (MEC) network) and so on.
  • the data network includes an application server, and the application server provides business services to the terminal device through data transmission with the terminal device.
  • the core network is used to connect the terminal device to a DN that can implement services of the terminal device.
  • the functions of each network element in the core network are described below:
  • the core network access and mobility management function network element can be used to manage the access control and mobility of the terminal device. In practical applications, it includes a network in long term evolution (LTE)
  • LTE long term evolution
  • the mobility management function in the mobility management entity (MME) and the access management function are added in the framework, which can be specifically responsible for the registration of the terminal device, mobility management, tracking area update process, reachability detection, Selection of network elements for session management functions, mobile state transition management, etc.
  • the core network access and mobility management function network element may be an AMF (access and mobility management function) network element.
  • AMF access and mobility management function
  • the core network The access and mobility management function network element may still be an AMF network element or have another name, which is not limited in this application.
  • the AMF may provide a Namf service.
  • the session management function network element may be used for session management (including establishment, modification, and release of the session) of the terminal device, selection and reselection of user plane function network elements, Internet protocol of the terminal device (internet protocol) (IP) address allocation, quality of service (QoS) control, etc.
  • the session management function network element may be an SMF (session management function) network element, as shown in FIG. 2.
  • the session management function network element may still be an SMF network. Yuan, or other names, this application is not limited.
  • the SMF may provide an Nsmf service.
  • the policy control function network element can be used for policy control decisions, providing functions such as service data flow and application detection, gating, QoS, and flow-based charging control.
  • the policy control function network element may be a PCF (policy control function) network element, as shown in FIG. 2.
  • the policy control function network element may still be a PCF network. Yuan, or other names, this application is not limited.
  • the PCF network element may provide an Npcf service.
  • the main function of the application function network element is to interact with the 3rd Generation Partnership Project (3GPP) core network to provide services to affect service flow routing, access network capability opening, and policy control.
  • 3GPP 3rd Generation Partnership Project
  • the application function network element may be an AF (application function) network element, as shown in FIG. 2.
  • the application function network element may still be an AF network element, or There are other names, which are not limited in this application.
  • the application function network element is an AF network element, the AF network element may provide a Naf service.
  • the data management network element may be used to manage subscription data of the terminal device, registration information related to the terminal device, and the like.
  • the data management network element may be a unified data management network element (UDM), for example, as shown in FIG. 2.
  • UDM unified data management network element
  • the data management network element may still be UDM network elements, or other names, are not limited in this application.
  • the UDM network element may provide a Nudm service.
  • the network open function network element can be used to enable 3GPP to securely provide network service capabilities to third-party AFs (for example, Services Capability Server (SCS), Application Server (AS), etc.).
  • the network open function network element may be a NEF (network exposure function) network element, as shown in FIG. 2.
  • NEF network exposure function
  • the network open function network element may still be a NEF network. Yuan, or other names, this application is not limited.
  • the network open function network element is a NEF
  • the NEF may provide Nnef services to other network function network elements.
  • the user plane function network element may be used to forward user plane data of the terminal device.
  • the main functions are data packet routing and forwarding, mobility anchors, uplink classifiers to support routing service flows to the data network, and branch points to support multi-homed packet data unit (PDU) sessions.
  • the user plane function network element may be a UPF (user plane function) network element, as shown in FIG. 2; in future communications, such as 6G, the user plane function network element may still be a UPF network. Yuan, or other names, this application is not limited.
  • Each of the above network elements in the core network can also be called a functional entity, which can be a network element implemented on dedicated hardware, or a software instance running on dedicated hardware, or an instance of a virtualized function on an appropriate platform
  • the above virtualization platform may be a cloud platform.
  • FIG. 2 the architecture of the communication system shown in FIG. 2 is not limited to only the network elements shown in the figure, and may also include other devices not shown in the figure.
  • the specific applications in this application are not listed here one by one. .
  • each network element in the core network does not limit the distribution form of each network element in the core network.
  • the distribution form shown in FIG. 2 is only exemplary, and is not limited in the present application.
  • the following description uses the network element shown in FIG. 2 as an example for description, and the XX network element is simply referred to as XX. It should be understood that the names of all network elements in this application are merely examples, and may be called other names in future communications, or the network elements involved in this application in future communications may also be obtained by other entities or devices with the same function. Instead, this application does not limit this. The description is unified here, and will not be repeated later.
  • the communication system shown in FIG. 2 does not constitute a limitation of the communication system applicable to the embodiment of the present application.
  • the communication system architecture shown in FIG. 2 is a 5G system architecture.
  • the method in the embodiment of the present application is also applicable to various future communication systems, such as 6G or other communication networks.
  • the hibernation method for a terminal device provided in the embodiment of the present application is applicable to a communication system as shown in FIG. 2.
  • the specific process of the method includes:
  • Step 301 The terminal device monitors a signal within a preset time.
  • the terminal device is configured with DRX, that is to say, the terminal device adopts the DRX cycle shown in FIG. 1, and monitors and receives the PDCCH in the OnDuration in the DRX cycle.
  • the terminal device can Do not listen or receive PDCCH to reduce power consumption.
  • the preset time may be a certain time point or a certain period of time.
  • the preset time may be a specific time position of an offset before the start of the DRX cycle, and may be a time point of monitoring a signal as shown in FIG. 4;
  • the preset time may be a time position at the beginning of the OnDuration time of the DRX cycle (that is, the offset value in the solution shown in FIG. 4 is 0, for example, it may be Time point of the monitoring signal as shown in FIG. 5).
  • the preset time when the preset time is a certain time point, the preset time may be any time within an OnDuration time in a DRX cycle, such as the time point of the monitoring signal shown in FIG. 6; or, The preset time may also be any time within the "activation time" of the DRX.
  • the preset time when the preset time is a certain period of time, the preset time may be a period of time starting from a specific time position (which may be a time point in the above description), and the period of time is one or more Symbol length, or length of one or more subframes, or, one or more milliseconds, or the preset time may end at a specific time position (which may be a time point in the above description) The previous period of time, such as one or more symbol lengths, or one or more subframe lengths, or one or more milliseconds.
  • the preset time when the preset time is a certain period of time, the preset time may be an OnDuration time in a DRX cycle, such as a time period of a monitoring signal shown in FIG.
  • the preset time may also be Can be the "activation time" of DRX. It should be noted that the situation of the preset time in the above example is merely an example, and is not intended to limit the preset time of the present application. The preset time may also have various other situations, which are not enumerated in this application.
  • the terminal device listening for a signal within a preset time may specifically be: the terminal device listening for a sleep signal, a wake-up signal, or an indication signal within a preset time.
  • the instruction signal may include instruction information, and the instruction information may indicate sleep or wake-up, that is, sleep instruction information and wake-up instruction information.
  • sleep the instruction signal includes the sleep instruction information
  • wake-up the instruction signal includes the wake instruction information.
  • the signal may or may not be received.
  • the form of the signal may be a physical layer sequence, or may be downlink control information (DCI), or may be medium access control (MAC) ) Control unit (CE) (MAC) (CE), or may be a medium access control (MAC) protocol data unit (PDU) (MAC PDU).
  • DCI downlink control information
  • MAC medium access control
  • CE Control unit
  • PDU protocol data unit
  • the terminal device when the terminal device monitors (that is, receives) the sleep signal within the preset time, or does not monitor the wake-up signal, or monitors including the sleep signal, In the indication signal of the sleep indication information, the terminal device does not need to start onDurationTimer in the following n (n is an integer greater than or equal to 1) DRX cycles, or the terminal device does not need to be in the subsequent set duration.
  • Start the onDurationTimer that is, the terminal device can sleep.
  • the onDurationTimer may also be referred to as drx-onDurationTimer. In the embodiment of the present application, only the onDurationTimer is used as an example for description. It should be understood that the onDurationTimer may be replaced by the drx-onDurationTimer.
  • the terminal device when the terminal device monitors (that is, receives) the wake-up signal within the preset time, or does not monitor the sleep signal, or monitors that includes the When the wake-up information indication signal, the terminal device needs to wake up in the following n (n is an integer greater than or equal to 1) DRX cycles, or the terminal device needs to wake up in the subsequent set time, That is, you need to enable onDurationTimer.
  • the set duration may be an absolute time length, for example, N milliseconds (ms), or N subframe lengths, or N symbol lengths, or N symbol lengths. Slot length, etc., or N physical downlink control channel monitoring opportunities (PDCCH monitoring), where N is a number greater than zero or N is an integer greater than zero; or the sleep duration may be in units of a DRX cycle or Take "OnDuration" time as a unit, for example, N DRX cycles or N "OnDuration" times, where N is an integer greater than zero.
  • the sleep duration may also be other time length information, which is not specifically limited in this application.
  • step 301 is an optional step, that is, the terminal device may not perform this step, but determines in other ways whether the terminal device receives a signal indicating wake-up within the preset time period, and further Go to step 302. This application does not limit this.
  • Step 302 If the terminal device does not receive a signal indicating wake-up within a preset time, if the InactivityTimer is running, the terminal device stops the InactivityTimer.
  • the InactivityTimer may also be referred to as drx-InactivityTimer. In the embodiment of the present application, only the InactivityTimer is used as an example for description. It should be understood that the InactivityTimer may be replaced by drx-InactivityTimer.
  • the terminal device does not receive a signal indicating wake-up within the preset time, which may be any one of the following three cases:
  • Case a1 The terminal device receives a sleep signal within a preset time.
  • Case a2 The terminal device does not receive a wake-up signal within a preset time.
  • Case a3 The terminal device receives an instruction signal within a preset time, and the instruction signal includes sleep instruction information.
  • the terminal device needs to sleep, so when the InactivityTimer is running, the terminal device needs to stop the InactivityTimer. In this way, the terminal device can truly go to sleep, without being affected by the InactivityTimer and remaining activated for a period of time, so that power consumption can be better saved, and the demand for power saving can be met.
  • the terminal device stopping the InactivityTimer may specifically be: the terminal device stops the InactivityTimer when the terminal device does not receive a signal indicating wake-up within the preset time (or after). Or, the terminal device stops the InactivityTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the (current) DXR cycle is a DRX cycle in which the preset time is located, and the start of the next DRX cycle refers to an OnDuration start position of the next DRX cycle. It should be noted that both the (current) cycle and the next cycle involved in the following embodiments of the present application can be understood as the above description, and are not repeated one by one in the following.
  • the InactivityTimer when the terminal device does not receive a signal indicating wake-up within the preset time (or after), the InactivityTimer is stopped, which may specifically refer to : The terminal device stops the InactivityTimer when receiving the sleep signal or when receiving the indication signal (or after).
  • the terminal device may also reset the InactivityTimer, that is, set the value of the InactivityTimer to an initial value (for example, 0). In this way, when the InactivityTimer needs to be turned on next time, the InactivityTimer can be timed from 0 to avoid affecting the normal process.
  • the terminal device Due to the current DRX mechanism, if the terminal device is configured with a short DRX cycle, when the InactivityTimer times out, the terminal device needs to start or restart the short cycle timer ShortCycleTimer to enable the terminal device to use the Short DRX cycle. Therefore, in an optional implementation manner, the terminal device stops the InactivityTimer, and the terminal device starts or restarts the ShortCycleTimer. In this way, when the terminal device stops the InactivityTimer in time, the original DRX mechanism is also maintained, and the terminal device can continue to use the short DRX cycle.
  • the starting or restarting of the ShortCycleTimer by the terminal device may be: starting (or after) the terminal device when the terminal device does not receive a signal indicating wakeup within the preset time (or after).
  • the ShortCycleTimer; or the terminal device starts or restarts the ShortCycleTimer at the beginning of the next DRX cycle of the (current) DRX cycle. That is, the terminal device starts or restarts the ShortCycleTimer while stopping the InactivityTimer.
  • the terminal device when the terminal device does not receive a signal indicating wake-up within the preset time, a network device (such as a base station) will not schedule the terminal device in a subsequent period of time, and the terminal may subsequently A short DRX cycle is not applicable, but a long DRX cycle is used to achieve more power saving. Therefore, in an optional implementation manner, the terminal device stops the InactivityTimer, and the terminal device uses a long DRX cycle. DRX cycle.
  • the terminal device if the terminal device needs to use a long DRX cycle, if the ShortCycleTimer is running, the terminal device stops the ShortCycleTimer, or the terminal device stops and resets all Said ShortCycleTimer. In this way, the terminal device can successfully switch from a short DRX cycle to a long DRX cycle.
  • the terminal device stops the ShortCycleTimer, or stops and resets the ShortCycleTimer. Specifically, the terminal device does not receive a signal indicating wake-up within the preset time. Time (or after), stop the ShortCycleTimer, or stop and reset the ShortCycleTimer; it may also be: when the terminal device starts the next DRX cycle of the (current) DRX cycle, stop the ShortCycleTimer, or stop and Reset the ShortCycleTimer.
  • the terminal device stops the onDurationTimer.
  • the onDurationTimer may also be referred to as drx-onDurationTimer.
  • the onDurationTimer is used as an example for description. It should be understood that the onDurationTimer can be replaced with drx-onDurationTimer.
  • the terminal device does not receive a signal indicating wake-up within the "OnDuration" time of the DRX cycle, it can also be understood that the preset time is within the "OnDuration" time of the DRX cycle, and at this time the onDurationTimer may be running , The terminal device stops the onDurationTimer.
  • the terminal device stopping the onDurationTimer may specifically be: the terminal device stopping the onDurationTimer when the terminal device does not receive a signal indicating wake-up within the preset time (or after). Or, the terminal device stops the onDurationTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the onDurationTimer when the terminal device does not receive a signal indicating wake-up within the preset time (or after), the onDurationTimer is stopped, which may specifically refer to : The terminal device stops the onDurationTimer when receiving the sleep signal or when receiving the indication signal (or after).
  • the terminal device may also reset the onDurationTimer, that is, set the value of the onDurationTimer to an initial value (for example, 0). In this way, when the onDurationTimer needs to be turned on next time, the onDurationTimer can be timed from 0 to avoid affecting the normal process.
  • the terminal device when the signal is DCI, the terminal device does not start or restart the activity timer InactivityTimer.
  • the terminal device when a terminal device receives a DCI (PDCCH) indicating a new transmission, the terminal device needs to start or restart the InactivityTimer in order to receive subsequent scheduled data.
  • the signal may have other indication functions in addition to event information that can indicate the terminal device to wake up or sleep.
  • the signal may also indicate a new transmission.
  • the terminal device when the signal is a DCI indicating a new transmission, the terminal device does not start or restart the InactivityTimer.
  • the terminal device With the sleeping method of the terminal device provided in the embodiment of the present application, if the terminal device does not receive a signal indicating wake-up within a preset time, if the InactivityTimer is running, the terminal device stops the InactivityTimer. In the prior art, if the InactivityTimer is running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer expires. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 701 The terminal device monitors a signal within a preset time.
  • the step 701 is similar to the step 301 in the embodiment shown in FIG. 3, and for details, reference may be made to the description in the above step 301, and the overlap is not repeated here.
  • Step 702 If the terminal device does not receive a signal indicating wake-up within the preset time, and if RetransmissionTimer is running, the terminal device stops the RetransmissionTimer.
  • the RetransmissionTimer may also be referred to as drx-RetransmissionTimer.
  • the RetransmissionTimer is used as an example for description. It should be understood that the RetransmissionTimer may be replaced by drx-RetransmissionTimer.
  • the terminal device does not receive a signal indicating wake-up within the preset time, and in step 302 shown in FIG. 3, the terminal device does not receive a signal indicating wake-up within a preset time.
  • the signals are the same. For details, refer to the related descriptions involved in step 302 above. Details are not repeated here.
  • the RetransmissionTimer may be one or more of an uplink retransmission timer (RetransmissionTimer (uplink, UL)) and a downlink retransmission timer (RetransmissionTimer (downlink, DL)).
  • the RetransmissionTimer UL may also be recorded as drx-RetransmissionTimer UL; the RetransmissionTimer DL may also be recorded as drx-RetransmissionTimer DL; in the embodiment of the present application, only the RetransmissionTimer UL and RetransmissionTimer DL are used as examples for description. It should be understood that the RetransmissionTimer UL may be replaced by drx-RetransmissionTimer UL; the RetransmissionTimer DL may be replaced by drx-RetransmissionTimer DL.
  • the terminal device stops the RetransmissionTimer, which can be specifically divided into the following three cases:
  • the terminal device stopping the RetransmissionTimer may specifically be: the terminal device stops the RetransmissionTimer when (or after) the terminal device does not receive a signal indicating wake-up within the preset time. Or, the terminal device stops the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the terminal device stops the RetransmissionTimer when the terminal device does not receive a signal indicating wake-up within the preset time (or after), which may specifically refer to :
  • the terminal device stops the RetransmissionTimer when receiving the sleep signal or when receiving the indication signal (or after).
  • the terminal device may also reset the RetransmissionTimer, that is, set the value of the RetransmissionTimer to an initial value (for example, 0). In this way, when the RetransmissionTimer needs to be turned on next time, the RetransmissionTimer can be timed from 0 to avoid affecting the normal process.
  • the terminal device stops the RetransmissionTimer.
  • the terminal device stops the RetransmissionTimer.
  • the terminal device needs to remain activated for a period of time until the timer expires. In other words, through the above method, the terminal device can be truly put to sleep, which can better save power consumption and meet the demand for saving power consumption.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 801 The terminal device monitors a signal within a preset time.
  • step 801 is similar to step 301 in the embodiment shown in FIG. 3, and for details, reference may be made to the description in step 301 above, and details are not repeated herein.
  • Step 802 If the terminal device does not receive a signal indicating wake-up within the preset time, and if the InactivityTimer and the RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer.
  • the InactivityTimer is similar to the InactivityTimer involved in the embodiment shown in FIG. 3. For details, refer to the description of the InactivityTimer in the embodiment shown in FIG.
  • the RetransmissionTimer involved in the illustrated embodiment is similar. For details, refer to the description of the RetransmissionTimer in the embodiment shown in FIG. 3, and details are not repeated here.
  • the RetransmissionTimer may be one or more of RetransmissionTimer UL and RetransmissionTimer DL. Therefore, if the InactivityTimer and the RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer, which can be specifically classified into the following three cases:
  • Case c2 If the InactivityTimer and the RetransmissionTimer DL are running, the terminal device stops the InactivityTimer and the RetransmissionTimer DL.
  • Case c3 If the InactivityTimer, the RetransmissionTimer UL, and the RetransmissionTimer DL are running, the terminal device stops the InactivityTimer, the RetransmissionTimer UL, and the RetransmissionTimer DL.
  • the terminal device stopping the InactivityTimer and the RetransmissionTimer may specifically be: when the terminal device does not receive a signal indicating wake-up within the preset time (or after) Stop the InactivityTimer and the RetransmissionTimer; or, the terminal device stops the InactivityTimer and the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the related solution for the terminal device to stop the InactivityTimer is similar to the related solution involved in step 302 in the embodiment shown in FIG. 3, and specific reference may be made to each other, and details are not described herein again; and the terminal device
  • the related scheme for stopping the RetransmissionTimer is similar to the related scheme involved in step 702 in the embodiment shown in FIG. 7, and specific reference may be made to each other, and details are not described herein again.
  • the terminal device may also reset the InactivityTimer and the RetransmissionTimer, that is, set the values of the InactivityTimer and the RetransmissionTimer to initial values ( (E.g. 0). In this way, when the InactivityTimer and the RetransmissionTimer need to be turned on next time, the InactivityTimer and the RetransmissionTimer can be timed from 0 to avoid affecting the normal process.
  • the terminal device stops the InactivityTimer and the RetransmissionTimer.
  • the terminal device needs to remain activated for a period of time until the timer ends. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • An embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to a communication system as shown in FIG. 2. As shown in FIG. 9, the specific process of the method includes:
  • Step 901 The terminal device receives a signal indicating sleep from a communication device.
  • the terminal device may be configured with or without DRX, which is not limited in this embodiment.
  • the receiving, by the terminal device, a signal indicating sleep from the communication device may specifically include: receiving, by the terminal device, a sleep signal from the communication device; or, the terminal device Receiving an instruction signal from the communication device, where the instruction signal includes sleep instruction information.
  • the case where the hibernation signal and the indication signal include the hibernation indication information is similar to the hibernation signal and the signal containing the hibernation indication information involved in step 301 in the embodiment shown in FIG. 3, and can be referred to each other.
  • the form of the signal indicating the hibernation is similar to the form of the signal indicating the wake-up in the embodiment shown in FIG. 3.
  • the description of the form of the signal involved in step 301 They are not listed here one by one.
  • the communication device may be a network device, such as a base station, or may be another device, such as a terminal device.
  • the terminal device and the terminal device can communicate directly without going through a network device. At this time, the terminal device can receive a message sent by another terminal device. signal.
  • D2D device-to-device
  • Step 902 The terminal device starts or restarts a sleep timer, and sleeps during the running of the sleep timer.
  • the sleeping of the terminal device during the running of the sleep timer may include: the terminal device is in the The PDCCH is not monitored during the sleep timer operation.
  • the terminal device sleeping during the sleep timer may further include the following three modes:
  • Mode d1 The terminal device does not send a type-0-triggered (sounding reference signal) (SRS) triggered during a sleep timer operation.
  • SRS sounding reference signal
  • Method d2 or the terminal device does not report channel state information (CSI) during the running of the sleep timer.
  • CSI channel state information
  • Mode d3 The terminal device does not send the type-0-triggered SRS and does not report the CSI during the sleep timer operation.
  • the terminal device before the terminal device receives a signal indicating sleep from the communication device (that is, performs the foregoing steps), the terminal device further receives a sleep duration configured by the communication device, for example, The terminal device may receive an RRC message, and the RRC message includes the sleep duration configured by the communication device. In this way, the terminal device may subsequently configure a required sleep duration for the sleep timer. It should be noted that, when the sleep timer is started or restarted, the sleep timer will run for such a long time as "sleep duration", and when the sleep time is run for such a long time, the sleep sleep may be considered The timer expired.
  • the signal includes indication information, where the indication information indicates a sleep duration.
  • the instruction information may indicate the sleep duration: the instruction information may be the sleep duration directly. In this case, the terminal device may directly know the sleep duration; or the instruction information may indicate the sleep duration.
  • the indication information may also indicate the sleep duration in other ways, which is not specifically limited in this application.
  • the terminal device when the instruction information indicates one of at least one duration configured by the communication device, before the terminal device receives a signal indicating sleep from the communication device, the terminal device The terminal device also receives at least one duration configured by the communication device. For example, the terminal device may receive an RRC message, where the RRC message includes the at least one duration configured by the communication device, and the sleep duration is the at least one One of a duration.
  • the terminal device further configures the terminal device after the terminal device learns the sleep duration in any of the foregoing ways, and before the terminal device starts or restarts the sleep timer.
  • the timing duration of the sleep timer is the sleep duration. In this way, the terminal device can sleep for the sleep duration as needed.
  • the sleep duration may be an absolute time length, for example, N ms, or N subframe lengths, or N symbol lengths, or N timeslot lengths ( slots), or N physical downlink control channel monitoring opportunities (PDCCH monitoring), where N is a number greater than zero or N is an integer greater than zero; or, the sleep duration may be in units of a DRX cycle or in an "On Duration" "Time is a unit, such as N DRX cycles or N" OnDuration "times, and N is an integer greater than zero.
  • the sleep duration may also be other time length information, which is not specifically limited in this application.
  • the terminal device when the signal indicating sleep is DCI, the terminal device does not start or restart the activity timer InactivityTimer.
  • the terminal device when a terminal device receives a DCI (PDCCH) indicating a new transmission, the terminal device needs to start or restart the InactivityTimer in order to receive subsequent scheduled data.
  • the signal indicating sleep may also have other indication functions.
  • the signal indicating sleep may also indicate a new transmission.
  • the terminal device does not start or restart the InactivityTimer.
  • the sleep timer has a higher priority than other timers of "activation time". For example, when onDurationTimer and InactivityTimer are running, as long as the sleep timer is running, the terminal The device will sleep; for example, when the onDurationTimer, the InactivityTimer, and the RetransmissionTimer are all running, as long as the sleep timer is running, the terminal device will sleep.
  • the terminal device starts or restarts a sleep timer after receiving a signal indicating sleep from a communication device, and sleeps during the running of the sleep timer; wherein the terminal device Sleeping during the running of the sleep timer includes: the terminal device does not listen to the PDCCH during the running of the sleep timer.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 1001 The terminal device monitors a signal.
  • the terminal device can monitor signals within a preset duration; specifically, when the terminal device monitors signals within the preset duration, steps 1001 and FIG. 3 Step 301 in the illustrated embodiment is similar.
  • steps 1001 and FIG. 3 Step 301 in the illustrated embodiment is similar.
  • Step 1002 If the terminal device receives a signal indicating sleep, and if InactivityTimer is running, the terminal device stops the InactivityTimer.
  • the receiving of the signal indicating sleep by the terminal device may specifically include: receiving the sleep signal by the terminal device; or receiving the instruction signal by the terminal device, the instruction signal Contains hibernation instructions.
  • the terminal device stops the InactivityTimer, and if the InactivityTimer involved in step 302 in the embodiment shown in FIG. 3 is running, the terminal device stops the InactivityTimer
  • the method of InactivityTimer is similar. For details, refer to the related description involved in step 302, and details are not repeated here.
  • the terminal device With the sleep method of the terminal device provided in the embodiment of the present application, if the terminal device receives a signal indicating sleep, if the InactivityTimer is running, the terminal device stops the InactivityTimer. In the prior art, if the InactivityTimer is running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer expires. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 1101 The terminal device monitors a signal.
  • the terminal device can monitor signals within a preset duration; specifically, when the terminal device monitors signals within the preset duration, the steps 1101 and FIG. 3 Step 301 in the illustrated embodiment is similar.
  • the steps 1101 and FIG. 3 Step 301 in the illustrated embodiment is similar.
  • Step 1102 If the terminal device receives a signal indicating sleep, and if RetransmissionTimer is running, the terminal device stops the RetransmissionTimer.
  • the terminal device receives the signal indicating sleep is the same as the case where the terminal device involved in step 1001 receives the signal indicating sleep, which can be referred to each other for details, and will not be repeated here. .
  • the terminal device stops the RetransmissionTimer, which is similar to the related method involved in step 702 in the embodiment shown in FIG. 7. For details, see step 702 above. Relevant descriptions involved in the description will not be repeated here.
  • the terminal device With the sleep method of the terminal device provided in the embodiment of the present application, if the terminal device receives a signal indicating wake-up, if the RetransmissionTimer is running, the terminal device stops the RetransmissionTimer. In the prior art, if the RetransmissionTimer is running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer expires. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 1201 The terminal device monitors the signal.
  • the terminal device can monitor signals within a preset duration; specifically, when the terminal device monitors signals within the preset duration, the steps 1101 and FIG. 3 Step 301 in the illustrated embodiment is similar.
  • the steps 1101 and FIG. 3 Step 301 in the illustrated embodiment is similar.
  • Step 1202 If the terminal device receives a signal indicating sleep, and if the InactivityTimer and the RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer.
  • the terminal device receives the signal indicating sleep is the same as the case where the terminal device involved in step 1001 receives the signal indicating sleep, which can be referred to each other for details, and will not be repeated here. .
  • the terminal device stops the InactivityTimer and the RetransmissionTimer, which is similar to the related method involved in step 802 in the embodiment shown in FIG. 8. For details, refer to the above-mentioned step 802. Related descriptions are not repeated here.
  • the terminal device With the sleep method of the terminal device provided in the embodiment of the present application, if the terminal device receives a signal indicating sleep, if the InactivityTimer and RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer.
  • the terminal device if InactivityTimer and RetransmissionTimer are running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer ends. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 1301 The terminal device receives an instruction message, where the instruction message is used to instruct the terminal device to stop a specific timer.
  • the terminal device is configured with DRX, that is to say, the terminal device adopts the DRX cycle shown in FIG. 1, and monitors and receives the PDCCH in the OnDuration in the DRX cycle.
  • the terminal device can Do not listen or receive PDCCH to reduce power consumption.
  • the specific timer may be one or more of onDurationTimer, InactivityTimer, and RetransmissionTimer (RetransmissionTimerUL and / or RetransmissionTimerDL).
  • the instruction message may be a new message, or an existing message (or signaling) may be reused, and an "instruction" is added to the existing function of the existing message (or signaling).
  • the terminal device stops the specific timer function that is, the instruction message may have other functions besides the capability of "instructing the terminal device to stop the specific timer", which is not limited in this application.
  • the instruction message may reuse an existing long DRX control MAC (CE), or the instruction message may reuse an existing DRX control MAC (CE).
  • the terminal device may receive an instruction message from a communication device, for example, as shown in the figure.
  • the communication device may be a network device, such as a base station, or may be another Equipment, such as terminal equipment.
  • the indication message may be in a form of a physical layer sequence, or a DCI, or a MAC CE, or a MAC PDU.
  • the terminal device may receive the indication message when using a long DRX cycle.
  • the terminal device continues to use the long DRX cycle.
  • the terminal device receives the indication message, not to change the DRX cycle, but mainly to stop one or more of the onDurationTimer, InactivityTimer, and RetransmissionTimer, that is, the terminal device can immediately sleep to achieve more power saving.
  • the network device may send the instruction message to the terminal device, indicating that the terminal device can immediately sleep.
  • the terminal device may receive the instruction message when using a long DRX cycle, and after the terminal device receives the instruction message, the terminal device Use a short DRX cycle; or, the terminal device receives the instruction message when using the short DRX cycle, and after the terminal device receives the instruction message, the terminal device continues to use the short DRX cycle; The terminal device receives the instruction message when using a short DRX cycle, and after the terminal device receives the instruction message, the terminal device uses a long DRX cycle.
  • the terminal device receives the instruction message when using the short DRX cycle, and after the terminal device receives the instruction message, the terminal device continues to use the short DRX cycle
  • the method further includes: the terminal device does not start or restart the short cycle timer ShortCycleTimer.
  • the terminal device receives the indication message, not to replace the DRX cycle, nor to extend the use time of the short DRX cycle, mainly to stop one or more of onDurationTimer, InactivityTimer, and RetransmissionTimer, that is, the terminal.
  • the device can sleep immediately to achieve more power saving.
  • the terminal device starts or restarts the short cycle timer ShortCycleTimer at this time, the time period during which the terminal device is in the short DRX cycle becomes longer, and it takes longer to enter the long DRX cycle, which is not conducive to power saving. Therefore, the terminal device does not start or restart the short cycle timer ShortCycleTimer, so that the cycle timer ShortCycleTimer continues to count, so as to enter the long DRX cycle as soon as possible, so as to achieve the purpose of more power saving.
  • an indication field may be added to an existing message (or signaling), where the indication field indicates whether a short-cycle timer ShortCycleTimer needs to be started or restarted, for example, when the indication field takes a first value Indicates that the short cycle timer ShortCycleTimer needs to be started or restarted.
  • the value of the indication field is the second value, it indicates that the short cycle timer ShortCycleTimer is not started or restarted.
  • Step 1302 If onDurationTimer is running, the terminal device stops the onDurationTimer.
  • the terminal device stopping the onDurationTimer may specifically be: the terminal device stops the onDurationTimer when receiving the instruction message, or the terminal device stops receiving the onDurationTimer Stop the onDurationTimer after the instruction message.
  • the terminal device may also reset the onDurationTimer (the terminal device stops and resets the onDurationTimer), that is, set the value of the onDurationTimer to An initial value (for example, 0), so that when the onDurationTimer needs to be turned on next time, the onDurationTimer can be timed from 0 to avoid affecting the normal process.
  • the onDurationTimer the terminal device stops and resets the onDurationTimer
  • An initial value for example, 0
  • the terminal device stops the RetransmissionTimer; wherein the RetransmissionTimer may be one or more of RetransmissionTimerUL and RetransmissionTimerDL.
  • the RetransmissionTimer UL may also be recorded as drx-RetransmissionTimer UL; the RetransmissionTimer DL may also be recorded as drx-RetransmissionTimer DL; in the embodiment of the present application, only the RetransmissionTimer UL and RetransmissionTimer DL are used as examples for description. It should be understood that the RetransmissionTimer UL may be replaced by drx-RetransmissionTimer UL; the RetransmissionTimer DL may be replaced by drx-RetransmissionTimer DL.
  • the terminal device stops the RetransmissionTimer, which can be specifically divided into the following three cases:
  • the terminal device stopping the RetransmissionTimer may specifically be: the terminal device stops the RetransmissionTimer when receiving the instruction message, or the terminal device receives the Stop the RetransmissionTimer after the instruction message.
  • the terminal device may also reset the RetransmissionTimer (the terminal device stops and resets the RetransmissionTimer), that is, set the value of the RetransmissionTimer to An initial value (for example, 0), so that when the RetransmissionTimer needs to be turned on next time, the RetransmissionTimer can be timed from 0 to avoid affecting the normal process.
  • the RetransmissionTimer the terminal device stops and resets the RetransmissionTimer
  • An initial value for example, 0
  • the terminal device stops the onDurationTimer. It can make the network device stop the onDurationTimer in time when it is determined that the terminal device has no subsequent data transmission, so that the terminal device enters sleep and does not need to remain awake to receive messages. That is to say, through the above method, the terminal device can be hibernated in time, so that power consumption can be better saved, and the demand for power saving can be met.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 1401 The terminal device receives an instruction message, where the instruction message is used to instruct the terminal device to stop a specific timer, wherein the terminal device is configured with DRX.
  • step 1401 is similar to step 1301 in the embodiment shown in FIG. 13.
  • step 1401 is similar to step 1301 in the embodiment shown in FIG. 13.
  • Step 1402 If the InactivityTimer is running, the terminal device stops the InactivityTimer.
  • the terminal device stopping the InactivityTimer may specifically be: the terminal device stops the InactivityTimer when receiving the instruction message, or the terminal device receives the Stop the InactivityTimer after the instruction message.
  • the terminal device may also reset the InactivityTimer (the terminal device stops and resets the InactivityTimer), that is, setting the value of the InactivityTimer to An initial value (for example, 0), so that when the InactivityTimer needs to be turned on next time, the InactivityTimer can be timed from 0 to avoid affecting the normal process.
  • the InactivityTimer the terminal device stops and resets the InactivityTimer
  • An initial value for example, 0
  • the terminal device stops the RetransmissionTimer; wherein the RetransmissionTimer may be one or more of RetransmissionTimerUL and RetransmissionTimerDL.
  • the RetransmissionTimer may be one or more of RetransmissionTimerUL and RetransmissionTimerDL.
  • the terminal device stops the InactivityTimer. It can make the network device stop the InactivityTimer in time when it is determined that the terminal device has no subsequent data transmission, so that the terminal device enters sleep and does not need to remain awake to receive messages. That is to say, through the above method, the terminal device can be hibernated in time, so that power consumption can be better saved, and the demand for power saving can be met.
  • an embodiment of the present application further provides a method for sleeping a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 1501 The terminal device receives an instruction message, where the instruction message is used to instruct the terminal device to stop a specific timer, wherein the terminal device is configured with DRX.
  • step 1501 is similar to step 1301 in the embodiment shown in FIG. 13.
  • step 1501 is similar to step 1301 in the embodiment shown in FIG. 13.
  • Step 1502 If the onDurationTimer and the InactivityTimer are running, the terminal device stops the onDurationTimer and the InactivityTimer.
  • the terminal device stops the onDurationTimer and the InactivityTimer. For details, refer to the related description of the terminal device stopping the onDurationTimer in step 1302 above, and the description in step 1402 above. The terminal device stops the related description related to the InactivityTimer, which is not repeatedly described here.
  • the terminal device stops the RetransmissionTimer; wherein the RetransmissionTimer may be one or more of RetransmissionTimerUL and RetransmissionTimerDL.
  • the RetransmissionTimer may be one or more of RetransmissionTimerUL and RetransmissionTimerDL.
  • the terminal device stops the onDurationTimer and InactivityTimer. It can make the network device stop onDurationTimer and InactivityTimer in time when it is determined that the terminal device has no subsequent data transmission, so that the terminal device enters hibernation and does not need to remain awake to receive messages. That is to say, through the above method, the terminal device can be hibernated in time, so that power consumption can be better saved, and the demand for power saving can be met.
  • each solution of the sleep method of the terminal device provided in the embodiments of the present application is described from the perspective of interaction between each network element or device.
  • each network element and device for example, the foregoing terminal device, includes a hardware structure and / or a software module corresponding to each function.
  • this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • the terminal device when the terminal device provided in this application implements a corresponding function through a software module, the terminal device may include a receiving unit 1601 and a processing unit 1602.
  • the terminal device may include a receiving unit 1601 and a processing unit 1602.
  • the terminal device shown in FIG. 16 may be used to perform operations of the terminal device in the embodiments shown in FIG. 3, FIG. 7, and FIG. 8.
  • the receiving unit 1601 is configured to receive a signal; the processing unit 1602 is configured to stop the InactivityTimer if the receiving unit 1601 does not receive a signal indicating wake-up within a preset time, and if the activity timer InactivityTimer is running Or, if the retransmission timer RetransmissionTimer is running, stop the RetransmissionTimer; or, if the InactivityTimer and the RetransmissionTimer are running, stop the InactivityTimer and the RetransmissionTimer.
  • the terminal device is configured to receive DRX discontinuously.
  • the receiving unit 1601 does not receive a signal indicating wake-up within a preset time, and is specifically configured to: receive a sleep signal within a preset time; or do not receive a signal within a preset time A wake-up signal is received; or an instruction signal is received within a preset time, and the instruction signal includes sleep instruction information.
  • the processing unit 1602 stops the InactivityTimer, and is specifically configured to stop the InactivityTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processing unit 1602 stops the RetransmissionTimer, and is specifically configured to stop the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processing unit 1602 is further configured to: reset the InactivityTimer if the InactivityTimer is running; or reset the RetransmissionTimer if the RetransmissionTimer is running; or if the InactivityTimer and the RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is one or more of an uplink retransmission timer RetransmissionTimerUL and a downlink retransmission timer RetransmissionTimerDL.
  • processing unit 1602 is further configured to stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processing unit 1602 is further configured to stop the InactivityTimer and use a long DRX cycle.
  • the processing unit 1602 is further configured to stop the ShortCycleTimer if the short-cycle timer ShortCycleTimer is running, or stop and reset the ShortCycleTimer.
  • the terminal device Based on the terminal device, if the terminal device does not receive a signal indicating wake-up within a preset time, if the InactivityTimer and / or RetransmissionTimer are running, the terminal device stops the InactivityTimer and / or the RetransmissionTimer. In the prior art, if InactivityTimer and / or RetransmissionTimer are running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer ends. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device shown in FIG. 16 may also be used to perform the operations of the terminal device in the embodiment shown in FIG. 9.
  • the receiving unit 1601 is configured to receive a signal indicating sleep from a communication device; the processing unit 1602 is configured to start or restart a sleep timer and sleep while the sleep timer is running; wherein, during the sleep Sleeping during the timer operation includes: not monitoring the physical downlink control channel PDCCH during the sleep timer operation.
  • the processing unit 1602 sleeping during the running of the sleep timer further includes:
  • the receiving unit 1601 receives a signal indicating sleep from the communication device, and is specifically configured to: receive a sleep signal from the communication device; or receive an instruction from the communication device Signal, the indication signal includes sleep indication information.
  • the receiving unit 1601 is further configured to receive a sleep duration configured by the communication device before receiving a signal indicating sleep from the communication device.
  • the signal includes indication information, where the indication information indicates a sleep duration.
  • the receiving unit 1601 before receiving the sleep instruction signal from the communication device, the receiving unit 1601 is further configured to receive at least one duration configured by the communication device, where the sleep duration is the One of at least one duration.
  • the processing unit 1602 before starting or restarting the sleep timer, is further configured to configure a timing duration of the sleep timer to be the sleep duration.
  • the terminal device After receiving a signal indicating sleep from a communication device, starting or restarting a sleep timer and sleeping during the running of the sleep timer; wherein the terminal device sleeping during the running of the sleep timer includes : The terminal device does not listen to the PDCCH during the running of the sleep timer.
  • the terminal device shown in FIG. 16 may also be used to perform the operations of the terminal device in the embodiments shown in FIG. 10, FIG. 11, and FIG. 12.
  • the receiving unit 1601 is configured to receive a signal; the processing unit 1602 is configured to, if the receiving unit 1601 receives a signal indicating sleep, if the activity timer InactivityTimer is running, the terminal device stops the InactivityTimer; or If the retransmission timer RetransmissionTimer is running, the terminal device stops the RetransmissionTimer; or if the InactivityTimer and the RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer.
  • the terminal device is configured to receive DRX discontinuously.
  • the receiving unit 1601 receives a signal indicating sleep, and is specifically configured to: receive a sleep signal; or receive an instruction signal, where the instruction signal includes sleep instruction information.
  • the processing unit 1602 stops the InactivityTimer, and is specifically configured to stop the InactivityTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processing unit 1602 stops the RetransmissionTimer, and is specifically configured to stop the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processing unit 1602 is further configured to: reset the InactivityTimer if the InactivityTimer is running; or reset the RetransmissionTimer if the RetransmissionTimer is running; or if the InactivityTimer and the RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is one or more of an uplink retransmission timer RetransmissionTimerUL and a downlink retransmission timer RetransmissionTimerDL.
  • processing unit 1602 is further configured to stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processing unit 1602 is further configured to stop the InactivityTimer and use a long DRX cycle.
  • the processing unit 1602 is further configured to stop the ShortCycleTimer if the ShortCycleTimer is running, or stop and reset the ShortCycleTimer.
  • the terminal device Based on the above terminal device, if the terminal device receives a signal indicating sleep, if the InactivityTimer and / or RetransmissionTimer are running, the terminal device stops the InactivityTimer and / or the RetransmissionTimer. In the prior art, if InactivityTimer and / or RetransmissionTimer are running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer ends. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device shown in FIG. 16 may be further configured to perform operations of the terminal device in the embodiments shown in FIG. 13, FIG. 14, and FIG. 15.
  • the receiving unit 1601 is configured to receive an instruction message, where the instruction message is used to instruct the terminal device to stop a specific timer, wherein the terminal device is configured to discontinuously receive DRX;
  • the processing unit 1602 is configured to stop the onDurationTimer if the continuous timer onDurationTimer is running; or stop the InactivityTimer if the activity timer InactivityTimer is running; or stop if the onDurationTimer and the InactivityTimer are running The onDurationTimer and the InactivityTimer.
  • the processing unit 1602 is further configured to: if the onDurationTimer is running, reset the onDurationTimer; or, if the InactivityTimer is running, reset the InactivityTimer.
  • the processing unit 1602 is further configured to stop the RetransmissionTimer if a retransmission timer RetransmissionTimer is running, where the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL and a downlink retransmission timing. Or RetransmissionTimerDL.
  • the processing unit 1602 is further configured to: if the RetransmissionTimer is running, reset the RetransmissionTimer.
  • the indication message is a physical layer sequence, or a DCI, or a MAC CE, or a MAC PDU.
  • the receiving unit 1601 receives an instruction message, and is specifically configured to receive the instruction message when the processing unit 1602 uses a long DRX cycle.
  • the processing unit 1602 is further configured to continue to use the long DRX cycle.
  • the receiving unit 1601 receives an indication message, and is specifically configured to receive the indication message when the processing unit 1602 uses a short DRX cycle.
  • the processing unit 1602 is further configured to continue to use the short DRX cycle.
  • processing unit 1602 is further configured not to start or restart the short cycle timer ShortCycleTimer.
  • an instruction message is received. If onDurationTimer and / or InactivityTimer are running, the terminal device stops the onDurationTimer and / or InactivityTimer. It can make the network device stop onDurationTimer and / or InactivityTimer in time when it is determined that the terminal device has no subsequent data transmission, so that the terminal device enters hibernation and does not need to remain awake to receive messages. That is to say, through the above method, the terminal device can be hibernated in time, so that power consumption can be better saved, and the demand for power saving can be met.
  • the division of the units in the embodiments of the present application is schematic, and is only a logical function division. There may be another division manner in actual implementation.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the integrated unit When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium.
  • a computer device which may be a personal computer, a server, or a network device
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .
  • the terminal device may include a transceiver 1701 and a processor 1702, and optionally may also include a memory 1703.
  • the terminal device may include at least one processor and at least one memory, and only one processor and one memory are exemplarily shown in FIG. 17.
  • the processor 1702 may be a central processing unit (CPU), a network processor (NP), a combination of a CPU and an NP, and so on.
  • the processor 1702 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field-programmable gate array
  • GAL general array logic
  • the transceiver 1701 and the processor 1702 are connected to each other.
  • the transceiver 1701 and the processor 1702 are connected to each other through a bus 1704;
  • the bus 1704 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. .
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 17, but it does not mean that there is only one bus or one type of bus.
  • the terminal device shown in FIG. 17 may be used to perform the operations of the terminal device in the embodiments shown in FIG. 3, FIG. 7, and FIG. 8.
  • the transceiver 1701 is configured to transmit and receive signals when receiving a call from the processor 1702; and the processor 1702 is configured to activate if the transceiver 1701 does not receive a signal indicating wake-up within a preset time, Stop the InactivityTimer when the timer InactivityTimer is running; or stop the RetransmissionTimer if the retransmission timer RetransmissionTimer is running; or stop the InactivityTimer and the RetransmissionTimer if the InactivityTimer and the RetransmissionTimer are running.
  • the terminal device is configured to receive DRX discontinuously.
  • the transceiver 1701 does not receive a signal indicating wakeup within a preset time, and is specifically configured to: receive a sleep signal within a preset time; or do not receive a signal within a preset time A wake-up signal is received; or an instruction signal is received within a preset time, and the instruction signal includes sleep instruction information.
  • the processor 1702 stops the InactivityTimer, and is specifically configured to stop the InactivityTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processor 1702 stops the RetransmissionTimer, and is specifically configured to stop the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processor 1702 is further configured to: reset the InactivityTimer if the InactivityTimer is running; or reset the RetransmissionTimer if the RetransmissionTimer is running; or if the InactivityTimer and the RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is one or more of an uplink retransmission timer RetransmissionTimerUL and a downlink retransmission timer RetransmissionTimerDL.
  • the processor 1702 is further configured to stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processor 1702 is further configured to stop the InactivityTimer and use a long DRX cycle.
  • the processor 1702 is further configured to stop the ShortCycleTimer if the short cycle timer ShortCycleTimer is running, or stop and reset the ShortCycleTimer.
  • the memory 1703 is coupled to the processor 1702 and is configured to store a program and the like.
  • the program may include program code, where the program code includes a computer operation instruction.
  • the memory 1703 may include a RAM, and may also include a non-volatile memory (non-volatile memory), for example, at least one disk memory.
  • the processor 1702 executes an application program stored in the memory 1703 to implement the foregoing functions, thereby implementing the sleeping method of the terminal device shown in FIG. 3, FIG. 7, and FIG.
  • the terminal device Based on the terminal device, if the terminal device does not receive a signal indicating wake-up within a preset time, if the InactivityTimer and / or RetransmissionTimer are running, the terminal device stops the InactivityTimer and / or the RetransmissionTimer. In the prior art, if InactivityTimer and / or RetransmissionTimer are running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer ends. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device shown in FIG. 17 may also be used to perform the operations of the terminal device in the embodiment shown in FIG. 9.
  • the transceiver 1701 is configured to receive a signal indicating sleep from a communication device when receiving a call from the processor 1702; the processor 1702 is configured to start or restart a sleep timer, and Sleeping during operation; wherein sleeping during operation of the sleep timer includes: not monitoring PDCCH during operation of the sleep timer.
  • the processor 1702 sleeping during the running of the sleep timer further includes:
  • the transceiver 1701 receives a signal indicating sleep from the communication device, and is specifically configured to: receive a sleep signal from the communication device; or receive an instruction from the communication device Signal, the indication signal includes sleep indication information.
  • the transceiver 1701 before receiving the sleep instruction signal from the communication device, is further configured to receive a sleep duration configured by the communication device.
  • the signal includes indication information, where the indication information indicates a sleep duration.
  • the transceiver 1701 before receiving the signal indicating sleep from the communication device, is further configured to receive at least one duration configured by the communication device, where the sleep duration is the One of at least one duration.
  • the processor 1702 before starting or restarting the sleep timer, is further configured to configure a timing duration of the sleep timer to be the sleep duration.
  • the memory 1703 is coupled to the processor 1702 and is configured to store a program and the like.
  • the program may include program code, where the program code includes a computer operation instruction.
  • the memory 1703 may include a RAM, and may also include a non-volatile memory (non-volatile memory), for example, at least one disk memory.
  • the processor 1702 executes an application program stored in the memory 1703 to implement the foregoing functions, thereby implementing a sleep method of the terminal device as shown in FIG. 9.
  • the terminal device After receiving a signal indicating sleep from a communication device, starting or restarting a sleep timer and sleeping during the running of the sleep timer; wherein the terminal device sleeping during the running of the sleep timer includes : The terminal device does not listen to the PDCCH during the running of the sleep timer.
  • the terminal device shown in FIG. 17 may be further configured to perform operations of the terminal device in the embodiments shown in FIG. 10, FIG. 11, and FIG. 12.
  • the transceiver 1701 is configured to receive a signal when receiving a call from the processor 1702; the processor 1702 is configured to, if the transceiver 1701 receives a signal indicating sleep, if the activity timer InactivityTimer is running The terminal device stops the InactivityTimer; or, if a retransmission timer RetransmissionTimer is running, the terminal device stops the RetransmissionTimer; or, if the InactivityTimer and the RetransmissionTimer are running, the terminal device stops the InactivityTimer and the RetransmissionTimer. Wherein, the terminal device is configured to receive DRX discontinuously.
  • the transceiver 1701 receives a signal indicating sleep, and is specifically configured to: receive a sleep signal; or receive an instruction signal, where the instruction signal includes sleep instruction information.
  • the processor 1702 stops the InactivityTimer, and is specifically configured to stop the InactivityTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processor 1702 stops the RetransmissionTimer, and is specifically configured to stop the RetransmissionTimer at the beginning of the next DRX cycle of the (current) DRX cycle.
  • the processor 1702 is further configured to: reset the InactivityTimer if the InactivityTimer is running; or reset the RetransmissionTimer if the RetransmissionTimer is running; or if the InactivityTimer and the RetransmissionTimer are running, reset the InactivityTimer and the RetransmissionTimer.
  • the RetransmissionTimer is one or more of an uplink retransmission timer RetransmissionTimerUL and a downlink retransmission timer RetransmissionTimerDL.
  • the processor 1702 is further configured to stop the InactivityTimer, and start or restart the short cycle timer ShortCycleTimer.
  • the processor 1702 is further configured to stop the InactivityTimer and use a long DRX cycle.
  • the processor 1702 is further configured to stop the ShortCycleTimer if the ShortCycleTimer is running, or stop and reset the ShortCycleTimer.
  • the memory 1703 is coupled to the processor 1702 and is configured to store a program and the like.
  • the program may include program code, where the program code includes a computer operation instruction.
  • the memory 1703 may include a RAM, and may also include a non-volatile memory (non-volatile memory), for example, at least one disk memory.
  • the processor 1702 executes an application program stored in the memory 1703 to implement the foregoing functions, thereby implementing the sleeping method of the terminal device shown in FIG. 10, FIG. 11, and FIG. 12.
  • the terminal device Based on the above terminal device, if the terminal device receives a signal indicating sleep, if the InactivityTimer and / or RetransmissionTimer are running, the terminal device stops the InactivityTimer and / or the RetransmissionTimer. In the prior art, if InactivityTimer and / or RetransmissionTimer are running, even when the terminal device is instructed to sleep, the terminal device needs to remain activated for a period of time until the timer ends. That is to say, the terminal device can be truly dormant through the above method, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device shown in FIG. 17 may also be used to perform the operations of the terminal device in the embodiments shown in FIG. 13, FIG. 14, and FIG. 15.
  • the transceiver 1701 is configured to receive an instruction message when receiving a call from the processor 1702, and the instruction message is used to instruct the terminal device to stop a specific timer, wherein the terminal device is configured for discontinuous reception.
  • DRX discontinuous reception
  • the processor 1702 is configured to stop the onDurationTimer if the continuous timer onDurationTimer is running; or stop the InactivityTimer if the activity timer InactivityTimer is running; or stop if the onDurationTimer and the InactivityTimer are running The onDurationTimer and the InactivityTimer.
  • the processor 1702 is further configured to: if the onDurationTimer is running, reset the onDurationTimer; or, if the InactivityTimer is running, reset the InactivityTimer.
  • the processor 1702 is further configured to stop the RetransmissionTimer if a retransmission timer RetransmissionTimer is running, where the RetransmissionTimer is an uplink retransmission timer RetransmissionTimerUL and a downlink retransmission timing. Or RetransmissionTimerDL.
  • the processor 1702 is further configured to: if the RetransmissionTimer is running, reset the RetransmissionTimer.
  • the indication message is a physical layer sequence, or a DCI, or a MAC CE, or a MAC PDU.
  • the transceiver 1701 receives an instruction message, and is specifically configured to receive, by the processor 1702, the instruction message when a long DRX cycle is used.
  • the processor 1702 is further configured to continue to use the long DRX cycle.
  • the transceiver 1701 receives an instruction message, and is specifically configured to receive, by the processor 1702, the instruction message when a short DRX cycle is used.
  • the processor 1702 is further configured to continue to use the short DRX cycle.
  • the processor 1702 is further configured to not start or restart the short cycle timer ShortCycleTimer.
  • the memory 1703 is coupled to the processor 1702 and is configured to store a program and the like.
  • the program may include program code, where the program code includes a computer operation instruction.
  • the memory 1703 may include a RAM, and may also include a non-volatile memory (non-volatile memory), for example, at least one disk memory.
  • the processor 1702 executes an application program stored in the memory 1703 to implement the foregoing functions, thereby implementing the sleeping method of the terminal device shown in FIG. 13, FIG. 14, and FIG. 15.
  • an instruction message is received. If onDurationTimer and / or InactivityTimer are running, the terminal device stops the onDurationTimer and / or InactivityTimer. It can make the network device stop onDurationTimer and / or InactivityTimer in time when it is determined that the terminal device has no subsequent data transmission, so that the terminal device enters hibernation and does not need to remain awake to receive messages. That is to say, through the above method, the terminal device can be hibernated in time, so that power consumption can be better saved, and the demand for power saving can be met.
  • an embodiment of the present application further provides a method for indicating a status of a terminal device, which is applicable to the communication system shown in FIG. 2.
  • the specific process of the method includes:
  • Step 1801 The terminal device receives a first message from the communication device, where the first message indicates time information for the terminal device to wake up or sleep.
  • the communication device may be a network device, such as a base station, or may be another device, such as a terminal device.
  • the first message itself may instruct the terminal device to wake up or sleep, and the first message is associated with the time information, so that the first message may be used to indicate the Time information for the terminal device to wake up or sleep.
  • the communication device may configure the time information associated with the first message to the terminal device through a broadcast message or an RRC dedicated message or other message, or the time information associated with the first message may also be It is set in advance and stored in the terminal device.
  • the first message may be a wake-up signal, and then the first message may instruct the terminal device to wake up.
  • the first message May indicate time information for the terminal device to wake up; for another example, the first message may be a go-to-sleep signal, the first message may indicate the terminal device to sleep, combined with the first The time information associated with a message, and the first message may indicate time information of the terminal device sleeping.
  • the first message may include first indication information, and the first indication information indicates the time information.
  • the first message itself may instruct the terminal device to wake up or sleep, and the first indication information included in the first message is used to indicate the time information, in combination with the first message A property of the terminal and the first indication information in the first message, and the first message may indicate time information for the terminal device to wake up or sleep. For example, if the first message is a wake-up signal, the first message may instruct the terminal device to wake up.
  • the first message may indicate The wake-up time information of the terminal device; for another example, if the first message is a go-to-sleep signal, the first message may instruct the terminal device to sleep, in combination with the first message First indication information, where the first message may indicate time information of the terminal device sleeping.
  • the first message may include second indication information, and the second indication information indicates that the terminal device wakes up or sleeps.
  • the first message itself may be associated with the time information, for example, the communication device configures the time information associated with the first message to the terminal through a broadcast message or an RRC dedicated message or other message. The device or the time information associated with the first message may be set in advance and stored in the terminal device.
  • the second indication information in the first message indicates that the terminal device wakes up, and in combination with the time information associated with the first message, the first message may indicate time information that the terminal device wakes up ;
  • the second indication information in the first message indicates that the terminal device is dormant, and in combination with the time information associated with the first message, the first message may indicate that the terminal device is dormant Time information.
  • the first message may include first indication information and second indication information, the first indication information indicates the time information, and the second indication information indicates the terminal The device wakes up or sleeps. In this implementation manner, the first message itself cannot instruct the terminal device to wake up or hibernate. Combining the second indication information and the first indication information in the first message, the first message can indicate Time information of the terminal device waking up or sleeping.
  • the second indication information in the first message indicates that the terminal device wakes up, and in combination with the first indication information in the first message, the first message may indicate that the terminal device wakes up Time information; for another example, the second indication information in the first message instructs the terminal device to sleep, and in combination with the first indication information in the first message, the first message may indicate the Information about the terminal device sleep time.
  • the time information may be a length of time that the terminal device wakes up or sleeps. It can be understood as: the length of time during which the terminal device maintains wake-up or sleep when receiving the first message (or after). For example, from the time when the terminal device receives the first message (or after) to the end of the wake-up time, the terminal device is awake; for example, the terminal device receives all the information from the terminal device. When the first message is generated (or after), and the time period until the end of the sleep period ends, the terminal device is in the sleep state.
  • the time point at which the terminal device starts to wake up or sleep based on the first message may be the moment when the first message is received (or after), or it may be another predetermined time Point, the length of time that the terminal device wakes up or sleeps can be calculated from the time point when the wakeup or sleep starts, which is not limited in this application.
  • the time information may be a length of time before the terminal device wakes up or sleeps. It can be understood that the length of time from when (or after) the terminal device receives the first message to when it wakes up or sleeps, that is, when the terminal device (or after) receives the first message, it does not wake up immediately. Or sleep, but only wake up or sleep after a period of time (ie, the length of time).
  • the time information may be a time when the terminal device wakes up or ends hibernation. It can be understood that: when the terminal device receives (or after) the first message, the time point at which the wake-up or hibernation ends. For example, when the first message is received (or after) from the terminal device, wake-up is started, and the time from the wake-up to the end of wake-up is maintained, or when the first message is received (or after) from the terminal device Time to start hibernation and maintain hibernation until the end of hibernation.
  • the time when the terminal device starts to wake up or sleep based on the first message may be immediately when (or after) the first message is received, or may be another predetermined time point, so The length of time that the terminal device wakes up or sleeps can be calculated from the time point when the wake up or sleep is started, which is not limited in this application.
  • the time length involved in the above may be one or more milliseconds; or the time length may be one or more subframes; or the time length may be one or more Time slots; or the time length may be one or more DRX cycles; or the time length may be one or more OnDuration; or the time length may be one or more paging opportunities; or The time length may be one or more PDCCH monitoring opportunities; or the time length may be a time length in milliseconds; or the time length may be a time length in subframes; or, The time length may be a time length in units of time slots; or the time length may be a time length in units of DRX cycles; or the time length may be a time length in units of OnDuration ; Or, the time length may be a time length in units of a paging opportunity; or, the time length may be a PDCCH monitoring opportunity as The unit of time.
  • the time length is one or more of "something”
  • the time length is a time length in the unit of "something”
  • the two may be considered equivalent in a certain scenario.
  • “So and so” are the milliseconds mentioned above and so on.
  • the time length may be N (N is an integer greater than or equal to 1) OnDuration, which means from the beginning The wake-up or sleep time starts, and the terminal device wakes up or sleeps in the subsequent N OnDurations.
  • the first indication information indicating the time information may specifically be a value of the first indication information indicating the time information.
  • the first indication information indicates a value of a length of time that the terminal device wakes up or sleeps (such as N milliseconds, N Durations, etc., where N is an integer greater than or equal to 1).
  • the first indication information indicates a value of a length of time (such as N milliseconds, N Durations, etc.) before the terminal device wakes up or sleeps.
  • the first indication information indicates a value at a time point when the terminal device wakes up or ends hibernation.
  • the first indication information indicating the time information may specifically indicate an index value for the first indication information, and the index value corresponds to a value of the time information.
  • the index value corresponds to a value of a length of time (such as N milliseconds, N Duration, etc.) of the terminal device, or the index value corresponds to a value of a length of time before the terminal device wakes up or sleeps (such as N milliseconds, N Durations, etc.); or the index value corresponds to a value at a time point when the terminal device wakes up or ends sleep.
  • the correspondence between the index value and the time information value may be pre-configured by the communication device to the terminal device.
  • the communication device may be configured to the terminal device through a broadcast message, an RRC dedicated message, or other messages, or the correspondence between the index value and the time information value may be set in advance and stored in the terminal device.
  • the index values ⁇ 1,2,3 ⁇ correspond to the time information values ⁇ a, b, c ⁇ , respectively.
  • the first indication information indicates an index value of 1, the first indication information is considered to indicate the time information. Is a.
  • the first message may be a MAC PDU, or the first message may be a MAC CE (where the MAC CE is a part of the MAC PDU).
  • the following multiple implementation manners of the first message may be included:
  • the first message when the first message is a MAC CE, it can be known through the logical channel identifier (LCID) in the MAC subheader of the media access control subheader that the corresponding MAC CE is the first MAC.
  • LCID logical channel identifier
  • the LCID may be a newly introduced LCID, or an existing LCID may be reused, which is not limited in this application.
  • the format of the MAC subheader can be shown in FIG. 19.
  • the first indication information may be carried in a MAC subheader of the MAC PDU, or the first indication information may be carried in a MAC CE of the MAC PDU.
  • the first message is a MAC CE
  • the LCID may be a newly introduced LCID or a duplicated LCID.
  • the first indication information may occupy 2 bits in the MAC subheader, as shown in FIG. 20.
  • the first indication information when the first indication information is carried in the MAC CE of the MAC PDU, the first indication information may occupy 4 bits in the MAC CE, as shown in FIG. 21. It should be noted that the first indication information specifically occupies several bits. This application is not limited. In order to ensure that the length of the MAC CE is in bytes (eight bits), the remaining bits may be reserved bits or padding. Bits, or other information bits.
  • the second indication information may be carried in a MAC subheader of the MAC PDU, or the second indication information may be carried in a MAC CE of the MAC PDU.
  • the first message is a MAC CE
  • the LCID may be a newly introduced LCID or a duplicated LCID.
  • the second indication information may occupy 1 bit in the MAC subheader, as shown in FIG. 22.
  • the second indication information when the second indication information is carried in the MAC CE of the MAC PDU, for example, the second indication information may occupy 1 bit in the MAC CE, as shown in FIG. 23. It should be noted that the second indication information specifically occupies several bits. This application is not limited. In order to ensure that the length of the MAC CE is in bytes (eight bits), the remaining bits may be reserved bits or padding. Bits, or other information bits.
  • the first indication information when the first message includes the first indication information and the second indication information: the first indication information may be carried in a MAC subheader of the MAC PDU Or, the first indication information may be carried in the MAC CE of the MAC PDU; the second indication information may be carried in the MAC subheader of the MAC PDU, or the second indication information may be carried In the MAC CE of the MAC PDU. That is to say, the manner in which the first indication information and the second indication information carry positions may be combined in pairs. For the locations specifically carried in the first indication information or the second indication information, reference may be made to the foregoing implementation manner. Method.
  • the first message when the first message is a MAC CE, it can be known from the LCID in the MAC subheader of the media access control subheader that the corresponding MAC is the first message.
  • the LCID may be a newly introduced LCID or may be reused. Existing LCID.
  • the first indication information when both the first indication information and the second indication information are carried in the MAC CE of the MAC PDU, the first indication information may occupy 3 bits in the MAC CE, and the second indication information may Occupies 1 bit in the MAC CE, as shown in FIG.
  • the first indication information is carried in the MAC CE of the MAC PDU
  • the second indication information is carried in the MAC subheader of the MAC PDU
  • the first indication information may occupy 3 bits in the MAC CE
  • the second indication information may occupy 1 bit in the MAC subheader, as shown in FIG. 25, where (a) in FIG. 25 is the first indication information
  • the schematic carried in the MAC CE, and (b) is a schematic carried in the second indication information in the MAC subheader.
  • the first indication information and the second indication information specifically occupy several bits. This application is not limited. In order to ensure that the length of the MAC CE is in bytes (eight bits), the remaining bits can be For reserved bits, or padding bits, or other information bits.
  • the first message may be RRC signaling, such as a broadcast message or an RRC dedicated message.
  • the first message may be DCI, and the first message may be carried on a PDCCH.
  • Step 1802 If the first message indicates time information for the terminal device to wake up, the terminal device wakes up based on the time information; or, if the first message indicates time information for the terminal device to sleep, then The terminal device sleeps based on the time information.
  • the wake-up of the terminal device can be understood as that the terminal device needs to monitor the PDCCH, and the sleeping of the terminal device can be understood as that the terminal device does not need to monitor the PDCCH. It should be noted that this application does not limit the state before the terminal device wakes up or sleeps. For example, when the terminal device is being woken up, if the first message indicates time information of the terminal device waking up, the The terminal device continues to wake up, and if the first message indicates time information for the terminal device to sleep, the terminal device changes from wake up to sleep.
  • the terminal device when the terminal device is in hibernation, if the first message indicates time information for the terminal device to wake up, the terminal device changes from hibernation to wake up, and if the first message indicates the terminal device The sleep time information, the terminal device continues to sleep.
  • the terminal device wakes up based on the time information may be understood as: the terminal device wakes up and maintains wake up
  • the time is the length of time that the terminal device wakes up corresponding to the time information;
  • the terminal device sleeping based on the time information can be understood as: the time during which the terminal device sleeps and maintains sleep is the corresponding time corresponding to the time information Describes the length of time the terminal device sleeps. Specifically, for the time when the terminal device starts to wake up or sleep, refer to the related description involved in step 1801 above, and details are not repeated here.
  • the terminal device wakes up based on the time information may also be understood as: the terminal device wakes up And wake up after the length of time the terminal device corresponding to the time information wakes up; the terminal device sleeping based on the time information can also be understood as: the terminal device sleeping and the terminal device corresponding to the time information sleeping Hibernation starts after a length of time.
  • the terminal device wakes up based on the time information can be understood as: the terminal device wakes up and maintains wake up Time ends when the terminal device corresponding to the time information wakes up; the terminal device sleeping based on the time information can be understood as: the time when the terminal device sleeps and maintains sleep until the terminal device corresponding to the time information sleeps At the end of time.
  • the terminal device sleeping based on the time information can be understood as: the time when the terminal device sleeps and maintains sleep until the terminal device corresponding to the time information sleeps At the end of time.
  • the time when the terminal device starts to wake up or sleep refer to the related description involved in step 1801 above, and details are not repeated here.
  • the terminal device when the first message is DCI, after the terminal device receives the first message from the communication device, the terminal device does not start or restart activities.
  • Timer InactivityTimer when a terminal device receives a DCI (PDCCH) indicating a new transmission, the terminal device needs to start or restart the InactivityTimer in order to receive subsequent scheduled data.
  • the terminal device because the first Messages are not directly related to data scheduling, so the terminal device does not need to start or restart InactivityTimer.
  • the first message in addition to the event information that can indicate that the terminal device wakes up or sleeps, can also have other indication functions.
  • the first message may also indicate a new transmission.
  • the terminal device receives the first message from the communication device, the terminal device does not Start or not restart InactivityTimer.
  • the terminal device stopping the activity timer may be: the terminal device stops the InactivityTimer when (or after) receiving the first message; or, the terminal device is in the (current) DRX Stop the InactivityTimer at the beginning of the next DRX cycle of the cycle.
  • the (current) DXR cycle is a DRX cycle in which the time when the first message is received, and the start of the next DRX cycle refers to an OnDuration start position of the next DRX cycle. .
  • resetting the activity timer by the terminal device may be: the terminal device sets a value of the InactivityTimer to an initial value (for example, 0). In this way, when the InactivityTimer needs to be turned on next time, the InactivityTimer can be timed from 0 to avoid affecting the normal process.
  • the terminal device stopping the onDurationTimer may specifically be: the terminal device stops the onDurationTimer when (or after) receiving the first message; or, the terminal device is in the (current) DRX The onDurationTimer is stopped at the beginning of the next DRX cycle of the cycle.
  • resetting the onDurationTimer by the terminal device may specifically be that the terminal device sets a value of the onDurationTimer to an initial value (for example, 0). In this way, when the onDurationTimer needs to be turned on next time, the onDurationTimer can be timed from 0 to avoid affecting the normal process.
  • the terminal device stops the retransmission timer, or, The terminal device stops and resets the retransmission timer.
  • the RetransmissionTimer may be one or more of an uplink retransmission timer (RetransmissionTimer (uplink, UL)) and a downlink retransmission timer (RetransmissionTimer (downlink, DL)).
  • the RetransmissionTimer UL may also be recorded as drx-RetransmissionTimer UL; the RetransmissionTimer DL may also be recorded as drx-RetransmissionTimer DL; in the embodiment of the present application, only the RetransmissionTimer UL and RetransmissionTimer DL are used as examples for description. It should be understood that the RetransmissionTimer UL may be replaced by drx-RetransmissionTimer UL; the RetransmissionTimer DL may be replaced by drx-RetransmissionTimer DL.
  • the terminal device stops the RetransmissionTimer, which can be specifically divided into three cases: For details, see the implementation shown in FIG. Cases b1, b2, and b3 are involved in the example, and overlaps are not repeated here.
  • the terminal device stopping the RetransmissionTimer may specifically be: the terminal device stops the RetransmissionTimer when (or after) receiving the first message; or, the terminal device is in the (current) DRX The RetransmissionTimer is stopped at the beginning of the next DRX cycle of the cycle.
  • resetting the RetransmissionTimer by the terminal device may specifically be that the terminal device sets a value of the RetransmissionTimer to an initial value (for example, 0). In this way, when the RetransmissionTimer needs to be turned on next time, the RetransmissionTimer can be timed from 0 to avoid affecting the normal process.
  • the terminal device receives a first message from the communication device, and the first message indicates time information of the terminal device to wake up or sleep; if the first message indicates If the terminal device wakes up the time information, the terminal device wakes up based on the time information; or if the first message indicates the terminal device sleep time information, the terminal device sleeps based on the time information.
  • the terminal device can flexibly wake up or sleep according to the first message.
  • the terminal device can be flexibly hibernated relative to the existing technology, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device shown in FIG. 16 may be used to perform the operations of the terminal device in the embodiment shown in FIG. 18 described above.
  • the receiving unit 1601 is configured to receive a first message from a communication device, where the first message indicates time information for the terminal device to wake up or sleep; the processing unit 1602 is configured to, if the first message indicates the terminal Wake-up time information of the device wakes up based on the time information; or, if the first message indicates time information of the terminal device sleeping, sleep based on the time information.
  • the first indication information indicates the time information.
  • the first message includes second indication information, and the second indication information indicates that the terminal device wakes up or sleeps.
  • the time information is a length of time when the terminal device wakes up or sleeps; or, the time information is a length of time before the terminal device wakes up or sleeps; or, the time The information is the time when the terminal device wakes up or ends hibernation.
  • the time length is: one or more milliseconds; or, one or more subframes; or, one or more time slots; or, one or more discontinuous reception DRX cycles ; Or, one or more OnDuration; or, one or more paging opportunities; or, one or more physical downlink control channel PDCCH monitoring opportunities; or, the length of time in milliseconds; or, the unit of subframes
  • the length of time in units of time slots; or the length of time in units of discontinuous reception DRX cycles; or the length of time in units of OnDuration; or the length of time in units of paging opportunities The length of time; or the length of time in units of physical downlink control channel PDCCH monitoring opportunities.
  • the first message is a MAC PDU or RRC signaling.
  • the first indication information is carried in a media interface of the MAC PDU.
  • the control sub-header or the first indication information is carried in a MAC CE of the MAC PDU.
  • the second indication information is carried in a media interface of the MAC PDU.
  • the second indication information is carried in a MAC CE of the MAC PDU.
  • the first indication information and all The second indication information may be carried in the following manner: both the first indication information and the second indication information are carried in a media access control subheader of the MAC PDU; or, the first indication information and the The second indication information is all carried in the MAC CE of the MAC PDU; or the first indication information is carried in the media access control subheader of the MAC PDU, and the second indication information is carried in all The MAC CE of the MAC PDU; or the second indication information is carried in a media access control subheader of the MAC PDU, and the first indication information is carried in a MAC CE of the MAC PDU.
  • the first message may be DCI.
  • the processing unit 1602 is further configured to not start or restart an activity timer.
  • the processing unit 1602 is further configured to stop the activity timer, or, The processing unit 1602 is further configured to stop and reset the activity timer.
  • the processing unit 1602 is further configured to stop the continuous timer, or The processing unit 1602 is further configured to stop and reset the duration timer.
  • the processing unit 1602 is further configured to stop the retransmission timer, Alternatively, the processing unit 1602 is further configured to stop and reset the retransmission timer.
  • the terminal device Based on the above terminal device, receiving a first message from a communication device, the first message indicating time information for the terminal device to wake up or sleep; if the first message indicates time information for the terminal device to wake up, the The terminal device wakes up based on the time information; or if the first message indicates time information that the terminal device sleeps, the terminal device sleeps based on the time information.
  • the terminal device can flexibly wake up or sleep according to the first message.
  • the terminal device can be flexibly hibernated relative to the existing technology, so that power consumption can be better saved and the demand for power saving can be met.
  • the terminal device shown in FIG. 17 may also be used to perform operations of the terminal device in the embodiment shown in FIG. 18, for example:
  • the present application further provides a terminal device, which includes a transceiver 1701, at least one memory, and at least one processor 1702, where:
  • the transceiver 1701 is configured to send and receive signals or messages when receiving a call from the processor 1702; the processor 1702 is configured to control the transceiver 1701 to receive a first message from a communication device, the first message Time information indicating the terminal device to wake up or sleep; if the first message indicates time information to wake up the terminal device, wake up based on the time information; or if the first message indicates the terminal device to sleep Time information, sleep based on the time information.
  • the first indication information indicates the time information.
  • the first message includes second indication information, and the second indication information indicates that the terminal device wakes up or sleeps.
  • the time information is a length of time when the terminal device wakes up or sleeps; or, the time information is a length of time before the terminal device wakes up or sleeps; or, the time The information is the time when the terminal device wakes up or ends hibernation.
  • the time length is: one or more milliseconds; or, one or more subframes; or, one or more time slots; or, one or more discontinuous reception DRX cycles ; Or, one or more OnDuration; or, one or more paging opportunities; or, one or more physical downlink control channel PDCCH monitoring opportunities; or, the length of time in milliseconds; or, the unit of subframes
  • the length of time in units of time slots; or the length of time in units of discontinuous reception DRX cycles; or the length of time in units of OnDuration; or the length of time in units of paging opportunities The length of time; or the length of time in units of physical downlink control channel PDCCH monitoring opportunities.
  • the first message is a MAC PDU or RRC signaling.
  • the first indication information is carried in a media interface of the MAC PDU.
  • the control sub-header or the first indication information is carried in a MAC CE of the MAC PDU.
  • the second indication information is carried in a media interface of the MAC PDU.
  • the second indication information is carried in a MAC CE of the MAC PDU.
  • the first indication information and all The second indication information may be carried in the following manner: both the first indication information and the second indication information are carried in a media access control subheader of the MAC PDU; or, the first indication information and the The second indication information is all carried in the MAC CE of the MAC PDU; or the first indication information is carried in the media access control subheader of the MAC PDU, and the second indication information is carried in all The MAC CE of the MAC PDU; or the second indication information is carried in a media access control subheader of the MAC PDU, and the first indication information is carried in a MAC CE of the MAC PDU.
  • the first message is DCI.
  • the processor 1702 when the first message is a DCI, the processor 1702 is further configured to not start or restart an activity timer.
  • the processor 1702 is further configured to stop the activity timer, or The processor 1702 is further configured to stop and reset the activity timer.
  • the processor 1702 is further configured to stop the continuous timer, or The processor 1702 is further configured to stop and reset the duration timer.
  • the processor 1702 is further configured to stop the retransmission timer, Alternatively, the processor 1702 is further configured to stop and reset the retransmission timer.
  • the memory 1703 is coupled to the processor 1702 and is configured to store a program and the like.
  • the program may include program code, where the program code includes a computer operation instruction.
  • the memory 1703 may include a RAM, and may also include a non-volatile memory (non-volatile memory), for example, at least one disk memory.
  • the processor 1702 executes an application program stored in the memory 1703 to implement the functions described above, thereby implementing a status indication method of the terminal device as shown in FIG. 18.
  • the terminal device Based on the above terminal device, receiving a first message from a communication device, the first message indicating time information for the terminal device to wake up or sleep; if the first message indicates time information for the terminal device to wake up, the The terminal device wakes up based on the time information; or if the first message indicates time information that the terminal device sleeps, the terminal device sleeps based on the time information.
  • the terminal device can flexibly wake up or sleep according to the first message.
  • the terminal device can be flexibly hibernated relative to the existing technology, so that power consumption can be better saved and the demand for power saving can be met.
  • this application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions
  • the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.

Abstract

一种终端设备的休眠方法及装置,用以实现满足节省功耗的需求。在该方法中,若终端设备在预设时间内未接收到指示唤醒的信号,若InactivityTimer和/或RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和/或所述RetransmissionTimer。可以避免现有技术中若InactivityTimer和/或RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,满足节省功耗的需求。

Description

一种终端设备的休眠方法及装置 技术领域
本申请涉及通信技术领域,尤其涉及一种终端设备的休眠方法及装置。
背景技术
第五代(5generation,5G)新空口(new radio,NR)技术沿用了长期演进技术(long term evolution,LTE)中的非连续接收(discontinuous reception,DRX)机制。基站为处于无线资源控制(radio resource control,RRC)连接态的终端设备(也称用户设备(User Equipment,UE))配置的一个DRX周期,其中DRX周期可以为长的DRX周期,还可以为短的DRX周期,其中长的DRX周期是默认必须配置、而短的DRX周期是可选配置,若配置了短的DRX周期,UE会在使用短的DRX周期的时候开启短周期定时器(ShortCycleTimer),当ShortCycleTimer超时则转换为长的DRX周期。
DRX周期由“持续时间(On Duration)”部分和“DRX机会(Opportunity for DRX)”部分组成,其中,在“On Duration”时间内UE监听并接收物理下行控制信道(physical downlink control channel,PDCCH),在“Opportunity for DRX”时间内UE可以不监听或不接收PDCCH以减少功耗。DRX机制包括持续定时器(onDurationTimer或drx-onDurationTimer),在每个DRX周期的开始(即每个DRX周期的on Duration的开始)UE需要开启onDurationTimer,当onDurationTimer超时则表示“on Duration”时间结束,此时UE进入“Opportunity for DRX”时间。
此外,DRX机制中还包括活动定时器(InactivityTimer或drx-InactivityTimer),具体的,当UE在“on Duration”时间内接收到指示初传(new transmission)的PDCCH时,由于UE很可能在接下来的时间内继续被基站调度,UE需要开启InactivityTimer,在InactivityTimer运行时间内UE需要监听并接收PDCCH。以及,DRX机制中还包括重传定时器(RetransmissionTimer或drx-RetransmissionTimer),由于基站可能在RetransmissionTimer运行时间内调度UE的重传,在RetransmissionTimer运行时间内UE需要监听并接收PDCCH。其中,RetransmissionTimer具体包括了上行RetransmissionTimer(RetransmissionTimerUL或drx-RetransmissionTimerUL)和下行RetransmissionTimer(RetransmissionTimerDL或drx-RetransmissionTimerDL)。
综上可知,UE需要在onDurationTimer、InactivityTimer、RetransmissionTimer(RetransmissionTimerUL、RetransmissionTimerDL)运行过程中监听并接收PDCCH,上述时间可以称为DRX的“激活时间(Active Time)”,UE需要醒来(或唤醒)准备接收信令和数据等。而不在上述Timer的运行期间,或者,不在其他需要处于“激活时间”的特殊情况下,UE可以不需要监听并接收PDCCH,此时称为DRX的“休眠时间”,UE可以休眠。其中,其他需要处于“激活时间”的特殊情况例如:随机接入竞争解决定时器ra-ContentionResolutionTimer运行过程中,或发送了调度请求SR且SR还处于挂起(pending)的状态,或在成功接收到随机接入响应消息且该随机接入响应消息没有包含对应的随机接入前导码之后,还没有收到指示初传的小区无线网络临时标识(cell radio network temporary identifier,C-RNTI)加扰的PDCCH。
但是在实际中,在上述激活时间内,UE可能并不需要接收PDCCH,可以休眠,也就 说是UE可能会在该时间内白白醒来,白白消耗监听PDCCH的功耗。所以如何节省功耗是亟待解决的问题。
目前,为了节省功耗引入了指示信号,可以利用指示信号来实现UE进入休眠。然而目前的方法,只能按照现有DRX机制中规定的onDuration时间或者DRX周期的时间去指示UE休眠,而在InactivityTimer或RetransmissionTimer已经开启的时候,UE仍会保持一段时间的激活时间,仍然会导致UE的功耗增加。因此现有的方法还不能很好的节省功耗。
发明内容
本申请提供一种终端设备的休眠方法及装置,用以实现满足节省功耗的需求。
第一方面,本申请提供了一种终端设备的休眠方法,该方法包括:
若终端设备在预设时间内未接收到指示唤醒的信号的情况下,若活动定时器InactivityTimer正在运行,所述终端设备停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer;其中,所述终端设备配置了非连续接收DRX。
通过上述方法,可以避免现有技术中若InactivityTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
结合第一方面,在第一方面的第一种可能的实现方式中,所述终端设备在预设时间内未接收到指示唤醒的信号,具体可以包括:所述终端设备在预设时间内接收到休眠信号;或者,所述终端设备在预设时间内未接收到唤醒信号;或者,所述终端设备在预设时间内接收到指示信号,所述指示信号中包含休眠指示信息。
通过上述方法,所述终端设备可以准确地确定所述终端设备没有接收到指示唤醒的信号。
结合第一方面或第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,所述终端设备停止所述InactivityTimer,具体可以为:所述终端设备在预设时间内未接收到指示唤醒的信号时停止所述InactivityTimer;或者,所述终端设备在预设时间内未接收到指示唤醒的信号后停止所述InactivityTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
结合第一方面、第一方面的第一种和第二种可能的实现方式中的任一项,在第一方面的第三种可能的实现方式中,所述终端设备停止所述RetransmissionTimer,具体可以为:所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
结合第一方面、第一方面的第一种至第三种可能的实现方式中的任一项,在第一方面的第四种可能的实现方式中,所述终端设备还可以执行:若所述InactivityTimer正在运行,所述终端设备重置所述InactivityTimer;或者,若所述RetransmissionTimer正在运行,所述终端设备重置所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备重置所述InactivityTimer和所述RetransmissionTimer。
通过上述方法,在下一次需要开启所述InactivityTimer和/或所述RetransmissionTimer 时,可以使所述InactivityTimer和/或所述RetransmissionTimer从初始值开始计时,以免影响正常流程。
结合第一方面、第一方面的第一种至第四种可能的实现方式中的任一项,在第一方面的第五种可能的实现方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第一方面、第一方面的第一种至第五种可能的实现方式中的任一项,在第一方面的第六种可能的实现方式中,所述终端设备停止所述InactivityTimer,并且所述终端设备启动或者重启短周期定时器ShortCycleTimer。这样可以使在所述终端设备及时停止所述InactivityTimer时,也保持原DRX机制不变,可以使所述终端设备继续使用所述短的DRX周期。
结合第一方面、第一方面的第一种至第五种可能的实现方式中的任一项,在第一方面的第七种可能的实现方式中,所述终端设备停止所述InactivityTimer,并且所述终端设备使用长的DRX周期。这样可以使所述终端设备更加省电。
结合第一方面的第七种可能的实现方式,在第一方面的第八种可能的实现方式中,若短周期定时器ShortCycleTimer正在运行,所述终端设备停止所述ShortCycleTimer,或者,所述终端设备停止并重置所述ShortCycleTimer。这样,所述终端设备可以成功从短的DRX周期切换到长的DRX周期。
结合第一方面、第一方面的第一种至第八种可能的实现方式中的任一项,在第一方面的第九种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为下行控制信息(downlink control information,DCI),或者可以为媒介接入控制(medium access control,MAC)控制单元(control elements,CE)(MAC CE),或者可以为媒介接入控制(medium access control,MAC)协议数据单元(protocol data unit,PDU)(MAC PDU)。
结合第一方面的第九种可能的实现方式,在第一方面的第十种可能的实现方式中,若所述信号为下行控制信息DCI,所述终端设备不启动或不重启所述InactivityTimer。
结合第一方面、第一方面的第一种至第十种可能的实现方式中的任一项,在第一方面的第十一种可能的实现方式中,若持续定时器正在运行,所述终端设备停止所述持续定时器,或者,所述终端设备停止并重置所述持续定时器。
第二方面,本申请提供了一种终端设备的休眠方法,该方法包括:
终端设备接收来自通信设备的指示休眠的信号后,启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,所述终端设备在所述休眠定时器运行期间休眠包括:所述终端设备在所述休眠定时器运行期间不监听物理下行控制信道PDCCH。
通过上述方法,可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
结合第二方面,在第二方面的第一种可能的实现方式中,所述终端设备在所述休眠定时器运行期间休眠还可以包括:所述终端设备在所述休眠定时器运行期间不发送类型0触发的探测参考信号type-0-triggered SRS;或者,所述终端设备在所述休眠定时器运行期间不上报信道状态信息CSI;或者,所述终端设备在所述休眠定时器运行期间不发送所述type-0-triggered SRS且不上报所述CSI。其中,所述类型0触发的探测参考信号即周期探测参考信号periodic SRS和半静态探测参考信号semi-persistent SRS,所述终端设备在所述休眠定 时器运行期间不发送类型0触发的探测参考信号type-0-triggered SRS,也即,所述终端设备在所述休眠定时器运行期间不发送周期探测参考信号periodic SRS和/或半静态探测参考信号semi-persistent SRS。
通过上述方法,所述终端设备可以休眠的更加彻底,从而可以更加节省功耗。
结合第二方面或第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,所述终端设备接收来自所述通信设备的指示休眠的信号,可以包括:所述终端设备接收来自所述通信设备的休眠信号;或者所述终端设备接收来自所述通信设备的指示信号,所述指示信号中包含休眠指示信息。
通过上述方法,所述终端设备可以准确确定接收到指示休眠的信号。
结合第二方面、第二方面的第一种和第二种可能的实现方式中的任一项,在第二方面的第三种可能的实现方式中,所述终端设备接收来自所述通信设备的指示休眠的信号之前,所述终端设备还接收所述通信设备配置的休眠时长。
通过上述方法,所述终端设备可以获知所述休眠时长,以使后续为休眠定时器配置定时时长为所述休眠时长。
结合第二方面、第二方面的第一种和第二种可能的实现方式中的任一项,在第二方面的第四种可能的实现方式中,所述信号中包括指示信息,所述指示信息指示休眠时长。
通过上述方法,所述终端设备可以通过所述指示信息获知所述休眠时长,以使后续为休眠定时器配置定时时长为所述休眠时长。
结合第二方面的第四种可能的实现方式,在第二方面的第五种可能的实现方式中,所述终端设备接收来自所述通信设备的指示休眠的信号之前,所述终端设备接收所述通信设备配置的至少一个时长,所述休眠时长为所述至少一个时长中的一个。
通过上述方法,所述终端设备可以通过指示信息在所述至少一个时长中获得所述休眠时长。
结合第二方面、第二方面的第三种至第五种可能的实现方式中的任一项,在第二方面的第六种可能的实现方式中,所述终端设备启动或重启休眠定时器之前,配置所述休眠定时器的定时时长为所述休眠时长。这样,所述终端设备可以休眠所述休眠时长。
结合第二方面、第二方面的第一种至第六种可能的实现方式中的任一项,在第一方面的第七种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
结合第二方面、第二方面的第一种至第七种可能的实现方式中的任一项,在第一方面的第八种可能的实现方式中,所述通信设备可以为网络设备,例如基站,还可以为其他设备,例如终端设备。
结合第二方面的第七种可能的实现方式,在第二方面的第九种可能的实现方式中,若所述信号为下行控制信息DCI,所述终端设备不启动或不重启活动定时器InactivityTimer。
第三方面,本申请提供了一种终端设备的休眠方法,该方法包括:
若终端设备接收到指示休眠的信号的情况下,若活动定时器InactivityTimer正在运行,所述终端设备停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述 RetransmissionTimer;其中,所述终端设备配置了非连续接收DRX。
通过上述方法,可以避免现有技术中若InactivityTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
结合第三方面,在第三方面的第一种可能的实现方式中,所述终端设备接收到指示休眠的信号,具体可以包括:所述终端设备接收到休眠信号;或者所述终端设备接收到指示信号,所述指示信号中包含休眠指示信息。
通过上述方法,所述终端设备可以准确地确定所述终端设备接收到指示休眠的信号。
结合第三方面或第三方面的第一种可能的实现方式,在第三方面的第二种可能的实现方式中,所述终端设备停止所述InactivityTimer,具体可以为:所述终端设备在接收到指示休眠的信号时停止所述InactivityTimer;或者,所述终端设备在接收到指示休眠的信号后停止所述InactivityTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
结合第三方面、第三方面的第一种和第二种可能的实现方式中的任一项,在第三方面的第三种可能的实现方式中,所述终端设备停止所述RetransmissionTimer,具体可以为所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
结合第三方面、第三方面的第一种至第三种可能的实现方式中的任一项,在第三方面的第四种可能的实现方式中,所述终端设备还可以执行:若所述InactivityTimer正在运行,所述终端设备重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,所述终端设备重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备重置所述InactivityTimer和所述RetransmissionTimer。
通过上述方法,在下一次需要开启所述InactivityTimer和/或所述RetransmissionTimer时,可以使所述InactivityTimer和/或所述RetransmissionTimer从初始值开始计时,以免影响正常流程。
结合第三方面、第三方面的第一种至第四种可能的实现方式中的任一项,在第三方面的第五种可能的实现方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第三方面、第三方面的第一种至第五种可能的实现方式中的任一项,在第三方面的第六种可能的实现方式中,所述终端设备停止所述InactivityTimer,并且所述终端设备启动或者重启短周期定时器ShortCycleTimer。这样可以使在所述终端设备及时停止所述InactivityTimer时,也保持原DRX机制不变,可以使所述终端设备继续使用所述短的DRX周期。
结合第三方面、第三方面的第一种至第五种可能的实现方式中的任一项,在第三方面的第七种可能的实现方式中,所述终端设备停止所述InactivityTimer,并且所述终端设备使用长的DRX周期。这样可以使所述终端设备更加省电。
结合第三方面的第七种可能的实现方式,在第三方面的第八种可能的实现方式中,若短周期定时器ShortCycleTimer正在运行,所述终端设备停止所述ShortCycleTimer,或者,所述终端设备停止并重置所述ShortCycleTimer。这样,所述终端设备可以成功从短的DRX 周期切换到长的DRX周期。
结合第三方面、第三方面的第一种至第八种可能的实现方式中的任一项,在第三方面的第九种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
结合第三方面的第九种可能的实现方式,在第三方面的第十种可能的实现方式中,若所述信号为下行控制信息DCI,所述终端设备不启动或不重启所述InactivityTimer。
结合第三方面、第三方面的第一种至第十种可能的实现方式中的任一项,在第三方面的第十一种可能的实现方式中,若持续定时器正在运行,所述终端设备停止所述持续定时器,或者,所述终端设备停止并重置所述持续定时器。
第四方面,本申请提供了一种终端设备的休眠方法,该方法包括:
终端设备接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器;若持续定时器onDurationTimer正在运行,所述终端设备停止所述onDurationTimer;或者若活动定时器InactivityTimer正在运行,所述终端设备停止所述InactivityTimer;或者若所述onDurationTimer和所述InactivityTimer正在运行,所述终端设备停止所述onDurationTimer和所述InactivityTimer;其中,所述终端设备配置了DRX。
通过上述方法,可以使终端设备及时进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
结合第四方面,在第四方面的第一种可能的实现方式中,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer,其中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第四方面或第四方面的第一种可能的实现方式,在第四方面的第二种可能的实现方式中,所述指示消息为物理层序列、或DCI、或MAC CE、或MAC PDU。
结合第四方面、第四方面的第一种和第二种可能的实现方式中的任一项,在第四方面的第三种可能的实现方式中,所述终端设备接收指示消息,具体可以为所述终端设备在使用长的DRX周期时,接收所述指示消息。
结合第四方面的第三种可能的实现方式,在第四方面的第四种可能的实现方式中,所述终端设备继续使用所述长的DRX周期。
结合第四方面、第四方面的第一种和第二种可能的实现方式中的任一项,在第四方面的第五种可能的实现方式中,所述终端设备接收指示消息,具体可以为所述终端设备在使用短的DRX周期时,接收所述指示消息。
结合第四方面的第五种可能的实现方式,在第四方面的第六种可能的实现方式中,所述终端设备继续使用所述短的DRX周期。
结合第四方面的第五种或第六种可能的实现方式,在第四方面的第七种可能的实现方式中,所述终端设备不启动或不重启短周期定时器ShortCycleTimer。
结合第四方面、第四方面的第一种至第七种可能的实现方式中的任一项,在第四方面的第八种可能的实现方式中,若所述onDurationTimer正在运行,所述终端设备还可以重置所述onDurationTimer;若所述InactivityTimer正在运行,所述终端设备还可以重置所述InactivityTimer。
通过上述方法,在下一次需要开启所述InactivityTimer和/或所述onDurationTimer时,可以使所述InactivityTimer和/或所述onDurationTimer从初始值开始计时,以免影响正常流程。
结合第四方面的第一种可能的实现方式,在第四方面的第九种可能的实现方式中,若所述RetransmissionTimer正在运行,所述终端设备还可以重置所述RetransmissionTimer。
通过上述方法,在下一次需要开启所述RetransmissionTimer时,可以使所述RetransmissionTimer从初始值开始计时,以免影响正常流程。
第五方面,本申请还提供了一种终端设备,该终端设备包括:
接收单元,用于接收信号;处理单元,用于若所述接收单元在预设时间内未接收到指示唤醒的信号,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
结合第五方面,在第五方面的第一种可能的实现方式中,所述接收单元在预设时间内未接收到指示唤醒的信号,具体用于:在预设时间内接收到休眠信号;或者在预设时间内未接收到唤醒信号;或者在预设时间内接收到指示信号,所述指示信号中包含休眠指示信息。
结合第五方面或第五方面的第一种可能的实现方式,在第五方面的第二种可能的实现方式中,所述处理单元停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
结合第五方面、第五方面的第一种和第二种可能的实现方式中的任一项,在第五方面的第三种可能的实现方式中,所述处理单元停止所述RetransmissionTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
结合第五方面、第五方面的第一种至第三种可能的实现方式中的任一项,在第五方面的第四种可能的实现方式中,所述处理单元还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
结合第五方面、第五方面的第一种至第四种可能的实现方式中的任一项,在第五方面的第五种可能的实现方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第五方面、第五方面的第一种至第五种可能的实现方式中的任一项,在第五方面的第六种可能的实现方式中,所述处理单元还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
结合第五方面、第五方面的第一种至第五种可能的实现方式中的任一项,在第五方面的第七种可能的实现方式中,所述处理单元还用于停止所述InactivityTimer,并且使用长的DRX周期。
结合第五方面的第七种可能的实现方式,在第五方面的第八种可能的实现方式中,所述处理单元还用于若短周期定时器ShortCycleTimer正在运行,停止所述ShortCycleTimer, 或者,停止并重置所述ShortCycleTimer。
结合第五方面、第五方面的第一种至第八种可能的实现方式中的任一项,在第五方面的第九种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
结合第五方面的第九种可能的实现方式,在第五方面的第十种可能的实现方式中,若所述信号为下行控制信息DCI,所述终端设备不启动或不重启所述InactivityTimer。
结合第五方面、第五方面的第一种至第十种可能的实现方式中的任一项,在第五方面的第十一种可能的实现方式中,若持续定时器正在运行,所述处理单元还用于停止所述持续定时器,或者,停止并重置所述持续定时器。
第六方面,本申请还提供了一种终端设备,该终端设备包括:
接收单元,用于接收来自通信设备的指示休眠的信号;处理单元,用于启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,在所述休眠定时器运行期间休眠包括:在所述休眠定时器运行期间不监听物理下行控制信道PDCCH。
结合第六方面,在第六方面的第一种可能的实现方式中,所述处理单元在所述休眠定时器运行期间休眠还包括:
在所述休眠定时器运行期间不发送类型0触发的探测参考信号type-0-triggered SRS;或者在所述休眠定时器运行期间不上报信道状态信息CSI;或者在所述休眠定时器运行期间不发送所述type-0-triggered SRS且不上报所述CSI。
结合第六方面或第六方面的第一种可能的实现方式,在第六方面的第二种可能的实现方式中,所述接收单元接收来自所述通信设备的指示休眠的信号,具体用于:接收来自所述通信设备的休眠信号;或者接收来自所述通信设备的指示信号,所述指示信号中包含休眠指示信息。
结合第六方面、第六方面的第一种和第二种可能的实现方式中的任一项,在第六方面的第三种可能的实现方式中,所述接收单元在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的休眠时长。
结合第六方面、第六方面的第一种和第二种可能的实现方式中的任一项,在第六方面的第四种可能的实现方式中,所述信号中包括指示信息,所述指示信息指示休眠时长。
结合第六方面的第四种可能的实现方式,在第六方面的第五种可能的实现方式中,所述接收单元在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的至少一个时长,所述休眠时长为所述至少一个时长中的一个。
结合第六方面、第六方面的第三种至第五种可能的实现方式中的任一项,在第六方面的第六种可能的实现方式中,所述处理单元在启动或重启休眠定时器之前,还用于配置所述休眠定时器的定时时长为所述休眠时长。
结合第六方面、第六方面的第一种至第六种可能的实现方式中的任一项,在第六方面的第七种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
结合第六方面的第七种可能的实现方式,在第六方面的第八种可能的实现方式中,若所述信号为下行控制信息DCI,所述终端设备不启动或不重启活动定时器InactivityTimer。
第七方面,本申请还提供了一种终端设备,该终端设备包括:
接收单元,用于接收信号;处理单元,用于若所述接收单元接收到指示休眠的信号,若活动定时器InactivityTimer正在运行,所述终端设备停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
结合第七方面,在第七方面的第一种可能的实现方式中,所述接收单元接收到指示休眠的信号,具体用于:接收到休眠信号;或者接收到指示信号,所述指示信号中包含休眠指示信息。
结合第七方面或第七方面的第一种可能的实现方式,在第七方面的第二种可能的实现方式中,所述处理单元停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
结合第七方面、第七方面的第一种和第二种可能的实现方式中的任一项,在第七方面的第三种可能的实现方式中,所述处理单元停止所述RetransmissionTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
结合第七方面、第七方面的第一种至第三种可能的实现方式中的任一项,在第七方面的第四种可能的实现方式中,所述处理单元还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
结合第七方面、第七方面的第一种至第四种可能的实现方式中的任一项,在第七方面的第五种可能的实现方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第七方面、第七方面的第一种至第五种可能的实现方式中的任一项,在第七方面的第六种可能的实现方式中,所述处理单元还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
结合第七方面、第七方面的第一种至第五种可能的实现方式中的任一项,在第七方面的第七种可能的实现方式中,所述处理单元还用于停止所述InactivityTimer,并且使用长的DRX周期。
结合第七方面的第七种可能的实现方式,在第七方面的第八种可能的实现方式中,所述处理单元还用于若ShortCycleTimer正在运行,停止所述ShortCycleTimer,或者,停止并重置所述ShortCycleTimer。
结合第七方面、第七方面的第一种至第八种可能的实现方式中的任一项,在第七方面的第九种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
结合第七方面的第九种可能的实现方式,在第七方面的第十种可能的实现方式中,若所述信号为下行控制信息DCI,所述终端设备不启动或不重启所述InactivityTimer。
结合第七方面、第七方面的第一种至第十种可能的实现方式中的任一项,在第七方面的第十一种可能的实现方式中,若持续定时器正在运行,所述处理单元还用于停止所述持续定时器,或者,停止并重置所述持续定时器。
第八方面,本申请还提供了一种终端设备,该终端设备包括:
接收单元,用于接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器,其中,所述终端设备配置了非连续接收DRX;处理单元,用于若持续定时器onDurationTimer正在运行,停止所述onDurationTimer;或者,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若所述onDurationTimer和所述InactivityTimer正在运行,停止所述onDurationTimer和所述InactivityTimer。
结合第八方面,在第八方面的第一种可能的实现方式中,所述处理单元还用于:若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer,其中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第八方面或第八方面的第一种可能的实现方式,在第八方面的第二种可能的实现方式中,所述指示消息为物理层序列、或DCI、或MAC CE、或MAC PDU。
结合第八方面、第八方面的第一种和第二种可能的实现方式中的任一项,在第八方面的第三种可能的实现方式中,所述接收单元接收指示消息,具体用于所述处理单元在使用长的DRX周期时,接收所述指示消息。
结合第八方面的第三种可能的实现方式,在第八方面的第四种可能的实现方式中,还用于继续使用所述长的DRX周期。
结合第八方面、第八方面的第一种和第二种可能的实现方式中的任一项,在第八方面的第五种可能的实现方式中,所述终端设备接收指示消息,具体可以为所述终端设备在使用短的DRX周期时,接收所述指示消息。
结合第八方面的第五种可能的实现方式,在第八方面的第六种可能的实现方式中,所述终端设备继续使用所述短的DRX周期。
结合第八方面的第五种或第六种可能的实现方式,在第八方面的第七种可能的实现方式中,所述终端设备不启动或不重启短周期定时器ShortCycleTimer。
第九方面,本申请还提供了一种终端设备,该终端设备包括收发器、至少一个存储器和至少一个处理器,其中:
所述收发器用于在接收到所述处理器的调用时收发信号;所述处理器用于与所述存储器耦合,调用所述存储器中的程序,执行以下步骤:若所述收发器在预设时间内未接收到指示唤醒的信号时,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
结合第九方面,在第九方面的第一种可能的实现方式中,所述收发器在预设时间内未接收到指示唤醒的信号,具体用于:在预设时间内接收到休眠信号;或者在预设时间内未接收到唤醒信号;或者在预设时间内接收到指示信号,所述指示信号中包含休眠指示信息。
结合第九方面或第九方面的第一种可能的实现方式,在第九方面的第二种可能的实现方式中,所述处理器停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
结合第九方面、第九方面的第一种和第二种可能的实现方式中的任一项,在第九方面的第三种可能的实现方式中,所述处理器停止所述RetransmissionTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
结合第九方面、第九方面的第一种至第三种可能的实现方式中的任一项,在第九方面的第四种可能的实现方式中,所述处理器还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
结合第九方面、第九方面的第一种至第四种可能的实现方式中的任一项,在第九方面的第五种可能的实现方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第九方面、第九方面的第一种至第五种可能的实现方式中的任一项,在第九方面的第六种可能的实现方式中,所述处理器还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
结合第九方面、第九方面的第一种至第五种可能的实现方式中的任一项,在第九方面的第七种可能的实现方式中,所述处理器还用于停止所述InactivityTimer,并且使用长的DRX周期。
结合第九方面的第七种可能的实现方式,在第九方面的第八种可能的实现方式中,所述处理器还用于若短周期定时器ShortCycleTimer正在运行,停止所述ShortCycleTimer,或者,停止并重置所述ShortCycleTimer。
结合第九方面、第九方面的第一种至第八种可能的实现方式中的任一项,在第九方面的第九种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
结合第九方面、第九方面的第一种至第九种可能的实现方式中的任一项,在第九方面的第十种可能的实现方式中,若持续定时器正在运行,所述处理器还用于停止所述持续定时器,或者,停止并重置所述持续定时器。
第十方面,本申请还提供了一种终端设备,该终端设备包括收发器、至少一个存储器和至少一个处理器,其中:
所述收发器用于在接收到所述处理器的调用时接收来自通信设备的指示休眠的信号;所述处理器,用于与所述存储器耦合,调用所述存储器中的程序,执行以下步骤:启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,在所述休眠定时器运行期间休眠包括:在所述休眠定时器运行期间不监听PDCCH。
结合第十方面,在第十方面的第一种可能的实现方式中,所述处理器在所述休眠定时器运行期间休眠还包括:在所述休眠定时器运行期间不发送类型0触发的探测参考信号type-0-triggered SRS;或者在所述休眠定时器运行期间不上报信道状态信息CSI;或者在所述休眠定时器运行期间不发送所述type-0-triggered SRS且不上报所述CSI。
结合第十方面或第十方面的第一种可能的实现方式,在第十方面的第二种可能的实现方式中,所述收发器接收来自所述通信设备的指示休眠的信号,具体用于:接收来自所述通信设备的休眠信号;或者接收来自所述通信设备的指示信号,所述指示信号中包含休眠 指示信息。
结合第十方面、第十方面的第一种和第二种可能的实现方式中的任一项,在第十方面的第三种可能的实现方式中,所述收发器在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的休眠时长。
结合第十方面、第十方面的第一种和第二种可能的实现方式中的任一项,在第十方面的第四种可能的实现方式中,所述信号中包括指示信息,所述指示信息指示休眠时长。
结合第十方面的第四种可能的实现方式,在第十方面的第五种可能的实现方式中,所述收发器在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的至少一个时长,所述休眠时长为所述至少一个时长中的一个。
结合第十方面、第十方面的第三种至第五种可能的实现方式中的任一项,在第十方面的第六种可能的实现方式中,所述处理器在启动或重启休眠定时器之前,还用于配置所述休眠定时器的定时时长为所述休眠时长。
结合第十方面、第十方面的第一种至第六种可能的实现方式中的任一项,在第十方面的第七种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
第十一方面,本申请还提供了一种终端设备,该终端设备包括收发器、至少一个存储器和至少一个处理器,其中:
所述收发器,用于在接收到所述处理器的调用时接收信号;所述处理器,用于与所述存储器耦合,调用所述存储器中的程序,执行以下步骤:若所述收发器接收到指示休眠的信号,若活动定时器InactivityTimer正在运行,所述终端设备停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
结合第十一方面,在第十一方面的第一种可能的实现方式中,所述收发器接收到指示休眠的信号,具体用于:接收到休眠信号;或者接收到指示信号,所述指示信号中包含休眠指示信息。
结合第十一方面或第十一方面的第一种可能的实现方式,在第十一方面的第二种可能的实现方式中,所述处理器停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
结合第十一方面、第十一方面的第一种和第二种可能的实现方式中的任一项,在第十一方面的第三种可能的实现方式中,所述处理器停止所述RetransmissionTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
结合第十一方面、第十一方面的第一种至第三种可能的实现方式中的任一项,在第十一方面的第四种可能的实现方式中,所述处理器还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
结合第十一方面、第十一方面的第一种至第四种可能的实现方式中的任一项,在第十 一方面的第五种可能的实现方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第十一方面、第十一方面的第一种至第五种可能的实现方式中的任一项,在第十一方面的第六种可能的实现方式中,所述处理器还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
结合第十一方面、第十一方面的第一种至第五种可能的实现方式中的任一项,在第十一方面的第七种可能的实现方式中,所述处理器还用于停止所述InactivityTimer,并且使用长的DRX周期。
结合第十一方面的第七种可能的实现方式,在第十一方面的第八种可能的实现方式中,所述处理器还用于若ShortCycleTimer正在运行,停止所述ShortCycleTimer,或者,停止并重置所述ShortCycleTimer。
结合第十一方面、第十一方面的第一种至第八种可能的实现方式中的任一项,在第十一方面的第九种可能的实现方式中,所述信号的形式可以为一种物理层序列,或者可以为DCI,或者可以为MAC CE,或者可以为MAC PDU。
结合第十一方面、第十一方面的第一种至第九种可能的实现方式中的任一项,在第十一方面的第十种可能的实现方式中,若持续定时器正在运行,所述处理器还用于停止所述持续定时器,或者,停止并重置所述持续定时器。
第十二方面,本申请还提供了一种终端设备,该终端设备包括收发器、至少一个存储器和至少一个处理器,其中:
所述收发器,用于在接收到所述处理器的调用时接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器,其中,所述终端设备配置了非连续接收DRX;
所述处理器,用于与所述存储器耦合,调用所述存储器中的程序,执行以下步骤:若持续定时器onDurationTimer正在运行,停止所述onDurationTimer;或者,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若所述onDurationTimer和所述InactivityTimer正在运行,停止所述onDurationTimer和所述InactivityTimer。
结合第十二方面,在第十二方面的第一种可能的实现方式中,所述处理器还用于:若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer,其中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
结合第十二方面或第十二方面的第一种可能的实现方式,在第十二方面的第二种可能的实现方式中,所述指示消息为物理层序列、或DCI、或MAC CE、或MAC PDU。
结合第十二方面、第十二方面的第一种和第二种可能的实现方式中的任一项,在第十二方面的第三种可能的实现方式中,所述收发器接收指示消息,具体用于所述处理器在使用长的DRX周期时,接收所述指示消息。
结合第十二方面的第三种可能的实现方式,在第十二方面的第四种可能的实现方式中,还用于继续使用所述长的DRX周期。
结合第十二方面、第十二方面的第一种和第二种可能的实现方式中的任一项,在第十二方面的第五种可能的实现方式中,所述终端设备接收指示消息,具体可以为所述终端设备在使用短的DRX周期时,接收所述指示消息。
结合第十二方面的第五种可能的实现方式,在第十二方面的第六种可能的实现方式中,所述终端设备继续使用所述短的DRX周期。
结合第十二方面的第五种或第六种可能的实现方式,在第十二方面的第七种可能的实现方式中,所述终端设备不启动或不重启短周期定时器ShortCycleTimer。
第十三方面,本申请还提供了一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述任一种方法。
第十四方面,本申请还提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述任一种方法。
第十五方面,本申请还提供了一种芯片,所述芯片与存储器相连,用于读取并执行所述存储器中存储的程序指令,以实现上述任一种方法。
第十六方面,本申请还提供了一种终端设备的状态指示方法,该方法包括:
终端设备接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;若所述第一消息指示所述终端设备唤醒的时间信息,则所述终端设备基于所述时间信息唤醒;或者,若所述第一消息指示所述终端设备休眠的时间信息,则所述终端设备基于所述时间信息休眠。
通过上述方法,所述终端设备可以根据所述第一消息灵活唤醒或者休眠。并且相对于现有技术,由于引入了对终端设备休眠的时间信息的指示,可以使终端设备相对于现有技术灵活休眠,从而可以更好的节省功耗,满足节省功耗的需求。
结合第十六方面,在第十六方面的第一种可能的实现方式中,所述第一消息可以包括第一指示信息,所述第一指示信息指示所述时间信息。这样所述第一消息可以通过所述第一指示信息指示所述终端设备唤醒或者休眠的时间信息。
结合第十六方面或第十六方面的第一种可能的实现方式,在第十六方面的第二种可能的实现方式中,所述第一消息可以包括第二指示信息,所述第二指示信息指示所述终端设备唤醒或者休眠。
通过上述方法,所述第一消息可以通过所述第二指示信息实现终端设备唤醒或者休眠的指示。
结合第十六方面、第十六方面的第一种和第二种可能的实现方式中的任一项,在第十六方面的第三种可能的实现方式中,所述时间信息可以为所述终端设备唤醒或者休眠的时间长度;或者,所述时间信息可以为所述终端设备唤醒或者休眠之前的时间长度;或者,所述时间信息可以为所述终端设备唤醒或者休眠结束的时间。
通过上述方法,可以通过多种方式灵活对所述终端设备唤醒或者休眠的事件进行指示。
结合第十六方面的第三种可能的实现方式,在第十六方面的第四种可能的实现方式中,所述时间长度可以为:一个或多个毫秒;或者,一个或多个子帧;或者,一个或多个时隙;或者,一个或多个非连续接收DRX周期;或者,一个或多个On Duration;或者,一个或多个寻呼机会(paging occasion,PO);或者,一个或多个物理下行控制信道PDCCH监听机会;或者,以毫秒为单位的时间长度;或者,以子帧为单位的时间长度;或者,以时隙为单位的时间长度;或者,以非连续接收DRX周期为单位的时间长度;或者,以On  Duration个数为单位的时间长度;或者,以寻呼机会为单位的时间长度;或者,以物理下行控制信道PDCCH监听机会为单位的时间长度。
通过上述方法,可以通过多种方式来表示所述时间长度,可以是所述时间长度比较灵活。
结合第十六方面的第一种可能的实现方式,在第十六方面的第五种可能的实现方式中,所述第一消息可以为MAC PDU或者RRC信令。
结合第十六方面的第五种可能的实现方式,在第十六方面的第六种可能的实现方式中,所述第一指示信息可以携带在所述MAC PDU的媒介接入控制子头中,或者,所述第一指示信息可以携带在所述MAC PDU的MAC CE中。
通过上述方法,所述第一指示信息可以成功携带在所述第一消息中,以实现指示所述终端设备唤醒或者休眠的时间信息。
结合第十六方面的第二种可能的实现方式,在第十六方面的第七种可能的实现方式中,所述第一消息可以为MAC PDU。
结合第十六方面的第七种可能的实现方式,在第十六方面的第八种可能的实现方式中,所述第二指示信息可以携带在所述MAC PDU的媒介接入控制子头中,或者,所述第二指示信息可以携带在所述MAC PDU的MAC CE中。
通过上述方法,所述第二指示信息可以成功携带在所述第一消息中,以实现指示所述终端设备唤醒或者休眠。
结合第十六方面、第十六方面的第一种至第四种可能的实现方式中的任一项,在第十六方面的第九种可能的实现方式中,所述第一消息可以为MAC PDU或者RRC信令。
结合第十六方面、第十六方面的第一种至第四种可能的实现方式中的任一项,在第十六方面的第十种可能的实现方式中,所述第一消息可以为DCI。
结合第十六方面的第十种可能的实现方式,在第十六方面的第十一种可能的实现方式中,所述终端设备不启动或不重启活动定时器。这样可以节省操作。
结合第十六方面、第十六方面的第一种至第十一种可能的实现方式中的任一项,在第十六方面的第十二种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若活动定时器正在运行,所述终端设备停止所述活动定时器,或者,所述终端设备停止并重置所述活动定时器。这样可以使所述终端设备更加省电。
结合第十六方面、第十六方面的第一种至第十一种可能的实现方式中的任一项,在第十六方面的第十三种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若持续定时器正在运行,所述终端设备停止所述持续定时器,或者,所述终端设备停止并重置所述持续定时器。这样可以使所述终端设备更加省电。
结合第十六方面、第十六方面的第一种至第十一种可能的实现方式中的任一项,在第十六方面的第十四种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若重传定时器正在运行,所述终端设备停止所述重传定时器,或者,所述终端设备停止并重置所述重传定时器。这样可以使所述终端设备更加省电。
第十七方面,本申请还提供了一种终端设备,该终端设备包括:
接收单元,用于接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;处理单元,用于若所述第一消息指示所述终端设备唤醒的时间信息, 则基于所述时间信息唤醒;或者,若所述第一消息指示所述终端设备休眠的时间信息,则基于所述时间信息休眠。
结合第十七方面,在第十七方面的第一种可能的实现方式中,所述第一消息包括第一指示信息,所述第一指示信息指示所述时间信息。
结合第十七方面或第十七方面的第一种可能的实现方式,在第十七方面的第二种可能的实现方式中,所述第一消息包括第二指示信息,所述第二指示信息指示所述终端设备唤醒或者休眠。
结合第十七方面、第十七方面的第一种和第二种可能的实现方式中的任一项,在第十七方面的第三种可能的实现方式中,所述时间信息为所述终端设备唤醒或者休眠的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠之前的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠结束的时间。
结合第十七方面的第三种可能的实现方式,在第十七方面的第四种可能的实现方式中,所述时间长度为:一个或多个毫秒;或者,一个或多个子帧;或者,一个或多个时隙;或者,一个或多个非连续接收DRX周期;或者,一个或多个On Duration;或者,一个或多个寻呼机会;或者,一个或多个物理下行控制信道PDCCH监听机会;或者,以毫秒为单位的时间长度;或者,以子帧为单位的时间长度;或者,以时隙为单位的时间长度;或者,以非连续接收DRX周期为单位的时间长度;或者,以On Duration个数为单位的时间长度;或者,以寻呼机会为单位的时间长度;或者,以物理下行控制信道PDCCH监听机会为单位的时间长度。
结合第十七方面的第一种可能的实现方式,在第十七方面的第五种可能的实现方式中,所述第一消息为MAC PDU或者RRC信令。
结合第十七方面的第五种可能的实现方式,在第十七方面的第六种可能的实现方式中,所述第一指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第一指示信息携带在所述MAC PDU的MAC CE中。
结合第十七方面的第二种可能的实现方式,在第十七方面的第七种可能的实现方式中,所述第一消息为MAC PDU。
结合第十七方面的第七种可能的实现方式,在第十七方面的第八种可能的实现方式中,所述第二指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第二指示信息携带在所述MAC PDU的MAC CE中。
结合第十七方面、第十七方面的第一种至第四种可能的实现方式中的任一项,在第十六方面的第九种可能的实现方式中,所述第一消息为MAC PDU或者RRC信令。
结合第十七方面、第十七方面的第一种至第四种可能的实现方式中的任一项,在第十七方面的第十种可能的实现方式中,所述第一消息为DCI。
结合第十七方面的第十种可能的实现方式,在第十七方面的第十一种可能的实现方式中,所述处理单元还用于不启动或不重启活动定时器。
结合第十七方面、第十七方面的第一种至第十一种可能的实现方式中的任一项,在第十七方面的第十二种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若活动定时器正在运行,所述处理单元还用于停止所述活动定时器,或者,所述处理单元还用于停止并重置所述活动定时器。
结合第十七方面、第十七方面的第一种至第十一种可能的实现方式中的任一项,在第 十七方面的第十三种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若持续定时器正在运行,所述处理单元还用于停止所述持续定时器,或者,所述处理单元还用于停止并重置所述持续定时器。
结合第十七方面、第十七方面的第一种至第十一种可能的实现方式中的任一项,在第十七方面的第十四种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若重传定时器正在运行,所述处理单元还用于停止所述重传定时器,或者,所述处理单元还用于停止并重置所述重传定时器。
第十八方面,本申请还提供了一种终端设备,该终端设备包括收发器、至少一个存储器和至少一个处理器,其中:
所述收发器用于在接收到所述处理器的调用时收发信号或消息;所述处理器用于与所述存储器耦合,调用所述存储器中的程序,执行以下步骤:控制所述收发器接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;若所述第一消息指示所述终端设备唤醒的时间信息,则基于所述时间信息唤醒;或者,若所述第一消息指示所述终端设备休眠的时间信息,则基于所述时间信息休眠。
结合第十八方面,在第十八方面的第一种可能的实现方式中,所述第一消息包括第一指示信息,所述第一指示信息指示所述时间信息。
结合第十八方面或第十八方面的第一种可能的实现方式,在第十八方面的第二种可能的实现方式中,所述第一消息包括第二指示信息,所述第二指示信息指示所述终端设备唤醒或者休眠。
结合第十八方面、第十八方面的第一种和第二种可能的实现方式中的任一项,在第十八方面的第三种可能的实现方式中,所述时间信息为所述终端设备唤醒或者休眠的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠之前的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠结束的时间。
结合第十八方面的第三种可能的实现方式,在第十八方面的第四种可能的实现方式中,所述时间长度为:一个或多个毫秒;或者,一个或多个子帧;或者,一个或多个时隙;或者,一个或多个非连续接收DRX周期;或者,一个或多个On Duration;或者,一个或多个寻呼机会(paging occasion,PO);或者,一个或多个物理下行控制信道PDCCH监听机会;或者,以毫秒为单位的时间长度;或者,以子帧为单位的时间长度;或者,以时隙为单位的时间长度;或者,以非连续接收DRX周期为单位的时间长度;或者,以On Duration个数为单位的时间长度;或者,以寻呼机会为单位的时间长度;或者,以物理下行控制信道PDCCH监听机会为单位的时间长度。
结合第十八方面的第一种可能的实现方式,在第十八方面的第五种可能的实现方式中,所述第一消息为MAC PDU或者RRC信令。
结合第十八方面的第五种可能的实现方式,在第十八方面的第六种可能的实现方式中,所述第一指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第一指示信息携带在所述MAC PDU的MAC CE中。
结合第十八方面的第二种可能的实现方式,在第十八方面的第七种可能的实现方式中,所述第一消息为MAC PDU。
结合第十八方面的第七种可能的实现方式,在第十八方面的第八种可能的实现方式中, 所述第二指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第二指示信息携带在所述MAC PDU的MAC CE中。
结合第十八方面、第十八方面的第一种至第四种可能的实现方式中的任一项,在第十六方面的第九种可能的实现方式中,所述第一消息为MAC PDU或者RRC信令。
结合第十八方面、第十八方面的第一种至第四种可能的实现方式中的任一项,在第十八方面的第十种可能的实现方式中,所述第一消息为DCI。
结合第十八方面的第十种可能的实现方式,在第十八方面的第十一种可能的实现方式中,所述处理器还用于不启动或不重启活动定时器。
结合第十八方面、第十八方面的第一种至第十一种可能的实现方式中的任一项,在第十八方面的第十二种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若活动定时器正在运行,所述处理器还用于停止所述活动定时器,或者,所述处理器还用于停止并重置所述活动定时器。
结合第十八方面、第十八方面的第一种至第十一种可能的实现方式中的任一项,在第十八方面的第十三种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若持续定时器正在运行,所述处理器还用于停止所述持续定时器,或者,所述处理器还用于停止并重置所述持续定时器。
结合第十八方面、第十八方面的第一种至第十一种可能的实现方式中的任一项,在第十八方面的第十四种可能的实现方式中,若所述第一消息指示所述终端设备休眠的时间信息,若重传定时器正在运行,所述处理器还用于停止所述重传定时器,或者,所述处理器还用于停止并重置所述重传定时器。
第十九方面,本申请还提供了一种计算机存储介质,所述计算机存储介质中存储有计算机可执行指令,所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述第十六方面提及的任一种方法。
第二十方面,本申请还提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第十六方面提及的任一种方法。
第二十一方面,本申请还提供了一种芯片,所述芯片与存储器相连,用于读取并执行所述存储器中存储的程序指令,以实现上述第十六方面提及的任一种方法。
附图说明
图1为本申请提供的一种DRX周期的示意图;
图2为本申请提供的一种通信系统的架构图;
图3为本申请提供的一种终端设备的休眠方法的流程图;
图4为本申请提供的一种监听信号的预设时间的示意图;
图5为本申请提供的另一种监听信号的预设时间的示意图;
图6为本申请提供的一种监听信号的预设时间的示意图;
图7为本申请提供的另一种终端设备的休眠方法的流程图;
图8为本申请提供的另一种终端设备的休眠方法的流程图;
图9为本申请提供的另一种终端设备的休眠方法的流程图;
图10为本申请提供的另一种终端设备的休眠方法的流程图;
图11为本申请提供的另一种终端设备的休眠方法的流程图;
图12为本申请提供的另一种终端设备的休眠方法的流程图;
图13为本申请提供的另一种终端设备的休眠方法的流程图;
图14为本申请提供的另一种终端设备的休眠方法的流程图;
图15为本申请提供的另一种终端设备的休眠方法的流程图;
图16为本申请提供的一种终端设备的结构示意图;
图17为本申请提供的一种终端设备的结构图;
图18为本申请提供的一种终端设备的状态指示方法的流程图;
图19为本申请提供的一种第一消息的示意图;
图20为本申请提供的一种第一消息的示意图;
图21为本申请提供的一种第一消息的示意图;
图22为本申请提供的一种第一消息的示意图;
图23为本申请提供的一种第一消息的示意图;
图24为本申请提供的一种第一消息的示意图;
图25为本申请提供的一种第一消息的示意图。
具体实施方式
下面将结合附图对本申请作进一步地详细描述。
本申请实施例提供一种终端设备的休眠方法及装置,用以实现满足节省功耗的需求。其中,本申请所述方法和装置基于同一发明构思,由于方法及装置解决问题的原理相似,因此装置与方法的实施可以相互参见,重复之处不再赘述。
以下,对本申请中的部分用语进行解释说明,以便于本领域技术人员理解。
1)、DRX周期,可以包括如图1所示的“On Duration”部分和“Opportunity for DRX”部分。在“On Duration”时间内终端设备监听并接收PDCCH,在“Opportunity for DRX”时间内UE可以不监听或不接收PDCCH以减少功耗。所述DRX周期可以分为短的DRX周期(Short DRX Cycle)或者长的DRX周期(Long DRX cycle)。其中,需要说明的是,所述终端设备接收PDDCH是指所述终端设备接收承载在PDCCH上的下行控制信息(downlink control information,DCI)。
2)、唤醒信号(wake-up signal),用于指示终端设备唤醒,其中若在预设时间内没有接收到唤醒信号,则默认指示终端设备休眠。
3)、休眠信号(go-to-sleep signal),用于指示终端设备休眠,其中若在预设时间内没有接收到休眠信号,则默认指示终端设备唤醒。
4)、本申请实施例中的“多个(种)”,是指两个(种)或两个(种)以上。
5)、在本申请的描述中,“第一”、“第二”等词汇,仅用于区分描述的目的,而不能理解为指示或暗示相对重要性,也不能理解为指示或暗示顺序。
为了方便描述,在本申请的实施例中,活动定时器均以InactivityTimer示出,重传定时器均以RetransmissionTimer示出,短周期定时器均以ShortCycleTimer示出。
为了更加清晰地描述本申请实施例的技术方案,下面结合附图,对本申请实施例提供的终端设备的休眠方法及装置进行详细说明。
本申请实施例提供的终端设备的休眠方法使用的一种可能的通信系统的架构,可以包 括网络开放功能网元、策略控制功能网元、数据管理网元、应用功能网元、核心网接入和移动性管理功能网元、会话管理功能网元、终端设备、接入网设备、用户面功能网元和数据网络。其中,图2示出了所述通信系统的架构的一种可能的示例,具体包括:NEF网元、PCF网元、UDM网元、AF网元、AMF网元、SMF网元、UE、接入网(access network,AN)设备、UPF网元和数据网络(data network,DN)。其中,AMF网元与终端设备之间可以通过N1接口相连,AMF与AN设备之间可以通过N2接口相连,AN设备与UPF之间可以通过N3接口相连,SMF与UPF之间可以通过N4接口相连,UPF与DN之间可以通过N6接口相连。接口名称只是一个示例说明,本申请实施例对此不作具体限定。应理解,本申请实施例并不限于图2所示通信系统,图2中所示的网元的名称在这里仅作为一种示例说明,并不作为对本申请的方法适用的通信系统的架构中包括的网元的限定。下面对所述通信系统中的各个网元或设备的功能进行详细描述:
所述终端设备,又可以称之为用户设备(user equipment,UE)、移动台(mobile station,MS)、移动终端(mobile terminal,MT)等,是一种向用户提供语音和/或数据连通性的设备。例如,所述终端设备可以包括具有无线连接功能的手持式设备、车载设备、计算设备、移动台(mobile station,MS)或连接到无线调制解调器的其他处理设备等,以及经接入网与一个或多个核心网进行通信的移动终端。目前,所述终端设备可以是:手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device,MID)、可穿戴设备,虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self-driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端,或智慧家庭(smart home)中的无线终端等。其中,图2中所述终端设备以UE示出,仅作为示例,并不对终端设备进行限定。
无线接入网络可以为图2所示的接入网(access network,AN),向所述终端设备提供无线接入服务。所述接入网设备是所述通信系统中将所述终端设备接入到无线网络的设备。所述接入网设备为无线接入网中的节点,又可以称为基站,还可以称为无线接入网(radio access network,RAN)节点(或设备)。目前,一些接入网设备的举例为:gNB、传输接收点(transmission reception point,TRP)、演进型节点B(evolved Node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(Node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved NodeB,或home Node B,HNB)、基带单元(base band unit,BBU),或无线保真(wireless fidelity,Wifi)接入点(access point,AP)等。
所述数据网络,例如图2所示的数据网络(data network,DN),可以是因特网(Internet)、IP多媒体业务(IP Multi-media Service,IMS)网络、区域网络(即本地网络,例如移动边缘计算(mobile edge computing,MEC)网络)等。所述数据网络中包括应用服务器,所述应用服务器通过与所述终端设备进行数据传输,为所述终端设备提供业务服务。
核心网用于将所述终端设备接入可以实现所述终端设备的业务的DN。下面对所述核心网中各个网元的功能进行描述:
所述核心网接入和移动性管理功能网元,可用于对所述终端设备的接入控制和移动性进行管理,在实际应用中,其包括了长期演进(long term evolution,LTE)中网络框架中移 动管理实体(mobility management entity,MME)里的移动性管理功能,并加入了接入管理功能,具体可以负责所述终端设备的注册、移动性管理、跟踪区更新流程、可达性检测、会话管理功能网元的选择、移动状态转换管理等。例如,在5G中,所述核心网接入和移动性管理功能网元可以是AMF(access and mobility management function)网元,例如图2所示,在未来通信,如6G中,所述核心网接入和移动性管理功能网元仍可以是AMF网元,或有其它的名称,本申请不做限定。当所述核心网接入和移动性管理功能网元是AMF网元时,所述AMF可以提供Namf服务。
所述会话管理功能网元,可用于负责所述终端设备的会话管理(包括会话的建立、修改和释放),用户面功能网元的选择和重选、所述终端设备的互联网协议(internet protocol,IP)地址分配、服务质量(quality of service,QoS)控制等。例如,在5G中,所述会话管理功能网元可以是SMF(session management function)网元,例如图2所示,在未来通信,如6G中,所述会话管理功能网元仍可以是SMF网元,或有其它的名称,本申请不做限定。当会话管理功能网元时SMF网元时,所述SMF可以提供Nsmf服务。
所述策略控制功能网元,可用于负责策略控制决策、提供基于业务数据流和应用检测、门控、QoS和基于流的计费控制等功能等。例如,在5G中,所述策略控制功能网元可以是PCF(policy control function)网元,例如图2所示,在未来通信,如6G中,所述策略控制功能网元仍可以是PCF网元,或有其它的名称,本申请不做限定。当所述策略控制功能网元是PCF网元,所述PCF网元可以提供Npcf服务。
所述应用功能网元,主要功能是与第三代合作伙伴计划(the 3rd generation partnership project,3GPP)核心网交互来提供服务,来影响业务流路由、接入网能力开放、策略控制等。例如,在5G中,所述应用功能网元可以是AF(application function)网元,例如图2所示,在未来通信,如6G中,所述应用功能网元仍可以是AF网元,或有其它的名称,本申请不做限定。当所述应用功能网元是AF网元时,所述AF网元可以提供Naf服务。
所述数据管理网元,可用于管理所述终端设备的签约数据、与所述终端设备相关的注册信息等。例如,在5G中,所述数据管理网元可以是统一数据管理网元(unified data management,UDM),例如图2所示,在未来通信,如6G中,所述数据管理网元仍可以是UDM网元,或有其它的名称,本申请不做限定。当所述数据管理网元是UDM网元时,所述UDM网元可以提供Nudm服务。
所述网络开放功能网元,可用于使3GPP能够安全地向第三方的AF(例如,业务能力服务器(Services Capability Server,SCS)、应用服务器(Application Server,AS)等)提供网络业务能力等。例如,在5G中,所述网络开放功能网元可以是NEF(network exposure function)网元,例如图2所示,在未来通信,如6G中,所述网络开放功能网元仍可以是NEF网元,或有其它的名称,本申请不做限定。当所述网络开放功能网元是NEF时,所述NEF可以向其他网络功能网元提供Nnef服务。
所述用户面功能网元,可用于转发终端设备的用户面数据。主要功能是数据包路由和转发、移动性锚点、上行分类器来支持路由业务流到数据网络、分支点来支持多归属分组数据单元(Packet Data Unit,PDU)会话等。例如,在5G中,所述用户面功能网元可以是UPF(user plane function)网元,例如图2所示;在未来通信,如6G中,所述用户面功能网元仍可以是UPF网元,或有其它的名称,本申请不做限定。
核心网中的以上各个网元也可以称为功能实体,既可以是在专用硬件上实现的网络元 件,也可以是在专用硬件上运行的软件实例,或者是在适当平台上虚拟化功能的实例,例如,上述虚拟化平台可以为云平台。
需要说明的是,图2所示的通信系统的架构中不限于仅包含图中所示的网元,还可以包含其它未在图中表示的设备,具体本申请在此处不再一一列举。
需要说明的是,本申请实施例并不限定核心网中各个网元的分布形式,图2所示的分布形式只是示例性的,本申请不作限定。
为方便说明,本申请后续均以图2所示的网元为例进行说明,并将XX网元直接简称为XX。应理解,本申请中所有网元的名称仅仅作为示例,在未来通信中还可以称为其它名称,或者在未来通信中本申请涉及的网元还可以通过其它具有相同功能的实体或者设备等来替代,本申请对此均不作限定。这里做统一说明,后续不再赘述。
需要说明的是,图2所示的通信系统并不构成本申请实施例能够适用的通信系统的限定。图2所示的通信系统架构为5G系统架构,可选的,本申请实施例的方法还适用于未来的各种通信系统,例如6G或者其他通信网络等。
本申请实施例提供的一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图3所示,该方法的具体流程包括:
步骤301、终端设备在预设时间内监听信号。
其中,所述终端设备配置了DRX,也就是说所述终端设备采用图1所示的DRX周期,在DRX周期中的On Duration内监听并接收PDCCH,在Opportunity for DRX时间内所述终端设备可以不监听或不接收PDCCH以减少功耗。
在一种可选的实施方式中,所述预设时间可以为某个时间点,还可以为某个时间段。例如,所述预设时间为某个时间点时,所述预设时间可以是DRX周期开始之前一个偏移(offset)的特定时间位置,可以如图4所示的监听信号的时间点;又例如,所述预设时间为某个时间点时,所述预设时间可以是DRX周期的On Duration时间最开始的时间位置(即图4所示的方案中offset取值为0,例如,可以如图5所示的监听信号的时间点)。又例如,所述预设时间为某个时间点时,所述预设时间可以是DRX周期中的On Duration时间内的任一个时刻,例如图6所示的监听信号的时间点;或者,所述预设时间还可以是DRX的“激活时间”内的任一个时刻。又例如,当所述预设时间为某个时间段时,所述预设时间可以是从特定时间位置(可以为上述描述中的时间点)开始的一段时间,该一段时间如一个或多个符号(symbol)长度、或者、一个或多个子帧(subframe)长度、或者、一个或多个毫秒,或者,所述预设时间可以是到特定时间位置(可以为上述描述中的时间点)结束之前的一段时间,该一段时间如一个或多个符号(symbol)长度、或者、一个或多个子帧(subframe)长度、或者、一个或多个毫秒。又例如,所述预设时间为某个时间段时,所述预设时间可以是DRX周期中的On Duration时间,例如图6所示的监听信号的时间段;或者,所述预设时间还可以是DRX的“激活时间”。需要说明的是,上述举例中的预设时间的情况仅仅作为示例,并不作为对本申请预设时间的限定,所述预设时间还可以有多种其他情况,本申请不再一一列举。
在一种可选的实施方式中,所述终端设备在预设时间内监听信号,具体可以为:所述终端设备在预设时间内监听休眠信号、唤醒信号或者指示信号。其中所述指示信号可以包括指示信息,所述指示信息可以指示休眠或唤醒,也即休眠指示信息和唤醒指示信息。当 所述指示信号指示休眠时,所述指示信号中包含所述休眠指示信息;当所述指示信号指示唤醒时,所述指示信号中包含所述唤醒指示信息。
应理解,所述终端设备在所述预设时间内监听信号的过程中,可能接收到信号,也可能未接收到信号。在一种可选的实施方式中,所述信号的形式可以为一种物理层序列,或者可以为下行控制信息(downlink control information,DCI),或者可以为媒介接入控制(medium access control,MAC)控制单元(control elements,CE)(MAC CE),或者可以为媒介接入控制(medium access control,MAC)协议数据单元(protocol data unit,PDU)(MAC PDU)。
在一种可选的实施方式中,当所述终端设备在所述预设时间内监听到(也即接收到)所述休眠信号,或者未监听到所述唤醒信号,或者监听到包括所述休眠指示信息的指示信号时,在后续的n(n为大于或者等于1的整数)个DRX周期所述终端设备都不需要开启onDurationTimer,或者在后续的设定时长内所述终端设备都不需要开始所述onDurationTimer,即所述终端设备可以休眠。其中,所述onDurationTimer也可以记为drx-onDurationTimer,本申请实施例中仅以所述onDurationTimer为例进行说明,应理解,所述onDurationTimer均可以替换为所述drx-onDurationTimer。
在一种可选的实施方式中,当所述终端设备在所述预设时间内监听到(也即接收到)所述唤醒信号,或者未监听到所述休眠信号,或者监听到包括所述唤醒信息的指示信号时,在后续的n(n为大于或者等于1的整数)个DRX周期所述终端设备都需要醒来,或者在后续的设定时长内所述终端设备都需要醒来,即都需要开启onDurationTimer。
在一种可选的实施方式中,所述设定时长可以为绝对时间长度,例如N个毫秒(ms)、或N个子帧长度(subframe)、或N个符号长度(symbol)、或N个时隙长度(slot)等、或N个物理下行控制信道监听机会(PDCCH monitoring occasion),N为大于零的数或N为大于零的整数;或者,所述休眠时长可以以DRX周期为单位或者以“On Duration”时间为单位,例如N个DRX周期、或N个“On Duration”时间,N为大于零的整数。当然,上述举例仅仅为一个示例,所述休眠时长还可以为其他时间长度信息,本申请对此不作具体限定。
需要说明的是,步骤301为可选的步骤,即所述终端设备可以不执行这个步骤,而是通过其它方式确定所述终端设备在所述预设时长内是否接收到指示唤醒的信号,进而执行步骤302。本申请对此不作限定。
步骤302、若所述终端设备在预设时间内未接收到指示唤醒的信号,若InactivityTimer正在运行,所述终端设备停止所述InactivityTimer。
其中,所述InactivityTimer也可以记为drx-InactivityTimer,本申请实施例中仅以所述InactivityTimer为例进行说明。应理解,所述InactivityTimer均可以替换为drx-InactivityTimer。
在一种可选的实施方式中,所述终端设备在所述预设时间内未接收到指示唤醒的信号,可以为以下三种情况中的任一种:
情况a1:所述终端设备在预设时间内接收到休眠信号。
情况a2:所述终端设备在预设时间内未接收到唤醒信号。
情况a3:所述终端设备在预设时间内接收到指示信号,所述指示信号中包含休眠指示信息。
上述三种情况下,所述终端设备均需要休眠,因此,在所述InactivityTimer正在运行时,所述终端设备需要停止所述InactivityTimer。这样所述终端设备可以真正进入休眠,而不会受到所述InactivityTimer的影响而多余保持激活一段时间,这样可以更好地节省功耗,从而可以满足节省功耗的需求。
在一种可选的实施方式中,所述终端设备停止所述InactivityTimer,具体可以为:所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)停止所述InactivityTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。其中,示例性的,所述(当前)DXR周期为所述预设时间所在的DRX周期,所述下一个DRX周期开始指的是所述下一个DRX周期的On Duration起始位置。需要说明的是,在本申请下面的实施例涉及的(当前)周期和下一个周期均可以理解为上述描述,下面不再一一重复限定。
在一种可选的实施方式中,在上述情况a1和情况a3中,所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)停止所述InactivityTimer,具体可以指:所述终端设备在接收到所述休眠信号或者在接收到所述指示信号时(或之后)停止所述InactivityTimer。
在一种可选的实施方式中,若所述InactivityTimer正在运行,所述终端设备还可以重置所述InactivityTimer,即将所述InactivityTimer的值设置为初始值(例如0)。这样在下一次需要开启所述InactivityTimer时,可以使所述InactivityTimer从0开始计时,以免影响正常流程。
由于现在的DRX机制中,如果所述终端设备配置了短的DRX周期时,当所述InactivityTimer超时时,所述终端设备需要启动或者重启短周期定时器ShortCycleTimer,以使所述终端设备使用所述短的DRX周期。因此,在一种可选的实施方式中,所述终端设备停止所述InactivityTimer,并且所述终端设备启动或者重启所述ShortCycleTimer。这样可以使在所述终端设备及时停止所述InactivityTimer时,也保持原DRX机制不变,可以使所述终端设备继续使用所述短的DRX周期。
在一种可选的实施方式中,所述终端设备启动或者重启所述ShortCycleTimer可以为:所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)启动或者重启所述ShortCycleTimer;或者所述终端设备在(当前)DRX周期的下一个DRX周期开始时启动或者重启所述ShortCycleTimer。也即所述终端设备在停止所述InactivityTimer的同时启动或者重启所述ShortCycleTimer。
又由于,当所述终端设备在所述预设时间内未接收到指示唤醒的信号时,网络设备(例如基站)在后续一段时间内不会调度所述终端设备,所述终端此时后续可以不适用短的DRX周期,而使用长的DRX周期,以达到更省电的目的,因此,在一种可选的实施方式中,所述终端设备停止所述InactivityTimer,并且所述终端设备使用长的DRX周期。
在一种可选的实施方式中,所述终端设备在需要使用长的DRX周期的情况下,若ShortCycleTimer正在运行,所述终端设备停止所述ShortCycleTimer,或者,所述终端设备停止并重置所述ShortCycleTimer。这样,所述终端设备可以成功从短的DRX周期切换到长的DRX周期。
在一种可选的实施方式中,所述终端设备停止所述ShortCycleTimer,或者停止并重置所述ShortCycleTimer,具体可以为:所述终端设备在所述预设时间内未接收到指示唤醒的 信号时(或之后),停止所述ShortCycleTimer,或者停止并重置所述ShortCycleTimer;还可以为:所述终端设备在(当前)DRX周期的下一个DRX周期开始时,停止所述ShortCycleTimer,或者停止并重置所述ShortCycleTimer。
在一种可选的实施方式中,若onDurationTimer正在运行,所述终端设备停止所述onDurationTimer。其中,所述onDurationTimer也可以记为drx-onDurationTimer,本申请实施例中仅以所述onDurationTimer为例进行说明。应理解,所述onDurationTimer均可以替换为drx-onDurationTimer。例如,所述终端设备在DRX周期的“On Duration”时间内未接收到指示唤醒的信号,也可以理解为所述预设时间在DRX周期的“On Duration”时间内,此时onDurationTimer可能正在运行,所述终端设备停止所述onDurationTimer。
在一种可选的实施方式中,所述终端设备停止所述onDurationTimer,具体可以为:所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)停止所述onDurationTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述onDurationTimer。
在一种可选的实施方式中,在上述情况a1和情况a3中,所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)停止所述onDurationTimer,具体可以指:所述终端设备在接收到所述休眠信号或者在接收到所述指示信号时(或之后)停止所述onDurationTimer。
在一种可选的实施方式中,若所述onDurationTimer正在运行,所述终端设备还可以重置所述onDurationTimer,即将所述onDurationTimer的值设置为初始值(例如0)。这样在下一次需要开启所述onDurationTimer时,可以使所述onDurationTimer从0开始计时,以免影响正常流程。
在一种可选的实施方式中,所述信号为DCI的情况下,所述终端设备不启动或不重启活动定时器InactivityTimer。具体的,在现有技术中,当终端设备接收到指示新传的DCI(PDCCH)时,终端设备需要启动或重启InactivityTimer,以便接收后续调度的数据,而本实施方式中,由于所述第一消息与数据调度没有直接关系,因此所述终端设备不需要启动或重启InactivityTimer。一种具体的实施方式中,所述信号除了可以指示所述终端设备唤醒或者休眠的事件信息之外,还可以具有其他指示功能。例如,所述信号还可以指示新传,当所述信号为指示新传的DCI的情况下,所述终端设备不启动或不重启InactivityTimer。
采用本申请实施例提供的终端设备的休眠方法,若终端设备在预设时间内未接收到指示唤醒的信号,若InactivityTimer正在运行,所述终端设备停止所述InactivityTimer。可以避免现有技术中若InactivityTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图7所示,该方法的具体流程包括:
步骤701、终端设备在预设时间内监听信号。
具体的,所述步骤701与图3所示的实施例中步骤301类似,具体可以参见上述步骤301中的描述,重复之处此处不再赘述。
步骤702、若所述终端设备在所述预设时间内未接收到指示唤醒的信号,若 RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer。
其中,所述RetransmissionTimer也可以记为drx-RetransmissionTimer,本申请实施例中仅以所述RetransmissionTimer为例进行说明。应理解,所述RetransmissionTimer均可以替换为drx-RetransmissionTimer。
在一种可选的实施方式中,所述终端设备在所述预设时间内未接收到指示唤醒的信号,与图3所示的步骤302中终端设备在预设时间内未接收到指示唤醒的信号相同,具体可以参见上述步骤302中涉及的相关描述,重复之处此处不再赘述。
在一种可选的实施方式中,所述RetransmissionTimer可以为上行重传定时器(RetransmissionTimer(uplink,UL))和下行重传定时器(RetransmissionTimer(downlink,DL))中的一种或多种。其中,所述RetransmissionTimer UL也可以记为drx-RetransmissionTimer UL;所述RetransmissionTimer DL也可以记为drx-RetransmissionTimer DL;本申请实施例中仅以所述RetransmissionTimer UL和RetransmissionTimer DL为例进行说明。应理解,所述RetransmissionTimer UL均可以替换为drx-RetransmissionTimer UL;所述RetransmissionTimer DL均可以替换为drx-RetransmissionTimer DL。
在一种可选的实施方式中,根据所述RetransmissionTimer的具体情况,则若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer,具体可以分为以下三种情况:
情况b1:若RetransmissionTimer UL正在运行,所述终端设备停止所述RetransmissionTimer UL。
情况b2:若RetransmissionTimer DL正在运行,所述终端设备停止所述RetransmissionTimer DL。
情况b3:若RetransmissionTimer UL和RetransmissionTimer DL正在运行,所述终端设备停止所述RetransmissionTimer UL和所述RetransmissionTimer DL。
在一种可选的实施方式中,所述终端设备停止所述RetransmissionTimer,具体可以为:所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)停止所述RetransmissionTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
在一种可选的实施方式中,在上述情况a1和情况a3中,所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)停止所述RetransmissionTimer,具体可以指:所述终端设备在接收到所述休眠信号或者在接收到所述指示信号时(或之后)停止所述RetransmissionTimer。
在一种可选的实施方式中,若所述RetransmissionTimer正在运行,所述终端设备还可以重置所述RetransmissionTimer,即将RetransmissionTimer的值设置为初始值(例如0)。这样在下一次需要开启所述RetransmissionTimer时,可以使所述RetransmissionTimer从0开始计时,以免影响正常流程。
采用本申请实施例提供的终端设备的休眠方法,若终端设备在预设时间内未接收到指示唤醒的信号,若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer。可以避免现有技术中若RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功 耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图8所示,该方法的具体流程包括:
步骤801、终端设备在预设时间内监听信号。
具体的,所述步骤801与图3所示的实施例中步骤301类似,具体可以参见上述步骤301中的描述,重复之处此处不再赘述。
步骤802、若所述终端设备在所述预设时间内未接收到指示唤醒的信号,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。
其中,所述InactivityTimer与图3所示的实施例中涉及的InactivityTimer类似,具体可以参见图3所示的实施例中对InactivityTimer描述,此处不再重复赘述;同理,所述RetransmissionTimer与图7所示的实施例中涉及的RetransmissionTimer类似,具体可以参见图3所示的实施例中对RetransmissionTimer描述,此处不再重复赘述。
在一种可选的实施方式中,所述RetransmissionTimer可以为RetransmissionTimer UL和RetransmissionTimer DL中的一种或多种。因此,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer,具体可以分为以下三种情况:
情况c1:若所述InactivityTimer和所述RetransmissionTimer UL正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer UL。
情况c2:若所述InactivityTimer和所述RetransmissionTimer DL正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer DL。
情况c3:若所述InactivityTimer、所述RetransmissionTimer UL和所述RetransmissionTimer DL正在运行,所述终端设备停止所述InactivityTimer、所述RetransmissionTimer UL和所述RetransmissionTimer DL。
在一种可选的实施方式中,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer,具体可以为:所述终端设备在所述预设时间内未接收到指示唤醒的信号时(或之后)停止所述InactivityTimer和所述RetransmissionTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer和所述RetransmissionTimer。
其中,所述终端设备停止所述InactivityTimer的相关方案与图3所示的实施例中步骤302中涉及的相关方案相似,具体可以相互参见,此处不再一一赘述;以及,所述终端设备停止所述RetransmissionTimer的相关方案与图7所示的实施例中步骤702中涉及的相关方案相似,具体可以相互参见,此处不再一一赘述。
在一种可选的实施方式中,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备还可以重置所述InactivityTimer和所述RetransmissionTimer,即将InactivityTimer和所述RetransmissionTimer的值设置为初始值(例如0)。这样在下一次需要开启所述InactivityTimer和所述RetransmissionTimer时,可以使所述InactivityTimer和所述RetransmissionTimer从0开始计时,以免影响正常流程。
采用本申请实施例提供的终端设备的休眠方法,若终端设备在预设时间内未接收到指 示唤醒的信号,若InactivityTimer和RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。可以避免现有技术中若InactivityTimer和RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图9所示,该方法的具体流程包括:
步骤901、终端设备接收来自通信设备的指示休眠的信号。
其中,所述终端设备可以配置了DRX,也可以没有配置DRX,本实施例对此不作限定。
在一种可选的实施方式中,所述终端设备接收来自所述通信设备的指示休眠的信号,具体可以为:所述终端设备接收来自所述通信设备的休眠信号;或者,所述终端设备接收来自所述通信设备的指示信号,所述指示信号中包含休眠指示信息。其中,所述休眠信号和所述指示信号包含所述休眠指示信息的情况与图3所示的实施例中步骤301中涉及的休眠信号和包含休眠指示信息的信号类似,可以相互参见。
在一种可选的实施方式中,所述指示休眠的信号的形式与图3所示的实施例中指示唤醒的信号的形式类似,具体可以参见步骤301中涉及的信号的形式的相关描述,此处不再一一列举。
在一种可选的实施方式中,所述通信设备可以为网络设备,例如基站,还可以为其他设备,例如终端设备。可选的,当在设备到设备(device-to-device,D2D)场景中,终端设备和终端设备可以直通通信而不需要经过网络设备,此时所述终端设备可以接收另一终端设备发送的信号。
步骤902、所述终端设备启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,所述终端设备在所述休眠定时器运行期间休眠可以包括:所述终端设备在所述休眠定时器运行期间不监听PDCCH。
在一种可选的实施方式中,所述终端设备在所述休眠定时器运行期间休眠还可以包括一下三种方式:
方式d1:所述终端设备在所述休眠定时器运行期间不发送类型0触发的探测参考信号(type-0-triggered(sounding reference signal,SRS))。
方式d2:或者所述终端设备在所述休眠定时器运行期间不上报信道状态信息(channel state information,CSI)。
方式d3:所述终端设备在所述休眠定时器运行期间不发送所述type-0-triggered SRS且不上报所述CSI。
在一种可选的实施方式中,所述终端设备在接收来自所述通信设备的指示休眠的信号之前(即执行上述步骤),所述终端设备还接收所述通信设备配置的休眠时长,例如所述终端设备可以接收RRC消息,所述RRC消息中包含了所述通信设备配置的所述休眠时长。这样所述终端设备后续可以为所述休眠定时器配置所需的休眠时长。需要说明的是,当启动或重启所述休眠定时器时,所述休眠定时器会运行“休眠时长”这么长的时间,当运行了“休眠时长”这么长的时间,则可以认为所述休眠定时器超时。
在一种可选的实施方式中,所述信号中包括指示信息,所述指示信息指示休眠时长。 其中,所述指示信息指示休眠时长可以为:所述指示信息可以直接为所述休眠时长,在这种情况下,所述终端设备可以直接获知所述休眠时长;或者所述指示信息可以指示所述通信设备配置的至少一个时长中的一个,将指示的该时长作为所述休眠时长,例如,当所述通信设备配置了10个时长时,所述指示信息为3时,所述指示信息可以指示所述10个时长中按顺序排列的第三个时长为所述休眠时长。当然,上述举例仅仅为一个示例,所述指示信息还可以通过其它方式指示所述休眠时长,本申请对此不作具体限定。
在一种可选的实施方式中,当所述指示信息指示所述通信设备配置的至少一个时长中的一个时,所述终端设备在接收来自所述通信设备的指示休眠的信号之前,所述终端设备还接收所述通信设备配置的至少一个时长,例如所述终端设备可以接收RRC消息,该RRC消息中包含了所述通信设备配置的所述至少一个时长,所述休眠时长为所述至少一个时长中的一个。
在一种可选的实施方式中,所述终端设备无论通过上述哪种方式获知所述休眠时长之后,在所述终端设备启动或者重启所述休眠定时器之前,所述终端设备还配置所述休眠定时器的定时时长为所述休眠时长。这样所述终端设备可以按需休眠所述休眠时长。
在一种可选的实施方式中,所述休眠时长可以为绝对时间长度,例如N个ms、或N个子帧长度(subframe)、或N个符号长度(symbol)、或N个时隙长度(slot)等、或N个物理下行控制信道监听机会(PDCCH monitoring occasion),N为大于零的数或N为大于零的整数;或者,所述休眠时长可以以DRX周期为单位或者以“On Duration”时间为单位,例如N个DRX周期、或N个“On Duration”时间,N为大于零的整数。当然,上述举例仅仅为一个示例,所述休眠时长还可以为其他时间长度信息,本申请对此不作具体限定。
在一种可选的实施方式中,所述指示休眠的信号为DCI的情况下,所述终端设备不启动或不重启活动定时器InactivityTimer。具体的,在现有技术中,当终端设备接收到指示新传的DCI(PDCCH)时,终端设备需要启动或重启InactivityTimer,以便接收后续调度的数据,而本实施方式中,由于所述第一消息与数据调度没有直接关系,因此所述终端设备不需要启动或重启InactivityTimer。一种具体的实施方式中,所述指示休眠的信号除了可以指示所述终端设备唤醒或者休眠的事件信息之外,还可以具有其他指示功能。例如,所述指示休眠的信号还可以指示新传,当所述指示休眠的信号为指示新传的DCI的情况下,所述终端设备不启动或不重启InactivityTimer。
在一种可选的实施方式中,所述休眠定时器优先级比其它“激活时间”的定时器均高,例如,当onDurationTimer和InactivityTimer正在运行时,只要所述休眠定时器运行,所述终端设备就会休眠;又例如,当所述onDurationTimer、所述InactivityTimer和RetransmissionTimer均正在运行时,只要所述休眠定时器运行,所述终端设备就会休眠。
采用本申请实施例提供的终端设备的休眠方法,终端设备接收来自通信设备的指示休眠的信号后,启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,所述终端设备在所述休眠定时器运行期间休眠包括:所述终端设备在所述休眠定时器运行期间不监听PDCCH。通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图10所示,该方法的具体流程包括:
步骤1001、终端设备监听信号。
在一种可选的实施方式中,所述终端设备可以监听预设时长内的信号;具体的,当所述终端设备监听所述预设时长内的信号时,所述步骤1001与图3所示的实施例中步骤301类似,具体可以参见上述步骤301中的描述,重复之处此处不再赘述。
步骤1002、若所述终端设备接收到指示休眠的信号,若InactivityTimer正在运行,所述终端设备停止所述InactivityTimer。
在一种可选的实施方式中,所述终端设备接收到指示休眠的信号,具体可以包括:所述终端设备接收到休眠信号;或者,所述终端设备接收到指示信号,所述指示信号中包含休眠指示信息。
在一种可选的实施方式中,若所述InactivityTimer正在运行,所述终端设备停止所述InactivityTimer,与图3所示的实施例中步骤302中涉及的若InactivityTimer正在运行,终端设备停止所述InactivityTimer的方法类似,具体可以参见上述步骤302中涉及的相关描述,此处不再重复赘述。
采用本申请实施例提供的终端设备的休眠方法,若终端设备接收到指示休眠的信号,若InactivityTimer正在运行,所述终端设备停止所述InactivityTimer。可以避免现有技术中若InactivityTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图11所示,该方法的具体流程包括:
步骤1101、终端设备监听信号。
在一种可选的实施方式中,所述终端设备可以监听预设时长内的信号;具体的,当所述终端设备监听所述预设时长内的信号时,所述步骤1101与图3所示的实施例中步骤301类似,具体可以参见上述步骤301中的描述,重复之处此处不再赘述。
步骤1102、若所述终端设备接收到指示休眠的信号,若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer。
在一种可选的实施方式中,所述终端设备接收到指示休眠的信号与上述步骤1001中涉及的终端设备接收到指示休眠的信号的情况相同,具体可以相互参见,此处不再重复赘述。
在一种可选的实施方式中,若所述RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer,与图7所示的实施例中步骤702中涉及的相关方法类似,具体可以参见上述步骤702中涉及的相关描述,此处不再重复赘述。
采用本申请实施例提供的终端设备的休眠方法,若终端设备接收到指示唤醒的信号,若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer。可以避免现有技术中若RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图12所示,该方法的具体流程包括:
步骤1201、终端设备监听信号。
在一种可选的实施方式中,所述终端设备可以监听预设时长内的信号;具体的,当所述终端设备监听所述预设时长内的信号时,所述步骤1101与图3所示的实施例中步骤301类似,具体可以参见上述步骤301中的描述,重复之处此处不再赘述。
步骤1202、若所述终端设备接收到指示休眠的信号,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。
在一种可选的实施方式中,所述终端设备接收到指示休眠的信号与上述步骤1001中涉及的终端设备接收到指示休眠的信号的情况相同,具体可以相互参见,此处不再重复赘述。
在一种可选的实施方式中,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer,与图8所示的实施例中步骤802中涉及的相关方法类似,具体可以参见上述步骤802中涉及的相关描述,此处不再重复赘述。
采用本申请实施例提供的终端设备的休眠方法,若终端设备接收到指示休眠的信号,若InactivityTimer和RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。可以避免现有技术中若InactivityTimer和RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图13所示,该方法的具体流程包括:
步骤1301、终端设备接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器。
其中,所述终端设备配置了DRX,也就是说所述终端设备采用图1所示的DRX周期,在DRX周期中的On Duration内监听并接收PDCCH,在Opportunity for DRX时间内所述终端设备可以不监听或不接收PDCCH以减少功耗。所述特定定时器可以为:onDurationTimer、InactivityTimer和RetransmissionTimer(RetransmissionTimerUL和/或RetransmissionTimerDL)中的一种或多种。需要说明的是,所述指示消息可以是一条新的消息,也可以复用现有的消息(或信令)、在现有消息(或信令)已有功能的基础上加上了“指示终端设备停止特定定时器”的功能,也就是说,所述指示消息除了“指示所述终端设备停止特定定时器”的能力、还可以有其他功能,本申请不做限定。例如,所述指示消息可以复用现有的长DRX控制MAC CE(Long DRX Command MAC CE),或者,所述指示消息可以复用现有的DRX控制MAC CE(DRX Command MAC CE)。
在一种可选的实施方式中,所述终端设备可以接收来自通信设备的指示消息,例如图中所示,可选的,所述通信设备可以为网络设备,例如基站等,或者可以为其他设备,例如终端设备等。
在一种可选的实施方式中,所述指示消息的形式可以为一种物理层序列,或DCI,或MAC CE,或MAC PDU。
在一种可选的实施方式中,所述终端设备可以在使用长的DRX周期时,接收所述指示消息。在一种可选的实施方式中,在之后的流程中,所述终端设备继续使用所述长的DRX 周期。此时,所述终端设备接收所述指示消息,不是为了更换DRX周期,主要是为了停止onDurationTimer、InactivityTimer、RetransmissionTimer中的一个或多个,即所述终端设备可以立即休眠,以达到更省电的目的。例如,当网络设备发现后续没有数据需要发送给所述终端设备,网络设备可以发送所述指示消息给所述终端设备,指示终端设备可以立即休眠。需要说明的是,在其他可选的实施方式中,还可以为:所述终端设备在使用长的DRX周期时接收所述指示消息,并且在所述终端设备接收指示消息之后,所述终端设备使用短的DRX周期;或者,所述终端设备在使用短的DRX周期时接收所述指示消息,并且在所述终端设备接收所述指示消息之后,所述终端设备继续使用短的DRX周期;所述终端设备在使用短的DRX周期时接收所述指示消息,并且在所述终端设备接收指示消息之后,所述终端设备使用长的DRX周期。
在一种可选的实施方式中,所述终端设备在使用短的DRX周期时接收所述指示消息,并且在所述终端设备接收所述指示消息之后,所述终端设备继续使用短的DRX周期,还包括:所述终端设备不启动或不重启短周期定时器ShortCycleTimer。此时,所述终端设备接收所述指示消息,不是为了更换DRX周期,也不想延长短的DRX周期的使用时间,主要是为了停止onDurationTimer、InactivityTimer、RetransmissionTimer中的一个或多个,即所述终端设备可以立即休眠,以达到更省电的目的。若此时终端设备启动或重启短周期定时器ShortCycleTimer,则导致终端设备处于短的DRX周期的时间段变长,需要更长的时间才能进入长的DRX周期,不利于省电。因此,终端设备不启动或不重启短周期定时器ShortCycleTimer,使周期定时器ShortCycleTimer继续计时,以尽快进入长的DRX周期,以达到更省电的目的。
需要说明的是,若复用现有的消息(或信令),例如DRX控制MAC CE(DRX Command MAC CE),并在现有消息(或信令)已有功能的基础上加上了“不启动或不重启短周期定时器ShortCycleTimer”的功能。一种可能的方式,可以在现有的消息(或信令)中增加指示域,所述指示域指示是否需要启动或重启短周期定时器ShortCycleTimer,例如,当指示域取值为第一值时,指示需要启动或重启短周期定时器ShortCycleTimer,当指示域取值为第二值时,指示不启动或不重启短周期定时器ShortCycleTimer。
步骤1302、若onDurationTimer正在运行,所述终端设备停止所述onDurationTimer。
在一种可选的实施方式中,所述终端设备停止所述onDurationTimer,具体可以为:所述终端设备在接收到所述指示消息时停止所述onDurationTimer,或者,所述终端设备在接收到所述指示消息后停止所述onDurationTimer。
在一种可选的实施方式中,若所述onDurationTimer正在运行,所述终端设备还可以重置所述onDurationTimer(所述终端设备停止并重置所述onDurationTimer),即将所述onDurationTimer的值设置为初始值(例如0),这样在下一次需要开启所述onDurationTimer时,可以使所述onDurationTimer从0开始计时,以免影响正常流程。
在一种可选的实施方式中,若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;其中,所述RetransmissionTimer可以为RetransmissionTimerUL和RetransmissionTimerDL中的一种或多种。其中,所述RetransmissionTimer UL也可以记为drx-RetransmissionTimer UL;所述RetransmissionTimer DL也可以记为drx-RetransmissionTimer DL;本申请实施例中仅以所述RetransmissionTimer UL和RetransmissionTimer DL为例进行说明。应理解,所述RetransmissionTimer UL均可以替换 为drx-RetransmissionTimer UL;所述RetransmissionTimer DL均可以替换为drx-RetransmissionTimer DL。
在一种可选的实施方式中,根据所述RetransmissionTimer的具体情况,则若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer,具体可以分为以下三种情况:
情况d1:若RetransmissionTimer UL正在运行,所述终端设备停止所述RetransmissionTimer UL。
情况d2:若RetransmissionTimer DL正在运行,所述终端设备停止所述RetransmissionTimer DL。
情况d3:若RetransmissionTimer UL和RetransmissionTimer DL正在运行,所述终端设备停止所述RetransmissionTimer UL和所述RetransmissionTimer DL。
在一种可选的实施方式中,所述终端设备停止所述RetransmissionTimer,具体可以为:所述终端设备在接收到所述指示消息时停止所述RetransmissionTimer,或者,所述终端设备在接收到所述指示消息后停止所述RetransmissionTimer。
在一种可选的实施方式中,若所述RetransmissionTimer正在运行,所述终端设备还可以重置所述RetransmissionTimer(所述终端设备停止并重置所述RetransmissionTimer),即将所述RetransmissionTimer的值设置为初始值(例如0),这样在下一次需要开启所述RetransmissionTimer时,可以使所述RetransmissionTimer从0开始计时,以免影响正常流程。
采用本申请实施例提供的终端设备的休眠方法,若终端设备接收到指示消息,若onDurationTimer正在运行,所述终端设备停止所述onDurationTimer。可以使网络设备在确定终端设备后续没有数据传输时及时停止onDurationTimer,从而使终端设备进入休眠、不需要再保持唤醒来接收消息。也就是说通过上述方法可以使终端设备及时进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图14所示,该方法的具体流程包括:
步骤1401、终端设备接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器,其中,所述终端设备配置了DRX。
具体的,所述步骤1401与图13所示的实施例中步骤1301类似,具体可以参见上述步骤1301中的描述,重复之处此处不再赘述。
步骤1402、若InactivityTimer正在运行,所述终端设备停止所述InactivityTimer。
在一种可选的实施方式中,所述终端设备停止所述InactivityTimer,具体可以为:所述终端设备在接收到所述指示消息时停止所述InactivityTimer,或者,所述终端设备在接收到所述指示消息后停止所述InactivityTimer。
在一种可选的实施方式中,若所述InactivityTimer正在运行,所述终端设备还可以重置所述InactivityTimer(所述终端设备停止并重置所述InactivityTimer),即将所述InactivityTimer的值设置为初始值(例如0),这样在下一次需要开启所述InactivityTimer时,可以使所述InactivityTimer从0开始计时,以免影响正常流程。
在一种可选的实施方式中,若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;其中,所述RetransmissionTimer可以为RetransmissionTimerUL和RetransmissionTimerDL中的一种或多种。其中,RetransmissionTimer的详细介绍以及对所 述终端设备停止所述RetransmissionTimer的详细介绍可以参见上述图13所示的实施例中步骤1302中涉及的相关描述,重复之处此处不再赘述。
采用本申请实施例提供的终端设备的休眠方法,若终端设备接收到指示消息,若InactivityTimer正在运行,所述终端设备停止所述InactivityTimer。可以使网络设备在确定终端设备后续没有数据传输时及时停止InactivityTimer,从而使终端设备进入休眠、不需要再保持唤醒来接收消息。也就是说通过上述方法可以使终端设备及时进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的休眠方法,适用于如图2所示的通信系统。参阅图15所示,该方法的具体流程包括:
步骤1501、终端设备接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器,其中,所述终端设备配置了DRX。
具体的,所述步骤1501与图13所示的实施例中步骤1301类似,具体可以参见上述步骤1301中的描述,重复之处此处不再赘述。
步骤1502、若所述onDurationTimer和所述InactivityTimer正在运行,所述终端设备停止所述onDurationTimer和所述InactivityTimer。
在一种可选的实施方式中,所述终端设备停止所述onDurationTimer和所述InactivityTimer,具体可以参见上述步骤1302中所述终端设备停止所述onDurationTimer涉及的相关描述,以及上述步骤1402中所述终端设备停止所述InactivityTimer涉及的相关描述,此处不再重复赘述。
在一种可选的实施方式中,若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;其中,所述RetransmissionTimer可以为RetransmissionTimerUL和RetransmissionTimerDL中的一种或多种。其中,RetransmissionTimer的详细介绍以及对所述终端设备停止所述RetransmissionTimer的详细介绍可以参见上述图13所示的实施例中步骤1302中涉及的相关描述,重复之处此处不再赘述。
采用本申请实施例提供的终端设备的休眠方法,若终端设备接收到指示消息,若onDurationTimer和InactivityTimer正在运行,所述终端设备停止所述onDurationTimer和InactivityTimer。可以使网络设备在确定终端设备后续没有数据传输时及时停止onDurationTimer和InactivityTimer,从而使终端设备进入休眠、不需要再保持唤醒来接收消息。也就是说通过上述方法可以使终端设备及时进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
上述本申请提供的实施例中,分别从各个网元或者设备之间交互的角度对本申请实施例提供的终端设备的休眠方法的各方案进行了介绍。可以理解的是,各个网元和设备,例如上述终端设备为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本申请中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
例如,当本申请提供的终端设备通过软件模块来实现相应的功能时,所述终端设备可 以包括接收单元1601和处理单元1602,具体可以参考如图16所示的结构示意图。
在一个实施例中,图16所示终端设备可用于执行上述图3、图7、图8所示的实施例中的终端设备的操作。例如:
所述接收单元1601,用于接收信号;所述处理单元1602,用于若所述接收单元1601在预设时间内未接收到指示唤醒的信号,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
在一种可选的实施方式中,所述接收单元1601在预设时间内未接收到指示唤醒的信号,具体用于:在预设时间内接收到休眠信号;或者在预设时间内未接收到唤醒信号;或者在预设时间内接收到指示信号,所述指示信号中包含休眠指示信息。
在一种可选的实施方式中,所述处理单元1602停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
在一种可选的实施方式中,所述处理单元1602停止所述RetransmissionTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
在一种可选的实施方式中,所述处理单元1602还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
在一种可选的实施方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
在一种可选的实施方式中,所述处理单元1602还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
在一种可选的实施方式中,所述处理单元1602还用于停止所述InactivityTimer,并且使用长的DRX周期。
在一种可选的实施方式中,所述处理单元1602还用于若短周期定时器ShortCycleTimer正在运行,停止所述ShortCycleTimer,或者,停止并重置所述ShortCycleTimer。
基于上述终端设备,若终端设备在预设时间内未接收到指示唤醒的信号,若InactivityTimer和/或RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和/或所述RetransmissionTimer。可以避免现有技术中若InactivityTimer和/或RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
在另一个实施例中,图16所示终端设备还可用于执行上述图9所示的实施例中的终端设备的操作。例如:
所述接收单元1601,用于接收来自通信设备的指示休眠的信号;所述处理单元1602,用于启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,在所述休眠定时器运行期间休眠包括:在所述休眠定时器运行期间不监听物理下行控制信道PDCCH。
在一种可选的实施方式中,所述处理单元1602在所述休眠定时器运行期间休眠还包括:
在所述休眠定时器运行期间不发送类型0触发的探测参考信号type-0-triggered SRS;或者在所述休眠定时器运行期间不上报信道状态信息CSI;或者在所述休眠定时器运行期间不发送所述type-0-triggered SRS且不上报所述CSI。
在一种可选的实施方式中,所述接收单元1601接收来自所述通信设备的指示休眠的信号,具体用于:接收来自所述通信设备的休眠信号;或者接收来自所述通信设备的指示信号,所述指示信号中包含休眠指示信息。
在一种可选的实施方式中,所述接收单元1601在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的休眠时长。
在一种可选的实施方式中,所述信号中包括指示信息,所述指示信息指示休眠时长。
在一种可选的实施方式中,所述接收单元1601在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的至少一个时长,所述休眠时长为所述至少一个时长中的一个。
在一种可选的实施方式中,所述处理单元1602在启动或重启休眠定时器之前,还用于配置所述休眠定时器的定时时长为所述休眠时长。
基于上述终端设备,接收来自通信设备的指示休眠的信号后,启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,所述终端设备在所述休眠定时器运行期间休眠包括:所述终端设备在所述休眠定时器运行期间不监听PDCCH。通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
在另一个实施例中,图16所示终端设备还可用于执行上述图10、图11、图12所示的实施例中的终端设备的操作。例如:
所述接收单元1601,用于接收信号;所述处理单元1602,用于若所述接收单元1601接收到指示休眠的信号,若活动定时器InactivityTimer正在运行,所述终端设备停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
在一种可选的实施方式中,所述接收单元1601接收到指示休眠的信号,具体用于:接收到休眠信号;或者接收到指示信号,所述指示信号中包含休眠指示信息。
在一种可选的实施方式中,所述处理单元1602停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
在一种可选的实施方式中,所述处理单元1602停止所述RetransmissionTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
在一种可选的实施方式中,所述处理单元1602还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
在一种可选的实施方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
在一种可选的实施方式中,所述处理单元1602还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
在一种可选的实施方式中,所述处理单元1602还用于停止所述InactivityTimer,并且使用长的DRX周期。
在一种可选的实施方式中,所述处理单元1602还用于若ShortCycleTimer正在运行,停止所述ShortCycleTimer,或者,停止并重置所述ShortCycleTimer。
基于上述终端设备,若终端设备接收到指示休眠的信号,若InactivityTimer和/或RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和/或所述RetransmissionTimer。可以避免现有技术中若InactivityTimer和/或RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
在另一个实施例中,图16所示终端设备还可用于执行上述图13、图14、图15所示的实施例中的终端设备的操作。例如:
所述接收单元1601,用于接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器,其中,所述终端设备配置了非连续接收DRX;
所述处理单元1602,用于若持续定时器onDurationTimer正在运行,停止所述onDurationTimer;或者,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若所述onDurationTimer和所述InactivityTimer正在运行,停止所述onDurationTimer和所述InactivityTimer。
在一种可选的实施方式中,所述处理单元1602还用于:若所述onDurationTimer正在运行,还重置所述onDurationTimer;或者,若所述InactivityTimer正在运行,还重置所述InactivityTimer。
在一种可选的实施方式中,所述处理单元1602还用于:若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer,其中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
在一种可选的实施方式中,所述处理单元1602还用于:若所述RetransmissionTimer正在运行,还重置所述RetransmissionTimer。
在一种可选的实施方式中,所述指示消息为物理层序列、或DCI、或MAC CE、或MAC PDU。
在一种可选的实施方式中,所述接收单元1601接收指示消息,具体用于所述处理单元1602在使用长的DRX周期时,接收所述指示消息。
在一种可选的实施方式中,所述处理单元1602还用于继续使用所述长的DRX周期。
在一种可选的实施方式中,所述接收单元1601接收指示消息,具体用于所述处理单元1602在使用短的DRX周期时,接收所述指示消息。
在一种可选的实施方式中,所述处理单元1602还用于继续使用所述短的DRX周期。
在一种可选的实施方式中,所述处理单元1602还用于不启动或不重启短周期定时器ShortCycleTimer。
基于上述终端设备,接收到指示消息,若onDurationTimer和/或InactivityTimer正在运行,所述终端设备停止所述onDurationTimer和/或InactivityTimer。可以使网络设备在确定终端设备后续没有数据传输时及时停止onDurationTimer和/或InactivityTimer,从而使终端设备进入休眠、不需要再保持唤醒来接收消息。也就是说通过上述方法可以使终端设备及时进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
需要说明的是,本申请实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
又例如,当上述终端设备通过硬件来实现相应的功能时,所述终端设备可以包括收发器1701和处理器1702,可选的还可以包括存储器1703,具体可以参考如图17所示结构图。应理解所述终端设备可以包括至少一个处理器和至少一个存储器,图17中仅示例性的示出了一个处理器和一个存储器。
其中,处理器1702可以是中央处理器(central processing unit,CPU),网络处理器(network processor,NP)或者CPU和NP的组合等等。处理器1702还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit,ASIC),可编程逻辑器件(programmable logic device,PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device,CPLD),现场可编程逻辑门阵列(field-programmable gate array,FPGA),通用阵列逻辑(generic array logic,GAL)或其任意组合。处理器1702在实现上述功能时,可以通过硬件实现,当然也可以通过硬件执行相应的软件实现。
收发器1701和处理器1702之间相互连接。可选的,收发器1701和处理器1702通过总线1704相互连接;总线1704可以是外设部件互连标准(Peripheral Component Interconnect,PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture,EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示,图17中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
在一个实施例中,图17所示的终端设备可用于执行上述图3、图7、图8所示的实施例中的终端设备的操作。例如:
所述收发器1701用于在接收到所述处理器1702的调用时收发信号;所述处理器1702 用于若所述收发器1701在预设时间内未接收到指示唤醒的信号时,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
在一种可选的实施方式中,所述收发器1701在预设时间内未接收到指示唤醒的信号,具体用于:在预设时间内接收到休眠信号;或者在预设时间内未接收到唤醒信号;或者在预设时间内接收到指示信号,所述指示信号中包含休眠指示信息。
在一种可选的实施方式中,所述处理器1702停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
在一种可选的实施方式中,所述处理器1702停止所述RetransmissionTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
在一种可选的实施方式中,所述处理器1702还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
在一种可选的实施方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
在一种可选的实施方式中,所述处理器1702还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
在一种可选的实施方式中,所述处理器1702还用于停止所述InactivityTimer,并且使用长的DRX周期。
在一种可选的实施方式中,所述处理器1702还用于若短周期定时器ShortCycleTimer正在运行,停止所述ShortCycleTimer,或者,停止并重置所述ShortCycleTimer。
在一种可选的实施方式中,存储器1703,与处理器1702耦合,用于存放程序等。具体地,程序可以包括程序代码,该程序代码包括计算机操作指令。存储器1703可能包括RAM,也可能还包括非易失性存储器(non-volatile memory),例如至少一个磁盘存储器。处理器1702执行存储器1703所存放的应用程序,实现上述功能,从而实现如图3、图7、图8所示的终端设备的休眠方法。
基于上述终端设备,若终端设备在预设时间内未接收到指示唤醒的信号,若InactivityTimer和/或RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和/或所述RetransmissionTimer。可以避免现有技术中若InactivityTimer和/或RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
在另一个实施例中,图17所示终端设备还可用于执行上述图9所示的实施例中的终端设备的操作。例如:
所述收发器1701用于在接收到所述处理器1702的调用时接收来自通信设备的指示休眠的信号;所述处理器1702,用于启动或重启休眠定时器,并在所述休眠定时器运行期间 休眠;其中,在所述休眠定时器运行期间休眠包括:在所述休眠定时器运行期间不监听PDCCH。
在一种可选的实施方式中,所述处理器1702在所述休眠定时器运行期间休眠还包括:
在所述休眠定时器运行期间不发送类型0触发的探测参考信号type-0-triggered SRS;或者在所述休眠定时器运行期间不上报信道状态信息CSI;或者在所述休眠定时器运行期间不发送所述type-0-triggered SRS且不上报所述CSI。
在一种可选的实施方式中,所述收发器1701接收来自所述通信设备的指示休眠的信号,具体用于:接收来自所述通信设备的休眠信号;或者接收来自所述通信设备的指示信号,所述指示信号中包含休眠指示信息。
在一种可选的实施方式中,所述收发器1701在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的休眠时长。
在一种可选的实施方式中,所述信号中包括指示信息,所述指示信息指示休眠时长。
在一种可选的实施方式中,所述收发器1701在接收来自所述通信设备的指示休眠的信号之前,还用于接收所述通信设备配置的至少一个时长,所述休眠时长为所述至少一个时长中的一个。
在一种可选的实施方式中,所述处理器1702在启动或重启休眠定时器之前,还用于配置所述休眠定时器的定时时长为所述休眠时长。
在一种可选的实施方式中,存储器1703,与处理器1702耦合,用于存放程序等。具体地,程序可以包括程序代码,该程序代码包括计算机操作指令。存储器1703可能包括RAM,也可能还包括非易失性存储器(non-volatile memory),例如至少一个磁盘存储器。处理器1702执行存储器1703所存放的应用程序,实现上述功能,从而实现如图9所示的终端设备的休眠方法。
基于上述终端设备,接收来自通信设备的指示休眠的信号后,启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;其中,所述终端设备在所述休眠定时器运行期间休眠包括:所述终端设备在所述休眠定时器运行期间不监听PDCCH。通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
在另一个实施例中,图17所示终端设备还可用于执行上述图10、图11、图12所示的实施例中的终端设备的操作。例如:
所述收发器1701,用于在接收到所述处理器1702的调用时接收信号;所述处理器1702,用于若所述收发器1701接收到指示休眠的信号,若活动定时器InactivityTimer正在运行,所述终端设备停止所述InactivityTimer;或者,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer;或者,若所述InactivityTimer和所述RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和所述RetransmissionTimer。其中,所述终端设备配置了非连续接收DRX。
在一种可选的实施方式中,所述收发器1701接收到指示休眠的信号,具体用于:接收到休眠信号;或者接收到指示信号,所述指示信号中包含休眠指示信息。
在一种可选的实施方式中,所述处理器1702停止所述InactivityTimer,具体用于在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。
在一种可选的实施方式中,所述处理器1702停止所述RetransmissionTimer,具体用于 在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
在一种可选的实施方式中,所述处理器1702还用于:若所述InactivityTimer正在运行,重置所述InactivityTimer;或者若所述RetransmissionTimer正在运行,重置所述RetransmissionTimer;或者若所述InactivityTimer和所述RetransmissionTimer正在运行,重置所述InactivityTimer和所述RetransmissionTimer。
在一种可选的实施方式中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
在一种可选的实施方式中,所述处理器1702还用于停止所述InactivityTimer,并且启动或者重启短周期定时器ShortCycleTimer。
在一种可选的实施方式中,所述处理器1702还用于停止所述InactivityTimer,并且使用长的DRX周期。
在一种可选的实施方式中,所述处理器1702还用于若ShortCycleTimer正在运行,停止所述ShortCycleTimer,或者,停止并重置所述ShortCycleTimer。
在一种可选的实施方式中,存储器1703,与处理器1702耦合,用于存放程序等。具体地,程序可以包括程序代码,该程序代码包括计算机操作指令。存储器1703可能包括RAM,也可能还包括非易失性存储器(non-volatile memory),例如至少一个磁盘存储器。处理器1702执行存储器1703所存放的应用程序,实现上述功能,从而实现如图10、图11、图12所示的终端设备的休眠方法。
基于上述终端设备,若终端设备接收到指示休眠的信号,若InactivityTimer和/或RetransmissionTimer正在运行,所述终端设备停止所述InactivityTimer和/或所述RetransmissionTimer。可以避免现有技术中若InactivityTimer和/或RetransmissionTimer正在运行时,即使指示终端设备休眠时,终端设备也需要保持一段时间的激活,直至定时器结束的情况。也就是说通过上述方法可以使终端设备真正进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
在另一个实施例中,图17所示终端设备还可用于执行上述图13、图14、图15所示的实施例中的终端设备的操作。例如:
所述收发器1701,用于在接收到所述处理器1702的调用时接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器,其中,所述终端设备配置了非连续接收DRX;
所述处理器1702,用于若持续定时器onDurationTimer正在运行,停止所述onDurationTimer;或者,若活动定时器InactivityTimer正在运行,停止所述InactivityTimer;或者,若所述onDurationTimer和所述InactivityTimer正在运行,停止所述onDurationTimer和所述InactivityTimer。
在一种可选的实施方式中,所述处理器1702还用于:若所述onDurationTimer正在运行,还重置所述onDurationTimer;或者,若所述InactivityTimer正在运行,还重置所述InactivityTimer。
在一种可选的实施方式中,所述处理器1702还用于:若重传定时器RetransmissionTimer正在运行,停止所述RetransmissionTimer,其中,所述RetransmissionTimer为上行重传定时器RetransmissionTimerUL和下行重传定时器RetransmissionTimerDL中的一种或多种。
在一种可选的实施方式中,所述处理器1702还用于:若所述RetransmissionTimer正在运行,还重置所述RetransmissionTimer。
在一种可选的实施方式中,所述指示消息为物理层序列、或DCI、或MAC CE、或MAC PDU。
在一种可选的实施方式中,所述收发器1701接收指示消息,具体用于所述处理器1702在使用长的DRX周期时,接收所述指示消息。
在一种可选的实施方式中,所述处理器1702还用于继续使用所述长的DRX周期。
在一种可选的实施方式中,所述收发器1701接收指示消息,具体用于所述处理器1702在使用短的DRX周期时,接收所述指示消息。
在一种可选的实施方式中,所述处理器1702还用于继续使用所述短的DRX周期。
在一种可选的实施方式中,所述处理器1702还用于不启动或不重启短周期定时器ShortCycleTimer。
在一种可选的实施方式中,存储器1703,与处理器1702耦合,用于存放程序等。具体地,程序可以包括程序代码,该程序代码包括计算机操作指令。存储器1703可能包括RAM,也可能还包括非易失性存储器(non-volatile memory),例如至少一个磁盘存储器。处理器1702执行存储器1703所存放的应用程序,实现上述功能,从而实现如图13、图14、图15所示的终端设备的休眠方法。
基于上述终端设备,接收到指示消息,若onDurationTimer和/或InactivityTimer正在运行,所述终端设备停止所述onDurationTimer和/或InactivityTimer。可以使网络设备在确定终端设备后续没有数据传输时及时停止onDurationTimer和/或InactivityTimer,从而使终端设备进入休眠、不需要再保持唤醒来接收消息。也就是说通过上述方法可以使终端设备及时进行休眠,从而可以更好的节省功耗,可以满足节省功耗的需求。
基于上述实施例,本申请实施例还提供了一种终端设备的状态指示方法,适用于如图2所示的通信系统。参阅图18所示,该方法的具体流程包括:
步骤1801、终端设备接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息。
在一种可选的实施方式中,所述通信设备可以为网络设备,例如基站等,或者可以为其他设备,例如终端设备等。
在一种可选的实施方式中,所述第一消息本身可以指示所述终端设备唤醒或者休眠,同时所述第一消息关联着所述时间信息,从而可以实现所述第一消息指示所述终端设备唤醒或者休眠的时间信息。示例性的,通信设备可以通过广播消息或RRC专用消息或其他消息将所述第一消息关联的所述时间信息配置给所述终端设备,或者所述第一消息关联的所述时间信息还可以预先设置好并储存在所述终端设备中。例如,所述第一消息可以为唤醒信号(wake-up signal),则所述第一消息可以指示所述终端设备唤醒,结合所述第一消息关联的所述时间信息,所述第一消息可以指示所述终端设备唤醒的时间信息;又例如,所述第一消息可以为休眠信号(go-to-sleep signal),则所述第一消息可以指示所述终端设备休眠,结合所述第一消息关联的所述时间信息,所述第一消息可以指示所述终端设备休眠的时间信息。
在另一种可选的实施方式中,所述第一消息可以包括第一指示信息,所述第一指示信 息指示所述时间信息。在该实施方式中,所述第一消息本身可以指示所述终端设备唤醒或者休眠,所述第一消息中包括的所述第一指示信息用于指示所述时间信息,结合所述第一消息本身的属性和所述第一消息中的所述第一指示信息,所述第一消息即可指示所述终端设备唤醒或者休眠的时间信息。例如,所述第一消息为唤醒信号(wake-up signal),则所述第一消息可以指示终端设备唤醒,结合第一消息中的所述第一指示信息,所述第一消息可以指示所述终端设备唤醒的时间信息;又例如,所述第一消息为休眠信号(go-to-sleep signal),则所述第一消息可以指示终端设备休眠,结合所述第一消息中的所述第一指示信息,所述第一消息可以指示所述终端设备休眠的时间信息。
在又一种可选的实施方式中,所述第一消息可以包括第二指示信息,所述第二指示信息指示所述终端设备唤醒或者休眠。在该实施方式中,所述第一消息本身可以关联着所述时间信息,如通信设备通过广播消息或RRC专用消息或其他消息将所述第一消息关联的所述时间信息配置给所述终端设备,或者所述第一消息关联的所述时间信息可以预先设置好并储存在所述终端设备中。例如,所述第一消息中的所述第二指示信息指示所述终端设备唤醒,结合所述第一消息关联的所述时间信息,所述第一消息可以指示所述终端设备唤醒的时间信息;又例如,所述第一消息中的所述第二指示信息指示所述终端设备休眠,结合所述第一消息关联的所述时间信息,所述第一消息可以指示所述终端设备休眠的时间信息。
在又一种可选的实施方式中,所述第一消息可以包括第一指示信息和第二指示信息,所述第一指示信息指示所述时间信息,所述第二指示信息指示所述终端设备唤醒或者休眠。在该实施方式中,所述第一消息本身无法指示终端设备唤醒或者休眠,结合所述第一消息中的所述第二指示信息和所述第一指示信息,所述第一消息即可指示所述终端设备唤醒或者休眠的时间信息。例如,所述第一消息中的所述第二指示信息指示所述终端设备唤醒,结合所述第一消息中的所述第一指示信息,所述第一消息可以指示所述终端设备唤醒的时间信息;又例如,所述第一消息中的所述第二指示信息指示所述终端设备休眠,结合所述第一消息中的所述第一指示信息,所述第一消息可以指示所述终端设备休眠的时间信息。
在一种可选的实施方式中,所述时间信息可以为所述终端设备唤醒或者休眠的时间长度。可以理解为:所述终端设备接收到所述第一消息时(或之后)维持唤醒或休眠的时间长度。例如,从所述终端设备接收到所述第一消息时(或之后)开始、一直到唤醒的时间长度结束这段时间,所述终端设备处于唤醒;又例如,从所述终端设备接收到所生第一消息时(或之后)开始、一直到休眠的时间长度结束这段时间,所述终端设备处于休眠。需要说明的是,所述终端设备基于所述第一消息开始唤醒或休眠的时间点可以是接收到所述第一消息时(或之后)立即开始的时刻,也可以是其他预先规定好的时间点,所述终端设备唤醒或者休眠的时间长度可以从该开始唤醒或休眠的时间点开始计算,本申请对此不做限定。
在另一种可选的实施方式中,所述时间信息可以为所述终端设备唤醒或者休眠之前的时间长度。可以理解为:所述终端设备接收到所述第一消息时(或之后)到开始唤醒或休眠的时间长度,即所述终端设备接收到所述第一消息时(或之后)并不是立即唤醒或休眠,而是在一个时间段(即所述时间长度)后才唤醒或休眠。
在又一种可选的实施方式中,所述时间信息可以为所述终端设备唤醒或者休眠结束的时间。可以理解为:所述终端设备接收到所述第一消息时(或之后)唤醒或休眠结束的时间点。例如,从所述终端设备接收到所述第一消息时(或之后)开始唤醒、并维持唤醒到 唤醒结束的时间,或者,从所述终端设备接收到所述第一消息时(或之后)开始休眠、并维持休眠到休眠结束的时间。需要说明的是,所述终端设备基于所述第一消息开始唤醒或休眠的时间可以是接收到所述第一消息时(或之后)立即开始,也可以是其他预先规定好的时间点,所述终端设备唤醒或者休眠的时间长度可以从该开始唤醒或休眠的时间点开始计算,本申请对此不做限定。
在一种可选的实施方式中,上述涉及的所述时间长度可以为一个或多个毫秒;或者,所述时间长度可以为一个或多个子帧;或者,所述时间长度可以为一个或多个时隙;或者,所述时间长度可以为一个或多个DRX周期;或者,所述时间长度可以为一个或多个On Duration;或者,所述时间长度可以为一个或多个寻呼机会;或者,所述时间长度可以为一个或多个PDCCH监听机会;或者,所述时间长度可以为以毫秒为单位的时间长度;或者,所述时间长度可以为以子帧为单位的时间长度;或者,所述时间长度可以为以时隙为单位的时间长度;或者,所述时间长度可以为以DRX周期为单位的时间长度;或者,所述时间长度可以为以On Duration个数为单位的时间长度;或者,所述时间长度可以为以寻呼机会为单位的时间长度;或者,所述时间长度可以为以PDCCH监听机会为单位的时间长度。例如,所述时间长度为一个或多个“某某”,以及所述时间长度为以“某某”为单位的时间长度,在一定场景中两者可以认为是等同的。其中,“某某”为上述涉及的毫秒等等。例如,所述时间长度为一个或多个On Duration或以On Duration个数为单位的时间长度时,所述时间长度可以为N(N为大于或等于1的整数)个On Duration,表示从开始唤醒或休眠的时间开始,所述终端设备在后续N个On Duration都唤醒或休眠。
在一种可选的实施方式中,所述第一指示信息指示所述时间信息具体可以为所述第一指示信息指示所述时间信息的值。例如,所述第一指示信息指示所述终端设备唤醒或者休眠的时间长度的值(如N个毫秒、N个Duration等,N为大于或等于1的整数)。又例如,所述第一指示信息指示所述终端设备唤醒或者休眠之前的时间长度的值(如N个毫秒、N个Duration等)。又例如,所述第一指示信息指示所述终端设备唤醒或者休眠结束的时间点的值。
在另一种可选的实施方式中,所述第一指示信息指示所述时间信息具体可以为所述第一指示信息指示索引值,所述索引值对应所述时间信息的值。例如,所述索引值对应所述终端设备唤醒或者休眠的时间长度的值(如N个毫秒、N个Duration等);或者所述索引值对应终端设备唤醒或者休眠之前的时间长度的值(如N个毫秒、N个Duration等);或者所述索引值对应终端设备唤醒或者休眠结束的时间点的值。其中,所述索引值和所述时间信息的值的对应关系可以由通信设备预先配置给所述终端设备。如通信设备可以通过广播消息或RRC专用消息或其他消息配置给所述终端设备,或者所述索引值和所述时间信息的值的对应关系可以预先设置好并储存在所述终端设备中。例如,索引值{1,2,3}分别对应时间信息的值{a,b,c},当所述第一指示信息指示索引值1,则认为所述第一指示信息指示所述时间信息的值为a。
在一种可选的实施方式中,所述第一消息可以为MAC PDU,或者所述第一消息可以为MAC CE(其中MAC CE为MAC PDU中的一部分)。在此种情况下,可以包括以下多种所述第一消息的实现方式:
一种示例性的实现方式中,所述第一消息为MAC CE时,通过媒介接入控制子头MAC subheader中的逻辑信道标识(logical channel ID,LCID)可以知道对应的MAC CE为 所述第一消息。其中所述LCID可以是新引入的LCID、也可以复用现有的LCID,本申请对此不作限定。示例性的,MAC subheader的格式示意图可以如图19所示。
另一种示例性的实现方式中,所述第一指示信息可以携带在所述MAC PDU的MAC subheader中,或者,所述第一指示信息可以携带在所述MAC PDU的MAC CE中。例如,所述第一消息为MAC CE时,通过媒介接入控制子头MAC subheader中的LCID可以知道对应的MAC CE为所述第一消息,所述LCID可以是新引入的LCID、也可以复用现有的LCID。例如,所述第一指示信息携带在所述MAC PDU的MAC subheader中时,所述第一指示信息可以占用MAC subheader中的2比特,如图20所示。又例如,所述第一指示信息携带在所述MAC PDU的MAC CE中时,所述第一指示信息可以占用MAC CE中的4比特,如图21所示。需要说明的是,所述第一指示信息具体占用几个比特本申请不做限定,为了保证MAC CE的长度以字节(八比特)为单位,剩余的比特位可以为预留比特、或填充比特、或其他信息比特。
另一种示例性的实现方式中,所述第二指示信息可以携带在所述MAC PDU的MAC subheader中,或者,所述第二指示信息可以携带在所述MAC PDU的MAC CE中。例如,所述第一消息为MAC CE时,通过媒介接入控制子头MAC subheader中的LCID可以知道对应的MAC CE为所述第一消息,所述LCID可以是新引入的LCID、也可以复用现有的LCID。例如,所述第二指示信息携带在所述MAC PDU的MAC subheader中时,所述第二指示信息可以占用MAC subheader中的1比特,如图22所示。又例如,所述第二指示信息携带在所述MAC PDU的MAC CE中时,如所述第二指示信息可以占用MAC CE中的1比特,如图23所示。需要说明的是,所述第二指示信息具体占用几个比特本申请不做限定,为了保证MAC CE的长度以字节(八比特)为单位,剩余的比特位可以为预留比特、或填充比特、或其他信息比特。
另一种示例性的实现方式中,当所述第一消息包括所述第一指示信息和所述第二指示信息的情况下:所述第一指示信息可以携带在所述MAC PDU的MAC subheader中,或者,所述第一指示信息可以携带在所述MAC PDU的MAC CE中;所述第二指示信息可以携带在所述MAC PDU的MAC subheader中,或者,所述第二指示信息可以携带在所述MAC PDU的MAC CE中。也即是说,所述第一指示信息和第二指示信息携带的位置的方式可以两两组合,针对所述第一指示信息或所述第二指示信息具体携带的位置,可参考上述实现方式中的方法。例如,所述第一消息为MAC CE时,通过媒介接入控制子头MAC subheader中的LCID可以知道对应的MAC CE为所述第一消息,该LCID可以是新引入的LCID、也可以复用现有的LCID。例如,所述第一指示信息和所述第二指示信息均携带在所述MAC PDU的MAC CE中时,所述第一指示信息可以占用MAC CE中的3比特,所述第二指示信息可以占用MAC CE中的1比特,如图24所示;又例如,所述第一指示信息携带在所述MAC PDU的MAC CE中,所述第二指示信息携带在所述MAC PDU的MAC subheader中时,所述第一指示信息可以占用MAC CE中的3比特,所述第二指示信息可以占用MAC subheader中的1比特,如图25所示,其中图25中(a)为第一指示信息携带在MAC CE中的示意,(b)为所述第二指示信息携带在MAC subheader中的示意。需要说明的是,所述第一指示信息和所述第二指示信息具体占用几个比特本申请不做限定,为了保证MAC CE的长度以字节(八比特)为单位,剩余的比特位可以为预留比特、或填充比特、或其他信息比特。
在一种可选的实施方式中,所述第一消息可以为RRC信令,例如广播消息或RRC专用消息等。
在一种可选的实施方式中,所述第一消息可以为DCI,所述第一消息可以承载在PDCCH上。
步骤1802、若所述第一消息指示所述终端设备唤醒的时间信息,则所述终端设备基于所述时间信息唤醒;或者,若所述第一消息指示所述终端设备休眠的时间信息,则所述终端设备基于所述时间信息休眠。
其中,所述终端设备唤醒可以理解为所述终端设备需要监听PDCCH,所述终端设备休眠可以理解为终端设备不需要监听PDCCH。需要说明的是,本申请不限定所述终端设备唤醒或休眠之前的状态,例如,所述终端设备正处于唤醒时,若所述第一消息指示所述终端设备唤醒的时间信息,则所述终端设备继续唤醒,若所述第一消息指示所述终端设备休眠的时间信息,则所述终端设备从唤醒变为休眠。又例如,所述终端设备正处于休眠时,若所述第一消息指示所述终端设备唤醒的时间信息,则所述终端设备从休眠变为唤醒,若所述第一消息指示所述终端设备休眠的时间信息,则所述终端设备继续休眠。
在一种可选的实施方式中,当所述时间信息为所述终端设备唤醒或者休眠的时间长度时,所述终端设备基于所述时间信息唤醒可以理解为:所述终端设备唤醒且维持唤醒的时间为所述时间信息对应的所述终端设备唤醒的时间长度;所述终端设备基于所述时间信息休眠可以理解为:所述终端设备休眠且维持休眠的时间为所述时间信息对应的所述终端设备休眠的时间长度。具体的,所述终端设备开始唤醒或休眠的时间可以参见上述步骤1801中涉及的相关描述,此处不再重复赘述。
在另一种可选的实施方式中,当所述时间信息为所述终端设备唤醒或者休眠之前的时间长度时,所述终端设备基于所述时间信息唤醒还可以理解为:所述终端设备唤醒且在所述时间信息对应的终端设备唤醒的时间长度后开始唤醒;所述终端设备基于所述时间信息休眠还可以理解为:所述终端设备休眠且在所述时间信息对应的终端设备休眠的时间长度后开始休眠。
在一种可选的实施方式中,当所述时间信息为所述终端设备唤醒或者休眠结束的时间时,所述终端设备基于所述时间信息唤醒可以理解为:所述终端设备唤醒且维持唤醒的时间到所述时间信息对应的终端设备唤醒的时间点时结束;所述终端设备基于所述时间信息休眠可以理解为:终端设备休眠且维持休眠的时间到所述时间信息对应的终端设备休眠的时间点时结束。具体的,所述终端设备开始唤醒或休眠的时间可以参见上述步骤1801中涉及的相关描述,此处不再重复赘述。
在一种可选的实施方式中,当所述第一消息为DCI的情况下,所述终端设备接收来自所述通信设备的所述第一消息后,所述终端设备不启动或不重启活动定时器InactivityTimer。具体的,在现有技术中,当终端设备接收到指示新传的DCI(PDCCH)时,终端设备需要启动或重启InactivityTimer,以便接收后续调度的数据,而本实施方式中,由于所述第一消息与数据调度没有直接关系,因此所述终端设备不需要启动或重启InactivityTimer。
一种具体的实施方式中,所述第一消息除了可以指示所述终端设备唤醒或者休眠的事件信息之外,还可以具有其他指示功能。例如,所述第一消息还可以指示新传,当所述第一消息为指示新传的DCI时,所述终端设备接收来自所述通信设备的所述第一消息后,所述终端设备不启动或不重启InactivityTimer。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若活动定时器正在运行,所述终端设备停止所述活动定时器,或者,所述终端设备停止并重置所述活动定时器。示例性的,所述终端设备停止所述活动定时器可以为:所述终端设备在接收到所述第一消息时(或之后)停止所述InactivityTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述InactivityTimer。其中,示例性的,所述(当前)DXR周期为接收到所述第一消息的时间所在的DRX周期,所述下一个DRX周期开始指的是所述下一个DRX周期的On Duration起始位置。需要说明的是,在本申请图18所示的实施例中涉及的(当前)周期和下一个周期均可以理解为上述描述,下面不再一一重复限定。示例性的,所述终端设备重置所述活动定时器可以为:所述终端设备将所述InactivityTimer的值设置为初始值(例如0)。这样在下一次需要开启所述InactivityTimer时,可以使所述InactivityTimer从0开始计时,以免影响正常流程。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若持续定时器onDurationTimer正在运行,所述终端设备停止所述持续定时器,或者,所述终端设备停止并重置所述持续定时器。示例性的,所述终端设备停止所述onDurationTimer,具体可以为:所述终端设备在接收到所述第一消息时(或之后)停止所述onDurationTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述onDurationTimer。示例性的,所述终端设备重置所述onDurationTimer具体可以为:所述终端设备将所述onDurationTimer的值设置为初始值(例如0)。这样在下一次需要开启所述onDurationTimer时,可以使所述onDurationTimer从0开始计时,以免影响正常流程。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若重传定时器RetransmissionTimer正在运行,所述终端设备停止所述重传定时器,或者,所述终端设备停止并重置所述重传定时器。在一种可选的实施方式中,所述RetransmissionTimer可以为上行重传定时器(RetransmissionTimer(uplink,UL))和下行重传定时器(RetransmissionTimer(downlink,DL))中的一种或多种。其中,所述RetransmissionTimer UL也可以记为drx-RetransmissionTimer UL;所述RetransmissionTimer DL也可以记为drx-RetransmissionTimer DL;本申请实施例中仅以所述RetransmissionTimer UL和RetransmissionTimer DL为例进行说明。应理解,所述RetransmissionTimer UL均可以替换为drx-RetransmissionTimer UL;所述RetransmissionTimer DL均可以替换为drx-RetransmissionTimer DL。
在一种可选的实施方式中,根据所述RetransmissionTimer的具体情况,则若RetransmissionTimer正在运行,所述终端设备停止所述RetransmissionTimer,具体可以分为三种情况:具体可参见图7所示的实施例中涉及的情况b1、情况b2和情况b3,重复之处此处不再重复赘述。
示例性的,所述终端设备停止所述RetransmissionTimer,具体可以为:所述终端设备在接收到所述第一消息时(或之后)停止所述RetransmissionTimer;或者,所述终端设备在(当前)DRX周期的下一个DRX周期开始时停止所述RetransmissionTimer。
示例性的,所述终端设备重置所述RetransmissionTimer具体可以为:所述终端设备将所述RetransmissionTimer的值设置为初始值(例如0)。这样在下一次需要开启所述RetransmissionTimer时,可以使所述RetransmissionTimer从0开始计时,以免影响正常流程。
采用本申请实施例提供的终端设备的状态指示方法,终端设备接收来自通信设备的第 一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;若所述第一消息指示所述终端设备唤醒的时间信息,则所述终端设备基于所述时间信息唤醒;或者若所述第一消息指示所述终端设备休眠的时间信息,则所述终端设备基于所述时间信息休眠。通过上述方法,所述终端设备可以根据所述第一消息灵活唤醒或者休眠。并且相对于现有技术,由于引入了对终端设备休眠的时间信息的指示,可以使终端设备相对于现有技术灵活休眠,从而可以更好的节省功耗,满足节省功耗的需求。
基于以上实施例,在一个实施例中,图16所示终端设备可用于执行上述图18所示的实施例中的终端设备的操作。例如:
所述接收单元1601用于接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;所述处理单元1602用于若所述第一消息指示所述终端设备唤醒的时间信息,则基于所述时间信息唤醒;或者,若所述第一消息指示所述终端设备休眠的时间信息,则基于所述时间信息休眠。
在一种可选的实施方式中,所述第一指示信息指示所述时间信息。
在一种可选的实施方式中,所述第一消息包括第二指示信息,所述第二指示信息指示所述终端设备唤醒或者休眠。
在一种可选的实施方式中,所述时间信息为所述终端设备唤醒或者休眠的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠之前的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠结束的时间。
在一种可选的实施方式中,所述时间长度为:一个或多个毫秒;或者,一个或多个子帧;或者,一个或多个时隙;或者,一个或多个非连续接收DRX周期;或者,一个或多个On Duration;或者,一个或多个寻呼机会;或者,一个或多个物理下行控制信道PDCCH监听机会;或者,以毫秒为单位的时间长度;或者,以子帧为单位的时间长度;或者,以时隙为单位的时间长度;或者,以非连续接收DRX周期为单位的时间长度;或者,以On Duration个数为单位的时间长度;或者,以寻呼机会为单位的时间长度;或者,以物理下行控制信道PDCCH监听机会为单位的时间长度。
在一种可选的实施方式中,所述第一消息为MAC PDU或者RRC信令。
在一种可选的实施方式中,当所述第一消息为MAC PDU,且所述第一消息包括所述第一指示信息时,所述第一指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第一指示信息携带在所述MAC PDU的MAC CE中。
在一种可选的实施方式中,当所述第一消息为MAC PDU,且所述第一消息包括所述第二指示信息时,所述第二指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第二指示信息携带在所述MAC PDU的MAC CE中。
在一种可选的实施方式中,当所述第一消息为MAC PDU,且所述第一消息包括所述第一指示信息和所述第二指示信息时,所述第一指示信息和所述第二指示信息的携带可以为以下方式:所述第一指示信息和所述第二指示信息均携带在所述MAC PDU的媒介接入控制子头中;或者,所述第一指示信息和所述第二指示信息均携带在所述MAC PDU的MAC CE中;或者,所述第一指示信息携带在所述MAC PDU的媒介接入控制子头中,所述第二指示信息携带在所述MAC PDU的MAC CE中;或者,所述第二指示信息携带在所述MAC PDU的媒介接入控制子头中,所述第一指示信息携带在所述MAC PDU的MAC CE中。
在一种可选的实施方式中,所述第一消息可以为DCI。
在一种可选的实施方式中,所述第一消息为DCI时,所述处理单元1602还用于不启动或不重启活动定时器。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若活动定时器正在运行,所述处理单元1602还用于停止所述活动定时器,或者,所述处理单元1602还用于停止并重置所述活动定时器。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若持续定时器正在运行,所述处理单元1602还用于停止所述持续定时器,或者,所述处理单元1602还用于停止并重置所述持续定时器。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若重传定时器正在运行,所述处理单元1602还用于停止所述重传定时器,或者,所述处理单元1602还用于停止并重置所述重传定时器。
基于上述终端设备,接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;若所述第一消息指示所述终端设备唤醒的时间信息,则所述终端设备基于所述时间信息唤醒;或者若所述第一消息指示所述终端设备休眠的时间信息,则所述终端设备基于所述时间信息休眠。这样,所述终端设备可以根据所述第一消息灵活唤醒或者休眠。并且相对于现有技术,由于引入了对终端设备休眠的时间信息的指示,可以使终端设备相对于现有技术灵活休眠,从而可以更好的节省功耗,满足节省功耗的需求。
基于上述实施例,在一个实施例中,图17所示的终端设备还可以用于执行图18所示的实施例中终端设备的操作,例如:
第十八方面,本申请还提供了一种终端设备,该终端设备包括收发器1701、至少一个存储器和至少一个处理器1702,其中:
所述收发器1701用于在接收到所述处理器1702的调用时收发信号或消息;所述处理器1702用于控制所述收发器1701接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;若所述第一消息指示所述终端设备唤醒的时间信息,则基于所述时间信息唤醒;或者,若所述第一消息指示所述终端设备休眠的时间信息,则基于所述时间信息休眠。
在一种可选的实施方式中,所述第一指示信息指示所述时间信息。
在一种可选的实施方式中,所述第一消息包括第二指示信息,所述第二指示信息指示所述终端设备唤醒或者休眠。
在一种可选的实施方式中,所述时间信息为所述终端设备唤醒或者休眠的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠之前的时间长度;或者,所述时间信息为所述终端设备唤醒或者休眠结束的时间。
在一种可选的实施方式中,所述时间长度为:一个或多个毫秒;或者,一个或多个子帧;或者,一个或多个时隙;或者,一个或多个非连续接收DRX周期;或者,一个或多个On Duration;或者,一个或多个寻呼机会;或者,一个或多个物理下行控制信道PDCCH监听机会;或者,以毫秒为单位的时间长度;或者,以子帧为单位的时间长度;或者,以时隙为单位的时间长度;或者,以非连续接收DRX周期为单位的时间长度;或者,以On Duration个数为单位的时间长度;或者,以寻呼机会为单位的时间长度;或者,以物理下行 控制信道PDCCH监听机会为单位的时间长度。
在一种可选的实施方式中,所述第一消息为MAC PDU或者RRC信令。
在一种可选的实施方式中,当所述第一消息为MAC PDU,且所述第一消息包括所述第一指示信息时,所述第一指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第一指示信息携带在所述MAC PDU的MAC CE中。
在一种可选的实施方式中,当所述第一消息为MAC PDU,且所述第一消息包括所述第二指示信息时,所述第二指示信息携带在所述MAC PDU的媒介接入控制子头中,或者,所述第二指示信息携带在所述MAC PDU的MAC CE中。
在一种可选的实施方式中,当所述第一消息为MAC PDU,且所述第一消息包括所述第一指示信息和所述第二指示信息时,所述第一指示信息和所述第二指示信息的携带可以为以下方式:所述第一指示信息和所述第二指示信息均携带在所述MAC PDU的媒介接入控制子头中;或者,所述第一指示信息和所述第二指示信息均携带在所述MAC PDU的MAC CE中;或者,所述第一指示信息携带在所述MAC PDU的媒介接入控制子头中,所述第二指示信息携带在所述MAC PDU的MAC CE中;或者,所述第二指示信息携带在所述MAC PDU的媒介接入控制子头中,所述第一指示信息携带在所述MAC PDU的MAC CE中。
在一种可选的实施方式中,所述第一消息为DCI。
在一种可选的实施方式中,所述第一消息为DCI时,所述处理器1702还用于不启动或不重启活动定时器。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若活动定时器正在运行,所述处理器1702还用于停止所述活动定时器,或者,所述处理器1702还用于停止并重置所述活动定时器。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若持续定时器正在运行,所述处理器1702还用于停止所述持续定时器,或者,所述处理器1702还用于停止并重置所述持续定时器。
在一种可选的实施方式中,若所述第一消息指示所述终端设备休眠的时间信息,若重传定时器正在运行,所述处理器1702还用于停止所述重传定时器,或者,所述处理器1702还用于停止并重置所述重传定时器。
在一种可选的实施方式中,存储器1703,与处理器1702耦合,用于存放程序等。具体地,程序可以包括程序代码,该程序代码包括计算机操作指令。存储器1703可能包括RAM,也可能还包括非易失性存储器(non-volatile memory),例如至少一个磁盘存储器。处理器1702执行存储器1703所存放的应用程序,实现上述功能,从而实现如图18所示的终端设备的状态指示方法。
基于上述终端设备,接收来自通信设备的第一消息,所述第一消息指示所述终端设备唤醒或者休眠的时间信息;若所述第一消息指示所述终端设备唤醒的时间信息,则所述终端设备基于所述时间信息唤醒;或者若所述第一消息指示所述终端设备休眠的时间信息,则所述终端设备基于所述时间信息休眠。这样,所述终端设备可以根据所述第一消息灵活唤醒或者休眠。并且相对于现有技术,由于引入了对终端设备休眠的时间信息的指示,可以使终端设备相对于现有技术灵活休眠,从而可以更好的节省功耗,满足节省功耗的需求。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产 品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (95)

  1. 一种终端设备的休眠方法,其特征在于,包括:
    若终端设备在预设时间内未接收到指示唤醒的信号,并且活动定时器正在运行,所述终端设备停止所述活动定时器,或者
    若终端设备在预设时间内未接收到指示唤醒的信号,并且重传定时器正在运行,所述终端设备停止所述重传定时器,或者
    若终端设备在预设时间内未接收到指示唤醒的信号,并且所述活动定时器和所述重传定时器正在运行,所述终端设备停止所述活动定时器和所述重传定时器;
    其中,所述终端设备配置了非连续接收DRX,所述终端设备在所述活动定时器运行时接收物理下行控制信道PDCCH,所述终端设备在所述重传定时器运行时监听PDCCH。
  2. 如权利要求1所述的方法,其特征在于,所述终端设备在预设时间内未接收到指示唤醒的信号,包括:
    所述终端设备在预设时间内接收到休眠信号;或者
    所述终端设备在预设时间内未接收到唤醒信号;或者
    所述终端设备在预设时间内接收到指示信号,所述指示信号中包含休眠指示信息。
  3. 如权利要求1或2所述的方法,其特征在于,所述终端设备配置了非连续接收DRX包括:所述终端设备配置了DRX周期;
    所述终端设备停止所述活动定时器,包括:
    所述终端设备在当前DRX周期的下一个DRX周期开始时停止所述活动定时器。
  4. 如权利要求1-3任一项所述的方法,其特征在于,所述终端设备配置了非连续接收DRX包括:所述终端设备配置了DRX周期;
    所述终端设备停止所述重传定时器,包括:
    所述终端设备在当前DRX周期的下一个DRX周期开始时停止所述重传定时器。
  5. 如权利要求1-4任一项所述的方法,其特征在于,还包括:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且所述活动定时器正在运行,所述终端设备重置所述活动定时器;或者
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且所述重传定时器正在运行,所述终端设备重置所述重传定时器;或者
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且所述活动定时器和所述重传定时器正在运行,所述终端设备重置所述活动定时器和所述重传定时器。
  6. 如权利要求1-5任一项所述的方法,其特征在于,所述重传定时器为上行重传定时器和下行重传定时器中的一种或多种。
  7. 如权利要求1-6任一项所述的方法,其特征在于,还包括:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且活动定时器正在运行,所述终端设备停止所述活动定时器,并启动或者重启短周期定时器;其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  8. 如权利要求1-6任一项所述的方法,其特征在于,还包括:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且活动定时器正在运行,所述终端设备停止所述活动定时器,并使用长的DRX周期。
  9. 如权利要求8所述的方法,其特征在于,还包括:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且短周期定时器正在运行,所述终端设备停止所述短周期定时器,或者,所述终端设备停止并重置所述短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  10. 如权利要求1至9中任一项所述的方法,其特征在于,所述指示唤醒的信号为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  11. 如权利要求10所述的方法,其特征在于,还包括:
    所述指示唤醒的信号为下行控制信息DCI,所述终端设备不启动或不重启所述活动定时器。
  12. 如权利要求1至11中任一项所述的方法,其特征在于,还包括:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且持续定时器正在运行,所述终端设备停止所述持续定时器,或者,所述终端设备停止并重置所述持续定时器。
  13. 一种终端设备的休眠方法,其特征在于,包括:
    终端设备接收指示休眠的信号;
    所述终端设备启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;
    其中,所述终端设备在所述休眠定时器运行期间休眠包括:所述终端设备在所述休眠定时器运行期间不监听物理下行控制信道PDCCH。
  14. 如权利要求13所述的方法,其特征在于,所述终端设备在所述休眠定时器运行期间休眠还包括:
    所述终端设备在所述休眠定时器运行期间不发送类型0触发的探测参考信号;或者
    所述终端设备在所述休眠定时器运行期间不上报信道状态信息CSI;或者
    所述终端设备在所述休眠定时器运行期间不发送所述探测参考信号且不上报所述CSI。
  15. 如权利要求13或14所述的方法,其特征在于,所述终端设备接收指示休眠的信号,包括:
    所述终端设备接收来自所述通信设备的休眠信号;或者
    所述终端设备接收来自所述通信设备的指示信号,所述指示信号中包含休眠指示信息。
  16. 如权利要求13-15任一项所述的方法,其特征在于,所述终端设备接收来自通信设备的指示休眠的信号之前,所述方法还包括:
    所述终端设备接收所述通信设备配置的休眠时长。
  17. 如权利要求13-15任一项所述的方法,其特征在于,所述信号中包括指示信息,所述指示信息指示休眠时长。
  18. 如权利要求17所述的方法,其特征在于,所述终端设备接收来自通信设备的指示休眠的信号之前,所述方法还包括:
    所述终端设备接收所述通信设备配置的至少一个时长,所述休眠时长为所述至少一个时长中的一个。
  19. 如权利要求16-18任一项所述的方法,其特征在于,所述终端设备启动或重启休眠定时器之前,所述方法还包括:
    所述终端设备配置所述休眠定时器的定时时长为所述休眠时长。
  20. 如权利要求13至19中任一项所述的方法,其特征在于,所述指示休眠的信号为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  21. 如权利要求20所述的方法,其特征在于,所述指示休眠的信号为下行控制信息DCI,所述终端设备不启动或不重启所述活动定时器。
  22. 一种终端设备的休眠方法,其特征在于,包括:
    若终端设备接收到指示休眠的信号,并且活动定时器正在运行,所述终端设备停止所述活动定时器;或者
    若终端设备接收到指示休眠的信号,并且重传定时器正在运行,所述终端设备停止所述重传定时器;或者
    若终端设备接收到指示休眠的信号,并且活动定时器和重传定时器正在运行,所述终端设备停止所述活动定时器和所述重传定时器;
    其中,所述终端设备配置了非连续接收DRX,所述终端设备在所述活动定时器运行时监听物理下行控制信道PDCCH,所述终端设备在所述重传定时器运行时监听PDCCH。
  23. 如权利要求22所述的方法,其特征在于,所述终端设备接收到指示休眠的信号的情况具体包括:
    所述终端设备接收到休眠信号;或者
    所述终端设备接收到指示信号,所述指示信号中包含休眠指示信息。
  24. 如权利要求22或23所述的方法,其特征在于,所述终端设备停止所述活动定时器,具体包括:
    所述终端设备在接收到指示休眠的信号时停止所述活动定时器;或者,
    所述终端设备在接收到指示休眠的信号后停止所述活动定时器;或者,
    所述终端设备在当前DRX周期的下一个DRX周期开始时停止所述活动定时器。
  25. 如权利要求22至24中任一项所述的方法,其特征在于,所述终端设备停止所述重传定时器,具体包括:
    所述终端设备在当前DRX周期的下一个DRX周期开始时停止所述重传定时器。
  26. 如权利要求22至25中任一项所述的方法,其特征在于,所述方法还包括:
    若终端设备接收到指示休眠的信号,并且所述活动定时器正在运行,所述终端设备重置所述活动定时器;或者
    若终端设备接收到指示休眠的信号,并且所述重传定时器正在运行,所述终端设备重置所述重传定时器;或者
    若终端设备接收到指示休眠的信号,并且所述活动定时器和重传定时器正在运行,所述终端设备重置所述重传定时器。
  27. 如权利要求22至26中任一项所述的方法,其特征在于,所述重传定时器为上行重传定时器和下行重传定时器中的一种或多种。
  28. 如权利要求22至27中任一项所述的方法,其特征在于,还包括:
    若所述终端设备接收到指示休眠的信号,并且活动定时器正在运行,所述终端设备停止所述活动定时器,并且所述终端设备启动或者重启短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  29. 如权利要求22至27中任一项所述的方法,其特征在于,还包括:
    若所述终端设备接收到指示休眠的信号,并且活动定时器正在运行,若所述活动定时器正在运行,所述终端设备停止所述活动定时器,并使用长的DRX周期。
  30. 如权利要求29所述的方法,其特征在于,还包括:
    在所述终端设备接收到指示休眠的信号的情况下,若短周期定时器正在运行,所述终端设备停止所述短周期定时器,或者,所述终端设备停止并重置所述短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  31. 如权利要求22至30中任一项所述的方法,其特征在于,所述指示休眠的信号为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  32. 如权利要求31所述的方法,其特征在于,所述指示休眠的信号为下行控制信息DCI,所述终端设备不启动或不重启所述活动定时器。
  33. 如权利要求22至31中任一项所述的方法,其特征在于,还包括:
    若所述终端设备在预设时间内未接收到指示休眠的信号,并且持续定时器正在运行,所述终端设备停止所述持续定时器,或者,所述终端设备停止并重置所述持续定时器。
  34. 一种终端设备的休眠方法,其特征在于,包括:
    终端设备接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器;
    若所述终端设备接收到指示消息,并且持续定时器正在运行,所述终端设备停止所述持续定时器;或者
    若所述终端设备接收到指示消息,并且活动定时器正在运行,所述终端设备停止所述活动定时器;或者
    若所述终端设备接收到指示消息,并且持续定时器和活动定时器正在运行,所述终端设备停止所述持续定时器和所述活动定时器;
    其中,所述终端设备配置了非连续接收DRX,所述终端设备在所述持续定时器运行时监听物理下行控制信道PDCCH,所述终端设备在所述活动定时器运行时监听PDCCH。
  35. 如权利要求34所述的方法,其特征在于,还包括:
    若所述终端设备接收到指示消息,并且重传定时器正在运行,所述终端设备停止所述重传定时器。
  36. 如权利要求35所述的方法,其特征在于,所述重传定时器为上行重传定时器和下行重传定时器中的一种或多种。
  37. 如权利要求34或35所述的方法,其特征在于,所述指示消息为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  38. 如权利要求34-37任一项所述的方法,其特征在于,所述终端设备接收指示消息包括:
    所述终端设备在使用长的DRX周期时,接收所述指示消息。
  39. 如权利要求38所述的方法,其特征在于,所述方法还包括:
    所述终端设备接收到所述指示消息,继续使用所述长的DRX周期。
  40. 如权利要求34-39任一项所述的方法,其特征在于,所述终端设备接收指示消息包括:
    所述终端设备在使用短的DRX周期时,接收所述指示消息。
  41. 如权利要求40所述的方法,其特征在于,所述方法还包括:
    所述终端设备接收到所述指示消息,继续使用所述短的DRX周期。
  42. 如权利要求41所述的方法,其特征在于,所述方法还包括:
    所述终端设备接收到所述指示消息,不启动或不重启短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  43. 如权利要求34-42中任一项所述的方法,其特征在于,所述方法还包括:
    若所述终端设备接收到所述指示消息,并且所述持续定时器正在运行,所述终端设备重置所述持续定时器;或者
    若所述终端设备接收到所述指示消息,并且所述活动定时器正在运行,所述终端设备重置所述活动定时器;或者
    若所述终端设备接收到所述指示消息,并且所述持续定时器和活动定时器正在运行,所述终端设备重置所述持续定时器和所述活动定时器。
  44. 如权利要求34-43中任一项所述的方法,其特征在于,所述方法还包括:
    所述终端设备接收到所述指示消息,并且重传定时器正在运行,所述终端设备重置所述重传定时器。
  45. 一种终端设备,其特征在于,包括:
    接收单元,用于接收信号;
    处理单元,用于:
    在预设时间内通过所述接收单元未接收到指示唤醒的信号,并且活动定时器正在运行,所述终端设备停止所述活动定时器,或者
    在预设时间内通过所述接收单元未接收到指示唤醒的信号,并且重传定时器正在运行,所述终端设备停止所述重传定时器,或者
    在预设时间内通过所述接收单元未接收到指示唤醒的信号,并且所述活动定时器和所述重传定时器正在运行,所述终端设备停止所述活动定时器和所述重传定时器;
    其中,所述终端设备配置了非连续接收DRX,所述终端设备在所述活动定时器运行时接收物理下行控制信道PDCCH,所述终端设备在所述重传定时器运行时监听PDCCH。
  46. 如权利要求45所述的终端设备,其特征在于,所述接收单元具体用于:
    接收休眠信号,或者接收唤醒信号,或者接收指示信号,其中,所述指示信号中包含休眠指示信息;
    在预设时间内通过所述接收单元未接收到指示唤醒的信号包括:
    在预设时间内通过所述接收单元接收到所述休眠信号,或者在预设时间内通过所述接收单元未接收到所述唤醒信号,或者在预设时间内通过所述接收单元接收到所述指示信号。
  47. 如权利要求45或46所述的终端设备,其特征在于,所述终端设备配置了非连续接收DRX包括:所述终端设备配置了DRX周期;
    所述停止所述活动定时器中,所述处理单元具体用于:
    在当前DRX周期的下一个DRX周期开始时停止所述活动定时器。
  48. 如权利要求45-47任一项所述的终端设备,其特征在于,所述终端设备配置了非连续接收DRX包括:所述终端设备配置了DRX周期;
    所述停止所述重传定时器中,所述处理单元具体用于:
    在当前DRX周期的下一个DRX周期开始时停止所述重传定时器。
  49. 如权利要求45-48任一项所述的终端设备,其特征在于,所述处理单元还用于:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且所述活动定时器正在运行,则重置所述活动定时器;或者
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且所述重传定时器正在运行,则重置所述重传定时器;或者
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且所述活动定时器和所述重传定时器正在运行,则重置所述活动定时器和所述重传定时器。
  50. 如权利要求45-49任一项所述的终端设备,其特征在于,所述重传定时器为上行重传定时器和下行重传定时器中的一种或多种。
  51. 如权利要求45-50任一项所述的终端设备,其特征在于,所述处理单元还用于:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且活动定时器正在运行,停止所述活动定时器,并启动或者重启短周期定时器;其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  52. 如权利要求45-51任一项所述的终端设备,其特征在于,所述处理单元还用于:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且活动定时器正在运行,所述终端设备停止所述活动定时器,并使用长的DRX周期。
  53. 如权利要求52所述的终端设备,其特征在于,所述处理单元还用于:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且短周期定时器正在运行,停止所述短周期定时器,或者,停止并重置所述短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  54. 如权利要求45至53中任一项所述的终端设备,其特征在于,所述指示唤醒的信号为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  55. 如权利要求54所述的终端设备,其特征在于,所述处理单元还用于:
    若所述指示唤醒的信号为下行控制信息DCI,不启动或不重启所述活动定时器。
  56. 如权利要求45至55中任一项所述的终端设备,其特征在于,所述处理单元还用于:
    若所述终端设备在预设时间内未接收到指示唤醒的信号,并且持续定时器正在运行,停止所述持续定时器,或者,停止并重置所述持续定时器。
  57. 一种终端设备,其特征在于,包括:
    接收单元,用于接收指示休眠的信号;
    处理单元,用于启动或重启休眠定时器,并在所述休眠定时器运行期间休眠;
    其中,在所述休眠定时器运行期间休眠,所述处理单元具体用于:在所述休眠定时器运行期间不监听物理下行控制信道PDCCH。
  58. 如权利要求57所述的终端设备,其特征在于,在所述休眠定时器运行期间休眠中,所述处理单元还具体用于:
    在所述休眠定时器运行期间不发送类型0触发的探测参考信号;或者
    在所述休眠定时器运行期间不上报信道状态信息CSI;或者
    在所述休眠定时器运行期间不发送所述探测参考信号且不上报所述CSI。
  59. 如权利要求57或58所述的终端设备,其特征在于,在接收指示休眠的信号中,所述接收单元具体用于:
    接收来自所述通信设备的休眠信号;或者
    接收来自所述通信设备的指示信号,所述指示信号中包含休眠指示信息。
  60. 如权利要求57-59任一项所述的终端设备,其特征在于,所述接收单元还用于:
    在接收来自通信设备的指示休眠的信号之前,
    接收所述通信设备配置的休眠时长。
  61. 如权利要求57-60任一项所述的终端设备,其特征在于,所述信号中包括指示信息,所述指示信息指示休眠时长。
  62. 如权利要求61所述的终端设备,其特征在于,所述接收单元还用于:
    在接收来自通信设备的指示休眠的信号之前,接收所述通信设备配置的至少一个时长,所述休眠时长为所述至少一个时长中的一个。
  63. 如权利要求60-62任一项所述的终端设备,其特征在于,在启动或重启休眠定时器之前,所述处理器还用于:
    配置所述休眠定时器的定时时长为所述休眠时长。
  64. 如权利要求57至63中任一项所述的终端设备,其特征在于,所述指示休眠的信号为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  65. 如权利要求64所述的终端设备,其特征在于,所述指示休眠的信号为下行控制信息DCI,所述处理器还用于:不启动或不重启所述活动定时器。
  66. 一种终端设备,其特征在于,包括:
    接收单元,用于接收指示休眠的信号;
    处理单元,用于:
    在通过所述接收单元接收到指示休眠的信号,并且活动定时器正在运行,停止所述活动定时器;或者
    在通过所述接收单元接收到指示休眠的信号,并且重传定时器正在运行,停止所述重传定时器;或者
    在终端设备接收到指示休眠的信号,并且活动定时器和重传定时器正在运行,停止所述活动定时器和所述重传定时器;
    其中,所述终端设备配置了非连续接收DRX,所述终端设备在所述活动定时器运行时监听物理下行控制信道PDCCH,所述终端设备在所述重传定时器运行时监听PDCCH。
  67. 如权利要求66所述的终端设备,其特征在于,通过所述接收单元接收到指示休眠的信号,具体包括:
    所述接收单元接收到休眠信号;或者
    所述接收单元接收到指示信号,所述指示信号中包含休眠指示信息。
  68. 如权利要求66或67所述的终端设备,其特征在于,在停止所述活动定时器,所述处理器具体用于:
    在通过所述接收单元接收到指示休眠的信号时停止所述活动定时器;或者,
    所述终端设备在通过所述接收单元接收到指示休眠的信号后停止所述活动定时器;或者,
    所述终端设备在通过所述接收单元当前DRX周期的下一个DRX周期开始时停止所述活动定时器。
  69. 如权利要求66至68中任一项所述的终端设备,其特征在于,在停止所述重传定时器,所述处理器具体用于:
    在当前DRX周期的下一个DRX周期开始时停止所述重传定时器。
  70. 如权利要求66至69中任一项所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到指示休眠的信号,并且所述活动定时器正在运行,重置所述活动定时器;或者
    在通过所述接收单元接收到指示休眠的信号,并且所述重传定时器正在运行,重置所述重传定时器;或者
    在通过所述接收单元接收到指示休眠的信号,并且所述活动定时器和重传定时器正在运行,重置所述重传定时器。
  71. 如权利要求66至70中任一项所述的终端设备,其特征在于,所述重传定时器为上行重传定时器和下行重传定时器中的一种或多种。
  72. 如权利要求66至71中任一项所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到指示休眠的信号,并且活动定时器正在运行,停止所述活动定时器,并且启动或者重启短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  73. 如权利要求66至71中任一项所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到指示休眠的信号,并且活动定时器正在运行,若所述活动定时器正在运行,停止所述活动定时器,并使用长的DRX周期。
  74. 如权利要求73所述的终端设备,其特征在于,所述处理器还用于:
    通过所述接收单元接收到指示休眠的信号的情况下,若短周期定时器正在运行,停止所述短周期定时器,或者,停止并重置所述短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  75. 如权利要求66至74中任一项所述的终端设备,其特征在于,所述指示休眠的信号为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  76. 如权利要求75所述的终端设备,其特征在于,所述指示休眠的信号为下行控制信息DCI,所述处理器还用于:
    不启动或不重启所述活动定时器。
  77. 如权利要求66至75中任一项所述的终端设备,其特征在于,所述处理器还用于:
    在预设时间内通过所述接收单元未接收到指示休眠的信号,并且持续定时器正在运行,停止所述持续定时器,或者,停止并重置所述持续定时器。
  78. 一种终端设备,其特征在于,包括:
    接收单元,用于接收指示消息,所述指示消息用于指示所述终端设备停止特定定时器;
    处理单元,用于:
    在所述接收单元接收到指示消息,并且持续定时器正在运行,所述持续定时器;或者
    在所述接收单元接收到指示消息,并且活动定时器正在运行,停止所述活动定时器;或者
    在所述接收单元接收到指示消息,并且持续定时器和活动定时器正在运行,停止所述持续定时器和所述活动定时器;
    其中,所述终端设备配置了非连续接收DRX,所述终端设备在所述持续定时器运行时监听物理下行控制信道PDCCH,所述终端设备在所述活动定时器运行时监听PDCCH。
  79. 如权利要求78所述的终端设备,其特征在于,所述处理器还用于:
    在所述接收单元接收到指示消息,并且重传定时器正在运行,停止所述重传定时器。
  80. 如权利要求79所述的终端设备,其特征在于,所述重传定时器为上行重传定时器和下行重传定时器中的一种或多种。
  81. 如权利要求79或80所述的终端设备,其特征在于,所述指示消息为物理层序列、或下行控制信息DCI、或媒介接入控制控制单元MAC CE、或媒介接入控制协议数据单元MAC PDU。
  82. 如权利要求79-81任一项所述的终端设备,其特征在于,所述接收单元具体用于:
    在使用长的DRX周期时,接收所述指示消息。
  83. 如权利要求82所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到所述指示消息,继续使用所述长的DRX周期。
  84. 如权利要求79-83任一项所述的终端设备,其特征在于,所述接收单元具体用于:
    在使用短的DRX周期时,接收所述指示消息。
  85. 如权利要求84所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到所述指示消息,继续使用所述短的DRX周期。
  86. 如权利要求85所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到所述指示消息,不启动或不重启短周期定时器,其中,所述短周期定时器运行时所述终端设备采用短的DRX周期。
  87. 如权利要求78-86中任一项所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到所述指示消息,并且所述持续定时器正在运行,重置所述持续定时器;或者
    在通过所述接收单元接收到所述指示消息,并且所述活动定时器正在运行,重置所述活动定时器;或者
    在通过所述接收单元接收到所述指示消息,并且所述持续定时器和活动定时器正在运行,重置所述持续定时器和所述活动定时器。
  88. 如权利要求78-86中任一项所述的终端设备,其特征在于,所述处理器还用于:
    在通过所述接收单元接收到所述指示消息,并且重传定时器正在运行,重置所述重传定时器。
  89. 一种终端设备,其特征在于,包括收发器、至少一个存储器和至少一个处理器,其中:
    所述收发器,用于在接收到所述处理器的调用时接收和发送信号;
    所述至少一个处理器,用于与所述至少存储器耦合,调用所述存储器中的程序,使所述终端设备执行如权利要求1-44中任一项所述的方法。
  90. 一种计算机存储介质,其特征在于,所述计算机存储介质中存储有计算机可执 行指令,所述计算机可执行指令在被所述计算机调用时用于使所述计算机执行上述权利要求1-44中任一项所述的方法。
  91. 一种包含指令的计算机程序产品,其特征在于,当其在计算机上运行时,使得计算机执行上述权利要求1-44中任一项所述的方法。
  92. 一种装置,其特征在于,包括处理器、处理器与存储器耦合,所述存储器用于存储指令,所述处理器用于执行所述指令,使所述装置执行如权利要求1-44中任一项所述的方法。
  93. 如权利要求92所述的装置,其特征在于,所述装置为芯片。
  94. 如权利要求92或93所述的装置,其特征在于,所述存储器为片外存储器或片内集成存储器。
  95. 一种装置,其特征在于,包括处理器、所述处理器用于执行指令,使所述装置执行如权利要求1-44中任一项所述的方法。
PCT/CN2019/075084 2018-08-09 2019-02-14 一种终端设备的休眠方法及装置 WO2020029568A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/266,721 US11871349B2 (en) 2018-08-09 2019-02-14 Sleep method for terminal device and apparatus
EP19846376.2A EP3826369A4 (en) 2018-08-09 2019-02-14 Sleep method and apparatus for terminal device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201810902746.X 2018-08-09
CN201810902746 2018-08-09
CN201811044304.2A CN109219116B (zh) 2018-08-09 2018-09-07 一种终端设备的休眠方法及装置
CN201811044304.2 2018-09-07

Publications (1)

Publication Number Publication Date
WO2020029568A1 true WO2020029568A1 (zh) 2020-02-13

Family

ID=64986705

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/075084 WO2020029568A1 (zh) 2018-08-09 2019-02-14 一种终端设备的休眠方法及装置

Country Status (4)

Country Link
US (1) US11871349B2 (zh)
EP (1) EP3826369A4 (zh)
CN (1) CN109219116B (zh)
WO (1) WO2020029568A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113840358A (zh) * 2020-06-24 2021-12-24 Oppo(重庆)智能科技有限公司 报文过滤方法、移动终端及计算机可读存储介质
EP4165911A4 (en) * 2020-09-17 2023-11-15 Samsung Electronics Co., Ltd. METHOD AND USER EQUIPMENT FOR MANAGING SLEEP DURATION IN A CDRX SESSION

Families Citing this family (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109219116B (zh) 2018-08-09 2022-05-31 华为技术有限公司 一种终端设备的休眠方法及装置
US11606751B2 (en) * 2018-08-17 2023-03-14 Interdigital Patent Holdings, Inc. Power saving signals in wireless communication
US20220078715A1 (en) * 2019-01-22 2022-03-10 Beijing Xiaomi Mobile Software Co., Ltd. Methods and apparatuses for using power-saving signal pattern, device and system
CN111510998A (zh) * 2019-01-31 2020-08-07 夏普株式会社 由用户设备执行的方法以及用户设备
CN111526567B (zh) * 2019-02-02 2021-07-16 华为技术有限公司 一种信号传输方法和装置
CN111436103B (zh) * 2019-02-02 2021-12-24 维沃移动通信有限公司 节能模式的切换方法、节能模式的配置方法及通信设备
WO2020163998A1 (zh) * 2019-02-12 2020-08-20 Oppo广东移动通信有限公司 无线通信的方法和设备
EP3927023A4 (en) * 2019-02-13 2022-02-09 Beijing Xiaomi Mobile Software Co., Ltd. METHOD AND APPARATUS FOR USING A POWER-SAVING SIGNALING MODE AND TERMINAL
CN111586812B (zh) * 2019-02-15 2023-08-25 海信集团有限公司 一种终端接收节能信号的方法及终端
US11223444B2 (en) * 2019-03-14 2022-01-11 Mediatek Singapore Pte. Ltd. Method and apparatus for channel quality information reporting under discontinuous reception in mobile communications
CN111698768B (zh) * 2019-03-15 2021-07-09 华为技术有限公司 通信方法及其装置
EP4284111A3 (en) * 2019-03-28 2024-02-21 Koninklijke Philips N.V. Power-saving active bwp
WO2020211022A1 (zh) * 2019-04-17 2020-10-22 北京小米移动软件有限公司 终端睡眠状态控制方法、装置及计算机可读存储介质
WO2020215332A1 (zh) * 2019-04-26 2020-10-29 Oppo广东移动通信有限公司 非连续接收的方法和设备
CN111867020A (zh) * 2019-04-30 2020-10-30 大唐移动通信设备有限公司 一种数据传输的方法和设备
WO2020220361A1 (zh) * 2019-04-30 2020-11-05 Oppo广东移动通信有限公司 Drx操作方法及相关设备
US20220217636A1 (en) 2019-05-03 2022-07-07 Samsung Electronics Co., Ltd. Methods and systems for handling power saving signals to improve power saving performance of ue
CN110072203B (zh) * 2019-05-06 2021-10-19 河南工学院 一种基于物联网的大学生就业信息收集方法及收集系统
US20220217637A1 (en) * 2019-05-06 2022-07-07 Beijing Xiaomi Mobile Software Co., Ltd. Inactivity timer timeout processing methods and apparatuses
SG11202112995RA (en) * 2019-05-24 2021-12-30 Beijing Xiaomi Mobile Software Co Ltd Monitoring method, signaling issuing method, and communication device
WO2020248153A1 (en) * 2019-06-12 2020-12-17 Nokia Shanghai Bell Co., Ltd. Mechanism for handling pdcch skipping and wake up signaling
WO2020258103A1 (zh) * 2019-06-26 2020-12-30 北京小米移动软件有限公司 监听方法、指示下发方法及装置、通信设备及存储
CN113196864B (zh) * 2019-07-04 2023-09-26 Oppo广东移动通信有限公司 非连续接收的方法和装置
CN111294902B (zh) * 2019-07-05 2021-06-18 展讯通信(上海)有限公司 唤醒方法及装置、存储介质、终端
JP7319229B2 (ja) * 2019-07-05 2023-08-01 華碩電腦股▲ふん▼有限公司 無線通信システムにおける電力節約信号のモニタリングのための方法及び装置
CN111294901B (zh) * 2019-07-05 2021-12-21 展讯通信(上海)有限公司 进入睡眠的方法及装置、存储介质、用户设备
WO2021007824A1 (zh) * 2019-07-17 2021-01-21 北京小米移动软件有限公司 唤醒信号处理、信息下发方法及装置、通信设备及介质
US20220256464A1 (en) * 2019-07-29 2022-08-11 Beijing Xiaomi Mobile Software Co., Ltd. Sidelink communication method and apparatus, and storage medium
WO2021031169A1 (zh) * 2019-08-21 2021-02-25 Oppo广东移动通信有限公司 信道监听方法、装置、终端、基站和存储介质
CN112468273B (zh) * 2019-09-06 2022-09-13 维沃移动通信有限公司 处理方法和设备
CN113767674B (zh) * 2019-09-27 2023-10-20 华为技术有限公司 一种定时器控制的方法和装置
CN112825589B (zh) * 2019-11-21 2022-03-11 维沃移动通信有限公司 一种进入休眠行为的方法和终端
CN112994852B (zh) * 2019-12-13 2023-06-09 维沃移动通信有限公司 上行控制信息上报方法及装置、通信设备
CN113079558B (zh) * 2020-01-03 2022-10-18 荣耀终端有限公司 一种功耗控制方法、芯片系统及终端设备
CN113225845A (zh) * 2020-01-21 2021-08-06 华硕电脑股份有限公司 处理关于周期性传送的侧链路不连续接收的方法和设备
CN113163413B (zh) * 2020-01-22 2023-09-01 华为技术有限公司 无线通信方法、终端设备和网络设备
WO2021159277A1 (zh) * 2020-02-11 2021-08-19 北京小米移动软件有限公司 数据通信方法、装置、通信设备及存储介质
CN111869274B (zh) * 2020-06-03 2023-09-19 北京小米移动软件有限公司 数据传输处理方法、装置、用户设备及存储介质
CN114071502B (zh) * 2020-08-05 2024-05-07 维沃移动通信有限公司 配置方法及装置
WO2022032527A1 (zh) * 2020-08-12 2022-02-17 北京小米移动软件有限公司 信息处理方法、装置、通信设备及存储介质
US20220070776A1 (en) * 2020-08-25 2022-03-03 Qualcomm Incorporated Methods and system for forward link power saving in a star topology of user equipment
CN114258117A (zh) * 2020-09-25 2022-03-29 维沃移动通信有限公司 确定终端行为的方法、指示终端行为的方法及装置
CN112291860A (zh) * 2020-12-25 2021-01-29 广东省新一代通信与网络创新研究院 一种基于下行链路控制信息扩展的节能方法及系统
WO2023060447A1 (zh) * 2021-10-12 2023-04-20 Oppo广东移动通信有限公司 信号发送方法、信号接收方法、装置、设备及存储介质
WO2024031613A1 (en) * 2022-08-12 2024-02-15 Qualcomm Incorporated Providing a sleep indication during a discontinuous reception active time
CN115826731B (zh) * 2022-10-19 2023-07-11 科东(广州)软件科技有限公司 休眠控制方法及装置、存储介质和计算设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101534297A (zh) * 2009-03-05 2009-09-16 北京交通大学 一种实现流控制传输协议的动态流创建方法
CN101651530A (zh) * 2008-08-11 2010-02-17 中兴通讯股份有限公司 不连续接收和测量间隙冲突时的处理方法
CN105813177A (zh) * 2014-12-27 2016-07-27 华为技术有限公司 非连续接收周期管理方法和装置
CN109219116A (zh) * 2018-08-09 2019-01-15 华为技术有限公司 一种终端设备的休眠方法及装置

Family Cites Families (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101541067B (zh) * 2008-03-21 2011-02-02 凌阳电通科技股份有限公司 在非连续接收机制中停留在短周期的方法
CN102421148B (zh) * 2010-09-28 2016-03-30 华为技术有限公司 一种控制多种通信系统实现通信的方法和用户设备
US9167618B2 (en) * 2010-11-16 2015-10-20 At&T Mobility Ii Llc Data bundling and fast dormancy based upon intelligent application learning
CN102625432B (zh) * 2011-01-28 2016-01-27 华为技术有限公司 一种非连续接收的方法和装置
CN103582166B (zh) * 2012-08-09 2017-05-03 电信科学技术研究院 终端配置方法及终端设备
EP3148262B1 (en) * 2014-05-21 2023-11-01 Sharp Kabushiki Kaisha Terminal device and method
US11310740B2 (en) * 2014-11-04 2022-04-19 Qualcomm Incorporated Discontinuous reception mode with two-stage wake-up
JP6618084B2 (ja) * 2014-11-06 2019-12-11 シャープ株式会社 端末装置、基地局装置および方法
WO2017052596A1 (en) * 2015-09-25 2017-03-30 Maruti Gupta Low-power wakeup radio for mobile devices
EP3363253B1 (en) * 2015-10-14 2020-12-02 Telefonaktiebolaget LM Ericsson (publ) Managing transitions between different user equipment activity configurations
US10524206B2 (en) * 2015-12-09 2019-12-31 Qualcomm Incorporated Macro and micro discontinuous reception
EP3226456B1 (en) * 2016-04-01 2020-06-03 Panasonic Intellectual Property Corporation of America Asynchronous retransmission protocol
US20180020405A1 (en) * 2016-07-13 2018-01-18 Intel IP Corporation Wake-up packet acknowledgement procedure
US20180020404A1 (en) * 2016-07-14 2018-01-18 Po-Kai Huang Wake-up packet backoff procedure
EP3497623B1 (en) * 2016-08-11 2022-11-02 Datang Mobile Communications Equipment Co., Ltd. Method and apparatus for on-demand mobile device access
CN115174012B (zh) * 2016-08-19 2024-04-16 瑞典爱立信有限公司 用于处理通信网络中的不连续接收的方法和装置
CN108282849B (zh) 2017-01-06 2022-09-27 中兴通讯股份有限公司 数据发送、数据接收方法及装置、接入点、站点
US10462744B2 (en) * 2017-02-14 2019-10-29 Intel IP Corporation Methods and systems for reuse of a wireless medium during wake-up of a wireless device
US11483810B2 (en) * 2017-04-03 2022-10-25 Huawei Technologies Co., Ltd. Methods and systems for resource configuration of wireless communication systems
US10588171B2 (en) * 2017-05-12 2020-03-10 Qualcomm Incorporated Techniques for multi-state DRX in new radio
US10904845B2 (en) * 2017-05-15 2021-01-26 Qualcomm Incorporated Synchronization channel for a wake-up receiver (WUR) in a communication device
US10841876B2 (en) * 2017-05-15 2020-11-17 Qualcomm Incorporated Wake-up signal (WUS) and wake-up receiver (WUR) in a communication device
US11218965B2 (en) * 2017-05-24 2022-01-04 Lg Electronics Inc. Method and apparatus for transmitting and receiving a wake-up signal in a wireless communication system
CN111034278B (zh) * 2017-06-28 2023-05-23 Lg电子株式会社 无线lan系统中发送或接收帧的方法及其装置
CN109429310B (zh) * 2017-07-20 2021-04-06 维沃移动通信有限公司 一种drx参数的指示方法、相关设备及系统
WO2019033112A1 (en) * 2017-08-11 2019-02-14 Intel Corporation ALARM SIGNALING IN WIRELESS TELECOMMUNICATION NETWORKS
US11089547B2 (en) * 2017-10-30 2021-08-10 Intel Corporation Apparatus, system, and method to tear down a negotiated wake-up radio mode
US11184854B2 (en) * 2017-11-02 2021-11-23 Lg Electronics Inc. Method for transmitting or receiving frame in wireless LAN and apparatus therefor
WO2019125748A1 (en) * 2017-12-18 2019-06-27 Kyocera Corporation Increasing mtc device power-consumption efficiency by using common wake-up signal
WO2019158446A1 (en) * 2018-02-15 2019-08-22 Sony Corporation Wake_up signal candidate indicator
WO2019217259A1 (en) * 2018-05-08 2019-11-14 Idac Holdings, Inc. Wireless transmit receive unit (wtru) reachability
WO2020029249A1 (en) * 2018-08-10 2020-02-13 Apple Inc. Wake up signal for cellular communication in unlicensed spectrum
US11606751B2 (en) * 2018-08-17 2023-03-14 Interdigital Patent Holdings, Inc. Power saving signals in wireless communication
BR112021005493A2 (pt) * 2018-09-28 2021-06-15 Nokia Technologies Oy método, aparelho e produto de programa de computador
EP4250827A3 (en) * 2018-12-21 2023-11-22 Telefonaktiebolaget LM Ericsson (publ) Conditional wake-up signal configuration for new radio
CN111436098A (zh) * 2019-01-11 2020-07-21 华为技术有限公司 通信方法及装置
WO2020215332A1 (zh) * 2019-04-26 2020-10-29 Oppo广东移动通信有限公司 非连续接收的方法和设备
EP4135367A4 (en) * 2020-04-07 2023-04-19 Beijing Xiaomi Mobile Software Co., Ltd. WAKE-UP TIME CONTROL METHOD AND APPARATUS AND COMPUTER READABLE STORAGE MEDIUM
WO2022103147A1 (ko) * 2020-11-12 2022-05-19 엘지전자 주식회사 Nr v2x에서 sl drx 온-듀레이션에서 사이드링크 재전송 동작을 수행하는 방법 및 장치
US20220232477A1 (en) * 2021-01-15 2022-07-21 Qualcomm Incorporated Downlink traffic jitter handling for xr ue power saving
EP4278710A1 (en) * 2021-01-15 2023-11-22 Qualcomm Incorporated Downlink traffic jitter handling for xr ue power saving
KR20240041951A (ko) * 2021-08-17 2024-04-01 엘지전자 주식회사 Nr v2x에서 사이드링크 전송 상태 지시 기반의 sl drx 동작 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651530A (zh) * 2008-08-11 2010-02-17 中兴通讯股份有限公司 不连续接收和测量间隙冲突时的处理方法
CN101534297A (zh) * 2009-03-05 2009-09-16 北京交通大学 一种实现流控制传输协议的动态流创建方法
CN105813177A (zh) * 2014-12-27 2016-07-27 华为技术有限公司 非连续接收周期管理方法和装置
CN109219116A (zh) * 2018-08-09 2019-01-15 华为技术有限公司 一种终端设备的休眠方法及装置

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113840358A (zh) * 2020-06-24 2021-12-24 Oppo(重庆)智能科技有限公司 报文过滤方法、移动终端及计算机可读存储介质
EP4165911A4 (en) * 2020-09-17 2023-11-15 Samsung Electronics Co., Ltd. METHOD AND USER EQUIPMENT FOR MANAGING SLEEP DURATION IN A CDRX SESSION
US11974226B2 (en) 2020-09-17 2024-04-30 Samsung Electronics Co., Ltd. Method and UE for managing sleep duration in CDRX session

Also Published As

Publication number Publication date
EP3826369A4 (en) 2021-12-29
EP3826369A1 (en) 2021-05-26
CN109219116A (zh) 2019-01-15
CN109219116B (zh) 2022-05-31
US11871349B2 (en) 2024-01-09
US20210306952A1 (en) 2021-09-30

Similar Documents

Publication Publication Date Title
WO2020029568A1 (zh) 一种终端设备的休眠方法及装置
CN109155970B (zh) 用于配置无线网络中的不连续接收模式的方法和装置
TW201943292A (zh) 喚醒無線電有效重新發現及媒體存取方法
TW202010336A (zh) 一種信號發送、接收方法、網路設備及終端
WO2018076749A1 (zh) 唤醒方法和设备
WO2021016766A1 (zh) 省电方法、装置、终端、接入网设备及可读存储介质
WO2014161472A1 (zh) 一种进行寻呼的方法、装置及系统
WO2018059020A1 (zh) 一种非连续接收的方法及相关装置
EP3554145B1 (en) Discontinuous reception method and device
WO2011038696A1 (zh) 一种调度信息传输的方法及系统
CN102932884B (zh) 一种实现drx的方法和系统
WO2013189070A1 (zh) 用户设备辅助信息上报的方法、用户设备和基站
WO2014161376A1 (zh) 一种激活时刻的计算方法及装置
JP2020519180A (ja) マルチキャストベアラ管理方法及び端末デバイス
WO2012116555A1 (zh) 非连续接收方法及装置
US10455506B2 (en) Method and apparatus for discontinuous reception
WO2020052572A1 (zh) 一种信息检测方法及装置
WO2022152054A1 (zh) 省电处理方法、装置及终端
JP2023513722A (ja) 不連続受信処理方法、端末、装置及び媒体
WO2021128341A1 (zh) 非连续接收控制方法、设备及存储介质
TW201826862A (zh) 用於非連續接收的訊號傳輸方法、終端設備和網路設備
WO2021016958A1 (zh) 省电信号的参数动态变更方法、装置、终端和介质
CN114286429A (zh) 一种通信方法及设备
WO2018149280A1 (zh) 数据接收方法及装置
WO2022083418A1 (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: 19846376

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

Country of ref document: EP

Effective date: 20210219