Methods and apparatus for multitasking and intelligent location selection for cdrx

Abstract

Apparatuses, methods, and computer-readable media are disclosed herein for facilitating multitasking and intelligent position selection during connected mode discontinuous reception (CDRX) mode. Example techniques disclosed herein enable a UE to perform multiple tasks during the same SSBS to reduce the number of wake-up SSBSs. For example, the disclosed techniques enable a UE to perform an RLM task and a loop tracking task during a first SSBS, thereby reducing the number of wake-up SSBSs. In some examples, the UE can also perform a search task or a measurement task during the same first SSBS, thereby further reducing the number of wake-up SSBSs. Example techniques disclosed herein can also enable a UE to select for which SSBS events to wake up during an off duration of a CDRX cycle.

Description

[0001] This application is a divisional application of the granted invention patent filed on August 19, 2020, with application number 202080059000.2 and invention title "Method and apparatus for multitasking and intelligent location selection for CDRX".

[0002] Claiming priority

[0003] This application claims the benefit and priority of U.S. Patent Application No. 16 / 556,091, filed on August 29, 2019, entitled “METHODS AND APPARATUS TOFACILITATE MULTI-TASKING AND SMART LOCATION SELECTION DURING CONNECTED-MODEDISCONTINUOUS RECEPTION MODE”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0004] In summary, this disclosure relates to communication systems, and more specifically, to wireless communications including discontinuous reception modes. Background Technology

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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.

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G / NR is part of a continuous evolution of mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., in conjunction with the Internet of Things (IoT),) and others. 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 can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G / NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0007] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict 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 descriptions that follow.

[0008] Sometimes, a User Equipment (UE) can operate according to a Connectivity Mode Discontinuous Receive (CDRX) cycle to conserve power. When operating according to a CDRX cycle, the UE can wake up and actively communicate with network devices (such as a base station) during the on duration of the CDRX cycle. The UE can then enter a sleep state during the off duration of the CDRX cycle. When the UE operates during the off duration, the UE's primary modem can operate at a lower power level or be turned off, and the UE's loops (e.g., Automatic Gain Control (AGC) loop, Time Tracking (TTL) loop, Frequency Tracking (FTL) loop, Power Delay Profile (PDP) loop, and / or Channel Estimation loop) may lose synchronization.

[0009] Synchronization signals (including Synchronization Signal Blocks (SSBs) and Synchronization Signal Burst Sets (SSBSs)) are reference signals that can be periodically transmitted by the network and received by the UE. In some examples, the UE can use synchronization signals received during the off-duration of a CDRX cycle to perform one or more tasks in preparation for the upcoming on-duration of the CDRX cycle. For example, during an SSBS, the UE can perform Radio Resource Management (RRM) tasks (such as search and / or measurement tasks) to search for any available cellular resources and / or beam resources and / or to measure the quality of any identified resources. The UE can also, alternatively, perform Radio Link Monitoring (RLM) tasks during an SSBS to manage links to any identified resources. The UE can also, alternatively, perform loop tracking tasks during an SSBS to synchronize the UE's loops (e.g., AGC loops, TTL, FTL, PDP loops, and / or channel estimation loops).

[0010] The example techniques disclosed herein enable a UE to perform multiple tasks during the same SSBS, thereby reducing the number of SSBSs that need to be woken up. For example, the disclosed techniques enable a UE to perform an RLM task and a loop tracking task during the first SSBS, thus reducing the number of SSBSs woken up from four to three. In some examples, the UE can also perform a search task or a measurement task during the same first SSBS, further reducing the number of SSBSs woken up from three to two.

[0011] The example techniques disclosed herein also enable the UE to select which SSBS events to wake up for during the off duration of the CDRX cycle. For example, different tasks may have their own time periods, and SSBS events may also have their own time periods. The UE can then determine which SSBS events to wake up for based on a determination of which tasks can be performed during the same SSBS event and different time periods, so that certain tasks (e.g., loop tracking tasks) can be maintained, and that the UE can maintain a relatively long off duration during the CDRX cycle.

[0012] In one aspect of this disclosure, methods, computer-readable media, and apparatus are provided. An example apparatus for wireless communication at a UE selects a first SSBS event during the off duration of a CDRX cycle, during which a loop tracking task and an RLM task are performed. The apparatus determines whether the UE is capable of performing a third task associated with at least one frequency range during the first SSBS event. The apparatus performs the third task associated with the at least one frequency range during the first SSBS event.

[0013] In other or alternative examples of this disclosure, methods, computer-readable media, and apparatus are provided. An example apparatus for wireless communication at a UE determines a first SSBS event received during a time frame corresponding to the start of the on-time duration of a CDRX cycle. The apparatus determines whether the first SSBS event is a shareable SSBS based on whether the UE is able to perform at least a measurement task and a loop tracking task during the first SSBS event. When the first SSBS event is a shareable SSBS, the apparatus performs a measurement task during the first SSBS event; and when the first SSBS event is a non-shareable SSBS, the apparatus performs a measurement task during a second SSBS event, which is different from the first SSBS event.

[0014] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more aspects in detail. However, these features indicate only some of the various ways in which the principles of these aspects may be employed, and this specification is intended to include all such aspects and their equivalents. Attached Figure Description

[0015] Figure 1 This is a schematic diagram illustrating an example of a wireless communication system and access network.

[0016] Figure 2A , Figure 2B , Figure 2C and Figure 2D This is a schematic diagram showing examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe.

[0017] Figure 3 This is a schematic diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0018] Figure 4 An example SS block location mapping is shown in accordance with the teachings disclosed herein.

[0019] Figure 5 This is an example communication flow between a base station and a UE, based on the teachings disclosed herein.

[0020] Figure 6 , Figure 7 and Figure 8 An example scheduling of SSBS events is shown when multitasking is enabled, in accordance with the teachings disclosed herein.

[0021] Figure 9A This shows a timeline of scheduling using the tracking pattern in accordance with the teachings disclosed herein.

[0022] Figure 9B The timeline of the preheating mode scheduling is shown in accordance with the teachings disclosed herein.

[0023] Figure 10 This is another example of a communication flow between a base station and a UE, based on the teachings disclosed herein.

[0024] Figure 11A This shows a timeline of the adoption of options for shareable SSBS in accordance with the teachings disclosed herein.

[0025] Figure 11B This shows a timeline of the adoption of non-shareable SSBS in accordance with the teachings disclosed herein.

[0026] Figure 12A The timeline shows the adoption of the choice of a shareable SSBS and a tracking reference signal (TRS) in accordance with the teachings disclosed herein.

[0027] Figure 12B This document presents a timeline of the adoption of non-shareable SSBS and TRS in accordance with the teachings disclosed herein.

[0028] Figure 13 and Figure 14 This is a flowchart of an example method for wireless communication at the UE based on the teachings disclosed herein.

[0029] Figure 15 This is a conceptual data flow diagram illustrating the data flow between different units / components in the example device.

[0030] Figure 16 This is a schematic diagram illustrating an example of a hardware implementation of a device employing a processing system. Detailed Implementation

[0031] The specific embodiments described below with reference to the accompanying drawings are intended as a description of various configurations and are not intended to represent only the configurations in which the concepts described herein can be practiced. Specific details are included in the specific embodiments for the purpose of providing a full understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0032] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and shown in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “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 on the specific application and the design constraints imposed on the system as a whole.

[0033] By way of example, an element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including 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, system-on-a-chip (SoCs), 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 functions described herein. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

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

[0035] As used herein, the term computer-readable medium is explicitly defined to include any type of computer-readable storage device and / or storage disk, excluding propagation signals and transmission media. As used herein, “computer-readable medium,” “machine-readable medium,” “computer-readable memory,” and “machine-readable storage” are used interchangeably.

[0036] Figure 1 This is a schematic diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes base station 102, UE 104, evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0037] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected to EPC 160 via backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G / NR (collectively referred to as Next Generation RAN (NG-RAN)) can be connected to core network 190 via backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and delivery of warning messages. Base stations 102 can communicate directly or indirectly (e.g., via EPC 160 or core network 190) through backhaul link 134 (e.g., X2 interface). Backhaul link 134 can be wired or wireless.

[0038] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for its respective geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be via one or more carriers. Base station 102 / UE 104 may use spectrum allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction, with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetrical with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0039] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0040] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0041] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve coverage of the access network and / or increase the capacity of the access network.

[0042] Base station 102 (whether it is a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in the conventional sub-6GHz spectrum, in millimeter wave (mmW) frequencies, and / or near-mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near-mmW frequencies, gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is a portion of the RF spectrum in the electromagnetic spectrum. EHF has a range of 30GHz to 300GHz and wavelengths between 1mm and 10mm. Radio waves in this band may be referred to as millimeter waves. Near-mmW can extend down to a frequency of 3GHz with a wavelength of 100mm. Ultra-high frequency (SHF) bands extend between 3GHz and 30GHz and are also referred to as centimeter waves. Communication using mmW / near mmW radio frequency bands (e.g., 3 GHz - 300 GHz) has extremely high path loss and short range. mmW base station 180 can utilize beamforming 182 with UE 104 to compensate for the extremely high path loss and short range.

[0043] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions for base station 180 may be the same or different. The transmit and receive directions for UE 104 may be the same or different.

[0044] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides IP address allocation and other functions to the UE. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for MBMS transmissions to content providers, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to base stations 102 belonging to areas of a Multicast-Broadcast Single Frequency Network (MBSFN) that broadcasts specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0045] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that processes signaling between UE 104 and core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services.

[0046] A base station may also be referred to as a gNB, Node B, Evolved Node B (eNB), access point, base transceiver, wireless base station, wireless transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radio units, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.

