Handling downlink messages at connected devices

Abstract

Methods, systems, and devices for wireless communication are described. A wireless device may establish a non-cellular connection with a user equipment (UE) to operate in a connected mode. Additionally, the wireless device and UE may support a cellular connection with a wireless network. If the wireless network transmits a downlink message to the wireless device, the wireless device may refrain from receiving the downlink message via a cellular connection with the wireless network. For example, a wireless device may receive a wake-up signal from a network entity, the wake-up signal indicating that a message can be provided via a cellular connection. Based on operating in the connected mode, the wireless device may receive messages from the UE via a non-cellular connection, rather than receiving messages from the network entity via a cellular connection. In some examples, the UE may transmit a decoded version of the message to the wireless device.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 461,772, filed September 6, 2023, entitled “HANDLINGDOWNLINK MESSAGES AT CONNECTED DEVICES”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following text relates to wireless communication, including the handling of downlink messages at connected devices. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A 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 technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0005] Some wireless devices support non-cellular connectivity, such as Bluetooth. For example, a first wireless device can connect to (e.g., pair with) a second wireless device by establishing a non-cellular connection. Non-cellular connections can support communication between wireless devices, such as communication between a UE (e.g., a mobile phone) and a connected wireless device (e.g., a smartwatch). If the connected wireless device also connects to the wireless network via a cellular connection, cellular and non-cellular connections can potentially introduce redundant processing. In some cases, the wireless device may redundantly decode the same messages received via both cellular and non-cellular connections, thereby increasing processing overhead at the wireless device and reducing battery life. Summary of the Invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses that support handling downlink messages at connected devices. For example, the described techniques provide improved processing overhead and battery life at a wireless device supporting a non-cellular connection with a user equipment (UE). For example, a wireless device (e.g., a smart watch or other connected device) can establish a non-cellular connection (e.g., a Bluetooth connection) with another wireless device (e.g., a UE, such as a smartphone) to operate in a connected mode. Additionally, the wireless device and the UE can support a cellular connection with a wireless network. If a network entity of the wireless network transmits a downlink message to the wireless device via the cellular connection, the UE can receive the message and can forward the message to the wireless device via the non-cellular connection. To improve processing overhead and conserve power, the wireless device can refrain from receiving the downlink message via the cellular connection. For example, the wireless device can receive a wake-up signal from the network entity, where the wake-up signal indicates that the message is available to be provided to the wireless device via the cellular connection. Based on operating in the connected mode, the wireless device can refrain from receiving or decoding the message via the cellular connection in response to the wake-up signal, and can instead receive the message from the UE via the non-cellular connection. In some examples, the UE can transmit a decoded version of the message to the wireless device so that the wireless device can refrain from decoding the message. Such techniques can improve the battery life of the wireless device by reducing processing resources for downlink message reception if the wireless device is operating in the connected mode.

[0007] A method for wireless communication by a wireless device is described. The method can include establishing a non-cellular connection between the wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message is available to be provided via the cellular connection. The method can further include receiving the message via the non-cellular connection based on the operation of the wireless device in the connected mode with the UE.

[0008] A wireless device is described. The wireless device can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories. The one or more processors can be capable of operating individually or collectively to execute the code to cause the wireless device to establish a non-cellular connection between the wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and receive, from a network entity via a cellular connection, a wake-up signal indicating that a message can be provided via the cellular connection. The one or more processors can be capable of operating individually or collectively to further execute the code to cause the wireless device to receive the message via the non-cellular connection based on the operation of the wireless device in the connected mode with the UE.

[0009] Another wireless device for wireless communication is described. The wireless device can include means for establishing a non-cellular connection between the wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and means for receiving, from a network entity via a cellular connection, a wake-up signal indicating that a message can be provided via the cellular connection. The wireless device can further include means for receiving the message via the non-cellular connection based on the operation of the wireless device in the connected mode with the UE.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code can include instructions executable by a processor to establish a non-cellular connection between a wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and receive, from a network entity via a cellular connection, a wake-up signal indicating that a message can be provided via the cellular connection. The code can further include instructions executable by the processor to receive the message via the non-cellular connection based on the operation of the wireless device in the connected mode with the UE.

[0011] Some examples of the method, wireless device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for monitoring for the message via the non-cellular connection according to a paging cycle, where the message can be received via the non-cellular connection based on the monitoring.

[0012] Some examples of the method, wireless device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for refraining from performing a wake-up procedure in response to the wake-up signal based on the operation of the wireless device in the connected mode with the UE.

[0013] Some examples of the method, wireless device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving the message additionally via the cellular connection, and refraining from decoding the message received additionally via the cellular connection based on the operation of the wireless device in the connected mode with the UE.

[0014] Some examples of the method, wireless device, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for refraining from decoding the message received via the non-cellular connection based on the message being decoded at the UE.

[0015] In some examples of the method, wireless device, and non-transitory computer-readable medium described herein, the non-cellular connection includes a Bluetooth connection.

[0016] In some examples of the method, wireless device, and non-transitory computer-readable medium described herein, the wireless device includes a smart watch or a wearable device, and the smart watch or the wearable device is paired with the UE.

[0017] A method for wireless communication by a UE is described. The method can include establishing a non-cellular connection between the UE and a wireless device, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and receiving a message via a cellular connection with a network entity, the message being associated with the wireless device. The method can further include transmitting the message to the wireless device via the non-cellular connection based on the message being associated with the wireless device and the operation of the wireless device in the connected mode with the UE.

[0018] A UE is described. The UE can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories. The one or more processors can be individually or collectively capable of operating to execute the code to cause the UE to establish a non-cellular connection between the UE and a wireless device, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and receive a message via a cellular connection with a network entity, the message being associated with the wireless device. The one or more processors can be individually or collectively capable of operating to further execute the code to cause the UE to transmit the message to the wireless device via the non-cellular connection based on the message being associated with the wireless device and the operation of the wireless device in the connected mode with the UE.

[0019] Another UE for wireless communication is described. The UE can include means for establishing a non-cellular connection between the UE and a wireless device, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and means for receiving a message via a cellular connection with a network entity, the message being associated with the wireless device. The UE can further include means for transmitting the message to the wireless device via the non-cellular connection based on the message being associated with the wireless device and the operation of the wireless device in the connected mode with the UE.

[0020] A non-transitory computer-readable medium storing code for wireless communication is described. The code can include instructions executable by a processor to establish a non-cellular connection between a UE and a wireless device, the non-cellular connection supporting operation of the wireless device in a connected mode with the UE, and receive a message via a cellular connection with a network entity, the message being associated with the wireless device. The code can further include instructions executable by the processor to transmit the message to the wireless device via the non-cellular connection based on the message being associated with the wireless device and the operation of the wireless device in the connected mode with the UE.

[0021] In some examples of the method, UE, and non-transitory computer- readable medium described herein, transmitting the message via the non-cellular connection can include operations, features, means, or instructions for transmitting the message via the non-cellular connection according to a paging cycle.

[0022] Some examples of the method, UE, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for decoding the message received via the cellular connection, where transmitting the message via the non-cellular connection can include operations, features, means, or instructions for transmitting the decoded message to the wireless device via the non-cellular connection.

[0023] Some examples of the method, UE, and non-transitory computer- readable medium described herein can further include operations, features, means, or instructions for determining to forward the message to the wireless device based on the message including an indicator of the wireless device, where the message can be transmitted via the non-cellular connection based on the determination.

