Paging techniques for wireless devices with hybrid capabilities

Abstract

Methods, systems, and devices are described for wireless communication in which a user equipment (UE) may monitor one or more paging messages based on a paging early indication (PEI) and whether the UE operates according to a first bandwidth configuration or a second bandwidth configuration. The UE may decode the PEI and determine whether to monitor one or more subsequent paging messages based on one or more fields of the PEI. The PEI may include one or more fields associated with different UE types, the fields indicating one or more UE subgroup identifications for which the associated paging message is to be monitored, where different subgroup identifications are associated with different UE types.

Description

[0001] Cross-reference

[0002] This patent application claims the benefit of International Application PCT / CN2022 / 126067, filed on October 19, 2022 by Lei et al. and entitled "PAGING TECHNIQUES FOR WIRELESS DEVICES WITH MIXED CAPABILITIES", which is assigned to the assignee of the present application. The entire disclosure of this international application is incorporated herein by reference. Technical Field

[0003] The following relates to wireless communication, including paging techniques for wireless devices with mixed capabilities. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and so on. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, LTE-Advanced (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 multi-access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0005] In some wireless communication systems, to reduce power consumption, a Discontinuous Reception (DRX) cycle may be configured at a wireless device, where the wireless device switches between a lower power state and a higher power state at specific intervals. In some cases, when in the higher power state, the wireless device may monitor paging messages indicating that the device has information to convey, and the device may change the timing of the higher power state based on these paging messages. Enhanced techniques for monitoring such paging messages may help further reduce power consumption and improve system efficiency. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatus for supporting paging techniques for wireless devices with hybrid capabilities. For example, the described technology provides that a user equipment (UE) may monitor one or more paging communications based on whether the UE is operating according to a first bandwidth configuration or a second bandwidth configuration, where the first bandwidth configuration and the second bandwidth configuration have different receive bandwidths for one or more of the paging communications. According to some aspects, in a discontinuous reception (DRX) cycle, a network entity may send control signaling providing a paging early indication (PEI), and the UE may receive the control signaling. The UE may decode the PEI and determine whether to monitor one or more subsequent paging communications based on the PEI.

[0007] In some aspects, a single PEI may include one or more fields associated with different UE types, such that the PEI includes a first UE subgroup identification (ID) field for a UE ID or UE class ID that may be signaled together with the PEI, and one or more of a second UE subgroup ID field or a third UE subgroup ID field for UEs operating with a reduced bandwidth (e.g., low-layer UEs). In some cases, the second UE subgroup ID field may indicate a subgroup ID assigned by a core network entity via non-access stratum (NAS) signaling. Additionally or alternatively, the third UE subgroup ID field may indicate a subgroup ID assigned by the serving network entity of the UE. In some aspects, separate PEIs may be sent for different UE types. In some cases, separate physical control resource sets (CORESETs) associated with different UE types may be configured for the separate PEIs. In some cases, separate search space sets may be configured for different UE types, different radio network temporary identifiers (RNTIs) may be configured for different UE types, or different demodulation reference signals (DMRSs) or waveforms may be configured for different UE types.

[0008] In some other aspects, the PEI may include a status indication for each of two or more subgroups associated with the UE ID or UE class ID indicated in the PEI. In some cases, the status indication may be a two-bit status indication that indicates whether the associated paging message is for a UE with a first bandwidth configuration, a second bandwidth configuration, any bandwidth configuration, or a UE without a UE ID or UE class ID. In some other aspects, information may be included in a paging control channel transmission (e.g., a paging physical downlink control channel (PDCCH)) that provides resource allocation for a paging message shared channel communication (e.g., a paging physical downlink shared channel (PDSCH)). In such cases, the paging control channel transmission may indicate the type of UE paged in the paging message, such as by using a two-bit status indication. UEs not indicated to monitor the shared channel for paging messages may terminate paging message decoding to save power. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 Examples of wireless communication systems that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0010] Figure 2 Examples of a portion of a wireless communication system that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0011] Figure 3A and Figure 3B Examples of paging transmission schemes that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0012] Figure 4 Examples of paging transmission schemes that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0013] Figure 5 Examples of PEI structures that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0014] Figure 6 Examples of process flows that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0015] Figure 7 Examples of process flows that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0016] Figure 8 Examples of process flows that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0017] Figure 9A and Figure 9B Examples of PEI resources that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0018] Figure 10 and Figure 11 Examples of block diagrams of devices that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated.

[0019] Figure 12A block diagram of a communication manager that illustrates paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure.

[0020] Figure 13 A diagram of a system that includes a device that illustrates paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure.

[0021] Figure 14 and Figure 15 A block diagram of a device that illustrates paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure.

[0022] Figure 16 A block diagram of a communication manager that illustrates paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure.

[0023] Figure 17 A diagram of a system that includes a device that illustrates paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure.

[0024] Figures 18 to 26 A flowchart that illustrates a method for supporting paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. Detailed Description

[0025] During wireless communication, a network entity may convey to a User Equipment (UE) that a paging message will be delivered to the UE in a paging occasion (PO) associated with a discontinuous reception (DRX) cycle. Such paging messages can be used to notify the UE in idle or inactive mode of incoming data. To notify the UE of such paging messages, a Paging Early Indicator (PEI) field may be used in control signaling to indicate the paging occasion (PO) in which the UE can receive the paging message. Additionally or alternatively, a UE in such idle mode may also monitor short messages (e.g., system information messages, emergency notifications, or both). Such short messages may be included in further control signaling that schedules the paging message. Furthermore, in some deployments, there may be different types of UEs, including a first type of UE operating according to a first bandwidth configuration and a second type of UE operating according to a second bandwidth configuration. In the first bandwidth configuration, a first downlink bandwidth (e.g., 20 MHz downlink bandwidth) is used to transmit paging control channel messages (e.g., paging Physical Downlink Control Channel (PDCCH) messages) and paging shared channel messages (e.g., paging Physical Downlink Shared Channel (PDSCH) messages). In the second bandwidth configuration, the first downlink bandwidth (e.g., 20 MHz downlink bandwidth) is used to transmit paging control channel messages, and a second downlink bandwidth (e.g., 5 MHz downlink bandwidth) is used to transmit paging shared channel messages. The second type of UE may include, for example, a Reduced Capability (RedCap) UE with relatively low complexity and lower cost.

[0026] In the case where there are multiple different types of UEs, a downlink bandwidth corresponding to a lower supported downlink bandwidth of one or more device types can be used to send one or more paging messages (e.g., paging PDSCH messages). For example, if a second type of UE operates using a 5 MHz downlink bandwidth for paging PDSCH messages, the 5 MHz downlink bandwidth can be used to send at least some of the paging PDSCH messages in the paging PDSCH messages. However, compared to a first type of UE that operates using a 20 MHz bandwidth for all paging messages, the reduction in bandwidth may result in fewer UEs being paged in a particular DRX cycle. Therefore, in the case where a relatively large number of UEs are to be paged, some UEs may have to wait for multiple DRX cycles to receive the paging. For example, a UE can transition to a higher power consumption state of the DRX cycle to monitor for paging, and due to the relatively low bandwidth of the paging message, the UE can actually receive the paging message in a subsequent DRX cycle, which is one or more DRX cycles after the initial DRX cycle, and the initial DRX cycle corresponds to the time when the paging could be sent if a larger downlink bandwidth were used. In such cases, the UE wakes up and monitors the paging PDCCH in each DRX cycle, which consumes power at the UE and increases the latency of communication. Additionally, if the UE is able to monitor the PEI, the UE can skip the monitoring and decoding of some POs based on the PEI indication. However, in the case where there are multiple different types of UEs, the existing PEI signaling does not provide an indication related to the type of UE being paged. Therefore, even when implementing the PEI technology, a deployment using multiple types of UEs with multiple different bandwidth configurations may result in increased power consumption of some UEs.

[0027] According to various aspects discussed herein, to reduce or eliminate such drawbacks of other methods, a UE can receive control signaling including a PEI field that can be associated with a PO, and the PEI field can indicate whether a UE with a specific bandwidth configuration is to monitor for paging messages in the associated PO. In some aspects, the UE can monitor one or more paging communications based on whether the UE operates according to a first bandwidth configuration or a second bandwidth configuration, where the first bandwidth configuration and the second bandwidth configuration have different receive bandwidths for one or more of these paging communications (e.g., a 20 MHz downlink bandwidth for paging PDSCH for the first bandwidth configuration and a 5 MHz downlink bandwidth for paging PDSCH for the second bandwidth configuration). According to some aspects, in a DRX cycle, a network entity can send control signaling providing the PEI, and the UE can receive the control signaling. The UE can decode the PEI and determine whether to monitor one or more subsequent paging communications based on the PEI.

[0028] In some aspects, the PEI may include one or more fields associated with different UE types, such that the PEI includes a first UE subgroup identification (ID) field for a UE ID or UE class ID of a first subgroup of UEs that may be signaled together with the PEI, and one or more of a second UE subgroup ID field or a third UE subgroup ID field for UEs operating with reduced bandwidth (e.g., low-layer UEs or UEs of RedCap). In some cases, the second UE subgroup ID field may indicate a subgroup ID assigned by a core network entity via non-access stratum (NAS) signaling. Additionally or alternatively, the third UE subgroup ID field may indicate a subgroup ID assigned by a serving network entity of the UE.

[0029] In some other aspects, separate PEIs may be sent for different UE types. In some cases, a separate PEI may be configured with a separate control resource set (CORESET) associated with different UE types. In some cases, separate search space sets may be configured for different UE types, different radio network temporary identifiers (RNTIs) may be configured for different UE types, or different demodulation reference signals (DMRS) or waveforms may be configured for different UE types.

[0030] In some other aspects, the PEI may include a status indication for each of two or more subgroups associated with the UE ID or UE class ID indicated in the PEI. In some cases, the status indication may be a two-bit status indication that indicates whether the associated paging message is for a UE with a first bandwidth configuration, a second bandwidth configuration, any bandwidth configuration, or a UE without a UE ID or UE class ID. In some other aspects, information may be included in a paging control channel transmission (e.g., paging physical downlink control channel (PDCCH)) that provides resource allocation for paging message shared channel communication (e.g., paging physical downlink shared channel (PDSCH)). In such cases, the paging control channel transmission may indicate the type of UE being paged in the paging message, such as by using a two-bit status indication. UEs not indicated to monitor the shared channel for paging messages may terminate paging message decoding to save power.

[0031] The methods described herein provide various benefits to wireless communication, including reduced power consumption due to shorter wake-up times, reduced latency due to improved paging message timing, and precise indication of when a short message will be received by a UE. Additionally, the techniques discussed herein can reduce the consumption of processing resources (e.g., due to fewer blind decoding operations), which can provide enhanced system efficiency and an enhanced user experience.

[0032] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are then described in conjunction with exemplary paging transmission schemes, control signaling schemes, and process flows. Aspects of the present disclosure are further illustrated and described by reference to apparatus diagrams, system diagrams, and flowcharts related to paging techniques for wireless devices with hybrid capabilities.

[0033] Figure 1 An example of a wireless communication system 100 that supports paging techniques for wireless devices with hybrid capabilities in accordance with 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 a Long-Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0034] The network entities 105 may be dispersed throughout a geographical 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 names. In some examples, the network entities 105 and the UEs 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 geographical coverage area) within which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographical area within which the network entity 105 and the UEs 115 may support signal communication according to one or more radio access technologies (RATs).

[0035] 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 in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated. The UEs 115 described herein may be capable of supporting communication with various types of devices such as Figure 1 other UEs 115 or network entities 105 as shown.

[0036] 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, a device, an equipment, 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 yet 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 from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc. may include the disclosure of UE 115, network entity 105, device, equipment, computing system, etc. as nodes. For example, the disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0037] In some examples, network entity 105 may communicate with core network 130, or with each other, or both. For example, network entity 105 may communicate with 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, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical link, optical fiber link), one or more wireless links (e.g., radio link, wireless optical link), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155.

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

[0039] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., disaggregated base station architecture, disaggregated RAN architecture) that may be configured to utilize a protocol stack physically or logically distributed between two or more network entities 105 (such as an integrated access and backhaul (IAB) network, open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or virtualized RAN (vRAN) (e.g., 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., near-real-time RIC (near RT RIC), 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, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in a disaggregated 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 a disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0040] The functional split between the CU 160, DU 165, and RU 170 is flexible and can support different functions, depending on which functions are performed at the CU 160, DU 165, or RU 170 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof). For example, a functional split of the protocol stack can be employed between the CU 160 and DU 165 such that the CU 160 can support one or more layers of the protocol stack and the DU 165 can support one or more different layers of the protocol stack. In some examples, the CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 can be connected to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can 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) functions and signaling and can each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack can be employed between the DU 165 and RU 170 such that the DU 165 can support one or more layers of the protocol stack and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, the functional split between the CU 160 and DU 165 or between the DU 165 and RU 170 can be within a protocol layer (e.g., some functions of a protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of that protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU 160 can be connected to one or more DU 165s via an intermediate transport communication link 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RU 170s via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the intermediate transport communication link 162 or the fronthaul communication link 168 can be implemented according to the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the respective network entities 105 communicating via such communication links.

[0041] In some wireless communication systems (e.g., wireless communication system 100), the 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 node 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 the supported access and backhaul links (e.g., backhaul communication link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB donor. The IAB-MT may include a separate 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 communication links with additional entities (e.g., IAB nodes 104, UEs 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the split 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.

[0042] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), an IAB node 104, and one or more UEs 115. The IAB donor may facilitate the connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and a RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be an example of a part of the backhaul link), and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a part of the backhaul link).

