Communication transmitted via a user device

Abstract

The present disclosure relates to wireless communication, and more particularly, to connection establishment and configuration. In some aspects, a user equipment (UE) receives, from a connected device, an indication associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being relayed by the UE between the connected device and the network node. The UE is configured to relay one or more communications between the connected device and the network node, at least partially based on the indication. Numerous other aspects are described.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This patent application claims priority to U.S. Patent Application No. 17 / 663,099, entitled "COMMUNICATIONS CARRIED VIA A USER EQUIPMENT", filed on May 12, 2022, which is expressly incorporated herein by reference.

[0002] Aspects of the present disclosure generally relate to wireless communications and to techniques and apparatus for communications carried via a user equipment.

Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system can use a multiple access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP (registered trademark)).

[0004] A wireless network can include one or more network nodes that support communication for wireless communication devices such as user equipment (UE) or a plurality of UEs. The UE may communicate with the network node via downlink communication and uplink communication. "Downlink" (or "downlink, DL") refers to the communication link from the network node to the UE, and "uplink" (or "uplink, UL") refers to the communication link from the UE to the network node. Some wireless networks can support device-to-device communication via local links (e.g., among other examples, sidelink (SL), wireless local area network (WLAN) link, and / or wireless personal area network (WPAN) link).

[0005] These multi-connectivity techniques are adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the municipal, national, regional, or global levels. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by the 3GPP. NR is designed to better support mobile broadband internet access by improving spectral efficiency, reducing costs, enhancing services, utilizing new spectrum, using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation, and by integrating better with other open standards.

Summary of the Invention

[0006] Some aspects described herein relate to a method of wireless communication implemented by a user equipment (UE). The method may include receiving, from a connected device, an indication associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being transmitted by the UE between the connected device and the network node. The method may include configuring the UE to transmit one or more communications between the connected device and the network node, at least partially based on the indication.

[0007] Some aspects described herein relate to a method of wireless communication implemented by a device. The method may include transmitting, to a UE, one or more instructions associated with management of one or more communications between the device and a network node of a wireless network, the one or more communications being communicated by the UE between the device and the network node. The method may include configuring the device for one or more communications via the UE, at least partially based on the instructions.

[0008] Some aspects described herein relate to a method of wireless communication implemented by a UE. The method may include transmitting, across a network associated with a network node, a first indication of one or more first parameters of a communication link between the UE and an application server. The method may include receiving, across the network, a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication.

[0009] Some aspects described herein relate to a method of wireless communication implemented by a network node. The method may include receiving, across a network associated with the network node, a first indication of one or more first parameters of a communication link between the UE and an application server. The method may include transmitting, across the network, a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication.

[0010] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, from a connected device, an instruction associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being transmitted by the UE between the connected device and the network node. The one or more processors may be configured to configure the UE to transmit one or more communications between the connected device and the network node, at least partially based on the instruction.

[0011] Some aspects described herein relate to a device for wireless communication. The device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send, to a UE, an instruction associated with management of one or more communications between the device and a network node of a wireless network, the one or more communications being transmitted by the UE between the device and the network node. The one or more processors may be configured to configure the device for one or more communications via the UE, at least partially based on the instruction.

[0012] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send, across a network associated with a network node, a first instruction of one or more first parameters of a communication link between the UE and an application server. The one or more processors may be configured to receive, at least partially based on the first instruction, a second instruction of one or more second parameters for communicating across the network.

[0013] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a first indication of one or more first parameters of a communication link between a UE and an application server across a network associated with the network node. The one or more processors may be configured to transmit a second indication of one or more second parameters for communicating across the network, based at least in part on the first indication.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, from a connected device, an indication associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being communicated by the UE between the connected device and the network node. The set of instructions, when executed by one or more processors of the UE, may cause the UE to be configured to transmit one or more communications between the connected device and the network node, based at least in part on the indication.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a device. The set of instructions, when executed by one or more processors of the device, may cause the device to cause the UE to transmit an indication associated with management of one or more communications between the device and a network node of a wireless network, the one or more communications being communicated by the UE between the device and the network node. The set of instructions, when executed by one or more processors of the device, may cause the device to be configured to communicate one or more communications via the UE, based at least in part on the indication.

[0016] Some aspects described herein relate to a non - transitory computer - readable medium storing a set of instructions for wireless communication by one or more instructions when executed by one or more processors of a UE. The set of instructions, when executed by one or more processors of the UE, can cause one or more instructions to transmit a first indication of one or more first parameters of a communication link between the UE and an application server over a network associated with the network node when executed by the one or more processors. The set of instructions, when executed by one or more processors of the UE, can cause one or more instructions to receive a second indication of one or more second parameters for communicating over the network based at least in part on the first indication when executed by the one or more processors of the UE.

[0017] Some aspects described herein relate to a non - transitory computer - readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, can cause the network node to receive a first indication of one or more first parameters of a communication link between the UE and an application server over a network associated with the network node. The set of instructions, when executed by one or more processors of the network node, can cause the network node to transmit a second indication of one or more second parameters for communicating over the network based at least in part on the first indication.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a connected device, an indication associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being relayed by the apparatus between the connected device and the network node. The apparatus may include means for configuring the apparatus to transmit one or more communications between the connected device and the network node, based at least in part on the indication.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, an indication associated with management of one or more communications between the device and a network node of a wireless network, the one or more communications being relayed by the UE between the apparatus and the network node. The apparatus may include means for configuring the apparatus for one or more communications via the UE, based at least in part on the indication.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, across a network associated with a network node, a first indication of one or more first parameters of a communication link between the apparatus UE and an application server. The apparatus may include means for receiving, across the network, a second indication of one or more second parameters for communicating across the network, based at least in part on the first indication.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, across a network associated with a network node, a first indication of one or more first parameters of a communication link between the UE and an application server. The apparatus may include means for transmitting, across the network, a second indication of one or more second parameters for communicating across the network, based at least in part on the first indication.

[0022] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, wireless communication devices, and / or processing systems substantially as described herein with reference to and as illustrated by the drawings and specification.

[0023] The foregoing has outlined broadly the features and technical advantages of examples according to the present disclosure in order that the following Detailed Description may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The nature of the concepts disclosed herein, both their organization and methods of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and explanation, and not as a definition of the limits of the claims.

[0024] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects may be implemented in many different configurations and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is contemplated that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and configurations.

[0025] So that the above-listed features of the present disclosure can be understood in detail, a more detailed description, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the attached drawings. It should be noted, however, that the attached drawings illustrate only certain exemplary embodiments of the present disclosure and therefore should not be considered as limiting the scope of the present disclosure, since the present description may admit of other equally effective embodiments. The same reference numbers in different drawings may identify the same or similar elements. [Brief description of the drawings]

[0026]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

[0027] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure is intended to encompass all aspects of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspects of the present disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects described herein. In addition, the scope of the present disclosure is intended to encompass such an apparatus or method that is practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of a claim.

[0028] Several aspects of a telecommunications system are now presented with reference to various apparatus and techniques that are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0029] Although aspects may be described herein using terminology commonly associated with 5G or New Radio (NR) radio access technology (RAT), aspects of the disclosure may be applicable to other RATs, such as 3G RATs, 4G RATs, and / or 5G and beyond RATs (e.g., 6G).

[0030] FIG. 1 illustrates an example of a wireless network 100. The wireless network 100 may be or include an element of a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other entities. The network node 110 is an example of a network node that communicates with the UE 120. As illustrated, the network node 110 may include one or more network nodes. For example, the network node 110 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0031] In some embodiments, the network node 110 is or includes a network node, such as a RU, that communicates with the UE 120 over a radio access link. In some embodiments, the network node 110 is or includes a network node, such as a DU, that communicates with other network nodes 110 over a fronthaul link or a midhaul link. In some embodiments, the network node 110 is or includes a network node, such as a CU, that communicates with other network nodes 110 over a midhaul link or with a core network over a backhaul link. In some embodiments, the network node 110 (such as an aggregated network node 110 or a disaggregated network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network nodes 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, or transmission reception points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some embodiments, the network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in the wireless network 100 through various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0032] In some embodiments, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network node 110 or a network node subsystem serving this coverage area depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 with associations with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In the embodiment shown in FIG. 1, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or multiple (e.g., three) cells. In some embodiments, a cell may not necessarily be stationary and a geographic area of ​​a cell may move according to the location of a network node 110 that is mobile (e.g., a mobile network node).

[0033] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a non-aggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, the term "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN Intelligent Controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to one device configured to perform one or more functions, such as functions described herein in connection with the network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, multiple different devices (which may be located at the same geographic location or different geographic locations) may each be configured to perform at least a portion of the functions or duplicate the implementation of at least a portion of the functions, and the term "base station" or "network node" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, more than one base station function may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.

[0034] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive a transmission of data from an upstream node (e.g., the network node 110 or the UE 120) and forward the transmission of data to a downstream node (e.g., the UE 120 or the network node 110). A relay station may be a UE 120 that can relay a transmission for another UE 120. In the embodiment shown in FIG. 1, a network node 110d (e.g., a relay network node) may communicate with the network node 110a (e.g., a macro network node) and the UE 120d to facilitate communication between the network node 110a (e.g., a macro network node) and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, or a repeater, among other examples.