[0024] In some examples of the method, UE, and non-transitory computer- readable medium described herein, the non-cellular connection includes a Bluetooth connection.

[0025] In some examples of the method, UE, and non-transitory computer- readable medium described herein, the wireless device includes a smart watch or a wearable device, and the smart watch or the wearable device is paired with the UE. BRIEF DESCRIPTION OF DRAWINGS

[0026] Figure 1 AND Figure 2 An example of a wireless communications system that supports handling downlink messages at connected devices is shown in accordance with one or more aspects of the present disclosure.

[0027] Figure 3 An example of a flow diagram illustrating a method that supports handling downlink messages at connected devices is shown in accordance with one or more aspects of the present disclosure.

[0028] Figure 4 An example of a process flow that supports handling downlink messages at connected devices is shown in accordance with one or more aspects of the present disclosure.

[0029] Figure 5 AND Figure 6 A block diagram of a device that supports handling downlink messages at connected devices is shown in accordance with one or more aspects of the present disclosure.

[0030] Figure 7 A block diagram of a communications manager that supports handling downlink messages at connected devices is shown in accordance with one or more aspects of the present disclosure.

[0031] Figure 8 A diagram of a system including a device that supports handling downlink messages at connected devices is shown in accordance with one or more aspects of the present disclosure.

[0032] Figures 9 to 13 An example of a flow diagram illustrating a method that supports handling downlink messages at connected devices is shown in accordance with one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0033] Some wireless communications systems can include wireless devices that support non-cellular connections, such as Bluetooth connections. For example, a first wireless device can connect to a second wireless device (e.g., pair with it) by establishing a non-cellular connection. The non-cellular connection can support communications between the wireless devices, such as between a user equipment (UE) (e.g., a mobile phone) and a connected wireless device (e.g., a smart watch). Additionally or alternatively, the wireless devices can support a cellular connection with a wireless network. In some cases, a wireless device can establish both a cellular connection with a wireless network and a non-cellular connection with another wireless device (e.g., a UE). In some such cases, the cellular connection and the non-cellular connection can potentially introduce redundant processing at the wireless device. For example, the wireless device can redundantly decode the same message received via both the cellular connection and the non-cellular connection, potentially increasing processing overhead and reducing battery life at the wireless device.

[0034] If a wireless device operates in connected mode, it (e.g., a smartwatch or other connected device) can support techniques for efficiently handling downlink messages. For example, the wireless device may connect to a wireless network via a cellular connection and connect to a UE (e.g., a second wireless device) via a non-cellular connection. If a network entity of the wireless network sends a downlink message to the wireless device via a cellular connection, the UE may receive the message and may forward it to the wireless device via a non-cellular connection. To improve processing overhead and save power, the wireless device may avoid receiving the downlink message via the cellular connection. For example, the wireless device may receive a wake-up signal from a network entity, indicating that the message can be provided to the wireless device via the cellular connection. Based on operation in connected mode, the wireless device may respond to the wake-up signal to avoid receiving or decoding the message via the cellular connection and may alternatively receive the message from the UE via the non-cellular connection. By receiving the message via a non-cellular connection with the UE and avoiding receiving or decoding the message via a cellular connection with the wireless network, the wireless device avoids redundant processing and correspondingly improves processing overhead and battery life.

[0035] In some examples, the UE may transmit a decoded version of a message to a wireless device via a non-cellular connection (e.g., Bluetooth), allowing the wireless device to determine the message content without decoding the message. Additionally or alternatively, the wireless device may receive messages from the UE according to the paging cycle of the non-cellular connection. For example, the wireless device may wake up based on a Bluetooth paging cycle and monitor one or more messages transmitted as paging messages via a non-cellular connection.

[0036] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described by way of process flow diagrams, apparatus diagrams, system diagrams, and flowcharts relating to the processing of downlink messages at a connected device.

[0037] Figure 1 An example of a wireless communication system 100 supporting the handling of downlink messages at a connected device according to one or more aspects of this disclosure is shown. 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 Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0038] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0039] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0040] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be 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 disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a 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.

[0041] In some examples, network entity 105 may communicate with core network 130, communicate 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 entities 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 entities 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 links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

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

[0043] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0044] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 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) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0045] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can 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 DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with 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 node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0046] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an 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 RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the 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 a part of the backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be a part of the backhaul link).

[0047] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 may provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE 115.

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

[0049] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the handling of downlink messages at connected devices as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

[0051] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc.Figure 1 As shown.

[0052] UE 115 and network entity 105 can 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" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) 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 coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

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

[0054] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with 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).

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

[0056] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number 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)).

[0057] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), 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 (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

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

[0059] Some UE 115 devices (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 may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable 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 geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

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

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

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

[0063] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0064] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

[0066] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0067] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission via logical channels. The MAC layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer can map transport channels to physical channels.

[0068] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0069] In some examples, wireless devices within the wireless communication system 100 may additionally support non-cellular connectivity. For example, a wireless device (e.g., UE 115) may support a cellular connection with network entity 105. A cellular connection may be an example of a wireless connection supporting communication according to a cellular RAT (such as LTE, LTE-A, LTE-A Pro, NR, or any other cellular RAT). A wireless device may additionally support a non-cellular connection with another wireless device. A non-cellular connection may be an example of a wireless connection (e.g., a D2D connection) supporting communication according to a non-cellular RAT (such as Bluetooth, Wi-Fi, or any other non-cellular RAT). For example, a smartwatch (e.g., first UE 115) may connect to a wireless network via a cellular connection and may additionally connect to a smartphone (e.g., second UE 115) via a non-cellular connection.

[0070] Wireless devices (such as UE 115) may include Bluetooth-enabled devices capable of pairing with other Bluetooth-enabled devices, which may include wireless audio devices (e.g., headsets, earphones, speakers, headphones, headphones), display devices (e.g., televisions, computer monitors), microphones, meters, valves, or any other devices. Bluetooth communication can refer to a short-range communication protocol and can be used to connect and exchange information between wireless devices (e.g., between mobile phones, computers, smartwatches or other wearable devices, digital cameras, wireless headsets, speakers, keyboards, mice or other input peripherals, and similar devices). Bluetooth systems may be organized using a master-slave relationship employing a time-division duplex protocol with defined time slots, such as 625 microseconds, in which transmission alternates between a master device (e.g., a smartphone) and one or more slave devices (e.g., paired devices, such as smartwatches). In some examples, UE 115 may generally refer to a master device in wireless communication system 100, and wireless devices may refer to slave devices. However, the master device and slave device can each be examples of a wireless device, UE 115, or both. Additionally, a wireless device can be referred to as a connected device or a device operating in a connected mode based on the device's Bluetooth role configuration. That is, designating a wireless device as a connected device may not indicate a difference in device capabilities, but rather may refer to or indicate the role the wireless device plays in the wireless communication system 100.

[0071] Bluetooth-enabled devices are compatible with specific Bluetooth profiles to use the required services. A Bluetooth profile can refer to a specification about one aspect of Bluetooth-based wireless communication between devices. That is, a profile specification can refer to a set of instructions for using the Bluetooth protocol stack in a specific way and can include information such as a suggested user interface format, options and parameters at each layer of the Bluetooth protocol stack. For example, the Bluetooth specification can include various profiles that define the behavior associated with each communication endpoint to implement a specific use case. Profiles can be defined according to a protocol stack that facilitates and allows interoperability between endpoint devices from different manufacturers by enabling applications to discover and use services that other nearby Bluetooth-enabled devices may be providing. The Bluetooth specification defines pairs of device roles (e.g., the role of a wireless device connected to UE 115), which together form a single use case called a profile (e.g., for communication between the wireless device and UE 115). An example profile defined in the Bluetooth specification is a hands-free profile (HFP) for voice telephony, where one device implements the audio gateway (AG) role and the other implements the hands-free (HF) device role. Another example is the Advanced Audio Distribution Profile (A2DP) for high-quality audio streaming, where one device implements the Audio Source Device (SRC) role and the other device implements the Audio Destination Device (SNK) role.

