Early indication of paging in non-terrestrial networks

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may communicate a connection release message via a first beam to release a connection between the UE and a network entity. The UE may obtain an indication associated with a second beam of the non-terrestrial network entity, the indication indicating a set of one or more beams associated with the paging early indication. The UE may monitor a PEI paging message based on whether the first beam is included in the set of one or more beams. Alternatively, the UE may skip monitoring PEI based on the first beam to be excluded from the set of one or more beams, and the UE may monitor paging messages during a paging occasion. In some examples, the UE may receive, from the non-terrestrial network entity, a message indicating the set of one or more beams.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. patent application No. 17 / 892,680, entitled “PAGING EARLY INDICATIONS IN NON-TERRESTRIAL NETWORKS,” filed by LASTNAME et al. on August 22, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Background Art

[0003] The following relates to wireless communications, including managing paging in a network.

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] An apparatus for wireless communication at a UE is described. The apparatus may include a processor and a memory coupled to the processor, the processor being configured to communicate a connection release message to release a connection via a first beam associated with communication between the UE and a network entity. In some examples, the processor may be configured to obtain an indication associated with a second beam, the indication indicating a set of one or more beams associated with a paging early indication (PEI). In some examples, the processor may monitor a paging message via the second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0006] A method for wireless communication at a UE is described. The method may include: communicating a connection release message via a first beam associated with communication between the UE and a network entity to release a connection. In some examples, the method may include: obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with a PEI. The method may also include: monitoring a paging message via the second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include components for communicating a connection release message to release a connection via a first beam associated with communication between the UE and a network entity. In some examples, the apparatus may include components for obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with a PEI. In some examples, the apparatus may also include components for monitoring a paging message via the second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that are executable by a processor to communicate a connection release message to release a connection via a first beam associated with communication between the UE and a network entity. In some examples, the instructions may be executable by the processor to obtain an indication associated with a second beam, the indication indicating a set of one or more beams associated with a PEI. The instructions may also be executable by the processor to monitor a paging message via the second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0009] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring the PEI via the second beam based on the first beam being included in the set of one or more beams.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: based on receiving the PEI, using the second beam to monitor downlink control information (DCI) associated with a paging occasion (PO).

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first beam and the second beam can be the same.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of one or more additional beams from the network entity, the one or more additional beams and the second beam having adjacent beam coverage areas, the set of one or more beams including the second beam and the one or more additional beams.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring DCI associated with the PO via the second beam based on the first beam being excluded from the set of one or more beams.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a last-used-beam-only indication from the network entity, wherein the indication associated with the second beam may be obtained based on the last-used-beam-only indication.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for storing an indication of the first beam associated with a recent communication between the UE and the network entity, wherein the paging message may be monitored based on the stored indication of the first beam.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first beam may be associated with a recent communication between the UE and the network entity.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a system information block (SIB) from a network entity and via the second beam, the system information block (SIB) indicating the set of one or more beams associated with the PEI.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a third beam as a resident beam for the UE to monitor one or more channels associated with the network entity, and receiving a SIB from the network entity and via the third beam, the SIB indicating a second set of one or more beams associated with the PEI.

[0019] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor and a memory coupled to the processor. The processor may be configured to communicate a connection release message via a first beam to release a connection associated with a UE. In some examples, the processor may determine a set of one or more beams associated with a second beam and a PEI, and output the PEI based on the set of one or more beams associated with the PEI.

[0020] A method of wireless communication at a network entity is described. The method may include communicating a connection release message via a first beam to release a connection associated with a UE. In some examples, the method may include determining a set of one or more beams associated with a second beam and a PEI, and outputting the PEI based on the set of one or more beams associated with the PEI.

[0021] Another apparatus for wireless communication at a network entity is described. The apparatus may include components for communicating a connection release message via a first beam to release a connection associated with a UE. In some examples, the apparatus may include components for determining a set of one or more beams associated with a second beam and a PEI and components for outputting the PEI based on the set of one or more beams associated with the PEI.

[0022] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to communicate a connection release message via a first beam to release a connection associated with a UE. In some examples, the code may include instructions executable by a processor to determine a set of one or more beams associated with a second beam and a PEI, and output the PEI based on the set of one or more beams associated with the PEI.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting an indication of the set of one or more beams to the UE and via the second beam.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, outputting the indication of the set of one or more beams may include operations, features, components, or instructions for outputting an indication of the SIB of the set of one or more beams associated with the PEI.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a last used beam only indication, wherein the set of one or more beams associated with the PEI may be determined based on the last used beam only indication being output.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting the PEI using the second beam based on the first beam being included in the set of one or more beams associated with the PEI.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting an indication of one or more additional beams, the one or more additional beams and the second beam having adjacent beam coverage areas, wherein the set of the one or more beams includes the second beam and the one or more additional beams.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first beam and the second beam can be the same.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first beam may be associated with a most recent transmission between the UE and the network entity.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for storing an indication of the first beam, wherein the PEI may be output based on storing the indication of the first beam.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a control message during the PO based on outputting the PEI. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 An example of a wireless communication system supporting PEI in a non-terrestrial network (NTN) according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 2 An example of a network architecture supporting PEI in an NTN according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 3An example of a wireless communication system supporting PEI in an NTN according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 4 An example of a process flow for supporting PEI in NTN according to one or more aspects of the present disclosure is illustrated.

[0036] Figure 5 An example of a process flow for supporting PEI in NTN according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 6 and Figure 7 A block diagram of a device supporting PEI in an NTN according to one or more aspects of the present disclosure is shown.

[0038] Figure 8 A block diagram of a communication manager supporting PEI in an NTN according to one or more aspects of the present disclosure is shown.

[0039] Fig. 9 A diagram of a system including a device supporting PEI in an NTN according to one or more aspects of the present disclosure is shown.

[0040] Fig.10 and Fig.11 A block diagram of a device supporting PEI in an NTN according to one or more aspects of the present disclosure is shown.

[0041] Fig.12 A block diagram of a communication manager supporting PEI in an NTN according to one or more aspects of the present disclosure is shown.

[0042] Fig.13 A diagram of a system including a device supporting PEI in an NTN according to one or more aspects of the present disclosure is shown.

[0043] Figures 14 to 19 A flow chart illustrating a method of supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0044] A network entity may send a PEI to a UE to instruct the UE to monitor an upcoming PO. In some examples, the network entity may send a PEI to multiple UEs belonging to the same paging subgroup. For example, the network entity may broadcast the PEI in a beam corresponding to a cell of the network entity. The UE may detect the PEI indicating the paging subgroup to which the UE belongs, and determine to monitor an upcoming PO. Alternatively, if the UE does not detect the PEI, the UE may skip monitoring for an upcoming PO. In some examples, the network entity may broadcast an indication (e.g., a lastUsedCellOnly indication) to UEs within a cell to indicate that these UEs should monitor the PEI only if the last connection of these UEs was released by the cell. Therefore, if the last connection of the UE was released by a different cell, the UE may monitor the upcoming PO even if the UE did not detect the PEI.

[0045] In some cases, since the non-terrestrial network entity has a large cell coverage area, using each beam corresponding to a cell to send a PEI to a paging subgroup of UEs may result in unnecessary signaling overhead and power consumption at the non-terrestrial network entity. In addition, the number of UEs in a paging subgroup may be large because the number of UEs served by a cell may be larger for a non-terrestrial network entity than for a terrestrial network entity due to the larger cell coverage area of ​​the non-terrestrial network entity. Therefore, whenever a UE in a paging subgroup is paged (e.g., scheduled to receive a paging DCI), each of the other UEs in the paging subgroup may detect the PEI and determine to monitor the corresponding PO, even when there is no paging DCI available for the other UEs. This may result in false alarm problems at the other UEs, which may result in increased power consumption at the other UEs.