[0035] The wireless network 100 may be a heterogeneous network including different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different susceptibility to interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5-40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1-2 watts).

[0036] The network controller 130 may couple to or communicate with a set of network nodes 110 and may provide coordination and control for these network nodes 110. The network controller 130 may communicate with the network nodes 110 via backhaul or midhaul communication links. The network nodes 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links. In some aspects, the network controller 130 may be or may include a CU or core network device.

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

[0038] Some UEs 120 may be considered as machine-type communication (MTC) UEs or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, or a location tag that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component or a memory component. In some embodiments, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

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

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

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided by frequency or wavelength into various classes, bands, or channels. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified with frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU).

[0042] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 or FR2 characteristics, and thus may effectively extend the features of FR1 or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is contained within the EHF band.

[0043] With these examples in mind, unless otherwise specified, the term "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specified, the term "millimeter wave" as used herein may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, or FR5, or may be within the EHF band. It is contemplated that the frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may receive instructions from a connected device associated with managing one or more communications between the connected device and a network node of a wireless network, the one or more communications being communicated by the UE between the connected device and the network node, and may configure the UE to communicate the one or more communications between the connected device and the network node based at least in part on the instructions. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0045] In some aspects, a device (e.g., a connected device and / or a UE) may include a communications manager 140. In some aspects, a device may be a type of UE and / or may be configured to communicate with a network node via a UE (e.g., an additional UE). As described in more detail elsewhere herein, the communications manager 140 may send instructions to the UE associated with managing one or more communications between the device and a network node of a wireless network, the communications manager 140 communicating by the UE between the device and the network node, and may configure the device for one or more communications via the UE based at least in part on the instructions. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0046] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may send a first indication of one or more first parameters of a communications link between the UE and an application server across a network associated with a network node and may receive a second indication of one or more second parameters for communicating across the network based at least in part on the first indication. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0047] In some aspects, the network node may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may receive a first indication of one or more first parameters of a communications link between a UE and an application server across a network associated with the network node and may transmit a second indication of one or more second parameters for communicating across the network based at least in part on the first indication. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0048] 2 illustrates an example network node 110 200 in communication with a UE 120 in a wireless network 100. The network node 110 may be equipped with a set of antennas 234a-234t, such as T antennas (T≧1). The UE 120 may be equipped with a set of antennas 252a-252r, such as R antennas (R≧1). The network node 110 of the example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0049] At the network node 110, the transmit processor 220 may receive data destined for the UE 120 (or set of UEs 120) from a data source 212. The transmit processor 220 may use one or more channel quality indicators (CQIs) received from the UE 120 to select one or more modulation and coding schemes (MCSs) for the UE 120. The network node 110 may process (e.g., code and modulate) data for the UE 120 using the MCS selected for the UE 120 and provide data symbols to the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or higher layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), denoted as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (denoted as MOD) of modem 232.Each modem 232 may process a respective output symbol stream using a respective modulator component (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, or upconvert) the output sample stream using a respective modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), depicted as antennas 234a through 234t.

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

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

[0052] One or more antennas (e.g., antennas 234a-t or antennas 252a-r) may include or be contained within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, or antenna array may include (in a single housing or multiple housings) one or more antenna elements, a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled to one or more transmitting or receiving components, such as one or more components of FIG.

[0053] On the uplink, in the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some embodiments, the modem 254 of the UE 120 may include a modulator and a demodulator. In some embodiments, the UE 120 includes a transceiver. The transceiver may include any combination of the antennas 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to implement aspects of any of the processes described herein.

[0054] In the network node 110, uplink signals from the UE 120 or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component, denoted as DEMOD, of the modem 232), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some embodiments, the modem 232 of the network node 110 may include a modulator and a demodulator. In some embodiments, the network node 110 includes a transceiver. The transceiver may include any combination of antennas 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the processes described herein.

[0055] In some aspects, the controller / processor 280 may be a component of a processing system. A processing system may generally be a system or set of machines or components that receives inputs, processes the inputs, and generates a set of outputs (e.g., that may be passed to other systems or components of the UE 120). For example, the processing system of the UE 120 may be a system that includes various other components or subcomponents of the UE 120.

[0056] The processing system of the UE 120 may interface with one or more other components of the UE 120, process information (e.g., input or signal) received from one or more other components, or output information to one or more other components. For example, a chip or modem of the UE 120 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some embodiments, the first interface may be an interface between the processing system of the chip or modem and a receiver, such that the UE 120 receives information or signal input, and the information may be passed to the processing system. In some embodiments, the second interface may be an interface between the processing system of the chip or modem and a transmitter, such that the UE 120 transmits information output from the chip or modem. One skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0057] In some aspects, the controller / processor 240 may be a component of a processing system. A processing system may generally be a system or set of machines or components that receives inputs, processes the inputs, and generates a set of outputs (which may, for example, be passed to other systems or components of the network node 110). For example, the processing system of the network node 110 may be a system that includes various other components or subcomponents of the network node 110.

[0058] The processing system of the network node 110 may interface with one or more other components of the network node 110, process information (e.g., input or signal) received from one or more other components, or output information to one or more other components. For example, a chip or modem of the network node 110 may include a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some embodiments, the first interface may be an interface between the processing system of the chip or modem and a receiver, such that the network node 110 receives information or signal input and the information may be passed to the processing system. In some embodiments, the second interface may be an interface between the processing system of the chip or modem and a transmitter, such that the network node 110 may transmit information output from the chip or modem. One skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0059] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or any other component of FIG. 2 may perform one or more techniques associated with communications conveyed via the UE, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component (or combination of components) of FIG. 2 may perform or direct the operation of, for example, process 900 of FIG. 9, process 1000 of FIG. 10, process 1100 of FIG. 11, and / or process 1200 of FIG. 12, or other processes described herein. The memory 242 and the memory 282 may store data and program codes for the network node 110 and the UE 120, respectively. In some embodiments, the memory 242 and the memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code or program code) for wireless communications. For example, the one or more instructions, when executed by one or more processors of the network node 110 or the UE 120 (e.g., directly or after compilation, translation, or interpretation), may cause the one or more processors, the UE 120, or the network node 110 to perform or direct operations, such as process 900 of Figure 9, process 1000 of Figure 10, process 1100 of Figure 11, process 1200 of Figure 12, or other processes described herein. In some embodiments, executing the instructions may include executing the instructions, converting the instructions, compiling the instructions, or interpreting the instructions.

[0060] In some aspects, the UE includes means for obtaining one or more communication parameters associated with one or more communications to be transmitted by the UE and / or means for transmitting the one or more communications based at least in part on a congestion control algorithm selected from a set of candidate congestion control algorithms, the congestion control algorithm being selected based at least in part on the one or more communication parameters. The means for causing the UE to perform the operations described herein may include, for example, one or more of the communications manager 140, the antennas 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0061] 2 are shown as separate components, the functionality described with respect to the blocks may be implemented in a single hardware, software, or combination component, or in various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, TX MIMO processor 266, or another processor may be performed by or under the control of controller / processor 280.

