Enhancing user experience in low data cases with wake-up signal on

Abstract

The invention relates to enhancing user experience in low data cases with wake-up signal on. A user equipment (UE) with enhanced configured grant transmission is provided. The UE operates by determining whether a wake-up signal (WUS) indicator is received. The UE also determines whether a wake-up trigger condition is satisfied, and based on the determination that the trigger condition is satisfied, the UE determines whether the UE is configured with a power saving wake-up (ps-WakeUp) parameter. Based on a determination that the UE is configured with the ps-WakeUp parameter, the UE determines whether the ps-WakeUp parameter is set to false. Further, based on a determination that the ps-WakeUp parameter is set false, and based on a determination that the WUS indicator is not received, the UE transitions from a sleep state to an active state during a next discontinuous reception (DRX) on duration period.

Description

[0001] Cross-references

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 529,412, filed on July 28, 2023, entitled “ENHANCING USER EXPERIENCE IN LOWDATA USE CASE WITH WAKE UP SIGNAL ON,” the contents of which are incorporated herein by reference in their entirety. Background Art Technical Field

[0003]

[0013] The described aspects generally relate to techniques for reducing latency and power consumption in wireless communication systems.

[0004] Related fields

[0005] 5G New Radio (NR) supports a wide range of use cases and applications with stringent latency and power consumption requirements. Connected mode discontinuous reception (DRX) is a fundamental technique for optimizing power consumption in 5G NR devices, especially in bursty traffic scenarios where traffic bursts alternate with idle periods. Summary of the invention

[0006] Some aspects of the present disclosure relate to apparatus and methods for enhancing user experience in low data use cases with wake-up signal (WUS) turned on. For example, some aspects of the present disclosure relate to configuring a user equipment (UE) to wake up during a DRX on duration when a power save wake-up (ps-WakeUp) parameter is set to false and no WUS indicator is received.

[0007] Some aspects of the present disclosure relate to a UE having: a transceiver configured to enable wireless communication with a base station; and a processor communicatively coupled to the transceiver. The processor is configured to determine whether a wake-up trigger condition is met. Based on the determination that the trigger condition is met, the UE determines whether a wake-up signal (WUS) indicator is received. In addition, the UE determines whether the wake-up trigger condition is met. Based on the determination that the trigger condition is met, the UE determines whether it is configured with a power saving wake-up (ps-WakeUp) parameter. Next, based on the determination that the UE is configured with a ps-WakeUp parameter, the UE determines whether the ps-WakeUp parameter is set to false. Based on the determination that the ps-WakeUp parameter is set to false, and based on the determination that the WUS indicator is not received, the UE is configured to transition from a sleep state to an active state during the next discontinuous reception (DRX) on-duration period.

[0008] According to some aspects, based on a determination that a WUS indicator is received, and based on a determination that the WUS indicator is set to false, the processor is further configured to configure the UE to transition from a sleep state to an active state during a next DRX on duration period. According to some aspects, based on a determination that a WUS indicator is not received, the processor is further configured to configure the UE to remain in an active state during a next DRX off duration period. According to some aspects, based on a determination that the UE is not configured with a ps-WakeUp parameter, the processor is further configured to determine whether a WUS indicator is received. Next, based on a determination that a WUS indicator is not received, the UE is configured to transition from a sleep state to an active state during a next DRX on duration period. Alternatively, based on a determination that a WUS indicator is received, and based on a determination that the WUS indicator is set to false, the processor is further configured to configure the UE to remain in an active state during a next DRX on duration period.

[0009] According to some aspects, when a WUS indicator is received, the WUS indicator is received within a downlink control information (DCI) format 2_6 message. According to some aspects, when the UE is in the process of receiving a real-time messaging service, it is determined that the wake-up trigger condition is met. According to some aspects, when the UE is in the process of performing a cell handover, it is determined that the wake-up trigger condition is met. According to some aspects, when the UE is in the process of performing a frequency-division bandwidth part (BWP) handover, it is determined that the wake-up trigger condition is met. According to some aspects, when the UE is configured for high-speed train (HST) communication, it is determined that the wake-up trigger condition is met.

[0010] The present invention is provided for the purpose of illustrating some aspects only, so as to provide an understanding of the subject matter described herein. Therefore, the above-mentioned features are only examples and should not be understood as narrowing the scope or essence of the subject matter in the present disclosure. Other features, aspects and advantages of the present disclosure will become apparent from the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and enable those skilled in the relevant art to make and use the present disclosure.

[0012] Figure 1 An example wireless system implementing techniques for enhancing user experience in low data use cases with a wake-up signal (WUS) turned on is shown in accordance with some aspects of the present disclosure.

[0013] Figure 2A block diagram of an example system of an electronic device implementing techniques for enhancing user experience in low data use cases with WUS turned on, according to some aspects of the present disclosure, is shown.

[0014] Figure 3 An example connected mode discontinuous reception (DRX) configuration 300 is shown in accordance with some aspects of the present disclosure.

[0015] Figure 4 An exemplary method for avoiding potential user experience degradation when a WUS is not successfully received according to some aspects of the present disclosure is shown.

[0016] Figure 5 An example method performed by a UE for enhancing user experience in low data use cases with WUS turned on according to some aspects of the present disclosure is shown.

[0017] Figure 6 is an example computer system for implementing some aspects or portions thereof.

