Paging early indication response

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can receive, from a network entity, an indication to configure a paging early indication (PEI) response to one or more of: a subset of UEs; a paging occasion; or the beam direction. The UE can receive a PEI from the network entity. The UE can send the PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response. The UE can receive a paging indication from the network entity and during the paging occasion based at least in part on the PEI response. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 812,346, entitled “PAGING EARLY INDICATION RESPONSES,” filed on July 13, 2022, which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for Paging Early Indication (PEI) responses. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network entities (e.g., base stations) that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a network entity via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network entity to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network entity.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] In some specific implementations, an apparatus for wireless communication at a user equipment (UE) includes a memory and one or more processors, which are coupled to the memory and configured to: receive an indication from a network entity to configure a paging early indication (PEI) response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction; receive the PEI from the network entity, send a PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response; and receive a paging indication from the network entity and during the paging occasion based at least in part on the PEI response.

[0008] In some specific implementations, an apparatus for wireless communication at a network entity includes a memory and one or more processors, which are coupled to the memory and configured to: send an indication to a UE to configure a PEI response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction; send a PEI to the UE, receive a PEI response from the UE based at least in part on the PEI and the indication to configure the PEI response; and send a paging indication to the UE and during the paging occasion based at least in part on the PEI response.

[0009] In some specific implementations, a method of wireless communication performed by a UE includes: receiving an indication from a network entity to configure a PEI response for one or more of the following: a UE subgroup paging occasion; or a beam direction; receiving a PEI from the network entity; sending a PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response; and receiving a paging indication from the network entity and during the paging occasion based at least in part on the PEI response.

[0010] In some specific implementations, a method of wireless communication performed by a network entity includes: sending an indication to a UE to configure a PEI response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction; sending a PEI to the UE; receiving a PEI response from the UE based at least in part on the PEI and the indication to configure the PEI response; and sending a paging indication to the UE and during the paging occasion based at least in part on the PEI response.

[0011] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive an indication from a network entity to configure a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction; receive a PEI from the network entity; send a PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response; and receive a paging indication from the network entity and during a paging occasion based at least in part on the PEI response.

[0012] In some specific implementations, a non-transitory computer-readable medium storing an instruction set for wireless communication includes one or more instructions that, when executed by one or more processors of a network entity, cause the network entity to: send an indication to a UE to configure a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction; send a PEI to the UE; receive a PEI response from the UE based at least in part on the PEI and the indication to configure the PEI response; and send a paging indication to the UE and during the paging occasion based at least in part on the PEI response.

[0013] In some specific implementations, an apparatus for wireless communication includes: a component for performing the following operations: receiving an indication from a network entity to configure a PEI response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction; receiving a PEI from the network entity; a component for sending a PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response; and a component for receiving a paging indication from the network entity and during a paging occasion based at least in part on the PEI response.

[0014] In some specific implementations, an apparatus for wireless communication includes: a component for sending an indication to a UE to configure a PEI response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction; a component for sending a PEI to the UE; a component for receiving a PEI response from the UE based at least in part on the PEI and the indication for configuring the PEI response; and a component for sending a paging indication to the UE and during the paging occasion based at least in part on the PEI response.

[0015] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, network entities, base stations, wireless communication devices, and / or processing systems as substantially described herein with reference to and as illustrated in the accompanying figures and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of a decomposed network entity architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of a Paging Early Indication (PEI) according to the present disclosure.

[0023] Figure 5 to Figure 6 is a diagram illustrating an example associated with a PEI response according to the present disclosure.

[0024] Figures 7 and 8 is a diagram illustrating an example process associated with a PEI response according to the present disclosure.

[0025] Figures 9 and 10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0026] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0027] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0028] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0029] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network entities 110 (shown as network entity 110a, network entity 110b, network entity 110c, and network entity 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The network entity 110 is an entity that communicates with the UE 120. The network entity 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each network entity 110 may provide communication coverage for a specific geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network entity 110 and / or a network entity subsystem serving the coverage area, depending on the context in which the term is used.

[0030] The network entity 110 may provide communication coverage for macro cells, pico cells, femto cells, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro base station. A base station for a pico cell may be referred to as a pico base station. A base station for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , the network entity 110a may be a macro base station for the macro cell 102a, the network entity 110b may be a pico base station for the pico cell 102b, and the BS network entity may be a femto base station for the femto cell 102c. A base station may support one or more (e.g., three) cells.

[0031] In some aspects, the term "network entity" (e.g., network entity 110) may refer to a clustered base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "network entity" may refer to a device configured to perform one or more functions (such as the functions described herein in conjunction with network entity 110). In some aspects, the term "network entity" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "network entity" may refer to any one or more of those different devices. In some aspects, the term "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "network entity" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0032] In some examples, cells may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network entity 110 (e.g., a mobile base station). In some examples, the network entities 110 may be interconnected with each other and / or with one or more other network entities 110 or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.

[0033] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network entity 110d (e.g., a relay base station) can communicate with a network entity 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the network entity 110a and the UE 120d. The network entity 110 that relays communication may be referred to as a relay station, a relay base station, a relay, etc.

[0034] The wireless network 100 may be a heterogeneous network including different types of network entities 110, such as macro base stations, pico base stations, femto base stations, relay base stations, TRPs, RUs, etc. These different types of network entities 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0035] The network controller 130 may be coupled to or in communication with a set of network entities 110 and may provide coordination and control for the network entities 110. The network controller 130 may communicate with the network entities 110 via backhaul communication links. The network entities 110 may also communicate directly or indirectly with each other via wireless or wired backhaul communication links.