[0062] The deployment of a communication system such as a 5G NR system may be configured in multiple ways with various components or components. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a radio access network (RAN) node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or non-aggregated architecture. For example, a base station (e.g., a Node B (NB), evolved NB (eNB), NR base station (BS), 5G NB, gNode B (gNB), access point (AP), TRP, or cell, among other examples), or one or more units (or one or more components) performing a base station function may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a non-aggregated base station. A "network entity" or "network node" may refer to a disaggregated base station or one or more units of a disaggregated base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0063] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (e.g., one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be collocated with the CU, or alternatively may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0064] The operation or network design of the base station type may take into account the aggregated nature of the base station functionality. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (e.g., a network configuration supported by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating the base station functionality into one or more units that may be deployed separately. A disaggregated base station may include functions implemented across two or more units in various physical locations as well as functions implemented virtually for at least one unit, which may allow flexibility in the network design. Various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0065] 3 illustrates an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link or indirectly with the core network 320 via one or more disaggregated control units (e.g., a quasi-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, e.g., through an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 340 simultaneously.

[0066] Each of the units including CU310, DU330, RU340, and the quasi-RT RIC325, non-RT RIC315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. A related processor or controller that provides instructions to each of the units or to one or more communication interfaces of each respective unit may be configured to communicate with one or more of the other units via the transmission medium. In some embodiments, each of the units includes a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium, and a wireless interface including a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive, transmit, or both receive and transmit signals to one or more of the other units via a wireless transmission medium.

[0067] In some aspects, the CU 310 can host one or more higher layer control functions. Such control functions can include a radio resource control (RRC) function, a packet data convergence protocol (PDCP) function, or a service data adaptation protocol (SDAP) function, among other examples. Each control function can implement an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functions (e.g., a Central Unit-User Plane (CU-UP) function), control plane functions (e.g., a Central Unit-Control Plane (CU-CP) function), or a combination thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface, when implemented in an O-RAN configuration. The CU 310 may be implemented to communicate with the DU 330, as necessary, for network control and signaling.

[0068] Each DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more upper physical (PHY) layers, at least in part according to a functional division such as that defined by 3GPP. In some aspects, the one or more upper PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more lower PHY layers, such as implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which may also be referred to as a module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU330 or with control functions hosted by the CU310.

[0069] Each RU 340 may implement lower layer functions. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node hosting RF processing functions or lower PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional division such as a lower layer functional division (e.g., a functional division defined by 3GPP). In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

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

[0071] The non-RT RIC 315 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / functions in the quasi-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the quasi-RT RIC 325 (e.g., via an A1 interface). The quasi-RT RIC 325 can be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources through data collection and actions via interfaces that connect one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the quasi-RT RIC 325 (e.g., via an E2 interface).

[0072] In some implementations, the non-RT RIC 315 can receive parameters or external enrichment information from an external server to generate the AI / ML models to be deployed in the quasi-RT RIC 325. Such information can be utilized by the quasi-RT RIC 325 and can be received at the SMO framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some embodiments, the non-RT RIC 315 or the quasi-RT RIC 325 can be configured to adjust the behavior or performance of the RAN. For example, the non-RT RIC 315 may monitor long-term trends and patterns regarding performance and use the AI / ML models to implement corrective actions through the SMO framework 305 (e.g., reconfiguration via the O1 interface) or through the creation of RAN management policies (e.g., A1 interface policies).

[0073] As noted above, Figure 3 is provided as an example, other implementations may differ from those described with respect to Figure 3.

[0074] 4 is a diagram illustrating an example connection conveyed by a UE in accordance with the present disclosure. As shown in FIG. 4, a connected device may communicate with an application server via a connection between the connected device and a network node. For example, the UE and the network node may be hops along a communication path from the connected device and the application server.

[0075] As indicated by reference numeral 405, the UE may receive a configuration for communicating with a network over a first link between the UE and a network node. The first link may use a RAT configured for cellular communications (e.g., 5G or LTE, among other examples). The configuration may indicate communication parameters based at least in part on channel conditions, an indication from the UE regarding a type of communication expected, and / or traffic at the network node (e.g., within a cell of the network served by the network node), among other examples.

[0076] The UE and the connected device may exchange communications for the connected device and the application server over a second link between the UE and the connected device, as indicated by reference numeral 410. The second link may be based at least in part on a protocol used for the second link (e.g., a local area network, or a short-range wireless connection, among other examples).

[0077] Network nodes and application servers may exchange communications for connected devices and application servers, as indicated by reference numeral 415. In some networks, network nodes and application servers may exchange communications over wireless and / or wired connections that may include one or more hops.

[0078] As indicated by reference numeral 420, the network node and the UE may communicate based at least in part on the configuration of the first link. The configuration of the first link may be independent of the second link and / or the connection between the network node and the application server. In some networks, for example, timing, latency, and / or other communication parameters may not be suitable and / or optimized for communication between the connected device and the application server. In some networks, the communication may not be able to meet timing requirements, which may distort and / or cause failures in the data feed, such as an extended reality (XR) stream or a video stream. In this manner, the communication between the connected device and the application server may have communication errors that consume processing, power, network, and / or communication resources to detect and correct.

[0079] As noted above, Figure 4 is provided as an example. Other implementations may differ from that described with respect to Figure 4.

[0080] In some aspects described herein, a connected device may use a cross-layer service entity to provide instructions associated with managing one or more communications between the connected device and a network node (e.g., on the path to an application server) to a UE having a connection with the network node. The connected device may provide application-based communication parameters as part of the instructions. The connected device may provide instructions to an application layer entity (e.g., a cross-layer service entity) of the UE via an application layer entity (e.g., a cross-layer service proxy entity) of the connected device. A cross-layer application programming interface (API) may provide information from the application layer entity of the UE to a modem of the UE.

[0081] Cross-layer services may be used to indicate different features and / or modem optimizations that may improve communications of the connected devices. Additionally or alternatively, cross-layer services may increase responsiveness to adaptation of the connected device's application to change parameters of the OTA connection between the UE and the network node. The UE's modem, transmit chain, and / or other components may be configured and / or adjusted to meet the requirements of the connected device's application.

[0082] In one example, the connected device may be an XR device that is tethered to the UE and invokes a service (e.g., low-latency MAC (LLM) service and / or positioning service) on the UE. The XR device and the UE exchange device configurations (e.g., timing parameters of a link between the XR device and the UE, timing parameters of a link between the UE and the network, and / or application-based parameters, among other examples) to optimize end-to-end performance of communications between the XR device and the application server. The XR device may receive configuration information to optimize the link between the UE and the XR device for communications with the network (e.g., the network node to which the UE is connected).

[0083] In another embodiment, the application layer entity of the UE provides a bandwidth estimation (e.g., for the uplink and / or downlink) to the connected device via the application layer entity of the UE and the application layer entity of the connected device. The application client of the connected device may use the bandwidth estimation to configure end-to-end rate adaptation for communication with an application server. For example, the application client of the connected device may call a bandwidth estimation API function of the connected device. The bandwidth estimation API function may obtain a bandwidth estimate of a link between the connected device and the UE via a modem of the connected device. The bandwidth estimation API function may call a cross-layer service proxy entity that retrieves a bandwidth estimate of a link between the UE and the network from a cross-layer service entity of the UE. The bandwidth estimation API function may return a minimum of a bandwidth estimate of a link between the connected device and the UE and a bandwidth estimate of a link between the UE and the network. Based at least in part on the bandwidth estimate, the application client of the connected device may configure communication with an application server via the UE and the network.

[0084] In some aspects, an application layer entity (e.g., a cross-layer service proxy entity) of the connected device discovers an application layer entity (e.g., a cross-layer service entity) of the UE configured to provide cross-layer information to the modem, the transmit chain, and / or other components of the UE. In some aspects, the application layer entity of the connected device may discover the application layer entity of the UE via a local area network direct information exchange (e.g., Wi-Fi Direct), a short-range wireless information exchange (e.g., Bluetooth low energy advertisement (BTLE)), or a domain name system information exchange, among other examples.

[0085] In some aspects, the application layer entity of the connected device and the application layer entity of the UE may perform mutual authentication to verify that the UE is authorized to convey communications for the connected device and that the connected device is authorized to use the UE to convey communications. In some aspects, the application layer entity of the connected device and the application layer entity of the UE may use device level mutual authentication, such as a network password (e.g., a Wi-Fi password), to perform mutual authentication. In some aspects, the application layer entity of the connected device and the application layer entity of the UE may use a shared secret authentication to perform mutual authentication.

[0086] In some aspects, a device connected to a UE may communicate to exchange data and / or other messages (e.g., configuration information). For example, a device connected to a UE may exchange messages at least partially based on application inputs from an application client on the connected device. In some aspects, the UE and the connected device may use sockets such as, among other examples, one or more transmission control protocol (TCP) sockets, or one or more user datagram protocol (UDP) over Internet protocol (IP) sockets. In some aspects, the message format may be defined and mutually agreed upon between the application layer entity of the connected device and the application layer entity of the UE.

[0087] At least partially based on the use of an application layer entity for a device connected to a UE to communicate physical layer metrics and / or parameters, the connected device may improve communication with an application server via the UE and the associated network. For example, timing, latency, rate adaptation, and / or other communication parameters may be configured and / or optimized for communication between the connected device and the application server. In this way, the communication may meet timing requirements, which may reduce distortion and / or disruption to a data feed such as an XR stream or a video stream. In this way, the communication between the connected device and the application server may reduce communication errors that may otherwise consume processing, power, network, and / or communication resources to detect and correct.

[0088] FIG. 5 is a diagram of example 500 associated with communication transmitted via a UE according to the present disclosure. As shown in FIG. 5, a network node (e.g., network node 110, CU, DU, and / or RU) may communicate with a UE (e.g., UE 120). In some aspects, the network node and the UE may be part of a wireless network (e.g., wireless network 100). The UE and the network node may provide a connection between a connected device (e.g., among others in the example, a device connected to the UE, an XR device, and / or an additional UE) and an application server. For example, the connected device may exchange communications with the UE via a link, the UE may exchange communications with the network node via a link, and the network node may exchange communications with the application server via a connection (e.g., among others in other examples, wireless or wired, single-hop or multi-hop).

[0089] As indicated by reference numeral 505, the network node and the UE may exchange configuration information and / or establish a connection. For example, the network node may transmit configuration information and the UE may receive configuration information. In some aspects, the UE may receive the configuration information via one or more of, among other examples, RRC signaling, one or more medium access control (MAC) control elements (CEs), and / or downlink control information (DCI). In some aspects, the configuration information may include, among other examples, an indication of one or more configuration parameters (e.g., already known to the UE and / or previously indicated by the network node or other network devices) for selection by the UE and / or explicit configuration information for use by the UE to configure the UE.

[0090] In some aspects, the configuration information may indicate, among other examples, that the UE should be configured for communication with the network node, at least partially based on traffic conditions at the network node, the traffic needs of the UE, and / or channel conditions. In some aspects, the UE may indicate that it can relay communication between a device to which the UE is connected and an application server.

[0091] As indicated by reference numeral 510, the UE may configure itself for communication with the network node. In some aspects, the UE may be configured to communicate data generated or terminated at the UE. In some aspects, the UE can be configured to perform one or more operations described herein, at least partially based on the configuration information.

[0092] As indicated by reference numeral 515, the UE and the connected device may establish a connection between application layer entities (e.g., cross-layer service entities) of the UE and the connected device. In some aspects, the UE and the connected device may establish a connection between the cross-layer service proxy entity of the connected device and the cross-layer service entity of the UE. In some aspects, to establish the connection, the UE and the connected device may perform a discovery operation in which the connected device discovers services via the UE. The discovery operation may include, among other examples, direct local area network information exchange, short-range wireless information exchange, and / or domain name system information exchange. In some aspects, the UE and the connected device may perform an authentication operation in which the connected device and the UE authenticate the connection with each other. In some aspects, the authentication operation may include, among other examples, device-level mutual authentication or shared secret key authentication.

[0093] In some aspects, the link between the UE and a connected device may be at least partially based on a first RAT (e.g., a short-range RAT such as Wi-Fi, Bluetooth, and / or near field communication, among other examples). In some aspects, the link between the UE and a network node may be at least partially based on a second RAT (e.g., a cellular network RAT such as 5G or LTE).

[0094] As indicated by reference numeral 520, the UE may provide an indication of the parameters of the link between the UE and the network node, and the connected device may receive it. In some aspects, the indication may indicate a performance indicator of the link between the UE and the network node. For example, the performance indicator may indicate, among other examples, the throughput of the link between the UE and the network node, the timing parameters of the link, and / or the error rate of the link. In some aspects, the UE may provide an indication that facilitates a cross-layer API for communication between the application layer and the physical layer to the application layer entity (e.g., a cross-layer service entity) of the connected device via the application layer entity (e.g., a cross-layer service proxy entity) of the connected device.

[0095] In some aspects, the UE may transmit an indication of the communication occasion timing and / or duration (e.g., discontinuous reception (DRX) on the duration timing) for the link between the UE and the network node. For example, the UE may transmit an indication of the communication occasion timing and / or duration together with an indication of the parameters of the link between the UE and the network node to the connected device, and / or may transmit it after receiving an indication from the connected device (e.g., as described with respect to reference numeral 525).

[0096] As indicated by reference numeral 525, the UE may receive an instruction for the management of one or more communications between the UE and a network node, and a connected device may transmit it. For example, the instruction may be at least partially based on one or more communications generated or terminated at the connected device that are transmitted between the connected device and the network node (e.g., en route to an application server). An instruction for the management of one or more communications may indicate quality of service (QoS) requirements, latency requirements, and / or bandwidth requirements associated with an application client of the connected device.

[0097] In some aspects, the UE may receive an instruction from an application layer entity of the connected device via the application layer entity of the UE.

[0098] As indicated by reference numeral 530, the UE may transmit an instruction of one or more parameters for one or more communications between the UE and a network node. For example, among other examples, the UE may transmit an instruction of QoS parameters, timing requirements (e.g., latency requirements), periodicity of periodic communications, and / or expected bandwidth to be used for one or more communications. In some aspects, the one or more parameters may be at least partially based on the UE establishing a connection with the connected device for the UE to transmit one or more communications between the connected device and the network node.

[0099] As indicated by reference numeral 535, the UE may receive an instruction to accept or reject one or more parameters of one or more communications between the UE and a network node. For example, with respect to reference numeral 530, the UE may indicate the requested parameters, and the UE may determine whether to grant the requested parameters for one or more communications to the UE.

[0100] As indicated by reference numeral 540, the UE may be configured to relay one or more communications between a connected device and a network node. For example, the UE may update the configuration described with respect to reference numeral 510, at least in part based on acting as a hop in a link between the network node and the connected device. In some aspects, the UE may configure itself, at least in part based on transmitting an indication of one or more parameters for one or more communications and / or at least in part based on receiving an indication of acceptance or rejection of one or more parameters.

[0101] As indicated by reference numeral 545, the UE may relay one or more communications between a connected device and a network node, at least in part based on how the UE is configured. In some aspects, the network node may relay (e.g., route) one or more communications to an application server.

[0102] In some aspects, relaying one or more communications may include the network node transmitting one or more downlink communications and the UE receiving the one or more downlink communications and forwarding them to the connected device. In some aspects, relaying one or more communications may include the UE receiving one or more uplink communications from the connected device and transmitting the one or more uplink communications to the network node for routing to an application server.

[0103] Based at least in part on using an application layer entity for a device connected to a UE to communicate physical layer metrics and / or parameters, the connected device may improve communication with an application server via the UE and associated network. For example, timing, latency, rate adaptation, and / or other communication parameters may be configured and / or optimized for communication between the connected device and the application server. In this way, communication may meet timing requirements, which may reduce distortion and / or impairments to a data feed such as an XR stream or video stream. In this way, communication between the connected device and the application server may reduce communication errors that would otherwise consume processing, power, network, and / or communication resources to detect and correct.

[0104] As shown above, FIG. 5 is provided as an example. Other embodiments may differ from those described with respect to FIG. 5.

[0105] FIG. 6 is a diagram of example 600 associated with communication transmitted via a UE according to the present disclosure. As shown in FIG. 6, a device (e.g., UE120, an XR device, and / or a device connected to the UE) may communicate with a UE (e.g., UE120). In some aspects, the device and the UE may be part of a wireless network (e.g., a local area network) and / or may be connected through a direct connection (e.g., Bluetooth). The UE may provide a connection between the device and the application server. For example, the device may exchange communication with the UE via a link, the UE may exchange communication with a network node via the link, and the network node may exchange communication with the application server via a connection (e.g., wireless or wired, single-hop or multi-hop, among other examples).

[0106] As shown in FIG. 6, device 605 may include an application processor 610 associated with application 615, and a high level operating system (HLOS) and / or software development kit (SDK) 620. Application 615 may communicate with cross-layer service proxy 625 using HLOS and / or SDK API 630.

[0107] UE 635 may include an application processor 640 associated with HLOS and / or SDK 645. HLOS and / or SDK 645 may include a cross-layer service 650 configured to communicate with the UE's modem 655. For example, cross-layer service 650 may indicate one or more parameters (e.g., modem-based parameters) for communicating via the physical layer, at least in part based on receiving one or more parameters in the application layer or a higher layer. Cross-layer service 650 may indicate one or more parameters for communicating with a network node to cross-layer feature 660 of modem 655, at least in part based on application-based parameters. In some aspects, cross-layer service 650 may receive an indication of one or more parameters used to configure an application client for communicating, at least in part based on the configuration of the communication link with modem 655 and / or the network node, from cross-layer feature 660. Cross-layer service 650 and cross-layer feature 660 may communicate via a modem API 665 that may include a cross-layer API. Cross-layer service proxy 625 and cross-layer service 650 may communicate via connection 670. Connection 670 may include an application layer connection.

[0108] As shown above, FIG. 6 is provided as an example. Other embodiments may differ from those described with respect to FIG. 6.

[0109] FIG. 7 is a diagram illustrating example 700 associated with network orchestration by a network node according to the present disclosure. As shown in FIG. 5, a network node (e.g., network node 110, a core network (CN) network node, a CU, a DU, and / or an RU) may communicate with one or more UEs (e.g., UE 120). In some aspects, the network node and the one or more UEs may be part of a wireless network (e.g., wireless network 100) and / or may communicate via an additional network node (e.g., a RAN network node).

[0110] As shown by reference numeral 705, the one or more UEs and the network node may establish one or more connections between a cross-layer entity of the one or more UEs and a cross-layer entity of the network node. For example, among other examples, the network node may establish a first connection between a first cross-layer entity of the network node and a cross-layer entity of a first UE, and the network node may establish a second connection between a cross-layer entity of the network node (e.g., the first cross-layer entity or the second cross-layer entity) and a cross-layer entity of a second UE.

[0111] In some aspects, establishing the connection may include a discovery operation in which the network node discovers a cross-layer service entity of the UE and / or an authentication operation in which the network node and the UE mutually authenticate the connection. In some aspects, the discovery operation may include, among other examples, local area network information exchange, wide area network information exchange, and / or domain name system information exchange. In some aspects, the authentication operation may include, among other examples, device-level mutual authentication or shared secret key authentication. The network node may similarly establish a connection with an application server.

[0112] As indicated by reference numeral 710, a UE among one or more UEs may send an indication of one or more parameters (e.g., one or more first parameters) of a communication link between the UE and an application server. In some aspects, a network node may receive the indication via an additional network node, such as a RAN network node connected to the UE. The RAN network node may route the indication to the network node. Additionally or alternatively, the network node may include a RAN network node or may be collocated with a RAN network node. In some aspects, the UE may send an indication from a cross-layer service entity of the UE to a cross-layer service proxy entity of the network node. For example, the indication may be transmitted over application layer communication between the UE and the network node.

[0113] In some aspects, the UE may indicate, among other examples, QoS requirements, latency requirements, and / or bandwidth requirements. Additionally or alternatively, the UE may indicate the periodicity of periodic communications associated with an application client in the UE.

[0114] In some aspects, the UE may indicate one or more parameters associated with a link between the UE and a network (e.g., a RAN network node of the network). For example, the UE may indicate, among other examples, the throughput of a link between the UE and an additional network node associated with the network node, or the timing parameters of a link between the UE and the additional network node.

[0115] As indicated by reference numeral 715, the network node may receive an indication of one or more parameters (e.g., one or more first parameters) of a communication link between the UE and the application server from the application server. For example, the application server may indicate, among other things, QoS requirements, latency requirements, bandwidth requirements, and / or the periodicity of periodic communications associated with the application client in the UE. In this way, the network node may determine an optimized communication schedule for the application server and / or the application client for communicating via the network associated with the network node.

[0116] As indicated by reference numeral 720, the UE may receive an indication of one or more parameters (e.g., one or more second parameters) for communicating across the network associated with the network node. For example, the UE may receive an indication of, among other things, the periodicity for communication, the bandwidth available for communication, and / or the timing of communication. In some aspects, the network node may send an indication from the cross-layer service proxy entity of the network node to the cross-layer service entity of the UE. For example, the indication may be transmitted over the application layer communication between the network node and the UE.

[0117] As indicated by reference numeral 725, the UE may configure itself to communicate with the application server across the network. For example, the UE may configure itself at least in part based on transmitting an indication of one or more parameters of the communication link between the UE and the application server. In some aspects, the UE may configure itself at least in part based on receiving configuration information from the RAN network node and / or the network node and at least in part based on parameters for communicating across the network (e.g., as described with respect to reference numeral 720).

[0118] Based at least in part on the UE and the network node sharing parameters for the communication link and / or related communications, the network node can improve network efficiency, reduce dropped packets, and / or reduce congestion on the network, at least in part based on orchestrating the communications. For example, the network node may indicate the timing for communication between the UE and the application server to avoid congested routing times. In this way, the network node can reduce communication errors that might otherwise consume processing, power, network, and / or communication resources to detect and correct.

[0119] As shown above, FIG. 7 is provided as an example. Other embodiments may differ from those described with respect to FIG. 7.

[0120] FIG. 8 is a diagram of example 800 associated with network orchestration by a network node according to the present disclosure. As shown in FIG. 8, a network node (e.g., network node 110, CN network node, CU, DU, and / or RU) can communicate with one or more UEs (e.g., UE120) and one or more servers. The network node can communicate using cross-layer entities of the network node, and cross-layer entities of one or more UEs, and / or one or more servers, for communicating at the application layer and / or for providing or receiving communications at lower layers.

[0121] The network node 805 includes a cross-layer service proxy entity 810 and a cross-layer service proxy entity 815 for communicating with one or more UEs. For example, the network node 805 may use the cross-layer service proxy entity 810 to communicate with the UE 820. The UE 820 may include an application processor 825 associated with the HLOS and / or SDK 830. The HLOS and / or SDK 830 may include a cross-layer service 835 configured to communicate with the UE's modem 840. For example, the cross-layer service 835 may indicate one or more parameters (e.g., modem-based parameters) for communicating via the physical layer, at least in part based on receiving one or more parameters in the application layer or a higher layer. The cross-layer service 835 may indicate one or more parameters for communicating with a network node (e.g., a RAN network node) to the cross-layer feature 845 of the modem 840, at least in part based on application-based parameters. In some aspects, the cross-layer service 835 may receive an indication of one or more parameters that can be used to configure an application client for communicating, at least in part based on the configuration of the communication link with the modem 840 and / or the network node, from the cross-layer feature 845. The cross-layer service 835 and the cross-layer feature 845 may communicate via a modem API 850 that may include a cross-layer API. In some aspects, the network node 805 may communicate with a UE 855 having a cross-layer service 860 via the cross-layer service proxy 815.

[0122] The network node 805 may also communicate with one or more servers associated with application clients operating on the UE 820 and / or UE 855. For example, the network node 805 may communicate with a server 865 having an application 870 associated with an application client of the UE 820. Additionally or alternatively, the network node 805 may communicate with a server 875 having an application 880 associated with an application client of the UE 855. In this way, the network node may receive information associated with the applications 870, 880, and / or the application clients of the UE 820 and / or UE 855. Among other examples, the network node may determine one or more parameters that may optimize communication between the applications 870, 880, and / or the application clients of the UE 820 and / or UE 855 such that communication errors are reduced and routing times during which communication is congested are avoided.

[0123] As shown above, FIG. 8 is provided as an example. Other embodiments may differ from those described with respect to FIG. 8.

[0124] FIG. 9 is a diagram illustrating an exemplary process 900, such as may be performed by a UE, according to the present disclosure. The exemplary process 900 is an example of operations performed by a UE (e.g., UE 120) associated with communication transmitted via the UE.

[0125] As shown in FIG. 9, in some aspects, process 900 may include receiving, from a connected device, an instruction associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being transmitted by a UE between the connected device and the network node (block 910). For example, the UE may receive (e.g., using communication manager 140 and / or receiving component 1302 shown in FIG. 13), from the connected device, an instruction associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being transmitted by the UE between the connected device and the network node, as described above.

[0126] As further shown in FIG. 9, in some aspects, process 900 may include configuring the UE to transmit one or more communications between the connected device and the network node, at least partially based on the instruction (block 920). For example, the UE may configure (e.g., using communication manager 140 and / or communication manager 1308 shown in FIG. 13) to transmit one or more communications between the connected device and the network node, at least partially based on the instruction, as described above.

[0127] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or elsewhere in this specification, with respect to one or more other processes described.

[0128] In a first aspect, a first link between the UE and a connected device is at least partially based on a first RAT, and a second link between the UE and a network node is a second RAT.

[0129] In a second aspect, alone or in combination with the first aspect, process 900 includes providing one or more indications to a connected device of either the throughput of the link between the UE and the network node or the timing parameters of the link between the UE and the network node.

[0130] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving an indication includes receiving the indication at the cross-layer service entity of the UE from the cross-layer service proxy entity of the connected device.

[0131] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 900 includes establishing a connection between the cross-layer service proxy entity of the connected device and the cross-layer service entity of the UE.

[0132] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, establishing the connection includes performing one or more of a discovery operation in which the connected device discovers services via the UE or an authentication operation in which the connected device and the UE mutually authenticate the connection.

[0133] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the discovery operation includes one or more of direct local area network information exchange, short-range wireless information exchange, or domain name system information exchange.

[0134] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the authentication operation includes one or more of device-level mutual authentication or shared secret key authentication.

[0135] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, it further includes transmitting an indication of communication occasion timing for a link between the UE and the network node to a connected device, and an indication associated with the management of one or more communications between the connected device and the network node is at least partially based on the communication occasion timing.

[0136] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 900 further includes transmitting an indication of one or more parameters for one or more communications to a network node, and the indication of the one or more parameters is at least partially based on establishing a connection with a device to which the UE is connected for the UE to transmit one or more communications between the connected device and the network node.

[0137] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 900 includes transmitting one or more communications between a connected device and a network node, at least partially based on configuring the UE.

[0138] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, transmitting one or more communications between a connected device and a network node includes one or more of transmitting downlink communication to a connected device via one or more sockets of the UE, or receiving uplink communication from a connected device via one or more sockets of the UE.

[0139] FIG. 9 shows exemplary blocks of process 900, but in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or blocks configured differently from those shown in FIG. 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0140] Figure 10 is a diagram showing an exemplary process 1000 implemented by, for example, a device according to the present disclosure. The exemplary process 1000 is an example in which a device (e.g., among others in the examples, e.g., a connected device, a UE, and / or an XR device) performs operations associated with communications transmitted via the UE.