[0046] Thus, according to aspects of the present disclosure, the techniques, systems, and devices described herein enable a UE to determine a beam set associated with a non-terrestrial network and determine whether to monitor PEI based on the beam set and the last used beam (e.g., the beam associated with the most recent communication in which the last connection was released). For example, the UE may send a connection release message to a network entity or receive the connection release message from a network entity to release the cell to which the UE is connected. The connection release message may indicate that the UE is operating in an idle or inactive mode and may be sent or received via a control channel.

[0047] The beam set may correspond to a subset of beams available in the cell. For example, the beam set may include a first beam and, in some cases, one or more beams adjacent to the first beam. For example, the UE may determine that the last used beam of the UE is included in the beam set and monitor the PEI via a resident beam (e.g., a beam of the network entity 105 where the UE 115 resides). Alternatively, the UE may determine that the last used beam of the UE is excluded from the beam set and determine to skip monitoring the PEI, and in some examples, use the resident beam to monitor the PO associated with the UE. Therefore, the network entity may consider PEI transmission for a subset of beams available in the cell (e.g., the first beam and, in some cases, one or more adjacent beams), which may reduce transmission overhead and power consumption at the network entity. In addition, the paging subgroups of the UE may be smaller in size because the paging subgroups may correspond to UEs operating within a beam set (e.g., instead of all beams available in the cell), and the false alarm frequency may be reduced, thereby reducing power consumption at the UE.

[0048] Aspects of the present disclosure are first described in the context of a wireless communication system. In addition, aspects of the present disclosure are illustrated with reference to process flows. Aspects of the present disclosure are further illustrated and described with reference to device diagrams, system diagrams, and flow diagrams related to PEI in NTN.

[0049] Figure 1 An example of a wireless communication system 100 supporting PEI in an NTN according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be an LTE network, an LTE-A network, an LTE-A Pro network, an NR network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0050] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0051] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 105).

[0052] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, reference to UE 115, network entity 105, apparatus, device, or computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, or computing system, etc. as a node. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0053] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information or signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0054] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0055] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0056] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0057] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of the CU 160, DU 165, or RU 170). The CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0058] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas (e.g., of the RU 170) of the IAB node 104 for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports a communication link with another entity (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0059] Where the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support PEI in an NTN as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0060] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0061] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.

[0062] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0063] The signal waveform transmitted via the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively high amount of resource elements (e.g., in the transmission duration) and a relatively high order of the modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0064] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period. seconds, of which may indicate the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0065] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0066] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0067] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of the control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0068] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors (such as the capabilities of the network entity 105), such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0069] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0070] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0071] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communications may include private communications or group communications and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms "ultra-reliable," "low latency," and "ultra-reliable low latency" are used interchangeably herein.

[0072] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0073] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0074] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide service to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0075] The electromagnetic spectrum is often subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles, even though a portion of FR1 is greater than 6 GHz. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, even though it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) that is identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0076] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4–1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0077] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used herein, the term "sub-6 GHz" or the like, etc., can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used herein, the term "millimeter wave" or the like, etc., can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0078] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands can be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0079] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports of multiple rows and columns that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0080] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a sending device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the sending device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the sending device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the sending device or the receiving device or relative to some other orientation).

[0081] UE 115 may camp on a cell of network entity 105. For example, UE 115 may have selected a cell (e.g., after completing a cell selection process) and may monitor system information (e.g., SIB) and paging information associated with the cell. In some examples, UE 115 may select a camping beam (e.g., a beam of a cell on which UE 115 camps), and UE 115 may monitor the camping beam for transmissions or broadcasts (e.g., system information or paging information) from the cell. In some cases, the camping beam may be the best beam (e.g., a beam with the highest signal strength), which may be a synchronization signal block (SSB) beam or a physical broadcast channel beam.

[0082] The network entity communication manager 101 may manage communications between the network entity 105 and other devices in the wireless communication system 100. In a similar manner, the UE communication manager 102 may manage communications between the UE 115 and other devices in the wireless communication system 100. As described herein, the network entity 105 may refer to a terrestrial communication device (such as a base station 140) or a non-terrestrial communication device (such as a satellite 185, a balloon, a drone, or another non-terrestrial device). The non-terrestrial network entity 105 may be connected to the terrestrial network entity 105 via a gateway 190. In some examples, the non-terrestrial network entity 105 may correspond to a first cell type (e.g., an NTN cell type), and the terrestrial network entity 105 may correspond to a second cell type different from the first cell type (e.g., a terrestrial (TN) cell type).

[0083] The non-terrestrial network entity 105 may provide coverage for areas where the terrestrial network entity 105 may not be available. The channel corresponding to the non-terrestrial network entity 105 may be characterized by a strong line-of-sight condition because the signal provided by the non-terrestrial network entity 105 may be reflected in the sky (e.g., as opposed to the signal corresponding to the terrestrial network entity 105 which may travel on the ground). The coverage area of ​​the beam radiated from the non-terrestrial network entity 105 may have relatively clear boundaries (e.g., compared to the terrestrial network entity 105 beam boundaries), and the UE 115 may operate within a single beam service area (e.g., except in the case where the UE 115 is located at the boundary between two service areas). In some examples, the service area of ​​the beam corresponding to the non-terrestrial network entity 105 may be larger than the service area of ​​the beam corresponding to the terrestrial network entity 105.

[0084] The network entity 105 may send a PEI to the UE 115 to instruct the UE 115 to monitor an upcoming PO. In some examples, the network entity 105 may send a PEI to multiple UEs 115 belonging to the same paging subgroup. For example, the network entity 105 may broadcast the PEI in a beam corresponding to a cell. The UE 115 may detect the PEI indicating the paging subgroup to which the UE 115 belongs, and determine to monitor an upcoming PO. Alternatively, if the UE 115 does not detect the PEI, the UE 115 may determine to skip monitoring for an upcoming PO. In some examples, the network entity 105 may broadcast an indication (e.g., a lastUsedCellOnly indication) to the UEs 115 within the cell to indicate that these UEs 115 should monitor the PEI only if the last connection of these UEs 115 is released by the cell. Therefore, if the last connection of the UE 115 is released by a different cell, the UE 115 may monitor the upcoming PO even if the UE 115 does not detect the PEI.

[0085] In some cases, since the non-terrestrial network entity 105 has a large cell coverage area that may be associated with multiple beams, sending a PEI to a paging subgroup of UEs 115 using each beam corresponding to a cell may result in unnecessary signaling overhead and power consumption at the non-terrestrial network entity 105. In addition, the number of UEs 115 in one paging subgroup may be large because the number of UEs 115 served by one cell of the non-terrestrial network entity 105 may be larger than the number of UEs served by a cell of the terrestrial network entity 105 due to the larger cell coverage area of ​​the non-terrestrial network entity. Therefore, whenever a UE 115 in a paging subgroup is paged (e.g., scheduled to receive a paging DCI), each of the other UEs 115 in the paging subgroup may detect the PEI and determine to monitor the corresponding PO, even when there is no paging DCI available for the other UEs 115. This may result in false alarm issues at the other UEs 115 of the large paging subgroup, which may result in increased power consumption at the plurality of UEs 115.

