Enhancing user experience in burst data environments by enabling wake-up signals for carrier aggregation or dual connectivity

Abstract

The present disclosure relates to enhancing user experience by enabling wake-up signals for carrier aggregation or dual connectivity in a burst data environment. A user equipment (UE) operating using a wake-up signal (WUS) in conjunction with carrier aggregation, dual connectivity, and / or multi-SIM is provided. The UE operates by determining whether the UE is configured to operate simultaneously using the first connection and the second connection. Based on a determination that the UE is configured to operate simultaneously using the first connection and the second connection, the UE determines whether a wake-up signal (WUS) indicator corresponding to a first discontinuous reception (DRX) cycle is received. The UE then determines whether a wake-up trigger condition is satisfied, and based on determining that the wake-up trigger condition is satisfied, the UE determines whether it is configured with a power saving wake-up (ps-WakeUp) parameter. Based on a determination that the UE is configured with a ps-WakeUp parameter, based on a determination that the ps-WakeUp parameter is set to false, and based on a determination that a WUS indicator corresponding to the first DRX cycle is not received, the UE is configured to remain in an active state during a DRX OFF duration period of the first DRX cycle.

Description

TECHNICAL FIELD

[0001] Aspects described relate generally to techniques for reducing latency and power consumption in wireless communication systems. BACKGROUND

[0002] 5G New Radio (NR) supports a wide range of use cases and applications with strict latency and power consumption requirements. Connected mode discontinuous reception (DRX) is a fundamental technique used to optimize power consumption in 5G NR devices, especially in bursty traffic scenarios where traffic bursts alternate with idle periods. Carrier aggregation, dual connectivity, and multi-subscriber identity module (multi-SIM) techniques provide greater flexibility, enhanced data rates, and improved connectivity for mobile network users. SUMMARY

[0003] Some aspects of the disclosure relate to apparatuses and methods for enhancing user experience in low data use cases with wake-up signal (WUS) on. For example, some aspects of the disclosure relate to configuring a user equipment (UE) using carrier aggregation, dual connectivity, and / or multi-SIM operation to wake up during a DRX on duration when a power saving wake-up (ps-WakeUp) parameter is set to false and no WUS indicator is received.

[0004] Some aspects of the 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 the UE is configured to operate using a first connection and a second connection simultaneously. Based on determining that the UE is configured to operate using the first connection and the second connection simultaneously, the UE determines whether a wake-up signal (WUS) indicator corresponding to a first discontinuous reception (DRX) cycle is received. The UE then determines whether a wake-up trigger condition is satisfied, and based on determining that the wake-up trigger condition is satisfied, the UE determines whether it is configured with a power saving wake-up (ps-WakeUp) parameter. Based on determining that the UE is configured with the ps-WakeUp parameter, determining that the ps-WakeUp parameter is set to false, and determining that no WUS indicator corresponding to the first DRX cycle is received, the UE is subsequently configured to remain in an active state during a DRX off duration period of the first DRX cycle.

[0005] According to some aspects, based on determining that the WUS indicator corresponding to the second DRX cycle is received and determining that the WUS indicator corresponding to the second DRX cycle is set to false, the processor is further configured to configure the UE to transition from the sleep state to the active state during a DRX on-duration period of the second DRX cycle. According to some aspects, the WUS indicator corresponding to the second DRX cycle is received within a downlink control information (DCI) format 2_6. According to some aspects, based on determining that the WUS indicator corresponding to the first DRX cycle is not received, the processor is further configured to configure the UE to transition from the sleep state to the active state during a DRX on-duration period of the first DRX cycle.

[0006] According to some aspects, the UE is configured to operate using carrier aggregation, and the first connection and the second connection correspond to a first bandwidth part (BWP) and a second BWP, respectively. According to some aspects, the UE is configured to operate using dual connectivity, and the first connection is established with a first base station and the second connection is established with a second base station. According to some aspects, the UE is configured to operate using dual subscriber identity modules (SIMs), and the first connection is established using a first SIM and the second connection is established using a second SIM.

[0007] According to some aspects, the second connection of the UE is designated for receiving low-rate data, and the processor is further configured to: determine whether a data rate of the application is less than a threshold; and based on determining that the data rate of the application is less than the threshold, the UE uses the second connection for the application. According to some aspects, the wake-up trigger condition is determined to be satisfied when the UE receives real-time messaging traffic. According to some aspects, the wake-up trigger condition is determined to be satisfied when the UE is in a process of performing a BWP switch.

[0008] This Summary is provided to illustrate some aspects and to provide a basic understanding of the subject matter described herein. Accordingly, the above-described features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter in the disclosure. Other features, aspects, and advantages of the disclosure will become apparent from the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF DRAWINGS

[0009] 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 disclosure and to enable a person skilled in the relevant art to make and use the disclosure.

[0010] Figure 1 An example wireless system illustrating techniques for implementing enhanced user experience in low data use cases using wake-up signals (WUS) in conjunction with carrier aggregation, dual connectivity, and / or multi-SIM operation in accordance with some aspects of the present disclosure is illustrated.

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

[0012] Figure 3 An example connected mode discontinuous reception (DRX) configuration 300 according to some aspects of the disclosure is illustrated.

[0013] Figure 4 An example method for avoiding user experience degradation when a WUS is not successfully received according to some aspects of the disclosure is illustrated.

[0014] Figure 5 An example method for avoiding user experience degradation when a WUS is not successfully received at a UE due to BWP switching according to some aspects of the disclosure is illustrated.

[0015] Figure 6 An example method for avoiding user experience degradation when a WUS is not successfully received at a multi-SIM UE according to some aspects of the disclosure is illustrated.

[0016] Figure 7 An example method for avoiding user experience degradation when a WUS is not successfully received at a multi-SIM UE using carrier aggregation or dual connectivity according to some aspects of the disclosure is illustrated.

[0017] Figure 8 An example method performed by a UE for enhancing user experience in low data use cases using WUS in conjunction with carrier aggregation, dual connectivity, and / or multi-SIM operation according to some aspects of the disclosure is illustrated.

[0018] Figure 9 is an example computer system for implementing some aspects, or portions thereof.

[0019] The present disclosure is described with reference to the attached drawings. In the drawings, like reference numerals indicate like structure, and a consistent number across drawings indicates a consistent element. Additionally, the left-most digit of the reference numeral typically identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

[0020] 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 large capacity needed to accommodate high user density scenarios. mMTC services are characterized by a large number of sensors or connected devices that typically send small amounts of non-delay-sensitive information, and URLLC services refer to services that are expected to have particularly low latency and extremely high reliability.

[0021] Carrier aggregation, dual connectivity, and multi-SIM technologies enable enhanced network performance and user experience. Carrier aggregation combines multiple frequency bands to support a single data stream, significantly boosting data rates and improving network efficiency. Dual connectivity allows a mobile device to connect to two different base stations simultaneously, often across different network technologies, which provides increased data throughput and more reliable connectivity. Multi-SIM functionality enables a device to support multiple SIM cards, allowing a user to connect to different mobile networks or manage multiple phone numbers. Together, these technologies provide users with greater flexibility, enhanced data rates, and improved connectivity, particularly in areas with varying network coverage and traffic demands.

