WO2022126409A1

WO2022126409A1 - Drx adjustment for a multi-sim device

Info

Publication number: WO2022126409A1
Application number: PCT/CN2020/136701
Authority: WO
Inventors: Karthikeyan Sabapathi; Ramesh PANTHAM; Narendra Pulicherla; Praveen Peruru; Ling Xie
Original assignee: Qualcomm Incorporated
Priority date: 2020-12-16
Filing date: 2020-12-16
Publication date: 2022-06-23

Abstract

A wireless device, such as a multi-SIM UE, detects one or more collisions between discontinuous reception (DRX) based on a first subscription for a first radio access technology (RAT) and operation based on a second subscription for a second RAT. The wireless device transmits, to a network, timing information associated with the DRX based on the first RAT. A base station receives the timing information associated with the DRX based on the first RAT. The base station adjusts a DRX configuration for the wireless device based on the timing information.

Description

DRX ADJUSTMENT FOR A MULTI-SIM DEVICE

BACKGROUND Technical Field

The present disclosure relates generally to communication systems, and more particularly, to a discontinuous reception (DRX) timing adjustment in a multi-SIM device.

Introduction

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a user equipment (UE) . The apparatus may detect one or more collisions between discontinuous reception (DRX) based on a first subscription for a first radio access technology (RAT) and operation based on a second subscription for a second RAT. The apparatus may transmit, to a network, timing information associated with the DRX based on the first RAT.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a base station. The apparatus may receive, from a UE, timing information associated with discontinuous reception (DRX) based on the first RAT, the timing information being based on one or more collisions between the DRX based for the first RAT and UE operation based on a second subscription for a second RAT. The apparatus may adjust a DRX configuration for the UE based on the timing information.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

FIG. 4 illustrates an example communication flow between wireless devices.

FIG. 5 is a diagram illustrating example scenarios associated with CDRX-related collisions.

FIG. 6 illustrates example UE capability information.

FIG. 7 is a flowchart of a method of wireless communication.

FIG. 8 is a flowchart of a method of wireless communication.

FIG. 9 is a diagram illustrating an example of a hardware implementation for an example apparatus.

FIG. 10 is a diagram illustrating an example of a hardware implementation for an example apparatus.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

A UE may be configured by a base station for discontinuation reception (DRX) . When there is no data transmission in either direction (e.g., UL/DL) , the UE may operate using the DRX mode. In the DRX mode, the UE monitors a PDCCH channel discontinuously using a sleep and wake cycle. When the UE is in an RRC connected state or an RRC connected mode, the DRX may also be referred to as Connected Mode DRX (C-DRX) . DRX conserves battery power at the UE. In a non-DRX mode, the UE monitors for PDCCH in each subframe to check whether there is downlink data available. Continuous monitoring of the PDCCH drains the UE’s battery power.

A UE may include more than one subscriber identity module (SIM) . In some examples, the UE 402 may perform concurrent communication activities for multiple SIMs, such as for the first SIM and the second SIM. Such operation may be referred to as multi-SIM (MSIM) operation. The device comprising the multiple SIMs may be referred to as an MSIM device.

The multiple SIMs may share an RF front end of the UE, e.g., including one or more antennas. The UE may tune away from a subscription of the first SIM in order to use the RF front end to perform an activity for the subscription of the other SIM. Collisions, e.g., an overlap in time, may occur between wireless communication activities in a multi-SIM device. Due to the tune away from one subscription on one of the SIMs, the UE may be unable to wake up during a DRX cycle for that SIM. The UE may miss signaling from the base station, leading to increased latency, reduced throughput, and increased power use.

Aspects presented herein enable the UE to provide information to the base station that enables the base station to adjust communication with the UE having the DRX configuration (e.g., through an offset or an adjusted DRX configuration) in order to help the UE improve reception by avoiding, or reducing, collisions between operation based on the multiple SIMs at the UE.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC) ) . The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface) . The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN) ) may interface with core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface) . The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

A base station 102, whether a small cell 102' or a large cell (e.g., macro base station) , may include and/or be referred to as an eNB, gNodeB (gNB) , or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182'. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182”. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 /UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

Referring again to FIG. 1, in certain aspects, the UE 104 may include a discontinuous reception component 198 configured to detect one or more collisions between discontinuous reception (DRX) based on a first subscription for a first radio access technology (RAT) and operation based on a second subscription for a second RAT, and transmit, to a network, timing information associated with the DRX based on the first RAT. In certain aspects, the base station 180 may include a discontinuous reception component 199 configured to receive, from the UE, timing information associated with discontinuous reception (DRX) based on the first RAT, the timing information being based on one or more collisions between the DRX based for the first RAT and UE operation based on a second subscription for a second RAT, and adjust a DRX configuration for the UE based on the timing information. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While