[0086] Thus, the techniques, systems, and devices described herein enable a UE 115 to determine a beam set associated with a cell and determine whether to monitor PEI based on the beam set and a last used beam (e.g., a last used resident beam whose last connection was released). The beam set may correspond to a subset of all beams available in the cell. For example, the beam set may include a first beam (e.g., a resident beam) and, in some cases, one or more beams adjacent to the first beam. For example, the UE 115 may determine that the last used beam of the UE 115 is included in the beam set and monitor the PEI via the resident beam (e.g., a beam of the network entity 105 on which the UE 115 resides). Alternatively, the UE 115 may determine that the last used beam of the UE 115 is excluded from the beam set and determine to skip monitoring the PEI, and in some examples, use the resident beam to monitor the PO associated with the UE 115. Therefore, the network entity 105 may consider PEI transmission for a subset of beams (e.g., the first beam and, in some cases, one or more adjacent beams) of all beams available in the cell, which may reduce transmission overhead and power consumption at the network entity 105. In addition, paging subgroups of UEs 115 may be smaller in size because these paging subgroups may correspond to UEs 115 operating within a set of beams (e.g., rather than UEs 115 operating within all beams available in the cell), which may reduce false alarm frequencies at other UEs 115 and reduce power consumption at the UEs 115.

[0087] Figure 2An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting PEI in an NTN according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near-RT RIC 175-b via an E2 link or a non-RTRIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

[0088] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals over a wireless transmission medium, or to send signals over a wireless transmission medium to one or more of the other network entities 105, or both.

[0089] In some examples, CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, or SDAP, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 160-a. CU 160-a may be configured to handle user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or a combination thereof. In some examples, CU 160-a 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 160-a may be implemented to communicate with DU 165-a for network control and signaling.

[0090] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, or the like), depending at least in part on functional divisions such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0091] In some examples, lower layer functions may be implemented by one or more RUs 170-a. For example, a RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) or both based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UEs 115-a. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable the DU 165-a and the CU 160-a to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0092] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a 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 (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface.The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0093] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

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

[0095] The network architecture 200 may support PEI of non-terrestrial network entities. For example, any combination of network entities included in the network architecture 200 may support non-terrestrial network entities, terrestrial network entities, or a combination thereof. The non-terrestrial network entities may include RU 170-a, DU 165-a, CU 160-a, or any combination thereof (e.g., as a component or otherwise connected or communicating with satellite 185 or other non-terrestrial network entities).

[0096] UE 115 may determine a beam set associated with a cell and determine whether to monitor PEI based on the beam set used for communicating with the cell of the non-terrestrial network entity and the last used beam (e.g., the beam associated with the most recent communication for which the last connection was released). The beam set may correspond to a subset of beams available in the cell of the non-terrestrial network entity. For example, the beam set may include a first beam and, in some cases, one or more beams adjacent to the first beam. In some examples, UE 115 may receive an indication of the beam set from the non-terrestrial network entity 105.

[0097] UE 115 may determine that the last used beam of UE 115 is included in the beam set and use the resident beam to monitor the PEI. Alternatively, UE 115 may determine that the last used beam of UE 115 is excluded from the beam set and determine to skip monitoring the PEI, and in some examples, use the resident beam to monitor the PO associated with UE 115. Therefore, the non-terrestrial network entity may consider PEI transmission for a beam subset of all beams available in the cell, which may reduce transmission overhead and power consumption at the network entity.

[0098] Figure 3 An example of a wireless communication system 300 supporting PEI in an NTN according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may be as described herein with reference to Figure 1In some examples, the wireless communication system 300 may include the wireless communication system 100 described in the reference Figure 2 The wireless communication system 300 may include: UE 115-b and UE 115-c, which may be as shown in FIG. Figure 1 and Figure 2 An example of a UE 115 described; and a network entity 105-a, which may be as described in reference Figure 1 and Figure 2 An example of a network entity 105 is depicted. In some cases, the network entity 105-a may be an example of a non-terrestrial network entity 105-a, such as a satellite 185-a.

[0099] The network entity 105-a may support multiple beam coverage areas 305 in the cell 335, such as beam coverage areas 305-a, 305-b, 305-c, and 305-d associated with beams 340-a, 340-b, 340-c, and 340-d, respectively. The beam coverage areas may be associated with communication links 310 (such as communication link 310-a and communication link 310-b) used to communicate with the UE 115, which communication links may be as described herein. Figure 1 In some examples, beam coverage area 305 may be associated with beam coverage area 305 corresponding to terrestrial network entity 105. Thus, UE 115 may be more likely to operate within a single beam coverage area 305. For example, UE 115-b may operate within beam coverage area 305-b, and UE 115-c may operate within beam coverage area 305-d. In some examples, because beam coverage area 305 of network entity 105-a may be large, a dwell beam 340 selected by UE 115-b for communicating with a cell of network entity 105-a may be more likely to be the same as a last used beam 340 (e.g., a last used dwell beam 340) associated with a most recent communication whose last connection was released (e.g., suspended) by UE 115-b or a cell of network entity 105-a.

[0100] The network entity 105-a may transmit the SIB 315 containing information about the cell 335 via the beam 340 associated with each beam coverage area 305. For example, the network entity 105-a may transmit the SIB 315-a to the UE 115-b via the beam 340-b associated with the beam coverage area 305-b, and transmit the SIB 315-b to the UE 115-c via the beam 340-d associated with the beam coverage area 305-d. In some examples, the information contained in each SIB 315 associated with the cell 335 may be the same. Alternatively, the information contained in each SIB 315 may be different for each beam 340 of the cell 335. In some cases, if the UE 115 may switch to another beam 340 of the cell 335 (e.g., reselect the camp beam 340), the UE 115 may read the SIB 315 corresponding to the beam 340 to which the UE 115 switched. For example, if the UE 115-b moves to the beam coverage area 305-c, the UE 115-b may reselect the dwelling beam 340-c and re-read the SIB 315 associated with the dwelling beam 340-c associated with the beam coverage area 305-c.

[0101] In some examples, the network entity 105-a may transmit (e.g., after the SSB 320) a PEI 325 indicating a paging subgroup. The UE 115 may detect the PEI 325 indicating a paging subgroup that may be associated with the UE 115, and the UE 115 may monitor (e.g., process) an upcoming PO 330. For example, if the UE 115-b detects the PEI 325 corresponding to the paging subgroup of the UE 115-b, the UE 115-b may monitor the upcoming PO 330-a using the camping beam 340-b (e.g., the beam 340-b of the network entity 105-a on which the UE 115-b is camped). In another example, if the UE 115-b does not detect the PEI 325, the UE 115-b may skip monitoring for the upcoming PO 330-a. In some cases, the network entity 105-a may send an indication (e.g., in system information such as SIB 315) that the UE 115 should monitor the PEI in the last used cell (e.g., a lastUsedCellOnly indication). For example, if the network entity 105-a broadcasts the lastUsedCellOnly indication, the UE 115-b may monitor the PEI 325 if the last connection was released within the cell 335. Alternatively, if the last connection of the UE 115-b was released by a different cell other than the cell 335, the network entity 105-a may not send the PEI 325 for the UE 115-b in the cell 335, and the UE 115-b may monitor the PEI 330 even if the UE 115-b does not detect the PEI 325.