[0022] Energy efficiency is a key aspect of 5G NR deployments on both the UE side and the network side. Reducing latency along with UE power consumption can help enhance user experience while prolonging UE battery life. In 5G NR, connected mode discontinuous reception (DRX) is a fundamental technique to reduce UE power consumption, particularly in bursty traffic scenarios where traffic bursts alternate with idle periods. Connected mode DRX in 5G NR takes advantage of idle periods by allowing a UE to turn off its receiver circuitry and enter a sleep state during an off duration in which the UE does not need to monitor a physical downlink control channel (PDCCH). However, the UE periodically wakes up during configured on durations 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 durations, rather than continuously, results in a significant reduction in UE power consumption.

[0023] 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 a UE, the network transmits a WUS indicator that informs the UE to continue sleeping during a DRX on duration, resulting in further energy saving at the UE. Similarly, when downlink data is expected for the UE, the WUS indicator informs the UE to wake up during the DRX on duration.

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

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

[0026] Figure 1 An example wireless system 100 implementing techniques for enhancing user experience in low data use cases with WUS on is illustrated in accordance with some aspects of the disclosure. The example wireless system 100 is provided for illustrative purposes only and does not limit the disclosed aspects. The wireless system 100 can include, but is not limited to, base stations 104 and 106 and a user equipment (UE) 102.

[0027] According to some aspects, the base stations 104 and 106 can be fixed stations or mobile stations. Each of the base stations 104 and 106 can be referred to as a cellular Internet of Things (IoT) base station, an evolved NodeB (eNB), a next Generation NodeB (gNB), a 5G NodeB (NB), or some other equivalent terminology. In some examples, the base stations 104 and 106 can be interconnected to one another and / or to the network by various types of backhaul interfaces, such as a direct physical connection or a wireless connection, a virtual network, or the like (not shown), using various types of transporting networks, such as an optical fiber, a wireless connection, a router, a hub, or the like.

[0028] According to some aspects, the UE 102 can be configured to operate based on a wide variety of wireless communication technologies. These technologies can include, but are not limited to, those based on Third Generation Partnership Project (3GPP) standards. The UE 102 can be stationary or mobile. The 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 computer, 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, medical equipment or gear, a biometric sensor or device, a wearable device (a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (such as a smart ring or a smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component, a smart meter, industrial manufacturing equipment, a global positioning system device, an Internet of Things (IoT) device, a machine type communication (MTC) device, an evolved or enhanced machine type communication (eMTC) device, or any other suitable device configured to communicate via a wireless medium. For example, MTC and eMTC devices can include robots, drones, location tags, etc. Further, the UE 102 can be an augmented reality device, a virtual reality device, a mixed reality device, etc.

[0029] According to some aspects, the UE 102 can be capable of communicating with one or more base stations of the wireless system 100. According to some aspects, the wireless system 100 can utilize one or more radio access technologies (RATs) and can have overlapping coverage from one or more RATs. According to some aspects, one or more of the base stations 104, 106 are NR base stations. An NR radio access network (RAN) includes NR base stations and a New Radio core network (CN). An NR base station can be a next generation NodeB (gNB). The UE 102 can access external networks via the NR base stations and the NR CN.

[0030] DRX operation is controlled by parameters configured through radio resource control (RRC). The BS 104 configures a set of connected mode DRX parameters to the UE 102. These parameters set the duration of the DRX cycle, timers, and on / off periods in milliseconds. According to some aspects, the UE 102 transmits its capability information to the network in response to a network's capability information query. The UE capability information can include a "drx-Adaption-r16" parameter. In response, the network can configure one or more of the following RRC parameters to the UE 102: a radio network temporary identifier (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 location of DCI format 2_6 "ps-PositionDCI-2-6-r16," and a power saving wake-up parameter "ps-WakeUp."

[0031] In addition, the connected mode DRX parameters can be selected based on the application type so that power and resource savings are maximized. When DRX is enabled, the battery power consumption of the UE 102 is reduced. However, this reduction in power consumption comes at the cost of increased latency. This is because there can be an extended delay in receiving data because, according to the DRX cycle configured for the UE 102, the UE can 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.

[0032] Figure 2 A block diagram of an example system 200 of an electronic device that implements techniques for enhancing user experience in low data use cases with WUS on according to some aspects of the disclosure is illustrated. The system 200 can represent the base station 104 and / or the UE 103 of the system 100. The system 200 includes a processor 210, one or more transceivers 220a-220n, a communication infrastructure 240, a memory 250, an operating system 252, applications 254, and antennas 260. The illustrated system is provided as an example portion of the system 200, and the system 200 can include other circuitry and subsystems. In addition, although the components of the system 200 are illustrated as separate components, aspects of the disclosure can include any combination of these components, fewer components, or additional components.

[0033] Memory 250 can include random access memory (RAM) and / or cache and can include control logic (e.g., computer software) and / or data. Memory 250 can include other storage devices or memory, such as, but not limited to, hard disk drives and / or removable storage devices / units. According to some examples, an operating system 252 can be stored in memory 250. Operating system 252 can manage data transfer between memory 250 and / or one or more applications 254 to processor 210 and / or one or more transceivers 220a-n. In some examples, operating system 252 maintains one or more network protocol stacks (e.g., Internet protocol stacks, cellular protocol stacks, etc.) that can include multiple logical layers. At corresponding layers of the protocol stack, operating system 252 includes control mechanisms and data structures to perform functions associated with that layer.

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

[0035] System 200 can also include a communication infrastructure 240. Communication infrastructure 240 provides, for example, communication between processor 210, one or more transceivers 220a-n, and memory 250. In some implementations, communication infrastructure 240 can be a bus. Processor 210, together with computer instructions stored in memory 250, performs operations that enable system 200 of system 100 to implement techniques to enhance user experience in low data use cases with WUS on as described herein in accordance with some aspects of the present disclosure. Alternatively, processor 210 can be “hard coded” to implement techniques to enhance user experience in low data use cases with WUS on as described herein.

[0036] The one or more transceivers 220a-220n transmit and receive communication signals enabling techniques for enhancing user experience in low data use cases with WUS on according to some aspects, and can be coupled to antennas 260. The antennas 260 can include one or more antennas, which can be of the same or different types. The one or more transceivers 220a-220n allow the system 200 to communicate with other devices, which can be wired and / or wireless. In some examples, the one or more transceivers 220a-220n can include processors, controllers, radios, sockets, plugs, amplifiers, filters, buffers, and similar circuitry / devices for connecting to and communicating on networks. According to some examples, the one or more transceivers 220a-220n can include one or more circuits for connecting to and communicating on wired and / or wireless networks.

[0037] According to some aspects, the one or more transceivers 220a-220n can include cellular subsystems, WLAN subsystems, and / or Bluetooth™ subsystems, each including its own radio transceiver and protocols, as will be appreciated by one of skill in the art based on the discussion provided herein. In some implementations, the one or more transceivers 220a-220n can include more or less systems for communicating with other devices.

[0038] In some examples, the one or more transceivers 220a-220n can include one or more circuits (including a WLAN transceiver) for enabling connectivity and communication via a WLAN network, such as but not limited to a network based on standards described in IEEE 802.11. Additionally or alternatively, the one or more transceivers 220a-220n can include one or more circuits (including a Bluetooth™ transceiver) to enable connectivity and communication based on, for example, a Bluetooth™ protocol, a Bluetooth™ Low Energy protocol, or a Bluetooth™ Low Energy Remote protocol. For example, the transceiver 220n can include a Bluetooth™ transceiver.

[0039] Additionally, the one or more transceivers 220a-220n can include one or more circuits (including a cellular transceiver) for connecting to and communicating on a cellular network, such as 5G NR, etc. For example, the one or more transceivers 220a-220n can be configured to operate according to one or more of Rel-15, Rel-16, Rel-17, or other releases of 3GPP standards.

[0040] Figure 3An example connected mode DRX configuration 300 is illustrated in accordance with some aspects of the present disclosure. The DRX configuration specifies a periodic repetition of an on-duration, and then specifies a possible inactivity period. In the example 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 remains monitoring the PDCCH for potential subsequent data scheduling until the DRX inactivity timer expires. However, if no data is scheduled, the UE 102 can turn off its RF circuitry (in the transceiver) and enter a sleep state. The UE 102 then wakes up to monitor the PDCCH during the periodically configured DRX on-duration.

[0041] 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 only monitor the PDCCH during the configured DRX on-duration results in a significant power saving at the UE 102. However, since the UE 102 does not know exactly when it can receive a downlink resource allocation, the UE typically monitors the PDCCH during the DRX on-duration even when no transmission is scheduled. This unnecessary PDCCH monitoring can consume a significant amount of power.

[0042] Further improvements in power consumption can be achieved if the network tells the UE 102 whether it should wake up and monitor the PDCCH during the upcoming DRX on-duration. 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 a long DRX cycle and checks a WUS indicator. When the UE 102 expects to receive data, the WUS indicator is set to inform 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 inform the UE 102 to remain in a sleep state for the entire DRX cycle, thereby minimizing unnecessary PDCCH monitoring.

[0043] According to some aspects, BS 104 transmits the WUS indicator to UE 102 using DCI format 2_6. However, other DCI formats or non-DCI communication 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, the Cyclic Redundancy Check (CRC) of DCI 2_6 is scrambled by the Power Saving Radio Network Temporary Identifier (PS-RNTI) corresponding to UE 102.

[0044] exist Figure 3 In the example, UE 102 wakes up and checks the WUS indicator (e.g., 302b, 304b, and 306b) before the start of each DRX cycle (e.g., 302a, 304a, and 306a). In the example, WUS indicator 302b is set to false (e.g., "0"), 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, the next WUS indicator 304b is set to true (e.g., "1"), indicating that UE 102 expects to receive data during DRX cycle 304a. Therefore, UE 102 starts a DRX on-duration timer for DRX cycle 304a. Consequently, UE 102 wakes up and remains in active mode during the on-duration 304c of DRX cycle 304a, and monitors the PDCCH.

[0045] In addition, Figure 3In the example of FIG. 3, the WUS indicator 306b transmitted by the BS 104 is not successfully detected by the UE 102. According to aspects, the WUS indicator (e.g., in DCI format 2_6) can 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 aspects, the WUS indicator 306b can not be detected by the UE 102 when the UE 102 and the BS 104 are out of sync. According to aspects, the WUS 306b can not be detected by the UE 102 when the UE 102 is in a heavily loaded cell. According to aspects, the WUS indicator 306b can not be detected by the UE 102 when the UE 102 is in mobility conditions and misses a tracking area update. According to aspects, the WUS indicator 306b can not be detected by the UE 102 when the UE 102 is performing a BWP switch that results in reconfiguration of the connected mode DRX mode. According to aspects, the WUS indicator 306b can not be detected by the UE 102 when a change in traffic pattern results in reconfiguration of the DRX mode. According to aspects, the WUS 306b can not be detected by the UE 102 when the UE is in high speed mobility conditions (e.g., HST scenario).

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

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

[0048] exist Figure 3 In the example, 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), UE 102 wakes up during the on-duration 306c of 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), UE 102 does not wake up during the on-duration 306c of DRX cycle 306a. As mentioned earlier, as a result of not waking up during DRX cycle 306a, UE 102 may miss receiving scheduled downlink data. When UE 102 has already been scheduled with a transmission it cannot detect in the downlink, BS 104 retransmits the data at a later time, and this retransmission may result in increased latency. When users are receiving latency-sensitive services, the degradation of user experience can be severe.