[0047] Refer again Figure 1 In some respects, UE 104 can be configured to manage one or more aspects of wireless communication during CDRX via multiplexing and intelligent location selection of reference signals. As an example, in Figure 1In this configuration, UE104 may include CDRX component 198, which is configured to select a first SSBS event during the off duration of the CDRX cycle, during which a loop tracking task and an RLM task are performed. CDRX component 198 may also be configured to determine whether the UE is able to perform a third task associated with at least one frequency range during the first SSBS event, and whether the third task associated with said at least one frequency range can be performed during the first SSBS event.

[0048] In additional or alternative examples, CDRX component 198 may be configured to determine a first SSBS event received during a time frame corresponding to the start of the CDRX cycle's open duration. CDRX component 198 may also be configured to determine whether the first SSBS event is a shareable SSBS based on whether the UE is able to perform at least a measurement task and a loop tracking task during the first SSBS event. CDRX component 198 may also be configured to perform a measurement task during the first SSBS event when the first SSBS event is a shareable SSBS event, and to perform a measurement task during a second SSBS event, different from the first SSBS event, when the first SSBS event is a non-shareable SSBS event.

[0049] While the following description provides examples of a UE performing tasks “during” an SSBS event, it should be understood that the concepts described herein can be applied to examples where a UE performs its respective tasks “based on” and / or “using” an SSBS event. For example, a UE may perform (and / or complete) a task after an SSBS event, but based on (and / or using) measurements taken during the SSBS event. Furthermore, while the following description provides examples based on 5G / NR, it should be understood that the concepts described herein can be applied to other communication technologies. For example, the concepts described herein can be applied to LTE, LTE-A, CDMA, GSM, and / or other radio technologies (or RATs) in which a UE can operate in DRX mode.

[0050] Figure 2A This is a schematic diagram 200 showing an example of the first subframe within a 5G / NR frame structure. Figure 2B This is a schematic diagram 230 illustrating an example of a DL channel within a 5G / NR subframe. Figure 2C This is a schematic diagram 250 showing an example of a second subframe within a 5G / NR frame structure. Figure 2DThis is a schematic diagram 280 illustrating an example of a UL channel within a 5G / NR subframe. The 5G / NR frame structure can be FDD (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL), or TDD (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). In the case of... Figure 2A , Figure 2C In the provided example, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and X is flexibly used between DL / UL, and subframe 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot format 0 and slot format 1 are full DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via a received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI) or semi-statically / statically via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G / NR frame structures that are TDD.

[0051] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) OFDM (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Spread Spectrum OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe can be based on the time slot configuration and the numbering scheme. For slot configuration 0, different digital schemes μ0 to μ5 consider 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different digital schemes 0 to μ2 consider 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the digital scheme. The subcarrier spacing can be equal to 2. μ * 15 kHz, where μ is the digital scheme from 0 to 5. Accordingly, digital scheme μ = 0 has a subcarrier spacing of 15 kHz, and digital scheme μ = 5 has a subcarrier spacing of 480 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D Examples are provided for slot configuration 0 (with 14 symbols per slot) and digital scheme μ=0 (with 1 slot per subframe). The subcarrier spacing is 15 kHz, and the symbol duration is approximately 66.7 μs.

[0052] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)), which consists of 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried through each RE depends on the modulation scheme.

[0053] As in Figure 2AAs shown, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as Rx for a specific configuration, where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0054] Figure 2B Examples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in an OFDM symbol. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH) carrying the Primary Information Block (MIB) may logically be grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) that are not transmitted via the PBCH, and paging messages.

[0055] As in Figure 2C As shown, some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the preceding one or two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. Although not shown, the UE can transmit a Sounding Reference Signal (SRS). The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0056] Figure 2DExamples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0057] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides the following associated RRC layer functions: broadcasting system information (e.g., MIB, SIB), 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 functions associated with: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with: transmission of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), and MAC... SDU performs demultiplexing of TB, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0058] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection of the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially precoded to produce multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimate can be derived based on reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318TX. Each transmitter 318TX can use its respective spatial stream to modulate an RF carrier for transmission.

[0059] At UE 350, each receiver 354RX receives signals via its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements Layer 3 and Layer 2 functions.

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

[0061] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides RRC layer functions associated with: system information (e.g., MIB, SIB) acquisition, RRC connection and measurement reporting; PDCP layer functions associated with: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with: transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functions associated with: mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing and logical channel prioritization.

[0062] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use its own spatial stream to modulate the RF carrier for transmission.

[0063] UL transmission is handled at base station 310 in a manner similar to that described for the receiver functions incorporated at UE 350. Each receiver 318RX receives signals via its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0064] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel 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 ACK and / or NACK protocols to support HARQ operation.

[0065] At least one of the TX processor 368, RX processor 356, and controller / processor 359 of UE 350 can be configured to perform operations related to... Figure 1 Various aspects related to the CDRX component 198.

[0066] Sometimes, the UE can operate according to the CDRX cycle to save power. When operating according to the CDRX cycle, the UE can wake up and actively communicate with network devices (such as base stations) during the on duration of the CDRX cycle. Then, the UE can enter a sleep state during the off duration of the CDRX cycle. When the UE operates during the off duration, the UE's primary modem can operate at a lower power level or be turned off, and the UE's loops (e.g., AGC loop, TTL, FTL, PDP loop, and / or channel estimation loop) may lose synchronization.

[0067] Synchronization signals (including SSB and SSBS) are reference signals that can be periodically transmitted by the network and received by the UE. In some examples, the UE can use synchronization signals received during the off-duration of a CDRX cycle to perform one or more tasks in preparation for the upcoming on-duration of the CDRX cycle. For example, the UE can perform RRM (such as search and / or measurement tasks) during SSBS to search for any available cellular resources and / or beam resources and / or to measure the quality of any identified resources. The UE can also perform RLM tasks during SSBS to manage links to any identified resources. The UE can also perform loop tracking tasks during SSBS to synchronize the UE's loops (e.g., AGC loop, TTL, FTL, PDP loop, and / or channel estimation loop).

[0068] In some examples, certain information may be useful for certain tasks within a task. For example, search and / or measurement tasks may use SSBS resources within a Synchronization Signal-Based Measurement Timing Configuration (SMTC) window. In some examples, the SMTC window duration may be, for example, 1 ms, 2 ms, etc. In some examples, the SMTC periodicity may range from 5 ms to 160 ms. In some examples, the SMTC window timing offset may range from 0 ms to the SMTC periodicity minus one. Typically, the SMTC periodicity may be longer than the SSBS duration. For example, the SSBS periodicity may be 20 ms, and the SMTC periodicity may be 40 ms.

[0069] Figure 4 Example SS block location mapping 400 is shown. Example SS block location mapping 400 shows a 20ms example window and demonstrates that SSBS events can last for 0.5ms (e.g., two SSBS events occur within a 1ms timeframe). Example SS block location mapping 400 shows two example mapping options based on different frequency bands. Figure 4 In the illustrated example, each mapping option shows that an SSBS event can include 14 different SSBs (e.g., ranging from 0 to 13). For example, Figure 4 Each SSBS includes multiple SSBs, and each SSB corresponds to a different UE beam.

[0070] It should be understood that in some examples, the UE can be woken up for different SSBS events to perform different tasks within a task. However, multiple wake-ups for SSBS events can increase power consumption at the UE, especially when the UE is operating in CDRX mode. Furthermore, it should be understood that the timing of SSBS wake-ups (e.g., when an SSB is received) can be used to increase power savings when operating in CDRX mode. For example, SSBS events can be periodic so that multiple SSBS events can occur during the off duration. In some such examples, the UE can select certain SSBS events for wake-up to increase the time between wake-up SSBS events. The increased time between wake-up SSBS events helps improve power efficiency at the UE.

[0071] The example techniques disclosed herein enable a UE to perform multiple tasks during the same SSBS, thereby reducing the number of SSBSs that need to be woken up. For example, aspects may enable the UE to perform an RLM task and a loop tracking task during a single SSBS. Using a single SSBS for the RLM and loop tracking tasks allows the UE to reduce the number of SSBSs woken up from four to three. In some examples, the UE may also perform a search or measurement task during the same SSBS, further reducing the number of SSBSs woken up from three to two.

[0072] The example techniques disclosed herein also enable a UE to select the SSBS event for wake-up during the off duration of a CDRX cycle. For example, different tasks can have their own time periods, and SSBS events can also have their own time periods. The UE can determine the specific SSBS event to wake up for its UE based on a determination of which tasks can be performed during the same SSBS event and different time periods. SSBS events can be selected such that some tasks (e.g., loop tracking tasks) can be maintained, and that the UE can maintain a relatively long off duration.

[0073] Figure 5 An example of wireless communication 500 between base station 502 and UE 504 as given herein is shown. One or more aspects of base station 502 may be provided by Figure 1 Base stations 102 / 180 and / or Figure 3 This is achieved through base station 310. One or more aspects of UE 504 can be implemented by... Figure 1 UE 104 and / or Figure 3 This is achieved using UE 350.

[0074] It should be understood that while wireless communication 500 includes a base station 502 communicating with a UE 504, in additional or alternative examples, base station 502 may communicate with any suitable number of UEs 504 and / or base station 502, and / or UE 504 may communicate with any suitable number of base stations 502 and / or UE 504. Furthermore, while wireless communication 500 includes an example SSBS transmission 560, it should be understood that in additional or alternative examples, wireless communication 500 may include multiple SSBS transmissions that can be periodically sent from base station 502 to UE 504 and / or other UEs.

[0075] exist Figure 5In the illustrated example, base station 502 may send periodic scheduling 510 to UE 504. Periodic scheduling 510 may configure UE 504 to perform one or more tasks based on one or more time periods. For example, periodic scheduling 510 may configure UE 504 to perform a search task every eight CDRX cycles, to perform a measurement task every eight CDRX cycles, to perform a loop tracking task every 160ms, and to perform an RLM task every 320ms. Base station 502 may send periodic scheduling 510 via Master Information Block (MIB), System Information Block (SIB), RRC signaling, Downlink Control Information (DCI) signaling, and / or Media Access Control-Control Element (MAC-CE).