[0043] The IAB node 104 may refer to a RAN node that provides IAB functions (e.g., access for UEs 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node towards the child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards the parent nodes associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay transmissions for UEs through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or a child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., the DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0044] For example, the IAB node 104 may be referred to as a parent node supporting communication for a child IAB node or as a child IAB node associated with an IAB donor or both. The IAB donor may include a CU 160 having a wired or wireless connection to the core network 130 (e.g., a fronthaul communication link 120) and may act as the parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, or may signal transmissions directly to the UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling over the NR Uu interface to the MT of the IAB node 104. Communication with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communication with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104.

[0045] In the context where the techniques described herein are applied to a split RAN architecture, one or more components of the split RAN architecture may be configured to support paging techniques for wireless devices with hybrid capabilities as described herein. For example, some operations described as being performed by the 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 split RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

[0046] The 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 "device" may also be referred to as a unit, a station, a terminal, or a client, etc. The 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, the 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.

[0047] The UE 115 described herein may be capable of communicating with various types of devices, such as other UE 115s that 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., asFigure 1 as shown

[0048] UE 115 and 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 set of RF spectrum resources having a physical layer structure defined to support communication link 125. For example, a carrier for communication link 125 may include a portion (e.g., bandwidth part (BWP)) of an RF spectrum band operating 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 operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, 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 network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of network entity 105. For example, the terms "transmit", "receive", or "communicate" when referring to network entity 105 may refer to any part of network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0049] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. A carrier may be associated with a frequency channel (e.g., evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by UE 115. A carrier may operate in an independent mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-independent mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

[0050] The communication link 125 shown in the wireless communication system 100 may include a downlink transmission (e.g., forward link transmission) from the network entity 105 to the UE 115, an uplink transmission (e.g., reverse link transmission) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink communication and uplink communication (e.g., in TDD mode).

[0051] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0052] The signal waveform transmitted via a carrier may include a plurality of subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing an MCM technique, a resource element may refer to the 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 amount of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such 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 space resources (e.g., spatial layers or beams), and the use of multiple space resources may increase the data rate or data integrity for communication with the UE 115.

[0053] The time interval for the network entity 105 or the UE 115 can be expressed as a multiple of a basic time unit, which may, for example, refer to the sampling period T s = 1 / (Δf max ·Nf ) seconds, where Δf max can represent the supported subcarrier spacing, and N f can represent the supported discrete Fourier transform (DFT) size. The time intervals of the communication resources can be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

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

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

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

[0057] In some examples, the network entity 105 (e.g., base station 140, RU 170) can be movable and thus provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different techniques can overlap, but different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different techniques can be supported by different network entities 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0058] Some UEs 115 (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC can include communication from devices with integrated sensors or meters to measure or obtain information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 can be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographical event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0059] Some UEs 115 can be configured to operate in power consumption-reducing modes, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not concurrent transmission and reception). In some examples, half-duplex communication can be performed with a reduced peak rate. Other energy-saving techniques for UEs 115 include: entering a power-saving deep sleep mode when not participating in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured to operate using a narrowband protocol type that is associated with a defined portion or range within a carrier, within a guard band of the carrier, or outside the carrier (e.g., a set of subcarriers or resource blocks (RBs)).

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

[0061] In some examples, the UE 115 may be configured to support direct communication 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 performing D2D communication in a group may be within the coverage area 110 of a network entity 105 (e.g., base station 140, RU 170), and this network entity may support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside 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, where each UE 115 transmits to each of the other UEs 115 in the group. In some examples, the network entity 105 may facilitate the scheduling of resources for D2D communication. In some other examples, D2D communication may be performed between UEs 115 without involving the network entity 105.

[0062] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as a roadside unit), or communicate with the network via vehicle-to-network (V2N) communication via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or both.

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

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

[0065] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can use an unlicensed band (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 an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 can employ carrier sensing for collision detection and avoidance. In some examples, the operation using the unlicensed band can be combined with a component carrier operating using a licensed band based on a carrier aggregation configuration (e.g., LAA). The operation using the unlicensed spectrum can include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or device-to-device (D2D) transmissions, etc.

[0066] The network entity 105 (e.g., base station 140, RU 170) or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or the UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operation 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, the 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 in multiple rows and columns that the network entity 105 may use for beamforming to support communication with the UE 115. Similarly, the UE 115 may include one or more antenna arrays, which may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0067] 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 transmitting device or a receiving device (e.g., network entity 105, UE 115) to shape or direct an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via the antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals conveyed via the antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment 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 transmitting device or the receiving device or relative to some other orientation).

[0068] In some embodiments, the UE 115 may receive control signaling (e.g., from the network entity 105) that may include one or more PEIs. Such PEIs may be associated with notifying the UE 115 that the UE 115 will receive one or more paging messages. In some aspects, the UE 115 may monitor one or more paging messages based on the PEI and whether the UE is operating according to a first bandwidth configuration or a second bandwidth configuration, where the first bandwidth configuration and the second bandwidth configuration have different reception bandwidths for one or more of the paging messages. According to some aspects, the UE 115 may decode a PEI transmitted in the PEI occasion of a DRX cycle and determine whether to monitor one or more subsequent paging communications based on one or more fields of the PEI. In some cases, a single PEI may include one or more fields associated with different UE types, such that the PEI includes a first UE subgroup ID field for a UE ID or UE class ID of a first subgroup of UEs that may be signaled together with the PEI, and one or more of a second UE subgroup ID field or a third UE subgroup ID field for a UE (e.g., a lower layer UE) of the UE as an associated type. In some cases, the second UE subgroup ID field may indicate a subgroup ID assigned by a core network entity (e.g., the CU 160 or the DU 165) via NAS signaling. Additionally or alternatively, the third UE subgroup ID field may indicate a subgroup ID assigned by a serving network entity of the UE 115 (e.g., the RU 170, the RIC 175, or the base station 140). In some aspects, separate PEIs may be transmitted for different UE types. In some cases, separate PEIs may be configured with separate CORESETs associated with different UE types. In some cases, separate search space sets may be configured for different UE types, different RNTIs may be configured for different UE types, or different DMRSs or waveforms may be configured for different UE types.

[0069] Figure 2 Illustrates an example of a wireless communication system 200 that supports paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. The wireless communication system 200 may include a network entity 105-a, which may be an example of one or more of the network entities discussed with respect to other figures. The wireless communication system 200 may include a UE 115-b, which may be an example of the UE discussed with respect to other figures.

[0070] As described herein, during wireless communication, network entity 105-a may have data to send to UE 115-a. However, due to power saving mode or other circumstances, UE 115-a may not be in the active mode for receiving data. Therefore, network entity 105-a may send a paging message to UE 115-a during the PO of the DRX cycle to indicate to UE 115-a that there is data waiting for UE 115-a or that UE 115-a will perform some other action with the wireless communication network. In some cases, network entity 105-a may notify UE 115-a of the paging message that will be received by using the PEI. Such PEI may be an example of control signaling communication 205, which may indicate to UE 115-a that UE 115-a will receive the paging message in one or more POs 210.

[0071] In some cases, the PEI may indicate multiple POs (e.g., up to eight POs or another number of POs), such as PO 210. Additionally, the PEI may indicate one or more paging subgroups that may be associated with the paging message within a PO such as PO 210. In some examples, a single PO may have multiple paging subgroups (e.g., up to eight paging subgroups or another number of paging subgroups).

[0072] Network entity 105-a may send the PEI to UE 115-a via the first control signaling 205 (e.g., DCI). The PEI may be indicated via one or more PEI fields 215 included in the first control signaling 205. For example, the PEI may include one or more paging indication fields mapped to one or more UE subgroups, where the one or more UE subgroups include a first set of paging subgroups of a first type of UE configured to support a first receive bandwidth configuration (e.g., having a 20 MHz downlink bandwidth for paging PDSCH messages) and a second set of paging subgroups of a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration (e.g., having a 5 MHz downlink bandwidth for paging PDSCH messages). Based on the PEI, UE 115-a may monitor the paging resources 220 of PO 210 for one or more paging communications 225 (e.g., paging PDCCH, paging PDSCH).

[0073] In some cases, one or more PEI fields may be associated with a subgroup ID assigned by a core network entity via NAS signaling. Additionally or alternatively, one or more PEI fields may indicate a subgroup ID assigned by a serving network entity such as network entity 105-a. In some other aspects, separate PEIs may be sent for different UE types. In such cases, the separate PEIs may be configured with separate control resource sets (CORESETs) associated with different UE types. Additionally or alternatively, separate search space sets may be configured for different UE types, different RNTIs may be configured for different UE types, or different DMRSs or waveforms may be configured for different UE types.

[0074] In some other aspects, the PEI may include a status indication for each of two or more subgroups associated with the UE ID or UE class ID indicated in the PEI. In some cases, the status indication may be a two-bit status indication that indicates whether the associated paging message is for a UE with a first bandwidth configuration, a second bandwidth configuration, any bandwidth configuration, or a UE without a UE ID or UE class ID. In some other aspects, the information may be included in a paging control channel transmission (e.g., paging PDCCH) that provides resource allocation for paging message shared channel communication (e.g., paging PDSCH). In such cases, the paging control channel transmission may indicate the type of UE being paged in the paging message, such as by using the two-bit status indication described above. In the case where UE 115-a is not indicated to monitor the shared channel for paging messages, UE 115-a may terminate paging message decoding to save power.

[0075] Figure 3A and Figure 3B Examples of paging transmission schemes 300 and 301 that support paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure are illustrated. Paging transmission schemes 300 and 301 may implement one or more aspects of wireless communication system 100 or wireless communication system 200, or may be implemented by them. For example, paging transmission schemes 300 and 301 may be implemented by UE 115 or network entity 105, both of which may be examples of corresponding devices as described in reference Figure 1 and Figure 2 described. In Figure 3A and Figure 3B example, network entity 105 may be an example of a CU, DU, RU, base station, IAB node, or one or more other network nodes as described in reference Figure 1 described.

[0076] In Figure 3AIn an example, the first paging message 305-a can be sent in the DRX cycle 320 using the first downlink bandwidth 310 (e.g., W MHz). In Figure 3A and Figure 3B In an example, the paging message 305 can have a first downlink bandwidth 310 corresponding to a legacy / advanced UE, which is larger than the bandwidth of a lower-layer or RedCap UE. In some cases, the first downlink bandwidth 310 can be a 20 MHz bandwidth (e.g., W = 20). In some cases, the first paging message 305-a can include an indication of small data transmission (SDT) 315-a for a UE (e.g., UE A). As described herein, in some deployments implementing the example of Figure 3A all UEs can support a reception bandwidth of up to W MHz for paging. In such cases, up to L paging records can be multiplexed in the paging message 305-a. Thus, if there are L UEs being paged (including UE A configured with mobile-terminated (MT) SDT), all UEs can receive the paging at the end of a single DRX cycle.

[0077] In Figure 3B In an example, there can be multiple different UE types, and the network entity can send a paging message 325 with a second bandwidth configuration that uses a second downlink bandwidth 330 different from the first downlink bandwidth 310. In some cases, the second downlink bandwidth 330 can be W / M MHz, where M is greater than 1. For example, the second downlink bandwidth 330 can be 5 MHz (e.g., W = 20 and M = 4). Additionally, there can be UEs that support a larger downlink bandwidth corresponding to the first downlink bandwidth and can receive the paging message 305, such as the UE that receives the second paging message 305-b in the third DRX cycle 320 in Figure 3B . Similar to that described with reference to Figure 3A in some cases, the second paging message 305-b can include an indication of SDT 315-b for a UE (e.g., UE A).

