Measurement and scheduling of intra-frequency and inter-frequency reference signals

Abstract

Aspects relate to measuring and scheduling reference signals. A user equipment (UE) detects a reference signal having overlapping resources and determines a context associated with the reference signal. Layer 1 (L1) measurements of at least one reference signal are then performed according to a priority ranking associated with the context. In another aspect, a network entity determines a resource schedule that enables a UE to preferentially perform L1 measurements of reference signals from a non-serving cell, and communicates with the UE according to the schedule. In yet another aspect, the UE communicates with the gNb using a transmit configuration indication (TCI) state associated with a corresponding pool of a control resource set (CORESET). A beam fault detection (BFD) reference signal is then explicitly identified via configuration signaling, or implicitly identified based on the TCI state. The BFD reference signal is then monitored to facilitate detecting a beam fault event.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority and the benefit of U.S. Provisional Patent Application No. 63 / 423,026, filed on November 6, 2022, and U.S. Non - Provisional Patent Application No. 18 / 494,531, filed on October 25, 2023, the entire contents of which are hereby incorporated by reference. Technical Field

[0003] The techniques discussed below generally relate to wireless communication and, more specifically, to the measurement and scheduling of intra - frequency and inter - frequency reference signals. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single - Carrier Frequency Division Multiple Access (SC - FDMA) systems, and Time Division - Synchronous Code Division Multiple Access (TD - SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with Enhanced Mobile Broadband (eMBB), Massive Machine - Type Communication (mMTC), and Ultra - Reliable Low - Latency Communication (URLLC). Some aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Summary of the Invention

[0006] The following presents a summary of one or more aspects of the present disclosure to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all contemplated features of the present disclosure and is neither intended to identify key or important elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a prelude to the more detailed description that is presented later.

[0007] According to a first example, a user equipment (UE) is disclosed that includes a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor is configured to detect a first reference signal and a second reference signal, where the first reference signal has resources overlapping with the second reference signal, and where at least one of the first reference signal or the second reference signal is from a non-serving cell. The processor is further configured to: determine a context associated with at least one of the first reference signal or the second reference signal; and perform a layer 1 (L1) measurement of at least one of the first reference signal or the second reference signal according to a priority ranking associated with the context.

[0008] In other examples, a method for wireless communication in a UE is disclosed. The method includes detecting a first reference signal and a second reference signal, where the first reference signal has resources overlapping with the second reference signal, and where at least one of the first reference signal or the second reference signal is from a non-serving cell. The method further includes: determining a context associated with at least one of the first reference signal or the second reference signal; and performing an L1 measurement of at least one of the first reference signal or the second reference signal according to a priority ranking associated with the context.

[0009] Another example provides a network entity configured for wireless communication. The network entity includes a memory and a processor coupled to the memory. The processor is configured to determine a scheduling associated with a resource configuration, where the resource configuration enables the UE to preferentially perform an L1 measurement of a reference signal from a non-serving cell. The processor is further configured to communicate with the UE according to the scheduling.

[0010] According to yet another example, a UE is disclosed that includes a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor is configured to communicate with a gNodeB (gNb) using one or more transmission configuration indication (TCI) states, where each of the one or more TCI states is associated with a corresponding CORESET pool of one or more control resource sets (CORESETs), and where each CORESET pool corresponds to a transmit receive point (TRP). The processor is further configured to identify one or more sets of beam failure detection (BFD) reference signals, where the one or more sets of BFD reference signals are explicitly identified via configuration signaling from the gNb or implicitly identified based on one or more TCI states in the absence of configuration signaling. The processor is further configured to monitor the one or more sets of BFD reference signals to facilitate detection of a beam failure event.

[0011] After studying the following detailed embodiments, these and other aspects of the present disclosure will be more fully understood. After studying the following description of specific examples of the present disclosure in conjunction with the accompanying drawings, other aspects, features, and examples of the present disclosure will be apparent to those of ordinary skill in the art. Although the features of the present disclosure may be discussed below with respect to certain examples and the accompanying drawings, all examples of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various examples of the present disclosure discussed herein. In a similar manner, although the examples may be discussed below as examples of devices, systems, or methods, it should be understood that such examples may be implemented in a variety of devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system including an access network.

[0013] Figure 2A is a diagram illustrating an example of a first frame.

[0014] Figure 2B is a diagram illustrating an example of DL channels within a subframe.

[0015] Figure 2C is a diagram illustrating an example of a second frame.

[0016] Figure 2D is a diagram illustrating an example of a subframe.

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

[0018] Figure 4 is a diagram illustrating an example of a decomposed base station architecture.

[0019] Figure 5 is a diagram illustrating an example of a layer 1 or layer 2 (L1 / L2) mobility scenario for a primary cell (PCell).

[0020] Figure 6 is a diagram illustrating an example of an L1 / L2 mobility scenario for a secondary cell (SCell) handover.

[0021] Figure 7 is a diagram illustrating an example of an L1 / L2 mobility scenario for a cell group (CG).

[0022] Figure 8Is a diagram illustrating the transmission of synchronization signal blocks (SSBs) or channel state information (CSI) reference signals (RSs) for both intra-frequency measurement and inter-frequency measurement.

[0023] Figure 9 Is a diagram illustrating an example of a configuration message for configuring L1 measurement.

[0024] Figure 10 Is a message diagram illustrating various messages for performing L1 measurement.

[0025] Figure 11 Is a conceptual data flow diagram illustrating the data flow between different components / elements in an example base station.

[0026] Figure 12 Is a conceptual data flow diagram illustrating the data flow between different components / elements in an example user equipment (UE).

[0027] Figure 13 Is a block diagram illustrating an example of the hardware implementation of a user equipment (UE) employing a processing system according to some aspects.

[0028] Figure 14 Is a flowchart illustrating a first example of a method for communication in a UE according to some aspects.

[0029] Figure 15 Is a flowchart illustrating a second example of a method for communication in a UE according to some aspects.

[0030] Figure 16 Is a block diagram illustrating an example of the hardware implementation of a network entity (such as a base station) employing a processing system according to some aspects.

[0031] Figure 17 Is a flowchart illustrating a method for communication in a network entity according to some aspects. Detailed Description

[0032] For the purpose of describing the innovative aspects of the present disclosure, the detailed description set forth below relates to certain specific implementations. However, those of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. Some examples in the present disclosure are based on wireless and wired local area network (LAN) communications according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standard, the IEEE 802.3 Ethernet standard, and the IEEE 1901 power line communication (PLC) standard. However, the described specific implementations can be implemented in any device, system, or network capable of transmitting and receiving RF signals according to any one of the following wireless communication standards: including any one of the IEEE 802.11 standards, Standards, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband CDMA (W-CDMA), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE), AMPS, or other known signals for communicating within a wireless network, cellular network, or Internet of Things (IoT) network (such as a system utilizing 3G, 4G, or 5G or further specific implementations thereof).

[0033] Traditionally, in a wireless communication network such as a 5G NR network, mobility procedures are performed at layer 3 (L3) using Radio Resource Control (RRC) signaling. The mobility procedures allow a User Equipment (UE) to move from a source cell to a target cell. The mobility procedures can be based on layer 3 measurements of candidate cells. For example, a UE can be configured to measure candidate cells and send measurement reports in response to various conditions. In some scenarios, when the UE establishes an RRC connection with the target cell, the L3 mobility procedures may involve an interruption or gap in communication. Compared to the L3 mobility procedures, mobility procedures at layer 1 or layer 2 (L1 / L2) offer the possibility of increasing the mobility speed. However, L1 and L2 offer less flexibility in terms of the types and content of messages that can be sent. Additionally, L1 measurements may require different definitions for intra-frequency and inter-frequency measurements in order for the UE to be properly configured and perform L1 measurements.

[0034] The present disclosure provides L1 measurements that can be used in L1 / L2 mobility. Contrary to the L3 configuration of the measurement object or measurement report, the L1 measurements can be configured as channel state information (CSI) reference signal (RS) measurement resources. Although 3GPP TS version 17 may allow the configuration of CSI-RS measurement resources for intra-frequency cells, such measurements are too limited for L1 / L2 mobility. In a particular aspect disclosed herein, the UE detects a first reference signal and a second reference signal having overlapping resources, where at least one of these reference signals is from a non-serving cell, and where the UE performs L1 measurements of at least one of these reference signals according to a context-associated prioritization determined by the UE. In another aspect disclosed herein, a network entity (e.g., gNb) determines a scheduling associated with a resource configuration that enables the UE to preferentially perform L1 measurements of reference signals from non-serving cells. In yet another aspect disclosed herein, the UE is configured to implicitly identify a beam failure detection (BFD) reference signal based on a TCI state without configuration signaling from the network.

[0035] Particular implementations of the subject matter described in this disclosure can be realized to achieve one or more of the following potential advantages. The L1 / L2 mobility procedure can improve the latency of mobility, thereby reducing the interruption of communication during mobility. The use of CSI-RS measurement resources can provide flexibility in measuring both intra-frequency candidate cells and inter-frequency candidate cells in the configuration. L1 / L2 mobility can use less signaling overhead than other mobility procedures.

[0036] Certain aspects of a telecommunications system will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system.

[0037] For example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. The processor can include an interface or can be coupled to an interface that can obtain or output signals. The processor can obtain signals via the interface and output signals via the interface. In some specific implementations, the interface can be a printed circuit board (PCB) transmission line. In some other specific implementations, the interface can include a wireless transmitter, a wireless transceiver, or a combination thereof. For example, the interface can include a radio frequency (RF) transceiver that can be implemented to receive or transmit signals, or both. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, executing threads, processes, functions, etc.

[0038] Thus, in one or more example implementations, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded on a computer-readable medium as one or more instructions or code. A computer-readable medium includes computer storage media, which can be referred to as non-transitory computer-readable media. Non-transitory computer-readable media may not include transitory signals. The storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can 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 the foregoing types of computer-readable media, or any other medium capable of storing computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0039] Figure 1FIG. is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (high-power cellular base station) or a small cell (low-power cellular base station). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells. Small cells include femto cells, pico cells, and micro cells. The base station 102 may be configured with a split RAN (D-RAN) or an open RAN (O-RAN) architecture, where functionality is split among multiple units (such as a central unit (CU), one or more distributed units (DU), or radio units (RU)). Such architectures may be configured to utilize a protocol stack that is logically split between one or more units (such as one or more CUs and one or more DUs). In some aspects, the CU may be implemented within an edge RAN node, and in some aspects, one or more DUs may be co-located with the CU or may be geographically distributed among one or more RAN nodes. The DU may be implemented to communicate with one or more RUs.

[0040] In some embodiments, one or more of the UEs 104 may include an L1 measurement component 140 that measures L1 channel characteristics. The L1 measurement component 140 may include a configuration component 142 configured to receive, from a current serving cell, a configuration of channel state information (CSI) reference signal (RS) measurement resources for L1 measurement of a candidate cell. The L1 measurement component 140 may include a measurement component 144 configured to measure a signal transmitted from the candidate cell based on whether the candidate cell is an in-band candidate cell or an inter-band candidate cell. In some embodiments, the L1 measurement component may optionally include a reporting component 146 configured to transmit an L1 CSI report including measurements of the candidate cell.