[0018] The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, like reference numerals indicate identical or functionally similar elements. Additionally, generally, the leftmost digit of a reference numeral identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

[0019] Use case scenarios for 5G NR include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC). These use cases cover a wide range of applications with highly varying requirements. For example, eMBB is designed to cater to the large capacity required to accommodate high user density scenarios. mMTC services are characterized by a large number of sensors or connected devices that typically transmit a small amount of non-delay-sensitive information, and URLLC services refer to services that are expected to have particularly low latency and extremely high reliability.

[0020] Energy efficiency is a key aspect of 5G NR deployment on both the UE side and the network side. Reducing latency together with UE power consumption can help enhance the user experience while extending UE battery life. In 5GNR, connected mode discontinuous reception (DRX) is a fundamental technique to reduce UE power consumption, especially in bursty traffic scenarios where traffic bursts alternate with idle periods. Connected mode DRX in 5G NR takes advantage of idle periods by allowing the UE to turn off its receiver circuitry and enter a sleep state during the off duration in which the UE does not need to monitor the physical downlink common control channel (PDCCH). However, the UE periodically wakes up during the configured on duration to monitor the PDCCH for possible resource allocations. Since monitoring the PDCCH is a power-intensive operation, enabling the UE to monitor the PDCCH only during the configured DRX on duration, rather than continuously, results in a significant reduction in UE power consumption.

[0021] A further reduction in UE power consumption can be achieved using wake-up signaling. The wake-up signal (WUS) feature was introduced in 3GPP Release 16 as an enhancement to connected mode DRX. When no downlink data is expected for the UE, the network sends a WUS indicator that notifies the UE to continue sleeping during the DRX On Duration, resulting in further energy savings at the UE. Similarly, when downlink data is expected for the UE, the WUS indicator notifies the UE to wake up during the DRX On Duration.

[0022] However, in some situations (e.g., during bad RF conditions), the UE may not detect the WUS, and failed WUS detection may significantly reduce the quality of service provided to the user. For example, if the network schedules downlink transmission during a DRX cycle, and the UE remains in sleep mode during the corresponding on-duration due to failed WUS detection, the UE may miss receiving the scheduled downlink data. This may result in subsequent data retransmissions, resulting in increased latency.

[0023] In order to solve the above technical problems, the embodiments of this document provide a technology for enhancing the user experience in low data use cases when WUS is turned on. Specifically, the embodiments of this document provide a technology for avoiding potential user experience degradation when WUS is not successfully received. Some aspects of the present disclosure relate to configuring the UE to transition from a sleep state to an active state during the next DRX on duration period when a WUS indicator is not received, a wake-up trigger condition is met, and a power saving wake-up (ps-WakeUp) parameter is set to false. Additionally, some aspects of the present disclosure relate to preventing the UE from entering a sleep state as long as the wake-up trigger condition is met when a WUS indicator is not received, a wake-up trigger condition is met, and a ps-WakeUp parameter is set to false.

[0024] Figure 1 An example wireless system 100 is shown that implements techniques for enhancing user experience in low data use cases with WUS turned on according to some aspects of the present disclosure. The example wireless system 100 is provided for illustration purposes only and does not limit the disclosed aspects. The wireless system 100 may include, but is not limited to, a base station 104 and a user equipment (UE) 102.

[0025] According to some aspects, base station 104 can be a fixed station or a mobile station. Base station 104 can be referred to as a cellular Internet of Things (IoT) base station, an evolved Node B (eNB), a next generation Node B (gNB), a 5G Node B (NB), or some other equivalent term. In some examples, base stations 104 can be interconnected to each other and / or to other base stations or network nodes in the network through various types of backhaul interfaces such as direct physical connections, virtual networks, etc. (not shown).

[0026] According to some aspects, UE 102 can be configured to operate based on a wide variety of wireless communication technologies. These technologies may include, but are not limited to, technologies based on the third generation partnership project (3GPP) standard. UE 102 can be stationary or mobile. UE 102 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a desktop computer, a cordless phone, a wireless local loop station, a wireless sensor, a tablet computer, a camera, a video surveillance camera, a gaming device, a netbook, an ultrabook, a medical device or equipment, a biometric sensor or device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry such as a smart ring or smart bracelet), an entertainment device (e.g., music or video equipment, or a satellite radio), a vehicle component, a smart meter, an industrial manufacturing equipment, a global positioning system device, an Internet of Things (IoT) device, a machine type communication (MTC) device, an evolution or enhancement of a machine type communication (eMTC) device, or any other suitable device configured to communicate via a wireless medium. For example, MTC and eMTC devices may include robots, drones, location tags, etc. In addition, UE 102 may be an augmented reality device, a virtual reality device, a mixed reality device, etc.

[0027] According to some aspects, UE 102 may be able to communicate with one or more base stations of wireless system 100. According to some aspects, wireless system 100 may utilize one or more radio access technologies (RATs) and may have overlapping coverage from one or more RATs. According to some aspects, the base station is a NR base station. The NR radio access network (RAN) includes an NR base station and a new radio core network (CN). The NR base station may be a next generation node B (gNB). UE 102 may access external networks via the NR base station and the NR CN.