[0102] According to the examples described herein, the UE 115 may determine a set of one or more beams 345 associated with the monitoring PEI 325. In some examples, the network entity 105-a may determine the set of one or more beams 345 and send an indication of the set to the UE 115-b via the dwell beam 345-b (e.g., in the SIB 315-a). For example, if the UE 115-b moves to a new beam coverage area 305-c and reselects the dwell beam 340-c, the UE 115-b may receive another indication of the set of one or more beams 345 corresponding to the dwell beam 340-c for the reselected resident beam 340-c (e.g., in another SIB 315). Additionally or alternatively, the UE 115-b may autonomously determine the set of one or more beams 345 associated with the cell of the new beam coverage area 305-c. In some examples, the set of one or more beams 345 may include the current dwelling beam 340 and, in some cases, one or more beams adjacent to the current dwelling beam (e.g., beams with consecutive beam indices and / or beams with adjacent / overlapping beam coverage areas on the ground). For example, the set of one or more beams 345 associated with UE 115-b may include a beam with a beam index The dwell beam 340-b and, in some cases, includes a beam index The adjacent beam 340-a (eg, corresponding to the beam coverage area 305-a) and the beam index In another example, the set of one or more beams 345 associated with the UE 115-c may include a beam index The dwell beam 340-d and in some cases, includes a beam index In another example, the set of one or more beams 345 associated with the UE 115-c may also include neighboring beams from a neighboring cell (e.g., a cell different from the cell 335 and served by the same network entity 105-a or a different network entity).

[0103] The UE 115-b may monitor the PEI 325 based on the set of one or more beams 345. For example, the UE 115-b may determine to monitor the PEI 325 based on whether the last used beam 340 of the UE 115-b (e.g., the beam 340 for which the last connection of the UE 115-b was released or suspended) is included in the set of one or more beams 345. That is, the UE 115-b may determine that the last used beam 340 of the UE 115-b is included in the set of one or more beams 345, and monitor the PEI 325. If the UE 115-b detects the PEI 325, the UE 115-b may monitor the PO 330 via the dwell beam 340-b. Alternatively, UE 115-b may determine that the last used beam 340 of UE 115-b (e.g., when UE 115-b moves to or from another beam coverage area 305) is excluded from the set of one or more beams 345 and skip monitoring PEI 325. In this case, UE 115-b may monitor PO 330 via the resident beam 340-b (e.g., when PEI 325 is not detected).

[0104] Thus, if the last used beam 340 of the UE 115-b is included in the set of one or more beams 345 associated with the UE 115-b, the network entity 105-a may send the PEI 325 to the UE 115-b. Thus, the network entity 105-a may consider a smaller subset of the UEs 115 for transmitting the PEI 325 in each beam 340 associated with the beam coverage area 305 of the cell 335. For example, the paging subgroup associated with the PEI 325 may be reduced to include UEs 115 operating within the set of one or more beams 340 (e.g., the beam 340 associated with the beam coverage area 305, and in some cases one or more adjacent beams 345). Thus, the number of PEI 325 transmissions may be reduced, thereby reducing overhead and power consumption at the network entity 105-a. In addition, since the size of the paging subgroup for network entity 105-a may be smaller relative to the TN network entity 105, the frequency of false alarms at UE 115 (e.g., UE 115 receives PEI 325 for another UE 115 in the same paging subgroup) can be reduced, thereby reducing power consumption at UE 115.

[0105] In some examples, the network entity 105-a may store the last used beam 340 information corresponding to the UE 115. For example, the network entity 105-a may store the last used beam 340 of the UE 115-b after the connection with the UE 115-b is released or suspended. In some implementations, the network entity 105-a may send a message to a core network (CN) indicating the last used beam 340 information of the UE 115 (e.g., after the connection with the UE 115 is released or suspended). If a paging message addressed to the UE 115 is to be sent, the CN may send the last used beam 340 information corresponding to the UE 115 to the network entity 105-a. Thus, if the network entity 105-a determines to send a paging message addressed to the UE 115 in the PO 330 (e.g., a paging message for an RRC_INACITVE or RRC_IDLE UE 115), the network entity 105-a may determine one or more beams 340 for sending the PEI 325 based on the stored last used beam 340 information.

[0106] In some examples, various aspects described herein involving a set of one or more beams 345 associated with PEI 325 transmissions may be activated or applied to a network entity 105-a based on certain scenarios or deployments. For example, if the network entity 105-a is a geostationary orbit (GEO) or medium earth orbit (MEO) satellite 185 whose service time for the area under consideration is greater than a threshold time, these aspects may be enabled. Similarly, the number of beams 345 to be included in the set of one or more beams 340 associated with PEI 325 transmissions may be based on the satellite 185 type or deployment scenario. For example, in the case of a fast earth mobile cell 335 (e.g., a cell 335 having a beam coverage area 305 that moves along the ground as the network entity 105-a moves), the set of one or more beams 345 may include a larger number of beams 340. Therefore, more UEs 115 camping on the beams 340 of the cell 335 may apply the PEI 325 procedure to improve power saving.

[0107] In some cases, the network entity 105-a may change the number of beams 340 in the set of one or more beams 345 based on one or more of real-time traffic in the beam 340 under consideration and the number of UEs 115 that have released connections in the beam 345 (e.g., the beam 340 to be indicated in the set of one or more beams 340). For example, if the network entity 105-a determines that the traffic load in the beam 340 under consideration is low, the network entity 105-a may increase the number of beams 340 included in the set of one or more beams 345 corresponding to the beam 340 under consideration (e.g., to include one or more neighboring beams 340). As a result, more UEs 115 residing in the beam under consideration may apply the PEI 325 procedure to reduce power consumption.

[0108] Figure 4 An example of a process flow 400 for supporting PEI in an NTN according to one or more aspects of the present disclosure is illustrated. The process flow 400 may be referenced herein. Figure 1 and Figure 3 The process flow 400 may include a UE 115-d, which may be a wireless communication system 100 or a wireless communication system 300 as described above. Figures 1 to 3 The example of UE 115 described herein may include a network entity 105-b, which may be as described in reference Figures 1 to 3 An example of a network entity 105 is described. In the following description of process flow 400, operations performed by the device may be performed in a different order or at a different time. Additionally or alternatively, some operations may also be omitted from process flow 400 and other operations may be added to process flow 400.

[0109] At 405, the network entity 105-b may send a message to the UE 115-d including an indication of a set of beams associated with PEI monitoring (e.g., a beam index). For example, the network entity 105-b may send the indication of the set of beams in a SIB (e.g., an NTN-specific SIB). In some examples, the indication of the set of beams may include a set of one or more SSB beams, an index corresponding to the set of one or more SSB beams, or both. In some cases, the network entity 105-b may send a message (e.g., a SIB) including a last used beam only indication. If the resident beam of the UE 115-d is the beam in which the last connection of the UE 115-d was released (i.e., the resident beam is the last used beam of the UE 115-d), the last used beam only indication may indicate that the UE 115-d monitors the PEI using the resident beam (e.g., the beam of the network entity 105-b on which the UE 115-d is resident).

[0110] At 410, the UE 115-d may determine a beam set associated with PEI monitoring. For example, the UE 115-d may obtain an indication associated with a resident beam (e.g., a beam of the network entity 105-b on which the UE 115-d is resident), the indication indicating the beam set associated with PEI monitoring. In some cases, the UE 115-d may obtain the indication associated with the resident beam set based on a message received from the network entity 105-b containing the indication. Alternatively, the UE 115-d may autonomously determine the indication of the beam set. For example, the network entity 105-b may have sent previous signaling to the UE 115-d indicating information about the beams of the network entity 105-b (e.g., a set of SSB beams and corresponding indices), which may assist the UE 115-d in determining beams adjacent to the current resident beam. The beam set may be a dwelling beam, and in some cases, the beam set may additionally include one or more neighboring beams (e.g., beams with consecutive beam indices) that are adjacent to the dwelling beam. In some examples, the UE 115-d may determine the beam set based on previous signaling from the network entity 105-b, a technical specification (e.g., a pre-configured specification), or a combination thereof.