[0041] In some embodiments, one or more of the base stations 102 may include a measurement control component 120 configured to manage L1 measurements of the UEs. The measurement control component 120 may include a configuration Tx component 122 configured to transmit, from a current serving cell, a configuration of channel state information (CSI) reference signal (RS) measurement resources for L1 measurement of a candidate cell. The configuration is based on whether the candidate cell is an in-band candidate cell or an inter-band candidate cell. The measurement control component 120 may include a reporting Rx component 124 configured to receive an L1 CSI report including measurements of the candidate cell.

[0042] The base station 102 configured for 4G LTE (collectively referred to as the evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (such as the S1 interface), which can be wired or wireless. The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interact with the core network 190 via a second backhaul link 184, where the second backhaul link 184 can be wired or wireless. In addition to other functions, the 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 (such as 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), subscriber and equipment tracking, radio access network information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (such as via the EPC 160 or the core network 190) on a third backhaul link 134 (such as the X2 interface). The third backhaul link 134 can be wired or wireless.

[0043] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. There may be overlapping geographical coverage areas 110. 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 including both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which can serve a restricted group called a closed subscriber group (CSG). The communication link 112 between base station 102 and UE 104 can include an UL (also known as the reverse link) transmission from UE 104 to base station 102 or a DL (also known as the forward link) transmission from base station 102 to UE 104. The communication link 112 can use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity. The communication link can pass through one or more carriers. For each carrier allocated in carrier aggregation with a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 can use a spectrum with a bandwidth of up to Y MHz (such as 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers can be asymmetric with respect to DL and UL (such as, more or fewer carriers can be allocated for DL compared to UL). Component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell) and the secondary component carriers can be referred to as secondary cells (SCells).

[0044] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use DL / UL WWAN spectrum. The D2D communication link 158 can use one or more sidelink channels, such as the physical sidelink broadcast channel (PSBCH), the physical sidelink discovery channel (PSDCH), the physical sidelink shared channel (PSSCH), and the physical sidelink control channel (PSCCH). D2D communication can be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0045] The wireless communication system may further include a Wi-Fi access point (AP) 150, which 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 Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0046] The small cell 102' may operate in licensed or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may adopt NR and use the same 5 GHz unlicensed spectrum as that used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may boost the coverage of the access network or increase the capacity of the access network.

[0047] Whether it is the small cell 102' or a large cell (such as a macro base station), the base station 102 may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations (such as the gNB 180) may operate in one or more frequency bands within the electromagnetic spectrum.

[0048] The electromagnetic spectrum is generally subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as the Frequency Range Designation FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Similar naming issues sometimes occur with FR2. Although it is different from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) determined by the International Telecommunication Union (ITU) as the "millimeter wave" (mmW) band, it is generally (interchangeably) referred to as the "millimeter wave" band in various documents and articles. Communications using the mmW radio frequency band have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for this path loss and short range.

[0049] Taking the above aspects into account, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" etc. is used in this article, it may generally represent a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" etc. is used in this article, it may generally represent a frequency that can include mid-band frequencies, can be within FR2, or can be within the EHF band. Communications using the mmW radio frequency band have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for this path loss and short range.

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

[0051] The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that processes signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, or other IP services.

[0052] The base station may include or be referred to as a gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of the UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (such as MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with a similar function. Some UEs 104 may be referred to as IoT devices (such as parking meters, fuel pumps, ovens, vehicles, heart monitors, etc.). The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term.

[0053] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies, including future 6G technologies.

[0054] Figure 2A FIG. 200 is a diagram illustrating an example of a first frame. Figure 2B FIG. 230 is a diagram illustrating an example of a DL channel within a subframe. Figure 2C FIG. 250 is a diagram illustrating an example of a second frame. Figure 2D FIG. 280 is a diagram illustrating an example of a subframe. The 5G NR frame structure can be FDD, where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL, or it can be TDD, where for a specific set of subcarriers (carrier system bandwidth), the subframes in the set of subcarriers are dedicated to both DL and UL. A subset of the total cell bandwidth of a cell is referred to as a bandwidth part (BWP), and bandwidth adaptation is achieved by configuring the UE with the BWP and informing the UE which of the configured BWPs is the current active BWP. In one aspect, a narrow bandwidth part (NBWP) refers to a BWP having a bandwidth less than or equal to the maximum configurable bandwidth of the BWP. The bandwidth of the NBWP is less than the carrier system bandwidth.

[0055] In 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 (with most being DL), where D is DL, U is UL, and X can be flexibly used between DL / UL, and subframe 3 is configured with slot format 34 (with most being UL). Although subframes 3 and 4 are shown to have slot formats 34 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0 and 1 are all-DL and all-UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by receiving a slot format indicator (SFI) (configured dynamically via downlink control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0056] Other wireless communication technologies may have different frame structures or different channels. One frame (10 milliseconds (ms)) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot can include 14 symbols, and for slot configuration 1, each slot can include 7 symbols. The symbols on the DL can be cyclic prefix (CP) OFDM (CP - OFDM) symbols. The symbols on the UL can be CP - OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT - s - OFDM) symbols (also known as single - carrier frequency - division multiple access (SC - FDMA) symbols) (for power - limited scenarios; limited to single - stream transmission). The number of slots within a subframe is based on the slot configuration and numerology. For slot configuration 0, the different numerologies μ0 to 5 respectively allow each subframe to have 1, 2, 4, 8, 16, and 32 slots. For slot configuration 1, the different numerologies 0 to 2 allow each subframe to have 2, 4, and 8 slots respectively. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols per slot and 2 μ slots per subframe. The subcarrier spacing and symbol length / duration are functions of the numerology. The subcarrier spacing can be equal to 2 μ *15 kHz, where μ is the numerology from 0 to 5. Thus, the subcarrier spacing for numerology μ = 0 is 15 kHz, and the subcarrier spacing for numerology μ = 5 is 480 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2DAn example of a slot configuration 0 with 14 symbols per slot and a parameter set μ = 2 with 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs).

[0057] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0059] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine resource element groups (REGs), each REG including four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) can be in symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and L1 identification. The secondary synchronization signal (SSS) can be in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the L1 cell identification group number and radio frame timing. Based on the L1 identification and the L1 cell identification 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 master information block (MIB) can be logically grouped with the PSS and the SSS to form a synchronization signal (SS) / PBCH block (SSB). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted by the PBCH (such as system information blocks (SIBs)), and paging messages.

[0060] As Figure 2CAs illustrated, some of the REs in the RE carry DM-RS for channel estimation at the base station (for a specific configuration, which is indicated as R, 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 previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a sounding reference signal (SRS). The SRS can be transmitted in the last symbol of the subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the teeth of the comb. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0061] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), or UCI.

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

[0063] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on 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. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes such as 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 may be split into parallel streams. Each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal such as a pilot in the time domain or frequency domain, and combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is space precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 or channel condition feedback. Each spatial stream may be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX modulates an RF carrier with the corresponding spatial stream for transmission.

[0064] At the UE 350, each receiver 354RX receives signals via its corresponding 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 the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 uses a fast Fourier transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates computed by the channel estimator 358. These soft decisions are decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. These data and control signals are provided to the controller / processor 359 that implements layer 3 and layer 2 functionality.

[0065] 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 between the transport channel and the logical channel, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for supporting HARQ operations using error detection with the ACK or NACK protocol.

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

[0067] Channel estimates derived by the channel estimator 358 based on reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select appropriate decoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0068] UL transmissions are processed at the base station 310 in a manner similar to that described in connection with the receiver functionality at the UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0069] 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 between the transport channel and the logical channel, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for supporting HARQ operations using error detection with the ACK or NACK protocol.

[0070] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects in conjunction with Figure 1 L1 measurement component 140. For example, memory 360 may include executable instructions that define L1 measurement component 140. TX processor 368, RX processor 356, and / or controller / processor 359 may be configured to execute L1 measurement component 140.

[0071] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects in conjunction with Figure 1 measurement control component 120. For example, memory 376 may include executable instructions that define measurement control component 120. TX processor 316, RX processor 370, and / or controller / processor 375 may be configured to execute measurement control component 120.

[0072] Figure 4 is a diagram illustrating an exemplary disaggregated base station 400 architecture. The disaggregated base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with core network 420 via a backhaul link, or indirectly with core network 420 through one or more disaggregated base station units such as a near real-time (near-RT) Radio Access Network (RAN) Intelligent Controller (RIC) 425 via an E2 link, or a non-real-time (non-RT) RIC 415 associated with a Service Management and Orchestration (SMO) framework 405, or both. CU 410 may communicate with one or more distributed units (DUs) 430 via a respective midhaul link such as an F1 interface. DU 430 may communicate with one or more radio units (RUs) 440 via a respective fronthaul link. RU 440 may communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some particular implementations, UE 104 may be served simultaneously by multiple RUs 440.

[0073] Each of the units (i.e., CU 410, DU 430, RU 440, and the near RT RIC 425, non-RT RIC 415, and SMO framework 405) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or transmit signals, or both, to one or more of the other units via a wireless transmission medium.

[0074] In some aspects, the CU 410 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may utilize an interface that is configured to convey signals with other control functions hosted by the CU 410. The CU 410 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some embodiments, the CU 410 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bi-directionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 410 may be implemented to communicate with the DU 430 for network control and signaling.

[0075] The DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, the DU 430 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least partially according to a functional split (such as those defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 430 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 430 or with control functions hosted by the CU 410.

[0076] Lower layer functionality may be implemented by one or more RUs 440. In some deployments, the RUs 440 controlled by the DU 430 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both at least partially based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 440 may be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of control and user plane communication with the RUs 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration may enable the implementation of the DU 430 and the CU 410 in a cloud-based RAN architecture (such as a vRAN architecture).

[0077] The SMO framework 405 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 405 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 405 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 490) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 410, DU 430, RU 440, and near RT RIC 425. In some specific implementations, the SMO framework 405 can communicate with the hardware aspect of the 4G RAN (such as the Open eNB (O-eNB) 411) via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 can communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 can also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405.

[0078] The non-RT RIC 415 can be configured to include a logical function that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near RT RIC 425. The non-RT RIC 415 can be coupled to or communicate with the near RT RIC 425 (such as via the A1 interface). The near RT RIC 425 can be configured to include a logical function that can enable near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and this interface (such as via the E2 interface) connects one or more CUs 410, one or more DUs 430, or both, and the O-eNB to the near RT RIC 425.

[0079] In some specific implementations, to generate the AI / ML models to be deployed in the near RT RIC 425, the non-RT RIC 415 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near RT RIC 425 and can be received from non-network data sources or from network functions at the SMO framework 405 or at the non-RT RIC 415. In some examples, the non-RT RIC 415 or the near RT RIC 425 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 415 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 405 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0080] Figure 5 FIG. is an illustration showing an example of an L1 / L2 mobility scenario 500 for a primary cell (PCell). The UE 104 can initially be served by an active PCell 510. L1 / L2 mobility can allow the update of the PCell based on L1 measurements via L1 / L2 signaling. Scenario 500 can be applied to single PCell changes without carrier aggregation (CA). L1 / L2 mobility can be applied to both intra-frequency mobility and inter-frequency mobility.

[0081] During the L1 / L2 mobility procedure, the UE 104 can determine a target candidate cell (e.g., new PCell 520a) from a set of candidate cells 520. For example, the set of candidate cells 520 can include candidate PCells 520a, 520b, and 520c. The target candidate PCell 520a can be selected based on, for example, L1 measurements.