[0141] As shown in Figure 10, in some aspects, process 1000 may include sending (block 1010) to the UE instructions associated with the management of one or more communications between the device and a network node of a wireless network, where the one or more communications are transmitted by the UE between the device and the network node. For example, the device may (e.g., using communication manager 140 and / or transmission component 1504 shown in Figure 15) send to the UE instructions associated with the management of one or more communications between the device and a network node of a wireless network, where the one or more communications are transmitted by the UE between the device and the network node, as described above.

[0142] As further shown in Figure 10, in some aspects, process 1000 may include configuring (block 1020) the device for one or more communications via the UE, at least partially based on the instructions. For example, the device may (e.g., using communication manager 140 and / or communication manager 1408 shown in Figure 14) configure the device for one or more communications via the UE, at least partially based on the instructions, as described above.

[0143] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or elsewhere in this specification with respect to one or more other processes.

[0144] In a first aspect, the first link between the UE and the device is at least partially based on a first RAT, and the second link between the UE and the network node is a second RAT.

[0145] In a second aspect, alone or in combination with the first aspect, process 1000 includes receiving, from the UE, one or more indications of either the throughput of the link between the UE and the network node or the timing parameters of the link between the UE and the network node.

[0146] In a third aspect, alone or in combination with one or more of the first and second aspects, configuring the device for one or more communications includes one or more communication parameters that are at least partially based on either the throughput of the link between the UE and the network node or the throughput of the link between the device and the UE.