[0072] For a Bluetooth-enabled commercial device to function correctly in a configuration file that implements a role, another device implementing the corresponding role can be within the radio range of the first device. For example, for an HF device (such as a Bluetooth headset) operating according to a hands-free configuration file, a device implementing the AG role (e.g., a cellular phone) can be within radio range. Similarly, for high-quality mono or stereo audio streaming according to A2DP, a device implementing the SNK role (e.g., a Bluetooth headset or Bluetooth speaker) can be within radio range of a device implementing the SRC role (e.g., a stereo music player).

[0073] The Bluetooth specification defines a layered data transmission architecture and various protocols and procedures for handling data communicated between two devices implementing specific profile use cases. For example, various logical links can be used to support different application data transmission thresholds, with each logical link associated with logical transmissions possessing specific characteristics such as flow control, acknowledgment mechanisms, repetition mechanisms, sequence numbering, and scheduling behavior. The Bluetooth protocol stack can be divided into two parts: a controller stack that includes a timing-critical radio interface, and a host stack that handles high-level data. The controller stack can be implemented in a relatively low-cost silicon device comprising a Bluetooth radio and a microprocessor. The controller stack can be responsible for establishing connection links, such as asynchronous connectionless (ACL) links (or ACL connections), synchronous connection-oriented (SCO) links (or SCO connections), extended synchronous connection-oriented (eSCO) links (or eSCO connections), or other logical transport channel links.

[0074] In some examples, the controller stack may implement Link Management Protocol (LMP) functionality, Low Energy Link Layer (LELL) functionality, or other supporting functions. The host stack may be implemented as part of the operating system or as an installable suite on top of the operating system. The host stack may be responsible for Logical Link Control and Adaptation Protocol (L2CAP) functionality, Bluetooth Network Encapsulation Protocol (BNEP) functionality, Service Discovery Protocol (SDP) functionality, or other functions. In some examples, the controller stack and host stack may communicate via a Host Controller Interface (HCI). In some other examples (e.g., for integrated devices such as Bluetooth headsets), the host stack and controller stack may run on the same microprocessor to reduce mass production costs. For such hostless systems, the HCI may be optional and may be implemented as an internal software interface.

[0075] One or more wireless devices can establish a non-cellular connection (such as a D2D communication link 135) between two Bluetooth-enabled devices (e.g., between two UEs 115) and provide communication or services (e.g., according to a Bluetooth profile). For example, the Bluetooth connection can be an eSCO connection for voice calls (e.g., which allows retransmission), an ACL connection for music streaming (e.g., A2DP), or another type of Bluetooth connection. For example, eSCO packets can be transmitted in predetermined time slots (e.g., six Bluetooth time slots each for eSCO). A regular interval between eSCO packets can be specified when the Bluetooth link is established. eSCO packets communicated with a specific slave device (e.g., a connected wireless device) can be acknowledged and can be retransmitted during a retransmission window if unacknowledged. Additionally or alternatively, an ACL connection (A2DP profile) can be used to stream audio between the UE 115 and the connected wireless device. In some cases, an ACL connection can occupy one, three, or five Bluetooth time slots used for data or voice. Other Bluetooth profiles supported by Bluetooth-enabled devices may include Bluetooth Low Energy (BLE) (e.g., providing reduced power consumption and cost while maintaining similar communication range), Human Interface Device Profile (HID) (e.g., providing a low-latency link with a low power threshold), or other Bluetooth profiles.

[0076] In some examples, Bluetooth-enabled wireless devices can be examples of battery-powered devices. Power optimization and battery life can be important for the use of battery-powered devices. For example, wireless devices can be examples of wearable devices within an IoT system, such as smartwatches. Some smartwatch batteries can support capacities from 400 mAH to 600 mAH for 3.7 volts (V). Optimizing or otherwise improving the use of battery resources in a smartwatch can enable it to allocate such battery resources to other activities, extend the smartwatch's average battery life, or both. For example, continuous modem activity at a smartwatch can consume its battery resources.

[0077] For example, a smartwatch (e.g., a wireless device, first UE 115) can connect to a smartphone (e.g., second UE 115) using Bluetooth or another non-cellular connection. Additionally, the smartwatch and smartphone can connect to a wireless network using a corresponding cellular connection (e.g., communication link 125). The smartwatch and smartphone (e.g., a mobile device accompanying the smartwatch) may be able to receive the same messages via a cellular connection (such as LTE communication link 125). For example, the wireless network may transmit a set of messages to both the smartwatch and the smartphone, which (e.g., in some cases, an average of 20 to 30 messages per day) includes promotional messages, data packets, banking information, service packages, shopping information, sports information, personal texts, or any combination of these or other messages. If both the smartwatch and the smartphone receive the same message (e.g., the same downlink message from the wireless network) and decode the message in parallel, the smartwatch, smartphone, or both may inefficiently consume power in redundant processing. In some cases, decoding the message at the smartwatch may consume relatively more power than decoding the message at the smartphone. Avoiding such dual decoding on both the smartwatch and the smartphone can support battery saving on the smartwatch, the smartphone, or both.

[0078] If a smartwatch (e.g., UE 115) is operating in a connected mode with an accompanying mobile device (e.g., a smartphone, another UE 115), the smartwatch can support techniques for efficiently handling downlink messages. For example, if network entity 105 of a wireless network transmits a downlink message to the smartwatch via a cellular connection, the accompanying mobile device can receive the message and forward it to the smartwatch via a non-cellular connection. To improve processing overhead and save power, the smartwatch can avoid receiving downlink messages via a cellular connection. Based on operating in a connected mode, the smartwatch can alternatively receive messages from the accompanying mobile device via a non-cellular connection. The smartwatch can avoid redundant processing by receiving messages via a non-cellular connection with the accompanying mobile device and avoiding receiving or decoding the message via a cellular connection with the wireless network (e.g., with network entity 105), thereby improving processing overhead and battery life accordingly.

[0079] Figure 2 An example of a wireless communication system 200 supporting the handling of downlink messages at a connected device according to one or more aspects of this disclosure is shown. The wireless communication system 200 may be as described in reference... Figure 1 An example of the described wireless communication system 100. Wireless communication system 200 may include network entity 105-a, which may be as described in reference... Figure 1Examples of network entity 105 described herein (e.g., CU, DU, RU, core network entity, or any combination of these network devices or other network devices). Network entity 105-a may provide network coverage for coverage area 110-a. Network entity 105-a may be provided via downlink channel 210, uplink channel 215, or both, and may be as described in reference. Figure 1 The described UE 115 example communicates with UE 115-a, wireless device 205, or both. For example, wireless device 205 may be an example of a wearable device (e.g., a smartwatch), a connected device, or any other device that supports non-cellular connection 220 with UE 115-a. Wireless communication system 200 may support techniques for wireless device 205 to efficiently receive messages 235 from the wireless network when wireless device 205 operates in a connection mode with UE 115-a.