[0036] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0037] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network entity, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly (e.g., without using network entity 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network entity 110.

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0041] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0042] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, a UE (e.g., UE 120) may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may receive an indication from a network entity to configure a paging early indication (PEI) response for one or more of: a UE subgroup; a paging occasion; or a beam direction; receive a PEI from a network entity; send a PEI response to the network entity based at least in part on the PEI and an indication to configure the PEI response; and receive a paging indication from the network entity and during the paging occasion based at least in part on the PEI response. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0044] In some aspects, a network entity (e.g., network entity 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send an indication to a UE to configure a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction; send a PEI to the UE; receive a PEI response from the UE based at least in part on the PEI and the indication to configure the PEI response; and send a paging indication to the UE and during the paging occasion based at least in part on the PEI response. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0046] Figure 2 2 is a diagram illustrating an example 200 of a network entity 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network entity 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0047] At the network entity 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network entity 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network entity 110 and / or other network entities 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network entity 110 via the communication unit 294.

[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0051] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network entity 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform operations described herein (eg, with reference to Figures 5 to 10 ) or any aspect of any of the methods described herein.

[0052] At the network entity 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network entity 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network entity 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity 110 may include a modulator and a demodulator. In some examples, the network entity 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be configured by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to FIG. 2 ). Figures 5 to 10 ) or any aspect of any of the methods described herein.

[0053] The controller / processor 240 of the network entity 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the network entity 110 may perform one or more techniques associated with PEI response, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network entity 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of may perform or direct e.g. Figure 7 The process 700 Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network entity 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network entity 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network entity 110 to perform or direct, for example, Figure 7 The process 700 Figure 8 The process 800 of and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0054] In some aspects, a UE (e.g., UE 120) includes: a component for receiving an indication of configuring a PEI response for one or more of the following from a network entity: a UE subgroup; a paging occasion; or a beam direction; a component for receiving a PEI from a network entity; a component for sending a PEI response to a network entity based at least in part on the PEI and the indication of configuring the PEI response; and / or a component for receiving a paging indication from a network entity and during a paging occasion based at least in part on the PEI response. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0055] In some aspects, a network entity (e.g., network entity 110) includes: means for sending an indication to a UE configuring a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction; means for sending a PEI to the UE; means for receiving a PEI response from the UE based at least in part on the PEI and the indication configuring the PEI response; and / or means for sending a paging indication to the UE and during the paging occasion based at least in part on the PEI response. In some aspects, means for the network entity to perform operations described herein may include, for example, one or more of the following: a communications manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0056] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0057] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0058] Figure 3 is a diagram illustrating an example 300 of a decomposed network entity architecture according to the present disclosure.

[0059] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station (e.g., network entity 110) or one or more units (or one or more components) that perform network entity functionality may be implemented in an aggregated or decomposed architecture. For example, a network entity (such as a Node B (NB), an eNB, an NR BS, a 5G NB, an access node (AP), a TRP, a cell, etc.) may be implemented as an aggregated base station (also referred to as a standalone BS or a monolithic BS) or a decomposed base station.

[0060] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, namely a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0061] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an IAB network, an O-RAN (such as a network configuration sponsored by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0062] Figure 3 The decomposed network entity architecture shown in FIG. 1 may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. The RU 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0063] Each of these units (e.g., CU 310, DU 330, RU 340), as well as near-RT RIC 325, non-RTRIC 315, and SMO framework 305 may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send 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, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0064] In some aspects, CU 310 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 be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0065] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium 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.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may further 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 DU 330 or with control functions hosted by CU 310.

[0066] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts 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, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of communicating with the control and user planes of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0067] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0068] The non-RT RIC 315 may be configured to include logic functions that 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 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0069] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0070] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0071] Figure 4 is a diagram illustrating an example 400 of a PEI according to the present disclosure.

[0072] As shown by reference numeral 402, the network entity may perform synchronization signal block (SSB) scanning. During SSB scanning, the network entity may use multiple beams to transmit multiple SSBs. The number of beams may be equal to the number of SSBs actually transmitted.

[0073] As shown by reference numeral 404, the network entity may transmit multiple PEIs using multiple beams. The network entity may transmit the multiple PEIs to one or more UEs (eg, a subgroup of UEs). The network entity may transmit the multiple PEIs during a PEI opportunity.

[0074] In some aspects, the PEI may be a PEI based on a physical downlink control channel (PDCCH). The PEI may be associated with a control resource set (CORESET) (e.g., CORESET#0) or a common CORESET configured in a system information block type 1 (SIB1). The PEI may be associated with a dedicated search space. The PEI payload size may be configured by a network entity, and the PEI payload size may not be greater than the payload size of the paging indication. When subgroups are not configured, the total number of bits used for the PEI field may be represented as POnumPerPEI, and when subgroups are configured, the total number of bits used for the PEI field may be (POnumPerPEI×subgroupsNumPerPO), where POnumPerPEI=1, 2, 4, 8, and the maximum value subgroupsNumPerPO=8. There may be a one-to-one mapping between the PEI PDCCH monitoring opportunity within the paging occasion and the paging PDCCH monitoring opportunity. The location of the PEI PDCCH monitoring opportunity may be configured via a SIB (such as SIB1). The location may be based at least in part on a reference point, which may be configured by a frame level offset from a first one of the associated paging frames.The symbol level offset from the reference point may indicate the location of the first PEI PDCCH monitoring opportunity.

[0075] As shown in the figure numeral 406, the network entity may perform monitoring during one or more PEI response opportunities. During one of the PEI response opportunities, the network entity may receive a PEI response from one of the multiple UEs. In other words, the network entity may monitor the PEI response within the configured PEI response opportunity. The UE may send a PEI response based at least in part on receiving the PEI from the network entity. The UE may send the PEI response using a transmit beam, which may correspond to one of the multiple beams used by the network entity. The UE may send the PEI response so that the network entity can locate the UE that may be idle / inactive at the beam / cell level.

[0076] As shown in the figure 408, when the network entity detects a PEI response received from the UE, the network entity may send a paging indication during a paging occasion. The network entity may send the paging indication via a PDCCH or a physical downlink shared channel (PDSCH). The paging indication may also be referred to as a paging PDCCH / PDSCH. The network entity may send the paging indication using a transmit beam, which may correspond to a transmit beam used by the UE to send the PEI response. In contrast to using multiple beams to send the paging indication, the network entity may use only one transmit beam to send the paging indication. In other words, the network entity may use beam information obtained by the network entity during PEI response detection to reduce beam scanning for the paging indication. Therefore, the network entity may save signaling overhead.

[0077] The UE may receive the PEI from the network entity, and the UE may send a PEI response to the network entity based at least in part on receiving the PEI. The UE may send the PEI response before the network entity sends the paging indication. Thus, as opposed to using multiple beams to send the paging indication, the network entity may use beam information obtained via detecting the PEI response to intelligently send the paging indication using a specific beam corresponding to the UE.

[0078] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0079] A network entity (e.g., network entity 110) may send a PEI to a UE, and the UE may send a PEI response to the network entity based at least in part on receiving the PEI. The network entity may send a paging indication to the UE based at least in part on the PEI response received from the UE. However, the PEI may not configure the UE to send a PEI response based at least in part on certain criteria. In addition, some UEs may support PEI responses, while other UEs may not support PEI responses. In addition, sending a PEI response by the UE may save resources at the network entity, but may result in increased signaling to the UE, which may consume additional power at the UE.