subframes

3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.

Other wireless communication technologies may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols/slot and 2 ^μ slots/subframe. The subcarrier spacing and symbol length/duration are a function of the numerology. The subcarrier spacing may be equal to 2 ^μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology.

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK /negative ACK (NACK) ) feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318 TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with 198 of FIG. 1.

At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with 199 of FIG. 1.

The UE’s DRX configuration may be configured by the network using RRC signaling from a base station, such as in an RRC Connection Setup request or an RRC connection reconfiguration request. A DRX configuration may include the configuration of one or more timers and values. In some examples, the DRX configuration may include any of an ON duration Timer, a DRX inactivity timer, a DRX retransmission timer, a DRX UL retransmission timer, a long DRX cycle, a value of the DRX start offset, a DRX short cycle timer, and/or a short DRX cycle, among others. A DRX cycle may comprise a periodic repetition of an on duration in which the UE monitors for PDCCH from the base station and an off duration. FIG. 5 illustrates an example of a DRX cycle 500 including periodic on durations during which the UE monitors for PDCCH and off durations during which the UE may not monitor for the PDCCH. The off duration may be referred to as a DRX opportunity. During the off duration, the UE does not monitor for PDCCH. The UE may enter a sleep mode or a low power mode in which the UE minimizes power consumption by shutting down a radio frequency (RF) function without detecting communication from the base station.

The on duration timer may correspond to a number of consecutive PDCCH subframes to be monitored or decoded when the UE wakes up from the off duration in the DRX Cycle. The DRX retransmission timer may correspond to a consecutive number of PDCCH subframes for the UE to monitor when a retransmission is expected by the UE. The DRX inactivity timer may correspond to an amount of time before the UE may again enter the off duration following successfully decoding PDCCH. The amount of time may be in terms of a transmission time interval (TTI) duration. After a UE successfully receives downlink data, the DRX Inactivity Timer may start counting a number of subframes. If any uplink or downlink data transmissions occur while the DRX inactivity timer is running, the timer restarts. If the DRX inactivity timer expires without uplink or downlink activity, the UE may enter the DRX cycle to achieve power savings. The UE may start with a short DRX cycle. The DRX short cycle may correspond to a first DRX cycle that the UE enters after successful expiration of DRX inactivity timer. FIG. 5 illustrates an example 550 showing an example DRX short cycle. The UE may operate using the short DRX cycle until a DRX short cycle timer expires. Once the DRX short cycle expires, the UE may enter a long DRX cycle. The example 550 in FIG. 5 also illustrates an example DRX long cycle. A DRX short cycle timer may correspond to a number of consecutive subframes during which the UE follows the short DRX cycle after the DRX inactivity timer has expired. The UE may further be able to transition to an idle mode DRX based on an RRC inactivity timer.

A UE may include more than one subscriber identity module (SIM) . FIG. 4 illustrates an example of a UE 402 that includes a first SIM 401 and a second SIM 403. In some examples, the UE 402 may perform concurrent communication activities for multiple SIMs, such as for the first SIM 401 and the second SIM 403. Such operation may be referred to as multi-SIM (MSIM) operation. The device comprising the multiple SIMs may be referred to as an MSIM device. The MSIM operation may be fully concurrent, e.g. with an activity for one SIM being performed at a time that overlaps with a different activity for another SIM.

The SIMs may operate in different modes or in similar modes. For example, one of the SIMs may operate in a DRX mode while the other SIM operates in an idle mode, e.g., performing idle mode activities such as monitoring or decoding pages from a base station, performing measurements, performing cell acquisition, or receiving system information from a base station, among other examples. In another example, one SIM may operate in a first DRX mode, and the other SIM may operate in a second DRX mode. These examples are non-limiting, and the aspects presented herein may similarly be applied for SIMs operating in other modes.

In some aspects, the second SIM 403 may be for the same radio access technology (RAT) as the first SIM 401. In some examples, the first SIM 401 and the second SIM 504 may both operate based on NR. In other aspects, the second SIM 403 may operate using a different RAT than the first SIM 401. For example, one of the SIMs (e.g., 401 or 403) may operate based on NR, and the other SIM may operate based on NR-U, LTE, WCDMA, GSM, or 1x, among other examples. In some examples, one SIM may be for a designated data subscriber (DDS) RAT and the other SIM may be for a non-DDS RAT.

Collisions, e.g., an overlap in time, may occur between wireless communication activities in a multi-SIM device. The multiple SIMs (e.g., 401, 403) may share an RF front end of the UE, e.g., including one or

more antennas

409a, 409b, etc. The UE may tune away from a subscription of the first SIM in order to use the RF front end to perform an activity for the subscription of the other SIM.