[0080] Network entity 105-a may communicate with UE 115-a, wireless device 205 (e.g., another UE 115 or other wireless device), or both. For example, network entity 105-a may transmit signals to UE 115-a, wireless device 205, or both via downlink channel 210. Additionally or alternatively, network entity 105-a may receive signals from UE 115-a, wireless device 205, or both via uplink channel 215. In some examples, network entity 105-a may be an example or component of a base station or other network device that provides cellular network connectivity to UE 115-a, wireless device 205, or both. Network entity 105-a, UE 115-a, or both may establish a cellular connection 225-a between network entity 105-a and UE 115-a. Similarly, network entity 105-a, wireless device 205, or both can establish a cellular connection 225-b between network entity 105-a and wireless device 205. Therefore, both UE 115-a and wireless device 205 can communicate with the wireless network via the cellular connection.

[0081] In some cases, UE 115-a, wireless device 205, or both may additionally establish a non-cellular connection 220 between UE 115-a and wireless device 205. For example, wireless device 205 may be an example of a smartwatch, and UE 115-a may be an example of a smartphone. Wireless device 205 (e.g., a smartwatch) may pair with UE 115-a (e.g., a smartphone) using Bluetooth connectivity or other non-cellular connections 220. Such non-cellular connections 220 may support continuous connectivity between wireless device 205 and UE 115-a. When the non-cellular connection 220 between wireless device 205 and UE 115-a is active, wireless device 205 may be in a connected mode with UE 115-a.

[0082] Non-cellular connection 220 can support a degree of redundancy with cellular connection 225-b of wireless device 205. For example, if network entity 105-a sends or otherwise transmits message 235 via downlink channel 210, wireless device 205 can support receiving message 235 using cellular connection 225-b. However, additionally, UE 115-a can receive message 235 using cellular connection 225-a and can forward message 235 to wireless device 205 using non-cellular connection 220 (e.g., Bluetooth connection) based on one or more connection mode services. Therefore, the same message 235 carrying the same information can be provided to wireless device 205 via both network and UE connection (e.g., both cellular connection 225-b and non-cellular connection 220).

[0083] To improve processing overhead and battery life at wireless device 205, wireless device 205 can efficiently handle such redundant message transmission and reception when operating in connected mode (e.g., when paired with UE 115-a via non-cellular connection 220 or otherwise connected). For example, wireless device 205 can avoid decoding both message 235 transmitted via cellular connection 225-b and message 235 transmitted via non-cellular connection 220 (e.g., the same message 235) (e.g., in parallel). Additionally or alternatively, wireless device 205 can avoid receiving both message 235 transmitted via cellular connection 225-b and message 235 transmitted via non-cellular connection 220. By avoiding performing one or more of these processes, wireless device 205 can save processing resources and battery life.

[0084] UE 115-a can receive one or more messages from the wireless network. UE 115-a can determine which messages are forwarded to wireless device 205 via non-cellular connection 220. In some examples, message 235 may include an identifier indicating that message 235 will be delivered to wireless device 205. In some cases, this identifier may be an example of a device identifier or a UE identifier for wireless device 205. UE 115-a can determine whether to forward message 235 to wireless device 205 based on the identifier included in the message indicating wireless device 205.

[0085] UE 115-a can transmit the same message as the one transmitted from the wireless network to wireless device 205 via cellular connection 225-b via non-cellular connection 220. In some cases, wireless device 205 can receive messages from UE 115-a via non-cellular connection 220 based on wireless device 205 supporting a continuous Bluetooth pairing connection with UE 115-a (e.g., an accompanying mobile phone). Therefore, when operating in connected mode, wireless device 205 can receive messages initially transmitted from the wireless network to wireless device 205 from UE 115-a without significant delay (e.g., within a threshold time window). When operating in connected mode, wireless device 205 can use non-cellular connection 220 (e.g., Bluetooth connection) to receive messages from UE 115-a and can avoid using cellular connection 225-b to receive messages (e.g., the same message) from network entity 105-a or to decode that message.

[0086] For example, wireless device 205 can operate in sleep mode when in idle mode. Operating in sleep mode conserves processing resources and battery life compared to active or awake states. If the wireless network has information to transmit to wireless device 205, network entity 105-a can send or otherwise transmit a wake-up signal 230. Wake-up signal 230 can indicate that message 235 is available to wireless device 205 via cellular connection 225-b. Wireless device 205 can detect the wake-up signal (e.g., using a wake-up radio, low-power radio, or other receiver). In some examples, based on wireless device 205 operating in a connection mode with UE 115-a, wireless device 205 may avoid waking up in response to wake-up signal 230 to receive message 235 via cellular connection 225-b. In some other examples, wireless device 205 may wake up in response to wake-up signal 230 but may avoid monitoring message 235. In still other examples, wireless device 205 may wake up in response to wake-up signal 230 and may receive the corresponding message 235. However, wireless device 205 may avoid decoding message 235 by operating in connected mode.

[0087] Wireless device 205 may alternatively receive message 235 from UE 115-a via non-cellular connection 220. In some examples, wireless device 205 may wake up in response to wake-up signal 230 and receive message 235 from UE 115-a. In some cases, UE 115-a may receive message 235 from the network and may send message 235 to wireless device 205 via the next available resource. In some other cases, UE 115-a may send message 235 to wireless device 205 at the next paging cycle timing. For example, non-cellular connection 220 may support Bluetooth paging cycles in which paging messages can be transmitted via Bluetooth connection within intervals defined by the cycle length. UE 115-a may transmit one or more messages including message 235 to wireless device 205 via resources at timings defined by the paging cycle. Wireless device 205 can save power and processing resources by waking up and receiving one or more messages from UE 115-a via non-cellular connection 220 within intervals defined by the paging cycle. Wireless device 205 (e.g., modem of wireless device 205) may otherwise operate in sleep mode to save power.

[0088] In some examples, UE 115-a may forward message 235 as an encoded message to wireless device 205. Wireless device 205 may receive the encoded message 235 and decode it to determine the message content. In some other examples, UE 115-a may forward message 235 as a decoded message to wireless device 205. For example, UE 115-a may receive message 235 and decode it. As an example of a secure connection between UE 115-a and wireless device 205 based on non-cellular connection 220, UE 115-a may send the decoded message 235 to wireless device 205. Wireless device 205 may receive the decoded message 235 and determine the message content without performing further decoding. Wireless device 205 can save battery resources and improve processing overhead by avoiding (e.g., disabling) decoding of message 235 at wireless device 205. For example, UE 115-a can perform the decoding process and use non-cellular connection 220 to provide the already decoded message 235 to radio device 205, instead of performing double decoding of the same message 235 at both UE 115-a and radio device 205. Therefore, when radio device 205 operates in connected mode, it can use non-cellular connection 220 to receive downlink messages and determine message content.

[0089] Figure 3 An example flowchart illustrating a method 300 for processing downlink messages at a connected device, according to one or more aspects of this disclosure, is shown. Wireless communication systems (such as reference 1) Figure 1 and Figure 2The described wireless communication system 100 or wireless communication system 200 may support method 300. For example, UE 115 (such as reference) Figure 2 The described UE 115-a) can perform one or more operations of method 300. Additionally or alternatively, a wireless device (e.g., a connecting device, a wearable device, or UE 115) (such as reference 115) may also perform these operations. Figure 2 The described wireless device 205 can perform one or more operations of method 300.