[0076] At 520, UE 504 can determine the number of wake-up SSBS events that facilitate the execution of different tasks during its operation based on at least one frequency range and periodic scheduling. As described above, in some examples, UE 504 may be able to execute multiple tasks during the same SSBS event to reduce the number of wake-up SSBS events when operating in CDRX mode. In some examples, the different tasks can be multitasking based on, for example, frequency range. For example, when UE 504 is operating in the sub-6 GHz frequency range (FR1), UE 504 may not perform beam scheduling. Accordingly, when UE 504 is operating in FR1, UE 504 can determine to execute a search task, a loop tracking task, and an RLM task during the same SSBS event. In other examples, UE 504 can determine to execute a measurement task, a loop tracking task, and an RLM task during the same SSBS event.

[0077] In other examples, UE 504 can operate in the millimeter-wave (mmW) frequency range (FR2) and can perform UE beam scheduling. In some examples, when UE 504 is operating in FR2, different tasks within a task can use different information to perform their respective tasks. For example, when UE 504 is performing a search task, the UE beam can be selected in a round-robin manner. For example, if UE 504 can access eight different beams, UE 504 can select the first UE beam for performing the first search task, select the next UE beam for performing the second search task, and so on. Therefore, when performing a search task, 504 can perform a search to identify any cell resources and / or beam resources available to the UE, and thus UE 504 can utilize any SSBS, because each SSBS contains different SSBs (and corresponding UE beams) (such as combined...). Figure 4 (As shown).

[0078] When UE 504 is performing a measurement task, the UE beam can be selected per SSB rather than per SSBS. As described above, each SSB corresponds to its own UE beam and the quality of the resources identified to facilitate the measurement task. Therefore, for each beam for which UE 504 wants to measure its quality, UE 504 can get one opportunity for that beam.

[0079] When UE 504 is performing a loop tracking task, the UE beam can be selected with respect to the serving beam. For example, the loop tracking task facilitates the synchronization of AGC loops, TTL loops, FTL loops, PDP loops, and / or channel estimation loops. Therefore, to facilitate the execution of the loop tracking task, UE 504 can measure characteristics associated with the serving beam.

[0080] When UE 504 is performing an RLM task, the UE beam can be selected with respect to a virtual serving beam. It should be understood that the virtual serving beam can overlap with the serving beam. Therefore, to facilitate the execution of the RLM task, UE 504 can measure characteristics associated with the serving beam.

[0081] Based on the different parameters associated with performing different tasks (e.g., search task, measurement task, loop tracking task, and RLM task), some tasks can be performed during the same SSBS when UE 504 is operating in FR2. For example, UE 504 can perform both the loop tracking task and the RLM task during the same SSBS event. Furthermore, because performing the search task facilitates the search for any available cell resources and / or beam resources, in some examples, the execution of the search task may not be shared with other tasks when UE 504 is operating in FR2.

[0082] In some examples, UE 504 may also be able to perform measurement tasks along with loop tracking and RLM tasks while operating in FR2. However, since measurement tasks facilitate the measurement of resource quality, it may be beneficial for the corresponding beam to meet certain thresholds. For example, UE 504 can measure the signal-to-interference and noise ratio (SINR) associated with the widest serving beam and compare the measured SINR to a measurement threshold (e.g., a SINR threshold). In some examples, when the measured SINR meets the SINR threshold, UE 504 can determine that the serving beam can be used to perform the measurement task, and therefore, the serving beam can be used to perform the measurement task, loop tracking task, and RLM task.

[0083] However, when the measured SINR does not meet the SINR threshold, UE 504 can determine to enable beam refinement mode to further refine the beam for performing measurement tasks. In some such examples, UE 504 can perform measurement tasks as well as loop tracking and RLM tasks during separate SSBS events. For example, UE 504 can determine to perform measurement tasks during SSBS events, and can perform loop tracking and RLM tasks during different SSBS events.

[0084] Therefore, when operating in FR2, UE 504 can perform different tasks (e.g., search task, measurement task, loop tracking task, and RLM task) during two or three SSBS events based on whether beam refinement mode is enabled or disabled. For example, when beam refinement mode is not enabled (e.g., the measured SINR meets the SINR threshold), UE 504 can perform the measurement task, loop tracking task, and RLM task during the first SSBS event, and the search task during the second SSBS event. In other examples where beam refinement mode is enabled (e.g., the measured SINR does not meet the SINR threshold), UE 504 can perform the measurement task during the first SSBS event, the loop tracking task and RLM task during the second SSBS event, and the search task during the third SSBS event.

[0085] Although the above disclosure describes determining the number of wake-up SSBS events at point 520 based on whether the UE is operating in FR1 or FR2, which may differ depending on the execution of different tasks during that period, it should be understood that in other examples, the UE may utilize different techniques to determine the number of wake-up SSBS events. For example, the above disclosure describes that when the UE is operating in FR1, the UE may not perform beam scheduling, and when the UE is operating in FR2, the UE may perform beam scheduling. However, it should be understood that in other or alternative examples, the UE may perform beam scheduling when operating in FR1 and / or the UE may not perform beam scheduling when operating in FR2. In some such examples, it should be understood that the disclosed techniques are not limited to a specific frequency range associated with beam scheduling being performed or not performed. For example, the determination of the number of wake-up SSBS events for the execution of different tasks during that period may be based on whether the UE is performing beam scheduling.

[0086] At 530, UE 504 can select the location to wake up the SSBS event in order to increase the sleep between SSBS event wake-up events.