[0080] In various aspects of the techniques and apparatus described herein, a UE may receive an indication of configuring a PEI response for a UE subgroup, a paging occasion, and / or a beam direction from a network entity. The UE may receive a PEI from a network. The PEI may be configured to dynamically activate or deactivate a PEI response using a single bit flag. The PEI may be configured to dynamically activate or deactivate a PEI response for a UE subgroup, a paging occasion, and / or a beam direction using a bitmap. The PEI response may be semi-statically configured for a UE subgroup, a paging occasion, and / or a beam direction via system information or dedicated RRC signaling. In some aspects, the UE may send a capability signaling indicating that the UE supports a PEI response. In some aspects, the UE may receive a tracking reference signal (TRS) or a channel state information reference signal (CSI-RS) from a network entity based at least in part on the network entity receiving a PEI response, wherein the TRS or CSI-RS may improve the UE's reception of a paging indication, thereby motivating the UE to spend resources sending a PEI response to a network entity. Thus, the UE may be configured to send a PEI response based at least in part on certain criteria (eg, UE subgroup, paging occasion, and / or beam direction).

[0081] Figure 5 is a diagram illustrating an example 500 associated with a PEI response according to the present disclosure. Figure 5 As shown in , example 500 includes communications between a UE (eg, UE 120) and a network entity (eg, network entity 110). In some aspects, the UE and the network entity may be included in a wireless network (such as wireless network 100).

[0082] As shown in the figure numeral 502, the UE may receive an indication from a network entity to configure a PEI response for a UE subgroup, a paging occasion, and / or a beam direction. The UE may receive the PEI via a PDCCH. The PEI may be configured to dynamically activate or deactivate the PEI response using a single bit flag. The PEI may be configured to dynamically activate or deactivate the PEI response for a UE subgroup, a paging occasion, and / or a beam direction using a bitmap. The PEI response may be semi-statically configured for a UE subgroup, a paging occasion, and / or a beam direction via system information or dedicated RRC signaling.

[0083] In some aspects, a network entity may send a PEI PDCCH that dynamically activates / deactivates a PEI response, for example, by indicating a single bit flag that activates / deactivates a PEI response. A network entity may send a PEI PDCCH to one or more UEs associated with one or more (e.g., one or more) UE subgroups. A network entity may activate / deactivate a PEI response for one or more UE subgroups, which may enable / disable a PEI response from one or more UEs associated with one or more UE subgroups. A network entity may activate / deactivate a PEI response within one or more associated paging occasions. A PEI PDCCH may indicate one or more bitmaps to indicate support for a PEI response for a subgroup and / or paging occasion. A PEI response may be activated / deactivated for one or more beam directions. In order to support beam-specific availability of a PEI response, a PEI PDCCH sent in one beam direction may indicate a PEI response bitmap that applies only to that beam direction.

[0084] In some aspects, the network entity may configure the PEI response in a semi-static manner. The network entity may configure the PEI response via system information or via dedicated RRC signaling. The network entity may semi-statically configure the PEI response for one or more UE subgroups, one or more paging occasions, and / or one or more beam directions.

[0085] In some aspects, the network entity may be based at least in part on the hierarchical indication. For example, up to eight UE subgroups may be RRC configured. The network entity may configure four UE subgroups via RRC signaling to support PEI responses. The PEI PDCCH may dynamically activate / deactivate PEI responses for the four UE subgroups.

[0086] In some aspects, the PEI may be carried via the PDCCH (eg, downlink control information (DCI) formats 2-7). The PDCCH may carry the PEI for up to 8 paging occasions and for each paging occasion, the PDCCH may carry the PEI for up to 8 UE subgroups.

[0087] As indicated by reference numeral 504, the UE may send capability signaling to the network entity indicating that the UE supports PEI responses. It is contemplated that the UE monitors the PEI and sends a PEI response based at least in part on the capability signaling.

[0088] In some aspects, legacy UEs may not support PEI responses, and in this case, the paging PDCCH / PDSCH for the legacy UEs should still be beam scanned (e.g., the paging PDCCH / PDSCH should be sent on multiple beams rather than on a specific beam corresponding to the PEI response).

[0089] In some aspects, a UE (e.g., a non-legacy UE) may indicate to a network entity an optional capability to support PEI responses, and the network may separate these UEs from legacy UEs. In other words, based at least in part on capability signaling, the network entity may separate UEs that support PEI responses from legacy UEs that do not support PEI responses. The network entity may determine different UE subgroups, where the subgroups of UEs (e.g., non-legacy UEs) may be different from the subgroups of legacy UEs (or legacy subgroups). The network entity may send paging PDCCH / PDSCH in a beam scanning manner for a subgroup of legacy UEs. The network entity may send paging PDCCH / PDSCH using a specific beam (without beam scanning) for a subgroup of UEs. In addition, the network entity may configure separate PEIs (e.g., different PEI paging monitoring opportunities and / or radio network temporary identifiers (RNTIs)) for subgroups of UEs.