[0049] For example, when a user is receiving latency-sensitive services (e.g., streaming video), missed detection by WUS can lead to a severe degradation in user experience (e.g., video pauses or reduced video quality). Other example scenarios where missed detection by WUS can lead to a severe degradation in user experience include: mobility scenarios where the UE moves from one cell to another, UEs switching their active bandwidth portion (BWP), UEs in high-speed train scenarios, and UEs configured with carrier aggregation.

[0050] Figure 4An example method 400 for reducing or avoiding user experience degradation when a WUS is not successfully received at the UE 102 according to some aspects of the present disclosure is illustrated. For convenience, the method 400 will be described as being performed by the UE 102, but the method 400 can be performed by any suitable system or apparatus. Figures 1 to 3 and Figure 9 The functions of the elements of Figure 4 , for example, Figure 4 may be performed by the UE 102. For example, the processor 210 can perform or cause the performance of the functions of Figure 2 in conjunction with other elements of Figure 4 . The method 400 can also be performed by the system 200 of Figure 2 and / or the computer system 900 of Figure 9 . However, the method 400 is not limited to the specific aspects depicted in those figures, and can be performed using other systems as will be appreciated by one skilled in the art. It will be understood that not all of the operations can be necessary, and that the operations can not be performed in the same order as shown in Figure 4 .

[0051] At 402, it is determined whether the network supports WUS in combination with carrier aggregation or dual connectivity. According to some aspects, the network (e.g., BS 104 and BS 106) transmits a UE capability enquiry message to request capability information from the UE 102. The network can specify the type of RAT for which the network is requesting capability information (e.g., NR, EUTRA-NR, EUTRA, etc.). According to some aspects, the UE capability enquiry message can include a UE capability request filter that allows the network to request specific capability information (e.g., capabilities related to DRX, carrier aggregation, dual connectivity, multi-SIM, etc.) rather than a complete set of capabilities.

[0052] According to some aspects, the UE 102 responds to the network using a UE capability information message. If the UE 102 supports WUS, the UE can include a “drx-Adaption-rl6” parameter in the capability information message. According to some aspects, the UE 102 transmits a capability information message that includes information corresponding to supported frequency band combinations for carrier aggregation. Alternatively or additionally, the UE 102 transmits a capability information message that includes a specific field indicating the support of dual connectivity by the UE 102 (e.g., NRDC support or ENDC support). According to some aspects, the UE 102 can transmit a capability information message that indicates the support of carrier aggregation by the UE 102 in a dual connectivity context by indicating how to aggregate multiple carriers across both a primary node and a secondary node.