[0087] Once UE 504 determines at 520 how many SSBS events might be needed to perform different tasks, UE 504 can then select different wake-up SSBS events at 530 to increase the sleep between wake-up SSBS events (e.g., to increase the duration of UE 504's sleep state). For example, UE 504 can select certain SSBS events for improved loop tracking and / or to increase the duration of the sleep state. For example, UE 504 can select SSBS events within a time frame at the beginning of the on-duration period during the off-duration period (e.g., the SSBS event closest to the beginning of the on-duration period during the off-duration period can be selected). In some such examples, UE 504 can perform at least the loop tracking task and the RLM task during the selected SSBS events. In some examples, when UE 504 is operating in FR1, UE 504 can also perform a search task or a measurement task during the selected SSBS events. In some examples, when UE 504 is operating in FR2, UE 504 can perform measurement tasks during a selected SSBS event, for example, when beam refinement mode is not enabled.

[0088] Then, UE 504 can transition between the on and off states based on the selected location of the CDRX cycle and the wake-up SSBS event. For example, UE 504 can transition to the off state at 540 to save power during the off duration of the CDRX cycle. At 550, UE 504 can transition from the off state to the on state based on the selected location of the wake-up SSBS event. It should be understood that in some examples, UE 504 can remain in the off state while other SSBS events can occur during the off duration of the CDRX cycle. For example, based on the SSBS periodicity and the duration of the CDRX cycle, one or more SSBS events can occur during the off duration that UE 504 discards (e.g., without transitioning to the on state for reception).

[0089] Then, UE 504 can receive a scheduled wake-up SSBS transmission 560 while in the enabled state. UE 504 can then perform one or more tasks at 570 based on the wake-up SSBS transmission 560. For example, when operating in FR1, UE 504 can perform a search task, a loop tracing task, and an RLM task, or it can perform a measurement task, a loop tracing task, and an RLM task. In other examples, when operating in FR2, UE 504 can perform a search task, a loop tracing task, an RLM task, and / or a measurement task.

[0090] In some examples, at 580, UE 504 can then return to the off state at 540. In some such examples, UE 504 can transition to the off state based on the location of the next wake-up SSBS event.

[0091] Figure 6 An example schedule 600 for SSBS events is shown when multitasking is enabled. In the illustrated example, schedule 600 corresponds to the UE operating in FR1. In the illustrated example, the UE can be configured (e.g., based on...) Figure 5 The periodic scheduling (510) involves performing a search task every eight CDRX cycles, a measurement task every eight CDRX cycles, a loop tracking task every 160ms, and an RLM task every 320ms. It should be understood that in some examples, the UE may utilize the execution of the search task in place of the execution of the measurement task. For example, performing a search task facilitates the search for cell resources and / or beam resources available to the UE. In some such examples, the UE may also perform a measurement task as part of the search task to measure the quality of any identified cell resources and / or beam resources. Therefore, in some examples, when the UE performs a search task, if, for example, the periodicity of the search task and the measurement task is satisfied based on the performed search task, the UE may substitute for the subsequent execution of the measurement task.

[0092] exist Figure 6 In the illustrated example, the CDRX cycle has a duration of 160 ms, and the SSBS periodicity is 40 ms. Accordingly, each CDRX cycle of example schedule 600 includes four SSBS events. Furthermore, as described above, the UE can discard (or ignore) certain SSBS events. Thus, example schedule 600 illustrates a wake-up SSBS event 605 (e.g., an SSBS event that wakes the UE from its off duration) and other SSBS events 610 (e.g., SSBS events ignored by the UE).

[0093] exist Figure 6 In the example described, the UE is operating in FR1. Accordingly, during the same SSBS event, the UE can perform one of (1) a loop tracking task, (2) an RLM task, and (3) a search task or a measurement task. In addition, to improve the performance of the loop tracking task, the UE can select the SSBS event that is closest to the start of the on duration during the off duration.

[0094] For example, in Figure 6In the described scheduling 600, the UE selects a first wake-up SSBS event 605a during which it performs the search task, loop tracking task, and RLM task. As shown in the illustrated example, the first wake-up SSBS event 605a is the closest SSBS event that occurs during the off duration and before the start of the on duration 620a. The UE's execution of the search task can substitute for the execution of the measurement task. Based on the periodicity of the configuration of the search and measurement tasks, the UE may not execute the search and measurement tasks until the eighth subsequent CDRX cycle.

[0095] Furthermore, since the UE is configured to perform a loop tracking task every 160ms in the illustrated example, the UE performs a first loop tracking task during a first wake-up SSBS event 605a, a second wake-up SSBS event 605b during which a second loop tracking task is selected to be performed, and a third wake-up SSBS event 605c during which a third loop tracking task is selected to be performed. As shown in the illustrated example, the second wake-up SSBS event 605b is the closest SSBS event during the off duration and before the start of the on duration 620b. Similarly, the third wake-up SSBS event 605c is the closest SSBS event during the off duration and before the start of the on duration 620c.

[0096] Furthermore, due to the UE in Figure 6 In the example described, the UE is configured to perform an RLM task every 320ms, therefore the UE performs a first RLM task during the first wake-up SSBS event 605a, and a third wake-up SSBS event 605c during which a second RLM task is selected to be performed. Figure 6 As illustrated in the schedule 600, the third wake-up SSBS event 605c occurs 320ms after the first wake-up SSBS event 605a.

[0097] Therefore, as in Figure 6As illustrated in the example, by multitasking certain tasks within a task during the same SSBS event, the number of SSBS events allocated to perform different tasks can be reduced. For example, instead of waking up for six different SSBS events to perform different tasks (e.g., three loop tracking tasks, two RLM tasks, and one search task), example scheduling 600 enables the UE to select three wake-up SSBS events 605 during which six different tasks are performed (e.g., by performing the first loop tracking task, the first RLM task, and the search task during the first wake-up SSBS event 605a, by performing the second loop tracking task during the second wake-up SSBS event 605b, and by performing the third loop tracking task and the second RLM task during the third wake-up SSBS event 605c).

[0098] Figure 7 and Figure 8 Example schedules 700 and 800 for SSBS events when multitasking is enabled are shown respectively. In the illustrated examples, schedules 700 and 800 correspond to UE operation in FR2. Similar to... Figure 6 Example dispatch 600, the UE can be configured (e.g., based on) Figure 5 The periodic scheduling (510) executes a search task every eight CDRX cycles, a measurement task every eight CDRX cycles, a loop tracing task every 160ms, and an RLM task every 320ms.

[0099] exist Figure 7 and Figure 8 In the illustrated examples, the CDRX cycle has a duration of 80 ms, and the SSBS periodicity is 20 ms. Therefore, each CDRX cycle of example schedules 700 and 800 includes four SSBS events. Furthermore, as described above, the UE can discard (or ignore) certain SSBS events. Thus, example schedules 700 and 800 illustrate wake-up SSBS events 705 and 805 (e.g., SSBS events that wake the UE from its off duration) and other SSBS events 710 and 810 (e.g., SSBS events ignored by the UE).

[0100] exist Figure 7 and Figure 8In the illustrated example, the UE is operating in FR2. Accordingly, the UE may not perform a search task and another task during the same SSBS event (e.g., an SSBS event during which the UE performs a search task may not be multitasked with another task within the same task). Therefore, the UE may perform a search task during a first SSBS event, and may perform a loop tracking task and an RLM task during a second SSBS event, which is different from the first SSBS event. In some examples, the UE may also perform a measurement task during the second SSBS event. For example, the UE may compare the measured SINR of its widest serving beam with a SINR threshold to determine whether beamfinding mode is enabled. In some such examples, when beamfinding mode is enabled, the UE may perform a measurement task during a third SSBS event. In other examples where beamfinding mode is not enabled (or disabled), the UE may perform a measurement task during the second SSBS event (e.g., the UE may perform a measurement task, a loop tracking task, and an RLM task during the second SSBS event). In addition, to improve the performance of the loop tracking task, and regardless of whether beam refinement mode is enabled, the UE can choose to perform the loop tracking task (and RLM task) during the SSBS event received during the off duration that is closest to the start of the on duration.

[0101] For example, in Figure 7 In the described scheduling 700, the UE determines that beam refinement mode is not enabled, and therefore, the UE can select a first wake-up SSBS event 705a to perform measurement tasks, loop tracking tasks, and RLM tasks during its duration. As shown in the illustrated example, the first wake-up SSBS event 705a is an SSBS event received during the off duration and closest to the start of the on duration 720b and preceding the start of the on duration 720b.

[0102] Furthermore, the UE can select the second wake-up SSBS event 705b as the first SSBS event to occur after the start of the on-duration 720b. Therefore, as... Figure 7 As illustrated in the example, the UE can be woken up (or transitioned to the on state) in response to the first wake-up SSBS event 705a, the on duration 720b, and the second wake-up SSBS event 705b, while remaining in the off state and ignoring the events described. Figure 7 The two shown examples are the remaining SSBS events 710 that occurred during the CDRX cycle.

[0103] refer to Figure 8In the illustrated scheduling 800, the UE determines to enable beam refinement mode, and therefore, the UE can select a first wake-up SSBS event 805a for scheduling and executing loop tracking and RLM tasks (e.g., the UE does not perform measurement tasks during the first wake-up SSBS event 805a). As shown in the illustrated example, the first wake-up SSBS event 805a is an SSBS event received during the off duration and closest to the start of the on duration 820b and preceding the start of the on duration 820b.

[0104] Furthermore, the UE can select a second wake-up SSBS event 805b, which corresponds to the first SSBS event to occur after the start of the on-duration duration 820b. The UE can also select a third wake-up SSBS event 805c, which corresponds to the next SSBS event to occur after the second wake-up SSBS event 805b. Therefore, as in Figure 8 As illustrated in the example, the UE can be woken up (or transition to the on state) in response to the first wake-up SSBS event 805a, the on duration 820b, the second wake-up SSBS event 805b, and the third wake-up SSBS event 805c, while remaining in the off state and ignoring the events described. Figure 8 The remaining SSBS events 810 that occur during the CDRX cycle of the two descriptions.

[0105] Therefore, as shown in example scheduling 700, 800, by selecting the respective wake-up SSBS events, the UE may be able to benefit from a relatively long sleep state and further power savings during the CDRX cycle. Furthermore, by selecting the position of the SSBS event relatively close to the start of the on duration, during which at least the loop tracking task is performed (e.g., during the off duration and within a time frame prior to the start of the on duration), the UE may be able to improve the performance of the loop tracking task by improving the quality of the respective estimates and / or measurements associated with the execution of the loop tracking task. For example, due to Figure 7 and Figure 8 The first wake-up SSBS events 705a and 805a are closest to the start of their respective on-duration periods, so any measurements and / or estimates associated with performing the tracking task when the UE transitions to the on state during the on-duration period can be considered "latest" or most recent.

[0106] While the above description discloses techniques for facilitating multitasking and intelligent location selection of SSBS for tasks with different off-duty durations (e.g., search tasks, measurement tasks, loop tracing tasks, and RLM tasks) during the CDRX cycle, the following description discloses additional or alternative scheduling techniques related to loop tracing tasks.

[0107] As described above, CDRX mode allows the UE to turn off one or more components (such as the receiver) during certain time periods (e.g., during the off duration of a CDRX cycle) because the UE does not expect to receive any communication. Although the UE may not receive any communication during the off duration, it still expects to maintain some information and connection with the network. For example, the UE can be configured to periodically perform cell search and measurement tasks (e.g., searching for any cell resources available to the UE and measuring the quality of such resources), beam search and measurement tasks (e.g., searching for any beam resources available to the UE and measuring the quality of such resources), and loop tracking tasks (sometimes called "synchronization loops") (e.g., synchronization of AGC loops, TTL, FTL, PDP loops, and / or channel estimation loops). The execution of the loop tracking task enables the UE to synchronize with the network when it transitions from an off state to an on state, for example, during the on duration of a CDRX cycle.

[0108] The example techniques disclosed herein enable the UE to perform a loop tracking task before the start of the open duration, thus preparing the UE to connect at the start of the open duration.

[0109] As described above, a synchronization signal is a reference signal that can be periodically sent by the network and received by the UE. In some examples, the UE can use the synchronization signal received during the off duration of a CDRX cycle to perform one or more tasks in preparation for the upcoming on duration of the CDRX cycle. Furthermore, the network can send a synchronization signal regardless of whether any particular UE is in an on state or waiting for a synchronization signal.

[0110] In some examples, the network may also transmit Tracking Reference Signal (TRS) transmissions to the UE. In some such examples, the TRS transmission may have a different periodicity and / or location than the SSBS transmission. In some examples, the location of the TRS event may be positioned closer to the start of the on-duration than the location of the SSBS event. For example, the TRS event may be located within a first time frame before the start of the on-duration, while the SSBS event may be located within a second time frame before the start of the on-duration and beyond the first time frame. In some examples, the TRS event may be located closer to the start of the on-duration than the location of the SSBS event.

[0111] In some examples, the UE can perform search and measurement tasks as well as loop tracking tasks during SSBS transmissions. Conversely, the UE can perform loop tracking tasks during TRS transmissions (e.g., search and measurement tasks may not be performed during TRS transmissions).

[0112] Figure 9A Example timeline 900 is shown, illustrating the use of tracking mode scheduling for scheduling loop tracking tasks. Figure 9A In the illustrated example, the UE is configured with a predetermined scheduling period for performing the loop tracking task. For example, timeline 900 includes a CDRX loop with an 80ms period and a predetermined scheduling period of 160ms for performing the loop tracking task.

[0113] However, it should be understood that increasing the duration of the CDRX cycle can provide improved power savings to the UE. For example, some networks can configure the CDRX cycle to 320ms or 640ms. In some examples, increasing the duration of the CDRX cycle may lead to an increased likelihood of the UE losing synchronization with the network. For instance, if the UE is moving during the off duration of the CDRX cycle, the longer duration of the CDRX cycle may cause the UE to lose connection with cell resources and / or beam resources when the UE does transition to the on state during the on duration of the CDRX cycle.

[0114] Therefore, in some examples, the UE can determine the expected sleep duration during the CDRX cycle and whether the expected sleep duration exceeds the warm-up limit. In some such examples, if the expected sleep duration exceeds the warm-up limit, the UE can switch to warm-up mode and select an SSBS event within a time frame preceding the next warm-up duration, during which search and measurement tasks and loop tracking tasks are performed. It should be understood that the execution of search and measurement tasks can correspond to performing a search task (as described above) to identify any cell resources and / or beam resources available to the UE, and performing a measurement task (as described above) to measure the quality of any such identified resources.

[0115] Figure 9B Example timeline 950 is shown, illustrating the use of preheating mode scheduling for scheduling loop tracing tasks. Figure 9B In the illustrated example, the UE is configured with a CDRX cycle having a duration of 320 ms and a preheating limit of 160 ms. The UE can determine that no selected wake-up event exists during the off duration of the CDRX cycle, and therefore, the expected sleep duration of 320 ms is greater than the preheating limit of 160 ms. In some such examples, the UE can transition to a preheating mode and select a wake-up SSBS event 960 prior to the start of the on duration 970. In the illustrated example, the UE can perform search and measurement tasks and loop tracking tasks (e.g., execution of AGC loops, TTL, FTL, PDP loops, and / or channel estimation loops) during the wake-up SSBS event 960.

[0116] Figure 10 Another example of wireless communication 1000 between base station 1002 and UE 1004 is shown, as given herein. One or more aspects of base station 1002 may be provided by Figure 1 Base station 102 / 180 Figure 3 Base station 310 and / or Figure 5 This is achieved through base station 502. One or more aspects of UE 504 can be implemented by... Figure 1 UE 104 Figure 3 UE 350 and / or Figure 5 This is achieved using UE 504.

[0117] It should be understood that although wireless communication 1000 includes a base station 1002 communicating with a UE 1004, in additional or alternative examples, base station 1002 may communicate with any appropriate number of UEs 1004 and / or base station 1002, and / or UE 1004 may communicate with any appropriate number of base stations 1002 and / or UE 1004. Furthermore, although wireless communication 1000 includes an example SSBS or TRS transmission 1060, it should be understood that in additional or alternative examples, wireless communication 1000 may include multiple SSBS and / or TRS transmissions that may be periodically transmitted from base station 1002 to UE 1004 and / or other UEs.

[0118] exist Figure 10 In the illustrated example, base station 1002 may send periodic scheduling 1010 to UE 1004. Periodic scheduling 1010 may configure UE 1004 to perform one or more tasks based on one or more time periods. Furthermore, periodic scheduling 1010 may indicate to UE 1004 the CDRX duration and SSBS periodicity. In some examples, periodic scheduling 1010 may also indicate to UE 1004 whether TRS transmissions are available for UE 1004 and / or TRS periodicity. Base station 1002 may send periodic scheduling 1010 via MIB, via SIB, via RRC signaling, via DCI signaling, and / or via MAC-CE.

[0119] At 1020, UE 1004 can determine whether an SSBS event is a shareable SSBS event. As described above, in some examples, UE 1004 can determine that a selected SSBS event for which a loop tracing task is performed during its period is an SSBS event that can also be used to perform search and measurement tasks (e.g., an SSBS event that is a shareable SSBS event for which both loop tracing and search and measurement tasks can be performed during its period). For example, reducing the number of SSBS events that UE 1004 can wake up for may be beneficial, and therefore identifying shareable SSBS events may be beneficial for UE 1004.

[0120] In some examples, to determine whether an SSBS event is a shareable SSBS event, UE 1004 may determine whether the signal used to perform a loop tracking task can also be used to perform search and measurement tasks. For example, in some examples, UE 1004 may be performing search and measurement tasks related to the serving beam and / or cell resources. In some such examples, UE 1004 may be able to use the serving beam and / or cell resources to perform both search and measurement tasks and loop tracking tasks, and therefore, the UE can determine that the corresponding SSBS event is a shareable SSBS event.

[0121] In other examples, UE 1004 may be performing search and measurement tasks related to, for example, neighboring cell resources rather than the serving cell. In some such examples, performing a loop tracing task based on neighboring cell resources may not produce useful estimates and / or measurements for maintaining synchronization with the serving cell. Therefore, in some such examples, when the search and measurement task is related to neighboring cell resources, UE 1004 may determine that the selected SSBS event during which the loop tracing task is performed is not a shareable SSBS event (e.g., the UE may also not perform the search and measurement task during the selected SSBS event). In some such examples, UE 1004 may determine a first SSBS event during which the loop tracing task is performed, and may determine a second SSBS event during which the search and measurement task is performed.

[0122] In some examples, whether an SSBS event is a shareable SSBS event can be based on whether UE 1004 is able to perform a loop tracing task within a predetermined coherent time from a previous execution of the loop tracing task. For example, there may be a threshold buffer duration after the completion of the search and measurement task and the loop tracing task, before the UE is able to perform decoding of downlink transmissions (e.g., PDCCH) received during the on-duration period. In some such examples, if UE 1004 determines that the threshold buffer duration may not be met (e.g., the interval between the completion of the search and measurement task and the loop tracing task and the start of decoding of the downlink transmission is no greater than the threshold buffer duration), UE 1004 can determine that the SSBS event is not a shareable SSBS event (e.g., the SSBS event is a non-shareable SSBS event).

[0123] At 1030, UE 1004 can determine whether a TRS event is available to UE 1004. In some examples, a TRS event can provide UE 1004 with relatively up-to-date information compared to an SSBS event, and therefore, it may be beneficial for UE 1004 to select a TRS event during which a loop tracing task is performed and an SSBS event during which a search and measurement task is performed.

[0124] For example, as described above, in some examples, a TRS event can be located relatively closer to the start of the on-time duration compared to an SSBS event, and therefore, a TRS event can provide relatively "updated" or more recent information for performing a loop tracing task compared to an SSBS event. In some such examples, UE 1004 can determine that scheduling the execution of the loop tracing task during a TRS event may be more beneficial.

[0125] At 1040, UE 1004 can determine the wake-up schedule. For example, UE 1004 can determine the wake-up schedule based on whether the SSBS event is a shareable SSBS event and whether the TRS event is available to UE 1004. It should be understood that the wake-up schedule can correspond to the scheduling of selected SSBS events and / or selected TRS events for the UE to wake up during its period to perform one or more tasks.

[0126] In some examples, when UE 1004 determines that an SSBS event is a shareable SSBS event, UE 1004 can select a shareable SSBS event and perform search and measurement tasks and loop tracking tasks during the shareable SSBS event.

[0127] In some examples, when UE 1004 determines that an SSBS event is a non-shareable SSBS event, UE 1004 may choose to perform a first SSBS event during which a loop tracing task is performed, and may choose to perform a second SSBS event during which a search and measurement task is performed.

[0128] In some examples, when UE 1004 determines that a TRS event is available to UE 1004, UE 1004 may also determine whether performing a loop tracing task during a TRS event can provide additional power savings compared to performing a loop tracing task during, for example, a shareable SSBS event or multiple SSBS events (e.g., when the SSBS event selected for the execution of the loop tracing task is a non-shareable event).

[0129] For example, when UE 1004 determines that the SSBS event selected for performing the loop tracing task is a non-shareable SSBS event, UE 1004 can determine whether the TRS event is positioned relatively closer to the start of the on-duration period compared to the SSBS event. In some such examples, when UE 1004 determines that the TRS event is positioned relatively closer to the start of the SSBS event, UE 1004 can select the TRS event and perform the loop tracing task during the TRS event. UE 1004 can then select the SSBS event during which the search and measurement tasks are performed. In other examples where UE 1004 determines that the SSBS event is positioned relatively closer to the start of the on-duration period compared to the TRS event, UE 1004 can select a first SSBS event (e.g., the selected SSBS event) during which the loop tracing task is performed, and a second SSBS event during which the search and measurement tasks are performed.

[0130] In some examples where UE 1004 determines that the SSBS event selected for execution of the loop tracing task is a shareable SSBS event and that the TRS event is available, UE 1004 may choose to select the TRS event for execution of the loop tracing task when selecting the TRS event saves more power than selecting the shareable SSBS event. For example, UE 1004 may determine a first duration (D_pre) based on the start of the shareable SSBS event and the start of the TRS event. UE 1004 may also determine a second duration (D_after) based on the end of the on-time duration and the end of the SSBS event following the start of the on-time duration. UE 1004 may then compare the first duration (D_pre) with the second duration (D_after), and if the first duration (D_pre) is greater than the second duration (D_after), determine that selecting the TRS event for execution of the loop tracing task provides power savings.

[0131] In some examples, after determining whether to perform the loop tracing task and search and measurement task during a shared SSBS event, TRS event, and SSBS event or during two SSBS events, UE 1004 can also determine the location of the selected SSBS and / or TRS event.

[0132] For example, in order to schedule and execute loop tracking tasks, UE 1004 can select either an SSBS event or a TRS event that is located during the off duration and at the beginning of the duration closest to the upcoming on duration.

[0133] When selecting SSBS events for scheduling and executing search and measurement tasks, UE 1004 can select shareable SSBS events when, for example, TRS events are unavailable or TRS events are available but do not provide power savings.

[0134] In some examples, UE 1004 can select an SSBS event following the start of the on duration for scheduling and executing search and measurement tasks. In some examples, the start of the selected SSBS event may overlap with the on duration. In some examples, the start of the selected SSBS event may follow the end of the on duration (e.g., there may be an interval between the end of the on duration and the start of the selected SSBS event). In some such examples, UE 1004 can cancel (or skip) the transition from the on state to the off state during the interval.

[0135] It should be understood that UE 1004 can select SSBS events following the start of the on duration for scheduling and executing search and measurement tasks to increase power savings. For example, consider an example where the CDRX duration is 80 ms, the on duration is 10 ms, and the SSBS periodicity is 20 ms (e.g., four SSBS events occur during the 80 ms interval). In some such examples, during a 100 ms interval, UE 1004 can be woken up for a first SSBS event during which a loop tracing task is performed, transition to the on state within 10 ms of the on duration, remain off for the second and third SSBS events, be woken up for a fourth SSBS event during which a search and measurement task is performed, and then be woken up for a fifth SSBS event during which a loop tracing task is performed before the next on duration.

[0136] In contrast, in the illustrated example, when UE 1004 selects an SSBS event occurring after the start of the on duration for scheduling and executing search and measurement tasks, UE 1004 can be woken up for a first SSBS event during which a loop-tracking task is performed, transition to the on state within 10ms of the on duration, wake up for a second SSBS event during which a search and measurement task is performed, and then remain in the off state for the third through fifth SSBS events. Furthermore, in the above example, because the 20ms interval between the first and second SSBS events is interrupted by the transition to the on state within 10ms of the on duration, the total duration for which UE 1004 remains in the off state during the example CDRX cycle is increased, thus providing UE 1004 with increased power savings compared to locating the SSBS event used for executing the search and measurement task before the SSBS event selected for executing the loop-tracking task.

[0137] At 1050, UE 1004 can then transition between the on and off states based on the wake-up schedule determined at 1040. For example, UE 1004 can transition to the off state during the off duration of the CDRX cycle to save power. UE 1004 can then wake up before the occurrence of a selected SSBS or TRS transmission 1060 and based on the wake-up schedule. It should be understood that in some examples, UE 1004 can remain in the off state, while other SSBS events and / or TRS events can be transmitted by base station 1002 during the off duration of the CDRX cycle.

[0138] Then, UE 1004 can receive scheduled SSBS or TRS transmissions 1060 in the enabled state. UE 1004 can then perform one or more tasks at 1070 based on the SSBS or TRS transmission 1060. For example, for a shared SSBS event, UE 1004 can perform a search and measurement task as well as a loop tracing task. In other examples, UE 1004 can perform a loop tracing task for an SSBS event or for a TRS event, and can perform a search and measurement task for (different) SSBS events.

[0139] It should be understood that in some examples, UE 1004 can return to 1050 to continue transitioning between the on and off states based on wake-up scheduling.

[0140] Figure 11A Example timeline 1100 shows the adoption of a shareable SSBS selection. For example, the UE can select SSBS event 1110 for scheduling and executing search and measurement tasks as well as loop tracking tasks. Figure 11A In the illustrated example, SSBS event 1110 is selected as an SSBS event within the time frame at the start of the on-duration 1120 (e.g., within 10 ms of the start of the on-duration 1120). For example, SSBS event 1110 can be positioned as the closest SSBS event during the off-duration of the CDRX cycle and before the start of the on-duration 1120. By selecting an SSBS event within the time frame at the start of the on-duration 1120, the UE may be able to improve the quality of estimation and / or measurement through the execution of loop tracking tasks.

[0141] Figure 11B Example timeline 1150 shows an example of using a non-shareable SSBS. For example, the UE can determine that the execution of search and measurement tasks and the execution of loop tracking tasks may not be scheduled during the same SSBS event. Figure 11B In the illustrated example, the UE can select a first SSBS event 1160a to schedule and execute a loop tracking task, and can select a second SSBS event 1160b to schedule and execute a search and measurement task. Similar to... Figure 11A Example timeline 1100, Figure 11B The UE can select a first SSBS event 1160 used for scheduling and executing loop tracking tasks as the SSBS event within the time frame at the start of the on duration 1170 (e.g., the closest SSBS event during the off duration and before the start of the on duration 1170). The UE can select a second SSBS event 1160b corresponding to an SSBS event after the start of the on duration 1170. In some examples, the start of the second SSBS event 1160b may overlap with the on duration 1170.

[0142] Figure 12A Example timeline 1200 shows the selection of a shareable SSBS when TRS is available. For example, the UE can determine that the execution of search and measurement tasks and the execution of loop tracking tasks can be scheduled during the same SSBS event. Figure 12A In the example described, the UE can also determine that the TRS event is available and therefore can be selected for scheduling and execution of the loop tracking task.

[0143] For example, in the timeline 1200 illustrated in Figure 12, the UE can identify a first SSBS event 1210a located within the time frame at the beginning of the on-duration 1220 and a second SSBS event 1210b located after the beginning of the on-duration 1220. The UE can also determine that the TRS event 1230 is available for the UE to perform a loop tracking task.

[0144] In some examples, to determine whether to select TRS event 1230 for scheduling and executing the loop tracking task, the UE can determine whether a first duration (D_pre) between the start of the first SSBS event 1210a and the start of TRS event 1230 is greater than a second duration (D_after) between the end of the on-time duration 1220 and the end of the second SSBS event 1210b. In some such examples, when the first duration (D_pre) is greater than the second duration (D_after), the UE can select TRS event 1230 for scheduling and executing the loop tracking task. The UE can then select the second SSBS event 1210 for scheduling and executing the search and measurement task. Although Figure 12A The second SSBS event 1210 is located after the start of the on-duration 1220, but it should be understood that in other examples, the second SSBS event 1210 can be located anywhere after the TRS event 1230.

[0145] It should be understood that in other examples where the first duration (D_pre) is no greater than the second duration (D_after), the UE can determine to select the first SSBS event 1210a for scheduling and execution of the search and measurement tasks and the loop tracking tasks (as described above). Figure 11A Example timeline 1100 is described.

[0146] Figure 12B Example timeline 1250 shows the selection of a non-shareable SSBS when TRS is available. For example, the UE can determine that the execution of search and measurement tasks and the execution of loop tracking tasks may not be performed during the same SSBS event. Figure 12B In the example described, the UE can also determine that the TRS event is available and therefore can be selected for scheduling and execution of the loop tracking task.

[0147] exist Figure 12B In the example timeline 1250 described, the UE can identify a first SSBS event 1260a located within the time frame at the beginning of the on-duration 1270 and a second SSBS event 1260b located after the beginning of the on-duration 1270. The UE can also determine that the TRS event 1280 is available for the UE to perform a loop tracking task.

[0148] In the illustrated example, when the UE determines that the selection of the non-shareable SSBS event and the TRS event are available, the UE can then compare the positions of the first SSBS event 1260a and the TRS event 1280 relative to the start of the on-duration 1270. For example, as Figure 12B As shown, compared to the first SSBS event 1260a, the TRS event 1280 is positioned closer to the start of the on-duration 1270. Since the UE determines to select a non-shareable SSBS event, the UE can select the TRS event 1280 for scheduling and executing loop tracking tasks, and can select the second SSBS event 1260b for scheduling and executing search and measurement tasks. In some examples, the start of the second SSBS event 1260b may overlap with the on-duration 1270. Although Figure 12B The second SSBS event 1260b is located after the start of the on-duration 1270, but it should be understood that in other examples, the second SSBS event 1260b can be located anywhere after the TRS event 1280.

[0149] It should be understood that in other examples, the first SSBS event may be located closer to the start of the on-time duration compared to the TRS event. In some such examples, the UE can select the first SSBS event for scheduling and executing loop tracking tasks, and can select the second SSBS event for scheduling and executing search and measurement tasks (as described above). Figure 11B (As described in example timeline 1150). Therefore, it should be understood that after determining to utilize non-shareable SSBS events, the UE can select the "updator" in the TRS event and the first SSBS event for scheduling and executing the loop tracking task.

[0150] In some examples, when the UE selects an SSBS event after the start of the on duration for scheduling and executing search and measurement tasks, as described above, in conjunction with... Figure 11B , Figure 12A and Figure 12B As shown in the example timelines at 1150, 1200, and 1250, the UE can determine whether to skip transitioning to the off state during the period between the end of the on duration and the start of the second SSBS event.

[0151] It should be understood that while the above examples describe a single SSBS event and / or a single TRS event preceding the start of the on-time duration for scheduling and executing one or more tasks, in other examples, any appropriate number of SSBS events and / or TRS events (e.g., two events, three events, etc.) may be selected for scheduling and executing one or more tasks. For example, in some examples, the UE may select multiple SSBS events preceding the start of the on-time duration for scheduling and executing one or more tasks.

[0152] Figure 13 This is a flowchart 1300 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, UE 350, UE 504, UE 1004, device 1502 / 1502', and / or processing system 1614, which may include memory 360 and may be the entire UE 350 or components of UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). Optional aspects are illustrated using dashed lines. This method can improve the power efficiency of a UE operating in CDRX mode by reducing the number of wake-up SSBS events and / or by increasing the duration during which the UE is in a powered-off state.

[0153] At 1302, the UE can select a first SSBS event during the off duration of the CDRX cycle, during which the loop tracking task and RLM task are performed. For example, the SSBS event selection component 1508 of device 1502 can facilitate the selection of a first SSBS event during which the loop tracking task and RLM task are performed. In some examples, the first SSBS event may be located within the first time frame at the beginning of the on duration of the CDRX cycle.

[0154] At 1304, the UE can determine whether it is capable of performing a third task associated with at least one frequency range during the first SSBS event. For example, capability determination component 1510 can facilitate the determination of whether the UE is capable of performing a third task during the first SSBS event. In some examples, whether the UE can perform a third task during the first SSBS event may depend on whether the UE is operating in the sub-6 GHz frequency range (FR1) or the millimeter-wave frequency range (FR2). In some examples, whether the UE can perform a third task during the first SSBS event may depend on whether the UE is performing beam scheduling.

[0155] If the UE determines at 1304 that it is operating in FR1, then at 1306 the UE can determine that it is capable of performing a third task during the first SSBS event. For example, when the UE is operating in FR1, the capability determination component 1510 can facilitate the determination that the UE is capable of performing a third task during the first SSBS event.

[0156] At 1308, the UE can select a second SSBS event to perform the fourth task during its period. For example, SSBS event selection component 1508 can facilitate the selection of a second SSBS event to perform the fourth task during its period.

[0157] At 1310, the UE may perform a third task during the first SSBS event. For example, task execution component 1512 may facilitate the execution of the third task during the first SSBS event. In some examples, the third task may be one of a measurement task or a search task, and the fourth task may be another of a measurement task or a search task.

[0158] If the UE determines at 1304 that it is operating in FR2, then at 1312 the UE can perform a measurement associated with the serving beam. For example, measurement processing component 1514 can facilitate the execution of the measurement associated with the serving beam. In some examples, the measurement may be a SINR measurement associated with the serving beam. In some examples, the serving beam may be the widest beam serving the UE (e.g., transmitted on the widest frequency range beam serving the UE).

[0159] At 1314, the UE can determine whether the measurement meets the measurement threshold. For example, the measurement processing component 1514 can facilitate the determination of whether the measurement meets the measurement threshold.

[0160] If the UE determines at 1314 that the measurement does not meet the measurement threshold, the UE can enable beamfinding mode at 1316. For example, the measurement processing component 1514 can facilitate the enabling of beamfinding mode. Control can then proceed to 1320 to determine whether the UE is able to perform a third task during the first SSBS event.

[0161] If the UE determines at 1314 that the measurement meets the measurement threshold, the UE can disable the beamfinding mode at 1318. For example, the measurement processing component 1514 can facilitate the disabling of the beamfinding mode. Control can then proceed to 1320 to determine whether the UE can perform a third task during the first SSBS event.

[0162] At 1320, when the UE is operating in FR2, the UE can determine whether it is capable of performing a third task during the first SSBS event. For example, when the UE is operating in FR2, the capability determination component 1510 can facilitate the determination of whether the UE is capable of performing a third task during the first SSBS event. In some examples, the UE can determine whether it is capable of performing a third task during the first SSBS event based on a determination regarding the disabling of beam refinement mode. In some examples, the UE can determine whether it is incapable of performing a third task during the first SSBS event based on a determination regarding the enabling of beam refinement mode.

[0163] If the UE determines at 1320 that it is capable of performing a third task during the first SSBS event, then at 1322 the UE may perform the third task during the first SSBS event. For example, task execution component 1512 may facilitate the execution of the third task during the first SSBS event. It should be understood that the UE may also perform loop tracking and RLM tasks during the first SSBS event.

[0164] At 1324, the UE can perform a search task during the second SSBS event. For example, task execution component 1512 can facilitate the execution of the search task during the second SSBS event. In some examples, the second SSBS event may be located at the first SSBS event after the start of the open duration.

[0165] If the UE determines at 1320 that it cannot perform the third task during the first SSBS event, then at 1326 the UE can perform the loop tracking task and the RLM task during the first SSBS event. For example, the task execution component 1512 can facilitate the execution of the loop tracking task and the RLM task during the first SSBS event.

[0166] At 1328, the UE can perform a search task during the second SSBS event. For example, task execution component 1512 can facilitate the execution of the search task during the second SSBS event. In some examples, the second SSBS event can be located at the first SSBS event after the start of the open duration.

[0167] At 1330, the UE can perform a measurement task during the third SSBS event. For example, task execution component 1512 can facilitate the execution of the measurement task during the third SSBS event. In some examples, the second SSBS event can be located at the first SSBS event after the start of the activation duration. In some examples, the third SSBS event can be located after the second SSBS event.

[0168] Figure 14This is a flowchart 1400 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, UE 350, UE 504, UE 1004, device 1502 / 1502', and / or processing system 1614, which may include memory 360 and may be the entire UE 350 or components of UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). Optional aspects are illustrated using dashed lines. This method can improve the power efficiency of a UE operating in CDRX mode by identifying shareable SSBS events and thus reducing the number of wake-up SSBS events and / or by increasing the duration during which the UE is in a powered-off state.

[0169] At 1402, the UE can determine the first SSBS event received during a time frame corresponding to the start of the on-time duration of the CDRX cycle. For example, the SSBS event selection component 1508 of device 1502 can facilitate the determination of the first SSBS event located within a time frame at the start of the on-time duration of the CDRX cycle.

[0170] At 1404, the UE can determine whether the first SSBS event is a shareable SSBS based on whether at least the measurement task and the loop tracking task can be performed during the first SSBS event. For example, the shareable processing component 1516 can facilitate the determination of whether the first SSBS event is a shareable SSBS.

[0171] If the UE determines at 1404 that the first SSBS event is a shareable SSBS, then at 1406 the UE can determine whether a TRS event can be selected for the execution of the loop tracking task. For example, the TRS processing component 1518 can facilitate the determination of whether a TRS event can be selected for the execution of the loop tracking task. In some examples, when the TRS event is positioned closer to the start of the on-duration period relative to the first SSBS event, the UE can determine that the TRS event can be selected for the execution of the loop tracking task.

[0172] If the UE determines at 1406 that the TRS event is not available (or no available TRS event exists), then at 1408 the UE can perform a loop tracking task during the first SSBS event. For example, task execution component 1512 can facilitate the execution of the loop tracking task during the first SSBS event.

[0173] At 1410, the UE can perform a measurement task during the first SSBS event. For example, the task execution component 1512 can facilitate the execution of the measurement task during the first SSBS event.

[0174] If the UE determines at 1406 that the TRS event is optional (e.g., for the execution of a loop tracing task), then at 1412 the UE can execute the loop tracing task during the TRS event. For example, task execution component 1512 can facilitate the execution of the loop tracing task during the TRS event.

[0175] At 1414, the UE can perform a measurement task during the first SSBS event. For example, the task execution component 1512 can facilitate the execution of the measurement task during the first SSBS event.

[0176] If the UE determines at 1404 that the first SSBS event is a non-shareable SSBS, then at 1416 the UE can determine whether a TRS event can be selected for the execution of the loop tracking task. For example, the TRS processing component 1518 can facilitate this determination. In some examples, when the TRS event is positioned closer to the start of the on-duration period relative to the first SSBS event, the UE can determine that the TRS event can be selected for the execution of the loop tracking task.

[0177] If the UE determines at 1416 that the TRS event is unselectable (or that no TRS event is available), then at 1418 the UE can perform a loop tracing task during the first SSBS event. For example, task execution component 1512 can facilitate the execution of the loop tracing task during the first SSBS event.

[0178] At 1420, the UE can perform a measurement task during the second SSBS event. For example, task execution component 1512 can facilitate the execution of the measurement task during the second SSBS event. In some examples, the second SSBS event may occur after the start of the on-time duration of the CDRX cycle.

[0179] If the UE determines at 1416 that the TRS event is optional (e.g., for the execution of a loop tracing task), then at 1422 the UE can execute the loop tracing task during the TRS event. For example, task execution component 1512 can facilitate the execution of the loop tracing task during the TRS event.

[0180] At 1424, the UE can perform a measurement task during the second SSBS event. For example, task execution component 1512 can facilitate the execution of the measurement task during the second SSBS event. In some examples, the second SSBS event may occur after the TRS event.

[0181] Figure 15This is a conceptual data flow diagram 1500 illustrating the data flow between different units / components in an example device 1502 communicating with base station 1550. Device 1502 may be a UE. Device 1502 may execute the methods of flowcharts 1300 and / or 1400. Device 1502 includes a receiving component 1504, a transmitting component 1506, an SSBS event selection component 1508, a capability determination component 1510, a task execution component 1512, a measurement processing component 1514, a shareable processing component 1516, and a TRS processing component 1518.

[0182] The receiving component 1504 can be configured to receive various types of signals / messages and / or other information from other devices, including the base station 1550. Messages / information may be received via the receiving component 1504 and provided to one or more components of the device 1502 for further processing and use in performing various operations. For example, the receiving component 1504 can be configured to receive signaling including receiving periodic scheduling, SSBS events, and / or TRS events.

[0183] The transmitting component 1506 can be configured to transmit uplink transmissions to, for example, a base station 1550.

[0184] The SSBS event selection component 1508 can be configured to select a first SSBS event that performs a loop tracking task and an RLM task during the off duration of the CDRX cycle, select a second SSBS event that performs a fourth task during the off duration, and / or determine a first SSBS event received during a time frame corresponding to the start of the on duration of the UE's CDRX cycle (e.g., as described in conjunction with 1302, 1308 and / or 1402).

[0185] Capability determination component 1510 can be configured to determine whether the UE is able to perform a third task during the first SSBS event (e.g., as described in conjunction with 1304, 1306 and / or 1320).

[0186] The task execution component 1512 can be configured to perform a third task during a first SSBS event, a search task during a second SSBS event, a loop tracing task and an RLM task during a first SSBS event, a measurement task during a third SSBS event, a loop tracing task during a first SSBS event, a measurement task during a first SSBS event, a loop tracing task during a TRS event, and / or a measurement task during a second SSBS event (e.g., as described in conjunction with 1310, 1320, 1324, 1326, 1328, 1330, 1408, 1410, 1412, 1414, 1418, 1420, 1422 and / or 1424).

[0187] Measurement processing component 1514 can be configured to perform measurements associated with the serving beam, determine whether the measurement meets a measurement threshold, enable beam refinement mode and / or disable beam refinement mode (e.g., as described in conjunction with 1312, 1314, 1316 and / or 1318).

[0188] The shareable processing component 1516 can be configured to determine whether the first SSBS event is a shareable SSBS based on whether at least a measurement task and a loop tracing task can be performed during the first SSBS event (e.g., as described in conjunction with 1404).

[0189] TRS processing component 1518 can be configured to determine whether a TRS event is selectable for the execution of a loop tracing task (e.g., as described in conjunction with 1406 and / or 1416).

[0190] The device may include the functions described above. Figure 13 and / or Figure 14 The flowchart shows the algorithm's additional components in each box. Accordingly, in the above... Figure 13 and / or Figure 14 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of those components. A component can be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0191] Figure 16 This is a schematic diagram 1600 illustrating an example of a hardware implementation of a device 1502' employing a processing system 1614. The processing system 1614 may be implemented using a bus architecture typically represented by a bus 1624. Depending on the specific application and overall design constraints of the processing system 1614, the bus 1624 may include any number of interconnect buses and bridges. The bus 1624 links various circuits together, including one or more processors and / or hardware components represented by processors 1604, components 1504, 1506, 1508, 1510, 1512, 1514, 1516, 1518, and computer-readable medium / memory 1606. The bus 1624 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0192] Processing system 1614 may be coupled to transceiver 1610. Transceiver 1610 is coupled to one or more antennas 1620. Transceiver 1610 provides a means for communicating with various other devices over a transmission medium. Transceiver 1610 receives signals from one or more antennas 1620, extracts information from the received signals, and provides the extracted information to processing system 1614 (specifically, receiving component 1504). Furthermore, transceiver 1610 receives information from processing system 1614 (specifically, transmitting component 1506) and generates signals to be applied to one or more antennas 1620 based on the received information. Processing system 1614 includes processor 1604 coupled to computer-readable medium / memory 1606. Processor 1604 is responsible for general processing, including the execution of software stored on computer-readable medium / memory 1606. When executed by processor 1604, the software causes processing system 1614 to perform the various functions described above for any particular device. The computer-readable medium / memory 1606 can also be used to store data manipulated by the processor 1604 when executing software. The processing system 1614 also includes at least one of components 1504, 1506, 1508, 1510, 1512, 1514, 1516, and 1518. These components may be software components running in the processor 1604 and located / stored in the computer-readable medium / memory 1606, one or more hardware components coupled to the processor 1604, or some combination thereof. The processing system 1614 may be a component of the UE 350 and may include memory 360 and / or at least one of the following: TX processor 368, RX processor 356, and / or controller / processor 359. Alternatively, the processing system 1614 may be the entire UE (e.g., see...). Figure 3 (UE 350).