[0082] Figure 6 FIG. is an illustration showing an example of an L1 / L2 mobility scenario 600 for secondary cell (SCell) handover. Similar to the PCell scenario, the UE 104 can initially be served by an active PCell 610. The active PCell 610 can perform CA with an SCell 620. During the L1 / L2 mobility procedure, the UE 104 can determine a target candidate SCell (e.g., new SCell 620a) from a set of candidate SCells 620. For example, the set of candidate SCells 620 can include candidate SCells 620a, 620b, and 620c, which are SCells configured to perform CA with the PCell 610. The target candidate SCell 620a can be selected based on, for example, L1 measurements. The L1 / L2 mobility procedure can switch the candidate SCell 620a to become the new PCell. In some specific implementations, the old PCell 610 can become an SCell or can no longer be used as a serving cell (e.g., due to poor channel conditions).

[0083] Figure 7 FIG. is an illustration showing an example of the L1 / L2 mobility scenario 700 for a cell group (CG). When the UE 104 is configured with a cell group, the special cell (SpCell) and SCell can be switched as a group. For example, the current serving CG 710 may include the SpCell and SCell. The candidate CG set 720 may include candidate CGs 720a, 720b, and 720c. L1 / L2 mobility may allow for updating the serving CG 710 via L1 / L2 signaling based on L1 measurements. The target candidate CG 720a may be selected based on, for example, L1 measurements. The L1 / L2 mobility procedure may switch the candidate CG 720a to become the new serving CG.

[0084] L1 / L2 mobility may include mechanisms and procedures for L1 / L2-based inter-cell mobility to reduce mobility latency. For example, the configuration and maintenance for multiple candidate cells may allow for the rapid application of the configuration for the candidate cell 520. The dynamic switching mechanism between candidate serving cells (including PCell, SCell, and SpCell) may satisfy multiple potential applicable scenarios based on L1 / L2 signaling. L1 enhancements for inter-cell beam management (including L1 measurements and reports and beam indication) may facilitate L1 / L2 mobility. Timing advance management for candidate cells may facilitate L1 / L2 mobility. The CU-DU interface signaling supporting L1 / L2 mobility may be applicable to a distributed architecture. Example L1 / L2 mobility scenarios include: independent, CA, and NR-DC cases with serving cell changes within a cell group (CG); cases within the DU and cases between the CU and DU within the CU (applicable to independent and CA); both intra-frequency mobility and inter-frequency mobility; both the FR1 frequency range and the FR2 frequency range; and when the source cell and the target cell are synchronized or asynchronous.

[0085] Figure 8 FIG. is an illustration 800 showing the transmission of synchronization signal blocks (SSBs) and / or CSI-RSs for both intra-frequency mobility and inter-frequency mobility. The active serving cell 810 (e.g., PCell 510, PCell 610, or CG 710) may transmit the SSB 812 at the center frequency within the configured active bandwidth part (BWP) 806 within the carrier bandwidth 802. The various candidate cells 820 may include intra-frequency candidate cells 830 and inter-frequency candidate cells 840, 850, or 860.

[0086] A candidate cell 830 within a frequency can be a candidate cell that operates on the same carrier bandwidth 802, active BWP 806, and center frequency as the active serving cell 810 and has the same subcarrier spacing (SCS) as the active serving cell. For example, L3 in-frequency measurements can be defined as SSB-based in-frequency measurements, provided that the center frequency of the SSB of the serving cell indicated for measurement is the same as the center frequency of the SSB of the neighboring cell, and the subcarrier spacing of the two SSBs is also the same. For L3 measurements, it should be understood that the SSB does not need to be in the active BWP of the serving cell (e.g., the SSB can be extended to SSB / CSI-RS). In terms of inter-frequency measurements, L3 inter-frequency can be defined as a measurement that is not an in-frequency measurement (e.g., where in the candidate cell, the center frequency of the SCS of the SSB is different from the center frequency of the serving cell).

[0087] In NR Release 17, only narrow-category L1 in-frequency measurements of non-serving cells are allowed. For example, the UE can be configured in a serving cell configuration with CSI-RS, where the TCI of the CSI-RS is quasi-co-located with the non-serving cell SSB. However, the non-serving cell CSI-RS is restricted to having, for example, the same scrambling seed as the serving cell, an aligned Point A configuration, the same SCS, an aligned center frequency, and a system frame number (SFN) offset. Therefore, the configurable L1 in-frequency measurements in NR Release 17 may not be applicable to L1 / L2 mobility procedures with various types of cells.

[0088] In one aspect, the definition of in-frequency cells for L1 measurements can be relaxed or extended. For example, L1 measurements of candidate cells can be configured in the current serving cell because non-serving cell CSI-RS must be configured in the active DL BWP, but at least some configurations do not need to follow the serving cell: for example, the SCS and center frequency must be the same as the serving cell, but the scrambling sequence seed can follow the scrambling sequence seed of the non-serving cell. Similarly, the Point A configuration or SFN offset can vary. As another example, the L3 definition of in-frequency cells (e.g., the same center frequency and SCS) can be applied with optional additional restrictions such as the same BWP, the same SFN offset, or other BWP parameters.

[0089] The UE may perform intra-frequency measurements on candidate cells that meet the extended definition. In some specific implementations, such intra-frequency measurements do not require a measurement gap. However, in some specific implementations, the received timing difference between the serving cell and the candidate cell may be greater than the cyclic prefix (CP) length according to the SCS of the candidate cell. In this case, a symbol-level gap may be used to allow the UE to adjust the timing to receive a complete symbol. The symbol gap may be configured before and / or after the consecutive SSB / CSI RS symbols used for inter-frequency measurements (e.g., in the SSB measurement timing configuration (SMTC) window). For some definitions of intra-frequency cells, a measurement gap may be configured when the non-serving cell CSI-RS is outside the downlink active BWP.

[0090] In one aspect, any cell that does not meet the definition of an intra-frequency cell may be considered an inter-frequency cell. For example, inter-frequency cells may include the following scenarios: 1) the frequency of the measured RS is not covered by any of the active BWPs of the SpCell and Scells configured for the UE, but is covered by some of the configured BWPs of the SpCell and Scells configured for the UE; and 2) the frequency of the measured RS is not covered by any of the configured BWPs of the SpCell and Scells configured for the UE. Traditionally, L1 measurements of inter-frequency cells cannot be configured.

[0091] A first type of inter-frequency candidate cell 850 may transmit an SSB or CSI-RS 852 outside the active BWP 806 of the active serving cell 810 but within the configured carrier bandwidth 802 of the active serving cell 810.

[0092] As another example, a second type of inter-frequency candidate cell 860 may transmit an SSB or CSI-RS 862 outside the configured carrier bandwidth 802 of the active serving cell 810 (e.g., in carrier bandwidth 804).

[0093] As another example, a third type of inter-frequency candidate cell 840 may be a candidate cell that is different from the active serving cell 810 in terms of center frequency, SCS, active BWP, or carrier bandwidth 802. For example, the inter-frequency candidate cell 830 may transmit an SSB or CSI-RS 842 within the active BWP 806 of the active serving cell 810 but at a center frequency or SCS different from that of the SSB 812 of the active serving cell 810.

[0094] In one aspect, when the inter-frequency SSB / CSI-RS 842 is fully contained within the active DL BWP of the serving cell, the UE 104 may be able to perform inter-frequency measurements based on SSB / CSI-RS without measurement gaps. The UE may indicate the ability to perform inter-frequency measurements without measurement gaps on the inter-frequency cell 840. This ability may indicate limitations on the SCS or timing difference. In one aspect, it may be assumed that the UE is configured to perform inter-frequency measurements based on SSB / CSI with measurement gaps when the inter-frequency SSB / CSI 852 or 862 is outside the active DL BWP 806 of the serving cell. Additionally, if the Tx timings of the serving cell and the candidate cell are not aligned (e.g., the RRC flag deriveSSB-IndexFromCell is disabled), then the SMTC or measurement gaps may be configured. The measurement gaps may be configured before and / or after consecutive SSB / CSI RS symbols used for inter-frequency measurements (e.g., within the SMTC window).

[0095] Figure 9 Is a diagram of an example RRC configuration 900 for L1 measurements of a candidate cell. In one aspect, the RRC configuration 900 may include a CSI measurement configuration 910.

[0096] In some embodiments, the configuration of CSI-RS measurement resources for a candidate cell may be included within the configuration of the serving cell 920. For example, the serving cell 920 may include measurement resources for serving cell CSI-RS and measurement resources for candidate cell CSI-RS or SSB. The measurement resources for the candidate cell may include a PCI index. The PCI index may identify a separate configuration (e.g., an L3 measurement object) of the candidate cell 930. Parameters for the L1 measurement object may be defined in the separate configuration of the candidate cell 930. For example, the separate configuration of the candidate cell 930 may indicate one or more of the following: SFN alignment; the effective isotropic radiated power (EIRP) offset from the current serving cell; the scrambling sequence; the BWP setting of the candidate cell; whether the candidate cell is configured with symbol-level gaps or an SSB measurement timing configuration (SMTC); or the assumed reception timing difference between the candidate cell and the current serving cell. In some embodiments, the configuration of the candidate cell 930 may include a reference frequency CSI-RS. In some embodiments, the configuration of the candidate cell 930 indicates a measurement gap configuration, subcarrier spacing, power offset, SFN alignment with the serving cell, or bandwidth part information.

[0097] In some specific implementations, the CSI measurement configuration 910 may include a candidate cell configuration 940, which includes measurement resources for candidate cells. The measurement resources may correspond to SSBs or CSI-RSs for mobility. For example, the measurement resources corresponding to an SSB may indicate the set of SSBs to be measured, the SSB frequency, the SSB subcarrier spacing, and / or SMTC. The measurement resources for an SSB may include a measurement gap configuration. The measurement resources corresponding to a CSI-RS may include a reference cell index identifying a reference cell for timing. The measurement resources corresponding to a CSI-RS may include one or more of the following: subcarrier spacing, power offset, alignment with the SFN of the serving cell, or bandwidth part information.

[0098] Figure 10 Message diagram 1000 illustrates various messages for L1 measurements. The UE 104 may send a capability message 1010 indicating the UE's ability to perform L1 measurements.

[0099] The serving cell 810 may send an RRC configuration 1020. The RRC configuration 1020 may configure channel CSI-RS measurement resources for L1 measurements of candidate cells. For example, the RRC configuration 1020 may include the CSI measurement configuration 910.

[0100] The serving cell 810 may send an SSB 1030 for the serving cell. For example, the SSB / CSI-RS 1030 may correspond to the SSB 812. The UE 104 may perform L1 measurements (e.g., measure the L1 reference signal received power (RSRP) or the L1 signal-to-noise plus interference ratio (SINR) of the SSB 1030). In some specific implementations, the measurement gap 1032 may allow the UE 104 to adjust timing and / or frequency before the candidate cell 820 transmits an SSB / CSI-RS 1040 on the configured measurement resources. For example, the SSB / CSI-RS 1040 may correspond to any one of the SSB / CSI-RS 832, 842, 852, or 862. The UE 104 may measure the SSB / CSI-RS 1040 of the candidate cell to obtain L1 measurements, such as L1 RSRP or L1 SINR. In one aspect, the measurement may be based on whether the candidate cell is an in-band candidate cell or an inter-band candidate cell. For example, the presence or length of the measurement gap 1032 may be based on the type of the candidate cell.