[0028] DRX operation is controlled by parameters configured through radio resource control (RRC). BS104 configures a set of connected mode DRX parameters to UE 102. These parameters set the duration of the DRX cycle, timer, and on / off period in milliseconds. According to some aspects, in response to the network's capability information query, UE 102 sends its capability information to the network. The UE capability information may include a "drx-Adaption-r16" parameter. In response, the network may configure one or more of the following RRC parameters to UE 102: RNTI value "ps-RNTI-r16", power saving offset value "ps-Offset-r16", size of DCI format 2_6 "sizeDCI-2-6-r16", position of DCI format 2_6 "ps-PositionDCI-2-6-r16", and power saving wake-up parameter "ps-WakeUp".

[0029] In addition, the connection mode DRX parameters can be selected based on the application type so as to maximize power and resource savings. When DRX is enabled, the battery power consumption of the UE 102 is reduced. However, this reduction in power consumption comes at the expense of increased latency. This is because there may be an extended delay in receiving data because, according to the DRX cycle configured for the UE 102, the UE may only be reachable when the UE is active. In addition, the latency increases with the DRX cycle length, i.e., the longer the DRX cycle length, the higher the latency. Therefore, the DRX parameters must be carefully selected so that the packet delay is minimized and the power savings are maximized.

[0030] Figure 2 A block diagram of an example system 200 of an electronic device implementing techniques for enhancing user experience in low data use cases with WUS turned on according to some aspects of the present disclosure is shown. System 200 may represent a base station 104 and / or a UE 103 of system 100. System 200 includes a processor 210, one or more transceivers 220a to 220n, a communication infrastructure 240, a memory 250, an operating system 252, an application 254, and an antenna 260. The illustrated system is provided as an exemplary portion of system 200, and system 200 may include other circuits and subsystems. In addition, although the system of system 200 is shown as separate components, aspects of the present disclosure may include any combination of these components, fewer components, or more components.

[0031] The memory 250 may include random access memory (RAM) and / or cache, and may include control logic components (e.g., computer software) and / or data. The memory 250 may include other storage devices or memories, such as, but not limited to, a hard drive and / or a removable storage device / unit. According to some examples, an operating system 252 may be stored in the memory 250. The operating system 252 may manage data transmission from the memory 250 and / or one or more application programs 254 to the processor 210 and / or one or more transceivers 220a-220n. In some examples, the operating system 252 maintains one or more network protocol stacks (e.g., an Internet protocol stack, a cellular protocol stack, etc.) that may include multiple logical layers. At the corresponding layer of the protocol stack, the operating system 252 includes a control mechanism and a data structure to perform functions associated with the layer.

[0032] According to some examples, applications 254 may be stored in memory 250. Applications 254 may include applications (e.g., user applications) used by wireless system 200 and / or a user of wireless system 200. Applications in applications 254 may include applications such as, but not limited to, radio streaming, video streaming, remote control, and / or other user applications.

[0033] The system 200 may also include a communication infrastructure 240. The communication infrastructure 240 provides, for example, communication between the processor 210, one or more transceivers 220a to 220n, and the memory 250. In some specific implementations, the communication infrastructure 240 may be a bus. The processor 210, together with the computer instructions stored in the memory 250, executes to enable the system 200 of the system 100 to implement the operation of the technology of enhancing the user experience in low data use cases with WUS turned on according to some aspects of the present disclosure as described herein. Alternatively, the processor 210 may be "hard coded" to implement the technology of enhancing the user experience in low data use cases with WUS turned on as described herein.

[0034] One or more transceivers 220a to 220n transmit and receive communication signals implementing the technology for enhancing the user experience in low data use cases when WUS is turned on according to some aspects, and may be coupled to antenna 260. Antenna 260 may include one or more antennas that may be the same or different types. One or more transceivers 220a to 220n allow the system 200 to communicate with other devices that may be wired and / or wireless. In some examples, one or more transceivers 220a-220n may include processors, controllers, radio components, sockets, plugs, amplifiers, filters, buffers, and similar circuits / devices for connecting to a network and communicating on the network. According to some examples, one or more transceivers 220a to 220n may include one or more circuits for connecting to a wired network and / or a wireless network and communicating thereon.

[0035] According to some aspects, one or more transceivers 220a-220n may include a cellular subsystem, a WLAN subsystem, and / or a Bluetooth subsystem. TM Subsystems, each of which includes its own radio transceiver and protocol, as will be understood by those skilled in the art based on the discussion provided herein. In some implementations, one or more transceivers 220a to 220n may include more or fewer systems for communicating with other devices.