[0193] In one configuration, the means 1502 / 1502' for wireless communication may include: a unit for selecting a first SSBS event during the off duration of a CDRX cycle, during which a loop tracking task and an RLM task are performed. The means may include: a unit for determining whether the UE is able to perform a third task associated with at least one frequency range during the first SSBS event. The means may include: a unit for performing the third task associated with said at least one frequency range during the first SSBS event. The means may include: a unit for selecting a second SSBS event during which a fourth task is performed. The means may include: a unit for performing measurements associated with a serving beam. The means may include: a unit for enabling a beam refinement mode when the measurement meets a measurement threshold. The means may include: a unit for disabling the beam refinement mode when the measurement does not meet a measurement threshold. The means may include: a unit for determining whether the UE is able to perform the third task during the first SSBS event when the beam refinement mode is disabled. The means may include: a unit for performing a search task during the second SSBS event. The apparatus may include units for performing a loop tracking task and an RLM task during a first SSBS event after determining that the UE is unable to perform a third task during the first SSBS event. The apparatus may include units for performing a search task during a second SSBS event. The apparatus may include units for performing a measurement task during a third SSBS event received after the second SSBS event. The apparatus may include units for determining a first SSBS event received during a time frame corresponding to the start of the CDRX cycle's open duration. The apparatus may include units for determining whether the first SSBS event is a shareable SSBS based on whether the UE is able to perform at least a measurement task and a loop tracking task during the first SSBS event. The apparatus may include units for performing a measurement task during the first SSBS event when the first SSBS event is a shareable SSBS. The apparatus may include units for performing a measurement task during a second SSBS event, different from the first SSBS event, when the first SSBS event is a non-shareable SSBS. The apparatus may include units for performing a loop tracing task during a first SSBS event when the first SSBS event is a shareable SSBS, wherein the first SSBS event is the last SSBS event received before the start of the open duration of the CDRX loop. The apparatus may also include units for performing a loop tracing task during a first SSBS event when the first SSBS event is a non-shareable SSBS, wherein the first SSBS event is the last SSBS event received before the start of the open duration of the CDRX loop, and wherein a second SSBS event is received after the start of the open duration of the CDRX loop.The apparatus may include a unit for determining whether the UE is capable of performing a loop tracking task during a TRS event, based on whether the TRS event is received between the start of the CDRX cycle's open duration and the start of the CDRX cycle's closed duration. The apparatus may also include a unit for performing a loop tracking task during a TRS event when the TRS event is available.