[0101] In some specific implementations, the UE 104 may send a CSI report 1050 including L1 measurements of the candidate cell 820. The UE 104, the serving cell 810, and / or the candidate cell may determine whether to perform an L1 / L2 mobility procedure based on the CSI report 1050.

[0102] During an example L1 / L2 mobility procedure, serving cell 810 and / or candidate cell 820 may send message 1060 that preconfigures or indicates a TCI state. For example, message 1060 may include RRC configuration and / or MAC-CE. Serving cell 810 and / or candidate cell 820 may send an L1 / L2 mobility command 1070 (e.g., MAC-CE or DCI) that indicates to the UE to switch to candidate cell 820. Candidate cell 820 (now the new serving cell) may send a TCI state indication 1080 (e.g., DCI) to inform the UE of the TCI state to be used for communicating with the new serving cell, where the TCI state indication 1080 may be transmitted before, simultaneously with, or after the cell handover command.

[0103] Figure 11 FIG. 1100 is a conceptual data flow diagram that illustrates data flows between different components / elements in example base station 102, which may be a base station 102 that includes a measurement control component 120 ( Figure 1 ). The measurement control component 120 may be implemented by Figure 3 the memory 376 and TX processor 316, RX processor 370, and / or controller / processor 375. For example, the memory 376 may store executable instructions that define the measurement control component 120, and the TX processor 316, RX processor 370, and / or controller / processor 375 may execute these instructions.

[0104] Base station 102 may include a receiver component 1170, which may include, for example, a radio frequency (RF) receiver for receiving the signals described herein. Base station 102 may include a transmitter component 1172, which may include, for example, an RF transmitter for transmitting the signals described herein. In one aspect, the receiver component 1170 and the transmitter component 1172 may be co-located in a transceiver (such as Figure 3 illustrated by TX / RX 318 in

[0105] As discussed with respect to Figure 1 the measurement control component 120 may include a configured Tx component 122 and a reporting Rx component 124.

[0106] The receiver component 1170 may receive UL signals from UE 104 that include a capability message 1010 and a CSI report 1050. The receiver component 1170 may provide the capability message 1010 to the configured Tx component 122. The receiver component 1170 may provide the CSI report 1050 to the reporting Rx component 124, providing the message to the reporting Rx component 124.

[0107] The configuration Tx component 122 can be configured to send, from the current serving cell, a configuration of CSI-RS measurement resources for L1 measurements of candidate cells. In some specific implementations, the configuration Tx component 122 can obtain a capability message 1010. The configuration Tx component 122 can determine, based on the capability message 1010, that the UE 104 is capable of performing L1 measurements. The configuration Tx component 122 can receive information about candidate cells from the core network 190 (e.g., the AMF 192). The configuration Tx component 122 can select candidate cells for the UE 104 and generate an RRC configuration 1020 that identifies the L1 measurement resources corresponding to these candidate cells. This configuration is based on whether the candidate cells are intra-frequency candidate cells or inter-frequency candidate cells. For example, the configuration Tx component 122 can generate a CSI measurement configuration 910. The parameters for each measurement resource can be based on the type of candidate cell. The configuration Tx component 122 can output the RRC configuration 1020 to be sent to the UE 104 via the transmitter component 1172.

[0108] The reporting Rx component 124 can be configured to receive an L1 CSI report 1050 that includes measurements of candidate cells. For example, the measurement control component 120 can obtain the L1 CSI report 1050 via the receiver component 1170. In some specific implementations, the reporting Rx component 124 can evaluate the L1 measurements. For example, the reporting Rx component 124 determines whether the L1 measurements meet the L1 / L2 mobility conditions. In some specific implementations, the reporting Rx component 124 can output an L1 / L2 mobility message (such as message 1060, mobility command 1070, or TCI state indication 1080) to be sent to the UE 104 via the transmitter component 1172.

[0109] Figure 12 is a conceptual data flow diagram 1200 that illustrates the data flow between different components / parts in the exemplary UE 104, and this exemplary UE can be an example of the UE 104 ( Figure 1 ) and includes an L1 measurement component 140. The L1 measurement component 140 can be implemented by the memory 360 and the TX processor 368, the RX processor 356, and / or the controller / processor 359. For example, the memory 360 can store executable instructions that define the L1 measurement component 140, and the TX processor 368, the RX processor 356, and / or the controller / processor 359 can execute these instructions.

[0110] The UE 104 can include a receiver component 1270, which can include, for example, an RF receiver for receiving the signals described herein. The UE 104 can include a transmitter component 1272, which can include, for example, an RF transmitter for transmitting the signals described herein. In one aspect, the receiver component 1270 and the transmitter component 1272 can be co-located in a transceiver (such as Figure 3in the TX / RX 352).

[0111] As discussed with respect to Figure 1 As discussed, the L1 measurement component 140 may include a configuration component 142 and a measurement component 144. In some embodiments, the L1 measurement component 140 may include a reporting component 146 and / or a mobility component 1210.

[0112] The receiver component 1270 may receive the DL signals described herein, such as the RRC configuration 1020, the SSB / CSI-RS 1030, the SSB / CSI-RS 1040, the message 1060, the mobility command 1070, or the TCI state indication 1080. The receiver component 1270 may provide the RRC configuration 1020 to the configuration component 142. The receiver component 1270 provides the SSB / CSI-RS 1030 and / or the SSB / CSI-RS 1040 to the measurement component 144. The receiver component 1270 may provide the message 1060, the mobility command 1070, or the TCI state indication 1080 to the mobility component 1210.

[0113] The configuration component 142 may be configured to receive, from the current serving cell, a configuration of CSI-RS measurement resources for L1 measurements of candidate cells. For example, the configuration component 142 may receive the RRC configuration 1020 via the receiver component 1270. The configuration component 142 may determine, based on the information element of the RRC configuration 1020, the CSI-RS measurement resources for L1 measurements of candidate cells. The configuration component 142 may output the measurement resources to the measurement component 144. The configuration component 142 may output a reporting configuration to the reporting component 146.

[0114] The measurement component 144 may be configured to measure signals transmitted from candidate cells based on whether the candidate cells are intra-frequency candidate cells or inter-frequency candidate cells. For example, the measurement component 144 may receive the SSB / CSI-RS 1030, 1040 via the receiver component 1270. In some embodiments, the measurement component 144 may tune the receiver component 1270 to the correct frequency to receive inter-frequency SSB / CSI-RS. In some embodiments, the measurement component 144 may adjust the timing for receiving the SSB / CSI-RS. The measurement component 144 may determine measurements such as L1 RSRP or L1 SINR based on the received SSB / CSI-RS. The measurement component 144 may output these measurements to the reporting component 146 and / or the mobility component 1210.

[0115] The reporting component 146 may be configured to send an L1 CSI report 1050 including measurements of candidate cells. For example, the reporting component 146 may obtain a reporting configuration from the configuration component 142. The reporting component 146 may obtain these measurements from the measurement component 144. The reporting component 146 may include the configured measurements in the CSI report 1050. The reporting component 146 may output the CSI report 1050 for transmission via the transmitter component 1272.

[0116] The mobility component 1210 may be configured to perform L1 / L2 mobility procedures. The mobility component 1210 may receive mobility messages via the receiver component 1270. For example, the mobility component 1210 may receive a message 1060, a mobility command 1070, and / or a TCI state indication 1080. The mobility component 1210 may configure the UE 104 as indicated in the L1 / L2 mobility message.

[0117] Figure 13 FIG. is a block diagram conceptually illustrating an example of a hardware implementation of a user equipment (UE) 1300 employing a processing system 1314 in accordance with some aspects of the present disclosure. In accordance with various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using the processing system 1314, which includes one or more processors 1304. In some implementations, the UE 1300 may correspond to any of the UEs or scheduled entities shown in any of the figures included herein.

[0118] The UE 1300 may be implemented using a processing system 1314 that includes one or more processors 1304. Examples of the processor 1304 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, the UE 1300 may be configured to perform any one or more of the functions described herein. That is, the processor 1304 as utilized in the UE 1300 may be used to implement any one or more of the processes and procedures described below.

[0119] In this example, a bus architecture, generally represented by bus 1302, may be utilized to implement processing system 1314. Bus 1302 may include any number of interconnected buses and bridges, depending on the specific application of processing system 1314 and overall design constraints. Bus 1302 communicatively couples together various circuits of one or more processors, generally represented by processor 1304, memory 1305, and computer-readable medium, generally represented by computer-readable medium 1306. Bus 1302 may also link various other circuits, such as a timing source, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further herein. Bus interface 1308 provides an interface between bus 1302 and transceiver 1310, and between bus 1302 and interface 1330. Transceiver 1310 provides a communication interface or component for communicating with various other devices via a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1310, each transceiver being configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial). At least one interface 1330 (e.g., a network interface and / or user interface) provides a communication interface or component for communicating with various other devices and apparatuses (e.g., with UE 1300 or other devices housed within the same device as an external device) via an internal bus or via an external transmission medium, such as an Ethernet cable.

[0120] Processor 1304 is responsible for managing bus 1302 and general processing, including the execution of software stored on computer-readable medium 1306. The software, when executed by processor 1304, causes processing system 1314 to perform the various functions described hereinafter for any particular apparatus. Computer-readable medium 1306 and memory 1305 may also be used to store data manipulated by processor 1304 when executing the software.

[0121] One or more processors 1304 in the processing system may execute the software. The software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on computer-readable medium 1306.

[0122] The computer-readable medium 1306 can be a non-transitory computer-readable medium. Non-transitory computer-readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disc (CD) or digital versatile disc (DVD)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 1306 can reside within the processing system 1314, be located external to the processing system 1314, or be distributed across multiple entities including the processing system 1314. The computer-readable medium 1306 can be embodied in a computer program product. For example, the computer program product can include the computer-readable medium in a package material. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure, depending on the particular application and overall design constraints imposed on the overall system.

[0123] The UE 1300 can be configured to perform any one or more of the operations described herein (e.g., as described above in connection with Figures 1 to 12 and as described below in connection with Figure 14 and Figure 15 ). In some aspects of the present disclosure, the processor 1304 utilized in the UE 1300 can include circuitry configured for various functions.

[0124] In one aspect, the processor 1304 can include communication and processing circuitry 1341. The communication and processing circuitry 1341 can include one or more hardware components that provide a physical structure that performs various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuitry 1341 can also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuitry 1341 can include two or more transmit / receive chains. The communication and processing circuitry 1341 can also be configured to execute communication and processing instructions 1351 included on the computer-readable medium 1306 to implement one or more of the functions described herein.

[0125] In a particular configuration of the UE 1300, the processor 1304 may detect a first reference signal and a second reference signal in conjunction with the communication and processing circuitry 1341 and / or the transceiver 1310, where the first reference signal has resources that overlap with the second reference signal, and where at least one of the first reference signal or the second reference signal is from a non-serving cell. In this configuration, the processor 1304 may also, in conjunction with the communication and processing circuitry 1341 and / or the transceiver 1310, determine the context associated with at least one of the first reference signal or the second reference signal, and perform a layer 1 (L1) measurement of at least one of the first reference signal or the second reference signal according to a prioritization associated with the context.