[0036] In some examples, one or more transceivers 220a-220n may include one or more circuits (including a WLAN transceiver) for enabling connection and communication via a WLAN network (such as, but not limited to, a network based on the standards described in IEEE 802.11). Additionally or alternatively, one or more transceivers 220a-220n may include one or more circuits (including a WLAN transceiver) for enabling connection and communication via a WLAN network (such as, but not limited to, a network based on the standards described in IEEE 802.11). TM Protocol, Bluetooth TM Low Energy Protocol or Bluetooth TM One or more circuits for connection and communication with low energy long range protocols (including Bluetooth TM For example, the transceiver 220n may include a Bluetooth TM Transceiver.

[0037] Additionally, one or more transceivers 220a to 220n may include one or more circuits (including cellular transceivers) for connecting to and communicating on a cellular network such as 5G NR, etc. For example, one or more transceivers 220a-220n may be configured to operate in accordance with one or more of Rel-15, Rel-16, Rel-17, or other versions of the 3GPP standard.

[0038] Figure 3 An example connected mode DRX configuration 300 is shown according to some aspects of the present disclosure. The DRX configuration specifies periodic repetitions of an on-duration and then specifies possible periods of inactivity. In the exemplary DRX configuration 300, each DRX cycle (e.g., 302a, 304a, and 306a) consists of an on-duration (e.g., 302c, 304c, and 306c) during which the UE 102 enters an active state and monitors the PDCCH for possible downlink resource allocations. If the UE 102 successfully detects a PDCCH with downlink control information (DCI) indicating a new DL transmission, the UE remains in the active state and starts a DRX inactivity timer. The UE 102 keeps monitoring the PDCCH for potential subsequent data scheduling until the DRX inactivity timer expires. However, if no data is scheduled, the UE 102 may shut down its RF circuit (in the transceiver) and enter a sleep state. The UE 102 then wakes up during the periodically configured DRX on-duration to monitor the PDCCH.

[0039] When DRX is configured, the UE 102 does not need to continuously monitor the PDCCH. Since monitoring the PDCCH is a power intensive operation, enabling the UE 102 to monitor the PDCCH only during the configured DRX On Duration results in a significant power saving at the UE 102. However, since the UE 102 cannot know exactly when it may receive a downlink resource allocation, the UE monitors the PDCCH during the DRX On Duration even when the UE has not been scheduled for transmission. This unnecessary PDCCH monitoring can consume a significant amount of power.

[0040] If the network tells the UE 102 whether it should wake up and monitor the PDCCH during the upcoming DRX on-duration, further improvements in power consumption can be achieved. In 3GPP Release 16, a wake-up signal (WUS) feature was introduced as an enhancement to DRX operation. When the WUS feature is configured, the UE 102 wakes up at a configurable time (e.g., ps-offset time units) before the start of the long DRX cycle and checks the WUS indicator. When the UE 102 expects to receive data, the WUS indicator is set to notify the UE 102 to wake up and monitor the PDCCH during the on-duration of the next DRX cycle. However, when the UE 102 does not expect to receive data during the DRX cycle, the WUS indicator is set to notify the UE 102 to remain in a sleep state throughout the DRX cycle, thereby minimizing unnecessary PDCCH monitoring.

[0041] According to some aspects, BS 104 transmits a WUS indicator to UE 102 using DCI format 2_6. However, other DCI formats or non-DCI communications may be used. The WUS indicator informs UE 102 whether to start a DRX on duration timer for the next DRX cycle for potential data scheduling. According to some aspects, a WUS indicator set to true (e.g., the WUS indicator is set to bit "1") informs UE 102 to start a DRX on duration timer for the next long DRX cycle. Similarly, a WUS indicator set to false (e.g., the WUS indicator is set to bit "0") informs UE 102 not to start a DRX on duration timer for the next long DRX cycle. According to some aspects, a cyclic redundancy check (CRC) of DCI 2_6 is scrambled by a power saving radio network temporary identifier (PS-RNTI) corresponding to UE 102.

[0042] exist Figure 3In the example of , UE 102 wakes up and checks WUS indicators (e.g., 302b, 304b, and 306b) before each DRX cycle (e.g., 302a, 304a, and 306a) starts. In the example, WUS indicator 302b is set to false, indicating that UE 102 does not expect to receive data during DRX cycle 302a. Therefore, UE 102 does not start the DRX on-duration timer for DRX cycle 302a. Therefore, UE 102 remains in sleep mode during the on-duration 302c of DRX cycle 302a. Figure 3 In the example of , the next WUS indicator 304b is set to true, indicating that the UE 102 expects to receive data during the DRX cycle 304a. Therefore, the UE 102 starts the DRX on-duration timer for the DRX cycle 304a. Therefore, the UE 102 wakes up and remains in active mode during the on-duration 304c of the DRX cycle 304a and monitors the PDCCH.

[0043] In addition, Figure 3 In the example of , the WUS indicator 306b sent by the BS 104 is not successfully detected by the UE 102. According to some aspects, the WUS indicator (e.g., in DCI format 2_6) may not be detected by the UE 102 due to poor propagation conditions (e.g., reference signal received power (RSRP) and / or signal to interference plus noise ratio (SINR) less than a threshold). According to some aspects, when the UE 102 and the BS 104 are out of synchronization, the UE 102 may not detect the WUS indicator 306b. According to some aspects, when the UE 102 is in a heavily loaded cell, the UE 102 may not detect the WUS 306b. According to some aspects, when the UE 102 is in a mobility condition and misses a tracking area update, the UE 102 may not detect the WUS indicator 306b. According to some aspects, when the UE 102 is performing a BWP switch resulting in a reconfiguration of a connected mode DRX mode, the UE 102 may not detect the WUS indicator 306b. According to some aspects, when a change in traffic pattern results in a reconfiguration of the DRX pattern, the UE 102 may not detect the WUS indicator 306b. According to some aspects, when the UE is in a high-speed mobility condition (eg, HST scenario), the UE 102 may not detect the WUS 306b.

[0044] According to some aspects, when the WUS indicator 306b is not detected, the UE 102 may remain in sleep mode during the on-duration 306c of the DRX cycle 306a. The failed detection of DCI format 2_6 may result in poor quality of service. For example, if the network schedules downlink transmission during DRX 306a, and the UE 102 remains in sleep mode during the on-duration 306c due to a failed decoding of DCI format 2_6, the UE 102 may miss receiving the scheduled downlink data.

[0045] An optional power saving wake-up parameter ps-WakeUp (also referred to as ps-WakeUp-r16) was introduced in Release 16. The ps-WakeUp parameter can be used to minimize the degradation of the user experience when the UE 102 fails to detect the WUS indicator 306b. According to some aspects, the ps-WakeUp parameter is sent by the BS as part of the initial configuration. According to some aspects, when the ps wake-up parameter is enabled (e.g., when the ps-WakeUp parameter is set to "true") and the WUS indicator 306b is not detected, the UE 102 wakes up during the on-duration of the DRX cycle. However, when the ps-WakeUp parameter is not configured or when the ps-WakeUp parameter is not enabled (e.g., when the ps-WakeUp parameter is set to "false"), when the WUS indicator 306b is not detected, the UE 102 does not wake up during the on-duration of the DRX cycle.

[0046] exist Figure 3 In the example of , when the ps-wakeup parameter is enabled (e.g., the ps-wakeup parameter is set to "true") and no WUS indicator is received (e.g., no DCI 2_6 is detected), the UE 102 wakes up during the on-duration 306c of the DRX cycle 306a. However, when the optional ps-WakeUp parameter is not configured or when the ps-WakeUp parameter is not enabled (e.g., the ps-WakeUp parameter is set to "false") and no WUS 306b is received (e.g., no DCI 2_6 is detected), the UE 102 does not wake up during the on-duration 306c of the DRX cycle 306a. As mentioned previously, as a result of not waking up during the DRX cycle 306a, the UE 102 may miss receiving the scheduled downlink data. When the UE 102 has been scheduled for a transmission in the downlink that it cannot detect, the BS 104 retransmits the data at a later time, and the retransmission may result in increased delay. When the user is receiving delay-sensitive services, the degradation of the user experience may be severe.

[0047] For example, when the user is receiving latency-sensitive services (e.g., streaming video, etc.), missed detection of the WUS may result in severe degradation of the user experience (e.g., video freeze or video quality degradation). Other example scenarios where missed detection of the WUS may result in severe degradation of the user experience include mobility scenarios where the UE moves from one cell to another, the UE switches its active bandwidth part (BWP), the UE in a high-speed train scenario, the UE configured with carrier aggregation, etc.

[0048] Figure 4 An exemplary method 400 for avoiding potential user experience degradation when a WUS is not successfully received according to some aspects of the present disclosure is shown. Figures 1 to 3 and Figure 6 The elements are used to describe Figure 4 ,For example, Figure 4 The functions of may be performed by UE 102. For example, processor 210 may be combined with Figure 2 other components to execute or cause to be executed Figure 5 Method 400 can also be performed by Figure 2 System 200 and / or Figure 6 The method 400 is performed by a computer system 600. However, the method 400 is not limited to the specific aspects depicted in those figures, and other systems may be used to perform the method, as will be understood by those skilled in the art. It should be understood that not all operations may be required, and these operations may not be performed in the same manner as described above. Figure 4 The same sequence as shown is performed.

[0049] At 402, a determination is made as to whether the UE 102 supports WUS. According to some aspects, the UE 102 sends its capability information to the network. If the UE 102 supports WUS, the UE may include a "drx-Adaption-r16" parameter in the capability information it sends. According to some aspects, the UE 102 may send its capability information in response to a capability query from the network. If the UE 102 does not support WUS, the example method 400 ends at 412. However, if the UE 102 supports WUS, the method 400 proceeds to 404.

[0050] At 404, a determination is made as to whether the network supports WUS. The WUS feature for connected mode DRX was introduced in 3GPP Release 16. As mentioned above, UE 102 sends its capability information to the network, and the UE capability information may include a "drx-Adaption-r16" parameter. If the network supports WUS, the network configures one or more of the following parameters to UE 102: an RNTI value "ps-RNTI-r16", a power saving offset value "ps-Offset-r16", a size of DCI format 2_6 "sizeDCI-2-6-r16", a position of DCI format 2_6 "ps-PositionDCI-2-6-r16", and a power saving wake-up parameter "ps-WakeUp". If the network does not support WUS, the example method 400 ends at 412. However, if the network supports WUS, the method 400 proceeds to 406.

[0051] At 406, a determination is made as to whether a wake-up trigger condition is met. According to some aspects, the wake-up trigger condition is met if the UE 102 finds itself in a situation where missed detection of a WUS may result in a severe degradation of the user experience. According to some aspects, the wake-up trigger condition is met when the UE 102 receives a predetermined type of service. According to some aspects, the wake-up trigger condition is met if the UE 102 receives a latency-sensitive service (e.g., real-time video communication, streaming service, etc.). According to some aspects, the wake-up trigger condition is met if the UE 102 is in a mobility situation (such as a handover or redirection from one cell to another). According to some aspects, the wake-up trigger condition is met if the UE 102 is in the process of switching its active bandwidth part (BWP). According to some aspects, the wake-up trigger condition is met if the network configures HST to the UE 102 on SIB2. If the wake-up trigger condition is not met, the example method 400 ends. However, if the wake-up trigger condition is met, the method 400 proceeds to 408.

[0052] At 408, a determination is made whether the ps-WakeUp parameter is set to false. According to some aspects, the network configures RRC parameters related to WUS to the UE 102. The RRC parameters include an indication of whether the ps-WakeUp parameter is enabled (i.e., indicating whether the ps-WakeUp parameter is set to "true" or "false"). If the ps-wakeUp-r16 parameter is set to true, the example method 400 ends at 412. However, if the ps-WakeUp parameter is not enabled (i.e., the ps-WakeUp parameter is set to "false"), the method 400 proceeds to 410.

[0053] At 410, according to some aspects, based on a determination that the wake-up trigger condition is met and the ps-WakeUp parameter is set to false, the UE 102 is configured to wake up during the DRX-on duration as long as the wake-up trigger condition is met. Alternatively, based on a determination that the wake-up trigger condition is met and the ps-WakeUp parameter is set to false, the UE 102 is prevented from entering a sleep state as long as the wake-up trigger condition is met.

[0054] Figure 5 An exemplary method 500 is shown for enhancing the user experience in a low data use case when the wake-up signal is turned on, performed by a UE according to some aspects of the present disclosure. Figures 1 to 4 and Figure 6 The elements are used to describe Figure 5 ,For example, Figure 5 The functions of may be performed by UE 102. For example, processor 210 may be combined with Figure 2 other components to execute or cause to be executed Figure 5 Method 500 can also be performed by Figure 2 System 200 and / or Figure 6 The method 500 is performed by a computer system 600. However, the method 500 is not limited to the specific aspects depicted in those figures, and other systems may be used to perform the method, as will be understood by those skilled in the art. It should be understood that not all operations may be required, and these operations may not be performed in the same manner as described above. Figure 5 The same sequence as shown is performed.

[0055] At 502, UE 102 determines whether a wake-up signal (WUS) indicator is received. According to some aspects, UE 102 receives the WUS indicator within a DCI format 2-6 message. The WUS indicator informs UE 102 whether to start a DRX on duration timer for the next DRX cycle for potential data scheduling. According to some aspects, a WUS indicator set to true (e.g., the WUS indicator is set to bit "1") informs UE 102 to start the DRX on duration timer for the next long DRX cycle. Similarly, a WUS indicator set to false (e.g., the WUS indicator is set to bit "0") informs UE 102 not to start the DRX on duration timer for the next long DRX cycle.

[0056] However, the WUS indicator (e.g., 306b) sent by BS 104 may not be successfully detected by UE 102. According to some aspects, UE 102 may not detect the WUS indicator (e.g., DCI format 2_6) due to poor RF channel conditions (e.g., reference signal received power (RSRP) and / or signal to interference plus noise ratio (SINR) less than a threshold). According to some aspects, when UE 102 and BS 104 are out of sync, UE 102 may not detect the WUS indicator. According to some aspects, when UE 102 is in a heavily loaded cell, UE 102 may not detect the WUS. According to some aspects, when UE 102 is in a mobility condition and misses a tracking area update, UE 102 may not detect the WUS. According to some aspects, when UE 102 is performing a BWP switch resulting in a reconfiguration of a connected mode DRX mode, UE 102 may not detect the WUS. According to some aspects, when a change in traffic pattern results in a reconfiguration of the DRX pattern, the UE 102 may not detect the WUS. According to some aspects, when the UE is in a high-speed mobility condition (eg, HST scenario), the UE 102 may not detect the WUS.

[0057] At 504, the UE 102 determines whether a wake-up condition is satisfied. According to some aspects, if the UE receives a predetermined type of delay-sensitive traffic (e.g., real-time video communication, streaming traffic, etc.), the UE determines that the wake-up trigger condition is satisfied. According to some aspects, if the UE 102 receives a predetermined type of delay-sensitive traffic for at least a threshold amount of time, the UE 102 determines that the wake-up trigger condition is satisfied. According to some aspects, if the UE 102 is in a mobility situation (such as a handover or redirection from one cell to another), the UE 102 determines that the wake-up trigger condition is satisfied. According to some aspects, if the UE 102 is in the process of performing a frequency-division BWP handover, the UE determines that the wake-up trigger condition is satisfied. According to some aspects, if the network configures HST to the UE 102 on SIB2, the UE 102 determines that the wake-up trigger condition is satisfied. According to some aspects, if the UE 102 is in an HST scenario for at least a threshold amount of time, the UE determines that the wake-up trigger condition is satisfied. According to some aspects, the threshold amount of time is a parameter configured by the network.

[0058] At 506, based on the determination that the trigger condition is met, the UE 102 determines whether it is configured with a power saving wake-up (ps-WakeUp) parameter. According to some aspects, the network may configure a set of DRX-related RRC parameters including the ps-WakeUp parameter to the UE 102. According to some aspects, the configured ps-WakeUp parameter may be set to true or false. When the ps-WakeUp parameter is set to true, the UE 102 may start an associated drx-on duration timer when a WUS indicator (e.g., DCI format 2_6) is monitored but not detected. Alternatively, according to some aspects, since the ps-WakeUp parameter is an optional parameter, the network may not configure the ps-WakeUp parameter to the UE 102.

[0059] At 508, based on the determination that the UE 102 is configured with a ps-WakeUp parameter, the UE 102 determines whether the ps-WakeUp parameter is set to false. If the ps-WakeUp parameter is not set to false, the example method 500 ends. However, if the ps-WakeUp parameter is set to false, the method 500 proceeds to 510.

[0060] At 510, based on a determination that the ps-WakeUp parameter is set to false and based on a determination that a WUS indicator is not received, the UE 102 transitions from the sleep state to the active state during a next discontinuous reception (DRX) on-duration period. According to some aspects, based on a determination that a WUS indicator is received and based on a determination that the WUS indicator is set to false, the UE 102 may be configured to transition from the sleep state to the active state during a next DRX on-duration period.

[0061] In addition, based on the determination that the WUS indicator is not received, the UE 102 remains in the active state during the next DRX off duration period. According to some aspects, based on the determination that the ps-WakeUp parameter is set to false and the WUS indicator is not received, the UE 102 may be configured to not enter the sleep state as long as the wake-up trigger condition is met. According to some aspects, based on the determination that the UE 102 is not configured with the ps-WakeUp parameter, the UE 102 determines whether the WUS indicator is received. Based on the determination that the WUS indicator is not received, the UE is configured to transition from the sleep state to the active state during the next DRX on duration period. According to some aspects, based on the determination that the WUS indicator is received, and based on the determination that the WUS indicator is set to false, the UE 102 may be configured to remain in the active state during the next DRX on duration period.

[0062] For example, one or more computer systems such as Figure 6The computer system 600 shown is used to implement various aspects. The computer system 600 may be any well-known computer capable of performing the functions described herein, such as Figure 1 UE 102. The computer system 600 includes one or more processors (also referred to as central processing units or CPUs), such as a processor 604. The processor 604 is connected to a communication infrastructure 606 (e.g., a bus). The computer system 600 also includes a user input / output device 603, such as a monitor, a keyboard, a pointing device, etc., which communicates with the communication infrastructure 606 through a user input / output interface 602. The computer system 600 also includes a main memory or primary storage 606, such as a random access memory (RAM). The main memory 608 may include one or more levels of cache. Control logic components (e.g., computer software) and / or data are stored in the main memory 608.

[0063] The computer system 600 may also include one or more secondary storage devices or memories 610. The secondary storage 610 may include, for example, a hard disk drive 612 and / or a removable storage device or drive 614. The removable storage drive 614 may be a floppy disk drive, a tape drive, an optical drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0064] The removable storage drive 614 may interact with a removable storage unit 618. The removable storage unit 618 includes a computer usable or readable storage device having computer software (control logic) and / or data stored thereon. The removable storage unit 618 may be a floppy disk, a magnetic tape, a compact disk, a DVD, an optical storage disk, and / or any other computer data storage device. The removable storage drive 614 reads from and / or writes to the removable storage unit 618 in a well-known manner.