[0194] The aforementioned unit may be one or more of the aforementioned components of device 1502 and / or the processing system 1614 of device 1502' configured to perform the functions described through the aforementioned unit. As described above, the processing system 1614 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Accordingly, in one configuration, the aforementioned unit may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions described through the aforementioned unit.

[0195] The example techniques disclosed herein facilitate reducing the number of times a UE operating in CDRX mode can be woken up to receive a reference signal (such as an SSBS), thereby enabling the UE to improve power efficiency when operating in CDRX mode. Furthermore, the example techniques disclosed herein facilitate intelligent location selection of the received reference signal, thereby enabling the UE to increase the off-duty duration during CDRX cycles, and thus reduce power consumption when operating in CDRX mode.

[0196] It is to be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the example method. Based on design preferences, it is to be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of each box in the order shown, but are not intended to limit one to the given specific order or hierarchy.

[0197] The foregoing description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein references to singular elements are not intended to mean “one and only one,” but rather “one or more,” unless expressly stated otherwise. The word “exemplary” as used herein means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred over or superior to other aspects. Unless expressly stated otherwise, the term “some” refers to one or more. For example, 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" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements described throughout the various aspects of this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. The terms "module", "mechanism", "element", "device", etc., may not be a substitute for the term "unit". Accordingly, no claim element is to be interpreted as a functional module unless the element is expressly stated using the phrase "unit for...".