[0053] If the network supports carrier aggregation, the network communicates to the UE 102 parameters and configuration information corresponding to carrier aggregation through RRC signaling. The carrier aggregation configuration information can include configuration of a primary cell and one or more secondary cells as well as details about the frequency bands and channels used for each component carrier involved in the aggregation. If the network supports dual connectivity, the network communicates to the UE 102 parameters and configuration information corresponding to dual connectivity through RRC signaling. The dual connectivity configuration can include allocation of a master cell group (MCG) and a secondary cell group (SCG) as well as specific bearers for NRDC or ENDC split between them.

[0054] If the network supports WUS on carrier aggregation or dual connectivity, the network communicates to the UE 102 parameters and configuration information corresponding to WUS through RRC signaling in addition to the configuration information corresponding to carrier aggregation or dual connectivity. According to some aspects, the network configures the UE 102 with one or more of the following WUS parameters: 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 location 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 on carrier aggregation or dual connectivity, the example method 400 ends at 412. However, if the network supports WUS carrier aggregation or dual connectivity, the method 400 proceeds to 404.

[0055] At 404, a determination is made as to whether the UE 102 supports WUS on carrier aggregation or dual connectivity. According to some aspects, the UE 102 can transmit its capability information to the network in response to a capability enquiry from the network. As indicated above, if the UE 102 supports WUS, the capability information can include the “drx-Adaption-r16” parameter. According to some aspects, if the UE 102 supports carrier aggregation, the UE transmits a capability information message that includes information corresponding to the supported frequency band combinations for carrier aggregation. Alternatively or additionally, if the UE 102 supports dual connectivity, the UE 102 transmits a capability information message that includes a specific field indicating the UE’s 102 support for dual connectivity (e.g., NRDC support or ENDC support). According to some aspects, the UE 102 can transmit capability information that indicates its support for carrier aggregation in the context of dual connectivity by indicating how multiple carriers are aggregated across both a master node and a secondary node. If the UE 102 does not support WUS on carrier aggregation or dual connectivity, the example method 400 ends at 412. However, if the UE 102 supports WUS on carrier aggregation or dual connectivity, the method 400 proceeds to 406.

[0056] At 406, a determination is made as to whether a wake-up trigger condition is satisfied. According to some aspects, the wake-up trigger condition is satisfied if the UE 102 finds itself in a situation in which a missed detection of a WUS can result in a severe degradation of user experience. According to some aspects, the wake-up trigger condition is satisfied when a predetermined type of application (e.g., a video messaging application) is active at the UE 102. According to some aspects, the wake-up trigger condition is satisfied when the UE 102 receives a predetermined type of traffic (e.g., bursty data traffic). According to some aspects, the wake-up trigger condition is satisfied if the UE 102 receives latency sensitive traffic (e.g., real-time video communication, streaming traffic, etc.). According to some aspects, the wake-up trigger condition is satisfied if the UE 102 is in a mobility situation, such as a handover or redirection from one cell to another cell. According to some aspects, the wake-up trigger condition is satisfied 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 satisfied if the network configures the UE 102 with HST on SIB2. If the wake-up trigger condition is not satisfied, the example method 400 ends at 412. However, if the wake-up trigger condition is satisfied, the method 400 proceeds to 408.

[0057] At 408, a determination is made as to whether the ps-WakeUp parameter is set to false for the n-th cell (e.g., a cell on an aggregated component carrier) or dual connectivity cell to which the UE 102 is connected. According to some aspects, the network configures the UE 102 with an RRC parameter related to the WUS. The RRC parameter includes an indication of whether the ps-wakeUp parameter is enabled. For example, the RRC parameter can indicate 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.

[0058] At 410, according to some aspects, based on a determination that the wake-up trigger condition is satisfied and the ps-wakeUp parameter is set to false, the UE 102 wakes up during the DRX on-duration as long as the wake-up trigger condition is satisfied. Alternatively, based on a determination that the wake-up trigger condition is satisfied 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 satisfied.

[0059] Figure 5An example method 500 for reducing or avoiding user experience degradation when a WUS is not successfully received at the UE 102 due to a BWP switch is illustrated in accordance with some aspects of the present disclosure. For convenience, the method 500 will be described with respect to the components of the UE 102 of FIG. 2. Figures 1 to 3 and Figure 9 The functions of the elements of Figure 5 , for example, Figure 5 may be performed by the UE 102. For example, the processor 210 can perform or cause the performance of the functions of Figure 2 in conjunction with other elements of Figure 5 . The method 500 can also be performed by the system 200 of Figure 2 and / or the computer system 900 of Figure 9 . But the method 500 is not limited to the specific aspects depicted in those figures, and can be performed using other systems as will be appreciated by one of skill in the art. It should be understood that not all of the operations are necessarily required, and that the operations can not be performed in the same order as shown in Figure 5 .

[0060] At 502, it is determined whether the network supports WUS and downlink control information (DCI) based BWP switching in combination with carrier aggregation or dual connectivity. According to some aspects, the network (e.g., BS 104 and BS 106) transmits a UE capability enquiry message to request capability information from the UE 102. According to some aspects, the UE 102 responds to the network using a UE capability information message. If the UE 102 supports WUS, the UE includes a “drx-Adaption-r16” parameter in the capability information message. Alternatively or additionally, the UE 102 transmits a capability information message that includes a specific field indicating the UE’s 102 support for dual connectivity (e.g., NR DC support or ENDC support). According to some aspects, the UE 102 can transmit a capability information message that indicates the UE’s 102 support for carrier aggregation in a dual connectivity context by indicating how multiple carriers are aggregated across both a primary node and a secondary node.

[0061] If the network supports carrier aggregation, the network communicates to the UE 102, through RRC signaling, parameters and configuration information corresponding to carrier aggregation. Alternatively or additionally, if the network supports dual connectivity, the network communicates to the UE 102, through RRC signaling, parameters and configuration information corresponding to dual connectivity. According to some aspects, the network configures the UE 102 with multiple BWPs, and the network switches the active BWP among the multiple BWPs based on the activity of the UE 102. If the network supports WUS on carrier aggregation or dual connectivity, the network communicates, through RRC signaling, parameters and configuration information corresponding to WUS in addition to the configuration information corresponding to carrier aggregation or dual connectivity. According to some aspects, the network configures the UE 102 with one or more of the following WUS parameters: RNTI value “ps-RNTI-r16”, power saving offset value “ps-Offset-r16”, size of DCI format 2_6 “sizeDCI-2-6-r16”, location of DCI format 2_6 “ps-PositionDCI-2-6-r16”, and power saving wake up parameter “ps-WakeUp”.

[0062] If the network does not support WUS and BWP switching on carrier aggregation or dual connectivity, the example method 500 ends at 520. However, if the network supports WUS and BWP switching on carrier aggregation or dual connectivity, the method 500 proceeds to 504.

[0063] At 504, it is determined whether the UE 102 supports WUS and BWP switching on carrier aggregation or dual connectivity. According to some aspects, the UE 102 can transmit its capability information to the network in response to a capability enquiry from the network. As indicated above, if the UE 102 supports WUS, the UE 102 can include the “drx-Adaption-r16” parameter in the capability information message that it transmits. According to some aspects, if the UE 102 supports carrier aggregation, the UE can transmit a capability information message that includes information corresponding to the supported band combinations for carrier aggregation. Alternatively or additionally, if the UE 102 supports dual connectivity, the UE can transmit a capability information message that includes a specific field indicating the UE’s 102 support for dual connectivity (e.g., NR DC support or ENDC support). According to some aspects, the UE 102 can be configured with multiple BWPs, and the UE can be configured to switch the active BWP based on its activity. If the UE 102 does not support WUS on carrier aggregation or dual connectivity, the example method 500 ends at 520. However, if the UE 102 supports WUS on carrier aggregation or dual connectivity, the method 500 proceeds to 506.