[0065] According to some aspects, secondary memory 610 may include other devices, tools, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 600. Such devices, tools, or other methods may include, for example, a removable storage unit 622 and an interface 620. Examples of removable storage unit 622 and interface 620 may include a program cartridge and cartridge interface (such as found in video game devices), a removable memory chip (such as an EPROM or PROM) and an associated socket, a memory stick and USB port, a memory card and an associated memory card slot, and / or any other removable storage unit and associated interface.

[0066] The computer system 600 may also include a communication or network interface 624. The communication interface 624 enables the computer system 600 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference numeral 628). For example, the communication interface 624 may allow the computer system 600 to communicate with the remote device 628 via a communication path 626, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic components and / or data may be transmitted to and from the computer system 600 via the communication path 626.

[0067] The operations in the foregoing aspects can be implemented in various configurations and architectures. Thus, some or all of the operations in the foregoing aspects may be performed in hardware, software, or in both hardware and software. In some aspects, a tangible, non-transient device or article includes a tangible, non-transient computer-usable or readable medium on which a control logic component (software) is stored, also referred to herein as a computer program product or program storage device. This includes, but is not limited to, a computer system 600, a main memory 608, an auxiliary memory 610, and removable storage units 618 and 622, as well as tangible articles embodying any combination of the foregoing. Such control logic components, when executed by one or more data processing devices (such as computer system 600), cause such data processing devices to operate as described herein.