For example, a UE may support NR and other RATs (e.g., NR/LTE) , and may have connected mode DRX (CDRX) configured on both the NR dedicated data subscription (DDS) RAT (e.g., a first subscription, Sub1) and the non-DDS RAT (s) (e.g., a second subscription, Sub2) . A wakeup for the DRX cycle of one SIM may collide, or overlap in time, with a different activity on the other SIM. In some examples, a collision may occur between a DRX wakeup for one subscription (e.g., a first SIM) that overlaps in time with DRX wakeup for the other subscription (e.g., the second SIM) . For example, an NR CDRX (e.g., DDS) wakeup period for the first SIM may overlap in time with a non-DDS idle mode DRX page wakeup for the second SIM. As another example, an NR DDS CDRX wakeup period may overlap in time with a non-DDS CDRX wakeup period, . In some examples, a DRX mode may not be usable if the first and second SIM are both in a connected mode, e.g., it may not be possible for the UE to operate in a CDRX mode when both the first SIM and the second SIM are in a connected mode. For example, an NR DDS CDRX may be unusable (e.g., long DRX cycle < 320 ms) when both the first and second subscription (e.g., for SIM 1 and SIM 2) are in the connected mode.

As the UE may tune away from one SIM in order to use baseband or RF front end resources for the other SIM, the SIM for which the UE has tuned away may not have an opportunity to wake up for a DRX cycle. The UE may miss messages for that SIM causing a degradation in performance. For example, when a collision occurs between activities of the multiple SIMs, an NR DDS subscription may miss or skip an opportunity to wake up at the overlapping CDRX ON occasion (e.g., as specified by the frame number and the slot number) , because the baseband or RF resources may be unavailable due to the tune away of the multi-SIM device to the other subscription.

Failure for the NR DDS to wake up at the specified CDRX ON occasions may be associated with several negative consequences. For example, it may result in a failure to decode signaling messages or the connected mode radio bearer scheduling from the network in the current CDRX wakeup occasion. As a result, connectivity and/or radio link synchronization with the base station may be affected due to the missed signaling for mobility procedures, beam management procedures, SCell activation/deactivation, and/or BWP switching, etc. Accordingly, the UE may declare a radio link failure (RLF) and may attempt to reestablish the radio connection from the idle state through procedures associated with the random-access channel (RACH) .

A delayed wakeup may be performed on the NR DDS after the tune away is completed, and the retransmissions of the scheduled data at the PHY, MAC, and/or RLC layers from the base station may be received. However, PHY layer HARQ may be recombined in the process, and the decoding performance may depend on the radio channel quality. The process may involve signaling of NACK status PDUs at RLC and PDCP layers to recover the PDUs lost in the wakeup. Accordingly, a higher latency may result, because the UE may miss signaling leading to a retransmission and delayed reception. The delay and added transmission may lead to a reduction in the UE throughput performance. In other words, the user may experience poor performance. Furthermore, the increased wakeup timeline in the NR DDS due to the delayed wakeup and attempts to recover the scheduling from retransmissions may increase power consumption.

FIG. 4 illustrates an example communication flow 400 between wireless devices. At 410, the UE 402 may detect collisions between DRX based on a first subscription for a first RAT (e.g., using SIM 1 401) and operation based on a second subscription for a second RAT (e.g., using SIM 2 403) . For example, the DRX manager 405 may detect the overlap in time between the operations for the SIMs. As illustrated in FIG. 6, the UE 402 may detect collisions based on a number of scenarios. In some aspects, the one or more collisions may be based on a first DRX wakeup for the first RAT (e.g., base station 404) overlapping in time with an idle mode DRX page wakeup for the second RAT (e.g., RAT 407) . In some aspects, the one or more collisions may be based on a first DRX wakeup for the first RAT overlapping in time with a connected mode DRX page wakeup for the second RAT. In some aspects, the one or more collisions may be based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT and the second subscription for the second RAT. FIG. 4 illustrates an example, in which the UE may tune away from the first SIM to monitor for a page 406 from the second RAT 407. During the tune away, the UE 402 may miss a wakeup occasion for the DRX cycle of the first SIM and may miss the indication to wake up 408. Thus, the UE might not wake up for the first RAT and may miss communication on the first RAT.

In order to help to avoid or address the collision, the UE may provide assistance information to a base station for at least one of the RATs. The assistance information may enable the base station to adjust scheduling for the UE, or a configuration for the UE, in order to avoid potential collisions and/or to improve power savings of the UE through a more efficient configuration.