Claims

1. A method for wireless communication at a user equipment (UE), comprising: Select a first synchronization signal burst set SSBS event during which a plurality of first tasks associated with at least one frequency range are performed, wherein the first SSBS event occurs during the off-duration period of a discontinuous reception DRX cycle; and The plurality of first tasks are performed during the first SSBS event.

2. The method according to claim 1, wherein, The DRX cycle is a Connected Mode Discontinuous Receive (CDRX) cycle.

3. The method according to claim 1, wherein, The plurality of first tasks includes two or more of the following: Radio Link Monitoring (RLM) task; Search task; Loop tracking task; or Measurement task.

4. The method according to claim 1, further comprising: Select a second SSBS event during which a second task associated with at least the frequency range is performed, wherein the second SSBS event is different from the first SSBS event; and The second task is performed during the second SSBS event.

5. The method according to claim 4, wherein, The plurality of first tasks performed during the first SSBS event include a loop tracking task and a radio link monitoring (RLM) task, and the second tasks performed during the second SSBS event include a search task or a measurement task.

6. The method according to claim 1, wherein, The frequency range includes the sub-6 GHz frequency range (FR1).

7. The method according to claim 1, wherein, The frequency range includes the millimeter wave frequency range (FR2), and the method further includes: Perform measurements associated with the serving beam; When the measurement meets the measurement threshold, the beam refinement mode is activated; and When the measurement does not meet the measurement threshold, the beam refinement mode is disabled.