[0078] Therefore, in Figure 3B In an example, different DRX cycles can provide paging resources for different UE types. As described above, since the bandwidth of the paging message 325 (e.g., paging message 325-a of the first DRX cycle 320 and paging message 325-b of the second DRX cycle 320) is lower, even if there are fewer than L UEs being paged in the example of Figure 3A UE A may need to monitor the PO in multiple DRX cycles and at a higher frequency than in Figure 3AIn the example, SDT 315-b is received at a later time than SDT 315-a. In the case where the operation is based on traditional paging and PEI techniques, in Figure 3B 's example, UE A may consume more power and experience a longer delay, even in Figure 3B 's example than in Figure 3A 's example, fewer UEs are paged. This may lead to increased power consumption (e.g., due to additional time in a higher power state and performing blind decoding of paging control signaling sent via PDCCH, which indicates paging resources for paging messages). As described above, even in the case where PEI can be achieved, existing PEI does not provide an indication of the type of UE (e.g., RedCap / low layer or non-RedCap / high layer UE) that should monitor paging messages. Thus, further enhancements to PEI, such as those discussed herein, can help reduce power consumption in a system with multiple different types of UEs. Thus, in accordance with various aspects discussed herein, in Figure 3B 's example, the efficiency of UE A can be improved by signaling to the UE that it can transition to a lower power mode for the first two DRX cycles 320.

[0079] Figure 4 illustrates an example of a paging transmission scheme 400 that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. The paging transmission scheme 400 may implement one or more aspects of the wireless communication system 100 or the wireless communication system 200, or be implemented by them. For example, the paging transmission scheme 400 may be implemented by UE 115 or the network entity 105, both of which may be examples of corresponding devices as described with reference to Figure 1 and Figure 2 . In Figure 4 's example, the network entity 105 may be an example of a CU, DU, RU, base station, IAB node, or one or more other network nodes as described with reference to Figure 1 .

[0080] In Figure 4In the example, the PEI 405 can be sent in the PEI occasion 410 and can provide an indication of one or more subgroup IDs for which paging messages are to be monitored. For example, a first group of UEs can be configured with a first subgroup ID (e.g., via RRC signaling and / or other signaling such as MAC control element (MAC-CE) or downlink control information (DCI)), and a second group of UEs can be configured with a second subgroup ID (e.g., via RRC signaling, MAC-CE, and / or DCI). If the PEI 405 indicates the first subgroup ID, the second group of UEs can stop monitoring further paging communications during the associated DRX period after decoding the PEI 405. In this example, based on the first subgroup ID in the PEI 405, the UEs in the first group of UEs can monitor the paging PDCCH 415. In some cases, different POs 420 can be associated with the PEI 405, such as a first PO 420-a that can provide a first paging PDCCH 415-a and a second PO 420-b that can provide a second paging PDCCH 415-b. The PEI 405 can be carried by a PDCCH sent in the PEI occasion 410, where the PEI occasion 410 can be configured as part of the system information, for example. In some cases, such as in Figure 4 the example, one PEI 405 can be associated with multiple POs 420, although in other examples, a single PO 420 can be associated with the PEI 405.

[0081] Paging messages such as the paging PDSCH 425 can be scheduled by the paging PDCCH 415. In this example, the first paging PDCCH 415-a can provide DCI including scheduling information for the first paging PDSCH 425-a, and the second paging PDCCH 415-b can provide DCI including scheduling information for the second paging PDSCH 425-b. As described above, if both the network entity and the UE support the PEI 405, any UE not indicated in the PEI 405 can skip decoding both the paging PDCCH 415 and the paging PDSCH 425. As described herein, in some cases, the PEI 405 can include one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first group of paging subgroups of a first type of UE configured to support a first receive bandwidth configuration and a second group of paging subgroups of a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. In such cases, the UE can determine whether to monitor or skip monitoring the PO 420 based on the UE's bandwidth configuration. Refer to Figure 5 Figures 9 for a more detailed discussion of examples of PEI fields and associated operations for determining whether to monitor or skip monitoring paging messages.

[0082] In some cases, a network entity or a UE may not support PEI. In such cases, the UE may need to decode the paging PDCCH 415 (e.g., by monitoring the PO 420). According to some aspects discussed herein, such a UE may still skip decoding the paging PDSCH 425 based on the indication in the paging PDCCH 415. In some cases, the network entity may include supplementary information in the paging PDCCH 415 to indicate whether the paging message (e.g., the paging PDCSH 425) includes paging records for a single UE type or a mixed UE type, such that the UE can terminate the paging PDSCH 25 decoding earlier to save power. In some cases, the paging PDCCH 415 may include a two-bit indicator to indicate the content of the paging message, such as:

[0083] 01: The paging message is only applicable to advanced / legacy UEs;

[0084] 10: The paging message is only applicable to low-layer UEs;

[0085] 11: The paging message is applicable to all UE types;

[0086] 00: In the next paging cycle, no UE in the subgroup is paged.

[0087] Using such techniques, the UE can decode the paging PDCCH 415 and determine whether to decode the associated paging PDSCH 425, which can reduce power consumption and the amount of processing resources used for decoding operations.

[0088] Figure 5 An example of a PEI structure 500 that supports paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure is illustrated. The PEI structure 500 may implement one or more aspects of the wireless communication system 100 or the wireless communication system 200, or be implemented by them. For example, the PEI structure 500 may be implemented by the UE 115 or the network entity 105, both of which may be examples of the corresponding devices as described in reference Figure 1 and Figure 2 description. In the Figure 5 example, the network entity 105 may be an example of a CU, a DU, an RU, a base station, an IAB node, or one or more other network nodes as described in reference Figure 1 description.

[0089] As described herein, according to various aspects, a UE may be configured with PEI sub - packets based on UE capabilities. In some cases, when different UE types co - exist in a network supporting PEI, subgroup IDs may be configured in the PEI based on UE capabilities, where the PEI is shared by different UE types. In some cases, for a low - layer UE that supports sub - packets for core network control of the PEI, a first set of subgroup IDs 505 dedicated to the low - layer UE's PEI may be included in the PEI structure 500 (e.g., as a first PEI field). In some cases, the ID associated with the first set of subgroup IDs 505 may be assigned by a core network entity (e.g., CU or DU) via NAS signaling. The first set of subgroup IDs 505 may support K subgroup IDs, such as by using a bit - field, where if the associated subgroup ID is not activated for monitoring paging messages, the bit indicates zero, and if the associated subgroup ID is activated for monitoring paging messages, the bit indicates one. In some cases, the UE may be an RRC configured with the associated subgroup ID of the first set of subgroup IDs 505. This set of activated fields or bits may be associated with one or more POs, which may also be RRC - configured, configured in system information (e.g., in one or more system information blocks (SIBs)), or any combination thereof.

[0090] In Figure 5 an example, a set of additional subgroup IDs 510 (e.g., as a second PEI field) may be included in the PEI structure 500, which corresponds to the PEI subgroup IDs based on the UE ID or UE class ID. In this example, the set of subgroup IDs 510 may contain up to L subgroup IDs and thus includes L bits in the PEI structure. Although the various examples discussed herein use a bitmap structure in which the bits in the associated PEI field indicate whether the associated subgroup ID is active, other examples may use other addressing techniques to identify the subgroup IDs, such as a mapping of one or more subgroups to bit values of an associated field.

[0091] Additionally or alternatively, in some cases, network entities such as base stations, RUs, and / or RICs may have PEI capabilities and may allow mixed UE types to camp on the cells served by that network entity. In such cases, the network entity may configure subgroup IDs in the second set of subgroup IDs 515 (e.g., indicated in the third PEI field). In some cases, one or more subgroup IDs dedicated to the PEI of lower-layer UEs may be configured by the network entity and broadcast to the served UEs in the system information (SI). In some cases, a network entity with PEI capabilities that allows lower-layer UEs to camp may provide a set of numbers (e.g., UE class IDs) common to the lower-layer UEs that can be broadcast in the SI, and the lower-layer UEs use this set of numbers to determine the PO index and subgroup ID in the second set of subgroup IDs 515 of the PEI structure 500. In some cases, within a paging message, the network entity may use a temporary mobile subscriber identity (TMSI) such as 5G-S-TMSI to identify different UEs with the same capabilities. Thus, the PEI structure 500 includes multiple paging indication fields mapped to multiple corresponding UE subgroups, and these subgroup UEs include a first set of paging subgroups of a first type of UE configured to support a first receive bandwidth configuration (e.g., corresponding to one or more subgroup IDs in the first set of subgroup IDs 505 or the second set of subgroup IDs 515) and a second set of paging subgroups of a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration (e.g., corresponding to one or more subgroup IDs in the first set of subgroup IDs 505 or the second set of subgroup IDs 515 that are not in the first set of paging subgroups).

[0092] Additionally or alternatively, in some aspects, a downlink reference signal availability indication 520 may be provided in the PEI structure 500. Such a downlink reference signal availability indication 520 may indicate that one or more reference signals, such as a tracking reference signal (TRS), a non-cell-defined synchronization signal block (NCD-SSB), a positioning reference signal (PRS), or any combination thereof, may be attached to the subgroup ID indicated in the PEI structure 500 (e.g., which may be used for UEs with a subgroup ID indicated in a set of subgroup IDs configured by a core network entity, determined by a UE_ID / UE class ID, indicated by a serving network entity, or any combination thereof).

[0093] In some other aspects, the network or the UE may not support PEI sub-packets or separate PEI transmissions based on UE capabilities, and the network entity may still provide assistance information to the UE that monitors the PEI. In some cases, for a UE with PEI capabilities, the network entity may signal additional information in the PEI that includes a field only for subgroup ID 510. In such cases, if the subgroup ID is associated with UEs of different UE types (e.g., both high-tier and low-tier UEs are associated with the same subgroup ID), the PEI may have an enhanced bit-width for the fields mapped to each subgroup ID, or may have a mask or bitmap to indicate the status of the paging subgroup identified by the subgroup ID (e.g., associated with a low-tier UE). In some cases, the enhanced bit-width may provide a two-bit indication for the status indication of each paging subgroup (e.g., instead of a one-bit indication), where the two-bit indication may indicate the content of the paging message, such as:

[0094] 01: The paging message is applicable only to high-tier / legacy UEs;

[0095] 10: The paging message is applicable only to low-tier UEs;

[0096] 11: The paging message is applicable to all UE types;

[0097] 00: In the next paging cycle, no UE in the subgroup is paged.

[0098] Using such techniques, the UE can decode the PEI and determine whether to monitor the associated PO, which can reduce power consumption and the amount of processing resources used for decoding operations.

[0099] Figure 6 Illustrates an example of a process flow 600 that supports paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. The process flow 600 may implement various aspects of the present disclosure described herein. The elements described in the process flow 600 (e.g., UE 115-b, network entity 105-b, core network 130-a) may be examples of similarly named elements described herein.

[0100] In the following description of the process flow 600, the operations between various entities or elements may be performed in a different order or at different times. Some operations may also be excluded from the process flow 600, or other operations may be added. Although various entities or elements are shown performing the operations of the process flow 600, some aspects of some operations may also be performed by other entities or elements of the process flow 600 or by entities or elements not depicted in the process flow or any combination thereof.

[0101] At 605, UE 115-b may send and network entity 105-b and core network 130-a may receive UE capability indication and UE assistance information. In some cases, the UE capability indication may indicate that UE 115-b is a UE with PEI capability. Additionally, the UE capability indication may indicate that UE 115-b is capable of enhanced PEI, where different groups of paging subgroups may be associated with different types of UEs (e.g., lower-layer UEs configured for reduced shared channel downlink bandwidth as opposed to higher-layer UEs with greater shared channel downlink bandwidth).

[0102] At 610, core network 130-a may provide an indication of a dedicated subgroup ID based on the UE capabilities. In some cases, the dedicated subgroup ID configured by core network 130-a may be mapped to a first PEI field among a plurality of PEI fields, the first PEI field being associated with a plurality of subgroup IDs, where different subgroup IDs may correspond to different UE types.

[0103] At 615, network entity 105-b may send a PEI to UE 115-b. The PEI may indicate to UE 115-b whether there is a paging message for UE 115-b in the PO associated with the PEI. In some cases, the PEI may be sent in a DRX cycle and may be associated with subsequent paging occasions configured for multiple different types of UEs, where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first group of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second group of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. In some cases, UE 115-b may determine whether to monitor a subsequent PO associated with the PEI at least partially based on whether the subgroup ID in the PEI is configured for the UE type of the first UE 115-b.

[0104] At 620, one or more paging messages may be sent by network entity 105-b or by core network 130-a via network entity 105-b. UE 115-b may monitor the one or more paging messages based on a determination made according to the PEI and the associated subgroup ID of UE 115-b.

[0105] Figure 7An example of process flow 700 is illustrated that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. Process flow 700 may implement various aspects of the present disclosure described herein. The elements described in process flow 700 (e.g., UE 115-c, network entity 105-c, core network 130-b) may be examples of similarly named elements described herein.

[0106] In the following description of process flow 700, operations between various entities or elements may be performed in different orders or at different times. Some operations may also be excluded from process flow 700, or other operations may be added. Although various entities or elements are shown performing the operations of process flow 700, some aspects of some operations may also be performed by other entities or elements of process flow 700 or by entities or elements not depicted in the process flow or any combination thereof.