As illustrated at 412, the UE 402 may transmit to the base station 404, and the base station 404 may receive from the UE 402, timing information associated with the DRX based on the first RAT. In some aspects, the UE may provide the information to the network in response to detecting a single collision. In some aspects, the UE 402 may transmit the timing information to the network in response to detecting a threshold number of collisions. In some aspects, the UE 402 may transmit to the network (e.g., the base station 404) , and the base station 404 may receive from the UE 402, the timing information in UE capability information (e.g., in a UEAssistanceInformation message comprising a UE assistance information element (IE) ) . In some aspects, the UE 402 may transmit to the network (e.g., the base station 404) , and the base station 404 may receive from the UE 402, the timing information in a delay budget report (e.g., in a DelayBudgetReport parameter) . The delay budget report may be comprised in the UE assistance information IE, in some examples. For example, the delay budget report parameter may indicate a period of time. The period of time may provide a recommendation to the base station to avoid the collision between the DRX cycle of the first SIM and the operation of the other SIM. As a set of non-limiting examples, the delay budget parameter may indicate one of a set of possible time offset values (e.g., including positive and negative values) such as -1,280 ms, -640 ms, -320 ms, -160 ms, -80 ms, -60 ms, -40 ms, -20 ms, 0 ms, 20 ms, 40 ms, 60 ms, 80 ms, 160 ms, 320 ms, 640 ms, or 1, 280 ms, etc. In some aspects, the delay budget report may be specified in milliseconds (ms) to modify the current NR CDRX cycle duration to avoid collision with another subscription’s idle state or connected state wakeups. Although the timing information is referred to as a “delay budget report, ” the timing information that indicates a time adjustment to avoid an overlap in MSIM activity may also be referred to by a different name.

In some aspects, the UE 402 may indicate, in the timing information, a DRX cycle length to the network (e.g., the base station 404) in response to detecting the one or more collisions. In particular, the UE may indicate, in the timing information, either an increased DRX cycle length or a decreased DRX cycle length to the network (e.g., the base station 404) in response to detecting the one or more collisions. In one embodiment, the UE 402 may indicate, in the timing information, an offset value to the network (e.g., the base station 404) in response to detecting the one or more collisions.

At 414, the base station 404 may adjust a DRX configuration for the UE 402 based on the timing information. Thus, the UE assistance information with the delay budget report may trigger the base station to adjust the DRX configuration of the UE to avoid the collisions at the UE. The adjustment may be made via either an RRC connection reconfiguration or an RRC connection setup. The timing information may indicate for the network to offset a DRX cycle of the first SIM, e.g., in order to avoid the collision. The base station may respond by adjusting the DRX cycle by the offset, or by transmitting signaling to the UE at the indicated offset.

At 416, the base station 404 may configure a new DRX configuration for the UE 402 based on the timing information. The timing information may indicate for the network to reduce a DRX cycle of the first SIM, e.g., in order to increase opportunities for the UE to receiving signaling from the network. Thus, if some of the opportunities collide with operation of the other SIM, the UE may still have opportunities to receive the signaling from the first RAT. For example, if the UE detects one or more collisions for a DRX cycle having a length of 640 ms, the UE may indicate -320 ms. The base station may respond by adjusting the DRX cycle to 320 ms. Thus, even if the UE skips a wakeup occasion and waits until the next wake up occasion to receive the signaling from the base station 404, the UE may still receive the signaling based on a 640 ms period. In other examples, the UE may indicate 320 ms, which may indicate for the base station to apply a 320 ms DRX cycle. In other examples, the UE may indicate for the base station to increase the DRX cycle to avoid collisions or to reduce missed signaling from the base station. The UE may determine the timing information to indicate to the base station based on a traffic pattern of the first SIM. For example, the UE 402 may request a reduction in the DRX cycle if there is a higher amount of traffic for the first RAT, and the UE may request a longer DRX cycle if there is a lower amount of traffic for the first RAT. In some aspects, the base station 404 may apply a new offset for the DRX configuration based on the timing information.

At 418, the base station 404 may transmit to the UE 402, and the UE 402 may receive from the base station 404, an updated DRX configuration for the first RAT or the second RAT based on the timing information. In some aspects, the base station 404 may transmit to the UE 402, and the UE 402 may receive from the base station 404, a new offset for a DRX configuration for the first RAT or the second RAT based on the timing information.

FIG. 6illustrates non-limiting example scenarios associated with DRX-related collisions. In some aspects, as illustrated in the collision 601 in diagram 600, the one or more collisions may be based on a first DRX wakeup for the first RAT overlapping in time with an idle mode DRX page wakeup for the second RAT. In other aspects, the one or more collisions (e.g.,

collisions

603a and 603b) may be based on a first DRX wakeup for the first RAT overlapping in time with a connected mode DRX page wakeup for the second RAT, such as illustrated in the diagram 625. In other aspects, the one or more collisions may be based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT (e.g., that establishes a connection at 602 and remains in a connected mode) and the second subscription for the second RAT (e.g., that establishes a connection at 604 and remains in a connected mode) . For example, in diagram 650, the UE may determine that CDRX is not usable during the period 606 that both subscriptions are in a connected mode.