[0111] At 415, UE 115-d may determine that the last used beam of UE 115-d is included in the beam set. For example, UE 115-d may determine that the last used beam of UE 115-d is included in the beam set based on the index of the last used beam. In some examples, UE 115-d may store the last used beam information after the connection is released, and UE 115-d may read the stored information to determine whether the last used beam is included in the beam set. UE 115-d may determine to monitor PEI via the dwell beam based on the last used beam of UE 115-d being included in the beam set.

[0112] At 420, UE 115-d may monitor for paging messages (e.g., PEI) via the dwelling beam based on the last used beam of UE 115-d being included in the beam set. Network entity 105-b may send a PEI, which may indicate a paging subgroup. For example, network entity 105-b may determine that a paging message is to be sent to UE 115-d, and the last used beam of UE 115-d is included in the beam set. Network entity 105-b may then send a PEI indicating a paging subgroup corresponding to UE 115-d via the dwelling beam.

[0113] At 425, the network entity 105-b may send a paging message during the PO of the UE 115-d. The UE 115-d may monitor the PO for the paging message, for example, based on receiving the PEI.

[0114] Figure 5 An example of a process flow 500 for supporting PEI in an NTN according to one or more aspects of the present disclosure is illustrated. The process flow 500 may be described in reference to Figure 1 and Figure 3 The process flow 500 may include a UE 115-e, which may be a wireless communication system 100 or a wireless communication system 300 as described above. Figures 1 to 4 The example of UE 115 described herein may include a first network entity 105-c, which may be as described in reference Figures 1 to 4 An example of a network entity 105 is described. In the following description of process flow 500, operations performed by the device may be performed in a different order or at a different time. Additionally or alternatively, some operations may be omitted from process flow 500 and other operations may be added to process flow 500.

[0115] At 505, the network entity 105-c may send a message to the UE 115-e including an indication of a set of beams associated with PEI monitoring (e.g., a beam index). For example, the network entity 105-c may send the indication of the set of beams in a SIB (e.g., an NTN-specific SIB). In some examples, the indication of the set of beams may include a set of one or more SSB beams, an index corresponding to the set of one or more SSB beams, or both. In some cases, the network entity 105-c may send a message (e.g., a SIB) including a last used beam only indication. If the resident beam of the UE 115-e is the beam in which the last connection of the UE 115-e was released (i.e., the resident beam is the last used beam of the UE 115-e), the last used beam only indication may indicate that the UE 115-e uses the resident beam (e.g., the beam of the network entity 105-c on which the UE 115-e is resident) to monitor PEI.

[0116] At 510, the UE 115-e may determine a beam set associated with PEI monitoring. For example, the UE 115-e may obtain an indication associated with a resident beam (e.g., a beam of the network entity 105-c on which the UE 115-e is resident), the indication indicating the beam set associated with PEI monitoring. In some cases, the UE 115-e may obtain the indication associated with the resident beam beam set based on a message received from the network entity 105-c containing the indication. Alternatively, the UE 115-e may autonomously determine the indication of the beam set. For example, the network entity 105-c may have sent previous signaling to the UE 115-e indicating information about the beams of the network entity 105-c (e.g., a set of SSB beams and corresponding indices), which may assist the UE 115-e in determining beams adjacent to the current resident beam. The beam set may be a dwelling beam, and in some cases, the beam set may additionally include one or more neighboring beams (e.g., beams with consecutive beam indices) that are adjacent to the dwelling beam. In some examples, the UE 115-e may determine the beam set based on previous signaling from the network entity 105-c, a technical specification (e.g., a pre-configured specification), or a combination thereof.

[0117] At 515, UE 115-e may determine that the last used beam of UE 115-e is excluded from the beam set (e.g., is not within the beam set). For example, UE 115-e may determine that the last used beam of UE 115-e is not included in the beam set based on the index of the last used beam. In some examples, UE 115-e may store the last used beam information after the connection is released, and UE 115-e may read the stored information to determine whether the last used beam is included in the beam set. UE 115-e may determine to skip monitoring PEI via the current resident beam based on the last used beam of UE 115-e being excluded from the beam set.

[0118] At 520, UE 115-e may refrain from monitoring PEI based on the last used beam of UE 115-e being excluded from the beam set. Additionally, network entity 105-c may refrain from sending PEI indicating a paging subgroup for UE 115-e. For example, network entity 105-c may determine that a paging message is to be sent to UE 115-e, and network entity 105-c may determine that the last used beam of UE 115-e is not included in the beam set associated with the dwell beam of UE 115-e. Therefore, network entity 105-c may skip sending PEI for UE 115-e via the dwell beam of UE 115-e.

[0119] At 525, the network entity 105-c may send a paging message during the PO of the UE 115-e. Despite not monitoring and not detecting the PEI in response to determining that the last used beam is not within the beam set associated with the camp beam of the UE 115-e, the UE 115-e may still monitor the PO for the paging message.

[0120] Figure 6 A block diagram 600 of a device 605 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0121] The receiver 610 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to PEI in NTN), user data, control information, or any combination thereof. The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0122] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to PEI in NTN), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0123] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of components for performing various aspects of the PEI in the NTN as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0124] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0125] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0126] In some examples, communication manager 620 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 610, transmitter 615, or both. For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in conjunction with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0127] According to examples as disclosed herein, the communication manager 620 may support wireless communication at the UE. For example, the communication manager 620 may be configured to or otherwise support a component for communicating a connection release message to release a connection via a first beam associated with communication between the UE and a network entity. The communication manager 620 may be configured to or otherwise support a component for obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with the PEI. The communication manager 620 may be configured to or otherwise support a component for monitoring a paging message via a second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0128] By including or configuring a communication manager 620 according to examples as described herein, a device 605 (e.g., a processor controlling or otherwise coupled with a receiver 610, a transmitter 615, a communication manager 620, or a combination thereof) may support techniques for performing PEI transmission in an NTN with reduced power consumption and by more efficiently utilizing communication resources.

[0129] Figure 7 A block diagram 700 of a device 705 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0130] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to PEI in NTN), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0131] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to PEI in NTN), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0132] Device 705 or its various components may be examples of components for performing various aspects of PEI in NTN as described herein. For example, communication manager 720 may include connection release component 725, indication component 730, paging message manager 735, or any combination thereof. Communication manager 720 may be an example of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 710, transmitter 715, or both. For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or integrate with receiver 710, transmitter 715, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0133] According to examples as disclosed herein, the communication manager 720 may support wireless communication at the UE. The connection release component 725 may be configured to or otherwise support means for communicating a connection release message to release a connection via a first beam associated with communication between the UE and a network entity. The indication component 730 may be configured to or otherwise support means for obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with the PEI. The paging message manager 735 may be configured to or otherwise support means for monitoring a paging message via a second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0134] Figure 8 A block diagram 800 of a communication manager 820 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of PEI in an NTN as described herein. For example, the communication manager 820 may include a connection release component 825, an indication component 830, a paging message manager 835, a PEI monitoring component 840, an additional beam component 845, a DCI monitoring component 850, a last used beam component 855, a beam information storage manager 860, a system information receiver 865, a beam selection manager 870, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0135] According to examples as disclosed herein, the communication manager 820 may support wireless communication at the UE. The connection release component 825 may be configured to or otherwise support means for communicating a connection release message to release a connection via a first beam associated with communication between the UE and a network entity. The indication component 830 may be configured to or otherwise support means for obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with the PEI. The paging message manager 835 may be configured to or otherwise support means for monitoring a paging message via a second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0136] In some examples, PEI monitoring component 840 can be configured or otherwise support components for monitoring PEI via a second beam based on the first beam being included in a set of one or more beams.