[0090] At 305, UE 115 can be attached to a wireless network. For example, UE 115 can establish a wireless connection with the wireless network via network entity 105, such as a cellular connection (e.g., an LTE connection, an NR connection). Additionally, UE 115 can be paired with a wireless device (such as a smartwatch). UE 115 can pair with the wireless device by establishing a non-cellular connection (such as a Bluetooth connection).

[0091] At 310, UE 115 can determine whether a downlink message has been detected from the wireless network. For example, UE 115 can monitor one or more messages from network entity 105. If UE 115 is operating in discontinuous reception (DRX) mode, UE 115 can wake up from an idle mode (e.g., sleep mode or other relatively low-power mode) according to the DRX cycle to monitor downlink messages. If UE 115 fails to detect a downlink message, UE 115 can re-enter idle mode at 330. Alternatively, if UE 115 detects a downlink message, UE 115 can receive the downlink message from the wireless network (e.g., from network entity 105) at 315.

[0092] At 320, UE 115 may determine whether it is paired with a radio device. Additionally, UE 115 may determine whether a received downlink message indicates a radio device. For example, the downlink message may indicate the radio device's device identifier as the target destination (e.g., intended destination) of the downlink message. If UE 115 is not paired with a radio device, or if the downlink message does not indicate a radio device, UE 115 may re-enter idle mode at 330. Alternatively, if UE 115 is paired with a radio device, the downlink message indicates a radio device, or both, at 325, UE 115 may send (e.g., forward) the downlink message to the paired radio device via a non-cellular connection. UE 115 may re-enter idle mode at 330 based on forwarding the message to the radio device or based on receiving confirmation that the radio device has successfully received the message via a non-cellular connection. For example, in some cases, the radio device may provide feedback information about the message, allowing UE 115 to retransmit the message via a non-cellular connection if the radio device fails to receive it successfully. In some examples, if the wireless device fails to successfully receive messages from UE 115 a threshold number of times (e.g., one failure or multiple failures), the wireless device may receive messages from the wireless network (e.g., via a cellular connection) or decode such messages. In some examples, the wireless device may additionally or alternatively enter idle mode at 330 based on successfully receiving messages from UE 115 via a non-cellular connection.

[0093] Figure 4 An example of a process flow 400 supporting the processing of downlink messages at a connected device according to one or more aspects of this disclosure is shown. In some examples, process flow 400 may be provided by, as referenced Figure 1 and Figure 2 The wireless communication system 100 or wireless communication system 200 described herein are implemented in various aspects. For example, process flow 400 may include network entity 105-b (e.g., CU, DU, RU, core network entity or any combination thereof), UE 115-b, and wireless device 405, which may be as referenced herein. Figures 1 to 3 Examples of the network entity 105, UE 115, and wireless device (e.g., a connectivity device, a wearable device, or UE 115) described herein. In the following description of process flow 400, operations between devices may be performed in different order or at different times. Some operations may be excluded from process flow 400, or other operations may be added. Although network entity 105-b, UE 115-b, and wireless device 405 are shown as performing operations of process flow 400, some aspects of some operations may be performed by one or more other devices or entities.

[0094] At 410, UE 115-b may establish a first cellular connection with the wireless network, for example, via network entity 105-b. Additionally, wireless device 405 may establish a second cellular connection with the wireless network, for example, via network entity 105-b. At 415, wireless device 405, UE 115-b, or both may establish a non-cellular connection between wireless device 405 and UE 115-b. The non-cellular connection may support the operation of wireless device 405 in a connection mode (e.g., pairing mode) with UE 115-b. The non-cellular connection may be an example of a Bluetooth connection. In some examples, wireless device 405 may be an example of a smartwatch or other wearable device paired with UE 115-b, and the UE may be an example of a smartphone or other accompanying device.

[0095] At 420, the wireless network can determine that a message is awaiting transmission to wireless device 405. Network entity 105-b can transmit a wake-up signal indicating that the message is available via a cellular connection. For example, the wake-up signal can trigger one or more devices to wake up from a relatively low-power mode to monitor the message via a downlink channel. In some cases, the wake-up signal can indicate one or more resources for receiving the message via a downlink channel. Wireless device 405 can receive the wake-up signal via a second cellular connection (e.g., from network entity 105-b). In some cases, UE 115-b can additionally receive the wake-up signal via a first cellular connection.

[0096] At 425, network entity 105-b may transmit a message via a downlink channel in one or more resources indicated by a wake-up signal. UE 115-b may receive the message via a first cellular connection with network entity 105-b. This message may be associated with radio device 405. For example, UE 115-b may determine that the message is associated with radio device 405 based on an indicator that the message includes radio device 405. However, in some examples, radio device 405 may avoid performing a wake-up procedure in response to a wake-up signal based on its operation in the connection mode with UE 115-b. In some such examples, radio device 405 may avoid receiving the message via a second cellular connection based on avoiding performing a wake-up procedure. In some other examples, radio device 405 may additionally receive the message via a second cellular connection, but radio device 405 may avoid decoding the message received via the cellular connection based on its operation in the connection mode with UE 115-b.

[0097] At 430, UE 115-b may decode a message received from the wireless network via the first cellular connection. At 435, wireless device 405 may monitor the message via a non-cellular connection according to the paging cycle. At 440, UE 115-b may send the message via a non-cellular connection based on the association of the message with wireless device 405 and the operation of wireless device 405 in the connection mode with UE 115-b. In some cases, UE 115-b may send the message via a non-cellular connection according to the paging cycle. Wireless device 405 may receive the message via a non-cellular connection based on the operation of wireless device 405 in the connection mode with UE 115-b. In some examples, UE 115-b may send the message as a decoded message, and wireless device 405 may avoid decoding the message based on the fact that the message received via the non-cellular connection has already been decoded by UE 115-b. Therefore, wireless device 405 can receive messages via a non-cellular connection with UE 115-b, instead of receiving messages from network entity 105-b via a second cellular connection, thereby avoiding redundant decoding of the same messages at wireless device 405.

[0098] Figure 5 A block diagram 500 illustrates a device 505 supporting the processing of downlink messages at a connected device according to one or more aspects of this disclosure. Device 505 may be an example of a UE 115 or various aspects of a wireless device as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0099] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to downlink messages at the processing connection device). The information may be transmitted to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0100] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to handling downlink messages at the connected device). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0101] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of disposing of downlink messages at a connected device as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0102] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0103] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code (e.g., implemented as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0104] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated in combination with the receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0105] According to the examples disclosed herein, the communication manager 520 may support wireless communication. For example, the communication manager 520 may be capable of, configured to, or operable to support components for establishing a non-cellular connection between a wireless device (e.g., device 505) and a UE, the non-cellular connection supporting the operation of the wireless device in a connection mode with the UE. The communication manager 520 may be capable of, configured to, or operable to support components for receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection. The communication manager 520 may be capable of, configured to, or operable to support components for receiving such a message via a non-cellular connection based on the operation of the wireless device in a connection mode with the UE.

[0106] Additionally or alternatively, according to the examples disclosed herein, the communication manager 520 may support wireless communication. For example, the communication manager 520 may be capable of, configured to, or operable to support components for establishing a non-cellular connection between a UE (e.g., device 505) and a wireless device, the non-cellular connection supporting the operation of the wireless device in a connection mode with the UE. The communication manager 520 may be capable of, configured to, or operable to support components for receiving messages associated with a wireless device via a cellular connection with a network entity. The communication manager 520 may be capable of, configured to, or operable to support components for sending a message via a non-cellular connection to a wireless device based on the association of the message with the wireless device and the operation of the wireless device in a connection mode with the UE.