[0064] At 506, it is determined whether the network configures a BWP for low data use cases on the nth cell (e.g., an aggregated component carrier) or a dual connectivity cell. According to some aspects, the network can configure the UE 102 to have multiple BWPs within a component carrier. According to some aspects, the UE 102 can be configured with up to four BWPs (e.g., BWPs 1-4). However, only one BWP can be active at any given time. According to some aspects, different BWPs can be optimized for different types of traffic or service requirements. As an example, BWP 1 with a low bandwidth can be optimized for low data use cases, and BWP 2 with a higher bandwidth can be optimized for high data use cases. Thus, the network can configure BWP 1 on the aggregated component carrier or on the dual connectivity cell for low data use cases. If the network does not configure a specific BWP for low data use cases on the aggregated component carrier or on the dual connectivity cell to the UE 102, the method 500 ends at 520. However, if the network configures a specific BWP for low data use cases on the aggregated component carrier or on the dual connectivity cell, the method 500 proceeds to 508.

[0065] At 508, it is determined whether the ps-WakeUp parameter is set to false for the nth cell (e.g., an aggregated component carrier) or a dual connectivity cell to which the UE 102 is connected. According to some aspects, the network configures the UE 102 with RRC parameters related to WUS. 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 500 ends at 520. However, if the ps-WakeUp parameter is not enabled (i.e., the ps-WakeUp parameter is set to “false”), the method 500 proceeds to 510.

[0066] At 510, it is determined whether the UE 102 is transmitting or receiving at a data rate less than a threshold (e.g., a threshold rate of M mbps) for a pre-defined amount of time (e.g., T seconds). If the UE 102 is transmitting or receiving at a data rate less than the threshold rate for T seconds, it is determined that the UE 102 is operating in a low data rate scenario, and the method 500 proceeds to 512. If the UE 102 is transmitting or receiving data at a rate greater than or equal to the threshold (e.g., the threshold rate) for T seconds, it is determined that the UE 102 is operating in a high data rate scenario, and the method 500 proceeds to 516.

[0067] At 512, based on determining that the UE 102 is transmitting or receiving at a data rate less than the threshold rate for T seconds, the network can command the UE 102 to switch to BWP 2 on the nth cell (e.g., nth carrier component) or a secondary cell group (SCG) cell, which is configured for low data use cases.

[0068] At 514, according to some aspects, based on determining that the UE 102 in the low data rate scenario is commanded to switch to BWP 2, the UE 102 is configured to wake up for T+Δ seconds during the DRX on duration during the BWP switch. Alternatively, based on determining that the UE 102 in the low data rate scenario is commanded to switch to BWP 2, the UE 102 is prevented from entering a sleep state for a duration of T+Δ seconds during the BWP switch. According to some aspects, Δ is a configurable parameter for the fine-tuning method 500.

[0069] At 516, based on determining that the UE 102 is transmitting or receiving at a data rate greater than or equal to the threshold rate for T seconds, the network can command the UE 102 to switch to BWP 1 on the nth cell (e.g., nth carrier component) or SCG cell, which is configured for high data use cases.

[0070] At 518, according to some aspects, based on determining that the UE 102 in the high data rate scenario is commanded to switch to BWP 1, the UE 102 is configured to wake up for T+Δ seconds during the DRX on duration during the BWP switch. Alternatively, based on determining that the UE 102 in the high data rate scenario is commanded to switch to BWP 1, the UE 102 is prevented from entering a sleep state for a duration of T+Δ seconds during the BWP switch. According to some aspects, Δ is a configurable parameter for the fine-tuning method 500.

[0071] Figure 6 An example method 600 for reducing or avoiding potential user experience degradation when a WUS is not successfully received at a multi-SIM UE is illustrated in accordance with some aspects of the present disclosure. For ease and not limitation, functions of Figures 1 to 3 and Figure 9 may be performed by the UE 102. For example, the processor 210 can perform or cause performance of the functions of Figure 6 in conjunction with other elements of Figure 6 . The method 600 can also be performed by the system 200 of Figure 2 and / or the apparatus 400 of Figure 6 . The method 600 can also be performed by the system 200 of Figure 2 and / or the apparatus 400 of Figure 9the computer system 900 executes. The method 600 is not limited to only those specific aspects depicted in the drawings and can be performed using other systems as will be appreciated by one skilled in the art. It is to be understood that not all of the operations shown can be required and that some operations can be performed in different orders than shown. Figure 6

[0072] At 602, it is determined whether the network supports WUS. As mentioned above, the UE 102 transmits its capability information to the network, and the UE capability information can include the "drx-Adaption-r16" parameter. If the network supports WUS, the network configures the UE 102 with one or more of the following parameters: the RNTI value "ps-RNTI-r16", the power saving offset value "ps-Offset-r16", the size of DCI format 2_6 "sizeDCI-2-6-r16", the location of DCI format 2_6 "ps-PositionDCI-2-6-r16", and the power saving wake up parameter "ps-WakeUp". If the network does not support WUS, the example method 600 ends at 612. However, if the network supports WUS, the method 600 proceeds to 604.

[0073] At 604, it is determined whether the UE 102 supports WUS and multi-SIM capability. According to some aspects, the UE 102 can transmit its capability information to the network in response to a capability inquiry from the network. If the UE 102 supports multi-SIM capability, the UE can transmit a capability information message indicating that the UE can support multiple SIM cards (e.g., the UE 102 has a first SIM and a second SIM). If the UE 102 supports WUS when using multiple SIM cards, the UE can include the cumulative "drx-Adaption-r16" parameter in the capability information corresponding to all of the multiple SIMs. Alternatively, the UE 102 can include the "drx-Adaption-r16" parameter in a capability information message for each SIM of the UE 102. If the UE 102 does not support WUS and multi-SIM card capability, the example method 600 ends at 612. However, if the UE 102 supports WUS and multi-SIM capability, the method 600 proceeds to 612.

[0074] ​At 606, it is determined whether a wake-up trigger condition is satisfied on any of the SIMs of the UE 102. According to some aspects, the wake-up trigger condition is satisfied when the UE 102 receives a predetermined type of traffic on any of the SIMs of the UE 102. According to some aspects, the wake-up trigger condition is satisfied if the UE 102 receives latency sensitive traffic (e.g., real-time video communication, streaming traffic, etc.) on any of the SIMs of the UE 102. According to some aspects, the wake-up trigger condition is satisfied if the UE 102 is in a mobility situation, such as a handover or redirection from one cell to another cell. According to some aspects, the wake-up trigger condition is satisfied 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 satisfied if the network configures the UE with HST on SIB2 on any of the SIMs of the UE 102. If the wake-up trigger condition is not satisfied, the example method 600 ends at 612. However, if the wake-up trigger condition is satisfied, the method 400 proceeds to 608.