FIG. 7 is a flowchart 700 of a method of wireless communication. The method may be performed by a UE (e.g., the

UE

104, 350, the UE 402; the apparatus 902) . Optional aspects are illustrated with a dashed line. The method may enable the UE to assist the network in adjusting DRX for the UE due to overlapping MSIM activities that may cause the UE to skip a wakeup period.

At 702, the UE detects one or more collisions between DRX based on a first subscription for a first RAT and operation based on a second subscription for a second RAT. For example, 702 may be performed by the collision component 940 in FIG. 9. The one or more collisions may be based on a first DRX wakeup for the first RAT overlapping in time with an idle mode DRX page wakeup for the second RAT, e.g., as described in connection with 600 in FIG. 6. The one or more collisions may be based on a first DRX wakeup overlapping in time with a connected mode DRX page wakeup for the second RAT, e.g., as described in connection with 625 in FIG. 6. The one or more collisions may be based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT and the second subscription for the second RAT, e.g., as described in connection with 650 in FIG. 6.

At 704, the UE 402 may transmit to the base station timing information associated with the DRX based on the first RAT. For example, 704 may be performed by the timing information component 942 in FIG. 9 via the transmission component 934. As described in connection with FIG. 4, the UE may transmit the timing information in response to detecting a single collision (e.g., as illustrated in the example 600 in FIG. 6) or may transmit the timing information in response to detecting multiple collisions, e.g., a threshold number of collisions. The example 625 in FIG. 6 illustrates an example showing the detection of multiple collisions. The UE may transmit the timing information to the network in UE capability information, e.g., as described in connection with 412 FIG. 4. The UE may indicate a DRX cycle length to the network in response to detecting the one or more collisions. The UE may indicate an increased DRX cycle length to the network in response to detecting the one or more collisions. The UE may indicate a decreased DRX cycle length to the network in response to detecting the one or more collisions. As described above, the UE may determine the timing information to indicate to the base station (e.g., a reduction or increase) based on a traffic pattern (e.g., an amount of traffic and or historical pattern of traffic for the first RAT) . The UE may indicate an offset value to the network in response to detecting the one or more collisions.

Finally, at 706, the UE may receive from the base station an updated DRX configuration for the first RAT or the second RAT based on the timing information, e.g., as described in connection with FIG. 4. In some aspects, at 708, the UE may receive from the base station a new offset for a DRX configuration for the first RAT or the second RAT based on the timing information, e.g., as described in connection with FIG. 4. For example, 706 may be performed by the DRX component 944 in FIG. 9 via the reception component 930.

FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by a base station (e.g., the base station 102/180, 350, 404; the apparatus 1002) . Optional aspects are illustrated with a dashed line. The method may enable a base station to adjust communication with a UE having a DRX configuration in order to reduce latency and improve reception at a MSIM UE.

At 802, the base station may receive from the UE timing information associated with the DRX based on the first RAT. The base station may receive the timing information in UE capability information, e.g., as described in connection with 412 in FIG. 4. For example, the base station may receive the timing information in a delay budget report from the UE. The timing information may be based on one or more collisions between the DRX based on a first subscription for the first RAT and UE operation based on a second subscription for a second RAT. For example, 802 may be performed by the timing information component 1040 in FIG. 10 via the reception component 1030. The timing information may indicate a DRX cycle, e.g., a DRX cycle length requested by the UE. The timing information may indicate an increased DRX cycle length based on the one or more collisions at the UE. The timing information may indicate a decreased DRX cycle length based on the one or more collisions at the UE. The timing information may indicate an offset value.

At 804, the base station may adjust a DRX configuration for the UE based on the timing information. For example, 804 may be performed by the DRX component 1042 in FIG. 10. At 806, the base station may configure a new DRX configuration for the UE based on the timing information. In another embodiment, the base station may apply a new offset for the DRX configuration based on the timing information, as illustrated at 808. For example, 806 may be performed by the DRX component 1042 in FIG. 10. The one or more collisions may be based on a first DRX wakeup for the first RAT overlapping in time with an idle mode DRX page wakeup for the second RAT, e.g., as described in connection with 600 in FIG. 6. The one or more collisions may be based on a first DRX wakeup overlapping in time with a connected mode DRX page wakeup for the second RAT, e.g., as described in connection with 625 in FIG. 6. The one or more collisions may be based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT and the second subscription for the second RAT, e.g., as described in connection with 650 in FIG. 6. The base station may adjust the DRX configuration, e.g., based on any of the aspects described in connection with FIG. 4.