[0107] At 705, UE 115-c may send and network entity 105-c and core network 130-b may receive a UE capability indication and UE assistance information. In some cases, the UE capability indication may indicate that UE 115-c is a UE with PEI capability. Additionally, the UE capability indication may indicate that UE 115-c is capable of enhanced PEI, where different groups of paging subgroups may be associated with different types of UEs (e.g., lower-layer UEs configured for reduced shared channel downlink bandwidth as opposed to higher-tier UEs with greater shared channel downlink bandwidth).

[0108] At 710, core network 130-b may provide an indication of UE capabilities and context for access stratum communication to network entity 105-c. In some cases, the capabilities may indicate that UE 115-c is a UE with PEI capability, and may indicate the UE type of UE 115-c. In some cases, core network 130-b may indicate that network entity 105-c may configure subgroup IDs for PEI associated with different UE types. Network entity 105-c may identify one or more UE subgroups and configure different subgroup IDs for different types of UEs.

[0109] At 715, network entity 105-c may send system information (e.g., one or more SIBs) indicating one or more dedicated subgroup IDs associated with different UE types. The different subgroup IDs may be explicitly indicated by network entity 105-c such that PEIs indicating different subgroup IDs may indicate to UE 115-c whether to monitor one or more POs associated with the PEI.

[0110] At 720, network entity 105-c may send a Paging Encoding Indicator (PEI) to UE 115-c. The PEI may indicate to UE 115-c whether there is a paging message for UE 115-c in a Paging Occasion (PO) associated with the PEI. In some cases, the PEI may be sent within a Discontinuous Reception (DRX) cycle and may be associated with subsequent paging opportunities configured for multiple different types of UEs, where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, and the one or more UE subgroups include a first set of paging subgroups for a first type of UE configured to support a first reception bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second reception bandwidth configuration different from the first reception bandwidth configuration. In some cases, UE 115-c may determine whether to monitor a subsequent PO associated with the PEI at least in part based on whether the subgroup ID in the PEI is configured for the UE type of the first UE 115-c.

[0111] At 725, one or more paging messages may be sent by network entity 105-c or by core network 130-b via network entity 105-c. UE 115-c may monitor the one or more paging messages based on a determination made according to the PEI and the associated subgroup ID of UE 115-c.

[0112] Figure 8 An example of a process flow 800 that supports paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure is illustrated. The process flow 800 may implement various aspects of the present disclosure described herein. The elements described in the process flow 800 (e.g., UE 115-d, network entity 105-d, core network 130-c) may be examples of similarly named elements described herein.

[0113] In the following description of the process flow 800, operations between various entities or elements may be performed in a different order or at different times. Some operations may also be excluded from the process flow 800, or other operations may be added. Although various entities or elements are shown as performing the operations of the process flow 800, some aspects of some operations may also be performed by other entities or elements of the process flow 800 or by entities or elements not depicted in the process flow or any combination thereof.

[0114] At 805, UE 115-d may send and network entity 105-d and core network 130-c may receive UE capability indication and UE assistance information. In some cases, the UE capability indication may indicate that UE 115-d is a UE with PEI capability. Additionally, the UE capability indication may indicate that UE 115-d is capable of enhanced PEI, where different groups of paging subgroups may be associated with different types of UEs (e.g., lower-layer UEs configured for reduced shared channel downlink bandwidth as opposed to higher-layer UEs with greater shared channel downlink bandwidth).

[0115] At 810, core network 130-c may provide an indication of UE capabilities and context for access stratum communication to network entity 105-d. In some cases, the capabilities may indicate that UE 115-d is a UE with PEI capability and may indicate the UE type of UE 115-d. In some cases, core network 130-c may indicate to network entity 105-d the subgroup IDs for PEI that may be configured for association with different UE types. Network entity 105-d may identify one or more UE subgroups and configure different subgroup IDs for different types of UEs.

[0116] At 815, network entity 105-d may send system information (e.g., one or more SIBs) indicating one or more UE class IDs for PO and PEI subgroup ID determination. Different UE class IDs may be indicated by network entity 105-d such that PEIs indicating different subgroup IDs may indicate to UE 115-d whether to monitor one or more POs associated with the PEI.

[0117] At 820, network entity 105-d may send a PEI to UE 115-d. The PEI may indicate to UE 115-d whether there is a paging message for UE 115-d in the PO associated with the PEI. In some cases, the PEI may be sent in a DRX cycle and may be associated with subsequent paging opportunities configured for multiple different types of UEs, where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first group of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second group of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. In some cases, UE 115-d may determine whether to monitor subsequent POs associated with the PEI at least in part based on whether the subgroup ID in the PEI is configured for the UE type of the first UE 115-d.

[0118] At 825, one or more paging messages may be sent by network entity 105-d or by core network 130-c via network entity 105-d. UE 115-d may monitor one or more paging messages based on a determination made according to the PEI and the associated subgroup ID of UE 115-d.

[0119] Figure 9A and Figure 9B Examples of PEI resources 900 and 901 that support paging techniques for wireless devices with hybrid capabilities according to one or more aspects of the present disclosure are illustrated. PEI resources 900 and 901 may implement, or be implemented by, one or more aspects of wireless communication system 100 or wireless communication system 200. For example, PEI resources 900 and 901 may be implemented by UE 115 or network entity 105, both of which may be examples of corresponding devices as described in reference Figure 1 and Figure 2 described. In Figure 9A and Figure 9B example, network entity 105 may be an example of a CU, DU, RU, base station, IAB node, or one or more other network nodes as described in reference Figure 1 described.

[0120] As described herein, according to various aspects, a UE may be configured with a PEI based on UE capabilities. In some cases, when different UE types coexist in a network that supports PEI, different PEIs based on UE capabilities may be the configured PEIs, where the different PEIs are associated with different UE types. In some cases, such as Figure 9A illustrated, separate CORESETs may be provided for different PEIs. In such cases, a first downlink bandwidth 905 associated with a high-tier / legacy UE may be associated with a first CORESET and may be used for the transmission of PEI 910 for the high-tier / legacy UE. A second downlink bandwidth 915 may be associated with a low-tier UE, may be associated with a second CORESET, and may be used for the transmission of PEI 920 for the low-tier UE. In such cases, PEI 920 for the low-tier UE may be transmitted on a CORESET associated with a separately configured narrowband downlink bandwidth portion, such as Figure 9A illustrated. In other cases, as Figure 9B illustrated, PEI 960 for the low-tier UE may be transmitted on a narrowband CORESET nested within a shared downlink bandwidth portion 950. In this example, a larger bandwidth of the shared downlink bandwidth portion 950 may be used to transmit PEI 955 associated with the high-tier / legacy UE.

[0121] In some cases, a separate search space set configuration can be provided for the PEI, where different ranges of aggregation levels (ALs) or different time offsets / periodicity / skip rules for PDCCH monitoring can be configured for UEs with different UE types. In such cases, different types of UEs can monitor the PEI based on the configured search space set and can decode the associated PEI indicating whether the UE is to monitor the PO. Additionally or alternatively, different radio network temporary identifiers (RNTIs) can be used for different PEIs associated with different types of UEs. In such cases, the PEI for low-layer UEs can be scrambled by a group RNTI different from the PEI-RNTI configured for legacy / advanced UEs. Additionally or alternatively, different DMRSs or signal waveforms can be used for different PEIs associated with different types of UEs. For example, the DMRS transmitted together with the PEI for low-layer UEs can be configured with a different scrambling ID, different antenna ports, or different density / mode for RE mapping than the PEI for advanced / legacy UEs; or a sequence-based PEI can be configured for low-layer UEs.

[0122] Figure 10 Block diagram 1000 illustrates a device 1005 that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. Device 1005 can be an example of aspects of UE 115 as described herein. Device 1005 can include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 can also include a processor. Each of these components can communicate with one another (e.g., via one or more buses).

[0123] Receiver 1010 can provide components for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to paging techniques for wireless devices with hybrid capabilities), such as packets, user data, control information, or any combination thereof. The information can be passed to other components of device 1005. Receiver 1010 can utilize a single antenna or a set of multiple antennas.

[0124] Transmitter 1015 can provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 can transmit information associated with various information channels (e.g., control channels, data channels, information channels related to paging techniques for wireless devices with hybrid capabilities), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 1015 can be co-located with receiver 1010 in a transceiver module. Transmitter 1015 can utilize a single antenna or a set of multiple antennas.

[0125] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or their various components can be examples of components for performing aspects of paging techniques for wireless devices with hybrid capabilities as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can support methods for performing one or more of the functions described herein.

[0126] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in communication management circuitry). The hardware can 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 configured to or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and the memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

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

[0128] In some examples, the communication manager 1020 can be configured to use or otherwise cooperate with the receiver 1010, the transmitter 1015, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 1020 can receive information from the receiver 1010, convey information to the transmitter 1015, or integrate in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0129] According to an example as disclosed herein, the communication manager 1020 may support wireless communication at a first UE. For example, the communication manager 1020 may be configured to or otherwise support components for receiving control signaling communication for PEI in a DRX cycle, where the PEI is associated with a subsequent PO configured for multiple different types of UEs, and the PEI includes one or more paging indication fields mapped to one or more UE subgroups, and the one or more UE subgroups include a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The communication manager 1020 may be configured to or otherwise support components for determining whether to monitor a subsequent PO associated with the PEI based on whether the subgroup ID in the PEI is configured for the UE type of the first UE.

[0130] By including or configuring a communication manager 1020 according to an example as described herein, a device 1005 (e.g., a control receiver 1010, a transmitter 1015, a communication manager 1020, or a processor combined with or otherwise coupled thereto) may support techniques for indicating whether a UE is to monitor one or more paging messages, which may reduce power consumption due to a shorter UE wake-up time, reduce latency due to improved paging message timing, and / or reduce consumption of processing resources due to fewer blind decoding operations, which may provide enhanced system efficiency and an enhanced user experience.

[0131] Figure 11 Block diagram 1100 illustrates a device 1105 that supports paging techniques for a wireless device with hybrid capabilities according to one or more aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or the UE 115 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).

[0132] The receiver 1110 may provide components for receiving information associated with various information channels (e.g., control channels, data channels, information channels related to paging techniques for a wireless device with hybrid capabilities) such as packets, user data, control information, or any combination thereof. The information may be passed to other components of the device 1105. The receiver 1110 may utilize a single antenna or a set of multiple antennas.

[0133] The transmitter 1115 may provide components for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to paging techniques for wireless devices with hybrid capabilities), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a set of multiple antennas.

[0134] The device 1105 or its various components may be examples of components for performing various aspects of paging techniques for wireless devices with hybrid capabilities as described herein. For example, the communication manager 1120 may include a PEI manager 1125, a paging manager 1130, or any combination thereof. The communication manager 1120 may be an example of aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 may receive information from the receiver 1110, convey information to the transmitter 1115, or integrate in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0135] According to examples disclosed herein, the communication manager 1120 may support wireless communication at a first UE. The PEI manager 1125 may be configured to or otherwise support components for receiving control signaling communication for the PEI in a DRX cycle, where the PEI is associated with subsequent POs configured for multiple different types of UEs, and where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The paging manager 1130 may be configured to or otherwise support components for determining whether to monitor subsequent POs associated with the PEI based on whether the subgroup ID in the PEI is configured for the UE type of the first UE.

[0136] Figure 12FIG. 1200 is a block diagram of a communication manager 1220 that illustrates paging techniques in support of a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. The communication manager 1220 may 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 may be examples of components for performing various aspects of paging techniques for a wireless device with hybrid capabilities as described herein. For example, the communication manager 1220 may include a PEI manager 1225, a paging manager 1230, a PEI resource manager 1235, a subgroup ID manager 1240, a reference signal manager 1245, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0137] In accordance with an example as disclosed herein, the communication manager 1220 may support wireless communication at a first UE. The PEI manager 1225 may be configured to or otherwise support components for receiving control signaling communication for a PEI in a DRX cycle, the PEI being associated with a subsequent PO configured for a plurality of different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The paging manager 1230 may be configured to or otherwise support components for determining whether to monitor a subsequent PO associated with the PEI based on whether a subgroup ID in the PEI is configured for the UE type of the first UE.

[0138] In some examples, the PEI manager 1225 may be configured to or otherwise support components for receiving subsequent control signaling communication for a PEI in a subsequent DRX cycle, the PEI being associated with one or more subsequent POs configured for one or more multiple types of UEs. In some examples, the paging manager 1230 may be configured to or otherwise support components for skipping monitoring one or more of the subsequent POs associated with the PEI based on a paging indication field indicating that a subgroup ID configured for the UE type of the first UE will not be paged in the subsequent PO associated with the PEI.

[0139] In some examples, to support receiving control signaling communication, the PEI manager 1225 may be configured to or otherwise support components for receiving PEI in a DRX cycle, where the PEI includes a set of multiple paging indication fields for multiple UE types, and the multiple UE types are allowed to monitor paging messages, short messages, system information, other control signaling of a serving network entity, or any combination thereof. In some examples, each paging indication field in the set of multiple paging indication fields is associated with the identification of a different set of paging subgroup IDs, and indicates whether UEs sharing the same subgroup ID will be paged at a subsequent PO associated with the PEI.