[0075] At 608, it is determined whether the ps-WakeUp parameter is set to false on any of the SIMs of the UE 102. According to some aspects, the network configures the UE 102 with RRC parameters related to WUS. The RRC parameters include an indication of whether the ps-wakeUp parameter is enabled for each of the SIMs of the UE 102 (i.e., indicating whether the ps-WakeUp parameter is set to “true” or “false”). If the ps-wakeUp-r16 parameter is set to true on all of the SIMs of the UE 102, the example method 600 ends. However, if the ps-WakeUp parameter is not enabled (i.e., the ps-WakeUp parameter is set to “false”) on any of the SIMs of the UE 102, the method 600 proceeds to 610.

[0076] At 610, according to some aspects, based on a determination that the wake-up trigger condition is satisfied and the ps-wakeUp parameter is set to false on at least one SIM of the multi-SIM UE 102, the UE 102 is configured to wake up during the DRX on duration as long as the wake-up trigger condition is satisfied. Alternatively, based on a determination that the wake-up trigger condition is satisfied and the ps-wakeUp parameter is set to false on at least one SIM of the multi-SIM UE 102, the UE 102 is prevented from entering a sleep state as long as the wake-up trigger condition is satisfied.

[0077] Figure 7An example method 700 for reducing or avoiding user experience degradation when a WUS is not successfully received at a multi-SIM UE using carrier aggregation or dual connectivity is illustrated in accordance with some aspects of the present disclosure. For convenience, the method 700 will be described with respect to the components of the UE 102 of FIG. 1. Figures 1 to 3 and Figure 9 The functions of the elements of Figure 7 , for example, Figure 7 may be performed by the UE 102. For example, the processor 210 can perform or cause the performance of the functions of Figure 2 in conjunction with other elements of Figure 7 . The method 700 can also be performed by the system 200 of Figure 2 and / or the computer system 900 of Figure 9 . The method 700 is not limited to the particular aspects depicted in those figures, and can be performed using other systems as will be appreciated by one skilled in the art. It will be appreciated that not all of the operations can be needed, and that the operations can not be performed in the same order as illustrated by Figure 7 .

[0078] At 702, it is determined whether the network supports WUS in conjunction with carrier aggregation or dual connectivity. According to some aspects, the network transmits a UE capability enquiry message to request capability information from the UE 102. According to some aspects, the UE capability enquiry message can include a UE capability request filter that allows the network to request specific capability information (e.g., capabilities related to DRX, carrier aggregation, dual connectivity, multi-SIM, etc.) rather than a complete set of capabilities.

[0079] According to some aspects, the UE 102 responds to the network using a UE capability information message. In response to receiving the UE capability information, if the network supports carrier aggregation, the network communicates parameters and configuration information corresponding to carrier aggregation to the UE 102 through RRC signaling. The carrier aggregation configuration information can include configuration of a primary cell and one or more secondary cells, details about the frequency bands and channels used for each component carrier involved in the aggregation. Alternatively or additionally, if the network supports dual connectivity, the network communicates parameters and configuration information corresponding to dual connectivity to the UE 102 through RRC signaling. The dual connectivity configuration can include allocation of a master cell group (MCG) and a secondary cell group (SCG) and specific bearers for NRDC or ENDC split between them.

[0080] If the network supports WUS on carrier aggregation or dual connectivity, the network communicates the parameters and configuration information corresponding to WUS through RRC signaling in addition to the configuration information corresponding to carrier aggregation or dual connectivity. According to some aspects, the network configures the UE 102 with one or more of the following WUS parameters: RNTI value “ps-RNTI-r16”, power saving offset value “ps-Offset-r16”, size of DCI format 2_6 “sizeDCI-2-6-r16”, location of DCI format 2_6 “ps-PositionDCI-2-6-r16”, and power saving wake up parameter “ps-WakeUp”. If the network does not support WUS on carrier aggregation or dual connectivity, the example method 700 ends at 712. However, if the network supports WUS carrier aggregation or dual connectivity, the method 700 proceeds to 704.

[0081] At 704, it is determined whether the UE 102 supports WUS on carrier aggregation or dual connectivity and multi-SIM capability. According to some aspects, the UE 102 can transmit its capability information to the network in response to a capability enquiry from the network. If the UE 102 supports multi-SIM capability (e.g., the UE 102 has a first SIM and a second SIM), the UE 102 can transmit a capability information message indicating that it can support multiple SIM cards. If the UE 102 supports WUS when using multiple SIM cards, the UE can include the cumulative “drx-Adaption-r16” parameter in the capability information corresponding to the multiple SIMs.

[0082] According to some aspects, if the UE 102 supports carrier aggregation, the UE transmits a capability information message including information corresponding to the supported band combinations for carrier aggregation. Alternatively or additionally, if the UE supports dual connectivity, the UE transmits a capability information message including a specific field indicating the support of dual connectivity (e.g., NR DC support or ENDC support) by the UE 102. If the UE 102 does not support WUS on carrier aggregation or dual connectivity and multi-SIM capability, the example method 700 ends at 712. However, if the UE 102 supports WUS on carrier aggregation or dual connectivity and multi-SIM capability, the method 400 proceeds to 706.

[0083] At 706, a determination is made as to whether the ps-WakeUp parameter is set to false for the nth cell (e.g., a cell on an aggregated component carrier) or a dual connectivity cell to which the UE 102 is connected. According to some aspects, the network configures the UE 102 with RRC parameters related to the WUS. The RRC parameters include an indication of whether the ps-wakeUp parameter is enabled for the nth cell or the dual connectivity cell to which the UE 102 is connected (i.e., indicates whether the ps-WakeUp parameter is set to “true” or “false”). If the ps-wakeUp-r16 parameter is set to true for the nth cell or the dual connectivity cell, the example method 400 ends at 712. However, if the ps-WakeUp parameter is not enabled (i.e., the ps-WakeUp parameter is set to “false”), the method 700 proceeds to 708.

[0084] At 708, a determination is made as to whether the ps-WakeUp parameter is set to false on any of the SIMs of the multi-SIM UE 102. According to some aspects, the network configures the UE 102 with RRC parameters related to the WUS. The RRC parameters include an indication of whether the ps-wakeUp parameter is enabled for each of the SIMs of the UE 102 (i.e., indicates whether the ps-WakeUp parameter is set to “true” or “false”). If the ps-wakeUp-r16 parameter is set to true on all of the SIMs of the UE 102, the example method 700 ends at 712. However, if the ps-WakeUp parameter is not enabled (i.e., the ps-WakeUp parameter is set to “false”) on any of the SIMs of the UE 102, the method 700 proceeds to 710.