[0090] In past methods, the UE may determine whether to monitor PEI based at least in part on the UE specific implementation. When the UE determines not to monitor PEI, the UE may be expected to monitor paging occasions associated with the UE. However, in some aspects, when the UE indicates support for PEI and PEI responses, the UE may be expected to monitor PEI and send a PEI response after receiving the PEI. When the UE does not send a PEI response, the UE may not receive a paging indication from a network entity because the network entity may not be able to obtain beam information associated with the PEI response. When the network entity supports multiple paging attempts, the UE may receive a paging indication, but the UE may experience a delay in receiving the paging indication.

[0091] The UE may send a PEI response to the network entity based at least in part on the PEI, as indicated by reference numeral 506. The UE may send the PEI response based at least in part on the PEI, an indication to configure the PEI response, and / or capability signaling.

[0092] As shown in the figure 508, the UE may receive a TRS or CSI-RS from a network entity before or after the paging occasion. The TRS or CSI-RS may be triggered at least in part based on the network entity receiving a PEI response. In some aspects, the TRS may be an aperiodic TRS or a periodic TRS. The TRS configuration associated with the TRS may be based at least in part on the RRC configuration. The TRS may be a public TRS or a dedicated TRS. The PEI may indicate whether the public TRS is available, whether the dedicated TRS is supported, or whether the dedicated TRS is available. The dedicated TRS may be associated with a UE-specific, beam-specific, or UE subgroup-specific validity duration. In some aspects, the CSI-RS may be an aperiodic CSI-RS or a periodic CSI-RS. The CSI-RS may be a public CSI-RS or a dedicated CSI-RS. The CSI-RS may be associated with repetition. The PEI may indicate whether the public CSI-RS is available, whether the dedicated CSI-RS is supported, or whether the dedicated CSI-RS is available. A dedicated CSI-RS may be associated with a UE-specific, beam-specific, or UE subgroup-specific validity duration.

[0093] In past versions of NR, TRS may be supported for UEs in idle / inactive mode to reduce UE power consumption. TRS may be used for time and frequency synchronization. No dedicated TRS may be configured for UEs in idle / inactive mode. The network may configure the TRS used by connected mode UEs to UEs in idle / inactive mode. TRS may be periodic (e.g., only periodic TRS may be supported and non-periodic TRS may not be supported). TRS may achieve power savings due to increased opportunities for tracking loop updates and / or longer sleep durations for UEs. The network entity may signal the SIB to provide the configuration of TRS. Layer 1 (L1) signaling may indicate whether TRS is sent at the configured opportunity. TRS availability information may be carried by both paging PDCCH and PEI. TRS availability information may be based at least in part on a bitmap in DCI, where up to six bits may be used for the bitmap. In the TRS resource set configuration, a group ID may be provided, where the group ID value may be mapped to a bit in the TRS availability indication field. A network-configured validity duration may be supported for TRS availability indication signaling, wherein the availability information may remain valid during the validity duration. In addition, TRS may be quasi-co-located with the transmitted SSB.

[0094] In some aspects, the PEI response sent by the UE may result in energy savings at the network entity because the network entity may not need to use multiple beams to send the paging indication, but the network entity may use a beam corresponding to the beam associated with the PEI response to send the paging indication. However, the energy savings at the network entity may cause the UE to consume additional power because the UE must send the PEI response to the network entity. Therefore, the network entity may incentivize the UE to implement and use the PEI response feature.

[0095] In some aspects, a network entity may send a dedicated TRS to a UE based at least in part on the UE sending a PEI response to the network entity. The network entity may send the dedicated TRS before (or after) a paging occasion. The dedicated TRS may improve power consumption of the UE, and the dedicated TRS may improve reception of paging indications during paging occasions. The sending of the dedicated TRS may be triggered by the reception of a PEI response. The dedicated TRS that may be triggered by a PEI response may be aperiodic or periodic. The TRS configuration associated with the dedicated TRS may be RRC configured, or the TRS configuration may be configured based at least in part on system information.

[0096] In some aspects, the PEI PDCCH may indicate whether a common TRS is available. In some aspects, the PEI PDCCH may indicate whether a dedicated TRS is supported. For example, when a UE sends a PEI response, a network entity may send a dedicated TRS to the UE. In some aspects, the PEI PDCCH may indicate whether a dedicated TRS is available. For example, a dedicated TRS may be supported and may have been triggered for a given duration. In some aspects, a dedicated TRS may have a validity duration, where the validity duration may be UE-specific, beam-specific, and / or subgroup-specific.

[0097] In some aspects, the network entity may send the CSI-RS to the UE based at least in part on the UE sending a PEI response to the network entity. The network entity may send the CSI-RS before (or after) a paging occasion. The CSI-RS may improve power consumption of the UE, and the CSI-RS may improve reception of paging indications during paging occasions. The sending of the CSI-RS may be triggered by reception of a PEI response. The CSI-RS may be a dedicated CSI-RS or a public CSI-RS. The network entity may send the CSI-RS in a periodic manner or in an aperiodic manner. The network entity may repeatedly send the CSI-RS, which may allow the UE to check multiple receive beams.

[0098] In some aspects, the PEI PDCCH may indicate whether a common CSI-RS is available. In some aspects, the PEI PDCCH may indicate whether a dedicated CSI-RS is supported. For example, when a UE sends a PEI response, a network entity may send a CSI-RS to the UE. In some aspects, the PEI PDCCH may indicate whether a CSI-RS is available. For example, a CSI-RS may be supported and may have been triggered for a given duration. In some aspects, a CSI-RS may have a validity duration, where the validity duration may be UE-specific, beam-specific, and / or subgroup-specific.

[0099] As shown in reference numeral 510, the UE may receive a paging indication from the network entity and during a paging occasion based at least in part on the PEI response. The UE may receive the paging indication based at least in part on beam information associated with the PEI response, which may prevent the network entity from performing beam scanning when sending the paging indication, thereby reducing energy usage at the network entity.