[0147] In a fourth aspect, alone or in combination with one or more of the first to third aspects, transmitting an indication includes transmitting an indication from a cross-layer service proxy entity of the device to a cross-layer service entity of the UE.

[0148] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1000 includes establishing a connection between the cross-layer service proxy entity of the device and the cross-layer service entity of the UE.

[0149] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, establishing the connection includes performing one or more of a discovery operation in which the device discovers a service via the UE or an authentication operation in which the device and the UE mutually authenticate the connection.

[0150] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the discovery operation includes one or more of direct local area network information exchange, short-range wireless information exchange, or domain name system information exchange.

[0151] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the authentication operation includes one or more of device-level mutual authentication or shared secret key authentication.

[0152] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 1000 includes receiving, from the UE, an indication of communication occasion timing for a link between the UE and a network node, and an indication associated with the management of one or more communications between the device and the network node is at least partially based on the communication occasion timing.

[0153] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process 1000 includes transmitting, via the UE to an application server, an indication of one or more parameters for one or more communications, and the indication of the one or more parameters is at least partially based on establishing a connection with the UE to convey one or more communications between the device and the network node.

[0154] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process 1000 includes transmitting one or more communications to a network node via the UE or receiving one or more communications from a network node via the UE.

[0155] In a twelfth aspect, transmitting one or more communications to a network node via a UE, alone or in combination with one or more of the first to eleventh aspects, includes transmitting one or more communications to the UE via one or more sockets of the UE; or receiving one or more communications from a network node via a UE includes receiving one or more communications from the network node via one or more sockets of the UE.