FIG. 9 is a diagram 900 illustrating an example of a hardware implementation for an apparatus 902. The apparatus 902 is a UE and includes a cellular baseband processor 904 (also referred to as a modem) coupled to a cellular RF transceiver 922 and one or more subscriber identity modules (SIM) cards 920, an application processor 906 coupled to a secure digital (SD) card 908 and a screen 910, a Bluetooth module 912, a wireless local area network (WLAN) module 914, a Global Positioning System (GPS) module 916, and a power supply 918. The cellular baseband processor 904 communicates through the cellular RF transceiver 922 with the UE 104 and/or BS 102/180. The cellular baseband processor 904 may include a computer-readable medium /memory. The computer-readable medium /memory may be non-transitory. The cellular baseband processor 904 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the cellular baseband processor 904, causes the cellular baseband processor 904 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor 904 when executing software. The cellular baseband processor 904 further includes a reception component 930, a communication manager 932, and a transmission component 934. The communication manager 932 includes the one or more illustrated components. The components within the communication manager 932 may be stored in the computer-readable medium /memory and/or configured as hardware within the cellular baseband processor 904. The cellular baseband processor 904 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 902 may be a modem chip and include just the baseband processor 904, and in another configuration, the apparatus 902 may be the entire UE (e.g., see 350 of FIG. 3) and include the aforediscussed additional modules of the apparatus 902.

The communication manager 932 includes a collision component 940 that is configured to detect collisions between DRX based on a first subscription for a first RAT and operation based on a second subscription for a second RAT, e.g., as described in connection with 702 in FIG. 7. The communication manager 932 further includes a timing information component 942 that is configured to transmit to the base station timing information associated with the DRX based on the first RAT, e.g., as described in connection with 704 in FIG. 7. The communication manager 932 further includes a DRX component 944 that is configured to receive from the base station an updated DRX configuration for the first RAT or the second RAT based on the timing information, or in another embodiment, to receive from the base station a new offset for a DRX configuration for the first RAT or the second RAT based on the timing information, e.g., as described in connection with 706 in FIG. 7.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 7. As such, each block in the aforementioned flowchart of FIG. 7 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

In one configuration, the apparatus 902, and in particular the cellular baseband processor 904, includes means for detecting collisions between DRX based on a first subscription for a first RAT and operation based on a second subscription for a second RAT; means for transmitting, to a network, timing information associated with the DRX based on the first RAT; and means for receiving an updated DRX configuration for the first RAT or the second RAT based on the timing information, or means for receiving a new offset for a DRX configuration for the first RAT or the second RAT based on the timing information. The aforementioned means may be one or more of the aforementioned components of the apparatus 902 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 902 may include the TX Processor 368, the RX Processor 356, and the controller/processor 359. As such, in one configuration, the aforementioned means may be the TX Processor 368, the RX Processor 356, and the controller/processor 359 configured to perform the functions recited by the aforementioned means.

FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1002. The apparatus 1002 is a BS and includes a baseband unit 1004. The baseband unit 1004 may communicate through a cellular RF transceiver 1022 with the UE 104. The baseband unit 1004 may include a computer-readable medium /memory. The baseband unit 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the baseband unit 1004, causes the baseband unit 1004 to perform the various functions described supra. The computer-readable medium /memory may also be used for storing data that is manipulated by the baseband unit 1004 when executing software. The baseband unit 1004 further includes a reception component 1030, a communication manager 1032, and a transmission component 1034. The communication manager 1032 includes the one or more illustrated components. The components within the communication manager 1032 may be stored in the computer-readable medium /memory and/or configured as hardware within the baseband unit 1004. The baseband unit 1004 may be a component of the BS 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

The communication manager 1032 includes a timing information component 1040 that is configured to receive from the UE timing information associated with the DRX based on the first RAT, the timing information being based on one or more collisions between the DRX based for the first RAT and UE operation based on a second subscription for a second RAT, e.g., as described in connection 802 in FIG. 8. The communication manager 1032 further includes a DRX component 1042 that is configured to adjust a DRX configuration for the UE based on the timing information, e.g., as described in connection with 804 in FIG. 8. The DRX component 1042 may be further configured to configure a new DRX configuration for the UE based on the timing information, or in another embodiment, to apply a new offset for the DRX configuration based on the timing information, e.g., as described in connection with 806 in FIG. 8.

The apparatus may include additional components that perform each of the blocks of the algorithm in the aforementioned flowchart of FIG. 8. As such, each block in the aforementioned flowchart of FIG. 8 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