[0100] In some aspects, the network entity may be a first network entity. The first network entity may send signaling to the second network entity indicating whether a PEI response is to be implemented for paging the UE and / or criteria to be satisfied for the PEI response to be implemented. The signaling may be UE-specific, cell-specific, and / or beam-specific. In one example, the first network entity may be a first next generation radio access network (NG-RAN), and the second network entity may be a second NG-RAN. In another example, the first network entity may be a NG-RAN, and the second network entity may be an access and mobility management function (AMF), or vice versa.

[0101] In some aspects, various parameters for paging may be exchanged over the backhaul interface. For example, when sending a paging message to the second NG-RAN to page the UE, the AMF or the first NG-RAN may indicate a paging priority. The paging priority may indicate whether the paging UE should be handled with priority. As another example, when sending a paging message to the second NG-RAN to page the UE, the AMF or the first NG-RAN may indicate a paging attempt count and an expected number of paging attempts.

[0102] In some cases, implementing the PEI response feature may negatively impact UE performance due to the possibility that the PEI response will not be reliably detected by the network entity. The network entity may not send the paging message to the UE, which may result in increased latency. In addition, in the absence of a PEI response, the UE may be paged in multiple directions and on multiple cells, which may result in a higher probability that the paging message may reach the UE in a shorter period of time and with better quality.

[0103] In some aspects, enabling the PEI response feature for a UE may depend on the paging strategy. For example, when the NG-RAN receives an indication of the paging attempt count [k] and an indication of the expected number [K] of paging attempts for the UE to be paged, when k < K, or when k = 1, or generally for k < K - X where X is a predefined value, the PEI response may be enabled. In other words, the PEI response may be at least partially based on the paging attempt count being less than the expected number of paging attempts, or at least partially based on the paging attempt count being equal to one, or at least partially based on the paging attempt count being less than the expected number of paging attempts minus a first predefined value (e.g., X). As another example, when the NG-RAN receives an indication of the paging priority for the UE to be paged (e.g., not for voice over NR (VoNR) but for Internet data services), the PEI response may not be enabled, or when the paging priority is less than Y where Y is a predefined value, the PEI response may be enabled. In other words, the PEI response may be at least partially based on a value associated with the paging priority being less than a second predefined value (e.g., Y).

[0104] In some aspects, signaling between the AMF and the NG-RAN may be supported for core network (CN) paging, or signaling between NG-RANs (e.g., between a first NG-RAN and a second NG-RAN) may be supported for radio access network (RAN) paging. The signaling may indicate whether the PEI response will be implemented for paging the UE, where the indication of whether the PEI response will be implemented may be cell-specific and / or beam-specific. The signaling may indicate the criteria (e.g., the X and Y predefined values) for which the PEI response can be implemented, where the indication of the criteria for which the PEI response can be implemented may be UE-specific, cell-specific, and / or beam-specific.

[0105] As indicated above, Figure 5 is provided as an example. Other examples may be different from the examples described with respect to Figure 5 the examples described.

[0106] Figure 6 is a diagram illustrating Example 600 associated with the PEI response according to the present disclosure.

[0107] As Figure 6As shown in , a network entity may send an SSB to a UE, which may be initially associated with a deep sleep mode. The network entity may send a PEI to the UE. The UE may send a PEI response to a second network entity based at least in part on receiving the PEI. During the light / deep sleep mode, the UE may or may not receive other SSBs and / or radio resource management (RRM) signaling. The network entity may send a TRS to the UE based at least in part on a PEI response received from the UE. The network entity may send the TRS before a paging occasion. The network entity may send a paging indication during a paging occasion. The TRS may improve the reception of a paging indication during a paging occasion.

[0108] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0109] Figure 7 7 is a diagram illustrating an example process 700 performed, for example, by a UE according to the present disclosure. Example process 700 is an example in which a UE (eg, UE 120) performs operations associated with a PEI response.

[0110] like Figure 7 As shown in , in some aspects, process 700 may include receiving an indication from a network entity to configure a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction, and receiving PEI from the network entity (block 710). For example, a UE (e.g., using Fig. 9 The communication manager 140 and / or receiving component 902 depicted in the figure can receive an indication from a network entity to configure a PEI response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction, and receive the PEI from the network entity, as described above.

[0111] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include sending a PEI response to a network entity based at least in part on the PEI and an indication of configuring the PEI response (block 720). Fig. 9 The depicted communications manager 140 and / or transmitting component 904) can transmit a PEI response to a network entity based at least in part on the PEI and an indication to configure the PEI response, as described above.

[0112] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include receiving a paging indication from a network entity and during a paging occasion based at least in part on the PEI response (block 730). For example, a UE (e.g., using Fig. 9The communication manager 140 and / or receiving component 902 depicted in FIG. 1 may receive a paging indication from a network entity and during a paging occasion based at least in part on a PEI response, as described above.

[0113] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0114] In a first aspect, the PEI is configured to dynamically activate or deactivate a PEI response using a single bit flag.

[0115] In a second aspect, alone or in combination with the first aspect, the PEI is configured to use a bitmap to dynamically activate or deactivate a PEI response for one or more of a UE subgroup, a paging occasion, or a beam direction.

[0116] In a third aspect, alone or in combination with one or more of the first and second aspects, a PEI response is semi-statically configured via system information or dedicated RRC signaling for one or more of a UE subgroup, a paging occasion, or a beam direction.

[0117] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 700 includes sending capability signaling to a network entity indicating that the UE supports PEI responses, wherein the UE is expected to monitor PEI and send a PEI response based at least in part on the capability signaling.

[0118] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 700 includes receiving a TRS from a network entity before or after a paging occasion, wherein the TRS is triggered by receipt of a PEI response.

[0119] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the TRS is a non-periodic TRS or a periodic TRS, the TRS configuration associated with the TRS is based at least in part on the RRC configuration, the TRS is a public TRS or a dedicated TRS, the PEI indicates whether a public TRS is available, whether a dedicated TRS is supported, or whether a dedicated TRS is available, and the dedicated TRS is associated with a UE-specific, beam-specific, or UE subgroup-specific validity period.

[0120] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 700 includes receiving a CSI-RS from a network entity before or after a paging occasion, wherein the CSI-RS is triggered by receipt of a PEI response.