[0126] In another aspect of this particular configuration, it is contemplated that the prioritization associated with the context may be based on any one of a variety of parameters. For example, the prioritization may be based on whether the L1 measurement is an inter-frequency measurement or an intra-frequency measurement, and / or based on whether the overlapping resources have the same subcarrier spacing (SCS). In another aspect, the prioritization is based on the UE capabilities corresponding to how many overlapping resources the UE can measure at one time, and / or based on the UE capabilities corresponding to how many cell reference signals the UE can measure at one time.

[0127] Also contemplated are various other parameters on which the prioritization may be based. For example, the prioritization may be based on the frequency band from which the first reference signal and the second reference signal are detected. The prioritization may also be based on the corresponding reference signal type associated with the first reference signal and the second reference signal (e.g., CSI-RS or SSB), and / or based on the type of L1 measurement to be performed (e.g., L1 SINR measurement, where the prioritization is based on whether at least one of the first reference signal or the second reference signal is an interference measurement reference signal).

[0128] In another example, the prioritization may be based on the purpose of the overlapping resources. For example, it is contemplated that the purpose of the overlapping resources may be one of radio link monitoring (RLM), beam failure detection (BFD), candidate beam detection (CBD), layer 1 reference signal received power (L1-RSRP) measurement, or layer 1 signal to interference plus noise ratio (L1-SINR) measurement.

[0129] In yet another example, the prioritization may be based on the physical cell identifier (PCI) associated with at least one of the first reference signal or the second reference signal. For example, it is contemplated that the prioritization may be based on whether the PCI is the serving cell PCI or the non-serving cell PCI.

[0130] Various examples of inter-frequency and intra-frequency measurement limitations that may be implemented by the UE 1300 are provided herein. For example, when CSI-RS is configured for L1-RSRP measurement, a first set of examples is contemplated.

[0131] In a first example of this first set, for both FR1 and FR2, when the CSI-RS for L1-RSRP measurement is in the same OFDM symbol as the SSB for RLM, BFD, CBD, or L1-RSRP measurement, UE 1300 may not need to receive the CSI-RS for L1-RSRP measurement in the PRB that overlaps with the SSB.

[0132] In a second example of this first set, for FR1, when the SSB for RLM, BFD, CBD, or L1-RSRP measurement is within the active BWP and has the same SCS as the CSI-RS for L1-RSRP measurement, UE 1300 may be allowed to perform CSI-RS measurement without restriction.

[0133] In a third example of this first set, for FR1, when the SSB for RLM, BFD, CBD, or L1-RSRP measurement is within the active BWP and has a different SCS from the CSI-RS for L1-RSRP measurement, UE 1300 may be allowed to perform CSI-RS measurement with restrictions according to the capabilities of UE 1300. For example, in a specific configuration, if UE 1300 supports "simultaneousRxDataSSB-DiffNumerology", UE 1300 may be allowed to perform CSI-RS measurement without restriction. However, if UE 1300 does not support "simultaneousRxDataSSB-DiffNumerology", then UE 1300 may need to measure either the CSI-RS or the SSB for L1-RSRP measurement but not both (which may result in a longer measurement period for CSI-RS-based L1-RSRP measurement).

[0134] In a fourth example of this first set, for FR1, when the CSI-RS for L1-RSRP measurement is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD, or L1-RSRP measurement, UE 1300 may be allowed to measure the CSI-RS for L1-RSRP measurement without any restriction.

[0135] In the fifth example of this first set, for FR2, when the CSI-RS for L1-RSRP measurement on a CC is in the same OFDM symbol as the SSB for RLM, BFD, or L1-RSRP measurement on the same or a different CC in the same frequency band, or in the same symbol as the SSB for CBD measurement on the same or a different CC in the same frequency band when a beam failure is detected, the UE 1300 may need to measure either the CSI-RS or the SSB for L1-RSRP measurement but not both (which may result in a longer measurement period for CSI-RS-based L1-RSRP measurement).

[0136] In the sixth example of this first set, for FR2, when the CSI-RS for L1-RSRP measurement on a CC is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD, or L1-RSRP measurement on the same or a different CC in the same frequency band, the UE 1300 may need to measure either the CSI-RS or the other CSI-RS for L1-RSRP measurement but not both (which may result in a longer measurement period for CSI-RS-based L1-RSRP measurement) for the following cases: 1) The CSI-RS for L1-RSRP measurement or the other CSI-RS in the resource set is configured with repetition ON; 2) Another CSI-RS is configured in q1 and a beam failure is detected; or 3) The two CSI-RSs are not quasi-co-located (QCL) with respect to QCL-Type D, or the UE 1300 does not know the QCL information. Otherwise, the UE 1300 may be allowed to measure the CSI-RS for L1-RSRP measurement without any restrictions.

[0137] A second set of exemplary embodiments is envisioned when CSI-RS is configured for L1-SINR measurement.

[0138] In the first example of this second set, for both FR1 and FR2, when the CSI-RS configured for L1-SINR measurement is in the same OFDM symbol as the SSB for RLM, BFD, CBD, L1-RSRP, or L1-SINR measurement, the UE 1300 may not need to receive the CSI-RS for L1-SINR measurement in the PRBs overlapping with the SSB.

[0139] In the second example of this second set, for FR1, when the SSB used for RLM, BFD, CBD, L1-RSRP, or L1-SINR measurement is within the active BWP and has the same SCS as the CSI-RS configured for L1-SINR measurement, the UE 1300 is allowed to perform CSI-RS measurement without restriction.

[0140] In the third example of this second set, for FR1, when the SSB used for RLM, BFD, CBD, L1-RSRP, or L1-SINR measurement is within the active BWP and has a different SCS from the CSI-RS configured for L1-SINR measurement, the UE 1300 is allowed to perform CSI-RS measurement with restrictions according to the capabilities of the UE 1300. For example, in a specific configuration, if the UE 1300 supports "simultaneousRxDataSSB-DiffNumerology", the UE 1300 is allowed to perform CSI-RS measurement without restriction. However, if the UE 1300 does not support "simultaneousRxDataSSB-DiffNumerology", the UE 1300 may need to measure either the CSI-RS or the SSB for L1-SINR measurement but not both (which may result in a longer measurement period for CSI-RS-based L1-SINR measurement).

[0141] In the fourth example of this second set, for FR1, when the CSI-RS configured for L1-SINR measurement is in the same OFDM symbol as another CSI-RS used for RLM, BFD, CBD, L1-RSRP, or L1-SINR measurement, the UE 1300 is allowed to measure the CSI-RS for L1-SINR measurement without any restriction.

[0142] In the fifth example of this second set, for FR2, when the CSI-RS configured for L1-SINR measurement on one CC is in the same OFDM symbol as the SSB used for RLM, BFD, L1-RSRP, or L1-SINR measurement on the same CC or a different CC in the same frequency band, or in the same symbol as the SSB used for CBD measurement on the same CC or a different CC in the same frequency band when a beam failure is detected, the UE 1300 may need to measure either the CSI-RS or the SSB for L1-SINR measurement but not both (which may result in a longer measurement period for CSI-RS-based L1-SINR measurement).

[0143] In the sixth example of this second set, for FR2, when the CSI-RS configured for L1-SINR measurement on a CC is in the same OFDM symbol as another CSI-RS for RLM, BFD, CBD, L1-RSRP, or L1-SINR measurement on the same or a different CC in the same frequency band, the UE 1300 may need to measure either the CSI-RS for L1-SINR measurement or the other CSI-RS but not both (which may result in a longer measurement period for CSI-RS-based L1-SINR measurement) for the following cases: 1) The CSI-RS for L1-SINR measurement or another CSI-RS in the resource set is configured with repeated activation; 2) The CSI-RS or the other CSI-RS is configured as a dedicated interference management resource (IMR) for L1-SINR calculation using the SSB as the channel measurement resource (CMR); 3) Another CSI-RS is configured in q1 and a beam failure is detected; or 4) The two CSI-RSs are not quasi-co-located (QCL) with respect to QCL-Type D, or the UE 1300 does not know the QCL information. Otherwise, the UE 1300 may be allowed to measure the CSI-RS for L1-SINR measurement without any restrictions.

[0144] When CSI interference management (CSI-IM) resources are configured for L1-SINR measurement, a third set of exemplary embodiments is envisioned.

[0145] In the first example of this third set, for both FR1 and FR2, when the CSI-IM resources configured for L1-SINR measurement are in the same OFDM symbol as the SSB for RLM, BFD, CBD, L1-RSRP, or L1-SINR measurement, the UE1300 may not need to measure the CSI-IM resources configured for L1-SINR measurement in the PRBs overlapping with the SSB.

[0146] In the second example of this third set, for FR1, the UE 1300 may be allowed to measure the CSI-IM resources configured for L1-SINR measurement without any restrictions.

[0147] In a third example of this third set, for FR2, when the CSI-IM resource configured for L1-SINR measurement on a CC is in the same OFDM symbol as the SSB for RLM, BFD, L1-RSRP, or L1-SINR measurement on the same CC or a different CC in the same frequency band, or in the same symbol as the SSB for CBD measurement on the same CC or a different CC in the same frequency band when a beam failure is detected, UE 1300 may need to measure either the CSI-IM resource or the SSB for L1-SINR measurement but not both (which may result in a longer measurement period for L1-SINR measurement).

[0148] In a fourth example of this third set, for FR2, when the CSI-IM resource configured for L1-SINR measurement on a CC is in the same OFDM symbol as the CSI-RS for RLM, BFD, CBD, L1-RSRP, or L1-SINR measurement on the same CC or a different CC in the same frequency band, UE 1300 may need to measure either the CSI-IM resource or the CSI-RS for L1-SINR measurement but not both (which may result in a longer measurement period for L1-SINR measurement) for the following cases: 1) The CSI-RS in the resource set is configured with repeated activation; 2) The CSI-IM resource or the CSI-RS is configured as a dedicated IMR for L1-SINR calculation with the SSB as the CMR; 3) The CSI-RS is configured in q1 and a beam failure is detected; or 4) The CMR and the CSI-RS for L1-SINR measurement are not quasi-co-located (QCL) with respect to QCL-Type D, or UE 1300 does not know the QCL information. Otherwise, UE 1300 may be allowed to measure the CSI-IM resource configured for L1-SINR measurement without any restrictions.

[0149] In another configuration of UE 1300, processor 1304 may communicate with a gNodeB (gNb) using one or more transmission configuration indication (TCI) states in conjunction with communication and processing circuitry 1341 and / or transceiver 1310, where each of the one or more TCI states is associated with a corresponding CORESET pool of one or more control resource sets (CORESETs), and where each CORESET pool corresponds to a transmit receive point (TRP). In this configuration, processor 1304 may also identify one or more sets of beam failure detection (BFD) reference signals in conjunction with communication and processing circuitry 1341 and / or transceiver 1310 (e.g., where the one or more sets of BFD reference signals are source reference signals associated with one or more TCI states), where the one or more sets of BFD reference signals are explicitly identified via configuration signaling from the gNb or implicitly identified based on one or more TCI states in the absence of configuration signaling. Processor 1304 may also monitor the one or more sets of BFD reference signals in conjunction with communication and processing circuitry 1341 and / or transceiver 1310 to facilitate detection of a beam failure event.

[0150] Aspects of this particular configuration are envisioned. For example, it is envisioned that processor 1304 may be configured to identify a single set of BFD reference signals based on indication signaling received from the gNb corresponding to a single TCI state. Processor 1304 may then also be configured to associate the single set of BFD reference signals with each TRP of the cell.