[0156] FIG. 10 shows exemplary blocks of process 1000, but in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those shown in FIG. 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0157] FIG. 11 is a diagram showing an exemplary process 1100, for example, implemented by a UE according to the present disclosure. The exemplary process 1100 is an example of a UE (e.g., UE 120) performing operations associated with communications transmitted via the UE.

[0158] As shown in FIG. 11, in some aspects, process 1100 may include transmitting a first indication of one or more first parameters of a communication link between the UE and an application server across a network associated with a network node (block 1110). For example, the UE may transmit a first indication of one or more first parameters of a communication link between the UE and an application server across a network associated with a network node, as described above (e.g., using communication manager 140 and / or transmission component 1304 shown in FIG. 13).

[0159] As further shown in FIG. 11, in some aspects, process 1100 may include receiving (block 1120) a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication. For example, the UE may receive (e.g., using communication manager 140 and / or receiving component 1302 shown in FIG. 13), as described above, a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication.

[0160] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects, described with respect to one or more other processes described below and / or elsewhere in this specification.

[0161] In a first aspect, the first indication indicates one or more of the throughput of a link between the UE and an additional network node associated with the network node, or the timing parameters of a link between the UE and the additional network node.

[0162] In a second aspect, alone or in combination with the first aspect, the network node includes a CN network node, and receiving the first indication of the one or more first parameters includes receiving the first indication via a RAN network node.

[0163] In a third aspect, alone or in combination with one or more of the first and second aspects, sending the first indication includes sending the first indication from a cross-layer service entity of the UE to a cross-layer service proxy entity of the network node.

[0164] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1100 includes establishing a connection between a cross-layer service proxy entity of a network node and a cross-layer service entity of a UE.

[0165] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, establishing the connection includes performing one or more of a discovery operation in which the network node discovers the cross-layer service entity of the UE, or an authentication operation in which the network node and the UE mutually authenticate the connection.

[0166] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the discovery operation includes one or more of local area network information exchange, wide area network information exchange, or domain name system information exchange.

[0167] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the authentication operation includes one or more of device-level mutual authentication or shared secret key authentication.

[0168] FIG. 11 shows exemplary blocks of process 1100, but in some aspects, process 1100 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those shown in FIG. 11. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0169] FIG. 12 is a diagram showing an exemplary process 1200 performed, for example, by a network node according to the present disclosure. The exemplary process 1200 is an example of operations performed by a network node (e.g., a CN network node and / or network node 805) related to network orchestration by the network node.

[0170] As shown in FIG. 12, in some aspects, process 1200 may include receiving (block 1210) a first indication of one or more first parameters of a communication link between a UE and an application server across a network associated with a network node. For example, a network node may receive (e.g., using communication manager 150 and / or receiving component 1502 shown in FIG. 15) a first indication of one or more first parameters of a communication link between a UE and an application server across a network associated with the network node, as described above.

[0171] As further shown in FIG. 12, in some aspects, process 1200 may include transmitting (block 1220) a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication. For example, a network node may transmit (e.g., using communication manager 150 and / or transmitting component 1504 shown in FIG. 15) a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication, as described above.

[0172] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in other parts of this specification, with respect to one or more other processes described herein.

[0173] In a first aspect, the first indication indicates one or more of the throughput of a link between the UE and an additional network node associated with the network node, the timing parameters of a link between the UE and the additional network node, the throughput of a link between the application server and the additional network node, or the timing parameters of a link between the application server and the additional network node.

[0174] In a second aspect, alone or in combination with the first aspect, the network node includes a CN network node, and receiving the first instruction includes receiving the first instruction via a RAN network node, or receiving the first instruction via an application server, including one or more of these.

[0175] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving the first instruction includes receiving the first instruction at a cross-layer service proxy entity of the network node from a cross-layer service entity of the UE.

[0176] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1200 includes establishing a connection between a cross-layer service proxy entity of the network node and a cross-layer service entity of the UE.

[0177] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, establishing the connection includes performing one or more of a discovery operation in which the network node discovers the cross-layer service entity of the UE, or an authentication operation in which the network node and the UE mutually authenticate the connection.

[0178] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the discovery operation includes one or more of local area network information exchange, wide area network information exchange, or domain name system information exchange.

[0179] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the authentication operation includes one or more of device-level mutual authentication, or shared secret key authentication.

[0180] FIG. 12 shows exemplary blocks of process 1200, but in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those shown in FIG. 12. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0181] FIG. 13 is a diagram of an exemplary apparatus 1300 for wireless communication. Apparatus 1300 may be a UE, or a UE may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 can communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. Further shown, apparatus 1300 may include a communication manager 1308 (e.g., communication manager 140).

[0182] In some aspects, apparatus 1300 may be configured to perform one or more operations described herein with respect to FIGS. 5 - 8. Additionally or alternatively, apparatus 1300 may be configured to perform one or more processes described herein, such as process 900 of FIG. 9, process 1100 of FIG. 11, or a combination thereof. In some aspects, apparatus 1300 and / or one or more components shown in FIG. 13 may include one or more components of the UE described with respect to FIG. 2. Additionally or alternatively, one or more components shown in FIG. 13 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of a set of components may be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non - transitory computer - readable medium and executable by a controller or processor to perform the function or operation of the component.

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

[0184] The transmitting component 1304 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1306. In some aspects, one or more other components of the device 1300 may generate the communications and provide the generated communications to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing on the generated communications (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and transmit the processed signals to the device 1306. In some aspects, the transmitting component 1304 may include one or more antennas, modems, modulators, transmit MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the UE described with respect to FIG. 2. In some aspects, the transmitting component 1304 may be collocated with the receiving component 1302 in a transceiver.

[0185] The receiving component 1302 may receive, from a connected device, an instruction associated with the management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being transmitted by the UE between the connected device and the network node. The communication manager 1308 may configure the UE to transmit one or more communications between the connected device and the network node, at least partially based on the instruction.

[0186] The transmitting component 1304 may provide the connected device with one or more instructions of either the throughput of the link between the UE and the network node or the timing parameters of the link between the UE and the network node.

[0187] The communication manager 1308 may establish a connection between the cross-layer service proxy entity of the connected device and the cross-layer service entity of the UE.

[0188] The transmitting component 1304 may transmit to the network node an instruction of one or more parameters for one or more communications, the instruction of the one or more parameters being at least partially based on establishing a connection of the UE with the connected device for the UE to transmit one or more communications between the connected device and the network node.

[0189] The communication manager 1308 may transmit one or more communications between the connected device and the network node, at least partially based on configuring the UE.

[0190] The transmitting component 1304 may transmit a first instruction of one or more first parameters of a communication link between the UE and an application server across a network associated with the network node. The receiving component 1302 may receive a second instruction of one or more second parameters for communicating across the network, at least partially based on the first instruction.

[0191] The communication manager 1308 may establish a connection between the cross-layer service proxy entity of the network node and the cross-layer service entity of the UE.

[0192] The number and configuration of the components shown in FIG. 13 are provided as an example. In practice, there may be additional components, fewer components, different components, or components configured differently from those shown in FIG. 13. Further, two or more components shown in FIG. 13 may be implemented within a single component, or a single component shown in FIG. 13 may be implemented as a plurality of distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG. 13 may perform one or more functions described as being performed by another set of components shown in FIG. 13.

[0193] FIG. 14 is a diagram of an exemplary apparatus 1400 for wireless communication. The apparatus 1400 may be a device, or a device may include the apparatus 1400. In some aspects, the apparatus 1400 includes a receiving component 1402 and a transmitting component 1404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1400 may communicate with another device 1406 (such as a UE, a base station, or another wireless communication device) using the receiving component 1402 and the transmitting component 1404. Further shown, the apparatus 1400 may include a communication manager 1408 (e.g., communication manager 140).

[0194] In some aspects, apparatus 1400 may be configured to perform one or more operations described herein with respect to FIGS. 5-8. Additionally or alternatively, apparatus 1400 may be configured to perform one or more processes described herein, such as process 1000 of FIG. 10. In some aspects, apparatus 1400 and / or one or more components shown in FIG. 14 may include one or more components of the device described with respect to FIG. 2. Additionally or alternatively, one or more components shown in FIG. 14 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more components of a set of components may be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0195] Receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from apparatus 1406. Receiving component 1402 may provide the received communications to one or more other components of apparatus 1400. In some aspects, receiving component 1402 may perform signal processing (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and provide the processed signals to one or more other components of apparatus 1400. In some aspects, receiving component 1402 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the device described with respect to FIG. 2.

[0196] The transmitting component 1404 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communications and transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the devices described with respect to FIG. 2. In some aspects, the transmitting component 1404 may be collocated with the receiving component 1402 in a transceiver.

[0197] The transmitting component 1404 may transmit to the UE one or more instructions associated with the management of one or more communications between the device and a network node of the wireless network, the one or more communications being transmitted by the UE between the device and the network node. The communication manager 1408 may configure the device for one or more communications via the UE, at least in part based on the instructions.

[0198] The receiving component 1402 may receive from the UE one or more instructions of either the throughput of the link between the UE and the network node or the timing parameters of the link between the UE and the network node.

[0199] The communication manager 1408 may establish a connection between the cross-layer service proxy entity of the device and the cross-layer service entity of the UE.

[0200] The receiving component 1402 may receive from the UE an indication of the communication occasion timing for the link between the UE and the network node, and the indication associated with the management of one or more communications between the device and the network node is at least partially based on the communication occasion timing.

[0201] The transmitting component 1404 may transmit, via the UE, an indication of one or more parameters for one or more communications to the application server, and the indication of the one or more parameters is at least partially based on establishing a connection with the UE to convey one or more communications between the device and the network node.

[0202] The transmitting component 1404 may transmit one or more communications to the network node via the UE.

[0203] The receiving component 1402 may receive one or more communications from the network node via the UE.

[0204] The number and configuration of the components shown in FIG. 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or components configured differently from those shown in FIG. 14. Further, two or more of the components shown in FIG. 14 may be implemented within a single component, or a single component shown in FIG. 14 may be implemented as a plurality of distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG. 14 may perform one or more functions described as being performed by another set of components shown in FIG. 14.

[0205] FIG. 15 is a diagram of an exemplary apparatus 1500 for wireless communication. The apparatus 1500 may be a network node, or the network node may include the apparatus 1500. In some aspects, the apparatus 1500 includes a receiving component 1502 and a transmitting component 1504 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1500 can use the receiving component 1502 and the transmitting component 1504 to communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device). Further shown, the apparatus 1500 may include a communication manager 1508 (e.g., communication manager 150).