[0107] By including or configuring a communication manager 520 according to examples as described herein, device 505 (e.g., at least one processor that controls or otherwise couples to receiver 510, transmitter 515, communication manager 520, or a combination thereof) may support techniques for reducing processing overhead, reducing power consumption, or both for device 505 (e.g., a wireless device operating in a connected mode with UE 115). For example, device 505 may receive messages via a non-cellular connection to UE 115 and may avoid receiving the same messages via a cellular connection, avoid decoding the same messages via a cellular connection, or both, thereby effectively reducing processing overhead and power consumption at device 505. In some examples, messages received via a non-cellular connection may have already been decoded at UE 115, further reducing the processing associated with decoding operations at device 505.

[0108] Figure 6 A block diagram 600 illustrates a device 605 supporting the processing of downlink messages at a connected device according to one or more aspects of this disclosure. Device 605 may be an example of aspects of a device 505 as described herein, a UE 115, a wireless device, or any combination thereof. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0109] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to downlink messages at the processing connection device). The information may be transmitted to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

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

[0111] Device 605 or its various components may be examples of parts for performing various aspects of disposing of downlink messages at a connected device as described herein. For example, communication manager 620 may include connection component 625, wake-up signal component 630, connection message component 635, downlink message component 640, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0112] According to the examples disclosed herein, the communication manager 620 may support wireless communication. The connectivity component 625 is capable of, configured to, or operable to support components for establishing a non-cellular connection between a wireless device (e.g., device 605) and a UE, the non-cellular connection supporting the operation of the wireless device in a connection mode with the UE. The wake-up signal component 630 is capable of, configured to, or operable to support components for receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection. The connectivity message component 635 is capable of, configured to, or operable to support components for receiving the message via a non-cellular connection based on the operation of the wireless device in a connection mode with the UE.

[0113] Additionally or alternatively, according to the examples disclosed herein, the communication manager 620 may support wireless communication. The connectivity component 625 is capable of, configured to, or operable to support components for establishing a non-cellular connection between the UE (e.g., device 605) and a wireless device, which supports the operation of the wireless device in a connection mode with the UE. The downlink messaging component 640 is capable of, configured to, or operable to support components for receiving messages associated with a wireless device via a cellular connection with a network entity. The connectivity messaging component 635 is capable of, configured to, or operable to support components for sending a message via a non-cellular connection to the wireless device based on the association of the message with the wireless device and the operation of the wireless device in a connection mode with the UE.

[0114] Figure 7A block diagram 700 illustrates a communication manager 720 supporting the handling of downlink messages at a connected device according to one or more aspects of this disclosure. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of handling downlink messages at a connected device as described herein. For example, the communication manager 720 may include a connection component 725, a wake-up signal component 730, a connection message component 735, a downlink message component 740, a monitoring component 745, a decoder 750, a forwarding component 755, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0115] According to the examples disclosed herein, the communication manager 720 can support wireless communication at the wireless device. The connectivity component 725 is capable of, configured to, or operable to support components for establishing a non-cellular connection between the wireless device and the UE, which supports the operation of the wireless device in a connection mode with the UE. The wake-up signal component 730 is capable of, configured to, or operable to support components for receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection. The connectivity message component 735 is capable of, configured to, or operable to support components for receiving the message via a non-cellular connection based on the operation of the wireless device in a connection mode with the UE.

[0116] In some examples, the monitoring component 745 is capable of, configured to, or operable to support components for monitoring messages received via a noncellular connection based on the paging cycle, wherein the messages are received via the noncellular connection based on the monitoring.

[0117] In some examples, the wake-up signal component 730 is capable of, configured to, or operable to support components for avoiding the execution of a wake-up process in response to a wake-up signal based on the operation of the wireless device in a connection mode with the UE.

[0118] In some examples, the downlink message component 740 is capable of, configured to, or operable to support components for additionally receiving the message via the cellular connection. In some examples, the decoder 750 is capable of, configured to, or operable to support components for avoiding decoding of the message additionally received via the cellular connection based on the operation of the radio device in the connection mode with the UE.

[0119] In some examples, decoder 750 is capable of, configured to, or operable to support components for avoiding decoding of the message received via a non-cellular connection based on the message being decoded at the UE.

[0120] In some examples, non-cellular connectivity includes Bluetooth connectivity. In some examples, the wireless device includes a smartwatch or wearable device. In some examples, the smartwatch or wearable device is paired with the UE.

[0121] Additionally or alternatively, according to the examples disclosed herein, the communication manager 720 may support wireless communication at the UE. In some examples, the connectivity component 725 is capable of, configured to, or operable to support components for establishing a non-cellular connection between the UE and a wireless device that supports the operation of the wireless device in a connection mode with the UE. The downlink messaging component 740 is capable of, configured to, or operable to support components for receiving messages associated with a wireless device via a cellular connection with a network entity. In some examples, the connectivity messaging component 735 is capable of, configured to, or operable to support components for sending a message via a non-cellular connection to the wireless device based on the association of the message with the wireless device and the operation of the wireless device in a connection mode with the UE.

[0122] In some examples, in order to support sending the message over a non-cellular connection, the connection message component 735 can be configured or operable to support components for sending the message over a non-cellular connection according to the paging cycle.

[0123] In some examples, decoder 750 is capable of, configured to, or operable to support components for decoding the message received via a cellular connection. In some examples, to support sending the message via a non-cellular connection, connection message component 735 is capable of, configured to, or operable to support components for sending the decoded message to a wireless device via a non-cellular connection.

[0124] In some examples, the forwarding component 755 is capable of, configured to, or operable to support the determination of which part of the message is forwarded to the wireless device based on the message including an indicator of the wireless device, wherein the message is sent via a non-cellular connection based on the determination.

[0125] In some examples, non-cellular connectivity includes Bluetooth connectivity. In some examples, the wireless device includes a smartwatch or wearable device. In some examples, the smartwatch or wearable device is paired with the UE.

[0126] Figure 8A diagram of a system 800 including device 805 supporting the handling of downlink messages at a connected device, according to one or more aspects of this disclosure. Device 805 may be an example of a component of device 505, device 605, UE 115, wireless device, or any combination thereof as described herein, or may include such components. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicable ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

[0127] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0128] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired or wireless link as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0129] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable (e.g., processor-executable) code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 830 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0130] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks that support the disposal of downlink messages at a connected device). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein.

[0131] According to the examples disclosed herein, the communication manager 820 may support wireless communication at a wireless device. For example, the communication manager 820 may be capable of, configured to, or operable to support components for establishing a non-cellular connection between a wireless device (e.g., device 805) and a UE, the non-cellular connection supporting the operation of the wireless device in a connection mode with the UE. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection. The communication manager 820 may be capable of, configured to, or operable to support components for receiving such a message via a non-cellular connection based on the operation of the wireless device in a connection mode with the UE.

[0132] Additionally or alternatively, according to the examples disclosed herein, the communication manager 820 may support wireless communication at the UE. For example, the communication manager 820 may be capable of, configured to, or operable to support components for establishing a non-cellular connection between the UE (e.g., device 805) and a wireless device, the non-cellular connection supporting the operation of the wireless device in a connection mode with the UE. The communication manager 820 may be capable of, configured to, or operable to support components for receiving messages associated with a wireless device via a cellular connection with a network entity. The communication manager 820 may be capable of, configured to, or operable to support components for sending a message via a non-cellular connection to the wireless device based on the association of the message with the wireless device and the operation of the wireless device in a connection mode with the UE.