[0151] In another aspect, processor 1304 may be configured to identify multiple sets of BFD reference signals based on indication signaling received from the gNb corresponding to multiple TCI states. Processor 1304 may then also be configured to associate the multiple sets of BFD reference signals with the corresponding multiple TRPs of the cell. For example, processor 1304 may be configured to detect a beam failure event at the TRP level and / or at the cell level.

[0152] In another aspect, processor 1304 may be configured to identify multiple sets of BFD reference signals based on indication signaling received from the gNb corresponding to a single TCI state. For example, processor 1304 may be configured to implicitly select multiple sets of BFD reference signals based on a single TCI state and a previously indicated TCI state.

[0153] In another example, it is contemplated that the processor 1304 may be configured to identify multiple sets of BFD reference signals when the UE has not received signaling indicating the TCI state. For this example, the processor 1304 may also be configured to: identify multiple sets of BFD reference signals based on an active TCI code point including multiple TCI states; select, among all TCI code points having two or more TCI states, the TCI code point having the lowest identifier; and use two or more TCI states included in the selected TCI code point to identify the BFD reference signals to be monitored.

[0154] In another aspect, the processor 1304 may be configured to receive a scheduling command for a communication assignment via a specific CORESET pool. For this example, the processor 1304 may also be configured to select, from one or more TCI states, the TCI state associated with the specific CORESET pool used for the communication assignment. Here, it should be understood that the communication assignment may be any one of various types, including, for example, a type corresponding to one of the following: semi-persistent / aperiodic (SP / AP) channel state information reference signal (CSI-RS) for tracking reference signals, channel state feedback, beam management, SP / AP sounding reference signal (SRS) for antenna switching, codebook-based transmission, non-codebook-based transmission, physical random access channel (PRACH) based on a physical downlink control channel (PDCCH) command, SP / AP physical uplink shared channel (PUSCH), or SP / AP physical uplink control channel (PUCCH).

[0155] Next, referring to Figure 14 , a flowchart is provided that illustrates a first exemplary wireless communication method 1400 implemented by a UE in accordance with some aspects of the present disclosure. As described herein, in certain specific implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for the implementation of all examples. In some examples, method 1400 may be performed by the UE 1300 illustrated in Figure 13 . In some examples, method 1400 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0156] At block 1402, the UE 1300 may detect a first reference signal and a second reference signal, where the first reference signal has resources overlapping with the second reference signal, and where at least one of the first reference signal or the second reference signal is from a non-serving cell. In one aspect, the process of block 1402 may be implemented by a component for detecting reference signals, and in a particular aspect, the component may be implemented by the processor 1304, communication and processing circuitry 1341, and / or transceiver 1310 or their equivalents.

[0157] In addition, at block 1404, the UE 1300 may determine the context associated with at least one of the first reference signal or the second reference signal. In one aspect, the process of block 1404 may be implemented by components for determining the context, and in a particular aspect, the components may be implemented by the processor 1304 and / or the communication and processing circuitry 1341 or their equivalents.

[0158] Method 1400 ends at block 1406, where the UE 1300 may perform L1 measurements of at least one of the first reference signal or the second reference signal according to a prioritization associated with the context. In one aspect, the process of block 1406 may be implemented by components for performing L1 measurements of the reference signal, and in a particular aspect, the components may be implemented by the processor 1304 and / or the communication and processing circuitry 1341 or their equivalents.

[0159] Next, referring Figure 15 , a flowchart is provided that illustrates a second exemplary wireless communication method 1500 implemented by a UE according to some aspects of the present disclosure. As described herein, in certain specific implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for the implementation of all examples. In some examples, method 1500 may be performed by Figure 13 the UE 1300 illustrated in

[0160] At block 1502, the UE 1300 may communicate with the gNb using one or more TCI states, where each of the one or more TCI states is associated with a corresponding CORESET pool of one or more CORESETs, and where each CORESET pool corresponds to a TRP. In one aspect, the process of block 1502 may be implemented by components for communicating with the gNb, and in a particular aspect, the components may be implemented by the processor 1304, the communication and processing circuitry 1341, and / or the transceiver 1310 or their equivalents.

[0161] Further at block 1504, the UE 1300 may identify one or more sets of BFD reference signals, where the one or more sets of BFD reference signals are explicitly identified via configuration signaling from the gNb or implicitly identified based on one or more TCI states in the absence of configuration signaling. In one aspect, the process of block 1504 may be implemented by components for identifying the sets of BFD reference signals, and in a particular aspect, the components may be implemented by the processor 1304 and / or the communication and processing circuitry 1341 or their equivalents.

[0162] Method 1500 ends at block 1506, where UE 1300 may monitor one or more sets of BFD reference signals to facilitate detection of a beam failure event. In one aspect, the process of block 1506 may be implemented by components for monitoring BFD reference signals, and in a particular aspect, the components may be implemented by processor 1304 and / or communication and processing circuitry 1341 or their equivalents.

[0163] Figure 16 FIG. is a block diagram conceptually illustrating an example of a hardware implementation of a network node or entity 1600 employing a processing system 1614 in accordance with some aspects of the present disclosure. In accordance with various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using processing system 1614, which includes one or more processors 1604. In some implementations, network entity 1600 may correspond to a BS (e.g., gNB, eNB, etc.) or any one of the scheduling entities shown in any of the figures included herein. In another aspect, network entity 1600 may be configured as a base station operable in an Open RAN (O-RAN) environment, where the base station (e.g., 1600) is decomposed and includes different parts, including a distributed unit (DU), a centralized unit (CU), and a radio unit (RU). In still other aspects, the disclosed and illustrated processing portions of network entity 1600 may be implemented within the RU, DU, and / or CU or portions of each. Additionally, network entity 1600 may be a stationary network entity or a mobile network entity.

[0164] Network entity 1600 may be implemented using processing system 1614, which includes one or more processors 1604. Examples of processors 1604 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout the present disclosure. In various examples, network entity 1600 may be configured to perform any one or more of the functions described herein. That is, processor 1604 as utilized in network entity 1600 may be used to implement any one or more of the processes and procedures described herein.

[0165] In this example, a bus architecture, generally represented by bus 1602, may be utilized to implement processing system 1614. Bus 1602 may include any number of interconnected buses and bridges, depending on the specific application of processing system 1614 and overall design constraints. Bus 1602 communicatively couples together various circuits of one or more processors (generally represented by processor 1604), memory 1605, and computer-readable medium (generally represented by computer-readable medium 1606). Bus 1602 may also link various other circuits, such as a timing source, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further herein. Bus interface 1608 provides an interface between bus 1602 and transceiver 1610, and between bus 1602 and interface 1630. Transceiver 1610 provides a communication interface or component for communicating with various other devices via a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1610, each transceiver configured to communicate with a respective network type (e.g., terrestrial or non-terrestrial). At least one interface 1630 (e.g., a network interface and / or a user interface) provides a communication interface or component for communicating with various other devices and equipment (e.g., network entity 1600 or other devices housed within the same device as an external device) via an internal bus or an external transmission medium, such as an Ethernet cable.

[0166] Processor 1604 is responsible for managing bus 1602 and general processing, including the execution of software stored on computer-readable medium 1606. The software, when executed by processor 1604, causes processing system 1614 to perform the various functions described hereinafter for any particular device. Computer-readable medium 1606 and memory 1605 may also be used to store data manipulated by processor 1604 when executing the software.

[0167] One or more processors 1604 in the processing system may execute the software. The software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on computer-readable medium 1606.

[0168] The computer-readable medium 1606 can be a non-transitory computer-readable medium. Non-transitory computer-readable media include, for example, magnetic storage devices (such as hard disks, floppy disks, magnetic strips), optical disks (such as compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (such as cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 1606 can reside within the processing system 1614, be located external to the processing system 1614, or be distributed across multiple entities including the processing system 1614. The computer-readable medium 1606 can be embodied in a computer program product. For example, the computer program product can include the computer-readable medium in a packaging material. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure, depending on the particular application and overall design constraints imposed on the overall system.

[0169] The network entity 1600 can be configured to perform any one or more of the operations described herein (e.g., as described above in connection with Figures 1 to 12 and as described below in connection with Figure 17 ). In some aspects of the present disclosure, the processor 1604 utilized in the network entity 1600 can include circuitry configured for various functions.

[0170] The processor 1604 can be configured to generate, schedule, and modify resource assignments or grants for time-frequency resources (e.g., a collection of one or more resource elements). For example, the processor 1604 can schedule time-frequency resources within multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) subframes, time slots, and / or mini-slots to carry user data traffic and / or control information to and / or from multiple UEs.

[0171] The processor 1604 may be configured to schedule resources for transmitting downlink reference signals (e.g., SSB or CSI-RS) or DCI (or SRS trigger) on multiple downlink beams for downlink beam scanning, based on the selected downlink beam scanning type and the selected number of downlink reference signal resources indicated in a request received from the UE for uplink beam refinement. The processor 1604 may also be configured to schedule resources for uplink transmission of uplink reference signals (e.g., SRS) on multiple uplink beams for uplink beam scanning, based on the selected beam scanning type and the selected number of uplink reference signal resources indicated in the request. The processor 1604 may also be configured to schedule resources that the UE may use to send the request. For example, the uplink beam refinement request resources may include resources for scheduling transmission of PUCCH, PUSCH, PRACH occasion, or RRC message. In some examples, the processor 1604 may be configured to schedule PUSCH resources for an uplink beam refinement request in response to receiving a scheduling request from the UE.

[0172] The processor 1604 may also be configured to schedule resources for transmitting uplink signals. In some examples, based on an indication of the uplink signal associated with one or more uplink transmission beams included in the request, the resources may be associated with one or more uplink transmission beams and one or more corresponding receive beams applied to the uplink signal (e.g., based on uplink BPL). In some examples, the resources may be associated with an uplink transmission scheme that indicates the number of uplink transmission beams to be used for the uplink signal, the number of repetitions per uplink transmission beam of the uplink signal, and the multiplexing scheme when using more than one uplink transmission beam to transmit the uplink signal.

[0173] The processor 1604 may include communication and processing circuitry 1641. The communication and processing circuitry 1641 may include one or more hardware components that provide a physical structure that performs various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuitry 1641 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuitry 1641 may include two or more transmit / receive chains. In another example, the communication and processing circuitry 1641 may be configured to convey higher layer information, such as RRC configuration information, to the UE. The communication and processing circuitry 1641 may also be configured to execute communication and processing software 1651 included on a computer-readable medium 1606 to implement one or more functions described herein.

[0174] In a particular configuration of network entity 1600, processor 1604 may, in conjunction with communication and processing circuitry 1641 and / or transceiver 1610, determine a schedule associated with a resource configuration that enables a UE (e.g., UE 1300) to preferentially perform L1 measurements of reference signals from a non-serving cell. In this configuration, processor 1604 may also, in conjunction with communication and processing circuitry 1641 and / or transceiver 1610, communicate with the UE according to the schedule.

[0175] Various aspects of schedule restrictions for this particular configuration are envisioned. For example, it is envisioned that the schedule may restrict the UE from transmitting a set of communications (e.g., where the set of communications includes at least one of PUCCH communication, PUSCH communication, or SRS) during L1 measurements, and / or the schedule may restrict the UE from receiving a set of communications related to channel quality indicator (CQI) calculation (e.g., where the set of communications includes at least one of PDCCH communication, PDSCH communication, TRS, or CSI-RS) during L1 measurements.

[0176] In another aspect, it is envisioned that the schedule may restrict a time window between consecutive reference signals during which L1 measurements may be performed, where the time window is K1 symbols before a subsequent reference signal and K2 symbols after a previous reference signal. Here, it is also envisioned that K1 and K2 may be calculated in any of various ways. For example, processor 1604 may be configured to calculate K1 and K2 based on a tone spacing between data and at least one of a first reference signal from a serving cell or a second reference signal from a non-serving cell. Processor 1604 may also be configured to calculate K1 and K2 based on a time difference between receiving the first reference signal from the serving cell and receiving the second reference signal from the non-serving cell. In another aspect, processor 1604 is configured to calculate K1 and K2 based on an alignment between a transmission time of the first reference signal from the serving cell and a transmission time of the second reference signal from the non-serving cell. In yet another aspect, processor 1604 is configured to calculate K1 and K2 based on whether the L1 measurement is an inter-frequency measurement or an intra-frequency measurement.

[0177] Various examples of schedule restrictions that may be implemented by network entity 1600 are provided herein. For example, a first set of exemplary schedule restrictions is envisioned for L1-RSRP measurements.

[0178] In a first example of this first set, scheduling restrictions on L1-RSRP measurements due to L1-SINR measurements are envisioned. Here, there are no scheduling restrictions due to L1-SINR measurements performed based on CSI-RS for the following cases: 1) where CSI-RS is only used for L1-SINR measurements of CSI-RS-based CMR; 2) where CSI-RS is used for L1-SINR measurements of CSI-RS-based CMR plus CSI-RS-based ZP-IMR / NZP-IMR; and 3) where CSI-RS is used for L1-SINR measurements of CSI-RS-based CMR plus ZP-IMR, where CSI-RS is quasi-co-located (QCL) with the active TCI state for PDCCH / PDSCH and is not in a CSI-RS resource set with repeated activation. Otherwise, for all other cases: 1) for UEs that support FR2 power class 6 and are not configured with [highSpeedMeasFlagFR2-r17], and for UEs that do not support FR2 power class 6, it is expected that the UE will not transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / CSI-RS for tracking / CSI-RS for CQI on the CSI-RS of the L1-RSRP measurement symbol to be targeted for L1-SINR measurement; and 2) for UEs that support FR2 power class 6 and are configured with [highSpeedMeasFlagFR2-r17], it is expected that the UE will not transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / CSI-RS for tracking / CSI-RS for CQI on the symbol to be targeted for L1-SINR measurement and on one data symbol before and one data symbol after the symbol to be targeted for L1-SINR measurement. Here, it should be understood that when in-band carrier aggregation is performed, the scheduling restrictions on the serving cell for performing L1-SINR measurements may apply to all serving cells in this band on symbols that completely or partially overlap with the restricted symbols.