[0140] In some examples, the set of multiple paging indication fields includes one or more of a first paging indication field, a second paging indication field, or a third paging indication field, where the first paging indication field provides a first set of subgroup IDs configured by a core network entity, the second paging indication field provides a second set of subgroup IDs associated with a UE ID or a UE class ID, and the third paging indication field provides a third set of subgroup IDs configured at a serving cell belonging to a radio access network (RAN) notification area (RNA) of the UE. In some examples, the first control signaling further indicates activating one or more downlink reference signals associated with one or more UE subgroups for UEs in an idle or inactive state. In some examples, the one or more downlink reference signals include one or more of a tracking reference signal, a non-cell defined (NCD) synchronization signal block (SSB), a positioning reference signal (PRS), or any combination thereof.

[0141] In some examples, to support receiving control signaling communication, the PEI Resource Manager 1235 may be configured to or otherwise support components for receiving a first PEI in a first set of resources for a first set of paging subgroups configured for UEs of a first type and a second PEI in a second set of resources for a second set of paging subgroups configured for UEs of a second type, where the first PEI and the second PEI are associated with or shared by POs respectively configured for different UE types. In some examples, the first set of resources is indicated by a first Control Resource Set (CORESET) associated with the first set of paging subgroups, and the second set of resources is indicated by a second CORESET associated with the second set of paging subgroups. In some examples, the first set of resources is associated with a first search space set configured for the first set of paging subgroups, and the second set of resources is associated with a second search space set configured for the second set of paging subgroups. In some examples, the first PEI is scrambled with a first set of Group Radio Network Temporary Identifiers (G-RNTIs) associated with the first set of paging subgroups, and a second G-RNTI is used to scramble the second PEI of the second set of paging subgroups. In some examples, the first set of resources is associated with a first Demodulation Reference Signal (DMRS) or a first waveform configuration associated with the first set of paging subgroups, and the second set of resources is associated with a second DMRS or a second waveform configuration associated with the second set of paging subgroups.

[0142] In some examples, to support receiving control signaling communication, the Subgroup ID Manager 1240 may be configured to or otherwise support components for receiving a PEI including a multi-bit field indicating which one of the first set of paging subgroups, the second set of paging subgroups, or any combination thereof will be paged at a subsequent PO associated with the PEI. In some examples, a first UE monitors a PO of a downlink control channel, the downlink control channel providing resource allocation for shared channel communication including a paging message, and where based on the shared channel communication not carrying any paging messages for the first set of paging subgroups or the second set of paging subgroups, the downlink control channel indicates that one or more of the first set of paging subgroups or the second set of paging subgroups will skip decoding of the shared channel communication.

[0143] Figure 13FIG. illustrates a system 1300 including a device 1305 that supports paging techniques for wireless devices with hybrid capabilities, in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of the device 1005, the device 1105, or the UE 115 as described herein, or include components thereof. The device 1305 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, code 1335, and a processor 1340. These components may be electronically communicated or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled via one or more buses (e.g., bus 1345).

[0144] The I / O controller 1310 may manage input signals and output signals of the device 1305. The I / O controller 1310 may also manage peripheral devices not integrated into the device 1305. In some cases, the I / O controller 1310 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1310 may utilize an operating system, such as MS- or another known operating system. Additionally or alternatively, the I / O controller 1310 may represent, or interact with, a modem, a keyboard, a mouse, a touch screen, or similar device. In some cases, the I / O controller 1310 may be implemented as part of a processor, such as the processor 1340. In some cases, a user may interact with the device 1305 via the I / O controller 1310 or via hardware components controlled by the I / O controller 1310.

[0145] In some cases, device 1305 may include a single antenna 1325. However, in some other cases, device 1305 may have more than one antenna 1325, and the more than one antenna may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1315 may communicate bidirectionally via one or more antennas 1325, wired or wireless links, as described herein. For example, transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1315 may also include a modem for: modulating a packet; providing the modulated packet to one or more antennas 1325 for transmission; and demodulating a packet received from one or more antennas 1325. Transceiver 1315 or transceiver 1315 and one or more antennas 1325 may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof, as described herein.

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

[0147] Processor 1340 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks supporting paging techniques for wireless devices with hybrid capabilities). For example, device 1305 or components of device 1305 may include processor 1340 and memory 1330 coupled to or coupled with processor 1340, and processor 1340 and memory 1330 are configured to perform the various functions described herein.

[0148] According to examples as disclosed herein, the communication manager 1320 may support wireless communication at a first UE. For example, the communication manager 1320 may be configured to or otherwise support components for receiving control signaling communication for a PEI in a DRX cycle, where the PEI is associated with a subsequent PO configured for multiple different types of UEs, and where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The communication manager 1320 may be configured to or otherwise support components for determining whether to monitor a subsequent PO associated with the PEI based on whether a subgroup ID in the PEI is configured for the UE type of the first UE.

[0149] By including or configuring the communication manager 1320 according to examples as described herein, the device 1305 may support techniques for indicating whether a UE is to monitor one or more paging messages, which may reduce power consumption due to shorter UE wake-up times, reduce latency due to improved paging message timing, and / or reduce consumption of processing resources due to fewer blind decoding operations, which may provide enhanced system efficiency and an enhanced user experience.

[0150] In some examples, the communication manager 1320 may be configured to use or otherwise cooperate with the transceiver 1315, one or more antennas 1325, or any combination thereof to perform various operations (e.g., receive, monitor, transmit). 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 processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions executable by the processor 1340 to cause the device 1305 to perform aspects of the paging techniques for wireless devices with hybrid capabilities as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.

[0151] Figure 14 Block diagram 1400 illustrates a device 1405 that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. The device 1405 may be an example of aspects of the network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0152] The receiver 1410 may provide components 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 passed to other components of the device 1405. In some examples, the receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.

[0153] The transmitter 1415 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 1405. For example, the transmitter 1415 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 1415 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0154] The communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof or their various components may be examples of components for performing various aspects of the paging techniques for a wireless device with hybrid capabilities as described herein. For example, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0155] In some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). 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 are configured to or otherwise support components for performing the functions described in this disclosure. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0156] Additionally or alternatively, in some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices that are configured to or otherwise support components for performing the functions described in this disclosure.

[0157] In some examples, the communication manager 1420 may be configured to use or otherwise cooperate with the receiver 1410, the transmitter 1415, or both to perform various operations (e.g., receive, obtain, monitor, output, transmit). For example, the communication manager 1420 may receive information from the receiver 1410, convey information to the transmitter 1415, or integrate in combination with the receiver 1410, the transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

[0158] According to an example as disclosed herein, the communication manager 1420 may support wireless communication at a network entity. For example, the communication manager 1420 may be configured to or otherwise support components for sending control signaling communication for PEI to at least a first UE in a DRX cycle, where the PEI is associated with a subsequent PO configured for multiple different types of UEs, and where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups of a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups of a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The communication manager 1420 may be configured to or otherwise support components for sending a paging message to a first UE in a first paging resource associated with the first type of UE based on the first UE being a first type of UE and the subgroup ID in the PEI being configured for the first type of UE.

[0159] By including or configuring a communication manager 1420 according to an example as described herein, a device 1405 (e.g., a control receiver 1410, a transmitter 1415, a communication manager 1420, or a processor combined with or otherwise coupled thereto) may support techniques for indicating whether a UE is to monitor one or more paging messages, which may reduce power consumption due to a shorter UE wake-up time, reduce latency due to improved paging message timing, and / or reduce consumption of processing resources due to fewer blind decoding operations, which may provide enhanced system efficiency and an enhanced user experience.

[0160] Figure 15 Block diagram 1500 illustrates a device 1505 that supports paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of aspects of the device 1405 or the network entity 105 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. The device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0161] The receiver 1510 may provide components 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 passed to other components of the device 1505. In some examples, the receiver 1510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0162] The transmitter 1515 may provide components for outputting (e.g., transmitting, providing, conveying, delivering) information generated by other components of the device 1505. For example, the transmitter 1515 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 1515 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, the transmitter 1515 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1515 and the receiver 1510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0163] The device 1505 or its various components may be examples of components for performing aspects of paging techniques for wireless devices with hybrid capabilities as described herein. For example, the communication manager 1520 may include a PEI manager 1525, a paging manager 1530, or any combination thereof. The communication manager 1520 may be an example of aspects of the communication manager 1420 as described herein. In some examples, the communication manager 1520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise in cooperation with the receiver 1510, the transmitter 1515, or both. For example, the communication manager 1520 may receive information from the receiver 1510, convey information to the transmitter 1515, or integrate in combination with the receiver 1510, the transmitter 1515, or both to obtain information, output information, or perform various other operations as described herein.

[0164] According to an example as disclosed herein, a communication manager 1520 may support wireless communication at a network entity. A PEI manager 1525 may be configured to or otherwise support components for sending control signaling communication for a PEI to at least a first UE in a DRX cycle, where the PEI is associated with a subsequent PO configured for multiple different types of UEs, and where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups of a first type of UEs configured to support a first receive bandwidth configuration and a second set of paging subgroups of a second type of UEs configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. A paging manager 1530 may be configured to or otherwise support components for sending a paging message to a first UE in a first paging resource associated with the first type of UEs based on the first UE being a first type of UE and a subgroup ID in the PEI being configured for the first type of UEs.

[0165] Figure 16 Block diagram 1600 illustrates a communication manager 1620 that supports paging techniques for a wireless device with hybrid capabilities, in accordance with one or more aspects of the present disclosure. The communication manager 1620 may be an example of aspects of the communication manager 1420, the communication manager 1520, or both as described herein. The communication manager 1620 or its various components may be examples of components for performing aspects of paging techniques for a wireless device with hybrid capabilities as described herein. For example, the communication manager 1620 may include a PEI manager 1625, a paging manager 1630, a PEI resource manager 1635, a subgroup ID manager 1640, a reference signal manager 1645, 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 the 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.

[0166] According to an example as disclosed herein, the communication manager 1620 may support wireless communication at a network entity. The PEI manager 1625 may be configured to or otherwise support components for sending control signaling communication for PEI to at least a first UE in a DRX cycle, where the PEI is associated with a subsequent PO configured for multiple different types of UEs, and where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups of a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups of a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The paging manager 1630 may be configured to or otherwise support components for sending a paging message to a first UE in a first paging resource associated with the first type of UE based on the first UE being a first type of UE and the subgroup ID in the PEI being configured for the first type of UE.

[0167] In some examples, the PEI manager 1625 may be configured to or otherwise support components for configuring one or more UEs to skip monitoring one or more subsequent POs associated with the PEI based on a paging indication field that indicates that the subgroup ID configured for a first UE type or a second UE type associated with each of the one or more UEs will not be paged in a subsequent PO associated with the PEI. In some examples, to support sending control signaling communication, the PEI manager 1625 may be configured to or otherwise support components for sending the PEI in a DRX cycle, where the PEI includes a set of multiple paging indication fields for multiple UE types that are allowed to monitor paging messages, short messages, system information, other control signaling of a serving network entity, or any combination thereof.

[0168] In some examples, each paging indication field in the set of multiple paging indication fields is associated with the identification of a different set of paging subgroup IDs, and indicates whether UEs sharing the same subgroup ID will be paged in a subsequent PO associated with the PEI. In some examples, the set of multiple paging indication fields includes one or more of a first paging indication field, a second paging indication field, or a third paging indication field, where the first paging indication field provides a first set of subgroup IDs configured by a core network entity, the second paging indication field provides a second set of subgroup IDs associated with a UE ID or a UE class ID, and the third paging indication field provides a third set of subgroup IDs configured at a serving cell belonging to a radio access network (RAN) notification area (RNA) of the UE. In some examples, the first control signaling further indicates activation of one or more downlink reference signals associated with one or more UE subgroups for UEs in an idle or inactive state. In some examples, the one or more downlink reference signals include one or more of a tracking reference signal, a non-cell defined (NCD) synchronization signal block (SSB), a positioning reference signal (PRS), or any combination thereof.

[0169] In some examples, to support the transmission of control signaling communication, the PEI resource manager 1635 may be configured to or otherwise support a component for transmitting a first PEI in a first set of resources configured for a first set of paging subgroups of a first type of UE. In some examples, to support the transmission of control signaling communication, the PEI resource manager 1635 may be configured to or otherwise support a component for transmitting a second PEI in a second set of resources configured for a second set of paging subgroups of a second type of UE, where the first PEI and the second PEI are associated with or shared by POs respectively configured for different UE types.