[0133] By including or configuring a communication manager 820 according to an example as described herein, device 805 may support techniques for reducing power consumption, extending battery life, improving processing power utilization, or any combination thereof. For example, device 805 (e.g., a wireless device operating in a connection mode with UE 115) may avoid receiving downlink messages via a cellular connection, avoid decoding downlink messages received via a cellular connection, or both, to reduce power consumption and processing resources associated with downlink message reception. Such techniques may extend the battery life of device 805 (e.g., a smartwatch or other wireless device).

[0134] In some examples, the communication manager 820 may be configured to use or otherwise coordinate with the transceiver 815, one or more antennas 825, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or performed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of disposing of downlink messages at a connected device as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0135] Figure 9 A flowchart illustrating a method 900 for processing downlink messages at a connected device, according to various aspects of this disclosure, is shown. Operation of method 900 may be implemented by a wireless device (e.g., UE 115) or its components as described herein. For example, operation of method 900 may be implemented by, as referenced... Figures 1 to 8The described wireless device performs the functions described. In some examples, the wireless device may execute a set of instructions to control the functional elements of the wireless device to perform the described functions. Additionally or alternatively, the wireless device may use dedicated hardware to perform aspects of the described functions.

[0136] At 905, the method may include establishing a non-cellular connection between a wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connection mode with the UE. Operation at 905 may be performed according to examples as disclosed herein. In some examples, aspects of operation at 905 may be provided by reference to [reference needed]. Figure 7 The described connection component 725 is executed.

[0137] At 910, the method may include receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection. Operation of 910 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 910 may be provided by reference to [reference needed]. Figure 7 The described wake-up signal component 730 is executed.

[0138] At 915, the method may include receiving the message via the non-cellular connection based on the operation of the wireless device in the connection mode with the UE. The operation of 915 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 915 may be provided by reference to [reference needed]. Figure 7 The described connection message component 735 is executed.

[0139] Figure 10 A flowchart illustrating a method 1000 for processing downlink messages at a connected device, according to various aspects of this disclosure, is shown. Operation of method 1000 may be implemented by a wireless device (e.g., UE 115) or its components as described herein. For example, operation of method 1000 may be implemented by, as referenced... Figures 1 to 8 The described wireless device performs the functions described. In some examples, the wireless device may execute a set of instructions to control the functional elements of the wireless device to perform the described functions. Additionally or alternatively, the wireless device may use dedicated hardware to perform aspects of the described functions.

[0140] At 1005, the method may include establishing a non-cellular connection between a wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connection mode with the UE. The operation of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1005 may be provided by reference to [reference needed]. Figure 7 The described connection component 725 is executed.

[0141] At 1010, the method may include receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection. The operation of 1010 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1010 may be provided by reference to [reference needed]. Figure 7 The described wake-up signal component 730 is executed.

[0142] At 1015, the method may include avoiding the execution of a wake-up process in response to the wake-up signal based on the operation of the wireless device in the connection mode with the UE. The operation of 1015 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1015 may be provided by reference to [reference needed]. Figure 7 The described wake-up signal component 730 is executed.

[0143] At 1020, the method may include monitoring the message via the non-cellular connection according to the paging cycle. The operation of 1020 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1020 may be as described in the references... Figure 7 The monitoring component 745 described is executed.

[0144] At 1025, the method may include the operation of the wireless device in the connection mode with the UE and receiving the message via the non-cellular connection based on the monitoring. The operation of 1025 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1025 may be as described in references... Figure 7 The described connection message component 735 is executed.

[0145] Figure 11 A flowchart illustrating a method 1100 for processing downlink messages at a connected device, according to various aspects of this disclosure, is shown. Operation of method 1100 may be implemented by a wireless device (e.g., UE 115) or its components as described herein. For example, operation of method 1100 may be implemented by, as referenced... Figures 1 to 8 The described wireless device performs the functions described. In some examples, the wireless device may execute a set of instructions to control the functional elements of the wireless device to perform the described functions. Additionally or alternatively, the wireless device may use dedicated hardware to perform aspects of the described functions.

[0146] At 1105, the method may include establishing a non-cellular connection between a wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connection mode with the UE. Operation of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1105 may be provided by reference to [reference needed]. Figure 7 The described connection component 725 is executed.

[0147] At 1110, the method may include receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection. The operation of 1110 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1110 may be as described in the references... Figure 7 The described wake-up signal component 730 is executed.

[0148] At 1115, the method may include receiving the message via the cellular connection. The operation of 1115 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1115 may be as described in the references... Figure 7 The downlink messaging component 740 described is executed.

[0149] At 1120, the method may include avoiding decoding of the message received via the cellular connection based on the operation of the wireless device in the connection mode with the UE. The operation of 1120 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1120 may be provided by reference to [reference needed]. Figure 7 The described decoder 750 is executed.

[0150] At 1125, the method may include receiving the message via the non-cellular connection based on the operation of the wireless device in the connection mode with the UE. The operation of 1125 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1125 may be as described in references... Figure 7 The described connection message component 735 is executed.

[0151] Figure 12 A flowchart illustrating a method 1200 for processing downlink messages at a connected device, according to various aspects of this disclosure, is shown. Operation of method 1200 can be implemented by a UE or its components as described herein. For example, operation of method 1200 can be performed by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE can 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.

[0152] At 1205, the method may include establishing a non-cellular connection between the UE and a wireless device, the non-cellular connection supporting operation of the wireless device in a connection mode with the UE. Operation of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1205 may be provided by reference to [reference needed]. Figure 7 The described connection component 725 is executed.

[0153] At 1210, the method may include receiving a message associated with the wireless device via a cellular connection to a network entity. Operation of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1210 may be provided by reference to [reference needed]. Figure 7 The downlink messaging component 740 described is executed.

[0154] At 1215, the method may include sending the message via the non-cellular connection based on the association of the message with the wireless device and the operation of the wireless device in the connection mode with the UE. The operation of 1215 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1215 may be as described in references... Figure 7 The described connection message component 735 is executed.

[0155] Figure 13 A flowchart illustrating a method 1300 for processing downlink messages at a connected device, according to various aspects of this disclosure, is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein performs the following: In some examples, the UE can 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.

[0156] At 1305, the method may include establishing a non-cellular connection between the UE and a wireless device, the non-cellular connection supporting operation of the wireless device in a connection mode with the UE. Operation of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1305 may be provided by reference to [reference needed]. Figure 7 The described connection component 725 is executed.

[0157] At 1310, the method may include receiving a message associated with the wireless device via a cellular connection to a network entity. Operation of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1310 may be derived from references... Figure 7 The downlink messaging component 740 described is executed.

[0158] At 1315, the method may include decoding the message received via the cellular connection. The operation of 1315 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 7 The described decoder 750 is executed.

[0159] At 1320, the method may include sending the decoded message to the wireless device via the non-cellular connection based on the association of the message with the wireless device and the operation of the wireless device in the connection mode with the UE. The operation of 1320 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1320 may be provided by reference to [reference needed]. Figure 7 The described connection message component 735 is executed.

[0160] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a wireless device, the method comprising: establishing a non-cellular connection between the wireless device and a UE, the non-cellular connection supporting operation of the wireless device in a connection mode with the UE; receiving a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection; and receiving the message via the non-cellular connection based at least in part on the operation of the wireless device in the connection mode with the UE.