[0179] In a second example of this first set, scheduling restrictions are envisioned if the following conditions are met: 1) The UE has been notified of a system information update via paging; and 2) The gap between the PDCCH that the UE monitors (and provides the system information update) in the type 2-PDCCH CSS set and the PDCCH that the UE monitors in the type 0-PDCCH CSS set is greater than two time slots. Under these conditions, for the SSB and CORESET used for RMSI scheduling multiplexing mode 3, it is expected that the UE will receive the PDCCH and the corresponding PDSCH that the UE monitors in the type 0-PDCCH CSS set on the SSB symbols to be measured for L1-SINR measurement. Additionally, under these conditions, for the SSB and CORESET used for RMSI scheduling multiplexing mode 2, it is expected that the UE will receive the PDSCH corresponding to the PDCCH that the UE monitors in the type 0-PDCCH CSS set on the SSB symbols to be measured for L1-SINR measurement.

[0180] A second set of exemplary embodiments is envisioned for L1-SINR measurement. For example, a first example of this second set is envisioned for FR1, where no scheduling restrictions are implemented because L1-SINR measurement is performed on the SSB and CSI-RS is configured for L1-SINR measurement with the same SCS as the PDSCH / PDCCH in FR1.

[0181] In a second example of this second set, a specific implementation is envisioned for FR2. For this example, there are no scheduling restrictions due to L1-SINR measurements performed based on CSI-RS for the following cases: 1) where CSI-RS is only used for L1-SINR measurements of CSI-RS-based CMR; 2) where CSI-RS is used for L1-SINR measurements of CSI-RS-based CMR plus CSI-RS-based ZP-IMR / NZP-IMR; and 3) where CSI-RS is used for L1-SINR measurements of CSI-RS-based CMR plus ZP-IMR, where CSI-RS is quasi-co-located (QCL) with the active TCI state for PDCCH / PDSCH and is not in a CSI-RS resource set with repeated activation. Otherwise, for all other cases: 1) for UEs not configured with [highSpeedMeasFlagFR2-r17] that support FR2 power class 6, and for UEs that do not support FR2 power class 6, it is expected that the UE will not transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / CSI-RS for tracking / CSI-RS for CQI on the CSI-RS of the L1-RSRP measurement symbol to be used for L1-SINR measurement; and 2) for UEs that support FR2 power class 6 and are configured with [highSpeedMeasFlagFR2-r17], it is expected that the UE will not transmit PUCCH / PUSCH / SRS or receive PDCCH / PDSCH / CSI-RS for tracking / CSI-RS for CQI on the symbol to be used for L1-SINR measurement and on one data symbol before and one data symbol after the symbol to be used for L1-SINR measurement. Here, it should be understood that when in-band carrier aggregation is performed, the scheduling restrictions on the serving cell for performing L1-SINR measurements may apply to all serving cells in this band on symbols that fully or partially overlap with the restricted symbols.

[0182] In a third example of this second set, scheduling restrictions are envisioned if the following conditions are met: 1) The UE has been notified of a system information update via paging; and 2) The gap between the PDCCH that the UE monitors (and provides the system information update) in the type 2-PDCCH CSS set and the PDCCH that the UE monitors in the type 0-PDCCH CSS set is greater than two time slots. Under these conditions, for the SSB and CORESET used for RMSI scheduling multiplexing mode 3, it is expected that the UE will receive the PDCCH and the corresponding PDSCH that the UE monitors in the type 0-PDCCH CSS set on the SSB symbol to be measured for L1-SINR measurement. Additionally, under these conditions, for the SSB and CORESET used for RMSI scheduling multiplexing mode 2, it is expected that the UE will receive the PDSCH corresponding to the PDCCH that the UE monitors in the type 0-PDCCH CSS set on the SSB symbol to be measured for L1-SINR measurement.

[0183] Next, referring to Figure 17 , a flowchart is provided that illustrates an exemplary wireless communication method 1700 according to some aspects of the present disclosure. As described herein, in certain specific implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for the implementation of all examples. In some examples, method 1700 may be performed by Figure 16 the network entity 1600 illustrated in

[0184] (e.g., a gNB or a base station, including a base station operable in an O-RAN environment). In some examples, method 1700 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0185] Additionally, at block 1704, the network entity 1600 may communicate with the UE according to the scheduling. In one aspect, the process of block 1704 may be implemented by a component for communicating with the UE, and in a particular aspect, the component may be implemented by the processor 1604, the communication and processing circuit 1641, and the transceiver 1610 or their equivalents.

[0186] It is further noted that the present disclosure may include the following additional aspects of the present disclosure.

[0187] Aspect 1: A UE, the UE includes a transceiver, a memory, and a processor coupled to the transceiver and the memory, wherein the processor is configured to: detect a first reference signal and a second reference signal, wherein the first reference signal has resources overlapping with the second reference signal, and wherein at least one of the first reference signal or the second reference signal comes from a non-serving cell; determine a context associated with at least one of the first reference signal or the second reference signal; and perform L1 measurements on at least one of the first reference signal or the second reference signal according to a priority ranking associated with the context.

[0188] Aspect 2: The UE according to Aspect 1, wherein the priority ranking associated with the context is based on whether the L1 measurement is an inter-frequency measurement or an intra-frequency measurement.

[0189] Aspect 3: The UE according to Aspect 1 or 2, wherein the priority ranking associated with the context is based on whether the overlapping resources have the same SCS.

[0190] Aspect 4: The UE according to any one of Aspects 1 to 3, wherein the priority ranking associated with the context is based on the UE capability corresponding to how many of the overlapping resources the UE can measure at one time.

[0191] Aspect 5: The UE according to any one of Aspects 1 to 4, wherein the priority ranking associated with the context is based on the UE capability corresponding to how many cell reference signals the UE can measure at one time.

[0192] Aspect 6: The UE according to any one of Aspects 1 to 5, wherein the priority ranking associated with the context is based on the frequency bands from which the first reference signal and the second reference signal are detected.

[0193] Aspect 7: The UE according to any one of Aspects 1 to 6, wherein the priority ranking associated with the context is based on the corresponding reference signal types associated with the first reference signal and the second reference signal.

[0194] Aspect 8: The UE according to any one of Aspects 1 to 7, wherein the priority ranking associated with the context is based on the type of L1 measurement to be performed.

[0195] Aspect 9: The UE according to any one of Aspects 1 to 8, wherein the priority ranking associated with the context is based on the purpose of the overlapping resources.

[0196] Aspect 10: The UE according to any one of Aspects 1 to 9, wherein the prioritization associated with the context is based on the PCI associated with at least one of the first reference signal or the second reference signal.

[0197] Aspect 11: A method for wireless communication in a UE, the method comprising: detecting a first reference signal and a second reference signal, wherein the first reference signal has resources overlapping with the second reference signal, and wherein at least one of the first reference signal or the second reference signal is from a non-serving cell; determining a context associated with at least one of the first reference signal or the second reference signal; and performing L1 measurements on at least one of the first reference signal or the second reference signal according to a prioritization associated with the context.

[0198] Aspect 12: A network entity configured for wireless communication, the network entity comprising a memory and a processor coupled to the memory, the processor being configured to: determine a scheduling associated with a resource configuration, wherein the resource configuration enables the UE to preferentially perform L1 measurements on reference signals from non-serving cells; and communicate with the UE according to the scheduling.

[0199] Aspect 13: The network entity according to Aspect 12, wherein the scheduling restricts the UE from transmitting a communication set during the L1 measurement.

[0200] Aspect 14: The network entity according to any one of Aspects 12 to 13, wherein the scheduling restricts the UE from receiving a communication set related to CQI calculation during the L1 measurement.

[0201] Aspect 15: The network entity according to any one of Aspects 12 to 14, wherein the scheduling restricts a time window between consecutive reference signals during which the L1 measurement can be performed, and wherein the time window is K1 symbols before a subsequent reference signal and K2 symbols after a previous reference signal.

[0202] Aspect 16: The network entity according to any one of Aspects 12 to 15, wherein the processor is configured to calculate K1 and K2 based on a tone interval between data and at least one of a first reference signal from a serving cell or a second reference signal from the non-serving cell.

[0203] Aspect 17: The network entity according to any one of Aspects 12 to 16, wherein the processor is configured to calculate K1 and K2 based on a time difference between receiving a first reference signal from a serving cell and receiving a second reference signal from the non-serving cell.

[0204] Aspect 18: The network entity according to any one of Aspects 12 to 17, wherein the processor is configured to calculate K1 and K2 based on the alignment between the transmission time of a first reference signal from a serving cell and the transmission time of a second reference signal from the non-serving cell.