[0121] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the CSI-RS is an aperiodic CSI-RS or a periodic CSI-RS, the CSI-RS is a common CSI-RS or a dedicated CSI-RS, the CSI-RS is associated with repetition, the PEI indicates whether the common CSI-RS is available, whether the dedicated CSI-RS is supported, or whether the dedicated CSI-RS is available, and the dedicated CSI-RS is associated with a UE-specific, beam-specific, or UE subgroup-specific validity duration.

[0122] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the PEI response is based at least in part on a paging attempt count being less than an expected number of paging attempts, at least in part on a paging attempt count being equal to one, or at least in part on a paging attempt count being less than an expected number of paging attempts minus a first predefined value.

[0123] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the PEI response is based at least in part on a value associated with the paging priority being less than a second predefined value.

[0124] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks in the blocks of the process 700 may be performed in parallel.

[0125] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a network entity in accordance with the present disclosure. Example process 800 is an example in which a network entity (eg, network entity 110) performs operations associated with a PEI response.

[0126] like Figure 8 As shown in FIG. 8 , in some aspects, process 800 may include sending an indication to a UE to configure a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction, and sending the PEI to the UE (block 810). For example, a network entity (e.g., using Fig.10 The communication manager 150 and / or sending component 1004 depicted in the figure can send an indication to the UE to configure a PEI response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction, and send the PEI to the UE, as described above.

[0127] like Figure 8As further shown in FIG. 8 , in some aspects, process 800 may include receiving a PEI response from a UE based at least in part on the PEI and an indication of configuring a PEI response (block 820). For example, a network entity (e.g., using Fig.10 The depicted communications manager 150 and / or receiving component 1002) can receive a PEI response from a UE based at least in part on the PEI and an indication to configure the PEI response, as described above.

[0128] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending a paging indication to the UE and during a paging occasion based at least in part on the PEI response (block 830). For example, a network entity (e.g., using Fig.10 The communication manager 150 and / or the sending component 1004 depicted in FIG. 1 may send a paging indication to the UE and during a paging occasion based at least in part on the PEI response, as described above.

[0129] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0130] In a first aspect, process 800 includes receiving capability signaling from a UE indicating that the UE supports PEI responses.

[0131] In a second aspect, alone or in combination with the first aspect, process 800 includes: sending a TRS to the UE before or after a paging occasion, wherein the TRS is triggered by receiving a PEI response; or sending a CSI-RS to the UE before or after a paging occasion, wherein the CSI-RS is triggered by receiving a PEI response.

[0132] In a third aspect, either alone or in combination with one or more of the first and second aspects, the network entity is a first network entity, and process 800 includes sending signaling to a second network entity indicating one or more of the following: whether a PEI response is to be implemented for paging the UE, or criteria to be satisfied for a PEI response to be implemented, and the signaling is one or more of UE-specific, cell-specific, or beam-specific.

[0133] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted in the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks in the blocks of the process 800 may be performed in parallel.

[0134] Fig. 9900 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a UE, or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a network entity, or another wireless communication device) using receiving component 902 and transmitting component 904.

[0135] In some aspects, the apparatus 900 may be configured to perform the Figure 5 to Figure 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 and / or Fig. 9 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0136] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0137] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0138] The receiving component 902 may receive an indication from a network entity to configure a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction. The receiving component 902 may receive a PEI from the network entity. The sending component 904 may send a PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response. The receiving component 902 may receive a paging indication from the network entity and during a paging occasion based at least in part on the PEI response.

[0139] The transmitting component 904 can transmit capability signaling to a network entity indicating that the UE supports PEI responses, wherein the UE is expected to monitor PEI and transmit PEI responses based at least in part on the capability signaling. The receiving component 902 can receive a TRS from the network entity before or after a paging occasion, wherein the TRS is triggered by the reception of the PEI response. The receiving component 902 can receive a CSI-RS from the network entity before or after a paging occasion, wherein the CSI-RS is triggered by the reception of the PEI response.

[0140] Fig. 9 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 9 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 9 Two or more components shown in the figure may be implemented in a single component, or Fig. 9 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig. 9 Another set of components shown in the figure performs one or more functions.

[0141] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a network entity, or a network entity may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a network entity, or another wireless communication device) using receiving component 1002 and transmitting component 1004.

[0142] In some aspects, the apparatus 1000 may be configured to perform the Figure 5 to Figure 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.10 The apparatus 1000 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0143] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0144] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0145] The transmitting component 1004 may transmit an indication to the UE to configure a PEI response for one or more of: a UE subgroup; a paging occasion; or a beam direction. The transmitting component 1004 may transmit the CSI-PEI to the UE. The receiving component 1002 may receive a PEI response from the UE based at least in part on the PEI and the indication to configure the PEI response. The transmitting component 1004 may transmit a paging indication to the UE and during the paging occasion based at least in part on the PEI response.

[0146] The receiving component 1002 may receive capability signaling from the UE indicating that the UE supports PEI responses. The sending component 1004 may send a TRS to the UE before or after a paging occasion, wherein the TRS is triggered by receiving a PEI response. The sending component 1004 may send a CSI-RS to the UE before or after a paging occasion, wherein the CSI-RS is triggered by receiving a PEI response.

[0147] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.10 Two or more components shown in may be implemented in a single component, or Fig.10 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The assembly of (one or more) components shown in the executable is described as being composed of Fig.10 Another collection of components shown in the figure performs one or more functions.

[0148] The following provides an overview of some aspects of the disclosure:

[0149] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication from a network entity to configure a paging early indication (PEI) response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction; receiving a PEI from the network entity; sending the PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response; and receiving a paging indication from the network entity and during the paging occasion based at least in part on the PEI response.

[0150] Aspect 2: The method according to aspect 1, wherein the PEI is configured to dynamically activate or deactivate the PEI response using a single bit flag.

[0151] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the PEI is configured to use a bitmap to dynamically activate or deactivate the PEI response for one or more of the following: the UE subgroup, the paging occasion, or the beam direction.