[0068] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use Figure 6 The various aspects of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the various aspects may operate with software, hardware, and / or operating system implementations other than those described herein.

[0069] It should be understood that the Detailed Description section, rather than the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary aspects of the present disclosure as contemplated by the inventors, and thus are not intended to limit the present disclosure or the appended claims in any way.

[0070] Although the present disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and essence of the present disclosure. For example, and without limiting the generality of this paragraph, the various aspects are not limited to the software, hardware, firmware and / or entities shown in the figures and / or described herein. In addition, the various aspects (whether or not explicitly described herein) have significant practicality for fields and applications outside the examples described herein.

[0071] Various aspects have been described herein by means of functional building blocks that illustrate specific implementations of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. As long as the specified functions and relationships (or their equivalents) are properly performed, alternative boundaries may be defined. In addition, alternative aspects may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0072] References herein to "one aspect," "aspect," "one example," "example," or similar phrases indicate that the described aspects may include a particular feature, structure, or characteristic, but each aspect may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same aspect. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with one aspect, it is within the knowledge of a person skilled in the relevant art to incorporate such feature, structure, or characteristic into other aspects, whether or not explicitly mentioned or described herein.

[0073] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary aspects, but should be defined only in accordance with the following claims and their equivalents.

[0074] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be convenient for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should only be after receiving the user's informed consent. Additionally, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.