[0170] In some examples, the first set of resources is indicated by a first control resource set (CORESET) configuration associated with the first set of paging subgroups, and the second set of resources is indicated by a second CORESET configuration associated with the second set of paging subgroups. In some examples, the first set of resources is associated with a first search space set configured for the first set of paging subgroups, and the second set of resources is associated with a second search space set configured for the second set of paging subgroups. In some examples, the first PEI is scrambled with a first set of radio network temporary identifiers (G-RNTIs) associated with the first set of paging subgroups, and a second G-RNTI is used to scramble the second PEI of the second set of paging subgroups. In some examples, the first set of resources is associated with a first DMRS or a first waveform configuration associated with the first set of paging subgroups, and the second set of resources is associated with a second DMRS or a second waveform configuration associated with the second set of paging subgroups.

[0171] In some examples, to support sending control signaling communication, the subgroup ID manager 1640 may be configured to or otherwise support components for sending a PEI that includes a multi-bit field indicating which of a first set of paging subgroups, a second set of paging subgroups, or any combination thereof will be paged at a subsequent PO associated with the PEI. In some examples, a first UE monitors a PO of a downlink control channel that provides resource allocation for shared channel communication including a paging message, and wherein based on the shared channel communication not carrying any paging message for the first set of paging subgroups or the second set of paging subgroups, the downlink control channel indicates that one or more of the first set of paging subgroups or the second set of paging subgroups will skip decoding of the shared channel communication.

[0172] Figure 17 FIG. illustrates a system 1700 including a device 1705 that supports paging techniques for wireless devices with hybrid capabilities, in accordance with one or more aspects of the present disclosure. The device 1705 may be an example of the device 1405, the device 1505, or the network entity 105 as described herein, or include components thereof. The device 1705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication via one or more wired interfaces, via one or more wireless interfaces, or any combination thereof. The device 1705 may include components that support outputting and obtaining communication, such as a communication manager 1720, a transceiver 1710, an antenna 1715, a memory 1725, code 1730, and a processor 1735. These components may be electronically communicated or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) coupled via one or more buses (e.g., bus 1740).

[0173] As described herein, the transceiver 1710 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1710 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1710 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1705 may include one or more antennas 1715, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1710 may also include a modem for: modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1715, via a wired transmitter), receiving a modulated signal (e.g., from one or more antennas 1715, from a wired receiver), and demodulating a signal. In some implementations, the transceiver 1710 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1715 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1715 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1710 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 1710 or the transceiver 1710 and one or more antennas 1715 or the transceiver 1710 and one or more antennas 1715 and one or more processors or memory components (e.g., processor 1735 or memory 1725 or both) may be included in a chip or chip assembly installed in the device 1705. 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).

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

[0175] The processor 1735 may include intelligent hardware devices (such as general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1735 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 1735. The processor 1735 may be configured to execute computer-readable instructions stored in a memory (such as the memory 1725) to cause the device 1705 to perform various functions (such as functions or tasks supporting paging techniques for wireless devices with hybrid capabilities). For example, the device 1705 or components of the device 1705 may include the processor 1735 and the memory 1725 coupled to the processor 1735, and the processor 1735 and the memory 1725 are configured to perform the various functions described herein. The processor 1735 may be an example of a cloud computing platform (such as one or more physical nodes and supporting software, such as an operating system, virtual machine, or container instance), which may host functions for performing the functions of the device 1705 (such as by executing the code 1730). The processor 1735 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1705 (such as within the memory 1725). In some specific implementations, the processor 1735 may be a component of a processing system. A processing system generally may refer to a system or series of machines or components that receive inputs and process these inputs to produce a set of outputs (the set of outputs may be passed to other systems or components of, for example, the device 1705). For example, the processing system of the device 1705 may refer to a system including various other components or sub-components of the device 1705, such as the processor 1735 or the transceiver 1710 or the communication manager 1720 or a combination of other components or components of the device 1705. The processing system of the device 1705 may interface with other components of the device 1705 and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of the device 1705 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 the processing system of the chip or modem and a transmitter such that the device 1705 may transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver such that the device 1705 can obtain information or signal input and the information can be passed to the processing system. One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input and the second interface may also output information or signal output.

[0176] In some examples, the bus 1740 may support communication within a protocol layer of a protocol stack (e.g., within the protocol layer). In some examples, the bus 1740 may support communication associated with a logical channel of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of the device 1705 or communication performed between different components of the device 1705 that may be co-located or located at different locations (e.g., where the device 1705 may refer to a system in which one or more of the communication manager 1720, transceiver 1710, memory 1725, code 1730, and processor 1735 may be located in one component or divided among different components).

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

[0178] According to an example as disclosed herein, the communication manager 1720 may support wireless communication at a network entity. For example, the communication manager 1720 may be configured to or otherwise support components for sending control signaling communication for PEI to at least a first UE in a DRX cycle, where the PEI is associated with a subsequent PO configured for multiple different types of UEs, and the PEI includes one or more paging indication fields mapped to one or more UE subgroups, and the one or more UE subgroups include a first set of paging subgroups of a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups of a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The communication manager 1720 may be configured to or otherwise support components for sending a paging message to the first UE in a first paging resource associated with the first type of UE based on the first UE being a first type of UE and the subgroup ID in the PEI being configured for the first type of UE.

[0179] By including or configuring the communication manager 1720 according to an example as described herein, the device 1705 may support techniques for indicating whether a UE is to monitor one or more paging messages, which may reduce power consumption due to a shorter UE wake-up time, reduce latency due to improved paging message timing, and / or reduce consumption of processing resources due to fewer blind decoding operations, which may provide enhanced system efficiency and an enhanced user experience.

[0180] In some examples, the communication manager 1720 may be configured to use or otherwise cooperate with the transceiver 1710, one or more antennas 1715 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, obtain, monitor, output, transmit). Although the communication manager 1720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1720 may be supported or performed by the transceiver 1710, the processor 1735, the memory 1725, the code 1730, or any combination thereof. For example, the code 1730 may include instructions executable by the processor 1735 to cause the device 1705 to perform aspects of the paging techniques for wireless devices with hybrid capabilities as described herein, or the processor 1735 and the memory 1725 may be otherwise configured to perform or support such operations.

[0181] Figure 18 A flowchart of an illustrative method 1800 supporting paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure is illustrated. The operations of method 1800 may be implemented by a UE or its components as described herein. For example, the operations of method 1800 may be implemented by a UE as referenced Figures 1 to 13The described UE 115 performs. 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 aspects of the described functions.

[0182] At 1805, the method may include: receiving, in a DRX cycle, control signaling communication for a PEI associated with a subsequent PO configured for multiple different types of UEs, where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, and the one or more UE subgroups include a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The operations at 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations at 1805 may be performed by a PEI manager 1225 as described in reference to Figure 12 the description.

[0183] At 1810, the method may include: determining whether to monitor a subsequent PO associated with the PEI based on whether a subgroup ID in the PEI is configured for the UE type of a first UE. The operations at 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations at 1810 may be performed by a paging manager 1230 as described in reference to Figure 12 the description.

[0184] Figure 19 Illustrates a flowchart of an illustrative method 1900 that supports paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. The operations of method 1900 may be implemented by a UE or its components as described herein. For example, the operations of method 1900 may be performed by a UE 115 as described in reference to Figures 1 to 13 the description. 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 aspects of the described functions.

[0185] In 1905, the method may include: receiving control signaling communication for a PEI in a DRX cycle, the PEI being associated with subsequent POs configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The operations of 1905 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a PEI manager 1225 as described with reference to Figure 12 described.

[0186] In 1910, the method may include: determining whether to monitor a subsequent PO associated with the PEI based on whether a subgroup ID in the PEI is configured for the UE type of a first UE. The operations of 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a paging manager 1230 as described with reference to Figure 12 described.

[0187] In 1915, the method may include: receiving subsequent control signaling communication for a PEI in a subsequent DRX cycle, the PEI being associated with one or more subsequent POs configured for one or more multiple types of UEs. The operations of 1915 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1915 may be performed by a PEI manager 1225 as described with reference to Figure 12 described.

[0188] In 1920, the method may include: skipping monitoring one or more of the subsequent POs associated with the PEI based on a paging indication field that indicates that a subgroup ID configured for the UE type of a first UE will not be paged in the subsequent POs associated with the PEI. The operations of 1920 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1920 may be performed by a paging manager 1230 as described with reference to Figure 12 described.

[0189] Figure 20 FIG. 2000 is a flow diagram of an illustrative method for supporting paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. The operations of method 2000 may be implemented by a UE or its components as described herein. For example, the operations of method 2000 may be performed by a UE or its components as described with reference to Figures 1 to 13The described UE 115 performs. 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 aspects of the described functions.

[0190] In 2005, the method may include: receiving control signaling communication for a PEI in a DRX cycle, the PEI being associated with a subsequent PO configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The operations of 2005 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a PEI manager 1225 as described in reference Figure 12 described.

[0191] In 2010, the method may include: receiving a PEI in a DRX cycle, the PEI including a set of multiple paging indication fields for multiple UE types, the multiple UE types being allowed to monitor paging messages, short messages, system information, other control signaling of a serving network entity, or any combination thereof. The operations of 2010 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a PEI manager 1225 as described in reference Figure 12 described.

[0192] In 2015, the method may include: determining whether to monitor a subsequent PO associated with the PEI based on whether a subgroup ID in the PEI is configured for the UE type of a first UE. The operations of 2015 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a paging manager 1230 as described in reference Figure 12 described.

[0193] Figure 21 FIG. 2100 is a flow diagram of an illustrative method for supporting paging techniques for a wireless device with hybrid capabilities in accordance with one or more aspects of the present disclosure. The operations of method 2100 may be implemented by a UE or its components as described herein. For example, the operations of method 2100 may be performed by a UE 115 as described in reference Figures 1 to 13 described. 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 aspects of the described functions.

[0194] In 2105, the method may include: receiving a first PEI in a first set of resources of a first set of paging subgroups configured for a first type of UE, and receiving a second PEI in a second set of resources of a second set of paging subgroups configured for a second type of UE, wherein the first PEI and the second PEI are associated with POs respectively configured for different UE types or are shared by different UE types. The operations of 2105 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2105 may be performed by a PEI resource manager 1235 as described with reference to Figure 12 described.

[0195] In 2110, the method may include: determining whether to monitor a subsequent PO associated with the PEI based on whether a subgroup ID in the PEI is configured for the UE type of a first UE. The operations of 2110 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2110 may be performed by a paging manager 1230 as described with reference to Figure 12 described.

[0196] Figure 22 FIG. 2200 is a flow diagram illustrating an example method for supporting paging techniques for a wireless device having hybrid capabilities in accordance with one or more aspects of the present disclosure. The operations of method 2200 may be implemented by a UE or components thereof as described herein. For example, the operations of method 2200 may be performed by a UE 115 as described with reference to Figures 1 to 13 described. In some examples, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0197] In 2205, the method may include: receiving a PEI including a multi-bit field that indicates which of a first set of paging subgroups, a second set of paging subgroups, or any combination thereof will be paged in a subsequent PO associated with the PEI. The operations of 2205 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2205 may be performed by a subgroup ID manager 1240 as described with reference to Figure 12 described.

[0198] In 2210, the method may include: determining whether to monitor a subsequent PO associated with the PEI based on whether a subgroup ID in the PEI is configured for the UE type of a first UE. The operations of 2210 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 2210 may be performed by a paging manager 1230 as described with reference to Figure 12 described.

[0199] Figure 23A flowchart of an exemplary method 2300 is illustrated that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. Operations of method 2300 may be implemented by a network entity or its components as described herein. For example, operations of method 2300 may be performed by a network entity as described with reference to Figure 1 FIGS. 9 and Figures 14 to 17 described network entity. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0200] At 2305, the method may include: sending control signaling communication for a PEI to at least a first UE in a DRX cycle, the PEI being associated with a subsequent PO configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The operation of 2305 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 2305 may be performed by a PEI manager 1625 as described with reference to Figure 16 described.

[0201] At 2310, the method may include: sending a paging message to the first UE in a first paging resource associated with the first type of UE based on the first UE being a first type of UE and a subgroup ID in the PEI being configured for the first type of UE. The operation of 2310 may be performed in accordance with examples disclosed herein. In some examples, aspects of the operation of 2310 may be performed by a paging manager 1630 as described with reference to Figure 16 described.

[0202] Figure 24 A flowchart of an exemplary method 2400 is illustrated that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. Operations of method 2400 may be implemented by a network entity or its components as described herein. For example, operations of method 2400 may be performed by a network entity as described with reference to Figure 1 FIGS. 9 and Figures 14 to 17 described network entity. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0203] At 2405, the method may include: configuring one or more UEs to skip monitoring one or more subsequent POs associated with a PEI based on a paging indication field that indicates that a subgroup ID for a first UE type or a second UE type configured for each of the one or more UEs will not be paged in a subsequent PO associated with the PEI. The operations of 2405 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations of 2405 may be performed by a PEI manager 1625 as described with reference to Figure 16 described.

[0204] At 2410, the method may include: sending control signaling communication for a PEI to at least a first UE in a DRX cycle, the PEI being associated with subsequent POs configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The operations of 2410 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations of 2410 may be performed by a PEI manager 1625 as described with reference to Figure 16 described.