[0152] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the PEI response is semi-statically configured via system information or dedicated radio resource control signaling for one or more of the following: the UE subgroup, the paging occasion, or the beam direction.

[0153] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: sending capability signaling to the network entity indicating that the UE supports the PEI response, wherein the UE is expected to monitor the PEI and send the PEI response based at least in part on the capability signaling.

[0154] Aspect 6: The method according to any one of aspects 1 to 5 further includes: receiving a Tracking Reference Signal (TRS) from the network entity before or after the paging occasion, wherein the TRS is triggered by reception of the PEI response.

[0155] Aspect 7: A method according to Aspect 6, wherein: the TRS is a non-periodic TRS or a periodic TRS; the TRS configuration associated with the TRS is based at least in part on a radio resource control configuration; the TRS is a public TRS or a dedicated TRS; the PEI indicates whether the public TRS is available, whether the dedicated TRS is supported, or whether the dedicated TRS is available; and the dedicated TRS is associated with a UE-specific, beam-specific, or UE subgroup-specific validity duration.

[0156] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: receiving a channel state information reference signal (CSI-RS) from the network entity before or after the paging occasion, wherein the CSI-RS is triggered by receiving the PEI response.

[0157] Aspect 9: A method according to Aspect 8, wherein: the CSI-RS is a non-periodic CSI-RS or a periodic CSI-RS; the CSI-RS is a common CSI-RS or a dedicated CSI-RS; the CSI-RS is associated with repetition; the PEI indicates whether the common CSI-RS is available, whether the dedicated CSI-RS is supported, or whether the dedicated CSI-RS is available; and the dedicated CSI-RS is associated with a UE-specific, beam-specific, or UE subgroup-specific validity duration.

[0158] Aspect 10: A method according to any one of Aspects 1 to 1, wherein the PEI response is based at least in part on a paging attempt count being less than an expected number of paging attempts, at least in part on the paging attempt count being equal to one, or at least in part on the paging attempt count being less than the expected number of paging attempts minus a first predefined value.

[0159] Aspect 11: The method according to any one of aspects 1 to aspect 1, wherein the PEI response is based at least in part on a value associated with the paging priority being less than a second predefined value.

[0160] Aspect 12: A method of wireless communication performed by a network entity, comprising: sending an indication to a user equipment (UE) to configure a paging early indication (PEI) response for one or more of the following: a UE subgroup; a paging occasion; or a beam direction; sending a PEI to the UE; receiving the PEI response from the UE based at least in part on the PEI and the indication to configure the PEI response; and sending a paging indication to the UE and during the paging occasion based at least in part on the PEI response.

[0161] Aspect 13: The method according to Aspect 12 further includes: receiving capability signaling from the UE indicating that the UE supports the PEI response.

[0162] Aspect 14: The method according to any one of Aspects 12 to 13 further includes: sending a tracking reference signal (TRS) to the UE before or after the paging occasion, wherein the TRS is triggered by the reception of the PEI response; or sending a channel state information reference signal (CSI-RS) to the UE before or after the paging occasion, wherein the CSI-RS is triggered by the reception of the PEI response.

[0163] Aspect 15: A method according to any one of Aspects 12 to 14, wherein the network entity is a first network entity, and the method further includes: receiving signaling from a second network entity indicating one or more of the following: whether the PEI response will be implemented for paging the UE, or criteria to be met for the PEI response to be implemented, and wherein the signaling is one or more of UE-specific, cell-specific, or beam-specific.

[0164] Aspect 16: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.

[0165] Aspect 17: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to execute the method according to one or more of aspects 1 to 11.

[0166] Aspect 18: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 1 to 11.

[0167] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.

[0168] Aspect 20: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 11.

[0169] Aspect 21: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 12 to 15.

[0170] Aspect 22: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 12 to 15.

[0171] Aspect 23: An apparatus for wireless communication, comprising at least one component for performing the method according to one or more of aspects 12 to 15.

[0172] Aspect 24: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 12 to 15.

[0173] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 12 to 15.

[0174] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0175] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads, processes and / or functions implemented, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0176] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0177] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0178] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; and one or more processors coupled to the memory and configured to: Receiving an indication from a network entity to configure a paging early indication (PEI) response for one or more of: UE subgroup; Paging occasion; or Beam direction; receiving PEI from the network entity; and sending the PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response; as well as A paging indication is received from the network entity and during the paging occasion based at least in part on the PEI response. 2 . The apparatus of claim 1 , wherein the PEI is configured to dynamically activate or deactivate the PEI response using a single bit flag.

3. The apparatus of claim 1, wherein the PEI is configured to use a bitmap to dynamically activate or deactivate the PEI response for one or more of: the UE subgroup, the paging occasion, or the beam direction.

4. The apparatus of claim 1, wherein the PEI response is semi-statically configured via system information or dedicated radio resource control signaling for the one or more of: the UE subgroup, the paging occasion, or the beam direction.

5. The apparatus of claim 1 , wherein the one or more processors are further configured to: Capability signaling is sent to the network entity indicating that the UE supports the PEI response, wherein the UE is expected to monitor the PEI and send the PEI response based at least in part on the capability signaling.

6. The apparatus of claim 1, wherein the one or more processors are further configured to: A Tracking Reference Signal (TRS) is received from the network entity before or after the paging occasion, wherein the TRS is triggered by receipt of the PEI response.

7. The device according to claim 6, wherein: The TRS is a non-periodic TRS or a periodic TRS; a TRS configuration associated with the TRS based at least in part on a radio resource control configuration; The TRS is a public TRS or a dedicated TRS; The PEI indicates whether the public TRS is available, whether the dedicated TRS is supported, or whether the dedicated TRS is available; and The dedicated TRS is associated with a UE-specific, beam-specific or UE subgroup-specific validity duration.

8. The apparatus of claim 1, wherein the one or more processors are further configured to: A channel state information reference signal (CSI-RS) is received from the network entity before or after the paging occasion, wherein the CSI-RS is triggered by reception of the PEI response.