[0137] In some examples, DCI monitoring component 850 can be configured or otherwise support components for monitoring downlink control information associated with PO using a second beam based on receiving PEI. In some examples, the first beam and the second beam are the same.

[0138] In some examples, the additional beam component 845 may be configured as or otherwise support components for receiving indications of one or more additional beams from a network entity, the one or more additional beams and the second beam having adjacent beam coverage areas, the set of one or more beams including the second beam and the one or more additional beams.

[0139] In some examples, the DCI monitoring component 850 may be configured to or otherwise support components for monitoring downlink control information associated with the PO via a second beam based on the first beam being excluded from a set of one or more beams.

[0140] In some examples, the last used beam component 855 may be configured to or otherwise support components for receiving only a last used beam indication from a network entity, wherein the indication associated with the second beam is obtained based on only the last used beam indication.

[0141] In some examples, beam information storage manager 860 can be configured to or otherwise support components for storing an indication of a first beam associated with a recent communication between the UE and a network entity, wherein the paging message is monitored based on the stored indication of the first beam. In some examples, the first beam is associated with a recent communication between the UE and the network entity.

[0142] In some examples, the system information receiver 865 may be configured or otherwise support components for receiving a system information block from a network entity and via a second beam, the system information block indicating a set of one or more beams associated with the PEI.

[0143] In some examples, the beam selection manager 870 may be configured or otherwise support means for selecting a third beam as a dwell beam for monitoring one or more channels associated with a network entity (e.g., a dwell beam of a UE). In some examples, the system information receiver 865 may be configured or otherwise support means for receiving a system information block from the network entity and via the third beam, the system information block indicating a second set of one or more beams associated with the PEI.

[0144] Fig. 9A diagram of a system 900 including a device 905 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein, or include components thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

[0145] I / O controller 910 may manage input and output signals for device 905. I / O controller 910 may also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® , MS-DOS ® 、MS-WINDOWS ® , OS / 2 ® ,UNIX ® 、LINUX ® or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0146] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired or wireless link, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

[0147] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 935 may not be directly executable by the processor 940, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may also contain, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0148] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to enable the device 905 to perform various functions (e.g., functions or tasks supporting PEI in the NTN). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform various functions described herein.

[0149] According to examples as disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support a component for communicating a connection release message to release a connection via a first beam associated with communication between the UE and a network entity. The communication manager 920 may be configured to or otherwise support a component for obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with the PEI. The communication manager 920 may be configured to or otherwise support a component for monitoring a paging message via a second beam based on whether the first beam is included in the set of one or more beams associated with the PEI.

[0150] By including or configuring the communication manager 920 according to examples as described herein, the device 905 may support techniques for PEI transmission in an NTN with reduced power consumption and by more efficiently utilizing communication resources.

[0151] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of the PEI in the NTN as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0152] Fig.10 A block diagram 1000 of a device 1005 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0153] The receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0154] The transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1005. For example, the transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0155] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of components for performing various aspects of PEI in NTN as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0156] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0157] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0158] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0159] According to examples as disclosed herein, the communication manager 1020 may support wireless communication at a network entity. For example, the communication manager 1020 may be configured to or otherwise support components for communicating a connection release message via a first beam to release a connection associated with the UE. The communication manager 1020 may be configured to or otherwise support components for determining a set of one or more beams associated with the second beam and the PEI. The communication manager 1020 may be configured to or otherwise support components for outputting the PEI based on the set of one or more beams associated with the PEI.

[0160] By including or configuring a communication manager 1020 according to examples as described herein, a device 1005 (e.g., a processor controlling or otherwise coupled with a receiver 1010, a transmitter 1015, a communication manager 1020, or a combination thereof) may support techniques for performing PEI transmission in an NTN with reduced power consumption and by more efficiently utilizing communication resources.

[0161] Fig.11 A block diagram 1100 of a device 1105 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0162] The receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0163] The transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)). In some examples, the transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0164] The device 1105 or its various components may be examples of components for performing various aspects of PEI in NTN as described herein. For example, the communication manager 1120 may include a connection release manager 1125, a beam determination component 1130, a PEI output manager 1135, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0165] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The connection release manager 1125 may be configured to or otherwise support components for communicating a connection release message via a first beam to release a connection associated with the UE. The beam determination component 1130 may be configured to or otherwise support components for determining a set of one or more beams associated with the second beam and the PEI. The PEI output manager 1135 may be configured to or otherwise support components for outputting the PEI based on the set of one or more beams associated with the PEI.

[0166] Fig.12A block diagram 1200 of a communication manager 1220 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The communication manager 1220 can be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components can be examples of components for performing various aspects of PEI in an NTN as described herein. For example, the communication manager 1220 may include a connection release manager 1225, a beam determination component 1230, a PEI output manager 1235, a beam indication component 1240, a last used beam output component 1245, a beam storage manager 1250, a control message component 1255, a system information output manager 1260, an additional beam manager 1265, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0167] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The connection release manager 1225 may be configured to or otherwise support components for communicating a connection release message via a first beam to release a connection associated with the UE. The beam determination component 1230 may be configured to or otherwise support components for determining a set of one or more beams associated with the second beam and the PEI. The PEI output manager 1235 may be configured to or otherwise support components for outputting the PEI based on the set of one or more beams associated with the PEI.

[0168] In some examples, beam indication component 1240 may be configured as or otherwise support components for outputting an indication of a set of one or more beams to a UE and via a second beam.

[0169] In some examples, to support outputting an indication of a set of one or more beams, system information output manager 1260 may be configured as or otherwise support components for outputting a system information block indicating a set of one or more beams associated with a PEI.

[0170] In some examples, the last used beam output component 1245 may be configured or otherwise support components for outputting only last used beam indications, wherein a set of one or more beams associated with the PEI is determined based on the only last used beam indications being output.

[0171] In some examples, PEI output manager 1235 may be configured or otherwise support components for outputting the PEI using the second beam based on the first beam being included in a set of one or more beams associated with the PEI.

[0172] In some examples, the additional beam manager 1265 may be configured to or otherwise support components for outputting an indication of one or more additional beams, the one or more additional beams and the second beam having adjacent beam coverage areas, wherein the set of one or more beams includes the second beam and the one or more additional beams. In some examples, the first beam and the second beam are the same. In some examples, the first beam is associated with a most recent transmission between the UE and the network entity.

[0173] In some examples, beam storage manager 1250 can be configured or otherwise support components for storing an indication of a first beam, wherein the PEI is output based on storing the indication of the first beam.

[0174] In some examples, control message component 1255 can be configured or otherwise support components for outputting control messages during PO based on output PEI.

[0175] Fig.13 A diagram of a system 1300 including a device 1305 supporting PEI in an NTN according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0176] As described herein, the transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem for modulating a signal, thereby providing a modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1315, from a wired receiver), and for demodulating a signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmitting operations or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components that are operable to: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