[0205] At 2415, the method may include: sending a paging message to a first UE in a first paging resource associated with the first type of UE based on the first UE being a first type of UE and the subgroup ID in the PEI being configured for the first type of UE. The operations of 2415 may be performed in accordance with the examples disclosed herein. In some examples, aspects of the operations of 2415 may be performed by a paging manager 1630 as described with reference to Figure 16 described.

[0206] Figure 25 Illustrates a flowchart of an example method 2500 that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. The operations of method 2500 may be implemented by a network entity or its components as described herein. For example, the operations of method 2500 may be performed by a network entity as described with reference to Figure 1 through FIG. 9 and Figures 14 to 17 described. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0207] At 2505, the method may include: sending control signaling communication for a PEI in a DRX cycle to at least a first UE, the PEI being associated with a subsequent PO configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups of a first type of UEs configured to support a first receive bandwidth configuration and a second set of paging subgroups of a second type of UEs configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration. The operations at 2505 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 2505 may be performed by a PEI manager 1625 as described with reference to Figure 16 described.

[0208] At 2510, the method may include: sending a PEI in a DRX cycle, the PEI including a set of multiple paging indication fields for multiple UE types, the multiple UE types being allowed to monitor paging messages, short messages, system information, other control signaling of a serving network entity, or any combination thereof. The operations at 2510 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 2510 may be performed by a PEI manager 1625 as described with reference to Figure 16 described.

[0209] At 2515, the method may include: sending a paging message to a first UE in a first paging resource associated with the first UE based on the first UE being a first type of UE and a subgroup ID in the PEI being configured for the first type of UE. The operations at 2515 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 2515 may be performed by a paging manager 1630 as described with reference to Figure 16 described.

[0210] Figure 26 illustrates a flowchart of an example method 2600 that supports paging techniques for wireless devices with hybrid capabilities in accordance with one or more aspects of the present disclosure. The operations of method 2600 may be implemented by a network entity or its components as described herein. For example, the operations of method 2600 may be performed by a network entity as described with reference to Figure 1 to FIG. 9 and Figures 14 to 17 described. In some examples, the network entity may execute a set of instructions to control functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0211] At 2605, the method may include: transmitting a first PEI in a first set of resources of a first set of paging subgroups configured for UEs of a first type. The operations at 2605 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 2605 may be performed by a PEI resource manager 1635 as described with reference to Figure 16 described.

[0212] At 2610, the method may include: transmitting a second PEI in a second set of resources of a second set of paging subgroups configured for UEs of a second type, where the first PEI and the second PEI are associated with or shared by POs respectively configured for different UE types. The operations at 2610 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 2610 may be performed by a PEI resource manager 1635 as described with reference to Figure 16 described.

[0213] At 2615, the method may include: transmitting a paging message to a first UE in a first paging resource associated with the first type of UE based on the first UE being a UE of the first type and a subgroup ID in the PEI being configured for UEs of the first type of UE type. The operations at 2615 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 2615 may be performed by a paging manager 1630 as described with reference to Figure 16 described.

[0214] An overview of aspects of the present disclosure is provided below:

[0215] Aspect 1: A method for wireless communication at a first UE, the method including: receiving, in a DRX cycle, control signaling communication for a paging early indication (PEI) associated with subsequent paging occasions configured for multiple different types of UEs, where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups configured for UEs of a first type that support a first receive bandwidth configuration and a second set of paging subgroups configured for UEs of a second type that support a second receive bandwidth configuration different from the first receive bandwidth configuration; and determining whether to monitor the subsequent paging occasion associated with the PEI based at least in part on whether a subgroup identifier (ID) in the PEI is configured for the UE type of the first UE.

[0216] Aspect 2: The method according to aspect 1, the method further comprising: receiving, in a subsequent DRX cycle, subsequent control signaling communication for a PEI, the PEI being associated with one or more subsequent paging occasions configured for one or more of a plurality of types of UEs; and skipping, at least in part based on a paging indication field, monitoring one or more of the subsequent paging occasions associated with the PEI, the paging indication field indicating that the subgroup ID of the UE type configured for the first UE will not be paged in the subsequent paging occasion associated with the PEI.

[0217] Aspect 3: The method according to any one of aspects 1 to 2, wherein receiving the control signaling communication comprises: receiving, in the DRX cycle, the PEI, the PEI including a plurality of PEI fields for a plurality of UE types, the plurality of UE types being allowed to monitor paging messages, short messages, system information, other control signaling of a serving network entity, or any combination thereof.

[0218] Aspect 4: The method according to aspect 3, wherein each PEI field of the plurality of PEI fields is associated with an identification of a different set of paging subgroup IDs and indicates whether UEs sharing the same subgroup ID will be paged in the subsequent paging occasion associated with the PEI.

[0219] Aspect 5: The method according to aspect 4, wherein the plurality of PEI fields includes one or more of a first PEI field, a second PEI field, or a third PEI field, wherein the first PEI field provides a first set of subgroup IDs configured by a core network entity, the second PEI field provides a second set of subgroup IDs associated with a UE ID or a UE class ID, and the third PEI field provides a third set of subgroup IDs configured at a serving cell belonging to a radio access network (RAN) notification area (RNA) of the UE.

[0220] Aspect 6: The method according to any one of aspects 3 to 5, wherein the first control signaling further indicates activating, for a UE in an idle or inactive state, one or more downlink reference signals associated with the one or more UE subgroups.

[0221] Aspect 7: The method according to aspect 6, wherein the one or more downlink reference signals include one or more of a tracking reference signal, a non-cell defined (NCD) synchronization signal block (SSB), a positioning reference signal (PRS), or any combination thereof.

[0222] Aspect 8: The method according to aspect 1, wherein receiving the control signaling communication includes: receiving a first PEI in a first set of resources of the first set of paging subgroups configured for the first type of UE, and receiving a second PEI in a second set of resources of the second set of paging subgroups configured for the second type of UE, wherein the first PEI and the second PEI are associated with a PO respectively configured for different UE types or shared by different UE types.

[0223] Aspect 9: The method according to aspect 8, wherein the first set of resources is indicated by a configuration of a first control resource set (CORESET) associated with the first set of paging subgroups, and the second set of resources is indicated by a configuration of a second CORESET associated with the second set of paging subgroups.

[0224] Aspect 10: The method according to any one of aspects 8 to 9, wherein the first set of resources is associated with a first search space set configured for the first set of paging subgroups, and the second set of resources is associated with a second search space set configured for the second set of paging subgroups.

[0225] Aspect 11: The method according to any one of aspects 8 to 10, wherein the first PEI is scrambled with a first group of radio network temporary identifiers (G-RNTIs) associated with the first set of paging subgroups, and wherein a second G-RNTI is used to scramble the second PEI of the second set of paging subgroups.

[0226] Aspect 12: The method according to any one of aspects 8 to 11, wherein the first set of resources is associated with a first DMRS or a first waveform configuration associated with the first set of paging subgroups, and the second set of resources is associated with a second DMRS or a second waveform configuration associated with the second set of paging subgroups.

[0227] Aspect 13: The method according to aspect 1, wherein receiving the control signaling communication includes: receiving a PEI including a multi-bit field that indicates which of the first set of paging subgroups, the second set of paging subgroups, or any combination thereof will be paged in the subsequent paging occasion associated with the PEI.

[0228] Aspect 14: The method according to aspect 1, wherein the first UE monitors the paging occasion of the downlink control channel, the downlink control channel provides resource allocation for shared channel communication including a paging message, and wherein based on the shared channel communication not carrying any paging message for the first set of paging subgroups or the second set of paging subgroups, the downlink control channel indicates that one or more of the first set of paging subgroups or the second set of paging subgroups will skip decoding the shared channel communication.

[0229] Aspect 15: A method for wireless communication at a network entity, the method comprising: sending control signaling communication for a paging early indication (PEI) to at least a first UE in a DRX cycle, the paging early indication (PEI) being associated with subsequent paging occasions configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups for a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups for a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration; and sending a paging message to the first UE in a first paging resource associated with the first type of UE at least partially based on the first UE being the first type of UE and a subgroup identifier (ID) in the PEI being configured for the first type of UE.

[0230] Aspect 16: The method according to aspect 15, the method further comprising: configuring one or more UEs to skip monitoring one or more subsequent paging occasions associated with the PEI at least partially based on a paging indication field indicating that the subgroup ID for the first UE type or the second UE type associated with each of the one or more UEs will not be paged at the subsequent paging occasion associated with the PEI.

[0231] Aspect 17: The method according to any one of aspects 15 to 16, wherein sending the control signaling communication comprises: sending the PEI in the DRX cycle, the PEI including multiple PEI fields for multiple UE types, the multiple UE types being allowed to monitor paging messages, short messages, system information, other control signaling of a serving network entity, or any combination thereof.

[0232] Aspect 18: The method according to aspect 17, wherein each PEI field in the multiple PEI fields is associated with the identification of a different set of paging subgroup IDs and indicates whether UEs sharing the same subgroup ID will be paged at the subsequent paging occasion associated with the PEI.

[0233] Aspect 19: The method according to aspect 18, wherein the plurality of PEI fields include one or more of a first PEI field, a second PEI field, or a third PEI field, wherein the first PEI field provides a first set of subgroup IDs configured by a core network entity, the second PEI field provides a second set of subgroup IDs associated with a UE ID or a UE class ID, and the third PEI field provides a third set of subgroup IDs configured at a serving cell belonging to a radio access network (RAN) notification area (RNA) of the UE.

[0234] Aspect 20: The method according to any one of aspects 17 to 19, wherein the first control signaling further indicates activation of one or more downlink reference signals associated with the one or more UE subgroups for a UE in an idle or inactive state.

[0235] Aspect 21: The method according to aspect 20, wherein the one or more downlink reference signals include one or more of a tracking reference signal, a non-cell-defined (NCD) synchronization signal block (SSB), a positioning reference signal (PRS), or any combination thereof.

[0236] Aspect 22: The method according to aspect 15, wherein transmitting the control signaling communication includes: transmitting a first PEI in a first set of resources of a first set of paging subgroups configured for the first type of UE; and transmitting a second PEI in a second set of resources of a second set of paging subgroups configured for the second type of UE, wherein the first PEI and the second PEI are associated with a PO configured for different UE types or shared by different UE types.

[0237] Aspect 23: The method according to aspect 22, wherein the first set of resources is indicated by a configuration of a first control resource set (CORESET) associated with the first set of paging subgroups, and the second set of resources is indicated by a configuration of a second CORESET associated with the second set of paging subgroups.

[0238] Aspect 24: The method according to any one of aspects 22 to 23, wherein the first set of resources is associated with a first search space set configured for the first set of paging subgroups, and the second set of resources is associated with a second search space set configured for the second set of paging subgroups.

[0239] Aspect 25: The method according to any one of aspects 22 to 24, wherein the first PEI is scrambled with a first set of radio network temporary identifiers (G-RNTIs) associated with the first set of paging subgroups, and wherein a second G-RNTI is used to scramble the second PEI of the second set of paging subgroups.

[0240] Aspect 26: The method according to any one of aspects 22 to 25, wherein the first set of resources is associated with a first DMRS or a first waveform configuration associated with the first set of paging subgroups, and the second set of resources is associated with a second DMRS or a second waveform configuration associated with the second set of paging subgroups.

[0241] Aspect 27: The method according to aspect 15, wherein transmitting the control signaling communication includes: transmitting a PEI including a multi-bit field indicating which one of the first set of paging subgroups, the second set of paging subgroups, or any combination thereof will be paged in the subsequent paging occasion associated with the PEI.

[0242] Aspect 28: The method according to aspect 15, wherein the first UE monitors the paging occasion of a downlink control channel, the downlink control channel providing resource allocation for a shared channel communication including a paging message, and wherein based on the shared channel communication not carrying any paging message for the first set of paging subgroups or the second set of paging subgroups, the downlink control channel indicates that one or more of the first set of paging subgroups or the second set of paging subgroups will skip decoding of the shared channel communication.

[0243] Aspect 29: A first UE, the first UE including: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first UE to perform the method according to any one of aspects 1 to 14.

[0244] Aspect 30: A first UE, the first UE including at least one component for performing the method according to any one of aspects 1 to 14.

[0245] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 14.

[0246] Aspect 32: A network entity, the network entity comprising: one or more memories that store processor-executable code; and one or more processors coupled to the one or more memories and operable, individually or jointly, to execute the code to cause the network entity to perform the method according to any one of Aspects 15 to 28.

[0247] Aspect 33: A network entity, the network entity comprising at least one component for performing the method according to any one of Aspects 15 to 28.

[0248] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by one or more processors to perform the method according to any one of Aspects 15 to 28.

[0249] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps may be rearranged or otherwise modified and other specific implementations are also possible. Additionally, aspects from two or more of these methods may be combined.

[0250] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques 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.

[0251] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to 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.

[0252] The various illustrative blocks and components described in this disclosure may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the 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).