[0205] Aspect 19: The network entity according to any one of Aspects 12 to 18, wherein the processor is configured to calculate K1 and K2 based on whether the L1 measurement is an inter-frequency measurement or an intra-frequency measurement.

[0206] Aspect 20: A UE, the UE comprising a transceiver, a memory, and a processor coupled to the transceiver and the memory, wherein the processor is configured to: communicate with a gNb using one or more TCI states, wherein each of the one or more TCI states is associated with a corresponding CORESET pool of one or more CORESETs, and wherein each CORESET pool corresponds to a TRP; identify one or more sets of BFD reference signals, wherein the one or more sets of BFD reference signals are explicitly identified via configuration signaling from the gNb or implicitly identified based on the one or more TCI states in the absence of the configuration signaling; and monitor the one or more sets of BFD reference signals to facilitate detection of a beam failure event.

[0207] Aspect 21: The UE according to Aspect 20, wherein the processor is configured to identify a single set of BFD reference signals based on indication signaling received from the gNb corresponding to a single TCI state, and wherein the processor is further configured to associate the single set of BFD reference signals with each TRP of the cell.

[0208] Aspect 22: The UE according to Aspect 20 or 21, wherein the processor is configured to identify multiple sets of BFD reference signals based on indication signaling received from the gNb corresponding to multiple TCI states, and wherein the processor is further configured to associate the multiple sets of BFD reference signals with corresponding multiple TRPs of the cell.

[0209] Aspect 23: The UE according to Aspect 22, wherein the processor is configured to detect the beam failure event at the TRP level.

[0210] Aspect 24: The UE according to Aspect 22, wherein the processor is configured to detect the beam failure event at the cell level.

[0211] Aspect 25: The UE according to any one of aspects 20 to 24, wherein the processor is configured to identify a plurality of sets of BFD reference signals based on indication signaling corresponding to a single TCI state received from the gNb, and wherein the processor is further configured to implicitly select a plurality of sets of BFD reference signals based on the single TCI state and a previously indicated TCI state.

[0212] Aspect 26: The UE according to any one of aspects 20 to 25, wherein the processor is configured to identify a plurality of sets of BFD reference signals when the UE has not received indication signaling of a TCI state.

[0213] Aspect 27: The UE according to any one of aspects 20 to 26, wherein the processor is configured to: identify a plurality of sets of BFD reference signals based on an active TCI code point including a plurality of TCI states; select a TCI code point having the lowest identifier among all TCI code points having two or more TCI states; and use the two or more TCI states included in the selected TCI code point to identify the BFD reference signals to be monitored.

[0214] Aspect 28: The UE according to any one of aspects 20 to 27, wherein the one or more sets of BFD reference signals are source reference signals associated with the one or more TCI states.

[0215] Aspect 29: The UE according to any one of aspects 20 to 28, wherein the processor is configured to receive a scheduling command for communication assignment via a specific CORESET pool, and wherein the processor is further configured to select a TCI state associated with the specific CORESET pool for the communication assignment from the one or more TCI states.

[0216] Aspect 30: The UE according to aspect 29, wherein the communication assignment is of a type corresponding to one of the following: SP / AP CSI-RS for tracking reference signals, channel state feedback, beam management, SP / AP SRS for antenna switching, codebook-based transmission, non-codebook-based transmission, PRACH based on PDCCH commands, SP / AP PUSCH, or SP / AP PUCCH.

[0217] Certain aspects of a wireless communication network have been presented with reference to example embodiments. As will be readily understood by those skilled in the art, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0218] For example, aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). Aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing Institute of Electrical and Electronics Engineers (IEEE) standards, such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wide Band (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the particular application and the overall design constraints imposed on the system.

[0219] Within this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration." Any particular implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or superior to other aspects of the disclosure. Similarly, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object has never physically contacted the second object directly. The term "circuitry" is used broadly, and is intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors are connected and configured to perform the functions described herein, without limitation as to the type of electronic circuitry) and software implementations of information and instructions (where these information and instructions are executed by a processor to perform the functions described herein). As used herein, the term "determine" can include a variety of actions. For example, "determine" can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, resolving, selecting, choosing, establishing, receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc.

[0220] Figures 1 to 17 One or more of the illustrated components, steps, features, and / or functions may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 17The apparatus, device, and / or component illustrated in any of the figures herein may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0221] It should be understood that the specific order or hierarchy of steps in the methods disclosed herein is illustrative of example processes. It should be understood that based on design preferences, the specific order or hierarchy of steps in these methods may be rearranged. The appended method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented, unless specifically recited herein.

[0222] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein but are to be accorded the full scope consistent with the language of the claims, where the reference to an element in the singular is not intended to mean "one and only one" but rather "one or more" unless explicitly stated otherwise. The term "some," unless specifically stated otherwise, means one or more. A phrase referring to "at least one" of a list of items means any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. A user equipment (UE), the user equipment (UE) comprises: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor is configured to: detect a first reference signal and a second reference signal, wherein the first reference signal has resources overlapping with the second reference signal, and wherein at least one of the first reference signal or the second reference signal is from a non-serving cell; determine a context associated with at least one of the first reference signal or the second reference signal; and perform a layer 1 (L1) measurement of at least one of the first reference signal or the second reference signal according to a priority order associated with the context.

2. The UE according to claim 1, wherein the priority order associated with the context is based on whether the L1 measurement is an inter-frequency measurement or an intra-frequency measurement.

3. The UE according to claim 1, wherein the priority order associated with the context is based on whether the overlapping resources have the same subcarrier spacing (SCS).

4. The UE according to claim 1, wherein the priority order associated with the context is based on the UE capability corresponding to how many of the overlapping resources the UE can measure at one time.

5. The UE according to claim 1, wherein the priority order associated with the context is based on the UE capability corresponding to how many cell reference signals the UE can measure at one time.

6. The UE according to claim 1, wherein the priority order associated with the context is based on the frequency band from which the first reference signal and the second reference signal are detected.

7. The UE according to claim 1, wherein the priority order associated with the context is based on the corresponding reference signal type associated with the first reference signal and the second reference signal.

8. The UE according to claim 1, wherein the priority order associated with the context is based on the type of L1 measurement to be performed.

9. The UE according to claim 1, wherein the priority order associated with the context is based on the purpose of the overlapping resources.

10. The UE according to claim 1, wherein the priority order associated with the context is based on the physical cell identifier (PCI) associated with at least one of the first reference signal or the second reference signal.

11. A method for wireless communication at a user equipment (UE), the method comprises: detecting a first reference signal and a second reference signal, wherein the first reference signal has resources overlapping with the second reference signal, and wherein at least one of the first reference signal or the second reference signal is from a non-serving cell; determining a context associated with at least one of the first reference signal or the second reference signal; and performing a layer 1 (L1) measurement of at least one of the first reference signal or the second reference signal according to a priority order associated with the context.

12. A network entity configured for wireless communication, the network entity comprising: a memory; and a processor coupled to the memory, the processor being configured to: determine a scheduling associated with a resource configuration, wherein the resource configuration enables a user equipment (UE) to preferentially perform layer 1 (L1) measurements of reference signals from a non-serving cell; and communicate with the UE according to the scheduling.

13. The network entity according to claim 12, wherein the scheduling restricts the UE from transmitting a set of communications during the L1 measurement.

14. The network entity according to claim 12, wherein the scheduling restricts the UE from receiving a set of communications related to channel quality indicator (CQI) calculation during the L1 measurement.

15. The network entity according to claim 12, wherein the scheduling restricts a time window between consecutive reference signals during which the L1 measurement can be performed, and wherein the time window is K1 symbols before a subsequent reference signal and K2 symbols after a previous reference signal.

16. The network entity according to claim 15, wherein the processor is configured to calculate K1 and K2 based on a tone interval between data and at least one of a first reference signal from a serving cell or a second reference signal from the non-serving cell.

17. The network entity according to claim 15, wherein the processor is configured to calculate K1 and K2 based on a time difference between receiving a first reference signal from a serving cell and receiving a second reference signal from the non-serving cell.

18. The network entity according to claim 15, wherein the processor is configured to calculate K1 and K2 based on an alignment between a transmission time of a first reference signal from a serving cell and a transmission time of a second reference signal from the non-serving cell.

19. The network entity according to claim 15, wherein the processor is configured to calculate K1 and K2 based on whether the L1 measurement is an inter-frequency measurement or an intra-frequency measurement.

20. A user equipment (UE), the user equipment (UE) comprising: a transceiver; a memory; and a processor coupled to the transceiver and the memory, wherein the processor is configured to: communicate with a gNodeB (gNb) using one or more transmission configuration indicator (TCI) states, wherein each of the one or more TCI states is associated with a corresponding CORESET pool of one or more control resource sets (CORESETs), and wherein each CORESET pool corresponds to a transmit receive point (TRP); identify one or more sets of beam failure detection (BFD) reference signals, wherein the one or more sets of BFD reference signals are explicitly identified via configuration signaling from the gNb, or implicitly identified based on the one or more TCI states in the absence of the configuration signaling; and monitor the one or more sets of BFD reference signals to facilitate detection of a beam failure event.

21. The UE according to claim 20, wherein the processor is configured to identify a single set of BFD reference signals based on indication signaling received from the gNb corresponding to a single TCI state, and wherein the processor is further configured to associate the single set of BFD reference signals with each TRP of the cell.

22. The UE according to claim 20, wherein the processor is configured to identify multiple sets of BFD reference signals based on indication signaling received from the gNb corresponding to multiple TCI states, and wherein the processor is further configured to associate the multiple sets of BFD reference signals with the corresponding multiple TRPs of the cell.

23. The UE according to claim 22, wherein the processor is configured to detect the beam failure event at the TRP level.

24. The UE according to claim 22, wherein the processor is configured to detect the beam failure event at the cell level.

25. The UE according to claim 20, wherein the processor is configured to identify multiple sets of BFD reference signals based on indication signaling received from the gNb corresponding to a single TCI state, and wherein the processor is further configured to implicitly select multiple sets of BFD reference signals based on the single TCI state and a previously indicated TCI state.

26. The UE according to claim 20, wherein the processor is configured to identify multiple sets of BFD reference signals when the UE has not received indication signaling of the TCI state.

27. The UE according to claim 20, wherein the processor is configured to: identify multiple sets of BFD reference signals based on an active TCI code point including multiple TCI states; select a TCI code point with the lowest identifier among all TCI code points having two or more TCI states; and use the two or more TCI states included in the selected TCI code point to identify the BFD reference signals to be monitored.

28. The UE according to claim 20, wherein the one or more sets of BFD reference signals are source reference signals associated with the one or more TCI states.

29. The UE according to claim 20, wherein the processor is configured to receive a scheduling command for communication assignment via a specific CORESET pool, and wherein the processor is further configured to select a TCI state associated with the specific CORESET pool for the communication assignment from the one or more TCI states.

30. The UE according to claim 29, wherein the communication assignment is of a type corresponding to one of the following: semi-persistent / aperiodic (SP / AP) channel state information reference signal (CSI-RS) for tracking reference signals, channel state feedback, beam management, SP / AP sounding reference signal (SRS) for antenna switching, codebook-based transmission, non-codebook-based transmission, physical random access channel (PRACH) based on a physical downlink control channel (PDCCH) command, SP / AP physical uplink shared channel (PUSCH), or SP / AP physical uplink control channel (PUCCH).

Images