[0177] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0178] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1325) to enable the device 1305 to perform various functions (e.g., functions or tasks supporting PEI in the NTN). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform various functions described herein. The processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, a virtual machine, or a container instance)), which may host functions for performing functions of the device 1305 (e.g., by executing code 1330). The processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as in the memory 1325). In some specific implementations, the processor 1335 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce an output set (the output set may be passed to, for example, other systems or components of the device 1305). For example, the processing system of the device 1305 may refer to a system including various other components or subcomponents of the device 1305, such as the processor 1335, or the transceiver 1310, or the communication manager 1320, or other components or combinations of components of the device 1305. The processing system of the device 1305 may interface with other components of the device 1305 and may process information (such as input or signals) received from other components or output information to other components. For example, a chip or modem of the device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1305 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system and a receiver of a chip or modem, such that the device 1305 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0179] In some examples, bus 1340 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305, or communications performed between different components of device 1305 that may be co-located or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one component of different components or divided between different components).

[0180] In some examples, the communication manager 1320 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1320 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1320 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 1320 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0181] According to examples as disclosed herein, the communication manager 1320 may support wireless communication at a network entity. For example, the communication manager 1320 may be configured to or otherwise support components for communicating a connection release message via a first beam to release a connection associated with the UE. The communication manager 1320 may be configured to or otherwise support components for determining a set of one or more beams associated with the second beam and the PEI. The communication manager 1320 may be configured to or otherwise support components for outputting the PEI based on the set of one or more beams associated with the PEI.

[0182] By including or configuring the communication manager 1320 according to examples as described herein, the device 1305 may support techniques for PEI transmission in an NTN with reduced power consumption and by more efficiently utilizing communication resources.

[0183] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of the PEI in the NTN as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0184] Fig.14 1400 is a flowchart illustrating a method 1400 for supporting PEI in NTN according to one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0185] At 1405, the method may include: communicating a connection release message via a first beam associated with communication between the UE and the network entity to release the connection. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described connection release component 825 is performed.

[0186] At 1410, the method may include obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with the PEI. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The description instructs component 830 to perform.

[0187] At 1415, the method may also include: monitoring the paging message via the second beam based on whether the first beam is included in the set of one or more beams associated with the PEI. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The paging message manager 835 described above is executed.

[0188] Fig.15 1 is a flowchart illustrating a method 1500 for supporting PEI in NTN according to one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be used to perform. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0189] At 1505, the method may include: communicating a connection release message via a first beam associated with communication between the UE and the network entity to release the connection. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The described connection release component 825 is performed.

[0190] At 1510, the method may include obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with the PEI. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The description instructs component 830 to perform.

[0191] At 1515, the method may also include: monitoring the paging message via the second beam based on whether the first beam is included in the set of one or more beams associated with the PEI. The operations of 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The paging message manager 835 described above is executed.

[0192] At 1520, the method may include: based on the first beam being included in the set of one or more beams, monitoring the PEI via the second beam. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figure 8 The PEI monitoring component 840 described above is executed.

[0193] At 1525, the method may include: monitoring downlink control information associated with the PO using a second beam based on receiving the PEI. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figure 8 The DCI monitoring component 850 described above is performed.

[0194] Fig.16 1 is a flowchart illustrating a method 1600 for supporting PEI in NTN according to one or more aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 The UE 115 described herein may be used to perform. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0195] At 1605, the method may include: communicating a connection release message via a first beam associated with communication between the UE and the network entity to release the connection. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The described connection release component 825 is performed.

[0196] At 1610, the method may include obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with the PEI. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 8 The description instructs component 830 to perform.

[0197] At 1615, the method may also include: monitoring the paging message via the second beam based on whether the first beam is included in the set of one or more beams associated with the PEI. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The paging message manager 835 described above is executed.

[0198] At 1620, the method may include: based on the first beam being excluded from the set of one or more beams, monitoring downlink control information associated with the PO via the second beam. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 8 The DCI monitoring component 850 described above is performed.

[0199] Fig.17 1 is a flowchart illustrating a method 1700 for supporting PEI in an NTN according to one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 as well as Figures 10 to 13In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0200] At 1705, the method may include: communicating a connection release message via the first beam to release a connection associated with the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The connection release manager 1225 described above is executed.

[0201] At 1710, the method may include determining a set of one or more beams associated with the second beam and the PEI. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The beam determination component 1230 described above is performed.

[0202] At 1715, the method may include: outputting the PEI based on a set of one or more beams associated with the PEI. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.12 The PEI output manager 1235 described above is executed.

[0203] Fig.18 1 is a flowchart illustrating a method 1800 for supporting PEI in an NTN according to one or more aspects of the present disclosure. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0204] At 1805, the method may include: communicating a connection release message via the first beam to release a connection associated with the UE. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The connection release manager 1225 described above is executed.

[0205] At 1810, the method may include determining a set of one or more beams associated with the second beam and the PEI. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.12 The beam determination component 1230 described above is performed.

[0206] At 1815, the method may include: outputting the PEI based on a set of one or more beams associated with the PEI. The operations of 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference Fig.12 The PEI output manager 1235 described above is executed.

[0207] At 1820, the method may include: outputting an indication of a set of one or more beams to the UE and via the second beam. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.12 The beam indication component 1240 described above is performed.

[0208] Fig.19 1 is a flowchart illustrating a method 1900 for supporting PEI in an NTN according to one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0209] At 1905, the method may include: communicating a connection release message via the first beam to release a connection associated with the UE. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.12 The connection release manager 1225 described above is executed.

[0210] At 1910, the method may include determining a set of one or more beams associated with a second beam and a PEI. The operations of 1910 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.12 The beam determination component 1230 described above is performed.

[0211] At 1915, the method may include: outputting the PEI based on a set of one or more beams associated with the PEI. The operations of 1915 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.12 The PEI output manager 1235 described above is executed.

[0212] At 1920, the method may include: outputting only the last used beam indication, wherein a set of one or more beams associated with the PEI is determined based on the only last used beam indication being output. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be described with reference to Fig.12 The last described is performed using the beam output component 1245 .

[0213] The following provides an overview of various aspects of the disclosure:

[0214] Aspect 1: A method for wireless communication at a UE, the method comprising: communicating a connection release message to release a connection via a first beam associated with communication between the UE and a network entity; obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with a PEI; and monitoring a paging message via the second beam based at least in part on whether the first beam is included in the set of one or more beams associated with the PEI.

[0215] Aspect 2: According to the method of aspect 1, monitoring the paging message includes: monitoring the PEI via the second beam at least in part based on the first beam being included in the set of one or more beams.

[0216] Aspect 3: The method according to aspect 2 further includes: using the second beam to monitor DCI associated with PO based at least in part on receiving the PEI.

[0217] Aspect 4: The method according to any one of aspects 2 to 3, wherein the first beam and the second beam are the same.

[0218] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: receiving an indication of one or more additional beams from the network entity, the one or more additional beams and the second beam having adjacent beam coverage areas, and the set of one or more beams includes the second beam and the one or more additional beams.

[0219] Aspect 6: According to the method described in any one of Aspects 1, 4 and 5, monitoring the paging message includes: monitoring the DCI associated with the PO via the second beam, at least in part based on the first beam being excluded from the set of one or more beams.

[0220] Aspect 7: According to the method according to any one of Aspects 1 to 6, the method also includes: receiving an indication of only the last used beam from the network entity, wherein the indication associated with the second beam is obtained at least in part based on the indication of only the last used beam.