Claims

1. A user equipment (UE), comprising: a transceiver configured to implement wireless communication; and a processor communicatively coupled to the transceiver and configured to: determining whether a wake-up signal (WUS) indicator is received; Determine whether the wake-up trigger condition is met; Based on the determination that the wake-up trigger condition is satisfied, determining whether the UE is configured with a power saving wake-up (ps-WakeUp) parameter; Based on a determination that the UE is configured with the ps-WakeUp parameter, determining whether the ps-WakeUp parameter is set to false; as well as Based on a determination that the ps-WakeUp parameter is set to false and based on a determination that the WUS indicator is not received, configuring the UE to transition from a sleep state to an active state during a next discontinuous reception (DRX) on-duration period.

2. The UE according to claim 1, wherein: Based on a determination that the WUS indicator is received, and based on a determination that the WUS indicator is set to false, the processor is further configured to: The UE is configured to transition from the sleep state to the active state during the next DRX On-Duration period.

3. The UE according to claim 1, wherein: Based on a determination that the WUS indicator is not received, the processor is further configured to: The UE is configured to remain in the active state during a next DRX off-duration period.

4. The UE according to claim 1, wherein: Based on a determination that the UE is not configured with the ps-WakeUp parameter, the processor is further configured to: Based on a determination that the WUS indicator is not received, the UE is configured to transition from the sleep state to the active state during the next DRX On-Duration period.