[0206] In some aspects, the apparatus 1500 may be configured to perform one or more operations described herein with respect to FIGS. 5-8. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as the process 1200 of FIG. 12. In some aspects, the apparatus 1500 and / or one or more components shown in FIG. 15 may include one or more components of the network node described with respect to FIG. 2. Additionally or alternatively, one or more components shown in FIG. 15 may be implemented within one or more components described with respect to FIG. 2. Additionally or alternatively, one or more of a set of components may be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0207] The receiving component 1502 may receive communications such as reference signals, control information, data communications, or combinations thereof from the device 1506. The receiving component 1502 may provide the received communications to one or more other components of the device 1500. In some aspects, the receiving component 1502 may perform signal processing on the received communications (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of the device 1500. In some aspects, the receiving component 1502 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the network nodes described with respect to FIG. 2.

[0208] The transmitting component 1504 may transmit communications such as reference signals, control information, data communications, or combinations thereof to the device 1506. In some aspects, one or more other components of the device 1500 may generate the communications, and may provide the generated communications to the transmitting component 1504 for transmission to the device 1506. In some aspects, the transmitting component 1504 may perform signal processing on the generated communications (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may transmit the processed signals to the device 1506. In some aspects, the transmitting component 1504 may include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the network nodes described with respect to FIG. 2. In some aspects, the transmitting component 1504 may be collocated with the receiving component 1502 in a transceiver.

[0209] The receiving component 1502 may receive a first indication of one or more first parameters of a communication link between the UE and the application server across a network associated with the network node. The transmitting component 1504 may transmit a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication.

[0210] The communication manager 1508 may establish a connection between a cross-layer service proxy entity of the network node and a cross-layer service entity of the UE.

[0211] The number and configuration of the components shown in FIG. 15 are provided as an example. In practice, there may be additional components, fewer components, different components, or components configured differently than those shown in FIG. 15. Further, two or more components shown in FIG. 15 may be implemented within a single component, or a single component shown in FIG. 15 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG. 15 may perform one or more functions described as being performed by another set of components shown in FIG. 15.

[0212] The following provides an overview of some aspects of the present disclosure.

[0213] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising receiving, from a connected device, an indication associated with management of one or more communications between the connected device and a network node of a wireless network, the one or more communications being relayed by the UE between the connected device and the network node, and configuring the UE to relay one or more communications between the connected device and the network node, at least partially based on the indication.

[0214] Aspect 2: The method according to aspect 1, wherein a first link between the UE and a connected device is at least partially based on a first radio access technology (RAT), and a second link between the UE and a network node is a second RAT.

[0215] Aspect 3: The method according to aspect 1 or 2, further comprising providing one or more of an indication of a throughput of a link between the UE and a network node, or a timing parameter of a link between the UE and a network node, to a connected device.

[0216] Aspect 4: The method according to any of aspects 1 to 3, wherein receiving the indication includes receiving the indication at a cross-layer service entity of the UE from a cross-layer service proxy entity of a connected device.

[0217] Aspect 5: The method according to any of aspects 1 to 4, further comprising establishing a connection between a cross-layer service proxy entity of a connected device and a cross-layer service entity of the UE.

[0218] Aspect 6: The method according to aspect 5, wherein establishing the connection includes performing one or more of a discovery operation in which a connected device discovers a service via the UE, or an authentication operation in which a connected device and the UE mutually authenticate the connection.

[0219] Aspect 7: The method according to aspect 6 or 7, wherein the discovery operation includes one or more of local area network direct information exchange, short-range wireless information exchange, or domain name system information exchange.

[0220] Aspect 8: The method according to aspect 6, wherein the authentication operation includes one or more of device-level mutual authentication or shared secret key authentication.

[0221] Aspect 9: The method according to any one of Aspects 1 to 8, further comprising sending, to a connected device, an indication of communication occasion timing for a link between the UE and the network node, wherein an indication associated with management of one or more communications between the connected device and the network node is at least partially based on the communication occasion timing.

[0222] Aspect 10: The method according to any one of Aspects 1 to 9, further comprising sending, to a network node, an indication of one or more parameters for one or more communications, wherein the indication of the one or more parameters is at least partially based on establishing a connection with the device to which the UE is connected for the UE to convey one or more communications between the device to which the UE is connected and the network node.

[0223] Aspect 11: The method according to any one of Aspects 1 to 10, further comprising conveying one or more communications between the connected device and the network node, at least partially based on configuring the UE.

[0224] Aspect 12: The method according to Aspect 11, wherein conveying one or more communications between the connected device and the network node includes one or more of transmitting downlink communication to the connected device via one or more sockets of the UE, or receiving uplink communication from the connected device via one or more sockets of the UE.

[0225] Aspect 13: A method of wireless communication implemented by a device, the method comprising: sending, to a user equipment (UE), an indication associated with management of one or more communications between the device and a network node of a wireless network, the one or more communications being conveyed by the UE between the device and the network node; and configuring the device for one or more communications via the UE, at least partially based on the indication.

[0226] Aspect 14: The method according to aspect 13, wherein the first link between the UE and the device is at least partially based on a first radio access technology (RAT), and the second link between the UE and the network node is a second RAT.

[0227] Aspect 15: The method according to aspect 13 or 14, further comprising receiving, from the UE, one or more indications of throughput of the link between the UE and the network node or timing parameters of the link between the UE and the network node.

[0228] Aspect 16: Configuring the device for one or more communications is at least partially based on one or more of the throughput of the link between the UE and the network node or the throughput of the link between the device and the UE, the configuration including one or more communication parameters, the method according to aspect 15.

[0229] Aspect 17: The method according to any of aspects 13 - 16, wherein transmitting the indication includes transmitting an indication from the cross-layer service proxy entity of the device to the cross-layer service entity of the UE.

[0230] Aspect 18: The method according to any of aspects 13 - 17, further comprising establishing a connection between the cross-layer service proxy entity of the device and the cross-layer service entity of the UE.

[0231] Aspect 19: The method according to aspect 18, wherein establishing the connection includes performing one or more of a discovery operation in which the device discovers a service via the UE or an authentication operation in which the device and the UE mutually authenticate the connection.

[0232] Aspect 20: The method according to aspect 19, wherein the discovery operation includes one or more of local area network direct information exchange, short-range wireless information exchange, or domain name system information exchange.

[0233] Aspect 21: The method according to aspect 19 or 20, wherein the authentication operation includes one or more of device-level mutual authentication or shared secret key authentication.

[0234] Aspect 22: The method according to any one of aspects 13 to 21, further comprising receiving, from the UE, an indication of communication occasion timing for a link between the UE and the network node, wherein an indication associated with the management of one or more communications between the device and the network node is at least partially based on the communication occasion timing.

[0235] Aspect 23: The method according to any one of aspects 13 to 22, further comprising transmitting, via the UE, an indication of one or more parameters for one or more communications to an application server, wherein the indication of the one or more parameters is at least partially based on establishing a connection with the UE to transmit one or more communications between the device and the network node.

[0236] Aspect 24: The method according to any one of aspects 13 to 23, further comprising transmitting one or more communications to a network node via the UE or receiving one or more communications from a network node via the UE.

[0237] Aspect 25: The method according to aspect 24, wherein transmitting one or more communications to a network node via the UE includes transmitting one or more communications to the UE via one or more sockets of the UE, or receiving one or more communications from a network node via the UE includes receiving one or more communications from the UE via one or more sockets of the UE.

[0238] Aspect 26: A method of wireless communication performed by a user equipment (UE), the method comprising: transmitting a first indication of one or more first parameters of a communication link between the UE and an application server across a network associated with a network node; and receiving a second indication of one or more second parameters for communicating across the network, at least partially based on the first indication.

[0239] Aspect 27: The method according to aspect 26, wherein the first indication indicates one or more of a throughput of a link between the UE and an additional network node associated with the network node, or a timing parameter of a link between the UE and the additional network node.

[0240] Aspect 28: The method according to aspect 26 or 27, wherein the network node includes a core network (CN) network node, and receiving the first indication of the one or more first parameters includes receiving the first indication via a radio access network (RAN) network node.

[0241] Aspect 29: The method according to any one of aspects 26 to 28, wherein transmitting the first indication includes transmitting the first indication from a cross-layer service entity of the UE to a cross-layer service proxy entity of the network node.

[0242] Aspect 30: The method according to any one of aspects 26 to 29, further comprising establishing a connection between a cross-layer service proxy entity of the network node and a cross-layer service entity of the UE.

[0243] Aspect 31: The method according to aspect 30, wherein establishing the connection includes performing one or more of a discovery operation in which the network node discovers the cross-layer service entity of the UE, or an authentication operation in which the network node and the UE mutually authenticate the connection.

[0244] Aspect 32: The method according to aspect 31, wherein the discovery operation includes one or more of local area network information exchange, wide area network information exchange, or domain name system information exchange.

[0245] Aspect 33: The method according to aspect 31 or 32, wherein the authentication operation includes one or more of device-level mutual authentication or shared secret key authentication.

[0246] Aspect 34: A method of wireless communication performed by a network node, comprising receiving a first indication of one or more first parameters of a communication link between a user equipment (UE) and an application server across a network associated with the network node, and transmitting a second indication of one or more second parameters for communicating across the network based at least in part on the first indication.

[0247] Aspect 35: The method according to aspect 34, wherein the first indication indicates one or more of the throughput of the link between the UE and an additional network node associated with the network node, the timing parameters of the link between the UE and the additional network node, the throughput of the link between the application server and the additional network node, or the timing parameters of the link between the application server and the additional network node.

[0248] Aspect 36: The method according to aspect 34 or 35, wherein the network node includes a core network (CN) network node, and receiving the first indication includes receiving the first indication via a radio access network (RAN) network node or receiving the first indication via an application server.

[0249] Aspect 37: The method according to any one of Aspects 34 to 36, wherein receiving the first instruction includes receiving the first instruction at a cross-layer service proxy entity of a network node from a cross-layer service entity of a UE.

[0250] Aspect 38: The method according to any one of Aspects 34 to 37, further including establishing a connection between a cross-layer service proxy entity of a network node and a cross-layer service entity of a UE.

[0251] Aspect 39: The method according to Aspect 38, wherein establishing the connection includes performing one or more of a discovery operation in which the network node discovers the cross-layer service entity of the UE, or an authentication operation in which the network node and the UE mutually authenticate the connection.

[0252] Aspect 40: The method according to Aspect 39, wherein the discovery operation includes one or more of local area network information exchange, wide area network information exchange, or domain name system information exchange.

[0253] Aspect 41: The method according to Aspect 39 or 40, wherein the authentication operation includes one or more of device-level mutual authentication or shared secret key authentication.

[0254] Aspect 42: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the device to perform one or more of the methods according to Aspects 1 to 41.

[0255] Aspect 43: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, wherein the one or more processors are configured to perform one or more of the methods according to Aspects 1 to 41.

[0256] Aspect 44: An apparatus for wireless communication, comprising at least one means for implementing one or more of the methods of Aspects 1 to 41.

[0257] Aspect 45: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to implement one or more of the methods of Aspects 1 to 41.

[0258] Aspect 46: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to implement one or more of the methods of Aspects 1 to 41.

[0259] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Modifications and variations can be added in light of the foregoing disclosure, or obtained from practice of the aspects.

[0260] As used herein, the term "component" shall be construed broadly as hardware and / or a combination of hardware and software. "Software" shall be construed broadly to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods does not limit the aspects. Thus, those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods at least in part based on the description herein, and the operations and behaviors of the systems and / or methods are described herein without reference to specific software code.

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

[0262] Even if certain combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure in various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or not disclosed herein. The disclosure in various aspects includes each dependent claim combined with any other claim within the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. By way of example, "at least one of a, b, or c" includes a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination having multiple of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other order of a, b, and c).

[0263] None of the elements, acts, or instructions used in this specification should be construed as important or essential unless expressly described as such. Also, as used in this specification, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Further, as used in this specification, the article "the" is intended to include one or more items referred to in relation to the article "the" and may be used interchangeably with "one or more". Additionally, as used in this specification, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more". When only one item is intended, the phrase "only one" or similar words are used. Also, as used in this specification, terms such as "has", "have", "having", etc. shall be open-ended terms that do not limit the elements modified by these terms (e.g., an element "having" A can also have B). Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified. Also, as used in this specification, the term "or" is inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise specified (e.g., when used in combination with "either" or "only one of").

Claims

1. 1. A user equipment (UE) for wireless communications, comprising: Memory and one or more processors coupled to the memory; wherein the one or more processors: receiving, at a cross-layer service entity of the UE, from a connected device, instructions associated with managing one or more communications between the connected device and a network node of a wireless network, the one or more communications being conveyed by the UE between the connected device and the network node; configuring the UE to convey the one or more communications between the connected device and the network node based at least in part on the instructions; and The UE is configured to:

2. A system comprising: a first link between the UE and the connected device; and a second link between the UE and the network node, wherein the first link between the UE and the connected device is based at least in part on a first radio access technology (RAT); The UE of claim 1 , wherein the second link between the UE and the network node is a second RAT.

3. the one or more processors: to the connected device, the throughput of the link between the UE and the network node; or timing parameters of the link between the UE and the network node; 10. The UE of claim 1, further configured to provide one or more indications of:

4. The one or more processors, in order to receive the instructions, The UE of claim 1 , configured to receive the indication from a cross-layer service proxy entity of the connected device.

5. the one or more processors: further configured to establish a connection between a cross-layer service proxy entity of the connected device and a cross-layer service entity of the UE; wherein the one or more processors, in order to establish the connection, a discovery operation in which the connected device discovers services via the UE; or an authentication operation in which the connected device and the UE mutually authenticate the connection; 2. The UE of claim 1, configured to implement one or more of:

6. The discovery operation: Local area network direct information exchange, short-range wireless information exchange, or Domain Name System Information Exchange, and / or The authentication operation Device-level mutual authentication, or Shared secret key authentication, 6. The UE of claim 5, comprising one or more of:

7. 10. The UE of claim 1, further comprising: sending to the connected device an indication of communication occasion timing for a link between the UE and the network node, wherein the indication associated with managing the one or more communications between the connected device and the network node is based at least in part on the communication occasion timing.

8. the one or more processors: further configured to send to the network node an indication of one or more parameters for the one or more communications; the indication of the one or more parameters is based at least in part on the UE establishing a connection with the connected device for conveying the one or more communications between the connected device and the network node. The UE of claim 1.

9. the one or more processors: further configured to convey the one or more communications between the connected device and the network node based at least in part on configuring the UE; Optionally, the one or more processors, for conveying the one or more communications between the connected device and the network node, sending downlink communications to the connected devices via one or more sockets of the UE; or receiving uplink communications from the connected devices via one or more sockets of the UE; The UE of claim 1 , configured to:

10. 1. A user equipment (UE) for wireless communications, comprising: Memory and one or more processors coupled to the memory; wherein the one or more processors: transmitting, from a cross-layer service entity of the UE, across a network associated with a network node, a first indication of one or more first parameters of a communication link between the UE and an application server; receiving, based at least in part on the first instruction, a second instruction of one or more second parameters for communication across the network; The UE is configured to:

11. The first instruction: the throughput of a link between the UE and an additional network node associated with the network node; or timing parameters of a link between the UE and the additional network node; 11. The UE of claim 10, wherein the UE indicates one or more of:

12. the network nodes include core network (CN) network nodes; 11. The UE of claim 10, wherein the one or more processors are configured to receive the first indication of the one or more first parameters via a radio access network (RAN) network node.

13. wherein the one or more processors, in order to transmit the first instruction, The UE of claim 10 , configured to send the first indication to a cross-layer service proxy entity of the network node.

14. 1. A method of wireless communication implemented by a user equipment (UE), comprising: receiving, at a cross-layer service entity of the UE, from a connected device, instructions associated with managing one or more communications between the connected device and a network node of a wireless network, the one or more communications being conveyed by the UE between the connected device and the network node; configuring the UE to convey the one or more communications between the connected device and the network node based at least in part on the instructions; and A method comprising:

15. 1. A method of wireless communication implemented by a user equipment (UE), comprising: transmitting, from a cross-layer service entity of the UE, across a network associated with a network node, a first indication of one or more first parameters of a communication link between the UE and an application server; receiving, based at least in part on the first instruction, a second instruction of one or more second parameters for communication across the network; A method comprising:

Images