[0253] 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 code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software, hardware, firmware, hardwiring, or any combination of these. The features implementing the functions may also be physically located at different positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0254] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that can be accessed by a general or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general or special purpose computer or a general or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted 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 microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disk may reproduce data magnetically, and disc may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0255] As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items accompanied by a phrase such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, a listing 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 construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may 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 "at least partially based on".

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

[0257] In the drawings, like reference numerals may be used to refer to like components or features. Additionally, various components of the same type may be distinguished by adding a dash and a second label used to differentiate between like components after the reference numeral. If only the first reference numeral is used in the specification, the description may apply to any one of the like components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0258] The description set forth herein with reference to the drawings describes example configurations and does not represent all examples that may be implemented or are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples". The detailed description includes specific details for providing an understanding of the described technology. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0259] The present description is provided to enable a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person 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 is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first user equipment (UE) for wireless communication, the first user equipment (UE) comprises: one or more memories that store processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first UE to: receive control signaling communication for a paging early indication (PEI) in a discontinuous reception (DRX) cycle, the paging early indication (PEI) being associated with subsequent paging occasions configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups of a first type of UE configured to support a first reception bandwidth configuration and a second set of paging subgroups of a second type of UE configured to support a second reception bandwidth configuration different from the first reception bandwidth configuration; and determine whether to monitor the subsequent paging occasion associated with the PEI at least in part based on whether a subgroup identifier (ID) in the PEI is configured for the UE type of the first UE.

2. The first UE according to claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first UE to: receive subsequent control signaling communication for the PEI in a subsequent DRX cycle, the PEI being associated with one or more subsequent paging occasions configured for one or more multiple types of UEs; and skip monitoring one or more of the subsequent paging occasions associated with the PEI at least in part based on a paging indication field indicating that the subgroup ID configured for the UE type of the first UE will not be paged in the subsequent paging occasion associated with the PEI.

3. The first UE according to claim 1, wherein, to receive the control signaling communication, the one or more processors are capable of operating individually or jointly to execute the code to cause the first UE to: receive the PEI in the DRX cycle, the PEI including multiple paging indication fields for multiple UE types that are permitted to monitor paging messages, short messages, system information, other control signaling of a serving network entity, or any combination thereof.

4. The first UE according to claim 3, wherein each paging indication field of the multiple paging indication fields is associated with the identification of a different set of paging subgroup IDs and indicates whether UEs sharing the same subgroup ID will be paged in the subsequent paging occasion associated with the PEI.

5. The first UE according to claim 4, wherein the plurality of paging indication fields include one or more of a first paging indication field, a second paging indication field, or a third paging indication field, wherein the first paging indication field provides a first set of subgroup IDs configured by a core network entity, the second paging indication field provides a second set of subgroup IDs associated with a UE ID or a UE class ID, and the third paging indication field provides a third set of subgroup IDs configured at a serving cell belonging to a radio access network (RAN) notification area (RNA) of the UE.

6. The first UE according to claim 3, wherein the first control signaling further indicates activation of one or more downlink reference signals associated with the one or more UE subgroups for a UE in an idle or inactive state.

7. The first UE according to claim 6, wherein the one or more downlink reference signals include one or more of a tracking reference signal, a non-cell defined (NCD) synchronization signal block (SSB), a positioning reference signal (PRS), or any combination thereof.

8. The first UE according to claim 1, wherein, for receiving the control signaling communication, the one or more processors are individually or jointly operable to execute the code to cause the first UE to: receive a first PEI in a first set of resources of a first set of paging subgroups configured for the first type of UE, and receive a second PEI in a second set of resources of a second set of paging subgroups configured for the second type of UE, wherein the first PEI and the second PEI are associated with a PO configured for different UE types or shared by different UE types.

9. The first UE according to claim 8, wherein the first set of resources is indicated by a first control resource set (CORESET) associated with the first set of paging subgroups, and the second set of resources is indicated by a second CORESET associated with the second set of paging subgroups.

10. The first UE according to claim 8, wherein the first set of resources is associated with a first search space set configured for the first set of paging subgroups, and the second set of resources is associated with a second search space set configured for the second set of paging subgroups.

11. The first UE according to claim 8, wherein the first PEI is scrambled with a first set of radio network temporary identifiers (G-RNTIs) associated with the first set of paging subgroups, and wherein a second G-RNTI is used to scramble the second PEI of the second set of paging subgroups.

12. The first UE according to claim 8, wherein the first set of resources is associated with a first demodulation reference signal (DMRS) or a first waveform configuration associated with the first set of paging subgroups, and the second set of resources is associated with a second DMRS or a second waveform configuration associated with the second set of paging subgroups.

13. The first UE according to claim 1, wherein, To receive the control signaling communication, the one or more processors are individually or jointly operable to execute the code to cause the first UE to: Receive a PEI including a multi-bit field indicating which one of the first set of paging subgroups, the second set of paging subgroups, or any combination thereof will be paged at the subsequent paging occasion associated with the PEI.

14. The first UE according to claim 1, wherein the first UE monitors the paging occasion of a downlink control channel, the downlink control channel provides resource allocation for shared channel communication including a paging message, and wherein based on the shared channel communication not carrying any paging message for the first set of paging subgroups or the second set of paging subgroups, the downlink control channel indicates that one or more of the first set of paging subgroups or the second set of paging subgroups will skip decoding of the shared channel communication.

15. A network entity for wireless communication, the network entity comprising: One or more memories that store processor-executable code; and One or more processors coupled to the one or more memories and individually or jointly operable to execute the code to cause the network entity to: Send control signaling communication for a paging early indication (PEI) to at least a first user equipment (UE) in a discontinuous reception (DRX) cycle, the paging early indication (PEI) being associated with a subsequent paging occasion configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups of a first type of UE configured to support a first reception bandwidth configuration and a second set of paging subgroups of a second type of UE configured to support a second reception bandwidth configuration different from the first reception bandwidth configuration; and Send a paging message to the first UE in a first paging resource associated with the first type of UE at least in part based on the first UE being the first type of UE and a subgroup identifier (ID) in the PEI being configured for the first type of UE.

16. The network entity according to claim 15, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Configure one or more UEs to skip monitoring one or more subsequent paging occasions associated with the PEI at least in part based on a paging indication field indicating that the subgroup ID for the first UE type or the second UE type associated with each of the one or more UEs will not be paged at the subsequent paging occasion associated with the PEI.

17. The network entity according to claim 15, wherein, To send the control signaling communication, the one or more processors are individually or jointly operable to execute the code to cause the network entity to: Send the PEI in the DRX cycle, the PEI including a plurality of paging indication fields for a plurality of UE types, the plurality of UE types being allowed to monitor paging messages, short messages, system information, other control signaling of the serving network entity, or any combination thereof.

18. The network entity according to claim 17, wherein each paging indication field among the plurality of paging indication fields is associated with an identification of a different set of paging subgroup IDs and indicates whether UEs sharing the same subgroup ID will be paged at the subsequent paging occasion associated with the PEI, and wherein the plurality of paging indication fields includes one or more of a first paging indication field, a second paging indication field, or a third paging indication field, wherein the first paging indication field provides a first set of subgroup IDs configured by a core network entity, the second paging indication field provides a second set of subgroup IDs associated with a UE ID or a UE class ID, and the third paging indication field provides a third set of subgroup IDs configured at a serving cell belonging to a radio access network (RAN) notification area (RNA) of the UE.

19. The network entity according to claim 17, wherein the first control signaling further indicates activation of one or more downlink reference signals associated with the one or more UE subgroups for UEs in an idle or inactive state, and wherein the one or more downlink reference signals include one or more of a tracking reference signal, a non-cell-defined (NCD) synchronization signal block (SSB), a positioning reference signal (PRS), or any combination thereof.

20. The network entity according to claim 15, wherein, To send the control signaling communication, the one or more processors are individually or jointly operable to execute the code to cause the network entity to: Send a first PEI in a first set of resources of the first set of paging subgroups configured for the first type of UE; and Send a second PEI in a second set of resources of the second set of paging subgroups configured for the second type of UE, wherein the first PEI and the second PEI are associated with or shared by paging occasions respectively configured for different UE types.

21. The network entity according to claim 20, wherein: The first set of resources is indicated by a first control resource set (CORESET) associated with the first set of paging subgroups, and the second set of resources is indicated by a second CORESET associated with the second set of paging subgroups, The first set of resources is associated with a first search space set configured for the first set of paging subgroups, and the second set of resources is associated with a second search space set configured for the second set of paging subgroups, The first PEI is scrambled with a first set of radio network temporary identifiers (G-RNTIs) associated with the first set of paging subgroups, and wherein a second G-RNTI is used to scramble the second PEI of the second set of paging subgroups, or The first set of resources is associated with a first demodulation reference signal (DMRS) or a first waveform configuration associated with the first set of paging subgroups, and the second set of resources is associated with a second DMRS or a second waveform configuration associated with the second set of paging subgroups.

22. The network entity according to claim 15, wherein, For transmitting the control signaling communication, the one or more processors are operable, individually or jointly, to execute the code to cause the network entity to: Transmit a PEI including a multi-bit field indicating which of the first set of paging subgroups, the second set of paging subgroups, or any combination thereof will be paged at the subsequent paging occasion associated with the PEI.

23. The network entity according to claim 15, wherein the first UE monitors the paging occasion of the downlink control channel, the downlink control channel provides resource allocation for shared channel communication including a paging message, and wherein based on the shared channel communication not carrying any paging message for the first set of paging subgroups or the second set of paging subgroups, the downlink control channel indicates that one or more of the first set of paging subgroups or the second set of paging subgroups will skip decoding of the shared channel communication.

24. A method for wireless communication by a first user equipment (UE), the method comprising: Receiving control signaling communication for a paging early indication (PEI) in a discontinuous reception (DRX) cycle, the paging early indication (PEI) being associated with a subsequent paging occasion configured for multiple different types of UEs, wherein the PEI includes one or more paging indication fields mapped to one or more UE subgroups, the one or more UE subgroups including a first set of paging subgroups of a first type of UE configured to support a first receive bandwidth configuration and a second set of paging subgroups of a second type of UE configured to support a second receive bandwidth configuration different from the first receive bandwidth configuration; and Determining whether to monitor the subsequent paging occasion associated with the PEI at least in part based on whether a subgroup identifier (ID) in the PEI is configured for the UE type of the first UE.

25. The method according to claim 24, the method further comprising: Receiving subsequent control signaling communication for a PEI in a subsequent DRX cycle, the PEI being associated with one or more subsequent paging occasions configured for one or more multiple types of UEs; and Skip monitoring one or more subsequent paging occasions in the subsequent paging occasions associated with the PEI, at least in part based on a paging indication field, where the paging indication field indicates that the subgroup ID of the UE type configured for the first UE will not be paged in the subsequent paging occasions associated with the PEI.

26. The method according to claim 24, wherein receiving the control signaling communication comprises: Receiving the PEI in the DRX cycle, where the PEI includes a plurality of paging indication fields for a plurality of UE types, and the plurality of UE types are allowed to monitor paging messages, short messages, system information, other control signaling of the serving network entity, or any combination thereof.

27. The method according to claim 24, wherein receiving the control signaling communication comprises: Receiving a first PEI in a first set of resources of a first set of paging subgroups configured for the first type of UE, and receiving a second PEI in a second set of resources of a second set of paging subgroups configured for the second type of UE, where the first PEI and the second PEI are associated with paging occasions configured for different UE types or are shared by different UE types.

28. A method for wireless communication by a network entity, the method comprises: Sending control signaling communication for a paging early indication (PEI) to at least a first user equipment (UE) in a discontinuous reception (DRX) cycle, where the paging early indication (PEI) is associated with subsequent paging occasions configured for a plurality of different types of UEs, and where the PEI includes one or more paging indication fields mapped to one or more UE subgroups, and the one or more UE subgroups include a first set of paging subgroups of a first type of UE configured to support a first reception bandwidth configuration and a second set of paging subgroups of a second type of UE configured to support a second reception bandwidth configuration different from the first reception bandwidth configuration; and Sending a paging message to the first UE in a first paging resource associated with the first type of UE, at least in part based on the first UE being the first type of UE and the subgroup identifier (ID) in the PEI being configured for the UE type of the first type of UE.

29. The method according to claim 28, the method further comprises: Configuring one or more UEs to skip monitoring one or more subsequent paging occasions associated with the PEI, at least in part based on a paging indication field, where the paging indication field indicates that the subgroup ID of the first UE type or the second UE type configured for each of the one or more UEs will not be paged in the subsequent paging occasions associated with the PEI.

30. The method according to claim 28, wherein sending the control signaling communication comprises: Transmit the PEI in the DRX cycle, where the PEI includes a plurality of paging indication fields for a plurality of UE types, and the plurality of UE types are allowed to monitor paging messages, short messages, system information, other control signaling of the serving network entity, or any combination thereof.

Images