5. The UE according to claim 4, wherein: Based on a determination that the WUS indicator is received, and based on a determination that the WUS indicator is set to false, the processor is further configured to: The UE is configured to remain in the active state during the next DRX On-Duration period.

6. The UE of claim 1, wherein when the WUS indicator is received, the WUS indicator is received within a downlink control information (DCI) format 2_6. 7 . The UE according to claim 1 , wherein when the UE is in the process of receiving a real-time messaging service, it is determined that the wake-up trigger condition is satisfied. 8 . The UE according to claim 1 , wherein when the UE is in the process of performing a cell handover, it is determined that the wake-up trigger condition is satisfied. 9 . The UE according to claim 1 , wherein when the UE is in the process of performing frequency-division bandwidth part (BWP) switching, it is determined that the wake-up trigger condition is satisfied.

10. The UE of claim 1, wherein when the UE is configured for high speed train (HST) communication, it is determined that the wake-up trigger condition is satisfied.

11. A method of operating a user equipment (UE), comprising: determining whether a wake-up signal (WUS) indicator is received; Determine whether the trigger condition is met; Based on the determination that the trigger condition is met, determining whether the UE is configured with a power saving wake-up (ps-WakeUp) parameter; Based on a determination that the UE is configured with the ps-WakeUp parameter, determining whether the ps-WakeUp parameter is set to false; as well as Based on a determination that the ps-WakeUP parameter is set to false and based on a determination that the WUS indicator is not received, configuring the UE to transition from a sleep state to an active state during a next discontinuous reception (DRX) on-duration period.

12. The method according to claim 11, further comprising: Based on a determination that the WUS indicator is received, and based on a determination that the WUS indicator is set to false, configuring the UE to transition from the sleep state to the active state during the next DRX On-Duration period.

13. The method according to claim 11, further comprising: Based on a determination that the WUS indicator is not received, the UE is configured to remain in the active state during a next DRX Off Duration period.

14. The method of claim 11, based on the determination that the UE is not configured with the ps-WakeUp parameter, the method further comprising: Based on a determination that the WUS indicator is not received, the UE is configured to transition from the sleep state to the active state during the next DRX On-Duration period.

15. The method according to claim 14, further comprising: Based on a determination that the WUS indicator is received, and based on a determination that the WUS indicator is set to false, configuring the UE to remain in the active state during the next DRX Off Duration period.

16. A non-transitory computer readable medium (CRM) having instructions stored thereon, the instructions, when executed by a processor of a user equipment (UE), causing the UE to perform operations comprising: determining whether a wake-up signal (WUS) indicator is received; Determine whether the trigger condition is met; Based on the determination that the trigger condition is met, determining whether the UE is configured with a power saving wake-up (ps-WakeUp) parameter; Based on a determination that the UE is configured with the ps-WakeUp parameter, determining whether the ps-WakeUp parameter is set to false; as well as Based on a determination that the ps-WakeUP parameter is set to false and based on a determination that the WUS indicator is not received, configuring the UE to transition from a sleep state to an active state during a next discontinuous reception (DRX) on-duration period.

17. The non-transitory CRM of claim 16, the operations further comprising: Based on a determination that the WUS indicator is received, and based on a determination that the WUS indicator is set to false, configuring the UE to transition from the sleep state to the active state during the next DRX On-Duration period.

18. The non-transitory CRM of claim 16, the operations further comprising: Based on a determination that the WUS indicator is not received, the UE is configured to remain in the active state during a next DRX Off Duration period.

19. The non-transient CRM of claim 16, based on the determination that the UE is not configured with the ps-WakeUp parameter, the operations further comprising: Based on a determination that the WUS indicator is not received, the UE is configured to transition from the sleep state to the active state during the next DRX On-Duration period.

20. The non-transitory CRM of claim 19, the operations further comprising: Based on a determination that the WUS indicator is received, and based on a determination that the WUS indicator is set to false, configuring the UE to remain in the active state during the next DRX Off Duration period.

Images