[go: up one dir, main page]

WO2022016543A1 - Procédé, dispositif et support de stockage informatique de communication - Google Patents

Procédé, dispositif et support de stockage informatique de communication Download PDF

Info

Publication number
WO2022016543A1
WO2022016543A1 PCT/CN2020/104552 CN2020104552W WO2022016543A1 WO 2022016543 A1 WO2022016543 A1 WO 2022016543A1 CN 2020104552 W CN2020104552 W CN 2020104552W WO 2022016543 A1 WO2022016543 A1 WO 2022016543A1
Authority
WO
WIPO (PCT)
Prior art keywords
mode
monitoring
wake
signal
discontinuous reception
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/104552
Other languages
English (en)
Inventor
Jianguo Liu
Chunli Wu
Mads LAURIDSEN
Tao Tao
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to CN202080006829.6A priority Critical patent/CN114846855B/zh
Priority to PCT/CN2020/104552 priority patent/WO2022016543A1/fr
Publication of WO2022016543A1 publication Critical patent/WO2022016543A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power 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/028—Power 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices and computer readable storage media of communication for a discontinuous reception (DRX) operation.
  • DRX discontinuous reception
  • a DRX operation is performed to reduce physical downlink control channel (PDCCH) monitoring which consumes a significant amount of power.
  • RRC radio resource control
  • the DRX operation there are two types of the DRX operation, i.e., a short DRX cycle and a long DRX cycle. If both the long DRX cycle and the short DRX cycle are configured for the terminal device, the short DRX cycle is used after a DRX inactivity timer runs out or a DRX Command medium access control (MAC) control element (CE) is received during the active time. Finally, the long DRX cycle is entered after the short DRX timer runs out.
  • MAC medium access control
  • a network device possibly cannot acquire a channel for transmission of a PDCCH and a physical downlink shared channel (PDSCH) for transmission of a MAC CE due to a downlink listen-before-talk (LBT) failure.
  • PDSCH physical downlink shared channel
  • LBT downlink listen-before-talk
  • example embodiments of the present disclosure provide a solution for a DRX operation.
  • a method of communication comprises: monitoring, at a first device and from a second device, a first wake-up signal for a first mode of a discontinuous reception operation; and in response to receiving the first wake-up signal with a wake-up indication, performing the discontinuous reception operation in a second mode of the discontinuous reception operation.
  • a method of communication comprises: monitoring, at a first device and from a second device, a first wake-up signal for a first mode of a discontinuous reception operation; in the absence of the first wake-up signal, determining whether a first failure in a downlink control channel occurs; and in accordance with a determination that the first failure occurs, performing a second monitoring of a second wake-up signal for a second mode of the discontinuous reception operation.
  • a method of communication comprises: transmitting, at a second device and to a first device, a first wake-up signal for a first mode of a discontinuous reception operation for performance of the discontinuous reception operation in a second mode by the first device in response to receiving the first wake-up signal with a wake-up indication.
  • a method of communication comprises: transmitting, at a second device and to a first device, a first wake-up signal for a first mode of a discontinuous reception operation for performance of the discontinuous reception operation in a second mode by the first device in the absence of the first wake-up signal due to a failure in a downlink control channel.
  • a first device comprising: at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the first device to perform the method according to at least one of the first and second aspects.
  • a second device comprising: at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the second device to perform the method according to at least one of the third and fourth aspects.
  • a non-transitory computer readable medium comprises program instructions for causing an apparatus to perform the method according to at least one of the first and second aspects.
  • non-transitory computer readable medium comprises program instructions for causing an apparatus to perform the method according to at least one of the third and fourth aspects.
  • Fig. 1 illustrates an example communication network in which example embodiments of the present disclosure may be implemented
  • Fig. 2 illustrates a diagram of a DRX operation according to a conventional solution
  • Fig. 3A illustrates a flowchart illustrating a process of communication for a DRX operation according to some embodiments of the present disclosure
  • Fig. 3B illustrates a flowchart illustrating another process of communication for a DRX operation according to some embodiments of the present disclosure
  • Fig. 4 illustrates a diagram of an example DRX operation according to example embodiments of the present disclosure
  • Fig. 5 illustrates a diagram of another example DRX operation according to example embodiments of the present disclosure
  • Fig. 6 illustrates a flowchart of an example method of communication implemented at a first device according to example embodiments of the present disclosure
  • Fig. 7 illustrates a flowchart of another example method of communication implemented at a first device according to example embodiments of the present disclosure
  • Fig. 8 illustrates a flowchart of another example method of communication implemented at a first device according to example embodiments of the present disclosure
  • Fig. 9 illustrates a flowchart of an example method of communication implemented at a second device according to example embodiments of the present disclosure
  • Fig. 10 illustrates a flowchart of another example method of communication implemented at a second device according to example embodiments of the present disclosure
  • Fig. 11 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
  • FIG. 12 illustrates a block diagram of an example computer readable medium in accordance with example embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • suitable generation communication protocols including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the a
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
  • BS base station
  • AP access point
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • NR NB also referred to as a gNB
  • RRU Remote Radio Unit
  • RH radio header
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/
  • Fig. 1 illustrates an example communication network 100 in which embodiments of the present disclosure can be implemented.
  • the network 100 includes a first device 110 and a second device 120 serving the second device 120.
  • the first device 110 is shown as a terminal device and the second device 120 is shown as a network device.
  • the network 100 may include any suitable number of first and second devices adapted for implementing embodiments of the present disclosure.
  • the first device 110 and the second device 120 may communicate with each other via a channel such as a wireless communication channel.
  • the communications in the network 100 may conform to any suitable standards including, but not limited to, LTE, LTE-evolution, LTE-advanced (LTE-A) , wideband code division multiple access (WCDMA) , code division multiple access (CDMA) and global system for mobile communications (GSM) and the like.
  • the communications may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols.
  • the first device 110 needs to monitor a downlink control channel such as a PDCCH from the second device 120.
  • the PDCCH monitoring consumes a significant amount of power at the first device 110.
  • the first device 110 may be configured to perform a DRX operation.
  • the DRX operation may comprise two operation modes, i.e., a long DRX cycle and a short DRX cycle.
  • Some services such as voice-over Internet protocol (IP) are characterized by periods of regular transmission and followed by periods of no or very little activity.
  • IP voice-over Internet protocol
  • the short DRX cycle can optionally be configured in addition to the long DRX cycle.
  • the short DRX cycle is used after a DRX inactivity timer runs out, and the long DRX cycle is entered after the short DRX timer runs out.
  • a terminal device will only start the DRX inactivity timer after a PDCCH occasion in which a PDCCH indicates a new uplink or downlink transmission, and then will start a DRX short cycle timer in the first symbol after an expiry of the DRX inactivity timer.
  • the short DRX cycle is used upon a DRX command MAC CE is received during the active time (e.g., when DRX on duration or DRX inactivity timer is running) , and the long DRX cycle is entered after the short DRX timer runs out.
  • a terminal device needs to monitor a PDCCH during the active time of the long DRX cycle and check whether it receives the DRX command MAC CE from a network device. If receiving the DRX command MAC CE, the terminal device will start a DRX short cycle timer in the first symbol after the end of the DRX command MAC CE reception.
  • a LBT operation is required to be performed before transmission in unlicensed band according to the regulatory requirements in certain regions in order to achieve coexistence fairness with other radio access technologies (RATs) (e.g. new radio-unlicensed (NR-U) /license assisted access (LAA) /Wi-Fi) .
  • RATs radio access technologies
  • NR-U new radio-unlicensed
  • LAA license assisted access
  • Wi-Fi wireless local area network
  • ED maximum energy detection
  • Release-16 NR-U if a network device needs to access the channel for downlink transmission, it shall follow the downlink channel access procedure defined in TS 37.213. In this case, for unlicensed deployment, the network device possibly cannot acquire the channel for transmission of PDCCH and PDSCH for transmission of MAC CE due to a downlink LBT failure.
  • a wake-up signal is provided to a terminal device via a PDCCH prior to the DRX on duration of the long DRX cycle.
  • the WUS is also known as downlink control information (DCI) -based power saving signal (DCI with cyclic redundancy check (CRC) scrambled by a power saving-radio network temporary identifier (PS-RNTI) , also referred to as DCP) .
  • DCI downlink control information
  • CRC cyclic redundancy check
  • PS-RNTI power saving-radio network temporary identifier
  • the terminal device will wake up and monitor the PDCCH during the on duration if a wake-up indication bit of the WUS is 1, and the terminal device will not wake up if the wake-up indication bit is 0.
  • a ps-Wakeup bit can be defined to control whether the terminal device wakes up or not if the DCP is not detected.
  • the terminal device does not monitor for the DCP during the active time and that the WUS only applies to monitoring for DRX on duration belonging to the long DRX cycle.
  • the DCP is configured only for the long DRX cycle.
  • a terminal device is configured to monitor the DCP prior to the long DRX cycle to determine whether to wake up or not. If the terminal device doesn’t detect the DCP due to a downlink LBT failure, and the ps-Wakeup bit indicates that the terminal device does not wake up, the terminal device will not wake up to monitor PDCCH during the DRX on duration. In this case, the terminal device will furthermore not start the DRX short cycle timer for use of the short DRX cycle, because neither the DRX inactivity timer expires nor the DRX command MAC CE is transmitted.
  • Fig. 2 illustrates a diagram 200 of a DRX operation according to a conventional solution.
  • the terminal device is configured with both short DRX cycle and long DRX cycle.
  • a DRX inactive timer (denoted as drx-InactiveTimer) is set to 3 slots
  • an on duration timer (denoted as onDurationTimer) is set to 2 slots
  • a short DRX cycle (denoted as shortDrxCycle) is set to 5 slots
  • a long DRX cycle (denoted as longDrxCycle) is set to 10 slots
  • an offset for start of a short DRX cycle (denoted as drxStarOffset) is set to 0
  • a short DRX cycle timer (denoted as drxShortCycleTimer) is set to 3 slots.
  • sign “S” denotes a LBT success for WUS
  • sign “I” denote
  • the terminal device if the terminal device receives the WUS prior to the long DRX cycle in slot#0 of SFN#0, it will monitor PDCCH during active time of the long DRX cycle. If the terminal device receives any PDCCH for new uplink or downlink transmission in the slot#0 of the SFN#0, it will start the DRX inactivity timer. After the DRX inactivity timer expires, the terminal device will start the DRX short cycle timer from the slot#4 of SFN#0 and thus use the short DRX cycle.
  • the terminal device cannot receive the WUS prior to the long DRX cycle in SFN#2 due to a downlink LBT failure, as shown by 201, it will skip the PDCCH monitoring until next long DRX cycle. So, there is no chance to start the DRX short cycle timer for use of the short DRX cycle.
  • the network device is still possibly not able to acquire the channel for transmission of PDCCH during on duration of the long DRX cycle even if it transmits the WUS prior to the long DRX cycle. If the terminal device doesn’t receive PDCCH for indication of new uplink or downlink transmission or a DRX command MAC CE, the terminal device won’t start the DRX short cycle timer for use of the short DRX cycle. If the short DRX cycle is configured but cannot be used due to the LBT, it’s obvious that the traffic latency associated to the short DRX cycle will be increased.
  • the ps-Wakeup bit can be defined to control whether the terminal device wakes up or not if the terminal device does not detect the DCP outside the active time. If the ps-Wakeup bit indicates wake up of the terminal device and the DCP associated with the long DRX cycle has not been received, the terminal device will start the DRX on duration timer after a DRX slot offset from the beginning of the subframe. Otherwise, the terminal device will skill PDCCH monitoring for the current DRX cycle for power saving.
  • the ps-Wakeup bit can be defined to wake up the terminal device to monitor PDCCH during active time of the long DRX cycle even if the network device is blocked for WUS transmission prior to the long DRX cycle due to a downlink LBT failure.
  • the solution may cause extra power consumption as the terminal device needs to monitor the PDCCH during active time of long DRX cycle even if the network device would not schedule the terminal device. Furthermore, the network device needs to transmit the WUS to inform the terminal device not to wake-up even if it would not schedule the terminal device, which will introduce extra downlink resource overhead. Thus, the network device would not prefer to configure the ps-Wakeup bit for a DRX operation. As a result, the terminal device is still not able to use the short DRX cycle if the network device can’t get a channel for transmission of PDCCH during active time of the long DRX cycle due to a downlink LBT failure.
  • a long DRX cycle is also referred to as a first mode of DRX operation
  • a short DRX cycle is also referred to as a second mode of DRX operation.
  • a WUS for convenience, also referred to as a first WUS herein
  • the WUS comprises a wake-up indication
  • the second mode will be started.
  • a message for convenience, also referred to as a first message herein
  • This aspect is applicable for licensed and unlicensed band or can be explicitly configurable whether to apply such behavior.
  • a monitoring for convenience, also referred to as a second monitoring herein
  • a WUS for convenience, also referred to as a second WUS herein
  • the terminal device can be specified or configured to skip further monitoring for the second mode.
  • a message for convenience, also referred to as a third message herein
  • This aspect is applicable for unlicensed band or can be explicitly configurable.
  • an efficient mechanism can be provided for better support of a short DRX cycle with low latency and power consumption in licensed and unlicensed bands.
  • the short DRX cycle is enabled when transmission of either WUS or PDCCH associated with the long DRX cycle is blocked due to a failure in a downlink channel such as a downlink LBT failure.
  • Embodiments of the present disclosure may introduce or involve the following messages and information to control the use of the first and second modes:
  • a first message for example, also referred to as a ps-ShortCycle-WakeUp message herein
  • the first message may comprise an indication bit. The value of the indication bit can be arbitrarily set.
  • a second message (for example, also referred to as a ps-Wakeup bit herein) as to whether the first device 110 wakes up in the first mode.
  • a second message indicates whether the first monitoring herein of a downlink control channel in the first mode is to be started in absence of the WUS.
  • the third message may comprise an indication bit.
  • the value of the indication bit can be arbitrarily set.
  • Fig. 3A illustrates a flowchart 301 illustrating a process of communication for a DRX operation according to some embodiments of the present disclosure.
  • the second device 120 may transmit 301 a first WUS for a first mode of a DRX operation to the first device 110.
  • the first WUS may indicate the first device 110 to wake up.
  • the first WUS may indicate the first device 110 to not wake up.
  • the first WUS may comprise an indication bit. In some embodiments, if the indication bit is 1, it is indicated that the first device 110 wakes up, and if the indication bit is 0, it is indicated that the first device 110 does not wake up.
  • 1 of the indication bit may also be used to indicate that the first device 110 does not wake up, and 0 of the indication bit may also be used to indicate that the first device 110 wakes up.
  • the present application does not make limitation for this.
  • the second device 120 may also transmit 302 any of the above-listed messages and information to the first device 110. In some embodiments, the second device 120 may transmit any of these messages and information via a higher layer RRC signaling. In some embodiments, the second device 120 may transmit any of these messages and information via a lower layer physical signaling. For example, the second device 120 may configure the first message through a WUS or DCP associated with the first mode. It should be noted that the transmission of these messages and information can be performed in any other suitable ways.
  • the first device 110 monitors 303 the first WUS for the first mode. Assuming that the first device 110 receives the first WUS. In some embodiments, if the first device 110 receives the first WUS with a non-wake-up indication, the first device 110 may continue to monitor the first WUS.
  • the terminal device 120 performs 306 the DRX operation in a second mode of the DRX operation. That is, the short DRX cycle is used.
  • the first device 110 may also start a DRX on duration timer for the first mode.
  • the first device 110 may determine 305, from the first message, whether the second mode of the DRX operation is to be started, and if determining that the second mode is to be started, the terminal device 120 may perform 306 the DRX operation in the second mode.
  • the first device 110 may start a short cycle timer for the second mode and monitor a downlink control channel such as a PDCCH according to short cycle until the short cycle timer expires. In this way, the short DRX cycle is enabled. In some alternative embodiments, the first device 110 may start the short cycle timer after an offset (denoted as drx-StartOffset herein) from the beginning of the subframe.
  • drx-StartOffset an offset
  • drx-StartOffset [ (SFN ⁇ 10) + subframe number] modulo (drx-LongCycle) , where SFN denotes a system frame number, and drx-LongCycle denotes a length of the first mode.
  • the short cycle timer may be started upon reception of the WUS. In some embodiments, the short cycle timer may be started upon the starting of the OnDuration timer after the reception of the WUS. Of course, this is merely an example, and any other suitable ways are also feasible for the start of the short DRX cycle.
  • duration of the short cycle timer can be determined in a predefined manner.
  • the duration of the short cycle timer may be the minimum value determined by min (drx-ShortCycleTimer, the remaining short DRX cycles available in the current long DRX cycle (i.e. until next OnDuration of the long DRX cycle) ) .
  • the duration of the short cycle timer may be configured to be one of drx-ShortCycleTimer and the remaining short DRX cycles available in the current long DRX cycle.
  • the duration of the short cycle timer may be determined by using a separately configured timer.
  • the duration of the short cycle timer may be configured by a higher layer RRC signaling.
  • the duration of the short cycle timer applied for the current short DRX cycle may be configured through the DCP or the WUS.
  • the first device 110 may start 307 the first monitoring in the first mode. In some embodiments, the first device 110 may start a DRX on duration timer for the first mode and monitor the downlink control channel during the active time of the first mode.
  • the first device 110 may determine 308 whether the downlink control channel is blocked due to a failure in the downlink control channel. In other words, the first device 110 may perform transmission detection of the second device 120 to determine whether the second device 120 can get the channel during the active time of the first mode. In some embodiments, the first device 110 may perform the transmission detection in unlicensed band based on a downlink reference signal such as a demodulation reference signal (DMRS) or other reference signals. In some alternative embodiments, the first device 110 may perform the transmission detection in unlicensed band based on DCI such as group common (GC) -PDCCH or UE-specific PDCCH.
  • a downlink reference signal such as a demodulation reference signal (DMRS) or other reference signals.
  • DMRS demodulation reference signal
  • the first device 110 may perform the transmission detection in unlicensed band based on DCI such as group common (GC) -PDCCH or UE-specific PDCCH.
  • the first device 110 may perform the DRX operation based on an existing procedure in Release 16 NR. For example, the first device 110 may start a DRX inactivity timer after the PDCCH occasion in which a PDCCH indicates a new downlink or uplink transmission, and may start the use of the second mode at the expiry of the DRX inactivity timer. Alternatively, the first device 110 may monitor the PDCCH during active time of the first mode, and if it receives a DRX command MAC CE from the second device 120, the first device 110 may start the use of the second mode in the first symbol after the end of DRX command MAC CE reception. Other details are omitted here to avoid confusing the present disclosure.
  • the first device 110 may determine 308, from the third message, whether the second monitoring of the second WUS for the second mode is to be started.
  • the first device 110 may start 309 the second monitoring.
  • the first device 110 may determine occasions for the second monitoring. For example, the first device 110 may receive information about the occasions via a higher layer RRC signaling, and determine the occasions from the information. In some embodiments, the information may comprise a value of a configured timer.
  • the first device 110 may monitor the second WUS within the configured timer. In some alternative embodiments, the first device 110 may monitor the second WUS until next long cycle. In some alternative embodiments, the first device 110 may monitor the second WUS until the second WUS is received.
  • the second device 120 may transmit 310 the second WUS at the occasions.
  • the first device 110 may determine 311 whether the second WUS is received at one of the occasions for the second monitoring. If determining that the second WUS is received at one of the occasions, the first device 110 may stop 312 the second monitoring at the occasions. In this way, power saving at the first device 110 is achieved by associating WUS monitoring at one occasion with multiple short DRX cycles. Then, the first device 110 may perform 313 the DRX operation in the second mode.
  • the operation as shown by 313 is similar with that as shown by 306, and thus its details are omitted here.
  • the first device 110 may return to monitor the first WUS for the first mode. If determining from the third message that the second monitoring is not to be started, the first device 110 may also return to monitor the first WUS for the first mode. That is, the first device 110 may skip further monitoring of short DRX cycles until next long DRX cycle occurs.
  • Fig. 4 illustrates a diagram 400 of an example DRX operation according to example embodiments of the present disclosure.
  • the first device 110 may detect the first WUS prior to the long DRX cycle but does not monitor transmission from the second device 120, e.g., due to a downlink LBT failure during active time of long DRX cycle, or if the first device 110 does not detect the first WUS prior to the long DRX cycle, e.g., due to a LBT failure, the first device 110 will be trigged to monitor the second WUS for short DRX cycles until next long DRX cycle.
  • a DRX inactive timer (denoted as drx-InactiveTimer) is set to 3 slots
  • an on duration timer (denoted as onDurationTimer) is set to 2 slots
  • a short DRX cycle (denoted as shortDrxCycle) is set to 5 slots
  • a long DRX cycle (denoted as longDrxCycle) is set to 20 slots
  • an offset for start of a short DRX cycle (denoted as drxStarOffset) is set to 0
  • a short DRX cycle timer (denoted as drxShortCycleTimer) is set to 3 slots.
  • ps-ShortDrxCycle-WakeUp is configured with “FALSE” , which indicates that the first device 110 does not wake up
  • ps-ShortDrxCycle-WusMonitor is configured with “TURE” , which indicates that a second monitoring for a second WUS is to be started.
  • sign “x” for WUS denotes that the WUS is not detected
  • sign “ ⁇ ” for WUS denotes that the WUS is detected.
  • sign “x” for drx-OnDurationTimer denotes that the OnDurationTimer is not started
  • sign “ ⁇ ” for drx-OnDurationTimer denotes that the OnDurationTimer is started.
  • the first device 110 will stop the second monitoring for short DRX cycles, and start the short cycle timer with duration of 2 short DRX cycles after the DCP reception, as denoted as Drx-ShortCycleTimerWus and shown by 401, and then monitor during on duration of short DRX cycles until the short cycle timer expires at the end of the SFN#1.
  • Drx-ShortCycleTimerWus duration of 2 short DRX cycles after the DCP reception
  • Fig. 3B illustrates a flowchart 301 illustrating another process of communication for a DRX operation according to some embodiments of the present disclosure.
  • the second device 120 may transmit 320 a first WUS for a first mode of a DRX operation to the first device 110.
  • the operation as shown by 320 is similar with that as shown by 301 in Fig. 3A, and thus its details are omitted here.
  • the second device 120 may also transmit 321 any of the above-listed messages and information to the first device 110.
  • the operation as shown by 321 is similar with that as shown by 302 in Fig. 3A, and thus its details are also omitted here.
  • the first device 110 monitors 322 the first WUS for the first mode. Assuming that the first device 110 does not receive the first WUS. The first device 110 determines 323 whether the first WUS is blocked due to a failure (for convenience, also referred to as a first failure herein) of a downlink control channel. If determining that the first WUS is blocked due to the first failure, the first device 110 performs 327 a second monitoring of a second WUS for a second mode of the DRX operation.
  • a failure for convenience, also referred to as a first failure herein
  • the first device 110 may determine 324 from the second message whether a first monitoring of a downlink control channel in the first mode is to be started. If determining from the second message that the first monitoring is to be stated, the first device 110 may perform 325 the DRX operation in the second mode. In this way, the short cycle is used. In some embodiments, upon determining the first monitoring is to be started, the first device 110 may determine from the first message whether the second mode is to be started. If determining that the second mode is to be started, the first device 110 may perform 325 the DRX operation in the second mode. If determining that the second mode is not to be started, the first device 110 may operate in a similar process as shown by 307-313 in Fig. 3A. Its details are not repeated here for concise.
  • the first device 110 may perform 327 the second monitoring of the second WUS. In some embodiments, upon determining that the first monitoring is not to be started, the first device 110 may determine 326 from the third message whether the second monitoring is to be started. If determining that the second monitoring is to be started, the first device 110 may perform 327 the second monitoring.
  • the first device 110 may determine occasions for the second monitoring. For example, the first device 110 may receive information about the occasions via a higher layer RRC signaling, and determine the occasions from the information. In some embodiments, the information may comprise a value of a configured timer. In some embodiments, the first device 110 may monitor the second WUS within the configured timer. In some alternative embodiments, the first device 110 may monitor the second WUS until next long cycle. In some alternative embodiments, the first device 110 may monitor the second WUS until the second WUS is received.
  • the second device 120 may transmit 328 the second WUS at the occasions.
  • the first device 110 may determine 329 whether the second WUS is received at one of the occasions for the second monitoring. If determining that the second WUS is received at one of the occasions, the first device 110 may stop 330 the second monitoring at the occasions. In this way, power saving at the first device 110 is achieved by associating WUS monitoring at one occasion with multiple short DRX cycles. Then, the first device 110 may perform 331 the DRX operation in the second mode.
  • the operation as shown by 331 is similar with that as shown by 306 in Fig. 3A, and thus its details are omitted here for concise.
  • the first device 110 may return to monitor the first WUS for the first mode. If determining from the third message that the second monitoring is not to be started, the first device 110 may also return to monitor the first WUS for the first mode. That is, the first device 110 may skip further monitoring of short DRX cycles until next long DRX cycle occurs.
  • the operations as shown by 327-331 are similar with that as shown by 309-313 in Fig. 3A, and their details are omitted here for concise.
  • Fig. 5 illustrates a diagram 500 of another example DRX operation according to example embodiments of the present disclosure. Assume that the first device 110 does not detect the first WUS prior to the long DRX cycle but the second message indicates that the first monitoring is to be started.
  • a DRX inactive timer (denoted as drx-InactiveTimer) is set to 3 slots
  • an on duration timer (denoted as onDurationTimer) is set to 2 slots
  • a short DRX cycle (denoted as shortDrxCycle) is set to 5 slots
  • a long DRX cycle (denoted as longDrxCycle) is set to 20 slots
  • an offset for start of a short DRX cycle (denoted as drxStarOffset) is set to 0
  • a short DRX cycle timer (denoted as drxShortCycleTimer) is set to 3 slots.
  • ps-ShortDrxCycle-WakeUp is configured with “TRUE” , which indicates that the first device 110 wakes up.
  • sign “x” denotes that the first WUS is not detected, and sign “ ⁇ ” denotes a start of a short DRX cycle.
  • the first device 110 may start drx-ShortCycleTimer with duration of 3 short DRX cycles from the beginning of on-duration occasion for the long DRX cycle (i.e. the slot#0 of SFN#0) in the case that the ps-ShortDrxCycle-WakeUp (i.e., the first message) indicates a start of the second mode, as shown by 501.
  • the above-listed values in this example are merely an example, and do not make limitation for the present disclosure.
  • embodiments of the present disclosure provide methods of communication implemented at a first device and at a second device. These methods will be described below with reference to Figs. 6 to 10.
  • Fig. 6 illustrates a flowchart of a method 600 of communication implemented at a first device according to example embodiments of the present disclosure.
  • the method 600 can be implemented at the first device 110 shown in Fig. 1.
  • the method 600 will be described with reference to Fig. 1. It is to be understood that method 600 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the first device 110 monitors a first WUS for a first mode of a DRX operation. In some embodiments, the first device 110 may monitor the first WUS in any suitable manner. At block 620, the first device 110 determines whether the first WUS with a wake-up indication is received. In some embodiments, upon receiving a first WUS, the first device 110 may determine whether the first WUS comprises a wake-up indication. In some embodiments, the first WUS may comprise a non-wake-up indication, i.e., the first device 110 does not wake up. In these embodiments, the first device 110 may return to block 610 to continue to monitor the first WUS.
  • the first WUS may comprise a wake-up indication, i.e., the first device 110 wakes up.
  • the first device 110 may start a DRX on duration timer for the first mode. In this way, the first mode is used, i.e., a long DRX cycle is started.
  • the process proceeds to block 630.
  • the first device 110 performs the DRX operation in the second mode.
  • the first device 110 may start a timer (for convenience, also referred to as a second timer herein) for duration of the second mode.
  • the timer is a ShortCycleTimer as mentioned above.
  • the first device 110 may monitor a downlink control channel (such as a PDCCH) until the second timer expires. In this way, one or more short DRX cycles can be started.
  • the first device 110 may start the short cycle timer after an offset (denoted as drx-StartOffset) from the beginning of the subframe.
  • drx-StartOffset [ (SFN ⁇ 10) + subframe number] modulo (drx-LongCycle) , where SFN denotes a system frame number, and drx-LongCycle denotes a length of the first mode.
  • the short cycle timer may be started upon reception of the WUS.
  • the short cycle timer may be started upon the starting of the OnDuration timer after the reception of the WUS.
  • this is merely an example, and any other suitable ways are also feasible for the start of the short DRX cycle.
  • the first device 110 may determine, from a first message (for example, ps-ShortCycle-WakeUp message) , whether a second mode of the DRX operation is to be started.
  • the first message is received from the second device 120 and indicates whether the second mode is to be started.
  • the first message may comprise an indication bit. A first value of the indication bit may indicate that the second mode is to be started, and a second value of the indication bit may indicate that the second mode is not to be started. The first and second values may be arbitrarily set. If determining that the second mode is to be started, the first device 110 may perform the DRX operation in the second mode. In this way, the short DRX cycle will be forcedly used.
  • the first device 110 may start a first monitoring of a downlink control channel in the first mode. For example, the first device 110 may monitor a PDCCH in the first mode. In some embodiments, the first device 110 may perform transmission detection of the second device 120 so as to determine whether the second device 120 can get the channel during the active time of the first mode. In some embodiments, the first device 110 may perform the transmission detection in unlicensed band based on a downlink reference signal such as a DMRS. In some alternative embodiments, the first device 110 may perform the transmission detection in unlicensed band based on DCI such as GC-PDCCH or UE-specific PDCCH.
  • DCI such as GC-PDCCH or UE-specific PDCCH.
  • the first device 110 may skip monitoring of a second WUS for the second mode and continue to monitor the first WUS for the first mode. In this case, the short DRX cycle is not used. If determining that a failure in the downlink control channel occurs, the first device 110 may perform the second monitoring.
  • the first device 110 may determine from a third message (for example, ps-ShortCycle-WusMonitor message) whether the second monitoring is to be started. In some embodiments, the third message is received from the second device 120 via any suitable ways. If determining from the third message that the second monitoring is not to be stated, the first device 110 may return to monitor the first WUS. If determining from the third message that the second monitoring is to be stated, the first device 110 may perform the second monitoring.
  • a third message for example, ps-ShortCycle-WusMonitor message
  • the first device 110 may determine occasions for the second monitoring. For example, the first device 110 may receive information about the occasions via a higher layer RRC signaling, and determine the occasions from the information. In some embodiments, the information may comprise a value of a configured timer. In some embodiments, the first device 110 may monitor the second WUS within the configured timer. In some alternative embodiments, the first device 110 may monitor the second WUS until next long cycle. In some alternative embodiments, the first device 110 may monitor the second WUS until the second WUS is received.
  • the first device 110 may stop the second monitoring at the occasions. In this way, power saving at the first device 110 is enhanced by associating WUS monitoring at one occasion with multiple short DRX cycles. Then the first device 110 may perform the DRX operation in the second mode, as described with reference to block 630. Thereby, the short DRX cycle is used.
  • an enhanced DRX mechanism is provided for better support of short DRX cycle with low latency and power consumption in licensed and unlicensed bands in the case that a WUS for a long DRX cycle is received.
  • the use of short DRX cycle is enabled when transmission of a PDCCH associated to the long DRX cycle is blocked due to a failure in a downlink control channel such as a LBT failure.
  • Fig. 7 illustrates a flowchart of another method 700 of communication implemented at a first device according to example embodiments of the present disclosure.
  • the method 700 can be implemented at the first device 110 shown in Fig. 1.
  • the method 700 will be described with reference to Fig. 1. It is to be understood that method 700 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the first device 110 monitors a first WUS for a first mode of a DRX operation. In some embodiments, the first device 110 may monitor the first WUS in any suitable manner. At block 720, the first device 110 determines whether the first WUS is blocked due to a failure (for convenience, also referred to as a first failure) in a downlink channel.
  • a failure for convenience, also referred to as a first failure
  • the first device 110 may perform transmission detection of the second device 120 so as to determine whether the second device 120 can acquire the channel during the active time of the first mode. In some embodiments, the first device 110 may perform the transmission detection in unlicensed band based on a downlink reference signal such as a DMRS. In some alternative embodiments, the first device 110 may perform the transmission detection in unlicensed band based on DCI such as GC-PDCCH or UE-specific PDCCH.
  • DCI such as GC-PDCCH or UE-specific PDCCH.
  • the first device 110 may continue to monitor the first WUS for the first mode. In this case, the short DRX cycle is not used. If determining that the first failure occurs, that is, the first WUS is blocked due to the first failure, at block 730, the first device 110 performs a second monitoring of a second WUS for a second mode of the DRX operation.
  • the first device 110 may determine from a third message (for example, ps-ShortCycle-WusMonitor message) whether the second monitoring is to be started. In some embodiments, the third message is received from the second device 120 via any suitable ways. If determining from the third message that the second monitoring is not to be stated, the first device 110 may return to monitor the first WUS. If determining from the third message that the second monitoring is to be stated, the first device 110 may perform the second monitoring.
  • a third message for example, ps-ShortCycle-WusMonitor message
  • the first device 110 may determine occasions for the second monitoring. For example, the first device 110 may receive information about the occasions via a higher layer RRC signaling, and determine the occasions from the information. In some embodiments, the information may comprise a value of a configured timer (for convenience, also referred to as a first timer herein) . In some embodiments, the first device 110 may monitor the second WUS within the configured timer. In some alternative embodiments, the first device 110 may monitor the second WUS until next long cycle. In some alternative embodiments, the first device 110 may monitor the second WUS until the second WUS is received.
  • a configured timer for convenience, also referred to as a first timer herein
  • the first device 110 may stop the second monitoring at the occasions. In this way, power saving at the first device 110 is enhanced by associating WUS monitoring at one occasion with multiple short DRX cycles. Then the first device 110 may perform the DRX operation in the second mode. Thereby, the short DRX cycle is used.
  • the first device 110 may start a timer (for convenience, also referred to as a second timer herein) for duration of the second mode.
  • the timer is a ShortCycleTimer as mentioned above.
  • the first device 110 may monitor a downlink control channel (such as a PDCCH) until the second timer expires. In this way, one or more short DRX cycles can be started.
  • the first device 110 may start the second timer after an offset (denoted as drx-StartOffset) from the beginning of the subframe.
  • drx-StartOffset [ (SFN ⁇ 10) + subframe number] modulo (drx-LongCycle) , where SFN denotes a system frame number, and drx-LongCycle denotes a length of the first mode.
  • the short cycle timer may be started upon reception of the WUS. In some embodiments, the short cycle timer may be started upon the starting of the OnDuration timer after the reception of the WUS. Of course, this is merely an example, and any other suitable ways are also feasible for the start of the short DRX cycle.
  • an enhanced DRX mechanism is provided for better support of short DRX cycle with low latency and power consumption in licensed and unlicensed bands in the case that no WUS for a long DRX cycle is received.
  • the use of short DRX cycle is enabled when transmission of a WUS associated to the long DRX cycle is blocked due to a failure in a downlink channel such as a LBT failure.
  • Fig. 8 illustrates a flowchart of another method 800 of communication implemented at a first device according to example embodiments of the present disclosure.
  • the method 800 can be implemented at the first device 110 shown in Fig. 1.
  • the method 800 will be described with reference to Fig. 1.
  • method 800 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the solutions described with reference to Figs. 6 and 7 can be used separately to support the use of short DRX cycle, and also can be combined to support the use of short DRX cycle. Although the combination is described in connection with Fig. 8, it can be carried out in any other suitable ways, and is not limited to that in Fig. 8.
  • the first device 110 may determine whether a first WUS for a first mode of DRX operation (i.e., long DRX cycle) is received from the second device 120. If the first device 110 receives the first WUS, the process proceeds to block 802. At block 802, the first device 110 may determine whether the first WUS comprises a wake-up indication. If determining that the first WUS comprises a non-wake-up indication, the first device 110 will continue to monitor the first WUS. If determining that the first WUS comprises a wake-up indication, the first device 110 may start a DRX on duration timer for the long DRX cycle, and the process proceeds to block 803.
  • a first WUS for a first mode of DRX operation i.e., long DRX cycle
  • the first device 110 may determine, from the first message (for example, ps-ShortCycle-WakeUp message) , whether a second mode of DRX operation (i.e., short DRX cycle) is to be started.
  • the first message is received from the second device 120 via any suitable ways. If determining that the second mode is to be started, At block 804, the first device 110 may perform the DRX operation in the second mode. In this way, the short DRX cycle will be used.
  • the first device 110 may start a timer (for example, a ShortCycleTimer, also referred to as a second timer for convenience) for duration of the second mode, and monitor a downlink control channel such as a PDCCH until the timer expires.
  • a timer for example, a ShortCycleTimer, also referred to as a second timer for convenience
  • PDCCH downlink control channel
  • the process proceeds to block 805.
  • the first device 110 may determine whether the first WUS is blocked due to a failure (also referred to as a first failure for convenience) in downlink channel.
  • the first device 110 may perform transmission detection of the second device 120 so as to determine whether the second device 120 can get the channel during the active time of the first mode.
  • the first device 110 may perform the transmission detection in unlicensed band based on a downlink reference signal such as a DMRS.
  • the first device 110 may perform the transmission detection in unlicensed band based on DCI such as GC-PDCCH or UE-specific PDCCH.
  • the first device 110 may return to block 801 and continue to monitor the first WUS for the first mode. In this case, the short DRX cycle is not used. If determining that the first failure occurs, that is, the first WUS is blocked due to the first failure, the process proceeds to block 806.
  • the first device 110 may determine, from the second message (for example, ps-Wakeup bit) , whether a first monitoring of a downlink control channel is to be started.
  • the second message is received from the second device 120 via any suitable ways. If determining that the first monitoring is to be started, the first device 110 may also start a DRX on duration timer for the long DRX cycle, and the process proceeds to block 803. If determining that the first monitoring is not to be started, the process proceeds to block 809 which will be described later.
  • the process proceeds to block 807.
  • the first device 110 may start the first monitoring of the downlink control channel (for example, a PDCCH) in the first mode.
  • the first device 110 may perform transmission detection of the second device 120 so as to determine whether the second device 120 can get the channel during the active time of the first mode.
  • the first device 110 may perform the transmission detection in unlicensed band based on a downlink reference signal such as a DMRS.
  • the first device 110 may perform the transmission detection in unlicensed band based on DCI such as GC-PDCCH or UE-specific PDCCH.
  • the process proceeds to block 814.
  • the first device 110 may perform the DRX operation based on an existing procedure in Release 16 NR. For example, the first device 110 may start a DRX inactivity timer after the PDCCH occasion in which a PDCCH indicates a new downlink or uplink transmission, and may start the use of the second mode at the expiry of the DRX inactivity timer.
  • the first device 110 may monitor the PDCCH during active time of the first mode, and if it receives a DRX command MAC CE from the second device 120, the first device 110 may start the use of the second mode in the first symbol after the end of DRX command MAC CE reception.
  • Other details are omitted here to avoid confusing the present disclosure.
  • the process proceeds to block 809.
  • the first device 110 may determine, from the third message (for example, ps-ShortCycle-WusMonitor message) , whether a second monitoring of a second WUS for the second mode is to be started.
  • the third message is received from the second device 120 via any suitable ways. If determining from the third message that the second monitoring is not to be stated, the first device 110 may return to monitor the first WUS at block 801.
  • the process proceeds to block 810.
  • the first device 110 may perform the second monitoring.
  • the first device 110 may determine occasions for the second monitoring.
  • the first device 110 may receive information about the occasions via a higher layer RRC signaling, and determine the occasions from the information.
  • the information may comprise a value of a configured timer (for convenience, also referred to as a first timer herein) .
  • the first device 110 may monitor the second WUS within the configured timer.
  • the first device 110 may monitor the second WUS until next long cycle.
  • the first device 110 may monitor the second WUS until the second WUS is received.
  • the first device 110 may determine whether the second WUS is received at one of the occasions for the second monitoring. If determining that the second WUS is received at one of the occasions, at block 812, the first device 110 may stop the second monitoring at the occasions. In this way, power saving at the first device 110 is enhanced by associating WUS monitoring at one occasion with multiple short DRX cycles. Then the process proceeds to block 804, where the first device 110 performs the DRX operation in the second mode as described above. Thereby, the short DRX cycle is used.
  • an enhanced DRX mechanism is provided for better support of short DRX cycle with low packet latency and low power consumption in licensed and unlicensed bands, which enable use of short DRX cycle if transmission of either WUS or PDCCH associated to the long DRX cycle is blocked due to a failure in downlink channel.
  • Fig. 9 illustrates a flowchart of a method 900 of communication implemented at a second device according to example embodiments of the present disclosure.
  • the method 900 can be implemented at the second device 120 shown in Fig. 1.
  • the method 900 will be described with reference to Fig. 1. It is to be understood that method 900 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the second device 120 transmits, to the first device 110, a first WUS for a first mode of DRX operation for performance of the DRX operation in a second mode by the first device 110 in response to receiving the first WUS with a wake-up indication.
  • the second device 120 may also transmit, to the first device 110, a first message (for example, ps-ShortCycle-WakeUp message) as to whether a second mode of DRX operation is to be started.
  • the second device 120 may transmit the first message through DCP associated with the first WUS.
  • the second device 120 may transmit the first message via a higher layer RRC signaling separately from the first WUS. It should be noted that the present application does not make limitation for the transmission of the first WUS and the first message.
  • the second device 120 may transmit, to the first device 110, a second message (for example, ps-Wakeup bit) as to whether a first monitoring of a downlink control channel in the first mode is to be started.
  • the second device 120 may transmit the second message via a higher layer RRC signaling.
  • the second device 120 may transmit the second message via a lower layer physical signaling. It should be noted that the present application does not make limitation for the transmission of the second message.
  • the second device 120 may transmit, to the first device 110, a third message (for example, ps-ShortCycle-WusMonitor message) as to whether a second monitoring of a second wake-up signal for the second mode is to be started.
  • a third message for example, ps-ShortCycle-WusMonitor message
  • the second device 120 may transmit the third message via a higher layer RRC signaling.
  • the second device 120 may transmit the third message via a lower layer physical signaling. It should be noted that the present application does not make limitation for the transmission of the third message.
  • the second device 120 may transmit, to the first device 110, information (for example, search space set configuration for short DRX cycle) about occasions for the second monitoring, and transmit, to the first device 110, the second wake-up signal at one of the occasions.
  • the second device 120 may transmit the information about the occasions via a higher layer RRC signaling. It should be noted that the present application does not make limitation for the transmission of this information.
  • an efficient mechanism can be provided to control the use of the short DRX cycle when transmission of either WUS or PDCCH associated with the long DRX cycle is blocked due to a failure in a downlink control channel.
  • the short DRX cycle is better supported with low packet latency and low power consumption in licensed and unlicensed bands.
  • Fig. 10 illustrates a flowchart of a method 1000 of communication implemented at a second device according to example embodiments of the present disclosure.
  • the method 1000 can be implemented at the second device 120 shown in Fig. 1.
  • the method 1000 will be described with reference to Fig. 1. It is to be understood that method 1000 may further include additional blocks not shown and/or omit some shown blocks, and the scope of the present disclosure is not limited in this regard.
  • the second device 120 transmits, to the first device 110, a first WUS for a first mode of DRX operation for performance of the DRX operation in a second mode by the first device 110 in the absence of the first WUS due to a failure in downlink channel.
  • the second device 120 may also transmit, to the first device 110, a first message (for example, ps-ShortCycle-WakeUp message) as to whether a second mode of DRX operation is to be started.
  • the second device 120 may transmit the first message through DCP associated with the first WUS.
  • the second device 120 may transmit the first message via a higher layer RRC signaling separately from the first WUS. It should be noted that the present application does not make limitation for the transmission of the first WUS and the first message.
  • the second device 120 may transmit, to the first device 110, a second message (for example, ps-Wakeup bit) as to whether a first monitoring of a downlink control channel in the first mode is to be started.
  • the second device 120 may transmit the second message via a higher layer RRC signaling.
  • the second device 120 may transmit the second message via a lower layer physical signaling. It should be noted that the present application does not make limitation for the transmission of the second message.
  • the second device 120 may transmit, to the first device 110, a third message (for example, ps-ShortCycle-WusMonitor message) as to whether a second monitoring of a second wake-up signal for the second mode is to be started.
  • a third message for example, ps-ShortCycle-WusMonitor message
  • the second device 120 may transmit the third message via a higher layer RRC signaling.
  • the second device 120 may transmit the third message via a lower layer physical signaling. It should be noted that the present application does not make limitation for the transmission of the third message.
  • the second device 120 may transmit, to the first device 110, information (for example, search space set configuration for short DRX cycle) about occasions for the second monitoring, and transmit, to the first device 110, the second wake-up signal at one of the occasions.
  • the second device 120 may transmit the information about the occasions via a higher layer RRC signaling. It should be noted that the present application does not make limitation for the transmission of this information.
  • an efficient mechanism can be provided to control the use of the short DRX cycle when transmission of either WUS or PDCCH associated with the long DRX cycle is blocked due to a failure in a downlink channel such as a downlink LBT failure.
  • the short DRX cycle is better supported with low latency and power consumption in licensed and unlicensed bands.
  • an apparatus capable of performing any of the method 600 may comprise means for performing the respective steps of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for monitoring, at a first device and from a second device, a first wake-up signal for a first mode of a discontinuous reception operation; and means for in response to receiving the first wake-up signal with a wake-up indication, performing the discontinuous reception operation in a second mode of the discontinuous reception operation.
  • the means for performing the discontinuous reception operation in the second mode comprises: means for determining from a first message whether a second mode of the discontinuous reception operation is to be started, the first message received from the second device; and means for in accordance with a determination that the second mode is to be started, performing the discontinuous reception operation in the second mode.
  • the apparatus further comprises: means for in accordance with a determination from the first message that the second mode is not to be started, starting a first monitoring of a downlink control channel in the first mode; and means for in accordance with a determination that a failure in the downlink control channel occurs, performing a second monitoring of a second wake-up signal for the second mode.
  • the means for performing the second monitoring comprises: means for determining from a third message whether the second monitoring is to be started, the third message received from the second device; and means for in accordance with a determination that the second monitoring is to be started, performing the second monitoring.
  • the means for performing the second monitoring comprises: means for determining occasions for the second monitoring; and means for determining whether the second wake-up signal is received at one of the occasions.
  • the apparatus further comprises: means for in accordance with a determination that the second wake-up signal is received, stopping the second monitoring at the occasions; and means for performing the discontinuous reception operation in the second mode.
  • the means of determining whether the second wake-up signal is received comprises at least one of: means of monitoring, within a first timer, whether the second wake-up signal is received; means of monitoring whether the second wake-up signal is received until the end of the first mode; and means of monitoring whether the second wake-up signal is received until the second wake-up signal is received.
  • the means of performing the discontinuous reception operation in the second mode comprises: means of starting a second timer for duration of the second mode; and means of monitoring a downlink control channel until the second timer expires.
  • the first mode is a long cycle of the discontinuous reception operation
  • the second mode is a short cycle of the discontinuous reception operation.
  • the first device is a terminal device
  • the second device is a network device.
  • an apparatus capable of performing any of the method 700 may comprise means for performing the respective steps of the method 700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises: means for monitoring, at a first device and from a second device, a first wake-up signal for a first mode of a discontinuous reception operation; means for in the absence of the first wake-up signal, determining whether a first failure in a downlink control channel occurs; and means for in accordance with a determination that the first failure occurs, performing a second monitoring of a second wake-up signal for a second mode of the discontinuous reception operation.
  • the means for performing the second monitoring comprises: means for determining from a second message whether a first monitoring of a downlink control channel in the first mode is to be started, the second message received from the second device; and means for in accordance with a determination from the second message that the first monitoring is not to be started, performing the second monitoring.
  • the apparatus further comprises: means for in accordance with a determination from the second message that the first monitoring is to be started, determining from a first message whether a second mode of the discontinuous reception operation is to be started, the first message received from the second device; and means for in accordance with a determination that the second mode is to be started, performing the discontinuous reception operation in the second mode.
  • the apparatus further comprises: means for in accordance with a determination that the second mode is not to be started, starting a first monitoring of a downlink control channel in the first mode; and means for in accordance with a determination that a second failure in the downlink control channel occurs, performing the second monitoring.
  • the means for performing the second monitoring comprises: means for determining from a third message whether the second monitoring is to be started, the third message received from the second device; and means for in accordance with a determination that the second monitoring is to be started, performing the second monitoring.
  • the means for performing the second monitoring comprises: means for determining occasions for the second monitoring; and means for determining whether the second wake-up signal is received at one of the occasions.
  • the apparatus further comprises: means for in accordance with a determination that the second wake-up signal is received, stopping the second monitoring at the occasions; and means for performing the discontinuous reception operation in the second mode.
  • the means for determining whether the second wake-up signal is received comprises at least one of: means for monitoring, within a first timer, whether the second wake-up signal is received; means for monitoring whether the second wake-up signal is received until the end of the first mode; and means for monitoring whether the second wake-up signal is received until the second wake-up signal is received.
  • the means for performing the discontinuous reception operation in the second mode comprises: means for starting a second timer for duration of the second mode; and means for monitoring a downlink control channel until the second timer expires.
  • the first mode is a long cycle of the discontinuous reception operation
  • the second mode is a short cycle of the discontinuous reception operation.
  • the first device is a terminal device
  • the second device is a network device.
  • an apparatus capable of performing any of the method 900 may comprise means for performing the respective steps of the method 900.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for transmitting, at a second device and to a first device, a first wake-up signal for a first mode of a discontinuous reception operation for performance of the discontinuous reception operation in a second mode by the first device in response to receiving the first wake-up signal with a wake-up indication.
  • an apparatus capable of performing any of the method 1000 may comprise means for performing the respective steps of the method 1000.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for transmitting, at a second device and to a first device, a first wake-up signal for a first mode of a discontinuous reception operation for performance of the discontinuous reception operation in a second mode by the first device in the absence of the first wake-up signal due to a failure in a downlink control channel.
  • the apparatus further comprises at least one of: means for transmitting, to the first device, a first message as to whether the second mode is to be started; means for transmitting, to the first device, a second message as to whether a first monitoring of a downlink control channel in the first mode is to be started; and means for transmitting, to the first device, a third message as to whether a second monitoring of a second wake-up signal for the second mode is to be started.
  • the apparatus further comprises: means for transmitting, to the first device, information about occasions for the second monitoring; and means for transmitting, to the first device, the second wake-up signal at one of the occasions.
  • the first mode is a long cycle of the discontinuous reception operation
  • the second mode is a short cycle of the discontinuous reception operation.
  • the first device is a terminal device
  • the second device is a network device.
  • FIG. 11 is a simplified block diagram of a device 1100 that is suitable for implementing embodiments of the present disclosure.
  • the device 1100 may be provided to implement the first device or second device, for example first device 110 or the second device 120 as shown in Fig. 1.
  • the device 1100 includes one or more processors 1110, one or more memories 1120 coupled to the processor 1110, and one or more communication modules 1140 (such as, transmitters and/or receivers) coupled to the processor 1110.
  • the communication module 1140 is for bidirectional communications.
  • the communication module 1140 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 1110 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1100 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 1120 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1124, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 1122 and other volatile memories that will not last in the power-down duration.
  • a computer program 1130 includes computer executable instructions that are executed by the associated processor 1110.
  • the program 1130 may be stored in the ROM 1124.
  • the processor 1110 may perform any suitable actions and processing by loading the program 1130 into the RAM 1122.
  • the embodiments of the present disclosure may be implemented by means of the program 1130 so that the device 1100 may perform any process of the disclosure as discussed with reference to Figs. 3A to 10.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 1130 may be tangibly contained in a computer readable medium which may be included in the device 1100 (such as in the memory 1120) or other storage devices that are accessible by the device 1100.
  • the device 1100 may load the program 1130 from the computer readable medium to the RAM 1122 for execution.
  • the computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • FIG. 12 shows an example of the computer readable medium 1200 in form of CD or DVD.
  • the computer readable medium has the program 1130 stored thereon.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the methods 600-1000 as described above with reference to Figs. 6-10.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Landscapes

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

Abstract

Des modes de réalisation de la présente invention concernent des procédés, des dispositifs et des supports de stockage lisibles par ordinateur de communication. Un second dispositif transmet à un premier dispositif un premier signal de réveil pour un premier mode d'une opération de réception discontinue. Le premier dispositif surveille le premier signal de réveil, et si le premier signal de réveil est reçu avec une indication de réveil, le premier dispositif effectue l'opération de réception discontinue dans le second mode. De cette manière, un mécanisme efficace peut être fourni pour mieux prendre en charge l'utilisation du second mode avec une faible latence de paquets et une faible consommation d'énergie dans des bandes autorisées et des bandes non autorisées.
PCT/CN2020/104552 2020-07-24 2020-07-24 Procédé, dispositif et support de stockage informatique de communication Ceased WO2022016543A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080006829.6A CN114846855B (zh) 2020-07-24 2020-07-24 通信方法、设备和计算机可读介质
PCT/CN2020/104552 WO2022016543A1 (fr) 2020-07-24 2020-07-24 Procédé, dispositif et support de stockage informatique de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/104552 WO2022016543A1 (fr) 2020-07-24 2020-07-24 Procédé, dispositif et support de stockage informatique de communication

Publications (1)

Publication Number Publication Date
WO2022016543A1 true WO2022016543A1 (fr) 2022-01-27

Family

ID=79729738

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/104552 Ceased WO2022016543A1 (fr) 2020-07-24 2020-07-24 Procédé, dispositif et support de stockage informatique de communication

Country Status (2)

Country Link
CN (1) CN114846855B (fr)
WO (1) WO2022016543A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118201041A (zh) * 2024-02-06 2024-06-14 荣耀终端有限公司 一种通信方法及相关设备
CN118444763A (zh) * 2023-09-05 2024-08-06 荣耀终端有限公司 一种电子设备、电子设备唤醒方法及相关装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180007734A1 (en) * 2015-03-13 2018-01-04 Huawei Technologies Co., Ltd. Apparatus and Methods in a Wireless Communication Network
US20200037396A1 (en) * 2018-07-24 2020-01-30 Toufiqul Islam Downlink control channel signaling for improving ue power consumption
CN111373825A (zh) * 2018-07-25 2020-07-03 联发科技股份有限公司 针对ue功率节省的唤醒信号操作

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2621242A1 (fr) * 2012-01-26 2013-07-31 Panasonic Corporation Opération de réception discontinue améliorée dotée d'opportunités d'éveil supplémentaire
EP3141076B1 (fr) * 2014-05-08 2022-05-04 Telefonaktiebolaget LM Ericsson (publ) Périodes d'activité relatives pour un ue effectuant des opérations cellulaires de dispositif à dispositif (d2d)
US10588171B2 (en) * 2017-05-12 2020-03-10 Qualcomm Incorporated Techniques for multi-state DRX in new radio
CN117858278A (zh) * 2019-01-10 2024-04-09 北京三星通信技术研究有限公司 一种物理下行控制信道的监听方法、终端设备及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180007734A1 (en) * 2015-03-13 2018-01-04 Huawei Technologies Co., Ltd. Apparatus and Methods in a Wireless Communication Network
US20200037396A1 (en) * 2018-07-24 2020-01-30 Toufiqul Islam Downlink control channel signaling for improving ue power consumption
CN111373825A (zh) * 2018-07-25 2020-07-03 联发科技股份有限公司 针对ue功率节省的唤醒信号操作

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "Draft WID: Power Saving Enhancements", 3GPP DRAFT; RP-192070_REL-17 POWER SAVING ENHANCEMENTS_DRAFT WID, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Newport Beach, USA; 20190916 - 20190920, 9 September 2019 (2019-09-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051782592 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118444763A (zh) * 2023-09-05 2024-08-06 荣耀终端有限公司 一种电子设备、电子设备唤醒方法及相关装置
CN118444763B (zh) * 2023-09-05 2025-03-25 荣耀终端股份有限公司 一种电子设备、电子设备唤醒方法及相关装置
CN118201041A (zh) * 2024-02-06 2024-06-14 荣耀终端有限公司 一种通信方法及相关设备

Also Published As

Publication number Publication date
CN114846855A (zh) 2022-08-02
CN114846855B (zh) 2024-01-30

Similar Documents

Publication Publication Date Title
US12063597B2 (en) Communication method and device
US11963104B2 (en) Mechanism for interactions for entering into sleep mode
WO2022213392A1 (fr) Mécanisme d'amélioration de radiomessagerie
WO2022016543A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023216264A1 (fr) Rapport d'état de relaxation de mesure de signal
WO2023173310A1 (fr) Mécanisme de positionnement amélioré
US12336045B1 (en) Measurement relaxation
WO2022021313A1 (fr) Mécanisme de saut de détection de transmission pour économie d'énergie
WO2024098224A1 (fr) Fonctionnement de signal de réveil à puissance inférieure
US20240023190A1 (en) Method, device and computer readable medium for communications
WO2024234204A1 (fr) Améliorations apportées à la surveillance de liaison descendante
WO2024098225A1 (fr) Fonctionnement de signal de réveil à faible puissance avec configuration de réception discontinue
WO2024026790A1 (fr) Procédé et appareil d'indication de schéma de communication
US20240260000A1 (en) Method and apparatus for paging
WO2025152188A1 (fr) Relâchement de mesure
US20250261107A1 (en) Methods and devices for discontinuous transmission or discontinuous reception
WO2025030433A1 (fr) Surveillance d'informations de commande de liaison descendante sur la base d'informations de configuration et d'état d'opération discontinue de cellule
US20250267579A1 (en) Dynamic transmission of wake-up signal
WO2024098227A1 (fr) Synchronisation de liaison montante avec des signaux de réveil de puissance inférieure
WO2022077226A1 (fr) Réception discontinue dans une communication de liaison latérale
CN121153303A (zh) 对下行链路监测的增强
WO2018145767A1 (fr) Synchronisation pour drx étendue
WO2020258104A1 (fr) Notification d'état de configuration de réception discontinue
GB2638233A (en) Dynamic transmission of wake-up signal
WO2025238477A1 (fr) Délestage de mesure

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20946257

Country of ref document: EP

Kind code of ref document: A1