In one configuration, the apparatus 1002, and in particular the baseband unit 1004, includes means for receiving, from the UE, timing information associated with DRX based on the first RAT, the timing information being based on one or more collisions between the DRX based on a first subscription for the first RAT and UE operation based on a second subscription for a second RAT; means for adjusting a DRX configuration for the UE based on the timing information; and means for configuring a new DRX configuration for the UE based on the timing information, or means for applying a new offset for the DRX configuration based on the timing information. The aforementioned means may be one or more of the aforementioned components of the apparatus 1002 configured to perform the functions recited by the aforementioned means. As described supra, the apparatus 1002 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the aforementioned means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the aforementioned means.

Therefore, when the multi-SIM UE detects a collision case, the UE may provide the timing information to the base station and may help avoid NR CDRX ON collision with Sub2 connected mode or idle mode DRX wakeups. Accordingly, the radio link synchronization with the base station may be maintained for the subscription without decoding issues, and NR reestablishment procedures may be avoided. This may help maintain or improve latency and throughput performance. Further, placing the DRX ON occasions for the two subscriptions in such a way that they are close enough to each other but do not collide may help reduce modem wakeup overhead, as one wakeup instead of two separate wakeups may be executed, which may bring about savings in power consumption.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” should be interpreted to mean “under the condition that” rather than imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

Aspect 1 is a method of wireless communication at a user equipment (UE) , comprising: detecting one or more collisions between discontinuous reception (DRX) based on a first subscription for a first radio access technology (RAT) and operation based on a second subscription for a second RAT; and transmitting, to a network, timing information associated with the DRX based on the first RAT.

Aspect 2 is the method of aspect 1, where the UE transmits the timing information to the network in response to detecting a threshold number of collisions.

Aspect 3 is the method of any of

aspects

1 and 2, where the UE transmits the timing information to the network in UE capability information.

Aspect 4 is the method of any of aspects 1 to 3, where the UE transmits the timing information to the network in a delay budget report.

Aspect 5 is the method of any of aspects 1 to 4, where the UE indicates a DRX cycle length to the network in response to detecting the one or more collisions.

Aspect 6 is the method of aspect 5, where the UE indicates an increased DRX cycle length to the network in response to detecting the one or more collisions.

Aspect 7 is the method of aspect 5, where the UE indicates a decreased DRX cycle length to the network in response to detecting the one or more collisions.

Aspect 8 is the method of any of aspects 1 to 7, where the UE indicates an offset value to the network in response to detecting the one or more collisions.

Aspect 9 is the method of any of aspects 1 to 8, further comprising: receiving an updated DRX configuration for the first RAT or the second RAT based on the timing information.

Aspect 10 is the method of any of aspects 1 to 8, further comprising: receiving a new offset for a DRX configuration for the first RAT or the second RAT based on the timing information.

Aspect 11 is the method of any of aspects 1 to 10, where the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with an idle mode DRX page wakeup for the second RAT.

Aspect 12 is the method of any of aspects 1 to 11, where the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with a connected mode DRX page wakeup for the second RAT.

Aspect 13 is the method of any of aspects 1 to 12, where the one or more collisions are based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT and the second subscription for the second RAT.

Aspect 14 is an apparatus for wireless communication, the apparatus being a user equipment (UE) , and including at least one processor coupled to a memory and configured to implement a method as in any of aspects 1 to 13.

Aspect 15 is an apparatus for wireless communication, the apparatus being a user equipment (UE) , and including means for implementing a method as in any of aspects 1 to 13.

Aspect 16 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement a method as in any of aspects 1 to 13.

Aspect 17 is a method of wireless communication at a base station serving a user equipment (UE) based on a first subscription for a first radio access technology (RAT) , comprising: receiving, from the UE, timing information associated with discontinuous reception (DRX) based on the first RAT, the timing information being based on one or more collisions between the DRX based on a first subscription for the first RAT and UE operation based on a second subscription for a second RAT; and adjusting a DRX configuration for the UE based on the timing information.

Aspect 18 is the method of aspect 17, further comprising: configuring a new DRX configuration for the UE based on the timing information.

Aspect 19 is the method of aspect 17, further comprising: applying a new offset for the DRX configuration based on the timing information.

Aspect 20 is the method of any of aspects 17 to 19, where the base station receives the timing information in UE capability information.

Aspect 21 is the method of any of aspects 17 to 20, where the base station receives the timing information in a delay budget report from the UE.

Aspect 22 is the method of any of aspects 17 to 21, where the timing information indicates a DRX cycle length.

Aspect 23 is the method of aspect 22, where the timing information indicates an increased DRX cycle length based on the one or more collisions.

Aspect 24 is the method of aspect 22, where the timing information indicates a decreased DRX cycle length based on the one or more collisions.