9. The device according to claim 8, wherein: The CSI-RS is an aperiodic CSI-RS or a periodic CSI-RS; The CSI-RS is a public CSI-RS or a dedicated CSI-RS; The CSI-RS is associated with repetition; The PEI indicates whether the common CSI-RS is available, whether the dedicated CSI-RS is supported, or whether the dedicated CSI-RS is available; and The dedicated CSI-RS is associated with a UE-specific, beam-specific, or UE subgroup-specific validity duration.

10. The apparatus of claim 1 , wherein the PEI response is based at least in part on a paging attempt count being less than an expected number of paging attempts, at least in part on the paging attempt count being equal to one, or at least in part on the paging attempt count being less than the expected number of paging attempts minus a first predefined value.

11. The apparatus of claim 1, wherein the PEI response is based at least in part on a value associated with a paging priority being less than a second predefined value.

12. An apparatus for wireless communication at a network entity, comprising: Memory; and one or more processors coupled to the memory and configured to: Sending an indication to a user equipment (UE) to configure a paging early indication (PEI) response for one or more of: UE subgroup; Paging occasion; or Beam direction; Sending PEI to the UE; receiving, from the UE, the PEI response based at least in part on the PEI and the indication to configure the PEI response; as well as A paging indication is sent to the UE and during the paging occasion based at least in part on the PEI response.

13. The apparatus of claim 12, wherein the one or more processors are further configured to: Capability signaling is received from the UE indicating that the UE supports the PEI response.

14. The apparatus of claim 12, wherein the one or more processors are further configured to: sending a Tracking Reference Signal (TRS) to the UE before or after the paging occasion, wherein the TRS is triggered by reception of the PEI response; or A channel state information reference signal (CSI-RS) is transmitted to the UE before and after the paging occasion, wherein the CSI-RS is triggered by the reception of the PEI response.

15. The apparatus of claim 12, wherein the network entity is a first network entity, and wherein the one or more processors are further configured to: Signaling is received from a second network entity indicating one or more of whether the PEI response is to be implemented for paging the UE, or criteria to be satisfied for the PEI response to be implemented, and wherein the signaling is one or more of UE-specific, cell-specific, or beam-specific.

16. A method of wireless communication performed by a user equipment (UE), comprising: Receiving an indication from a network entity to configure a paging early indication (PEI) response for one or more of: UE subgroup; Paging time; or Beam direction; receiving PEI from the network entity; sending the PEI response to the network entity based at least in part on the PEI and the indication to configure the PEI response; as well as A paging indication is received from the network entity and during the paging occasion based at least in part on the PEI response.

17. The method of claim 16, wherein the PEI is configured to dynamically activate or deactivate the PEI response using a single bit flag.

18. The method of claim 16, wherein the PEI is configured to use a bitmap to dynamically activate or deactivate the PEI response for the one or more of: the UE subgroup, the paging occasion, or the beam direction.

19. The method of claim 16, wherein the PEI response is semi-statically configured via system information or dedicated radio resource control signaling for the one or more of: the UE subgroup, the paging occasion, or the beam direction.

20. The method of claim 16, further comprising: Capability signaling is sent to the network entity indicating that the UE supports the PEI response, wherein the UE is expected to monitor the PEI and send the PEI response based at least in part on the capability signaling.

21. The method of claim 16, further comprising: A Tracking Reference Signal (TRS) is received from the network entity before or after the paging occasion, wherein the TRS is triggered by receipt of the PEI response.

22. The method of claim 21, wherein: The TRS is a non-periodic TRS or a periodic TRS; a TRS configuration associated with the TRS based at least in part on a radio resource control configuration; The TRS is a public TRS or a dedicated TRS; The PEI indicates whether the public TRS is available, whether the dedicated TRS is supported, or whether the dedicated TRS is available; and The dedicated TRS is associated with a UE-specific, beam-specific or UE subgroup-specific validity duration.

23. The method of claim 16, further comprising: A channel state information reference signal (CSI-RS) is received from the network entity before or after the paging occasion, wherein the CSI-RS is triggered by reception of the PEI response.

24. The method of claim 23, wherein: The CSI-RS is an aperiodic CSI-RS or a periodic CSI-RS; The CSI-RS is a public CSI-RS or a dedicated CSI-RS; The CSI-RS is associated with repetition; The PEI indicates whether the common CSI-RS is available, whether the dedicated CSI-RS is supported, or whether the dedicated CSI-RS is available; and The dedicated CSI-RS is associated with a UE-specific, beam-specific, or UE subgroup-specific validity duration.

25. The method of claim 16, wherein the PEI response is based at least in part on a paging attempt count being less than an expected number of paging attempts, at least in part on the paging attempt count being equal to one, or at least in part on the paging attempt count being less than the expected number of paging attempts minus a first predefined value.

26. The method of claim 16, wherein the PEI response is based at least in part on a value associated with the paging priority being less than a second predefined value.

27. A method of wireless communication performed by a network entity, comprising: Sending an indication to a user equipment (UE) to configure a paging early indication (PEI) response for one or more of: UE subgroup; Paging occasion; or Beam direction; Sending PEI to the UE; receiving the PEI response from the UE based at least in part on the PEI and the indication to configure the PEI response; as well as A paging indication is sent to the UE and during the paging occasion based at least in part on the PEI response.

28. The method according to claim 27, further comprising: Capability signaling is received from the UE indicating that the UE supports the PEI response.

29. The method of claim 27, further comprising: sending a tracking reference signal (TRS) to the UE before or after the paging occasion, wherein the TRS is triggered by reception of the PEI response; or A channel state information reference signal (CSI-RS) is transmitted to the UE before and after the paging occasion, wherein the CSI-RS is triggered by the reception of the PEI response.

30. The method of claim 27, wherein the network entity is a first network entity, and the method further comprises: Signaling is received from a second network entity indicating one or more of whether the PEI response is to be implemented for paging the UE, or criteria to be satisfied for the PEI response to be implemented, and wherein the signaling is one or more of UE-specific, cell-specific, or beam-specific.

Images