[0221] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method also includes: storing an indication of the first beam associated with the most recent communication between the UE and the network entity, wherein the paging message is monitored at least in part based on the stored indication of the first beam.

[0222] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the first beam is associated with a recent communication between the UE and the network entity.

[0223] Aspect 10: According to the method described in any one of Aspects 1 to 9, obtaining the indication of the set of one or more beams includes: receiving a SIB from a network entity and via the second beam, the SIB indicating the set of one or more beams associated with the PEI.

[0224] Aspect 11: According to the method described in Aspect 10, the method also includes: selecting a third beam as the resident beam of the UE for monitoring one or more channels associated with the network entity; and receiving an SIB from the network entity and via the third beam, the SIB indicating a second set of one or more beams associated with the PEI.

[0225] Aspect 12: A method for wireless communication at a network entity, the method comprising: communicating a connection release message via a first beam to release a connection associated with a UE; determining a set of one or more beams associated with a second beam and a PEI; and outputting the PEI based at least in part on the set of one or more beams associated with the PEI.

[0226] Aspect 13: The method according to aspect 12 further comprises: outputting an indication of the set of one or more beams to the UE and via the second beam.

[0227] Aspect 14: The method according to aspect 13, wherein outputting the indication of the set of one or more beams further comprises: outputting a SIB indicating the set of one or more beams associated with the PEI.

[0228] Aspect 15: According to the method described in any one of Aspects 12 to 14, the method further includes: outputting an indication of only the last used beam, wherein the set of one or more beams associated with the PEI is determined at least in part based on the indication of only the last used beam being output.

[0229] Aspect 16: According to the method of any one of Aspects 12 to 15, outputting the PEI includes: outputting the PEI using the second beam based at least in part on the first beam being included in the set of one or more beams associated with the PEI.

[0230] Aspect 17: According to the method of Aspect 16, the method also includes: outputting an indication of one or more additional beams, the one or more additional beams and the second beam having adjacent beam coverage areas, wherein the set of the one or more beams includes the second beam and the one or more additional beams.

[0231] Aspect 18: The method according to any one of aspects 12 to 17, wherein the first beam and the second beam are the same.

[0232] Aspect 19: A method according to any one of Aspects 12 to 18, wherein the first beam is associated with a most recent transmission between the UE and the network entity.

[0233] Aspect 20: The method according to any one of aspects 12 to 19, the method further comprising: storing an indication of the first beam, wherein the PEI is outputted based at least in part on storing the indication of the first beam.

[0234] Aspect 21: The method according to any one of aspects 12 to 20, further comprising: outputting a control message during PO based at least in part on outputting the PEI.

[0235] Aspect 22: An apparatus for performing wireless communication at a UE, the apparatus comprising: a processor; and a memory, the memory being coupled to the processor, the processor being configured to execute the method according to any one of aspects 1 to 11.

[0236] Aspect 23: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 11.

[0237] Aspect 24: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 11.

[0238] Aspect 25: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; and a memory, the memory coupled to the processor, the processor being configured to perform the method according to any one of aspects 12 to 21.

[0239] Aspect 26: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 12 to 21.

[0240] Aspect 27: A non-transitory computer-readable medium storing a code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method according to any one of aspects 12 to 21.

[0241] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0242] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0243] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0244] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0245] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features implementing the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0246] Computer-readable media include both non-transient computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-transient storage media can be any available media that can be accessed by a general or special computer. By way of example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or can be used to carry or store desired program code components in the form of instructions or data structures and any other non-transient media that can be accessed by a general or special computer or a general or special processor. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0247] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".

[0248] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like, etc. Furthermore, "determining" may include receiving (e.g., receiving information) and accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0249] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0250] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0251] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, wherein the processor is configured to: communicating a connection release message via a first beam associated with communication between the UE and a network entity to release the connection; obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with a paging early indication; and Monitoring a paging message via the second beam is performed based at least in part on whether the first beam is included in the set of one or more beams associated with the paging early indication.

2. The apparatus of claim 1 , wherein to monitor the paging message, the processor is configured to: Based at least in part on the first beam being included in the set of one or more beams, monitoring the paging early indication via the second beam.

3. The apparatus of claim 2, wherein the processor is further configured to: Based at least in part on receipt of the paging early indication, the second beam is used to monitor downlink control information associated with a paging occasion. The apparatus of claim 2 , wherein the first beam and the second beam are the same.

5. The apparatus of claim 1, wherein the processor is further configured to: An indication of one or more additional beams is received from the network entity, the one or more additional beams and the second beam having adjacent beam coverage areas, the set of one or more beams including the second beam and the one or more additional beams.

6. The apparatus of claim 1 , wherein to monitor the paging message, the processor is configured to: Based at least in part on the first beam being excluded from the set of one or more beams, downlink control information associated with a paging occasion is monitored via the second beam.

7. The apparatus of claim 1, wherein the processor is further configured to: A last used beam only indication is received from the network entity, wherein the indication associated with the second beam is obtained based at least in part on the last used beam only indication.

8. The apparatus of claim 1, wherein the processor is further configured to: An indication of the first beam associated with a most recent communication between the UE and the network entity is stored, wherein the paging message is monitored based at least in part on the stored indication of the first beam.

9. The apparatus of claim 1, wherein the first beam is associated with a most recent communication between the UE and the network entity.

10. The apparatus of claim 1, wherein to obtain the indication associated with the second beam, the processor is configured to: A system information block is received from a network entity and via the second beam, the system information block indicating the set of one or more beams associated with the paging early indication.

11. The apparatus of claim 10, wherein the processor is further configured to: selecting a third beam as a dwell beam for monitoring one or more channels associated with the network entity; and A system information block is received from a network entity and via the third beam, the system information block indicating a second set of one or more beams associated with the paging early indication.

12. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor, wherein the processor is configured to: communicating a connection release message via a first beam to release a connection associated with a user equipment (UE); determining a set of one or more beams associated with the second beam and the paging early indication; and The paging early indication is output based at least in part on the set of one or more beams associated with the paging early indication.

13. The apparatus of claim 12, wherein the processor is further configured to: An indication of the set of one or more beams is output to the UE and via the second beam.

14. The apparatus of claim 12, wherein the processor is further configured to: A last used beam only indication is output, wherein the set of one or more beams associated with the paging early indication is determined based at least in part on the last used beam only indication being output.

15. The apparatus of claim 12, wherein to output the paging early indication, the processor is configured to: Based at least in part on the first beam being included in the set of one or more beams associated with the paging early indication, the paging early indication is output using the second beam.

16. The apparatus of claim 15, wherein the processor is further configured to: An indication of one or more additional beams is output, the one or more additional beams and the second beam having adjacent beam coverage areas, wherein the set of one or more beams includes the second beam and the one or more additional beams.

17. The apparatus of claim 12, wherein the first beam and the second beam are the same.

18. The apparatus of claim 12, wherein the first beam is associated with a most recent transmission between the UE and the network entity.

19. The apparatus of claim 12, wherein the processor is further configured to: An indication of the first beam is stored, wherein the paging early indication is output based at least in part on storing the indication of the first beam.

20. A method for wireless communication at a user equipment (UE), the method comprising: communicating a connection release message via a first beam associated with communication between the UE and a network entity to release the connection; obtaining an indication associated with a second beam, the indication indicating a set of one or more beams associated with a paging early indication; and Monitoring a paging message via the second beam is performed based at least in part on whether the first beam is included in the set of one or more beams associated with the paging early indication.

Images