Aspect 25 is the method of any of aspects 17 to 24, where the timing information indicates an offset value.

Aspect 26 is the method of any of aspects 17 to 25, where the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with an idle mode DRX page wakeup for the second RAT.

Aspect 27 is the method of any of aspects 17 to 26, where the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with a connected mode DRX page wakeup for the second RAT.

Aspect 28 is the method of any of aspects 17 to 27, where the one or more collisions are based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT and the second subscription for the second RAT.

Aspect 29 is an apparatus for wireless communication, the apparatus being a base station, and including at least one processor coupled to a memory and configured to implement a method as in any of aspects 17 to 28.

Aspect 30 is an apparatus for wireless communication, the apparatus being a base station, and including means for implementing a method as in any of aspects 17 to 28.

Aspect 31 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement a method as in any of aspects 17 to 28.

Claims

A method of wireless communication at a user equipment (UE) , comprising:

detecting one or more collisions between discontinuous reception (DRX) based on a first subscription for a first radio access technology (RAT) and operation based on a second subscription for a second RAT; and

transmitting, to a network, timing information associated with the DRX based on the first RAT.
The method of claim 1, wherein the UE transmits the timing information to the network in response to detecting a threshold number of collisions.
The method of claim 1, wherein the UE transmits the timing information to the network in UE capability information.
The method of claim 3, wherein the UE transmits the timing information to the network in a delay budget report.
The method of claim 1, wherein the UE indicates a DRX cycle length to the network in response to detecting the one or more collisions.
The method of claim 5, wherein the UE indicates an increased DRX cycle length to the network in response to detecting the one or more collisions.
The method of claim 5, wherein the UE indicates a decreased DRX cycle length to the network in response to detecting the one or more collisions.
The method of claim 1, wherein the UE indicates an offset value to the network in response to detecting the one or more collisions.
The method of claim 1, further comprising:

receiving an updated DRX configuration for the first RAT or the second RAT based on the timing information.
The method of claim 1, further comprising:

receiving a new offset for a DRX configuration for the first RAT or the second RAT based on the timing information.
The method of claim 1, wherein the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with an idle mode DRX page wakeup for the second RAT.
The method of claim 1, wherein the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with a connected mode DRX page wakeup for the second RAT.
The method of claim 1, wherein the one or more collisions are based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT and the second subscription for the second RAT.
An apparatus for wireless communication, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

detect one or more collisions between discontinuous reception (DRX) based on a first subscription for a first radio access technology (RAT) and operation based on a second subscription for a second RAT; and

transmit, to a network, timing information associated with the DRX based on the first RAT.
The apparatus of claim 14, wherein the UE transmits the timing information to the network in response to detecting a threshold number of collisions.
The apparatus of claim 14, wherein the UE transmits the timing information to the network in UE capability information.
A method of wireless communication at a base station serving a user equipment (UE) based on a first subscription for a first radio access technology (RAT) , comprising:

receiving, from the UE, timing information associated with discontinuous reception (DRX) based on the first RAT, the timing information being based on one or more collisions between the DRX based on a first subscription for the first RAT and UE operation based on a second subscription for a second RAT; and

adjusting a DRX configuration for the UE based on the timing information.
The method of claim 17, further comprising:

configuring a new DRX configuration for the UE based on the timing information.
The method of claim 17, further comprising:

applying a new offset for the DRX configuration based on the timing information.
The method of claim 17, wherein the base station receives the timing information in UE capability information.
The method of claim 20, wherein the base station receives the timing information in a delay budget report from the UE.
The method of claim 17, wherein the timing information indicates a DRX cycle length.
The method of claim 22, wherein the timing information indicates an increased DRX cycle length based on the one or more collisions.
The method of claim 22, wherein the timing information indicates a decreased DRX cycle length based on the one or more collisions.
The method of claim 17, wherein the timing information indicates an offset value.
The method of claim 17, wherein the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with an idle mode DRX page wakeup for the second RAT.
The method of claim 17, wherein the one or more collisions are based on a first DRX wakeup for the first RAT overlapping in time with a connected mode DRX page wakeup for the second RAT.
The method of claim 17, wherein the one or more collisions are based on a DRX mode being unusable due to a connected mode for the first subscription for the first RAT and the second subscription for the second RAT.
An apparatus for wireless communication, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receive, from the UE, timing information associated with discontinuous reception (DRX) based on the first RAT, the timing information being based on one or more collisions between the DRX based for the first RAT and UE operation based on a second subscription for a second RAT; and

adjust a DRX configuration for the UE based on the timing information.
The apparatus of claim 29, the at least one processor being further configured to:

configure a new DRX configuration for the UE based on the timing information.