[0085] At 710, according to some aspects, based on a determination that the wake-up trigger condition is satisfied, the ps-wakeUp parameter is set to false on at least one of the SIMs of the multi-SIM UE 102, and the ps-WakeUp parameter is set to false for the nth cell or the dual connectivity cell to which the UE 102 is connected, the UE 102 is configured to wake up during the DRX on duration as long as the wake-up trigger condition is satisfied. According to some aspects, the wake-up trigger condition is satisfied when the UE 102 receives a predetermined type of traffic on any of the SIMs of the UE 102. According to some aspects, the wake-up trigger condition is satisfied if the UE 102 receives latency sensitive traffic (e.g., real-time video communications, streaming traffic, etc.) on any of the SIMs of the UE 102. Alternatively, based on a determination that the wake-up trigger condition is satisfied and the ps-wakeUp parameter is set to false on at least one of the SIMs of the multi-SIM UE 102, the UE 102 is prevented from entering a sleep state as long as the wake-up trigger condition is satisfied.

[0086] Figure 8 Example method 800, performed by a UE according to some aspects of this disclosure, is illustrated for enhancing the user experience in low data rate use cases when a wake-up signal is enabled. For convenience and not limitation, further details are available regarding... Figures 1 to 4 and Figure 9 To describe the components Figure 8 ,For example, Figure 8 The functionality can be performed by UE 102. For example, processor 210 can be combined with... Figure 2 Other components perform or cause execution Figure 8 The function. Method 800 can also be derived from... Figure 2 System 200 and / or Figure 9 The method is executed by computer system 900. However, method 800 is not limited to the specific aspects depicted in the figures, and other systems may be used to perform the method, as those skilled in the art will understand. It should be understood that not all operations may be necessary, and these operations may not be performed in accordance with... Figure 8 Perform them in the same order as shown.

[0087] At 802, UE 102 determines whether it is configured to operate using both a first connection and a second connection simultaneously. According to some aspects, the UE is configured to operate using carrier aggregation, and the first connection and the second connection may correspond to a first bandwidth portion (BWP) and a second BWP, respectively. According to some aspects, the UE is configured to operate using dual connectivity, and may establish a first connection with a first base station and a second connection with a second base station. According to some aspects, the UE is configured to operate using a dual subscriber identity module (SIM), and may use a first SIM to establish a first connection and a second SIM to establish a second connection. If the UE is not configured to operate using both the first and second connections simultaneously, example method 800 ends at 812. However, if the UE is configured to operate using both the first and second connections simultaneously, method 800 proceeds to 804.

[0088] At 804, based on the determination that UE 102 is configured to operate using both the first and second connections simultaneously, UE 102 determines whether a Wake-up Signal (WUS) indicator corresponding to the first Discontinuous Receive (DRX) cycle has been received. According to some aspects, the WUS indicator corresponding to the first DRX cycle is received within Downlink Control Information (DCI) format 2_6. If the WUS indicator corresponding to the first DRX cycle is received, example method 800 terminates at 812. However, if no WUS indicator corresponding to the first DRX cycle is received, method 800 proceeds to 806.

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

[0090] At 808, based on determining that the wake-up trigger condition is satisfied, the UE 102 determines whether it is configured with a power saving wake-up (ps-WakeUp) parameter. If the UE is not configured with the ps-WakeUp parameter, the example method 800 ends at 812. However, if the UE is configured with the ps-WakeUp parameter, the method 800 proceeds to 810.

[0091] At 810, based on determining that the UE 102 is configured with the ps-WakeUp parameter, based on determining that the ps-WakeUp parameter is set to false, and based on determining that no WUS indicator corresponding to the first DRX cycle is received, the UE 102 is configured to remain in an active state during a DRX off duration period of the first DRX cycle.

[0092] According to some aspects, based on determining that no WUS indicator corresponding to the first DRX cycle is received, the UE can be configured to transition from a sleep state to an active state during a DRX on duration period of the first DRX cycle. According to some aspects, based on determining that a WUS indicator corresponding to the second DRX cycle is received, and based on determining that the WUS indicator corresponding to the second DRX cycle is set to false, the UE can be configured to transition from a sleep state to an active state during a DRX on duration period of the second DRX cycle.

[0093] Various aspects can be implemented, for example, using one or more computer systems, such as Figure 9The illustrated computer system 900) to implement the techniques described herein. The computer system 900 can be any well-known computer capable of performing the functions described herein, such as a computer Figure 1 The computer system 900 includes one or more processors (also called central processing units, or CPUs) such as a processor 904. The processor 904 is connected to a communication infrastructure 906 (e.g., a bus). The computer system 900 also includes a user input / output interface 902 through which the system 900 receives a user input and / or provides a user output to a user. The user input / output interface 902 can include, for example, a monitor, a keyboard, a pointing device, etc. The computer system 900 further includes a main memory 908, such as a random access memory (RAM), and a secondary memory 910. The secondary memory 910 can include, for example, a hard disk drive 912 and / or a removable storage drive 914. The removable storage drive 914 can be a floppy disk drive, a magnetic tape drive, an optical disk drive, a tape backup device, and / or any other storage device.

[0094] The computer system 900 can further include a storage device or memory 910. The storage device 910 can include, for example, a hard disk drive 912 and / or a removable storage drive 914. The removable storage drive 914 can be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a tape backup device, and / or any other storage device.

[0095] The removable storage drive 914 can interact with a removable storage unit 918. The removable storage unit 918 includes a computer-usable or computer-readable medium 920 on which is stored computer software (control logic) and / or data. The removable storage unit 918 can be a floppy disk, a magnetic tape, an optical disk, a DVD, an optical storage disk, and / or any other storage device.

[0096] According to some aspects, the secondary memory 910 can include other means, instrumentalities, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by the computer system 900. Such means, instrumentalities, or other methods can include, for example, a removable storage unit 922 and an interface 920. Examples of the removable storage unit 922 and the interface 920 can include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a storage stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0097] The computer system 900 can also include a communications or network interface 924. The communications interface 924 enables the computer system 900 to communicate and interact with any

[0098] The operations in the foregoing detailed description are described in terms of operations on data that are performed by functional blocks, single lines of code or other entities. This functionality can be implemented in various ways, particularly in terms of software, firmware, hardware, and / or any combination of these. In this context, software should be interpreted broadly to mean any quantifiable computer- readable medium that includes program instructions executable by one or more data processing devices, such as the computer system 900. For example, the software can include one or more computer programs, subroutines, functions, procedures, modules, applications, applets, and / or other code segments. The software can be stored on any type of non-transitory computer- readable medium, including the computer system 900, the main memory 908, the secondary memory 910, and the removable storage units 918 and 922, as well as any tangible articles of manufacture that embody the foregoing. Such software, when executed by the one or more data processing devices, causes the data processing devices to perform such operations as described herein.

[0099] Based on the teachings of the disclosure provided herein, it will be apparent to those having ordinary skill in the related art how to implement the aspects of the disclosure using any of the Figure 9 In particular, the aspects can operate with software, hardware, and / or operating systems other than those described herein.

[0100] It should be understood that the detailed description and not the summary and abstract are intended to explain the claimed application. The summary and abstract can set forth one or more but not all exemplary aspects of the present disclosure and thus are not intended to limit the present disclosure or the appended claims in any way.

[0101] While the disclosure has been described herein with reference to exemplary aspects and applications, it will be apparent to those of ordinary skill in the art that numerous modifications can be made without departing from the scope and spirit of the disclosure. For example, and without limiting the generality of this paragraph, the aspects are not limited to the software, hardware, firmware, and / or entities illustrated and / or described herein. In addition, the aspects (whether or not explicitly described herein) have significant utility outside the examples described herein.