[0161] Aspect 2: According to the method of aspect 1, the method further includes: monitoring the message via the non-cellular connection according to a paging cycle, wherein the message is received via the non-cellular connection based at least in part on the monitoring.

[0162] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: avoiding the execution of a wake-up process in response to the wake-up signal based at least in part on the operation of the wireless device in the connection mode with the UE.

[0163] Aspect 4: The method according to any one of Aspects 1 to 2, the method further comprising: additionally receiving the message via the cellular connection; and avoiding decoding the message additionally received via the cellular connection based at least in part on the operation of the wireless device in the connection mode with the UE.

[0164] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: avoiding decoding of the message received via the non-cellular connection based at least in part on the message being decoded at the UE.

[0165] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the non-cellular connection includes a Bluetooth connection.

[0166] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the wireless device includes a smartwatch or wearable device, wherein the smartwatch or wearable device is paired with the UE.

[0167] Aspect 8: A method for wireless communication by a UE, the method comprising: establishing a non-cellular connection between the UE and a wireless device, the non-cellular connection supporting operation of the wireless device in a connection mode with the UE; receiving a message associated with the wireless device via a cellular connection with a network entity; and transmitting the message to the wireless device via the non-cellular connection, at least in part based on the association of the message with the wireless device and the operation of the wireless device in the connection mode with the UE.

[0168] Aspect 9: According to the method of aspect 8, sending the message via the non-cellular connection includes: sending the message via the non-cellular connection according to a paging cycle.

[0169] Aspect 10: The method according to any one of Aspects 8 to 9, the method further comprising: decoding the message received via the cellular connection, wherein sending the message via the non-cellular connection comprises: sending the decoded message via the non-cellular connection to the wireless device.

[0170] Aspect 11: The method according to any one of Aspects 8 to 10, the method further comprising: determining, at least in part, to forward the message to the wireless device based on the message including an indicator of the wireless device, wherein the message is transmitted via the non-cellular connection at least in part based on the determination.

[0171] Aspect 12: The method according to any one of Aspects 8 to 11, wherein the non-cellular connection includes a Bluetooth connection.

[0172] Aspect 13: The method according to any one of Aspects 8 to 12, wherein the wireless device includes a smartwatch or wearable device, wherein the smartwatch or wearable device is paired with the UE.

[0173] Aspect 14: A wireless device comprising: 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, thereby enabling the wireless device to perform the method according to any one of Aspects 1 to 7.

[0174] Aspect 15: A wireless device for wireless communication, the wireless device comprising at least one component for performing the method according to any one of aspects 1 to 7.

[0175] Aspect 16: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of Aspects 1 to 7.

[0176] Aspect 17: A UE comprising: 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, thereby enabling the UE to perform a method according to any one of Aspects 8 to 13.

[0177] Aspect 18: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 8 to 13.

[0178] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of Aspects 8 to 13.

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

[0180] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative 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 techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0182] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A 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 cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0183] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality can 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 functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0184] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose 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, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. 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 coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0185] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, 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" could be based on both condition A and condition B without departing from the scope of this 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".

[0186] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0187] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0188] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0189] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A wireless device, the wireless device comprising: One or more memories, wherein the one or more memories 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, thereby enabling the wireless device to: A non-cellular connection is established between the wireless device and the user equipment (UE), the non-cellular connection supporting the operation of the wireless device in a connection mode with the UE; Receive a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection; as well as The message is received via the non-cellular connection based at least in part on the operation of the wireless device in the connection mode with the UE.

2. The wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code, thereby causing the wireless device to: The messages are monitored via the non-cellular connection according to the paging cycle, wherein the messages are received via the non-cellular connection based at least in part on the monitoring.

3. The wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code, thereby enabling the wireless device to: The wake-up process is avoided in response to the wake-up signal, at least in part, based on the operation of the wireless device in the connection mode with the UE.

4. The wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code, thereby enabling the wireless device to: Additionally, the message is received via the cellular connection; and Decoding of messages additionally received via the cellular connection is avoided, at least in part, based on the operation of the wireless device in the connection mode with the UE.

5. The wireless device of claim 1, wherein the one or more processors are individually or jointly further operable to execute the code, thereby causing the wireless device to: Decoding of the message received via the non-cellular connection is avoided, at least in part, based on the fact that the message is decoded at the UE.

6. The wireless device of claim 1, wherein the non-cellular connection includes a Bluetooth connection.

7. The wireless device of claim 1, wherein the wireless device includes a smartwatch or wearable device, wherein the smartwatch or wearable device is paired with the UE.

8. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the UE to: A non-cellular connection is established between the UE and the wireless device, the non-cellular connection supporting the operation of the wireless device in the connection mode with the UE; Messages are received via a cellular connection to a network entity, and these messages are associated with the wireless device. as well as The message is sent to the wireless device via the non-cellular connection, at least in part based on the association of the message with the wireless device and the operation of the wireless device in the connection mode with the UE.

9. The UE of claim 8, wherein, in order to transmit the message via the non-cellular connection, the one or more processors are capable of operating individually or jointly to execute the code, thereby causing the UE to: The message is sent via the non-cellular connection according to the paging cycle.

10. The UE of claim 8, wherein the one or more processors are individually or jointly further operable to execute the code, thereby causing the UE to: Decoding the message received via the cellular connection, wherein, in order to transmit the message via the non-cellular connection, the one or more processors can operate individually or jointly to execute the code, thereby enabling the UE to: The decoded message is sent to the wireless device via the non-cellular connection.

11. The UE of claim 8, wherein the one or more processors are individually or jointly further operable to execute the code, thereby causing the UE to: The decision to forward the message to the wireless device is based at least in part on the message including an indicator of the wireless device, wherein the message is sent via the non-cellular connection based at least in part on the decision.

12. The UE of claim 8, wherein the non-cellular connection includes a Bluetooth connection.

13. The UE of claim 8, wherein the wireless device includes a smartwatch or wearable device, wherein the smartwatch or wearable device is paired with the UE.

14. A method for wireless communication by a wireless device, the method comprising: A non-cellular connection is established between the wireless device and the user equipment (UE), the non-cellular connection supporting the operation of the wireless device in a connection mode with the UE; Receive a wake-up signal from a network entity via a cellular connection, the wake-up signal indicating that a message can be provided via the cellular connection; as well as The message is received via the non-cellular connection based at least in part on the operation of the wireless device in the connection mode with the UE.

15. The method of claim 14, further comprising: The messages are monitored via the non-cellular connection according to the paging cycle, wherein the messages are received via the non-cellular connection based at least in part on the monitoring.

16. The method of claim 14, further comprising: The wake-up process is avoided in response to the wake-up signal, at least in part, based on the operation of the wireless device in the connection mode with the UE.

17. The method of claim 14, further comprising: The message is additionally received via the cellular connection; as well as Decoding of messages additionally received via the cellular connection is avoided, at least in part, based on the operation of the wireless device in the connection mode with the UE.

18. The method of claim 14, further comprising: Decoding of the message received via the non-cellular connection is avoided, at least in part, based on the fact that the message is decoded at the UE.

19. The method of claim 14, wherein the non-cellular connection includes a Bluetooth connection.

20. The method of claim 14, wherein the wireless device comprises a smartwatch or wearable device, wherein the smartwatch or wearable device is paired with the UE.

Images