8. The method according to claim 7, further comprising: When the beam refinement mode is disabled, it is determined that the UE is able to perform the plurality of first tasks during the first SSBS event.

9. The method according to claim 7, wherein, The service beam is transmitted on the widest frequency range beam serving the UE.

10. The method according to claim 1, wherein, The first SSBS event is received before the start of the on duration of the DRX cycle, and the method further includes: A second task associated with at least the frequency range is performed during a tracking reference signal TRS event, wherein the TRS event is received before the start of the on-duration of the DRX cycle.

11. The method according to claim 10, wherein, The TRS event is closer to the on-duration of the DRX cycle than the SSBS event.

12. The method according to claim 10, wherein, The plurality of first tasks include a measurement task and a search task, and wherein the second task includes a loop tracking task.

13. The method of claim 10, further comprising: Determine whether the TRS event is located between the start of the first SSBS event and the start of the on duration of the DRX cycle; as well as The second task is performed during the TRS event based on the determination that the TRS event occurs between the start of the first SSBS event and the start duration of the DRX cycle.

14. A method for wireless communication at a user equipment (UE), comprising: Determine the first set of SSBS events received before the start of the on-duration of the discontinuous reception DRX cycle; Execute the first task during the first SSBS event; A second SSBS event is determined, which is received before the start of the on-duration of the DRX cycle and after the first SSBS event; as well as The second task is performed during the second SSBS event.

15. The method according to claim 14, wherein, The DRX cycle is a Connected Mode Discontinuous Receive (CDRX) cycle.

16. The method of claim 14, wherein, The first task includes a search task, and the second task includes a measurement task.

17. The method of claim 14, wherein, The first task includes one or more of the following: radio link monitoring (RLM) task, loop tracing task, measurement task, or search task.

18. The method according to claim 14, wherein, The second task includes one or more of the following: radio link monitoring (RLM) task, loop tracing task, measurement task, or search task.

19. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as One or more processors coupled to the memory, the one or more processors being configured individually or collectively to cause the device to perform the method according to any one of claims 1-13.

20. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as One or more processors coupled to the memory, the one or more processors being configured individually or collectively to cause the device to perform the method according to any one of claims 14-18.

Images