[0102] This document has described various aspects using functional building blocks that exemplify specific implementations of functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are performed appropriately. Furthermore, alternative aspects may perform functional blocks, steps, operations, methods, etc., in a different order than that described herein.

[0103] References to “an aspect,” “aspect,” “an example,” “example,” or similar phrases herein indicate that the aspect described may include a particular feature, structure, or characteristic, but each aspect may not necessarily include that particular feature, structure, or characteristic. Furthermore, such wording does not necessarily refer to the same aspect. Additionally, when a particular feature, structure, or characteristic is described in conjunction with an aspect, whether or not it is explicitly mentioned or described herein, the combination of those features, structures, or characteristics with other aspects is within the knowledge of a person skilled in the art.

[0104] The breadth and scope of this disclosure should not be limited by any of the foregoing exemplary aspects, but should be defined solely by the following claims and their equivalents.

[0105] This disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with robust privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to privacy policies and measures that are recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable entity purposes and should not be shared or sold outside of these legitimate purposes. Furthermore, such collection / sharing should only occur upon receipt of informed consent from the user. Additionally, such entities should consider taking any necessary steps to protect and safeguard the right to access such personal information data and ensure that other entities with access to personal information data comply with the privacy policies and procedures of those other entities. Furthermore, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and privacy measures. Moreover, policies and measures should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including considerations of specific 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 Transfer and Accountability Act (HIPAA); while in other countries, health data 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), the user equipment (UE) comprising: A transceiver configured to enable wireless communication; as well as A processor, communicatively coupled to the transceiver and configured to: Determine whether the UE is configured to operate using both the first and second connections simultaneously; Based on the determination that the UE is configured to operate using both the first connection and the second connection simultaneously, it is determined whether a wake-up signal (WUS) indicator corresponding to the first discontinuous reception (DRX) cycle is received; Determine whether the wake-up trigger conditions are met; Based on the determination that the wake-up triggering condition is met, it is determined whether the UE is configured with a power-saving wake-up (ps-WakeUp) parameter; Based on determining that the UE is configured with the ps-WakeUp parameter, determining that the ps-WakeUp parameter is set to false, and determining that no WUS indicator corresponding to the first DRX cycle is received, the UE is configured to remain active during the DRX off duration period of the first DRX cycle.

2. The UE according to claim 1, wherein based on determining that the WUS indicator corresponding to the second DRX cycle is received and determining that the WUS indicator corresponding to the second DRX cycle 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 DRX on duration period of the second DRX cycle.

3. The UE of claim 2, wherein the WUS indicator corresponding to the second DRX cycle is received within downlink control information (DCI) format 2-6.

4. The UE of claim 1, wherein, based on determining that no WUS indicator corresponding to the first DRX cycle has been received, the processor is further configured to: The UE is configured to transition from a sleep state to an active state during the DRX on duration of the first DRX cycle.

5. The UE of claim 1, wherein the UE is configured to operate using carrier aggregation, and wherein the first connection and the second connection correspond to a first bandwidth portion (BWP) and a second BWP, respectively.

6. The UE of claim 1, wherein the UE is configured to operate using dual connectivity, and wherein the first connection is established with a first base station and the second connection is established with a second base station.

7. The UE of claim 1, wherein the UE is configured to operate using a dual subscriber identity module (SIM), and wherein a first SIM is used to establish the first connection, and a second SIM is used to establish the second connection.

8. The UE of claim 1, wherein the second connection is designated for receiving low-rate data, and the processor is further configured to: Determine if the application's data rate is less than the threshold; and Based on the determination that the data rate of the application is less than the threshold, the second connection is used for the application.

9. The UE according to claim 1, wherein when the UE is receiving real-time message transmission and reception services, it is determined that the wake-up triggering condition is met.

10. The UE according to claim 1, wherein the wake-up trigger condition is determined to be satisfied when the UE is performing a BWP handover.

11. A method of operating user equipment (UE), the method comprising: Determine whether the UE is configured to operate using both the first and second connections simultaneously; Based on the determination that the UE is configured to operate using both the first connection and the second connection simultaneously, it is determined whether a wake-up signal (WUS) indicator corresponding to the first discontinuous reception (DRX) cycle is received; Determine whether the wake-up trigger conditions are met; Based on the determination that the wake-up triggering condition is met, it is determined whether the UE is configured with a power-saving wake-up (ps-WakeUp) parameter; Based on determining that the UE is configured with the ps-WakeUp parameter, determining that the ps-WakeUp parameter is set to false, and determining that no WUS indicator corresponding to the first DRX cycle is received, the UE is configured to remain active during the DRX off duration period of the first DRX cycle.

12. The method of claim 11, further comprising, based on determining that the WUS indicator corresponding to the second DRX cycle has been received and determining that the WUS indicator corresponding to the second DRX cycle has been set to false: The UE is configured to transition from the sleep state to the active state during the DRX on duration period of the second DRX cycle.

13. The method of claim 11, wherein the UE is configured to operate using carrier aggregation, and wherein the first connection and the second connection correspond to a first bandwidth portion (BWP) and a second BWP, respectively.

14. The method of claim 11, wherein the UE is configured to operate using dual connectivity, and wherein the first connection is established with a first base station and the second connection is established with a second base station.

15. The method of claim 11, wherein the UE is configured to operate using a dual subscriber identity module (SIM), and wherein a first SIM is used to establish the first connection, and a second SIM is used to establish the second connection.

16. A non-transitory computer-readable medium (CRM) having instructions stored thereon, the instructions causing the user equipment (UE) to perform operations when executed by a processor, the operations including: Determine whether the UE is configured to operate using both the first and second connections simultaneously; Based on the determination that the UE is configured to operate using both the first connection and the second connection simultaneously, it is determined whether a wake-up signal (WUS) indicator corresponding to the first discontinuous reception (DRX) cycle is received; Determine whether the wake-up trigger conditions are met; Based on the determination that the wake-up triggering condition is met, it is determined whether the UE is configured with a power-saving wake-up (ps-WakeUp) parameter; Based on determining that the UE is configured with the ps-WakeUp parameter, determining that the ps-WakeUp parameter is set to false, and determining that no WUS indicator corresponding to the first DRX cycle is received, the UE is configured to remain active during the DRX off duration period of the first DRX cycle.

17. The non-transient CRM of claim 16, further comprising, based on determining that the WUS indicator corresponding to the second DRX cycle has been received, and based on determining that the WUS indicator corresponding to the second DRX cycle has been set to false: The UE is configured to transition from the sleep state to the active state during the DRX on duration period of the second DRX cycle.

18. The non-transient CRM of claim 16, wherein the UE is configured to operate using carrier aggregation, and wherein the first connection and the second connection correspond to a first bandwidth portion (BWP) and a second BWP, respectively.

19. The non-transient CRM of claim 16, wherein the UE is configured to operate using dual connectivity, and wherein the first connection is established with a first base station and the second connection is established with a second base station.

20. The non-transient CRM of claim 16, wherein the UE is configured to operate using a dual subscriber identity module (SIM), and wherein a first SIM is used to establish the first connection, and a second SIM is used to establish the second connection.

Images